https://worldofeuc.com logo
Join Slack
Powered by
I changed a NetScaler IP address through the GUI, ...
# citrix-netscaler
j
I changed a NetScaler IP address through the GUI, it asks for a reboot - yet as soon as the reboot finishes it has gone back to the old IP address. What gives?
j
How did you change the NSIP in the GUI? (Care to make a screenshot 🙂 )
That said (or asked if you prefer), NSIP changes should never be done using the GUI. Drop into a NetScaler shell, and use the command :
Copy code
set ns config -IPAddress <...> -netmask <...>
Before you issue the reboot command (or let the previous command do it), make sure you save the config.
j
Should the NSIP be the same on both nodes? I did it through the GUI 😞
r
no, NSIP is different on both nodes
j
No! NSIP = individual IP address, unique for every node. SNIP (and others) = owned by the HA Pair or cluster
So, while you can change the SNIP (Subnet IP) through the GUI, the NSIP you shouldn't (although it probably allows you to if you were able to do it)
So, in practice I usually have 3 sequential IP addresses for management: For example: Node 1 - NSIP: 192.168.100.101 Node 2 - NSIP: 192.168.100.102 SNIP for management: 192.168.100.100
(The SNIP will always point to the PRIMARY node in an HA pair)
j
Sorry I meant the SNIP on both nodes, my brain is fried
j
The SNIP will be the same yes, but only active on the PRIMARY node
(as it is shared)
j
So do you set a SNIP on the secondary?
j
on failover, the NetScaler will send a gratitious ARP packet to the upstream switches to inform them the MAC Address for the IP has changed, so traffic can reach the other node
No, let's say you just configured to nodes in a HA pair. As soon as you add it on the primary node, it will pop-up on the secondary as well
The important part being that you manage changes on a HA Pair from the PRIMARY node
j
OK
j
Hence, once you have configured HA and added a SNIP, you do all changes from the SNIP
(because that will connect you to the primary node automatically)
c
FYI if you are also adding a new snip you need to make sure its bound to relevant VLAN's with the interfaces on the Netscaler and you may have to change firewall rules as the netscaler will use the SNIP as the source ip for backend communication
j
OK, so if I change the IP address through the GUI and don't set a SNIP (I need to add it to the HA pair once I change the IP address), once I've done it about five times and it keeps going back to the old one, should I assume it's not working and do the command line instead?
j
NSIP changes, always on CLI 🙂
👍 1
j
OK let me try that after I pick my son up
OK so if I change the IP address from the CLI I get the same behaviour, reboot and it has gone back to the old one
I'm tapping out, my head is done in
So I connect via SSH, show ns config shows the old IP address, do set ns config -IPAddress x.x.x.x -netmask x.x.x.x then save ns config, then reboot - and it just changes back? Is there a log somewhere I can check?
👍 1
r
shell / cd nsconfig / cat ns.conf | grep ip
after you change it, and save config
j
hmmm
the output looks like this
j
grep -i ip
j
Think I've sorted it - there was a screw-up in the Azure network settings 🤦‍♂️
When you add a new node to an HA pair, do you do it from the primary (existing) node or secondary (new) - or does it not matter?
Oh fuck I think I've done it the wrong way round. I'm having a real bad day
r
well dang, you didn't mention Azure. 😄 No worries bud. cheers
j
Haha. I've just had to restore the primary to a snapshot because of my blonde moment there - looks like I will be redoing the upgrade tomorrow.
But I think I might survive now 🙂
j
Nsip is the appliance ip address, the management ip. You would ssh to the nsip for each appliance. The SNIP is a floating IP address that the netscaler uses to route traffic to back end networks. The primary in a ha pair owns the snip, in a failover this along with vips fail over to the secondary. The SNIp can be changed, or multiple can be added. They should always be changed on the primary
Open in Slack
PreviousNext
Powered by