Sponsored Content
Operating Systems AIX Pb Etherchannel/deconnexion port reseau Post 302409022 by Trunk on Wednesday 31st of March 2010 04:33:04 AM
Old 03-31-2010
Pb Etherchannel/deconnexion port reseau

Hello,

On a partition with AIX 5300-11-01-0944.
1 etherchannel ent9 with aggregation ent3/ent7.

Code:
# lsdev |grep ent
...
ent3            Available 07-01    4-Port 10/100/1000 Base-TX PCI-Express Adapter (14106803)
...
ent7            Available 0A-01    4-Port 10/100/1000 Base-TX PCI-Express Adapter (14106803)
...
ent9            Available          EtherChannel / IEEE 802.3ad Link Aggregation

When I physically disconnect the cable from ent3 and that I reconnect it, it does not go up. The led with the back of the chart remain extinct.
With the restarting of the partition all is OK.
Below some infos on the state of the etherchannel and the errpt.

After deconnection:
Code:
# errpt |pg
EC0BCCD4   0331011510 T H ent3           ETHERNET DOWN

# entstat -d ent9
ETHERNET STATISTICS (ent3) :
....
Link Status: UNKNOWN
Media Speed Selected: 1000 Mbps Full Duplex
Media Speed Running: Unknown

# errpt |pg
F3931284   0331011610 I H ent3           ETHERNET NETWORK RECOVERY MODE
EC0BCCD4   0331011510 T H ent3           ETHERNET DOWN

# entstat -d ent9
ETHERNET STATISTICS (ent3) :
....
Link Status: Up
Media Speed Selected: 1000 Mbps Full Duplex
Media Speed Running: 1000 Mbps Full Duplex

Have you an idea ?
Thanks.

Last edited by zxmaus; 04-20-2010 at 06:38 AM.. Reason: added code tags
 

10 More Discussions You Might Find Interesting

1. AIX

EtherChannel network redundance problem

Problem description: On the condition of EtherChannel function of AIX, when the data exchange between the nodes on the network, there sometimes lost datat packets and cause the application failed. Once we deconfig EtherChannel and use the single adapter configuration, the application works... (0 Replies)
Discussion started by: Frank2004
0 Replies

2. AIX

Problem with Etherchannel

I'm trying to configure Etherchannel on AIX 5.3 and I'm having some problems. I am aggregating both of the onboard NIC's (ent0 and ent1) into a new adapter ent2 for failover reasons obviously. At first I was experiencing a problem where about 50% of all my packets would be dropped. Then after... (4 Replies)
Discussion started by: acascianelli
4 Replies

3. AIX

AIX / Etherchannel / VLANs

I have 1 AIX server, 4 dual ported fiber attached ethernet cards and 4 VLANS coming in. Is it possible to present those 8 ports as 1 IP address using etherchannel? Thanks. (5 Replies)
Discussion started by: jwholey
5 Replies

4. AIX

Can EtherChannel be a redundancy config?

I have one p5 server, no lpar, 2 physical network adapter, bundle as one EtherChannel. The two 2 physical network adapter connect to 2 network switches. How to make this as a redundancy config? Current is if one physical network adapter down, the seond one will go through the network. but if... (2 Replies)
Discussion started by: rainbow_bean
2 Replies

5. AIX

EtherChannel interface ping pelicularity

I have few AIX servers in my data center, which have their EtherChannel configured to have a fat pipe (active/active) and a nagios server to monitor the server uptimes. Nagios server pings every server in the data center and we have pretty much every known unix flavor in this data center. When... (3 Replies)
Discussion started by: thenomad
3 Replies

6. AIX

Aggregated Etherchannel

Hi, I have a AIX5.3 P6-520 with 8x1Gb Ethernet ports with possible connections to 2 CISCO 2960 switches. I can create 8023ad Etherchannels which work correctly with the switches (I have set up for LACP passive and a valid channels) But can create 2x 8023ad 4Gb Etherchannels with no backups.... (2 Replies)
Discussion started by: spitzie
2 Replies

7. AIX

Etherchannel failover testing

Hi Guys, I am trying to test an etherchannel failover and switchback. I did failover from primary to backup adapter, but now I am not able to switch it back to primary. phcxxxxx:/ > entstat -d ent4 | grep Active Active channel: backup adapter ... (1 Reply)
Discussion started by: snchaudhari2
1 Replies

8. Linux

Problème d'interface réseau

bonjour, j'ai un serveur Linux ayant 2 interfaces eth0 et eth1. j'ai configuré deux adresses IP de deux réseaux différents sur les 2 interfaces, et je les ai connecté sur 2 commutateurs différents. l'adresse IP de eth0 répond sans problème au ping des équipement de son réseau d'appartenance, malheureusement cela... (1 Reply)
Discussion started by: cerco
1 Replies

9. Solaris

How to find port number wwn of particular port on dual port HBA,?

please find the below o/p for your reference bash-3.00# fcinfo hba-port HBA Port WWN: 21000024ff295a34 OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 375-3356-02 Firmware Version: 05.03.02 FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies

10. AIX

PowerVM SEA etherchannel performance ?

Hello, POWER7 machine. 4 x 1Gbit port ethernet adapter is dedicated to vios. 8023ad etherchannel is created using those 4 ports. Etherchannel adapter is shared to lpars using SEA. If I test network performance directly from vios partition (using iperf) I'm geting nice 4Gbit throughput. But if... (3 Replies)
Discussion started by: vilius
3 Replies
EM(4)							   BSD Kernel Interfaces Manual 						     EM(4)

NAME
em -- Intel(R) PRO/1000 Gigabit Ethernet adapter driver SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device em Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_em_load="YES" DESCRIPTION
The em driver provides support for PCI Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 81572, 82573, and 82574 Ethernet controller chips. The driver supports Transmit/Receive checksum off- load and Jumbo Frames on all but 82542-based adapters. Furthermore it supports TCP segmentation offload (TSO) on all adapters but those based on the 82543, 82544 and 82547 controller chips. The identification LEDs of the adapters supported by the em driver can be controlled via the led(4) API for localization purposes. For further hardware information, see the README included with the driver. For questions related to hardware requirements, refer to the documentation supplied with your Intel PRO/1000 adapter. All hardware require- ments listed apply to use with FreeBSD. Support for Jumbo Frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the adapter to receive and transmit Jumbo Frames. The maximum MTU size for Jumbo Frames is 16114. This driver version supports VLANs. The em driver supports the following media types: autoselect Enables auto-negotiation for speed and duplex. 10baseT/UTP Sets 10Mbps operation. Use the mediaopt option to select full-duplex mode. 100baseTX Sets 100Mbps operation. Use the mediaopt option to select full-duplex mode. 1000baseSX Sets 1000Mbps operation. Only full-duplex mode is supported at this speed. 1000baseTX Sets 1000Mbps operation. Only full-duplex mode is supported at this speed. The em driver supports the following media options: full-duplex Forces full-duplex operation half-duplex Forces half-duplex operation. Only use mediaopt to set the driver to full-duplex. If mediaopt is not specified, the driver defaults to half-duplex. For more information on configuring this device, see ifconfig(8). HARDWARE
The em driver supports Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 82572, 82573, and 82574 controller chips: o Intel PRO/1000 CT Network Connection (82547) o Intel PRO/1000 F Server Adapter (82543) o Intel PRO/1000 Gigabit Server Adapter (82542) o Intel PRO/1000 GT Desktop Adapter (82541PI) o Intel PRO/1000 MF Dual Port Server Adapter (82546) o Intel PRO/1000 MF Server Adapter (82545) o Intel PRO/1000 MF Server Adapter (LX) (82545) o Intel PRO/1000 MT Desktop Adapter (82540) o Intel PRO/1000 MT Desktop Adapter (82541) o Intel PRO/1000 MT Dual Port Server Adapter (82546) o Intel PRO/1000 MT Quad Port Server Adapter (82546EB) o Intel PRO/1000 MT Server Adapter (82545) o Intel PRO/1000 PF Dual Port Server Adapter (82571) o Intel PRO/1000 PF Quad Port Server Adapter (82571) o Intel PRO/1000 PF Server Adapter (82572) o Intel PRO/1000 PT Desktop Adapter (82572) o Intel PRO/1000 PT Dual Port Server Adapter (82571) o Intel PRO/1000 PT Quad Port Server Adapter (82571) o Intel PRO/1000 PT Server Adapter (82572) o Intel PRO/1000 T Desktop Adapter (82544) o Intel PRO/1000 T Server Adapter (82543) o Intel PRO/1000 XF Server Adapter (82544) o Intel PRO/1000 XT Server Adapter (82544) LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5). hw.em.rxd Number of receive descriptors allocated by the driver. The default value is 256. The 82542 and 82543-based adapters can handle up to 256 descriptors, while others can have up to 4096. hw.em.txd Number of transmit descriptors allocated by the driver. The default value is 256. The 82542 and 82543-based adapters can handle up to 256 descriptors, while others can have up to 4096. hw.em.rx_int_delay This value delays the generation of receive interrupts in units of 1.024 microseconds. The default value is 0, since adapters may hang with this feature being enabled. hw.em.rx_abs_int_delay If hw.em.rx_int_delay is non-zero, this tunable limits the maximum delay in which a receive interrupt is generated. hw.em.tx_int_delay This value delays the generation of transmit interrupts in units of 1.024 microseconds. The default value is 64. hw.em.tx_abs_int_delay If hw.em.tx_int_delay is non-zero, this tunable limits the maximum delay in which a transmit interrupt is generated. DIAGNOSTICS
em%d: Unable to allocate bus resource: memory A fatal initialization error has occurred. em%d: Unable to allocate bus resource: interrupt A fatal initialization error has occurred. em%d: watchdog timeout -- resetting The device has stopped responding to the network, or there is a problem with the network connection (cable). SUPPORT
For general information and support, go to the Intel support website at: http://support.intel.com. If an issue is identified with the released source code on the supported kernel with a supported adapter, email the specific information related to the issue to <freebsdnic@mailbox.intel.com>. FILES
/dev/led/em* identification LED device nodes EXAMPLES
Make the identification LED of em0 blink: echo f2 > /dev/led/em0 Turn the identification LED of em0 off again: echo 0 > /dev/led/em0 SEE ALSO
altq(4), arp(4), igb(4), led(4), netintro(4), ng_ether(4), polling(4), vlan(4), ifconfig(8) HISTORY
The em device driver first appeared in FreeBSD 4.4. AUTHORS
The em driver was written by Intel Corporation <freebsdnic@mailbox.intel.com>. BUGS
Hardware-assisted VLAN processing is disabled by default. You can enable it on an em interface using ifconfig(8). BSD
May 14, 2010 BSD
All times are GMT -4. The time now is 02:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy