Can't Ping Cisco devices

We are experiencing a very weird problem with some of the switches.

There are 3 3500 series that I cannot ping the device at all.

Recently, we went to a VLAN configuration and I can ping two switches on the other side of these switches
but i can ping the switches first in line.

(switch>>fiber>>switch) and (switch>>cat5>>switch>>fiber>>switch)

Anyone ever heard of anything like this?

Thanks in advance
AB
LVL 1
AmericanBridgeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Don JohnstonInstructorCommented:
Was it working before or is this new behavior? Are the VLAN interfaces of the switch up? Are the trunks carrying that VLAN allowed on the trunks?
0
btassureCommented:
And are you on the same vlan as the one whose interface you are pinging? And is there routing between your vlan and that of switch's vlan ip address?
0
sterudpaCommented:
is ICMP turned on at the switch?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

AmericanBridgeAuthor Commented:
Yes it was working when the network was flat.

The VLAN interfaces on the switches are up. All Vlans are allowed on each trunk.

The routing works fine between. I am pinging from a client VLAN to the switch VLAN. Two switches are ping able and 2 are not.
0
Don JohnstonInstructorCommented:
This is going to require some additional information:

The ip addresses/mask of the source and destination.
A topology diagram (or explanation)
Relevant portions of the configs of the switches
0
btassureCommented:
I assume it isnt something simple like the 2 switches are on the same ip addresses or anything?
0
Don JohnstonInstructorCommented:
That is one of MANY things which could be causing this symptom.
0
btassureCommented:
True but it's one of the easiest to check :o)
0
AmericanBridgeAuthor Commented:
All of the devices have their own IP in the correct subnet. The devices have their own subnet.

The entire network is a class B default with a /24 mask.

The VLANs are as follows
VLAN 1 - Clients
VLAN 2 - VoIP
VLAN 3 - Servers
VLAN 4 - Internet
VLAN 5 - Network devices
VLAN 6 - Segregated net for outside access
VLAN 7 - Printers

The current topology is a core switch that has one fiber to a 3500 which has a fiber to another 3500 and a Cat5 uplink to a 2600 that has a fiber to another 2600 which has a wireless bridge connection to a 3500. Sounds a bit complicated but it's the only way we could connect all clients.

As I stated before, I can ping the 2600 that hang off of the fiber connection from the other 2600 (far switch) and I can ping the 3500 on the other side of the wireless bridge.

The other 3 I cannot ping.
0
Don JohnstonInstructorCommented:
Not to be repetitive,

This is going to require some additional information:

The ip addresses/mask of the source and destination.
A topology diagram (or explanation)
Relevant portions of the configs of the switches

For example. I've lost count of the number of times where a connectivity problem ended up being one incorrect digit in an IP address.
I'm not certain I understand your topology. Is this it?

3500-----3500-----3500----2600-----2600

What models are the 3500's?

And finally, without being able to see the configs, all I can do is say "Check the IP addresses. Check the trunking. Check that the interfaces are up."

0
AmericanBridgeAuthor Commented:



            -Fiber-------------4510R (layer 3 device)
        -
    -  
3500XL ___cat5___2900XL---fiber----2900XL___----___--Wireless__----__----___3524
     -
        -
           -Fiber--------------3524


I won't post IPs so just trust that I have them right. The IPs have correct masks and are not new IPs for the devices.

What section of the config would you need? I am the one who re-configured these so I know the config from top-bottom.
0
Don JohnstonInstructorCommented:
>I can ping the 2600 that hang off of the fiber connection from the other 2600

Where are the 2600's? This is what you're pinging from, right?

And are you using public IP's or private?
0
AmericanBridgeAuthor Commented:
Oops sorry, they are all 2900 switches, not 2600 routers.

All private IPs and I am pinging from a client VLAN node sitting on the 4510R
0
Don JohnstonInstructorCommented:
So one of the pings that doesn't work is from a VLAN 1 device on the 4510 to the 3500XL?

Post the config of the 4510 and the 3500XL.
0
AmericanBridgeAuthor Commented:
I got it fixed actually. And I'm not sure why it worked on some and not all.

I forgot to add the def gateway for the switch VLAN.

What is weird is that the one 3524 on the wireless bridge didn't have the gateway changed to the new VLAN gateway.

And that's that.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Switches / Hubs

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.