- Index
- Preface
- Product Overview
- Command-Line Interfaces (CLI)
- Smart Port Macros
- Virtual Switching Systems (VSS)
- Fast Software Upgrades
- Stateful Switchover (SSO)
- Non-Stop Forwarding (NSF)
- RPR Supervisor Engine Redundancy
- Switch Fabric Functionality
- Interface Configuration
- UniDirectional Link Detection (UDLD)
- Power Management
- Environmental Monitoring
- Online Diagnostics
- Onboard Failure Logging (OBFL)
- Cisco IP Phone Support
- Power over Ethernet
- Layer 2 LAN Port Configuration
- Flex Links
- EtherChannels
- IEEE 802.1ak MVRP and MRP
- VLAN Trunking Protocol (VTP)
- VLANs
- Private VLANs (PVLANs)
- Private Hosts
- IEEE 802.1Q Tunneling
- Layer 2 Protocol Tunneling (L2PT)
- Spanning Tree Protocols (STP, MST)
- Optional STP Features
- IP Unicast Layer 3 Switching
- Policy-Based Routing (PBR)
- Layer 3 Interface Configuration
- Unidirectional Ethernet (UDE) and unidirectional link routing (UDLR)
- Multiprotocol Label Switching (MPLS)
- MPLS VPN Support
- Ethernet over MPLS (EoMPLS)
- Virtual Private LAN Services (VPLS)
- Ethernet Virtual Connections (EVC)
- Layer 2 over Multipoint GRE (L2omGRE)
- IPv4 Multicast Layer 3 Features
- IPv4 Multicast IGMP Snooping
- IPv4 PIM Snooping
- IPv4 Multicast VLAN Registration (MVR)
- IPv4 IGMP Filtering
- IPv4 Router Guard
- IPv4 Multicast VPN Support
- IPv6 Multicast Layer 3 Features
- IPv6 MLD Snooping
- NetFlow Hardware Support
- Call Home
- System Event Archive (SEA)
- Backplane Platform Monitoring
- Local SPAN, RSPAN, and ERSPAN
- SNMP IfIndex Persistence
- Top-N Reports
- Layer 2 Traceroute Utility
- Mini Protocol Analyzer
- PFC QoS Overview
- PFC QoS Guidelines and Restrictions
- PFC QoS Classification, Marking, and Policing
- PFC QoS Policy Based Queueing
- PFC QoS Global and Interface Options
- AutoQoS
- MPLS QoS
- PFC QoS Statistics Data Export
- Cisco IOS ACL Support
- Cisco TrustSec (CTS)
- AutoSecure
- MAC Address-Based Traffic Blocking
- Port ACLs (PACLs)
- VLAN ACLs (VACLs)
- Policy-Based Forwarding (PBF)
- Denial of Service (DoS) Protection
- Control Plane Policing (CoPP)
- Dynamic Host Configuration Protocol (DHCP) Snooping
- IP Source Guard
- Dynamic ARP Inspection (DAI)
- Traffic Storm Control
- Unknown Unicast and Multicast Flood Control
- IEEE 802.1X Port-Based Authentication
- Web-Based Authentication
- Port Security
- Lawful Intercept
- Online Diagnostic Tests
- Migrating From a 12.2SX QoS Configuration
Layer 2 over Multipoint GRE (L2omGRE)
- Prerequisites for L2omGRE
- Restrictions for L2omGRE
- Information About L2omGRE
- Default Settings for L2omGRE
- How to Configure L2omGRE
- Verifying the L2omGRE Configuration
Note ●
For complete syntax and usage information for the commands used in this chapter, see these publications:
http://www.cisco.com/en/US/products/ps9536/prod_command_reference_list.html
- Cisco IOS Release 12.2SY supports only Ethernet interfaces. Cisco IOS Release 12.2SY does not support any WAN features or commands.
http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.html
Participate in the Technical Documentation Ideas forum
Prerequisites for L2omGRE
Restrictions for L2omGRE
- The L2omGRE feature is supported in VSS mode.
- The VLAN interface used to support L2omGRE cannot also be configured to support any Layer 3 features.
- You can configure QoS to police (rate limit) Layer 2 traffic that is flooded in a VLAN because it is addressed to a currently unlearned MAC-Layer destination address (see match l2 miss in the “Traffic Classification” section).
Information About L2omGRE
The L2omGRE feature provides Layer 2 connectivity between multiple separate network sites by extending the topology of a Layer 2 broadcast domain through an mGRE tunnel (see Figure 39-1).
The L2omGRE feature associates a VLAN interface with an mGRE tunnel interface. mGRE tunnel interfaces configured to support the L2omGRE feature function like Layer 2 LAN ports to provide Layer 2 switching (bridging) for traffic of all types in the VLAN, so that the tunnel only carries traffic addressed to devices accessible through the mGRE tunnel (see the “Information about Layer 2 Ethernet Switching” section). The switch will learn MAC addresses that are accessible through mGRE tunnels and the show mac address-table command displays the learned addresses.
The PFC and any DFCs support bridging and mGRE tunnel encapsulation and decapsulation in hardware.
Each tunnel can carry multiple L2omGRE-connected VLANs. The tunnel encapsulation includes the VLAN ID. When the tunneled traffic is decapsulated, the VLAN ID in the tunneled traffic is used to select the correct VLAN for the traffic.
Default Settings for L2omGRE
How to Configure L2omGRE
- Configuring a Loopback Interface
- Configuring an mGRE Tunnel Interface
- Configuring a VLAN Interface
- L2omGRE Configuration Examples
Configuring a Loopback Interface
To configure a loopback inteface to support L2omGRE, perform this task:
Configuring an mGRE Tunnel Interface
To configure an mGRE tunnel inteface, perform this task:
|
|
|
|
|---|---|---|
Creates a tunnel interface and enters interface configuration mode. Note VLAN interfaces on this switch refer to this tunnel number. |
||
Router(config-if)# ip nhrp map tunnel_address loopback_address |
Configures the IP-to-nonbroadcast multiaccess (NBMA) address mapping to the loopback interface IP addresses configured on the other switches with L2omGRE tunnel interfaces. |
|
Router(config-if)# ip nhrp network-id ID |
Enables the Next Hop Resolution Protocol (NHRP) for the mGRE tunnels. Use the same ID value on all of the L2omGRE tunnel interfaces. |
|
Router(config-if)# tunnel source loopback number |
Associates this tunnel interface with the loopback interface. |
|
Router(config-if)# tunnel mode gre multipoint |
||
Configuring a VLAN Interface
To configure a VLAN interface to support L2omGRE, perform this task:
|
|
|
|
|---|---|---|
Creates the VLAN interface and enters interface configuration mode. |
||
Router(config-if)# platform xconnect l2gre tunnel number |
Associates the VLAN interface with an L2omGRE tunnel interface. |
|
L2omGRE Configuration Examples
The L2omGRE configuration commands must be coordinated as follows:
- The ip nhrp map commands on each switch point to the tunnel and loopback IP addresses on each of the other switches.
- On each switch, the tunnel source loopback command points to the loopback interface configured on that switch.
- On each switch, the platform xconnect l2gre tunnel command points to the L2omGRE tunnel interface on that switch.
Enter the show platform l2transport gre summary command to display information about the L2omGRE configuration on a switch.
Verifying the L2omGRE Configuration
Enter the show platform l2transport gre command to display information about L2omGRE, including traffic statistics.
http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.html
Participate in the Technical Documentation Ideas forum
Feedback