[crossbow-discuss] dladm vnic-create fails; conf files; command name

Steffen Weiberle Steffen.Weiberle at Sun.COM
Sat Dec 16 14:11:06 PST 2006


I have tried the Crossbow FBUs on top of build 54 for both SPARC (with bge) and x64 (with e1000g), 
and in both cases I get error in fundamental places.

After additional attempts at things, I am able to hang the SPARC system.

Has anyone else tried these bits on 54?

Thanks
Steffen

First error:
# dladm create-vnic -d bge2 -m 9:7:8:9:10:8d 1
dladm: VNIC creation failed: File exists

Where the file that exists is /etc/vnic.conf, which has the folling in it:
...
# Use the dladm(1m) command to change the contents of this file.

1       bge3    auto    -       -       0

I had plumbed bge3 manually, so I can understand why something might be in there.

Second error:
After moving /etc/vnic.conf aside,
# dladm create-vnic -d bge2 -m 9:7:8:9:10:8d 1
dladm: VNIC creation failed: Invalid argument

And an empty /etc/vnic.conf is create, BTW.

After removing /etc/vnic.conf and rebooting, therefore no bge3 configuration:
# dladm create-vnic -d bge2 -m 9:7:8:9:10:8d 1
dladm: VNIC creation failed: Invalid argument

Plus, on the console:
vnic: WARNING: vnic_dev_create failed with 22


A documentation NIT:

dladm should reference the file /etc/vnic.conf if it uses it.

And in the spirit of consistency, if netrcm uses a file in /etc/inet/netrcm.conf, then:

1. It should also be documented in netrcm(1M), and

2. The location of the files for dladm and netrcm should be the same directory, IMHO.


Also, why is netrcm the command name when a lot of other admin command are *adm? A lot is an 
understatement, there are no other 'admin' commands that I can see in /usr/sbin that aren't *adm.



More information about the crossbow-discuss mailing list