Use Case for Disk Full Errors

The Use Case for Disk Full Errors explains the following scenarios:

• Disk Full Event is generated in BMC Event Management for the Microsoft Exchange Server, for example, BEM.
• Atrium Orchestrator verifies when the disk space threshold has been breached.
• If the disk space threshold is breached, Atrium Orchestrator executes remediation actions on the Microsoft Exchange directory.
• BMC Atrium Orchestrator validates the remediation for disk clean up.
• If the disk clean up action is remediated, Atrium Orchestrator suppresses the event.

Pre-requisites for Disk Full Errors

The pre-requisites for the use case are as follows.

• Enable the following adapters on the grid.
  • Microsoft Exchange 2003 adapter: Enable the adapter using the default configuration, whose parameters point to the setup of the Exchange Server.
  • Windows Command adapter: Enable the adapter with an empty configuration.
  • BMC Event Management monitor adapter: Enable the adapter with the default configuration (using configuration elements like port, gateway-name, and encryption-key ) to monitor BMC Event Management events raised for low disk space on the Exchange Server.
  • BMC Event Management actor adapter: Enable the adapter with the default configuration (using the configuration elements like cell-name, user-name, mcell-dir-file-path, and config-file-location ) to act upon events raised by the BMC Event Management application for low disk space on the Exchange Server.

    Note

    BMC Event Management v7.3 is the supported version.

• Deploy and activate the following modules:
  • AO-AD-Microsoft_Exchange_v2003
  • RBA-AD-BMC_Event_Manager
  • AutoPilot-AD-Utilities
  • AutoPilot-OA-Physical_Device_Utilities
  • AutoPilot-OA-Common_Utilities
• Edit the following module configuration parameters as per the environment settings:
  • BEMActorAdapterName: Specifies the name of the BMC Event Management actor adapter to act upon the BMC Event Management event (for example, bemactor).
  • DiskSpaceThresholdValue: Specifies the maximum usage of the disk space, beyond which cleanup is triggered after receiving the BMC Event Management monitor event (for example, 73).
  • Exchange2003AdapterName: Specifies the Microsoft Exchange 2003 actor adapter name enabled on the peer (for example, MicrosoftExchangeActorAdapter).
  • ExchangeServerInstallationDirectory: Specifies the drive on the Microsoft Exchange Server computer for which disk space usage is checked. For example, C:, E:
  • ExchangeServerName: Specifies the name of the Microsoft Exchange Server (in Exchange Management Console) for which Message Tracking Logs are deleted (for example, S-17125 ).
  • SMTPVirtualServerName: Specifies the name of the SMTP Virtual Server where contents of the BadMail folder and SMTP protocol logs are deleted (for example, SMTPabc ).
  • WindowsCommandAdapterName: Specifies the name of the Windows Command adapter enabled on the grid to check the disk usage on Exchange Server computer (for example, wcli).
  • WindowsCommandHostName: Specifies the host name for the Windows Command adapter (for example, 10.154.1.176 ).
  • WindowsCommandPassword: Specifies the password for the Windows Command adapter (for example, pass123).
  • WindowsCommandUserName: Specifies the user name for the Windows Command adapter (for example, user123).
    
    

1. After providing the pre-requisites, run the use case by creating an event in the BMC Event Management application with the event message set to Low Disk Space on Exchange Server.
2. This event triggers the Disk Full Errors process according to an existing rule in the Microsoft Exchange 2003 module.
3. The Microsoft Exchange 2003 module checks the threshold of the disk space usage:
   1. If the disk space threshold is not breached, the workflow updates the event for BMC Event Management (using BMC Event Management actor adapter) with a note, AO did not find the disk usage to breach the threshold.
   2. If the disk space threshold is breached, the workflow triggers the Disk Space Cleanup process by deleting the BadMail folder contents, the SMTP Protocol Logs for the SMTP Virtual Server, and the Message Tracking Logs for the Microsoft Exchange Server. During the cleanup process, if the workflow fails to delete the logs, it ends by updating BMC Event Management event with the note, BadMail directory cleanup failed. Please use operator assisted remediation process to reclaim disk.
4. After the successful cleanup of the disk, the process checks again if the disk usage is below the threshold, and updates BMC Event Management with a note after completion, Closing after disk space remediation by Exchange adapter and marks the state as Closed.
5. After the cleanup of the disk, if the disk usage is still not below the threshold, the workflow updates BMC Event Management with a note and keeps the state as Open, Disk usage issue could not be remediated despite Exchange Server logs cleanup. Please use operator assisted remediation process to reclaim disk.