Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cdb30a7c, userName='null'}
JIRAIDAUTHDSC-15936
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c85e00fa, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc1e0747, userName='null'}
JIRAIDAPPR2DSC-16294
REV3UserResourceIdentifier{userKey=8a00a0c85fd202bb01600fc680190023, userName='null'}
JIRAIDAPPRDSC-16946
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ced60ca3, userName='null'}

Consider the following before replacing an AMC121 CPU:

  • The new AMC121 CPU, which will be used for replacing the failed AMC121 CPU in the
    Spacevars
    0series5
     system, must contain a working OS version and a working software version.
  • The functional AMC121 CPU in the

    Spacevars
    0series5
     system is called the working AMC121 CPU.

    Info
    titleNote

    In the following examples, the failed AMC121 CPU is in slot 24 (Carrier blade 2, bay 4) and the working AMC121 CPU is in slot 14 (Carrier blade 1, bay 4).


    • The working AMC121 CPU is accessed using SSH from the customer OAM workstation.
    • The failed or new AMC121 CPU is accessed using SSH from the working AMC121 CPU (or NDM) using the internal IP address.
             

    • A USB key with a minimum of 1GB capacity is required for the
      Spacevars
      0series5
       USB key backup portion of this procedure. The USB key must also be formatted as "W95 FAT32" filesystem.

...