免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
12下一页
最近访问板块 发新帖
查看: 3457 | 回复: 13
打印 上一主题 下一主题

T3磁盘阵列如何查看日志? [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2005-06-03 10:28 |只看该作者 |倒序浏览
前两天4800主机突然报错找不到T3上的资源了,sybase数据库也无法正常运行了,这时注意到T3控制器上最右边有个叫online的灯变成黄色(不闪烁)了;
把主机和T3重启后,问题就解决了,不知道为什么???
想查看T3磁盘阵列的日志,不知怎么做,具体什么命令?

注:以前没有在工作站上建立过日志主机!

论坛徽章:
0
2 [报告]
发表于 2005-06-03 10:36 |只看该作者

T3磁盘阵列如何查看日志?

这个情况不好说,有可能是T3的电池不行了,T3的日志要用串口到T3上看,其实从/var/adm/messages里也应该可以看见信息

论坛徽章:
0
3 [报告]
发表于 2005-06-03 10:47 |只看该作者

T3磁盘阵列如何查看日志?

电池应该没问题,刚刚换过的!
/var/adm/messages这个文件怎么看呢,vi 、more、cat?
对了下面是一些信息:请高手帮忙看看!
t3b0:/:<1>;fru stat
CTLR    STATUS   STATE       ROLE        PARTNER    TEMP
------  -------  ----------  ----------  -------    ----
u1ctr   ready    enabled     master      u2ctr      37.0
u2ctr   ready    enabled     alt master  u1ctr      36.0

DISK    STATUS   STATE       ROLE        PORT1      PORT2      TEMP  VOLUME
------  -------  ----------  ----------  ---------  ---------  ----  ------
u1d1    ready    enabled     data disk   ready      ready      36    vol1
u1d2    ready    enabled     data disk   ready      ready      37    vol1
u1d3    ready    enabled     data disk   ready      ready      35    vol1
u1d4    ready    enabled     data disk   ready      ready      36    vol1
u1d5    ready    enabled     data disk   ready      ready      35    vol1
u1d6    ready    enabled     data disk   ready      ready      34    vol1
u1d7    ready    enabled     data disk   ready      ready      35    vol1
u1d8    ready    enabled     data disk   ready      ready      34    vol1
u1d9    ready    enabled     standby     ready      ready      34    vol1
u2d1    ready    enabled     data disk   ready      unknown    36    vol2
u2d2    ready    enabled     data disk   ready      unknown    35    vol2
u2d3    ready    enabled     data disk   ready      unknown    35    vol2
u2d4    ready    enabled     data disk   ready      unknown    35    vol2
u2d5    ready    enabled     data disk   ready      unknown    35    vol2
u2d6    ready    enabled     data disk   ready      unknown    35    vol2
u2d7    ready    enabled     data disk   ready      unknown    35    vol2
u2d8    ready    enabled     data disk   ready      unknown    35    vol2
u2d9    ready    enabled     standby     ready      unknown    34    vol2

LOOP    STATUS   STATE       MODE        CABLE1     CABLE2     TEMP
------  -------  ----------  -------     ---------  ---------  ----
u2l1    ready    enabled     master      installed  installed  27.0
u2l2    offline
u1l1    ready    enabled     master      -          installed  33.5
u1l2    ready    enabled     slave       -          installed  34.5

POWER   STATUS   STATE       SOURCE  OUTPUT  BATTERY  TEMP    FAN1    FAN2
------  -------  ---------   ------  ------  -------  ------  ------  ------
u1pcu1  ready    enabled     line    normal  normal   normal  normal  normal
u1pcu2  ready    enabled     line    normal  normal   normal  normal  normal
u2pcu1  ready    enabled     line    normal  normal   normal  normal  normal
u2pcu2  ready    enabled     line    normal  normal   normal  normal  normal
t3b0:/:<3>;fru list
ID      TYPE               VENDOR       MODEL        REVISION       SERIAL
------  -----------------  -----------  -----------  -------------  --------
u1ctr   controller card    0301         501-5710-02( 0200/020103    116301
u2ctr   controller card    0301         501-5710-02( 0200/020103    115270
u1d1    disk drive         SEAGATE      ST336605FSUN A538           3FP1RXCY
u1d2    disk drive         SEAGATE      ST336605FSUN A538           3FP1S29P
u1d3    disk drive         SEAGATE      ST336605FSUN A538           3FP1S3BZ
u1d4    disk drive         SEAGATE      ST336605FSUN A538           3FP1S480
u1d5    disk drive         SEAGATE      ST336605FSUN A538           3FP1RG6C
u1d6    disk drive         SEAGATE      ST336605FSUN A538           3FP1S3X8
u1d7    disk drive         SEAGATE      ST336605FSUN A538           3FP1RYC0
u1d8    disk drive         SEAGATE      ST336605FSUN A538           3FP1S42N
u1d9    disk drive         SEAGATE      ST336605FSUN A538           3FP1S3VQ
u2d1    disk drive         SEAGATE      ST336605FSUN A538           3FP1MX0V
u2d2    disk drive         SEAGATE      ST336605FSUN A538           3FP1MXWR
u2d3    disk drive         SEAGATE      ST336605FSUN A538           3FP1MWWF
u2d4    disk drive         SEAGATE      ST336605FSUN A538           3FP1MWP5
u2d5    disk drive         SEAGATE      ST336605FSUN A538           3FP1MYW6
u2d6    disk drive         SEAGATE      ST336605FSUN A538           3FP1MMVE
u2d7    disk drive         SEAGATE      ST336605FSUN A538           3FP1MZ4E
u2d8    disk drive         SEAGATE      ST336605FSUN A538           3FP1MXMK
u2d9    disk drive         SEAGATE      ST336605FSUN A538           3FP1MYKV
u1l1    loop card          SLR-MI       375-0085-01-  5.02 Flash    099056
u1l2    loop card          SLR-MI       375-0085-01-  5.02 Flash    098310
u2l1    loop card          SLR-MI       375-0085-01-  5.02 Flash    094932
u2l2    loop card
u1pcu1  power/cooling unit TECTROL-CAN  300-1454-01( 0000           094309
u1pcu2  power/cooling unit TECTROL-CAN  300-1454-01( 0000           094235
u2pcu1  power/cooling unit TECTROL-CAN  300-1454-01( 0000           094974
u2pcu2  power/cooling unit TECTROL-CAN  300-1454-01( 0000           094920
u1mpn   mid plane          SLR-MI       501-5709-05- 0050           057083
u2mpn   mid plane          SLR-MI       370-3990-02- 0000           051912
3b0:/:<5>;vol stat

vol1          u1d1   u1d2   u1d3   u1d4   u1d5   u1d6   u1d7   u1d8   u1d9
mounted        0      0      0      0      0      0      0      0      0
vol2          u2d1   u2d2   u2d3   u2d4   u2d5   u2d6   u2d7   u2d8   u2d9
mounted        0      0      0      0      0      0      0      0      0
t3b0:/:<6>;vol list

volume         capacity     raid  data      standby
vol1           236.059 GB   5     u1d1-8    u1d9
vol2           236.059 GB   5     u2d1-8    u2d9
t3b0:/:<7>;sys list
blocksize          : 16k
cache              : writebehind
mirror             : off
mp_support         : mpxio
naca               : off
rd_ahead           : off
recon_rate         : med
sys memsize        : 128 MBytes
cache memsize      : 1024 MBytes
enable_volslice    : on
fc_topology        : auto

论坛徽章:
0
4 [报告]
发表于 2005-06-03 10:53 |只看该作者

T3磁盘阵列如何查看日志?

我知道了,应该是cat /var/adm/messages
:/: help
arp  cat  cd  cmp  cp  date  echo  head help  ls  mkdir  mv  ping pwd  rm  rmdir  tail  touch boot disable disk enable fru id logger lpc more passwd port proc reset set shutdown sync sys tzset ver vol ep refresh route ofdg lun hwwn

论坛徽章:
0
5 [报告]
发表于 2005-06-03 11:24 |只看该作者

T3磁盘阵列如何查看日志?

telnet to T3;
more syslog.

论坛徽章:
0
6 [报告]
发表于 2005-06-03 11:27 |只看该作者

T3磁盘阵列如何查看日志?

u2l2    offline  有问题,

线或卡

论坛徽章:
0
7 [报告]
发表于 2005-06-03 12:05 |只看该作者

T3磁盘阵列如何查看日志?

u2l2    offline
我看到了,应该是两个T3内部连接线或卡有问题吧!
那具体是什么问题,怎么看呢?

论坛徽章:
0
8 [报告]
发表于 2005-06-03 17:27 |只看该作者

T3磁盘阵列如何查看日志?

more syslog

论坛徽章:
0
9 [报告]
发表于 2005-06-08 14:58 |只看该作者

T3磁盘阵列如何查看日志?

May 29 16:04:46 BATD[2]: N: Battery Refreshing cycle starts from this point.
May 29 16:04:50 LPCT[2]: N: u1pcu1: Refreshing battery
May 29 16:04:53 LPCT[2]: N: u2pcu1: Refreshing battery
May 29 16:10:48 BATD[2]: N: u1pcu1: battery passed health check.
May 29 16:10:54 BATD[2]: N: u2pcu1: battery passed health check.
May 30 03:49:14 LPCT[2]: N: u1pcu2: Refreshing battery
May 30 03:49:17 LPCT[2]: N: u2pcu2: Refreshing battery
May 30 03:55:12 BATD[2]: N: u1pcu2: battery passed health check.
May 30 03:55:18 BATD[2]: N: u2pcu2: battery passed health check.
May 30 09:56:54 ROOT[2]: N: u2ctr Initializing loop 1 ISP2200 ... firmware status = 3
May 30 09:56:54 ROOT[2]: N: u2ctr Detected 19 FC-AL ports on loop 1
May 30 09:56:54 ROOT[2]: N: u2ctr loop 1 TARGET_ID = 0x1 (ALPA = 0xe
May 30 09:57:18 ROOT[2]: N: u2ctr Initializing loop 2 ISP2200 ... firmware status = 3
May 30 09:57:18 ROOT[2]: N: u2ctr Detected 10 FC-AL ports on loop 2
May 30 09:57:18 ROOT[2]: N: u2ctr loop 2 TARGET_ID = 0x1 (ALPA = 0xe
May 30 09:57:24 LPCT[2]: N: u2pcu2: Battery not OK
May 30 09:57:24 LPCT[2]: N: u1pcu2: Battery not OK
May 30 09:57:35 ROOT[2]: N: 19 fcal ports were detected on l1
May 30 09:57:35 ROOT[2]: N: 10 fcal ports were detected on l2
May 30 09:57:37 ROOT[2]: N: u2ctr found 18 disks in system
May 30 09:57:57 ROOT[2]: W: u1ctr: Disabled
May 30 09:58:08 ROOT[2]: N: T3B Release 2.01.03 2002/11/14 20:16:35 (192.168.0.40)
May 30 09:58:10 ROOT[2]: N: u2ctr System has 1 active controller(s)
May 30 09:58:10 snmp[2]: N: snmpd cold start
May 30 09:58:22 ROOT[2]: N: u2ctr Initializing host port u2p1 ISP2200 ... firmware status = 3
May 30 09:58:23 ROOT[2]: N: u2ctr Host port u2p1 Current Topology = Fabric Point to Point, Port ID = 0x100
May 30 09:58:24 ISR1[2]: N: u2ctr ISP2200[2] PDB resync done (host id 2, wwn 210100e08b28630c)
May 30 09:58:24 FCC0[2]: N: u2ctr PDB Changed on port 3 (id 2)
May 30 09:58:24 FCC0[2]: N: u2ctr : LMK:  not registered WWN = 21 1 0 e0 8b 28 63 c, id = 2.
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 0 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 1 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 2 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 3 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 4 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 5 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 6 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 7 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 8 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 9 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 0 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 1 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 2 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 3 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 4 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 5 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 6 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 7 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 8 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 9 is accessible
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 2 1 0 TT 20 TID AB30 OP 0) Target in Unit Attention
May 30 09:58:24 FCC0[2]: N: u2ctr unsupported opcode 4d lun 4
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 2 1 0 TT 20 TID AB84 OP 4D) Invalid command opcode
May 30 09:58:24 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 4.
May 30 09:58:24 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 4.
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 2 1 0 TT 20 TID AC44 OP 0) Target in Unit Attention
May 30 09:58:24 FCC0[2]: N: u2ctr unsupported opcode 4d lun 3
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 2 1 0 TT 20 TID AC74 OP 4D) Invalid command opcode
May 30 09:58:24 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 3.
May 30 09:58:24 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 3.
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 2 1 0 TT 20 TID ACBC OP 0) Target in Unit Attention
May 30 09:58:24 FCC0[2]: N: u2ctr unsupported opcode 4d lun 2
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 2 1 0 TT 20 TID ACEC OP 4D) Invalid command opcode
May 30 09:58:24 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 2.
May 30 09:58:24 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 2.
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 2 1 0 TT 20 TID AD34 OP 0) Target in Unit Attention
May 30 09:58:24 FCC0[2]: N: u2ctr unsupported opcode 4d lun 1
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 2 1 0 TT 20 TID AD64 OP 4D) Invalid command opcode
May 30 09:58:24 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 1.
May 30 09:58:24 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 1.
May 30 09:58:24 ISR1[2]: N: u2ctr ISP2200[2] PDB resync done (host id 1, wwn 210000e08b086014)
May 30 09:58:24 FCC0[2]: N: u2ctr PDB Changed on port 3 (id 1)
May 30 09:58:24 FCC0[2]: N: u2ctr : LMK:  not registered WWN = 21 0 0 e0 8b 8 60 14, id = 1.
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 0 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 1 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 2 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 3 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 4 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 5 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 6 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 7 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 8 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 9 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 0 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 1 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 2 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 3 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 4 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 5 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 6 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 7 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 8 is accessible
May 30 09:58:24 SNXT[2]: N: u2ctr : DoReportLun elun 9 is accessible
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID AEFC OP 0) Target in Unit Attention
May 30 09:58:24 FCC0[2]: N: u2ctr unsupported opcode 4d lun 9
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID AF68 OP 4D) Invalid command opcode
May 30 09:58:24 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 9.
May 30 09:58:24 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 9.
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID B10C OP 0) Target in Unit Attention
May 30 09:58:24 FCC0[2]: N: u2ctr unsupported opcode 4d lun 8
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID B13C OP 4D) Invalid command opcode
May 30 09:58:24 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 8.
May 30 09:58:24 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 8.
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID B184 OP 0) Target in Unit Attention
May 30 09:58:24 FCC0[2]: N: u2ctr unsupported opcode 4d lun 7
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID B1B4 OP 4D) Invalid command opcode
May 30 09:58:24 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 7.
May 30 09:58:24 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 7.
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID B1FC OP 0) Target in Unit Attention
May 30 09:58:24 FCC0[2]: N: u2ctr unsupported opcode 4d lun 6
May 30 09:58:24 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID B22C OP 4D) Invalid command opcode
May 30 09:58:25 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 6.
May 30 09:58:25 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 6.
May 30 09:58:25 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID B274 OP 0) Target in Unit Attention
May 30 09:58:25 FCC0[2]: N: u2ctr unsupported opcode 4d lun 5
May 30 09:58:25 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID B2A4 OP 4D) Invalid command opcode
May 30 09:58:25 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 5.
May 30 09:58:25 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 5.
May 30 09:58:25 ISR1[2]: N: u2ctr ISP2200[2] Received Link initialization in Point-to-Point mode
May 30 09:58:25 ISR1[2]: N: u2ctr ISP2200[2] PDB Invalidated (host id 1, wwn 210000e08b086014)
May 30 09:58:25 ISR1[2]: N: u2ctr ISP2200[2] PDB Invalidated (host id 2, wwn 210100e08b28630c)
May 30 09:58:25 ISR1[2]: N: u2ctr ISP2200[2] PDB resync done (host id 1, wwn 210000e08b086014)
May 30 09:58:25 FCC0[2]: N: u2ctr PDB Changed on port 3 (id 1)
May 30 09:58:25 FCC0[2]: N: u2ctr : LMK:  not registered WWN = 21 0 0 e0 8b 8 60 14, id = 1.
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 0 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 1 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 2 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 3 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 4 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 5 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 6 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 7 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 8 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 9 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 0 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 1 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 2 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 3 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 4 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 5 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 6 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 7 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 8 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 9 is accessible
May 30 09:58:25 ISR1[2]: N: u2ctr ISP2200[2] PDB resync done (host id 2, wwn 210100e08b28630c)
May 30 09:58:25 FCC0[2]: N: u2ctr PDB Changed on port 3 (id 2)
May 30 09:58:25 FCC0[2]: N: u2ctr : LMK:  not registered WWN = 21 1 0 e0 8b 28 63 c, id = 2.
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 0 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 1 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 2 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 3 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 4 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 5 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 6 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 7 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 8 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 9 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 0 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 1 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 2 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 3 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 4 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 5 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 6 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 7 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 8 is accessible
May 30 09:58:25 SNXT[2]: N: u2ctr : DoReportLun elun 9 is accessible
May 30 09:58:25 FCC0[2]: N: u2ctr (ITL 2 1 0 TT 20 TID B5C8 OP 0) Target in Unit Attention
May 30 09:58:25 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID B5D4 OP 0) Target in Unit Attention
May 30 09:58:25 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID B5E0 OP 0) Target in Unit Attention
May 30 09:58:25 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID B5EC OP 0) Target in Unit Attention
May 30 09:58:25 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID B5F8 OP 0) Target in Unit Attention
May 30 09:58:25 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID B604 OP 0) Target in Unit Attention
May 30 10:21:49 FCC0[2]: N: u2ctr (ITL 2 1 1 TT 20 TID A968 OP 2 Target in Unit Attention
May 30 11:01:42 FCC0[2]: N: u2ctr (ITL 2 1 1 TT 20 TID B280 OP 2 Target in Unit Attention
May 30 11:01:48 FCC0[2]: N: u2ctr (ITL 2 1 1 TT 20 TID B328 OP 2 Target in Unit Attention
May 30 12:48:01 FCC0[2]: N: u2ctr (ITL 2 1 1 TT 20 TID AF20 OP 2A) Target in Unit Attention
May 30 12:48:06 FCC0[2]: N: u2ctr (ITL 2 1 1 TT 20 TID AFB0 OP 2A) Target in Unit Attention
May 30 12:51:07 ISR1[2]: N: u2ctr ISP2200[2] PDB Invalidated (host id 1, wwn 210000e08b086014)
May 30 12:51:07 ISR1[2]: N: u2ctr ISP2200[2] PDB Invalidated (host id 2, wwn 210100e08b28630c)
May 30 12:51:07 ISR1[2]: W: u2ctr ISP2200[2] Received LOOP DOWN async event
May 30 12:51:09 LPCT[2]: W: u2pcu1: On battery, serial no = 094974
May 30 12:51:09 LPCT[2]: W: u2pcu2: On battery, serial no = 094920
May 30 12:51:09 LPCT[2]: W: u1pcu1: On battery, serial no = 094309
May 30 12:51:09 LPCT[2]: W: u1pcu2: On battery, serial no = 094235
May 30 12:59:33 ROOT[1]: N: u1ctr Initializing loop 1 ISP2200 ... firmware status = 3
May 30 12:59:33 ROOT[1]: N: u1ctr Detected 19 FC-AL ports on loop 1
May 30 12:59:33 ROOT[1]: N: u1ctr loop 1 TARGET_ID = 0x0 (ALPA = 0xef)
May 30 13:00:01 ROOT[1]: N: u1ctr Initializing loop 2 ISP2200 ... firmware status = 3
May 30 13:00:01 ROOT[1]: N: u1ctr Detected 10 FC-AL ports on loop 2
May 30 13:00:01 ROOT[1]: N: u1ctr loop 2 TARGET_ID = 0x0 (ALPA = 0xef)
May 30 13:00:03 LPCT[1]: N: u1pcu1: Battery not OK
May 30 13:00:03 LPCT[1]: N: u1pcu2: Battery not OK
May 30 13:00:03 LPCT[1]: N: u2pcu1: Battery not OK
May 30 13:00:03 LPCT[1]: N: u2pcu2: Battery not OK
May 30 13:00:03 LPCT[1]: N: u2ctr: Select ID changed to 2
May 30 13:00:18 ROOT[1]: N: 19 fcal ports were detected on l1
May 30 13:00:18 ROOT[1]: N: 10 fcal ports were detected on l2
May 30 13:00:46 ROOT[1]: N: u1ctr found 18 disks in system
May 30 13:01:09 ROOT[1]: N: T3B Release 2.01.03 2002/11/14 20:16:35 (192.168.0.40)
May 30 13:01:11 ROOT[1]: N: u1ctr Waiting for 1 slave controller(s) to come up...
May 30 13:01:11 ROOT[1]: N: u1ctr u1: Configuring local data
May 30 13:01:20 ROOT[1]: N: u1ctr u2: Initializing drives
May 30 13:01:24 ISR1[1]: N: u1ctr ISP2200[0] Received LIP(f8,cb) async event
May 30 13:01:26 SVDT[1]: N: 20 fcal ports were detected on l1
May 30 13:02:56 ROOT[1]: N: u1ctr u2: Configuring local data
May 30 13:02:57 ROOT[1]: N: u1ctr u2: Waiting for configuration data from master
May 30 13:03:44 ROOT[1]: N: u1ctr System has 2 active controller(s)
May 30 13:03:44 snmp[1]: N: snmpd cold start
May 30 13:01:24 ROOT[2]: N: u2ctr Initializing loop 1 ISP2200 ... firmware status = 3
May 30 13:01:34 ROOT[2]: N: u2ctr Detected 20 FC-AL ports on loop 1
May 30 13:01:34 ROOT[2]: N: u2ctr loop 1 TARGET_ID = 0x1 (ALPA = 0xe
May 30 13:01:58 ROOT[2]: N: u2ctr Initializing loop 2 ISP2200 ... firmware status = 3
May 30 13:02:08 ROOT[2]: N: u2ctr Detected 10 FC-AL ports on loop 2
May 30 13:02:08 ROOT[2]: N: u2ctr loop 2 TARGET_ID = 0x1 (ALPA = 0xe
May 30 13:02:25 ROOT[2]: N: 20 fcal ports were detected on l1
May 30 13:02:25 ROOT[2]: N: 10 fcal ports were detected on l2
May 30 13:02:53 ROOT[2]: N: u2ctr found 18 disks in system
May 30 13:02:54 ROOT[2]: N: T3B Release 2.01.03 2002/11/14 20:16:35 (192.168.0.40)
May 30 13:03:55 ROOT[2]: N: u2ctr Initializing host port u2p1 ISP2200 ... firmware status = 3
May 30 13:03:57 ROOT[1]: N: u1ctr Initializing host port u1p1 ISP2200 ... firmware status = 3
May 30 13:03:57 ROOT[1]: N: u1ctr Host port u1p1 Current Topology = Fabric Point to Point, Port ID = 0x100
May 30 13:03:55 ROOT[2]: N: u2ctr Host port u2p1 Current Topology = Fabric Point to Point, Port ID = 0x100
May 30 13:03:58 SMON[2]: N: u2ctr loop 2 path failed event received
May 30 13:04:00 ISR1[1]: N: u1ctr ISP2200[2] Received Link initialization in Point-to-Point mode
May 30 13:03:58 ISR1[2]: N: u2ctr ISP2200[2] Received Link initialization in Point-to-Point mode
May 30 13:16:01 ISR1[2]: N: u2ctr ISP2200[2] PDB resync done (host id 1, wwn 210000e08b086014)
May 30 13:16:01 FCC0[2]: N: u2ctr PDB Changed on port 3 (id 1)
May 30 13:16:01 FCC0[2]: N: u2ctr : LMK:  not registered WWN = 21 0 0 e0 8b 8 60 14, id = 1.
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 0 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 1 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 2 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 3 is accessible
May 30 13:16:08 ISR1[1]: N: u1ctr ISP2200[2] PDB resync done (host id 1, wwn 210000e08b08a70a)
May 30 13:16:08 FCC0[1]: N: u1ctr PDB Changed on port 0 (id 1)
May 30 13:16:08 FCC0[1]: N: u1ctr : LMK:  not registered WWN = 21 0 0 e0 8b 8 a7 a, id = 1.
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 0 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 1 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 2 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 3 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 4 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 5 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 6 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 7 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 8 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 9 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 0 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 1 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 2 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 3 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 4 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 5 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 6 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 7 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 8 is accessible
May 30 13:16:08 SNXT[1]: N: u1ctr : DoReportLun elun 9 is accessible
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 1 TT 20 TID ABFC OP 0) Target in Unit Attention
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 1 TT 20 TID AC20 OP 25) Need LUN ownership
May 30 13:16:09 FCC0[1]: N: u1ctr unsupported opcode 4d lun 8
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 1 TT 20 TID AC2C OP 4D) Invalid command opcode
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 8.
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 8.
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 1 TT 20 TID AC74 OP 0) Target in Unit Attention
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 1 TT 20 TID AC98 OP 25) Need LUN ownership
May 30 13:16:09 FCC0[1]: N: u1ctr unsupported opcode 4d lun 7
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 1 TT 20 TID ACA4 OP 4D) Invalid command opcode
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 7.
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 7.
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 1 TT 20 TID ACEC OP 0) Target in Unit Attention
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 1 TT 20 TID AD10 OP 25) Need LUN ownership
May 30 13:16:09 FCC0[1]: N: u1ctr unsupported opcode 4d lun 6
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 1 TT 20 TID AD1C OP 4D) Invalid command opcode
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 6.
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 6.
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 1 TT 20 TID AD64 OP 0) Target in Unit Attention
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 1 TT 20 TID AD88 OP 25) Need LUN ownership
May 30 13:16:09 FCC0[1]: N: u1ctr unsupported opcode 4d lun 5
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 1 TT 20 TID AD94 OP 4D) Invalid command opcode
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 5.
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 5.
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 0 TT 20 TID ADDC OP 0) Target in Unit Attention
May 30 13:16:09 FCC0[1]: N: u1ctr unsupported opcode 4d lun 4
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 0 TT 20 TID AE0C OP 4D) Invalid command opcode
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 4.
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 4.
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 0 TT 20 TID AE54 OP 0) Target in Unit Attention
May 30 13:16:09 FCC0[1]: N: u1ctr unsupported opcode 4d lun 3
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 0 TT 20 TID AE84 OP 4D) Invalid command opcode
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 3.
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 3.
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 0 TT 20 TID AECC OP 0) Target in Unit Attention
May 30 13:16:09 FCC0[1]: N: u1ctr unsupported opcode 4d lun 2
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 0 TT 20 TID AEFC OP 4D) Invalid command opcode
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 2.
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 2.
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 0 TT 20 TID AF44 OP 0) Target in Unit Attention
May 30 13:16:09 FCC0[1]: N: u1ctr unsupported opcode 4d lun 1
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 0 TT 20 TID AF74 OP 4D) Invalid command opcode
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 1.
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 1.
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 0 TT 20 TID AFBC OP 0) Target in Unit Attention
May 30 13:16:09 FCC0[1]: N: u1ctr unsupported opcode 4d lun 0
May 30 13:16:09 FCC0[1]: N: u1ctr (ITL 1 0 0 TT 20 TID AFEC OP 4D) Invalid command opcode
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 0.
May 30 13:16:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 0.
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 4 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 5 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 6 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 7 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 8 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 9 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 0 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 1 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 2 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 3 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 4 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 5 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 6 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 7 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 8 is accessible
May 30 13:16:01 SNXT[2]: N: u2ctr : DoReportLun elun 9 is accessible
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID ABFC OP 0) Target in Unit Attention
May 30 13:16:02 FCC0[2]: N: u2ctr unsupported opcode 4d lun 8
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID AC2C OP 4D) Invalid command opcode
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 8.
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 8.
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID AC74 OP 0) Target in Unit Attention
May 30 13:16:02 FCC0[2]: N: u2ctr unsupported opcode 4d lun 7
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID ACA4 OP 4D) Invalid command opcode
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 7.
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 7.
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID ACEC OP 0) Target in Unit Attention
May 30 13:16:02 FCC0[2]: N: u2ctr unsupported opcode 4d lun 6
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID AD1C OP 4D) Invalid command opcode
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 6.
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 6.
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID AD64 OP 0) Target in Unit Attention
May 30 13:16:02 FCC0[2]: N: u2ctr unsupported opcode 4d lun 5
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID AD94 OP 4D) Invalid command opcode
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 5.
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 5.
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID ADDC OP 0) Target in Unit Attention
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID AE00 OP 25) Need LUN ownership
May 30 13:16:02 FCC0[2]: N: u2ctr unsupported opcode 4d lun 4
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID AE0C OP 4D) Invalid command opcode
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 4.
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 4.
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID AE54 OP 0) Target in Unit Attention
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID AE78 OP 25) Need LUN ownership
May 30 13:16:02 FCC0[2]: N: u2ctr unsupported opcode 4d lun 3
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID AE84 OP 4D) Invalid command opcode
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 3.
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 3.
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID AECC OP 0) Target in Unit Attention
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID AEF0 OP 25) Need LUN ownership
May 30 13:16:02 FCC0[2]: N: u2ctr unsupported opcode 4d lun 2
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID AEFC OP 4D) Invalid command opcode
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 2.
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 2.
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID AF44 OP 0) Target in Unit Attention
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID AF68 OP 25) Need LUN ownership
May 30 13:16:02 FCC0[2]: N: u2ctr unsupported opcode 4d lun 1
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID AF74 OP 4D) Invalid command opcode
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 1.
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 1.
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID AFBC OP 0) Target in Unit Attention
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID AFE0 OP 25) Need LUN ownership
May 30 13:16:02 FCC0[2]: N: u2ctr unsupported opcode 4d lun 0
May 30 13:16:02 FCC0[2]: N: u2ctr (ITL 1 1 0 TT 20 TID AFEC OP 4D) Invalid command opcode
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 0.
May 30 13:16:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 0.
May 30 13:17:04 ISR1[1]: N: u1ctr ISP2200[2] PDB resync done (host id 2, wwn 210100e08b28899a)
May 30 13:17:04 FCC0[1]: N: u1ctr PDB Changed on port 0 (id 2)
May 30 13:17:04 FCC0[1]: N: u1ctr : LMK:  not registered WWN = 21 1 0 e0 8b 28 89 9a, id = 2.
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 0 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 1 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 2 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 3 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 4 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 5 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 6 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 7 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 8 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 9 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 0 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 1 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 2 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 3 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 4 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 5 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 6 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 7 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 8 is accessible
May 30 13:17:04 SNXT[1]: N: u1ctr : DoReportLun elun 9 is accessible
May 30 13:17:02 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID B034 OP 0) Target in Unit Attention
May 30 13:17:02 FCC0[2]: N: u2ctr unsupported opcode 4d lun 9
May 30 13:17:02 FCC0[2]: N: u2ctr (ITL 1 1 1 TT 20 TID B064 OP 4D) Invalid command opcode
May 30 13:17:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 9.
May 30 13:17:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 9.
May 30 13:17:09 FCC0[1]: N: u1ctr (ITL 1 0 1 TT 20 TID B340 OP 0) Target in Unit Attention
May 30 13:17:09 FCC0[1]: N: u1ctr (ITL 1 0 1 TT 20 TID B364 OP 25) Need LUN ownership
May 30 13:17:09 FCC0[1]: N: u1ctr unsupported opcode 4d lun 9
May 30 13:17:09 FCC0[1]: N: u1ctr (ITL 1 0 1 TT 20 TID B370 OP 4D) Invalid command opcode
May 30 13:17:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 0 for lun 9.
May 30 13:17:09 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 8 from port 1 for lun 9.
May 30 13:17:09 ISR1[2]: N: u2ctr ISP2200[2] PDB resync done (host id 2, wwn 210100e08b28630c)
May 30 13:17:11 FCC0[1]: N: u1ctr (ITL 2 0 0 TT 20 TID B3A0 OP 0) Target in Unit Attention
May 30 13:17:09 FCC0[2]: N: u2ctr PDB Changed on port 3 (id 2)
May 30 13:17:09 FCC0[2]: N: u2ctr : LMK:  not registered WWN = 21 1 0 e0 8b 28 63 c, id = 2.
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 0 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 1 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 2 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 3 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 4 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 5 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 6 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 7 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 8 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 9 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 0 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 1 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 2 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 3 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 4 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 5 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 6 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 7 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 8 is accessible
May 30 13:17:09 SNXT[2]: N: u2ctr : DoReportLun elun 9 is accessible
May 30 13:17:32 CLTT[1]: N: Initiator 2, port 16 releases lun 0
May 30 13:17:39 FCC0[2]: N: u2ctr (ITL 2 1 1 TT 20 TID B3A0 OP 0) Target in Unit Attention
May 30 13:17:40 FCC0[2]: N: u2ctr (ITL 2 1 1 TT 20 TID B4C0 OP 0) Target in Unit Attention
May 30 13:17:40 FCC0[2]: N: u2ctr (ITL 2 1 1 TT 20 TID B5E0 OP 0) Target in Unit Attention
May 30 13:17:40 FCC0[2]: N: u2ctr (ITL 2 1 1 TT 20 TID B700 OP 0) Target in Unit Attention
May 30 13:17:41 FCC0[2]: N: u2ctr (ITL 2 1 1 TT 20 TID B820 OP 0) Target in Unit Attention
May 30 13:17:51 CLTT[1]: N: Initiator 1, port 16 releases lun 4
May 30 13:17:52 CLTT[1]: N: Initiator 1, port 16 releases lun 2
May 30 13:17:52 CLTT[1]: N: Initiator 1, port 16 releases lun 3
May 30 13:17:52 CLTT[1]: N: Initiator 1, port 16 releases lun 1
May 30 13:17:53 FCC0[1]: N: u1ctr (ITL 2 0 0 TT 20 TID A998 OP 57) Target in Unit Attention
May 30 13:17:53 FCC0[1]: N: u1ctr (ITL 2 0 0 TT 20 TID A9A4 OP 57) Target in Unit Attention
May 30 13:17:53 FCC0[1]: N: u1ctr (ITL 2 0 0 TT 20 TID A9BC OP 57) Target in Unit Attention
May 30 13:17:53 FCC0[1]: N: u1ctr (ITL 2 0 0 TT 20 TID A9E0 OP 57) Target in Unit Attention
May 30 13:17:54 CLTT[1]: N: Initiator 2, port 16 releases lun 2
May 30 13:17:54 CLTT[1]: N: Initiator 2, port 16 releases lun 3
May 30 13:17:52 CLTT[2]: N: Initiator 2, port 16 releases lun 5
May 30 13:17:53 CLTT[2]: N: Initiator 2, port 16 releases lun 6
May 30 13:17:55 CLTT[1]: N: Initiator 2, port 16 releases lun 4
May 30 13:17:55 CLTT[1]: N: Initiator 2, port 16 releases lun 1
May 30 13:17:55 CLTT[2]: N: Initiator 2, port 16 releases lun 7
May 30 13:17:58 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 1.
May 30 13:17:58 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 1.
May 30 13:17:58 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 2.
May 30 13:17:58 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 2.
May 30 13:17:58 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 3.
May 30 13:17:58 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 3.
May 30 13:17:58 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 4.
May 30 13:17:58 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 4.
May 30 13:17:56 CLTT[2]: N: Initiator 2, port 16 releases lun 8
May 30 13:17:57 CLTT[2]: N: Initiator 2, port 16 releases lun 9
May 30 13:17:58 CLTT[2]: N: Initiator 1, port 16 releases lun 5
May 30 13:17:58 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 5.
May 30 13:17:58 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 5.
May 30 13:17:59 CLTT[2]: N: Initiator 1, port 16 releases lun 6
May 30 13:17:59 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 6.
May 30 13:17:59 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 6.
May 30 13:18:04 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 1.
May 30 13:18:04 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 1.
May 30 13:18:04 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 2.
May 30 13:18:04 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 2.
May 30 13:18:04 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 3.
May 30 13:18:04 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 3.
May 30 13:18:04 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 4.
May 30 13:18:04 SNXT[1]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 4.
May 30 13:18:00 CLTT[2]: N: Initiator 1, port 16 releases lun 7
May 30 13:18:00 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 7.
May 30 13:18:00 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 7.
May 30 13:18:02 CLTT[2]: N: Initiator 1, port 16 releases lun 8
May 30 13:18:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 8.
May 30 13:18:02 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 8.
May 30 13:18:03 CLTT[2]: N: Initiator 1, port 16 releases lun 9
May 30 13:18:03 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 9.
May 30 13:18:03 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 9.
May 30 13:18:03 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 9.
May 30 13:18:03 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 9.
May 30 13:18:03 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 6.
May 30 13:18:03 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 6.
May 30 13:18:03 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 7.
May 30 13:18:03 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 7.
May 30 13:18:03 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 5.
May 30 13:18:03 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 5.
May 30 13:18:03 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 0 for lun 8.
May 30 13:18:03 SNXT[2]: N: PGR_IN: 0 keys will be returned in the data buffer size 128 from port 1 for lun 8.

论坛徽章:
0
10 [报告]
发表于 2005-06-08 15:08 |只看该作者

T3磁盘阵列如何查看日志?

上面是syslog的内容,高手请指点一二!
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP