if you need to upgrade a cisco UCS “brain”, the procedure exist publically available at cisco but I post here a bit more details after a first experience …
Step 1
Mount the replacement fabric interconnects into either the same rack or an adjacent rack.
Refer to the Cisco UCS 6200 Series Installation Guide for details.
Step 2
Using either the Cisco UCS Manager CLI or GUI, verify the state (subordinate or active) of the fabric interconnects.
See http://www.cisco.com/en/us/docs/unified_computing/ucs/sw/upgrading/from1.4/to2.0/b_upgradingciscoucsfrom1.4to2.0_chapter_0101.html.
Step 3
Back up the software configuration information and the Cisco UCS Manager software.
Step 4
Disable the server ports on the subordinate fabric interconnect.
Step 5
Power down the subordinate fabric interconnect by unplugging it from the power source.
If you are monitoring the upgrade using a KVM session, you may need to reconnect the KVM session when you power down the fabric interconnect.
Step 6
Disconnect the cables from the chassis FEXes or fabric extenders to the subordinate fabric interconnect ports in slot 1 on the old fabric interconnect.
Step 7
Connect these cables into the corresponding ports on slot 1 of one of the new Cisco UCS 6248 UP fabric interconnects, using the connection records to preserve the port mapping and the configured server pinning.
Step 8
Disconnect the L1/L2, M1 management, and console cables on the old fabric interconnect.
The ports for these connections are on the opposite side of the interconnect, so if your cables are just barely long enough to connect two rack-adjacent Cisco UCS 6120 interconnects you will probably need new cables.
Step 9
Connect the M1 management, and console cables to the new Cisco UCS 6248 UP.
Step 10
Connect the L1/L2 cables that were disconnected onto the new Cisco UCS 6248 UP :
- L1 connects to L1
- L2 connects to L2.
Step 11
Disconnect the Ethernet or FC cables from slot 2 of the old fabric interconnect.
Step 12
Connect the Ethernet or FC cables to the corresponding ports in slot 2 of the new Cisco UCS 6248 UP.
Some may go to slot 1, depending on the mappings planned out earlier in the process.
Step 13
Connect the power to the new Cisco UCS 6248 UP, it will automatically boot and run POST tests. If it reboots itself, this is a normal behavior.
IMPORTANT:
Directly connect the console port to a terminal and observe the boot sequence. You should at some point see the Basic System Configuration Dialog, where you will configure the switch as a subordinate interconnect. If you do not see this dialog, you either have different builds of software on your old primary and new subordinate, or the new subordinate has previously been part of a cluster and will need to have all configuration information wiped before it can be added to a cluster as a subordinate. In either case, immediately disconnect the L1 and L2 connections and complete the process bring up as a standalone fabric interconnect, then correct the issue before proceeding further.
We power on the FI after the first cables swap, Server ports are disabled
N5000 BIOS v.3.6.0, Wed 05/09/2012, 03:15 PM
[2J[1;1H[25;78H98[1;1H[25;78H9C[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78H99[1;1H[25;78H99[1;1H[25;78H99[1;1H[25;78H92[1;1H[25;78H99[1;1H[25;78HA0[1;1H[25;78HA2[1;1H[25;78HA3[1;1H[25;78HA0[1;1H[25;78HA2[1;1H[25;78HA3[1;1H[25;78HB2[1;1H[2J[1;1H B2[1;1H[0;37;40m[2J[1;37;40m[1;1HVersion 2.00.1201. Copyright (C) 2009 American Megatrends, Inc. [2J[2JBooting kickstart image: bootflash:/installables/switch/ucs-6100-k9-kickstart.5
.2.3.N2.2.23c.bin....
...............................................................................
..............................................Image verification OK
ÿUsage: init 0123456SsQqAaBbCcUu
INIT: [ 10.665234] I2C - Mezz absent
Starting system POST.....
Executing Mod 1 1 SEEPROM Test:...done (0 seconds)
Executing Mod 1 1 GigE Port Test:....done (32 seconds)
Executing Mod 1 1 PCIE Test:.................done (0 seconds)
Mod 1 1 Post Completed Successfully
POST is completed
can't create lock file /var/lock/mtab~207: No such file or directory (use -n flag to override)
S10mount-ramfs.supnuovaca Mounting /isan 3000m
Mounted /isan
Creating /callhome..
Mounting /callhome..
Creating /callhome done.
Callhome spool file system init done.
nohup: redirecting stderr to stdout
autoneg unmodified, ignoring
autoneg unmodified, ignoring
Checking all filesystems....r. done.
Checking NVRAM block device ... done
The startup-config won't be used until the next reboot.
.
Loading system software
Uncompressing system image: bootflash:/installables/switch/ucs-6100-k9-system.5.2.3.N2.2.23c.bin
Loading plugin 0: core_plugin...
Loading plugin 1: eth_plugin...
Loading plugin 2: fc_plugin...
C
10+1 records in
10+1 records out
8538 bytes (8.5 kB) copied, 4.3137e-05 s, 198 MB/s
ethernet end-host mode on CA
FC end-host mode on CA
n_port virtualizer mode.
---------------------------------------------------------------
INIT: Entering runlevel: 3
touch: cannot touch `/var/lock/s
/isan/bin/muxif_config: fex vlan id: -f,4042
Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
Added VLAN with VID == 4042 to IF -:muxif:-
cp: cannot stat `/isan/plugin_img/fex.bin': No such file or directory
---------------------
enabled fc feature
---------------------
2015 Mar 1 09:21:56 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files begin - clis
2015 Mar 1 09:22:00 %$ VDC-1 %$ Mar 1 09:21:59 %KERN-0-SYSTEM_MSG: [ 10.665234] I2C - Mezz absent - kernel
2015 Mar 1 09:22:06 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files end - clis
2015 Mar 1 09:22:06 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: init begin - clis
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
2015 Mar 1 09:23:09 %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online
System is coming up ... Please wait ...
nohup: appending output to `nohup.out'
2015 Mar 1 09:23:24 switch %$ VDC-1 %$ %USER-2-SYSTEM_MSG: Running in PIO stats mode - carmelusd
We try to join the fabric – but …
---- Basic System Configuration Dialog ----
This setup utility will guide you through the basic configuration of
the system. Only minimal configuration including IP connectivity to
the Fabric interconnect and its clustering mode is performed through these steps.
Type Ctrl-C at any time to abort configuration and reboot system.
To back track or make modifications to already entered values,
complete input till end of section and answer no when prompted
to apply configuration.
Enter the configuration method. (console/gui) ? console
Installer has detected the presence of a peer Fabric interconnect. This Fabric interconnect will be added to the cluster. Continue (y/n) ? y
Enter the admin password of the peer Fabric interconnect:
Connecting to peer Fabric interconnect... done
Retrieving config from peer Fabric interconnect... done
Peer Fabric Interconnect Model is 6100 and different from Local Fabric Interconnect Model 6248 . Cannot trigger the firmware Synchronization
Do you wish to setup this fabric in standalone mode? [hint: Please Remove the cable before selecting 'y'] (y/n): n
Cannot proceed with peer that has a different Image Version. Restarting installer.
We configure the FI as standalone to put same firmware
Enter the configuration method. (console/gui) [console] ? console
Enter the setup mode; setup newly or restore from backup. (setup/restore) ? setup
You have chosen to setup a new Fabric interconnect. Continue? (y/n): y
Enforce strong password? (y/n) [y]: n
Enter the password for "admin":
Confirm the password for "admin":
Is this Fabric interconnect part of a cluster(select 'no' for standalone)? (yes/no) [n]: n
Enter a system name : dc03-ucs
Physical Switch Mgmt0 IP address : 10.41.5.71
Physical Switch Mgmt0 IPv4 netmask : 255.255.255.0
IPv4 address of the default gateway : 10.41.5.1
Configure the DNS Server IP address? (yes/no) [n]: n
Configure the default domain name? (yes/no) [n]: n
Join centralized management environment (UCS Central)? (yes/no) [n]: n
Following configurations will be applied:
Switch Fabric=A
System Name=dc03-ucs
Enforced Strong Password=no
Physical Switch Mgmt0 IP Address=10.41.5.71
Physical Switch Mgmt0 IP Netmask=255.255.255.0
Default Gateway=10.41.5.1
Ipv6 value=0
Apply and save the configuration (select 'no' if you want to re-enter)? (yes/no): yes
Applying configuration. Please wait.
Configuration file - Ok
Cisco UCS 6200 Series Fabric Interconnect
We upgrade the bundle using the web interface
Use the infrastructure workflow, it takes a while … (30 min )
We reboot with correct firmware
Cisco UCS 6200 Series Fabric Interconnect
dc03-ucs-A login: [ 1628.406302] Shutdown Ports..
[ 1628.440678] writing reset reason 9,
INIT:
INIT: Sending processes the TERM signal
Sending all processes the TERM signal...
Sending all processes the KILL signal...
Saving random seed:
Syncing hardware clock to system time WARNING from hwclock: The clock was in 11 minute mode, which normally means that something else, possibly an NTP daemon, has been setting the hardware clock. Setting the clock with hwclock turns off 11 minute mode. See hwclock documentation.
Unmounting file systems: umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
/var/tmp: c
Unmounting file systems (retry): umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
/var/tmp: c
Unmounting file systems (retry): umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
/var/tmp: c
umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
mount: you must specify the filesystem type
mount: /var not mounted already, or bad option
Please stand by while rebooting the system...
[ 1659.685775] Resetting board
N5000 BIOS v.3.6.0, Wed 05/09/2012, 03:15 PM
[2J[1;1H[25;78H98[1;1H[25;78H9C[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78H99[1;1H[25;78H99[1;1H[25;78H99[1;1H[25;78H92[1;1H[25;78H99[1;1H[25;78HA0[1;1H[25;78HA2[1;1H[25;78HA3[1;1H[25;78HA0[1;1H[25;78HA2[1;1H[25;78HA3[1;1H[25;78HB2[1;1H[2J[1;1H B2[1;1H[0;37;40m[2J[1;37;40m[1;1HVersion 2.00.1201. Copyright (C) 2009 American Megatrends, Inc. [2J[2JBooting kickstart image: bootflash:/installables/switch/ucs-6100-k9-kickstart.5
.2.3.N2.2.23d.bin....
...............................................................................
..............................................Image verification OK
ÿUsage: init 0123456SsQqAaBbCcUu
INIT: [ 10.688287] I2C - Mezz absent
Starting system POST.....
Executing Mod 1 1 SEEPROM Test:...done (0 seconds)
Executing Mod 1 1 GigE Port Test:....done (32 seconds)
Executing Mod 1 1 PCIE Test:.................done (0 seconds)
Mod 1 1 Post Completed Successfully
POST is completed
can't create lock file /var/lock/mtab~207: No such file or directory (use -n flag to override)
S10mount-ramfs.supnuovaca Mounting /isan 3000m
Mounted /isan
Creating /callhome..
Mounting /callhome..
Creating /callhome done.
Callhome spool file system init done.
nohup: redirecting stderr to stdout
autoneg unmodified, ignoring
autoneg unmodified, ignoring
Checking all filesystems..... done.
Checking NVRAM block device ... done
The startup-config won't be used until the next reboot.
.
Loading system software
Uncompressing system image: bootflash:/installables/switch/ucs-6100-k9-system.5.2.3.N2.2.23d.bin
Loading plugin 0: core_plugin...
Loading plugin 1: eth_plugin...
Loading plugin 2: fc_plugin...
C
10+1 records in
10+1 records out
8538 bytes (8.5 kB) copied, 5.0374e-05 s, 169 MB/s
ethernet end-host mode on CA
FC end-host mode on CA
n_port virtualizer mode.
---------------------------------------------------------------
INIT: Entering runlevel: 3
touch: cannot touch `/var/lock/subsys/n
/isan/bin/muxif_config: fex vlan id: -f,4042
Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
Added VLAN with VID == 4042 to IF -:muxif:-
cp: cannot stat `/isan/plugin_img/fex.bin': No such file or directory
---------------------
enabled fc feature
---------------------
2015 Mar 1 09:50:20 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files begin - clis
2015 Mar 1 09:50:23 %$ VDC-1 %$ Mar 1 09:50:23 %KERN-0-SYSTEM_MSG: [ 10.688287] I2C - Mezz absent - kernel
2015 Mar 1 09:50:30 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files end - clis
2015 Mar 1 09:50:30 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: init begin - clis
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
2015 Mar 1 09:51:41 %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online
System is coming up ... Please wait ...
2015 Mar 1 09:51:52 dc03-ucs-A %$ VDC-1 %$ %USER-2-SYSTEM_MSG: Running in PIO stats mode - carmelusd
We reset the configuration to factory to permit synchronisation
Cisco UCS 6200 Series Fabric Interconnect
dc03-ucs-A login: admin
Password:
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2009, Cisco Systems, Inc. All rights reserved.
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
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
[Kdc03-ucs-A# connect local-mgmt
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2009, Cisco Systems, Inc. All rights reserved.
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
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
dc03-ucs-A(local-mgmt)# erase config
All UCS configurations will be erased and system will reboot. Are you sure? (yes/no):yes
Removing all the configuration. Please wait....
/bin/rm: cannot remove directory `/bootflash/sysdebug//tftpd_logs': Device or resource busy
sudo: cannot get working directory
sudo: cannot get working directory
Configurations are cleaned up. Rebooting....
[ 408.459209] Shutdown Ports..
[ 408.493606] writing reset reason 9,
Broadcast message from root (ttyS0) (Sun Mar 1 09:55:24 2015):
Step 14 (Optional)
- Remap Cisco UCS 6100 fabric interconnect FC ports 2/1 to 2/4 on a N10-E0440 expansion module or any slot 3 ports onto the new fabric interconnect expansion module
- Use Cisco UCS Manager to delete the ports on the subordinate fabric interconnect that you will need to move within the configuration.
- For each port you have just deleted, create new ports on either slot 1 or slot 2. These ports must use the same port type definitions as the old ports, but will use different port numbers.
- For recently moved Ethernet server ports, reconfigure the associated service profile to use the new port number for the appropriate LAN pin group.
- For recently moved uplink Ethernet ports, reconfigure the port channel settings to use the new ports.
- For recently moved uplink FC ports, reconfigure the associated service profile SAN pin group to use the new ports.
- Re-acknowledge chassis for blade servers and fabric extender for rack servers.
- This will be disruptive to traffic, but is necessary in this specific scenario.
If you use SAN pingroup, this can be avoided
Step 15
The new subordinate fabric interconnect will automatically synchronize the configuration and database/state information from the primary fabric interconnect. Synchronization between primary and subordinate fabric interconnects can take several minutes. You may see an error message that will persist until the server ports are enabled. The port configuration is copied from the subordinate switch to the new hardware.
We replay the setup to join the existing FI
INIT: Sending processes the TERSending all processes the TERM signal...
Sending all processes the KILL signal...
Saving random seed:
Syncing hardware clock to system time WARNING from hwclock: The clock was in 11 minute mode, which normally means that something else, possibly an NTP daemon, has been setting the hardware clock. Setting the clock with hwclock turns off 11 minute mode. See hwclock documentation.
Unmounting file systems: umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
/var/tmp: c
Unmounting file systems (retry): umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
/var/tmp: c
Unmounting file systems (retry): umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
/var/tmp: c
umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
mount: you must specify the filesystem type
mount: /var not mounted already, or bad option
Please stand by while rebooting the system...
[ 437.545853] Resetting board
N5000 BIOS v.3.6.0, Wed 05/09/2012, 03:15 PM
[2J[1;1H[25;78H98[1;1H[25;78H9C[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78H99[1;1H[25;78H99[1;1H[25;78H99[1;1H[25;78H92[1;1H[25;78H99[1;1H[25;78HA0[1;1H[25;78HA2[1;1H[25;78HA3[1;1H[25;78HA0[1;1H[25;78HA2[1;1H[25;78HA3[1;1H[25;78HB2[1;1H[2J[1;1H B2[1;1H[0;37;40m[2J[1;37;40m[1;1HVersion 2.00.1201. Copyright (C) 2009 American Megatrends, Inc. [2J[2JBooting kickstart image: bootflash:/installables/switch/ucs-6100-k9-kickstart.5
.2.3.N2.2.23d.bin....
...............................................................................
..............................................Image verification OK
ÿUsage: init 0123456SsQqAaBbCcUu
INIT: [ 10.655176] I2C - Mezz absent
Starting system POST.....
Executing Mod 1 1 SEEPROM Test:...done (0 seconds)
Executing Mod 1 1 GigE Port Test:...
.ing all filesystems.....rr done.
Checking NVRAM block device ... done
The startup-config won't be used until the next reboot.
.
Loading system software
done (32 seconds)
Executing Mod 1 1 PCIE Test:.................done (0 seconds)
Mod 1 1 Post Completed Successfully
POST is completed
can't create lock file /var/lock/mtab~207: No such file or directory (use -n flag to override)
S10mount-ramfs.supnuovaca Mounting /isan 3000m
Mounted /isan
Creating /callhome..
Mounting /callhome..
Creating /callhome done.
Callhome spool file system init done.
nohup: redirecting stderr to stdout
autoneg unmodified, ignoring
autoneg unmodified, ignoring
CheckUncompressing system image: bootflash:/installables/switch/ucs-6100-k9-system.5.2.3.N2.2.23d.bin
Loading plugin 0: core_plugin...
Loading plugin 1: eth_plugin...
Loading plugin 2: fc_plugin...
C
10+1 records in
10+1 records out
8538 bytes (8.5 kB) copied, 4.4848e-05 s, 190 MB/s
ethernet end-host mode on CA
FC end-host mode on CA
n_port virtualizer mode.
---------------------------------------------------------------
INIT: Entering runlevel: 3
touch: cannot touch `/var/lock/subsys/n
/isan/bin/muxif_config: fex vlan id: -f,4042
Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
Added VLAN with VID == 4042 to IF -:muxif:-
cp: cannot stat `/isan/plugin_img/fex.bin': No such file or directory
---------------------
enabled fc feature
---------------------
2015 Mar 1 09:58:29 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files begin - clis
2015 Mar 1 09:58:33 %$ VDC-1 %$ Mar 1 09:58:32 %KERN-0-SYSTEM_MSG: [ 10.655176] I2C - Mezz absent - kernel
2015 Mar 1 09:58:39 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files end - clis
2015 Mar 1 09:58:39 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: init begin - clis
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
2015 Mar 1 09:59:42 %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online
nohup: appending output to `nohup.out'
2015 Mar 1 09:59:47 switch %$ VDC-1 %$ %USER-2-SYSTEM_MSG: Running in PIO stats mode - carmelusd
2015 Mar 1 10:00:02 switch %$ VDC-1 %$ %USER-2-SYSTEM_MSG: Load time of /isan/etc/routing-sw/cli/if_manager.cli__: 699162ms - ascii_cfg_server
---- Basic System Configuration Dialog ----
This setup utility will guide you through the basic configuration of
the system. Only minimal configuration including IP connectivity to
the Fabric interconnect and its clustering mode is performed through these steps.
Type Ctrl-C at any time to abort configuration and reboot system.
To back track or make modifications to already entered values,
complete input till end of section and answer no when prompted
to apply configuration.
Enter the configuration method. (console/gui) ? console
Installer has detected the presence of a peer Fabric interconnect. This Fabric interconnect will be added to the cluster. Continue (y/n) ? y
Enter the admin password of the peer Fabric interconnect:
Connecting to peer Fabric interconnect... done
Retrieving config from peer Fabric interconnect... done
Peer Fabric interconnect Mgmt0 IPv4 Address: 10.41.5.72
Peer Fabric interconnect Mgmt0 IPv4 Netmask: 255.255.255.0
Cluster IPv4 address : 10.41.5.70
Peer FI is IPv4 Cluster enabled. Please Provide Local Fabric Interconnect Mgmt0 IPv4 Address
Physical Switch Mgmt0 IP address : 10.41.5.71
Apply and save the configuration (select 'no' if you want to re-enter)? (yes/no): yes
Applying configuration. Please wait.
Configuration file - Ok
After sync we reboot
Cisco UCS 6200 Series Fabric Interconnect
DC03-UCSFI-A login: [ 791.089211] Shutdown Ports..
[ 791.123573] writing reset reason 9,
INIT: Sending all processes the TERM signal...
Sending all processes the KILL signal...
Saving random seed:
Syncing hardware clock to system time WARNING from hwclock: The clock was in 11 minute mode, which normally means that something else, possibly an NTP daemon, has been setting the hardware clock. Setting the clock with hwclock turns off 11 minute mode. See hwclock documentation.
Unmounting file systems: umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
/var/tmp: c
Unmounting file systems (retry): umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
/var/tmp: c
Unmounting file systems (retry): umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
/var/tmp: c
umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
mount: you must specify the filesystem type
mount: /var not mounted already, or bad option
Please stand by while rebooting the system...
[ 821.626515] Resetting board
N5000 BIOS v.3.6.0, Wed 05/09/2012, 03:15 PM
[2J[1;1H[25;78H98[1;1H[25;78H9C[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78H99[1;1H[25;78H99[1;1H[25;78H99[1;1H[25;78H92[1;1H[25;78H99[1;1H[25;78HA0[1;1H[25;78HA2[1;1H[25;78HA3[1;1H[25;78HA0[1;1H[25;78HA2[1;1H[25;78HA3[1;1H[25;78HB2[1;1H[2J[1;1H B2[1;1H[0;37;40m[2J[1;37;40m[1;1HVersion 2.00.1201. Copyright (C) 2009 American Megatrends, Inc. [2J[2JBooting kickstart image: bootflash:/installables/switch/ucs-6100-k9-kickstart.5
.2.3.N2.2.23d.bin....
...............................................................................
..............................................Image verification OK
ÿUsage: init 0123456SsQqAaBbCcUu
INIT: [ 10.640506] I2C - Mezz absent
Starting system POST.....
Executing Mod 1 1 SEEPROM Test:...done (0 seconds)
Executing Mod 1 1 GigE Port Test:....done (32 seconds)
Executing Mod 1 1 PCIE Test:.................done (0 seconds)
Mod 1 1 Post Completed Successfully
POST is completed
can't create lock file /var/lock/mtab~207: No such file or directory (use -n flag to override)
S10mount-ramfs.supnuovaca Mounting /isan 3000m
Mounted /isan
Creating /callhome..
Mounting /callhome..
Creating /callhome done.
Callhome spool file system init done.
nohup: redirecting stderr to stdout
autoneg unmodified, ignoring
autoneg unmodified, ignoring
Checking all filesystems..... done.
Checking NVRAM block device ... done
The startup-config won't be used until the next reboot.
.
Loading system software
Uncompressing system image: bootflash:/installables/switch/ucs-6100-k9-system.5.2.3.N2.2.23d.bin
Loading plugin 0: core_plugin...
Loading plugin 1: eth_plugin...
Loading plugin 2: fc_plugin...
C
10+1 records in
10+1 records out
8538 bytes (8.5 kB) copied, 4.5856e-05 s, 186 MB/s
ethernet end-host mode on CA
FC end-host mode on CA
n_port virtualizer mode.
---------------------------------------------------------------
INIT: Entering runlevel: 3
touch: cannot touch `/var/lock/subsys/netfs': No
/isan/bin/muxif_config: fex vlan id: -f,4042
Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
Added VLAN with VID == 4042 to IF -:muxif:-
cp: cannot stat `/isan/plugin_img/fex.bin': No such file or directory
[cluster]
---------------------
enabled fc feature
---------------------
2015 Mar 1 10:13:12 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files begin - clis
2015 Mar 1 10:13:16 %$ VDC-1 %$ Mar 1 10:13:15 %KERN-0-SYSTEM_MSG: [ 10.640506] I2C - Mezz absent - kernel
2015 Mar 1 10:13:22 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files end - clis
2015 Mar 1 10:13:22 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: init begin - clis
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
2015 Mar 1 10:14:32 switch %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online
2015 Mar 1 10:14:46 DC03-UCSFI-A %$ VDC-1 %$ %USER-2-SYSTEM_MSG: Running in PIO stats mode - carmelusd
Cisco UCS 6200 Series Fabric Interconnect
DC03-UCSFI-A login:
Step 16
Verify that the data path is ready. See http://www.cisco.com/en/us/docs/unified_computing/ucs/sw/upgrading/from1.4/to2.0/b_ upgradingciscoucsfrom1.4to2.0_chapter_0100.html. Make sure all faults are resolved before proceeding.
- Verify and if necessary reconfigure the SAN pin group for FC ports in the associated service profile.
- Verify and if necessary reconfigure the LAN pin group for Ethernet ports in the associated service profile.
- Verify and if necessary reconfigure the port channel for uplink Ethernet ports.
Step 17
Enable the server ports that had been disabled in Step 4.
- If you have changed port mappings, you may need to re-acknowledge the chassis or rack server connected to the subordinate fabric interconnect.
- Verify and if necessary reconfigure Ethernet ports as server ports.
Step 18
Promote the subordinate fabric interconnect to active, and repeat the process on the second Cisco UCS 6248 UP. Cable the second new fabric interconnect identically to the first, and allow the reconfiguration done to be applied to the second new fabric interconnect as well. See http://www.cisco.com/en/us/docs/unified_computing/ucs/sw/upgrading/from1.4/to2.0/b_ upgradingciscoucsfrom1.4to2.0_chapter_0100.html
First FI is done, we can validate the setup on UCS manager and start rebuilding the second FI
In this case we have the same hardware so we don’t need to preupgrade the FI, since version 2.2 it is automatic
We disable server ports, swap cable and power on the FI
^@
.done (32 seconds)
Executing Mod 1 1 PCIE Test:.................done (0 seconds)
Mod 1 1 Post Completed Successfully
POST is completed
can't create lock file /var/lock/mtab~207: No such file or directory (use -n flag to override)
S10mount-ramfs.supnuovaca Mounting /isan 3000m
Mounted /isan
Creating /callhome..
Mounting /callhome..
Creating /callhome done.
Callhome spool file system init done.
nohup: redirecting stderr to stdout
autoneg unmodified, ignoring
autoneg unmodified, ignoring
Checking all filesystems....r. done.
Checking NVRAM block device ... done
The startup-config won't be used until the next reboot.
.
Loading system software
Uncompressing system image: bootflash:/installables/switch/ucs-6100-k9-system.5.2.3.N2.2.23c.bin
Loading plugin 0: core_plugin...
Loading plugin 1: eth_plugin...
Loading plugin 2: fc_plugin...
C
10+1 records in
10+1 records out
8538 bytes (8.5 kB) copied, 4.5662e-05 s, 187 MB/s
ethernet end-host mode on CA
FC end-host mode on CA
n_port virtualizer mode.
---------------------------------------------------------------
INIT: Entering runlevel: 3
touch: cannot touch `/var/lock/subsys/netfs': No
/isan/bin/muxif_config: fex vlan id: -f,4042
Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
Added VLAN with VID == 4042 to IF -:muxif:-
cp: cannot stat `/isan/plugin_img/fex.bin': No such file or directory
---------------------
enabled fc feature
---------------------
2015 Mar 1 10:52:11 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files begin - clis
2015 Mar 1 10:52:15 %$ VDC-1 %$ Mar 1 10:52:14 %KERN-0-SYSTEM_MSG: [ 10.647153] I2C - Mezz absent - kernel
2015 Mar 1 10:52:21 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files end - clis
2015 Mar 1 10:52:21 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: init begin - clis
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
2015 Mar 1 10:53:25 %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online
2015 Mar 1 10:53:28 switch %$ VDC-1 %$ %USER-2-SYSTEM_MSG: Running in PIO stats mode - carmelusd
System is coming up ... Please wait ...
nohup: appending output to `nohup.out'
We merge the FI
---- Basic System Configuration Dialog ----
This setup utility will guide you through the basic configuration of
the system. Only minimal configuration including IP connectivity to
the Fabric interconnect and its clustering mode is performed through these steps.
Type Ctrl-C at any time to abort configuration and reboot system.
To back track or make modifications to already entered values,
complete input till end of section and answer no when prompted
to apply configuration.
Enter the configuration method. (console/gui) ? console
Installer has detected the presence of a peer Fabric interconnect. This Fabric interconnect will be added to the cluster. Continue (y/n) ? y
Enter the admin password of the peer Fabric interconnect:
Connecting to peer Fabric interconnect... done
Retrieving config from peer Fabric interconnect... done
Installer has determined that the peer Fabric Interconnect is running a different firmware version than the local Fabric. Cannot join cluster.
Local Fabric Interconnect
UCSM version : 2.2(3c)
Kernel version : 5.2(3)N2(2.23c)
System version : 5.2(3)N2(2.23c)
local_model_no : 6248
Peer Fabric Interconnect
UCSM version : 2.2(3d)
Kernel version : 5.2(3)N2(2.23d)
System version : 5.2(3)N2(2.23d)
peer_model_no : 6248
As we have same hardware but not same firmware we are proposed the automatic update
Do you wish to update firmware on this Fabric Interconnect to the Peer's version? (y/n): y
[1;31m[1mUpdating firmware of Fabric Interconnect....... [ Please don't press Ctrl+c while updating firmware ][0m
Updating images
Please wait for firmware update to complete....
[1;31m[1m Checking the Compatibility of new Firmware..... [ Please don't Press ctrl+c ]. [0m
Verifying image bootflash:/installables/switch/ucs-6100-k9-kickstart.5.2.3.N2.2.23d.bin for boot variable "kickstart".
[# ] 0%[####################] 100% -- SUCCESS
Verifying image bootflash:/installables/switch/ucs-6100-k9-system.5.2.3.N2.2.23d.bin for boot variable "system".
[# ] 0%[####################] 100% -- SUCCESS
Verifying image type.
[# ] 0%[##### ] 20%[####### ] 30%[######### ] 40%[########### ] 50%[########### ] 50%[########### ] 50%[################### ] 90%[####################] 100%[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/installables/switch/ucs-6100-k9-system.5.2.3.N2.2.23d.bin.
[# ] 0%[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/installables/switch/ucs-6100-k9-kickstart.5.2.3.N2.2.23d.bin.
[# ] 0%[####################] 100% -- SUCCESS
Extracting "bios" version from image bootflash:/installables/switch/ucs-6100-k9-system.5.2.3.N2.2.23d.bin.
[# ] 0%[####################] 100% -- SUCCESS
Performing module support checks.
[####################] 100% -- SUCCESS
Notifying services about system upgrade.
[####################] 100% -- SUCCESS
Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes disruptive reset Incompatible image
Images will be upgraded according to following table:
Module Image Running-Version New-Version Upg-Required
------ ---------- ---------------------- ---------------------- ------------
1 system 5.2(3)N2(2.23c) 5.2(3)N2(2.23d) yes
1 kickstart 5.2(3)N2(2.23c) 5.2(3)N2(2.23d) yes
1 bios v3.6.0(05/09/2012) v3.6.0(05/09/2012) no
1 SFP-uC v1.1.0.0 v1.0.0.0 no
1 power-seq v3.0 v3.0 no
3 power-seq v2.0 v2.0 no
1 uC v1.2.0.1 v1.2.0.1 no
Switch will be reloaded for disruptive upgrade.
Install is in progress, please wait.
Performing runtime checks.
[####################] 100% -- SUCCESS
Setting boot variables.
[# ] 0%[####################] 100% -- SUCCESS
Performing configuration copy.
[# ] 0%[### ] 10%[#### ] 15%[##### ] 20%[###### ] 25%[####### ] 30%[######## ] 35%[######### ] 40%[########## ] 45%[########### ] 50%[############# ] 60%[############## ] 65%[############### ] 70%[################ ] 75%[################# ] 80%[################## ] 85%[################### ] 90%[####################] 95%[####################] 100%[####################] 100% -- SUCCESS
Install has been successful.
[1;31m[1m Firmware Updation Successfully Completed. Please wait to enter the IP address [0m
Peer Fabric interconnect Mgmt0 IPv4 Address: 10.41.5.71
Peer Fabric interconnect Mgmt0 IPv4 Netmask: 255.255.255.0
Cluster IPv4 address : 10.41.5.70
Peer FI is IPv4 Cluster enabled. Please Provide Local Fabric Interconnect Mgmt0 IPv4 Address
Physical Switch Mgmt0 IP address : 10.41.5.72
Apply and save the configuration (select 'no' if you want to re-enter)? (yes/no): yes
Applying configuration. Please wait.
Configuration file - Ok
FI will now reboot after which you can access the switch.
WARNING: There is unsaved configuration!!!
WARNING: This command will reboot the system
2015 Mar 1 11:03:39 DC03-UCSFI-B %$ VDC-1 %$ %PFMA-2-PFM_SYSTEM_RESET: Manual system restart from Command Line Interface
[ 801.579621] Shutdown Ports..
[ 801.614014] writing reset reason 9,
2015 Mar 1 11:03:39 DC03-UCSFI-B %$ VDC-1 %$ Mar 1 11:03:39 %KERN-0-SYSTEM_MSG: [ 801.579621] Shutdown Ports.. - kernel
2015 Mar 1 11:03:39 DC03-UCSFI-B %$ VDC-1 %$ Mar 1 11:03:39 %KERN-0-SYSTEM_MSG: [ 801.614014] writing reset reason 9, - kernel
INIT: Sending all processes the TERM signal...
Sending all processes the KILL signal...
Saving random seed:
Syncing hardware clock to system time WARNING from hwclock: The clock was in 11 minute mode, which normally means that something else, possibly an NTP daemon, has been setting the hardware clock. Setting the clock with hwclock turns off 11 minute mode. See hwclock documentation.
Unmounting file systems: umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
/var/tmp: c
Unmounting file systems (retry): umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
/var/tmp: c
Unmounting file systems (retry): umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
/var/tmp: c
umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
mount: you must specify the filesystem type
mount: /var not mounted already, or bad option
Please stand by while rebooting the system...
[ 835.988253] Resetting board
N5000 BIOS v.3.6.0, Wed 05/09/2012, 03:15 PM
[2J[1;1H[25;78H98[1;1H[25;78H9C[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78HB4[1;1H[25;78H99[1;1H[25;78H99[1;1H[25;78H99[1;1H[25;78H92[1;1H[25;78H99[1;1H[25;78HA0[1;1H[25;78HA2[1;1H[25;78HA3[1;1H[25;78HA0[1;1H[25;78HA2[1;1H[25;78HA3[1;1H[25;78HB2[1;1H[2J[1;1H B2[1;1H[0;37;40m[2J[1;37;40m[1;1HVersion 2.00.1201. Copyright (C) 2009 American Megatrends, Inc. [2J[2JBooting kickstart image: bootflash:/installables/switch/ucs-6100-k9-kickstart.5
.2.3.N2.2.23d.bin....
...............................................................................
..............................................Image verification OK
ÿUsage: init 0123456SsQqAaBbCcUu
INIT: [ 10.633654] I2C - Mezz absent
Starting system POST.....
Executing Mod 1 1 SEEPROM Test:...done (0 seconds)
Executing Mod 1 1 GigE Port Test:....done (32 seconds)
Executing Mod 1 1 PCIE Test:.................done (0 seconds)
Mod 1 1 Post Completed Successfully
POST is completed
can't create lock file /var/lock/mtab~207: No such file or directory (use -n flag to override)
S10mount-ramfs.supnuovaca Mounting /isan 3000m
Mounted /isan
Creating /callhome..
Mounting /callhome..
Creating /callhome done.
Callhome spool file system init done.
nohup: redirecting stderr to stdout
autoneg unmodified, ignoring
autoneg unmodified, ignoring
Checking all filesystems..... done.
Checking NVRAM block device ... done
The startup-config won't be used until the next reboot.
.
Loading system software
Uncompressing system image: bootflash:/installables/switch/ucs-6100-k9-system.5.2.3.N2.2.23d.bin
Loading plugin 0: core_plugin...
Loading plugin 1: eth_plugin...
Loading plugin 2: fc_plugin...
C
10+1 records in
10+1 records out
8538 bytes (8.5 kB) copied, 4.5178e-05 s, 189 MB/s
ethernet end-host mode on CA
FC end-host mode on CA
n_port virtualizer mode.
---------------------------------------------------------------
INIT: Entering runlevel: 3
touch: cannot touch `/var/lock/subsys/netfs': No
/isan/bin/muxif_config: fex vlan id: -f,4042
Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
Added VLAN with VID == 4042 to IF -:muxif:-
cp: cannot stat `/isan/plugin_img/fex.bin': No such file or directory
[cluster]
---------------------
enabled fc feature
---------------------
2015 Mar 1 11:07:09 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files begin - clis
2015 Mar 1 11:07:12 %$ VDC-1 %$ Mar 1 11:07:11 %KERN-0-SYSTEM_MSG: [ 10.633654] I2C - Mezz absent - kernel
2015 Mar 1 11:07:18 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: loading cmd files end - clis
2015 Mar 1 11:07:18 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: CLIS: init begin - clis
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
2015 Mar 1 11:08:26 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: Running in PIO stats mode - carmelusd
2015 Mar 1 11:08:27 %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online
System is coming up ... Please wait ...
Second FI is alive, we can go to UCS manager to validate setup
Cisco UCS 6200 Series Fabric Interconnect
DC03-UCSFI-B login:
We need to replay step 14 to 18 to validate all
NB all VM running on our ESX were still in production during all the time, we have “some” messages about redundancy lost …