ABB Power Systems

FOX61x
Ethernet Services
User Manual
User Manual FOX61x
Ethernet Services

Release History: Release 1: December 2012

Copyright and Confidentiality: Copyright in this document vests in ABB LTD.

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 ABB.
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 authorised by
contract or otherwise in writing by ABB.

Disclaimer: ABB has taken reasonable care in compiling this document, however ABB 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.
ABB 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.
ABB reserves the right to amend this document at any time without prior notice.

Blank pages: Any blank page present is to accommodate double-sided printing.

Document No.: 1KHW002468

ABB Switzerland Ltd

Power Systems
Bruggerstrasse 72
CH-5400 Baden
Switzerland © December 2012 by ABB Switzerland Ltd
Content

1 Preface 5
1.1 Precautions and safety 5
1.2 Symbols 5
1.3 Document history 5
1.4 Target audience 5
1.5 Definition of terms 6

2 Application description 7

3 Required items 8
3.1 Hardware and tools 8
3.2 Software 9
3.3 Feature licences 10

4 Commissioning 11
4.1 Introduction 11
4.2 Prerequisites 11
4.3 Commissioning steps 11

5 Annex 30
5.1 Associated FOX documents 30

FOX61xEthernet Services 3
4 FOX61xEthernet Services
 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 EN 60950 (Safety of Information Technology
Equipment).

1.2 Symbols

This User Manual uses the following symbols:

NOTICE Non-observance could result in equipment damage.

Failing to comply with this may result in physical damage.
→ Possible actions are given.

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 where applicable.

1.3 Document history

Table 1: Document history

Date FOX Release Changes since previous version
December 2012 R1 First version

1.4 Target audience

This User Manual is targeted at persons who are entrusted with the installa-
tion, provisioning, operation and administration of the system.

FOX61xEthernet Services 5
PREFACE

The persons targeted are

• the installation personnel, and/or
• the provisioning personnel.

Please note:
Only trained and skilled personnel (maintenance staff as per EN 60950) may
install and maintain the system.

1.5 Definition of terms

For an explanation of terms used in this document please refer to

1KHW028514 FOX61x Terms and Abbreviations.

6 FOX61xEthernet Services
 APPLICATION DESCRIPTION

2 Application description
The FOX switching function, called “chassis switch” is supported by the fol-
lowing pluggable units:
• CESM1 or CESM1-F (the core unit, see 1KHW002469 FOX61x CESM1),
• SAMO2 or SAMO2-F (SDH STM-16 / 4 / 1 unit, see 1KHW002477
FOX61x SAMO2),
• ETOP1 or ETOP1-F (12 port optical or electrical SFP Ethernet unit, see
1KHW002471 FOX61x ETOP1),
• ELET1 (24 port Electrical Ethernet unit, see 1KHW002472 FOX61x
ELET1).
The ports of these units are part of the chassis switch functionality and can
be operated as one logical entity.
The set of Ethernet ports that are part of the chassis switch are the basis for
the FOX61x application described in this User Manual.
Other units may also provide layer 2 functionality, but are not included in the
“chassis switch” function. Their layer 2 function needs to be configured on
the unit itself. For more information refer to 1KHW002459 FOX61x Release
Notes.
The figure below shows a sample application that uses the chassis switch
functionality.

Figure 1: Sample FOX61x application

For more information on system characteristics and features please refer to
1KHW002464 FOX61x System Description (sections “Ethernet traffic func-
tions” and “Customer bridge functionality”) and to 1KHW002466 FOXCST
Operation.

FOX61xEthernet Services 7
REQUIRED ITEMS

3 Required items
3.1 Hardware and tools

This section gives an overview of the hardware and tools which are neces-
sary to build up the FOX61x application shown in 2 "Application description"
(on page 7).

3.1.1 Subracks
For setting up one node one of the following FOX subracks is required:
• FOX615 with NE fan unit FAMO1
• FOX615 without fan unit for fanless operation
• FOX612 with fan unit FAMO2

3.1.2 Control units (HW)

One or two of the following core units are required (do not mix the two
types!):
• CESM1 for operation with NE fan unit only
• CESM1-F for fanless operation only

3.1.3 Service units (HW)

One or several of the following service units are required:
• SAMO2 for operation with a NE fan unit only
• SAMO2-F for fanless operation only
• ETOP1 for operation with a NE fan unit only
• ETOP1-F for fanless operation only
• ELET1 for operation with a NE fan unit only

3.1.4 Cables
The following cables are required:
• for connecting the FOX subrack to the DC power supply the power cable
for the FOX subrack is required, either part of the subrack package, or
ordered separately. Detailed subrack installation information is given in
1KHW002461 FOX615 Installation.
• for connecting the service PC to the management interface of the FOX:
an Ethernet cable with sufficient length, depending on the situation at the
location you are working in.
• for connecting any Ethernet equipment with user traffic to the switch:
Ethernet cables with sufficient length, depending on the situation on site,
or suitable optical fibres. Refer to 1KHW002498 FOX61x Electrical
Cables for more information.

8 FOX61xEthernet Services
 REQUIRED ITEMS

NOTICE Degrading or breaking of optical fibre with loss of communication link!

Excessive bending of optical fibres and ignoring the minimum bending radius
of 15 mm will cause degrading or breaking of the optical fibre with loss of
communication link.
→ Do not bend or press optical fibres.
→ Always keep at least the minimum bending radius.

3.1.5 Tools
For fixing the units in the subrack you’ll need:
• a set of screwdrivers for standard slot head screws no. 1 to 4, and
• a set of screwdrivers for “Phillips” head screws no. 1 to 3.

3.1.6 PC Hardware

In order to manage a FOX network element you need a suitable PC for

installation of the local craft terminal FOXCST. FOXCST runs on operating
systems as specified in 1KHW002459 FOX61x Release Notes, section
“management software”. For minimum requirements on PC hardware refer to
1KHW002459 FOX61x Release Notes.

3.2 Software

This section gives an overview of the software that is necessary to configure

and maintain the application described in 2 "Application description" (on
page 7).

3.2.1 Embedded Software (ESW)

Embedded software (ESW) for service units is provided on a CD-ROM or it
can be downloaded from the ABB Extranet, provided you have a valid
account.
Detailed information about the embedded software available for the current
release is available in the document 1KHW002459 FOX61x Release Notes.

3.2.2 FOXCST management software

The local craft terminal FOXCST is required for managing a node and its
functionality. Minimum version required is R1A.

FOX61xEthernet Services 9
REQUIRED ITEMS

3.3 Feature licences

Parts of the FOX functionality are subject to feature licences. For more infor-
mation on feature licences refer to 1KHW002459 FOX61x Release Notes.

Please note:
Only the SAMO2 or SAMO2-F unit requires a feature licence for STM-16
operation, but this feature is not directly related to the chassis switching
functionality.

10 FOX61xEthernet Services
 COMMISSIONING

4 Commissioning
4.1 Introduction

This section describes the steps to commission the FOX61x function (Ether-
net bridge, VLANs, switch ports, and Spanning Tree protocols) for a sample
application similar to the one shown in 2 "Application description" (on
page 7).

4.2 Prerequisites

In order to successfully get a FOX switching application up and running you

need to have appropriate knowledge of the FOX equipment, its functionality
and its possible management access. It is hence assumed that you have
read the relevant parts of the following FOX documents:
1KHW002464 FOX61x System Description,
1KHW002466 FOXCST Operation,
1KHW002459 FOX61x Release Notes,
and that you have purchased and made available the appropriate FOX
equipment.

4.3 Commissioning steps

This section describes the following essential main steps to commission an

FOX61x application:
• Prepare the hardware
• Prepare the FOX
• Prepare the service PC
• Assign and start software
•

4.3.1 Prepare the hardware

Proceed as follows:
1. Install the FOX subrack in a rack with all required cables (powering,
earthing, signal cables).
2. Install a fan if you have any units that require a fan unit. For details on
NE installation refer to 1KHW002461 FOX615 Installation.
3. Unpack the pluggable units and plug them into one of the slots of the
FOX subrack. You need at least a control unit in slot 11.

FOX61xEthernet Services 11
COMMISSIONING

4.3.2 Prepare the FOX

Once each of the required units is plugged in an appropriate slot and all
cables are connected,
Proceed as follows:
1. Switch on the power for the subrack.
2. Wait until the at least the core unit has started up (all four front LEDs are
on).

4.3.3 Prepare the service PC

Proceed as follows:
1. Get hold of a desktop or notebook PC with one of the supported operat-
ing systems, preferably Windows 7.
2. Install the FOXCST GUI from a CD-ROM, memory stick or via download
from the ABB Extranet; refer to 1KHW002465 FOXCST Installation for
more details.
3. Start the FOXCST from the link on the desktop or from the entry in “all
programs”; refer to 1KHW002466 FOXCST Operation for more details
on FOXCST operation.
4. Physically connect your PC to the local management port of the core unit
CESM1 or CESM1-F using an Ethernet cable.
5. Connect the FOXCST to the FOX you have prepared in “Prepare the
FOX”, using “File - Connect...”, via the “local” connection as shown in
Figure 2:

Figure 2: Set up connection to a NE

 FOXCST is now locally connected to your FOX.

Please note:
For other ways to connect to the FOX refer to 1KHW002465 FOXCST Instal-
lation.

12 FOX61xEthernet Services
 COMMISSIONING

Please note:
In order to access your FOX remotely you need to set up a suitable manage-
ment interface. Please refer to 1KHW002466 FOXCST Operation for more
details.

4.3.4 Assign and start software

Proceed as follows:
1. Select “Tools - Software Download...” from the FOXCST main menu:

Figure 3: Menu selection for ESW download

2. Select the required software for all units, by clicking on the “Software to
install” column for each of the entries in the table.
3. Click “Download and Start...” to start installation of the software. When
completed, click “Close”.
4. Re-connect to the FOX.

Please note:
For options to download and install ESW on a factory default core unit refer
to 1KHW002469 FOX61x CESM1.

4.3.5 Configure the application: Do common bridge settings

Proceed as follows:

1. Select the tab from the main tabs of the FOXCST GUI.
2. Select “Bridges” from the tree view on the left hand side of the ECST
GUI:

Figure 4: The “Bridge” instance in the “Switching” tree

3. Select the “bridge-1 Customer Bridge” from the table. This opens a
“General” and a “QoS” tab on the right hand side of the ECST window.
4. In the tab set the MAC learning aging time in the range 10 ..
672 s. This tab also provides some more properties with related status
information.

FOX61xEthernet Services 13
COMMISSIONING

5. In the tab, “Priority Mapping” set the “user priority to traffic class”
mapping that shall be applied to the bridge-1. This mapping is applicable
to ports that have “Trust L2” enabled; see step 24 (on page 20).

Figure 5: Default Priority Mapping settings

Risk of operating trouble!

The use of Traffic Class 7 may have a negative impact on system stability
since this traffic class is used for internal control traffic within the system.
→ Do not use traffic class 7 for the “user priority to traffic class” mapping.
→ Use only traffic classes 0 to 6 for the “user priority to traffic class”
mapping.
6. Set the “IP DSCP to traffic class” mapping; therefore make a preselec-
tion of the IP DSCP class by selecting “All”, or any of the “CS0” to “CS7”
entries in the Class Selector. Then set the “Traffic Class” and “Modify
PCP” (Priority Code Point) properties for each of the table entries. This
mapping is applicable to ports that have “Trust L3” enabled; see step 24
(on page 20).

Figure 6: Sample IP DSCP Mapping settings

Risk of operating trouble!

The use of Traffic Class 7 may have a negative impact on system stability
since this traffic class is used for internal control traffic within the system.
→ Do not use traffic class 7 for the “IP DSCP to traffic class” mapping.
→ Use only traffic classes 0 to 6 for the “IP DSCP to traffic class” map-
ping.

14 FOX61xEthernet Services
 COMMISSIONING

7. Define up to 4 scheduling profiles to be used as default on the bridge.

Profile 1 is predefined and cannot be edited. Profiles 2 to 5 can be edited
by setting the algorithm, and the weight if the algorithm is different from
“Strict Priority”.

Figure 7: Scheduling Profiles

 You can apply any one of these profiles to physical ports (see the
“QoS” tab of physical ports in the user manual of Ethernet units).
End of instruction for common bridge settings

4.3.6 Configure the application: Do the bridge VLANs setup

In order to configure the chassis switch to behave like several smaller

switches VLANs are created and applied.

8. Make sure you have selected the main tab.

9. Select “bridge-1” from the “Switching - Bridges” tree on the left hand side
of the FOXCST GUI:

Figure 8: The “bridge-1” instance in the “Switching” tree

10. Select the tab. This will display all existing VLANs.
11. Click the “Create” button to create a new VLAN, or click the “Create
Bulk...” button to create a range of new VLANs:

Figure 9: Dialogue to create a new VLAN

FOX61xEthernet Services 15
COMMISSIONING

Figure 10: Dialogue to create a range of new VLANs

12. Enter a VLAN ID in the range 2 .. 4094 and a name for the new VLAN,
or, for bulk configuration, enter a VLAN range, e.g. “100-150”. Click OK
to apply.
 The VLAN(s) is (are) added to the list of VLANs. If required, repeat
this for further VLANs to be configured.
13. For VLANs created as bulk you may need to enter a name for each of
the VLANs by editing each VLAN’s name in the VLAN list:

Figure 11: Dialogue to edit VLAN names

Please note:
You can create a VLAN also by applying a port VLAN ID (PVID) to a chassis
switch port as shown in step 20 (on page 19) below. If you want to assign a
name to a VLAN created this way you will however have to add a name as
shown in step 13 above.

Please note:
If you want to configure VLAN memberships for “General” ports (see step 19
(on page 17) below), we recommend that you configure the required VLANs
as early as possible. Ports can be added to existing VLANs as shown further
below. You can however add VLANs at any time if required.
14. To display information for a specific VLAN, select the VLAN from the
table. This displays its member ports (upper part of the VLAN proper-
ties):

Figure 12: Display VLAN member ports (sample after configuration)

15. To check the learned MAC addresses for a specific VLAN click on the
refresh button below the “Filtering Database” title (lower part of the VLAN
properties):

16 FOX61xEthernet Services
 COMMISSIONING

Figure 13: Display VLAN forwarding database showing learned MAC

addresses (sample after configuration)
End of instruction for bridge VLANs setup

4.3.7 Configure the application: Do the bridge ports setup

16. Select the tab.

17. Select a port listed in the list of the “Ports” tab:

Figure 14: A port instance selected in the list of bridge-1 ports

18. You can filter the listed ports by unit, PVID, and port mode using the cor-
responding filter elements:

Figure 15: Bridge ports display filters

19. Modify the port mode as required:

Figure 16: Port mode configuration

FOX61xEthernet Services 17
COMMISSIONING

Please note:
The following port modes are available:
• Trunk:
A trunk port forwards VLAN tagged frames only. In ingress direction all
VLAN tagged frames for VLANs in the VLAN list (see section 4.3.6) are
accepted. Untagged or priority tagged frames are dropped. Inside the
chassis switch the frames keep their VLAN ID.
In egress direction all frames are forwarded with their VLAN ID. A trunk
port has no PVID (see step 20 (on page 19) below).
• Access:
An access port forwards untagged or priority tagged frames only. In
ingress direction only untagged or priority tagged frames are accepted;
the latter become tagged with the PVID (see step 20 (on page 19)
below). The PVID must be member of the bridge VLANs. VLAN tagged
frames are dropped.
In egress direction frames with the PVID are forwarded as untagged
frames, i.e. the VLAN ID is removed. All other frames are dropped.
• Trunk with Native VLAN:
A trunk with native VLAN port forwards all frames. In ingress direction all
VLAN tagged frames are accepted whose VLAN-ID is member of the
bridge VLANs. Untagged or priority tagged frames are tagged with the
PVID.
In egress direction frames carrying the PVID are forwarded as untagged
frames, i.e. the VLAN ID is removed. All other frames are forwarded with
their VLAN ID.
• General:
A general port gives full flexibility in configuring a bridge port, i.e. for each
VLAN you can configure its behaviour as required. Ingress frames can be
“all”, “untagged and priority tagged”, or “VLAN tagged”. Untagged frames
are tagged with the PVID.
In egress direction for frames tagged with any bridge VLAN ID you can
configure the egress frame type (tagged, untagged).
For more information refer to the Ethernet switch description in
1KHW002464 FOX61x System Description.

Please note:
You can select several ports using the mouse in combination with the “Strg”
(“Ctrl”) or the “Shift” key of the keyboard, and set the port mode for these
selected ports via the context menu selection “Set Mode”:

Figure 17: Multiple port mode configuration

18 FOX61xEthernet Services
 COMMISSIONING

Please note:
Only the port mode “General” allows “VLAN Configuration” to be set.
→ If port mode is set to “General” you can configure (add or remove) the
VLANs for that port:

Figure 18: VLAN configuration dialogue

→ To add the selected port to one or several VLANs click “Add to
VLANs” and enter the VLANs or VLAN range(s). If frames shall be
sent untagged for the respective VLAN on the selected port, select
“Untagged Frames”, else leave the default “Tagged Frames”:

Figure 19: Add port to VLANs dialogue

Risk of operating trouble!

If a VLAN is entered that currently doesn’t exist as bridge VLAN, the VLAN is
not automatically created, and no warning will be issued. Traffic will not be
forwarded in that VLAN unless you create the VLAN.
→ In order to make such a VLAN effective you need to configure it as
bridge VLAN. Refer to step 10 (on page 15) above.
20. Set the port VLAN ID (PVID) in the range 1 .. 4089. This option is availa-
ble for ports in “Access”, “General”, and “Trunk with Native VLAN” mode,
but not for “Trunk” mode. The port VLAN ID (PVID) is automatically cre-
ated as bridge VLAN (confirmation required) and added to all untagged
ingress frames on the port.
21. Set the acceptable frame types. All ingress frames that do not match this
setting are discarded:

FOX61xEthernet Services 19
COMMISSIONING

Figure 20: Set acceptable frame types

22. Set the default priority for the port. This priority is used for prioritizing the
frames within the switch if no priority information is available for a spe-
cific frame, or if both “Trust L2” and “Trust L3” (see step 23 below) are
disabled:

Figure 21: Set the default priority

23. Activate the ingress filtering if required by checking the checkbox. When
activated, any ingress frame is discarded that does not match any of the
VLANs configured in “VLAN Configuration” (see Figure 18) for that port.

Figure 22: Ingress filtering activated

24. Select the QoS tab to configure QoS settings for the selected port. Set
the mapping of “received priority” to “regenerated priority”. This will be
applied to frames received on the port provided the 802.1Q priority bits
are set.It will also be applied to Default Priority of the port (see step 22
above).

20 FOX61xEthernet Services
 COMMISSIONING

Enable or disable the trust modes. “Trust L2” means that the received
priority bits are used for queueing of the frame. “Trust L3” means the IP
DSCP bits are used for frame queueing.

Figure 23: QoS Settings with trusting L2 activated

25. Check the status of a port by selecting the required port from the port list
and clicking on the “Status” tab. This shows a list of VLANs assigned to
that port. VLANs are shown with VLAN ID, the configured name, and the
egress frame type (tagged or untagged):

Figure 24: Display of port status information

26. In order to allow frames to pass through your chassis switch you need to
set the admin state of all required ports to “up”. You do this by either
− changing to the “Commissioning” tab of the FOXCST GUI, selecting
the appropriate unit on it physical unit, and setting the admin state in
the “Main, Administrative Status, State” column of the “Port (Ethernet)”
tab from “Down” to “Up” (in-line editing of the table entries or use of
context menu; multiple selection of ports is supported),
or
− changing to the “Tree View” tab of the FOXCST GUI, selecting the
appropriate port on its physical unit, and setting the “Admin Status” in
“Main - General” to “Up”.

27. Click on the “Apply changes to NE” icon in the FOXCST main win-
dow’s icon bar.

FOX61xEthernet Services 21
 28. If required click on the “Save to NE” icon to persistently save the
settings to the NE database.
 You have successfully set up a sample bridge configuration for the
FOX61x application.
End of instruction for bridge ports setup

4.3.8 Configure the application: Do the Spanning Tree setup (RSTP)

To set up the Spanning Tree proceed as follows:

29. If not yet done, select the tab from the main tabs of the
FOXCST GUI.
30. Select “Spanning Tree” from the “Switching - Protocols” tree on the left
hand side of the FOXCST GUI:

Figure 25: The “Spanning Tree” instance in the “Switching” tree

31. Select “bridge-1 Customer Bridge RSTP” from the list view on the right
hand side of the “Switching” tree. This will pre-select RSTP as the span-
ning tree protocol used on the node.

Please note:
If you want to use MSTP instead of RSTP, proceed with step 42 below.

Figure 26: The “RSTP” instance selected from the protocol list
 This opens a “Status” and a “Configuration” tab in the right part of the
GUI.
32. Select the “Status” tab to check the current settings. This may show set-
tings as follows:
 COMMISSIONING

Figure 27: Sample “RSTP” status

33. Select the “Configuration” tab to configure the RSTP settings:

Figure 28: Sample “RSTP” settings for “Priority”, “Maximum Age”, “Hello
Time”, “Forwarding Delay”, and “Tx Hold Count”.
34. Select “bridge-1” from the tree view on the left hand side of the FOXCST
GUI:

Figure 29: The “bridge-1” instance in the “Switching - Protocols” tree

35. From the list of ports that support RSTP you can now enable RSTP on
all required switch ports by activating the “STP Enabled” checkbox:

Figure 30: Sample of enabling RSTP on switch ports

36. Click on the “Status” tab for the selected port.
 This presents the current settings as shown in the following example:

FOX61xEthernet Services 23
COMMISSIONING

Figure 31: Sample of a port’s RSTP status

37. Click on the “Configuration” tab for the selected port.
 Select the required “Priority” and “Path Cost” settings:

Figure 32: Sample of RSTP port settings

38. Click on the “Apply changes to NE” icon in the FOXCST main win-
dow’s icon bar.

39. If required click on the “Save to NE” icon to persistently save the
settings to the NE database.
 You have successfully set up a sample RSTP configuration for the
FOX61x application. If you now go on with the next steps, you’ll lose
your RSTP settings because the modes RSTP and MSTP can only be
used exclusively.
End of instruction for RSTP setup

4.3.9 Configure the application: Do the Spanning Tree setup (MSTP)

40. If not yet done, select the tab from the main tabs of the
FOXCST GUI.
41. Select “Spanning Tree” from the tree view on the left hand side of the
FOXCST GUI:

24 FOX61xEthernet Services
 COMMISSIONING

Figure 33: The “Spanning Tree” instance in the “Switching” tree

42. If you want to use MSTP instead of RSTP select the “bridge-1 Customer
Bridge” entry and change “RSTP” to “MSTP” by selecting MSTP in-line.

Figure 34: The “MSTP” instance selected from the protocol list

Please note:
If you have configured any MSTP or RSTP settings before, you will lose
those settings when changing the STP mode of operation. To make you
aware of this a warning message is issued:

Figure 35: Warning when changing the STP mode of operation

43. In the “Status” dialogue on the right hand side you’ll see the current set-
tings for the Common and Internal Spanning Tree (CIST). These are the
common settings used for MSTP:

Figure 36: The “CIST” status for the MSTP protocol

44. For setting CIST parameters select the “Configuration” tab. This provides
the parameters “Priority”, “Maximum Age”, “Hello Time”, “Forward
Delay”, “Tx Hold Count”, “Max Hops”, “Region Name”, and “Revision”.

FOX61xEthernet Services 25
COMMISSIONING

Figure 37: “CIST” configuration parameters

45. In the same dialogue window, but below the CIST parameters, you cre-
ate one or several MSTP instances, “MSTI-n”, by clicking on the “Create
MSTI” button below the “MST Instances” table:

Figure 38: “Create MSTI” dialogue

46. Once a MSTI-n is created you can select it in the top selection box
above the “Status” / “Configuration” tabs:

Figure 39: Select MSTI-1 after its creation

47. Now you configure the MSTI-n instance, i.e. you set the priority and
assign or unassign VLANs:

26 FOX61xEthernet Services
 COMMISSIONING

Figure 40: MSTI-1 configuration

Figure 41: MSTI-1 VLAN assignment

48. Select “bridge-1” from the “Switching - Protocols - Spanning Tree” tree
on the left hand side of the FOXCST GUI:

Figure 42: The “bridge-1” instance in the “Switching - Protocols” tree

49. From the list of ports that support MSTP you can now enable MSTP on
any required switch port by activating the “Enabled” checkbox:

Figure 43: Sample of enabling MSTP on switch ports

50. Select a port and click on the “Status” tab for the selected port.
 This presents the current CIST settings as shown in the following
example:

FOX61xEthernet Services 27
COMMISSIONING

Figure 44: Sample of a port’s MSTP status (CIST status)

51. By selecting a MSTP instance (MSTI) instead of the common instance
(CIST) you can display the MSTI status.
52. Click on the “Configuration” tab to set the CIST parameters, and/or the
MSTI-n parameters for the selected port.
 Select the required “Priority” and “Path Cost” settings:

Figure 45: Sample of MSTP port settings for CIST (left) and MSTI-1 (right)

53. Click on the “Apply changes to NE” icon in the FOXCST main win-
dow’s icon bar.

54. If required click on the “Save to NE” icon to persistently save the
settings to the NE database.
 You have successfully set up a sample MSTP configuration for the
FOX61x application.
End of instruction for MSTP setup

28 FOX61xEthernet Services
 ANNEX

5 Annex
5.1 Associated documents

1KHW028514 FOX61x Terms and Abbreviations

1KHW002497 FOX61x Precautions and Safety
1KHW002459 FOX61x Release Notes
1KHW002460 FOX61x Product Features and Characteristics
1KHW002461 FOX615 Installation
1KHW002462 FOX612 Installation
1KHW002463 FOX61x Lightning Protection
1KHW002464 FOX61x System Description
1KHW002465 FOXCST Installation
1KHW002466 FOXCST Operation
1KHW002467 FOX61x TDM Services
1KHW002469 FOX61x CESM1
1KHW002470 FOX61x LESU1
1KHW002471 FOX61x ETOP1
1KHW002472 FOX61x ELET1
1KHW002473 FOX61x LEDE1
1KHW002474 FOX61x DATI1
1KHW002475 FOX61x EPSI1
1KHW002476 FOX61x SAMO1
1KHW002477 FOX61x SAMO2
1KHW002478 FOX61x LEDS1
1KHW002479 FOX61x LEDA1
1KHW002480 FOX61x LEXI1
1KHW002481 FOX61x LECO1
1KHW002483 FOX61x TEPI1
1KHW002484 FOX61x OPIC1
1KHW002498 FOX61x Electrical Cables

FOX61xEthernet Services 29
ANNEX

30 FOX61xEthernet Services
Contact us

ABB Switzerland Ltd

Power Systems

1KHW002468 © Copyright 2012 ABB. All rights reserved.

Bruggerstrasse 72
CH-5400 Baden
Tel. +41 58 585 77 37
Fax +41 58 585 55 77
E-mail: utility.communication@ch.abb.com

www.abb.com/utilitycommunication