Log in
|
How to Buy
|
Contact Us
|
United States (Change)

## Choose Country

### North America

- United States

### Europe

- Deutschland - Germany
- España - Spain
- France
- Italia - Italy
- Россия - Russia
- United Kingdom

### Asia Pacific

- Asean Region (Vietnam, Indonesia, Singapore, Malaysia)
- Australia
- 中国 - China
- India
- 日本 - Japan
- 대한민국 - Korea
- 台灣 - Taiwan

Remember my choice

# Technical Documentation

Download Software
Research a Problem
Case Management
Contract & Product Management
Technical Documentation
Documentation Archive
Enterprise MIBs
File Format Help
Glossary
Portable Libraries
End-of-Life Products
Contact Support
Guidelines and Policies
Security Resources
Rate and give feedback: Feedback Received. Thank You!
Rate and give feedback:
This document helped resolve my issue. Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:
E-mail:

## Related Documentation

- Configuring MPLS LSPs for L2VPNs and Configuring MPLS LSPs for VPLS in the JunosE BGP and MPLS Configuration Guide

# mpls

#### Syntax

To enable MPLS on a virtual router in Global Configuration mode, or to create an MPLS major interface in Interface Configuration mode:

[ no ] mpls

To modify the subscriber policy for MPLS packets in Subscriber Policy Configuration mode:

mpls { permit | deny }

no mpls

#### Release Information

Command introduced before JunosE Release 7.1.0.

#### Description

In Global Configuration mode, creates MPLS in the current virtual router. By default, MPLS does not exist in a VR. The no mpls version removes MPLS from the VR, and additionally removes all MPLS major interfaces, MPLS shim interfaces, MPLS load-balancing groups, MPLS minor interfaces, and MPLS forwarding tables from the VR.

In Interface Configuration mode, creates an MPLS major interface stacked on the current layer 2 interface, and automatically enables MPLS in the current VR if it has not already been enabled. If the MPLS major interface already exists, no action is taken and no message is generated. An error message is generated if you issue the command for a layer 2 interface that does not support MPLS major interfaces. You cannot enable MPLS on a loopback interface. The no mpls version removes the MPLS major interface.

In Subscriber Policy Configuration mode, modifies the subscriber policy for MPLS to define whether the subscriber (client) interfaces that belong to a bridge group or to a VPLS instance forward (permit) or filter (deny) MPLS packets. The no version restores the default value, permit MPLS packets.

In Subscriber Policy Configuration mode, you cannot change the default subscriber policy values for trunk (server) interfaces that belong to a bridge group or to a VPLS instance. You also cannot change the default subscriber policy values for a VPLS virtual core interface, which acts as a trunk interface. The VPLS virtual core interface represents all of the MPLS tunnels from the router to the remote VPLS edge (VE) devices.

| Note: MPLS does not exist by default and must be created, either explicitly with this command, or implicitly with another mpls configuration command. If you create MPLS implicitly, for example by issuing the command mpls lsp retries 10, MPLS remains disabled until you enable it, by issuing the mpls command.

#### Options

- permit—Specifies that the subscriber interface associated with the bridge group or VPLS instance forwards MPLS packets
- deny—Specifies that the subscriber interface associated with the bridge group or VPLS instance filters MPLS packets

#### Mode

Global Configuration, Interface Configuration, Subscriber Policy Configuration

## Related Documentation

- Configuring MPLS LSPs for L2VPNs and Configuring MPLS LSPs for VPLS in the JunosE BGP and MPLS Configuration Guide

#### Published: 2011-09-29

Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices
Copyright© 1999-2011 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out