Section 17.1.4 – Westermo RedFox Series User Manual

Page 367

Advertising
background image

Westermo OS Management Guide

Version 4.17.0-0

In WeOS v4.17.0, the LACP system priority is set to 0x8000 (hex), system iden-
tifier is set to the MAC address of the first member port of the aggregate, the
port priority is set to 0x8000 (hex), and the operational key is set to the config-
ured aggregate identifier (see

sections 17.2

and

17.3

). More information about

aggregate selection can be found in IEEE 802.3ad/802.1AX [

13

].

17.1.4

Link Aggregates and Low layer protocols

17.1.4.1

Link Aggregation and VLAN

Ethernet and DSLorts on WeOS units are associated (untagged or tagged with one
or more VLANs as described in

chapter 13

. Link aggregates can not be mapped

directly to VLANs. Instead the user must add each of the aggregate member
ports to the intended VLAN(s).

For the setup in

fig. 17.2

, the physical ports 1-4 are mapped tagged (”tagged

1-4”) to VLANs 1&2 rather than the aggregates (i.e., ”tagged a1,a2” is not
possible as of WeOS v4.17.0). An extract of the configuration file is shown below.

Example

vlan 1

name vlan1
untagged 5-7
tagged 1-4
end

vlan 2

name vlan2
untagged 8-10
tagged 1-4
end

17.1.4.2

Link Aggregation and Link Alarms

As described in

section 24.1

the operational state (Up/Down) of Ethernet and DSL

ports can be used as alarm triggers, i.e., link alarms. When a port is a member of
a link aggregate, it is still possible to define link alarms for the individual member
ports. It is also possible to create link alarms for the aggregates.

Below is a CLI configuration example where a link alarm is configured for aggre-
gate a1. The aggregate has state Down when all its member ports has state

➞ 2015 Westermo Teleindustri AB

367

Advertising
This manual is related to the following products: