Configuring System Logging

The syslog servers run on remote systems that log system messages based on the syslog protocol. You can configure up to eight IPv4 or IPv6 syslog servers.

To support the same configuration of syslog servers on all switches in a fabric, you can use Cisco Fabric Services (CFS) to distribute the syslog server configuration.

Note: When the device first initializes, messages are sent to syslog servers only after the network is initialized.

You can use system message logging to control the destination and to filter the severity level of messages that system processes generate. You can configure logging to terminal sessions, a log file, and syslog servers on remote systems.

You can configure which system messages should be logged based on the facility that generated the message and its severity level.

For more information, see the Cisco Nexus 9000 Series NX-OS System Management Configuration Guide.

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-installation-and-configuration-guides-list.html/

This section contains payload examples and CLIs to demonstrate how to use the NX-API REST API to configure system logging on Cisco Nexus 3000 and 9000 Series switches and to show how the REST APIs correspond to the CLI commands.

Configuring Console Logging

Configuring Console Logging
POST http://<IP_Address>/api/mo/sys/syslog/console.json
{
    "syslogConsole": {
        "attributes": {
            "adminState": "enabled",
            "severity": "critical"
}}}

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.

MODN
syslogConsole sys/syslog/console


syslogConsole Properties

The following table contains information about the syslogConsole 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 NameData TypeDescriptionValues
adminStatemon:AdminState
(scalar:Enum8)
The administrative state of the console terminal.SELECTION:
1 - enabled
2 - disabled
DEFAULT: enabled
severitysyslog:Severity
(scalar:Enum8)
The minimum severity level of the messages to be displayed.SELECTION:
0 - emergencies
1 - alerts
2 - critical
3 - errors
4 - warnings
5 - notifications
6 - information
7 - debugging
DEFAULT: critical


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 Module Logging

Configuring Module Logging
POST http://<IP_Address>/api/mo/sys/syslog/inst.json
{
"syslogInst": {
    "attributes": {
        "modAdminState": "<state>",
        "modSeverity": "<severity>"
}}}

Configures the linecard logging instance.

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.

MODN
syslogInst sys/syslog/inst


syslogInst Properties

The following table contains information about the syslogInst 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 NameData TypeDescriptionValues
modAdminStatemon:AdminState
(scalar:Enum8)
SELECTION:
1 - enabled
2 - disabled
DEFAULT: enabled
modSeveritysyslog:Severity
(scalar:Enum8)
Severity levelSELECTION:
0 - emergencies
1 - alerts
2 - critical
3 - errors
4 - warnings
5 - notifications
6 - information
7 - debugging
DEFAULT: notifications


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 the Log File

Configuring the Log File
POST http://<IP_Address>/api/mo/sys/syslog/file.json
{
    "syslogFile": {
        "attributes": {
            "adminState": "enabled",
            "name": "<logFileName>",
            "severity": "<severity>",
            "size": "<size>"
}}}

Configures the log file.

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.

MODN
syslogFile sys/syslog/file


syslogFile Properties

The following table contains information about the syslogFile 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 NameData TypeDescriptionValues
adminStatemon:AdminState
(scalar:Enum8)
The administrative state of the local file.SELECTION:
1 - enabled
2 - disabled
DEFAULT: enabled
namepol:ObjName
(naming:Name256)
Object name
MAX SIZE: 199
DEFAULT: messages
severitysyslog: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: information
sizesyslog:FileSize
(scalar:Uint32)
Specifies the maximum file size.
RANGE: [4096 , 4194304]
DEFAULT: 4194304


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 Monitor Logging

Configuring Monitor Logging
POST http://<IP_Address>/api/mo/sys/syslog/monitor.json
{
  "syslogTermMonitor": {
    "attributes": {
      "adminState": "<state>",
      "severity": "<severity>"
}}}

Configures monitor logging.

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.

MODN
syslogTermMonitor sys/syslog/monitor


syslogTermMonitor Properties

The following table contains information about the syslogTermMonitor 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 NameData TypeDescriptionValues
adminStatemon:AdminState
(scalar:Enum8)
The destination policy administrative state. If enabled, the system uses the destination policy when an error matching the associated cause is encountered. Otherwise, the system ignores the policy even if a matching error occurs. By default, all policies are enabled.SELECTION:
1 - enabled
2 - disabled
DEFAULT: enabled
severitysyslog:Severity
(scalar:Enum8)
SeveritySELECTION:
0 - emergencies
1 - alerts
2 - critical
3 - errors
4 - warnings
5 - notifications
6 - information
7 - debugging
DEFAULT: notifications


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 the Logging Timestamp

Configuring the Logging Timestamp
POST http://<IP_Address>/api/mo/sys/syslog/timestamp.json
{
  "syslogTimeStamp": {
    "attributes": {
      "format": "<granularity>"
}}}

Configures logging timestamp granularity.

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.

MODN
syslogTimeStamp sys/syslog/timestamp


syslogTimeStamp Properties

The following table contains information about the syslogTimeStamp 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 NameData TypeDescriptionValues
formatsyslog:TimeStampFormat
(scalar:Enum8)
FormatSELECTION:
0 - microseconds
1 - milliseconds
2 - seconds
DEFAULT: seconds


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 Interface Logging

Configuring Interface Logging
POST http://<IP_Address>/api/mo/sys/syslog/source.json
{
  "syslogSourceInterface": {
    "attributes": {
      "adminState": "<state>",
      "ifName": "<interface><slot>/<port>"
}}}

Enables and configures logging on an interface.

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.

MODN
syslogSourceInterface sys/syslog/source


syslogSourceInterface Properties

The following table contains information about the syslogSourceInterface 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 NameData TypeDescriptionValues
adminStatemon:AdminState
(scalar:Enum8)
The destination policy administrative state. If enabled, the system uses the destination policy when an error matching the associated cause is encountered. Otherwise, the system ignores the policy even if a matching error occurs. By default, all policies are enabled.SELECTION:
1 - enabled
2 - disabled
DEFAULT: enabled
ifNamenw:IfId
(base:IfIndex)
InterfaceMust match first field in the output of `show intf brief`. Example: Eth1/1 or Vlan100


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

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 Logging Level

Enables and configures logging level on a system facility.
POST http://<IP_Address>/api/mo/sys/syslog/level-<facility-name>.json
Configuring the logging level for AAA at "Alert" level.
{
    "aaaUserEp": {
        "children": [
            {
              "aaaAuthRealm": {
                "attributes": {
                  "loggingLevel": "Alert"
}}}]}}

Enables and configures logging level on a system facility.

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.

MODN
aaaUserEp sys/userext
aaaAuthRealm sys/userext/authrealm


aaaAuthRealm Properties

The following table contains information about the aaaAuthRealm 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 NameData TypeDescriptionValues
loggingLevelaaa:LoggingLevel
(scalar:Enum8)
AAA Logging level
RANGE: [0 , 7]
DEFAULT: Error


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 Logging Level NVE

Configuring Logging Level NVE
POST http://<IP_Address>/api/mo/sys/syslog/level-<facility-name>.json
{
  "loggingFacility": {
    "attributes": {
      "facilityName": "nve",
      "severityLevel": "warnings"
    }
  }
}

Enables and configures logging level NVE in the logging library.

Note: The property information for this example was added in Release 10.4(2).


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.

MODN
aaaUserEp sys/logging/loglevel/


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 Remote Logging Server

Configuring Remote Logging Server
POST http://<IP_Address>/api/mo/sys/syslog.json
{
    "syslogSyslog": {
      "children": [
        {
          "syslogRemoteDest": {
            "attributes": {
              "forwardingFacility": "<facility>",
              "host": "<hostname>",
              "severity": "<severity>",
              "vrfName": "<vrfName>"
}}}]}}

Configures remote logging on a server.

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.

MODN
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 NameData TypeDescriptionValues
forwardingFacilitysyslog: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
hostaddress:HostNameOrDottedQuad
(string:Basic)
Hostname or IP for export destination
MAX SIZE: 254
severitysyslog: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
vrfNamel3:VrfName
(string:Basic)
The vrf that remote host belongs toA 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

Clearing a Logfile

Clearing a Logfile
POST http://<IP_Address>/api/mo/sys/action.json
{
    "actionLSubj": {
        "attributes": {
            "dn": "sys/action/lsubj-[sys/syslog]"

        }
        "children" : [{
            "syslogFileClearLogfileLTask" : {
                "attributes" : {
                    "adminSt" : "start",
                    "dn" : "sys/action/lsubj-[sys/syslog]/syslogFileClearLogfileLTask",
                    "freq": "one-shot"
}}}]}}

Clears the logfile.

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.

MODN
actionLSubj sys/action/lsubj-{[oDn]}


actionLSubj Properties

The following table contains information about the actionLSubj 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 NameData TypeDescriptionValues
dn
reference:BinRef
A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module.


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 the ICMPv6 Syslog Message Level

Configuring the ICMPv6 Syslog Message Level
POST http://<mgmt0_IP>/api/mo/sys/icmpv6.json
{
 "icmpv6Entity": {
   "children": [
     {
       "icmpv6Inst": {
         "attributes": {
           "loggingLevel": "Error"
}}}]}}
{
    imdata:[]
}
<System>
  <icmpv6-items>
    <inst-items>
      <loggingLevel>Error</loggingLevel>
    </inst-items>
  </icmpv6-items>
</System>

Configures the ICMPv6 logging level.


CLI Command

The CLI command below is the equivalent to the payload example 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 or the YANG tab to view the XML payload.

logging Level icmpv6 3

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.

MODN
icmpv6Entity sys/icmpv6
icmpv6Inst sys/icmpv6/inst


icmpv6Inst Properties

The following table contains information about the icmpv6Inst 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 NameData TypeDescriptionValues
loggingLevel
icmpv6:LoggingLevel
scalar:Enum8
ICMPv6 Logging LevelSELECTION:
  • 0 - Emergency
  • 1 - Alert
  • 2 - Critical
  • 3 - Error
  • 4 - Warning
  • 5 - Notice
  • 6 - Informational
  • 7 - Debug
  • DEFAULT: Error(3)

  • 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 the IPv6 PIM Syslog Message Level

    Configuring the IPv6 PIM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/pim6/inst.json
    
    {
      "pim6Inst": {
        "children": [
          {
            "pim6Gl": {
              "attributes": {
                "logLvl": "1"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <pim6-items>
        <inst-items>
          <gl-items>
            <logLvl>1</logLvl>
          </gl-items>
        </inst-items>
      </pim6-items>
    </System>
    

    Note: This example was added in Release 9.2(2).


    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 level ipv6 pim 1

    Note: The property information for this example was added in Release 9.3(3).


    Verifying a DME Configuration
    The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

    MODN
    pim6Inst sys/pim6/inst
    pim6Gl sys/pim6/inst/gl


    pim6Gl Properties

    The following table contains information about the pim6Gl 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 NameData TypeDescriptionValues
    logLvlmcast:LogLevelRange
    (scalar:Uint16)
    Syslog filter level
    RANGE: [0 , 7]
    DEFAULT: 0


    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 the IPv6 PIM Syslog Message Level

    Deleting the IPv6 PIM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/pim6/inst.json
    
    {
      "pim6Inst": {
        "children": [
          {
            "pim6Gl": {
              "attributes": {
                "logLvl": "0"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <pim6-items>
        <inst-items>
          <gl-items>
            <logLvl>0</logLvl>
          </gl-items>
        </inst-items>
      </pim6-items>
    </System>
    

    Note: This example was added in Release 9.2(2).


    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 level ipv6 pim 1

    Note: The property information for this example was added in Release 9.3(3).


    Verifying a DME Configuration
    The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

    MODN
    pim6Inst sys/pim6/inst
    pim6Gl sys/pim6/inst/gl


    pim6Gl Properties

    The following table contains information about the pim6Gl 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 NameData TypeDescriptionValues
    logLvlmcast:LogLevelRange
    (scalar:Uint16)
    Syslog filter level
    RANGE: [0 , 7]
    DEFAULT: 0


    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 the LDAP Syslog Message Level

    Configuring the LDAP Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/userext.json
    
    {
      "aaaUserEp": {
        "children": [
          {
            "aaaLdapEp": {
              "attributes": {
                "loggingLevel": "alert"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <userext-items>
        <ldapext-items>
          <loggingLevel>1</loggingLevel>
        </ldapext-items>
      </userext-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    logging level ldap 1


    aaaLdapEp Properties

    The following table contains information about the aaaLdapEp 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 NameData TypeDescriptionValues
    loggingLevelaaa:LdapLogLevel
    (scalar:Enum8)
    LDAP Logging levelSELECTION:
    0 - emergency
    1 - alert
    2 - critical
    3 - error
    4 - warning
    5 - notification
    6 - informational
    7 - debug
    DEFAULT: critical


    Related Documentation

    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.

    MODN
    aaaUserEp sys/userext
    aaaLdapEp sys/userext/ldapext


    aaaLdapEp Properties

    The following table contains information about the aaaLdapEp 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 NameData TypeDescriptionValues
    loggingLevelaaa:LdapLogLevel
    (scalar:Enum8)
    LDAP Logging levelSELECTION:
    0 - emergency
    1 - alert
    2 - critical
    3 - error
    4 - warning
    5 - notification
    6 - informational
    7 - debug
    DEFAULT: critical


    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 the LDAP Syslog Message Level

    Deleting the LDAP Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/userext.json
    
    {
      "aaaUserEp": {
        "children": [
          {
            "aaaLdapEp": {
              "attributes": {
                "loggingLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <userext-items>
        <ldapext-items>
          <loggingLevel>2</loggingLevel>
        </ldapext-items>
      </userext-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    no logging level ldap 1


    aaaLdapEp Properties

    The following table contains information about the aaaLdapEp 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 NameData TypeDescriptionValues
    loggingLevelaaa:LdapLogLevel
    (scalar:Enum8)
    LDAP Logging levelSELECTION:
    0 - emergency
    1 - alert
    2 - critical
    3 - error
    4 - warning
    5 - notification
    6 - informational
    7 - debug
    DEFAULT: critical


    Related Documentation

    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.

    MODN
    aaaUserEp sys/userext
    aaaLdapEp sys/userext/ldapext


    aaaLdapEp Properties

    The following table contains information about the aaaLdapEp 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 NameData TypeDescriptionValues
    loggingLevelaaa:LdapLogLevel
    (scalar:Enum8)
    LDAP Logging levelSELECTION:
    0 - emergency
    1 - alert
    2 - critical
    3 - error
    4 - warning
    5 - notification
    6 - informational
    7 - debug
    DEFAULT: critical


    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 the MRIB Syslog Message Level

    Configuring the MRIB Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/m6rib/inst.json
    
    {
      "m6ribInst": {
        "children": [
          {
            "m6ribDom": {
              "attributes": {
                "name": "default"
              },
              "children": [
                {
                  "m6ribLogLevel": {
                    "attributes": {
                      "level": "1",
                      "type": "m6rib"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <m6rib-items>
        <inst-items>
          <dom-items>
            <Dom-list>
              <name>default</name>
              <loglevel-items>
                <level>1</level>
                <type>m6rib</type>
              </loglevel-items>
            </Dom-list>
          </dom-items>
        </inst-items>
      </m6rib-items>
    </System>
    

    Note: This example was added in Release 9.2(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    logging level m6rib 1

    Note: The property information for this example was added in Release 9.3(3).


    Verifying a DME Configuration
    The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

    MODN
    m6ribInst sys/m6rib/inst
    m6ribDom sys/m6rib/inst/dom-{name}
    m6ribLogLevel sys/m6rib/inst/dom-{name}/loglevel


    m6ribDom Properties

    The following table contains information about the m6ribDom 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 NameData TypeDescriptionValues
    namenaming:Name256
    (string:Basic)
    The name of the object.
    MAX SIZE: 63


    m6ribLogLevel Properties

    The following table contains information about the m6ribLogLevel 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 NameData TypeDescriptionValues
    levelm6rib:LogLevel
    (scalar:Uint16)
    Logging Level
    RANGE: [0 , 7]
    typestring:Basic
    Logging typeA 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 the MRIB Syslog Message Level

    Deleting the MRIB Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/m6rib/inst.json
    
    {
      "m6ribInst": {
        "children": [
          {
            "m6ribDom": {
              "attributes": {
                "name": "default"
              },
              "children": [
                {
                  "m6ribLogLevel": {
                    "attributes": {
                      "status": "deleted"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <m6rib-items>
        <inst-items>
          <dom-items>
            <Dom-list>
              <name>default</name>
              <loglevel-items xc:operation="delete">
              </loglevel-items>
            </Dom-list>
          </dom-items>
        </inst-items>
      </m6rib-items>
    </System>
    

    Note: This example was added in Release 9.2(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    no logging level m6rib 1

    Note: The property information for this example was added in Release 9.3(3).


    Verifying a DME Configuration
    The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

    MODN
    m6ribInst sys/m6rib/inst
    m6ribDom sys/m6rib/inst/dom-{name}
    m6ribLogLevel sys/m6rib/inst/dom-{name}/loglevel


    m6ribDom Properties

    The following table contains information about the m6ribDom 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 NameData TypeDescriptionValues
    namenaming:Name256
    (string:Basic)
    The name of the object.
    MAX SIZE: 63


    m6ribLogLevel Properties

    The following table contains information about the m6ribLogLevel 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 NameData TypeDescriptionValues
    statusmo: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 the Netstack Syslog Message Level

    Configuring the Netstack Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/ipv4.json
    
    {
     "ipv4Entity": {
       "children": [
         {
           "ipv4Inst": {
             "attributes": {
               "loggingLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <ipv4-items>
        <inst-items>
          <loggingLevel>critical</loggingLevel>
        </inst-items>
      </ipv4-items>
    </System>
    

    Sets the syslog filter level for netstack.


    CLI Command

    The CLI command below is the equivalent to the payload example 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 or the YANG tab to view the XML payload.

    logging level netstack 2

    Note: The property information for this example was added in Release 9.3(3).


    Verifying a DME Configuration
    The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

    MODN
    ipv4Entity sys/ipv4
    ipv4Inst sys/ipv4/inst


    ipv4Inst Properties

    The following table contains information about the ipv4Inst 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 NameData TypeDescriptionValues
    loggingLevelarp:LoggingLevel
    (scalar:Enum8)
    Logging levelSELECTION:
    0 - emergency
    1 - alert
    2 - critical
    3 - error
    4 - warning
    5 - notification
    6 - informational
    7 - debug
    DEFAULT: error


    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

    Using the Hostname as the Origin Id of Logging Messages

    Using the Hostname as the Origin Id of Logging Messages
    
    POST http://<mgmt0_IP>/api/mo/sys/syslog.json
    
    {
      "syslogSyslog": {
        "children": [
          {
            "syslogOriginid": {
              "attributes": {
                "idtype": "hostname"
              }
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <syslog-items>
        <originid-items>
          <idtype>hostname</idtype>
        </originid-items>
      </syslog-items>
    </System>
    

    Note: This example was added in Release 9.2(3).


    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 origin-id hostname

    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.

    MODN
    syslogSyslog sys/syslog
    syslogOriginid sys/syslog/originid


    syslogOriginid Properties

    The following table contains information about the syslogOriginid 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 NameData TypeDescriptionValues
    idtypesyslog:OriginIdType
    (scalar:Enum8)
    OriginId type for Hostname, IP or StringSELECTION:
    0 - unknown
    1 - hostname
    2 - ip
    3 - string
    DEFAULT: unknown


    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

    Disabling the Hostname as the Origin Id of Logging Messages

    Disabling the Hostname as the Origin Id of Logging Messages
    
    POST http://<mgmt0_IP>/api/mo/sys/syslog.json
    
    {
      "syslogSyslog": {
        "children": [
          {
            "syslogOriginid": {
              "attributes": {
                "status": "deleted"
              }
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <syslog-items>
        <originid-items xc:operation="delete">
        </originid-items>
      </syslog-items>
    </System>
    

    Note: This example was added in Release 9.2(3).


    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 origin-id hostname

    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.

    MODN
    syslogSyslog sys/syslog
    syslogOriginid sys/syslog/originid


    syslogOriginid Properties

    The following table contains information about the syslogOriginid 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 NameData TypeDescriptionValues
    statusmo: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

    Using the IP as the Origin Id of Logging Messages

    Using the IP as the Origin Id of Logging Messages
    
    POST http://<mgmt0_IP>/api/mo/sys/syslog.json
    
    {
      "syslogSyslog": {
        "children": [
          {
            "syslogOriginid": {
              "attributes": {
                "idtype": "ip",
                "idvalue": "1.2.3.4"
              }
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <syslog-items>
        <originid-items>
          <idtype>ip</idtype>
          <idvalue>1.2.3.4</idvalue>
        </originid-items>
      </syslog-items>
    </System>
    

    Note: This example was added in Release 9.2(3).


    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 origin-id ip 1.2.3.4

    Note: The property information for this example was added in Release 9.3(3).


    Verifying a DME Configuration
    The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

    MODN
    syslogSyslog sys/syslog
    syslogOriginid sys/syslog/originid


    syslogOriginid Properties

    The following table contains information about the syslogOriginid 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 NameData TypeDescriptionValues
    idtypesyslog:OriginIdType
    (scalar:Enum8)
    OriginId type for Hostname, IP or StringSELECTION:
    0 - unknown
    1 - hostname
    2 - ip
    3 - string
    DEFAULT: unknown
    idvaluesyslog:OriginIdValue
    (string:Basic)
    OriginId value for Hostname, IP or String
    MAX SIZE: 199


    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

    Disabling the IP as the Origin Id of Logging Messages

    Disabling the IP as the Origin Id of Logging Messages
    
    POST http://<mgmt0_IP>/api/mo/sys/syslog.json
    
    {
      "syslogSyslog": {
        "children": [
          {
            "syslogOriginid": {
              "attributes": {
                "status": "deleted"
              }
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <syslog-items>
        <originid-items xc:operation="delete">
        </originid-items>
      </syslog-items>
    </System>
    

    Note: This example was added in Release 9.2(3).


    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 origin-id ip 1.2.3.4

    Note: The property information for this example was added in Release 9.3(3).


    Verifying a DME Configuration
    The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

    MODN
    syslogSyslog sys/syslog
    syslogOriginid sys/syslog/originid


    syslogOriginid Properties

    The following table contains information about the syslogOriginid 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 NameData TypeDescriptionValues
    statusmo: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

    Appending a String to the Front of Syslog Messages

    Appending a String to the Front of Syslog Messages
    
    POST http://<mgmt0_IP>/api/mo/sys/syslog.json
    
    {
      "syslogSyslog": {
        "children": [
          {
            "syslogOriginid": {
              "attributes": {
                "idtype": "string",
                "idvalue": "SampleString_123"
              }
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <syslog-items>
        <originid-items>
          <idtype>string</idtype>
          <idvalue>SampleString_123</idvalue>
        </originid-items>
      </syslog-items>
    </System>
    

    Note: This example was added in Release 9.2(3).


    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 origin-id string SampleString_123

    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.

    MODN
    syslogSyslog sys/syslog
    syslogOriginid sys/syslog/originid


    syslogOriginid Properties

    The following table contains information about the syslogOriginid 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 NameData TypeDescriptionValues
    idtypesyslog:OriginIdType
    (scalar:Enum8)
    OriginId type for Hostname, IP or StringSELECTION:
    0 - unknown
    1 - hostname
    2 - ip
    3 - string
    DEFAULT: unknown
    idvaluesyslog:OriginIdValue
    (string:Basic)
    OriginId value for Hostname, IP or String
    MAX SIZE: 199


    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

    Removing a String from the Front of Syslog Messages

    Removing a String from the Front of Syslog Messages
    
    POST http://<mgmt0_IP>/api/mo/sys/syslog.json
    
    {
      "syslogSyslog": {
        "children": [
          {
            "syslogOriginid": {
              "attributes": {
                "status": "deleted"
              }
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <syslog-items>
        <originid-items xc:operation="delete">
        </originid-items>
      </syslog-items>
    </System>
    

    Note: This example was added in Release 9.2(3).


    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 origin-id string SampleString_123

    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.

    MODN
    syslogSyslog sys/syslog
    syslogOriginid sys/syslog/originid


    syslogOriginid Properties

    The following table contains information about the syslogOriginid 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 NameData TypeDescriptionValues
    statusmo: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 the Syslog Message Level for All Facilities

    Configuring the Syslog Message Level for All Facilities
    
    POST http://<mgmt0_IP>/api/mo/sys/logging.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "attributes": {
                      "all": "enableall",
                      "severityLevel": "alerts"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
     <logging-items>
        <loglevel-items>
          <all>enableall</all>
          <severityLevel>alerts</severityLevel>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level all 1


    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.

    MODN
    loggingLogging sys/logging
    loggingLogLevel sys/logging/loglevel


    loggingLogLevel Properties

    The following table contains information about the loggingLogLevel 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 NameData TypeDescriptionValues
    alllogging:LoggingEnableAll
    (scalar:Enum8)
    Logging level all state disabled/enabledSELECTION:
    0 - unspecified
    1 - enableall
    2 - disableall
    DEFAULT: unspecified
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for all the facilitesSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the Syslog Message Level for All Facilities

    Deleting the Syslog Message Level for All Facilities
    
    POST http://<mgmt0_IP>/api/mo/sys/logging.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "attributes": {
                      "all": "disableall"
                    }
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <all>disableall</all>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level all 1


    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.

    MODN
    loggingLogging sys/logging
    loggingLogLevel sys/logging/loglevel


    loggingLogLevel Properties

    The following table contains information about the loggingLogLevel 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 NameData TypeDescriptionValues
    alllogging:LoggingEnableAll
    (scalar:Enum8)
    Logging level all state disabled/enabledSELECTION:
    0 - unspecified
    1 - enableall
    2 - disableall
    DEFAULT: unspecified


    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 the ASCII-CFG Syslog Message Level

    Configuring the ASCII-CFG Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "children": [
                      {
                        "loggingFacility": {
                          "attributes": {
                            "facilityName": "ascii-cfg",
                            "severityLevel": "alerts"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>ascii-cfg</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level ascii-cfg 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[ascii-cfg]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the ASCII-CFG Syslog Message Level

    Deleting the ASCII-CFG Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "children": [
                      {
                        "loggingFacility": {
                          "attributes": {
                            "facilityName": "ascii-cfg",
                            "severityLevel": "information"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>ascii-cfg</facilityName>
              <severityLevel>information</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level ascii-cfg 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[ascii-cfg]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the BFD Syslog Message Level

    Configuring the BFD Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "bfd",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>bfd</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level bfd 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[bfd]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the BFD Syslog Message Level

    Deleting the BFD Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "bfd",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>bfd</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level bfd 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[bfd]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the Bootvar Syslog Message Level

    Configuring the Bootvar Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "bootvar",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>bootvar</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level bootvar 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[bootvar]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility name. The value can be numeric or a character string.SELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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

    Unconfiguring the Bootvar Syslog Message Level

    Unconfiguring the Bootvar Syslog Message Level  
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "bootvar",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>bootvar</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level bootvar 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[bootvar]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the Callhome Syslog Message Level

    Configuring the Callhome Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "callhome",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>callhome</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level callhome 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[callhome]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the Callhome Syslog Message Level

    Deleting the Callhome Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "callhome",
                "severityLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>callhome</facilityName>
              <severityLevel>critical</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level callhome 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[callhome]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the CLIs Syslog Message Level

    Configuring the CLIs Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "clis",
                "severityLevel": "information"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>clis</facilityName>
              <severityLevel>information</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level clis 6


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[clis]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: errors


    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 the CLIs Syslog Message Level

    Deleting the CLIs Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "clis",
                "severityLevel": "errors"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>clis</facilityName>
              <severityLevel>errors</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level clis 6


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[clis]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the Clock Manager Syslog Message Level

    Configuring the Clock Manager Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "datetimeClock": {
              "attributes": {
                "loggingLevel": "debug"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <clock-items>
        <loggingLevel>debug</loggingLevel>
      </clock-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    logging level clk_mgr 7


    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.

    MODN
    datetimeClocksys/clock


    datetimeClock Properties

    The following table contains information about the datetimeClock 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 NameData TypeDescriptionValues
    loggingLeveldatetime:LoggingLevel
    (scalar:Enum8)
    Clock manager logging levelSELECTION:
    0 - emergency
    1 - alert
    2 - critical
    3 - error
    4 - warning
    5 - notif
    6 - inform
    7 - debug
    DEFAULT: critical


    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

    For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Deleting the Clock Manager Syslog Message Level

    Deleting the Clock Manager Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "datetimeClock": {
              "attributes": {
                "loggingLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <clock-items>
        <loggingLevel>critical</loggingLevel>
      </clock-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    no logging level clk_mgr 7


    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.

    MODN
    datetimeClocksys/clock


    datetimeClock Properties

    The following table contains information about the datetimeClock 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 NameData TypeDescriptionValues
    loggingLeveldatetime:LoggingLevel
    (scalar:Enum8)
    Clock manager logging levelSELECTION:
    0 - emergency
    1 - alert
    2 - critical
    3 - error
    4 - warning
    5 - notif
    6 - inform
    7 - debug
    DEFAULT: critical


    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

    For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Configuring the CTS Syslog Message Level

    Configuring the CTS Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "children": [
                      {
                        "loggingFacility": {
                          "attributes": {
                            "facilityName": "cts",
                            "severityLevel": "alerts"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>cts</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level cts 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[cts]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the CTS Syslog Message Level

    Deleting the CTS Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "children": [
                      {
                        "loggingFacility": {
                          "attributes": {
                            "facilityName": "cts",
                            "severityLevel": "errors"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>cts</facilityName>
              <severityLevel>errors</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level cts 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[cts]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the Diagnostic Port Loopback Test Syslog Message Level

    Configuring the Diagnostic Port Loopback Test Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "diag_port_lb",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>diag_port_lb</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level diag_port_lb 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[diag_port_lb]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the Diagnostic Port Loopback Test Syslog Message Level

    Deleting the Diagnostic Port Loopback Test Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "diag_port_lb",
                "severityLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>diag_port_lb</facilityName>
              <severityLevel>critical</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level diag_port_lb 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[diag_port_lb]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the Delta Statistics Syslog Message Level

    Configuring the Delta Statistics Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "ethdstats",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>ethdstats</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level ethdstats 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[ethdstats]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the Delta Statistics Syslog Message Level

    Deleting the Delta Statistics Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "ethdstats",
                "severityLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>ethdstats</facilityName>
              <severityLevel>critical</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level ethdstats 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[ethdstats]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 ELTM Syslog Message Level

    Configuring ELTM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "eltm",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>eltm</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level eltm 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[eltm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 ELTM Syslog Message Level

    Deleting ELTM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "children": [
                      {
                        "loggingFacility": {
                          "attributes": {
                            "facilityName": "eltm",
                            "severityLevel": "critical"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
     <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>eltm</facilityName>
              <severityLevel>critical</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level eltm 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[eltm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the Ethernet SPAN Syslog Message Level

    Configuring the Ethernet SPAN Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "monitor",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>monitor</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level monitor 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[monitor]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the Ethernet SPAN Syslog Message Level

    Deleting the Ethernet SPAN Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "monitor",
                "severityLevel": "errors"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>monitor</facilityName>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level monitor 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[monitor]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the EVMC Syslog Message Level

    Configuring the EVMC Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "evmc",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>evmc</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level evmc 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[evmc]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the EVMC Syslog Message Level

    Deleting the EVMC Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "evmc",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>evmc</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level evmc 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[evmc]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the Fabric Forwarding Syslog Message Level

    Configuring the Fabric Forwarding Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "hmm",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>hmm</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level fabric forwarding 5


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[hmm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the Fabric Forwarding Syslog Message Level

    Deleting the Fabric Forwarding Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "hmm",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>hmm</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level fabric forwarding 5


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[hmm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the Feature Manager Syslog Message Level

    Configuring the Feature Manager Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "feature-mgr",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>feature-mgr</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level feature-mgr 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[feature-mgr]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the Feature Manager Syslog Message Level

    Deleting the Feature Manager Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "feature-mgr",
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>feature-mgr</facilityName>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level feature-mgr 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[feature-mgr]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the FEX Syslog Message Level

    Configuring the FEX Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "children": [
                      {
                        "loggingFacility": {
                          "attributes": {
                            "facilityName": "fex",
                            "severityLevel": "alerts"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>fex</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3)


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the opt-left corner of the pane on the right to view the JSON payload. Click the YANG tab to view the XML payload.

    logging level fex 1


    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.

    MODN
    topSystem sys
    loggingLogging sys/logging
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[fex]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the FEX Syslog Message Level

    Deleting the FEX Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "children": [
                      {
                        "loggingFacility": {
                          "attributes": {
                            "facilityName": "fex",
                            "severityLevel": "notifications"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>fex</facilityName>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3)


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the opt-left corner of the pane on the right to view the JSON payload. Click the YANG tab to view the XML payload.

    no logging level fex 1


    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.

    MODN
    topSystem sys
    loggingLogging sys/logging
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-{[facilityName]}


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the GPIXM Syslog Message Level

    Configuring the GPIXM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "gpixm",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>gpixm</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level gpixm 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[gpixm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the GPIXM Syslog Message Level

    Deleting the GPIXM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "gpixm",
                "severityLevel": "warnings"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>gpixm</facilityName>
              <severityLevel>warnings</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level gpixm 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[gpixm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the HSRP Syslog Message Level

    Configuring the HSRP Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "hsrp",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>hsrp</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level hsrp 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[hsrp]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the HSRP Syslog Message Level

    Deleting the HSRP Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "hsrp",
                "severityLevel": "errors",
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>hsrp</facilityName>
              <severityLevel>errors</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level hsrp 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[hsrp]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the ICAM Syslog Message Level

    Configuring the ICAM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "icam",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>icam</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level icam 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[icam]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the ICAM Syslog Message Level

    Deleting the ICAM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "icam",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>icam</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level icam 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[icam]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the IM Syslog Message Level

    Configuring the IM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "im",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>im</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level im 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[im]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the IM Syslog Message Level

    Deleting the IM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "im",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>im</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level im 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[im]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the Interface VLAN Syslog Message Level

    Configuring the Interface VLAN Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "interface-vlan",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>interface-vlan</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level interface-vlan 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[interface-vlan]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the Interface VLAN Syslog Message Level

    Deleting the Interface VLAN Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "children": [
                      {
                        "loggingFacility": {
                          "attributes": {
                            "facilityName": "interface-vlan",
                            "severityLevel": "critical"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
       <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>interface-vlan</facilityName>
              <severityLevel>critical</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level interface-vlan 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[interface-vlan]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the IPQOSMGR Syslog Message Level

    Configuring the IPQOSMGR Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "ipqos",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>ipqos</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level ipqos 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[ipqos]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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

    Unconfiguring the IPQOSMGR Syslog Message Level

    Unconfiguring the IPQOSMGR Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "ipqos",
                "severityLevel": "warnings"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>ipqos</facilityName>
              <severityLevel>warnings</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level ipqos 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[ipqos]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 IP SLA Sender Syslog Message Level

    Configuring IP SLA Sender Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/sla/inst.json
    
    {
      "slaInst": {
        "children": [
          {
            "slaSender": {
              "attributes": {
                "loggingLevel": "1"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <sla-items>
        <inst-items>
          <sender-items>
            <loggingLevel>1</loggingLevel>
          </sender-items>
        </inst-items>
      </sla-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level ip sla sender 1


    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.

    MODN
    slaInst sys/sla/inst
    slaSender sys/sla/inst/sender


    slaSender Properties

    The following table contains information about the slaSender 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 NameData TypeDescriptionValues
    loggingLevelscalar:Uint32
    configures the logging level for ip sla sender. The property can be set only if feature sla sender is enabled.
    RANGE: [0 , 7]
    DEFAULT: 3


    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 IP SLA Sender Syslog Message Level

    Deleting IP SLA Sender Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/sla/inst.json
    
    {
      "slaInst": {
        "children": [
          {
            "slaSender": {
              "attributes": {
                "loggingLevel": "3"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <sla-items>
        <inst-items>
          <sender-items>
            <loggingLevel>3</loggingLevel>
          </sender-items>
        </inst-items>
      </sla-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level ip sla sender 1


    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.

    MODN
    slaInst sys/sla/inst
    slaSender sys/sla/inst/sender


    slaSender Properties

    The following table contains information about the slaSender 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 NameData TypeDescriptionValues
    loggingLevelscalar:Uint32
    configures the logging level for ip sla sender. The property can be set only if feature sla sender is enabled.
    RANGE: [0 , 7]
    DEFAULT: 3


    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 the IP SLA Twamp-Server Syslog Message Level

    Configuring the IP SLA Twamp-Server Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "slaEntity": {
              "children": [
                {
                  "slaInst": {
                    "children": [
                      {
                        "slaTwampServer": {
                          "attributes": {
                            "loggingLevel": "1"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <sla-items>
        <inst-items>
          <twampserver-items>
            <loggingLevel>1</loggingLevel>
          </twampserver-items>
        </inst-items>
      </sla-items>
    </System>
    

    Note: This example was added in Release 9.3(3)


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the opt-left corner of the pane on the right to view the JSON payload. Click the YANG tab to view the XML payload.

    logging level ip sla twamp-server 1


    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.

    MODN
    topSystem sys
    slaEntity sys/sla
    slaInst sys/sla/inst
    slaTwampServer sys/sla/inst/twampserver


    slaTwampServer Properties

    The following table contains information about the slaTwampServer 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 NameData TypeDescriptionValues
    loggingLevelscalar:Uint32
    configures the logging level for twamp server. The property can be set only if feature sla twamp-server is enabled.
    RANGE: [0 , 7]
    DEFAULT: 2


    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 the IP SLA Twamp-Server Syslog Message Level

    Deleting the IP SLA Twamp-Server Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/sla/inst.json
    
    {
      "slaInst": {
        "children": [
          {
            "slaTwampServer": {
              "attributes": {
                "loggingLevel": "2"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <sla-items>
        <inst-items>
          <twampserver-items>
            <loggingLevel>2</loggingLevel>
          </twampserver-items>
        </inst-items>
      </sla-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level ip sla twamp-server 1


    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.

    MODN
    slaInst sys/sla/inst
    slaTwampServer sys/sla/inst/twampserver


    slaTwampServer Properties

    The following table contains information about the slaTwampServer 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 NameData TypeDescriptionValues
    loggingLevelscalar:Uint32
    configures the logging level for twamp server. The property can be set only if feature sla twamp-server is enabled.
    RANGE: [0 , 7]
    DEFAULT: 2


    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 the ISCM Syslog Message Level

    Configuring the Level for ISCM Syslog Messages
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "iscm",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>iscm</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level iscm 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[iscm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the ISCM Syslog Message Level

    Deleting the ISCM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "iscm",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>iscm</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level iscm 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[iscm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the IS-IS Syslog Message level

    Configuring the IS-IS Syslog Message level
    
    POST http://<mgmt0_IP>/api/mo/sys/isis.json
    
    {
      "isisEntity": {
        "children": [
          {
            "isisSysLog": {
              "attributes": {
                "logLevel": "4"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <isis-items>
        <syslog-items>
          <logLevel>4</logLevel>
        </syslog-items>
      </isis-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    logging level isis 4


    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.

    MODN
    isisSysLog sys/isis/syslog
    isisEntity sys/isis


    isisSysLog Properties

    The following table contains information about the isisSysLog 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 NameData TypeDescriptionValues
    logLevelisis:LogL
    (scalar:Uint32)
    Holds IS-IS Logging Level
    RANGE: [0 , 7]


    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 the IS-IS Syslog Message level

    Deleting the IS-IS Syslog Message level
    
    POST http://<mgmt0_IP>/api/mo/sys/isis.json
    
    {
      "isisEntity": {
        "children": [
          {
            "isisSysLog": {
              "attributes": {
                "logLevel": "deleted"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <isis-items>
        <syslog-items nc:operation="delete">
        </syslog-items>
      </isis-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    no logging level isis 4


    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.

    MODN
    isisSysLog sys/isis/syslog
    isisEntity sys/isis


    isisSysLog Properties

    The following table contains information about the isisSysLog 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 NameData TypeDescriptionValues
    logLevelisis:LogL
    (scalar:Uint32)
    Holds IS-IS Logging Level
    RANGE: [0 , 7]


    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 the L3VM Syslog Message Level

    Configuring the L3VM Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "l3vm",
                "severityLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>l3vm</facilityName>
              <severityLevel>critical</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level l3vm 2


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[l3vm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the L3VM Syslog Message Level

    Deleting the L3VM Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "l3vm",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>l3vm</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).

    Note: Issuing a DELETE operation reverts the severityLevel property to the default value (5 - notifications).


    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 level l3vm 2


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[l3vm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the LACP Syslog Message Level

    Configuring the LACP Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "lacp",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>lacp</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level lacp 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[lacp]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the LACP Syslog Message Level

    Deleting the LACP Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "lacp",
                "severityLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>lacp</facilityName>
              <severityLevel>critical</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level lacp 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[lacp]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the LIM Syslog Message Level

     Configuring the LIM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "lim",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>lim</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level lim 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[lim]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: critical


    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 the LIM Syslog Message Level

     Deleting the LIM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "lim",
                "severityLevel": "critical",
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>lim</facilityName>
              <severityLevel>critical</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level lim 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[lim]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the Line Card Manager Syslog Message Level

    Configuring the Line Card Manager Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/lcm.json
    
    {
      "lcmEntity": {
        "children": [
          {
            "lcmModLogLevel": {
              "attributes": {
                "loggingLevel": "1"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <lcm-items>
        <modloglevel-items>
          <loggingLevel>1</loggingLevel>
        </modloglevel-items>
      </lcm-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    logging level module 1


    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.

    MODN
    lcmEntitysys/lcm
    lcmModLogLevelsys/lcm/modloglevel


    lcmModLogLevel Properties

    The following table contains information about the lcmModLogLevel 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 NameData TypeDescriptionValues
    loggingLevellcm:LoggingLevel
    (scalar:Uint16)
    Logging Level
    RANGE: [0 , 7]
    DEFAULT: 5


    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

    For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Deleting the Line Card Manager Syslog Message Level

    Deleting the Line Card Manager Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/lcm.json
    
    {
      "lcmEntity": {
        "children": [
          {
            "lcmModLogLevel": {
              "attributes": {
                "loggingLevel": "5"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <lcm-items>
        <modloglevel-items>
          <loggingLevel>5</loggingLevel>
        </modloglevel-items>
      </lcm-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    no logging level module 1


    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.

    MODN
    lcmEntitysys/lcm
    lcmModLogLevelsys/lcm/modloglevel


    lcmModLogLevel Properties

    The following table contains information about the lcmModLogLevel 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 NameData TypeDescriptionValues
    loggingLevellcm:LoggingLevel
    (scalar:Uint16)
    Logging Level
    RANGE: [0 , 7]
    DEFAULT: 5


    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

    For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Configuring the MFDM Syslog Message level

    Configuring the MFDM Syslog Message level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "mfdm",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>mfdm</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level mfdm 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[mfdm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the MFDM Syslog Message level

    Deleting the MFDM Syslog Message level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "mfdm",
                "severityLevel": "critical",
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>mfdm</facilityName>
              <severityLevel>critical</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level mfdm 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[mfdm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the MIG UTILS Daemon Syslog Message Level

    Configuring the MIG UTILS Daemon Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "capLogLevel": {
              "attributes": {
                "loggingLevel": "1"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <caploglevel-items>
        <loggingLevel>1</loggingLevel>
      </caploglevel-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    logging level capability 1


    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.

    MODN
    capLogLevelsys/caploglevel


    capLogLevel Properties

    The following table contains information about the capLogLevel 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 NameData TypeDescriptionValues
    loggingLevelcap:LoggingLevel
    (scalar:Uint16)
    Logging Level
    RANGE: [0 , 7]
    DEFAULT: 2


    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

    For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Deleting the MIG UTILS Daemon Syslog Message Level

    Deleting the MIG UTILS Daemon Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "capLogLevel": {
              "attributes": {
                "loggingLevel": "2"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <caploglevel-items>
        <loggingLevel>2</loggingLevel>
      </caploglevel-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    no logging level capability 1


    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.

    MODN
    capLogLevelsys/caploglevel


    capLogLevel Properties

    The following table contains information about the capLogLevel 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 NameData TypeDescriptionValues
    loggingLevelcap:LoggingLevel
    (scalar:Uint16)
    Logging Level
    RANGE: [0 , 7]
    DEFAULT: 2


    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

    For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Configuring MVSH Syslog Message Level

    Configuring MVSH Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "mvsh",
                "severityLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>mvsh</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level mvsh 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[mvsh]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 MVSH Syslog Message Level

    Deleting MVSH Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "mvsh",
                "severityLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>mvsh</facilityName>
              <severityLevel>critical</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level mvsh 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[mvsh]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the NAT Syslog Message Level

    Configuring the NAT Syslog Message Level  
    
    POST http://<mgmt0_IP>/api/mo/sys/nat.json
    
    {
      "natEntity": {
        "children": [
          {
            "natInst": {
              "attributes": {
                "loggingLevel": "alert"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <nat-items>
        <inst-items>
          <loggingLevel>alert</loggingLevel>
        </inst-items>
      </nat-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    logging level nat 1


    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.

    MODN
    natEntitysys/nat
    natInstsys/nat/inst


    natInst Properties

    The following table contains information about the natInst 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 NameData TypeDescriptionValues
    loggingLevelarp:LoggingLevel
    (scalar:Enum8)
    Logging level information for NATSELECTION:
    0 - emergency
    1 - alert
    2 - critical
    3 - error
    4 - warning
    5 - notification
    6 - informational
    7 - debug
    DEFAULT: warning


    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

    For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Deleting the NAT Syslog Message Level

    Deleting the NAT Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/nat.json
    
    {
      "natEntity": {
        "children": [
          {
            "natInst": {
              "attributes": {
                "loggingLevel": "warning"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <nat-items>
        <inst-items>
          <loggingLevel>warning</loggingLevel>
        </inst-items>
      </nat-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    no logging level nat 1


    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.

    MODN
    natEntitysys/nat
    natInstsys/nat/inst


    natInst Properties

    The following table contains information about the natInst 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 NameData TypeDescriptionValues
    loggingLevelarp:LoggingLevel
    (scalar:Enum8)
    Logging level information for NATSELECTION:
    0 - emergency
    1 - alert
    2 - critical
    3 - error
    4 - warning
    5 - notification
    6 - informational
    7 - debug
    DEFAULT: warning


    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

    For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Configuring NXOS SDK Syslog Message Level

    Configuring NXOS SDK Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "nxsdk",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>nxsdk</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level nxsdk 7


    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.

    MODN
    loggingFacility sys/logging/loglevel/facility-[nxsdk]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 NXOS SDK Syslog Message Level

    Deleting NXOS SDK Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "nxsdk",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>nxsdk</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level nxsdk 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[nxsdk]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the OpenFlow Syslog Message Level

    Configuring the OpenFlow Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "children": [
                      {
                        "loggingFacility": {
                          "attributes": {
                            "facilityName": "openflow",
                            "severityLevel": "debugging"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>openflow</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
     </logging-items>
    

    Note: This example was added in Release 9.3(3).


    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 level openflow ?


    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.

    MODN
    topSystem sys
    loggingLogging sys/logging
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[openflow]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 OSPF Syslog Message Level

    Configuring OSPF Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "ospf",
                "severityLevel": "information"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>ospf</facilityName>
              <severityLevel>information</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level ospf 6


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[ospf]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 OSPF Syslog Message Level

    Deleting OSPF Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "children": [
                      {
                        "loggingFacility": {
                          "attributes": {
                            "facilityName": "ospf",
                            "severityLevel": "notifications"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>ospf</facilityName>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level ospf 6


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[ospf]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring OSPFv3 Syslog Message Level

    Configuring OSPFv3 Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "ospfv3",
                "severityLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>ospfv3</facilityName>
              <severityLevel>critical</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level ospfv3 2


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[ospfv3]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 OSPFv3 Syslog Message Level

    Deleting OSPFv3 Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "children": [
                      {
                        "loggingFacility": {
                          "attributes": {
                            "facilityName": "ospfv3",
                            "severityLevel": "notifications"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>ospfv3</facilityName>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level ospfv3 2


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[ospfv3]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the Packet Manager Syslog Message Level

    Configuring the Packet Manager Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/pktmgr.json
    
    {
      "pktmgrEntity": {
        "children": [
          {
            "pktmgrInst": {
              "attributes": {
                "loggingLevel": "error"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <pktmgr-items>
        <inst-items>
          <loggingLevel>error</loggingLevel>
        </inst-items>
      </pktmgr-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    logging level pktmgr 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.

    MODN
    pktmgrEntitysys/pktmgr
    pktmgrInstsys/pktmgr/inst


    pktmgrInst Properties

    The following table contains information about the pktmgrInst 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 NameData TypeDescriptionValues
    loggingLevelarp:LoggingLevel
    (scalar:Enum8)
    Logging LevelSELECTION:
    0 - emergency
    1 - alert
    2 - critical
    3 - error
    4 - warning
    5 - notification
    6 - informational
    7 - debug
    DEFAULT: critical


    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

    For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Deleting the Packet Manager Syslog Message Level

    Deleting the Packet Manager Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/pktmgr.json
    
    {
      "pktmgrEntity": {
        "children": [
          {
            "pktmgrInst": {
              "attributes": {
                "loggingLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <pktmgr-items>
        <inst-items>
          <loggingLevel>critical</loggingLevel>
        </inst-items>
      </pktmgr-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    no logging level pktmgr 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.

    MODN
    pktmgrEntitysys/pktmgr
    pktmgrInstsys/pktmgr/inst


    pktmgrInst Properties

    The following table contains information about the pktmgrInst 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 NameData TypeDescriptionValues
    loggingLevelarp:LoggingLevel
    (scalar:Enum8)
    Logging LevelSELECTION:
    0 - emergency
    1 - alert
    2 - critical
    3 - error
    4 - warning
    5 - notification
    6 - informational
    7 - debug
    DEFAULT: critical


    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

    For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Configuring the PFSTAT Syslog Message Level

    Configuring the PFSTAT Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "pfstat",
                "loggingEnable": "enabled",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>pfstat</facilityName>
              <loggingEnable>enabled</loggingEnable>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level pfstat 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[pfstat]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    loggingEnablelogging:Boolean
    (scalar:Enum8)
    Logging level all state disabled/enabledSELECTION:
    0 - disabled
    1 - enabled
    DEFAULT: disabled
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the PFSTAT Syslog Message Level

    Deleting the PFSTAT Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "pfstat",
                "loggingEnable": "disabled"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>pfstat</facilityName>
              <loggingEnable>disabled</loggingEnable>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level pfstat 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[pfstat]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    loggingEnablelogging:Boolean
    (scalar:Enum8)
    Logging level all state disabled/enabledSELECTION:
    0 - disabled
    1 - enabled
    DEFAULT: disabled


    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 the PIXM Syslog Message Level

    Configuring the PIXM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "pixm",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>pixm</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level pixm 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[pixm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the PIXM Syslog Message Level

    Deleting the PIXM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "pixm",
                "severityLevel": "warnings"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>pixm</facilityName>
              <severityLevel>warnings</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level pixm 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[pixm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the Platform Manager Logging Level

    Configuring the Platform Manager Logging Level
    
    POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
    
    {
      "platformEntity": {
        "children": [
          {
            "platformLogLevel": {
              "attributes": {
                "loggingLevel": "1"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <pltfm-items>
        <loglevel-items>
          <loggingLevel>1</loggingLevel>
        </loglevel-items>
      </pltfm-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    logging level platform 1


    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.

    MODN
    platformEntity sys/pltfm
    platformLogLevel sys/pltfm/loglevel


    platformLogLevel Properties

    The following table contains information about the platformLogLevel 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 NameData TypeDescriptionValues
    loggingLevelplatform:LoggingLevel
    (scalar:Uint16)
    Logging Level
    RANGE: [0 , 7]
    DEFAULT: 5


    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 the Platform Manager Logging Level

    Deleting the Platform Manager Logging Level
    
    POST http://<mgmt0_IP>/api/mo/sys/pltfm.json
    
    {
      "platformEntity": {
        "children": [
          {
            "platformLogLevel": {
              "attributes": {
                "loggingLevel": "5"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <pltfm-items>
        <loglevel-items>
          <loggingLevel>5</loggingLevel>
        </loglevel-items>
      </pltfm-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    no logging level platform 1


    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.

    MODN
    platformEntity sys/pltfm
    platformLogLevel sys/pltfm/loglevel


    platformLogLevel Properties

    The following table contains information about the platformLogLevel 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 NameData TypeDescriptionValues
    loggingLevelplatform:LoggingLevel
    (scalar:Uint16)
    Logging Level
    RANGE: [0 , 7]
    DEFAULT: 5


    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 the PLTFM Config Syslog Message Level

    Configuring the PLTFM Config Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "pltfm_config",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>pltfm_config</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level pltfm_config 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[pltfm_config]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the PLTFM Config Syslog Message Level

    Deleting the PLTFM Config Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "children": [
                      {
                        "loggingFacility": {
                          "attributes": {
                            "facilityName": "pltfm_config",
                            "severityLevel": "warnings"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
        <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>pltfm_config</facilityName>
              <severityLevel>warnings</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level pltfm_config 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[pltfm_config]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the RES_MGR Syslog Message Level

    Configuring the RES_MGR Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "res_mgr",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>res_mgr</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level res_mgr 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[res_mgr]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the RES_MGR Syslog Message Level

    Deleting the RES_MGR Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "res_mgr",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>res_mgr</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level res_mgr 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[res_mgr]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the RPM Syslog Message Level

    Configuring the RPM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "rpm",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>rpm</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level rpm 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[rpm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the RPM Syslog Message Level

    Deleting the RPM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "children": [
                      {
                        "loggingFacility": {
                          "attributes": {
                            "facilityName": "rpm",
                            "severityLevel": "notifications"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>rpm</facilityName>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level rpm 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[rpm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the Security Syslog Message Level

    Configuring the Security Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "securitySecurity": {
              "attributes": {
                "loggingLevel": "alert"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <security-items>
        <loggingLevel>alert</loggingLevel>
      </security-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    logging level security 1


    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.

    MODN
    securitySecuritysys/security


    securitySecurity Properties

    The following table contains information about the securitySecurity 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 NameData TypeDescriptionValues
    loggingLevelarp:LoggingLevel
    (scalar:Enum8)
    Security Logging LevelSELECTION:
    0 - emergency
    1 - alert
    2 - critical
    3 - error
    4 - warning
    5 - notification
    6 - informational
    7 - debug
    DEFAULT: error


    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

    For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Deleting the Security Syslog Message Level

    Deleting the Security Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "securitySecurity": {
              "attributes": {
                "loggingLevel": "error"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <security-items>
        <loggingLevel>error</loggingLevel>
      </security-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    no logging level security


    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.

    MODN
    securitySecuritysys/security


    securitySecurity Properties

    The following table contains information about the securitySecurity 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 NameData TypeDescriptionValues
    loggingLevelarp:LoggingLevel
    (scalar:Enum8)
    Security Logging LevelSELECTION:
    0 - emergency
    1 - alert
    2 - critical
    3 - error
    4 - warning
    5 - notification
    6 - informational
    7 - debug
    DEFAULT: error


    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

    For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html

    For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

    Configuring the SKSD Syslog Message Level

    Configuring the SKSD Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "sksd",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>sksd</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level sksd 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[sksd]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the SKSD Syslog Message Level

    Deleting the SKSD Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
        "loggingLogLevel": {
            "children": [
                      {
                "loggingFacility": {
                  "attributes": {
                    "facilityName": "sksd",
                    "severityLevel": "errors"
    }}}]}}
      
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>sksd</facilityName>
              <severityLevel>errors</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level sksd 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[sksd]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the SNMP Syslog Message Level

    Configuring the Syslog Filter Level for SNMP Messages 
    
    POST http://<mgmt0_IP>/api/mo/sys/snmp.json
    
    {
      "snmpEntity": {
        "children": [
          {
            "snmpInst": {
              "attributes": {
                "loggingLevel": "emergencies"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <snmp-items>
        <inst-items>
          <loggingLevel>emergencies</loggingLevel>
        </inst-items>
      </snmp-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    logging level snmpd 0


    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.

    MODN
    snmpEntity sys/snmp
    snmpInst sys/snmp/inst


    snmpInst Properties

    The following table contains information about the snmpInst 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 NameData TypeDescriptionValues
    loggingLevelsnmp:SnmpLogLevel
    (scalar:Enum8)
    Set level for SNMP syslog messagesSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: critical


    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 the SNMP Syslog Message Level

    Deleting the SNMP Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/snmp.json
    
    {
      "snmpEntity": {
        "children": [
          {
            "snmpInst": {
              "attributes": {
                "loggingLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <snmp-items>
        <inst-items>
          <loggingLevel>critical</loggingLevel>
        </inst-items>
      </snmp-items>
    </System>
    

    Note: This example was added in Release 9.3(1).


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

    no logging level snmpd 0


    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.

    MODN
    snmpEntity sys/snmp
    snmpInst sys/snmp/inst


    snmpInst Properties

    The following table contains information about the snmpInst 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 NameData TypeDescriptionValues
    loggingLevelsnmp:SnmpLogLevel
    (scalar:Enum8)
    Set level for SNMP syslog messagesSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: critical


    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 the Track Syslog Message Level

    Configuring the Track Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "track",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>track</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level track 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[track]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 a Track Syslog Message Level

    Deleting a Track Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "track",
                "severityLevel": "errors"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>track</facilityName>
              <severityLevel>errors</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level track 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[track]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the Tunnel Syslog Message Level

    Configuring the Tunnel Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "tunnel",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>tunnel</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level tunnel 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[tunnel]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the Tunnel Syslog Message Level

    Deleting the Tunnel Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "tunnel",
                "severityLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>tunnel</facilityName>
              <severityLevel>critical</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level tunnel 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[tunnel]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the UFDM Syslog Message Level

    Configuring the UFDM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "ufdm",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>ufdm</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level ufdm 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[ufdm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the UFDM Syslog Message Level

    Deleting the UFDM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "ufdm",
                "severityLevel": "errors"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>ufdm</facilityName>
              <severityLevel>errors</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level ufdm 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[ufdm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the VMM Syslog Message Level

    Configuring the VMM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "vmm",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>vmm</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level vmm 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[vmm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the VMM Syslog Message Level

    Deleting the VMM Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "vmm",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>vmm</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level vmm 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[vmm]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the VNTAG_MGR Syslog Message Level

    Configuring the VNTAG_MGR Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "children": [
                      {
                        "loggingFacility": {
                          "attributes": {
                            "facilityName": "vntag_mgr",
                            "severityLevel": "alerts"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>vntag_mgr</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3)


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the opt-left corner of the pane on the right to view the JSON payload. Click the YANG tab to view the XML payload.

    logging level vntag_mgr 1


    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.

    MODN
    topSystem sys
    loggingLogging sys/logging
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-{[facilityName]}


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the VNTAG_MGR Syslog Message Level

    Deleting the VNTAG_MGR Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys.json
    
    {
      "topSystem": {
        "children": [
          {
            "loggingLogging": {
              "children": [
                {
                  "loggingLogLevel": {
                    "children": [
                      {
                        "loggingFacility": {
                          "attributes": {
                            "facilityName": "vntag_mgr",
                            "severityLevel": "notifications"
                          }
                        }
                      }
                    ]
                  }
                }
              ]
            }
          }
        ]
      }
    }
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>vntag_mgr</facilityName>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3)


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the opt-left corner of the pane on the right to view the JSON payload. Click the YANG tab to view the XML payload.

    no logging level vntag_mgr 1

    https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html


    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.

    MODN
    topSystem sys
    loggingLogging sys/logging
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-{[facilityName]}


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the VRRP-CFG Syslog Message Level

    Configuring the VRRP-CFG Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "vrrp-cfg",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>vrrp-cfg</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level vrrp-cfg 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[vrrp-cfg]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the VRRP-CFG Syslog Message Level

    Deleting the VRRP-CFG Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "vrrp-cfg",
                "severityLevel": "errors"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>vrrp-cfg</facilityName>
              <severityLevel>errors</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level vrrp-cfg 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[vrrp-cfg]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the VRRPv3 Syslog Message Level

    Configuring the VRRPv3 Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "vrrpv3",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>vrrpv3</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level vrrpv3 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[vrrpv3]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the VRRPv3 Syslog Message Level

    Deleting the VRRPv3 Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "vrrpv3",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>vrrpv3</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level vrrpv3 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[vrrpv3]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the XML Agent Server Syslog Message Level

    Configuring the XML Agent Server Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "xmlma",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>xmlma</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level xml server 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[xmlma]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the XML Agent Server Syslog Message Level

    Deleting the XML Agent Server Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "xmlma",
                "severityLevel": "errors"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>xmlma</facilityName>
              <severityLevel>errors</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System> 
    

    Note: This example was added in Release 9.3(3).


    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 level xml server 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[xmlma]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the XML Master Agent Syslog Message Level

    Configuring the XML Master Agent Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "xmlma",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>xmlma</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level xmlma 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[xmlma]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the XML Master Agent Syslog Message Level

    Deleting the XML Master Agent Syslog Message Level
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "xmlma",
                "severityLevel": "errors"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>xmlma</facilityName>
              <severityLevel>errors</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 level xmlma 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[xmlma]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA 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

    Configuring the Rate Limit for Log Messages

    Configuring the Rate Limit for Log Messages
    
    POST http://<mgmt0_IP>/api/mo/sys/syslog.json
    
    {
      "syslogSyslog": {
        "children": [
          {
            "syslogLoggingRateLimit": {
              "attributes": {
                "ratelimit": "enabled"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <syslog-items>
        <loggingratelimit-items>
          <ratelimit>enabled</ratelimit>
        </loggingratelimit-items>
      </syslog-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 rate-limit


    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.

    MODN
    syslogSyslog sys/syslog
    syslogLoggingRateLimit sys/syslog/loggingratelimit


    syslogLoggingRateLimit Properties

    The following table contains information about the syslogLoggingRateLimit 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 NameData TypeDescriptionValues
    ratelimitcallhome:Boolean
    (scalar:Enum8)
    rate-limit of syslog messagesSELECTION:
    0 - disabled
    1 - enabled
    DEFAULT: enabled


    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

    Disabling the Rate Limit for Log Messages

    Deleting the Rate Limit for Log Messages
    
    POST http://<mgmt0_IP>/api/mo/sys/syslog.json
    
    {
      "syslogSyslog": {
        "children": [
          {
            "syslogLoggingRateLimit": {
              "attributes": {
                "ratelimit": "disabled"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <syslog-items>
        <loggingratelimit-items>
          <ratelimit>disabled</ratelimit>
        </loggingratelimit-items>
      </syslog-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 rate-limit


    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.

    MODN
    syslogSyslog sys/syslog
    syslogLoggingRateLimit sys/syslog/loggingratelimit


    syslogLoggingRateLimit Properties

    The following table contains information about the syslogLoggingRateLimit 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 NameData TypeDescriptionValues
    ratelimitcallhome:Boolean
    (scalar:Enum8)
    rate-limit of syslog messagesSELECTION:
    0 - disabled
    1 - enabled
    DEFAULT: enabled


    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 DNS Refresh Interval for Remote Syslog Server Hostnames

    Configuring DNS Refresh Interval for Remote Syslog Server Hostnames 
    
    POST http://<mgmt0_IP>/api/mo/sys/syslog.json
    
    {
      "syslogSyslog": {
        "children": [
          {
            "syslogDnsInterval": {
              "attributes": {
                "dnsRefreshInterval": "255"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <syslog-items>
        <dnsinterval-items>
          <dnsRefreshInterval>255</dnsRefreshInterval>
        </dnsinterval-items>
      </syslog-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 dns-refresh-interval 255


    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.

    MODN
    syslogSyslog sys/syslog
    syslogDnsInterval sys/syslog/dnsinterval
    dnsRefreshInterval:255


    syslogDnsInterval Properties

    The following table contains information about the syslogDnsInterval 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 NameData TypeDescriptionValues
    dnsRefreshIntervalscalar:Uint32
    DNS refresh interval for remote syslog server hostnames
    RANGE: [10 , 1440]
    DEFAULT: 60


    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

    Disabling DNS Refresh Interval for Remote Syslog Server Hostnames

    Deleting DNS Refresh Interval for Remote Syslog Server Hostnames 
    
    POST http://<mgmt0_IP>/api/mo/sys/syslog.json
    
    {
      "syslogSyslog": {
        "children": [
          {
            "syslogDnsInterval": {
              "attributes": {
                "dnsRefreshInterval": "60"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <syslog-items>
        <dnsinterval-items>
          <dnsRefreshInterval>60</dnsRefreshInterval>
        </dnsinterval-items>
      </syslog-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 dns-refresh-interval 255


    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.

    MODN
    syslogSyslog sys/syslog
    syslogDnsInterval sys/syslog/dnsinterval
    dnsRefreshInterval:60


    syslogDnsInterval Properties

    The following table contains information about the syslogDnsInterval 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 NameData TypeDescriptionValues
    dnsRefreshIntervalscalar:Uint32
    DNS refresh interval for remote syslog server hostnames
    RANGE: [10 , 1440]
    DEFAULT: 60


    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 the Hostname as Origin-Id of Logging Messages

    Configuring the Hostname as Origin-Id of Logging Messages
    
    POST http://<mgmt0_IP>/api/mo/sys/syslog.json
    
    {
      "syslogSyslog": {
        "children": [
          {
            "syslogOriginid": {
              "attributes": {
                "idtype": "hostname"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <syslog-items>
        <originid-items>
          <idtype>hostname</idtype>
        </originid-items>
      </syslog-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 origin-id hostname


    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.

    MODN
    syslogSyslog sys/syslog
    syslogOriginid sys/syslog/originid


    syslogOriginid Properties

    The following table contains information about the syslogOriginid 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 NameData TypeDescriptionValues
    idtypesyslog:OriginIdType
    (scalar:Enum8)
    OriginId type for Hostname, IP or StringSELECTION:
    0 - unknown
    1 - hostname
    2 - ip
    3 - string
    DEFAULT: unknown


    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 the Hostname as Origin-Id of Logging Messages

    Deleting the Hostname as Origin-Id of Logging Messages
    
    POST http://<mgmt0_IP>/api/mo/sys/syslog.json
    
    {
      "syslogSyslog": {
        "children": [
          {
            "syslogOriginid": {
              "attributes": {
                "status": "deleted"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <syslog-items>
        <originid-items nc:operation="delete">
        </originid-items>
      </syslog-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 origin-id hostname


    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.

    MODN
    syslogSyslog sys/syslog
    syslogOriginid sys/syslog/originid


    syslogOriginid Properties

    The following table contains information about the syslogOriginid 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 NameData TypeDescriptionValues
    statusmo: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 the IP Address as Origin-Id of Logging Messages

    Configuring the IP Address as Origin-Id of Logging Messages
    
    POST http://<mgmt0_IP>/api/mo/sys/syslog.json
    
    {
      "syslogSyslog": {
        "children": [
          {
            "syslogOriginid": {
              "attributes": {
                "idtype": "ip",
                "idvalue": "HostName"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <syslog-items>
        <originid-items>
          <idtype>ip</idtype>
          <idvalue>HostName</idvalue>
        </originid-items>
      </syslog-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 origin-id ip HostName


    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.

    MODN
    syslogSyslog sys/syslog
    syslogOriginid sys/syslog/originid


    syslogOriginid Properties

    The following table contains information about the syslogOriginid 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 NameData TypeDescriptionValues
    idtypesyslog:OriginIdType
    (scalar:Enum8)
    OriginId type for Hostname, IP or StringSELECTION:
    0 - unknown
    1 - hostname
    2 - ip
    3 - string
    DEFAULT: unknown
    idvaluesyslog:OriginIdValue
    (string:Basic)
    OriginId value for Hostname, IP or String
    MAX SIZE: 199


    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 a Text String as Origin Id of Logging Messages

    Deleting a Text String as Origin Id of Logging Messages
    
    POST http://<mgmt0_IP>/api/mo/sys/syslog.json
    
    {
      "syslogSyslog": {
        "children": [
          {
            "syslogOriginid": {
              "attributes": {
                "status": "deleted"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <syslog-items>
        <originid-items nc:operation="delete">
        </originid-items>
      </syslog-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 origin-id string SampleString_123


    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.

    MODN
    syslogSyslog sys/syslog
    syslogOriginid sys/syslog/originid


    syslogOriginid Properties

    The following table contains information about the syslogOriginid 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 NameData TypeDescriptionValues
    statusmo: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 a Text String as Origin Id of Logging Messages

    Configuring a Text String as Origin Id of Logging Messages
    
    POST http://<mgmt0_IP>/api/mo/sys/syslog.json
    
    {
      "syslogSyslog": {
        "children": [
          {
            "syslogOriginid": {
              "attributes": {
                "idtype": "string",
                "idvalue": "SampleString_123"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <syslog-items>
        <originid-items>
          <idtype>string</idtype>
          <idvalue>SampleString_123</idvalue>
        </originid-items>
      </syslog-items>
    </System>
    

    Note: This example was added in Release 9.3(3).


    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 origin-id string SampleString_123


    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.

    MODN
    syslogSyslog sys/syslog
    syslogOriginid sys/syslog/originid


    syslogOriginid Properties

    The following table contains information about the syslogOriginid 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 NameData TypeDescriptionValues
    idtypesyslog:OriginIdType
    (scalar:Enum8)
    OriginId type for Hostname, IP or StringSELECTION:
    0 - unknown
    1 - hostname
    2 - ip
    3 - string
    DEFAULT: unknown
    idvaluesyslog:OriginIdValue
    (string:Basic)
    OriginId value for Hostname, IP or String
    MAX SIZE: 199


    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 the MSDP Syslog Message Level

    Configuring the MSDP Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "msdp",
                "severityLevel": "debugging"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>msdp</facilityName>
              <severityLevel>debugging</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(5).


    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 level ip msdp 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[msdp]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the MSDP Syslog Message Level

    Deleting the MSDP Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "msdp",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>msdp</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(5).


    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 level ip msdp 7


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[msdp]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the MSDP Syslog Message Level

    Configuring the MSDP Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "msdp",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>msdp</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(5).


    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 level ip msdp 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[msdp]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 the MSDP Syslog Message Level

    Deleting the MSDP Syslog Message Level 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "msdp",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>msdp</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(5).


    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 level ip msdp 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[msdp]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 Global IPv6 Multicast Forwarding

    Configuring Global IPv6 Multicast Forwarding 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "mcastfwdv6",
                "severityLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>mcastfwdv6</facilityName>
              <severityLevel>critical</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(5).


    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 level mcastfwdv6 2


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[mcastfwdv6]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 Global IPv6 Multicast Forwarding

    Deleting Global IPv6 Multicast Forwarding 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "mcastfwdv6",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>mcastfwdv6</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(5).


    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 level mcastfwdv6 2


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[mcastfwdv6]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 Message for Global IPv6 Multicast Forwarding

    Configuring Syslog Message for Global IPv6 Multicast Forwarding 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "mcastfwdv6",
                "severityLevel": "critical"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>mcastfwdv6</facilityName>
              <severityLevel>critical</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(5).


    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 level mfwdv6 2


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[mcastfwdv6]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 Message for Global IPv6 Multicast Forwarding

    Deleting Syslog Message for Global IPv6 Multicast Forwarding 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "mcastfwdv6",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>mcastfwdv6</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(5).


    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 level mfwdv6 2


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[mcastfwdv6]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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 Filter Level for OSPF

    Configuring Syslog Filter Level for OSPF 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "ospf",
                "severityLevel": "alerts"
    }}}]}}
    
    {
        :
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>ospf</facilityName>
              <severityLevel>alerts</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(5).


    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 level ospf 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[ospf]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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

    Note: All theses commands apply for VRF as well.

    Deleting Syslog Filter Level for OSPF

    Deleting Syslog Filter Level for OSPF 
    
    POST http://<mgmt0_IP>/api/mo/sys/logging/loglevel.json
    
    {
      "loggingLogLevel": {
        "children": [
          {
            "loggingFacility": {
              "attributes": {
                "facilityName": "ospf",
                "severityLevel": "notifications"
    }}}]}}
    
    {
        
    }
    
    <System>
      <logging-items>
        <loglevel-items>
          <facility-items>
            <Facility-list>
              <facilityName>ospf</facilityName>
              <severityLevel>notifications</severityLevel>
            </Facility-list>
          </facility-items>
        </loglevel-items>
      </logging-items>
    </System>
    

    Note: This example was added in Release 9.3(5).


    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 level ospf 1


    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.

    MODN
    loggingLogLevel sys/logging/loglevel
    loggingFacility sys/logging/loglevel/facility-[ospf]


    loggingFacility Properties

    The following table contains information about the loggingFacility 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 NameData TypeDescriptionValues
    facilityNamecomp:DelimitedString
    (string:Basic)
    Facility Name of individual processes subscribed for logging levelA sequence of characters
    severityLevelsyslog:Severity
    (scalar:Enum8)
    Logging severity level for individual facility nameSELECTION:
    0 - emergencies
    1 - alerts
    2 - critical
    3 - errors
    4 - warnings
    5 - notifications
    6 - information
    7 - debugging
    DEFAULT: notifications


    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