Sponsored Content
Operating Systems Solaris IPMP on Private interconnects Post 302526583 by puravc on Wednesday 1st of June 2011 01:41:04 AM
Old 06-01-2011
ipmp on private interconnects

Hi mack1982,

Can you please explain me about how to achieve a fully redundant private network with 2 dedicated switches (so that neither the port, nor the cables, nor the switches become a single point of failure)?

We connect eth2 from both nodes to switch1 and eth2 from both nodes to switch2. So 2 completely redundant paths. How should we proceed from here? We configure IPMP on these 2 interfaces. But it does not look correct.
So should there be a cross or straight cable between switch1 & switch2?
Should the IP Address assigned to 4 ports (eth2 & eth3 on both nodes) should belong to the same LAN or different LAN? i.e. all 4 from 192.168.2.x or eth2 has to be from 192.168.2.x and eth3 has to be from 192.168.3.x? If 2 diff. LAN then will IPMP work on it? If 1 LAN then we would need a cross cable between switches to make it 1 network else all 4 IPs cant ping/see each other. So as you see, i am confused and it would be great if you can help me understand this.

many thanks.
 

10 More Discussions You Might Find Interesting

1. IP Networking

private network to private network gateway

i have one private network with one ip address, and i have a seperate network on a seperate ip address. now, each network is behind a firewall/router. now what i want to do is be able to access one server on the second network from a computer on the first., but with the private ip address, (this... (2 Replies)
Discussion started by: norsk hedensk
2 Replies

2. Solaris

Ipmp

Hi All, Kindly help me in configuring IPMP or guid me to some link, tried goggling however no luck. Thanks in anticipation (1 Reply)
Discussion started by: kumarmani
1 Replies

3. Solaris

IPMP config

Hi All, I have unplumbed one interface. after that ifconfig -a shows that lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 ... (7 Replies)
Discussion started by: jegaraman
7 Replies

4. Solaris

IPMP questions

Probe-based IPMP active - active Probe-based IPMP active - passive Link-based only active -standby ???? What are differences between Probe-based IPMP active - passive anddd Link-based only active -standby ???!!! For example in active active probe-based IPMP there are lets... (6 Replies)
Discussion started by: samar
6 Replies

5. Solaris

setting up IPMP

Guide me in setting up IPMP on solaris 10 box . my system has 2 physical interface bge0 - not used bge1 - 10.10.10.10 bge1:1 - 10.10.10.11 please guide , how can i implement IPMP on this server , how many additional test ip is required ? , as 2 ip's are configured on bge1 interface ,... (3 Replies)
Discussion started by: skamal4u
3 Replies

6. Solaris

IPMP Configuration

Hi all, Currently i got a server which had two interface. I had study the <SystemAdministration Guide: IP> but still donno what is the correct step to configure it. Can u all help me on it? thanks # ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index... (6 Replies)
Discussion started by: SmartAntz
6 Replies

7. Solaris

IPMP Configuration

Dear All, I have configured IPMP in one of my SUN machine which is having solros 9 version. I have updated all files like /etc/hosts,/etc/hostname.ce0 and /etc/hostname.ce1 and rebooted the server. But IP's are not mounted which i have given in /etc/hosts file. Please find the below ifconfig... (6 Replies)
Discussion started by: lbreddy
6 Replies

8. Solaris

ipmp testing

Please tell me how to configure IPMP in vmware what is the basic working concept of IPMP. please help me (1 Reply)
Discussion started by: sijocg
1 Replies

9. Solaris

IPMP problem

Hi all i had two interface ce0 and ce5 but when i run the ifconfig, it show me alot of extra virtual interface, may i know how to remove it? # ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 ce0:... (2 Replies)
Discussion started by: SmartAntz
2 Replies

10. Solaris

Can we configure link based IPMP in private connectivity in Oracle RAC

Hi I would like to know whether we can configure link based IPMP in private connectivity in Oracle RAC Regarsd ---------- Post updated at 04:35 PM ---------- Previous update was at 04:27 PM ---------- Here I am taking about in case of private connectivity through cross cable (6 Replies)
Discussion started by: sb200
6 Replies
FCOEADM(8)							  Open-FCoE Tools							FCOEADM(8)

NAME
fcoeadm - The Open-FCoE Administration Tool SYNOPSIS
fcoeadm [-m|--mode fabric|vn2vn] -c|--create ethX fcoeadm -d|--destroy ethX fcoeadm -r|--reset ethX fcoeadm -S|--Scan [ethX] fcoeadm -i|--interface [ethX] fcoeadm -f|--fcfs [ethX] fcoeadm -t|--target [ethX] fcoeadm -l|--lun [ethX] fcoeadm -s|--stats ethX [interval] fcoeadm -b|--lesb ethX [interval] fcoeadm -h|--help fcoeadm -v|--version DESCRIPTION
The fcoeadm utility is the Fibre Channel over Ethernet (FCoE) management tool for the Open-FCoE project. fcoeadm may be used to create, destroy, and reset an FCoE instance on a given network interface. For these operations fcoeadm sends a command to a running fcoemon process, via a socket interface. fcoemon will then perform the requested operation. fcoeadm also provides operations to query information about FCoE instances, including interface information, target information, LUN information, and port statistics. For much of this information, fcoeadm relies on the libhbalinux implementation of the HBA API. Only one operation may be given on a command. OPTIONS
-m, --mode fabric|vn2vn Used together with the create option to control the FCoE mode of operation. The mode defaults to fabric but this option allows the selection of vn2vn mode. OPERATIONS
-c, --create ethX Creates an FCoE instance based on the specified network interface. Note that if there is not an fcoemon configuration file for the interface (/etc/fcoe/cfg-ethX, see fcoemon), then the created FCoE instance will not require DCB. -d, --destroy ethX Destroys the FCoE instance on the specified network interface. This will not destroy FCoE instances created by fipvlan. -r, --reset ethX Resets the FCoE instance on the specified network interface. This will not reset FCoE instances created by fipvlan. -S, --Scan ethX Rescan for new targets and LUNs on the provided instance. This command will not rescan any NPIV instances created on the same port. This will not rescan any FCoE instance created by fipvlan. -i, --interface [ethX] Show information about the FCoE instance on the specified network interface, or all FCoE instances if no network interface is specified. -f, --fcfs [ethX] Show information about the discovered Fibre Channel Forwarders (FCFs) on the specified network interface, or all discovered FCFs if no network interface is specified. -t, --target [ethX] Show information about the discovered targets associated with the FCoE instance on the specified network interface. If no network interface is specified, information about discovered targets from all FCoE instances will be shown. -l, --lun [ethX] Show detailed information about the discovered SCSI LUNs associated with the FCoE instance on the specified network interface. If no network interface is specified, information about SCSI LUNs from all FCoE instances will be shown. -s, --stats ethX [interval] Show the statistics (including FC4 statistics) of the FCoE connection on the specified network interface. The information will be displayed repeatedly until the user cancels the command. The statistics will be printed every specified interval (in seconds). interval should be specified as a whole number greater than 0. If interval is not specified, a default interval of one second is used. -b, --lesb ethX [interval] Show the Link Error Statistics Block (LESB) of the FCoE connection on the specified network interface. The information will be displayed repeatedly until the user cancels the command. The LESB statistics will be printed every specified interval (in seconds). interval should be specified in whole integers greater than 0. If the interval is not specified, a default interval of one second is used. -h, --help Displays the usage message of the fcoeadm command. -v, --version Displays the version of the fcoeadm command. INTERFACE NAMES
The actual name for ethX depends on the AUTO_VLAN setting in the fcoemon interface configuration (/etc/fcoe/cfg-ethX, see fcoemon). If AUTO_VLAN is set to yes, the interface name ethX references the network device itself. If AUTO_VLAN is set to no, the interface name ethX references the VLAN device. EXAMPLES
Creates an FCoE instance on eth2.101 fcoeadm -c eth2.101 Creates an FCoE VN2VN instance on eth2.101 fcoeadm -m vn2vn -c eth2.101 Destroys the FCoE instance on eth2.101 fcoeadm -d eth2.101 Resets the FCoE instance on eth2.101 fcoeadm -r eth2.101 Show the information of all the adapters and their ports having FCoE instances created fcoeadm -i Show the information of all FCoE instances on interface eth3. fcoeadm -i eth3 Show the information of all the discovered targets from all the ports having FCoE instances created (they may be on different adapter cards). A brief listing of discovered LUNs are listed after the target they are associated with, if any fcoeadm -t Show the information of all the discovered targets from a given port (eth3) having FCoE instance created. A brief listing of discovered LUNs are listed after each target they are associated with, if any fcoeadm -t eth3 Show the detailed information of all the LUNs discovered on all FCoE connections fcoeadm -l Show the detailed information of all the LUNs associated with a specific interface fcoeadm -l eth3.101 Show the statistics information of a specific port eth3 having FCoE instances created. The statistics are displayed one line per time interval. The default interval is one second if an interval is not specified fcoeadm -s eth3 fcoeadm -s eth3 3 SEE ALSO
fcoemon(8) SUPPORT
fcoeadm is part of the fcoe-utils package, maintained through the Open-FCoE project. Resources for both developers and users can be found at the Open-FCoE website http://open-fcoe.org/ Open-FCoE 11/08/2012 FCOEADM(8)
All times are GMT -4. The time now is 09:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy