Re: [j-nsp] Loopback interface and rib-groups

2012-03-25 Thread Alex Arseniev

You don't have to do that with lo0 interface routes in JUNOS.
Configure lo0.nonzero-unit-number with same IP, put it in Salt RI and it 
will work.

HTH
Rgds
Alex

- Original Message - 
From: Alexander Shikoff minot...@crete.org.ua

To: juniper-nsp@puck.nether.net
Sent: Sunday, March 25, 2012 3:39 AM
Subject: [j-nsp] Loopback interface and rib-groups



Hello List,

I have lo0.0 interface in default routing table :

minot...@br1-gdr.ki# show interfaces lo0
unit 0 {
   family inet {
   address 109.68.40.32/32;
   }
}

minot...@br1-gdr.ki# run show route 109.68.40.32/32 table inet.0

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

109.68.40.32/32*[Direct/0] 00:38:51
via lo0.0


I export interface route to other routing instance:
[edit]
minot...@br1-gdr.ki# show routing-options interface-routes
rib-group inet rg-Main2Salt;

[edit]
minot...@br1-gdr.ki# show routing-options rib-groups rg-Main2Salt
import-rib [ inet.0 Salt.inet.0 ];

[edit]
minot...@br1-gdr.ki# run show route 109.68.40.32/32 table Salt

Salt.inet.0: 399123 destinations, 407025 routes (399121 active, 0 
holddown, 2 hidden)

+ = Active Route, - = Last Active, * = Both

109.68.40.32/32*[Direct/0] 00:33:52
via lo0.0

But when I'm trying to ping 109.68.40.32 via interface in Salt instance
I get replies not from 109.68.40.32:

/home/minotaurping 109.68.40.32
PING 109.68.40.32 (109.68.40.32): 56 data bytes
64 bytes from 109.68.40.225: icmp_seq=0 ttl=61 time=0.933 ms
64 bytes from 109.68.40.225: icmp_seq=1 ttl=61 time=0.904 ms
^C
--- 109.68.40.32 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.904/0.919/0.933/0.014 ms

109.68.40.225 is an adress of interface in Salt instance:
minot...@br1-gdr.ki# show interfaces xe-1/3/0
unit 0 {
   description Core;
   family inet {
   no-redirects;
   address 109.68.40.225/29;
   }
}

What's wrong? Thanks in advance!

--
MINO-RIPE
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp



___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


[j-nsp] Loopback interface and rib-groups

2012-03-24 Thread Alexander Shikoff
Hello List,

I have lo0.0 interface in default routing table :

minot...@br1-gdr.ki# show interfaces lo0 
unit 0 {
family inet {
address 109.68.40.32/32;
}
}

minot...@br1-gdr.ki# run show route 109.68.40.32/32 table inet.0  

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

109.68.40.32/32*[Direct/0] 00:38:51
 via lo0.0


I export interface route to other routing instance:
[edit]
minot...@br1-gdr.ki# show routing-options interface-routes 
rib-group inet rg-Main2Salt;

[edit]
minot...@br1-gdr.ki# show routing-options rib-groups rg-Main2Salt 
import-rib [ inet.0 Salt.inet.0 ];

[edit]
minot...@br1-gdr.ki# run show route 109.68.40.32/32 table Salt   

Salt.inet.0: 399123 destinations, 407025 routes (399121 active, 0 holddown, 2 
hidden)
+ = Active Route, - = Last Active, * = Both

109.68.40.32/32*[Direct/0] 00:33:52
 via lo0.0

But when I'm trying to ping 109.68.40.32 via interface in Salt instance
I get replies not from 109.68.40.32:

/home/minotaurping 109.68.40.32
PING 109.68.40.32 (109.68.40.32): 56 data bytes
64 bytes from 109.68.40.225: icmp_seq=0 ttl=61 time=0.933 ms
64 bytes from 109.68.40.225: icmp_seq=1 ttl=61 time=0.904 ms
^C
--- 109.68.40.32 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.904/0.919/0.933/0.014 ms

109.68.40.225 is an adress of interface in Salt instance:
minot...@br1-gdr.ki# show interfaces xe-1/3/0   
unit 0 {
description Core;
family inet {
no-redirects;
address 109.68.40.225/29;
}
}

What's wrong? Thanks in advance!

-- 
MINO-RIPE
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp