Step 3: Verify Installation and Discover VMBus UUIDs

This step waits for SSR 7.1.4 to finish installing on both VMs, confirms both routers appear on the conductor, and discovers the VMBus UUIDs for the WAN and LAN interfaces on each router. You must record these UUIDs before configuring the routers on the conductor.

Wait for Installation to Complete

The BYOL software installs SSR 7.1.4 automatically after each VM is deployed. This process takes approximately 20 minutes after the VM first starts. Both VMs install in parallel, so you do not need to wait for one to finish before checking the other.

The installation is complete when both routers appear in show assets on the conductor.

Verify the Routers Are Running

On each router, enter the SSR PCLI and confirm the system is running:

su admin

Enter your password at the prompt.

admin@node0.azure-hub-router# show system

The status should return running. Repeat for the spoke router:

admin@node0.azure-spoke-router# show system

Verify the Routers Appear on the Conductor

After installation, each router contacts the conductor and appears as a pending asset.

In the Conductor GUI, select Configuration.
Select Authority and look under Routers.
Both azure-hub-router and azure-spoke-router should appear with pending associations.

If a router does not appear within 15 minutes of installation completing, verify that:

The conductor's public IP is reachable from the router WAN subnet over ports 930, 4505, and 4506.
The correct conductor IP was supplied in the deployment template or cloud-init block.

Network Interface Layout

The BYOL conductor-managed router template deploys a VM with network interfaces attached in the following order:

Linux Interface	Azure NIC Name	Subnet
ge-0-0	azure-spoke-router-public	ssr-spoke-wan
ge-0-1	azure-spoke-router-private	ssr-spoke-lan

Discover VMBus UUIDs

In Azure, device interfaces are identified by VMBus UUID rather than PCI address. You must discover the VMBus UUID for each WAN and LAN interface before configuring the routers on the conductor.

Perform the following steps on each router separately. Record the UUIDs — you will need them in Step 4.

Identify VMBus UUIDs From the Router VM

Open the devicemap to see the VMBus UUID mapping for the attached interfaces.

cat /var/lib/128technology/devicemap.json | jq

Exit the CLI and run sudo from the linux shell before opening the devicemap.

admin@node.router# quit 
[t128@ssr-hub-router-1 ~]$ sudo cat /var/lib/128technology/devicemap.json | jq 

{ 
  "source": "bootstrapper", 
  "ethernet": [ 
    { 
      "type": "WAN", 
      "name": "ge-0-0", 
      "description": "", 
      "bcpNetwork": { 
        "standaloneBranch": { 
          "name": "wan1" 
        } 
      }, 

      "pciAddress": null, 
      "vmbusId": "002248be-be61-0022-48be-be61002248be" 
    }, 
    { 
      "type": "LAN", 
      "name": "ge-0-1", 
      "description": "", 
      "bcpNetwork": { 
        "standaloneBranch": { 
          "name": "lan2" 
        } 
      }, 

      "pciAddress": null, 
      "vmbusId": "002248be-bb15-0022-48be-bb15002248be" 
    } 
  ], 
  "lte": [] 
} 

Take note of the device names and associated VMBus ID.

VMBus UUID Reference Table

Record your discovered UUIDs using the following table. You will substitute these values throughout Step 4.

Router	Interface	Role	Subnet	VMBus UUID
`azure-hub-router`	`ge-0-0`	WAN	`ssr-hub-wan`	`<hub-wan-vmbus-uuid>`
`azure-hub-router`	`ge-0-1`	LAN	`ssr-hub-lan`	`<hub-lan-vmbus-uuid>`
`azure-spoke-router`	`ge-0-0`	WAN	`ssr-spoke-wan`	`<spoke-wan-vmbus-uuid>`
`azure-spoke-router`	`ge-0-1`	LAN	`ssr-spoke-lan`	`<spoke-lan-vmbus-uuid>`

Next Step

Proceed to Step 4 — Configure Hub and Spoke Routers.

Wait for Installation to Complete​

Verify the Routers Are Running​

Verify the Routers Appear on the Conductor​

Network Interface Layout​

Discover VMBus UUIDs​

Identify VMBus UUIDs From the Router VM​

VMBus UUID Reference Table​

Next Step​