[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

1292.0. "DEcbridge 620 forgets it's IP address" by GIDDAY::STANISLAUS () Fri Mar 25 1994 00:30

	Reading note 1029 in this conference makes me believe that it is normal
for DECbridge 620 to forget its IP address and that you need a bootp server to
tell the DEcbridge it's IP address.

	I have a customer and there is no Unix system on this site. They have
DECmcc.

	This cutsomer's DECbridge  620 loses it's IP address on power fail.
Should we tell him that he needs a bootp server, otherwise he needs to set the
IP address everytime the DECbridge powers up.

Alphonse
T.RTitleUserPersonal
Name		DateLines
1292.1KONING::KONINGPaul Koning, B-16504Fri Mar 25 1994 11:507
The way I read 1029.1, the Bootp only happens if you haven't set an IP address
in NVRAM.  If you have, then it should remember this across powerups and
not do any Bootp.  If that's not what is happening, perhaps the NVRAM has
a problem.  Can you set address or protocol filters and have them remain in
effect across powerups?

	paul
1292.2check the dipswitchesNYOS02::AMMUFri Mar 25 1994 16:0210
    
    	Check the dipswitches. May be they are set to default to factory
    settings, in whichcase you lose the ip address. Dipswitch #2 should be
    up (off) to retain the current parameters.
    
    Also, if you do have novell 802.3 on the network, makesure you have
    set the esysIPXSWITCH to true in snmp mib, to translate the frame
    between ethernet to FDDI correctly.
    
    ammu
1292.3QUIVER::STEFANIHave the # for the Mars Observer?Wed Mar 30 1994 00:3721
    >>Also, if you do have novell 802.3 on the network, makesure you have
    >>set the esysIPXSWITCH to true in snmp mib, to translate the frame
    >>between ethernet to FDDI correctly.
    
    Be careful...if you have ETHERNET_802.3 and *NO* ETHERNET_II IPX
    clients on the Ethernet side of the bridge, throw the switch so that
    the "raw 802.3" IPX packets get translated into standard FDDI frames. 
    Doing this, however, causes problems for ETHERNET_II clients since
    translated ETHERNET_II packets will look the same as the "corrected"
    ETHERNET_802.3 packets on the FDDI ring, but going back from FDDI to
    Ethernet, they'll be translated to ETHERNET_802.3.

    Basically, it's an all-or-nothing switch.  My advice is to try to
    discourage ETHERNET_802.3 IPX frame type use as much as possible and
    only use this switch when you're able to segment all of your
    ETHERNET_802.3 nodes on one side of the bridge.  Note, Novell is also
    actively discouraging use of this frame type.
    
    If you (or anyone) has further questions on this topic, let me know.

       - Larry