HP OpenVMS Systems

DECnet circuit On-Synchronizing?

» close window

The Question is:

 
 We are exepriencing some Decnet problems with one of our systems.
  One of the circuits is in "synchronizing" substate as the following
  command shwos it:
  NCP>sh circ ewa-0 charac
 
 
  Circuit Volatile Characteristics as of 29-JAN-1999 19:52:08
 
  Circuit = EWA-0
 
  State                    = on
  Substate                 = -synchronizing
  Service                  = disabled
  Cost                     = 4
  Maximum routers allowed  = 33
  Router priority          = 64
  Hello timer              = 15
  Type                     = Ethernet
We determined that is not a routing problem.
  Does someone have any sugestions how can we get rid of the
  "synchronizing" substate of this circuit?
  Thank you for your time! Have a good day!
  Monica Todirita
 

The Answer is :

 
  This could be anything from an OpenVMS problem to an Ethernet controller
  problem to a network cabling problem -- more commonly than not, either
  the Ethernet cabling or the Ethernet controller hardware is at fault,
  something preventing the node from contacting an adjacent DECnet router.
 
  Check for additional messages generated on the operator consoles, if any.
 
  Typically, circuit on-synchronizing means that the node initialization
  sequence between two adjacencent nodes is failing, and this failure will
  usually indicate a routing-related or network-related problem.  Generally,
  circuit on-synchronizing can be caused by any of the following:
 
   o  DECnet event 4.2, Node out-of-range packet loss
 
   o  DECnet event 4.3, Oversized packet loss
 
   o  DECnet event 4.6, Verification reject
 
   o  The circuit is on and the executor state is off
 
   o  The circuit is on and the line is off
 
   o  Insufficient BYTLM (buffered I/O limit), working set extent,
      or other NETACP process quota
 
 
  To increase NETACP process quotas on DECnet Phase IV, use commands
  similar to the following:
 
    NCP> set exec state off
    $ define/sys/exec netacp$buffer_limit 65536 ! or higher
    $ define/sys/exec netacp$extent       8192  ! or higher
    $ @sys$manager:startnet
 
  To calculate the buffered I/O limit, start with 3500 bytes to simply
  start up DECnet Phase IV.  Add the total of receive_buffers times
  device_buffer_size for all controllers present.  Increase this value
  by 7200 bytes when service is enabled on a circuit.  Increase this
  value further upward as required, and assume 65536 as a minimum.
 
  Please contact the Compaq customer support center for further
  assistance in resolving this problem.
 

  

     

     
answer written or last revised on ( 1-FEB-1999 )
     
» close window