FlexSwitch on Voyager

This guide provides guidance for configuring the various transponder modes on a Voyager switch running FlexSwitch.

Voyager Overview

Voyager is the industry’s first open-source packet-optical transponder platform combining dense wavelength division multiplexing (DWDM) technology with switching and routing functionality. It takes in client data signals (e.g., 100 GbE) from switches or routers, and packages these signals into the proper signaling format for metro or long-haul transmission.

Architecture

The figure below depicts the internal architecture of the Voyager platform. It consists of two 100G-400G flexible rate DWDM modules connected to an advanced L2/L3 Broadcom forwarding engine. Each DWDM can be configured for QPSK, 8-QAM and 16-QAM modulation formats with coherent reception and digital dispersion and PMD compensation.

Voyager Diagram

Voyager comprises two optical modules (DWDM: 0 and DWDM: 1) and a Broadcom BCM 56962 switch with L2/L3 capability.

DWDM Configuration

When running in with IndependentLaneMode, the DWDM module can be viewed as two independent modems sharing a single management interface. This allows the network interfaces to terminate on different remote-end DWDM module interfaces. When independent lane mode is disabled, the DWM module operates as a single transponder where the transmit signal is split across both network interfaces. In this mode (coupled-mode), both network interfaces must be connected to the same remote network interfaces (i.e., network interface 0 connected to remote network interface 0 and network interface 1 connected to remote network interface 1). By default, the DWDM module is configured with independent lanes enabled.

The DWDM module has configurable crossbar switch between the network interfaces and the client interfaces. Additionally, the client transmit and client receive signals can be configured independently. The client interfaces are number 0, 1, 2, and 3. Each network interface has two 100G-capable tributary lane. The lane numbers 0, 1, 2, and 3 directly map to a network interface’s Tributary map. The client interface to network lane values are configurable.

The lane numbers 0, 1, 2, and 3 directly map to a network interface’s Tributary map. The client interface to network lane values are configurable. The default mappings are as shown below.

DWDM Module

Default Port Mapping

  • Ports fpPort13 through fpPort20 are 'internal' ports connecting from the broadcom chip to the optical modules

The following is the default port mapping:

  • fpPort 13 -- (fixed) - dwdmModule 0 (ClntIntf 0) ---- (configurable) — (NwIntf) L3
  • fpPort 14 -- (fixed) - dwdmModule 0 (ClntIntf 1) ---- (configurable) — (NwIntf) L3
  • fpPort 15 -- (fixed) - dwdmModule 0 (ClntIntf 2) ---- (configurable) — (NwIntf) L4
  • fpPort 16 -- (fixed) - dwdmModule 0 (ClntIntf 3) ---- (configurable) — (NwIntf) L4
  • fpPort 17 -- (fixed) - dwdmModule 1 (ClntIntf 0) ---- (configurable) — (NwIntf) L1
  • fpPort 18 -- (fixed) - dwdmModule 1 (ClntIntf 1) ---- (configurable) — (NwIntf) L1
  • fpPort 19 -- (fixed) - dwdmModule 1 (ClntIntf 2) ---- (configurable) — (NwIntf) L2
  • fpPort 20 -- (fixed) - dwdmModule 1 (ClntIntf 3) ---- (configurable) — (NwIntf) L2

Voyager Transponder Modes

Transponder modes are a set of predefined configurations. The full details for each mode are described below.

The purpose of these modes is to make the Voyager switch act like an Ethernet-to-optical mux where traffic received on the front panel ports are mapped directly to a network port. It allows administrators with little to no networking background to quickly deploy the platform for this specific use case.

The InServiceWire mode maps the first 8 100G ports to the 4x200G optical lanes.

The InServiceOverSub (over-subscribed mode) maps all twelve front panel 100G ports to the 4x200G optical lanes. Since there is 1200G potential bandwidth on the client side mapped to only 800G bandwidth on the optical side, it is oversubsribed. As with all oversubscription cases, the assumption is that not all client side ports are used at full capacity 100% of the time so traffic loss due to congestion is minimum.

Voyager transponder modes comprise the following:

  • InServiceWire mode: No additional VLANs or L3 configurations should be configured. Doing so can affect the connectivity between upstream and downstream interfaces.

Note

Breakout cables are not supported in this mode.

  • InServiceOverSub: No additional VLANs or L3 configurations should be configured. Doing so can affect the connectivity between upstream and downstream interfaces.

Note

Breakout cables are not supported in this mode.

  • OutOfService: No configuration restrictions in this mode. When switching to this mode, all front-panel interfaces are disabled.
  • InServicePacketOptical: No configuration restrictions in this mode. When switching to this mode, all front-panel interfaces are enabled.

InServiceWire Mode

The InServiceWire Mode creates a one-to-one mapping of traffic from the front panel interface (fpPort1 - 8) to the internal interfaces (fpPort 13 - 20). This is accomplished by creating 8 unique VLANs (vlan 2 - vlan 8) and assigning each pair of ports to the same vlan. Therefore, all untagged traffic received on fpPort1 will be sent out fpPort13.

VLAN Ports
2 fpPort1 (untagged), fpPort13 (untagged)
3 fpPort2 (untagged), fpPort14 (untagged)
4 fpPort3 (untagged), fpPort15 (untagged)
5 fpPort4 (untagged), fpPort16 (untagged)
6 fpPort5 (untagged), fpPort17 (untagged)
7 fpPort6 (untagged), fpPort18 (untagged)
8 fpPort7 (untagged), fpPort19 (untagged)
9 fpPort8 (untagged), fpPort20 (untagged)

InServiceOverSub Mode

The InServiceOverSub creates a many-to-one mapping of traffic from the front panel interface (fpPort1 - 12) to the internal interfaces (fpPort 13 - 20). This is accomplished by creating 12 VLANs and assigned each pair of ports to the same vlan. In this configuration, ports fpPort15-18 are overloading with two downstream interfaces as shown below

VLAN Ports
2 fpPort1 (untagged), fpPort13 (tagged)
3 fpPort2 (untagged), fpPort14 (tagged)
4 fpPort3 (untagged), fpPort15 (tagged)
5 fpPort4 (untagged), fpPort16 (tagged)
6 fpPort5 (untagged), fpPort17 (tagged)
7 fpPort6 (untagged), fpPort18 (tagged)
8 fpPort7 (untagged), fpPort19 (tagged)
9 fpPort8 (untagged), fpPort20 (tagged)
10 fpPort9 (untagged),fpPort15 (tagged)
11 fpPort10 (untagged),fpPort16 (tagged)
12 fpPort11 (untagged),fpPort17 (tagged)
13 fpPort12 (untagged),fpPort18 (tagged)

OutOfService

This mode is currently no-op. Changing the transponder mode to OutOfService sets all front-panel interfaces to the admin-down state. You can admin-up interfaces as needed and configure VLANs, routing protocols, etc., as needed.

Note

This mode for using Voyager as a normal L2/L3 switch.

InServicePacketOptical

This mode is currently no-op. Changing the transponder mode to InServicePacketOptical sets all front-panel interfaces to the admin-up state

Note

This mode for using Voyager as a normal L2/L3 switch.

InServiceRegen

In this mode all front panel ports are disabled (fpPort1 - 20) and the optical module client interfaces are placed in loopback mode.