05-05-2011
Supported Memory Configurations on Netra T2000
I need to upgrade the memory configuration on our T2000s to 24 Gb. I presently have 8x2Gb DIMMS in Rank 0 and 8x1Gb DIMMS in Rank 1, but the OS only recognizes 16Gb. How can I upgrade these T2000s to 24Gb?
9 More Discussions You Might Find Interesting
1. Solaris
I have one Sun Netra T2000 Server. The ALOM SC admin password of this server is not known. Could you anyone help and tell me how can i reset the SC admin account password??
Thanks in advance.. (2 Replies)
Discussion started by: sudhir_shet
2 Replies
2. Solaris
Hello All,
I was finaly was able to recover my root password, thanks to this board ;)
Now, I need to change the IP, well when I do netstat -rn the following displays:
192.168.0.77 127.0.0.1 UH 1 0 lo0
127.0.2.1 127.0.0.1 UH 1... (3 Replies)
Discussion started by: nexOne
3 Replies
3. Solaris
Hello,
I wrote a script which monitor the keyswitch state repeatedly each 10 minutes.
I'm extracting the keyswitch status by using prtdiag.
The script works fine for Netra v440 , but I found that prtdiag under Netra 1290 don't give keyswitch status.
unlike Netra 440 server , I found that... (2 Replies)
Discussion started by: Alalush
2 Replies
4. Solaris
Hi,
I have a netra t2000 running solaris 10. It is fully patched with the latest patch cluster and also patch 118833-36 and 126897-02. The SC sys_event level is set to 3.
I am running a test to show hardware log status, e.g simulating a power supply failure.Hence I unplug one of te... (3 Replies)
Discussion started by: ulemsee
3 Replies
5. Filesystems, Disks and Memory
Does anyone have experience with automating Raid configurations with Areca controllers? Or if this even possible. I'd like to setup a script to automate raiding of my machine over serial. Anyone have any experience, or anything similar to this?
Update: Perl::Expect is my friend. (0 Replies)
Discussion started by: dnbert
0 Replies
6. Solaris
I work with a network management tool, which, for various reasons, is installed on a solaris server.This is a Sunfire T2000 server with 16 CPUs and 8GB of RAM. I have installed a Solaris 10 ZFS and 8GB swap. From the beginning I had problems with memory occupation that it rises progressively to 95%... (4 Replies)
Discussion started by: drusa79
4 Replies
7. AIX
dears is the configurations in the red correct for sendmail.cf
DWdatawarehouse
my louts nots server = DSlstn-lono-svr
# ... define this only if sendmail cannot automatically determine your domain
#Dj$w.Foo.COM
# top level psuedo domains
CP.
# UUCP relay host
#DYrelayhostname... (4 Replies)
Discussion started by: thecobra151
4 Replies
8. Android
Running latest Android for Galaxy Tab 8.9 and bought a 32GB USB flash memory stick for file transfers, etc. Would not work. Searched the net for clues and could not find any. Then, back at the IT store, found out that Galaxy Tab currently only supports up to 16GB for the USD flash memory stick.... (0 Replies)
Discussion started by: Neo
0 Replies
9. Linux
Dear experts
I've managed to configure Blind, Zone files and i can view the domain that i created via nslookup and ping the domain on the same server.
Server: 41.216.x.xx
Address: 41.216.4.175#53
Name: mail.eeee.co.zm
Address: 41.216.x.xx
However, when... (1 Reply)
Discussion started by: herberwz
1 Replies
LEARN ABOUT OSF1
dh_systemd_start
DH_SYSTEMD_START(1) Debhelper DH_SYSTEMD_START(1)
NAME
dh_systemd_start - start/stop/restart systemd unit files
SYNOPSIS
dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]
DESCRIPTION
dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
sysv init script is available.
As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
which case it will only be restarted after the upgrade). This logic is not used when there is a corresponding SysV init script because
invoke-rc.d performs the stop/start/restart in that case.
OPTIONS
--restart-after-upgrade
Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10.
In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
--no-restart-after-upgrade
Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to
be stopped in the prerm script and started again in the postinst script.
-r, --no-stop-on-upgrade, --no-restart-on-upgrade
Do not stop service on upgrade.
--no-start
Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
corresponding init script).
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.
Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.
SEE ALSO
debhelper(7)
AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_START(1)