We help IT Professionals succeed at work.
Troubleshooting Question

Cannot move Citrix Netscaler server to a new Hyper-V host

J.R. Sitman
J.R. Sitman asked
on
86 Views
Last Modified: 2020-09-30
When I copy the Netscaler Virtual disk to a new Hyper-V host and then create a new VM, the new VM starts fine but when I try to access it's IP address I cannot.

So I have to turn off the new VM and start the original VM.

I have no idea why this is happening.   I copied and moved 4 other VM from one server to another and they all work fine.

Comment
Watch Question

Olivier MARCHETTACitrix Support and Infrastructure Engineer
CERTIFIED EXPERT

Commented:
Netscaler is a network appliance, if you move only the disk, and create a new VM with a new network adapter and with a new MAC address, this could explain why it is not working. If you do not want to reconfigure the network, I would recommend you to properly export/import the VM.
J.R. SitmanIT Director

Author

Commented:
Can it be exported while it's running or does it have to be shut down
Olivier MARCHETTACitrix Support and Infrastructure Engineer
CERTIFIED EXPERT

Commented:
I am not an Hyper-V expert but I would personnally shut down the VM and merge (delete) all snapshots before exporting.
J.R. SitmanIT Director

Author

Commented:
Thanks
J.R. SitmanIT Director

Author

Commented:
The export, import went fine.   I was able to access Netscaler via it's IP address, however, we cannot log into Citrix receiver.  I shut down the new VM and started the original.  We can log in to Citrix.

Any help will be appreciated.
Olivier MARCHETTACitrix Support and Infrastructure Engineer
CERTIFIED EXPERT

Commented:
What is the error when trying to login? Does the new Hyper-V host has access to the network where StoreFront and Active Directory are located?
J.R. SitmanIT Director

Author

Commented:
The Store App is not currently available.   I've never tested access to the StoreFront.    How?
Olivier MARCHETTACitrix Support and Infrastructure Engineer
CERTIFIED EXPERT

Commented:
Use the IP addersses of your Citrix Infrastructure servers.You should have a Citrix Delivery Controller and a StoreFront server, but note that sometimes, in small deployments, the StoreFront server is deployed on the same machine as the Delivery Controller.

Try to ping the Citrix infrastructure server adresses from your new Hyper-V host and from the virtual network used by NetScaler. Make sure that you have a connectivity between NetScaler and the Citrix backend infrastructure from the new Hyper-V host. 

J.R. SitmanIT Director

Author

Commented:
I can ping in both directions.   From the server that is the Store to the new Host and from the Host to the Store.   The new host has 3 IP's 2 that are NIC and one Virtual.   would that have any effect?
Olivier MARCHETTACitrix Support and Infrastructure Engineer
CERTIFIED EXPERT

Commented:
Ideally you should make the same test from the NetScaler appliance.
Login to the NetScaler console and run some ping test.

Are you using the same VLAN on the NetScaler VM NIC on the new host?
NetScaler has a minimum of 3 IP addresses: NSIP, SNIP, VIP. That's 1 for the interface admin, 1 for the backend communications and 1 for the NS Gateway portal (where your users logs in). So it is important to use the exact same VLAN configuration.
J.R. SitmanIT Director

Author

Commented:
Before I do that I want to make sure starting the new Netscaler appliance won't conflict with the existing one.   Let me know.
Olivier MARCHETTACitrix Support and Infrastructure Engineer
CERTIFIED EXPERT

Commented:
It will conflict because it will use the same IP addresses. You cannot have them both running at the same time on the same VLAN. 
J.R. SitmanIT Director

Author

Commented:
OK
J.R. SitmanIT Director

Author

Commented:
I stopped the original VM and started the new VM.   I tried pinging the Store and two other servers.   I could not ping any of them.
Olivier MARCHETTACitrix Support and Infrastructure Engineer
CERTIFIED EXPERT

Commented:
If you can ping the Storefront server / Actrive Directory server from your Hyper-V host but not from the  hosted VM, it's maybe caused by a vritual switch or physical switch misconfiguration.

Check the virtual switch properties in Hyper-V, make sure it's connected to the appropriate network card.
There's also maybe a misconfiguration at the physical switch level.
Check the switch port configuration or trunk / VLAN aggregation on your physical switch to make sure that you have the same VLAN configuration used by the other Hyper-V host.

In order to make sure that this is not related to the NetScaler appliance, I would perosnnally quickly deploy a small linux VM connected to the new Hyper-V host, connected to the same virtual switch, amd make some ping test.


J.R. SitmanIT Director

Author

Commented:
I'll look again tonight.   Thanks
IT Director
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION

Gain unlimited access to on-demand training courses with an Experts Exchange subscription.

Get Access
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Empower Your Career
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions