-
User Guide for Device Fault Manager 3.1 (With LMS 3.1)
-
Open Source License Acknowledgements
-
Preface
-
Chapter1:Introduction
-
Chapter2:Getting Started with DFM
-
Chapter3:Using the Alerts and Activities Display
-
Chapter4:Using Device Management
-
Chapter5:Using Notification Services
-
Chapter6:Using Fault History
-
Chapter7:Configuring and Administering DFM (Basic)
-
Chapter8:Managing Groups
-
Chapter9:Configuring Views for the Alerts and Activities Display
-
Chapter10:Configuring Polling and Thresholds
-
Chapter11:Administering DFM (Advanced)
-
Appendix A:MIBs Polled
-
Appendix B:Processed and Pass-Through Traps, and Unidentified Traps and Events
-
Appendix C:Notification MIB
-
Appendix D:Events Processed
-
Appendix E:Polling—SNMP and ICMP
-
Appendix F:How DFM Calculates Repeated Restarts and Flapping
-
Appendix G:Frequently Asked Questions in DFM
-
Index
-
Table Of Contents
Getting Started with Device Management
Types of Devices and Device Elements that DFM Monitors
Ports and Interfaces that DFM Manages
Listing Ports and Interfaces in the DFM Inventory
Understanding the Device and Credentials Repository
Events That Trigger DCR and DFM Synchronization
Understanding How DFM Imports Devices
How DFM Identifies Devices Imported from the DCR
How DFM Handles Containing and Contained Devices
Understanding the Device Summary and Device States
Importing All DCR Devices into DFM
Creating Device Group Filters to Control DCR Device Import
Manually Importing DCR Devices into DFM
Determining Which Devices Are in DCR But Not in DFM
Viewing Alias (Duplicate) Devices
Verifying Device Import Using Discovery Status
Troubleshooting Device Import and Discovery
Editing Device Configuration and Credentials
Rediscovering and Deleting Devices
Understanding the Device Details Display
Modifying SNMP Timeout and Retries
Using Device Management
These topics explain how to use Device Fault Manager (DFM) Device Management:
•
Getting Started with Device Management
•
•
•
•
•
•
Getting Started with Device Management
For DFM to monitor a device, you must first add the device to the Device and Credentials Repository (DCR). Use the DCR to perform the following operations:
•
•
•
•
After a device is added to the DCR, you can then add it to the DFM inventory, which is separate from the DCR. You can automatically add all devices as they are added to the DCR; you can create filters to control devices that are added to DFM; or you can add devices manually (the default setting).
For more information on how DFM is affected by the DCR, refer to Understanding the Device and Credentials Repository.
DFM is the front-end for performing the following operations on devices in the DFM inventory:
•
•
•
•
As DFM discovers devices, they pass through various device states until they are fully recognized by DFM (see Verifying Device Import Using Discovery Status for details).
After a device is discovered, DFM manages the device and its components according to the polling and threshold settings that apply to the device group (when it is added to the DCR, the DCR assigns the device to a device group).
Technically, DFM manages a device when the device's management state is set to True. DFM does not manage a device when its management state is set to False.
A device with a management state set to False is also called a suspended device. You can also selectively unmanage device components (see Performing Bulk Manage and Unmanage Operations).
Note
For information on how many devices DFM can manage, refer to Installing and Getting Started with CiscoWorks LAN Management Solution 3.1. If the DFM inventory exceeds your device limit, you will see a warning message.
For more information, see Responding to Messages About Device Limits.
Types of Devices and Device Elements that DFM Monitors
When devices are added to the DCR, they are assigned to Common Services System Defined Groups. The group to which the DCR assigns the device depends on the device type users specify when they add the device.
If you do not select a device type, or selects the wrong device type, the DCR designates the device as Unknown, and it is assigned to the Common Services Unknown group. (For devices with no specified device type, DFM assigns a device type when it discovers the device.) See Table 4-2 for more information.
When devices are imported into CiscoWorks, Common Services assigns each device to the appropriate CiscoWorks Common Services system defined group. These groups are listed in Common Services System Defined Groups.
When a device is added to the DFM inventory, DFM assigns the device components to the appropriate DFM system defined port and interface groups. These groups are listed in DFM System Defined Groups.
DFM manages many device components: chassis, cards, fans, interfaces, memory, Multilayer Switch Feature Cards (MSFCs), Multilayer Switch Modules (MSMs), ports, power supplies, processors, Route Switch Feature Cards (RSFCs), Route Switch Modules (RSMs), SNMP agents, temperature sensors, VLANs, and voltage sensors.
For a detailed list of specific device families and models that DFM supports, see Supported Device Table for Device Fault Manager at http://www.cisco.com/en/US/products/sw/cscowork/ps2421/products_device_support_tables_list.html.
The Alerts and Activities display does not report alerts generated on VLANs. However, you can view VLAN information on the Event properties page and in the Detailed Device View. See Viewing Event Properties and Starting the Detailed Device View.
Ports and Interfaces that DFM Manages
DFM manages device ports and interfaces, as described in the following:
•
–
–
•
When a device is added to DFM, DFM assigns the device interfaces and ports to DFM system defined groups depending on their type. For more information on port and interface groups, see DFM System Defined Groups.
Listing Ports and Interfaces in the DFM Inventory
Note
To find out how many trunk and access ports are currently in the DFM inventory, use the sm_tpmgr command:
# NMSROOT\objects\smarts\bin\sm_tpmgr.exe --server=DFM --sizesLocate the line that is similar to the following:
Number of Ports: 761 [92/92]In this example, 761 represents the number of discovered ports, out of which 92 are managed. Unless you have reconfigured DFM to manage access ports, you can assume these 92 ports are trunk ports.
For interfaces, locate the line that is similar to the following:
Number of Interfaces: 351 [322/280]In this example, 351 represents the number of discovered interfaces, out of which 322 are managed.
To list specific ports and interfaces by their types, names, group membership, or managed state, use the sm_adapter command in conjunction with the getNetworkAdapters.asl script. The syntax is as follows (this command is one line):
# NMSROOT\objects\smarts\bin\sm_adapter.exe --server=DFM [-Dargument] utils\getNetworkAdapters.aslThe arguments to the -D option are described in the following table.
The following examples show how you can use the getNetworkAdapters.asl script.
•
sm_adapter -s DFM utils/getNetworkAdapters.asl•
sm_adapter -s DFM -DNetworkAdapterType=all -DPortType=all -DGroupName="lab-gw.cisco.com" -DManagedState=all utils/getNetworkAdapters.asl•
sm_adapter -s DFM -DGroupName="lab-gw.cisco.com" utils/getNetworkAdapters.asl•
sm_adapter -s DFM -DNetworkAdapterType=Interface -DGroupName="lab-gw.cisco.com" -DManagedState=managed utils/getNetworkAdapters.asl•
sm_adapter -s DFM -DNetworkAdapterType=Interface -DGroupName="lab-gw.cisco.com" -DManagedState=unmanaged utils/getNetworkAdapters.asl•
sm_adapter -s DFM -DNetworkAdapterType=all -DPortType=all -DGroupName="CFG-Interface Groups/1 Gb Ethernet" -DManagedState=unmanaged utils/getNetworkAdapters.asl•
sm_adapter -s DFM -DNetworkAdapterType=all -DPortType=all -DGroupName="CFG-Port Groups - Access Ports/10/100 Mb Ethernet" -DManagedState=managed utils/getNetworkAdapters.asl•
sm_adapter -s DFM -DNetworkAdapterType=all -DPortType=all -DGroupName="CFG-Port Groups - Trunk Ports/10/100 Mb Ethernet" -DManagedState=managed utils/getNetworkAdapters.aslFor instructions on how to manage and unmanage ports, interfaces, IP addresses and other elements, see Suspending Device and Element Monitoring.
Understanding the Device and Credentials Repository
The DCR is a centralized device repository for sharing device information across applications. It provides a single place for managing device credentials and attributes, ensuring consistency across applications.
Individual applications can query the DCR for a device list, device attributes, and device credentials. Changes to the DCR are propagated to all applications. Thus, you should use the DCR to add, import, and export devices, and to change device credentials.
Note
After a device is added to the DCR, you can add it to the DFM inventory. When a device is added to the DCR, the DCR assigns a DCR ID to every managed component. The DCR maps components to devices using either the device name or IP address. When the DCR device is added to DFM, DFM maps the DCR ID to a device name during discovery (see How DFM Determines Device Names).
DFM also uses the DCR ID to verify if the device or component already exists in the DFM inventory (in which case it is not added but is designated as an alias device).
Further information on how DFM identifies devices—such as whether DFM uses an IP address or DNS name as the device name—is provided in Importing Devices into DFM.
By default, DFM is configured so that you must add devices manually, as the devices are added to the DCR. (If you change the setting using CiscoWorks Assistant (CWA), the CWA setting takes priority. Refer to the CiscoWorks Assistant documentation for more information.)
You can change the configuration so that DFM automatically adds all devices when they added to the DCR. You can also use customized filters that control which DCR devices are imported into DFM. When a device is deleted locally (from the DFM inventory), the DCR is not affected.
The device is added to the Device Import list, which shows which devices are in the DCR but not in DFM. In this way, you can easily add the device back to DFM, if you need to.
If a device is deleted from the DCR (global delete), it is deleted from DFM (and all other applications that use that DCR). (For information on deleting components of aggregate devices, see How DFM Handles Containing and Contained Devices.)
All inventory synchronization between the DCR and DFM is controlled from the Device Import page. You can access this page from the DFM home page by selecting Device Management > Device Import. See these topics for more information:
•
•
Note
For more information on the DCR, refer to the Common Services online help.
Events That Trigger DCR and DFM Synchronization
The following events will trigger synchronization between the DFM inventory and the DCR:
•
•
–
–
•
See these topics for more information:
DCR Masters and Slaves
By default, the DCR mode is standalone (single server), and CiscoWorks supports one DCR per CiscoWorks server. However, you can configure the DCR to use a master/slave model.
In this model, the master DCR is the primary repository residing on a CiscoWorks server. Slave DCRs reside on other CiscoWorks servers, and replicate the DCR master. Any change in the master DCR is propagated to slave DCRs.
This allows applications on different servers to use a synchronized device inventory. Using the master/slave model is transparent to DFM.
If the DCR used by your instance of DFM is changed from master to slave, or from standalone to slave, the DCR device list is synchronized with the DFM inventory.
All devices are removed from the DFM inventory (regardless of the device import mode).
•
•
For more information on the DCR Master/Slave model, refer to the Common Services online help.
Understanding How DFM Imports Devices
These topics provide information about the devices and elements you will see in the DFM inventory:
•
•
How DFM Identifies Devices Imported from the DCR
When a device is added to DFM from the DCR, DFM attempts to resolve the DNS name (hostname). DFM does not use the DCR Display Name. Table 4-1 shows how DFM names devices, depending on how the devices are added to the DCR.
After a device is added to the DCR with a specified MDF type and sysObjectID, no one can overwrite it, even if it is incorrect. The only exception is if no sysObjectID is supplied, as described in the previous table.
For information on how DFM performs polling and discovery, refer to Appendix E, "Polling—SNMP and ICMP."
How DFM Handles Containing and Contained Devices
DFM supports contained and containing devices (also referred to as aggregate devices). These are devices that have a parent/child relationship with another device, such as a Catalyst switch (parent) containing an MSFC (child). The switch is considered the containing device, and the MSFC is the contained device.
DFM discovers contained devices depending on the setting of the EnableContainedDevice attribute in the configuration file NMSROOT/objects/vhm/inventorycollector/InventoryCollector.conf. By default, this attribute is set to False.
When the attribute is set to False, any action you perform on a containing device will not be performed on the contained device. You can also perform the rediscover, delete, and suspend operations on a contained device, and it will have no effect on the containing device. However, a contained device can be added and resumed only if the containing device is added or resumed.
When the attribute is set to True, if you add to or rediscover a containing device in DFM, the contained device is also added or discovered.
To set the EnableContainedDevice attribute, use the following procedure.
Step 1
Step 2
•
EnableContainedDevice=False
•
EnableContainedDevice=True
Step 3
a.
On Windows:
net stop crmdmgmtOn Solaris:
/etc/init.d/dmgtd stopb.
On Windows:
net start crmdmgmtOn Solaris:
/etc/init.d/dmgtd stop
Understanding the Device Summary and Device States
The Device Summary lists the device states for all devices in the DFM inventory. The device summary appears when you select Device Management > Device Summary from the DFM home page. Figure 4-1 shows an example of the Device Summary page.
Figure 4-1 Device Summary Page
Table 4-2 describes the information displayed on the Device Summary page.
Table 4-2 Device Summary and Device States
Status
Lists the state the devices are in, from the following possibilities:
Known
The device has been successfully imported, and is fully managed by DFM.
Learning
DFM is discovering the device. This is the beginning state, when the device is first added or is being rediscovered. Some of the data collectors may still be gathering device information.
Questioned
DFM cannot successfully manage the device. See Troubleshooting Device Import and Discovery.
Pending
The device is being deleted. (DFM is waiting for confirmation from all of its data collectors before purging the device and its details.)
Unknown
The device is not supported by DFM.
Number of Devices
The number of devices that are in each device state.
Importing Devices into DFM
A device must be in the DCR before you can add it to the DFM inventory. DFM supports these methods of device import:
•
–
–
–
•
To verify your filter settings, from the DFM home page, select Device Management > Device Import.
Note
Importing Devices with SNMPV3 Credentials
There are three different flavors of SNMPv3 credentials - NoAuthNoPriv, AuthNoPriv, and AuthPriv.
DFM discovers and manages only a device with SNMPv3 AuthNoPriv credentials.
The following are the ways in which DFM reacts when a device is imported into DCR with SNMPv3 Credentials:
•
•
•
Importing All DCR Devices into DFM
By default, DFM is configured to use manual device import. You can modify the configuration so that DFM will automatically add all DCR devices to the DFM inventory.
Figure 4-2 shows the Auto Allocation Settings page.
Figure 4-2 Auto Allocation Settings
The following procedure describes how to configure device import so that all DCR devices are automatically added to DFM.
Note
Step 1
Step 2
The Auto Allocation page opens.
If you previously removed any devices from DFM, they will be listed.
Step 3
a.
b.
c.
DFM will be synchronized with the DCR. Any DCR devices currently not in DFM will be added and any new devices that are added to the DCR will be automatically added.
Any new devices that are added directly to DFM will be discovered.
Step 4
If you do not require the alias for your deployment, remove it using Common Services > Device and Credentials > Device Management.
If you exceed your device limit, DFM will continue to operate, but you will notice that devices are not being added to DFM. Check the license log as described in Viewing and Maintaining Log Files.
For information on device-based licensing, see Responding to Messages About Device Limits.
For information on the rediscovery schedule, see Configuring Rediscovery Schedules.
Creating Device Group Filters to Control DCR Device Import
This topic explains how you can control which DCR devices are added to the DFM inventory by creating a device group filter. A DCR device is only added to DFM if it belongs to the device group in the filter.
Any devices that do not match the filter criteria will be listed in the Device Import tree, and will be available for manual import.
The following procedure describes how to create a customized device import filter.
Step 1
Step 2
The Auto Allocation page opens.
If you previously removed any devices from DFM, they will be listed.
Step 3
a.
b.
c.
Devices only from the selected groups will be added into DFM.
Note
Step 4
a.
List of currently managed devices but do not satisfy Auto Allocation Policy page opens.
Figure 4-3 shows an example of the List of currently managed devices but do not satisfy Auto Allocation Policy.
Figure 4-3 List of currently managed devices but do not satisfy Auto Allocation Policy
b.
Note
Step 5
The Auto Allocation Settings Summary page opens. It lists the following:
•
•
•
•
Figure 4-4 shows an example of the Auto Allocation Settings Summary page.
Figure 4-4 Auto Allocation Settings Summary
The numbers appear as links. Click the number links to view the list of devices and their IP addresses.
Step 6
Step 7
If you do not require the alias for your deployment, remove it using Common Services > Device and Credentials > Device Management.
If you exceed your device limit, DFM displays a warning message. You can get more information from the license log as described in Viewing and Maintaining Log Files.
For information on device-based licensing, see Responding to Messages About Device Limits.
For information on how to handle duplicate devices, see Viewing Alias (Duplicate) Devices.
Manually Importing DCR Devices into DFM
By default, DFM is configured so that you must manually add DCR devices into the DFM inventory.
Figure 4-5 shows the Manual Device Import page.
Figure 4-5 Manual Device Import page
This topic explains how to add devices to the DFM inventory by selecting specific devices.
It also explains how to revert back to manual device import, if you changed the import method.
Step 1
Step 2
The Manual Allocation page opens.
If you previously removed any devices from DFM, they will be listed.
Step 3
Step 4
DFM displays a message that the devices have imported successfully. To check the status, look under Rediscover/Delete or Discovery Status. See Rediscovering and Deleting Devices or Verifying Device Import Using Discovery Status.
Step 5
a.
The Auto Allocation page opens. This is if you were using customized filters or automatic import, but no longer want to.
b.
c.
DFM is configured to use Manual Allocation.
Step 6
If you do not require the alias for your deployment, remove it using Common Services > Device and Credentials > Device Management.
If you exceed your device limit, DFM displays a warning message. You can get more information from the license log as described in Viewing and Maintaining Log Files. For information on device-based licensing, see Responding to Messages About Device Limits.
For information on how to handle duplicate devices, see Viewing Alias (Duplicate) Devices.
Determining Which Devices Are in DCR But Not in DFM
To identify devices that are in the DCR but not in DFM, use the Device Import page. The Device Import page lists devices that are not in DFM for these reasons:
•
•
If no devices are listed, then all DCR devices are in the DFM inventory. You can start the Device Import page by selecting Device Management > Device Import from the DFM home page.
For information on moving devices from the DCR into DFM, see Creating Device Group Filters to Control DCR Device Import. For information on duplicate devices, see Viewing Alias (Duplicate) Devices.
Viewing Alias (Duplicate) Devices
The Alias Devices page lists all devices for which DFM has found duplicates. DFM considers a device to be an alias when the device is added to DFM using its IP address, device name, or host name; and the IP address, device name, or host name already exists in the DCR.
Step 1
Step 2
DFM displays all alias devices for the selected device in the Alias Devices field.
If you want to delete the alias device, use Common Services > Device and Credentials > Device Management.
Verifying Device Import Using Discovery Status
After adding a device, you can verify that it has been imported by using the Discovery Status page.
Step 1
The Discovery Status page opens.
Figure 4-6 Discovery Status Page
Step 2
Step 3
The Last Discovered column displays the time it was fully discovered. A Known state on the device indicates that it was imported successfully.
For a complete explanation of the device states, see Understanding the Device Summary and Device States.
Step 4
Troubleshooting Device Import and Discovery
To access Learning, Questioning, and Pending states:
Step 1
The Rediscover/Delete Devices page opens. (This page is described in Rediscovering and Deleting Devices.)
Figure 4-7 Rediscover/Delete Devices Page
Step 2
See Verifying Device Import Using Discovery Status.
Step 3
The Item Information field gets populated.
Step 4
If the Discovery Progress percentage does not change in a reasonable amount of time. This is 10 minutes for a single device import and 3 hours for a 1,500-device bulk import:
a.
•
•
If it is not, stop and start it using Server > Admin > Processes.
b.
•
•
If it is not, stop and restart it using Server > Admin > Processes.
c.
The Process Management page opens.
•
•
For Questioned Devices, locate your device in one of the following folders:
•
–
Update the device credentials (as described in Editing Device Configuration and Credentials), and readd the device.
–
You can verify this problem by selecting Device Management > Rediscover/Delete, clicking the device link, and checking the Error Message in the Item Information panel. It displays MDFIdmismatch.
Fix the MDF type by reconfiguring the Device Type filed using Common Services > Device and Credentials > Device Management.
–
–
–
–
•
For Pending devices (devices in the process of being deleted), if the device has been in the Pending state for more than ten minutes, stop and restart the InventoryCollector process using the Common Services Process Management page (Server > Admin > Processes).
Exporting Devi ces
You can export devices to create a backup of your devices list, or to import DFM devices into another CiscoWorks server that accepts DCR-format import files. The export file will contain a list of all managed devices, along with their credentials.
You can export devices using either of the following methods:
•
For more information, from the Common Services home page select Device and Credentials > Device Management and click the Help button.
•
Use the following procedure to create a file containing the DFM 3.1 devices. Log information is written to NMSROOT\log\dfmLogs\TIS\DeviceManagement.log.
Step 1
a.
The Process Status report appears.
b.
Note
Step 2
•
NMSROOT/bin/dfmexport fn=fileName ft=CSV|XML•
NMSROOT\bin\dfmexport.bat fn=fileName ft=CSV|XMLwhere fn indicates the output filename and ft indicates the format.
The export file is saved to the NMSROOT/importfiles directory. You should use a unique name for file name so that previous export files are not overwritten.
Editing Device Configuration and Credentials
After you add devices, you can change their configuration setup using CiscoWorks Common Services.
From the Common Services home page, select Device and Credentials > Device Management. From the Device Properties page, you can edit the following credentials:
•
•
•
•
Note
Click the Help button to view more information on the device credentials you can change using Common Services.
Rediscovering and Deleting Devices
Rediscovering and deleting specific devices is controlled by the Rediscover/Delete Devices page. Figure 4-7 shows the Rediscover/Delete Devices page.
Note
The Rediscover/Delete Devices page contains two panes.
•
•
For more information, see Selecting Objects and Groups.
The devices that appear in the device selector are organized in folders by device state. (For a description of device states, see Understanding the Device Summary and Device States.) The folders appear only if there is a device to go in the folder. Figure 4-8 shows an example of the device selector.
Figure 4-8 Rediscover/Delete Devices Device Selector
Devices are displayed in four possible states: Known, Learning, Pending, and Questioned. DFM creates the following folders:
•
•
•
•
Note
Details about and procedures for rediscovering or deleting devices using this page are provided in these topics:
Rediscovering Devices
Through the Rediscover/Delete Devices page, you can rediscover devices or device groups. When rediscovery takes place, if there are any changes to a device or group configuration, the new settings will overwrite any previous settings.
Rediscovery occurs only for active devices. Suspended devices do not go through rediscovery. If some of the devices you are selecting for rediscovery are suspended devices, DFM displays messages indicating that only the active devices will go through rediscovery.
The following events will also trigger rediscovery:
•
•
•
Note
Step 1
The Rediscover/Delete Devices page appears.
Note
Step 2
With many devices in DFM, it can sometimes be difficult to locate the devices you are interested in. To assist you in locating devices, use the search option in the device selector. For more information, see Selecting Objects and Groups.
Step 3
Rediscovery is started. To view rediscovery status, select Device Management > Discovery Status.
Deleting Devices
The DFM Rediscover/Delete Devices page allows you to delete devices from the DFM inventory (local deletion). DFM will no longer recognize the device.
You can only delete devices if you are using filters to customize your device import. If DFM is set to import all DCR devices, the delete operation will fail; the deleted device will simply be re-added to the DFM inventory.
If you do not want this to happen, you should configure a customized import filter as described in Creating Device Group Filters to Control DCR Device Import.
When a device is deleted from the DCR (which can only be done from the Common Services home page), it is automatically deleted from DFM, regardless of the device import setting. If you want to delete an alias device, use Common Services > Device and Credentials > Device Management.
While a device is being deleted, DFM does not allow any rediscovery, suspend, or resume operations to be performed on the device. When you delete a containing device, all of the contained devices are deleted.
If you only want to suspend the managed state of a device, you do not need to delete the device from DFM. You can suspend and resume the managed state of a device through the Detailed Device View page. For more details on suspending and resuming the managed state of a device, see the following:
•
•
Depending upon the load that exists on the system, DFM takes approximately 15 to 40 seconds to delete a device.
Note
Step 1
The Rediscover/Delete Devices page appears.
Note
Step 2
With many devices in DFM, it can sometimes be difficult to locate the devices you are interested in. To assist you in locating devices, use the search option in the device selector. For more information, see Selecting Objects and Groups.
Step 3
If the Delete button is disabled, it means that DFM is set to import all DCR devices by default. The deleted device would be automatically re-added to DFM.
Step 4
Viewing Device Details
On the Device Details page, you select the devices for which you want to see device details. The Device Details display opens and displays the information for the devices. You can also start a Detailed Device View (DDV) from this page, which is useful when you want to view details about a device that has no current alerts.
The Device Details display provides basic information about the device such as name, IP address, when it was added, and so on. For a description of the Device Details display, see Understanding the Device Details Display.
Devices are organized in folders according to their device state. For a description of device states, see Understanding the Device Summary and Device States.
Step 1
The Device Details page appears.
Step 2
Step 3
Do this for each device for which you want to view details. If you want to view details for all of the devices in a group, click the box next to the group.
With many devices in DFM, it can sometimes be difficult to locate the devices you are interested in. To locate devices, use the Search option in the device selector. For more information, see Selecting Objects and Groups.
Step 4
The Device Details display appears.
Understanding the Device Details Display
The Device Details display shows details for the devices that you select. See Viewing Device Details for information on selecting devices.
Figure 4-9 shows an example of the Device Details display.
Figure 4-9 Device Details Display
Table 4-3 describes the information displayed in the Device Details display.
To start a Detailed Device View for the device, click the Device Name link. The DDV page is displayed.
Detailed Device View
The Detailed Device View (DDV) provides extensive information on the devices and device components.
You can view information on devices that DFM is currently managing, as well as devices whose management you have suspended (regardless of whether the device is generating an alert):
•
•
•
See these topics for more information:
•
•
•
Note
Modifying SNMP Timeout and Retries
If an SNMP query does not respond in time, DFM will time out. It will then retry contacting the device for as many times as displayed when you select Device Management > SNMP Config.
The timeout period is doubled for every subsequent retry. For example, if the timeout value is 4 seconds and the retries value is 3, DFM waits for 4 seconds before the first retry, 8 seconds before the second retry, and 16 seconds before the third retry.
The SNMP timeout and retries are global settings.
The default values are:
•
•
Figure 4-10 shows an example of the SNMP Configuration page.
Note
Figure 4-10 SNMP Configuration Page
