Cisco Prime Nerk 43 User Guide

							 
28-3
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing Virtual Port Channel (vPC) Configurations
Step 2In the Inventory window, choose Logical Inventory>VPC Domain. The vPC domain details are 
displayed in the content pane as shown in Figure 28-2.
Figure 28-2 vPC Domain in Logical Inventory
Table 28-1 describes the vPC domain details. 
						

							 
28-4
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing Virtual Port Channel (vPC) Configurations
Table 28-1 vPC Domain Properties
Field Name Description
Domain  ID Unique ID that is used to identify the vPC peer links and ports connected 
to the vPC downstream devices. 
Peer Status Status of the peer link.
Keep Alive Status Status of the keep alive link, which could be Alive or Down.
Consistency Status Consistency status of the vPC, which could be Success or Failed.
vPC Role Role of the vPC, which could be Primary or Secondary.
Peer Gateway Enabled Status of the peer gateway, which could be Enabled or Disabled.
Graceful Consistency 
Check EnabledIndicates whether graceful consistency check is enabled or disabled. 
This consistency check helps in preventing traffic drops.
Auto Recovery Enabled Indicates whether auto recovery is enabled or disabled.
vPC Domain Mac 
AddressMAC address of the vPC domain.
FabricPath Switch ID ID of the FabricPath switch connected to the vPC.
vPC Peer Link
vPC ID Unique ID for vPC peer link.
Status Status of the port channel used for communication, which could be Up 
or Down. 
Port  Channel vPC used as the port channel for communication. Click the hyperlink, to 
view the relevant Ethernet link aggregation node in the physical 
inventory.
vPC Keep Alive
Destination Destination IP address of the peer switch.
Status Status of the keep alive link, which could be Alive or Down.
Interval Interval time required to check whether the peer switch is active or 
inactive.
Timeout Time taken by the peer switch to respond. 
Hold Timeout Amount of time during which the peer switch information is stored.
Port Interface used for the communication.
VPC Port Channel
vPC ID Unique virtual Port Channel ID.
Port Channel Ethernet link used as the port channel for communication. Click the 
hyperlink, to view the relevant Ethernet link aggregation node in the 
physical inventory.
Port Status Status of the vPC, which could be Up or Down.
Consistency Status Consistency status of the vPC, which could be Success or Failed.
Consistency Reason Reason for the consistency status. 
						

							 
28-5
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing Cisco FabricPath Configurations
The following VPC commands can be launched from the inventory by right-clicking VPC Domain and 
choosing Commands > Show. Your permissions determine whether you can run these commands (see 
Permissions for Vision Client NE-Related Operations, page B-4). To find out if a device supports these 
commands, see the Cisco Prime Network 4.3.2 Supported Cisco VNEs. 
Viewing Cisco FabricPath Configurations
Cisco FabricPath is an innovation in Cisco NX-OS software that brings the stability and scalability of 
routing to Layer 2. It provides a foundation to build a scalable fabric—a network that itself looks like a 
single virtual switch from the perspective of its users. The switched domain does not have to be 
segmented anymore, providing data center–wide workload mobility. Because traffic is no longer 
forwarded along a spanning tree, the bisectional bandwidth of the network is not limited, and massive 
scalability is possible. 
Cisco FabricPath introduces an entirely new Layer 2 data plane by encapsulating the frames entering the 
fabric with a header that consists of routable source and destination addresses. These addresses are the 
address of the switch on which the frame was received and the address of the destination switch to which 
the frame is heading. From there, the frame is routed until it is reaches the remote switch, where it is 
de-encapsulated and delivered in its original Ethernet format.
Cisco FabricPath provides the following features:
Allows Layer 2 multipathing in the FabricPath network. 
Provides built-in loop prevention and mitigation with no need to use the Spanning Tree Protocol 
(STP). 
Provides a single control plane for unknown unicast, broadcast, and multicast traffic. 
Enhances mobility and virtualization in the FabricPath network. 
The system randomly assigns a unique switch ID to each device that is enabled with FabricPath. After 
you enable FabricPath on the devices, you can configure an Ethernet interface or a port channel interface 
as a FabricPath interface. If one member of the port channel is in FabricPath mode, then all the other 
members will also be in FabricPath mode. After you configure the interface as a FabricPath interface, it 
automatically becomes a trunk port, capable of carrying traffic for multiple Virtual Local Area Networks 
(VLANs). 
Prime Network supports Cisco FabricPath on Cisco Nexus 5000 series and Cisco Nexus 7000 series 
network elements. Figure 28-3 shows a Cisco FabricPath architecture. Command Navigation Description
Show Port Channel 
CapacityRight-click on the VPC node> 
Commands> ShowUse this command to view and confirm 
the port channel capacity details.
Show vPCUse this command to view the vPCs 
available for the selected domain.
Show vPC Consistency 
ParametersUse this command to view the vPC 
consistency parameters. 
						

							 
28-6
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing Cisco FabricPath Configurations
Figure 28-3 Cisco FabricPath Architecture
To view the FabricPath configuration in Prime Network Vision:
Step 1Right-click on the required device and choose the Inventory option. 
Step 2In the Inventory window, choose Logical Inventory> FabricPath. The FabricPath configuration 
details are displayed in the content pane as shown in Figure 28-4. You can also view the properties, by 
right-clicking the FabricPath node and choosing Properties.
279717
FP networkS3
B
CE
S1S2
A
CE
FP networkS3
B
CE
S1S2
A
CE
S4
vPCvPC+ 
						

							 
28-7
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing Cisco FabricPath Configurations
Figure 28-4 Cisco FabricPath Node in Logical Inventory
Table 28-2 describes the FabricPath configuration details.
Table 28-2 Cisco FabricPath Configuration
Field Name Description
Switch ID Unique ID of the Cisco FabricPath virtual switch.
System-ID System MAC address of the Cisco FabricPath.
Gracefulmerge 
DisabledIndicates whether graceful merge feature is enabled are not. Value could 
be Tr u e or False. If this feature is enabled, the switch would be 
effectively linked to the Cisco FabricPath network. If disabled, you may 
experience traffic drops.
Allocate Delay (sec) Time delay during new resource propagation.
Linkup Delay (sec) Time delay for detecting conflicts during linkup sessions.
Transition Delay (sec) Time delay during transition of value propagation.
FabricPath Interfaces
Port Ethernet link, which is configured as a Cisco FabricPath. Click the 
hyperlink to view the interface link in physical inventory.
Interface Name Name of the interface for which switch port mode is configured as a 
Cisco FabricPath. 
						

							 
28-8
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing the Virtual Device Context and Port Allocation
The following FabricPath commands can be launched from the inventory by right-clicking FabricPath 
and choosing Commands > Show. Your permissions determine whether you can run these commands 
(see Permissions for Vision Client NE-Related Operations, page B-4). To find out if a device supports 
these commands, see the Cisco Prime Network 4.3.2 Supported Cisco VNEs. 
Viewing the Virtual Device Context and Port Allocation
The Virtual Device Context (VDC) partitions a single physical device into multiple logical devices that 
provide fault isolation, management isolation, address allocation isolation, service differentiation 
domains, and adaptive resource management. You can manage a VDC instance within a physical device 
independently. Each VDC appears as a unique device to the connected users. A VDC runs as a separate 
logical entity within the physical device, maintains its own unique set of running software processes, has 
its own configuration, and can be managed by a separate administrator.
In Prime Network, you can view the VDC context and port allocation details for a Nexus 7000 device. 
Each context will contain a list of allocated ports.
To view the VDC context details:
Step 1Right-click on the Nexus 7000 device and choose the Inventory option.
Step 2In the Inventory window, choose Logical Inventory>Context. 
Step 3In the content pane, click the Allocated Interfaces tab. The VDC context details are displayed in the 
content pane as shown in Figure 28-5. The Interface Name and the related Associated Entity are 
displayed in the content pane.Command Navigation Description
FabricPath ConflictRight-click on the FabricPath 
node> Commands> ShowUse this command to view the 
Cisco FabricPath conflicts.
MAC Address-Table 
Learning ModeUse this command to view the MAC 
address-table learning mode. 
						

							 
28-9
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing the Virtual Device Context and Port Allocation
Figure 28-5 Allocated Interfaces tab
Step 4
Click the link in the Associated Entity field and you will be able to view the related interface node 
details under the Physical Inventory.
Configuring Prompts and Messages for Unconfigured VDC for a Nexus Device
You can configure prompts and messages of unconfigured Virtual Device Context (VDC) for a Cisco 
Nexus device by using runRegTool.
Prime Network reads these prompts at the time of switching to unconfigured VDC to avoid collectors 
from blocking the expected prompt. When the prompts are completely read, Prime network receives the 
interactive mode response from the device, say Cisco Nexus device. Prime Network detects the situation 
by comparing the device response with the configured messages of unconfigured VDC in the Registry. 
After the situation is detected, Prime Network avoids configuring the unconfigured VDC by aborting the 
switchto command. As soon as the current command result is marked as Valid, you can proceed with 
inventory discovery.
If either Unconfigured VDC is configured or Suspended VDC is activated, click Poll Now to view the 
updated inventory details.
NoteEnsure that prompts and messages must be defined with a unique name and full description.
To configure new prompts, run the below command: 
						

							 
28-10
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing Virtualized Resources
runRegTool.sh -gs 127.0.0.1 set 0.0.0.0 
site/ciscovdc-cisco-nexus70xx-product/cisco-catalyst/nexus70xx/product/software 
versions/default 
version/ip_default/protocols/telnet/unconfigured_vdc_context/expected_prompts/  
Example: runRegTool.sh -gs 127.0.0.1 set 0.0.0.0 
site/ciscovdc-cisco-nexus70xx-product/cisco-catalyst/nexus70xx/product/software 
versions/default 
version/ip_default/protocols/telnet/unconfigured_vdc_context/expected_prompts/prom
pt1 [n]:
To configure messages, run the below command:
runRegTool.sh -gs 127.0.0.1 set 0.0.0.0 
site/ciscovdc-cisco-nexus70xx-product/cisco-catalyst/nexus70xx/product/software 
versions/default 
version/ip_default/protocols/telnet/unconfigured_vdc_context/expected_messages/ 
Example: runRegTool.sh -gs 127.0.0.1 set 0.0.0.0 
site/ciscovdc-cisco-nexus70xx-product/cisco-catalyst/nexus70xx/product/software 
versions/default 
version/ip_default/protocols/telnet/unconfigured_vdc_context/expected_messages/mes
sage0  Admin Secure Password.
Viewing Virtualized Resources
Virtualization is a concept of creating a virtual version of any resource, such as hardware platform, 
operating system, storage device, or network resources, as shown in Figure 28-6. It provides a layer of 
abstraction between computing, storage and networking hardware, and the applications running on it. 
Virtual infrastructure gives administrators the advantage of managing pooled resources across the 
enterprise, allowing IT managers to be more responsive to dynamic organizational needs and to better 
leverage infrastructure investments.
The VMware vCenter Server provides centralized management of virtualized hosts and virtual machines 
from a single console. With VMware vCenter Server, virtual environments are easier to manage: a single 
administrator can manage hundreds of workloads, more than doubling typical productivity in managing 
physical infrastructure.
In Prime Network, VCenter is modelled as a VNE. 
NoteVCenter is created as a separate VNE using the Administration client. For more information about 
creating a new VNE, see the Cisco Prime Network 4.3.2 Administrator Guide. You must specify the http 
credentials for VCenter. However the SNMP credentials are optional, and the SSH credentials are not 
required.
Note. 
						

							 
28-11
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing Virtualized Resources
Figure 28-6 Virtualization Concept
The various components of virtualization are:
Hypervisor (Host Server)
A hypervisor, also called a blade server, a virtual machine manager, or a host server, is a program that 
allows multiple operating systems to share a single hardware host. Each operating system appears to 
have the hosts processor, memory, and other resources all to itself. However, the hypervisor is actually 
controlling the host processor and resources, allocating what is needed to each operating system in turn 
and making sure that the guest operating systems (called virtual machines) do not disrupt each other.
Virtual Machine
A virtual representation of a real machine using software that provides an operating environment, which 
can run or host a guest operating system.
Guest Operating System
An operating system running in a virtual machine environment that would otherwise run directly on a 
separate physical system.
Data Store
A data store represents a storage location for virtual machine files. It can be a Virtual Machine File 
System (VMFS) volume, a directory on Network Attached Storage, or a local file system path.
Data Center
Data Center serves as a container for hosts, virtual machines, networks, and data stores. 
Cluster
A cluster is a collection of servers that operate as if it is a single machine. The primary purpose of these 
clusters is to provide uninterrupted access to data, even if a server loses network or storage connectivity, 
or fails completely, or if the application running on the server fails.
Resource Pool
A resource pool is a logical abstraction for flexible management of resources. Resource pools can be 
grouped into hierarchies and used to hierarchically partition available CPU and memory resources.It is 
the foundation of virtual data centers, virtual desktops, high availability and other options on virtual 
servers. Resource pools aggregate CPU processing power and memory, along with any other relevant 
components, then share these hardware resources among virtual machines (VMs). 
						

							 
28-12
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing Virtualized Resources
The following topics explain how to view and monitor virtual data center properties in 
Prime Network Vision:
Viewing Virtual Data Centers, page 28-12
Viewing the Data Stores of a Data Center, page 28-12
Viewing the Host Servers of a Data Center, page 28-13
Viewing all the Virtual Machines managed by vCenter, page 28-17
Viewing the Virtual Machines of a Data Center, page 28-18
Viewing the Host Cluster Details, page 28-21
Viewing the Resource Pool Details, page 28-23
Viewing Virtual Data Centers
To view the virtual data centers in the logical inventory:
Step 1Right-click on the required device and choose the Inventory option. 
Step 2In the Inventory window, choose Logical Inventory> Compute Virtualization. The virtual data centers 
are listed in the content pane.
Table 28-3 describes the virtual data center properties.
Step 3Right-click the data center and choose Properties to view more details.
Viewing the Data Stores of a Data Center
To view the details of data stores available for a data center:
Step 1Right-click on the required device and choose the Inventory option. 
Step 2In the Inventory window, choose Logical Inventory>Compute Virtualization >Data Center >All 
Data Stores. The available data stores are displayed in the content pane. You can view the data store 
properties from the table or by right-clicking the required data store and choosing Properties.
Table 28-4 describes the data store properties.
Table 28-3 Virtual Data Center Properties
Field Name Description
Name Name of the data center.
IP Address IP address of the vCenter, which manages the virtual data center.
DNS name The DNS name of the data center.