- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Multi-homed SD-UX Server
Operating System - HP-UX
1820230
Members
3396
Online
109620
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
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
05-03-2004 09:33 AM
05-03-2004 09:33 AM
Multi-homed SD-UX Server
I could experiment with this and figure it out, but it would take a little doing to get the environment set up until Wednesday. Thought someone here might know from experience... or really just tell me if the solution I'm considering is the right approach.
We're preparing to create an Ignite-UX/SD-UX server in our hosted data center. Primary LAN interface will be connected to the customer network which has VLANS set up to restrict access. (We'll have a "build" VLAN to allow Ignite-UX to boot on the built-in NICs as it requires while we're staging the servers before switching them to their respective customer VLANs.) The thought crossed my mind that I think we'd rather have the DHCP, image transfer, and SD-UX traffic go over the second interface on our management network (completely different IP subnet also). This way, the SD-UX server could be easily accessible for future software pushes/pulls (assuming we leave that switch port set to allow access from all of the customer VLANs).
However, as fussy as SD-UX is about the server IP address, I'm wondering how to go about this. When doing the swcopy to get the individual "tape" depots added to the server's software depot, I don't specify the -d option so it seems to assume the primary IP address based on hostname.
Would it be as simple as changing the swcopy to include the management IP address of the server with the -d option to get the depot to recognize it as the desired interface?
Any pitfalls to consider in setting something like this up?
We're preparing to create an Ignite-UX/SD-UX server in our hosted data center. Primary LAN interface will be connected to the customer network which has VLANS set up to restrict access. (We'll have a "build" VLAN to allow Ignite-UX to boot on the built-in NICs as it requires while we're staging the servers before switching them to their respective customer VLANs.) The thought crossed my mind that I think we'd rather have the DHCP, image transfer, and SD-UX traffic go over the second interface on our management network (completely different IP subnet also). This way, the SD-UX server could be easily accessible for future software pushes/pulls (assuming we leave that switch port set to allow access from all of the customer VLANs).
However, as fussy as SD-UX is about the server IP address, I'm wondering how to go about this. When doing the swcopy to get the individual "tape" depots added to the server's software depot, I don't specify the -d option so it seems to assume the primary IP address based on hostname.
Would it be as simple as changing the swcopy to include the management IP address of the server with the -d option to get the depot to recognize it as the desired interface?
Any pitfalls to consider in setting something like this up?
--
Jeff Traigle
Jeff Traigle
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
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP