RSA Authentication Manager 7.1 Installation and Configuration Guide

More documents

Recommendations

Info

RSA Authentication Manager 7.1 Installation and Configuration Guide Important: During the installation process, an internal RADIUS account is created. This account is used internally and does not require direct interaction. The account name and password must never expire in order for Authentication Manager to function properly. The account name begins with “Radius,” for example, Radiuss9YmgxlA. Ensure that this account is not restricted by any network policies that might cause it to expire. Before you install a replica instance, do the following: 1. Ensure that the clock on the replica host is synchronized with the clock on the primary instance host. 2. Copy the license files to the replica host so that the license files are available locally. 3. On the primary instance, create a replica package file using the Operations Console. You may also need to create a primary data .dmp file if you want to copy the primary database to the replica manually. For instructions, see the following section, “Generating a Replica Package File.” Important: Do not rename either the replica package .pkg file or the primary data .dmp file. You cannot install a replica instance if you rename these files. 4. Copy the replica package file, and, if you are doing a manual data transfer, the primary data .dmp file from the primary instance to the replica host. Each package file is unique, functioning properly only on the host specified during its creation. For instructions, see “Transferring the Replica Package File” on page 49. 5. Confirm that the following ports are opened or closed, as described. Port/Type 1812/TCP 1813/TCP 2334/TCP 5500/UDP 7002/TCP 7004/TCP Function Open for SNMP and CCM/replication communication Open for RADIUS administration, if RADIUS is installed Open for Oracle communication • Open when RADIUS is installed • Close when RADIUS is not installed Open for the Authentication Manager adjudicator Open for administration communication between the Authentication Manager primary instance and replica instance when they are in different geographical locations. 6. (Optional) Change the limits for allocated disk space or number of days for logging. Do this when your physical disk space is less than 100 GB to avoid running out of disk space. For more information and instructions, see “Changing the Default Limits for Logging” on page 54. 46 4: Installing a Replica Instance
RSA Authentication Manager 7.1 Installation and Configuration Guide Installing a Replica Instance The following table provides a high-level overview of the tasks you must perform to install a replica instance. Task Reference 1. Install the primary instance. Chapter 3, “Installing an RSA Authentication Manager Primary Instance” 2. Using the primary instance Operations Console, generate a replica package file for the replica instance. You will be asked to provide the fully qualified hostname, IP address, and master password of the primary instance. The following section, “Generating a Replica Package File” 3. Transfer the replica package file to the replica host. “Transferring the Replica Package File” on page 49 4. Optional. Using the primary instance Operations Console, generate a primary instance data .dmp file. Note: You cannot generate a primary instance data .dmp file without also generating a replica package file. The following section, “Generating a Replica Package File” 5. Transfer the primary data .dmp file to the replica host. “Transferring the Replica Package File” on page 49 6. Install a replica instance. “Installing the Replica Instance” on page 49 7. Using the replica instance Operations Console, attach the replica instance to the primary instance. “Attaching the Replica Instance” on page 52 Generating a Replica Package File When you install an Authentication Manager replica instance, you must provide a replica package file and, if you are doing a manual data transfer, the primary data .dmp file. Replica package file. A.pkg file containing information about the Authentication Manager primary instance that enables replication from the primary to the replica instances. Primary data file. A.dmp file containing a copy of the data in the primary database. The data from the primary database must be copied to the replica database when a replica instance is first installed. Use the RSA Operations Console on the Authentication Manager primary instance to generate the replica package file and, if you are doing a manual data transfer, the primary data .dmp file. 4: Installing a Replica Instance 47
Page 1 and 2: RSA Authentication Manager 7.1 Inst
Page 7: RSA Authentication Manager 7.1 Inst
Page 97 and 98:
RSA Authentication Manager 7.1 Inst
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117:
Page 120 and 121:
Page 122 and 123:
Page 125 and 126:
Page 127 and 128:
Page 129:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203:
show all

RSA Authentication Manager 7.1 Installation and Configuration Guide

Create successful ePaper yourself

Delete template?

Save as template?