Cisco 2924M-Xl Swiches

[mcp87]

I currently have 3 2924-XL switch all with the 2 port 100FX module. I am trying to get the them all to talk to each other but i am running into a wall. All three switch have been reset, and all have green link lights where the fiber is connect into them but i can not ping any of the switches from any of the them. I am fairly new to configuring cisco stuff so need any help that i can get. Interims of the why everything is connected one switch has a fiber cable going to each of the other two switches.

 

[vipergg]

I would start by getting them back to the defaults by doing a write erase and then reload , on each switch under vlan1 give them each a different address in the same subnet . Make sure vlan 1 is up (no shut). You should be able to ping the addresses in this config because they are all in the same subnet in vlan 1 .

 

[mcp87]

Ok i did that and the vlans show as follows:

192.168.2.2>show vlan
VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Fa0/1, Fa0/2, Fa0/3, Fa0/4,
Fa0/5, Fa0/6, Fa0/7, Fa0/8,
Fa0/9, Fa0/10, Fa0/11, Fa0/12,
Fa0/13, Fa0/14, Fa0/15, Fa0/16,
Fa0/17, Fa0/18, Fa0/19, Fa0/20,
Fa0/21, Fa0/22, Fa0/23, Fa0/24,
Fa1/1, Fa1/2, Fa2/1, Fa2/2,
Fa2/3, Fa2/4
1002 fddi-default active
1003 token-ring-default active
1004 fddinet-default active
1005 trnet-default active

VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
1 enet 100001 1500 - - - - - 0 0
1002 fddi 101002 1500 - - - - - 0 0
1003 tr 101003 1500 - - - - - 0 0
1004 fdnet 101004 1500 - - - ieee - 0 0
1005 trnet 101005 1500 - - - ibm - 0 0
192.168.2.2>

192.168.2.3>show vlan
VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Fa0/1, Fa0/2, Fa0/3, Fa0/4,
Fa0/5, Fa0/6, Fa0/7, Fa0/8,
Fa0/9, Fa0/10, Fa0/11, Fa0/12,
Fa0/13, Fa0/14, Fa0/15, Fa0/16,
Fa0/17, Fa0/18, Fa0/19, Fa0/20,
Fa0/21, Fa0/22, Fa0/23, Fa0/24,
Fa1/1, Fa1/2
1002 fddi-default active
1003 token-ring-default active
1004 fddinet-default active
1005 trnet-default active

VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
1 enet 100001 1500 - - - - - 1002 1003
1002 fddi 101002 1500 - - - - - 1 1003
1003 tr 101003 1500 1005 0 - - srb 1 1002
1004 fdnet 101004 1500 - - 1 ibm - 0 0
1005 trnet 101005 1500 - - 1 ibm - 0 0
192.168.2.3>

I simplfied things and have reduced the number of switches to two for the time being with one fiber calbe between them, link lights are green. But still can not ping each other nor can a machine on either switch ping another machine on the other switch.

What else do i need to do?

 

[vipergg]

Looks right , where are you trying to ping them from ? On the console or are plugged into one of the switches on a 10/100 port ? If you are on the console I don't see why you couldn't talk to them . If you do a show cdp neighbor from the one switch can you see the other 2 ? If not you have a physical cable issue as cdp runs at layer 2 . CDP will show you the other switches address and what port you are connected to if everything is ok.

 

[mcp87]

Here is the show cdp neig information:

User Access Verification

Password:
192.168.2.2>enable
Password:
192.168.2.2#show cdp
Global CDP information:
Sending CDP packets every 60 seconds
Sending a holdtime value of 180 seconds
Sending CDPv2 advertisements is enabled
192.168.2.2#show cdp neig
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater

Device ID Local Intrfce Holdtme Capability Platform Port ID
192.168.2.2#ping 192.168.2.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.2.3, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
192.168.2.2#


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
User Access Verification

Password:
192.168.2.3>enable
Password:
Password:
192.168.2.3#sow cdp
^
% Invalid input detected at '^' marker.

192.168.2.3#show cdp
Global CDP information:
Sending CDP packets every 60 seconds
Sending a holdtime value of 180 seconds
Sending CDPv2 advertisements is enabled
192.168.2.3#show cdp ?
entry Information for specific neighbor entry
holdtime Time CDP info kept by neighbors
interface CDP interface status and configuration
neighbors CDP neighbor entries
run CDP Process running
timer Time CDP info is resent to neighbors
traffic CDP statistics
| Output modifiers
<cr>

192.168.2.3#show cdp neig
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater

Device ID Local Intrfce Holdtme Capability Platform Port ID
192.168.2.2 Fas 1/1 131 T S WS-C2924M-Fas 1/1
192.168.2.3#ping 192.168.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.2.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
192.168.2.3#

As you can see 192.168.2.3 can see 192.168.2.2 as a Trans Bridge, Switch. But 192.168.2.2 can not see 192.168.2.3 at all and ping does not work from either console to either switch nor from a 10/100 port on either switch to other switch.

Grrr , What would cause this? Is it correctable?

 

[mcp87]

Anyone have any ideas on what i should do next?

 

[vipergg]

Looks like you have half a path on this connection , if you can see it one way and not the other then you don't have a complete path , bad fiber , patch cord , or bad port on switch etc .... Looks like the xmit from the .2 to .3 is ok because the .3 can see the .2 but the other side , xmit from .3 to .2 is no good because the .2 cannot see the .3 . Thus also you would not be able to ping in this scenario also . You do not have layer connectivity in both directions if you can't get cdp to work from both directions , this is still a physical type thing .

 

[mcp87]

Hmmm interesting, thanks for the information.

 

[mcp87]

Problem has been resolved, apparently one the switch was using a IOS from 1999 12.0(5)XU 2000 and the other switch was using 12.0(5)WCS 2002. Not personaly knowing if this was the problem i went ahead and copied the newer ios from the switch and put on the other reobooted both switches, reconfigured and presto change o. They now both see each other in cdp, can ping each other, and now allow traffic accross the fiber link.

Thanks to all who tried to help!