Link to home
Start Free TrialLog in
Avatar of leblanc
leblanc

asked on

cannot ping Avaya IP Office directly connected to an access switch

I have an Avaya IP Office (10.10.10.10) connecting to my access switch and I cannot ping it. However, I can ping it from my core switches. My core switches are running HSRP. Any thoughts will be greatly appreciated. Thanks
SOLUTION
Avatar of Otto_N
Otto_N
Flag of South Africa image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Avatar of Aaron Tomosky
Aaron Tomosky
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of leblanc
leblanc

ASKER

Yes default ip route on the IP Office is missing.

Aaron,
You are right on.

Otto,
You got it too.


Thank you.
Hi, I don't know if it is too late to add a question to this because I have a very similar situation and though I understand what you are saying, I don't understand how to make it work. The Avaya is on my LAN which is on one subnet, (109). All the Avaya stuff works on that subnet. I have a second subnet (112) connected through my SonicWall and all of the apps, except Avaya, work well between the subnets. I can ping anything from the 109 subnet, and anything but the Avaya management address from the 112 subnet. I understand from Aaron's comment that I need to change a setting in Avaya to allow the Avaya management address to be seen from the 112 subnet. Still, I haven't been able to figure out how to do that.  Any guidance or help will be appreciated. Thanks,
B.  mrbbrown@hotmail.com
Add a default route in the avaya like I said above. Normal network connections use the gateway like adults, but the avaya is a little child that needs a default route in addition to the gateway in the IP address settings. It's weird.
Aaron,

Thanks for the response. It sounds good. I just haven't figured out whether I can still add one. I apologize for being so ignorant about this stuff. Here is a picture of what Avaya shows me.  I couldn't figure out how to add an additional LAN ie no LAN3 available, and I tried to expand the subnet mask of the .109 subnet to /23, but that didn't seem to help either. I'll reboot the computer housing the Avaya tonight and see if it is just wanting a reboot. Thanks again for your having looked at the problem and giving help so far.User generated image
Just add the 112 subnet also out lan 1 to the routes.
Aaron, That works!  As I said, I apologize for being so ignorant. Thanks for your patience. Hallelujah!
Np. It's a weird one that took me a bit to figure out the first time I experienced it personally, so I'm happy to help. Avaya really should make 0.0.0.0 mean what it's supposed to mean.
Well, Thank you! I appreciate the help.