6

MIB

Source

Function

 

 

 

Nokia Enhanced SNMP

proprietary

Note: IPSO does not send traps that this MIB supports when

Solution Suite PM IRP MIB

 

the Nokia platform is used as an IP security device.

Nokia NE3S Registration MIB

proprietary

 

Nokia Link Aggregation MIB

proprietary

Contains the traps required for managing link aggregation.

Nokia NTP MIB

proprietary

 

SNMPv2-CONF

 

IPSO does not support this MIB but it is included for those

 

 

customers who need it to enable their management tools.

 

 

This MIB resides in the /etc/snmp/mibs/unsupported

 

 

directory.

 

 

 

Both the proprietary MIBs and the public MIBs are supplied with the system. To view more detailed information about the MIBs, see the /etc/snmp/mibs directory.

Note

The SNMPv2-CONF MIB resides in the /etc/snmp/mibs/unsupported directory.

The SNMP agent implemented in Nokia IPSO enables an SNMP manager to monitor the device and to modify the sysName, sysContact and sysLocation objects only.

Note

You must configure an SNMP string first to configure sysContact and sysLocation.

Use Network Voyager to perform the following tasks:

„Define and change one read-only community string.

„Define and change one read-write community string.

„Enable and disable the SNMP daemon.

„Create SNMP users.

„Modify SNMP user accounts.

„Add or delete trap receivers.

„Enable or disable the various traps.

„Enter the location and contact strings for the device.

SNMP Proxy Support for Check Point MIB

IPSO supports the use of a proxy for SNMP GetRequest and SNMP GetNextRequest for Check Point objects. The following are guidelines and limitations you should be aware of.

252

Nokia Network Voyager for IPSO 4.0 Reference Guide

Page 252
Image 252
Nokia IPSO 4.0 manual Snmp Proxy Support for Check Point MIB, 252