HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Broadcom iSCSI boot invalid DHCP values displayed
BladeSystem - General
1827885
Members
1553
Online
109969
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
06-04-2010 06:09 AM
06-04-2010 06:09 AM
Broadcom iSCSI boot invalid DHCP values displayed
This concerns the Broadcom NC532i adapter on BL460c G6.
I have had success in getting the NIC to log on to our iSCSI target (MSA2324i) using all static parameters in the BIOS, and am now trying to get it to work from DHCP so that we can take advantage of dynamic profile mapping through Virtual Connect.
I have configured the DHCP server with a static lease tied to the MAC address of the adapter, and set up Option 12 (to specify the host IQN) and Option 17 to specify the target properties.
The lease is configured to provide an IP address of 10.5.233.111 (our target is 10.5.233.81) and I have set the correct mask and gateway.
When the server starts its boot sequence, it shows "iSCSI Boot V3.1.5", then displays "Acquiring DHCP parameters for interface (then follows the correct MAC address).
It claims success at connecting to the DHCP server and displays all the initiator and target iSCSI details correctly from the configured options, but the host IP settings are completely wrong. It is displaying an IP address of 104.115.50.46, a mask of 100.92.102.115 and a gateway of 46.98.111.111 !!! Which is all total junk.
I have checked and treble-checked that the NIC is set to get all its settings from DHCP. I have also tried HBA mode and not, and although the MAC address used differs, the end results are the same.
I have been through the remaining adapters in the BIOS and ensured that there is no trace of these values anywhere I can see them. But it is consistent each time it goes round its boot sequence. Understandably, the attempt at booting fails with "Unable to establish TCP communications with target".
Has anybody seen this kind of behaviour before? Ring any bells? Got any suggestions? Please... Loads of points on offer for a bit of inspiration ;-)
Bob
I have had success in getting the NIC to log on to our iSCSI target (MSA2324i) using all static parameters in the BIOS, and am now trying to get it to work from DHCP so that we can take advantage of dynamic profile mapping through Virtual Connect.
I have configured the DHCP server with a static lease tied to the MAC address of the adapter, and set up Option 12 (to specify the host IQN) and Option 17 to specify the target properties.
The lease is configured to provide an IP address of 10.5.233.111 (our target is 10.5.233.81) and I have set the correct mask and gateway.
When the server starts its boot sequence, it shows "iSCSI Boot V3.1.5", then displays "Acquiring DHCP parameters for interface (then follows the correct MAC address).
It claims success at connecting to the DHCP server and displays all the initiator and target iSCSI details correctly from the configured options, but the host IP settings are completely wrong. It is displaying an IP address of 104.115.50.46, a mask of 100.92.102.115 and a gateway of 46.98.111.111 !!! Which is all total junk.
I have checked and treble-checked that the NIC is set to get all its settings from DHCP. I have also tried HBA mode and not, and although the MAC address used differs, the end results are the same.
I have been through the remaining adapters in the BIOS and ensured that there is no trace of these values anywhere I can see them. But it is consistent each time it goes round its boot sequence. Understandably, the attempt at booting fails with "Unable to establish TCP communications with target".
Has anybody seen this kind of behaviour before? Ring any bells? Got any suggestions? Please... Loads of points on offer for a bit of inspiration ;-)
Bob
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