Organisation
Westermo Network Technologies AB

Installation

The following prerequisites have to be fulfilled to successfully execute WeConfig:

• WinPcap 4.1.3 installed or,
• Npcap 1.6 or later

If neither WinPcap nor Npcap is installed, WeConfig will run in a reduced mode and not all functionality will be available.
WeConfig will offer to install WinPcap if it believes the user would benefit from it.
WeConfig 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/.

Usage

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

• IPConfig protocol for devices running WeOS 4
• mDNS for devices running WeOS 5, Ibex, and BRD/MRD devices.
• HTTPS (Web) must be enabled on WeOS devices. Administrator password must match the setup in the device access dialog. Factory default passwords will be assumed if no administrator password has been specified in WeConfig.
• SNMP protocol. The read community has to be set on the device, matching the setup in the device access dialog. Factory default ready community will be assumed if none have been specified.
• LLDP protocol
• SSH CLI access on WeOS devices. Administrator password must match the setup in the device access dialog. Factory default passwords will be assumed if no administrator password has been specified in WeConfig.

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.
• Basic Setup uses the IPConfig protocol to setup devices on devices running WeOS 4.32 and older. On such devices, the IPConfig protocol must be enabled on the devices to use Basic Setup.
• Backup, restore and firmware upgrade all use the HTTPS interface on WeOS based devices.
• Upgrade on WeOS based devices uses the HTTPS interface.
• All configuration of WeOS devices depends on the use of CLI; hence, CLI must be enabled on the target devices.

News
Support for WeOS 5.21.0
Added interop support for WeOS 5.21.0

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 WeConfig 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 IPConfig protocol.
• Conflicting IP addresses can only be identified on WeOS units, and only for the IP address retrieved using the IPConfig protocol.
• WeConfig does not identify if an IP Address is statically configured or retrieved from a DHCP server. When setting an IP address using WeConfig, it is applied as a static address.
• Non WeOS units have limited support in WeConfig.
• Limited WeConfig SNMP trap support will be available when MS Windows SNMP Trap Host server is activated. For WeConfig 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 firmware version must be 4.18.0 or higher due to a limitation in earlier firmwares.
• Some NICs (mostly low end USB NICs) discard LLDP frames. This means that WeConfig cannot learn where it is connected in the network.
• VLAN configuration is not supported on WeOS 4.13.4 or previous versions.
• WeConfig might not show SNMP traps sent from routers.
• Device connections might not be displayed correctly until 30 seconds after a link up/down event.
• Configuration 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.
• WeConfig is not able to configure Vipers with TTDP enabled on versions of WeOS prior to 5.14.
• WeConfig cannot detect powerline devices (DDW-002).
• The ping and traceroute tools cannot be executed reliably from Falcon devices due to a model specific limitation.
• The functionality of WeConfig in portable mode is limited.
• Optimization of firmware packages will not be done for WeOS 5.13.0 or higher.
• When importing devices from CSV files, model name and firmware version is required in order for a device to be properly identified. Unidentified devices are treated as “unknown devices”.
• WeConfig is not able to identify connections between xRD devices.
• Connections between MRD and BRD devices cannot be derived due to a firmware limitation.
• WeConfig cannot be started from a shared network drive in portable mode.
• When updating the log slider in advanced application settings, a restart of WeConfig may be needed to properly reflect the changes, particularly if trying to log “Everything”
• WeConfig cannot change IP addresses on more than one WeOS 4.33.0 device at a time, when they are in IP conflict with each other, due to a firmware limitation.

Fixed Issues

in 1.20.1

0019742| 1.21.1| SYSTEM| WeConfig can not read vlans on WeOS 5.20

0019742| 1.21.2| SYSTEM| WeConfig can not configure vlans on WeOS 5.20

0019750| 1.21.2| SYSTEM| Ibex RT-330 Firmware upgrade to 6.11.x fails

0019769| 1.21.2| SYSTEM| Upgrading from versions older then 4.16 fails

Prepared by
WeConfig Team| Document
WeConfig 1.21.2 Release Notes
---|---
Approved by
The Program Manager| Date
May 31, 2024| Document No
186018-164897f2

References

• Npcap: Windows Packet Capture Library & Driver

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>