
IndexIndex
No other types of flexible blocks or nodes can be included in the chain, or
send traffic through the EFN324.
Only one uplink is permitted from the daisy chain. Rapid spanning tree is
not supported for embedded daisy chained EFN324 Ethernet access
switches.
The EMP and PEM do not know the order in which the EFN Ethernet
access switches are connected. The EMP and PEM simply see each EFN
Ethernet access switch as an independent flexible block.
PEM only configures the service VLANs on the EFN that the Enduser is
connected to. In EFN Ethernet access switches where the service VLAN is
not configured, the traffic is handled by the transit switching domain.
PEM only configures Quality of Service on the EFN that the Enduser is
connected to. In the remaining EFN324 Ethernet access switches, traffic is
forwarded as “best effort”, in other words, with the lowest of each QoS
parameter.
A transit switching domain must be configured manually in the Ethernet
access switches. VLAN 2 is reserved for this. A transit link for the
management VLAN switching domain must also be configured. More
information on this is given in the CLI commands below.
The initial configuration of the embedded EFN and the configuration of a daisy
chain are included in the
EFN324 Installation Guide
.
To configure the uplink and transit link for the management VLAN for the
chain, enter the following commands in
each
EFN:
set vlan 1 transit_link ethernet_port 25 uplink
ethernet_port 26
To configure a transit switching domain manually in the Ethernet access
switches, enter the following commands in
each
EFN, except the last EFN in
the chain:
set vlan 2 description transit
set node_control default_vlan vlan 2
connect vlan 2 ethernet_port 25,26
set vlan 2 transit_link ethernet_port 25 uplink
ethernet_port 26
Содержание EFN324
Страница 1: ...EFN324 User Guide EDA 1200...
Страница 4: ...Error No text of specified style in document Glossary 168 Index 170...
Страница 176: ......