Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsNTPPeerPMode",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"unspecified",
"(",
"0",
")",
",",
"symmetricActive",
"(",
"1",
")",
",",
"symmetricPassive",
"(",
"2",
")",
",",
"client",
"(",
"3",
")",
",",
"server",
"(",
"4",
")",
",",
"broadcast",
"(",
"5",
")",
",",
"reservedControl",
"(",
"6",
")",
",",
"reservedPrivate",
"(",
"7",
")",
",",
"broadcastclient",
"(",
"8",
")",
",",
"multicastclient",
"(",
"9",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"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'.\"",
"::=",
"{",
"fsNTPPeerEntry",
"32",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"unspecified",
0
],
[
"symmetricActive",
1
],
[
"symmetricPassive",
2
],
[
"client",
3
],
[
"server",
4
],
[
"broadcast",
5
],
[
"reservedControl",
6
],
[
"reservedPrivate",
7
],
[
"broadcastclient",
8
],
[
"multicastclient",
9
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"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'."
],
null,
null,
null,
null
]
}