05-24-2013
Please get a new DIMM and fix. Run the diagnostics (Extended level) and once completed. Bring down the server and make it up and check if its shows full required Memory size..
If this doesnt work, you need replace a New tested Motherboard with RAM
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
In my script i am executing sql file and there are some variables in SQL files which are assigned at run time. one of the variable value is having more than 240 characters and at time of execution its getting failed with error as "is too long. maximum size is 240 characters."
... (1 Reply)
Discussion started by: pooga17
1 Replies
2. Solaris
Hi All,
I have new Netra 240 box which is not detecting its harddisk equiped with itse same har disk are detected when I swap with another machine.
Same time If I swap hardisk of other machine to this Netra 240 box, also do not work. I have checked chassis, cabling etc and all looks fine. ... (1 Reply)
Discussion started by: xpwistler
1 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
hey guys i'm in university and i bought my self a sun ultra SPARC netra 500mhz machine with the usb ports a vga gfc and cdrom drive
now i have a problem (bought it off ebay) i trying to install a fresh solaris 10 server op onto it but it looks like it previously had linix installed and... (38 Replies)
Discussion started by: garethmob
38 Replies
5. Solaris
Hi guys. I have an old Netra T1 that I'm hoping to recover here so I can twiddle around with Solaris 10.
It's been unable to power on despite issuing the "poweron" command or hitting the switch at the back of the server for some time. The LOM command "env" reports ALARM3 ON and everything else... (8 Replies)
Discussion started by: detach8
8 Replies
6. Solaris
Hi,
sunfire v240 and netra 240 are looks similar. system board, memory and processors are similar, then why netra 240 called as telco server?
can anyone tell the difference.
RJS (1 Reply)
Discussion started by: rajasekg
1 Replies
7. UNIX for Dummies Questions & Answers
Hello everyone,
I'm extremely new when it comes to SUN servers so bear with me and hopefully I can describe the issue I have accurately.
At work we just received a refurbished SUN Netra 240 server. I was told to change some of the EEprom settings, and to do that I was to use a... (0 Replies)
Discussion started by: afferbwt
0 Replies
8. Solaris
Hi,
When I am trying to boot my SUN Netra 240 Machine its giving some boot error.
> {1} ok boot -i
> Boot device: /pci@1c,600000/scsi@2/disk@0,0:a File and args: -i
> Boot load failed.
> The file just loaded does not appear to be executable.
> {1} ok
I tried to boot it from cdrom... (9 Replies)
Discussion started by: ppandey21
9 Replies
9. Solaris
I am trying to use a serial communications device that is connected to /dev/ttyb on a netra 240 server. This is a solaris zone configuration using solaris 10 0910. I am able to access /dev/ttyb from the global zone but not throught he non-global zone. I have enabled all of the tty devices in my... (0 Replies)
Discussion started by: disagreeable
0 Replies
10. Solaris
Hi,
One of my Netra 240 went into hung state and I had to reboot it. I powered it off and tried booting it again but unsuccessful. It is not connected to SAN and have local disks. Not able to boot in failsafe mode too.
There are two disks of 72GB, both are mirrored in SVM. It complains about... (5 Replies)
Discussion started by: solaris_1977
5 Replies
cmx(8) System Manager's Manual cmx(8)
Name
cmx - generic communication exerciser
Syntax
/usr/field/cmx [ -h ] [ -ofile ] [ -tn ] -l line-1 ...
Description
The exerciser will write, read, and validate random data and packet lengths on a given communications line. The line under test must have
a loopback connector attached to the distribution panel or the cable and the line must be disabled in the file and a non-modem line. That
is, the flag must be set to off.
The exerciser runs until or kill -15 pid is sent to the process.
A logfile is made in for you to examine and then remove. If there are errors listed in the logfile, make sure that you check the file,
because that is where the driver and kernel error messages are saved.
You must specify the -l flag followed by the lines to test. The line-n arguments identify the lines to be tested. A maximum of 32 lines
can be tested at any one time. The line-n arguments are specified as names taken from the directory without the letters ``tty''. For
example, if the directory lists tty03, the line argument is 03.
The DEVICES section lists the devices that can be tested.
Restrictions
If there is a need to run a system exerciser over an NFS link or on a diskless system there are some restrictions. For exercisers that
need to write into a file system, such as the target file system must be writable by root. Also the directory, in which any of the exer-
cisers are executed, must be writable by root because temporary files are written into the current directory. These latter restrictions
are sometimes difficult to overcome because often NFS file systems are mounted in a way that prevents root from writing into them. Some of
the restrictions may be overcome by copying the exerciser to another directory and then executing it.
Options
-h Prints help message about this command.
-ofile Save output diagnostics in file.
-tn Run time in minutes (n). The default is to run until a or kill -15 pid is sent to the process.
Restrictions
Pseudo devices (those whose first character after tty is p, q, r, s, t, u) cannot be tested. Neither can lta devices with major #39.
Devices
Use the command on to find out which tty line corresponds to a device line number.
Examples
The following example runs the exerciser for 60 minutes on lines 00, 13, 22, and 32.
% /usr/field/cmx -t60 -l 00 13 22 32
The following example runs the exerciser on lines 11, 42, 45, and 76 in the background until interrupted by a or kill -15 pid.
% /usr/field/cmx -l 11 42 45 76 &
See Also
Guide to System Exercisers
cmx(8)