BSC NWI-E Configuration

1 General Information

1.1 Introduction

The purpose of this document is to provide information and tools to set up a supported configuration of the BSC NWI-E 450A. More information on Operation and Management of the BSC NWI-E can be found in Reference [6] and Reference [7].

This User Guide does not document the hardware aspects of BSC NWI-E installation. See Reference [3] for more information.

The pair of layer 3 (IP) switches that constitutes the BSC IP network interface are stand-alone and self-contained with regard to both the Central Processor (CP) and Regional Processor (RP). All IP traffic to and from BSC goes through the NWI-Es.

The Plant Engineering Description (PED) BSC IP Infrastructure, 5/194 01-APT 210 09 describes how to connect the BSC NWI-E to a BSC.

The BSC NWI-Es are working in an active-active setup, so there will be network traffic in the A-side and B-side path simultaneously.

1.2 Prerequisites

This revision of the User Guide assumes the following:

ExtremeXOS 12.3.1.2 or later release approved by Ericsson. A Personal Computer (PC) workstation connected to the BSC NWI-E, see Section 2.2. A network plan. See Reference [1] for more information: Clearance to use the Intercon, IPS subnet as local, non-routed networks; otherwise

other, installation-specific, subnets must be chosen.

1.3 Revision Information

1.4 Typographical Conventions

The commands that are entered in the Command Line Interface (CLI) are formatted as

command text some command lines are too long to fit the format of this \ document, they are written on multiple lines with a \ backslash character as a continuation character.

Please note that the line continuation character is not entered, instead, the command is entered as a single line to the CLI. System response is in

bold.

2 Switch Management

2.1 General

The BSC NWI-E are managed either through a CLI or from OSS. The CLI is accessible both locally through the serial management port or the local Ethernet management port (DensiShield connector) and remotely using Telnet and SSH version 2 when available.

Remote access is not possible until the switch has been configured with an IP address by using the local management port.

If the local serial management port is used, the requirement for access is either that a terminal server (with an available port) is installed at the site or that on-site personnel with a terminal (laptop) is available.

2.2 Configuring a New Switch

A suitable setup for configuration of a new switch would be a laptop or workstation with

A serial port and terminal emulation software A null-modem cable (TSR 491 616/0 or equivalent) between the serial port on the PC

and the serial management port of the switch Text editor to produce the parameter files for each switch. Python interpreter, version 2.6 The script BSC_NWI-E_configuration.py The parameter file template parameter_file_template.txt

Use these serial port settings:

Baud rate: 9600 Data bits: 8 Stop bit: 1 Parity: None Flow Control: xon/xoff

Use the terminal emulation software to log on to the switch (“admin” with blank password).

Make sure that the software version in the switch is correct. If necessary, install the correct version from OSS after the setup has been completed.

Download the configuration file generated by the script in Section 5.3 from the PC workstation by pasting the configuration into the terminal window.

The switch has to be rebooted to make the new configuration effective.

More information on installation of the BSC NWI-E can be found in Reference [3].

2.3 Login to a Configured BSC NWI-E Switch

Use SSH or telnet to log in to a configured switch. Use the IP address of VLAN SR_OM (see Section 3.4) as the host address:

ssh <admin-id>@<SR_OM-address>

<admin-id> can be “admin” or some other ID with administrative privileges that has been created in the switch. The SSH client will ask for a password to use.

2.4 Backup and Restore of the Configuration

The configuration in the switch should be saved to a suitable storage by the command

upload configuration <TFTP server IP address> \ <file name> vr VR-Default

or the equivalent scp2 command

scp2 vr VR-Default configuration \ <user>@<ipaddress>:<remote_file>

3 Switch Configuration

3.1 General

This chapter describes the supported configurations in the BSC NWI-E. You must be logged in with administrative privileges to do configuration changes.

Caution!

“Broadcast storms” may occur if an unconfigured or severely misconfigured switch is connected or if a connected switch is de-configured. Such storms of Ethernet packets can cause connected hosts to become overloaded and reboot, and they can also affect other nodes connected to the same site switch.

This means that the switch must be configured as described in Section 2.2 before it is connected to the rest of the BSC.

Once there is a working configuration for a switch, save it to a backup area as described in Section 2.4 or use the built-in functionality in OSS to save backups.

3.2 Supported Configurations

The BSC NWI-E supports 4 different types of external network configurations.

Note: There can only be one type of external network configuration per BSC. It is not allowed to have one type for VLAN SR_OM and another for VLAN SR_Abis even if they are port separated.

3.2.1 Type 1 - BSC LAN Switch Standard External Network Configuration

This external network type is the legacy external network configuration type also supported by BSC LAN Switch.

Figure 1 External network configuration of the type that the BSC LAN Switch and OSS support

3.2.2 Type 2 - No Pre-emptive VRRP

This is a variation of external network type 1.

The static routing is the same as for the external network type described in Section 3.2.1. What differs is that the VRRP for each external network is using a third IP address where side A BSC NWI-E is the master and side B BSC NWI-E is the backup. Pre-emption is turned off for the VRRP, thus reducing the

network impacts to one fail-over. Note that the VRRP master has priority 200 and the VRRP backup has priority 100.

Figure 2 External network configuration 2, a variation of the type supported by OSS for BSC LAN Switch, but without a pre-emptive VRRP

3.2.3 Type 3 - External L2 Over Crosslink

There is only one static route per external host subnet (for example. OSS, SGSN) that points to the VRRP address for the Site Routers. All external VLANs must now also include port group Crosslink to make a L2 connection between the two BSC NWI-Es. There is no need for configuring VLAN Intercon or its associated subnet.

The VRRP for each external network is using a third IP address where side A BSC NWI-E is the master and side B BSC NWI-E is the backup. Pre-emption is turned off for the VRRP, thus reducing the network impacts to one fail-over. Note that the VRRP master has priority 200 and the VRRP backup has priority 100

Figure 3 External network configuration 3, L2 over crosslink

3.2.4 Type 4 - No L2 Between Site Routers

The primary static route per external host subnet (e.g. OSS, SGSN) points to the corresponding Site Router. The secondary static route points to IP address of the other BSC NWI-E on subnet Intercon. The difference in routing compared to the external network type in chapter 5.1.6.1, is that the two sides have different primary static routes. Note that the suffixes “_a” and “_b” are added to the external VLANs depending on which BSC NWI-E they reside on. This is to avoid a name conflict when doing a IP consistency check since the two VLANs will have two different subnets and associated subnet masks.

Figure 4 External network configuration 4, No L2 between site routers

3.3 Set the Correct Time and Date

The use of NTP to keep the correct date and time is recommended. To enable NTP synchronization enter the correct IP addresses to the SNTP_x parameters in the parameter file before generating configuration files for the BSC NWI-E.

The UTC time zone is used by default in NWI-E; date and time is entered in the format indicated between “<>”

config time <mm/dd/yyyy hh:mm:ss>

The “config time” command must be entered manually, as it is not part of the configuration generated by the script in Section 5.3. A better alternative is to obtain correct time by entering the SNTP settings in the parameter file for the python script.

3.4 Create and Configure the Subnets

3.4.1 General

The PED BSC IP Infrastructure shows all supported ways to connect a BSC to NWI-E.

The simplified diagram of the BSC NWI-E in Figure 5 shows some of the IP hosts that will connect to/through the NWI-E.

Figure 5 Simplified Diagram of the BSC NWI-E

It should be noted that the BSC NWI-Es as such do not pose any restrictions on the order of connecting/disconnecting APG4x, STOC and GPH.

The following VLANs are created in the BSC NWI-Es as shown in Figure 6:

SR_Gb for connection of Gb over IP traffic to site LAN (optional) SR_OM for connection to the O&M site LAN (mandatory) SR_Abis for connection of Abis over IP traffic to BTSs (optional) SR_SS7 for the Sigtran traffic to the site LAN (optional).

SR_A_userplane for the A over IP traffic to site LAN (optional). Only valid from BSC 09A

BSC_Inner for connection of internal hosts to the NWI-E Intercon for the interconnection of the two BSC NWI-Es LH_A and LH_B for the OSE Ethernet internal communication

Figure 6 Logical View of the VLANs in the Two Switches

Brief description of the VLANs:

The SR_Gb VLAN carries the incoming and outgoing traffic to the SGSNs.

The SR_OM VLAN carries the traffic to and from the O&M LAN on the site.

The SR_Abis VLAN carries the outgoing traffic to the BTS nodes. The SR_SS7 carries the SS7 traffic to and from the signalling hosts.

The SR_A_userplane carries the traffic to and from the MGW hosts.

The Intercon VLAN enables VRRP to function as the fail-over mechanism. The two IP addresses used (one in each switch) are completely internal and not visible to outside hosts.

The LH_A and LH_B VLANs carries the OSE Ethernet communication. The traffic on the VLAN in the A-side switch is kept separate from the traffic in the B-side switch. The VLANs does not carry any IP traffic.

The BSC_inner VLAN carries the O&M traffic for applications such as R-PMO (GPH), ROMT/IP (STOC) and the APG4x.

If VLAN tagging is to be used for a north bound VLANs, that is VLANs on port group Payload, then all north bound VLANs must use VLAN tagging. It is not possible to mix VLAN tagging and no VLAN tagging on port group External.

All South Bound VLANs except LH_A and LH_B extend over both switches by including the Crosslink port group and by using VLAN tagging.

In the configuration commands in this document, an example subnet structure is used. The subnets and IP addresses are listed in Table 1

Table 1 Subnet Structure Example

Subnet name IP subnet A-Side switch IP B-Side switch IP

address address SR_Gb 10.40.16.0/29 10.40.16.3 10.40.16.4 SR_OM 10.40.32.0/29 10.40.32.5 10.40.32.6 SR_Abis 10.40.48.0/29 10.40.48.8 10.40.48.9 SR_SS7 10.40.52.0/29 10.40.52.3 10.40.52.4 SR_A_userplane 10.40.53.0/29 10.40.53.3 10.40.53.4 Internal_Intercon 192.168.2.0/30 192.168.2.1 192.168.2.2 Internal_IPS 192.168.0.0/23 192.168.0.1 192.168.1.1 Internal_OM 172.30.38.0/28 172.30.38.1 172.30.38.2 Internal_Gb 172.30.12.0/25 172.30.12.1 172.30.12.2 Internal_Abis 172.30.74.0/26 172.30.74.1 172.30.74.2 Internal_SS7 172.30.78.0/28 172.30.78.1 172.30.78.2 Internal_A 172.30.79.0/28 172.30.78.1 172.30.78.2

Figure 7 Front Panel of the BSC NWI-E switch

Table 2 shows the member ports of each port group. Table 3 shows the member port groups of each VLAN.

To connect cables on ports 12 and 13, an SPF module must be used.

Table 2 Port Group Member Ports

Port Group Member Ports Internal 1-8 Crosslink 9, 10 External 11-13 Note:

Ports 9 and 10 in port group Crosslink are link aggregated. Table 3 VLAN Member Port Groups

VLAN Name Member Port Gro SR_Gb, SR_Abis, SR_SS7, SR_OM, SR_A_userplane External (and Cros Intercon CrossLink LH_A, LH_B Internal BSC_Inner Internal and Cross

3.4.2 Port Separation and VLAN Tagging for External VLANs

Each external VLAN is configured to use one, and only one, of the three external ports included in the port group External.

If any external VLAN is the sole user of a port, then it's optional to have tagging on that VLAN. Should several external VLANs share a port then it is mandatory that the VLANs are tagged.

3.4.3 Routing

Only static routes are supported. No spanning tree protocol or RIP is supported in the BSC NWI-E configuration, even if the BSC NWI-E can handle the protocols. Which static routes to set up are connected to how the external network is configured.

The static routes are for all the external host subnets where the corresponding application hosts exist

OSS for VLAN SR_OM

SGSN for VLAN SR_Gb

STN for VLAN SR_Abis

MSC for VLAN SR_SS7

MGW for VLAN SR_A_userplane

4 Additional Configuration

This chapter describes some other recommended settings. These additional settings are not taken care of by the Python script in Section 5.1, they have to be manually configured.

4.1 Add Access Profiles

Access profiles helps to improve security by limiting access to various features in the switch. admin is for both login restriction and SNMP access (not included in the Python script). For local access, the Internal_OM subnet is also added. This enables on-site personnel to attach a laptop to a free internal port to manage the switches.

create access-profile admin type ipaddress configure access-profile admin add ipaddress \ OSS_1/n configure access-profile admin add ipaddress \ OSS_2/n configure access-profile admin add ipaddress \ Internal_OM_subnet/n

5 Python Script to Generate Configuration Files

5.1 General

The Python script Reference [2] used for configuration of the BSC NWI-E has everything needed for layer 2 and 3 connectivity and also ACL settings..

The configuration generated by the script should be transferred to the switch as described in Section 2.2.

5.2 Parameter File

The format of the parameter file Reference [5] is shown in the following example. The following variations are possible:

The number of OSS subnets can be from one and upwards.

The number of SGSN subnets can be from zero and upwards.

The number of STN subnets can be from zero and upwards. The number of SIG subnets can be from zero and upwards.

The number of MGW subnets can be from zero and upwards.

The subnet sizes can be adjusted to the needs of the actual installation.

For more information on the subnet sizes, see Reference [1].

Parameter usage:

ACLs

<yes, no>

Set to yes if the output configuration files shall contain the A the BSC NWI-E. Set to no, no ACLs will be generated.

Mandatory.

Sysname_side_A

<string>

This string will identify the side A BSC NWI-E. It can be retri SNMP and it is used as a prompt in the CLI

Mandatory.

Sysname_side_B

<string>

This string will identify the side A BSC NWI-E. It can be retri SNMP and it is used as a prompt in the CLI

Mandatory.

SSH

<yes, no>

If SSH should be configured or not. If it is configured then te disabled

Mandatory.

External_net_type

<1, 2, 3, 4>

External network type. See Section 3.2

Mandatory.

Internal_Intercon <IP, side A>/<IP, side B>/<netmask>

IP addresses for side A and side B BSC NWI-E and the assoc netmask.

Ignored when External_net_type is set to 3; otherwise mand

Internal_Intercon_tag

<VLAN tag>

VLAN tag id for VLAN Intercon.

Ignored when External_net_type is set to 3; otherwise mand

Internal_tag

<VLAN tag>

VLAN tag id for VLAN BSC_Inner

Mandatory.

Internal_IPS

<IP, side A>/<IP, side B>/<netmask>

IP addresses for side A and side B BSC NWI-E and the assoc netmask

Mandatory.

Internal_OM

<IP, side A>/<IP, side B>/<netmask>

IP addresses for side A and side B BSC NWI-E and the assoc netmask

Mandatory.

Internal_OM_vrrp

<VRRP IP address, or empty>

Controls whether a VRRP is set up in the Internal_OM subne This is the IP address the APG40/43 will have as a single gat

Optional.

Internal_Abis

<IP, side A>/<IP, side B>/<netmask>

IP addresses for side A and side B BSC NWI-E and the assoc netmask.

Mandatory if Abis over IP is used.

Internal_Gb

<IP, side A>/<IP, side B>/<netmask>

IP addresses for side A and side B BSC NWI-E and the assoc netmask.

Mandatory if Gb over IP is used.

Internal_A

<IP, side A>/<IP, side B>/<netmask>

IP addresses for side A and side B BSC NWI-E and the assoc netmask.

Mandatory if A over IP (user plane) is used.

Internal_SS7

<IP, side A>/<IP, side B>/<netmask>

IP addresses for side A and side B BSC NWI-E and the assoc netmask.

Mandatory if SIGTRAN is used.

SR_Gb_subnet

<IP, side A>/<IP, side B>/<netmask>

IP addresses for side A and side B BSC NWI-E and the assoc netmask.

Mandatory if Gb over IP is used.

SR_Gb_port

<11, 12, 13>

Mandatory if Gb over IP is used.

SR_Gb_tag

<VLAN tag>/<untagged, or nothing>

The VLAN tag for VLAN SR_Gb. Mandatory if Gb over IP is us “untagged” means that the VLAN is to be untagged external another VLAN uses the same port then the VLAN is always ta

Mandatory if Gb over IP is used.

SR_Gb_gw

<IP for Gb GW>/<IP for Gb GW side b, or empty>

The first IP address is for the gateway to be used for Gb ove If the external network type is set to 1, 2 or 3, this means th Router VRRP address. If the external network type is set to 4 address is the IP address of Site Router side A; and the seco address is to Site Router side B.

First address is mandatory when Gb over IP is used. Second mandatory for external network type 4, and is ignored for th external network types.

SR_Gb_vrrp

<VRRP address>

This defines the VRRP address for VLAN SR_Gb.

Mandatory for external network type 2 when using Gb over I ignored for the other external network types.

SR_Gb_vrid <VRID>/<VRID. or empty>

When using external network type 1 the first VRID is for the instance that has the IP address that side A BSC NWI-E own second VRID is for the VRRP instance that has the IP addres B BSC NWI-E owns. Both are mandatory for external networ When using external network type 2 the first VRID defines th used for the VRRP instance; and the second VRID is ignored parameter is mandatory for external network type 2. This pa ignored for the other external network types.

SR_Gb_sgsn_<x>

<IP subnet>/<netmask>

Defines an SGSN subnet. the <x> in the parameter is a num between 1 and 20 and is incremented when there are severa subnets.

At least one subnet must be defined when using Gb over IP.

SR_OM_subnet

<IP, side A>/<IP, side B>/<netmask>

IP addresses for side A and side B BSC NWI-E and the assoc netmask.

Mandatory

SR_OM_port

<11, 12, 13>

Mandatory

SR_OM_tag

<VLAN tag>/<untagged, or nothing>

The VLAN tag for VLAN SR_OM. “Untagged” means that the be untagged externally; if another VLAN uses the same port VLAN is always tagged.

Mandatory if Gb over IP is used.

SR_OM_gw

<IP for OM GW>/<IP for OM GW side b, or empty>

The first IP address is for the gateway to be used for O&M tr the external network type is set to 1, 2 or 3, this means the Router VRRP address. If the external network type is set to 4 address is the IP address of Site Router side A; and the seco address is to Site Router side B.

First address is mandatory. Second address is mandatory fo network type 4, and is ignored for the other external networ

SR_OM_vrrp

<VRRP address>

This defines the VRRP address for VLAN SR_OM.

Mandatory for external network type 2; and ignored for the

external network types.

SR_OM_vrid

<VRID>/<VRID. or empty>

When using external network type 1 the first VRID is for the instance that has the IP address that side A BSC NWI-E own second VRID is for the VRRP instance that has the IP addres B BSC NWI-E owns. Both are mandatory for external networ When using external network type 2 the first VRID defines th used for the VRRP instance; and the second VRID is ignored parameter is mandatory for external network type 2. This pa ignored for the other external network types.

SR_OM_oss_<x>

<IP subnet>/<netmask>

Defines an OSS subnet. The <x> in the parameter is a num between 1 and 20 and is incremented when there are severa subnets. At least one subnet must be defined.

SR_Abis_subnet

<IP, side A>/<IP, side B>/<netmask>

IP addresses for side A and side B BSC NWI-E and the assoc netmask.

Mandatory if Abis over IP is used.

SR_Abis_port

<11, 12, 13>

Mandatory if Abis over IP is used.

SR_Abis_tag

<VLAN tag>/<untagged, or nothing>

The VLAN tag for VLAN SR_Abis. Mandatory if Abis over IP is “untagged” means that the VLAN is to be untagged external another VLAN uses the same port then the VLAN is always ta

Mandatory if Abis over IP is used.

SR_Abis_gw

<IP for Abis GW>/<IP for Abis GW side b, or empty>

The first IP address is for the gateway to be used for Abis ov traffic. If the external network type is set to 1, 2 or 3, this m Site Router VRRP address. If the external network type is se first address is the IP address of Site Router side A; and the address is to Site Router side B.

First address is mandatory when Abis over IP is used. Secon is mandatory for external network type 4, and is ignored for external network types.

SR_Abis_vrrp

<VRRP address>

This defines the VRRP address for VLAN SR_Abis.

Mandatory for external network type 2 when using Abis over ignored for the other external network types.

SR_Abis_vrid

<VRID>/<VRID. or empty>

When using external network type 1 the first VRID is for the instance that has the IP address that side A BSC NWI-E own second VRID is for the VRRP instance that has the IP addres B BSC NWI-E owns. Both are mandatory for external networ When using external network type 2 the first VRID defines th used for the VRRP instance; and the second VRID is ignored parameter is mandatory for external network type 2. This pa ignored for the other external network types.

SR_Abis_stn_<x>

<IP subnet>/<netmask>

Defines an STN subnet. The <x> in the parameter is a numb between 1 and 20 and is incremented when there are severa subnets. At least one subnet must be defined when using Ab

SR_OEN_subnet

<IP, side A>/<IP, side B>/<netmask>

IP addresses for side A and side B BSC NWI-E and the assoc netmask.

Mandatory if a separate net for Open Event Notification is us

SR_OEN_port

<11, 12, 13>

Mandatory if OEN is used.

SR_OEN_tag

<VLAN tag>/<untagged, or nothing>

The VLAN tag for VLAN SR_OEN. Mandatory if OEN is used. “ means that the VLAN is to be untagged externally; if anothe uses the same port then the VLAN is always tagged.

Mandatory if OEN is used.

SR_OEN_gw

<IP for OEN GW>/<IP for OEN GW side b, or empty>

The first IP address is for the gateway to be used for OEN tr external network type is set to 1, 2 or 3, this means the Site VRRP address. If the external network type is set to 4 the fir is the IP address of Site Router side A; and the second addre Site Router side B.

First address is mandatory when OEN is used. Second addre mandatory for external network type 4, and is ignored for th external network types.

SR_OEN_vrrp <VRRP address>

This defines the VRRP address for VLAN SR_OEN.

Mandatory for external network type 2 when using OEN; and for the other external network types.

SR_OEN_vrid

<VRID>/<VRID. or empty>

When using external network type 1 the first VRID is for the instance that has the IP address that side A BSC NWI-E own second VRID is for the VRRP instance that has the IP addres B BSC NWI-E owns. Both are mandatory for external networ When using external network type 2 the first VRID defines th used for the VRRP instance; and the second VRID is ignored parameter is mandatory for external network type 2. This pa ignored for the other external network types.

SR_OEN_coll_<x>

<IP subnet>/<netmask>

Defines a collector subnet. The <x> in the parameter is a nu between 1 and 20 and is incremented when there are severa subnets.

It is optional to define this parameter when using Open Even Notification since some customers prefer to have the collecto OSS subnet instead.

SR_SS7_subnet

<IP, side A>/<IP, side B>/<netmask>

IP addresses for side A and side B BSC NWI-E and the assoc netmask.

Mandatory if SIGTRAN is used.

SR_SS7_port

<11, 12, 13>

Mandatory if SIGTRAN is used.

SR_SS7_tag

<VLAN tag>/<untagged, or nothing>

The VLAN tag for VLAN SR_SS7. “Untagged” means that the be untagged externally; if another VLAN uses the same port VLAN is always tagged.

Mandatory if SIGTRAN is used.

SR_SS7_gw

<IP for SS7 GW>/<IP for SS7 GW side b, or empty>

The first IP address is for the gateway to be used for SIGTRA If the external network type is set to 1, 2 or 3, this means th Router VRRP address. If the external network type is set to 4 address is the IP address of Site Router side A; and the seco

address is to Site Router side B.

First address is mandatory when SIGTRAN is used. Second a mandatory for external network type 4, and is ignored for th external network types.

SR_SS7_vrrp

<VRRP address>

This defines the VRRP address for VLAN SR_SS7.

Mandatory for external network type 2 when using SIGTRAN ignored for the other external network types.

SR_SS7_vrid

<VRID>/<VRID. or empty>

When using external network type 1 the first VRID is for the instance that has the IP address that side A BSC NWI-E own second VRID is for the VRRP instance that has the IP addres B BSC NWI-E owns. Both are mandatory for external networ When using external network type 2 the first VRID defines th used for the VRRP instance; and the second VRID is ignored parameter is mandatory for external network type 2. This pa ignored for the other external network types.

SR_SS7_msc_<x>

<IP subnet>/<netmask>

Defines an MSC subnet. The <x> in the parameter is a num between 1 and 20 and is incremented when there are severa subnets.

At least one subnet must be defined when using SIGTRAN. SR_A_userplane_subnet

<IP, side A>/<IP, side B>/<netmask>

IP addresses for side A and side B BSC NWI-E and the assoc netmask.

Mandatory if A over IP is used. SR_A_userplane_port

<11, 12, 13>

Mandatory if A over IP is used. SR_A_userplane_tag

<VLAN tag>/<untagged, or nothing>

The VLAN tag for VLAN SR_A_userplane. “Untagged” means VLAN is to be untagged externally; if another VLAN uses the then the VLAN is always tagged.

Mandatory if A over IP is used. SR_A_userplane_gw

<IP for A GW>/<IP for A GW side b, or empty>

The first IP address is for the gateway to be used for A over

If the external network type is set to 1, 2 or 3, this means th Router VRRP address. If the external network type is set to 4 address is the IP address of Site Router side A; and the seco address is to Site Router side B.

First address is mandatory when A over IP is used. Second a mandatory for external network type 4, and is ignored for th external network types.

SR_A_userplane_vrrp

<VRRP address>

This defines the VRRP address for VLAN SR_A_userplane.

Mandatory for external network type 2 when using A over IP ignored for the other external network types.

SR_A_userplane_vrid

<VRID>/<VRID. or empty>

When using external network type 1 the first VRID is for the instance that has the IP address that side A BSC NWI-E own second VRID is for the VRRP instance that has the IP addres B BSC NWI-E owns. Both are mandatory for external networ When using external network type 2 the first VRID defines th used for the VRRP instance; and the second VRID is ignored parameter is mandatory for external network type 2. This pa ignored for the other external network types.

SR_A_userplane_mgw_<x>

<IP subnet>/<netmask>

Defines an MGW subnet. The <x> in the parameter is a num between 1 and 20 and is incremented when there are severa subnets.

At least one subnet must be defined when using A over IP.

SNTP_<x>

<IP address>

Defines a Network Time Protocol (NTP) server where the BS can sync its time. Vital for having the correct time and date files. This parameter is optional. A maximum of two NTP ser be defined.

5.3 Generating Configuration

The Python script Reference [2] will generate the required command sequence for a supported configuration. The script gets the site-specific parameters from a text file. The file name for the parameter file is given as a command line parameter to the script. Output is two files named <sysname side A>_<date>.cfg and <sysname side B>_<date>.cfg respectively.

Script usage examples (assuming that the script is named 'NWI-E_base_config.py', generating a dual switch configuration):

C:\wrk> NWI-E_base_config.py BSC123.conf

The .conf file is the parameter file and the .cfg files are the resulting switch configuration files.

6 Concepts

Load-sharing

In this document, load-sharing refers to a technique where two cables share the traffic for a connection. Both sides of the conn must be configured to do load-sharing, so the site LAN switch configured for load-sharing if more than one cable is attached.

Also known as trunking and link aggregation.

North Bound

A North Bound VLAN is a VLAN that has traffic to and from a p BSC NWI-E switch facing the external network. In this docume the name begins with SR_ are North Bound VLANs.

Port Group A way of showing the intended use of a range of ports. In the this document it does not mean Link Aggregation Group (LAG)

South Bound

A South Bound VLAN is a VLAN that has traffic to and from a p BSC NWI-E switch facing the BSC internal network. In this doc VLANs not beginning with SR_ in their name are South Bound

STN In this version of document, STN is used as termination unit fo IP.

Syslog Syslog has its origin in the Unix world. It is a (loosely) standar of transferring log messages over an IP network.

VLAN Tagging

VLAN tagging is a way of extending a VLAN over more than on Ethernet switch. Ethernet packets with different tag values can transported over the same connection and still be kept to diffe VLANs. The tag values are in an extension of the Ethernet pack

Glossary

ACL Access Control List APG Adjunct Processor Group BOOTP Bootstrap Protocol BSC Base Station Controller

CLI Command Line Interface CP Central Processor CSU Circuit Switched Network DHCP Dynamic Host Configuration Protocol DoS Denial of Service EXB Extension Switch Board GPH GPRS Packet Handler GPRS General Packet Radio Service ICMP Internet Control Message Protocol IP Internet Protocol LAN Local Area Network MAC Media Access Controller MGW Media Gateway MXB Main Switch Board NWI-E Network Interface-Ethernet OSE Operating System Enea, the RP Operating System PC Personal Computer PGW Packet Gateway PGWB Packet Gateway Board PSU Packet Switched Userplane RBS Radio Base Station RP Regional Processor RPP

Regional Processor with PCI Interface SGSN Serving GPRS Support Node SNMP Simple Network Management Protocol SNTP Simple Network Time Protocol SR Site Router SSH Secure Shell STN Site Transport Node for RBS STOC System Terminal for Open Communication STP Spanning Tree Protocol TCP Transmission Control Protocol TRH Transceiver Handler UDP User Datagram Protocol VLAN Virtual LAN VRRP Virtual Router Redundancy Protocol

Reference List

Ericsson Documents [1] BSC IP Addressing. [2] BSC NWI-E Configuration File Compiler. [3] BSC, NWI-E, Install, OPERATIONAL INSTRUCTION. [4] BSC, NWI-E Software, Install, OPERATIONAL INSTRUCTION. [5] Parameter File Template. Other Documents [6] ExtremeXOS Command Reference Guide 12.3. USER GUIDE. [7] ExtremeXOS Concepts Guide 12.3. USER GUIDE.