- NG Firewall firmware versions 4.2.x, 5.0.x, 5.2.x
- netfence firmware versions 4.2.x
The Control Centre Event user interface does not show any events from other Barraucda NG Firewall gateways. Only events generated by the CC are shown.
Two event processes are running on a netfence Control Centre concurrently. They both use the same listening port. The only difference between them is the IP address they are listening to.
The box event service records events that are generated by the CC box itself. It is bound to the "Management IP" of the CC box .
The mevent service records events that are generated on Barracuda NG Firewall gateways. It is bound to the "Virtual Server IP".
If a user logs into the MC server using the box IP instead of the server IP, the event user interface of the CC will show only the events of the CC box, since the CC event GUI connects to the IP address specified at login.
When the "Management IP" and CC "Virtual Server IP" of the CC are identical, a conflict arouses between the two services. The box event service is started before the mevent service, and so without exclusive listening IP the start-up of the mevent service is blocked. If a user logs into the CC server is such a situation, he will thus only be connected to a GUI showing the events on the CC box itself.
It is advisable never to use identical management and server IPs on Barracuda NF Control Centres!
Use the correct IP address to log into the CC services. Always use the "Virtual Server IP"!
If the "Management IP" and the "Virtual Server IP" of the system are identical, you have to change the server IP of the CC.
Make sure to insert the new server IP into the "Config" > "Multi-Range" > "Global Settings" > "CC Identity" configuration before modifying the "Virtual Server IP!
The Barracuda NG Firewall gateways will otherwise not accept any configuration updates from the new IP address of the CC.