Trying to access exec mode in ACI Leaf switch

[a.azambuja]

Hi, Im running APIC controller 3.0(2)K and I saw in previous versions that using "attach" to a Leaf, I can access the exec mode and input some shows. But in my version I go only to the "object" mode as bellow.

apic1# bash
admin@apic1:~> attach Leaf01
This command is being deprecated on APIC controller, please use NXOS-style equivalent command
# Executing command: ssh Leaf01 -b 10.0.0.1

admin@leaf01's password:
admin@leaf1:~>        <--- This is the "object mode" different from previous APIC versions like 2.x

I just want to enter in exec mode to see "show vpc" for example... 

[RedNectar · Accepted solution]

Hi a.azambuja,

Firstly, you don't need to access the leaf switches in order to issue commands on the leaf switches, you can do that form the APIC using the fabric prefix.  For example, if you wnated to issue a show vpc command on both leaf 101 and 102, you could enter the command:

fabric 101,102 show vpc

I've pasted an exmple below.

Secondly, there is no concept of exec mode in ACI, but if you really want to (and there are SOME commands that don't work with the fabric option, typically bash commands) then you can still access the leaf using ssh (which is in fact what attach is transformed to if you use it.)

Below are two example of how to issue the show vpc command in an ACI environment, the first using the fabric construct, the second from an ssh session:

Example #1: using fabric

apic1# fabric 101,102 show vpc
----------------------------------------------------------------
 Node 101 (Leaf101)
----------------------------------------------------------------
Legend:
                (*) - local vPC is down, forwarding via vPC peer-link

vPC domain id                     : 12
Peer status                       : peer adjacency formed ok
vPC keep-alive status             : Disabled
Configuration consistency status  : success
Per-vlan consistency status       : success
Type-2 consistency status         : success
vPC role                          : primary
Number of vPCs configured         : 1
Peer Gateway                      : Disabled
Dual-active excluded VLANs        : -
Graceful Consistency Check        : Enabled
Auto-recovery status              : Enabled (timeout = 240 seconds)
Operational Layer3 Peer           : Disabled

vPC Peer-link status
---------------------------------------------------------------------
id   Port   Status Active vlans
--   ----   ------ --------------------------------------------------
1           up     -

vPC status
----------------------------------------------------------------------
id   Port   Status Consistency Reason                     Active vlans
--   ----   ------ ----------- ------                     ------------
685  Po17   up     success     success                    2093-2094


----------------------------------------------------------------
 Node 102 (Leaf102)
----------------------------------------------------------------
Legend:
                (*) - local vPC is down, forwarding via vPC peer-link

vPC domain id                     : 12
Peer status                       : peer adjacency formed ok
vPC keep-alive status             : Disabled
Configuration consistency status  : success
Per-vlan consistency status       : success
Type-2 consistency status         : success
vPC role                          : secondary
Number of vPCs configured         : 1
Peer Gateway                      : Disabled
Dual-active excluded VLANs        : -
Graceful Consistency Check        : Enabled
Auto-recovery status              : Enabled (timeout = 240 seconds)
Operational Layer3 Peer           : Disabled

vPC Peer-link status
---------------------------------------------------------------------
id   Port   Status Active vlans
--   ----   ------ --------------------------------------------------
1           up     -

vPC status
----------------------------------------------------------------------
id   Port   Status Consistency Reason                     Active vlans
--   ----   ------ ----------- ------                     ------------
685  Po1    up     success     success                    2093-2094

Example #2: using ssh

apic1# ssh leaf101
Password:
Last login: Wed Apr  3 20:09:54 2019 from 10.0.0.1
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2018, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
Leaf101# show vpc
Legend:
                (*) - local vPC is down, forwarding via vPC peer-link

vPC domain id                     : 12
Peer status                       : peer adjacency formed ok
vPC keep-alive status             : Disabled
Configuration consistency status  : success
Per-vlan consistency status       : success
Type-2 consistency status         : success
vPC role                          : primary
Number of vPCs configured         : 1
Peer Gateway                      : Disabled
Dual-active excluded VLANs        : -
Graceful Consistency Check        : Enabled
Auto-recovery status              : Enabled (timeout = 240 seconds)
Operational Layer3 Peer           : Disabled

vPC Peer-link status
---------------------------------------------------------------------
id   Port   Status Active vlans
--   ----   ------ --------------------------------------------------
1           up     -

vPC status
----------------------------------------------------------------------
id   Port   Status Consistency Reason                     Active vlans
--   ----   ------ ----------- ------                     ------------
685  Po17   up     success     success                    2093-2094

Leaf101#

I hope this helps

---

Don't forget to mark answers as correct if it solves your problem. This helps others find the correct answer if they search for the same problem

---

[a.azambuja · Accepted solution]

Great!
Tks!!!