Cisco OL-4015-08 Manual de usuario Pagina 242

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 678
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 241
594
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(32)S6
CSCsg80310
Symptoms: Egress packet rate is doubled due to fragmentation. This can be seen in the output of the
show ip mroute vrf vrf-name active command.
Conditions: This symptom has been observed only in multicast VPN environment for 1500 bytes
packets when the egress linecard is based on Layer 3 Forwarding Engine 3 or 5.
Workaround: Increase the MTU of the egress interface (towards the CE) to 1501.
CSCsg80414
Symptoms: MPLS OAM ping and traceroute to TE tunnel tail fail at penultimate hop
Conditions: This symptom has been observed when the penultimate hop P router has 4 port OC48
E4 line card. The egress line card E4+ is 4 port OC48. Move the egress fiber to another port on the
ingress E4 line card and problem is gone.
Workaround: There is no workaround.
CSCsg82004
Symptoms: SPA-1XCHSTM1/OC3 interface does not come up on physical loopback
Conditions: This symptom has been observed with a physical loopback.
Workaround: There is no workaround.
CSCsg95313
Symptoms: A router with a DPT uplink is stuck in reload loop. Every time the router reloads a crash
occurs.
Conditions: This symptom has been observed when some DPT uplinks when using images that have
the latest version of the Rx FPGA (for example: 32.SY1, 32.S5).
Workaround: There is no workaround.
CSCsg95894
Symptoms: The GSR systems incorrectly detect removal of all cards in the system, including the
Active RP. If a Standby RP is present it will automatically assume Active role but it will also not see
any other cards in the system. User-initiated or automatic system reload attempts will fail, the
system being unable to come back up. Only a power cycle of the entire chassis will restore the
system to normal operation - the only difference from the case in which a _permanent_ h/w failure
affecting the MBUS CAN, not covered by this bug.
Conditions: This symptom has been observed in extremely rare occurrences, with no apparent
reason. The only theory that could explain the symptoms and was successfully simulated in the lab
is a temporary failure in the MBUS h/w circuitry.
Workaround: No workaround can presently prevent the service interruption. A manual power cycle
of the chassis would restore normal operation.
Further Problem Description: The MBUS is the backbone of the GSR - a shared CAN bus
connecting all cards in the system. A jam condition on this bus would affect communication between
all cards, effectively bringing the system down with at least the symptoms described above. The jam
condition can happen only if a permanent or temporary failure occurs in the MBUS circuitry. There
is nothing the software can do if the failure is permanent, not even a chassis power cycle would
correct the problem. Sequenced physical OIRs for all cards in the system would be the only way of
identifying the bad one. But at least in some of the temporary failure cases there are chances of
software-driven, automatic recovery, which would reduce or maybe even eliminate completely the
service interruption. This bug was raised to track the implementation of this particular recovery
solution.
Vista de pagina 241
1 2 ... 237 238 239 240 241 242 243 244 245 246 247 ... 677 678

Comentarios a estos manuales

Sin comentarios