1820230 Members
3396 Online
109620 Solutions
New Discussion

Multi-homed SD-UX Server

 
Jeff_Traigle
Honored Contributor

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?
--
Jeff Traigle