10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
hi! i got a rhel 6.3 host that already have an xfs filesystem mounted from a SAN (let's call it SAN-1) whose size is 9TB.
i will be receiving another SAN (let's call it SAN-2) storage of 15TB size. this new addition is physically on another SAN storage. SAN-1 is on a Pillar storage while the new... (6 Replies)
Discussion started by: rino19ny
6 Replies
2. AIX
Hi Experts,
I have configured A D40 Array. There is an faulty disk which is not part of an raid volume but shows fault in the diagnostics.
pdisk15 U0.1-P1-I1/Q1-W40AA83CC2400D
SSA160 Physical Disk Drive ( MB)
Is there a way to stop this... (2 Replies)
Discussion started by: vuppala360
2 Replies
3. AIX
Hi All,
What's the proper procedure for removing SSA arrays? Is the procedure like these?
- rmdev ssa disk
- physical turn off the ssa
- cfgmgr
There's no more filesystem or logical volume on it. It's just pdisk and hdisk.
Thanks in advance,
itik (3 Replies)
Discussion started by: itik
3 Replies
4. AIX
Hi guys,
I'd like to share my migration/mirroring of ssa to san. No downtime for users, probably I/O performance.
here's the step:
1 After the lun had been carved on the SAN and the connections had been done on AIX fiber card
2 “lspv” and look for the new SAN hdisk? on the bottom, say... (1 Reply)
Discussion started by: itik
1 Replies
5. Linux
Dear Srs,
I have a Linux server (linux01) booting from SAN with a volume in a Nexsan SATAbeast storage array (san01). The disk/volume has four ext3 partitions, total size is near to 400GB, but only 20-30GB are in use.
I need to move this disk/volume to another Nexsan SATAbeast storage array... (0 Replies)
Discussion started by: Santi
0 Replies
6. Solaris
Hi everyone,
I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN?
At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies
7. AIX
I've a problem with an IBM StorageWorks - Seagate SSA drive, model ST373453LC (IBM P/N 24P3733, Type S53D073, 72,8 GB 15K - USCSI 4 - 320 SSA). I bought this disk used but working; it came from an unknown IBM SSA storage array. I've removed the SCA - SSA adapter (IBM 18P3051 - 001 - R0) and i tried... (0 Replies)
Discussion started by: Linolinux
0 Replies
8. AIX
I am in the process of updating ssa adapters, drives and enclosures and wanted to know if there are any caveats that anyone would like to share. The documentation is not very clear on the ordering of the updates.
Any tips would be appreciated. (1 Reply)
Discussion started by: chosie
1 Replies
9. AIX
Helo:
We updated form AIX 4.3.3 to AIX 5.1-7 and after this we spent more than double time in read from external disks. Aparently the ssa cards microcode is at last level and all the ptf and apars are instaled.
Out backups expent more than double time, but curiously in read only, if we write in... (0 Replies)
Discussion started by: Javier Gutierre
0 Replies
10. AIX
Hi
Can I add disks on the fly to extend the capacity of an existing RAID 5 volume?
It's created on a 4P Advanced SSA Raid Adapter.
I need to extend a volume group, so I figured it would be easiest to extend the "physical disk" which is a RAID5 volume.
Thanks. (1 Reply)
Discussion started by: osee
1 Replies
PKI --REQ(1) strongSwan PKI --REQ(1)
NAME
pki --req - Create a PKCS#10 certificate request
SYNOPSIS
pki --req [--in file] [--type type] --dn distinguished-name [--san subjectAltName] [--password password] [--digest digest]
[--outform encoding] [--debug level]
pki --req --options file
pki --req -h | --help
DESCRIPTION
This sub-command of pki(1) is used to create a PKCS#10 certificate request.
OPTIONS
-h, --help
Print usage information with a summary of the available options.
-v, --debug level
Set debug level, default: 1.
-+, --options file
Read command line options from file.
-i, --in file
Private key input file. If not given the key is read from STDIN.
-t, --type type
Type of the input key. Either rsa or ecdsa, defaults to rsa.
-d, --dn distinguished-name
Subject distinguished name (DN). Required.
-a, --san subjectAltName
subjectAltName extension to include in request. Can be used multiple times.
-p, --password password
The challengePassword to include in the certificate request.
-g, --digest digest
Digest to use for signature creation. One of md5, sha1, sha224, sha256, sha384, or sha512. Defaults to sha1.
-f, --outform encoding
Encoding of the created certificate file. Either der (ASN.1 DER) or pem (Base64 PEM), defaults to der.
EXAMPLES
Generate a certificate request for an RSA key, with a subjectAltName extension:
pki --req --in key.der --dn "C=CH, O=strongSwan, CN=moon"
--san moon@strongswan.org > req.der
Generate a certificate request for an ECDSA key and a different digest:
pki --req --in key.der --type ecdsa --digest sha256
--dn "C=CH, O=strongSwan, CN=carol" > req.der
SEE ALSO
pki(1)
5.1.1 2013-07-31 PKI --REQ(1)