Configuring SNMP for OVOC Connectivity
Connection between the device and OVOC is through SNMP. Once connected, the device can send SNMP traps to OVOC, and OVOC can perform various operations on the device such as maintenance actions, and fault and performance management.
|
●
|
Make sure that the SNMP settings on the device and on OVOC are identical.
|
|
●
|
OVOC uses the following default settings:
|
|
✔
|
SNMPv2: public for the read-community string, private for read-write community string, and trapuser for the trap community string. |
|
✔
|
SNMPv3: OVOCUser for user name; SHA-1 for authentication protocol; AES-128 for privacy protocol; 123456789 for the 'Authentication Key' and 'Privacy Key' password. |
|
●
|
If the device is located behind NAT and you have added it to OVOC by serial number or by auto-detection, you also need to configure (through ini file) the device to send NAT keep-alive traps to the OVOC port to keep the NAT pinhole open for SNMP messages sent from OVOC to the device: |
|
✔
|
[SendKeepAliveTrap] = [1] |
|
✔
|
[KeepAliveTrapPort] = [1161] |
|
✔
|
[NatBindingDefaultTimeout] = [30] |
|
➢
|
To configure SNMP for device-OVOC connectivity: |
|
3.
|
Configure an SNMPv2 or SNMPv3 user: |
|
5.
|
If the device is located behind NAT and you have added the device to OVOC by its serial number or using auto-detection, you also need to configure (through ini file) the device to send NAT keep-alive traps to the OVOC port to keep the NAT pinhole open for SNMP messages sent from OVOC to the device:
|
|
a.
|
Enable the sending of NAT keep-alive traps to OVOC, by configuring the [SendKeepAliveTrap] parameter to [1]. |
|
b.
|
Define the OVOC port to where the device sends the NAT keep-alive traps, by using the [KeepAliveTrapPort] parameter. |
|
c.
|
Define the interval between each sent NAT keep-alive trap, by using the [NatBindingDefaultTimeout] parameter. |
|
6.
|
Restart the device with a save-to-flash for your settings to take effect.
|