Thanks Spuluka,
I had already set interfaces vlan unit 400 family inet address 10.0.0.26/24, and this interface is pingable by any device in the vlan. Are you saying that it makes a difference if the address is actually 1.1.1.1 (de facto)? As of now I cannot ping the lo0 which I have configured as 10.0.0.240/32. I used to have this configured as 10.0.0.240/24 but for some reason I could not ping 10.0.0.26 when the lo0 whas a /24.
Here is what smicker (thanks again smicker) had suggested:
<smicker
1. you are missing L3 assignment of your RVI
set vlans vlan-400 l3-interface vlan.400
2. Once you set that you will then have two routes to 10.0.0.0/24 since lo0 is overlapping with vlan-400
root@ex2200-c> show route protocol direct
inet.0: 6 destinations, 7 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.0.0.0/24 *[Direct/0] 00:08:17
> via vlan.400
[Direct/0] 00:00:03> via lo0.0
Change lo0 to use a /32 and, assuming your default gateway is set correctly on your NMS, you should be able to reach both.
root@ex2200-c> show route protocol direct
inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.0.0.0/24 *[Direct/0] 00:07:40
> via vlan.400
10.0.0.240/32 *[Direct/0] 00:00:24> via lo0.0
ou do not need to add next-hops for subnets that are directly connected to the router--they are automatically inserted into the routing table as direct routes.
route 10.0.0.240/32 next-hop 10.0.0.26; <<----- I added this per your instructions route 10.0.0.0/24 next-hop 10.0.0.26; <<----- Do I actually need this? I added it myself.
Do not forget to add the L3 mapping to vlan 400.
set vlans vlan-400 l3-interface vlan.400
If you can add a topology diagram it could help answer the other questions.
smicker>
But I still was not able to ping the address assigned to the loopback, 10.0.0.14. (it was 10.0.0.240/32, I changed the 240 to 14).
robmin@ex2200c# show interfaces lo0
unit 0 {
family inet {
address 10.0.0.14/32;
}
}
I tried setting this, just now as a /24. and it still is not pingable. Why is the loopback in the switch not pingable? Isn't it that loopbacks are always suppossed to be pingable?
Just now, after makeing it /24, I get this:
robmin@ex2200c# run show route protocol direct
inet.0: 15 destinations, 16 routes (13 active, 0 holddown, 2 hidden)
+ = Active Route, - = Last Active, * = Both
10.0.0.0/24 *[Direct/0] 4d 23:03:21
> via vlan.400
[Direct/0] 00:10:20
> via lo0.0
Here is my question from above:
I was told that the loopback is a virtual layer 3 interface. So why can't the layer 3 vlan-400 route to the layer 3 loopback? They are both on layer 3, and are they both directly connected?
This is where I thought that adding some kind of static route in the routing-table (a layer 3 map) would allow traffic destined for the loopback to be able to get to it and get back. But when you (smicker) reminded me that directly connected addresses don't need to be explicity added to the table, I got confused. I understand the concept, but is the loopback directly connected? And if it is, then why can't vlan-400 traffic automatically find it?
So no matter what I do I still can't ping lo0. And if I set 10.0.0.26/24, assigned to unit 400, my gateway for devices in vlan-400, are they still going to be able to get to the cable modem on 10.0.0.1/24 - the current Gateway, and ultimately the Internet?
P.S. I tried setting the gateway on one computer to 10.0.0.26 and I was surprised that it was still able to get to the Internet. I guess the switch somehow routes traffic destined for other networks to 10.0.0.1 through its own routing table? But, alas, this still did not make lo0 pingable. ???? I don't understand why the loopback is not pingable. From what I have read and studied over the years, I got the idea that the loopback was always up so that you could rely upon it for things that needed to persist in determining if the device was still there, like routing protocols (STP, RIP, OSPF, etc). But if my loopback is not seeable, how would this even be possible?
robmin@ex2200c# show routing-options
static {
route 0.0.0.0/0 next-hop 10.0.0.1; <<<--------------- I guess this is why that computer still got to the Internet?
route 240.0.0.8/32 discard;
route 240.0.0.9/32 reject;
route 1.1.1.1/32 {
next-hop 10.40.1.1;
qualified-next-hop 2.2.2.2 {
preference 7;
}
}
route 7.7.7.7/32 next-hop 10.20.1.3;
route 18.18.18.18/32 next-hop 10.80.1.1;
route 6.6.6.6/32 next-hop 10.60.1.1;
route 10.60.31.0/24 next-hop 10.60.1.1;
Thanks spuluka.