In the Cisco IPS Threat Defense Bulletin 6-21-2012, there is listed a problem with IOS Release 15.0(1)M8 and the issue described in the caveat CSCtz27137:
IOS IPS Important Notice
IOS IPS customers running version 12.4T, 15.0M, or 15.1M - a critical software defect has been identified which may cause your router to reload and be stuck in a boot loop if IOS IPS signature version S639 or later is installed on the device. Recovery of impacted devices is possible only via a serial console connection through the device's ROMMON mode. For customers who are using IOS IPS signatures S638 or earlier, there is no issues. Customers wishing to upgrade the IOS IPS signature version to S639 or later must first be running a fixed version of IOS on the device prior to upgrading the IPS signatures. Fixed versions of IOS include: 15.2(4)M, 15.1(3)T4, 15.2(3)T1, 15.1(4)M5, 12.4(24)T8 and later. Please refer to defect CSCtz27137
for additional details and steps to recover impacted devices.
I have a 7206VXR router (NPE-G1) running 15.0(1)M8 Advanced IP Services and using IOS IPS signature 638, but would like to update to the latest signature. If I do a search on the Cisco web site for CSCtz27137, it brings up Release 15.1(3)T Caveats only.
This is totally confusing to say the least. Which current IOS for the 7200 series with Advanced IP Services is safe to use with an IPS signature greater than 638? I do not want to lose Zone Based Firewall, EIGRP, NAT, and DHCP services.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...