Physically connect the switches
Spines 5812s and Leafs 4610s
Spine1 port1 (40G) connects to Spine2 port1 (40G)
Spine1 port2 (40G) connects to Spine2 port2 (40G)
Leaf1 port1 (10G) connects to Spine1 port1 (10G)
Leaf1 port2 (10G) connects to Spine2 port1 (10G)
Leaf2 port1 (10G) connects to Spine1 port2 (10G)
Leaf2 port2 (10G) connects to Spine2 port2 (10G)
...
LeafN port1 (10G) connects to Spine1 portN (10G)
LeafN port2 (10G) connects to Spine2 portN (10G)
Spines 4610s and Leafs 4610s
Spine1 port5 (10G) connects to Spine2 port5 (10G)
Spine1 port6 (10G) connects to Spine2 port6 (10G)
Leaf1 port1 (10G) connects to Spine1 port1 (10G)
Leaf1 port2 (10G) connects to Spine2 port1 (10G)
...
Leaf4 port1 (10G) connects to Spine1 port4 (10G)
Leaf4 port2 (10G) connects to Spine2 port4 (10G)
Access the Cluster
Use the CC GUI at "http://IP_Address_of_Spine_Switch"
or console login into one of the spine switches
user: admin
password: pica8
- launch CC by entering "cc" on the CLI
cc
you may be prompted for the admin password again as you are redirected to the primary CC spine if you happened to log into the secondary spine
- initialize CC by entering "setup init" on the CC prompt
setup init
1-N
choose the port range that connect to the leaf switches
- enter "showleafs" on the CC prompt to see your 4 leaf cluster up and running
showleafs
Output will only show leafs connected to the first 4 ports until licenses are installed. Deployment with 4610 spines requires licenses and does not support demo mode
send "" show version
send self,peer show running-config | display set
...
CC Commands
Status
showleafs
showspines
checktopo - This command checks the spine and leaf cabling connections and alerts you if it detects an inconsistency.
viewlog
Initialization
setup init
setup net
setup mgmt
manage_license
Configuration
send - Relays config commands to a set or all switches. Supports %n-m% numerical expansion to minimize configuration commands; only a single expansion is supported per config line
runscript - Pushes a Linux Shell script to the switch and runs it on the switch. Generally used for Linux and OVS/OpenFlow configurations.
ssh
_ - Used for local switch CLI command execution
rem - config remark / comment
Operational
switch_reinit - Restart PICOS service on the switch
switch_erase - Erase all configuration on the switch
switch_rekey - Reinitialize the SSH key used between the spines and leafs
File Management
file_get - get a file onto the spine switch from an upstream location
file_list
file_del
file_push - push a file to the leaf switch from the spine
push_autorun - push a file to the switch and install it as the PICOS pre-start or post-start execute autorun script for customization of switch boot process
Config Management
config_save - Spines/Leaf replacements are automatically restored to previous config - if a previous config is not there you end up with the starter config - so remember to config_save for spines after major changes
config_restore
config_save_ovs
config_restore_ovs
config_purge - Deletes all configuration backups for a switch slot. This followed up with a switch_erase and switch_reinit will completely reset a switch
config_copy - copy configuration from one switch to another
Licensing
CC requires the PICOS Enterprise license which activates all switch ports. Contact us to request one
Use the CC GUI at "http://IP_Address_of_Spine_Switch" for license install
or use the CLI "manage_license" command to "show" the switch hardware ID, get a license for that switch and then "install" a license by copy-pasting the license when prompted
manage_license show peer
manage_license install peer
manage_license show self
manage_license install self
on applying license to the spines you need to restart the spine switches
switch_reinit peer
switch_reinit self
after reinit you will be able to see all your leaf switches when you run "show leafs"
you can now proceed to install licenses on all the leaf switches
manage_license show 1
manage_license install 1
...
manage_license show N
manage_license install N
switch_reinit 1-N
Image Install
If you are installing PICOS on bare metal switches download the software images for the Spines and Leafs from the "CC" directory on PICOS’s software download site You may need to request an SSO account if you don't already have one.
Additional details on PICOS available on the PICA8 Docs website.
Onie install:
ONIE install across all switches at once using a DHCP server with the option default-url option
eg. ISC-DHCP-Server DHCP option:
default-url = "http://172.16.0.44/CC/s.bin";
Or Manual install:
5812
GRUB bootloader - choose ONIE NOS install
onie-discovery-stop
ifconfig eth0 172.16.0.236/24
onie-nos-install [tftp|http]://URL
4610
Interrupt boot process and drop down to bootloader shell
run onie_bootcmd
onie-discovery-stop
ifconfig eth0 172.16.0.241/24
onie-nos-install [tftp|http]://URL