cfgadm_ac(1m)

1cfgadm_ac(1M)           System Administration Commands           cfgadm_ac(1M)
2
3
4

NAME

6       cfgadm_ac - EXX00 memory system administration
7

SYNOPSIS

9       /usr/sbin/cfgadm [-c configure] [-f]
10            [-o disable-at-boot | enable-at-boot ] ac#:bank# ...
11
12
13       /usr/sbin/cfgadm [-c unconfigure]
14            [-o disable-at-bootp | enable-at-boot ] ac#:bank# ...
15
16
17       /usr/sbin/cfgadm [-v]
18            [-o quick | normal | extended, [max_errors=#] ] -t ac#:bank#...
19
20
21       /usr/sbin/cfgadm -x relocate-test ac#:bank# ...
22
23
24       /usr/sbin/cfgadm [-l] -o disable-at-boot | enable-at-boot ac#:bank# ...
25
26

DESCRIPTION

28       The       ac       hardware       specific      library      /usr/plat‐
29       form/sun4u/lib/cfgadm/cfgadm_ac.so.1  provides  the  functionality  for
30       configuring  and  unconfiguring memory banks on E6X00, E5X00, E4X00 and
31       E3X00 systems as part of  the  Dynamic  Reconfiguration  of  CPU/Memory
32       boards using cfgadm_sysctrl(1M).
33
34
35       Memory  banks  appear as attachment points in the device tree. For each
36       CPU/Memory board, two attachment points are  published,  one  for  each
37       bank  on  the  board:  bank0 and bank1. If the bank is unpopulated, the
38       receptacle state is empty. If the bank  is  populated,  the  receptacle
39       state  is connected. The receptacle state of a memory bank can never be
40       disconnected. The occupant state of a connected memory bank can be con‐
41       figured  or unconfigured. If the occupant state is configured, the mem‐
42       ory is in use by Solaris, if unconfigured it is not.
43

OPTIONS

45       Refer to cfgadm(1M) for complete descriptions of the command options.
46
47
48       The following options are supported:
49
50       -c configure | unconfigure
51
52           Change the occupant state. The configure argument ensures that  the
53           memory  is  initialized  and  adds the memory to the Solaris memory
54           pool. The unconfigure argument  removes  the  memory  from  use  by
55           Solaris.  When  a  CPU/Memory board is to be removed from a system,
56           both banks of memory must be unconfigured.
57
58           cfgadm refuses the configure operation if the memory on  the  board
59           is  marked  disabled-at-boot (see info field), unless either the -f
60           (force) option or the enable at boot flag, (-o enable-at-boot),  is
61           given.  The  configure operation takes a short time proportional to
62           the size of memory that must be initialized.
63
64           cfgadm refuses the unconfigure operation  if there  is  not  enough
65           uncommitted  memory  in  the  system (VM viability error) or if the
66           bank to be unconfigured has memory that can't be removed (non-relo‐
67           catable  pages  error).  The  presence  of non-relocatable pages is
68           indicated by the word permanent in the info listing field. Removing
69           memory  from use by Solaris may take a significant time due to fac‐
70           tors such as system load and how much paging to  secondary  storage
71           is required. The unconfigure operation can be cancelled at any time
72           and the memory returned to the fully configured state by interrupt‐
73           ing the command invocation with a signal. The unconfigure operation
74           self-cancels if no memory can be removed within a  timeout  period.
75           The  default  timeout period of 60 seconds can be changed using the
76           -o timeout=# option, with a value of 0 disabling the timeout.
77
78
79       -f
80
81           Force option. Use this option to override the block on  configuring
82           a  memory  bank marked as disabled at boot in the non-volatile dis‐
83           abled-memory-list  variable.  See  Platform  Notes:Sun   Enterprise
84           6x00/5x00/4x00/3x00 Systems
85
86
87       -l
88
89           List option. This option is supported as described in cfgadm(1M).
90
91           The type field is always memory.
92
93           The info field has the following information for empty banks:
94
95             slot# empty
96
97
98           The slot# indicates the system slot into which the CPU/Memory board
99           is inserted. For example, if this were slot11 the attachment  point
100           for  use  with  cfgadm  to manipulate the associated board would be
101           sysctrl0:slot11.   The info field has the following information for
102           connected banks:
103
104             slot# sizeMb|sizeGb [(sizeMb|sizeGb used)] base 0x###
105                   [interleaved #-way] [disabled at boot] [permanent]
106
107
108           The  size  of  the bank is given in Mb or Gb as appropriate. If the
109           memory is less than completely used, the used size is reported. The
110           physical  base  address is given in hexadecimal. If the memory bank
111           is interleaved with some  other  bank,  the  interleave  factor  is
112           reported.  If the memory on the board is disabled at boot using the
113           non-volatile disabled-memory-list variable, this  is  reported.  If
114           the bank has memory that cannot be removed this is reported as per‐
115           manent.
116
117
118       -o disable-at-boot | enable-at-boot
119
120           These options allow the state of the non-volatile  disabled-memory-
121           list variable to be modified. These options can be used in conjunc‐
122           tion with the issuing of a  -c  option  or  with  the  explicit  or
123           implied  listing  command, -l, if no command is required. Use of -o
124           enable-at-boot with the configure command to override the block  on
125           configuring memory on a board in the disabled memory list.
126
127
128       -o extended | normal | quick
129
130           Use with the -t option to specify test level.
131
132           The normal test level ensures that each memory cell stores both a 0
133           and a 1, and checks that all cells are separately addressable.  The
134           quick test level only does the 0s and 1s test, and typically misses
135           address line problems. The extended test uses patterns to test  for
136           adjacent  cell  interference  problems.   The default test level is
137           normal. See -t option.
138
139
140       -o max_errors=#
141
142           Use with the -t option to specify the  maximum  number  of  allowed
143           errors. If not specified, a default of 32 is assumed.
144
145
146       -o timeout=#
147
148           Use  with  the unconfigure command to set the self-cancelling time‐
149           out. The default value is 60 and the unit is seconds. A value of  0
150           means no timeout.
151
152
153       -t
154
155           Test  an  unconfigured bank of memory. Specify the test level using
156           the -o quick | normal | extended option.
157
158           cfgadm exits with a 0 (success) if the test was able to run on  the
159           memory  bank.  The result of the test is available in the condition
160           for the attachment point.
161
162
163       -v
164
165           Verbose option. Use this option in combination with         the  -t
166           option to display detailed progress and results of tests.
167
168
169       -x relocate-test
170
171           For  all  pages  of  memory  in use on the specified memory bank, a
172           relocation  operation  as  used  in  the  unconfigure  command   is
173           attempted.  The  success  of this operation does not guarantee that
174           the bank can be unconfigured. Failure indicates  that  it  probably
175           cannot be unconfigured. This option is for test purposes only.
176
177

OPERANDS

179       The following operand is supported:
180
181       ac#:bank#    The  attachment  points  for memory banks are published by
182                    instances of the address controller (ac) driver (ac#). One
183                    instance  of  the  ac  driver  is  created for each system
184                    board, but only those instances associated with CPU/Memory
185                    boards  publish  the two bank attachment points, bank0 and
186                    bank1.
187
188                     This form conforms to  the  logical  ap_id  specification
189                    given in cfgadm(1M). The corresponding physical ap_ids are
190                    listed in the FILES section.
191
192                    The ac driver instance numbering has no  relation  to  the
193                    slot number for the   corresponding board. The full physi‐
194                    cal attachment point identifier has the slot number incor‐
195                    porated  into  it  as twice the slot number in hexadecimal
196                    directly following the fhc@ part.
197
198

FILES

200       /devices/fhc@*,f8800000/ac@0,1000000:bank?
201
202           attachment points
203
204
205       /usr/platform/sun4u/lib/cfgadm/cfgadm_ac.so.1
206
207           hardware specific library file
208
209

ATTRIBUTES

211       See attributes(5) for descriptions of the following attributes:
212
213
214
215
216       ┌─────────────────────────────┬─────────────────────────────┐
217       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
218       ├─────────────────────────────┼─────────────────────────────┤
219       │Availability                 │SUNWkvm.u                    │
220       └─────────────────────────────┴─────────────────────────────┘
221

NOTES

233       Refer  to  the Sun Enterprise 6x00, 5x00, 4x00 and 3x00 Systems Dynamic
234       Reconfiguration User's Guide for additional details  regarding  dynamic
235       reconfiguration of EXX00 system CPU/Memory boards.
236
237
238
239SunOS 5.11                        29 Sep 1999                    cfgadm_ac(1M)