Configuring an Ethernet Interface Range
Configuring the Source Id Inserted in the Timestamp (Egress)
Configuring the Source Id Inserted in the Timestamp (Egress)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2",
"packetTimestampEgressSourceId": "1",
"packetTimestampState": "enable-egress"
}
}
},
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3",
"packetTimestampEgressSourceId": "1",
"packetTimestampState": "enable-egress"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/2</id>
<packetTimestampEgressSourceId>1</packetTimestampEgressSourceId>
<packetTimestampState>enable-egress</packetTimestampState>
</PhysIf-list>
<PhysIf-list>
<id>eth1/3</id>
<packetTimestampEgressSourceId>1</packetTimestampEgressSourceId>
<packetTimestampState>enable-egress</packetTimestampState>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note: This example was added in Release 9.2(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
interface ethernet 1/2-3
timestamp egress id 1
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 Ids Inserted in the Timestamp (Egress and Ingress)
Configuring the Source Ids Inserted in the Timestamp (Egress and Ingress)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2",
"packetTimestampEgressSourceId": "1",
"packetTimestampIngressSourceId": "1",
"packetTimestampState": "enable-both"
}
}
},
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3",
"packetTimestampEgressSourceId": "1",
"packetTimestampIngressSourceId": "1",
"packetTimestampState": "enable-both"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/2</id>
<packetTimestampEgressSourceId>1</packetTimestampEgressSourceId>
<packetTimestampIngressSourceId>1</packetTimestampIngressSourceId>
<packetTimestampState>enable-both</packetTimestampState>
</PhysIf-list>
<PhysIf-list>
<id>eth1/3</id>
<packetTimestampEgressSourceId>1</packetTimestampEgressSourceId>
<packetTimestampIngressSourceId>1</packetTimestampIngressSourceId>
<packetTimestampState>enable-both</packetTimestampState>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note: This example was added in Release 9.2(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
interface ethernet 1/2-3
timestamp egress id 1 ingress id 1
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 Id Inserted in the Timestamp (Ingress)
Configuring the Source Id Inserted in the Timestamp (Ingress)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2",
"packetTimestampIngressSourceId": "1",
"packetTimestampState": "enable-ingress"
}
}
},
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3",
"packetTimestampIngressSourceId": "1",
"packetTimestampState": "enable-ingress"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/2</id>
<packetTimestampIngressSourceId>1</packetTimestampIngressSourceId>
<packetTimestampState>enable-ingress</packetTimestampState>
</PhysIf-list>
<PhysIf-list>
<id>eth1/3</id>
<packetTimestampIngressSourceId>1</packetTimestampIngressSourceId>
<packetTimestampState>enable-ingress</packetTimestampState>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note: This example was added in Release 9.2(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
interface ethernet 1/2-3
timestamp ingress id 1
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 Ids Inserted in the Timestamp (Ingress and Egress)
Configuring the Source Ids Inserted in the Timestamp (Ingress and Egress)
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2",
"packetTimestampEgressSourceId": "1",
"packetTimestampIngressSourceId": "1",
"packetTimestampState": "enable-both"
}
}
},
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3",
"packetTimestampEgressSourceId": "1",
"packetTimestampIngressSourceId": "1",
"packetTimestampState": "enable-both"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/2</id>
<packetTimestampEgressSourceId>1</packetTimestampEgressSourceId>
<packetTimestampIngressSourceId>1</packetTimestampIngressSourceId>
<packetTimestampState>enable-both</packetTimestampState>
</PhysIf-list>
<PhysIf-list>
<id>eth1/3</id>
<packetTimestampEgressSourceId>1</packetTimestampEgressSourceId>
<packetTimestampIngressSourceId>1</packetTimestampIngressSourceId>
<packetTimestampState>enable-both</packetTimestampState>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note: This example was added in Release 9.2(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
interface ethernet 1/2-3
timestamp ingress id 1 egress id 1
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 Timestamp
Deleting a Timestamp
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"interfaceEntity": {
"children": [
{
"l1PhysIf": {
"attributes": {
"id": "eth1/2",
"packetTimestampState": "disable"
}
}
},
{
"l1PhysIf": {
"attributes": {
"id": "eth1/3",
"packetTimestampState": "disable"
}
}
}
]
}
}
]
}
}
{
imdata:[]
}
<System>
<intf-items>
<phys-items>
<PhysIf-list>
<id>eth1/2</id>
<packetTimestampState>disable</packetTimestampState>
</PhysIf-list>
<PhysIf-list>
<id>eth1/3</id>
<packetTimestampState>disable</packetTimestampState>
</PhysIf-list>
</phys-items>
</intf-items>
</System>
Note: This example was added in Release 9.2(3).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
interface ethernet 1/2-3
no timestamp
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: