Sponsored Content
Full Discussion: SUN T5240 vs M3000
Operating Systems Solaris SUN T5240 vs M3000 Post 302430591 by rajasekg on Friday 18th of June 2010 05:37:21 AM
Old 06-18-2010
SUN T5240 vs M3000

Thanks for your suggestion
 

9 More Discussions You Might Find Interesting

1. Solaris

raidctl on SUN T5240

Setting up a T5240 with two disks c1t0d0 and c1t1d0. I am trying to use raidctl but when I issue. raidctl -l I get Controller 1 Disk: 0.0.0 Disk: 0.1.0 So I try raidctl -c '0.0.0 0.1.0' -r 1 1 and I get "Array in use." I try (4 Replies)
Discussion started by: photon
4 Replies

2. Solaris

Can't PowerOn M3000 - Bad Data CRC

Hi, I was working on the M3000 and I did a init 0, powered off the system during the weekend. When I tried to poweron today, the XSCF linux boot image keeps on rebooting and does not go to the login for XSCF access. The "Check" LED is on amber. Tried diagnosing but cant get the system up. Any help... (1 Reply)
Discussion started by: incredible
1 Replies

3. Solaris

Raidctl - Sun T5240 Solaris 10 Problem

I tried using raidctl earlier today to use my 2 disks in a RAID1 setup and I totally destroyed my OS install. I'm sure I did something funky and it freaked out. No big deal...right? This is what I was seeing after a reboot. I decided to just reinstall the OS. It let me go through all of... (3 Replies)
Discussion started by: kingdbag
3 Replies

4. Solaris

XSCF on M3000

Hi, I've updated a few M3000s to new firmware without any hassle, but on one of them the following is happening: XSCF> getflashimage -u wayner ftp://10.16.122.200/tftpboot/IKXCP1102.tar.gz Error: insufficient free space Any idea how to delete whatever old firmware is on there so I can... (7 Replies)
Discussion started by: cabaiste
7 Replies

5. Solaris

Bizarre Sun T5240 behavior

Hi - I have a T5240 with 7 LDOMS configured. One night, network comm was broken somehow. Nobody was doing anything on the machine at the time. Here is what I saw in messages: WARNING: nxge3 : nxge_dma_mem_alloc: ddi_dma_mem_alloc kmem alloc failed WARNING: nxge3 : nxge_alloc_rx_buf_dma:... (2 Replies)
Discussion started by: pyroman
2 Replies

6. Emergency UNIX and Linux Support

disk replacment, SUN M3000

we have a SUN M3000 server. setup as only 1 domain. disk c0t0d0 and c0t1d0 and setup as SVM mirrors. a few days ago disk T1 failed. new we have replaced the disk, but can's see the disk in format. have done cfgadm and devfsadm. still can't access the new disk in format. the output... (6 Replies)
Discussion started by: robsonde
6 Replies

7. Solaris

Application running too slow on Sun SPARC T5440 but run normal on sun M3000

Hi all, I have application running on sun server T5440 4x8x1.4 GHz, 64 GB RAM, application running very slow though load average too low. when I install my application on another server SUN M3000 (One CPU 1x8x2.5GHz, 8GB RAM), application run smoothly. Here is my server T5440 info: ... (6 Replies)
Discussion started by: insatiable1610
6 Replies

8. Solaris

Poor performance on an M3000

Hi We have an M3000 single physical processor and 8gb of memory running Solaris 10. This system runs two Oracle Databases one on Oracle 9i and One on Oracle 10g. As soon as the Oracle 10g database starts we see an immediate drop in system performance, for example opening an ssh session can... (6 Replies)
Discussion started by: gregsih
6 Replies

9. Solaris

Using a Modem on a T5-2 or a T5240

Hi Folks, Just a quick question - hopefully! I have an application currently running on a V890 with Solaris 9, I'd like to move this to either one of our T-5's or one of the T5240's in a Legacy container on an LDOM - but the fly in the ointment is the application still uses a standard Hayes... (3 Replies)
Discussion started by: gull04
3 Replies
certmonger(1)						      General Commands Manual						     certmonger(1)

NAME
getcert SYNOPSIS
getcert stop-tracking [options] DESCRIPTION
Tells certmonger to stop monitoring or attempting to obtain or refresh a certificate. TRACKING OPTIONS
-i NAME The certificate was tracked using the request with the specified nickname. If this option is not specified, some combination of -d and -n or -f can be used to specify which certificate should henceforth be forgotten. KEY AND CERTIFICATE STORAGE OPTIONS
-d DIR The certificate is the one stored in the specified NSS database. -n NAME The certificate is the one which has this nickname. Only valid with -d. -t TOKEN If the NSS database has more than one token available, the certificate is stored in this token. This argument only rarely needs to be specified. Only valid with -d. -f FILE The certificate is or was to be stored in this file. -k FILE The private key is or was to be stored in this file. Only valid with -f. OTHER OPTIONS
-v Be verbose about errors. Normally, the details of an error received from the daemon will be suppressed if the client can make a diagnostic suggestion. BUGS
Please file tickets for any that you find at https://fedorahosted.org/certmonger/ SEE ALSO
certmonger(8) getcert(1) getcert-list(1) getcert-list-cas(1) getcert-request(1) getcert-resubmit(1) getcert-start-tracking(1) certmonger- certmaster-submit(8) certmonger-ipa-submit(8) certmonger_selinux(8) certmonger Manual 3 November 2009 certmonger(1)
All times are GMT -4. The time now is 05:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy