[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::fddi

Title:FDDI - The Next Generation
Moderator:NETCAD::STEFANI
Created:Thu Apr 27 1989
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2259
Total number of notes:8590

497.0. "bridge500 and firmware 3.0" by TPOV07::CLARKSU () Thu Mar 12 1992 05:39

 Hi There,
 A very simple question. What is the lowest hardware and firmware version for
 the BRIDGE500 if I hope to upgrade this bridge firmware to 3.0 ?
 What will happen if my bridge doesn't match that requirement ?
 Your reply will be very appreciated.

 Bset regards
 Clark Su  
T.RTitleUserPersonal
Name
DateLines
497.1DECbridge 500 V3.0 release notes.........28888::B_GOODWINTime is an illusion...Thu Mar 12 1992 15:41112

               DECbridge 500 Operational Firmware V3.0
                            Release Notes

     This release of DECbridge 500  Firmware  contains  the  following
     functionality which is new from V2.2.

     1.  The capability to manage the DECbridge 500 with SNMP has been
         added  in  this  version.   SNMP  Get Requests are supported,
         through the community "public".  The SNMP Cold Trap  is  sent
         to  the  community  "traps", to Trap addresses configured via
         ELMS, if any.

     2.  MIBs supported - The MIBs implemented are MIB-II as  per  RFC
         1213,  DEC  Vendor  MIB  ELANEXT v1.3, the experimental draft
         IETF FDDI MIB v0.6, Nov 1990, and the experimental draft IETF
         Bridge  MIB  D6,  February  1991.  The DEC Vendor MIB ELANEXT
         v1.3 can be accessed at gatekeeper.dec.com via anonymous ftp,
         in  the  /private/mib  directory.  Please retrieve the README
         file for MIB information.

     3.  The IP support stack has been incorporated to  support  SNMP.
         Protocols  implemented are IP, ARP, UDP, and ICMP.  BOOTP has
         been implemented to allow the DECbridge 500  to  get  its  IP
         address,  unless  the  device  is already configured with one
         permanently via ELMS.

     4.  ELMS supports sets  and  removals  for  IP  address,  Gateway
         address  and  Trap  Addresses.   Setting  the  IP  address or
         Gateway address to 0.0.0.0  is  equivalent  to  removing  the
         corresponding address.

     5.  ELMS supports adds and removals of Ethernet protocol types to
         the  Non  Translated  Protocol  (NTP) table.  This feature is
         provided mainly to  alleviate  problems  in  a  transparently
         bridged  FDDI/NI  extended  LAN  where  the AppleTalk Phase 2
         protocol is in use.  Packets with protocol  type  present  in
         the  NTP  table  will  be  translated  to  the form they were
         received in, even if the packet was transmitted by a  station
         in  RFC  1042  format, across a pair of DECbridge 500's.  The
         NTP table contains the Apple ARP Protocol type (80-F3)  as  a
         factory  set  default  which allows both AppleTalk 1 and 2 to
         work  across  a  pair  of  DECbridge  500's.   The  following
         commands  are  available  through  DECelms  to manage the NTP
         table :

          -  Add an ethernet protocol type to the NTP table.

                  ELMS> add bridge1 ntp 90-08 password secret

          -  Remove an entry from the NTP table.

                  ELMS> remove bridge1 ntp 90-08 password secret

                                                                Page 2


          -  Show entries in the NTP table

                  ELMS> show bridge1 ntp


     6.  802.3 Length - If the 802.3 Length field is smaller than  the
         received  packet size indicates it should be, the packet will
         be translated into a packet with the  appropriate  length  as
         indicated  by  the  802.3 Length field.  In this case, if the
         received packet on the 802.3 network is not  a  minimum  size
         packet, the NI Length error counter on the 802.3 port will be
         incremented.


     The following bugs were fixed from V2.2.

     1.  IP Length - If a large IP packet is received on the FDDI  and
         it  is to be fragmented, and the total length field in the IP
         header indicates less data than  the  size  of  the  received
         packet  (ie,  there  was  padding),  then the padding will be
         removed during fragmentation.  Previously, such packets  were
         discarded.


     The following are warnings for the network manager to be aware of
     after installing DECbridge 500 Firmware V3.0.

     1.  The DECbridge 500 should be configured  with  an  IP  address
         either  with  the  use of ELMS, or by setting up the hardware
         address of the unit with an IP address in a BOOTP  server  on
         the  network.   Note that the device will periodically try to
         get its IP address approximately every 1 minute  using  BOOTP
         until it is configured with an IP address.

     2.  If you use Appletalk Phase 2 and have upgraded your DECbridge
         500  units  to  Firmware  V3.0  follow one of the steps given
         below to ensure the presence of the Apple ARP protocol  value
         in the NTP table.

          -  Use DECelms to reset the  bridge  with  the  factory  set
             defaults.

                  ELMS> init bridge1 with defaults password secret

          -  If  the  bridge  already  contains   management   created
             address/protocol   filters   or  other  parameters  whose
             default values were changed through management, then  the
             previous  step  would destroy these changes.  In order to
             avoid this the following command can be given on  DECelms
             to add Apple ARP in the NTP table.

                  ELMS> add bridge1 ntp 80-f3 password secret