[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
|
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
Hi
My Customer need help to configure 4 Metrum RSP-2150 Tapes on an Alphaserver
1000A 4/266
with Digital Unix V4.0b .
I've never seen such tape, so I know nothing about this kind of tape.
He made the "tz" devices with /dev/MAKEDEV and the tapes works ok.
But in the startup entries from uerf he can't see any devices nor other
information from the system. The same in /var/adm/messages output.
After he disconnected the tapes from the system, the uerf entries looks like
normal .
I think , it's necessary to define an correct entry in the /etc/ddr.dbase for
the RSP-2150 tape and make a ddr_config -c to create a new /etc/ddr.db
database. If this is correct - how must look like this entry ??
Here is an startup entry without the tapes:
********************************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 300. SYSTEM STARTUP
SEQUENCE NUMBER 0.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Thu Feb 20 12:02:33 1997
OCCURRED ON SYSTEM wrzx19
SYSTEM ID x0006001B
SYSTYPE x00000000
MESSAGE Alpha boot: available memory from
_0x850000 to 0x7fee000
Digital UNIX V4.0B (Rev. 564); Wed
_Feb 19 16:06:10 MET 1997
physical memory = 128.00 megabytes.
available memory = 119.71 megabytes.
using 484 buffers containing 3.78
_megabytes of memory
AlphaServer 1000A 4/266
Firmware revision: 4.7
PALcode: OSF version 1.45
pci0 at nexus
eisa0 at pci0
ace0 at eisa0
ace1 at eisa0
lp0 at eisa0
fdi0 at eisa0
fd0 at fdi0 unit 0
cirrus0 at eisa0
cirrus0: Cirrus Logic CL-GD5428 (SVGA)
_512 Kbytes
pci2000 at pci0 slot 8
isp0 at pci2000 slot 0
isp0: QLOGIC ISP1020A
cam_logger: CAM_ERROR packet
cam_logger: bus 0
isp_probe
NVRAM parameters invalid, using driver
_Fast10 defaults
isp0: Firmware revision 2.10 (loaded
_by console)
scsi0 at isp0 slot 0
rz0 at scsi0 target 0 lun 0 (LID=0)
_(DEC RZ28D (C) DEC 0010)
_(Wide16)
rz4 at scsi0 target 4 lun 0 (LID=1)
_(DEC RRD45 (C) DEC 0436)
psiop0 at pci2000 slot 1
Loading SIOP: script 80a700, reg
_82011000, data 405f2610
scsi1 at psiop0 slot 0
psiop1 at pci2000 slot 2
Loading SIOP: script 816700, reg
_82011100, data 405f2a10
scsi2 at psiop1 slot 0
psiop2 at pci2000 slot 3
Loading SIOP: script 822700, reg
_82011200, data 405f2e10
scsi3 at psiop2 slot 0
psiop3 at pci2000 slot 4
Loading SIOP: script 82e700, reg
_82011300, data 405f3210
scsi4 at psiop3 slot 0
tu0: DECchip 21040-AA: Revision: 2.4
tu0 at pci0 slot 11
tu0: DEC TULIP Ethernet Interface,
_hardware address: 00-00-F8-21-8A-23
tu0: console mode: selecting 10BaseT
_(UTP) port: half duplex: no link
fta0 DEC DEFPA FDDI Module, Hardware
_Revision 0
fta0 at pci0 slot 12
fta0: DMA Available.
fta0: DEC DEFPA (PDQ) FDDI Interface,
_Hardware address: 00-00-F8-60-11-D3
fta0: Firmware rev: 2.46
gpc0 at eisa0
No FRU table entry found in
_console-rpb
--Not creating a FRU table errorlog
_packet
kernel console: cirrus0
dli: configured
=========================
and now with the tapes connected to the system:
************************************************
uerf version 4.2-011 (122)
********************************* ENTRY 1.
*********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 300. SYSTEM STARTUP
SEQUENCE NUMBER 0.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Thu Feb 20 12:08:33 1997
OCCURRED ON SYSTEM wrzx19
SYSTEM ID x0006001B
SYSTYPE x00000000
MESSAGE li: configured
********************************* ENTRY 2.
*********************************
The output from /var/adm/messages:
**********************************
Feb 20 12:02:33 wrzx19 vmunix: Alpha boot: available memory from 0x850000 to
0x7fee000
Feb 20 12:02:33 wrzx19 vmunix: Digital UNIX V4.0B (Rev. 564); Wed Feb 19
16:06:10 MET 1997
Feb 20 12:02:33 wrzx19 vmunix: physical memory = 128.00 megabytes.
Feb 20 12:02:33 wrzx19 vmunix: available memory = 119.71 megabytes.
Feb 20 12:02:33 wrzx19 vmunix: using 484 buffers containing 3.78 megabytes of
memory
Feb 20 12:02:33 wrzx19 vmunix: AlphaServer 1000A 4/266
Feb 20 12:02:33 wrzx19 vmunix: Firmware revision: 4.7
Feb 20 12:02:33 wrzx19 vmunix: PALcode: OSF version 1.45
Feb 20 12:02:33 wrzx19 vmunix: pci0 at nexus
Feb 20 12:02:33 wrzx19 vmunix: eisa0 at pci0
Feb 20 12:02:33 wrzx19 vmunix: ace0 at eisa0
Feb 20 12:02:33 wrzx19 vmunix: ace1 at eisa0
Feb 20 12:02:33 wrzx19 vmunix: lp0 at eisa0
Feb 20 12:02:34 wrzx19 vmunix: fdi0 at eisa0
Feb 20 12:02:34 wrzx19 vmunix: fd0 at fdi0 unit 0
Feb 20 12:02:34 wrzx19 vmunix: cirrus0 at eisa0
Feb 20 12:02:34 wrzx19 vmunix: cirrus0: Cirrus Logic CL-GD5428 (SVGA) 512
Kbytes
Feb 20 12:02:34 wrzx19 vmunix: pci2000 at pci0 slot 8
Feb 20 12:02:34 wrzx19 vmunix: isp0 at pci2000 slot 0
Feb 20 12:02:34 wrzx19 vmunix: isp0: QLOGIC ISP1020A
Feb 20 12:02:34 wrzx19 vmunix: cam_logger: CAM_ERROR packet
Feb 20 12:02:34 wrzx19 vmunix: cam_logger: bus 0
Feb 20 12:02:34 wrzx19 vmunix: isp_probe
Feb 20 12:02:34 wrzx19 vmunix: NVRAM parameters invalid, using driver Fast10
defaults
Feb 20 12:02:34 wrzx19 vmunix: isp0: Firmware revision 2.10 (loaded by
console)
Feb 20 12:02:34 wrzx19 vmunix: scsi0 at isp0 slot 0
Feb 20 12:02:34 wrzx19 vmunix: rz0 at scsi0 target 0 lun 0 (LID=0) (DEC
RZ28D (C) DEC 0010) (Wide16)
Feb 20 12:02:34 wrzx19 vmunix: rz4 at scsi0 target 4 lun 0 (LID=1) (DEC
RRD45 (C) DEC 0436)
Feb 20 12:02:34 wrzx19 vmunix: psiop0 at pci2000 slot 1
Feb 20 12:02:34 wrzx19 vmunix: Loading SIOP: script 80a700, reg 82011000, data
405f2610
Feb 20 12:02:34 wrzx19 vmunix: scsi1 at psiop0 slot 0
Feb 20 12:02:34 wrzx19 vmunix: psiop1 at pci2000 slot 2
Feb 20 12:02:34 wrzx19 vmunix: Loading SIOP: script 816700, reg 82011100, data
405f2a10
Feb 20 12:02:34 wrzx19 vmunix: scsi2 at psiop1 slot 0
Feb 20 12:02:34 wrzx19 vmunix: psiop2 at pci2000 slot 3
Feb 20 12:02:34 wrzx19 vmunix: Loading SIOP: script 822700, reg 82011200, data
405f2e10
Feb 20 12:02:34 wrzx19 vmunix: scsi3 at psiop2 slot 0
Feb 20 12:02:34 wrzx19 vmunix: psiop3 at pci2000 slot 4
Feb 20 12:02:34 wrzx19 vmunix: Loading SIOP: script 82e700, reg 82011300, data
405f3210
Feb 20 12:02:34 wrzx19 vmunix: scsi4 at psiop3 slot 0
Feb 20 12:02:34 wrzx19 vmunix: tu0: DECchip 21040-AA: Revision: 2.4
Feb 20 12:02:34 wrzx19 vmunix: tu0 at pci0 slot 11
Feb 20 12:02:34 wrzx19 vmunix: tu0: DEC TULIP Ethernet Interface, hardware
address: 00-00-F8-21-8A-23
Feb 20 12:02:34 wrzx19 vmunix: tu0: console mode: selecting 10BaseT (UTP)
port: half duplex: no link
Feb 20 12:02:34 wrzx19 vmunix: fta0 DEC DEFPA FDDI Module, Hardware Revision 0
Feb 20 12:02:34 wrzx19 vmunix: fta0 at pci0 slot 12
Feb 20 12:02:34 wrzx19 vmunix: fta0: DMA Available.
Feb 20 12:02:34 wrzx19 vmunix: fta0: DEC DEFPA (PDQ) FDDI Interface, Hardware
address: 00-00-F8-60-11-D3
Feb 20 12:02:34 wrzx19 vmunix: fta0: Firmware rev: 2.46
Feb 20 12:02:35 wrzx19 vmunix: gpc0 at eisa0
Feb 20 12:02:35 wrzx19 vmunix: No FRU table entry found in console-rpb
Feb 20 12:02:35 wrzx19 vmunix: --Not creating a FRU table errorlog packet
Feb 20 12:02:35 wrzx19 vmunix: kernel console: cirrus0
Feb 20 12:02:35 wrzx19 vmunix: dli: configured
Feb 20 12:02:35 wrzx19 vmunix: ADVFS: using 1153 buffers containing 9.00
megabytes of memory
Feb 20 12:02:35 wrzx19 vmunix: fta0: Link Unavailable.
Feb 20 12:02:35 wrzx19 vmunix: fta0: Link Available.
Feb 20 12:03:15 wrzx19 vmunix: Environmental Monitoring Subsystem Configured.
Feb 20 12:08:33 wrzx19 vmunix: li: configured
Feb 20 12:08:33 wrzx19 vmunix: ADVFS: using 1153 buffers containing 9.00
megabytes of memory
Feb 20 12:08:33 wrzx19 vmunix: fta0: Link Unavailable.
Feb 20 12:08:33 wrzx19 vmunix: fta0: Link Available.
Feb 20 12:09:25 wrzx19 vmunix: Environmental Monitoring Subsystem Configured.
=========================
scu> show edt
CAM Equipment Device Table (EDT) Information:
Device: RZ28D Bus: 0, Target: 0, Lun: 0, Type: Direct Access
Device: RZ28D Bus: 0, Target: 0, Lun: 1, Type: (not present)
Device: RZ28D Bus: 0, Target: 0, Lun: 2, Type: (not present)
Device: RZ28D Bus: 0, Target: 0, Lun: 3, Type: (not present)
Device: RZ28D Bus: 0, Target: 0, Lun: 4, Type: (not present)
Device: RZ28D Bus: 0, Target: 0, Lun: 5, Type: (not present)
Device: RZ28D Bus: 0, Target: 0, Lun: 6, Type: (not present)
Device: RZ28D Bus: 0, Target: 0, Lun: 7, Type: (not present)
Device: RRD45 Bus: 0, Target: 4, Lun: 0, Type: Read-Only Direct Access
Device: RRD45 Bus: 0, Target: 4, Lun: 1, Type: (not present)
Device: RRD45 Bus: 0, Target: 4, Lun: 2, Type: (not present)
Device: RRD45 Bus: 0, Target: 4, Lun: 3, Type: (not present)
Device: RRD45 Bus: 0, Target: 4, Lun: 4, Type: (not present)
Device: RRD45 Bus: 0, Target: 4, Lun: 5, Type: (not present)
Device: RRD45 Bus: 0, Target: 4, Lun: 6, Type: (not present)
Device: RRD45 Bus: 0, Target: 4, Lun: 7, Type: (not present)
Device: RSP-2150 Bus: 2, Target: 1, Lun: 0, Type: Sequential Access
Device: RSP-2150 Bus: 2, Target: 1, Lun: 1, Type: Sequential Access
Device: RSP-2150 Bus: 2, Target: 1, Lun: 2, Type: Sequential Access
Device: RSP-2150 Bus: 2, Target: 1, Lun: 3, Type: Sequential Access
Device: RSP-2150 Bus: 2, Target: 1, Lun: 4, Type: Sequential Access
Device: RSP-2150 Bus: 2, Target: 1, Lun: 5, Type: Sequential Access
Device: RSP-2150 Bus: 2, Target: 1, Lun: 6, Type: Sequential Access
Device: RSP-2150 Bus: 2, Target: 1, Lun: 7, Type: Sequential Access
Device: RSP-2150 Bus: 2, Target: 3, Lun: 0, Type: Sequential Access
Device: RSP-2150 Bus: 2, Target: 3, Lun: 1, Type: Sequential Access
Device: RSP-2150 Bus: 2, Target: 3, Lun: 2, Type: Sequential Access
Device: RSP-2150 Bus: 2, Target: 3, Lun: 3, Type: Sequential Access
Device: RSP-2150 Bus: 2, Target: 3, Lun: 4, Type: Sequential Access
Device: RSP-2150 Bus: 2, Target: 3, Lun: 5, Type: Sequential Access
Device: RSP-2150 Bus: 2, Target: 3, Lun: 6, Type: Sequential Access
Device: RSP-2150 Bus: 2, Target: 3, Lun: 7, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 1, Lun: 0, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 1, Lun: 1, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 1, Lun: 2, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 1, Lun: 3, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 1, Lun: 4, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 1, Lun: 5, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 1, Lun: 6, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 1, Lun: 7, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 3, Lun: 0, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 3, Lun: 1, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 3, Lun: 2, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 3, Lun: 3, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 3, Lun: 4, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 3, Lun: 5, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 3, Lun: 6, Type: Sequential Access
Device: RSP-2150 Bus: 3, Target: 3, Lun: 7, Type: Sequential Access
=========================
scu> sho edt bus 2 target 1 lun 0 full
CAM Equipment Device Table (EDT) Information:
Inquiry Information:
SCSI Bus ID: 2
SCSI Target ID: 1
SCSI Target LUN: 0
Peripheral Device Type: 0x1 (Sequential Access)
Peripheral Qualifier: 0 (Peripheral Device Connected)
Device Type Modifier: 0
Removable Media: Yes
ANSI Version: 1 (Complies to ANSI X3.131-1986, SCSI-1)
ECMA Version: 0
ISO Version: 0
Response Data Format: 0 (SCSI-1)
Additional Length: 51
Vendor Identification: Metrum
Product Identification: RSP-2150
Firmware Revision Level: V05.
Furthermore 32 of /dev/rmt* devices (and nrm*..) were created on system
startup,
although he needs only rmt0* - rmt4* (and nrm.. devices). So is it possible to
avoid creating of the LUN's devices ??
any help is greatly appriciated
/Walter
[Posted by WWW Notes gateway]
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 8925.1 | Try using DECevent | NETRIX::"[email protected]" | Jan Reimers | Fri Feb 21 1997 13:26 | 4 |
| uerf is no longer updated and maintained. It may not be able to
understand the newer entries in the error log. Try using DECevent
to see if the system information is available.
[Posted by WWW Notes gateway]
|