As others have said, check to see if portfast is enabled. But also check to
see if
trunk autonegotiation is enabled and if Etherchannel/Port Aggregation
Protocol is
enabled. These two will typically consume about 18 seconds to negotiate and
figure
out that your Fluke (or other device) isn't trunking and isn't channelling.
Commands:
show trunk [m/n] (look at mode, usually defaults to auto, you may want it
off)
show port channel m/n (look at mode, usually defaults to auto silent, you
may want it off)
set trunk m/n off (turns trunking off completely on this port, no
negotiation)
set port channel m/n mode off (turns channelling off completely on this
port, no negotiation)
Ethan
""Larry Ogun-Banjo"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> We have just installed some new catalyst switches 650x and 69xx. I have
> noticed
> that whenever I connected with a fluke to test connectivity on the ports,
it
> takes approximately 20 secs to get its first contact with another device.
I'm
> aware the switch port needs to learn the mac address etc but I would not
have
> thought it would take so long. Are there any commands that would speedup
the
> network discovery or is this normal behaviour on a new port?
> Pardon this trivial question but it would help.
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=8337&t=8177
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
