IBM 3745 Series, Hardware Maintenance Reference

Page: 419 / 712

3. The exact layout depends on the BER type and BER ID (see the BER formats
description at the end of each BER type xx section).
┌─────────┬──────┬──────┬──────┬──────┬──────┬──────┬──────┐
│ Byte
│ 21 │ 22 │ 23 │ 24 │ 25 │ 26 │ 27 │
├─────────┼──────┼──────┼──────┼──────┼──────┼──────┼──────┤
│ Contents│ ðð
│ ðð │ F5 │ 8F │ 12 │ 21 │ 87 │
├─────────┼──────┴──────┴──────┴──────┼──────┼──────┼──────┤
│ Meaning │ One bit = 1 sec
│ Dec │ 21st │ 87 │
│ │ 62 863 sec = 17h 27m 43s │ │ │ │
└─────────┴───────────────────────────┴──────┴──────┴──────┘
Figure 11-2. Example of Date and Time
NCP/PEP BER Formats Versus MOSS BER Formats: The following chart
explains why the BER formats and contents of NCP/PEP-generated records are dif-
ferent from the MOSS-generated records.
┌─────────────┐
┌─────────┤ 3745 ├─────────┐
│ └─────────────┘ │
6 6
┌──────────────────┐ ┌───────────────────┐
│ MOSS + POWER │ │ CCU + ADAPTERS │
└────────┬─────────┘ └─────────┬─────────┘
6 6
┌──────────────────────────────┐ ┌──────────────────────────────────┐
│ BERs are built by MOSS
│ │ BERs are built by NCP/PEP and │
│ and kept internally │ │ passed to MOSS for recording │
├──────────────────────────────┤ ├──────────────────────────────────┤
│ BER characteristics:
│ │ BER characteristics: │
│ - Structure │ │ - Structure │
│ - Thresholds │ │ - Thresholds │
│ │ │ │
│ are common to MOSS processor │ │ are common for all BERs under │
│ I/Os and to the power sub- │ │ NCP/PEP control. │
│ system. │ │ │
├──────────────────────────────┤ ├──────────────────────────────────┤
│ When
the CCU or NCP/PEP are │ │ When MOSS or the MOSS/CCU │
│ down, MOSS takes the control │ │ interface are down, NCP/PEP │
│ and creates corresponding │ │ records the error as BERs and │
│ BERs. │ │ keeps in its CRP. │
│ (BER type ð1 ID ð1 ERR ð5/ð7 │ │ (BER type ð1 IDs 91, B3, C1, C2 │
│ are the only non-MOSS/POWER │ │ are the only MOSS area BERs │
│ area BERs generated by MOSS) │ │ generated by NCP/PEP) │
├──────────────────────────────┤ ├──────────────────────────────────┤
│
│ │ │
│ Diagnosis is done while MOSS │ │ Diagnosis using BERs can be │
│ is offline. Diagnostics are │ │ done online (Autober). │
│ run by the MOSS IML sequence │ │ The CCU/adapters diagnostics run │
│ (No customer impact)
│ │ offline. │
│ │ │ │
└─────────────┬────────────────┘ └─────────────────┬────────────────┘
│ │
│ │
│ │
│ │
│ ┌────────────────────┐ │
└──────5│ FRU exchange is │%──────┘
│ power ON for LICs │
└────────────────────┘
Figure 11-3. BER Formatting by MOSS and NCP/PEP
BER Storage on Disk
The MOSS stores the BERs, prepared in the MOSS RAM, on the wraparound
BER file on disk in the order of their arrival.
Chapter 11. Error Logging
11-7