Ping (Monitor) Controller AIR-CT2504 and Managed AccessPoints AIR-AP2802I

[Dancis]

Hello together,

i want to monitor the AP-Controller "AIR-CT2504-K9" and his managed AccessPoints "AIR-AP2802I-E-K9".

Main goal is that i can Ping all APs but actually it doesn't work.

I find a section where to enable SSH, HTTP(S) and SMTP but nothing for Ping.

It is not a problem of the firewall (all traffic allowed both directions, routes configured), and the APs have there correct IP, Subnet and Gateway.

So i guess that they may not answer the Ping-Request or may not route back to the Ping-Source or something like that.

Do you know this problem?

Ping Source is e.g. 172.16.10.1 / 255.255.255.0 / Gateway 172.16.10.254

Target AP    is e.g. 172.16.25.1 / 255.255.255.0 / Gateway 172.16.25.254

Best Regards,

Dancis

[Scott Fella]

I have never seen or heard of an issue like that. I run a few different environments at my home and I can ping all controllers and ap's with no issues. Even at work, I can ping all controllers and ap's, but as long as I'm on a subnet that is allowed by the FW. "I find a section where to enable SSH, HTTP(S) and SMTP but nothing for Ping." There is no functionality to not allow ping. Connect a laptop to the same vlan and see if ping works, start trying to eliminate variables.

[Dancis · Accepted solution]

Hey people,

your're right.

Problem was not the firewall and also not the AP.

Problem was a misconfigured switch where the appropriate VLAN was not added to Trunk.

Ping is possible without any configurations.

Thank you for helping.

Best Regards

Dancis

[Sandeep Choudhary]

If PING is not wiorking between two diff subnets then it must be an issue of routing or firewall blocking!

Regards

Dont forget to rate helpful posts