[j-nsp] Logical-Systems Management SNMP
Gabriel Farias
I have a router model M10i Junos 9.6R1.13 running and is working with
three-logical systems (LS1, LS2 and LS3), I need to manage all logical
systems using SNMP, the best way?
*I am using the command*:
set snmp community <name-community> logical-system <name-system>
In addition to this command that is needed?
Thanks,
Gabriel Farias
_______________________________________________
juniper-nsp mailing list junip...@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Gabriel Farias
I used the following configuration, but I'm having error and the server
database can not read the information via snmp.
Do you have any hint of what is happening?
thanks
*Attempting Server*:
sa19rb1:/ # ping 10.251.42.230 -n 4
PING 10.251.42.230: 64 byte packets
64 bytes from 10.251.42.230: icmp_seq=0. time=1. ms
64 bytes from 10.251.42.230: icmp_seq=1. time=1. ms
64 bytes from 10.251.42.230: icmp_seq=2. time=1. ms
64 bytes from 10.251.42.230: icmp_seq=3. time=1. ms
----10.251.42.230 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 1/1/1
sa19rb1:/ # snmpwalk 10.251.42.230 system
snmpwalk: No response arrived before timeout.
*Configure used*
{master}[edit]
qos@IXR01RJO# show snmp
community XPTO {
authorization read-only;
logical-system RT30RJO {
routing-instance manager-snmp;
}
}
trap-options {
logical-system RT30RJO {
routing-instance manager-snmp {
source-address 10.251.42.230;
}
}
}
routing-instance-access;
traceoptions {
file debug-snmp;
flag all;
}
{master}[edit]
qos@IXR01RJO# run monitor start debug-snmp
*ERROR*:
{master}[edit]
qos@IXR01RJO#
*** debug-snmp ***
Jun 17 16:35:28 snmpd[5709] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Jun 17 16:35:28 snmpd[5709] >>> Get-Next-Request
Jun 17 16:35:28 snmpd[5709] >>> Source: 10.31.0.236
Jun 17 16:35:28 snmpd[5709] >>> Destination: 10.251.42.230
Jun 17 16:35:28 snmpd[5709] >>> Version: SNMPv1
Jun 17 16:35:28 snmpd[5709] >>> Request_id: 0x5709
Jun 17 16:35:28 snmpd[5709] >>> Community: XPTO
Jun 17 16:35:28 snmpd[5709] >>> Error: status=0 / vb_index=0
Jun 17 16:35:28 snmpd[5709] >>> OID : system
Jun 17 16:35:28 snmpd[5709] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Jun 17 16:35:28 SNMPD_AUTH_RESTRICTED_ADDRESS: nsa_initial_callback: request
from address 10.31.0.236 not allowed
Jun 17 16:35:28 SNMPD_AUTH_FAILURE: nsa_initial_embedcomm: unauthorized SNMP
community from 10.31.0.236 to unknown community name (XPTO)
Jun 17 16:35:28 ns_trap_internal
Jun 17 16:35:28 ns_trap_internal
Jun 17 16:35:29 snmpd[5709] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Jun 17 16:35:29 snmpd[5709] >>> Get-Next-Request
Jun 17 16:35:29 snmpd[5709] >>> Source: 10.31.0.236
Jun 17 16:35:29 snmpd[5709] >>> Destination: 10.251.42.230
Jun 17 16:35:29 snmpd[5709] >>> Version: SNMPv1
Jun 17 16:35:29 snmpd[5709] >>> Request_id: 0x5709
Jun 17 16:35:29 snmpd[5709] >>> Community: XPTO
Jun 17 16:35:29 snmpd[5709] >>> Error: status=0 / vb_index=0
Jun 17 16:35:29 snmpd[5709] >>> OID : system
Jun 17 16:35:29 snmpd[5709] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Jun 17 16:35:29 SNMPD_AUTH_RESTRICTED_ADDRESS: nsa_initial_callback: request
from address 10.31.0.236 not allowed
Jun 17 16:35:29 SNMPD_AUTH_FAILURE: nsa_initial_embedcomm: unauthorized SNMP
community from 10.31.0.236 to unknown community name (XPTO)
Jun 17 16:35:32 snmpd[5709] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Jun 17 16:35:32 snmpd[5709] >>> Get-Next-Request
Jun 17 16:35:32 snmpd[5709] >>> Source: 10.31.0.236
Jun 17 16:35:32 snmpd[5709] >>> Destination: 10.251.42.230
Jun 17 16:35:32 snmpd[5709] >>> Version: SNMPv1
Jun 17 16:35:32 snmpd[5709] >>> Request_id: 0x5709
Jun 17 16:35:32 snmpd[5709] >>> Community: XPTO
Jun 17 16:35:32 snmpd[5709] >>> Error: status=0 / vb_index=0
Jun 17 16:35:32 snmpd[5709] >>> OID : system
Jun 17 16:35:32 snmpd[5709] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Jun 17 16:35:32 SNMPD_AUTH_RESTRICTED_ADDRESS: nsa_initial_callback: request
from address 10.31.0.236 not allowed
Jun 17 16:35:32 SNMPD_AUTH_FAILURE: nsa_initial_embedcomm: unauthorized SNMP
community from 10.31.0.236 to unknown community name (XPTO)
Tranks
Gabriel Farias
2010/6/10 Gabriel Farias <gabriel...@gmail.com>
Dan Farrell
Dan
Dan Farrell
# snmpwwalk -c XPTO 10.251.42.230 system
Dan
-----Original Message-----
From: Dan Farrell
Sent: Thursday, June 17, 2010 4:39 PM
To: 'Gabriel Farias'; junip...@puck.nether.net; juniper-n...@puck.nether.net
Subject: RE: [j-nsp] Logical-Systems Management SNMP
# set snmp community XPTO clients 10.31.0.236
Dan
-----Original Message-----
From: juniper-n...@puck.nether.net [mailto:juniper-n...@puck.nether.net] On Behalf Of Gabriel Farias
Sent: Thursday, June 17, 2010 4:16 PM
To: junip...@puck.nether.net; juniper-n...@puck.nether.net
Subject: Re: [j-nsp] Logical-Systems Management SNMP
Subodh Kumar
Is the NMS sending SNMP queries on an interface in Logical System? If
No (i.e. the snmp queries are coming on fxp0 or an interfaces in
"default" routing-instance (inet.0)), then you don't need the below
configuration:
set snmp community <name-community> logical-system <name-system>
A simple configuration of "set snmp community <name-community>" shall
work for you. To get the Logical-system/routing-instance specific data
from the router, you just need to append
"<logical-system-name>/<routing-system-name>@" before the configured
community in the SNMP request PDU.
For more details, pls refer to section on "Identifying a Routing
Instance" on page 99 of the document at:
http://www.juniper.net/techpubs/en_US/junos9.6/information-products/topi
c-collections/config-guide-network-mgm/config-guide-network-mgm.pdf
Thanks
Subodh
> -----Original Message-----
> From: juniper-n...@puck.nether.net [mailto:juniper-nsp-
> bou...@puck.nether.net] On Behalf Of Dan Farrell
> Sent: Friday, June 18, 2010 2:11 AM
> To: Gabriel Farias; junip...@puck.nether.net; juniper-nsp-
> bou...@puck.nether.net
> Subject: Re: [j-nsp] Logical-Systems Management SNMP
>