Configuring NTP
he Network Time Protocol (NTP) synchronizes the time of day among a set of distributed time servers and clients so that you can correlate time-specific information, such as system logs, received from the devices in your network.
This section contains payload examples and CLIs to demonstrate how to use the NX-API REST API to configure NTP on Cisco Nexus 3000 and 9000 Series switches and to show how the REST APIs correspond to the CLI commands.
For more information, see the Cisco Nexus 9000 Series NX-OS System Management Configuration Guide.
Enabling NTP
Enabling NTP
POST http://<IP_Address>/api/mo/sys/fm.json
{
"fmEntity": {
"children": [
{
"fmNtpd": {
"attributes": {
"adminSt": "enabled"
}}}]}}
<System>
<fm-items>
<ntpd-items>
<adminSt>enabled</adminSt>
</ntpd-items>
</fm-items>
</System>
This example enables the NTP feature.
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right.
feature ntp
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
fmEntity | sys/fm |
fmNtpd | sys/fm/ntpd |
fmNtpd Properties
The following table contains information about the fmNtpd properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
adminSt | fm:AdminState (scalar:Enum8) | Admin status | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Disabling NTP
Disabling NTP
POST http://<IP_Address>/api/mo/sys/fm.json
{
"fmEntity": {
"children": [
{
"fmNtpd": {
"attributes": {
"status": "deleted"
}}}]}}
<System>
<fm-items>
<ntpd-items xc:operation="delete">
</ntpd-items>
</fm-items>
</System>
This example disables the NTP feature.
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right.
no feature ntp
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
fmEntity | sys/fm |
fmNtpd | sys/fm/ntpd |
fmNtpd Properties
The following table contains information about the fmNtpd properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring General NTP Settings
Configuring General NTP Settings
POST http://<IP_Address>/api/mo/sys/time.json
{
"datetimeClkPol": {
"attributes": {
"authSt": "enabled",
"logging": "enabled",
"loggingLevel": "critical",
"master": "enabled",
"masterStratum": "8"
},
"children": [
{
"datetimeNtpAuth": {
"attributes": {
"id": "123",
"isEncrypt": "no",
"key": "MD5_String"
}}}]}}
<System>
<time-items>
<authSt>enabled</authSt>
<logging>enabled</logging>
<loggingLevel>critical</loggingLevel>
<master>enabled</master>
<masterStratum>8</masterStratum>
<auth-items>
<NtpAuth-list>
<id>123</id>
<isEncrypt>false</isEncrypt>
<key>MD5_String</key>
</NtpAuth-list>
</auth-items>
</time-items>
</System>
This example enables NTP authentication and logging.
CLI Commands
The CLI commands and options listed below are used to create the payload example displayed in the pane on the right.
logging level ntp 2
ntp authenticate
ntp authentication-key 123 md5 MD5_String
ntp logging
ntp master 8
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeNtpAuth | sys/time/auth-{id} |
datetimeClkPol Properties
The following table contains information about the datetimeClkPol properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
authSt | datetime:AdminState (scalar:Enum8) | A property that indicates if the Datetime policy authentication is enabled or disabled. | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
logging | datetime:AdminState (scalar:Enum8) | NTP Logging Status | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
loggingLevel | datetime:LoggingLevel (scalar:Enum8) | NTP Logging Level | SELECTION: 0 - emergency 1 - alert 2 - critical 3 - error 4 - warning 5 - notif 6 - inform 7 - debug DEFAULT: critical |
master | datetime:AdminState (scalar:Enum8) | NTP Master Configuration | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
masterStratum | datetime:Stratum (scalar:UByte) | NTP Master Stratum Level | RANGE: [1 , 15] DEFAULT: 8 |
datetimeNtpAuth Properties
The following table contains information about the datetimeNtpAuth properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | datetime:AuthKeyId (scalar:Uint16) | The NTP key ID. | RANGE: [1 , 0xffff] DEFAULT: 1 |
isEncrypt | datetime:Encrypt (scalar:Bool) | Is Encrypted Flag | SELECTION: 0 - unspecified DEFAULT: unspecified |
key | datetime:Key (string:Basic) | The NTP authentication key. | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Disabling Configured NTP Settings
Disabling Configured NTP Settings
POST http://<IP_Address>/api/mo/sys/time.json
{
"datetimeClkPol": {
"attributes": {
"authSt": "disabled",
"logging": "disabled",
"loggingLevel": "critical",
"master": "disabled",
"masterStratum": "8"
},
"children": [
{
"datetimeNtpAuth": {
"attributes": {
"id": "123",
"isEncrypt": "no"
}}}]}}
<System>
<time-items>
<authSt>disabled</authSt>
<logging>disabled</logging>
<loggingLevel>critical</loggingLevel>
<master>disabled</master>
<masterStratum>8</masterStratum>
<auth-items>
<NtpAuth-list>
<id>123</id>
<isEncrypt>false</isEncrypt>
</NtpAuth-list>
</auth-items>
</time-items>
</System>
This example disables NTP authentication and logging.
CLI Commands
The CLI commands and options listed below are used to create the payload example displayed in the pane on the right.
no logging level ntp 2
no ntp authenticate
no ntp authentication-key 123 md5 MD5_String
no ntp logging
no ntp master 8
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeNtpAuth | sys/time/auth-{id} |
datetimeClkPol Properties
The following table contains information about the datetimeClkPol properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
authSt | datetime:AdminState (scalar:Enum8) | A property that indicates if the Datetime policy authentication is enabled or disabled. | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
logging | datetime:AdminState (scalar:Enum8) | NTP Logging Status | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
loggingLevel | datetime:LoggingLevel (scalar:Enum8) | NTP Logging Level | SELECTION: 0 - emergency 1 - alert 2 - critical 3 - error 4 - warning 5 - notif 6 - inform 7 - debug DEFAULT: critical |
master | datetime:AdminState (scalar:Enum8) | NTP Master Configuration | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
masterStratum | datetime:Stratum (scalar:UByte) | NTP Master Stratum Level | RANGE: [1 , 15] DEFAULT: 8 |
datetimeNtpAuth Properties
The following table contains information about the datetimeNtpAuth properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | datetime:AuthKeyId (scalar:Uint16) | The NTP key ID. | RANGE: [1 , 0xffff] DEFAULT: 1 |
isEncrypt | datetime:Encrypt (scalar:Bool) | Is Encrypted Flag | SELECTION: 0 - unspecified DEFAULT: unspecified |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring NTP Access Restrictions
Configuring NTP Access Restrictions
POST http://<IP_Address>/api/mo/sys/time.json
{
"datetimeClkPol": {
"children": [
{
"datetimeAccessGroup": {
"attributes": {
"peer": "ACL_1",
"queryOnly": "ACL_1234",
"serve": "ACL_12",
"serveOnly": "ACL_123"
}}}]}}
<System>
<time-items>
<accessgroup-items>
<peer>ACL_1</peer>
<queryOnly>ACL_1234</queryOnly>
<serve>ACL_12</serve>
<serveOnly>ACL_123</serveOnly>
</accessgroup-items>
</time-items>
</System>
The access group options are scanned in the following order, from least restrictive to most restrictive. However, if NTP matches a deny ACL rule in a configured peer, ACL processing stops and does not continue to the next access group option.
- The peer keyword enables the device to receive time requests and NTP control queries and to synchronize itself to the servers specified in the access list.
- The serve keyword enables the device to receive time requests and NTP control queries from the servers specified in the access list but not to synchronize itself to the specified servers.
- The serve-only keyword enables the device to receive only time requests from servers specified in the access list.
- The query-only keyword enables the device to receive only NTP control queries from the servers specified in the access list.
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right.
ntp access-group peer ACL_1
ntp access-group serve ACL_12
ntp access-group serve-only ACL_123
ntp access-group query-only ACL_1234
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeAccessGroup | sys/time/accessgroup |
datetimeAccessGroup Properties
The following table contains information about the datetimeAccessGroup properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
peer | string:Basic | NTP Peer Access Group Name (max 63 characters) | A sequence of characters |
queryOnly | string:Basic | NTP QueryOnly Access Group Name (max 63 characters) | A sequence of characters |
serve | string:Basic | NTP Serve Access Group Name (max 63 characters) | A sequence of characters |
serveOnly | string:Basic | NTP ServeOnly Access Group Name (max 63 characters) | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring NTP Authentication Key
Configuring NTP Authentication Key
POST http://<IP_Address>/api/mo/sys/time.json
{
"datetimeClkPol": {
"children": [
{
"datetimeNtpAuth": {
"attributes": {
"authType": "md5",
"encryptType": "type6",
"id": "11",
"isEncrypt": "yes",
"key": "JDYkxkkwpfVUBAiYzcKF6bPO\/CQU4QcNZ67DnYI5jahrfjUJJIZckxJRzBx\/+y\/cUneYwuK6enISAA=="
"isEncrypt": "yes"
}}}]}}
<System>
<time-items>
<auth-items>
<NtpAuth-list>
<id>5</id>
<isEncrypt>false</isEncrypt>
<key>asdf1234xyz</key>
<trusted>true</trusted>
</NtpAuth-list>
</auth-items>
</time-items>
</System>
This example configures a clear text trusted key as key number 5.
CLI Commands
The CLI commands and options listed below are used to create the payload example displayed in the pane on the right.
ntp authentication-key number {md5 | aes128mac} password string
ntp trusted-key 5
Note: The property information for this example was added in Release 10.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeNtpAuth | sys/time/auth-{id} |
datetimeNtpAuth Properties
The following table contains information about the datetimeNtpAuth properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | datetime:AuthKeyId (scalar:Uint16) | The NTP key ID. | RANGE: [1 , 0xffff] DEFAULT: 1 |
isEncrypt | datetime:Encrypt (scalar:Bool) | Is Encrypted Flag | SELECTION: 0 - unspecified DEFAULT: unspecified |
key | datetime:Key (string:Basic) | The NTP authentication key. | A sequence of characters |
trusted | scalar:Bool | A property that indicates if the NTP authentication is trusted. | SELECTION: true or false |
authType | string:Basic | Authentication type. | SELECTION: md5 aes128cmac |
encryptType | string:Basic | Encription type. | SELECTION: type 0 6 7 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Disabling NTP Authentication Key
Disabling NTP Authentication Key
POST http://<IP_Address>/api/mo/sys/time.json
{
"datetimeClkPol": {
"children": [
{
"datetimeNtpAuth": {
"attributes": {
"id": "5",
"isEncrypt": "no",
"trusted": "no"
}}}]}}
<System>
<time-items>
<auth-items>
<NtpAuth-list>
<id>5</id>
<isEncrypt>false</isEncrypt>
<trusted>false</trusted>
</NtpAuth-list>
</auth-items>
</time-items>
</System>
This example disables a clear text trusted key configured as key number 5.
CLI Commands
The CLI commands and options listed below are used to create the payload example displayed in the pane on the right.
no ntp authentication-key 5 md5 asdf1234xyz
no ntp trusted-key 5
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeNtpAuth | sys/time/auth-{id} |
datetimeNtpAuth Properties
The following table contains information about the datetimeNtpAuth properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
id | datetime:AuthKeyId (scalar:Uint16) | The NTP key ID. | RANGE: [1 , 0xffff] DEFAULT: 1 |
isEncrypt | datetime:Encrypt (scalar:Bool) | Is Encrypted Flag | SELECTION: 0 - unspecified DEFAULT: unspecified |
trusted | scalar:Bool | A property that indicates if the NTP authentication is trusted. | SELECTION: true or false |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring an NTP Server and Peer
Configuring an NTP Server and Peer
POST http://<IP_Address>/api/mo/sys/time.json
{
"datetimeClkPol": {
"children": [
{
"datetimeNtpProvider": {
"attributes": {
"keyId": "123",
"maxPoll": "4",
"minPoll": "4",
"name": "4.3.2.1",
"preferred": "yes",
"provT": "server",
"vrf": "VRF_1"
}}},{
"datetimeNtpProvider": {
"attributes": {
"keyId": "123",
"maxPoll": "4",
"minPoll": "4",
"name": "1.2.3.4",
"preferred": "yes",
"provT": "peer",
"vrf": "VRF_1"
}}}]}}
<System>
<time-items>
<prov-items>
<NtpProvider-list>
<name>4.3.2.1</name>
<keyId>123</keyId>
<maxPoll>4</maxPoll>
<minPoll>4</minPoll>
<preferred>true</preferred>
<provT>server</provT>
<vrf>VRF_1</vrf>
</NtpProvider-list>
<NtpProvider-list>
<name>1.2.3.4</name>
<keyId>123</keyId>
<maxPoll>4</maxPoll>
<minPoll>4</minPoll>
<preferred>true</preferred>
<provT>peer</provT>
<vrf>VRF_1</vrf>
</NtpProvider-list>
</prov-items>
</time-items>
</System>
This example forms an association with an NTP server.
CLI Commands
The CLI commands and options listed below are used to create the payload example displayed in the pane on the right.
ntp peer 1.2.3.4 key 123 maxpoll 4 minpoll 4 prefer use-vrf VRF_1
ntp server 4.3.2.1 key 123 maxpoll 4 minpoll 4 prefer use-vrf VRF_1
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeNtpProvider | sys/time/prov-{[name]} |
datetimeNtpProvider Properties
The following table contains information about the datetimeNtpProvider properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
keyId | datetime:KeyId (scalar:Uint16) | The NTP provider key ID. The range is from 1 to 65535. | RANGE: [1, 65535] |
maxPoll | datetime:Poll (scalar:UByte) | The NTP maximum interval default in seconds. | RANGE: [4 , 16] DEFAULT: 6 |
minPoll | datetime:Poll (scalar:UByte) | The NTP minimum interval default in seconds. | RANGE: [4 , 16] DEFAULT: 4 |
name | pol:ObjName (naming:Name256) | Object name | RANGE: [1 , 80] |
preferred | scalar:Bool | A property that indicates if the NTP server is preferred. Only one preferred server is allowed. | SELECTION: true or false |
provT | datetime:ProvT (scalar:Enum8) | NTP Server Or Peer | SELECTION: 0 - peer 1 - server 2 - invalid DEFAULT: invalid |
vrf | l3:VrfName (string:Basic) | Identifies the VRF for the NTP providers | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the NTP Source IP Address
Configuring the NTP Source IP Address
POST http://<IP_Address>/api/mo/sys/time.json
{
"datetimeClkPol": {
"children": [
{
"datetimeNtpSrcIp": {
"attributes": {
"srcIp": "1.2.3.4",
"srcIpv6": "0::0"
}}}]}}
<System>
<time-items>
<srcIp-items>
<srcIp>1.2.3.4</srcIp>
<srcIpv6>0::0</srcIpv6>
</srcIp-items>
</time-items>
</System>
This example sets the NTP source IP address to 1.2.3.4.
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right.
ntp source 1.2.3.4
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeNtpSrcIp | sys/time/srcIp |
datetimeNtpSrcIp Properties
The following table contains information about the datetimeNtpSrcIp properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
srcIp | address:IPv4 | Source IP Address | Value must match ipv4 format |
srcIpv6 | address:IPv6 | Source IPv6 Address | Value must match ipv6 format |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting a Configured NTP Source IP Address
Deleting a Configured NTP Source IP Address
POST http://<IP_Address>/api/mo/sys/time.json
{
"datetimeClkPol": {
"children": [
{
"datetimeNtpSrcIp": {
"attributes": {
"srcIp": "0.0.0.0"
}}}]}}
<System>
<time-items>
<srcIp-items>
<srcIp>0.0.0.0</srcIp>
</srcIp-items>
</time-items>
</System>
This example unsets the NTP source IP address that was set to 1.2.3.4.
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right.
no ntp source 1.2.3.4
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeNtpSrcIp | sys/time/srcIp |
datetimeNtpSrcIp Properties
The following table contains information about the datetimeNtpSrcIp properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
srcIp | address:IPv4 | Source IP Address | Value must match ipv4 format |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the NTP Source IP Address (Ipv6)
Configuring the NTP Source IP Address (Ipv6)
POST http://<IP_Address>/api/mo/sys/time.json
{
"datetimeClkPol": {
"children": [
{
"datetimeNtpSrcIp": {
"attributes": {
"srcIp": "0.0.0.0",
"srcIpv6": "1::2"
}}}]}}
<System>
<time-items>
<srcIp-items>
<srcIp>0.0.0.0</srcIp>
<srcIpv6>1::2</srcIpv6>
</srcIp-items>
</time-items>
</System>
This example sets the NTP source IP address to 1.2.3.4.
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right.
ntp source 1::2
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeNtpSrcIp | sys/time/srcIp |
datetimeNtpSrcIp Properties
The following table contains information about the datetimeNtpSrcIp properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
srcIp | address:IPv4 | Source IP Address | Value must match ipv4 format |
srcIpv6 | address:IPv6 | Source IPv6 Address | Value must match ipv6 format |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting a Configured NTP Source IP Address (Ipv6)
Deleting a Configured NTP Source IP Address (Ipv6)
POST http://<IP_Address>/api/mo/sys/time.json
{
"datetimeClkPol": {
"children": [
{
"datetimeNtpSrcIp": {
"attributes": {
"srcIp": "0.0.0.0"
}}}]}}
<System>
<time-items>
<srcIp-items>
<srcIp>0.0.0.0</srcIp>
</srcIp-items>
</time-items>
</System>
This example unsets the NTP source IP address that was set to 1.2.3.4.
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right.
no ntp source 1::2
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeNtpSrcIp | sys/time/srcIp |
datetimeNtpSrcIp Properties
The following table contains information about the datetimeNtpSrcIp properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
srcIp | address:IPv4 | Source IP Address | Value must match ipv4 format |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the NTP Source Interface
Configuring the NTP Source Interface
POST http://<IP_Address>/api/mo/sys/time.json
{
"datetimeClkPol": {
"children": [
{
"datetimeNtpSrcIf": {
"attributes": {
"srcIf": "eth2/1"
}}}]}}
<System>
<time-items>
<srcIp-items>
<srcIp>0.0.0.0</srcIp>
</srcIp-items>
</time-items>
</System>
This example sets the NTP source interface to Ethernet port 2/1.
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right.
ntp source-interface ethernet 2/1
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeNtpSrcIf | sys/time/srcIf |
datetimeNtpSrcIf Properties
The following table contains information about the datetimeNtpSrcIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
srcIf | nw:IfId (base:IfIndex) | Source Interface | Must match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the NTP Source Interface
Deleting the NTP Source Interface
POST http://<IP_Address>/api/mo/sys/time.json
{
"datetimeClkPol": {
"children": [
{
"datetimeNtpSrcIf": {
"attributes": {
"status": "deleted"
}}}]}}
<System>
<time-items>
<srcIf-items xc:operation="delete">
</srcIf-items>
</time-items>
</System>
This example deletes the NTP source interface set to Ethernet port 2/1.
CLI Command
The CLI command below is the equivalent to the payload example displayed in the pane on the right.
no ntp source-interface ethernet 2/1
Note: The property information for this example was added in Release 9.3(3).
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeNtpSrcIf | sys/time/srcIf |
datetimeNtpSrcIf Properties
The following table contains information about the datetimeNtpSrcIf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
status | mo:ModificationStatus (scalar:Bitmask32) | The upgrade status. This property is for internal use only. | SELECTION: 2 - created 4 - modified 8 - deleted 16 - replaced |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring to Scan ACLs Present in all NTP Access Groups
Configuring to Scan ACLs Present in all NTP Access Groups
POST http://<mgmt0_IP>/api/mo/sys/time.json
{
"datetimeClkPol": {
"children": [
{
"datetimeAccessGroup": {
"attributes": {
"matchAll": "enabled"
}}}]}}
{
imdata:[]
}
<System>
<time-items>
<accessgroup-items>
<matchAll>enabled</matchAll>
</accessgroup-items>
</time-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
ntp access-group match-all
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeAccessGroup | sys/time/accessgroup |
datetimeClkPol | sys/time |
datetimeAccessGroup Properties
The following table contains information about the datetimeAccessGroup properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
matchAll | datetime:AdminState (scalar:Enum8) | Scan All NTP Access-Group Options | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting a Configuration to Scan ACLs Present in all NTP Access Groups
Deleting a Configuration to Scan ACLs Present in all NTP Access Groups
POST http://<mgmt0_IP>/api/mo/sys/time.json
{
"datetimeClkPol": {
"children": [
{
"datetimeAccessGroup": {
"attributes": {
"matchAll": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<time-items>
<accessgroup-items>
<matchAll>disabled</matchAll>
</accessgroup-items>
</time-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no ntp access-group match-all
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeAccessGroup | sys/time/accessgroup |
datetimeClkPol | sys/time |
datetimeAccessGroup Properties
The following table contains information about the datetimeAccessGroup properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
matchAll | datetime:AdminState (scalar:Enum8) | Scan All NTP Access-Group Options | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Enabling Control Mode Packets
Enabling Control Mode Packets
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"datetimeClkPol": {
"attributes": {
"allowControl": "enabled"
}}}]}}
{
imdata:[]
}
<System>
<time-items>
<allowControl>enabled</allowControl>
</time-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
ntp allow control
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeClkPol Properties
The following table contains information about the datetimeClkPol properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
allowControl | datetime:AdminState (scalar:Enum8) | Allow Control Mode NTP Packets | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Disabling Control Mode Packets
Disabling Control Mode Packets
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"datetimeClkPol": {
"attributes": {
"allowControl": "disabled",
"rateLimit": "3"
}}}]}}
{
imdata:[]
}
<System>
<time-items>
<allowControl>disabled</allowControl>
<rateLimit>3</rateLimit>
</time-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no ntp allow control
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeClkPol Properties
The following table contains information about the datetimeClkPol properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
allowControl | datetime:AdminState (scalar:Enum8) | Allow Control Mode NTP Packets | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
rateLimit | datetime:allowCtrlRateLimit (scalar:Uint32) | Rate-Limit NTP Control Mode Packets | RANGE: [1 , 65535] DEFAULT: 3 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Rate Limit for Control Packets
Configuring the Rate Limit for Control Packets
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"datetimeClkPol": {
"attributes": {
"allowControl": "enabled",
"rateLimit": "34565"
}}}]}}
{
imdata:[]
}
<System>
<time-items>
<allowControl>enabled</allowControl>
<rateLimit>34565</rateLimit>
</time-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
ntp allow control rate-limit 34565
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeClkPol Properties
The following table contains information about the datetimeClkPol properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
allowControl | datetime:AdminState (scalar:Enum8) | Allow Control Mode NTP Packets | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
rateLimit | datetime:allowCtrlRateLimit (scalar:Uint32) | Rate-Limit NTP Control Mode Packets | RANGE: [1 , 65535] DEFAULT: 3 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Rate Limit for Control Packets
Deleting the Rate Limit for Control Packets
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"datetimeClkPol": {
"attributes": {
"allowControl": "disabled",
"rateLimit": "3"
}}}]}}
{
imdata:[]
}
<System>
<time-items>
<allowControl>disabled</allowControl>
<rateLimit>3</rateLimit>
</time-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no ntp allow control rate-limit 34565
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeClkPol Properties
The following table contains information about the datetimeClkPol properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
allowControl | datetime:AdminState (scalar:Enum8) | Allow Control Mode NTP Packets | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
rateLimit | datetime:allowCtrlRateLimit (scalar:Uint32) | Rate-Limit NTP Control Mode Packets | RANGE: [1 , 65535] DEFAULT: 3 |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring Enabling Private Mode Packets
Configuring Enabling Private Mode Packets
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"datetimeClkPol": {
"attributes": {
"allowPrivate": "enabled"
}}}]}}
{
imdata:[]
}
<System>
<time-items>
<allowPrivate>enabled</allowPrivate>
</time-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
ntp allow private
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeClkPol Properties
The following table contains information about the datetimeClkPol properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
allowPrivate | datetime:AdminState (scalar:Enum8) | Allow Private Mode NTP Packets | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting Enabling Private Mode Packets
Deleting Enabling Private Mode Packets
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"datetimeClkPol": {
"attributes": {
"allowPrivate": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<time-items>
<allowPrivate>disabled</allowPrivate>
</time-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no ntp allow private
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeClkPol Properties
The following table contains information about the datetimeClkPol properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
allowPrivate | datetime:AdminState (scalar:Enum8) | Allow Private Mode NTP Packets | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring NTP Passive
Configuring NTP Passive
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"datetimeClkPol": {
"attributes": {
"passive": "enabled"
}}}]}}
{
imdata:[]
}
<System>
<time-items>
<passive>enabled</passive>
</time-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
ntp passive
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeClkPol Properties
The following table contains information about the datetimeClkPol properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
passive | datetime:AdminState (scalar:Enum8) | Enable/Disable Passive NTP Associations | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting NTP Passive
Deleting NTP Passive
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"datetimeClkPol": {
"attributes": {
"passive": "disabled"
}}}]}}
{
imdata:[]
}
<System>
<time-items>
<passive>disabled</passive>
</time-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no ntp passive
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.
MO | DN |
---|---|
datetimeClkPol | sys/time |
datetimeClkPol Properties
The following table contains information about the datetimeClkPol properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.
Property Name | Data Type | Description | Values |
---|---|---|---|
passive | datetime:AdminState (scalar:Enum8) | Enable/Disable Passive NTP Associations | SELECTION: 1 - enabled 2 - disabled DEFAULT: disabled |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide: