Cisco Prime Nerk 43 User Guide

							 
26-27
Cisco Prime Network 4.3.2 User Guide
Chapter 26      Managing Mobile Transport Over Pseudowire (MToP) Networks
  Viewing MLPPP Properties
Table 26-13 describes the information that is displayed for MLPPP. 
Step 3To view properties for individual MLPPP bundles, double-click the hyperlinked entry in the MLPPP 
Bundle table. 
Table 26-14 describes the information that is displayed in the MLPPP Properties window. 
Table 26-13 MLPPP Properties
Field Description
Type Type of properties; in this case, MLPPP.
MLPPP Bundle Table
MLPPP MLPPP bundle name, hyperlinked to the MLPPP Properties window.
Name MLPPP interface name. 
Group MLPPP group to which the bundle belongs.
Active Link Number of active interfaces participating in MLPPP. 
Admin Status Administrative status of the MLPPP bundle: Up or Down.
Operational Status Administrative status of the MLPPP bundle: Up or Down.
LCP Status Link Control Protocol (LCP) status of the MLPPP bundle: Closed, 
Open, Started, or Unknown. 
Table 26-14 MLPPP Bundle and Member Properties
Field Description
MLPPP MLPPP bundle name, hyperlinked to MLPPP in logical inventory.
Name MLPPP interface name. 
Group Group to which the MLPPP bundle belongs.
Active Link Number of active interfaces participating in MLPPP. 
Admin Status Administrative status of the MLPPP bundle: Up or Down.
Operational Status Operational status of the MLPPP bundle: Up or Down.
LCP Status Link Control Protocol (LCP) status of the MLPPP bundle: Closed, 
Open, Started, or Unknown. 
Minimum Configured 
LinkMinimum number of configured links for an MLPPP bundle.
Maximum Configured 
LinkMaximum number of configured links for an MLPPP bundle.
Bandwidth Bandwidth allocated to the MLPPP bundle. 
MTU Size of the Maximum Transmission Unit (MTU), from 1 to 2147483647 
bytes. 
Keepalive Status of the keepalive function: Set, Not Set, or Unknown. 
Keepalive Time If keepalive is enabled, the amount of time, in seconds, to wait before 
sending a keepalive message. 
Interleave Enabled Whether or not interleaving of small fragments is enabled.  
						

							 
26-28
Cisco Prime Network 4.3.2 User Guide
Chapter 26      Managing Mobile Transport Over Pseudowire (MToP) Networks
  Viewing MLPPP Properties
Fragment Disable Whether fragmentation is enabled or disabled: True or False.
Fragment Delay Maximum size, in units of time, for packet fragments on an MLPPP 
bundle. Values range from 1 to 999. 
Fragment Maximum Maximum number of MLPPP bundle fragments. 
Keepalive Retry Number of times that the device sends keepalive packets without 
response before closing the MLPPP bundle protocol. Values range from 
2 to 254.
Load Threshold Minimum load threshold for the MLPPP bundle. If the traffic load falls 
below the threshold, the link is removed.
Table 26-14 MLPPP Bundle and Member Properties (continued)
Field Description 
						

							 
26-29
Cisco Prime Network 4.3.2 User Guide
Chapter 26      Managing Mobile Transport Over Pseudowire (MToP) Networks
  Viewing MLPPP Link Properties
Step 4To view the interface properties in physical inventory, double-click the required entry in the ID column. 
Viewing MLPPP Link Properties
An MLPPP link is a link that connects two MLPPP devices. 
To view MLPPP link properties: 
Step 1In the Vision client map view, select a link connected to two MLPPP devices and open the link quick 
view window as shown in Figure 26-15.
Figure 26-15 MLPPP Link in Link Quick View
Step 2
In the link quick view window, click Properties. 
MLPPP Members Table
ID MLPPP bundle member identifier, hyperlinked to the interface in 
physical inventory. 
Type No value is displayed in this field. 
Binding Information Binding information to which the interface is associated. The value is 
null.
Binding Status No value is displayed in this field.
Discovery Protocols Discovery protocol used on the interface.
Table 26-14 MLPPP Bundle and Member Properties (continued)
Field Description 
						

							 
26-30
Cisco Prime Network 4.3.2 User Guide
Chapter 26      Managing Mobile Transport Over Pseudowire (MToP) Networks
  Viewing MLPPP Link Properties
Step 3In the link properties window, select the MLPPP link. The link properties are displayed as shown in 
Figure 26-16.
Figure 26-16 MLPPP Link Properties
Table 26-15 describes the information that is displayed for the MLPPP link. 
Table 26-15 MLPPP Link Properties
Field Description
General Properties
Link Type Link protocol. In this case, MLPPP.
Type Type of link: Dynamic or Static.
Bi Directional Whether the link is bidirectional: True or False.
MLPPP Properties Properties are displayed for both ends of the MLPPP link.
MLPPP Interface configured for MLPPP, hyperlinked to the entry in physical 
inventory.
Group MLPPP group to which the interface belongs.
Active  Link Number of active interfaces participating in the MLPPP link for each device. 
Admin Status Administrative status of the interface: Up or Down.
Operational Status Operational status of the interface: Up or Down.
LCP Status LCP status of the MLPPP interface: Closed, Open, Started, or Unknown. 
						

							 
26-31
Cisco Prime Network 4.3.2 User Guide
Chapter 26      Managing Mobile Transport Over Pseudowire (MToP) Networks
  Viewing MPLS Pseudowire Over GRE Properties
Viewing MPLS Pseudowire Over GRE Properties 
Generic routing encapsulation (GRE) is a tunneling protocol, originated by Cisco Systems and 
standardized in RFC 2784. GRE encapsulates a variety of network layer packets inside IP tunneling 
packets, creating a virtual point-to-point link to devices at remote points over an IP network. GRE 
encapsulates the entire original packet with a standard IP header and GRE header before the IPsec 
process. GRE can carry multicast and broadcast traffic, making it possible to configure a routing 
protocol for virtual GRE tunnels. 
In RAN backhaul networks, GRE is used to transport cell site traffic across IP networks (nonMPLS). In 
addition, GRE tunnels can be used to transport TDM traffic (TDMoMPLSoGRE) as part of the 
connectivity in the following sample scenarios:
Among cell site-facing Cisco 7600 routers and base station controller (BSC) site-facing Cisco 7600 
routers.
Between a Cisco Mobile Wireless Router (MWR) device and a BSC site-facing Cisco 7600 router.
Using GRE tunnels to transport Any Traffic over MPLS (AToM) enables mobile service providers to 
deploy AToM pseudowires in a network where MPLS availability is discontinuous; for example, in 
networks where the pseudowire endpoints are located in MPLS edge routers with a plain IP core 
network, or where two separate MPLS networks are connected by a transit network with plain IP 
forwarding. 
To view the properties for MPLS pseudowire over GRE: 
Step 1In the Vision client, right-click the required device, then choose Inventory. 
Step 2In the Inventory window, choose Logical Inventory > Pseudowires. The Tunnel Edges table is 
displayed in the content pane as shown in Figure 26-17. 
Step 3Select the required entry and scroll horizontally until you see the required information. 
Figure 26-17 MPLS Pseudowire Tunnels over GRE Properties  
						

							 
26-32
Cisco Prime Network 4.3.2 User Guide
Chapter 26      Managing Mobile Transport Over Pseudowire (MToP) Networks
  Viewing MPLS Pseudowire Over GRE Properties
Table 26-16 describes the information included in the Tunnel Edges table specifically for MPLS 
pseudowire tunnels over GRE. 
Step 4To view GRE Tunnel properties, choose Logical Inventory > GRE Tunnels.
Figure 26-18 shows the Tunnel Edges table that is displayed for GRE tunnels.
Figure 26-18 GRE Tunnel Properties in Logical Inventory 
Table 26-17 describes the information that is displayed for GRE tunnels in logical inventory. 
Table 26-16 MPLS Pseudowire over GRE Properties
Field Description
Pseudowire Type Type of pseudowire relevant to MToP: 
AT M  A A L 5  S D U — AT M  w i t h  AT M  A d a p t a t i o n  L a y e r  5  
(AAL5) service data units. 
ATM n-to-one VCC—ATM with n-to-one virtual channel 
connection (VCC). 
ATM n-to-one VPC—ATM with n-to-one virtual path 
connection (VPC).
CESoPSN Basic—CESoPSN basic services with CAS. 
SAToP E1—SAToP on an E1 interface. 
Local MTU Size, in bytes, of the MTU on the local interface. 
Remote MTU Size, in bytes, of the MTU on the remote interface. 
Preferred Path Tunnel Path to be used for MPLS pseudowire traffic.
Click the hyperlinked entry to view the tunnel details in logical 
inventory.  
						

							 
26-33
Cisco Prime Network 4.3.2 User Guide
Chapter 26      Managing Mobile Transport Over Pseudowire (MToP) Networks
  Network Clock Service Overview
Network Clock Service Overview
Network clock service refers to the means by which a clock signal is generated or derived and distributed 
through a network and its individual nodes for the purpose of ensuring synchronized network operation. 
Network clocking is particularly important for mobile service providers to ensure proper transport of 
cellular traffic from cell sites to Base Station Control (BSC) sites.
NoteIn Prime Network, clock service refers to network clock service.
The following topics describe how to use the Vision client to monitor clock service: 
Monitoring Clock Service, page 26-34
Monitoring PTP Service, page 26-35
Viewing Pseudowire Clock Recovery Properties, page 26-41 
Viewing SyncE Properties, page 26-45
Applying a Network Clock Service Overlay, page 26-48
Viewing CEM and Virtual CEM Properties, page 26-49 
Table 26-17 GRE Tunnel Properties in Logical Inventory
Field Description
Name Tunnel name.
IP Address Tunnel IP address.
Source IP address local to the device.
Destination IP address of the remote router. 
State State of the tunnel: Up or Down. 
Keepalive Time If keepalive is enabled, the amount of time, in seconds, to wait before 
sending a keepalive message.
Type Tunnel type.
Keepalive Status of the keepalive function: Set, Not Set, or Unknown.
Keepalive Retry Number times that the device continues to send keepalive packets 
without response before bringing the tunnel interface protocol down. 
Values range from 2 to 254, with a default of 3. 
						

							 
26-34
Cisco Prime Network 4.3.2 User Guide
Chapter 26      Managing Mobile Transport Over Pseudowire (MToP) Networks
  Network Clock Service Overview
Monitoring Clock Service 
To monitor clock service:
Step 1In the Vision client, right-click the required device, then choose Inventory. 
Step 2In the Inventory window, choose Logical Inventory > Clock. Clock service information is displayed in 
the content pane as shown in Figure 26-19. 
Figure 26-19 Clock Service Properties
Table 26-18 describes the information displayed for clocking service. 
Table 26-18 Clock Service Properties
Field Description
Clock Service Mode This field is not populated.
Network Clock Select 
ModeAction to take if the master device fails:
Non-revert—Do not use the master device again after it recovers from the 
failure.
Revert—Use the master device again after it recovers and functions 
correctly for a specified amount of time.
Unknown—The network clock selection mode is unknown.
Service Status Status of the system service:
Initializing—The service is starting up.
Down—The service is down.
Reset—The service has been reset.
Running—The service is running. 
Other—A status other than those listed.  
						

							 
26-35
Cisco Prime Network 4.3.2 User Guide
Chapter 26      Managing Mobile Transport Over Pseudowire (MToP) Networks
  Network Clock Service Overview
Monitoring PTP Service 
In networks that employ TDM, periodic synchronization of device clocks is required to ensure that the 
receiving device knows which channel is which for accurate reassembly of the data stream. The 
Precision Time Protocol (PTP) standard: 
Specifies a clock synchronization protocol that enables this synchronization. 
Applies to distributed systems that consist of one or more nodes communicating over a network. 
Defined by IEEE 1588-2008, PTP Version 2 (PTPv2) allows device synchronization at the nanosecond 
level. 
PTP uses the concept of master and slave devices to achieve precise clock synchronization. Using PTP, 
the master device periodically starts a message exchange with the slave devices. After noting the times 
at which the messages are sent and received, each slave device calculates the difference between its 
system time and the system time of the master device. The slave device then adjusts its clock so that it 
is synchronized with the master device. When the master device initiates the next message exchange, the  Active Clock Source Current active clock source used by the device.
Hold Timeout How long the device waits before reevaluating the network clock entry. Values 
can be from 0-86400 seconds, Not Set, or infinite.
Service Type Type of system service, such as Clock or Cisco Discovery Protocol. 
Use Stratum4 Quality of the clock source:
True—Use Stratum 4, the lowest level of clocking quality.
False—(Default) Use Stratum 3, a higher level of clocking quality than 
Stratum 4. 
Clock Source TableThis table is displayed only if there are active clock sources.
Clock Source Current active clock source used by the device. 
Network Clock 
PriorityPriority of the clock source with 1 being the highest priority.
Source Type Method by which clocking information is provided:
BITS—Timing is supplied by a Building Integrated Timing Supply (BITS) 
port clock.
E1/T1—Clocking is provided via an E1 or T1 interface.
Packet-Timing—Clocking is provided over a packet-based network.
Synchronous Ethernet—Clocking is provided by Synchronous Ethernet.
Others—Clocking is provided by a source other than the above. 
Valid Source Validity of the clock source:
True—The clock source is valid and operational. 
False—The clock source is not valid or is not operational. 
Table 26-18 Clock Service Properties (continued)
Field Description 
						

							 
26-36
Cisco Prime Network 4.3.2 User Guide
Chapter 26      Managing Mobile Transport Over Pseudowire (MToP) Networks
  Network Clock Service Overview
slave device again calculates the difference and adjusts its clock. This repetitive synchronization ensures 
that device clocks are coordinated and that data stream reassembly is accurate. For configuring PTP, see 
Configuring SONET, page 26-53.