About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Troubleshooting
Problem
This document lists the necessary steps to add a system to a BRMS network, remove a system from a BRMS network, or rename a BRMS system.
Resolving The Problem
Adding a System to a BRMS Network
This example shows how to establish a BRMS network between two IBM System i systems, SYSTEM01 and SYSTEM02. For best results, follow the steps in the order in which they appear, and complete each step before moving on to the next. Ensure that all of the steps are completed when setting up your network. Do the following:
Notes:
Note: When you remove a system from the network, and you want to keep the active volumes created on that system you need to make sure that the media information present on the removed system is moved to target system as well.
These are some options:
1) If system had Receive media info set to *LIB, they should remove it using *RENAME option
2) If system had Receive media info set to *NONE they can use these steps:
A. On the source system, save QUSRBRM/QA1AHS file.
B. On the target system, restore QUSRBRM/QA1AHS saved in Step A to a different library.
C. On the target system, run the following commands
INZBRM OPTION(*MERGE) FROMLIB(OLDLIB) TOLIB(QUSRBRM) MERGE(*HST) where OLDLIB is the library where QUSRBRM/QA1AHS was restored to in Step B.
D. On the target system, rename media information just restored
INZBRM OPTION(*CHGSYSNAM) PRVSYSNAM(old_LCLNETID.old_LCLLOCNAME) NEWSYSNAM(*LCL)
This example shows how to establish a BRMS network between two IBM System i systems, SYSTEM01 and SYSTEM02. For best results, follow the steps in the order in which they appear, and complete each step before moving on to the next. Ensure that all of the steps are completed when setting up your network. Do the following:
| 1. | Save library QUSRBRM on all SYSTEM01. |
| 2. | Save library QUSRBRM on SYSTEM02. |
| 3. | Ensure that the communications link on SYSTEM01 for SYSTEM02 is active. |
| 4. | Perform the following: For TCP/IP - Use the WRKTCPSTS OPTION(*IFC) command to determine the status of the TCP/IP interfaces. For APPC - Use the WRKCFGSTS command to determine the status for line (*LIN), controller (*CTL), and device description (*DEV). |
| 5. | Designate SYSTEM01 to be your master system. Note: Once two or more systems are in a BRMS network, there is no longer the concept of a master system. The BRMS network is now a PEER network. |
| 6. | Ensure there is no BRMS activity on either system. |
| 7. | On SYSTEM01, run the WRKPCYBRM *SYS command to get to the system policy menu. Once there, do the following: a Select Option 4 (Change Network Group), and press the Enter key. b If you are using TCP/IP to communicate with other systems in the network change the Enable for TCP/IP field from *NO to *YES (R540 and below) or Communication method to *IP or *AVAIL (R610 and above). c To add SYSTEM02 to the master system to create the network, type SYSTEM02 in the Remote location field. Then, type the name of the remote network in the Remote Network ID column, and press the Enter key. BRMS searches the network for the specified system name. When BRMS finds the system name (in our example, SYSTEM02), BRMS adds it to *MEDINV (the BRMS network group name). SYSTEM02 is still an inactive member of the network group. |
| 8. | Note: Step 8 is not required if the system you want to add to the network does not contain media information (no BRMS activity has occurred on the system). On SYSTEM02, use the Work with Media (WRKMEDBRM) command to determine if any media information exists. If media information does not exist, go to Step 9. Because BRMS is fully operational, media information exists on SYSTEM02. To copy the media information from the SYSTEM02, run the following command, and press the Enter key: CPYMEDIBRM OPTION(*TOFILE) |
| 9. | Activate SYSTEM01 in the BRMS network with SYSTEM02. On SYSTEM02, run the following command: INZBRM OPTION(*NETSYS) FROMSYS(APPN.SYSTEM01) |
| 10. | Select an I for each of these messages received: Entries exist for Media. (R I C) Entries exist for Media policy. (R I C) Entries exist for Media class. (R I C) Entries exist for Location. (R I C) Entries exist for Move policy. (R I C) |
| 11. | If the CPYMEDIBRM OPTION(*TOFILE) was run in Step 8, run a CPYMEDIBRM OPTION(*FROMFILE) on SYSTEM02 now. |
| 12. | To add additional systems repeat Steps 2 through 11 for each additional system. |
Notes:
| 1. | If adding multiple systems to a BRMS network, follow the above steps one time for each system, BRMS will propagate all information to other systems already in the BRMS network. |
| 2. | Add only one system at a time. Complete all steps before starting on the next system. |
| 3. | Once Step 11 is complete, there is no longer the concept of a master system. BRMS runs in a peer system environment indicating that movement and adding media can be run on any system. (refer to the BRMS manual SC41-5345 for more information on BRMS networking and how it works). Always run maintenance on each system. |
| 4. | If a system is already in a BRMS network, it must be removed from the existing BRMS network before it can be added to another BRMS network. (See section on removing a system from a BRMS network). |
| 5. | Ensure all required RDB directory entries exist and are correct: BRMS Networking: Relational Database Directory Entries |
| 6. | If using TCP/IP, refer to the BRMS website: TCPIP Networking |
| 7. | When using TCP/IP for BRMS networking, all systems in the BRMS network have to be able to PING all other systems by name (or BRMS name, if used). |
| 8. | When adding a system to a BRMS network, if the Receive Media Info parameter in the system policy is set to *LIB, it will be changed back to *NONE when the INZBRM *NETSYS is run. This is because BRMS gets the info from the system specified in the FROMSYS parameter and it would be set to *NONE. Because of this, saved history from the other system(s) is not copied over to the new system being added. Saved history from the other systems in the BRMS network will only be synched to the new system from the time it is added onwards once Receive Media Info changed to *LIB. To sync the saved history information, users can follow document Adding Saved History to a System That Has Just Been Added to a BRMS Network: |
Removing a System from a BRMS Network
This example shows how to remove a system from a BRMS network. For this example, we have servers SYSTEM01, SYSTEM02, SYSTEM03, and SYSTEM04. In this example, SYSTEM03 is removed from the BRMS network. For best results, follow the steps in the order in which they appear, and complete each step before moving on to the next. Perform all of the steps when removing a system from the BRMS network.
Note: It is recommended that only one system is removed at a time. Complete the following steps for one system before removing the next system.
This example shows how to remove a system from a BRMS network. For this example, we have servers SYSTEM01, SYSTEM02, SYSTEM03, and SYSTEM04. In this example, SYSTEM03 is removed from the BRMS network. For best results, follow the steps in the order in which they appear, and complete each step before moving on to the next. Perform all of the steps when removing a system from the BRMS network.
Note: It is recommended that only one system is removed at a time. Complete the following steps for one system before removing the next system.
| 1. | Save QUSRBRM on SYSTEM03. |
| 2. | On SYSTEM03, run the WRKPCYBRM *SYS command to get to the system policy menu. Once there, do the following: a Select Option 4 (Change Network Group), and press the Enter key. b Type 4 next to all systems listed at the same time, and press the Enter key. c On the next screen , select *YES for Remove media information. Press the Enter key. |
| 3. | Depending on what you want to happen to the media owned by SYSTEM03, depends on which system you do this step on. A. For another system to take ownership of the media currently owned by SYSTEM03, do the following on that system: a Type the WRKPCYBRM *SYS command to get to the system policy. b Select Option 4 (Change Network Group), and press the Enter key. c Select Option 4 on SYSTEM03, and press the Enter key. d Change Remove Media information to *RENAME, and press the Enter key. B. If you do not want any system remaining in the BRMS network to take ownership of the media currently owned by SYSTEM03, do the following on any one of the other systems: a Type the WRKPCYBRM *SYS command to get to the system policy. b Select Option 4 (Change Network Group), and press the Enter key. c Select Option 4 on SYSTEM03, and press the Enter key. d Change Remove Media information to *YES, and press the Enter key. |
SYSTEM03 has now been removed from the BRMS network.
Renaming a BRMS System or setting a BRMS name
In order to define BRMS media ownership, you can use a BRMS user defined name or Network attributes - Network ID (NETID) and Default local location name (LCLLOCNAME).
If you are changing the BRMS user defined name or the network attributes, this change will affect BRMS.
| 1. |
If a system is in a BRMS network, first follow the Steps to 1, 2 and 3 B) in the process on Removing a System from a BRMS Network
|
| 2. | A. change the BRMS user defined name (if there is one). Procedure to Use a BRMS System Name is documented in Using a BRMS User-Defined System Name in a High Availability Environment
or
B. if using Network attributes, run CHGNETA to make necessary changes to information.
Note: If the local system name is changed during CHGNETA then an IPL is required to implement that change. It is preferred that IPL be performed before proceeding with the command below to rename the media.
|
| 3. |
A. INZBRM OPTION(*CHGSYSNAM) PRVSYSNAM(oldBRMSname) NEWSYSNAM(newBRMSname)
or
B. INZBRM OPTION(*CHGSYSNAM) PRVSYSNAM(NETID.OLSSYSNAME) NEWSYSNAM(*LCL)
|
| 4. |
If the system was in a BRMS network, add it back following the process in Adding a System to a BRMS Network
|
Note: If the network attributes have already being changed while the system was in an active BRMS network, the following additional steps must be taken:
| 1. | Type WRKPCYBRM *SYS to get to the system policy. |
| 2. | Select Option 4 (Change Network Group), and press the Enter key. |
| 3. | Select Option 4 on OLDSYSNAME, and press the Enter key. Important Note: Do this on only one system at this time. |
| 4. | Change Remove Media information to *RENAME, and press the Enter key. |
| 5. | Follow the section above - Removing a System from a BRMS Network |
| 6. | Follow the section above - Adding a System to a BRMS Network if wanting to have the system in a BRMS network |
Note: When you remove a system from the network, and you want to keep the active volumes created on that system you need to make sure that the media information present on the removed system is moved to target system as well.
These are some options:
1) If system had Receive media info set to *LIB, they should remove it using *RENAME option
2) If system had Receive media info set to *NONE they can use these steps:
A. On the source system, save QUSRBRM/QA1AHS file.
B. On the target system, restore QUSRBRM/QA1AHS saved in Step A to a different library.
C. On the target system, run the following commands
INZBRM OPTION(*MERGE) FROMLIB(OLDLIB) TOLIB(QUSRBRM) MERGE(*HST) where OLDLIB is the library where QUSRBRM/QA1AHS was restored to in Step B.
D. On the target system, rename media information just restored
INZBRM OPTION(*CHGSYSNAM) PRVSYSNAM(old_LCLNETID.old_LCLLOCNAME) NEWSYSNAM(*LCL)
Additional information about BRMS network can be found on the BRMS wiki
BRMS Networking Videos
We have created two videos that show how to prepare partitions for BRMS Networking and add them to a BRMS network.
Part 1: System Preparation
We have created two videos that show how to prepare partitions for BRMS Networking and add them to a BRMS network.
Part 1: System Preparation
Part 2: Adding Partitions
[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CKTAA2","label":"Backup Recovery Install Migration-\u003EBRMS"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]
Historical Number
361619501
Was this topic helpful?
Document Information
More support for:
IBM i
Component:
Backup Recovery Install Migration->BRMS
Software version:
All Versions
Operating system(s):
IBM i
Document number:
643923
Modified date:
15 November 2024
UID
nas8N1019155
Manage My Notification Subscriptions