Users polling the device from a routing-instance
will only able to view the properties of that particular routing-instance
. This article provides a procedure to enable users to see all the routing-instances
.
All the routing-instance
statistics should be visible when polling through a routing-instance
.
Use the procedure described in KB13080 to enable routing-instance
access. When users try to poll using the community string <routing-instance>@<community>
, they will only be able to see the statistics of that named routing-instance
.
To see statistics of all the routing-instances, can use the community string: @<community>. Do not specify any routing-instance name before the '@' symbol.
Other possible variations:
- <community> - which works if user polls directly from inet.0
- <routing-instance>@<community> - which polls information for specific routing instance
- default@<community> - which allows polling information about inet.0 only
Example:
Consider the following configuration:
interfaces {
fe-0/0/0 {
description "default routing-instance interface";
unit 0 {
family inet {
address 192.168.2.1/24;
}
}
}
fe-0/0/5 {
description "custom routing-instance interface";
unit 0 {
description "custom routing-instance interface logical unit";
family inet {
address 172.27.201.4/24;
}
}
}
}
snmp {
community jsrx {
authorization read-write;
routing-instance custom {
clients {
172.27.199.0/24;
172.27.201.0/24;
0.0.0.0/0 restrict;
}
}
}
routing-instance-access;
}
routing-instances {
custom {
instance-type virtual-router;
interface fe-0/0/5.0;
routing-options {
static {
route 172.27.199.0/24 next-hop 172.27.201.3;
}
}
}
}
The device is being polled on interface fe-0/0/5 (172.27.201.4) using community custom@jsrx
. If the user does an SNMP MIB walk to get all the interface descriptions (snmb mib walk oid "1.3.6.1.2.1.31.1.1.1.18" or "ifAlias"
), the device will return the following results:
1.3.6.1.2.1.31.1.1.1.18.513 custom routing-instance interface
1.3.6.1.2.1.31.1.1.1.18.530 custom routing-instance interface logical unit
If the same OID is polled using community default@jsrx
on interface fe-0/0/5 (172.27.201.4), the device will return the following results:
1.3.6.1.2.1.31.1.1.1.18.507 default routing-instance interface
In case the interface that being polled is the default routing-instance and the configuration is as follows:
interfaces {
fe-0/0/0 {
description "default routing-instance interface";
unit 0 {
family inet {
address 192.168.2.1/24;
}
}
}
fe-0/0/5 {
description "custom routing-instance interface";
unit 0 {
description "custom routing-instance interface logical unit";
family inet {
address 172.27.201.4/24;
}
}
}
}
snmp {
community jsrx {
authorization read-write;
clients {
172.27.201.0/24;
0.0.0.0/0 restrict;
172.27.199.0/24;
}
}
}
routing-instances {
custom {
instance-type virtual-router;
interface fe-0/0/0.0;
routing-options {
static {
route 172.27.199.0/24 next-hop 172.27.201.3;
}
}
}
}
Now if the poll uses community jsrx
on interface fe-0/0/5 using IP 172.27.201.4, the device will return the following result:
1.3.6.1.2.1.31.1.1.1.18.507 default routing-instance interface
1.3.6.1.2.1.31.1.1.1.18.513 custom routing-instance interface
1.3.6.1.2.1.31.1.1.1.18.530 custom routing-instance interface logical unit