Generate CSM switch configs
Generating configuration files can be done for singular switch or for the full system. For example; in a case where you suspect a configuration issue on single switch you can generate just that one file for easier debugging purposes.
- Generating configuration file for single switch:
canu generate switch config --csm 1.2 -a full --ccj hela-ccj.json --sls-file sls_file.json --name sw-spine-001 --folder generated
- Generating configuration files for the entire system:
canu generate network config --csm 1.2 -a full --ccj hela-ccj.json --sls-file sls_file.json --folder generated
The following are the different architectures that can be specified:
Again, make sure that you select the correct (-a) architecture specific to your setup:
- Tds – Aruba-based Test and Development System. These are small systems characterized by Kubernetes NCNs cabling directly to the spine.
- Full – Aruba-based Leaf-Spine systems, usually customer production systems.
- V1 – Dell and Mellanox based systems of either a TDS or Full layout.
Generating a configuration file can be done for a single switch, or for the full system. Below are example commands for both scenarios:
Important
Modify the following items in your command:
--csm
: Which CSM version configuration do you want to use? For example, 1.2 or 1.0--a
: What is the system architecture? (See above)--ccj
: Match theccj.json
file to the one you created for your system.-
--sls
: Match thesls_file.json
to the one you created for your system. -
Generate a configuration file for single switch:
bash
ncn# canu generate switch config --csm 1.2 -a full --ccj system-ccj.json --sls-file sls_file.json --name sw-spine-001
- Generate a configuration files for full system:
bash
ncn# canu generate network config --csm 1.2 -a full --ccj system-ccj.json --sls-file sls_file.json --folder generated