Cisco Prime Nerk 43 User Guide

							 
28-23
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing Virtualized Resources
Viewing the Resource Pool Details
To view the resource pool details:
Step 1In the Vision client, right-click on the required device and select the Inventory option.
Step 2In the Inventory menu, expand the Logical Inventory node.
Step 3Select Compute Virtualization> Data Center> Host Clusters> Host cluster. The host cluster details 
are displayed in the content pane.
NoteAlternatively, you can also view the host cluster details by selecting Compute Virtualization> Data 
Center> All Host> Host.
Step 4In the Compute Resource Pools tab in the content pane, click on a resource pool link in the Resource 
Pool field. The Compute Resource Pool Properties window is displayed.In 
Table 28-10 describes the resource pool details. Share The relative importance of the virtual machine for memory allocation, 
which could be High, Normal, or Low.
Custom Share Weight The custom share weight assigned to the virtual machine.
Statistics tab
CPU Usage CPU usage by the virtual machine, in GHz.
Memory Usage Memory usage by the virtual machine, in GB.
Disk Usage Amount of disk space used by the virtual machine, in GB.
Active Guest Memory 
UsageActive guest memory used by the virtual machine, in GB.
Clustered Hosts 
Host Name The name of the host server in the clustered host.
Associated Host The link to the associated host, which when clicked will take you to the 
relevant host server.
Compute Resource Pool
Provider Name The compute resource pool name.
Description The description of the compute resource pool.
Status The status of the compute resource pool.
Root Pool Indicates whether the compute resource pool is the root pool.
Table 28-8 Host Cluster Details (continued)
Field Name Description 
						

							 
28-24
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing Virtualized Resources
Table 28-9 Resource Pool Properties
Field Name Description
Name The compute resource pool name.
Provider Name The description of the compute resource pool.
Status The status of the compute resource pool.
Root Pool Indicates whether the compute resource pool is the root pool.
CPU Allocation tab
Resource Type The type of resource, which in this instance is CPU.
Allocatable The maximum CPU allocation for the virtual machine, in GHz.
Reserved The CPU allocation reserved for the virtual machine, in GHz.
Unreserved The unreserved CPU allocation for the virtual machine, in GB.
Unlimited Provision Indicates whether unlimited CPU allocation provision is available for 
the virtual machine.
Share The relative importance of the virtual machine for CPU allocation, 
which could be High, Normal, or Low.
Configured Reservation The CPU reservation configured for the virtual machine.
Available Reservation The CPU reservation available for the virtual machine.
Overhead The overhead CPU allocation for the virtual machine, in GHz.
Custom Share Weight The custom share weight assigned to the virtual machine.
Memory Allocation tab
Resource Type The type of resource.
Allocatable The maximum memory allocation for the virtual machine, in GHz.
Reserved The memory allocation reserved for the virtual machine, in GHz.
Unallocated The memory not allocated for the virtual machine.
Overhead The overhead memory allocation for the host center, in GHz.
Unlimited Provision Indicates whether unlimited memory allocation provision is available 
for the virtual machine.
Unreserved The unreserved memory allocation for the virtual machine, in GB.
Share The CPU reservation configured for the virtual machine.
Custom Share Weight The CPU reservation available for the virtual machine.
Configured Reservation The memory reservation configured for the virtual machine.
Available Reservation The memory reservation available for the virtual machine. 
						

							 
28-25
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing the Map Node for an UCS Network Element
Viewing the Map Node for an UCS Network Element
Using the Vision client, you can view the physical layout and topology among the multi-chassis devices 
on the map. The multi-chassis devices have more than one physical chassis, but they are represented as 
a single entity in Prime Network. In a map, this device is shown as an aggregation of all the device 
chassis. For more information on viewing multi-chassis devices, see Viewing Multi-Chassis Devices, 
page 8-5.
For a Cisco Unified Computing Service (UCS) device, you can view its chassis along with the other 
elements relevant to the UCS device, such as Blade Server and IO Modules. 
Another important component of the UCS is the Fabric InterConnect. The Fabric InterConnect is a core 
part of the UCS device. It provides both network connectivity and management capabilities to all 
attached blades and chassis. All chassis, and therefore all blades, attached to the interconnects become 
part of a single, highly available management domain.
To view the physical inventory of a UCS:
Step 1Right-click on the UCS device and choose the Inventory option. 
Step 2In the Inventory window, expand the Physical Inventory node. The Chassis and Fabric Interconnect 
chassis are displayed below the node as shown in Figure 28-9.
Figure 28-9 Physical Inventory Node for a UCS Device
Step 3
Expand the Chassis node. The Blade servers, Fans, and the IO Modules that make up the Chassis are 
displayed under this node.
Step 4Expand the Fabric InterConnect node.The slots and the power supply are available here. You can click 
on each individual node under these nodes to view more details.  
						

							 
28-26
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing the Map Node for an UCS Network Element
Step 5Close the inventory window.
Each of these parts, i.e. the blade servers, Fabric InterConnect chassis, and IO Modules, can be 
connected to each other internally. For example, an IO Module can be connected to a blade server or 
there could also be a link between the IO Module and Fabric InterConnect chassis. 
The Ethernet links between the different components of a UCS can be categorized as:
Backplane links—The links that connect a chassis to a backplane port via the IO Module.
Fabric links—The links that connect a chassis to a Fabric InterConnect port via the IO Module.
You can also view this link in a map that contains a separate map node for each of the following elements:
Fabric Interconnect Chassis
Blade Server Chassis
Cisco Blade Server
IO Module
The blade server chassis is shown as an aggregation that also contains the IO Module.
To view the map for a UCS device:
Step 1In the Vision client, open a map with a UCS device. The UCS device is displayed with a plus (+) sign. 
Click on the + sign. The map containing the links between each element in the UCS device is shown in 
the window as shown in Figure 28-10.
Figure 28-10 UCS Map Node with Aggregation Links 
						

							 
28-27
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing the Map Node for an UCS Network Element
NoteSub-nodes are available for the chassis that have blade servers under them. You can expand/contract 
these sub-nodes to view more details. However, the elements under the Fabric InterConnect chassis will 
not be displayed in the map.You can also view the inventory for an element by double-clicking on a node 
in the map. The inventory window will open with the selected node.
Step 2Hover your mouse cursor over the required link in a map. A link tooltip is displayed. The tooltip displays 
the link endpoints identified by the element or service name and the number of links represented by the 
line on the map.
Step 3To view additional link information, click the tooltip. The link quick view window is displayed. 
Alternatively, you can also double-click the link to view the link quick view window.
NoteYou can view links belonging to a specific type by clicking the Filter icon in the navigation pane and 
selecting the relevant check box. Open the link again and only the selected type of link is displayed. For 
more information about filtering a map, see Using Link Filters to Find Links, page 7-21.
Step 4Close the window.
Step 5In the map, double-click an element icon to open the Physical inventory and view the ports under it. For 
example, if you double-click on an IO Module element, the Inventory window is displayed along with 
the Backplane and Fabric ports under the IO Module node.
Step 6In the map, double click on a link to view it’s properties such as the link type, port alias, and port 
location. For more information on link properties, see Viewing Link Status and Detailed Link Properties, 
page 7-25.
NoteThe links between the UCS components can also be viewed in the Cisco Unified Computing System 
Manager application.
Discovering the UCS Devices by Network Discovery
The Network Discovery feature automatically discovers network devices by traversing the network. The 
required information is an IP address for a seed device, and the SNMPv 2 or SNMPv 3 credentials. This 
information is added to a discovery profile that specifies the IP and SNMP information, along with any 
additional protocols or filters you want Prime Network to use. 
You can also discover the UCS devices by Network Discovery. To manage a UCS device, the CLI and 
http credentials are required. However, the existing network discovery does not support http.
Since the CLI and http credentials are identical most of the times, the CLI credentials will be copied into 
http. You need to create a new discovery profile (using telnet or SSH credentials) for the UCS device and 
execute it. For more information about adding devices using Network Discovery, see the Cisco Prime 
Network 4.3.2 Administrator Guide. 
						

							 
28-28
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing the Virtual Network Devices of a Data Center
Viewing the Virtual Network Devices of a Data Center
Prime Network supports the following virtual network devices of a data center:
Cisco Cloud Service Router (CSR) 1000v
Cisco Nexus 1000V
Virtual Security Gateway
Viewing the CSR 1000v Properties
The Cisco Cloud Services Router (CSR) 1000V is a single-tenant router in virtual form-factor that 
delivers comprehensive WAN gateway functionality to multi-tenant provider-hosted clouds. It is a 
software router that an enterprise or a cloud provider can deploy as a virtual machine (VM) in a 
provider-hosted cloud.The Cisco CSR 1000V provides selected Cisco IOS XE features on a 
virtualization platform. It also provides secure connectivity from the enterprise premise (such as a 
branch office or data center) to the public or private cloud. Figure 28-11 depicts the deployment of CSR 
1000v on a provider hosted cloud:
Figure 28-11 Deployment of CSR 1000v on a Provider Hosted Cloud
The Cisco CSR 1000V serves primarily as a router per tenant. In other words, since the CSR 1000v is 
situated on the tenant’s side, each tenant gets its dedicated routing instance and services (along with its 
own VPN connections, firewall policies, QoS rules, access control, and so on).
To view the CSR 1000v properties:
Step 1In the Vision client, open a map that contains the CSR 1000v device.
Step 2Right-click and choose the Inventory option to open the Inventory window.
Step 3In the Inventory window, click the device name to view the Element properties as shown in 
Figure 28-12. For more information about the properties window, see Drilling Down into the Properties 
of a Network Element, page 8-2. 
						

							 
28-29
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing the Nexus 1000V Properties
Figure 28-12 Element Properties Window
NoteThe CSR 1000v device is associated with a hypervisor and physically available on a blade server. 
The links to the hypervisor and blade server are displayed in the Properties window.
Step 4Under the Logical Inventory node, you can view the Access Lists, Cisco Discovery Protocol, Operating 
System requirements, and Routing Entities. For more information about the logical inventory properties, 
see Viewing the Logical Properties of a Device (Traffic, Routing, Information, Tunnels, Data Link 
Aggregations, Processes), page 8-21.
Step 5Under the Physical Inventory node, you can view the two slots under the Chassis node. 
NoteThe first slot contains the Route Processor with three interface ports—one for management and the other 
two for data traffic. The second slot contains the Embedded Services Processor.
Viewing the Nexus 1000V Properties
The Cisco Nexus 1000V device is a a distributed virtual switch solution that is fully integrated within 
VMware Virtual Infrastructure, including VMware vCenter for the virtualization administrator. This 
solution off loads the configuration of the virtual switch and port groups to the network administrator to 
enforce a consistent datacenter network policy. It manages a data center defined by a VirtualCenter. Each 
server in the data center is represented as a module and can be managed as if it were a module in a 
physical Cisco switch. 
The Cisco Nexus 1000V has the following components that can virtually emulate a 66-slot modular 
Ethernet switch with redundant supervisor functions: 
						

							 
28-30
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing the Nexus 1000V Properties
Virtual Ethernet module (VEM)—The Virtual Ethernet Module (VEM) is one part of the Cisco 
Nexus 1000V device that actually switches data traffic. Several VEMs are controlled by one VSM. 
All the VEMs that form a switch domain should be in the same virtual Data Center as defined by 
VMware VirtualCenter.
Virtual supervisor module (VSM)—The VSM is a standalone, external, physical or virtual appliance 
that performs the following functions for the Cisco Nexus 1000V system (that is, the combination 
of the VSM itself and all VEMs it controls):
–Configuration.
–Management
–Monitoring.
–Diagnostics.
–Integration with VMware vCenter
In the Cisco Nexus 1000V, traffic is switched between virtual machines locally at each VEM instance. 
Each VEM also interconnects the local virtual machine with the rest of the network through the upstream 
access-layer network switch (blade, top-of-rack, end-of-row, and so forth). The VSM runs the control 
plane protocols and configures the state of each VEM accordingly, but it never forwards packets. 
In Prime Network, you can view the connectivity between the Nexus 1000V device and the host and 
blade server as shown in Figure 28-13. 
Figure 28-13 Connectivity between Nexus 1000V and host/blade server
In other words, you can view the hosts under vCenter to which the device provides switching support 
and the underlying blade servers that are connected to the device. 
To view the connectivity:
Step 1Right-click on the vCenter device and choose the Inventory option. 
						

							 
28-31
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing the Nexus 1000V Properties
Step 2In the Inventory window, choose Logical Inventory > Compute Virtualization>Virtual Data 
Center>Host Servers>Host Server. 
Step 3In the content pane, click the link in the Associated VEM Module field. You can view the details of the 
UCS blade server of the Nexus 1000v device to which the vCenter is connected to.
Viewing the VSG Properties
The Cisco Virtual Security Gateway (VSG) is a virtual firewall appliance that provides trusted access to 
virtual data center and cloud environments. The Cisco VSG enables a broad set of multi tenant 
workloads that have varied security profiles to share a common compute infrastructure in a virtual data 
center private cloud or in a public cloud. By associating one or more virtual machines (VMs) into distinct 
trust zones, the Cisco VSG ensures that access to trust zones is controlled and monitored through 
established security policies. 
Figure 28-14 depicts the deployment of VSG:
Figure 28-14 Deployment of VSG
The Cisco VSG operates with the Cisco Nexus 1000V in the VMware vSphere hypervisor, and the Cisco 
VSG leverages the virtual network service datapath (vPath) that is embedded in the Nexus 1000V Virtual 
Ethernet Module (VEM). A VEM can be associated to a Cisco VSG.
To view the VSG Properties:
Step 1In the Vision client, open a map that contains the VSG device. 
						

							 
28-32
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing the Compute Server Support Details
Step 2Right-click and choose the Inventory option to open the Inventory window.
Step 3In the Inventory window, click the device name to view the Element properties. For more information 
about the properties window, see Drilling Down into the Properties of a Network Element, page 8-2
NoteThe VSG device is associated with a hypervisor and physically available on a blade server. The 
links to the hypervisor and blade server are displayed in the Properties window.
Step 4Under the Logical Inventory node, you can view the Access Lists, Cisco Discovery Protocol, Operating 
System requirements, and Routing Entities. For more information about the logical inventory properties, 
see Viewing the Logical Properties of a Device (Traffic, Routing, Information, Tunnels, Data Link 
Aggregations, Processes), page 8-21.
Step 5Under the Physical Inventory node, you can view only one slot.
Viewing the Compute Server Support Details
Prime Network provides support for the following compute servers:
UCS B-Series Servers—The Cisco UCS B-Series Blade Servers are crucial building blocks of the 
Cisco Unified Computing System and are designed to increase performance, energy efficiency, and 
flexibility for demanding virtualized and non virtualized applications. Each Cisco UCS B-Series 
Blade Server uses converged network adapters (CNAs) for access to the unified fabric. This design 
reduces the number of adapters, cables, and access-layer switches while still allowing traditional 
LAN and SAN connectivity.
UCS C-Series Servers—Cisco UCS C-Series Rack Servers deliver unified computing in an 
industry-standard form factor to reduce total cost of ownership and increase agility
Third party or Non-Cisco servers—Includes support for non-UCS servers such as HP, Dell or IBM. 
In Prime Network, the UCS B-Series and UCS C-Series servers are modelled as part of the UCS VNE. 
The UCS C-Series (standalone) and non-Cisco servers are modelled as individual VNEs.
NoteFor a Cisco UCS device, you can also view the physical inventory, which includes the blade server, 
Fabric InterConnect and IO Modules. You can also view the physical layout and topology for the UCS 
device on the map. For more information, see Viewing the Map Node for an UCS Network Element, 
page 28-25.
NoteThere is also a direct correlation between the blade server and its associated virtual entities. For instance, 
if the blade server is shut down, then the associated entities such as the virtual machines and hypervisor 
will also be shut down. 
To view the UCS server details:
Step 1In the Vision client, right-click a UCS device and choose the Inventory option.
Step 2In the Inventory window, expand the Physical Inventory node.