Reset the Password on Router without Losing the Old Configuration File

• Console cable needed on router
• Power off router
• Turn on router and issue the break command through Putty
• In rommon, hit question mark to see your options
o You should see confreg
• Change confreg to 0x2142
o >confreg 0x2142
• Reset the router
o >reset
• Once the router reboots, cancel the initial setup dialog. You just need the old startup-config
o >show startup-config
• Once you verify you see your old file, copy the old file to the running-config
o #copy startup-config running-config
• You are now in your old config file without the passwords. Now you can reset your password:
o #conf t
o #enable secret cisco
o #exit
o #copy run start
• Next, you need to change the configreg entry from when we changed it in ROMMON.
o #conf t
o #config-register 0x2102
o #exit
o #write
• Finally, you want to ensure your interfaces are all up since sometimes they go into admin down state and need to be brought up manually. You can reboot if necessary, but now you have access back into the router.

To Log into a Switch from Current Switch

1. You can perform this either from user mode or privileged mode:
a. SW1>ssh -l user_name ip_address
b. SW1#ssh -l user_name ip_address
2. After you pivot into the system from either of the above commands, type in the user’s password (the user you are using to log into the distant switch).

Configure Default Gateway on Cisco Switch

1. First, escalate into global configuration mode:
a. SW1(config)#Config Terminal
2. In global configuration mode you can now make a global setting indicating your default gateway for the switch:
a. SW1(config)#ip default-gateway ip_address

Configure Gateway of Last Resort

1. First, log into the switch you wish to configure.
2. Next, escalate up to Configure Terminal and then type the following:
    a. #conf t
    b.  #ip default-gateway 172.16.X.X
    c.  #end
    d.  #write
3. Next you can direct your traffic through this route if you wish, as a gateway of last resort:
    a. #ip route 0.0.0.0 0.0.0.0 172.16.X.X
    b. #end
    c. #write
4. Verify by typing in the following:
    a.  #show ip route
    b.  Then verify you see a gateway of last resort listed.


Reference:
https://www.cisco.com/c/en/us/support/docs/ip/routing-information-protocol-rip/16448-default.html

Clearing UCSM error F0933 “named VLAN for vNIC cannot be resolved” errors

1.    First off upon logging onto your UCSM you find this lovely error:

2.    So what is happening here is you done messed up A A Ron! A VLAN was deleted from the global LAN Cloud area and more than likely is still attached to a vNIC template out there. There can be some other causes, but this has been the most common issue I have found with this error. Your UCS has a VLAN it does not know what to do with.
3.    So, from the error screen, go ahead and go to your LAN section in your UCS and go to your vNIC templates section:

4.    Now we can go ahead and select this VLAN we thought was gone, and click on the Delete at the bottom.

5.    Once you delete the VLAN, the errors should go down or start going away. You want to check all your vNIC templates to ensure it has been removed.

Video Issues Upon Logon in Linux

Sometimes you will get login issues such as a blank screen, login loops, and other ways you cannot just logon within Linux distros. The best way to do this is the following:

1. First, when you get to the boot menu and see your Linux distro (s), hit the “e” key to enter edit mode. This will bring up the kernel startup options.
2. You want to find where it stays “quiet splash” screen and then change “quiet splash” to “nomodeset”. This will basically start the system with no graphics drivers which may be causing you video issues upon login.
3. Hold CTRL+X to startup your Linux system.
4. You Should now be able to login to the GUI with no default drivers which may be causing issues.

Reference:

https://wiki.ubuntu.com/Kernel/KernelBootParameters

Edit Alarms in vSphere

1.    First log into your vSphere.
2.    Next, click on the “Home” icon in the top left of your vSphere screen.

3.    Next, click on “Global Inventory Lists” on the dropdown.

4.    Then click on vCenter Servers.

5.    Click on the vCenter server you wish to edit alarms on.

6.    Next, click on the “Monitor” tab.

7.    In the monitor tab, you have three options:
a.    All Issues: This will list all the issues in your vCenter.
b.    Triggered Alarms: This will show any currently triggered alarms in your current vCenter.
c.    Alarm Definitions: This is the tab you want to click on. This tab is all of the definitions of the alarms in vCenter. Definitions are just the configurations/descriptions of your alarms.
8.    Click on the alarm you wish to edit. You will see a menu in the right of your alarm definition screen displaying your selected alarm.
9.    Next, you want to click on the “Edit” button in the top right of the menu showing your alarm definition attributes.

10.    Finally this is the popup you can configure/re-configure your alarms:
a.    General: just allows you to select what will trigger the alarm, virtual machines, clusters, hosts, etc. Items in your vCenter you wish to know about.
b.    Triggers: This will allow you to set the specific alert you wish to trigger. You can have VM Memory usage, CPU usage, power, etc.
c.    Actions: This is where you will put in what actions you wish the system to automatically perform.
11.    You will fill out the appropriate sections to monitor what you wish to keep track of and then click Next to go through the menus and Finish to finalize your edit.

Reference:
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.monitoring.doc/GUID-79AC1262-D701-4BC8-8F8D-F046AE0578CF.html

Upload Firmware into UCSM (GUI)

1.    First off, log into your UCSM system you wish to upload to.
2.    Next, click on the following tabs:
    a.    Equipment
    b.    Firmware Management
    c.    Installed Firmware
3.    Next, under the “Installed Firmware” section, click on “Download Firmware”. This option means the Fabric Interconnects (FIs) themselves will download the software into their flash. Not you downloading the software yourself. It is confusing at first, but remember this is you pushing the firmware to the FIs and they download it.
4.    After you click this, then you can select the file you wish to upload and then click “OK”.
5.    Your software will start uploading into the FI so it can download. If you need to check the progress of the download, click on the “Download Tasks” tab to the right of the “Installed Firmware” tab.
6.    Finally, you can verify your firmware was uploaded/downloaded by selecting the “Packages” tab and you should see your new firmware upload in here.

Reference:
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-manager/GUI-User-Guides/Firmware-Mgmt/4-0/b_UCSM_GUI_Firmware_Management_Guide_4-0/b_UCSM_GUI_Firmware_Management_Guide_4-0_chapter_0100.html#task_0EE4036D9F434685A3CD94EBC0501B66

Terminating UCSM Sessions Manually

1.    Sometimes your UCSM web sessions will get hung up and prevent you from logging in. The following will help you remove the selected sessions you wish to terminate and then allow access again.
2.    First SSH into your UCSM FIs.
3.    Next type in the following:
    a.    #scope security
    b.    #show user-session “local or remote”
    c.    #delete user-session “local or remote” UserName SessionID
        i.    This will be the select username you wish to terminate along with their Session ID. Be CAREFUL, some users might have SSH or the Web interface, or both up. Make sure you select the right Session ID.
    d.    #commit-buffer
4.    Now you should be able to close out all of your web browsers you have the UCSM open in, go back and try to re-log on.

5.    Finally, another way to terminate is you can terminate all Cisco Integrated Management Controller (CIMC) sessions. The above method is preferred since you can specify which one, but continue the following if you are still having issues:
    a.    #scope security
    b.    #show cimc-sessions “local or remote”
    c.    #show cimc-sessions “local or remote” UserName
    d.    #scope security
    e.    #terminate cimc-sessions “local or remote”-user UserName
    f.    This will close cimc sessions. Are you sure? (yes/no): yes
6.    Again, close out of your browsers with the USCM open in and then re-open and try to authenticate again.

Reference:
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-manager/CLI-User-Guides/Admin-Management/3-1/b_Cisco_UCS_Manager_CLI_Administration_Mgmt_Guide_3_1/b_Cisco_UCS_Manager_CLI_Administration_Mgmt_Guide_3_1_chapter_0111.html

Re-issue Certificate for UCSM

1.    You will sometimes have a certificate expire on your UCSM. This will show up as a “Major” error in your UCSM errors/logs. This can be cleared by re-issuing a new certificate within the fabric interconnects.
2.    First, log into the fabric interconnects through SSH.
3.    Once you have logged into the FI, use the following commands to re-issue new certificate:
    a.    #scope security
    b.    #scope keyring default
    c.    #set regenerate yes
    d.    #commit-buffer
        i.    WARNING!: This WILL disconnect your web sessions. Be wary if you have others currently working in the UCSM, for it will disconnect them all.
4.    It can take up to 3-5 minutes to re-generate a new certificate for the UCSM. Give it a few minutes then use the following commands to verify the new key has been created:
    a.    #scope security
    b.    #show keyring detail
    c.    The following should be showing:
        i.    RSA key modules: ModXXXX
        ii.    Trustpoint: XXX
        iii.    Cert Status: Valid (here it should show valid or self-signed, not expired)
5.    You should now be able to log back into your UCSM and see the error cleared.