1. DOMSA01.exe Driver
2. EventType601-61.txt File Contents

EventType601-61.txt Driver File Contents (DOMSA01.exe)

EventCategoryName,EventTypeName,Description
"Software","System Up Mssg from IT Assistant","When IT Assistant has detected a system as down, when the system comes back up, IT Assistant will emit this event upon a discovery or status round."
"Software","System Down Mssg from IT Assistant","When IT Assistant cannot communicate with a discovered system, it will emit this event upon a discovery or status round. This occurs only once."
"Network","NIC Failover Event","This trap is generated to indicate that adapter Fail-Over event has occured."
"Cluster","Generic SNMP Trap","Generic SNMP trap generated by NuView ClusterX applications and services.\nVarbind #1:  Custom string.\nVariables:\n  1: clxTrapDataString01\n     Syntax=Display String\n     Descr=Custom string 1 (Varbind #1) for NuView ClusterX trap."
"Cluster","Failure of a node in an MSCS cluster","This trap is sent when ClusterX detects the failure of a node in an MSCS cluster. The trap identifies the cluster,the name of the node that failed \nVariables:\n  1: clxTrapDataClusterName\n     Syntax=Display String\n     Descr=Name of the MSCS Cluster. \n  2: clxTrapDataNodeName\n     Syntax=Display String\n     Descr=Name of the MSCS Node. "
"Cluster","Failure of an MSCS cluster","This trap is sent when ClusterX detects the failure of an MSCS cluster. The trap identifies the name of the failed cluster \nVariables:\n  1: clxTrapDataClusterName\n     Syntax=Display String\n     Descr=Name of the MSCS Cluster. "
"Cluster","Failure of a resource detected","This trap is sent when ClusterX detects the failure of a resource on an MSCS cluster. The trap identifies the names of the cluster, node and resource \nVariables:\n  1: clxTrapDataClusterName\n     Syntax=Display String\n     Descr=Name of the MSCS Cluster. \n  2: clxTrapDataNodeName\n     Syntax=Display String\n     Descr=Name of the MSCS Node. \n  3: clxTrapDataResourceName\n     Syntax=Display String\n     Descr=Name of the MSCS Resource. "
"Cluster","Detection of node joining or rejoining cluster","This trap is sent when ClusterX detects that node has joined or rejoined an MSCS cluster. The trap identifes the name of the cluster and the name of the node that joined.\nVariables:\n  1: clxTrapDataClusterName\n     Syntax=Display String\n     Descr=Name of the MSCS Cluster. \n  2: clxTrapDataNodeName\n     Syntax=Display String\n     Descr=Name of the MSCS Node. "
"Cluster","Detection of a failure of the private or public cluster interconnects","This trap is sent when ClusterX detects the failure of the private or public cluster interconnects on an MSCS cluster.\nVariables:\n  1: clxTrapDataClusterName\n     Syntax=Display String\n     Descr=Name of the MSCS Cluster. \n  2: clxTrapDataNetworkName\n     Syntax=Display String\n     Descr=Network Name"
"Cluster","Detected the cluster service wrote a normal event to the NT event log","This trap is generated when ClusterX detects that the Cluster Service has written a new entry in the Windows NT Event Log on a managed cluster.It contains the information about cluster service log\nVariables:\n  1: clxTrapEventDate\n     Syntax=Display String\n     Descr=Date of the Event created in NT event log file \n  2: clxTrapEventTime\n     Syntax=Display String\n     Descr=Time of the Event created in NT event log file \n  3: clxTrapEventSource\n     Syntax=Display String\n     Descr=Source of the Event created in NT event log file \n  4: clxTrapEventCategory\n     Syntax=Display String\n     Descr=Category of the Event created in NT event log file \n  5: clxTrapEventID\n     Syntax=Display String\n     Descr=ID of the Event created in NT event log file\n  6: clxTrapEventUser\n     Syntax=Display String\n     Descr=User which created the event in NT event log file \n  7: clxTrapEventComputer\n     Syntax=Display String\n     Descr=Computer which created Event in NT event log file"
"Cluster","Detected the cluster service wrote a warning event to the NT event log","This trap is generated when ClusterX detects that the Cluster Service has written a new entry in the Windows NT Event Log on a managed cluster.It contains the information about cluster service log\nVariables:\n  1: clxTrapEventDate\n     Syntax=Display String\n     Descr=Date of the Event created in NT event log file \n  2: clxTrapEventTime\n     Syntax=Display String\n     Descr=Time of the Event created in NT event log file \n  3: clxTrapEventSource\n     Syntax=Display String\n     Descr=Source of the Event created in NT event log file \n  4: clxTrapEventCategory\n     Syntax=Display String\n     Descr=Category of the Event created in NT event log file \n  5: clxTrapEventID\n     Syntax=Display String\n     Descr=ID of the Event created in NT event log file\n  6: clxTrapEventUser\n     Syntax=Display String\n     Descr=User which created the event in NT event log file \n  7: clxTrapEventComputer\n     Syntax=Display String\n     Descr=Computer which created Event in NT event log file"
"Cluster","Detected the cluster service wrote a critical event to the NT event log","This trap is generated when ClusterX detects that the Cluster Service has written a new entry in the Windows NT Event Log on a managed cluster.It contains the information about cluster service log\nVariables:\n  1: clxTrapEventDate\n     Syntax=Display String\n     Descr=Date of the Event created in NT event log file \n  2: clxTrapEventTime\n     Syntax=Display String\n     Descr=Time of the Event created in NT event log file \n  3: clxTrapEventSource\n     Syntax=Display String\n     Descr=Source of the Event created in NT event log file \n  4: clxTrapEventCategory\n     Syntax=Display String\n     Descr=Category of the Event created in NT event log file \n  5: clxTrapEventID\n     Syntax=Display String\n     Descr=ID of the Event created in NT event log file\n  6: clxTrapEventUser\n     Syntax=Display String\n     Descr=User which created the event in NT event log file \n  7: clxTrapEventComputer\n     Syntax=Display String\n     Descr=Computer which created Event in NT event log file"
"Cluster","Application failure detected","This trap is sent when ClusterX detects the failure of an application on a monitored node.\nVarbind #1: Cluster Name\nVarbind #2: Node Name\nVarbind #3: Application Name\nVarbind #4: Application Failure Reason\nVarbind #5: Application Failure Action"
"Cluster","WLBS has written an informational entry in the Windows NT Event Log","This trap is generated when ClusterX detects that WLBS has written an informational entry in the Windows NT Event Log on a managed cluster.\nVarbind #1: Event Creation Date\nVarbind #2: Event Creation Time\nVarbind #3: Event Source\nVarbind #4: Event Category\nVarbind #5: Event ID\nVarbind #6: Event Creation User\nVarbind #7: Event Creation Computer"
"Cluster","WLBS has written a warning entry in the Windows NT Event Log","This trap is generated when ClusterX detects that WLBS has written a warning entry in the Windows NT Event Log on a managed cluster.\nVarbind #1: Event Creation Date\nVarbind #2: Event Creation Time\nVarbind #3: Event Source\nVarbind #4: Event Category\nVarbind #5: Event ID\nVarbind #6: Event Creation User\nVarbind #7: Event Creation Computer"
"Cluster","WLBS has written an error entry in the Windows NT Event Log","This trap is generated when ClusterX detects that WLBS has written an error entry in the Windows NT Event Log on a managed cluster.\nVarbind #1: Event Creation Date\nVarbind #2: Event Creation Time\nVarbind #3: Event Source\nVarbind #4: Event Category\nVarbind #5: Event ID\nVarbind #6: Event Creation User\nVarbind #7: Event Creation Computer"
"Cluster","WLBS cluster operation control has been suspended","This trap is sent when ClusterX detects that WLBS cluster operation control has been suspended.\nVarbind #1: Cluster Name\nVarbind #2: Node Name"
"Cluster","WLBS cluster operation control has been resumed","This trap is sent when ClusterX detects that WLBS cluster operation control has been resumed.\nVarbind #1: Cluster Name\nVarbind #2: Node Name"
"Cluster","WLBS cluster operations have started","This trap is sent when ClusterX detects that WLBS cluster operations have started.\nVarbind #1: Cluster Name\nVarbind #2: Node Name"
"Cluster","WLBS cluster operations have stopped","This trap is sent when ClusterX detects that WLBS cluster operations have stopped.\nVarbind #1: Cluster Name\nVarbind #2: Node Name"
"Cluster","WLBS cluster operations have started draining","This trap is sent when ClusterX detects that WLBS cluster operations have started draining; once drained, cluster operations will stop.\nVarbind #1: Cluster Name\nVarbind #2: Node Name"
"Cluster","Node in a WLBS cluster has converged","This trap is sent when ClusterX detects that a node in a WLBS cluster has converged.\nVarbind #1: Cluster Name\nVarbind #2: Node Name"
"Cluster","WLBS traffic handling for the rule containing the specified port number has been enabled","This trap is sent when ClusterX detects that WLBS traffic handling for the rule containing the specified port number has been enabled.\nVarbind #1: Cluster Name\nVarbind #2: Node Name\nVarbind #3: Port Number or 'ALL'"
"Cluster","WLBS traffic handling for the rule containing the specified port number has been disabled for ALL traffic","This trap is sent when ClusterX detects that WLBS traffic handling for the rule containing the specified port number has been disabled for ALL traffic.\nVarbind #1: Cluster Name\nVarbind #2: Node Name\nVarbind #3: Port Number or 'ALL'"
"Cluster","WLBS traffic handling for the rule containing the specified port number has been disabled for NEW traffic","This trap is sent when ClusterX detects that WLBS traffic handling for the rule containing the specified port number has been disabled for NEW traffic.\nVarbind #1: Cluster Name\nVarbind #2: Node Name\nVarbind #3: Port Number or 'ALL'"
"Cluster","Application has come on line on a monitored node","This trap is sent when ClusterX detects that an application has come on line on a monitored node.\nVarbind #1: Cluster Name\nVarbind #2: Node Name\nVarbind #3: Application Name\nVarbind #4: Action Taken"
"Cluster","WLBS cluster parameters have been reloaded from the registry","ClusterX detects that WLBS cluster parameters have been reloaded from the registry.\nVarbind #1: Cluster Name\nVarbind #2: Node Name"
"Power","Dell AC Cord No Power Non-redundant","Dell AC Cord No Power Non-redundant"
"Power","Dell AC Cord Normal","Dell AC Cord Normal"
"Power","Dell AC Cord Failure","Dell AC Cord Failure"
"Operating System","SNMP Shutdown","A shutdown trap signifies that the sending protocol entity is stopped."
"Other","DRSC Test TRAP Event","The DRSC generated a test trap event in response to a user request.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC Authentication Error","DRSC Authentication Failures during a time period have Exceeded a Threshold.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC Lost Communication with ESM","DRSC cannot communicate with the baseboard management controller (ESM).\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC Communication with ESM is OK","DRSC is communicating normally with the baseboard management controller (ESM).\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC Detected System Powered-Off","The DRSC has detected a System power state change to powered-off.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC Detected System Powered-On","The DRSC has detected a system power state change to powered-on.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC Detected Watchdog Expired","The DRSC has detected that the system watchdog has expired indicating a system hang.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data." 
"Power","DRSC Battery Charge Low","The DRSC Battery charge is below 25% indicating that the battery may only be able to power the DRSC for 8-10 minutes.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Environmental","DRSC Temperature Normal","The DRSC Temperature probe has retured to a normal value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Environmental","DRSC Temperature Warning","The DRSC Temperature probe has detected a Warning value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Environmental","DRSC Temperature Failure","The DRSC Temperature probe has detected a failure (or critical) value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Power","DRSC Voltage Normal","A DRSC voltage has returned to a normal value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Power","DRSC Battery Warning","A DRSC voltage probe has detected a warning value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Power","DRSC Voltage Failure","A DRSC voltage probe has detected a failure (or critical) value.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC System Event Log Warning","The DRSC has detected a new event in the System Event Log with Severity.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","DRSC System Event Log Critical","The DRSC has detected a new event in the System Event Log with Severity.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","System Event Log 80% Full","System Event Log 80% Full.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","System Event Log 90% Full","System Event Log 90% Full.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Other","System Event Log 100% Full","System Event Log 100% Full.\nVariables:\n1: alertSystem\n\tName of the system generating the alert.\n2: alertTableIndexOID\n\tOID for the index attribute in the table that contains the object causing the alert. This value can be used to uniquely identify the object causing the alert and to correlate different alerts caused by an object. If not applicable, the value will be 0.0.\n3: alertMessage\n\tMessage describing the alert.\n4: alertCurrentStatus\n\tCurrent status of object causing the alert.\n5: alertPreviousStatus\n\tPrevious status of object causing the alert.\n6: alertData\n\tAlert data."
"Storage","Logical drive background initialization started","Logical drive background initialization started.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated.\n\t2: virtualDiskNameEv\n\tSyntax=Display String\n\tDescr=Virtual Disk for which trap is generated."
"Storage","Logical drive background initialization stopped","Logical drive background initialization stopped.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated.\n\t2: virtualDiskNameEv\n\tSyntax=Display String\n\tDescr=Virtual Disk for which trap is generated."
"Storage","Logical drive background initialization paused","Logical drive background initialization paused.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated.\n\t2: virtualDiskNameEv\n\tSyntax=Display String\n\tDescr=Virtual Disk for which trap is generated."
"Storage","Logical drive background initialization restarted","Logical drive background initialization restarted.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated.\n\t2: virtualDiskNameEv\n\tSyntax=Display String\n\tDescr=Virtual Disk for which trap is generated."
"Storage","Logical drive background initialization failed","Logical drive background initialization failed.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated.\n\t2: virtualDiskNameEv\n\tSyntax=Display String\n\tDescr=Virtual Disk for which trap is generated."
"Storage","Logical drive background initialization completed","Logical drive background initialization completed.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated.\n\t2: virtualDiskNameEv\n\tSyntax=Display String\n\tDescr=Virtual Disk for which trap is generated."
"Storage","BBU calibration cycle started","BBU calibration cycle started.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated."
"Storage","BBU calibration cycle finished","BBU calibration cycle finished.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated."
"Storage","BBU calibration cycle canceled","BBU calibration cycle canceled.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated."
"Storage","BBU battery not present","BBU battery not present.\nVariables:\n\t1: controllerNameEv\n\tSyntax=\nDisplay String\n\tDescr=Controller Name for which trap is generated."