Fund@RELAY.PROTEON.COM (01/11/90)
>We are thinking about Netware for VMS, we actually had our money on the >table, then realized the Econfig thing. Is it possible to use Netware >for VMS, 7 or 8 normal servers using 802.3, some clients using 802.3 >shells, and a few using packet drivers?? >Kevin Quinn All segments do not have to be ECONFIGed. If you have two Ethernet cards bridged in a server, only the one connected to the backbone will require this modification. All segments connecting to the backbone must be ECONFIGed to have them all play together. Glenn Fund Internet: Fund@Relay.proteon.com Principal Research Specialist CompuServe: 75170,1060 Sanders Associates cc:Mail Fund at Proteonwebo DW Highway South Phone: (603) 885-6242 MS NHQ4-0138 Director of The Greater Boston Area Nashua, NH 03061 Novell Users Group. Co-Founder and President of the Affiliation of NetWare Users "ANU Day Is Dawning"
ronc@XLNVAX.EXCELAN.COM (Ron Cully) (01/13/90)
> >We are thinking about Netware for VMS, we actually had our money on the > >table, then realized the Econfig thing. Is it possible to use Netware > >for VMS, 7 or 8 normal servers using 802.3, some clients using 802.3 > >shells, and a few using packet drivers?? > > >Kevin Quinn > > All segments do not have to be ECONFIGed. If you have two Ethernet > cards bridged in a server, only the one connected to the backbone > will require this modification. > > All segments connecting to the backbone must be ECONFIGed to have them > all play together. > > Glenn Fund Internet: Fund@Relay.proteon.com This is not entirely correct. It is possible to run both Ethernet type nodes (econfiged) and 802.3 nodes (default) together on the same backbone. To do this, an internal or external bridge is configured so that one side does 802.3 and the other does Ethernet. BOTH of the NICs are connected to the backbone, but each NIC must have a unique network address. Because the 2 NICs use different link level packet formats, they don't see each others packets even though both 802.3 and Ethernet packets are on the same wire. Because 802.3 and Ethernet are legal on Ethernet, there is no problem with confusing other nodes. By doing this, it is possible to have a mix of ECONFIGed and non-ECONFIGed clients and servers on the same net. All clients will be able to see all servers when an SLIST is done. This is good to remember especially when NetWare for VMS is being added to an existing NetWare Ethernet backbone since VMS can ONLY use Ethernet link format. There is no need to run a new segment for the VMS machine; just get a 2nd NIC for one of the servers and configure that NIC for Ethernet. A short while ago, someone was concerned about an ECONFIGed server causing loss of the MAC VAP. I don't have any direct experience with any problems (I'm trying to make problems in my lab now), but I have used the MAC VAP with an ECONFIGed server (although I don't remember which card I used). The MAC VAP is a true gateway. It accepts unadulterated AFP requests and sends out the required NCP requests (over IPX) on the MACs behalf. When the reply comes back, the reply is then converted to AFP and sent back to the MAC. Since AFP uses Ethernet protocol, the MAC VAP uses a different link level interface on the server. It has to in order to coexist with the default 802.3 protocol. Therefore, ECONFIGing the server should have no affect on the MAC VAP (because they use different software). If someone has experienced a problem with this, I would be very interested in getting the details so that I can try and reproduce it. The reason I bring up the MAC VAP issue is that you should be able to use an existing MAC VAP server to perform the Ethernet to 802.3 routing function when adding a NetWare for VMS server to an existing 802.3 NetWare network. Thanks! Ron Cully Product Marketing Engineer, NetWare for VMS