Cisco Cisco Prime Network 4.2 Mode D'Emploi
Cisco Prime Network 4.2.2 Supported Technologies and Topologies
22
Link type: MPLS-TP.
The link is bidirectional.
The link is bidirectional.
Discovery and verification techniques:
6.1.18 FC and FCoE
The Fiber Channel (FC) and Fiber Channel over Ethernet (FCoE) topologies represent a link between two
native Fiber Channel interfaces or between two Fiber Channel components of FCoE interfaces that are
connected in the network. In the VNE model, the endpoints of the link are Fiber Channel IMOs
(IFiberChannel), which represent the underlying native (FC) or virtual (FCoE) Fiber Channel ports.
native Fiber Channel interfaces or between two Fiber Channel components of FCoE interfaces that are
connected in the network. In the VNE model, the endpoints of the link are Fiber Channel IMOs
(IFiberChannel), which represent the underlying native (FC) or virtual (FCoE) Fiber Channel ports.
Note: Fiber Channel interfaces can be connected in a point-to-point, arbitrated loop, or
switched fabric topology. Prime Network supports link discovery only for the switched
fabric, discovering links on extension and node ports.
fabric, discovering links on extension and node ports.
Link type: Fiber Channel
Discovery and verification techniques:
6.1.19 Entity Association
The Entity Association topology represents a link between two related entities located in two different
VNEs, representing physical or virtual devices. In the VNE model, the end points of the link can be any
component/IMO. In Prime Network 4.2.2, it is used to connect the physical and virtual entities as listed
below:
VNEs, representing physical or virtual devices. In the VNE model, the end points of the link can be any
component/IMO. In Prime Network 4.2.2, it is used to connect the physical and virtual entities as listed
below:
Physical server (IServer IMO) & Virtual Device running on this server (IManagedElement
IMO). Virtual devices include CSR1000v, Nexus1000v, VSG, etc.
IMO). Virtual devices include CSR1000v, Nexus1000v, VSG, etc.
Physical server (IServer IMO) & Host (IHost under virtualization inventory)
Virtual Machine (IVirtualMachine IMO) & Virtual Device (IManagedElement IMO)
VEM (Virtual Ethernet Module – modelled as IModule in Nexus1000v) & Host (Hypervsior
under virtualization inventory) and Physical server (IServer IMO)
under virtualization inventory) and Physical server (IServer IMO)
Note: In the above list, only item #1 & #4 will be shown as external links in the topology or
device map view. Item #2 & #3 are just hyperlinks between components across VNEs and
will not be visible in the topology view.
will not be visible in the topology view.
Link type: Entity Association
Discovery and verification techniques:
Entity Association Information