Jump to content

Recommended Posts

Posted

Hey all, thought I would try this forum hoping it can help.  I have two SDX 16000 hosts running multiple netscaler instances on different vlans.  Recently I was reviewing settings and connected to one of the hosts LOM interface and launched the console.  The Menu items had an incorrect host name so I thought I would try to change that.  When I selected the section "Network and Management Interface" to change this setting it seemed to reset all the network settings.  I was able to set them all back to what they were, but now when on the main menu the right side of the menus are all blank.   Everything seems to be responding though so I thought maybe just a bug.  However now on my SDX host when I view the list of Instances two of them are showing Down.  These instances are reachable and running, so that tells me that the SDX 'Manage through internal network' is not working.  I suspect it is because of what happened through the console interface which is Xenserver settings.   I've confirmed its not using Internal Network because the two instances mgmt IP are on the same network as the SVM mgmt IP,  and the using a mgmt PBR on the instances per best practices they are forcing return traffic to the gateway for that network.  This was not an issue before messing with the LOM menu.

So I have a SDX firmware upgrade scheduled this week so it will get a reboot.  I'm hoping this will clear things up but if not, any thoughts on why this occurred?  My second SDX setup the exact same way is not having this issue with any Instances, and the LOM console menu's/information look normal.
I have opened a support request for this, but the engineers have not been able to provide any useful information.

TIA.

2024-09-16_08-51-17.PNG

2024-09-16_08-50-40.PNG

Posted

The Citrix Devs should add a console message. "If you use this it will break".  That would be helpful

I'll post an update later this week after the upgrade and reboot as to whether this cleared up.

Posted

Ok, well the reboot of the SDX seemed to resolve the issue.  Everything looks normal again from the Console and communication restored from SVM to the Instances.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...