Sponsored Content
Operating Systems Linux Red Hat Extremely low throughput between AIX 7.2 and RHEL Maipo Post 303044541 by Neo on Wednesday 26th of February 2020 12:13:40 AM
Old 02-26-2020
Quote:
Originally Posted by MadeInGermany
I wonder why the shown MTU is 1460 while the standard is 1500.
But if your LAN switch/router works better with 1460 then try to set it on the other box, too.

I remember a similar issue (severe packet loss), where all Linux systems had the standard MTU 1500. The LAN guy changed the MTU on the LAN switch (or router?), and that fixed it.
Google Cloud mandates this MTU:

Quote:
Gateway MTU vs. system MTU

You must configure your peer VPN gateway to use a MTU of no greater than 1460 bytes. A value of 1460 bytes is recommended because that matches the default MTU setting for Google Cloud VM instances.

The effective MTU for peer systems and Google Cloud VMs is typically lower than the MTU of your VPN gateway:

For TCP traffic, MSS clamping rewrites the SYN packet of the initial TCP handshake. This allows systems to dynamically adjust Maximum Segment Size (MSS) to accommodate encapsulation.

For UDP traffic, Path MTU Discovery (PMTUD) can negotiate smaller MTU sizes, under certain circumstances, provided that your firewall permits ICMP traffic.
REF: MTU considerations | Cloud VPN | Google Cloud
 

9 More Discussions You Might Find Interesting

1. IP Networking

Gigabit Link throughput

As a rule of thumb in doing calculations, what figure would you use in Mbytes/sec? I know the answer varies grealty on the topolgy of the network but I wonde what newteok engineers use a rough rule of thumb? Many thanks. (1 Reply)
Discussion started by: debd
1 Replies

2. IP Networking

How to improve throughput?

I have a 10Gbps network link connecting two machines A and B. I want to transfer 20GB data from A to B using TCP. With default setting, I can use 50% bandwidth. How to improve the throughput? Is there any way to make throughput as close to 10Gbps as possible? thanks~ :) (3 Replies)
Discussion started by: andrewust
3 Replies

3. UNIX for Dummies Questions & Answers

SOLARIS vs AIX vs RHEL

Hi I'm wondering what are the differences between SOLARIS, AIX and RHEL ? I would like to know in which operating system is best for what kind of implementation ? Why some companies use Solaris instead of e.g. AIX and etc. ? thx for help. (1 Reply)
Discussion started by: presul
1 Replies

4. AIX

Migrating RHEL 5 UNIX users to AIX

Hi, I'm able to migrate UNIX users/groups from Solaris to AIX (with same password using 13-char encrypted password from shadow file) but no luck with RHEL 5 to AIX. I see encrypted password in RHEL 5 is bit lengthier than 13-char. Is there any way to convert encrypted password such that same... (1 Reply)
Discussion started by: reddyr
1 Replies

5. AIX

High Runqueue (R) LOW CPU LOW I/O Low Network Low memory usage

Hello All I have a system running AIX 61 shared uncapped partition (with 11 physical processors, 24 Virtual 72GB of Memory) . The output from NMON, vmstat show a high run queue (60+) for continous periods of time intervals, but NO paging, relatively low I/o (6000) , CPU % is 40, Low network.... (9 Replies)
Discussion started by: IL-Malti
9 Replies

6. Red Hat

High RAM usage, extremely low swapping

Hi team I have three physical servers running on Red Hat Enterprise Linux Server release 6.2 with the following memory conditions: # cat /proc/meminfo | grep -i mem MemTotal: 8062888 kB MemFree: 184540 kB Shmem: 516 kB and the following swap conditions: ... (6 Replies)
Discussion started by: hedkandi
6 Replies

7. UNIX for Advanced & Expert Users

Help understanding differences between AIX and RHEL

I have started a new job which requires AIX admin skills, which I have, and RHEL skills. Does anyone have a cheat sheet that if I know how to solve the problem in AIX how would I do that in RHEL? I was an IBM pre-sales technical trying to keep sales guys honest - not possible. Any other links to... (5 Replies)
Discussion started by: SpenceSnyder
5 Replies

8. Shell Programming and Scripting

AIX to RHEL migration - awk treating 0e[0-9]+ as 0 instead of string issue

Greetings Experts, We are migrating from AIX to RHEL Linux. I have created a script to verify and report the NULLs and SPACEs in the key columns and duplicates on key combination of "|" delimited set of big files. Following is the code that was successfully running in AIX. awk -F "|" 'BEGIN {... (5 Replies)
Discussion started by: chill3chee
5 Replies

9. AIX

Question about shared filesystem btw AIX and RHEL

We found out that the Spectrum Scale (GPFS) doesnt support mix nodes (AIX and RHEL) on direct attached storage. Is there any other options besides NFS for mix O/S? Trying to avoid network type of shared filesystem which might end up high traffic on IO because we do run backup jobs on those... (0 Replies)
Discussion started by: kiasu
0 Replies
atmelan(8)						      System Manager's Manual							atmelan(8)

NAME
atmelan - Configures LAN-Emulation clients as network interfaces. SYNOPSIS
/usr/sbin/atmelan command arguments OPTIONS
This section is organized by the tasks you can perform with the atmelan command. Each task subsection provides the atmelan command syntax and the arguments to use to complete the tasks. Creating a LAN-Emulation Client Syntax: /usr/sbin/atmelan create driver=name [type=type] [mtu=mtu] [name=elan_name] [lecs=addr [,addr, addr, addr] | les=addr] [unit=unit_number | elan=unit_number] Creates a new LAN-Emulation Client (LEC) and configures it as a network interface. If no additional arguments are specified, the defaults are 802.3 type and an MTU of 1516 bytes. Specifies the physical interface with which to associate the new LEC. Specifies the interface type. The following types are supported: Ethernet/802.3. Specifies the message transfer unit (MTU) size. The following MTU sizes are sup- ported: 1516, 4544, 9234, and 18190. When specified with the name option, the emulated LAN must already be configured on the ATM switch to support the specified MTU size. If it is not configured for the specified MTU size, the request is ignored. Specifies the name of the emulated LAN to join. The emulated LAN name must already be configured on the ATM switch. If the name is not configured on the ATM switch, the LEC joins the default emulated LAN. Note You can join an emulated LAN on a switch only once for each adapter; do not join the same elan multiple times from the same adapter. If you want to join the same emulated LAN on the same switch, you must install another adapter and join the emulated LAN from it. Specifies that the LEC connect to the LAN-Emulation Configuration Server (LECS) at the ATM address specified by the addr arguments for the emulated LAN configuration. You can specify up to 4 addresses. The LEC tries the addresses in order until a successful configuration has been completed. If all addresses fail, the "well known address" is tried before the process begins again. If no lecs option is specified (default), the LEC connects to the LECS at the "well known address". Do not use the lecs option with the les option. Specifies that the LEC go directly to the LAN-Emulation Server (LES) at the ATM address specified by addr argument and bypass the configuration phase. If this argument is not specified, the LEC contacts a LAN-Emulation Configuration Server (LECS) to obtain a LES address. Do not use the les option with the lecs option. Specifies a LEC interface unit number. Specifies an ELAN unit number. For example, to create an emulated LAN interface using Ethernet frame format and Fiber Distributed Data Interface (FDDI) frame sizes, enter: # atmelan create driver=lta0 mtu=4544 To create an emulated LAN interface that bypasses the configuration phase and directly contacts a LAN-Emulation Server (LES), enter: # atmelan create les=LES_A The ATM address is an alias that is in the /etc/atmhosts file. Detaching a LEC Interface from an ATM Network Syntax: /usr/sbin/atmelan detach unit=unit_number | elan=unit_number Detaches a LEC interface specified by either unit or elan arguments from an ATM network. Specifies a LEC interface unit number. The unit_number is obtained by the netstat -i command. Specifies an ELAN unit number. The unit_number is obtained by the netstat -i command. Attaching a LEC Interface to an ATM Network Syntax: /usr/sbin/atmelan attach driver=name unit=unit_number | elan=unit_number [lecs=addr [,addr, addr, addr] | les=addr] [name=elan_name] [type=type] [mtu=mtu] Attaches the specified, previously detached LEC network interface to an ATM network. After the LEC interface is attached, issue the ifcon- fig elanx up command to configure the interface. Specifies the physical interface with which to associate the LEC. Specifies a LEC inter- face unit number. This is the unit number that was previously detached. Specifies an ELAN unit number. This is the unit number that was previously detached. Specifies that the LEC connect to the LAN-Emulation Configuration Server (LECS) at the ATM address specified by the addr arguments for the emulated LAN configuration. You can specify up to 4 addresses. The LEC tries the addresses in order until a suc- cessful configuration has been completed. If all addresses fail, the "well known address" is tried before the process begins again. If no lecs option is specified (default), the LEC connects to the LECS at the "well known address". Do not use the lecs option with the les option. Specifies that the LEC go directly to the LAN-Emulation Server (LES) at the ATM address specified by addr argument and bypass the configuration phase. If this argument is not specified, the LEC contacts a LAN-Emulation Configuration Server (LECS) to obtain a LES address. Do not use the les option with the lecs option. Specifies the name of the emulated LAN to join. The emulated LAN name must already be configured on the ATM switch. If the name is not configured on the ATM switch, the LEC joins the default emulated LAN. Speci- fies the interface type. The following types are supported: Ethernet/802.3. Specifies the message transfer unit (MTU) size. The following MTU sizes are supported: 1516, 4544, 9234, and 18190. When specified with the name option, the emulated LAN must already be configured on the ATM switch to support the specified MTU size. If it is not configured for the specified MTU size, the request is ignored. Displaying State and Counters for an LEC Interface Syntax: /usr/sbin/atmelan show | status [unit=unit_number] Shows the state and counters for a LEC interface. If no unit number is specified, information for LEC unit 0 (elan0) is displayed. Shows the state and counters for a LEC interface. If no unit number is specified, information for LEC unit 0 (elan0) is displayed. Specifies a LEC interface unit number, if you want to display LEC information for LEC unit numbers other than unit 0 (elan0). The unit_number is obtained by the netstat -i command. For example, unit 0 is elan0, unit 1 is elan1, and so on. DESCRIPTION
The atmelan command creates and configures LAN-Emulation Clients (LEC) as network interfaces. The first interface created appears as elan0, the second as elan1, and so on. The atmelan command can also show counters, parameters, and the state of each LEC. SEE ALSO
Commands: atmconfig(8), atmsig(8), learp(8) Files: atmhosts(4) Asynchronous Transfer Mode Network Administration atmelan(8)
All times are GMT -4. The time now is 12:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy