Share:|

BMC Network Automation allows you to enhance the logs for a particular problem area by adding fine-tuned entries in your logs directory. In this blog post, I will share tips on how to do use these features effectively.

 

*Note* Please revert the logging to the default state once you are done actively troubleshooting. The enhanced logging may cause App server to run slow.

 

You can Enhance Logging to troubleshoot issues and pinpoint the problem in the following ways:

 

1. Enhance logging by editing the logging.properties file.

    (Pre 8.5 release – system restart required)

    Windows: C:\BCA-Networks-Data\ logging.properties (Default Location)

    Linux: /var/bca-networks-data/logging.properties (Default Location)

 

2. Enhance logging by editing logging properties in the BNA UI. To do so please navigate to the Admin Tab --> Logging. (For 8.5 release and above – system restart NOT required)

 

Sysadmin.png

You can set the following logging levels for better understanding:

 

  • ALL
  • SEVERE
  • WARNING
  • INFO

 

  The following are the DEFAULT logging levels set in BNA:

 

# Default log level for miscellaneous classes.

  .level=WARNING (Can be changed to ALL and SEVERE)

 

# Default log level for ena classes.

  com.bmc.bcan.level=WARNING

  sun.net.www.level=WARNING

 

# Default log level for EnaLoader.

  com.bmc.bcan.engine.service.system.EnaLoader.level=WARNING

  com.bmc.bcan.engine.service.system.EnaLoader.level=ALL

  (Can also be used for performance testing)

 

The following are the ENHANCED logging levels that can be set in BNA:

 

# Suggested log levels for troubleshooting related to Atrium Orchestrator Integration

  com.bmc.ao.level=ALL

  com.bmc.rba.level= ALL

  com.realops.level= ALL

 

# Suggested log levels for troubleshooting related to CLM POD and Container

  com.bmc.bcan.engine.network.pcm.level=ALL

  com.bmc.bcan.engine.network.ipam.level=ALL

 

# Suggested log levels for troubleshooting related to Database

  com.bmc.bcan.engine.database.level=ALL

  com.bmc.bcan.engine.database.admin.level=ALL

  com.bmc.bcan.engine.database.persistence.level=ALL

  com.bmc.bcan.engine.database.persistence.DBSessionFactory.level=ALL

  com.bmc.bcan.engine.database.persistence.DBTools.level=ALL

  com.bmc.bcan.engine.database.ScheduledDatabaseTask.level=ALL

  com.bmc.bcan.engine.database.imports.level=ALL

  com.bmc.bcan.engine.database.exports.level=ALL

 

# Suggested log levels for troubleshooting related to Devices and Groups

  com.bmc.bcan.engine.network.devices.DeviceActionUtil.level=ALL 

  com.bmc.bcan.engine.network.devices.DeviceStore.level=ALL

  com.bmc.bcan.engine.network.devices.SimpleGroup.level=ALL

  com.bmc.bcan.engine.network.devices.SimpleGroupStore.level=ALL

  com.bmc.bcan.engine.network.devices.CombogroupStore.level=ALL

  com.bmc.bcan.agent.shared.imported.network.devices.DeviceType.level=ALL

  com.bmc.bcan.agent.shared.imported.network.devices.DeviceTypeMap.level=ALL

 

# Suggested log levels for troubleshooting related to Device Import.

  com.bmc.bcan.engine.database.imports.DeviceImportFormatMap.level=ALL

  com.bmc.bcan.engine.database.imports.DeviceImportDigester.level=ALL

  com.bmc.bcan.engine.database.imports.DeviceImportFormat.level=ALL

  com.bmc.bcan.engine.database.imports.OverlayImport.level=ALL

  com.bmc.bcan.engine.database.imports.GenericJdbcTransformer.level=ALL

  com.bmc.bcan.engine.database.imports.DeviceImportTransformer.level=ALL

 

# Suggested log levels for troubleshooting related to File Transfer

  com.bmc.bcan.agent.shared.imported.network.fileTransfer.TransferFile.level=ALL

  com.bmc.bcan.agent.shared.imported.network.fileTransfer.TransferFile.level=ALL

  com.bmc.bcan.engine.network.devices.DeviceActionUtil.level=ALL

 

# Suggested log levels for troubleshooting related to Jobs

  com.bmc.bcan.engine.network.jobs.level=ALL

 

# Suggested log levels for troubleshooting related to Network

  com.bmc.bcan.engine.network.level=ALL

 

# Suggested log levels for troubleshooting related to Performance

  com.bmc.bcan.webapp.level=ALL

  com.bmc.bcan.webapp.reports.level=ALL

  com.bmc.bcan.engine.util.MemoryLockManager.level=ALL

 

# Suggested log levels for troubleshooting related to Remote Device Agents

  com.bmc.bcan.agent.level=ALL

  com.bmc.bcan.agent.shared.imported.network.devices.comm.DeviceCommand.level=ALL

  com.bmc.bcan.agent.shared.installed.util.level=ALL

 

# Suggested log levels for troubleshooting related to Reports

  com.bmc.bcan.engine.user.reports.level=ALL

  com.bmc.bcan.webapp.reports.level=ALL

 

# Suggested log levels for troubleshooting related to Scripts

  com.bmc.bcan.shared.imported.network.scripts.level=ALL

  com.bmc.bcan.engine.network.scripts.ConfigurationStore.level=ALL

  com.bmc.bcan.engine.network.scripts.DeltaStore.level=ALL

  com.bmc.bcan.engine.network.scripts.TemplateStore.level=ALL

  com.bmc.bcan.engine.network.scripts.TemplateGroupStore.level=ALL

 

# Suggested log levels for troubleshooting related to Security

  com.bmc.bcan.engine.user.security.level=ALL

 

# Suggested log levels for troubleshooting related to Web Service

  com.bmc.bcan.ws.level=ALL

 

# Suggested log levels for troubleshooting related to Authentication

   com.bmc.bcan.catalina.authenticator.level=ALL

   com.bmc.bcan.catalina.realm.level=ALL

   com.bmc.bcan.engine.network.proxy.level=ALL

   com.bmc.bcan.engine.user.security.level=ALL

 

In Customer Support, we find that knowing what logs to enable and where to look for symptoms is the best place to start troubleshooting issues.  I hope this post has been useful.  You can add your comments or rating below.  To see more like this, see BMC BladeLogic Pulse Blog Posts.

 

# Suggested log levels for troubleshooting related to Web Service