Pre-Network Bringup

Use this checklist before you build the fabric onsite. It focuses on design inputs, automation outputs, and BCM readiness so that physical bringup and Network Validate steps proceed without rework.

Prerequisites and inputs

• Confirm network planning and addressing align with your site and DGX model; refer to Network planning and design and subnet guidance in that chapter where applicable.

• Complete BCM bootstrap through head-node and rack-side OOB so switches can be reached for provisioning; follow BCM bootstrap workflow.

• Run netautogen and related tooling so BCM holds the expected devices, categories, and addressing; refer to Application workflow and Input file format and manifest.

• To add object into the BCM use bcm-pod-setup command.

Pre-Run Process

This section covers the validation and preparation steps that you should perform before beginning the actual deployment.

1. To validate P2P

   • Analyze / Restructure P2P (using GUI)

     1. Analyze Point-to-Point (P2P) network connections

     2. Identify P2P topology patterns and dependencies

     3. Restructure P2P connections for netautogen to consume

     4. Validate P2P link configurations

2. To Generate Network Configuration

   • To Access the UI:

     1. Go to Network Analyzer Dashboard:

        1. Temporary Login: bcm / bcm123

        2. Select 2: Network Auto Generate

           1. Project Name

           2. DGX Type

           3. Upload siteinfo.yml. For more information, see SiteInfo format.

           4. Upload p2p_ethernet.csv. For more information, see Point-to-Point (P2P) format.

           5. Upload rack inventory files. For more information, see Factory inventory data example.

        3. Press: Generate Configuration

           1. If there is an error, check the file and logs to fix it manually.

   • Option 1: Download the generated project (Download Project)

     1. Will gave tar.gz file contains all the generated configuration files for the switches and BCM JSON files.

   • Option 2: Deploy Virtual Env. in AIR for network validation (Launch Air SIM)

     1. Will gave Virtual Environment in AIR, which can be used to validate the network configuration.

3. To Bring up Base Command Manager (BCM) in Krusty Environment

   Note

   To Validate the bcm-pod-setup, then use Krusty as an virtual example.

     $ cod cc --version 11.0-dev --distro ubuntu2404 --head-node-root-volume-size 80 -m cod.8g4c -n 0
   
     $ apt-get update; apt-get install bcm-superpod-network bcm-post-install
   
   
   * **CM-Create IMAGE:**
       **bcm-pod-setup** will look for the directory for pre-existing image of the dgx (*/cm/image/<dgx_image>*)
   
   * **Depending on the Environment:**
       Airgapped Environment: adding ``--skipdist`` (not to update the apt-get package)
   

4. To perform the bcm-superpod-network automation, follow BCM Bootstrap Step 4 — Generate config in BCM Bootstrap Workflow.

5. To perform the bcm-pod-setup automation, follow BCM Bootstrap Step 5 — Importing objects into BCM in BCM Bootstrap Workflow.

Internal Reference
Mixed Architecture Setup
fxexport Setup
Control Node Image Setup

Handoff to validation

After switches are installed and reachable, use Network Validate for health checks, EVPN verification, customer reachability, and negative testing.