Westermo MRD-350 Software

Brand: Westermo

Model: MRD-350

Type: Software

Organisation

Westermo

Prepared by Document

The WeConﬁg Team Release Notes WeConﬁg 1.18.3

Approved by Date Document No

The Program Manager August 24, 2023 186018-g20ad412

Release Notes WeConﬁg 1.18.3

Contents

1 About 2

1.1 Installation ....................................... 2

1.2 Usage .......................................... 2

2 News 4

2.1 UndockedWindows................................... 4

2.2 MSIBasedInstaller................................... 4

2.3 AutomaticUpdateOptions ............................... 4

2.4 UpdateNotiﬁcations .................................. 4

2.5 FirmwareUpgrades................................... 4

2.6 SSHClient ....................................... 5

2.7 Usability......................................... 5

2.8 xRDFunctionality ................................... 5

2.9 PortableInstallations .................................. 5

2.10DeviceImport...................................... 6

2.11 3G and 4G Cellular Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Limitations 7

4 Fixed Issues 9

Organisation

Westermo

Prepared by Document

The WeConﬁg Team Release Notes WeConﬁg 1.18.3

Approved by Date Document No

The Program Manager August 24, 2023 186018-g20ad412

1 About

WeConﬁg is a Windows based tool for conﬁguration and maintenance of Westermo switches and

routers.

For more information about Westermo and other product offerings see www.westermo.com.

1.1 Installation

The following prerequisites have to be fulﬁlled to successfully execute WeConﬁg:

• WinPcap 4.1.3 installed or, Npcap 1.6 or later

If neither WinPcap nor Npcap is installed, WeConﬁg will run in a reduced mode and not all function-

ality will be available.

WeConﬁg will offer to install WinPcap if it believes the user would beneﬁt from it.

WeConﬁg will only maintain compatibility with current and legacy versions of Microsoft Windows

that not has reached its EOL (End Of Life) date.

Note! If you are using Npcap make sure that you have acquired a valid license. Licensing details are

available at https://npcap.com/.

1.2 Usage

The following may have to be enabled on the managed switches/routers to get full functionality of

WeConﬁg:

• IPConﬁg protocol

• HTTPS (Web) must be enabled

Administrator password must be setup in the WeConﬁg Settings dialogue.

• SNMP protocol. The read community has to be set.

The same read community has to be setup in WeConﬁg Project Settings dialogue.

• LLDP protocol

• SSH CLI access

The functionality dependent on the respective item above is described below.

• Information gathering from the device, including topology information to be able to draw a

device map is performed using SNMP.

Organisation

Westermo

Prepared by Document

The WeConﬁg Team Release Notes WeConﬁg 1.18.3

Approved by Date Document No

The Program Manager August 24, 2023 186018-g20ad412

• Basic Setup uses the IPConﬁg protocol to setup devices on devices running WeOS 4.32 and

older. On such devices, the IPConﬁg protocol must be enabled on the devices to use Basic

Setup.

• Backup, restore and ﬁrmware upgrade all use the HTTPS interface.

• Upgrade with HTTPS-upload method uses the HTTPS interface.

• To use SSH access an external SSH client must be set up in the Settings dialogue.

• All conﬁguration of WeOS devices depends on the use of SSH; hence, SSH must be enabled on

the target devices.

Organisation

Westermo

Prepared by Document

The WeConﬁg Team Release Notes WeConﬁg 1.18.3

Approved by Date Document No

The Program Manager August 24, 2023 186018-g20ad412

2 News

WeConﬁg 1.18 introduces the following new functions and improvements:

2.1 Undocked Windows

Undocked windows may now be put into the “always on top” mode, meaning that it will obscure the

main window. The setting is in the system menu of the undocked window (click the top right icon of

the window). The setting is remembered per window, and is persisted between restarts of WeConﬁg.

The default behavior of undocked windows is to not obscure the main window.

2.2 MSI Based Installer

In strict IT environments, where automatic updates of software are prohibited, WeConﬁg may now

also be installed using MSI. It is recommended to only use the MSI installer if required. MSI based

installations will never automatically update itself, but it will check for new versions on startup. If a

new version is found, the user is provided a link to download the new MSI ﬁle.

2.3 Automatic Update Options

The automatic update option Never has been removed. It was added for IT environments for where

automatic updates are prohibited. In such strict environments, the MSI based installer should be used.

Previous selected setting will be revered to On Approval, meaning that WeConﬁg will notify when an

update is available, and the user is given a choice to install or skip that update.

2.4 Update Notiﬁcations

When new versions of WeConﬁg are available, or have been automatically installed, we now provide

a direct link to the release notes for the new version. Clicking on it will open the link using the default

web browser.

2.5 Firmware Upgrades

Two warnings have been added:

• When the user wants to perform ﬁrmware upgrade on multiple devices in full parallel, a warning

is shown to the user, requiring the user to conﬁrm.

• When the user wants to perform a regular (smart) upgrade on multiple devices, and the path from

the PC to the network is not known, the user is warned that the upgrade will be downgraded to

a sequential upgrade.

Organisation

Westermo

Prepared by Document

The WeConﬁg Team Release Notes WeConﬁg 1.18.3

Approved by Date Document No

The Program Manager August 24, 2023 186018-g20ad412

For WeOS 4 devices, WeConﬁg will default to take as few steps as possible to upgrade it to a target

version. This behavior can be turned off, to make WeConﬁg strictly adhere to best practices, and

always upgrade by stepping through all minor versions between the current and target version.

For WeOS 5 devices, WeConﬁg will default to best practices, and always upgrade by stepping through

all minor versions between the current and target version. This behavior can be turned off, but it is not

recommended. Use at your own risk.

2.6 SSH Client

PuTTY has until now been distributed together with WeConﬁg. From now on, WeConﬁg will rely on

the built in OpenSSH Client in Windows. It can be enabled under “Optional features” in Windows.

Custom clients may still be used.

2.7 Usability

New usability improvements around device conﬁguration ﬁles:

• When importing and exporting device conﬁguration ﬁles, WeConﬁg will remember the direc-

tory imported from or exported to. The next time a device conﬁguration ﬁle is imported, or

exported, the ﬁle dialogs will start in the last used directory.

• WeConﬁg will now suggest more descriptive ﬁle names when exporting device conﬁguration

ﬁles.

It is now possible to right click multiple devices and open multiple device web pages and SSH sessions

in one click.

2.8 xRD Functionality

It is now possible to perform the following actions on xRD devices:

• Reboot

• Factory reset

• Download tech support ﬁle

2.9 Portable Installations

To avoid data corruption, WeConﬁg no longer allow to be started from a shared network drive in

portable installations. To ensure that WeConﬁg functions properly in portable installations, make sure

to copy the installation to a private folder that is not accessed concurrently by other users.

Organisation

Westermo

Prepared by Document

The WeConﬁg Team Release Notes WeConﬁg 1.18.3

Approved by Date Document No

The Program Manager August 24, 2023 186018-g20ad412

2.10 Device Import

When importing devices from CSV ﬁles, imported devices will no longer obscure existing devices in

the topology.

2.11 3G and 4G Cellular Diagnostics

It is now possible to monitor RSRP, RSRQ(4G) and RSSI (3G & 4G) on the Ibex product family.

Organisation

Westermo

Prepared by Document

The WeConﬁg Team Release Notes WeConﬁg 1.18.3

Approved by Date Document No

The Program Manager August 24, 2023 186018-g20ad412

3 Limitations

• Upgrade using HTTPS-upload is supported from WeOS 4.13 and later.

To upgrade an older WeOS version, TFTP/FTP method must be used. A TFTP or a FTP server

must be running on the WeConﬁg PC. The path to the TFTP/FTP root folder is setup in the

Settings dialogue.

• Hostname and location is limited to 10 and 11 characters for factory reset/default WeOS 4

devices, due to limitations of the IPConﬁg protocol.

• Conﬂicting IP addresses can only be identiﬁed on WeOS units, and only for the IP address

retrieved using the IPConﬁg protocol.

• WeConﬁg does not identify if an IP Address is statically conﬁgured or retrieved from a DHCP

server. When setting an IP address using WeConﬁg, it is applied as a static address.

• Non WeOS units have limited support in WeConﬁg.

• Limited WeConﬁg SNMP trap support will be available when MS Windows SNMP Trap Host

server is activated. For WeConﬁg to provide as much SNMP trap support as possible, please

disable the MS Windows Trap Host server.

• If alarm monitoring for SNR high/low is to function properly, the device’s ﬁrmware version

must be 4.18.0 or higher due to a limitation in earlier ﬁrmwares.

• Some NICs (mostly low end USB NICs) discard LLDP frames. This means that WeConﬁg

cannot learn where it is connected in the network.

• VLAN conﬁguration is not supported on WeOS 4.13.4 or previous versions.

• WeConﬁg might not show SNMP traps sent from routers.

• Device connections might not be displayed correctly until 30 seconds after a link up/down event.

• Conﬁguration of passwords and password to access MRD devices must only contain character

(a-z, A-Z and 0-9), otherwise access to device may not work.

• WeConﬁg is not able to conﬁgure Vipers with TTDP enabled on versions of WeOS prior to

5.14.

• WeConﬁg cannot detect powerline devices (DDW-002).

• The ping and traceroute tools cannot be executed reliably from Falcon devices due to a model

speciﬁc limitation.

• The functionality of WeConﬁg in portable mode is limited.

• Optimization of ﬁrmware packages will not be done for WeOS 5.13.0 or higher.

Organisation

Westermo

Prepared by Document

The WeConﬁg Team Release Notes WeConﬁg 1.18.3

Approved by Date Document No

The Program Manager August 24, 2023 186018-g20ad412

• When importing devices from CSV ﬁles, model name and ﬁrmware version is required in order

for a device to be properly identiﬁed. Unidentiﬁed devices are treated as “unknown devices”.

• WeConﬁg is not able to identify connections between xRD devices.

• Connections between MRD and BRD devices cannot be derived due to a ﬁrmware limitation.

• WeConﬁg cannot be started from a shared network drive in portable mode.

Organisation

Westermo

Prepared by Document

The WeConﬁg Team Release Notes WeConﬁg 1.18.3

Approved by Date Document No

The Program Manager August 24, 2023 186018-g20ad412

4 Fixed Issues

Issue Version Category Description

#0019055 1.18.0 GUI Critical VLANs are not blocked from deletion in WeConﬁg

#0019125 1.18.0 SYSTEM Double-click on project ﬁle does not open project in WeConﬁg

#0019133 1.18.0 GUI Function lost for stepwise ﬁrmware upgrades.

#0019157 1.18.0 SYSTEM Hardening/routing does not work at all for WeOS 5

#0019159 1.18.0 SYSTEM Wrongfully conﬁgured SSL port makes CLI interpreter fail on

aborted contexts.

#0019189 1.18.0 GUI Syslog tab is empty after releasing the window and closing

#0019211 1.18.0 SYSTEM Device icon are not displayed in an air gapped environment

#0019285 1.18.1 GUI Adding xRD devices manually crashes when typing in a version

number

#0019286 1.18.1 SYSTEM CSV imported devices have blank passwords

#0019290 1.18.2 SYSTEM Ibex: http password parameter changed

#0019294 1.18.2 SYSTEM Opening projects from WeConﬁg < 1.18 with “unknown de-

vices” is not possible

#0019300 1.18.2 SYSTEM Network Baseline report fails for WeOS devices - ports cannot

be shown on the report

#0019345 1.18.3 GUI When discovering factory default xRD devices, WeConﬁg

shows the wrong UI for conﬁguration

#0019364 1.18.3 SYSTEM Ping summary on 5.16 makes pingtool fail parsing

Westermo MRD-350 Software

Westermo MRD-350 Software

Related papers