Cisco Cisco Prime Network 4.0 ユーザーガイド
Cisco Prime Network 4.0 Supported Technologies and Topologies
OL-29352-01
21
6.2.4 PNNI Information
In this technique, each port in the ATM switch is identified with two values:
Node ID.
Port ID.
6.2.5 BFD Session Source and Destination
In this technique, the source and destination addresses of a BDF session are verified by
matching them against the source and destination addresses of the potential adjacent
neighbors. The session’s source address is matched to the neighbor’s destination address
and the session’s destination source is matched to the neighbor’s source address since one
side’s source is the other side’s destination. This method works on the assumption that
multiple BFD sessions running on the same router cannot have the same source and
destination address.
matching them against the source and destination addresses of the potential adjacent
neighbors. The session’s source address is matched to the neighbor’s destination address
and the session’s destination source is matched to the neighbor’s source address since one
side’s source is the other side’s destination. This method works on the assumption that
multiple BFD sessions running on the same router cannot have the same source and
destination address.
6.2.6 BGP Information
In this technique, the local BGP identifier is compared to the remote BGP identifier or a
potential neighbor for each BGP Neighbor Entry. This topology technique assumes
uniqueness of the BGP identifier in the network.
potential neighbor for each BGP Neighbor Entry. This topology technique assumes
uniqueness of the BGP identifier in the network.
6.2.7 MAC
In this technique, the Ethernet port MAC is checked to see if it is the only one learned on
the other Ethernet port (using bridge and ARP tables).
This technique discovers links between two routers or the router and switch, but not
between two switches (includes the generic VNE).
the other Ethernet port (using bridge and ARP tables).
This technique discovers links between two routers or the router and switch, but not
between two switches (includes the generic VNE).
6.2.8 REP (Resilient Ethernet Protocol)
If REP is enabled between switches, the information that is provided by the 'show REP
topology' command is used to connect the topology according to the REP configuration.
topology' command is used to connect the topology according to the REP configuration.
6.2.9 LACP
If the LAG is configured as LACP, actor and partner system ID are compared between the
two devices (local actor = remote partner and vice versa).
two devices (local actor = remote partner and vice versa).
6.2.10 OAM
If OAM is configured between two devices, local and remote OAM MACs are compared
between the two devices (local OAM MAC = remote OAM MAC and vice versa).
This protocol has the highest priority and hence will be the first to be checked if it is
enabled.
between the two devices (local OAM MAC = remote OAM MAC and vice versa).
This protocol has the highest priority and hence will be the first to be checked if it is
enabled.
6.2.11 MLPPP Endpoint Identifier
In this technique, the Local and the Remote MLPPP End Point Identifier are verified by
matching them against the Remote and the Local MLPPP End Point Identifier of the
potential adjacent neighbors.
The Local MLPPP End Point Identifier is matched to the neighbor Remote MLPPP End Point
Identifier.
matching them against the Remote and the Local MLPPP End Point Identifier of the
potential adjacent neighbors.
The Local MLPPP End Point Identifier is matched to the neighbor Remote MLPPP End Point
Identifier.