Problem configuring NIC in DGUX


 
Thread Tools Search this Thread
Special Forums IP Networking Problem configuring NIC in DGUX
# 1  
Old 09-11-2007
Power Problem configuring NIC in DGUX

Old DG box Aviion PentiumPro running R4.20Mu06 being used to try to recreate Ingres db from backup tapes so machine has not been operational before and some of original files in /etc may have ben overwritten

Unable to get NIC working
Any pointers on how to go about configuring NIC Smilie
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Configuring NIC device in Solaris 9 SPARC OS [QEMU]

I have Xubuntu 18.04 installed on my PC. I have created a 10G .img image file created by QEMU-IMG. I have installed inside of it Solaris 9 SPARC edition . If I try and mount the image file as a loop device (using sudo losetup /dev/loop0 /path-to-img-file) I can only mount it as read only. ... (1 Reply)
Discussion started by: alphatron150
1 Replies

2. UNIX for Dummies Questions & Answers

Need help with listing and sorting in DGUX

Hello all, very much a Unix newbie. My company has an old DG/UX system we use for customer data. I need to archive some data to clear some space, so I wanted to be able to list items in each directory by size, to grab some "low hanging" fruit to give me some breathing room as the system is... (0 Replies)
Discussion started by: Trader2699
0 Replies

3. Solaris

NIC problem

can anyone help me fix this? what command should I use to bring them back to "TRUE"? Interface Speed Duplex Autoneg --------- ----- ------ ------- ce0 100 Mbit/s FULL FALSE ce5 100 Mbit/s FULL ... (3 Replies)
Discussion started by: uuontario
3 Replies

4. Solaris

IPMP. Is this a NIC problem!!?

-- IPMP Groups -- Node Name Group Status Adapter Status --------- ----- ------ ------- ------ IPMP Group: hostname1.xx-xxxx.xxxi sc_ipmp1 Online ce5 Online IPMP Group: hostname1.xx-xxxx.xxxi ipmpgrp01... (2 Replies)
Discussion started by: FeNiCrC_Neil
2 Replies

5. UNIX for Dummies Questions & Answers

nic problem

hello friends i am using x86 pc i can install solaris o/s but nic card is not deceting. i am not able see in file called /etc/path_to_inst. i did /touch reconfigu and devfsadm also. i used external nic card also realtech 8169d am using gigabyte mother board 775. (0 Replies)
Discussion started by: manoj123
0 Replies

6. UNIX for Dummies Questions & Answers

DGUX manuals

Hi Anyone know where i get DGUX manuals.... Cheers (1 Reply)
Discussion started by: Flipper_Al
1 Replies

7. Solaris

Configuring 1 Nic card with 2 IP addresses and 2 seperate default Gateways in Solaris

Hi ...... I'm trying to configure my Solaris servers with only one NIC card to have 2 IP addresses as well as 2 different default gateways. ( NOT to be confused with multi-pathing - with 2 physical IPs & 1 virtual ip) Thanks, Remi (1 Reply)
Discussion started by: Remi
1 Replies

8. HP-UX

configuring nic card

using sam i have tryed to configure the nic, however when i try to do so i get an error saying i couldn't as i was using BIND ? (0 Replies)
Discussion started by: bobstar01
0 Replies

9. HP-UX

Configuring NIC

Hi. I have HP-9000 Server running HP-UX 10.20. rECENTLY OUR network upgraded to 100mb/sec and I want to do same on the server. So, I add the second Network card (100MB). But the problem is, I can't find a way of configuring this card. How am i going to tell the server to use this 100mb card... (1 Reply)
Discussion started by: wobitu
1 Replies
Login or Register to Ask a Question
BACKUP_RESTOREDB(8)					       AFS Command Reference					       BACKUP_RESTOREDB(8)

NAME
backup_restoredb - Restores a saved copy of the Backup Database SYNOPSIS
backup restoredb [-portoffset <TC port offset>] [-localauth] [-cell <cell name>] [-help] backup res [-p <TC port offset>] [-l] [-c <cell name>] [-h] DESCRIPTION
The backup restoredb command restores to the Backup Server machine's local disk a version of the Backup Database previously written to tape by using the backup savedb command. (If the "FILE YES" instruction appears in the /var/lib/openafs/backup/CFG_device_name file associated with the specified port offset, then the backup restoredb command restores data from the backup data file listed for that port offset in the Tape Coordinator's /var/lib/openafs/backup/tapeconfig file, instead of from tape. For the sake of clarity, the following text refers to tapes only, but the Backup System handles backup data files in much the same way.) The most common reason to run this command is to replace a corrupted or otherwise damaged Backup Database; use the backup dbverify command to determine the database's status. The command can also be used to restore records that were removed from the database when the -archive argument was included on a previous backup savedb command. The command completely overwrites the existing Backup Database records for volume sets, Tape Coordinators, and the dump hierarchy with the corresponding information from the saved version. It does not overwrite existing dump records, but instead interleaves the records from the copy being restored. If both the existing database (on the Backup Server machine's disk) and the copy being restored include a record about the same dump, the Backup System retains the one in the existing database. The Tape Coordinator's default response to this command is to access the first tape it needs by invoking the "MOUNT" instruction in the local /var/lib/openafs/backup/CFG_device_name file, or by prompting the backup operator to insert the tape if there is no "MOUNT" instruction. However, if the "AUTOQUERY NO" instruction appears in the CFG_device_name file, or if the issuer of the butc command included the -noautoquery flag, the Tape Coordinator instead expects the tape to be in the device already. If it is not, or is the wrong tape, the Tape Coordinator invokes the "MOUNT" instruction or prompts the operator. It also invokes the "MOUNT" instruction or prompts for any additional tapes needed to complete the restore operation; the backup operator must arrange to provide them. CAUTIONS
If the database is corrupted, do not attempt to restore a saved database on top of it. Instead, use the instructions for repairing a corrupted database in the OpenAFS Administration Guide chapter about performing backup operations. OPTIONS
-portoffset <TC port offset> Specifies the port offset number of the Tape Coordinator handling the tapes for this operation. -localauth Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The backup command interpreter presents it to the Backup Server, Volume Server and VL Server during mutual authentication. Do not combine this flag with the -cell argument. For more details, see backup(8). -cell <cell name> Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see backup(8). -help Prints the online help for this command. All other valid options are ignored. EXAMPLES
The following example shows the Backup Database being restored from the Tape Coordinator with port offset 0: % backup restoredb PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on every machine where the Backup Server is running, or must be logged onto a server machine as the local superuser "root" if the -localauth flag is included. SEE ALSO
butc(5), backup(8), backup_dbverify(8), backup_savedb(8), butc(8) The OpenAFS Administration Guide at <http://docs.openafs.org/AdminGuide/>. COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 BACKUP_RESTOREDB(8)