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

Conference irocz::common_brouters

Title:Digital Brouters Conference
Notice:New common-code brouter family: RouteAbout, DECswitch 900
Moderator:MARVIN::HARTLL
Created:Mon Jul 17 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:929
Total number of notes:3736

867.0. "IPX problem on the VNbus" by DEKVC::SEUNGJOOSON () Fri Apr 18 1997 10:00

Hello,

I have encountered the IPX problem on the VNbus.

     IPX station                                     IPX server
         |                                                |
       DVNEE   DVNEX  DVNEF------ fddi--------Cisco------fddi---
         |       |      |
       --------------------VNbus

All VNswitch 900's locate within same DEChub900(MAM version is V5.0),
and all firmware version of VNswitch 900's are V1.5.  All ports including
ethernet, fast ethernet, and FDDI are in the same default VLAN. 
Cisco performs Novell routing between two FDDI LANs.

At the bridge config> prompt,  entered "enable ipx-translation" command.

However, NetWare communication between IPX station and IPX server does
not work.  As result of various simulation test, it leads me that
IPX frame coming from VNbus is not translating into *FDDI* LAN in the
DVNEF(VNswitch 900EF) module.

So now temporarily, I deleted the VNbus on DEChub900, and instead I
configured multiple Ethernets for three VNswitch 900s, and IPX works well.

But the customer have to use VNbus for IPX communication. What did I
make a mistake for IPX running?  Or is it known issue?  I'd much appreciate
for your any advice.  Thanks in advance and regards.
SJ.
T.RTitleUserPersonal
Name
DateLines
867.1IROCZ::GUNNERFri Apr 18 1997 12:396
Which VNswitch did you enable IPX-translation on ? You need to
set it on the VNswitchEE I think - the Ethernet IPX frames are
going to get translated to/from FDDI on the EE, not on the EF.
They will be getting forwarded over the VNbus in FDDI format.

Chris
867.2Enabled on both the EF and EE?NETCAD::BATTERSBYFri Apr 18 1997 13:2910
    I think though the IPX packets are going to be encapsulated
    within the FDDI frames, so I would think the IPX-translation
    has to be enabled on both the EF and the EE. IE: everything
    in the client/server path.
    It's been a while since I've walked thru this scenario on the 
    DECswitch, and it's a rainy Friday morning with my brain still 
    water-logged. :-)
    
    
    Bob
867.3IROCZ::GUNNERFri Apr 18 1997 14:266
No, the IPX translation occurs when going to/from Ethernet and FDDI frame
formats. In the switching path in this scenario the translation will 
only occur once on the EE module. The EF module will simply forward 
FDDI frames between the VNbus and the FDDI interface without translation.

Chris
867.4RE: # of translations....NETCAD::BATTERSBYFri Apr 18 1997 14:383
    Thanks Chris, yes I forgot that nuance. It's clear now. :-)
    
    bob
867.5still problemDEKVC::SEUNGJOOSONTue Apr 22 1997 02:2315
Hello Chris, and Bob

Thank you very much for your comments.

I enabled "ipx-translation" at all VNswitch 900 modules at first.
This time I disabled "ipx-translation" only in the VNswitch 900EF,
but the IPX still does not work. Did you simulate it?

As temporary workaround until fixing thru IPMT, I disconnected all
VNswitch from VNbus, instead created Ethernet IMB channels, and drag
down to its. And enabled "ipx-translation" at all VNswitch 900 modules.
Now IPX works.

Thank you again.
SJ.
867.6CSR configuration problemFORBIN::WILKINSONTue Apr 22 1997 19:366
    We think we have this problem identified.  It has to do with the
    CSR configuration of the VNbus.  IPX raw packets are not recognized
    on the VNbus.  This should be fixed in the next maintenance release.
    
    Hugh
    
867.7Hmmm... it's that VNbus thingy that was the problem :-)NETCAD::BATTERSBYWed Apr 30 1997 14:4711
    >As temporary workaround until fixing thru IPMT, I disconnected all
    >VNswitch from VNbus, instead created Ethernet IMB channels, and drag
    >down to its. And enabled "ipx-translation" at all VNswitch 900 modules.
    >Now IPX works.
    
    Ok that explains why my original perception was correct. With the 
    absence of use of the VNbus on the VNswitch, the way to get this
    to work *is* to enable "ipx-translation" on all modules in the
    path, as I did recall was the way one would do it on the DECswitch's.
    
    Bob