Symptom: The system allows configuration of more than 16 VRFs.
Conditions: After you configure more than 16 VRFs, the system does not display the error message
Max VRF limit (16) reached !!! and creates the VRF.
Workaround: There is no workaround for this issue.
Symptom: The show power inline command on the ESM can display incorrect power values for Available/Used.
Conditions: This issue has been observed when ESM PoE ports are connected to Powered Device (PD) simulators such as Sifos simulators.
Workaround: Reload the ESM, or perform a shut down/no shut down of the interfaces connected to the Sifos simulator until the used power is zero. Wait for the power negotiation to stabilize every time you turn the interfaces on and off, then shut down all interfaces. The switch should return all power reserved.
Check the PoE values on individual ports using the show power inline Fastethernet 0/<1-4> detail command that lists the actual power allocated and used by that PD.
Symptom: Redundant PRP packets on the same PRP link are not filtered out by the switch.
Conditions: PRP is a redundancy protocol that allows the same PRP-tagged packet to be sent on two separate PRP-enabled Ethernet switch ports. Upon receiving these two packets, the switch will remove one of them. However, PRP does not allow more than one identical packet on each link. Identical packets (two or more) appearing on the same link will NOT be filtered out.
Workaround: This is a fundamental limitation of PRP duplicate discard and there is no workaround.
Symptom: In a PTP over PRP configuration, Gi0/1 is not able to read the Gi0/2 phy timestamp.
Conditions: When the PRP channel is configured, PTP traffic will not go to the LAN B port.
Workaround: In this PRP release, because of hardware limitations, PTP packets will not have redundancy (redundancy of PTP packets is not implemented according to the specification). However, because most of the uplink ports need to connect to the grand master clock in some of the network topology, PTP packets are allowed to tunnel through the PRP pair ports.
Due to the system design, in this release, PRP only supports PTP packets to be tunneled to the PRP LAN A port.
In the network design, you can put a grand master clock in LAN A, which provides the time source for the downlink port slave.
Symptom: Occasionally, when one of the two PRP LAN cables are disconnected (causing a LINK_DOWN condition) and then reconnected, a small number of packet drops and/or CRC errors may be observed on the PRP LAN link that did not go down. The number of packet drops may be in the 1-4 range, and the number of CRC errors may be in the 1-2 range.
CRC errors and packet drops on the link that was taken down may also occur, but of course these are expected (due to LINK_DOWN).
Conditions: This condition will worsen as the traffic rate increases.
Workaround: Do not take the link down. For example, you can add a small Ethernet switch to ensure that both PRP links stay up even in the event of network disturbance.
Symptom: Tracebacks were seen while configuring a backup interface on the ESM.
Conditions: Tracebacks were seen while issuing the default int interface-type interface-number command on an interface with switchport backup interface configured on the GRWIC-D-ES.
Workaround: Use the no switchport backup interface command instead of the default int interface-type interface-number command.
Accessing Bug Search Tool
You can use the Bug Search Tool to find information about caveats for this release, including a description of the problems and available workarounds. The Bug Search Tool lists both open and resolved caveats.
To access Bug Search Tool, you need the following items:
- Internet connection
- Web browser
- Cisco.com user ID and password
To access the Bug Search Tool, enter the following URL:
To access the Bug Search Tool to search on a specific caveat, enter the following URL: