L2CP Processing Deployment Considerations9-6 User Manual ML700Deployment ConsiderationsSpecial traffic (IEEE reserved multicast MAC addresses, Cisco management MACaddresses) from the customer's LAN can be tunneled through the service provider WANwithout triggering L2 features (like STP) on service provider devices. This section providesseveral examples to illustrate the issue.Table 40: Examples of Deployment ConsiderationsCASE DescriptionCASE1 (onpage 9-6)Customer LAN uses Cisco equipment and Cisco's STP (but notPVST+), Provider WAN does not use STPCASE 2 (onpage 9-7)Customer LAN uses Cisco PVST+, Provider WAN does notuse STPCase 3A (onpage 9-8)Customer uses Cisco PVST+, Provider uses IEEE 802.1STP/RSTP or Cisco PVST+Case 3B (onpage 9-8)Customer uses Cisco PVST+, Provider uses IEEE 802.1STP/RSTPCase 1CASE1. Customer LAN uses Cisco equipment and Cisco's STP (but not PVST+),Provider WAN does not use STPIn most cases, Cisco equipment can be used in the customer's LAN without requiringcomplex configuration of the ML - ML default L2CP configuration is sufficient.By default, each ML NE forwards all Cisco traffic (0x01-00-0C-**-**-** reserved forproprietary Cisco protocols such as ISL, CDP, VTP, PVST+) as regular traffic (according toVLANs membership rules configured on the NE). To restore the default setting:1. In the MetaASSIST View, L2CP pane (on page 9-3), click the Configure CiscoAddresses button2. Select as Regular Service Traffic, and click OK.3. Repeat on all ML NEs participating in the forwarding.NOTE: Cisco frames can be also enforcedly forwarded ignoring regular traffic VLAN rules, and usinganother VID dedicated for this purpose. For such deployment, use transparent tunnel (see below) onCPE and tunnel by TAG on CO.
