Cisco Cisco IOS Software Release 12.4(23) 릴리즈 노트
427
Caveats for Cisco IOS Release 12.4
OL-7656-15 Rev. J0
Resolved Caveats—Cisco IOS Release 12.4(10b)
Workaround: Configure an applet to enter the buffer values again after a reload. A sample applet
would be:
would be:
event manager applet add-buffer
event syslog occurs 1 pattern ".*%SYS-5-RESTART: System restarted --.*"
action 1.0 cli command "enable"
action 2.0 cli command "configure terminal"
action 3.0 cli command "buffers particle-clone 16384"
action 4.0 cli command "buffers header 4096"
action 5.0 cli command "buffers fastswitching 8192"
action 6.0 syslog msg "Reinstated buffers command"
•
CSCsg03830
Symptoms: The tacacs-server directed-request command appears in the running configuration
when is should be disabled. When you disable the command by entering no tacacs-server
directed-request and reload the router, the command appears to be enabled once more.
when is should be disabled. When you disable the command by entering no tacacs-server
directed-request and reload the router, the command appears to be enabled once more.
Conditions: This symptom is observed on a Cisco router that runs a Cisco IOS software image that
integrates the fix for CSCsa45148, which disables the tacacs-server directed-request command by
default.
integrates the fix for CSCsa45148, which disables the tacacs-server directed-request command by
default.
A list of the affected releases can be found at
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa45148. Cisco IOS
software releases that are not listed in the “First Fixed-in Version” field at this location are not
affected.
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa45148. Cisco IOS
software releases that are not listed in the “First Fixed-in Version” field at this location are not
affected.
Temporary Workaround: Each time after you have reloaded the router, disable the command by
entering no tacacs-server directed-request.
entering no tacacs-server directed-request.
•
CSCsg48183
Symptoms: A router may unexpectedly send an ARP request from all its active interfaces to the
nexthop of the network of an SNMP server.
nexthop of the network of an SNMP server.
Conditions: This symptom is observed on a Cisco router that has the snmp-server host command
enabled after any of the following actions occur:
enabled after any of the following actions occur:
–
You reload the router.
–
A switchover of the active RP occurs.
–
You enter the redundancy force-switchover main-cpu command.
Workaround: There is no workaround.
•
CSCsg48725
Symptoms: A TLB exception may occur on a Cisco platform that functions as a PE router in an
MPLS environment, and the following error message may be generated:
MPLS environment, and the following error message may be generated:
TLB (load or instruction fetch) exception, CPU signal 10 (BadVaddr : DEADBEF3)
Conditions: This symptom is observed on a Cisco platform when TACACs accounting and
authorization is enabled and when the TACACs server is reachable through the global routing table.
authorization is enabled and when the TACACs server is reachable through the global routing table.
Workaround: Disable AAA. Is this not an option, there is no workaround.