Configuring AS-4 Dot Notation
Configuring the ASN Notation to ASDOT Format
Configuring the ASN Notation to ASDOT Format
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"l3vmEntity": {
"attributes": {
"asFormat": "asdot"
}}}]}}
{
imdata:[]
}
<System>
<l3vm-items>
<asFormat>asdot</asFormat>
</l3vm-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
as-format asdot
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue 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 |
---|---|
l3vmEntity | sys/l3vm |
l3vmEntity Properties
The following table contains information about the l3vmEntity properties in the DME 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 |
---|---|---|---|
asFormat | l3vm:AsFormatType (scalar:Enum8) | Specifies the Autonomous system number (ASN) notation to asdot format | SELECTION: 0 - asplain 1 - asdot DEFAULT: asplain |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:
Deleting the ASN Notation to ASDOT Format
Deleting the ASN Notation to ASDOT Format
POST http://<mgmt0_IP>/api/mo/sys.json
{
"topSystem": {
"children": [
{
"l3vmEntity": {
"attributes": {
"asFormat": "asplain"
}}}]}}
{
imdata:[]
}
<System>
<l3vm-items>
<asFormat>asplain</asFormat>
</l3vm-items>
</System>
Note: This example was added in Release 9.3(1).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.
no as-format asdot
Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue 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 |
---|---|
l3vmEntity | sys/l3vm |
l3vmEntity Properties
The following table contains information about the l3vmEntity properties in the DME 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 |
---|---|---|---|
asFormat | l3vm:AsFormatType (scalar:Enum8) | Specifies the Autonomous system number (ASN) notation to asdot format | SELECTION: 0 - asplain 1 - asdot DEFAULT: asplain |
Related Documentation
For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:
For detailed information about classes and attributes in the payload, see the NX-API DME Model Reference: https://developer.cisco.com/media/dme/index.html
For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide: