Setup & User Guide
121 |
DOC-246-GDE-Pivot3 Acuity 2.3 Setup & User Guide-v1.0.docx
Network-Management System (NMS)
Third-party management software using SNMP can be found from many sources. Some are simple trap catchers that
route traps to email. Others involve more sophisticated polling mechanisms. Some examples of third-party management
software packages include HP OpenView product family, IBM Tivoli products, Solarwinds Orion Network Performance
Monitor, Trap Receiver, and WhatsUp Gold.
When the network-management application uses SNMP for polling, be sure to set up polls for both static IP addresses of
each node. Otherwise a failed switch may not be reported.
The vPG agents use default SNMP ports. The NMS must allow access to UDP port 162 to receive traps and UDP port 161 to
poll for information. Each of these ports may have to be opened on the NMS if a firewall is enabled.
Many network-management applications use SMTP to forward traps as email. The network-management application will
push an SMTP message to the corporate email server, which will forward the message as an email to a specified email
address. The default SMTP port is TCP port 25. This port must be exempted from a firewall at the corporate email server.
Ports for SNMP network management
Port Transport Used For Must be open at
25 TCP SMTP email Email server receiving SMTP messages
161 UDP SNMP requests Acuity Management Station
162 UDP SNMP traps Acuity Management Station
Community Strings
Community Strings are configured through vSMS for an Acuity vPG. There are separate Community Strings for SNMP
Clients and Trap Targets. The common default value for both community strings is “public.”
The Community String for SNMP Clients is used to allow the agents to be in a group polled by an NMS. Specifically, this is
the Community String for SNMP GETs. SNMP SETs are not supported. The agents will only answer an NMS retrieval
request if the NMS knows the Community String.
The Community String for Trap Targets allows an NMS functioning as a trap receiver to filter for desired traps. Trap
receivers receive all traps sent and it is up to this NMS to filter on the Community String. A trap receiver may choose to
ignore the Community String.
Pivot3 MIB
SNMP uses management information bases (MIBs) to define the variables an SNMP managed system offers. A Pivot3 MIB
has been defined to describe each object identifier used for alerts and status for Pivot3 storage. The Pivot3 MIB is
contained within the file PIVOT3SYS-MIB.txt which may be found on the “Pivot3 Software & Documentation Disc” in the
SNMP Support folder.
The SNMP MIB hierarchy is a tree with levels defined by different organizations. When importing a MIB file into a
management software application, the MIB details will exist within that hierarchy. The Pivot3 MIB will be imported into the
enterprises class of the MIB tree. MIB-II is also supported.
For accelerated nodes, two more MIB files are used: UCD-SNMP-MIB.txt and UCD-DISKIO-MIB.txt. These usually already
exist in a standard MIB set of files and, if not, can be found by searching for those file names on the Internet.
To Next Page
Loading...