You probably should be using the non-public GLDv2 VLAN interfaces. I'm not sure if they even work properly in Nevada though. In Nevada, the GLDv3 is the preferred way, though since it isn't public either, you might need to have a plan to integrate your driver into Nevada.
Btw, if you are building a driver that you would like to be integrated into Nevada, and can donate a couple of matching hardware cards to Sun, I'd be willing to sponsor you. Then using GLDv3 would be a better option. (Note, I'm assuming this is for some common link media like copper 1Gb or 100Mb. If its for 10Gb, I might have trouble sponsoring you since I still don't have test equipment for it. -- In fact I've offered to sponsor other 10Gb cards, but lack of suitable test peer hardware has stymied efforts there.) -- Garrett Tom Chen wrote: > Hello, > > I am trying to test VLAN of my new GLDv2 driver, qla, on Nevada 91. I am > wondering how to setup VLAN now. I used "ifconfig qla3000 plumb" to set up > qla driver with vlan id 3, however, this command does not work in nv91. > > # dladm show-link > LINK CLASS MTU STATE OVER > e1000g0 phys 1500 up -- > e1000g1 phys 1500 unknown -- > qla0 phys 1500 up -- > qla1 phys 1500 up -- > > # ifconfig qla3000 plumb > ifconfig: cannot open link "qla3000": Operation not supported > > # dladm create-vlan -l qla0 -v 3 qla3000 > dladm: VLAN over 'qla0' may require lowered MTU; must use -f (see dladm(1M)) > : operation not supported > > Tom > > > This message posted from opensolaris.org > _______________________________________________ > networking-discuss mailing list > [email protected] > _______________________________________________ networking-discuss mailing list [email protected]
