Snmpv3 Proxy Configuration; Remote Monitoring - Cisco ONS 15600 Reference Manual

Chapter 13 SNMP
For security reasons, the SNMP proxy feature must be enabled at all receiving and transmitting NEs to
function. For instructions to do this, refer to the Cisco ONS 15600 SDH Procedure Guide.

13.9 SNMPv3 Proxy Configuration

The GNE can act as a proxy for the ENEs and forward SNMP requests to other SNMP entities (ENEs)
irrespective of the types of objects that are accessed. For this, you need to configure two sets of users,
one between the GNE and NMS, and the other between the GNE and ENE. In addition to forwarding
requests from the NMS to the ENE, the GNE also forwards responses and traps from the ENE to the
NMS.
The proxy forwarder application is defined in RFC 3413. Each entry in the Proxy Forwarder Table
consists of the following parameters:
•
•
•
•
•

13.10 Remote Monitoring

The ONS 15600 SDH incorporates RMON to allow network operators to monitor Ethernet facility
performance and events. Software Releases 7.0 and later provide remote data communications channel
(DCC) monitoring using 64-bit RMON over the DCC to gather historical and statistical Ethernet data.
In general, the ONS 15600 SDH system RMON is based on the IETF-standard MIB RFC 2819 and
includes the following five groups from the standard MIB: Ethernet Statistics, History Control, Ethernet
History, Alarm, and Event.
Typical RMON operations, other than threshold provisioning, are invisible to the CTC user.
Note
78-18400-01
Proxy Type—Defines the type of message that may be forwarded based on the translation
parameters defined by this entry. If the Proxy Type is read or write, the proxy entry is used for
forwarding SNMP requests and their response between the NMS and the ENE. If the Proxy Type is
trap, the entry is used for forwarding SNMP traps from the ENE to the NMS.
Context Engine ID/Context Name—Specifies the ENE to which the incoming requests should be
forwarded or the ENE whose traps should be forwarded to the NMS by the GNE.
TargetParamsIn—Points to the Target Params Table that specifies the GNE user who proxies on
behalf of an ENE user. When the proxy type is read or write, TargetParamsIn specifies the GNE user
who receives requests from an NMS, and forwards requests to the ENE. When the proxy type is trap,
TargetParamsIn specifies the GNE user who receives notifications from the ENE and forwards them
to the NMS. TargetParamsIn and the contextEngineID or the contextName columns are used to
determine the row in the Proxy Forwarder Table that could be used for forwarding the received
message.
Single Target Out—Refers to the Target Address Table. After you select a row in the Proxy
Forwarder Table for forwarding, this object is used to get the target address and the target parameters
that are used for forwarding the request. This object is used for requests with proxy types read or
write, which only requires one target.
Multiple Target Out (Tag)—Refers to a group of entries in the Target Address Table. Notifications
are forwarded using this tag. The Multiple Target Out tag is only relevant when proxy type is Trap
and is used to send notifications to one or more NMSs.

13.9 SNMPv3 Proxy Configuration

Cisco ONS 15600 SDH Reference Manual, Release 9.0
13-17