Alan wrote: >I am wondering if people are looking at using persistent DHCP for this. To >make it work you have to use layer 2 VSWITCHes and you have to manage >MACIDs on the NICDEFs. Your automation tools have to "manufacture" a new >MACID for every new NICDEF and put it there or on COMMAND DEFINE NIC. >(I've created such automation for DIRMAINT.)
>It means that the network people can operate the DHCP server, whether its >onboard as a Linux guest or outboard, and take responsibility for changing >things (home, DR, IP changes, etc.) I'm not. I don't want to have to involve another group involved. Right now DR is entirely automated and operations staff does the whole thing. Our VM ids map to IP addresses (not hostnames) and I can relate the 2 without looking at a spreadsheet all the time. On servers with more than one interface their IPs end in the same octet. I don't want network people sticking other devices in our subnets and messing with the scheme :) And i don't want to have to submit (more) paperwork! VM provided MACIDs are fine with us. Marcy ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
