Sponsored Content
Operating Systems Linux Red Hat Extremely low throughput between AIX 7.2 and RHEL Maipo Post 303044537 by MadeInGermany on Tuesday 25th of February 2020 03:47:57 PM
Old 02-25-2020
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.
 

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
zeppelin(8)						       Maintenance Commands						       zeppelin(8)

NAME
zeppelin - ATM LAN Emulation client demon (LED) Zeppelin SYNOPSIS
zeppelin [-b ] [-c LECS_address | -s LES_address] [-e esi] [-n VLAN_name] [-m mesg_mask] [-l listen_address | selector] [-i interface_num- ber] [-I physical_interface_number] [-t 1516|1580|4544|9234|18190] [-1 ] [-2 ] [-p ] [-F logfile] [-f Fore_specific_name] DESCRIPTION
A LAN Emulation Client is an entity in an ATM endstation that performs data forwarding, address resolution and other control functions. It uses the LUNI interface when communicating with other components in emulated LANs. It provides upper protocol layers a MAC like interface similar to IEEE 802.3/Ethernet or IEEE 802.5/Token Ring LAN. LAN Emulation client code is divided into two parts: user space application LAN Emulation Demon called (LED) zeppelin(8), and the kernel component. Zeppelin is responsible for control operations needed in LAN Emulation clienthood. It forms the necessary VCCs and receives all the LE control frames and acts accordingly. It also controls the operation of the LEC kernel component. Linux LEC supports only Ethernet type of emulated LAN. SIGHUP causes restart of the LEC. All resources are released and zeppelin is started. OPTIONS
-b Run in background (i.e. in a forked child process) after initializing kernel interface. -c LECS_address ATM address of lecs(8) (Lan Emulation Configuration Server), if not set, Well-Known server address is used. -s LES_address ATM address of les(8) (Lan Emulation Server), can be used in bypassing configuration phase in joining emulated Lan i.e lecs address is not used. -e esi Mac address to use when communicating in Emulated LAN. E.g. 00:20:22:23:04:05 . -n VLAN_name Name of the virtual LAN to which joining is requested. This is used in LE_CONFIGURE_REQUEST to LECS or LE_JOIN_RESPONSE to LES, if configuration phase is bypassed. -m mesg_mask Sometimes one wants to know more what is happening in LE daemon e.g. when nothing works. This is a hexadecimal long value setting global message mask. 0 = No messages, ffff = All messages. -l listen_address | selector Local ATM address that zeppelin uses as local binding point in signalling. Use this if you are running more than one client or a set of LE servers. The local ATM address can be specified by either giving the full ATM address or the desired selector byte. -i interface_number Linux LEC supports up to 40+8 network interfaces. The interface_number tells zeppelin to which of these to attach. Ethernet type network interfaces are numbered from "lec0" to "lec39" and Token Ring interfaces are from "lec40" to "lec47". These parameters are tweakable during the kernel compile, see <linux/atmlec.h>. -I physical_interface_number The physical interface this LANE client should bind to. If your host has multiple ATM network cards, you can use this option to choose which card this zeppelin will use. -t MTU The MTU of ELAN to join. You need to also use ifconfig(8) to set the MTU of the LANE interface. -1 Run as LANEv1 client. This is the default. -2 Run as LANEv2 client. This is required by MPOA. -p Enable proxy. When started with this option, it is possible to bridge packets between ATM and Ethernet. That is, you can use LANE interfaces with normal bridging. See the Bridging mini-Howto for more info. -F logfile Instead of writing debug messages to stderr, write the messages to the file logfile. Use syslog as the file name to use the sys- log(3) facility. -f Fore specific name The LANE servers on Fore ATM switches can display a special name if a client can supply one. This name shows with command 'conf lane les show advanced'. TOKEN RING CONSIDERATIONS
A number of lec interfaces is reserved for Token Ring ELANs when the kernel is compiled with Token Ring (CONFIG_TR) support. See the dis- cussion about interface_number command line option above. The Linux Token Ring LANE client does not support bridging between legacy Token Ring and ATM parts of the ELAN, so using the -p option is not recommended. Token Ring support has received less testing than its Ethernet counterpart. FILES
/var/run/lec[interface number].pid The file containing the process id of zeppelin. BUGS
John Bonham died 1980 and Led Zeppelin broke. Please report any other bugs to Heikki Vatiainen <hessu@cs.tut.fi> AUTHORS
Marko Kiiskila, TUT <carnil@cs.tut.fi> and Heikki Vatiainen, TUT <hessu@cs.tut.fi> SEE ALSO
lecs(8), mpcd(8), atmsigd(8), les(8), qos(7) Linux Nov 29, 1999 zeppelin(8)
All times are GMT -4. The time now is 11:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy