11-04-2008
adding memory to sun blade server ...
Hi, this is my 1st post here, I don't know is it proper or not for the question I have, but I may try ask anyway, since it is question about sun's hw/sw issue...
I have my blade 1000 installed additional memory kits, it was originally 2G memory installed on Group0(Bank 0/2) Dimm slots, I got some 2nd hand memory kits from eBay, and installed it, after reboot(touch /reconfigure, shutdown,then install memory modules), I use "prtconf -v" but something caught my eye, the " memory-controller, instance #1" is different as usual:
.....
memory-controller, instance #0
Driver properties:
name='logical-bank-ma-regs' type=int items=8 dev=none
value=80007e00.00030000.80007e00.00030100.80007e00.00030200.80007e00.00030300
Register Specifications:
Bus Type=0x400, Address=0x400000, Size=0x48
Device Minor Nodes:
dev=(158,0)
dev_path=/memory-controller@0,400000:mc-us3
spectype=chr type=minor
dev_link=/dev/mc/mc0
SUNW,UltraSPARC-III, instance #1
Driver properties:
name='pm-class' type=string items=1 dev=none
value='CPU'
name='pm-components' type=string items=4 dev=none
value='NAME=CPU Speed' + '1=1/32 of Normal' + '2=1/2 of Normal' + '3=Normal'
Register Specifications:
Bus Type=0x400, Address=0x800000, Size=0x10000
memory-controller, instance #1
Driver properties:
name='logical-bank-ma-regs' type=int items=8 dev=none
value=00000000.00000000.00000000.00000000.00000000.00000000.00000000.00000000
Register Specifications:
Bus Type=0x400, Address=0xc00000, Size=0x48
Device Minor Nodes:
dev=(158,1)
dev_path=/memory-controller@1,400000:mc-us3
spectype=chr type=minor
dev_link=/dev/mc/mc1
I'm wondering about why "memory-controller, instance #1" got all "0" value other then "memory-controller, instance #0"? it actually got total 4G memory now, but why the new installed 2G memory kits got all "0" value information? what does the "value=" mean in the section? anything I shall watch out especially?
my sun balde 1000 was installed solaris 10 8/07, with recommanded patch installed.
thanks.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I would like to upgrade the memory in my Sun Blade 150 workstation. In reading through Sun's Blade 150 DIMM Installation Guide, it indicates that the memory must be "certified by Sun for the Sun Blade 150 system."
Does anyone know if any SDRAM, PC133 • CL=2 • Unbuffered • ECC • 133MHz • 3.3V ... (2 Replies)
Discussion started by: here2learn
2 Replies
2. Solaris
hello,
I have SunBlade 2000 with XVR-1000 graphics card. Xserver won't loaded. I've reinstalled OS 9 ( loaded Driver) nor 10 still won't do it. Anyone has this problem or have any ideas whats' wrong, greatly appreciated!!
thanks in adv. (1 Reply)
Discussion started by: anphdula
1 Replies
3. Solaris
Hi, I've been a member for a while but have never posted. I have a Sun Blade 100 desktop and I just installed Solaris 10 and it is unbearably slow. I only have 128 Meg of RAM and need to upgrade. I have searched and found many online resources that have RAM, but I was wondering if anyone has... (12 Replies)
Discussion started by: BrewDudeBob
12 Replies
4. Hardware
Can you mix DIMMs in a T6320 (sparc) blade? I have read/heard that the DIMMs in a memory bay must be identical but can you have different size DIMMs installed in the blade?
For instance, can you have 1 4GB DIMM in bay 0, 2 2GB DIMMs in bay 1, 4 1 GB DIMMs in bay 2 and 2 2GB DIMMs in bay 3 for a... (0 Replies)
Discussion started by: bluescreen
0 Replies
5. Solaris
I need to add two new hard drives of 300 GB capacity to a SunSPARC T5440 server. The server currently has two hard drives of 146 GB each.
How do I add the new drives to the existing UFS?
What are the procedures involved in setting this server with the new hard drives? I am very new to Solaris... (6 Replies)
Discussion started by: ramatnmcc
6 Replies
6. Solaris
I have recently re-installed Solaris 10 on a Sun Blade 150 followed by a patch set (10_Recommended) dated 2011.12.05.
I have just noticed /bin/sun now returns false, rather than true. See below.
$ uname -a
SunOS myblade1 5.10 Generic_147440-07 sun4u sparc SUNW,Sun-Blade-100
$ /bin/sparc &&... (1 Reply)
Discussion started by: apmcd47
1 Replies
7. Solaris
We have a 6000 chassis with three blades in it. Two of the blades have "Oracle/Sun" memory in them with no complaints. The third blade is populated with Dataram dimms. That 3rd blade continues to flag a slot bad. Oracle has said they would not support the blade with Dataram memory it it. I didn't... (1 Reply)
Discussion started by: brownwrap
1 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I have server SUN BLADE T6340 and i tried install debian sparc on this machine.
Will it work ?
In the specification is written only Solaris 10. (4 Replies)
Discussion started by: PtaQ
4 Replies
9. Solaris
Hi all,
My home server was Solaris for quite a while- I started with an Ultra 2 about 20 years ago, ended with a Blade 2000- but I've transitioned to Linux and am not going back. I miss the Solaris experience a bit (but not the Oracle experience), besides running with modern and small and quiet... (0 Replies)
Discussion started by: gpounce32768
0 Replies
LEARN ABOUT MOJAVE
nisserver
nisserver(1M) System Administration Commands nisserver(1M)
NAME
nisserver - set up NIS+ servers
SYNOPSIS
/usr/lib/nis/nisserver -r [-x] [-f] [-v] [-Y] [ -d NIS+_domain] [ -g NIS+_groupname] [-l network_passwd]
/usr/lib/nis/nisserver -M [-x] [-f] [-v] [-Y] -d NIS+_domain [ -g NIS+_groupname] [ -h NIS+_server_host]
/usr/lib/nis/nisserver -R [-x] [-f] [-v] [-Y] [ -d NIS+_domain] [ -h NIS+_server_host]
DESCRIPTION
The nisserver shell script can be used to set up a root master, non-root master, and replica NIS+ server with level 2 security (DES). If
other authentication mechanisms are configured with nisauthconf(1M), nisserver will set up a NIS+ server using those mechanisms. nisauth-
conf(1M) should be used before nisserver.
When setting up a new domain, this script creates the NIS+ directories (including groups_dir and org_dir) and system table objects for the
domain specified. It does not populate the tables. nispopulate(1M) must be used to populate the tables.
OPTIONS
-d NIS+_domain Specifies the name for the NIS+ domain. The default is your local domain.
-f Forces the NIS+ server setup without prompting for confirmation.
-g NIS+_groupname Specifies the NIS+ group name for the new domain. This option is not valid with -R option. The default group is
admin.<domain>.
-h NIS+_server_host Specifies the hostname for the NIS+ server. It must be a valid host in the local domain. Use a fully qualified
hostname (for example, hostx.xyz.sun.com.) to specify a host outside of your local domain. This option is only
used for setting up non-root master or replica servers. The default for non-root master server setup is to use the
same list of servers as the parent domain. The default for replica server setup is the local hostname.
-l network_password Specifies the network password with which to create the credentials for the root master server. This option is
only used for master root server setup (-r option). If this option is not specified, the script prompts you for
the login password.
-M Sets up the specified host as a master server. Make sure that rpc.nisd(1M) is running on the new master server
before this command is executed.
-R Sets up the specified host as a replica server. Make sure that rpc.nisd is running on the new replica server.
-r Sets up the server as a root master server. Use the -R option to set up a root replica server.
-v Runs the script in verbose mode.
-x Turns the echo mode on. The script just prints the commands that it would have executed. Note that the commands
are not actually executed. The default is off.
-Y Sets up a NIS+ server with NIS-compatibility mode. The default is to set up the server without NIS-compatibility
mode.
USAGE
Use the first synopsis of the command (-r) to set up a root master server. To run the command, you must be logged in as super-user on the
server machine.
Use the second synopsis of the command (-M) to set up a non-root master server for the specified domain. To run the command, you must be
logged in as a NIS+ principal on a NIS+ machine and have write permission to the parent directory of the domain that you are setting up.
The new non-root master server machine must already be an NIS+ client (see nisclient(1M)) and have the rpc.nisd(1M) daemon running.
Use the third synopsis of the command (-R) to set up a replica server for both root and non-root domains. To run the command, you must be
logged in as a NIS+ principal on a NIS+ machine and have write permission to the parent directory of the domain that you are replicating.
The new non-root replica server machine must already be an NIS+ client and have the rpc.nisd daemon running.
EXAMPLES
Example 1: Setting up Servers
To set up a root master server for domain sun.com.:
root_server# /usr/lib/nis/nisserver -r -d sun.com.
For the following examples make sure that the new servers are NIS+ clients and that rpc.nisd is running on these hosts before executing
nisserver. To set up a replica server for the sun.com. domain on host sunreplica:
root_server# /usr/lib/nis/nisserver -R -d sun.com. -h sunrep
To set up a non-root master server for domain xyz.sun.com. on host sunxyz with the NIS+ groupname as admin-mgr.xyz.sun.com.:
root_server# /usr/lib/nis/nisserver -M -d xyz.sun.com. -h sunxyz
-g admin-mgr.xyz.sun.com.
To set up a non-root replica server for domain xyz.sun.com. on host sunabc:
sunxyz# /usr/lib/nis/nisserver -R -d xyz.sun.com. -h sunabc
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
nis+(1), nisgrpadm(1), nismkdir(1), nisaddcred(1M), nisauthconf(1M), nisclient(1M), nisinit(1M), nispopulate(1M), nisprefadm(1M), nis-
setup(1M), rpc.nisd(1M), attributes(5)
NOTES
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are
available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html.
SunOS 5.10 13 Dec 2001 nisserver(1M)