Configuring a UDP-Jitter Operation

Configuring a Destination Port

Configuring a Destination Port 
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "45299"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>45299</dstPort>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  dest-port 45299


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]


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 Acceptable Clock Synchronization Error in Oneway Measurement

Configuring the Acceptable Clock Synchronization Error in Oneway Measurement 
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "absoluteClockTolerance": "84339",
                  "destip": "1.1.1.1",
                  "dstPort": "2345"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <absoluteClockTolerance>84339</absoluteClockTolerance>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  clock-tolerance ntp oneway absolute 84339


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
absoluteClockTolerancesla:ClockToleranceAbsolute
(scalar:Uint32)
Oneway NTP Clock Tolerance absolute Value
RANGE: [0 , 100000]
DEFAULT: 0
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]


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 Default Acceptable Clock Synchronization Error

Configuring the Default Acceptable Clock Synchronization Error
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "absoluteClockTolerance": "0",
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "percentClockTolerance": "0"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <absoluteClockTolerance>0</absoluteClockTolerance>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <percentClockTolerance>0</percentClockTolerance>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  default clock-tolerance


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
absoluteClockTolerancesla:ClockToleranceAbsolute
(scalar:Uint32)
Oneway NTP Clock Tolerance absolute Value
RANGE: [0 , 100000]
DEFAULT: 0
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
percentClockTolerancesla:ClockTolerancePercent
(scalar:Uint32)
Oneway NTP Clock Tolerance Value in percentage
RANGE: [0 , 100]
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 Acceptable Clock Synchronization Error in Oneway Measurement

Deleting the Acceptable Clock Synchronization Error in Oneway Measurement 
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "absoluteClockTolerance": "0",
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "percentClockTolerance": "0"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <absoluteClockTolerance>0</absoluteClockTolerance>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <percentClockTolerance>0</percentClockTolerance>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no clock-tolerance ntp oneway absolute 84339


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
absoluteClockTolerancesla:ClockToleranceAbsolute
(scalar:Uint32)
Oneway NTP Clock Tolerance absolute Value
RANGE: [0 , 100000]
DEFAULT: 0
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
percentClockTolerancesla:ClockTolerancePercent
(scalar:Uint32)
Oneway NTP Clock Tolerance Value in percentage
RANGE: [0 , 100]
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 Acceptable Clock Synchronization Error in Oneway Measurement as a Percent Value

Configuring the Acceptable Clock Synchronization Error in Oneway Measurement as a Percent Value 
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "percentClockTolerance": "60"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <percentClockTolerance>60</percentClockTolerance>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  clock-tolerance ntp oneway percent 60


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
percentClockTolerancesla:ClockTolerancePercent
(scalar:Uint32)
Oneway NTP Clock Tolerance Value in percentage
RANGE: [0 , 100]
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 Acceptable Clock Synchronization Error in Oneway Measurement as a Percent Value

Deleting the Acceptable Clock Synchronization Error in Oneway Measurement as a Percent Value 
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "absoluteClockTolerance": "0",
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "percentClockTolerance": "0"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <absoluteClockTolerance>0</absoluteClockTolerance>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <percentClockTolerance>0</percentClockTolerance>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no clock-tolerance ntp oneway percent 60


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
absoluteClockTolerancesla:ClockToleranceAbsolute
(scalar:Uint32)
Oneway NTP Clock Tolerance absolute Value
RANGE: [0 , 100000]
DEFAULT: 0
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
percentClockTolerancesla:ClockTolerancePercent
(scalar:Uint32)
Oneway NTP Clock Tolerance Value in percentage
RANGE: [0 , 100]
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 Frequency in Seconds

Configuring the Frequency in Seconds
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "frequency": "597709"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <frequency>597709</frequency>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  frequency 597709


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
frequencysla:Frequency
(scalar:Uint32)
Frequency of an operation - The interval at which the configured destination is tracked by the probe. Frequency in seconds(default value is 60). Minimum frequency value for an IP SLAs HTTP probe operation is 60 seconds but 1 second for other probes.
RANGE: [0 , 604800]
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 Default Frequency

Configuring the Default Frequency
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "frequency": "60"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <frequency>60</frequency>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  default frequency


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
frequencysla:Frequency
(scalar:Uint32)
Frequency of an operation - The interval at which the configured destination is tracked by the probe. Frequency in seconds(default value is 60). Minimum frequency value for an IP SLAs HTTP probe operation is 60 seconds but 1 second for other probes.
RANGE: [0 , 604800]
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

Deleting the Frequency in Seconds

Deleting the Frequency in Seconds
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "frequency": "60"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <frequency>60</frequency>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no frequency 597709


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
frequencysla:Frequency
(scalar:Uint32)
Frequency of an operation - The interval at which the configured destination is tracked by the probe. Frequency in seconds(default value is 60). Minimum frequency value for an IP SLAs HTTP probe operation is 60 seconds but 1 second for other probes.
RANGE: [0 , 604800]
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 Operation Packet Priority

Configuring the Operation Packet Priority
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "operationPktPriority": "high"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <operationPktPriority>high</operationPktPriority>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  operation-packet-priority high


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
operationPktPrioritysla:OpPktPriority
(scalar:Enum8)
Operation Packet PrioritySELECTION:
0 - none
1 - normal
2 - high
DEFAULT: normal


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 Default Operation Packet Priorities

Configuring the Default Operation Packet Priorities
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "operationPktPriority": "normal"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <operationPktPriority>normal</operationPktPriority>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  default operation-packet-priority


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
operationPktPrioritysla:OpPktPriority
(scalar:Enum8)
Operation Packet PrioritySELECTION:
0 - none
1 - normal
2 - high
DEFAULT: normal


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 Operation Packet Priority

Deleting the Operation Packet Priority
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "operationPktPriority": "normal"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <operationPktPriority>normal</operationPktPriority>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no operation-packet-priority high


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
operationPktPrioritysla:OpPktPriority
(scalar:Enum8)
Operation Packet PrioritySELECTION:
0 - none
1 - normal
2 - high
DEFAULT: normal


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 Operation Packet Priority to Normal

Configuring the Operation Packet Priority to Normal
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "operationPktPriority": "normal"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <operationPktPriority>normal</operationPktPriority>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  operation-packet-priority normal


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
operationPktPrioritysla:OpPktPriority
(scalar:Enum8)
Operation Packet PrioritySELECTION:
0 - none
1 - normal
2 - high
DEFAULT: normal


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 Operation Packet Priority to Normal

Deleting the Operation Packet Priority to Normal
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "operationPktPriority": "normal"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <operationPktPriority>normal</operationPktPriority>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no operation-packet-priority normal


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
operationPktPrioritysla:OpPktPriority
(scalar:Enum8)
Operation Packet PrioritySELECTION:
0 - none
1 - normal
2 - high
DEFAULT: normal


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 Owner of Entry

Configuring the Owner of Entry
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "owner": "SampleString_123"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <owner>SampleString_123</owner>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  owner 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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
ownerstring:Basic
Owner string of the probe(Max size 127)A sequence of characters


Related Documentation

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

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

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

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

Configuring the Default Owner

Configuring the Default Owner
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "owner": ""
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <owner></owner>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  default owner


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
ownerstring:Basic
Owner string of the probe(Max size 127)A sequence of characters


Related Documentation

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

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

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

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

Deleting the Owner of Entry

Deleting the Owner of Entry
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "owner": ""
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <owner></owner>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no owner 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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
ownerstring:Basic
Owner string of the probe(Max size 127)A sequence of characters


Related Documentation

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

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

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

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

Configuring the UDP-Jitter Precision in Microseconds

Configuring the UDP-Jitter Precision in Microseconds
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "precision": "microseconds"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <precision>microseconds</precision>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  precision microseconds


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
precisionsla:Precision
(scalar:Enum8)
Precision configurationSELECTION:
1 - microseconds
2 - milliseconds
DEFAULT: milliseconds


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 UDP-Jitter Precision in Microseconds

Deleting the UDP-Jitter Precision in Microseconds
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "precision": "milliseconds"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <precision>milliseconds</precision>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no precision microseconds


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
precisionsla:Precision
(scalar:Enum8)
Precision configurationSELECTION:
1 - microseconds
2 - milliseconds
DEFAULT: milliseconds


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 UDP-Jitter Precision in Milliseconds

Configuring the UDP-Jitter Precision in Milliseconds
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "precision": "milliseconds"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <precision>milliseconds</precision>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  precision milliseconds


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
precisionsla:Precision
(scalar:Enum8)
Precision configurationSELECTION:
1 - microseconds
2 - milliseconds
DEFAULT: milliseconds


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 Default Precision of Measurement

Configuring the Default Precision of Measurement
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "precision": "milliseconds"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <precision>milliseconds</precision>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  default precision


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
precisionsla:Precision
(scalar:Enum8)
Precision configurationSELECTION:
1 - microseconds
2 - milliseconds
DEFAULT: milliseconds


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 UDP-Jitter Precision in Milliseconds

Deleting the UDP-Jitter Precision in Milliseconds
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "precision": "milliseconds"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <precision>milliseconds</precision>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no precision milliseconds


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
precisionsla:Precision
(scalar:Enum8)
Precision configurationSELECTION:
1 - microseconds
2 - milliseconds
DEFAULT: milliseconds


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 Data Size Request

Configuring the Data Size Request
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "reqDataSize": "9373"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <reqDataSize>9373</reqDataSize>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  request-data-size 9373


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
reqDataSizesla:ReqDataSize
(scalar:Uint32)
Sets the protocol data size in the payload of an IP SLAs operation's request packet.
RANGE: [16 , 17512]
DEFAULT: 32


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 Request Data Size

Configuring the Request Data Size
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "reqDataSize": "32"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <reqDataSize>32</reqDataSize>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  default request-data-size


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
reqDataSizesla:ReqDataSize
(scalar:Uint32)
Sets the protocol data size in the payload of an IP SLAs operation's request packet.
RANGE: [16 , 17512]
DEFAULT: 32


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 Data Size Request

Deleting the Data Size Request
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "reqDataSize": "32"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <reqDataSize>32</reqDataSize>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no request-data-size 9373


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
reqDataSizesla:ReqDataSize
(scalar:Uint32)
Sets the protocol data size in the payload of an IP SLAs operation's request packet.
RANGE: [16 , 17512]
DEFAULT: 32


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 User-Defined Tag

Configuring a User-Defined Tag
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "tag": "SampleString_123"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <tag>SampleString_123</tag>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  tag 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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
tagstring:Basic
User defined tag string (Max Size 127)A sequence of characters


Related Documentation

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

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

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

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

Deleting a User-Defined Tag

Deleting a User-Defined Tag
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "tag": ""
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <tag></tag>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no tag 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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
tagstring:Basic
User defined tag string (Max Size 127)A sequence of characters


Related Documentation

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

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

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

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

Configuring the Default User-Defined Tag

Configuring the Default User-Defined Tag
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "tag": ""
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <tag></tag>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  default tag


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
tagstring:Basic
User defined tag string (Max Size 127)A sequence of characters


Related Documentation

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

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

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

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

Configuring the Operation Threshold

Configuring the Operation Threshold
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "threshold": "10734"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <threshold>10734</threshold>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  threshold 10734


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
thresholdsla:Threshold
(scalar:Uint32)
Operation threshold - this is an upper limit for the observed RTT for the probe. RTT value of a probe exceeding the configured threshold will be marked with Overthreshold return code.
RANGE: [1 , 60000]
DEFAULT: 5000


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 Default Threshold

Configuring the Default Threshold
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "threshold": "5000"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <threshold>5000</threshold>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  default threshold


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
thresholdsla:Threshold
(scalar:Uint32)
Operation threshold - this is an upper limit for the observed RTT for the probe. RTT value of a probe exceeding the configured threshold will be marked with Overthreshold return code.
RANGE: [1 , 60000]
DEFAULT: 5000


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 Operation Threshold

Deleting the Operation Threshold
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "threshold": "5000"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <threshold>5000</threshold>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no threshold 10734


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
thresholdsla:Threshold
(scalar:Uint32)
Operation threshold - this is an upper limit for the observed RTT for the probe. RTT value of a probe exceeding the configured threshold will be marked with Overthreshold return code.
RANGE: [1 , 60000]
DEFAULT: 5000


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 Timeout of an Operation

Configuring the Timeout of an Operation
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "timeout": "477429727"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <timeout>477429727</timeout>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  timeout 477429727


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
timeoutsla:Timeout
(scalar:Uint32)
Timeout of an operation - this is the maximum wait time for completing the operation. The probe will be marked with Timeout return code.
RANGE: [0 , 604800000]
DEFAULT: 5000


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 Default Timeout

Configuring the Default Timeout
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "timeout": "5000"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <timeout>5000</timeout>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  default timeout


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
timeoutsla:Timeout
(scalar:Uint32)
Timeout of an operation - this is the maximum wait time for completing the operation. The probe will be marked with Timeout return code.
RANGE: [0 , 604800000]
DEFAULT: 5000


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 Timeout of an Operation

Deleting the Timeout of an Operation
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "timeout": "5000"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <timeout>5000</timeout>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no timeout 477429727


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
timeoutsla:Timeout
(scalar:Uint32)
Timeout of an operation - this is the maximum wait time for completing the operation. The probe will be marked with Timeout return code.
RANGE: [0 , 604800000]
DEFAULT: 5000


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 Type of Service

Configuring the Type of Service
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "ipTos": "130"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <ipTos>130</ipTos>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  tos 130


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
ipTosscalar:Uint32
TOS if the probe is tracking IPv4 destination and Traffic Class if the probe is tracking IPv6 destination.RANGE: [0, 4294967295]


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 Default Type of Service

Configuring the Default Type of Service
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "ipTos": "0"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <ipTos>0</ipTos>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  default tos


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
ipTosscalar:Uint32
TOS if the probe is tracking IPv4 destination and Traffic Class if the probe is tracking IPv6 destination.RANGE: [0, 4294967295]


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 Type of Service

Deleting the Type of Service
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "ipTos": "0"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <ipTos>0</ipTos>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no tos 130


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
ipTosscalar:Uint32
TOS if the probe is tracking IPv4 destination and Traffic Class if the probe is tracking IPv6 destination.RANGE: [0, 4294967295]


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 Traffic Class

Configuring the Traffic Class 
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "ipv6TrafficClass": "230"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <ipv6TrafficClass>230</ipv6TrafficClass>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  traffic-class 230


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
ipv6TrafficClassscalar:Uint32
TOS if the probe is tracking IPv4 destination and Traffic Class if the probe is tracking IPv6 destination.RANGE: [0, 4294967295]


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 Default Traffic Class

Configuring the Default Traffic Class
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "ipv6TrafficClass": "0"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <ipv6TrafficClass>0</ipv6TrafficClass>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  default traffic-class


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
ipv6TrafficClassscalar:Uint32
TOS if the probe is tracking IPv4 destination and Traffic Class if the probe is tracking IPv6 destination.RANGE: [0, 4294967295]


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 Traffic Class

Deleting the Traffic Class 
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "ipv6TrafficClass": "0"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <ipv6TrafficClass>0</ipv6TrafficClass>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no traffic-class 230


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
ipv6TrafficClassscalar:Uint32
TOS if the probe is tracking IPv4 destination and Traffic Class if the probe is tracking IPv6 destination.RANGE: [0, 4294967295]


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 SLAs for a VPN Routing/Forwarding Instances

Configuring IP SLAs for a VPN Routing/Forwarding Instances
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "vrf": "SampleString_123"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <vrf>SampleString_123</vrf>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  vrf 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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
vrfl3:VrfName
(string:Basic)
vrf on which the probe is configured.A sequence of characters
DEFAULT: default


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 Default IP SLAs for a VPN Routing/Forwarding instance

Configuring the Default IP SLAs for a VPN Routing/Forwarding instance
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "vrf": "default"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <vrf>default</vrf>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  default vrf


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
vrfl3:VrfName
(string:Basic)
vrf on which the probe is configured.A sequence of characters
DEFAULT: default


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 SLAs for a VPN Routing/Forwarding Instances

Deleting IP SLAs for a VPN Routing/Forwarding Instances
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "vrf": "default"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <vrf>default</vrf>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no vrf 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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
vrfl3:VrfName
(string:Basic)
vrf on which the probe is configured.A sequence of characters
DEFAULT: default


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 Destination IP Address

Configuring the Destination IP Address
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destHostName": "SampleString_123",
                  "destip": "1.1.1.1",
                  "dstPort": "2345"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destHostName>SampleString_123</destHostName>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  dest-ipaddr 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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destHostNamestring:Basic
Destination Host Name, if IP address is resolved from DNS server.Modifying this property is not allowed in case of icmp-echo probe.A sequence of characters
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]


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 Destination Address

Configuring the IPv6 Destination Address
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destHostName": "1:2::3:4",
                  "destip": "1.1.1.1",
                  "dstPort": "2345"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destHostName>1:2::3:4</destHostName>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  dest-ipaddr 1:2::3: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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destHostNamestring:Basic
Destination Host Name, if IP address is resolved from DNS server.Modifying this property is not allowed in case of icmp-echo probe.A sequence of characters
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]


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 Data Verification

Configuring Data Verification
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "verifyData": "yes"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <verifyData>true</verifyData>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  verify-data


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
verifyDatascalar:Bool
Verify Data for Corruption. When data verification is enabled, each operation response is checked for corruption. Use the verify-data command with caution during normal operations because it generates unnecessary overhead.SELECTION: true or false


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 Default Data Verification

Configuring Default Data Verification
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "verifyData": "no"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <verifyData>false</verifyData>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  default verify-data


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
verifyDatascalar:Bool
Verify Data for Corruption. When data verification is enabled, each operation response is checked for corruption. Use the verify-data command with caution during normal operations because it generates unnecessary overhead.SELECTION: true or false


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 Data Verification

Deleting Data Verification
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "dstPort": "2345",
                  "verifyData": "no"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <dstPort>2345</dstPort>
              <verifyData>false</verifyData>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter 1.1.1.1 2345
  no verify-data


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
verifyDatascalar:Bool
Verify Data for Corruption. When data verification is enabled, each operation response is checked for corruption. Use the verify-data command with caution during normal operations because it generates unnecessary overhead.SELECTION: true or false


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 to Enable Control Packets Exchange

Configuring to Enable Control Packets Exchange
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "advFactor": "20",
                  "codecInterval": "22718",
                  "codecNumPkts": "45907",
                  "codecSize": "13179",
                  "codecType": "g711alaw",
                  "control": "yes",
                  "destHostName": "SampleString_123",
                  "dstPort": "15734",
                  "srcHostName": "SampleString_123",
                  "srcPort": "15734"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <advFactor>20</advFactor>
              <codecInterval>22718</codecInterval>
              <codecNumPkts>45907</codecNumPkts>
              <codecSize>13179</codecSize>
              <codecType>g711alaw</codecType>
              <control>true</control>
              <destHostName>SampleString_123</destHostName>
              <dstPort>15734</dstPort>
              <srcHostName>SampleString_123</srcHostName>
              <srcPort>15734</srcPort>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter SampleString_123 15734 codec g711alaw advantage-factor 20 codec-interval 22718 codec-numpackets 45907 codec-size 13179 source-port 15734 source-ip SampleString_123 control enable


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter
slaSender sys/sla/inst/sender


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
advFactorsla:AdvFactor
(scalar:UByte)
Advantage factor
RANGE: [0 , 20]
DEFAULT: 0
codecIntervalsla:Interval
(scalar:Uint32)
Interval between packets
RANGE: [4 , 60000]
DEFAULT: 20
codecNumPktssla:CodecNumPkts
(scalar:Uint32)
Number of packets per operation
RANGE: [1 , 60000]
DEFAULT: 1000
codecSizesla:CodecSize
(scalar:Uint32)
Number of bytes per packet
RANGE: [16 , 16384]
DEFAULT: 32
codecTypesla:CodecType
(scalar:Enum8)
Codec TypeSELECTION:
0 - none
1 - g711ulaw
2 - g711alaw
3 - g729a
DEFAULT: none
controlscalar:Bool
To turn on/off Control Packets Exchanging mechanism between the sender and the responder, control is enabled by default.SELECTION: true or false
DEFAULT: true
destHostNamestring:Basic
Destination Host Name, if IP address is resolved from DNS server.Modifying this property is not allowed in case of icmp-echo probe.A sequence of characters
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
srcHostNamestring:Basic
Source Host Name, if IP address is resolved from DNS server. Modifying this property is not allowed.A sequence of characters
srcPortscalar:Uint32
Source UDP Port configuration for udp-jitter probe and if the srcPort is not configured, then source port will be used.RANGE: [0, 4294967295]


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 Configuration for Enabling Control Packets Exchange

Deleting the Configuration for Enabling Control Packets Exchange
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "advFactor": "20",
                  "codecInterval": "22718",
                  "codecNumPkts": "45907",
                  "codecSize": "13179",
                  "codecType": "g711alaw",
                  "control": "yes",
                  "destHostName": "SampleString_123",
                  "dstPort": "15734",
                  "srcHostName": "SampleString_123",
                  "srcPort": "15734"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <advFactor>20</advFactor>
              <codecInterval>22718</codecInterval>
              <codecNumPkts>45907</codecNumPkts>
              <codecSize>13179</codecSize>
              <codecType>g711alaw</codecType>
              <control>true</control>
              <destHostName>SampleString_123</destHostName>
              <dstPort>15734</dstPort>
              <srcHostName>SampleString_123</srcHostName>
              <srcPort>15734</srcPort>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 no udp-jitter SampleString_123 15734 codec g711alaw advantage-factor 20 codec-interval 22718 codec-numpackets 45907 codec-size 13179 source-port 15734 source-ip SampleString_123 control enable


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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter
slaSender sys/sla/inst/sender


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
advFactorsla:AdvFactor
(scalar:UByte)
Advantage factor
RANGE: [0 , 20]
DEFAULT: 0
codecIntervalsla:Interval
(scalar:Uint32)
Interval between packets
RANGE: [4 , 60000]
DEFAULT: 20
codecNumPktssla:CodecNumPkts
(scalar:Uint32)
Number of packets per operation
RANGE: [1 , 60000]
DEFAULT: 1000
codecSizesla:CodecSize
(scalar:Uint32)
Number of bytes per packet
RANGE: [16 , 16384]
DEFAULT: 32
codecTypesla:CodecType
(scalar:Enum8)
Codec TypeSELECTION:
0 - none
1 - g711ulaw
2 - g711alaw
3 - g729a
DEFAULT: none
controlscalar:Bool
To turn on/off Control Packets Exchanging mechanism between the sender and the responder, control is enabled by default.SELECTION: true or false
DEFAULT: true
destHostNamestring:Basic
Destination Host Name, if IP address is resolved from DNS server.Modifying this property is not allowed in case of icmp-echo probe.A sequence of characters
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
srcHostNamestring:Basic
Source Host Name, if IP address is resolved from DNS server. Modifying this property is not allowed.A sequence of characters
srcPortscalar:Uint32
Source UDP Port configuration for udp-jitter probe and if the srcPort is not configured, then source port will be used.RANGE: [0, 4294967295]


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 Source Address

Configuring the Source Address
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "advFactor": "20",
                  "codecInterval": "22718",
                  "codecNumPkts": "45907",
                  "codecSize": "13179",
                  "codecType": "g711alaw",
                  "control": "no",
                  "destHostName": "SampleString_123",
                  "dstPort": "15734",
                  "srcHostName": "SampleString_123",
                  "srcPort": "15734"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <advFactor>20</advFactor>
              <codecInterval>22718</codecInterval>
              <codecNumPkts>45907</codecNumPkts>
              <codecSize>13179</codecSize>
              <codecType>g711alaw</codecType>
              <control>false</control>
              <destHostName>SampleString_123</destHostName>
              <dstPort>15734</dstPort>
              <srcHostName>SampleString_123</srcHostName>
              <srcPort>15734</srcPort>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 udp-jitter SampleString_123 15734 codec g711alaw advantage-factor 20 codec-interval 22718 codec-size 13179 codec-numpackets 45907 control disable source-port 15734 source-ip 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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter
slaSender sys/sla/inst/sender


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
advFactorsla:AdvFactor
(scalar:UByte)
Advantage factor
RANGE: [0 , 20]
DEFAULT: 0
codecIntervalsla:Interval
(scalar:Uint32)
Interval between packets
RANGE: [4 , 60000]
DEFAULT: 20
codecNumPktssla:CodecNumPkts
(scalar:Uint32)
Number of packets per operation
RANGE: [1 , 60000]
DEFAULT: 1000
codecSizesla:CodecSize
(scalar:Uint32)
Number of bytes per packet
RANGE: [16 , 16384]
DEFAULT: 32
codecTypesla:CodecType
(scalar:Enum8)
Codec TypeSELECTION:
0 - none
1 - g711ulaw
2 - g711alaw
3 - g729a
DEFAULT: none
controlscalar:Bool
To turn on/off Control Packets Exchanging mechanism between the sender and the responder, control is enabled by default.SELECTION: true or false
DEFAULT: true
destHostNamestring:Basic
Destination Host Name, if IP address is resolved from DNS server.Modifying this property is not allowed in case of icmp-echo probe.A sequence of characters
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
srcHostNamestring:Basic
Source Host Name, if IP address is resolved from DNS server. Modifying this property is not allowed.A sequence of characters
srcPortscalar:Uint32
Source UDP Port configuration for udp-jitter probe and if the srcPort is not configured, then source port will be used.RANGE: [0, 4294967295]


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 Source Address

Deleting the Source Address
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "advFactor": "20",
                  "codecInterval": "22718",
                  "codecNumPkts": "45907",
                  "codecSize": "13179",
                  "codecType": "g711alaw",
                  "control": "no",
                  "destHostName": "SampleString_123",
                  "dstPort": "15734",
                  "srcHostName": "SampleString_123",
                  "srcPort": "15734"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <advFactor>20</advFactor>
              <codecInterval>22718</codecInterval>
              <codecNumPkts>45907</codecNumPkts>
              <codecSize>13179</codecSize>
              <codecType>g711alaw</codecType>
              <control>false</control>
              <destHostName>SampleString_123</destHostName>
              <dstPort>15734</dstPort>
              <srcHostName>SampleString_123</srcHostName>
              <srcPort>15734</srcPort>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </sender-items>
    </inst-items>
  </sla-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.

ip sla 1
 no udp-jitter SampleString_123 15734 codec g711alaw advantage-factor 20 codec-interval 22718 codec-size 13179 codec-numpackets 45907 control disable source-port 15734 source-ip 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
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter
slaSender sys/sla/inst/sender


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.RANGE: [0, 4294967295]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
advFactorsla:AdvFactor
(scalar:UByte)
Advantage factor
RANGE: [0 , 20]
DEFAULT: 0
codecIntervalsla:Interval
(scalar:Uint32)
Interval between packets
RANGE: [4 , 60000]
DEFAULT: 20
codecNumPktssla:CodecNumPkts
(scalar:Uint32)
Number of packets per operation
RANGE: [1 , 60000]
DEFAULT: 1000
codecSizesla:CodecSize
(scalar:Uint32)
Number of bytes per packet
RANGE: [16 , 16384]
DEFAULT: 32
codecTypesla:CodecType
(scalar:Enum8)
Codec TypeSELECTION:
0 - none
1 - g711ulaw
2 - g711alaw
3 - g729a
DEFAULT: none
controlscalar:Bool
To turn on/off Control Packets Exchanging mechanism between the sender and the responder, control is enabled by default.SELECTION: true or false
DEFAULT: true
destHostNamestring:Basic
Destination Host Name, if IP address is resolved from DNS server.Modifying this property is not allowed in case of icmp-echo probe.A sequence of characters
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]
srcHostNamestring:Basic
Source Host Name, if IP address is resolved from DNS server. Modifying this property is not allowed.A sequence of characters
srcPortscalar:Uint32
Source UDP Port configuration for udp-jitter probe and if the srcPort is not configured, then source port will be used.RANGE: [0, 4294967295]


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 Max Number of History Buckets to Collect

Configuring the Max Number of History Buckets to Collect 
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "distributionsOfStatsKept": "8",
                  "dstPort": "2345"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <distributionsOfStatsKept>8</distributionsOfStatsKept>
              <dstPort>2345</dstPort>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </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.

ip sla 1
  udp-jitter 1.1.1.1 2345
   history distributions-of-statistics-kept 8


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
slaSender sys/sla/inst/sender
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.
RANGE: [1 , 2147483647]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
distributionsOfStatsKeptscalar:Uint32
Maximum number of statistics distribution buckets to capture
RANGE: [1 , 20]
DEFAULT: 1
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]


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 Max Number of Statistics Distribution Buckets to Capture

Deleting the Max Number of Statistics Distribution Buckets to Capture 
POST http://<mgmt0_IP>/api/mo/sys/sla/inst/sender.json
{
  "slaSender": {
    "children": [
      {
        "slaProbe": {
          "attributes": {
            "id": "1"
          },
          "children": [
            {
              "slaUdpJitter": {
                "attributes": {
                  "destip": "1.1.1.1",
                  "distributionsOfStatsKept": "1",
                  "dstPort": "2345"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <sla-items>
    <inst-items>
      <sender-items>
        <operation-items>
          <Probe-list>
            <id>1</id>
            <udpjitter-items>
              <destip>1.1.1.1</destip>
              <distributionsOfStatsKept>1</distributionsOfStatsKept>
              <dstPort>2345</dstPort>
            </udpjitter-items>
          </Probe-list>
        </operation-items>
      </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.

ip sla 1
  udp-jitter 1.1.1.1 2345
   no history distributions-of-statistics-kept 8


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
slaSender sys/sla/inst/sender
slaProbe sys/sla/inst/sender/operation-1
slaUdpJitter sys/sla/inst/sender/operation-1/udpjitter


slaProbe Properties

The following table contains information about the slaProbe 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
idscalar:Uint32
Operation index which is unique for each probe, all the probe related configs and the statistics are displayed using this index.
RANGE: [1 , 2147483647]


slaUdpJitter Properties

The following table contains information about the slaUdpJitter 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
destipaddress:Ip
Destination IP address which is tracked by the probe.This property is not applicable if the configured probe type is HTTP or DNS. Modifying this property is not allowed in case of icmp-echo probe.Value must match ipv4 or ipv6 known format
distributionsOfStatsKeptscalar:Uint32
Maximum number of statistics distribution buckets to capture
RANGE: [1 , 20]
DEFAULT: 1
dstPortscalar:Uint32
Destion UDP Port configuration for the UDP probe, it is must to configure the destination port.RANGE: [0, 4294967295]


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