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_01C3AE3E.98DACD6C
Content-Type: text/plain;
charset="iso-8859-1"
Hi Marianne,
Thanks for your infor, I only have a single sun server as backup and master
server going to Compaq SAN switch with two JNI cards, two fibre conneciton
to the switch, the first JNI card can see the robotic arm and the first 8
tape drive, the second JNI card see the other 8 tape drives. JNI card was
configured persistent binding by ports of the Tape library fibre-router, the
ATL FC230 fibre router has three ports, the frist two ports were used as the
last port is for failover. The first port going to two scsi bus, the first
scsi bus to robotic arm and two drives, second scsi bus to another two
drives, so each scsi port mapped to two drives. The setup is Fabric SAN
I still have a gut feel that below error messages is somethings to do with
NetBackup port communication or may be network related but don't know where
should I look into. tldd is the middleman talking to ltid and tldcd, somehow
tldd couldn't talk to tldcd and timeout then tape library going to DOWN
state, suprisingly after that tldd manages to talk to tldcd again and tape
libary going UP state again, it keeps on and on, and how this thing happen
and how to prevent it ? why tldd couldn't talk to tldcd in what kind of
circumstances ?
Nov 16 17:29:18 sgs15i-001 tldd[21598]: TLD(2) [21598] unable to connect to
tldcd on sgs15i-001: Cannot assign requested address (126)
Nov 16 17:29:18 sgs15i-001 tldd[1322]: TLD(2) going to DOWN state, status:
Control daemon connect or protocol error
Nov 16 17:33:22 sgs15i-001 tldd[1322]: TLD(2) going to UP state
Thanks a lot
Robert
-----Original Message-----
From: Marianne van den Berg
[mailto:Marianne.vandenBerg AT lechabilestorage.co DOT za]
Sent: Tuesday, November 18, 2003 8:00 PM
To: Robert Loh
Subject: RE: [Veritas-bu] Cannot assign requested address ?
Hi Robert
Are you by any chance using Arbitrated Loop in your SAN?
Have a look at the extract from the SSO manual - it looks as if Arbitrated
Loop gives you the worst performance.
Fibre Channel Topologies
Fibre channel protocol is designed to be low in overhead so it can function
over a device channel, yet flexible so messages have addresses and can be
efficiently switched. Devices that participate in fibre channel networking
have names and identities. Fibre channel was designed to be as adept for
carrying storage protocols (SCSI, HIPPI, and IPI) as carrying network
protocols (IP and ATM).
At the lowest layers of the 5-layer protocol, fibre channel defines the
following types of device connections.
Point-to-Point
This topology is the closest to a SCSI connection. It consists of two fibre
channel devices connected directly together. The transmit fibre of one
device goes to the receive fibre of the other device, and vice versa. There
is no sharing of the media, so the devices enjoy the total bandwidth of the
link. A link initialization is required of the two devices before
communication can begin.
Arbitrated Loop (FC-AL)
This is the most dominant fibre channel topology because of low cost, but is
falling out of favor because of poor performance. This topology allows up
to 126 devices to reside on a physical loop.Any device on the loop must
negotiate access to the loop in order to transfer data. The media is shared
among the devices, limiting each device's access.
Arbitrated loops are private in that devices on the loop are only visible to
the host where the loop is connected and only a minimal self-identification
procedure is conducted at system startup.
Switched Fibre Channel (Fibre Channel Fabric or Fabric)
This topology is used to connect many (up to 224) devices in a cross-point
switched configuration. The benefit of this topology is that many devices
can communicate at the same time and the media can be shared. It also
requires fibre channel switches.
Marianne van den Berg
Senior Support Engineer
LECHABILE Storage Solutions (PTY) Ltd
Tel: +27 11 519 8134
Mobile: +27 82 468 8107
mailto: Mariannev@LechabileSS <mailto:Mariannev AT LechabileSS.co DOT za>
.co.za
This e-mail and attachments relating thereto, is intended for the
above-mentioned recipient. If you have received this e-mail in error, kindly
notify the sender and delete it immediately as it contains information
relating to the official business of Lechabile Storage Solutions (Pty)
Limited, which is confidential, legally privileged and proprietary to
Lechabile Storage Solutions (Pty) Limited. Lechabile Storage Solutions (Pty)
Limited does not own and endorse any other content. The views and opinions
expressed in this e-mail are those of the sender unless clearly stated as
being those of Lechabile Storage Solutions (Pty) Limited.
-----Original Message-----
From: Robert Loh [mailto:robert AT softsource.com DOT sg]
Sent: Tuesday, November 18, 2003 3:52 AM
To: Marianne van den Berg
Subject: RE: [Veritas-bu] Cannot assign requested address ?
Hi Marianne,
I am very sure that the device configuration files are all correct, if not I
would be able to mount/unmount backup to respective drives successfully. We
are using JNI so persistent binding was setup and below error messages
occurred no because of server after reboot.
Weirld thing is it says going to down then after few minutes it come up by
itself. DOWN and UP make me feel very worry. Any other thought ? :)
Oh yes, sgscan return the right config.
CHeers....
Robert
-----Original Message-----
From: Marianne van den Berg
[mailto:Marianne.vandenBerg AT lechabilestorage.co DOT za]
Sent: Monday, November 17, 2003 4:50 PM
To: Robert Loh
Subject: RE: [Veritas-bu] Cannot assign requested address ?
Hi Robert
Have you checked output from sgscan? Compare this output with your device
configuration.
If persistent binding is not in place, it is possible that device names were
changed after a reboot.
Regards
Marianne van den Berg
Senior Support Engineer
LECHABILE Storage Solutions (PTY) Ltd
Tel: +27 11 519 8134
Mobile: +27 82 468 8107
mailto: Mariannev@LechabileSS <mailto:Mariannev AT LechabileSS.co DOT za>
.co.za
This e-mail and attachments relating thereto, is intended for the
above-mentioned recipient. If you have received this e-mail in error, kindly
notify the sender and delete it immediately as it contains information
relating to the official business of Lechabile Storage Solutions (Pty)
Limited, which is confidential, legally privileged and proprietary to
Lechabile Storage Solutions (Pty) Limited. Lechabile Storage Solutions (Pty)
Limited does not own and endorse any other content. The views and opinions
expressed in this e-mail are those of the sender unless clearly stated as
being those of Lechabile Storage Solutions (Pty) Limited.
-----Original Message-----
From: Robert Loh [mailto:robert AT softsource.com DOT sg]
Sent: Monday, November 17, 2003 10:04 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Cannot assign requested address ?
Hi folks,
NetBackup 3.4.2 with ATL P7000 16 x SDLT220 LVD drives connected to Compaq
SAN switch with a single backup server (media server)
Always receiving error below in my /var/adm/messages in Solaris 8
Nov 16 17:29:18 sgs15i-001 tldd[21598]: TLD(2) [21598] unable to connect to
tldcd on sgs15i-001: Cannot assign requested address (126)
Nov 16 17:29:18 sgs15i-001 tldd[1322]: TLD(2) going to DOWN state, status:
Control daemon connect or protocol error
Nov 16 17:33:22 sgs15i-001 tldd[1322]: TLD(2) going to UP state
Nov 16 18:15:53 sgs15i-001 tldd[9349]: TLD(2) [9349] unable to connect to
tldcd on sgs15i-001: Cannot assign requested address (126)
Nov 16 18:15:53 sgs15i-001 tldd[1322]: TLD(2) going to DOWN state, status:
Control daemon connect or protocol error
Nov 16 18:18:22 sgs15i-001 tldd[1322]: TLD(2) going to UP state
NetBackup error or tape library error !
Appreciate for helping.
Thanks.Robert
------_=_NextPart_001_01C3AE3E.98DACD6C
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>[Veritas-bu] Cannot assign requested address ?</TITLE>
<META content="MSHTML 6.00.2800.1106" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=297023901-19112003>Hi
Marianne,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=297023901-19112003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=297023901-19112003>Thanks
for your infor, I only have a single sun server as backup and master server
going to Compaq SAN switch with two JNI cards, two fibre conneciton to the
switch, the first JNI card can see the robotic arm and the first 8 tape drive,
the second JNI card see the other 8 tape drives. JNI card was configured
persistent binding by ports of the Tape library fibre-router, the ATL FC230
fibre router has three ports, the frist two ports were used as the last port is
for failover. The first port going to two scsi bus, the first scsi bus to
robotic arm and two drives, second scsi bus to another two drives, so each scsi
port mapped to two drives. The setup is Fabric SAN</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=297023901-19112003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=297023901-19112003>I
still have a gut feel that below error messages is somethings to do with
NetBackup port communication or may be network related but don't know where
should I look into. tldd is the middleman talking to ltid and tldcd, somehow
tldd couldn't talk to tldcd and timeout then tape library going to DOWN state,
suprisingly after that tldd manages to talk to tldcd again and tape libary
going
UP state again, it keeps on and on, and how this thing happen and how to
prevent
it ? why tldd couldn't talk to tldcd in what kind of circumstances
?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=297023901-19112003>
<P><FONT size=2>Nov 16 17:29:18 sgs15i-001 tldd[21598]: TLD(2) [21598] unable
to
connect to tldcd on sgs15i-001: Cannot assign requested address
(126)</FONT></P></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=297023901-19112003><FONT
face="Times New Roman" color=#000000>Nov 16 17:29:18 sgs15i-001 tldd[1322]:
TLD(2) going to DOWN state, status: Control daemon connect or protocol
error</FONT><FONT color=#000000><FONT face="Times New Roman"><FONT size=3>
<BR></FONT><FONT size=2>Nov 16 17:33:22 sgs15i-001 tldd[1322]: TLD(2) going to
UP state</FONT><FONT size=3> </FONT></FONT></FONT><BR></SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=297023901-19112003>Thanks
a lot</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=297023901-19112003>Robert</DIV></SPAN></FONT>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Marianne van den Berg
[mailto:Marianne.vandenBerg AT lechabilestorage.co DOT za]<BR><B>Sent:</B>
Tuesday,
November 18, 2003 8:00 PM<BR><B>To:</B> Robert Loh<BR><B>Subject:</B> RE:
[Veritas-bu] Cannot assign requested address ?<BR><BR></FONT></DIV>
<DIV id=0></DIV>
<DIV><SPAN class=734175011-18112003><FONT face=Arial color=#0000ff
size=2> Hi Robert</FONT></SPAN></DIV>
<DIV><SPAN class=734175011-18112003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=734175011-18112003><FONT face=Arial color=#0000ff
size=2>Are you by any chance using Arbitrated Loop in your
SAN? </FONT></SPAN></DIV>
<DIV><SPAN class=734175011-18112003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=734175011-18112003><FONT face=Arial color=#0000ff
size=2>Have
a look at the extract from the SSO manual - it looks as if Arbitrated Loop
gives you the worst performance.</FONT> </SPAN></DIV>
<DIV><SPAN class=734175011-18112003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=734175011-18112003><B><FONT face=Arial>
<P align=left>Fibre Channel Topologies</P></B></FONT><FONT
face="Times New Roman">
<P align=left><FONT size=2>Fibre channel protocol is designed to be low in
overhead so it can function over a device<SPAN class=734175011-18112003><FONT
face=Arial color=#0000ff> </FONT></SPAN>channel, yet flexible
so <SPAN class=734175011-18112003><FONT face=Arial color=#0000ff>
</FONT></SPAN>messages have addresses and can be efficiently switched.
Devices<SPAN class=734175011-18112003><FONT face=Arial color=#0000ff>
</FONT></SPAN>that participate in fibre channel networking have names and
identities. Fibre channel was<SPAN class=734175011-18112003><FONT face=Arial
color=#0000ff> </FONT></SPAN>designed to be as adept for carrying
storage protocols (SCSI, HIPPI, and IPI) as carrying<SPAN
class=734175011-18112003><FONT face=Arial color=#0000ff>
</FONT></SPAN></FONT><FONT size=2>network protocols (IP and ATM).</FONT></P>
<P align=left><FONT size=2>At the lowest layers of the 5-layer protocol,
fibre
channel defines the following types of<SPAN class=734175011-18112003><FONT
face=Arial color=#0000ff> </FONT></SPAN></FONT><FONT size=2>device
connections.</FONT></P></FONT><B><FONT face=Arial size=1>
<P align=left><FONT size=2>Point-to-Point</FONT></P></B></FONT><FONT
face="Times New Roman" size=1>
<P align=left>This topology is the closest to a SCSI connection. It consists
of two fibre channel devices connected<SPAN class=734175011-18112003><FONT
face=Arial color=#0000ff size=2> </FONT></SPAN>directly together. The
transmit fibre of one device goes to the receive fibre of the other device,
and<SPAN class=734175011-18112003><FONT face=Arial color=#0000ff
size=2>
</FONT></SPAN>vice versa. There is no sharing of the media, so the devices
enjoy the total bandwidth of the link. A<SPAN class=734175011-18112003><FONT
face=Arial color=#0000ff size=2> </FONT></SPAN>link initialization is
required of the two devices before communication can
begin.</P></FONT><B><FONT
face=Arial size=1>
<P align=left><FONT size=2>Arbitrated Loop (FC-AL)</FONT></P></B></FONT><FONT
face="Times New Roman" size=1>
<P align=left>This is the most dominant fibre channel topology because of low
cost, but is falling out of favor<SPAN class=734175011-18112003><FONT
face=Arial color=#0000ff size=2> </FONT></SPAN>because of poor
performance. This topology allows up to 126 devices to reside on a physical
loop.Any device on the loop must negotiate access to the loop in order to
transfer data. The media is<SPAN class=734175011-18112003><FONT face=Arial
color=#0000ff size=2> </FONT></SPAN>shared among the devices, limiting
each device</FONT><FONT face="Times New Roman" size=1>'</FONT><FONT
face="Times New Roman" size=1>s access.</P>
<P align=left>Arbitrated loops are private in that devices on the loop are
only visible to the host where the loop<SPAN class=734175011-18112003><FONT
face=Arial color=#0000ff size=2> </FONT></SPAN>is connected and only a
minimal self-identification procedure is conducted at system
startup.</P></FONT><B><FONT face=Arial size=1>
<P align=left><FONT size=2>Switched Fibre Channel (Fibre Channel Fabric or
Fabric)</FONT></P></B></FONT><FONT face="Times New Roman" size=1>
<P align=left>This topology is used to connect many (up to 2</FONT><FONT
face="Times New Roman" size=1>24</FONT><FONT face="Times New Roman" size=1>)
devices in a cross-point switched configuration.<SPAN
class=734175011-18112003><FONT face=Arial color=#0000ff size=2>
</FONT></SPAN>The benefit of this topology is that many devices can
communicate at the same time and the media<SPAN
class=734175011-18112003><FONT
face=Arial color=#0000ff size=2> </FONT></SPAN>can be shared. It also
requires fibre channel switches.</P></FONT> </SPAN><BR><BR></DIV><SPAN
id=hbblock>
<DIV> </DIV>
<DIV> </DIV>
<P><B><FONT face="Comic Sans MS" size=2>Marianne van den
Berg<BR></FONT></B><FONT face="Comic Sans MS" size=2>Senior Support
Engineer<BR></FONT><B></B><B><FONT face=Roman size=2>LECHABILE Storage
Solutions (PTY) Ltd<BR></FONT></B><FONT face="Comic Sans MS" size=2>Tel: +27
11 519 8134<BR>Mobile: +27 82 468 8107<BR>mailto:</FONT><U> <FONT
face="Times New Roman" color=#0000ff size=2><A
href="mailto:Mariannev AT LechabileSS.co DOT
za">Mariannev@LechabileSS</FONT><FONT
face="Times New Roman" color=#0000ff size=2>.co.za</A> </FONT></U></P>
<P><B><I><FONT face="Comic Sans MS" color=#800080 size=1>This e-mail and
attachments relating thereto, is intended for the above-mentioned recipient.
If you have received this e-mail in error, kindly notify the sender and
delete
it immediately as it contains information relating to the official business
of
Lechabile Storage Solutions (Pty) Limited, which is confidential, legally
privileged and proprietary to Lechabile Storage Solutions (Pty) Limited.
Lechabile Storage Solutions (Pty) Limited does not own and endorse any other
content. The views and opinions expressed in this e-mail are those of the
sender unless clearly stated as being those of Lechabile Storage Solutions
(Pty) Limited.</FONT></I></B><I></I></P>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Robert Loh
[mailto:robert AT softsource.com DOT sg]<BR><B>Sent:</B> Tuesday, November
18, 2003
3:52 AM<BR><B>To:</B> Marianne van den Berg<BR><B>Subject:</B> RE:
[Veritas-bu] Cannot assign requested address ?<BR><BR></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=883525301-18112003>Hi
Marianne,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=883525301-18112003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=883525301-18112003>I
am very sure that the device configuration files are all correct, if not I
would be able to mount/unmount backup to respective drives successfully. We
are using JNI so persistent binding was setup and below error messages
occurred no because of server after reboot.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=883525301-18112003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=883525301-18112003>Weirld thing is it says going to down then after
few minutes it come up by itself. DOWN and UP make me feel very worry. Any
other thought ? :)</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=883525301-18112003>Oh
yes, sgscan return the right config.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=883525301-18112003>CHeers....<BR>Robert</SPAN></FONT></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Marianne van den Berg
[mailto:Marianne.vandenBerg AT lechabilestorage.co DOT
za]<BR><B>Sent:</B>
Monday, November 17, 2003 4:50 PM<BR><B>To:</B> Robert
Loh<BR><B>Subject:</B> RE: [Veritas-bu] Cannot assign requested address
?<BR><BR></FONT></DIV>
<DIV id=0></DIV><FONT face=Arial color=#0000ff size=2></FONT><FONT
face=Arial color=#0000ff size=2></FONT><BR><SPAN
class=034464608-17112003><FONT face=Arial color=#0000ff size=2> Hi
Robert </FONT></SPAN><BR><SPAN id=hbblock><LABEL id=HbSession
SessionId="1849968924"></LABEL>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=034464608-17112003><FONT face=Arial color=#0000ff
size=2>Have you checked output from sgscan? Compare this output with your
device configuration.</FONT></SPAN></DIV>
<DIV><SPAN class=034464608-17112003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=034464608-17112003><FONT face=Arial color=#0000ff
size=2>If persistent binding is not in place, it is possible that device
names were changed after a reboot.</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=034464608-17112003><FONT face=Arial color=#0000ff
size=2>Regards</FONT></SPAN></DIV>
<P><B><FONT face="Comic Sans MS" size=2>Marianne van den
Berg<BR></FONT></B><FONT face="Comic Sans MS" size=2>Senior Support
Engineer<BR></FONT><B></B><B><FONT face=Roman size=2>LECHABILE Storage
Solutions (PTY) Ltd<BR></FONT></B><FONT face="Comic Sans MS" size=2>Tel:
+27 11 519 8134<BR>Mobile: +27 82 468 8107<BR>mailto:</FONT><U> <FONT
face="Times New Roman" color=#0000ff size=2><A
href="mailto:Mariannev AT LechabileSS.co DOT
za">Mariannev@LechabileSS</FONT><FONT
face="Times New Roman" color=#0000ff size=2>.co.za</A> </FONT></U></P>
<P><B><I><FONT face="Comic Sans MS" color=#800080 size=1>This e-mail and
attachments relating thereto, is intended for the above-mentioned
recipient. If you have received this e-mail in error, kindly notify the
sender and delete it immediately as it contains information relating to
the official business of Lechabile Storage Solutions (Pty) Limited, which
is confidential, legally privileged and proprietary to Lechabile Storage
Solutions (Pty) Limited. Lechabile Storage Solutions (Pty) Limited does
not own and endorse any other content. The views and opinions expressed
in
this e-mail are those of the sender unless clearly stated as being those
of Lechabile Storage Solutions (Pty) Limited.</FONT></I></B><I></I></P>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Robert Loh
[mailto:robert AT softsource.com DOT sg]<BR><B>Sent:</B> Monday,
November 17,
2003 10:04 AM<BR><B>To:</B>
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B>
[Veritas-bu] Cannot
assign requested address ?<BR><BR></FONT></DIV>
<P><FONT size=2>Hi folks,</FONT> </P>
<P><FONT size=2>NetBackup 3.4.2 with ATL P7000 16 x SDLT220 LVD drives
connected to Compaq SAN switch with a single backup server (media
server)</FONT></P>
<P><FONT size=2>Always receiving error below in my /var/adm/messages in
Solaris 8 </FONT></P>
<P><FONT size=2>Nov 16 17:29:18 sgs15i-001 tldd[21598]: TLD(2) [21598]
unable to connect to tldcd on sgs15i-001: Cannot assign requested
address (126)</FONT></P>
<P><FONT size=2>Nov 16 17:29:18 sgs15i-001 tldd[1322]: TLD(2) going to
DOWN state, status: Control daemon connect or protocol error</FONT>
<BR><FONT size=2>Nov 16 17:33:22 sgs15i-001 tldd[1322]: TLD(2) going to
UP state</FONT> <BR><FONT size=2>Nov 16 18:15:53 sgs15i-001 tldd[9349]:
TLD(2) [9349] unable to connect to tldcd on sgs15i-001: Cannot assign
requested address (126)</FONT></P>
<P><FONT size=2>Nov 16 18:15:53 sgs15i-001 tldd[1322]: TLD(2) going to
DOWN state, status: Control daemon connect or protocol error</FONT>
<BR><FONT size=2>Nov 16 18:18:22 sgs15i-001 tldd[1322]: TLD(2) going to
UP state</FONT> </P>
<P><FONT size=2>NetBackup error or tape library error !</FONT>
<BR><FONT
size=2>Appreciate for helping.</FONT> <BR><FONT
size=2>Thanks.Robert</FONT> </P></BLOCKQUOTE></SPAN>
<P><FONT face=Arial color=#0000ff
size=2></FONT></P></BLOCKQUOTE></BLOCKQUOTE></SPAN>
<P></P></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C3AE3E.98DACD6C--
|
