Table Of Contents
Release Notes for Cisco IOS Release 12.2ZU on the Cisco ME 6500 Series Ethernet Switches
Cisco ME 6500 Series Ethernet Switches (ME6524)
Feature Set Guidelines and Restrictions
Images in Release 12.2(18)ZU and Rebuilds
Advanced IP Services Feature Set in Release 12.2(18)ZU and Rebuilds
IP Base Feature Set Images in Release 12.2(18)ZU and Rebuilds
New Features in Release 12.2(18)ZU2
New Features in Release 12.2(18)ZU1
Features in Release 12.2(18)ZU
Unsupported Features and Commands
Resolved Caveats in Release 12.2(18)ZU2
Resolved Caveats in Release 12.2(18)ZU1
Additional Troubleshooting Information
Cisco IOS Software Documentation Set
Release 12.2 Documentation Set
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco IOS Release 12.2ZU on the Cisco ME 6500 Series Ethernet Switches
January 30, 2007
Note
This publication applies to the ME6524 platform.
The most current release notes for 12.2ZU are available at this URL:
http://www.cisco.com/en/US/docs/switches/metro/me6500/software/12.2_18_ZU/release/notes/ol_9584.html
Contents
This publication consists of these sections:
•
New Features in Release 12.2(18)ZU2
•
New Features in Release 12.2(18)ZU1
•
Features in Release 12.2(18)ZU
•
Unsupported Features and Commands
•
Resolved Caveats in Release 12.2(18)ZU2
•
Resolved Caveats in Release 12.2(18)ZU1
•
Obtaining Documentation, Obtaining Support, and Security Guidelines
List of Releases
Note
See the "Feature Sets" section for information about which releases are deferred.
Release 12.2ZU consists of these releases:
•
Release 12.2(18)ZU2:
–
Date of release: 30 Jan 2007
–
Based on Release 12.2(18)ZU1
•
Release 12.2(18)ZU1:
–
Date of release: 30 Oct 2006
–
Based on Release 12.2(18)ZU
•
Release 12.2(18)ZU:
–
Date of release: 03 Aug 2006
–
Based on Release 12.2(18)SXF3
This publication does not describe features that are available in Release 12.2, Release 12.2 T, Release 12.2 S, or other Release 12.2 early deployment releases.
For a list of the Release 12.2 caveats that apply to Release 12.2ZU, see the "Resolved Caveats in Release 12.2(18)ZU1" section and refer to this publication:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/prod_release_notes_list.html
For a list of the Release 12.2 S caveats that apply to Release 12.2ZU, see the "Resolved Caveats in Release 12.2(18)ZU1" section and refer to this publication:
http://www.cisco.com/en/US/docs/ios/12_2s/release/notes/122Srn.html
Supported Hardware
These sections describe the hardware supported in Release 12.2ZU:
•
Cisco ME 6500 Series Ethernet Switches (ME6524)
Note
The PFC3C partitions the hardware FIB table to route IPv4 unicast, IPv4 multicast, MPLS, and IPv6 unicast and multicast traffic in hardware. Traffic for routes that do not have entries in the hardware FIB table are routed by the MSFC in software. The defaults are:
•
IPv4 unicast and MPLS—192,000 routes
•
IPv4 multicast and IPv6 unicast and multicast—32,000 routes
The size of the global internet routing table plus any local routes might exceed the default partition sizes.
These are the theoretical maximum numbers of routes for the supported protocols (the maximums are not supported simultaneously):
•
IPv4 and MPLS—Up to 239,000 routes
•
IPv4 multicast and IPv6 unicast and multicast—Up to 119,000 routes
Enter the mls cef maximum-routes command to repartition the hardware FIB table. IPv4 unicast and MPLS require one hardware FIB table entry per route. IPv4 multicast and IPv6 unicast and multicast require two hardware FIB table entries per route. Changing the partition for one protocol makes corresponding changes in the partitions of the other protocols. You must enter the reload command to put configuration changes made with the mls cef maximum-routes command into effect.
Cisco ME 6500 Series Ethernet Switches (ME6524)
Product ID
(append "=" for spares) Product Description Minimum Software Version ME-C6524GS-8SCisco ME 6500 Series Ethernet switches:
•
Switch processor (SP):
–
256-MB DRAM
–
128-MB bootflash
•
Policy Feature Card 3C (PFC3C):
–
Supports a theoretical maximum of 96 K MAC addresses (64 K MAC addresses recommended maximum).
–
The PFC3C operates in PFC3C mode. Enter the show platform hardware pfc mode command to display the PFC3 mode.
•
Route processor (RP)—Multilayer Switch Feature Card 2A (MSFC2A):
–
512-MB DRAM
–
64-MB bootflash
•
Fan tray: FAN-C6524
•
Power supplies: PWR-400W-DC
•
64 chassis MAC addresses
•
Eight Gigabit Ethernet SFP ports:
–
Requires Gigabit Ethernet SFPs
–
1 port group: ports 25-32
–
QoS port architecture (Rx/Tx): 2q8t/1p3q8t
•
ME-C6524GS-8S:
–
24 Gigabit Ethernet SFP ports (requires Gigabit Ethernet SFPs)
–
4 port groups: ports 1-6, 7-12, 13-18, 19-24
–
QoS port architecture (Rx/Tx): 1q2t/1p3q8t
•
ME-C6524GT-8S:
–
24 10/100/1000 Mbps RJ-45 Ethernet ports
–
4 port groups: ports 1-6, 7-12, 13-18, 19-24
–
QoS port architecture (Rx/Tx): 1q2t/1p3q8t
12.2(18)ZU
ME-C6524GT-8SNote
See this publication for Cisco ME 6500 Series Ethernet switch hardware information:
http://www.cisco.com/en/US/products/ps6845/prod_installation_guides_list.html
Gigabit Ethernet SFPs
Note
These DWDM-SFPs are not supported in Release 12.2(18)ZU2:
•
DWDM-SFP-5817—1000BASE-DWDM 1558.17 nm SFP (100-GHz ITU grid) SFP module
•
DWDM-SFP-5252—1000BASE-DWDM 1552.52 nm SFP (100-GHz ITU grid) SFP module
•
DWDM-SFP-5172—1000BASE-DWDM 1551.72 nm SFP (100-GHz ITU grid) SFP module
•
DWDM-SFP-5012—1000BASE-DWDM 1550.12 nm SFP (100-GHz ITU grid) SFP module
•
DWDM-SFP-4692—1000BASE-DWDM 1546.92 nm SFP (100-GHz ITU grid) SFP module
•
DWDM-SFP-4373—1000BASE-DWDM 1543.73 nm SFP (100-GHz ITU grid) SFP module
•
DWDM-SFP-4214—1000BASE-DWDM 1542.14 nm SFP (100-GHz ITU grid) SFP module
•
DWDM-SFP-3977—1000BASE-DWDM 1539.77 nm SFP (100-GHz ITU grid) SFP module
•
DWDM-SFP-3898—1000BASE-DWDM 1538.98 nm SFP (100-GHz ITU grid) SFP module
•
DWDM-SFP-3582—1000BASE-DWDM 1535.82 nm SFP (100-GHz ITU grid) SFP module
•
DWDM-SFP-3504—1000BASE-DWDM 1535.04 nm SFP (100-GHz ITU grid) SFP module
Fast Ethernet SFPs
Feature Sets
These sections describe the feature sets in Release 12.2ZU:
•
Feature Set Guidelines and Restrictions
•
Images in Release 12.2(18)ZU and Rebuilds
Feature Set Guidelines and Restrictions
These are the feature set guidelines and restrictions:
•
There are no 12.2ZU boot loader images: none are required.
•
The releases includes strong encryption images. Strong encryption images are subject to U.S. and local country export, import, and use laws. The country and class of end users eligible to receive and use Cisco encryption solutions are limited. Refer to this publication for more information:
http://www.cisco.com/pcgi-bin/Software/Crypto/crypto_main.pl
•
Many TFTP server implementations cannot transfer 16 MB or larger files. To transfer 16 MB or larger files, you might need to use FTP or rcp. Refer to this online publication for procedures:
http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/fcf008.html
•
The k9 images support SSH 3DES access and the IPsec Network Security feature (configured with the crypto ipsec command) in software on the MSFC2A. IPsec in software on the MSFC2A is supported only for administrative connections.
Feature Set Descriptions
This section lists all of the features that are unique to the Advanced IP Services feature set, and some of the features that are common to both feature sets. See the "Features in Release 12.2(18)ZU" section for a more complete list of supported features.
Images in Release 12.2(18)ZU and Rebuilds
•
Advanced IP Services Feature Set in Release 12.2(18)ZU and Rebuilds
•
IP Base Feature Set Images in Release 12.2(18)ZU and Rebuilds
Advanced IP Services Feature Set in Release 12.2(18)ZU and Rebuilds
Image Filename and Size in Bytes Description and Product IDs6523-advipservicesk9-mz.122-18.ZU2 (25,206,820)
s6523-advipservicesk9-mz.122-18.ZU1 (25,204,260)
s6523-advipservicesk9-mz.122-18.ZU (25,199,108)Note
This is a limited-access strong encryption image.
ADVANCED IP SERVICES SSH: S523AIK9L-12218ZU
IP Base Feature Set Images in Release 12.2(18)ZU and Rebuilds
Image Filename and Size in Bytes Description and Product IDs6523-ipbasek9-mz.122-18.ZU2 (25,203,652)
s6523-ipbasek9-mz.122-18.ZU1 (25,202,116)
s6523-ipbasek9-mz.122-18.ZU (25,196,996)Note
This is a limited-access strong encryption image.
IP BASE SSH LAN ONLY: S523IBK9L-12218ZU
s6523-ipbase-mz.122-18.ZU2 (23,870,372)
s6523-ipbase-mz.122-18.ZU1 (23,867,812)
s6523-ipbase-mz.122-18.ZU (23,865,252)IP BASE LAN ONLY: S523IBL-12218ZU
New Features in Release 12.2(18)ZU2
•
DWDM SFP transceivers (see the "Gigabit Ethernet SFPs" section)
•
TCP MSS Adjustment—See this publication:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124tcg/tiapp_c/htiptcp.htm#wp1067289
New Features in Release 12.2(18)ZU1
None.
Features in Release 12.2(18)ZU
. This section describes the features in Release 12.2(18)ZU, 03 Aug 2006:
•
4096 Layer 2 VLANs—See this publication:
Note
We recommend that you configure a combined total of no more than 2,000 Layer 3 VLAN interfaces and Layer 3 ports.
•
ARP ACLs for QoS Filtering—See this publication:
•
BGP Configuration Using Peer Templates—See this publication:
http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/s_bgpct.html
•
BGP Cost Community—See this publication:
http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/s_bgpcc.html
•
BGP Dynamic Update Peer-Groups—See this publication:
http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/s_bgpdpg.html
•
BGP Increased Support of Numbered AS-path Access Lists to 500—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfbgp.html
•
BGP multipath load sharing for both eBGP and iBGP in an MPLS-VPN—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2sx/feature/guide/fsxeibmp.html
Note
With the BGP multipath load sharing for both eBGP and iBGP in an MPLS-VPN feature configured, do not attach output service policies to VRF interfaces. (CSCsb25509)
For nonMPLS environments, see the Interior Border Gateway Protocol (iBGP) Multipath Load Sharing feature.•
BGP Restart Session After Max-Prefix Limit—See this publication:
•
BGP Route-Map Continue—See this publication:
http://www.cisco.com/en/US/docs/ios/12_4t/12_4t4/t_bgprco.html
•
BGP Route-Map Policy List Support—See this publication:
http://www.cisco.com/en/US/docs/ios/12_4t/12_4t4/t_bgprco.html
•
BGP support for TTL security check—See this publication:
http://www.cisco.com/en/US/docs/ios/12_3t/12_3t7/feature/guide/gt_btsh.html
•
Bidirectional Forwarding Detection (BFD) standard implementation—See this publication:
http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/fs_bfd.html
Note
Also see "OSPF support for BFD over IPv4."
•
Bidirectional Protocol Independent Multicast (PIM) in hardware—See this publication:
•
Boot Protocol (BOOTP) relay— See this publication:
http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/fcf012.html
•
Cisco IOS IP Event Dampening—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2t/12_2t13/feature/guide/ftipevdp.html
•
Cisco IOS IPv6 Provider Edge Router (6PE) over MPLS (supported only in PFC3BXL or PFC3B mode)—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2t/ipv6/SA_mpls6.html
•
Cisco IOS Secure Copy (SCP)—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2t/12_2t2/feature/guide/ftscp.html
•
Clear hardware interface counters—See this publication:
http://www.cisco.com/en/US/docs/switches/metro/me6500/software/12.2_18_ZU/command/reference/cr.html
•
CNS Interactive CLI—Network management applications can use the Cisco Networking Services (CNS) agents to manage network routers. The CNS agent provides the capability to send commands to a router from a programmable source. The CNS Interactive CLI feature introduces a new XML interface that allows you to send interactive commands to a router, such as commands that generate prompts for user input. A benefit of this feature is that interactive commands can be aborted before they have been fully processed. For example, for commands that generate a significant amount of output, the XML interface can be customized to limit the size of the output or the length of time allowed for the output to accumulate. The capability to use a programmable interface to abort a command before its normal termination (similar to manually aborting a command) can greatly increase the efficiency of diagnostic applications that might use this functionality. The new XML interface also allows for multiple commands to be processed in a single session. The response for each command is packaged together and sent in a single response event.
•
Configurable Per VLAN MAC Learning (PVL)—See the mac-address-table learning command in this publication:
http://www.cisco.com/en/US/docs/switches/metro/me6500/software/12.2_18_ZU/command/reference/cr.html
•
Custom IEEE 802.1Q Ethertypes—See this publication:
•
DHCP Option 82 on untrusted Port—See this publication:
•
DHCP Snooping—See this publication:
•
Digital Optical Monitoring (DOM)—See the show interfaces transceiver command in this publication:
http://www.cisco.com/en/US/docs/switches/metro/me6500/software/12.2_18_ZU/command/reference/cr.html
•
DSCP transparency (also called "Preserving the Received ToS Byte")—See the procedures in this publication:
•
Dynamic ARP Inspection (DAI)—See this publication:
•
Dynamic Host Configuration Protocol (DHCP)— See this publication:
http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfdhcp.html
•
Egress ACL support for remarked DSCP—See this publication:
•
Egress DSCP mutation—See the procedures in this publication:
•
Egress policing for LAN ports configured as Layer 3 interfaces and for VLAN interfaces—See the procedures in this publication for information about configuring the service-policy output command:
•
EIGRP MPLS VPN PE-CE site of origin (SoO)—See this publication:
http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/s_mvesoo.html
•
Embedded network management improvements—See this publication:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/7600mibs/index.htm
•
Encapsulated Remote SPAN (ERSPAN)—See this publication:
•
EtherChannel Enhancement - 128 EtherChannels Support—See this publication:
•
EtherChannel Min-Links—See this publication:
•
EtherChannel—See this publication:
http://www.cisco.com/univercd/cc/td/doc/product/metro/me6500/122zu/sg/channel.htm
•
Ethernet over MPLS (EoMPLS)—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/atom.html
•
Flex Links—See this publication:
•
Gateway Load Balancing Protocol—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/fs_glbp2.html
•
Generic Online Diagnostics (GOLD)—See this publication:
•
Hardware Capacity Monitoring—See this publication:
•
Hardware Control Plane Interface for Control Plane Policing (CoPP):
–
Cisco ME 6500 series switches do not support CoPP output rate limiting (policing).
–
Cisco ME 6500 series switches do not support the CoPP silent operation mode.
–
Cisco ME 6500 series switches do not support the match protocol arp command.
–
See this publication:
•
Hardware support for directed broadcasts with the mls ip directed-broadcast command—See this publication:
http://www.cisco.com/en/US/docs/switches/metro/me6500/software/12.2_18_ZU/command/reference/M1.html
•
Hardware switching for ICMP traffic when Cisco IOS reflexive ACLs are configured. (CSCeb20666)
•
Hardware-assisted IP-in-IP tunneling and generic routing encapsulation (GRE) tunneling—The PFC3C support the following tunnel commands:
–
tunnel destination
–
tunnel mode gre
–
tunnel mode ipip
–
tunnel source
–
tunnel ttl
–
tunnel tos
Other supported types of tunneling run in software on the MSFC2A.
The tunnel ttl command (default 255) sets the TTL of encapsulated packets.
The tunnel tos command, if present, sets the ToS byte of a packet when it is encapsulated. If the tunnel tos command is not present and QoS is not enabled, the ToS byte of a packet sets the ToS byte of the packet when it is encapsulated. If the tunnel tos command is not present and QoS is enabled, the ToS byte of a packet as modified by PFC QoS sets the ToS byte of the packet when it is encapsulated.
To configure GRE tunneling and IP-in-IP tunneling, see these publications:
http://www.cisco.com/en/US/docs/ios/12_2/interface/configuration/guide/icflogin.html
/en/US/docs/ios/12_2/interface/command/reference/irfshoip.html
To configure the tunnel tos and tunnel ttl commands, see this publication:
http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/12s_tos.html
Note the following information about tunnels:
–
Each hardware-assisted tunnel must have a unique source. Hardware-assisted tunnels cannot share a source even if the destinations are different. Use secondary addresses on loopback interfaces or create multiple loopback interfaces. (CSCdy72539)
–
Each tunnel interface uses one internal VLAN.
–
Each tunnel interface uses one additional router MAC address entry per router MAC address.
–
The PFC3C supports PFC QoS features on tunnel interfaces.
–
The MSFC2A supports tunnels configured with egress features on the tunnel interface. Examples of egress features are output Cisco IOS ACLs, NAT and PAT (for inside to outside translation), and encryption.
•
Hardware-assisted Multiple-path Unicast Reverse Path Forwarding (Unicast RPF)—See this publication:
•
Hardware-assisted NetFlow Aggregation—See this publication:
•
Hardware-assisted Network Address Translation (NAT) and Port Address Translation (PAT) for IPv4 unicast and multicast traffic—Note the following information about hardware-assisted NAT:
–
The PFC3C does not support NAT or PAT for multicast traffic.
–
The PFC3C does not support NAT or PAT configured with a route map that specifies length.
–
The PFC3C does not support NAT or PAT configured with a route map that specifies static translations.
–
When you configure NAT or PAT and NDE on an interface, the PFC3C sends all traffic in fragmented packets to the MSFC2A to be processed in software. (CSCdz51590)
To configure NAT or PAT, see the "Configuring Network Address Translation" section at this URL:
http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfipadr.html
For information about configuring NAT or PAT with route maps, see this publication:
http://www.cisco.com/en/US/tech/tk648/tk361/technologies_q_and_a_item09186a00800e523b.shtml
To prevent a significant volume of NAT or PAT traffic from being sent to the MSFC2A, due to either a DoS attack or a misconfiguration, enter the mls rate-limit unicast acl {ingress | egress} command described in this publication:
http://www.cisco.com/en/US/docs/switches/metro/me6500/software/12.2_18_ZU/command/reference/M1.html
(CSCea23296)
•
Hardware-assisted policy-based routing (PBR) for route-map sequences that use the match ip address, set ip next-hop, and set ip default next-hop PBR keywords.
To configure PBR, see the "Configuring Policy-Based Routing" section at this URL:
When configuring PBR, follow these guidelines and restrictions:
–
The PFC3C provides hardware support for PBR configured on a tunnel interface.
–
The PFC3C does not provide hardware support for PBR configured with the set ip next-hop keywords if the next hop is a tunnel interface.
–
If the MSFC2A address falls within the range of a PBR ACL, traffic addressed to the MSFC2A is policy routed in hardware instead of being forwarded to the MSFC2A. To prevent policy routing of traffic addressed to the MSFC2A, configure PBR ACLs to deny traffic addressed to the MSFC2A.
–
Any options in Cisco IOS ACLs that provide filtering in a PBR route map that would cause flows to be sent to the MSFC2A to be switched in software are ignored. For example, logging is not supported in ACEs in Cisco IOS ACLs that provide filtering in PBR route maps.
–
PBR traffic through switching module ports where PBR is configured is routed in software if the switching module resets. (CSCee92191)
•
Hardware-supported counters for hardware-supported ACLs, displayed by the show tcam interface command. See this publication:
•
IEEE 802.1Q protocol tunneling—See this publication:
•
IEEE 802.1Q tunneling—See this publication:
•
IEEE 802.1s - Multiple Spanning Tree (MST) Standard Compliance—See this publication:
•
IEEE 802.1w, rapid reconfiguration of spanning tree—See this publication:
•
IEEE 802.1X Port-Based Authentication—See this publication:
•
IEEE 802.3ad, link aggregation control protocol (LACP)—See this publication:
•
IGMP snooping and IGMP snooping querier—See this publication:
•
Ingress CoS mutation on IEEE 802.1Q tunnel ports—See this publication:
•
Interior Border Gateway Protocol (iBGP) Multipath Load Sharing—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/fsbgpls.html
Note
For MPLS support, see BGP Multipath Load Sharing for Both eBGP and iBGP in an MPLS-VPN.
•
Internet Group Management Protocol Version 3 (IGMPv3) snooping—See this publication:
•
Invalid Special Parameter Index (SPI) Recovery—See this publication:
http://www.cisco.com/en/US/docs/ios/12_3t/12_3t2/feature/guide/gt_ispir.html
•
IP Unnumbered for VLAN-SVI interfaces—See this publication:
•
Hardware support for these basic IPv6 functions:
–
IPv6 standard access control lists (ACLs)
–
IPv6 extended ACLs
–
Reflexive ACLs
–
Manually configured v6 tunnels
–
ISATAP (ISATAP with 6-to-4 prefix is not supported in hardware)
–
Automatically configured IPv4 compatible tunnels
–
6-to-4 tunnel
–
IPv6 over IPV4 IP in IP tunnels
•
Software support for these basic IPv6 functions:
–
IPv6 addressing architecture
–
ICMPv6
–
Neighbor Discovery
–
Static ND cache entry
–
IPv6 stateless autoconfiguration
–
ICMPv6 Redirect
–
MTU path Discovery for IPv6
–
IPv6 ICMP rate limiting
–
IPv6 over IPV4 GRE tunnels
•
Software support for IPv6 routing:
–
Static routes within IPv6
–
RIPng
–
MP-BGP4
–
OSPFv3
–
ISIS
–
Configuring an IPv6 Multiprotocol BGP Peer using a link local address
–
IPv6 MP-BGP distance command
•
Switching support for IPv6:
–
Process
–
CEFv6
–
Distributed CEFv6
•
Software support for these IPv6 applications:
–
Ping
–
Traceroute
–
Telnet
–
TFTP (client only)
–
FTP
–
SSH over IPv6
–
DNS
–
HTTP server
For configuration information, see this publication:
http://www.cisco.com/en/US/docs/ios/12_2t/ipv6/ipv6_vgf.html
For command reference information, see this publication:
http://www.cisco.com/en/US/docs/ios/12_3t/ipv6/ipv6_r.html
•
IPv6 access services: DHCPv6 prefix delegation—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2t/ipv6/ipv6_vgf.html
•
IPv6 hardware: multicast assist—See this publication:
•
IPv6 multicast: Bootstrap Router (BSR)—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2t/ipv6/SA_mcast.html
•
IPv6 Multicast: HW assisted egress replication—See this publication:
•
IPv6 QoS: (quality of service)—See this publication:
•
Jumbo frames on all Ethernet ports—See this publication:
•
Layer 2 protocol tunneling global threshold—See the l2protocol-tunnel global drop-threshold command in the command reference at this URL:
http://www.cisco.com/en/US/docs/switches/metro/me6500/software/12.2_18_ZU/command/reference/cr.html
•
Layer 2 switch ports and VLAN trunks with the Dynamic Trunking Protocol (DTP), including support on Gigabit Ethernet ports for jumbo frames—See this publication:
•
Layer 2 traceroute—See this publication:
•
Local proxy ARP—See the Command Reference publication.
Note
To use the local proxy ARP feature, you must enable the IP proxy ARP feature. The IP proxy ARP feature is enabled by default. See the "Enabling Proxy ARP" section at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/ip_c/ipcprt1/1cdipadr.htm•
MAC address-based traffic blocking—See this publication:
•
MLD snooping—See this publication:
•
MPLS LDP - Inbound Label Binding Filtering—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/fsinbd4.html
•
MPLS LSP ping/traceroute and AToM VCCV—See this publication:
http://www.cisco.com/en/US/docs/ios/12_4t/12_4t11/ht_lspng.html
•
MPLS Traffic Engineering (TE) Fast Reroute (FRR) Link and Node Protection—See these publications:
http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/fsfrr24.html
•
MPLS Traffic Engineering DiffServ Aware (DS-TE)—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/fsdserv3.html
Note
MPLS Traffic Engineering DiffServ Aware (DS-TE) is not supported on Port channel interfaces or switch virtual interfaces (SVIs).
•
MPLS Traffic Engineering (TE) Forwarding Adjacency—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/fstefa_3.html
•
MPLS Traffic Engineering (TE) Interarea Tunnels—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/fsiarea3.html
•
MPLS VPN support for EIGRP between Provider Edge (PE) and Customer Edge (CE) —See this publication:
http://www.cisco.com/en/US/docs/ios/12_2t/12_2t15/feature/guide/fteipece.html
Note
The MPLS VPN support for EIGRP between Provider Edge (PE) and Customer Edge (CE) feature also provides EIGRP support for VRF Lite.
•
MPLS Virtual Private Networks (MPLS VPN; supported only in PFC3BXL or PFC3B mode)—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/fsmvpns.html
•
MPLS VPN Carrier Supporting Carrier (supported only in PFC3BXL or PFC3B mode)—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/fs2scsc.html
http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/fscsclbl.html
•
MPLS VPN—Inter-AS—IPv4 BGP Label Distribution (supported only in PFC3BXL or PFC3B mode)—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/fsiaslbl.html
•
MPLS VPN ID (supported only in PFC3BXL or PFC3B mode)—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/vpnid2.html
•
MPLS VPN—OSPF and Sham-Link Support—See this publication:
http://www.cisco.com/en/US/docs/ios/12_0st/12_0st21/feature/guide/shamlink.html
•
Multicast-VPN: Multicast Support for MPLS VPN—See this publication:
Note
Support for MVPN also includes support for multicast VRF (MVRF). MVRF is also known as multicast over VRF-lite.
•
Multiple-Hot Standby Routing Protocol— See this publication:
http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfip.html
•
NDE—See this publication:
•
NetFlow - Bridged Flow Statistics—See this publication:
•
NetFlow Data Export—See this publication:
•
Netflow Multiple Export Destinations:
–
Allows entry of a second ip flow-export destination command
–
See this publication:
•
NetFlow v9 Export Format, including NetFlow Export of BGP Nexthop Information—See this publication:
http://www.cisco.com/en/US/docs/ios/12_3/feature/gde/nfv9expf.html
•
Optimized ACL logging—See this publication:
•
OSPF Forwarding Address Suppression in Translated Type-5 LSAs—See this publication:
http://www.cisco.com/en/US/docs/ios/12_2t/12_2t15/feature/guide/ftoadsup.html
•
OSPF Inbound Filtering Using Route Maps with a Distribute List—See this publication:
http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/routmap.html
•
OSPF Incremental Shortest Path First (i-SPF)—See this publication:
http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/ospfispf.html
•
OSPF Limit on Number of Redistributed Routes—See this publication:

