Cisco OL-4015-08 Instrukcja Użytkownika Pobierz pdf (Strona 647)

999

Cross-Platform Release Notes for Cisco IOS Release 12.0S

OL-1617-14 Rev. Q0

Caveats

Resolved Caveats—Cisco IOS Release 12.0(30)S

• CSCef20651

Symptoms: Pings with the ToS bits set to 00, 10, 1F, 20, 2F, 30, 3F.... E0, EF, F0, or FF function fine

but pings with any other ToS bit values fail.

Conditions: This symptom is observed in a configuration in which one CE router connects to a

Cisco 10000 series that functions as a PE router and that connects via a Gigabit Ethernet interface

to another Cisco 10000 series that also functions as a PE router. This PE router connects, in turn, to

another CE router. The pings drop when tag disposition occurs, but not when imposition occurs.

Workaround: There is no workaround.

• CSCef20996

Symptoms: An SNMP query on cbQosREDClassCfg objects may take up a very large part of the

CPU utilization of a router. Depending on the overall CPU utilization and query frequency, some

side effects such as CPU hogs may occur.

Conditions: This symptom is observed on a Cisco router that runs Cisco IOS Release 12.0 S.

Workaround: There is no workaround.

• CSCef21262

Symptoms: An MPLS static label that is configured as an outgoing label is not installed in the MPLS

forwarding table.

Conditions: This symptom is observed on a Cisco router that runs Cisco IOS Release 12.0(29)S

when a static label is assigned as an outgoing label for a FEC by entering the mpls static binding

ipv4 prefix mask output nexthop label command. The statically configured outgoing label is not

installed in the MPLS forwarding table.

Note that a static label that is assigned as a local label is properly installed in the MPLS forwarding

table.

Workaround: Configure an LDP session to the next hop router over the next hop interface, and

configure the next hop router to prevent it from advertising the label for the impacted prefix by

entering the mpls ldp advertise-labels command.

• CSCef22069

Symptoms: On a Cisco 12000 series that functions as an egress PE router in an MPLS VPN network,

after the customer-facing Gigabit Ethernet line card is reloaded, the ingress line card that receives

an incoming VPN label with a destination with a glean adjacency (which requires an ARP) without

a BGP session may not properly complete the adjacency, causing traffic to be dropped.

Conditions: This symptom is mostly observed with static recursive route configurations. To recover

from the symptom, manually ping the interface of the CE router from the adjacent PE router.

Workaround: Configure the static ARP entries for the nexthop router that is configured in the static

recursive routes.

• CSCef22498

Symptoms: When MPLS VPN is configured over IP tunnels and IP packets of a certain size (for

example, 41 bytes) pass via the tunnel, the following error messages are generated on the customer

facing interface (CFI) of a line card:

%EE48-3-BM_ERRS: ToFab BM PLIM error 2000 %EE48-3-BM_ERR_DECODE: ToFab PLIM

radar_plim_max_len_err

These errors are followed by a reset of the hardware forwarding engine, and the line card stops

responding to fabric pings.

Conditions: This symptom is observed on a Cisco 12000 series when MPLS VPN is configured over

IP tunnels.

1 2 ... 642 643 644 645 646 647 648 649 650 651 652 ... 677 678

Komentarze do niniejszej Instrukcji

Brak uwag

Cisco OL-4015-08 Instrukcja Użytkownika Strona 647

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Networking Cisco OL-4015-08