- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- ETLA problem
StoreEver Tape Storage
1753505
Members
7121
Online
108794
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО05-24-2004 02:09 AM
тАО05-24-2004 02:09 AM
ETLA problem
Resetting NSR configuration after power failure.
Hello,
First I describe my configuration:
Library ESL9595 L2 (firmware 3.48)
Pn: 343378-B21
HP sn: US50413002
CPQ sn: 2G43MB91N002
8 drives LTO2 (firmware F43W)
2 NSRs E2400-160 (firmware 5.3.0B)
1 Interface Manager Card (firmware 1.200)
Command View ESL 1.200
Thru 1st SCSI port I have connected Robot and 1 Drive
Thru each of the other SCSI ports I have connected drives (1 drive per SCSI bus).
My Management Card (Extended Tape Library Architecture )has static IP address.
NSR has a DHCP turned ON, so IP addresses comes from Management Card.
NSRs have Indexed Maps with Auto Discovery On Reboot Events parameter.
There is no problem with Management Card (status in Command View is OK).
Management Card working in Automatic Mode.
Also I can ping this card, telnet, serial communication and view inventory of the library.
After look in the configuration of Management Card (via serial port) I check, that everything is correct and SAVE configuration.
PROBLEM:
After power failure (or OFF/ON library) NSRs loose configuration!
I still have Indexed maps, but all are EMPTY.
Also parameter ├в Auto Discovery On Reboot Events parameter├в goes to ├в Manual Discovery├в .
Also parameter ├в Number of Controller LUNS├в changes from 1 (default) to 4.
Two times I do NOT have this problem ├в I reboot library and NSRs keep configuration.
One time, after reboot, ONE NSR loose configuration, but other keeps.
How is it possible?
Is it possible, that Management Card can do it?
Or maybe I have problem with configuration of this card.
Another strange thing:
In Command View ESL I have permanently info about NSR: ├в Reboot Required├в .
But after reboot (even only N
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-24-2004 04:17 AM
тАО05-24-2004 04:17 AM
Re: ETLA problem
Miroslaw,
I have seen E1200-160 cards loosing modifications after a reboot, too, but I could never reproduce it reliably. Since then I always try to explicitly save the configuration through the character-mode interface and I try to reboot after any change to check if it stuck.
Apart from that I tell my customers to save the configuration via FTP.
I have seen E1200-160 cards loosing modifications after a reboot, too, but I could never reproduce it reliably. Since then I always try to explicitly save the configuration through the character-mode interface and I try to reboot after any change to check if it stuck.
Apart from that I tell my customers to save the configuration via FTP.
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-26-2004 07:20 PM
тАО05-26-2004 07:20 PM
Re: ETLA problem
In an ETLA configuration the mapping must be performed via Command View and NOT the serial port. I suggest that the maps are deleted and then re-created via Command View ESL and Secure manager.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP