Sandy Williams Posted April 24, 2018 Posted April 24, 2018 Hello, trying to migrate a VIP from one VPX to another VPX. I deleted the VIP from the old VPX and adding it to the new VPX (after removing the IP I tried pinging it and got nothing). add lb vserver Storefront_LB_VS SSL x.x.x.x 443 ERROR: Address already in use I also tried 'show arp' on the new VPX and saw the IP so I removed it from ARP. I'm at a loss now.. I gave up and added the IP back to the old VPX because I'm wasting a lot of time. The new VPX is running the very latest firmware - NS12.0 Build 57.24. The VPX that was my old one is running a few minor builds older..
Ryan Goldstein Posted April 24, 2018 Posted April 24, 2018 go under netork > IP addresses and remove the IP from the orginal netscaler, removing VIP does not remove IP. Maybe even on new netscaler its their by mistake
Sandy Williams Posted April 24, 2018 Author Posted April 24, 2018 Nope, as soon as I remove the VIP the IP doesn't show up under network > IP Addresses I just tried again, removed and tried to re-add to new.. nope.. On both did 'sh run | grep "< ip address>" and there's nothing
Madhur Walia Posted April 24, 2018 Posted April 24, 2018 Hi, Can you connect the new NS to putty and run "sh run | grep <VIP IP>". If this IP is already configured on NS, you will get to know the related config. Regards, Madhur
Sandy Williams Posted April 24, 2018 Author Posted April 24, 2018 Yes, on both I ran 'sh run | grep "< ip address>"' and there's nothing (after I removed it from the old VPX)
Eric Wiegand Posted June 17, 2019 Posted June 17, 2019 This is happening to me too. The network > IP address is gone. There's nothing in sh ns runningconfig -withdefaults... still says Address in use. I'm on NetScaler NS12.0: Build 60.10.nc
Eric Wiegand Posted June 17, 2019 Posted June 17, 2019 On 4/24/2018 at 4:10 PM, Sandy Williams said: Yes, on both I ran 'sh run | grep "< ip address>"' and there's nothing (after I removed it from the old VPX) Ok. so I figured it out. The Netscaler apparently creates a system service under the hood when you use a domain name in the session profiles. I was able to reuse the IP by unbinding the session profiles from Gateway and also editing the session action -wihome value with a fake url. Once I changed the session action to a temporary bogus url, it allowed me to reuse the IP.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.