Conference noted::decnis

> when will you support DEcnis /RouteAbout Configuration connected thru Frame
>Relay?

I don't quite understand what you mean. You can connect DECNIS to RouteAbout
over Frame Relay today by selecting PPP over Frame Relay as the datalink at the
RouteAbout end.

> when will you support BOOTP/MOP over Frame Relay ?

It is unlikely that we will ever support loading the DECNIS over a Frame Relay
connection - if that is what you mean by this question. The ROMs have no
knowledge of the Frame Relay protocols (neither the various flavours of LMI or
UNI, nor the possible encapsulations) and have no configuration control which
would allow the indication of which PVC to use to attempt the load over.

With an MPC-II or MPC-III it is possible to load a replacement flash image over
the active network using TFTP (regardless of the datalinks involved or the
remoteness of the image source) and program that into memory ready for the next
re-boot. With MPC-III the flash is split into two parts which allows one part to
be erased and reprogrammed without opening a window where the system would be
unusable if the link or power failed.

Please indicate if these answers didn't address the intent of your questions.

John

  John,

  i'm confuse, from Documentation chapter 8.20.5 restriction on Frame
  relay,statement said


  _only DECNIS-to-DECNIS or DECNIS-to-WANrouter500 operation is supported

  i can't see anything about Routeabout,should i missing something ?

  thanks

  Jean-Yves

This documentation is incorrect and must have been so for several years, we have
been supporting interoperation with DECBrouter90 (and hence other cisco
platforms) for a long time.

RouteAbout changed to allow the use of the DECNIS style of Frame Relay
encapsulation, it wasn't a change to the DECNIS so I suppose it didn't trigger
anybody to change the DECNIS documentation to indicate we support connection to
the RouteAbout.

I'll get the documentation fixed.

Note that MOST of the restrictions listed in 8.20.5 no longer apply with V4.0-5
and later:

The BECN bit is ignored
The DE bit is always set ineligble
No flow control

   All the three above are address explicitly by V4.0-5. BECNs do now modify
   the flow control operation and, if prioritisation is also used DE can be
   set on low-priority packet.

Only DECNIS-to-DECNIS

   This is the item that we addressing in the note - its just wrong
   
neither BOOTP nor MOP

   Unfortunately this persists. The only way of modifying the load image is
   using the console commands on MPC-II or MPC-III to TFTP the new image
   while the FrameRelay network is active.

There is no per DLC counter support

   Specifically added in V4.0-5 all the normal routing circuit and PPP link
   counters can be read for each circuit and there are new
   FRBS.channel.connection counters for FECN, BECN, DE etc.
   
There is no CTF support
   
   Although CTF hasn't been enhanced to support Frame Relay, DTF does
   support Frame Relay

 Thanks

 i prefer that..

 Jean-Yves