Procedimento de reimplantação do Ultra-M AutoVNF

Introduction

Este documento descreve as etapas necessárias para reimplantar uma AutoVNF em um Ultra-M. A AutoVNF é responsável por ativar o Virtual Network Function Manager (VNFM) e a Virtual Network Function (VNF). 

Pré-verificações

1. Faça login no OpenStack Platform Diretor (OSPD) e verifique o status da máquina virtual (VMs) no relatório de integridade.

[stack@labucs300-ospd ~]$ cat /var/log/cisco/ultram-health/*.report | grep -i xxx

[stack@labucs300-ospd ~]$ cat /var/log/cisco/ultram-health/ultram_health_uas.report
---------------------------------------------------------------------------------------------------------
 VNF-ID/VNFD-ID           | UAS Node | Status| Error Info, if any         
---------------------------------------------------------------------------------------------------------
10.10.10.40/LABPGW300-UAS | autovnf  | :-)   | LABPGW300-UAS:(alive)
                          |          |       |   labucs300-UAS-LABPGW300-UAS-core-UAS2-2:(alive)
                          |          |       |   labucs300-UAS-LABPGW300-UAS-core-UAS2-1:(alive)
10.10.10.40/LABPCF300-UAS | autovnf  | :-)   | LABPCF300-UAS:(alive)
                          |          |       |   labucs300-UAS-LABPCF300-UAS-core-UAS1-2:(alive)
                          |          |       |   labucs300-UAS-LABPCF300-UAS-core-UAS1-1:(alive)
10.10.10.45/LABPCF300-UGP | vnf-em   | :-)   | LABPCF300-UGP:(alive)
                          |          |       |   LABPCF300-LABPCF300-UGP-core-EM1-3:(alive)
                          |          |       |   LABPCF300-LABPCF300-UGP-core-EM1-2:(alive)
                          |          |       |   LABPCF300-LABPCF300-UGP-core-EM1-1:(alive)
10.10.10.45/LABPCF300-ESC | esc      | :-)   | LABPCF300-ESC:(alive)
                          |          |       |   LABPCF300-LABPCF300-ESC-core-ESC1-1:(alive)
                          |          |       |   LABPCF300-LABPCF300-ESC-core-ESC1-2:(alive)
10.10.10.45/LABPCF300-UGP | vnf      | :-)   | LABPCF300-UGP:(alive)
                          |          |       |   LABPCF300-LABPCF300-UGP-core-LABPCF300-CF-VDU-1:(alive)
                          |          |       |   LABPCF300-LABPCF300-UGP-core-LABPCF300-CF-VDU-0:(alive)
                          |          |       |   LABPCF300-LABPCF300-UGP-core-LABPCF300-SF-VDU-3:(alive)
                          |          |       |   LABPCF300-LABPCF300-UGP-core-LABPCF300-SF-VDU-2:(alive)
                          |          |       |   LABPCF300-LABPCF300-UGP-core-LABPCF300-SF-VDU-1:(alive)
                          |          |       |   LABPCF300-LABPCF300-UGP-core-LABPCF300-SF-VDU-0:(alive)
                          |          |       |   LABPCF300-LABPCF300-UGP-core-LABPCF300-SF-VDU-6:(alive)
                          |          |       |   LABPCF300-LABPCF300-UGP-core-LABPCF300-SF-VDU-5:(alive)
                          |          |       |   LABPCF300-LABPCF300-UGP-core-LABPCF300-SF-VDU-4:(alive)
10.10.10.48/LABPGW300-UGP | vnf-em   | :-)   | LABPGW300-UGP:(alive)
                          |          |       |   LABPGW300-LABPGW300-UGP-core-EM2-2:(alive)
                          |          |       |   LABPGW300-LABPGW300-UGP-core-EM2-3:(alive)
                          |          |       |   LABPGW300-LABPGW300-UGP-core-EM2-1:(alive)
10.10.10.48/LABPGW300-ESC | esc      | :-)   | LABPGW300-ESC:(alive)
                          |          |       |   LABPGW300-LABPGW300-ESC-core-ESC2-1:(alive)
                          |          |       |   LABPGW300-LABPGW300-ESC-core-ESC2-2:(alive)
10.10.10.48/LABPGW300-UGP | vnf      | :-)   | LABPGW300-UGP:(alive)
                          |          |       |   LABPGW300-LABPGW300-UGP-core-LABPGW300-SF-VDU-4:(alive)
                          |          |       |   LABPGW300-LABPGW300-UGP-core-LABPGW300-SF-VDU-5:(alive)
                          |          |       |   LABPGW300-LABPGW300-UGP-core-LABPGW300-SF-VDU-6:(alive)
                          |          |       |   LABPGW300-LABPGW300-UGP-core-LABPGW300-SF-VDU-0:(alive)
                          |          |       |   LABPGW300-LABPGW300-UGP-core-LABPGW300-SF-VDU-1:(alive)
                          |          |       |   LABPGW300-LABPGW300-UGP-core-LABPGW300-SF-VDU-2:(alive)
                          |          |       |   LABPGW300-LABPGW300-UGP-core-LABPGW300-SF-VDU-3:(alive)
                          |          |       |   LABPGW300-LABPGW300-UGP-core-LABPGW300-CF-VDU-0:(alive)
                          |          |       |   LABPGW300-LABPGW300-UGP-core-LABPGW300-CF-VDU-1:(alive)
---------------------------------------------------------------------------------------------------------

2. Verifique o status da AutoVNF.

[stack@labucs300-ospd ~]$ source *core
[stack@labucs300-ospd ~]$ nova list | grep LABPGW300-UAS-core-UAS2
| 8608fda4-b763-4753-95ff-2e07852098e3 | labucs300-UAS-LABPGW300-UAS-core-UAS2-1 | ACTIVE | - | Running | labucs300-UAS-LABPGW300-ORCH-NW=192.0.2.15; labucs300-UAS-LABPGW300-MGMT-NW=192.0.2.7 |
| 19f4496c-3907-4ea5-84c9-e5a6ef222392 | labucs300-UAS-LABPGW300-UAS-core-UAS2-2 | ACTIVE | - | Running | labucs300-UAS-LABPGW300-ORCH-NW=192.0.2.17; labucs300-UAS-LABPGW300-MGMT-NW=192.0.2.16

labucs300-UAS-LABPGW300-UAS-core-UAS2-2 -> VNFM2-UAS-VIP Primary
labucs300-UAS-LABPGW300-UAS-core-UAS2-1 -> Secondary 

3. Faça login na AutoIT e verifique os registros de pulsação.

ubuntu@labucs300-autoit-2:~$ grep "'restarting'" /var/log/cisco/uas/heartbeat.log
2021-02-22 01:41:42,808 - 192.0.2.15: Notify Event: {'action': 'restart', 'source': 'heartbeat', 'event': 'restarting', 'ip': '192.0.2.15'}
2021-02-22 01:45:42,251 - 192.0.2.15: Notify Event: {'action': 'restart', 'source': 'heartbeat', 'event': 'restarting', 'ip': '192.0.2.15'}
2021-02-23 01:43:36,013 - 192.0.2.15: Notify Event: {'action': 'restart', 'source': 'heartbeat', 'event': 'restarting', 'ip': '192.0.2.15'}
2021-02-23 01:45:55,785 - 192.0.2.15: Notify Event: {'action': 'restart', 'source': 'heartbeat', 'event': 'restarting', 'ip': '192.0.2.15'}
2021-02-24 01:45:19,680 - 192.0.2.15: Notify Event: {'action': 'restart', 'source': 'heartbeat', 'event': 'restarting', 'ip': '192.0.2.15'}

ubuntu@labucs300-autoit-2:~$ cd /var/log/cisco/uas
ubuntu@labucs300-autoit-2:/var/log/cisco/uas$ grep "Rebooting Instance" uas_USPCHBWorker.log
2019-06-26 18:26:13,088 - Rebooting Instance: 19f4496c-3907-4ea5-84c9-e5a6ef222392
2019-06-29 03:45:12,710 - Rebooting Instance: 19f4496c-3907-4ea5-84c9-e5a6ef222392
2020-07-17 00:46:25,800 - Rebooting Instance: 19f4496c-3907-4ea5-84c9-e5a6ef222392
2020-07-18 00:47:13,347 - Rebooting Instance: 19f4496c-3907-4ea5-84c9-e5a6ef222392
2020-07-18 05:11:11,133 - Rebooting Instance: 19f4496c-3907-4ea5-84c9-e5a6ef222392
2020-07-18 5:16:07,333 - Rebooting Instance: 19f4496c-3907-4ea5-84c9-e5a6ef222392 

Backup do AutoVNF

O AutoVNF é responsável por ativar VNFM e VNF individuais. O AutoDeploy envia a configuração necessária para instanciar o VNFM e o VNF para o AutoVNF e o AutoVNF faz esta operação. Para ativar o VNFM,

O AutoVNF fala diretamente com o VIM/openstack e, quando o VNFM estiver ativo, o AutoVNF usa o VNFM para ativar o VNF.

O AutoVNF tem redundância de 1:1 e, na configuração do UltraM, 2 VMs AutoVNF em execução no modo HA.

Detalhes do backup do AutoVNF:

• Configuração running
• CDB ConfD
• Logs AutoVNF (de cada instância do AutoVNF)
• Configuração de syslog

Importante: Os backups devem ser executados antes de qualquer ativação/desativação no POD/local especificado e carregados no servidor de backup. 

1. Defina ha_debug como ON em AutoIT Primário e Secundário em /opt/uas_baseconfig.txt.

Note: O sinalizador ha_debug é todo capital. É LIGADO ou DESLIGADO.

ubuntu@labucs300-autoit-2:~$ vi /opt/uas_baseconfig.txt
ha: true
ha-vip: 172.16.181.7
ha-secret: f99d04acb84807c4c6c6c0eaad392b5c
orch-ips: 172.16.181.5,172.16.181.8
orch-intf: eth0
prov-ha-vip: 172.16.181.13
prov-intf: eth0
profile: AUTOIT
ha_debug: ON

ubuntu@labucs300-autoit-1:~$ vi /opt/uas_baseconfig.txt
ha: true
ha-vip: 172.16.181.7
ha-secret: f99d04acb84807c4c6c6c0eaad392b5c
orch-ips: 172.16.181.5,172.16.181.8
orch-intf: eth0
prov-ha-vip: 172.16.181.13
prov-intf: eth0
profile: AUTOIT
ha_debug: ON

2. Interrompa o serviço AutoIT na AutoIT Principal com estes comandos:

ssh   ubuntu@ < AutoIT Floating IP>
sudo -i
service autoit stop

Isso evita que a AutoIT dispare a recuperação automática do Ultra Automation Services (UAS) quando o desligamento é iniciado em etapas posteriores.

ubuntu@labucs300-autoit-2:~$ sudo -i
root@labucs300-autoit-2:~#
root@labucs300-autoit-2:~# service autoit status
autoit start/running, process 25001
root@labucs300-autoit-2:~# service autoit stop

3. Defina ha_debug como ON em Primary e Secondary AutoVNF (UAS) no arquivo /opt/uas_baseconfig.txt.

ubuntu@labucs300-uas-LABPGW300-uas-core-uas2-2:~$ vi /opt/uas_baseconfig.txt
ha: true
ha-vip: 192.0.2.8
ha-secret: d5a9fee60ddae4fe357677dcf1320e51
orch-ips: 192.0.2.15,192.0.2.17
orch-intf: eth0
profile: AUTOVNF
ha_debug: ON

ubuntu@labucs300-uas-LABPGW300-uas-core-uas2-2:~$ ssh ubuntu@192.0.2.15
ubuntu@labucs300-uas-LABPGW300-uas-core-uas2-1:~$ cat /opt/uas_baseconfig.txt
ha: true
ha-vip: 192.0.2.8
ha-secret: d5a9fee60ddae4fe357677dcf1320e51
orch-ips: 192.0.2.15,192.0.2.17
orch-intf: eth0
profile: AUTOVNF
ha_debug: ON

4. Desligue o UAS secundário do OSPD com comentários.

 . corerc ; openstack server stop <VMName>

labucs300-UAS-LABPGW300-UAS-core-UAS2-2 -> VNFM2-UAS-VIP Primary
labucs300-UAS-LABPGW300-UAS-core-UAS2-1 -> Secondary

[stack@labucs300-ospd ~]$ nova list | grep LABPGW300-UAS-core-UAS2
| 8608fda4-b763-4753-95ff-2e07852098e3 | labucs300-UAS-LABPGW300-UAS-core-UAS2-1 | ACTIVE | - | Running | labucs300-UAS-LABPGW300-ORCH-NW=192.0.2.15; labucs300-UAS-LABPGW300-MGMT-NW=192.0.2.7 |
| 19f4496c-3907-4ea5-84c9-e5a6ef222392 | labucs300-UAS-LABPGW300-UAS-core-UAS2-2 | ACTIVE | - | Running | labucs300-UAS-LABPGW300-ORCH-NW=192.0.2.17; labucs300-UAS-LABPGW300-MGMT-NW=192.0.2.16

[stack@labucs300-ospd ~]$. corerc ; openstack server stop labucs300-UAS-LABPGW300-UAS-core-UAS2-1

5. Pare os serviços uas-confd e autovnf no UAS com estes comandos:

service uas-confd stop
service autovnf stop

ubuntu@labucs300-uas-LABPGW300-uas-core-uas2-2:~$ sudo -i 
root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# service uas-confd status
uas-confd start/running, process 1305
root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# service autovnf status
autovnf start/running, process 24208
root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# service uas-confd stop
uas-confd stop/waiting
root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# service autovnf stop
autovnf stop/waiting

6. Faça um backup do banco de dados de conferência do UAS e copie-o em um servidor de backup com estes comandos:

cd /opt/cisco/usp/uas/confd-latest/var/confd/
tar -cvf <pod>_<VNF>_UAS_cdb_backup.tar cdb/

root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# cd /opt/cisco/usp/uas/confd-latest/var/confd/
root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# tar -cvf Autovnf_cdb_backup.tar cdb/
cdb/
cdb/O.cdb
cdb/C.cdb
cdb/aaa_init.xml
cdb/A.cdb
root@labucs300-uas-LABPGW300-uas-core-uas2-2:/opt/cisco/usp/uas/confd-latest/var/confd# ll Autovnf_cdb_backup_cdb_backup.tar 
total 1612
drwxr-xr-x 3 root root 4096 Jan 24 2017 ..
drwxr-xr-x 2 root root 4096 Jan 24 2017 log
drwxr-xr-x 8 root root 4096 Oct 11 11:30 webui
drwxr-xr-x 2 root root 4096 Oct 19 19:18 candidate
drwxr-xr-x 2 root root 4096 Oct 23 13:00 rollback
drwxr-xr-x 2 root root 4096 Oct 28 17:00 cdb
drwxr-xr-x 3 root root 4096 Oct 28 17:00 state
drwxr-xr-x 8 root root 4096 Oct 31 18:00 .
-rw-r--r-- 1 root root 1617920 Oct 31 18:00 Autovnf_cdb_backup.tar

7. Reinicie os serviços uas-confd e autovnf no UAS com estes comandos:

service uas-confd start
service autovnf start

root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# service uas-confd start
uas-confd start/running, process 13852
root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# service autovnf start
autovnf start/running, process 13853

8. Reinicie o UAS secundário do OSPD com estes comandos:

. corerc ; openstack server start <VMName>

[stack@labucs300-ospd ~]$. corerc ; openstack server start labucs300-UAS-LABPGW300-UAS-core-UAS2-1

9. Verifique se o UAS Primário e Secundário aparecem como ativo no comando show uas.

ubuntu@labucs300-uas-LABPGW300-uas-core-uas2-2:~$ sudo -i
root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# confd_cli -u admin -C
Welcome to the ConfD CLI
admin connected from 127.0.0.1 using console on labucs300-uas-LABPGW300-uas-core-uas2-2
labucs300-uas-LABPGW300-uas-core-uas2-2#show uas 
uas version 6.2.0
uas state active
uas external-connection-point 192.0.2.8
INSTANCE IP STATE ROLE 
-----------------------------------
0.0.0.0 error CONFD-Secondary
192.0.2.15 alive CONFD-Secondary
192.0.2.17 alive CONFD-Primary

10. Altere ha_debug para OFF no UAS (Primary and Secondary AutoVNF, principal e secundário) do arquivo /opt/uas_baseconfig.txt.

ubuntu@labucs300-uas-LABPGW300-uas-core-uas2-2:~$ vi /opt/uas_baseconfig.txt
ha: true
ha-vip: 192.0.2.8
ha-secret: d5a9fee60ddae4fe357677dcf1320e51
orch-ips: 192.0.2.15,192.0.2.17
orch-intf: eth0
profile: AUTOVNF
ha_debug: OFF
ubuntu@labucs300-uas-LABPGW300-uas-core-uas2-2:~$ ssh ubuntu@192.0.2.15
ubuntu@labucs300-uas-LABPGW300-uas-core-uas2-1:~$ cat /opt/uas_baseconfig.txt
ha: true
ha-vip: 192.0.2.8
ha-secret: d5a9fee60ddae4fe357677dcf1320e51
orch-ips: 192.0.2.15,192.0.2.17
orch-intf: eth0
profile: AUTOVNF
ha_debug: OFF

11. Reinicie o serviço de inicialização automática no AutoIT Principal com o comando service autoit start.

ubuntu@labucs300-autoit-2:~$ sudo -i
root@labucs300-autoit-2:~# service autoit start

12. Verifique se a AutoIT primária e secundária aparece como ativa com o comando show uas.

ubuntu@labucs300-autoit-2:~$ sudo -i
root@labucs300-autoit-2:~# confd_cli -u admin -C 
Welcome to the ConfD CLI
admin connected from 127.0.0.1 using console on labucs300-autoit-2
labucs300-autoit-2#show uas
uas version 6.2.0
uas state active
uas external-connection-point 172.16.181.7
INSTANCE IP STATE ROLE 
-----------------------------------
172.16.181.5 alive CONFD-Secondary 
172.16.181.8 alive CONFD-Primary

13. Defina ha_debug como OFF em Primary e Secondary AutoIT no arquivo /opt/uas_baseconfig.txt.

ubuntu@labucs300-autoit-2:~$ vi /opt/uas_baseconfig.txt
ha: true
ha-vip: 172.16.181.7
ha-secret: f99d04acb84807c4c6c6c0eaad392b5c
orch-ips: 172.16.181.5,172.16.181.8
orch-intf: eth0
prov-ha-vip: 172.16.181.13
prov-intf: eth0
profile: AUTOIT
ha_debug: OFF

ubuntu@labucs300-autoit-1:~$ vi /opt/uas_baseconfig.txt
ha: true
ha-vip: 172.16.181.7
ha-secret: f99d04acb84807c4c6c6c0eaad392b5c
orch-ips: 172.16.181.5,172.16.181.8
orch-intf: eth0
prov-ha-vip: 172.16.181.13
prov-intf: eth0
profile: AUTOIT
ha_debug: OFF

14. Colete registros do UAS e transfira-os para um servidor de backup.

root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# cd /opt/cisco/usp/uas/confd-latest/var/confd/
root@labucs300-uas-LABPGW300-uas-core-uas2-2:/opt/cisco/usp/uas/confd-latest/var/confd# cd /opt/cisco/usp/uas/scripts/
root@labucs300-uas-LABPGW300-uas-core-uas2-2:/opt/cisco/usp/uas/scripts# sudo ./collect-uas-logs.sh 
Dumping output for show transaction in file /tmp/uas-logs/transactions.txt
Dumping output for show log in file /tmp/uas-logs/transactions.txt
Dumping output for show running-config in file /tmp/uas-logs/confd_output.txt
Dumping output for show uas in file /tmp/uas-logs/confd_output.txt
Dumping output for show usp in file /tmp/uas-logs/confd_output.txt
..........

15. Faça login no AutoVNF secundário e repita a etapa anterior para coletar os logs e transferi-los para o servidor de backup.

16. Faça backup da configuração do syslog nas VMs AutoVNF primária e secundária e transfira-as para o servidor de backup. Os arquivos estão localizados nestes diretórios:

root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# ls /etc/rsyslog.d/00-autovnf.conf 
/etc/rsyslog.d/00-autovnf.conf
root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# ls /etc/rsyslog.conf
/etc/rsyslog.conf

17. Ative o serviço de inicialização automática com o comando service autoit start no AutoIT principal.

ubuntu@labucs300-autoit-2:~$ sudo -i
root@labucs300-autoit-2:~#
root@labucs300-autoit-2:~# service autoit start
autoit start/running, process 25001

18. Defina o modo de flag ha_debug como OFF no /opt/uas_baseconfig.txt em Primary AutoVNF e AutoIT.

ubuntu@labucs300-uas-LABPGW300-uas-core-uas2-2:~$ vi /opt/uas_baseconfig.txt
ha: true
ha-vip: 192.0.2.8
ha-secret: d5a9fee60ddae4fe357677dcf1320e51
orch-ips: 192.0.2.15,192.0.2.17
orch-intf: eth0
profile: AUTOVNF
ha_debug: OFF

ubuntu@labucs300-autoit-2:~$ vi /opt/uas_baseconfig.txt
ha: true
ha-vip: 172.16.181.7
ha-secret: f99d04acb84807c4c6c6c0eaad392b5c
orch-ips: 172.16.181.5,172.16.181.8
orch-intf: eth0
prov-ha-vip: 172.16.181.13
prov-intf: eth0
profile: AUTOIT
ha_debug: OFF

19. Confirme os serviços uas-confd e autovnf em execução no UAS.

root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# service uas-confd status
uas-confd start/running, process 1305
root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# service autovnf status
autovnf start/running, process 24208

Reimplantação da AutoVFN

1. Efetue login na Implantação automática e observe a instância do UAS.

ubuntu@labucs300-autodeploy-2:~$ sudo su 
root@labucs300-autodeploy-2:/home/ubuntu# confd_cli -u admin -C
Welcome to the ConfD CLI
admin connected from 127.0.0.1 using console on labucs300-autodeploy-2
labucs300-autodeploy-2#show nsr
 nsr         LABSGW300-instance
 nsd         LABSGW300
 vnfr        [ LABPCF300-LABPCF300-ESC LABPCF300-LABPCF300-UGP ]
 vnf-package [ usp_6_2_b8 ]
 vim-artifact vim_art_rack
nsr LABPGW300-instance
 nsd         LABPGW300
 vnfr        [ LABPGW300-LABPGW300-ESC LABPGW300-LABPGW300-UGP ]
 vnf-package [ usp_6_2_b8 ]
 vim-artifact vim_art_rack
nsr labucs300-UAS-instance
 nsd         labucs300-UAS
 vnfr        [ labucs300-UAS-LABPCF300-UAS labucs300-UAS-LABPGW300-UAS ]
 vnf-package [ usp_6_2_b8 ]
 vim-artifact vim_art_rack

2. Desative o AutoVNF de AutoDeploy com o comando desative nsd-id <nsd-id> vnfd <vnfd-id>.

ubuntu@labucs300-autodeploy-2:~$ /opt/cisco/usp/uas/confd-6.3.1/bin/confd_cli -u admin -C
Welcome to the ConfD CLI
admin connected from 10.10.10.10 using ssh on labucs300-autodeploy-2
labucs300-autodeploy-2#nsd:deactivate nsd-id labucs300-UAS vnfd [LABPGW300-UAS]
transaction-id 1560431372-357328 

3. Confirme o status da transação.

labucs300-autodeploy-2#show transaction 
                                                           DEPLOYMENT                                                 STATUS 
TX ID                               TX TYPE                ID            TIMESTAMP                        STATUS      DETAIL 
------------------------------------------------------------------------------------------------------------------------------
1560431372-357328                   activate-ns-deployment labucs300-UAS 2019-06-13T13:09:32.357355-00:00 in-progress - 
1560431372-357328/1560431373-102024 activate-ns-deployment labucs300-UAS 2019-06-13T13:09:33.102041-00:00 in-progress - 

4. Verifique os registros da transação. Nesse caso, labucs300-UAS - transações: 1560431372-357328 e 1560431372-357328/1560431373-102024.

labucs300-autodeploy-2#show log 1560431372-357328 | display xml
<config xmlns="http://tail-f.com/ns/config/1.0">
<log xmlns="http://www.cisco.com/usp/nfv/usp-transaction">
<tx-id>1560431372-357328</tx-id>
<log>
2019-06-13 13:09:33,367 - Send Deployment notification for: labucs300-UAS-instance
2019-06-13 13:09:33,375 - Deployment activate-ns-deployment: labucs300-UAS started
2019-06-13 13:09:33,378 - Adding NSR: labucs300-UAS-instance
2019-06-13 13:09:33,385 - Start pipeline of 1 tasks
2019-06-13 13:09:33,390 - Scheduling Task: labucs300-UAS
2019-06-13 13:09:33,400 - Waiting for all workers to finish the transactions
2019-06-13 13:15:00,006 - Deployment activate-ns-deployment: labucs300-UAS succeeded
2019-06-13 13:15:00,020 - Send Deployment notification for: labucs300-UAS-instance
2019-06-13 13:09:33,437 - Send Deployment notification for: labucs300-UAS-instance-deploy
2019-06-13 13:09:33,441 - Deployment activate-ns-deployment: labucs300-UAS started
……………

labucs300-autodeploy-2#show log 1560431372-357328/1560431373-102024 | display xml
<config xmlns="http://tail-f.com/ns/config/1.0">
<log xmlns="http://www.cisco.com/usp/nfv/usp-transaction">
<tx-id>1560431372-357328/1560431373-102024</tx-id>
<log>
2019-06-13 13:09:33,437 - Send Deployment notification for: labucs300-UAS-instance-deploy
2019-06-13 13:09:33,441 - Deployment activate-ns-deployment: labucs300-UAS started
2019-06-13 13:09:33,446 - Adding NSR: labucs300-UAS-instance, VNFR: labucs300-UAS-LABPCF300-UAS, vlrs: None
2019-06-13 13:09:33,453 - Adding NSR: labucs300-UAS-instance, VNFR: labucs300-UAS-LABPGW300-UAS, vlrs: None
2019-06-13 13:09:33,463 - VNF deployment pre-check success(all-not-present)
2019-06-13 13:09:33,472 - VNF-Package deployment pre-check success(all-not-present)
2019-06-13 13:09:33,481 - VIM-Artifact deployment pre-check success
2019-06-13 13:09:33,487 - Skipping VIM-Orch pre-deployment, since VIM-Orch is not defined
2019-06-13 13:09:33,496 - Skipping VIM pre-deployment, since VIM is not defined
2019-06-13 13:09:33,499 - NS pre-check success
2019-06-13 13:09:33,503 - Copying '/home/ubuntu/usp-6_2_b8.iso' to '/var/cisco/isos/labucs300-UAS_usp_6_2_b8'
2019-06-13 13:09:53,359 - Updated path to URL 'http://172.16.181.14:5000/isos/labucs300-UAS_usp_6_2_b8'

5. Aguarde até que a transação seja concluída e confirme o estado.

labucs300-autodeploy-2#show transaction 
                                                           DEPLOYMENT                                            STATUS 
TX ID                               TX TYPE                ID            TIMESTAMP                        STATUS DETAIL 
------------------------------------------------------------------------------------------------------------------------------
1560431372-357328                   activate-ns-deployment labucs300-UAS 2019-06-13T13:09:32.357355-00:00 success - 
1560431372-357328/1560431373-102024 activate-ns-deployment labucs300-UAS 2019-06-13T13:09:33.102041-00:00 success - 

6. Ative o VNFD do AutoVNF na Implantação automática com o comando ativate nsd-id <nsd-id> vnfd <vnfd-id>.

ubuntu@labucs300-autodeploy-2:~$ /opt/cisco/usp/uas/confd-6.3.1/bin/confd_cli -u admin -C
Welcome to the ConfD CLI
admin connected from 10.253.110.47 using ssh on labucs300-autodeploy-2
labucs300-autodeploy-2#nsd:activate nsd-id labucs300-UAS vnfd [LABPGW300-UAS]
transaction-id 1560431371-357330 

7. Verifique o status da transação e colete logs da transação com estes comandos:

show transaction
show log <transaction-id> | display xml
show log <transaction-id> | display xml

8. Aguarde até que as transações sejam concluídas. O comando show transaction mostra o estado das transações.

Restauração de backup

1. No AutoIT Primário, defina o modo de flag ha_debug como ON em /opt/uas_baseconfig.txt.

ubuntu@labucs300-autoit-2:~$ vi /opt/uas_baseconfig.txt
ha: true
ha-vip: 172.16.181.7
ha-secret: f99d04acb84807c4c6c6c0eaad392b5c
orch-ips: 172.16.181.5,172.16.181.8
orch-intf: eth0
prov-ha-vip: 172.16.181.13
prov-intf: eth0
profile: AUTOIT
ha_debug: ON

2. Em AutoIT principal, pare o serviço automaticamente. Esta etapa é para evitar que a AutoIT recupere automaticamente o UAS.

ubuntu@labucs300-autoit-2:~$ sudo -i
root@labucs300-autoit-2:~#
root@labucs300-autoit-2:~# service autoit status
autoit start/running, process 25001
root@labucs300-autoit-2:~# service autoit stop

3. No UAS principal, defina o modo de flag ha_debug como ON em /opt/uas_baseconfig.txt.

ubuntu@labucs300-uas-LABPGW300-uas-core-uas2-2:~$ vi /opt/uas_baseconfig.txt
ha: true
ha-vip: 192.0.2.8
ha-secret: d5a9fee60ddae4fe357677dcf1320e51
orch-ips: 192.0.2.15,192.0.2.17
orch-intf: eth0
profile: AUTOVNF
ha_debug: ON

4. No UAS secundário, defina o modo de flag ha_debug como ON em /opt/uas_baseconfig.txt.

ubuntu@labucs300-uas-LABPGW300-uas-core-uas2-1:~$ cat /opt/uas_baseconfig.txt
ha: true
ha-vip: 192.0.2.8
ha-secret: d5a9fee60ddae4fe357677dcf1320e51
orch-ips: 192.0.2.15,192.0.2.17
orch-intf: eth0
profile: AUTOVNF
ha_debug: ON

5. No OSPD, pare o servidor UAS secundário com o comando OpenStack.

labucs300-UAS-LABPGW300-UAS-core-UAS2-2 -> VNFM2-UAS-VIP Primary
labucs300-UAS-LABPGW300-UAS-core-UAS2-1 -> Secondary

[stack@labucs300-ospd ~]$. corerc ; openstack server stop labucs300-UAS-LABPGW300-UAS-core-UAS2-1

6. No UAS principal, pare o serviço uas-confd.

ubuntu@labucs300-uas-LABPGW300-uas-core-uas2-2:~$ sudo -i 
root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# service uas-confd status
uas-confd start/running, process 1305
root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# service uas-confd stop
uas-confd stop/waiting

7. No UAS principal, copie o arquivo de backup do CDB para o diretório /opt/cisco/usp/uas/confd-latest/var/confd/.

root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# cp Autovnf_cdb_backup.tar to /opt/cisco/usp/uas/confd-latest/var/confd/

8. No UAS principal, exclua os arquivos no diretório CBD.

root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# cd /opt/cisco/usp/uas/confd-latest/var/confd/ ; rm cdb/*

9. No UAS principal, extraia arquivos do arquivo de backup do CDB.

root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# cd /opt/cisco/usp/uas/confd-latest/var/confd/ ; tar -xvf <archive_backup_tar_file>

10. No OSPD, reinicialize o UAS principal com comandos OpenStack.

[stack@labucs300-ospd ~]$ source *core
[stack@labucs300-ospd ~]$ nova list | grep LABPGW300-UAS-core-UAS2
| 8608fda4-b763-4753-95ff-2e07852098e3 | labucs300-UAS-LABPGW300-UAS-core-UAS2-1 | ACTIVE | - | Running | labucs300-UAS-LABPGW300-ORCH-NW=192.0.2.15; labucs300-UAS-LABPGW300-MGMT-NW=192.0.2.7 |
| 19f4496c-3907-4ea5-84c9-e5a6ef222392 | labucs300-UAS-LABPGW300-UAS-core-UAS2-2 | ACTIVE | - | Running | labucs300-UAS-LABPGW300-ORCH-NW=192.0.2.17; labucs300-UAS-LABPGW300-MGMT-NW=192.0.2.16

labucs300-UAS-LABPGW300-UAS-core-UAS2-2 -> VNFM2-UAS-VIP Primary
labucs300-UAS-LABPGW300-UAS-core-UAS2-1 -> Secondary

[stack@labucs300-ospd ~]$ nova reboot --hard 19f4496c-3907-4ea5-84c9-e5a6ef222392
Request to reboot server <Server: auto-testautovnf1-uas-2> has been accepted.

11. Espere até que o UAS principal apareça. Verifique o status do UAS no UAS principal após a reinicialização. O estado Principal está ativo enquanto o secundário mostra o estado desconhecido.

ubuntu@labucs300-uas-LABPGW300-uas-core-uas2-2:~$ sudo -i
root@labucs300-uas-LABPGW300-uas-core-uas2-2:~# confd_cli -u admin -C
Welcome to the ConfD CLI
admin connected from 127.0.0.1 using console on labucs300-uas-LABPGW300-uas-core-uas2-2
labucs300-uas-LABPGW300-uas-core-uas2-2#show uas 
uas version 6.2.0
uas state active
uas external-connection-point 192.0.2.8
INSTANCE IP STATE ROLE 
-----------------------------------
192.0.2.15 unknown CONFD-Secondary 
192.0.2.17 alive CONFD-Primary

12. No OSPD, inicie o UAS secundário com o comando OpenStack.

[stack@labucs300-ospd ~]$. corerc ; openstack server start labucs300-UAS-LABPGW300-UAS-core-UAS2-1

13. No OSPD, verifique se os estados do UAS primário e secundário estão ativos.

[stack@labucs300-ospd ~]$ openstack server list | grep labucs300-UAS-LABPGW300
| 19f4496c-3907-4ea5-84c9-e5a6ef222392 | labucs300-UAS-LABPGW300-UAS-core-UAS2-2 | ACTIVE | labucs300-UAS-LABPGW300-ORCH-NW=192.0.2.17; labucs300-UAS-LABPGW300-MGMT-NW=192.0.2.16 | labucs300-UAS-usp_6_2_b8-core-uas |
| 8608fda4-b763-4753-95ff-2e07852098e3 | labucs300-UAS-LABPGW300-UAS-core-UAS2-1 | ACTIVE | labucs300-UAS-LABPGW300-ORCH-NW=192.0.2.15; labucs300-UAS-LABPGW300-MGMT-NW=192.0.2.7 | labucs300-UAS-usp_6_2_b8-core-uas |

14. No UAS principal, verifique se os estados do UAS primário e secundário estão vivos.

labucs300-uas-LABPGW300-uas-core-uas2-2#show uas 
uas version 6.2.0
uas state active
uas external-connection-point 192.0.2.8
INSTANCE IP STATE ROLE 
-----------------------------------
192.0.2.15 alive CONFD-Secondary
192.0.2.17 alive CONFD-Primary

15. No serviço automático de início da AutoIT Principal.

ubuntu@labucs300-autoit-2:~$ sudo -i
root@labucs300-autoit-2:~# service autoit start

16. Verifique se a sessão Secure Shell (SSH) permanece ativa por alguns minutos para UAS primário e secundário.

17. No UAS principal, defina o modo de flag ha_debug como OFF em /opt/uas_baseconfig.txt.

ubuntu@labucs300-uas-LABPGW300-uas-core-uas2-2:~$ vi /opt/uas_baseconfig.txt
ha: true
ha-vip: 192.0.2.8
ha-secret: d5a9fee60ddae4fe357677dcf1320e51
orch-ips: 192.0.2.15,192.0.2.17
orch-intf: eth0
profile: AUTOVNF
ha_debug: OFF

18.  No UAS secundário, defina o modo de flag ha_debug como OFF em /opt/uas_baseconfig.txt.

ubuntu@labucs300-uas-LABPGW300-uas-core-uas2-1:~$ cat /opt/uas_baseconfig.txt
ha: true
ha-vip: 192.0.2.8
ha-secret: d5a9fee60ddae4fe357677dcf1320e51
orch-ips: 192.0.2.15,192.0.2.17
orch-intf: eth0
profile: AUTOVNF
ha_debug: OFF

19. No AutoIT Primário, defina o modo de flag ha_debug como OFF em /opt/uas_baseconfig.txt.

 ubuntu@labucs300-autoit-2:~$ vi /opt/uas_baseconfig.txt
ha: true
ha-vip: 172.16.181.7
ha-secret: f99d04acb84807c4c6c6c0eaad392b5c
orch-ips: 172.16.181.5,172.16.181.8
orch-intf: eth0
prov-ha-vip: 172.16.181.13
prov-intf: eth0
profile: AUTOIT
ha_debug: OFF

20. No AutoVNF, verifique os arquivos 0-autovnf.conf e rsyslog.conf e restaure-os a partir do backup anterior.

ubuntu@autoit-tb1-autovnf1-core-avf-1:~#sudo su
root@autoit-tb1-autovnf1-core-avf-1:~#ls /etc/rsyslog.d/00-autovnf.conf
00-autovnf.conf

root@autoit-tb1-autovnf1-core-avf-1:~#/home/ubuntu#ls /etc/rsyslog.conf
rsyslog.conf

Pós-cheques

No OSPD, verifique se ambas as AutoVNFs estão ativas e verifique o relatório de verificação de integridade do Ultra-M.

[stack@labucs300-ospd ~]$ cat /var/log/cisco/ultram-health/*.report | grep -i xxx

[stack@labucs300-ospd ~]$ cat /var/log/cisco/ultram-health/ultram_health_uas.report