Cisco OL-4015-08 Bedienungsanleitung Seite 424

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 678
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 423
776
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(31)S3
CSCsb25404
Symptoms: The startup configuration in NVRAM is not loaded onto line cards when the router is
manually reloaded.
Conditions: This symptom is observed on a Cisco 12000 series that functions as a multiservice edge
(MSE) router when the ATM Cell Relay over MPLS feature is configured on 500 connections. The
symptom may also occur on other platforms.
Workaround: After the router has been reloaded, cut and paste the initially rejected configuration
onto the line cards.
CSCsb28139
Symptoms: An LDP/BGP adjacency is not formed, and a ping does not go through.
Conditions: This symptom is observed on a Cisco 12000 series that functions in a scaled VPN
environment when an Engine 6 line card faces the core of the MPLS network.
Workaround: Enter the clear ip route * command.
CSCsb38396
Symptoms: When a 2-port or 4-port channelized T3 to DS0 SPA is configured with MFR
subinterfaces and when you enter the shutdown interface configuration command followed by the
no shutdown interface configuration command on one of the subinterfaces, the subinterface does
not come up.
Conditions: This symptom is observed on a Cisco 12000 series.
Workaround: Enter the shutdown interface configuration command followed by the no shutdown
interface configuration command on the main interface to enable the subinterface to come up.
CSCsb39165
Symptoms: A Cisco router may report high CPU usage and memory depletion under a specific
MPLS VPN configuration with static routes.
Conditions: This symptom is observed when equal cost static routes to a subnet point to a next hop
address and there is a summary route that covers one of the next hops pointing to Null0.
If the directly connected route to the next hop is terminated because the interface goes down, the
original route recurses to Null0 while the route recursing through the interface that is still up remains
in the routing table. The end result is that the route now points to both Null0 and to a valid interface
that is up, causing an MPLS recursion problem that results in high CPU usage and memory
depletion.
The following is an example configuration:
ip route a.a.a.a b.b.b.b y.y.y.y
ip route a.a.a.a b.b.b.b z.z.z.z
ip route y.y.y.y mask Null0
If the directly connected route y.y.y.y is removed the a/b subnet recurses through the y.y.y.y/mask
route to Null0.
Workaround: Use routes that point to both a next hop and an egress interface, as in the following
example:
ip route a.a.a.a b.b.b.b interfaceY y.y.y.y
ip route a.a.a.a b.b.b.b interfaceZ z.z.z.z
Workaround: There is no workaround.
Seitenansicht 423
1 2 ... 419 420 421 422 423 424 425 426 427 428 429 ... 677 678

Kommentare zu diesen Handbüchern

Keine Kommentare