I need a quick sanity check. I am having problems setting up EtherChannel between an HP server and a Cat 2960G switch. I have the switchports in "active", and 802.3ad configured on the server. I can get the bundling working, but whenever the server re-boots, the EtherChannel goes into an inconsistent state: the switch believes the two links are bundled correctly, but the server does not. If I then shut and no shut the Po interface, the bundle comes up correctly on both sides. But clearly I cannot be on hand every time the server guys want to reboot their server.
The HP support guy wants me to moinitor the LACP during the re-boot. I set up debug lacp all, and sent him the results, but he is not happy with that ... he wants a Wireshark trace. Now, is that possible? As far as I can see, LACP uses the IEEE Slow_Protocols_Multicast 01:80:C2:00:00:02, which is link-constrained. That is, it will not be forwarded by any MAC bridge. So presumably that means I will not see it on a SPAN or RSPAN monitor. (That makes sense, because if a link-constrained protocol were seen outside its proper link, it could play havoc with the topology, unless it were hidden inside some encapsulation.)
So, excuse me if I am being thick, but has anyone here ever successfully done a 2-way trace of LACP using Wireshark? If so, how did you do it? Is there some sort of two-ended probe you can put in the cable or something?
P.S. It is so long since I was last on this forum that everything has all changed. It feels like going back to your native country after a 20-year absence.
It's been a while since i saw you on here. NetPro has changed quite a bit i guess compared to the old site Hope your'e well and enjoying the benefits of being a CCIE.
As for SPAN, i must admit my understanding was that SPAN was fairly dumb in that it simply sent a copy of every packet to the destination span port. I have never captured LACP packets but i can't see why they should be any different. Indeed some of the config guides explicitly state that you can capture LACP packets with SPAN -
Hi Jon, it's good to hear ffrom you, and congratulations on all those points you have built up. I am relieved to see so many familiar names here. So even if the geography of the "country" has changed, my old friends are still my friends.
Sorry, revised this posting. Clicked before fully engaging brain.
Is it possible that the layer-2 link-local stuff can be monitored by SPAN but not by RSPAN? I did an RSPAN of the ports I was interested, but I could not see any CDP, for example, even though CDP is actually running on the monitored ports.
The config guides across switches and even the different release config guides for the same switch are not consistent in their information. Some talk only about BPDUs not being able to be monitored whilst some talk of BPDUs + other L2 switch protocols. But i would assume this is why you did not see any CDP packets in your RSPAN.
OK, I've got it now. On the 2960, layer-2 control protocols (LACP, STP, etc.) are not replicated into a SPAN session unless you include the keywords encapsulation replicate in the monitor destination, like:
If the destination is an RSPAN VLAN (monitor session 1 destination remote vlan 40), then you are not offered any of the encapsulation options. That way, the replicated packets cannot confuse the topology on their way from the monitored point to the monitorng point.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...