Configuring a BGP Router

This section contains payload and CLI examples to demonstrate many of the BGP configuration options and to show how the REST APIs correspond to the CLI commands.

Creating a BGP Instance

Creating a BGP Instance
POST http://<mgmt0_IP>/api/mo/sys/bgp.json
{
 "bgpEntity": {
   "children": [
     {
       "bgpInst": {
         "attributes": {
           "asn": "100"
}}}]}}
{
    imdata:[]
}
<System>
  <bgp-items>
    <inst-items>
      <asn>100</asn>
    </inst-items>
  </bgp-items>
</System>

This example enables BGP and assigns the AS number to the local BGP speaker. The AS number can be a 16-bit integer or a 32-bit integer in the form of a higher 16-bit decimal number and a lower 16-bit decimal number in xx.xx format.

Issue an HTTP GET request to verify that the configuration was successful. See Verifying a BGP Instance.


CLI Command

The CLI command below is the equivalent of the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.

router bgp 100

Note: The property information for this example was added in Release 9.3(3).


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

MODN
bgpEntity sys/bgp
bgpInst sys/bgp/inst


bgpInst Properties

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

Property NameData TypeDescriptionValues
asnbgp:AsnNum
(string:Basic)
Autonomous system numberA 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

Verifying a BGP Instance

Verifying a BGP Instance
GET http://<IP_address>/api/mo/sys/bgp/inst.json 
{
    "totalCount": "1",
    "imdata": [
        {
            "bgpInst": {
                "attributes": {
                    "activateTs": "2017-12-23T13:54:24.388+00:00",
                    "adminSt": "enabled",
                    "affGrpActv": "0",
                    "asPathDbSz": "0",
                    "asn": "100",
                    "attribDbSz": "116",
                    "childAction": "",
                    "createTs": "2017-12-23T13:53:49.823+00:00",
                    "ctrl": "fastExtFallover",
                    "disPolBatch": "enabled",
                    "disPolBatchv4PfxLst": "",
                    "disPolBatchv6PfxLst": "",
                    "dn": "sys/bgp/inst",
                    "epeActivePeers": "0",
                    "epeConfiguredPeers": "0",
                    "fabricSoo": "unknown:unknown:0:0",
                    "flushRoutes": "disabled",
                    "isolate": "disabled",
                    "lnkStClnt": "inactive",
                    "lnkStSrvr": "inactive",
                    "medDampIntvl": "0",
                    "memAlert": "normal",
                    "modTs": "2017-12-23T13:55:11.144+00:00",
                    "monPolDn": "uni/fabric/monfab-default",
                    "name": "bgp-Inst",
                    "numAsPath": "0",
                    "numRtAttrib": "1",
                    "operErr": "",
                    "persistentOnReload": "true",
                    "snmpTrapSt": "disable",
                    "srgbMaxLbl": "none",
                    "srgbMinLbl": "none",
                    "status": "",
                    "syslogLvl": "err",
                    "uid": "0",
                    "ver": "v4",
                    "waitDoneTs": "2017-12-23T13:59:29.028+00:00"
                }
            }
        }
    ]
}
GET:  http://<IP_Address>/restconf/data/Cisco-NX-OS-device:System/bgp-items/inst-items/asn
<asn>100</asn>

Note: The property information for this example was added in Release 9.3(3).


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

MODN
bgpInst sys/bgp/inst


bgpInst Properties

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

Property NameData TypeDescriptionValues
activateTsscalar:Date
Activation timestampDATE FORMAT: %Y-%m-%dT%H:%M:%S.%f%z
adminStnw:AdminSt
(scalar:Enum8)
The administrative state of the object or policy.SELECTION:
1 - enabled
2 - disabled
DEFAULT: enabled
affGrpActvbgp:AffGrpActv
(scalar:Uint16)
Activate the affinity group
RANGE: [0 , 65535]
asPathDbSzbgp:AsPathDbSz
(scalar:Uint32)
Current size of AS path databaseRANGE: [0, 4294967295]
asnbgp:AsnNum
(string:Basic)
Autonomous system numberA sequence of characters
attribDbSzbgp:AttribDbSz
(scalar:Uint32)
Current size of attribute databaseRANGE: [0, 4294967295]
childAction
mo:ModificationChildAction
scalar:Bitmask32
Delete or ignore. For internal use only.SELECTION:
  • 16384u - deleteAll
  • 4096u - ignore
  • 8192u - deleteNonPresent
  • DEFAULT: 0
  • createTsscalar:Date
    Creation timestampDATE FORMAT: %Y-%m-%dT%H:%M:%S.%f%z
    ctrlnw:InstCtrl
    (scalar:Bitmask64)
    The control state.SELECTION:
    1 - stateful-ha
    DEFAULT: fastExtFallover
    disPolBatchbgp:AdminSt
    (scalar:Enum8)
    Disable Batching Evaluation To All PeersSELECTION:
    1 - enabled
    2 - disabled
    DEFAULT: disabled
    disPolBatchv4PfxLststring:Basic
    Disable Batching Evaluation Of IPv4 Prefix Advertisements To All PeersA sequence of characters
    disPolBatchv6PfxLststring:Basic
    Disable Batching Evaluation Of IPv6 Prefix Advertisements To All PeersA sequence of characters
    dn
    reference:BinRef
    A tag or metadata is a non-hierarchical keyword or term assigned to the fabric module.
    epeActivePeersbgp:NumPeers
    (scalar:Uint32)
    EPE Active PeersRANGE: [0, 4294967295]
    epeConfiguredPeersbgp:NumPeers
    (scalar:Uint32)
    EPE Configured PeersRANGE: [0, 4294967295]
    fabricSoobase:Community
    Fabric Site of Origin extcommunity
    flushRoutesbgp:AdminSt
    (scalar:Enum8)
    Flush routes in RIB upon controlled restartSELECTION:
    1 - enabled
    2 - disabled
    DEFAULT: disabled
    isolatebgp:AdminSt
    (scalar:Enum8)
    Isolate router from BGP perspectiveSELECTION:
    1 - enabled
    2 - disabled
    DEFAULT: disabled
    lnkStClntbgp:LsAdminSt
    (scalar:Enum8)
    EPE Link-State ServerSELECTION:
    0 - inactive
    1 - active
    DEFAULT: inactive
    lnkStSrvrbgp:LsAdminSt
    (scalar:Enum8)
    EPE Link-State ServerSELECTION:
    0 - inactive
    1 - active
    DEFAULT: inactive
    medDampIntvlbgp:MedIntvl
    (scalar:Uint32)
    Setting med dampening interval
    RANGE: [0 , 4294967295]
    memAlertnw:MemAlertLevel
    (scalar:Enum8)
    Memory Alert LevelSELECTION:
    0 - normal
    1 - minor
    2 - major
    3 - critical
    DEFAULT: normal
    modTsmo:TStamp
    (scalar:Date)
    The time when this object was last modified.SELECTION:
    0 - never
    DEFAULT: never
    monPolDn
    reference:BinRef
    The monitoring policy attached to this observable object.
    namenaming:Name256
    (string:Basic)
    The name of the object.
    MAX SIZE: 128
    DEFAULT: bgp
    numAsPathcap:Quant
    (scalar:Uint16)
    The number of autonomous system (AS) path entries learned.
    RANGE: [0 , 0xFFFF]
    DEFAULT: 0
    numRtAttribcap:Quant
    (scalar:Uint16)
    The number of route attribute entries learned.
    RANGE: [0 , 0xFFFF]
    DEFAULT: 0
    operErrnw:OperErrQual
    (scalar:Bitmask64)
    Operational Errors QualifierSELECTION:
    1 - init-err
    2 - mem-err
    4 - ipc-err
    8 - int-err
    16 - sock-err
    32 - proto-err
    persistentOnReload
    mo:Persistent
    scalar:Enum8
    NO COMMENTSSELECTION:
  • 0 - false
  • 1 - true
  • DEFAULT: true(1)
  • snmpTrapSt
    snmp:SnmpTrapSt
    scalar:Enum8
    Administrative port snmp trap stateSELECTION:
  • 1 - enable
  • 2 - disable
  • DEFAULT: disable(2)
  • srgbMaxLblbgp:SRGBRange
    (scalar:Uint32)
    Segment Routing Global Block Max Label. (Value should be in the range 16000-471804 when feature segment-routing is enabled.
    RANGE: [0 , 471804]
    DEFAULT: none
    srgbMinLblbgp:SRGBRange
    (scalar:Uint32)
    Segment Routing Global Block Min Label. (Value should be in the range 16000-471804 when feature segment-routing is enabled.
    RANGE: [0 , 471804]
    DEFAULT: none
    statusmo:ModificationStatus
    (scalar:Bitmask32)
    The upgrade status. This property is for internal use only.SELECTION:
    2 - created
    4 - modified
    8 - deleted
    16 - replaced
    syslogLvl
    syslog:Level
    scalar:Enum8
    syslog levelSELECTION:
  • 0 - emerg
  • 1 - alert
  • 2 - crit
  • 3 - err
  • 4 - warn
  • 5 - notif
  • 6 - inform
  • 7 - debug
  • DEFAULT: err(3)
  • uid
    scalar:Uint16
    A unique identifier for this object.
    ver
    bgp:Ver
    scalar:Enum8
    BGP version.SELECTION:
  • 4 - v4
  • DEFAULT: v4(4)
  • waitDoneTsscalar:Date
    The timestamp when the BGP protocol came out of wait mode.DATE FORMAT: %Y-%m-%dT%H:%M:%S.%f%z


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 BGP

    Deleting a BGP
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp.json
    
    {
    "bgpEntity": {
      "children": [
        {
          "bgpInst": {
            "attributes": {
              "status": "deleted"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items xc:operation="delete">
        </inst-items>
      </bgp-items>
    </System>
    

    This Example demonstrates how to delete a BGP instance.


    CLI Commands

    The CLI command below is the equivalent of the payload example displayed in the pane on the right. Click the DME tab in the top-left corner of the right pane to view the JSON payload or the YANG tab to view the XML payload.

    no router bgp 100

    Note: The property information for this example was added in Release 9.3(3).


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

    MODN
    bgpEntity sys/bgp
    bgpInst sys/bgp/inst


    bgpInst Properties

    The following table contains information about the bgpInst properties in the DME payload. For 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)
    The upgrade status. This property is for internal use only.SELECTION:
    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 the Router Id

    Configuring the Router Id 
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp/inst.json
    
    {
     "bgpInst": {
       "attributes": {
         "asn": "100"
       },
       "children": [
         {
           "bgpDom": {
             "attributes": {
               "name": "default",
               "rtrId": "1.1.1.1"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <dom-items>
            <Dom-list>
              <name>default</name>
              <rtrId>1.1.1.1</rtrId>
            </Dom-list>
          </dom-items>
        </inst-items>
      </bgp-items>
    </System>
    

    This example configures the BGP router ID. This IP address identifies this BGP speaker.


    CLI Commands

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

    router bgp 100
     router-id 1.1.1.1

    Note: The property information for this example was added in Release 9.3(3).


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

    MODN
    bgpInst sys/bgp/inst
    bgpDom sys/bgp/inst/dom-{name}


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpDom Properties

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

    Property NameData TypeDescriptionValues
    namenaming:Name256
    (string:Basic)
    The name of the object.
    MAX SIZE: 63
    rtrIdip:RtrId
    (address:IPv4)
    The BGP router ID.Value must match ipv4 format


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Cluster Id

    Configuring the Cluster Id     
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp/inst.json
    
    {
     "bgpInst": {
       "attributes": {
         "asn": "100"
       },
       "children": [
         {
           "bgpDom": {
             "attributes": {
               "clusterId": "110",
               "name": "default"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <dom-items>
            <Dom-list>
              <name>default</name>
              <clusterId>110</clusterId>
            </Dom-list>
          </dom-items>
        </inst-items>
      </bgp-items>
    </System>
    

    This example configures the local router as one of the route reflectors that serve the cluster. You specify a cluster ID to identify the cluster. This command triggers an automatic soft clear or refresh of BGP neighbor sessions.


    CLI Commands

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

    router bgp 100
     cluster-id 110

    Note: The property information for this example was added in Release 9.3(3).


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

    MODN
    bgpInst sys/bgp/inst
    bgpDom sys/bgp/inst/dom-{name}


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpDom Properties

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

    Property NameData TypeDescriptionValues
    clusterIdbgp:ClusterId
    (string:Basic)
    The BGP route reflector ID (Cluster ID) that identifies the cluster of the route reflector domain.A sequence of characters
    namenaming:Name256
    (string:Basic)
    The name of the object.
    MAX SIZE: 63


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Graceful Restart Helper

    Configuring the Graceful Restart Helper
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp/inst.json
    
    {
       "bgpInst": {
         "attributes": {
           "asn": "100"
         },
         "children": [
           {
             "bgpDom": {
               "attributes": {
                 "name": "default"
               },
               "children": [
                 {
                   "bgpGr": {
                     "attributes": {
                       "ctrl": "complete,helper"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <dom-items>
            <Dom-list>
              <name>default</name>
              <gr-items>
                <ctrl>complete,helper</ctrl>
              </gr-items>
            </Dom-list>
          </dom-items>
        </inst-items>
      </bgp-items>
    </System>
    

    This example enables the graceful restart helper functionality. Use this command if you have disabled graceful restart but you still want to enable graceful restart helper functionality. This command triggers an automatic notification and session reset for the BGP neighbor sessions.


    CLI Commands

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

    router bgp 100
     graceful-restart-helper

    Note: The property information for this example was added in Release 9.3(3).


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

    MODN
    bgpInst sys/bgp/inst
    bgpDom sys/bgp/inst/dom-{name}
    bgpGr sys/bgp/inst/dom-{name}/gr


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpDom Properties

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

    Property NameData TypeDescriptionValues
    namenaming:Name256
    (string:Basic)
    The name of the object.
    MAX SIZE: 63


    bgpGr Properties

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

    Property NameData TypeDescriptionValues
    ctrlbgp:GrCtrl
    (scalar:Bitmask8)
    Graceful restart controlsSELECTION:
    1 - helper
    2 - complete
    DEFAULT: complete


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Graceful Restart Time

    Configuring the Graceful Restart Time  
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp/inst.json
    
    {
       "bgpInst": {
         "attributes": {
           "asn": "100"
         },
         "children": [
           {
             "bgpDom": {
               "attributes": {
                 "name": "default"
               },
               "children": [
                 {
                   "bgpGr": {
                     "attributes": {
                       "restartIntvl": "200"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <dom-items>
            <Dom-list>
              <name>default</name>
              <gr-items>
                <restartIntvl>200</restartIntvl>
              </gr-items>
            </Dom-list>
          </dom-items>
        </inst-items>
      </bgp-items>
    </System>
    

    This example configures the maximum time for a restart sent to the BGP peer.


    CLI Commands

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

    router bgp 100
     graceful-restart restart-time 200

    Note: The property information for this example was added in Release 9.3(3).


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

    MODN
    bgpInst sys/bgp/inst
    bgpDom sys/bgp/inst/dom-{name}
    bgpGr sys/bgp/inst/dom-{name}/gr


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpDom Properties

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

    Property NameData TypeDescriptionValues
    namenaming:Name256
    (string:Basic)
    The name of the object.
    MAX SIZE: 63


    bgpGr Properties

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

    Property NameData TypeDescriptionValues
    restartIntvlbgp:GrIntvl
    (scalar:Uint16)
    The graceful restart interval.
    RANGE: [1 , 3600]
    DEFAULT: 120


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Graceful Restart Stale-Path Time

    Configuring the Graceful Restart Stale-path Time  
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp/inst.json
    
    {
       "bgpInst": {
         "attributes": {
           "asn": "100"
         },
         "children": [
           {
             "bgpDom": {
               "attributes": {
                 "name": "default"
               },
               "children": [
                 {
                   "bgpGr": {
                     "attributes": {
                       "staleIntvl": "400"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <dom-items>
            <Dom-list>
              <name>default</name>
              <gr-items>
                <staleIntvl>400</staleIntvl>
              </gr-items>
            </Dom-list>
          </dom-items>
        </inst-items>
      </bgp-items>
    </System>
    

    This example configures the maximum time that BGP keeps the stale routes from the restarting BGP peer.


    CLI Commands

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

    router bgp 100
     graceful-restart stalepath-time 400

    Note: The property information for this example was added in Release 9.3(3).


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

    MODN
    bgpInst sys/bgp/inst
    bgpDom sys/bgp/inst/dom-{name}
    bgpGr sys/bgp/inst/dom-{name}/gr


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpDom Properties

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

    Property NameData TypeDescriptionValues
    namenaming:Name256
    (string:Basic)
    The name of the object.
    MAX SIZE: 63


    bgpGr Properties

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

    Property NameData TypeDescriptionValues
    staleIntvlbgp:GrStaleIntvl
    (scalar:Uint16)
    The stale interval for routes advertised by the BGP peer.
    RANGE: [1 , 3600]
    DEFAULT: 300


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Confederation Identifier

    Configuring the Confederation Identifier     
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp/inst.json
    
    {
     "bgpInst": {
       "attributes": {
         "asn": "100"
       },
       "children": [
         {
           "bgpDom": {
             "attributes": {
               "name": "default"
             },
             "children": [
               {
                 "bgpConfederation": {
                   "attributes": {
                     "asn": "102"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <dom-items>
            <Dom-list>
              <name>default</name>
              <confed-items>
                <asn>102</asn>
              </confed-items>
            </Dom-list>
          </dom-items>
        </inst-items>
      </bgp-items>
    </System>
    

    This example configures a confederation identifier for an AS confederation. This command triggers an automatic notification and session reset for the BGP neighbor sessions.


    CLI Commands

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

    router bgp 100
     confederation identifier 102

    Note: The property information for this example was added in Release 9.3(3).


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

    MODN
    bgpInst sys/bgp/inst
    bgpDom sys/bgp/inst/dom-{name}
    bgpConfederation sys/bgp/inst/dom-{name}/confed


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpDom Properties

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

    Property NameData TypeDescriptionValues
    namenaming:Name256
    (string:Basic)
    The name of the object.
    MAX SIZE: 63


    bgpConfederation Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous System Number, takes value from (1-4294967295 \ 1-65535[.(0-65535)])


    Related Documentation

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

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

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

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

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

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

    Relaxing AS-Path Restrictions when Choosing Multipath

    Relaxing AS-Path Restrictions when Choosing Multipath  
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp/inst.json
    
    {
     "bgpInst": {
       "attributes": {
         "asn": "100"
       },
       "children": [
         {
           "bgpDom": {
             "attributes": {
               "name": "default"
             },
             "children": [
               {
                 "bgpPathCtrl": {
                   "attributes": {
                     "asPathMultipathRelax": "enabled"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <dom-items>
            <Dom-list>
              <name>default</name>
              <pathctrl-items>
                <asPathMultipathRelax>enabled</asPathMultipathRelax>
              </pathctrl-items>
            </Dom-list>
          </dom-items>
        </inst-items>
      </bgp-items>
    </System>
    

    Allows load sharing across the providers with different (but equal-length) AS paths. Without the as-path multipath-relax option, the AS paths must be identical for load sharing.


    CLI Commands

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

    router bgp 100
     bestpath as-path multipath-relax

    Note: The property information for this example was added in Release 9.3(3).


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

    MODN
    bgpInst sys/bgp/inst
    bgpDom sys/bgp/inst/dom-{name}
    bgpPathCtrl sys/bgp/inst/dom-{name}/pathctrl


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpDom Properties

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

    Property NameData TypeDescriptionValues
    namenaming:Name256
    (string:Basic)
    The name of the object.
    MAX SIZE: 63


    bgpPathCtrl Properties

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

    Property NameData TypeDescriptionValues
    asPathMultipathRelaxbgp:AdminSt
    (scalar:Enum8)
    Relax AS-Path restriction when choosing multipathsSELECTION:
    1 - enabled
    2 - disabled
    DEFAULT: disabled


    Related Documentation

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

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

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

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

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

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

    Comparing the Router Id for Identical EBGP Paths

    Comparing the Router Id for Identical EBGP Paths         
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp/inst.json
    
    {
     "bgpInst": {
       "attributes": {
         "asn": "100"
       },
       "children": [
         {
           "bgpDom": {
             "attributes": {
               "name": "default"
             },
             "children": [
               {
                 "bgpPathCtrl": {
                   "attributes": {
                     "compRtrId": "enabled"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <dom-items>
            <Dom-list>
              <name>default</name>
              <pathctrl-items>
                <compRtrId>enabled</compRtrId>
              </pathctrl-items>
            </Dom-list>
          </dom-items>
        </inst-items>
      </bgp-items>
    </System>
    

    Compares the router IDs for identical eBGP paths.


    CLI Commands

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

    router bgp 100
     bestpath compare-routerid

    Note: The property information for this example was added in Release 9.3(3).


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

    MODN
    bgpInst sys/bgp/inst
    bgpDom sys/bgp/inst/dom-{name}
    bgpPathCtrl sys/bgp/inst/dom-{name}/pathctrl


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpDom Properties

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

    Property NameData TypeDescriptionValues
    namenaming:Name256
    (string:Basic)
    The name of the object.
    MAX SIZE: 63


    bgpPathCtrl Properties

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

    Property NameData TypeDescriptionValues
    compRtrIdbgp:AdminSt
    (scalar:Enum8)
    Compare Router IdSELECTION:
    1 - enabled
    2 - disabled
    DEFAULT: disabled


    Related Documentation

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

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

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

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

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

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

    Compare MED on Paths from a Different AS

    Compare MED on Paths from a Different AS        
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp/inst.json
    
    {
     "bgpInst": {
       "attributes": {
         "asn": "100"
       },
       "children": [
         {
           "bgpDom": {
             "attributes": {
               "name": "default"
             },
             "children": [
               {
                 "bgpPathCtrl": {
                   "attributes": {
                     "alwaysCompMed": "enabled"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <dom-items>
            <Dom-list>
              <name>default</name>
              <pathctrl-items>
                <alwaysCompMed>enabled</alwaysCompMed>
              </pathctrl-items>
            </Dom-list>
          </dom-items>
        </inst-items>
      </bgp-items>
    </System>
    

    Compares MED on paths from different autonomous systems.


    CLI Commands

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

    router bgp 100
     bestpath always-compare-med

    Note: The property information for this example was added in Release 9.3(3).


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

    MODN
    bgpInst sys/bgp/inst
    bgpDom sys/bgp/inst/dom-{name}
    bgpPathCtrl sys/bgp/inst/dom-{name}/pathctrl


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpDom Properties

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

    Property NameData TypeDescriptionValues
    namenaming:Name256
    (string:Basic)
    The name of the object.
    MAX SIZE: 63


    bgpPathCtrl Properties

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

    Property NameData TypeDescriptionValues
    alwaysCompMedbgp:AdminSt
    (scalar:Enum8)
    Compare MED on paths from different ASSELECTION:
    1 - enabled
    2 - disabled
    DEFAULT: disabled


    Related Documentation

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

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

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

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

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

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

    Configuring the Default Route for Nexthop Address Resolution

    Configuring the Default Route for Nexthop Address Resolution
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp.json
    
    {
      "bgpEntity": {
        "children": [
          {
            "bgpInst": {
              "attributes": {
                "asn": "100",
                "nhSupprDefRes": "enabled"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <nhSupprDefRes>enabled</nhSupprDefRes>
        </inst-items>
      </bgp-items>
    </System>
    

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


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME 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 bgp 100
      nexthop suppress-default-resolution


    Verifying a DME Configuration

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

    MODN
    bgpEntity sys/bgp
    bgpInst sys/bgp/inst


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters
    nhSupprDefResscalar:Enum8nexthop suppress-default-resolutionAenabled or disabled
    DEFAULT: disabled


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Default Route for Nexthop Address Resolution

    Deleting the Default Route for Nexthop Address Resolution
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp.json
    
    {
      "bgpEntity": {
        "children": [
          {
            "bgpInst": {
              "attributes": {
                "asn": "100",
                "nhSupprDefRes": "disabled"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <nhSupprDefRes>disabled</nhSupprDefRes>
        </inst-items>
      </bgp-items>
    </System>
    

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


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME 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 bgp 100
      no nexthop suppress-default-resolution


    Verifying a DME Configuration

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

    MODN
    bgpEntity sys/bgp
    bgpInst sys/bgp/inst


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters
    nhSupprDefResscalar:Enum8nexthop suppress-default-resolutionAenabled or disabled
    DEFAULT: disabled


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Socket History Buffer Size

    Configuring the Socket History Buffer Size 
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp.json
    
    {
      "bgpEntity": {
        "children": [
          {
            "bgpInst": {
              "attributes": {
                "asn": "100"
              },
              "children": [
                {
                  "bgpEvtHist": {
                    "attributes": {
                      "size": "81000",
                      "type": "socket"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <evthist-items>
            <EvtHist-list>
              <type>socket</type>
              <size>81000</size>
            </EvtHist-list>
          </evthist-items>
        </inst-items>
      </bgp-items>
    </System>
    

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


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME 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 bgp 100
     event-history socket size 81000


    Verifying a DME Configuration

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

    MODN
    bgpEntity sys/bgp
    bgpInst sys/bgp/inst
    bgpEvtHist sys/bgp/inst/evthist-socket


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpEvtHist Properties

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

    Property NameData TypeDescriptionValues
    sizebgp:Size
    (scalar:Uint32)
    Configure event-history with buffer size
    RANGE: [0 , 4]
    DEFAULT: default
    typebgp:EhType
    (scalar:Enum8)
    Configure event-history {cli \ events \


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Socket History Buffer Size

    Deleting the Socket History Buffer Size 
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp.json
    
    {
      "bgpEntity": {
        "children": [
          {
            "bgpInst": {
              "attributes": {
                "asn": "100"
              },
              "children": [
                {
                  "bgpEvtHist": {
                    "attributes": {
                      "size": "disable",
                      "type": "socket"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <evthist-items>
            <EvtHist-list>
              <type>socket</type>
              <size>1</size>
            </EvtHist-list>
          </evthist-items>
        </inst-items>
      </bgp-items>
    </System>
    

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


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME 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 bgp 100
     no event-history socket size 81000


    Verifying a DME Configuration

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

    MODN
    bgpEntity sys/bgp
    bgpInst sys/bgp/inst
    bgpEvtHist sys/bgp/inst/evthist-socket


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpEvtHist Properties

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

    Property NameData TypeDescriptionValues
    sizebgp:Size
    (scalar:Uint32)
    Configure event-history with buffer size
    RANGE: [0 , 4]
    DEFAULT: default
    typebgp:EhType
    (scalar:Enum8)
    Configure event-history {cli \ events \


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Socket History Buffer Size as Disable

    Configuring the Socket History Buffer Size as Disable
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp.json
    
    {
      "bgpEntity": {
        "children": [
          {
            "bgpInst": {
              "attributes": {
                "asn": "100"
              },
              "children": [
                {
                  "bgpEvtHist": {
                    "attributes": {
                      "size": "disable",
                      "type": "socket"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <evthist-items>
            <EvtHist-list>
              <type>socket</type>
              <size>1</size>
            </EvtHist-list>
          </evthist-items>
        </inst-items>
      </bgp-items>
    </System>
    

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


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME 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 bgp 100
     event-history socket size disable


    Verifying a DME Configuration

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

    MODN
    bgpEntity sys/bgp
    bgpInst sys/bgp/inst
    bgpEvtHist sys/bgp/inst/evthist-socket


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpEvtHist Properties

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

    Property NameData TypeDescriptionValues
    sizebgp:Size
    (scalar:Uint32)
    Configure event-history with buffer size
    RANGE: [0 , 4]
    DEFAULT: default
    typebgp:EhType
    (scalar:Enum8)
    Configure event-history {cli \ events \


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Socket History Buffer Size as Disable

    Deleting the Socket History Buffer Size as Disable
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp.json
    
    {
      "bgpEntity": {
        "children": [
          {
            "bgpInst": {
              "attributes": {
                "asn": "100"
              },
              "children": [
                {
                  "bgpEvtHist": {
                    "attributes": {
                      "size": "disable",
                      "type": "socket"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <evthist-items>
            <EvtHist-list>
              <type>socket</type>
              <size>1</size>
            </EvtHist-list>
          </evthist-items>
        </inst-items>
      </bgp-items>
    </System>
    

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


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME 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 bgp 100
     no event-history socket size disable


    Verifying a DME Configuration

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

    MODN
    bgpEntity sys/bgp
    bgpInst sys/bgp/inst
    bgpEvtHist sys/bgp/inst/evthist-socket


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpEvtHist Properties

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

    Property NameData TypeDescriptionValues
    sizebgp:Size
    (scalar:Uint32)
    Configure event-history with buffer size
    RANGE: [0 , 4]
    DEFAULT: default
    typebgp:EhType
    (scalar:Enum8)
    Configure event-history {cli \ events \


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Socket History Buffer Size as Small

    Configuring the Socket History Buffer Size as Small 
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp.json
    
    {
      "bgpEntity": {
        "children": [
          {
            "bgpInst": {
              "attributes": {
                "asn": "100"
              },
              "children": [
                {
                  "bgpEvtHist": {
                    "attributes": {
                      "size": "small",
                      "type": "socket"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <evthist-items>
            <EvtHist-list>
              <type>socket</type>
              <size>2</size>
            </EvtHist-list>
          </evthist-items>
        </inst-items>
      </bgp-items>
    </System>
    

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


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME 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 bgp 100
     event-history socket 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
    bgpEntity sys/bgp
    bgpInst sys/bgp/inst
    bgpEvtHist sys/bgp/inst/evthist-socket


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpEvtHist Properties

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

    Property NameData TypeDescriptionValues
    sizebgp:Size
    (scalar:Uint32)
    Configure event-history with buffer size
    RANGE: [0 , 4]
    DEFAULT: default
    typebgp:EhType
    (scalar:Enum8)
    Configure event-history {cli \ events \


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Socket History Buffer Size as Small

    Deleting the Socket History Buffer Size as Small 
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp.json
    
    {
      "bgpEntity": {
        "children": [
          {
            "bgpInst": {
              "attributes": {
                "asn": "100"
              },
              "children": [
                {
                  "bgpEvtHist": {
                    "attributes": {
                      "size": "disable",
                      "type": "socket"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <evthist-items>
            <EvtHist-list>
              <type>socket</type>
              <size>1</size>
            </EvtHist-list>
          </evthist-items>
        </inst-items>
      </bgp-items>
    </System>
    

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


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME 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 bgp 100
     no event-history socket 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
    bgpEntity sys/bgp
    bgpInst sys/bgp/inst
    bgpEvtHist sys/bgp/inst/evthist-socket


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpEvtHist Properties

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

    Property NameData TypeDescriptionValues
    sizebgp:Size
    (scalar:Uint32)
    Configure event-history with buffer size
    RANGE: [0 , 4]
    DEFAULT: default
    typebgp:EhType
    (scalar:Enum8)
    Configure event-history {cli \ events \


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Socket History Buffer Size as Medium

    Configuring the Socket History Buffer Size as Medium 
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp.json
    
    {
      "bgpEntity": {
        "children": [
          {
            "bgpInst": {
              "attributes": {
                "asn": "100"
              },
              "children": [
                {
                  "bgpEvtHist": {
                    "attributes": {
                      "size": "medium",
                      "type": "socket"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <evthist-items>
            <EvtHist-list>
              <type>socket</type>
              <size>3</size>
            </EvtHist-list>
          </evthist-items>
        </inst-items>
      </bgp-items>
    </System>
    

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


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME 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 bgp 100
     event-history socket 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
    bgpEntity sys/bgp
    bgpInst sys/bgp/inst
    bgpEvtHist sys/bgp/inst/evthist-socket


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpEvtHist Properties

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

    Property NameData TypeDescriptionValues
    sizebgp:Size
    (scalar:Uint32)
    Configure event-history with buffer size
    RANGE: [0 , 4]
    DEFAULT: default
    typebgp:EhType
    (scalar:Enum8)
    Configure event-history {cli \ events \


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Socket History Buffer Size as Medium

    Deleting the Socket History Buffer Size as Medium 
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp.json
    
    {
      "bgpEntity": {
        "children": [
          {
            "bgpInst": {
              "attributes": {
                "asn": "100"
              },
              "children": [
                {
                  "bgpEvtHist": {
                    "attributes": {
                      "size": "disable",
                      "type": "socket"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <evthist-items>
            <EvtHist-list>
              <type>socket</type>
              <size>1</size>
            </EvtHist-list>
          </evthist-items>
        </inst-items>
      </bgp-items>
    </System>
    

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


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME 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 bgp 100
     no event-history socket 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
    bgpEntity sys/bgp
    bgpInst sys/bgp/inst
    bgpEvtHist sys/bgp/inst/evthist-socket


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpEvtHist Properties

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

    Property NameData TypeDescriptionValues
    sizebgp:Size
    (scalar:Uint32)
    Configure event-history with buffer size
    RANGE: [0 , 4]
    DEFAULT: default
    typebgp:EhType
    (scalar:Enum8)
    Configure event-history {cli \ events \


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Socket History Buffer Size as Large

    Configuring the Socket History Buffer Size as Large 
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp.json
    
    {
      "bgpEntity": {
        "children": [
          {
            "bgpInst": {
              "attributes": {
                "asn": "100"
              },
              "children": [
                {
                  "bgpEvtHist": {
                    "attributes": {
                      "size": "large",
                      "type": "socket"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <evthist-items>
            <EvtHist-list>
              <type>socket</type>
              <size>4</size>
            </EvtHist-list>
          </evthist-items>
        </inst-items>
      </bgp-items>
    </System>
    

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


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME 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 bgp 100
     event-history socket 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
    bgpEntity sys/bgp
    bgpInst sys/bgp/inst
    bgpEvtHist sys/bgp/inst/evthist-socket


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpEvtHist Properties

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

    Property NameData TypeDescriptionValues
    sizebgp:Size
    (scalar:Uint32)
    Configure event-history with buffer size
    RANGE: [0 , 4]
    DEFAULT: default
    typebgp:EhType
    (scalar:Enum8)
    Configure event-history {cli \ events \


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 Socket History Buffer Size as Large

    Deleting the Socket History Buffer Size as Large 
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp.json
    
    {
      "bgpEntity": {
        "children": [
          {
            "bgpInst": {
              "attributes": {
                "asn": "100"
              },
              "children": [
                {
                  "bgpEvtHist": {
                    "attributes": {
                      "size": "disable",
                      "type": "socket"
    }}}]}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <evthist-items>
            <EvtHist-list>
              <type>socket</type>
              <size>1</size>
            </EvtHist-list>
          </evthist-items>
        </inst-items>
      </bgp-items>
    </System>
    

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


    CLI Commands

    The CLI commands are equivalent to the payload examples displayed in the pane on the right. Click the DME 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 bgp 100
     no event-history socket 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
    bgpEntity sys/bgp
    bgpInst sys/bgp/inst
    bgpEvtHist sys/bgp/inst/evthist-socket


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters


    bgpEvtHist Properties

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

    Property NameData TypeDescriptionValues
    sizebgp:Size
    (scalar:Uint32)
    Configure event-history with buffer size
    RANGE: [0 , 4]
    DEFAULT: default
    typebgp:EhType
    (scalar:Enum8)
    Configure event-history {cli \ events \


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 BGP Enhanced-Error Handling

    Configuring BGP Enhanced-Error Handling
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp.json
    
    {
      "bgpEntity": {
        "children": [
          {
            "bgpInst": {
              "attributes": {
                "asn": "100",
                "enhancedErr": "yes"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <enhancedErr>true</enhancedErr>
        </inst-items>
      </bgp-items>
    </System>
    

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


    CLI Commands

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

    router bgp 100
      enhanced-error


    Verifying a DME Configuration

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

    MODN
    bgpEntity sys/bgp
    bgpInst sys/bgp/inst


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters
    enhancedErrscalar:Bool
    Enable BGP Enhanced Error Handling to prevent inadvertent session resets for minor errors. See RFC7606 for more detailsSELECTION: true or false
    DEFAULT: true


    Related Documentation

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

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

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

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

    For information about using the payloads, see the Cisco Nexus 9000 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 BGP Enhanced-Error Handling

    Deleting BGP Enhanced-Error Handling
    
    POST http://<mgmt0_IP>/api/mo/sys/bgp.json
    
    {
      "bgpEntity": {
        "children": [
          {
            "bgpInst": {
              "attributes": {
                "asn": "100",
                "enhancedErr": "no"
    }}}]}}
    
    {
        imdata:[]
    }
    
    <System>
      <bgp-items>
        <inst-items>
          <asn>100</asn>
          <enhancedErr>false</enhancedErr>
        </inst-items>
      </bgp-items>
    </System>
    

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


    CLI Commands

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

    router bgp 100
      no enhanced-error


    Verifying a DME Configuration

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

    MODN
    bgpEntity sys/bgp
    bgpInst sys/bgp/inst


    bgpInst Properties

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

    Property NameData TypeDescriptionValues
    asnbgp:AsnNum
    (string:Basic)
    Autonomous system numberA sequence of characters
    enhancedErrscalar:Bool
    Enable BGP Enhanced Error Handling to prevent inadvertent session resets for minor errors. See RFC7606 for more detailsSELECTION: true or false
    DEFAULT: true


    Related Documentation

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

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

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

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

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

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