Virtual Routers; Creating Snmp Proxy; Disabling And Reenabling Snmp Proxy - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - SYSTEM BASICS CONFIGURATION GUIDE 2010-10-04 Configuration Manual

Software for e series broadband services routers system basics configuration guide
Hide thumbs Also See for JUNOSE SOFTWARE FOR E SERIES 11.3.X - SYSTEM BASICS CONFIGURATION GUIDE 2010-10-04:
Table of Contents

Advertisement

Virtual Routers

Copyright © 2010, Juniper Networks, Inc.
Table 17: Relationship Among Groups, Security Levels, and Views
(continued)
Group Name
Security Level
private
authentication
only
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.

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
Read View
Write View
user
user
Chapter 4: Configuring SNMP
Notification/
Trap View
user
143

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 11.3

Table of Contents