Cisco OL-4015-08 Manuel d'utilisateur Page 597

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 678
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 596
949
Cross-Platform Release Notes for Cisco IOS Release 12.0S
OL-1617-14 Rev. Q0
Caveats
Resolved Caveats—Cisco IOS Release 12.0(30)S1
Conditions: This symptom is observed when the no access-list command fails while a nonvolatile
generation (NVGEN) occurs.
Workaround: There is no workaround.
CSCef77337
Symptoms: An IPv6 ACL is not properly applied to multiple interfaces.
Conditions: This symptom is observed on a Cisco 12000 series when an IPv6 ACL is applied to
multiple interfaces (that is, four or more) and is modified to exceed layer 4 operating capabilities
that can be supported in hardware.
Workaround: There is no workaround.
CSCef82700
Symptoms: A 4-port Gigabit Ethernet (GE) line card generates TCAM errors when a large QoS
configuration is applied. The following messages are generated:
%QM-2-TCAM_ERROR: TCAM pgm error(8): ACL Merge Failed
%QM-4-SW_SWITCH: Interface GigabitEthernet2/0 routed traffic will be software
switched in egress direction(s)
In addition, when you modify the policy map while it is still attached to the interface of the 4-port
GE line card, the TCAM utilization goes up drastically; however, when you remove the policy map
from the interface, the TCAM utilization is not brought back to zero.
Conditions: These symptoms are observed on a Cisco 12000 series when a child policy map with 75
or more customers is applied and when each child policy has at least 6 queues.
Workaround: Change the default merge algorithm to POD by entering the hw-module slot
slot-number reload command for the slot in which the affected line card is installed.
Alternate Workaround: To avoid problems with the policy map modification, remove the service
policy from the interface, modify the service policy, and reattach the service policy to the interface.
CSCef85231
Symptoms: When SSO redundancy mode is configured and you enter the no form of the mpls ldp
neighbor targeted command to deconfigure a previously configured command, the standby RP may
reload. The symptom may also occur when you enter the no form of the mpls ldp neighbor
implicit-withdraw command. For example, any of the following command sequences may cause
the symptom to occur:
Example 1:
mpls ldp neighbor 10.0.0.1 targeted ldp
...
no mpls ldp neighbor 10.0.0.1 targeted ldp
Example 2:
mpls ldp neighbor 10.0.0.1 targeted ldp
...
no mpls ldp neighbor 10.0.0.1 implicit-withdraw
Conditions: This symptom is observed when the mpls ldp neighbor targeted command is
configured and when the Label Distribution Protocol (LDP) is globally disabled. (By default, LDP
is globally enabled, but it can be disabled by entering the no mpls ip global configuration
command.) The symptom does not occur when other commands are configured for the specific
neighbor, for example, if an MD5 password is configured for the neighbor as illustrated in the
command sequence below:
no mpls ip
Vue de la page 596
1 2 ... 592 593 594 595 596 597 598 599 600 601 602 ... 677 678

Commentaires sur ces manuels

Pas de commentaire