Veritas-bu

[Veritas-bu] Parity Errors flooding /var/adm/messages on Sola ris 2.6

2000-10-06 14:05:53
Subject: [Veritas-bu] Parity Errors flooding /var/adm/messages on Sola ris 2.6
From: Taylor, Larry A. LTaylor AT sempra DOT com
Date: Fri, 6 Oct 2000 11:05:53 -0700
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C02FC0.16964450
Content-Type: text/plain;
        charset="iso-8859-1"

Actually it's  the StorageTek 9740 robot only operates  at fast-wide (20
MBs) and the drives operate at Ultra fast-wide(40MBs).  Run the robot on
it's own SCSI controller; you can run two 9840 drives on the same controller
at 40 MBs without encountering the parity error/reducing transfer rate.

-----Original Message-----
From: Bob Bakh [mailto:bbakh AT veritas DOT com]
Sent: Friday, October 06, 2000 10:56 AM
To: Ray Frederick; R.G.Hall
Cc: Craig_Everett AT intuit DOT com; veritas-bu AT mailman.eng.auburn DOT edu;
SD_SA_Backup AT intuit DOT com
Subject: RE: [Veritas-bu] Parity Errors flooding /var/adm/messages on
Sola ris 2.6


One more cause which is funny, is if you use a SCSI cable that is just too
long, what is too long, well that's up to the computer to decide.

Those wacky computers and drives with their needs.

Bob

-----Original Message-----
From: Ray Frederick [mailto:ray AT west.gecems DOT com]
Sent: Friday, October 06, 2000 8:45 AM
To: R.G.Hall
Cc: Craig_Everett AT intuit DOT com; veritas-bu AT mailman.eng.auburn DOT edu;
SD_SA_Backup AT intuit DOT com
Subject: Re: [Veritas-bu] Parity Errors flooding /var/adm/messages on
Solaris 2.6


Right you are gang,

> > Oct  5 11:25:30 hostname unix: WARNING: /pci@6,4000/scsi@3 (glm4):
> > Oct  5 11:25:30 hostname unix:  SCSI bus DATA IN phase parity error

Pretty vague error but almost always caused by hardware failure along the
scsi
bus. ie. initiator, terminator, cable, bad device.  


> > Oct  5 11:25:30 hostname unix:  Target 5 reducing sync. transfer rate
> > Oct  5 11:25:30 hostname unix: WARNING :
ID[SUNWpd.glm.sync_wide_backoff.6014]

This is not really a failure but more a function of Solaris that allows a
fast
controller to work with slower devices. Remember that your bus will only be
as fast as the slowest device. But in this case it appears to have reduced
the bus speed in an effort to salvage a scsi transaction that failed.

RF


"R.G.Hall" wrote:
> 
> Just to say that this isn't the only possible cause. We got these errors
> when attaching an L280 to a U10. After an awful lot of phone calls, h/w
> swapping, checking for diferential vs single-ended cables and so on, it
> turned out that the short SCSI jumper cable between the two sides (ie
> between the drive and the robotics) was duff.
> 
> TTFN,
>  Richard Hall
> 
> On Thu, 5 Oct 2000, Donna Nadimi wrote:
> 
> > I ran into this exact problem recently!  I'm happy to share.
> >
> > The cause of this is that you have too many drives daisy-chained
together.
> > If you have more than two drives per SCSI bus, you get these data in
parity
> > errors.
> >
> > The only good solution is to unchain the drives.  I've found that two
drives
> > chained
> > together (and the robot) work well.  Anymore than that and you have a
> > transfer speed
> > problem between the Sun scsi controller and the drives.
> >
> > Good luck.
> >
> > --donna
> >
> > Donna Nadimi
> > UNIX Systems Engineer
> > Lucasfilm Ltd.
> > donna.nadimi AT lucasfilm DOT com
> >
> >
> >
> >
> > -----Original Message-----
> > From: Everett, Craig [mailto:Craig_Everett AT intuit DOT com]
> > Sent: Thursday, October 05, 2000 7:23 PM
> > To: 'veritas-bu AT mailman.eng.auburn DOT edu'
> > Cc: SD SA Backup
> > Subject: [Veritas-bu] Parity Errors flooding /var/adm/messages on
> > Solaris 2.6
> >
> >
> > I've got a large environment using Netbackup 3.2 installed on mostly Sun
> > E-450's running Solaris 2.6.
> >
> > These servers are attached to StorageTek 9740's and L700's using
DLT7000's.
> >
> > These servers are experiencing a flood of SCSI parity errors when the
> > DLT7000 drives are initialized.
> >
> > Sun doesn't seem to know what is causing this issue. We tried to apply a
Sun
> > SUNWpd patch with no relief.
> >
> > Has anyone else seen anything remotely similar to this and if so what
did
> > you do to resolve this issue.
> >
> > Below is an example of what I'm seeing.
> >
> >
> > Oct  5 11:25:30 hostname unix: WARNING: /pci@6,4000/scsi@3 (glm4):
> > Oct  5 11:25:30 hostname unix:  SCSI bus DATA IN phase parity error
> > Oct  5 11:25:30 hostname unix: WARNING: ID[SUNWpd.glm.parity_check.6010]
> > Oct  5 11:25:30 hostname unix: WARNING: /pci@6,4000/scsi@3 (glm4):
> > Oct  5 11:25:30 hostname unix:  Target 5 reducing sync. transfer rate
> > Oct  5 11:25:30 hostname unix: WARNING:
> > ID[SUNWpd.glm.sync_wide_backoff.6014]
> > Oct  5 11:25:30 hostname unix: WARNING: /pci@6,4000/scsi@3 (glm4):
> > Oct  5 11:25:30 hostname unix:  SCSI bus DATA IN phase parity error
> > Oct  5 11:25:30 hostname unix: WARNING: ID[SUNWpd.glm.parity_check.6010]
> > Oct  5 11:25:30 hostname unix: WARNING: /pci@6,4000/scsi@3 (glm4):
> > Oct  5 11:25:30 hostname unix:  SCSI bus DATA IN phase parity error
> > Oct  5 11:25:30 hostname unix: WARNING: ID[SUNWpd.glm.parity_check.6010]
> > Oct  5 11:25:30 hostname unix: WARNING: /pci@6,4000/scsi@3 (glm4):
> > Oct  5 11:25:30 hostname unix:  SCSI bus DATA IN phase parity error
> > Oct  5 11:25:30 hostname unix: WARNING: ID[SUNWpd.glm.parity_check.6010]
> > Oct  5 11:25:30 hostname unix: WARNING: /pci@6,4000/scsi@3 (glm4):
> > Oct  5 11:25:30 hostname unix:  SCSI bus DATA IN phase parity error
> >
> > Thanks,
> >
> >
> > Craig Everett
> > Intuit INC
> > San Diego
> > _______________________________________________
> > Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> > _______________________________________________
> > Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

------_=_NextPart_001_01C02FC0.16964450
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>RE: [Veritas-bu] Parity Errors flooding /var/adm/messages on =
Sola ris 2.6</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Actually it's&nbsp; the StorageTek 9740 robot only =
operates&nbsp; at fast-wide (20 MBs) and the drives operate at Ultra =
fast-wide(40MBs).&nbsp; Run the robot on it's own SCSI controller; you =
can run two 9840 drives on the same controller at 40 MBs without =
encountering the parity error/reducing transfer rate.</FONT></P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Bob Bakh [<A =
HREF=3D"mailto:bbakh AT veritas DOT com">mailto:bbakh AT veritas DOT 
com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Friday, October 06, 2000 10:56 AM</FONT>
<BR><FONT SIZE=3D2>To: Ray Frederick; R.G.Hall</FONT>
<BR><FONT SIZE=3D2>Cc: Craig_Everett AT intuit DOT com; =
veritas-bu AT mailman.eng.auburn DOT edu;</FONT>
<BR><FONT SIZE=3D2>SD_SA_Backup AT intuit DOT com</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] Parity Errors flooding =
/var/adm/messages on</FONT>
<BR><FONT SIZE=3D2>Sola ris 2.6</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>One more cause which is funny, is if you use a SCSI =
cable that is just too</FONT>
<BR><FONT SIZE=3D2>long, what is too long, well that's up to the =
computer to decide.</FONT>
</P>

<P><FONT SIZE=3D2>Those wacky computers and drives with their =
needs.</FONT>
</P>

<P><FONT SIZE=3D2>Bob</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Ray Frederick [<A =
HREF=3D"mailto:ray AT west.gecems DOT com">mailto:ray AT west.gecems DOT 
com</A>]</FON=
T>
<BR><FONT SIZE=3D2>Sent: Friday, October 06, 2000 8:45 AM</FONT>
<BR><FONT SIZE=3D2>To: R.G.Hall</FONT>
<BR><FONT SIZE=3D2>Cc: Craig_Everett AT intuit DOT com; =
veritas-bu AT mailman.eng.auburn DOT edu;</FONT>
<BR><FONT SIZE=3D2>SD_SA_Backup AT intuit DOT com</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Veritas-bu] Parity Errors flooding =
/var/adm/messages on</FONT>
<BR><FONT SIZE=3D2>Solaris 2.6</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Right you are gang,</FONT>
</P>

<P><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix: =
WARNING: /pci@6,4000/scsi@3 (glm4):</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix:&nbsp; =
SCSI bus DATA IN phase parity error</FONT>
</P>

<P><FONT SIZE=3D2>Pretty vague error but almost always caused by =
hardware failure along the</FONT>
<BR><FONT SIZE=3D2>scsi</FONT>
<BR><FONT SIZE=3D2>bus. ie. initiator, terminator, cable, bad =
device.&nbsp; </FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix:&nbsp; =
Target 5 reducing sync. transfer rate</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix: =
WARNING :</FONT>
<BR><FONT SIZE=3D2>ID[SUNWpd.glm.sync_wide_backoff.6014]</FONT>
</P>

<P><FONT SIZE=3D2>This is not really a failure but more a function of =
Solaris that allows a</FONT>
<BR><FONT SIZE=3D2>fast</FONT>
<BR><FONT SIZE=3D2>controller to work with slower devices. Remember =
that your bus will only be</FONT>
<BR><FONT SIZE=3D2>as fast as the slowest device. But in this case it =
appears to have reduced</FONT>
<BR><FONT SIZE=3D2>the bus speed in an effort to salvage a scsi =
transaction that failed.</FONT>
</P>

<P><FONT SIZE=3D2>RF</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&quot;R.G.Hall&quot; wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Just to say that this isn't the only possible =
cause. We got these errors</FONT>
<BR><FONT SIZE=3D2>&gt; when attaching an L280 to a U10. After an awful =
lot of phone calls, h/w</FONT>
<BR><FONT SIZE=3D2>&gt; swapping, checking for diferential vs =
single-ended cables and so on, it</FONT>
<BR><FONT SIZE=3D2>&gt; turned out that the short SCSI jumper cable =
between the two sides (ie</FONT>
<BR><FONT SIZE=3D2>&gt; between the drive and the robotics) was duff.</F=
ONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; TTFN,</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; Richard Hall</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; On Thu, 5 Oct 2000, Donna Nadimi wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I ran into this exact problem =
recently!&nbsp; I'm happy to share.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The cause of this is that you have too =
many drives daisy-chained</FONT>
<BR><FONT SIZE=3D2>together.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; If you have more than two drives per SCSI =
bus, you get these data in</FONT>
<BR><FONT SIZE=3D2>parity</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; errors.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; The only good solution is to unchain the =
drives.&nbsp; I've found that two</FONT>
<BR><FONT SIZE=3D2>drives</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; chained</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; together (and the robot) work well.&nbsp; =
Anymore than that and you have a</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; transfer speed</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; problem between the Sun scsi controller =
and the drives.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Good luck.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; --donna</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Donna Nadimi</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; UNIX Systems Engineer</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Lucasfilm Ltd.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; donna.nadimi AT lucasfilm DOT com</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; From: Everett, Craig [<A =
HREF=3D"mailto:Craig_Everett AT intuit DOT com">mailto:Craig_Everett AT intuit 
DOT com=
</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sent: Thursday, October 05, 2000 7:23 =
PM</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: =
'veritas-bu AT mailman.eng.auburn DOT edu'</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Cc: SD SA Backup</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: [Veritas-bu] Parity Errors =
flooding /var/adm/messages on</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Solaris 2.6</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I've got a large environment using =
Netbackup 3.2 installed on mostly Sun</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; E-450's running Solaris 2.6.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; These servers are attached to StorageTek =
9740's and L700's using</FONT>
<BR><FONT SIZE=3D2>DLT7000's.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; These servers are experiencing a flood of =
SCSI parity errors when the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; DLT7000 drives are initialized.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Sun doesn't seem to know what is causing =
this issue. We tried to apply a</FONT>
<BR><FONT SIZE=3D2>Sun</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; SUNWpd patch with no relief.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Has anyone else seen anything remotely =
similar to this and if so what</FONT>
<BR><FONT SIZE=3D2>did</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; you do to resolve this issue.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Below is an example of what I'm =
seeing.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix: =
WARNING: /pci@6,4000/scsi@3 (glm4):</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix:&nbsp; =
SCSI bus DATA IN phase parity error</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix: =
WARNING: ID[SUNWpd.glm.parity_check.6010]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix: =
WARNING: /pci@6,4000/scsi@3 (glm4):</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix:&nbsp; =
Target 5 reducing sync. transfer rate</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix: =
WARNING:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
ID[SUNWpd.glm.sync_wide_backoff.6014]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix: =
WARNING: /pci@6,4000/scsi@3 (glm4):</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix:&nbsp; =
SCSI bus DATA IN phase parity error</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix: =
WARNING: ID[SUNWpd.glm.parity_check.6010]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix: =
WARNING: /pci@6,4000/scsi@3 (glm4):</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix:&nbsp; =
SCSI bus DATA IN phase parity error</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix: =
WARNING: ID[SUNWpd.glm.parity_check.6010]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix: =
WARNING: /pci@6,4000/scsi@3 (glm4):</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix:&nbsp; =
SCSI bus DATA IN phase parity error</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix: =
WARNING: ID[SUNWpd.glm.parity_check.6010]</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix: =
WARNING: /pci@6,4000/scsi@3 (glm4):</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Oct&nbsp; 5 11:25:30 hostname unix:&nbsp; =
SCSI bus DATA IN phase parity error</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Thanks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Craig Everett</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Intuit INC</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; San Diego</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; <A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; <A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C02FC0.16964450--