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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

6500 Switches question

Status
Not open for further replies.

jlf175

MIS
Jun 18, 2009
2
US
Hi there,
I'm currently trying to replace a 5509 switch running CatOS with a 6500 series switch running IOS. My first run through the config for the new 6500 did not seem to go well though so I'm posting here to hopefully receive some help and guidance.

The new switch connects via a Gig interface (fiber) to our core switch which is a 6506E. The core switch communicates just fine with the old 5509.

Currently these are, I believe, the pertinent parts for the configuration on the new 6500 Switch but I must have done something wrong:

!
interface GigabitEthernet1/1 (interface with the gigabit connnection)
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 22
switchport mode trunk

interface Vlan22
description omitted
ip address 192.168.22.4 255.255.255.0
ip helper-address 192.168.20.24
ip directed-broadcast 101

---

On the core switch side I have this information for the gigabit interface as well as the vlan located on the core:

!
interface GigabitEthernet5/4
description VLAN22 Dungeon Connection
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 22
switchport mode trunk
no ip address

!
interface Vlan22
description Dungeon VLAN22
ip address 192.168.22.1 255.255.255.0
ip helper-address 192.168.20.24
ip directed-broadcast 101

 
are you doing any layer 3 routing? what do those look like?
 
do you see the cdp neighbors?

How about an extended ping sourcing from each vlan?
 
the first question is when you tie the two switches together do you have a L1 connection (link light on each end) ? If you have the old 5500 port definition can you post that ?
 
This problem has been resolved. The solution was, as I thought, pretty simple.

When testing your VLANs and connections, you have to be sure to have a device plugged into one of the ports on the switch. I don't know why this is but I'm guessing it has something to do with spanning trees.

I also placed the switch in transparent mode for vtp as well tweaked the settings a little to be this for the switch:

vlan 22
!
!
interface GigabitEthernet1/1
description VLAN22 Dungeon Connection
switchport
switchport trunk encapsulation dot1q
switchport mode trunk

interface FastEthernet2/1
switchport
switchport access vlan 22
switchport mode access


interface Vlan22
description Dungeon Switch
ip address 192.168.22.4 255.255.255.0
ip helper-address 192.168.20.24
ip directed-broadcast 101
!
ip default-gateway 192.168.22.1

ip route 0.0.0.0 0.0.0.0 192.168.22.1

After these changes the switch worked great again. Thanks for all the assistance!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top