Quantcast
Channel: All Ethernet Switching posts
Viewing all articles
Browse latest Browse all 10307

Re: Can't ping my lo0 on switch from computers attached to vlan on that switch.

$
0
0

Thank you for the explanation about directly connected routes. So I TOOK OUT the two static

routes, 10.0.0.0/24 next-hop 10.0.0.26 and, 10.0.0.240 next-hop 10.0.0.26.

robmin@ex2200c# show routing-options
static {
route 0.0.0.0/0 next-hop 10.0.0.1;
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;


I had already added this as you asked me to on your previous post.

robmin@ex2200c# show interfaces lo0
unit 0 {
family inet {
address 10.0.0.4/32;  <<<---- This was the 10.0.0.240, I changed it just now to 10.0.0.4 in all the places it occured.

 

By The Way, you suggested: Change lo0 to use a /32 and, assuming your default gateway is set correctly on your NMS, you should be able to reach both. How can a ping get a response with the /32, doesn't it have to be a /24 like everything else on the network to talk to devices. In Other workds, doesn't a /24 put it on the same subnet? Don't devices have to be in the same subnet (vlan) inorder to ping each other? Wouldn't this make it so the ping can't get to the lo0 interface?

 

robmin@ex2200c# show interfaces vlan
unit 0 {
family inet {
dhcp {
vendor-id Juniper-ex2200-c-12p-2g;
}
}...

}
unit 400 {
family inet {
address 10.0.0.26/24;
}
}

 

robmin@ex2200c# run show route protocol direct

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

10.0.0.0/24 *[Direct/0] 1d 11:06:20
> via vlan.400
10.0.0.240/32 *[Direct/0] 1d 10:47:37
> via lo0.0

 

robmin@ex2200c# show vlans vlan-400
interface {
ge-0/1/0.0; --->> Comcast router/modem/gateway (all nodes have their gateways set to this)
ge-0/0/0.0; --->> CISCO 1841 Router
ge-0/0/1.0; --->> Juniper J2350 Router
ge-0/0/2.0; --->> MacBook Air this is USB'd/DB-9'd/Cat5e'd into my console port on EX2200-c
ge-0/0/3.0; --->> Ubuntu Server with NMS Server to do the SNMP Management
ge-0/0/7.0; --->> Debian Bare Metal Machine
ge-0/0/10.0; --->> Windows Server 2008 R2 sp1 64-bit AMD
ge-0/0/11.0; --->> Windows Server 2008 Standard 32-bit i386


TOPOLOGY

EX2200-c Switch, 10.0.0.4 on lo0 (changed from .240 to .4) still can't be pinged from outside the

switch.

EX2200-c Switch ge-0/1/0, 10.0.0.26 <---wired---> 10.0.0.1, Comast Router/Modem/Gateway

Ports ge-0/0/0, 1, 2, 3, 7,10, 11 (7 total) are connected using
unit 0 family ethernet-switching port-mode access

Ubuntu 14.04 with OpenNMS Server and Remote desktop server Thinlinc, 10.0.0.19

Windows Server 2008 standard, 10.0.0.18

Windows Server 2008 R2, 10.0.0.17

Windows 7 Professional Client laptop 10.0.0.15

Debian 8.3.0 Server, 10.0.0.7
with VirtualBox running Remote desktop server Ulteo, 10.0.0.8

Junipter J2350 router connected directly to ge-0/0/1, turned off since I haven't configured the

router yet.

Cisco 1841 router directly connected to ge-0/0/0, also turned off for now
I just grabbed these two devices from my CCIE lab today.

All of these computers, servers and devices are connected to the EX2200-c switch on ports in the

vlan-400. The switch can ping everyone of them except my Windows Server 2008 R2 on

10.0.0.17 and and ubuntu physical and virtual machines .7, .8. very very ODD.
All other nodes can ping all addresses except the lo0, 10.0.0.4.

Parallels Virtual Machine Guest OS Windows 7 Professional on MacBook Air, 10.0.0.3

MacBook Air, 10.0.0.2

Cannot ping the lo0 address of 10.0.0.4 from any device plugged into a port on the Switch.

HERE I NOTICED SOMETHING:

Logical interface vlan.400 (Index 87) (SNMP ifIndex 535)
Flags: Up SNMP-Traps 0x4000 Encapsulation: ENET2
Input packets : 23129
Output packets: 5983
Protocol inet, MTU: 1500
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.0/24, Local: 10.0.0.26, Broadcast: 10.0.0.255 <<<---- I noticed this,
it seems that the fourth octet is missing from the Destination address here.

robmin@ex2200c# show interfaces lo0
unit 0 {
family inet {
address 10.0.0.4/32; <<<---- Here it has the fourth octet.

 

robmin@ex2200c> show interfaces lo0
Physical interface: lo0, Enabled, Physical link is Up
Interface index: 6, SNMP ifIndex: 6
Type: Loopback, MTU: Unlimited
Device flags : Present Running Loopback
Interface flags: SNMP-Traps
Link flags : None
Last flapped : Never
Input packets : 16569142
Output packets: 16569142

Logical interface lo0.0 (Index 65) (SNMP ifIndex 16)
Flags: Down SNMP-Traps Encapsulation: Unspecified
Input packets : 60
Output packets: 60
Protocol inet, MTU: Unlimited
Flags: None
Addresses, Flags: Is-Default Is-Primary
Local: 10.0.0.4

Logical interface lo0.16384 (Index 64) (SNMP ifIndex 21)
Flags: Encapsulation: Unspecified
Input packets : 0
Output packets: 0
Protocol inet, MTU: Unlimited
Flags: None
Addresses, Flags: Primary
Local: 127.0.0.1

show vlans
Name Tag Interfaces
default
None
v100 100
ge-0/0/9.0
v25 25
ge-0/0/4.0, ge-0/0/9.0
v50 50
ge-0/0/5.0, ge-0/0/9.0
vlan-100
None
vlan-400
ge-0/0/0.0, ge-0/0/1.0, ge-0/0/2.0*, ge-0/0/3.0*,
ge-0/0/7.0*, ge-0/0/10.0*, ge-0/0/11.0*, ge-0/1/0.0*
vlan-lpc
None


Viewing all articles
Browse latest Browse all 10307

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>