Management
Highlighted
Management

SNMP Traps and routing-instance mgmt_junos

3 weeks ago

Hello,

 

We want to start using the mgmt_junos routing instance, but I can't get the SNMP traps to work. They keep being sent via the default inet.0 instead of the mgmt_junos routing instance

 

In my logs, I keep seeing these messages:

snmpd[5643]: SNMPD_SEND_FAILURE: trap_io_send_trap_now: send to (10.0.x.y) failure: No route to host

 

This route does not exist in the default inet.0, but there is a default route in mgmt_junos.inet.0:

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

0.0.0.0/0 *[Static/5] 1w1d 06:54:12
> to 10.x.y.z via fxp0.0

 

On system, I added management-instance

Radius, snmp polling, etcetera is all working fine

 

under snmp, I have the following configuration:

community public {
authorization read-only;
clients {
10.0.x.0/24;
}
routing-instance mgmt_junos;
}
trap-options {
routing-instance mgmt_junos {
source-address 10.x.y.z;
}
}
trap-group space {
targets {
10.0.x.y;
}
routing-instance mgmt_junos;
}
routing-instance-access;

 

But still, the MX204 running 18.1R3-S3.8 keeps using the default inet.0 for sending snmp traps.

Any suggestions?

 

Regards

Roel

3 REPLIES 3
Highlighted
Management

Re: SNMP Traps and routing-instance mgmt_junos

[ Edited ]
3 weeks ago

Hello Roel,

 

Please include the below line and let me know whether it helps.

 

user@host# set routing-options static route 10.0.x.y next-table mgmt_junos.inet.0

user@host# commit

 

10.0.x.y should be your SNMP server. This way when the route lookup happens the SNMP traps will try to send via inet.0 and since we have pointed a static route towards the management instance it will sent out via fxp0.



Thanks,
π00bm@$t€®.
Please, Mark My Solution Accepted if it Helped, Kudos are Appreciated too!!!
Highlighted
Management

Re: SNMP Traps and routing-instance mgmt_junos

3 weeks ago

That seems to work, but it's more a workaround as an actual fix.

 

Is there no other way to have JunOS use mgmt_junos routing instance for sending traps via fxp0 by default?

Highlighted
Management

Re: SNMP Traps and routing-instance mgmt_junos

3 weeks ago

Hello Roel,

 

Ideally, if we give routing-instance mgmt_junos under SNMP trap hierarchy it should work however in your case I guess it doesn't help.

 

As per the following technical document, only NTP, DNS, Syslog, Radius, TACACS+, BMP and Automation Scripts work under Management Instance. i.e. mgmt_junos - https://www.juniper.net/documentation/en_US/junos/topics/topic-map/management-interface-in-non-defau...

 

Since, there is no SNMP support under mgmt_junos I think it is not working. So, I guess it is an expected behaviour.



Thanks,
π00bm@$t€®.
Please, Mark My Solution Accepted if it Helped, Kudos are Appreciated too!!!
Feedback