Sponsored Content
Operating Systems Solaris Sun Fire E2900 crashed. Help analyze explorer Post 302368473 by Sun Fire on Thursday 5th of November 2009 01:32:54 AM
Old 11-05-2009
Quote:
Originally Posted by vettec3
Did the server actually panic I cant see any panic string.

The problems I see could have made the server sluggish or hang it.
The first messages has to do with veritas volumemanager/filesystem
and you are having problems with the fibre connection to the SUN3510 raid.

I would update HBA card driver (sun would probably tell you to ugrade tha SAN "package" its varios patches) ,firmware in the 3510 array and check
fibre cables and "GBICS"

Actually yes, the server crash, and under /var/crash I have unix.0, vmcore.0 , and bounds files.


3510 FC firmware is latest.

I agree regarding the driver, I found the server patch level is kind of old, so my colleague installed the latest patches and upgraded drivers. He kept it under observation.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Sun Fire v1280 is crashing

I still haven't got an answer to this question... Excerpt from My SysAd Blog A colleague of mine is having a problem with a Sun Fire v1280 server crashing. He tried Googling for the error message in red but hasn't found anything yet. Your insights would be greatly appreciated. "cannot... (2 Replies)
Discussion started by: esofthub
2 Replies

2. UNIX for Dummies Questions & Answers

Sun Fire 280R

Hello all, I'm lost and can't figure this problem out. I have a Sun fire 280R running Solaris 8. Everything was working great. I have one drive in bay 1(not 0). But when I reboot the system it trys to open files in /dev/rdsk/c1t1d0s0. Should it have been opeing /dev/rdsk/c1t0d0s0, the... (4 Replies)
Discussion started by: larryase
4 Replies

3. Solaris

Sun Fire V1280 / E2900 / Netra 1280

Hello, I'm trying to fix this server System Board (CPU/Memory Unit). The error indicates that its missing 3.3VDC. So far all the fuses and caps have been checked. I new at this type of machine, need help for idea on this system. Thank you in advance. Vu (0 Replies)
Discussion started by: vhtran
0 Replies

4. Solaris

Sun Machine Crashed

During system startup the following warnings are appear. Warning: /pci@8, 700000/scsi@6, 1 (g1m1) Connected command timeout for target 9.0 Warning: /pci@8, 700000/scsi@6, 1 (g1m1) Target 9 reducing sync, transfer rate Warning: /pci@8, 700000/scsi@6, 1... (5 Replies)
Discussion started by: tabreaz
5 Replies

5. Solaris

Sun Fire 280R Sun Solaris CRT/Monitor requirements

I am new to Sun. I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor? Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies

6. Solaris

Config reader module in Sun MC Agent not work in E2900

Hi men, Have you ever meet this error ? I install full Sun MC 4.0 packages (+ Add ons) exception of Sun Midrange Platform Administration because i don't know how to configure it Then all other servers are ok, only E2900 servers have Config reader module error: Data Acquisition error I... (12 Replies)
Discussion started by: tien86
12 Replies

7. Solaris

Question for Sun explorer

I am running Sun Explorer to collect data, but /proc is very big in size so it is takin time to get completed. (Running from past 3 hours). I ran --> /opt/SUNWexplo/bin/explorer -w all,zones root@tsrim03:/# ps -ef | grep -i explo root 27623 6539 0 06:28:59 pts/1 0:03 ksh -p... (1 Reply)
Discussion started by: solaris_1977
1 Replies

8. Solaris

How-to find SerialNumber Sun E2900

several newbie questions: > how-to find serialnumber for Sun E2900 prtdiag -v does not show chassis serial number > LOM is not connectable . Are there any tools to get automatically Serial numbers for HW. Thanks ! (7 Replies)
Discussion started by: magedfawzy
7 Replies

9. Solaris

Sun fire x2270

Hello, I have purchaced an old SUn fire x2270 server . I wanted to make ILOM upgrade to the latest version of software : ILOM 3.0.9.18.a r126592 BIOS vers. 2.09 Server 2.2.3 (10-Aug-2018) Because my version is very outdated. But i can't download the updatebecause it's require... (4 Replies)
Discussion started by: LouisLakoute
4 Replies
tnfxtract(1)							   User Commands						      tnfxtract(1)

NAME
tnfxtract - extract kernel probes output into a trace file SYNOPSIS
tnfxtract [ -d dumpfile -n namelist] tnf_file DESCRIPTION
The tnfxtract utility collects kernel trace output from an in-core buffer in the Solaris kernel, or from the memory image of a crashed sys- tem, and generates a binary TNF trace file like those produced directly by user programs being traced. Either both or neither of the -d and -n options must be specified. If neither is specified, trace output is extracted from the running ker- nel. If both are specified, the -d argument names the file containing the (crashed) system memory image, and the -n argument names the file containing the symbol table for the system memory image. The TNF trace file tnf_file produced is exactly the same size as the in-core buffer; it is essentially a snapshot of that buffer. It is legal to run tnfxtract while kernel tracing is active, i.e., while the in-core buffer is being written. tnfxtract insures that the output file it generates is low-level consistent, that is, that only whole probes are written out, and that internal data structures in the buffer are not corrupted because the buffer is being concurrently written. The TNF trace file generated is suitable as input to tnfdump(1), which will generate an ASCII file. OPTIONS
The following options are supported: -d dumpfile Uses dumpfile as the system memory image, instead of the running kernel. The dumpfile is normally the path name of a file generated by the savecore utility. -n namelist Uses namelist as the file containing the symbol table information for the given dumpfile. OPERANDS
The following operand is supported: tnf_file Output file generated by tnfxtract based on kernel trace output from an in-core buffer in the Solaris kernel. EXAMPLES
Example 1: Extracting probes from a running kernel Extract probes from the running kernel into ktrace.out: example% tnfxtract ktrace.out Example 2: Extracting probes from a kernel crash dump Extract probes from a kernel crash dump into ktrace.out: example% tnfxtract -d /var/crash/`uname -n`/vmcore.0 -n /var/crash/`uname -n`/unix.0 ktrace.out EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWtnfc | +-----------------------------+-----------------------------+ SEE ALSO
prex(1), tnfdump(1), savecore(1M), tnf_kernel_probes(4), attributes(5) SunOS 5.10 19 Aug 2003 tnfxtract(1)
All times are GMT -4. The time now is 02:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy