Restoring 128-port devices after mksysb system restore

Special Notices

Please use this information with care. IBM will not be responsible for damages of any kind resulting from its use. The use of this information is the sole responsibility of the customer and depends on the customer's ability to evaluate and integrate this information into the customer's operational environment.

Abstract

This document describes issues related to restoring tty and printer devices attached to 128-port adapters using the RAN (Remote Asynchronous Nodes).

Date: Apr. 5-7, 1999

Index

• Overview of 128-port devices.
• What are the potential problems?
• Preventing mksysb problems.
• Collecting data prior to making a mksysb tape.
• Restoring devices using collected data.
  • Step by step to restore a tty.
  • Automating the process. Includes a script
• Restoring when no data was collected.

Levels supported by document

AIX Level 4.2.1 or Greater
AIX Level 4.3

Status

The status of this document and the accompanying script is that minimal testing has been done, but it now covers the main bases.

Overview of 128-port devices

Devices on the RS/6000 are numbered in the order in which they are added to the operating system. The system administrator can maintain a logical order to devices, or can choose to add devices in a random order. By maintaining a logical order to devices, many problems can be avoided as will be shown in the section Preventing mksysb problems..

128-port adapter numbering

128-port adapters are numbered in the order in which they are added to the system. If more than one adapter is added at the same time, then the order will be dependent on the order in which the bus is walked during the next boot sequence. The device name will be depending on the type of bus.

BUS	device names
Microchannel	cxma0, cxma1, ..
ISA	cxia0, cxia1, ..
PCI	cxpa0, cxpa1, ..

Bus walk order

The order of walking the bus is dependent on the RS/6000 model.

For the model H50 and H70 the order is:

  H50 order 		H70 order

  PCI slot 3		PCI slot 3

  PCI slot 4		PCI slot 4

  PCI slot 5		PCI slot 1

  PCI slot 1		PCI slot 2

  PCI slot 2		PCI slot 7

  PCI slot 6		PCI slot 8

  PCI slot 7		PCI slot 5

  PCI slot 8		PCI slot 6

  PCI slot 9

  ISA card 1

  ISA card 2

lsdev -Cc adapter | grep cx

cxpa0   Available 10-70    IBM 128-Port Async (PCI) Adapter

cxpa1   Available 30-60    IBM 128-Port Async (PCI) Adapter

The location code is dependent on the RS/6000 model and bus type.

Possible 128-Port adapter locations on the RS/6000 F50 and F70 are shown in this table:

	RS/6000 H50		RS/6000 H70
Slot Number	Location	Parent'	Location	Parent'
PCI slot 1	20-58	pci1	20-58	pci1
PCI slot 2	20-60	pci1	20-60	pci1
PCI slot 3	10-68	pci0	10-68	pci0
PCI slot 4	10-70	pci0	10-70	pci0
PCI slot 5	10-78	pci3	40-58	pci3
PCI slot 6	30-60	pci3	40-60	pci3
PCI slot 7	30-68	pci2	30-68	pci2
PCI slot 8	30-70	pci2	30-70	pci2
PCI slot 9	30-78	pci2	NA	NA
First ISA card	01-01	isa1	NA	NA
Second ISA card	01-02	isa2	NA	NA

Back the the lsdev command, you can add a -F flag and show the parent as shown here:

lsdev -Cc adapter -F"name location parent description" | grep cx

cxpa0   10-70    pci0    IBM 128-Port Async (PCI) Adapter

cxpa1   30-60    pci2    IBM 128-Port Async (PCI) Adapter

In an ideal system, the lower numbers will be located earlier in the sequence of walking the bus.

RAN numbering

RAN's are also numbered in the order in which they are added. This order has nothing to do with the adapter that they are located on. RANS are included among async adapters and are named sa3, sa4, sa5,.. The starting sa number for the first RAN will be dependent on the RS/6000 model and the adapters that have been installed earlier or have been found earlier in the boot sequence. In the boot sequence, the sequence that the RAN's are found is based first on the sequence in which the adapters are discovered, and then in the sequence of the line number and note number of the individual RAN's that are turned on during the boot. If a previously defined RAN is turned off during bootup, it will show up as defined.

The associating between the RAN and the parent 128-port adapter is can be seen by using the lsdev command :

lsdev -Cc concentrator

sa3 Available 10-70-11 16-Port RAN EIA-232 for 128-Port Adapter

sa4 Available 10-70-22 16-Port RAN EIA-232 for 128-Port Adapter

sa5 Available 30-60-21 16-Port RAN EIA-232 for 128-Port Adapter

Again, the lsdev command can add the -F flag to format the output to include the parent adapter.

lsdev -Cc concentrator -F"name location parent description"

sa3 10-70-11 cxpa0 16-Port RAN EIA-232 for 128-Port Adapter

sa4 10-70-22 cxpa0 16-Port RAN EIA-232 for 128-Port Adapter

sa5 30-60-21 cxpa1 16-Port RAN EIA-232 for 128-Port Adapter

TTY and Printer Device numbering

The first three two byte sequences of the tty or lp location will show the location of the parent RAN, while the last two bytes will show the port of the RAN.

To see the tty devices use:

lsdev -Cc tty

tty0 Available 01-S1-00-00 Asynchronous Terminal

tty1 Available 10-70-11-00 Asynchronous Terminal

tty2 Available 10-70-11-01 Asynchronous Terminal

tty3 Available 10-70-11-02 Asynchronous Terminal

tty4 Available 30-60-21-15 Asynchronous Terminal

tty5 Available 30-60-21-00 Asynchronous Terminal

tty6 Available 10-70-22-00 Asynchronous Terminal

tty7 Available 10-70-22-08 Asynchronous Terminal

lsdev -Cc printer

lp0 Available 10-70-11-05 Lexmark 4039 plus LaserPrinter

lp1 Available 10-70-22-04 IBM 4039 LaserPrinter

lp2 Available 30-60-21-09 Lexmark Optra laser printer

Wiring Diagram

Based on the previous information, construct a wiring diagram for your 128-port devices. For the sample configurations shown, the diagram might looks something like:

Device major and minor numbers

Major and Minor numbers for tty and lp devices can be found by doing a directory listing of the /dev directory. 128-port adapters and RAN's do not have major and minor numbers and do not have accessible special device files.

Look at the device files with ls -l /dev as shown below. The two numbers before the date are the major and minor numbers. The major number is operating system dependent, while the minor number is based on the location of the tty or lp device.

ls -l /dev/tty*

crw-rw-rw-   1 root     system     1,  0 Apr 05 10:40 /dev/tty

crw--w--w-   1 root     system    16,  0 Apr 05 10:41 /dev/tty0

crw-------   1 root     system    36,  0 Apr 02 17:13 /dev/tty1

crw-------   1 root     system    36,  1 Apr 02 17:13 /dev/tty2

crw-------   1 root     system    36,  2 Apr 02 17:13 /dev/tty3

crw-------   1 root     system    36,335 Apr 02 17:13 /dev/tty4

crw-------   1 root     system    36,320 Apr 02 17:13 /dev/tty5

crw--w--w-   1 root     system    36, 80 Apr 05 10:41 /dev/tty6

crw-------   1 root     system    36, 88 Apr 02 17:13 /dev/tty7

ls -l /dev/lp*

crw-rw-rw-   1 root     system    36,  5 Apr 02 17:13 /dev/lp0

crw-rw-rw-   1 root     system    36, 84 Apr 02 17:13 /dev/lp1

crw-rw-rw-   1 root     system    36,329 Apr 02 17:13 /dev/lp2

What are the potential problems?

When a system is restored from a mksysb tape, the device numbering for some devices such as 128-port adapters and RAN's is based on the order in which they are found while walking the bus, and this may be totally different from the numbers assigned during the original configuration of these devices. The problem is exacerbated by the fact that tty and lp devices attached to a ran are not renumbered during the mksysb, but are assigned based on the parent name (i.e. the RAN sa number).

Simple example.

One of the simplest examples of this problem is the case where you have only one 128-port adapter. When you start, you have only one RAN, and you place that RAN on line two of the adapter. The ran becomes SA3 because SA0, SA1, and SA2 are already used by the integrated serial ports on the H50. This ran will most likely have a node number of one, so the location for sa3 will be xx-yy-21. Sometime later, you have requirements for more users and add a new RAN, and to keep things optimal you add this ran on line 1. This new RAN becomes sa4 at location xx-yy-11. Of course we have already added tty and lp devices to the first RAN, and will add ones to this RAN. To keep this simple, lets just work with the two devices that are attached to port 0 on each ran. On the first RAN, you added an IBM3151 terminal on the first port of the ran, and on the later RAN, you added an Lexmark Optra printer on port 0. The device list now shows these devices as:

  tty0 Available 01-S1-00-00 Asynchronous Terminal

  tty1 Available 10-70-21-00 Asynchronous Terminal

  lp0 Available 10-70-11-00 Lexmark Optra laser printer

What happened during the mksysb restoration is that the RAN that was formerly known as sa4 was found earlier in the restoration process than the previous sa3. Since there are only two RAN's, the process is fairly simple: sa3 -> sa4 and sa4 -> sa3. Looking at a list of devices you now see:

  tty0 Available 01-S1-00-00 Asynchronous Terminal

  tty1 Available 10-70-11-00 Asynchronous Terminal

  lp0 Available 10-70-21-00 Lexmark Optra laser printer

Preventing mksysb problems.:

If there is no change in the RAN sa numbers, then there will be no problems with TTY or Printer devices. The goal in preventing mksysb problems is to start on day one of installation planning for the mksysb.

If you follow these rules, you should not have mksysb restoration problems with devices attached to 128-port adapters.

• Always put the first 128-port adapter in the lowest slot based on the "walk" the bus order for that RS/6000 model.
• Add subsequent adapters in the correct "walk the bus" order.
• Always add node 1 line 1 first, node 2 line 1 next, ...
• Complete adding nodes on line 1 before adding any nodes to line3.
• Add nodes in order to line 2 of the first adapter before adding any RAN's to the second adapter.
• Always fully populate each 128-port fully using the line 1 before line 2, and node 1, 2, 3, & 4 order before adding RAN's to a later 128-port adapter.
• Make sure all RAN's are on and connected before starting the mksysb restoration.

Collecting data prior to making a mksysb tape:

At the time that you create the mksysb tape, use a script to save information about all your 128-port related devices. The following script will save all the information you need to successfully restore your system.

#!/bin/ksh

# Get customized attributes (lsattr info)

# Useful for restoring devices

odmget -q "name like tty*" CuAt > CuAt.tty

odmget -q "name like lp*" CuAt > CuAt.lp

odmget -q "name like sa*" CuAt > CuAt.sa

odmget -q "name like cx*" CuAt > CuAt.cx

# Get Customized Device info.  Contains location and sa

# Useful for restoring devices

odmget -q "name like tty*" CuDv > CuDv.tty

odmget -q "name like lp*" CuDv > CuDv.lp

odmget -q "name like sa*" CuDv > CuDv.sa

odmget -q "name like cx*" CuDv > CuDv.cx

# Get customized driver info. Contains device minor number

# Useful for restoring devices

odmget -q "value3 like tty*" CuDvDr > CuDvDr.tty

odmget -q "value3 like lp*" CuDvDr > CuDvDr.lp

odmget -q "value3 like sa*" CuDvDr > CuDvDr.sa

odmget -q "value3 like cx*" CuDvDr > CuDvDr.cx

# Get device status info 

# Useful for determining which devices need modified.

lsdev -Cc tty -F"name status location parent description" > lsdev.tty

lsdev -Cc printer -F"name status location parent description" > lsdev.printer

lsdev -Cc adapter -F"name status location parent description" > lsdev.adapter

lsdev -Cc concentrator -F"name status location parent description" >  lsdev.concentrator

# Get dev directory info

# Show the major and minor numbers of devices

ls -l /dev/tty* > ls.tty

ls -l /dev/lp* > ls.lp

ls -l /dev/cx* > ls.cx

# Use snap to collect all async and printer information

snap -A

snap -p

# Move snap information to current directory

cp /tmp/ibmsupt/printer/*.snap .

cp /tmp/ibmsupt/async/*.snap .

Restoring devices using collected data.:

Collected post mksysb data.

Create a base directory for the restoration such as /tmp/128port. Change to this directory and create three subdirectories: pre, post, and working. Change to the pre directory and restore the data that you collected prior to creating the mksysb tape. Change to the post directory and run the get128.sh script to collect data after the mksysb restoration. Change to the working directory to evaluate the problem and begin the fix.

Evaluating the problem

To evaluate if there is a problem, and the extent of the problem you can look at devices in order from adapter to RAN to tty or printer.

The steps to evaluate the problem are:

• Check to see if the adapters remained in the same place.
• Check to see if the RAN sa numbers changed.
• Check to see if the printer and terminal locations changed.

Check to see if the adapters moved locations

It is not really important the the adapters keep the same device numbers. What we want to see here is if adapters have been moved to new slots. If they have not been moved, then we don't need to use the adapter information in restoring our terminal and printer devices.

To see if the adapters have moved check the differences in the device files saved from the pre and post installation. If the diff command shown below returns nothing or if the device numbers have not changed for the adapters, then you will have no problems. This is the typical case when you are restoring the mksysb on the same system that you made the tape from. For example:

# diff ../pre/lsdev.adapter ../post/lsdev.adapter | grep cx

> cxpa0   Available 10-70    IBM 128-Port Async (PCI) Adapter

< cxpa0   Available 10-70    IBM 128-Port Async (PCI) Adapter

> cxpa1   Available 30-60    IBM 128-Port Async (PCI) Adapter

< cxpa1   Available 30-60    IBM 128-Port Async (PCI) Adapter

# diff ../pre/lsdev.adapter ../post/lsdev.adapter | grep cx

new cxpa1   Available 10-70    IBM 128-Port Async (PCI) Adapter

old cxpa0   Available 10-70    IBM 128-Port Async (PCI) Adapter

new cxpa0   Available 10-60    IBM 128-Port Async (PCI) Adapter

old cxpa1   Available 30-60    IBM 128-Port Async (PCI) Adapter

Check to see if the RANs moved locations

The tty and printer assignments are based on the RAN sa number, and not on their original location. This means that if the RAN gets a new sa number that the tty and printer definitions will be associated with the RAN that gets the same sa number after the mksysb restore. To see if any RANs changed sa numbers use the diff command as shown in the following example:

# diff ../pre/lsdev.concentrator ../post/lsdev.concentrator

1,4c1,3

PRE

< sa3 Available 10-70-22 16-Port RAN EIA-232 for 128-Port Adapter

< sa4 Available 30-60-21 16-Port RAN EIA-232 for 128-Port Adapter

< sa5 Available 10-70-11 16-Port RAN EIA-232 for 128-Port Adapter

---

POST

> sa3 Available 10-70-11 16-Port RAN EIA-232 for 128-Port Adapter

> sa4 Available 10-70-22 16-Port RAN EIA-232 for 128-Port Adapter

> sa5 Available 30-60-21 16-Port RAN EIA-232 for 128-Port Adapter

Check to see if the tty/lp's moved locations

Based on what we learned about the RAN's, we can conclude that tty and lp devices will change locations. To confirm this, we can again use the diff command on our example files:

# diff ../pre/lsdev.tty ../post/lsdev.tty                  

< tty1 Available 10-70-22-00 Asynchronous Terminal

< tty2 Available 10-70-22-01 Asynchronous Terminal

< tty3 Available 10-70-22-02 Asynchronous Terminal

< tty4 Available 10-70-11-15 Asynchronous Terminal

< tty5 Available 10-70-11-00 Asynchronous Terminal

< tty6 Available 30-60-21-00 Asynchronous Terminal

< tty7 Available 30-60-21-08 Asynchronous Terminal

---

> tty1 Available 10-70-11-00 Asynchronous Terminal

> tty2 Available 10-70-11-01 Asynchronous Terminal

> tty3 Available 10-70-11-02 Asynchronous Terminal

> tty4 Available 30-60-21-15 Asynchronous Terminal

> tty5 Available 30-60-21-00 Asynchronous Terminal

> tty6 Available 10-70-22-00 Asynchronous Terminal

> tty7 Available 10-70-22-08 Asynchronous Terminal

and

# diff ../pre/lsdev.printer ../post/lsdev.printer

< lp0 Available 10-70-22-05 Lexmark 4039 plus LaserPrinter

< lp1 Available 30-60-21-04 IBM 4039 LaserPrinter

< lp2 Available 10-70-11-09 Lexmark Optra laser printer

---

> lp0 Available 10-70-11-05 Lexmark 4039 plus LaserPrinter

> lp1 Available 10-70-22-04 IBM 4039 LaserPrinter

> lp2 Available 30-60-21-09 Lexmark Optra laser printer

Example of restoring a single tty

Although it would be easier to just remove and read this one tty, I want to use it as an illustration of how the process can be automated for a group of TTY's. The keys to restoring a tty is to correct the odm entries in the customized databases. In the collection script, we gathered information from all of the associated customized data bases. In this section, we will look at the entries that we retrieved and see how we can use these to create a working TTY at the original location.

First find the location of the original tty7 from the pre lsdev.tty file.

 tty7 Available 30-60-21-08 sa4 Asynchronous Terminal

 sa5 Available 30-60-21 16-Port RAN EIA-232 for 128-Port Adapter

The following shows the information from this database as obtained from the pre and post directories and then shows the correct value for a new tty added at this location after the mksysb.

Pre mksysb	Post mksysb	Corrected for restore
CuDv: name = "tty7" status = 1 chgstatus = 1 ddins = "" location = "30-60-21-08" parent = "sa4" connwhere = "8" PdDvLn = "tty/rs232/tty"	CuDv: name = "tty7" status = 1 chgstatus = 1 ddins = "" location = "10-70-22-08" parent = "sa4" connwhere = "8" PdDvLn = "tty/rs232/tty"	CuDv: name = "tty7" status = 1 chgstatus = 1 ddins = "" location = "30-60-21-08" parent = "sa5" connwhere = "8" PdDvLn = "tty/rs232/tty"

CuDv:

        name = "tty7"

        status = 0

        chgstatus = 1

        ddins = ""

        location = "30-60-21-08"

        parent = "sa5"

        connwhere = "8"

        PdDvLn = "tty/rs232/tty"

Note: You do not need to fix this database because it is rebuilt by mkdev during the re-add of the tty. This information is only provided for your information, but is not needed for reinstalling the tty.

Again we can compare the entries from pre, post, and fixed for this tty7 example.

Pre mksysb	Post mksysb	Corrected for restore
CuDvDr: resource = "devno" value1 = "48" value2 = "328" value3 = "tty7"	CuDvDr: resource = "devno" value1 = "36" value2 = "88" value3 = "tty7"	CuDvDr: resource = "devno" value1 = "36" value2 = "328" value3 = "tty7"

Note: The value1 value or major number comes from the post file, and the value2 or minor number comes from the pre file.

Based on this we now have our second file or CuDvDr.tty7:

CuDvDr:

        resource = "devno"

        value1 = "36"

        value2 = "328"

        value3 = "tty7"

CuAt:

        name = "tty7"

        attribute = "login"

        value = "enable"

        type = "R"

        generic = "DU"

        rep = "sl"

        nls_index = 18

CuAt:

        name = "tty7"

        attribute = "term"

        value = "ibm3151"

        type = "R"

        generic = "DU"

        rep = "s"

        nls_index = 17

1. Remove the current tty7 definition from the database

2.   pdisable tty7
   

3.   rmdev -l tty7 -d
   

4. This removes all of the odm entries without doing a odmdelete. It also removes the special devices file /dev/tty7.
5. Make sure that there are no tty or lp devices at the new location in the CuDv.tty7 file.

6.   lsdev -Cc tty | grep 30-60-21-08
   

7.   lsdev -Cc printer | grep 30-60-21-08
   

8. Add the new tty7. This can be done with the "mkdev" command or by adding the corrected stanzas to the odm with the odmadd command.

9.   odmadd CuDv.tty7
   

10.   odmadd CuAt.tty7
    

11. Adding stanza's with the odmadd command can cause problems if you run the command twice or run the command while a device is still defined. For this reason, it is probably better to add the devices with the mkdev command. You will need the new parent, and the PdDvLn information for the mkdev command. The PdDvLn field of the odm provides the information for the -c -s and -t flags of the mkdev command.

12.         PdDvLn = "tty/rs232/tty"
    

13.         -c tty -s rs232 -t tty
    

14. The syntax of the mkdev command is:

15.   mkdev -l $tty -c $c1 -s $s1 -t $t1 -p $p1 -w $w1
    

    • The $tty parameter is replaced with the tty name.
    • The $cl parameter is the class from the PdDvLn field
    • The $s1 parameter is the subclass from the PdDvLn field
    • The $t1 parameter is the type from the PdDvLn field
    • The $p1 is the parent adapter (example: sa5)
    • The $w1 parameter is the port number on the RAN
16. Check to see that the new device has been added with lsdev

17.   lsdev -Cl tty7
    

18.   If you use odmadd:
    

19.   tty7 Defined 30-60-21-08 Asynchronous Terminal
    

20.   If you use mkdev
    

21.   tty7 Available 30-60-21-08 Asynchronous Terminal
    

22. Configure the device with mkdev to add the /dev/tty7 file, to change the status in the CuDv database, and to add an entry in the /etc/inittab file if you used odmadd

23.   mkdev -l tty7
    

24. Check to see if the device is now available, and try to log in to the tty.

25.   lsdev -Cl tty7
    

26.   tty7 Available 30-60-21-08 Asynchronous Terminal
    

27. If you used mkdev, then run a chdev for each device based on the CuAt attribute and value fileds.

28.   chdev -l $tty -a "attribute=value"
    

30.   Example:
    

31.   chdev -l tty4 -a "login=enable"
    

32.   chdev -l tty4 -a "term=ibm3151"
    

Automating the restoration.

Looking at the process in the previous example, you can easily come to the conclusion that it would be a lot easier to simply remove and re-add all the tty devices. In fact, this may be true, but keeping the tty's assigned to the right location would be an accounting nightmare. In this section, I will attempt to describe a solution that might help restore all of the tty and lp devices in a single step. This procedure assumes that you have not moved cables, and that all 128-port adapters are in the same slot as previous.

The steps in this automation are to:

1. Extract the odm information for only those devices into new working files.
   • The pre-mksysb information can be obtained from the mksysb tape
   • The post-reinstall information can be obtained directly from the system
2. Make sure the same number of RAN and 128-port adapters still exist.
3. Identify any 128-port adapter cards that have been changed location.
4. Identify any RAN that have changed locations.
5. Identify only the tty and lp devices that have change parent (sa) names.
6. Remove the old tty and lp devices that have changed names
7. Re-add the new tty and lp devices to the correct parent.
8. Re-add the old attributes to the tty and lp devices
9. Test the new devices.

Automation Script.

Click here to download the script as a tar file rebuild.tar.

This tar file contains two files:

• rebuild: This is the executable shell script.
• 128p_mksysb.txt: This is a text version of this document.

  tar xvf rebuild.tar

one assumptions made in this scripts:

• You don't add or remove 128-port cards or RAN during the migration.

Running the script

Before running the script, log in to tty's that you suspect problems from and type tty to determine the tty number. Once you have finished running the script, repeat this exercise to determine if you have the desired tty name.

The script can be run from any directory. Use something like /home/restore. Once you are done, you could then clean up everything with:

  rm -R /home/restore

  rm -R /tmp/etc

No tape write necessary

PRE-restore data already available

Do you want to refresh local settings? (y or n) 

In this example, I have already run the script before and so things are all cleaned up, but I want to run through the script again, so I will answer n. If this was the first time, it would have asked me to put the mksysb tape in the tape drive and hit enter. If no local data was collected, it would not prompt.

Ready to check for compatibility between 128-port adapters

and RAN before and after the mksysb tape restoration

Hit enter to continue: 

There are  2 adapters before and after the mksysb

There are  3 RAN before and after the mksysb

The number of RAN and adapters matches so we can continue

This section of the program makes sure we match

the 128-port concentrators from their pre mksysb

locations to their post mksysb locations

Press enter to continue. 

The previous section confirmed that there were no hardware changes to the system.

Now find matches between pre-mksysb and reinstall RANs

Example: location 10-60-21

The first four numbers "10-60" identify the 128-port adapter

The first digit of the last number identifies the line

The second digit of the last number is the ran node

Example 21 is line 2, node 1

If you are unsure of the locations of your cards, exit this

program (ctrl-C), and "cat ../pre/lsdev.concentrator" and 

"cat ../post/lsdev.concentrator" to understand the previous

and current assigned RAN locations

1: PRE: 30-60-21 not found on new configuration

        H50 30-60 card found at H70 40-60

        30-60-21 mapped to 40-60-21 

The script now looks at the locations of the RAN. In this case, there were no adapters at location 30-60, but it recognizes that there if this is a migration to an H70 that 40-60 is an equivalent adapter location. If the card was moved, it would have prompted for possible matches.

2: PRE: 10-70-22 not found on new configuration

        Card is at same address, Node has changed

        Map 10-70-22 to 10-70-21? (y or n) 

This second RAN was found to exist on the same card as previously, but during the rebuild the RAN node number changed from 2 to 1. This might be an indication that sometime previously a RAN was removed from the old configuration, or the node number got set wrong during installation. Again after looking at the files in ../pre and ../post, I respond with y to this question.

3: 10-70-11 matched 10-70-11

This is the more normal sequence where the RAN has maintained the same location, but simply changed names creating the problem.

RAN remap table

PRE: 30-60-21 mapped to NEW: 40-60-21

PRE: 10-70-22 mapped to NEW: 10-70-21

PRE: 10-70-11 stays at NEW: 10-70-11

Is this correct? (y or n) 

The script here shows you the re-assignments that will be made between the two systems. Since the information is correct, type y to continue. Typing n stops the script, letting you gather more information before running it again.

tty1:       PRE: 30-60-21-00 POST: 10-70-11-00 Moveto: 40-60-21-00

tty2:   PRE: 30-60-21-15 POST: 10-70-11-15 Moveto: 40-60-21-15

tty3:   Already at 10-70-21-00 on sa4

tty4:   Already at 10-70-21-15 on sa4

tty5:   PRE: 10-70-11-00 POST: 40-60-21-00 Moveto: 10-70-11-00

tty6:   PRE: 10-70-11-15 POST: 40-60-21-15 Moveto: 10-70-11-15

lp0:    PRE: 30-60-21-08 POST: 10-70-11-08 Moveto: 40-60-21-08

lp1:    Already at 10-70-21-09 on sa4

lp2:    PRE: 10-70-11-10 POST: 40-60-21-10 Moveto: 10-70-11-10

Press enter to continue 

The next output, shows which tty's will be moved during the rebuild process. In this case tty2, tty3, and lp1 are on the correct sa# and will not be removed and readded. tty1, tty2 and lp0 were on the ran in slot 6 on the H50 before migration, but are now assigned to the 128-port adapter in slot 4 of the H70. The process will move them back to the slot 6 adapter at location 40-60 after the rebuild.

tty5, tty6, and lp2 were moved from the adapter in slot-4 of the H50 to slot 6 on the H70, and will be moved back by the script to slot 4 of the H70.

After confirming this information is correct, press enter to continue. If the information is not correct, press ctrl-C to break out of the script, gather information and rerun the script.

Making sure devices are idle

/dev/tty1: 

pdisable tty1

/dev/tty2: 

pdisable tty2

/dev/tty5: 

pdisable tty5

/dev/tty6: 

pdisable tty6

/dev/lp0: 

/dev/lp2: 

All devices should now be disabled

Remove the tty and lp devices

Make sure that all TTY's in chtty.list have been removed

Check: tty1 Available 40-60-21-00 Asynchronous Terminal

Removing tty1

tty1  deleted

tty1 was removed successfully

Check: tty2 Available 40-60-21-15 Asynchronous Terminal

Removing tty2

tty2  deleted

tty2 was removed successfully

Check: tty5 Available 10-70-11-00 Asynchronous Terminal

Removing tty5

tty5  deleted

tty5 was removed successfully

Check: tty6 Available 10-70-11-15 Asynchronous Terminal

Removing tty6

tty6  deleted

tty6 was removed successfully

Check: lp0 Available 40-60-21-08 Lexmark 4039 plus LaserPrinter

Removing lp0

lp0  deleted

lp0 was removed successfully

Check: lp2 Available 10-70-11-10 IBM 4039 LaserPrinter

Removing lp2

lp2  deleted

lp2 was removed successfully

Ready to re-add the tty and lp devices that were removed

Press Enter when ready to continue

This shows that all the devices where removed successfully. If some of the devices were busy, you would have been asked to close the task, and press enter to continue. If you break out at this time from the script, you should answer n when asked to get new information from the system in the first stage of the script.

Configuring ttys

tty1 added successfully

Change is login=enable

tty1 changed

Change is term=ibm3151

tty1 changed

tty2 added successfully

Change is login=enable

tty2 changed

Change is term=ibm3151

tty2 changed

tty5 added successfully

Change is login=enable

tty5 changed

Change is term=ibm3151

tty5 changed

tty6 added successfully

Change is login=enable

tty6 changed

Change is term=ibm3151

tty6 changed

lp0 added successfully

lp2 added successfully

This shows that the tty and lp devices were re-added successfully.

Confirming devices that were readded are available

tty1 Available 40-60-21-00 Asynchronous Terminal

tty2 Available 40-60-21-15 Asynchronous Terminal

tty5 Available 10-70-11-00 Asynchronous Terminal

tty6 Available 10-70-11-15 Asynchronous Terminal

lp0 Available 40-60-21-08 Lexmark 4039 plus LaserPrinter

lp2 Available 10-70-11-10 IBM 4039 LaserPrinter

This shows that the devices are now available.

Look for errors in the rebuild.log shown here for this successful run.

There are  2 adapters before and after the mksysb

There are  3 RAN before and after the mksysb

tty1    PRE: 30-60-21-00 POST: 10-70-11-00 Moveto: 40-60-21-00

tty2    PRE: 30-60-21-15 POST: 10-70-11-15 Moveto: 40-60-21-15

tty3: No change required.

tty4: No change required.

tty5    PRE: 10-70-11-00 POST: 40-60-21-00 Moveto: 10-70-11-00

tty6    PRE: 10-70-11-15 POST: 40-60-21-15 Moveto: 10-70-11-15

lp0     PRE: 30-60-21-08 POST: 10-70-11-08 Moveto: 40-60-21-08

lp1: No change required.

lp2     PRE: 10-70-11-10 POST: 40-60-21-10 Moveto: 10-70-11-10

pdisable tty1

pdisable tty2

pdisable tty5

pdisable tty6

Removing tty1 with mkdev -l tty1 -d

tty1 was removed successfully

Removing tty2 with mkdev -l tty2 -d

tty2 was removed successfully

Removing tty5 with mkdev -l tty5 -d

tty5 was removed successfully

Removing tty6 with mkdev -l tty6 -d

tty6 was removed successfully

Removing lp0 with mkdev -l lp0 -d

lp0 was removed successfully

Removing lp2 with mkdev -l lp2 -d

lp2 was removed successfully

Configuring TTY's

tty1 added successfully

tty1 changed login=enable

tty1 changed term=ibm3151

tty2 added successfully

tty2 changed login=enable

tty2 changed term=ibm3151

tty5 added successfully

tty5 changed login=enable

tty5 changed term=ibm3151

tty6 added successfully

tty6 changed login=enable

tty6 changed term=ibm3151

lp0 added successfully

lp2 added successfully

The remap.list files shows the RAN mappings between systems:

30-60-21 40-60-21

10-70-22 10-70-21

10-70-11 10-70-11

The chtty.list file shows the tty's that were moved and the locations before and after the move.

tty1    tty tty rs232 30-60-21 from 10-70-11 to 40-60-21

tty2    tty tty rs232 30-60-21 from 10-70-11 to 40-60-21

tty5    tty tty rs232 10-70-11 from 40-60-21 to 10-70-11

tty6    tty tty rs232 10-70-11 from 40-60-21 to 10-70-11

lp0     printer lex4039+ rs232 30-60-21 from 10-70-11 to 40-60-21

lp2     printer ibm4039 rs232 10-70-11 from 40-60-21 to 10-70-11

Rerunning the script.

I moved the ../post directory information to save it and reran the script to see what new changes it would find.

No tape write necessary

PRErestore data already available

Restoring current ODM to ../post

tty1 Available 40-60-21-00 sa5 tty/rs232/tty

tty2 Available 40-60-21-15 sa5 tty/rs232/tty

tty3 Available 10-70-21-00 sa4 tty/rs232/tty

tty4 Available 10-70-21-15 sa4 tty/rs232/tty

tty5 Available 10-70-11-00 sa3 tty/rs232/tty

tty6 Available 10-70-11-15 sa3 tty/rs232/tty

lp0 Available 40-60-21-08 sa5 printer/rs232/lex4039+

lp1 Available 10-70-21-09 sa4 printer/rs232/lexOptra+

lp2 Available 10-70-11-10 sa3 printer/rs232/ibm4039

cxpa0 Available 10-70 pci0 adapter/pci/4f111b00

cxpa1 Available 40-60 pci3 adapter/pci/4f111b00

sa3 Available 10-70-11 cxpa0 concentrator/sync_pci/16c232

sa4 Available 10-70-21 cxpa0 concentrator/sync_pci/16c232

sa5 Available 40-60-21 cxpa1 concentrator/sync_pci/16c232

Ready to check for compatibility between 128-port adapters

and RAN before and after the mksysb tape restoration

Hit enter to continue: 

Notice that this shows information for all tty and lp devices on all 128-port adapters.

There are  2 adapters before and after the mksysb

There are  3 RAN before and after the mksysb

The number of RAN and adapters matches so we can continue

This section of the program makes sure we match

the 128-port concentrators from their pre mksysb

locations to their post mksysb locations

Press enter to continue. 

Now find matches between pre-mksysb and reinstall RANs

Example: location 10-60-21

The first four numbers "10-60" identify the 128-port adapter

The first digit of the last number identifies the line

The second digit of the last number is the ran node

Example 21 is line 2, node 1

If you are unsure of the locations of your cards, exit this

program (ctrl-C), and "cat ../pre/lsdev.concentrator" and 

"cat ../post/lsdev.concentrator" to understand the previous

and current assigned RAN locations

1: PRE: 30-60-21 not found on new configuration

        Card has moved

        Map 30-60-21 to 40-60-21? (y or n) y

2: PRE: 10-70-22 not found on new configuration

        Card is at same address, Node has changed

        Map 10-70-22 to 10-70-21? (y or n) y

3: 10-70-11 matched 10-70-11

RAN remap table

PRE: 30-60-21 mapped to NEW: 40-60-21

PRE: 10-70-22 mapped to NEW: 10-70-21

PRE: 10-70-11 stays at NEW: 10-70-11

Is this correct? (y or n) y

tty1:       Already at 40-60-21-00 on sa5

tty2:   Already at 40-60-21-15 on sa5

tty3:   Already at 10-70-21-00 on sa4

tty4:   Already at 10-70-21-15 on sa4

tty5: No change required.

tty6: No change required.

lp0:    Already at 40-60-21-08 on sa5

lp1:    Already at 10-70-21-09 on sa4

lp2: No change required.

Press enter to continue 

From this, you can see that I was still asked the questions, and could make new answers which would re-arrange the tty's again, but since they are in the right place, no new changes are made. The log this time shows:

There are  2 adapters before and after the mksysb

There are  3 RAN before and after the mksysb

tty1: No change required.

tty2: No change required.

tty3: No change required.

tty4: No change required.

tty5: No change required.

tty6: No change required.

lp0: No change required.

lp1: No change required.

lp2: No change required.

Remember to check the tty names on your terminals.

Restoring when no data was collected.

The script above collects data from the mksysb tape and the rebuilt system and requires no other data except a knowledge of the system.

Special Notices

This document was produced in the United States. IBM may not offer the products, programs, services or features discussed herein in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the products, programs, services, and features available in your area. Any reference to an IBM product, program, service or feature is not intended to state or imply that only IBM's product, program, service or feature may be used. Any functionally equivalent product, program, service or feature that does not infringe on any of IBM's intellectual property rights may be used instead of the IBM product, program, service or feature.

Information in this document concerning non-IBM products was obtained from the suppliers of these products, published announcement material or other publicly available sources. Sources for non-IBM list prices and performance numbers are taken from publicly available information including D.H. Brown, vendor announcements, vendor WWW Home Pages, SPEC Home Page, GPC (Graphics Processing Council) Home Page and TPC (Transaction Processing Performance Council) Home Page. IBM has not tested these products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. Send license inquires, in writing, to IBM Director of Licensing, IBM Corporation, New Castle Drive, Armonk, NY 10504-1785 USA.

All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only. Contact your local IBM office or IBM authorized reseller for the full text of a specific Statement of General Direction.

The information contained in this document has not been submitted to any formal IBM test and is distributed "AS IS". While each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. The use of this information or the implementation of any techniques described herein is a customer responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. Customers attempting to adapt these techniques to their own environments do so at their own risk.

The information contained in this document represents the current views of IBM on the issues discussed as of the date of publication. IBM cannot guarantee the accuracy of any information presented after the date of publication.

All prices shown are IBM's suggested list prices; dealer prices may vary.

IBM products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.

Any performance data contained in this document was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements quoted in this document may have been made on development-level systems. There is no guarantee these measurements will be the same on generally-available systems. Some measurements quoted in this document may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

The following terms are registered trademarks of International Business Machines Corporation in the United States and/or other countries: ADSTAR, AIX, AIX/6000, AS/400, C Set++, CICS, CICS/6000, DB2, ESCON, IBM, Information Warehouse, LANStreamer, LoadLeveler, Magstar, MediaStreamer, Micro Channel, MQSeries, Netfinity, Parallel Sysplex, POWERparallel, PowerPC (logo), RS/6000, S/390, Service Director, ThinkPad, TURBOWAYS, Videocharger, VisualAge. The following terms are trademarks of International Business Machines Corporation in the United States and/or other countries: AIX PVMe, AS/400e, DB2 Universal Database, Deep Blue, e-business (logo), HACMP/6000, Intelligent Miner, Intellistation, Network Station, POWER2 Architecture, PowerPC 604, PowerPC Architecture, SmoothStart, SP. A full list of U.S. trademarks owned by IBM may be found at www.ibm.com/legal/copy/trade.html.

Microsoft, Windows, Windows NT and the Windows 95 logo are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries or both. UNIX is a registered trademark of The Open Group. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States and other countries. Lotus, Lotus Domino and Lotus Notes are trademarks or registered trademarks of Lotus Development Corporation. Tivoli, TME, TME 10 and TME 10 Global Enterprise Manager are trademarks or registered trademarks of Tivoli Systems, Inc. Other company, product and service names, which may be denoted by a double asterisk (**), may be trademarks or service marks of others.

Index for H50 to H70 migration notes
Return to Terminal Tips Index non-frames
Return to Terminal Tips Index FRAMES
Tesch's Home with Frames