Lucent Technologies 585-210-940 Create an alternate boot device, # ls -l /dev/rdsk/newbootdev

Page 32

Installing Mirrored Systems

CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems

How to upgrade an Enterprise platform to disk mirroring

26

 

 

 

# metastat

 

 

 

 

. . .

 

 

 

 

d21: Mirror

 

 

 

 

Submirror 0: d19

 

 

 

State: Okay

 

 

 

Submirror 1: d20

 

 

 

State: Okay

 

 

 

. . .

 

 

 

 

d19: Submirror of d21

 

 

 

State: Okay

 

 

 

 

Size: 14398560 blocks

 

 

 

Stripe 0:

 

 

 

 

Device

Start Block

Dbase

State

Hot Spare

c0t0d0s3

0

No

Okay

 

Stripe 1:

 

 

 

 

Device

Start Block

Dbase State

Hot Spare

c0t2d0s1

0

No

Okay

 

d20: Submirror of d21

 

 

 

State: Okay

 

 

 

 

Size: 14398560 blocks

 

 

 

Stripe 0:

 

 

 

 

Device

Start Block

Dbase State

Hot Spare

c0t1d0s3

 

0

No

Okay

Stripe 1:

 

 

 

 

Device

Start Block

Dbase State

Hot Spare

c0t3d0s1

 

0

No

Okay

 

 

 

 

 

Step 11: Create an alternate boot device

If the stripes of d19 and d20 do not account for all the disk drives on your system, check your disk drive connections. If discrepancies persist, telephone the Lucent National Customer Care Center at 1.800.242.2121, or contact your Lucent representative or distributor.

Set up an alternate boot device by doing the following procedure:

1.Enter the following command:

# ls -l /dev/rdsk/<newbootdev>

where newbootdev is the device name of the disk chosen as boot disk 2 (recorded as the d12 metadevice on page 13).

If your boot disk 2 were c0t2d0s0, for example, the system would respond with something like this:

lrwxrwxrwx 1 root root 83 Jun 18 15:23 /dev/rdsk/c0t2d0s0 ->

../../devices/sbus@3,0/SUNW,fas@3,8800000 /sd@2,0:a,raw

2.Record the part of the line immediately following /devices and preceding :a. For the example above, you would record the part of the line beginning /sbus@3,0 and ending sd@2,0.

Page 31 Page 33
Image 32
Page 31 Page 33
Contents CentreVu Call Management System Comments Table of Contents CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems Index CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems IiiCentreVu CMS Release 3 Version 8 Disk-Mirrored Systems Backed up just as often as unmirrored systems Disk mirroring definedMetadevices Concatenated Mirrors State databasesSolstice DiskSuite D21 D20 How CMS implements disk mirroringD19 D11 D13 D12D15 D17 D16Mirror layouts Mirror d13 Mirror d21 Mirror d17Root filesystem Cms filesystem Submirror DisksEnterprise Required software Additional referencesHow CMS implements disk mirroring How to upgrade an Enterprise platform to disk mirroring Disk drive slotsIncreasing system capacity Identify mirror devicesDevice Names Submirror d15 Submirror d16# ls -l /dev/dsk/c1t6d0s0 SystemDo this step only if you have an Enterprise 3500 system How to upgrade an Enterprise platform to disk mirroring Ok boot -r # ls -l /dev/dsk/c2t6d0s0Do this step only if you have an Enterprise 3000 system Enter format partition3500 Disk PartFlag StartingEnter partition q # export PATH=$PATH/usr/opt/SUNWmd/sbin/olds# metadb -a -c3 -f /dev/rdsk/device # metadbDx y 1 device Set up the mirrors for the root file system # metainit -f d11 D11 Concat/stripe is set up# metainit -f d13 D13 Concat/stripe is set up # metainit -f d12 D12 Concat/stripe is set up# /usr/sbin/shutdown -i6 -g0 -y Password password# metaroot d13 Set up the mirrors for the swap space # metainit -f d15 D15 Concat/stripe is set up# metainit d17 D17 Concat/stripe is set up # metainit d16 D16 Concat/stripe is set up# swap -a /dev/md/dsk/d17 Set up the /cms mirror Verify disk space Disk Space VerificationCreate an alternate boot device # ls -l /dev/rdsk/newbootdevOk nvalias bootdevice2 device Ok boot bootdevice2# /usr/sbin/shutdown -y -i0 -g0 Sbus@3,0/SUNW,fas@3,8800000/sd@2,0Factory installation procedures for disk mirroring Install the hardwareInstall the application software 3500 Disk PartCheck the disk.type file # stty erase Ctrl-H # ksh -o# olds -mirrored -mkfiles Run the setup scripts Ok boot -r Hostname console login root Password password14171072 14205776 1430988814376992 14446400 14550512Disk Space Verification Install the CMS software Enter the following command ok devalias # chmod +x /olds/chkDisks Factory installation procedures for disk mirroring Using the alternate boot device Ok setenv boot-device disk # eeprom boot-device=diskCanceling chkDisks Maintaining the chkDisks crontabActivating chkDisks Verifying chkDisks # crontab -lDoing a Cmsadm backup on a mirrored system Run the backupPrint the vfstab file # lp /etc/vfstabLabel and store the tapes Restoring from a Cmsadm Backup # cpio -icmudv -C 10240 -I deviceRestoring from a Cmsadm Backup # umount /cms Repairing or rebuilding the /cms file systemRepairing /cms If you did not alter the vfstab file, do the following Rebuilding /cmsIf you altered the vfstab file earlier , do the following # metainit d19 D19 Concat/Stripe is set up # metainit d21 mirror is set up# metadetach d21 d20 D21 submirror d20 is detached # metaclear d20 D20 Concat/Stripe is cleared14724032 14793440 # newfs Dev/md/rdsk/d2114585216 14654624 Restoring a mirrored system from a Cmsadm backup Power off the systemSelect Language Ok boot cdromTask Action Result Identify the system ContinueConfirm Information Click ContinueSet the Name Service options 255.255.255.0 isInstallation Initial Set the date and timeGeographic Region RegionInstallation screen is Services? screen isAllocate Client Select LanguagesSelect the hard disks GB Disk Slice NameClick Continue Mount Remote File Click Begin Installation Reboot/No RebootClick Reboot Complete the OS installation # /olds/olds -cleanup Reestablish the disk mirrors# olds -mirrored -checkdisk Success, checking md.tab.new # PATH=$PATH/usr/opt/SUNWmd/sbin/olds # export Path# olds mirrored -mkfiles Success, creating md.tab.new Hostname login root Password root password Restoring specific files from a Cmsadm backup Adding new disks to a standard mirrored system # /usr/opt/SUNWmd/sbin/metastat# olds -mirrored -mkfiles c0t10d0 c0t11d0 # olds -mirrored -setup newdisk1 newdisk2 Adding new disks to a nonstandard mirrored system # df -k /cms# metattach d19 newdisk1 # metattach d20 newdisk2 # metattach d19 c0t10d0s1 # metattach d20 c0t11d0s1# growfs -M /cms /dev/md/rdsk/d21 # metastat# ls -l /dev/dsk/c Lrwxrwxrwx 1 root Root Replacing a faulty diskIdentify the faulty disk Identify the submirrors Size 14960160 blocks Stripe DeviceDbase State Hot Spare C0t2d0s1 Okay Stripe Device Dbase State Hot Spare C0t4d0s3 OkayDetach the submirrors Metadetach metamirror submirrorRemove state database replicas boot disks only Replace the faulty disk driveRecreate the state database replicas Reboot the system boot disks only You may delay this step until a more convenient time# metainit d20 # metattach d21 d20Setting up replicas Replacing replicas State Database Replicas# metadb -d -f /dev/dsk/c0t0d0s1 # metadb -d -c4 -f /dev/dsk/c0t0d0s1FC-AL E Partitioning disks with the format commandEnter # format Enter partition q How to tell whether your mirrored system is standard Root Metadevice Device NamesExamples of valid system files Valid vfstab filesValid vfstab file for a non mirrored R3V8 CMS system Valid vstab file for an R3V8 CMS system with mirrored disksValid md.tab file for a 4 disk mirrored R3V8 CMS system Valid md.tab filesValid md.tab file for a 3 disk non mirrored R3V8 CMS system Enter mount /cms Remounts /cms Excessively long resyncUnmount /cms umount /cms System fails to recognize all disk drives If you receive a This command may hang the systemEnter setenv auto-boot? false Toshiba XMS5701TASUN12XCD099704/09/97 Ok setenv auto-boot? trueOk boot -r Console login root Password Fixing needs maintenance messages C0t0d0s0 OkayOk setenv boot-device bootdevice2 Boot problemsPrimary boot device is not available Excessive reboot time Touch /etc/notrouterLog files File Name Description# ls /olds/chkDisks # /olds/chkDisksError messages Error Messages Explanation ResponseMessage Explanation Response # metareplace -e d13 c0t0d0s0Device devicename cannot be setup or does Not exist Disk diskname already setup, exitingDevice devicename will not be used Message ExplanationMessage Response No disks found! Internal error Command not foundMetadb hostname cxtyd0sz has a Metadevice database replica Metadetach systemname d21 resync ProgressMessage Error Messages Response DiskSuite Software must be installed To run this script File filename could not be restoredDisk is not recognized by cms /cms filesystem needs to be mountedTouch /cms/db/unixstart cannot create Enter reset-allUnbalanced configurations not supported Usage olds -mirrored -checkdisks Configuration, configure manuallyYou must be root in order to run this command Symbols IndexNeeds maintenance messages How Are We Doing?

585-210-940 specifications

Lucent Technologies, founded in 1996 as a spin-off from AT&T, emerged as a leader in telecommunications, contributing significantly to the advancement of network technologies. The model 585-210-940, an innovative product from Lucent, exemplifies their commitment to providing cutting-edge solutions for communication networks.

The 585-210-940 is primarily recognized as a digital cross-connect system (DCS) designed to manage and route digital voice and data traffic efficiently. This system plays a crucial role in facilitating seamless communication by allowing service providers to interconnect different digital circuits and manage bandwidth effectively. One of the main features of the 585-210-940 is its ability to support multiple protocols, which enhances interoperability among diverse communication platforms.

A standout characteristic of this system is its scalability. The 585-210-940 can adapt to growing network demands, making it suitable for both small enterprises and large service providers. This flexibility ensures that users can expand their systems without a complete overhaul, thereby reducing costs and downtime during upgrades. Additionally, the system provides fault tolerance, ensuring high availability and reliability, which are essential metrics for any critical telecommunications infrastructure.

Lucent Technologies also integrated advanced monitoring and management capabilities into the 585-210-940. This feature allows operators to track performance metrics and identify potential issues in real time. The system includes a user-friendly interface that simplifies network management tasks, making it accessible to operators with varying levels of technical expertise.

Moreover, the 585-210-940 is designed to support high capacity, handling numerous channels simultaneously without compromising performance. This capability is particularly beneficial in environments with heavy data traffic, such as urban centers or large corporate hubs.

In conclusion, Lucent Technologies' 585-210-940 serves as a robust solution for telecommunications, encapsulating many of the core innovations of the late 20th century. With its support for multiple protocols, scalability, fault tolerance, and advanced management capabilities, it stands out as an essential component for any modern communication network, reflecting Lucent's legacy in the industry.
Top Page Image Contents