Installare Routed PON 24.1.2 - Single VM Lab

Introduzione

Questo documento descrive una procedura dettagliata per l'installazione del software Cisco Routed PON Manager nel laboratorio locale.

Prerequisiti

Requisiti

• Conoscenza dell'ambiente server Linux
• Conoscenza degli editor di testo Linux
• Strumenti Linux - openssh-server, net-tools, ntpd
  
  

Componenti usati

• Macchina virtuale Linux (VM)
  • 2 vCPU
  • 8 GB di RAM
  • 20 GB di spazio (minimo)
• Ubuntu 20.04.06 LTS

Le informazioni discusse in questo documento fanno riferimento a dispositivi usati in uno specifico ambiente di emulazione. Su tutti i dispositivi menzionati nel documento la configurazione è stata ripristinata ai valori predefiniti. Se la rete è operativa, valutare attentamente eventuali conseguenze derivanti dall'uso dei comandi.

Configurazione

Macchina virtuale

Strumenti

In questo documento si presume che la VM sia stata configurata per l'accesso, che il sistema operativo Ubuntu sia stato installato e configurato con la connettività di rete, che gli strumenti elencati in Requisiti siano stati installati e che il file zip Routed PON sia stato scaricato. Per facilitare l'operazione, sono stati forniti i comandi Ubuntu apt per scaricare e installare gli strumenti consigliati.

sudo apt install net-tools
sudo apt install openssh-server
sudo apt install ntpd

Disimballaggio

1) Creare una directory di installazione in cui decomprimere il file zip Routed PON 24.1.2.

rpon@rpon-mgr:~$ mkdir Routed_PON_24_1_2

2) Decomprimere Cisco_Routed_PON_24_1_2_Release.zip nella directory assegnata.

rpon@rpon-mgr:~/PON_Mgr_24_1_2$ unzip Cisco_Routed_PON_24_1_2_Release.zip 
Archive: Cisco_Routed_PON_24_1_2_Release.zip
inflating: PON_MANAGER_SIGNED_CCO/R4.0.0-Cisco-UB2004-sign.tar.gz 
inflating: PON_MANAGER_SIGNED_CCO/README 
inflating: PON_MANAGER_SIGNED_CCO/verify.tar.gz

3) Cambiare la directory (cd) nella cartella PON_MANAGER_SIGNED_CCO appena creata ed elencare (ls) i file.

rpon@rpon-mgr:~/PON_Mgr_24_1_2/PON_MANAGER_SIGNED_CCO$ ls -la
total 29120
drwxrwxr-x 2 rpon rpon 4096     Jun 13 09:26 .
drwxrwxr-x 3 rpon rpon 4096     Jun 13 09:26 ..
-rw-rw-r-- 1 rpon rpon 29792662 Mar 15 05:21 R4.0.0-Cisco-UB2004-sign.tar.gz
-rw-rw-r-- 1 rpon rpon 1966     Mar 15 05:21 README
-rw-rw-r-- 1 rpon rpon 11502    Mar 15 05:21 verify.tar.gz

4) Estrarre il file R4.0.0-Cisco-UB2004-sign.tar.gz utilizzando il file tar -xvf R4.0.0-Cisco-UB2004-sign.tar.gz.

rpon@rpon-mgr:~/PON_Mgr_24_1_2/PON_MANAGER_SIGNED_CCO$ tar -xvf R4.0.0-Cisco-UB2004-sign.tar.gz 
R4.0.0-Cisco-UB2004-sign/
R4.0.0-Cisco-UB2004-sign/R4.0.0-Cisco-UB2004.tar.gz.signature
R4.0.0-Cisco-UB2004-sign/R4.0.0-Cisco-UB2004.tar.gz

5) Inserire il CD nella directory dei segni R4.0.0-Cisco-UB2004 ed elencare i file.

rpon@rpon-mgr:~/PON_Mgr_24_1_2/PON_MANAGER_SIGNED_CCO$ cd R4.0.0-Cisco-UB2004-sign/
rpon@rpon-mgr:~/PON_Mgr_24_1_2/PON_MANAGER_SIGNED_CCO/R4.0.0-Cisco-UB2004-sign$ ls -la
total 29112
drwxr-xr-x 2 rpon rpon 4096     Mar 15 04:51 .
drwxrwxr-x 3 rpon rpon 4096     Jun 13 09:26 ..
-rw-r--r-- 1 rpon rpon 29796139 Mar 15 04:51 R4.0.0-Cisco-UB2004.tar.gz
-rw-r--r-- 1 rpon rpon 3546     Mar 15 04:51 R4.0.0-Cisco-UB2004.tar.gz.signature

6) Untar R4.0.0-Cisco-UB2004-tar.gz tramite tar -xvf R4.0.0-Cisco-UB2004.tar.gz.

rpon@rpon-mgr:~/PON_Mgr_24_1_2/PON_MANAGER_SIGNED_CCO/R4.0.0-Cisco-UB2004-sign$ tar -xvf R4.0.0-Cisco-UB2004.tar.gz 
---- snipped for brevity -----

7) Viene ora creata una nuova directory denominata R4.0.0-Cisco-UB2004 CD in questa directory.

rpon@rpon-mgr:~/PON_Mgr_24_1_2/PON_MANAGER_SIGNED_CCO/R4.0.0-Cisco-UB2004-sign/R4.0.0-Cisco-UB2004$ ls -la
total 116
drwxr-xr-x 7 rpon rpon 4096  Mar 14 11:11 .
drwxr-xr-x 3 rpon rpon 4096  Jun 13 09:26 ..
-rw-r--r-- 1 rpon rpon 8196  Mar 14 11:10 .DS_Store
-rwxr-xr-x 1 rpon rpon 13650 Mar 14 11:10 get-support-info.sh
drwxr-xr-x 3 rpon rpon 4096  Mar 14 11:10 grafana_dashboards
-rwxr-xr-x 1 rpon rpon 25392 Mar 14 11:10 install.sh
-rw-r--r-- 1 rpon rpon 1493  Mar 14 11:11 PonCntlInit.json
drwxr-xr-x 2 rpon rpon 4096  Mar 14 11:10 R4.0.0-Firmware
drwxr-xr-x 5 rpon rpon 4096  Mar 14 11:14 R4.0.0-Netconf-UB2004
drwxr-xr-x 6 rpon rpon 4096  Mar 14 11:14 R4.0.0-PonManager-UB2004
-rw-r--r-- 1 rpon rpon 7949  Mar 14 11:11 README.txt
-rwxr-xr-x 1 rpon rpon 2349  Mar 14 11:10 status.sh
drwxr-xr-x 2 rpon rpon 4096  Mar 14 11:10 tools
-rwxr-xr-x 1 rpon rpon 2245  Mar 14 11:10 uninstall.sh
-rwxr-xr-x 1 rpon rpon 8605  Mar 14 11:11 upgrade.sh

Installazione

Visualizzare il file README.txt per le fasi di installazione. Questa installazione utilizza l'opzione 2 per la nuova installazione.

rpon@rpon-mgr:~/PON_Mgr_24_1_2/PON_MANAGER_SIGNED_CCO/R4.0.0-Cisco-UB2004-sign/R4.0.0-Cisco-UB2004$ cat README.txt 

--- snipped for brevity ---

Option 2: New Installation
===========================

Step 1 : Verify System Requirements:
------------------------------------

a) Verify system is running ubuntu version 20.04

user@system:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: bionic

b) Verify the ethernet interfaces are configured on the ubuntu system
1) Look for your Ethernet Interfaces: "ifconfig" or "ip a". <<< make note of interfaces listed >>>
2) There are multiple ways to configure interfaces on Ubuntu 18.04 and 20.04
3) The simplest way is via Netplan
4) Netplan is located in the /etc/netplan directory
5) There will be a file similar in name to "01-network-manager-all.yaml"
6) Edit this file with your favorite editor such as "nano" or "vi"

c) user@system:~$ sudo nano /etc/netplan/<net-plan-name>.yaml
Sample Netplan text <<< Make sure indentation is consistent >>>

network:
 version: 2
 renderer: NetworkManager
 ethernets:
  eno1: <<< MCMS IP Interface >>>
  dhcp4: no <<< No DHCP >>>
  dhcp6: no <<< No DHCP >>>
  addresses: [172.16.41.5/24] <<< Static IPv4 >>>
  gateway4: 172.16.41.1 <<< IPv4 default Gateway >>>
   nameservers: <<< DNS Addresses >>>
 vlans: <<< Configured VLANs >>>
  vlan4090: <<< "l2EthInterfaceName" VLAN named vlan4090 assigned to PON Controller Interface >>>
  id: 4090 <<< VLAN number >>>
  link: eno2 <<< PON Controller Interface >>>

d) After finished editing, Save and exit, then enter "netplan apply" to enable new configuration.

e) Verify ubuntu system has connectivity to Internet


Step 2 : Installation
---------------------

a) Run the installation script "install.sh":

user@system:<install_directory>/R4.0.0-UB2004$ sudo ./install.sh -e <l2EthInterfaceName>

This script will do the following:
• Install MongoDB 
• Install MCMS PON Manager
• Install MCMS Netconf Server
• Install PON Controller and UMT Relay (using the Ethernet interface specificed)

Required:
-e <l2EthInterfaceName> interface name of L2 port

Optional: 
-d <databaseIpAaddress> IP address of MongoDB database
-n <databaseName> MongoDB database name for PON Manager
-m Install only PonManager/MongoDB/NETCONF
-c Install only PonController

defaults: 
-d <databaseIpAddress> = 127.0.0.1 
-n <databaseName> = tibit_pon_controller


Informational: How to verify all processes are running
=======================================================

a) Verify MongoDB is running

user@system:~$ sudo systemctl status mongod.service
● mongod.service - MongoDB Database Server
Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-08-30 11:56:38 PDT; 3 days ago
Main PID: 15035 (mongod)
CGroup: /system.slice/mongod.service
└─15035 /usr/bin/mongod --config /etc/mongod.conf

b) Verify MCMS PON Manager Apache Web Server is running

user@system:~$ sudo systemctl status apache2.service
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: active (running) since Fri 2019-08-16 15:19:09 PDT; 1 weeks 2 days ago
Process: 2981 ExecReload=/usr/sbin/apachectl graceful (code=exited, status=0/SUCCESS)
Main PID: 8471 (apache2)

---- Removed addtional information regarding PON Controller as this is installed in the XR Router so these instructions do not apply to the VM. ---

NetPlan

Utilizzando un editor di file di testo linux (nano, vi), modificare il file YAML situato nella directory /etc/netplan/ utilizzando il modello fornito nel file README.txt nella cartella di installazione. Popolare le informazioni IP specifiche della rete e della VM.

rpon@rpon-mgr:~/PON-mgr-24.1.2/PON_MANAGER_SIGNED_CCO/R4.0.0-Cisco-UB2004-sign/R4.0.0-Cisco-UB2004$ sudo nano /etc/netplan/01-network-manager-all.yaml
network:
 version: 2
 renderer: NetworkManager
 network:
  ethernets:
   ens192: <- This VM's network adapter is ens192. If the default is NOT ens192, change this value to the desired network adapter
    dhcp4: no
    dhcp6: no
    addresses: [IPv4 address and subnet]
    gateway4: [V4Gateway]
    nameservers:
      addresses: [DNS Server(s)]
vlans:
 vlan.4090:
  id: 4090
  link: [VM network adapter name]

Verificare che la configurazione di netplan sia corretta visualizzando il file tramite cat. Questo output è solo un esempio lab. Utilizzare gli indirizzi IP specifici per la rete. Una volta completati e usciti dall'editor di testo, eseguire sudo netplan apply.

Esempio Lab:

rpon@rpon-mgr:~/PON-mgr-24.1.2/PON_MANAGER_SIGNED_CCO/R4.0.0-Cisco-UB2004-sign/R4.0.0-Cisco-UB2004$ cat /etc/netplan/01-network-manager-all.yaml 
# Let NetworkManager manage all devices on this system
network:
 version: 2
 renderer: NetworkManager
 ethernets:
  ens192:
    dhcp4: no
    dhcp6: no
    addresses: [10.122.140.232/28]
    gateway4: 10.122.140.225
    nameservers:
      addresses: [172.18.108.43,172.18.108.34]
 vlans:
   vlan4090:
     id: 4090
     link: ens192

rpon@rpon-mgr:~/PON-mgr-24.1.2/PON_MANAGER_SIGNED_CCO/R4.0.0-Cisco-UB2004-sign/R4.0.0-Cisco-UB2004$ sudo netplan apply

Installazione pacchetto

Eseguire l'installazione utilizzando gli argomenti scelti. Per questa installazione, utilizzare -e, -d e -m. Come indicato nel file README.txt, -e indica all'installatore l'interfaccia Ethernet della VM da utilizzare, -d imposta l'indirizzo IP applicato al file mongo.conf per il MongoDB da utilizzare e -m installa PON Manager, MongoDB e NETCONF.

Esempio:
sudo ./install.sh -e ens192 -d [IndirizzoIP] -m

rpon@rpon-mgr:~/PON_MANAGER_SIGNED_CCO/R4.0.0-Cisco-UB2004-sign/R4.0.0-Cisco-UB2004$ sudo ./install.sh -e ens192 -d 10.122.140.232 -m

--- Installation snipped for brevity ---

Installation complete!

MCMS Component Versions:
PON Manager: R4.0.0
PON NETCONF: R4.0.0
PON Controller: Not Installed 

Verifica

Controllo dello stato del servizio

Eseguire un controllo dello stato sui servizi installati per verificare che siano attivi e in esecuzione tramite lo script status.sh, situato nella stessa directory di installazione.

• servizio.mondio
• apache2.service
• tibit-netopeer2-server.service
• tibit-netconf.service

Esempio:

rpon@rpon-mgr:~/PON-mgr-24.1.2/PON_MANAGER_SIGNED_CCO/R4.0.0-Cisco-UB2004-sign/R4.0.0-Cisco-UB2004$ sudo ./status.sh
MCMS Component Versions:
PON Manager: R4.0.0
PON NETCONF: R4.0.0
PON Controller: Not Installed

● mongod.service - MongoDB Database Server
Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2024-06-12 19:45:37 EDT; 2min 49s ago
Main PID: 54731 (mongod)
Memory: 74.7M
CGroup: /system.slice/mongod.service
└─54731 /usr/bin/mongod --config /etc/mongod.conf

● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2024-06-12 19:46:44 EDT; 1min 42s ago
Main PID: 62165 (apache2)
Tasks: 123 (limit: 9419)
Memory: 18.6M
CGroup: /system.slice/apache2.service
├─62165 /usr/sbin/apache2 -k start
├─62167 /usr/sbin/apache2 -k start
├─62168 /usr/sbin/apache2 -k start
└─62169 /usr/sbin/apache2 -k start

● tibit-netopeer2-server.service - Tibit Communications, Inc. Netopeer2 Server
Loaded: loaded (/lib/systemd/system/tibit-netopeer2-server.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2024-06-12 19:47:04 EDT; 1min 21s ago
Process: 63029 ExecStart=/opt/tibit/netconf/bin/start_netopeer2_server.sh (code=exited, status=0/SUCCESS)
Main PID: 63035 (netopeer2-serve)
Tasks: 7 (limit: 9419)
Memory: 5.4M
CGroup: /system.slice/tibit-netopeer2-server.service
└─63035 /opt/tibit/netconf/bin/netopeer2-server -v 1 -t 55

● tibit-netconf.service - Tibit Communications, Inc. NetCONF Server
Loaded: loaded (/lib/systemd/system/tibit-netconf.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2024-06-12 19:47:04 EDT; 1min 21s ago
Process: 63023 ExecStartPre=/opt/tibit/netconf/bin/shm_clean.sh (code=exited, status=0/SUCCESS)
Process: 63027 ExecStartPre=/opt/tibit/netconf/bin/sysrepocfg --copy-from startup -d running (code=exited, status=0/SUCCESS)
Main PID: 63028 (tibit-netconf)
Tasks: 17 (limit: 9419)
Memory: 49.4M
CGroup: /system.slice/tibit-netconf.service
├─63028 /opt/tibit/netconf/bin/tibit-netconf
└─63037 /opt/tibit/netconf/bin/tibit-netconf

11. Aprire un browser Internet e immettere l'indirizzo IP della macchina virtuale.

schermata di accesso a PON Manager

Documentazione di riferimento

• Pagina di supporto e download di Cisco
• Pagina Soluzione Cisco Routed PON
• Guida all'installazione di Cisco Routed PON
• Guida all'installazione di Cisco Routed PON
• Note sulla versione per Cisco Routed PON, Cisco IOS® XR release 24.1.1 e 24.1.2