Quantcast
Channel: All Routing posts
Viewing all 8688 articles
Browse latest View live
↧

MX480 - 16.3 - 6VPE IPv6 Routes Hidden

February 1, 2017, 8:13 am
$
0
0

Greetings.

 

I have been struggling with completing a setup in the lab where I have 2 MX's routers acting as PEs.  The default RI is configured for MPBGP peering where both IPv4 and IPv6 routes will be distributed to various VRFs. The Ipv4 works fine.  I have gone through many different websites and tried many configurations and I am still unable to get the IPv6 routes to become usable.  I know I am missing a secret sauce but at this point I am unable to figure it out.  Looking for valid suggections (really appreciate it).

 

I am using the Mapped IPv4<>IPv6 addresses for the interfaces between the 2 nodes.  The route I am concerend with is 2021:........ 

 

The interface ae44 is the link from the MX to a series of QFX switched where the end CE device is located.  VLAN 2300 and 2301 are the redundant paths to the end device, I cna ping both the IPv4 and v6 addresses across the links.  I am only working on 1 of the PEs at the moment to get the setup working.  IPv4 is working to both PEs today.

 

Please let me know what other info you need to look at.  Again, I really appreciate the help in advance.

 

<snippets>

set version 16.1R3.10
set system allow-v4mapped-packets
set interfaces ae44 description "MX10 to SWL044VC Underlay"
set interfaces ae44 vlan-tagging
set interfaces ae44 mtu 9022
set interfaces ae44 encapsulation extended-vlan-bridge
set interfaces ae44 aggregated-ether-options lacp active
set interfaces ae44 aggregated-ether-options lacp periodic fast
set interfaces ae44 unit 303 vlan-id 303
set interfaces ae44 unit 309 vlan-id 309
set interfaces ae44 unit 323 vlan-id 323
set interfaces ae44 unit 329 vlan-id 329
set interfaces ae44 unit 2300 vlan-id 2300
set interfaces ae44 unit 2301 vlan-id 2301
set interfaces ae44 unit 2350 vlan-id 2350
set interfaces ae44 unit 2351 vlan-id 2351
set interfaces ae44 unit 2352 vlan-id 2352
set interfaces ae44 unit 2353 vlan-id 2353
set interfaces ae44 unit 2360 vlan-id 2360
set interfaces ae44 unit 2361 vlan-id 2361
set interfaces ae44 unit 2362 vlan-id 2362
set interfaces ae44 unit 2363 vlan-id 2363
set interfaces irb mtu 9022
set interfaces irb gratuitous-arp-reply
set interfaces irb unit 303 family inet address 172.18.120.1/24
set interfaces irb unit 309 family inet address 172.18.121.1/24
set interfaces irb unit 323 family inet address 172.18.122.1/24
set interfaces irb unit 329 family inet address 172.18.123.1/24
set interfaces irb unit 2300 family inet address 10.220.21.1/30
set interfaces irb unit 2300 family inet address 10.220.23.1/30
set interfaces irb unit 2300 family inet6 address ::ffff:10.220.21.1/126
set interfaces irb unit 2300 family mpls
set interfaces irb unit 2301 family inet address 10.220.21.5/30
set interfaces irb unit 2301 family inet address 10.220.23.5/30
set interfaces irb unit 2301 family inet6 address ::ffff:adc:1505/126
set interfaces irb unit 2301 family mpls
set interfaces irb unit 2350 family inet address 10.220.21.9/30
set interfaces irb unit 2350 family inet address 10.220.23.9/30
set interfaces irb unit 2350 family inet6 address 2275:0:0:3fd:10:220:21:9/126
set interfaces irb unit 2351 family inet address 10.220.21.17/30
set interfaces irb unit 2351 family inet address 10.220.23.17/30
set interfaces irb unit 2351 family inet6 address 2275:0:0:3fd:10:220:21:d/126
set interfaces irb unit 2352 family inet address 10.220.21.25/30
set interfaces irb unit 2352 family inet address 10.220.23.25/30
set interfaces irb unit 2352 family inet6 address 2275:0:0:3fd:10:220:21:11/126
set interfaces irb unit 2353 family inet6 address 2275:0:0:3fd:10:220:21:31/126
set interfaces irb unit 2360 family inet address 10.220.21.13/30
set interfaces irb unit 2360 family inet address 10.220.23.13/30
set interfaces irb unit 2360 family inet6 address 2275:0:0:3fd:10:220:21:15/126
set interfaces irb unit 2361 family inet address 10.220.21.21/30
set interfaces irb unit 2361 family inet address 10.220.23.21/30
set interfaces irb unit 2361 family inet6 address 2275:0:0:3fd:10:220:21:19/126
set interfaces irb unit 2362 family inet address 10.220.21.29/30
set interfaces irb unit 2362 family inet address 10.220.23.29/30
set interfaces irb unit 2362 family inet6 address 2275:0:0:3fd:10:220:21:1d/126
set interfaces irb unit 2363 family inet6 address 2275:0:0:3fd:10:220:21:35/126
set interfaces lo0 unit 0 family inet address 10.229.21.2/32
set interfaces lo0 unit 0 family inet6 address 2275:0:0:3fd:10:229:21:2/128
set interfaces lo0 unit 0 family inet6 address ::ffff:10.229.21.2/128
set interfaces lo0 unit 21 family inet address 10.229.21.2/32
set interfaces lo0 unit 2232 family inet6 address 2275:0:0:3fd:10:229:21:31/128

    set routing-options static route 10.229.21.1/32 next-hop 10.220.21.2
    set routing-options static route 10.229.21.1/32 next-hop 10.220.21.6
    set routing-options static route 10.229.21.21/32 next-hop 10.220.21.18
    set routing-options static route 10.229.21.21/32 next-hop 10.220.21.22
    set routing-options static route 10.229.21.31/32 next-hop 10.220.21.26
    set routing-options static route 10.229.21.31/32 next-hop 10.220.21.30
    set routing-options static route 10.229.23.1/32 next-hop 10.220.23.2
    set routing-options static route 10.229.23.1/32 next-hop 10.220.23.6
    set routing-options static route 10.229.23.21/32 next-hop 10.220.23.18
    set routing-options static route 10.229.23.21/32 next-hop 10.220.23.22
    set routing-options static route 10.229.23.31/32 next-hop 10.220.23.26
    set routing-options static route 10.229.23.31/32 next-hop 10.220.23.30
    set routing-options rib-groups myrib import-rib VF-NC-S1-OPCO2.inet.0
    set routing-options rib-groups myrib import-rib VF-NC-S1-OPCO1.inet.0
    set routing-options rib-groups myrib import-rib inet.0
    set routing-options rib-groups myrib import-rib VF-NC-SGi.inet.0
    set routing-options rib-groups myrib import-rib inet6.3
    set routing-options rib-groups myrib import-rib VF-NC-SGi.inet6.0
    set routing-options route-distinguisher-id 172.18.74.30
    set routing-options autonomous-system 10100
    set routing-options forwarding-table export load-balancing-policy
    set routing-options resolution rib bgp.l3vpn.0 resolution-ribs inet.0
    set protocols mpls ipv6-tunneling
    set protocols mpls interface ae44.2300
    set protocols mpls interface ae44.2301

    set protocols bgp group vf-nc-mpbgp type external
    set protocols bgp group vf-nc-mpbgp multihop ttl 2
    set protocols bgp group vf-nc-mpbgp accept-remote-nexthop
    set protocols bgp group vf-nc-mpbgp local-address 10.229.21.2
    set protocols bgp group vf-nc-mpbgp family inet unicast
    set protocols bgp group vf-nc-mpbgp family inet-vpn unicast
    set protocols bgp group vf-nc-mpbgp family inet6 labeled-unicast explicit-null  <<< This is the latest config change.  I have tried not using this as well.
    set protocols bgp group vf-nc-mpbgp family inet6-vpn unicast
    set protocols bgp group vf-nc-mpbgp vpn-apply-export
    set protocols bgp group vf-nc-mpbgp bfd-liveness-detection minimum-interval 167
    set protocols bgp group vf-nc-mpbgp bfd-liveness-detection minimum-receive-interval 167
    set protocols bgp group vf-nc-mpbgp bfd-liveness-detection multiplier 3
    set protocols bgp group vf-nc-mpbgp bfd-liveness-detection no-adaptation
    set protocols bgp group vf-nc-mpbgp bfd-liveness-detection session-mode multihop
    set protocols bgp group vf-nc-mpbgp multipath
    set protocols bgp group vf-nc-mpbgp neighbor 10.229.21.1 peer-as 10210

    set routing-instances VF-NC-SGi instance-type vrf
    set routing-instances VF-NC-SGi interface ae13.2231
    set routing-instances VF-NC-SGi route-distinguisher 172.18.74.30:300
    set routing-instances VF-NC-SGi vrf-target import target:10100:300
    set routing-instances VF-NC-SGi vrf-target export target:10100:300
    set routing-instances VF-NC-SGi vrf-table-label
    set routing-instances VF-NC-SGi routing-options static route 0.0.0.0/0 next-hop 192.168.12.201
    set routing-instances VF-NC-SGi routing-options autonomous-system 121030
    set routing-instances VF-NC-SGi routing-options auto-export
    set routing-instances VF-NC-SGi protocols bgp graceful-restart
    set routing-instances VF-NC-SGi protocols bgp group vf-nc-sgi type external
    set routing-instances VF-NC-SGi protocols bgp group vf-nc-sgi local-address 192.168.12.202
    set routing-instances VF-NC-SGi protocols bgp group vf-nc-sgi peer-as 121200
    set routing-instances VF-NC-SGi protocols bgp group vf-nc-sgi local-as 121031
    set routing-instances VF-NC-SGi protocols bgp group vf-nc-sgi multipath
    set routing-instances VF-NC-SGi protocols bgp group vf-nc-sgi neighbor 192.168.12.201

    <snippet>
    labadmin@rchmx480-vmcg10> show route table VF-NC-SGi.inet6.0 detail hidden

    VF-NC-SGi.inet6.0: 20 destinations, 20 routes (3 active, 0 holddown, 17 hidden)
    2021:1:2:1::/64 (1 entry, 0 announced)
             BGP    Preference: 170/-101
                    Route Distinguisher: 10210:300
                    Next hop type: Unusable, Next hop index: 0
                    Address: 0x283ec84
                    Next-hop reference count: 50
                    State: <Secondary Hidden Ext ProtectionCand>
                    Local AS: 10100 Peer AS: 10210
                    Age: 17:06:35   Metric: 1
                    Validation State: unverified
                    Task: BGP_10210.10.229.21.1
                    AS path: 10210 ?
                    Communities: target:10100:300
                    Import Accepted
                    VPN Label: 42
                    Localpref: 100
                    Router ID: 21.21.1.1
                    Primary Routing Table bgp.l3vpn-inet6.0

    2021:1:2:2::/63 (1 entry, 0 announced)
             BGP    Preference: 170/-101
                    Route Distinguisher: 10210:300
                    Next hop type: Unusable, Next hop index: 0
                    Address: 0x283ec84
                    Next-hop reference count: 50                    State: <Secondary Hidden Ext ProtectionCand>
                    Local AS: 10100 Peer AS: 10210
                    Age: 17:06:35   Metric: 1
                    Validation State: unverified
                    Task: BGP_10210.10.229.21.1
                    AS path: 10210 ?
                    Communities: target:10100:300
                    Import Accepted
                    VPN Label: 43
                    Localpref: 100
                    Router ID: 21.21.1.1
                    Primary Routing Table bgp.l3vpn-inet6.0

    labadmin@rchmx480-vmcg10> show bgp summary
    Groups: 9 Peers: 13 Down peers: 1
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet.0
                          78         21          0          0          0          0
    inet6.0
                           0          0          0          0          0          0
    bgp.l3vpn.0
                         107        107          0          0          0          0
    bgp.l3vpn-inet6.0
                          25          0          0          0          0          0
    Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    10.229.21.1           10210       2068       2250       0       0    17:07:09 Establ
      inet.0: 0/9/9/0
      bgp.l3vpn.0: 21/21/21/0
      bgp.l3vpn-inet6.0: 0/22/22/0
      VF-NC-S1-OPCO1.inet6.0: 0/3/3/0
      VF-NC-S1-OPCO1.inet.0: 9/9/9/0
      VF-NC-S1-OPCO2.inet.0: 9/9/9/0
      VF-NC-SGi.inet.0: 3/3/3/0
      VF-NC-S1-OPCO2.inet6.0: 0/2/2/0
      VF-NC-SGi.inet6.0: 0/17/17/0 <<<<<<<<<<<<<Hidden routes.
↧
Search

Re: Problems peering between two iBGP peers

February 1, 2017, 10:40 am
$
0
0

DOH! I didn't really think of that.  I removed the AS padding and played with some of the other options and it plunked right into inet.0.  So, there ya go. Thanks for pointing that out.

↧
↧

Re: MX480 - 16.3 - 6VPE IPv6 Routes Hidden

February 1, 2017, 11:04 am
$
0
0

Hello,

 

There is a lot of configuration that is extra or not needed. There's a confusion in your rib-groups, you have a lot of tables in "myrib" and you're not applying it anywhere, so it's not doing anything. Also, you are making routes from bgp.l3vpn.0 to be resolved via inet.0, which makes me think you have no routes in inet.3, so no routes will be copied to inet6.3 with "ipv6-tunneling". Could you share a simple diagram with the devices, connections and IP's (phy interfaces, sub-interfaces/vlans and loopbacks). (This could speed up if I could access the lab via teamviewer or something similar)

 

This could show you a bit what is happening:

show route resolution unresolved         

show route receive-protocol bgp 10.229.21.1 table bgp.l3vpn-inet6.0 hidden  <<< Get the next hop x.x.x.x

show route x.x.x.x

 

 

↧

Re: MX480 - 16.3 - 6VPE IPv6 Routes Hidden

February 1, 2017, 12:38 pm
$
0
0

You are corect, there are no routes in inet.3 or inet6.3.  Some of this configuration I used from a few websites showing IPv4.  All the routes and traffic flow are correct and work (by accident, maybe) for v4 but the issue is v6 and some of that very well can be a misunderstanding. 

 

MPBGP is new to me and the work I am doing.  I will try to put a pic together. 

 

labadmin@rchmx480-vmcg10> show route receive-protocol bgp 10.229.21.1 table bgp.l3vpn-inet6.0 hidden

bgp.l3vpn-inet6.0: 34 destinations, 34 routes (9 active, 0 holddown, 25 hidden)
Restart Complete
  Prefix                  Nexthop              MED     Lclpref    AS path
  10210:300:2021:1:2:1::/64
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2021:1:2:2::/63
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2021:1:2:4::/62
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2021:1:2:8::/61
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2021:1:2:10::/60
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2021:1:2:20::/59
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2021:1:2:40::/58
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2021:1:2:80::/57
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2021:1:2:100::/56
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2021:1:2:200::/55
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2021:1:2:400::/54
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2021:1:2:800::/53
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2021:1:2:1000::/52
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2021:1:2:2000::/51
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2021:1:2:4000::/50
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2021:1:2:8000::/49
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:300:2280::1020:2:2010:8:101/128
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:101:2280::1020:2:2011:3:1/128
                          ::ffff:10.229.21.1   1                  10210 ?
  10210:101:fdc9::4e99:10:210:21:0/125
                          ::ffff:10.229.21.1                      10210 ?
  10210:101:fdc9::4e99:10:210:21:8/125
                          ::ffff:10.229.21.1                      10210 ?
  10210:102:fdc9::4e99:ad2:1510/125
                          ::ffff:10.229.21.1                      10210 ?
  10210:102:fdc9::4e99:ad2:1518/125
                          ::ffff:10.229.21.1                      10210 ?



labadmin@rchmx480-vmcg10> show route table inet6.3

labadmin@rchmx480-vmcg10> show route table inet.3<snippet>
labadmin@rchmx480-vmcg10> show route resolution unresolved
Tree Index 1
Tree Index 2
Tree Index 6
Tree Index 3
Tree Index 4
10210:300:2021:1:2:2::/127
        Protocol Nexthop: ::ffff:10.229.21.1 Push 43
        Indirect nexthop: 0x0 - INH Session ID: 0x0      Path forwarding nexthops link: 0x0
         Path inh link: 0x0

10210:300:2021:1:2:4::/126
        Protocol Nexthop: ::ffff:10.229.21.1 Push 44
        Indirect nexthop: 0x0 - INH Session ID: 0x0      Path forwarding nexthops link: 0x0
         Path inh link: 0x0

10210:300:2021:1:2:8::/125
        Protocol Nexthop: ::ffff:10.229.21.1 Push 45
        Indirect nexthop: 0x0 - INH Session ID: 0x0      Path forwarding nexthops link: 0x0
         Path inh link: 0x0

10210:300:2021:1:2:10::/124
        Protocol Nexthop: ::ffff:10.229.21.1 Push 46
        Indirect nexthop: 0x0 - INH Session ID: 0x0      Path forwarding nexthops link: 0x0
         Path inh link: 0x0

10210:300:2021:1:2:20::/123
        Protocol Nexthop: ::ffff:10.229.21.1 Push 47
        Indirect nexthop: 0x0 - INH Session ID: 0x0      Path forwarding nexthops link: 0x0
         Path inh link: 0x0

10210:300:2021:1:2:40::/122
        Protocol Nexthop: ::ffff:10.229.21.1 Push 48
        Indirect nexthop: 0x0 - INH Session ID: 0x0      Path forwarding nexthops link: 0x0
         Path inh link: 0x0

I have attached a simple PDF of the configuration.  

↧

Re: MX480 - 16.3 - 6VPE IPv6 Routes Hidden

February 1, 2017, 1:05 pm
$
0
0

Don't worry, 6PE and 6VPE is and advanced topic if you're new to MP-BGP.

 

Your issue is that ::ffff:10.229.21.1 is not present on inet6.3, and bgp.l3vpn-inet6.0 resolves it's routes next-hops with inet6.3. I understand the PE's are directly connected (no need for an LSP to reach 10.229.21.1), so you can use a rib-group to export the direct route 10.229.21.1 from inet.0 to inet6.3, this will automatically place the route as an ipv6 ipv4-mapped address in inet6.3. The simplest way to do this:

 

set routing-options rib-group inet0-inet63 import-rib [inet.0 inet6.3]          <<< create the rib-group stating that routes placed in inet.0 should also be placed in inet6.3 (this does not do anything by itself)

set routing-options interface-routes rib-group inet inet0-inet63        <<< this applies the rib-group to the interface routes (protocol direct) in the router.

 

You could also add a policy to filter only 10.229.21.1/32 in the rib-group.

 

Kindly try that and check again the same commands.

 

 

↧
↧

Re: MX480 - 16.3 - 6VPE IPv6 Routes Hidden

February 1, 2017, 2:00 pm
$
0
0

I want to thank you for your time.  I had to modify the command you provided as if gave an error (inet.0 vs inet6.0) .  The biggest thing is learning how all the various route tables are used and shared with the system. 

 

set routing-options rib-groups inet0-inet63 import-rib inet6.0
set routing-options rib-groups inet0-inet63 import-rib inet6.3

set routing-options interface-routes rib-group inet6 inet0-inet63

set routing-options rib inet6.3 static route ::ffff:10.229.21.1/128 next-hop ::ffff:10.220.21.2
set routing-options rib inet6.3 static route ::ffff:10.229.21.1/128 next-hop ::ffff:10.220.21.6

labadmin@rchmx480-vmcg10# run show route table VF-NC-SGi.inet6.0

VF-NC-SGi.inet6.0: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

2021:1:2:1::/64    *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified
                    > to ::ffff:10.220.21.2 via irb.2300, Push 42
                      to ::ffff:10.220.21.6 via irb.2301, Push 42
2021:1:2:2::/63    *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified> to ::ffff:10.220.21.2 via irb.2300, Push 43
                      to ::ffff:10.220.21.6 via irb.2301, Push 43
2021:1:2:4::/62    *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified> to ::ffff:10.220.21.2 via irb.2300, Push 44
                      to ::ffff:10.220.21.6 via irb.2301, Push 44
2021:1:2:8::/61    *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified
                      to ::ffff:10.220.21.2 via irb.2300, Push 45> to ::ffff:10.220.21.6 via irb.2301, Push 45
2021:1:2:10::/60   *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified> to ::ffff:10.220.21.2 via irb.2300, Push 46
                      to ::ffff:10.220.21.6 via irb.2301, Push 46
2021:1:2:20::/59   *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified> to ::ffff:10.220.21.2 via irb.2300, Push 47
                      to ::ffff:10.220.21.6 via irb.2301, Push 47
2021:1:2:40::/58   *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified> to ::ffff:10.220.21.2 via irb.2300, Push 48
                      to ::ffff:10.220.21.6 via irb.2301, Push 48
2021:1:2:80::/57   *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified> to ::ffff:10.220.21.2 via irb.2300, Push 49
                      to ::ffff:10.220.21.6 via irb.2301, Push 49
2021:1:2:100::/56  *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified> to ::ffff:10.220.21.2 via irb.2300, Push 50
                      to ::ffff:10.220.21.6 via irb.2301, Push 50
2021:1:2:200::/55  *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified> to ::ffff:10.220.21.2 via irb.2300, Push 51
                      to ::ffff:10.220.21.6 via irb.2301, Push 51
2021:1:2:400::/54  *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified> to ::ffff:10.220.21.2 via irb.2300, Push 52
                      to ::ffff:10.220.21.6 via irb.2301, Push 52
2021:1:2:800::/53  *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified
                      to ::ffff:10.220.21.2 via irb.2300, Push 53> to ::ffff:10.220.21.6 via irb.2301, Push 53
2021:1:2:1000::/52 *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified> to ::ffff:10.220.21.2 via irb.2300, Push 54
                      to ::ffff:10.220.21.6 via irb.2301, Push 54
2021:1:2:2000::/51 *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified> to ::ffff:10.220.21.2 via irb.2300, Push 55
                      to ::ffff:10.220.21.6 via irb.2301, Push 55
2021:1:2:4000::/50 *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified> to ::ffff:10.220.21.2 via irb.2300, Push 56
                      to ::ffff:10.220.21.6 via irb.2301, Push 56
2021:1:2:8000::/49 *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified> to ::ffff:10.220.21.2 via irb.2300, Push 57
                      to ::ffff:10.220.21.6 via irb.2301, Push 57
2275::3fc:192:168:12:300/126
                   *[Direct/0] 3w0d 06:02:19> via ae13.2231
2275::3fc:192:168:12:302/128
                   *[Local/0] 3w0d 06:02:19
                      Local via ae13.2231
2280::1020:2:2010:8:101/128
                   *[BGP/170] 00:02:29, MED 1, localpref 100, from 10.229.21.1
                      AS path: 10210 ?, validation-state: unverified
                      to ::ffff:10.220.21.2 via irb.2300, Push 58> to ::ffff:10.220.21.6 via irb.2301, Push 58
fe80::223:9c08:b7fb:e8c2/128
                   *[Local/0] 3w0d 06:02:19
                      Local via ae13.2231


[edit]
labadmin@rchmx480-vmcg10# run ping routing-instance VF-NC-SGi 2280::1020:2:2010:8:101
PING6(56=40+8+8 bytes) 2275::3fc:192:168:12:302 --> 2280::1020:2:2010:8:101
16 bytes from 2280::1020:2:2010:8:101, icmp_seq=0 hlim=64 time=2.126 ms
16 bytes from 2280::1020:2:2010:8:101, icmp_seq=1 hlim=64 time=1.812 ms
16 bytes from 2280::1020:2:2010:8:101, icmp_seq=2 hlim=64 time=2.417 ms
16 bytes from 2280::1020:2:2010:8:101, icmp_seq=3 hlim=64 time=2.308 ms
^C
--- 2280::1020:2:2010:8:101 ping6 statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/std-dev = 1.812/2.166/2.417/0.229 ms

I was able to ping from the PE to a loopback on the end device and it works. 

↧

Re: MX480 - 16.3 - 6VPE IPv6 Routes Hidden

February 1, 2017, 2:31 pm
$
0
0
Glad to know you learned something! Sorry for the confusion with the inet0 and inet6, forgot the 6 hehe.
↧

MVPN - PE configurations

February 2, 2017, 11:08 am
$
0
0

Hello,

Need help migrating configs from Cisco to Juniper for a customer scenario that needs Multicast over MPLS/L3VPN.

 

I have the Juniper config guide for Multicast, and it has a very good section for "Next-Generation Network Multicast VPNs".

 

The problem is that there are so many variations of MVPN, that it is confusing as to what is mandatory in a basic stripped-down MVPN config (for a lab scenario).   All I need is basic multicast working between the CE's (over a working L3VPN lab).   Once I  have it up and working, I can play with the tuning options.

 

Much thanks in advance for the communities help with this.

 

NOTE:   currently using this Juniper guide-book.  Junos OS: Multicast Protocols Feature Guide (2017)

↧
Search

Expand loose hop - MPLS LSP across domains

February 2, 2017, 11:52 am
$
0
0

Hi,

 

I'm using the vMX to test MPLS LSP across differnet OSPF areas/AS.

 

I can't seem to get the following configuration to work

 

Topology

R1 (10.200.86.1) -> R3 -> R5 (ASBR) -> R7 (ASBR) -> R9 -R12 (10.200.86.12)

 

root@vMX-R1> show configuration protocols mpls
label-switched-path R1-to-R12 {
from 10.200.86.1;
to 10.200.86.12;
inter-domain;
}

 

root@vMX-R1> show mpls lsp extensive
Ingress LSP: 1 sessions

10.200.86.12
From: 10.200.86.1, State: Dn, ActiveRoute: 0, LSPname: R1-to-R12
ActivePath: (none)
PathDomain: Inter-domain
LSPtype: Static Configured, Penultimate hop popping
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
Primary State: Dn
Priorities: 7 0
SmartOptimizeTimer: 180
Will be enqueued for recomputation in 20 second(s).
58 Feb 2 19:48:19.543 CSPF failed: no route toward 10.200.86.12[73 times]

 

ASBR configs

root@vMX-R5> show configuration protocols ospf
traffic-engineering;
area 0.0.0.0 {
interface xe-0/0/0.0;
interface lo0.0 {
passive;
}
interface xe-0/0/1.0;
interface xe-0/0/2.0 {
passive {
traffic-engineering {
remote-node-id 192.168.86.21;
}
}
}
interface xe-0/0/3.0;
interface lt-0/0/0.0;
}

 

root@vMX-R5> show configuration protocols mpls
expand-loose-hop;
interface xe-0/0/0.0;
interface xe-0/0/1.0;
interface xe-0/0/2.0;
interface xe-0/0/3.0;

 

root@vMX-R7> show configuration protocols ospf
traffic-engineering;
area 0.0.0.0 {
interface xe-0/0/0.0 {
passive {
traffic-engineering {
remote-node-id 192.168.86.22;
remote-node-router-id 10.200.86.5;
}
}
}
interface lo0.0 {
passive;
}
interface xe-0/0/1.0;
interface xe-0/0/2.0;
interface xe-0/0/3.0;
}

 

root@vMX-R7> show configuration protocols mpls
expand-loose-hop;
interface xe-0/0/0.0;
interface xe-0/0/1.0;
interface xe-0/0/2.0;
interface xe-0/0/3.0;

 

 

TED database from R1

root@vMX-R1> show ted database
TED database: 0 ISIS nodes 37 INET nodes
ID Type Age(s) LnkIn LnkOut Protocol
10.5.1.1-1 Net 7538 0 2 OSPF(0.0.0.0)
To: 10.200.86.5, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 5.5.5.5, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
10.200.86.1 Rtr 341 2 1 OSPF(0.0.0.0)
To: 192.168.86.6-1, Local: 192.168.86.6, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
10.1.1.2 --- 3793 1 0
10.1.1.2-1 Net 3793 0 2 OSPF(0.0.0.0)
To: 10.1.1.2, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.1, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.2-1 Net 3804 2 2 OSPF(0.0.0.0)
To: 10.200.86.2, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.4, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
10.200.86.2 Rtr 371 2 2 OSPF(0.0.0.0)
To: 192.168.86.74-1, Local: 192.168.86.74, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 192.168.86.2-1, Local: 192.168.86.2, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
10.200.86.3 Rtr 163 3 2 OSPF(0.0.0.0)
To: 192.168.86.45-1, Local: 192.168.86.45, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 192.168.86.6-1, Local: 192.168.86.5, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
10.200.86.4 Rtr 370 3 3 OSPF(0.0.0.0)
To: 192.168.86.42-1, Local: 192.168.86.42, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 192.168.86.81-1, Local: 192.168.86.82, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 192.168.86.2-1, Local: 192.168.86.1, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
5.5.5.5 --- 7538 1 0
10.200.86.5 Rtr 298 4 2 OSPF(0.0.0.0)
To: 192.168.86.21, Local: 192.168.86.22, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 192.168.86.45-1, Local: 192.168.86.46, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.6-1 Net 341 2 2 OSPF(0.0.0.0)
To: 10.200.86.1, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.3, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
10.200.86.6 Rtr 2221 2 4 OSPF(0.0.0.0)
To: 192.168.86.49-1, Local: 192.168.86.50, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 192.168.86.81-1, Local: 192.168.86.81, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 192.168.86.10-1, Local: 192.168.86.9, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 192.168.86.25, Local: 192.168.86.26, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
10.200.86.7 Rtr 2383 3 4 OSPF(0.0.0.0)
To: 192.168.86.65-1, Local: 192.168.86.66, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.5, Local: 192.168.86.21, Remote: 192.168.86.22
Local interface index: 0, Remote interface index: 0
To: 192.168.86.34-1, Local: 192.168.86.34, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 192.168.86.93-1, Local: 192.168.86.93, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
10.200.86.8 Rtr 2378 4 4 OSPF(0.0.0.0)
To: 192.168.86.65-1, Local: 192.168.86.65, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 192.168.86.98-1, Local: 192.168.86.97, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 192.168.86.25-1, Local: 192.168.86.25, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 192.168.86.101-1, Local: 192.168.86.101, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
10.200.86.9 Rtr 401 3 2 OSPF(0.0.0.0)
To: 192.168.86.34-1, Local: 192.168.86.33, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 192.168.86.105-1, Local: 192.168.86.105, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.10-1 --- 2365 1 0
10.200.86.10 --- 409 5 0
10.200.86.11 --- 5217 2 0
10.200.86.12 Rtr 113 1 1 OSPF(0.0.0.0)
To: 192.168.86.113-1, Local: 192.168.86.114, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
10.200.86.13 --- 2378 1 0
192.168.86.21 --- 2742 1 0
192.168.86.25 --- 2221 1 0
192.168.86.25-1 Net 2378 1 2 OSPF(0.0.0.0)
To: 10.200.86.6, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.8, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.34-1 Net 5301 2 2 OSPF(0.0.0.0)
To: 10.200.86.7, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.9, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.42-1 Net 3097 1 2 OSPF(0.0.0.0)
To: 10.200.86.4, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.5, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.45-1 Net 163 2 2 OSPF(0.0.0.0)
To: 10.200.86.5, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.3, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.49-1 --- 3148 1 0
192.168.86.65-1 Net 2383 2 2 OSPF(0.0.0.0)
To: 10.200.86.7, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.8, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.74-1 Net 563 1 2 OSPF(0.0.0.0)
To: 10.200.86.2, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.3, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.81-1 Net 2522 2 2 OSPF(0.0.0.0)
To: 10.200.86.4, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.6, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.93-1 Net 5139 1 2 OSPF(0.0.0.0)
To: 10.200.86.7, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.10, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.98-1 Net 2383 1 2 OSPF(0.0.0.0)
To: 10.200.86.8, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.10, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.101-1 Net 5217 1 2 OSPF(0.0.0.0)
To: 10.200.86.8, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.11, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.105-1 Net 5031 1 2 OSPF(0.0.0.0)
To: 10.200.86.9, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.10, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.109-1 Net 5301 0 2 OSPF(0.0.0.0)
To: 10.200.86.10, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.11, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.113-1 Net 5301 1 2 OSPF(0.0.0.0)
To: 10.200.86.9, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.12, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
ID Type Age(s) LnkIn LnkOut Protocol
192.168.86.138-1 Net 5301 0 2 OSPF(0.0.0.0)
To: 10.200.86.10, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0
To: 10.200.86.13, Local: 0.0.0.0, Remote: 0.0.0.0
Local interface index: 0, Remote interface index: 0

↧
↧

Re: Expand loose hop - MPLS LSP across domains

February 2, 2017, 2:27 pm
$
0
0

Hello,

 

Interesting scenario, we will have to check it step by step. You need a route towards 10.200.86.12 in R1 (could be in inet.0), could you do a "show route" for that? Also, you have remote-node-router-id only specified on one of the ASBRs, I don't think it is needed.

 

Besides from that, seems weird that the TED in R1 has node info from R9, it isn't supposed to, as they are in separate ospf domains.

↧

Re: MVPN - PE configurations

February 2, 2017, 6:26 pm
$
0
0

Hi,

 

Have you tried this link, this has working example you are looking for.

 

https://www.juniper.net/documentation/en_US/junos15.1/topics/example/multicast-vpn-example-mbgp-mvpn-solutions.html

 

Hope it helps.

 

----------------------------------------------------------------------------------------------------
If this post was helpful, please mark this post as an "Accepted Solution".
Kudos are always appreciated!
----------------------------------------------------------------------------------------------------

↧

Re: Problem with FPC on mx5

February 3, 2017, 2:01 am
$
0
0

root@jMX80-Test> show chassis network-services
Network Services Mode: Enhanced-IP

root@jMX80-Test> show configuration chassis network-services

root@jMX80-Test> configure
Entering configuration mode

↧

ospf area0 not connected

February 3, 2017, 3:36 am
$
0
0

 ospf.jpg

 

 

as shown above a019's area0 is not connected to a020's area0(they connect to each via trunk which work for area1)

 

Same problem for b019/020

 

1:what is the impact of this design?(better to use traffic to explain)

2:how to fix

 

Thanks in advance   I love juniper

↧
↧

Re: ospf area0 not connected

February 3, 2017, 10:12 am
$
0
0

Hello,

 

I hope you are doing well. From what I understand, you have two separate areas, both area 0. The trunk links a019-a020 and b019-b020 are both configured in area 1. Taking the previous into account:

 

1. This will prevent the router's in one area 0 to see the routes from the other area 0 routers. For example,a019 will only see the routes from b019 and the area 1 link with a020, but it will not install any routes from a020-b020's backbone. So no traffic will be able to flow from the left side of your diagram to the right and vice-versa.

2. The logical thing would be to change the area1 links to area0, but that's obvious and I imagine you have reasons for not doing this, what are this conditions? You could use virtual-links or multiarea adjacency. But the most important questions to really give a good answer are:

- Why are a019-a020 and b019-b020 links in area 1 and for which reasons should they remain that way (if there are any)?

- What is the role of router1, router4, router5 and router6? Are they also part of ospf, if so of which area?

 

Regards,

 

 

↧

Re: MVPN - PE configurations

February 3, 2017, 11:33 am
$
0
0

Hi Sara,

Thanks for responding so quickly.

Yes.  Your link is a sub-heading of the full doc that I linked. It is the best example that I can find out there for the JUNIPER configuration, but it is still a little confusing.

 

Part of the problem that I am having is setting up the PROVIDER-TUNNEL, is that the example uses RSVP-TE.  

  • My lab is a basic LDP with a functioning L3VPN network between CPE's. 
  • possible missing or misconfigure provider-tunnel config?

 

I really need help on my config, because I am starting to throw the whole toolbox of commands -- without really knowing what I am missing.   I am attaching the configs for PE1 and PE2.

 

===================

CPE-1-----PE1----P1----P2----PE2-----CPE-2

  • ISIS/LDP/BGP for L3VPN underlay
  • OSPF for CPE-to-CPE ipv4 routing is good

 SomeLabGuy@CPE-1> traceroute 200.200.200.200 source 100.100.100.100
note:   traceroute to CPE-2 loopback from CPE-1 loopback  
 1  192.168.1.1 (192.168.1.1)  4.064 ms  2.493 ms  2.292 ms
 2  12.12.12.2 (12.12.12.2)  3.705 ms  5.336 ms  4.046 ms
     MPLS Label=299808 CoS=0 TTL=1 S=0
     MPLS Label=16 CoS=0 TTL=1 S=1
 3  23.23.23.3 (23.23.23.3)  3.643 ms  4.275 ms  3.671 ms
     MPLS Label=299808 CoS=0 TTL=1 S=0
     MPLS Label=16 CoS=0 TTL=2 S=1
 4  172.16.2.200 (172.16.2.200)  4.199 ms *  4.505 ms

 

===================

PE1 (relative config is attached):

SomeLabGuy@PE1> show mvpn neighbor
MVPN instance:
<snip legend>
Family : INET

Instance : CPE-1
  MVPN Mode : RPT-SPT


<snip>


Instance : CPE-1
  MVPN Mode : RPT-SPT

 


SomeLabGuy@PE1> show mvpn instance
MVPN instance:
<snip legend>
Family : INET

Instance : CPE-1
  MVPN Mode : RPT-SPT
  Provider tunnel: I-P-tnl:LDP-P2MP:1.1.1.1, lsp-id 16777217

 

<snip>


Instance : CPE-1
  MVPN Mode : RPT-SPT
  Provider tunnel: I-P-tnl:LDP-P2MP:1.1.1.1, lsp-id 16777217

 

 

===================

PE2 (relative config is attached):

SomeLabGuy@PE-2> show mvpn neighbor
MVPN instance:

<snip legend>

Family : INET

Instance : CPE-2
  MVPN Mode : RPT-SPT

<snip>


Instance : CPE-2
  MVPN Mode : RPT-SPT

 


SomeLabGuy@PE-2> show mvpn instance
MVPN instance:

<snip legend>

Family : INET

Instance : CPE-2
  MVPN Mode : RPT-SPT
  Provider tunnel: I-P-tnl:LDP-P2MP:4.4.4.4, lsp-id 16777217

<snip>


Instance : CPE-2
  MVPN Mode : RPT-SPT
  Provider tunnel: I-P-tnl:LDP-P2MP:4.4.4.4, lsp-id 16777217

 

 

 

 

 

 

 

 

↧
Search

SNMP index dynamic subscriber

February 3, 2017, 12:00 pm
$
0
0

Hi,

 

I would like to monitor my dynamic subscribers via SNMP.

But every time the session reestablished the SNMP interface index get a new value.

 

Is there a way to set this static via RADIUS or retrieve the index via RADIUS in my accounting table ?

 

Or any other idea's ?

 

Thnx

 

 

Kind regards,

↧

Re: ospf area0 not connected

February 3, 2017, 4:31 pm
$
0
0

- Why are a019-a020 and b019-b020 links in area 1 and for which reasons should they remain that way (if there are any)?

                       ------------------------it is a trunk link, all vlans ip are in area1(a019-a020) or area2(b019-b020),so it is area1 or 2....

                                                      Can I add another vlan for area0 and enable it in this trunk ? so it can be in area1 and area 0(a019-a020)

                                                      

- What is the role of router1, router4, router5 and router6? Are they also part of ospf, if so of which area?

                      ---------------------------router1 and router4 are in area1 and 5.6 in area2,they are the ASBR.

                                                   

I have one question, in the current config, if a019-b019 is down, will router1/4 be able to reach router5/6.It seems it still can reach....

                                                     

↧
↧

Re: ospf area0 not connected

February 3, 2017, 6:58 pm
$
0
0

Ok. It seems I am not undertanding 100% the topology from that diagram, if you could add the details of interfaces and IP's a little more clearly I would appreciate it.

 

Another thing I am not understanding is, why don't you configure all the links between a019, a020, b019 and b020 in area 0. Router1/4 are in area1 and are not interconnected between each other directly or through more routers, and Router5/6 are in area2 and are not interconnected between each other directly or through more routers, so because of this there would be no issue doing that.

↧

Re: How to apply different bandwidth policers to different traffic arriving on the same logical interface

February 4, 2017, 1:05 am
$
0
0

Hi Aarriola,

 

Thank you so much for the input. i will test it and update.

 

 

lish

↧

Re: ospf area0 not connected

February 4, 2017, 5:34 pm
$
0
0

I hope it is clear now.

 

it has 2 seperated ospf area0   a019-b019 and a020-b020.

 

r1 and r4 are connect to area0 a019-b019 since it is vlan...

 

I wonder whether it has problem  and what it is.

 

sorry for the cofusion.

↧
Viewing all 8688 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>