HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- iSCSI initiator configuration: insf command does n...
Operating System - HP-UX
1826614
Members
2946
Online
109695
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
Forums
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
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-25-2008 02:19 AM
05-25-2008 02:19 AM
iSCSI initiator configuration: insf command does not respond.
iSCSIutil connection to an equallogic SAN went correct until creation of devicefile using insf -H 255 command: Insf and iscsiutil –pO do not respond (no error message).
1.) Could someone check if the configuration below is correct or give me a clue to find out what’s wrong?
2.) How to reset the CHAP secret parameter to its initial value (empty)?
Find below the output of Iscsiutil –l, –pD and isoscan commands:
A) ioscan -fnH 255 says:
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
iscsi 0 255/0 iscsi CLAIMED VIRTBUS iSCSI Virtual Node
B) issciutil –l says:
Initiator Name : iqn.1986-03.com.hp:stcuxp01.1182901557
Initiator Alias :
Authentication Method : None
CHAP Method : CHAP_UNI
Initiator CHAP Name :
CHAP Secret : none
NAS Hostname :
NAS Secret :
Radius Server Hostname :
Header Digest : None,CRC32C (default)
Data Digest : None,CRC32C (default)
SLP Scope list for iSLPD :
C) iscsiutil -pD says:
Discovery Target Information
----------------------------
Target # 1
-----------
IP Address : 10.100.100.20
iSCSI TCP Port : 3260
iSCSI Portal Group Tag : 1
User Configured:
----------------
Authenticaton Method : None
CHAP Method : CHAP_UNI
Initiator CHAP Name :
CHAP Secret : none
Header Digest : None,CRC32C (default)
Data Digest : None,CRC32C (default)
Target # 2
-----------
IP Address : 10.100.100.21
iSCSI TCP Port : 3260
iSCSI Portal Group Tag : 1
User Configured:
----------------
Authenticaton Method : None
CHAP Method : CHAP_UNI
Initiator CHAP Name :
CHAP Secret : none
Header Digest : None,CRC32C (default)
Data Digest : None,CRC32C (default)
1.) Could someone check if the configuration below is correct or give me a clue to find out what’s wrong?
2.) How to reset the CHAP secret parameter to its initial value (empty)?
Find below the output of Iscsiutil –l, –pD and isoscan commands:
A) ioscan -fnH 255 says:
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
iscsi 0 255/0 iscsi CLAIMED VIRTBUS iSCSI Virtual Node
B) issciutil –l says:
Initiator Name : iqn.1986-03.com.hp:stcuxp01.1182901557
Initiator Alias :
Authentication Method : None
CHAP Method : CHAP_UNI
Initiator CHAP Name :
CHAP Secret : none
NAS Hostname :
NAS Secret :
Radius Server Hostname :
Header Digest : None,CRC32C (default)
Data Digest : None,CRC32C (default)
SLP Scope list for iSLPD :
C) iscsiutil -pD says:
Discovery Target Information
----------------------------
Target # 1
-----------
IP Address : 10.100.100.20
iSCSI TCP Port : 3260
iSCSI Portal Group Tag : 1
User Configured:
----------------
Authenticaton Method : None
CHAP Method : CHAP_UNI
Initiator CHAP Name :
CHAP Secret : none
Header Digest : None,CRC32C (default)
Data Digest : None,CRC32C (default)
Target # 2
-----------
IP Address : 10.100.100.21
iSCSI TCP Port : 3260
iSCSI Portal Group Tag : 1
User Configured:
----------------
Authenticaton Method : None
CHAP Method : CHAP_UNI
Initiator CHAP Name :
CHAP Secret : none
Header Digest : None,CRC32C (default)
Data Digest : None,CRC32C (default)
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2008 06:23 AM
05-25-2008 06:23 AM
Re: iSCSI initiator configuration: insf command does not respond.
Shalom,
Most of the time disk devices are created with the command
insf -C disk
SEP
Most of the time disk devices are created with the command
insf -C disk
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2008 08:45 PM
05-25-2008 08:45 PM
Re: iSCSI initiator configuration: insf command does not respond.
Thanks for your quick response; insf -C disk also does not respond, no error message. How can I check if the SAN is accessible?
The only test I know is ping the IP-addresses of the SAN.
Is there any other action that has to be done at the equallogic end to provide the disk?
The only test I know is ping the IP-addresses of the SAN.
Is there any other action that has to be done at the equallogic end to provide the disk?
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP