03-30-2013 01:04 AM - edited 07-03-2021 11:48 PM
Hello,
We have installed 2 new WiSM-2 in HA with software version 7.3. We have also upgrade NCS 1.1 to PI 1.2.
After adding the primairy WiSM-2 in PI we can manage the WiSM-2 for a short time from PI. But after a few minutes we lost the connection to the WiSM. After searching while we experience the problem we found the following:
- PI and WiSM are in the same subnet
- Both PI and WiSM can ping the gateway.
- Both PI and WiSM can ping a lot of other devices in the same subnet and other subnets.
- We can manage PI and WiSM directly from it's ownGUI.
- PI and WiSM have each others ARP entry in their own ARP table
- BUT PI AND WISM CANNOT PING EACH OTHER
- after doing a 'clear arp' on the WiSM the connection between PI and the WiSM is established again for a few minutes and we can manage the WiSM from PI.
Does someone expecting the smae problem and a solution for this?
Thank you in advance
Sent from Cisco Technical Support iPad App
03-30-2013 01:27 AM
What exact PI versoin you have? what exact WiSM version you are running?
Make sure versions are compatible as per:
Rating useful replies is more useful than saying "Thank you"
03-30-2013 03:07 AM
Hi Amjad,
The versions we're using are compatible
PI version 1.2.1
WiSM version 7.3.112.0
When I clear the arp table it's working for a few minutes......
Sent from Cisco Technical Support iPad App
04-03-2013 06:59 AM
It might sound silly but I feel that you should check the IP addressing, or Vlan config on the connecting switch or ICMP needs to be checked on PI using the icmp-status and traceroute command.
HTH
04-04-2013 12:55 AM
Thanks for your response.
I checked the IP addressing VLAN Config but these are correct. If it wasn’t you should think that communication isn’t possible at all.
ICMP is enabled in the NCS. Both devices are in the same subnet so the traceroute just shows 1 hop.
NCS/admin# show icmp_status
icmp echo response is turned on
NCS/admin# traceroute 192.168.x.x
traceroute to 192.168.x.x (192.168.x.x), 30 hops max, 40 byte packets
1 192.168.x.x 0.758 ms 0.790 ms 0.837 ms
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