Cisco Cisco Prime Network 4.0 ユーザーガイド
Cisco Prime Network 4.0 Supported Technologies and Topologies
OL-29352-01
17
6.1.12 Pseudowire
The Pseudowire topology represents a link between the endpoints of an MPLS-based
pseudowire tunnel in the network. In the VNE model, the endpoints of the link are PTP
Layer 2 MPLS tunnel IMOs (IPTPLayer2MplsTunnel), which represent the pseudowire
tunnel endpoints.
Prime Network discovers PWE3 Network layer topology by searching for matches between
the local and remote router IP addresses in any one-hop-away remote side’s PTP Layer 2
MPLS tunnel. In particular, it compares the local and remote router IP addresses and
tunnel identifications.
Link type: Tunnel
Discovery and verification technique:
pseudowire tunnel in the network. In the VNE model, the endpoints of the link are PTP
Layer 2 MPLS tunnel IMOs (IPTPLayer2MplsTunnel), which represent the pseudowire
tunnel endpoints.
Prime Network discovers PWE3 Network layer topology by searching for matches between
the local and remote router IP addresses in any one-hop-away remote side’s PTP Layer 2
MPLS tunnel. In particular, it compares the local and remote router IP addresses and
tunnel identifications.
Link type: Tunnel
Discovery and verification technique:
6.1.13 GRE Tunnel
The GRE Tunnel topology represents a link between the endpoints of a GRE tunnel in the
network. In the VNE model, the endpoints of the link are GRE Tunnel IMOs (Generic
Routing Encapsulation (GRE) Tunnel Interface (ITunnelGRE)), which represent the GRE
tunnel endpoints.
Prime Network discovers the GRE topology by comparing the source and destination IP
address on both sides accordingly.
Link type: GRE tunnel
Discovery and verification technique:
network. In the VNE model, the endpoints of the link are GRE Tunnel IMOs (Generic
Routing Encapsulation (GRE) Tunnel Interface (ITunnelGRE)), which represent the GRE
tunnel endpoints.
Prime Network discovers the GRE topology by comparing the source and destination IP
address on both sides accordingly.
Link type: GRE tunnel
Discovery and verification technique:
6.1.14 VPN
The VPN topology represents a link between two VRFs that are part of a VPN. In other
words, VPN traffic can pass between customer sites connected to these VRFs. In the VNE
model, the endpoints of the link are VRF IMOs (Virtual Routing Forwarding (VRF) Entity
(IVrf)), which represent the VRF forwarding entities in the network element.
Prime Network discovers MPLS-BGP-based VPN network topology by searching for the
existence of a local VRF entity’s imported route taget among the exported route targets of
any remote side.
Link type: VPN or VPNv6
Discovery and verification techniques:
words, VPN traffic can pass between customer sites connected to these VRFs. In the VNE
model, the endpoints of the link are VRF IMOs (Virtual Routing Forwarding (VRF) Entity
(IVrf)), which represent the VRF forwarding entities in the network element.
Prime Network discovers MPLS-BGP-based VPN network topology by searching for the
existence of a local VRF entity’s imported route taget among the exported route targets of
any remote side.
Link type: VPN or VPNv6
Discovery and verification techniques:
families.
6.1.15 VLAN Service Links
A VLAN service link represents either an Ethernet or a LAG link in the context of a specific
VLAN. It connects two Ethernet Flow Point entities, which represent Ethernet or LAG ports
in the context of a specific VLAN, or with VLAN match criteria.
The two Ethernet Flow Points can reside in the same Layer 2 domain, or connect between
two different Layer 2 domains when a VLAN TAG manipulation is used.
The VLAN service links are not discovered using the standard topology mechanism that
resides in the VNE layer, but rather by the Carrier Ethernet discovery. The discovery
mechanism uses Ethernet and LAG links, VNE inventory modeling information of the
Ethernet/LAG interfaces, and Ethernet Flow Point entities as inputs for the VLAN service
VLAN. It connects two Ethernet Flow Point entities, which represent Ethernet or LAG ports
in the context of a specific VLAN, or with VLAN match criteria.
The two Ethernet Flow Points can reside in the same Layer 2 domain, or connect between
two different Layer 2 domains when a VLAN TAG manipulation is used.
The VLAN service links are not discovered using the standard topology mechanism that
resides in the VNE layer, but rather by the Carrier Ethernet discovery. The discovery
mechanism uses Ethernet and LAG links, VNE inventory modeling information of the
Ethernet/LAG interfaces, and Ethernet Flow Point entities as inputs for the VLAN service