Аутентификация в FI UCS

Если нативная аутентификация по умолчанию установлена  LDAP и при этом нет доступа к домену, то для входа в CLI нужно использовать

login: ucs-local\admin

в GUI такой проблемы нет, т.к там можно выбрать метод аутентификации

Netapp - Вывод контроллера из режима lockdown

************************************************************
*Default E-Series Contoller Shell Passwords
************************************************************
NetApp Systems:
06.xx CFW and below (VxWorks 5.x): infiniti/infiniti
07.xx and 8.xx: shellUsr/wy3oo&w4 (In some early 7.xx cases this may be shellUsr/infiniti instead)
11.30.x: eos/wy3oo&w4 (for eos shell) and diag/wy3oo&w4 (for dom0/linux shell)
11.40.x: eos/<UI admin password> (for eos shell) and diag/<UI admin password> (for dom0/linux shell)
SPRI Login: spri/SPRIentry

OEM Systems:
Apollo (SUN/Oracle): shellUsr/y2llojp
Mercury (Dell) As of x.03 NVSRAM: DF4m/2> (shell) and supportDell (SPRI)
Catera (IBM) 07.10 and above: shellUsr/wy3oo&w4 (In some cases this may be shellUsr/infiniti
instead)

************************************************************
*Default E-Series Contoller Setting IP addresses
************************************************************
https://E2800_Controller_IP

Controller 1 (port 1): IP Address: 192.168.128.101/24
     (port 2): IP Address: 192.168.129.101/24
Controller 2 (port 1): IP Address: 192.168.128.102/24
     (port 2): IP Address: 192.168.129.102/24

************************************************************
*Global System Reset
************************************************************

Не моё :)

All command should be run shellUsr/wy3oo&w4

Run the following command
-> sysWipe
Warning: This command is extremely destructive.  As such, it should not be used as part of configuration restoration.
If you are NOT planning on restoring the configuration / recovering user data, you may perform sysWipeAllConfigData.
If you ARE planning on restoring the configuration / recovering user data, you may perform bdbmClearPrimaryDatabase
as part of the recovery procedure.
value = 35 = 0x23 = '#'
-> sysWipeAllConfigData
-> sysReboot

#if Controller A is lockdown

Run the following command on both controllers
>lemClearLockdown
>clearHardwareLockdown
>psvClearSodRebootLoopCounter

then hardware unplug controller A and run the following command on ctrl-B
>loadDebug
>cmgrSetAltToFailed
>cmgrSetAltToOptimal
Then Hot-plug controller A

************************************************************
*System Administrator Reset Password
************************************************************
1. Use SPRI Login: spri/SPRIentry and go to point 4
2. Use the shellUsr/wy3oo&w4 and type "spriMenuPwdReset", password should be reseted.

Redundancy change to Grid

Replace  Power Policy  from N+1 to Grid in gui, but if I connect to ssh  I see policy N+1 !

A# connect iom 1
Attaching to FEX 1 ...
To exit type 'exit', to abort type '$.'
Bad terminal type: "dumb". Will assume vt100.
fex-1# show platform software cmcctrl power redundanc
==============================
Last update TS                 : 29672035
Stale TS                 : 29672095
Now                         : 29672059
Cluster master                 : yes
Policy                        : N+1
State                        : ok
Total power available        : 7500
Total power usage        : 746
Power budget requested        : 3320
PSU input line                 : High
-----------
Grid                        : 0
        Active PS        : 0 1 2
        Spare PS        : 3
        Unavailable PS        :
-----------
==============================



Resolution - Need reseat IOM module !!!
A# connect iom 1
Attaching to FEX 1 ...
To exit type 'exit', to abort type '$.'
Bad terminal type: "dumb". Will assume vt100.

fex-1# show platform software cmcctrl power redundanc

==============================
Last update TS                 : 29729758
Stale TS                 : 29729818
Now                         : 29729763
Cluster master                 : yes
Policy                        : Grid
State                        : ok
Total power available        : 10000
Total power usage        : 773
Power budget requested        : 3149
PSU input line                 : High
-----------
Grid                        : 0
        Active PS        : 0 1
        Spare PS        :
        Unavailable PS        :
-----------
-----------
Grid                        : 1
        Active PS        : 2 3
        Spare PS        :
        Unavailable PS        :
-----------
==============================

Upgrade CISCO UCS

Open a Pre-Emptive Support Call

Step 1: Perform a backup of your FI’s and create All Configuration and Full-State backup files.
– Admin State: Enabled
– Type: Full State
Step 2: Disable Call Home
Step 3: Verify the FA failover settings
    3.1 Click on the Admin tab, expand Equipment > Fabric Interconnects. Click the FI node for the fabric interconnect that you want to verify.
    3.2 In the Status area, verify that the Overall Status is operable.
    3.3 If the fields in the High Availability Details area are not displayed, click the Expand icon to the right of the heading.
    3.4 Verify the settigs for the FI’s:
    Ready field – Yes
    State field – Up

Step 4: Check the associated Maintenance Policy
    4.1 Click on the Servers tab, expand Servers > Policies. Expand the organisation for where you want to create the policy. Expand Maintenance Policies and verify that your maintenance policy is in use by the relevant Server Profile Templates.

Step 5: Verify the Status of the IO modules
    5.1 Click on the Equipment tab, expand Equipment > Chassis.
    5.2 Click on the chassis you want to verify for and click the IO Modules tab. For each IO module check that the overall status is Operable

Step 6 Verifying the Status of Servers
    6.1 Click the Equipment tab and click Equipment. Select the Servers Tab and for each server check that the overall status is Ok.
    6.2 Click on Equipment and Chassis > Chassis Number > Servers. Click the Inventory tab and select the Adapters sub-tab. Verify that the adapters are all operational.

Step 7 Check on the Ethernet and Fabric paths (provides a baseline for checking later)
    7.1 Connect to the FI via SSH. You can then connect to the individual FI’s using the connect nxos command. Next run the command to show the active number of ethernet connections. The number of connections can be checked against those once he upgrade has been completed. The fwm command will show the number of MAC addresses connected also.
    UCS-A /fabric-interconnect # connect nxos a
    UCS-A(nxos)# show int br | grep -v down | wc –l
    86
    UCS-A(nxos)# show platform fwm info hw-stm | grep ‘1.’ | wc –l
    80

    7.2 While connected via SSH you can also check the number of active fibre connections.
    UCS-A /fabric-interconnect # connect nxos a
    UCS-A(nxos)# show npv flogi-table
    UCS-A(nxos)# show npv flogi-table | grep fc | wc -l
    3
    Perform the same commands on fabric b.

!!!!!!    7.3 Check the flogi database and the number of servers logged into the fabric.
    UCS-A /fabric-interconnect # connect nxos a
    UCS-A(nxos)# show flogi database
    UCS-A(nxos)# show flogi database | grep fc | wc -l
    8   



Step 8 Check the Available Space on Fabric Interconnect
    If an image download fails, check whether the bootflash on the fabric interconnect or fabric interconnects in the Cisco UCS has sufficient available space.
    Step 8.1 Click on the Equipment tab > expand Equipment > Fabric Interconnects. Click the fabric interconnect on which you want to check the available space. Select the General tab.
    Step 8.2 Expand the Local Storage Information area. and check that the FI bootflash is less than 50%. If not, dlete some old files form the FI and also any old tech support files.

Step 9 Download Software Bundles
    Go to Cisco’s website and download the relevant software. You’ll then need to upload it to the FIs. This is called downloading the package even though you’re uploading to the fabric interconnects. Odd I know but what can you do. Once you’ve downloaded the required files you can then perform the upgrades by activating the new firmware versions.
    Step 9.1 Click the Equipment tab, select the Equipment node. Click on the Firmware Management tab. Click the Installed Firmware tab and select Download Firmware.
    Step 9.2 In the Download Firmware dialog box, click the Local File System radio button in the Location of the Image File field.


Upgrading the Infrastructure Firmware with Auto Install:
Step 10: Install the infrastructure firmware.
    10.1 Click on the Equipment tab, select Equipment and click on Firmware Management tab. Click the Firmware Auto Install tab and in the actions areas click Install Infrastructure Firmware
    10.2 In the Prerequisites I clicked on Ignore All. This was due to some non-critical alerts from the blade servers. Once selected click Next.
    10.3 In the Properties area of the Install Infrastructure Firmware dialog box, enter a description, select the firmware version number and select Upgrade Now. Click Finish.
    10.4 Acknowledge the reboot of the primary fabric interconnect. If you do not acknowledge that reboot, Cisco UCS Manager cannot complete the infrastructure upgrade and the upgrade remains pending indefinitely.
    10.5 On the toolbar, click Pending Activities. In the Pending Activities dialog box, click the User Acknowledged Activities tab. Select Reboot Now.
    10.6 Click OK. UCSM will reboot immediately. You cannot stop this reboot after you click OK.


Upgrading the Server Firmware with Auto Install:
Step 11: Begin the server installation. Click the Equipment tab, select the Equipment node, click the Firmware Management tab and click Firmware Auto Install tab. In the Actions area click Install Server Firmware.
    11.1 On the prerequisites page review the settings. Click Ignore All and click Next.
    11.2 Select the newly uploaded server firmware bundle for the B-Series and click Next.
    11.3 Select the firmware policy you want to update. Make sure that this policy is used by all the Service Profile Templates you need to update.
    11.4 Review the dependency packages and click Next
    11.5 Review the impacted endpoints and check the new version is correct. Click Install.
    11.6 Click Ok on the auto-install confirmation
    11.7 You can check the progress of the upgrade using the FSM tab for each server. Each blade will require a reboot as part of the upgrade. This can be activated by selecting Pending Activites in the taskbar and choosing which blades to reboot based on your business requirements.
    11.8 Once the reboots have completed the server firmware will have completed its upgrade process.


В случае отката необходимо:
For downgrade, you need to select the old running firmware and start the upgrade process. This will install old firmware.