Q: Why is the
"Send Mail" action not working?
: The mail server credentials might be incorrect or mail server might not be
accessible from Command Center.
Action : Check
the mail server credentials and verify that the mail server is accessible from
command center server. If the mail server credentials are not correct, edit the
Administration > Mail Server Settings .
You can refer to
the exception logged under
Example of log
entry for this exception:
Exception while sending mail notification. Sending failed;
nested exception is:
class javax.mail.MessagingException: Could not connect to SMTP host: 10.102.173.25, port: 25;
nested exception is:
java.net.ConnectException: Connection refused: connect
Invalid HostName or Port, unable to connect the mail server
: The Events/Alarms fields are not configured correctly.
if Event/Alarm fields are configured correctly. The Message field, should match
or be a part of the message of any incoming Event/Alarm.
Example of log
entry for this exception:
Q: Can I keep a
historical log of SNMP alarms and events in Command Center ?
A: Currently, only
10000 events are displayed, due to user-interface restrictions, but, by
default, the events/alarms from the past 6 months are stored in the database.
Q: Command Center is
not receiving the traps sent by a device. What are the possible causes?
A: The possible
reasons for not receiving traps could be:
If you enable firewall on Command Center server, it does not receive the traps
SNMP port is
being used by some other application in the Command Center server system.
are set to suppress the action.
Scope is set for the device.
set with incorrect message fields.
alarm age set to a high value.
Center is installed on a Linux server, the iptable configuration might cause
filtering of SNMP packets.
unmanaged devices are not processed by Command Center.
Trap port has been changed by the administrator under Administration >
Settings > Trap Forward Settings.
Q: Do I need to
specifically enable SNMP on Command Center? if yes, how can I do so?
A: You need not enable
SNMP. It is already running on port 8161. When the Command Center service is
running, Command Center behaves as an SNMP agent on port 8161, and any SNMP
manager can contact Command Center through this port.
Q: Can I set triggers
for all of the devices?
A: Yes. In theAdd Filters window,
field empty. All the devices discovered are then selected.
Q: Alarm Triggers
actions are not being initiated for the generic category of alarms.
A: Since Alarms are
not updated for generic traps, such as reboot, you have to manually clear the
alarm to reenable the alarm trigger action, or you have to create triggers for
the generic category of events.
Q: Syslogs and
AppFirewall reports are not generated. What are the possible causes?
- Syslog settings on the
NetScaler are not properly configured for Command Center to receive the syslog
- Syslog port 514 is
occupied by other application.
- AppFirewall related
syslogs are not generated for the ICA type for a specified time period.
Q: Since all traps are
sent to both the Command Center agent and the main Command Center, does the
Command Center agent ignore these or are they sent to the database through the
A: Traps are handled
only by the Command Center server, which adds its IP address as a trap
destination on the NetScaler device during NetScaler device discovery.
Q: How can I
customize the purge interval?
A: You can specify
the interval at which Command Center should purge syslog data. By default,
Command Center stores syslog messages for the last 90 days. To customize the
purge interval, navigate to Administration > Server Settingsand specify the
number of days in theSyslog Clean interval (in days) field. Only the records
older than the number of days that you specify are purged. For example, if you
specify as 45 days, Command Center purges syslog messages that are older than
Q: I am able to view
unwanted IPs in Failure Objects.
A: The unwanted IP
addresses are from AppFirewall Client IP. Create a filter to suppress
Q: Is it possible to
export data from Command Center for Syslogs, Appfirewall and AGEE logs?
Q: Why am I
not able to receive the SNMP traps from the device?
A: If the
wrapper.log file contains the following entry:
"WARNING : Traps
cannot be received on port : 162", failure to receive the traps could have
the following possible causes:
Cause1 : If any other SNMP trap service is running on port 162, which is
receiving the traps, Command Center might not be able to receive the SNMP
2: Traps from unmanaged devices are not processed by Command Center.
Check if to see if the trap destination and port are correctly configured on
Q: Why am I not able
to view the old events?
Explanation: By default, Command Center does not display the entire
database. The default is a maximum 10,000 events, no older than 6 months.
1: Command Center displays only 10,000 events in client GUI.
can change this setting by modifying the value of the
EVENT_WINDOW_SIZE parameter in the NmsProcessesBE.conf file,
which is in the <CC_HOME>/conf directory.
2: Events older than 6 months are deleted.
Action : By
default, the interval for cleaning the events is 6 months. You can change the
interval by modifying the value of the
CLEAN_EVENT_INTERVAL parameter in NmsProcessesBE.conf file,
which is in the <CC_HOME>/conf.
Q: I am not able to
view "Available Failed Objects" for a particular trap category. How do I
troubleshoot the problem?
A: Explanation: When
Command Center receives a trap, the failed objects become persistent in the
Command Center database. The "Available Failed Objects" popup window displays
Cause: If Command Center has not received a trap for that category even
once, you cannot see any failed objects for that particular trap.
can edit the field manually
entity-related event/alarm,(entityup/down, entityNameChanged, or entityofs),
configure the failed object in the event/alarm trigger:
$vserver_name OR $service_name OR
For a Threshold
- Rx Average
current client connections:CC_Vsvr(10.102.31.110:8443)