[Xen-users] bond/trunk issues

[Srija G <srijavg@xxxxxxxxx>]

Hi ,


I asked the following  question few  days back, but  did not  get  any reply. 

I am trying to set  bond/trunk with  mode=4, not successful still yet.  The  configuration  is  as
below  in the mail attached. 

After few  search  , found  rhel5.4  bonding module  has  few  issues.  Now the server is being upgraded
to rhel5.5.  But the issue  did not solve still yet. While rebooting the server   , in the dmesg  getting the
messages  as,

bonding: bond0: enslaving eth1 as a backup interface with a down link.
bnx2: eth1 NIC SerDes Link is Up, 1000 Mbps full duplex
bonding: bond0: link status definitely up for interface eth1.

It will be really appreciated  if someone helps me to figuring out the problems.

Thanks again



_______________________________________________________

Hi ,
  I am trying to configure  bond/trunk  on RHEL 5.4 86_64 OS.
 The bond/trunk works  when I am using mode=1, ie fault-tolerance (active-backup)
 But when I am trying to configure with mode=4, ie 802.3ad Dynamic link aggregation,
  it is not working. 

  Here is the configuration I did:

  -  Considering one  port for bonding ,  now only eth1 as it is a test server has only one port 

  -  the 3 subnets are being considered 12- 14

  -  Included bonding drivers.  and the /etc/modprobe.conf mentioned the parameters as

     alias bond0 bonding
     options bond0 mode=4 miimon=100 lacp_rate=1

  -  In /etc/sysconfig/network-scripts area created few config files as follows;

      ifcfg-bond0  :  DEVICE=bond0
                      BOOTPROTO=none
                      >                      Type=Ethernet
        

      ifcfg-eth1   :  DEVICE=eth1   
                      USERCTL=no
                      >                      MASTER=bond0
                      BOOTPROTO=none
                      HWADDR=xx:xx:xx:xx:xx:xx 
                      SLAVE=yes

    
      ifcfg-bond0.12 :  DEVICE=bond0.12
                        >                        TYPE=Ethernet
                        BOOTPROTO=static
                        IPADDR=xxx.xx.xx.xx
                        NETMASK=255.255.255.0
                        VLAN=yes

      Similarly created ifcfg-bond0.13 and ifcfg-bond.14 like ifcfg-bond0.12

   -  Here is the switch side configuration:

      interface Port-channel60
      description <server> trunk/channel
      switchport trunk allowed vlan 1,12-14,460
      switchport mode trunk
      spanning-tree portfast trunk
      end

      xxx-es-bcs1#sh run int g1/0/4        
      Building configuration...

      Current configuration : 192 bytes
       !
      interface GigabitEthernet1/0/4
      description <server> trunk
      switchport trunk allowed vlan 1,12-14,460
      switchport mode trunk
      channel-group 60 mode active
      spanning-tree portfast trunk
      end

   -  Kept  tag 460 for future use ..

   -  I am getting the file  in /proc/net/bonding/pbond0  not bond0,  here is the display

      Ethernet Channel Bonding Driver: v3.4.0 (October 7, 2008)

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

802.3ad info
LACP rate: fast
Active Aggregator Info:
        Aggregator ID: 1
        Number of ports: 1
        Actor Key: 17
        Partner Key: 1
        Partner Mac Address: 00:00:00:00:00:00

Slave Interface: eth1
MII Status: up
Link Failure Count: 0
Permanent HW addr: xx:xx:xx:xx:xx:xx
Aggregator ID: 1

    -  here is the display  of /proc/net/vlan/bond0.12


pbond0.12  VID: 12       REORDER_HDR: 1  dev->priv_flags: 81
         total frames received            0
          total bytes received            0
      Broadcast/Multicast Rcvd            0

      total frames transmitted           68
       total bytes transmitted        14925
            total headroom inc            0
           total encap on xmit            0
Device: pbond0
INGRESS priority mappings: 0:0  1:0  2:0  3:0  4:0  5:0  6:0 7:0
EGRESSS priority Mappings:

Similary  the other two subnets also.....

_________________________________________________
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users