08-21-2006 05:47 AM - edited 03-10-2019 03:10 AM
Hi Guys,
I need some information!
Is the IDSM2 hot-swappable in a Cisco 6509 Chassis?
Recently I installed the IDSM2 on an Cisco 6509 Chassis (with two Sup720s in SSO mode). But chassis rebooted specifying that the
"%C6K_PLATFORM-2-PEER_RESET: RP is being reset by the SP"
After rebooting the secondary SUP became active.
Can anyone give an explaination for this?
Also Please do let me know whether the IDSM is hot-swappable or not?
Prompt response will be appreciated.
Thanks
Anand
08-21-2006 06:06 AM
Hi,
The proper way to remove IDSM2 blade is to power off @shutdown the blade from switch CLI.
This is because IDSM2 has internal harddisk that need to be shutdown properly. Otherwise, you may corrupt the disk.
For the IDSM2, the term hot-swap is true only if you shut it down properly, then remove it.
Rgds,
AK
08-21-2006 07:43 AM
Well, I understand the power of and remove procedure in IDSM2 blade.
I faced this specific problem when i was "INSERTING" the card the chassis.
So again my question arises.
What do you think?
is there specific requirement when i have two SUPs?
08-21-2006 04:00 PM
What's the IDSM2 operation mode - inline or promiscuous?
Not sure if this is rerlated, and depends on your settings. With inline, traffic may or may not allowed to pass through without mandatory IDSM2 inspection. And if you removed the blade, this could have disconnect the traffic flow (L3 plus other SupEngine processing of the passing traffic). With this, the active SupEngine was unable to communicate and allow passing traffic to get throuigh. This cut-off is making the module isolated, and this could be the reason why the standby SupEngine triggered.
Rgds,
AK
08-21-2006 07:24 PM
well, it is still not configured. It is just inserted into the 6500 Chassis. So whatever is the default config (promiscous).
08-21-2006 09:24 PM
If that the case, maybe it could be other things, even to the extend of bugs.
As you're saying, the blade is properly shutdown and removed from the slot. This make the active SupEngine to go down, and standby takes over.
With fresh idsm2 (not configured), this shouldn't happened. From my experience, I can always remove and put back the module without any issues with SupEngine.
BTW, IDSM2 is confirmed hot-swap, and shouldn't caused any issue to the switch
http://www.cisco.com/en/US/products/hw/modules/ps2706/products_data_sheet09186a00801e55dd.html
Rgds,
AK
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide