Disabling and Reenabling SNMP Proxy
The ability to proxy SNMP from a virtual router (VR) is enabled by default whenever
you create a virtual router agent. However, you can disable or reenable the proxy
feature on each virtual router agent to address any network security issues. To disable
proxy on an agent (router), you must use SNMP or the CLI snmp-server proxy disable
command.
NOTE: Disabling the proxy function on a particular virtual router disables the use of
proxy through that virtual router. You can, however, use the proxy function to access
a proxy-disabled virtual router through another virtual router that does have the
proxy function enabled.
Communicating with the SNMP Engine
The SNMP engine performs the following tasks for SNMPv3:
â– Sends and receives messages.
â– Prepares messages and extracts data from messages.
â– Authenticates, encrypts, and decrypts messages.
â– Determines whether access to a managed task is allowed.
Each SNMP engine has an SnmpEngine ID, a hexadecimal number 15 octets long.
Table 18 on page 154 shows the structure of the SnmpEngine ID.
Table 18: SnmpEngineID Structure Object
DescriptionOctet Assignment
E Series router SNMP management private enterprise number1 – 4
Indicates that octets 6–15 contain information determined by the E Series
router
5
The MAC address for the device. For E120 and E320 routers, the MAC
address is a unique ID based on chassis ID.
6 – 11
The 32-bit (4 octet) router index (or routerUID)12 – 15
Request protocol data units (PDUs) for the SNMP engine must contain the
corresponding contextEngine ID and contextName for the SNMP engine. When the
system receives a PDU, it examines the contextEngine ID and contextName, and
forwards the request to the corresponding virtual router.
â– The contextEngine ID is the same as the SnmpEngine ID.
â– The contextName is an internally derived ASCII string associated with the router.
It has the format routerN, where N is a number (with no leading zeros) in the
154 â– Overview
JUNOSe 11.1.x System Basics Configuration Guide