Cisco OL-4015-08 Manual de usuario Pagina 252

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 678
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 251
604
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(32)S5
ip access-group 115 in
interface GigabitEthernet 2/0/3
no ip access-group in
Workaround: Add a slight delay between interface configuration changes. This example shows the
changed configuration which has no issues:
interface GigabitEthernet 2/0/0
ip access-group 115 in
<========== Couple of sec delay
interface GigabitEthernet 2/0/1
ip access-group 115 in
<========== Couple of sec delay
interface GigabitEthernet 2/0/3
no ip access-group in
CSCsg03530
Symptoms: On a Cisco 12000-series Internet router running Cisco IOS Release 12.0(32)S or later,
a SIP-600 or SIP-601 line card may exhibit the following error and software-switch packets:
Logs:
*Sep 13 02:39:55 KST: %QM-2-TCAM_ERROR: TCAM pgm error(46): LC based QOS Mgr failed
*Sep 13 02:39:55 KST: %QM-4-SW_SWITCH: Interface GigabitEthernet3/0/0.36 routed
traffic will be software switched in egress direction(s)
Conditions: This symptom occurs when the following are present on the same line card.
1. A policy-map configured on DOWN (but not shutdown) interface and the same policy-map
configured on a SHUTDOWN interface.
2. If any UP interfaces also have the policy-map configured, the error may be seen.
Workarounds: There are three separate workarounds. Only one needs to be chosen:
1. Configure a separate policy-map (with different name) on each interface on that LC. The
problem is only seen when interfaces are sharing the same policy.
Note This may not be feasible for policies using complex class-maps due to increased
resource utilization, especially when ACL matching is used.
2. Ensure SHUT interfaces never have a policy configured. Remove policies before shutting down
any interface. Bring interfaces up before applying a policy which is also present on other
interfaces.
3. Reload the line card. This needs to be done once each time the router is reloaded (after it comes
up completely). If the LC has been reloaded since the most recent router reboot, the problem
will not be seen.
Recovery from error:
If the error has already been seen on the router, possible modes of recovery are:
1. Reloading the LC will recover the LC and prevent any further problems while the router remains
up. One of the other workaround should also be selected to prevent the symptom when the router
is later rebooted.
2. Shut down all affected interfaces. Shut down any interfaces which are in the DOWN state and
have the policy attached. Remove the policy from all the shutdown interfaces. Now the policy
can be reapplied and interfaces brought back up.
Vista de pagina 251
1 2 ... 247 248 249 250 251 252 253 254 255 256 257 ... 677 678

Comentarios a estos manuales

Sin comentarios