IPV6 Migration on s72033-adventerprisek9_wan-mz.122-18.SXE6b.bin ios image

Hi,
Can Cisco 7600-7609 model router support ipv6 and NAT64. and in my router ios is s72033-adventerprisek9_wan-mz.122-18.SXE6b.bin".whether i have to upgrade the ios version?

Hi there,
You platform does support IPv6, but the NAt64 feature is currently only available on IOS-XE (ISR, CSR and ASR).
http://tools.cisco.com/ITDIT/CFN/jsp/by-feature-technology.jsp
cheers,
Seb.

Similar Messages

Can I upgrade FWSM 4.0.3 to 4.0.17 with Chassis IOS s72033-adventerprisek9_wan-mz.122-33.SXH4.bin ?

Hi,
Can I upgrade FWSM 4.0.3 to 4.0.17 with Chassis IOS s72033-adventerprisek9_wan-mz.122-33.SXH4.bin ?
In chassis's slot we have ACE and FWSM slot also. if I will upgrade chassis it will reboot ACE too.
I do not want to reload Chassis.
Thanks,
Shain Bharati

Hi Shain
I upgraded my client's Cisco FWSM from 4.0.3 to 4.1.7 few months ago, and everything was good. I didn't have to do incremental upgrade as proposed by Cisco (best practise). This saves time because in the real world, we don't normally have the luxury of long maintenance window (in a non-HA environment).
However, if you choose to upgarde to 4.0.17, that's fine too. The upgrade has no bearing to the IOS version currently running in your C6509 chassis. This is because the FWSM runs on its' own operating system.
For further details on this, you could refer to http://www.cisco.com/en/US/docs/security/fwsm/fwsm41/release/notes/fwsmrn41.html
If you ask me personally, go for 4.1.9 as your FWSM will then be covered with the latest bug fixes.
P/S: If you think this comment is helpful, please do rate them accordingly.

CSM 4.2(1) e CIsco7609 s72033-pk9sv-mz.122-18.SXD5.bin

WE have idle=1 under vserver for traffic UDP, but the real change after 4seconds and not after 1 second. It is possible?Thanks
Ira

The minimum idle timeout is 4.
0 means infinite and all values below 4 are swaped with a value of 4.
You can see the current value with the following command:
gdufour-cat6k-2(config-module-csm)#vser test
gdufour-cat6k-2(config-slb-vserver)#idle ?
<0-13500000> idle timer value in seconds (0 is infinite(!!) default is 3600)
gdufour-cat6k-2(config-slb-vserver)#idle 1
gdufour-cat6k-2#sho mod csm 3 vser name test det
TEST, type = SLB, state = OUTOFSERVICE, v_index = 15
virtual = 1.1.1.1/32:0 unidir, UDP, service = NONE, advertise = FALSE
idle = 4, replicate csrp = none, vlan = ALL,
^^^^^^^^^
However, I have to admit this is strange to allow the configuration of a value of 1 and then silently change the value to 4.
I'll check what we can do.
Regards,
Gilles.

IPv6 Migration DC

Hi Team,
We are maintaining a small size Data Center for hosting and shared services for multiple customers. Currently we are running on IPv4 , we want to migrate into IPv6. Please let us know the best option and best technology to use for our infrastructure. Our infrastructure is little complex. Please help me in a smoother way how to proceed further to acheive to IPv6.
Thank You in advance.
Regards,
Kiran Malla.

Hi,
Start by deploying dual stack IPv4/IPv6 across your network. See the following guide for details:
http://www.cisco.com/en/US/products/ps6553/product_at_a_glance_list.html
Dual stack has the following benefits:
Native dual stack does not require any tunneling mechanisms on internal networks
Both IPv4 and IPv6 run independent of each other
Dual stack supports gradual migration of endpoints, networks, and applications
Don't forget to rate all posts that are helpful.

High Memory in Cisco IOS upto 122-55.SE9.bin

Hi,
We have Cisco 2960TCL switches in our environment which have 64MB DRAM and 32MB default memories. When we are going to upgrade their IOS on
122-55-XX or upper builds then switch utilized 65% of its memory but when we installed IOS on 122-53-XX or lower builds switch utilize 33% - 35 % of their memory.
I do not think its bug type of issue.
Kindly advice me on this.
BR,
Arshad

Hi,
This can be expected since the newer versions will have more features and the *Init* process holding memory has gone up on some of them.
Hope this helps.

Cisco 7606 FIB Protocol Allocation mismatch after mls cef maximum-routes command

Hi,
we are trying to fine tune the mls cef maximum-routes without success for ipv4 on our Cisco 7606 router equiped like this:
Mod Ports Card Type Model Serial No.
2 24 CEF720 24 port 1000mb SFP WS-X6724-SFP SAL09169CP0
6 2 Supervisor Engine 720 (Active) WS-SUP720-3BXL SAL10370YH7
Mod MAC addresses Hw Fw Sw Status
2 0013.c38b.ed9c to 0013.c38b.edb3 2.2 12.2(14r)S5 12.2(33)SRC1 Ok
6 0017.9441.b750 to 0017.9441.b753 5.2 8.4(2) 12.2(33)SRC1 Ok
Mod Sub-Module Model Serial Hw Status
2 Centralized Forwarding Card WS-F6700-CFC SAL09159C8T 2.0 Ok
6 Policy Feature Card 3 WS-F6K-PFC3BXL SAL10360CJ0 1.8 Ok
6 MSFC3 Daughterboard WS-SUP720 SAL10360GNX 2.5 Ok
the show version is like this:
System image file is "bootdisk:c7600s72033-adventerprisek9-mz.122-33.SRC1.bin"
We tryied to set the value of the ipv4 FIB TCAM to 720k with this command:
mls cef maximum-routes ip 720
and then to save the configuration we used the "write" command. This was the output after we wrote the configuration:
FIB TCAM maximum routes :
=======================
Current :-
IPv4 + MPLS - 512k (default)
IPv6 + IP Multicast - 256k (default)
User configured :-
IPv4 - 720k
MPLS - 16k (default)
IPv6 + IP Multicast - 144k (default)
Upon reboot :-
IPv4 - 720k
MPLS - 16k (default)
IPv6 + IP Multicast - 144k (default)
so we reloaded the router to get the new value.
when the router was up again it start to reload each 4 minutes. The FIB TCAM value was:
show mls cef maximum-routes
Reload scheduled for 13:50:09 DST Wed Aug 13 2014 (in 2 minutes and 51 seconds)
Reload reason: FIB Protocol Allocation mismatchFIB TCAM maximum routes :
=======================
Current :-
IPv4 + MPLS - 512k (default)
IPv6 + IP Multicast - 256k (default)
User configured :-
IPv4 + MPLS - 512k (default)
IPv6 + IP Multicast - 256k (default)
Upon reboot :-
IPv4 + MPLS - 512k (default)
IPv6 + IP Multicast - 256k (default)
We know that our cisco is able to handle up to 1M of ipv4 routes inside the TCAM but we cannot set more than 512k ipv4 routes.
Why the router doesn't accept the new value?
Thanks
http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/117712-problemsolution-cat6500-00.html
http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/116132-problem-catalyst6500-00.html
https://supportforums.cisco.com/discussion/12250356/recommended-value-7600-ipv4-fib-tcam

Hi Paolo,
#sho ver
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXI13, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Tue 11-Mar-14 04:53 by prod_rel_team
ROM: System Bootstrap, Version 12.2(17r)S2, RELEASE SOFTWARE (fc1)
punk.gs2 uptime is 17 hours, 55 minutes
Uptime for this control processor is 17 hours, 55 minutes
Time since punk.gs2 switched to active is 17 hours, 54 minutes
System returned to ROM by reload at 22:32:30 BST Mon Sep 1 2014 (SP by reload)
System restarted at 22:35:24 BST Mon Sep 1 2014
System image file is "disk0:s72033-adventerprisek9_wan-mz.122-33.SXI13.bin"
Last reload reason: Reload Command
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco WS-C6504-E (R7000) processor (revision 2.0) with 983008K/65536K bytes of memory.
Processor board ID FOX11270F1B
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from power-on
11 Virtual Ethernet interfaces
50 Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
#remote command switch show version
Cisco IOS Software, s72033_sp Software (s72033_sp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXI13, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Tue 11-Mar-14 05:09 by prod_rel_team
ROM: System Bootstrap, Version 8.5(4)
punk.gs2 uptime is 17 hours, 55 minutes
Time since punk.gs2 switched to active is 17 hours, 55 minutes
System returned to ROM by reload at 22:32:30 BST Mon Sep 1 2014
System restarted at 22:34:17 BST Mon Sep 1 2014
System image file is "disk0:s72033-adventerprisek9_wan-mz.122-33.SXI13.bin"
Last reload reason: Reload Command
cisco Catalyst 6000 (R7000) processor with 983008K/65536K bytes of memory.
Processor board ID FOX11270F1B
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
50 Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.
500472K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
Hope that helps.

Idsm-2 problem: sensor upgrade from 4.1 to 5 or higher

Hi all,
I have a problem with my IDSM-2 module. I'm trying to sensor upgrade from IDS to IPS software (from 4.1 version to 5.x or higher).
If I do this from sensor under "admin user" and use major patch - IPS-K9-maj-5.0-1e-S149.rpm.pkg then I receive error:
"Error: idsPackageMgr: digital signature of the update file was not valid, use CCO to replace corrupted file ".
But file "IPS-K9-maj-5.0-1e-S149.rpm.pkg" is NOT corrupted. I cheked it under "service user" with md5sum utility - checksum is correct.
If I try to upgrade from maintance mode (ie re-image with wipe all information in application partition) then I receive:
"Application image upgrade complete. You can boot the image now.
Partition upgraded successfully"
Next, I'm reboot IDSM-2 module and receive:
"000133: Sep 7 15:10:18.622 MSK/MDD: %HA_EM-6-LOG: Mandatory.go_bootup.tcl: GOLD EEM TCL policy for boot up diagnostic
000134: Sep 7 15:10:18.290 MSK/MDD: %DIAG-SP-3-MAJOR: Module 4: Online Diagnostics detected a Major Error. Please use 'show diagnostic result <target>' to see test results.
000135: Sep 7 15:10:18.294 MSK/MDD: %CONST_DIAG-SP-3-BOOTUP_TEST_FAIL: Module 4: TestPCLoopback failed on port(s) 3-4
000136: Sep 7 15:10:19.170 MSK/MDD: %OIR-SP-3-LC_FAILURE: Module 4 has Major online diagnostic failure, Card will be reset to re-run diagnostic. Please check sup-bootflash diaginfo file for previous detailed diagnostic result.
000137: Sep 7 15:10:19.170 MSK/MDD: %OIR-SP-3-PWRCYCLE: Card in module 4, is being power-cycled 'off (Diagnostic Failure)'
000138: Sep 7 15:10:19.170 MSK/MDD: %C6KPWR-SP-4-DISABLED: power to module in slot 4 set off (Diagnostic Failure)"
ie module go to the "PwrDown" state.
I try to upgrade for next firmware:
IPS-K9-maj-5.0-1e-S149.rpm.pkg
IPS-IDSM2-K9-sys-1.1-a-7.0-5a-E4.bin.gz
IPS-K9-7.0-5a-E4.pkg
IPS-K9-maj-5.0-1e-S149.rpm.pkg
WS-SVC-IDSM2-K9-sys-1.1-a-5.0-1.bin.gz
and did not get success
chassis - 6509-e, sup - VS-S720-10G + VS-F6K-PFC3C, ios - s72033-adventerprisek9_wan-mz.122-33.SXI6.bin
maintance software for IDSM-2 module - 3.4(2)m
Could you please help me? Thanks in advance!

I have a problem with my IDSM-2 module. I'm trying to sensor upgrade from IDS to IPS software (from 4.1 version to 5.x or higher). If I do this from sensor under "admin user" and use major patch - IPS-K9-maj-5.0-1e-S149.rpm.pkg then I receive error: "Error: idsPackageMgr: digital signature of the update file was not valid, use CCO to replace corrupted file ". But file "IPS-K9-maj-5.0-1e-S149.rpm.pkg" is NOT corrupted. I cheked it under "service user" with md5sum utility - checksum is correct.
It has been a long time since I've seen a sensor running 4.1 or an upgrade to 5.0(1e) . If I recall correctly, there were some issues with upgrading if you were running a release from the 4.1 train earlier than 4.1(4). Additionally, the upgrade from 4.1 -> 5.0 includes a configuration conversion (due to differences between the software trains), which was prone to failure depending on the presence of certain configuration options.
Unless you absolutely need to keep the existing configuration, you would save yourself time and effort by simply re-imaging the sensor directly to the desired release. Modern (supported) releases would be either 7.0(5a)E4 or 6.2(3)E4.
Next, I'm reboot IDSM-2 module and receive:"000133: Sep 7 15:10:18.622 MSK/MDD: %HA_EM-6-LOG: Mandatory.go_bootup.tcl: GOLD EEM TCL policy for boot up diagnostic000134: Sep 7 15:10:18.290 MSK/MDD: %DIAG-SP-3-MAJOR: Module 4: Online Diagnostics detected a Major Error. Please use 'show diagnostic result ' to see test results.000135: Sep 7 15:10:18.294 MSK/MDD: %CONST_DIAG-SP-3-BOOTUP_TEST_FAIL: Module 4: TestPCLoopback failed on port(s) 3-4000136: Sep 7 15:10:19.170 MSK/MDD: %OIR-SP-3-LC_FAILURE: Module 4 has Major online diagnostic failure, Card will be reset to re-run diagnostic. Please check sup-bootflash diaginfo file for previous detailed diagnostic result.000137: Sep 7 15:10:19.170 MSK/MDD: %OIR-SP-3-PWRCYCLE: Card in module 4, is being power-cycled 'off (Diagnostic Failure)'000138: Sep 7 15:10:19.170 MSK/MDD: %C6KPWR-SP-4-DISABLED: power to module in slot 4 set off (Diagnostic Failure)"
I would try re-imaging the sensor once more using the IPS-IDSM2-K9-sys-1.1-a-7.0-5a-E4.bin.gz System Recovery Image file found here, following the procedure described here. If the module still fails to boot after that (still citing a Diagnostic Failure), try moving it to another slot in the chassis (if possible).
What color is the IDSM-2 Status LED (on front of module) when it is in this state? An RMA may be necessary to resolve this.

Cisco sup720-3bxl crashes

Hello everyone,
4 weeks passed in debugging Cisco SUP720-3BXL crashes and I don't know what to do...
It's new Cisco module without warranty and since first day it crashes when "minimal or complete diagnostic" is turned on during boot.
When manually the diagnostic is executed, it rises up major fault related to TestFabricSnakeForward & TestFabricSnakeBackward only....perhaps because the second sup720 is not installed yet.
I would like to ask you to take a look and help me to figure out what is going on.
* ROMMON System Bootstrap is Version 8.5(4)
* System Bootstrap is Version 12.2(17r)SX7
* Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXJ7, RELEASE SOFTWARE (fc5)
* s72033-adventerprisek9_wan-mz.122-33.SXJ7.bin MD5: 91dd95feac52e580e5ec42e61d8a8269
I'll appreciate any help! Thanks!
Console output while booting up:
cisco WS-C6509-E (R7000) processor (revision 1.2) with 983008K/65536K bytes of memory.
Processor board ID SMG0940NFAT
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
1 Virtual Ethernet interface
26 Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Press RETURN to get started!
*Jul 21 08:45:56.171: % SNMP ID Persistence Error : Unable to open file : No such file or directory
*Jul 21 08:45:58.935: RP: Currently running ROMMON from F2 region
00:01:49: %SYS-5-CONFIG_I: Configured from memory by console
00:01:52: %SYS-5-RESTART: System restarted --
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXJ7, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Sun 09-Feb-14 10:55 by prod_rel_team
*Jul 21 08:44:23.031: %SYS-SP-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output.
*Jul 21 08:45:53.515: SP: SP: Currently running ROMMON from F1 region
*Jul 21 08:46:06.391: %SYS-SP-5-RESTART: System restarted --
Cisco IOS Software, s72033_sp Software (s72033_sp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXJ7, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Sun 09-Feb-14 11:05 by prod_rel_team
00:01:52: %OIR-SP-6-INSPS: Power supply inserted in slot 1
00:01:52: %C6KPWR-SP-4-PSOK: power supply 1 turned on.
00:01:52: %OIR-SP-6-INSPS: Power supply inserted in slot 2
00:01:52: %C6KPWR-SP-4-PSOK: power supply 2 turned on.
00:01:52: %C6KPWR-SP-4-PSREDUNDANTBOTHSUPPLY: in power-redundancy mode, system is operating on both power supplies.
00:01:54: %C6KPWR-SP-4-DISABLED: power to module in slot 3 set off (admin request)
00:01:54: %C6KPWR-SP-4-DISABLED: power to module in slot 4 set off (admin request)
00:01:54: %C6KPWR-SP-4-DISABLED: power to module in slot 7 set off (admin request)
00:01:stop dia55: %FABRIC-SP-5-CLEAR_BLOCK: Clear block option is off for the fabric in slot 5.
00:01:56: %FABRIC-SP-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 5 became active.
00:01:58: %DIAG-SP-6-RUN_MINIMUM: Module 5: Running Minimal Diagnostics...
%Software-forced reload
Early Notification of crash condition..
08:46:23 UTC Mon Jul 21 2014: Breakpoint exception, CPU signal 23, PC = 0x42B8DE98
   Possible software fault. Upon reccurence, please collect
   crashinfo, "show tech" and contact Cisco Technical Support.
-Traceback= 42B8DE98 42B8B9D8 427D20DC 427D2108 425D15B4 42651F54 42651FB0 40AC4A1C 40AC58EC 40AC580C 40AC65E0 42747E40 4273943C 42739658 42B804E4
$0 : 00000000, AT : 44FF0000, v0 : 44580000, v1 : 00000029
a0 : 50AEF658, a1 : 0000F100, a2 : 00000000, a3 : 00000000
t0 : 00000020, t1 : 3400F101, t2 : 3400C100, t3 : FFFF00FF
t4 : 42B80CC0, t5 : 5000DAB0, t6 : 00000000, t7 : 0000323C
s0 : 00000000, s1 : 44E30000, s2 : 5049E2D4, s3 : 0000001F
s4 : 5049E2D4, s5 : 50E1BDB4, s6 : 00000000, s7 : 08F48AC8
t8 : 08028FEC, t9 : 00000000, k0 : 00000000, k1 : 00000000
gp : 44FEA180, sp : 5000DBB0, s8 : 00000000, ra : 42B8B9D8
EPC : 42B8DE98, ErrorEPC : 3EFDBFF7, SREG     : 3400F103
MDLO : 00000000, MDHI     : 00000000, BadVaddr : 00000000
DATA_START : 0x4493E430
Cause 00000824 (Code 0x9): Breakpoint exception
Writing crashinfo to bootflash:crashinfo_RP_20140721-084623-UTC
=== Flushing messages (08:46:23 UTC Mon Jul 21 2014) ===
Buffered messages:
*Jul 21 08:45:56.171: % SNMP ID Persistence Error : Unable to open file : No such file or directory
*Jul 21 08:45:58.935: RP: Currently running ROMMON from F2 region
00:01:49: %SYS-5-CONFIG_I: Configured from memory by console
00:01:52: %SYS-5-RESTART: System restarted --
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXJ7, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Sun 09-Feb-14 10:55 by prod_rel_team
*Jul 21 08:44:23.031: %SYS-SP-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output.
*Jul 21 08:45:53.515: SP: SP: Currently running ROMMON from F1 region
*Jul 21 08:46:06.391: %SYS-SP-5-RESTART: System restarted --
Cisco IOS Software, s72033_sp Software (s72033_sp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXJ7, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Sun 09-Feb-14 11:05 by prod_rel_team
00:01:52: %OIR-SP-6-INSPS: Power supply inserted in slot 1
00:01:52: %C6KPWR-SP-4-PSOK: power supply 1 turned on.
00:01:52: %OIR-SP-6-INSPS: Power supply inserted in slot 2
00:01:52: %C6KPWR-SP-4-PSOK: power supply 2 turned on.
00:01:52: %C6KPWR-SP-4-PSREDUNDANTBOTHSUPPLY: in power-redundancy mode, system is operating on both power supplies.
00:01:54: %C6KPWR-SP-4-DISABLED: power to module in slot 3 set off (admin request)
00:01:54: %C6KPWR-SP-4-DISABLED: power to module in slot 4 set off (admin request)
00:01:54: %C6KPWR-SP-4-DISABLED: power to module in slot 7 set off (admin request)
00:01:55: %FABRIC-SP-5-CLEAR_BLOCK: Clear block option is off for the fabric in slot 5.
00:01:56: %FABRIC-SP-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 5 became active.
00:01:58: %DIAG-SP-6-RUN_MINIMUM: Module 5: Running Minimal Diagnostics...
00:02:08: %DIAG-SP-6-DIAG_STOPPED: Module 5: Diagnostic is stopped.
Queued messages:
00:02:08: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.
00:02:08: %DIAG-SP-6-DIAG_STOPPED: Module 5: Diagnostic is stopped.
Output when "no diagnostic bootup level minimal" is set:
Router#show version
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXJ7, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Sun 09-Feb-14 10:55 by prod_rel_team
ROM: System Bootstrap, Version 12.2(17r)SX7, RELEASE SOFTWARE (fc1)
cisco WS-C6509-E (R7000) processor (revision 1.2) with 983008K/65536K bytes of memory.
Processor board ID SMG0940NFAT
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
1 Virtual Ethernet interface
26 Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
Router#show context
System was restarted by reload at 07:00:32 UTC Sat Jul 19 2014
s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXJ7, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Compiled Sun 09-Feb-14 10:55 by prod_rel_team (current version)
Image text-base: 0x4010132C, data-base: 0x44932210
Stack trace from system failure:
FP: 0x5000DBB0, RA: 0x42B8DE98
FP: 0x5000DBB0, RA: 0x42B8B9D8
FP: 0x5000DBD0, RA: 0x427D20DC
FP: 0x5000DBE8, RA: 0x427D2108
FP: 0x5000DC00, RA: 0x425D15B4
FP: 0x5000DC38, RA: 0x42651F54
FP: 0x5000DC60, RA: 0x42651FB0
FP: 0x5000DC80, RA: 0x40AC4A1C
Fault History Buffer:
s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXJ7, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Compiled Sun 09-Feb-14 10:55 by prod_rel_team
Signal = 23, Code = 0x24, Uptime 00:02:08
$0 : 00000000, AT : 44FF0000, v0 : 44580000, v1 : 00000029
a0 : 50AEF658, a1 : 0000F100, a2 : 00000000, a3 : 00000000
t0 : 00000020, t1 : 3400F101, t2 : 3400C100, t3 : FFFF00FF
t4 : 42B80CC0, t5 : 5000DAB0, t6 : 00000000, t7 : 0000323C
s0 : 00000000, s1 : 44E30000, s2 : 5049E2D4, s3 : 0000001F
s4 : 5049E2D4, s5 : 50E1BDB4, s6 : 00000000, s7 : 08F48AC8
t8 : 08028FEC, t9 : 00000000, k0 : 00000000, k1 : 00000000
gp : 44FEA180, sp : 5000DBB0, s8 : 00000000, ra : 42B8B9D8
Router# show region
Region Manager:
      Start         End     Size(b) Class Media Name
0x08000000 0x0BFFFFFF    67108864 Iomem R/W    iomem
0x40000000 0x4BFFFFFF   201326592 Local R/W    main
0x4010132C 0x4492FFFF    75689172 IText R/O    main:text
0x44932210 0x44FE046F     7004768 IData R/W    main:data
0x44FE0470 0x46E7C50F    32096416 IBss   R/W    main:bss
0x46E7C510 0x4BFFFFFF    85474032 Local R/W    main:heap
0x50000000 0x7FFF7FFF   805273600 Local R/W    more_heap
0x80000000 0x8BFFFFFF   201326592 Local R/W    main:(main_k0)
0xA0000000 0xABFFFFFF   201326592 Local R/W    main:(main_k1)
Free Region Manager:
      Start         End     Size(b) Class Media Name
Router#show stacks
Minimum process stacks:
Free/Size   Name
5692/6000   OIR IOS Process
5652/6000   ISSU Infra API Delayed Registration Process
5608/6000   VS CHASSIS Info
4188/6000   IPC ISSU Versioning Process
2708/6000   IPC ISSU Receive Process
5540/6000   IPC Zone Manager
5680/6000   ICC Retry Q
4020/6000   IPC Split Init
3456/6000   ICC Nego Client
3540/6000   NTI Trigger Instance for EP ID 0x5
5692/6000   CDP BLOB
5332/6000   C6K_POWER_Process
3500/6000   eobc_init_process
924/3000   mcm_ipc_slave_open_session_to_master_process
5552/6000   PM MP Process
10732/12000 EARL INFO CAPABILITY process
5520/6000   Cat6k Stack MIB Init
5296/6000   C6K ENV RP init
2968/6000   c6k ivrfs
4740/6000   SPAN Subsystem
5380/6000   PostOfficeNet
Minimum process stacks:
Free/Size   Name
52756/60000 EEM TCL Proc
54768/60000 EEM Auto Registration Proc
5504/6000   SASL MAIN
11696/12000 cdp init process
8180/12000 Init
4844/6000   Draco DFS Port Registation Proc
3552/6000   IPC LC Port Opener
4488/6000   LCC Configure
5688/6000   MPLS ACL RP CFG Background
5304/6000   TRANGE RP POPULATE NEW PROC
5312/6000   IP ACL RP Background
5360/6000   RADIUS INITCONFIG
2676/6000   draco-oir-process:slot 5
5180/6000   SLB RF Active Proc
5520/6000   Link Status process
5628/6000   URPF stats
Interrupt level stacks:
Level    Called Unused/Size Name
1        1141   7644/9000 Inband Interrupt
2       46719   7112/9000 EOBC Interrupt
3         374   8460/9000 Management Interrupt
4       16781   8536/9000 Console Uart
Interrupt level stacks:
Level    Called Unused/Size Name
5           0   9000/9000 Mistral Error Interrupt
7       94627   8552/9000 NMI Interrupt Handler
System was restarted by reload at 07:00:32 UTC Sat Jul 19 2014
s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXJ7, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Compiled Sun 09-Feb-14 10:55 by prod_rel_team (current version)
Image text-base: 0x4010132C, data-base: 0x44932210
Stack trace from system failure:
FP: 0x5000DBB0, RA: 0x42B8DE98
FP: 0x5000DBB0, RA: 0x42B8B9D8
FP: 0x5000DBD0, RA: 0x427D20DC
FP: 0x5000DBE8, RA: 0x427D2108
FP: 0x5000DC00, RA: 0x425D15B4
FP: 0x5000DC38, RA: 0x42651F54
FP: 0x5000DC60, RA: 0x42651FB0
FP: 0x5000DC80, RA: 0x40AC4A1C
******* Information of Last System Crash **********
Using bootflash:crashinfo_RP.
%Error opening bootflash:crashinfo_RP (File not found)
****** Information of Last System Crash - SP ******
Using sup-bootflash:crashinfo_20140718-103205.
Router#diagnostic start module 5 test C
Diagnostic[Module 5]: Running test(s) 5,8-10,13,17-25 may disrupt normal system operation
Do you want to continue? [no]: yes
Router#
00:20:57: %DIAG-SP-6-SKIP_ONDEMAND_ACTIVE_TO_STANDBY_TEST: Module 5: TestActiveToStandbyLoopback cannot be executed for active device.
00:21:00: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestLoopback{ID=5} ...
00:21:02: %DIAG-SP-6-TEST_OK: Module 5: TestLoopback{ID=5} has completed successfully
00:21:02: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestNewIndexLearn{ID=6} ...
00:21:02: %DIAG-SP-6-TEST_OK: Module 5: TestNewIndexLearn{ID=6} has completed successfully
00:21:02: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestDontConditionalLearn{ID=7} ...
00:21:02: %DIAG-SP-6-TEST_OK: Module 5: TestDontConditionalLearn{ID=7} has completed successfully
00:21:02: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestBadBpduTrap{ID=8} ...
00:21:04: %DIAG-SP-6-TEST_OK: Module 5: TestBadBpduTrap{ID=8} has completed successfully
00:21:04: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestMatchCapture{ID=9} ...
00:21:06: %DIAG-SP-6-TEST_OK: Module 5: TestMatchCapture{ID=9} has completed successfully
00:21:06: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestProtocolMatchChannel{ID=10} ...
00:21:12: %DIAG-SP-6-TEST_OK: Module 5: TestProtocolMatchChannel{ID=10} has completed successfully
00:21:12: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestFibDevices{ID=11} ...
00:21:22: %DIAG-SP-6-TEST_OK: Module 5: TestFibDevices{ID=11} has completed successfully
00:21:22: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestIPv4FibShortcut{ID=12} ...
00:21:22: %DIAG-SP-6-TEST_OK: Module 5: TestIPv4FibShortcut{ID=12} has completed successfully
00:21:22: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestL3Capture2{ID=13} ...
00:21:23: %DIAG-SP-6-TEST_OK: Module 5: TestL3Capture2{ID=13} has completed successfully
00:21:23: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestIPv6FibShortcut{ID=14} ...
00:21:23: %DIAG-SP-6-TEST_OK: Module 5: TestIPv6FibShortcut{ID=14} has completed successfully
00:21:23: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestMPLSFibShortcut{ID=15} ...
00:21:23: %DIAG-SP-6-TEST_OK: Module 5: TestMPLSFibShortcut{ID=15} has completed successfully
00:21:23: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestNATFibShortcut{ID=16} ...
00:21:23: %DIAG-SP-6-TEST_OK: Module 5: TestAclPermit{ID=17} has completed successfully
00:21:23: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestAclDeny{ID=18} ...
00:21:27: %DIAG-SP-6-TEST_OK: Module 5: TestAclDeny{ID=18} has completed successfully
00:21:27: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestQoSTcam{ID=19} ...
00:21:27: %DIAG-SP-6-TEST_OK: Module 5: TestQoSTcam{ID=19} has completed successfully
00:21:27: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestL3VlanMet{ID=20} ...
00:21:28: %DIAG-SP-6-TEST_OK: Module 5: TestL3VlanMet{ID=20} has completed successfully
00:21:28: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestIngressSpan{ID=21} ...
00:21:28: %DIAG-SP-6-TEST_OK: Module 5: TestIngressSpan{ID=21} has completed successfully
00:21:28: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestEgressSpan{ID=22} ...
00:21:28: %DIAG-SP-6-TEST_OK: Module 5: TestEgressSpan{ID=22} has completed successfully
00:21:28: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestNetflowInlineRewrite{ID=23} ...
00:21:30: %DIAG-SP-6-TEST_OK: Module 5: TestNetflowInlineRewrite{ID=23} has completed successfully
00:21:30: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestFabricSnakeForward{ID=24} ...
00:21:31: %DIAG-SP-3-TEST_FAIL: Module 5: TestFabricSnakeForward{ID=24} has failed. Error code = 0x6F (DIAG_FABRIC_SNAKE_EXTRNL_ERROR)
00:21:31: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestFabricSnakeBackward{ID=25} ...
00:21:33: %DIAG-SP-3-TEST_FAIL: Module 5: TestFabricSnakeBackward{ID=25} has failed. Error code = 0x6F (DIAG_FABRIC_SNAKE_EXTRNL_ERROR)
00:21:33: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestFirmwareDiagStatus{ID=32} ...
00:21:33: %DIAG-SP-6-TEST_OK: Module 5: TestFirmwareDiagStatus{ID=32} has completed successfully
00:21:33: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestOBFL{ID=40} ...
00:21:33: %DIAG-SP-6-TEST_OK: Module 5: TestOBFL{ID=40} has completed successfully
00:21:33: %DIAG-SP-6-TEST_RUNNING: Module 5: Running TestCFRW{ID=41} ...
00:21:33: %DIAG-SP-3-TEST_SKIPPED: Module 5: TestCFRW{ID=41} is skipped
Router#show diagnostic events
Diagnostic events (storage for 500 events, 62 events recorded)
Number of events matching above criteria = 62
Event Type (ET): I - Info, W - Warning, E - Error
Time Stamp         ET [Card] Event Message
07/21 09:02:02.183 I [5]    Diagnostic is stopped
07/21 09:02:03.419 I [5]    TestTransceiverIntegrity Passed
07/21 09:03:03.255 I [5]    TestUnusedPortLoopback Skipped
07/21 09:04:03.291 I [5]    TestUnusedPortLoopback Skipped
07/21 09:05:03.291 I [5]    TestUnusedPortLoopback Skipped
07/21 09:06:03.291 I [5]    TestUnusedPortLoopback Skipped
07/21 09:07:03.291 I [5]    TestUnusedPortLoopback Skipped
07/21 09:08:03.291 I [5]    TestUnusedPortLoopback Skipped
07/21 09:09:03.291 I [5]    TestUnusedPortLoopback Skipped
07/21 09:10:03.291 I [5]    TestUnusedPortLoopback Skipped
07/21 09:11:03.291 I [5]    TestUnusedPortLoopback Skipped
07/21 09:12:03.303 I [5]    TestUnusedPortLoopback Skipped
07/21 09:13:03.303 I [5]    TestUnusedPortLoopback Skipped
07/21 09:14:03.303 I [5]    TestUnusedPortLoopback Skipped
07/21 09:15:04.447 I [5]    TestUnusedPortLoopback Skipped
07/21 09:16:04.447 I [5]    TestUnusedPortLoopback Skipped
07/21 09:17:04.447 I [5]    TestUnusedPortLoopback Skipped
07/21 09:18:04.447 I [5]    TestUnusedPortLoopback Skipped
07/21 09:18:25.311 E [5]    diag_pf_display_test_result_detail[5]: info_str e
                             mpty
07/21 09:19:04.447 I [5]    TestUnusedPortLoopback Skipped
07/21 09:20:04.447 I [5]    TestUnusedPortLoopback Skipped
07/21 09:21:04.435 I [5]    TestLoopback Passed
07/21 09:21:04.467 I [5]    TestNewIndexLearn Passed
07/21 09:21:04.491 I [5]    TestDontConditionalLearn Passed
07/21 09:21:06.503 I [5]    TestBadBpduTrap Passed
07/21 09:21:08.699 I [5]    TestMatchCapture Passed
07/21 09:21:14.667 I [5]    TestProtocolMatchChannel Passed
07/21 09:21:24.903 I [5]    TestFibDevices Passed
07/21 09:21:24.963 I [5]    TestIPv4FibShortcut Passed
07/21 09:21:25.431 I [5]    TestL3Capture2 Passed
07/21 09:21:25.487 I [5]    TestIPv6FibShortcut Passed
07/21 09:21:25.543 I [5]    TestMPLSFibShortcut Passed
07/21 09:21:25.599 I [5]    TestNATFibShortcut Passed
07/21 09:21:25.659 I [5]    TestAclPermit Passed
07/21 09:21:29.451 I [5]    TestAclDeny Passed
07/21 09:21:29.579 I [5]    TestQoSTcam Passed
07/21 09:21:30.679 I [5]    TestL3VlanMet Passed
07/21 09:21:30.719 I [5]    TestIngressSpan Passed
07/21 09:21:30.771 I [5]    TestEgressSpan Passed
07/21 09:21:32.643 I [5]    TestNetflowInlineRewrite Passed
07/21 09:21:33.247 E [5]    check_diag_packets[5/1]: newpak is NULL!
07/21 09:21:33.375 E [5]    inject_external_snake_test_pkt [5/0]: check_diag_
                             packets failed
07/21 09:21:33.411 E [5]    test_fw_snake_external[5/0]: FORWARD loopback mod
                             e snake test (PARALLEL) failed
07/21 09:21:33.879 E [5]    check_diag_packets[5/1]: newpak is NULL!
07/21 09:21:33.995 E [5]    inject_external_snake_test_pkt [5/0]: check_diag_
                             packets failed
07/21 09:21:34.095 E [5]    test_fw_snake_external[5/0]: FORWARD loopback mod
                             e snake test (PARALLEL) failed
07/21 09:21:34.095 E [5]    TestFabricSnakeForward Failed
07/21 09:21:34.095 E [5]    test_fabric_snake_forward[5]: test_fabric_snake_e
                             xternal failed
07/21 09:21:34.671 E [5]    check_diag_packets[5/18]: newpak is NULL!
07/21 09:21:34.799 E [5]    inject_external_snake_test_pkt [5/17]: check_diag
                             _packets failed
07/21 09:21:34.835 E [5]    test_fw_snake_external[5/17]: BACKWARD loopback m
                             ode snake test (PARALLEL) failed
07/21 09:21:35.283 E [5]    check_diag_packets[5/18]: newpak is NULL!
07/21 09:21:35.399 E [5]    inject_external_snake_test_pkt [5/17]: check_diag
                             _packets failed
07/21 09:21:35.499 E [5]    test_fw_snake_external[5/17]: BACKWARD loopback m
                             ode snake test (PARALLEL) failed
07/21 09:21:35.499 E [5]    TestFabricSnakeBackward Failed
07/21 09:21:35.499 E [5]    test_fabric_snake_backward[5]: test_fabric_snake_
                             external failed
07/21 09:21:35.515 I [5]    TestFirmwareDiagStatus Passed
07/21 09:21:35.515 I [5]    TestOBFL Passed
07/21 09:21:35.515 I [5]    TestCFRW Skipped
07/21 09:21:35.627 I [5]    TestUnusedPortLoopback Skipped
07/21 09:22:35.631 I [5]    TestUnusedPortLoopback Skipped
07/21 09:23:35.631 I [5]    TestUnusedPortLoopback Skipped
Router#

I changed the slot from 5 to 6 but no difference...
I have attached the tech support files.
TechSupport__Before_Running_Diag.txt - Before running manually "diagnostic start module 6 test C"
TechSupport__After_Running_Diag.txt - Before running manually "diagnostic start module 6 test C"
Just did it in case of differences.

Syslog triggered action during 8am – 4pm, Monday – Friday

Hi. I am new to EEM, and have read some postings here before giving this a try. But i Need some help and recommendations.
C6513E Supervisor Engine 720 10GE with s72033-adventerprisek9_wan-mz.122-33.SXH8.bin (does not support some of the command syntax)
C2821 – current IOS no good. What software version would be recommended?
objective: during 8am – 4pm, Monday – Friday, to detect eigrp neighbor, if it goes down, passive the respective interface.
example:
read out Vlan108 from “Neighbor * is down” and execute commands “router eigrp 36” and “passive-interface Vlan108”
May 13 09:32:36: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 36: Neighbor 10.9.3.2 (Vlan108) is down
event manager applet eigrp36_flap
event timer cron cron-entry 0 8 * * 1-5 name MonFri maxrun 28800
event syslog pattern "DUAL-5-NBRCHANGE: IP-EIGRP(0) 36: Neighbor ([^,]+) is down "
action 1.0 regexp "Neighbor $([^,]+)$ is down" $_syslog_msg match vlan
action 2.0 cli command "enable"
action 3.0 cli command "configure terminal"
action 4.0 cli command "router eigrp 36"
action 5.0 cli command "passive interface $vlan"
action 6.0 cli command "exit"
action 7.0 cli command "exit"
The script is version one and must have some issue with it. I haven't been able to test the script, since the platform/IOS listed above cannot support all the command syntax.
Thanks in advance.
N

If this must run on your 6500, then you'll need Tcl. This applet will work natively on IOS 12.4(22)T and higher. For other versions, you'll need to first convert it to Tcl at http://www.marcuscom.com/convert_applet/ and register it as an EEM Tcl policy.
event manager applet passive-eigrp
event syslog pattern "DUAL-5-NBRCHANGE: IP-EIGRP(0) 36: Neighbor.*is down"
action 001 cli command "enable"
action 002 cli command "show clock"
action 003 regexp "([0-9]+):[0-9]+:[0-9]+ [^ ]+ (Mon|Tue|Wed|Thu|Fri)" "$_cli_result" match hour day
action 004 if $hour ge 8
action 005 if $hour lt 16
action 006 regexp "Neighbor [0-9\.]+ .([A-Za-z0-9\.:]+)" $_syslog_msg match intf
action 007 cli command "config t"
action 008 cli command "router eigrp 36"
action 009 cli command "passive interface $intf"
action 010 cli command "end"
action 011 end
action 012 end

6500 Advanced ENT SSH ( Modular )

I have installed this image "s72033-adventerprisek9_wan-vz.122-18.SXF5.bin" for the 6500. After the switch reloaded i got the following message when i issued show version (at the end of show version) ...
"Patching is not available since the system is not running from an installed image. To install please use the "install file" command"...
Any idea?
Thanks in advance
Abd Alqader

Hi Abd Alqader
Cisco IOS Software images offering Software Modularity can run in two different modes-either using a single binary image or an installed image. Running the system from a binary image is what most operators are familiar with: a single binary IOS image serving the switch processor and route processor. In contrast, the system will run from a file system with a directory and file structure in if it is running an installed image. The suggested mode of operation is "installed mode".
Since you are running from a binary image patching is not avalaible.
Here you are the complete story about IOS Modularity in 6500 and how to run in "installed mode":
http://www.cisco.com/en/US/products/hw/switches/ps708/products_white_paper0900aecd80313e09.shtml
HTH

NAM Upgrade Problem

While I was upgrading NAM 2 from ver 3.6 to 4.1 I found that the connection is (Flapping) after the upgrade, then I found the following error on the core. (The NAM module is restarting)
000947: 12w1d: %SNMP-5-MODULETRAP: Module 2 [Down] Trap
000948: 12w1d: %OIR-SP-3-PWRCYCLE: Card in module 2, is being power-cycled 'off (Module not responding to Keep Alive polling)'
000949: 12w1d: %C6KPWR-SP-4-DISABLED: power to module in slot 2 set off (Module not responding to Keep Alive polling)
After checking the error meaning, I have found that the workaround is to restart the module many times!!
But the problem never solved, the problem only is resolved if I restarted the NAM in the (cf:1) mode, otherwise the module keeps restarting.
The following are the output of the show ver:
[email protected]# show ver
NAM application image version: 3.6(1a)
Maintenance image version: 2.1(3)
NAM Daughter Card Micro code version: 1.34.1.28 (NAM)
BIOS Version: 4.0-Rel 6.0.4
Installed patches:
No patches are installed on this system.
And the Version I'm upgrading to is (the same as NAM1):
upgrade ftp://172.17.0.10/c6svc-nam.3-6-1a.bin.gz
Could anyone help to resolve this problem?

The output of the show module on the switch:
#sh module
Mod Ports Card Type Model Serial No.
2 8 Network Analysis Module WS-SVC-NAM-2 SAD070802VL
Mod MAC addresses Hw Fw Sw Status
2 0002.7ee5.048c to 0002.7ee5.0493 1.0 7.2(1) 3.6(1a) Ok
Mod Online Diag Status
2 Pass
The output of the show Version on the switch:
#sh ver
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXI1, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Sat 28-Mar-09 10:30 by prod_rel_team
ROM: System Bootstrap, Version 12.2(17r)SX5, RELEASE SOFTWARE (fc1)
XCC_CAI01_CORE02 uptime is 13 weeks, 2 days, 13 hours, 20 minutes
Uptime for this control processor is 13 weeks, 2 days, 13 hours, 37 minutes
Time since XCC_CAI01_CORE02 switched to active is 13 weeks, 2 days, 13 hours, 36 minutes
System returned to ROM by power cycle at 12:58:02 UTC Tue Jun 16 2009 (SP by power on)
System restarted at 21:57:04 CLT Mon Jun 22 2009
System image file is "sup-bootdisk:s72033-adventerprisek9_wan-mz.122-33.SXI1.bin"
Last reload reason: Unknown reason
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco WS-C6513 (R7000) processor (revision 2.0) with 983008K/65536K bytes of memory.
Processor board ID SAL1306J6JY
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
1 SIP-200 controller (8 E1).
11 Virtual Ethernet interfaces
212 Gigabit Ethernet interfaces
4 Ten Gigabit Ethernet interfaces
12 Serial interfaces
8 Channelized E1 ports
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
Just a small update, the version I'm upgrading to is: upgrade ftp://172.17.0.10/c6svc-nam.4-1-1.bin.gz

Can Ciscoview cause high cpu spikes?

I was using LMS 3.2, Ciscoview to open a view on a 6500 that has 2 WS-SUP720-3B supervisors and is running s72033-adventerprisek9_wan-mz.122-33.SXH4.bin.
The device was taking a bit to open up, so I clicked it a couple more times and a couple of minutes later it finally opened.
At the same time I had a telnet session to the device and noted thru sh proc cpu sorted that the SNMP ENGINE had spiked to 95% utilization.
Could Ciscoview be the cause of this? I have found through testing that multiple clicks can cause a small cpu jump (6% - 12%) but I haven't yet reproduced the 95% utilization I saw that day.
Is there an initial discovery that Ciscoview first does to gather it's information that's more intensive than subsquent polling?
-Dave

A couple more questions. Does Ciscoview perform snmpwalks or snmpgets on the device when it is the first time it's contacting it? In the trace logs, I noted:
2009/10/16 22:07:42 EDT TRACE CvDevice: Orig Device Info:
id=192.168.255.21, ipAddr=/192.168.255.21
2009/10/16 22:07:42 EDT TRACE CvDevice: New Device Info:
id=192.168.255.21, ipAddr=192.168.255.21
2009/10/16 22:07:42 EDT TRACE CvDevice: Opening device
192.168.255.21_
polling interval=60...
2009/10/16 22:07:42 EDT TRACE Vector: Getting existing CT....
2009/10/16 22:07:42 EDT TRACE Vector: Index of matched CT is -1
2009/10/16 22:07:42 EDT TRACE Vector: Containment tree not found in the
cache
2009/10/16 22:07:42 EDT TRACE Util: Request: ReqId=47, Cmd=Get,
Session=192.168.255.21Session,
I've noted in attempts to open a device the first time, it takes awhile to open which I'm assuming is the snmpwalk/gets being performed on the device to update its cache. When is this cache cleared? On server reboot?

WS-C6509-E IOS Upgrade

Hello,
I have WS-C6509-E chassis which have 2 Sup ( ( VS-S720-10G )
I want to upgrade s72033-adventerprisek9_wan-mz.122-33.SXI3.bin TO s72033-adventerprisek9_wan-mz.122-33.SXI12.bin
I do not want to come accross with service outage ( boot etc. ).So I want to use ISSU etc. for this operation.
Is ISSU supported with SXI3 ?
Is it possible to direct upgrade SXI3 to SXI12 with ISSU ?
Thanks.

I have 2 Sup. ( active - passive )What is name of this operation ?
It's called "the old fashion way".
1. Make sure you MATCH the MD5 hash value of the IOS file you've downloaded from the Cisco website against the MD5 hash value found in the Cisco website.
2. Copy the IOS from your TFTP to the primary supervisor card: copy tftp sup-bootflash:
3. Copy the IOS from your TFTP to the secondary card.
4. Change the bootstring to boot the new IOS:
conf t
boo sys flash sup-bootflash:new_ios.bin
boo sys flash sup-bootflash:old_ios.bin
end
wr
5. Once you've completed the steps, you force the primary card to boot. Once the primary card boots up, force the secondary card to boot.

Fiber refusing to pass layer 3 traffic / Copper trunk works

Hello everyone
crazy issue here.. everything looks like it should be working but doesnt!
a summary would be our 3750 switches will not trunk over fiber (SM or MM) to our core 6500. They work just fine over copper.
The funny thing is, ONE 3750 works over a SM fiber run.
Our goal is to have redundancy to all switches, 1x copper trunk and 1x fiber trunk. running spanning tree mode rapid-pvst. VTP mode transparent (all VLANs are created manually on all switches --- they exist.)
however, the fiber trunks on 2 switches will only pass layer 2 (CDP neighbor has full detail, mac address-table builds off the 6500) but will not ping the directly connected 6500. we are using cisco brand SFP/GBICs GLC-SX-MM &GLC-LH-SM (we are sure the correct SFP is used with correct fiber type)
debug arp / debug ip packet shows Switch B & C never actually learn the core's mac address and tie it to the IP of 153.29.45.1. all switches have a default gateway of 153.29.45.1.
SWITCH A :
interface GigabitEthernet1/0/48 description CopperTrunk-to-Core switchport trunk encapsulation dot1q switchport trunk native vlan 48 switchport trunk allowed vlan 37,48,172 switchport mode trunk interface GigabitEthernet1/1/1 description FiberTrunk-to-Core switchport trunk encapsulation dot1q switchport trunk native vlan 48 switchport trunk allowed vlan 37,48,172 switchport mode dynamic desirable interface Vlan48
ip address 153.29.45.67 255.255.255.192
no ip redirects
no ip proxy-arp
SWITCH B:
interface GigabitEthernet1/1/1 description FiberTrunk-to-Core switchport trunk encapsulation dot1q switchport trunk native vlan 47 switchport trunk allowed vlan 37,47,172 switchport mode trunk interface GigabitEthernet2/0/48 description CopperTrunk-to-Core switchport trunk encapsulation dot1q switchport trunk native vlan 47 switchport trunk allowed vlan 37,47,172 interface Vlan47 ip address 153.29.45.8 255.255.255.224 no ip redirects no ip proxy-arp
SWITCH C:
interface GigabitEthernet1/0/48 description CopperTrunk-to-Core switchport trunk encapsulation dot1q switchport trunk native vlan 48 switchport trunk allowed vlan 37,48,172 switchport mode trunk interface GigabitEthernet1/1/1description FiberTrunk-to-Core switchport trunk encapsulation dot1q switchport trunk native vlan 48 switchport trunk allowed vlan 37,48,172 switchport mode trunk
interface Vlan48 ip address 153.29.45.81 255.255.255.192no ip redirects no ip proxy-arp
CORE(6500):
interface GigabitEthernet2/40 description Switch_B_Copper switchport switchport trunk encapsulation dot1q switchport trunk native vlan 47 switchport trunk allowed vlan 37,47,172 switchport mode trunk interface GigabitEthernet2/43 description Switch_A_Copper switchport switchport trunk encapsulation dot1q switchport trunk native vlan 48 switchport trunk allowed vlan 37,48,172 switchport mode trunk interface GigabitEthernet2/40 description Switch_C_Copper switchport switchport trunk encapsulation dot1q switchport trunk native vlan 48 switchport trunk allowed vlan 37,48,172 switchport mode trunk
interface GigabitEthernet3/43 description Switch_A_Fiber switchport switchport trunk encapsulation dot1q switchport trunk native vlan 48 switchport trunk allowed vlan 37,48,172 switchport mode trunk interface GigabitEthernet3/40 description Switch_B_Fiber switchport switchport trunk encapsulation dot1q switchport trunk native vlan 47 switchport trunk allowed vlan 36,37,47,172,500 switchport mode trunk interface GigabitEthernet3/44 description Switch_C_Fiber switchport switchport trunk encapsulation dot1q switchport trunk native vlan 48 switchport trunk allowed vlan 37,48,172 switchport mode trunk interface Vlan47 description Internal_Management ip address 153.29.45.1 255.255.255.224 no ip redirects no ip proxy-arp interface Vlan48 description Management ip address 153.29.45.65 255.255.255.192
Summary: copper links work fine on all 3 switches. switch A & B refuse to pass layer 3 data on Fiber trunks. all were recently updated to version 12.2(53r) SE2 (c3740e-universalk9-mz.122-55.SE8.bin). Core is on 12.2 (33) SXI12 (s72033-adventerprisek9_wan-mz.122-33.SXI12.bin).
any suggestions are appreciated.

Leo: here ya go
GigabitEthernet3/43 is up, line protocol is up (connected) Hardware is C6k 1000Mb 802.3, address is 2894.0f57.437a (bia 2894.0f57.437a) Description: FiberTrunk-to-SwitchA MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 1000Mb/s, media type is LH input flow-control is off, output flow-control is off Clock mode is auto ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:08, output 00:00:24, output hang never Last clearing of "show interface" counters never Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 191000 bits/sec, 67 packets/sec 5 minute output rate 752000 bits/sec, 112 packets/sec 92584292 packets input, 25411211351 bytes, 0 no buffer Received 315527 broadcasts (83158 multicasts) 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 0 multicast, 0 pause input 0 input packets with dribble condition detected 148923032 packets output, 114663742745 bytes, 0 underruns 0 output errors, 0 collisions, 6 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier, 0 PAUSE output 0 output buffer failures, 0 output buffers swapped out GigabitEthernet6/1 is down, line protocol is down (notconnect) Hardware is C6k 1000Mb 802.3, address is 001a.a22d.6984 (bia 001a.a22d.6984) Description: FiberTestPort MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, reliability 255/255, txload 0/255, rxload 0/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 1000Mb/s, media type is LH input flow-control is off, output flow-control is off Clock mode is auto ARP type: ARPA, ARP Timeout 04:00:00 Last input 01:52:33, output 01:51:56, output hang never Last clearing of "show interface" counters never Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 218 packets input, 26637 bytes, 0 no buffer Received 182 broadcasts (63 multicasts) 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 0 multicast, 0 pause input 0 input packets with dribble condition detected 9476 packets output, 1084062 bytes, 0 underruns 0 output errors, 0 collisions, 3 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier, 0 PAUSE output 0 output buffer failures, 0 output buffers swapped out
let me know if you'd like to see anything else.

Cisco 6509 with 10G Module

Hello,
We have Cisco 6509 Core Switch with following details & we need to install WS-X6716-10T-3C module in int.
Can some body advise which slot number i should use in 6509 ?
Do i need to upgrade supervisor engine IOS for this ?
Is it hot swapable module & can i install this module in production ?
6509_CORE#sh ver
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXI6, RELEASE SOFTWARE (fc4)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Mon 28-Mar-11 12:09 by prod_rel_team
ROM: System Bootstrap, Version 12.2(17r)SX7, RELEASE SOFTWARE (fc1)
6509_CORE uptime is 2 years, 30 weeks, 1 day, 3 hours, 13 minutes
Uptime for this control processor is 2 years, 30 weeks, 1 day, 1 hour, 44 minutes
Time since AUB_CORE switched to active is 2 years, 30 weeks, 1 day, 1 hour, 44 minutes
System returned to ROM by power cycle at 11:55:23 UTC Wed Apr 27 2011 (SP by power-on)
System restarted at 11:16:22 AST Sun Jun 26 2011
System image file is "sup-bootdisk:s72033-adventerprisek9_wan-mz.122-33.SXI6.bin"
Last reload reason: Reload Command
cisco WS-C6509-E (R7000) processor (revision 1.5) with 983008K/65536K bytes of memory.
Processor board ID SMC1426001S
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
4294967295 Ethernet interfaces
33 Virtual Ethernet interfaces
150 Gigabit Ethernet interfaces
100 Ten Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
6509_CORE#sh module
Mod Ports Card Type                              Model              Serial No.
1   24 CEF720 24 port 1000mb SFP              WS-X6724-SFP       SAL1430P2QU
2   48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX     SAL1429N6XB
3   16 CEF720 16 port 10GE                    WS-X6716-10GE      SAL1430NYUE
4   16 CEF720 16 port 10GE                    WS-X6716-10GE      SAL1430NX5A
5    5 Supervisor Engine 720 10GE (Active)    VS-S720-10G        SAL1430NUJE
7   16 CEF720 16 port 10GE                    WS-X6716-10GE      SAL1645RJTF
Mod MAC addresses                       Hw    Fw           Sw           Status
1 d0d0.fd62.d9e0 to d0d0.fd62.d9f7   4.4   12.2(18r)S1 12.2(33)SXI6 Ok
2 c84c.75b8.596c to c84c.75b8.599b   3.4   12.2(18r)S1 12.2(33)SXI6 Ok
3 001f.6cac.11d0 to 001f.6cac.11df   1.0   12.2(18r)S1 12.2(33)SXI6 Ok
4 5475.d06e.0988 to 5475.d06e.0997   1.0   12.2(18r)S1 12.2(33)SXI6 Ok
5 001e.4a7f.3068 to 001e.4a7f.306f   3.2   8.5(4)       12.2(33)SXI6 Ok
7 fc99.4736.2d80 to fc99.4736.2d8f   1.1   12.2(18r)S1 12.2(33)SXI6 Ok
Mod Sub-Module                  Model              Serial       Hw     Status
1 Distributed Forwarding Card WS-F6700-DFC3C     SAL1430P282 1.4    Ok
2 Centralized Forwarding Card WS-F6700-CFC       SAL1430NRAS 4.1    Ok
3 Distributed Forwarding Card WS-F6700-DFC3C     SAL1430P26L 1.4    Ok
4 Distributed Forwarding Card WS-F6700-DFC3C     SAL1430NZRM 1.4    Ok
5 Policy Feature Card 3       VS-F6K-PFC3C       SAL1429N6B7 1.1    Ok
5 MSFC3 Daughterboard         VS-F6K-MSFC3       SAL1430NN3R 5.0    Ok
7 Distributed Forwarding Card WS-F6700-DFC3C     SAL1644RAZF 1.5    Ok
Mod Online Diag Status
1 Pass
2 Pass
3 Pass
4 Pass
5 Pass
7 Pass

Hello cmarva,
I got power requirement from core switch:
6509_CORE#show power
system power redundancy mode = redundant
system power total =     3795.12 Watts (90.36 Amps @ 42V)
system power used =      2748.06 Watts (65.43 Amps @ 42V)
system power available = 1047.06 Watts (24.93 Amps @ 42V)
                        Power-Capacity PS-Fan Output Oper
PS   Type               Watts   A @42V Status Status State
1    WS-CAC-4000W-INT   3795.12 90.36 OK     OK     on
2    WS-CAC-4000W-INT   3795.12 90.36 OK     OK     on
                        Pwr-Allocated Oper
Fan Type               Watts   A @42V State
1    WS-C6509-E-FAN      210.00 5.00 OK
                        Pwr-Requested Pwr-Allocated Admin Oper
Slot Card-Type          Watts   A @42V Watts   A @42V State State
1    WS-X6724-SFP        162.96 3.88   162.96 3.88 on   on
2    WS-X6748-GE-TX      325.50 7.75   325.50 7.75 on    on
3    WS-X6716-10GE       457.80 10.90   457.80 10.90 on    on
4    WS-X6716-10GE       457.80 10.90   457.80 10.90 on    on
5    VS-S720-10G         338.10 8.05   338.10 8.05 on    on
6    (Redundant Sup)       -     -      338.10 8.05 -     -
7    WS-X6716-10GE       457.80 10.90   457.80 10.90 on    on
system auxiliary power mode = off
system auxiliary power redundancy operationally = non-redundant
system primary connector power limit =   10920.00 Watts (260.00 Amps @ 42V)
system auxiliary connector power limit = 10500.00 Watts (250.00 Amps @ 42V)
system primary power used =              2748.06 Watts (65.43 Amps @ 42V)
system auxiliary power used =            0 Watt
As per Cisco document i require this power WS-X6716-10T-3C: 509.3W (12.1A @ 42V) & from output available power is system power available = 1047.06 Watts (24.93 Amps @ 42V)
Looks like im good to go. Can you verify please ?
http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/product_data_sheet09186a00801dce34.html
Regards,

IPV6 Migration on s72033-adventerprisek9_wan-mz.122-18.SXE6b.bin ios image

Similar Messages

Maybe you are looking for