Ibex-RT-330-5G 50155 LTE
Router & Mobile Gateway
User Manual

Ibex-RT-330-5G 50155 LTE Router & Mobile Gateway

Prepared by
WeConfig Team| Document
WeConfig 1.19.2 Release Notes
---|---
Approved by
The Program Manager| Date
December 11, 2023| Document No
186018-078dc34b

Installation

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

• WinSCP 4.1.3 installed or,
• Pcap 1.6 or later

If neither WinSCP nor Pcap is installed, WeConfig will run in a reduced mode and not all functionality will be available.
WeConfig will offer to install WinSCP 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 Pcap 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 Woe’s 4

• men’s for devices running Woe’s 5, Ibex, and BRD/MRD devices.

• HTTPS (Web) must be enabled on Woe’s 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 Woe’s 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 Woe’s 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 Woe’s based devices.

• Upgrade on Woe’s based devices uses the HTTPS interface.

• All configuration of Woe’s devices depends on the use of CLI; hence, CLI must be enabled on the target devices.

News
Firmware Downloads

It is now possible to have WeConfig automatically download device firmware’s. It is configurable to download only firmware’s of interest, and it will work together with previously downloaded firmware.
Firmware that has not been validated by Westeros (e.g. beta releases) will be shown with a warning triangle. WeConfig will not attempt to apply any upgrade rules to such packages.

FRNT
FRNTv2 is now supported. The UI for FRNT has changed from being device centric to ring centric.
Rings are created or edited in their entirety, rather than a loose collection of devices.
Reboot
When devices are rebooted, WeConfig will wait until they are responding again.
Release Notes
Release notes are now delivered inside the application. The application keeps a record of all previous versions, as well as any new version that has not yet been installed. Furthermore, it is browsable and searchable from inside the application.
User Guide
An updated user guide experience is now available inside of the application, and once opened (F1) will follow the program context around. This context tracking can be disabled.
Show Port Labels
It is now possible to let WeConfig show port labels on the device connections in the topology view.
Ibex 5G Support
5G support has been added to both “Selected Device” and “Diagnostics”.

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

zooms the entire software

0019431| 1.19.0| SYSTEM| Background security scan: non-WeOS devices are

treated as if they has a WeOS CLI

0019432| 1.19.0| SYSTEM| Secondary firmware upgrade fails

0019433| 1.19.0| GUI| Non-gregorian calendars are not properly handled

0019439| 1.19.0| SYSTEM| Change SSH-Port crashes FW Upgrade

0019440| 1.19.0| GUI| Firmware upgrade gives the wrong error message when

device cannot be contacted

0019450| 1.19.0| GUI| Project File not opening in WeConfig 1.18.4

0019452| 1.19.0| SYSTEM| New Project while project file is opened in another

process causes a program termination

0019434| 1.19.0| SYSTEM| Netmask Error when using Template file

0019459| 1.19.0| SYSTEM| Possibility to take Units found via PING into device

access

0019462| 1.19.0| GUI| SNMP read community not always updated

0019494| 1.19.1| GUI| The “Add device” function does not work!

0019497| 1.19.1| SYSTEM| Projects with devices that have aggregate ports in

their VLANs cannot be loaded

0019499| 1.19.1| SYSTEM| WeOS 5 packages are not usable after download until

WeConfig has been restarted

0019500| 1.19.1| GUI| WeConfig crashes when notifications pop up

0019502| 1.19.1| SYSTEM| WeConfig crashes when configuration files are

exported

0019505| 1.19.1| SYSTEM| Missing default hello time when setting port in

existing FRNT v2 horseshoe

0019507| 1.19.2| SYSTEM| Loading projects with manually added connections

fail

0019512| 1.19.2| GUI| When refreshing a device, the CLI communication status

is reset to “unknown” even though the refresh over CLI was successful

0019514| 1.19.2| GUI| Remove unnecessary WLAN monitoring parameters for Ibex

devices

0019516| 1.19.2| SYSTEM| When scripts entered into the CLI tab in WeConfig,

any occurence of the hash character (#) is treated as a comment

0019518| 1.19.2| SYSTEM| WeConfig cannot diagnose CPU load average or

available memory on WeOS 5 devices

0019521| 1.19.2| SYSTEM| FRNTv2 cannot be configured on Coronet based WeOS 5

devices

References

• Npcap: Windows Packet Capture Library & Driver

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>