Last week, we discussed these excellent troubleshooters that can act as savior in cases of medium / climbing (/ blogs / 2012 / 01/27 / high-diagnostictroubleshooting -utilities-on-NetScaler /). The focus this week is on technical support tools that we have in the diagnostic module.
Many times, when you open a support case, the first thing you would be asked to provide "technical support" file. What is this file and how you get it? unique place where you can do all this is the "Diagnostics" page on the user interface. the tools of technical support have many options and let us walk in important here
Generate support files :. This option will generate the support file that collects all relevant data for debugging and analysis This file generally includes:.
- Newnslog file "/ var / NSLog / "
- dmesg file" / NSLog / / var "
- file-based process" / var / core / "
- core database files to "/ var / crash /"
- FLES messages to "/ var / log /"
- Ns.log files in "/ var / log /"
- of other user process log "/ var / log /"
- configuration file "/ nsconfig /"
- user monitor modules "/ nsconfig / monitors /"
- important configuration file "/ etc /"
- .recovery file "/ flash /"
- Various command output from "shell"
- Nsapimgr release of "shell"
- objects downloaded from "/ var / download /"
- files Profiler logs "/ var / nsproflog /"
- Sync files newspaper "/ var / nssynclog /"
surprised to the amount of data collected :). This is to ensure that you are not prompted for individual files repeatedly slowing down the whole process. Run the utility and easy to get all the data in the single zip file and download it from the same window.
Apart from these files and data, in some cases, you need to take some living traces to debug the issue and that is the next available utility:
Start new trace: This utility helps you to collect the trace of live NetScaler network. We have seen that many of those of the connection level or latency kinds of questions require a trace file for debugging. Collecting trace is simple but collecting the right way is important to help the analysis. NetScaler can run multiple Gbps of traffic in the direct environment of collection and track with GB of data is not good. Most trace analysis tools die opening the file and you are asked to provide smaller trace files. It is important to collect relevant flow in the trace file that needs attention or we can spend several days go to the capture. The utility helps you here to collect trace file right and you just need to choose the right options
- Package Size :. always make sure that you change the default packet size of 164 to the size you need otherwise keep 0 which means we collect parcel of all sizes on the wire
- duration: this is very important to collect short for effective analysis files
- trace file format: this will allow you to switch between "nstrace" and "tcpdump". Our guideline is to gather in "nstrace 'format as keep specific information intact NetScaler
- Expression Filter: This is of enormous importance because it allows you to pin point the fundamental problem area. You can add phrases to the filter. The qualifiers of expression could be
- Source IP
- Source Port
- Destination IP
- Destination Port
- IP address
- Port
- Type of Service
- rest time
- State
- service name
- virtual server name
- Log ID
- Interface
- VLAN
These are a lot of options to make the filter and much more effective you can do Boolean calculations on these. There is additional option for tracing the filtered peer connection traffic. This is very useful when you specify only one source IP as the filter, but also need to see the server side connections for this IP source original client connections
- Capture Mode :. there are lots of these modes which also helps you to collect the trace is specific to the problem scenario.
This section also provides other options to download the files and trace individual basis. The other interesting option it provides is launching "Trace Back" on a live system.
You must provide the files of the core and basis to run gdb utility to collect back trace. This also comes in handy when downloading huge database file takes time and look in plain tracing can provide engineering clues about the nature of the accident.
Overall it is a lot of rich tools and utilities provided to make your work simpler 
0 Komentar