Saturday, September 5, 2026

Perform a Cisco Hardware RMA

These are some of the critical steps when performing a Cisco hardware Return Material Authorization (RMA). This applies to any Cisco device, i.e. router, switch, firewall, etc. The common RMA FAQ can be found in this link. I broke down the RMA process into these different steps (with the help of AI):

Step 1: Initial Troubleshooting and Cisco TAC Engagement
Step 2: Hardware Replacement 
Step 3: Initial RMA Router Validation 
Step 4: Install the Required Software
Step 5: Restore License Files
Step 6: Main Interface Activation and Generate New SSH Key
Step 7: Restore Router Configuration
Step 8: Validation and Acceptance Testing
Step 9: Return Defective Hardware
 

Step 1: Initial Troubleshooting and Cisco TAC Engagement

Raise a Cisco TAC service request (SR) case via the Support Case Manager portal (CCO login required). 

Provide the following information:
  • Detailed problem description
  • Impact assessment and outage details
  • Network topology or Visio diagram (recommended)
  • Device model and serial number
  • Relevant timestamps
 
Attach the following output in the case portal:
  • show log
  • Required show command outputs
  • show tech-support
  • Crash information if available (show crashinfo)

Note: Try to engage a Cisco TAC engineer as early as possible to expedite troubleshooting and RMA if required.

Before performing any recovery action, ensure the necessary device files are backed up. Using an external USB disk is recommended for quick file transfers.

Backup the following from the reported router, if applicable:

  • IOS-XE image
  • ROMmon firmware
  • startup-config from NVRAM (dir nvram:)
  • License files (show license all)
If the IOS-XE and ROMmon files cannot be recovered, download the matching version from the Cisco Software Download Center (CCO login required).

Attempt device recovery if the router is unresponsive:

  1. Connect to the router using a console cable.
  2. Coordinate all troubleshooting activities with the TAC engineer.
  3. Perform a hard reboot/power cycle
  4. Monitor/capture the entire boot sequence from console.

Verify:

  • ROMmon accessibility
  • IOS-XE boot progress
  • Hardware diagnostics (POST)
  • Crash messages or boot failures

Request Cisco TAC to initiate an RMA if troubleshooting and recovery efforts are unsuccessful

Confirm:

  • Hardware part number
  • Service contract entitlement
  • Shipping address
  • Delivery priority

Important: Cisco RMA shipment doesn't include:

  • Power supply
  • Rack mounting ear/kit
  • Existing SFP/GBIC modules


Step 2: Hardware Replacement 

Once the RMA replacement router arrives, prepare to shut down the failed device:

  1. Power off the faulty router.
  2. Label all connected cables:
    • Power cables
    • RJ45 Ethernet cables
    • Fiber cables
  3. Document:
    • Interface-to-cable mapping
    • Installed SFPs/GBICs
    • Rack position/slot

Remove hardware:

  1. Remove power supplies.
  2. Remove SFPs/GBICs.
  3. Remove rack mounting ears.
  4. Unmount the router from the rack.

 

Install the RMA Router:

  1. Transfer the following components to the RMA replacement router:
    • Power supplies
    • Rack mounting ears
    • SFPs/GBICs
  2. Mount the RMA router in the rack.
  3. Reconnect:
    • Power cables
    • RJ45 cables
    • Fiber connections
  4. Apply sticker labels to the front and rear of the chassis. 

 

Step 3: Initial RMA Router Validation 

Verify base hardware info on the RMA router and monitor its bootup via console. Execute the following commands:

show inventory
show version
show platform
show license all
show run

Verify:

  • Correct hardware model
  • Correct memory size
  • Module detection
  • Chassis serial number
  • License status 


Step 4: Install the Required Software

Transfer the IOS-XE and ROMmon files from external USB disk to the RMA router bootflash. 

copy usb0:asrxx-rommon.16xx.pkg bootflash:

copy 
usb0:asrxx-universalk9.16.xx.SPA.bin bootflash:

dir bootflash:

 

Verify the MD5 hash and compare it from the Cisco Software Center website. 

#verify /md5 asrxx-rommon.16xx.pkg

#verify /md5 asrxx-universalk9.16.xx.SPA.bin

 

Perform the RMA router upgrade. Start with the ROMmon firmware upgrade first.


#upgrade rom-monitor filename bootflash:asrxx-rommon.16xx.pkg  all    

reload

show platform



Perform the main IOS-XE upgrade next.

configure terminal

no boot system

boot system flash bootflash:asrxx-universalk9.16.xx.SPA.bin   // TARGET IOS-XE
boot system flash bootflash:asr1001x-universalk9.03.12.xx.bin   // DEFAULT IOS-XE IN RMA 

write memory

show run | inc boot

reload


Phase 5: Restore License Files


If the router is using a Traditional license (non Smart License), re-host or transfer the license file to the RMA router. Contact TAC License team to manually assist and email the Traditional license file. You can also ask the current TAC engineer to open a collaboration ticket with TAC License team to expedite the process.


#show license udi   !! GIVE TAC LICENSE TEAM THE UDI SERIAL NUMBER

#copy usb0:/JAD23xx.lic bootflash:

#license install bootflash:JAD23xx.lic 

show version

show license all


Phase 6: Main Interface Activation and Generate a new SSH Key

Enable the main physical interfaces that have the attached SFP and RJ45/fiber cables. Don't save the config at this stage yet.

configure terminal 

interface TenGigabitEthernet0/0/0
 no shutdown

interface GigabitEthernet0/0/1
 no shutdown

interface GigabitEthernet0
 no shutdown


 

To prevent remote access lock out, generate a new SSH key and temporary enable Telnet under the VTY lines. You can disable Telnet once remote SSH/AAA is working.

configure terminal  

ip domain name local.com

crypto key generate rsa modulus 2048
 

line vty 0 4

transport input all

 

Phase 7: Restore Router Configuration

Copy the startup-config (from old router) via USB to running-config (RMA router).

#copy usb0:startup-config-new running-config

 

Phase 8: Validation and Acceptance Testing

Perform RMA router validation and save config once it's fully operational.

show inventory

show version

show platform

show ip interface brief

show ip bgp summary

write memory



You'll also need to re-configure SNMP and re-poll the RMA router in your NMS server.

configure terminal 

no snmp-server 

snmp-server group <GROUP> v3 auth read <VIEW> access <ACL>


snmp-server user <USER> <GROUP> v3 auth sha <PW>


snmp-server view <VIEW> internet included
snmp-server view <VIEW> system included
snmp-server view <VIEW> interfaces included

snmp-server location <DEVICE LOCATION>
snmp-server contact <ADMIN CONTACT>

write memory

 

Phase 9: Return Defective Hardware

Put the failed Cisco router in the same box that was shipped. Use the Cisco POWR portal to arrange courier pickup. There's an option in the portal to request the courier to print the shipping label.

Friday, July 31, 2026

Renumbering a Cisco 9300 Switch

Here's a Cisco link to renumber a Cisco switch stack. Validate the current switch stack number using the show switch command. In my scenario, it's only a single switch which was pulled out from a previous switch stack. I had to renumber the switch using the privilege command switch <current-number> renumber <new-number> in order to display the correct interface number. A reload is required afterwards.

 

C9300#show switch
Switch/Stack Mac Address : 2416.9d7b.1234 - Local Mac Address
Mac persistency wait time: Indefinite
                                             H/W   Current
Switch#   Role    Mac Address     Priority Version  State
-------------------------------------------------------------------------------------
 1       Member   0000.0000.0000     0              Provisioned                 
*2       Active   2416.9d7b.1234     1      V03     Ready 

 

C9300#switch ?
  <1-16>  Switch Number
  clear   Reset the switch mode to N+1

C9300#switch 2 ?
  priority    Set the priority of the specified switch
  renumber    Renumber the specified switch number
  ring-speed  Set the switch ring speed to low/high
  role        Set the new switch mode of the Switch
  stack       Stack port enable or disable

C9300#switch 2 renumber ?
  <1-16>  New number of the Switch

C9300#switch 2 renumber 1
WARNING: Changing the switch number may result in a configuration change for that switch.  The interface configuration associated with the old switch number will remain as a provisioned configuration. New Switch Number will be effective after next reboot. Do you want to continue?[y/n]? [yes]: yes

C9300#reload

System configuration has been modified. Save? [yes/no]: y
Building configuration...
[OK]Reload command is being issued on Active unit, this will reload the whole stack


The switch was already in the correct number/order but it still had Gi2/0/x interfaces.

C9300#show switch
Switch/Stack Mac Address : 2416.9d7b.1234 - Local Mac Address
Mac persistency wait time: Indefinite
                                             H/W   Current
Switch#   Role    Mac Address     Priority Version  State
-------------------------------------------------------------------------------------
*1       Active   2416.9d7b.1234     1      V03     Ready                   
 2       Member   0000.0000.0000     0              Provisioned                 


C9300#show interface description
Interface                      Status         Protocol Description
Vl1                            up             up
Gi0/0                          admin down     down
Gi1/0/1                        down           down
Gi1/0/2                        down           down
Gi1/0/3                        down           down
Gi1/0/4                        down           down
Gi1/0/5                        down           down
Gi1/0/6                        down           down
Gi1/0/7                        down           down
Gi1/0/8                        down           down
Gi1/0/9                        down           down
Gi1/0/10                       down           down
Gi1/0/11                       down           down
Gi1/0/12                       down           down
Gi1/0/13                       down           down
Gi1/0/14                       down           down
Gi1/0/15                       down           down
Gi1/0/16                       down           down
Gi1/0/17                       down           down
Gi1/0/18                       down           down
Gi1/0/19                       down           down
Gi1/0/20                       down           down
Gi1/0/21                       down           down
Gi1/0/22                       down           down
Gi1/0/23                       down           down
Gi1/0/24                       down           down
Gi1/0/25                       down           down
Gi1/0/26                       down           down
Gi1/0/27                       down           down
Gi1/0/28                       down           down
Gi1/0/29                       down           down
Gi1/0/30                       down           down
Gi1/0/31                       down           down
Gi1/0/32                       down           down
Gi1/0/33                       down           down
Gi1/0/34                       down           down
Gi1/0/35                       down           down
Gi1/0/36                       down           down
Gi1/0/37                       down           down
Gi1/0/38                       down           down
Gi1/0/39                       down           down
Gi1/0/40                       down           down
Gi1/0/41                       down           down
Gi1/0/42                       down           down
Gi1/0/43                       down           down
Gi1/0/44                       down           down
Gi1/0/45                       down           down
Gi1/0/46                       down           down
Gi1/0/47                       down           down
Gi1/0/48                       down           down
Gi1/1/1                        down           down
Gi1/1/2                        down           down
Gi1/1/3                        down           down
Gi1/1/4                        down           down
Te1/1/1                        down           down
Te1/1/2                        down           down
Te1/1/3                        down           down
Te1/1/4                        down           down
Te1/1/5                        down           down
Te1/1/6                        down           down
Te1/1/7                        down           down
Te1/1/8                        down           down
Fo1/1/1                        down           down
Fo1/1/2                        down           down
Twe1/1/1                       down           down
Twe1/1/2                       down           down
Ap1/0/1                        up             up
Gi2/0/1                        down           down
Gi2/0/2                        down           down
Gi2/0/3                        down           down
Gi2/0/4                        down           down
Gi2/0/5                        down           down
Gi2/0/6                        down           down
Gi2/0/7                        down           down
Gi2/0/8                        down           down
Gi2/0/9                        down           down
Gi2/0/10                       down           down
Gi2/0/11                       down           down
Gi2/0/12                       down           down
Gi2/0/13                       down           down
Gi2/0/14                       down           down
Gi2/0/15                       down           down
Gi2/0/16                       down           down
Gi2/0/17                       down           down
Gi2/0/18                       down           down
Gi2/0/19                       down           down
Gi2/0/20                       down           down
Gi2/0/21                       down           down
Gi2/0/22                       down           down
Gi2/0/23                       down           down
Gi2/0/24                       down           down
Gi2/0/25                       down           down
Gi2/0/26                       down           down
Gi2/0/27                       down           down
Gi2/0/28                       down           down
Gi2/0/29                       down           down
Gi2/0/30                       down           down
Gi2/0/31                       down           down
Gi2/0/32                       down           down
Gi2/0/33                       down           down
Gi2/0/34                       down           down
Gi2/0/35                       down           down
Gi2/0/36                       down           down
Gi2/0/37                       down           down
Gi2/0/38                       down           down
Gi2/0/39                       down           down
Gi2/0/40                       down           down
Gi2/0/41                       down           down
Gi2/0/42                       down           down
Gi2/0/43                       down           down
Gi2/0/44                       down           down
Gi2/0/45                       down           down
Gi2/0/46                       down           down
Gi2/0/47                       down           down
Gi2/0/48                       down           down
Gi2/1/1                        down           down
Gi2/1/2                        down           down
Gi2/1/3                        down           down
Gi2/1/4                        down           down
Te2/1/1                        down           down
Te2/1/2                        down           down
Te2/1/3                        down           down
Te2/1/4                        down           down
Te2/1/5                        down           down
Te2/1/6                        down           down
Te2/1/7                        down           down
Te2/1/8                        down           down
Fo2/1/1                        down           down
Fo2/1/2                        down           down
Twe2/1/1                       down           down
Twe2/1/2                       down           down
Ap2/0/1                        down           down

 

It still had the switch <number> provision <platform> command, which is used to preconfigure interfaces before physically stacking the switch. I just negate using switch 2 provision c9300-48p to remove the Gi2/0/x interfaces. You'll need to reload to take effect.

 

C9300#show run | i switch
switch 1 provision c9300-48p
switch 2 provision c9300-48p
C9300#
C9300#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
C9300(config)#no switch 2 provision c9300-48p
C9300(config)#end
C9300#write memory
Building configuration...
[OK]
C9300#reload
Reload command is being issued on Active unit, this will reload the whole stack
Proceed with reload? [confirm]
 

C9300#show switch
Switch/Stack Mac Address : 2416.9d7b.1234 - Local Mac Address
Mac persistency wait time: Indefinite
                                             H/W   Current
Switch#   Role    Mac Address     Priority Version  State
-------------------------------------------------------------------------------------
*1       Active   2416.9d7b.1234     1      V03     Ready                       


C9300#show interface description
Interface                      Status         Protocol Description
Vl1                            up             up
Gi0/0                          admin down     down
Gi1/0/1                        down           down
Gi1/0/2                        down           down
Gi1/0/3                        down           down
Gi1/0/4                        down           down
Gi1/0/5                        down           down
Gi1/0/6                        down           down
Gi1/0/7                        down           down
Gi1/0/8                        down           down
Gi1/0/9                        down           down
Gi1/0/10                       down           down
Gi1/0/11                       down           down
Gi1/0/12                       down           down
Gi1/0/13                       down           down
Gi1/0/14                       down           down
Gi1/0/15                       down           down
Gi1/0/16                       down           down
Gi1/0/17                       down           down
Gi1/0/18                       down           down
Gi1/0/19                       down           down
Gi1/0/20                       down           down
Gi1/0/21                       down           down
Gi1/0/22                       down           down
Gi1/0/23                       down           down
Gi1/0/24                       down           down
Gi1/0/25                       down           down
Gi1/0/26                       down           down
Gi1/0/27                       down           down
Gi1/0/28                       down           down
Gi1/0/29                       down           down
Gi1/0/30                       down           down
Gi1/0/31                       down           down
Gi1/0/32                       down           down
Gi1/0/33                       down           down
Gi1/0/34                       down           down
Gi1/0/35                       down           down
Gi1/0/36                       down           down
Gi1/0/37                       down           down
Gi1/0/38                       down           down
Gi1/0/39                       down           down
Gi1/0/40                       down           down
Gi1/0/41                       down           down
Gi1/0/42                       down           down
Gi1/0/43                       down           down
Gi1/0/44                       down           down
Gi1/0/45                       down           down
Gi1/0/46                       down           down
Gi1/0/47                       down           down
Gi1/0/48                       down           down
Gi1/1/1                        down           down
Gi1/1/2                        down           down
Gi1/1/3                        down           down
Gi1/1/4                        down           down
Te1/1/1                        down           down
Te1/1/2                        down           down
Te1/1/3                        down           down
Te1/1/4                        down           down
Te1/1/5                        down           down
Te1/1/6                        down           down
Te1/1/7                        down           down
Te1/1/8                        down           down
Fo1/1/1                        down           down
Fo1/1/2                        down           down
Twe1/1/1                       down           down
Twe1/1/2                       down           down
Ap1/0/1                        up             up

Friday, July 10, 2026

Troubleshoot Cisco Router SSH RSA Issue

I wasn't able to remotely SSH to a Cisco router using different management jump servers. I got different error message below.

admin@server01:~$ ssh 172.27.6.1

The authenticity of host '172.27.6.1 (172.27.6.1)' can't be established.

RSA key fingerprint is SHA256:ESsfNyzjhVIYlQ/ZWDwGBeBJg6Hn1mfSO3NEW012345.

This key is not known by any other names.

Are you sure you want to continue connecting (yes/no/[fingerprint])? yes

Warning: Permanently added '172.27.6.1' (RSA) to the list of known hosts.

ssh_dispatch_run_fatal: Connection to 172.27.6.1 port 22: incorrect signature

 

 

admin@server02~$ ssh 172.27.6.1

The authenticity of host '172.27.6.1 (172.27.6.1)' can't be established.

RSA key fingerprint is 43:03:59:93:b3:98:46:92:64:bd:8d:f7:2d:12:34:56.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added '172.27.6.1' (RSA) to the list of known hosts.

RSA_public_decrypt failed: error:0407006A:rsa routines:RSA_padding_check_PKCS1_type_1:block type is not 01

key_verify failed for server_host_key

 

I've temporary enabled Telnet and regenerated (zeroise) the SSH/RSA key. Make sure domain name is configured.

Router#show ip ssh

SSH Enabled - version 1.99

Authentication methods:publickey,keyboard-interactive,password

Authentication Publickey Algorithms:x509v3-ssh-rsa,ssh-rsa

Hostkey Algorithms:x509v3-ssh-rsa,ssh-rsa

Encryption Algorithms:aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc

MAC Algorithms:hmac-sha1,hmac-sha1-96

Authentication timeout: 120 secs; Authentication retries: 3

Minimum expected Diffie Hellman key size : 1024 bits

IOS Keys in SECSH format(ssh-rsa, base64 encoded): CISCO_IDEVID_SUDI

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDGzzxJCzuFj/sHvJuZA4fzhV6t6XHDR73aCPNZZxoD

5iuUp8pu14OAV5L+Zu+EL6QZqV88bcmRvSYp05JmLrGmlBv4QAJluyla85PnZurC4OBxSxWg/gx40mzJ

yWeHnlQd1euxbo0J0+gkwLQYWmrsgGLpfqhXKDAUVCzhPdpjRdUT3wg2Cbk49YSr+LntrPwBVBRF7dEl

p1mGs2ykL0LDmU6rlWf9O1aRsUYmFhgK16pFekFGluKmrdaoak5sfk9ch38rr5O8rejcsjp408PyeJrS

jgB3sVTBpywcG39LtmLaku5xQrGfjlowyBOyRaLRgbjZDvdfl7aqABC12345

 

Router#show run | inc domain

no ip domain lookup

ip domain name local.com

 

I initially removed the SSH/RSA key and configured the basic rsa key without configuring a label but still couldn't SSH.

Router(config)#crypto key zeroize

% All keys will be removed.

% All router certs issued using these keys will also be removed.

Do you really want to remove these keys? [yes/no]: yes

 

Router(config)#crypto key generate rsa modulus 2048

The name for the keys will be: Router.local.com

 

% The key modulus size is 2048 bits

% Generating 2048 bit RSA keys, keys will be non-exportable...

[OK] (elapsed time was 0 seconds) 

 

I've zerioise the SSH key again and explicitly configured a label and keypair-name. I was able to SSH to the router afterwards.

Router(config)#crypto key zeroize

% All keys will be removed.

% All router certs issued using these keys will also be removed.

Do you really want to remove these keys? [yes/no]: yes

Router(config)#

Router(config)#crypto key generate rsa mod 2048 label Router.local.com

The name for the keys will be: Router.local.com

 

% The key modulus size is 2048 bits

% Generating 2048 bit RSA keys, keys will be non-exportable...

[OK] (elapsed time was 2 seconds)

 

Router(config)#ip ssh rsa keypair-name Router.local.com

Router(config)# end

Router#write memory

Building configuration...

[OK]


Wednesday, June 10, 2026

Configure Cisco Smart Licensing Using Policy (CSLU)

Here's a Cisco link and a video tutorial to configure Cisco Smart Licensing Using Policy (CSLU). Below are the commands to be used in a Cisco IOS-XE device. 

In the Cisco Smart Software Manager (CSSM, a.ka. Smart License), click the blue hyperlink > CLSU Transport URL.


ip name-server <PRIMARY DNS IP> <SECONDARY DNS IP>
ip domain lookup 
ip domain lookup source-interface Loopback0
ip http client source-interface Loopback0

license smart transport cslu

license smart url cslu https://<ON PREM SMART LICENSE SERVER IP>/cslu/v1/pi/<VIRTUAL ACCOUNT>

crypto pki trustpoint SLA-TrustPoint
 revocation-check none

#license smart sync all

 

I've configured CLSU in a Cisco 8000v router 

C8000v#conf t

Enter configuration commands, one per line.  End with CNTL/Z.

C8000v(config)#ip name-server 10.6.6.7 10.8.8.9

C8000v(config)#ip domain lookup

C8000v(config)#ip domain lookup source-interface Loopback0

C8000v(config)#ip http client

C8000v(config)#license smart transport cslu

C8000v(config)#license smart url cslu https://myccsm01.com/cslu/v1/pi/my-va-4

C8000v(config)#crypto pki trustpoint SLA-TrustPoint

C8000v(ca-trustpoint)# revocation-check none

C8000v(ca-trustpoint)#end

C8000v#write memory

Building configuration...

[OK]


C8000v#ping mycssm01.com source Loopback0

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.1.7.9, timeout is 2 seconds:

Packet sent with a source address of 10.4.6.41

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 116/116/116 ms


C8000v#license smart sync all

 

Nov 25 00:47:39.403 UTC: CSR CSL:pid = C8000V, sn = 91Y2A1B1234

Nov 25 00:47:39.948 UTC: %SYS-6-PRIVCFG_ENCRYPT_SUCCESS: Successfully encrypted private config file

Nov 25 00:47:39.979 UTC: CSR CSL:

LIC_OBJSTORE_OPEN: IFS open successful. Objname: satimeflagsync.data, App ID:3

Nov 25 00:47:39.990 UTC: CSR CSL:

LIC_OBJSTORE_WRITE: IFS write successful. Objname: satimeflagsync.data, Bytes written: 2384, Write offset: 2384, App ID: 3

Nov 25 00:47:39.990 UTC: CSR CSL:

LIC_OBJSTORE_CLOSE: IFS close successful. FD:0, App ID: 3


Nov 25 09:59:34.556 UTC: CSR CSL:

LIC_OBJSTORE_STAT:Unable to get the size of the object - No such object, App ID: 3

Nov 25 09:59:34.564 UTC: CSR CSL:

LIC_OBJSTORE_STAT:Unable to get the size of the object - No such object, App ID: 3

Nov 25 09:59:34.572 UTC: CSR CSL:

LIC_OBJSTORE_STAT: IFS stat successful. Path: /1759269975.rum.  Objsize: 1047, App ID: 3

Nov 25 09:59:34.581 UTC: CSR CSL:

LIC_OBJSTORE_OPEN: IFS open successful. Objname: 1759269975.rum, App ID:3

Nov 25 09:59:34.590 UTC: CSR CSL:

LIC_OBJSTORE_READ: IFS read successful. Objname: 1759269975.rum, Bytes read: 1047, Read offset: 1047, App ID: 3

LIC_OBJSTORE_OPEN: IFS open successful. Objname: saRumReportMetaData.txt, App ID:3

Nov 25 09:59:37.141 UTC: CSR CSL:

LIC_OBJSTORE_WRITE: IFS write successful. Objname: saRumReportMetaData.txt, Bytes written: 6880, Write offset: 6880, App ID: 3

Nov 25 09:59:37.141 UTC: CSR CSL:

LIC_OBJSTORE_CLOSE: IFS close successful. FD:0, App ID: 3

Nov 25 09:59:37.159 UTC: CSR CSL:

LIC_OBJSTORE_OPEN: IFS open successful. Objname: satimeflagsync.data, App ID:3

Nov 25 09:59:37.168 UTC: CSR CSL:

LIC_OBJSTORE_WRITE: IFS write successful. Objname: satimeflagsync.data, Bytes written: 2384, Write offset: 2384, App ID: 3

Nov 25 09:59:37.168 UTC: CSR CSL:

LIC_OBJSTORE_CLOSE: IFS close successful. FD:0, App ID: 3


<OUTPUT TRUNCATED>


Validate the Smart License status using the show license summary command.

C8000v#show license summary

Account Information:

  Smart Account: <none>

  Virtual Account: <none>

 

License Usage:

  License                 Entitlement Tag               Count Status

  -----------------------------------------------------------------------------

  network-advantage_T0    (NWSTACK_T0_A)                    1 IN USE

  dna-advantage_T0        (DSTACK_T0_A)                     1 IN USE


You can also validate the Smart License status in the CSSM server (either Cisco public cloud or On Prem), go to Smart Licensing > Inventory > Product Instance tab > Event Log.



Saturday, May 2, 2026

Copying Files in a Cisco Nexus 9000 Switch

Here's a Cisco link in copying or transferring a Nexus config file to a remove server (or local USB). This is useful if you're doing an RMA and needed to quickly transfer config from old to new Nexus switch. If you're using the USB flash drive/disk, make sure it's formatted to FAT16

 

N9K# copy running-config usb1:my-config.cfg

Copy complete, now saving to disk (please wait)...

Copy complete.

 

 

N9K# dir usb1:

       4096    Feb 06 09:41:48 2026  System Volume Information/

      34494    Feb 06 09:41:48 2026  autorun.ico

        194    Feb 06 09:41:48 2026  autorun.inf

      23462    Mar 07 03:55:23 2026  my-config.cfg

 2058225152    Feb 06 11:18:24 2026  nxos.9.3.x.bin


The NX-OS file transfer took a few minutes to finish. Make sure your USB drive has enough memory.

N9K# copy nxos64-cs.10.x.M.bin usb1:nxos64-cs.10.x.M.bin

Copy progress 70% 1957560KB

file error

Destination: No space left on device


Friday, April 10, 2026

Junos OS File Directory and MD5 Checksum

I needed to download the Junos OS used in our MX device.

You can use the file list /var/temp CLI command to check the OS image stored (dir or show bootflash: in Cisco)

admin@junos> file list /var/tmp/

 

/var/tmp/:

Jtac-logs.tgz

LOCK_FILE

appidd_cust_app_trace

appidd_trace_debug

bcast.bdisp.log

bcast.disp.log

bcast.rstdisp.log

bcast.undisp.log

current-config.txt

ebmq_authd_vty

ebmq_bbe-pfcp-proxy-vty_vty

ex_autod_config

ex_autod_rollback_cfg

junos-vmhost-install-mx-x86-64-2x.4Rx.8.tgz

krt_rpf_filter.txt

mmcq_authd

mmcq_bbe-cupm

mmcq_bbeStatsdGetCollector

mmcq_cupm-bbe-up-pfcp-proxyd

mmcq_cupm-ep_RepClientUpEpClient

mmcq_cupm-ep_RepServerUpEpClient

mmcq_mmdb_rep_mmcq

mmcq_sdb_bbe_mmcq

netproxy

package.log

pc /

pfe_debug_commands

phone-home/

pics/

pkg_cleanup.log.err

re0.tgz

rtsdb/

sd-upgrade/


To validate the image MD5 checksum, use the file checksum md5 <path/file> command. 

admin@junos> file checksum md5 /var/tmp/junos-vmhost-install-mx-x86-64-2x.4Rx.8.tgz   
MD5 (/var/tmp/junos-vmhost-install-mx-x86-64-2x.4Rx.8.tgz) = 0d02de0cc7aec60825d2dbe513e0af12

Go to the Juniper Software Downloads site, search for the Product, OS and Version. Click Checksums (a hyperlink) to view the MD5, SHA1, etc.

Click the tgz file (a hyperlink), click "I Agree" to proceed.


You can download the OS image locally in your PC or directly to your Juniper device. To download the OS image from your device, just run the file copy <URL destination> command (copy/paste the URL string).


Sunday, March 1, 2026

Configure Policy-Based Routing (PBR) in a Cisco Router

Here's a link in configuring a Policy-Based Routing (PBR) in a Cisco router. I was trying to configure PBR on a customer VRF to test or simulate customer traffic to a new FortiGate firewall. The customer traffic is currently NAT'd to a Cisco ASA firewall.

CE#trace vrf CUST 8.8.8.8 source 192.168.199.1

Type escape sequence to abort.

Tracing the route to 8.8.8.8

VRF info: (vrf in name/id, vrf out name/id)

  1 10.6.9.50 0 msec 0 msec 0 msec

  2 216.12.34.5 0 msec 0 msec 4 msec   // CISCO ASA HOP

  3 72.250.194.1 0 msec 4 msec 0 msec

 

<OUTPUT TRUNCATED>

 

  9  *  *  * 

 10 8.8.8.8 4 msec 8 msec 8 msec


 

Note you'll need to apply PBR in the "ingress" or LAN interface. You also can't configure a Loopback interface then do a ping test sourced locally from the said Loopback. The ping test should be sourced from an IP host/subnet that's "behind" or a Layer 3 hop away from the router doing the PBR.


You'll also need to consider local traffic flows, i.e. if a host would need to access internal resources such as DNS, then you'll need a deny ACL (extended) to exclude those IP/subnets.

PE#show access-list 199 
Extended IP access list 199
    10 deny ip 192.168.199.0 0.0.0.255 10.1.1.0 0.0.0.255   // EXCLUDE INTERNAL DNS TRAFFIC 
    20 permit ip 192.168.199.0 0.0.0.255 any   // PERMIT 192.168.199.0/24 TO INTERNET (NEW FW)

PE#show run | sec route-map MY-PBR   // NO NEED TO CONFIGURE: set vrf <VRF>  
route-map MY-PBR permit 10 
 match ip address 199
 set ip next-hop 172.20.8.12

PE(config)#interface GigabitEthernet0/0/1   // LAN INTERFACE
PE(config-if)#ip policy route-map MY-PBR


CE#ping vrf CUST 8.8.8.8 source 192.168.199.1 rep 10   // GOOGLE DNS
Type escape sequence to abort.
Sending 10, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
Packet sent with a source address of 192.168.199.1 
!!!!!!!!!!
Success rate is 100 percent (10/10), round-trip min/avg/max = 4/8/20 ms


CE#ping vrf CUST 72.163.4.185 source 192.168.199.1   // CISCO.COM
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 72.163.4.185, timeout is 2 seconds:
Packet sent with a source address of 192.168.199.1 
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/8 ms

CE#traceroute vrf CUST 8.8.8.8 source 192.168.199.1       

Type escape sequence to abort.

Tracing the route to 8.8.8.8

VRF info: (vrf in name/id, vrf out name/id)

  1 10.6.9.50 0 msec 0 msec 0 msec

  2 172.20.8.12 msec 4 msec 0 msec   // FORTIGATE HOP

  3 66.12.34.56 0 msec 0 msec 0 msec

 

<OUTPUT TRUNCATED>


 11  *  *  * 
 12 8.8.8.8 4 msec 4 msec 4 msec

 

The PBR was confirmed working when CE router traceroute hop via the new FortiGate IP address. I also checked the NAT translations via the FortiView Sessions. The other RFC1918 IP subnets were still NAT'd via the Cisco ASA firewall.