Update Device Interface and Connection Information

Contents
casp1032
 
 
 
DX NetOps Spectrum
 can perform automatic discovery and mapping of a device’s interfaces and connections based on the following events and conditions:
  • A change in the number of configured interfaces on a device.
  • When a device sends a LINK up trap.
  • When 
    DX NetOps Spectrum
     reconfigures a modeled device.
OneClick administrators can also manually update this information about a modeled device. See for information about viewing a device’s interface, sub-interface, and connection information.
Automatic Updates of Device Interface and Connection Information
You can use the following attributes to configure 
DX NetOps Spectrum
 to automatically update interface and connection information about a device.
  • Automatically Reconfigure Interfaces
  • Discover Connections After Link-Up Events
  • Create Subinterfaces
  • Discovery After Reconfigure
  • Topologically Locate Model
Automatically Reconfigure Interfaces
When this attribute is set to Yes, 
DX NetOps Spectrum
 monitors the device for a change in the number of configured interfaces. If it detects a change, 
DX NetOps Spectrum
 automatically updates the device model to reflect the interface changes. The updated interface information appears in the Interfaces view for the device.
Discover Connections After Link-Up Events
 
DX NetOps Spectrum
 automatically discovers and maps a model’s connections one poll interval after it receives a Link Up trap from a device when the Discover Connections After Link-Up Events attribute is set to Yes. This delay lets the device fully reconfigure its related SNMP tables before 
DX NetOps Spectrum
 reads them. The Poll Interval setting for the device appears in the Information view, SPECTRUM Modeling Information subview.
 
Special Considerations for Flapping Interfaces
 
A "flapping" interface is one that is constantly coming up and going back down, usually because of a problem on the device. When Device Discovery After Link-Up Events is set to ‘Yes,’ 
DX NetOps Spectrum
 excludes LinkUp traps from flapping interfaces. As a result, the stream of LinkUp traps from a flapping interface does not interfere with a LinkUp trap for another interface on the same device. The connection discovery action can run as expected.
When 
DX NetOps Spectrum
 detects a flapping interface, a minor alarm is generated on the related device. After a default interval of 10 minutes without receiving a trap from that interface, the alarm clears. The default settings that are used to identify and track flapping interfaces are configured using Event Rules associated with Events 0x220002, 0x220006. The default settings are as follows:
  • An Event Sequence Rule on Event 0x220002, which generates Event 0x220006 if a LinkUp trap is received and is followed by a LinkDown trap from the same interface within 60 seconds.
  • An Event Rate Window Rule on Event 0x220006, which generates Event 0x220007 if 15 0x220006 events are generated within 5 minutes (300 seconds). Event 0x220007 generates a Minor alarm on the device.
  • An Event Pair Rule on Event 0x220006 which generates Event 0x220008 if Event 0x220006 is not followed by Event 0x220007 within 10 minutes (600 seconds). Event 0x220008 clears the minor alarm generated by Event 0x220007.
The default values generate an alarm after 15 LinkUp/Down trap pairs are received. Also by default, the alarm is cleared 10 minutes after the last LinkUp/Down Trap pair is received. You can modify these settings by defining flapping interface event thresholds. The applicable rules are specified in the 
<$SPECROOT>
/SS/CsVendor/IETF/EventDisp file.
For information about manually editing the files, for information about 
DX NetOps Spectrum
 events and event rules, and for information about changing the event rules associated with events 0x220002 and 0x220006, see the .
Create Sub-Interfaces Attribute
When this attribute is set to Yes, and the modeled device supports RFC 1573, 
DX NetOps Spectrum
 models the sub-interfaces for the device. 
DX NetOps Spectrum
 differentiates between physical and logical interfaces. It creates sub-interfaces using the logical interface information that it gathered from the device. A sub-interface appears in the Interfaces tab for a device, nested beneath the logical interface where it is configured.
Discovery After Reconfigure
When this attribute is set to Yes, 
DX NetOps Spectrum
 rediscovers device connections each time that the device model is reconfigured. Both an interface reconfiguration and a manual device reconfiguration trigger a rediscovery when this attribute is enabled.
Topologically Relocate Model
When this attribute is set to Yes, 
DX NetOps Spectrum
 determines whether a device model must be moved to a different topology during a Discovery. 
DX NetOps Spectrum
 moves the device if necessary, based on updated connection mapping.
Manually Updating Interface and Connection Information
You can manually initiate an interface reconfiguration and connection discovery using the following options in the Tools, Reconfiguration menu and the Reconfiguration subview on the Information tab:
  • Reconfigure Model
  • Discover Connections
  • Rediscover SNMP MIBs
  • Rename Interface Models
  • Reevaluate Model Name
  • Reevaluate NCM Device Family
About Reconfiguring Models
When you activate a Reconfigure Model action, 
DX NetOps Spectrum
 finds the interfaces on the device and updates the device interface modeling.
Reconfigure Model actions do 
not
 change the model type. To change the model type, either run the NewMM.pl script or delete and remodel the device by IP address. For more information about running NewMM.pl, see .
The following parameters are reevaluated during a Reconfigure Model action:
  •  
    Device Type
    Verifies the current Device Type attribute value.
  •  
    Model Name
    Checks the Model Naming Order setting on the VNM, and determines whether the device model requires a change.
  •  
    Application Discovery
    Performs a Reconfigure SNMP MIBs action.
  •  
    Interface Discovery
    Determines which interfaces exist on a device, and updates the device modeling as needed.
  •  
    Normalized Source
    Verifies the attribute to use for gathering device CPU and memory usage information.
  •  
    Serial Number
    Verifies the device serial number, if available, and updates the device model if necessary.
  •  
    802.3ad Trunk Memberships
    Checks to see if the device interfaces are members of a 802.3ad trunk.
  •  
    NCM Device Family
    Checks the Device Family value that Network Configuration Manager uses to groups devices by vendor.
Reconfigure a Model
You can reconfigure a model to update device interface information. When you activate a Reconfigure Model action, 
DX NetOps Spectrum
 finds the interfaces on the device and updates the device interface modeling.
 
Follow these steps:
 
  1. Locate the model.
  2. Right-click the model and select Reconfiguration, Reconfigure Model.
    The Reconfigure Model dialog opens, showing the progress of the requested action.
  3. Click OK.
    The Reconfigure Model dialog closes. The model is reconfigured.
Discover Connections
Starting from this release, you can run Discover Connections on multiple devices. When you run the Discover Connections command, 
DX NetOps Spectrum
 performs a Discovery on the selected devices. Discovery data lets 
DX NetOps Spectrum
 update and remap the device model connection information. You can also use this functionality to discover connections in a network container.
 If the discovery is already running on a device, the remaining devices are added to the Discovery queue. A pop-up message appears with the following message:"Another discovery process is currently in progress. Only one discovery process at a time is allowed per <Landscape Name> landscape, queuing request for background processing." 
To know how to view the queue, refer View Queue.
 
Follow these steps:
 
  1. Locate the container for which you want to discover connections in the Explorer tab.
  2. Right-click the container, and select Reconfiguration, Discover Connections.
    The Discover Connections dialog shows the progress of the requested action. If connections are successfully discovered, this dialog indicates success.
  3. Click OK.
    The Discover Connections dialog closes. The connections among the devices in the selected LAN container now appear as pipes in the Topology view.
Discover Connections Queue
The Discover Connections Queue feature allows you to initiate multiple discover connectivity tasks (for example, discover connections after reconfiguration) by adding them to a queue. You do not have to wait for a discovery task to complete to initiate a new one. When the previous task completes, the discovery tasks that are added to the Discover Connections Queue start automatically. You can review the status of a discovery task in the Events tab.
If a mapping process is in progress and you initiate a new Discover Connection action, the following message appears:
“Another discovery process is in progress. Only one discovery process at a time is allowed per landscape, so it is queued.”
 If you trigger the Discover Connections action through REST API, you get the message as 'SUCCESS' when the action is queued.
Also, if the “Discovery After Reconfigure” or the “Discover Connection After Link-up Events” option is set to 'Yes' then the Discover Connectivity action triggers are queued to Discover Connections Queue.
Once the task that is already running completes, a new task in the queue starts. When you select a model, the discovery status messages for that model appear in the Events tab.
View Discover Connections Queue
To view the queue, run the following CLI command on the TopologyWrkSpc model. The queue entries are written to the $SPECROOT/SS/ADiscDebug file. 
 To enalbe the ADiscDebug file, go to VNM -> AutoDiscovery Control -> Debug Options -> Debug AutoDiscovery then set the value to 'ON'.
 ./update action=0x10601 mh=themodelhandleofthe"TopologyWrkSpc"model
Example: > ./update action=0x10601 mh=0x10003aupdate action: successfulResponse has 0 attributes:
In the ADiscDebug file, the following message appears: 'Dumping the pending rediscovery models'
Clear Discover Connections Queue
To clear the discover connection queue, run the following CLI command on the TopologyWrkSpc model:
./update action=0x10602 mh=themodelhandleofthe"TopologyWrkSpc"model
Example: > ./update action=0x10602 mh=0x10003aupdate action: successfulResponse has 0 attributes:
In the ADiscDebug file, the following message appears:
'Clearing the pending rediscovery queue'
Rediscover SNMP MIBs
When a device model is created, 
DX NetOps Spectrum
 automatically creates models for each of the major and minor applications the device supports. Click Reconfigure SNMP MIBs to retrieve application support information from the device. The application models for the device are updated with any changes.
Rename Interface Models
Use this function to update a device’s interface model names after changing the device’s Interface Name Primary Suffix attribute or the Interface Name Secondary Suffix attribute. Using this command forces 
DX NetOps Spectrum
 to rename the interface models using the current values of both the primary and secondary suffixes for the interface model. Some of the suffix options include ifName, ifAlias, ifDescr, and ifIndex.
Entity Table Interface Stacking
When modeling interfaces, 
DX NetOps Spectrum
 uses the information contained within the MIB II ifStackTable to determine their logical stacking. For example, in the case of a frame relay interface with DLCI sub-interfaces, 
DX NetOps Spectrum
 attempts to stack the interfaces using information in the ifStackTable.
If you set the use_if_entity_stacking (0x12a83) attribute to TRUE on a device model in the Attributes tab, 
DX NetOps Spectrum
 attempts to use information from RFC2737 (Entity MIB) to determine interface stacking if the ifStackTable method fails. If an interface does not support ifStackTable, but the interface 
does
 support the Entity MIB, 
DX NetOps Spectrum
 will attempt to stack the interface model using information in the entPhysicalTable.
 
Note: 
This is done on a case-by-case basis as some vendors do not implement the RFC2737 indexing scheme correctly, which can cause interfaces to be incorrectly stacked.
Reevaluate Model Name
Determines whether to change the device’s model name based on the VNM Model Naming Order setting for the VNM managing the device. See 
SpectroSERVER
 Control Subview for information about the VNM Model Naming Order setting.
Reevaluate NCM Device Family
Automatically places a device in the proper device family after a firmware upgrade. For example, if you have a Cisco device that appears in the CatOS family and you then upgrade this device with new firmware and it changes to CiscoIOS, the device does not switch its family automatically. Instead, you can update it using the Reconfigure menu.
Access Interface and Connection Update Controls
You can access to the interface and connection update controls described in this section as shown in the following table:
 
Attribute
 
 
Tools, Reconfiguration Menu
 
 
Reconfiguration
 
 
Attribute Editor
 
Automatically Reconfigure Interfaces
 
X
X
Discovery Connections After Link Up Events
 
X
X
Discovery After Reconfigure
 
X
X
Create Sub-Interfaces
 
X
 
Topologically Relocate Model
 
X
X
Reconfigure Model
X
X
 
Discover Connections
X
X
 
Rediscover SNMP MIBs
X
X
 
Rename Interface Models
X
X
 
Reevaluate Model Name
X
X
 
Reevaluate NCM Device Family
X
 
 
Tools, Reconfiguration Menu
The Tools, Reconfiguration menu provides quick access to reconfiguration actions you can perform on a selected device model. You can also access this menu by right-clicking the device you want to reconfigure.
Reconfiguration Subview and Advanced Subview
The Reconfiguration subview provides access to attributes that control when 
DX NetOps Spectrum
 updates a device’s interface, connection, and topology information. You can also manually reconfigure a device and discover a device’s connections from this subview.
The Advanced section of the Reconfiguration subview provides access to individual model reconfiguration functions that occur as part of the Reconfigure Model function. In some cases, you may want to perform these actions separately instead of performing an overall Reconfigure Model action.
Attribute Editor
Use the Attribute Editor to access some of the interface and connection update parameters for many models or modeled devices.
The Discover Connections Queue feature in the latest release of 
DX NetOps Spectrum
 allows you to initiate multiple discovery tasks by adding them to a queue. You do not to wait till a discovery task to complete to initiate a new one. The discovery tasks added to the Discover Connections Queue are started automatically if the previous task is complete. You can review the status of a discovery task in the Events tab.