Sponsored Content
Full Discussion: LPAR and CFGMGR
Operating Systems AIX LPAR and CFGMGR Post 302083997 by LegendMan on Tuesday 8th of August 2006 06:07:17 PM
Old 08-08-2006
LPAR and CFGMGR

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.

Any help is greatly appreciated.
 

10 More Discussions You Might Find Interesting

1. AIX

cfgmgr and hdisk number allocation

Hi - can anybody tell me what the default behaviour is for cfgmgr when it allocates hdisk numbers to newly discovered disks in the ODM ? I want to add a disk from our FAStT700 SAN disk array and import it on our p-series (AIX 5.2). Problem is we import and export Flashcopy devices fror scripted... (5 Replies)
Discussion started by: fosteria
5 Replies

2. AIX

cfgmgr

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

cfgmgr: Filesets missing

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

Dual port NIC, cfgmgr

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. AIX

cfgmgr in my aix box

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

6. AIX

LPAR freezes after switching of storage (lpar is mirrored)

Hi all, I have the following configuration 2 ds3524 storage disk systems located over 2 locations 2 P720 server located over 2 locations DS3524 are connected to san switch. Each vio server has 1 fc adapter attached to a san switch. per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
Discussion started by: markiemark
2 Replies

7. AIX

cfgmgr: 0514-621 WARNING

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. AIX

Time taking for cfgmgr on dual VIO

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

9. AIX

How to differentiate between a standalone LPAR and a VIOC (which again is a lpar)?

There can be configurations in IBM Server wherein a standalone partition is created on some supported IBM Server Or A VIOS - VIOC LPARs created. Now in both cases they are lpars. But if I want to differentiate b/w a standalone LPAR vs an VIOC LPAR how can I do..? On a... (2 Replies)
Discussion started by: Manish00712
2 Replies

10. Post Here to Contact Site Administrators and Moderators

Cfgmgr Error

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
vblade-persist(8)					      System Manager's Manual						 vblade-persist(8)

NAME
vblade-persist - manage persistent exported ATA-over-Ethernet devices SYNOPSIS
vblade-persist ls [--no-header] vblade-persist setup shelf slot netif blockdev vblade-persist destroy shelf slot vblade-persist { start | stop | restart | auto | noauto } shelf slot vblade-persist { start | stop | restart | auto | noauto } all vblade-persist mac shelf slot { ls | clear } vblade-persist mac shelf slot { add | del } [ addr ... ] DESCRIPTION
The vblade-persist script is used to show and manipulate persistently-exported ATA-over-Ethernet devices. It has a simple subcommand syn- tax. Persistent AoE device exports can be configured to come up at boot time. For each running persistent AoE export, a symlink pointing to the backing device is created in /dev/etherd/, mirroring the devices seen by clients of the AoE device. MANAGEMENT SUBCOMMANDS
ls [--noheader] vblade-persist ls shows all existing persistent AoE exports. The columns of the output are, in order: AoE Shelf, AoE Slot, Network Inter- face, Backing Device, AutoStart, Status. AutoStart is either "auto" (start automatically at boot), or "noauto" (don't start automatically at boot). Status should be either "run" (running) or "down" (not running). The optional --no-header argument suppresses the header line. This may be convenient for machine-parseable output. setup shelf slot netif source vblade-persist setup creates a new persistent exported AoE block device. You must supply all four additional arguments. These are the same arguments supplied to vblade(8). You should specify source using an absolute path. New devices set up this way are noauto (not brought up automatically at boot) and down (not exported immediately). destroy shelf slot vblade-persist destroy halts any running exported AoE block device managed by vblade-persist and removes the service directory used to man- age it. start shelf slot stop shelf slot restart shelf slot These commands control a specific exported AoE device. Instead of specifying shelf and slot , you can also provide the special keyword all which will act on every exported AoE device. auto shelf slot noauto shelf slot These commands control whether a specific exported AoE device should be started automatically ( auto ) or not ( noauto ) at system boot time. Instead of specifying shelf and slot , you can also provide the special keyword all which will act on every exported AoE device. MAC-ADDRESS FILTERING You can use vblade-persist to restrict access to specific exports by MAC address, using the mac subcommand. mac shelf slot ls List all MAC addresses allowed to access the specified device, one per line. If the list is empty, no MAC address limits are imposed on this device. mac shelf slot clear Remove all MAC address filtering from the specified device. No MAC address limits will be imposed on this device. mac shelf slot add [ addr ... ] Add a MAC address (or more than one) to the list of allowed addresses for the specified device. Note that if there were no MAC addresses listed previously, this will enable MAC address filtering for the device. mac shelf slot del [ addr ... ] Remove a MAC address (or more than one) from the list of allowed addresses for the specific device. Note that if you remove all the MAC addresses from the list, this will disable MAC address filtering for the device. EXAMPLES
Set up /dev/sda2 as shelf 2, slot 3 on the network served by interface eth0. Make sure it starts automatically at boot, and start it up now: vblade-persist setup 2 3 eth0 /dev/sda2 vblade-persist auto 2 3 vblade-persist start 2 3 Limit that same export to MAC addresses aa:bb:cc:dd:ee:ff and 11:22:33:44:55:66: vblade-persist mac 2 3 add aa:bb:cc:dd:ee:ff 11:22:33:44:55:66 Remove all MAC address restrictions on the same export: vblade-persist mac 2 3 clear BUGS
You can't currently use the vblade-persist framework to export a device (or two) with the same shelf/slot identifier on two different net- work interfaces. DEPENDENCIES
The exports themselves are handled by vblade(8). Supervision of the exports and convenient management is enabled by runsv(8), from the runit suite. SEE ALSO
vblade(8), runsv(8) AUTHOR
Daniel Kahn Gillmor <dkg@fifthhorseman.net> vblade-persist 2007-11-11 vblade-persist(8)
All times are GMT -4. The time now is 06:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy