Connecting C3560-IPBASEK9-M to existing C2960-LANBASE-M
Hi, I am trying to connect a new C3560-IPBASEK9-M to an older C2960-LANBASE-M. I want to trunk a fast Ethernet port on each and connect them.
We have two other C3560-IPBASE-M switches that are connected this way and seem to work fine.
I have tried to configure the C3560-IPBASEK9-M and the older C2960-LANBASE-M in a similar fashion as the two that are working. I get link lights on both, and can get CDP information. However, I cannot connect to the network through the new C3560-IPBASEK9-M when I plug a laptop into it. Also, I cannot telnet to it.
I saw elsewhere on Experts Exchange that the LANBASE IOS does not support IP routing. I assume this means I cannot use the command ‘ip classless'. Could this be the problem? If so, would it help to reverse the setup (connecting the new C3560-IPBASEK9-M to the fiber network, and then connecting the old C2960-LANBASE-M to the new switch)?
We have two other C3560-IPBASE-M switches that are connected this way and seem to work fine.
I have tried to configure the C3560-IPBASEK9-M and the older C2960-LANBASE-M in a similar fashion as the two that are working. I get link lights on both, and can get CDP information. However, I cannot connect to the network through the new C3560-IPBASEK9-M when I plug a laptop into it. Also, I cannot telnet to it.
I saw elsewhere on Experts Exchange that the LANBASE IOS does not support IP routing. I assume this means I cannot use the command ‘ip classless'. Could this be the problem? If so, would it help to reverse the setup (connecting the new C3560-IPBASEK9-M to the fiber network, and then connecting the old C2960-LANBASE-M to the new switch)?
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
The LANBASE code on the 3560 doesn't support dynamic routing (possible exception with stub routing depending on code version). It will still support static routing. The ip classless only refers to the ability to use IP addressing that doesn't conform to the strictest CIDR rules such as 192.168.x.x/23.
I would console in to the switch and look at what's happening. The vlan interface with the IP configured may not be what you thought, the interface could be down, or you could be plugged in to a port on a different vlan. There could be an ACL on the vty lines denying you access.
You say you get CDP information. When you do a "show cdp neigh detail" does the 3560's IP address show up?
Posting the config of both devices indicating which ports are connected will be helpful. Also run the commands:
show spann
show vlan
show vtp stat
show int status
show int status err
show int trunk
I would console in to the switch and look at what's happening. The vlan interface with the IP configured may not be what you thought, the interface could be down, or you could be plugged in to a port on a different vlan. There could be an ACL on the vty lines denying you access.
You say you get CDP information. When you do a "show cdp neigh detail" does the 3560's IP address show up?
Posting the config of both devices indicating which ports are connected will be helpful. Also run the commands:
show spann
show vlan
show vtp stat
show int status
show int status err
show int trunk
Okay, we are going to give it another try in the morning. I put everything back the way it was and powered down the new switch.
Just to clarify, the 2960 is the one with the LANBASE code.
I also briefly tried connecting the new switch straight into the fiber network and taking the old switch out of play (We might just take it out of play permanently). I also had problems connecting to the network with the new switch plugged into fiber. So I am thinking it has something to do with the new switch config.
I have to get permission to post the config. I don't think I will be able to. Is there a certain section that would be helpful or that I should concentrate on?
Just to clarify, the 2960 is the one with the LANBASE code.
I also briefly tried connecting the new switch straight into the fiber network and taking the old switch out of play (We might just take it out of play permanently). I also had problems connecting to the network with the new switch plugged into fiber. So I am thinking it has something to do with the new switch config.
I have to get permission to post the config. I don't think I will be able to. Is there a certain section that would be helpful or that I should concentrate on?
To shorten it, remove any line with a password or identifying information like a circuit id or account number, remove interfaces that aren't the uplink or the port connected to your pc. Post the rest including the show commands I suggested.
also, the 2960 with LANBASE can do static routing. LAN-lite cannot. 3560 can always do routing, but how advanced of routing you can do depends on code level and licensing.
also, the 2960 with LANBASE can do static routing. LAN-lite cannot. 3560 can always do routing, but how advanced of routing you can do depends on code level and licensing.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial