As Tim has pointed out it is normal behavior if you ping to the network address or to the network broadcast address of the local subnet that you may get answers. Cisco routers generally do generate responses to .0 and .255 addresses (note that some early implementations used .0 as the broadcast address - I believe that this is why Cisco generates a response).
Vlad points out that there is some difference whether we are pinging to addresses of the local subnet (the network address or network broadcast address) or to addresses outside the local subnet. If we are pinging to addresses outside the local subnet then what happens depends on how the remote router is configured: if the router interface is configured with ip directed-broadcast then the router does forward the packet and we may get responses from devices within the remote subnet. But if the remote router is configured with no ip directed-broadcast then it does not forward the packet. (The last time I tested this the remote router did generate a response to the ping even though it did not forward onto the remote subnet.)
So certainly it is normal behavior if you ping the address within the local subnet and get a response.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...