Solved: Help, Switch 3750, Assignment master of the stack

Luis Salazar · ‎04-27-2010

Hi Guys,

I have 3x Stacked 3750 switch, Sw1 is the master. I had a problem with the service when I change the assignment of master of the stack. The problem was solved reloading the switch.

The question is why happened this?, what is the problem of change the assignment of master of the stack?, what is the right procedure to do this change?

I really appreciate your comments, i'm sorry for my bad english,

Regards,

Edison Ortiz · ‎04-27-2010

There is no reason for changing the stack master.

I recommend reading the documentation on several ways you could change the stack master

http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_50_se/configuration/guide/swstack.html#wp1234264

Most of the ways are service impacting thus not recommended during production.

View solution in original post

shailesh.h · ‎04-27-2010

STACK Troubleshooting document link provides answer to your problem as well as query what will happen if change the master switch

http://www.cisco.com/en/US/partner/docs/switches/lan/catalyst3750/software/troubleshooting/switch_stacks.html

Shailesh

View solution in original post

Edison Ortiz · ‎04-29-2010

Lots of traceback so an event occurred that caused the outage. I recommend saving that traceback log and opening a TAC case for further troubleshooting.

Switch 2 would have the same config as Switch 1. They are all part of the same stack. During switchover, network services may be impacted but not for long. In you case, the stack was affected by a traceback condition.

Again, opening a TAC case to determine the root cause would be my recommendation..

Regards

Edison.

View solution in original post

Edison Ortiz · ‎04-27-2010

What kind of problems did you encounter?

How did you change the Master assignment?

When the Master stack changes, the MAC Address from the stack also changes which determines the Bridge ID.

This potentially generates a STP calculation throughout your L2 domain.

Without knowing your entire topology, it's very hard to tell what caused the disruption of services without you providing more information and perhaps a diagram.

Regards

Edison.

Luis Salazar · ‎04-27-2010

There was a problem with routing, and sending/recieving packets. personally Ì don`t change the assignment of the master of the stack, it was the personal of thecnical support who informs to me this problem.

They tell me that they changed the master stack, and i assumed that this was the cause of the problem.

They send to me, the 'Show tech' of the switch, i don`t know if this help.

what's the procedure to change the Master assignment? and what is the reason to do that?

Thank you very much for your comments,

Regards,

Edison Ortiz · ‎04-27-2010

There is no reason for changing the stack master.

I recommend reading the documentation on several ways you could change the stack master

http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_50_se/configuration/guide/swstack.html#wp1234264

Most of the ways are service impacting thus not recommended during production.

Luis Salazar · ‎04-29-2010

Hey, thanks a lot for your comments, i have now the situation more clear,

The case is this:

i have 3 sw3750,

Switch   Ports Model              SW Version              SW Image
------   ----- -----              ----------              ----------
     1   26     WS-C3750-24TS      12.2(25)SEB4            C3750-ADVIPSERVICESK
*    2   26     WS-C3750-24TS      12.2(25)SEB4            C3750-ADVIPSERVICESK
     3   26     WS-C3750-24TS      12.2(25)SEB4            C3750-ADVIPSERVICESK

The master is the sw1, but for some reason, the master changed to sw2, i don't think the sw has restarted, or power off and then power on.

------------------ show switch detail ------------------

                                            Current
Switch# Role       Priority     State
--------------------------------------------------------
1       Slave          15        Ready
*2       Master       13        Ready
3       Slave          11        Ready

         Stack Port Status             Neighbors
Switch# Port 1     Port 2           Port 1   Port 2
--------------------------------------------------------
1        Ok         Ok                2        3
2        Ok         Ok                3        1
3        Ok         Ok                1        2

the cause of the problem of the network (the problem of packets, routing), was because the sw2 doesn't has the routes and the configuration tha the sw1 have,, right? so the sw2 doest not know what to do?

the problem solves when the sw's restarted, and then the master it`s again sw1.

this is the log's, taked when the sw2 was the master:

------------------ show logging ------------------

Syslog logging: enabled (0 messages dropped, 1 messages rate-limited, 448 flushes, 0 overruns, xml disabled, filtering disabled)
    Console logging: level debugging, 216431 messages logged, xml disabled,
                     filtering disabled
    Monitor logging: level debugging, 0 messages logged, xml disabled,
                     filtering disabled
    Buffer logging: level debugging, 215994 messages logged, xml disabled,
                    filtering disabled
    Exception Logging: size (4096 bytes)
    Count and timestamp logging messages: disabled
    File logging: file flash:mylog,
        max size 4096, min size 0,
        level critical, 13 messages logged
    Trap logging: level informational, 219182 message lines logged
        Logging to 172.21.100.250, 219165 message lines logged, xml disabled,
               filtering disabled
        Logging to 10.64.100.3, 219165 message lines logged, xml disabled,
               filtering disabled
        Logging to 10.161.100.246, 219165 message lines logged, xml disabled,
               filtering disabled
        Logging to 172.21.100.69, 219165 message lines logged, xml disabled,
               filtering disabled
        Logging to 172.21.100.66, 219165 message lines logged, xml disabled,
               filtering disabled
        Logging to 10.161.100.111, 219165 message lines logged, xml disabled,
               filtering disabled

Log Buffer (4096 bytes):
AMMGR-3-INDEX_ERROR: cam value/mask index 1288491026 is invalid (EEHYP_CS_801-1)
-Traceback= 97CFEC 318318 31C264 31C9E8 31CB88 31CD94 378FCC 37AC28 37A97C 36E860 36F780 36315C 363A4C 75E3A8 7585EC (EEHYP_CS_801-1)
Apr 24 16:07:12: invalid mask index 0xFFFFFFFE, context = 16BA0E8/144bit-context, (EEHYP_CS_801-1)
             first_mask_index = 0x0, last_mask_index = 0x4AF (EEHYP_CS_801-1)
Apr 24 16:07:12: -Traceback= 3182F4 31C264 31C9E8 31CB88 31CD94 378FCC 37AC28 37A97C 36E860 36F780 36315C 363A4C 75E3A8 7585EC (EEHYP_CS_801-1)
Apr 24 16:07:12: %TCAMMGR-3-INDEX_ERROR: cam value/mask index -2 is invalid (EEHYP_CS_801-1)
-Traceback= 97CFEC 318318 31C264 31C9E8 31CB88 31CD94 378FCC 37AC28 37A97C 36E860 36F780 36315C 363A4C 75E3A8 7585EC (EEHYP_CS_801-1)
Apr 24 16:07:12: invalid mask index 0x4CCCCE32, context = 16BA0E8/144bit-context, (EEHYP_CS_801-1)
             first_mask_index = 0x0, last_mask_index = 0x4AF (EEHYP_CS_801-1)
Apr 24 16:07:12: -Traceback= 3182F4 31C264 31C9E8 31CB88 31CD94 378FCC 37AC28 37A97C 36E860 36F780 36315C 363A4C 75E3A8 7585EC (EEHYP_CS_801-1)
Apr 24 16:07:12: %TCAMMGR-3-INDEX_ERROR: cam value/mask index 1288490546 is invalid (EEHYP_CS_801-1)
-Traceback= 97CFEC 318318 31C264 31C9E8 31CB88 31CD94 378FCC 37AC28 37A97C 36E860 36F780 36315C 363A4C 75E3A8 7585EC (EEHYP_CS_801-1)
Apr 24 16:07:16: invalid mask index 0x4CCCD012, context = 16BA0E8/144bit-context, (EEHYP_CS_801-1)
             first_mask_index = 0x0, last_mask_index = 0x4AF (EEHYP_CS_801-1)
Apr 24 16:07:16: -Traceback= 3182F4 31C264 31C9E8 31CB88 31CD94 378FCC 37AC28 37A97C 36E860 36F780 36315C 363A4C 75E3A8 7585EC (EEHYP_CS_801-1)
Apr 24 16:07:16: %TCAMMGR-3-INDEX_ERROR: cam value/mask index 1288491026 is invalid (EEHYP_CS_801-1)
-Traceback= 97CFEC 318318 31C264 31C9E8 31CB88 31CD94 378FCC 37AC28 37A97C 36E860 36F780 36315C 363A4C 75E3A8 7585EC (EEHYP_CS_801-1)
Apr 24 16:07:16: invalid mask index 0xFFFFFFFE, context = 16BA0E8/144bit-context, (EEHYP_CS_801-1)
             first_mask_index = 0x0, last_mask_index = 0x4AF (EEHYP_CS_801-1)
Apr 24 16:07:16: -Traceback= 3182F4 31C264 31C9E8 31CB88 31CD94 378FCC 37AC28 37A97C 36E860 36F780 36315C 363A4C 75E3A8 7585EC (EEHYP_CS_801-1)
Apr 24 16:07:16: %TCAMMGR-3-INDEX_ERROR: cam value/mask index -2 is invalid (EEHYP_CS_801-1)
-Traceback= 97CFEC 318318 31C264 31C9E8 31CB88 31CD94 378FCC 37AC28 37A97C 36E860 36F780 36315C 363A4C 75E3A8 7585EC (EEHYP_CS_801-1)
Apr 24 16:07:16: invalid mask index 0x4CCCCE32, context = 16BA0E8/144bit-context, (EEHYP_CS_801-1)
             first_mask_index = 0x0, last_mask_index = 0x4AF (EEHYP_CS_801-1)
Apr 24 16:07:16: -Traceback= 3182F4 31C264 31C9E8 31CB88 31CD94 378FCC 37AC28 37A97C 36E860 36F780 36315C 363A4C 75E3A8 7585EC (EEHYP_CS_801-1)
Apr 24 16:07:16: %TCAMMGR-3-INDEX_ERROR: cam value/mask index 1288490546 is invalid (EEHYP_CS_801-1)
-Traceback= 97CFEC 318318 31C264 31C9E8 31CB88 31CD94 378FCC 37AC28 37A97C 36E860 36F780 36315C 363A4C 75E3A8 7585EC (EEHYP_CS_801-1)
Apr 24 16:07:20: invalid mask index 0x4CCCD012, context = 16BA0E8/144bit-context, (EEHYP_CS_801-1)
             first_mask_index = 0x0, last_mask_index = 0x4AF (EEHYP_CS_801-1)
Apr 24 16:07:20: -Traceback= 3182F4 31C264 31C9E8 31CB88 31CD94 378FCC 37AC28 37A97C 36E860 36F780 36315C 363A4C 75E3A8 7585EC (EEHYP_CS_801-1)
Apr 24 16:07:20: %TCAMMGR-3-INDEX_ERROR: cam value/mask index 1288491026 is invalid (EEHYP_CS_801-1)
-Traceback= 97CFEC 318318 31C264 31C9E8 31CB88 31CD94 378FCC 37AC28 37A97C 36E860 36F780 36315C 363A4C 75E3A8 7585EC (EEHYP_CS_801-1)
Apr 24 16:07:20: invalid mask index 0xFFFFFFFE, context = 16BA0E8/144bit-context, (EEHYP_CS_801-1)
             first_mask_index = 0x0, last_mask_index = 0x4AF (EEHYP_CS_801-1)
Apr 24 16:07:20: -Traceback= 3182F4 31C264 31C9E8 31CB88 31CD94 378FCC 37AC28 37A97C 36E860 36F780 36315C 363A4C 75E3A8 7585EC (EEHYP_CS_801-1)
Apr 24 16:07:20: %TCAMMGR-3-INDEX_ERROR: cam value/mask index -2 is invalid (EEHYP_CS_801-1)
-Traceback= 97CFEC 318318 31C264 31C9E8 31CB88 31CD94 378FCC 37AC28 37A97C 36E860 36F780 36315C 363A4C 75E3A8 7585EC (EEHYP_CS_801-1)

Edison Ortiz · ‎04-29-2010

Lots of traceback so an event occurred that caused the outage. I recommend saving that traceback log and opening a TAC case for further troubleshooting.

Switch 2 would have the same config as Switch 1. They are all part of the same stack. During switchover, network services may be impacted but not for long. In you case, the stack was affected by a traceback condition.

Again, opening a TAC case to determine the root cause would be my recommendation..

Regards

Edison.

Luis Salazar · ‎04-29-2010

Thanks a lot Edison,

Regards,

shailesh.h · ‎04-27-2010

STACK Troubleshooting document link provides answer to your problem as well as query what will happen if change the master switch

http://www.cisco.com/en/US/partner/docs/switches/lan/catalyst3750/software/troubleshooting/switch_stacks.html

Shailesh