Redistributing BGP into ISIS

I have issue Reditributing BGP into ISIS network. I have Router R1 running ISIS Level-2 with a neighborn router R2 ISIS L1-L2. Router R1 has a peering BGP with another router, so I want to redistribute network that receives from peering BGP and anounce to its neighbour ISIS.
Here are go setting, all seems to be ok, but withen I check into R2 network 172.16.40.0 it gets "% Subnet not in table"
R1 ISIS
R1#sh isis neighbors
R2 L2   Gi9/3       172.30.100.98   UP    24       R1.09
router isis
net 49.0001.0000.0000.0024.00
is-type level-2-only
redistribute connected
redistribute bgp 11562 route-map Metricas level-1-2
route-map Metricas permit 10
match ip address 20
access-list 20 permit 172.16.40.0 0.0.0.255
R1#show ip bgp neighbors 172.16.40.38 received-routes
   Network          Next Hop            Metric LocPrf Weight Path
* i172.16.40.0/24 172.16.40.38             0    100      0 i
Command "redistribute bgp 11562 route-map Metricas level-1-2" I tried with "redistribute bgp 11562 route-map Metricas level-2" too, but didnt work. Please, help me

The prefix you're trying to redistribute into IS-IS is coming from an iBGP peering. By default, the BGP process will not redistribute iBGP into an IGP because this scenario can frequently create routing loops. If you really want to do this and you're sure your routing setup is stable, you can override this behaviour by adding the "bgp redistribute-internal" configuration command under your "router bgp" process.
Make sure you issue a "clear bgp ipv4 unicast *" to clear the BGP table once you've made the configuration change.

Similar Messages

BGP and ISIS

Hi,
Is there any relation between ISIS overload bit timer and BGP graceful restart timer. Does BGP timer should be always greater than ISIS overload bit timer.
Thanks,
Prakash

Prakash,
Setting the overload bit only prevents the router to be used as a transit router.
Directly connected subnets are still reachable to other routers. So if you had two routers configured with overload bit, you could still establish a BGP session between their respective loopback addresses assuming they are either directly connected or the routers in between do not have their overload bit set.
Regards,

How does set metric-type internal (bgp) work?

i can't realise how the command "set metric-type internal " to work.
bgp announce to ebgp use the igp next-hop metric as the med.
the igp means only isis?
does ospf use it ?
will you tell me how to use it ? give me an example . thinks

Hi,
This command can be used into two different contexts:
1- Redistribution into ISIS
When you are redistributing routes into ISIS, you have the choice to set the metric-type as internal (between 0 and 64) or external (between 65 and 128)
Internal metric are always prefer over external metric
2- Set the MED to reflect IGP cost to the NH on eBGP updates
You are receiving an iBGP update and before sending it to your eBGP peers, you want the MED for that prefix set to your IGP cost to the iBGP peer announcing this prefix.
In this case the IGP can be anything.
This command is not necessary if you are redistributing the route into BGP directly instead of receiving them from iBGP. In such case, the MED reflects by default the IGP cost of the redistributed prefix.
HTH
Laurent.

BGP peers with same AS number

Hi All,
As in the network topology attached (replica of actual network), I would like to know if there is any way that routes received from PE-RTR1 in CE-RTR can be advertised to PE-RTR2 and vice versa, so that PE-RTR1 & PE-RTR2 can reach each other.
Routing protocol used between PE-RTR1 & CE and PE-RTR2 & CE is BGP.
The issue seems to be due to same AS number of PE-RTR1 & PE-RTR2. It might not be possible to change AS numbers defined. Is there any way to overcome this situation?
Thanks in advance..
Regards,
Nagabhushan

I read that a bit too quickly.
If you're connecting your locations via the ISP and they all use the same AS, they'll all need the statement I mentioned in my previous comment. If you already have communication between them via the ISP, then this command is probably already there.
If you're connecting everything via fibre to the primary location, you can just peer with the other locations using the same AS and you'll be fine... though there are some considerations if you're redistributing BGP into an internal routing protocol.
In your current configuration, is each location seeing the networks from the other sites propagating from the ISP via BGP?

How can my network access the Internet?

Hi all,
All in GNS3 lab scenario I created.
Hope anybody can shed light on this matter. I have for example a multi area OSPF domain. Like all of my remote sites are in area x, y, and z and all connects to area 0, in the area 0 I have this ASBR 7200 that has an EBGP peer to R1 (ISP) that connects to R2 and R2 connects to R3, which in turn R3 connects back to my ASBR 7200.
I would like to know how can I reach all of the BGP subnets being advertised by R1 (basically the internet) from my remote sites in area x, y and z? As you can see in the topology I am using obviously RFC 1918 addresses on my network and I used all public IP addresses on the BGP routers. I would like to know how I can reach all those for example all 500,000 routes in order for my remote sites to access the internet? I can't redistribute BGP into my OSPF (since it will break). I tried configuring the subnets on my remote sites on the ASBR 7200 using network command, and the BGP routers can see those subnets, but inside my network I cannot see the subnet that I have created in R3 (pretending it's an internet site). What seems to be missing in my config in the ASBR?
Please any inputs gladly appreciated.
Please remove configuration in 3RD_PARTY-7200-ASBR router, I would like to know how can my local sites see loopback 99.99.99.0 in R3 without redistribution into OSPF...
redistribute bgp 65535 subnets

Yes you will need to NAT at some point to go from private to public address space. Here is a basic configuration if you are interested:
interface F8
ip nat inside
interface G0
ip nat outside
ip access-list standard NAT
permit 192.168.11.0 0.0.0.255
ip nat inside source list NAT interface G0 overload

Why internal EIGRP flapping when a WAN link is flapping?

I have router A and B running EIGRP in between. Router B has a WAN connection into the carrier.
Recently the EIGRP neighboring between A and B was flapping. In the mean time the WAN link was flapping too.
Router B was running BGP over the WAN link and redistributing BGP into EIGRP.
Why the WAN link issue caused the EIGRP neighboring up and down?
Thanks
Gary

When we attempted to ping the ISP's router will a full size MTU packet, the packet gets dropped. Any packets greater than 400 bytes gets dropped.

Problems with running EIGRP as PE-CE routing protocol 2

Dear all,
I am facing with the exact problem as a previous user of running EIGRP as the PE-CE routing protocol for a MPLS VPN customer, but in different hardware. The PE router is a 7609-S RSP720-3CXL-GE running IOS 12.2(33)SRC3.
(When I have 33 prefixes or more in the VRF table on the PE, and I try to advertise this network to the CE router (by redistributing BGP into EIGRP), the EIGRP process begins to flap.
I can't advertise prefix more that 32 subnets at a time why?????
The very weird part here, is that when I do debug ip eigrp on the PE and the CE, I can see that the PE router is sending the routes to the CE, but on the CE I can see nothing.)
In my case there is 16 prefixes. When redistributing BGP into EIGRP on allready adjasent EIGRP neighbors everything works perfect, until some side clears it then it begans flaping. On PE router debug is show "retry limit exceeded" ,on CE "Interface Goodbye received"
If solution will be same what software should I use?
Thanks,
George Shiukashvili

George,
Let me ask a few questions:
What is the link layer technology that interconnects the PE and CE that are currently experiencing these issues?
Are there any devices inside the PE-CE path that could at least possibly (and randomly) block multicasts and/or large packets?
Is it possible to modify the EIGRP configuration both on PE and CE to manual neighbor definition using the neighbor commands? This would force all EIGRP comunication between the PE and CE to run as unicast, possibly avoiding some issues with multicast packet delivery.
Is it possible for you to post some show commands from both the PE and CE? I would be interested in seeing the show ip interface, show interfaces, show running-config interface regarding the particular interfaces on PE and CE that connect to each other, and also, I would like to see the EIGRP configuration on both devices.
I agree with the assessment of Mahesh - the preliminary information we have suggest that either the PE packets are not arriving at the CE, or the ACK packets from CE are not arriving back at the PE. Your own debug analysis furthermore revealed that there are no EIGRP Update packets arriving from the PE at the CE. Problems with MTU could indeed cause these problems but it is necessary to inspect the entire path between PE and CE.
Best regards,
Peter

Mpls-te vs performance routing (PFR)

Hello All,
Can someone tell me if MPLS-TE can use ip sla stats like PFR and is anyone using PFR in a enterprise (single AS) and redistrubing BGP to an IGP.
current we are using regular OSPF with Mpls looking for with smarter load balancing capability.
1. All traffic is voip
2. core is 7200 vxr's
any suggestions / links are appreciated
thanks
john

Hello John,
MPLS Te has its own signaling plane based on RSVP-TE and TE extensions of link state protocols.
So it doesn't use or interact with IP SLA.
to be noted that if you are in an MPLS scenario you don't need to redistribute BGP into OSPF.
the mpls forwarding for recursion follows the LSP path to the BGP next-hop (loopback or remote PE).
so if you multiple paths to BGP next-hop CEF based per destination load balancing using exor of IP SA, IP DA, and hash should already happens.
if you redistribute the BGP networks in IGP LDP will create additional LSPs for these IP subnets but the load balancing should not improve.
if you have two paths to BGP next hop you will have two paths to VOIP subnet
but using per packet load balancing has negative effects on jitter (delay variation)
Hope to help
Giuseppe

Trouble with vrf / OSPF

Hi
Because of a migation i need two connectin from one 6500 to a 3550. See the following scenario (just two switches!)
6500 ---------------- 3550
OSPF 100 -- vlan1 -- OSPF 100
OSPF 100 -- vlan2 -- OSPF 1000 vrf C1
Everythings works fine at the start, which is good. The bad thing, after i reboot the 3550 i have no neighborship from 3550 OSPF 1000 vrf C1 to 6500 global OSPF.
Thats because 3550 OSPF 1000 sends no hellos out of vlan 2. So probalby something's broken with the process.
Clear ospf process doesn't help.
The workaround is to delete OSPF 200 vrf C1 configuration and configure it again. But this is not what i want in a live environment.
Has anybody an idea?
cheers patrick

Hi Saul,
The issue is that the ASR9K knows how to get to 172.16.161.6 (or 172.16.19.30) but the EX8208 does not know how to get back to 172.16.19.6, which is the source address used for the ping request. This is because the C6500 redistribute ospf into bgp but it does not redistribute bgp into ospf.
Regards

BGP Redistribute-internal and MPLS

Hi, usually when redistributing from BGP into IGP only EBGP routes are redistributed unless the bgp redistribute-internal command is configured which allows the redistribution of IBGP routes. However when doing the same redistribution on a PE router for a IGP running with the CE it seems that this command is not needed and IBGP routes still get redistributed into the IGP. It works without this command. Does anyone know why this is the case?
I have been trying to understand this for some time now and it seems very trivial however its been bugging me and was hoping someone could clarify. Thx

Hi Vikram,
Well, look at it this way, in the case of MPLS VPN, BGP between the PEs (address-family ipv4 vrf x) is used to transport the customer routes between CEs, and thus it is very logical that it should redistribute all kind of routes (in the case of MPLS VPN the customer routes are always going to be iBGP anyway since they are redistributed from IGP (PE-CE) on another PE - except on the local router when the customer is using BGP as the PE-CE routing protocol) - using another prospective, redistributing iBGP routes into IGPs may cause routing loops to form within an autonomous system, but in the case of PE-CE the redistribution is done into a routing protocol outside the BGP domain (customer side).
I hope that i've been informative.
BR,
Mohammed Mahmoud.

Best-practice to redistribute NAT entries into OSPF

I have several different subnets that are all either NAT'd or accessible via a VPN. There's no actual route on the ASA to the addresses, and they're not directly connected, eliminating the usual redistribution commands.
What is the best-practice for redistributing such entries into an OSPF area? In the past, I've had static entries on the upstream firewall, allowing the rest of the network to see this. I'm trying to get rid of as many static routes as possible (or at least make them a floating route so as to provide backup should something in OSPF fail), but am having difficulty figuring out how to redistribute these into the OSPF area.
I can't use a summary-address command as there's no external routes that are being redistributed. The area range command is out as I don't have a separate area that routes are being redistributed from.
One thought I've had is to create a static null route for each subnet (allowing me to redistribute static, and have the static entries only on the originating box), but I imagine rather than NAT'ng or open the site-to-site VPN, it would discard traffic (as the destination is null).
Any ideas on what to do when you have "imaginary" addresses that don't exist anywhere but in NAT entries or that's defined as interesting traffic for a site-to-site VPN?
Thanks in advance.

I have the code working without use of config files. I am just disappointed that it is not working using the configuration files. That was one of the primary intents of my code re-factoring.
Katherine
Xiong , If you are proposing this as an answer then does this imply that Microsoft's stance is not to use configuration files with SSIS?? Please answer.
SM

Not working multitopology ISIS with IOS and IOS-XR

Hi everyone,
I've gon a problem setting up IPv6 routing with ISIS in the test network. There are four routers connected as shown on the image.
I've got problems setting up IPv6 routing in this topology. I tried single topology and multitopology ISIS. Neither of them works properly. Single topology simple does not come up when IPv6 is configured in ISIS. Multitopology yet comes up but uyields only working IPv4 roting. I can see that IPv6 ISIS RIB is buit by the routers, but it is not copied into the main routing table.
That's what I get in the multitopology mode:
All neignors are up.
R2#show isis neighbors
Tag null:
System Id Type Interface IP Address State Holdtime Circuit Id
R7 L1 Et0/2 2.2.27.7 UP 7 R7.04
R8 L1 Et0/1 2.2.28.8 UP 9 R8.03
R9 L1 Et0/0 2.2.29.9 UP 7 R9.01
Database in consistent on all four routers
R2#show isis database
Tag null:
IS-IS Level-1 Link State Database:
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
R2.00-00 * 0x0000001C 0x21DD 727 0/0/0
R7.00-00 0x00000011 0xF6EF 866 0/0/0
R7.04-00 0x00000007 0x5CD2 1117 0/0/0
R8.00-00 0x0000000B 0xD2EA 941 0/0/0
R8.01-00 0x00000006 0xF0C3 878 0/0/0
R8.03-00 0x00000006 0x7E39 805 0/0/0
R9.00-00 0x0000000B 0x4071 817 0/0/0
R9.01-00 0x00000006 0x8D2A 783 0/0/0
R9.03-00 0x00000006 0xE3CC 840 0/0/0
ISIS IPv6 RIB contains only local prefixes
R2#show isis ipv6 rib
IS-IS IPv6 process , local RIB
2002:2:2::7/128
2002:2:2:27::/64
2002:2:2:78::/64
2002:2:2:79::/64
IPv6 topology is not complete as if R8 and R9 were not in database
R2#show isis ipv6 topology
Tag null:
IS-IS TID 2 paths to level-1 routers
System Id Metric Next-Hop Interface SNPA
R2 --
R7 10 R7 Et0/2 0202.5a00.b120
R8 **
R9 **
A closer look at isis database:
R2#show isis database detail
Tag null:
IS-IS Level-1 Link State Database:
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
R2.00-00 * 0x0000001D 0x1FDE 1004 0/0/0
Area Address: 47.0002
Topology: IPv4 (0x0)
IPv6 (0x2)
NLPID: 0xCC 0x8E
Hostname: R2
IP Address: 2.2.0.2
Metric: 10 IP 2.2.0.2/32
Metric: 10 IP 2.2.29.0/24
Metric: 10 IP 2.2.28.0/24
Metric: 10 IP 2.2.27.0/24
IPv6 Address: 2002:2:2::2
Metric: 10 IPv6 (MT-IPv6) 2002:2:2:29::/64
Metric: 10 IPv6 (MT-IPv6) 2002:2:2:28::/64
Metric: 10 IPv6 (MT-IPv6) 2002:2:2:27::/64
Metric: 10 IPv6 (MT-IPv6) 2002:2:2::2/128
Metric: 10 IS-Extended R7.04
Metric: 10 IS-Extended R8.03
Metric: 10 IS-Extended R9.01
Metric: 10 IS (MT-IPv6) R7.04
Metric: 10 IS (MT-IPv6) R8.03
Metric: 10 IS (MT-IPv6) R9.01
R7.00-00 0x00000012 0xF4F0 1187 0/0/0
Area Address: 47.0002
Topology: IPv4 (0x0)
IPv6 (0x2)
NLPID: 0xCC 0x8E
Hostname: R7
IP Address: 2.2.0.7
Metric: 10 IP 2.2.0.7/32
Metric: 10 IP 2.2.78.0/24
Metric: 10 IP 2.2.79.0/24
Metric: 10 IP 2.2.27.0/24
IPv6 Address: 2002:2:2::7
Metric: 10 IPv6 (MT-IPv6) 2002:2:2:78::/64
Metric: 10 IPv6 (MT-IPv6) 2002:2:2:79::/64
Metric: 10 IPv6 (MT-IPv6) 2002:2:2:27::/64
Metric: 10 IPv6 (MT-IPv6) 2002:2:2::7/128
Metric: 10 IS-Extended R7.04
Metric: 10 IS-Extended R8.01
Metric: 10 IS-Extended R9.03
Metric: 10 IS (MT-IPv6) R7.04
Metric: 10 IS (MT-IPv6) R8.01
Metric: 10 IS (MT-IPv6) R9.03
R7.04-00 0x00000007 0x5CD2 640 0/0/0
Metric: 0 IS-Extended R7.00
Metric: 0 IS-Extended R2.00
R8.00-00 0x0000000B 0xD2EA 464 0/0/0
Area Address: 47.0002
NLPID: 0xCC 0x8E
Topology: IPv4 (0x0)
IPv6 (0x2)
Hostname: R8
IP Address: 2.2.0.8
IPv6 Address: 2002:2:2::8
Metric: 10 IS-Extended R8.01
Metric: 10 IS-Extended R8.03
Metric: 10 IP 2.2.0.8/32
Metric: 10 IP 2.2.28.0/24
Metric: 10 IP 2.2.78.0/24
Metric: 10 IPv6 (MT-IPv6) 2002:2:2::8/128
Metric: 10 IPv6 (MT-IPv6) 2002:2:2:28::/64
Metric: 10 IPv6 (MT-IPv6) 2002:2:2:78::/64
R8.01-00 0x00000007 0xEEC4 1155 0/0/0
Metric: 0 IS-Extended R8.00
Metric: 0 IS-Extended R7.00
R8.03-00 0x00000006 0x7E39 328 0/0/0
Metric: 0 IS-Extended R8.00
Metric: 0 IS-Extended R2.00
R9.00-00 0x0000000C 0x3E72 1035 0/0/0
Area Address: 47.0002
NLPID: 0xCC 0x8E
Topology: IPv4 (0x0)
IPv6 (0x2)
Hostname: R9
IP Address: 2.2.0.9
IPv6 Address: 2002:2:2::9
Metric: 10 IS-Extended R9.01
Metric: 10 IS-Extended R9.03
Metric: 10 IP 2.2.0.9/32
Metric: 10 IP 2.2.29.0/24
Metric: 10 IP 2.2.79.0/24
Metric: 10 IPv6 (MT-IPv6) 2002:2:2::9/128
Metric: 10 IPv6 (MT-IPv6) 2002:2:2:29::/64
Metric: 10 IPv6 (MT-IPv6) 2002:2:2:79::/64
R9.01-00 0x00000007 0x8B2B 1048 0/0/0
Metric: 0 IS-Extended R9.00
Metric: 0 IS-Extended R2.00
R9.03-00 0x00000007 0xE1CD 1091 0/0/0
Metric: 0 IS-Extended R9.00
Metric: 0 IS-Extended R7.00
I don't understand the following: Why R8 doesn't consider itself attached to Pseudonodes R8.01 and R8.03 in IPv6 topology? The same question about R9 and Pseudonodes R9.01 and R9.03 in IPv6 topology. R7 and R2 consider themselves as attached to Pseudonode R7.04, although R7.04 doesn't look much different from the rest of the Pseudonode LSPs in the database. This fact still doesn't allow them to calculate a correct RIB.
Am I missing something?
Configs of the devices is below:
######R2########
service timestamps debug datetime msec
service timestamps log datetime msec
hostname R2
boot-start-marker
boot-end-marker
vrf definition ABC
rd 2:2
address-family ipv4
route-target export 2:2
route-target import 2:2
route-target import 1002:2
exit-address-family
no aaa new-model
clock timezone PST 0
ip source-route
ip cef
ipv6 unicast-routing
ipv6 cef
multilink bundle-name authenticated
mpls label protocol ldp
interface Loopback0
ip address 2.2.0.2 255.255.255.255
ip router isis
ipv6 address 2002:2:2::2/128
ipv6 router isis
interface Ethernet0/0
ip address 2.2.29.2 255.255.255.0
ip router isis
ipv6 address 2002:2:2:29::2/64
ipv6 router isis
mpls ip
interface Ethernet0/1
ip address 2.2.28.2 255.255.255.0
ip router isis
ipv6 address 2002:2:2:28::2/64
ipv6 router isis
mpls ip
interface Ethernet0/2
ip address 2.2.27.2 255.255.255.0
ip router isis
ipv6 address 2002:2:2:27::2/64
ipv6 router isis
mpls ip
interface Ethernet0/3
no ip address
shutdown
interface Ethernet1/0
vrf forwarding ABC
ip address 172.2.142.2 255.255.255.0
interface Ethernet1/1
no ip address
shutdown
interface Ethernet1/2
no ip address
shutdown
interface Ethernet1/3
no ip address
shutdown
router isis
net 47.0002.0000.0000.0002.00
is-type level-1
metric-style wide
address-family ipv6
multi-topology
exit-address-family
router rip
version 2
address-family ipv4 vrf ABC
redistribute bgp 2 metric 1
network 172.2.0.0
no auto-summary
version 2
exit-address-family
router bgp 2
no bgp default ipv4-unicast
bgp log-neighbor-changes
neighbor 2.2.0.9 remote-as 2
neighbor 2.2.0.9 update-source Loopback0
address-family ipv4
no synchronization
network 2.2.0.2 mask 255.255.255.255
neighbor 2.2.0.9 activate
neighbor 2.2.0.9 send-community
no auto-summary
exit-address-family
address-family vpnv4
neighbor 2.2.0.9 activate
neighbor 2.2.0.9 send-community extended
neighbor 2.2.0.9 next-hop-self
exit-address-family
address-family ipv4 vrf ABC
no synchronization
redistribute rip
exit-address-family
no ip http server
mpls ldp router-id Loopback0
control-plane
line con 0
exec-timeout 0 0
privilege level 15
logging synchronous
line aux 0
line vty 0 4
login
end
######R7########
service timestamps debug datetime msec
service timestamps log datetime msec
hostname R7
boot-start-marker
boot-end-marker
vrf definition ABC
rd 2:2
address-family ipv4
route-target export 2:2
route-target import 2:2
route-target import 1002:2
exit-address-family
no aaa new-model
clock timezone PST 0
ip source-route
ip cef
ipv6 unicast-routing
ipv6 cef
multilink bundle-name authenticated
mpls label protocol ldp
interface Loopback0
ip address 2.2.0.7 255.255.255.255
ip router isis
ipv6 address 2002:2:2::7/128
ipv6 router isis
interface Ethernet0/0
ip address 2.2.78.7 255.255.255.0
ip router isis
ipv6 address 2002:2:2:78::7/64
ipv6 router isis
mpls ip
interface Ethernet0/1
ip address 2.2.79.7 255.255.255.0
ip router isis
ipv6 address 2002:2:2:79::7/64
ipv6 router isis
mpls ip
interface Ethernet0/2
ip address 2.2.27.7 255.255.255.0
ip router isis
ipv6 address 2002:2:2:27::7/64
ipv6 router isis
mpls ip
interface Ethernet0/3
no ip address
shutdown
interface Ethernet1/0
vrf forwarding ABC
ip address 172.2.17.7 255.255.255.0
interface Ethernet1/1
no ip address
shutdown
interface Ethernet1/2
no ip address
shutdown
interface Ethernet1/3
no ip address
shutdown
interface Serial2/0
no ip address
no fair-queue
serial restart-delay 0
interface Serial2/1
no ip address
shutdown
serial restart-delay 0
interface Serial2/2
no ip address
shutdown
serial restart-delay 0
interface Serial2/3
no ip address
shutdown
serial restart-delay 0
router ospf 100 vrf ABC
log-adjacency-changes
redistribute bgp 2 subnets
network 172.2.0.0 0.0.255.255 area 0
router isis
net 47.0002.0000.0000.0007.00
is-type level-1
metric-style wide
address-family ipv6
multi-topology
exit-address-family
router bgp 2
no bgp default ipv4-unicast
bgp log-neighbor-changes
neighbor 2.2.0.9 remote-as 2
neighbor 2.2.0.9 update-source Loopback0
neighbor 2002:2:2::9 remote-as 2
neighbor 2002:2:2::9 update-source Loopback0
address-family ipv4
no synchronization
network 2.2.0.7 mask 255.255.255.255
neighbor 2.2.0.9 activate
neighbor 2.2.0.9 send-community
no auto-summary
exit-address-family
address-family vpnv4
neighbor 2.2.0.9 activate
neighbor 2.2.0.9 send-community extended
exit-address-family
address-family ipv6
no synchronization
network 2002:2:2::7/128
neighbor 2002:2:2::9 activate
exit-address-family
address-family ipv4 vrf ABC
no synchronization
redistribute ospf 100 vrf ABC
exit-address-family
no ip http server
mpls ldp router-id Loopback0
control-plane
line con 0
exec-timeout 0 0
privilege level 15
logging synchronous
line aux 0
line vty 0 4
login
end
######R9########
hostname R9
telnet vrf default ipv4 server max-servers 100
username student
group root-lr
secret 5 $1$FJX6$23S1vUlkI7nuRNSFMWR8N0
aaa authentication login default local
cdp
vrf ABC
address-family ipv4 unicast
import route-target
2:2
1002:2
export route-target
2:2
control-plane
management-plane
out-of-band
interface MgmtEth0/0/CPU0/0
allow Telnet
interface Loopback0
ipv4 address 2.2.0.9 255.255.255.255
ipv6 address 2002:2:2::9/128
interface MgmtEth0/0/CPU0/0
ipv4 address 10.0.8.129 255.255.255.0
interface GigabitEthernet0/2/1/0
description uplink SW4
interface GigabitEthernet0/2/1/1
description uplink R2, R5
interface GigabitEthernet0/2/1/1.29
description - VLAN 29 (R2)
ipv4 address 2.2.29.9 255.255.255.0
ipv6 address 2002:2:2:29::9/64
dot1q vlan 29
interface GigabitEthernet0/2/1/1.59
description - VLAN 59 (R5)
vrf ABC
ipv4 address 172.2.59.9 255.255.255.0
dot1q vlan 59
interface GigabitEthernet0/2/1/2
description uplink R6, R7
interface GigabitEthernet0/2/1/2.69
description - VLAN 69 (R6)
ipv4 address 2.2.69.9 255.255.255.0
ipv6 address 2002:2:2:69::9/64
dot1q vlan 69
interface GigabitEthernet0/2/1/2.79
description - VLAN 79 (R7)
ipv4 address 2.2.79.9 255.255.255.0
ipv6 address 2002:2:2:79::9/64
dot1q vlan 79
interface GigabitEthernet0/2/1/3
shutdown
interface GigabitEthernet0/2/1/4
shutdown
interface POS0/2/0/0
shutdown
interface POS0/2/0/1
shutdown
interface POS0/2/0/2
shutdown
interface POS0/2/0/3
shutdown
route-policy default_policy_pass_all
pass
end-policy
router static
address-family ipv4 unicast
2.2.69.6/32 GigabitEthernet0/2/1/2.69
router isis abc
is-type level-1
net 47.0002.0000.0000.0009.00
address-family ipv4 unicast
metric-style wide
interface Loopback0
address-family ipv4 unicast
address-family ipv6 unicast
interface GigabitEthernet0/2/1/1.29
address-family ipv4 unicast
address-family ipv6 unicast
interface GigabitEthernet0/2/1/2.79
address-family ipv4 unicast
address-family ipv6 unicast
router bgp 2
address-family ipv4 unicast
network 2.2.0.9/32
address-family vpnv4 unicast
address-family ipv6 unicast
network 2002:2:2::9/128
address-family vpnv6 unicast
neighbor 2.2.0.2
remote-as 2
update-source Loopback0
address-family ipv4 unicast
next-hop-self
address-family vpnv4 unicast
route-reflector-client
neighbor 2.2.0.7
remote-as 2
update-source Loopback0
address-family ipv4 unicast
next-hop-self
address-family vpnv4 unicast
route-reflector-client
next-hop-self
address-family ipv6 unicast
next-hop-self
address-family vpnv6 unicast
next-hop-self
neighbor 2.2.0.8
remote-as 2
update-source Loopback0
address-family ipv4 unicast
next-hop-self
address-family vpnv4 unicast
route-reflector-client
next-hop-self
neighbor 2.2.69.6
remote-as 1002
address-family ipv4 unicast
route-policy default_policy_pass_all in
route-policy default_policy_pass_all out
address-family vpnv4 unicast
route-policy default_policy_pass_all in
route-policy default_policy_pass_all out
neighbor 2002:2:2::7
remote-as 2
update-source Loopback0
address-family ipv6 unicast
next-hop-self
neighbor 2002:2:2:69::6
remote-as 1002
address-family ipv6 unicast
route-policy default_policy_pass_all in
route-policy default_policy_pass_all out
vrf ABC
rd 2:2
address-family ipv4 unicast
redistribute eigrp 100
mpls ldp
router-id 2.2.0.9
interface GigabitEthernet0/2/1/1.29
interface GigabitEthernet0/2/1/2.79
router eigrp 100
vrf ABC
address-family ipv4
default-metric 100000 10 250 1 1500
autonomous-system 100
redistribute bgp 2
interface GigabitEthernet0/2/0/1.59
interface GigabitEthernet0/2/1/1.59
end
######R8########
hostname R8
telnet vrf default ipv4 server max-servers 100
username student
group root-lr
secret 5 $1$Y39m$k.fAmjkI6OEFDmiIfSkGt1
aaa authentication login default local
cdp
vrf ABC
address-family ipv4 unicast
import route-target
2:2
1002:2
export route-target
2:2
control-plane
management-plane
out-of-band
interface MgmtEth0/0/CPU0/0
allow Telnet
interface Loopback0
ipv4 address 2.2.0.8 255.255.255.255
ipv6 address 2002:2:2::8/128
interface MgmtEth0/0/CPU0/0
ipv4 address 10.0.8.128 255.255.255.0
interface GigabitEthernet0/2/1/0
description uplink SW3
interface GigabitEthernet0/2/1/1
description uplink R3, R7
interface GigabitEthernet0/2/1/1.38
description - VLAN 38 (R3)
vrf ABC
ipv4 address 172.2.38.8 255.255.255.0
dot1q vlan 38
interface GigabitEthernet0/2/1/1.78
description - VLAN 78 (R7)
ipv4 address 2.2.78.8 255.255.255.0
ipv6 address 2002:2:2:78::8/64
dot1q vlan 78
interface GigabitEthernet0/2/1/2
description uplink R2, R15
interface GigabitEthernet0/2/1/2.28
description - VLAN 28 (R2)
ipv4 address 2.2.28.8 255.255.255.0
ipv6 address 2002:2:2:28::8/64
dot1q vlan 28
interface GigabitEthernet0/2/1/2.158
description - VLAN 158 (R15)
dot1q vlan 158
route-policy default_policy_pass_all
pass
end-policy
router isis abc
is-type level-1
net 47.0002.0000.0000.0008.00
address-family ipv4 unicast
metric-style wide
interface Loopback0
address-family ipv4 unicast
address-family ipv6 unicast
interface GigabitEthernet0/2/1/1.78
address-family ipv4 unicast
address-family ipv6 unicast
interface GigabitEthernet0/2/1/2.28
address-family ipv4 unicast
address-family ipv6 unicast
router bgp 2
address-family ipv4 unicast
network 2.2.0.8/32
address-family vpnv4 unicast
neighbor 2.2.0.9
remote-as 2
update-source Loopback0
address-family ipv4 unicast
next-hop-self
address-family vpnv4 unicast
vrf ABC
rd 2:2
address-family ipv4 unicast
network 172.2.38.0/24
allocate-label all
neighbor 172.2.38.3
remote-as 123
address-family ipv4 unicast
route-policy default_policy_pass_all in
route-policy default_policy_pass_all out
as-override
send-extended-community-ebgp
mpls ldp
router-id 2.2.0.8
interface GigabitEthernet0/2/1/1.78
interface GigabitEthernet0/2/1/2.28
end
RP/0/0/CPU0:R8#

Hello,
Can you check on XR that you have option of enabling metric-style wide under ipv6 address-family.I'm not sure but i suppose you will also need to configure metric-style wide under ipv6 address-family as you are using multi-topology .IOS default run single topology and XR run default multi-topology.only need to be sure that you are running same topology and metric-style same on all router,in transition process like from multi to single or changing metric-style you can use "metric-style transition" option..
Regards,
Ashish

How do you Redistribution EIGRP into OSPF and maintain a distance of 250 for a static route?

Ok, I have scoured the forums long enough and have to post. The design is below. I moved a firewall to our new data center, which required adding some static routes for VPN connections and broadband backups. To minimize the amount of static routes I redistribute static into EIGRP with a route-map and prefix-list.
My problem is the next part of my network. When the data leaves my 56128's it hits an edge device connecting to our dark fiber. On this edge device I am running OSPF onto the dark fiber, then redistribute some EIGRP subnets into OSPF and again all is well.
Everything works up until the point the redistributed routes hit my RIB at my main data center where I am running IBGP. IBPG is run between our MPLS router and core for all our remote sites. When my backup route from the 56128's hits the cores, it supersedes the BGP route because the AD route O E2 [110/20] is lower than the BGP AD B [200/0]. Given the configuration below what can be done to remedy this? Oh when I redistribute I can only change the AD for the backup routes, all other routes should stay the same.
56128's where my static routes are:
ip route 192.168.101.0/24 192.168.30.77 name firewall 250
router eigrp 65100
redistribute static route-map Static-To-Eigrp
route-map Static-To-Eigrp permit 10
match ip address prefix-list Static2Eigrp
ip prefix-list Static2Eigrp seq 2 permit 192.168.101.0/24
Edge device:
router eigrp 65100
network 172.18.0.5 0.0.0.0
network 172.18.0.32 0.0.0.3
network 172.18.0.36 0.0.0.3
redistribute ospf 65100 metric 2000000 0 255 1 1500
redistribute static metric 200000 0 255 1 1500 route-map STATICS_INTO_EIGRP
passive-interface default
no passive-interface Port-channel11
no passive-interface Port-channel12
eigrp router-id 172.18.0.5
router ospf 65100
router-id 172.18.0.5
log-adjacency-changes
redistribute eigrp 65100 subnets route-map EIGRP_INTO_OSPF
passive-interface default
no passive-interface GigabitEthernet1/0/1
no passive-interface GigabitEthernet1/0/2
no passive-interface GigabitEthernet2/0/1
no passive-interface GigabitEthernet2/0/2
network 172.18.0.0 0.0.255.255 area 0
ip prefix-list EIGRP_INTO_OSPF seq 5 permit 172.18.0.0/16 le 32
ip prefix-list EIGRP_INTO_OSPF seq 10 permit 192.168.94.0/29 le 32
ip prefix-list EIGRP_INTO_OSPF seq 15 permit 192.168.26.32/29 le 32
ip prefix-list EIGRP_INTO_OSPF seq 20 permit 192.168.30.72/29 le 32
ip prefix-list EIGRP_INTO_OSPF seq 25 permit 192.168.20.128/25 le 32
ip prefix-list EIGRP_INTO_OSPF seq 26 permit 192.168.101.0/24 le 32 <- Backup Route for MPLS Remote Office
route-map EIGRP_INTO_OSPF permit 10
match ip address prefix-list EIGRP_INTO_OSPF

So in the case of a /24. If it were say broken up into /25's? From our remote sites we are using aggregate-address summary-only. Not sure how I would advertise a more specific route via BGP, sorry.
I didnt have this problem until I moved my firewalls. They plugged into the cores where IBGP was running and the static never kicked in unless the bgp route disappeared. I guess I could use my static redistribution for my VPN sites and use statics across the cores for the handful of backup links I have.

Redistribution of "global" OSPF into a VRF

Im' trying to redistribute several routes learned via OSPF into a VRF. This VRF use EIGRP as routing protocol.
I'm not able to see any entry in the vrf table.
Have anybody done a similar things or can point me to samples and tips ?
Thanks
Marco
This is what I have done:
ip vrf 1
rd 1000:1
route-target export 1000:1
route-target import 1000:1
ip vrf 2
rd 1001:2
route-target export 1001:2
route-target import 1001:2
interface FastEthernet0/0
description connessione al porta 4/12
no ip address
duplex full
speed 100
interface FastEthernet0/0.1
description VLAN 1 per test
encapsulation dot1Q 34
ip vrf forwarding 1
ip address 192.168.230.1 255.255.255.248
ip nat inside
standby 1 ip 192.168.230.6
standby 1 priority 110
standby 1 track GigabitEthernet6/0.2
interface FastEthernet0/0.2
description VLAN 2 per test SNASW
encapsulation dot1Q 35
ip vrf forwarding 2
ip address 192.168.230.57 255.255.255.248
interface GigabitEthernet6/0.1
description vlan TEST_NAT
encapsulation dot1Q 42
ip address 192.168.230.9 255.255.255.248
standby 2 ip 192.168.230.14
standby 2 priority 110
interface GigabitEthernet6/0.2
description vlan NAT
encapsulation dot1Q 43
ip address 192.168.230.17 255.255.255.248
standby 3 ip 192.168.230.22
standby 3 priority 110
standby 3 track FastEthernet0/0.1
router eigrp 2000
auto-summary
address-family ipv4 vrf 2
network 192.168.230.56 0.0.0.3
no auto-summary
autonomous-system 1001
exit-address-family
address-family ipv4 vrf 1
network 192.168.230.0 0.0.0.3
no auto-summary
autonomous-system 1000
exit-address-family
no eigrp log-neighbor-changes
router ospf 1000
log-adjacency-changes
passive-interface FastEthernet0/0.1
passive-interface GigabitEthernet6/0.1
network 192.168.230.16 0.0.0.7 area 100.100.100.100

Hi,
I don't understand very well your question, because I really don't know if you are trying to configure VPN's over MPLS but, maybe this can help you.
When you are configuring VPN's over MPLS:
- Supported by VPN aware routing protocols: eBGP, OSPF, RIPv2, Static Routes. The EIGRP is not a supported VPN, vrf Protocol.
- When you are configuring VPN's over MPLS you have to configure BGP and the address family for BGP.
- Also you have to be very careful when you are assigning OSPF to a vrf.
An example:
router ospf 1000 vrf Customer_ABC
network 192.168.230.16 0.0.0.7 area z
redistribute bgp xxx
router bgp xxx
address-family ipv4 vrf Customer_ABC
redistribute ospf 1000
There's more to configure in bgp, like neighbors address family vpnv4, etc.
Sorry if this don't help you or if you already knew this.
Regards,
Hector

Vrf routes into global route table

Dear All
I am stuck with a design I am trying to come up with for our EDGE network and looking for ideas from the community.
It is similar to what is described here:
http://www.cisco.com/en/US/docs/solutions/Enterprise/Network_Virtualization/ServEdge.html#wp86450http://www.cisco.com/en/US/docs/solutions/Enterprise/Network_Virtualization/ServEdge.html#wp86904
In short we have a multi-context FWSM at 2 sites creating an EDGE network, each site operate independently. The sites are linked internally in a single routing domain using OSPF. Each of the outside networks are in seperate VRFs, single-tier model.
I need to find a way to:
1) link the 2 sites (currently is done with a GRE tunnel between the site vrfs, looking at replacing this with mp-bgp and l3vpn encapsulation)
2) redistribute routes from each of the vrf into the common global route table (running ospf)
1 is working nicely with mp-BGP peer between the sites and routes distributed between, however I am stuck on how to achieve 2.
The only way I can see is to change the global route table to a vrf, then use rt import/export. This is commonly described as shared services. When I did that I got stuck with how to do the BGP peering as the loopback I was using for the peering is inside the new vrf.
Basically I want dynamic routing from the global route table to learn routes from each of the sites vrf. Then if a particular site's vrf is unavailable, it can pick up the other site's route.
Am I missing something here? The document linked makes it sound incredibly easy yet I am struggling with how to implement it.
Any advice is much appreciated

Hello philip,
It is really hard to help you, if you do not provide topology where you would like to implement these changes, so just some thoughts to your points:
2) redistribute routes from each of the vrf into the common global route table (running ospf)
You can use PE - CE design. VRFs are terminated on PE with all routes you need in respective VRFs. On PE, MP-BGP routes are redistributed into respective VRF's OSPF process . PE is connected with CE via separate physical interface for each VRF or you can use one physical interface with dedicated sub-interface for each VRF. PE is peering with CE using OSPF. All routes end up in CE global routing table.
Problems with this design ->
- for each VRF you have to create separate OSPF process on PE and CE, also OSPF process ID has to be unique on PE for each VRF. Also OSPF process ID has to match to establish OSPF neighborship between PE-CE, so on CE you will have to redistribute OSPF routes from each process to your main OSPF process.
other workarounds ->
1) instead OSPF you will use as peering protocol BGP between PE-CE, but you still have to redistribute BGP routes to OSPF on CE
2) you will use different PE to redistribute each VRF -> BGP routes will be redistributed from VRF into OSPF (same process ID as your main OSPF ID). Routes will be advertised via OSPF into CE global routing table.
You will use on PE per VRF to redistribute routes into OSPF with same process ID as your main process ID. Thanks to different PEs, you can have same OSPF process ID, all these PEs will peer with same CE via OSPF.
I hope I made my thoughts understandable, cause its quite hard to explain
When I did that I got stuck with how to do the BGP peering as the loopback I was using for the peering is inside the new vrf.
This should not be a problem. You can have same IP on all VRF and also global table, so peering can still be done. After BGP routes are exchanged you can leak prefixes from one vrf to another or into global table as you need.
Best Regards
Please rate all helpful posts and close solved questions

Redistributing BGP into ISIS

Similar Messages

Maybe you are looking for