David Freedman wrote:
>ip route vrf Chmbr-General 0.0.0.0 0.0.0.0 10.120.24.2 ! This is an ASA
>on the 'LAN' for this site
>ip route vrf Chmbr-General 10.0.0.0 255.0.0.0 Serial0/1/0.310
Right, got you so far
>So I remove the static route pointing to 10.120.24.2 and point it to the
>remote MPLS
>ip route vrf Chmbr-General 0.0.0.0 0.0.0.0 10.120.24.2 ! This is an ASA
>on the 'LAN' for this site
>ip route vrf Chmbr-General 10.0.0.0 255.0.0.0 Serial0/1/0.310
Right, got you so far
>So I remove the static route pointing to 10.120.24.2 and point it to the
>remote MPLS spoke, 10.120.24.2.
You
ChrisSerafin wrote:
That does sound correct, I will schedule some testing time, thanks for
your input!
David Freedman wrote:
Chris, the key thing here are the vrf address-families
"> address-family ipv4 vrf -Voice" e.g
Imagine these like the equivalent of the normal ipv4 address-family, b
That does sound correct, I will schedule some testing time, thanks for
your input!
David Freedman wrote:
Chris, the key thing here are the vrf address-families
"> address-family ipv4 vrf -Voice" e.g
Imagine these like the equivalent of the normal ipv4 address-family, but
for each VRF proce
Chris, the key thing here are the vrf address-families
"> address-family ipv4 vrf -Voice" e.g
Imagine these like the equivalent of the normal ipv4 address-family, but
for each VRF process.
These do not currently have "redistribute static" in them so you can
quite safely install "ip route vrf
I have a Sprint MPLS cloud for which they extend the VRF configs down to
the CE. I am in the middle of divesting a section of these MPLS
routers/subnets off of the main cloud and onto their own VRFs. I
essentially want to start by making a handfull of the sites, change
their default route for I
