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
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
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. 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
6. AIX
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
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
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
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
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 NETBSD
eshconfig
ESHCONFIG(8) BSD System Manager's Manual ESHCONFIG(8)
NAME
eshconfig -- configure Essential Communications' HIPPI network interface
SYNOPSIS
eshconfig [-estx] [-b bytes] [-c bytes] [-d filename] [-i usecs] [-m bytes] [-r bytes] [-u filename] [-w bytes] [interface]
DESCRIPTION
eshconfig is used to configure device-specific parameters and download new firmware to the Essential Communications RoadRunner-based HIPPI
network interface. The interface is very sensitive to the DMA performance characteristics of the host, and so requires careful tuning to
achieve reasonable performance. In addition, firmware is likely to change frequently, which necessitates a reasonably easy way to update
that firmware.
Available operands for eshconfig:
-b bytes
Adjust the burst size for read (by NIC of host memory) DMA.
-c bytes
Adjust the burst size for write (by NIC of host memory) DMA.
-d filename
Filename for file to download into NIC firmware. This must be a file in the standard Essential format, with :04 preceding every
line, and a tag line at the end indicating the characteristics of the firmware file.
-e Write data to EEPROM. Normally, setting tuning parameters will only persist until the system is rebooted. Setting this parameter
ensures that the changes will be written to EEPROM.
-i usecs
Interrupt delay in microseconds.
-m bytes
Minimum number of bytes to DMA in one direction (read or write) before allowing a DMA in the other direction. Tuning this prevents
one direction from dominating the flow of bytes, and artificially throttling the NIC.
-r bytes
Bytes before DMA starts for read (from host to NIC). This controls how soon the DMA is triggered; until this many bytes are
requested, the DMA will not begin.
-s Show statistics for the HIPPI NIC. Repeat the option to suppress non-zero statistics.
-t Show current tuning parameters on the host.
-u filename
Name of file to which the NIC firmware should be uploaded. Not currently supported.
-w bytes
Number of bytes required before write (from NIC to host) DMA is started. Until this many bytes are ready to be written, the DMA will
not start.
-x Reset the NIC. This is necessary for the HIPPI-FP support, as ifconfig(8) will no longer physically reset the NIC when the inter-
faces goes up and down.
Only the super-user may modify the configuration of a network interface.
DIAGNOSTICS
Messages indicating the specified interface does not exist or the user is not privileged and tried to alter an interface's configuration.
SEE ALSO
esh(4), ifconfig(8)
HISTORY
The eshconfig command first appeared in NetBSD 1.4.
BSD
June 17, 2005 BSD