Link to home
Start Free TrialLog in
Avatar of satchelllowe
satchelllowe

asked on

Cisco 2950 port configuration when connecting to another switch

I have a problem at the moment where i need to connect an Extreme switch to my Cisco 2950 switch. The problem is that the port light comes up amber and does not pass any frames across to the VLAN.

The switch port on my Cisco 2950 has the following configuration:

interface FastEthernet0/10
 description INSIDE spare
 switchport access vlan 99
 switchport mode access
 switchport nonegotiate
!

Spanning-Tree is implemented on VLAN 99

Until yesterday port-fast was also enabled on this port. However i was lead to believe that this could be adding to the problem. Could you please advise me on how the switch should be configured to connect the the Extreme switch successfully?

Unfortunately i dont have any visability of the Extreme switch.

Thanks
ASKER CERTIFIED SOLUTION
Avatar of harbor235
harbor235
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It doesn't sound like a PVST-CST issue since the port is in access mode. Nor would portfast be causing this problem.

Are there any other paths from the Extreme switch back to the 2950 other than the link to fa0/10 through another switch?

What does the output of a "show spanning-tree vlan 99" show (port status for f0/10)?

How about "show interface status"?

-Don
Why is nonegotiate configured? Try doing this and see if it helps:
interface FastEthernet0/10
 no switchport nonegotiate
I would also check with the Extreme administrator how that port is configured. Is it configured to trunk or channel? If these are hard-configured on, the Cisco port won't come up and may log errors, and the Extreme port may do the same. You might look at the log on the Cisco switch with "sho log" and see if there are any errors. The errors will help you determine what you need to work out with the other admin.

Do this:
1. shut down the port on the cisco switch.
2. If you're on the console, make sure that messages log to the console. If you're remote, type "terminal monitor."
3. Turn up the port and see if there are any errors that show up. These should be logged also.

If the port goes down because of errors, the only way to bring it up is to shut down and no shut it. The switch will not administratively shut it down.
nonegotiate will have no effect since the port is being forced into access mode.
True. On the other hand, it doesn't belong there in this scenario.
Avatar of satchelllowe
satchelllowe

ASKER

The problem was with the BPDUs. Thanks for all your help.