[j-nsp] Strange OSPF Issue over MPLS VPN with PE-CE as OSPF !
vaibhava varma
svaibhava at gmail.com
Wed Jul 11 11:11:51 EDT 2012
Hi Ivan
Yes I did enable that under the RI. Also as I have mentioned before
that on the PE router I am able to see the routes under the VRF. These
routes are getting injected into OSPF with the VRF_Lite_CE also and
can verify it in the OSPF database there as shared earlier. Its only
that the VRF_Lite_CE is not accepting these routes into the VRF Table
there. I am using vrf-target but not any export policy under the VRF.
SS7 {
instance-type vrf;
interface fe-0/2/0.1;
route-distinguisher 10.1.26.2:3200;
vrf-target target:64512:3200;
vrf-table-label;
protocols {
ospf {
export to-ospf ;
area 0.0.0.0 {
interface fe-0/2/0.1;
}
}
}
}
Regards
Varma
On Wed, Jul 11, 2012 at 4:57 PM, Ivan Ivanov <ivanov.ivan at gmail.com> wrote:
> Hi,
>
> Do you have enabled vrf-table-lable under the routing-instances on the PEs?
> I remember that this could help. Not in such cases but you can give a shot.
>
> could you paste your expert VRF policy on PE2?
>
> Ivan,
>
>
> On Wed, Jul 11, 2012 at 2:16 PM, vaibhava varma <svaibhava at gmail.com> wrote:
>>
>> Hi Ivan
>>
>> The Subnet in question is pulled in OSPF Area 130 uner VRF normally.
>> This subnet is a customer facing subnet where we are running OSPF as
>> PE-CE. No policy is used there but still this is being picked up as
>> Type 5 on the other end PE.
>>
>> We have OSPF Neighbourshsip up over this subnet and also learning
>> routes over this peering and to add more on ther weird behaviour
>> routes learnt over this Subnet are showing up as Type 3 on the other
>> side but still not being installed in VRF Table of the VRF-Lite CE.
>>
>> Regards
>> Varma
>>
>> On Wed, Jul 11, 2012 at 4:39 PM, Ivan Ivanov <ivanov.ivan at gmail.com>
>> wrote:
>> > Hi,
>> >
>> > How is initially imported in OSPF the subnet in question with policy or?
>> > If
>> > it is with policy it is Type 5. Try to start OSPF on the interface with
>> > subnet in passive more instead of importing the direct route with
>> > policy.
>> >
>> > HTH,
>> > Ivan,
>> >
>> > On Wed, Jul 11, 2012 at 1:44 PM, vaibhava varma <svaibhava at gmail.com>
>> > wrote:
>> >>
>> >> Hi Ivan
>> >>
>> >> As informed before I have already used the same Domain ID 1.1.1.1 on
>> >> both PEs and still the route was being shown as Type 5 even though the
>> >> subnet was directly connected on another PE and part of same OSPF Area
>> >> there. The domain ID did not help in solving the issue.
>> >>
>> >> Any other pointers ?
>> >>
>> >> Regards
>> >> Varma
>> >>
>> >>
>> >>
>> >> On Wed, Jul 11, 2012 at 4:04 PM, Ivan Ivanov <ivanov.ivan at gmail.com>
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > This sounds really strange!
>> >> >
>> >> > Please check this link below and see if you can manage to change it
>> >> > to
>> >> > Type
>> >> > 3
>> >> >
>> >> >
>> >> >
>> >> > http://www.juniper.net/techpubs/software/junos/junos95/swconfig-vpns/id-10922834.html#id-10950345
>> >> >
>> >> > Let me know the result!
>> >> >
>> >> > cheers,
>> >> > Ivan,
>> >> >
>> >> >
>> >> >
>> >> > On Wed, Jul 11, 2012 at 12:54 PM, vaibhava varma
>> >> > <svaibhava at gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> Hi Ivan
>> >> >>
>> >> >> I tried to manually configure the same domain ID on the PE but still
>> >> >> the routes are being injected from the MP-iBGP into OSPF as Type 5
>> >> >> and
>> >> >> I really do not have any clue. Ideally it should have been a Type 3
>> >> >> route but it is not showing like that. And the strangest thing is
>> >> >> that
>> >> >> on Location B there is no issues anyhow. Both of them share the same
>> >> >> setup with the only difference in the OSPF Area towards PE.
>> >> >>
>> >> >> > Did you try with Type 3 route (ABR instead of ASBR role for PE)? I
>> >> >> > don't
>> >> >> > know if this is applicable for your design.
>> >> >> How can do the Type 3 Route here, Even I think that the Type 3
>> >> >> route
>> >> >> should solve the issue but not sure why.
>> >> >>
>> >> >> Regards
>> >> >> Varma
>> >> >>
>> >> >> On Wed, Jul 11, 2012 at 3:14 PM, Ivan Ivanov <ivanov.ivan at gmail.com>
>> >> >> wrote:
>> >> >> > Hi,
>> >> >> >
>> >> >> > Did you try with Type 3 route (ABR instead of ASBR role for PE)? I
>> >> >> > don't
>> >> >> > know if this is applicable for your design.
>> >> >> >
>> >> >> > I see that you use the same domain-id on both PE or I am wrong? In
>> >> >> > that
>> >> >> > case
>> >> >> > the LSA should be Type 3 not Type 5.
>> >> >> >
>> >> >> > HTH,
>> >> >> > Ivan,
>> >> >> >
>> >> >> >
>> >> >> > On Wed, Jul 11, 2012 at 11:45 AM, vaibhava varma
>> >> >> > <svaibhava at gmail.com>
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> Dear All
>> >> >> >>
>> >> >> >> I am experiencing a very strange issue for one of my customer's
>> >> >> >> Juniper MPLS VPN with PE-CE as OSPF. Below is the setup details:
>> >> >> >>
>> >> >> >>
>> >> >> >> Location A-CE1----OSPF Area
>> >> >> >>
>> >> >> >>
>> >> >> >> 120---VRF-Lite-CE1------OSPF_Area0---PE1-----MP-iBGP----PE2---OSPF_Area
>> >> >> >> 130--Locaton_B_CE2
>> >> >> >>
>> >> >> >> Now the routes of Location_B_CE2 are installed in PE1 VRF table
>> >> >> >> and
>> >> >> >> seen as an External Route in the OSPF Database of PE1 as well as
>> >> >> >> VRF_Lite_CE1 but not getting installed into the VRF Table of
>> >> >> >> VRF_Lite_CE1.
>> >> >> >>
>> >> >> >> Now I am stuck up on why the LSA s not getting installed into VRF
>> >> >> >> Table when the Forwarding Address is 0.0.0.0 and I have an
>> >> >> >> Internal
>> >> >> >> OSPF Route to the ASBR and also an ASBR Summary LSA.
>> >> >> >>
>> >> >> >> When I tried to do debug on that particular LSA I never saw the
>> >> >> >> LSA-ID
>> >> >> >> at all in the debug anytime.
>> >> >> >>
>> >> >> >> Also there is no issue for the Location_A_CE1 routes in reaching
>> >> >> >> Location_B_CE2 and they are getting installed fine.
>> >> >> >>
>> >> >> >> Below are logs for reference.
>> >> >> >>
>> >> >> >> Subnet in Question having Issue ; 10.26.66.192/30
>> >> >> >>
>> >> >> >> On PE1 VRF Table Entry
>> >> >> >>
>> >> >> >> root at LS-MSS-01# run show route table SS7 10.26.66.192 extensive
>> >> >> >>
>> >> >> >> SS7.inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0
>> >> >> >> hidden)
>> >> >> >> 10.26.66.192/30 (1 entry, 1 announced)
>> >> >> >> TSI:
>> >> >> >> OSPF area : 0.0.0.0, LSA ID : 10.26.66.192, LSA type : Extern
>> >> >> >> KRT in-kernel 10.26.66.192/30 -> {indirect(131070)}
>> >> >> >> *BGP Preference: 170/-101
>> >> >> >> Route Distinguisher: 10.1.26.33:3200
>> >> >> >> Next hop type: Indirect
>> >> >> >> Next-hop reference count: 9
>> >> >> >> Source: 10.1.26.33
>> >> >> >> Next hop type: Router, Next hop index: 583
>> >> >> >> Next hop: 10.1.26.190 via em0.0, selected
>> >> >> >> Label operation: Push 16
>> >> >> >> Protocol next hop: 10.1.26.33
>> >> >> >> Push 16
>> >> >> >> Indirect next hop: 8ec22d0 131070
>> >> >> >> State: <Secondary Active Int Ext>
>> >> >> >> Local AS: 64513 Peer AS: 64513
>> >> >> >> Age: 13:11 Metric2: 1
>> >> >> >> Task: BGP_64513.10.1.26.33+179
>> >> >> >> Announcement bits (2): 1-SS7-OSPF 2-KRT
>> >> >> >> AS path: I
>> >> >> >> Communities: target:64512:3200
>> >> >> >> domain-id:1.1.1.1:0
>> >> >> >> Import Accepted
>> >> >> >> VPN Label: 16
>> >> >> >> Localpref: 100
>> >> >> >> Router ID: 10.1.26.33
>> >> >> >> Primary Routing Table bgp.l3vpn.0
>> >> >> >> Indirect next hops: 1
>> >> >> >> Protocol next hop: 10.1.26.33 Metric: 1
>> >> >> >> Push 16
>> >> >> >> Indirect next hop: 8ec22d0 131070
>> >> >> >> Indirect path forwarding next hops: 1
>> >> >> >> Next hop type: Router
>> >> >> >> Next hop: 10.1.26.190 via em0.0
>> >> >> >> 10.1.26.33/32 Originating RIB: inet.3
>> >> >> >> Metric: 1 Node
>> >> >> >> path
>> >> >> >> count:
>> >> >> >> 1
>> >> >> >> Forwarding nexthops: 1
>> >> >> >> Nexthop: 10.1.26.190 via em0.0
>> >> >> >>
>> >> >> >> [edit]
>> >> >> >> root at LS-MSS-01#
>> >> >> >>
>> >> >> >> On PE1 OSPF Database Entry
>> >> >> >>
>> >> >> >>
>> >> >> >> root at LS-MSS-01# ...instance SS7 external extensive lsa-id
>> >> >> >> 10.26.66.192
>> >> >> >> OSPF AS SCOPE link state database
>> >> >> >> Type ID Adv Rtr Seq Age Opt
>> >> >> >> Cksum
>> >> >> >> Len
>> >> >> >> Extern *10.26.66.192 10.1.26.117 0x80000003 884 0xa2
>> >> >> >> 0x881a
>> >> >> >> 36
>> >> >> >> mask 255.255.255.252
>> >> >> >> Topology default (ID 0)
>> >> >> >> Type: 2, Metric: 0, Fwd addr: 0.0.0.0, Tag: 208.0.252.1
>> >> >> >> Gen timer 00:23:25
>> >> >> >> Aging timer 00:45:16
>> >> >> >> Installed 00:14:44 ago, expires in 00:45:16, sent 00:14:44 ago
>> >> >> >> Last changed 00:14:44 ago, Change count: 3, Ours
>> >> >> >>
>> >> >> >> [edit]
>> >> >> >> root at LS-MSS-01#
>> >> >> >>
>> >> >> >> On VRF-Lite_CE1 OSPF Database Entry
>> >> >> >>
>> >> >> >> root at PS-LS-01# ...instance SS7 external extensive lsa-id
>> >> >> >> 10.26.66.192
>> >> >> >> OSPF AS SCOPE link state database
>> >> >> >> Type ID Adv Rtr Seq Age Opt
>> >> >> >> Cksum
>> >> >> >> Len
>> >> >> >> Extern 10.26.66.192 10.1.26.117 0x80000003 924 0xa2
>> >> >> >> 0x881a
>> >> >> >> 36
>> >> >> >> mask 255.255.255.252
>> >> >> >> Topology default (ID 0)
>> >> >> >> Type: 2, Metric: 0, Fwd addr: 0.0.0.0, Tag: 208.0.252.1
>> >> >> >> Aging timer 00:44:36
>> >> >> >> Installed 00:15:23 ago, expires in 00:44:36
>> >> >> >> Last changed 00:15:23 ago, Change count: 3
>> >> >> >>
>> >> >> >> [edit]
>> >> >> >> root at PS-LS-01#
>> >> >> >>
>> >> >> >> root at PS-LS-01# ...se instance SS7 asbrsummary extensive
>> >> >> >>
>> >> >> >> OSPF database, Area 0.0.0.120
>> >> >> >> Type ID Adv Rtr Seq Age Opt
>> >> >> >> Cksum
>> >> >> >> Len
>> >> >> >> ASBRSum *10.1.26.117 10.200.32.5 0x80000008 193 0x22
>> >> >> >> 0x930e
>> >> >> >> 28
>> >> >> >> mask 0.0.0.0
>> >> >> >> Topology default (ID 0) -> Metric: 1
>> >> >> >> Gen timer 00:46:46
>> >> >> >> Aging timer 00:56:46
>> >> >> >> Installed 00:03:13 ago, expires in 00:56:47
>> >> >> >> Last changed 00:42:40 ago, Change count: 6, Ours
>> >> >> >>
>> >> >> >> [edit]
>> >> >> >> root at PS-LS-01#
>> >> >> >>
>> >> >> >> root at PS-LS-01# run show route table SS7
>> >> >> >>
>> >> >> >> SS7.inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0
>> >> >> >> hidden)
>> >> >> >> + = Active Route, - = Last Active, * = Both
>> >> >> >>
>> >> >> >> 10.1.26.116/30 *[OSPF/10] 00:42:59, metric 2
>> >> >> >> > to 10.200.32.6 via em1.0
>> >> >> >> 10.26.4.1/32 *[OSPF/150] 00:42:59, metric 0, tag 0
>> >> >> >> > to 10.200.32.6 via em1.0
>> >> >> >> 10.26.66.209/32 *[Local/0] 03:41:54
>> >> >> >> Reject
>> >> >> >> 10.200.32.4/30 *[Direct/0] 03:41:53
>> >> >> >> > via em1.0
>> >> >> >> 10.200.32.5/32 *[Local/0] 03:41:53
>> >> >> >> Local via em1.0
>> >> >> >> 224.0.0.5/32 *[OSPF/10] 03:42:12, metric 1
>> >> >> >> MultiRecv
>> >> >> >>
>> >> >> >> [edit]
>> >> >> >> root at PS-LS-01#
>> >> >> >>
>> >> >> >> Subnet Workig Fine : 10.200.32.4/0
>> >> >> >>
>> >> >> >> PE2 Entry
>> >> >> >>
>> >> >> >> root at TC-MSS-01# run show route table SS7 10.200.32.4 extensive
>> >> >> >>
>> >> >> >> SS7.inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0
>> >> >> >> hidden)
>> >> >> >> 10.200.32.4/30 (1 entry, 1 announced)
>> >> >> >> TSI:
>> >> >> >> OSPF area : 0.0.0.0, LSA ID : 10.200.32.4, LSA type : Extern
>> >> >> >> KRT in-kernel 10.200.32.4/30 -> {indirect(131070)}
>> >> >> >> *BGP Preference: 170/-101
>> >> >> >> Route Distinguisher: 10.1.26.1:3200
>> >> >> >> Next hop type: Indirect
>> >> >> >> Next-hop reference count: 9
>> >> >> >> Source: 10.1.26.1
>> >> >> >> Next hop type: Router, Next hop index: 578
>> >> >> >> Next hop: 10.1.26.189 via em0.0, selected
>> >> >> >> Label operation: Push 16
>> >> >> >> Protocol next hop: 10.1.26.1
>> >> >> >> Push 16
>> >> >> >> Indirect next hop: 8ec22d0 131070
>> >> >> >> State: <Secondary Active Int Ext>
>> >> >> >> Local AS: 64513 Peer AS: 64513
>> >> >> >> Age: 14:30 Metric2: 1
>> >> >> >> Task: BGP_64513.10.1.26.1+55880
>> >> >> >> Announcement bits (2): 0-SS7-OSPF 1-KRT
>> >> >> >> AS path: I
>> >> >> >> Communities: target:64512:3200
>> >> >> >> domain-id:1.1.1.1:0
>> >> >> >> Import Accepted
>> >> >> >> VPN Label: 16
>> >> >> >> Localpref: 100
>> >> >> >> Router ID: 10.1.26.1
>> >> >> >> Primary Routing Table bgp.l3vpn.0
>> >> >> >> Indirect next hops: 1
>> >> >> >> Protocol next hop: 10.1.26.1 Metric: 1
>> >> >> >> Push 16
>> >> >> >> Indirect next hop: 8ec22d0 131070
>> >> >> >> Indirect path forwarding next hops: 1
>> >> >> >> Next hop type: Router
>> >> >> >> Next hop: 10.1.26.189 via em0.0
>> >> >> >> 10.1.26.1/32 Originating RIB: inet.3
>> >> >> >> Metric: 1 Node
>> >> >> >> path
>> >> >> >> count:
>> >> >> >> 1
>> >> >> >> Forwarding nexthops: 1
>> >> >> >> Nexthop: 10.1.26.189 via em0.0
>> >> >> >>
>> >> >> >>
>> >> >> >> [edit]
>> >> >> >> root at TC-MSS-01#
>> >> >> >>
>> >> >> >> OSPF Database Entry on PE2
>> >> >> >>
>> >> >> >> root at TC-MSS-01# ...ase instance SS7 external extensive lsa-id
>> >> >> >> 10.200.32.4
>> >> >> >> OSPF AS SCOPE link state database
>> >> >> >> Type ID Adv Rtr Seq Age Opt
>> >> >> >> Cksum
>> >> >> >> Len
>> >> >> >> Extern *10.200.32.4 10.26.66.13 0x80000001 889 0xa2
>> >> >> >> 0xc338
>> >> >> >> 36
>> >> >> >> mask 255.255.255.252
>> >> >> >> Topology default (ID 0)
>> >> >> >> Type: 2, Metric: 0, Fwd addr: 0.0.0.0, Tag: 208.0.252.1
>> >> >> >> Gen timer 00:05:46
>> >> >> >> Aging timer 00:45:11
>> >> >> >> Installed 00:14:49 ago, expires in 00:45:11, sent 00:14:49 ago
>> >> >> >> Last changed 00:14:49 ago, Change count: 1, Ours
>> >> >> >>
>> >> >> >> [edit]
>> >> >> >> root at TC-MSS-01#
>> >> >> >>
>> >> >> >> OSPF Database Entry on Location_B_CE2
>> >> >> >>
>> >> >> >>
>> >> >> >> root at SAPC# run show ospf database external extensive lsa-id
>> >> >> >> 10.200.32.4
>> >> >> >> OSPF AS SCOPE link state database
>> >> >> >> Extern 10.200.32.4 10.26.66.193 0x80000001 16
>> >> >> >> 0xa2
>> >> >> >> 0x87bf
>> >> >> >> 36
>> >> >> >> mask 255.255.255.252
>> >> >> >> Topology default (ID 0)
>> >> >> >> Type: 2, Metric: 0, Fwd addr: 0.0.0.0, Tag: 208.0.252.1
>> >> >> >> Aging timer 00:59:43
>> >> >> >> Installed 00:00:15 ago, expires in 00:59:44
>> >> >> >> Last changed 00:00:15 ago, Change count: 1
>> >> >> >>
>> >> >> >> [edit]
>> >> >> >> root at SAPC#
>> >> >> >>
>> >> >> >> ASBR Summary LSA on Location_B_CE2-No output-LSA not there
>> >> >> >>
>> >> >> >> root at SAPC# run show ospf database asbrsummary extensive
>> >> >> >>
>> >> >> >> [edit]
>> >> >> >> root at SAPC#
>> >> >> >>
>> >> >> >> Location_B_CE2 Route table
>> >> >> >>
>> >> >> >> root at SAPC# run show route
>> >> >> >>
>> >> >> >> inet.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
>> >> >> >> + = Active Route, - = Last Active, * = Both
>> >> >> >>
>> >> >> >> 1.1.1.1/32 *[OSPF/10] 00:00:05, metric 1
>> >> >> >> > to 10.26.66.193 via em1.0
>> >> >> >> 10.1.26.116/30 *[OSPF/150] 00:00:05, metric 0, tag 3489725441
>> >> >> >> > to 10.26.66.193 via em1.0
>> >> >> >> 10.26.4.1/32 *[OSPF/150] 00:00:05, metric 0, tag 3489725441
>> >> >> >> > to 10.26.66.193 via em1.0
>> >> >> >> 10.26.66.192/30 *[Direct/0] 03:09:42
>> >> >> >> > via em1.0
>> >> >> >> 10.26.66.194/32 *[Local/0] 03:09:42
>> >> >> >> Local via em1.0
>> >> >> >> 10.26.251.1/32 *[Direct/0] 03:09:39
>> >> >> >> > via lo0.0
>> >> >> >> 10.200.32.4/30 *[OSPF/150] 00:00:05, metric 0, tag 3489725441
>> >> >> >> > to 10.26.66.193 via em1.0
>> >> >> >> 224.0.0.5/32 *[OSPF/10] 03:09:58, metric 1
>> >> >> >> MultiRecv
>> >> >> >>
>> >> >> >> [edit]
>> >> >> >> root at SAPC#
>> >> >> >>
>> >> >> >>
>> >> >> >> Any pointers would be much appreciated.
>> >> >> >>
>> >> >> >>
>> >> >> >> Regards
>> >> >> >> Vaibhava Varma
>> >> >> >> _______________________________________________
>> >> >> >> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> >> >> >> https://puck.nether.net/mailman/listinfo/juniper-nsp
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Best Regards!
>> >> >> >
>> >> >> > Ivan Ivanov
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Regards
>> >> >> Vaibhava Varma
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Best Regards!
>> >> >
>> >> > Ivan Ivanov
>> >>
>> >>
>> >>
>> >> --
>> >> Regards
>> >> Vaibhava Varma
>> >
>> >
>> >
>> >
>> > --
>> > Best Regards!
>> >
>> > Ivan Ivanov
>>
>>
>>
>> --
>> Regards
>> Vaibhava Varma
>
>
>
>
> --
> Best Regards!
>
> Ivan Ivanov
--
Regards
Vaibhava Varma
More information about the juniper-nsp
mailing list