Cisco Cisco Prime Network 4.0 ユーザーガイド
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
Cisco Prime Network 4.0 Supported Technologies and Topologies
22
OL-29352-01
6.2.12 GRE Tunnel Information
In this technique, each GRE tunnel is identified by the following criteria:
1. Source IP.
2. Destination IP.
2. Destination IP.
Taking the example of two tunnels T1 and T2 to match, the source IP address of T1 is
compared to the destination IP address of T2. Similarly, the destination IP address of T1 is
compared to the source IP address of T2.
compared to the destination IP address of T2. Similarly, the destination IP address of T1 is
compared to the source IP address of T2.
6.2.13 Pseudowire Information
In this technique, each pseudowire is identified by the following criteria:
Local and Remote router IP.
Tunnel ID.
Taking the example of two pseudowire tunnels Pw1 and Pw2 to match:
The local IP of Pw1 is compared to the remote IP of Pw2 and the remote IP of Pw1
is compared to the local IP of Pw2.
is compared to the local IP of Pw2.
Tunnel ID
6.2.14 VLAN ID Matching
In this technique, the VLAN configuration aspects of each pair of VLAN-enabled physically
connected Ethernet ports will be inspected to identify which VLAN tagged traffic crosses
this link. The type of VLAN configurations that are inspected include:
connected Ethernet ports will be inspected to identify which VLAN tagged traffic crosses
this link. The type of VLAN configurations that are inspected include:
Switchport in all configuration modes (Access, Trunk, Dot1q_Tunnel), including the
VLAN allowed and VLAN mapping.
VLAN allowed and VLAN mapping.
L2 sub-interfaces/service instances configured on the Ethernet port, specifically the
VLAN tag matching criteria.
VLAN tag matching criteria.
L3 sub-interfaces configured on the Ethernet port, specifically the VLAN tag
matching criteria.
matching criteria.
6.2.15 Route Targets
In this technique, each VRF is identified with the set of its import and export route targets
(for either IPv4 or IPv6 address families).
Atleast one pair of import or export route target of one VRF entity is matched to the export
or import route target or the other VRF entity.
(for either IPv4 or IPv6 address families).
Atleast one pair of import or export route target of one VRF entity is matched to the export
or import route target or the other VRF entity.
6.2.16 Physical Layer Counters
The physical layer is used for topology verification (that is, if a link has already been
discovered, it is tested periodically), which is done using counters. Physical layer counters
are based on the port traffic signature, using octet-based or octet- and packet–based
traffic.
Using the port traffic signature, it is possible to disqualify a connection between two ports
based on their counters.
discovered, it is tested periodically), which is done using counters. Physical layer counters
are based on the port traffic signature, using octet-based or octet- and packet–based
traffic.
Using the port traffic signature, it is possible to disqualify a connection between two ports
based on their counters.
6.2.17 IP Testing
Prime Network uses IP testing (IPv4) to discover the topology for PPP/HDCL and MPLS
technologies. In both cases, the IP test checks the IP configuration on the relevant
technologies. In both cases, the IP test checks the IP configuration on the relevant