cc/td/doc/product/cable/svc_ctrl/scappsbb
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Managing MPLS/VPN Support

How to Manage MPLS/VPN Support via SNMP

MPLS/VPN MIB Objects

MPLS/VPN Traps

How to Monitor MPLS/VPN Support via SCE Platform CLI

How to Display Subscriber Mappings

How to Clear Subscriber Mappings

How to Monitor Subscriber Counters

How to Monitor MPLS/VPN Counters

How to Monitor the PE Routers

How to Monitor Bypassed VPNs

How to Monitor Non-VPN Mappings

How to Manage MPLS/VPN Support via SM CLU

Options

How to Manage Individual Subscriber MPLS/VPN Mappings

How to Monitor Subscriber MPLS/VPN Mappings

How to Manage the SM Database MPLS/VPN Mappings


Managing MPLS/VPN Support


This module explains how to manage MPLS/VPN support.

How to Manage MPLS/VPN Support via SNMP 

How to Monitor MPLS/VPN Support via SCE Platform CLI 

How to Manage MPLS/VPN Support via SM CLU 

How to Manage MPLS/VPN Support via SNMP

SNMP support for MPLS/VPN auto-learn is provided in two ways:

MPLS/VPN MIB Objects 

MPLS/VPN Traps 

MPLS/VPN MIB Objects

The mplsVpnAutoLearnGrp MIB object group (pcubeSEObjs 17) contains information regarding MPLS/VPN auto-learning.

The objects in the mplsVpnAutoLearnGrp provide the following information:

maximum number of mappings

allowed current number of mappings

For more information, see the "Proprietary MIB Reference" in the Cisco Service Control Engine Software Configuration Guide.

MPLS/VPN Traps

There is one MPLS/VPN-related trap:

mplsVpnTotalHWMappingsThresholdExceeded (pcubeSeEvents 45)

To provide online notification of a resource deficiency, when the system reaches a level of 80% utilization of the hardware MPLS/VPN mappings, a warning message appears in the user log, and this SNMP trap is sent.

Both the warning and the trap are sent for each 100 mappings that are added after the threshold has been exceeded.

How to Monitor MPLS/VPN Support via SCE Platform CLI

The following sections describe functions you can perform using the SCE platform CLI:

How to Display Subscriber Mappings 

How to Clear Subscriber Mappings 

How to Monitor Subscriber Counters 

How to Monitor MPLS/VPN Counters 

How to Monitor the PE Routers 

How to Monitor Bypassed VPNs 

How to Monitor Non-VPN Mappings 

How to Display Subscriber Mappings

Use the following Viewer commands to display subscriber mappings. The following sections provide more information about the command displays:

How to Display All MPLS/VPN Mappings for a Specified Subscriber 

How to Display Only the number of MPLS/VPN Mappings for a Specified Subscriber 

How to Display the Name of the Subscriber who has a Specified Downstream Mapping 

How to Display the Mappings of Upstream Labels that Belong to Non-VPN Flows 

How to Display All MPLS/VPN Mappings for a Specified Subscriber


Step 1 From the SCE# prompt, type show interface linecard 0 subscriber name namemappings and press Enter.

The keyword " mappings" limits the output to the MPLS/VPN mapping information only. If the keyword is not used, all subscriber information is displayed, including the mappings.


Displaying All MPLS/VPN Mappings for a Specified Subscriber: Example

SCE# show interface linecard 0 subscriber name SubscriberX_1122334455 mappings Subscriber 'SubscriberX_1122334455' mappings: Downstream MPLS Mappings: PE-ID = 1.1.1.1 Mpls Label = 30 PE-ID = 1.1.1.1 Mpls Label = 256 PE-ID = 1.1.1.1 Mpls Label = 2 PE-ID = 1.1.1.1 Mpls Label = 3 PE-ID = 1.1.1.1 Mpls Label = 4 =====>Total Downstream Mappings: 5 Upstream MPLS Mappings: Upstream MPLS label: (MAC = 00:50:04:b9:c8:a0 BGP label = 0x14, LDP Label = 0xa) =====>Total Upstream Mappings: 1

How to Display Only the number of MPLS/VPN Mappings for a Specified Subscriber


Step 1 From the SCE# prompt, type show interface linecard 0 subscriber name namemappings |include Total and press Enter.


Displaying Only the number of MPLS/VPN Mappings for a Specified Subscriber: Example

SCE# show interface linecard 0 subscriber name SubscriberX_1122334455 mappings Subscriber 'SubscriberX_1122334455' mappings: =====>Total Downstream Mappings: 5 =====>Total Upstream Mappings: 1

How to Display the Name of the Subscriber who has a Specified Downstream Mapping


Step 1 From the SCE# prompt, type show interface linecard 0 subscriber mapping MPLS-VPN PE-ID pe-idBGP-label labeland press Enter.


How to Display the Mappings of Upstream Labels that Belong to Non-VPN Flows


Step 1 From the SCE# prompt, type show interface linecard 0 MPLS-VPN non-VPN-mappings and press Enter.


How to Clear Subscriber Mappings

Use this command to remove all learned upstream labels of a specified VPN subscriber.


Step 1 From the SCE(config if)# prompt, type no subscriber name namemapping upstream mpls all and press Enter.

This command, in effect, causes early label aging. Clearing the mappings allows relearning; labels will probably be quickly relearned after they have been cleared. Therefore, this command is useful when you want to update the mappings without waiting for the standard aging period.


How to Monitor Subscriber Counters

Use the following Viewer command to display subscriber counters, including those related to MPLS/VPN mappings.

About Subscriber Counters 

Monitoring Subscriber Counters: Example 

About Subscriber Counters

When MPLS/VPN subscribers are enabled, the following related counters appear in addition to the basic subscriber counters:

MPLS/VPN subscribers:

Current number of MPLS/VPN subscribers

Maximum number of MPLS/VPN subscribers

MPLS/VPN subscribers are also counted in the general subscribers counters, but the general subscribers maximum number does not apply to MPLS/VPN subscribers, which have a smaller maximum number.

MPLS/VPN mappings:

Current number of used MPLS/VPN mappings

Maximum number of MPLS/VPN mappings

Note that these values reflect the total number of mappings, not just the mappings used by MPLS/VPN subscribers. Bypassed VPNs also consume MPLS/VPN mappings.


Step 1 From the SCE# prompt, type show interface linecard 0 subscriber db counters and press Enter.


Monitoring Subscriber Counters: Example

SCE#show interface linecard 0 subscriber db counters Current values: =============== Subscribers: 2 used out of 99999 max. Introduced subscribers: 2. Anonymous subscribers: 0. Subscribers with mappings: 2 used out of 99999 max. IP mappings: 0 used.MPLS/VPN subscribers are enabled. MPLS/VPN mappings: 2 used out of 57344 max. MPLS/VPN subscribers: 2 used out of 2015 max. Subscribers with open sessions: 0. Subscribers with TIR mappings: 0. Sessions mapped to the default subscriber: 0. Peak values: ============ Peak number of subscribers with mappings: 2 Peak number occurred at: 14:56:55 ISR MON November 7 2005 Peak number cleared at: 13:29:39 ISR MON November 7 2005 Event counters: =============== Subscriber introduced: 2. Subscriber pulled: 0. Subscriber aged: 0. Pull-request notifications sent: 0. State notifications sent: 0. Logout notifications sent: 0. Subscriber mapping TIR contradictions: 0

Note The maximum number of subscribers when MPLS/VPN support is enabled is actually the maximum noted in the MPLS/VPN subscribers line (2015), rather than the maximum noted in the first line


How to Monitor MPLS/VPN Counters

Use the following Viewer command to display MPLS/VPN information.


Step 1 From the SCE# prompt, type show interface linecard 0 mpls vpn and press Enter.


Monitoring MPLS/VPN Counters: Example

SCE#show interface linecard 0 mpls vpn MPLS/VPN auto-learn mode is enabled. MPLS/VPN subscribers: 0 used out of 2015 max Total HW MPLS/VPN mappings utilization: 0 used out of 57344 max MPLS/VPN mappings are divided as follows: downstream VPN subscriber mappings: 0 upstream VPN subscriber mappings: 0 non-vpn upstream mappings: 0 downstream bypassed VPN mappings: 0 upstream bypassed VPN mappings: 0

How to Monitor the PE Routers

Use the following Viewer commands to monitor PE routers. These commands provide the following information:

How to Display the Configuration of all Currently Defined PE Routers 

How to Display the Configuration of a Specified PE Router 

How to Display the Configuration of all Currently Defined PE Routers


Step 1 From the SCE# prompt, type show interface linecard 0 MPLS VPN PE-Database and press Enter.


How to Display the Configuration of a Specified PE Router


Step 1 From the SCE# prompt, type show interface linecard 0 MPLS VPN PE-Database PE-ID pe-idand press Enter.


How to Monitor Bypassed VPNs

How to Display the Currently Bypassed VPNs 

How to Remove all Learned Bypassed VPNs 

How to Display the Currently Bypassed VPNs


Step 1 From the SCE# prompt, type show interface linecard 0 MPLS VPN Bypassed-VPNs and press Enter.


How to Remove all Learned Bypassed VPNs


Step 1 From the SCE# prompt, type clear interface linecard 0 MPLS VPN Bypassed-VPNs and press Enter.


How to Monitor Non-VPN Mappings

How to Display Non-VPN Mappings 

How to Remove all Learned non-VPN Mappings 

How to Display Non-VPN Mappings


Step 1 From the SCE# prompt, type s how interface linecard 0 MPLS VPN non-VPN-mappings and press Enter.


How to Remove all Learned non-VPN Mappings


Step 1 From the SCE# prompt, type clear interface linecard 0 MPLS VPN non-VPN-mappings and press Enter.


How to Manage MPLS/VPN Support via SM CLU

The SM CLU allows you to do the following:

Add, remove, and display MPLS/VPN mappings for a specified subscriber (VPN)

Clear all MPLS/VPN mappings from the SM database

Options

Use the p3subs utility to manage subscriber MPLS/VPN mappings.

The following options are available:

Subscriber-Name — The name assigned to the VPN when it was added as a subscriber.

RT@PE-IP — The mapping to be assigned to the subscriber/VPN. Multiple mappings can be specified using a comma.

RT = the route target of the VPN, specified using the ASN:n notation or the IP:n notation

Note that the Route Distinguisher may be specified rather than the route target

PE-IP = the loopback IP of the PE router connected to that VPN

How to Manage Individual Subscriber MPLS/VPN Mappings

p3subs


Step 1 From the shell prompt, type a command having the following general format: p3subs operation--subscriber= Subscriber-Name--mpls-vpn= RT@PE-IP[--additive-mapping]

The following tables present all the p3subs operations relevant to managing mappings.

Table 4-1 p3subs Mapping Operations

Operation

Description

--set

Add/update a subscriber. If the mapping exists, replaces the existing mapping, unless the additive-mapping option is used.

--remove-all-mappings

Removes all the mappings of specified subscriber.

--remove-mappings

Removes specified mapping of specified subscriber.


Table 4-2 p3subs Mapping Options

Options

Description

--additive-mapping

Adds the specified mappings to the existing ones (instead of replacing the existing mappings when this option is not used). Used with the set operation.



How to Monitor Subscriber MPLS/VPN Mappings


Step 1 From the shell prompt, type the following command: p3subs --show-all-mappings --subscriber= Subscriber-Name


How to Manage the SM Database MPLS/VPN Mappings

p3subsdb

Use the p3subsdb utility to remove the SM database MPLS/VPN mappings for all subscribers.


Step 1 From the shell prompt, type the following command: p3subsdb --remove-all-mpls-vpn



hometocprevnextglossaryfeedbacksearchhelp

Posted: Wed May 30 08:38:03 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.