I note similar, but slightly different reports in previous threads.  My setup 
in question includes Cisco 4900 series switches and Sun T1000 and T2000 servers 
connected at 1000 mb/s.  Servers are running Solaris 10 Update 3 (11/06) with 
the current recommended and security patch cluster.  We are not using jumbo 
frames, so the reported bug noted in previous threads shouldn't be affecting us.

This works:

- single port single VLAN (a.k.a. access mode on the Cisco)

- single port multiple VLANs (a.k.a. trunked VLANS on the Cisco) - but only 
after first configuring the simple setup above.  Without doing so, the Cisco 
doesn't seem to "see" the Sun system's MAC address and will not work.  One 
setup using this work-around, it survives reboots of both the Sun servers and 
the Cisco switches.

- two aggregated ports with a single VLAN

This does not work:

- two aggregated ports with multiple VLANS - does not work even trying the 
above noted "trick" of first using a single VLAN "access mode".  Turning LACP 
mode to active for the aggr doesn't seem to help (rebooted after making change 
too).

I've pasted some command output below.   The first aggr interface works fine, 
and  has a single IP address.  The second aggr does not work, even though the 
same VLANS work on both ports when configured as individual devices.  Any ideas?

Cheers,

-Nathan

# dladm show-aggr -L
key: 1 (0x0001) policy: L4      address: 0:14:4f:7e:77:2a (auto)
                LACP mode: off  LACP timer: short
    device    activity timeout aggregatable sync  coll dist defaulted expired
    e1000g0   passive  short   yes          no    no   no   no        no
    e1000g1   passive  short   yes          no    no   no   no        no
key: 2 (0x0002) policy: L4      address: 0:14:4f:7e:77:2c (auto)
                LACP mode: active       LACP timer: short
    device    activity timeout aggregatable sync  coll dist defaulted expired
    e1000g2   active   short   yes          yes   yes  yes  no        no
    e1000g3   active   short   yes          yes   yes  yes  no        no

# dladm show-aggr -s
key: 1  ipackets  rbytes      opackets   obytes          %ipkts %opkts
           Total        1813      130595      601       50169
           e1000g0      179       14312       235       19091           9.9     
39.1
           e1000g1      1634      116283      366       31078           90.1    
60.9
key: 2  ipackets  rbytes      opackets   obytes          %ipkts %opkts
           Total        20732     1771094     743       92994
           e1000g2      11277     951448      388       47816           54.4    
52.2
           e1000g3      9455      819646      355       45178           45.6    
47.8

# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 
index 1
        inet 127.0.0.1 netmask ff000000
aggr1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 10.52.106.11 netmask ffffff00 broadcast 10.52.106.255
        ether 0:14:4f:7e:77:2a
aggr210002: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 
index 3
        inet 10.48.210.101 netmask ffffff00 broadcast 10.48.210.255
        ether 0:14:4f:7e:77:2c
aggr220002: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 
index 4
        inet 10.50.220.101 netmask ffffff00 broadcast 10.50.220.255
        ether 0:14:4f:7e:77:2c
aggr230002: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 
index 5
        inet 10.52.230.101 netmask ffffff00 broadcast 10.52.230.255
        ether 0:14:4f:7e:77:2c
aggr240002: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 
index 6
        inet 10.54.240.101 netmask ffffff00 broadcast 10.54.240.255
        ether 0:14:4f:7e:77:2c
 
 
This message posted from opensolaris.org
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to