- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Confusion with 2312i and host based iscsi access
MSA Storage
1753666
Members
6222
Online
108799
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
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
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
02-08-2010 05:05 PM
02-08-2010 05:05 PM
Confusion with 2312i and host based iscsi access
seems that i'm confused on how exactly hosts access the MSA 2312i. We are using the open-iscsi utility to setup an initiator on CentOS/RHEL. I can do this and see the host come up, but then I have a ton of entries when I do an fdisk -l
How to specify the correct volume when attaching the host to the target?
Is it simply from the SMU to setup an explicit mapping per host connected so only that host can have Read-Write or Read only permissions?
earlier today I had 4 volumes, with default mappings opened up, and fdisk showed /dev/sde, sdf, sdh, sdi, etc.. all the correct size of the volumes I created. But.... there were also like 10 other sdX entries, all the same size again, but this time not showing a valid partition table -- when I removed the mappings for the other 3 volumes, then the fdisk output only showed the disk entries that had valid partition tables. However, I still don't know which is what volume from fdisk
Disk /dev/sda: 438.4 GB, 438489317376 bytes
255 heads, 63 sectors/track, 53309 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 1288 10241437+ 83 Linux
/dev/sda3 1289 1549 2096482+ 82 Linux swap / Solaris
/dev/sda4 1550 53309 415762200 5 Extended
/dev/sda5 1550 53309 415762168+ 83 Linux
Disk /dev/sdc: 1000.2 GB, 1000237170688 bytes
255 heads, 63 sectors/track, 121605 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 121605 976792131 83 Linux
Disk /dev/sde: 2048.0 GB, 2048000000000 bytes
255 heads, 63 sectors/track, 248988 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sde1 1 248988 1999996078+ 83 Linux
Disk /dev/sdf: 2048.0 GB, 2048000000000 bytes
255 heads, 63 sectors/track, 248988 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdf1 1 248988 1999996078+ 83 Linux
Disk /dev/sdh: 2048.0 GB, 2048000000000 bytes
255 heads, 63 sectors/track, 248988 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdh1 1 248988 1999996078+ 83 Linux
Disk /dev/sdi: 2048.0 GB, 2048000000000 bytes
255 heads, 63 sectors/track, 248988 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdi1 1 248988 1999996078+ 83 Linux
How to specify the correct volume when attaching the host to the target?
Is it simply from the SMU to setup an explicit mapping per host connected so only that host can have Read-Write or Read only permissions?
earlier today I had 4 volumes, with default mappings opened up, and fdisk showed /dev/sde, sdf, sdh, sdi, etc.. all the correct size of the volumes I created. But.... there were also like 10 other sdX entries, all the same size again, but this time not showing a valid partition table -- when I removed the mappings for the other 3 volumes, then the fdisk output only showed the disk entries that had valid partition tables. However, I still don't know which is what volume from fdisk
Disk /dev/sda: 438.4 GB, 438489317376 bytes
255 heads, 63 sectors/track, 53309 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 1288 10241437+ 83 Linux
/dev/sda3 1289 1549 2096482+ 82 Linux swap / Solaris
/dev/sda4 1550 53309 415762200 5 Extended
/dev/sda5 1550 53309 415762168+ 83 Linux
Disk /dev/sdc: 1000.2 GB, 1000237170688 bytes
255 heads, 63 sectors/track, 121605 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 121605 976792131 83 Linux
Disk /dev/sde: 2048.0 GB, 2048000000000 bytes
255 heads, 63 sectors/track, 248988 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sde1 1 248988 1999996078+ 83 Linux
Disk /dev/sdf: 2048.0 GB, 2048000000000 bytes
255 heads, 63 sectors/track, 248988 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdf1 1 248988 1999996078+ 83 Linux
Disk /dev/sdh: 2048.0 GB, 2048000000000 bytes
255 heads, 63 sectors/track, 248988 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdh1 1 248988 1999996078+ 83 Linux
Disk /dev/sdi: 2048.0 GB, 2048000000000 bytes
255 heads, 63 sectors/track, 248988 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdi1 1 248988 1999996078+ 83 Linux
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