Configuring Secure System Message Logging (TLS)
Configuring Auth as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility auth
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Auth as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility auth
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Authpriv as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility authpriv
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Authpriv as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility authpriv
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Cron as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility cron
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Cron as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility cron
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Daemon as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility daemon
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Daemon as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility daemon
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring FTP as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility ftp
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting FTP as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility ftp
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Kernel as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility kernel
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Kernel as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility kernel
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Local0 as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local0
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Local0 as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local0
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Local1 as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local1
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Local1 as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local1
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Local2 as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local2
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Local2 as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local2
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Local3 as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local3
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Local3 as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local3
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Local4 as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local4
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Local4 as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local4
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Local5 as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local5
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Local5 as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local5
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Local6 as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local6
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Local6 as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local6
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Local7 as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local7
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Local7 as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility local7
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring LPR as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility lpr
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting LPR as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility lpr
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Mail as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility mail
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Mail as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility mail
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring News as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility news
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting News as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility news
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring Syslog as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility syslog
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting Syslog as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility syslog
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring User as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility user
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting User as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility user
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Configuring UUCP as the Facility to Use When Forwarding to the Server
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.
logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility uucp
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
forwardingFacility | syslog:Facility (scalar:Enum16) | The facility to be used to send messages to this destination. | SELECTION: 0 - kern 1 - user 2 - mail 3 - daemon 4 - auth 5 - syslog 6 - lpr 7 - news 8 - uucp 9 - cron 10 - authpriv 11 - ftp 16 - local0 17 - local1 18 - local2 19 - local3 20 - local4 21 - local5 22 - local6 23 - local7 DEFAULT: local7 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
port | syslog:SyslogPort (scalar:Uint32) | The syslog service port of the remote destination. | RANGE: [1 , 65535] DEFAULT: 514 |
severity | syslog:Severity (scalar:Enum8) | The severity of the event, alert, or issue that caused the syslog entry to be generated. | SELECTION: 0 - emergencies 1 - alerts 2 - critical 3 - errors 4 - warnings 5 - notifications 6 - information 7 - debugging DEFAULT: notifications |
transport | mon:Transport (scalar:Enum8) | Transport | SELECTION: 0 - none 1 - tcp 2 - udp 3 - all 4 - tls DEFAULT: udp |
trustpointClientIdentity | string:Basic
| Trustpoint Client Identity | RANGE: [0 , 64] DEFAULT: |
vrfName | l3:VrfName (string:Basic) | The vrf that remote host belongs to | A sequence of characters |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html
Deleting UUCP as the Facility to Use When Forwarding to the Server
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 logging server host0 5 port 123 secure trustpoint client-identity TrustPointLabel_123 use-vrf VRF_1 facility uucp
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 |
syslogSyslog |
sys/syslog |
syslogRemoteDest |
sys/syslog/rdst-{host} |
syslogRemoteDest Properties
The following table contains information about the syslogRemoteDest 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 |
host | address:HostNameOrDottedQuad (string:Basic) | Hostname or IP for export destination | MAX SIZE: 254 |
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:
http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html
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:
https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html