Comtech EF Data VMS v3.12.x Vipersat - Manual (Page 511)

Appendix F - Northbound Interface F-13
MN/22156, rev 12 Operational Procedures
The second Hub associated (switched) demodulator is known in the VMS
switching engine, and is thus a cached value. To retrieve this information
requires some finesse, as the association is not as straight forward as the Eb/No.
The allocated device must first be learned through a series of steps and, once the
association is known, the internal value can be polled.
Steps to Identify Device
1. Set Read Community string “public@IP Address” to the modulator device in
question.
2. Query “modulatorId” OID to learn the entity identifier “moniker”
ves:cdm840-172.18.100.1,1,0
3. Copy the moniker or octet string into the Read Community.
4. Next, query the “deviceAllocationAllocatedDeviceId” OID to identify the
associated demodulator, ves:cdd880-192.168.150.212,2,0.
Note the device # in the octet string (shown in red below).
This is the instance that is part of the query:
ves:cdd880-192.168.150.212, 2 ,0
5. Write the learned demodulator IP Address (example, 192.168.150.212) into
the Read Community.
6. Query the modem’s MIB “cdd880RxFrequencyOffset” with an instance
from the learned (example #2) octet string.
Figure F-9 Results of Learned Association