Sponsored Content
Full Discussion: ethernet bonding
Operating Systems Linux ethernet bonding Post 302672345 by zaxxon on Monday 16th of July 2012 09:09:25 AM
Old 07-16-2012
As far as I do remember it depends a bit how to set it up on which derivate of Linux you are using. Config files etc. may be different a bit.
You might additionally have to use the command ifenslave to attach/detach NICs to a bonding device.

I move this thread to the Linux area - don't see a relation to "Infrastructure Monitoring".
 

10 More Discussions You Might Find Interesting

1. IP Networking

Bonding Internet Connections

I’m familiar with load balancing.. but Is it possible to actually bond multiple DSL lines together? I hear of ways to bond using MLPPP but that requires support from an ISP. Is there a way to actually bond without support from my ISP, or use say a cable modem and a DSL line together for faster... (0 Replies)
Discussion started by: harley313
0 Replies

2. AIX

vio server ethernet to vio client ethernet(concepts confusing)

Hi In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID. Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies

3. Red Hat

IP Bonding

Hi, What is IP bonding in Linux. What are its advantages How to create a IP bonding in redhat Linux. (1 Reply)
Discussion started by: chetansingh23
1 Replies

4. IP Networking

Bonding of IP tunnels

Hello. Our Company is spreaded over Germany. There are main offices an branch offices. These offices are mostly connecte via multiple sdsl. We build a IPSEC VPN Infrastructure using Aastaro Security Gateways appliances. It seemed that only one VPN Connetion between to offices could be... (0 Replies)
Discussion started by: mschwadorf
0 Replies

5. Red Hat

RHEL 5.5 NIC Bonding

I am new to linux. I have a falconstor CDP installation which runs on RHEL 5.5 (Tikanga). There is a vendor option to bond nics in either 802.3ad or round robin, I choose 802.3ad. The server is connected to a Cisco 3750 switch. The problem is dropped packets and eth03 wont come up in the PO... (0 Replies)
Discussion started by: tjcooper
0 Replies

6. Red Hat

Bonding a Bond with LACP

Does anyone know if it's possible to bond two bonds together? My situation is I have two older Cisco switches that cannot carry a LACP (bond level 4) aggregated between them, but separate aggregates can be setup on the switches themselves. In order to have redundancy of two switches I would... (0 Replies)
Discussion started by: christr
0 Replies

7. Red Hat

BONDING with Flapping issue!

Hi team, I'm running into a problem configuring bonding on an CentOS 64bit on DELL Server. I'm connecting eth0 and eth1 to a Cisco 2948 (CatOS 8.1(3)) and receiving flapping notices. The ethernet address is that of the primary interface. I have tried several different modes,... (3 Replies)
Discussion started by: leo_ultra_leo
3 Replies

8. IP Networking

Is bond0 ready and a bonding interface? - 4G Bonding Router Problems (RPI)

HI all, First post on the forum, and my first proper project on the Paspberry Pi, so sorry if this is in the wrong place. I am trying to turn my Pi in to a 3G/4G Bonding router. I have been researching and trying this for a week or so now. The basic plan is to have up to 6 ZTE MF823 USB... (0 Replies)
Discussion started by: elliottlc
0 Replies

9. Red Hat

Network Bonding Issue

I have one production system where my customized application runs.The applications require seamless network connectivity with different machines connected in LAN and WAN. As these applications are very critical, it is very much required to have a seamless network activity.The applications are... (4 Replies)
Discussion started by: Anjan Ganguly
4 Replies

10. Red Hat

Network bonding

Dear All , Very recently we have configured Network bonding in our Linux Server Redhat Linux 5.x. After configuring , we restarted the network services , the link was down after that , we could not login in to the Server. So after that , we logged in to console and tried to... (2 Replies)
Discussion started by: jegaraman
2 Replies
MKSWAP(8)						     Linux Programmer's Manual							 MKSWAP(8)

NAME
mkswap - set up a Linux swap area SYNOPSIS
mkswap [-c] [-vN] [-f] [-p PSZ] device [size] DESCRIPTION
mkswap sets up a Linux swap area on a device or in a file. (After creating the swap area, you need the swapon command to start using it. Usually swap areas are listed in /etc/fstab so that they can be taken into use at boot time by a swapon -a command in some boot script.) The device argument will usually be a disk partition (something like /dev/hda4 or /dev/sdb7) but can also be a file. The Linux kernel does not look at partition Id's, but many installation scripts will assume that partitions of hex type 82 (LINUX_SWAP) are meant to be swap par- titions. (Warning: Solaris also uses this type. Be careful not to kill your Solaris partitions.) The size parameter is superfluous but retained for backwards compatibility. (It specifies the desired size of the swap area in 1024-byte blocks. mkswap will use the entire partition or file if it is omitted. Specifying it is unwise - a typo may destroy your disk.) The PSZ parameter specifies the page size to use. It is almost always unnecessary (even unwise) to specify it, but certain old libc ver- sions lie about the page size, so it is possible that mkswap gets it wrong. The symptom is that a subsequent swapon fails because no swap signature is found. Typical values for PSZ are 4096 or 8192. Linux knows about two styles of swap areas, old style and new style. The last 10 bytes of the first page of the swap area distinguishes them: old style has `SWAP_SPACE', new style has `SWAPSPACE2' as signature. In the old style, the rest of this first page was a bit map, with a 1 bit for each usable page of the swap area. Since the first page holds this bit map, the first bit is 0. Also, the last 10 bytes hold the signature. So, if the page size is S, an old style swap area can describe at most 8*(S-10)-1 pages used for swapping. With S=4096 (as on i386), the useful area is at most 133890048 bytes (almost 128 MiB), and the rest is wasted. On an alpha and sparc64, with S=8192, the useful area is at most 535560992 bytes (almost 512 MiB). The old setup wastes most of this bitmap page, because zero bits denote bad blocks or blocks past the end of the swap space, and a simple integer suffices to indicate the size of the swap space, while the bad blocks, if any, can simply be listed. Nobody wants to use a swap space with hundreds of bad blocks. (I would not even use a swap space with 1 bad block.) In the new style swap area this is precisely what is done. The maximum useful size of a swap area now depends on the architecture. It is roughly 2GiB on i386, PPC, m68k, ARM, 1GiB on sparc, 512MiB on mips, 128GiB on alpha and 3TiB on sparc64. Note that before 2.1.117 the kernel allocated one byte for each page, while it now allocates two bytes, so that taking a swap area of 2 GiB in use might require 2 MiB of kernel memory. Presently, Linux allows 32 swap areas (this was 8 before Linux 2.4.10). The areas in use can be seen in the file /proc/swaps (since 2.1.25). mkswap refuses areas smaller than 10 pages. If you don't know the page size that your machine uses, you may be able to look it up with "cat /proc/cpuinfo" (or you may not - the con- tents of this file depend on architecture and kernel version). To setup a swap file, it is necessary to create that file before initializing it with mkswap , e.g. using a command like # dd if=/dev/zero of=swapfile bs=1024 count=65536 Note that a swap file must not contain any holes (so, using cp(1) to create the file is not acceptable). OPTIONS
-c Check the device (if it is a block device) for bad blocks before creating the swap area. If any are found, the count is printed. -f Force - go ahead even if the command is stupid. This allows the creation of a swap area larger than the file or partition it resides on. On SPARC, force creation of the swap area. Without this option mkswap will refuse to create a v0 swap on a device with a valid SPARC superblock, as that probably means one is going to erase the partition table. -p PSZ Specify the page size to use. -v0 Create an old style swap area. -v1 Create a new style swap area. If no -v option is given, mkswap will default to new style, but use old style if the current kernel is older than 2.1.117 (and also if PAGE_SIZE is less than 2048). The new style header does not touch the first block, so may be preferable, in case you have a boot loader or disk label there. If you need to use both 2.0 and 2.2 kernels, use the -v0 option when creating the swapspace. SEE ALSO
fdisk(8), swapon(8) Linux 2.2.4 25 March 1999 MKSWAP(8)
All times are GMT -4. The time now is 05:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy