- Enterasys Security Router User's Guide

Network Management through SNMP
2-38 Managing the XSR
When the memory governor is asked to allow or deny a new resource, the decision is based on:
• memory low watermark
•extreme limit
You can push the extreme limit of individual resources as long as the memory low watermark is
not met. Once the low watermark is met and you wish to create more resources, you must then
free up earlier configured resources.
The memory low watermark can constrain resource creation as follows:
• Un-carved (un-allocated) memory remains in the memory “pie”. If un-carved memory is
lesser than a given number (e.g., 1 Mbyte) creation is denied but if it is larger, it is permitted.
• All memory has been carved. Each free pool (64-byte, 128-byte, and others) must have at least
the defined number of blocks to permit resource creation.
The XSR manages memory more efficiently by means of different-sized memory blocks. Memory
is carved during run time based on malloc requests received. Depending on your startup
configuration, memory will be carved in different ways. There are more than 10 fixed-size pools,
with the amount of carved buffers in each pool depending on your startup configuration. You can
examine memory buffering with the
show buffers, show buffers malloc, and show buffers
i/o
commands.
If you intend to configure and un-configure a large number of resources, be advised to reboot the
XSR when necessary to optimize memory carving.
Also remember that resource creation will be denied in the highly unlikely event of an extreme
limit being reached.
Network Management through SNMP
XSR system monitoring provides for the SNMP v1 agent (READ-ONLY) including gets and
limited sets and SNMP v3 gets and sets. Standard MIB II modules are supported as well as
Enterasys MIBs, as listed in the following table. Proprietary MIBs are available via download at:
http://www.enterasys.com/support/mibs For a list of supported proprietary and standard
MIB objects, refer to the table in “Chapter 1: Network Management “of the XSR User Guide.
In order to use SNMP to gather statistics or configure the device, first configure the XSR’s SNMP
agent with the
snmp-server commands.
Variables you can set are: community name, traps, informs and host. SNMP v3 support includes
options to specify an engineID, security values for users and groups, and associated
show
commands. The
snmp-server view command is an especially powerful tool to display SNMP
objects either via their SNMP term or numerical ID. SNMP v3 data is stored in the
private-
config
file in Flash. Although SNMP is disabled by default, entering any SNMP configuration
command except
snmp-server disable will enable the server.
Refer to “XSR SNMP Proprietary and Associated Standard MIBs” on page B-1 for more
information about supported tables and table objects.
Caution: Do not enroll more certificates nor add more AAA users than permitted by the 1.5 MByte
system limit imposed on both Flash cert.dat and user.dat files, respectively. Doing so may
disable the XSR and require you to delete the files.