All MIBs › ZXR10-NTP-MIB › zxr10ntpCurSrvRsltPriority
zxr10ntpCurSrvRsltPriority
Module: ZXR10-NTP-MIB
OID (symbolic): ZXR10-NTP-MIB::zxr10ntpCurSrvRsltPriority
OID (numeric): 1.3.6.1.4.1.3902.3.110.19.4
Node type: OBJECT-TYPE
Type: Unsigned32
Access: read-only
Description: The NTP server priority,the min number with high priority.The value of 0 is invalid value.
What is zxr10ntpCurSrvRsltPriority?
The priority of the NTP server the device is currently synchronized against (lower is higher priority); a value of 0 is explicitly called out as invalid, so it shouldn't appear for an actively-used server.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3902.3.110.19.4 snmpwalk -v2c -c public <target> ZXR10-NTP-MIB::zxr10ntpCurSrvRsltPriority
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.3902.3.110.19.4.1 snmpget -v2c -c public <target> ZXR10-NTP-MIB::zxr10ntpCurSrvRsltPriority.1
Start monitoring ZTE ZXR10 carrier routers/switches (NTP sync-status/active-server/config status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ZXR10-NTP-MIB::zxr10ntpCurSrvRsltPriority OID value, configure state conditions and alerts, and monitor any ZTE ZXR10 carrier routers/switches (NTP sync-status/active-server/config status) from a single console.
OID Breakdown
Upper-level ancestors (8 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.3902 | zte | UAS-MIB |
| 1.3.6.1.4.1.3902.3 | zxr10 | ZXR10-BFD-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.3902.3.110 | zxr10ntp | ZXR10-NTP-MIB |
| 1.3.6.1.4.1.3902.3.110.19 | zxr10ntpCurSrvRsltInfo | ZXR10-NTP-MIB |
| 1.3.6.1.4.1.3902.3.110.19.4 | zxr10ntpCurSrvRsltPriority | ZXR10-NTP-MIB |