Peter Memishian writes: > > > Yeah, and naming them with my new vanity names will help me keep them > > straight, but 'dladm show-phys' will map the vanity names back tothe > > swapped physical names still. > > Does that really cause a problem? In general, administrators should > rarely be interacting with the device names, so it's not clear to me why > they'd care about those names.
This sounds a bit like the old "so how do I know which device name goes with which wire?" problem. I think Kyle was making assumptions about how the device numbering and naming worked, and how that ended up geographically identifying devices (at least _somewhat_). PCI enumeration run with different BIOS devices enabled and disabled throws one wrench into that idea, while vanity naming tosses in another (and possibly a solution as well). What we're missing (and have often discussed) is some clear way to associate datalink and/or IP level objects with the physical wires and ports that those things are using, so that a user can insert or remove a wire with some confidence that he's not doing something horribly wrong. Today, I think the best we've got is plugging in the wire, and then running snoop on successive devices until the "right" one is found. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
