PI 1.2 fails after ESXi server shutdown

[Jaaazman777]

Hello!

PI 1.2 virtual appliance ncs process doesn't start after shutting down the ESXi 5.0 host

We have the following deployment on ESXi 5.0 host

Small virtual appliance

• RAM minimum: 8 GB
• Hard disk minimum: 200 GB
• Processors: 4 virtual CPUs (vCPUs)

Before shutting down the ESXi, ncs process on PI 1.2 had been successfully shut down.

After ESX reloading PI 1.2 ncs proccess always starts with an error.

While starting the process (ncs start) there are the following errors (file is attached).

Has anyone faced this kind of problem?

[Scott Fella · Accepted solution]

There were a lot of issue with PI 1.2 and this was brought up at Cisco Live this year.  the recommendations from the developers was to bring up a new PI 1.3 and start from scratch.  This was the prefered way, now if your system is new, then this will be a good options, as you can just open a TAC case to rehost the license to your new VM.  If you have PI 1.2 that already ahs been setup with your floor plans, etc, then your in a tough spot as there are many ways to go about fixing this, but it might also delete your database.  Might be better to call TAC if you can't get the system running.  Here are some things you can try.

https://supportforums.cisco.com/docs/DOC-26960

ncs stop
ncs cleanup
ncs start

Here is a bug id:

CSCud33502 Bug Details

NCS121:ERROR: failback: Failed to start NCS on primary NCS after attempt

Symptom: After failback "Failed to start NCS on primary NCS after attempting registration with secondary".Conditions: NA. This scenario happens inconsistently.Workaround: NA

Thanks,

Scott

Help out other by using the rating system and marking answered questions as "Answered"

[Scott Fella]

Might want to look at this thread also:

https://supportforums.cisco.com/thread/2236452

Thanks,

Scott

Help out other by using the rating system and marking answered questions as "Answered"

[Jaaazman777]

I noticed some workaround:

Assume that PI 1.2 has IP from the 10.1.1.0/24

VMware has IP from the same network.

WMware is attached to switch access port.

When I change the virtual adapter to another network (ex. 10.2.2.0/24), PI boots successfully. After that I can change virtual adapter back to 10.1.1.0/24 and all works fine.

at the very first time during setup PI 1.2 was attached to that10.2.2.0/24 network and VMware was attached to trunk.

Then PI ip and virtual vm adapter moved to new netwrok 10.1.1.0/24