- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreOnce Backup Storage
- >
- D2d4004i iSCSI authentication
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
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
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
01-20-2010 10:26 PM - last edited on 04-24-2015 12:30 AM by Maiko-I
01-20-2010 10:26 PM - last edited on 04-24-2015 12:30 AM by Maiko-I
D2d4004i iSCSI authentication
Hi,
We've had a D2D4004i in operation for some time now.
When it was built, I assumed I was reading the manual incorrectly - the section which appeared to stated if a user went to a server and pointed an iSCSI initiator at it, it would create a new library for that server by default.
From the iSCSI SAN's I've worked with, there's always been a case of setting up a password for discovery, then another password for logon to a LUN. Then I can usually lock it down further by restricting access to an IP address range.
But I've found that by opening ESXi's storage management and just putting in the D2D's IP address as a discovery target, the D2D responds by creating a whole new tape library for it.
True, I can pre-create a library with a CHAP password requirement, preventing someone from accessing my business data.
But I looked at my server today and it had seven different Virtual Tape Libraries, from various people for various reasons performing on iSCSI discovery on this device - and I don't appear to be able to stop anyone from going ahead and consuming space should they be so inclined.
Beyond just placing this behind a firewall and letting it filter based on IP, I had really hoped I could turn off this autocreation "feature", apply a discovery password, or both.
Any assistance on this would be appreciated.
P.S. This thread has been moved from Tape Libraries and Drives to Disk-Based Backup. - Hp Forum moderator