As at 2020-08-13, this is currently in selective pre-release to supported customers only. Please contact Opmantek to be involved.
All of the below is subject to change in released versions of Open-AudIT, however the functionality will remain the same.
We heavily suggest you read this entire page before running any commands.
So you have a Cisco supplied spreadsheet in .xlsb format that contains lots of great information like serial numbers, date of purchase, warranty details and more and you want to get that information into Open-AudIT for easy reporting. Say no more...
We are developing a script to just this very thing. This is a perl script for Linux Open-AudIT servers only.
The information to be consumed relies on the Cisco Ready SMARTNET reports that can be requested from Cisco if you have SMARTNET contracts with them.
Running the Script
First thing to do is to convert the spreadsheet to something workable. That's a CSV. Open the spreadsheet in your program of choice and save the relevant tab (usually named "Powered by Cisco Ready") as a CSV. Copy that file to your Open-AudIT server in to the /usr/local/omk/bin directory. Name it cisco.csv.
Next, log on to your Open-AudIT server and change into the directory /usr/local/omk/bin
Now run the script. Done. It's that easy.
What is imported?
But which rows are imported? We have a few rules around this, namely:
- Product Type must equal CHASSIS
- A Serial Number must be present
- Covered Line Status must be either ACTIVE, EXPIRED or SIGNED
- The Last Date of Support must be after the configured value of 2019-01-01 (see below).
You'll not see much by default until it's complete. When it has done so, you'll see a summary like below.
We have some options that you can set by directly editing the script. These might be settable on the command line in future. They are below.
|name||default value||what it does|
|conf_file||/usr/local/omk/conf/opCommon.nmis||The full path to the Opmantek configuration file. Used to retrieve the UUID.|
0 - Summary output only
1 - Commands run
2 - Command outputs (usually file contents). A lot of information is dumped, use for troubleshooting only.
|filename||cisco.csv||The filename to be imported. If it's not in the default directory, the full path including name is OK to use.|
|last_date_of_support||2019-01-01||The date in YYYY-MM-DD format. Devices with a column value for 'Last Date of Support' that's older than this date will not be imported.|
|user||admin||The name of the Open-AudIT user performing the action. 'admin' is the default user and fine to use.|
Errors and Warnings (oh my!)
You may see lines beginning with DEBUG, INFO, WARNING or ERROR. Generally only ERROR lines are bad and will immediately halt the script execution.
Sample Spreadsheet Columns
Below are the columns from our current Cisco spreadsheet. If your order of these columns differs, it shouldn't matter, however your spreadsheet should contain all the columns used in the mappings below.
The dates we are assuming have a format of D/M/YYYY. These will be reformatted to YYYY-MM-DD for Open-AudIT.
|Serial Number / PAK number||Coverage||Covered Line Status||Business Entity||Sub Business Entity||Product Family||Product ID||Product Description||Asset Type||Product Type||Item Quantity||Covered Line Start Date||Covered Line End Date||Covered Line End Date FY-FQ||Contract Type||Service Brand Code||Contract Number||Subscription Reference ID||Ship Date||End of Product Sale Date||End of Software Maintenance Date||Last Date of Support||LDOS FY-FQ||End Of Life Product Bulletin||Warranty Type||Warranty End Date||Install Site Customer Registry GU Name||Install Site Customer Registry Party Name||Install Site Customer Registry Party ID||Install Site Name||Install Site ID||Install Site Address 1||Install Site City||Install Site State||Install Site Country||Install Site Postal Code||Product Bill to ID||Product Bill-to Partner Name||Product Partner BE GEO ID||POS Partner BE GEO ID||POS Partner BE GEO Name||Service Bill to ID||Service Bill-to Partner Name||Service Partner BE GEO ID||Product List Price $||Default Service List Price $||Default Service Level||Existing Coverage Level List Price $||Instance ID||Parent Instance ID||Product SO||Product PO||Service SO||Service PO||Web Order ID||Mapped to SWSS (Y/N)||Mapped to C1 (Y/N)||Auto-renewal flag|
Mapping the spreadsheet to Open-AudIT
Below are the mappings between the spreadsheet columns and those in Open-AudIT.
|Last Date of Support||end_of_life|
|End of Product Sale Date||end_of_production (new, see below)|
|Covered Line End Date||end_of_service|
|Serial Number / PAK number||hostname|
|End of Software Maintenance Date||maintenance_expires (new, see below)|
|Install Site Customer Registry GU Name||owner|
|Product List Price $||purchase_amount|
|Covered Line Start Date||purchase_date|
|Product Bill-to Partner Name||purchase_vendor|
|Serial Number / PAK number||serial|
|Warranty End Date||warranty_expires|
|Covered Line Status||warranty_status (new, see below)|
In addition to the above we set a few other fields as below.
|last_seen_by||nmap - so we can override this by discovery, audit or the GUI.|
|location_id||Calculated by inserting any missing Locations as below, then associating to the device.|
|org_id||1 - the default Org.|
By default, set to 'network device'. If one of the below matches, set.
We also import the list of Locations mapping the fields as below. If already present, we leave the Location as is. We test for this using the spreadsheet value for Install Site ID.
|Install Site Address 1||address|
|Install Site City||city|
|Install Site Country||country|
|Install Site ID||external_ident|
|Install Site Name||name|
|1 (the default Org)||org_id|
|Install Site Postal Code||postcode|
|Install Site State||state|
New Database Columns
As at Open-AudIT 3.4.0 we need three extra columns to populate. You can add these columns as below by running these commands on the command line of your Open-AudIT server.
NOTE - As at Open-AudIT 3.4.0, these attributes will not appear in the GUI. The template to enable this will ship in a future release.
Discovery and your Imported Devices
So you may already have some of these devices in Open-AudIT, you may not. How does Open-AudIT know what to do here? It all depends on the serial number. The spreadsheet doesn't contain the usual items we need to match devices (think hostname, ip, type, UUID, etc), but it does contain the device serial number. So you'll need to ensure your configuration item named 'match_serial' is set to 'y' (which is the default). As long as that is set, you can import and run discoveries in whichever order you like. Obviously discovery must be working and able to retrieve the serial from the device to perform the match. If you don't have working discovery (usually SNMP based for Cisco network equipment), you'll likely end up with duplicate devices - you have been warned! Just remember, Bulk Edit is your friend.
If you import a device, then run a discovery some fields may be overwritten. Model is likely the first one you'll notice. This is expected. Two screenshots are below of a device after import, then after discovery.
Note that this was an example only as the import was a Cisco Nexus and the discovered device was a Cisco 1841 router. I manually changed the serial to cause them to match.
Below are some sample queries we may refine and include in newer releases of Open-AudIT. To import them, copy the JSON contents and go to menu → Manage → Queries → List Queries and click the Import button in the top right of the table panel.
Devices Not Discovered
Devices Discovered Out of Contract
Discovered Inventory Report
Serial Numbers Not Found
Devices Without Serial Numbers