- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: NSR Reboot
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2003 02:00 AM
тАО12-22-2003 02:00 AM
NSR Reboot
I've got some sporadic trouble with my backups.
8 SDLTs are hooked up to an m2402 and routed to my backup server with a fca2101
Sometimes my jobs in BrightStor ARCserve crash with SCSI errors and such.
I figured out by looking in the log of the NSR that right about that time it reboots, but I really don't know why.
The only hint I got is the log entry right before the reboot which I cannot interpret.
It looks like this:
Reserved Instruction ExceptionType : 0a Address : 800af48c (inside fcpTrns_sendSpoofResponse) Return Address = 878e6f90 (inside unknown) Virtual Address : 00000018 Task : psOutQ
Can somebody tell me what it means?
TIA
Lyndon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2003 11:47 PM
тАО12-22-2003 11:47 PM
Re: NSR Reboot
Make sure your zoning is correct, and your TPLRO parameter is set at "2".
regards
christian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2003 01:18 AM
тАО12-30-2003 01:18 AM
Re: NSR Reboot
But the NSR and my Backup Server are the only connections on that FibreChannel Switch, so I did not set any zones.
I looked for that TPLRO option you mentioned and set it to 2 on the Backupserver with the lputilnt.exe.
But the only parameter I found and set was called ResetTPLRO, not TPLRO.
n e way, my NSR rebooted once more last night with exact the same event in the log. So it seems that parameter did not to the trick...
any other tips?
TIA
Lyndon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-02-2004 09:45 AM
тАО01-02-2004 09:45 AM
Re: NSR Reboot
We recently released 5.03.0b.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2004 07:17 PM
тАО01-04-2004 07:17 PM
Re: NSR Reboot
I can't find the newer version you're mentioning on the product support page of the M2402.
Could you possibly direct me to the download location?
Lyndon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2004 07:42 PM
тАО01-04-2004 07:42 PM
Re: NSR Reboot
Sure. You have to look under the 'cross operating system' catagory (a bit non-obvious to some).
The file is for use with the serial/telnet interface.
This link might get you there:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?locale=en_USтМй=English+%28US%29&pnameOID=261320&prodSeriesId=337412&prodTypeId=12169&basePartNum=COL3566&locBasepartNum=co-12621-3&os=Cross+OS&tech=Firmware
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2004 07:50 PM
тАО01-04-2004 07:50 PM
Re: NSR Reboot
ftp://ftp.hp.com/pub/softlib/software2/COL3566/co-12621-3/5.3.0b_fw_winston_x.dlx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2004 07:10 PM
тАО01-11-2004 07:10 PM
Re: NSR Reboot
Thanks for the link to the new firmware!
I uploaded it to the NSR an kept an eye on the backups closely the last few days...
seems like the reboot problem of the device disapeared but there are still messages in the log that disturb me!
First there are quite many of these: SCSI port 13 unexpected disconnect. But they don't seem to impact my backup.
Then last friday night I got SCSI Errors in Brighstor which are surely connected to following event-messages of the NSR:
SCSI port 14 invalid DSA
SCSI port 14 HTH error
SCSI port 14 bus reset
SCSI port 14 invalid DSA
CHK COND with Sense Key=0x3, ASC=0x11, ASCQ=0x0 returned from location 14/0/0
Do you have an idea why this happens?
Lyndon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-21-2004 11:55 PM
тАО01-21-2004 11:55 PM
Re: NSR Reboot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-22-2004 02:21 AM
тАО01-22-2004 02:21 AM
Re: NSR Reboot
Using the router web interface, go to "Report" on the main menu, select printable view, and save the whole page off as an html file. Send the file to ltt_team@hp.com, and I'll have the engineers review the error logs.
[Note, I'm not asking everyone with router problems to start sending them to LTT team -they should use their normal support process. However, we [the hp tape automation division] like to monitor the ITRC forums and select specific problems to have engineering look at. We've picked this one, since it might be one that more than one customer is experiencing. << end disclaimer>>]