APIC firmware upgrade failure?

[JCDM7]

Hi,

So, recently i tried to upgrade an APIC-server-M2 firmware with the recommended HUU iso acoording to the version of ACI software: specificly i tried to upgrade from 2.0(3i) to 4.1(2b) of firmware and ACI 4.2(1j) as specified in the release notes.

However after the upgrade of the firmware ACI won't start again, it gets stuck in: "Starting terminate Plymouth Boot Screen..."

Since is an APIC in a lab enviroment i tried to reinstall the ACI software as usual (KVM mapped .iso) but the installation gets stuck in the same place: "Starting terminate Plymouth Boot Screen", and when i show the stats on the KVM to see the transfer of the .iso it gets stuck about 150-600 MB.

I have tried to reinstall the same version of ACI it used to have and the suggested release with the same result.

Did the same thing happened to someone before?

Thanks.

[Robert Burns]

Boot the APIC and break into the BIOS "F2".  Check the status of the TPM.  Ensure its not "Disabled".  If it is, enable it and try again.

Robert

[JCDM7]

Hi Robert.

I've checked and the TPM status was "Enable".

I tried to disable it and enable it back but no changes in the ACI software installation.

[kristjankristinsson]

Did you check the upgrade paths?

Also, the waiting for plymouth, did you do the KVM mounted console? Try to mount the ISO from CIMC and use SOL as explained in Cisco APIC Installation and ACI Upgrade and Downgrade Guide - Installing or Recovering Cisco APIC Images [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco - see if that works better.

Procedure from link:

Step 1	Obtain the relevant Cisco APIC .iso image from CCO.
Step 2	Copy the .iso image to the HTTP server.
Step 3	Access the KVM console: Open the Cisco Integrated Management Controller (CIMC) GUI for the controller. From the CIMC GUI, choose Server > Summary > Launch KVM, then select either Java based KVM or HTML based KVM to access the KVM console. We recommend using the Java based KVM option whenever possible, because it is a more reliable option for larger-sized files.
Step 4	Access the Serial over LAN (SOL) console: From a terminal window, log in to the CIMC console: # ssh admin@cimc_ip Where cimc_ip is the CIMC IP address. For example: # ssh admin@192.0.2.1 admin@192.0.2.1's password: system# Change the scope to virtual media: system# scope vmedia system /vmedia # Map the .iso image to the HTTP server: system /vmedia # map-www volume_name http://http_server_ip_and_path iso_file_name Where: volume_name is the name of the volume. http_server_ip_and_path is the IP address of the HTTP server and the path to the .iso file location. iso_filename is the name of the .iso file. Note that there is a space between the http_server_ip_and_path and the iso_filename. For example: system /vmedia # map-www apic http://198.51.100.1/home/images/ aci-apic-dk9.4.0.3d.iso Server username: Check the mapping status: system /vmedia # show mappings detail The Map-Status should be shown as OK. Connect to SOL to monitor the installation process: system /vmedia # connect host
Step 5	From the KVM console: Choose Power > Power Cycle System (cold boot) to power cycle the controller.
Step 6	From the SOL console: Watch the screen during the boot process and prepare to press F6 at the appropriate moment to enter the boot selection menu. You should first see the following messages as the boot process begins: Cisco Systems, Inc. Configuring and testing memory.. Configuring platform hardware... ... System bootup messages continue to appear, until the point where you should see the following screen: ... Press <F2> Setup, <F6> Boot Menu, <F7> Diagnostics, <F8> Cisco IMC COnfiguration, <F12> Network Boot
Step 7	From the SOL console: When you see the message above, press F6 to enter the boot selection menu. You should see Entering boot selection menu... if you were able to press F6 at the appropriate moment. If you miss your opportunity and were not able to press F6 at the appropriate moment, go back to Step 5 to power cycle the controller and repeat the process until you are able to press F6 to enter the boot selection menu.
Step 8	From the SOL console: At the boot selection menu, select the Cisco CIMC-Mapped vDVD1.22 option as the one-time boot device. /------------------------------------\ | Please select boot device: | |------------------------------------| | (Bus 05 Dev 00)PCI RAID Adapter | | UNIGEN PHF16H0CM1-DTE PMAP | | Cisco vKVM-Mapped vHDD1.22 | | Cisco CIMC-Mapped vHDD1.22 | | Cisco vKVM-Mapped vDVD1.22 | | Cisco CIMC-Mapped vDVD1.22 | | Cisco vKVM-Mapped vFDD1.22 | | UEFI: Built-in EFI Shell | | IBA GE Slot 0100 v1585 | | IBA GE Slot 0101 v1585 | | Enter Setup | |------------------------------------| | ^ and v to move selection | | ENTER to select boot device | | ESC to boot using defaults | \------------------------------------/ You might also have to enter the BIOS password. The default password is password.
Step 9	From the SOL console: Enter the following: Determine if you want to enter the ISO URL to speed up the installation process. During the boot-up process, you might see the following message: To speed up the install, enter iso url in next ten minutes: You have two options at this stage: Enter the ISO URL: This option will make the installation process go faster. Following is an example HTTP URL that you might enter here: http://10.75.61.1/aci-apic-dk9.4.2.1j.iso If you choose this option, you will be asked to provide the protocol type, as shown in the following example: ? http://10.75.61.1/aci-apic-dk9.4.2.1j.iso ++ awk -F '/|:' '{print $4}' + urlip=10.75.61.1 + '[' -z http://10.75.61.1/aci-apic-dk9.4.2.1j.iso ']' + '[' -z 10.75.61.1 ']' + break + '[' -n http://10.75.61.1/aci-apic-dk9.4.2.1j.iso ']' + set +e + configured=0 + '[' 0 -eq 0 ']' + echo 'Configuring network interface' Configuring network interface + echo 'type static, dhcp, bash for a shell to configure networking, or url to re-enter the url: ' Choose the appropriate protocol type: static: If you choose this option, you will be asked to enter the interface name, management IP address and gateway. Following is an example of how to find the correct management interface: ? static + case $ntype in + configure_static + echo 'Available interfaces' Available interfaces + ls -l /sys/class/net total 0 lrwxrwxrwx. 1 root root 0 Sep 26 16:04 enp11s0 -> ../../devices/pci0000:00/0000:00:03.0/0000:06:00.0/0000:07:01.0/0000:09:00.0/0000:0a:00.0/0000:0b:00.0/net/enp11s0 lrwxrwxrwx. 1 root root 0 Sep 26 16:04 enp12s0 -> ../../devices/pci0000:00/0000:00:03.0/0000:06:00.0/0000:07:01.0/0000:09:00.0/0000:0a:01.0/0000:0c:00.0/net/enp12s0 lrwxrwxrwx. 1 root root 0 Sep 26 16:04 enp1s0f0 -> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/net/enp1s0f0 lrwxrwxrwx. 1 root root 0 Sep 26 16:04 enp1s0f1 -> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.1/net/enp1s0f1 lrwxrwxrwx. 1 root root 0 Sep 26 16:04 lo -> ../../devices/virtual/net/lo + read -p 'Interface to configure: ' interface Interface to configure: [anaconda] 1:main* 2:shell 3:log 4:storage-lo> Switch tab: Alt+Tab | Help: F1 In the output above, the network interface with the shorter pci numbering corresponds to the two Out-Of-Band management interfaces: enp1s0f0 (eth1-1) and enp1s0f1 (eth1-2). If both interfaces are cabled as they should be, you can select either of them. However, if only one interface has a cable connected to it, you must choose the interface that corresponds to the cabled port. dhcp Also note that you do not have a space between the http_server_ip_and_path and the iso_filename for this ISO URL (for example, http://198.51.100.1/home/images/aci-apic-dk9.4.0.3d.iso). Do not enter the ISO URL: If you do not want to enter the ISO URL, the installation process starts after ten minutes. The system starts fetching the ISO at this point. + read -p 'Interface to configure: ' interface Interface to configure: enp1s0f0 + read -p 'address: ' addr address: 10.75.39.72/24 + read -p 'gateway: ' gw gateway: 10.75.39.254 + ip addr add 10.75.39.72/24 dev enp1s0f0 + ip link set enp1s0f0 up + ip route add default via 10.75.39.254 ++ seq 1 2 + for count in '$(seq 1 2)' + ping -c 1 10.75.61.1 PING 10.75.61.1 (10.75.61.1) 56(84) bytes of data. 64 bytes from 10.75.61.1: icmp_seq=1 ttl=125 time=0.875 ms --- 10.75.61.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.875/0.875/0.875/0.000 ms + configured=1 + break + '[' 1 -eq 0 ']' + echo 'Fetching http://10.75.61.1/aci-apic-dk9.4.2.1j.iso' Fetching http://10.75.61.1/aci-apic-dk9.4.2.1j.iso + wget -o /dev/null -O /tmp/cdrom.iso http://10.75.61.1/aci-apic-dk9.4.2.1j.iso You can track the status of the process by going to Tools > Stats in the KVM console. Wait until you see the message poweroff in the SOL console, then exit from SOL by pressing Ctrl and x (Ctrl+x). Change the scope to virtual media again: system# scope vmedia system /vmedia # Unmap the .iso image that you mapped in 4.c: system /vmedia # unmap volume_name At the Save mapping prompt, enter yes if you want to save the mapping or no if you do not want to save the mapping. For example: system /vmedia # unmap apic Save mapping? Enther 'yes' or 'no' to confirm (CTRL-C to cancel) → yes system /vmedia # Connect back to SOL again: system /vmedia # connect host
Step 10	From the KVM console: Choose Power > Power on System to power on the controller.
Step 11	From the SOL console: Enter the following: During the boot process, press F6 to to enter the boot selection menu, then select the PCI RAID Adapter as the one-time boot device. You might also have to enter the BIOS password. The default password is password. Enter the options for the initial setup, such as fabric name, number of controllers, tunnel endpoint address pool, and infra VLAN ID to complete the installation process.

[OMBEER555]

how to map Map the .iso image to the HTTP server

how to creat HTTP server?

[RedNectar]

Hi @OMBEER555 ,

This question was answered two years ago.

Do you have a new question?  If so, ask it (click on Start a Conversation at the top of the page, or use this link)

[Robert Burns · Accepted solution]

Go into the BIOS during boot with F2 and check the status of the TPM. It may have disabled. If so re-enable it.

This was an issue during upgrade of older BIOSes.

Robert

[JCDM7]

That was the problem.

After looking again into the TPM menu on the BIOS it was not enabled. I have to set a BIOS password in order to enable TPM.

Thanks for the answer.