Amid increasingly peripheral network deployments, the need for ease of management well defined and a monitoring system has been existing for some of it's time. To meet this need a network management system, the Simple Network Management Protocol was incorporated and defined by the IETF.
SNMP is based on a model consisting of an SNMP manager, SNMP agent, SNMP and management information database managed. An SNMP agent sets the device management data managed as variables to the SNMP manager.
Now let's examine the NetScaler ADC. The SNMP agent on NetScaler ADC generates asynchronous notification of events called traps. NetScaler generates corresponding interrupt message whenever certain events occur.
The device NetScaler provides a set of state entities called SNMP alarms. When one of the alarm conditions are met, the NetScaler generates SNMP trap messages that are sent to the configured SNMP manager.
Command Center is a manageability and monitoring solution well composed offered by Citrix. It can manage all Citrix networking devices like NetScaler ADC, repeater devices, AGED, Bridge Cloud and SDX.
When Command Center (CC) is configured as an SNMP manager, the device managed as NetScaler ADC, the generated traps roads, the Command Center server. Every single trap routed CC is registered as an individual event in the Command Center server. CC stores this event for six months and only displays the last 10,000 events.
Every time a trap is received at the command center and the event, an alarm is generated. To understand this better, consider an example. Say, Command Center becomes a trap for an Entity class down to the vip123 virtual server on the device NetScaler 10.102.60.5.
An event and an alarm will be generated for the virtual server with vip123 category Down under Entity 10.102.60.5 device. Next vip123 time trap Unit downward is received by the control center of 10.102.60.5 device, a special event will be generated. But under the alarms, only the alarm previously generated will be updated with the latest retail vip123. At the same time, the alarm will keep the events previously received under vip123 that history.
In this way, you will always find more events for a specific device alarms. Both alarms and events are associated with a default severity level.
Now this alarm / event boils down to what these alarms notify the Command Center administrator. Based on the default traps severity levels, the administrator will be notified if it is a critical, major, minor, warning, info or alarm clear.
If an alarm Entity down is generated, it is deleted when corresponding Entity up trap is received at the CC server. If a trap Entity down is not generated for 24 hours, the alarm light will be removed from the system.
For all these alarms, depending on your specific criteria, you can also create an email notification system by creating an alarm trigger.
With Events, alarms and alarm triggers, the control center has a robust manageability and monitoring solution that gives the right to notification at the right time to the right person!
0 Komentar