Netscaler SDX::Bind VLAN config is missing from Secondary node when it is rebooted
Article ID: CTX205247
Updated On:
Description
On one VPX the LA channel shows up as LA/1 and on other VPX the LA channel shows up as LA/2.
The VLAN and bind VLAN commands are configured on both the nodes in HA separately.
Now if we reboot the Secondary node, after reboot the "bind vlan" command is showing on Primary but not shown on Secondary node.
This can be confirmed from CLI as well as GUI.
Resolution
The issue is reproducible in lab:
The issue is caused due to the different LA/x on your Primary and Secondary node.
On the Primary node it is LA/1 but on secondary node it is LA/2.
On Secondary node LA channel showing up as LA/2.
To fix the issue can you please do below:
=======
The issue is caused due to the different LA/x on your Primary and Secondary node.
On the Primary node it is LA/1 but on secondary node it is LA/2.
On Secondary node LA channel showing up as LA/2.
To fix the issue can you please do below:
=======
- From the SDX box which is hosting the Secondary VPX > Edit this instance > remove the LA/2 and bind any other interface (for testing) for now and click OK. It will ask for the reboot of Secondary node > Click YES to reboot Secondary.
- Once the Secondary node is back UP, remove the other interface we added for testing and re-add the LA/2 or the channel we want to the same Secondary VPX from SVM level > Click OK and it will ask for reboot again.
- Now when the Secondary comes back UP, please login to the VPX the channel will show up as LA/1.
- If it shows LA/1 then the Primary will sync the “add vlan” “bind vlan” command to secondary node and you will see the VLAN bound to LA/1 on Secondary automatically.
- Save the config on Primary and then reboot Secondary node to confirm if the “bind vlan” command is showing after reboot.
Problem Cause
The issue is caused due to the different LA/x channels (LA/1 on Primary and LA/2 on Secondary)
Was this article helpful?
Yes
No
Powered by
