Sponsored Content
Operating Systems Solaris OVM Server for SPARC ... Need Your Help Guys ! Post 302767455 by Mack1982 on Thursday 7th of February 2013 12:10:52 AM
Old 02-07-2013
Nice article. Curiously he didn't use a cluster file system as share storage. We have successfully test live migration on FC with QFS on the shared storage.
Anyway, my actual question was in reference to OVM Manager support for SPARC. OVM Manager cannot detect any storage on the T4 servers.
 

9 More Discussions You Might Find Interesting

1. Solaris

sparc server 20

I am having a sparc server 20 machine. can i use normal svga monitor and normal(ps2)keyboard with it. pls any body help me out (1 Reply)
Discussion started by: ajay234
1 Replies

2. Solaris

VNC server from the Companion cd. Solaris 8 SPARC

hey. i have been installing the VNC server from the solaris Companion cd under solaris 8 SPARC, when i try to open the vncserver i get: Xvnc is not in your PATH, how do i add it to the PATH ? and how do i install it if i need to do that, thx (0 Replies)
Discussion started by: mads-nielsen
0 Replies

3. Solaris

Jumpstart sparc client using x86 server.

Can I use a Jumpstart enviroment on x86 to install a sparc64 client? The idea is to install Solaris in an virtual environment (Sun Virtual Box) running on a pc (AMD), configure a Jumpstart server, and have a SUN Ultra 60 (sparc64) installed via the Jumpstart server. The SUN has no cdrom... (4 Replies)
Discussion started by: eldiablo
4 Replies

4. Solaris

Sparc 20 Server and Drum Scanner...

I am looking for a free low overhead software to do basic TIFF-16 levels and to jpeg conversion. I know very little about the Solaris OS so any pointers in what 7.0 already provides and what free software is already out there for imaging and easy ftp is appreciated. We also want to do web... (0 Replies)
Discussion started by: aleatory
0 Replies

5. Solaris

Diskless RedHat from a SPARC server

Hi all having a problem getting the redhat image to actually start loding and i receive a TFTP:Access Denied error after the redhat diskless machine grabs an IP from the solaris server which has a small scope set up on it. Here is what I did: used 2 redhat machines and rsync'd a to a... (2 Replies)
Discussion started by: caddyjoe77
2 Replies

6. Hardware

sun sparc server hdd sled

does anyone know where to look for that piece of metal attached to hard drive that inserts it into server (fire v125)? I've tried ebay, with no luck. (seller requires verified paypal address which is unpossible here) (0 Replies)
Discussion started by: orange47
0 Replies

7. Solaris

SPARC Enterprise T5440 Server, can not power off

SPARC Enterprise T5440 Server, can not power off I connect to Service Processor via serial port and submit the following to boot the system, it boots fine but can not power off the system. Can someone help? The following takes me to unix login -> start /SYS -> start /SP/console... (6 Replies)
Discussion started by: paulk93
6 Replies

8. Emergency UNIX and Linux Support

Oracle/Xen/OVM/OCFS2/Multipath/SAN Problems

Setup: Multiple Virtual Machines running OEL5 / Oracle RDBMS 11.2 OVM 2 / Xen 3.4.0 Cluster consisting of 3 Machines Shared SAN Storage synced with OCFS2 SAN connected with 4GB FC on 4 Paths per LUN SAN target are 2 EMC Clariion mirroring each other The problems we're facing are that... (6 Replies)
Discussion started by: pludi
6 Replies

9. UNIX and Linux Applications

Suggestion on running critical Oracle DBs on OVM

Hello, We have few critical databases running on T series servers. Setup consists of LDOMS and zonemanager running on them and databases are running on their zones. We want to get away from this setup and looking for alternate solution to run our Oracle databases. One option is OVM from Oracle.... (7 Replies)
Discussion started by: solaris_1977
7 Replies
SM(1)							    InterNetNews Documentation							     SM(1)

NAME
sm - Command-line interface to the INN storage manager SYNOPSIS
sm [-cdHiqRrSs] [token ...] DESCRIPTION
The INN storage manager is the subsystem that stores and keeps track of all of the articles and what storage backend they're in. All stored articles are assigned a storage API token. sm is a command-line interface to that storage manager, primarily used to retrieve articles by those tokens but also to perform other operations on the storage subsystem. token is the token of an article (the same thing that's returned by grephistory or stored in the history file). It looks something like: @0502000005A4000000010000000000000000@ Any number of tokens can be given on the command-line for any function other than -s. If none are, sm normally reads tokens from standard input, one per line. The default operation is to retrieve and write to standard output the corresponding article for each token given. If -s is given, sm instead stores the article given on standard input (in native format, not wire format) using the standard rules of the storage subsystem. If the article is stored successfully, the token of the article is printed to standard output. Please note that this does not make any attempt to write a history entry or any overview data, and is therefore only useful under very specific circumstances. OPTIONS
-c Show a clear, decoded form of the storage API token. Each part of the token is explained, in a human-readable string. Amongst other elements, this command gives the path to where the corresponding article is supposed to be stored. -d, -r Rather than retrieving the specified article, remove the article. This will delete the article out of the news spool and it will not subsequently be retrievable by any part of INN. It's equivalent to "ctlinnd cancel" except it takes a storage API token instead of a message-ID. -H Retrieve only the headers of the article rather than the entire article. This option cannot be used with -d, -r, -i, or -S. -i Show the newsgroup name and article number associated with the token rather than the article itself. Note that for crossposted articles, only the first newsgroup and article number to which the article is associated will be returned. -q Suppress all error messages except usage errors. -R Display the raw article. This means that line endings won't be converted to native line endings and will be left as CRLF sequences; leading periods will still be escaped for sending over NNTP, and the article will end in a CRLF.CRLF sequence. -S Write the article to standard output in the format used by rnews spool files. Multiple articles can be written in this format, and the resulting output can be fed to rnews (on another system, for example) to inject those articles into INN. This option cannot be used with -d, -r, -H, -i, or -R. -s Store the article given on standard input using the normal storage rules for articles as configured in storage.conf(5). Print the new token for the message to standard output if it is stored successfully. If this option is given, no other options except possibly -q should be given. EXIT STATUS
If all operations were successful, sm exits with status 0. If an operation on any of the provided tokens fails, sm will exit with status 1, even if the operations on other tokens were successful. In other words, if twenty tokens are fed to "sm -r" on stdin, 19 articles were successfully removed, but the sixth article couldn't be found, sm will still exit with status 1. This means that if you need to be sure whether a particular operation succeeded, you should run sm on one token at a time. HISTORY
Written by Katsuhiro Kondou <kondou@nec.co.jp> for InterNetNews. Rewritten in POD by Russ Allbery <rra@stanford.edu>. $Id: sm.pod 8818 2009-11-17 18:58:24Z iulius $ SEE ALSO
ctlinnd(8), grephistory(1), history(5), rnews(1), storage.conf(5). INN 2.5.2 2010-02-08 SM(1)
All times are GMT -4. The time now is 11:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy