Switching Um

USER MANUAL
FOX61x
Ethernet Switching
FOX61x Switch Function
Ethernet Switching User Manual
Document ID 1KHW028566
Document edition FOX61x System Release: R15B

Revision: A
Date: 2022-01-06
Copyright and confidentiality Copyright in this document vests in Hitachi Energy.

Manuals and software are protected by copyright. All rights reserved. The copying,
reproduction, translation, conversion into any electronic medium or machine
scannable form is not permitted, either in whole or in part. The contents of the
manual may not be disclosed by the recipient to any third party, without the prior
written agreement of Hitachi Energy.
An exception is the preparation of a backup copy of the software for your own use.
For devices with embedded software, the end-user license agreement on the
enclosed CD applies.
This document may not be used for any purposes except those specifically
authorized by contract or otherwise in writing by Hitachi Energy.
Disclaimer ABB is a registered trademark of ABB Asea Brown Boveri Ltd.

Manufactured by/for a Hitachi Energy company.
Hitachi Energy Switzerland Ltd (hereinafter referred to as Hitachi Energy) has taken
reasonable care in compiling this document, however Hitachi Energy accepts no
liability whatsoever for any error or omission in the information contained herein and
gives no other warranty or undertaking as to its accuracy.
Hitachi Energy can accept no responsibility for damages, resulting from the use of
the network components or the associated operating software. In addition, we refer to
the conditions of use specified in the license contract.
Hitachi Energy reserves the right to amend this document at any time without prior
notice.
The product/software/firmware or the resulting overall solution are designed for data
processing and data transmission and may therefore be connected to communication
networks. It is your sole responsibility to provide and continuously ensure a secure
connection between the product/software/firmware or the resulting overall solution
and your network or any other networks (as the case may be). You shall establish
and maintain any appropriate measures (such as but not limited to the installation of
firewalls, application of authentication measures, encryption of data, installation of
anti-virus programs, etc.) to protect the product/software/firmware or the resulting
overall solution, the network, its system and all the interfaces against any kind of
security breaches, unauthorized access, interference, intrusion, leakage and/or theft
of data or information. Hitachi Energy and its affiliates are not liable for damages
and/or losses related to such security breaches, any unauthorized access,
interference, intrusion, leakage and/or theft of data or information.
Although Hitachi Energy provides functionality testing on the products including
related firmware and software that we release, you should institute your own testing
program for any product updates or other major system updates (to include but not
limited to firmware/software changes, configuration file changes, third party software
updates or patches, hardware exchanges, etc.) to ensure that the security measures
that you have implemented have not been compromised and system functionality in
your environment is as expected.
Copyright 2022 Hitachi Energy. All rights reserved. 2

FOX61x | ETHERNET SWITCHING
Contents
1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Precautions and Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Symbols and Notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3 Document History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.4 Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.5 Definition of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 FOX61x packet based core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 FOX61x Switching Core and Service Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3.1 Port Type Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3.2 Ethernet Core and Service Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3.3 Ethernet Stand-Alone Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.3.4 Layer 2 Redundancy Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3 Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1 Feature Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.2 Functions and Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1 Ethernet Switch with VLAN Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1.1 FOX61x Switch Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1.2 VLAN Port Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1.3 General VLAN Port Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1.4 Traffic Quality of Service Features . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.1.5 Storm Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.2 Rapid Spanning Tree Protocol (RSTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.2.1 Transform a Mesh Network to a Tree Network . . . . . . . . . . . . . . . . . . . . . 20
4.2.2 Attach a Customer Network to a Core Network. . . . . . . . . . . . . . . . . . . . . 20
4.3 Equipment Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.3.1 Core Unit EQP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.3.2 Service Unit EQP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1 General Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.2 Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.2.1 Set up Global NE Bridge Port Parameters . . . . . . . . . . . . . . . . . . . . . . . 25
5.2.2 Set up the Network Element QoS Parameters . . . . . . . . . . . . . . . . . . . . . 26
5.2.3 Set up the Port QoS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2.4 Set up global Bridge Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.2.5 Set up Bridge VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.2.6 Set up Bridge Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.2.7 Set up Bridge Ports for Ethernet stand-alone Units. . . . . . . . . . . . . . . . . . . 31
5.3 Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.3.1 Set up a Spanning Tree using RSTP . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.4 Test of Readiness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.4.1 Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.1 Status and Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.1.1 Bridge Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.1.2 Bridge Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.1.3 Spanning Tree Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.1.4 Spanning Tree Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.2 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.3 Possible Faults and related Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.3.1 FOX61x active Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6.3.2 Unit not available (UNAV alarm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

FOX61x | ETHERNET SWITCHING
6.3.3 Port Down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

6.3.4 Switching Services not working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
7 User Interface Reference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
7.1 Managed Object Models (MOM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
7.1.1 MOM for the Port Types and QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
7.1.2 MOM for the Switching Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . 41
7.2 AP: / ne . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.2.1 AP: / ne, Main . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.3 AP: / Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.4 AP: / Switching / Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.4.1 AP: / Switching / Bridges, Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.5 AP: / Switching / Bridges / bridge-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
7.5.1 AP: / Switching / Bridges / bridge-1, Ports . . . . . . . . . . . . . . . . . . . . . . . 44
7.5.2 AP: / Switching / Bridges / bridge-1, VLANs . . . . . . . . . . . . . . . . . . . . . . 52
7.6 AP: / Switching / Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.7 AP: / Switching / Protocols / Spanning Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.7.1 AP: / Switching / Protocols / Spanning Tree, Spanning Trees . . . . . . . . . . . . . 54
7.8 AP: / Switching / Protocols / Spanning Tree / bridge-1 . . . . . . . . . . . . . . . . . . . . . . 56
7.8.1 AP: / Switching / Protocols / Spanning Tree / bridge-1, Ports . . . . . . . . . . . . . 56
8 Annex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
8.1 Associated FOX61x Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

FOX61x | ETHERNET SWITCHING PREFACE
1 Preface
1.1 Precautions and Safety

Before you handle any equipment you must comply with the safety advices.
Adherence to the safety instructions ensures compliance with the safety requirements as
defined in IEC 62368-1 (Safety of audio/video, information and communication technology
equipment).
Please refer to the following document:
[1KHW002497] Operating Instruction “Precautions and safety”.
1.2 Symbols and Notations

This User Manual uses the following symbols:
Risk of operating trouble!

Indicates that an action may lead to operating trouble or loss of data.
→ Possible actions are given.
Please note:
Shows significant information.
→ Possible actions are given.
1.3 Document History

Table 1: Document history
Document ID Rev. Date FOX61x Changes since previous version
release
1KHW028566 A January 2022 R15B Updated for current system release.
1KHW028566 F June 2021 R15A - Support of the WAN port expansion unit EPEX1.
- In the FOXCST the QoS related parameters are
moved to the new “QoS” view.
- Support of CE dual homing uplink tracking.
- Update copyright statement.
1KHW028566 E June 2020 R14A - QoS related items moved to the [1KHW029124] User
Manual “Quality of Service” document.
1KHW028566 D September 2019 R3B - Support of buffer CPS on the Ethernet service units.
1KHW028566 C March 2019 R3A_SP01 - Support of the Ethernet standalone switching unit
ESPO1.
- Support of the Ethernet standalone switching units
ESOP1 and ESOP1-F.
- Port shaping section added, see section 4.1.4 Traffic
Quality of Service Features (on page 19).
1KHW028566 B November 2018 R3A - Support of the CESM3 core unit.
- Support of the DEFM1 and DEFM1-F service unit.
- Minor editorial changes.
- New Hitachi Energy branding.
- Service unit SAMO5, SAMO5-F added.
1KHW028566 1 May 2018 R2D - Dual homing support for MPLS-TP VPLS services.
- Renewal of the QoS features and traffic class man-
agement.
- New routing unit EROP1.

FOX61x | ETHERNET SWITCHING PREFACE
Table 1: Document history (continued)

Document ID Rev. Date FOX61x Changes since previous version
release
1KHW028566 2 December 2016 R2C - RST protocol added.
- R-L2GP protocol added.
- Port QoS parameters moved from the FOXCST
Switching view to the Tree View (Trust L2, Trust L3).
- Default Priority parameter moved from the FOXCST
Switching view to the Tree View.
- No Bridge related alarms available.
1KHW028566 1 December 2015 R2B - Storm control information added.
- QoS reworked.
- Switching protocols removed.
1KHW028566 1 August 2014 R1C First revision for current system release.
1.4 Target Audience

This User Manual is targeted at persons who are entrusted with the provisioning, operation and
administration of the system.
The persons targeted are
• the provisioning personnel, and/or
• the operation and administration personnel
Please note:
Only instructed or skilled persons as per IEC 62368-1 may install and maintain the
system.
1.5 Definition of Terms

Table 2: Specific terms
Term Explanation
CESM1 Designates the core and control unit CESM1 or CESM1-F of FOX61x.
CESM2 Designates the core and control unit CESM2 or CESM2-F of FOX61x.
Core Unit Designates the core and control unit CESM1, CESM1-F, CESM2, CESM2-F or
CESM3 of FOX61x.
Where certain features or characteristics apply to a specific core unit only, the
CESM1, CESM1-F, CESM2, CESM2-F or CESM3 is named explicitly.
ETOP1 Designates the service unit ETOP1 or ETOP1-F of FOX61x.
SAMOx Designates the service unit SAMO5, SAMO5-F, SAMO2, SAMO2-F or SAMO3 of
FOX61x.
SAMO1 is excluded.
ESOP1 Designates the service unit ESOP1 or ESOP1-F of FOX61x.
DEFM1 Designates the service unit DEFM1 or DEFM1-F of FOX61x.
EROP1 Designates the service unit EROP1 or EROP1-F of FOX61x.
WAN port expan- Designates the WAN port expansion unit EPEX1. Up to two EPEX1 units can be
sion unit operated in a FOX615 R2 subrack together with a CESM3 core unit.

FOX61x | ETHERNET SWITCHING INTRODUCTION
2 Introduction
2.1 General
Ethernet based services in the FOX61x are part of the FOX61x multi-service functionality. They
can be implemented in one subrack together with TDM-based services.
The core unit and the service units behave as an integrated bridge called “FOX61x Switch”. The
FOX61x Switch fulfills the following two main functions:
• VLAN Bridging
• MPLS-TP Transport
Whereas the MPLS-TP transport function requires the VLAN bridging function for the manage-
ment channel and the VPLS application, the VLAN bridging function can be used completely
isolated of the MPLS-TP transport function in a subrack.
This document describes VLAN bridging functions of the FOX61x Switch, and the use of the
layer 2 protocols available in the FOX61x.
This User Manual does not cover the MPLS based aspects of services. For details on MPLS
based applications refer to [1KHW028618] User Manual “MPLS-TP Services”.
2.2 FOX61x packet based core

Each Ethernet service unit and the core unit plugged and assigned in the FOX61x subrack con-
tributes its switch ports to the FOX61x Switch, i.e. the FOX61x Switch ports are located on the
core unit and on the service units. From a spanning tree protocol viewpoint, the FOX61x
behaves as one RSTP entity.
But there are also some Ethernet service units operating as a stand alone bridge with its own
RSTP entity. These units access the FOX61x Switch via an Ethernet connection on the FOX61x
backplane. These backplane ports are handled like an external port of the FOX61x Switch.
For an overview of all FOX61x service units please refer to section 2.3 FOX61x Switching Core
and Service Units (on page 8).
The physical interconnection of all switching devices is done with 10 Gbit/s or 1 Gbit/s Ethernet
links from each service unit to the active core unit and to the standby core unit. All 10 Gbit/s or
1 Gbit/s Ethernet links present an Ethernet star.
The physical interconnection of the WAN port expansion unit to the active and standby CESM3
core unit plugged in a FOX615 R2 subrack is done with 40 Gbit/s links. Up to two WAN port
expansion units can be plugged in a FOX615 R2 subrack. The 40 Gbit/s links present a small
Ethernet star.
The active and the standby CESM3 core unit are in addition connected with one 1 Gbit/s and
four 10 Gbit/s Ethernet links.
Please note:
The switch circuit on the redundant CESM3 core unit is not active. It does not par-
ticipate in the FOX61x Switch.
→ The front ports of the standby CESM3 core unit are connected via the back-
plane to the switch circuit of the active CESM3 core unit.
The active and the standby CESM1 or CESM2 core units are in addition connected with two
10 Gbit/s Ethernet links.
Please note:
The switch circuits on both the working and the redundant CESM1 or CESM2 core
units are active and participate in the FOX61x Switch.

Please note:
Because of the FOX61x internal structure the switching and forwarding behavior is
not according to a standard switch in all cases. MAC forwarding databases are
maintained independently on each unit participating in the FOX61x Switch, i.e. the
forwarding databases of the units are not synchronized.
→ Unicast traffic sent from one unit to another unit is flooded to all units participat-
ing in the FOX61x Switch since the destination MAC address is not known on
the ingress unit.
FOX61x
Packet data interfaces
10GbE or 1GbE star

Stand alone bridge
Packet
network
Packet data interfaces Packet transport
FOX61x Switch
Ethernet bridge
Figure 1: FOX61x packet based core with FOX61x Switch and stand alone bridge
2.3 FOX61x Switching Core and Service Units
2.3.1 Port Type Configuration

By default there is no allocation of an Ethernet port to any function. The Ethernet “Port Type”
parameter must be configured before configuring the function.
An Ethernet port that shall participate in the FOX61x Switch must be configured to CVP port
type (Customer VLAN Port). Only if the port type is set to CVP the Ethernet port appears in the
switching configuration where all the switching parameters can be configured.
For more information on the port type please refer to [1KHW002464] User Manual “FOX615
R2/FOX615/FOX612/FOX611”.
2.3.2 Ethernet Core and Service Units

The FOX61x bridging function is supported by the following Ethernet core and service units:
• CESM3
• CESM2
• CESM1
• EPEX1
• ETOP1
• ELET1
• EPOI1
• SAMOx
• DEFM1
The Ethernet (front) ports of these units can be configured as FOX61x Switch ports.

Ethernet
CVP CVP
Service Core Unit
port port Packet
Unit
network
Ethernet star
Ethernet WAN port
CVP CVP
Service expansion
port port
Unit unit
FOX61x Switch
Figure 2: FOX61x Switch with Ethernet service units
2.3.3 Ethernet Stand-Alone Units

Because of their functions and HW design not all service units are fully integrated in the FOX-
61x Switch. Their physical and logical ports are not visible in the switching configuration.
These Ethernet stand-alone units access the FOX61x Switch with the internal port via the GbE
star. Correspondingly the internal Ethernet ports on the CESM1 or CESM2 unit, or on the back-
plane Ethernet ports of the CESM3 unit connecting the Ethernet stand-alone units can be con-
figured as FOX61x Switch ports.
The following units operate as Ethernet stand-alone units:
• EPSI1
• ESOP1
• ESPO1
• EROP1
• SAMO1
• CEPI1
• COSI1
• TEPI2
• OPIC2
• TEGO1
Ethernet
Stand-Alone
Unit CVP Packet
GbE star
port Core CVP network

CVP Unit port
Ethernet port
Stand-Alone
Unit
FOX61x Switch
Figure 3: FOX61x Switch with Ethernet stand-alone units

2.3.4 Layer 2 Redundancy Protocols

Layer 2 redundancy prevents the single point of failure in a network by having one or several
alternative paths. Redundancy can be implemented on any type of networks (linear, ring, mesh)
on any hierarchical layer (access-, distribution-, core layer) of a hierarchical design model.
When multiple paths exist from a source to a destination the protocol has to guarantee that
frames are not looped endlessly in a network. The protocol has to allow that either all paths can
be used (load sharing) or it has to break up the loop in the network.
The FOX61x Switch supports the following layer 2 redundancy protocols:
• RSTP

FOX61x | ETHERNET SWITCHING SPECIFICATION
3 Specification
3.1 Feature Licenses

Part of the FOX61x functionality is subject to feature licenses.
For more information on feature licenses please refer to [1KHW028777] Release Note “FOX61x
System Release R15B” and to [1KHW028776] Product Description “Feature Licenses for FOX-
61x”.
3.2 Functions and Specification

The FOX61x network element provides the functions and conforms to the corresponding stan-
dards and recommendations (conformance to applicable parts of the standards) as stated in
[1KHW002460] System Description “FOX61x R15B”.

FOX61x | ETHERNET SWITCHING FUNCTIONS
4 Functions
4.1 Ethernet Switch with VLAN Support

VLANs extend the traditional layer 3 router-bounded broadcast domain to a layer 2 VLAN-
bounded broadcast domain. Using VLANs allows to segment a network based on functions and
to control a network much better. Vice versa a logically segmented switched network can be
combined again to one entity.
4.1.1 FOX61x Switch Architecture

The main Ethernet traffic function of the FOX61x is the Ethernet switch with VLAN support
(based on IEEE 802.1Q). This function is implemented on the core and on the Ethernet service
units listed in section 2.3 FOX61x Switching Core and Service Units (on page 8). All switch ele-
ments implemented on the core unit and the Ethernet service units are interconnected via the
40 GbE-star (FOX615 R2 subrack with CESM3 core unit only), the 10 GbE-star or the 1 GbE-
star. Together they constitute one bridge instance, called the FOX61x Switch.
The five Ethernet front access ports on each core unit and all Ethernet ports on the Ethernet
service units are connected to the FOX61x Switch. In addition the switch instances of service
units not participating in the FOX61x Switch (e.g. EPSI1, ESOP1, ESPO1, EROP1, SAMO1,
CEPI1, COSI1, TEPI2, OPIC2, TEGO1) are connected to the FOX61x Switch via the serial GbE
links of the backplane 1 GbE star. In this case the ports to the 1 GbE-star link are handled as
external ports of the FOX61x Switch.
This architecture allows the switching of data between any Ethernet port on the core unit and
the Ethernet service units. For management purposes, the FOX61x Switch has a port con-
nected to the processor of the core unit.
Moreover, the switch instance on the redundant CESM1 or CESM2 core unit is also part of the
FOX61x Switch, using the 2 x 10 GbE point-to-point links between the two core unit slots. This
connection is only used with core unit equipment protection.
Please note:
The switch instance on the redundant CESM3 core unit is not part of the FOX61x
Switch.
The LAN segments connected to a port of a VLAN bridge are defined as
• “access links” if they carry untagged or priority tagged frames, or
• “trunk links” if they carry tagged frames (according to IEEE 802.1Q-2003, Annex D).
Every Ethernet front port or backplane port of the FOX61x Switch can be configured to be asso-
ciated with a trunk link. Accordingly, it is expected that all the frames arriving at these ports are
tagged. The VLAN IDs to be accepted by a port must be configured in the bridge instance. Per
default no VLANs are configured, except the default VLAN ID 1.
Alternatively a port can be configured to be associated with an access link. Frames arriving at
subscriber interfaces are normally untagged or priority tagged for most residential customer ser-
vices. The (port) VLAN tag is assigned to the frames in the FOX61x.
Please note:
As an alternative to a high speed Ethernet port on the core unit, a high speed
Ethernet port on a WAN port expansion unit can be used.

ETOP1, ELET1 Core Unit

Port
Port EPOI1
VLAN-ID
Eth port
1 1 Port Port
10GbE VLAN-ID
backplane 10GbE
1 1
Eth port
2 1
FOX61x Switch
Port ETOP1, ELET1

Port EPOI1
VLAN-ID
Eth port
1 1
10GbE
backplane 1GbE
1 5
Eth port
2 1
Figure 4: VLAN bridging with single tagging in FOX61x
When using the EoS service on the SAMO1 unit the backplane ports of the core unit can be
configured to the required port mode. Correspondingly the backplane ports also carry VLAN
tagged traffic or untagged traffic.
SAMO1
EoS Port Core Unit
Port Port GbE VLAN-ID
SDH port backplane Port Port
EoS 1 1
VLAN-ID
10GbE
1 1
SAMOx
EoS Port
Port Port VLAN-ID
SDH port
EoS 1 1 10GbE
backplane
SDH port
EoS 2 1
FOX61x Switch
Port ETOP1, ELET1

Port EPOI1
VLAN-ID
Eth port
1 1
10GbE
backplane 1GbE
1 5
Eth port
2 1
Figure 5: VLAN bridging and EoS with single tagging in FOX61x
In addition to the access port mode and the trunk port mode the FOX61x supports three addi-
tional port modes:
• Trunk with native VLAN
• General

• Q-in-Q
The port mode
• Unswitched
applies only for the SAMOx Ethernet front ports port-5 to port-8 and the corresponding EoS
groups. This port mode bypasses the FOX61x Switch. A SAMOx Ethernet front port and an
EoS group configured to the “unswitched” mode are directly connected with a point-to-point
connection.
The VLAN handling and all port parameters are described in section 4.1.2 VLAN Port Modes
(on page 14).
All switch devices of the FOX61x Switch need to have an updated MAC table in order to per-
form the forwarding of the frames. The FOX61x uses IVL (independent VLAN learning) for the
MAC learning process. This implies that the FOX61x holds independent MAC tables for each
VLAN. The FOX61x can hold a total of 64’000 MAC addresses.
The FOX61x Ethernet switch will support the Provider Bridge features according to IEEE
802.1Q in a future release.
4.1.2 VLAN Port Modes

The FOX61x Switch is a VLAN aware switch, i.e. inside the bridge only VLAN tagged frames
are forwarded. VLAN tagged frames can enter the FOX61x Switch by e.g. a trunk port or get
their VLAN tag assigned at the ingress of an access port.
The FOX61x Switch accepts only Ethernet frames with VLAN-IDs which are created in the
bridge configuration. VLAN tagged frames with other VLAN-IDs, i.e. which are not configured for
the bridge, are dropped.
Please note:
The VLAN-ID 1 is the default VLAN-ID and is available per default.
→ All other VLAN-IDs which shall be forwarded in the bridge must be created.
The FOX61x supports the following bridge port modes on the FOX61x Switch:
• Access port mode
An access port forwards untagged or priority tagged frames only.
The ingress direction accepts only untagged or priority tagged frames which become tagged
with the port VLAN-ID. The port VLAN-ID must be member of the bridge VLANs. VLAN
tagged frames are dropped.
The egress direction forwards only frames with the port VLAN-ID as untagged frames, i.e.
the VLAN-ID is removed. All other frames are dropped.
• Trunk port mode
A trunk port forwards VLAN tagged frames only.
The ingress direction accepts all VLAN tagged frames whose VLAN-ID is member of the
bridge VLANs. Untagged or priority tagged frames are dropped. Inside the FOX61x Switch
the frames keep their VLAN-ID.
The egress direction forwards all frames with their VLAN-ID.
Note that a trunk port has no port VLAN-ID.
• Trunk with native VLAN port mode
A trunk with native VLAN port forwards all frames.
bridge VLANs. Untagged or priority tagged frames become tagged with the port VLAN-ID.
The port VLAN-ID must also be member of the bridge VLANs.
The egress direction forwards frames with the port VLAN-ID as untagged frames, i.e. the
VLAN-ID is removed. All other frames are forwarded with their VLAN-ID.

• General port mode

A general port is fully configurable and provides full flexibility in the Ethernet frame handling.
Please refer to section 4.1.3 General VLAN Port Mode (on page 16).
• Q-in-Q port mode
A Q-in-Q port forwards all frames.
The ingress direction accepts all frames, be they VLAN tagged or untagged. The frames
become tagged with the port VLAN-ID, e.g. untagged ingress frames become single tagged,
single tagged ingress frames become double tagged. The port VLAN-ID must also be mem-
ber of the bridge VLANs.
The egress direction forwards only frames where the single or outer tag is the port VLAN-ID
and removes this VLAN-ID, e.g. single tagged frames become untagged, double tagged
frames become single tagged. Frames with another VLAN-ID are dropped.
• Unswitched port mode
An “unswitched” port can only be operated on a SAMOx unit. This setting configures the port
to be unswitched, i.e. excluded from the FOX61x Switch. For more information on this mode
refer to [1KHW028668] User Manual “SAMO2, SAMO2-F, SAMO3, SAMO5, SAMO5-F”.
The following parameters allow the detailed configuration of the required port behavior:
• Port mode
− Access
− Trunk
− Trunk with native VLAN
− General
− Q-in-Q
• Port VLAN ID (PVID)
− 1 to 4089
• Acceptable frame types (fixed according to the port mode configuration)
− Untagged and priority tagged (Access port mode)
− Tagged (Trunk port mode)
− All (Trunk with native VLAN and Q-in-Q port modes)
• Ingress filtering (only relevant for the general port mode)
− on
− off
An example of forwarding and dropping of Ethernet frames in ingress and egress direction for
the “Access”, “Trunk”, “Trunk with native VLAN” and “Q-in-Q” port modes is shown in the Figure
6.

Ingress port Egress port

Access Access
Untagged VLAN-ID 1 VLAN-ID 1 Port VLAN-ID: Untagged

Port VLAN-ID: -1
VLAN-ID 20 -1 dropped VLAN-ID 20 dropped
Bridge VLANs:
VLAN-ID 30 Bridge VLANs: dropped VLAN-ID 30 - 1, 20, 30 dropped
- 1, 20, 30
VLAN-ID 40 dropped
Trunk Trunk
Untagged dropped VLAN-ID 1 VLAN-ID 1

VLAN-ID 1 VLAN-ID 1
VLAN-ID 20 VLAN-ID 20 inner VLAN-ID 20 inner VLAN-ID 20
Bridge VLANs: Bridge VLANs:
- 1, 20, 30 - 1, 20, 30
VLAN-ID 30 VLAN-ID 30 VLAN-ID 20 VLAN-ID 20
VLAN-ID 40 dropped VLAN-ID 30 VLAN-ID 30
Trunk with native VLAN Trunk with native VLAN
Untagged VLAN-ID 1 VLAN-ID 1 Untagged

Port VLAN-ID: VLAN-ID 1 Port VLAN-ID:
VLAN-ID 20 -1 VLAN-ID 20 inner VLAN-ID 20 -1 VLAN-ID 20
VLAN-ID 30 Bridge VLANs: VLAN-ID 30 VLAN-ID 20 Bridge VLANs: VLAN-ID 20

- 1, 20, 30 - 1, 20, 30
VLAN-ID 40 dropped VLAN-ID 30 VLAN-ID 30
Q-in-Q Q-in-Q
Untagged VLAN-ID 1 VLAN-ID 1 Untagged

Port VLAN-ID: VLAN-ID 1 VLAN-ID 1 Port VLAN-ID:
VLAN-ID 20 -1 inner VLAN-ID 20 inner VLAN-ID 20 -1 VLAN-ID 20
VLAN-ID 1
VLAN-ID 30 Bridge VLANs: inner VLAN-ID 30 VLAN-ID 20 Bridge VLANs: dropped
- 1, 20, 30 - 1, 20, 30
VLAN-ID 1
VLAN-ID 40 inner VLAN-ID 40 VLAN-ID 30 dropped
Figure 6: VLAN port modes and frame handling example
4.1.3 General VLAN Port Mode

The “General” port mode gives full flexibility in configuring a bridge port. Particularly when using
the ingress filtering feature, the VLAN membership of a bridge port can be defined by the ports
VLAN membership table.
The ingress frame handling of a general port is defined by the “acceptable frame types” and the
“ingress filtering” parameters:
When ingress filtering is disabled the general ingress port forwards or drops Ethernet frames
as follows:
• Acceptable frame types = Untagged and priority tagged
The port acts like an “access” port, i.e. forwards untagged or priority tagged frames only.
The ingress direction accepts only untagged or priority tagged frames which become tagged
with the port VLAN-ID. The port VLAN-ID must be member of the bridge VLANs. VLAN
tagged frames are dropped.

• Acceptable frame types = Tagged

The port acts like a “trunk” port, i.e. forwards VLAN tagged frames only.
bridge VLANs. Untagged or priority tagged frames are dropped. Inside the FOX61x Switch
the frames keep their VLAN-ID.
Note that a general port with “Acceptable frame types = Tagged” has no port VLAN-ID.
• Acceptable frame types = All
The port acts like a “trunk with native VLAN” port, i.e. forwards all frames.
bridge VLANs. Untagged or priority tagged frames become tagged with the port VLAN-ID.
The port VLAN-ID must also be member of the bridge VLANs.
An example of forwarding and dropping of Ethernet frames in ingress direction with disabled
ingress filtering is shown in the Figure 7.
Ingress port
General/Untagged and
Priority tagged Frames
Untagged VLAN-ID 1
Port VLAN-ID:
VLAN-ID 20 -1 dropped
VLAN-ID 30 Bridge VLANs: dropped

- 1, 20, 30
VLAN-ID 40 dropped
General/Tagged Frames
Untagged dropped
VLAN-ID 20 VLAN-ID 20
Bridge VLANs:
- 1, 20, 30
VLAN-ID 40 dropped
General/All Frames
Untagged VLAN-ID 1
Port VLAN-ID:
VLAN-ID 20 -1 VLAN-ID 20
VLAN-ID 30 Bridge VLANs: VLAN-ID 30

- 1, 20, 30
VLAN-ID 40 dropped
Figure 7: General port mode, ingress frame handling example, no ingress filtering
A bridge port configured to the general port mode provides a VLAN membership table. When
ingress filtering is enabled the general ingress port drops all Ethernet frames whose VLAN-ID
is not listed in the VLAN membership table. This results in the following behavior:
• Acceptable frame types = Untagged and priority tagged
The port forwards untagged or priority tagged frames only. The port VLAN-ID must be a
member of the bridge VLANs and also listed in the VLAN membership table.
• Acceptable frame types = Tagged
The port forwards VLAN tagged frames only whose VLAN-ID is member of the bridge VLANs
and also listed in the VLAN membership table.

• Acceptable frame types = All

The port forwards all frames whose VLAN-ID is member of the bridge VLANs and also listed
in the VLAN membership table. Note that untagged or priority tagged frames become tagged
with the port VLAN-ID. The port VLAN-ID must also be listed in the VLAN membership table.
An example of forwarding and dropping of Ethernet frames in ingress direction with enabled
ingress filtering is shown in the Figure 8.
Ingress port
General/Untagged and
Priority tagged Frames
Untagged Port VLAN-ID: VLAN-ID 1

-1
VLAN-ID 20 dropped
Bridge VLANs:
- 1, 20, 30
VLAN-ID 30 dropped
VLAN-ID 40 VLAN Membership, dropped

tagged or untagged:
VLAN-ID 50 - 1, 20, 40 dropped
General/Tagged Frames
Untagged dropped

- 1, 20, 30
VLAN-ID 30 dropped
VLAN Membership,
tagged or untagged:
VLAN-ID 50 dropped
General/All Frames
Untagged VLAN-ID 1
Port VLAN-ID:
-1
Bridge VLANs:
VLAN-ID 40 VLAN Membership, dropped

tagged or untagged:
- 1, 20, 40
VLAN-ID 50 dropped
Figure 8: General port mode, ingress frame handling example, with ingress filtering
The VLAN membership table controls also the Ethernet frame handling of a general port in
egress direction. The egress port drops all Ethernet frames whose VLAN-ID is not listed in the
VLAN membership table.
VLANs in the VLAN membership table can be marked as tagged or untagged:
• Tagged
VLANs are forwarded with their VLAN-ID.
• Untagged
VLANs are forwarded as untagged frames, i.e. the VLAN-ID is removed.
An example of forwarding and dropping of Ethernet frames in egress direction is shown in the
Figure 9.

Egress port
General

- 1, 20, 30, 40, 50
VLAN Membership,
tagged:
VLAN-ID 30 dropped
- 1, 20
VLAN-ID 40 VLAN membership, Untagged

untagged:
VLAN-ID 50 - 40 dropped
Figure 9: General port mode, egress frame handling example
4.1.4 Traffic Quality of Service Features

For a description of the
• traffic classification,
• traffic rate limiting,
• drop precedence handling,
• traffic scheduling, and
• traffic shaping
please refer to [1KHW029124] User Manual “Quality of Service”.
4.1.5 Storm Control

The storm control feature limits the rate of
• broadcast traffic,
• multicast traffic,
• unknown unicast traffic, and
• known unicast traffic
to a configurable threshold. The traffic threshold is in the range of 0 to 100% of the port speed.
Storm control can be enabled on any external or internal Ethernet port.
Please refer to section 7.5.1.4 AP: / Switching / Bridges / bridge-1, Ports - Storm Control (on
page 51).
Please note:
The storm control feature does not block the traffic completely by setting the traffic
threshold to 0%.
→ A traffic rate of 0.5 Mbit/s is still possible.
Please note:
The storm control feature is not supported on bridge ports (CVP) that are part of a
VPLS.

4.2 Rapid Spanning Tree Protocol (RSTP)
4.2.1 Transform a Mesh Network to a Tree Network

STP is the well-known and preferred protocol allowing to have redundant paths on a hierarchical
network design. The protocol discovers the network so it can be used in any network topology
(link, ring, meshed). STP reduces the physical topology by blocking ports to an active tree topol-
ogy that reaches all segments of the network.
RSTP, the successor of STP provides faster convergence after a topology change by reducing
the number of switch port states. Both protocols ensure that only one logical path exists
between all destinations on a network.
Root
Designated Designated
Port Designated Port
Port
Root Port Root Port
Root Port Root Port
Non designated Port
Figure 10: Building an RSTP tree
For more details please refer to [1KHW002460] System Description “FOX61x R15B”.
Please note:
On FOX61x Switch ports RSTP is disabled by default. A maximum of 64 ports can
have RSTP enabled on the FOX61x Switch.

In order to avoid a loop enable RSTP before connecting the cables or before
changing the “Admin State” from “Down” to “Up”.
4.2.2 Attach a Customer Network to a Core Network

The attachment of a customer network (LAN) to a core network can be controlled with the fol-
lowing bridge port configuration parameters in the provider edge (PE):
• R-L2GP (Reverse L2 Gateway Protocol, only available if xSTP is enabled):
R-L2GP is a lightweight spanning tree implementation not keeping any STP state machine.
R-L2GP ports are always designated ports and in forwarding state. R-L2GP ports generate
manually configured pseudo root bridge BPDUs and detect topology change notifications
(TCN).


The R-L2GP ports of a FOX61x network element are not inter-operable with STP
enabled ports in the access network.
→ Make sure that RSTP (or MSTP) is active in the access network.
• Restricted TCN:
Prevents the propagation of a received TCN flag to other ports. Attached LANs will not flush
the Filtering Data Base (FDB).
• Restricted Role (only available if R-L2GP is disabled):
Prevents a bridge port taking over the root port role, so the port is always designated.
The following bridge parameters control the Dual Homing setup in the provider edge:
• TC Propagation to/from VPLS:
A TC detected at an R-L2GP enabled bridge port will activate the pseudo wire OAM “MAC
withdraw” message on the VPLS pseudo wires which have attachment circuits hosted by the
R-L2GP port.
A pseudo wire OAM “MAC withdraw” message detected at a VPLS pseudo wire will activate
a TC notification on the attached RSTP enabled bridge ports.
• TC Persistency Time:
Defines the time to apply the TC notification towards the RSTP enabled bridge ports.
It also defines the RSTP TC filtering time, i.e. within this time no additional pseudo wire OAM
“MAC withdraw” message can be initiated if the TC Persistency Time is not expired.
4.2.2.1 Single Link Connection

In the example in Figure 11 the customer network is connected via a single customer edge (CE)
to the provider edge (PE) of the MPLS core network.
R-L2GP = false
CPE Restricted Role = true PE 2 CE
Restricted TCN = true
CPE Core
CE 1 PE 1
Network
Customer
Network
(LAN) PE 3 CE
CPE
CPE
CPE designated port

RSTP isolated root port
blocked port
Figure 11: Customer network connected with one CE to the PE
In order to protect the core network from any topology changes in the customers network and
especially avoiding that the root bridge will be located in the customers network the port on PE 1
connecting the customers network should be configured with Restricted Role parameter set to
true. This port will never become a root port and the root bridge stays in the core network.
The Restricted TCN parameter can also be set to true. Any topology change notification (TCN)
coming from the customers network is not relevant for the core network and has not to be for-
warded.

4.2.2.2 Dual Link Connection

In case the customer network is connected via two CE devices to a PE there is a risk of a MAC
address black hole issue when using RSTP on the CE facing ports. In this case the CE facing
ports on the PE must be configured to the R-L2GP mode.
CPE R-L2GP = true PE 2 CE

Restricted TCN = false
CPE Core
CE 1 PE 1
Network
Customer
Network
(LAN)
R-L2GP = true PE 3 CE
Restricted TCN = false
CE 2
CPE
CPE designated port

RSTP isolated root port
blocked port
Figure 12: Customer network connected with two CE to the PE
The PE sends BPDUs to the CE 1 and CE2 presenting itself as a root bridge. In symmetric LAN
ring topologies the blocked port is on the opposite side of the root bridge. By configuring the R-
L2GP ports connected to CE 1 and CE 2 as the best root bridge (e.g. pseudo root bridge priority
= 0 and MAC address = 00:00:00:00:00:0A) the xSTP blocked port is enforced to be inside the
customer network.

All R-L2GP ports connected to the same customer network must use the same
pseudo root bridge priority and the same root bridge MAC address.
→ To control the blocked port location use a high xSTP path cost on a customer
network bridge port.

Do not allow an STP bridge in the customer network to win the root bridge election
over an R-L2GP port.
→ Two root bridges fighting to control the network most likely ends in a loop.
→ Configure a pseudo root identifier with a priority value 0 and 00:00:00 in the first
3 octets of the MAC address. (The pseudo root identifier is the concatenation of
priority and MAC address).
To be able to forward topology changes from CE 1 to CE 2 and vice versa, the Restricted TCN
parameter must be set to false. The PE monitors the TC bit in the received BPDUs. The PE
flushes the MAC addresses when receiving TC notifications:
• flush port to CE 2 when receiving TC from CE 1,
• flush port to CE 1 when receiving TC from CE 2.
4.2.2.3 Dual Homing Connection

In case the customer network is connected via two CE devices to two PEs (dual homing) the CE
facing ports on the PEs must be configured to the R-L2GP mode.


All R-L2GP ports connected to the same customer network must use the same
pseudo root bridge priority and the same root bridge MAC address.
→ To control the blocked port location use a high xSTP path cost on a customer
network bridge port.
Please note:
The Figure 13 only shows the “Switching” related configuration parameters.
→ The “MPLS-TP” related configuration parameters are not shown.
TC Propagation to/from VPLS = true
TC Persistency Time = 10 s
R-L2GP Enabled = true MPLS-TP

CPE Restricted TCN = false
Core PE 3 CE
Network
CPE CE 1 PE 1
Customer
Network VPLS
(LAN) full mesh
CE 2 PE 2
CPE
PE 4 CE
R-L2GP Enabled = true
CPE Restricted TCN = false
TC Propagation to/from VPLS = true

TC Persistency Time = 10 s
designated port
root port
blocked port
Figure 13: Customer network connected with two CE to two PE
Any topology change (TC) notification received by PE1 or PE2 from the customer network must
be forwarded to all PEs being part of the affected VPLS: The PE3 and PE4 must be aware
which PE, PE1 or PE2, must be addressed to access the CPEs in the customers network. The
dual homing setup is restricted to the MPLS-TP VPLS service type.
The forwarding of TC notifications and the flushing of affected MAC address tables inside the
VPLS is controlled by several configuration parameters.
In case the MPLS uplink connectivity of a PE is completely broken, the PE decouples itself from
the customer network by disabling its R-L2GP port(s). This feature is called “uplink tracking” for
customer edge dual homing. This feature helps the customer network members ignore the PE
network element and choose another MPLS-TP PE network elements R-L2GP port as their pre-
ferred root port to reach the MPLS network.
Please note:
Please refer to [1KHW028618] User Manual “MPLS-TP Services” for a detailed
description of the Dual Homing feature, the setting of the related configuration
parameters and of the CE dual homing uplink tracking feature.

4.3 Equipment Protection
4.3.1 Core Unit EQP

The FOX61x Switch function can be protected by implementing the 1:1 equipment protection for
the core unit.
The Ethernet front ports on the redundant core unit are active. The Ethernet internal ports on
the redundant core unit to the service units are not active. Nevertheless the internal ports must
be configured with the same parameter values as the corresponding ports on the active core
unit.
The FOXCST provides a configuration alignment support for the internal ports of the CESM1
and CESM2 core units connected to Ethernet stand-alone service units. For a description of this
feature refer to [1KHW002469] User Manual “CESM1, CESM1-F” or refer to [1KHW028642]
User Manual “CESM2, CESM2-F”.
The switch over time from the active to the standby unit depends on the layer 2 protocols used
and the network element role.
Please note:
All the switching protocols protect the user traffic against link failures but not equip-
ment failures. The Ethernet traffic interruption time when switching from the active
to the standby core unit depends strongly on the switch-over event, configuration
and the protocol.
Please note:
The switching protocols use dedicated network elements, either specified by con-
figuration or by the protocol itself, to build the tree (root bridge) and block the ports.
→ For this reason the time to converge the network will be longer if one of these
dedicated network elements is affected.
For more information regarding core unit equipment protection please refer to [1KHW002464]
User Manual “FOX615 R2/FOX615/FOX612/FOX611”, [1KHW028774] User Manual “CESM3”,
[1KHW028642] User Manual “CESM2, CESM2-F” and [1KHW002469] User Manual “CESM1,
CESM1-F”.
4.3.2 Service Unit EQP

The FOX61x supports 1:1 equipment protection for the service units SAMOx and for the Ether-
net stand-alone units COSI1, SAMO1, EPSI1 and EROP1 1.
Please note:
Ethernet stand-alone units are connected to the FOX61x Switch via the internal
backplane ports of the core unit. The layer 2 configuration must be done for all
internal ports, independent if the Ethernet stand-alone unit is protected or not.
Please note:
The internal port configuration on the core and the service units have to match for
correct operation.
1. Equipment protection with the EROP1 unit is only supported up to the ESW release r2.

FOX61x | ETHERNET SWITCHING COMMISSIONING
5 Commissioning
5.1 General Prerequisites

In order to commission Ethernet services on the FOX61x, you will need to fulfill the following
prerequisites:
• you need a network planning with regard to Ethernet connections in the FOX61x network
element and Ethernet transport in the network, i.e. you need to have a plan about how you
want to use Ethernet signals in both your access network and the regional Ethernet network;
• you need an Ethernet network with equipment that supports Ethernet signals;
• you need a FOX61x that is physically built into your access network. For installation of the
FOX61x
− refer to [1KHW002461] Installation Instruction “FOX615 R2 and FOX615 Installation”, or
− refer to [1KHW002462] Installation Instruction “FOX612 Installation”, or
− refer to [1KHW029142] Installation Instruction “FOX611 Installation”;
• you need released ESW installed on all of your FOX61x units supporting the functionality of
the current system release; for details about released ESW, refer to [1KHW028777] Release
Note “FOX61x System Release R15B”;
• you need a management connection to your FOX61x; for details about connecting to your
FOX61x, refer to [1KHW028522] User Manual “Management Communication”;
• you need the network element manager FOXCST that is connected to your FOX61x; for the
installation and operation of the FOXCST refer to [1KHW002466] User Manual “FOXCST”.
• you need the knowledge about the Ethernet signal properties connected to the FOX61x
ports. For details about Ethernet service relevant ports and properties refer to the section
4.1.2 VLAN Port Modes (on page 14) and refer to [1KHW029124] User Manual “Quality of
Service”.
5.2 Bridges
5.2.1 Set up Global NE Bridge Port Parameters

By default all the Ethernet ports of the FOX61x Switch are not configured. The Port Type Usage
is set to “None” and thus not available in the AP: /Switching/Bridges/bridge-1/Ports configura-
tion.
→ Port Type configuration. Proceed as follows:

1. In the FOXCST “Tree View”
- select the AP: /ne, Main - Port Type to see all the Ethernet ports of the FOX61x Switch
- or select the appropriate unit AP: /ne/unit-x, Main - Port Type to see only the Ethernet
ports of the selected unit.
- or select the appropriate port AP: /ne/unit-x/port-y, Main - Port Type to see only the
selected Ethernet port.

2. Select every Ethernet port used in the FOX61x Switch that needs to be configured later on in
the FOX61x Switching view and set the Port Type Usage to CVP (Customer VLAN Port).
Result: The global bridge port parameters are fully configured.

End of instruction.
5.2.2 Set up the Network Element QoS Parameters

The QoS configuration parameters of the FOX61x can be found in the “QoS” view of the
FOXCST at the AP: /QoS. These QoS parameters are applicable for all packet transport related
functions (e.g. VLAN bridging and MPLS-TP transport).
Please refer to [1KHW029124] User Manual “Quality of Service”.
5.2.3 Set up the Port QoS Parameters

The QoS configuration parameters of the FOX61x ports can be found in the “QoS” view of the
FOXCST at the
• AP: /QoS/Rate Limiting,
• AP: /QoS/Traffic Classification,
• AP: /QoS/Shaping, and
• AP: /QoS/Scheduling.
Please refer to [1KHW029124] User Manual “Quality of Service”.
5.2.4 Set up global Bridge Parameters

The configuration of the global bridge parameters includes:
• the MAC learning aging time
For a detailed description refer to section 7.4.1 AP: / Switching / Bridges, Bridges (on page 43).
→ Global bridge parameter configuration. Proceed as follows:

1. Select the “Switching” tab in the FOXCST.
2. Select “Bridges” in the tree view on the left hand side of the FOXCST:
3. Select the “bridge-1 Customer Bridge” in the Bridges table. This opens a further tab on the
right hand side of the FOXCST.
4. In the “General” tab set the MAC learning aging time or keep the default value of 300 s. For
details refer to section 7.4.1.1 AP: / Switching / Bridges, Bridges - General (on page 44).

Result: The global bridge parameters are fully configured.

End of instruction
5.2.5 Set up Bridge VLANs
Please note:
Hitachi Energy recommends to configure the required VLANs as early as possible.
Ports can be added easier to configured VLANs as it is shown further below. For
this reason the VLAN setup is described before the port configuration in this User
Manual. You can however add VLANs at any time if required.

Do not use VLANs 4059 to 4062 as bridge VLANs if you operate SAMOx units in
the FOX61x Switch.
→ The VLAN IDs 4059 to 4062 are used for internal purposes in the SAMOx units.
→ Bridge VLAN configuration. Proceed as follows:

2. Select “Switching / Bridges / bridge-1” in the tree view on the left hand side of the FOXCST:
3. Select the “VLANs” tab. This will display all existing VLANs. By default only the VLAN 1 is
defined.

4. Click on the button of the VLANs tab to create a new VLAN:
5. Enter a VLAN ID in the range 2 … 4089 (excluding 4059 … 4062 when using SAMOx) and a
name. Click OK to apply. The VLAN is added to the list of VLANs.
6. Alternatively click on the button to create a range of new VLANs:
7. Enter a VLAN ID range, e.g. “100-110”. Click OK to apply. The VLANs are added to the list
of VLANs.
8. For VLANs created as bulk the VLAN names can be added after creating the VLANs. Edit
each VLANs name in the VLAN list.
9. Repeat the steps 4 to 8 for further VLANs to be created.
10.To display information for a specific VLAN, select the VLAN in the VLANs table. This opens
further tabs on the right hand side of the FOXCST.
11.The “Ports” tab displays all FOX61x Switch ports which are member of the selected VLAN:
12.The “MAC Filtering” tab displays all learned MAC addresses for the selected VLAN. Click on
the refresh button to update the display.
13.To delete a VLAN or several VLANs select the VLAN(s) in the VLANs table and click on the
button.
Please note:
The default VLAN 1 cannot be deleted.
Result: VLANs are fully configured and can be used for the further bridge configuration.
End of instruction

Please note:
You can create a VLAN also by applying a port VLAN ID (PVID) to a FOX61x
Switch port as shown in section 5.2.6 Set up Bridge Ports (on page 29), step 7.
5.2.6 Set up Bridge Ports

Set up the ports of the FOX61x Switch once the Port Type and the VLANs are defined.
The procedures below apply to Ethernet service units as listed in section 2.3.2 Ethernet Core
and Service Units (on page 8). Special settings are required for Ethernet stand-alone units. The
related procedures are described in section 5.2.7 Set up Bridge Ports for Ethernet stand-alone
Units (on page 31).
→ Bridge port configuration. Proceed as follows:

2. Select “Switching / Bridges / bridge-1” in the tree view on the left hand side of the FOXCST:
3. Select the “Ports” tab. This will display all FOX61x Switch ports configured to the port mode
CVP.
4. If required filter the ports table content for a specific unit, for a specific port mode and/or for a
specific PVID.
5. Select a port in the ports table to configure the main port parameters.
Please note:
You can select several ports using the mouse in combination with the “Ctrl” or the
“Shift” key of the keyboard, and configure the main port parameters for these
selected ports via the context menu.
6. Modify the port mode as required. For a detailed description on port modes see section 4.1.2
VLAN Port Modes (on page 14):

Applying the port mode “Unswitched” to a port of a unit other than SAMOx leads to
blocked traffic on that port.
→ The port mode “Unswitched” is only supported by the SAMOx unit.

7. Modify the port VLAN ID (PVID) in the range 1 … 4089. This option is available for ports in
the following modes:
- Access,
- Trunk with Native VLAN,
- General (except when “Acceptable Frametypes” is set to “Tagged”),
- Q-in-Q.
In case the port VLAN ID (PVID) is not yet created a window pops up to create the VLAN
automatically.
8. Set the acceptable frame types. All ingress frames that do not match this setting are dis-
carded. This parameter can only be modified for ports in the General mode.
9. Activate the “Ingress Filtering” if required. This option is only available for ports in the Gen-
eral mode. When activated, any ingress frame is discarded that does not match any of the
VLANs configured in “VLAN Configuration” for that port. See section 4.1.3 General VLAN
Port Mode (on page 16).
Please note:
The “Storm Control” check box is activated if in the tab “Storm Control” one of the
traffic types is enabled.
→ See step 13 below.
10.Selecting a port in the ports table opens further tabs on the right hand side of the FOXCST.
11.The “VLANs” tab displays all VLANs the port is a member of. VLANs are shown with the
VLAN ID, the configured name, and the egress frame type:
12.The “VLAN Configuration” tab allows you to configure the VLAN membership for a General
port. You can configure (add or remove) VLANs for that port.

If a VLAN is added that currently does not exist as bridge VLAN, the VLAN is not
automatically created, and no warning is issued.
→ Traffic will not be forwarded in that VLAN unless you create the VLAN.
13.In the tab “Storm Control” you can activate the Storm Control feature. This activates ingress
rate limiters for broadcast, multicast, unknown unicast and/or known unicast packets. The
total threshold for all selected types of packets is set with “Traffic Threshold” in the range
0 … 100% (of the port speed).

Please note:
When the threshold is set to “0%”, about one packet per second is still admitted,
i.e. traffic of the specified types is not fully blocked.
Please note:
The rate limiter does not provide a steady rate at the configured threshold, but a
bursty behavior with the average at the configured threshold.
Please note:
The storm control feature is not supported on bridge ports (CVP) that are part of a
VPLS. Bridge ports that are part of a VPLS bypass the switch which would support
storm control at the ingress ports.
14.In order to allow frames to pass through the FOX61x Switch you need to set the admin state
of all required ports to “up”. Follow one of the procedures below:
− Select the required port(s) in the ports table of the “Switching” view, right-click the mouse
to open the context menu, and select “AdminState > Up”.
− Change to the “Commissioning” view of the FOXCST and select the appropriate unit in
the MO tree. Set the administrative state of the required port(s) in the “Main, Administra-
tive Status, State” column of the “Port (Ethernet)” tab to “Up”.
− Change to the “Tree View” of the FOXCST and select the appropriate port in the MO tree.
Set the “Admin Status” in “Main - General” to “Up”.
15.Apply the configuration changes.
16.If required save the configuration persistently to the NE database with “Save to NE”.
Result: You have successfully set up a bridge configuration for the Ethernet Switching
application.
End of instruction
5.2.7 Set up Bridge Ports for Ethernet stand-alone Units

When using one of the Ethernet stand-alone units as listed in section 2.3.3 Ethernet Stand-
Alone Units (on page 9), these units appear as FOX61x Switch ports using the internal Ethernet
ports of the CESM1 and CESM2 core unit or the backplane port of the CESM3 core unit. The
internal or backplane port number matches the slot number the Ethernet stand-alone unit is
plugged in. For example an EPSI1 unit plugged in slot-8 is connected to the FOX61x Switch
port
• /backplane/port-8 (for CESM3),
• /unit-11/iports/iport-8 (for CESM1 and CESM2),
• /unit-13/iports/iport-8 (for CESM1 and CESM2).

Please note:
The initial settings for the two ends of the internal connection between the FOX61x
Switch port and the Ethernet stand-alone unit port may differ.
→ Make sure that the configurations on these two ports are matching.
→ Example for an EPSI1 unit operated in slot 8. Proceed as follows:

1. Plug the EPSI1 unit into slot-8 of the FOX61x subrack and assign the unit.
2. In the “Tree View” of the FOXCST select the AP: /unit-8: EPSI1.
- Expand the sub-tree.
- Select the item “/internalPorts/port-1: 1 Gbit/s Ethernet”.
3. Go to the management function Configuration - Bridge.
- Set the VLAN mode to “Access”, “Trunk”, or “Trunk (Native VLAN)”, according to your
requirements.
4. Go to the management function Main - Admin And Oper Status.
- Make sure the administrative status is set to “Up”.
- For more settings refer to [1KHW002475] User Manual “EPSI1”.
CESM3 CESM1 and CESM2

5. In the “Tree View” of the FOXCST select the In the “Tree View” of the FOXCST select the
AP: /backplane/port-8. AP: /unit-11: CESM1 or CESM2.
6. Go to the management function Go to the management function
AP: /backplane/port-8, Main - Port Type. AP: /unit-11/iports/iport-8, Main - Port Type.
Set the Usage of the backplane port to CVP. Set the Usage of the internal port to CVP.
7. In the “Switching” view of the FOXCST select the In the “Switching” view of the FOXCST select the
AP: /Switching/Bridges/bridge-1. AP: /Switching/Bridges/bridge-1.
In the Ports tab select the item In the Ports tab select the item
“/backplane/port-8”. “/unit-11/iports/iport-8”.
8. Set the port mode to “Trunk”, “Access”, or “Trunk with Native VLAN”, in accordance with the
settings on the EPSI1 unit’s internal port as described above.
9. Make sure the PVID and the STP properties match between the EPSI1 bridge settings and the
FOX61x Switch STP settings
10. If using core unit redundancy make sure to
apply the identical settings for
“/unit-13/iports/iport-8: Ethernet”.
Use the alignment support feature at the AP:
/unit-11/Overview - Redundancy Support.
Result: You have successfully configured the basic settings for the internal connection of
an EPSI1 unit to the FOX61x Switch.
End of instruction
→ Example for a SAMO1 unit operated in slot 9. Proceed as follows:

1. Plug the SAMO1 unit into slot-9 of the FOX61x subrack and assign the unit.
2. In the “Tree View” of the FOXCST select the AP: /unit-9: SAMO1.
3. Go to the management function Configuration - General - EoS Resource Usage.
- Configure the Internal Port Usage parameter as described in [1KHW002476] User Man-
ual “SAMO1”, section “Ethernet internal interfaces”.
4. Make sure the administrative state of the internal port(s) is set to “Up”.

5. In the “Tree View” of the FOXCST select the In the “Tree View” of the FOXCST select the
AP: /backplane/port-9. AP: /unit-11: CESM1 or CESM2.


6. Go to the management function Go to the management function
AP: /backplane/port-9, Main - Port Type. AP: /unit-11/iports/iport-9, Main - Port Type.
Set the Usage of the backplane port to CVP. Set the Usage of the internal port to CVP.
7. In the “Switching” view of the FOXCST select the In the “Switching” view of the FOXCST select the
AP: /Switching/Bridges/bridge-1. AP: /Switching/Bridges/bridge-1.
In the Ports tab select the item In the Ports tab select the item
“/backplane/port-9”. “/unit-11/iports/iport-9”.
8. Set the port mode to “Trunk”, “Access”, “Trunk with Native VLAN”, “General” or “Q-in-Q” in
accordance with your requirements.
Please note:
The internal ports of the SAMO1 unit are VLAN unaware ports, and therefore any
packet from the FOX61x Switch is accepted and forwarded. However the settings
at ingress to the FOX61x Switch, e.g. the port mode, need special attention when
VLAN tagged traffic is used.
In this example this applies to the port mode and VLAN membership of the FOX-
61x Switch ports
• “/backplane/port-9” (for CESM3),
• “/unit-11/iports/iport-9” (for CESM1 or CESM2), and
• “/unit-13/iports/iport-9” (for CESM1 or CESM2).
9. Make sure that the switch at the remote end of the SAMO1 EoS connection is configured to
match the settings in the FOX61x Switch ports.
Result: You have successfully configured the basic settings for the internal connection of
an SAMO1 unit to the FOX61x Switch.
End of instruction
Please note:
The COSI1 unit does not show its internal ports on the unit.
→ The corresponding backplane port (when using CESM3) has to be configured to
accept VLAN tagged frames with the VLAN ID configured on the COSI1 unit.
→ The corresponding internal port on the CESM1 or CESM2 units has to be con-
figured to accept VLAN tagged frames with the VLAN ID configured on the
COSI1 unit.
Please note:
The EROP1 unit only supports VLAN tagged traffic on the internal ports.
→ The corresponding backplane port (when using CESM3) has to be configured to
accept VLAN tagged frames with the VLAN ID configured on the corresponding
EROP1 subinterface.
→ The corresponding internal port on the CESM1 or CESM2 units has to be con-
figured to accept VLAN tagged frames with the VLAN ID configured on the cor-
responding EROP1 subinterface.
5.3 Protocols
The FOX61x implements the standard protocol RSTP.
Follow the procedure below when setting up a protocol to prevent a loop:
• Setup all nodes and all ports in a ring or mesh structure using a common protocol.
• During setup set the administrative state of at least one port in the ring to “Down”.
• Connect the cables.

• Change the administrative state from “Down” to “Up” on all ports in the ring.
To simplify the configuration and troubleshooting an up-to-date network design should be avail-
able including all the relevant network and port configuration information.
This section describes the essential main steps to commission a switching protocol:
• 5.3.1 Set up a Spanning Tree using RSTP (on page 34).
5.3.1 Set up a Spanning Tree using RSTP
→ RSTP configuration. Proceed as follows:

1. Select the “Switching” view of the FOXCST.
2. Select “Switching / Protocols / Spanning Tree” in the tree view on the left hand side of the
FOXCST:
3. Select the Spanning Tree of bridge-1 in the Spanning Trees list. “RSTP” is the default span-
ning tree protocol used on the network element.
4. In the right part of the FOXCST select the “Status” tab to check the current settings.
5. In the right part of the FOXCST select the “Configuration” tab to configure the RSTP parame-
ters:

6. Select “Switching / Protocols / Spanning Tree / bridge-1” in the tree view on the left hand
side of the FOXCST:
7. In the port list table you can now enable RSTP by activating the “STP Enabled” check-box. If
the port must support the R-L2GP protocol enable also the “R-L2GP Enabled” check-box.
8. To display information for a specific port, select the STP enabled port in the ports table. This
opens further tabs on the right hand side of the FOXCST.
9. The “Status” tab presents the current settings:
10.In the “Configuration” tab you can configure the “Port Properties” and the “Path Cost” param-
eters. For R-L2GP enabled ports you can also configure the “Pseudo Root Bridge” parame-
ters:

11.Apply the configuration changes.

12.If required save the configuration persistently to the NE database with “Save to NE”.
Result: You have successfully set up a sample RSTP configuration for the Ethernet
Switching application.
End of instruction
5.4 Test of Readiness
5.4.1 Ethernet Services

Ethernet traffic is only working if all involved parts of the FOX61x network element are config-
ured correctly and in fault free state:
• The administrative and operational states have to be up on the
− used ports,
− used protocols
of all the core and service units.
• The VLANs must be configured and assigned on the relevant ports.
• The port modes must be configured correctly to transport the traffic and the relevant proto-
col.
• The protocol on the relevant ports must be enabled for loop prevention.
• No faults are reported in the FOXCST.
The FOX61x Switch is an Ethernet switch with its Ethernet ports distributed on all Ethernet units
within the FOX61x subrack. Using Ethernet stand-alone units the physical Ethernet ports can
even be on a remote FOX61x or a 3rd party device (e.g. using Ethernet over SDH). It is there-
fore up to the operator to coordinate the switching parameters on both link sides or in a broad-
cast multi-access network.

FOX61x | ETHERNET SWITCHING OPERATION
6 Operation
6.1 Status and Diagnostics
6.1.1 Bridge Status

For a detailed overview please refer to section 7.4 AP: / Switching / Bridges (on page 43).
6.1.2 Bridge Port Status

For a detailed overview please refer to section 7.5 AP: / Switching / Bridges / bridge-1 (on
page 44).
6.1.3 Spanning Tree Status

For a detailed overview please refer to section 7.7 AP: / Switching / Protocols / Spanning Tree
(on page 54).
6.1.4 Spanning Tree Port Status

For a detailed overview please refer to section 7.8 AP: / Switching / Protocols / Spanning Tree /
bridge-1 (on page 56).
6.2 Fault Management

The generic fault management aspects of the FOX61x are handled in the FOX61x User Manual.
Please refer to [1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611”.
6.3 Possible Faults and related Debugging

If a switching application has been created and configured but does not work, please check the
following hints to resolve the problem.
6.3.1 FOX61x active Failures

• Check the FOXCST “Alarms” tab:
The active alarms window lists in a table all active failures of the whole network element.
• The same information as with the FOXCST “Alarms” tab can be displayed with the network
element fault management at the AP: /ne:
The “Alarms” tab of the “Overview” management function lists in a table all active failures of
the whole network element.
You find the failure description and the possible failure causes in the corresponding unit user
manual or application user manual.
• If there are no active failures displayed for the service or application that is not performing as
required, you need to check for other possible causes. Please refer to the sections below.
6.3.2 Unit not available (UNAV alarm)

A reason for a service or application not performing as required can be a unit that is not avail-
able, or a unit that is not assigned.

• All units required for the service should be in the “OK” state:
The FOXCST “Tree View” shows the AP tree with all units.
• If a unit is in the “Plugged” state, you have to assign the unit under the AP: /unit-x, Main -
Equipment or using the context menu of the unit:
• A valid embedded software (ESW) for the unit has to be downloaded and configured under
the AP: /unit-x, Main - Software. For details about the ESW installation refer to
[1KHW002466] User Manual “FOXCST”.
• Configure the services as described in section 5 Commissioning (on page 25).
6.3.3 Port Down

• If you have not set the administrative state of a port to “Up”, the corresponding MO will be
fault free, but a switching service using this port will not perform since the resources required
for the service to work are inactive.
Check that all the ports are in the administrative status “Up” using the MO context menu as
shown above or selecting the Admin And Oper Status dialog, e.g. AP: /unit-x/port-y, Main -
Admin And Oper Status, or selecting the parent AP in the FOXCST “Commissioning” tab:
Set the administrative status to “Up”.
• Check that all the ports are in the operational status “Up” by selecting the Admin And Oper
Status dialog, e.g. AP: /unit-x/port-y, Main - Admin And Oper Status, or by selecting the par-
ent AP in the FOXCST “Commissioning” tab:
if the operational state is “Down” make sure
− that the failure status of the MO has no active alarm (e.g. LOS or AIS).
• Check that the port is configured correctly according to the application (e.g. Trunk).
6.3.4 Switching Services not working

Packet based networks are non-static networks. The active network structure can change using
layer 2 protocols, or devices and services can be added or removed. There is always a risk that
a network running without problems will show unexpected behavior as e.g. packet loss or
increased delay or jitter.
If a service is not working as expected first check the hints given in section 5.4 Test of Readi-
ness (on page 36). Then check the following points to solve the problem:
• Check the configuration parameters of the bridge in the FOXCST “Switching” view. Make
sure that all parameters are configured as required:
− Check the “Storm Control” parameters are enabled.
• Check the configuration parameters of the bridge ports in the FOXCST “Tree View”. Make
sure that all parameters are configured as required:
− Check the port Main parameters.
− Check the network element QoS parameters.
− Check the port QoS parameters.
• Check the internal ports TC Scheduling configuration of the service and core units.

The FOX61x backplane has a limited capacity and thus represents a potential point
of congestion. For more information about traffic scheduling please refer to refer to
[1KHW029124] User Manual “Quality of Service”.
6.3.4.1 Throughput not 100%

Because of the switch buffer resources persistent traffic with 100% load at SFP ports will gener-
ate a continuous small frame loss after a certain time.

Sustained zero frame loss is only possible if the network elements are synchronized via SyncE.
With the FOX61x system release R15B SyncE is supported on the core unit only.
6.3.4.2 Ethernet stand-alone service units

Ethernet stand-alone service units are connected via their internal port to the FOX61x Switch. A
service may not be working correctly when:
• the internal port parameters settings on both ends (different NEs) do not match.
• the protocol port parameter settings are not set as required.

FOX61x | ETHERNET SWITCHING USER INTERFACE REFERENCE
7 User Interface Reference

This section provides
• an overview of the managed object models (MOM) of the Ethernet switching related objects
in section 7.1 Managed Object Models (MOM) (on page 40), and
• the user interface reference of the FOX61x Ethernet switching function related management
functions in section 7.2 AP: / ne (on page 43) and following.
For a description about how to configure and bring into operation the Ethernet switching service
please refer to the section 5 Commissioning (on page 25) and section 6 Operation (on page 37).
In the tables of the sections below, the parameter default values for properties are underlined.
Please note:
For better legibility of numbers in this User Manual, inverted commas are used
when the number’s size exceeds three digits (e.g. 40’000). In parameter entry
fields of the FOXCST, these inverted commas must not be entered. Instead, the
numbers are entered without these inverted commas (e.g. 40000).
Please note:
Screenshots presented in this reference are examples and show configurations or
data that may not correspond to the view you see when managing your FOX61x
equipment.

Depending of the firewall settings of your element manager the display of the
FOXCST will not be updated correctly.
→ Enable the “Synchronization over Firewall” parameter in the Options menu of
the FOXCST.
7.1 Managed Object Models (MOM)
7.1.1 MOM for the Port Types and QoS

Figure 14 shows the AP tree and the management functions for the management of the port
type and QoS configuration, available in the FOXCST “Shelf View”, the FOXCST “Tree View”,
and the FOXCST “QoS” view.
The Port Type access point at the network element level shows all Ethernet ports available in
the NE. Note that the Port Type access point is also available at other layers, showing corre-
spondingly only a subset of all Ethernet ports.
• AP: / ne,
• AP: / backplane (when using CESM3),
• AP: / backplane / port-b (when using CESM3),
• AP: / unit-x / port-y,
• AP: / unit-x / iports / iport-z (on CESM1 and CESM2 only),
• AP: / unit-x / eos / eos-y (on SAMOx only),
• AP: / unit-x / eth/ port-y (on DEFM1 only).
With this MO you determine whether an Ethernet port is available for an Ethernet switching ser-
vice:
• Set the Port Type usage = CVP
The switching port is configured as customer VLAN port.
The QoS access point at the network element level shows the QoS parameter valid for all func-
tions in the network element.

• AP: / ne.
QoS parameters valid for a specific function or an interface only have to be configured on the
function (e.g. MPSL-TP) or the interface itself.
Tree View QoS
<a p> <a p>

FOX61x QoS
<mf> <mf>
Main QoS
<a ttribute> <a ttribute>

Por t Type Rate Li miting
Counters
Traffic Cla ssification
DSCP to PHB
PHB to PS C
To TC Map pings
TC Schedu ling Profiles
To E XP Mapping s
Resource Usage
Drop Profiles 1 1 CESM3
Default Sh apers 1
Class Type Sh apers 1
Figure 14: Port Type and QoS access points
Please note:
The QoS functions
- EXP to TC Mapping,
- PHB to EXP Mapping,
- PCP to EXP Mapping,
- Priority to EXP Mapping, and
- Class Type Shapers
are related to the MPLS-TP functionality of the FOX61x.
→ Please refer to [1KHW029124] User Manual “Quality of Service”.
7.1.2 MOM for the Switching Configuration

The FOX61x Switch is managed with the FOXCST using the management functions of the
FOXCST “Switching” view.
Figure 15 shows the AP tree and the management functions for the management of the FOX-
61x Switch.

<a p>
FOX61x
1 <a p>
Switchi ng
1 <a p>
Brid ges
1 <a p>
brid ge-1
1 <a p>
Pro tocols
1 <a p>
Spa nning Tree
1 <a p>
brid ge-1
Figure 15: MOM of the FOXCST “Switching” view
With these managed objects (MOs) the following functions are covered:
Table 3: FOX61x Managed Objects (MOs)

MO Description of the management functions
Switching Top AP for all FOX61x switching related items.
Bridges Configuration of the switching bridges “General” param-
eters.
Further information can be found in section 7.4 AP: /
Switching / Bridges (on page 43).
Bridges/bridge-1 Configuration of the switching bridge ports and
VLANs of the FOX61x Switch. Configuration and status
of the “Storm Control” and VLAN parameters on a
bridge port.
Switching / Bridges / bridge-1 (on page 44).
Protocols Parent MO for the Spanning Tree protocol.
Switching / Protocols (on page 54).
Spanning Tree Configuration and status of the Spanning Tree pro-
tocol global parameters. Dual Homing configura-
tion.
Switching / Protocols / Spanning Tree (on page 54).
Spanning Tree/bridge-1 Configuration and status of the Spanning Tree
bridge ports.
Switching / Protocols / Spanning Tree / bridge-1 (on
page 56).

7.2 AP: / ne
Please note:
The Access Point (AP) named “ne” in the AP tree of the FOXCST shows the addi-
tional information “FOX615 R2”, “FOX615”, “FOX612” or “FOX611”. For reasons of
simplicity and clarity, this additional information is not shown in the following sec-
tions since it is not used while navigating in the FOXCST.
Please note:
In the FOXCST dialog windows the “ne” AP is identified with a forward slash “/”. In
the following sections the identifier “/” is used instead of the identifier “ne”.
7.2.1 AP: / ne, Main

− “Main - Port Type
management function, please refer to [1KHW002464] User Manual “FOX615
7.3 AP: / Switching

This AP in the navigation window of the FOXCST “Switching” view is a structure element only
and does not provide any configurable parameters.
7.4 AP: / Switching / Bridges
7.4.1 AP: / Switching / Bridges, Bridges

The FOX61x provides one bridge instance named “bridge-1”:
Table 4: Bridges
Operation Name Parameter Name Range Description / Details
ID bridge-1 Bridge-1 is the only bridge (in the current
release).
Name Customer Bridge Customer Bridge is the only bridge.
Selecting the bridge-1 Customer Bridge in the information and control window opens the detail
information window.

7.4.1.1 AP: / Switching / Bridges, Bridges - General
Table 5: Bridges - General

Basics MAC Address <MAC address> Bridge MAC address.
Number of 5 … maximum given by Number of available bridge ports in the FOX61x
Bridged Ports inserted units Switch.
VLAN Max. VLAN ID 4089 Maximum value of the VLAN ID.
Max. Number of 4089 Maximum number of supported VLANs.
VLANs
Number of VLANs 1 … 4089 Number of configured VLANs.
MAC Learning Aging Time 10 … 300 … 672 s Aging time is the time after which a learned
MAC address is removed from the MAC
address table if no more packets are
detected with the respective source MAC
address.
Addresses Learned 0 … 64’000 Current number of learned MAC addresses.
Addresses Dis- 0 … 64’000 Current number of MAC addresses discarded.
carded
7.5 AP: / Switching / Bridges / bridge-1

By selecting the AP “Switching / Bridges / bridge-1” in the navigation window the Ports and
VLANs tabs will be displayed in the information and control window.
7.5.1 AP: / Switching / Bridges / bridge-1, Ports
7.5.1.1 AP: / Switching / Bridges / bridge-1, Ports - Global Parameters

The ports table displays all available FOX61x Switch ports and their configuration.
Only ports that are configured to the port type “CVP” are available in the ports table. For the port
type configuration please refer to [1KHW002464] User Manual “FOX615

Table 6: bridge-1, Ports - global parameters

Reference <MO address> MO address of the FOX61x Switch Ethernet
ports.
Mode Trunk Standard Trunk mode according IEEE 802.1Q
available on all switches. For a detailed
description see section 4.1.2 VLAN Port Modes
(on page 14).
Access Standard Access mode available on all
switches. For a detailed description see section
4.1.2 VLAN Port Modes (on page 14).
Trunk with Native VLAN The Trunk with Native VLAN mode allows to
carry untagged traffic over a trunk link. For a
detailed description see section 4.1.2 VLAN Port
Modes (on page 14).
General The proprietary General mode allows full flexi-
bility to configure a bridge port. For a
detailed description see section 4.1.2 VLAN Port
Modes (on page 14).
Q-in-Q The Q-in-Q mode allow to add and remove a
tag on a trunk port. For a detailed description
see section 4.1.2 VLAN Port Modes (on
page 14).
Unswitched This mode is only available for specific units
excluding the port from the FOX61x Switch. For
a detailed description see section 4.1.2 VLAN
Port Modes (on page 14).
PVID 1 … 4089 Port VLAN ID, applicable for the
- Access
- Trunk with Native VLAN
- Q-in-Q
- General
port modes.

Table 6: bridge-1, Ports - global parameters (continued)

Acceptable Frame- Tagged Only tagged frames are accepted at the
types ingress port, applicable for the
- Trunk (default, cannot be changed)
- General
- port modes.
Untagged and Priority Only untagged and priority tagged frames are
tagged accepted at the ingress port, applicable for
the
- Access (default, cannot be changed)
- General
port modes.
All All frames are accepted at the ingress port,
applicable for the
- Trunk with Native VLAN (default, cannot be
changed)
- General
- Q-in-Q (default, cannot be changed)
port modes.
Ingress Filtering This mode is only available in the General port
mode. When activated, any ingress frame is
discarded that does not match any of the
VLANs configured in “VLAN Configuration”
for that port. For more information see section
4.1.3 General VLAN Port Mode (on page 16).
When ingress filtering is disabled the general
ingress port forwards or drops Ethernet
frames dependent of the “Acceptable Frame-
types” configuration. For more information
see section 4.1.3 General VLAN Port Mode (on
page 16).
Storm Control This check box is read-only.
It is enabled when selecting one of the traffic
types in the Storm Control configuration. This
parameter applies for the
- Trunk
- Access
- Trunk with Native VLAN
- General
- Q-in-Q
port modes.
No traffic type is selected in the Storm Con-
trol configuration.
Bridge-1 ports can be configured in two different ways in the FOXCST:

• Right mouse button selection:
By selecting the right mouse button all port parameters of the selected table row(s) are avail-
able.

• Direct selection:
Selecting the parameter directly by clicking into the table field.
Ports can be added to the table or removed from the table with the following FOXCST buttons:
• Add a port:
Add a port to the bridge ports table. In the “Select a Port” dialog tick the required ports that
shall be added. Only ports with the port type usage “None” are selectable. The port type
usage of the added port(s) is set to “CVP”.
• Remove a port:
Remove the selected port(s) from the bridge ports table. The port type usage is reset to
“None”.
The content of the ports table can be filtered with the following FOXCST buttons:
• Filter for a Unit:
All units or a specific unit being part of the FOX61x Switch are selectable in the filter list. Per
default the ports of all units are displayed.
• Filter for the port mode:
All bridge-1 ports where the mode button is dark shaded are displayed in the bridge-1 ports
list. When clicking on a mode button, the button becomes light shaded and the correspond-
ing bridge-1 ports are hidden.
Per default all bridge-1 ports are displayed.
• Filter for a PVID:
Immediately after entering the first numerical value the ports list will be updated and the sym-
bol on the right of the entry field changes:

The port list can be cleared by deleting the characters with the keyboards “Delete” button or
by selecting the icon on the right side of the entry field.
Please note:
When using Ethernet stand-alone service units (i.e. EPSI1, ESOP1, ESPO1,
EROP1, SAMO1, CEPI1, COSI1, TEPI2, OPIC2, TEGO1) first assign the core unit
before assigning the Ethernet stand-alone unit.
→ Otherwise the internal ports of the core unit connecting the Ethernet stand-
alone units will not be available in the ports table.
When configuring a “General” port the following rules should be followed:
• A VLAN membership is required for the “General” port mode.
• If “Acceptable Frametypes” is set to “Tagged” the “Egress Frametype” for the VLAN Mem-
bership should be set to “Tagged Frames”.
• If “Acceptable Frametypes” is set to “Untagged and Priority tagged” or to “All” the PVID
VLAN should be added to the VLAN Membership with “Egress Frametype” set to “Untagged
Frames”.
• If “Acceptable Frametypes” is set to “Untagged and Priority tagged” or to “All” only one VLAN
Membership should be configured with “Egress Frametype” set to “Untagged Frames”.
Please note:
While configuring a port with its mode set to “General” inconsistent settings that do
not fulfill the above rules are indicated with an exclamation mark in the left most
column of the ports table. When you move the mouse pointer to the exclamation
mark a tool-tip indicates the cause(s) for the inconsistency. Such settings may well
be working for your special requirements, but are rather unusual. The following
table shows appropriate remedial actions:
Table 7: Inconsistent settings for “General” ports

Tool-tip message Remedial action
No VLAN Membership configured Configure at least one VLAN for this
port; see section 7.5.1.3 AP: / Switching /
Bridges / bridge-1, Ports - VLAN Configu-
ration (on page 49). With this the port is
member of at least one VLAN.
The port is configured to admit tagged If you made the setting intentionally, it
frames only, but to be an untagged is OK. If not, make sure the egress
member of at least one VLAN frame type for all VLANs of this port is
set to “Tagged Frames”. See section
7.5.1.3 AP: / Switching / Bridges / bridge-
1, Ports - VLAN Configuration (on
page 49).
The port is currently not an untagged If you made the setting intentionally, it
member of the Port VLAN (PVID = N) is OK. If not, add the port to the Port
VLAN; i.e. go to the “VLAN Configura-
Note: “N” is the VLAN ID of the Port tion” dialog (see section 7.5.1.3 AP: /
VLAN. Switching / Bridges / bridge-1, Ports -
VLAN Configuration (on page 49)), and
add the PVID so that the port is member
of the Port VLAN. Make sure the Egress
Frametype for the PVID is set to
“Untagged Frames”.

Table 7: Inconsistent settings for “General” ports (continued)

Tool-tip message Remedial action
The port is currently configured to be If you made the setting intentionally, it
an untagged member of more than is OK. If not, set the Egress Frametype
one VLAN of all VLANs but one to “Tagged
Frames”. Keep only one VLAN set to
“Untagged Frames”. See section 7.5.1.3
AP: / Switching / Bridges / bridge-1, Ports
- VLAN Configuration (on page 49).
7.5.1.2 AP: / Switching / Bridges / bridge-1, Ports - VLANs

The ports VLANs dialog is available for the following port modes:
• Trunk
• Access
• Trunk with Native VLAN
• General
• Q-in-Q
Table 8: bridge-1, Ports - VLANs

VLAN Membership ID 1 … 4089 Forwarded VLANs on a switch port according
to the port mode and PVID configuration.
Name 1 … 32 characters Name of the VLAN defined in the VLAN con-
figuration.
Egress Frametype Tagged Frames The following port modes forward tagged
frames at an egress port:
- Trunk (default, cannot be changed)
- Trunk with Native VLAN (default, except
default VLAN 1 which is untagged)
- General (configurable)
Untagged Frames The following port modes forward untagged
frames at an egress port:
- Access (default, cannot be changed)
- Trunk with Native VLAN (default VLAN 1
only)
- General (configurable)
- Q-in-Q (default, cannot be changed)
7.5.1.3 AP: / Switching / Bridges / bridge-1, Ports - VLAN Configuration

The ports VLAN configuration dialog is available for the General port mode.

Table 9: bridge-1, Ports - VLAN Configuration

VLAN Membership VLAN IDs 1 … 4089 Added VLANs configured with the “Add to
VLANs” button.
Egress Frametype Untagged Frames Configured Egress Frametype with the “Add
Tagged Frames to VLANs” button.
The content of the VLAN configuration table can be managed with the following FOXCST but-
tons:
• Add a VLAN or a range of VLANs:
This command opens the “Enter a Range of allowed VLANs” dialog:
Table 10: bridge-1, Ports - VLAN Configuration - Add to VLAN

VLANs 1 … 4089 Enter one VLAN or a VLAN range (e.g. 18-23)
to be accepted in the “General” mode.
Egress Frametype Tagged Frames Select the desired Egress Frametype.
Untagged Frames
Current VLANs Id 1 … 4089 ID of the configured VLANs.
Name 1 … 32 characters Name of the configured VLANs.
Please note:
All VLANs within the range will be accepted including the VLANs which are not yet
configured! Do not forget to configure the VLANs otherwise the traffic will not be
forwarded.
• Delete a VLAN or a range of VLANs:
This command deletes the selected VLAN(s).

7.5.1.4 AP: / Switching / Bridges / bridge-1, Ports - Storm Control
Table 11: bridge-1, Ports - Storm Control

Traffic Type Broadcast Activates the ingress rate limiter for broad-
cast packets on the respective port.
The ingress rate limiter is disabled.
Multicast Activates the ingress rate limiter for multi-
cast packets on the respective port.
Unknown Unicast Activates the ingress rate limiter for unknown
unicast packets on the respective port.
Known Unicast Activates the ingress rate limiter for known
unicast packets on the respective port.
Traffic Threshold Threshold 0 … 100% Traffic limit for the total of broadcast, multi-
cast and/or unicast packets. The threshold is
applied in relation to the port speed.
7.5.1.5 AP: / unit-x / Switching / Bridges / bridge-1, Ports - Packet Connectivity

− “Ports - Packet Connectivity”
management function, please refer to [1KHW002464] User Manual “FOX615
7.5.1.6 AP: / unit-x / Switching / Bridges / bridge-1, Ports - Rate Limiting

− “Ports - Rate Limiting”
management function, please refer to [1KHW029124] User Manual “Quality of Service”.
7.5.1.7 AP: / unit-x / Switching / Bridges / bridge-1, Ports - Traffic Classification

− “Ports - Traffic Classification”
management function, please refer to [1KHW029124] User Manual “Quality of Service”.

7.5.2 AP: / Switching / Bridges / bridge-1, VLANs
7.5.2.1 AP: / Switching / Bridges / bridge-1, VLANs - Global Parameters

The VLANs table displays all created VLANs. VLANs can be created and deleted:
Table 12: bridge-1, VLANs - global parameters

VLANs ID 1 … 4089 VLAN ID
# Members 0… Number of FOX61x Switch ports which are mem-
ber of the VLAN.
Name 1 … 32 characters Enter a name describing the VLAN.
VLANs are managed with the following FOXCST buttons:

• Create a new VLAN:
When clicking on this button the FOXCST launches the dialog window to create a new
VLAN.
• Create VLANs in bulk:
When clicking on this button the FOXCST launches the dialog window to create VLANs in
bulk.
Table 13: bridge-1, VLANs - global parameters - add VLAN

Create a new VLAN VLAN ID 2 … 4089 Enter a single VLAN ID
VLAN 1 (default) must not be configured.
Name 1 … 32 characters Enter a name describing the VLAN.

Table 13: bridge-1, VLANs - global parameters - add VLAN

Create VLANs in Range of VLANs 2 … 4089 Enter a VLAN range.
bulk - a single VLAN ID (e.g. 10)
- a range of VLAN IDs (e.g. 10-20)
- a sequence of VLAN IDs (e.g. 10,15,20)
- a sequence of ranges (e.g. 10-20,30,40-50)
VLAN 1 (default) must not be configured.
• Delete a VLAN:
When clicking on this button all selected VLANs in the VLANs table are deleted.
7.5.2.2 AP: / Switching / Bridges / bridge-1, VLANs - Ports

Selecting a specific VLAN in the VLANs table shows the member ports in the detail information
window.
Table 14: bridge-1, VLANs - Ports

Member Ports Reference <MO address> Shows all the physical ports assigned to the
selected VLAN.
Egress Frametype Tagged Frames Shows the Egress Frametype assigned to the
Untagged Frames member port.
7.5.2.3 AP: / Switching / Bridges / bridge-1, VLANs - MAC Filtering

Selecting a specific VLAN from the VLANs table shows the MAC filtering database in the detail
information window.

Table 15: bridge-1, VLANs - MAC Filtering

Filtering Database MAC Address <MAC address> Shows the learned MAC address.
Port <MO address> Shows the FOX61x Switch port where the MAC
was learned.
Status Other None of the following. This may include the
case where some other MIB objects are being
used to determine if and how frames,
addressed to the corresponding instance of
the FDB address, are being forwarded.
Learned Shows the learned MAC addresses.
Self The value of the corresponding instance of
the FDB address represents one of the device
addresses. The corresponding instance of the
FDP port indicates which of the device ports
has this address.
Management The value of the corresponding instance of
the FDB address is also the value of an exist-
ing instance of the bridge static unicast
addresses.
• Refresh the filtering database:
When clicking on this button MAC filtering database is refreshed.
7.6 AP: / Switching / Protocols

This AP in the navigation window of the FOXCST “Switching” view is a structure element only
and does not provide any configurable parameters.
7.7 AP: / Switching / Protocols / Spanning Tree
7.7.1 AP: / Switching / Protocols / Spanning Tree, Spanning Trees

The FOX61x provides one bridge instance:
By selecting the AP “Spanning Tree”, the bridge-1 Customer Bridge in the information and con-
trol window will be automatically selected.
Table 16: Spanning Trees

Instance Spanning Tree Spanning Tree is the only instance.
Protocol RSTP The bridge supports the RST protocol.
Bridge bridge-1 The bridge-1 is the only bridge (in the current
release).

Selecting the bridge-1 Spanning Tree in the information and control window opens the detail
information window.
7.7.1.1 AP: / Switching / Protocols / Spanning Tree, Spanning Trees (RSTP) - Status
Table 17: Spanning Trees (RSTP) - Status

Spanning Tree Local Bridge <MAC address> Local Bridge MAC address.
Priority 0 … 61’440 Configured Local Bridge priority.
Root Bridge <MAC address> Root Bridge MAC address.
Priority 0 … 61’440 Configured Root Bridge priority.
Root Port Cost 0 … 2’147’483’647 Calculated cost from the local bridge to the
root.
Timing Parameters Maximum Age 6 … 40 s Configured maximum age.
Hello Time 1 … 10 s Configured hello time.
Forward Delay 4 … 30 s Configured forward delay.
Hold Time 1 … 10 s Configured hold time.
7.7.1.2 AP: / Switching / Protocols / Spanning Tree, Spanning Trees (RSTP) - Configuration
Please note:
All RSTP bridges in a network should use the same “Maximum Age”, “Hello Time”
and “Forward Delay” parameter values.

Table 18: Spanning Trees (RSTP) - Configuration

Spanning Tree Priority 0 … 32’768 … 61’440 Set the Local Bridge priority.
step 4’096
Tx Hold Count 1 … 6 … 10 Limit the BPDU transmission rate per port.
The bucket size is given by the Tx Hold Count.
Timing Parameters Maximum Age 6 … 20 … 40 s Set the maximum duration a switch port
keeps the learned BPDU information.
The selectable range depends on other timing
parameters.
Hello Time 1 … 2 … 10 s Set the time interval to send BPDU frames on
a port.
parameters.
Forward Delay 4 … 15 … 30 s Set the time to spend in the listening and
learning states.
parameters.
Dual Homing TC Propagation A topology change (TC) detected at an R-
to/from VPLS L2GP enabled bridge port will send a PW OAM
“MAC withdraw” message on the VPLS
pseudo wires which have attachment circuits
hosted by the R-L2GP port.
A pseudo wire OAM “MAC withdraw” message
detected at a VPLS pseudo wire will activate a
TC notification on the attached RSTP enabled
bridge ports.
No TC propagation towards the VPLS and no
“MAC withdraw” propagation towards the
RSTP enabled bridge ports.
TC Persistency 10 … 60 … 300 s Time to apply the TC notification towards
Time RSTP enabled bridge ports.
It also defines the RSTP TC filtering time, i.e.
within this time no additional pseudo wire
OAM “MAC withdraw” message can be initi-
ated if the TC Persistency Time is not expired.
This parameter can only be modified if “TC
Propagation to/from VPLS” is set to true.
Please note:
Please refer to [1KHW028618] User Manual “MPLS-TP Services” for a description
of the Dual Homing feature.
7.8 AP: / Switching / Protocols / Spanning Tree / bridge-1
7.8.1 AP: / Switching / Protocols / Spanning Tree / bridge-1, Ports
7.8.1.1 AP: / Switching / Protocols / Spanning Tree / bridge-1, Ports - Global Parameters
The ports table displays all FOX61x Switch Ethernet ports and their configuration.

Table 19: bridge-1, Ports - Global Parameters

Reference <MO address> MO address of the FOX61x Switch Ethernet
port.
STP Enabled The port exchanges BPDU frames to deter-
mine the port role and port state.
The port does not exchange BPDU frames.
Not enabling STP on the port requires special
attention to prevent loops!
R-L2GP Enabled This tick box is only available if STP is
enabled.
Enable the R-L2GP protocol. The port acts as
a pseudo RSTP root bridge port.
See section 4.2.2.2 Dual Link Connection (on
page 22).
The port is a normal RSTP port.
Port State Discarding RSTP port states.
Learning In case of STP fallback the port states are
- Blocking
Forwarding - Listening
- Learning
- Forwarding
- Disabled

Per default no Spanning Tree protocols are enabled on the FOX61x Switch. For
loop prevention enable Spanning Tree on the relevant ports before changing the
“Admin State” “from “Down” to “Up”.
The content of the ports table can be filtered with the following FOXCST buttons:
• Filter for a Unit:
All units or a specific unit being part of the FOX61x Switch are selectable in the filter list. Per
default the ports of all units are displayed.
• Filter for the STP configuration:
Filter the ports according to the STP configuration:

− All: Display all ports.
− Enabled: Display only ports with STP enabled.
− Disabled: Display only ports with STP disabled.
Per default all ports are displayed.
7.8.1.2 AP: / Switching / Protocols / Spanning Tree / bridge-1 (RSTP), Ports - Status
The port status is only available if the port has STP enabled.

Table 20: bridge-1 (RSTP), Ports - Status

Port Status Port State Discarding RSTP port states.
Learning In case of STP fallback the port states are
- Blocking
Forwarding - Listening
- Learning
- Forwarding
- Disabled
Path Cost 0 … 2’147’483’647 Ingress port path cost to the local bridge.
Edgeport The port is at the edge of an RSTP tree.
The port is never intended to be connected to
another switch device. It immediately transi-
tions to the forwarding state when enabled.
The port is not an Edgeport. The port is used
inside an RSTP tree.
Point-To-Point The port is connected by a point-to-point LAN
segment to exactly one other bridge.
The link type is not point-to-point.
Port Role Root RSTP port roles.
Alternate In case of STP fallback the port roles are
- Root
Designated - Designated
Backup - Blocking
Disabled
1
Disputed State Conflicts between neighbor bridges in decid-
ing port roles can put the port into a disputed
state and the port goes to blocking state.
For example a port with restricted role (see sec-
tion 7.8.1.3 AP: / Switching / Protocols / Span-
ning Tree / bridge-1 (RSTP), Ports -
Configuration (on page 59)) that fails to agree
with its neighbor bridge ends up in
- Port Role = Designated,
- Port State = Blocking,
- Disputed State = true.
Note: A port configured as pseudo root
bridge never activates the “Disputed State”,
but it can be activated at the remote end.

Table 20: bridge-1 (RSTP), Ports - Status (continued)

Spanning Tree Designated Root <MAC address> Shows the designated root bridge MAC
address.
Priority 0 … 61’440 Shows the designated root bridge priority.
Designated Bridge <MAC address> Shows the designated bridge MAC address.
Priority 0 … 61’440 Shows the designated bridge priority.
Designated Port slot (1…21) + Shows the port identifier of the port on the
port (1…nn) designated bridge for this port segment.
A root port can never be a designated port.
Priority 0 … 61’440 Shows the designated port priority.
Designated Cost 0 … 2’147’483’647 Shows the path cost of the designated port
of the segment connected to this port.
1. The Disputed State is not static, i.e. the active state can toggle. Perform several display refresh actions in the FOXCST
to get the effective state.
7.8.1.3 AP: / Switching / Protocols / Spanning Tree / bridge-1 (RSTP), Ports - Configuration
The port configuration is only available if the port has STP enabled.
RSTP without R-L2GP RSTP with R-L2GP

Table 21: bridge-1 (RSTP), Ports - Configuration

Port Properties Priority 0 … 128 … 240 Enter the port priority.
step 16
Auto Edgeport The port is at the edge of an RSTP tree.
The port is not at the edge of an RSTP tree.
Restricted TCN Restricted TCN prevents the propagation of a
received TCN flag to other ports.
Attached LANs will not flush the Filtering Data Base
(FDB).
Restricted Role 1 Restricted Role prevents a bridge port taking over
the root port role, so the port is always designated.
If a better BPDU arrives on this port, the Restricted
Role port does not take the BPDU into account. In
case of a conflict the port will take the alternate role
and go to blocking state to protect the core bridged
network.
Enable Restricted Role on all ports where the root
bridge should not appear, e.g. towards a customer
LAN. In this way a switch in the customer LAN
attached to the bridge port cannot take over the
root bridge role.
See section 4.2.2.1 Single Link Connection (on
page 21).
Path Cost Automatic Cost Enabling the automatic cost parameter adjusts the
port cost according to the effective Ethernet link
speed.
Disabling the automatic cost parameters allows the
user to configure the Manual Cost value.
Manual Cost 1 … 200’000’000 Configure the port cost if Automatic Cost is dis-
abled.
Pseudo Root MAC Address <MAC address> Enter the pseudo root bridge MAC address used by
Bridge 2 the R-L2GP port.
Default: 00:00:00:FF:FF:FF
Priority 0 … 61’440, Enter the pseudo root bridge port priority.
step 4’096
1. Only available when R-L2GP is disabled.

2. Only available when R-L2GP is enabled.

FOX61x | ETHERNET SWITCHING ANNEX
8 Annex
8.1 Associated FOX61x Documents

[1KHW028777] Release Note “FOX61x System Release R15B”
[1KHW028514] Information “Terms and Abbreviations”
[1KHW002460] System Description “FOX61x R15B”
[1KHW002497] Operating Instruction “Precautions and safety”
[1KHW002464] User Manual “FOX615 R2/FOX615/FOX612/FOX611”
[1KHW002461] Installation Instruction “FOX615 R2 and FOX615 Installation”
[1KHW002462] Installation Instruction “FOX612 Installation”
[1KHW029142] Installation Instruction “FOX611 Installation”
[1KHW002467] User Manual “TDM Services”
[1KHW028522] User Manual “Management Communication”
[1KHW002466] User Manual “FOXCST”
[1KHW028618] User Manual “MPLS-TP Services”
[1KHW029124] User Manual “Quality of Service”
[1KHW002475] User Manual “EPSI1”
[1KHW028556] User Manual “CEPI1”
[1KHW002476] User Manual “SAMO1”
[1KHW028668] User Manual “SAMO2, SAMO2-F, SAMO3, SAMO5, SAMO5-F”
[1KHW002469] User Manual “CESM1, CESM1-F”
[1KHW028642] User Manual “CESM2, CESM2-F”
[1KHW028774] User Manual “CESM3”
[1KHW029154] User Manual “EPEX1”
[1KHW028559] User Manual “COSI1”
[1KHW028911] User Manual “EROP1, EROP1-F”
[1KHW028775] User Manual “DEFM1, DEFM1-F”
[1KHW028634] User Manual “TEPI2”
[1KHW028635] User Manual “OPIC2”

FOX61x | ETHERNET SWITCHING ANNEX
[1KHW028684] User Manual “TEGO1”
[1KHW028776] Product Description “Feature Licenses for FOX61x”

Hitachi Energy Switzerland Ltd
Bruggerstrasse 72
5400 Baden - Switzerland
Phone: please refer to https://www.hitachienergy.com/contact-us/Customer-Connect-Center

(Customer Connect Center)
Email: communication.networks@hitachienergy.com
www.hitachienergy.com/communication-networks
Document ID: 1KHW028566
Copyright 2022 Hitachi Energy. All rights reserved.

Specifications subject to change without notice.

Switching Um

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Switching Um

Uploaded by

Copyright:

Available Formats

USER MANUAL

Document edition FOX61x System Release: R15B

Copyright and confidentiality Copyright in this document vests in Hitachi Energy.

Disclaimer ABB is a registered trademark of ABB Asea Brown Boveri Ltd.

Copyright 2022 Hitachi Energy. All rights reserved. 2

Copyright 2022 Hitachi Energy. All rights reserved. 3

6.3.3 Port Down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Copyright 2022 Hitachi Energy. All rights reserved. 4

1.1 Precautions and Safety

1.2 Symbols and Notations

Risk of operating trouble!

1.3 Document History

Copyright 2022 Hitachi Energy. All rights reserved. 5

Table 1: Document history (continued)

1.4 Target Audience

1.5 Definition of Terms

Copyright 2022 Hitachi Energy. All rights reserved. 6

2.2 FOX61x packet based core

Copyright 2022 Hitachi Energy. All rights reserved. 7

Packet data interfaces

10GbE or 1GbE star

2.3 FOX61x Switching Core and Service Units

2.3.1 Port Type Configuration

2.3.2 Ethernet Core and Service Units

Copyright 2022 Hitachi Energy. All rights reserved. 8

2.3.3 Ethernet Stand-Alone Units

port Core CVP network

Figure 3: FOX61x Switch with Ethernet stand-alone units

Copyright 2022 Hitachi Energy. All rights reserved. 9

2.3.4 Layer 2 Redundancy Protocols

Copyright 2022 Hitachi Energy. All rights reserved. 10

3.1 Feature Licenses

3.2 Functions and Specification

Copyright 2022 Hitachi Energy. All rights reserved. 11

4.1 Ethernet Switch with VLAN Support

4.1.1 FOX61x Switch Architecture

Copyright 2022 Hitachi Energy. All rights reserved. 12

ETOP1, ELET1 Core Unit

Port ETOP1, ELET1

Figure 4: VLAN bridging with single tagging in FOX61x

Port ETOP1, ELET1

Figure 5: VLAN bridging and EoS with single tagging in FOX61x

Copyright 2022 Hitachi Energy. All rights reserved. 13

4.1.2 VLAN Port Modes

Copyright 2022 Hitachi Energy. All rights reserved. 14

• General port mode

Copyright 2022 Hitachi Energy. All rights reserved. 15

Ingress port Egress port

Untagged VLAN-ID 1 VLAN-ID 1 Port VLAN-ID: Untagged

Untagged dropped VLAN-ID 1 VLAN-ID 1

VLAN-ID 40 dropped VLAN-ID 30 VLAN-ID 30

Trunk with native VLAN Trunk with native VLAN

Untagged VLAN-ID 1 VLAN-ID 1 Untagged

VLAN-ID 30 Bridge VLANs: VLAN-ID 30 VLAN-ID 20 Bridge VLANs: VLAN-ID 20

Untagged VLAN-ID 1 VLAN-ID 1 Untagged

Figure 6: VLAN port modes and frame handling example

4.1.3 General VLAN Port Mode

Copyright 2022 Hitachi Energy. All rights reserved. 16

• Acceptable frame types = Tagged

VLAN-ID 30 Bridge VLANs: dropped

VLAN-ID 30 Bridge VLANs: VLAN-ID 30

Copyright 2022 Hitachi Energy. All rights reserved. 17

• Acceptable frame types = All