Hi There, 

I currently have an issue where I am unable to route from inet.0 to a directly connected device that is in a routing instance

The device is reachable when sourcing from the routing-instance however I need to be able to access the device from inet.0.

The peer device address is 185.96.18.29 and is connected to ge-0/0/6.782 and BGP is established

What am I missing that is making it so that I can not reach the device from inet.0?

Interface

description "TEST";
vlan-id 782;
family inet {
    address 185.96.18.28/31;
}

Routing Instance

test {
instance-type virtual-router;
interface ge-0/0/1.301;
interface ge-0/0/1.302;
interface ge-0/0/6.782;
routing-options {
    interface-routes {
        rib-group inet rib-test-interface-routes-v4;
    }
    autonomous-system 65500;
}
protocols {
    bgp {
        traceoptions {
            file btswip_bgp.log size 20k;
            flag all;
        }
        group supplier {
            neighbor 147.152.22.133 {
                peer-as 65235;
            }
            neighbor 147.152.22.129 {
                peer-as 65233;
            }
        }
        group customers {
            neighbor 185.96.18.29 {
                peer-as 64565;
            }
        }
    }
}

Rib Group

    rib-test-interface-routes-v4 {
        import-rib [ BT_WSIP.inet.0 inet.0 ];
    }
}

Interface Route - is done via an apply-group

int-routes-test-v4 {
    routing-options {
        interface-routes {
            rib-group inet rib-test-interface-routes-v4;
        }
    }
}

interface-routes {
apply-groups [ int-route-legacy-voip int-routes-test-v4 ];
}

Route output

inet.0: 172 destinations, 228 routes (170 active, 0 holddown, 2 hidden)
+ = Active Route, - = Last Active, * = Both

185.96.18.28/31    *[Direct/0] 01:59:07
                    > via ge-0/0/6.782

test.inet.0: 9 destinations, 15 routes (9 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

185.96.18.28/31    *[Direct/0] 1w6d 21:59:36
                    > via ge-0/0/6.782

Hi 

I peer EBGP woth cisco router. Status of BGP stuck in Connect state 

Output of log is below

May 17 10:56:30.470657 task_timer_reset: reset BGP_4652.61.19.60.1_Connect
May 17 10:56:30.470666 task_timer_set_oneshot_latest: timer BGP_4652.61.19.60.1_Connect interval set to 1:04
May 17 10:56:34.464676 task_process_events_internal: connect ready for BGP_4652.61.19.61.1
May 17 10:56:34.464714 bgp_connect_complete: error connecting to 61.19.61.1 (External AS 4652): Unknown error: -880758492
May 17 10:56:34.464718 BGP peer 61.19.61.1 (External AS 4652) CLOSE: close socket 88
May 17 10:56:34.464720 task_close: close socket 88 task BGP_4652.61.19.61.1
May 17 10:56:34.464723 task_reset_socket: task BGP_4652.61.19.61.1 socket 88
May 17 10:56:34.464750 bgp_event: peer 61.19.61.1 (External AS 4652) old state Connect event OpenFail new state Idle
May 17 10:56:34.464900 bgp_event: peer 61.19.61.1 (External AS 4652) old state Idle event Start new state Connect
May 17 10:56:34.464906 bgp_connect_start: peer 61.19.61.1 (External AS 4652)
May 17 10:56:34.464909 bgp_event: peer 61.19.61.1 (External AS 4652) old state Connect event ConnectRetry new state Connect
May 17 10:56:34.464937 task_get_socket: domain AF_INET type SOCK_STREAM protocol 0 socket 88
May 17 10:56:34.464954 task_set_option_internal: task BGP_4652.61.19.61.1 socket 88 option RecvBuffer(0) value 16384
May 17 10:56:34.464963 task_set_option_internal: task BGP_4652.61.19.61.1 socket 88 option SendBuffer(1) value 16384
May 17 10:56:34.464966 task_set_socket: task BGP_4652.61.19.61.1 socket 88
May 17 10:56:34.464983 task_set_option_internal: task BGP_4652.61.19.61.1 socket 88 option NonBlocking(8) value 1
May 17 10:56:34.464992 task_set_option_internal: task BGP_4652.61.19.61.1 socket 88 option ReUsePort(38) value 1
May 17 10:56:34.465008 task_set_option_internal: task BGP_4652.61.19.61.1 socket 88 option PathMTUDiscovery(26) value 0
May 17 10:56:34.465018 task_set_option_internal: task BGP_4652.61.19.61.1 socket 88 option TOS(16) value 192
May 17 10:56:34.465028 task_set_option_internal: task BGP_4652.61.19.61.1 socket 88 option DontRoute(5) value 1
May 17 10:56:34.465037 task_set_option_internal: task BGP_4652.61.19.61.1 socket 88 option IifRestrict(36) value 1
May 17 10:56:34.465045 task_set_option_internal: task BGP_4652.61.19.61.1 socket 88 option TTL(15) value 1
May 17 10:56:34.465060 task_set_option_internal: task BGP_4652.61.19.61.1 socket 88 option TcpAggressiveTransmission(59) value 0
May 17 10:56:34.465157 task_timer_reset: reset BGP_4652.61.19.61.1_Connect
May 17 10:56:34.465166 task_timer_set_oneshot_latest: timer BGP_4652.61.19.61.1_Connect interval set to 1:04

What's wrong??

Hi guys,

I have a problem to import ospf routes in my specified init.0 tables.

I have two L3 vrf instances on my Juniper MX router an I must import two virtuell router from my neighboor network.

We have bgp an the neighboor network have ospf.

Thr routes from the vr-voip from my neighbour must go in the L3_VoIP.init.0 and the routes from th vr-router wifi must go in the L3_Aerohive.init.0

I became on my Juniper Interface two vlans from his virtuell routers and i must import them in the init.0 table of my vr-routers.

Today all routes going in the global init.0 table and one vr router can see the other vr-router.

Hi folks, 

Sometimes when I'm troubleshooting complex MPLS environments I have doubts with the outputs of these CLI commands:

1) show route table inet.3

        All routes learned through MPLS. 

        Only I can see PUSH actions.

2) show route table mpls.0

       I can see SWAP actions and metric always is 1.

Please could you clarify when use it?

Thanks in advance!

A customer of ours has requested we run BGP to them for redundancy.

We are providing them a /24 IP block.

They do not have an AS number.

They do not need to peer with any other ISP's.

I believe the best solution is to peer to them using a private AS number and then just send them a default route as thats all they need.

I am used to peering to public AS's both upstream and downstream, I have only used private AS for iBGP for family inet vpn.

My question is peering wtih type internal appropriate or do i need to setup two private AS's, one on my side and one on there side, and peer usign to external.

Hi All,

We have PPPoE subscribers served by MX and free radius and all is well for now. 

currently the redius returns ingres/egress filter and each subscriber ends up with individual filter with his own couters.  the filter just references bandwidth policer. so each subsciber is ending up with 50mbps bandwidth polcer.  if i have some customers that i want to share one bandwith policer, how can i go about this? lets say i have 5 subscribers and i want this guys to share the 50mb link instead of each having 50mb filter attached per PP0 interface. 

Hello. I’m facing a problem with a new routing instance on MX-5 router. BGP session won’t establish.

May 17 18:09:16.583791 BGP_SET_INTERFACE_FAILED: bgp_set_peer_if: BGP peer 172.10.0.2 (External AS 78313) interface not found. Leaving peer idled

May 17 18:12:04.071366 bgp_connect_complete: error connecting to 172.10.0.2 (External AS 78313): Socket is not connected

May 17 18:19:34.072282 bgp_connect_complete: error connecting to 172.10.0.2 (External AS 78313): Socket is not connected

May 17 18:20:40.690218 bgp_color_sync_start:1421: 172.10.0.2 (External AS 78313): Color sync start for nlri's:

May 17 18:20:47.111615 bgp_connect_timeout: BGP_78313.172.10.0.2_Connect

May 17 18:20:47.111710 bgp_connect_start: peer 172.10.0.2 (External AS 78313)

May 17 18:20:47.111765 bgp_event: peer 172.10.0.2 (External AS 78313) old state Active event ConnectRetry new state Connect

May 17 18:20:47.112951 task_get_socket: domain AF_INET type SOCK_STREAM protocol 0 socket 136

May 17 18:20:47.113006 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option RecvBuffer(0) value 16384

May 17 18:20:47.113042 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option SendBuffer(1) value 16384

May 17 18:20:47.113081 task_set_socket: task BGP_78313.172.10.0.2 socket 136

May 17 18:20:47.113140 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option NonBlocking(8) value 1

May 17 18:20:47.113177 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option ReUsePort(38) value 1

May 17 18:20:47.113213 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option PathMTUDiscovery(26) value 0

May 17 18:20:47.113292 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option RoutingTable(27) value 8

May 17 18:20:47.113331 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option TOS(16) value 192

May 17 18:20:47.113366 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option DontRoute(5) value 1

May 17 18:20:47.113399 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option IifRestrict(36) value 1

May 17 18:20:47.113433 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option TTL(15) value 1

May 17 18:20:47.113470 Eval BFD turn-on, currently off for peer 172.10.0.2 (External AS 78313)(flinstance AZURE (kern-id 8)

May 17 18:20:47.113506 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option TcpAggressiveTransmission(59) value 0

May 17 18:20:47.113540 task_set_option_internal: task BGP_78313.172.10.0.2 socket 136 option EnableTcpNoDelay(63) value 0

May 17 18:20:47.114323 task_timer_reset: reset BGP_78313.172.10.0.2_Connect

May 17 18:20:47.114379 task_timer_set_oneshot_latest: timer BGP_78313.172.10.0.2_Connect interval set to 2:28

Routing instance:

[CODE]

RI-2 {

instance-type virtual-router;

interface ge-1/1/0.435;

routing-options {

autonomous-system 54553;

}

protocols {

bgp {

group IPv4-AZURE {

type external;

traceoptions {

file bgplog size 10k files 10;

flag all;

}

import IPv4-FILTER-IN;

export IPv4-PEER-FILTER-OUT;

neighbor 172.10.0.2 {

peer-as 78313;

}

}

}

}

}

Interface ge-1/1/0

[CODE]

vlan-tagging;

unit 120 {

vlan-id 120;

family inet {

}

address 1.1.1.1/30;

}

unit 435 {

vlan-id 435;

family inet {

address 172.10.0.1/30;

}

}

I’m able to ping BGP neighbor via routing-instance.

[CODE]

ping 172.10.0.2 routing-instance RI-2

PING 172.10.0.2 (172.10.0.2): 56 data bytes

64 bytes from 172.10.0.2: icmp_seq=0 ttl=255 time=27.840 ms

64 bytes from 172.10.0.2: icmp_seq=1 ttl=255 time=27.870 ms

64 bytes from 172.10.0.2: icmp_seq=2 ttl=255 time=27.766 ms

64 bytes from 172.10.0.2: icmp_seq=3 ttl=255 time=27.817 ms

BGP neighbor status

[CODE]

> show bgp neighbor 172.10.0.2

Peer: 172.10.0.2+179 AS 12076 Local: 172.10.0.1+54833 AS 5453

Group: IPv4-RI2 Routing-Instance: RI-2

Forwarding routing-instance: RI-2

Type: External State: Connect Flags: <>

Last State: Active Last Event: ConnectRetry

Last Error: None

Export: [ IPv4-PEER-FILTER-OUT ] Import: [ IPv4-FILTER-IN ]

Options: <Multihop Preference AddressFamily PeerAS Refresh>

Address families configured: inet-unicast

Holdtime: 90 Preference: 170

Number of flaps: 0

Trace options: detail open

Trace file: /var/log/bgplog size 0 files 1

I am looking for the maximum number of routes an MX480 can have in its route table?  I am supporting a client with an MX480 that has just over 1.5mill BGP routes in its table.  We lost one of its primary DIA links which provides a full internet routing table plus some vrfs for VPLS.  When the link flapped and protocols subsequently attempted to re-converge we received the following log message, with latency across the upstream network for a few minutes.

kernel: rt_pfe_veto: Memory usage of M_RTNEXTHOP type = (0) Max size possible for  M_RTNEXTHOP type = (16704245760) Current delayed unref = (40000) Max delayed unref on this platform = (40000) Current delayed weight unref = (40000) Max delayed weight unref on this platform= (400000) curproc = rpd

https://www.juniper.net/documentation/en_US/junos/topics/example/vpn-layer2-configuring.html

According to above link, for configuring Kompella draft of l2vpn  it is said to configure vrf-export, vrf-import policy(Mandatory). My question is why it is necessary to configure export import policy ? Why not  go for export target:2000:59856 format for exporting  routes ?

Hello friends,

I am trying to test a custom scenario in VPLS, but my setup is being stuck in 'OL' state {no outgoing label}. Following is the topology and configs and related show outputs. Can someone point out where I am going wrong?

Topology (please refer attached file for topo diagram if below topo diagram is jumbled up):
---------
=> Please note: P3 is a logical router running on PE2.
=> Not posting configs of P1, P2 and P4 as they are simple generic core routers (verified IGP connectivity between all PEs and Ps)

CE1---PE1----P1---P2------P3--------PE2---CE2
| | | (LR on PE2)
| | |
------P4------
|
PE3---CE3

Configs:
-------
PE1:
set interfaces ge-0/0/0 unit 0 family inet address 10.30.0.1/24
set interfaces ge-0/0/0 unit 0 family iso
set interfaces ge-0/0/0 unit 0 family inet6
set interfaces ge-0/0/0 unit 0 family mpls
set interfaces ge-0/0/1 unit 0 family inet address 10.20.0.1/24
set interfaces ge-0/0/1 unit 0 family iso
set interfaces ge-0/0/1 unit 0 family inet6
set interfaces ge-0/0/1 unit 0 family mpls
set interfaces ge-0/0/2 encapsulation ethernet-vpls
set interfaces ge-0/0/2 unit 0
set routing-instances vpls-red instance-type vpls
set routing-instances vpls-red protocols vpls traceoptions file vplstraces_PE1.txt
set routing-instances vpls-red protocols vpls traceoptions file size 40m
set routing-instances vpls-red protocols vpls traceoptions file world-readable
set routing-instances vpls-red protocols vpls traceoptions flag all detail
set routing-instances vpls-red protocols vpls vpls-id 1
set routing-instances vpls-red protocols vpls neighbor 10.255.144.228
set routing-instances vpls-red protocols vpls neighbor 10.255.144.89
set routing-instances vpls-red interface ge-0/0/2.0
set routing-options route-distinguisher-id 10.255.144.93
set routing-options router-id 10.255.144.93
set routing-options autonomous-system 100
set protocols ospf traffic-engineering
set protocols ospf area 0.0.0.0 interface all
set protocols ospf area 0.0.0.0 interface fxp0.0 disable
set protocols ospf area 0.0.0.0 interface ge-0/0/6.0 metric 10000
set protocols rsvp interface all link-protection
set protocols rsvp interface fxp0.0 disable
set protocols mpls label-switched-path r0-r5 to 192.168.255.205
set protocols mpls label-switched-path r0-r5 ldp-tunneling
set protocols mpls label-switched-path r0-r5 link-protection
set protocols mpls label-switched-path r0-r5 primary use-IF1
set protocols mpls label-switched-path r0-r8 to 10.255.144.89
set protocols mpls label-switched-path r0-r8 ldp-tunneling
set protocols mpls path use-IF1 10.20.0.2 strict
set protocols mpls path use-IF3 10.30.0.2 strict
set protocols mpls interface all
set protocols mpls interface fxp0.0 disable

PE2:
set logical-systems R5 interfaces ge-0/0/0 unit 0 family inet address 10.14.0.1/24
set logical-systems R5 interfaces ge-0/0/0 unit 0 family iso
set logical-systems R5 interfaces ge-0/0/0 unit 0 family inet6
set logical-systems R5 interfaces ge-0/0/0 unit 0 family mpls
set logical-systems R5 interfaces lo0 unit 105 description "R5 LR Loopback"
set logical-systems R5 interfaces lo0 unit 105 family inet address 192.168.255.205/32
set logical-systems R5 protocols ospf traffic-engineering
set logical-systems R5 protocols ospf area 0.0.0.0 interface all
set logical-systems R5 protocols ospf area 0.0.0.0 interface fxp0.0 disable
set logical-systems R5 protocols rsvp interface all
set logical-systems R5 protocols ldp interface ge-0/0/0.0
set logical-systems R5 protocols ldp interface fxp0.0 disable
set logical-systems R5 protocols ldp interface lo0.105
set logical-systems R5 protocols mpls label-switched-path r5-r0 to 10.255.144.93
set logical-systems R5 protocols mpls label-switched-path r5-r0 ldp-tunneling
set logical-systems R5 protocols mpls label-switched-path r5-r8 to 10.255.144.89
set logical-systems R5 protocols mpls label-switched-path r5-r8 ldp-tunneling
set logical-systems R5 protocols mpls interface all
set logical-systems R5 protocols ospf3 area 0.0.0.0 interface all
set logical-systems R5 protocols ospf3 area 0.0.0.0 interface fxp0.0 disable
set chassis network-services enhanced-ip
set interfaces ge-0/0/1 description "Default LR R1 to R7 LR on unit 2"
set interfaces ge-0/0/1 encapsulation ethernet-vpls
set interfaces ge-0/0/1 unit 0
set routing-instances vpls-red instance-type vpls
set routing-instances vpls-red protocols vpls traceoptions file vplstraces_PE2.txt
set routing-instances vpls-red protocols vpls traceoptions file size 40m
set routing-instances vpls-red protocols vpls traceoptions file world-readable
set routing-instances vpls-red protocols vpls traceoptions flag all detail
set routing-instances vpls-red protocols vpls vpls-id 1
set routing-instances vpls-red protocols vpls neighbor 10.255.144.93
set routing-instances vpls-red protocols vpls neighbor 10.255.144.89
set routing-instances vpls-red interface ge-0/0/1.0
set routing-options route-distinguisher-id 10.255.144.228
set routing-options router-id 10.255.144.228
set routing-options autonomous-system 100
set protocols ospf traffic-engineering
set protocols ospf area 0.0.0.0 interface all
set protocols ospf area 0.0.0.0 interface fxp0.0 disable
set protocols mpls interface all
set protocols mpls interface fxp0.0 disable

PE3:
set chassis network-services enhanced-ip
set interfaces ge-0/0/0 unit 0 family inet address 10.38.0.8/24
set interfaces ge-0/0/0 unit 0 family iso
set interfaces ge-0/0/0 unit 0 family mpls
set interfaces ge-0/0/1 description "Default LR R8 to R9 LR on unit 2"
set interfaces ge-0/0/1 encapsulation ethernet-vpls
set interfaces ge-0/0/1 unit 0
set routing-instances vpls-red instance-type vpls
set routing-instances vpls-red protocols vpls traceoptions file vplstraces_PE3.txt
set routing-instances vpls-red protocols vpls traceoptions file size 40m
set routing-instances vpls-red protocols vpls traceoptions file world-readable
set routing-instances vpls-red protocols vpls traceoptions flag all detail
set routing-instances vpls-red protocols vpls vpls-id 1
set routing-instances vpls-red protocols vpls neighbor 10.255.144.93
set routing-instances vpls-red protocols vpls neighbor 10.255.144.228
set routing-instances vpls-red interface ge-0/0/1.0
set routing-options route-distinguisher-id 10.255.144.89
set routing-options router-id 10.255.144.89
set routing-options autonomous-system 100
set protocols ospf traffic-engineering
set protocols ospf area 0.0.0.0 interface all
set protocols ospf area 0.0.0.0 interface fxp0.0 disable
set protocols rsvp interface all
set protocols rsvp interface fxp0.0 disable
set protocols mpls label-switched-path r8-r0 to 10.255.144.93
set protocols mpls label-switched-path r8-r0 ldp-tunneling
set protocols mpls label-switched-path r8-r5 to 192.168.255.205
set protocols mpls label-switched-path r8-r5 ldp-tunneling
set protocols mpls interface all
set protocols mpls interface fxp0.0 disable

Outputs:
---------
PE1:
regress@PE1_re> show vpls connections
<...truncated...>
Instance: vpls-red
VPLS-id: 1
Neighbor Type St Time last up # Up trans
10.255.144.228(vpls-id 1) rmt OL
10.255.144.89(vpls-id 1) rmt OL

regress@PE1_re> show rsvp session
Ingress RSVP: 3 sessions
To From State Rt Style Labelin Labelout LSPname
10.255.144.89 10.255.144.93 Dn 0 0 - - - r0-r8
128.220.12.37 10.255.144.93 Up 0 1 SE - 299792 Bypass->10.20.0.2
192.168.255.205 10.255.144.93 Up 0 1 SE - 299776 r0-r5
Total 3 displayed, Up 2, Down 1

Egress RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

Transit RSVP: 2 sessions
To From State Rt Style Labelin Labelout LSPname
10.255.144.93 192.168.255.205 Dn 0 0 - - - r5-r0
10.255.144.93 10.255.144.89 Dn 0 0 - - - r8-r0
Total 2 displayed, Up 0, Down 2

regress@PE1_re> show route protocol ospf

inet.0: 51 destinations, 51 routes (50 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both

10.14.0.0/24 *[OSPF/10] 03:12:18, metric 3
> to 10.30.0.2 via ge-0/0/0.0
to 10.20.0.2 via ge-0/0/1.0
10.23.0.0/24 *[OSPF/10] 03:12:18, metric 2
to 10.30.0.2 via ge-0/0/0.0
> to 10.20.0.2 via ge-0/0/1.0
10.24.0.0/24 *[OSPF/10] 03:12:18, metric 2
> to 10.20.0.2 via ge-0/0/1.0
10.34.0.0/24 *[OSPF/10] 03:13:02, metric 2
> to 10.30.0.2 via ge-0/0/0.0
10.38.0.0/24 *[OSPF/10] 03:13:02, metric 2
> to 10.30.0.2 via ge-0/0/0.0
128.220.12.23/32 *[OSPF/10] 03:12:18, metric 2
> to 10.30.0.2 via ge-0/0/0.0
to 10.20.0.2 via ge-0/0/1.0
128.220.12.37/32 *[OSPF/10] 03:12:18, metric 1
> to 10.20.0.2 via ge-0/0/1.0
128.220.12.77/32 *[OSPF/10] 03:13:02, metric 2
> to 10.30.0.2 via ge-0/0/0.0
128.220.12.195/32 *[OSPF/10] 03:13:02, metric 1
> to 10.30.0.2 via ge-0/0/0.0
192.168.255.205/32 *[OSPF/10] 03:12:18, metric 3
to 10.30.0.2 via ge-0/0/0.0
> to 10.20.0.2 via ge-0/0/1.0
224.0.0.5/32 *[OSPF/10] 03:15:29, metric 1
MultiRecv

inet.3: 1 destinations, 2 routes (1 active, 0 holddown, 1 hidden)

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

mpls.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)

PE2:
regress@PE2_re> show vpls connections
<...truncated...>
Instance: vpls-red
VPLS-id: 1
Neighbor Type St Time last up # Up trans
10.255.144.89(vpls-id 1) rmt OL
10.255.144.93(vpls-id 1) rmt OL

regress@PE2_re> show rsvp session logical-system R5
Ingress RSVP: 2 sessions
To From State Rt Style Labelin Labelout LSPname
10.255.144.89 192.168.255.205 Dn 0 0 - - - r5-r8
10.255.144.93 192.168.255.205 Dn 0 0 - - - r5-r0
Total 2 displayed, Up 0, Down 2

Egress RSVP: 2 sessions
To From State Rt Style Labelin Labelout LSPname
192.168.255.205 10.255.144.89 Up 0 1 FF 3 - r8-r5
192.168.255.205 10.255.144.93 Up 0 1 SE 3 - r0-r5
Total 2 displayed, Up 2, Down 0

Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

regress@PE2_re> show route protocol ospf

inet.0: 36 destinations, 36 routes (36 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

224.0.0.5/32 *[OSPF/10] 03:24:43, metric 1
MultiRecv

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

mpls.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)

l2circuit.0: 2 destinations, 2 routes (0 active, 0 holddown, 2 hidden)

PE3:
regress@PE3_re> show vpls connections
<...truncated...>
Instance: vpls-red
VPLS-id: 1
Neighbor Type St Time last up # Up trans
10.255.144.228(vpls-id 1) rmt OL
10.255.144.93(vpls-id 1) rmt OL

regress@PE3_re> show rsvp session
Ingress RSVP: 2 sessions
To From State Rt Style Labelin Labelout LSPname
10.255.144.93 10.255.144.89 Dn 0 0 - - - r8-r0
192.168.255.205 10.255.144.89 Up 0 1 FF - 299776 r8-r5
Total 2 displayed, Up 1, Down 1

Egress RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0

Transit RSVP: 2 sessions
To From State Rt Style Labelin Labelout LSPname
10.255.144.89 10.255.144.93 Dn 0 0 - - - r0-r8
10.255.144.89 192.168.255.205 Dn 0 0 - - - r5-r8
Total 2 displayed, Up 0, Down 2

regress@PE3_re> show route protocol ospf

inet.0: 49 destinations, 49 routes (49 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.14.0.0/24 *[OSPF/10] 03:16:01, metric 3
> to 10.38.0.3 via ge-0/0/0.0
10.20.0.0/24 *[OSPF/10] 03:14:10, metric 3
> to 10.38.0.3 via ge-0/0/0.0
10.23.0.0/24 *[OSPF/10] 03:16:01, metric 2
> to 10.38.0.3 via ge-0/0/0.0
10.24.0.0/24 *[OSPF/10] 03:16:01, metric 3
> to 10.38.0.3 via ge-0/0/0.0
10.30.0.0/24 *[OSPF/10] 03:13:06, metric 4
> to 10.38.0.3 via ge-0/0/0.0
10.34.0.0/24 *[OSPF/10] 03:16:01, metric 2
> to 10.38.0.3 via ge-0/0/0.0
128.220.12.23/32 *[OSPF/10] 03:16:01, metric 2
> to 10.38.0.3 via ge-0/0/0.0
128.220.12.37/32 *[OSPF/10] 03:14:10, metric 2
> to 10.38.0.3 via ge-0/0/0.0
128.220.12.195/32 *[OSPF/10] 03:16:01, metric 1
> to 10.38.0.3 via ge-0/0/0.0
128.220.14.157/32 *[OSPF/10] 03:13:06, metric 3
> to 10.38.0.3 via ge-0/0/0.0
192.168.255.205/32 *[OSPF/10] 03:16:01, metric 3
> to 10.38.0.3 via ge-0/0/0.0
224.0.0.5/32 *[OSPF/10] 03:18:01, metric 1
MultiRecv

inet.3: 1 destinations, 2 routes (1 active, 0 holddown, 1 hidden)

iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

mpls.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)

Model: acx5448

Junos: 19.1R1.6

We have just started rolling ACX5448's and have about 10 of them deployes without issue if they are simple LSR's, however as soon as we add l2circuits or any services to the box, they crash after 20-40hrs. Not sure what the trigger is but the aggregated bandwidth going through the box is 6-10gbps . Logs of when it crashes below, died at around 22:10 on the last occasion. We have had to roll back to ACX5048 where we have services present.

May 22 22:08:57  nzwlg-wn-ax-1 fpc0 DNX PKT: (buf alloc) failed allocating packet buffer

May 22 22:09:01  nzwlg-wn-ax-1 last message repeated 5 times

May 22 22:10:55  nzwlg-wn-ax-1 last message repeated 3496 times

May 22 22:10:55  nzwlg-wn-ax-1 fpc0 ACX_PFE_ERROR_NULL_ARG: pfe_dnx_egr_label_ifl_map_del: egress label(262147) -> ifl mapping doesn't exist.

May 22 22:10:55  nzwlg-wn-ax-1 fpc0 DNX PKT: (buf alloc) failed allocating packet buffer

May 22 22:11:03  nzwlg-wn-ax-1 last message repeated 171 times

May 22 22:11:37  nzwlg-wn-ax-1 last message repeated 674 times

May 22 22:11:37  nzwlg-wn-ax-1 xntpd: sendto(x.x.x.x): No route to host

May 22 22:11:37  nzwlg-wn-ax-1 fpc0 DNX PKT: (buf alloc) failed allocating packet buffer

May 22 22:12:03  nzwlg-wn-ax-1 last message repeated 519 times

May 22 22:12:40  nzwlg-wn-ax-1 last message repeated 732 times

May 22 22:12:39  nzwlg-wn-ax-1 xntpd: sendto(x.x.x.x): No route to host

Hi,

Could somebody please post output of the following commands:

- show chassis hardware

- show interfaces terse

and all PICs details if possible...?

Thanks,

Does Graceful Routing Engine Switchover (GRES) + Nonstop Active Routing (NSR) support Routing-Instances, and more in particular, the user-defined virtual-router routing instance type? It seems logical to me that it is supported but I want tot know it for sure.

Just to make it more clear what I mean:

GRES: [edit chassis redundancy] graceful-switchover;

NSR: [edit routing-options] nonstop-routing;

user-defined virtual-router routing instance type: [edit routing-instances just-a-name] instance-type virtual-router;

With regards,

Jean

Based on below BGP export policy "bgp-redistrib-ospf " , I have two questions

1, Will this policy accept route 10.61.11.17/24 and re-distribute into BGP ?

2. Will it re-distribute OSPF routes into BGP ?

Thanks in advance

policy-statement bgp-redistrib-ospf {
        term ospf-connected-advs {
            from {
                route-filter 10.61.0.0/20 longer accept;
                route-filter 10.80.0.0/21 exact accept;
                route-filter 10.135.0.0/16 longer accept;
                route-filter 0.0.0.0/0 exact;
  route-filter 10.61.11.0/24 exact accept;
                route-filter 172.30.2.192/26 longer accept;
                route-filter 10.148.14.0/23 orlonger reject;
                route-filter 10.148.114.0/23 orlonger reject;
                route-filter 10.61.16.0/21 exact accept;
                route-filter 10.86.0.0/23 exact accept;
                route-filter 10.138.0.0/23 exact accept;
                route-filter 10.64.16.0/23 exact accept;
                route-filter 10.148.4.0/23 exact accept;
                route-filter 10.148.104.0/23 exact accept;
                route-filter 10.0.0.0/8 orlonger reject;
            }
            then next term;
        }
        term from-bgp {
            from protocol bgp;
            then next policy;
        }
        term connected {
            from {
                protocol direct;
                interface [ lo0.0 ge-0/0/0.0 ];
            }
            then accept;
        }

protocols {
    bgp {
        path-selection cisco-non-deterministic;
        log-updown;
        export bgp-redistrib-ospf;
        group jweb-bgp {               
            type external;
            metric-out 0;
            local-address X.X.X.X;
            peer-as 209;
            neighbor X.X.X.X {
                metric-out 0;

    ospf {
        export ospf-redistributes;
        area 0.0.0.0 {
            interface lo0.0;
            interface ge-0/0/0.0;
        }

policy-statement ospf-redistributes {
        term bgp {
            from protocol bgp;
            then accept;
        }
        term from-ospf {
            from protocol ospf;
            then next policy;
        }
        term connected {
            from protocol direct;
            then accept;
        }

Hi 

I got an issue.

Many indirect routes are stuck in my VRF and casue my VRF's routing table have more 800,000 routes. But I've rejected these routes leaking from main table.

Can you give me some information how to reject it ?

> show route summary  table IRENE_R1_CU.inet.0
Autonomous system number: 64050
Router ID: 10.98.146.43

IRENE_R1_CU.inet.0: 830731 destinations, 856339 routes (11838 active, 818893 holddown, 6 hidden)
Direct: 16 routes, 14 active
Local: 14 routes, 5 active
BGP: 856299 routes, 11811 active
Static: 10 routes, 8 active

> show route logical-system CHINA table IRENE_R1_CU.inet.0 protocol bgp

IRENE_R1_CU.inet.0: 830731 destinations, 856339 routes (11838 active, 818893 holddown, 6 hidden)
+ = Active Route, - = Last Active, * = Both

1.0.0.0/24 [BGP/170] 3d 04:09:13, localpref 100
AS path: 13335 I, validation-state: unverified
Indirect
1.0.4.0/22 [BGP/170] 3d 04:08:17, localpref 100
AS path: 4826 38803 56203 I, validation-state: unverified
Indirect
1.0.4.0/24 [BGP/170] 01:23:04, localpref 100, from10.98.146.42
AS path: 4826 38803 56203 I, validation-state: unverified
Indirect
1.0.5.0/24 [BGP/170] 01:23:04, localpref 100, from 10.98.146.42
AS path: 4826 38803 56203 I, validation-state: unverified
Indirect

<Omited>

1.0.4.0/22 (1 entry, 1 announced)
State: <Record Pending>
BGP Preference: 170/-101
Next hop type: Indirect, Next hop index: 0
Address: 0xb236e10
Next-hop reference count: 189538
Next hop type: Router, Next hop index: 0
Next hop: 10.98.146.65 via lt-1/2/0.1, selected
Label operation: Push 606450
Label TTL action: prop-ttl
Load balance label: Label 606450: None;
Label element ptr: 0x6e514e40
Label parent element ptr: 0x0
Label element references: 5
Label element child references: 1
Label element lsp id: 0
Session Id: 0x0
Next hop: 10.98.146.69 via lt-2/2/0.1
Label operation: Push 606450
Label TTL action: prop-ttl
Load balance label: Label 606450: None;
Label element ptr: 0x6e514e40
Label parent element ptr: 0x0
Label element references: 5
Label element child references: 1
Label element lsp id: 0
Session Id: 0x0
Protocol next hop: 10.98.146.49
Indirect next hop: 0x25932230 1048600 INH Session ID: 0x60e69
State: <Secondary Delete Int Ext>
Local AS: 64050 Peer AS: 64050
Age: 3d 4:09:31 Metric2: 3
Validation State: unverified
Announcement bits (1): 2-RT
AS path: 4826 38803 56203 I (Originator)
Cluster list: 10.98.144.48 10.98.144.46 10.98.147.44 10.98.146.42 10.98.146.45
Originator ID: 10.98.146.49
Communities: 13000:420
Localpref: 100

Hello,

I have the following topology:

S1  (ge-0/0/2) ---- (ge-0/0/1) R3

S1 (ge-0/0/3) ---- (ge-0/0/1) R4

COnfiguration on S1 is:

interfaces {
ge-0/0/2 {
ether-options {
802.3ad ae0;
}
}
ge-0/0/3 {
ether-options {
802.3ad ae0;
}
}
ae0 {
flexible-vlan-tagging;
encapsulation extended-vlan-bridge;
aggregated-ether-options {
lacp {
active;
periodic fast;
}
}
unit 10 {
vlan-id 10;
}
unit 11 {
vlan-id 11;
}
}
irb {
unit 10 {
family inet {
address 17.8.10.10/24;
}
}
unit 11 {
family inet {
address 17.8.11.11/24;
}
}
}
}
protocols {
lldp {
interface all;
}
}
vlans {
MGM {
vlan-id 10;
interface ae0.10;
l3-interface irb.10;
}
MGM2 {
vlan-id 11;
interface ae0.11;
l3-interface irb.11;
}
}

On R3 is:

interfaces {
ge-0/0/1 {
gigether-options {
802.3ad {
lacp {
port-priority 100;
}
ae100;
}
}
}
ge-0/0/4 {
unit 0 {
family inet {
address 17.8.0.4/24;
}
}
}
ae100 {
flexible-vlan-tagging;
aggregated-ether-options {
lacp {
active;
system-id 00:00:00:00:00:01;
admin-key 100;
}
mc-ae {
mc-ae-id 100;
redundancy-group 100;
chassis-id 0;
mode active-standby;
status-control active;
}
}
}
}
protocols {
iccp {
local-ip-addr 17.8.0.4;
peer 17.8.0.3 {
redundancy-group-id-list [ 10 11 100 ];
liveness-detection {
minimum-interval 8000;
multiplier 3;
}
}
}
lldp {
interface all;
}
}
switch-options {
service-id 1;
}

On R4 is:

interfaces {
ge-0/0/1 {
gigether-options {
802.3ad {
lacp {
port-priority 200;
}
ae100;
}
}
}
ge-0/0/3 {
unit 0 {
family inet {
address 17.8.0.3/24;
}
}
}
ae100 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
aggregated-ether-options {
lacp {
active;
periodic fast;
system-id 00:00:00:00:00:01;
admin-key 100;
}
mc-ae {
mc-ae-id 100;
redundancy-group 100;
chassis-id 1;
mode active-standby;
status-control standby;
}
}
}
}
protocols {
iccp {
local-ip-addr 17.8.0.3;
peer 17.8.0.4 {
redundancy-group-id-list [ 10 11 100 ];
liveness-detection {
minimum-interval 8000;
multiplier 3;
}
}
}
lldp {
interface all;
}
}
switch-options {
service-id 1;
}

ICCP between R3 and R4 is UP:

root@R4# run show iccp

Redundancy Group Information for peer 17.8.0.4
TCP Connection : Established
Liveliness Detection : Up
Redundancy Group ID Status
10 Up
11 Up
100 Up

Client Application: l2ald_iccpd_client
Redundancy Group IDs Joined: None

Client Application: lacpd
Redundancy Group IDs Joined: None

[edit]
root@R3# run show iccp

Redundancy Group Information for peer 17.8.0.3
TCP Connection : Established
Liveliness Detection : Up
Redundancy Group ID Status
10 Up
11 Up
100 Up

Client Application: l2ald_iccpd_client
Redundancy Group IDs Joined: None

Client Application: lacpd
Redundancy Group IDs Joined: None

#show lacp interfaces and #show interfaces mc-ae are returning blank results on all devices, please help me understand what is wrong.

Regards,

Alexandru Minzat

Afternoon - JNCIE hopeful here

I have been preparing for some time now but have heard some distrubing rumors that there are significant differences between CoS configuration in current versions of Junos and the version used in the Lab (12.3). I am using vMXs on 15.1 (oldest available) in my lab presently and am hoping that this is an adequate representation of software in the lab.

Is this correct? If there are differences, can you suggest a version or platform that uses the same syntax as 12.3? such as vSRX at x version, etc.

thank you!

Hello!

Could someone explain the meaming of ISIS SFP timers?

According to the documentation there are three SFP options. I understand the delay and the holddown timers, but what is the rupid runs in terms of time? What is the maximum interval in miliseconds between SFP rapid runs until the holddown timer starts? is it zero? 

 coulde you please explained the behvoir of composite next hop by expamples and what is diffrent between composite next -hop and default behvoir next hop , and why it is recommend to used it in l2vpn ?