These release notes include important information about Cisco IOS Release 12.2(37)SE, Cisco IOS Release12.2(37)SE1, and any limitations, restrictions, and caveats that apply to the releases. Verify that these release notes are correct for your switch:

•If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.

You can download the switch software from this site (registered Cisco.com users with a login password):

http://www.cisco.com/kobayashi/sw-center/index.shtml

This software release is part of a special release of Cisco IOS software that is not released on the same 8-week maintenance cycle that is used for other platforms. As maintenance releases and future software releases become available, they will be posted to Cisco.com in the Cisco IOS software area.

Finding the Software Version and Feature Set

The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. The image is stored on the system board flash device (flash:).

You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version.

You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that you might have stored in flash memory.

Deciding Which Files to Use

The upgrade procedures in these release notes describe how to perform the upgrade by using a combined tar file. This file contains the Cisco IOS image file. To upgrade the switch through the command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.

Archiving Software Images

Before upgrading your switch software, make sure that you have archived copies of the current Cisco IOS release and the Cisco IOS release to which you are upgrading. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly in your network.

Cisco routinely removes old Cisco IOS versions from Cisco.com. See Product Bulletin 2863 for more information:

You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.

You can also configure the switch as a TFTP server to copy files from one switch to another without using an external TFTP server by using the tftp-server global configuration command. For more information about the tftp-server command, see the "Basic File Transfer Services Commands" section of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 at this URL:

Upgrading a Switch

This procedure is for copying the combined tar file to the switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.

Note For downloading software, we recommend that you connect to the TFTP server through a network node interface (NNI). If you want to connect to the server through a user network interface (UNI), see the "Troubleshooting" chapter of the software configuration guide for methods for enabling ping capability on UNIs. See the "New Software Features" section for a definition of NNIs and UNIs.

Step 3 Copy the image to the appropriate TFTP directory on the workstation, and make sure that the TFTP server is properly configured.

For more information, refer to Appendix B in the software configuration guide for this release.

Step 4 Log into the switch through the console port or a Telnet session.

Step 5 (Optional) Ensure that you have IP connectivity to the TFTP server by entering thisprivileged EXEC command:

Switch# pingtftp-server-address

Note By default, ping is supported on network node interfaces (NNIs), but you cannot ping from a user network interface (UNI) because the control-plane security feature drops ICMP response packets received on UNIs. See the "Troubleshooting" chapter of the software configuration guide for methods for pinging from the switch to a host connected to a UNI.

For more information about assigning an IP address and default gateway to the switch, refer to the software configuration guide for this release.

Step 6 Download the image file from the TFTP server to the switch. If you are installing the same version of software that is currently on the switch, overwrite the current image by entering this privileged EXEC command:

Limitations and Restrictions

You should review this section before you begin working with the switch. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.

Configuration

–When the switch is booted without a configuration (no config.text file in flash memory).

–When the switch is connected to a DHCP server that is configured to give an address to it (the dynamic IP address is assigned to VLAN 1).

–When an IP address is configured on VLAN 1 before the dynamic address lease assigned to VLAN 1 expires.

The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)

•The DHCP snooping binding database is not written to flash memory or a remote file in any of these situations:

–When the Network Time Protocol (NTP) is configured, but the NTP clock is not synchronized. You can check the clock status by entering the show NTP status privileged EXEC command and verifying that the network connection to the NTP server and the peer work correctly.

–The DHCP snooping database file is manually removed from the file system. After enabling the DHCP snooping database by configuring a database URL, a database file is created. If the file is manually removed from the file system, the DHCP snooping database does not create another database file. You need to disable the DHCP snooping database and enable it again to create the database file.

–The URL for the configured DHCP snooping database was replaced because the original URL was not accessible. The new URL might not take effect after the timeout of the old URL.

No workaround is necessary; these are the designed behaviors. (CSCed50819)

•When dynamic ARP inspection is enabled on a switch, ARP and RARP packets greater than 2016 bytes are dropped by the switch or switch stack. This is a hardware limitation.

However, when dynamic ARP inspection is not enabled and a jumbo MTU is configured, ARP and RARP packets are correctly bridged in hardware. (CSCed79734)

•Dynamic ARP inspection log entries might be lost after a switch failure. Any log entries that are still in the log buffer (have not been output as a system message) on a switch that fails are lost.

When you enter the show ip arp inspection log privileged EXEC command, the log entries from all switches in the stack are moved to the switch on which you entered the command.

There is no workaround. (CSCed95822)

•When port security is enabled on an interface in restricted mode and the switchport block unicast interface command has been entered on that interface, MAC addresses are incorrectly forwarded when they should be blocked

The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. (CSCee93822)

•A traceback error occurs if a crypto key is generated after an SSL client session.

There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)

IP

These are the IP limitations:

•Subnetwork Access Protocol (SNAP) encapsulated IP packets are dropped without an error message being reported at the interface. The switch does not support SNAP-encapsulated IP packets. There is no workaround. (CSCdz89142)

•The switch does not create an adjacent table entry when the ARP timeout value is 15 seconds and the ARP request times out. The workaround is to not set an ARP timeout value lower than 120 seconds. (CSCea21674)

MAC Addressing

This is the MAC addressing limitation:

When a MAC address is configured for filtering on the internal VLAN of a routed port, incoming packets from the MAC address to the routed port are not dropped. (CSCeb67937)

Multicasting

These are the multicasting limitations:

•The switch does not support tunnel interfaces, including DVMRP and PIM tunneling.

•Nonreverse-path forwarded (RPF) IP multicast traffic to a group that is bridged in a VLAN is leaked onto a trunk port in the VLAN even if the port is not a member of the group in the VLAN, but it is a member of the group in another VLAN. Because unnecessary traffic is sent on the trunk port, it reduces the bandwidth of the port. There is no workaround for this problem because non-RPF traffic is continuous in certain topologies. As long as the trunk port is a member of the group in at least one VLAN, this problem occurs for the non-RPF traffic. (CSCdu25219)

•If the number of multicast routes and Internet Group Management Protocol (IGMP) groups are more than the maximum number specified by the show sdm prefer global configuration command, the traffic received on unknown groups is flooded in the received VLAN even though the show ip igmp snooping multicast-table privileged EXEC command output shows otherwise. The workaround is to reduce the number of multicast routes and IGMP snooping groups to less than the maximum supported value. (CSCdy09008)

•IGMP filtering is applied to packets that are forwarded through hardware. It is not applied to packets that are forwarded through software. Hence, with multicast routing enabled, the first few packets are sent from a port even when IGMP filtering is set to deny those groups on that port. There is no workaround. (CSCdy82818)

•When you use the ip access-group interface configuration command with a router access control list (ACL) to deny access to a group in a VLAN, multicast data to the group that is received in the VLAN is always flooded in the VLAN, regardless of IGMP group membership in the VLAN. This provides reachability to directly connected clients, if any, in the VLAN. The workaround is to not apply a router ACL set to deny access to a VLAN interface. Apply the security through other means; for example, apply VLAN maps to the VLAN instead of using a router ACL for the group. (CSCdz86110)

•If an IGMP report packet has two multicast group records, the switch removes or adds interfaces depending on the order of the records in the packet:

–If the ALLOW_NEW_SOURCE record is before the BLOCK_OLD_SOURCE record, the switch removes the port from the group.

–If the BLOCK_OLD_SOURCE record is before the ALLOW_NEW_SOURCE record, the switch adds the port to the group.

The workaround is to enter the clear ip mroute privileged EXEC command on the interface. (CSCef42436)

Routing

These are the routing limitations:

•The switch does not support tunnel interfaces for routed traffic.

•A route map that has an ACL with a Differentiated Services Code Point (DSCP) clause cannot be applied to a Layer 3 interface. The switch rejects this configuration and displays a message that the route map is unsupported. There is no workaround. (CSCea52915)

•A spanning-tree loop might occur if all of these conditions are true:

–Port security is enabled with the violation mode set to protected.

–The maximum number of secure addresses is less than the number of switches connected to the port.

–There is a physical loop in the network through a switch whose MAC address has not been secured, and its BPDUs cause a secure violation.

The workaround is to change any one of the listed conditions. (CSCed53633)

QoS

This is a quality of service (QoS) limitation:

•CSCsb98219

When you use the bandwidth policy-map class command to configure more than one class in a policy map for Class-based Weighted Fair Queuing (CBWFQ), and the committed information rate (CIR) bandwidth for any of the classes is less than 2 percent of the interface rate, the CBWFQ classes in the policy may not receive the configured CIR bandwidths.

There is no workaround, but it is unlikely that a CBWFQ class would be configured with such a low CIR bandwidth.

SPAN and RSPAN

These are the SPAN and Remote SPAN (RSPAN) limitations.

•The egress SPAN data rate might degrade when multicast routing is enabled. The amount of degradation depends on the processor loading. Typically, the switch can egress SPAN at up to 40,000 packets per second (64-byte packets). As long as the total traffic being monitored is below this limit, there is no degradation. However, if the traffic being monitored exceeds the limit, only a portion of the source stream is spanned. When this occurs, the following console message appears: Decreased egress SPAN rate. In all cases, normal traffic is not affected; the degradation limits only how much of the original source stream can be egress spanned. If multicast routing is disabled, egress SPAN is not degraded. There is no workaround. If possible, disable multicast routing. If possible, use ingress SPAN to observe the same traffic. (CSCeb01216)

•Some IGMP report and query packets with IP options might not be ingress-spanned. Packets that are susceptible to this problem are IGMP packets containing 4 bytes of IP options (IP header length of 24). An example of such packets would be IGMP reports and queries having the router alert IP option. Ingress-spanning of such packets is not accurate and can vary with the traffic rate. Typically, very few or none of these packets are spanned. There is no workaround. (CSCeb23352)

•Cisco Discovery Protocol (CDP) and Port Aggregation Protocol (PAgP) packets received by network node interfaces (NNIs) from a SPAN source are not sent to the destination interfaces of a local SPAN session. The workaround is to use the monitor sessionsession_number destination {interface interface-idencapsulation replicate}global configuration command for local SPAN. (CSCed24036)

Trunking

These are the trunking limitations:

•IP traffic with IP options set is sometimes leaked on a trunk port. For example, a trunk port is a member of an IP multicast group in VLAN X but is not a member in VLAN Y. If VLAN Y is the output interface for the multicast route entry assigned to the multicast group and an interface in VLAN Y belongs to the same multicast group, the IP-option traffic received on an input VLAN interface other than one in VLAN Y is sent on the trunk port in VLAN Y because the trunk port is forwarding in VLAN Y, even though the port has no group membership in VLAN Y. There is no workaround. (CSCdz42909).

•For trunk ports or access ports configured with IEEE 802.1Q tagging, inconsistent statistics might appear in the show interfaces counters privileged EXEC command output. Valid IEEE 802.1Q frames of 64 to 66 bytes are correctly forwarded even though the port LED blinks amber, and the frames are not counted on the interface statistics. There is no workaround. (CSCec35100).

VLAN

These are the VLAN limitations:

•If the number of VLANs times the number of trunk ports exceeds the recommended limit of 13,000, the switch can fail.

The workaround is to not configure more than the recommended number of VLANs and trunks. (CSCeb31087)

•A CPUHOG message sometimes appears when you configure a private VLAN. Enable port security on one or more of the ports affected by the private VLAN configuration.

There is no workaround. (CSCed71422)

Open Caveats

This section describes the open caveats in this software release.

•CSCse07183

When you enter the service-policy input parent-policy- map-name interface configuration command to attach a per-port per-VLAN service policy, if two or more classes in the per-port per-VLAN parent policy contain the same VLAN, the attachment fails and this error message appears:

QoS: hqm_qoscli_classmap_filter_update_in_servpolicy Overlapping vlan is not allowed in class and class

This is because classes with overlapping VLANs are not allowed within a per-port per-VLAN parent policy. Overlapping VLAN classes occur when two or more class-maps in a per-port per-VLAN parent policy contain match statements the specify the same VLAN.

The workaround is to consolidate overlapping per-port per-VLAN parent classes with overlapping VLANs and to configure per-port per-VLAN child policy classes to classify and act on traffic as desired.

•CSCse11323

When 256 policy maps are configured globally on the system, the creation of the 257th policy map is rejected. The platform supports a maximum of 256 policy maps. If you then delete some existing policy maps and again configure the rejected policy map, when you try to attach that policy map to an interface, it might be rejected without any descriptive error message explaining the reason for the rejection or with an unexpected and incorrect error message.

The workaround is to delete the problematic policy map and to reconfigure it with a different name. The new policy map should be accepted as expected.

•CSCse85482

If the duplex mode of a GLC-T SFP module that is installed in a Cisco ME-3400G-12CS or ME-3400 2CS switch dual media port is changed from full to half (or the reverse), the mode does not change.

This only occurs if the previous duplex mode was not auto.

These are the workarounds. You only need to do one of these:

–Enter the shut and no shut interface configuration commands.

Change the duplex mode to auto before changing it to half or full.

•CSCsg36159

When using the CLI, you can configure a qualifiedqueue-limit under class-default for the policy map even though the configuration is not supported.

The workaround is to only use qualified queue-limits under nondefault classes.

•CSCsh12472

The switch might display tracebacks similar to this example when an EtherChannel interface port-channel type changes from Layer 2 to Layer 3 or the reverse:

Traceback messages appear if you enter the no switchport interface configuration command to change a Layer 2 interface that belongs to a port channel to a routed port.

There is no workaround.

•CSCsi06228

Although a match cos class-map configuration is only supported on IEE802.1Q trunk ports and should be blocked on IEEE 802.1Q tunnel ports, the switch accepts attaching a policy-map with a match cos class-map statement to a tunnel port.

The workaround is to not attach a policy map with a match cos statement to a tunnel port as this is not a supported configuration.

•CSCsi06399

When a RIP network and IP address are configured on an interface, a traceback error occurs after you enter the shutdown, no shutdown, switchport and no switchport interface configuration commands.

The workaround is to configure the RIP network and the IP address after you configure the interface.

•CSCsi06578

When you clear counters on an interface and then disable storm control on that interface, an incorrect value (an unusually large number) for McastSuppDiscards appears when you enter the show interface counters privileged EXEC command. This can occur when the interface had storm control enabled and experienced traffic with a data rate higher than the storm-control threshold so that storm control is dropping packets.

There is no workaround.

•CSCsi63999

Changing the spanning tree mode from rapid STP to MSTP can cause tracebacks when the virtual port error-disable feature is enabled when the STP mode is changed.

There is no workaround.

•CSCsi75246

An address learned as a supplicant that is aged out by port security aging is never relearned by port security under any of these conditions:

Resolved Caveats

Caveats Resolved in Cisco IOS Release 12.2(37)SE1

These caveats are resolved in Cisco IOS Release 12.2(37)SE1:

•CSCsc19259

The server side of the Secure Copy (SCP) implementation in Cisco IOS contains a vulnerability that allows any valid user, regardless of privilege level, to transfer files to and from an IOS device that is configured to be a Secure Copy server. This vulnerability could allow valid users to retrieve or write to any file on the device's filesystem, including the device's saved configuration. This configuration file may include passwords or other sensitive information.

The Cisco IOS Secure Copy Server is an optional service that is disabled by default. Devices that are not specifically configured to enable the Cisco IOS Secure Copy Server service are not affected by this vulnerability.

This vulnerability does not apply to the Cisco IOS Secure Copy Client feature.

The SCP (Secure Copy Protocol) support is now correctly included in the image. The show file systems and copy privileged EXEC commands now correctly show scp as an option.

•CSCsj19641

The switch no longer drops ARP packets destined to MAC addresses that are close to the MAC address block of the switch.

Caveats Resolved in Cisco IOS Release 12.2(37)SE

These caveats are resolved in Cisco IOS Release 12.2(37)SE:

•CSCsb12598

Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.

Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.

Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.

Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.

This error message no longer appears during authentication when a method list is used and one of the methods in the method list is removed:

AAA-3-BADMETHODERROR:Cannot process authentication method 218959117

•CSCsd85587

A vulnerability has been discovered in a third party cryptographic library which is used by a number of Cisco products. This vulnerability may be triggered when a malformed Abstract Syntax Notation One (ASN.1) object is parsed. Due to the nature of the vulnerability it may be possible, in some cases, to trigger this vulnerability without a valid certificate or valid application-layer credentials (such as a valid username or password).

Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.

The vulnerable cryptographic library is used in the following Cisco products:

Cisco IOS device may crash while processing malformed Secure Sockets Layer (SSL) packets. In order to trigger these vulnerabilities, a malicious client must send malformed packets during the SSL protocol exchange with the vulnerable device.

Successful repeated exploitation of any of these vulnerabilities may lead to a sustained Denial-of-Service (DoS); however, vulnerabilities are not known to compromise either the confidentiality or integrity of the data or the device. These vulnerabilities are not believed to allow an attacker will not be able to decrypt any previously encrypted information.

When a per-port per-VLAN QoS policy is attached to multiple trunk interfaces and one of the interfaces is changed to a routed port, the policy is no longer detached from all interfaces.

•CSCsg30295

When you configure an IP address on a switch virtual interface (SVI) with DCHP and enable DHCP snooping on the SVI VLAN, the switch SVI now obtains an IP address.

•CSCsg36159

The output of the show policy-map and show running-config commands now show the queue-limit configuration for qos-group values above 64. In addition, the switch now properly configures qos-group values above 16.

•CSCsg95349

When multicast routing and IGMP snooping are enabled, a member switch that receives join messages at a high rate can now correctly forward multicast traffic to all the multicast groups after a reload.

•CSCsh80943

An interface configured with a service policy no longer deletes the policy when the port is shut down and then re-enabled.

•CSCsh92834

When trunk ports are participating in a Flex Link configuration, entering a shutdown or no shutdown interface configuration command on the port no longer causes the switch to reload.

•CSCsh92844

Online insertion and removal (OIR) of an SFP module no longer causes error-disabled ports to change to Up or Standby states, resulting in lost data.

•CSCsi00879

When IGMP snooping is enabled, multicast traffic no longer is dropped after a port channel interface link flaps.

•CSCsi30888

The switch no longer halts when configuring link-state tracking with EtherChannel downstream ports or when booting up a switch already configured with link-state tracking with EtherChannel downstream ports.

Updates to the Command Reference

Commands for dynamic Address Resolution Protocol (ARP) inspection were revised in Cisco IOS Release 12.2(37)SE. These changes have not yet been incorporated into the command reference for this release.

ip arp inspection validate

Use the ip arp inspectionvalidate global configuration command to perform specific checks for dynamic Address Resolution Protocol (ARP) inspection. Use the no form of this command to return to the default settings.

ip arp inspection validate {[src-mac] [dst-mac] [ip [allow zeros] ]}

noip arp inspection validate [src-mac] [dst-mac] [ip [allow zeros] ]

Syntax Description

src-mac

Compare the source MAC address in the Ethernet header against the sender MAC address in the ARP body. This check is performed on both ARP requests and responses.

When enabled, packets with different MAC addresses are classified as invalid and are dropped.

dst-mac

Compare the destination MAC address in the Ethernet header against the target MAC address in ARP body. This check is performed for ARP responses.

When enabled, packets with different MAC addresses are classified as invalid and are dropped.

ip

Compare the ARP body for invalid and unexpected IP addresses. Addresses include 0.0.0.0, 255.255.255.255, and all IP multicast addresses.

Sender IP addresses are compared in all ARP requests and responses. Target IP addresses are checked only in ARP responses.

allow-zeros

Modifies the IP validation test so that ARPs with a sender address of 0.0.0.0 (ARP probes) are not denied.

Defaults

No checks are performed.

Command Modes

Global configuration

Command History

Release

Modification

12.2(20)SE

This command was introduced.

12.2(37)SE

The allow-zero keyword was added.

Usage Guidelines

You must specify at least one of the keywords. Each command overrides the configuration of the previous command; that is, if a command enables src-mac and dst-mac validations, and a second command enables IP validation only, the src-mac and dst-mac validations are disabled as a result of the second command.

The allow-zeros keyword interacts with ARP access control lists (ACLs) in this way:

•If you configure an ARP ACL to deny ARP probes, they are dropped even if the allow-zero keyword is specified.

Syntax Description

You can specify a single VLAN identified by VLAN ID number, a range of VLANs separated by a hyphen, or a series of VLANs separated by a comma. The range is 1 to 4094.

acl-match {matchlog | none}

Specify that the logging of packets is based on access control list (ACL) matches.

The keywords have these meanings:

•matchlog—Log packets based on the logging configuration specified in the access control entries (ACE). If you specify the matchlog keyword in this command and the log keyword in the permit or deny ARP access-list configuration command, Address Resolution Protocol (ARP) packets permitted or denied by the ACL are logged.

•none—Do not log packets that match ACLs.

dhcp-bindings {permit | all | none}

Specify the logging of packets is based on Dynamic Host Configuration Protocol (DHCP) binding matches.

The keywords have these meanings:

•all—Log all packets that match DHCP bindings.

•none—Do not log packets that match DHCP bindings.

•permit—Log DHCP-binding permitted packets.

arp-probe

Specify logging of packets permitted specifically because they are ARP probes.

Defaults

All denied or all dropped packets are logged. ARP probe packets are not logged.

Command Modes

Global configuration

Command History

Release

Modification

12.2(20)SE

This command was introduced.

12.2(37)SE

The arp-probe keyword was added.

Usage Guidelines

The term logged means that the entry is placed into the log buffer and that a system message is generated.

The acl-match and dhcp-bindings keywords merge with each other; that is, when you configure an ACL match, the DHCP bindings configuration is not disabled. Use the no form of the command to reset the logging criteria to their defaults. If neither option is specified, all types of logging are reset to log when ARP packets are denied. These are the options:

•acl-match—Logging on ACL matches is reset to log on deny.

•dhcp-bindings—Logging on DHCP binding matches is reset to log on deny.

If neither the acl-match or the dhcp-bindings keywords are specified, all denied packets are logged.

The implicit deny at the end of an ACL does not include the log keyword. This means that when you use the static keyword in the ip arp inspection filter vlan global configuration command, the ACL overrides the DHCP bindings. Some denied packets might not be logged unless you explicitly specify the deny ip any mac any log ACE at the end of the ARP ACL.

Examples

This example shows how to configure ARP inspection on VLAN 1 to log packets that match the permit commands in the ACL:

Switch(config)# arp access-list test1

Switch(config-arp-nacl)# permit request ip any mac any log

Switch(config-arp-nacl)# permit response ip any any mac any any log

Switch(config-arp-nacl)# exit

Switch(config)# ip arp inspection vlan 1 logging acl-match matchlog

You can verify your settings by entering the show ip arp inspection vlanvlan-range privileged EXEC command.

Related Commands

Command

Description

arp access-list

Defines an ARP ACL.

clear ip arp inspection log

Clears the dynamic ARP inspection log buffer.

ip arp inspection log-buffer

Configures the dynamic ARP inspection logging buffer.

show inventory log

Displays the configuration and contents of the dynamic ARP inspection log buffer.

show inventory vlanvlan-range

Displays the configuration and the operating state of dynamic ARP inspection for the specified VLAN.

show ip arp inspection

The output of this command has changed to include the ARP probe information.

This is an example of output from the show ip arp inspection command

Switch# show ip arp inspection

Source Mac Validation : Disabled

Destination Mac Validation : Disabled

IP Address Validation : Enabled

Vlan Configuration Operation ACL Match Static ACL

---- ------------- --------- --------- ----------

1 Enabled Active deny-all No

Vlan ACL Logging DHCP Logging Probe Logging

---- ----------- ------------ -------------

1 Acl-Match All Permit

Vlan Forwarded Dropped DHCP Drops ACL Drops

---- --------- ------- ---------- ---------

1 0 0 0 0

Vlan DHCP Permits ACL Permits Probe Permits Source MAC Failures

---- ------------ ----------- ------------- -------------------

1 0 0 0 0

Vlan Dest MAC Failures IP Validation Failures Invalid Protocol Data

---- ----------------- ---------------------- ---------------------

1 0 0 0

Update to the Regulatory Compliance and Safety Information

The Regulatory Compliance Standards section of the Regulatory Compliance and Safety Information for the Cisco ME 3400 and Cisco ME 2400 Ethernet Access Switches includes this new section:

Attach an ESD-preventive wrist strap to your wrist and to a bare metal surface.

Caution To comply with the Telcordia GR-1089 NEBS standard for electromagnetic compatibility and safety, for Ethernet RJ-45 ports, use only shielded Ethernet cables that are grounded on both ends. In a NEBS installation, all Ethernet ports are limited to intrabuilding wiring.

Caution The intrabuilding ports of the equipment or subassembly is only suitable for connection to intrabuilding or unexposed wiring or cabling. The intrabuilding ports of the equipment or subassembly MUST NOT be metallically connected to interfaces that connect to the OSP or its wiring. These interfaces are designed for use only as intrabuilding interfaces (Type 2 or Type 4 ports as described in GR-1089-CORE, Issue 4), and require isolation from the exposed OSP cabling. The addition of primary protectors is not sufficient protection in order to connect these interfaces metallically to OSP wiring.

Products that have an AC power connection are intended for deployments where an external surge protective device (SPD) is used at the AC power service equipment as defined by the National Electric Code (NEC).

This product is designed for a common bonding network (CBN) installation.

This product can be installed in a network telecommunication facility or location where the NEC applies.

An electrical conducting path should exist between the product chassis and the metal surface of the enclosure or rack in which it is mounted or to a grounding conductor. Electrical continuity should be provided by using thread-forming type mounting screws that remove any paint or nonconductive coatings and establish a metal-to-metal contact. Any paint or other nonconductive coatings should be removed on the surfaces between the mounting hardware and the enclosure or rack. The surfaces should be cleaned and an antioxidant applied before installation.

Updates to the Hardware Installation Guide

Installation Information

Cisco Ethernet Switches are equipped with cooling mechanisms, such as fans and blowers. However, these fans and blowers can draw dust and other particles, causing contaminant buildup inside the chassis, which can result in a system malfunction.

You must install this equipment in an environment as free as possible from dust and foreign conductive material (such as metal flakes from construction activities).

These standard provide guidelines for acceptable working environments and acceptable levels of suspended particulate matter:

•Network Equipment Building Systems (NEBS) GR-63-CORE

•National Electrical Manufacturers Association (NEMA) Type 1

•International Electrotechnical Commission (IEC) IP-20

Update to Appendix C

This information is being added to the "Wiring the DC-Input Power Source" section of Appendix C, "Connecting to DC Power," in the Cisco ME 3400 Ethernet Access Switch Hardware Installation Guide:

Before you wire the DC-input power source, review the warnings in this section and this information:

If the switch software detects that the circuit boards are not receiving power from an internal power supply, the software sends a message like this to the console:

This message means that an internal power supply is not providing power. To receive this alert if power fails on the ME 3400G-12CS-DC switch with two power feeds, we recommend that you connect one feed to the left DC power terminal block and the other to the right DC power terminal block. (See the example in Figure 1.)

Figure 1 Connecting Separate Feeds to Each of the DC Power Terminal Blocks

1

Primary power feed

2

Secondary (redundant) power feed

If you want an alert if an external power supply fails, do not connect feeds to one terminal block and from there connect feeds to the second terminal block. (See the example in Figure 2.) This configuration provides redundant power, and the switch continues to operate if one of the external power supplies fails. However, the software does not send a message to you that an internal power supply has failed.

Figure 2 Connecting Feeds from One Terminal Block to the Second Terminal Block

IP SLAs Support

The Cisco ME 3400 switch includes partial support for Cisco IOS IP Service Level Agreements (IP SLAs) to provide advanced network service monitoring information and collect data pertaining to SLAs verification. The switch can initiate and reply jitter probes. However, the traffic does not follow the queuing configuration that is applied to customer traffic. All locally originated traffic always goes to the same egress queue on the switch port, regardless of the ToS setting for the IP SLAs probe. We recommend the use of an external shadow router to measure latency and packet drop rate (PDR) across the switch.

For performance testing purposes, this configuration was validated:

1. Two switches connected back-to-back.

2. No protocols running on the switch CPUs, including STP.

3. Jitter probe send and receive rate:

a. 50 bidirectional probes sent with each probe consisting of up to 50 packets sent at 1-second intervals.

–Cisco Small Form-Factor Pluggable Modules Compatibility Matrix (not orderable but available on Cisco.com)

–Compatibility Matrix for 1000BASE-T Small Form-Factor Pluggable Modules (not orderable but available on Cisco.com)

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0704R)