We're building a network for DR, where we're testing a whole bunch of apps on the Intel servers and one app on 4 Unix servers that has hard coded production addresses (172.21.242.0/24). So, we figured we would have to deploy NAT to translate the production addresses for this app. The way we're building the network is with a couple of daisy chained routers. The first router would be the choke router and the second would NAT the addresses, similar to this:
The second router with the e0/e1 interfaces would be doing the NAT. This, I believe should work OK. What I need to clarify is, the Intel servers will be hanging off the first router and the Unix servers will be hanging off of the second router (the NAT router). When a packet with the destination address of 10.47.24.17 arrrives at the first router, how would we make sure that if the server with that address is hanging off of the first router, it would find it, otherwise, the packet would be sent to the second router?
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...