01-18-2015 08:19 PM - edited 03-19-2019 09:03 AM
Hi,
I have re-started cucm sub/pub on esxi host 5.0 and now i'm anable to access web GUI and can't ping to server IP.
can access the console on vmware ping between two server work fine.
Any idea to resolve this?
01-18-2015 08:42 PM
Frank - GUI can take upto 10 mins or so to come up. but if your servers are up you should be able to ping. Can you confirm you are still no able ping your server? Can you check and post back what you see on the output of show network eth0?
If you are not able to ping you can try and see if it makes any difference:
set network status eth0 down
set network status eth0 up
-Terry
Please rate all helpful posts
01-19-2015 12:14 AM
Hi Terry,
This is the response from TAC.
Sometime i'm able to ping and can access but suddenly stop connectivity. there is a unity server on same host it has connectivity all the time.
below comment from cisco tac.
Ping to SUB was failing.
Logged in to VSphere Client, did not see any error/events for the server.
“utils diagnose test” and “show network eth0 detail” did not give any errors.
Able to ping the PUB, NTP and the default gateway from the SUB.
SUB is reachable from the PUB as well with DB replication in a state of 2.
By this time SUB was reachable as well.
Pulled Syslog to check for any errors and we did not see any.
No issues on the SUB.
Thanks,
01-19-2015 01:02 AM
Is it resolved now - if not, whats outstanding? Did the issue fix by itself?
-Terry
01-19-2015 04:29 AM
yes I think its fixed by itself done some restarting virtual machine and esxi host but didn't work at all. after 45-50 minutes I was able to ping.
need to know how to resolve the issue rather than waiting 1 hour or next time it will not fixed by itself.
Thanks,
01-19-2015 04:39 PM
Its hard to tell without seeing all logs etc. As you already have a TA case I think TAC is in best position to comment why this happened. Let us know the outcome of TAC case.
-Terry
01-19-2015 04:52 PM
actually they told me there is no issue with cucm vm or esxi host config.
this should be routing issue. but it was working well before restarted vm and there's no routing issue.
01-19-2015 04:55 PM
As I said before its hard to find out what went wrong at this stage. In case, you get into similar situation log a TAC case right away. Unfortunately, that's the only advice I have for the time being.
-Terry
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide