HUAWEI-NTP-MIB

File: HUAWEI-NTP-MIB.mib (35943 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC HUAWEI-3COM-OID-MIB

Imported symbols

IpAddress Integer32 MODULE-IDENTITY
OBJECT-TYPE Counter32 Unsigned32
RowStatus TruthValue huaweiDatacomm

Defined Types

NTPPeerEntry  
SEQUENCE    
  hwNTPPeerConfig TruthValue
  hwNTPPeerAuthenable TruthValue
  hwNTPPeerAuthentic TruthValue
  hwNTPPeerRemAdr IpAddress
  hwNTPPeerRemPort Integer32
  hwNTPPeerLocAdr IpAddress
  hwNTPPeerLocPort Integer32
  hwNTPPeerLeap INTEGER
  hwNTPPeerHMode INTEGER
  hwNTPPeerStratum Integer32
  hwNTPPeerPPoll Integer32
  hwNTPPeerHPoll Integer32
  hwNTPPeerPrecision Integer32
  hwNTPPeerRootDelay OCTET STRING
  hwNTPPeerRootDispersion OCTET STRING
  hwNTPPeerRefId OCTET STRING
  hwNTPPeerRefTime OCTET STRING
  hwNTPPeerOrg OCTET STRING
  hwNTPPeerRec OCTET STRING
  hwNTPPeerXmt OCTET STRING
  hwNTPPeerReach Integer32
  hwNTPPeerValid Integer32
  hwNTPPeerTimer Integer32
  hwNTPPeerDelay OCTET STRING
  hwNTPPeerOffset OCTET STRING
  hwNTPPeerJitter OCTET STRING
  hwNTPPeerDispersion OCTET STRING
  hwNTPPeerKeyId Unsigned32
  hwNTPPeerFiltDelay OCTET STRING
  hwNTPPeerFiltOffset OCTET STRING
  hwNTPPeerFiltError OCTET STRING
  hwNTPPeerPMode INTEGER
  hwNTPPeerReceived Counter32
  hwNTPPeerSent Counter32
  hwNTPPeerFlash BITS
  hwNTPPeerRowStatus RowStatus

Defined Values

hwNTP 1.3.6.1.4.1.2011.5.25.22
This MIB provides mechanisms to monitor a NTP server.
MODULE-IDENTITY    

hwNTPSystemMIB 1.3.6.1.4.1.2011.5.25.22.1
OBJECT IDENTIFIER    

hwNTPSystemMIBObjects 1.3.6.1.4.1.2011.5.25.22.1.1
OBJECT IDENTIFIER    

hwNTPSysLeap 1.3.6.1.4.1.2011.5.25.22.1.1.1
Leap Indicator (LI): This is a two-bit code warning of an impending leap second to be inserted/deleted in the last minute of the current day, with bit 0 and bit 1, respectively, coded as follows: 00, no warning 01, last minute has 61 seconds 10, last minute has 59 seconds) 11, alarm condition (clock not synchronized).
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER noWarning(0), addSecond(1), subtractSecond(2), alarm(3)  

hwNTPSysStratum 1.3.6.1.4.1.2011.5.25.22.1.1.2
This is an eight-bit integer indicating the stratum level of the local clock, with values defined as follows: 0, unspecified 1, primary reference (e.g.,, radio clock) 2-255, secondary reference (via NTP)
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 1..16  

hwNTPSysPrecision 1.3.6.1.4.1.2011.5.25.22.1.1.3
Precision : This is a signed integer indicating the precision of the various clocks, in seconds to the nearest power of two. The value must be rounded to the next larger power of two; for instance, a 50-Hz (20 ms) or 60-Hz (16.67ms) power-frequency clock would be assigned the value -5 (31.25 ms), while a 1000-Hz (1 ms) crystal-controlled clock would be assigned the value -9 (1.95 ms).
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 -20..20  

hwNTPSysRootdelay 1.3.6.1.4.1.2011.5.25.22.1.1.4
Root Delay : This is a signed fixed-point number indicating the total roundtrip delay to the primary reference source at the root of the synchronization subnet, in milliseconds. Note that this variable can take on both positive and negative values, depending on clock precision and skew.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPSysRootdispersion 1.3.6.1.4.1.2011.5.25.22.1.1.5
Root Dispersion : This is a signed fixed-point number indicating the maximum error relative to the primary reference source at the root of the synchronization subnet, in milliseconds. Only positive values greater than zero are possible.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPSysRefid 1.3.6.1.4.1.2011.5.25.22.1.1.6
Reference Clock Identifier : This is a 32-bit code identifying the particular reference clock. In the case of stratum 0 (unspecified) or stratum 1 (primary reference source), this is a four-octet, left-justified, zero-padded ASCII string. Stratum, Code, Meaning 0, DCN, DCN routing protocol 0, TSP, TSP time protocol 1, ATOM, Atomic clock (calibrated) 1, WWVB, WWVB LF (band 5) radio 1, GOES, GOES UHF (band 9) satellite 1, WWV, WWV HF (band 7) radio
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPSysReftime 1.3.6.1.4.1.2011.5.25.22.1.1.7
Reference Timestamp : This is the local time, in timestamp format, when the local clock was last updated. If the local clock has never been synchronized, the value is zero.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPSysPoll 1.3.6.1.4.1.2011.5.25.22.1.1.8
Poll Interval : This is a signed integer indicating the minimum interval between transmitted messages, in seconds as a power of two. For instance, a value of six indicates a minimum interval of 64 seconds.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 -20..20  

hwNTPSysPeer 1.3.6.1.4.1.2011.5.25.22.1.1.9
This is a selector identifying the current synchronization source. Usually this will be a pointer to a structure containing the peer variables. The special value NULL indicates There is no currently valid synchronization source.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..2147483647  

hwNTPSysState 1.3.6.1.4.1.2011.5.25.22.1.1.10
This is a integer indicating the state of local clock.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER noUpdateClock(0), getfreqInfo(1), clockBySet(2), clockBySetAndNoFreq(3), clockBySyns(4), findError(5)  

hwNTPSysOffset 1.3.6.1.4.1.2011.5.25.22.1.1.11
The offset of two clocks is the time difference between them, in milliseconds.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPSysDrift 1.3.6.1.4.1.2011.5.25.22.1.1.12
Real clocks exhibit some variation in skew (second derivative of offset with time), which is called drift.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPSysCompliance 1.3.6.1.4.1.2011.5.25.22.1.1.13
This is a string indicating the system error.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPSysClock 1.3.6.1.4.1.2011.5.25.22.1.1.14
This is the current local time, in timestamp format. Local time is derived from the hardware clock of the particular machine and increments at intervals depending on the design used.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPSysStabil 1.3.6.1.4.1.2011.5.25.22.1.1.15
This is a indicating that stability of a clock is how well it can maintain a constant frequency.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPSysAuthenticate 1.3.6.1.4.1.2011.5.25.22.1.1.16
This is a integer indicating that system support authentication.
Status: current Access: read-write
OBJECT-TYPE    
  INTEGER noAuthenticate(0), authenticate(1)  

hwNTPSysPollSec 1.3.6.1.4.1.2011.5.25.22.1.1.17
PollSec Interval : This is a integer indicating the minimum interval between transmitted messages. For instance, a value of six indicates a minimum interval of 6 seconds.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32 2..1048576  

hwNTPSysClockSec 1.3.6.1.4.1.2011.5.25.22.1.1.18
This is the current local time, in integer format. Local time is derived from the hardware clock of the particular machine and increments at intervals depending on the design used.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

hwNTPServerIP 1.3.6.1.4.1.2011.5.25.22.1.1.19
The NTP server ip address. It must be a unicast address, rather than a broadcast address, a multicast address or the IP address of the local clock. To delete a configured NTP server ip address, please set hwNTPServerIP to 0.
Status: current Access: read-write
OBJECT-TYPE    
  IpAddress  

hwNTPPeerMIB 1.3.6.1.4.1.2011.5.25.22.2
OBJECT IDENTIFIER    

hwNTPPeerMIBObjects 1.3.6.1.4.1.2011.5.25.22.2.1
OBJECT IDENTIFIER    

hwNTPPeerTable 1.3.6.1.4.1.2011.5.25.22.2.1.1
This table provides information on the peers with which the local NTP server has associations. The peers are also NTP servers but running on different hosts.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    NTPPeerEntry

hwNTPPeerEntry 1.3.6.1.4.1.2011.5.25.22.2.1.1.1
Each peers' entry provides NTP information retrieved from a particular peer NTP server. Each peer is identified by a unique association identifier. Entries are automatically created when the user configures the NTP server to be associated with remote peers. Similarly entries are deleted when the user removes the peer association from the NTP server. Entries can also be created by the management station by setting values for the following objects: hwNTPPeerRemAdr and making the hwNTPPeerRowStatus as 'active'. At the least, the management station has to set a value for hwNTPPeerRemAdr to make the row active.
Status: current Access: not-accessible
OBJECT-TYPE    
  NTPPeerEntry  

hwNTPPeerConfig 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.1
This is a bit indicating that the association was created from configuration information and should not be demobilized if the peer becomes unreachable.
Status: current Access: read-only
OBJECT-TYPE    
  TruthValue  

hwNTPPeerAuthenable 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.2
This is a bit indicating that system support authentication.
Status: current Access: read-only
OBJECT-TYPE    
  TruthValue  

hwNTPPeerAuthentic 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.3
This is a bit indicating that massage pass authentication which is authentic.
Status: current Access: read-only
OBJECT-TYPE    
  TruthValue  

hwNTPPeerRemAdr 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.4
The IP address of the peer. When creating a new association, a value for this object should be set before the row is made active.
Status: current Access: not-accessible
OBJECT-TYPE    
  IpAddress  

hwNTPPeerRemPort 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.5
The UDP port number on which the peer receives NTP messages.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 1..65535  

hwNTPPeerLocAdr 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.6
The IP address of the local host. Multi-homing can be supported using this object.
Status: current Access: read-only
OBJECT-TYPE    
  IpAddress  

hwNTPPeerLocPort 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.7
The UDP port number on which the local host receives NTP messages.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 1..65535  

hwNTPPeerLeap 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.8
This is a two-bit code warning of an impending leap second to be inserted in the NTP timescale. The bits are set before 23:59 on the day of insertion and reset after 00:00 on the following day. This causes the number of seconds (rollover interval) in the day of insertion to be increased or decreased by one. The two bits are coded as below, 00, no warning 01, last minute has 61 seconds 10, last minute has 59 seconds 11, alarm condition (clock not synchronized)
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER noWarning(0), addSecond(1), subtractSecond(2), alarm(3)  

hwNTPPeerHMode 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.9
This is an integer indicating the association mode, with values coded as follows, 0, unspecified 1, symmetric active - A host operating in this mode sends periodic messages regardless of the reach ability state or stratum of its peer. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer 2, symmetric passive - This type of association is ordinarily created upon arrival of a message from a peer operating in the symmetric active mode and persists only as long as the peer is reachable and operating at a stratum level less than or equal to the host; otherwise, the association is dissolved. However, the association will always persist until at least one message has been sent in reply. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer 3, client - A host operating in this mode sends periodic messages regardless of the reach ability state or stratum of its peer. By operating in this mode the host, usually a LAN workstation, announces its willingness to be synchronized by, but not to synchronize the peer 4, server - This type of association is ordinarily created upon arrival of a client request message and exists only in order to reply to that request, after which the association is dissolved. By operating in this mode the host, usually a LAN time server, announces its willingness to synchronize, but not to be synchronized by the peer 5, broadcast - A host operating in this mode sends periodic messages regardless of the reach ability state or stratum of the peers. By operating in this mode the host, usually a LAN time server operating on a high-speed broadcast medium, announces its willingness to synchronize all of the peers, but not to be synchronized by any of them 6, reserved for NTP control messages 7, reserved for private use 8, broadcastclient 9, multicastclient
Status: current Access: not-accessible
OBJECT-TYPE    
  INTEGER unspecified(0), symmetricActive(1), symmetricPassive(2), client(3), server(4), broadcast(5), reservedControl(6), reservedPrivate(7), broadcastclient(8), multicastclient(9)  

hwNTPPeerStratum 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.10
This is a integer indicating the stratum level of the local clock, with values defined as follows: 0, unspecified 1, primary reference (e.g.,, radio clock) 2-255, secondary reference (via NTP)
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..255  

hwNTPPeerPPoll 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.11
The interval at which the peer polls the local host.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 -20..20  

hwNTPPeerHPoll 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.12
The interval at which the local host polls the peer.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 -20..20  

hwNTPPeerPrecision 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.13
This is a signed integer indicating the precision of the peer clock, in seconds to the nearest power of two. The value must be rounded to the next larger power of two; for instance, a 50-Hz (20 ms) or 60-Hz (16.67 ms) power-frequency clock would be assigned the value -5 (31.25 ms), while a 1000-Hz (1 ms) crystal-controlled clock would be assigned the value -9 (1.95 ms).
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 -20..20  

hwNTPPeerRootDelay 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.14
This is a signed fixed-point number indicating the total roundtrip delay to the primary reference source at the root of the synchronization subnet, in milliseconds. Note that this variable can take on both positive and negative values, depending on clock precision and skew.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPPeerRootDispersion 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.15
This is a signed fixed-point number indicating the maximum error of the peer clock relative to the primary reference source at the root of the synchronization subnet, in milliseconds. Only positive values greater than zero are possible.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPPeerRefId 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.16
The reference identifier of the peer. This is a 32-bit code identifying the particular reference clock. In the case of stratum 0 (unspecified) or stratum 1 (primary reference source), this is a four-octet, left-justified, zero-padded ASCII string. Stratum, Code, Meaning 0, DCN, DCN routing protocol 0, TSP, TSP time protocol 1, ATOM, Atomic clock (calibrated) 1, WWVB, WWVB LF (band 5) radio 1, GOES, GOES UHF (band 9) satellite 1, WWV, WWV HF (band 7) radio
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPPeerRefTime 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.17
This is the local time at the peer, in timestamp format, when the local clock was last updated. If the local clock has never been synchronized, the value is zero.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPPeerOrg 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.18
This is the local time, in timestamp format, at the peer when it's latest NTP message was sent. If the peer becomes unreachable the value is set to zero
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPPeerRec 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.19
This is the local time, in timestamp format, when the latest NTP message from the peer arrived. If the peer becomes unreachable the value is set to zero.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPPeerXmt 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.20
This is the local time, in timestamp format, at which the NTP message departed the sender.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPPeerReach 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.21
This is a shift register of NTP.WINDOW bits used to determine the reach ability status of the peer, with bits entering from the least significant (rightmost) end. A peer is considered reachable if at least one bit in this register is set to one
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..2147483647  

hwNTPPeerValid 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.22
This is an integer counter indicating the valid samples remaining in the filter register. It is used to determine the reach ability state and when the poll interval should be increased or decreased.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..255  

hwNTPPeerTimer 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.23
This is an integer counter used to control the interval of transmitted NTP messages from the local host to the peer.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..2147483647  

hwNTPPeerDelay 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.24
This is a signed fixed-point number indicating the roundtrip delay of the peer clock relative to the local clock over the network path between them, in milliseconds. Note that this variable can take on both positive and negative values, depending on clock precision and skew-error accumulation.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPPeerOffset 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.25
This is a signed, fixed-point number indicating the offset of the peer clock relative to the local clock, in milliseconds.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPPeerJitter 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.26
This is an indicating that peer of sample Variance
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPPeerDispersion 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.27
This is a signed fixed-point number indicating the maximum error of the peer clock relative to the local clock over the network path between them, in milliseconds. Only positive values greater than zero are possible.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPPeerKeyId 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.28
This is an unsigned integer identifying the cryptographic key used to generate the message-authentication code.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32 0..4294967295  

hwNTPPeerFiltDelay 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.29
Round-trip delay of the peer clock relative to the local clock over the network path between them, in milliseconds. This variable can take on both positive and negative values, depending on clock precision and skew-error accumulation.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPPeerFiltOffset 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.30
The offset of the peer clock relative to the local clock in milliseconds.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPPeerFiltError 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.31
The maximum error of the peer clock relative to the local clock over the network path between them, in milliseconds. Only positive values greater than zero are possible.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..128)  

hwNTPPeerPMode 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.32
This is an integer indicating the association mode, with values coded as follows, 0, unspecified 1, symmetric active - A host operating in this mode sends periodic messages regardless of the reach ability state or stratum of its peer. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer 2, symmetric passive - This type of association is ordinarily created upon arrival of a message from a peer operating in the symmetric active mode and persists only as long as the peer is reachable and operating at a stratum level less than or equal to the host; otherwise, the association is dissolved. However, the association will always persist until at least one message has been sent in reply. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer 3, client - A host operating in this mode sends periodic messages regardless of the reach ability state or stratum of its peer. By operating in this mode the host, usually a LAN workstation, announces its willingness to be synchronized by, but not to synchronize the peer 4, server - This type of association is ordinarily created upon arrival of a client request message and exists only in order to reply to that request, after which the association is dissolved. By operating in this mode the host, usually a LAN time server, announces its willingness to synchronize, but not to be synchronized by the peer 5, broadcast - A host operating in this mode sends periodic messages regardless of the reach ability state or stratum of the peers. By operating in this mode the host, usually a LAN time server operating on a high-speed broadcast medium, announces its willingness to synchronize all of the peers, but not to be synchronized by any of them 6, reserved for NTP control messages 7, reserved for private use 8, broadcastclient 9, multicastclient When creating a new peer association, if no value is specified for this object, it defaults to 'symmetricActive'.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER unspecified(0), symmetricActive(1), symmetricPassive(2), client(3), server(4), broadcast(5), reservedControl(6), reservedPrivate(7), broadcastclient(8), multicastclient(9)  

hwNTPPeerReceived 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.33
The number of received massages.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

hwNTPPeerSent 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.34
The number of send massages.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

hwNTPPeerFlash 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.35
The information about the massage.
Status: current Access: read-only
OBJECT-TYPE    
  BITS recvRepeatMsg(0), recvremanMsg(1), unSynMsg(2), dispBeyond(3), unauthenticate(4), unSynClock(5), straBeyond(6), rootDispBeyond(7), noAuthen(8), refuOperate(9)  

hwNTPPeerRowStatus 1.3.6.1.4.1.2011.5.25.22.2.1.1.1.36
The status object for this row. When a management station is creating a new row, it should set the value for cntpPeersPeerAddress at least, before the row can be made 'active'.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus