[c-nsp] 3750 & Waiting for Stack Master Election (around 30 seconds)...

[Tassos Chatzithomaoglou]

While booting, i'm getting:

===================================================================
Waiting for Stack Master Election (around 30 seconds)...
POST: PortASIC CAM Subsystem Tests : Begin
POST: PortASIC CAM Subsystem Tests : End, Status Passed

POST: No Cable found on stack port 1
POST: No Cable found on stack port 2

POST: PortASIC Stack Port Loopback Tests : Begin
POST: PortASIC Stack Port Loopback Tests : End, Status Passed

POST: PortASIC Port Loopback Tests : Begin
POST: PortASIC Port Loopback Tests : End, Status Passed

Election Complete
Switch 1 booting as Master
Waiting for Port download...Complete
===================================================================

Any idea how to avoid this delay on a 3750?

[Justin M. Streiner]

Are running your 3750(s) as a stack? If so, the stack master election
process is a critical/mandatory bootup process. I'm not aware of any way
to disable this if you're only running a single switch.

jms

Post by Tassos Chatzithomaoglou
===================================================================
Waiting for Stack Master Election (around 30 seconds)...
POST: PortASIC CAM Subsystem Tests : Begin
POST: PortASIC CAM Subsystem Tests : End, Status Passed
POST: No Cable found on stack port 1
POST: No Cable found on stack port 2
POST: PortASIC Stack Port Loopback Tests : Begin
POST: PortASIC Stack Port Loopback Tests : End, Status Passed
POST: PortASIC Port Loopback Tests : Begin
POST: PortASIC Port Loopback Tests : End, Status Passed
Election Complete
Switch 1 booting as Master
Waiting for Port download...Complete
===================================================================
Any idea how to avoid this delay on a 3750?
--
Tassos
_______________________________________________
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list cisco-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

[Tassos Chatzithomaoglou]

This is a standalone 3750 and i was trying to find a way to avoid this process.
Quite strange that Cisco doesn't provide one...

--
Tassos

Post by Justin M. Streiner
Are running your 3750(s) as a stack? If so, the stack master election
process is a critical/mandatory bootup process. I'm not aware of any
way to disable this if you're only running a single switch.
jms

Post by Tassos Chatzithomaoglou
===================================================================
Waiting for Stack Master Election (around 30 seconds)...
POST: PortASIC CAM Subsystem Tests : Begin
POST: PortASIC CAM Subsystem Tests : End, Status Passed
POST: No Cable found on stack port 1
POST: No Cable found on stack port 2
POST: PortASIC Stack Port Loopback Tests : Begin
POST: PortASIC Stack Port Loopback Tests : End, Status Passed
POST: PortASIC Port Loopback Tests : Begin
POST: PortASIC Port Loopback Tests : End, Status Passed
Election Complete
Switch 1 booting as Master
Waiting for Port download...Complete
===================================================================
Any idea how to avoid this delay on a 3750?
--
Tassos
_______________________________________________
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list cisco-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
ar

[Andy Ellsworth]

Post by Tassos Chatzithomaoglou
This is a standalone 3750 and i was trying to find a way to avoid this process.
Quite strange that Cisco doesn't provide one...

If you don't want stacking (and the associated longer boot times), you
might consider the Catalyst 3560 for future purchases. It's essentially
a 3750 minus the stacking capability.

-Andy

_______________________________________________
cisco-nsp mailing list cisco-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

[Tassos Chatzithomaoglou]

That would be possible if there was a 3560 with 12 SFP ports ;)

--
Tassos

Post by Andy Ellsworth

Post by Tassos Chatzithomaoglou
This is a standalone 3750 and i was trying to find a way to avoid this process.
Quite strange that Cisco doesn't provide one...

If you don't want stacking (and the associated longer boot times), you
might consider the Catalyst 3560 for future purchases. It's essentially
a 3750 minus the stacking capability.
-Andy
_______________________________________________
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list cisco-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp

[Justin M. Streiner]

Post by Tassos Chatzithomaoglou
This is a standalone 3750 and i was trying to find a way to avoid this process.
Quite strange that Cisco doesn't provide one...

In a way, it does make sense, actually...

If Cisco included a "no switch stacking" command or something similar,
they'd probably field a lot of support calls after people configured (or
if it was a default) then wonder why additional switches don't work when
they finally do start to build 3750 stacks in their wiring closets :)

jms
_______________________________________________
cisco-nsp mailing list cisco-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

[Chris Griffin]

But if the switch could autodetect if it had "link" on the stacking
ports and if not, skip the pause... that would be good.

Chris

Post by Justin M. Streiner

Post by Tassos Chatzithomaoglou
This is a standalone 3750 and i was trying to find a way to avoid this process.
Quite strange that Cisco doesn't provide one...

In a way, it does make sense, actually...
If Cisco included a "no switch stacking" command or something similar,
they'd probably field a lot of support calls after people configured (or
if it was a default) then wonder why additional switches don't work when
they finally do start to build 3750 stacks in their wiring closets :)
jms
_______________________________________________
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

[Alexander Koch]

Justin,

Post by Justin M. Streiner
If Cisco included a "no switch stacking" command or something similar,

you mean like in old times when ppl just simply did not spot
the 'no ip routing' even though it was jumping right into
their eyes (or not)?

Let us not go there. ;-)

-ako

_______________________________________________
cisco-nsp mailing list cisco-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

[Ian Dickinson]

Post by Alexander Koch
Justin,

Post by Justin M. Streiner
If Cisco included a "no switch stacking" command or something similar,

you mean like in old times when ppl just simply did not spot
the 'no ip routing' even though it was jumping right into
their eyes (or not)?
Let us not go there. ;-)

"Give us the rope and let us hang ourselves."

The right solution is that cisco fix the long delays so it's unnecessary,
but if not, let us choose for ourselves. Even 'no ip routing' is a valid
thing to do in some situations - should they remove it to make us safer? :-)
--
Ian Dickinson
Senior Network Development Engineer
Pipex
***@pipex.net
http://www.pipex.net

This e-mail is subject to: http://www.pipex.net/disclaimer.html
_______________________________________________
cisco-nsp mailing list cisco-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

[Adrian Chadd]

Post by Ian Dickinson
"Give us the rope and let us hang ourselves."
The right solution is that cisco fix the long delays so it's unnecessary,
but if not, let us choose for ourselves. Even 'no ip routing' is a valid
thing to do in some situations - should they remove it to make us safer? :-)

Hey, I'm all for even more knobs on Cisco equipment; there's more for me
to fix and implement properly when they call in the (clueful) consultants. :)

(Cue rant about macro templates in the later switches and how one customer
turned on cisco-desktop for everything incl. dual-homed servers; the servers
worked fine until they were rebooted when the cisco switch started denying
packets for security reasons..)




Adrian

_______________________________________________
cisco-nsp mailing list cisco-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/