Sponsored Content
Full Discussion: regd sunfire 480 r
Top Forums UNIX for Dummies Questions & Answers regd sunfire 480 r Post 38640 by thehoghunter on Tuesday 22nd of July 2003 09:23:21 AM
Old 07-22-2003
You have memory that has gone bad. Call SUN for a service call (800) 872-4786 .... or

if you have spare memory for this server, replace the memory in Bank 0 Dimm 2, J8001 side 1 on cpu board 3 for starters. That may solve your problem - if not, then replace all the memory in Bank 0 on cpu board 3.

Or, you could remove the memory out of that bank if you can run without it.
 

10 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

regd explorer

hiii i want to know how to install explorer in sparc e-250 OS solaris 8 iam able to install the software iam able to install the explorer,i use to run #./explorer -q -e other than this what all i should run to get all details.but iam just getting some thing which not related to o/s or h/w... (3 Replies)
Discussion started by: solaris8in
3 Replies

2. UNIX for Advanced & Expert Users

regd:-sunblade1000

hii alll i have sunblade 1000 i get a error all of sudden cpu panic error this comes twice a day is this because of patches not installed in the system or its regarding memory or cpu can any one helpme out thanks in advance solaris (2 Replies)
Discussion started by: solaris8in
2 Replies

3. Solaris

Regd Backup issue

hii alll Thanks for all the previous support. I need some clarification, i have client who is having 5 sun workstation ( ultra5 & ultra 10 and 1 ultra60) they orderd for backup device DLT drive , iam going to connect this dlt drive sparc ultra 60 i can configure locally,but my client... (1 Reply)
Discussion started by: solaris8in
1 Replies

4. Solaris

regd.sunblade 100

hii alll i have a problem with my sunblade100. when i switch on, no display comes but if i ping from a remote machine its pinging,but iam not able to telent to that sun server,what can be the problem,how can i sort ot this issue 2 thing in usb iam not able to use STOP N (to clear the... (3 Replies)
Discussion started by: solaris8in
3 Replies

5. Solaris

regd tanberg sdlt and sunfire v 880

Hii alll Thanks for the support, iam facing a problem regarding tanberg sdlt . iam trying to connect tanberg sdlt 160 to sun fire 880 r .As SUN FIRE DOSENT HAVE SCSI CONTROLLER IAM CONNECTING A ULTRA 2 SCSI CONTROLLER IN PCI SLOT AND FROM THERE IAM CONNECTING THE TANBERG SDLT 160. MY FIRST... (1 Reply)
Discussion started by: solaris8in
1 Replies

6. AIX

regd raid 0 configuration

Hey Alll Thanks for the help u give me yesterday,i need a help again from u all guys i have RS 6000 server with AIX 4.3.3 OS and with external storage (multipack) with 12 Hard disk drive which will be connected to RS 6000 scsi controller ,i dont have any raid card. now i have to... (0 Replies)
Discussion started by: solaris8in
0 Replies

7. Linux

installation proccedure regd Teacup helpdesk software

Hey All I have been asked to install Teacup - Helpdesk report management system .Iam trying to insall this software on Redhat 9, iam not that good in linux but i have been asked to instal this software so need ur help regarding this . i have installed redhat 9 . This is site where u guys can... (0 Replies)
Discussion started by: solaris8in
0 Replies

8. UNIX for Advanced & Expert Users

Regd: rcp

Hi, The B machine is using rcp method to copy a file to A machine. But it is not getting copied. Its giving the error as: remshd: Login incorrect. On A machine rhosts file has details about the B machine. Could anyone tell what could be done to make this work? Any help is appreciated.... (1 Reply)
Discussion started by: nehak
1 Replies

9. AIX

Query regd TL upgrade

I am new to AIX administration and am trying to upgrade my current TL from 6100-05 to 6100-07 , I had a look at the fix central and I have downloaded one which says TL 6100-07-00-1140 and other which says service pack 6100-07-05-1228. I have two test machines and I have applied directly... (0 Replies)
Discussion started by: nivaspIND
0 Replies

10. Solaris

Sun Fire 480 - devfsadm -C not working after replacing one of the boot disks

Our SunFire 480 - one of the boot disks failed. It is mirrored with VxVm. I followed the exact steps that is detailed in the veritas and sun guides (I can not post the URL since I don't have 5 posts yet.) After removing the failed disk, I ran devfsadm -C -c disk and it still shows the device... (7 Replies)
Discussion started by: jtamminen
7 Replies
cfgadm_ac(1M)						  System Administration Commands					     cfgadm_ac(1M)

NAME
cfgadm_ac - EXX00 memory system administration SYNOPSIS
/usr/sbin/cfgadm [-c configure] [-f] [-o disable-at-boot | enable-at-boot ] ac#:bank# ... /usr/sbin/cfgadm [-c unconfigure] [-o disable-at-bootp | enable-at-boot ] ac#:bank# ... /usr/sbin/cfgadm [-v] [-o quick | normal | extended, [max_errors=#] ] -t ac#:bank#... /usr/sbin/cfgadm -x relocate-test ac#:bank# ... /usr/sbin/cfgadm [-l] -o disable-at-boot | enable-at-boot ac#:bank# ... DESCRIPTION
The ac hardware specific library /usr/platform/sun4u/lib/cfgadm/cfgadm_ac.so.1 provides the functionality for configuring and unconfiguring memory banks on E6X00, E5X00, E4X00 and E3X00 systems as part of the Dynamic Reconfiguration of CPU/Memory boards using cfgadm_sysctrl(1M). Memory banks appear as attachment points in the device tree. For each CPU/Memory board, two attachment points are published, one for each bank on the board: bank0 and bank1. If the bank is unpopulated, the receptacle state is empty. If the bank is populated, the receptacle state is connected. The receptacle state of a memory bank can never be disconnected. The occupant state of a connected memory bank can be configured or unconfigured. If the occupant state is configured, the memory is in use by Solaris, if unconfigured it is not. OPTIONS
Refer to cfgadm(1M) for complete descriptions of the command options. The following options are supported: -c configure | unconfigure Change the occupant state. The configure argument ensures that the memory is initialized and adds the memory to the Solaris memory pool. The unconfigure argument removes the memory from use by Solaris. When a CPU/Memory board is to be removed from a system, both banks of memory must be unconfigured. cfgadm refuses the configure operation if the memory on the board is marked disabled-at-boot (see info field), unless either the -f (force) option or the enable at boot flag, (-o enable-at-boot), is given. The configure operation takes a short time proportional to the size of memory that must be initialized. cfgadm refuses the unconfigure operation if there is not enough uncommitted memory in the system (VM viability error) or if the bank to be unconfigured has memory that can't be removed (non-relocatable pages error). The presence of non-relocatable pages is indicated by the word permanent in the info listing field. Removing memory from use by Solaris may take a significant time due to factors such as system load and how much paging to secondary storage is required. The unconfigure operation can be cancelled at any time and the memory returned to the fully configured state by interrupting the command invocation with a signal. The unconfigure operation self-cancels if no memory can be removed within a timeout period. The default timeout period of 60 seconds can be changed using the -o timeout=# option, with a value of 0 disabling the timeout. -f Force option. Use this option to override the block on configuring a memory bank marked as disabled at boot in the non-volatile dis- abled-memory-list variable. See Platform Notes:Sun Enterprise 6x00/5x00/4x00/3x00 Systems -l List option. This option is supported as described in cfgadm(1M). The type field is always memory. The info field has the following information for empty banks: slot# empty The slot# indicates the system slot into which the CPU/Memory board is inserted. For example, if this were slot11 the attachment point for use with cfgadm to manipulate the associated board would be sysctrl0:slot11. The info field has the following information for connected banks: slot# sizeMb|sizeGb [(sizeMb|sizeGb used)] base 0x### [interleaved #-way] [disabled at boot] [permanent] The size of the bank is given in Mb or Gb as appropriate. If the memory is less than completely used, the used size is reported. The physical base address is given in hexadecimal. If the memory bank is interleaved with some other bank, the interleave factor is reported. If the memory on the board is disabled at boot using the non-volatile disabled-memory-list variable, this is reported. If the bank has memory that cannot be removed this is reported as permanent. -o disable-at-boot | enable-at-boot These options allow the state of the non-volatile disabled-memory-list variable to be modified. These options can be used in conjunc- tion with the issuing of a -c option or with the explicit or implied listing command, -l, if no command is required. Use of -o enable- at-boot with the configure command to override the block on configuring memory on a board in the disabled memory list. -o extended | normal | quick Use with the -t option to specify test level. The normal test level ensures that each memory cell stores both a 0 and a 1, and checks that all cells are separately addressable. The quick test level only does the 0s and 1s test, and typically misses address line problems. The extended test uses patterns to test for adjacent cell interference problems. The default test level is normal. See -t option. -o max_errors=# Use with the -t option to specify the maximum number of allowed errors. If not specified, a default of 32 is assumed. -o timeout=# Use with the unconfigure command to set the self-cancelling timeout. The default value is 60 and the unit is seconds. A value of 0 means no timeout. -t Test an unconfigured bank of memory. Specify the test level using the -o quick | normal | extended option. cfgadm exits with a 0 (success) if the test was able to run on the memory bank. The result of the test is available in the condition for the attachment point. -v Verbose option. Use this option in combination with the -t option to display detailed progress and results of tests. -x relocate-test For all pages of memory in use on the specified memory bank, a relocation operation as used in the unconfigure command is attempted. The success of this operation does not guarantee that the bank can be unconfigured. Failure indicates that it probably cannot be uncon- figured. This option is for test purposes only. OPERANDS
The following operand is supported: ac#:bank# The attachment points for memory banks are published by instances of the address controller (ac) driver (ac#). One instance of the ac driver is created for each system board, but only those instances associated with CPU/Memory boards publish the two bank attachment points, bank0 and bank1. This form conforms to the logical ap_id specification given in cfgadm(1M). The corresponding physical ap_ids are listed in the FILES section. The ac driver instance numbering has no relation to the slot number for the corresponding board. The full phys- ical attachment point identifier has the slot number incorporated into it as twice the slot number in hexadecimal directly following the fhc@ part. FILES
/devices/fhc@*,f8800000/ac@0,1000000:bank? attachment points /usr/platform/sun4u/lib/cfgadm/cfgadm_ac.so.1 hardware specific library file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWkvm.u | +-----------------------------+-----------------------------+ SEE ALSO
cfgadm(1M), cfgadm_sysctrl(1M), config_admin(3CFGADM), attributes(5) Sun Enterprise 6x00, 5x00, 4x00 and 3x00 Systems Dynamic Reconfiguration User's Guide Platform Notes:Sun Enterprise 6x00/5x00/4x00/3x00 Systems NOTES
Refer to the Sun Enterprise 6x00, 5x00, 4x00 and 3x00 Systems Dynamic Reconfiguration User's Guide for additional details regarding dynamic reconfiguration of EXX00 system CPU/Memory boards. SunOS 5.10 29 Sep 1999 cfgadm_ac(1M)
All times are GMT -4. The time now is 06:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy