Replacing 5509 with 6500 series CAT OS switch

fullerton175 · ‎05-27-2009

Hi,

Our office is currently attempting to replace an older 5509 switch with a 6500 series switch. Both systems run CAT-OS which is, unfortunately, not something I'm very familiar. However, I've tried to press on and figure out this issue but so far have not had much luck.

Currently the existing 5509 can communicate just fine over a VLAN (VLAN 22) to our core switch (a 6506 running IOS) but after entering in the same configuration into the new 6500 replacement switch I'm unable to ping between the new switch and the core switch.

I've included below parts of the 5509 config and the 6500 config in the hope someone might see this and provide assistance in what I've setup wrong on the new switch. I'll be excluding things like passwords, banners, and SNMP settings though as they are not relevant the question at hand.

--old config--

begin

!

# ***** NON-DEFAULT CONFIGURATION *****

!

#time: Mon Jan 19 2009, 20:27:24

!

#version 6.3(8)

set option fddi-user-pri enabled

#system

set system name Dungeon

!

#frame distribution method

set port channel all distribution mac both

!

#vtp

set vtp mode transparent

set vlan 1 name default type ethernet mtu 1500 said 100001 state active

set vlan 1002 name fddi-default type fddi mtu 1500 said 101002 state active

set vlan 1004 name fddinet-default type fddinet mtu 1500 said 101004 state activ

e stp ieee

set vlan 1005 name trnet-default type trbrf mtu 1500 said 101005 state active st

p ibm

set vlan 22

set vlan 1003 name token-ring-default type trcrf mtu 1500 said 101003 state acti

ve mode srb aremaxhop 7 stemaxhop 7 backupcrf off

!

#ip

set interface sc0 22 192.168.22.4/255.255.255.0 192.168.22.255

set ip route 0.0.0.0/0.0.0.0 192.168.22.1

!

#set boot command

set boot config-register 0x2

set boot system flash bootflash:cat5000-sup3.6-3-8.bin

set boot system flash bootflash:cat5000-sup3.5-5-8.bin

set boot system flash bootflash:cat5000-sup3_4-5-1.bin

set boot system flash bootflash:cat5000-sup3.4-3-1a.bin

!

#mls

set mls nde disable

!

# default port status is enable

!

#module 1 : 2-port 1000BaseSX Supervisor

set vlan 22 1/2

set trunk 1/1 desirable dot1q 1-1005

set trunk 1/2 off negotiate 1-1005

!

#module 2 : 24-port 10/100BaseTX Ethernet

set vlan 22 2/1-24

set trunk 2/1 off negotiate 1-1005

(the remaining modules appear similar to module 2 with each port on the module (2/2...2/24) being the same configuration as 2/1).

---end old config ---

---new switch config---

begin

!

# ***** NON-DEFAULT CONFIGURATION *****

!

#time: Wed May 27 2009, 11:46:04

!

#version 7.6(24a)

!

#system web interface version Engine Version: 5.3.4 ADP Device: Cat6000 ADP Version: 2.0 ADK: 49

!

#system

set system name Dungeon

!

#frame distribution method

set port channel all distribution mac both

!

#stp mode

set spantree mode pvst+

!

#vtp

set vtp domain mns

set vtp mode transparent

set vlan 1 name default type ethernet mtu 1500 said 100001 state active

set vlan 1002 name fddi-default type fddi mtu 1500 said 101002 state active

set vlan 1004 name fddinet-default type fddinet mtu 1500 said 101004 state active stp ieee

set vlan 1005 name trnet-default type trbrf mtu 1500 said 101005 state active stp ibm

set vlan 22

set vlan 1003 name token-ring-default type trcrf mtu 1500 said 101003 state active mode srb aremaxhop 7 stemaxhop 7 backupcrf off

!

#ip

set interface sc0 22 192.168.22.4/255.255.255.0 192.168.22.255

set interface sc1 down

set ip route 0.0.0.0/0.0.0.0 192.168.22.1

!

#set boot command

set boot config-register 0x10f

set boot system flash bootflash:

!

# default port status is enable

!

#module 1 : 2-port 1000BaseX Supervisor

set vlan 22 1/2

set udld disable 1/2

set trunk 1/1 desirable dot1q 1-1005,1025-4094

set trunk 1/2 off negotiate 1-1005,1025-4094

!

#module 2 : 48-port 10/100BaseTX Ethernet

set vlan 22 2/1-48

set trunk 2/1 off negotiate 1-1005,1025-4094

----

I'd really appreciate anyone's feedback on this. Thank you.

Giuseppe Larosa · ‎05-27-2009

Hello James,

do

sh port 1/2 on C6500 catos

do you see the port as enabled ?

you may need to enable it with

set port enable 1/2

if this is the port that connects to core switch.

Hope to help

Giuseppe

srue · ‎05-27-2009

# default port status is enable ...

it looks like both of these switches have the same IP address.

fullerton175 · ‎05-27-2009

Aye, that's correct. The 6500 is replacing the 5500. They have the same interface IP address since I unplugged the fiber connection to the 5500 and placed it into the 6500 as the new switch will be going into the same place as the old switc.

glen.grant · ‎05-27-2009

Whats the uplink on the old and new switch is 1/1 or 1/2 . Is the line trunking or just an access port ? Does the connecting link show connect ? Can you see cdp neighbor across that link ? If no then its a physical layer issue. also try entering "set vlan 22 mode active"

fullerton175 · ‎05-27-2009

I went into the config of the existing switch and did a show port on the port where the fiber connection is located. It shows to be a trunk.

If it helps for reference, on the main core switch which connects this new switch to the rest of the bank, the core switch (a 6506 running IOS) has the following listed for the connection from the main switch to the new switch causing me trouble:

----------

switchport

switchport encapsulation dot1q

switchport trunk allowed vlan 22

switchport mode trunk

no ip address

----------

This would seem to confirm that the connection between the core switch and the new switch should be a trunk using dot1q.

glen.grant · ‎05-27-2009

Try setting the catos port as

" set port 1/1 nonegotiate dot1q

clear trunk 1/1 1-21,23-1005,1025-4094

set vlaN 1 1/1

fullerton175 · ‎05-27-2009

Thank you to all who have provided guidance.

I will try these recommendations during off business hours, most likely tomorrow morning (5/28)

Giuseppe Larosa · ‎05-27-2009

Hello James,

because the new switch has the same ip address for management in vlan22 when you connect the new switch you need to clear the ARP table entry on the core switch otherwise the core switch tries to answer to the MAC address of old C5509.

check on core switch with

sh ip arp

before connecting new switch

then if you need (and you should) use

clear ip arp

on core switch

Hope to help

Giuseppe

fullerton175 · ‎05-28-2009

An excellent suggestion, thank you. I attempted to clear the entire arp table of the core yesterday after plugging in the new switch but I will try this suggestion as well as the others provided by you and the other experts who have responded here.

Won't be able to try anything until the 29th now due to some other issues which arose on the network (non-Cisco related).

fullerton175 · ‎05-29-2009

Small update...

The vendor we dealt with on the switch went ahead and has provided me a different supervisor engine which uses Cisco IOS instead of CatOS. We're going to install that since we're more familiar with IOS than CatOS here.

Or, more than likely it will result in a whole new slew of issues which I'll have to start another post for in the near future. :)