Status in source: current.
Names: rcNtpPeersVarEntry
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rcNtpPeersVarEntry",
"OBJECT-TYPE",
"SYNTAX",
"RcNtpPeersVarEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"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: rcNtpPeersPeerAddress, rcNtpPeersHostAddress and rcNtpPeersMode and making the rcNtpPeersEntryStatus as active(1). At the least, the management station has to set a value for rcNtpPeersPeerAddress to make the row active.\"",
"INDEX",
"{",
"rcNtpPeersAssocId",
"}",
"::=",
"{",
"rcNtpPeersVarTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"RcNtpPeersVarEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"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: rcNtpPeersPeerAddress, rcNtpPeersHostAddress and rcNtpPeersMode and making the rcNtpPeersEntryStatus as active(1). At the least, the management station has to set a value for rcNtpPeersPeerAddress to make the row active."
],
null,
null,
[
"INDEX",
[
[
0,
"rcNtpPeersAssocId"
]
]
],
null
]
}