- Cisco Nexus 3000 and 9000 Series NX-API REST Documentation
- Cisco Nexus 3000 and 9000 Series NX-API REST SDK User Guide and API Reference, Release 10.5(x)
- Getting Started with the Cisco Nexus 3000 and 9000 Series NX-API REST SDK
- Related Documentation
- New and Changed Information
- Manageability
- ISSU Commands
- Installing Software Packages
- Configuring NX-API Management
- Managing Images
- Manageability Actions
- Configuring GRPC tunnel destination
- Manageability Using YANG (NETCONF)
- Configuring Fundamentals
- High Availability and Redundancy
- Configuring ITD
- Configuring Interfaces
- Configuring Ethernet Interfaces
- Configuring a MAC Address Limitation
- Configuring VLAN Interfaces
- Configuring Loopback Interfaces
- Configuring MGMT Interfaces
- Configuring Breakout Profiles
- Configuring System Default Switchport
- Configuring UDLD
- Configuring BFD
- Configuring LACP
- Configuring Hostname Loopback
- Configuring Breakout on High-Bandwidth Interfaces
- Configuring Port-Channel Interfaces
- Configuring Virtual Port Channels
- Configuring Tunnel Interfaces
- Configuring Layer 2 Protocol Tunneling
- Configuring Network Address Translation (NAT)
- Configuring IP TCP MSS
- Configuring Hardware Profile Settings
- Querying Interface Information
- Clearing Statistics
- Configuring IP SLAs
- Configuring a DNS Operation
- Configuring a UDP-Echo Operation
- Configuring an HTTP Operation
- Configuring an ICMP-Echo Operation
- Configuring a UDP-Jitter Operation
- Configuring a Destination Port
- Configuring the Acceptable Clock Synchronization Error in Oneway Measurement
- Configuring the Default Acceptable Clock Synchronization Error
- Deleting the Acceptable Clock Synchronization Error in Oneway Measurement
- Configuring 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
- Configuring the Frequency in Seconds
- Configuring the Default Frequency
- Deleting the Frequency in Seconds
- Configuring the Operation Packet Priority
- Configuring the Default Operation Packet Priorities
- Deleting the Operation Packet Priority
- Configuring the Operation Packet Priority to Normal
- Deleting the Operation Packet Priority to Normal
- Configuring the Owner of Entry
- Configuring the Default Owner
- Deleting the Owner of Entry
- Configuring the UDP-Jitter Precision in Microseconds
- Deleting the UDP-Jitter Precision in Microseconds
- Configuring the UDP-Jitter Precision in Milliseconds
- Configuring the Default Precision of Measurement
- Deleting the UDP-Jitter Precision in Milliseconds
- Configuring the Data Size Request
- Configuring the Request Data Size
- Deleting the Data Size Request
- Configuring a User-Defined Tag
- Deleting a User-Defined Tag
- Configuring the Default User-Defined Tag
- Configuring the Operation Threshold
- Configuring the Default Threshold
- Deleting the Operation Threshold
- Configuring the Timeout of an Operation
- Configuring the Default Timeout
- Deleting the Timeout of an Operation
- Configuring the Type of Service
- Configuring the Default Type of Service
- Deleting the Type of Service
- Configuring the Traffic Class
- Configuring the Default Traffic Class
- Deleting the Traffic Class
- Configuring IP SLAs for a VPN Routing/Forwarding Instances
- Configuring the Default IP SLAs for a VPN Routing/Forwarding instance
- Deleting IP SLAs for a VPN Routing/Forwarding Instances
- Configuring the Destination IP Address
- Configuring the IPv6 Destination Address
- Configuring Data Verification
- Configuring Default Data Verification
- Deleting Data Verification
- Configuring to Enable Control Packets Exchange
- Deleting the Configuration for Enabling Control Packets Exchange
- Configuring the Source Address
- Deleting the Source Address
- Configuring the Max Number of History Buckets to Collect
- Deleting the Max Number of Statistics Distribution Buckets to Capture
- Configuring a TCP-Connect Operation
- Configuring an IP SLA Group Schedule
- Configuring Label Switching
- Configuring Segment Routing
- Configuring MPLS LDP
- Configuring Label Advertisement
- Configuring Label Allocation
- Configuring MPLS
- Disabling MPLS Forwarding for IP
- Configuring LDP Session Backoff
- Configuring LDP Discovery
- Configuring Explicit Null Label Advertisement
- Configuring LDP Graceful Restart
- Configuring LDP Holdtime
- Configuring a Neighbor
- Configuring an LDP Password
- Configuring LDP Logging
- Configuring LDP Labels
- Configuring an LDP Session
- Configuring MPLS LDP on an Interface
- Configuring Netstack
- Configuring Layer 2 Switching
- Configuring Flex Links
- Configuring Hairpin Forwarding
- Configuring Storm Control
- Configuring a Private VLAN (PVLAN)
- Configuring Multicast Routing
- Configuring PIM/PIM6
- Configuring MSDP
- Configuring IGMP
- Configuring MLD Snooping
- Configuring MRIB
- Configuring RPF Routes for Multicast
- Configuring Fabric Extender
- Configuring QoS
- Configuring Policing
- Configuring QoS Class Maps
- Configuring QoS Policy Maps
- Configuring a User-Defined Network QoS Policy
- Configuring the Hardware Buffer Utilization Thresholds
- Configuring Hardware QoS
- Configuring Hardware Profile Settings on the Cisco Nexus 3500 Platform
- Configuring Cisco Nexus 9000 (Cisco-ASIC based) Platform QoS
- Configuring Priority Flow Control
- Changing the Bandwidth Allocated to Unicast and Multicast Traffic
- Clearing Statistics
- Configuring TCAM
- Enabling Queue-Based ECN Marking
- Configuring Trust Boundaries
- Configuring Security
- Configuring FIPS Mode
- Configuring EAP Profile
- Configuring Keychain Management
- Configuring AAA
- Configuring RADIUS
- Configuring TACACS+
- Configuring LDAP
- Configuring SSH
- Configuring a Trustpool Policy
- Configuring a Trustpoint Certificate Authority
- Configuring a Trustpoint Certificate Authority
- Configuring Certificate Authority Related Information
- Crypto ca import for mytrustpoint pkcs12
- Configuring Telnet
- Configuring the Shell Type for Login
- Configuring User Accounts and RBAC
- Configuring the VSH Roles and Rules
- Configuring ACLs
- Configuring Port Security
- Configuring DHCP
- Configuring Password Encryption
- Configuring VPN Ids
- Configuring Unicast RPF (URPF)
- Configuring System Security Compliance
- Configuring Control Plane Policing
- Configuring Rate Limits
- Configuring MACsec
- Known Behaviour for Logging Level Configs
- Configuring System Management
- Configuring Sup Boot Variables
- Configuring System Cores
- Configuring System Trace Level
- Configuring the Fast Reload Network Stabilization Timer
- Configuring Frequency Synchronization
- Configuring NTP
- Configuring PTP
- Verifying PTP Counters
- Configuring Cisco Discovery Protocol
- Configuring Call Home
- Configuring Checkpoints and Rollback
- Configuring System Logging
- Configuring the Scheduler
- Configuring SNMP
- Configuring RMON
- Configuring Online Diagnostics
- Configuring EVMED
- Configuring Embedded Event Manager
- Configuring Memory Thresholds
- Configuring SPAN
- Configuring ERSPAN
- Configuring LLDP
- Enabling and Disabling LLDP
- Configuring LLDP in Global Mode
- Configuring LLDP on the if-eth-base/if-ethernet-all Command Mode
- Configuring LLDP on the if-gig-ether Command Mode
- Configuring LLDP on the if-gig-ether-all Command Mode
- Configuring LLDP on the if-mgmt-ether Command Mode
- Configuring the DCBXP Version
- Configuring System Interface Shutdown
- Configuring NetFlow
- Configuring Drop Report Tool
- Configuring sFlow
- Attaching a TAP Aggregation Policy to an Interface
- Configuring MPLS Stripping
- Configuring the Maintenance-Mode Profile
- Configuring Maintenance Mode
- Configuring CFS
- Configuring User-Defined Fields
- Configuring a Fan-Direction Mismatch
- System-Level High Availability
- Configuring NX-OS Container Tracker
- Configuring VXLAN
- VXLAN New and Changed
- Micro-segmentation for VXLAN Fabrics Using Group Policy Option (GPO)
- Configuring VXLAN BGP EVPN
- Configuring HMM
- Configure VXLAN FHS
- VXLAN Configuration Command Examples
- Configuring NVE Interfaces
- Configuring BGP EVPN Filtering
- Configuring VXLAN OAM (NGOAM)
- Executing Ping NVE, Traceroute NVE, and Path Trace NVE
- Configuring System NVE
- Associating NVE Interfaces with VNIs
- Configuring ngMVPN
- Configuring Selective Q-in-VNI
- Ephemeral (MOTL) MOs for NVE
- Configuring Unicast Routing
- Configuring the System Routing Mode
- Configuring ARP
- Configuring ALPM
- Configuring Logging for Software Forwarding of IP Packets
- Configuring DNS
- Configuring OSPF, OSPFv2, and OSPFv3
- Configuring OSPF
- Configuring OSPFv2
- Configuring OSPFv3
- Configuring an IPv6 Unicast Address Family Under an OSPFv3 Instance
- Configuring OSPFv3 Broadcast Network Type
- Configuring OSPFv3 on an Ethernet Interface
- Configuring OSPFv3 on a Loopback Interface
- Configuring OSPFv3 on a MGMT Interface
- Configuring OSPFv3 on a P2P Ethernet Interface
- Configuring OSPFv3 on a Tunnel Interface
- Configuring a Virtual Link Under an OSPFv3 Instance
- Configuring a VRF Under an OSPFv3 Instance
- Querying OSPFv3
- Configuring IS-IS
- Configuring IS-IS in Global Configuration Command Mode
- Configuring IS-IS in Interface Configuration Mode
- Configuring IS-IS in Router Configuration Mode
- Configuring IS-IS in Router VRF Configuration Mode
- Configuring IS-IS in Router IPv4 Address Family Configuration Mode
- Configuring IS-IS in Router IPv6 Address Family Configuration Mode
- IS-IS Operational Commands
- Configuring EIGRP
- Enabling EIGRP
- Disabling EIGRP
- Configuring isolate Under EIGRP
- Configuring flush-routes under EIGRP
- Configuring vrf
- Configuring EIGRP address-family
- Configuring EIGRP router-id
- Configuring EIGRP distance
- Configuring EIGRP maximum paths
- Configuring EIGRP default information originate
- Configuring EIGRP administrative state
- Configuring IPV4 EIGRP route redistribution
- Configuring IPv6 EIGRP route redistribution
- Configuring EIGRP table map filter
- Configuring EIGRP redistribute maximum prefix
- Configuring EIGRP graceful restart
- Configuring EIGRP log adjacency changes
- Configuring EIGRP log adjacency warnings
- Configuring EIGRP metric version
- Configuring EIGRP metric maximum hops
- Configuring EIGRP nsf await redistribute proto convergence
- Configuring EIGRP autonomous system number
- Configuring EIGRP nsf route-hold timer
- Configuring EIGRP nsf converge timer
- Configuring EIGRP nsf signal timer
- Configuring EIGRP timers active-time
- Configuring EIGRP supress fib pending
- Configuring EIGRP passive interface
- Configuring EIGRP metric weights
- Configuring EIGRP default metric
- Configuring EIGRP stub
- Configuring EIGRP authentication key chain
- Configuring EIGRP authentication mode
- Configuring BFD for EIGRP
- Configuring EIGRP in Interface Configuration Mode
- Configuring BGP
- Configuring a BGP Router
- VXLAN EVPN Traffic Engineering - Multi-Site Egress Load-Balancing
- VXLAN EVPN Traffic Engineering – RPM support
- Configuring BGP on a VRF
- Configuring BFD Multihop under a Neighbor
- Configuring an IPv4 Multicast Address Family
- Configuring an IPv4 MVPN Address Family
- Configuring an IPv4 Unicast Address Family
- Configuring an IPv6 MVPN Address Family
- Configuring an IPv6 Unicast Address Family
- Configuring a Link-State Address Family
- Configuring a VPNv4 Unicast Address Family
- Configuring a VPNv6 Unicast Address Family
- Configuring a Peer Policy Template
- Configuring an IPv4 Labeled Unicast Subaddress Family for a Peer Policy Template
- Configuring an IPv4 Unicast Subaddress Family for a Peer Policy Template
- Configuring an IPv6 Unicast Subaddress Family for a Peer Policy Template
- Configuring a VPNv4 Unicast Subaddress Family for a Peer Policy Template
- Configuring a VPNv6 Unicast Subaddress Family for a Peer Policy Template
- Configuring a Peer Policy Template with Peer Template Inheritance
- Configuring an IPv4 Labeled Unicast Subaddress Family for a Peer Policy Template with Peer Template Inheritance
- Configuring an IPv4 Unicast Subaddress Family for a Peer Policy Template with Peer Template Inheritance
- Configuring an IPv6 Unicast Subaddress Family for a Peer Policy Template with Peer Template Inheritance
- Configuring a VPNv4 Unicast Subaddress Family for a Peer Policy Template with Peer Template Inheritance
- Configuring a VPNv6 Unicast Subaddress Family for a Peer Policy Template with Peer Template Inheritance
- Configuring a Peer Template
- Configuring an IPv4 Labeled Subaddress Family for a Peer Template
- Configuring an IPv4 Unicast Subaddress Family for a Peer Template
- Configuring an IPv6 Unicast Subaddress Family for a Peer Template
- Configuring a VPNv4 Subaddress Family for a Peer Template
- Configuring a VPNV6 Subaddress Family for a Peer Template
- Configuring Peer Template Inheritance
- Configuring an IPv4 Labeled Unicast Subaddress Family for Peer Template Inheritance
- Configuring an IPv4 Unicast Subaddress Family for Peer Template Inheritance
- Configuring an IPv6 Unicast Subaddress Family for Peer Template Inheritance
- Configuring a VPNv4 Unicast Subaddress Family for Peer Template Inheritance
- Configuring a VPNv6 Unicast Subaddress Family for Peer Template Inheritance
- Configuring a Peer Template with Peer Template Inheritance
- Configuring an IPv4 Labeled Unicast Subaddress Family for a Peer Template with Peer Template Inheritance
- Configuring an IPv4 Unicast Subaddress Family for a Peer Template with Peer Template Inheritance
- Configuring an IPv6 Unicast Subaddress Family for a Peer Template with Peer Template Inheritance
- Configuring a VPNv4 Unicast Subaddress Family for a Peer Template with Peer Template Inheritance
- Configuring a VPNv6 Unicast Subaddress Family for a Peer Template with Peer Template Inheritance
- Configuring a BGP Neighbor (IP Address)
- Configuring an IPv4 Unicast Subaddress Family Under a BGP Neighbor (IP Address)
- Configuring an IPv6 Labeled Unicast Subaddress Family Under a BGP Neighbor (IP Address)
- Configuring an IPv6 Multicast Subaddress Family Under a BGP Neighbor (IP Address)
- Configuring an IPv6 Unicast Subaddress Family Under a BGP Neighbor (IP Address)
- Configuring an IPv4 MVPN Subaddress Family Under a BGP Neighbor (IP Address)
- Configuring an IPv6 MVPN Subaddress Family Under a BGP Neighbor (IP Address)
- Configuring an L2VPN EVPN Address Family under a BGP Neighbor (IP Address)
- Configuring a VPNv4 Unicast Subaddress Family Under a BGP Neighbor (IP Address)
- Configuring a VPNv6 Unicast Subaddress Family Under a BGP Neighbor (IP Address)
- Configuring BGP Session Templates Under a BGP Neighbor (IP Address)
- Configuring a BGP Neighbor (Ethernet Interface)
- Configuring an IPv4 Unicast Subaddress Family Under a BGP Neighbor (Ethernet Interface)
- Configuring an IPv6 MVPN Subaddress Family Under a BGP Neighbor (Ethernet Interface)
- Configuring an L2VPN EVPN Subaddress Family Under a BGP Neighbor (Ethernet Interface)
- Configuring a VPNv4 Unicast Subaddress Family Under a BGP Neighbor (Ethernet Interface)
- Configuring a VPNv6 Unicast Subaddress Family Under a BGP Neighbor (Ethernet Interface)
- Configuring a BMP Server
- Configuring Mixed ECMP
- About Querying Ephemeral Data
- Configuring RIP
- Configuring DSCP
- Configuring VRFs
- Configuring Route Policy Manager
- First-Hop Redundancy Protocols
- Configuring Hardware Forwarding
- Configuring Hardware Ejector
- Configuring Hardware Profile Settings
- Configuring the Site of Origin
- Configuring AS-4 Dot Notation
- Configuring Static Routing
- Configuring Load Sharing in the Unicast FIB
- Configuring OpenFlow
- Configuring RTP Flow Monitoring
- Configuring Kernel Stack
- Configuring Apphosting
- Controlling the Guest Shell
- Enabling the Guest Shell and Querying the Result
- Disabling the Guest Shell and Querying the Result
- Destroying the Guest Shell and Querying the Result
- Rebooting the Guest Shell and Querying the Result
- Increasing the Guest Shell Rootfs Size and Querying the Result
- Changing the CPU Memory Size that the Guest Shell Uses and Querying the Result
- Changing the Memory Size the Guest Shell Uses and Querying the Result
- Syncing the Guest Shell Rootfs to the Standby Supervisor and Querying the Result
- Exporting the Guest Shell Rootfs and Querying the Result
- Upgrading the Guest Shell Rootfs and Querying the Result
- Querying Guest Shell Information
- Change Virtual Service Global Configuration
- Managing System Hardware
- Configuring the Baseboard Management Controller
- Configuring Virtual Machine Tracker
- Configuring Virtual Device Contexts
- Configuring iCAM
- Configuring SRv6
- Configuring Smart Software Licensing
- Querying Configurations (Show Commands)
- Querying Advertised Routes
- Querying DHCP Relay Interfaces
- Querying Diagnostic Result Test IDs
- Querying the Environment Settings
- Querying Feature Status
- Querying Inventory Information
- Querying IS-IS Configurations
- Querying IP IGMP Groups
- Querying IP OSPF Neighbor Details
- Querying IP OSPF Neighbor VRF Information
- Querying L2VPN EVPN
- Querying LLDP
- Querying MAC Address Table Info
- Querying Module Information
- Querying NAT ITD
- Querying NTP Peer Status
- Querying an OSPFv2 Instance
- Querying Patterns
- Querying PIM Information
- Querying the Processes Log
- Querying Spanning Tree Information
- Querying a Summary of IP Interface Status and Configuration Information
- Querying TCAM Resource Utilization
- Querying MCAST NAT TCAM Resource Monitoring
- Querying NBM TCAM Resource Monitoring
- Querying the Version
- Querying VLAN ID Counters
- Querying VRF Information
- Querying VRRP Information
- Querying Forwarding Route Information
- Querying IP Route Details
- Querying the Current MOTD Banner Message
- Querying OSPF Neighbors
- Querying Analytic Information
- Querying Interface and VLAN Counters and Statistics
- Querying ITD Runtime Information
- Querying ePBR Runtime Information
- Using the Managed Object Browser
- Monitoring the Environment
CopyPOST 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"
}}}]}}]}}
Response
{
imdata:[]
}
Copy<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>
Configuring a UDP-Jitter Operation
Configuring a Destination Port
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Acceptable Clock Synchronization Error in Oneway Measurement
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
absoluteClockTolerance | sla:ClockToleranceAbsolute (scalar:Uint32) | Oneway NTP Clock Tolerance absolute Value | RANGE: [0 , 100000] DEFAULT: 0 |
destip | address: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 |
dstPort | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Default Acceptable Clock Synchronization Error
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
absoluteClockTolerance | sla:ClockToleranceAbsolute (scalar:Uint32) | Oneway NTP Clock Tolerance absolute Value | RANGE: [0 , 100000] DEFAULT: 0 |
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
percentClockTolerance | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Acceptable Clock Synchronization Error in Oneway Measurement
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
absoluteClockTolerance | sla:ClockToleranceAbsolute (scalar:Uint32) | Oneway NTP Clock Tolerance absolute Value | RANGE: [0 , 100000] DEFAULT: 0 |
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
percentClockTolerance | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Acceptable Clock Synchronization Error in Oneway Measurement as a Percent Value
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
percentClockTolerance | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Acceptable Clock Synchronization Error in Oneway Measurement as a Percent Value
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
absoluteClockTolerance | sla:ClockToleranceAbsolute (scalar:Uint32) | Oneway NTP Clock Tolerance absolute Value | RANGE: [0 , 100000] DEFAULT: 0 |
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
percentClockTolerance | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Frequency in Seconds
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
frequency | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Default Frequency
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
frequency | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Frequency in Seconds
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
frequency | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Operation Packet Priority
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
operationPktPriority | sla:OpPktPriority (scalar:Enum8) | Operation Packet Priority | SELECTION: 0 - none 1 - normal 2 - high DEFAULT: normal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Default Operation Packet Priorities
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
operationPktPriority | sla:OpPktPriority (scalar:Enum8) | Operation Packet Priority | SELECTION: 0 - none 1 - normal 2 - high DEFAULT: normal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Operation Packet Priority
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
operationPktPriority | sla:OpPktPriority (scalar:Enum8) | Operation Packet Priority | SELECTION: 0 - none 1 - normal 2 - high DEFAULT: normal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Operation Packet Priority to Normal
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
operationPktPriority | sla:OpPktPriority (scalar:Enum8) | Operation Packet Priority | SELECTION: 0 - none 1 - normal 2 - high DEFAULT: normal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Operation Packet Priority to Normal
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
operationPktPriority | sla:OpPktPriority (scalar:Enum8) | Operation Packet Priority | SELECTION: 0 - none 1 - normal 2 - high DEFAULT: normal |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Owner of Entry
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
owner | string: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Default Owner
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
owner | string: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Owner of Entry
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
owner | string: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the UDP-Jitter Precision in Microseconds
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
precision | sla:Precision (scalar:Enum8) | Precision configuration | SELECTION: 1 - microseconds 2 - milliseconds DEFAULT: milliseconds |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the UDP-Jitter Precision in Microseconds
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
precision | sla:Precision (scalar:Enum8) | Precision configuration | SELECTION: 1 - microseconds 2 - milliseconds DEFAULT: milliseconds |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the UDP-Jitter Precision in Milliseconds
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
precision | sla:Precision (scalar:Enum8) | Precision configuration | SELECTION: 1 - microseconds 2 - milliseconds DEFAULT: milliseconds |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Default Precision of Measurement
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
precision | sla:Precision (scalar:Enum8) | Precision configuration | SELECTION: 1 - microseconds 2 - milliseconds DEFAULT: milliseconds |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the UDP-Jitter Precision in Milliseconds
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
precision | sla:Precision (scalar:Enum8) | Precision configuration | SELECTION: 1 - microseconds 2 - milliseconds DEFAULT: milliseconds |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Data Size Request
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
reqDataSize | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Request Data Size
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
reqDataSize | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Data Size Request
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
reqDataSize | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring a User-Defined Tag
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
tag | string: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting a User-Defined Tag
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
tag | string: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Default User-Defined Tag
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
tag | string: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Operation Threshold
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
threshold | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Default Threshold
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
threshold | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Operation Threshold
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
threshold | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Timeout of an Operation
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
timeout | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Default Timeout
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
timeout | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Timeout of an Operation
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
timeout | sla: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Type of Service
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
ipTos | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Default Type of Service
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
ipTos | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Type of Service
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
ipTos | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Traffic Class
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
ipv6TrafficClass | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Default Traffic Class
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
ipv6TrafficClass | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Traffic Class
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
ipv6TrafficClass | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring IP SLAs for a VPN Routing/Forwarding Instances
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
vrf | l3: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Default IP SLAs for a VPN Routing/Forwarding instance
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
vrf | l3: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting IP SLAs for a VPN Routing/Forwarding Instances
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
vrf | l3: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Destination IP Address
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destHostName | string: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 |
destip | address: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 |
dstPort | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the IPv6 Destination Address
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destHostName | string: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 |
destip | address: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 |
dstPort | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring Data Verification
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
verifyData | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring Default Data Verification
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
verifyData | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting Data Verification
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
verifyData | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring to Enable Control Packets Exchange
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
advFactor | sla:AdvFactor (scalar:UByte) | Advantage factor | RANGE: [0 , 20] DEFAULT: 0 |
codecInterval | sla:Interval (scalar:Uint32) | Interval between packets | RANGE: [4 , 60000] DEFAULT: 20 |
codecNumPkts | sla:CodecNumPkts (scalar:Uint32) | Number of packets per operation | RANGE: [1 , 60000] DEFAULT: 1000 |
codecSize | sla:CodecSize (scalar:Uint32) | Number of bytes per packet | RANGE: [16 , 16384] DEFAULT: 32 |
codecType | sla:CodecType (scalar:Enum8) | Codec Type | SELECTION: 0 - none 1 - g711ulaw 2 - g711alaw 3 - g729a DEFAULT: none |
control | scalar: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 |
destHostName | string: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
srcHostName | string:Basic | Source Host Name, if IP address is resolved from DNS server. Modifying this property is not allowed. | A sequence of characters |
srcPort | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Configuration for Enabling Control Packets Exchange
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
advFactor | sla:AdvFactor (scalar:UByte) | Advantage factor | RANGE: [0 , 20] DEFAULT: 0 |
codecInterval | sla:Interval (scalar:Uint32) | Interval between packets | RANGE: [4 , 60000] DEFAULT: 20 |
codecNumPkts | sla:CodecNumPkts (scalar:Uint32) | Number of packets per operation | RANGE: [1 , 60000] DEFAULT: 1000 |
codecSize | sla:CodecSize (scalar:Uint32) | Number of bytes per packet | RANGE: [16 , 16384] DEFAULT: 32 |
codecType | sla:CodecType (scalar:Enum8) | Codec Type | SELECTION: 0 - none 1 - g711ulaw 2 - g711alaw 3 - g729a DEFAULT: none |
control | scalar: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 |
destHostName | string: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
srcHostName | string:Basic | Source Host Name, if IP address is resolved from DNS server. Modifying this property is not allowed. | A sequence of characters |
srcPort | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Source Address
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
advFactor | sla:AdvFactor (scalar:UByte) | Advantage factor | RANGE: [0 , 20] DEFAULT: 0 |
codecInterval | sla:Interval (scalar:Uint32) | Interval between packets | RANGE: [4 , 60000] DEFAULT: 20 |
codecNumPkts | sla:CodecNumPkts (scalar:Uint32) | Number of packets per operation | RANGE: [1 , 60000] DEFAULT: 1000 |
codecSize | sla:CodecSize (scalar:Uint32) | Number of bytes per packet | RANGE: [16 , 16384] DEFAULT: 32 |
codecType | sla:CodecType (scalar:Enum8) | Codec Type | SELECTION: 0 - none 1 - g711ulaw 2 - g711alaw 3 - g729a DEFAULT: none |
control | scalar: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 |
destHostName | string: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
srcHostName | string:Basic | Source Host Name, if IP address is resolved from DNS server. Modifying this property is not allowed. | A sequence of characters |
srcPort | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Source Address
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
advFactor | sla:AdvFactor (scalar:UByte) | Advantage factor | RANGE: [0 , 20] DEFAULT: 0 |
codecInterval | sla:Interval (scalar:Uint32) | Interval between packets | RANGE: [4 , 60000] DEFAULT: 20 |
codecNumPkts | sla:CodecNumPkts (scalar:Uint32) | Number of packets per operation | RANGE: [1 , 60000] DEFAULT: 1000 |
codecSize | sla:CodecSize (scalar:Uint32) | Number of bytes per packet | RANGE: [16 , 16384] DEFAULT: 32 |
codecType | sla:CodecType (scalar:Enum8) | Codec Type | SELECTION: 0 - none 1 - g711ulaw 2 - g711alaw 3 - g729a DEFAULT: none |
control | scalar: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 |
destHostName | string: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 |
dstPort | scalar:Uint32 | Destion UDP Port configuration for the UDP probe, it is must to configure the destination port. | RANGE: [0, 4294967295] |
srcHostName | string:Basic | Source Host Name, if IP address is resolved from DNS server. Modifying this property is not allowed. | A sequence of characters |
srcPort | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Configuring the Max Number of History Buckets to Collect
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
distributionsOfStatsKept | scalar:Uint32 | Maximum number of statistics distribution buckets to capture | RANGE: [1 , 20] DEFAULT: 1 |
dstPort | scalar: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:
See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:
https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the Max Number of Statistics Distribution Buckets to Capture
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.
MO | DN |
---|---|
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 Name | Data Type | Description | Values |
---|---|---|---|
id | scalar: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 Name | Data Type | Description | Values |
---|---|---|---|
destip | address: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 |
distributionsOfStatsKept | scalar:Uint32 | Maximum number of statistics distribution buckets to capture | RANGE: [1 , 20] DEFAULT: 1 |
dstPort | scalar: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:
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: