From IOS to Junos – Day 2

Notes from the day

I am just going to dump my text notes for the day, you have no idea how long it would take to format this stuff, and hell I do it to share, not to make profit.

 

** when I had shutdown after the previous days works,

I had a thought that the loopback 0 (only loopback adaptor in Junos)

would probably be done using unit numbers, as soon a I woke up and checked my

twitter I had a tweet from @networkjanitor

"In regards to Junos Loopbacks you can have multiple unit interfaces

and they can go diff vrfs"

so first task today is remove existing loopback 0 unit 0 address

and create new loopback 0 unit 10 address.

root@Junos1# edit interfaces lo0 

[edit interfaces lo0]

root@Junos1# edit unit 0 

[edit interfaces lo0 unit 0]

root@Junos1# show
family inet {
    address 10.254.200.1/32;
}

[edit interfaces lo0 unit 0]
root@Junos1# delete family inet address 10.254.200.1/32 

[edit interfaces lo0 unit 0]
root@Junos1# commit
commit complete

[edit interfaces lo0]
root@Junos1# edit unit 10 

[edit interfaces lo0 unit 10]
root@Junos1# set family inet address 10.254.200.1/32       

[edit interfaces lo0 unit 10]
root@Junos1# commit
[edit interfaces lo0]
  'unit 10'
    if_instance: Multiple loopback interfaces not permitted in master routing instance
error: configuration check-out failed

[edit interfaces lo0 unit 10]

** OH Dear, 

** after a bit of work I found that I had not deleted unit 0 of lo0 

[edit interfaces]
admin@Junos1# delete lo0 unit 0
commit

[edit]
root@Junos1# set interfaces lo0 unit 10 family inet address 10.254.200.1/32    

[edit]
root@Junos1# commit
commit complete

[edit]
root@Junos1# 

**problem resolved

========== Moving onto Junos2
** setup the same basics as Junos1
name
domain-name
ip addresses
ssh
I had to go back and look at day 1 note for some guidance.

** now thats done let try and get rip running between 1 and 2

root@Junos1> configure
Entering configuration mode

[edit]
root@Junos1# edit protocols
[edit protocols]
root@Junos1# set rip group 1 neighbor em1    

[edit protocols]
root@Junos1# commit
commit complete

** rig group name , I have used 1 need to look about and see what the standard way of representing this in JUNOS is

the same process on Junos 2 em0, I donot have ssh access yet so I am not pasting the commands

[edit protocols]
root@Junos1# set rip group 1 neighbor em1
[edit protocols]
root@Junos1# set rip group 1 neighbor em10

did the same on Junos2 but no routes. found this helpful page    http://knol.google.com/k/configuring-basic-rip-using-a-juniper-olive-junos-via-cli#

so by default RIP will not advertise routes out

[edit]
root@Junos1# edit policy-options
[edit policy-options]
root@Junos1# set policy-statement adv-rip-routes term 1 from protocol rip    

[edit]
root@Junos1# edit policy-options 

[edit policy-options]
root@Junos1# set policy-statement adv-rip-routes term 1 then accept 

[edit policy-options]
root@Junos1# commit 

[edit protocols rip]
root@Junos1# top 

commit complete
[edit policy-options]

root@Junos1# top edit protocols rip
[edit protocols rip]
root@Junos1# set group 1 export adv-rip-routes

** the command line will show what groups are aval and what policies --excellent

***I can not see 192.168.1.11 in router 2
found it I should habe used
root@Junos1# set policy-statement adv-rip-routes term 1 from protocol direct
in addition to rip
I had temporarily set it and remove it on router 2 so I could see the route in Junos 1

protocols {
    rip {
        group 1 {
            export adv-rip-routes;
            neighbor em0.0;
            neighbor lo0.10;
            neighbor em1.0;
        }
    }
}
policy-options {
    policy-statement adv-rip-routes {
        term 1 {
            from protocol [ rip direct ];
            then accept;
        }

which appear to work , I can now ssh onto 10.254.200.2 with admin user.

** need to understand direct and rip
assumption at this point is direct = routes generated by routing protocol from within this host.
rip= route in the rip protocol not from this host????

**Final update 3/10/11 23:30

direct = directly connected networks on this router. even if they donot have rip configure on the interface e.g

show route protocol direct

so enabling rip on the lo.10 was a waste of time

rip = would guess as above "routes in the rip protocol not from this host"

What I achieved

• Got loopback 10 sorted


• Got rip working although need to look at Direct/Rip from protocol

 

 

Noteworth thoughts

• I like the concept of setting up the routing protocol and establishing relationship without actually sending routing update, looking forward to see if this is the same with OSPF.


• Need more work on the show / diagnostic command to verify current status


• Need to investigate naming convention for protocol Groups