Just centralizing some information I found hard to find:
MSO OVA root login: root:cisco
MSO web interface login before 2.1(1): admin:We1come!
MSO web interface login after 2.1(1): admin:We1come2msc!
Before deployment make sure ESXI/vCenter has the correct time. The OVAs get their time from the hypervisor and MSO creates some certificates. If the time is incorrect and you change it after deployment you will have issues with these certificates and have to rebuild MSO.
If you are working with a Hypervisor with limited resources you can remove the CPU and RAM reservations on each of the deployed OVAs. This will allow you to get MSO setup. For whatever reason Cisco thinks each VM needs 48GB of RAM and some odd CPU reservation. In practice, you need about 4GB of RAM.
Deployment
- Upload 3 copies of the OVA
- Boot Node 1
- Set hostname to ‘node1’
- Set IP address
- Reboot
- Boot Node 2
- Set hostname to ‘node2’
- Set IP address
- Reboot
- Boot Node 3
- Set hostname to ‘node3’
- Set IP address
- Reboot
- SSH to Node
cd /opt/cisco/msc/builds/<build_number>/prodha
./msc_cfg_init.py
The script above will output something similar to the following. Save this for the other nodes
./msc_cfg_join.py SWMTKN1-4pu9zc9d81gxxw6mxec5tuxdt8nbarq1qnmfw9zcme1w1tljZh7w3iwsddvd97ieza3ym1s5gj5 <ip_address_of_the_first_node>
6. SSH to Node 2
cd /opt/cisco/msc/builds/<build_number>/prodha
./msc_cfg_join.py SWMTKN1-4pu9zc9d81gxxw6mxec5tuxdt8nbarq1qnmfw9zcme1w1tljZh7w3iwsddvd97ieza3ym1s5gj5 <ip_address_of_the_first_node>
7. SSH to Node 3
cd /opt/cisco/msc/builds/<build_number>/prodha
./msc_cfg_join.py SWMTKN1-4pu9zc9d81gxxw6mxec5tuxdt8nbarq1qnmfw9zcme1w1tljZh7w3iwsddvd97ieza3ym1s5gj5 <ip_address_of_the_first_node>
8. On Node 1
docker node ls
##Check Status of Docker##
./msc_deploy.py
Wait. The End.