02-20-2014 04:46 PM - edited 07-05-2021 12:15 AM
Hi All,
I am having a problem getting my MSE joined to my WCS.
It was joined at one point, but we changed the IP address on the eth0 interface from one IP to another and now it's showing up in WCS as UNREACHABLE. I have run through the setup of my MSE a couple of times, but no luck. Any thoughts?
I can ping the IP on the eth0 interface from the WCS server, but it still will not connect. We have already validated that the WCS username and password is correct by running through the setup.sh wizard.
Also, does it matter of eth0 and eth1 are the same IP address? They appear to be, but ICMP reachability exists with no packet loss. Is there a way to clear the arp cache or something like that? I noticed that when we change the IP back to the original, IP connectivity is restored. Seems odd.
Best Regards,
John
Solved! Go to Solution.
02-20-2014 05:24 PM
Try these commands
service mse stop
iptables -f
shutdown -r now
When the MSE comes back up
ifconfig -a
02-20-2014 05:04 PM
Make sure you restart the network
/etc/init.d/network restart
Sent from Cisco Technical Support iPhone App
02-20-2014 05:07 PM
Isn't the network restarted when the MSE restarts all the services following the setup.sh wizard?
Is the above information correct (yes, no, or ^): yes
------------------------------------------------------------
Setup will now attempt to apply the configuration.
Setting password/login parameters....
Setting wcs username.
Setting wcs password.
Restarting network services with new settings.
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Restarting MSE framework service.
Stopping MSE Platform
Thanks,
John
02-20-2014 05:09 PM
If you reboot the VM
Sent from Cisco Technical Support iPhone App
02-20-2014 05:10 PM
The MSE is a different service than the OS. So you have to restart the service.
Sent from Cisco Technical Support iPhone App
02-20-2014 05:16 PM
Give it a try and see if that fixes the issue.
Sent from Cisco Technical Support iPhone App
02-20-2014 05:18 PM
Hi Scott,
I just tried it, but it didn't fix the problem.
Someone told me about a command to clear the IP table? Have you heard of this?
Maybe I need to open a TAC case.
Regards,
John
02-20-2014 05:24 PM
Try these commands
service mse stop
iptables -f
shutdown -r now
When the MSE comes back up
ifconfig -a
02-20-2014 05:34 PM
Thanks, that worked. What happened?
02-20-2014 05:37 PM
Don't know... Most times you don't need to flush the tables, but sometimes you do. Typically the MSE doesn't get an IP change, but at least you know how to fix it now:)
Sent from Cisco Technical Support iPhone App
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: