Configurar a atualização automática do APIC a partir do 6.0(2H)

Introdução

Este documento descreve como o recurso de atualização automática funciona para o Cisco Application Policy Infrastructure Controller (APIC).

Quando é necessário?

No processo atual, sempre que um novo APIC é recebido via RMA (Return Material Authorization, Autorização de devolução de material) ou recém-adquirido, ele precisa executar a mesma versão do APIC que a da estrutura da ACI para ingressar no cluster. Isso exige a atualização do novo APIC para corresponder à versão do cluster existente antes de adicioná-lo à malha, o que é demorado e requer esforço manual.

Há dois casos de uso quando você precisa desse recurso.

1. Substituição de APIC defeituoso (APIC de RMA)
2. Expansão de cluster APIC

Pré-requisitos

Para simplificar o procedimento e torná-lo plug-and-play, o recurso de atualização automática do APIC foi introduzido a partir da versão 6.0(2) do ACI e das versões subsequentes.

Quando um novo APIC é introduzido na estrutura por meio de substituição ou adição, o software APIC deve ser compatível com o que está sendo executado no cluster. Normalmente, isso requer uma atualização, o que leva mais tempo para que o processo de atualização seja concluído e para que o APIC se associe à malha

Esse é um recurso automático que não requer nenhuma configuração.

Topologia

Nessa topologia, há três APICs executando a versão 6.0(5h) do ACI e o APIC3 apresenta falhas e requer substituição.

Etapas para executar a atualização automática do APIC

Depois de receber o APIC RMA, configure o IP do Cisco Integrated Management Controller (CIMC) para corresponder ao endereço CIMC anterior.

Etapa 1. Faça login na GUI do CIMC.

Etapa 2. Acesse o APIC por meio de KVM de teclado, vídeo e mouse.

Navegue para Iniciar vKVM > Clique nele > Mais uma guia de janela será aberta > Clique no hiperlink

Etapa 3. Inicialize o novo APIC para verificar a versão do APIC em execução (Você pode usar qualquer parâmetro fictício de Descoberta de Estrutura, como nome da Estrutura, ID da Estrutura, Pool TEP etc.)

Etapa 4. Depois que o novo APIC for inicializado, verifique a versão (você pode ver que a versão do APIC existente é 5.2.5c)

apic3# acidiag version <== To check the APIC version
5.2.5c

Etapa 5. Limpar e recarregar o novo APIC usando determinados comandos.

acidiag touch clean <<== Commands to remove all configuration and reboot the devices
acidiag touch setup
acidiag reboot

Etapa 6. Colete sam_export.config do APIC em funcionamento, pois essas informações serão usadas durante a inicialização do APIC.

apic1# cd /data/data_admin
apic1# pwd
/data/data_admin <=== Location of sam_exported.config file
apic1# ls -l | grep sam
-rw-r--r-- 1 root root 349 Jul  3 07:32 sam_exported.config

apic1# cat sam_exported.config
Setup for Active and Standby APIC
fabricDomain= bgl-aci04
fabricId= 1
systemName= bgl-aci04-apic1 <== APIC1 hostname , change based on APIC3
controllerID= 1
tepPool= 10.0.0.0/16
infraVlan= 3967
GIPo= 225.0.0.0/15
clusterSize= 5
standbyApic= NO
enableIPv4= Y
enableIPv6= N
firmwareVersion= 6.0(5h)
ifcIpAddr= 10.0.0.1
apicX= NO
podId= 1
standaloneApicCluster= no
oobIpAddr= 10.197.204.114/24 <== APIC1 OOB IP, Change based on APIC3

Etapa 7. Inicialize o novo APIC usando os dados coletados na Etapa 6.

Etapa 8. Remova o APIC3 com defeito da GUI do APIC01

Navegue até Sistema > Configurações do sistema > Controladores > Cluster como visto pelo nó

Clique em três pontos no lado direito do dispositivo. Clique em Encerrar

Etapa 9. Validar o estado administrativo do nó, ele é mostrado como "Fora de serviço" e a opção de desativação fica acinzentada.

Etapa 10. Remova o APIC3 com defeito do rack e instale o novo APIC3 no rack.

Etapa 11. Depois que o novo APIC for instalado no rack, ligue o novo APIC3 e conecte os cabos. Os cabos incluem uplinks de estrutura e portas de gerenciamento.

Etapa 12. Aguarde de 10 a 15 minutos para que o novo APIC possa ser ligado. Valide através do CIMC KVM se o novo APIC foi ligado e podemos ver o prompt de login. (O login funciona apenas com o rescue-user)

Etapa 13. Comissionar o APIC03 a partir da GUI do APIC01.

Navegue até Sistema > Configurações do sistema > Controladores > Cluster como visto pelo nó

Clique em três pontos do lado direito do dispositivo > Clique em Comissão

Etapa14: Adicione o endereço IP CIMC, o nome de usuário e a senha que foram usados no APIC antigo/com defeito que estamos substituindo. Clique em Validar. Depois que a validação for bem-sucedida.

Insira o nome do APIC, a senha de administrador (senha atual usada na malha), a ID do POD, o endereço de gerenciamento fora de banda e o gateway IPV4 e clique em Aplicar. (Todos esses parâmetros pertencem ao APIC antigo em caso de substituição).

Etapa 15. Aguarde de 10 a 15 minutos para que o novo APIC seja adicionado à estrutura com a versão 5.2(5c) do APIC.

apic1# acidiag avread                

Local appliance ID=1 ADDRESS=10.0.0.1 TEP ADDRESS=10.0.0.0/16 ROUTABLE IP ADDRESS=0.0.0.0 CHASSIS_ID=8ca31168-c4ab-11ee-a6c2-5d61e00b2df0

Cluster of 3 lm(t):1(2024-07-03T07:52:20.791+00:00) appliances (out of targeted 3 lm(t):3(2024-07-03T09:21:10.936+00:00)) with FABRIC_DOMAIN name=bgl-aci04 set to version=apic-6.0(5h) lm(t):3(2024-07-03T07:18:46.821+00:00); discoveryMode=PERMISSIVE lm(t):0(1970-01-01T00:00:00.004+00:00); drrMode=OFF lm(t):0(1970-01-01T00:00:00.004+00:00); kafkaMode=ON lm(t):1(2024-02-06T05:02:19.730+00:00); autoUpgradeMode=ON lm(t):2(2024-07-03T13:18:18.036+00:00); clusterInterface=infra

        appliance id=1  address=10.0.0.1 lm(t):1(2024-07-03T07:33:50.078+00:00) tep address=10.0.0.0/16 lm(t):1(2024-07-03T07:33:50.078+00:00) routable address=0.0.0.0 lm(t):1(zeroTime) oob address=10.197.204.114/24 lm(t):1(2024-07-03T07:52:20.955+00:00) version=6.0(5h) lm(t):1(2024-07-03T13:21:01.604+00:00) chassisId=8ca31168-c4ab-11ee-a6c2-5d61e00b2df0 lm(t):1(2024-07-03T13:21:01.604+00:00) capabilities=0X17EEFFFFFFFFF--0X2020--0X3--0X1 lm(t):1(2024-07-03T11:03:37.219+00:00) rK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T07:52:20.965+00:00) aK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T07:52:20.965+00:00) oobrK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T07:52:20.965+00:00) oobaK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T07:52:20.965+00:00) cntrlSbst=(APPROVED, FCH2322V05G) lm(t):1(2024-07-03T13:21:01.604+00:00) (targetMbSn= lm(t):0(zeroTime), failoverStatus=0 lm(t):0(zeroTime)) podId=1 lm(t):1(2024-07-03T07:33:50.078+00:00) commissioned=YES lm(t):1(zeroTime) registered=YES lm(t):1(2024-07-03T07:33:50.078+00:00) standby=NO lm(t):1(2024-07-03T07:33:50.078+00:00) DRR=NO lm(t):0(zeroTime) apicX=NO lm(t):1(2024-07-03T07:33:50.078+00:00) virtual=NO lm(t):1(2024-07-03T07:33:50.078+00:00) oob gw address=10.197.204.1 lm(t):1(2024-07-03T07:33:50.078+00:00) oob address v6=:: lm(t):1(2024-07-03T07:33:50.078+00:00) oob gw address v6=:: lm(t):1(2024-07-03T07:33:50.078+00:00) active=YES(2024-07-03T07:33:50.078+00:00) health=(applnc:255 lm(t):1(2024-07-03T11:03:39.196+00:00) svc's)

        appliance id=2  address=10.0.0.2 lm(t):3(2024-07-03T12:40:59.116+00:00) tep address=10.0.0.0/16 lm(t):2(2024-02-06T05:43:35.885+00:00) routable address=0.0.0.0 lm(t):0(zeroTime) oob address=10.197.204.115/24 lm(t):1(2024-07-03T13:21:01.948+00:00) version=6.0(5h) lm(t):2(2024-07-03T13:21:01.600+00:00) chassisId=557cdb0e-c4b2-11ee-a0a8-93aaf27bee50 lm(t):2(2024-07-03T13:21:01.600+00:00) capabilities=0X17EEFFFFFFFFF--0X2020--0X7--0X1 lm(t):2(2024-07-03T11:03:37.452+00:00) rK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:21:01.948+00:00) aK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:21:01.948+00:00) oobrK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:21:01.948+00:00) oobaK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:21:01.948+00:00) cntrlSbst=(APPROVED, FCH2323V09W) lm(t):2(2024-07-03T13:21:01.600+00:00) (targetMbSn= lm(t):0(zeroTime), failoverStatus=0 lm(t):0(zeroTime)) podId=1 lm(t):2(2024-07-03T08:19:03.478+00:00) commissioned=YES lm(t):3(2024-07-03T12:41:00.239+00:00) registered=YES lm(t):3(2024-07-03T12:41:00.239+00:00) standby=NO lm(t):1(2024-07-03T12:41:00.239+00:00) DRR=NO lm(t):1(2024-07-03T12:41:00.239+00:00) apicX=NO lm(t):1(2024-07-03T12:41:00.239+00:00) virtual=NO lm(t):0(zeroTime) oob gw address=10.197.204.1 lm(t):1(2024-07-03T08:40:04.837+00:00) oob address v6=:: lm(t):1(2024-07-03T13:21:01.948+00:00) oob gw address v6=:: lm(t):1(2024-02-06T05:46:22.175+00:00) active=YES(2024-07-03T13:21:01.694+00:00) health=(applnc:255 lm(t):2(2024-07-03T11:03:39.702+00:00) svc's)

        appliance id=3  address=10.0.0.3 lm(t):101(2024-07-03T13:18:17.965+00:00) tep address=10.0.0.0/16 lm(t):3(2024-07-03T12:40:40.900+00:00) routable address=0.0.0.0 lm(t):0(zeroTime) oob address=10.197.204.116/24 lm(t):1(2024-07-03T13:21:01.949+00:00) version=5.2(5c) lm(t):3(2024-07-03T13:21:01.736+00:00) chassisId=1c697d94-3939-11ef-a452-6d7c540421fa lm(t):3(2024-07-03T13:21:01.736+00:00) capabilities=0X17EEFFFFFFFFF--0X2020--0X4--0 lm(t):3(2024-07-03T13:20:59.140+00:00) rK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:21:01.949+00:00) aK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:21:01.949+00:00) oobrK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:21:01.949+00:00) oobaK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:21:01.949+00:00) cntrlSbst=(APPROVED, FCH2322V0AG) lm(t):3(2024-07-03T13:21:01.736+00:00) (targetMbSn= lm(t):0(zeroTime), failoverStatus=0 lm(t):0(zeroTime)) podId=1 lm(t):101(2024-07-03T13:18:17.965+00:00) commissioned=YES lm(t):1(2024-07-03T13:17:21.104+00:00) registered=YES lm(t):2(2024-07-03T13:18:18.036+00:00) standby=NO lm(t):101(2024-07-03T13:18:17.965+00:00) DRR=NO lm(t):1(2024-07-03T13:17:21.104+00:00) apicX=NO lm(t):101(2024-07-03T13:18:17.965+00:00) virtual=NO lm(t):0(zeroTime) oob gw address=0.0.0.0 lm(t):1(2024-07-03T13:21:01.562+00:00) oob address v6=:: lm(t):1(2024-07-03T13:21:01.949+00:00) oob gw address v6=:: lm(t):1(2024-02-06T06:06:24.927+00:00) active=YES(2024-07-03T13:21:01.562+00:00) health=(applnc:112 lm(t):3(2024-07-03T12:41:44.076+00:00) svc's) <<== APIC03 is still on 5.2(5c) version 

Etapa 16. O APIC existente atualizará esse novo APIC automaticamente para 6.0(5h) e o adicionará ao cluster também. Você pode manter isso em execução por mais 30 minutos e verificar a saída avread anterior novamente.

apic1# acidiag avread

Local appliance ID=1 ADDRESS=10.0.0.1 TEP ADDRESS=10.0.0.0/16 ROUTABLE IP ADDRESS=0.0.0.0 CHASSIS_ID=8ca31168-c4ab-11ee-a6c2-5d61e00b2df0

Cluster of 3 lm(t):1(2024-07-03T07:52:20.791+00:00) appliances (out of targeted 3 lm(t):3(2024-07-03T13:47:07.520+00:00)) with FABRIC_DOMAIN name=bgl-aci04 set to version=apic-6.0(5h) lm(t):3(2024-07-03T13:47:42.401+00:00); discoveryMode=PERMISSIVE lm(t):0(1970-01-01T00:00:00.004+00:00); drrMode=OFF lm(t):0(1970-01-01T00:00:00.004+00:00); kafkaMode=ON lm(t):1(2024-02-06T05:02:19.730+00:00); autoUpgradeMode=OFF lm(t):1(2024-07-03T13:45:43.249+00:00); clusterInterface=infra

        appliance id=1  address=10.0.0.1 lm(t):1(2024-07-03T07:33:50.078+00:00) tep address=10.0.0.0/16 lm(t):1(2024-07-03T07:33:50.078+00:00) routable address=0.0.0.0 lm(t):1(zeroTime) oob address=10.197.204.114/24 lm(t):1(2024-07-03T07:52:20.955+00:00) version=6.0(5h) lm(t):1(2024-07-03T13:45:43.249+00:00) chassisId=8ca31168-c4ab-11ee-a6c2-5d61e00b2df0 lm(t):1(2024-07-03T13:45:43.249+00:00) capabilities=0X17EEFFFFFFFFF--0X2020--0X7--0X1 lm(t):1(2024-07-03T13:45:43.249+00:00) rK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T07:52:20.965+00:00) aK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T07:52:20.965+00:00) oobrK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T07:52:20.965+00:00) oobaK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T07:52:20.965+00:00) cntrlSbst=(APPROVED, FCH2322V05G) lm(t):1(2024-07-03T13:45:43.249+00:00) (targetMbSn= lm(t):0(zeroTime), failoverStatus=0 lm(t):0(zeroTime)) podId=1 lm(t):1(2024-07-03T07:33:50.078+00:00) commissioned=YES lm(t):1(zeroTime) registered=YES lm(t):1(2024-07-03T07:33:50.078+00:00) standby=NO lm(t):1(2024-07-03T07:33:50.078+00:00) DRR=NO lm(t):0(zeroTime) apicX=NO lm(t):1(2024-07-03T07:33:50.078+00:00) virtual=NO lm(t):1(2024-07-03T07:33:50.078+00:00) oob gw address=10.197.204.1 lm(t):1(2024-07-03T07:33:50.078+00:00) oob address v6=:: lm(t):1(2024-07-03T07:33:50.078+00:00) oob gw address v6=:: lm(t):1(2024-07-03T07:33:50.078+00:00) active=YES(2024-07-03T07:33:50.078+00:00) health=(applnc:255 lm(t):1(2024-07-03T13:47:42.561+00:00) svc's)

        appliance id=2  address=10.0.0.2 lm(t):3(2024-07-03T13:24:30.725+00:00) tep address=10.0.0.0/16 lm(t):2(2024-02-06T05:43:35.885+00:00) routable address=0.0.0.0 lm(t):0(zeroTime) oob address=10.197.204.115/24 lm(t):1(2024-07-03T13:45:43.970+00:00) version=6.0(5h) lm(t):2(2024-07-03T13:45:42.995+00:00) chassisId=557cdb0e-c4b2-11ee-a0a8-93aaf27bee50 lm(t):2(2024-07-03T13:45:42.995+00:00) capabilities=0X17EEFFFFFFFFF--0X2020--0X7--0X1 lm(t):2(2024-07-03T13:45:42.994+00:00) rK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:45:43.970+00:00) aK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:45:43.970+00:00) oobrK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:45:43.970+00:00) oobaK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:45:43.970+00:00) cntrlSbst=(APPROVED, FCH2323V09W) lm(t):2(2024-07-03T13:45:42.995+00:00) (targetMbSn= lm(t):0(zeroTime), failoverStatus=0 lm(t):0(zeroTime)) podId=1 lm(t):2(2024-07-03T08:19:03.478+00:00) commissioned=YES lm(t):3(2024-07-03T13:24:30.745+00:00) registered=YES lm(t):3(2024-07-03T13:24:30.745+00:00) standby=NO lm(t):1(2024-07-03T13:24:30.745+00:00) DRR=NO lm(t):1(2024-07-03T13:24:30.745+00:00) apicX=NO lm(t):1(2024-07-03T13:24:30.745+00:00) virtual=NO lm(t):0(zeroTime) oob gw address=10.197.204.1 lm(t):1(2024-07-03T08:40:04.837+00:00) oob address v6=:: lm(t):1(2024-07-03T13:45:43.970+00:00) oob gw address v6=:: lm(t):1(2024-02-06T05:46:22.175+00:00) active=YES(2024-07-03T13:42:57.715+00:00) health=(applnc:255 lm(t):2(2024-07-03T13:47:42.560+00:00) svc's)

        appliance id=3  address=10.0.0.3 lm(t):102(2024-07-03T13:42:57.550+00:00) tep address=10.0.0.0/16 lm(t):3(2024-07-03T13:24:21.522+00:00) routable address=0.0.0.0 lm(t):0(zeroTime) oob address=10.197.204.116/24 lm(t):1(2024-07-03T13:45:44.004+00:00) version=6.0(5h) lm(t):3(2024-07-03T13:45:43.443+00:00) chassisId=5803434b-393f-11ef-8e96-2c4f52b32ad0 lm(t):3(2024-07-03T13:45:43.443+00:00) capabilities=0X17EEFFFFFFFFF--0X2020--0X7--0X1 lm(t):3(2024-07-03T13:51:50.477+00:00) rK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:45:43.964+00:00) aK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:45:43.964+00:00) oobrK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:45:43.964+00:00) oobaK=(stable,present,0X206173722D687373) lm(t):1(2024-07-03T13:45:43.964+00:00) cntrlSbst=(APPROVED, FCH2322V0AG) lm(t):3(2024-07-03T13:45:43.443+00:00) (targetMbSn= lm(t):0(zeroTime), failoverStatus=0 lm(t):0(zeroTime)) podId=1 lm(t):102(2024-07-03T13:42:57.550+00:00) commissioned=YES lm(t):1(2024-07-03T13:38:51.799+00:00) registered=YES lm(t):1(2024-07-03T13:42:57.480+00:00) standby=NO lm(t):102(2024-07-03T13:42:57.550+00:00) DRR=NO lm(t):1(2024-07-03T13:38:51.799+00:00) apicX=NO lm(t):102(2024-07-03T13:42:57.550+00:00) virtual=NO lm(t):0(zeroTime) oob gw address=10.197.204.1 lm(t):1(2024-07-03T13:45:43.257+00:00) oob address v6=:: lm(t):1(2024-07-03T13:45:44.004+00:00) oob gw address v6=:: lm(t):1(2024-02-06T06:06:24.927+00:00) active=YES(2024-07-03T13:45:43.045+00:00) health=(applnc:255 lm(t):3(2024-07-03T13:47:42.405+00:00) svc's) <<== APIC03 is upgraded to 6.0(5h) version and health 255 shows it is fully fit

Para verificar se a atualização automática está sendo executada sem erros, verifique o arquivo svc_ifc_appliancedirector.bin.log no APIC existente, que é responsável por atualizar o APIC recém-adicionado.

Local:  /var/log/dme/log

svc_ifc_appliancedirector.bin.log | grep "ApplianceAutoUpgrade.cpp"

4411||2024-07-03T13:03:02.014060877+00:00||appliance_director||DBG4||||# Registered APICs:3||../appliance/director/./ApplianceAutoUpgrade.cpp||115    <<   APIC3 is registered to the cluster

4411||2024-07-03T13:03:02.014069812+00:00||appliance_director||DBG4||||# APICs its version is same cluster version:2||../appliance/director/./ApplianceAutoUpgrade.cpp||116  <<   APIC01/02 have same version 6.0(5h)

4411||2024-07-03T13:03:02.014078887+00:00||appliance_director||DBG4||||# APICs its version is different cluster version:1||../appliance/director/./ApplianceAutoUpgrade.cpp||117   <<   APIC03 is running different version 5.2(5c)

4442||2024-07-03T13:04:02.025327143+00:00||appliance_director||DBG4||||Try to upgrade Appliance3||../appliance/director/./ApplianceAutoUpgrade.cpp||147    <<   Auto Upgrade Check Kicks in

4442||2024-07-03T13:04:02.025434226+00:00||appliance_director||DBG4||||ImageFile: /firmware/fwrepos/fwrepo/aci-apic-image-name.bin||../appliance/director/./ApplianceAutoUpgrade.cpp||160    <<  Image file location on Local APIC

4442||2024-07-03T13:04:02.025661541+00:00||appliance_director||DBG4||||Running rsync -8 -avzk --timeout 600 -e "ssh -p 1022 -i /securedata/ssh/root/id_rsa -o UserKnownHostsFile=/dev/null -o GSSAPIAuthentication=no -o StrictHostKeyChecking=no -o ConnectTimeout=60 -o ServerAliveInterval=60" /mgmt/support/insieme/auto_upgrade.py  root@10.0.0.3:/mgmt/support/insieme/auto_upgrade.py||../appliance/director/./ApplianceAutoUpgrade.cpp||202

4442||2024-07-03T13:04:03.001492232+00:00||appliance_director||DBG4||||Done: Copy auto_upgrade script to remote apic||../appliance/director/./ApplianceAutoUpgrade.cpp||220    <<  Upgrade script is copied to APIC03 from APIC01

4442||2024-07-03T13:04:03.001598593+00:00||appliance_director||DBG4||||Running rsync -8 -avzk --timeout 600 -e "ssh -p 1022 -i /securedata/ssh/root/id_rsa -o UserKnownHostsFile=/dev/null -o GSSAPIAuthentication=no -o StrictHostKeyChecking=no -o ConnectTimeout=60 -o ServerAliveInterval=60" /firmware/fwrepos/fwrepo/aci-apic-image-name.bin  root@10.0.0.3:/tmp/myImage.bin||../appliance/director/./ApplianceAutoUpgrade.cpp||226

4442||2024-07-03T13:13:59.287332478+00:00||appliance_director||DBG4||||Done: Copy iimage file to remote apic||../appliance/director/./ApplianceAutoUpgrade.cpp||244    <<  ISO image 6.0(5h) is coped to APIC03 from APIC01

4442||2024-07-03T13:13:59.287418460+00:00||appliance_director||DBG4||||Running ssh -p 1022 -i /securedata/ssh/root/id_rsa -o UserKnownHostsFile=/dev/null -o GSSAPIAuthentication=no -o StrictHostKeyChecking=no -o ConnectTimeout=60 -o ServerAliveInterval=60 root@10.0.0.3 "/mgmt/support/insieme/auto_upgrade.py 1 10.0.0.1"||../appliance/director/./ApplianceAutoUpgrade.cpp||250

4442||2024-07-03T13:17:55.430111171+00:00||appliance_director||DBG4||||Run remote upgrade done||../appliance/director/./ApplianceAutoUpgrade.cpp||268    <<   Running upgrade script on APIC03

4442||2024-07-03T13:17:55.430203755+00:00||appliance_director||DBG4||||Decommissioning Appliance 3||../appliance/director/./ApplianceAutoUpgrade.cpp||273    <<   APIC03 is decomissioned

4442||2024-07-03T13:20:25.430436301+00:00||appliance_director||DBG4||||Commissioning Appliance 3||../appliance/director/./ApplianceAutoUpgrade.cpp||277   <<   APIC03 is commissioned back to the fabric

Etapa 17. Em caso de falha na atualização automática do APIC, é seguido por uma falha.

Etapa 18. Para casos de falha, você sempre pode reativar a atualização automática do APIC fazendo uma recarga limpa e adicionando o novo APIC de volta à estrutura da ACI para detecção.

Se essas etapas não resolverem o problema, colete os registros de suporte técnico e entre em contato com o TAC da Cisco para obter assistência adicional.