Peter Memishian wrote: > > > # dladm show-link > > > qla0 type: legacy mtu: 1500 device: qla0 > > > qla1 type: legacy mtu: 1500 device: qla1 > > > bge0 type: non-vlan mtu: 1500 device: bge0 > > > bge3000 type: vlan 3 mtu: 1500 device: bge0 > > > bge1 type: non-vlan mtu: 1500 device: bge1 > > > bge2 type: non-vlan mtu: 1500 device: bge2 > > > bge3 type: non-vlan mtu: 1500 device: bge3 > > > # ifconfig qla3000 plumb > > > ifconfig: SIOCSLIFNAME for ip: qla3000: no such interface > > > > The fact that dladm says that your device is of type 'legacy' indicates > > that you aren't producing a GLDv3 driver. VLAN support is provided by > > the OS only for GLDv3 drivers - if you have a DLPI or GLDv2 driver then > > you have to do a bunch of work yourself. > > Or you can wait about a month for Clearview UV to integrate, at which > point you'll get VLAN support for free. See > http://opensolaris.org/os/project/clearview/uv for more details. > > (Or you can write to GLDv3 and integrate into ON.) >
And to be clear, if you don't have a need to support older releases of Nevada, I think that writing to GLDv3 and integrating into ON is the superior approach. Clearview helps legacy drivers participate more equally, but not fully equally, in the Nevada networking stack. Some things you just cannot do without a full GLDv3 driver. (For example, VLAN support for full MTU frames can't be done without at least some modification to the driver.) There are some performance implications as well. You will pay less overhead as a native GLDv3 driver. Of course, if you need to support the same binary on older Solaris, or cannot integrate into ON, then GLDv2 and waiting for Clearview may be your only reasonable approach. -- Garrett _______________________________________________ networking-discuss mailing list [email protected]
