Cisco CAS/CAM Servers exhibiting strange ping behavior explanation/cause?

Unanswered Question
Jun 3rd, 2010

This is the version of one of the servers:

# cat /etc/redhat-release
Cisco Clean Access Server

<<Linux version 2.6.18-cisco.nac.1 ([email protected]) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44))>>

Pings appear to work fine from the NAC servers themselves to other NAC servers(spread over about 4 or 5 different subnets to service different sections). However, there are strange timeouts from unexptected IPs. For example in a specific subnet A, the NAC server can ping out to whatever other systems just fine. However when I log onto the switch that's the gateway for subnet A, it is unable to ping the NAC server in its subnet. Other switches however can ping this subnet A server just fine. What logic is the server employing to cause this(my guess would be its perception of it's "gateway" in the subnet is different than the acutal "gateway's perception" of the subnet gateway)--any ideas?? Thanks.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Faisal Sehbai Fri, 06/04/2010 - 13:59


Routing on the CAS is dictated by the Click routing protocol. To verify where the traffic is going for a particular subnet, do this on your CAS:

cat /proc/click/real_routing_table/table

It should show you what the routing table your CAS is utilizing.




This Discussion