10.10.3  
SNMP Data 
 


Settings | Network | SNMP Data
 
SNMP Data is used to enter the data for the default MIB´s. This information can then be sent to the management station per MIB read (GET).

10.10.3.1  
Area: System identification 
Enter the data for the default MIB "RFC 1213" (MIB-2) here. This information can then be sent to the management station per MIB read (GET). There are no restrictions on the content of the entries, which are used simply to identify the communication system better to an SNMP management station.

Contact person  
Enter the name of the person who is responsible for technical issues of the communication system.

System name  
Enter the name of the communication system. Usually, the domain name is entered in the SNMP world.

Location  
Description of the communication system´s location.

10.10.3.2  
Trap Flags table 
For every type of error that can be signaled via SNMP error message (trap), you can set whether only one entry is made in the event log or whether a trap is also initiated.

Error class  
Displays the class of the (Class B) error.  
Error no.  
Displays the (Class B) error number.
Meaning  
This column describes the error in plain text.
Value  
This column can be edited, and it determines what should happen when a Class B error occurs in the communication system:
   -   Log = The error is saved only in the error history, which can be read per maintenance.
   -   Log+trap = The error is saved in the error history and is also sent as an SNMP error message (trap).
   -   Log+multiple trap = The error is saved in the error history and is sent multiple times as an SNMP error message (trap).

10.10.3.3  
Area: Multiple Trap 
If error events are configured for Log+multiple trap in the Trap Flags table, then these errors are signaled multiple times per SNMP trap when a corresponding error event occurs. The number of times a trap is signaled is specified in Multiple Trap.

10.10.3.4  
Area: SNMP Flags 

Enable SNMP  
This option activates the SNMP (Simple Network Management Protocol) of the communication system.

CDR Notification Traps  
This option is used to generate a trap for CDR applications when the call charge output stack exceeds a threshold value. Please note, however, that this applies only to CDR applications that read the call charge stack via TFTP

Port Status Notification Traps  
This option causes a trap to be generated whenever a change in the hardware occurs (e.g., when cards/telephones are plugged or unplugged). These traps are evaluated by the HiPath FM to update the hardware tables.

See also:  
   -   Section 10.10 "Settings | Network"
   -   HiPath 3000/5000 Feature Description, LAN Network

HiPath 3000/5000 V9, Manager E, Administrator Documentation, Issue 10   up Top
Disclaimer & Copyright   ID: P31003H3590M1000176A9   2014-03-03