As of Version 6.0 of Inventory for Network Devices and Version 6.1 of Asset Control, there is no functionality to synchronize inventory data with Asset Control for asset types other than "Computer". This document details a method of synchronizing network devices with asset records, and suggests the addition of data classes that are very common and relevant for the "Network Device" asset type.

There are many facets to asset management for network devices and many embellishments that can easily be added. The suggestions here cover the fundamentals as it relates to populating the asset database and offers typical attributes and relations that an asset manager, network support, network engineering, or network operations personnel may require in their daily activities.

The solution described in this whitepaper provides capabilities for:

• Automatically collecting and updating inventory on network devices
• Adding non-discoverable configuration management information to network devices
• Adding non-discoverable asset management information to network devices
• Relating warranties/service contracts to network devices
• Relating carrier provided SLAs to specific circuits
• Incident management and information access through the helpdesk

Altiris products covered in this document:

• Network Discovery (required)
• Inventory for Network Devices (required)
• Asset Control (required)
• Connector Solution (required)
• Contract Management (optional)
• Helpdesk Solution (optional)

Setup

Data Classes

First, it is necessary to set up some additional data classes for the Network Device Resource Type.

1. Create a new Editable Data Class under Configuration > Resource Settings > Data Classes > User Defined:

Name: Circuit Information

Multiple Rows: (checked)

Data Entry Tab Name: Circuits

Below are some suggested attributes for the data class. There are quite a few attributes listed that may not be relevant for all customers. The customer in the test case had a network composed of predominately Cisco or Nortel equipment, with varying circuit types including ATM, Frame Relay, DDS, DSL, Cable, ISDN PRI/BRI, and POTS lines. The customer chose to include much of the configuration information that cannot be discovered via any kind of polling mechanism or found in a MIB object, but is readily available in the myriads of other data sources. This is a very typical scenario that companies deal with.

*note: any property left blank in the table below was simply left as null in the configuration.

Name	Description	Type	Size	Key	List Values	Order
Interface		String	50	X		1
Circuit Identifier		String	50			2
Circuit Type		Static List	50		ATM, Frame Relay, DDS, DSL, Cable, PRI, BRI, Private Line	3
Carrier		Static List	50		AT&T, SBC, Verizon, Telus, Qwest, etc.	4
Install Date	Used to resolve service disputes resulting from different actual "go live" date	Date	N/A			5
Disconnect Date	Used to resolve service disputes resulting from earlier disconnects than carrier claims	Date	N/A			6
Line Coding		Static List	50		AMI, B8ZS	7
Framing		Static List	50		D4, ESF, SF	8
Equalization	Line equalization 0 - 133	Integer	50			9
Base Rate		Static List	50		Nx56, Nx64	10
Channel	Timeslot (1-24)	Integer	N/A			11
Channel Start	Starting timeslot	Integer	N/A			12
Bandwidth (Private Line)	For dialup (POTS)	String	50			13
Local Loop ID		String	50			14
DLCI	Frame Relay port address	Integer	N/A			15
Port Rate	Provisioned bandwidth, e.g. 384kbps	String	50			16
CIR	Committed Information Rate, minimum guaranteed throughput of PVC.	String	50			17
Port ID	Frame Relay port identifier	String	50			18
PVC	Permanent Virtual Circuit identifier	String	50			19
Destination DLCI	Remote end DLCI of attached PVC	Integer	N/A			20
ISDN Switch Type		Static List	50		Basic 5ESS, Basic NI1, Primary 4ESS, Primary 5ESS	21
SPID	ISDN number	Integer	N/A			22

Figure 1. Data class configuration for the "Circuit Information" multi-row table.

Click to view.

In order to simplify the data exchange process, it makes sense to use the single, default Resource Type of "Network Device" rather than multiple Resource Types for every kind of network device, such as routers, switches, etc. Therefore, you need some way to discern between the different kinds of equipment that would be labeled as a "Network Device".

To do this you need to add another class for the "Network Device" Resource Type.

2. Create a new Editable Data Class under Configuration>Resource Settings > Data Classes > User Defined:

Name: Network Device Type

Multiple Rows: (unchecked)

Data Entry Tab Name: General

For this data class, you have a choice of attribute types. One option is to use an attribute type of "Static List". This method is particularly nice if you plan to manage non-discoverable network devices because you can add any type you want and then either manually add them into Asset Control or import them from other data sources using Connector Solution.

Name	Description	Type	Size	Key	List Values	Order
Type	Describes the device type, such as "Router".	Static List	50		Router Switch CSU/DSU Printer UPS Firewall Load Balancer Access Point	1

Figure 2. Static List configuration for the Type attribute.

Click to view.

Figure 3. The result of the Static List in the form.

Click to view.

Another option is to use an attribute type of "SQL Query List". This eliminates the maintenance of the static list, but is limited to only those values that are stored in the Inv_SNMP_Identification.[DeviceType] field, as discovered through Network Discovery. Use this method only if you are confident that all of your managed devices can be read via SNMP and that you can correctly classify them. The query in this case should be as follows:

SELECT DISTINCT i.[DeviceType] AS 'Device Type' FROM dbo.Inv_SNMP_Identification i WHERE (UPPER(i.[DeviceType]) <> UPPER('Printer'))

Name	Description	Type	Size	Key	List Values	Order
Type	Describes the device type, such as "Router", but is limited to the distinct values for "DeviceType" in the database.	SQL Query List	50			1

Figure 4. SQL Query List configuration for the Type attribute.

Click to view.

Figure 5. The result of the SQL Query List in the form. Notice the more limited selection. If you wanted to add CSU/DSUs, for example, that were not discoverable via SNMP, you would not be able to use a relevant type.

Click to view.

3. Be sure to add the new data classes to the Network Device asset type at Configuration > Resource Settings > Resource Types > Asset Types > IT > Network Device.

Figure 6. Adding data classes to the Network Device asset type.

Click to view.

Data Sources and Import Mappings

Since Asset Control does not currently have a synchronization function for Inventory for Network Devices, it is necessary to utilize Connector Solution to extract data from the Notification Server database itself.

To complete the picture, the actual import consists of three phases: First, the asset records need to be generated. This involves extraction of data from the Inv_SNMP_Identification table using ResourceGuid as the key. Second, the Inv_SNMP_Interfaces table must populate the "Circuit Information" multi-row table in the asset record in order to set up primary keys based on the interface description and prepare it for even more data population from external sources ("ifDescr" This is the actual name of the interface or sub-interface, such as Serial0/0:0.125 and will be mostly consistent.). Again, ResourceGuid is used as the key to link the interfaces to the asset. Finally, a third data source and mapping of the customer's choosing populates the remaining fields in the "Circuit Information" multi-row table using the interface description as the key. Likely, a fourth import will also be required to fill in details such as Location, Owner, etc. Only the first and second imports are covered in this document.

Figure 7. Results of the new data class as seen on the asset edit form.

Click to view.

Data Source #1 - Asset record creation

1. Create an ODBC DSN with the following properties:

Driver: SQL Server

Name: <your_dsn_name>

Server: <your_sql_server>

Choose your login type based on the method by which you wish to connect to SQL Server.

Change the default database to "Altiris".

Take the defaults for the rest of the wizard.

Figure 8. ODBC DSN configuration.

Click to view.

Figure 9. ODBC DSN configuration.

Click to view.

Figure 10. ODBC DSN configuration.

Click to view.

2. Create a folder called "Network Devices" under Configuration>Server Settings > Notification Server Infrastructure > Data Replication > Data Sources >.

In the Network Devices folder, create a new ODBC Data Source with the following properties:

Name: NW Devices - Chassis

System DSN: <your_dsn_name>

Import Query:
SELECT * FROM dbo.Inv_SNMP_Identification s WHERE (UPPER(s.[DeviceType]) <> UPPER('Printer'))

*note: This expression filters out discovered printers, but will include any other device type that is collected.

Figure 11. Data source configuration for network device chassis'

Click to view.

3. Create another folder called "Network Devices" under Configuration > Server Settings > Notification Server Infrastructure > Data Replication > Import/Export Rules.

In this folder, create a Resources Import/Export Rule with the following properties:

Name: NW Devices - Chassis

Data Source: NW Devices - Chassis

Resource Type: Network Device

Replication Direction: Import

Allow Resource Creation: (checked)

Allow Resource Update: (checked)

Removed Assets: Left unchanged in the NS database

Resource Lookup Key: Resource Guid to _ResourceGuid

Column Mappings (as follows):

Resource Name: Name

IP Address: IpAddress

Network Device Type: DeviceType

*note: Remaining fields should be set to the default "-Select a Column -". Feel free to import other fields, but just make sure you double-check the column for column mapping. Connector Solution will make assumptions that you may not want. For example, any time there is a "Description" field in a data class, it will match it to "Description" in the source, which could result in erroneous data.

Save and execute.

Figure 12. Import rule for network devices chassis'

Click to view.

Data Source #2 - Circuit Information population

1. Under Configuration>Server Settings>Notification Server Infrastructure>Data Replication>Data Sources>Network Devices, create a new ODBC Data Source with the following properties:

Name: NW Devices - Interfaces

System DSN: <your_dsn_name> (same dsn as the chassis import)

Import Query:

SELECT * FROM dbo.Inv_SNMP_Interfaces s WHERE s.[Description] NOT LIKE '%Ethernet%'

*note: This expression filters out any interface with Ethernet properties. It is assumed that these interfaces will be LAN-side interfaces and won't have extraneous WAN circuit information.

Figure 13. Data source configuration for network device interfaces.

Click to view.

2. Under Configuration > Server Settings > Notification Server Infrastructure > Data Replication > Import/Export Rules > Network Devices, create a new Resources Import/Export Rule with the following properties:

Name: NW Devices - Interfaces

Data Source: NW Devices - Interfaces

Resource Type: Network Device

Replication Direction: Import

Allow Resource Creation: (checked)

Allow Resource Update: (checked)

Removed Assets: Left unchanged in the NS database

Resource Lookup Key: Resource Guid to _ResourceGuid

Column Mappings (as follows):

In the Circuit Information class, for "Interface": Description

*note: Remaining fields should be set to the default "—Select a Column –". Feel free to import other fields, but just make sure you double-check the column for column mapping. Connector Solution will make assumptions that you may not want. For example, any time there is a "Description" field in a data class, it will match it to "Description" in the source, which could result in erroneous data.

Save and execute.

*note: In actual production you would schedule these import policies. New and changed data would then automatically update the records

Figure 14. Import rule for network device interfaces.

Click to view.

Network Devices View in Asset Control

Creating a "picker" report for the Network Device asset type.

The standard picker report for Network Devices in Asset Control is a little basic. In order to simplify the data exchange process, we used a single Resource Type of "Network Device", rather than multiple Resource Types for every kind of network device, such as routers, switches, etc. However, since we created the "Type" custom attribute earlier, it is easy to discern between the different kinds of equipment. Unfortunately, the default picker report does not reflect this well, making it a little confusing to view the devices you want.

Report Configuration

This report combines the Type attribute that we created earlier with resources found in the Inv_SNMP_Identification table, and is able to be restricted based on a value supplied for Type.

1. To create the report, you'll first need to create a new folder. Create this folder as Reports>Assets and Inventory>Asset Management>Custom Reports.
2. Then, from the Custom Reports folder, create a new report. Choose the "Enter SQL Directly" option and paste in the following SQL:
   SELECT DISTINCT
         i.[_ResourceGuid] AS 'ResourceGUID',
         i.[DeviceClass] AS 'Device Class',
         i.[Name] AS 'Name',
         i.[IpAddress] AS 'IP Address',
         c.[Type] AS Type,
         i.[Description]
   FROM dbo.Inv_SNMP_Identification i
         JOIN dbo.Inv_Network_Device_Type c
               ON i.[_ResourceGuid] = c.[_ResourceGuid]
   WHERE c.[Type] = %Type%
   ORDER BY i.[Name]

3. Once finished, edit the report again and add a new Global Parameter with the following properties:

Name: Type

Parameter Type: Dropdown

User Prompt: Device Type

List Type: Query Results

Value Type: String

Value: SELECT DISTINCT Type FROM dbo.Inv_Network_Device_Type

One last step is to make sure that you hide the Resource Guid on the report. Do this in the report editor by selecting the Views button next to your query and make sure that the checkbox is enabled for ResourceGuid under the Known Columns section.

Apply changes to your report.

4. Right click on the report in the tree and move it to Reports > Assets and Inventory > Asset Management > Asset Type Picker Reports.
5. You will then need to select the new picker report from the Resources tab and it will become the default view.

Figure 15. Report configuration via the "Enter SQL Directly" method.

Click to view.

Figure 16. Global "Type" parameter for the picker report.

Click to view.

Figure 17. Views button in the report editor.

Click to view.

Figure 18. Hide the Resource Guid.

Click to view.

Figure 19. Report selector in the Network Device view on the Resources tab.

Click to view.

Figure 20. Results of picker report. The data set only reflects what we've imported so far, which is everything but printers. However, only routers and switches are part of the target data used for this whitepaper.

Click to view.

Experience the Power of Altiris

Now that you have a foundation for network device asset management, it's time to start embellishing it with additional relations that will maximize rapid access to key information. Altiris Contract Management Solution, when combined with Asset Control, enables management of all related contracts such as warranties/support agreements, SLAs, software licenses, etc.

Create Useful Embellishments to Contracts

Warranty/Support Agreement

1. Create a new Editable Data Class under Configuration>Resource Settings>Data Classes>User Defined:

Name: Warranty Details

Multiple Rows: (unchecked)

Data Entry Tab Name: General

Attributes:

Name	Description	Type	Size	Key	List Values	Order
Response Time		Static List	50		4 Hour, 8 Hour, Best Effort	1
Phone Number		String	50			2

Figure 21. Custom Warranty/Support Agreement attributes.

Click to view.

2. Add the new data class to the Warranty Contract Type at Configuration > Resource Settings > Resource Types > Contract Types > Other Contracts > Warranty.

Figure 22. Addition of custom data class to Warranty contract type.

Click to view.

Service Level Agreement

1. Create a new Editable Data Class under Configuration > Resource Settings > Data Classes > User Defined:

Name: Penalty/Bonus Clauses

Multiple Rows: (unchecked)

Data Entry Tab Name: General

Attributes:

Name	Description	Type	Size	Key	List Values	Order
Penalty Amount (Per Minute of Downtime)	Amount paid per minute for outages	Currency	50			1
Contract Bonus for Assured Uptime	Bonus paid to carrier at the end of the contract for keeping the circuit available during the life of the contract	Currency	50			2

Figure 23. Penalty/Bonus clause configuration.

Click to view.

2. Add the new data class to the Service Level Agreement Contract Type at Configuration > Resource Settings > Resource Types > Contract Types > Other Contracts > Service Level Agreement

Figure 24. Addition of custom data class to SLA contract type.

Click to view.

Relate Contracts to Network Device Asset Record

Relate Warranty/Support Agreement

1. Create a new Warranty/Support agreement in Resource Management>Resources > Contract Types>Other Contracts > Warranty.

Supply all of the relevant information for the warranty.

Link the network device asset records by selecting "Add List" in the Covered Hardware data class and then select the desired devices.

Select Done.

Figure 25. Relate assets to Warranty/Support Contracts.

Click to view.

Relate Service Level Agreement

This one is slightly more complicated because we're going to relate the SLA in the most appropriate spot, which is next to the Carrier name in the Circuit Information Multi-Row table.

1. Reopen the Data Class Configuration > Resource Settings > Data Classes > User Defined > Circuit Information.
2. Create a new attribute with the following properties:

Name	Description	Type	Size	Key	List Values	Order
SLA	Related SLA	Resource Foreign Key (select "Contract" for Resource Type)	N/A			5

The Foreign Key attribute type relates the record to tables of another type.

It is desirable to display this field next to the "Carrier" field in the Circuit Information table; therefore, it will be necessary to adjust the order of the attributes in the table. Unfortunately, this is a manual process. You must open each data class and adjust the order.

Figure 26. Addition of SLA field to Circuit Information table.

Click to view.

Figure 27. Configuration of the SLA foreign key attribute.

Click to view.

3. Open the asset record that you want to add the SLA to and click on the "Circuits" tab.

Figure 28. The new SLA field.

Click to view.

4. Click the SLA field to attach the SLA.

With the SLA field highlighted, you can now click on the "Lookup" button to review the SLA.

Select Done.

Figure 29. Review an SLA by launching it from the asset record.

Click to view.

Figure 30. SLA details showing the newly configured Penalty/Bonus clauses.

Click to view.

Figure 31. SLA payment details.

Click to view.

Record Cost Items for an Asset

Cost Items are any costs associated with the procurement, installation, or ongoing maintenance of an asset - in short, any hard cost that would be desirable to track against an asset. WAN devices often have significant costs in fees paid to the carrier to provide connectivity. These costs can be recorded right in the asset record for later financial analysis by Cost Center, Location, or Department.

To record a Cost Item, simply click on an asset's "Accounting Information" tab and enter a Cost Item in the Cost Items data class. It is on this page where you will also see related warranty/support contracts, expense types, depreciation schedules, status, etc.

To make cost items relevant for WAN equipment, it will be necessary to add some Cost Item Types, such as "Service". This is easily accomplished by editing the static list for the Cost Item Type attribute.

Figure 32. Cost Items and Warranty links from the asset record.

Click to view.

1. Edit the data class Data Class Configuration > Resource Settings > Data Classes > Asset Data Classes > Cost Items.
2. Select the "Type" attribute and edit the static list.

Figure 33. Cost Item configuration.

Click to view.

Further, you might wish to attach an accounting code to this Cost Item. You can easily create or import unique accounting codes.

1. Select Resource Management > Resources > Financial Types > Accounting Code.
2. Select the "Type" attribute and edit the static list.

Figure 34. Accounting Code configuration.

Click to view.

Helpdesk Integration

Where do you need the data the most? AT THE FRONT LINE!

Altiris Helpdesk Solution is a culmination point for many of the Altiris tools. From Helpdesk, users can review asset related data, including all of the details discussed in this document - circuit information, warranties, SLAs, owners and contacts, etc. Helpdesk automates traditional IT troubleshooting tasks on heterogeneous equipment by perfoming remote control, password resets, software delivery, backup and restore, connectivity testing, etc. Altiris Helpdesk Solution rounds out a complete suite of automation tools for managing Network Devices and the services they provide.

Figure 35. Network Device assets are automatically made available to select in a Helpdesk incident.

Click to view.

Figure 36. From an incident record, a Helpdesk user has immediate access to all kinds of asset information and troubleshooting tools.

Click to view.