Skip navigation
1 2 3 Previous Next

TrueSight Network Automation

35 posts
Share This:

TrueSight Network Automation (TSNA) is a web-based application that automates the configuration management, compliance management and vulnerability management of network assets. It is highly customizable to meet the needs of network admins. Though it is shipped with the default configuration, there are ways of changing the configuration to use it optimally and efficiently. Below are a few practices which you can apply to TrueSight Network Automation.Dashboard.png


Enable Security Settings: Today security is more important than ever. It is very important that you configure the tool to meet the security standards followed by your organization. TrueSight Network Automation is capable of guarding against XSS attacks, CSRF attacks and Brute force attacks. Also, it is strongly recommended that your database configuration is secured. In addition to that, please check the security algorithms used for communication by TSNA.


Configure RBAC: TrueSight Network Automation can manage fine grained access control. For example, not all users would need API access while others would need UI access and vice versa. Make sure that you share API access only with users that require it. Also, assign devices owned by different networking teams to different realms and create separate roles for those realms. For example, a user may need full access to the devices located in Austin but read only access to the devices located in Sydney. Such devices should be part of two different realms in TSNA.


Purge data: It is very important to purge older data for performance optimization. Administrators can configure the system to purge events, jobs, policies, and historical configurations according to their requirements. To set the purge criteria for events, jobs, and policies, see the Purge Settings in the Managing system parameters page. To set the purge criteria for historical configurations, see Adding or editing a realm.


Enable policies: There are many out-of-the-box (OOB) policies available, such as for configuration backup and sending notifications when compliance violations occur. Also, you can create your own policies to be triggered based on certain events. For example, anytime a new interface is added, the checks which you will manually execute can be automated using policies.

This can save a lot of manual effort for redundant activities. You can also create predefined jobs for sets of actions which you always execute together.


Enable auto groups: Though it may seem trivial, enabling auto groups can really help in grouping  devices the way you would execute actions on those devices. You can also create auto groups based on dynamic field values. This will help in keeping the grouping of devices in the proper order.


Use external scripts: If you have Perl, python or any other scripts which you use to execute commands, use external scripts in TSNA to call these scripts. Do not run these scripts outside of the tool. This will help ensure that only assigned users can execute these scripts and will keep track of which users executed these scripts and if anything goes wrong it will show what happened and why.


The above are some key basic practices and once you have become familiar with them, you can start exploring the following:

  1. Historical reporting using TSNA-DW and Smart Reporting
  2. Multi-Server Administration for keeping the content in sync between different TSNA servers such as QA, Preproduction and Production environments
  3. Vulnerability management for network devices
  4. Exporting events to any event management system, such as if you would like to collect all events on specific system.
  5. Managing devices in multiple networks using a single agent


To summarize, there are multiple configurations available which can optimize the security and performance of the TSNA. To know more, check detailed documentation.

If you are following any other practices, please mention in the comments section to share with other network admins.

Share This:


I hear a lot of concerns from network admins within large enterprises that network automation tools are good, but “my organization is risk averse, so we would not use network automation tools for making any configuration change to the core device and you can forget about OS image upgrades using such a tool.”  Also, we often hear a level of comfort or familiarity with in-house scripting.

Despite the benefits of network automation – greater productivity, quality, agility, job satisfaction, and more – network admins are reluctant to take the next step forward. Too often, the problem is not with the tool, but with the mindset and/or culture.  Change is hard.  So how to make that leap of faith?  Maybe it is to lower the stakes and take small wins.




We can embrace a culture of automation by taking baby steps.  Instead of trying to “eat the elephant in one sitting,” we can keep the end goal in mind and start small, focusing on simple use cases so that we begin our network automation journey with a winning record and build momentum.


  1. Backup.  Configuration of the network device is critical, and so it is important to capture the running configuration, saving it with a reliable automation tool instead of some SAN storage. Use network automation tools to regularly backup the configuration of the device.
  2. Troubleshooting.  You can use a network automation solution to fetch routing tables or simply ping devices, where you are not making any changes to the device whatsoever.  The should can help to accelerate problem resolution and minimize downtime.
  3. Make incremental changes to non-core devices.  Start using the tool for making frequent small changes to the devices such as enabling syslog.
  4. Begin creating config policies.  Start using policies to make sure device configurations are always in order.  Any deviation from the golden config should send you an alert notification, and as your comfort level increases, perhaps the policy can self-heal the devices by itself.
  5. Schedule jobs at daytime.  Schedule jobs using tools during your regular working hours, so that if something goes wrong you would be able to fix it. Once you trust that the tool is capable of executing the desired operations, you can schedule the operations during off-hours.  Again, place small bets, minimize risk, iterate, and learn.
  6. Make changes to series of devices at once.  There might be simple commands which you need to execute across a span of hundreds of devices.  Nobody would enjoy triggering these commands manually; automation tools can accomplish this task quite well.  Even if the operation fails on 10 devices, you still saved a lot of time and boredom for remaining devices, and the network engineer can focus on higher value troubleshooting instead of repetitive, tedious ditch digging.
  7. Generate reports for stakeholders.  Creating reports can be killing your staff’s limited time.  Removing duplicate data and formatting is simply a waste of time for network admins.  If this job of creating recurring reports can be delegated to a network automation solution, the results are more consistent and efficient, so that you get accurate data in real time.  Your internal customers/stakeholders will be happier, and your staff will thank you by not polishing their resume.


These small actions are going to save tremendous amount of time for Level one engineers and can be used productively for innovation and optimized network management.  As we become increasingly comfortable with the network automation solution, we can apply a similar incremental methodology to begin using it for advanced options such as upgrading OS images, compliance and vulnerability management.  Most importantly, the idea is to start somewhere, start now, and increase efficiency and agility for your organization.


To know more about advanced Network Automation, download the Network Automation Maturity Model whitepaper.

Share This:

I am glad to announce the release of new version of TrueSight Network Automation version 20.02. The new release brings a fresh, new user interface for the product.

In addition, it introduces new dashboard as well.  Following widgets are available as part of the dashboard:

  • Discrepancies – Displays the number and percentage (%) of online devices with and without discrepancies on a pie chart. Drilling down on the pie chart displays the devices and their realms.
  • Compliance violations – Displays the number and percentage (%) of online devices with and without compliance violations on a pie chart. Clicking on the pie chart displays the devices and their realms.
  • Devices with most compliance violations – Displays the devices with the greatest number of violations and the number of rules violated by the devices. When you click a device link, a pop-up window displays the rules violated by the device, the rule set to which the rule belongs, and the violation severity.
  • Recently failed jobs – Displays the job IDs of the recently failed jobs, the actions performed via those jobs, the users who initiated those jobs, and status of those jobs. When you click a job ID, the pop-up window displays the Job Details report.




Along with that, we are making the product more and more secured and you will see a lot of changes in the product related to the same.


Also, a highly voted idea: Active Directory to Role Mapping is also available as part of this release. Thank you to the Community for your continued input and participation.


And these are just the highlights!  Check out the page below for the comprehensive list of what is in 20.02:


TrueSight Network Automation 20.02


I would like to take this opportunity to thank you for all your support and I look forward to hearing your feedback.

Share This:

We are pleased to announce the release of our new reporting solution for TrueSight Network Automation. TrueSight Network Automation Reporting replaces BMC Decision Support for Network Automation.

This solution uses the following:

  • TrueSight Network Automation - Data Warehouse — A Network Automation component that works as the ETL engine and the data warehouse. This product also provides out-of-the-box reporting content.
  • TrueSight Smart Reporting - Platform — A reporting platform that enables you to administer, create, and publish reports seamlessly. The simple drag-and-drop UI allows you to create complex reports while providing an enhanced, user-friendly look to your reports for easy consumption.


Here is the overview of the features delivered with the 19.11 release:


Out-of-the-Box Reports

This version of Network Automation Reporting offers the following out-of-the-box reports. You can use these reports as is or customize them as you see fit.

  • Action Activity
  • Change Tracking
  • Compliance
  • Configuration Drift
  • Inventory
  • Source of Change




Custom Reports

If you do not want to use out-of-the-box reports or would like to add additional columns, you can create custom reports. You can compare and analyse reports by using filters, summaries, and calculations, and change the appearance of the reports.


By default, Network Automation Reporting stores a set of attributes for the devices and rules that are available in Network Automation. However, you can store additional attributes for these devices and rules in custom fields by using the dynamic fields feature of Network Automation. You can add any number of custom fields, and then use them to filter report content or display them as content in reports.


Using reports

Network Automation Reporting enables you to:

  • Export reports in the following formats: CSV, DOC, PDF, RTF, Text, XLS. You can also print your reports.
  • Share reports with others on an ad-hoc basis. You can send a report through email or embed a report into an HTML, Wiki, or a blog page.
  • Broadcast reports. You can send a report to one or more users based on a defined schedule and set of rules.
  • Schedule reports and share them through FTP. You can select the format for the report and schedule it to be sent to an FTP location.
  • Import and export your report models and views. You can migrate your content between multiple instances, for example, from the QA to the Production instance.


Viewing the ETL status

Network Automation Reporting provides a built-in, Java-based engine to extract, transform, and load (ETL) data from the Network Automation operational database to the warehouse database.

A user-friendly console in Network Automation Reporting enables you to view summary of all ETL runs on a single page and easily drill-down to see the status of an individual ETL run.


Supported Version of TrueSight Network Automation

Version 19.11 of TrueSight Network Automation Reporting is supported with version of TrueSight Network Automation.

Remember to upgrade TrueSight Network Automation to to use new reporting solution.


Supported Version of TrueSight Smart Reporting - Platform

Version 19.11 of TrueSight Network Automation Reporting is supported with version 19.3 of TrueSight Smart Reporting - Platform.


Support & Documentation

As BMC Decision Support for Network Automation (BDSNA) is going to be end of life in February 2020, we encourage customers to plan their migration to the new solution without delay.

BMC is fully committed to support you for any challenges which you face during this migration.


For more detail, please refer to the documentation available at the following URL:

Share This:

Attached is the sample python script that uses TSNA rest api to login , fetch all devices, and update the name of the devices whose IP address starts with "172". This sample script is for reference purpose only to showcase RestAPI functionality. Modify according to your needs.

Share This:

Hello Everyone,


I am excited to announce the newer release of TrueSight Network Automation 8.9 Service Pack 4 Patch 1 a.k.a, which has combination of features which were critical customer's asks, important fixes including security fixes.


Here are the highlights for this release:


Added more content sync capability to Multi-Server Administration:

Earlier, you could sync combo groups & device security profiles, now, you can push the following types of additional contents from a single application server to multiple application servers:

  • Global Substitution Parameters
  • Templates


Capability for adding groups to a combo group in Text field:

Earlier, you could add groups to a combo group by choosing operators and groups from menus. From this release, you can add operators and groups by entering Boolean expressions in a text editor.



Ability to set default violation severity for a new rule:

You can now define the default violation severity that should be assigned to a new rule. This can be defined by using a new system parameter, Default Violation Severity in the System Parameters page.


In addition, following capabilities were added:

  • Added support for A10 Networks Load Balancer.
  • Ability to assign groups to devices while importing from CSV and assigning devices to groups while adding/editing groups.
  • Support for validating device configuration passwords using additional algorithms
  • Added following additional device type support for vulnerability management:
    • Extreme Networks
    • Hewlett Packard Enterprise (HPE) Aruba
    • Palo Alto


For details, please refer following documentation link:


Also, do not forget to check important issues which were fixed as part of this patch release at:

Known and corrected issues - Documentation for TrueSight Network Automation 8.9 - BMC Documentation


At the end, I would like to request you to please provide us feedback in the comments section below or shoot an email to

Share This:

I am super excited to announce the release of a new version of TrueSight Network Automation 8.9 Service Pack 4 a.k.a 8.9.04.

Here are the highlights for this release:


Multi-Server Administration

We are launching a new console for syncing content & device searches across multiple instances of TSNA using a single interface. Using the Multi-Server Administration console, users would be able to sync Device Security Profiles & Combo Groups across multiple sites of TrueSight Network Automation servers. Not just that, the user would be able to search devices across different sites and launch the site from MSA portal.  The user can register all sites which need to be managed to the MSA portal.


This portal will be useful if you manage more than one TSNA server such as for Dev, QA, Stage or Production or if you keep a separate TSNA server per region.


Pushing TrueSight Network Automation events to EMS (event management software)

Now, you can push the events generated in TrueSight Network Automation to one or more syslog servers, defined as event receivers. This will allow TSNA events to be fed into log analysis solutions like TrueSight Operations Management(TSOM) or Splunk log managers.


Support for SAML 2.0

TrueSight Network Automation now supports SAML 2.0 (SSO) as the authentication mechanism with CA Single Sign-On as the Identity Provider (IdP) along with existing authentication mechanisms such as RADIUS, TACACS & LDAP. This means that you can launch TSNA server for SSO portals such as OKTA or CA Single Sign-On and the user would not be asked for credentials separately.


Support for latest version of Entuity

TrueSight Network Automation integrates with Entuity for a network monitoring solution. You can trigger TrueSight Network Automation jobs directly from Entuity to make desired changes. We have started supporting latest version of Entuity v 17.0.



We have expanded our RESTful APIs to now cover:

  • Device Agents
  • Discrepancy summary report
  • Dynamic Fields
  • Email distribution lists
  • Event Receivers
  • External event filters
  • External Links
  • Global substitution parameters
  • Job Approval Types
  • Remote File Servers
  • Roles
  • Security Vulnerability Importer
  • SNMP Manager Stations
  • Templates


As we are expanding our RESTful APIs, we suggest users migrate from SOAP API to RESTful APIs.


Along with this, because we are committed to keeping the tool as secure as possible, TrueSight Network Automation components (Multi-Server Administration, Application Server & Remote Device Agent) that use a bundled Java environment are shipped with Open JDK 11.


And these are just the highlights!  Check out the page below for the comprehensive list of what is in 8.9.04:


8.9.04: Service Pack 4 - TrueSight Network Automation 8.9


Thank you for all your support and I look forward to hearing your feedback.

Share This:

Software Defined Networking is a paradigm that separates control plane (brain or software) from the data plane (hardware) to simplify network management, by introducing:

  1. Centralized management (by decoupling control and data plane)
  2. Network programmability with APIs where network services and configurations are programmable (“software defined”) through access to the management plane via APIs
  3. Encourages use of virtualization in the data plane


SDN is a system that centralizes network resource management, so that administrators can manage traffic based on the need.


In the market, dominant players for SDN are Cisco (ACI) and VMware (NSX).


However, SDN comes with it’s own limitation. SDN, in itself, is not capable of configuration management, compliance and change management. In fact, security is a big challenge in SDN.



If you admire SDN solutions and want to implement it in your network, you need to address SDN's limitations first. You can use network automation solutions such as TrueSight Network Automation to manage SDN to overcome following challenges:

  1. Vulnerability Management: With SDN, new network security vulnerabilities arise, and it is very important to remediate these vulnerabilities, TrueSight Network Automation can help you to import vulnerabilities and to remediate vulnerabilities in one go.
  2. Compliance: Nowadays, compliancy is one of the mandate in most of the organizations, you will not get any exception for SDN devices either. You can use TrueSight Network Automation compliance engine to apply standards for regulatory and security rules such as SOX, PCI-DSS, HIPAA, NIST, DISA, and CIS.
  3. Configuration Management: It is important to maintain a golden copy of configuration for disaster recovery. You can implement a policy-based approach to configure SDN devices with templates based on best practices to simplify administration and ongoing maintenance.
  4. Change tracking mechanism: When network configuration changes are implemented, network engineers are required to document these changes in change management system. To automate the change tracking and documentation process, you can use TrueSight Network Automation to automatically create network change request in change management tool such as Remedy. After the change request is approved, the change is scheduled for execution in TrueSight Network Automation.


Not only this, automation tools give you a consistent way to seamlessly manage different networking technologies in your network and make the network audit ready.


TrueSight Network Automation already supports management of following SDN devices out of the box:

  1. VMWare NSX
  2. Cisco ACI


Also, you can develop your own device adapter if you would like to manage other SDN devices. You should be able to manage SDN devices in the same way as you used to manage your traditional devices without any overhead.


To summarize, SDN technology is prevailing in market and has it's own advantages, but you need an automation tools to complement the SDN technology and to manage network service delivery for multi-vendor infrastructure. You can consider leveraging TrueSight Network Automation for managing SDN devices without bothering about complexity which SDN devices bring with itself.


In case of any query or suggestion, feel free to comment in the section below.

Share This:

Network administrators need to manage thousands of devices across the globe and it is very hard to track end of life data for wide variety of devices such as switches, routers, firewalls and load balancers. When devices reach their end of life, the vendor stops supporting and no longer publishes patches for the devices. Continued use could lead to new and non-fixable vulnerabilities. Hence, it is critical for network admins to identify EOL’d devices and take necessary action as soon as possible.

TrueSight Network Automation can help you to identify such devices. TrueSight Network Automation can read the EOL bulletins released by Cisco and can alert network admins about EOLs of various devices in the device inventory report. You can import these EOL bulletins in advance of the EOL dates too.


All you have to do is run a canned predefined job called “Populate Cisco Device Board Models and their End of Life Date” and pass Cisco client credentials as runtime parameter.

Upon successful execution of the preceding steps, the End of Life column on the Devices page is populated with the EOL dates for the Cisco devices. If a device has multiple boards, the EOL date shown is the earliest EOL date amongst all device board models.

Once the EOL dates are populated you can use either Device Inventory report or Configuration Search report to view the reports as shown in Figure 1 below.


Figure 1


Another way of performing this operation would be via canned policy “Populate Cisco Device Board Models and their End of Life Date” and EOL data can be fetched and populated recursively as shown in Figure 2 below.


Figure 2


In addition, you can calculate service true-ups for products that Cisco has reached EOS during your current service period. Generate a Device Inventory report filtered by Entire Network and the PID. Calculate the difference between the contract Contract End Date and the EOS date for your service credits.


You can populate EOL data even when application server does not have internet connectivity using FetchCiscoEolData script.

For details refer detailed documentation at:


So, let us start using this functionality and identify EOL’d devices within minutes.

Please do write your comments and suggestions and let us know your views.

Share This:

I am thrilled to announce the release of TrueSight Network Automation (formerly called as BMC Network Automation) 8.9 Service Pack 3 a.k.a 8.9.03.

Here are some of the highlights of the release:


Report Backgrounding

With this release, all reports (except License Usage) will be generated in the background, where you don’t need to tie up your browser session by waiting for a report to display. Instead, you make selections and send the report generation into the background. The system then stores the result in the database and you can view the report any number of times.


Network Security Operations (SecOps) enhancements

Support for importing vulnerabilities from NVD repository:

Now, you can import vendor-supplied security vulnerability reports for Cisco and Juniper device types from the National Vulnerability Database (NVD) repository into the system, and use them to generate compliance rules that detect vulnerable device operating systems. A canned database of NVD-based Cisco and Juniper reports is shipped with the system.

Support for Cisco CVRF XML files formatted per version 1.2:

The canned importer named "Import Cisco Advisory From CVRF XML File" includes an updated stylesheet that now supports parsing Cisco CVRF XML files in version 1.1 or 1.2 formats.


Improved Telnet/SSH Session popup window

The UI-based popup window that interacts with the device command line interface in a Telnet/SSH Session job has been replaced, resulting in improved performance and VT100 support. The replacement is seamless; the window looks the same as it did in previous releases and provides the same functionality.


MultiNICs support for Remote agent

With this release, you can use a single agent to manage multiple networks, where each network is reachable via a different network interface card (NIC) at the device agent. When the agent communicates with devices belonging to a given network, all traffic (both device action traffic and syslog traffic) pass through the NIC for that network.



We have expanded our RESTful APIs to now cover Users, Device Security Profiles and Security Vulnerabilities. As we are expanding our RESTful APIs, we suggest users to migrate from SOAP API to  RESTful APIs.


And these are just the highlights!  Check out the page below for the comprehensive list of what is in 8.9.03:


8.9.03: Service Pack 3 - TrueSight Network Automation 8.9

Got a question or feedback? Talk to us in the comments section below

Share This:

We are excited to introduce you to our new YouTube channel “BladeLogic Automation” for "How-to" videos, intended to help with a specific task or feature of products in the BladeLogic Automation suite (BSA, BDSSA, BDA and BNA).





Focused contents:  The contents of this channel will only focus on providing technical videos for the Server Automation, Decision Support for Server Automation,Database Automation and Network Automation products.   This content is developed by the BMC Support technical teams.


Featured Playlists: The channel will focus on technical contents, such as how-to, troubleshooting guides and functional demonstrations. Similar features/functions and categories will have their own Playlists to reduce the time to search the contents.


Snippet of our Playlists:

Click  to receive notifications when the new technical content is posted on the channel and to get the most out of the products – BSA, BDSSA, BNA and BDA.

Refer to our "Playlists" to play all the videos organized by topic or a product.

Here are the current Playlists:


We welcome feedback from the community.

Share This:

Data warehouses are meant to keep huge data, often collected over a number of years. This often demands allocation of the right amount of space at the beginning when you set up your data warehouse. But often wrong estimation or forecasting of the space might result in your data warehouse failing over a period as data gets accumulated in it, thus, failing your application. This article presents guidelines about sizing BMC Decision Support – Network Automation data warehouse correctly so that it does not run out of space over period.


This article would mainly help BMC Decision Support - Network Automation administrators during new deployments.

The most fundamental factor that determines the space requirements is how many years do you want to retain the data for in the data warehouse. Once you decide the time period, next step is get the number of network devices managed by BMC Network Automation. Once these two factors are determined, you can use the following guidelines to determine the space required by the data warehouse.


Assuming BMC Network Automation is managing 25000 devices, then here are space requirements for it:


ETL runs   ->

Every 24 hours till 1 year:

Every 6 hours till 1 year:

Every 1 hours till 1 year:

DWH Size

10 GB

34 GB

190 GB

Master DB Size

2 GB

3 GB

3 GB

Work DB Size

3 GB

2 GB

2 GB


DWH: Data warehouse Database       DB: Database         ETL: Extract – Transform - Load


Size of Work and Master databases does not grow with the increase in the number of devices managed. So, the space requirement does not change.

Note: Size of DWH changes as per ETL frequency because with each ETL, DWH stores snapshot of compliance and drift status for the entire network and other information.

For example, If you are managing 100,00 devices through BMC Network Automation and you want to store the data for 5 years with ETL running every 24 hours, then the space requirements would be as follows:


DWH Size – [ 10 GB  * (100,00/250,000) ]  * 5   = 20 GB
Work DB Size – 3 GB
Master DB Size – 2 GB


So, the space required would be 25 GB (20 + 3 + 2). Hope you find this article to be useful while you are planning your new deployment for BMC Decision Support – Network Automation and would avoid your data warehouse from running out of space as time passes. Its always better to be proactive then reactive.

8.9.02 is now available !

Posted by Suma Bhat Oct 23, 2017
Share This:

I am excited to announce the release of BNA 8.9 Service Pack 2 a.k.a 8.9.02.  We have been listening to you and working tirelessly to give you the best network automation product in the market that enables you to be some of the most efficient and productive network engineering and operations folks out there !


Here are some of the highlights of the release:


Network SecOps & RESTful APIs

  • BNA’s vulnerability management capabilities now tie into Response Service. If you have not heard of Threat Director (on-prem solution) / Response Service(SaaS solution), our  solutions for vulnerability management across your datacenter, talk to your account manager about a presentation and a demo.
  • RESTful APIs: We have expanded our RESTful APIs to now cover RuleSet, Rule and Predefined Job services. As we expand our RESTful APIs, I’d like to remind our user community that the SOAP APIs will be supported but will not be enhanced going forward.


EOL management

  • Manage EOL of devices with our new capability that can automatically augments EOL information to devices, starting with Cisco devices. Don't be caught with security vulnerabilities in devices that have EOLed anymore !


Performance & Scale

  • Folks that are managing 10s of 1000s of devices or even 100s of thousands of devices, we’ve listened to how long some of the reports can take and and have addressed it with our report thread pooling enhancement. There is improvement across all reports, as compared to the previous release, but the ones I wanted to mention a few in particular:
    1. Device Inventory report - 90% faster
    2. Compliance Summary report - 81% faster
    3. Transcript Search report - 78% faster
    4. Configuration Comparison report - 68% faster
    5. ACL Search report - 48% faster
    6. Transcript comparison report - 36% faster
  • With several refactorings and optimizations on the backend, you can now manage up to 50,000 devices with a single instance of BNA . We will be updating the sizing recommendations shortly.


Device Adapter Development Guide


Enhanced Customer Experience, Security a Supportability

  • Device Inventory report can now be emailed through a job/policy
  • Simply recreate jobs with failures, to run them again ONLY on failed devices
  • Job filter has new groupings to make filtering easier 
  • OS Image filename filtering via white-listing or black-listing of filename patterns to disallow malicious file uploads
  • Runtime guards against incorrect database transaction isolation level settings

And these are just the highlights !  Check out the page below for the comprehensive list of what is in 8.9.02:

8.9.02: Service Pack 2 - BMC Network Automation 8.9


BMC Decision Support - Network Automation 8.9.02 is generally available as well.  Starting this release, BO configuration will not be part of the installer for BDS-NA.

We have included a  separate utility to deploy the BO content i.e. Import BIAR, Connection, User Creation in CMC and the JDBC driver configuration for all the supported database servers. Find details here: 8.9.02: Service Pack 2 - BMC Network Automation 8.9



8.9.01 is here !

Posted by Suma Bhat Apr 19, 2017
Share This:

BNA 8.9.01 now available !


I am very pleased to announce that BNA 8.9 Service Pack 1 is now available with the following new capabilities which we think you are going to find very useful !


Here are some highlights of the release:

1. RESTful APIs

We are introducing RESTful APIs with Swagger UI which is a user-friendly interface to experiment with the REST API calls with no need to write any programs to do so. See more here:

We will support SOAP APIs but no new enhancements will be added*.


2. Network SecOps and Rule engine enhancements

  1. Rule filter enhanced to allow filtering for:
    • rules which cannot be corrected,
    • rules which are correctable via:
      • correctable via Deploy to Active action
      • correctable via Deploy to Stored action
      • correctable via Remediate Action
  2. Rules can now check for specific configuration in conjunction with OS version, for a sharper vulnerability detection.
  3. Compliance summary report now can optionally show Base Score associated with vulnerability rules. Also the vulnerability rules now link to the associated vulnerability improving user experience to access Remediation recommendation from the vendor or other vulnerability information.



3. Expanded import/export capabilities

In addition to the existing compoenets, you can now export and import the following as well:

  • Combo groups,
  • Keywords, Conditions, Policies,
  • Dynamic Fields
  • Roles

This will enable environment specific customizations are your content-sync needs between dev/test/production environments or between multiple BNA instances for example.

*This is available as part of the existing ImportExportService WS API (SOAP).



4. Reporting enhancements

1. You can now choose to hide header in addition to footer during CSV export of the following:

    • Custom action captured results
    • Events list
    • Jobs
    • Predefined jobs
    • Policies
    • Send Email span action

2. Custom trail configurations can now be compared by launching the Configuration Comparison report through external URL



5. Performance improvements

With this latest release the engine has been tuned to fetch data more often from memory than from the database, so you should see improved performance of the following:

  • auto-groups
  • Dashboard
  • Event list page
  • Job list page
  • Rules list page
  • Job Details report


6. Platform enhancements

1. Support of OS management for Alcatel OmniSwitch 6860E-24

2. Microsoft Server 2016 is now supported

3. Microsoft SQL Server 2016 and PostgreSQL 9.5.6 is is now supported as well.



These are just some of the highlights of the release.

Check out the page below for the comprehensive list of what is in 8.9.01

8.9.01: Service Pack 1 - BMC Network Automation 8.9


Thanks !

Share This:

Need a dashboard that gathers information about the network devices and assesses how healthy they are ? Use the out-of-box health dashboard provided by BMC Decision Support – Network Automation.

Additionally, out-of-box reports provide detailed and summarised information about the security vulnerabilities affecting the devices in your environment. Read through the attached document to know how to import the required LCMBIAR file (also attached) and the reports' details.


Note: These reports are available only for version 8.9 of BMC Decision Support -  Network Automation.

Filter Blog

By date:
By tag: