Entuity Module Mpls PDF

USER GUIDE
Entuity 12.5
MPLS Module 2.0
The Entuity MPLS module supports management of MPLS by taking a tiered approach to management of the LDP, LSR and VPN technologies. Entuity MPLS provides detailed inventory information. For example, port-level application of VRFs and the association between VRFs, route distinguishers and imported and exported route targets. Performance data is available at the virtual port level (corresponding to a VRF).
North America Headquarters

4 Mount Royal Avenue Suite 340 Marlborough, MA 01752 Tel: +1 508 357 6344 Fax: +1 508 357 6358
EMEA Headquarters
9a Devonshire Square London, EC2M 4YN Tel: +44 (0)20 7444 4800 Fax: +44 (0)20 7444 4808
www.entuity.com
0000-0125-PD053 entuity_module_mpls.rev1.fm
Copyright 2000 - 2012 Entuity. All rights reserved.
Entuity The Entuity product and its related documentation are protected by copyright and distributed under licenses restricting use, copying, distribution, and decompilation. Unless you have negotiated with Entuity specific terms and conditions for using its product and associated documentation, such use shall be governed by Entuity's standard licence terms, a copy of which is distributed with the product. Entuity may make improvements and/or changes to the product(s) and/or program(s) described in this publication at any time. These changes will be incorporated into new editions of the relevant publication.
Entuity , Eye of the Storm , InSight Center , Green IT Perspective, Network Delivery Perspective and Service Delivery Perspective are registered trademarks of Entuity. All other trademarks are the property of their respective owners.
License terms and conditions of use for Entuity and included third party software can be found on the Entuity server at entuity_home/licenseTerms/. A listing of these third party trademarks, references and software included with Entuity is available through its web UI.
Entuity
Contents
1 Introducing Entuity MPLS Module
Activating Entuity MPLS .............................................................. 1-2 Module Licensing ................................................................... 1-2 Module Availability.................................................................. 1-2 Module Security...................................................................... 1-2
2 Managing Label Distribution Protocol (LDP)

LDP Overview .............................................................................. 2-2 Device MPLS ............................................................................... 2-2 MPLS LDP Entity ......................................................................... 2-4 MPLS LDP Entity .................................................................... 2-4 MPLS LDP Entity Status ......................................................... 2-6 MPLS LDP Peers ......................................................................... 2-8 MPLS LDP Peers General ...................................................... 2-8 MPLS LDP Label Ranges ....................................................... 2-9 MPLS LDP Peer Status......................................................... 2-10 MPLS LDP Label Ranges .......................................................... 2-11 MPLS LDP Label Range MPLS LDP Peers .......................... 2-11
3 Managing Label Switch Routers

MPLS LSR ................................................................................... 3-1
4 Introducing MPLS VPN

MPLS VRF General ..................................................................... 4-1 MPLS Route Targets ................................................................... 4-2 MPLS VRFs Status ...................................................................... 4-3 MPLS Interface VRF Instances General ..................................... 4-4 MPLS Interface VRF BGP Neighbors ..................................... 4-5 VRF on an Interface Instance ................................................. 4-6
5 Managing Entuity MPLS Events

Managing MPLS LSR Interface Error Events .............................. 5-1 Setting MPLS LSR Interface Error Thresholds....................... 5-1 Setting MPLS LSR Interface Thresholds ................................ 5-3 Managing MPLS LSR Platform Error Events .............................. 5-4
Entuity MPLS Module Guide iii
Entuity
Setting MPLS LSR Platform Error Thresholds ....................... 5-4 Managing MPLS VPN Events ..................................................... 5-6 Setting MPLS VPN Thresholds............................................... 5-6
6 Handling MPLS Traps

Setting up the Open Trap Receiver ........................................... 6-1
7 Reporting on Entuity MPLS

Running MPLS Reports .............................................................. 7-1
A Entuity Events
MPLS LDP Entity Errors .............................................................. A-1 MPLS LDP Entity Errors Cleared ................................................ A-1 MPLS LDP Entity Non-operational .............................................. A-1 MPLS LDP Entity Operational ..................................................... A-2 MPLS LDP Entity Rejected Sessions .......................................... A-2 MPLS LDP Entity Rejected Sessions Cleared ............................ A-2 MPLS LDP Entity Shutdown Notifications Received .................. A-3 MPLS LDP Entity Shutdown Notifications Received Cleared .... A-3 MPLS LDP Entity Shutdown Notifications Sent .......................... A-3 MPLS LDP Entity Shutdown Notifications Sent Cleared ............ A-4 MPLS LDP Peer Disappeared ..................................................... A-4 MPLS LDP Peer Newly Discovered ............................................ A-4 MPLS LDP Peer Non-operational ............................................... A-5 MPLS LDP Peer Operational ...................................................... A-5 MPLS LDP Peer TLV Errors ........................................................ A-5 MPLS LDP Peer TLV Errors Cleared ........................................... A-5 MPLS LDP Peer Unknown Message Types ............................... A-6 MPLS LDP Peer Unknown Message Types Cleared .................. A-6 MPLS LSR Interface High Discard Rate (Lookup Failure) .......... A-6 MPLS LSR Interface High Discard Rate (Lookup Failure) Cleared A-7 MPLS LSR Interface High Error Free Discard Rate (RX) ............ A-7 MPLS LSR Interface High Error Free Discard Rate (RX) Cleared A-7 MPLS LSR Interface High Error Free Discard Rate (TX) ............ A-7 MPLS LSR Interface High Error Free Discard Rate (TX) Cleared A-8 MPLS LSR Interface High Fragmentation Rate .......................... A-8 MPLS LSR Interface High Fragmentation Rate Cleared ............ A-8 MPLS LSR Interface Low Bandwidth .......................................... A-9
Entuity MPLS Module Guide iv
Entuity
MPLS LSR Interface Low Bandwidth Cleared ............................ A-9 MPLS LSR Interface Low Buffer Space ...................................... A-9 MPLS LSR Interface Low Buffer Space Cleared ........................ A-9 MPLS LSR Platform High Discard Rate (Lookup Failure) ........ A-10 MPLS LSR Platform High Discard Rate (Lookup Failure) Cleared A-10 MPLS LSR Platform High Error Free Discard Rate (RX) .......... A-10 MPLS LSR Platform High Error Free Discard Rate (RX) Cleared A-11 MPLS LSR Platform High Error Free Discard Rate (TX) ........... A-11 MPLS LSR Platform High Error Free Discard Rate (TX) Cleared A-11 MPLS LSR Platform High Fragmentation Rate ......................... A-11 MPLS LSR Platform High Fragmentation Rate Cleared ........... A-12 MPLS VRF High Illegal Label Rate ........................................... A-12 MPLS VRF High Illegal Label Rate Cleared .............................. A-12 MPLS VRF Interface BGP Neighbor Disappeared ................... A-13 MPLS VRF Interface BGP Neighbor Newly Discovered ........... A-13 MPLS VRF Non-operational ...................................................... A-13 MPLS VRF Operational ............................................................. A-13
Glossary Index
Entuity MPLS Module Guide
Entuity
Figures
Figure 2-1 Figure 2-2 Figure 2-3 Figure 2-4 Figure 2-5 Figure 2-6 Figure 2-7 Figure 2-8 Figure 3-1 Figure 4-1 Figure 4-2 Figure 4-3 Figure 4-4 Figure 4-5 Figure 4-6 Figure 4-7 Figure 5-1 Figure 5-2 Figure 5-3 Figure 5-4 Device MPLS .................................................................... 2-4 MPLS LDP Entity .............................................................. 2-6 MPLS LDP Entity Status ................................................... 2-8 MPLS LDP Peer General Details ...................................... 2-9 MPLS LDP Label Ranges ................................................. 2-10 MPLS LDP Peer Status .................................................... 2-11 MPLS LDP Label Range MPLS LDP Peers ...................... 2-11 MPLS LDP Label Range MPLS LDP Peers ...................... 2-12 MPLS LSR ........................................................................ 3-3 A Simple MPLS VPN Configuration ................................. 4-1 MPLS VRF General .......................................................... 4-2 VRF Route Targets ........................................................... 4-3 VRF Status ....................................................................... 4-4 MPLS Interface VRF Instances ........................................ 4-5 MPLS Interface VRF BGP Neighbors ............................... 4-5 VRF on an Interface Instance ........................................... 4-6 MPLS LSR Interface Error Event Thresholds ................... 5-2 MPLS LSR Interface Event Thresholds ............................ 5-3 MPLS LSR Platform Error Event Thresholds ................... 5-5 MPLS VPN Illegal Label Rate Thresholds ........................ 5-7
vi
1 Introducing Entuity MPLS Module

Entuity MPLS improves manageability of configuration and operation of MPLS-enabled networks. Entuity MPLS provides automatic, continual discovery of MPLS IP VPNs and takes a tiered approach to their management through its insight into:
Label Distribution Protocol (LDP), and its propagation of labels to LSRs Label Switch Routers (LSRs), and their label switching performance through which they
deliver core connectivity
MPLS-VPNs, and their pushing and dropping of labels at the MPLS edge to exploit the
label switching core, providing discrete virtual network topologies. With insight into each level Entuity MPLS provides detailed configuration, utilization, and performance data. LDP peering is fundamental, and Entuity MPLS discovers and closely monitors their configuration. Changes in peering are quickly discovered and events raised, for example when peers are discovered, appear or disappear, change status, issue alerts. The events clearly identify the concerned peers allowing your operations staff to pursue early problem resolution. The next tier of Entuity MPLS is through management of LSRs. LSR label switching can occur at either the interface or platform level, which Entuity MPLS can clearly identify. Key attributes discovered are label ranges accepted, through which you can identify misconfiguration, bandwidth and buffer space allocation, packet fragmentation. An extensive set of events available at the platform and interface levels alert on performance issues, for example high packet fragmentation, high discard rates, low LSR resources. The final tier of Entuity MPLS is VPN management. For each device Entuity MPLS can monitor Virtual Routing and Forwarding (VRF) technology, specifically the multiple instances of a routing table that co-exist within the same router at the same time. For example, portlevel application of VRFs and the association between VRFs, route distinguishers and imported and exported route targets. Performance data is available at the virtual port level (corresponding to a VRF). Example Use Cases:
VRF infrastructure report, to assist with conformance with corporate policies and
compliance procedures documentation of the MPLS network configuration. This report includes details of port-level application of VRFs and the association between VRFs, route distinguishers and imported and exported route targets.
Inconsistent VRF name report, to assist with global naming policies whereby all VRF
names (and often their constituent route targets and route distinguishers) are globally defined. This report shows where deviations from the convention may need to be corrected on a per device and per interface basis.
VPN scale estimation, to assess the growth of MPLS IP VPNs a network architect requires
an indication of the scale of each VPN.
Interface VPN utilization analysis, to allow drill-down to discover how much traffic each
VPN is contributing to the total and whether or not any of these VPNs are at capacity.
1-1
Entuity
Activating Entuity MPLS
Entuity MPLS module integrates with the Entuity IP SLA module, for example together providing details of event on availability failure within a VRF, LSP traceroute and IP SLA - Per VRF Performance. MPLS management information is available through the Component Viewer, Flex Reports and a new Essential Report.
Activating Entuity MPLS

Activation of Entuity MPLS does not require additional software installation. You must acquire an appropriate license, include its configuration and then run Entuity configure.
Module Licensing
Entuity MPLS is available under the standard Entuity license (see the Entuity Getting Started Guide).
Module Availability
The Entuity MPLS module is available with Entuity in all supported environments (see the Entuity Getting Started Guide).
Module Security
Entuity MPLS object details are placed into views within Entuity and access permissions granted based on that view membership according to the standard Entuity security model (see the Entuity Security Guide). To activate Entuity MPLS:
1) Acquire a valid license from your Entuity representative. The new license file should be
added to entuity_home/etc.
2) Stop the Entuity server. 3) From entuity_home/install run Entuity configure and when it is run: as a wizard, from the Module Select page check the Entuity MPLS module from the command line, when prompted enter yes to modify the activated modules
and again when prompted to activate the Entuity MPLS module.
4) Restart the Entuity server. 5) Entuitys discovery process takes a number of hours to discover all of the Entuity MPLS
attributes.
1-2
2 Managing Label Distribution Protocol (LDP)

The Label Distribution Protocol (LDP) establishes MPLS LSPs using the existing IP routing network. Entuity provides a detailed inventory of LDP distribution within its managed network. Through Component Viewer you can view a series of tabs including a breakdown of LDP configuration and current performance:
MPLS LDP Entity MPLS LDP Entity Status MPLS LDP Peers MPLS LDP Peer Status MPLS LDP Label Ranges MPLS LDP Label Range MPLS LDP Peers MPLS LDP Label Range Ports.
Entuity MPLS includes a set of events which monitor this polled data, providing clear insight into changes and possible problems with your LDP distribution. Events are raised against these measures, event thresholds are configurable:
MPLS LDP Entity Errors MPLS LDP Entity Operational Status MPLS LDP Entity Rejected Sessions MPLS LDP Entity Shutdown Notifications Received MPLS LDP Entity Shutdown Notifications Sent MPLS LDP Peer Disappeared MPLS LDP Peer Newly Discovered MPLS LDP Peer Operational Status MPLS LDP Peer TLV Errors MPLS LDP Peer Unknown Message Types
Entuity MPLS includes a series of key reports:
LDP Inventory Detail Report LDP Inventory Summary Report LDP Label Range Report LDP Peer Performance Report
Using Report Server you can also create new reports.
2-1
Entuity
LDP Overview
LDP Overview
LDP is a set of procedures by which one LSR informs another of the meaning of labels used to forward traffic between and through them. It is through LDP that LSRs establish Label Switched Paths (LSPs). LSPs are also known as MPLS tunnels. To maintain the Label Switched Router (LSR) database MPLS labels must be distributed. LDP associates a Forwarding Equivalence Class (FEC) with each LSP it creates. The FEC associated with an LSP specifies which packets are handled by that LSP. An LSP starts at the Label Edge Router (LER), which assigns the first label to the packet determined by the FEC. The LER then forwards the packet to the next router in the path, which swaps the packet's outer label for another label, and forwards it to the next router. The last router in the path removes the label from the packet and forwards the packet based on the header of its next layer, for example IPv4. LDP Peers are two LSRs which use LDP to exchange label/FEC mapping information. This exchange takes place during an LDP session.
Device MPLS
You can view device centric MPLS data through the MPLS tab on a device in Component Viewer. Entuity monitors device MPLS data. Attribute
LSR ID Loop Detection Capability
Description
The Label Switching Router (LSR) identifier is the first 4 bytes of the Label Distribution Protocol (LDP) identifier. Indicates the LSR loop detection capability, and not necessarily its current state. Loop detection is determined during session initialization, individual sessions may not run with loop detection. Loop detection can be: None, loop detection is not supported on this LSR.

Label Retention Mode
Other, loop detection is supported but by a method other than those explicitly defined in the MIB. Hop Count, loop detection is supported only through hop count. Path Vector, loop detection is supported only through path vector. Hop Count And Path Vector, loop detection is supported by both hop count and path vector.
When set to: Conservative, the advertised label mappings are retained only if they will be used to forward packets, i.e. if label came from a valid next hop.
Table 2-1 Device MPLS
Liberal, all advertised label mappings are retained whether they are from a valid next hop or not.
2-2
Entuity
Device MPLS
Attribute
LDP Session Traps Enabled
Description
When set to: Enabled, the mplsLdpSessionUp and mplsLdpSessionDown can be generated.
Max Label Stack Depth LSR In Segment Traps Enabled
Disabled, the mplsLdpSessionUp and mplsLdpSessionDown can not be generated. The default is Disabled.
Maximum stack depth supported by this LSR. Traps indicating incoming MPLS segments (labels). If administrative and operational status objects are down, the LSR does not forward packets. If these status objects are up, the LSR forwards packets. Traps indicating outgoing MPLS segments (labels). Traps indicating changes to the cross-connect table, e.g. the association between incoming and outgoing segments (labels). Number of ports. Number of VRFs configured on the router. Number of configured VRFs currently in use. Number of interfaces connected to all of the routers VRFs. Must be set to Enable for the router to send MPLS VPN SNMP notifications. Number of routes allowed on the router, which is only limited by the amount available for the router.
LSR Out Segment Traps Enabled LSR Cross Connect Traps Enabled Number of LSR Ports Number of Configured VRFs Number of Active VRFs Number of Interfaces Connected to VRFs VPN Notifications Enabled VPN Global Route Limit Table 2-1 Device MPLS
2-3
Entuity
MPLS LDP Entity
Figure 2-1 Device MPLS
MPLS LDP Entity

MPLS LDP Entity
Attribute
Label Retention Mode
Description
When configured to Conservative, the advertised label mappings are retained only if they will be used to forward packets, i.e. if label came from a valid next hop.
Liberal, then all advertised label mappings are retained whether they are from a valid next hop or not.
Threshold for Session Initiation Attempts When set to: 0 indicates that the threshold is infinity, and so effectively the SNMP notification is disabled.
1 or greater, the LDP entity sends an mplsLdpFailedInitSessionThresholdExceeded when the number of session initialization messages sent exceeds this threshold.
Table 2-2 MPLS LDP Entity
2-4
Entuity
MPLS LDP Entity
Attribute
Label Distribution Method
Description
When the LSR is using: Downstream Unsolicited distribution it advertises FEC-label bindings to its peers when it is ready to forward packets in the FEC by means of MPLS.
Downstream on Demand distribution provides FEClabel bindings to a peer in response to specific requests from the peer for a label for the FEC.
LDP Protocol Version Hop Count Limit
Version number of the protocol. When set to 0, this indicates that the version of the protocol is unknown. Maximum allowable number of hops permitted, applicable when Loop Detection Capability must be set to either Hop Count And Path Vector or Hop Count. LDP TCP port 646 used for establishing transport connection. The mplsLdpPathVectorLimitMismatch notification is generated when there is a mismatch in the Path Vector Limits between the Entity and Peer during session initialization. The session uses the value which is configured as the Entity's Path Vector Limit. However, a notification should be generated to indicate that a mismatch occurred. Value which is the proposed Hello hold time for this LDP Entity. A value of 0 means use the default, which is 15 seconds for Link Hellos and 45 seconds for Targeted Hellos. A value of 65535 means infinite.
LDP TCP Discovery Port PVL Mismatch Traps Enabled
Hello Hold Time
Is Targeted Peer

Targeted Peer Address Maximum PDU Length
When set to: true, the LDP entity uses targeted peers false the LDP entity does not uses targeted peers.
Address used for the Extended Discovery. Maximum PDU Length that is sent in the Common Session Parameters of an Initialization Message. A value of 255 or less specifies the default maximum length of 4096 octets. Value which is the proposed keep alive hold timer for this LDP Entity. UDP port, by default 646, used with the discovery message.
Keep Alive Hold Time LDP UDP Discovery Port Table 2-2 MPLS LDP Entity
2-5
Entuity
MPLS LDP Entity
Attribute
Path Vector Limit
Description
When set to: 0, loop detection for path vectors is disabled. a value greater than zero, loop detection for path vectors is enabled, and the Path Vector Limit is this value. For the Path Vector Limit to have effect the devices Loop Detection Capability must be set to either Hop Count And Path Vector or Path Vector.
Table 2-2 MPLS LDP Entity
Figure 2-2 MPLS LDP Entity
MPLS LDP Entity Status

:
Attribute
Admin Status
Description

Table 2-3 MPLS LDP Entity Status
Administrative status of this LDP Entity. When set to: Enable, the entity can create new sessions with its peer. Disable, any existing peer connections are lost. When set to disable the administrator can amend entity values
2-6
Entuity
MPLS LDP Entity
Attribute
Oper Status
Description

Attempted Sessions Rejects (No Hello) Rejects (Bad Ad.) Rejects (PDU Length) Rejects (LR)
Operational status of the LDP entity, which can be: Unknown, this should only be a transitional state. Enabled Disabled
Total number of attempted sessions for this LDP Entity. count of the Session Rejected/No Hello Error Notification Messages sent or received by the LDP entity. A count of the Session Rejected/Parameters Advertisement Mode Error Notification Messages sent or received by this LDP Entity. A count of the Session Rejected/Parameters Max Pdu Length Error Notification Messages sent or received by this LDP Entity. A count of the Session Rejected/Parameters Label Range Notification. Notification Messages sent or received by this LDP Entity. Number of Bad LDP Identifier Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity. Number of Bad PDU Length Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity. Number of Bad Message Length Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity. Number of Bad TLV Length Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity. Number of Malformed TLV Value Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity. Number of Session Keep Alive Timer Expired Errors detected by the session(s) (past and present) associated with this LDP Entity. Number of Shutdown Notifications received related to session(s) (past and present) associated with this LDP Entity. Number of Shutdown Notifications sent related to session(s) (past and present) associated with this LDP Entity. Change in the number of rejected sessions between the two most recent pollings. Change in the number of errors between the two most recent pollings. Change in the number of shutdowns received between the two most recent pollings. Change in the number of shutdowns sent between the two most recent pollings.
Bad Identifier Bad PDU Length, Length Errors TLV Length Errors Bad TLV Values Keep Alive Timeouts Shutdowns Received Shutdowns Sent Rejected Sessions Delta Error Delta Shutdowns Received Delta Shutdowns Sent Delta,
Table 2-3 MPLS LDP Entity Status
2-7
Entuity
MPLS LDP Peers
Figure 2-3 MPLS LDP Entity Status
MPLS LDP Peers

The connection from the local LDP entity to an LDP peer is through to the remote LDP entity. Details of the remote peered LDP are as viewed from the local entity.
:
Attribute
General MPLD LDP Label Ranges MPLS LDP Entity Peer Status Table 2-4 Remote Peer Details
Description
Discovery details, for example advertised IP address Supported label ranges Details of the remote entity Key status metrics.
MPLS LDP Peers General

This tab lists discovery details of the remote entity of the LDP peer: Attribute
Path Vector Loop Detection Advertised IP
Description
Indicates whether loop detection based on path vectors is disabled or enabled for this LDP peer. IP address advertised to its LDP peers.
Table 2-5 MPLS LDP Peers General Details
2-8
Entuity
MPLS LDP Peers
Attribute
Path Vector Hop Limit
Description
a value greater than zero, loop detection for path vectors is enabled, and the Path Vector Limit is this value. For the Path Vector Hop Limit to have effect the devices Loop Detection Capability must be set to either Hop Count And Path Vector or Path Vector. Label Distribution Method
When set to: 0, loop detection for path vectors is disabled.
When the LSR is using: Downstream Unsolicited distribution it advertises FEClabel bindings to its peers when it is ready to forward packets in the FEC by means of MPLS. Downstream on Demand distribution provides FEC-label bindings to a peer in response to specific requests from the peer for a label for the FEC.
Table 2-5 MPLS LDP Peers General Details
Figure 2-4 MPLS LDP Peer General Details
MPLS LDP Label Ranges

:
Attribute
Name IF Index Maximum Label Minimum Label Table 2-6 MPLS LDP Label Ranges
Description
Name of the label range. Interface index of the outgoing label of this LSP. Upper boundary of the label range. Lower boundary of the label range.
2-9
Entuity
MPLS LDP Peers
Figure 2-5 MPLS LDP Label Ranges
MPLS LDP Peer Status

An LDP peer is a remote LDP entity. Attribute
Status LDP Version Peer Max PDU Length
Description
Polled state of the session, i.e. Non existent, Initialized, Open receive, Open sent and Operational. Version number of the protocol. When set to 0, this indicates that the version of the protocol is unknown. Maximum PDU Length that is sent in the Common Session Parameters of an Initialization Message. A value of 255 or less specifies the default maximum length of 4096 octets. Number of Unknown Message Type Errors detected during this session. Discontinuities in the value of this counter can occur at reinitialization of the management system, and at other times as indicated by the value of mplsLdpSeeionDiscontinuityTime. Number of Unknown TLV Errors detected during this session. Discontinuities in the value of this counter can occur at reinitialization of the management system, and at other times as indicated by the value of mplsLdpSeeionDiscontinuityTime. Difference in the number of Unknown Message Type Errors detected between the last two pollings.
Unknown Message Type Errors
Unknown TLV Errors
Unknown Message Type Error Delta Table 2-7 MPLS LDP Peer Status
2-10
Entuity
Attribute
Unknown TLV Error Delta Table 2-7 MPLS LDP Peer Status
Description
Difference in the number of Unknown TLV Errors detected between the last two pollings.
Figure 2-6 MPLS LDP Peer Status

MPLS LDP Label Range MPLS LDP Peers
This tab shows the configuration of the remote entity: Attribute
Name Path Vector Loop Detection Advertised IP Path Vector Hop Limit
Description
Name of the MPLS LDP peer. Indicates whether loop detection based on path vectors is disabled or enabled for this LDP peer. IP address advertised to its LDP peers. When set to: 0 - loop detection for path vectors is disabled.
a value greater than zero - loop detection for path vectors is enabled, and the Path Vector Limit is this value. For the Path Vector Hop Limit to have effect the devices Loop Detection Capability must be set to either Hop Count And Path Vector or Path Vector.
Figure 2-7 MPLS LDP Label Range MPLS LDP Peers
2-11
Entuity
Attribute
Label Distribution Method
Description
When the LSR is using: Downstream Unsolicited distribution it advertises FEClabel bindings to its peers when it is ready to forward packets in the FEC by means of MPLS.
Downstream on Demand distribution provides FEClabel bindings to a peer in response to specific requests from the peer for a label for the FEC.
2-12
3 Managing Label Switch Routers

A Label Switch router (LSR) is a router that supports MPLS. It is through the LSR that originate the Label Switch Path (LSP). The ingress LSR computes the path for a given LSP. The egress router is the point of output from the LSR.
MPLS LSR
The label space can be set at the platform or interface space. You can also view the LSR configuration at both the device and interface level. Attribute
Min label (RX) Max label (RX) Min label (TX) Max label (TX) Usable Bandwidth
Description
Minimum value of an MPLS label that this LSR is willing to receive on this interface. Maximum value of an MPLS label that this LSR is willing to receive on this interface. Minimum value of an MPLS label that this LSR is willing to send on this interface. Maximum value of an MPLS label that this LSR is willing to send on this interface. Total amount of usable bandwidth on this interface and is specified in kilobits per second (Kbps). This variable is not applicable when applied to the interface with index 0. Total amount of available bandwidth available on this interface and is specified in kilobits per second (Kbps). This value is calculated as the difference between the amount of bandwidth currently in use and that specified in mplsInterfaceTotalBandwidth. This variable is not applicable when applied to the interface with index 0. Total amount of buffer space allocated for this interface. This variable is not applicable when applied to the interface with index 0. Total amount of buffer space available for this interface. This variable is not applicable when applied to the interface with index 0.
Available Bandwidth
Allocated Space
Available Space
Table 3-1 MPLS LSR
3-1
Entuity
MPLS LSR
Attribute
Label Space
Description
Either set to per Platform(0) or per Interface(1). When the value is: perInterface(1) bit is set then the value of Min label (RX), Max label (RX), Min label (TX), and Max label (TX) for this entry reflect the label ranges for this interface.
perPlatform(0) bit is set, then the value of value of Min label (RX), Max label (RX), Min label (TX), and Max label (TX) for this entry must be identical to the instance of these objects with index 0.
Labels In Use (RX) Packets (RX)
Number of inbound labels used. Number of labelled packets that have been received on this interface.
Error Free Discards (e.g. insufficient Number of outbound labelled packets, which were chosen to buffer) be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a labelled packet could be to free up buffer space. Lookup Failure Discards Number of labelled packets that have been received on this interface and were discarded because there were no matching entries found for them in mplsInSegmentTable. Number of top-most labels in the outgoing label stacks that were in use on this interface. Number of labelled packets that have been transmitted on this interface. Number of outbound labelled packets, which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a labelled packet could be to free up buffer space. Number of outgoing MPLS packets that required fragmentation before transmission on this interface. Difference between two contiguous inbound Error Free Discards sampled values, as a per second average. Difference between two contiguous outbound Error Free Discards sampled values, as a per second average.
Labels In Use (Tx) Packets (TX) Error Free Discards (Tx)
Packets Fragmented Rx Discard No Error Pkt Rate Tx Discard No Error Pkt Rate
Rx Discard Lookup Failure Pkt Rate Difference between two contiguous inbound Packets (Rx) sampled values, as a per second average. TX Pkt Fragmentation Rate Table 3-1 MPLS LSR Difference between two contiguous outbound Packets Fragmented sampled values, as a per second average.
3-2
Entuity
MPLS LSR
Figure 3-1 MPLS LSR
3-3
4 Introducing MPLS VPN

A network with an MPLS backbone provides the flexibility to deliver high value VPN services. The Provider Edge (PE) router provides a different, private view of the network to each VPN. This allows for different customers to use the same network resources, using different addressing to gain secure, customer specific routing. This separation is realised through separate VRF instances on a PE behaving as separate router emulations. These Virtual Routing and Forwarding Tables (VRF) are dedicated routing tables for Layer 3 VPNs contain IP prefixes. Entuity can monitor the performance of VRF instances through monitoring the success or failure of its route target distribution.
VPN Site 1 CE PE
MPLS Tunnel PE CE VPN Site 2
Figure 4-1 A Simple MPLS VPN Configuration
MPLS VRF General

Entuity gathers MPLS configuration data from every MPLS enabled port. Attribute
VRF Name VRF Description
Description
VRF name. Description of the VRF, for example its purpose. Denotes high-level water marker for the number of routes which this VRF may hold. Denotes mid-level water marker for the number of routes which this VRF may hold. Route Distinguisher that makes the VRF unique, distinguishing between overlapping addresses in the VRF. Maximum number of routes on the VRF. It must be less than or equal to the maximum possible number of routes unless it is set to 0.
VRF High-Water Route Threshold VRF Mid-Water Route Threshold

VRF Route Distinguisher VRF Maximum Routes
Table 4-1 MPLS VRF General
4-1
Entuity
MPLS Route Targets
Figure 4-2 MPLS VRF General
MPLS Route Targets

Router targets are used as targets for routing updates. The VRF RTs tab shows all of the routing targets associated with all instances of the VRF. Attribute
Name Route Target Description Type
Description
Name of the route target distribution policy. Route target identifier. Description of the route target Import/export distribution policy for the route target, i.e. import, export and import and export. The configuration of the VPN topology is determined through the Type setting of VRFs.
Table 4-2 MPLS Route Targets
4-2
Entuity
MPLS VRFs Status
Figure 4-3 VRF Route Targets
MPLS VRFs Status

The VRFs Status tab shows the status of the VRF, and a summary of key statistics for the VRF instances.
MPLS
Attribute
Oper status
Description
Operational status of the VRF. When it is set to: Up, one or more interfaces associated with the VRF is up
Active Interface Associated Interface Routes Added Routes Deleted Routes Illegal labels
Down, the are no interfaces associated with the VRF, or all of the interfaces associated to the VRF are down.
Number of interfaces associated with the VRF that are up. Number of interfaces associated with the VRF, including both active and inactive interfaces. Number of routes added over the lifetime of the VRF. Number of routes deleted over the lifetime of the VRF. Number of routes currently used by this VRF. Number of illegal label violations on the interface. These may indicate MPLS misconfiguration or an attempt to breach network security. Illegal label violation threshold. Number of illegal label violations per second.
Illegal labels Threshold Illegal label Violation Rate Table 4-3 MPLS VRFs Status
4-3
Entuity
MPLS Interface VRF Instances General
Figure 4-4 VRF Status

With MPLS you configure virtual routers, and within them divide a physical interface into multiple logical interfaces. For each logical interface you can assign a different VRF which can be for a different customer with a distinct FEC. You can configure routing send traffic to the appropriate virtual interface. Attribute
Name MPLS VRF Interface VRF Name Classification Edge Type RDP
Description
Identifies the VRF and its interface. VRF name. VRF name. The VPN classification which denotes the context of the link, e.g. carrier-of-carrier's, enterprise, inter-provider. Either the provider edge (PE) or customer edge (CE) router. VRF Interface Route Distribution Protocol across the PE-CE link, which can be: dummy

Table 4-4 MPLS Interface VRF Instances
none BGP OSPF RIP ISIS other
4-4
Entuity
Figure 4-5 MPLS Interface VRF Instances
MPLS Interface VRF BGP Neighbors

This tab details the BGP neighbors of the VRF instance on the interface. Attribute
Name Role Address
Description
Resolved name, or IP address of the device. Role played by this EBGP neighbor with respect to this VRF, e.g. CE. IP address of the EBGP neighbor.
Table 4-5 MPLS Interface VRF BGP Neighbors
Figure 4-6 MPLS Interface VRF BGP Neighbors
4-5
Entuity
VRF on an Interface Instance

This tab details the MPLS VRF associated with the virtual interface: Attribute
Name VRF Description VRF High-Water Routes Threshold VRF Mid-Water Routes Threshold VRF Route Distinguisher VRF Maximum Routes
Description
VRF name. Description of this VRF, e.g its purpose. High-level water marker for the number of routes which this VRF may hold. Mid-level water marker for the number of routes which this VRF may hold. Route distinguisher for this VRF. Maximum number of routes, summed across all VRFs, which the device allows. When set to 0, this indicates that the device is unable to determine the absolute maximum, and you could potentially set a configured maximum greater than that allowed by the device. Name of the VRF.
VRF Name
Table 4-6 VRF on an Interface Instance
Figure 4-7 VRF on an Interface Instance
4-6
5 Managing Entuity MPLS Events

Entuity MPLS events are managed by Entuitys event manager, which allows the standard customisation options, e.g. add annotations, modify threshold levels, acknowledge events. Default event thresholds are held at the root level, but can be overridden at the individual platform, interface, or VRF. All events are generated via polling. Entuity MPLS can also be extended to support MPLS traps through Entuitys Open Trap Receiver (OTR).
Managing MPLS LSR Interface Error Events

Entuity monitors interface error performance, with events being raised against these metrics:
LSR outbound discard no error rate. By default these events are not enabled. You can enable them through both Component Viewer and Explorer, Entuity recommend using Explorer as all MPLS thresholds are available from the same page. You can set the threshold at the Entuity server root level, platform or against the individual interface. Identification of what the event is raised against is through the events data fields: Attribute
Source Impacted
Inbound lookup failure discards Outbound lookup failure discards LSR inbound discard no error rate
Description
Identifies the device and MPLS interface against which the event is raised. Identifies the particular interface against which the event is raised, specifically: actual rate,
threshold value, where values above that indicate performance problems and Entuity should raise an event.
Table 5-1 MPLS LSR Interface Error Events
These events are cleared from either after ten minutes have elapsed or when Entuity raises a Clearing event, i.e. the next poll is within the threshold boundaries.
Setting MPLS LSR Interface Error Thresholds

Setting MPLS LSR Interface Error thresholds follows the same rules as setting other event thresholds. For example, thresholds can be set at these different levels:
Global level, i.e. using the Global View on the Entuity server. Component level, e.g. selecting a particular interface.
The process for setting an MPLS LSR interface error threshold is the same, regardless of the particular metric. This example sets thresholds against a particular interface:
5-1
Entuity
1) In Component Viewer navigate to the required interface and from the context menu select
Threshold Settings. Entuity displays the Threshold Settings dialog.
Figure 5-1 MPLS LSR Interface Error Event Thresholds
2) Select the MPLS LSR I/f Error tab.

Threshold
LSR High Rx Label Lookup Failure Rate
Description
Select Enabled to turn on the threshold, and accept or amend the default failure rate of 10 per second. A failure rate value greater than this threshold and Entuity raises an MPLS LSR Interface High Discard Rate (Lookup Failure) event. Select Enabled to turn on the threshold, and accept or amend the default failure rate of 10 per second. A failure rate value greater than this threshold and Entuity raises an MPLS LSR Interface High Discard Rate (Lookup Failure) event. Select Enabled to turn on the threshold, and accept or amend the default failure rate of 10 per second. A failure rate value greater than this threshold and Entuity raises an MPLS LSR Interface High Error Free Discard Rate (RX) event. Select Enabled to turn on the threshold, and accept or amend the default failure rate of 10 per second. A failure rate value greater than this threshold and Entuity raises an MPLS LSR Interface High Fragmentation Rate event.
LSR High Tx Label Lookup Failure Rate
LSR High Rx Discard No Error Rate
LSR High Tx Fragmentation Rate
Table 5-2 MPLS Thresholds
3) Select: Reset to cancel your unapplied changes and leave you in the dialog. Cancel to remove your unapplied changes and close the dialog.
Entuity MPLS Module Guide 5-2
Entuity
Apply to write the changes to the database and close the dialog. OK to save all your unapplied changes to the database and close the dialog. Default Settings, followed by Apply or OK, to make the settings for the device the
settings for the port.
Setting MPLS LSR Interface Thresholds

Setting MPLS LSR Interface Error thresholds follows the same rules as setting other event thresholds. For example, thresholds can be set at these different levels:
The process for setting an MPLS LSR interface threshold is the same, regardless of the particular metric. This example sets thresholds against a particular interface:
Figure 5-2 MPLS LSR Interface Event Thresholds
2) Select the MPLS LSR I/f tab.

Threshold
LSR Low Bandwidthe(kbps)
Description
Select Enabled to turn on the threshold, and accept or amend the default failure rate of 15 kilobytes per second. A failure rate value greater than this threshold and Entuity raises an MPLS LSR Interface Low Bandwidth event.
Table 5-3 MPLS LSR Interface
5-3
Entuity
Managing MPLS LSR Platform Error Events
Threshold
LSR Low Buffer Space
Description
Select Enabled to turn on the threshold, and accept or amend the default failure rate of 1024 bytes per second. A failure rate value greater than this threshold and Entuity raises an MPLS LSR Interface Low Buffer Space event.
Table 5-3 MPLS LSR Interface
3) Select:
Reset to cancel your unapplied changes and leave you in the dialog. Cancel to remove your unapplied changes and close the dialog. Apply to write the changes to the database and close the dialog. OK to save all your unapplied changes to the database and close the dialog. Default Settings, followed by Apply or OK, to make the settings for the device the settings for the port.

Entuity monitors interface error platform, with events being raised against these metrics:
LSR Outbound Discard No Error Rate. By default these events are not enabled. You can enable them and set the threshold level at the Entuity server root level or platform, Identification of what the event is raised against is through the events data fields: Attribute
Source Impacted
Inbound Lookup Failure Discards Outbound Packet Fragmentation LSR Inbound Discard No Error Rate
Description
Identifies the device and MPLS interface against which the event is raised. Identifies the interface against which the event is raised, specifically: actual rate, threshold value, where values above that indicate performance problems and Entuity should raise an event.
Table 5-4 MPLS LSR Platform Error Events
These events are cleared from either after ten minutes have elapsed, or when Entuity raises a Clearing event, i.e. the next poll is within the threshold boundaries.
Setting MPLS LSR Platform Error Thresholds

Setting MPLS LSR Platform Error thresholds follows the same rules as setting other event thresholds. For example, thresholds can be set at these different levels:
Entuity MPLS Module Guide 5-4
Entuity
The process for setting an MPLS LSR platform error threshold is the same, regardless of the particular metric. This example sets thresholds against a particular device:
Figure 5-3 MPLS LSR Platform Error Event Thresholds
2) Select the MPLS LSR Platform Error tab.

Threshold
LSR High Rx Label Lookup Failure Rate
Description
Select Enabled to turn on the threshold, and accept or amend the default failure rate of 10 per second. A failure rate value greater than this threshold and Entuity raises an MPLS LSR Platform High Discard Rate (Lookup Failure) event. Select Enabled to turn on the threshold, and accept or amend the default failure rate of 10 per second. A failure rate value greater than this threshold and Entuity raises an MPLS LSR Platform High Discard Rate (Lookup Failure) event. Select Enabled to turn on the threshold, and accept or amend the default failure rate of 10 per second. A failure rate value greater than this threshold and Entuity raises an MPLS LSR Platform High Error Free Discard Rate (RX) event. Select Enabled to turn on the threshold, and accept or amend the default failure rate of 10 per second. A failure rate value greater than this threshold and Entuity raises an MPLS LSR Platform High Fragmentation Rate event.
LSR High Tx Label Lookup Failure Rate
LSR High Rx Discard No Error Rate
LSR High Tx Fragmentation Rate
Table 5-5 MPLS LSR Platform Error
3) Select:
5-5
Entuity
Managing MPLS VPN Events

Entuity monitors VPN security and configuration, with events being raised when the VPN high illegal label rate crosses the set threshold. By default this event is not enabled. You can enable them and set the threshold level at the Entuity server root level, platform or against the individual interfaces. Identification of what the event is raised against is through the events data fields. These events are cleared either after ten minutes have elapsed, or when Entuity raises a Clearing event, i.e. the next poll is within the threshold boundaries. Attribute
Source Impacted
Description
Identifies the device and MPLS interface against which the event is raised. Identifies the interface against which the event is raised. Details identifies the: actual rate,
threshold value, where values above that indicate performance problems and Entuity should raise an event.
Table 5-6 MPLS LSR VPN Events
Setting MPLS VPN Thresholds

Setting MPLS VPN thresholds follows the same rules as setting other event thresholds. For example, thresholds can be set at these different levels:
Global level, i.e. using the Global View on the Entuity server. Component level, e.g. selecting a particular device.
To set the illegal label threshold against a particular device:
1) In Component Viewer navigate to the required device and from the context menu select
5-6
Entuity
Figure 5-4 MPLS VPN Illegal Label Rate Thresholds
2) Select the MPLS VPN tab.

Threshold
VPN High Illegal Label Rate Table 5-7 MPLS VPN
Description
Select Enabled to turn on the threshold, and accept or amend the default failure rate of 10 per second. A failure rate value greater than this threshold and Entuity raises an MPLS VRF High Illegal Label Rate event.
3) Select:
5-7
6 Handling MPLS Traps

Entuity can support MPLS traps through its Open Trap Receiver (OTR). The OTR requires you to parse into Entuity the MPLS MIBs containing the required trap definitions. OTR can then receive the traps and display then through Event Viewer. (For details on OTR see the Entuity Event Integration Guide.) These are the available MPLS traps:
mplsLdpInitSessionThresholdExceeded mplsLdpPathVectorLimitMismatch mplsLdpSessionUp mplsLdpSessionDown mplsInSegmentUp mplsInSegmentDown mplsOutSegmentUp mplsOutSegmentDown mplsXCUp mplsXCDown mplsXCUp mplsXCDown mplsVrfIfUp mplsVrfIfDown mplsNumVrfRouteMidThreshExceeded mplsNumVrfRouteMaxThreshExceeded mplsNumVrfSecIllegalLabelThreshExceeded.
Setting up the Open Trap Receiver

You can configure Entuity to handle MPLS traps through the Open Trap Receiver (OTR). You must load the MIBs containing the trap definitions into Entuity:
SNMPv2-CONF.my SNMPv2-TC.my INET-ADDRESS-MIB.my DIFFSERV-MIB.my MPLS-TC-STD-MIB.my MPLS-LSR-STD-MIB.my MPLS-LDP-STD-MIB.my MPLS-LSR-STD-MIB.my
6-1
Entuity
Setting up the Open Trap Receiver
MPLS-VPN-MIB.my.
h
Entuity do not supply the MPLS MIBs. To setup the Entuity OTR:
1) Copy the MPLS MIBs into entuity_home/lib/mibs. 2) Parse the MIBs into Entuity. For example to add MPLS-LDP-STD-MIB.my from
entuity_home/lib/tools run:
parseMibs MPLS-LDP-STD-MIB.my Search Path for mib files: c:\entuity\lib\mibs **** parseMibs starting **** Added 4 traps: Deleted 0 traps for c:\EYE\2008sp1-upgrade-to2008sp2\lib\mibs\MPLS-LDP-STD-MIB.my. Adding trap mplsLdpInitSessionThresholdExceeded .1.3.6.1.2.1.10.166.4.0.1 Adding trap mplsLdpPathVectorLimitMismatch .1.3.6.1.2.1.10.166.4.0.2 with with oid oid
Adding trap mplsLdpSessionUp with oid .1.3.6.1.2.1.10.166.4.0.3 Adding trap mplsLdpSessionDown with oid .1.3.6.1.2.1.10.166.4.0.4 **** parseMibs completed ****
Parse each MIB in turn.
3) Check the loaded traps using Component Viewer.
6-2
7 Reporting on Entuity MPLS

Entuity MPLS provides reports on the three tiers of MPLS management, against:
LDP configuration and performance LSR configuration MPLS VPN configuration.

Entuity MPLS includes these Reports Server reports:
MPLS LDP Label Ranges MPLS LDP Peer Details MPLS LDP Peer Performance MPLS LDP Summary MPLS LSR Detail MPLS LSR Inventory MPLS LSR Performance MPLS VPN Device Details MPLS VPN Route Capacity MPLS VPN Device Summary.
For details on these reports see the Entuity Reports Reference Manual.
Running MPLS Reports

Entuity MPLS reports are available from the Entuity web interface:
1) Select Reports. Entuity displays the Reports home page. 2) Select Connectivity and Routing and then the specific report. 3) Configure the report.
7-1
Appendix A Entuity Events

Events are shown in Event Viewer. This section contains event descriptions, causes and possible actions to take. This information is also available through the online help.
MPLS LDP Entity Errors

The LDP entity represents a label space that is targeted for distribution to an LDP peer. Default severity level: critical, color code: red.
Typical Causes
Entity errors may be:
Bad LDP Identifier Errors Bad PDU Length Errors Bad Message Length Errors Bad Message Length Errors Bad TLV Length Errors Malformed TLV Value Errors Keep Alive Timer Expiry Errors.
Actions
Investigate the entity configuration. The event includes the LDP entity device and associated LDP peer.
MPLS LDP Entity Errors Cleared

The LDP entity no longer has associated errors. Default severity level: information, color code: green.
Typical Causes
A corrected configuration, improvement in network performance.
Actions
None.
MPLS LDP Entity Non-operational

Indicates the LDP session state has transitioned from operational to a non-operational state. Default severity level: critical, color code: red.
A-1
Entuity
MPLS LDP Entity Operational
Typical Causes
Indicates the LDP session state has transitioned from operational.
Actions
The event includes the LDP entity device and associated LDP peer. Investigate the entity configuration; the event includes the new state of the session:
Unknown Non existent Initialized Open Receive Open Sent.
MPLS LDP Entity Operational

Indicates the LDP session state has transitioned from a non-operational to an operational state. Default severity level: information, color code: green.
Typical Causes
The session is operational as the LSR has received acceptable initialization and keep alive messages.
Actions
None.
MPLS LDP Entity Rejected Sessions

LSR has received a session initialization message but has rejected the session. Default severity level: critical, color code: red.
Typical Causes
One or more of the session parameters, for example LDP protocol version, label distribution method, timer values are not acceptable. The LSR responds by sending a Session Rejected/ Parameters Error Notification message and closing the TCP connection.
Actions
Investigate the configuration of the LSR.
MPLS LDP Entity Rejected Sessions Cleared

The LDP entity has now accepted the session. Default severity level: information, color code: green.
A-2
Entuity
MPLS LDP Entity Shutdown Notifications Received
Typical Causes
The LDP entity has now accepted the session.
Actions
None.
MPLS LDP Entity Shutdown Notifications Received

The LSR has received a shutdown notification message from the peered LSR. Default severity level: critical, color code: red.
Typical Causes
When the last Hello adjacency for a LDP session is deleted, the connected LSR terminates the LDP session. The peer may close the session when it concludes that the transport connection is bad or that the peer has failed, and it terminates the LDP session by closing the transport connection.
Actions
Investigate the network connection, the status of the LSR.
MPLS LDP Entity Shutdown Notifications Received Cleared

The integrity of the LDP session has been reestablished. Default severity level: information, color code: green.
Typical Causes
The peered LSR prematurely sent a session terminated notification message, which was subsequently followed by a Want To Reestablish session message.
Actions
None.
MPLS LDP Entity Shutdown Notifications Sent

When the last Hello adjacency for a LDP session is deleted, the LSR terminates the LDP session. Default severity level: critical, color code: red.
Typical Causes
The LSR may close the session when it concludes that the transport connection is bad or that the peer has failed, and it terminates the LDP session by closing the transport connection.
A-3
Entuity
MPLS LDP Entity Shutdown Notifications Sent Cleared
Actions
Investigate the network connection, the status of the LSR.
MPLS LDP Entity Shutdown Notifications Sent Cleared

The integrity of the LDP session has been reestablished. Default severity level: information, color code: green.
Typical Causes
The LSR prematurely sent a session terminated notification message, which was subsequently followed by a Want To Reestablish session message.
Actions
None.
MPLS LDP Peer Disappeared

The LSR peer has disappeared, an Entity Shutdown Notification message may already have been raised. Default severity level: critical, color code: red.
Typical Causes
The session has been shutdown and so the peer has disappeared. The administrator may have reconfigured\removed the LSR. Alternatively the LSR may have encountered problems.
Actions
When the disappearance is unexpected Entuity may have raised additional events that indicate the cause of the disappearance.
MPLS LDP Peer Newly Discovered

A newly discovered LDP peer indicates the establishment of a new LDP session. Default severity level: information, color code: green.
Typical Causes
Administrator has added a new LSR to your network.
Actions
Check that the newly discovered peer is an expected LSR, an unexpected LSR may indicate a security failure.
A-4
Entuity
MPLS LDP Peer Non-operational
MPLS LDP Peer Non-operational

Indicates the LDP session state has transitioned from an operational to a non-operational state. Default severity level: critical, color code: red.
Typical Causes
The event associated LDP peer has a state other than operational:
Unknown Non existent Initialized Open Receive Open Sent.
Actions
The event includes the non-operational peers device name and advertised IP address that you can use to investigate the state of the peer.
MPLS LDP Peer Operational

Indicates the LDP peer state has transitioned from a non-operational to an operational state. Default severity level: information, color code: green.
Typical Causes
Peer has returned to an operational state, for example after the device has been rebooted.
Actions
None.
MPLS LDP Peer TLV Errors

The peer has received a packet of the correct type but of unknown content. Default severity level: critical, color code: red.
Typical Causes
The content may have been corrupted during transmission across the network.
Actions
Check the sending LSR configuration.
MPLS LDP Peer TLV Errors Cleared

A previous message from the peered LSR had corrupt content, the subsequent message was correctly formed.
Entuity MPLS Module Guide A-5
Entuity
MPLS LDP Peer Unknown Message Types
Default severity level: information, color code: green.
Typical Causes
The state that caused corrupt content, for example transport problems, has been resolved.
Actions
None.
MPLS LDP Peer Unknown Message Types

The LDP peer received a message of an unknown type. Default severity level: critical, color code: red.
Typical Causes
LSRs support a defined set of message types, a packet that includes a message type not configured to the LSR cannot be processed.
Actions
Check the supports message types on the LSRs.
MPLS LDP Peer Unknown Message Types Cleared

A previous message from the peered LSR was of a type this LSR did not recognize. Default severity level: information, color code: green.
Typical Causes
The most recent packet from the peer is of a supported message type.
Actions
None.
MPLS LSR Interface High Discard Rate (Lookup Failure)

Indicates the number of labelled packets that have been received on this interface and were discarded because there were no matching entries found for them in mplsInSegmentTable. Default severity level: severe, color code: orange.
Typical Causes
There were no forwarding rules for these received packets.
Actions
Check the configuration of your forwarding tables.
A-6
Entuity
MPLS LSR Interface High Discard Rate (Lookup Failure) Cleared
MPLS LSR Interface High Discard Rate (Lookup Failure) Cleared

Indicates the interfaces discard rate caused by lookup failure has transitioned to below the set threshold. Default severity level: information, color code: green.
Typical Causes
The interface is receiving packets for which it has appropriate lookup table entries.
Actions
None.
MPLS LSR Interface High Error Free Discard Rate (RX)

The rate per second of inbound labelled packets, for which no error was detected, that the LSR discarded is above the set threshold. Default severity level: severe, color code: orange.
Typical Causes
The LSR may be short of buffer space.
Actions
Check the LSR configuration, there may also be low buffer events raised for the device.
MPLS LSR Interface High Error Free Discard Rate (RX) Cleared
Indicates the interfaces discard rate of error free packets has transitioned to below the set threshold. Default severity level: information, color code: green.
Typical Causes
The initial reason for discarding packets, e.g. low buffer space, has been resolved, or traffic to the LSR may have dropped.
Actions
None.
MPLS LSR Interface High Error Free Discard Rate (TX)

The rate per second of outbound labelled packets, for which no error was detected, that the LSR discarded is above the set threshold. Default severity level: severe, color code: orange.
Typical Causes
Entuity MPLS Module Guide A-7
Entuity
MPLS LSR Interface High Error Free Discard Rate (TX) Cleared
Actions
MPLS LSR Interface High Error Free Discard Rate (TX) Cleared
Indicates the interfaces discard rate of error free packets has transitioned to below the set threshold. Default severity level: information, color code: green.
Typical Causes
Actions
None.
MPLS LSR Interface High Fragmentation Rate

This event indicates the number of outgoing MPLS packets that required fragmentation before transmission on this interface is above the set threshold. Default severity level: severe, color code: orange.
Typical Causes
An interface capacity mismatch causes incoming packets to be fragmented before they can be transmitted. Fragmentation is a resource intensive process and can adversely affect LSR performance.
Actions
Configure the LSR to send and receive compatible sized packets.
MPLS LSR Interface High Fragmentation Rate Cleared

Indicates the interfaces fragmentation rate of has transitioned to below the set threshold. Default severity level: information, color code: green.
Typical Causes
A reconfiguration of the involved interfaces, a drop in traffic on the interface.
Actions
None.
A-8
Entuity
MPLS LSR Interface Low Bandwidth
MPLS LSR Interface Low Bandwidth

Indicates the total amount of available bandwidth available on this interface is below the set threshold. Available bandwidth is calculated as the difference between the amount of bandwidth currently in use and total bandwidth. Default severity level: severe, color code: orange.
Typical Causes
Overused interface.
Actions
For an interface showing consistently low bandwidth consider adjusting its load.
MPLS LSR Interface Low Bandwidth Cleared

Indicates the amount of free bandwidth on the interface has transitioned to below the low bandwidth threshold. Default severity level: information, color code: green.
Typical Causes
Reduced load on the interface.
Actions
None.
MPLS LSR Interface Low Buffer Space

Indicates the total amount of available buffer space available on this interface is below the set threshold. Available buffer space is calculated as the difference between the amount of buffer space currently in use and total buffer space. Default severity level: severe, color code: orange.
Typical Causes
Overused interface.
Actions
For an interface showing consistently low buffer space consider adjusting its load.
MPLS LSR Interface Low Buffer Space Cleared

Indicates the amount of free buffer space on the interface has transitioned to above the low buffer space threshold. Default severity level: information, color code: green.
A-9
Entuity
MPLS LSR Platform High Discard Rate (Lookup Failure)
Typical Causes
Reduced load on the interface.
Actions
None.
MPLS LSR Platform High Discard Rate (Lookup Failure)

Indicates the number of labelled packets that have been received on this platform and were discarded because there were no matching entries found for them in mplsInSegmentTable. Default severity level: severe, color code: orange.
Typical Causes
There were no forwarding rules for these received packets.
Actions
Check the configuration of your forwarding tables.
MPLS LSR Platform High Discard Rate (Lookup Failure) Cleared

Indicates the platforms discard rate caused by lookup failures has transitioned to below the set threshold. Default severity level: information, color code: green.
Typical Causes
The platform is receiving packets for which it has appropriate lookup table entries.
Actions
None.
MPLS LSR Platform High Error Free Discard Rate (RX)

The rate per second of inbound labelled packets, for which no error was detected, that the LSR discarded is above the set threshold. Default severity level: severe, color code: orange.
Typical Causes
Actions
A-10
Entuity
MPLS LSR Platform High Error Free Discard Rate (RX) Cleared
MPLS LSR Platform High Error Free Discard Rate (RX) Cleared
Indicates the platforms discard rate of error free packets has transitioned to below the set threshold. Default severity level: information, color code: green.
Typical Causes
Actions
None.
MPLS LSR Platform High Error Free Discard Rate (TX)

The rate per second of outbound labelled packets, for which no error was detected, that the LSR discarded is above the set threshold. Default severity level: severe, color code: orange.
Typical Causes
Actions
MPLS LSR Platform High Error Free Discard Rate (TX) Cleared
Indicates the platforms discard rate of error free packets has transitioned to below the set threshold. Default severity level: information, color code: green.
Typical Causes
Actions
None.
MPLS LSR Platform High Fragmentation Rate

This event indicates the number of outgoing MPLS packets that required fragmentation before transmission on this platform is above the set threshold. Default severity level: severe, color code: orange.
A-11
Entuity
MPLS LSR Platform High Fragmentation Rate Cleared
Typical Causes
An interface capacity mismatch causes incoming packets to be fragmented before they can be transmitted. Fragmentation is a resource intensive process and can adversely affect LSR performance.
Actions
Configure the LSR to send and receive compatible sized packets.
MPLS LSR Platform High Fragmentation Rate Cleared

Indicates the platforms fragmentation rate has transitioned to below the set threshold. Default severity level: information, color code: green.
Typical Causes
A reconfiguration of the involved interfaces, a drop in traffic on the platform.
Actions
None.
MPLS VRF High Illegal Label Rate

The VRF is receiving packets with labels for which it is not configured at a rate above the set threshold. Default severity level: severe, color code: orange.
Typical Causes
The VRF is receiving packets from an area of the network for which it is not configured. This may indicate a misconfiguration or security problem.
Actions
Investigate the source of the illegal labels.
MPLS VRF High Illegal Label Rate Cleared

The VRF is receiving packets with labels for which it is not configured at a rate below the set threshold. Default severity level: information, color code: green.
Typical Causes
A misconfiguration has been corrected.
Actions
None.
A-12
Entuity
MPLS VRF Interface BGP Neighbor Disappeared
MPLS VRF Interface BGP Neighbor Disappeared

The interface has not received the BGP keep alive message within the set time. Default severity level: critical, color code: red.
Typical Causes
This may be, for example, because the router has gone, or the route to the router is down.
Actions
When the involved devices are managed by Entuity you view router status.
MPLS VRF Interface BGP Neighbor Newly Discovered

A new BGP neighbor has been added to the network. Default severity level: minor, color code: yellow.
Typical Causes
The administrator has added a new BGP neighbor to the network.
Actions
Where you have concerns over security check the new neighbor is expected.
MPLS VRF Non-operational

When the number of active interfaces associated with a VRF is zero, then the VRF is not operational. Default severity level: critical, color code: red.
Typical Causes
The interfaces associated with the VRF are down, or a change in configuration has removed all of the interfaces associated with the VRF.
Actions
Check the number of interfaces, and check the configuration. None.
MPLS VRF Operational

Indicates the VRF has transitioned from a non-operational to an operational state. Default severity level: information, color code: green.
Typical Causes
VRF has returned to an operational state, for example after the device has been rebooted.
A-13
Entuity
MPLS VRF Operational
Actions
None.
A-14
Glossary
Data Management Kernel (DMK)
The DMK supports Entuity's intelligent discovery function. It includes out of the box data models for a wide range of managed devices including hundreds of Ethernet switches and routers. These customizable data models define the attributes of each managed element, its possible dependencies in relation to other elements of the network, and the specific details to retrieve for each element. The DMK manages these data models and automatically applies updates and changes to the Entuity database schema.
Device Support Datasets

. Datasets are available through these types of vendor files, all have a .vendor extension. These vendor files are, listed in ascending order of priority:
newbin.vendor, which is created in entuity_home\etc when Entuity discovers devices with

sysoids for which there is not a device support dataset. These generic device support datasets should be considered temporary definitions, and only used until Entuity supply an appropriate vendor file. Device support datasets in newbin.vendor have the lowest priority when Entuity is determining which vendor device definition to use to manage a device type.
bin.vendor has the second lowest priority when Entuity is determining the source of
device information.Device support datasets in bin.vendor have the second lowest priority when Entuity is determining which of those available to use to manage a device type.
exotica vendor files are installed to entuity_home\etc\exotica. Exotica files are only used by Entuity when they are copied to entuity_home\etc, either manually or during Entuity
configuration, e.g. when selecting a module. Device support datasets in exotica vendor files have the highest priority when Entuity is determining which vendor device definition to use to manage a device type.These files use a simple naming convention, using the vanilla filename, with a plus sign in the filename and identifying name, e.g. SOLSERV+managed Host.vendor. During Entuity upgrades configure identifies and removes exotica files from the installation that are now part of the updated bin.vendor. vendinfo identifies the vendor device support datasets available to Entuity and the decisions made when more than one vendor file is available for a particular sysoid; which device support dataset Entuity uses to manage that device type (as identified through its sysoid).
Device Types
In Entuity every device has a type, which you can view through the web interface and Component Viewer. The device type is derived from its vendor file information, and helps to
Entuity MPLS Module Guide Glossary-1
Entuity
determine how Entuity manages a device. Device types include hubs, switches and routers. There are also two Unclassified device types Unclassified device types have two distinct roles:
Basic Management and Ping-only, is used for those devices Entuity has taken under
management at the Basic Management and Ping-only level.
Full Management, is used for those devices Entuity has taken under management at the
Full level but for which there is no vendor file information but Entuity can generate a suitable generic device type. These are uncertified devices.
Drop Box
Drop box acts as a temporary repository for objects, for example gauges, charts, links, device metrics, that you want to include to new reports, dashboards.
Entuity
Entuity is both the name of the network management software and the company producing it. Entuity software is designed for networks of any size and complexity, from the smallest, simplest corporate infrastructure to the largest multinational. Every customer can access the full functionality of our cornerstone solution, incorporating fault, performance and inventory management.
Essential Reports
Entuity provide a number of Essential Report templates that determine the basic report type, e.g. PVC Data Loss report. An Entuity administrator can use these templates to create new Essential Report definitions, setting when the report runs, which view it reports on, the page layout and the reports Prime Time. Entuity users that have access to the associated views, can then access the generated reports through Reports in the web UI or Component Viewer. These reports are currently available as pdf documents.
Eye of the Storm (EYE)

Until Entuity 12.5 the software was known as Eye of the Storm (EYE).
FEC
Forwarding Equivalence Class (FEC) is central concept to MPLS. An FEC is a set of packets that a single router forwards to the same next hop, using the same interface and with the same handling (e.g. queuing). The FEC is determined only once, at the ingress to an LSP, rather than at every router hop along the path.
Glossary-2
Entuity
Management Level
Every device under Entuity management is managed according to its management level, which is set when the device is added to Entuity but can be subsequently amended. Each managed device costs one license object. These are the management levels:
Full Management (all interfaces), Entuity manages all interfaces on the device. Full Management (management interfaces only), Entuity only manages the management
interface.
Full Management (no interfaces) Basic Management Entuity collects only basic system information and the full IP address
table via SNMP. This management level is used when Entuity does not have the appropriate device support dataset (vendor file), cannot generate an appropriate dataset or you only want the device placed under basic management. Entuity does not manage any ports or modules on the device.
Ping Only, devices only under ping management, SNMP data is not collected for these
devices.
Polling Engine
The Polling Engine (or Core Management Engine) is the set of processes within an Entuity server responsible for all general network management tasks excluding flow collection (e.g. network discovery, inventory, monitoring, event management). Administrators can enable/disable an Entuity servers Polling Engine through configure, a decision which should be made according to the role the administrator wants the server to perform in the management of the network.
Reachability
Availability Monitor sends an ICMP ping to the management IP address of managed devices, by default every two minutes. Devices that respond are considered reachable, those that do not respond, after the set number of retries, are considered unreachable. When Availability Monitor is not running, then the reachability of the device is Unknown for that period, although Entuity maintains the last known state of the device. Entuity maintains a record of device reachability, which is available through Entuity reports, e.g. Routing Summary, Switching Summary, Device Uptime and Reachability reports.
Reboot
Entuity uses the device sysuptime to calculate when the device was last rebooted, or more accurately when the device last came up after being rebooted.
Glossary-3
Entuity
Uptime
By default Entuity polls devices every five minutes, retrieving device sysuptime. Entuity checks as to whether the device has been continually up since the last poll, and modifies the devices uptime value accordingly. When sysuptime indicates the device has been down during the polling interval but is now up, from sysuptime alone Entuity cannot identify for how long the device was down. Entuity takes this unknown time, and adds fifty percent of it to the known uptime value, with the remaining fifty percent considered UNKNOWN. For example where sysuptime has a value of two minutes. Entuity cannot determine the state of the device over the first three minutes of the polling interval. Entuity adds ninety seconds to the sysuptime value, giving an uptime value of two hundred and ten seconds and records the device state as UNKNOWN for ninety seconds. Device uptime is visible through Component Viewer, and is used in many reports, e.g. Routing Summary, Switching Summary, KPI Device Availability / Uptime.
VRF (Virtual Routing and Forwarding)

VRF allows multiple instances of a routing table to co-exist within the same router at the same time. Because the routing instances are independent, the same or overlapping IP addresses can be used without conflicting with each other.
Glossary-4
Entuity
Index
A
Activating MPLS VPN 1-2 threshold setting 5-4 MPLS LSR Platform High Discard Rate (Lookup Failure) threshold setting 5-5 MPLS LSR Platform High Error Free Discard Rate (RX) threshold setting 5-5 MPLS LSR Platform High Fragmentation Rate threshold setting 5-5 MPLS VRF High Illegal Label Rate threshold setting 5-7
C
configure MPLS VPN 1-2
D
Device Management Level Glossary-3 Device Support Datasets Glossary-1, Glossary-3 Device Types Glossary-2 DMK Glossary-1
O
Open Trap Receiver 5-1
E
Entuity MPLS VPN availability 1-2 configure 1-2 configuring 1-2 licensing 1-2 Events supported in Entuity A-1
U
Uncertified Device Glossary-2 Unclassified Device Types Glossary-2
L
Licensing 1-2
M
MPLS LSR Interface High Discard Rate (Lookup Failure) threshold setting 5-2 MPLS LSR Interface High Error Free Discard Rate (RX) threshold setting 5-2 MPLS LSR Interface High Fragmentation Rate threshold setting 5-2 MPLS LSR Interface Low Bandwidth threshold setting 5-3 MPLS LSR Interface Low Buffer Space
Index-1

Entuity Module Mpls PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Entuity Module Mpls PDF

Transféré par

Droits d'auteur :

Formats disponibles

USER GUIDE

North America Headquarters

Copyright 2000 - 2012 Entuity. All rights reserved.

2 Managing Label Distribution Protocol (LDP)

3 Managing Label Switch Routers

4 Introducing MPLS VPN

5 Managing Entuity MPLS Events

6 Handling MPLS Traps

7 Reporting on Entuity MPLS

Entuity MPLS Module Guide

Entuity MPLS Module Guide

1 Introducing Entuity MPLS Module

Entuity MPLS Module Guide

Activating Entuity MPLS

Activating Entuity MPLS

Entuity MPLS Module Guide

2 Managing Label Distribution Protocol (LDP)

Entuity MPLS includes a series of key reports:

Using Report Server you can also create new reports.

Entuity MPLS Module Guide

Table 2-1 Device MPLS

Entuity MPLS Module Guide

Max Label Stack Depth LSR In Segment Traps Enabled

Entuity MPLS Module Guide

MPLS LDP Entity

Figure 2-1 Device MPLS

MPLS LDP Entity

Table 2-2 MPLS LDP Entity

Entuity MPLS Module Guide

MPLS LDP Entity

LDP Protocol Version Hop Count Limit

LDP TCP Discovery Port PVL Mismatch Traps Enabled

Hello Hold Time

Entuity MPLS Module Guide

MPLS LDP Entity

Table 2-2 MPLS LDP Entity

Figure 2-2 MPLS LDP Entity

MPLS LDP Entity Status

Entuity MPLS Module Guide

MPLS LDP Entity

Table 2-3 MPLS LDP Entity Status

Entuity MPLS Module Guide

MPLS LDP Peers

Figure 2-3 MPLS LDP Entity Status

MPLS LDP Peers

MPLS LDP Peers General

Table 2-5 MPLS LDP Peers General Details

Entuity MPLS Module Guide

MPLS LDP Peers

When set to: 0, loop detection for path vectors is disabled.

Table 2-5 MPLS LDP Peers General Details

Figure 2-4 MPLS LDP Peer General Details

MPLS LDP Label Ranges

Entuity MPLS Module Guide

MPLS LDP Peers

Figure 2-5 MPLS LDP Label Ranges

MPLS LDP Peer Status

Unknown Message Type Errors

Unknown TLV Errors

Entuity MPLS Module Guide

MPLS LDP Label Ranges

Figure 2-6 MPLS LDP Peer Status

MPLS LDP Label Ranges