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