Hoi @Kevinkrikhaar
Op de azure status page stond eerst het volgende (om 2AM):
Shortly before the start time of this incident, a new network topology description was added into the network automation systems that manage the West Europe region. This new topology included links that were about to be added to the network to increase the capacity in West Europe, but the physical links had not yet been connected or turned on. This network topology description incorrectly listed these links as being ‘Production’. The network automation systems detected LAGs that contained working physical links as well as the non-working ‘Production’ links. Then, as designed, network automation began issuing commands consistent with standard mitigations to turn off the LAGs, to prevent impact due to potential link imbalance.
Helaas nu weggehaald, mogelijk bij het artikel plaatsen?
Op de azure status page stond eerst het volgende (om 2AM):
Shortly before the start time of this incident, a new network topology description was added into the network automation systems that manage the West Europe region. This new topology included links that were about to be added to the network to increase the capacity in West Europe, but the physical links had not yet been connected or turned on. This network topology description incorrectly listed these links as being ‘Production’. The network automation systems detected LAGs that contained working physical links as well as the non-working ‘Production’ links. Then, as designed, network automation began issuing commands consistent with standard mitigations to turn off the LAGs, to prevent impact due to potential link imbalance.
Helaas nu weggehaald, mogelijk bij het artikel plaatsen?