The VIP address screen will only appears on DNAC1 install setup.  DNAC1 uses "START A CLUSTER" and DNAC2 & DNAC3 uses "JOIN A CLUSTER".   Take a look at my worksheet.  It shows a picture of the NICs and the MLOMs.  The MLOMs are the 10gb links.   Left = 10Gbit port [enp10s0] - Intra Cluster Link (recommended) Right = 10Gbit port [enp9s0] - Enterprise Network Left = 1Gbit port [enp1s0f0] - Management (recommended) Right = 1Gbit port [enp1s0f1] - Cloud Update Connectivity (recommended)   For Example: NETWORK ADAPTER #1 10_Gbit port [enp10s0] - Intra Cluster Link (recommended) NETWORK ADAPTER #2 1_Gbit port [enp1s0f0] - Management (recommended) NETWORK ADAPTER #3 1_Gbit port [enp1s0f1] - Cloud Update Connectivity (recommended) NETWORK ADAPTER #4 10_Gbit port [enp9s0] - Enterprise Network (recommended)   Here is a sample of what I have configured for the MLOMs   From the ACCESS SWITCH interface Ethernet1/12 description DNAC1 MLOM2 Intra Cluster Network switchport mode trunk switchport trunk allowed vlan 11 ! interface Ethernet1/16 description DNAC2 MLOM2 Intra Cluster Network switchport mode trunk switchport trunk allowed vlan 11 ! interface Ethernet1/18 description DNAC3 MLOM2 Intra Cluster Network switchport mode trunk switchport trunk allowed vlan 11 ** interface Ethernet1/11 description DNAC1 MLOM1 Enterprise Network switchport mode trunk switchport trunk allowed vlan 211 ! interface Ethernet1/15 description DNAC2 MLOM1 Enterprise Network switchport mode trunk switchport trunk allowed vlan 211 ! interface Ethernet1/17 description DNAC3 MLOM1 Enterprise Network switchport mode trunk switchport trunk allowed vlan 211       deadbeef-n9k1# show mac address-table vlan 11 Legend: * - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC age - seconds since last seen,+ - primary entry using vPC Peer-Link, (T) - True, (F) - False, C - ControlPlane MAC, ~ - vsan VLAN MAC Address Type age Secure NTFY Ports ---------+-----------------+--------+---------+------+----+------------------ * 11 380e.4d37.af0a dynamic 0 F F Eth1/12 * 11 b4de.31bd.7aa1 dynamic 0 F F Eth1/16 * 11 b4de.31dd.77ed dynamic 0 F F Eth1/18   deadbeef-n9k1# show mac address-table vlan 211 Legend: * - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC age - seconds since last seen,+ - primary entry using vPC Peer-Link, (T) - True, (F) - False, C - ControlPlane MAC, ~ - vsan VLAN MAC Address Type age Secure NTFY Ports ---------+-----------------+--------+---------+------+----+------------------ * 211 380e.4d37.af09 dynamic 0 F F Eth1/11 * 211 b4de.31bd.7aa0 dynamic 0 F F Eth1/15 * 211 b4de.31dd.77ec dynamic 0 F F Eth1/17     From the CIMC (DNAC1) Host Ethernet Interfaces Total 2 NAME CDN           MAC               MTU  VLAN  VLAN MODE eth0 VIC-MLOM-eth0 38:0E:4D:37:AF:09 1500 211   TRUNK eth1 VIC-MLOM-eth1 38:0E:4D:37:AF:0A 1500 11    TRUNK     If may serve you better to open a Cisco TAC Case so you can discuss all your questions and doubts with a Cisco DNA Center Engineer.   ... View more

ciscoworlds,   Each configured interface needs to be connected and status of UP. Each configured interface has an associated VIP address configured also so if you have 2 configured interfaces then you need 2 VIPs. so if you have 3 configured interfaces then you need 3 VIPs. so if you have 4 configured interfaces then you need 4 VIPs.   it just depends on your Cisco DNAC configuration.     ... View more

Umesh,   I see those SNMP attributes gathered during the inventory sync but as you mentioned they are not all shown in the API for getting device information.  The sysName is included in the API response as the hostname.  The other SNMP attributes may be stored in the postgres db and possibly be extracted but probably easier to use the API to get the list of all the network devices and glean out the management IP and then run SNMP queries against the devices themselves using a script.   Regards   T.  ... View more

Da Xu,   Just a reminder this is an External Community so please do not post  or reference internal links.  That said if you search internally I wrote an article on this topic on Techzone.   Look at my article: TOTD: HOW TO DELETE IP ADDRESS POOL WHEN YOU GET THE ERROR: “Error "Failed to delete IP Pool: ... has reserved subpools” ?   If you are using the  POSTMAN  NATIVE APP for OSX or Windows &  upgraded to the latest release, API requests to the DNAC may fail with "401 Unauthorized".  The issue is under investigation but as suggested use either RESTLET or the  POSTMAN  CHROME browser app for REST API calls to the DNAC.  Issue listed in attached email thread.   This is with POSTMAN.  Use RESTLET Client and the old & new token URLs will work:     ... View more

Avinash,   Installing a custom image on a regular UCS C220 M4S is not supported. Also, this is not the discussion form to have these conversations.  Please use internal mailers for any discussions for internal installations.   Regards T.   ... View more

The capabilities for shared services in tenants outside of “Tenant Common” started in release 1.2(3m) or later. I hope this helps. T. ... View more

Common – a special tenant with the purpose of providing “common” services to other tenants in the ACI fabric. Global reuse is a core principle in the common tenant. Some examples of common services are: a. Shared Private Networks b. Shared Bridge Domains c. DNS d. DHCP e. Active Directory Just to name a few...   You are correct in later releases of ACI Firmware other Tenants can be used in a similar way as the Common Tenant.  The difference is not all objects are seen globally in the fabric from other Tenants by default.  You would need to have certain configurations to make things seen.   I hope this helps! T. ... View more

Roy, I am glad that it is working.  For this question and for future questions, please mark your questions answered so that others can see the results for similar issues. Thanks T.  ... View more

Management preference for you and your environment is a decision best made by your networking team. That said, what ever management strategy that you choose does matter. In regards to INB vs. OOB, remember INB & OOB is for “management” of ACI nodes. That is APICs, Leaf nodes, Spine Nodes, etc… External Data collectors like Syslog, SNMP, and Callhome features communicate to the ACI nodes via INB, OOB, or Both. If both in-band and out-of-band management policies for ACI nodes (APIC\Leaf\Spine) are configured correctly & successfully deployed; the in-band management interface is the preferred management interface. Even if you configure a policy to use the out-of-band management EPG, the ACI node will still use the in-band management interface. The exceptions to the in-band management connectivity preference are: * The Destination IP address for the policy resides in the out-of-band management network. * The ACI Node receives a request packet destined to the node's IP address of the out-of-band management interface. The ACI Node will reply to the request using the out-of-band management interface. Originally, there was no way to change this management connectivity preference for ACI nodes. So in the latest versions ACI firmware, a feature was added to toggle between in-band and out-of-band connectivity on the APIC server for management access to devices such as authentication servers or SNMP servers external to the ACI fabric. A requirement for this feature for the toggling between in-band and out-of-band connectivity to have effect, Both in-band or out-of-band management must already be configured. Note: As noted above, this toggling between in-band and out-of-band connectivity feature will only change the management connectivity preference on the APIC controllers not the leaf or spine nodes. The leaf & spine nodes will continue to use the in-band management connectivity preference. In troubleshooting your issue, here are some things to try: if you are using INBAND management with OOB, disable INB management by simply unconfiguring INB static node management addresses for all of the nodes.  Then make sure the management EPG for your SNMP configuration is set to OOB. For OOB & INB, make sure that you have Static node management addresses configured for ALL nodes including the APICs.  Most ACI Administrators forget to configure static node management addresses for APICs since they configured them during the setup script. For contracts for the OOB, use the "default" common filter to allow all for the testing of the feature.  Also, use 0.0.0.0 for the subnet on the external management instance for testing feature. Make sure that your SNMP Collector's IP is configured in the SNMP Client groups in the SNMP fabric policies. Are you using SNMP v2 or v3?  If v3 make sure all of the v3 parameters are configured. What does the following commands show on the APIC(s): netstat -aon | grep ":161" netstat -lp | grep "snmp" show snmp clientgroups   ( you can xxxx out the IP addresses) moquery -c vzEntry | egrep -A 2 "161" moquery -c vzEntry | egrep -A 2 "162" moquery -c mgmtSubnet moquery -c mgmtRsOoBCons moquery -c vzOOBBrCP  moquery -c snmpRsEpg | egrep "snmp.RsEpg|dn|tDn" ps aux | grep snmp Also what version are you running? Thanks T. ... View more

also, Ask the ACI Experts: SNMP in the ACI Fabric https://supportforums.cisco.com/blog/13100731/ask-aci-experts-snmp-aci-fabric ... View more

Roy, Check out my document here: Technote: SNMP in the ACI Fabric https://supportforums.cisco.com/document/12961146/technote-snmp-aci-fabric T. ... View more