HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: retrive back $2$GGA1
Operating System - OpenVMS
1827789
Members
2694
Online
109969
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
07-13-2008 09:12 PM
07-13-2008 09:12 PM
retrive back $2$GGA1
I have difficult to retrieve back messing device who I don’t know how to troubleshoot. We have 2 backup device (MSL 5000 and MSL 6000). On MSL5000 know as $2$GGA0 as robotic SCSI. For MSL 6000 control by $2$GGA1 robotic SCSI. Previously its working fine. After we facing power trip (power down) , I restart back the vms and found missing device in $2$GGA1. The error massage as bellow.
HSIBD2::D_PROD:> sh dev $2$gga1
%SYSTEM-W-NOSUCHDEV, no such device available
HSIBD2::D_PROD:> sh dev gg
Device Device Error
Name Status Count
$2$GGA0: Online 0
The system only found $2$GGA0 as a device and messing $2$GGA1. We currently running on vms 7.3-2. In windows platform this backup are running well. How we can retrieve back this device. Thanks
HSIBD2::D_PROD:> sh dev $2$gga1
%SYSTEM-W-NOSUCHDEV, no such device available
HSIBD2::D_PROD:> sh dev gg
Device Device Error
Name Status Count
$2$GGA0: Online 0
The system only found $2$GGA0 as a device and messing $2$GGA1. We currently running on vms 7.3-2. In windows platform this backup are running well. How we can retrieve back this device. Thanks
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2008 06:32 AM
07-14-2008 06:32 AM
Re: retrive back $2$GGA1
Follow the instalation and configuration steps for the MSL 6000; this should manifest the GGA loader device for you.
You need to have the device configured correctly for the management LUN, and there are steps for OpenVMS itself. There are various places where a configuration problem can lurk here.
On the OpenVMS end, it's usually a one-shot of:
SYSMAN> IO FIND
SYSMAN> IO AUTO
The first is a one-shot command and goes rummaging around the FC SAN and builds the devices database file. The second then manifests the devices.
Subsequent reboots use the devices database file within the automatic boot-time autoconfiguration process to manifest the FC SAN devices.
There are equivalent configuration steps out on the MSL; see the installation documentation for that widget.
You need to have the device configured correctly for the management LUN, and there are steps for OpenVMS itself. There are various places where a configuration problem can lurk here.
On the OpenVMS end, it's usually a one-shot of:
SYSMAN> IO FIND
SYSMAN> IO AUTO
The first is a one-shot command and goes rummaging around the FC SAN and builds the devices database file. The second then manifests the devices.
Subsequent reboots use the devices database file within the automatic boot-time autoconfiguration process to manifest the FC SAN devices.
There are equivalent configuration steps out on the MSL; see the installation documentation for that widget.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2008 06:57 AM
07-14-2008 06:57 AM
Re: retrive back $2$GGA1
We never had power trips but may be the VMS node rebooted before the rest. If posible, try a reboot.
Wim
Wim
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2008 12:04 AM
07-15-2008 12:04 AM
Re: retrive back $2$GGA1
My guess is that the Fiber Router (NSR1200?) rebooted itself before the library completed it's boot.
You will have to reboot the router, then run a SYSMAN IO AUTO /SELECT=GGA*, which you _should_ be able to do while the system is operational, as long as you're not accessing the drives.
At the very least, you could log onto the router and check to see if it can see the tape robot. Through the web GUI Report screen, it should look something like this :-
Virtual Devices
Type State Map Cnt LUN ID Device Description Serial No.
CTLR UP 1 0 HP NS E1200-320
Rob.
You will have to reboot the router, then run a SYSMAN IO AUTO /SELECT=GGA*, which you _should_ be able to do while the system is operational, as long as you're not accessing the drives.
At the very least, you could log onto the router and check to see if it can see the tape robot. Through the web GUI Report screen, it should look something like this :-
Virtual Devices
Type State Map Cnt LUN ID Device Description Serial No.
CTLR UP 1 0 HP NS E1200-320
Rob.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP