Cisco Prime Nerk 43 User Guide

							  
27-227
Cisco Prime Network 4.3.2 User Guide
EDCS-1524415
Chapter 27      Managing Mobile Networks
  Monitoring the Mobility Management Entity
Table 27-142 Policy Configuration Details
Field Description
IMEI Query type The type of IMEI query use for attaching the user equipment and tracking 
area update procedure, which can be any one of the following:
imei (International Mobile Equipment Identity)
imei-sv (International Mobile Equipment Identity-Software Version)
Set UE Time Indicates whether the MME service must set the time in the UE during the 
attach or tracking area update procedure.
Deny Grey Listed Indicates whether the MME service must deny the grey listed equipment. In 
other words, it specifies whether the identification of the UE must be 
performed by the Equipment Identity Register (EIR) over the S13 interface.
Deny Unknown Indicates whether the MME service must deny service to an unknown 
equipment.
Verify Emergency Indicates whether the MME service must verify the equipment for 
emergency calls.
Allow On ECA Timeout Indicates whether the MME service must allow service of equipments that 
timeout on the ECA.
Initial Context Setup 
Failure TauIndicates policy, which applies to Tracking Area Update procedure when 
initial context setup failure is received.
Initial Context Setup 
Failure Service RequestIndicates policy that applies to a service request procedure.
Policy 
NAS-NON-DELIVERY Shows that handling for NAS-NON-DELIVERY message is Enabled.
Policy 
NAS-NOS-DELIVERY 
Modify Procedure 
TimerShows the timer value in seconds for the modify procedure.
MSC Echo Parameters Displays EGTPC echo parameters for MSC Fallback. The msc-echo-params 
configuration overrides any echo parameter that is configured in the 
egtp-service configuration for the corresponding SV service.
IPNE Service Associates an IPNE service with a MME service.
CSG Change 
NotificationEnables or disables the Closed Subscriber Group (CSG) Information 
reporting (notification) mechanism on the MME. When enabled, the MME 
includes the CSG Information Reporting Action IE with the appropriate 
Action field for subscribers.
ISR Capability Enables or disables the Idle-mode Signaling Reduction (ISR) feature on the 
MME service.
Location Service Associates a location service with a specified MME service. Only one 
location service should be associated with an MME Service.
Trap S1 Path 
EstablishmentSpecifies that the SNMP trap for the S1 path establishment is to be enabled 
or disabled.
EIR Query Type Indicates whether querying of EIR is enabled or disabled. 
						

							  
27-228
Cisco Prime Network 4.3.2 User Guide
EDCS-1524415
Chapter 27      Managing Mobile Networks
  Monitoring the Mobility Management Entity
MME Policy Configuration Commands
The following MME policy configuration commands can be launched from the logical inventory by 
right-clicking a MME policy and choosing Commands > Configuration. Your permissions determine 
whether you can run these commands (see Permissions Required to Perform Tasks Using the 
Prime Network Clients). To find out if a device supports these commands, see the Cisco Prime Network 
4.3.2 Supported Cisco VNEs. 
Viewing the S1 Interface Configuration Details
To view the S1 Interface configuration details for a MME service:
Step 1Right-click the required device in the Vision client and choose Inventory.
Step 2In the Logical Inventory window, choose Logical Inventory> Context> Mobile> MME> MME 
service> S1 Interface. The interface configuration details are displayed in the content pane.
Table 27-144 displays the S1 Interface configuration details.
Table 27-143 MME Policy Configuration Commands
Command Navigation Description
Modify Policy Logical Inventory > Context > 
Mobile > MME > MME service 
> Right-click the Policy> 
Commands> ConfigurationUse this command to modify the MME 
policy.
Modify Attach Logical Inventory > Context > 
Mobile > MME > MME service 
> Policy> Right-click the Attach 
> Commands> ConfigurationUse this command to modify the MME 
Attach details.
Modify TAU Logical Inventory > Context > 
Mobile > MME > MME service 
> Policy> Right-click the TAU > 
Commands> ConfigurationUse this command to modify the MME 
TAU details. 
						

							  
27-229
Cisco Prime Network 4.3.2 User Guide
EDCS-1524415
Chapter 27      Managing Mobile Networks
  Monitoring the Mobility Management Entity
Table 27-144 S1 Interface Configuration Details
Field Description
Primary IP Address The IP address (IPv4 or IPv6) of the interface configured as an S1-MME 
interface.
Secondary IP Address The optional IP address (IPv4 or IPv6) of the interface configured as an 
S1-MME interface.
SCTP Port The source SCTP port used for binding the SCTP socket to communicate 
with the eNodeB. This port can be any value between 1 and 65535, and 
defaults to 699.
Max Subscribers The maximum number of subscribers that can access the MME service on 
the interface. This number can be any value between 0 and 4,000,000.
QoS DSCP The Quality of Service (QoS) Differentiated Service Code Point (DSCP) 
used when sending data packets (of a particular 3GPP QoS class) over the 
S1-MME interface. This can be any one of the following values:
af11
af12
af13
af21
af22
af23
af31
af32
af33
af41
af42
af43
be
ef
Crypto  Template The name of the crypto template that is used when implementing IP Security 
on the S1-MME interface. 
S1 Interface Connected 
TrapIndicates whether the SNMP trap for the S1 interface connection equipment 
is enabled. 
						

							  
27-230
Cisco Prime Network 4.3.2 User Guide
EDCS-1524415
Chapter 27      Managing Mobile Networks
  Viewing the Stream Control Transmission Protocol
S1 MME Interface Commands
The following S1 MME interface commands can be launched from the logical inventory by 
right-clicking an S1 MME interface and choosing Commands > Configuration. Your permissions 
determine whether you can run these commands (see Permissions Required to Perform Tasks Using the 
Prime Network Clients). To find out if a device supports these commands, see the Cisco Prime Network 
4.3.2 Supported Cisco VNEs. 
Viewing the Stream Control Transmission Protocol
The Stream Control Transmission Protocol (SCTP) is a message oriented, reliable transport protocol 
with direct support for multi-homing that runs on top of Internet Protocol (IPv4/IPv6). Like TCP, SCTP 
provides reliable, connection-oriented data delivery with congestion control, path MTU discovery and 
message fragmentation.
Its role is similar to the roles of popular protocols such as Transmission Control Protocol (TCP) and User 
Datagram Protocol (UDP). It provides some of the same service features of both: it is message-oriented 
like UDP and ensures reliable, in-sequence transport of messages with congestion control like TCP.
SCTP offers the following services to the users:
Acknowledged error-free non-duplicated transfer of user data
Data fragmentation to conform to discovered path MTU size
Sequenced delivery of user messages within multiple streams, with an option for order-of-arrival 
delivery of individual user messages
Optional bundling of multiple user messages into a single SCTP packet
Network-level fault tolerance through supporting of multi-homing at either or both ends of an 
association
The SCTP application submits data to be transmitted in messages to the SCTP transport layer. The 
messages and control information is separated and placed in chunks (data and control chunks), each 
identified by a chunk header. A message can be fragmented over a number of data chunks, but each data 
chunk contains data from only one user message. SCTP bundles the chunks into SCTP packets, which 
are then submitted to the Internet Protocol. The SCTP packet consists of a packet header, SCTP control 
chuck (if required) and SCTP data chunks (if available). 
The primary distinguishing features of this new protocol are:
multi-homing—The ability of an association to support multiple IP addresses or interfaces at a given 
endpoint. Currently, SCTP does not do load-sharing, but with the multi-homing facility, SCTP has 
greater potential to survive a session in case of network failures. Using more than one address allows 
re-routing of packets in event of failure and also provides an alternate path for retransmissions. 
Endpoints can exchange lists of addresses during initiation of the association. One address is 
Table 27-145 S1 MME Interface Commands
Command Navigation Description
Modify S1 MME Logical Inventory > Context > 
Mobile > MME > MME service 
> Right-click the S1 Interface> 
Commands> ConfigurationUse this command to modify a S1 MME 
interface. 
						

							  
27-231
Cisco Prime Network 4.3.2 User Guide
EDCS-1524415
Chapter 27      Managing Mobile Networks
  Viewing the Stream Control Transmission Protocol
designated as the primary address to receive data. A single port number is used across the entire 
address list at an endpoint for a specific session. Heartbeat chunks are used to monitor availability 
of alternate paths with thresholds set to determine failure of alternate and primary paths.
NoteAn “association here refers to the connection between two endpoints in this context.
multi-streaming—Each stream represents a sequence of messages within a single association. These 
messages may be long or short, which include flags for control of segmentation and reassembly. 
Stream Identifiers and Stream Sequence numbers are included in the data packet to allow sequencing 
of messages on a per-stream basis. This ensures that unnecessary head-of-line blocking between 
independent streams of messages is avoided in case of loss in one stream. 
SCTP also provides a mechanism for designating order-of-arrival delivery as opposed to ordered 
delivery. The design of SCTP includes appropriate congestion avoidance behavior and resistance to 
flooding and masquerade attacks.
For devices such as the Cisco ASR 5000 series, SCTP carries signaling traffic that flows through IPSec 
tunnel over LTE S1-MME interface.
To view the SCTP configuration details:
Step 1Right-click the required device in the Vision client and choose Inventory.
Step 2In the Logical Inventory window, choose Logical Inventory >Context>Profile>SCTP Template. A 
list of SCTP templates is displayed in the content pane.
Step 3In the Logical Inventory window, select a template from the SCTP Template node. The SCTP template 
details are displayed in the content pane as shown in Figure 27-24.
Figure 27-24 SCTP Template Details 
						

							  
27-232
Cisco Prime Network 4.3.2 User Guide
EDCS-1524415
Chapter 27      Managing Mobile Networks
  Viewing the Stream Control Transmission Protocol
Table 27-146 describes the SCTP Template details.
Table 27-146 SCTP Template Details
Field Description
Template Name The unique name of the SCTP template.
NoteEach template can be configured with different values and 
associated to different services such as the MME service, diameter 
endpoint and so on.
RTO Alpha The Retransmission Timeout (RTO) alpha (smoothing factor) value that is 
used to calculate Smooth Round Trip Time (SRTT) and the Round Trip Time 
Variation (RTTVAR) for new Round Trip Time (RTT) measurements.
NoteRTO refers to the amount of time to wait before transmitting a 
package from the retransmission queue to the neighbor. SRTT refers 
to the amount of time (in milliseconds) it takes for a packet to be sent 
to the neighbor and for the local router to receive an 
acknowledgment for the packet.
RTO  Beta The Retransmission Timeout (RTO) beta (delay variance factor) value that is 
used to calculate Smooth Round Trip Time (SRTT) and the Round Trip Time 
Variation (RTTVAR) for new Round Trip Time (RTT) measurements.
Checksum The type of checksum that is used to increase data integrity of the SCTP 
packets, which can be any one of the following:
adler32—the Adler-32 checksum algorithm is used
crc32—the 32 bit cyclic redundancy check algorithm is used.
Cookie Lifetime The lifetime (in milliseconds) of the SCTP cookie.
Max Association 
RetransmissionThe maximum number of retransmissions allowed by this template for the 
SCTP associations.
Max Incoming Streams The maximum number of incoming SCTP streams.
Max Init 
RetransmissionsThe maximum number of SCTP initiation retransmissions.
Max  MTU  Size The maximum size (in bytes) of the Maximum Transmission Unit (MTU) for 
SCTP streams.
Min MTU Size The minimum size (in bytes) of the MTU for SCTP streams.
Start Max MTU The starting size (in bytes) of the MTU for SCTP streams.
Max Outgoing Streams The maximum number of outgoing SCTP streams.
Max Retransmissions 
PathThe maximum number of retransmissions of the SCTP paths.
RTO Initial The initial time (in milliseconds) for retransmission of SCTP packets.
RTO Max The maximum time (in milliseconds) for retransmission of SCTP packets.
RTO Min The minimum time (in milliseconds) for transmission of SCTP packets. 
						

							  
27-233
Cisco Prime Network 4.3.2 User Guide
EDCS-1524415
Chapter 27      Managing Mobile Networks
  Viewing the Stream Control Transmission Protocol
SACK Frequency The frequency of the Selective Acknowledgment (SACK) of the SCTP 
packets.
SACK Period The period (in milliseconds) of selective acknowledgment of the SCTP 
packets.
Heart Beat Status Indicates whether the option to send traffic over an alternate path, in case of 
a path failure, is enabled.
NoteThe Heartbeat message is sent to a peer endpoint to probe the 
reachability of a particular destination transport address defined in 
the present association. If the address is not reachable, the traffic is 
sent over an alternate address. If this option is enabled, then the 
failover recovery is not even known to the user.
Heart Beat Timer The amount of time (in seconds) to wait before a peer is considered 
unreachable. When a Heartbeat request is sent and if an acknowledgment is 
not received before this timer, then subsequent heartbeat requests are not 
sent and the peer is considered unreachable.
Bundle Status Indicates whether the data chunks must be bundled into packets before 
submitting to the IP. If this option is disabled, then the packets are sent 
without bundling.
Bundle  Timeout The amount of time (in seconds) after which the chunks of SCTP packets are 
bundled and committed for transmission. 
Alternate Accept Flag Indicates whether the alternate accept flag that denotes additional lifetime 
for the association, is enabled.
Table 27-146 SCTP Template Details (continued)
Field Description 
						

							  
27-234
Cisco Prime Network 4.3.2 User Guide
EDCS-1524415
Chapter 27      Managing Mobile Networks
  Viewing the Stream Control Transmission Protocol 
						

							CH A P T E R
 
28-1
Cisco Prime Network 4.3.2 User Guide
28
Managing Data Center Networks
Data Center is a centralized repository, either physical or virtual for the storage, management, 
dissemination of data and information organized around a particular manner. In other words, it is a 
facility used to house computer systems and associated components, such as telecommunications and 
storage systems. It generally includes redundant or backup power supplies, redundant data 
communication connections, environmental controls such as air conditioning or fire suppression, and 
security devices. 
Prime Network supports the following technologies as part of data center. If you cannot perform an 
operation that is described in these topics, you may not have sufficient permissions; see Permissions for 
Managing Data Center Networks, page B-26.
Viewing Virtual Port Channel (vPC) Configurations, page 28-1
Viewing Cisco FabricPath Configurations, page 28-5
Viewing Virtualized Resources, page 28-10
Viewing the Storage Area Network Support Details, page 28-37
Monitoring Virtualized Service Module, page 28-48
Viewing Virtual Port Channel (vPC) Configurations
A Virtual Port Channel (vPC) allows links that are physically connected to two different 
Cisco Nexus 7000 or Cisco Nexus 5000 series network elements to appear as a single port channel by a 
third device as shown in Figure 28-1. The third device can be a switch, server, or any other networking 
device that supports port channels. A vPC can provide Layer 2 multipathing, which allows you to create 
redundancy and increase bisectional bandwidth by enabling multiple parallel paths between nodes and 
allowing load balancing traffic. You can use only Layer 2 port channels in the vPC.  
						

							 
28-2
Cisco Prime Network 4.3.2 User Guide
Chapter 28      Managing Data Center Networks
  Viewing Virtual Port Channel (vPC) Configurations
Figure 28-1 vPC Architecture
A vPC consists of the following components:
Two vPC peer switches, among which one is primary and one is secondary. The system formed by 
the two peer switches is referred to as a vPC domain. 
A peer link, also known as multichassis EtherChannel trunk (MCT), which connects the vPC peer 
switches. A peer link is a redundant 10 Gigabit Ethernet Port Channel,which is used to carry traffic 
from one system to the other when needed and to synchronize forwarding tables.
vPC member ports that form the PortChannel and are split between the vPC peers. 
A routed link, called as a vPC peer-keepalive or fault-tolerant link is a Layer 3 Gigabit Ethernet link, 
used to resolve dual-active scenarios where the peer link connectivity is lost.
A vPC domain is associated to a single Virtual Device Context (VDC), so all vPC interfaces belonging 
to a given vPC domain must be defined in the same VDC. You must have a separate vPC peer link and 
peer keepalive link infrastructure for each VDC deployed. Consolidating a vPC pair (two vPC peer 
devices of the same domain) in two VDCs of the same physical device is not supported. The vPC peer 
link must use 10-Gigabit Ethernet ports for both ends of the link; otherwise, the link will not be formed.
A vPC provides the following benefits:
Allows a single device to use a port channel across two upstream devices
Eliminates STP blocked ports
Provides a loop-free topology
Uses all available uplink bandwidth
Provides fast convergence in case of link or a device failure
Provides link level resiliency
Assures high availability
Prime Network supports vPC on Cisco Nexus 5000 series and Cisco Nexus 7000 series network 
elements.
To view the vPC configuration details in Prime Network Vision:
Step 1Right-click on the required device and choose the Inventory option. 
vPC peer link
273225
Nexus 7000
device Nexus 7000
device
vPC
device vPC
devicevPC domain
Peer-keepalive  link