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:

https://docs.bmc.com/docs/display/public/tsna89/Populating+End+of+Life+data+for+Cisco+devices

https://docs.bmc.com/docs/display/public/tsna89/Identifying+end-of-sale+and+end-of-life+hardware

 

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.