I have a SunFire 280R connected to a single T3 array.
I got exactly one of these messages when the 280R
boots of the internal FCAL drive. When i boot the
machine of a root submirror on the T3 i get several
of these messages togeter like this
Aug 18 09:53:18 ISR1[1]: W: u1ctr ISP2100[2] Received LOOP DOWN async event^M
alternating with LOOP UP
messages
about 5 times.
You can get docs on line at
http://www.sun.com/products-n-solutions/hardware/docs/Network_Storage_Solutions /Workgroup/T3WG/index.html
there you can get the T3 admin guide.
> I have a SunFire 280R connected to a single T3 array.
> I got exactly one of these messages when the 280R
> boots of the internal FCAL drive. When i boot the
> machine of a root submirror on the T3 i get several
> of these messages togeter like this
>
> Aug 18 09:53:18 ISR1[1]: W: u1ctr ISP2100[2] Received
> LOOP DOWN async event^M
>
> alternating with LOOP UP
>
> messages
>
> about 5 times.
This sequence is indicative of a LIP (interruption of service) in the front-end host connected FC-AL
loop of the T3 ... as you have probably just rebooted the host, each connected FC-AL loop will note the
HBA restart and therefore the LIP will be initiated. The message from the T3 is a warning message
detailing its note of the LIP occurence.
The significant elements are:
Aug 18 09:53:18 #date and time (hence make sure that your clock is synced!)
ISR1 #reporting internal T3 task
[1]: #controller id on which task is running (ie. tray id 1, typically u1)
W: #warning message
u1ctr ISP2100[2] Received LOOP DOWN async event
# u1's controllers ISP2100, that is the QLogic FC controller chip, the [2] signifies on which loop -- the
T3 has three (0 and 1 are back-end loops, 2 is the front-end, host facing loop), received a LOOP DOWN
notification. From the host side you might be more familiar with the 'Loop Offline' message ...
The completion of the LIP process and the resumption of normal loop processing is signalled by the
subsequent LOOP UP (from Solaris 'Loop Online') messages ...
> You can get docs on line at
>
> http://www.sun.com/products-n-solutions/hardware/docs/N
> twork_Storage_Solutions/Workgroup/T3WG/index.html
>
> there you can get the T3 admin guide.
>
>
>
HTH
--
Craig Morgan
> This sequence is indicative of a LIP (interruption of
> service) in the front-end host connected FC-AL
> loop of the T3 ... as you have probably just rebooted
> the host, each connected FC-AL loop will note the
> HBA restart and therefore the LIP will be initiated.
> The message from the T3 is a warning message
> detailing its note of the LIP occurence.
>
> The significant elements are:
>
> Aug 18 09:53:18 #date and time (hence make sure that
> your clock is synced!)
> ISR1 #reporting internal T3 task
> [1]: #controller id on which task is running (ie. tray
> id 1, typically u1)
> W: #warning message
> u1ctr ISP2100[2] Received LOOP DOWN async event
> # u1's controllers ISP2100, that is the QLogic FC
> controller chip, the [2] signifies on which loop --
> the
> T3 has three (0 and 1 are back-end loops, 2 is the
> front-end, host facing loop), received a LOOP DOWN
> notification. From the host side you might be more
> familiar with the 'Loop Offline' message ...
>
> The completion of the LIP process and the resumption
> of normal loop processing is signalled by the
> subsequent LOOP UP (from Solaris 'Loop Online')
> messages ...
>
> > You can get docs on line at
> >
> >
> http://www.sun.com/products-n-solutions/hardware/docs/N
>
> > twork_Storage_Solutions/Workgroup/T3WG/index.html
> >
> > there you can get the T3 admin guide.
> >
> >
> >
>
> HTH
>
> --
> Craig Morgan
Thanks, that's cleared things up.
Alex Tarry