Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

connecting 3750 switch to 2924 switch 1

Status
Not open for further replies.

techalum

IS-IT--Management
Oct 11, 2006
38
US
I have run out of ports on my 3750G. I was given a cisco 2924 to cross connect. I have connected port 1/0/9 of the 3750 to int fa0/1 of the 2924 with a cross connect cable. I can't get the switches to see each other.

3750
interface GigabitEthernet1/0/9
switchport mode access
duplex full
speed 100
macro description cisco-desktop | cisco-desktop
spanning-tree portfast
spanning-tree bpduguard enable

2924
interface FastEthernet0/1
duplex full
speed 100
spanning-tree portfast

any help would be appreciated. i can provide full configsif needed.
 
Well, first off, I'd turn off spanning-tree portfast. That's bad news if someone comes behind you and plugs in a loop. Configuration looks good as your 3750 should slow down to 100mb and connect. Have you tried another cable for your cross-over? Mabye it's a Layer 1 issue.

"I can picture a world without war. A world without hate. A world without fear. And I can picture us attacking that world, because they'd never expect it."
- Jack Handey, Deep Thoughts
 
Shouldn't matter what kind of cable you use, the 3750 should auto detect whether or not it's a crossover.

I'd set the ports up as a trunk as well. Just my personal preference.

What are you getting in the logs?
 
I am using a cross-connect cable. How would I go about setting up trunking? I turned off the spanning-tree and still am not able to ping the 3750.
 
One more thing. We do use VLANS
VLAN 1 is set as:
interface Vlan1 for 3750
description Inside 192.168.172.x
ip address 192.168.172.1 255.255.255.0
ip accounting output-packets
ip rip send version 1 2
ip rip receive version 1 2

for 2900
interface VLAN1
description Inside 192.168.172.x
ip address 192.168.172.3 255.255.255.0
no ip directed-broadcast
ip accounting output-packets
no ip route-cache
 
I suggested the cable as it might be bad. Trunking is only necessary if you want to share the vlan information between the switches, and if you do...

switchport mode trunk
switchport encapsulation dot1q
switchport native vlan x

These commands will differ depending on CatOS, IOS that your using. Make sure that your VTP is setup correctly before you do this as you'd hate to overwrite your vlan database.

"I can picture a world without war. A world without hate. A world without fear. And I can picture us attacking that world, because they'd never expect it."
- Jack Handey, Deep Thoughts
 
What do the interfaces look like ? In your initial config you had spanning tree bpduguard enabled so when you plugged in the 2924 it would err-disable the port on the 3750 most likely because it would see bpdu's from the 2924.. Check to see what state the port on both sides is in. If one side is err-dsable then do a shut then a no shut on the port to bring it up . Do you have a link light on each side. Check the states on each side , on the switches use the show interface status command to look at the port states.
 
The 3750 was err-disable. i did a shut no-shut and then checked out my 2924. I can now ping out to the internet!!!!
Thank you vipergg!!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top