Virtual Routers; Creating Snmp Proxy - Juniper SYSTEM BASICS - CONFIGURATION GUIDE V 11.1.X Configuration Manual

System basics configuration guide software for e series broadband services routers
Table of Contents

Advertisement

Table 17: Relationship Among Groups, Security Levels, and Views (continued)

Virtual Routers

All SNMP-related CLI commands operate in the context of a virtual router, which
means that you must configure users, traps, communities, and so on for each server.
You must set the context using the virtual-router command and then configure
SNMP.
The show snmp commands show only statistics and configuration information for
the server/SNMP agent that corresponds to the current virtual router context.
The exceptions to this convention are the snmp-server contact and the snmp-server
location commands. With these commands, single instances of the contact and the
location are created regardless of the number of virtual routers.

Creating SNMP Proxy

Your JUNOSe software allows you to configure multiple virtual routers. Each virtual
router has its own SNMP server. At router initialization, SNMP creates a server for
each existing virtual router.
When router-specific data is required, the requestor can direct a request to a particular
server for a virtual router through the base community string extension: for example,
SNMP get public@megaRouter.
NOTE: In addition to the @ selector character, the system also supports the % selector
character. For example, SNMP get public%megaRouter.
When any system server parses a request and detects an extended community string,
it acts as proxy by forwarding the request to the server corresponding to the virtual
router name in the extension (for example, megaRouter). The target server then
processes the request and generates a response, which is then returned to the proxy
server and subsequently transmitted to the requester.
The JUNOSe implementation of SNMPv3 communicates with virtual routers by
assigning each proxy agent an SNMP engine ID. This difference is unimportant to
users of the CLI. However, if you use other SNMPv3 applications to manage the
router, refer to the following section.
Group Name
Security Level
private
authentication
only
Chapter 4: Configuring SNMP
Read View
Write View
user
user
Notification/
Trap View
user
153
Overview

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 11.1

Table of Contents