Configuring IS-IS in Router Configuration Mode

Configuring the Event-History Buffer Size for IS-IS Dynamic Flooding Events to Disabled

Configuring the Event-History Buffer Size for IS-IS Dynamic Flooding Events to Disabled 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "df"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>df</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
  isis event-history df size disabled


Verifying a DME Configuration

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

MODN
topSystem sys
isisEntity sys/isis
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-df
isisDom sys/isis/inst-TAG_1/dom-default


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting the Event-History Buffer Size for IS-IS Dynamic Flooding Events Configured as Disabled

Deleting the Event-History Buffer Size for IS-IS Dynamic Flooding Events Configured as Disabled 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "df"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>df</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
  no isis event-history df size disabled


Verifying a DME Configuration

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

MODN
topSystem sys
isisEntity sys/isis
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-df
isisDom sys/isis/inst-TAG_1/dom-default


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring the Event-History Buffer Size for IS-IS Dynamic Flooding Events to Small

Configuring the Event-History Buffer Size for IS-IS Dynamic Flooding Events to Small 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "df"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>df</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
  isis event-history df size small


Verifying a DME Configuration

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

MODN
topSystem sys
isisEntity sys/isis
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-df
isisDom sys/isis/inst-TAG_1/dom-default


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting the Event-History Buffer Size for IS-IS Dynamic Flooding Events Configured as Small

Deleting the Event-History Buffer Size for IS-IS Dynamic Flooding Events Configured as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "df"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>df</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
  no isis event-history df size small


Verifying a DME Configuration

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

MODN
topSystem sys
isisEntity sys/isis
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-df
isisDom sys/isis/inst-TAG_1/dom-default


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring the Event-History Buffer Size for IS-IS Dynamic Flooding Events to Medium

Configuring the Event-History Buffer Size for IS-IS Dynamic Flooding Events to Medium 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "df"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>df</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
  isis event-history df size medium


Verifying a DME Configuration

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

MODN
topSystem sys
isisEntity sys/isis
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-df
isisDom sys/isis/inst-TAG_1/dom-default


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting the Event-History Buffer Size for IS-IS Dynamic Flooding Events to Medium

Deleting the Event-History Buffer Size for IS-IS Dynamic Flooding Events to Medium 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "df"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>df</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
  no isis event-history df size medium


Verifying a DME Configuration

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

MODN
topSystem sys
isisEntity sys/isis
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-df
isisDom sys/isis/inst-TAG_1/dom-default


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring the Event-History Buffer Size for IS-IS Dynamic Flooding Events to Large

Configuring the Event-History Buffer Size for IS-IS Dynamic Flooding Events to Large 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "df"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>df</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
  isis event-history df size large


Verifying a DME Configuration

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

MODN
topSystem sys
isisEntity sys/isis
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-df
isisDom sys/isis/inst-TAG_1/dom-default


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting the Event-History Buffer Size for IS-IS Dynamic Flooding Events to Large

Deleting the Event-History Buffer Size for IS-IS Dynamic Flooding Events to Large 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "df"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>df</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
  no isis event-history df size large


Verifying a DME Configuration

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

MODN
topSystem sys
isisEntity sys/isis
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-df
isisDom sys/isis/inst-TAG_1/dom-default


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Flush Routes in RIB Upon Controlled Restart

Configuring Flush Routes in RIB Upon Controlled Restart
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "flushRoutes": "yes",
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <flushRoutes>true</flushRoutes>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 flush-routes


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
flushRoutesscalar:Bool
Flush IS-IS Routes on non graceful controlled restartSELECTION: true or false
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Flush Routes in RIB Upon Controlled Restart

Deleting Flush Routes in RIB Upon Controlled Restart
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "flushRoutes": "no",
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <flushRoutes>false</flushRoutes>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no flush-routes


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
flushRoutesscalar:Bool
Flush IS-IS Routes on non graceful controlled restartSELECTION: true or false
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Adjacency Event History Buffer Size as Disabled

Configuring Adjacency Event History Buffer Size as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "adj"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>adj</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history adjacency size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-adj
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Adjacency Event History Buffer Size as Disabled

Deleting Adjacency Event History Buffer Size as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "adj"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>adj</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history adjacency size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-adj
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Adjacency Event History Buffer Size Small

Configuring Adjacency Event History Buffer Size Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "adj"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>adj</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history adjacency size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-adj
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Adjacency Event History Buffer Size Small

Deleting Adjacency Event History Buffer Size Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "adj"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>adj</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history adjacency size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-adj
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Adjacency Event History Buffer Size Medium

Configuring Adjacency Event History Buffer Size Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "adj"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>adj</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history adjacency size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-adj
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Adjacency Event History Buffer Size Medium

Deleting Adjacency Event History Buffer Size Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "adj"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>adj</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history adjacency size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-adj
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Adjacency Event History Buffer Size Large

Configuring Adjacency Event History Buffer Size Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "adj"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>adj</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history adjacency size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-adj
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Adjacency Event History Buffer Size Large

Deleting Adjacency Event History Buffer Size Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "adj"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>adj</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history adjacency size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-adj
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring CLI Event History Buffer Size as Disabled

Configuring CLI Event History Buffer Size as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "cli"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>cli</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history cli size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-cli
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting CLI Event History Buffer Size as Disabled

Deleting CLI Event History Buffer Size as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "cli"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>cli</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history cli size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-cli
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring CLI Event History Buffer Size as Small

Configuring CLI Event History Buffer Size as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "cli"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>cli</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history cli size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-cli
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting CLI Event History Buffer Size as Small

Deleting CLI Event History Buffer Size as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "cli"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>cli</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history cli size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-cli
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring CLI Event History Buffer Size as Medium

Configuring CLI Event History Buffer Size as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "cli"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>cli</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history cli size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-cli
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting CLI Event History Buffer Size as Medium

Deleting CLI Event History Buffer Size as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "cli"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>cli</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history cli size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-cli
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring CLI Event History Buffer Size as Large

Configuring CLI Event History Buffer Size as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "cli"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>cli</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history cli size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-cli
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting CLI Event History Buffer Size as Large

Deleting CLI Event History Buffer Size as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "cli"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>cli</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history cli size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-cli
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring CSNP Event History Buffer Size as Disabled

Configuring CSNP Event History Buffer Size as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "csnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>csnp</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history csnp size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-csnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting CSNP Event History Buffer Size as Disabled

Deleting CSNP Event History Buffer Size as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "csnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>csnp</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history csnp size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-csnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring CSNP Event History Buffer Size as Small

Configuring CSNP Event History Buffer Size as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "csnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>csnp</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history csnp size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-csnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting CSNP Event History Buffer Size as Small

Deleting CSNP Event History Buffer Size as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "csnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>csnp</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history csnp size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-csnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring CSNP Event History Buffer Size as Medium

Configuring CSNP Event History Buffer Size as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "csnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>csnp</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history csnp size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-csnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting CSNP Event History Buffer Size as Medium

Deleting CSNP Event History Buffer Size as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "csnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>csnp</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history csnp size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-csnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring CSNP Event History Buffer Size as Large

Configuring CSNP Event History Buffer Size as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "csnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>csnp</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history csnp size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-csnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting CSNP Event History Buffer Size as Large

Deleting CSNP Event History Buffer Size as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "csnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>csnp</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history csnp size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-csnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring DIS Event History Buffer Size as Disabled

Configuring DIS Event History Buffer Size as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "dis"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>dis</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history dis size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-dis
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting DIS Event History Buffer Size as Disabled

Deleting DIS Event History Buffer Size as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "dis"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>dis</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history dis size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-dis
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring DIS Event History Buffer Size as Small

Configuring DIS Event History Buffer Size as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "dis"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>dis</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history dis size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-dis
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting DIS Event History Buffer Size as Small

Deleting DIS Event History Buffer Size as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "dis"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>dis</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history dis size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-dis
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring DIS Event History Buffer Size as Medium

Configuring DIS Event History Buffer Size as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "dis"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>dis</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history dis size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-dis
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting DIS Event History Buffer Size as Medium

Deleting DIS Event History Buffer Size as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "dis"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>dis</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history dis size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-dis
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring DIS Event History Buffer Size as Large

Configuring DIS Event History Buffer Size as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "dis"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>dis</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history dis size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-dis
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting DIS Event History Buffer Size as Large

Deleting DIS Event History Buffer Size as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "dis"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>dis</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history dis size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-dis
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for Events as Disabled

Configuring Event History Buffer Size for Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "events"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>events</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history events size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-events
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for Events as Disabled

Deleting Event History Buffer Size for Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "events"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>events</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history events size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-events
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for Events as Small

Configuring Event History Buffer Size for Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "events"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>events</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history events size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-events
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for Events as Small

Deleting Event History Buffer Size for Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "events"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>events</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history events size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-events
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for Events as Medium

Configuring Event History Buffer Size for Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "events"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>events</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history events size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-events
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for Events as Medium

Deleting Event History Buffer Size for Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "events"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>events</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history events size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-events
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for Events as Large

Configuring Event History Buffer Size for Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "events"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>events</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history events size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-events
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for Events as Large

Deleting Event History Buffer Size for Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "events"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>events</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history events size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-events
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for Graceful Restart Events as Disabled

Configuring Event History Buffer Size for Graceful Restart Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "gr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>gr</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history graceful size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-gr
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for Graceful Restart Events as Disabled

Deleting Event History Buffer Size for Graceful Restart Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "gr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>gr</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history graceful size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-gr
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for Graceful Restart Events as Small

Configuring Event History Buffer Size for Graceful Restart Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "gr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>gr</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history graceful size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-gr
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for Graceful Restart Events as Small

Deleting Event History Buffer Size for Graceful Restart Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "gr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>gr</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history graceful size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-gr
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for Graceful Restart Events as Medium

Configuring Event History Buffer Size for Graceful Restart Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "gr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>gr</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history graceful size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-gr
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for Graceful Restart Events as Medium

Deleting Event History Buffer Size for Graceful Restart Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "gr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>gr</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history graceful size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-gr
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for Graceful Restart Events as Large

Configuring Event History Buffer Size for Graceful Restart Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "gr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>gr</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history graceful size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-gr
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for Graceful Restart Events as Large

Deleting Event History Buffer Size for Graceful Restart Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "gr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>gr</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history graceful size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-gr
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for HA Events as Disabled

Configuring Event History Buffer Size for HA Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "ha"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>ha</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history ha size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ha
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer for HA Events as Disabled

Deleting Event History Buffer for HA Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "ha"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>ha</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history ha size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ha
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for HA Events as Small

Configuring Event History Buffer Size for HA Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "ha"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>ha</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history ha size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ha
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for HA Events as Small

Deleting Event History Buffer Size for HA Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "ha"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>ha</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history ha size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ha
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for HA Events as Medium

Configuring Event History Buffer Size for HA Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "ha"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>ha</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history ha size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ha
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for HA Events as Medium

Deleting Event History Buffer Size for HA Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "ha"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>ha</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history ha size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ha
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for HA Events as Large

Configuring Event History Buffer Size for HA Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "ha"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>ha</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history ha size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ha
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for HA Events as Large

Deleting Event History Buffer Size for HA Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "ha"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>ha</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history ha size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ha
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for IIH Events as Disabled

Configuring Event History Buffer Size for IIH Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "iih"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>iih</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history iih size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-iih
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for IIH Events as Disabled

Deleting Event History Buffer Size for IIH Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "iih"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>iih</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history iih size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-iih
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for IIH Events as Small

Configuring Event History Buffer Size for IIH Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "iih"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>iih</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history iih size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-iih
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for IIH Events as Small

Deleting Event History Buffer Size for IIH Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "iih"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>iih</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history iih size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-iih
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for IIH Events as Medium

Configuring Event History Buffer Size for IIH Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "iih"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>iih</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history iih size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-iih
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for IIH Events as Medium

Deleting Event History Buffer Size for IIH Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "iih"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>iih</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history iih size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-iih
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for IIH Events as Large

Configuring Event History Buffer Size for IIH Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "iih"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>iih</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history iih size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-iih
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for IIH Events as Large

Deleting Event History Buffer Size for IIH Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "iih"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>iih</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history iih size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-iih
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for LSP-Gen Events as Disabled

Configuring Event History Buffer Size for LSP-Gen Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "lspGen"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>lspGen</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history lsp-gen size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspGen
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for LSP-Gen Events as Disabled

Deleting Event History Buffer Size for LSP-Gen Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "lspGen"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>lspGen</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history lsp-gen size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspGen
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for LSP-Gen Events as Small

Configuring Event History Buffer Size for LSP-Gen Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "lspGen"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>lspGen</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history lsp-gen size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspGen
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for LSP-Gen Events as Small

Deleting Event History Buffer Size for LSP-Gen Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "lspGen"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>lspGen</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history lsp-gen size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspGen
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for LSP-Gen Events as Medium

Configuring Event History Buffer Size for LSP-Gen Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "lspGen"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>lspGen</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history lsp-gen size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspGen
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for LSP-Gen Events as Medium

Deleting Event History Buffer Size for LSP-Gen Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "lspGen"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>lspGen</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history lsp-gen size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspGen
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for LSP-Gen Events as Large

Configuring Event History Buffer Size for LSP-Gen Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "lspGen"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>lspGen</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history lsp-gen size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspGen
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for LSP-Gen Events as Large

Deleting Event History Buffer Size for LSP-Gen Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "lspGen"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>lspGen</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history lsp-gen size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspGen
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for PSNP Events as Disabled

Configuring Event History Buffer Size for PSNP Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "psnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>psnp</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history psnp size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-psnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for PSNP Events as Disabled

Deleting Event History Buffer Size for PSNP Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "psnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>psnp</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history psnp size disabled


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-psnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for PSNP Events as Small

Configuring Event History Buffer Size for PSNP Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "psnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>psnp</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history psnp size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-psnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for PSNP Events as Small

Deleting Event History Buffer Size for PSNP Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "psnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>psnp</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history psnp size small


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-psnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for PSNP Events as Medium

Configuring Event History Buffer Size for PSNP Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "psnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>psnp</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history psnp size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-psnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Deleting Event History Buffer Size for PSNP Events as Medium

Deleting Event History Buffer Size for PSNP Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "psnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>psnp</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 no isis event-history psnp size medium


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-psnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

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

Configuring Event History Buffer Size for PSNP Events as Large

Configuring Event History Buffer Size for PSNP Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "psnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>psnp</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

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


CLI Commands

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

router isis TAG_1
 isis event-history psnp size large


Verifying a DME Configuration

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

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-psnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

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

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

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

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

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

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for PSNP Events as Large

Deleting Event History Buffer Size for PSNP Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "psnp"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>psnp</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history psnp size large


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisEvtHstry sys/isis/inst-TAG_1/evthstry-psnp
isisDom sys/isis/inst-TAG_1/dom-default
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for SPF-Leaf Events As Disabled

Configuring Event History Buffer Size for SPF-Leaf Events As Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "spfLeaf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>spfLeaf</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history spf-leaf size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfLeaf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for SPF-Leaf Events As Disabled

Deleting Event History Buffer Size for SPF-Leaf Events As Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "spfLeaf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>spfLeaf</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history spf-leaf size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfLeaf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for SPF-Leaf Events as Small

Configuring Event History Buffer Size for SPF-Leaf Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "spfLeaf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>spfLeaf</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history spf-leaf size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfLeaf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for SPF-Leaf Events as Small

Deleting Event History Buffer Size for SPF-Leaf Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "spfLeaf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>spfLeaf</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history spf-leaf size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfLeaf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for SPF-Leaf Events as Medium

Configuring Event History Buffer Size for SPF-Leaf Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "spfLeaf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>spfLeaf</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history spf-leaf size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfLeaf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for SPF-Leaf Events as Medium

Deleting Event History Buffer Size for SPF-Leaf Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "spfLeaf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>spfLeaf</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history spf-leaf size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfLeaf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for SPF-Leaf Events as Large

Configuring Event History Buffer Size for SPF-Leaf Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "spfLeaf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>spfLeaf</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history spf-leaf size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfLeaf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for SPF-Leaf Events as Large

Deleting Event History Buffer Size for SPF-Leaf Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "spfLeaf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>spfLeaf</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history spf-leaf size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfLeaf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for LSP-Flood Events as Disabled

Configuring Event History Buffer Size for LSP-Flood Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "lspFlood"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>lspFlood</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history lsp-flood size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspFlood
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for LSP-Flood Events as Disabled

Deleting Event History Buffer Size for LSP-Flood Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "lspFlood"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>lspFlood</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history lsp-flood size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspFlood
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for LSP-Flood Events as Small

Configuring Event History Buffer Size for LSP-Flood Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "lspFlood"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>lspFlood</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history lsp-flood size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspFlood
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for LSP-Flood Events as Small

Deleting Event History Buffer Size for LSP-Flood Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "lspFlood"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>lspFlood</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history lsp-flood size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspFlood
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for LSP-Flood Events as Medium

Configuring Event History Buffer Size for LSP-Flood Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "lspFlood"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>lspFlood</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history lsp-flood size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspFlood
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for LSP-Flood Events as Medium

Deleting Event History Buffer Size for LSP-Flood Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "lspFlood"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>lspFlood</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history lsp-flood size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspFlood
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for LSP-Flood Events as Large

Configuring Event History Buffer Size for LSP-Flood Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "lspFlood"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>lspFlood</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history lsp-flood size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspFlood
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for LSP-Flood Events as Large

Deleting Event History Buffer Size for LSP-Flood Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "lspFlood"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>lspFlood</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history lsp-flood size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-lspFlood
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for MTR Events as Disabled

Configuring Event History Buffer Size for MTR Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "mtr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>mtr</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history mtr size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-mtr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for MTR Events as Disabled

Deleting Event History Buffer Size for MTR Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "mtr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>mtr</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history mtr size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-mtr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for MTR Events as Small

Configuring Event History Buffer Size for MTR Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "mtr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>mtr</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history mtr size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-mtr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for MTR Events as Small

Deleting Event History Buffer Size for MTR Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "mtr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>mtr</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history mtr size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-mtr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for MTR Events as Medium

Configuring Event History Buffer Size for MTR Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "mtr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>mtr</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history mtr size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-mtr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for MTR Events as Medium

Deleting Event History Buffer Size for MTR Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "mtr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>mtr</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history mtr size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-mtr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for MTR Events as Large

Configuring Event History Buffer Size for MTR Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "mtr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>mtr</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history mtr size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-mtr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for MTR Events as Large

Deleting Event History Buffer Size for MTR Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "mtr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>mtr</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history mtr size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-mtr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for Performance Events as Disabled

Configuring Event History Buffer Size for Performance Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "perf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>perf</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history perf size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-perf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for Performance Events as Disabled

Deleting Event History Buffer Size for Performance Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "perf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>perf</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history perf size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-perf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for Performance Events as Small

Configuring Event History Buffer Size for Performance Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "perf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>perf</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history perf size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-perf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for Performance Events as Small

Deleting Event History Buffer Size for Performance Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "perf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>perf</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history perf size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-perf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for Performance Events as Medium

Configuring Event History Buffer Size for Performance Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "perf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>perf</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history perf size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-perf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for Performance Events as Medium

Deleting Event History Buffer Size for Performance Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "perf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>perf</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history perf size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-perf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for Performance Events as Large

Configuring Event History Buffer Size for Performance Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "perf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>perf</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history perf size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-perf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for Performance Events as Large

Deleting Event History Buffer Size for Performance Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "perf"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>perf</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history perf size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-perf
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for Redist Events as Disabled

Configuring Event History Buffer Size for Redist Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "redist"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>redist</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history redist size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-redist
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for Redist Events as Disabled

Deleting Event History Buffer Size for Redist Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "redist"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>redist</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history redist size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-redist
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for Redist Events as Small

Configuring Event History Buffer Size for Redist Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "redist"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>redist</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history redist size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-redist
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for Redist Events as Small

Deleting Event History Buffer Size for Redist Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "redist"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>redist</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history redist size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-redist
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for Redist Events as Medium

Configuring Event History Buffer Size for Redist Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "redist"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>redist</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history redist size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-redist
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for Redist Events as Medium

Deleting Event History Buffer Size for Redist Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "redist"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>redist</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history redist size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-redist
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for Redist Events as Large

Configuring Event History Buffer Size for Redist Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "redist"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>redist</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history redist size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-redist
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for Redist Events as Large

Deleting Event History Buffer Size for Redist Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "redist"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>redist</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history redist size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-redist
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for SPF-Tree Events as Disabled

Configuring Event History Buffer Size for SPF-Tree Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "spfTree"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>spfTree</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history spf-tree size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfTree
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for SPF-Tree Events as Disabled

Deleting Event History Buffer Size for SPF-Tree Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "spfTree"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>spfTree</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history spf-tree size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfTree
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for SPF-Tree Events as Small

Configuring Event History Buffer Size for SPF-Tree Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "spfTree"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>spfTree</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history spf-tree size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfTree
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for SPF-Tree Events as Small

Deleting Event History Buffer Size for SPF-Tree Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "spfTree"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>spfTree</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history spf-tree size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfTree
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for SPF-Tree Events as Medium

Configuring Event History Buffer Size for SPF-Tree Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "spfTree"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>spfTree</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history spf-tree size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfTree
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for SPF-Tree Events as Medium

Deleting Event History Buffer Size for SPF-Tree Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "spfTree"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>spfTree</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history spf-tree size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfTree
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for SPF-Tree Events as Large

Configuring Event History Buffer Size for SPF-Tree Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "spfTree"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>spfTree</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history spf-tree size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfTree
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for SPF-Tree Events as Large

Deleting Event History Buffer Size for SPF-Tree Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "spfTree"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>spfTree</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history spf-tree size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-spfTree
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for SR Events as Disabled

Configuring Event History Buffer Size for SR Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "sr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>sr</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history sr size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-sr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for SR Events as Disabled

Deleting Event History Buffer Size for SR Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "sr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>sr</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history sr size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-sr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for SR Events as Small

Configuring Event History Buffer Size for SR Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "sr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>sr</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history sr size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-sr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for SR Events as Small

Deleting Event History Buffer Size for SR Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "sr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>sr</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history sr size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-sr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for SR Events Events as Medium

Configuring Event History Buffer Size for SR Events Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "sr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>sr</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history sr size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-sr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for SR Events Events as Medium

Deleting Event History Buffer Size for SR Events Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "sr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>sr</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history sr size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-sr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for SR Events Events as Large

Configuring Event History Buffer Size for SR Events Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "sr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>sr</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history sr size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-sr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for SR Events Events as Large

Deleting Event History Buffer Size for SR Events Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "sr"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>sr</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history sr size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-sr
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for TLV Events as Disabled

Configuring Event History Buffer Size for TLV Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "tlv"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>tlv</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history tlv size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-tlv
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for TLV Events as Disabled

Deleting Event History Buffer Size for TLV Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "tlv"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>tlv</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history tlv size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-tlv
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for TLV Events as Small

Configuring Event History Buffer Size for TLV Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "tlv"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>tlv</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history tlv size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-tlv
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for TLV Events as Small

Deleting Event History Buffer Size for TLV Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "tlv"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>tlv</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history tlv size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-tlv
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for TLV Events as Medium

Configuring Event History Buffer Size for TLV Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "tlv"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>tlv</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history tlv size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-tlv
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for TLV Events as Medium

Deleting Event History Buffer Size for TLV Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "tlv"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>tlv</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history tlv size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-tlv
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for TLV Events as Large

Configuring Event History Buffer Size for TLV Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "tlv"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>tlv</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history tlv size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-tlv
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for TLV Events as Large

Deleting Event History Buffer Size for TLV Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "tlv"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>tlv</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history tlv size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-tlv
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for ULIB Events as Disabled

Configuring Event History Buffer Size for ULIB Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "ulib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>ulib</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history ulib size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ulib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for ULIB Events as Disabled

Deleting Event History Buffer Size for ULIB Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "ulib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>ulib</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history ulib size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ulib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for ULIB Events as Small

Configuring Event History Buffer Size for ULIB Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "ulib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>ulib</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history ulib size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ulib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for ULIB Events as Small

Deleting Event History Buffer Size for ULIB Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "ulib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>ulib</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history ulib size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ulib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for ULIB Events as Medium

Configuring Event History Buffer Size for ULIB Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "ulib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>ulib</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history ulib size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ulib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for ULIB Events as Medium

Deleting Event History Buffer Size for ULIB Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "ulib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>ulib</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history ulib size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ulib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for ULIB Events as Large

Configuring Event History Buffer Size for ULIB Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "ulib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>ulib</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history ulib size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ulib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for ULIB Events as Large

Deleting Event History Buffer Size for ULIB Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "ulib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>ulib</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history ulib size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-ulib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for URIB Events as Disabled

Configuring Event History Buffer Size for URIB Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "disabled",
                        "type": "urib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>urib</type>
            <size>1</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history urib size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-urib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for URIB Events as Disabled

Deleting Event History Buffer Size for URIB Events as Disabled
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "urib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>urib</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history urib size disabled


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-urib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for URIB Events as Small

Configuring Event History Buffer Size for URIB Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "small",
                        "type": "urib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>urib</type>
            <size>2</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history urib size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-urib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for URIB Events as Small

Deleting Event History Buffer Size for URIB Events as Small
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "urib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>urib</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history urib size small


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-urib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for URIB Events as Medium

Configuring Event History Buffer Size for URIB Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "medium",
                        "type": "urib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>urib</type>
            <size>3</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history urib size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-urib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for URIB Events as Medium

Deleting Event History Buffer Size for URIB Events as Medium
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "urib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>urib</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history urib size medium


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-urib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Event History Buffer Size for URIB Events as Large

Configuring Event History Buffer Size for URIB Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "size": "large",
                        "type": "urib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list>
            <type>urib</type>
            <size>4</size>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isis event-history urib size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-urib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
sizeisis:EhSize
(scalar:Uint32)
configures buffer size in text/kb
RANGE: [0 , 4294967295]
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Event History Buffer Size for URIB Events as Large

Deleting Event History Buffer Size for URIB Events as Large
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisEvtHstry": {
                      "attributes": {
                        "status": "deleted",
                        "type": "urib"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <evthstry-items>
          <EvtHstry-list nc:operation="delete">
            <type>urib</type>
          </EvtHstry-list>
        </evthstry-items>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isis event-history urib size large


Verifying a DME Configuration
The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisDom sys/isis/inst-TAG_1/dom-default
isisEvtHstry sys/isis/inst-TAG_1/evthstry-urib
isisInst sys/isis/inst-TAG_1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisEvtHstry Properties

The following table contains information about the isisEvtHstry properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced
typeisis:EhType
(scalar:Enum32)
configures type of event historySELECTION:
0 - spfLeaf
1 - spfTree
2 - psnp
3 - csnp
4 - lspGen
5 - lspFlood
6 - iih
7 - adj
8 - dis
9 - events
10 - cli
11 - ha
12 - gr
13 - urib
14 - redist
15 - tlv
16 - mtr
17 - perf
18 - df
19 - sr
20 - ulib


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Isolating this Router from BGP Perspective

Isolating this Router from BGP Perspective
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "isolate": "yes",
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <isolate>true</isolate>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 isolate


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
isolatescalar:Bool
Isolate IS-IS Instance from other process tagsSELECTION: true or false
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Config for Isolating this Router from BGP Perspective

Deleting Config for Isolating this Router from BGP Perspective
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "isolate": "no",
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
}}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <isolate>false</isolate>
        <dom-items>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 no isolate


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
isolatescalar:Bool
Isolate IS-IS Instance from other process tagsSELECTION: true or false
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Adjacency Protocol Support Consistency Checker

Configuring Adjacency Protocol Support Consistency Checker
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "ctrl": "adj-check,set-attached-bit",
                        "type": "v4"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <ctrl>adj-check,set-attached-bit</ctrl>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv4 unicast
  adjacency-check


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v4
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
ctrlisis:DomAfControl
(scalar:Bitmask8)
The address family controls. This determines the address family to run. Note that IPv4 and IPv6 are both supported.SELECTION:
1 - adj-check
2 - set-attached-bit
DEFAULT: adj-check,set-attached-bit
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Adjacency Protocol Support Consistency Checker

Deleting Adjacency Protocol Support Consistency Checker
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "ctrl": "set-attached-bit",
                        "type": "v4"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <ctrl>set-attached-bit</ctrl>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv4 unicast
  no adjacency-check


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v4
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
ctrlisis:DomAfControl
(scalar:Bitmask8)
The address family controls. This determines the address family to run. Note that IPv4 and IPv6 are both supported.SELECTION:
1 - adj-check
2 - set-attached-bit
DEFAULT: adj-check,set-attached-bit
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring IPv4 BFD on all IS-IS interfaces

Configuring IPv4 BFD on all IS-IS interfaces
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "enableBfd": "yes",
                        "type": "v4"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <enableBfd>true</enableBfd>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv4 unicast
  bfd


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v4
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
enableBfdscalar:Bool
Enabling BFD on all IS-IS domain interfacesSELECTION: true or false
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting IPv4 BFD on all IS-IS interfaces

Deleting IPv4 BFD on all IS-IS interfaces
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "enableBfd": "no",
                        "type": "v4"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <enableBfd>false</enableBfd>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv4 unicast
  no bfd


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v4
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
enableBfdscalar:Bool
Enabling BFD on all IS-IS domain interfacesSELECTION: true or false
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Distribution of Routes Between IS-IS Levels

Configuring Distribution of Routes Between IS-IS Levels
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v4"
                      },
                      "children": [
                        {
                          "isisDistribute": {
                            "attributes": {
                              "all": "yes",
                              "destination": "l2",
                              "rmap": "",
                              "source": "l1"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <distribute-items>
                  <Distribute-list>
                    <source>l1</source>
                    <all>true</all>
                    <destination>l2</destination>
                    <rmap></rmap>
                  </Distribute-list>
                </distribute-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv4 unicast
  distribute level-1 into level-2 all


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v4
isisDistribute sys/isis/inst-TAG_1/dom-default/af-v4/distribute-l1
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisDistribute Properties

The following table contains information about the isisDistribute properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
allscalar:Bool
Holds Distribution of all level-n routesSELECTION: true or false
DEFAULT: no
destinationisis:LvlT
(scalar:Enum8)
Holds Destination Domain for Routes Distribute PolicySELECTION:
0 - p2p
1 - l1
2 - l2
DEFAULT: l1
rmapstring:Basic
Holds Route-map name for Distribute PolicyA sequence of characters
sourceisis:LvlT
(scalar:Enum8)
Holds Source Domain for Routes Distribute PolicySELECTION:
0 - p2p
1 - l1
2 - l2
DEFAULT: l1


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Distribution of Routes Between IS-IS Levels

Deleting Distribution of Routes Between IS-IS Levels
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v4"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv4 unicast
  no distribute level-1 into level-2 all


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v4
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Route Map to Constrain Distribution

Configuring a Route Map to Constrain Distribution
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v4"
                      },
                      "children": [
                        {
                          "isisDistribute": {
                            "attributes": {
                              "all": "no",
                              "destination": "l2",
                              "rmap": "SampleString_123",
                              "source": "l1"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <distribute-items>
                  <Distribute-list>
                    <source>l1</source>
                    <all>false</all>
                    <destination>l2</destination>
                    <rmap>SampleString_123</rmap>
                  </Distribute-list>
                </distribute-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv4 unicast
  distribute level-1 into level-2 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v4
isisDistribute sys/isis/inst-TAG_1/dom-default/af-v4/distribute-l1
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisDistribute Properties

The following table contains information about the isisDistribute properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
allscalar:Bool
Holds Distribution of all level-n routesSELECTION: true or false
DEFAULT: no
destinationisis:LvlT
(scalar:Enum8)
Holds Destination Domain for Routes Distribute PolicySELECTION:
0 - p2p
1 - l1
2 - l2
DEFAULT: l1
rmapstring:Basic
Holds Route-map name for Distribute PolicyA sequence of characters
sourceisis:LvlT
(scalar:Enum8)
Holds Source Domain for Routes Distribute PolicySELECTION:
0 - p2p
1 - l1
2 - l2
DEFAULT: l1


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Distribution of Routes Between IS-IS Levels

Deleting Distribution of Routes Between IS-IS Levels
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v4"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv4 unicast
  no distribute level-1 into level-2 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v4
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring the Maximum Paths per Destination

Configuring the Maximum Paths per Destination 
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "maxEcmp": "31",
                        "type": "v4"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <maxEcmp>31</maxEcmp>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv4 unicast
  maximum-paths 31


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v4
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
maxEcmpisis:Ecmp
(scalar:UByte)
Holds IS-IS Domain address family Max ECMP value
RANGE: [1 , 64]
DEFAULT: 8
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting the Maximum Paths per Destination

Deleting the Maximum Paths per Destination 
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "maxEcmp": "8",
                        "type": "v4"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <maxEcmp>8</maxEcmp>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv4 unicast
  no maximum-paths 31


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v4
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
maxEcmpisis:Ecmp
(scalar:UByte)
Holds IS-IS Domain address family Max ECMP value
RANGE: [1 , 64]
DEFAULT: 8
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

CLI: adjacency-check

CLI: adjacency-check
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "ctrl": "adj-check,set-attached-bit",
                        "type": "v6"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <ctrl>adj-check,set-attached-bit</ctrl>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  adjacency-check


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
ctrlisis:DomAfControl
(scalar:Bitmask8)
The address family controls. This determines the address family to run. Note that IPv4 and IPv6 are both supported.SELECTION:
1 - adj-check
2 - set-attached-bit
DEFAULT: adj-check,set-attached-bit
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

CLI: no adjacency-check

CLI: no adjacency-check
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "ctrl": "set-attached-bit",
                        "type": "v6"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <ctrl>set-attached-bit</ctrl>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  no adjacency-check


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
ctrlisis:DomAfControl
(scalar:Bitmask8)
The address family controls. This determines the address family to run. Note that IPv4 and IPv6 are both supported.SELECTION:
1 - adj-check
2 - set-attached-bit
DEFAULT: adj-check,set-attached-bit
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring IPv4 BFD on all IS-IS interfaces

Configuring IPv4 BFD on all IS-IS interfaces
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "enableBfd": "yes",
                        "type": "v6"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <enableBfd>true</enableBfd>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  bfd


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
enableBfdscalar:Bool
Enabling BFD on all IS-IS domain interfacesSELECTION: true or false
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting IPv4 BFD on all IS-IS interfaces

Deleting IPv4 BFD on all IS-IS interfaces
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "enableBfd": "no",
                        "type": "v6"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <enableBfd>false</enableBfd>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  no bfd


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
enableBfdscalar:Bool
Enabling BFD on all IS-IS domain interfacesSELECTION: true or false
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring to Apply Metric to Level-2 Links
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  isis ipv6 metric 1 level-2


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring to Apply Metric to Level-2 Links
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  no isis ipv6 metric 1 level-2


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Multitopology Transition Mode

Configuring Multitopology Transition Mode
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "mtType": "mtt",
                        "type": "v6"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <mtType>mtt</mtType>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  multi-topology transition


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
mtTypeisis:TopoT
(scalar:Enum8)
Holds IS-IS Domain address family Multi-topology informationSELECTION:
1 - st
2 - mt
3 - mtt
DEFAULT: st
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Multitopology Transition Mode

Deleting Multitopology Transition Mode
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "mtType": "st",
                        "type": "v6"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <mtType>st</mtType>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  no multi-topology transition


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
mtTypeisis:TopoT
(scalar:Enum8)
Holds IS-IS Domain address family Multi-topology informationSELECTION:
1 - st
2 - mt
3 - mtt
DEFAULT: st
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Policy to Constrain Redistribution

Configuring a Policy to Constrain Redistribution
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisInterLeakP": {
                            "attributes": {
                              "asn": "none",
                              "inst": "none",
                              "proto": "amt",
                              "rtMap": "SampleString_123"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <interleak-items>
                  <InterLeakP-list>
                    <proto>amt</proto>
                    <inst>none</inst>
                    <asn>none</asn>
                    <rtMap>SampleString_123</rtMap>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  redistribute amt route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisInterLeakP sys/isis/inst-TAG_1/dom-default/af-v6/interleak-none
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
rtMapstring:Basic
The name of the default route leak policy route map. This route map name is used to control distribution.A sequence of characters


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting a Policy to Constrain Redistribution

Deleting a Policy to Constrain Redistribution
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisInterLeakP": {
                            "attributes": {
                              "asn": "none",
                              "inst": "none",
                              "proto": "amt",
                              "status": "deleted"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <interleak-items>
                  <InterLeakP-list nc:operation="delete">
                    <proto>amt</proto>
                    <inst>none</inst>
                    <asn>none</asn>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  no redistribute amt route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisInterLeakP sys/isis/inst-TAG_1/dom-default/af-v6/interleak-none
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Policy to Constrain Redistribution (BGP)

Configuring a Policy to Constrain Redistribution (BGP)
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisInterLeakP": {
                            "attributes": {
                              "asn": "123",
                              "inst": "none",
                              "proto": "bgp",
                              "rtMap": "SampleString_123"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <interleak-items>
                  <InterLeakP-list>
                    <proto>bgp</proto>
                    <inst>none</inst>
                    <asn>123</asn>
                    <rtMap>SampleString_123</rtMap>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  redistribute bgp 123 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisInterLeakP sys/isis/inst-TAG_1/dom-default/af-v6/interleak-123
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
rtMapstring:Basic
The name of the default route leak policy route map. This route map name is used to control distribution.A sequence of characters


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting a Policy to Constrain Redistribution (BGP)

Deleting a Policy to Constrain Redistribution (BGP)
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisInterLeakP": {
                            "attributes": {
                              "asn": "123",
                              "inst": "none",
                              "proto": "bgp",
                              "status": "deleted"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <interleak-items>
                  <InterLeakP-list nc:operation="delete">
                    <proto>bgp</proto>
                    <inst>none</inst>
                    <asn>123</asn>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  no redistribute bgp 123 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisInterLeakP sys/isis/inst-TAG_1/dom-default/af-v6/interleak-123
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Policy to Constrain Redistribution (Directly Connected)

Configuring a Policy to Constrain Redistribution (Directly Connected)
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisInterLeakP": {
                            "attributes": {
                              "asn": "none",
                              "inst": "none",
                              "proto": "direct",
                              "rtMap": "SampleString_123"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <interleak-items>
                  <InterLeakP-list>
                    <proto>direct</proto>
                    <inst>none</inst>
                    <asn>none</asn>
                    <rtMap>SampleString_123</rtMap>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  redistribute direct route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisInterLeakP sys/isis/inst-TAG_1/dom-default/af-v6/interleak-none
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
rtMapstring:Basic
The name of the default route leak policy route map. This route map name is used to control distribution.A sequence of characters


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting a Policy to Constrain Redistribution (Directly Connected)

Deleting a Policy to Constrain Redistribution (Directly Connected)
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisInterLeakP": {
                            "attributes": {
                              "asn": "none",
                              "inst": "none",
                              "proto": "direct",
                              "status": "deleted"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <interleak-items>
                  <InterLeakP-list nc:operation="delete">
                    <proto>direct</proto>
                    <inst>none</inst>
                    <asn>none</asn>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  no redistribute direct route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisInterLeakP sys/isis/inst-TAG_1/dom-default/af-v6/interleak-none
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Policy to Constrain Redistribution (EIGRP)

Configuring a Policy to Constrain Redistribution (EIGRP)
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisInterLeakP": {
                            "attributes": {
                              "asn": "none",
                              "inst": "SampleString_123",
                              "proto": "eigrp",
                              "rtMap": "SampleString_123"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <interleak-items>
                  <InterLeakP-list>
                    <proto>eigrp</proto>
                    <inst>SampleString_123</inst>
                    <asn>none</asn>
                    <rtMap>SampleString_123</rtMap>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  redistribute eigrp SampleString_123 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisInterLeakP sys/isis/inst-TAG_1/dom-default/af-v6/interleak-none
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
rtMapstring:Basic
The name of the default route leak policy route map. This route map name is used to control distribution.A sequence of characters


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting a Policy to Constrain Redistribution (EIGRP)

Deleting a Policy to Constrain Redistribution (EIGRP)
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisInterLeakP": {
                            "attributes": {
                              "asn": "none",
                              "inst": "SampleString_123",
                              "proto": "eigrp",
                              "status": "deleted"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <interleak-items>
                  <InterLeakP-list nc:operation="delete">
                    <proto>eigrp</proto>
                    <inst>SampleString_123</inst>
                    <asn>none</asn>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  no redistribute eigrp SampleString_123 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisInterLeakP sys/isis/inst-TAG_1/dom-default/af-v6/interleak-none
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Policy to Constrain Redistribution

Configuring Policy to Constrain Redistribution
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisInterLeakP": {
                            "attributes": {
                              "asn": "none",
                              "inst": "SampleString_123",
                              "proto": "ospfv3",
                              "rtMap": "SampleString_123"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <interleak-items>
                  <InterLeakP-list>
                    <proto>ospfv3</proto>
                    <inst>SampleString_123</inst>
                    <asn>none</asn>
                    <rtMap>SampleString_123</rtMap>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  redistribute ospfv3 SampleString_123 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisInterLeakP sys/isis/inst-TAG_1/dom-default/af-v6/interleak-none
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
rtMapstring:Basic
The name of the default route leak policy route map. This route map name is used to control distribution.A sequence of characters


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Policy to Constrain Redistribution

Deleting Policy to Constrain Redistribution
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisInterLeakP": {
                            "attributes": {
                              "asn": "none",
                              "inst": "SampleString_123",
                              "proto": "ospfv3",
                              "status": "deleted"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <interleak-items>
                  <InterLeakP-list nc:operation="delete">
                    <proto>ospfv3</proto>
                    <inst>SampleString_123</inst>
                    <asn>none</asn>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  no redistribute ospfv3 SampleString_123 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisInterLeakP sys/isis/inst-TAG_1/dom-default/af-v6/interleak-none
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Policy to Constrain Redistribution (RIP)

Configuring a Policy to Constrain Redistribution (RIP)
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisInterLeakP": {
                            "attributes": {
                              "asn": "none",
                              "inst": "SampleString_123",
                              "proto": "rip",
                              "rtMap": "SampleString_123"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <interleak-items>
                  <InterLeakP-list>
                    <proto>rip</proto>
                    <inst>SampleString_123</inst>
                    <asn>none</asn>
                    <rtMap>SampleString_123</rtMap>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  redistribute rip SampleString_123 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisInterLeakP sys/isis/inst-TAG_1/dom-default/af-v6/interleak-none
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
rtMapstring:Basic
The name of the default route leak policy route map. This route map name is used to control distribution.A sequence of characters


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting a Policy to Constrain Redistribution (RIP)

Deleting a Policy to Constrain Redistribution (RIP)
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisInterLeakP": {
                            "attributes": {
                              "asn": "none",
                              "inst": "SampleString_123",
                              "proto": "rip",
                              "status": "deleted"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <interleak-items>
                  <InterLeakP-list nc:operation="delete">
                    <proto>rip</proto>
                    <inst>SampleString_123</inst>
                    <asn>none</asn>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  no redistribute rip SampleString_123 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisInterLeakP sys/isis/inst-TAG_1/dom-default/af-v6/interleak-none
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Policy to Constrain Redistribution (Static)

Configuring a Policy to Constrain Redistribution (Static)
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisInterLeakP": {
                            "attributes": {
                              "asn": "none",
                              "inst": "none",
                              "proto": "static",
                              "rtMap": "SampleString_123"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <interleak-items>
                  <InterLeakP-list>
                    <proto>static</proto>
                    <inst>none</inst>
                    <asn>none</asn>
                    <rtMap>SampleString_123</rtMap>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  redistribute static route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisInterLeakP sys/isis/inst-TAG_1/dom-default/af-v6/interleak-none
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
rtMapstring:Basic
The name of the default route leak policy route map. This route map name is used to control distribution.A sequence of characters


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting a Policy to Constrain Redistribution (Static)

Deleting a Policy to Constrain Redistribution (Static)
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisInterLeakP": {
                            "attributes": {
                              "asn": "none",
                              "inst": "none",
                              "proto": "static",
                              "status": "deleted"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <interleak-items>
                  <InterLeakP-list nc:operation="delete">
                    <proto>static</proto>
                    <inst>none</inst>
                    <asn>none</asn>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  no redistribute static route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisInterLeakP sys/isis/inst-TAG_1/dom-default/af-v6/interleak-none
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring L1|L2 Router to Set/Unset Attached Bit in its L1 LSP

Configuring L1|L2 Router to Set/Unset Attached  Bit in its L1 LSP
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "ctrl": "adj-check,set-attached-bit",
                        "type": "v6"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <ctrl>adj-check,set-attached-bit</ctrl>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  set-attached-bit


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
ctrlisis:DomAfControl
(scalar:Bitmask8)
The address family controls. This determines the address family to run. Note that IPv4 and IPv6 are both supported.SELECTION:
1 - adj-check
2 - set-attached-bit
DEFAULT: adj-check,set-attached-bit
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting L1|L2 Router to Set/Unset Attached Bit in its L1 LSP

Deleting L1|L2 Router to Set/Unset Attached  Bit in its L1 LSP
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "ctrl": "adj-check",
                        "type": "v6"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <ctrl>adj-check</ctrl>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  no set-attached-bit


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
ctrlisis:DomAfControl
(scalar:Bitmask8)
The address family controls. This determines the address family to run. Note that IPv4 and IPv6 are both supported.SELECTION:
1 - adj-check
2 - set-attached-bit
DEFAULT: adj-check,set-attached-bit
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Distribution of Routes Between IS-IS Levels

Configuring Distribution of Routes Between IS-IS Levels
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisDistribute": {
                            "attributes": {
                              "all": "yes",
                              "destination": "l2",
                              "rmap": "",
                              "source": "l1"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <distribute-items>
                  <Distribute-list>
                    <source>l1</source>
                    <all>true</all>
                    <destination>l2</destination>
                    <rmap></rmap>
                  </Distribute-list>
                </distribute-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  distribute level-1 into level-2 all


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisDistribute sys/isis/inst-TAG_1/dom-default/af-v6/distribute-l1
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisDistribute Properties

The following table contains information about the isisDistribute properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
allscalar:Bool
Holds Distribution of all level-n routesSELECTION: true or false
DEFAULT: no
destinationisis:LvlT
(scalar:Enum8)
Holds Destination Domain for Routes Distribute PolicySELECTION:
0 - p2p
1 - l1
2 - l2
DEFAULT: l1
rmapstring:Basic
Holds Route-map name for Distribute PolicyA sequence of characters
sourceisis:LvlT
(scalar:Enum8)
Holds Source Domain for Routes Distribute PolicySELECTION:
0 - p2p
1 - l1
2 - l2
DEFAULT: l1


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Distribution of Routes Between IS-IS Levels

Deleting Distribution of Routes Between IS-IS Levels
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  no distribute level-1 into level-2 all


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Route Map to Constrain Distribution

Configuring a Route Map to Constrain Distribution
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
                      },
                      "children": [
                        {
                          "isisDistribute": {
                            "attributes": {
                              "all": "no",
                              "destination": "l2",
                              "rmap": "SampleString_123",
                              "source": "l1"
}}}]}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
                <distribute-items>
                  <Distribute-list>
                    <source>l1</source>
                    <all>false</all>
                    <destination>l2</destination>
                    <rmap>SampleString_123</rmap>
                  </Distribute-list>
                </distribute-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  distribute level-1 into level-2 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisDistribute sys/isis/inst-TAG_1/dom-default/af-v6/distribute-l1
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisDistribute Properties

The following table contains information about the isisDistribute properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
allscalar:Bool
Holds Distribution of all level-n routesSELECTION: true or false
DEFAULT: no
destinationisis:LvlT
(scalar:Enum8)
Holds Destination Domain for Routes Distribute PolicySELECTION:
0 - p2p
1 - l1
2 - l2
DEFAULT: l1
rmapstring:Basic
Holds Route-map name for Distribute PolicyA sequence of characters
sourceisis:LvlT
(scalar:Enum8)
Holds Source Domain for Routes Distribute PolicySELECTION:
0 - p2p
1 - l1
2 - l2
DEFAULT: l1


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Distribution of Routes Between IS-IS Levels

Deleting Distribution of Routes Between IS-IS Levels
POST http://<mgmt0_IP>/api/mo/sys/isis.json
{
  "isisEntity": {
    "children": [
      {
        "isisInst": {
          "attributes": {
            "name": "TAG_1"
          },
          "children": [
            {
              "isisDom": {
                "attributes": {
                  "name": "default"
                },
                "children": [
                  {
                    "isisDomAf": {
                      "attributes": {
                        "type": "v6"
}}}]}}]}}]}}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>default</name>
            <af-items>
              <DomAf-list>
                <type>v6</type>
              </DomAf-list>
            </af-items>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 address-family ipv6 unicast
  no distribute level-1 into level-2 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-default
isisDomAf sys/isis/inst-TAG_1/dom-default/af-v6
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Authentication Check for Level-1 LSP/CSNP/PSNPs

Configuring Authentication Check for Level-1 LSP/CSNP/PSNPs
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "authCheckLvl1": "yes",
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <authCheckLvl1>true</authCheckLvl1>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  authentication-check level-1


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authCheckLvl1scalar:Bool
Authentication Check for IS-IS DOM on Level-1SELECTION: true or false
DEFAULT: yes
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authCheckLvl1scalar:Bool
Authentication Check for IS-IS DOM on Level-1SELECTION: true or false
DEFAULT: yes
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Authentication Check or Level-1 LSP/CSNP/PSNPs

Deleting Authentication Check or Level-1 LSP/CSNP/PSNPs
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "authCheckLvl1": "no",
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <authCheckLvl1>false</authCheckLvl1>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no authentication-check level-1


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authCheckLvl1scalar:Bool
Authentication Check for IS-IS DOM on Level-1SELECTION: true or false
DEFAULT: yes
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authCheckLvl1scalar:Bool
Authentication Check for IS-IS DOM on Level-1SELECTION: true or false
DEFAULT: yes
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Authentication Check for Level-2 LSP/CSNP/PSNPs

Configuring Authentication Check for Level-2 LSP/CSNP/PSNPs
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "authCheckLvl2": "yes",
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <authCheckLvl2>true</authCheckLvl2>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  authentication-check level-2


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authCheckLvl2scalar:Bool
Authentication Check for IS-IS DOM on Level-2SELECTION: true or false
DEFAULT: yes
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authCheckLvl2scalar:Bool
Authentication Check for IS-IS DOM on Level-2SELECTION: true or false
DEFAULT: yes
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Authentication Check for Level-2 LSP/CSNP/PSNPs

Deleting Authentication Check for Level-2 LSP/CSNP/PSNPs
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "authCheckLvl2": "no",
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <authCheckLvl2>false</authCheckLvl2>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no authentication-check level-2


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authCheckLvl2scalar:Bool
Authentication Check for IS-IS DOM on Level-2SELECTION: true or false
DEFAULT: yes
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authCheckLvl2scalar:Bool
Authentication Check for IS-IS DOM on Level-2SELECTION: true or false
DEFAULT: yes
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring IPv4 BFD on all IS-IS interfaces

Configuring IPv4 BFD on all IS-IS interfaces
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "enableBfd": "yes",
                              "type": "v4"
                            }
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <enableBfd>true</enableBfd>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  bfd


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
enableBfdscalar:Bool
Enabling BFD on all IS-IS domain interfacesSELECTION: true or false
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting IPv4 BFD on all IS-IS interfaces

Deleting IPv4 BFD on all IS-IS interfaces
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "enableBfd": "no",
                              "type": "v4"
                            }
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <enableBfd>false</enableBfd>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no bfd


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
enableBfdscalar:Bool
Enabling BFD on all IS-IS domain interfacesSELECTION: true or false
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring to Suppress Level-2 PDU

Configuring to Suppress Level-2 PDU 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1",
                        "passiveDflt": "l2"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <passiveDflt>l2</passiveDflt>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  passive-interface default level-2


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"
passiveDfltisis:PassiveT
(scalar:Enum8)
Holds IS-IS Domain passive-interface default levelSELECTION:
0 - l1
1 - l2
2 - l12
3 - unknown
DEFAULT: unknown


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"
passiveDfltisis:PassiveT
(scalar:Enum8)
Holds IS-IS Domain passive-interface default levelSELECTION:
0 - l1
1 - l2
2 - l12
3 - unknown
DEFAULT: unknown


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting to Suppress Level-2 PDU

Deleting to Suppress Level-2 PDU 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1",
                        "passiveDflt": "unknown"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <passiveDflt>unknown</passiveDflt>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no passive-interface default level-2


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"
passiveDfltisis:PassiveT
(scalar:Enum8)
Holds IS-IS Domain passive-interface default levelSELECTION:
0 - l1
1 - l2
2 - l12
3 - unknown
DEFAULT: unknown


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"
passiveDfltisis:PassiveT
(scalar:Enum8)
Holds IS-IS Domain passive-interface default levelSELECTION:
0 - l1
1 - l2
2 - l12
3 - unknown
DEFAULT: unknown


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Policy to Constrain Redistribution

Configuring a Policy to Constrain Redistribution
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "type": "v4"
                            },
                            "children": [
                              {
                                "isisInterLeakP": {
                                  "attributes": {
                                    "asn": "none",
                                    "inst": "none",
                                    "proto": "amt",
                                    "rtMap": "SampleString_123"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <interleak-items>
                  <InterLeakP-list>
                    <proto>amt</proto>
                    <inst>none</inst>
                    <asn>none</asn>
                    <rtMap>SampleString_123</rtMap>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  redistribute amt route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisInterLeakP sys/isis/inst-TAG_1/dom-VRF_1/af-v4/interleak-none
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
rtMapstring:Basic
The name of the default route leak policy route map. This route map name is used to control distribution.A sequence of characters


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting a Policy to Constrain Redistribution

Deleting a Policy to Constrain Redistribution
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "type": "v4"
                            },
                            "children": [
                              {
                                "isisInterLeakP": {
                                  "attributes": {
                                    "asn": "none",
                                    "inst": "none",
                                    "proto": "amt",
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <interleak-items>
                  <InterLeakP-list nc:operation="delete">
                    <proto>amt</proto>
                    <inst>none</inst>
                    <asn>none</asn>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no redistribute amt route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisInterLeakP sys/isis/inst-TAG_1/dom-VRF_1/af-v4/interleak-none
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Policy to Constrain Redistribution (BGP)

Configuring a Policy to Constrain Redistribution (BGP)
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "type": "v4"
                            },
                            "children": [
                              {
                                "isisInterLeakP": {
                                  "attributes": {
                                    "asn": "123",
                                    "inst": "none",
                                    "proto": "bgp",
                                    "rtMap": "SampleString_123"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <interleak-items>
                  <InterLeakP-list>
                    <proto>bgp</proto>
                    <inst>none</inst>
                    <asn>123</asn>
                    <rtMap>SampleString_123</rtMap>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  redistribute bgp 123 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisInterLeakP sys/isis/inst-TAG_1/dom-VRF_1/af-v4/interleak-123
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
rtMapstring:Basic
The name of the default route leak policy route map. This route map name is used to control distribution.A sequence of characters


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting a Policy to Constrain Redistribution (BGP)

Deleting a Policy to Constrain Redistribution (BGP)
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "type": "v4"
                            },
                            "children": [
                              {
                                "isisInterLeakP": {
                                  "attributes": {
                                    "asn": "123",
                                    "inst": "none",
                                    "proto": "bgp",
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <interleak-items>
                  <InterLeakP-list nc:operation="delete">
                    <proto>bgp</proto>
                    <inst>none</inst>
                    <asn>123</asn>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no redistribute bgp 123 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisInterLeakP sys/isis/inst-TAG_1/dom-VRF_1/af-v4/interleak-123
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Policy to Constrain Redistribution (Directly Connected)

Configuring a Policy to Constrain Redistribution (Directly Connected)
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "type": "v4"
                            },
                            "children": [
                              {
                                "isisInterLeakP": {
                                  "attributes": {
                                    "asn": "none",
                                    "inst": "none",
                                    "proto": "direct",
                                    "rtMap": "SampleString_123"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <interleak-items>
                  <InterLeakP-list>
                    <proto>direct</proto>
                    <inst>none</inst>
                    <asn>none</asn>
                    <rtMap>SampleString_123</rtMap>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  redistribute direct route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisInterLeakP sys/isis/inst-TAG_1/dom-VRF_1/af-v4/interleak-none
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
rtMapstring:Basic
The name of the default route leak policy route map. This route map name is used to control distribution.A sequence of characters


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting a Policy to Constrain Redistribution (Directly Connected)

Deleting a Policy to Constrain Redistribution (Directly Connected)
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "type": "v4"
                            },
                            "children": [
                              {
                                "isisInterLeakP": {
                                  "attributes": {
                                    "asn": "none",
                                    "inst": "none",
                                    "proto": "direct",
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <interleak-items>
                  <InterLeakP-list nc:operation="delete">
                    <proto>direct</proto>
                    <inst>none</inst>
                    <asn>none</asn>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no redistribute direct route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisInterLeakP sys/isis/inst-TAG_1/dom-VRF_1/af-v4/interleak-none
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Policy to Constrain Redistribution (EIGRP)

Configuring a Policy to Constrain Redistribution (EIGRP)
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "type": "v4"
                            },
                            "children": [
                              {
                                "isisInterLeakP": {
                                  "attributes": {
                                    "asn": "none",
                                    "inst": "SampleString_123",
                                    "proto": "eigrp",
                                    "rtMap": "SampleString_123"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <interleak-items>
                  <InterLeakP-list>
                    <proto>eigrp</proto>
                    <inst>SampleString_123</inst>
                    <asn>none</asn>
                    <rtMap>SampleString_123</rtMap>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  redistribute eigrp SampleString_123 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisInterLeakP sys/isis/inst-TAG_1/dom-VRF_1/af-v4/interleak-none
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
rtMapstring:Basic
The name of the default route leak policy route map. This route map name is used to control distribution.A sequence of characters


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting a Policy to Constrain Redistribution (EIGRP)

Deleting a Policy to Constrain Redistribution (EIGRP)
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "type": "v4"
                            },
                            "children": [
                              {
                                "isisInterLeakP": {
                                  "attributes": {
                                    "asn": "none",
                                    "inst": "SampleString_123",
                                    "proto": "eigrp",
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <interleak-items>
                  <InterLeakP-list nc:operation="delete">
                    <proto>eigrp</proto>
                    <inst>SampleString_123</inst>
                    <asn>none</asn>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no redistribute eigrp SampleString_123 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisInterLeakP sys/isis/inst-TAG_1/dom-VRF_1/af-v4/interleak-none
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Policy to Constrain Redistribution (RIP)

Configuring a Policy to Constrain Redistribution (RIP)
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "type": "v4"
                            },
                            "children": [
                              {
                                "isisInterLeakP": {
                                  "attributes": {
                                    "asn": "none",
                                    "inst": "SampleString_123",
                                    "proto": "rip",
                                    "rtMap": "SampleString_123"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <interleak-items>
                  <InterLeakP-list>
                    <proto>rip</proto>
                    <inst>SampleString_123</inst>
                    <asn>none</asn>
                    <rtMap>SampleString_123</rtMap>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  redistribute rip SampleString_123 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisInterLeakP sys/isis/inst-TAG_1/dom-VRF_1/af-v4/interleak-none
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
rtMapstring:Basic
The name of the default route leak policy route map. This route map name is used to control distribution.A sequence of characters


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting a Policy to Constrain Redistribution (RIP)

Deleting a Policy to Constrain Redistribution (RIP)
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "type": "v4"
                            },
                            "children": [
                              {
                                "isisInterLeakP": {
                                  "attributes": {
                                    "asn": "none",
                                    "inst": "SampleString_123",
                                    "proto": "rip",
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <interleak-items>
                  <InterLeakP-list nc:operation="delete">
                    <proto>rip</proto>
                    <inst>SampleString_123</inst>
                    <asn>none</asn>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no redistribute rip SampleString_123 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisInterLeakP sys/isis/inst-TAG_1/dom-VRF_1/af-v4/interleak-none
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Policy to Constrain Redistribution (Static)

Configuring a Policy to Constrain Redistribution (Static)
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "type": "v4"
                            },
                            "children": [
                              {
                                "isisInterLeakP": {
                                  "attributes": {
                                    "asn": "none",
                                    "inst": "none",
                                    "proto": "static",
                                    "rtMap": "SampleString_123"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <interleak-items>
                  <InterLeakP-list>
                    <proto>static</proto>
                    <inst>none</inst>
                    <asn>none</asn>
                    <rtMap>SampleString_123</rtMap>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  redistribute static route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisInterLeakP sys/isis/inst-TAG_1/dom-VRF_1/af-v4/interleak-none
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
rtMapstring:Basic
The name of the default route leak policy route map. This route map name is used to control distribution.A sequence of characters


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting a Policy to Constrain Redistribution (Static)

Deleting a Policy to Constrain Redistribution (Static)
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "type": "v4"
                            },
                            "children": [
                              {
                                "isisInterLeakP": {
                                  "attributes": {
                                    "asn": "none",
                                    "inst": "none",
                                    "proto": "static",
                                    "status": "deleted"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <interleak-items>
                  <InterLeakP-list nc:operation="delete">
                    <proto>static</proto>
                    <inst>none</inst>
                    <asn>none</asn>
                  </InterLeakP-list>
                </interleak-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no redistribute static route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisInterLeakP sys/isis/inst-TAG_1/dom-VRF_1/af-v4/interleak-none
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisInterLeakP Properties

The following table contains information about the isisInterLeakP properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
asnrtleak:Asn
(string:Basic)
The autonomous system number.A sequence of characters
DEFAULT: none
instrtleak:Inst
(string:Basic)
The inter protocol route leak policy instance.
MAX SIZE: 19
protortleak:Proto
(scalar:Enum8)
The list of protocols to match.SELECTION:
0 - unspecified
1 - static
2 - direct
3 - bgp
4 - isis
5 - ospf
6 - ospfv3
7 - eigrp
8 - host
9 - rip
10 - amt
11 - lisp
12 - hmm
13 - am
DEFAULT: unspecified
statusmo:ModificationStatus
(scalar:Bitmask32)
Modification statusSELECTION:
2 - created
4 - modified
8 - deleted
16 - replaced


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring L1|L2 Router to Set/Unset Attached Bit in its L1 LSP

Configuring L1|L2 Router to Set/Unset Attached  Bit in its L1 LSP
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "ctrl": "adj-check,set-attached-bit",
                              "type": "v4"
                            }
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <ctrl>adj-check,set-attached-bit</ctrl>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  set-attached-bit


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
ctrlisis:DomAfControl
(scalar:Bitmask8)
The address family controls. This determines the address family to run. Note that IPv4 and IPv6 are both supported.SELECTION:
1 - adj-check
2 - set-attached-bit
DEFAULT: adj-check,set-attached-bit
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting L1|L2 Router to Set/Unset Attached Bit in its L1 LSP

Deleting L1|L2 Router to Set/Unset Attached  Bit in its L1 LSP
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "ctrl": "adj-check",
                              "type": "v4"
                            }
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <ctrl>adj-check</ctrl>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no set-attached-bit


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
ctrlisis:DomAfControl
(scalar:Bitmask8)
The address family controls. This determines the address family to run. Note that IPv4 and IPv6 are both supported.SELECTION:
1 - adj-check
2 - set-attached-bit
DEFAULT: adj-check,set-attached-bit
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Authentication Keychain for Level-1 IIHs

Configuring Authentication Keychain for Level-1 IIHs 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "authKeyLvl2": "SampleString_123",
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <authKeyLvl2>SampleString_123</authKeyLvl2>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  authentication key-chain SampleString_123 level-2


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authKeyLvl2isis:AuthKeyN
(string:Basic)
Holds Authentication Key for IS-IS DOM on Level-2A sequence of characters
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authKeyLvl2isis:AuthKeyN
(string:Basic)
Holds Authentication Key for IS-IS DOM on Level-2A sequence of characters
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Authentication Keychain for Level-1 IIHs

Deleting Authentication Keychain for Level-1 IIHs 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "authKeyLvl2": "",
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <authKeyLvl2></authKeyLvl2>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no authentication key-chain SampleString_123 level-2


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authKeyLvl2isis:AuthKeyN
(string:Basic)
Holds Authentication Key for IS-IS DOM on Level-2A sequence of characters
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authKeyLvl2isis:AuthKeyN
(string:Basic)
Holds Authentication Key for IS-IS DOM on Level-2A sequence of characters
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring the Authentication Type as Cleartext Level-1 IIHs

Configuring the Authentication Type as Cleartext Level-1 IIHs
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "authTypeLvl1": "clear",
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <authTypeLvl1>clear</authTypeLvl1>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  authentication-type cleartext level-1


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl1isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-1SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl1isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-1SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting the Authentication Type as Cleartext Level-1 IIHs

Deleting the Authentication Type as Cleartext Level-1 IIHs
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "authTypeLvl1": "unknown",
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <authTypeLvl1>unknown</authTypeLvl1>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no authentication-type cleartext level-1


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl1isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-1SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl1isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-1SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring the Authentication Type as Cleartext Level-2 IIHs

Configuring the Authentication Type as Cleartext Level-2 IIHs 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "authTypeLvl2": "clear",
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <authTypeLvl2>clear</authTypeLvl2>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  authentication-type cleartext level-2


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl2isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-2SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl2isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-2SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting the Authentication Type as Cleartext Level-2 IIHs

Deleting the Authentication Type as Cleartext Level-2 IIHs
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "authTypeLvl2": "unknown",
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <authTypeLvl2>unknown</authTypeLvl2>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no authentication-type cleartext level-2


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl2isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-2SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl2isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-2SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring the Authentication Type as MD5 Level-1

Configuring the Authentication Type as MD5 Level-1 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "authTypeLvl1": "md5",
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <authTypeLvl1>md5</authTypeLvl1>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  authentication-type md5 level-1


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl1isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-1SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl1isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-1SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting the Authentication Type as MD5 Level-1

Deleting the Authentication Type as MD5 Level-1
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "authTypeLvl1": "unknown",
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <authTypeLvl1>unknown</authTypeLvl1>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no authentication-type md5 level-1


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl1isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-1SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl1isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-1SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring the Authentication Type as MD5 Level 2

Configuring the Authentication Type as MD5 Level 2 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "authTypeLvl2": "md5",
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <authTypeLvl2>md5</authTypeLvl2>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  authentication-type md5 level-2


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl2isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-2SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl2isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-2SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting the Authentication Type as MD5 Level 2

Deleting the Authentication Type as MD5 Level 2
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "authTypeLvl2": "unknown",
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <authTypeLvl2>unknown</authTypeLvl2>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no authentication-type md5 level-2


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl2isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-2SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
authTypeLvl2isis:AuthT
(scalar:Enum8)
Holds IS-IS DOM Authentication-Type for Level-2SELECTION:
1 - clear
2 - md5
3 - unknown
DEFAULT: unknown
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Distribution of Routes Between IS-IS Levels

Configuring Distribution of Routes Between IS-IS Levels
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "type": "v4"
                            },
                            "children": [
                              {
                                "isisDistribute": {
                                  "attributes": {
                                    "all": "yes",
                                    "destination": "l2",
                                    "rmap": "",
                                    "source": "l1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <distribute-items>
                  <Distribute-list>
                    <source>l1</source>
                    <all>true</all>
                    <destination>l2</destination>
                    <rmap></rmap>
                  </Distribute-list>
                </distribute-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  distribute level-1 into level-2 all


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisDistribute sys/isis/inst-TAG_1/dom-VRF_1/af-v4/distribute-l1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisDistribute Properties

The following table contains information about the isisDistribute properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
allscalar:Bool
Holds Distribution of all level-n routesSELECTION: true or false
DEFAULT: no
destinationisis:LvlT
(scalar:Enum8)
Holds Destination Domain for Routes Distribute PolicySELECTION:
0 - p2p
1 - l1
2 - l2
DEFAULT: l1
rmapstring:Basic
Holds Route-map name for Distribute PolicyA sequence of characters
sourceisis:LvlT
(scalar:Enum8)
Holds Source Domain for Routes Distribute PolicySELECTION:
0 - p2p
1 - l1
2 - l2
DEFAULT: l1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Distribution of Routes Between IS-IS Levels

Deleting Distribution of Routes Between IS-IS Levels
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no distribute level-1 into level-2 all


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring a Route Map to Constrain Distribution

Configuring a Route Map to Constrain Distribution
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "type": "v4"
                            },
                            "children": [
                              {
                                "isisDistribute": {
                                  "attributes": {
                                    "all": "no",
                                    "destination": "l2",
                                    "rmap": "SampleString_123",
                                    "source": "l1"
                                  }
                                }
                              }
                            ]
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <distribute-items>
                  <Distribute-list>
                    <source>l1</source>
                    <all>false</all>
                    <destination>l2</destination>
                    <rmap>SampleString_123</rmap>
                  </Distribute-list>
                </distribute-items>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  distribute level-1 into level-2 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisDistribute sys/isis/inst-TAG_1/dom-VRF_1/af-v4/distribute-l1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisDistribute Properties

The following table contains information about the isisDistribute properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
allscalar:Bool
Holds Distribution of all level-n routesSELECTION: true or false
DEFAULT: no
destinationisis:LvlT
(scalar:Enum8)
Holds Destination Domain for Routes Distribute PolicySELECTION:
0 - p2p
1 - l1
2 - l2
DEFAULT: l1
rmapstring:Basic
Holds Route-map name for Distribute PolicyA sequence of characters
sourceisis:LvlT
(scalar:Enum8)
Holds Source Domain for Routes Distribute PolicySELECTION:
0 - p2p
1 - l1
2 - l2
DEFAULT: l1


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Distribution of Routes Between IS-IS Levels

Deleting Distribution of Routes Between IS-IS Levels
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      }
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no distribute level-1 into level-2 route-map SampleString_123


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Configuring Maximum Paths per Destination

Configuring Maximum Paths per Destination 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "maxEcmp": "15",
                              "type": "v4"
                            }
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <maxEcmp>15</maxEcmp>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  maximum-paths 15


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
maxEcmpisis:Ecmp
(scalar:UByte)
Holds IS-IS Domain address family Max ECMP value
RANGE: [1 , 64]
DEFAULT: 8
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html

Deleting Maximum Paths per Destination

Deleting Maximum Paths per Destination 
POST http://<mgmt0_IP>/api/mo/sys.json
{
  "topSystem": {
    "children": [
      {
        "isisEntity": {
          "children": [
            {
              "isisInst": {
                "attributes": {
                  "name": "TAG_1"
                },
                "children": [
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "VRF_1"
                      },
                      "children": [
                        {
                          "isisDomAf": {
                            "attributes": {
                              "maxEcmp": "8",
                              "type": "v4"
                            }
                          }
                        }
                      ]
                    }
                  },
                  {
                    "isisDom": {
                      "attributes": {
                        "name": "default"
                      }
                    }
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}
{
    imdata:[]
}
<System>
  <isis-items>
    <inst-items>
      <Inst-list>
        <name>TAG_1</name>
        <dom-items>
          <Dom-list>
            <name>VRF_1</name>
            <af-items>
              <DomAf-list>
                <type>v4</type>
                <maxEcmp>8</maxEcmp>
              </DomAf-list>
            </af-items>
          </Dom-list>
          <Dom-list>
            <name>default</name>
          </Dom-list>
        </dom-items>
      </Inst-list>
    </inst-items>
  </isis-items>
</System>

Note: This example was added in Release 9.3(1).


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload. Click the YANG tab to view the XML payload.

router isis TAG_1
 vrf VRF_1
  no maximum-paths 15


Verifying a DME Configuration

The following table contains the distinguished name (DN) for each managed object (MO) in the DME payload. Issue a GET request using the DN to verify the configuration was posted or to get information about the configured properties of a particular object.

MODN
isisInst sys/isis/inst-TAG_1
isisDom sys/isis/inst-TAG_1/dom-VRF_1
isisDomAf sys/isis/inst-TAG_1/dom-VRF_1/af-v4
isisDom sys/isis/inst-TAG_1/dom-VRF_1
topSystem sys
isisEntity sys/isis


isisInst Properties

The following table contains information about the isisInst properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
null


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


isisDomAf Properties

The following table contains information about the isisDomAf properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
maxEcmpisis:Ecmp
(scalar:UByte)
Holds IS-IS Domain address family Max ECMP value
RANGE: [1 , 64]
DEFAULT: 8
typeisis:AfT
(scalar:Enum8)
TypeSELECTION:
1 - v4
2 - v6
DEFAULT: v4


isisDom Properties

The following table contains information about the isisDom properties in the DME payload. For more information about the properties and MOs, see the NX-API DME Model Reference linked in the Related Documentation section below.

Property NameData TypeDescriptionValues
name
naming:Name256
string:Basic
The IS-IS domain name. This name can be up to 64 characters. Note that you cannot change this name after the object has been saved. RANGE: Min: "1" Max: "128"


Related Documentation

For other CLI options, see the Cisco Nexus 9000 Series NX-OS Command Reference:

http://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-command-reference-list.html

See the NX-API DME Model Reference for detailed information about classes and attributes described in the payload:

https://developer.cisco.com/site/nx-os/docs/nexus-model-reference/

For information about using the payloads, see the Cisco Nexus 9000 Series NX-OS Programmability Guide:

https://www.cisco.com/c/en/us/support/switches/nexus-9000-series-switches/products-programming-reference-guides-list.html