I currently try to add a SRX-Box into Junos Space by using SNMPv3.
The interface on the box, by which Junos Space try to communicate with the box is located in a custom-routing-instance.
For that, the SNMPv3-Option "context" must be used.
But these context-option is not available within Junos Space Device Discovery Process. Only Auth/Enc and USer can be set.
Is there a way to add boxes to Junos Space by using SNMPv3 when the Junos-Space-Traffic will terminate on the box by an interface which is not memeber of master-instance ?
We are currently using Space Version 18.2 R1 Build 4
Go to Solution.
I am not a junos space expert. But what you want to achieve can be done by SNMPv2 community
1. Enable snmp for routing-instance
set snmp community global routing-instance test clients x.x.x.x/32 <<<IP of you mgmt server set snmp routing-instance-access
2. For example, you have routing-instance test and you have your snmp community as global. Here's the linux command to use from your polling server:
snmpwalk -v2c -c test@global <host> <oid>
3. For junos space, I guess what you need to manipulate is the SNMP community
thanks for the reply.
Yeah, I know you can configure the routing-instance access with SNMP v1/2, but as I mentioned I want/must use SNMPv3.So I guess I will create a JTAC-Ticket for that.
Currently you configure SNMPv3 & have reachability through default routing-instance only.
JUNOS Space does not yet support SNMPv3 via routing instance yet.
Here is PR 1400883 for same, its product limitation, in case if your customer requires SNMPv3 via JUNOS Space to query through a routing-instance, get in touch with Juniper Accounts team.
Here is link to PR for details:
Thanks for the information.
Hopefully this will be added in one of the next releases.