Skip to content

Running VLAB

Make sure to follow the prerequisites and check system requirements in the VLAB Overview section before running VLAB.

Initialize VLAB

First, initialize Fabricator by running hhfab init --dev --gw. This command creates the fab.yaml file, which is the main configuration file for the fabric. The --gw flag enables the gateway. This command supports several customization options that are listed in the output of hhfab init --help.

ubuntu@docs:~$ hhfab init --dev --gw
10:26:45 INF Hedgehog Fabricator version=v0.43.1
10:26:45 INF Generated initial config
10:26:45 INF Adjust configs (incl. credentials, modes, subnets, etc.) file=fab.yaml
10:26:45 INF Include wiring (fabric/gateway) files (.yaml) or adjust imported ones dir=include

VLAB Topology

Spine-Leaf

To generate a spine-leaf topology, use hhfab vlab gen. The following generates an ESLAG (EVPN Multi-Homing) topology:

ubuntu@docs:~$ hhfab vlab gen --mclag-leafs-count 0 --eslag-leaf-groups 2
10:26:46 INF Hedgehog Fabricator version=v0.43.1
10:26:46 INF Building VLAB wiring diagram fabricMode=spine-leaf
10:26:46 INF >>> spinesCount=2 fabricLinksCount=2 meshLinksCount=0
10:26:46 INF >>> eslagLeafGroups=2
10:26:46 INF >>> gatewayUplinks=2 gatewayDriver=kernel
10:26:46 INF >>> mclagLeafsCount=0 mclagSessionLinks=0 mclagPeerLinks=0
10:26:46 INF >>> orphanLeafsCount=1
10:26:46 INF >>> mclagServers=0 eslagServers=2 unbundledServers=1 bundledServers=1
10:26:46 INF >>> externalCount=0 externalMclagConnCount=0 externalEslagConnCount=0 externalOrphanConnCount=0
10:26:46 INF Generated wiring file name=vlab.generated.yaml

You can customize the topology with flags like --spines-count and --eslag-leaf-groups. For complete options, run hhfab vlab gen -h.

The topology with 2 spines, 2 ESLAG leaves, 1 orphan leaf, and a gateway is shown below:

graph TD

%% Style definitions
classDef gateway fill:#FFF2CC,stroke:#999,stroke-width:1px,color:#000
classDef spine   fill:#F8CECC,stroke:#B85450,stroke-width:1px,color:#000
classDef leaf    fill:#DAE8FC,stroke:#6C8EBF,stroke-width:1px,color:#000
classDef server  fill:#D5E8D4,stroke:#82B366,stroke-width:1px,color:#000
classDef mclag   fill:#F0F8FF,stroke:#6C8EBF,stroke-width:1px,color:#000
classDef eslag   fill:#FFF8E8,stroke:#CC9900,stroke-width:1px,color:#000
classDef external fill:#FFCC99,stroke:#D79B00,stroke-width:1px,color:#000
classDef hidden fill:none,stroke:none
classDef legendBox fill:white,stroke:#999,stroke-width:1px,color:#000

%% Network diagram
subgraph Gateways[" "]
    direction LR
    Gateway_1["gateway-1"]
end

subgraph Spines[" "]
    direction LR
    subgraph Spine_01_Group [" "]
        direction TB
        Spine_01["spine-01<br>spine"]
    end
    subgraph Spine_02_Group [" "]
        direction TB
        Spine_02["spine-02<br>spine"]
    end
end

subgraph Leaves[" "]
    direction LR
    subgraph Eslag_1 ["eslag-1"]
        direction LR
        Leaf_01["leaf-01<br>server-leaf"]
        Leaf_02["leaf-02<br>server-leaf"]
    end

    Leaf_03["leaf-03<br>server-leaf"]
end

subgraph Servers[" "]
    direction TB
    Server_03["server-03"]
    Server_01["server-01"]
    Server_02["server-02"]
    Server_04["server-04"]
    Server_05["server-05"]
    Server_06["server-06"]
end

%% Connections

%% Gateway connections
Gateway_1 ---|"enp2s2↔E1/7"| Spine_02
Gateway_1 ---|"enp2s1↔E1/7"| Spine_01

%% Spine_01 -> Leaves
Spine_01 ---|"E1/4↔E1/1<br>E1/5↔E1/2"| Leaf_01
Spine_01 ---|"E1/6↔E1/4<br>E1/5↔E1/3"| Leaf_02
Spine_01 ---|"E1/4↔E1/5<br>E1/5↔E1/6"| Leaf_03

%% Spine_02 -> Leaves
Spine_02 ---|"E1/7↔E1/3<br>E1/8↔E1/4"| Leaf_02
Spine_02 ---|"E1/6↔E1/1<br>E1/7↔E1/2"| Leaf_01
Spine_02 ---|"E1/6↔E1/5<br>E1/7↔E1/6"| Leaf_03

%% Leaves -> Servers
Leaf_01 ---|"enp2s1↔E1/2"| Server_02
Leaf_01 ---|"enp2s1↔E1/1"| Server_01
Leaf_01 ---|"enp2s1↔E1/3"| Server_03

Leaf_02 ---|"enp2s1↔E1/3<br>enp2s2↔E1/4"| Server_04
Leaf_02 ---|"enp2s2↔E1/2"| Server_02
Leaf_02 ---|"enp2s2↔E1/1"| Server_01

Leaf_03 ---|"enp2s1↔E1/2<br>enp2s2↔E1/3"| Server_06
Leaf_03 ---|"enp2s1↔E1/1"| Server_05

%% Mesh connections

%% External connections

subgraph Legend["Network Connection Types"]
    direction LR
    %% Create invisible nodes for the start and end of each line
    L1(( )) --- |"Fabric Links"| L2(( ))
    L5(( )) --- |"Bundled Server Links (x2)"| L6(( ))
    L7(( )) --- |"Unbundled Server Links"| L8(( ))
    L9(( )) --- |"ESLAG Server Links"| L10(( ))
    L11(( )) --- |"Gateway Links"| L12(( ))
    P1(( )) --- |"Label Notation: Downstream ↔ Upstream"| P2(( ))
end

class Gateway_1 gateway
class Spine_01,Spine_02 spine
class Leaf_01,Leaf_02,Leaf_03 leaf
class Server_03,Server_01,Server_02,Server_04,Server_05,Server_06 server
class Eslag_1 eslag
class L1,L2,L3,L4,L5,L6,L7,L8,L9,L10,L11,L12,P1,P2 hidden
class Legend legendBox
linkStyle default stroke:#666,stroke-width:2px
linkStyle 0,1 stroke:#CC9900,stroke-width:2px
linkStyle 2,3,4,5,6,7 stroke:#CC3333,stroke-width:4px
linkStyle 11,14 stroke:#66CC66,stroke-width:4px
linkStyle 8,9,12,13 stroke:#CC9900,stroke-width:4px,stroke-dasharray:5 5
linkStyle 10,15 stroke:#999999,stroke-width:2px
linkStyle 16 stroke:#B85450,stroke-width:2px
linkStyle 17 stroke:#82B366,stroke-width:2px
linkStyle 18 stroke:#000000,stroke-width:2px
linkStyle 19 stroke:#CC9900,stroke-width:2px,stroke-dasharray:5 5
linkStyle 20 stroke:#CC9900,stroke-width:2px
linkStyle 21 stroke:#FFFFFF

%% Make subgraph containers invisible
style Gateways fill:none,stroke:none
style Spines fill:none,stroke:none
style Leaves fill:none,stroke:none
style Servers fill:none,stroke:none
style Spine_01_Group fill:none,stroke:none
style Spine_02_Group fill:none,stroke:none

You can jump to the instructions to start VLAB, or see the next section for customizing the topology.

Mesh

To run the mesh topology, which does away with spine switches and connects leaves directly to each other, use the --mesh-links-count flag. This flag allows you to specify how many mesh links should be created between each pair of leaves. For example, to create a mesh topology with 2 links between each pair of leaves, run:

ubuntu@docs:~$ hhfab vlab gen --mesh-links-count 2
13:24:58 INF Hedgehog Fabricator version=v0.41.3
13:24:58 INF Building VLAB wiring diagram fabricMode=spine-leaf
13:24:58 INF >>> spinesCount=0 fabricLinksCount=0 meshLinksCount=2
13:24:58 INF >>> eslagLeafGroups=2
13:24:58 INF >>> mclagLeafsCount=0 mclagSessionLinks=0 mclagPeerLinks=0
13:24:58 INF >>> orphanLeafsCount=1
13:24:58 INF >>> mclagServers=2 eslagServers=2 unbundledServers=1 bundledServers=1
13:24:58 INF Generated wiring file name=vlab.generated.yaml

The default topology generated in this case will have 2 ESLAG leaves and 1 orphan leaf. Below is the corresponding diagram:

graph TD

%% Style definitions
classDef gateway fill:#FFF2CC,stroke:#999,stroke-width:1px,color:#000
classDef spine   fill:#F8CECC,stroke:#B85450,stroke-width:1px,color:#000
classDef leaf    fill:#DAE8FC,stroke:#6C8EBF,stroke-width:1px,color:#000
classDef server  fill:#D5E8D4,stroke:#82B366,stroke-width:1px,color:#000
classDef mclag   fill:#F0F8FF,stroke:#6C8EBF,stroke-width:1px,color:#000
classDef eslag   fill:#FFF8E8,stroke:#CC9900,stroke-width:1px,color:#000
classDef external fill:#FFCC99,stroke:#D79B00,stroke-width:1px,color:#000
classDef hidden fill:none,stroke:none
classDef legendBox fill:white,stroke:#999,stroke-width:1px,color:#000

%% Network diagram
subgraph Leaves[" "]
    direction LR
    subgraph ESLAG [ESLAG]
        direction LR
        Leaf_01["leaf-01<br>server-leaf"]
        Leaf_02["leaf-02<br>server-leaf"]
    end

    Leaf_03["leaf-03<br>server-leaf"]
end

subgraph Servers[" "]
    direction TB
    Server_03["server-03"]
    Server_01["server-01"]
    Server_02["server-02"]
    Server_04["server-04"]
    Server_05["server-05"]
    Server_06["server-06"]
end

%% Connections

%% Leaves -> Servers
Leaf_01 ---|"enp2s1↔E1/3"| Server_03
Leaf_01 ---|"enp2s1↔E1/1"| Server_01
Leaf_01 ---|"enp2s1↔E1/2"| Server_02

Leaf_02 ---|"enp2s2↔E1/1"| Server_01
Leaf_02 ---|"enp2s2↔E1/2"| Server_02
Leaf_02 ---|"enp2s1↔E1/3<br>enp2s2↔E1/4"| Server_04

Leaf_03 ---|"enp2s1↔E1/1"| Server_05
Leaf_03 ---|"enp2s1↔E1/2<br>enp2s2↔E1/3"| Server_06

%% Mesh connections
Leaf_01 ---|"E1/6↔E1/5<br>E1/5↔E1/4"| Leaf_02
Leaf_02 ---|"E1/6↔E1/7<br>E1/7↔E1/8"| Leaf_03
Leaf_01 ---|"E1/4↔E1/6<br>E1/5↔E1/7"| Leaf_03

%% External connections

subgraph Legend["Network Connection Types"]
    direction LR
    %% Create invisible nodes for the start and end of each line
    L15(( )) --- |"Mesh Links"| L16(( ))
    L5(( )) --- |"Bundled Server Links"| L6(( ))
    L7(( )) --- |"Unbundled Server Links"| L8(( ))
    L9(( )) --- |"ESLAG Server Links"| L10(( ))
    P1(( )) --- |"Label Notation: Downstream ↔ Upstream"| P2(( ))
end

class Leaf_01,Leaf_02,Leaf_03 leaf
class Server_03,Server_01,Server_02,Server_04,Server_05,Server_06 server
class ESLAG eslag
class L1,L2,L3,L4,L5,L6,L7,L8,L9,L10,L11,L12,P1,P2,L15,L16 hidden
class Legend legendBox
linkStyle default stroke:#666,stroke-width:2px
linkStyle 8,9,10 stroke:#0078D4,stroke-width:4px
linkStyle 5,7 stroke:#66CC66,stroke-width:4px
linkStyle 1,2,3,4 stroke:#CC9900,stroke-width:4px,stroke-dasharray:5 5
linkStyle 0,6 stroke:#999999,stroke-width:2px
linkStyle 11 stroke:#0078D4,stroke-width:2px
linkStyle 12 stroke:#82B366,stroke-width:2px
linkStyle 13 stroke:#000000,stroke-width:2px
linkStyle 14 stroke:#CC9900,stroke-width:2px,stroke-dasharray:5 5
linkStyle 15 stroke:#FFFFFF

%% Make subgraph containers invisible
style Leaves fill:none,stroke:none
style Servers fill:none,stroke:none

Gateway

The gateway is enabled by adding the --gw flag to hhfab init. It connects to two spines in spine-leaf topology or two leaves in mesh topology. The number of uplinks can be controlled using flags on hhfab vlab gen.

Lightweight Spine-Leaf

A default spine-leaf topology in VLAB requests more CPU and RAM than is commonly available. The lightweight topology requests 22 vCPUs and 23 GiB of RAM, it is 6 virtual machines, and still allows for traffic to transit a spine. The lightweight spine-leaf topology is 2 ESLAG leaves, 1 spine, 1 ESLAG Host, and 1 normal host. To launch the lightweight spine-leaf topology use the following command:

ubuntu@docs:~$ hhfab vlab gen --eslag-leaf-groups=2 --spines-count=1 --bundled-servers=0 --eslag-servers=1 --unbundled-servers=1
20:10:16 INF Hedgehog Fabricator version=v0.42.0
20:10:16 INF Building VLAB wiring diagram fabricMode=spine-leaf
20:10:16 INF >>> spinesCount=1 fabricLinksCount=2 meshLinksCount=0
20:10:16 INF >>> eslagLeafGroups=2
20:10:16 INF >>> mclagLeafsCount=0 mclagSessionLinks=0 mclagPeerLinks=0
20:10:16 INF >>> orphanLeafsCount=0
20:10:16 INF >>> mclagServers=2 eslagServers=1 unbundledServers=1 bundledServers=0
20:10:16 INF Generated wiring file name=vlab.generated.yaml

The lightweight spine-leaf topology looks like this:

graph TD

%% Style definitions
classDef spine   fill:#F8CECC,stroke:#B85450,stroke-width:1px,color:#000
classDef leaf    fill:#DAE8FC,stroke:#6C8EBF,stroke-width:1px,color:#000
classDef server  fill:#D5E8D4,stroke:#82B366,stroke-width:1px,color:#000
classDef eslag   fill:#FFF8E8,stroke:#CC9900,stroke-width:1px,color:#000
classDef hidden fill:none,stroke:none
classDef legendBox fill:white,stroke:#999,stroke-width:1px,color:#000

%% Network diagram
subgraph Spines[" "]
    direction LR
    subgraph Spine_01_Group [" "]
        direction TB
        Spine_01["spine-01<br>spine"]
    end
end

subgraph Leaves[" "]
    direction LR
    subgraph Eslag_1 ["eslag-1"]
        direction LR
        Leaf_01["leaf-01<br>server-leaf"]
        Leaf_02["leaf-02<br>server-leaf"]
    end

end

subgraph Servers[" "]
    direction TB
    Server_02["server-02"]
    Server_01["server-01"]
end

%% Connections

%% Spine_01 -> Leaves
Spine_01 --- Leaf_01
Spine_01 --- Leaf_02

%% Leaves -> Servers
Leaf_01 --- Server_01
Leaf_01 --- Server_02
Leaf_02 --- Server_01

subgraph Legend["Network Connection Types"]
    direction LR
    %% Create invisible nodes for the start and end of each line
    L1(( )) --- |"Fabric Links"| L2(( ))
    L7(( )) --- |"Unbundled Server Links"| L8(( ))
    L9(( )) --- |"ESLAG Server Links"| L10(( ))
end

class Spine_01 spine
class Leaf_01,Leaf_02 leaf
class Server_02,Server_01 server
class Eslag_1 eslag
class L1,L2,L7,L8,L9,L10 hidden
class Legend legendBox
linkStyle default stroke:#666,stroke-width:2px
linkStyle 0,1 stroke:#CC3333,stroke-width:4px
linkStyle 2,4 stroke:#CC9900,stroke-width:4px,stroke-dasharray:5 5
linkStyle 3 stroke:#999999,stroke-width:2px
linkStyle 5 stroke:#B85450,stroke-width:2px
linkStyle 6 stroke:#000000,stroke-width:2px
linkStyle 7 stroke:#CC9900,stroke-width:2px,stroke-dasharray:5 5

%% Make subgraph containers invisible
style Spines fill:none,stroke:none
style Leaves fill:none,stroke:none
style Servers fill:none,stroke:none
style Spine_01_Group fill:none,stroke:none

There are many customization options available for the VLAB topology. For a complete list of options, run hhfab vlab gen -h.

Additionally, you can pass extra Fabric configuration items using flags on init command or by passing a configuration file. For more information, refer to the Fabric Configuration section.

Once you have initialized the VLAB, download the artifacts and build the installer using hhfab build. This command automatically downloads all required artifacts from the OCI registry and builds the installer and all other prerequisites for running the VLAB.

Build the Installer and Start VLAB

To build and start the virtual machines, use hhfab vlab up. This command runs in the foreground and does not return, which allows you to stop all VLAB VMs by pressing Ctrl + C. 

ubuntu@docs:~$ hhfab vlab up
17:25:31 INF Hedgehog Fabricator version=v0.43.1
17:25:31 INF Wiring hydrated successfully mode=if-not-present
17:25:31 INF VLAB config loaded file=vlab/config.yaml
17:25:31 INF Downloader cache=/home/ubuntu/.hhfab-cache/v1 repo=ghcr.io prefix=githedgehog
17:25:31 INF Building control node installers
17:25:31 INF Building installer name=control-1 type=control mode=iso
17:25:31 INF Adding recipe bin and config to installer name=control-1 type=control mode=iso
17:25:33 INF Adding k3s and tools to installer name=control-1 type=control mode=iso
17:25:33 INF Adding toolbox to installer name=control-1 type=control mode=iso
17:25:34 INF Adding zot to installer name=control-1 type=control mode=iso
17:25:34 INF Adding flatcar upgrade bin to installer name=control-1 type=control mode=iso
17:25:34 INF Adding cert-manager to installer name=control-1 type=control mode=iso
17:25:34 INF Adding bash-completion to installer name=control-1 type=control mode=iso control=control-1
17:25:34 INF Adding config and wiring files to installer name=control-1 type=control mode=iso
17:25:34 INF Adding CLIs to installer name=control-1 type=control mode=iso
17:25:35 INF Building installer image, may take up to 5-10 minutes name=control-1 type=control mode=iso
...
17:25:48 INF Taps and bridge are ready count=7
17:25:48 INF Preparing new vm=control-1 type=control
17:26:28 INF Preparing new vm=gateway-1 type=gateway
17:27:12 INF Preparing new vm=server-01 type=server
17:27:14 INF Preparing new vm=server-02 type=server
17:27:16 INF Preparing new vm=server-03 type=server
17:27:17 INF Preparing new vm=server-04 type=server
17:27:19 INF Preparing new vm=server-05 type=server
17:27:21 INF Preparing new vm=server-06 type=server
17:27:23 INF Preparing new vm=leaf-01 type=switch
17:27:23 INF Preparing new vm=leaf-02 type=switch
17:27:23 INF Preparing new vm=leaf-03 type=switch
17:27:23 INF Preparing new vm=spine-01 type=switch
17:27:23 INF Preparing new vm=spine-02 type=switch
17:27:24 INF Starting VMs count=13 cpu="46 vCPUs" ram="42496 MB" disk="460 GB"
...
17:35:11 INF install(control-1): Jan 30 17:35:11 control-1 hhfab-recipe[1529]: Jan 30 17:35:11.024 INF Control node installation complete
17:35:21 INF All VMs are ready
17:35:21 INF All K8s nodes are ready
17:35:21 INF VLAB is ready
When the message INF VLAB is ready appears, the installer has finished. After this, you can get into the control node and other VMs to watch the Fabric coming up and switches getting provisioned. See Accessing the VLAB.

Enable Outside connectivity from VLAB VMs

By default, all test server VMs are isolated and have no connectivity to the host or the Internet. You can configure enable connectivity using hhfab vlab up --restrict-servers=false to allow the test servers to access the Internet and the host. When you enable connectivity, VMs get a default route pointing to the host, which means that in case of the VPC peering you need to configure test server VMs to use the VPC attachment as a default route (or just some specific subnets).

Accessing the VLAB

The hhfab vlab command provides ssh and serial subcommands to access the VMs. You can use ssh to get into the control node and test servers after the VMs are started. You can use serial to get into the switch VMs while they are provisioning and installing the software. After switches are installed you can use ssh to get into them.

You can select device you want to access or pass the name using the --vm flag.

ubuntu@docs:~$ hhfab vlab ssh
Use the arrow keys to navigate: ↓ ↑ → ←  and / toggles search
Select target for ssh:
  🦔 control-1
  gateway-1
  leaf-01
  leaf-02
  leaf-03
  server-01
  server-02
  server-03
  server-04
  server-05
  server-06
  spine-01
  spine-02

Default credentials

Fabricator creates default users and keys for you to login into the control node and test servers as well as for the SONiC Virtual Switches.

The default user with password-less sudo for the control node and test servers is core with password HHFab.Admin!. The admin user with full access and password-less sudo for the switches is admin with password HHFab.Admin!. The read-only, non-sudo user with access to the switch CLI is op with password HHFab.Op!.

Use Kubectl to Interact with the Fabric

On the control node you have access to kubectl, Fabric CLI, and k9s to manage the Fabric. To view information about the switches run kubectl get agents -o wide. After the control node is available it usually takes about 10-15 minutes for the switches to get installed.

After the switches are provisioned, the command returns something like this:

core@control-1 ~ $ kubectl get agents -o wide
NAME       ROLE          DESCR           HWSKU                      HEARTBEAT   APPLIED   APPLIEDG   CURRENTG   VERSION   SOFTWARE                ATTEMPT   ATTEMPTG   AGE
leaf-01    server-leaf   VS-01 ESLAG 1   DellEMC-S5248f-P-25G-DPB   11s         2m59s     1          1          v0.96.2   4.5.0-Enterprise_Base   2m59s     1          10m
leaf-02    server-leaf   VS-02 ESLAG 1   DellEMC-S5248f-P-25G-DPB   29s         3m17s     1          1          v0.96.2   4.5.0-Enterprise_Base   3m17s     1          10m
leaf-03    server-leaf   VS-03           DellEMC-S5248f-P-25G-DPB   19s         3m7s      1          1          v0.96.2   4.5.0-Enterprise_Base   3m7s      1          10m
spine-01   spine         VS-04           DellEMC-S5248f-P-25G-DPB   28s         3m16s     1          1          v0.96.2   4.5.0-Enterprise_Base   3m16s     1          10m
spine-02   spine         VS-05           DellEMC-S5248f-P-25G-DPB   17s         3m6s      1          1          v0.96.2   4.5.0-Enterprise_Base   3m6s      1          10m

The Heartbeat column shows how long ago the switch has sent the heartbeat to the control node. The Applied column shows how long ago the switch has applied the configuration. AppliedG shows the generation of the configuration applied. CurrentG shows the generation of the configuration the switch is supposed to run. Different values for AppliedG and CurrentG mean that the switch is in the process of applying the configuration.

At that point Fabric is ready and you can use kubectl and kubectl fabric to manage the Fabric. You can find more about managing the Fabric in the Running Demo and User Guide sections.

Getting main Fabric objects

You can list the main Fabric objects by running kubectl get on the control node. You can find more details about using the Fabric in the User Guide, Fabric API and Fabric CLI sections.

For example, to get the list of switches, run:

core@control-1 ~ $ kubectl get switch
NAME       PROFILE   ROLE          DESCR           GROUPS        AGE
leaf-01    vs        server-leaf   VS-01 ESLAG 1   ["eslag-1"]   10m
leaf-02    vs        server-leaf   VS-02 ESLAG 1   ["eslag-1"]   10m
leaf-03    vs        server-leaf   VS-03                         10m
spine-01   vs        spine         VS-04                         10m
spine-02   vs        spine         VS-05                         10m

Similarly, to get the list of servers, run:

core@control-1 ~ $ kubectl get server
NAME        TYPE      DESCR                        AGE
control-1   control   Control node                 10m
server-01             S-01 ESLAG leaf-01 leaf-02   10m
server-02             S-02 ESLAG leaf-01 leaf-02   10m
server-03             S-03 Unbundled leaf-01       10m
server-04             S-04 Bundled leaf-02         10m
server-05             S-05 Unbundled leaf-03       10m
server-06             S-06 Bundled leaf-03         10m

For connections, use:

core@control-1 ~ $ kubectl get connection
NAME                                 TYPE        AGE
server-01--eslag--leaf-01--leaf-02   eslag       10m
server-02--eslag--leaf-01--leaf-02   eslag       10m
server-03--unbundled--leaf-01        unbundled   10m
server-04--bundled--leaf-02          bundled     10m
server-05--unbundled--leaf-03        unbundled   10m
server-06--bundled--leaf-03          bundled     10m
spine-01--fabric--leaf-01            fabric      10m
spine-01--fabric--leaf-02            fabric      10m
spine-01--fabric--leaf-03            fabric      10m
spine-01--gateway--gateway-1         gateway     10m
spine-02--fabric--leaf-01            fabric      10m
spine-02--fabric--leaf-02            fabric      10m
spine-02--fabric--leaf-03            fabric      10m
spine-02--gateway--gateway-1         gateway     10m

For IPv4 and VLAN namespaces, use:

core@control-1 ~ $ kubectl get ipns
NAME      SUBNETS           AGE
default   ["10.0.0.0/16"]   10m

core@control-1 ~ $ kubectl get vlanns
NAME      AGE
default   10m

Reset VLAB

If VLAB is currently running, press Ctrl + C to stop it. To reset VLAB and start over run hhfab init -f. This option forces the process to overwrite your existing configuration in fab.yaml.

Next steps