



			Citrix Winview
			Application Notes

			CommVision CommSwitch 2500 Communications Server

			This application note is for
			informational use only and Citrix
			makes no representations or
			warranties with respect to the
			contents or use of this document or
			of any of third-party products
			discussed within.

						    
June 28,1995

Citrix Systems
210 University Drive
Suite 700
Coral Springs, FL 33071
(305) 755-0559
FAX (305) 341-6880


Overview:
---------

	This application note facilitates the configuration of the CommVision
CommSwitch Communications Server with Citrix "WinView for Networks". The 
CommSwitch provides a compact, rack-mountable, easy to manage Communications 
Server which can be used to centralize a WinView for Networks "cluster" into one 
location.

	The CommSwitch 2500 tested at Citrix was configured with 1 486DX/2-66mHz
System Processor, with 16MB of RAM, Novell NetWare 3.12 and NetWare Connect 1.0 
and (2) 486DX/4-100mHz Application Processors with 64MB of RAM and 540MB SCSI 
disk drives, which would each run WinView for Networks software. There is no 
limit to the number of Application Processors that can be installed in a 2500 
series chassis, the only limit being the 20 slot backplane. According to the 
documentation provided, CommSwitch 2700 and 2800 models support four and six
2500 chassis' respectively, yielding up to 120 PacketBus slots in a single 19" 
rack. Averaging 10 Application Processors per chassis, and 10-User WinView for 
Networks software on each Application Processor, multiplied by 4/6 chassis' 
yields 40/60 10-user WinView for Networks servers, or 400/600 users per rack 
unit (CommSwitch 2700/2800 respectively). The CommSwitch 2500/2700/2800 series 
offers enterprise-wide connectivity, with the advantage of scalable server 
technology, centralized administration, and communication server "clustering." 


Disclaimer:
-----------

	The scenarios described in this document have been tested by Citrix
Systems.  Other variations to the scenarios described in this document may
work, however they have not specifically been tested by Citrix.  In order
to recreate the configurations, you should use the specified revision
levels of all software products described in this document and stay within
the bounds of the features and functions described in this document.

	Please note that this application note is a living document and
will be modified as new information and versions of the software described
herein become availiable.  Make sure you have the latest version of this
document before you begin.  The latest version is always available in the
Citrix Forum on Compuserve.

Requirements:
-------------

	Hardware:
		CommVision CommSwitch 2500 rack unit(s) with:
			System Processor (DX/2 66mHz, NetWare 3.12/Connect 1.0
			Series 200 (486DX4 100 Mhz) processor boards
			

	Software:
		WinView for Networks 2.3 or higher
		CommVision PacketBus Driver for OS/2 (CVOS2E.SYS) 2.01 or higher
Setup:
------

	The normal WinView installation procedure should be followed as 
per the WinView for Networks Installation Manual, with the exception of exiting
to a WinView command prompt at the end of the installation procedure. Detailed
Instructions for modifying WinView for usage with the CommSwitch are included 
below, however, please note the Console Configuration issues listed below before 
beginning the installation procedure. Please read and understand the instructions
below before actually performing the modifications.


CommVision provides 2 OS/2 ODI drivers:
	CVOS2V.SYS for VIRTUAL_LAN  (CommVision Frame for IPX on the PacketBus) 
	CVOS2E.SYS for Ethernet     (Standard four Ethernet Frame Types) 

This section covers the usage of CVOS2E.SYS, which we recommend because it
supports all ethernet frame types necessary to attach to any internetworks.

Note: For TCP/IP for WinView usage, CVOS2E.SYS must be used. 


PacketBus Usage Background 
--------------------------

The CommSwitch utilizes the PacketBus architecture as an ethernet LAN segment
which connects the App Processors and the System Processor together. A driver
is loaded on the System Processor (CVPCKT.LAN), which initializes the PacketBus, 
as well as loading a frame type on the server which can be bound to a protocol. 
Any subsequent loads of CVPCKT.LAN serve to allow additional frame types and 
their respective protocols to be loaded and bound. For network communication 
outside of the CommSwitch, a NIC and it's driver must be loaded and bound to 
any necessary frame types and protocols. On the App Processor side, a driver 
for the PacketBus is loaded in WinView (CVOS2E.SYS), which can provide up to 4 
ethernet frame types as required. The NetWare software running on the System
Processor handles all routing of packets between the PacketBus and any true
ethernet segments which may be attached to the System Processor by use of true
ethernet NIC's in the CommSwitch. By loading additional frame types, additional
network protocols can be used, including TCP/IP, which can also be routed in and
out of the CommSwitch by the NetWare server by loading TCPIP.NLM with the 
parameter "forward=yes" appended to the "load TCPIP" command.

Below is a sample autoexec.ncf, taken from the tested configuration, for the 
NetWare 3.12 Operating System running on the System Processor, showing how to 
get IPX between the AP's and the SP running NetWare, and one external IPX
network connected to the CommSwitch SP using a 3Com 3c579 EISA NIC.
The *NOTE lines are additional information. They should *NOT* be typed in.


For IPX only, use the following statements, in addition to any other commands
needed in your autoexec.ncf:

(*NOTE* the next two lines are actually one continuous line on the server)
load cvpckt mem=DC000 int=A frame=VIRTUAL_LAN node_addr=00A09FFFED80 
  reset 16bit name=CV_VL  
load cvpckt mem=DC000 int=A frame=ETHERNET_802.3 name=CV_IPX
bind IPX to CV_IPX net=00501211
load 3c5x9 slot=2 frame=ETHERNET_802.3 name=IPXNET
bind IPX to IPXNET net=A


If TCP/IP for WinView 1.0 is going to be used, along with IPX, then use the
following statements:        


(*NOTE* the next two lines are actually one continuous line on the server)
load TCPIP forward=yes  *NOTE: This enables server routing of IP packets
load snmp  *NOTE: If SNMP management is going to be used
load cvpckt mem=DC000 int=A frame=VIRTUAL_LAN node_addr=00A09FFFED80 
  reset 16bit name=CV_VL  
load cvpckt mem=DC000 int=A frame=ETHERNET_802.3 name=CV_IPX
bind IPX to CV_IPX net=00501211
load cvpckt mem=DC000 int=A frame=ETHERNET_II name=CV_IP
bind IP to CV_IP address=128.128.66.1 mask=255.255.255.0
load 3c5x9 slot=2 frame=ETHERNET_802.3 name=IPXNET
bind IPX to IPXNET net=A
load 3c5x9 slot=2 frame=ETHERNET_II name=IPNET
bind IP to IPNET address=128.128.1.55 mask=255.255.255.0


*NOTES: 
	A) Substitute your IPX network, IP network addresses, IP subnet masks, 
	   and NIC drivers as appropriate. 
	B) Even though the VIRTUAL_LAN frame type isn't used, it *MUST* be
	   loaded before any of the ethernet frames will load.


This is the autoexec.ncf used on the test configuration, which included the use        
of Novell NetWare Connect 1.0:


file server name CV_SERVER
IPX internal net 25631675
load TCPIP forward=yes       *NOTE: This enables server routing of IP packets
load snmp                    *NOTE: If SNMP management is going to be used
load btrieve -u=1 -p=4096 -f=20 -h=60 -l=20 -c   *NOTE: for NetWare Connect 1.0

*NOTE* the next two lines are actually one continuous line on the server
load cvpckt mem=DC000 int=A frame=VIRTUAL_LAN node_addr=00A09FFFED80 reset 
 16bit name=CV_VL  
load cvpckt mem=DC000 int=A frame=ETHERNET_802.3 name=CV_IPX
bind IPX to CV_IPX net=00501211
load cvpckt mem=DC000 int=A frame=ETHERNET_II name=CV_IP
bind IP to CV_IP address=128.128.66.1 mask=255.255.255.0
load 3c5x9 slot=2 frame=ETHERNET_802.3 name=IPXNET
bind IPX to IPXNET net=A
load 3c5x9 slot=2 frame=ETHERNET_II name=IPNET
bind IP to IPNET address=128.128.1.55 mask=255.255.255.0
load REMOTE ""        
load RSPX
load MONITOR
;Begin NetWare Connect Auxiliary Subsystems initialization
load AIO
load AIODGXEM slot=1 port=104 mem=D0000
load NWCSTAT
load NWCCON
;Start NetWare Connect
load NWCSTART

WinView Application Server Modifications        
----------------------------------------

On the WinView for Networks Application Processor, when installing  NetWare 
support, choose the Intel EISA EtherExpress32. When asked for the slot number, 
enter any single digit number. Enter the preferred server you wish the AP to 
default to (in the case of our sample installation, we would use CV_SERVER). 
Continue the installation as normal.

When installation has completed, a screen will be presented which allows you
to ESCape out to the system prompt. Do so at this time, by pressing the <ESC>
key. Change to the \NETWARE directory on the WinView drive.

*NOTE*
Before installing the PacketBus driver for OS/2, verify with CommVision
that you have Version 2.01 or later of CVOS2E.SYS. This file is located on the
diskette labelled "CommSwitch Installation. PacketBus drivers, SNMP MIB and 
Diagnostics," which was included the the CommVision Communications Server.
The exact path to the file is  "A:\CLIENT\OS2\CVOS2E.SYS". Copy this file to 
the \NETWARE directory. run "E \CONFIG.SYS", and modify the line 
"DEVICE=C:\NETWARE\NE3200.SYS" to read "DEVICE=C:\NETWARE\CVOS2E.SYS".
This line will be about 15-20 lines from the bottom of the file. Press <F4> to
save and exit this file. Run "E \NETWARE\NET.CFG". Modify the line
"link driver ne3200" to read "link driver CVOS2E". Delete the line "slot x",
where "x" is the number you entered during installation (The delete command in
the WinView 'E' editor is <CONTROL><BACKSPACE>, and it deletes the current line
that the cursor is on. If TCP/IP support was installed, modify the line 
"bind NE3200" under "protocol ODINSUP" to read "bind CVOS2E". Press <F4> to 
save and exit this file. If TCP/IP support was installed, continue to the next 
section. otherwise, type "shutdown /now" to restart WinView.


Additional TCP/IP Modifications
-------------------------------
run "E \TCPIP\DRV\PROTOCOL.INI". Change all instances of "NE3200" to "CVOS2E".
Press <F4> to save and exit the file. Type "shutdown /now" to restart WinView.








Console Configuration Issues:
-----------------------------


1) Shared PS/2 mouse 

Description: This is an issue inherent with the CommVision session switching
capability being incompatible with WinView for Networks. Only the
foreground booted session may use the mouse AND, in order for the mouse
behavior to remain consistent, the 'session' must remain in the foreground,
limiting the usefullness of sharing the mouse.

Solution: In this situation, there are two solutions. The first solution is
to not load the mouse on the console at all. In this case, applications
that use the mouse can be used from remote workstations. If using a mouse
from the console is required, then upon installation, choose 'Microsoft PS/2
Mouse'. For this solution, it is required to plug in a PS/2 mouse into every 
processor board that requires a mouse.



2) Floppy drive access

Description: This is not really a description of a problem as much as it a
description of an inherent limitation of 'sharing' a floppy drive between
multiple CPUs. It is important that session switching between CPUs is NOT 
performed while floppy drive access is taking place. Doing so can cause 
incorrect and inconsistent floppy drive functioning, and data corruption or 
loss on the floppy diskette.

Solution: While doing disk copies, or while performing software
installation, or any access to the shared A: drive, DO NOT switch between
CPU sessions until the floppy drive operations are complete.



Manufacturer Contact Information
----------------------------------
Citrix Systems, Inc.    (305)755-0559
CommVision Corporation  (415)254-5720
