7/27/2019 entuity_module_mpls[1].pdf
1/58
North America Headquarters4 Mount Royal Avenue
Suite 340
Marlborough, MA 01752
Tel: +1 508 357 6344
Fax: +1 508 357 6358
EMEA Headquarters9a Devonshire Square
London,
EC2M 4YN
Tel: +44 (0)20 7444 4800
Fax: +44 (0)20 7444 4808
USER GUI
www.entuity.com 0000-0125-PD053 entuity_module_mpls.rev1.fm
Entuity 12.5MPLS Module 2.0
The Entuity MPLS module supports management of MPLS by taking
a ti ered 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 exportedroute targets. Performance data is available at the virtual port level
(corresponding to a VRF).
7/27/2019 entuity_module_mpls[1].pdf
2/58
Copyright 2000 - 2012 Entuity. All rights reserved.
Entuity
The Entuity product and its related documentation are protected by copyright and distributed under licenses restrictiuse, copying, distribution, and decompilation. Unless you have negotiated with Entuity specific terms and conditiofor using its product and associated documentation, such use shall be governed by Entuity's standard licence termscopy 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 publicationany 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 PerspectiveandService DelivPerspective 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 serverentuity_home/licenseTerms/. A listing of these third party trademarks, references and software included with Entuityavailable through its web UI.
7/27/2019 entuity_module_mpls[1].pdf
3/58
7/27/2019 entuity_module_mpls[1].pdf
4/58
Entuity
Entuity MPLS Module Guide
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-2MPLS 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-7MPLS 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
7/27/2019 entuity_module_mpls[1].pdf
5/58
Entuity
Entuity MPLS Module Guide
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-13MPLS VRF Non-operational ......................................................A-13
MPLS VRF Operational .............................................................A-13
Glossary
Index
7/27/2019 entuity_module_mpls[1].pdf
6/58
Entuity
Entuity MPLS Module Guide v
Figures
Figure 2-1 Device MPLS .................................................................... 2-4Figure 2-2 MPLS LDP Entity .............................................................. 2-6Figure 2-3 MPLS LDP Entity Status ................................................... 2-8
Figure 2-4 MPLS LDP Peer General Details ...................................... 2-9Figure 2-5 MPLS LDP Label Ranges ................................................. 2-10Figure 2-6 MPLS LDP Peer Status .................................................... 2-11Figure 2-7 MPLS LDP Label Range MPLS LDP Peers ...................... 2-11Figure 2-8 MPLS LDP Label Range MPLS LDP Peers ...................... 2-12Figure 3-1 MPLS LSR ........................................................................ 3-3Figure 4-1 A Simple MPLS VPN Configuration ................................. 4-1Figure 4-2 MPLS VRF General .......................................................... 4-2Figure 4-3 VRF Route Targets ........................................................... 4-3Figure 4-4 VRF Status ....................................................................... 4-4Figure 4-5 MPLS Interface VRF Instances ........................................ 4-5
Figure 4-6 MPLS Interface VRF BGP Neighbors ............................... 4-5Figure 4-7 VRF on an Interface Instance ........................................... 4-6Figure 5-1 MPLS LSR Interface Error Event Thresholds ................... 5-2Figure 5-2 MPLS LSR Interface Event Thresholds ............................ 5-3Figure 5-3 MPLS LSR Platform Error Event Thresholds ................... 5-5Figure 5-4 MPLS VPN Illegal Label Rate Thresholds ........................ 5-7
7/27/2019 entuity_module_mpls[1].pdf
7/58
Entuity MPLS Module Guide 1-
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 take
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 earproblem resolution.
The next tier of Entuity MPLS is through management of LSRs. LSR label switching can occ
at either the interface or platform level, which Entuity MPLS can clearly identify. Key attribute
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 instance
of a routing table that co-exist within the same router at the same time. For example, port-
level application of VRFs and the association between VRFs, route distinguishers andimported 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, rou
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 require
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.
7/27/2019 entuity_module_mpls[1].pdf
8/58
7/27/2019 entuity_module_mpls[1].pdf
9/58
Entuity MPLS Module Guide 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 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 insigh
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.
7/27/2019 entuity_module_mpls[1].pdf
10/58
Entuity LDP Overview
Entuity MPLS Module Guide 2-
LDP Overview
LDP is a set of procedures by which one LSR informs another of the meaning of labels use
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. Th
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 Description
LSR ID The Label Switching Router (LSR) identifier is the first 4 bytes of th
Label Distribution Protocol (LDP) identifier.
Loop Detection Capability Indicates the LSR loop detection capability, and not necessarily it
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.
Other, loop detection is supported but by a method other tha
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.
Label Retention Mode When set to:
Conservative, the advertised label mappings are retained onl
if they will be used to forward packets, i.e. if label came from a
valid next hop.
Liberal, all advertised label mappings are retained whether
they are from a valid next hop or not.
Table 2-1 Device MPLS
7/27/2019 entuity_module_mpls[1].pdf
11/58
Entuity Device MPL
Entuity MPLS Module Guide 2-
LDP Session Traps Enabled When set to:
Enabled, the mplsLdpSessionUp and mplsLdpSessionDown
can be generated.
Disabled, the mplsLdpSessionUp and mplsLdpSessionDown
can not be generated. The default is Disabled.
Max Label Stack Depth Maximum stack depth supported by this LSR.
LSR In Segment Traps
Enabled
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.
LSR Out Segment Traps
Enabled
Traps indicating outgoing MPLS segments (labels).
LSR Cross Connect Traps
Enabled
Traps indicating changes to the cross-connect table, e.g. the
association between incoming and outgoing segments (labels).
Number of LSR Ports Number of ports.
Number of Configured VRFs Number of VRFs configured on the router.
Number of Active VRFs Number of configured VRFs currently in use.
Number of Interfaces
Connected to VRFs
Number of interfaces connected to all of the routers VRFs.
VPN Notifications Enabled Must be set to Enable for the router to send MPLS VPN SNMP
notifications.
VPN Global Route Limit Number of routes allowed on the router, which is only limited by th
amount available for the router.
Attribute Description
Table 2-1 Device MPLS
7/27/2019 entuity_module_mpls[1].pdf
12/58
Entuity MPLS LDP Entit
Entuity MPLS Module Guide 2-
Figure 2-1 Device MPLS
MPLS LDP Entity
MPLS LDP Entity
Attribute Description
Label Retention Mode 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 anmplsLdpFailedInitSessionThresholdExceeded when
the number of session initialization messages sent
exceeds this threshold.
Table 2-2 MPLS LDP Entity
7/27/2019 entuity_module_mpls[1].pdf
13/58
Entuity MPLS LDP Entit
Entuity MPLS Module Guide 2-
Label Distribution Method 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 Version number of the protocol. When set to 0, this
indicates that the version of the protocol is unknown.
Hop Count Limit Maximum allowable number of hops permitted,
applicable when Loop Detection Capabilitymust be set t
either Hop Count And Path Vector or Hop Count.
LDP TCP Discovery Port LDP TCP port 646 used for establishing transport
connection.
PVL Mismatch Traps Enabled The mplsLdpPathVectorLimitMismatch notification is
generated when there is a mismatch in the Path VectorLimits 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.
Hello Hold Time 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.
Is Targeted Peer When set to:
true, the LDP entity uses targeted peers
false the LDP entity does not uses targeted peers.
Targeted Peer Address Address used for the Extended Discovery.
Maximum PDU Length 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.
Keep Alive Hold Time Value which is the proposed keep alive hold timer for thi
LDP Entity.
LDP UDP Discovery Port UDP port, by default 646, used with the discovery
message.
Attribute Description
Table 2-2 MPLS LDP Entity
7/27/2019 entuity_module_mpls[1].pdf
14/58
Entuity MPLS LDP Entit
Entuity MPLS Module Guide 2-
Figure 2-2 MPLS LDP Entity
MPLS LDP Entity Status
:
Path Vector Limit 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 Limitto have effect the devices Loop
Detection Capabilitymust be set to either Hop Count
And Path Vector or Path Vector.
Attribute Description
Admin 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
Table 2-3 MPLS LDP Entity Status
Attribute Description
Table 2-2 MPLS LDP Entity
7/27/2019 entuity_module_mpls[1].pdf
15/58
Entuity MPLS LDP Entit
Entuity MPLS Module Guide 2-
Oper Status Operational status of the LDP entity, which can be:
Unknown, this should only be a transitional state.
Enabled
Disabled
Attempted Sessions Total number of attempted sessions for this LDP Entity.
Rejects (No Hello) count of the Session Rejected/No Hello Error Notification
Messages sent or received by the LDP entity.
Rejects (Bad Ad.) A count of the Session Rejected/Parameters Advertisement Mode
Error Notification Messages sent or received by this LDP Entity.
Rejects (PDU Length) A count of the Session Rejected/Parameters Max Pdu Length Erro
Notification Messages sent or received by this LDP Entity.
Rejects (LR) A count of the Session Rejected/Parameters Label Range
Notification. Notification Messages sent or received by this LDP
Entity.
Bad Identifier Number of Bad LDP Identifier Fatal Errors detected by thesession(s) (past and present) associated with this LDP Entity.
Bad PDU Length, Number of Bad PDU Length Fatal Errors detected by the session(s
(past and present) associated with this LDP Entity.
Length Errors Number of Bad Message Length Fatal Errors detected by the
session(s) (past and present) associated with this LDP Entity.
TLV Length Errors Number of Bad TLV Length Fatal Errors detected by the session(s
(past and present) associated with this LDP Entity.
Bad TLV Values Number of Malformed TLV Value Fatal Errors detected by the
session(s) (past and present) associated with this LDP Entity.
Keep Alive Timeouts Number of Session Keep Alive Timer Expired Errors detected by th
session(s) (past and present) associated with this LDP Entity.Shutdowns Received Number of Shutdown Notifications received related to session(s)
(past and present) associated with this LDP Entity.
Shutdowns Sent Number of Shutdown Notifications sent related to session(s) (pas
and present) associated with this LDP Entity.
Rejected Sessions Delta Change in the number of rejected sessions between the two most
recent pollings.
Error Delta Change in the number of errors between the two most recent
pollings.
Shutdowns Received Delta Change in the number of shutdowns received between the two
most recent pollings.
Shutdowns Sent Delta, Change in the number of shutdowns sent between the two mostrecent pollings.
Attribute Description
Table 2-3 MPLS LDP Entity Status
7/27/2019 entuity_module_mpls[1].pdf
16/58
Entuity MPLS LDP Peer
Entuity MPLS Module Guide 2-
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.:
MPLS LDP Peers General
This tab lists discovery details of the remote entity of the LDP peer:
Attribute Description
General Discovery details, for example advertised IP address
MPLD LDP Label Ranges Supported label ranges
MPLS LDP Entity Details of the remote entity
Peer Status Key status metrics.
Table 2-4 Remote Peer Details
Attribute Description
Path Vector Loop Detection Indicates whether loop detection based on path vectors is
disabled or enabled for this LDP peer.
Advertised IP IP address advertised to its LDP peers.
Table 2-5 MPLS LDP Peers General Details
7/27/2019 entuity_module_mpls[1].pdf
17/58
Entuity MPLS LDP Peer
Entuity MPLS Module Guide 2-
Figure 2-4 MPLS LDP Peer General Details
MPLS LDP Label Ranges
:
Path Vector Hop Limit 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 Limitto have effect the devices LoopDetection Capabilitymust be set to either Hop Count And Path
Vector or Path Vector.
Label Distribution Method 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 FEC-label
bindings to a peer in response to specific requests from the
peer for a label for the FEC.
Attribute Description
Name Name of the label range.
IF Index Interface index of the outgoing label of this LSP.Maximum Label Upper boundary of the label range.
Minimum Label Lower boundary of the label range.
Table 2-6 MPLS LDP Label Ranges
Attribute Description
Table 2-5 MPLS LDP Peers General Details
7/27/2019 entuity_module_mpls[1].pdf
18/58
Entuity MPLS LDP Peer
Entuity MPLS Module Guide 2-1
Figure 2-5 MPLS LDP Label Ranges
MPLS LDP Peer Status
An LDP peer is a remote LDP entity.
Attribute Description
Status Polled state of the session, i.e. Non existent, Initialized, Ope
receive, Open sent and Operational.
LDP Version Version number of the protocol. When set to 0, this indicate
that the version of the protocol is unknown.
Peer Max PDU Length 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.
Unknown Message Type Errors Number of Unknown Message Type Errors detected during
this session.
Discontinuities in the value of this counter can occur at re-
initialization of the management system, and at other times
as indicated by the value of
mplsLdpSeeionDiscontinuityTime.
Unknown TLV Errors Number of Unknown TLV Errors detected during this
session.
Discontinuities in the value of this counter can occur at re-
initialization of the management system, and at other times
as indicated by the value of
mplsLdpSeeionDiscontinuityTime.
Unknown Message Type Error Delta Difference in the number of Unknown Message Type Errors
detected between the last two pollings.
Table 2-7 MPLS LDP Peer Status
7/27/2019 entuity_module_mpls[1].pdf
19/58
Entuity MPLS LDP Label Range
Entuity MPLS Module Guide 2-1
Figure 2-6 MPLS LDP Peer Status
MPLS LDP Label Ranges
MPLS LDP Label Range MPLS LDP Peers
This tab shows the configuration of the remote entity:
Unknown TLV Error Delta Difference in the number of Unknown TLV Errors detected
between the last two pollings.
Attribute Description
Name Name of the MPLS LDP peer.
Path Vector Loop Detection Indicates whether loop detection based on path vectors is
disabled or enabled for this LDP peer.
Advertised IP IP address advertised to its LDP peers.
Path Vector Hop Limit 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 Limitto have effect the devices LooDetection Capabilitymust be set to either Hop Count And
Path Vector or Path Vector.
Figure 2-7 MPLS LDP Label Range MPLS LDP Peers
Attribute Description
Table 2-7 MPLS LDP Peer Status
7/27/2019 entuity_module_mpls[1].pdf
20/58
Entuity MPLS LDP Label Range
Entuity MPLS Module Guide 2-1
Figure 2-8 MPLS LDP Label Range MPLS LDP Peers
Label Distribution Method 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 FEC-label bindings to a peer in response to specific request
from the peer for a label for the FEC.
Attribute Description
Figure 2-7 MPLS LDP Label Range MPLS LDP Peers
7/27/2019 entuity_module_mpls[1].pdf
21/58
Entuity MPLS Module Guide 3-
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 Description
Min label (RX) Minimum value of an MPLS label that this LSR is willing to
receive on this interface.
Max label (RX) Maximum value of an MPLS label that this LSR is willing to
receive on this interface.
Min label (TX) Minimum value of an MPLS label that this LSR is willing to
send on this interface.
Max label (TX) Maximum value of an MPLS label that this LSR is willing to
send on this interface.
Usable Bandwidth 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.
Available Bandwidth 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 inmplsInterfaceTotalBandwidth. This variable is not applicable
when applied to the interface with index 0.
Allocated Space Total amount of buffer space allocated for this interface. This
variable is not applicable when applied to the interface with
index 0.
Available Space Total amount of buffer space available for this interface. This
variable is not applicable when applied to the interface with
index 0.
Table 3-1 MPLS LSR
7/27/2019 entuity_module_mpls[1].pdf
22/58
Entuity MPLS LS
Entuity MPLS Module Guide 3-
Label Space Either set to per Platform(0) or per Interface(1). When the
value is:
perInterface(1) bit is set then the value ofMin 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 ofMin
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) Number of inbound labels used.
Packets (RX) Number of labelled packets that have been received on this
interface.
Error Free Discards (e.g. insufficient
buffer)
Number of outbound labelled packets, which were chosen t
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.
Labels In Use (Tx) Number of top-most labels in the outgoing label stacks that
were in use on this interface.
Packets (TX) Number of labelled packets that have been transmitted on
this interface.
Error Free Discards (Tx) Number of outbound labelled packets, which were chosen t
be discarded even though no errors had been detected to
prevent their being transmitted.
One possible reason for discarding such a labelled packetcould be to free up buffer space.
Packets Fragmented Number of outgoing MPLS packets that required
fragmentation before transmission on this interface.
Rx Discard No Error Pkt Rate Difference between two contiguous inbound Error Free
Discardssampled values, as a per second average.
Tx Discard No Error Pkt Rate Difference between two contiguous outbound Error Free
Discardssampled values, as a per second average.
Rx Discard Lookup Failure Pkt Rate Difference between two contiguous inbound Packets (Rx)sampled values, as a per second average.
TX Pkt Fragmentation Rate Difference between two contiguous outbound Packets
Fragmentedsampled values, as a per second average.
Attribute Description
Table 3-1 MPLS LSR
7/27/2019 entuity_module_mpls[1].pdf
23/58
Entuity MPLS LS
Entuity MPLS Module Guide 3-
Figure 3-1 MPLS LSR
7/27/2019 entuity_module_mpls[1].pdf
24/58
Entuity MPLS Module Guide 4-
4 Introducing MPLS VPN
A network with an MPLS backbone provides the flexibility to deliver high value VPN service
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 differentaddressing 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
VPNs contain IP prefixes. Entuity can monitor the performance of VRF instances through
monitoring the success or failure of its route target distribution.
Figure 4-1 A Simple MPLS VPN Configuration
MPLS VRF General
Entuity gathers MPLS configuration data from every MPLS enabled port.
Attribute Description
VRF Name VRF name.VRF Description Description of the VRF, for example its purpose.
VRFHigh-Water Route Threshold Denotes high-level water marker for the number of routeswhich this VRF may hold.
VRFMid-Water Route Threshold Denotes mid-level water marker for the number of routes whicthis VRF may hold.
VRF Route Distinguisher Route Distinguisher that makes the VRF unique, distinguishin
between overlapping addresses in the VRF.
VRF Maximum Routes Maximum number of routes on the VRF. It must be less than o
equal to the maximum possible number of routes unless it is
set to 0.
Table 4-1 MPLS VRF General
CE CEPE PE
VPN Site
1VPN Site
2
MPLS Tunnel
7/27/2019 entuity_module_mpls[1].pdf
25/58
Entuity MPLS Route Target
Entuity MPLS Module Guide 4-
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 Description
Name Name of the route target distribution policy.
Route Target Route target identifier.
Description Description of the route target
Type Import/export distribution policy for the route target, i.e. impor
export and import and export. The configuration of the VPNtopology is determined through the Type setting of VRFs.
Table 4-2 MPLS Route Targets
7/27/2019 entuity_module_mpls[1].pdf
26/58
Entuity MPLS VRFs Statu
Entuity MPLS Module Guide 4-
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 VR
instances.MPLS
Attribute Description
Oper status Operational status of the VRF. When it is set to:
Up, one or more interfaces associated with the VRF is up
Down, the are no interfaces associated with the VRF, or al
of the interfaces associated to the VRF are down.
Active Interface Number of interfaces associated with the VRF that are up.
Associated Interface Number of interfaces associated with the VRF, including both
active and inactive interfaces.
Routes Added Number of routes added over the lifetime of the VRF.
Routes Deleted Number of routes deleted over the lifetime of the VRF.
Routes Number of routes currently used by this VRF.
Illegal labels Number of illegal label violations on the interface. These may
indicate MPLS misconfiguration or an attempt to breach
network security.
Illegal labels Threshold Illegal label violation threshold.
Illegal label Violation Rate Number of illegal label violations per second.
Table 4-3 MPLS VRFs Status
7/27/2019 entuity_module_mpls[1].pdf
27/58
Entuity MPLS Interface VRF Instances Genera
Entuity MPLS Module Guide 4-
Figure 4-4 VRF Status
MPLS Interface VRF Instances General
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 Description
Name Identifies the VRF and its interface.
MPLS VRF Interface VRF name.
VRFName VRF name.Classification The VPN classification which denotes the context of the link,
e.g. carrier-of-carrier's, enterprise, inter-provider.
Edge Type Either the provider edge (PE) or customer edge (CE) router.
RDP VRF Interface Route Distribution Protocol across the PE-CE link
which can be:
dummy
none
BGP
OSPF
RIP
ISIS
other
Table 4-4 MPLS Interface VRF Instances
7/27/2019 entuity_module_mpls[1].pdf
28/58
Entuity MPLS Interface VRF Instances Genera
Entuity MPLS Module Guide 4-
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.
Figure 4-6 MPLS Interface VRF BGP Neighbors
Attribute Description
Name Resolved name, or IP address of the device.
Role Role played by this EBGP neighbor with respect to this VRF,
e.g. CE.
Address IP address of the EBGP neighbor.
Table 4-5 MPLS Interface VRF BGP Neighbors
7/27/2019 entuity_module_mpls[1].pdf
29/58
Entuity MPLS Interface VRF Instances Genera
Entuity MPLS Module Guide 4-
VRF on an Interface Instance
This tab details the MPLS VRF associated with the virtual interface:
Figure 4-7 VRF on an Interface Instance
Attribute Description
Name VRF name.
VRF Description Description of this VRF, e.g its purpose.
VRF High-Water Routes
Threshold
High-level water marker for the number of routes which this VR
may hold.
VRF Mid-Water Routes Threshold Mid-level water marker for the number of routes which this VR
may hold.
VRF Route Distinguisher Route distinguisher for this VRF.
VRF Maximum Routes Maximum number of routes, summed across all VRFs, which
the device allows. When set to 0, this indicates that the device i
unable to determine the absolute maximum, and you could
potentially set a configured maximum greater than that allowe
by the device.
VRF Name Name of the VRF.
Table 4-6 VRF on an Interface Instance
7/27/2019 entuity_module_mpls[1].pdf
30/58
Entuity MPLS Module Guide 5-
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 individualplatform, 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 metric
Inbound lookup failure discards
Outbound lookup failure discards
LSR inbound discard no error rate 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 availab
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:
These events are cleared from either after ten minutes have elapsed or when Entuity raises
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 th
particular metric. This example sets thresholds against a particular interface:
Attribute Description
Source Identifies the device and MPLS interface against which the event is raised.
Impacted 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
7/27/2019 entuity_module_mpls[1].pdf
31/58
Entuity Managing MPLS LSR Interface Error Event
Entuity MPLS Module Guide 5-
1) In Component Viewer navigate to the required interface and from the context menu seleThreshold 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.
3) Select:
Reset to cancel your unapplied changes and leave you in the dialog.
Cancel to remove your unapplied changes and close the dialog.
Threshold Description
LSR High Rx Label
Lookup Failure Rate
Select Enabled to turn on the threshold, and accept or amend the defau
failure rate of 10 per second. A failure rate value greater than this threshol
and Entuity raises an MPLS LSR Interface High Discard Rate (LookupFailure) event.
LSR High Tx Label
Lookup Failure Rate
Select Enabled to turn on the threshold, and accept or amend the defau
failure rate of 10 per second. A failure rate value greater than this threshol
and Entuity raises an MPLS LSR Interface High Discard Rate (Lookup
Failure) event.
LSR High Rx Discard
No Error Rate
Select Enabled to turn on the threshold, and accept or amend the defau
failure rate of 10 per second. A failure rate value greater than this threshol
and Entuity raises an MPLS LSR Interface High Error Free Discard Rate
(RX) event.
LSR High Tx
Fragmentation Rate
Select Enabled to turn on the threshold, and accept or amend the defau
failure rate of 10 per second. A failure rate value greater than this threshol
and Entuity raises an MPLS LSR Interface High Fragmentation Rate even
Table 5-2 MPLS Thresholds
7/27/2019 entuity_module_mpls[1].pdf
32/58
Entuity Managing MPLS LSR Interface Error Event
Entuity MPLS Module Guide 5-
Apply to write the changes to the database and close the dialog.
OKto 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 ThresholdsSetting 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 threshold is the same, regardless of the
particular metric. This example sets thresholds against a particular interface:
1) In Component Viewer navigate to the required interface and from the context menu seleThreshold Settings. Entuity displays the Threshold Settings dialog.
Figure 5-2 MPLS LSR Interface Event Thresholds
2) Select the MPLS LSR I/f tab.
Threshold Description
LSR Low
Bandwidthe(kbps)
Select Enabled to turn on the threshold, and accept or amend the defau
failure rate of 15 kilobytes per second. A failure rate value greater than thi
threshold and Entuity raises an MPLS LSR Interface Low Bandwidth even
Table 5-3 MPLS LSR Interface
7/27/2019 entuity_module_mpls[1].pdf
33/58
Entuity Managing MPLS LSR Platform Error Event
Entuity MPLS Module Guide 5-
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.
OKto 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.
Managing MPLS LSR Platform Error EventsEntuity monitors interface error platform, with events being raised against these metrics:
Inbound Lookup Failure Discards
Outbound Packet Fragmentation
LSR Inbound Discard No Error Rate
LSR Outbound Discard No Error Rate.
By default these events are not enabled. You can enable them and set the threshold level a
the Entuity server root level or platform,
Identification of what the event is raised against is through the events data fields:
These events are cleared from either after ten minutes have elapsed, or when Entuity raises
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:
Global level, i.e. using the Global View on the Entuity server.
Component level, e.g. selecting a particular interface.
LSR Low Buffer Space Select Enabled to turn on the threshold, and accept or amend the defau
failure rate of 1024 bytes per second. A failure rate value greater than thi
threshold and Entuity raises an MPLS LSR Interface Low Buffer Space
event.
Attribute Description
Source Identifies the device and MPLS interface against which the event is raised
Impacted 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
Threshold Description
Table 5-3 MPLS LSR Interface
7/27/2019 entuity_module_mpls[1].pdf
34/58
Entuity Managing MPLS LSR Platform Error Event
Entuity MPLS Module Guide 5-
The process for setting an MPLS LSR platform error threshold is the same, regardless of th
particular metric. This example sets thresholds against a particular device:
1) In Component Viewer navigate to the required interface and from the context menu seleThreshold Settings. Entuity displays the Threshold Settings dialog.
Figure 5-3 MPLS LSR Platform Error Event Thresholds
2) Select the MPLS LSR Platform Error tab.
3) Select:
Threshold Description
LSR High Rx LabelLookup Failure Rate
Select Enabled to turn on the threshold, and accept or amend the defaufailure rate of 10 per second. A failure rate value greater than this thresho
and Entuity raises an MPLS LSR Platform High Discard Rate (Lookup
Failure) event.
LSR High Tx Label
Lookup Failure Rate
Select Enabled to turn on the threshold, and accept or amend the defau
failure rate of 10 per second. A failure rate value greater than this thresho
and Entuity raises an MPLS LSR Platform High Discard Rate (Lookup
Failure) event.
LSR High Rx Discard
No Error Rate
Select Enabled to turn on the threshold, and accept or amend the defau
failure rate of 10 per second. A failure rate value greater than this thresho
and Entuity raises an MPLS LSR Platform High Error Free Discard Rate
(RX) event.
LSR High Tx
Fragmentation Rate
Select Enabled to turn on the threshold, and accept or amend the defau
failure rate of 10 per second. A failure rate value greater than this thresho
and Entuity raises an MPLS LSR Platform High Fragmentation Rate even
Table 5-5 MPLS LSR Platform Error
7/27/2019 entuity_module_mpls[1].pdf
35/58
Entuity Managing MPLS VPN Event
Entuity MPLS Module Guide 5-
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.
OKto 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.
Managing MPLS VPN Events
Entuity monitors VPN security and configuration, with events being raised when the VPN hig
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.
Setting MPLS VPN ThresholdsSetting 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 selecThreshold Settings. Entuity displays the Threshold Settings dialog.
Attribute Description
Source Identifies the device and MPLS interface against which the event is raised
Impacted 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
7/27/2019 entuity_module_mpls[1].pdf
36/58
Entuity Managing MPLS VPN Event
Entuity MPLS Module Guide 5-
Figure 5-4 MPLS VPN Illegal Label Rate Thresholds
2) Select the MPLS VPN tab.
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.
OKto 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.
Threshold Description
VPN High Illegal Label
Rate
Select Enabled to turn on the threshold, and accept or amend the defau
failure rate of 10 per second. A failure rate value greater than this thresho
and Entuity raises an MPLS VRF High Illegal Label Rate event.
Table 5-7 MPLS VPN
7/27/2019 entuity_module_mpls[1].pdf
37/58
Entuity MPLS Module Guide 6-
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 theEntuity 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). Yo
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
7/27/2019 entuity_module_mpls[1].pdf
38/58
Entuity Setting up the Open Trap Receive
Entuity MPLS Module Guide 6-
MPLS-VPN-MIB.my.
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 fromentuity_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-to
2008sp2\lib\mibs\MPLS-LDP-STD-MIB.my.
Adding trap mplsLdpInitSessionThresholdExceeded with oi
.1.3.6.1.2.1.10.166.4.0.1
Adding trap mplsLdpPathVectorLimitMismatch with oi
.1.3.6.1.2.1.10.166.4.0.2
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.
h
7/27/2019 entuity_module_mpls[1].pdf
39/58
Entuity MPLS Module Guide 7-
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/27/2019 entuity_module_mpls[1].pdf
40/58
Entuity MPLS Module Guide A-
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 associate
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.
7/27/2019 entuity_module_mpls[1].pdf
41/58
Entuity MPLS LDP Entity Operationa
Entuity MPLS Module Guide A-
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 distributio
method, timer values are not acceptable. The LSR responds by sending a Session Rejecte
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.
7/27/2019 entuity_module_mpls[1].pdf
42/58
Entuity MPLS LDP Entity Shutdown Notifications Receive
Entuity MPLS Module Guide A-
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.
7/27/2019 entuity_module_mpls[1].pdf
43/58
Entuity MPLS LDP Entity Shutdown Notifications Sent Cleare
Entuity MPLS Module Guide A-
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 hav
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 problem
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 indicata security failure.
7/27/2019 entuity_module_mpls[1].pdf
44/58
Entuity MPLS LDP Peer Non-operationa
Entuity MPLS Module Guide A-
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 CausesThe 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.
7/27/2019 entuity_module_mpls[1].pdf
45/58
Entuity MPLS LDP Peer Unknown Message Type
Entuity MPLS Module Guide A-
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.
ActionsCheck 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.
ActionsNone.
MPLS LSR Interface High Discard Rate (Lookup Failure)
Indicates the number of labelled packets that have been received on this interface and wer
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.
7/27/2019 entuity_module_mpls[1].pdf
46/58
Entuity MPLS LSR Interface High Discard Rate (Lookup Failure) Cleare
Entuity MPLS Module Guide A-
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 CausesThe 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 thLSR discarded is above the set threshold.
Default severity level: severe, color code: orange.
Typical Causes
The LSR may be short of buffer space.
7/27/2019 entuity_module_mpls[1].pdf
47/58
Entuity MPLS LSR Interface High Error Free Discard Rate (TX) Cleare
Entuity MPLS Module Guide A-
Actions
Check the LSR configuration, there may also be low buffer events raised for the device.
MPLS LSR Interface High Error Free Discard Rate (TX) Cleared
Indicates the interfaces discard rate of error free packets has transitioned to below the setthreshold.
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 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 ca
be transmitted. Fragmentation is a resource intensive process and can adversely affect LS
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.
7/27/2019 entuity_module_mpls[1].pdf
48/58
Entuity MPLS LSR Interface Low Bandwidt
Entuity MPLS Module Guide A-
MPLS LSR Interface Low Bandwidth
Indicates the total amount of available bandwidth available on this interface is below the se
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 s
threshold. Available buffer space is calculated as the difference between the amount of buffspace 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 ClearedIndicates 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.
7/27/2019 entuity_module_mpls[1].pdf
49/58
Entuity MPLS LSR Platform High Discard Rate (Lookup Failure
Entuity MPLS Module Guide A-1
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 th
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
The LSR may be short of buffer space.
Actions
Check the LSR configuration, there may also be low buffer events raised for the device.
7/27/2019 entuity_module_mpls[1].pdf
50/58
Entuity MPLS LSR Platform High Error Free Discard Rate (RX) Cleare
Entuity MPLS Module Guide A-1
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 CausesThe 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 Platform High Error Free Discard Rate (TX)
The rate per second of outbound labelled packets, for which no error was detected, that th
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 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
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 Platform High Fragmentation RateThis 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.
7/27/2019 entuity_module_mpls[1].pdf
51/58
Entuity MPLS LSR Platform High Fragmentation Rate Cleare
Entuity MPLS Module Guide A-1
Typical Causes
An interface capacity mismatch causes incoming packets to be fragmented before they ca
be transmitted. Fragmentation is a resource intensive process and can adversely affect LS
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 se
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. Thi
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 se
threshold.
Default severity level: information, color code: green.
Typical Causes
A misconfiguration has been corrected.
Actions
None.
7/27/2019 entuity_module_mpls[1].pdf
52/58
Entuity MPLS VRF Interface BGP Neighbor Disappeare
Entuity MPLS Module Guide A-1
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 CausesThe interfaces associated with the VRF are down, or a change in configuration has remove
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.
7/27/2019 entuity_module_mpls[1].pdf
53/58
Entuity MPLS VRF Operationa
Entuity MPLS Module Guide A-1
Actions
None.
7/27/2019 entuity_module_mpls[1].pdf
54/58
Entuity MPLS Module Guide Glossary-
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, i
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 applie
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 wisysoids 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 priorit
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 usedby Entuity when they are copied to entuity_home\etc, either manually or during Entuityconfiguration, 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
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 decision
made when more than one vendor file is available for a particular sysoid; which devicesupport 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
7/27/2019 entuity_module_mpls[1].pdf
55/58
Entuity
Entuity MPLS Module Guide Glossary-
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 thFull 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 th
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 typ
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 pag
layout and the reports Prime Time.
Entuity users that have access to the associated views, can then access the generatedreports 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 packet
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.
7/27/2019 entuity_module_mpls[1].pdf
56/58
Entuity
Entuity MPLS Module Guide Glossary-
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 manageme
interface.
Full Management (no interfaces)
Basic Management Entuity collects only basic system information and the full IP addres
table via SNMP. This management level is used when Entuity does not have the
appropriate device support dataset (vendor file), cannot generate an appropriate datase
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 device
by default every two minutes. Devices that respond are considered reachable, those that d
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.
7/27/2019 entuity_module_mpls[1].pdf
57/58
Entuity
Entuity MPLS Module Guide Glossary-
Uptime
By default Entuity polls devices every five minutes, retrieving device sysuptime. Entuitychecks as to whether the device has been continually up since the last poll, and modifies th
devices uptime value accordingly.
Whensysuptime 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. Entuitytakes 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 otwo 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 uptimevalue of two hundred and ten seconds and records the device state as UNKNOWN for nine
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 sam
time. Because the routing instances are independent, the same or overlapping IP addresse
can be used without conflicting with each other.
7/27/2019 entuity_module_mpls[1].pdf
58/58
Entuity
Index
A
Activating MPLS VPN 1-2
C
configure
MPLS VPN 1-2
D
Device Management Level Glossary-3
Device Support Datasets Glossary-1, Glossary-3
Device Types Glossary-2
DMKGlossary-1
E
Entuity MPLS VPN
availability 1-2
configure 1-2
configuring 1-2
licensing 1-2
Events
supported in EntuityA-1
LLicensing 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 Ratethreshold setting 5 2
threshold setting 5-4
MPLS LSR Platform High Discard Rate (Look
Failure)threshold setting 5-5
MPLS LSR Platform High Error Free Discard Ra
(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
O
Open Trap Receiver 5-1
U
Uncertified Device Glossary-2
Unclassified Device Types Glossary-2