Znyx Networks bh5700 manual Layer 3 Switch Configuration

Layer 3 Switch Configuration

The previous section outlines the Layer 2 switch configuration that is automatically configured when you initially bring up the OpenArchitect switch. In order to communicate between Layer2 interfaces, you must properly setup routing.

The steps to build a Layer 2 switch involve creating a group of switch ports in a VLAN (or Layer 2 switching domain) and bringing that interface up. zconfig creates the VLAN group of switch ports as well as a network interface. Use ifconfig(1M) on the network interface to bring up the VLAN group with Layer 2 switching. Layer 3 routing information is then used to route between the Layer 2 network devices.

Take a simple example of two VLANs configured on the switch, each with four ports. First teardown any existing configuration,

zconfig –t

Use zconfig to create two new VLANs, each with four ports, and untag them,

zconfig zhp0: vlan1=zre1..4

zconfig zre1..4=untag1 zconfig zhp1: vlan2=zre5..8

zconfig zre5..8=untag2

Now, use ifconfig to assign each zhp interface an IP address,

ifconfig zhp0 10.0.0.1 ifconfig zhp1 11.0.0.1

At this point, the Linux host has enough information to route between the networks of the directly attached interfaces, 10.0.0.0 via zhp0, and 11.0.0.0 via zhp1.

The next step is to enable the zl3d daemon to move that routing information from the host to the Ethernet Switch Blade switching tables in silicon. Once enabled, zl3d will monitor the Linux routing tables for changes in configuration and update the switch silicon tables. Start zl3d to update the switch tables:

zl3d zhp0 zhp1

The Ethernet Switch Blade switch is now configured as a Layer3 switch that can route between two Layer2 devices in silicon.

Using the S50layer3 Script

To modify the configuration to a Layer 3 switch, remove the S50layer2 file from the /etc/rcZ.d directory, and replace it with the example script file, S50layer3.

Ethernet Switch Blade User's Guide release 3.2.2j page 52