Answer

If you change the RMP‑100 network configuration so that AUX‑B is enabled in the 192.168.x.x subnet while the system is running, you may create an IP address range conflict with the existing LAN‑A subnet and some LAN‑A devices may lose connectivity or become unreachable.

This is similar to changing the IP address range on a home router: your laptop won’t automatically follow the new network settings until you disconnect/reconnect Wi‑Fi or reboot it.

Resolving the issue:

The RMP‑100 cannot automatically force peripherals to obtain new IP addresses. In these cases:

• You must reboot the RMP‑100 processor.

Is this normal?

Yes. This behavior reflects normal network and DHCP behavior, especially when devices are powered through external PoE injectors that the RMP‑100 cannot control.

• There is no supported, automated way for the processor to:
  • Warn downstream devices that the IP range is about to change, or
  • Force them to drop and renew their DHCP leases.
• As long as there are PoE injectors and DHCP‑assigned devices on those injectors, manual power‑cycling is required after a network change that affects the IP address ranges.