- Community Home
- >
- Storage
- >
- HPE Nimble Storage
- >
- Array Setup and Networking
- >
- Re: Usable Initiator Ports...
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
тАО01-05-2015 02:39 PM
тАО01-05-2015 02:39 PM
Greetings!
V virtual hosts connected to our SAN, and one of the three cannot seem to connect through the Nimble Connection Manager (2.0.7.10). We have to manually add the Target Portal Discovery IP address and even when we do, it shows Group: Unknown and no Host MPIO IP addresses. Also, under the Recent Tasks, Get Discovery Target Portals shows Discovery Target Portals Found = 1 (I'm assuming it's the one we manually entered) and Get Configuration Data ends with Usable Initiator Ports = 0.
Not sure why this host is different from the other two, but does anyone have some insight into this problem?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-05-2015 03:26 PM
тАО01-05-2015 03:26 PM
SolutionHi LT iT
there is a video blog here that walks you through setting up a volume with NCM
You want to make sure:
- the host can ping the arrays target/data ports from its data IP addresses
- if jumbo frames are configured the they are configured in the entire stack
- if its a clustered volume ensure the multi-initiator bit is set when provisioning
- have selected your ip interfaces to be used in NCM
any issues please post back or if it's urgent contact support and I'm sure they will guide you through it
cheers
rich
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-06-2015 06:19 AM
тАО01-06-2015 06:19 AM
Re: Usable Initiator Ports...
If its an option - I'd suggest starting from scratch with getting that Host connected to your iSCSI Storage network. Trace cables, confirm network switch port config, Host config, etc.. I'd be willing to bet you'll find something has been overlooked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2015 07:08 AM
тАО01-07-2015 07:08 AM
Re: Usable Initiator Ports...
So it turns out, one good reboot and everything appears to be working. Thanks for all your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2015 07:24 AM
тАО01-07-2015 07:24 AM
Re: Usable Initiator Ports...
Hah - a classic Windows fix.. reboot..