Cisco RestConf Cheatsheet

This post is a work in progress, as i’m currently using Restconf for different customer, I want to save/post some of the infos i discovered.

Get a Portchannel Subinterface
Delete a Portchannel Subinterface

How to read out the used ACI basic parameters

It happend to me more than once, that i needed the basic parameters that were used during the initial setup of the Fabric. For example if you configure a standby APIC later on, or if you (for whatever reason) reset and APIC and redo the initial configuration dialog.

Of course, we always document everything we do, so we could simply look the information up in the documentation! But there is a faster way, just hop onto one of the APICs and use a small cat command.

cat /data/data_admin/sam_exported.config

This gives you back all the of the base parameters you used, during the initial setup.

apic01# cat /data/data_admin/sam_exported.config
Setup for Active and Standby APIC

fabricDomain = DC
fabricID = 1
systemName = apic01
controllerID = 1
tepPool =
infraVlan = 3967
GIPo =
clusterSize = 3
standbyApic = NO
enableIPv4 = Y
enableIPv6 = N
firmwareVersion = 4.2(7f)
ifcIpAddr =
apicX = NO
podId = 1
oobIpAddr =

My colleague Matthias (A daily reader of the blog), pointed out that the sam_exported.config is only present in newer version. If the command doesn’t work for you, check out the attached Technote from Cisco 🙂

AAA (TACACS+) configuration for NDB

Today I integrated a NDB Controller VM with the ISE (TACACS) of a customer. As it wasn’t that easy to find the correct shell profile config, i thought that I will post it here as documentation 🙂

Possible cisco-av-pair’s for the NDB controller VM.

Write (Admin)


Read (Admin)

ISE configuration example for Admin access

AVI Networks – Reset Controller

Sometimes it’s required to reset a controller, this can be done from the cli.

First login to the controller you wish to reset

→ ssh admin@
Avi Cloud Controller

Avi Networks software, Copyright (C) 2013-2017 by Avi Networks, Inc.
All rights reserved.

Version:      18.2.2
Date:         2019-03-06 09:07:37 UTC
Build:        9224
Management:                UP
Gateway:                   UP

admin@'s password:

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 and

After that you need to switch to the AVI Shell and there you can issue the ‘reboot clean’ command. Credentials for the AVI Shell are the same as for the SSH Login.

admin@192-168-128-8:~$ shell
Login: admin

[admin:192-168-128-8]: > reboot clean

This will erase the entire configuration and reboot the cluster

Would you like to proceed? (yes/no): yes

This may take 2-3 minutes to complete. Please wait...

Lost connectivity to the controller -- Retrying to connect
Re-established connectivity -- Please retry the command

Broadcast message from root@192-168-128-8 (somewhere) (Fri Mar  8 16:46:51 2019)

Rebooting this VM because of the cluster event 'clean reboot'

Cisco ACI – Convert Leaf Ports (Uplink to Downlink)

Since ACI release 3.1(1) it’s now possible to use some of the Leaf Uplinks as Downlink Ports. This could help you out if there is a need for some 40/100G ports but you are currently only running 10G Leafs.
Currently the following Leafs support the conversion:

  • N9K-C9348GC-FXP
  • N9K-C93180LC-EX
  • N9K-C93180YC-FX
  • N9K-C93180YC-EX and N9K-C93180YC-EXU
  • N9K-C93108TC-EX
  • N9K-C93108TC-FX
  • N9K-C9336C-FX2 (only downlink to uplink conversion supported)

There are some limitations, check them out on the Cisco Page.

Our use case was to use some of the 40/100G Ports as Downlinks on a N9K-C93180YC-FX. The main limitation there is that the last 2 ports (53 and 54) don’t support conversion, no issue if you use them as Uplinks anyway.


ACI/N9K – How to convert a Nexus 9000 from NX-OS to ACI

Some time ago i posted how to convert a ACI switch to NX-OS, now the other way around.

Copy the file to the NX-OS Mode N9k

switch# copy scp: bootflash:
Enter source filename: Downloads/aci-n9000-dk9.12.2.1o.bin
Enter vrf (If no input, current vrf 'default' is considered): management
Enter hostname for the scp server:
Enter username: USER
aci-n9000-dk9.12.2.1o.bin                       1%   15MB   3.8MB/s   04:34 ETA

Change the boot mode to aci

switch(config)# boot aci bootflash:///aci-n9000-dk9.12.2.1o.bin
Warning: Please check list of all ACI supported hardware before doing this operation, not all hardware are supported.
Warning: Booting to an ACI image will remove all nxos configuration and format bootflash. Do you want to continue (y/n)?[n] y
Performing image verification and compatibility check, please wait....

Image verification successful.

That’s it, just boot the switch and you can join the fabric 🙂
Be aware that the first reload can take quite some time! (15minutes+)

switch# reload
!!!WARNING! there is unsaved configuration!!!
This command will reboot the system. (y/n)?  [n] y

Unable to create San-Port-Channel Between Nexus 5548UP and UCS(-Mini)

The Issue

We implemented a new UCS-Mini for a customer with existing Nexus 5548UP (5.1(3)N1(1a)), on the SAN Part we faced some strange issues:

2017 Mar 25 12:11:30 NEX5548-2 %PORT-5-IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN: %$VSAN 300%$ Interface san-port-channel 200 is down (No operational members)
2017 Mar 25 12:11:31 NEX5548-2 Mar 25 12:11:31 %KERN-3-SYSTEM_MSG: fc2_nsh_tx_frame: FC2 s_id/d_id/vsan error: sid=0xfffffe,did=0x0,vsan=300,rctl:0x23,type:0x1,oxid 0x4d,rxid:0xff25 - kernel
2017 Mar 25 12:12:10 NEX5548-2 %PORT-5-IF_PORT_QUIESCE_FAILED: Interface fc1/20 port quiesce failed due to failure reason: Force Abort Due to Link Failure (NOS/LOS) (0x119)
2017 Mar 25 12:12:10 NEX5548-2 %PORT-5-IF_DOWN_OLS_RCVD: %$VSAN 300%$ Interface fc1/20 is down (OLS received) san-port-channel 200
2017 Mar 25 12:12:10 NEX5548-2 Mar 25 12:12:10 %KERN-3-SYSTEM_MSG: fc2_nsh_tx_frame: FC2 s_id/d_id/vsan error: sid=0xfffffe,did=0x0,vsan=300,rctl:0x23,type:0x1,oxid 0x5a,rxid:0xff32 - kernel

The san-port-channel was really basic and added to just one VSAN

interface san-port-channel 200
  channel mode active
  switchport mode F
  switchport trunk mode off

vsan 220 interfaces:
    san-port-channel 100 san-port-channel 200

There was also an existing UCS where the san-port-channel worked without any issue

san-port-channel 100 is up
    Hardware is Fibre Channel


After some looking around i found a bug that matched pretty good on the cisco page.
I checked the MAC OUI on the UCS Mini

UCS-Mini-A# connect nxos
UCS-Mini-A(nxos)# show int fc1/1
fc1/1 is down
    Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
    Port WWN is XX:XX:00:de:fb:XX:XX:XX

These matches the OUIs described in the bug

Add MAC OUI “002a6a”, “8c604f”, “00defb” for 5k/UCS-FI

After upgrading the Nexus 5548UP to 5.2.1.N1.9b i was finally able to bring the san-port-channel up between the Nexus and the UCS-Mini.

  BIOS:      version 3.6.0
  loader:    version N/A
  kickstart: version 5.2(1)N1(9b)
  system:    version 5.2(1)N1(9b)

2017 Mar 26 07:52:12 NEX5548-2 %PORT-5-IF_UP: %$VSAN 300%$ Interface san-port-channel 200 is up in mode F