FeM-Net Status
Dashboard

All systems are operational.

Wireless (Aruba system) and Network Management
Fixed

Fixed

1 month ago —

We have not found any problems with stability or the setup of access points. Therefore this incident has been resolved.

Watching

1 month ago —

We were able to recover all crashed access points. We were able to setup all newly installed access points successfully.

We are monitoring the overall situation.

Reported

1 month ago —

The deployed fix failed to hinder the misbehaving access point crashing half of the cluster again, which happend a few minutes ago.

We are working hard on recovering from this incident.

Watching

1 month ago —

We have deployed the fix and are in the process of restoring access point setup operations.

Identified

1 month ago —

We are in the process of deploying the aforementioned fix. We are monitoring the infrastructure and are ready to rollback the fix

Investigating

1 month ago —

We are currently working on a fix to hinder newly registered access points from crashing the cluster. We are planning to deploy this fix in the early evening.

Identified

1 month ago —

The newly enabled access point did duplicated DHCP responses which failed about half of all access points in the FeM-Net. We were able to remove the access point physically.

Most of the access points are back online by now and we are trying to reproduce this behavoir in our testing network.

To prevent the same behavoir of other newly installed access points in House E we have disabled most of them.

Reported

1 month ago —

Migrating the APs has lead to a cluster failure. We are investigating the causal context.

Identified

1 month ago —

We are currently doing a manual on-premise-ap migration and setup into cluster mode.

Identified

1 month ago —

Some newly installed access points do not join the access point management cluster as configured, because of network management issues, but rather create "stand alone mesh systems" which are unable to deliver any FeM-WiFi and accept traffic.

We are currently working on a solution for migrating these APs in our cluster.

Investigating

1 month ago —

We have identified a component of our network management infrastructure to be the cause of parts of this issue. Please see this incident regarding issues with unresponsive access points.

Reported

1 month ago —

The access points do start the automatic configuration now, but fail midway. We are currently investigating this behavoir.

Watching

1 month ago —

We have deployed a fix for our setup process. The newly installed access points should now undergo automatic setup. We are monitoring the situation

Identified

1 month ago —

The access points seem to be unreachable by our DHCP server. We are currently working on a configuration update for the firewall and core router components to fix this issue.

1 month ago —

We are experiencing issues with initial configuration of the newly installed wifi access points in house E.

Incident UUID d9c4ceba-c67e-48b5-b55e-037deb0915ef