Abstract: Equipment generates a discovery message containing its address/node identification (ID) and/or other information. Adjacent equipment (e.g., physically adjacent equipment) monitors control overhead bytes (section trace (J0) bytes, Data Communication Channel (DCC) control overhead, General Communication Channel (GCC) control overhead, etc.) for this message, but does not generate a corresponding response message as called for in the standards/implementation agreements. Rather, it records the address/node ID and/or other information in order to identify its neighbor, and uses an alternative mechanism to either record the adjacency separately (e.g., at a Network Management System (NMS) in order to populate or verify its topology database) or communicate an out-of-band control message to the neighbor (e.g., using the received address/node ID as the destination address for the out-of-band control message, which carries its own address/node ID and link information).

Abstract: Equipment generates a discovery message containing its address/node identification (ID) and/or other information. Adjacent equipment (e.g., physically adjacent equipment) monitors control overhead bytes (section trace (J0) bytes, Data Communication Channel (DCC) control overhead, General Communication Channel (GCC) control overhead, etc.) for this message, but does not generate a corresponding response message as called for in the standards/implementation agreements. Rather, it records the address/node ID and/or other information in order to identify its neighbor, and uses an alternative mechanism to either record the adjacency separately (e.g., at a Network Management System (NMS) in order to populate or verify its topology database) or communicate an out-of-band control message to the neighbor (e.g., using the received address/node ID as the destination address for the out-of-band control message, which carries its own address/node ID and link information).