I was thinking of getting into Juniper and going down the cert route. There seem to be plenty of video series and materials about for JNCIA but this doesn't appear to be the case for JNCIS.

All I can find is a Sybex book which seems to cover an older exam JN0-303. Literally cannot find anything else on Amazon. Boson doesn't seem to cover this.

On the Juniper website there are options for on demand courses which are not cheap at all. I saw someone else mention a few Oreily books JUNOS Enterprise Routing and another book for Switching.

Just out of curiosity how have others who have passed this prepared?

Is this something Juniper are looking to address in the near future?

Thanks

Ive read the old study guides (JN0-332) and currently taking the recommended course for JN0-333.

Has anyone taken the exam recently and could give me some insight on, e.g what topics they ask a lot of questions on, any “trick questions” and so on.

Thanks!

Could someone please share this with me?

Fast Track no longer exists AFAIK?

Besides CBT nuggets anyone know where i can get good study guides for the JNCIS-ENT exam? I do have the Enterprise Routing 2nd edition book, maybe if i also get the Enterprise Switching book that would be good enough? Was hoping for something a bit more condensed like CBT nuggets.

My MPLS post the other week was pretty well received so I figured might as well show the other side of the coin and do it again with Juniper boxes.

#Topology

Today's Topology is similar to last time but Juniperified, we have:

• 4 x PE routers that are vMX
• 4 x P are vSRX
• 4 x CE routers are VSRX boxes as well.

There are again two customers, CUST-A and CUST-B because originality is hard.

To save on some config space I'll just focus on a single router at a time unless there is differences that are worth seeing.

#Provider Routers

###Disable Flow Mode

I'm using SRX routers for my core so we need to disable the default flow based mode and reboot the boxes before we can use them with MPLS.

root@P01# set security forwarding-options family inet6 mode packet-based 

[edit]
root@P01# set security forwarding-options family mpls mode packet-based 

[edit]
root@P01# set security forwarding-options family iso mode packet-based 

root@P01# commit 
commit complete

[edit]

root@P01# run request system reboot 
Reboot the system ? [yes,no] (no) yes

Once this is done we will no longer need to use security zones for everything.

###Basic Setup

To keep things clean I'm using a virtual-router instance to move the first interface into another routing table for management.

set routing-instances MGMT instance-type virtual-router
set routing-instances MGMT interface ge-0/0/0.0
set routing-instances MGMT routing-options static route 0.0.0.0/0 next-hop 10.20.2.1
set interfaces ge-0/0/0 unit 0 family inet address 10.20.2.211/24

Most of my interfaces are connecting to trunk ports to make life easier so I'm going to enable vlan tagging and use subinterfaces to connect to everything.

set interfaces ge-0/0/1 vlan-tagging
set interfaces ge-0/0/1 unit 3011 vlan-id 3011
set interfaces ge-0/0/1 unit 3011 family inet address 10.1.11.1/24
set interfaces ge-0/0/1 unit 3012 vlan-id 3012
set interfaces ge-0/0/1 unit 3012 family inet address 10.1.2.1/24
set interfaces ge-0/0/1 unit 3013 vlan-id 3013
set interfaces ge-0/0/1 unit 3013 family inet address 10.1.3.1/24
set interfaces ge-0/0/1 unit 3014 vlan-id 3014
set interfaces ge-0/0/1 unit 3014 family inet address 10.1.4.1/24
set interfaces lo0 unit 0 family inet address 192.168.255.1/32

Then I'll just turn on OSPF on all active interfaces in the routing instance.

root@P01# set protocols ospf area 0.0.0.0 interface all 

Once we are done we should see a neighbor with every other P router and a PE router (once we get that far)

root@P01# run show ospf neighbor 
Address          Interface              State     ID               Pri  Dead
10.1.11.254      ge-0/0/1.3011          Full      192.168.255.11   128    39
10.1.2.2         ge-0/0/1.3012          Full      192.168.255.2    128    32
10.1.3.3         ge-0/0/1.3013          Full      192.168.255.3    128    39
10.1.4.4         ge-0/0/1.3014          Full      192.168.255.4    128    34

###Enabling MPLS

While Cisco put effort into making sure MPLS is turned on right away, Juniper takes a bit more effort.

First we need to enable MPLS and LDP in the control plane under protocols, we can conveniently use the interface all keyword to enable it on all interfaces.

root@P01# set protocols mpls interface all 

root@P01# set protocols ldp interface all   

Next we need to turn it on for the forwarding plane by adding the mpls family to each interface on the router that will be in the MPLS path. This can be a bit annoying so you might want to look into things like config groups to ease the admin burden.

set interfaces ge-0/0/1 unit 3011 family mpls

set interfaces ge-0/0/1 unit 3012 family mpls

set interfaces ge-0/0/1 unit 3013 family mpls

set interfaces ge-0/0/1 unit 3014 family mpls

set interfaces lo0 unit 0 family mpls

#Route Reflector

We'll use a route reflector again but this time I'm just take advantage of the logical-system feature to carve PE01 and PE02 into two new Route Reflector boxes.

###RR01

First we'll turn on vlan-tagging for the interface I want to use since we still need to configure physical stuff at the interface level in logical-systems.

root@PE11# set interfaces ge-0/0/2 vlan-tagging 

Next we configure the interfaces like above under the logical-system.

root@PE11# set logical-systems RR01 interfaces ge-0/0/2 unit 3123 vlan-id 3123 
root@PE11# set logical-systems RR01 interfaces ge-0/0/2 unit 3123 family inet address 10.0.123.254/24 
root@PE11# set logical-systems RR01 interfaces ge-0/0/2 unit 3123 family mpls 
root@PE11# set logical-systems RR01 interfaces lo0 unit 1 family inet address 192.168.255.154/32 

root@PE11# set logical-systems RR01 protocols ospf area 0.0.0.0 interface all 
root@PE11# set logical-systems RR01 protocols mpls interface all 
root@PE11# set logical-systems RR01 protocols ldp interface all 

BGP is configured with the inet-vpn family which is the same as Cisco's VPNv4 family, the route reflector will have all for PEs as a peer, will use 65123 as the AS for iBGP and will set a cluster-id so Juniper knows it is a Route Reflector.

root@PE11# set logical-systems RR01 protocols bgp group PE-INTERNAL type internal 
root@PE11# set logical-systems RR01 protocols bgp group PE-INTERNAL local-address 192.168.255.154 
root@PE11# set logical-systems RR01 protocols bgp group PE-INTERNAL family inet-vpn unicast 
root@PE11# set logical-systems RR01 protocols bgp group PE-INTERNAL cluster 192.168.255.254 
root@PE11# set logical-systems RR01 protocols bgp group PE-INTERNAL neighbor 192.168.255.11 
root@PE11# set logical-systems RR01 protocols bgp group PE-INTERNAL neighbor 192.168.255.22 
root@PE11# set logical-systems RR01 protocols bgp group PE-INTERNAL neighbor 192.168.255.33 
root@PE11# set logical-systems RR01 protocols bgp group PE-INTERNAL neighbor 192.168.255.44 
root@PE11# set logical-systems RR01 routing-options autonomous-system 65123 

###RR02

root@PE22# set logical-systems RR02 interfaces ge-0/0/2 unit 3123 vlan-id 3123 
root@PE22# set logical-systems RR02 interfaces ge-0/0/2 unit 3123 family inet address 10.1.123.254/24 
root@PE22# set logical-systems RR02 interfaces ge-0/0/2 unit 3123 family mpls 
root@PE22# set logical-systems RR02 interfaces lo0 unit 1 family inet address 192.168.255.254/32 
root@PE22# set logical-systems RR02 protocols bgp group PE-INTERNAL type internal 
root@PE22# set logical-systems RR02 protocols bgp group PE-INTERNAL local-address 192.168.255.254 
root@PE22# set logical-systems RR02 protocols bgp group PE-INTERNAL family inet-vpn unicast 
root@PE22# set logical-systems RR02 protocols bgp group PE-INTERNAL cluster 192.168.255.254 
root@PE22# set logical-systems RR02 protocols bgp group PE-INTERNAL neighbor 192.168.255.11 
root@PE22# set logical-systems RR02 protocols bgp group PE-INTERNAL neighbor 192.168.255.22 
root@PE22# set logical-systems RR02 protocols bgp group PE-INTERNAL neighbor 192.168.255.33 
root@PE22# set logical-systems RR02 protocols bgp group PE-INTERNAL neighbor 192.168.255.44 
root@PE22# set logical-systems RR02 protocols ospf area 0.0.0.0 interface all 
root@PE22# set logical-systems RR02 protocols mpls interface all 
root@PE22# set logical-systems RR02 protocols ldp interface all 
root@PE22# set logical-systems RR02 routing-options autonomous-system 65123 

#Provider Edge

The PE will be similar to the Route-Reflector minus the logical system stuff, we'll setup the interfaces enable OSPF and MPLS, then peer with each of the RRs.

root@PE11# set routing-instances MGMT instance-type virtual-router 
root@PE11# set routing-instances MGMT interface ge-0/0/0.0 
root@PE11# set routing-instances MGMT routing-options static route 0.0.0.0/0 next-hop 10.20.2.1 
root@PE11# set interfaces ge-0/0/0 unit 0 family inet address 10.20.2.201/24 

root@PE11# set interfaces ge-0/0/1 vlan-tagging 
root@PE11# set interfaces ge-0/0/1 unit 3011 vlan-id 3011 
root@PE11# set interfaces ge-0/0/1 unit 3011 family inet address 10.1.11.254/24 
root@PE11# set interfaces ge-0/0/1 unit 3011 family mpls 
root@PE11# set interfaces ge-0/0/1 unit 3123 vlan-id 3123 
root@PE11# set interfaces ge-0/0/1 unit 3123 family inet address 10.0.123.11/24 
root@PE11# set interfaces ge-0/0/1 unit 3123 family mpls 
root@PE11# set interfaces ge-0/0/2 vlan-tagging 
root@PE11# set interfaces ge-0/0/5 unit 0 family inet address 192.168.1.254/24 

root@PE11# set interfaces lo0 unit 0 family inet address 192.168.255.11/32 
root@PE11# set interfaces lo0 unit 0 family inet6 address 2001:1234::1/128 
root@PE11# set interfaces lo0 unit 0 family mpls 

root@PE11# set routing-options autonomous-system 65123 
root@PE11# set protocols bgp group RR type internal 
root@PE11# set protocols bgp group RR local-address 192.168.255.11 
root@PE11# set protocols bgp group RR family inet-vpn unicast 
root@PE11# set protocols bgp group RR neighbor 192.168.255.154 
root@PE11# set protocols bgp group RR neighbor 192.168.255.254 

#VRF / Policies

Now our BGP is up it is time to create the last piece of the L3VPN and which is making the policies as well as the VRF the CE goes into.

###Policies

In Cisco land we controlled what route we imported and exported under the VRF configuration, Juniper does that too but for more granular control we will make a more elaborate policy.

First we make an community policy that just exports the PE's RD on each router.

root@PE11# set policy-options community RT-EXPORT-CE01 members target:65123:101 

Next we'll do the same for the import community where we will make one for each CE for flexibility's sake.

root@PE11# set policy-options community RT-IMPORT-CE01 members target:65123:101 
root@PE11# set policy-options community RT-IMPORT-CE02 members target:65123:102 
root@PE11# set policy-options community RT-IMPORT-CE03 members target:65123:103 
root@PE11# set policy-options community RT-IMPORT-CE04 members target:65123:104

With that in place we make a policy that will become our VRF-Export policy, we will say that if the protocol is directly connected or one of the routing protocols then we will add the export community and accept the route.

root@PE11# set policy-options policy-statement EXPORT-CE01 term EXPORT from protocol [ direct bgp rip ospf ]
root@PE11# set policy-options policy-statement EXPORT-CE01 term EXPORT then community add RT-EXPORT-CE01 
root@PE11# set policy-options policy-statement EXPORT-CE01 term EXPORT then accept 

If it doesn't match that criteria then we will reject it.

root@PE11# set policy-options policy-statement EXPORT-CE01 term REJECT then reject 

The VRF-Import policy will always be from MBGP so we match on protocol BGP, then we select what communities we want to talk to each other.

In our topology Cust-A is CE01 and CE02 so we'll do that then reject the rest.

root@PE11# set policy-options policy-statement IMPORT-CE01 term IMPORT from protocol bgp 
root@PE11# set policy-options policy-statement IMPORT-CE01 term IMPORT from community [ RT-IMPORT-CE01 RT-IMPORT-CE02 ] 
root@PE11# set policy-options policy-statement IMPORT-CE01 term IMPORT then accept 
root@PE11# set policy-options policy-statement IMPORT-CE01 term REJECT then reject

###VRFs

With all that in place we need to make a VRF instance. In my case I'm using ge-0/0/5 on all the PEs as the CE interface so we add it to the VRF, we also set the PE's proper RD and apply the VRF policies we just made. We also use vrf-table-label to help make the L3VPN happy.

root@PE11# set routing-instances CE01 instance-type vrf 
root@PE11# set routing-instances CE01 interface ge-0/0/5.0 
root@PE11# set routing-instances CE01 route-distinguisher 65123:101 
root@PE11# set routing-instances CE01 vrf-import IMPORT-CE01 
root@PE11# set routing-instances CE01 vrf-export EXPORT-CE01 
root@PE11# set routing-instances CE01 vrf-table-label 

We'll also set the router-id for the instance just to have a bit more control

root@PE11# set routing-instances CE01 routing-options router-id 192.168.255.11 

#Customer Edge

###PE01

Finally we will start working on the CE routing!

We need an export policy so Juniper knows what to send so I'll make a simple one that just accepts any route, since PE01 is BGP we'll setup that too. The config is the same as you have seen though you may want to use the as-override option if you are using BGP.

root@PE11# set policy-options policy-statement EXPORT-BGP then accept
root@PE11# set routing-instances CE01 protocols bgp group CUST-A type external 
root@PE11# set routing-instances CE01 protocols bgp group CUST-A export EXPORT-BGP 
root@PE11# set routing-instances CE01 protocols bgp group CUST-A peer-as 65101 
root@PE11# set routing-instances CE01 protocols bgp group CUST-A neighbor 192.168.1.1 as-override 



root@PE11# set policy-options policy-statement EXPORT-BGP then accept 

root@PE11# set policy-options policy-statement EXPORT-OSPF from protocol bgp 
root@PE11# set policy-options policy-statement EXPORT-OSPF then accept
root@PE11# set policy-options policy-statement EXPORT-RIP then metric 5 
root@PE11# set policy-options policy-statement EXPORT-RIP then accept 

###CE01, CE02, CE03, CE04

Since the CE's are still in flow mode, we need to make sure the interfaces we use are trusted by the security zone, we could get more specific but we aren't really playing with the firewall today :)

root@CE01# set security zones security-zone trust host-inbound-traffic system-services all 
root@CE01# set security zones security-zone trust host-inbound-traffic protocols all 
root@CE01# set security zones security-zone trust interfaces ge-0/0/1.0 
root@CE01# set security zones security-zone trust interfaces ge-0/0/2.0 

###CE01

For BGP we just do a normal peering and advertise everything directly connected.

root@CE01# set policy-options policy-statement EXPORT-BGP from protocol direct 
root@CE01# set policy-options policy-statement EXPORT-BGP then accept

root@CE01# set protocols bgp group CUST-A type external 
root@CE01# set protocols bgp group CUST-A export EXPORT-BGP 
root@CE01# set protocols bgp group CUST-A peer-as 65123 
root@CE01# set protocols bgp group CUST-A neighbor 192.168.1.254 

###CE02

Same with RIP for CE02

root@CE02# set policy-options policy-statement EXPORT-RIP from protocol direct 
root@CE02# set policy-options policy-statement EXPORT-RIP then accept

root@CE02# set protocols rip group CUST-A export EXPORT-RIP 
root@CE02# set protocols rip group CUST-A neighbor ge-0/0/1.0 

###CE03 and CE04

The OSPF CE is a bit unique because it is the only protocol we are looking at today that cares about external routes. Let's setup OSPF in two ways, one will simply add all interfaces to OSPF and the other will use the export method we have been doing

root@CE03# set protocols ospf area 0.0.0.0 interface all 
root@CE03# set protocols ospf area 0.0.0.0 interface lo0.0 passive 


root@CE04# set policy-options policy-statement EXPORT-OSPF from protocol direct 
root@CE04# set policy-options policy-statement EXPORT-OSPF then accept 
root@CE04# set protocols ospf export EXPORT-OSPF    
root@CE04# set protocols ospf area 0.0.0.0 interface ge-0/0/1.0 

Now we get the routes but routes from CE04 are external! We might talk about OSPF specific MPLS topics another day!

root@CE03# run show ospf route    
Topology default Route Table:

Prefix             Path  Route      NH       Metric NextHop       Nexthop      
                   Type  Type       Type            Interface     Address/LSP
192.168.3.254      Intra Area/AS BR IP            1 ge-0/0/1.0    192.168.3.254
172.16.31.0/24     Intra Network    IP            1 ge-0/0/2.0
172.16.32.0/24     Intra Network    IP            1 ge-0/0/2.0
172.16.33.0/24     Intra Network    IP            1 ge-0/0/2.0
172.16.34.0/24     Intra Network    IP            1 ge-0/0/2.0
172.16.41.0/24     Ext2  Network    IP            0 ge-0/0/1.0    192.168.3.254
172.16.42.0/24     Ext2  Network    IP            0 ge-0/0/1.0    192.168.3.254
172.16.43.0/24     Ext2  Network    IP            0 ge-0/0/1.0    192.168.3.254
172.16.44.0/24     Ext2  Network    IP            0 ge-0/0/1.0    192.168.3.254
192.168.3.0/24     Intra Network    IP            1 ge-0/0/1.0
192.168.4.0/24     Ext2  Network    IP            0 ge-0/0/1.0    192.168.3.254

#Verification

Now that everything is up we can make sure that BGP is working properly (probably should have done that sooner!)

root@PE11# run show bgp summary                                        
Groups: 2 Peers: 3 Down peers: 0
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
bgp.l3vpn.0          
                      12          6          0          0          0          0
Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
192.168.1.1           65101       1803       1794       0       3    13:27:34 Establ
  CE01.inet.0: 5/6/6/0
192.168.255.154       65123       1594       1582       0       1    11:54:35 Establ
  bgp.l3vpn.0: 6/6/6/0
  CE01.inet.0: 6/6/6/0
192.168.255.254       65123       1591       1581       0       1    11:54:41 Establ
  bgp.l3vpn.0: 0/6/6/0
  CE01.inet.0: 0/6/6/0

We can also see the MPLS interfaces on the router

root@PE11# run show mpls interface 
Interface        State       Administrative groups (x: extended)
ge-0/0/1.3011    Up         <none>
ge-0/0/1.3123    Up         <none>

[edit]

As well as the LDP neighbors

root@PE11# run show ldp neighbor 
Address                             Interface       Label space ID     Hold time
10.1.11.1                           ge-0/0/1.3011   192.168.255.1:0      14
10.0.123.33                         ge-0/0/1.3123   192.168.255.33:0     13
10.0.123.44                         ge-0/0/1.3123   192.168.255.44:0     13
10.0.123.254                        ge-0/0/1.3123   192.168.255.154:0    11

###PE01 Routing Table

Juniper groups everything into the routing table so we can see the main routing table, the MPLS labels, the VRF routes, and IPv6 routes all in one place! We can also see the INET-VPN routes so we can see if things are being learned properly.

root@PE11# run show route 

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

10.0.123.0/24      *[Direct/0] 12:09:45
                    > via ge-0/0/1.3123
10.0.123.11/32     *[Local/0] 12:09:45
                      Local via ge-0/0/1.3123
10.1.2.0/24        *[OSPF/10] 14:45:03, metric 2
                    > to 10.1.11.1 via ge-0/0/1.3011
10.1.3.0/24        *[OSPF/10] 14:45:03, metric 2
                    > to 10.1.11.1 via ge-0/0/1.3011
10.1.4.0/24        *[OSPF/10] 14:45:03, metric 2
                    > to 10.1.11.1 via ge-0/0/1.3011
10.1.11.0/24       *[Direct/0] 14:45:09
                    > via ge-0/0/1.3011
10.1.11.254/32     *[Local/0] 14:45:09
                      Local via ge-0/0/1.3011
10.1.123.0/24      *[OSPF/10] 11:41:39, metric 2
                    > to 10.0.123.33 via ge-0/0/1.3123
                      to 10.0.123.44 via ge-0/0/1.3123
10.2.3.0/24        *[OSPF/10] 11:42:39, metric 3
                      to 10.1.11.1 via ge-0/0/1.3011
                    > to 10.0.123.33 via ge-0/0/1.3123
10.2.4.0/24        *[OSPF/10] 11:41:48, metric 3
                      to 10.1.11.1 via ge-0/0/1.3011
                    > to 10.0.123.44 via ge-0/0/1.3123
10.2.22.0/24       *[OSPF/10] 11:41:39, metric 3
                      to 10.1.11.1 via ge-0/0/1.3011
                      to 10.0.123.33 via ge-0/0/1.3123
                    > to 10.0.123.44 via ge-0/0/1.3123
10.3.4.0/24        *[OSPF/10] 11:41:48, metric 3
                      to 10.1.11.1 via ge-0/0/1.3011
                      to 10.0.123.33 via ge-0/0/1.3123
                    > to 10.0.123.44 via ge-0/0/1.3123
10.3.33.0/24       *[OSPF/10] 11:42:39, metric 2
                    > to 10.0.123.33 via ge-0/0/1.3123
10.4.44.0/24       *[OSPF/10] 11:41:48, metric 2
                    > to 10.0.123.44 via ge-0/0/1.3123
192.168.255.1/32   *[OSPF/10] 14:45:03, metric 1
                    > to 10.1.11.1 via ge-0/0/1.3011
192.168.255.2/32   *[OSPF/10] 12:00:32, metric 2
                    > to 10.1.11.1 via ge-0/0/1.3011
192.168.255.3/32   *[OSPF/10] 11:42:39, metric 2
                    > to 10.1.11.1 via ge-0/0/1.3011
                      to 10.0.123.33 via ge-0/0/1.3123
192.168.255.4/32   *[OSPF/10] 11:41:48, metric 2
                    > to 10.1.11.1 via ge-0/0/1.3011
                      to 10.0.123.44 via ge-0/0/1.3123
192.168.255.11/32  *[Direct/0] 14:52:17
                    > via lo0.0
192.168.255.22/32  *[OSPF/10] 11:41:39, metric 2
                    > to 10.0.123.33 via ge-0/0/1.3123
                      to 10.0.123.44 via ge-0/0/1.3123
192.168.255.33/32  *[OSPF/10] 11:42:39, metric 1
                    > to 10.0.123.33 via ge-0/0/1.3123
192.168.255.44/32  *[OSPF/10] 11:41:48, metric 1
                    > to 10.0.123.44 via ge-0/0/1.3123
192.168.255.154/32 *[OSPF/10] 12:07:04, metric 1
                    > to 10.0.123.254 via ge-0/0/1.3123
192.168.255.254/32 *[OSPF/10] 11:41:39, metric 2
                      to 10.0.123.33 via ge-0/0/1.3123
                    > to 10.0.123.44 via ge-0/0/1.3123
224.0.0.2/32       *[LDP/9] 14:52:17, metric 1
                      MultiRecv
224.0.0.5/32       *[OSPF/10] 14:52:17, metric 1
                      MultiRecv

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

192.168.255.1/32   *[LDP/9] 14:45:03, metric 1
                    > to 10.1.11.1 via ge-0/0/1.3011
192.168.255.2/32   *[LDP/9] 12:00:32, metric 1
                    > to 10.1.11.1 via ge-0/0/1.3011, Push 299840
192.168.255.3/32   *[LDP/9] 11:42:38, metric 1
                    > to 10.1.11.1 via ge-0/0/1.3011, Push 299808
                      to 10.0.123.33 via ge-0/0/1.3123, Push 299776
192.168.255.4/32   *[LDP/9] 11:41:47, metric 1
                    > to 10.1.11.1 via ge-0/0/1.3011, Push 299792
                      to 10.0.123.44 via ge-0/0/1.3123, Push 299776
192.168.255.22/32  *[LDP/9] 11:37:45, metric 1
                    > to 10.0.123.33 via ge-0/0/1.3123, Push 299952
                      to 10.0.123.44 via ge-0/0/1.3123, Push 299952
192.168.255.33/32  *[LDP/9] 11:42:38, metric 1
                    > to 10.0.123.33 via ge-0/0/1.3123
192.168.255.44/32  *[LDP/9] 11:41:47, metric 1
                    > to 10.0.123.44 via ge-0/0/1.3123
192.168.255.154/32 *[LDP/9] 11:44:55, metric 1
                    > to 10.0.123.254 via ge-0/0/1.3123
192.168.255.254/32 *[LDP/9] 11:37:45, metric 1
                      to 10.0.123.33 via ge-0/0/1.3123, Push 299936
                    > to 10.0.123.44 via ge-0/0/1.3123, Push 299936

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

172.16.11.0/24     *[BGP/170] 13:28:31, localpref 100
                      AS path: 65101 I, validation-state: unverified
                    > to 192.168.1.1 via ge-0/0/5.0
172.16.12.0/24     *[BGP/170] 13:28:31, localpref 100
                      AS path: 65101 I, validation-state: unverified
                    > to 192.168.1.1 via ge-0/0/5.0
172.16.13.0/24     *[BGP/170] 13:28:31, localpref 100
                      AS path: 65101 I, validation-state: unverified
                    > to 192.168.1.1 via ge-0/0/5.0
172.16.14.0/24     *[BGP/170] 13:28:31, localpref 100
                      AS path: 65101 I, validation-state: unverified
                    > to 192.168.1.1 via ge-0/0/5.0
172.16.21.0/24     *[BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.154
                      AS path: I, validation-state: unverified
                      to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    > to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    [BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.254
                      AS path: I, validation-state: unverified
                      to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    > to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
172.16.22.0/24     *[BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.154
                      AS path: I, validation-state: unverified
                      to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    > to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    [BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.254
                      AS path: I, validation-state: unverified
                      to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    > to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
172.16.23.0/24     *[BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.154
                      AS path: I, validation-state: unverified
                      to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    > to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    [BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.254
                      AS path: I, validation-state: unverified
                      to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    > to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
172.16.24.0/24     *[BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.154
                      AS path: I, validation-state: unverified
                    > to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                      to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    [BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.254
                      AS path: I, validation-state: unverified
                    > to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                      to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
192.168.1.0/24     *[Direct/0] 14:45:09
                    > via ge-0/0/5.0
                    [BGP/170] 13:28:31, localpref 100
                      AS path: 65101 I, validation-state: unverified
                    > to 192.168.1.1 via ge-0/0/5.0
192.168.1.254/32   *[Local/0] 14:45:09
                      Local via ge-0/0/5.0
192.168.2.0/24     *[BGP/170] 00:33:22, localpref 100, from 192.168.255.154
                      AS path: I, validation-state: unverified
                      to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    > to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    [BGP/170] 00:33:22, localpref 100, from 192.168.255.254
                      AS path: I, validation-state: unverified
                      to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    > to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
192.168.254.1/32   *[BGP/170] 13:28:31, localpref 100
                      AS path: 65101 I, validation-state: unverified
                    > to 192.168.1.1 via ge-0/0/5.0
192.168.254.2/32   *[BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.154
                      AS path: I, validation-state: unverified
                    > to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                      to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    [BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.254
                      AS path: I, validation-state: unverified
                    > to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                      to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)

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

0.0.0.0/0          *[Static/5] 14:45:09
                    > to 10.20.2.1 via ge-0/0/0.0
10.20.2.0/24       *[Direct/0] 14:45:09
                    > via ge-0/0/0.0
10.20.2.201/32     *[Local/0] 14:45:09
                      Local via ge-0/0/0.0
                                        
mpls.0: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0                  *[MPLS/0] 14:52:17, metric 1
                      to table inet.0
0(S=0)             *[MPLS/0] 14:52:17, metric 1
                      to table mpls.0
1                  *[MPLS/0] 14:52:17, metric 1
                      Receive
2                  *[MPLS/0] 14:52:17, metric 1
                      to table inet6.0
2(S=0)             *[MPLS/0] 14:52:17, metric 1
                      to table mpls.0
13                 *[MPLS/0] 14:52:17, metric 1
                      Receive
16                 *[VPN/0] 14:52:17
                    > via lsi.0 (CE01), Pop      
299776             *[LDP/9] 14:45:03, metric 1
                    > to 10.1.11.1 via ge-0/0/1.3011, Pop      
299776(S=0)        *[LDP/9] 14:45:03, metric 1
                    > to 10.1.11.1 via ge-0/0/1.3011, Pop      
299792             *[LDP/9] 11:41:47, metric 1
                      to 10.1.11.1 via ge-0/0/1.3011, Swap 299792
                    > to 10.0.123.44 via ge-0/0/1.3123, Swap 299776
299808             *[LDP/9] 11:42:38, metric 1
                      to 10.1.11.1 via ge-0/0/1.3011, Swap 299808
                    > to 10.0.123.33 via ge-0/0/1.3123, Swap 299776
299824             *[LDP/9] 12:00:32, metric 1
                    > to 10.1.11.1 via ge-0/0/1.3011, Swap 299840
299856             *[LDP/9] 11:42:38, metric 1
                    > to 10.0.123.33 via ge-0/0/1.3123, Pop      
299856(S=0)        *[LDP/9] 11:42:38, metric 1
                    > to 10.0.123.33 via ge-0/0/1.3123, Pop      
299872             *[LDP/9] 11:41:47, metric 1
                    > to 10.0.123.44 via ge-0/0/1.3123, Pop      
299872(S=0)        *[LDP/9] 11:41:47, metric 1
                    > to 10.0.123.44 via ge-0/0/1.3123, Pop      
299904             *[LDP/9] 11:44:55, metric 1
                    > to 10.0.123.254 via ge-0/0/1.3123, Pop      
299904(S=0)        *[LDP/9] 11:44:55, metric 1
                    > to 10.0.123.254 via ge-0/0/1.3123, Pop      
299936             *[LDP/9] 11:37:45, metric 1
                    > to 10.0.123.33 via ge-0/0/1.3123, Swap 299936
                      to 10.0.123.44 via ge-0/0/1.3123, Swap 299936
299952             *[LDP/9] 11:37:45, metric 1
                    > to 10.0.123.33 via ge-0/0/1.3123, Swap 299952
                      to 10.0.123.44 via ge-0/0/1.3123, Swap 299952

bgp.l3vpn.0: 6 destinations, 12 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

65123:102:172.16.21.0/24                
                   *[BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.154
                      AS path: I, validation-state: unverified
                    > to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                      to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    [BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.254
                      AS path: I, validation-state: unverified
                    > to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                      to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
65123:102:172.16.22.0/24                
                   *[BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.154
                      AS path: I, validation-state: unverified
                    > to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                      to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    [BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.254
                      AS path: I, validation-state: unverified
                    > to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                      to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
65123:102:172.16.23.0/24                
                   *[BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.154
                      AS path: I, validation-state: unverified
                    > to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                      to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    [BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.254
                      AS path: I, validation-state: unverified
                    > to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                      to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
65123:102:172.16.24.0/24                
                   *[BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.154
                      AS path: I, validation-state: unverified
                      to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    > to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    [BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.254
                      AS path: I, validation-state: unverified
                      to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    > to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
65123:102:192.168.2.0/24                
                   *[BGP/170] 00:33:22, localpref 100, from 192.168.255.154
                      AS path: I, validation-state: unverified
                    > to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                      to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    [BGP/170] 00:33:22, localpref 100, from 192.168.255.254
                      AS path: I, validation-state: unverified
                    > to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                      to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
65123:102:192.168.254.2/32                
                   *[BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.154
                      AS path: I, validation-state: unverified
                      to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    > to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    [BGP/170] 00:31:09, MED 2, localpref 100, from 192.168.255.254
                      AS path: I, validation-state: unverified
                      to 10.0.123.33 via ge-0/0/1.3123, Push 19, Push 299952(top)
                    > to 10.0.123.44 via ge-0/0/1.3123, Push 19, Push 299952(top)

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

2001:1234::1/128   *[Direct/0] 14:52:17
                    > via lo0.0
fe80::250:560f:fc9e:4cd1/128
                   *[Direct/0] 14:52:17
                    > via lo0.0
ff02::2/128        *[INET6/0] 14:52:17
                      MultiRecv

#Pastebins

Here are the configs in pastebins for a bit more convenient looking at.

PE01

PE02

PE03

PE04

P01

P02

P03

P04

CE01

CE02

CE03

CE04

Hi. Seems like a pretty low traffic sub, but thought I would try my luck here. Title says it all. just looking for some JNCIS training materials. I know CBT Nuggets has the JNCIS-ENT but I wanted to try to find some other materials as well.

Hello reddit

I'm working in SP and doing some job related to r&s mostly with cisco equipment. I decided to start getting certifications in this field and go cisco R&S

Also I'm interested in security sphere and thinking about juniper security (i'm also doing SWIFT administration job, and SWIFT uses cisco in routing and switching and juniper in security(vpn boxes)). could you please clarify what is the difference between cisco and juniper security?

thanks in advance

I already hold a JNCIA but new job requires JNCIS so shortly will start working on that.

I used junos olive for labbing on jncia but since I will dive in more and more advanced stuff I wonder if olive is enough or maybe I should get some cheap equipment?

What about firefly, is it usable without a license?

Junos Security Overview

• Identify concepts, general features and functionality of Junos OS security
• Junos security architecture
• Branch vs. high-end platforms
• Major hardware components of SRX Series services gateways
• Packet flow
• Packet-based vs. session-based forwarding

Zones

• Identify concepts, benefits and operation of zones
• Zone types
• Dependencies
• Host inbound packet behavior
• Transit packet behavior
• Demonstrate knowledge of how to configure, monitor and troubleshoot zones
• Zone configuration steps
• Hierarchy priority (Inheritance)
• Monitoring and troubleshooting

Security Policies

• Identify the concepts, benefits and operation of security policies
• Policy types (default policy)
• Policy components
• Policy ordering
• Host inbound traffic examination
• Transit traffic examination
• Scheduling
• Rematching
• ALGs
• Address books
• Applications
• Demonstrate knowledge of how to configure, monitor and troubleshoot security policies
• Policies
• ALGs
• Address books
• Custom applications
• Monitoring and troubleshooting

Firewall User Authentication

• Describe the concepts, benefits and operation of firewall user authentication
• User Firewall
• User authentication types
• Authentication server support
• Client groups

Screens

• Identify the concepts, benefits and operation of Screens
• Attack types and phases
• Screen options
• Demonstrate knowledge of how to configure, monitor and troubleshoot Screens
• Screen configuration steps
• Monitoring and troubleshooting

NAT

• Identify the concepts, benefits and operation of NAT
• NAT types
• NAT/PAT processing
• Address persistence
• NAT proxy ARP
• Configuration guidelines
• Demonstrate knowledge of how to configure, monitor and troubleshoot NAT
• NAT configuration steps
• Monitoring and troubleshooting

IPSec VPNs

• Identify the concepts, benefits and operation of IPSec VPNs
• Secure VPN characteristics and components
• IPSec tunnel establishment
• IPSec traffic processing
• Junos OS IPSec implementation options
• Demonstrate knowledge of how to configure, monitor and troubleshoot IPSec VPNs
• IPSec VPN configuration steps
• Monitoring and troubleshooting

High Availability (HA) Clustering

• Identify the concepts, benefits and operation of HA
• HA features and characteristics
• Deployment requirements and considerations
• Chassis cluster characteristics and operation
• Cluster modes
• Cluster and node IDs
• Redundancy groups
• Cluster interfaces
• Real-time objects
• State synchronization
• Ethernet switching considerations
• IPSec considerations
• Manual failover
• Demonstrate knowledge of how to configure, monitor and troubleshoot clustering
• Cluster preparation
• Cluster configuration steps
• Monitoring and troubleshooting

Unified Threat Management (UTM)

• Identify concepts, general features and functionality of UTM
• Packet flow and processing
• Design considerations
• Policy flow
• Platform support
• Licensing
• Describe the purpose, configuration and operation of antispam filtering
• Methods
• Whitelists vs. blacklists
• Order of operations
• Traffic examination
• Configuration steps using the CLI
• Monitoring and troubleshooting
• Describe the purpose, configuration and operation of antivirus protection
• Scanning methods
• Antivirus flow process
• Scanning options and actions
• Configuration steps using the CLI
• Monitoring and troubleshooting
• Describe the concepts, benefits and operation of content and Web filtering
• Filtering features and solutions
• Configuration steps using the CLI
• Monitoring and troubleshooting

Protocol-Independent Routing

• Identify the concepts, operation and functionality of various protocol-independent routing components
• Static, aggregate, and generated routes
• Martian addresses
• Routing instances, including RIB groups
• Load balancing
• Filter-based forwarding
• Demonstrate knowledge of how to configure and monitor various protocol-independent routing components
• Static, aggregate, and generated routes
• Load balancing
• Filter-based forwarding

Open Shortest Path First (OSPF)

• Identify the concepts, operation and functionality of OSPF
• Link-state database
• OSPF packet types
• Router ID
• Adjacencies and neighbors
• Designated router (DR) and backup designated router (BDR)
• OSPF area and router types
• LSA packet types
• Demonstrate knowledge of how to configure, monitor and troubleshoot OSPF
• Areas, interfaces and neighbors
• Additional basic options
• Routing policy application
• Troubleshooting tools

Intermediate System to Intermediate System (IS-IS)

• Identify the concepts, operation and functionality of IS-IS
• Link-state database
• IS-IS PDUs
• TLVs
• Levels and areas
• Designated intermediate system (DIS)
• Metrics
• Demonstrate knowledge of how to configure, monitor and troubleshoot OSPF
• Areas, interfaces and neighbors
• Additional basic options
• Routing policy application
• Troubleshooting tools

Border Gateway Protocol (BGP)

• Identify the concepts, operation and functionality of BGP
• BGP basic operation
• BGP message types
• Attributes
• Route/path selection process
• IBGP and EBGP functionality and interaction
• Demonstrate knowledge of how to configure and monitor BGP
• Groups and peers
• Additional basic options
• Routing policy application

Layer 2 Bridging and VLANs

• Identify the concepts, operation, and functionality of Layer 2 bridging for the Junos OS
• Service Provider switching platforms
• Bridging elements and terminology
• Frame processing
• Virtual Switches
• Provider bridging (e.g., Q-in-Q tunneling)
• Identify the concepts, benefits, and functionality of VLANs
• Port modes
• Tagging
• MVRP
• IRB
• Demonstrate knowledge of how to configure, monitor and troubleshoot Layer 2 bridging and VLANs
• Interfaces and ports
• VLANs
• MVRP
• IRB
• Provider bridging

Spanning-Tree Protocols

• Identify the concepts, benefits, operation, and functionality of Spanning Tree Protocol and its variants
• STP, RSTP, MSTP and VSTP concepts
• Port roles and states
• BPDUs
• Convergence and reconvergence
• Spanning-tree security
• Demonstrate knowledge of how to configure, monitor and troubleshoot STP and its variants
• Spanning-tree protocols - STP, RSTP, MSTP, VSTP
• BPDU, loop and root protection

Multiprotocol Label Switching (MPLS) and MPLS VPNs

• Identify the concepts, operation, and functionality of MPLS
• MPLS terminology
• MPLS packet header
• End-to-end packet flow and forwarding
• Labels and the label information base (LIB)
• MPLS and routing tables
• RSVP
• LDP
• Identify the concepts, benefits, operation, and functionality of MPLS VPNs
• VPN routing tables
• Layer 3 VPN terminology and components
• BGP Layer 2 VPN terminology and components
• LDP Layer 2 circuit terminology and components
• Virtual private LAN service (VPLS) terminology and components
• MPLS VPN control plane traffic flow
• MPLS VPN data plane traffic flow
• Demonstrate knowledge of how to configure and monitor MPLS
• MPLS forwarding
• RSVP-signaled and LDP-signaled LSPs

IPv6

• Identify the concepts, operation and functionality of IPv6
• IPv4 vs. IPv6
• Address types, notation and format
• Address scopes
• Autoconfiguration
• Tunneling
• Demonstrate knowledge of how to configure and monitor IPv6
• Interfaces
• Static routes
• Dynamic routing - OSPFv3, IS-IS, BGP
• IPv6 over IPv4 tunneling

Tunnels

• Identify the concepts, requirements and functionality of IP tunneling
• Tunneling applications and considerations
• GRE
• IP-IP
• Demonstrate knowledge of how to configure and monitor IP tunnels
• GRE configuration
• IP-IP configuration

High Availability

• Identify the concepts, benefits, applications and requirements of high availability
• Link aggregation groups (LAG) and multichassis LAGs (MC-LAGs)
• Graceful restart (GR)
• Graceful Routing Engine switchover (GRES)
• Nonstop active routing (NSR)
• Nonstsop bridging (NSB)
• Bidirectional Forwarding Detection (BFD)
• Virtual Router Redundancy Protocol (VRRP)
• Unified In-Service Software Upgrade (ISSU)
• Ethernet Ring Protection (ERP)
• Demonstrate knowledge of how to configure and monitor high availability component
• LAG, MC-LAG
• Additional basic options
• GR, GRES, NSR and NSB
• VRRP
• ISSU

Layer 2 Switching and VLANs

• Identify the concepts, operation, and functionality of Layer 2 switching for the Junos OS
• Enterprise switching platforms
• Bridging components
• Frame processing
• Identify the concepts, benefits, and functionality of VLANs
• Ports
• Tagging
• Native VLANs and voice VLANs
• Inter-VLAN routing
• Demonstrate knowledge of how to configure, monitor and troubleshoot Layer 2 switching and VLANs
• Interfaces and ports
• VLANs
• Routed VLAN interfaces (RVI)

Spanning Tree

• Identify the concepts, benefits, operation, and functionality of the Spanning Tree Protocol
• STP and RSTP concepts
• Port roles and states
• BPDUs
• Convergence and reconvergence
• Demonstrate knowledge of how to configure and monitor STP and RSTP
• STP
• RSTP

Layer 2 Security

• Identify the concepts, benefits and operation of various protection and security features
• BPDU, loop and root protection
• Port security, including MAC limiting, DHCP snooping, Dynamic ARP inspection (DAI) and IP source guard
• Storm control
• Identify the concepts, benefits and operation of Layer 2 firewall filtres
• Filter types
• Processing order
• Match criteria and actions
• Demonstrate knowledge of how to configure and monitor Layer 2 security
• Protection
• Port security
• Storm control
• Firewall filter configuration and application

Protocol Independent Routing

• Identify the concepts, operation and functionality of various protocol-independent routing components
• Static, aggregate, and generated routes
• Martian addresses
• Routing instances, including RIB groups
• Load balancing
• Filter-based forwarding
• Demonstrate knowledge of how to configure and monitor various protocol-independent routing components
• Static, aggregate, and generated routes
• Load balancing
• Filter-based forwarding

Open Shortest Path First (OSPF)

• Identify the concepts, operation and functionality of OSPF
• Link-state database
• OSPF packet types
• Router ID
• Adjacencies and neighbors
• Designated router (DR) and backup designated router (BDR)
• OSPF area and router types
• LSA packet types
• Demonstrate knowledge of how to configure, monitor and troubleshoot OSPF
• Areas, interfaces and neighbors
• Additional basic options
• Routing policy application
• Troubleshooting tools

Intermediate System to Intermediate System (IS-IS)

• Identify the concepts, operation and functionality of IS-IS
• Link-state database
• IS-IS PDUs
• TLVs
• Adjacencies and neighbors
• Levels and areas
• Designated intermediate system (DIS)
• Metrics
• Demonstrate knowledge of how to configure, monitor and troubleshoot IS-IS
• Levels, interfaces and adjacencies
• Additional basic options
• Routing policy application
• Troubleshooting tools

Border Gateway Protocol (BGP)

• Identify the concepts, operation and functionality of BGP
• BGP basic operation
• BGP message types
• Attributes
• Route/path selection process
• IBGP and EBGP functionality and interaction
• Demonstrate knowledge of how to configure and monitor BGP
• Groups and peers
• Additional basic options
• Routing policy application

Tunnels

• Identify the concepts, requirements and functionality of IP tunneling
• Tunneling applications and considerations
• GRE
• IP-IP
• Demonstrate knowledge of how to configure and monitor IP tunnels
• GRE
• IP-IP

High Availability

• Identify the concepts, benefits, applications and requirements for high availability in a Junos OS environment
• Link aggregation groups (LAG)
• Redundant trunk groups (RTG)
• Virtual Chassis
• Graceful restart (GR)
• Graceful Routing Engine switchover (GRES)
• Nonstop active routing (NSR)
• Nonstop bridging (NSB)
• Bidirectional Forwarding Detection (BFD)
• Virtual Router Redundancy Protocol (VRRP)
• Unified In-Service Software Upgrade (ISSU)
• Demonstrate knowledge of how to configure and monitor high availability components
• LAG and RTG
• Virtual Chassis
• GR, GRES, NSR, and NSB
• VRRP
• ISSU

• What is JNCIS?

• What is its exam number?

• What is the current version of the exam?

• What OS does it cover?

• What is the most equivalent certification by another vendor?