Skip to content
CA Spectrum - 10.3
Documentation powered by DocOps

VNM Attributes in the Information Tab

Last update August 15, 2018

Contents

In OneClick, you can view and set various attributes for each Virtual Network Machine (VNM), or SpectroSERVER, in your CA Spectrum installation. The attributes available in the VNM Information view depend on the add-on applications that are installed as part of your CA Spectrum environment. The VNM attributes are grouped into subviews for specific applications and functionality. Most of the attributes have descriptive tooltips.

General Information Subview

The General Information subview provides information about the VNM such as its network or IP address, condition, contact status, and when it was last polled successfully. With administrator privileges, you can set the VNM rollup alarm attributes. See Rollup Alarm Settings for more information. It also contains the following option:

  • Percent Models Activated
    The percentage of models in the SpectroSERVER database that have been activated. The VNM icon will not change from its initial (blue) state until this value reaches 100%. This is useful to determine how close the SpectroSERVER is to becoming fully active after a restart. This value is also displayed in the message area of the CA Spectrum Control Panel.

CA Spectrum Modeling Information Subview

The CA Spectrum Modeling Information subview provides information about attributes such as SNMP community string, landscape, device type, and model type name.

Online Database Backup Subview

Use the settings available in this subview to configure online backups of the CA Spectrum database.

  • Automatic Backups
    Specifies whether the CA Spectrum database is automatically backed up.
    Default: Disabled.
  • Backup Interval
    Specifies how often, in hours and minutes, the CA Spectrum database is automatically backed up.
  • New Backup Date & Time
    Specifies the date and time of the next database backup.
  • Backup Compression
    Specifies whether to compress the backup file using the default compression mode.
    Default: Enabled.
  • Prefix for Backup File Name
    Specifies the prefix used in the database backup file name. File names are appended with the date the backup occurred.
  • Backup Directory
    Specifies the directory on the server where the backup files are written to. You must know the full path to the directory, as this is not a browse function.
  • Minimum Required Disk Space (MB)
    Specifies the amount of free disk space that must exist on the server for a backup to start.
Note: You can initiate an online backup immediately by clicking Begin Backup Now.

SpectroSERVER Control Subview

The SpectroSERVER Control subview lets you configure various aspects of each of your local landscapes through various attributes and settings. It also contains the following views:

The attributes and settings available in the SpectroSERVER Control subview include the following:

  • Device Thresholds
    Set the Device Thresholds attribute to Enabled to activate the threshold functionality on devices supporting threshold. Each threshold values setting must also be set to a non-zero value for the threshold to be active.
    Default: Enabled

  • Auto Connects
    Specifies whether CA Spectrum attempts to resolve the port connections when a pipe is created between two device models. This functionality will use the options that are enabled in the AutoDiscovery Control subview to resolve the port connections. Disabling Auto Connects can improve CA Spectrum performance if your modeled network contains management modules that support non-standard MIBs.
    Default: Enabled
  • Copy Users When Copying Group
    If the Copy Users when Copying Group attribute is set to Yes, whenever you copy a group or a user in a group from one landscape to another, the group and all users in the group are copied as well.
    Default: Enabled
  • Log When Device Cannot Be Contacted
    Specifies whether to continue logging attribute values (such as contact status) for models that have lost primary management contact with the devices they represent. In most cases, this is undesirable since it results in extra traffic to a part of the network where there may already be a problem. Hence, this option is disabled by default and logging is automatically suspended for a device when contact is lost.
  • VLAN Configuration
    Specifies whether Virtual Local Area Networks (VLANs) are modeled for networks on this VNM.
    Default: Disabled
  • Server Polling
    Stops SpectroSERVER from polling the devices it is managing on the network. When SpectroSERVER polling is stopped, the VNM icon displays a gray condition status but no alarm will be generated. To restart SpectroSERVER polling of models, click Start.
  • Minimum Disk Space (kBytes)
    Specifies the minimum amount of free disk space in kilobytes that must exist on the partition that the SpectroSERVER starts from for the SpectroSERVER to start. When the available space is less than this amount, a shutdown message is generated and the SpectroSERVER shuts down.
    Default: 2000
  • Use Fully Qualified Host Name
    Specifies whether the domain name is included with the host name when the Name Service selection is placed first in the Model Naming Order list. For example, if you select Yes here, the model’s icon would be created with a fully qualified name such as myhost.ca.com. If you select No here, the model’s icon would be created without a fully qualified name such as myhost. This only applies when you use the device name returned from the operating system.
    Default: Yes
  • Model Naming Order
    Specifies the order of the list of sources used by CA Spectrum to create model names for new models. If the first source at the top of the list is not available for a device, CA Spectrum attempts to use the next source in the list. The default order is as follows, with the top source being the first in priority:
    • SysName
    • IP Address
    • Name Service
    After changing the model naming order, click ‘Reevaluate All Model Names’ to have CA Spectrum run through all the models in the database and rename each one using the new model naming order.
    The following additional scenarios will trigger the device model name to be reevaluated using the current model name selection. It will not reevaluate based on a new model name selection:
    • If the IP address of the device changes and the model naming is based on IP Address or Name Service
    • If the Reconfiguration, Reevaluate Model Name(s) action is manually applied
    • If the Reconfiguration, Reconfigure Model action is manually applied
    Note: If you do not want a specific device model name to be changed, set the value of the model’s LOCK_MODEL_NAME (0x12a52) attribute to TRUE. This attribute locks the model name value so that it will not be changed.
  • Use Loopback
    If Use Loopback is set to Yes, the SpectroSERVER will use the loopback interface as a primary agent address.
    Default: No
  • Loopback if Description
    Enter a string in this field to identify a preferred loopback interface for CA Spectrum to use when modeling the device. CA Spectrum compares the string entered with the if_descr entries in the device IFTABLE for loopback interfaces only. If a match is found, CA Spectrum uses that loopback interface when it models the device. If there is no match, or no value is specified, CA Spectrum chooses the loopback interface on the device with the lowest if_index value.
  • Update Event Configuration
    Updates the SpectroSERVER with current alert and event mappings.

Alarm Information Subview

The Alarm Information subview provides the number of each type of generated alarm.

  • Active Alarms
    Displays currently outstanding alarms by severity.
  • Total Active Alarms
    Displays the sum of the outstanding alarms.
  • Total Alarms
    Displays the break-down of the different types of alarms generated since the last server restart.

    Note: Blue alarms that are caused by the creation of location or organization models are never cleared.
  • Total Alarms Generated
    Displays the total number of alarms generated since the last server restart.

Event Log Information Subview

The Event Log Information subview provides information related to the event logs. This subview contains the following settings:

  • Events Generated
    Indicates the total number of events generated since the last server restart.
  • Locally Stored Events
    Indicates the number of event records currently held in the database. This field will read "0" unless the Archive Manager is shut down. This will serve as backup storage area for database records until the Archive Manager is restarted.
  • Events Purged
    Indicates the number of event records written to the archive since the last server restart.
  • Max Log Size
    Indicates the maximum number of event records held in the database. When this number is reached, records will be deleted.

Statistics Log Information Subview

The Statistics Log Information subview provides information related to the statistics logs. This subview contains the following settings:

  • Records Generated
    Indicates the total number of statistic records generated since the last server restart.
  • Locally Stored Records
    Indicates the number of statistic records currently held in the database. This field will read "0" unless the Archive Manager is shut down. This will serve as backup storage area for database records until the Archive Manager is restarted.
  • Records Purged
    Indicates the number of statistic records written to the archive since the last server restart.
  • Max Log Size
    Indicates the maximum number of statistic records held in the database. When this number is reached records will be deleted.

Thread Information Subview

The Thread Information subview provides information about the configuration and usage of threads. Comparing the In Use and Available columns for polling, logging, notification, and timer threads can help in determining if SpectroSERVER is running out of thread resources.

Trap Management Subview

  • Unmanaged Trap Handling
    Specifies whether CA Spectrum processes “unmanaged” traps. Unmanaged traps are traps that come from devices which were not modeled in CA Spectrum. By default, the SpectroSERVER creates event records for any “unmanaged” traps it receives As long as this setting is enabled, SpectroSERVER processes these unmanaged traps just as it processes traps from modeled devices; that is, until a trap “storm” occurs (as defined by the Trap Storm Rate and Trap Storm Length attributes). 
    The processing of unmanaged traps not only lets the network administrator know about unmodeled devices that may need to be modeled, but also allows monitoring of overall trap traffic. And it provides troubleshooting capabilities when traps are not mapped correctly. However, unmanaged trap handling can place a significant performance burden on the event logging and the Archive Manager. Depending on your priorities, you can use this setting to disable unmanaged trap handling entirely, or you can leave it enabled but limit it through the trap storm rate and length settings. Remember though that these settings also govern trap processing for modeled devices as well.

    Note: Currently, only VNM models and EventAdmin models (created by users of the Southbound Gateway Toolkit) offer views that let you adjust these settings. For most device models, however, you can use the Attributes tab to create a custom view where you can adjust the default trap storm rate and length settings for that model. For more information about trap storm detection, see How Trap Storm Detection Works.

    Default: Enabled

  • Enable Trap Director
    Lets you enable Trap Director when you want a given SpectroSERVER to forward incoming traps to models on remote landscapes in a distributed SpectroSERVER environment.
    Default: Disabled
  • Remote Forwarding Cache Age Out (minutes)
    Lets you configure the Remote Forwarding Cache age out time (in minutes)
    Default: 180 minutes

How Trap Storm Detection Works

The SpectroSERVER can block the processing of traps that are coming from managed and unmanaged devices when a threshold is reached. Excessive traps that are coming at a high rate can take down your SpectroSERVER and Archive Manager. You can enable the trap storm detection at your SpectroSERVER or at the level of a modeled device. When devices that are modeled in CA Spectrum send more than 20 traps per second, you must adjust traps_per_sec_storm_threshold so that trap storm detection does not limit the ability to receive traps.

You can enable the trap storm detection at any level by configuring the following two attributes. These attributes are available under the Attributes in the Component detail pane for the selected VNM model or for a selected device model:

  • traps_per_sec_storm_threshold
    Defines the rate at which traps are received per second from a managed or unmanaged device. When this rate is sustained for the amount of time that is specified by the TrapStormLength, the SpectroSERVER stops the processing of traps from that unmanaged or managed device.
    Default: 20 traps per second
  • TrapStormLength
    Defines the time in seconds for which the traps_per_sec_storm_threshold value is sustained. SpectroSERVER considers it a trap storm and disables the processing of traps from that unmanaged or managed device.
    Default: 5 seconds

When traps received from any device reach the configured thresholds, the SpectroSERVER identifies this rate as a trap storm. The SpectroSERVER stops handling traps from that device and traps from other devices are not blocked. SpectroSERVER trap storm detection logic is based on each IP address of an unmanaged or a managed device (trap source) that sends traps to SpectroSERVER. As a result, you can configure each device to send traps to the SpectroSERVER at the appropriate rate.

SpectroSERVER does not stop the processing of unmanaged traps when the overall trap storm rate from all the unmanaged devices exceeds the single trap storm threshold rate of an unmanaged device. As a result, you can configure each unmanaged device to send traps to the SpectroSERVER at the appropriate rate.

AutoDiscovery Control Subview

The attributes available in the AutoDiscovery Control subview affect actions that occur during Discovery and Modeling sessions. If you have a DSS environment, you must make any changes in these settings to all your SpectroSERVERs.

These parameters are applied when you are using the Discover LANs functionality available in a device model’s Redundancy and Model Reconfiguration Options view, the Discover Connections functionality available from the right-click menu for a container model (LAN, Network, and so on), or the Auto Connects functionality used to resolve port connections when you manually draw a connection between two models. These parameters are also applied when you use the Discover Connections functionality with the Model by IP or New Model commands.

Each of these parameters is also available when you are selecting modeling options for Discovery. Parameters set in the AutoDiscovery modeling options override the default values for that AutoDiscovery.

Modeling and Protocol Options Subview

The modeling and protocol attributes affect how CA Spectrum discovers and models elements on a network using the following functionality:

  • Discovering and modeling LAN functionality available when reconfiguring a device model.
  • Discovering connections functionality for a container model (LAN, Network, and others).
  • Auto Connects functionality used to resolve port connections when you manually create a connection between two models.
  • Discover Connections functionality when creating a new model.
  • Create WA_Link Models
    Creates a WA_Link model between the interfaces of two routers linked by a wide area connection. This occurs during layer 3 mapping. If this option is not selected, the two linked interfaces are directly connected without the WA_Link model. See Wide Area Link Monitoring for information about Wide Area Link models and how they are used.
    Default: Yes
  • Create LANs (IP subnets)
    Specifies whether CA Spectrum uses a LAN container to represent an IP Subnet. Discovery creates the LAN container during the Layer 3 mapping process for any router interface that routes to a local LAN.
  • Create Physical Addresses
    When this option is enabled, a physical address model is created for any MAC address that is not associated with any modeled device but was heard by a switch. The layer 2 mapper attempts to find a connection for each address found. If a connection is found, a Fanout is created and the physical address is associated to it through Connects_To. If no connection is found the model is placed in Lost and Found. This option is not recommended.
  • Create 802.3 Fanout
    If this parameter is set to Yes and if CA Spectrum cannot make an accurate connection among three or more interfaces, a Fanout model named “802.3_Segment” will be created and these interfaces will be connected to the Fanout model. If this parameter is set to No, a Fanout model will not be created for the interfaces that have unclear connection information, and therefore these interfaces will not be mapped. However, if there is a data relay device’s interface among these interfaces, and all other interfaces are for end node devices, a Fanout model with name “Rpt_Segment” will be created.

Note: If you have 50 or more connections to a single Fanout model, consider changing this model to a Shared Media Link. The Shared Media Links must be modeled manually. These models can provide more control over fault management behavior when multiple connections are monitored. Unlike a Fanout model, Shared Media Links provide configurable thresholds for handling downstream connections that report problems. For example, a Fanout model reports a problem only when all downstream connections are down. However, a Shared Media Link can report the problem sooner, as when 60 percent of the downstream connections are down.

  • IP Address Tables
    Discovery disables Layer 3 mapping and maps only the Layer 2 connections, when this option is disabled. In addition, when this option is disabled, Discovery automatically disables the IP Route Tables option, the Create WA_Link Models option, and the Create LANs (IP subnets) option.
    Default: Yes
  • IP Route Tables
    Specifies whether CA Spectrum will use the IP Address Table to map routers. This option is set to No by default because these tables can be very large and very time-consuming for CA Spectrum to read. When this option is enabled, CA Spectrum will not be able to map unnumbered IP interfaces (0.0.0.0).
  • Source Address Tables
    If this is set to Yes, CA Spectrum will use the device’s Source Address table when discovering connectivity information about this device.
  • Spanning Tree Tables
    If this is set to Yes, CA Spectrum will use the device’s Spanning Tree table when discovering connectivity information about this device.
  • Discovery Protocol Tables
    Set the Discovery Protocol Tables attribute to Yes to allow CA Spectrum to map device connectivity using discovery protocol MIB information. Currently, the following discovery protocols are supported:
    • Nortel Discovery Protocol
    • Cisco Discovery Protocol
    • Extreme Discovery Protocol
    • Cabletron Discovery Protocol
    • Alcatel Discovery Protocol
    • Foundry Discovery Protocol
    • Link Layer Discovery Protocol
  • Traffic Resolution
    If the Traffic Resolution parameter is set to Yes, CA Spectrum will use network traffic data (ifInOctet and ifOutOctet statistics) to determine connections between interfaces, and in many cases eliminate the need for a Fanout model.
  • ARP Tables
    When enabled, CA Spectrum uses the ARP table to determine pingable MAC addresses for the connectivity mapping.
  • ATM Protocols
    If the ATM Protocols parameter is set to Yes, the ATM Discovery runs against all ATM switches in the SpectroSERVER database.
    Default: No
  • SNMP Community Strings
    Create, order, and delete community strings and profiles for SNMP v1, v2c, and v3, which are used, in order, when CA Spectrum attempts to access and model devices that were discovered using SNMP and for which no device community string was provided.
  • SNMP Ports
    The SNMP Ports section lets you create, order, and delete the list of ports to use when accessing and modeling devices. To add port numbers to this list, click Add under the SNMP Ports field, enter the port number and click OK.
  • IP Exclusion List
    A list of IP addresses or IP address ranges that will be ignored and which will not be modeled when devices are discovered.

Trap Based Continuous Discovery Subview

Use the Trap Based Continuous Discovery subview to configure CA Spectrum to automatically create a device model when it receives an SNMP or syslog trap from a device not already modeled. When the SpectroSERVER receives an unmanaged trap, it asserts an event on the VNM model indicating that an unmanaged trap was received.

All models created using Trap Based Continuous Discovery are placed in the New Device Container. CA Spectrum places new models created by a scheduled continuous discovery or by an unmanaged trap into this container.

  • Unmanaged Trap Discovery
    Set the Unmanaged Trap Discovery attribute to Yes to discover and model the source of an unmanaged trap using the IP address sent with the trap. This includes both SNMP and syslog traps from devices as well as Agent Log file matching traps. See SpectroSERVER Control Subview for information about how to enable unmanaged trap handling on the VNM.
  • New Devices In Maintenance
    Set the New Devices In Maintenance attribute to Yes to have new device models created based on an unmanaged trap put into maintenance mode when they are discovered.
  • Create Pingables
    Set the Create Pingables attribute to Yes to have CA Spectrum model devices that cannot be modeled using SNMP as type ‘Pingable,’ if the devices respond to a ping (ICMP) echo request.
  • Discover Connections
    If the Discover Connections attribute is set to Yes, CA Spectrum attempts to discover and model the connections for devices discovered by Trap-based Continuous Discovery.

Debug Options Subview

The Debug Options subview lets you turn on the AutoDiscovery debugging functionality using the following settings:

  • Debug AutoDiscovery
    Set the Debug AutoDiscovery attribute to ‘On’ to have CA Spectrum create a debug output file containing data on the status of the device modeling and mapping process for each Discovery session. These files are available at <$SPECROOT>/SS/ADiscDebug_<timestamp>. The Debug AutoDiscovery option is useful when the discovery modeling or mapping process is hanging or when there are connectivity mapping issues. In these cases, the output file indicates where and on which devices any difficulties were encountered.

    Note: In addition, you can debug a particular device's connectivity mapping process. To do this, set the Debug AutoDiscovery option to On.

    When Discovery’s modeling process is running, CA Spectrum prints out all connection information. This information includes the data collected from bride tables, Proprietary Discovery Protocols, Spanning Tree tables, potential connections, errors encountered, and any additional, pertinent information related to the mapped devices.

  • Abort Discovery
    The Abort Discovery button lets you stop and cancel a currently running AutoDiscovery.

Fault Isolation Subview

The Fault Isolation subview lets you configure various aspects of the CA Spectrum fault isolation functionality. For more information about this view, see Fault Isolation Settings.

Live Pipes Subview

Live Pipes functionality lets you enable port status monitoring for individual links and view link status. In CA Spectrum, a link is a connection between two devices that CA Spectrum has resolved to the port level. For more information about Live Pipes and network fault management, see Live Pipes and Fault Management.

The Live Pipes attribute must be set to ‘Enabled’ on the VNM to enable Live Pipes functionality on the VNM.

If you have administrator privileges, you can set other attributes in this view: Alarm Linked Ports, Suppress Linked Port Alarms, and Port Always Down Alarm Suppression.

Live Pipes and Global Collections in DSS Environments

In a DSS environment, the Live Pipes attribute must be set to the same value on all VNMs so that the Live Pipes functionality provides accurate link connection information in Global Collections. If Live Pipes is set to different values on VNMs in a DSS setup, the Live Pipes information in Global Collections will be unpredictable.

Alarm Management Subview

The Alarm Management subview lets you control some aspects of alarm management.

The AlarmMgmt model, which governs the Alarm Management subview, is a SpectroSERVER application. The AlarmMgmt model inherits the security string of the VNM model only if you have not independently changed the security string of the AlarmMgmt model.

For example, the security strings for the VNM and AlarmMgmt models are initially empty. You change the AlarmMgmt model security string to “Jack” and later, you change the security string for the VNM model to “Jill.” The AlarmMgmt mode security string is not changed to “Jill.”

AlarmMgmt model attributes are not distributed. Bring up the Alarm Management subview for each SpectroSERVER whose alarm management attribute values you want to change. Changing an attribute on one SpectroSERVER does not apply to any other SpectroSERVER.

Important! Displaying Initial and Suppressed alarms is not recommended in OneClick. These alarms can generate a significant volume of network traffic. CA Spectrum generates initial and suppressed alarms if the Disable Initial Alarms and Disable Suppressed Alarms settings for the Virtual Network Machine (VNM) managing your network are set to Yes.

The Alarm Management subview contains the following attribute settings:

  • Generate Alarm Events
    Enables the generation of alarm change events; CA Spectrum creates events (viewable in the Events tab) for alarm changes based on alarm creation, updating, and clearing events.

    Note: If the Generate Alarm Events option is disabled, you do not see Alarm History in the Alarms view.

    Default: Yes

  • Add Events to Alarms
    Controls whether alarm change events are added to each alarm. If disabled, alarm change events are not displayed under the Events tab of the Alarm view.
    Default: No
  • Age Out Residual Alarms Only
    Specifies whether only residual old alarms are cleared. Residual alarms are alarms that existed before SpectroSERVER restart and have not been reverified. If enabled, CA Spectrum clears only residual alarms that are based on the Alarm Age Out timer setting.
    Default: Yes
  • Alarm Age-Out Time (hours)
    Defines how long an alarm can exist in CA Spectrum. Once an alarm has existed for the number of hours that you specify by this attribute, it is a candidate for automatic removal. To disable this functionality, set this attribute to zero (0).
    Every hour, CA Spectrum checks the status of all alarms in the landscape and uses this option to determine whether alarms are cleared. Therefore, an alarm is not removed at the precise moment when its existence time has exceeded the time-out. An alarm can be, at most, an hour “overdue.” 

    You cannot age out non-user clearable alarms. The system functionality that generates such alarms, clears them. Maintenance Mode, Device Has Stopped Responding, and Management Agent Lost are the non-user clearable alarms.

    An aged out alarm which is cleared displays the "System.Alarm_AgeOut" value in its corresponding "Cleared By" column under "Cleared Alarms History" tab. The corresponding cleared event also displays this value in its "Cleared By" column under Events tab.
  • Disable Initial Alarms
    Specifies whether to generate an alarm when the condition of a model changes to Initial. Because these changes in the condition of a model can cause a flood of alarms, disabling this option can improve system performance.
    Default: Yes

    Note: If Initial, Suppressed, or the Maintenance alarms are disabled and later enabled, these alarms are not displayed in the Alarm view for existing models. Only the alarms that are generated after this option is enabled appear in the view.
  • Disable Suppressed Alarms
    Specifies whether to generate an alarm when the condition of a model changes to Suppressed. Because these changes in the condition of a model can cause a flood of alarms, disabling this option can improve system performance.
    Default: Yes
  • Disable Maintenance Alarms
    Specifies whether to generate an alarm when the condition of a model changes to Maintenance. Because these changes in the condition of a model can cause a flood of alarms, disabling this option can improve system performance.

    Note: For more information about putting devices in Maintenance mode, see the Using OneClick section.

    Default: No

  • Auto UnAcknowledge On New Occurrence
    Specifies whether to unacknowledge the new occurrence of an alarm.
    Default: No

BGP Manager Subview

The BGP Manager subview lets you globally configure BGP peer session monitoring.

The BGP Manager subview contains the following attribute settings:

  • BGP Peer Session Monitoring
    Monitors the status of the peer session on the BGP port at the polling interval of the port model's Polling_Interval Attribute value if this setting is enabled and the live pipe on the BGP peer session port is turned on. If you disable this option, an event of type 0x220018 is generated on the BGP downed port models to clear the BGP alarm.
    Default: Disabled
  • BGP Peer Session Discovery Interval (minutes)
    Indicates the interval for BGP peer session Discovery. If BGP Peer Session Monitoring is enabled, BGP Peer Session Discovery initially runs on each BGP device at SpectroSERVER startup and when a new BGP device is modeled. After, BGP Peer Session Discovery runs according to the interval you set.
    Default: 24 hours

Network Configuration Manager Subview

The Network Configuration Manager subview provides information about Network Configuration Manager.

This subview contains the following setting:

  • Export Directory
    Specifies the local directory to which you want to export configuration text files. If you want to export configuration text files to a network share, you must specify the UNC path to the directory. For example, \\Shared_Server\Export\ExportFiles.

TFTP Configuration Subview

The TFTP Configuration subview provides information about the Trivial FIle Transfer Protocol (TFTP). TFTP transfers configuration files.

This subview contains the following settings:

  • Default TFTP Directory
    Specifies the TFTP server path.
  • TFTP Transfer Timeout (sec)
    Specifies the maximum time (in seconds) for a data transfer to complete.
    Default: 50 seconds, which means the data must be completely transferred within 50 seconds.
Note: For more information about the TFTP server, see the Network Configuration Manager section.

FTP Configuration Subview

The FTP Configuration subview provides information about the File Transfer Protocol (FTP).

This subview contains the following settings:

  • FTP Username
    Specifies the FTP server username.
  • FTP Password
    Specifies the FTP server password.
  • Default FTP Directory
    Specifies the FTP server path.
Note: For more information about the FTP server, see the Network Configuration Manager section.

Thresholds And Watches Subview

You can create, configure, and administer watches in OneClick. View and configure watches from a table in the Thresholds And Watches subview.

Note: You can access the Thresholds and Watches subview from the Information tab for a model.

The Watches table displays information for each watch defined on that model. The Watch Status column displays the watch condition with color codes as follows:

  • Gray
    Indicates that the watch is inactive. The watch is not currently running because it has not been activated.
  • Blue
    Indicates the initial state of the watch. The watch is activated but has yet to run for the first time.
  • Green
    Indicates that the watch is active and running without any violation.
  • Yellow
    Indicates that the watch threshold is violated.
  • Red
    Indicates that the watch failed to evaluate. The text explains the reason.

The toolbar buttons let you do the following:

  • Activate
  • Deactivate
  • Create
  • Edit
  • Copy
  • Delete
  • Display watch information
  • Print watch information
  • Export the Watches table

Host Security Information Subview

When a client application connects to a SpectroSERVER, CA Spectrum reads the .hostrc file to obtain a list of valid hosts. If a host name from the .hostrc file does not resolve to a network address, you will receive a “Permission Denied” error message. In addition, an event and an alarm (Event00010e01, Prob00010e01) will be generated on the VNM indicating that there are unresolved host names.

To help you find the cause of this problem, the Host Security Information subview displays a list of resolved and unresolved host names.

Modeling Gateway Subview

You can view information about recent imports in a table in the Modeling Gateway subview.

The Modeling Gateway table displays information about recent imports. The number of import files listed is controlled by the Max Records field. The default value for the Max Records field is 30.

Note: For more information about the Modeling Gateway table, see the Modeling Gateway Toolkit section.

IP Services Subview

The IP Service subview provides information about VPN Manager and VPLS Manager. Further options are available depending upon the products you have installed.

Logical Connection Import Subview

The Logical Connection Import subview lets you create logical connections between virtual link models by importing a comma-delimited, ASCII file (text file or XML file) that defines the connections. You can define connections that include two ATM models or an ATM model and a Frame Relay model. Click the Import button to import a file.

Note: For more information about logical connections between virtual link models, see the ATM Circuit Manager section.

Shared IP Detection and Alarming

The following settings control when CA Spectrum generates alarms for shared IP addresses.

  • Shared IP Alarming
    Specifies whether shared IP alarming is enabled.
    Default: Disabled

    Note: Shared IP alarms will be cleared when you set the Shared IP Alarming attribute to Disabled.
  • Currently Shared IP Addresses
    Specifies which IP addresses are currently considered “shared” in CA Spectrum.

    Note: The IP addresses in the loopback subnet are displayed as shared addresses in the ‘Currently Shared IP Addresses’ list, however, no alarms will be triggered based on these addresses to help prevent multiple unnecessary alarms for a known and desired configuration.
  • Allowed Shared IP Addresses
    Specifies which IP addresses can be shared in CA Spectrum. Click Add or Remove to modify this list as needed.

    Note: You can modify a device model's NETWORK_ADDRESS (0x12d7f) attribute and PrimaryAddress (0x12d80) attribute if the device model's IP address is included in the Allowed Shared IP Addresses list on the VNM model.

Shared IP Alarms and Events

When CA Spectrum detects that two or more devices share one or more IP addresses, and you have configured CA Spectrum to generate alarms in this case, you will see an orange alarm on all device models that share the IP address or addresses. The event generated on each device will contain a list of all device models involved as well as a list of all shared IPs. The event will look similar to the following:

Device {X} of type {Y} has the following shared IP addresses:
<list of shared IPs and devices>

Since the detection of shared IP addresses is dependent on CA Spectrum device models, each time a new device model is created or destroyed, a new event containing updated data may need to be generated on the devices that have shared IPs.

No Unique IP Alarms and Events

If a device is found to contain no unique IP addresses, then a red alarm is asserted on it to notify you of this condition because no reliable communication or management may be made with that device. The event will look similar to the following:

Device {X} of type {Y} has no globally unique IP addresses.  Each of the following addresses is shared with another device:
<list of shared IPs and devices>

Network Address Is Shared

If you manually create a device using a shared IP address as the Network_Address you will receive an event such as the following:

Device {X} of type {Y} has its Network Address set to an IP that is currently shared by multiple devices.  No reliable communication or management may be made with this device.  The shared IP {shared IP} is shared by the following other devices:
<list of other devices>

Configuring Allowed/Non-Alarming Shared IP Addresses

You can configure CA Spectrum with a list of IP addresses, IP address ranges, or subnets for which sharing between multiple devices is allowed. Populate the Allowed Shared IP Addresses list with the addresses to share. The IP addresses on this list do not generate alarms.

You can use OneClick to add or remove IP addresses, IP address ranges, or subnets from this list. Shared alarms are cleared when you add an IP address to the list. Adding an IP address causes the associated device to have no more shared IP addresses that generate alarms.

Mtype Based IfType Filtering Subview

From CA Spectrum 10.3, you can filter interfaces of a device model which you do not want to model and monitor in CA Spectrum. In OneClick, The 'Mtype Based IfType Filtering Subview' allows you to filter interfaces of a device model.

You can access the 'Mtype Based IfType Filtering Subview' in the Information tab for a selected VNM model in the OneClick.

Mtype Iftype Map

The Mtype Iftype Map settings allow you to map the device model of the interfaces, which you want to filter and do not want to model. 

  • Mtype Value
    Specify the model type (MType) of the device model.
    For example: Rtr_Cisco Mtype value is 0x21000c
  • IfType Value 

    Specify the interfaces type (Iftype) values, which you do not want to model. The values must be comma (,) separated for multiple Iftype values.
    For example: The Iftype values for Ethernet interface (6) and Prop Virtual Interface (53) values are mentioned as 6,53 (refer to the screenshot)

Note: If these settings are done after the discovery of a device model, you must reconfigure the models to apply these settings.

CreateWALinkForPropVirtualInterface Attribute

The following attribute has been added to the VNM model type:

CreateWALinkForPropVirtualInterface

Type: Boolean

Default: False

Attribute ID: 0x1321b

You do not have a separate view for this attribute. Therefore, to view this attribute, navigate to the Component Details window of the VNM model type and click the Attributes tab.

You can set the attribute value to True to create a WA_Link connection between proprietary virtual interfaces. Previously discovered devices and connections are not affected by changing the value of this attribute. To view the changes, run the discovery again.

Was this helpful?

Please log in to post comments.

  1. JOSEPH ACKLEY
    2018-12-12 08:07

    The "Trap Management" subview section only discusses 3 parameters in this subview. There are 13 fields and 3 buttons in this subview.