I've had this working in Solaris 10U4, but this is the first I've tried in
OpenSolaris.... I'm using build 82, although I've experienced this in 79b as
well.
I'm creating an aggregate (802.3ad) link, using nge0 and nge1 on an Ultra 40M2.
I create the interface and get it working like so:
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
inet 127.0.0.1 netmask ff000000
nge0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 1500
index 2
inet 0.0.0.0 netmask ff000000
ether 0:14:4f:9b:bb:fe
nge1: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 1500
index 3
inet 0.0.0.0 netmask ff000000
ether 0:14:4f:9b:bb:ff
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
index 1
inet6 ::1/128
# ifconfig nge0 unplumb
# ifconfig nge1 unplumb
# svcadm disable nwam
# cat /etc/hostname.nge0
10.0.60.1
# mv /etc/hostname.nge0 /etc/hostname.aggr1
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
inet 127.0.0.1 netmask ff000000
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
index 1
inet6 ::1/128
# dladm create-aggr -d nge0 -d nge1 1
# ifconfig aggr1 plumb 10.0.60.1 netmask 255.255.255.0 up
And now the interface comes up, and works perfectly.
I want to make this persistent across reboots, hence the reason I created
/etc/hostname.aggr1. I do a "touch /reconfigure" and reboot. Once I reboot, the
aggr1 interface is gone, and I cannot even plumb it:
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
index 1
inet 127.0.0.1 netmask ff000000
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
index 1
inet6 ::1/128
Now when I try to look at dladm to see what the status of my aggr 1 device is,
it reports there are no aggr groups (it just says nothing):
# dladm show-aggr
# dladm show-dev
nge0 link: unknown speed: 0Mb duplex: unknown
nge1 link: unknown speed: 0Mb duplex: unknown
# ifconfig aggr1 unplumb
# ifconfig: unplumb: SIOCGLIFFLAGS: aggr1: no such interface
# ifconfig aggr1 plumb
# ifconfig: SIOCSLIFNAME for ip: aggr1: Invalid argument
But when I try to create a new aggr 1 device, it reports it does actually exist
(even though I cannot see it):
# dladm create-aggr -d nge0 -d nge1 1
dladm: create operation failed: object already exists
I have to delete it, and now I can recreate it:
# dladm delete-aggr 1
# dladm show-aggr
# dladm create-aggr -d nge0 -d nge1 1
And look, here it is:
# dladm show-aggr
key: 1 (0x0001) policy: L4 address: 0:14:4f:9b:bb:fe (auto)
device address speed duplex link
state
nge0 0:14:4f:9b:bb:fe 1000Mb full up
attached
nge1 0:14:4f:9b:bb:ff 1000Mb full up
attached
And now I can configure it and use it and life is good. Why is this aggr device
not persisting across reboots, and why does "dladm show-aggr" not show it, but
refuse to let me create it until I delete something that "isn't there"?
Any help would be greatly appreciated.
Thanks-
John Tracy
This message posted from opensolaris.org
_______________________________________________
networking-discuss mailing list
[email protected]
