why not start with the basics - check that you have a resolvable route to the 172.16 network from the layer 3 device in the 192.168 network, Also check you have a route back from the 172.16 network to the source. Try a traceroute to see how far your you can get, from both directions.
try pinging the device in the 172.16 network from itself to verify if it is pingable.
That lot should show up something, if not come back!
i tried pinging the 172.16 nw from router it pings,tried pinging it from the core switch but it doesnt.i am unable to ping it even from the utm..the utm pings up till the router i/f eth0/1 172.16.0.99 but no further.
had added accesslist on eth0/0 i/f to permit in 184.108.40.206/24 and permit out 172.16/24 nw.
actually what we require is just to monitor an application in 172.16/24 nw from 192.16/24 network.at the router, there is no route to 172.16/24 nw from 192.168/24 network.do we require a route to 172.16/24 network ?.....where should the route be included?...the core switch or router ?..the core switch has route till utm i/f.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...