ITEM: E9753L

(GENERAL RAN 128-PORT ASYNC INFO)What does a p4 on a 16 port RAN mean?




Question:

AIX 3.2.4.  
Risc 320.  
16 port RAN.  

What does a p4 in the display mean?.  19.2 modem baud type.
The modem is not accessable from the adapter.  

Response:

Response:

REMOTE RAN CONFIGURATION AIDE

It is first possible that you have set up your SMIT screens incorrectly.
Here is some more detail on setting up through SMIT:

   1) At the command line, enter smit 128psync.
   2) Select Change/Show Characteristics of a 128-Port
      Async Adapter.
      The changeable parameters for the host adapter are:
       Line 1 (2) Speed    - Select the baud rate supported
                             by the synchronous modem and the
                             telephone line.
       Line 1 (2) Cable Type - Must be 8-Wire.
       Node 1 Comm Mode     - See NOTE and Chart below.

   3) Select Cconfigure Devices Added after IPL in smit, or
      enter the command, cfgmgr from the command line. This
      allows AIX to recognize the latest hardware change.

   ** NOTE **
      When configuring the host adapter for synchronous modem
      attachment of remote RANs, a "virtual" RAN must be
      configured for operation (232_modem or 422_modem) IF
      less than four RANs are connected on a host adapter line.

      During synchronous modem operations, transmit and receive
      clocks at both ends of the phone link control the precise
      timing of the data flow. When a RAN is connected to the
      host adapter locally (direct connect), the RAN uses an
      internally generated clock to transmit data.

      When a RAN is connected to the host adapter in a remote
      connection via synchronous modems, the transmitted data
      is exeternally clocked. In other words, the transmit clock
      must be supplied from a modem.

      The data flow return path to the host adapter (which is the
      last RAN's TX clocking) must also be external.

   ** TABLE **

      The '*' marks the "virtual RAN providing the external clocking
      (232_modem is used in this example).

      For One Remote Concentrator:

      Node 1 Comm Mode        232_modem    (external clocking)
    * Node 2 Comm Mode        232_modem    (external clocking)
      Node 3 Comm Mode        direct       (internal clocking)
      Node 4 Comm Mode        direct       (internal clocking)

      For Two Remote Concentrators:

      Node 1 Comm Mode        232_modem    (external clocking)
      Node 2 Comm Mode        direct       (internal clocking)
    * Node 3 Comm Mode        232_modem    (external clocking)
      Node 4 Comm Mode        direct       (internal clocking)

      For Three Remote Concentrators:

      Node 1 Comm Mode        232_modem    (external clocking)
      Node 2 Comm Mode        direct       (internal clocking)
      Node 3 Comm Mode        direct       (internal clocking)
    * Node 4 Comm Mode        232_modem    (external clocking)

      For Four Remote Concentrators:

      Node 1 Comm Mode        232_modem    (external clocking)
      Node 2 Comm Mode        direct       (internal clocking)
      Node 3 Comm Mode        direct       (internal clocking)
      Node 4 Comm Mode        direct       (internal clocking)

 Another are to look for possible problems is the modem configuration.
 DigiBoard has verified that these DSU's work with the default
 sittings BUT some of the modems are shipped with incorrect jumpers
 set in the DSU. Refer to your owners manual for the jumpers that
 refer to "grounding signals". Signals inside the DSU must be grounded
 and some DSU are shipped with these jumpers set so that grounding is
 not done.

 Make sure the Host side DSU is set for external clocking and the
 remote DSU is set for repeator. Besides making sure the jumpers
 are correct and setting Sync, 232, and baud it should work! For
 future reference I'll append a list of modems that DigiBoard
 has verified (either by testing themselves or by customers).

 Here is some more information on RAN diags and display numbers:

                    RAN DIAGS
    To run the internal diagnostics programs from the
    RAN front panel, turn the RAN off and disconnect
    it and any other RAN's to be tested from the host
    adapter. Install a terminator plug on the RAN's
    'OUT/T' connector, press and hold the right arrow
    button while turning the power back on and wait for
    the POST (Power On Self Test) to complete. When 'P0'
    is displayed on the front panel and the 10 LEDs
    (TD thru IFC) are clear, release the right arrow
    button. If any of the LEDs stay on after the self
    test completes refer to 'P0' LED discussion below
    to determine the error detected.

    Once the diagnostic mode has been entered, pressing
    the right arrow button repeatedly will cycle through
    all of the test numbers without executing the tests.
    To execute a test, press the left arrow button while
    the desired test number is displayed. The left-hand
    decimal point of the 7-segment display will be turned
    on to indicate that a test is in progress.

    To stop running a test in progress, push the left arrow
    button for approximately 1 second (or until the left-hand
    decimal point in the 7-segment display goes off). The
    test will terminate, and the 7-segment display will show
    the test number preceded by 'P' (pass) or 'F' (fail).

    To exit diagnostic test mode and return to the initialized
    state ('P1' displayed), run Test 9, the Watchdog Timer test.
    This test ends by resetting the RAN and running the POST
    sequence.

    Since it appears you are failing test 8 (EEPROM) you
    should run this test. If this test fails and a service
    call is made. I would like to know the QSAR number for
    this concentrator so that we can track it through the
    IBM channels and get it back to DigiBoard. We have not
    seen this problem before on the IBM product line and
    would be very interested in it. The QSAR number is
    assigned by the service guy when he replaces the bad
    concentrator I think.

    What is En?  I'll just go thru them all so that you can
    teach the world.

    'P0'  -  Power-On self test. During this phase the modem
             signals (TD thru IFC) will come on starting with
             TD. Each one corresponds to a particular test(s)
             that has completed:
               TD - Clear interrupts, Enable upper memory - EPROM
                    (16K), set peripheral chip select base address
                    & PCS 0-3, Enable lower memory - 128K DRAM,
                    Enable mid-range memory base address - EEPROM,
                    Set mid-range memory size & PCS 4-6, Processor
                    flag & register tests, Set enhanced mode for
                    the 80186, Perform LED & 7 segment display test,
                    display 'P0'.
               RD - Test 64K DRAM from 00000H - 0FFFFH
              RTS - Test 64K DRAM from 10000H - 1FFFFH
              CTS - Set BIOS stack @ 1FC00H, Transfer interrupt
                    vectors from EPROM to DRAM, Mask all H/W
                    interrupts OFF, STI - Enable interrupts,
                    Real time clock is started.
              DSR - Test the 16 async ports in internal loopback.
              DCD - Test the sync port in internal loopback (422).
              DTR - Test the sync port in internal loopback (232).
               RI - EFC sync & async configuration is set, Sync
                    port is initialized for download.
              OFC - EEPROM read, checksum, & node test performed.
              IFC - EPROM data gets moved to DRAM data segment,
                    EPROM checksum is performed (VPD not included).

          If any of the test fail and are considered 'FATAL' by
          the BIOS, the LED will display 'Ed' (FATAL POST Error
          Diagnostic). The following Modem signals will come on
          based on the test failure detected:
               RD - Lower 64K RAM memory error (00000H - 0FFFFH)
              RTS - Upper 64K RAM memory error (10000H - 1FFFFH)
              DCD - Sync RS-422/DMA test failure.

          If any of the test fail and are considered 'NON FATAL' by
          the BIOS, the LED will display 'P1' (Ping Packet). The
          following Modem signals will come on based on the test
          failure detected:
              DTR - Internal loopback mode (232).
              RI  - Sync port initialization.
              OFC - EEPROM read, checksum, & node test performed.

          If there were no 'FATAL' errors, the POST diagnostics will
          automatically proceed to the command mode 'P1' and wait
          for sync packets from a Host Adapter Card or an operator
          entry to select user diagnostics. After the 1 second delay
          at the end of the POST diagnostics sequence, the display
          will change from 'P0' to 'P1' and 3 LEDs (DTR/RI/OFC) will
          begin cycling at a 200 ms rate as the command mode begins
          listening for synchronous packets in three different modes.
          Non-fatal errors will be displayed via the assigned LED
          discussed above.


    'P1'  -  Ping packet mode. Power on self test is complete,
             relays are open and waiting for some to talk to this
             RAN.

    'P2'  -  RAN has received a Ping packet from the host. This
             means that the host has succesfully transmitted a
             Ping packet to this RAN. This Ping packet carries
             the information that tells the RAN how to configure
             itself, such as baudrate, 422/232, etc..

    'P3'  -  This is NOT displayed on the LED's. Then the RAN
             transmits a packet that contains the RAN's
             physical characteristics for the host to determine
             which download image to send it. The RAN has no
             knowledge as to whether or not the packet was
             successfully received by the host.

    'P4'  -  Download image is being received from the host. The
             RAN will normally stay at 'P4' for a length of time,
             depending on the synchronous baud rate being used.

    'En'  -  Error Node. A valid Ping Packet was received but the
             node number in EEPROM is incorrect.

    'AC'  -  ACtivity. "AC" appears in the display window. The
             ten LEDs (TD thru IFC) turn on sequentially from
             left to right. The speed of this "chase light" display
             increases with the overall activity level of the RAN.

    '0-15' -  Modes 0  through 15 correspond to ports 0 through 15.
              Press the right or left buttons until the desired port
              number appears in the display window. The LEDs now
              become a "line monitor" for the selected port. The
              first eight LEDs indicators show the activity of each
              of the eight RS-232 signals (TD, RD, RTS, CTS, DSR, DCD,
              DTR, and RI) . The last two LED indicators show when
              output flow control (OFC) and input flow control (IFC)
              are active.

    'PC'  - Packet Count. "PC" appears in the display window, and the
            ten LEDs show a binary representation of total number of
            packets transmitted or received. Pressing both arrow
            buttons simultaneously resets the count to 0.

    'EC'  - Error Count. "EC" appears in the display window, and the
            ten LEDs show a binary representation of the total number
            of errors counted in the data. Pressing both arrow buttons
            simultaneously resets the count to 0.

    'PU'  - Process Utilization. "PU" appears in the display window,
            and the ten LEDs become a bar graph indicating the
            percentage (0 - 100%) of the time the RAN's microprocessor
            is being used.

    'LU'  - Line Utilization. "LU" appears in the display window, and
            the ten LEDs become a bar graph indicating the percentage
            (0 - 100%) of the time the synchronous communications line
            is being used.

    '1n,2n,...8n'  Node Number. The display window shows the node
            number of the RAN. The ten LEDs behave as in "AC" mode.
            The node numbers of the RANs in a daisy-chain must be
            assigned in ascending order, from the RAN closest to the
            host adapter, to the last RAN in the chain. Valid
            node numbers are one (1) through four (4). With 5-8
            reserved for future use.

         Troubleshooting Tips
         ---------------------

  Symptom: RAN displays 'P1' with DTR, RI and OFC LEDs scrolling.

  Solution: Normal "waiting" mode of RAN, meaning there is no
            communications from the host to the remote RAN. If
            both modems are communicating, test the RANs synchronous
            ports. Disconnect the RAN from the modem, connect the
            standard daisy-chain cable between the RAN's "IN" port
            and its "OUT/T" port. Run Diagnostic Test 6 (RS-422) or
            Test 7 (RS-232) to test the sync ports on the RAN.

   Symptom: RAN displays (and stays at) 'P2'.

   Solution: The remote RAN has received a packet of data from the
             host adapter. A data packet was sent back to the host
             adapter but is not being received by the host. Make
             sure the last remote RAN is terminated. Check the
             configuration of Nodes in SMIT. Check node number assigned
             to the RAN. Run Diagnostic Test 6 (or 7) to test the
             sync ports on the RAN.

    Symptom: RAN scrolls between 'P2' and 'P4'.

    Solution: The RAN is attempting to execute the code downloaded to
              the box, but the data may be corrupt. The 'P2' is another
              attempt to send a packet to the host. This action may be
              caused by a poor phone connection or the modems may be
              improperly set-up. Check modem cabling. Make sure modems
              are set for 'external' clocking.

    Symptom:  RAN displays (and stays at) 'P4'.

    Solution:  The RAN will normally stay at 'P4' for a length of time,
               depending on the synchronous baud rate being used, and
               the number of concentrators at the remote site. If full
               acknowledgement is not achieved within the built-in
               timeout period (approx. one minute), the remote RAN
               will switch to a 'defined' state. Check the status of
               the 'SA' devices in SMIT, which must be 'available'.

Another thing to note is in some instances a "modified" NE cable works.
This cable is documented below:

  Cable NE:  128-Port Async Controller EIA-232 Modem Cable, System.

  System End      Modem End
  Connector       Connector
(15-pin Male)   (25-pin Male)

  1   RxD         RxD     3
  4   RxC         RxC    17
  6   TxD         TxD     2
  9   TxC         TxC    15
  12  Signal      Signal  7
      Ground      Ground
Shell Shield      Shield  1
      Ground      Ground
  13  +5V         RTS,DTR 4,20

  Cable NF:  128-Port Async Controller EIA-232 Modem Cable, Device.

  Modem End      System End
  Connector      Connector
(25-pin Male)  (15-pin Female)

  3     RxD      RxD      6
  17    RxC      RxC      9
  2     TxD      TxD      1
  15    TxC      TxC      4
  7     Signal   Signal  12
        Ground   Ground
  1     Shield   Shield  Shell
        Ground   Ground
  4,20  RTS,DTR  +5V     13


Support Line: (GENERAL RAN 128-PORT ASYNC INFO)What does a p4 on a 16 port RAN mean? ITEM: E9753L
Dated: February 1994 Category: N/A
This HTML file was generated 99/06/24~13:30:52
Comments or suggestions? Contact us