4RF Aprisa SR+, Руководство пользователя

Страница: 238 / 492

238 | Managing the Radio
Aprisa SR+ User Manual 1.11.1
SNMPv3/2c Context Addressing
This ‘SNMP Context Addressing’ technique is an implementation that compresses and utilizes a more
efficient mechanism of managing communications with 4RF radios over the air within the same radio
network.
SNMPv3 is not user configurable and user can use this option with any NMS. The radio SNMP management
interface supports SNMPv3/2c context addressing. The SNMv3 context addressing allows the user to use
secure SNMPv3 management while improving NMS performance.
A NMS (Network Management System) can access any remote radio directly by using its IP address or via the
base station SNMPv3 context addressing. The SNMPv3 context addressing can compress the SNMPv3
management traffic OTA (Over The Air) to the remote radio by up to 90% relative to direct OTA SNMPv3
access to remote radio, avoiding the radio narrow bandwidth traffic loading.
To use Context Addressing to communicate with a remote radio:
•
Address the SNMP transaction to the base station i.e., use the base station’s IP address. If the base
station is a protected station, target the IP address of the active radio, since targeting the standby radio
will slow down the SNMP request and response as the active radio processes the context addressing
messages.
•
In the SNMP Context Name / Community String, use a string in the format of
e.g.,
‘public.runit_172.10.1.15’.
o
The ‘public’ portion is the actual community string that is required for the SNMP transaction
o
The ‘.’ is required to separate the remaining portion of the string
o
The ‘runit_’ portion i s to indicate that a remote radio registered to the base station is being
addressed
o
and the ‘ 172.10.1.15 ’ portion is the actual IP address of the remote radio
In this example, when the SNMP transaction is received by the base station, it is redirected to the specified
remote radio using the SNMP context addressing protocol of communications. The response to the original
SNMP transaction that was directed to the base station will contain the necessary information from the
remote radio and will be in a standard format
– appearing as a normal SNMP transaction response.
net-snmp command examples (where ‘ SNMP Protocol=All Version ’ at 'Supervisor > Security > Setup' page):
Example 1: Getting the Terminal Name (APRISASR-MIB: termName) - 1.3.6.1.4.1.14817.7.4.1.1.1.1.1.0 from
a remote radio IP address 10.30.56.81 via Base station IP address 10.30.56.80.
snmpget – v2c – c public.runit_10.30.56.81 10.30.56.80 1.3.6.1.4.1.14817.7.4.1.1.1.1.1.0
Example 2: Getting the TX Power (RFCONFIG-MIB: rfConfigPowerOutputSet) - 1.3.6.1.4.1.14817.3.14.2.30.0
snmpget – v2c – c public.runit_10.30.56.81 10.30.56.80 1.3.6.1.4.1.14817.3.14.2.30.0
Example 3: Reading the IP address
snmpget -v2c -c "public.runit_172.17.70.32" 172.17.70.31 1.3.6.1.4.1.14817.7.4.1.1.4.1.1.0
Example 4 : Reading the IP address using SNMPv3
snmpget -v3 -u privUserSHA -n "priv.runit_172.17.70.32" -l authPriv -a SHA -A privUserSHA -x AES -X
privUserSHA 172.17.70.31 1.3.6.1.4.1.14817.7.4.1.1.4.1.1.0
Example 5: SNMPWALK
snmpwalk -v2c -c public.runit_10.30.56.81 10.30.56.80 1.3.6.1.4.1.14817.7