And to provide a little supporting information for Denis, all the servers in our datacenter have 2 Ethernet connections but in the OS we have them teamed effectively making a single interface where an IP is assigned. So in ports I show eth0 and eth1 but in the IP I only assign them to the TEAM name. Ryan Farrington Senior Systems Engineer MedAssets 5556 Tennyson Pkwy Suite 200 Plano TX 75024 Direct - 972-244-0312 Cell - 972-836-6431 From: racktables-users-bounce@xxxxxxxxxxxxx [mailto:racktables-users-bounce@xxxxxxxxxxxxx] On Behalf Of infrastation@xxxxxxxxx Sent: Tuesday, June 15, 2010 10:53 AM To: racktables-users@xxxxxxxxxxxxx Subject: [racktables-users] Re: Items for the wish list. 15.06.2010, 16:30, "Michael Tiernan" <mtiernan@xxxxxxx>: > May I suggest that this be added to the wish list for racktables. > > When editing the ports of an object (in this case a server) I've affixed > the "Local name" of "eth0" to the first port. Now, when editing the IPV4 > allocation I'd "prefer" that the "Local name" of ports be fixed, maybe > as a pulldown of the available ports. The matter is, on Ports the object has its "sockets" listed, even those, which cannot transmit any data. And the "IPv4" tab refers to object's internal names of IP interfaces, which may be related to real sockets in an odd way. So it was left this way, when it was designed. May be, someone will arrange this in a cleaner way one day. -- Denis Ovsienko The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers