Hub IP addresses have potential to cause conflict. The H2 modules within hubs are given IP’s 192..5.0 & 192..6.0. A Hub acts as an independent core, requiring its own subnet, rather than a piece of kit connecting to a core’s subnet, like a card/panel/IO-box. Therefore, the first two octets of each Hub ID needs to be unique on the network, and not conflicting with any . of consoles/router-cores. This will not be a problem for any Apollo/Artemis systems as 192 is not used as a customer ID. It can be a problem for standalone Summa and Brio consoles that get shipped with a default customer ID of 192. If a core with a customer ID of 192 exists, then its rack ID needs to not conflict with any of the Hub IDs on the same network (even if the hubs are connected via a different core). We need to change the IP scheme for Hubs, to use a first octet that is valid and has not been used as a Hydra2 customer ID (Hydra2 ID’s started where Hydra1 IPs left off, so there should be some low numbers available). In the meantime, the simplest guidance to issue is not to use customer ID 192 if using H2Hubs.