11-16-2006
Flashcopy Scripts
Hello again,
Further to my original post; I'm looking at our existing Flashcopy scripts and the related changes prior to adding our new disks. Can anybody ratify the following scripted processes (in principal) ?
Recreate Flashcopies :
(Shutdown database - quiesce i/o)
1. SMcli -n "FAStT700" -c 'recreateFlashcopy logicalDrive ["FC VOL 1-1"];
2. SMcli -n "FAStT700" -c 'create mapping logicalDrive="FC VOL 1-1" logicalUnitNumber=xx host="AIX HOST";
3.hot_add (actually cfmgr -l deviceclass)
4. chdev -l hdiskxx -a pv=clear;
5. recreatevg -y fc_vgname hdiskxx hdiskxx hdiskxx etc
6. mount /fc_filesystem
Disable Flashcopies :
1. umount /fc_filesystem
2. varyoffvg fc_vgname
3. export fc_vgname
4. rmdev -l hdiskxx (omitting -d which we run currently)
5. Smcli -n "FAStT700" -c 'delete mapping logicalDrive="FC VOL 1-1" host ="AIX HOST";
6. SMcli -n "FAStT700" -c 'disableFlashCopy logicalDrive ["FC VOL 1-1"];
Do I need to do 'chdev -l hdiskxx -a pv=yes' after the clear (step 4) in the recreate to switch the pv from defined to available again; or will the 'hot_add' do that anyway?
Also we got an error with a dirty jfs2 superblock the other night when we mounted the FC volumes. I was wondering about (a) adding a 'sync;sync;sync' call before creating the FCs to flush the buffers and (b) adding a full fsck of the FC volumes before they are mounted; I'm not sure what the policy is on this ??
Thanks in advance.
10 More Discussions You Might Find Interesting
1. AIX
I have a P570 that for some reason is not allowing the P1-T6 NIC to be recognized. I have confirmed from the HMC that it is set for the LPAR, but when I do a cfgmgr, it won't recognize it. It though is recognizing the slot cards just fine which are P1-C3 for one shelf and P1-C3 of another shelf.... (1 Reply)
Discussion started by: LegendMan
1 Replies
2. AIX
Hi All,
I remember my old senior mentor in AIX that cfgmgr should not be terminated on your console. Because if it's terminated in the middle, the odm might get corrupted.
Is that true for AIX 5.x?
Regards,
itik (1 Reply)
Discussion started by: itik
1 Replies
3. AIX
Hi all,
I have a System i server with a couple of AIX LPARs.
One of the LPARs owns a dual-channel scsi adapter to which I connect a tape library (IBM TS3100) and a DVD Drive.
I had some problems to get the Tape Library detected but finally I got it:
rmt0 Available 03-08-01-4,0 IBM 3580... (1 Reply)
Discussion started by: wendelalexis
1 Replies
4. AIX
OS: AIX 6.1
The host has a dual port NIC installed and when I went to run `cfgmgr -v` to configure it I got an error showing device packages are missing from the install:
`cfgmgr -v` on 10.15.xx.xxx
cfgmgr: 0514-621 WARNING: The following device packages are required for device support but... (3 Replies)
Discussion started by: b1f30
3 Replies
5. Programming
i wrote a tiny version of tail command using a large buffer statically allocated but, in a second time, i found another version in which i use a bidimensional array dynamically allocated.
here is the first version
/*my tiny tail, it prints the last 5 line of a file
*/
#include<stdio.h>... (4 Replies)
Discussion started by: lucasclaus
4 Replies
6. AIX
Hi
When I run cfgmgr -v in my aix box I get the below error :
cfgmgr: 0514-621 WARNING: The following device packages are required for
device support but are not currently installed.
devices.loopback
My oslevel is 6100-06-02-1044
Please assist.
Please use and tags when... (3 Replies)
Discussion started by: samsungsamsung
3 Replies
7. AIX
Dear all
i have a sun SL500 tape library attached to my AIX box while issue the command cfgmgr i have the below issue
test>cfgmgr
cfgmgr: 0514-621 WARNING: The following device packages are required for
device support but are not currently installed.
devices.fcp.changer
please... (3 Replies)
Discussion started by: thecobra151
3 Replies
8. Solaris
Hi guys!
Could you tell me what's this figure about? (See the attached figure below.)
This is a representation of block allocation filesystem and extent allocation filesystem in Solaris.
Does this mean that in a block-based allocation, data are placed in individual blocks while in... (0 Replies)
Discussion started by: arah
0 Replies
9. AIX
Hi,
From the man page, cfgmgr configures devices and optionally installs device software by running the programs specified in the Configuration Rules object class and it is not dependent on platform .
Are there any fundamental differences impacting the speed of cfgmgr on a stand-alone and... (5 Replies)
Discussion started by: Sachin1987
5 Replies
10. Post Here to Contact Site Administrators and Moderators
Hi,
My AIX server able to detect the LUN's which is mapped from IBM v7k storage, And i allocated one more LUN from HP storage but it's appear two hdisk instead of one and it's showing incorrect LUN ID.
SDDPCM driver already installed on this server.
During cfgmgr, Im getting this message :... (1 Reply)
Discussion started by: xinuadmin
1 Replies
LEARN ABOUT OSF1
cfg_attr_t
cfg_attr_t(9s) cfg_attr_t(9s)
NAME
cfg_attr_t - General: Contains information for managing the loading and unloading of kernel modules
SYNOPSIS
typedef struct cfg_attr {
char name[CFG_ATTR_NAME_SZ];
uchar type;
uchar operation;
uint status;
long index;
union {
struct {
caddr_t val;
ulong min_size;
ulong max_size;
void (*disposal)();
ulong val_size;
} bin;
struct {
caddr_t val;
ulong min_len;
ulong max_len;
void (*disposal)();
} str;
struct {
ulong val;
ulong min_val;
ulong max_val;
} num;
} attr; } cfg_attr_t;
MEMBERS
Specifies the ASCII name of the attribute. The name must be between 2 and CFG_ATTR_NAME_SZ characters in length, including the terminating
null character. Do not begin the ASCII name of the attribute with the Method_ or Device_ characters. The cfgmgr framework reserves certain
names that begin with the Method_ and Device_ characters. Specifies the data type associated with the name attribute. See the DESCRIPTION
section for the constants you can pass to the type member. Specifies the operations that the cfgmgr framework can perform on the
attribute. See the DESCRIPTION section for the constants you can pass to the operation member. Stores the return code from operations
(configure, unconfigure, query) that the cfgmgr framework performs. See the DESCRIPTION section for the operation codes that the cfgmgr
framework can return to the status member. Stores a value that scopes the target for indexed attributes. Specifies a union of the possi-
ble attribute types used for storing values, kernel locations, validation criteria, and disposal routines. The cfgmgr framework uses the
appropriate union element according to the attribute type. For example, attributes of type CFG_ATTR_ULONGTYPE use the union element num.
DESCRIPTION
The cfg_attr_t data structure contains information for managing the configuring and unconfiguring of kernel modules. The cfgmgr framework
passes a pointer to this data structure to the kernel module's configure routine. The kernel module can parse this structure pointer to
check the validity of the values associated with the module's associated sysconfigtab file fragment and the /etc/sysconfigtab database.
You must set the type member to one of the following constants: Data type is a null-terminated array of characters. Data type is a 32-bit
signed integer. Data type is a 32-bit unsigned integer. Data type is a 64-bit signed integer. Data type is a 64-bit unsigned integer.
Data type is an array of bytes. Data type is an 8-bit unsigned character. Data type is a 16-bit unsigned short integer.
You can set the operation member to one of the following constants: The cfgmgr framework configures the attribute. This means the cfgmgr
framework obtains a data value for the attribute from the /etc/sysconfigtab database. The configure operation occurs when the cfgmgr frame-
work calls the configure routine at its CFG_OP_CONFIGURE entry point. (That is, the optype argument of the configure routine evaluates to
the CFG_OP_CONFIGURE constant.) The cfgmgr framework queries (reads) the attribute. This means the kernel module cooperates with the cfg-
mgr framework to provide the value associated with the attribute as a result of user-initiated query requests. These requests are typically
the result of the sysconfig -q command. The query operation occurs when the cfgmgr framework calls the configure routine at its
CFG_OP_QUERY entry point. (That is, the optype argument of the configure routine evaluates to the CFG_OP_QUERY constant.) The cfgmgr
framework reconfigures the attribute. This means the cfgmgr framework reconfigures the data value for the attribute. This functionality
allows a user to modify the attribute. A reconfigure request is typically the result of the sysconfig -r command. The reconfigure opera-
tion occurs when the cfgmgr framework calls the configure routine at its CFG_OP_RECONFIGURE entry point. (That is, the optype argument of
the configure routine evaluates to the CFG_OP_RECONFIGURE constant.)
The cfgmgr framework can return one of the following operation codes: Successful operation. The attribute you specified in the name member
does not exist. The attribute you specified in the name member does not support the operation. The subsystem failed. The value or size
of the attribute you specified in the name member is too small. The value or size of the attribute you specified in the name member is too
large. The data type that you specified for the attribute you specified in the name member is invalid or is a mismatch. The index associ-
ated with the attribute that you specified in the name member is invalid. The cfgmgr framework could not allocate memory for the specified
attribute. The attribute that you specified in the name member cannot be converted to a number.
FILES
SEE ALSO
Data Structures: cfg_subsys_attr_t(9s)
cfg_attr_t(9s)