Sponsored Content
Operating Systems Linux Red Hat Volume group not activated at boot after SAN migration Post 302952162 by vbe on Friday 14th of August 2015 09:35:55 AM
Old 08-14-2015
Is it SAN or NAS we are talking about? ( I have no RH anymore... so cant check...) but since LVM is the one HP gave to community it should behave similarly I believe, and I understand ISCSI uses standard network interface but SAN uses HBAs which are not the same and so does not need network ( TCP stuff ) up to work...
*
Addendum
Is there not a /etc/lvmrc file there? if so what does it say?

Last edited by vbe; 08-14-2015 at 10:47 AM.. Reason: typos ( Its Friday sorry if I'm unclear...) now Adeendum
 

10 More Discussions You Might Find Interesting

1. HP-UX

SAN migration

Hi, I'm going to be involved in a migration of SAN islands to one big SAN. I've not worked with SANs before and I'm not sure how to approach this. I suspect the disk devices on the HP servers are going to change, when the EVA's and servers are plugged into this new Cisco 9509 switch. Any... (0 Replies)
Discussion started by: Hils
0 Replies

2. UNIX for Advanced & Expert Users

LVM - Extending Logical Volume within Volume Group

Hello, I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB. If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information Regards Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies

3. AIX

Moving a Logical Volume from one Volume Group to Another

Does anyone have any simple methods for moving a current logical volume from one volume group to another? I do not wish to move the data from one physical volume to another. Basically, I want to "relink" the logical volume to exist in a different volume group. Any ideas? (2 Replies)
Discussion started by: krisw
2 Replies

4. AIX

Logical volume name conflict in two volume group

Hello, I am a french computer technician, and i speak English just a little. On Aix 5.3, I encounter a name conflict logical volume on two volume group. The first volume lvnode01 is OK in rootvg and mounted. It is also consistent in the ODM root # lsvg -l rootvg |grep lvnode01 ... (10 Replies)
Discussion started by: dantares
10 Replies

5. AIX

Adding a Volume Group to an HACMP Resource Group?

Hi, I have a 2 node Cluster. Which is working in active/passive mode (i.e Node#1 is running and when it goes down the Node#2 takes over) Now there's this requirement that we need a mount point say /test that should be available in active node #1 and when node #1 goes down and node#2 takes... (6 Replies)
Discussion started by: aixromeo
6 Replies

6. UNIX for Dummies Questions & Answers

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

Hi, I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies 1)Physical Volume 2)Volume Group 3)Logical Volume 4)Physical Partition Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies

7. UNIX for Dummies Questions & Answers

How to create a volume group, logical volume group and file system?

hi, I want to create a volume group of 200 GB and then create different file systems on that. please help me out. Its becomes confusing when the PP calculating PP. I don't understand this concept. (2 Replies)
Discussion started by: kamaldev
2 Replies

8. AIX

SAN Migration

Hi all, We are migrating our SAN storage from HSV360 to 3PAR. The system runs aix 6.1 version with HACMP. Please let me know what are requirements from OS side and how are the data copied to the new disks. (10 Replies)
Discussion started by: ElizabethPJ
10 Replies

9. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies

10. Red Hat

No space in volume group. How to create a file system using existing logical volume

Hello Guys, I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var. I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
SET_NET_DEFAULT(8)					      System Manager's Manual						SET_NET_DEFAULT(8)

NAME
s_n_d, set_net_default - select the default TCP/IP network SYNOPSIS
set_net_default: not found DESCRIPTION
This manual page is here because so many others refer to it. The set_net_default command does not exist under standard Minix, because the TCP/IP server only supports one network. The server under Minix-vmd supports four different networks, that can each be chosen as the default network. The TCP/IP library and commands do have a notion about a "default network" however, because the code is shared between the Minix versions. So if you want to venture into network programming then you should know about the devices and environment variables mentioned below to make your program compatible. (Especially since there is a plan to upgrade the TCP/IP server for standard Minix.) Options and environment to change the default Many TCP/IP programs implement the following options and environment variables to change the default devices set by set_net_default. The options are only implemented for low level programs where it makes sense to name a network device. The environment variables are used in all code. You can run a process and all its children connected to a different network by setting four environment variables. ETH_DEVICE=device -E device Device to use as raw ethernet device instead of the default /dev/eth. PSIP_DEVICE=device -P device Pseudo IP device to use instead of /dev/psip. IP_DEVICE=device -I device IP device to use instead of /dev/ip. TCP_DEVICE=device -T device TCP device to use. UDP_DEVICE=device -U device UDP device to use. FILES
/dev/eth[01] First and second raw ethernet. /dev/psip[01] First and second Pseudo IP network. /dev/ip[0123] IP devices for two ethernets and two Pseudo IP networks. /dev/tcp[0123] TCP devices for same four networks. /dev/udp[0123] UDP devices. /dev/eth, /dev/psip, /dev/ip, /dev/tcp, /dev/udp Devices for the default network, links to the devices above. Eth is only present if ethernet is the default, psip only for pseudo IP. SEE ALSO
ip(4), boot(8). AUTHOR
Kees J. Bot (kjb@cs.vu.nl) SET_NET_DEFAULT(8)
All times are GMT -4. The time now is 03:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy