- Community Home
- >
- Storage
- >
- Legacy
- >
- Disk
- >
- BCC replacement on one SC10
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2003 07:12 AM
05-14-2003 07:12 AM
BCC replacement on one SC10
please can somebody advise how we can replace the BCC on the SC10 JBOD configuration in high addressing mode split bus mode .the problem is that the controller is shown NO_HW in the ioscan but the disk are claimed and the srever is functioning normaly .please find attched the ioscan file .and there is also a message in the syslog file you find it bellow : May 14 06:23:36 lib-04 vmunix: SCSI: Reset detected -- lbolt: -1769448484, bus: 4 May 14 06:23:36 lib-04 vmunix: lbp->state: 60 May 14 06:23:36 lib-04 vmunix: lbp->offset: ffffffff May 14 06:23:36 lib-04 vmunix: lbp->uPhysScript: fa7fa000 May 14 06:23:36 lib-04 vmunix: From most recent interrupt: May 14 06:23:36 lib-04 vmunix: ISTAT: 02, SIST0: 02, SIST1: 00, DSTAT: 80, DSPS: fa7fa028 May 14 06:23:36 lib-04 vmunix: lsp: 0 May 14 06:23:36 lib-04 vmunix: lbp->owner: 0 May 14 06:23:36 lib-04 vmunix: scratch_lsp: 0 May 14 06:23:36 lib-04 vmunix: Pre-DSP script dump [fa7fa0e0]:
May 14 06:23:36 lib-04 vmunix: e0340004 00000000 e0100004 00000000
May 14 06:23:36 lib-04 vmunix: 48000000 00000000 78350000 00000000 May 14 06:23:36 lib-04 vmunix: Script dump [fa7fa100]:
May 14 06:23:36 lib-04 vmunix: 50000000 fa7fa028 80000000 0000000b
May 14 06:23:36 lib-04 vmunix: 0f000001 fa7fa580 60000040 00000000 May 14 06:23:36 lib-04 vmunix: NCR chip register dump for: 0x100200a May 14 06:23:36 lib-04 vmunix: 00: SCNTL3: 5f SCNTL2: 00 SCNTL1: 00 SCNTL0: d8
May 14 06:23:36 lib-04 vmunix: 04: GPREG: 0b SDID: 0c SXFER: 1f SCID: 47
May 14 06:23:36 lib-04 vmunix: 08: SBCL: 00 SSID: 8c SOCL: 00 SFBR: 00
May 14 06:23:36 lib-04 vmunix: 0c: SSTAT2: 0a SSTAT1: 0f SSTAT0: 00 DSTAT: 80
May 14 06:23:36 lib-04 vmunix: 10: DSA: c0ffffff May 14 06:23:36 lib-04 vmunix: 14: MBOX1: 00 MBOX0: 00 ISTAT1: 00 ISTAT: 00
May 14 06:23:36 lib-04 vmunix: 18: CTEST3: 71 CTEST2: 35 CTEST1: 00 CTEST0: ff
May 14 06:23:36 lib-04 vmunix: 1c: TEMP: fa7fad78 May 14 06:23:36 lib-04 vmunix: 20: CTEST6: c0 CTEST5: 24 CTEST4: 00 DFIFO: 00
May 14 06:23:36 lib-04 vmunix: 24: DCMDDBC: 50000000 May 14 06:23:36 lib-04 vmunix: 28: DNAD: fa7fa100 May 14 06:23:36 lib-04 vmunix: 2c: DSP: fa7fa108 May 14 06:23:36 lib-04 vmunix: 30: DSPS: fa7fa028 May 14 06:23:36 lib-04 vmunix: 34: SCRATCHA: ff00007d May 14 06:23:36 lib-04 vmunix: 38: DCNTL: a1 DWT: 00 DIEN: 7f DMODE: 4c
May 14 06:23:36 lib-04 vmunix: 3c: ADDER: faff4130 May 14 06:23:36 lib-04 vmunix: 40: SIST1: 00 SIST0: 00 SIEN1: 87 SIEN0: 8f
May 14 06:23:36 lib-04 vmunix: 44: GPCNTL: 0f MACNTL: f0 SWIDE: 00 SLPAR: 6b
May 14 06:23:36 lib-04 vmunix: 48: RESPID1: 00 RESPID0: 80 STIME1: 00 STIME0: 0c
May 14 06:23:36 lib-04 vmunix: 4c: STEST3: 80 STEST2: 00 STEST1: 0c STEST0: 76
May 14 06:23:36 lib-04 vmunix: 50: RESV50: 80 RESV51: e0 SIDL1: 00 SIDL0: 00
May 14 06:23:36 lib-04 vmunix: 54: CCNTL1: 00 CCNTL0: 00 SODL1: 0a SODL0: 00
May 14 06:23:36 lib-04 vmunix: 58: RESV58: 00 RESV59: 00 SBDL1: 00 SBDL0: 00
May 14 06:23:36 lib-04 vmunix: 5c: SCRATCHB: 00000000 May 14 06:23:36 lib-04 vmunix: 60: SCRATCHC: 00000000 May 14 06:23:36 lib-04 vmunix: 64: SCRATCHD: 0000
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2003 09:56 AM
05-14-2003 09:56 AM
Re: BCC replacement on one SC10
But you've got another at 0/7/0/0.14.0 that 'CLAIMED'.
Time to put in a HW call and get a CE out there.
You can also try the trouble shooting commands listed here, especially 'irdiag -v':
http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/J6173-90007/J6173-90007_top.html&con=/hpux/onlinedocs/J6173-90007/00/00/44-con.html&toc=/hpux/onlinedocs/J6173-90007/00/00/44-toc.html&searchterms=A5272A&queryid=20030514-114553
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2003 11:10 AM
05-14-2003 11:10 AM
Re: BCC replacement on one SC10
BCC is not hot pluggable and not customer replaceable, so I recommend you to call HP.
But before please check if SC10 power cycle will resolve the problem, and if this issue intermittent or not - is this BCC sometimes CLAIMED and sometimes NO_HW? Did you ever see backend disks as NO_HW also?
Eugeny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2003 12:35 PM
05-14-2003 12:35 PM
Re: BCC replacement on one SC10
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2003 12:35 PM
05-14-2003 12:35 PM
Re: BCC replacement on one SC10
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2003 10:21 PM
05-14-2003 10:21 PM
Re: BCC replacement on one SC10
There are a lot of possibilities for this problem:
1. HBA faulty
2. Cable faulty
3. Terminator faulty
4. BCC port faulty
5. That's it.
The BCC is not necessarily faulty; it could be other things. You should call HP to diagnose the problem themselves.
HTH,
Vince
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2003 05:41 AM
05-15-2003 05:41 AM
Re: BCC replacement on one SC10
Eugeny