09-30-2010
Migrate from MPXIO to Powerpath
Here is the issue:
I am building a database server using Solaris 10x86 U8.
The system is jumpstarted with mpxio enabled and booting from the san.
We need to have powerpath 5.3 installed and would like to have powerpath take control of the the boot san as well or have mpxio control the san boot drive and powerpath control any other san drive connected.
Anyone else already try this?
Any tips or anything at all?!
10 More Discussions You Might Find Interesting
1. Solaris
Hi All,
I have one question.
I found out that my system setting for mpxio-disable=yes. Sun recommend to change it to mpxio-disable=no and run stmsboot -e command.
But no one can tell will it affect the system or not and the system is sol-10 and using veritas volume manager and attached... (3 Replies)
Discussion started by: mailbox80
3 Replies
2. Solaris
Hi,
I have a quick question.
How can I see MPXIO statistics (like errors, how many I/O|throuput per path, ....) on Solaris 10? Does maybe a ready dtrace script exist (I do not have the knowledge to write one myself)?
I would be happy if somebody knows some good documentation/links (with... (1 Reply)
Discussion started by: victorinox
1 Replies
3. Solaris
How to change the following values in power path from SP B to SP A ?
Owner: default=SP B, current=SP B
this is excerpt from powermt display dev=all (3 Replies)
Discussion started by: fugitive
3 Replies
4. AIX
Hi Guys,
I have a problem while trying to upgrade to more current EMC powerpath software on AIX 5.3 - respectively uninstalling the existing one.
I tried to deinstall the powerpath software with removed disks - was working perfectly fine on 12 servers - but number 13 is failing with errors:
... (4 Replies)
Discussion started by: zxmaus
4 Replies
5. Red Hat
Hi ,
I have a redhat 5.3 server which has 2 vg.. one is rootvg in local harddisk and another one is applicationvg in SAN.. When I reboot the server , EMC powerpath driver is not starting up automatically. Hence applicationvg is not mounting properly. Therefore I need to unmount it manually and... (4 Replies)
Discussion started by: Makri
4 Replies
6. Solaris
Hi Kudo,
I wanna to know that how can I do mpxio device name to os native name mapping without using stmsboot -L I tried everything still not able to got the solution till I able to get these o/p
here is native disk info as well physical wat is the logical OS name of the disk
... (1 Reply)
Discussion started by: tarunn.dubeyy
1 Replies
7. Solaris
Hello,
I have an issue with veritas volume manager version 5.0 in combination with EMC powerpath version 5.2.0 running on Solaris10(Sparc). This server is fiber connected to a EMC Clariion CX3-40 SAN.
This is the situation :
Server is a SUN Enterprise M5000
OS = Solaris10 Sparc
Veritas... (1 Reply)
Discussion started by: chipke2005
1 Replies
8. Linux
Hello guys, I'm going crazy over here with a problem with a LUN created on a EMC CX3.
I did sucessfully managed to create the LUN on the Storage (the LUN is named DBLNX25EC_TST), after doing the following process:
echo "1" > /sys/class/fc_host/host<n>/issue_lip
and
echo "- - -" >... (10 Replies)
Discussion started by: Zarnick
10 Replies
9. Solaris
Hi all
I am running the following hardware:
2 SUN Solaris 10 machines
They are connected to EMC clarion LUNs
We are running a Sun Cluster 3.2 managing both nodes
We are using Solaris Volume Manager to handle the shared storage for the cluster. It is using a number of named disk sets that is... (0 Replies)
Discussion started by: abohmeed
0 Replies
10. Solaris
It seems like I lost one path on my Solaris-11 box. But I want to make sure before going to Storage team, if issue is from OS side or Storage side. Storage team is able to see that only one wwwn is looged in their switch. I am not at server's physical location. What does below output says ? I... (0 Replies)
Discussion started by: solaris_1977
0 Replies
LEARN ABOUT CENTOS
strongimcv_pki---self
PKI --SELF(1) strongSwan PKI --SELF(1)
NAME
pki --self - Create a self-signed certificate
SYNOPSIS
pki --self [--in file|--keyid hex] [--type t] --dn distinguished-name [--san subjectAltName] [--lifetime days] [--serial hex] [--flag flag]
[--digest digest] [--ca] [--ocsp uri] [--pathlen len] [--nc-permitted name] [--nc-excluded name] [--policy-mapping mapping]
[--policy-explicit len] [--policy-inhibit len] [--policy-any len] [--cert-policy oid [--cps-uri uri] [--user-notice text]]
[--outform encoding] [--debug level]
pki --self --options file
pki --self -h | --help
DESCRIPTION
This sub-command of pki(1) is used to create a self-signed certificate.
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.
-x, --keyid hex
Key ID of a private key on a smartcard.
-t, --type type
Type of the input key. Either rsa or ecdsa, defaults to rsa.
-d, --dn distinguished-name
Subject and issuer distinguished name (DN). Required.
-a, --san subjectAltName
subjectAltName extension to include in certificate. Can be used multiple times.
-l, --lifetime days
Days the certificate is valid, default: 1095.
-s, --serial hex
Serial number in hex. It is randomly allocated by default.
-e, --flag flag
Add extendedKeyUsage flag. One of serverAuth, clientAuth, crlSign, or ocspSigning. Can be used multiple times.
-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.
-b, --ca
Include CA basicConstraint extension in certificate.
-o, --ocsp uri
OCSP AuthorityInfoAccess URI to include in certificate. Can be used multiple times.
-p, --pathlen len
Set path length constraint.
-n, --nc-permitted name
Add permitted NameConstraint extension to certificate.
-N, --nc-excluded name
Add excluded NameConstraint extension to certificate.
-M, --policy-mapping issuer-oid:subject-oid
Add policyMapping from issuer to subject OID.
-E, --policy-explicit len
Add requireExplicitPolicy constraint.
-H, --policy-inhibit len
Add inhibitPolicyMapping constraint.
-A, --policy-any len
Add inhibitAnyPolicy constraint.
Certificate Policy
Multiple certificatePolicy extensions can be added. Each with the following information:
-P, --cert-policy oid
OID to include in certificatePolicy extension. Required.
-C, --cps-uri uri
Certification Practice statement URI for certificatePolicy.
-U, --user-notice text
User notice for certificatePolicy.
EXAMPLES
Generate a self-signed certificate using the given RSA key:
pki --self --in key.der --dn "C=CH, O=strongSwan, CN=moon"
--san moon.strongswan.org > cert.der
SEE ALSO
pki(1)
5.1.1 2013-07-31 PKI --SELF(1)