- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Re: R81.10 cluster release mismatch
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
R81.10 cluster release mismatch
I think I've found a bug in R81.10 cluster XL
The command show cluster release show "Cluster Mismatch" even if the release is the same between the gateways
I tthink the problem is the sequence of the output : see below
gw-1> show cluster release
Release: R81.10 T335
Kernel build: 996000021
FW1 build: 996000020
FW1 private fixes: HOTFIX_GOT_TPCONF_AUTOUPDATE
HOTFIX_PUBLIC_CLOUD_CA_BUNDLE_AUTOUPDATE
HOTFIX_R80_40_MAAS_TUNNEL_AUTOUPDATE
HOTFIX_R81_10_JUMBO_HF_MAIN
ID SW release
1 (local) R81.10 T335
2 R81.10 T335 (Mismatch)
gw-2> show cluster release
Release: R81.10 T335
Kernel build: 996000021
FW1 build: 996000020
FW1 private fixes: HOTFIX_GOT_TPCONF_AUTOUPDATE
HOTFIX_PUBLIC_CLOUD_CA_BUNDLE_AUTOUPDATE
HOTFIX_R81_10_JUMBO_HF_MAIN
HOTFIX_R80_40_MAAS_TUNNEL_AUTOUPDATE
ID SW release
1 R81.10 T335 (Mismatch)
2 (local) R81.10 T335
There is a simple way to fix that?
PS: also Cpinf -y all have different sequences of the same HF
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thats been like that since base R80.
