vethx inteface support speed after bonding

hi, all

I have a DD6300, i have already configured veth0 – it’s bonded two eth3a, eth3c – they connect over fiber cable to SW Cisco 4500, two ports 10gb uplink,

On Sw Cisco 4500 : port-chanel up, BW 20 Gb/s



But my veth0 only 10Gb/s

Interface Name:

veth0

Auto Negotiate:

Disabled

Hardware Address:

00:60:16:85:22:c8

Duplex:

Full

Cable:

Fiber

Speed:

10 Gb/s

MTU:

1500

Supported Speeds:

10000

Any problem with my config, everybody help me to solve it ?

Here is my configuration :

lv@dd6300-backup# net show settings

port enabled state DHCP IP address netmask type additional setting

/prefix length

—– ——- ——- —- ————————– ————– —- ——————————-

ethMa yes running no 10.36.202.15 255.255.255.0 n/a

fe80::260:16ff:fe86:c7c6** /64

eth3a yes running n/a n/a n/a n/a bonded to veth0

eth3b no down no n/a n/a n/a

eth3c yes running n/a n/a n/a n/a bonded to veth0

eth3d no down no n/a n/a n/a

veth0 yes running no 10.36.202.16 255.255.255.0 n/a lacp hash xor-L2L3: eth3a,eth3c

fe80::260:16ff:fe85:22c8** /64

—– ——- ——- —- ————————– ————– —- ——————————-

** auto_generated IPv6 address

Thanks !

Related:

  • No Related Posts

Re: Does anyone know the meaning of “isi_stats_d: connect() to devid 0 : Connection reset by peer”?

I often see the following message in /var/log/messages of some nodes.



>isi_stats_d[1893]: connect() to devid 0 192.168.0.7: Connection reset by peer

I know “192.168.0.7” is corresponding to the internal failover IP of node 7.



>nfs06-data-kks-7: lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384

>nfs06-data-kks-7: inet6 ::1 prefixlen 128 zone 1

>nfs06-data-kks-7: inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 zone 1

>nfs06-data-kks-7: inet 127.0.0.1 netmask 0xff000000 zone 1

>nfs06-data-kks-7: inet 192.168.0.7 netmask 0xffffff00 zone 1



Does it indicate any failure of HW or S/W?

If anyone knows the meaning of such message, please kindly tell me.



The cluster is IQ108NL x 13 nodes cluster, running with OneFS 7.1.1.11.

Related:

  • No Related Posts

7022474: How to configure “external” network in network.json

Define an “external” network in network.json according to “Custom Network Configuration, Providing Access to External Networks” chapter in SUSE OpenStack Cloud 7 Deployment Guide.

“external” : {

“add_bridge” : false,

“vlan” : XXX,

“ranges” : {

“host” : {

“start” : “192.168.150.1”,

“end” : “192.168.150.254”

}

},

“broadcast” : “192.168.150.255”,

“netmask” : “255.255.255.0”,

“conduit” : “intf1”,

“subnet” : “192.168.150.0”,

“use_vlan” : true

}

To have this “external” network before configuring barclamps use ‘crowbarctl’ command for a particular node.

On admin node:

#crowbarctl network interface enable default d52-54-00-63-a1-01.example.com external

#crowbarctl network hostip allocate default d52-54-00-63-a1-01.example.com external host

Then on d52-54-00-63-a1-01.example.com:

#systemctl restart chef-client.service

Afterwards configure iscsi initiator on the nodes. Deploy pacemaker, rabbitmq and database barclamps.

Related:

  • No Related Posts

ShareFile Firewall Configuration and IP Address

Related:

  • No Related Posts