Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Here is an interesting scenario:I have a set of IPTV multicast sources on an SVI (172.28.40.0/24), and due to some future planning I am looking to move those into another address range (10.2.13.0/24). I also have an unused ISR 3945 which connects to...
My organization is deploying some new 9407 switches for campus access, and one feature I've been looking at is using auto smart ports to set the ports for different settings, depending on what gets plugged in.
One of my challenges is that we are us...
Here is an interesting scenario for consideration:
I have an enterprise, "A", which intends to form a VPN to share data with remote partner, "B". Both A and B are using network space that overlaps, and for reasons beyond my control, the partner is...
Here's an interesting problem.
I am attempting to land multiple L2L IPSec tunnels on an ASR-1001-HX, but with multiple endpoint addresses on my side. At first glance, this looks like it should be doable with multiple HSRP redundancy groups. However...
I've got a weird scenario where I need to do a port-forward in NAT, as well as a source address translation at the same time. Let me explain.
I have a secondary ISP coming into a data center facility and I have been asked to come up with a configu...
I can use the MAC OUI for detection, but it wasn't among the things I was looking to do, especially since MAC list is bound to grow over time. I'd rather use LLDP inputs as something better-determined.I was hoping it would be possible to either augm...
After some rethinking, I managed to get this routing scenario working. My suspicion why this was not working is due to the VRF only having one actual interface present in its routing table.
As such, I moved the translation into the global table and ...
VTI sounds nice, except I don't have administrative control of the remote endpoints and there is a wide spread of expertise between the remote vendors and partners.
My current thought is to shrink the network I'm using and create separate /29s on add...
The chief requirement is redundancy in an event of a failure.
The separate addressing is to support multiple business units, leaving the capability to move the tunnels to another router pair without having to go through and renumber all the remote en...
Jon,
The suggestion to use an address range not related to the local inside subnet was the correct answer. I routed an unused subnet on the inside network to the router.
I combed through the lab environment this morning, and noticed I fat-fingered a...