11.2.7.2. How to Check When a Failure Occurs¶
| Operation Confirmed Version: | |
|---|---|
| Citrix Netscaler VPX Version11.0 Build67.12 Standard Edition | |
Here, GUI screen check method and various log outputs, when abnormality occurred with Citrix Netscaler VPX, will be described.
Precondition
This item contains check of syslog/trap messages.
For each setting method, please refer to the respective Tutorial.
VRRP failure¶
Check method of VRRP failure will be described.
Check method on the GUI screen
From the [ Configuration ] tab, move to [ System ] → [ Network ] → [ VMAC ].
If the Master has fault, the Backup system will be promoted to the Master. You can check the VRRP State on the following screen.
Check method on syslog
If switching occurs in VRRP, the following messages will be outputted.
In case of transition to the Master
LOCAL0.INFO: 2017/03/27:16:36:57 LB2 0-PPE-0 : default EVENT VRIDUP 6190 0 : VRID_(40) - State Master
In case of transition to the Backup
LOCAL0.INFO: 2017/03/27:16:39:16 LB2 0-PPE-0 : default EVENT VRIDDOWN 6200 0 : VRID_(40) - State Backup. Current Master: 100.xx.xx.26
Check method with trap
If VRRP switching occurs, the following Trap will be emitted.
vridStateChange (1.3.6.1.4.1.5951.1.1.0.142)
OID: enterprises.5951.1.1.0.142
enterprises.5951.4.1.10.2.42.0 = Counter32: 40
enterprises.5951.4.1.10.2.43.0 = IpAddress: 192.168.10.251
enterprises.5951.4.1.10.2.44.0 = Counter32: 100
enterprises.5951.4.1.10.2.46.0 = STRING: "100"
enterprises.5951.4.1.1.2.0 = IpAddress: 100.xx.xx.30
Packet capture
Instance Failure¶
The following is a check methods when instance failure occurred.
Check on the ECL Portal
On the ECL Portal, proceed from [ Cloud Computing ] → [ Network ] → [ Load Balancer ], and you can check the Load Balancer start-up state on the following screen.
Check method with trap
If the instance is restarted, the following trap will be emitted.
coldStart (1.3.6.1.6.3.1.1.5.1)
OID: coldStart
snmpTrapEnterprise.0 = OID: enterprises.5951.1.1
enterprises.5951.4.1.1.2.0 = IpAddress: 100.xx.xx.30
Service/ServiceGroup/VirtualServer Failure¶
The following is a check method when Service/ServiceGroup/VirtualServer Failure occurred.
If the Monitor (Health check) is down
It is a check method when the Health check that monitors state of each Service, fails.
Check method on syslog
If the Monitor fails, you can check the following output.
LOCAL0.INFO: 2017/03/27:17:41:14 LB2 0-PPE-0 : default EVENT MONITORDOWN 6211 0 : Monitor MonServiceBinding_TD_10_172.16.10.11:80_(http)(HTTP?Web-server-01?80) - State DOWN
If the Service/ServiceGroup is Down
If the Health check fails, ServiceGroup/Server will go Down.
The check method when they go down will be given below.
Check method on the GUI screen
If a Service is Down, you can check it on the following screen.
Tab「Configuration」 Traffic Management > Load Balancing > Services > Statistics
You can check “Down” on the following screen.
If a ServiceGroup is Down, you can check it on the following screen.
Tab「Configuration」 Traffic Management > Load Balancing > Services Group > Statistics
You can check “Down” on the following screen.
If the Virtual Server is down
If a ServiceGroup/Service is Down, the Virtual Server will go Down in the end.
Tab「Configuration」 Traffic Management > Load Balancing > Virtual Servers > Statistics
You can check “Down” on the following screen.
Check method on syslog
If a Service/ServiceGroup/VirtualServer is Down, you can check the following outputs.
Syslog output when a Service is Down
LOCAL0.NOTICE: 2017/03/28:02:52:21 LB1 0-PPE-0 : default EVENT DEVICEDOWN 434 0 : Device "server_svc_cfg_NSSVC_HTTP_TD_10_172.16.10.12:80(http-service-02)" - State DOWN
Syslog output when a ServiceGroup is Down
LOCAL0.NOTICE: 2017/03/28:02:41:16 LB1 0-PPE-0 : default EVENT DEVICEDOWN 425 0 : Device "server_serviceGroup_NSSVC_HTTP_TD_10_172.16.10.11:80(HTTP?Web-server-01?80)" - State DOWN
Syslog output when a Virtual Server is Down
LOCAL0.NOTICE: 2017/03/28:02:52:37 LB1 0-PPE-0 : default EVENT DEVICEDOWN 439 0 : Device "server_vip_NSSVC_HTTP_TD_10_172.16.100.100:80(http-vserver)" - State DOWN
Check method with trap
If a Service/ServiceGroup/VirtualServer is Down, the following trap will be emitted.
entitydown (1.3.6.1.4.1.5951.1.1.0.8)
Note
Traps emitted when a Service/ServiceGroup/VirtualServer is Down will be all transmitted with entitydown (1.3.6.1.4.1.5951.1.1.0.8). Please judge by the information stored in STRING:
Trap reception by Service Down
OID: enterprises.5951.1.1.0.8
enterprises.5951.4.1.10.2.3.0 = STRING: "server_svc_cfg_NSSVC_HTTP_TD_10_172.16.10.12:80(http-service-02)_DOWN"
enterprises.5951.4.1.2.1.1.54.15.104.116.116.112.45.115.101.114.118.105.99.101.45.48.50 = STRING: "http-service-02"
enterprises.5951.4.1.1.2.0 = IpAddress: 100.xx.xx.26
Trap reception by ServiceGroup Down
OID: enterprises.5951.1.1.0.8
enterprises.5951.4.1.10.2.3.0 = STRING: "server_serviceGroup_NSSVC_HTTP_TD_10_172.16.10.12:80(HTTP?Web-server-02?80)_DOWN"
enterprises.5951.4.1.2.7.1.33.4.72.84.84.80.21.72.84.84.80.63.87.101.98.45.115.101.114.118.101.114.45.48.50.63.56.48 = STRING: "HTTP?Web-server-02?80"
enterprises.5951.4.1.1.2.0 = IpAddress: 100.xx.xx.30
Trap reception by VirtualServer Down
OID: enterprises.5951.1.1.0.8
enterprises.5951.4.1.10.2.3.0 = STRING: "server_vip_NSSVC_HTTP_TD_10_172.16.100.100:80(http-vserver)_DOWN"
enterprises.5951.4.1.3.1.1.59.12.104.116.116.112.45.118.115.101.114.118.101.114 = STRING: "http-vserver"
enterprises.5951.4.1.1.2.0 = IpAddress: 100.xx.xx.26
Packet capture
