Microsoft Survivable Branch Appliance Support - Alarms

5

1

Alarm

ASM Unreachable

Communication

SBA Instance;PodName;ContainerType

Critical

• ASM system can not be reached, system is down.
• Check whether the ASM is rebooting.

5

2

Event

Clear ASM Unreachable

Communication

SBA Instance;PodName;ContainerType

• Clears alarm 'ASM Unreachable'.

5

3

Alarm

ASM Failure Recovered

Equipment

SBA Instance;PodName;ContainerType

Warning

• ASM system was previously unreachable, but has come up.
• This alarm doesn't autoclear so the user can investigate the cause, but the system should be working correctly now.

5

4

Alarm

ASM Services Not Running

Processing

SBA Instance;PodName;ContainerType

Critical

• ASM services are not running, calls through the ASM cannot be placed.

5

5

Event

Clear ASM Services Not Running

Processing

SBA Instance;PodName;ContainerType

• Clears alarm 'ASM Services Not Running'.

5

6

Alarm

ASM Services Restarted

Processing

SBA Instance;PodName;ContainerType

Warning

• ASM Services was previously stopped, but has started.
• This alarm doesn't autoclear so the user can investigate the cause, but ASM Services should be working correctly now.

5

7

Alarm

ASM Service Restart Failed

Processing

SBA Instance;PodName;ContainerType

Critical

• The system attempted to restart a failed service on the ASM, service did not start successfully.
• User interaction is required.

5

8

Event

ASM System Started

Processing

SBA Instance;PodName;ContainerType

• This event is set when the SBA communication system is first established, and usually indicates that the Application Solution Module (ASM) has finished booting.
• It should come up at system startup, it may come again if the ASM hardware is rebooted.

5

9

Event

ASM System Shutting down

Processing

SBA Instance;PodName;ContainerType

• A planned or deliberate shut down is taking place on the Application Solution Module (ASM).

5

10

Alarm

Ethernet Link Down

Equipment

SBA Instance;Port;PodName;ContainerType

Major

• Ethernet port specified has lost link.
• Source Instance: Eth0/Eth1 via SBA Monitor.

5

11

Event

Ethernet Link Up

Equipment

SBA Instance;Port;PodName;ContainerType

• Ethernet port specific has recovered link.

5

12

Alarm

ASM-SBC IP Subnet Mismatch

Equipment

SBA Instance;PodName;ContainerType

Critical

• The ASM and SBC Edge IP interfaces are in different subnets and cannot communicate.

5

13

Event

ASM-SBC IP Subnet Match

Equipment

SBA Instance;PodName;ContainerType

• The ASM and SBC Edge IP interfaces are in the same subnet and can now communicate.

• The QoE database is unreachable from ASM, make sure Skype for Business Server or Skype/Lync is deployed and Monitoring database is running.

• The QoE database is now reachable from ASM.

• Failed to store the QoE information from ASM.

• The ASM hasn't been able to apply the CAC update.

• ASM-SBC CAC Update applied.

• ASM Windows Server is not able to activate as genuine Microsoft product.
• Unlicensed ASM sends the alarm.
• The alarm is removed after the license key is successfully installed and the ASM module is restarted.

• NFS mounting of ASM drive failed, make sure ASM module is up and NFS service is running on the ASM module.
  

• ASM hard drive is NFS mounted and available.
  

• ASM Windows Server is activated as genuine Microsoft product.

5

23

Alarm

ASM IP Address conflict

Equipment

SBA Instance;PodName;ContainerType

Critical

• The current ASM IP [ipAddress] is in use by a [address] ('MAC address'), Change the [address] IP 'Is PowerCycle required' and retry.

5

24

Event

Clear ASM IP address conflict

Equipment

SBA Instance;PodName;ContainerType

• ASM IP address conflict cleared.

• ASM Ethernet Port has been detected down.

• ASM Ethernet Port has been detected down is cleared.

• ASM ([SbcCommsVersion]) and SBC ([SBCVersion]) firmware version does not match.

• ASM and SBC firmware version does not match is cleared.