<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="IncrediMail 1.0">
<STYLE>v\:* {
BEHAVIOR: url (#default#vml)
}
</STYLE>
<style>v\:* {
BEHAVIOR: url (#default#vml)
}
</style>
<!--IncrdiXMLRemarkStart>
<IncrdiX-Info>
<X-FID>79F8FDE2-E90C-4120-9A2C-E484CCFAA091</X-FID>
<X-FVER></X-FVER>
<X-FIT></X-FIT>
<X-FILE></X-FILE>
<X-FCOL></X-FCOL>
<X-FCAT></X-FCAT>
<X-FDIS></X-FDIS>
<X-Extensions></X-Extensions>
<X-BG>cid:49A933F2-78A0-40F1-8B65-31BE336043F1</X-BG>
<X-BGT>repeat</X-BGT>
<X-BGC>#f3eded</X-BGC>
<X-BGPX>left</X-BGPX>
<X-BGPY>top</X-BGPY>
<X-ASN></X-ASN>
<X-ASNF></X-ASNF>
<X-ASH></X-ASH>
<X-ASHF></X-ASHF>
<X-AN></X-AN>
<X-ANF></X-ANF>
<X-AP></X-AP>
<X-APF></X-APF>
<X-AD></X-AD>
<X-ADF></X-ADF>
<X-AUTO>X-ASN,X-ASH,X-AN,X-AP,X-AD</X-AUTO>
<X-CNT>;</X-CNT>
</IncrdiX-Info>
<IncrdiXMLRemarkEnd-->
</HEAD>
<BODY style="SCROLLBAR-ARROW-COLOR: #4a6184; SCROLLBAR-FACE-COLOR: #c6d7ff; MARGIN: 0px 10px 10px; BACKGROUND-REPEAT: repeat; SCROLLBAR-DARKSHADOW-COLOR: #bebebe; FONT-FAMILY: Arial; BACKGROUND-POSITION: left top; SCROLLBAR-HIGHLIGHT-COLOR: #ffffff; COLOR: #010158; SCROLLBAR-SHADOW-COLOR: #ffffff; FONT-SIZE: 12pt; SCROLLBAR-3DLIGHT-COLOR: #7b9ed6" background=cid:49A933F2-78A0-40F1-8B65-31BE336043F1 aLink=#0000ff scroll=yes link=#0000ff bgColor=#f3eded text=#010158 vLink=#0000ff SIGCOLOR="11031552">
<TABLE id=INCREDIMAINTABLE border=0 cellSpacing=0 cellPadding=2 width="100%">
<TBODY>
<TR>
<TD style="DIRECTION: ltr; FONT-SIZE: 12pt" dir=ltr id=INCREDITEXTREGION vAlign=top width="100%">
<DIV>Look through the script and make sure it is calling the same path you do when you manually run prtdiag. I have had issues with uname -i resolution on some hardware (sun4u vs sun4us on fujitsu hardware running solaris.)</DIV>
<DIV> </DIV>
<DIV>You can echo out the critical vars to a file when it runs to see what gets set. Think script debugging to output files.</DIV>
<DIV> </DIV>
<DIV>BTW - for the group - I have been working on the meta probe Galen wrote originally for my environment - I got it to go yellow on resyncs of the mirrors (SDS mirrored system volumes and some soft partitions), Today I got it to look for orphan meta devices, singletons that are not mounted, that would signal a broken mirror. I chose to look for singletons, as mirrors can be 3 way or more. I set a yellow and tell the viewer of a possible broken mirror , then list the single devices. I am thinking of putting in an exclusion file, so if a device is known and wanted to be this way for whatever purpose - it could be listed as an ignore.</DIV>
<DIV> </DIV>
<DIV>Any thoughts of other functions the Meta might look for? (we use default 2 way mirroring in SDS (aka SVM) so that I know best!</DIV>
<DIV> </DIV>
<DIV>Brian</DIV>
<DIV> </DIV>
<DIV id=INCREDISIGNATUREID>
<DIV>lurch@inorbit.com</DIV></DIV>
<DIV dir=ltr id=IncrediOriginalMessage><I>-------Original Message-------</I></DIV>
<DIV> </DIV>
<DIV id=receivestrings>
<DIV style="FONT-SIZE: 11pt" dir=ltr><I><B>From:</B></I> <A href="mailto:Craig.Cook@carquest.com">Craig Cook</A></DIV>
<DIV style="FONT-SIZE: 11pt" dir=ltr><I><B>Date:</B></I> 8/31/2009 11:05:27 AM</DIV>
<DIV style="FONT-SIZE: 11pt" dir=ltr><I><B>To:</B></I> <A href="mailto:hobbit@hswn.dk">hobbit@hswn.dk</A></DIV>
<DIV style="FONT-SIZE: 11pt" dir=ltr><I><B>Subject:</B></I> RE: [hobbit] bb-prtdiag.sh - Sun SPARC Enterprise M9000 Server</DIV></DIV>
<DIV> </DIV>
<DIV>>I am having truble with the bb-prtdiag script on "Sun SPARC Enterprise M9000 Server " and also "SUNW,UltraAX-i2" hardware. Always saying something is wrong when I cant see anything wrong?</DIV>
<DIV> </DIV>
<DIV>The M9000 has not explicitly been added for support.</DIV>
<DIV> </DIV>
<DIV>Check the readme with the bb-prtdiag tar file for how to run the built in debug.</DIV>
<DIV>There is also information in the comment section at the top of the script.</DIV>
<DIV> </DIV>
<DIV>Support for UltraAX-i2 has been added, run debug to find out why/where it is complaining.</DIV>
<DIV> </DIV>
<DIV>>bb-prtdiag is a very simple test. It looks at the return code of the prtdiag command.</DIV>
<DIV>No. bb-prtdiag does not look at the return code from running prtdiag. If you want a simple prtdiag check there is another one on deadcat.</DIV>
<DIV> </DIV>
<DIV>Craig</DIV>
<DIV> </DIV>
<DIV>To unsubscribe from the hobbit list, send an e-mail to</DIV>
<DIV><A href="mailto:hobbit-unsubscribe@hswn.dk">hobbit-unsubscribe@hswn.dk</A></DIV>
<DIV> </DIV>
<DIV> </DIV></TD></TR>
<TR>
<TD id=INCREDIFOOTER width="100%">
<TABLE cellSpacing=0 cellPadding=0 width="100%">
<TBODY>
<TR>
<TD width="100%"></TD>
<TD id=INCREDISOUND vAlign=bottom align=middle></TD>
<TD id=INCREDIANIM vAlign=bottom align=middle></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE></BODY></HTML>