Setting Up User and System Preferences
Depending on your system authority, Preferences page can either display user settings or a combination of user settings and system settings. One or more of these preference tabs appear when you open the Preferences page:
- User–All users can choose whether monitors and reports display local time or server time.
- Report–Network Administrators can specifying length of time Network Director reports are retained.
- General–Network Administrators can specifying a RingMaster URL.
- Monitoring–Network Administrators can change the polling interval for data collection for Monitor mode monitors. This page enables the internal processes used for data collection to be enabled or disabled. You can also specify database record retention periods on this tab.
- Fault–Network Administrators can enable or disable alarms. They can also set the retention period for alarms and the number of events per alarm.
This topic describes:
Accessing the Preferences page
To open the Preferences page, click the down arrow next to the System button in the Network Director banner and select Preferences as shown in Figure 1.
Figure 1: Accessing the Preferences Page

The Preferences page opens with User Preferences as the default tab.
Choosing Server Time or Local Time
All users can specify whether Network Director displays local time or the server’s time in monitors and reports on the User Preferences tab. The default setting is to display local time. To change the setting to display the server’s time:
- In the Preferences page, select Use Server Time from the list.
- Click OK to save your changes or click Cancel to close Preferences.
Specifying Search Preferences
Network Director indexes the device inventory data periodically to enable users to perform efficient searches. You can specify a time interval after which Network Director initiates the next indexing on the Search tab. You can also specify to stop indexing while devices are imported into Network Director. If you are running short of system memory, selecting this option can help save some memory and speed up the discovery and import of new devices. By default this option is selected and the search index update interval is set to 900 seconds.
Retaining Network Director Reports
By default, Network Director keeps reports for 30 days. However, Network Administrators can change the retention period from 0 to 365 days. To change the setting, move the slider right or left on the Report tab of Preferences to the new setting. Click OK to save the setting.
Linking to RingMaster
Sites with RingMaster licenses can launch the RingMaster application from within Network Director by supplying the RingMaster URL. After typing the URL on the General Settings tab of Preferences, you can click Launch RingMaster in Build mode to load RingMaster into the main page. To enable launching RingMaster from within Network Director, simply type in the URL and click OK to save the setting.
Changing Monitor Mode Settings
The Monitoring tab of Preferences consists of two sub-tabs:
- The Monitor Settings sub-tab enable you to change the default polling interval for data collection for Monitor mode monitors. You can also disable or re-enable the internal processes used for data collection on this sub-tab.
- The Client Session History sub-tab enables you to set the retention period for history records and the frequency that these records are checked for deletion.
This section describes:
- Disabling Data Collection for Monitors
- Changing the Polling Interval
- Specifying Database History Retention
Disabling Data Collection for Monitors
Network Director internally gathers data for monitors by using a set of data collector processes. You can disable these data collectors if they do not pertain to your installation. For example, if you do not use Virtual Chassis, you can disable the data collection processes used for Virtual Chassis.
The data collector processes are divided into the following categories:
- Client
- Equipment
- RF
- Traffic
One data collector can be used by multiple monitors. Likewise, some monitors can be supported by multiple data collectors. These data collectors are enabled by default. To ensure proper data collection, if Equipment data collectors are enabled, ensure the Traffic collector is also enabled.
To disable or re-enable a data collector:
- Determine which monitors are used by the data collectors.
Use Table 1 to determine the relationship
between the data collectors and the monitors.
Table 1: Monitor Mapping for Data Collectors
Monitor
Data Collector
Category
802.11 Packet Error
RFMonitorRadioStatsCollector
RF
AP Interference Source
RFMonitorIntSourcesCollector
RF
AP Status
EquipmentMonitorAPCollector
Equipment
Current Sessions
Client Monitor Collector and SessionCountCollector
Client
Error Trend
PortTrafficMonitorCollector
Traffic
Logical Interfaces
EquipmentMonitorLogicalInterfaceStatusCollector
Equipment
Find End Point
EquipmentMonitorEndPointCollector
Equipment
Percentage of Packets Retransmitted
RFMonitorRadioStatsCollector
RF
Port Status (physical)
EquipmentMonitorControllerCollector
Equipment
Radio Status
EquipmentMonitorAPCollector
Equipment
RF Neighborhood
RFMonitorRadioNeighborCollector
RF
RF Throughput or Packet Retransmitted
RFMonitorRadioStatsCollector
RF
Resource Utilization
EquipmentMonitorControllerCollector
Equipment
Session Trend
ClientMonitorCollector and SessionCountCollector
Client
Switch Status
EquipmentMonitorControllerCollector
Equipment
Traffic Trend
PortTrafficMonitorCollector
Traffic
Top Sessions by MAC Address
ClientMonitorCollector
Client
Top Users
ClientMonitorCollector
Client
Unicast vs Broadcast/Multicast
PortTrafficMonitorCollector
Traffic
Unicast vs Broadcast/Multicast Trend
PortTrafficMonitorCollector
Traffic
Virtual Chassis Topology
EquipmentMonitorVCStatsCollector and EquipmentMonitorVCCollector
Equipment
Virtual Chassis Protocol
EquipmentMonitorVCStatsCollector and EquipmentMonitorVCCollector
Equipment
Virtual Chassis Statistics
EquipmentMonitorVCStatsCollector and EquipmentMonitorVCCollector
Equipment
- Clear the check box to disable the collector or select to enable the collector.
- Click Save and Close to save the configuration and to close the window.
Changing the Polling Interval
The frequency that data is collected is determined by the polling interval. Table 2 shows the default polling intervals vary by data collector.
Table 2: Default Polling Intervals
Collector | Polling Interval |
|---|---|
ClientMonitorCollector | 10 minutes |
SessionCountCollector | 10 minutes |
EquipmentMonitorVCCollector | 30 minutes |
EquipmentMonitorVCStatsCollector | 30 minutes |
EquipmentMonitorLogicalInterfaceStatusCollector | 30 minutes |
EquipmentMonitorControllerCollector | 10 minutes |
EquipmentMonitorAPCollector | 10 minutes |
EquipmentMonitorEndPointCollector | 1440 minutes |
RFMonitorIntSourcesCollector | 15 minutes |
RFMonitorRadioNeighborCollector | 15 minutes |
RFMonitorStatsCollector | 10 minutes |
PortTrafficMonitorCollector | 10 minutes |
You can change the interval by:
- Selecting the polling interval for a data collector in the Monitor Settings table.
- Typing the new interval level in whole minutes. For example, do not specify 1.5 minutes. Recommended intervals are 5, 10, or 20 minutes.
- Clicking OK and Yes to verify the change to the configuration.
Specifying Database History Retention
To keep the database manageable, the system periodically checks the age of the records and retires those that have past an expiration date. By default, Network Director ages database records off at 90 days and runs a database cleanup every 6 hours.
Use the Client Session History sub-tab to change the default values:
- Select from the lists new values.
- Age of history records (in days) from 1 to 365 days.
- Cleanup job frequency (in hours) from 1 through 24 hours.
- Click OK to save the changes.
Changing Alarm Settings
Use Alarm Settings to enable individual alarms, set the retention period for alarms, and to specify the number of events to keep for each alarm. The Alarm Setup tab of Preferences has two sub-tabs:
- Alarms Settings, for enabling alarms and changing the severity setting for the alarm. All of the alarms on this page are preconfigured and enabled by default.
- Retention, for setting the retention period for alarms and for specifying the number of events to keep for each alarm.
This section describes:
- Changing the Severity of Individual Alarms
- Enabling Alarms
- Retaining Alarm History
- Specifying Event History
Changing the Severity of Individual Alarms
You can change the severity of the alarms to match your corporate procedures and guidelines. For example, at your company a DoS attack might be considered a critical alarm, but Network Director has a default severity for DoS attacks as a major alarm.
To change the severity of an alarm:
- Select the Severity in the specific alarm entry on the Alarm Setup page. A list of the severity levels appear.
- Select the new severity level for the alarm.
- Click OK and Yes to confirm the change to the severity setting.
Enabling Alarms
Ensure all devices are configured to send traps to Network Director. This task is performed for the devices in Deploy mode through Set SNMP Trap Configuration.
Use the Alarm Setup tab on the Alarm Settings page to disable and re-enable individual alarms or all alarms. Fault alarms are preconfigured and initially enabled. To enable or disable alarms:
- (Optional) Sort the alarms. By default, the list of alarms is sorted alphabetically within each category. You can also sort by description or alarm severity within a category by clicking a column heading.
- Review the alarms and either select the check box in the heading to select all of the alarms or select the check box for the individual alarms you want to enable. For a full description of each of the alarms, view Table 3.
- Click OK and Yes to verify the alarm change.
Table 3: Alarm Descriptions
Alarm Name | Description | Device Type |
|---|---|---|
AP and Radio (APAndRadio) | ||
AP License Limit Exceeded | Generated when the number of wireless LAN access points (WLAs) exceed the number of licenses configured on a wireless switch. The trap occurs when a wireless switch receives a packet from an inactive access point. The switch is unable to attach the access point without exceeding the maximum (licensed) number of active access points. | Wireless LAN controller |
AP Manager Changed Alarm | Generated when the access point’s secondary link becomes the primary link. | Wireless LAN controller |
AP Status Alarm | Generated when an access point changes state. | Wireless LAN controller |
AP Tunnel Limit Exceeded | Generated when the number of tunnels per access point are exceeded. This alarm is generated by the access point’s Primary Access Manager (PAM) when the access point rejects a tunnel creation request because it has already created the maximum number of tunnels it can support. | Wireless LAN controller |
M2U Conversion | Generated when multicast to unicast conversion is enabled on the access point, but cannot be performed. | Wireless LAN controllers |
Radio Channel Changed | Generated when autotune changes a radio's channel. | Wireless LAN controller |
Radio power changed | Generated when autotune changes a radio's power level. | Wireless LAN controller |
Radio Status Alarm | Generated when a radio changes state. It also contains aggregate information about the access point in operational state, its security level and service availability. | Wireless LAN controller |
WLC Tunnel Limit Exceeded | Generated when the wireless switch rejects a tunnel creation request because it has reached the maximum number of tunnels supported. When the trap event trpzWsTunnelLimitType equals the platform-tunnel-limit, the wireless switch has reached the maximum tunnel capacity. The actual tunnel limit varies by platform. When the trap trpzWsTunnelLimitType equals ap-ws-tunnel-limit, the wireless switch has reached the access point-to-switch tunnel’s limit. The value of that limit depends on the current situation of the wireless switch (mobility domain, network domain, network resiliency status). | Wireless LAN controller |
BFD | ||
BfdSessionDetectionTimeAlarm | Generated when the threshold value for detection time is set and the BFD session detection-time adapts to a value greater than the threshold. | EX Series Switch |
BfdSessionTxAlarm | Generated when the threshold value for transmit interval (in microseconds) is exceeded. | EX Series Switch |
BGP | ||
BgpM2BackwardTransitionAlarm | Generated when the BGP FSM moves from a higher-numbered state to a lower-numbered state. | EX Series Switch |
BgpM2EstablishedAlarm | Generated when the BGP Finite State Machine (FSM) enters the ESTABLISHED state. | EX Series Switch |
Chassis | ||
FanFailureAlarm | Generated when the specified cooling fan or impeller has failed (not spinning). | EX Series Switch |
FEBSwitchoverAlarm | Generated when the Forwarding Engine Board (FEB) has switched over. | EX Series Switch |
FRUCheckAlarm | Generated when the device has detected that a Field Replaceable Unit (FRU), has some operational errors and has gone into check state. | EX Series Switch |
FRUFailedAlarm | Generated when a FRU has failed. | EX Series Switch |
FRUInsertionAlarm | Generated when the system detects that the specified FRU is inserted into the chassis. | EX Series Switch |
FRUOfflineAlarm | Generated when the specified FRU goes offline. | EX Series Switch |
FRUOnlineAlarm | Generated when the specified FRU goes online. | EX Series Switch |
FRUPowerOffAlarm | Generated when the specified FRU is powered off. | EX Series Switch |
FRUPowerOnAlarm | Generated when the specified FRU is powered on. | EX Series Switch |
FRURemovalAlarm | Generated when the system detects that the specified FRU was removed from the chassis. | EX Series Switch |
HardDiskFailedAlarm | Generated when the hard disk for the specified routing engine has failed. | EX Series Switch |
HardDiskMissingAlarm | Generated when the hard disk in the specified routing engine is missing from the boot device list. | EX Series Switch |
PowerSupplyFailureAlarm | Generated when the specified power supply has failed (bad DC output). | EX Series Switch |
RedundancySwitchOverAlarm | Generated when a Graceful Routing Engine Switchover (GRES) occurs on a switch with dual Routing Engines or on a Virtual Chassis. | EX Series Switch |
TemperatureAlarm | Generated when the device has over heated. | EX Series Switch |
Client and User Session (ClientAndUserSession) | ||
Client Association Failure | Generated when a client is unable to associate with an access point. | Wireless LAN controller |
Client Authentication Failure | Generated when a client is unable to authenticate. | Wireless LAN controller |
Client Authorization Failure | Generated when a client fails authorization. | Wireless LAN controller |
Client Authorization Succeeded | Generated when a client authorizes. | Wireless LAN controller |
Client Cleared | Generated when a client session is cleared. | Wireless LAN controller |
Client Connectivity | Generated when a client session connects. | Wireless LAN controller |
Client DeAssociated | Generated when a client de-association occurs. | Wireless LAN controller |
Client DeAuthenticated | Generated when a client de-authenticates. | Wireless LAN controller |
Client Disconnected | Generated when a client session disconnects administratively. | Wireless LAN controller |
Client dot1x Failure | Generated when a client fails 802.1X. | Wireless LAN controller |
Client Dynamic Authorization Changed | Generated when the authorization attributes for a user are dynamically changed by a authorized dynamic authorization client. | Wireless LAN controller |
Client IP Address Changed | Generated when a client’s IP address changes, normally when the client first connects to the network. | Wireless LAN controller |
Client Roamed | Generated when a client roams from one location to another. | Wireless LAN controller |
Dynamic Authorization Client Alarm | Generated when the authorization attributes for a user are dynamically changed by an authorized dynamic authorization client. | Wireless LAN controller |
ClusterAndMoDo | ||
Cluster Sync Failure | Generated when the cluster configuration failed to apply. | Wireless LAN controller |
Mobility Domain Failback | Generated when the mobility domain fails back to the primary seed. | Wireless LAN controller |
Mobility Domain Failover | Generated when the mobility domain fails back to the secondary seed. | Wireless LAN controller |
Mobility Domain Join | Generated when a member joins the mobility domain. | Wireless LAN controller |
Mobility Domain Resiliency Status | Generated when a mobility domain seed changes resilient capacity. | Wireless LAN controller |
Mobility Domain Timeout | Generated when a mobility domain member times out. | Wireless LAN controller |
Configuration (Config) | ||
CmCfgChangeAlarm | Generated when the jnxCMCfgChgEventTable records a configuration management event. | EX Series Switch and wireless LAN controller |
CMRescueChangeAlarm | Generated when a change is made to the rescue configuration. | EX Series Switch and wireless LAN controller |
Core and controllers (CoreAndControllers) | ||
Device alarm | Generated when the device status changes (up to down or down to up). | EX Series Switch and wireless LAN controller |
CoS | ||
CoSAlmostOutOfDedicatedQueuesAlarm | Generated when only 10% of CoS queues are available. | EX Series Switch |
CoSOutOfDedicatedQueuesAlarm | Generated when there are no more available dedicated CoS queues. | EX Series Switch |
DHCP | ||
JdhcpLocalServerDupClientAlarm | Generated when a DHCP client is detected changing interfaces. | EX Series Switch |
JdhcpLocalServerlfLimitExceededAlarm | Generated when the client limit is reached on an interface. | EX Series Switch |
Jdhcpv6LocalServerLimitExceededAlarm | Generated when the client limit is reached on an interface for DHCPv6. | EX Series Switch |
DOM | ||
DomAlertSetAlarm | Generated when an interface detects Digital Optical Monitor (DOM) alarm conditions. | EX Series Switch |
Flow Collection (FlowCollection) | ||
CollFlowOverloadAlarm | Generated when a collector PIC detects a hard or soft flow overload. | EX Series Switch |
CollFtpSwitchOverAlarm | Generated when an FTP server switchover occurs. | EX Series Switch |
CollMemoryUnavailableAlarm | Generated when a PIC is out of memory or the memory is unavailable. | EX Series Switch |
CollUnavailableDestAlarm | Generated when a file transfer destination is unavailable. | EX Series Switch |
CollUnsuccessfulTransferAlarm | Generated when a collector file is unable to transfer because the destination is unavailable. | EX Series Switch |
General | ||
Authentication Failure Alarm | Generated when a protocol message is received that is not properly authenticated. | EX Series Switch and wireless LAN controller |
Cold Start Alarm | Generated when a device is re-initializing and its configuration might have changed. | EX Series Switch and wireless LAN controller |
Link Down Alarm | Generated when a link is down. The trap is generated when the ifOperStatus object for a communication link is about to enter the down state from another state other than notPresent. This other state is indicated by the included value of ifOperStatus. | EX Series Switch and wireless LAN controller |
Link Up Alarm | Generated when a link comes up that was previously in the down state. The trap is generated when the ifOperStatus object for a communication link left the down state and transitioned into another state other than notPresent state. This other state is indicated by the included value of ifOperStatus. | EX Series Switch and wireless LAN controller |
Warm Start Alarm | Generated when a device is re-initializing and its configuration has not changed. | EX Series Switch and wireless LAN controller |
Generic (GenericEvent) | ||
GenericEventTrapAlarm | Generated by an Op script or event policies. This notification can include one or more attribute-value pairs. The pairs are identified by the jnxEventAvAttribute and jnxEventAvValue objects. | EX Series Switch |
L2ALD | ||
L2aldGlobalMacLimitAlarm | Generated when the MAC limit is reached for the entire system. This trap is sent only once, when the limit is reached. | EX Series Switch |
L2aldInterfaceMacLimitAlarm | Generated when the given interface reaches the MAC limit (jnxl2aldInterfaceMacLimit). | EX Series Switch |
L2aldRoutingInstMacLimitAlarm | Generated when the MAC limit is reached for a given routing instance (jnxl2aldRoutingInst). | EX Series Switch |
L2CP | ||
LacpTimeOutAlarm | Generated when LACP has timed out. | EX Series Switch |
PortBpduErrorStatusChangeTrapAlarm | Generated when the port’s BPDU error state (no-error or detected) changes. | EX Series Switch |
PortLoopProtectStateChangeTrapAlarm | Generated when the port’s loop-protect state (no-error or loop-prevented) changes. | EX Series Switch |
PortRootProtectStateChangeTrapAlarm | Generated when the port’s root-protect state (no-error or root-prevented) changes. | EX Series Switch |
MAC Forwarding Database (MACFDB) | ||
MacChangedNotificationAlarm | Generated when MAC addresses of the monitored devices are learned or removed from the forwarding database (FDB). | EX Series Switch and wireless LAN controller |
Misc. | ||
Counter Measures Alarm | Generated when counter measures are started against a rogue. | Wireless LAN controller |
Device Configuration Saved | Generated when the running configuration of the switch is written to the configuration file. | Wireless LAN controller |
Multimedia Call Failure | Generated when a multimedia call fails. | Wireless LAN controller |
PoE failure | Generated when Power over Ethernet (PoE) has failed on the indicated port. | EX Series Switch |
Passive Monitoring (PassiveMonitoring) | ||
PMonOverloadSetAlarm | Generated when an overload condition is detected on a Passive Monitoring Interface. | EX Series Switch |
Ping | ||
PingEgressJitterThresholdExceededAlarm | Generated when egress time jitter (jnxPingMaxEgressUs minus jnxPingResultsMinEgressUs) exceeds the configured threshold (jnxPingCtlEgressJitterThreshold) causing the egressJitterThreshold bit to be set. | EX Series Switch and wireless LAN controller |
PingEgressStdDevThresholdExceededAlarm | Generated when the standard deviation of the egress time (jnxPingResultsStddevEgressUs) exceeds the configured threshold (jnxPingCtlEgressTimeThreshold) and the causes the egress bit to be set. | EX Series Switch and wireless LAN controller |
PingEgressThresholdExceededAlarm | Generated when the egress time (jnxPingResultsStdevEgressUs) exceeds the configured threshold (jnxPingCtlEgressTimeThreshold) and the egress threshold bit is set in jnxPingCtlTrapGeneration. | EX Series Switch and wireless LAN controller |
PingIngressJitterThresholdExceededAlarm | Generated when ingress time jitter (jnxPingResultsMaxIngressUs minus jnxPingResultsMinIngressUs) exceeds the configured threshold (jnxPingCtlIngressJitterThreshold) and the ingressJitterThreshold bit is set in jnxPingCtlTrapGeneration. | EX Series Switch and wireless LAN controller |
PingIngressStddevThresholdExceededAlarm | Generated when the standard deviation of the ingress time (jnxPingResultsStdDevIngressUs) exceeds the configured threshold (jnxPingCtlIngressStddevThreshold) and the ingress StdDevThreshold bit is set in jnxPingCtlTrapGeneration. | EX Series Switch and wireless LAN controller |
PingIngressThresholdExceededAlarm | Generated when the ingress time jitter (jnxPingResultsIngressUs) exceeds the configured threshold (jnxPingCtlIngressTimeThreshold) and the ingress threshold bit (jnxPingIngressThresholdExceeded) is set in jnxPingCtlTrapGeneration. | EX Series Switch and wireless LAN controller |
PingRttJitterThresholdExceededAlarm | Generated when the round trip time jitter (jnxPingResultsMaxRttUs minus jnxPingResultsMinRttUs) exceeds the configured threshold (jnxPingCtlRttJitterThreshold) and the rttJitterThreshold bit is set in jnxPingCtlTrapGeneration. | EX Series Switch and wireless LAN controller |
PingRttStdDevThresholdExceededAlarm | Generated when the standard deviation of the round trip time (jnxPingResultsStdDevRttUs) exceeds the configured threshold (jnxPingCtlRTTStdDev) and the rttStdDevThreshold bit is set in jnxPingCtlTrapGeneration. | EX Series Switch and wireless LAN controller |
PingRttThresholdExceededAlarm | Generated when the round trip time (jnxPingCtlRttThreshold) exceeds the configured threshold (jnxPingCtlRttThreshold) and the rttThreshold bit is set in jnxPingCtlTrapGeneration. | EX Series Switch and wireless LAN controller |
RF Detect (RFDETECT) | ||
Adhoc user detected | Generated when RF detection sweep finds an ad hoc user or if previously found ad hoc user disappears. | Wireless LAN controller |
Client Blacklisted | Generated when an association, re-association, or de-association request is detected from a blacklisted transmitter. | Wireless LAN controller |
DoS Attack Detected | Generated when RF detection finds a denial of service (DoS) occurring. | Wireless LAN controller |
DoS Port Detected | Generated when RF detection finds a denial of service (DoS) occurring. This trap collects port and access point information instead of information about the listener. | Wireless LAN controller |
RF Interference Detected | Generated when a new noise source appears. A given combination of noise source ID, listener, and channel triggers this trap. It is normally not triggered more than once every 15 minutes. | Wireless LAN controller |
RF Detect Classification Changed | Generated when the RF detection classification rules change. | Wireless LAN controller |
Rogue Device Detected | Generated when RF detection finds a rogue device. | Wireless LAN controller |
Rogue Wired WLA Client Detected | Generated when a client is detected that connected through a rogue access point that is attached to a wired port. | Wireless LAN controller |
Rogue WLA Client Detected | Generated when RF detection finds a suspect device. | Wireless LAN controller |
Rogue WLA Interference Detected | Generated when RF detection finds an interfering rogue access point. | Wireless LAN controller |
Spoofed MAC Detected | Generated when RF detection finds an access point using the MAC of the listener. | Wireless LAN controller |
Spoofed SSID Detected | Generated when RF detection finds an access point using the SSID of the listener, and the access point is not in the mobility domain. | Wireless LAN controller |
Suspected Device Detected | Generated when RF detection finds a suspect device. | Wireless LAN controller |
Unauthorized AP Detected | Generated when RF detection discovers an unauthorized access point being used. | Wireless LAN controller |
Unauthorized OUI Detected | Generated when RF detection finds an unauthorized OUI being used. | Wireless LAN controller |
Unauthorized SSID Detected | Generated when RF detection finds an unauthorized SSID being used. | Wireless LAN controller |
RMON | ||
RmonAlarmGetFailureAlarm | Generated when a GET request for an alarm variable returns an error. The specific error is identified by a varbind in jnxRmonAlarmGetFailReason. | EX Series Switch |
SONET | ||
SonetAlarmSetAlarm | Generated when there is a notification of a recently set SONET or SDH alarm on an interface. | EX Series Switch |
SONET APS (SONETAPS) | ||
APSEventChannelMismatchAlarm | Generated when the value of an instance of apsStatusChannelMismatches increments. | EX Series Switch |
APSEventFEPLFAlarm | Generated when the value of an instance of apsEventFEPLFs increments. | EX Series Switch |
APSEventModeMismatchAlarm | Generated when the value of an instance of apsEventModeMismatch increments. | EX Series Switch |
APSEventPSBFAlarm | Generated when the value of an instance of apsStatusPSBFs increments. | EX Series Switch |
APSEventSwitchoverAlarm | Generated when the value of an instance of apChanStatusSwitchover increments. | EX Series Switch |
Virtual Chassis (VirtualChassis) | ||
VccpMemberDownAlarm | Generated when a member is about to enter the down state. | EX Series Switch |
VccpMemberUpAlarm | Generated when a member has completed transition from the down state to another state. | EX Series Switch |
VccpPortDownAlarm | Generated when one of the member’s communication links is about to enter the down state. | EX Series Switch |
VccpPortUpAlarm | Generated when one of the member’s communication links has completed transition from the down state to another state. | EX Series Switch |
VNetwork | ||
HostConnectivityLostAlarm | Generated when all the uplink ports of a virtual switch residing in a host loses network connectivity. | Host |
HostNetworkRedundancyLostAlarm | Generated when some uplink ports of a virtual switch residing in a host loses network connectivity. It indicates that there are one or more ports that still has network connectivity. | Host |
VNetworkConnectivityLostAlarm | Generated when Network Director loses network connectivity with the vCenter server. | Virtual Network |
Retaining Alarm History
Use the Retention tab on the Alarm Settings page to specify the number of days to keep alarm history. The default retention time is 120 days; but you can specify a period of 7 through 1000 days. Specifying a longer retention time consumes more database resources. To change the alarm retention duration, type a new value and click OK and Yes to verify the change.
Specifying Event History
The Events per Alarm field enables you specify the number of event entries that are kept in the alarm history. This field is found on the Retention tab on the Alarm Settings page. The default setting for events is 20. To change the setting, type a new value and click OK and Yes to verify the change.

