Determining port-to-port connectivity in an extended bridge
Techniques for determining port-to-port connectivity in an extended bridge are provided. According to one set of embodiments, a port extender (PE) of the extended bridge (e.g., a base PE) can build a local database comprising connectivity information for one or more physical cascade ports of the PE. This building can be based on one or more messages received from another PE in the extended bridge (e.g., a transit PE) that is directly connected to the PE. The PE can then transmit, at a time of joining the extended bridge, the connectivity information to a controlling bridge (CB) of the extended bridge for storage thereon.
1. A method comprising:
building, by a port extender (PE) in an extended bridge, a local database comprising connectivity information for a plurality of physical cascade ports of the PE, wherein the building is based, at least in part, on one or more messages received from another PE in the extended bridge that is directly connected to the PE via a cascade trunk including two or more of the plurality of physical cascade ports, and wherein the connectivity information includes:
an indication of the cascade trunk;
identities of the two or more physical cascade ports in the cascade trunk; and
identities of two or more other physical cascade ports on said another PE that are directly connected to the two or more physical cascade ports in the cascade trunk; and
transmitting, by the PE at a time of joining the extended bridge, the connectivity information to a controlling bridge (CB) of the extended bridge.
2. The method of claim 1 wherein said another PE is a transit PE situated between the PE and the CB.
3. The method of claim 1 wherein the one or more messages are Link Layer Discovery Protocol (LLDP) messages.
4. The method of claim 1 wherein the one or more messages are inter-process communication (IPC) messages.
5. The method of claim 1 wherein the one or more messages are received at a time said another PE joins the extended bridge.
6. The method of claim 1 wherein the PE receives one message on each of the two or more physical cascade ports in the cascade trunk.
7. The method of claim 1 wherein the PE determines the connectivity information based on header information included in the one or more messages.
8. The method of claim 1 wherein the CB is configured to use the connectivity information for validating dynamic cascade port or link aggregation group (LAG) changes in the extended bridge.
9. The method of claim 1 wherein the CB is configured to use the connectivity information to display a topology of the extended bridge to a user.
10. A non-transitory computer readable storage medium having stored thereon program code executable by a port extender (PE) in an extended bridge, the program code causing the PE to:
build a local database comprising connectivity information for a plurality of physical cascade ports of the PE, wherein the building is based, at least in part, on one or more messages received from another PE in the extended bridge that is directly connected to the PE via a cascade trunk including two or more of the plurality of physical cascade ports, and wherein the connectivity information includes:
an indication of the cascade trunk;
identities of the two or more physical cascade ports in the cascade trunk; and
identities of two or more other physical cascade ports on said another PE that are directly connected to the two or more physical cascade ports in the cascade trunk; and
transmit, at a time of joining the extended bridge, the connectivity information to a controlling bridge (CB) of the extended bridge.
11. The non-transitory computer readable storage medium of claim 10 wherein said another PE is a transit PE situated between the PE and the CB.
12. The non-transitory computer readable storage medium of claim 10 wherein the one or more messages are received at a time said another PE joins the extended bridge.
13. The non-transitory computer readable storage medium of claim 10 wherein the PE determines the connectivity information based on header information included in the one or more messages.
14. A port extender (PE) for use in an extended bridge, the PE comprising:
a processor; and
a non-transitory computer readable medium having stored thereon program code that, when executed by the processor, causes the processor to:
build a local database comprising connectivity information for a plurality of physical cascade ports of the PE, wherein the building is based, at least in part, on one or more messages received from another PE in the extended bridge that is directly connected to the PE via a cascade trunk including two or more of the plurality of physical cascade ports, and wherein the connectivity information includes:
an indication of the cascade trunk;
identities of the two or more physical cascade ports in the cascade trunk; and
identities of two or more other physical cascade ports on said another PE that are directly connected to the two or more physical cascade ports in the cascade trunk; and
transmit, at a time of joining the extended bridge, the connectivity information to a controlling bridge (CB) of the extended bridge.
15. The PE of claim 14 wherein said another PE is a transit PE situated between the PE and the CB.
16. The PE of claim 14 wherein the one or more messages are received at a time said another PE joins the extended bridge.
17. The PE of claim 14 wherein the PE determines the connectivity information based on header information included in the one or more messages.