Have a look at this
http://www.tek-tips.com/vi
Decode this path
/pci@8,600000/pci@2/scsi@5
Can you paste
/etc/path_to_instant
Javeed Abdul
Main Topics
Browse All TopicsHi,
We recently had a power cut at the site of a development & DR server which I brought back up. When I start the Oracle DR instance, the server is fine and runs as required. When I startup any of the development instances on the server, my command prompt becomes unresponsive and the server essentially grinds to a halt.
I attach a snipet from my /var/adm/messages file - these errors appear any time I start one of the DEV environments:
Jul 2 00:05:34 colt /usr/lib/snmp/snmpdx: [ID 702911 daemon.error] Agent snmpd appeared dead but responded to ping
Jul 2 00:05:40 colt last message repeated 1 time
Jul 2 08:51:42 colt su: [ID 810491 auth.crit] 'su root' failed for michaelt on /dev/pts/2
Jul 2 08:53:00 colt su: [ID 810491 auth.crit] 'su applmgr' failed for michaelt on /dev/pts/2
Jul 2 08:58:09 colt pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Jul 2 08:58:09 colt genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Jul 2 08:58:49 colt pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Jul 2 08:58:49 colt genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Jul 2 08:59:19 colt pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Jul 2 08:59:19 colt genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Jul 2 08:59:38 colt sg: [ID 686534 kern.notice] VERITAS SCSA Generic Revision: 3.4d
Jul 2 08:59:57 colt pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Jul 2 08:59:57 colt genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Jul 2 09:02:32 colt sg: [ID 686534 kern.notice] VERITAS SCSA Generic Revision: 3.4d
Jul 2 09:02:41 colt pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
Jul 2 09:02:41 colt genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
Jul 2 09:02:47 colt sg: [ID 686534 kern.notice] VERITAS SCSA Generic Revision: 3.4d
Jul 2 09:25:53 colt scsi: [ID 365881 kern.info] /pci@8,600000/pci@2/scsi@5
Jul 2 09:25:53 colt <HP Ultrium LTO 2>
Jul 2 09:25:53 colt scsi: [ID 193665 kern.info] st39 at qus5: target 4 lun 0
Jul 2 09:25:53 colt genunix: [ID 936769 kern.info] st39 is /pci@8,600000/pci@2/scsi@5
Jul 2 12:09:04 colt /usr/lib/snmp/snmpdx: [ID 702911 daemon.error] Agent snmpd appeared dead but responded to ping
Any help would be massively appreciated....
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Have a look at this
http://www.tek-tips.com/vi
Decode this path
/pci@8,600000/pci@2/scsi@5
Can you paste
/etc/path_to_instant
Javeed Abdul
What error messages? Those log entries are spread out over a long period and, without the corresponding time you tried to start a new DB instance up, I don't see anything particularly worrying. The "st" device is just a tape drive. See if `prtdiag` shows you any faults.
That said, the slowdown problem sounds like a memory issue and Solaris is paging like mad to start the additional DB instance. Check the amount of memory detected at bootup is correct and use `vmstat` to see what's going on. Also check the Oracle config to make sure it's not grabbing more memory than you actually have!
Well I have reinstalled Netbackup on the advice of our hardware support contract. The server seems to be running fairly well, although I don't have an Oracle db to start up as I planned to recreate the Oracle instnaces... Therein lies the problem.
When in Netbackup, I attempt to import a catalog and I get the following error: Media Positioning Error. I have tried with three tapes so I'm fairly confident its not the media. I also get the following errors in messages when the netbackup import fails (see below)
I'm guessing its a hardware issue with the tape drive - what is the likelihood of this? I know he have some spare drives available in the server room - what is required to swap the drives and are they hot swappable?
Thanks for your help so far....
Terry
>>>Issue <<
Jul 2 12:09:04 colt /usr/lib/snmp/snmpdx: [ID 702911 daemon.error] Agent snmpd appeared dead but responded to ping
Agent Appears Dead
This error results when there is a inconsistency in configuration for a sub-agent where the sub-agent implements it's own security checking. The master agent snmpdx validates incoming requests based on ACLs defined in the subagent_name .acl file (in /etc/snmp/conf). If these differ from whatever file the sub-agent uses then snmpdx may forward a request which will be rejected by the sub-agent. If this is the case then the sub-agent will not respond to the request and snmpdx will time-out the request. After a certain number of consecutive time-outs snmpdx will issue it's own requests (with community public) to find out if the sub-agent is actually responding. If it does respond then this message is issued. If it doesn't the agent is disabled by snmpdx. The solution is to ensure that any specific sub-agent ACL configuration is also configured in a subagent_name .acl file.
Typically this happens with the supplied sub-agent mibiisa. By default there is no mibiisa.acl file and the mibiisa configuration file snmpd.conf defines the community strings mibiisa uses. As snmpdx doesn't perform and security checks for requests that are forwarded to mibiisa (as there is no mibiisa.acl file) then any invalid requests are silently ignored by mibiisa.
The number of consecutive time-outs (default 5) can be configured by implementing the undocumented -f n options to the startup script, where n specifies the number of time-outs. A value of 0 means no limit. Edit the /etc/rc3.d/S76snmpdx script and change:
/usr/lib/snmp/snmpdx -y -c /etc/snmp/conf
to:
/usr/lib/snmp/snmpdx -y -c /etc/snmp/conf -f 0
Now stop and start snmpdx:
/etc/rc3.d/S76snmpdx stop
/etc/rc3.d/S76snmpdx start
__________________________
>>>Issue <<
Jul 2 09:25:53 colt scsi: [ID 365881 kern.info] /pci@8,600000/pci@2/scsi@5
Jul 2 09:25:53 colt <HP Ultrium LTO 2>
Jul 6 13:17:13 colt scsi: [ID 107833 kern.notice] Sense Key: Media Error
Jul 6 13:17:13 colt scsi: [ID 107833 kern.notice] ASC: 0x14 (recorded entity not found), ASCQ: 0x0, FRU: 0x0
Jul 6 13:20:24 colt scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/pci@2/scsi@5
Jul 6 13:20:24 colt Error for Command: rezero/rewind Error Level: Fatal
Jul 6 13:20:24 colt scsi: [ID 107833 kern.notice] Requested Block: 1 Error Block: 1
Jul 6 13:20:24 colt scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: $
Fatal ,Media error..I would be replacing it..
Provide HP drive model.
uname -a
check the HP drive Documentation . That will give you a clue whether you can replace online /offline
Hope this help
The messages in the logs that reference VERITAS is the sg (SCSI pass-through) driver, which NetBackup uses to send control data to tape drives, mainly SCSI reserve and release.
You say you're running NetBackup 4.5, which depending on which patches are on it, could be pretty buggy with the sg driver, especially if you are using SSO (Shared Storage Option). NetBackup 4.5 is a really old version so I would want to know why you're running that older version.
I assume this is a NetBackup media server, which is a server that directly transfers data from disk to tape? If it's not designed to do that, you could always unload NetBackup which would get rid of the sg driver... I just don't know if that was the original intent... i.e. if NetBackup media server is no longer being used, you could get rid of it and see if that is what caused the problem.
Also depending on how the sg driver was configured, it could potentially be scanning a whole lot of controllers and targets, which would explain the time in between those messages... you can modify /kernel/drv/sg.conf to only scan the appropriate targets and LUNs, reinstall the sg driver (which reloads it), and then every subsequent reload should not have those delays.
However, the sg driver is just an initial load and discovery as referenced by your log messages... if the performance problem continues even after the driver was loaded, then you have another issue likely.
Business Accounts
Answer for Membership
by: gflmartinsPosted on 2009-07-02 at 07:40:05ID: 24763848
I should mention that I'm running Solaris 9... I have patch clusters as of 2006 (downloading the most recent from 2009) and Veritas Netbackup 4.5 which works and backs up data on the server each night.
Thanks