BCM Bootstrap Workflow#

This document outlines the step-by-step BCM (Baseboard Management Controller) bootstrap process for deploying network switches in a North-South network configuration. The process follows a specific sequence to ensure proper network establishment and switch provisioning.

Bootstrap Process Overview#

The BCM bootstrap workflow follows a hierarchical approach where switches are provisioned in a specific order to establish the network infrastructure. This process ensures that each stage builds upon the previous one, creating a stable and manageable network environment.

Key Principles:

  • Sequential Deployment: Switches are provisioned in a specific order to avoid dependencies

  • Centralized Management: All provisioning goes through the Access OOB switch

  • Progressive Network Build: Each stage adds to the network infrastructure

  • Fail-Safe Approach: Each stage must complete successfully before proceeding

Bootstrap Stages#

The following table provides a detailed breakdown of each stage in the BCM bootstrap process:

Stage

Switch Type

Description

Configuration Details

1

Primary OOB Switch (SN2201)

First bring up (primary) OOB SW

Primary OOB Switch Identification: The OOB switch directly connected to BCM Ethernet NIC is the PRIMARY This switch becomes the “Access OOB” switch for the entire network All other switches will be provisioned through this Access OOB switch Access OOB Configuration: BCM Ethernet NIC → Access OOB Switch ETH0 (Direct Connection) Access OOB Switch becomes the central OOB management point No uplink to SPINE/LEAF required for initial provisioning Eliminates dependency on external network infrastructure

2

Remaining OOB Switches

Remaining OOB Switches Provisioning

Secondary OOB Switch Provisioning: All remaining OOB switches connect ETH0 to Access OOB switch BCM provisions these switches through Access OOB → BCM path No direct BCM connection required for secondary switches Centralized management through Access OOB switch Provisioning Flow: BCM → Access OOB Switch → Secondary OOB Switch ETH0

3

SPINE Switches

SPINE Switches Configuration

SPINE Switch Provisioning: SPINE switches are configured after OOB network is established SPINE switches connect to Access OOB switch for management BCM provisions SPINE switches through Access OOB → BCM path SPINE switches form the core network backbone Provisioning Flow: BCM → Access OOB Switch → SPINE Switch ETH0 Configuration Steps: SPINE switch ETH0 connects to Access OOB switch BCM discovers SPINE switches through Access OOB SPINE switches receive configuration from BCM SPINE switches establish core network connectivity

4

TOR Switches

TOR Switches Configuration

TOR Switch Provisioning: TOR switches are configured last in the sequence TOR switches connect ETH0 to Access OOB switch BCM provisions TOR switches through Access OOB → BCM path TOR switches provide rack-level connectivity Provisioning Flow: BCM → Access OOB Switch → TOR Switch ETH0 Configuration Steps: TOR switch ETH0 connects to Access OOB switch BCM discovers TOR switches through Access OOB TOR switches receive configuration from BCM TOR switches establish rack-level connectivity

Troubleshooting#

Common issues and solutions during the BCM bootstrap process:

Stage 1 Issues: - BCM cannot reach Access OOB switch: Check physical cabling and IP configuration - Access OOB switch not booting: Verify power supply and firmware

Stage 2 Issues: - Secondary OOB switches not discovered: Check ETH0 connections to Access OOB - Provisioning failures: Verify BCM configuration and network settings

Stage 3 Issues: - SPINE switches not configuring: Check SPINE switch connections and BCM discovery - Core network not establishing: Verify SPINE switch configuration and routing

Stage 4 Issues: - TOR switches not configuring: Check TOR switch connections and BCM discovery - Rack connectivity issues: Verify TOR switch configuration and VLAN settings

Completion Criteria#

The BCM bootstrap process is considered complete when:

  1. All switches are provisioned and operational

  2. Network connectivity is established at all levels

  3. BCM can manage all switches through the Access OOB switch

  4. All validation steps pass successfully

  5. Network topology is verified and documented