Not a total solution yet, but I really appreciate your help smicker. I am half the way there.
--->> New Routing Table
{master:0}[edit routing-options]
robmin@ex2200c# show
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;
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.
}
--->> Changed lo0 to /32 ## Doesn't this make it so all address resolutions are covered?
{master:0}[edit]
robmin@ex2200c# show interfaces lo0
unit 0 {
family inet {
address 10.0.0.240/32; <<----- Changed this from /24 per your instructions
}
}
--->> This is the same: Interfaces vlan...
unit 400 {
family inet {
address 10.0.0.26/24; <<----- No change here
}
FROM THE SWITCH,
I can now ping 10.0.0.19, .18, 15 (.19 is my NMS server) Yaaaaaaaaayyyyy !
but not 10.0.0.17 - one of my windows servers ? VERY ODD.
FROM THE NETWORK COMPUTERS,
I can still ping all of the above addresses, .19, .18, .15 AND .17
I can now ping 10.0.0.26 (the interface to my 10.0.0.1 router/modem, the LAN/VLAN gateway).
STILL WONDERING:
-Why can't I ping the loopback of the switch from directly connected computers? I still can't ping my loopback adapter on 10.0.0.240/32.
I am very happy that my NMS server has access to the switch via .26.
- I am puzzled why the interface that is connected to the router/modem/gateway is able to be a path into the network. I guess the router is
acting like all good routers do and routing data to and from itself in both directions, back to my .26 interface on the switch and through the
switch to other devices via their directly connected interfaces.
But since each device is plugged directly into the switch (ex2200-c) it would seem they would be able to directly ping lo0, also.
This solves my big problem of wanting to learn about pulling SNMB info from the switch. THANKS THANKS THANKS
Here is the command I ran on the NMS server and the result I got back:
Command:
./snmp-request -c public -v -2c -Ow 10.0.0.26 .1.3.6.1.2.1.1
Result:
Using SNMP4J from: /usr/share/opennms/lib/snmp4j-2.3.1.jar
Using log4j-over-slf4j from: /usr/share/opennms/lib/log4j-over-slf4j-1.7.7.jar
Using SLF4J API from: /usr/share/opennms/lib/slf4j-api-1.7.7.jar
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
1.3.6.1.2.1.1.1.0 = MyMatrix switch
1.3.6.1.2.1.1.2.0 = 1.3.6.1.4.1.2636.1.1.1.2.43
1.3.6.1.2.1.1.3.0 = 6 days, 14:58:16.71
1.3.6.1.2.1.1.4.0 = rhcrco@hotmail.com, cell-phone+1
1.3.6.1.2.1.1.5.0 = snmp MyMatrix
1.3.6.1.2.1.1.6.0 = Marci's House or My House
1.3.6.1.2.1.1.7.0 = 6
Total requests sent: 7
Total objects received: 7
Total walk time: 65 milliseconds
This is awesome!!! Thank you very much!