Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"saNetPTPSyncInterval",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"sec-1",
"(",
"1",
")",
",",
"sec-2",
"(",
"2",
")",
",",
"sec-8",
"(",
"8",
")",
",",
"sec-16",
"(",
"16",
")",
",",
"sec-64",
"(",
"64",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"The sync interval shall be the interval in seconds between successive Sync messages issued by master clocks. It shall have the same value for all clocks in a subdomain. The value of sync interval is a compromise between the inherent stability of the clocks, the responsiveness of the clocks in a subdomain to change, and the communication load imposed by PTP. Allowed values are 1,2,8,16 and 64. Changes are applied after the initialization with the init key init-with-nvm or after reboot if the configuration was saved.\"",
"::=",
"{",
"saNetPTPConfiguration",
"12",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"sec-1",
1
],
[
"sec-2",
2
],
[
"sec-8",
8
],
[
"sec-16",
16
],
[
"sec-64",
64
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"The sync interval shall be the interval in seconds between successive Sync messages issued by master clocks. It shall have the same value for all clocks in a subdomain. The value of sync interval is a compromise between the inherent stability of the clocks, the responsiveness of the clocks in a subdomain to change, and the communication load imposed by PTP. Allowed values are 1,2,8,16 and 64. Changes are applied after the initialization with the init key init-with-nvm or after reboot if the configuration was saved."
],
null,
null,
null,
null
]
}