![]() ![]() Unfortunately, it does ‘blackhole’ any orphan ports on the secondary switch. This prevents the duplication of frames and loops from forming. In a case where the peer-link has failed, but both switches are still up, the secondary will immediately disable it’s vPC member ports. Fortunately, due to the keepalive link, both peers are able to determine that both switches are up, and they will keep their primary and secondary roles. If there is a peer-link failure, the switches can no longer share control information. ![]() The peer-link is the most critical component of the vPC domain. LACP will see the switch pair as a single device. These values match on both peers, so there is a single System ID as far as LACP is concerned. The system-MAC is generated from the Domain ID and a pool of virtual MAC addresses. It does this by generating the System ID from the system MAC. vPC is crafty and gets around this problem. This would cause havoc for LACP, as there would be two different LAGIDs. If there is a mismatch, the ports are excluded or the LAG stays down, depending on the implementation.īut vPC uses two switches at one end of the link. All ports in a port-channel must have the same LAGID. These four values (two at each end) create a LAGID (Link Aggregation Group Identifier). The second value is an identifier for the LAG, such as the port-channel ID. ![]() Auto assignment comes from the system priority and the System MAC address. It is a 64-bit value which can be manually assigned or automatically generated. When creating a port channel, LACP does its due diligence and compares a few values. Connecting to more than one device at a time is an error as far as LACP is concerned. The LACP standard needs all connections in a LAG to be between two devices only. They need to negotiate their parameters with LACP. The devices that connect to vPC use normal etherchannels or LAGs. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |