Configuring Layer 2 Protocol Tunneling And Bpdu Protection; Procedure); Table 139: Layer2 Circuit Configuration Details; Configuring Layer 2 Protocol Tunneling And Bpdu Protection (Nsm Procedure) - Juniper NETWORK AND SECURITY MANAGER 2010.3 - M-SERIES AND MX-SERIES DEVICES GUIDE REV1 Manual

M-series and MX-series Devices

Configuring Layer 2 Protocol Tunneling and BPDU Protection (NSM Procedure)

262
Layer 2 protocol tunneling allows Layer 2 protocol data units (PDUs) to be tunneled
through a network. This is useful to provide a single Spanning Tree Protocol (STP) domain
for subscribers across a service provider network. On the MX Series routers only, you can
configure Bridge Protocol Data Unit (BPDU) protection to ignore BPDUs received on
interfaces where none should be expected (for example, a LAN interface on a network
edge with no other bridges present). If a BPDU is received on a blocked interface, the
interface is disabled and stops forwarding frames. By default, all BPDUs are accepted
and processed on all interfaces.
To configure layer 2 protocol tunneling and BPDU protection in NSM:
In the NSM navigation tree, select Device Manager > Devices.
1.
Click the Device Tree tab, and then double-click the device to select it.
2.
Click the Configuration tab. In the configuration tree, expand Protocols > Layer2
3.
Control.
Add or modify settings as specified in Table 139 on page 262.
4.
Click one:
5.
OK—Saves the changes.
Cancel—Cancels the modifications.

Table 139: Layer2 Circuit Configuration Details

Task
Enable BPDU blocking on an
interface.
Your Action
1. Click Bpdu Block next to Layer2 Control.
2. In the Comment box, enter the comment.
3. From the Disable Timeout list, select the disable timeout
value.
Range: 10 through 3600
Default: If this option is not configured, the interface is not
periodically checked and remains disabled
4. Click Interface next to Bpdu Block.
5. Click Add new entry next to Interface.
6. In the Name box, enter the interface name.
7. In the Comment box, enter the comment.
Copyright © 2010, Juniper Networks, Inc.