Deploying switch configuration

Prerequisites

Ensure that you are logged into the NPS toolkit VM as root user.

Procedure
  1. To view the available switch profiles, run the following command: 
    nps show -p switch_profiles
    Following are the available switch profiles for RHOSP based on the validated hardware combinations:

    Validated hardware combinations

    Data switch type

    Corresponding switch profile

    HPE EL4000 with HPE ProLiant m510 (controllers and computes)

    Comware

    5950_Edge

    HPE ProLiant DL

    Comware

    5950_Core_without_dcn

    HPE Edgeline 8000 with HPE ProLiant e910

    Mellanox

    2100_el8k_rhosp

    SRIOV 8port and HPE Nimble Storage AF60

    Comware

    5950_sriov8port_with_nimble

    HPE EL4000 with HPE ProLiant m510 (controllers) and HPE Edgeline 8000 with HPE ProLiant e910 (compute) with 4 port

    Mellanox

    2100_el8k_rhosp_4p

    HPE ProLiant DL

    Mellanox

    2100_core

    HPE ProLiant DL (addon computes)

    Mellanox

    2100_core_addon

    HPE ProLiant DL

    Comware

    5950_Core_with_dcn

    HPE EL4000 with HPE ProLiant m510 (controllers) and HPE Edgeline 8000 with HPE ProLiant e910 (compute) with 2 port

    Mellanox

    2100_el8k_rhosp_2p

    HPE ProLiant DL with Hyperconverged infrastructure

    Altoline

    6960_core_hci

    HPE EL4000 with HPE ProLiant m510 (controllers) with Hyperconverged infrastructure

    Altoline

    6960_edge

    HPE EL4000 with HPE ProLiant m510 (controllers) and HPE Edgeline 8000 with HPE ProLiant e910 (compute) with 2 port

    Mellanox

    2100_rhocp_rhosp

    NOTE:

    Select the switch profile based on the hardware components (DL or EL, data switch type, and computes).

  2. To deploy switch configuration, run the following command:

    nps deploy -s switch -p <profile name> -t <type of switch> -nos <nos_type> -ip <comma seperated switch iLO_OOBM IPs>

    Where,

    <profile name> - switch profile you have selected.

    <type of switch> - data

    <nos_type> - comware or cumulus

    NOTE:
    By default, the information-level logs are displayed during execution of the NPS toolkit deploy command. To view the debug-level logs, provide the -l debug argument in the NPS toolkit command. For example: 
    nps deploy -s switch -p <Name of switch profile> -t <Type of switch> -nos <nos_type> -ip <comma seperated switch iLO_OOBM IPs> -l debug
  3. To verify the status of switch configuration, run the following command: 
    nps show --service switch
    NOTE:

    If the status is displayed as "Failed", see Switch automation status shows Failed.

  4. If you have selected to deploy Comware data switch, manually configure an uplink to the Customer infrastructure switch.
    The following code snippet shows an example uplink configuration to the customer infrastructure switch: 
    <5950-2>sys
[5950-2]int b 50
[5950-2-Bridge-Aggregation50]dis this
#
interface Bridge-Aggregation50
	description Uplink-to-Customer-Network
	port link-type trunk
	undo port trunk permit vlan 1
	port trunk permit vlan <OAM_VLAN> <CAN_VLAN> <provider VLAN> <transport VLAN>
	port trunk pvid vlan <pvid of customer VLAN>
	link-aggregation mode dynamic
	undo mac-address static source-check enable
#
return
[5950-2-Bridge-Aggregation50]
  5. If you must set static IP for management interface in data switches, perform the following steps for each switch:
    1. Log in to the data switch-1 console and run the following commands: 
      net add interface eth0 ip address <IP from ILO-OOBM range>/<subnet mask>
net add interface eth0 ip gateway <ILO OOBM network's gateway>
net add hostname <hostname>
net commit
    2. Log in to the data switch-2 console and run the following commands: 
      net add interface eth0 ip address <IP from ILO-OOBM range>/<subnet mask>
net add interface eth0 ip gateway <ILO OOBM network's gateway>
net add hostname <hostname>
net commit
  6. Perform this step for breaking the bonds on the switch ports connected to the FLR NICs of the controllers.
    NOTE:

    Applicable only to EL4000 controllers. Skip this step if the controllers are of any other server model.

    1. To delete the bonds, run the following command on both the data switches:
      Data switch 1 
      net del bond Ctrl1-EL4C2-CX
net del bond Ctrl2-EL4C3-CX
net del bond Ctrl3-EL4C4-CX
net commit
      Data switch 2 
      net del bond Ctrl1-EL4C2-CX
net del bond Ctrl2-EL4C3-CX
net del bond Ctrl3-EL4C4-CX
net commit
    2. To configure the ports as trunk port, run the following command on both the data switches:
      Data switch 1 
      net add bridge bridge ports swp6s1-3
net add interface swp6s1-3 mtu 9216
net add interface swp6s1-3 bridge pvid <VIM-PXE VLAN>
net add interface swp6s1-3 bridge vids <VIM-PXE VLAN>,<BLS VLAN>,<CLM VLAN>,<CAN VLAN>
net commit
      Data switch 2 
      net add bridge bridge ports swp6s1-3
net add interface swp6s1-3 mtu 9216
net add interface swp6s1-3 bridge pvid <VIM-PXE VLAN>
net add interface swp6s1-3 bridge vids <VIM-PXE VLAN>,<BLS VLAN>,<CLM VLAN>,<CAN VLAN>
net commit