Netware 6 Upgrade Strategy
Prepared By Paul Dunlop
Version 1.0
Date 15/07/2002
TABLE OF CONTENTS
CURRENT BUSINESS ISSUES ................................................................................................................3
CURRENT REQUIREMENTS ..................................................................................................................3
UPGRADE STRATEGY.............................................................................................................................4
NEW TECHNOLOGIES TO EMPLOY ...............................................................................................................4
NEW NETWORK SCHEMATIC (DRAFT) ........................................................................................................4
ADVANTAGES OF CENTRALISATION UTILISING CLUSTERING AND NAS ...........................5
DIS-ADVANTAGES OF CENTRALISATION UTILISING CLUSTERING AND NAS ...................5
IFOLDER DIAGRAM ................................................................................................................................6
DIFFERENCES BETWEEN NETWARE 6 & CITRIX .........................................................................6
MIGRATION PLAN ...................................................................................................................................7
NETWARE 6 STAGES ...................................................................................................................................7
PUBLIC INTERNET SITE MIGRATION ...........................................................................................................7
NAS REQUIREMENTS .............................................................................................................................8
NAS DIAGRAMS ........................................................................................................................................8
NAS WITHOUT REDUNDANCY ...................................................................................................................8
NAS WITH AK COLD DR SITE .................................................................................................................9
NAS TAPE SOLUTIONS .........................................................................................................................10
NAS STRATEGY ......................................................................................................................................11
COSTS ASSOCIATED .............................................................................................................................11
CONCERNS ...............................................................................................................................................11
RECOMMEND STRATEGY ...................................................................................................................12
D:\106752060.doc
2
Current Business Issues
Barnardos is currently undergoing a review of its network topology and services. This is being done to
primarily enable IT to ensure they have strategically looked ahead for the services the network is to
provide and the costs involved in scaling for potential growth, as well as any viable options to help
eliminate network traffic issues.
Current issues IT have presently involve:
 Intercare / Intranet connectivity to all employees.

High speed Internet access for VPN WAN connectivity is location limited. Some regional offices
cannot get high-speed access at all and have to use a 56k modem in their computers to connect to
the Internet.

Traffic charges – High volume of traffic related to IPSEC / VPN on Jetstream connections.

Centralised Workstation Management – Zenworks 3.1 failure to work with MS XP Pro.

Centralised Server Patching – Zenworks for Servers requirements.

Remote user data backup (ELC)
Some, if not all, of these issues can be resolved with a migration to a modified Netware 6 environment.
Bringing servers back one by one into a central clustered environment is ideal for enhancing the
capabilities of a “clustered server”. I.e., the more servers a cluster has in it acting as one big computer, the
more applications can run on the server – such as GroupWise Web access with iFolder with NDPS with
iPrint with Apache etc.
Current Requirements
An ideal network solution for Barnardos would be one that can cater for the following requirements:
1. Allow all users to access Intercare
2. Allow all users to access the Intranet
3. Allow all users access to the Internet
4. Allow all users to access Email
5. Allow all users to have some form of data backup
6. File and Print services accessible to all and managed centrally for strategic data usage projections,
hardware monitoring etc.
7. Allow monitoring of network services and usage
8. Have redundancy built into it
9. Allow for the remote management of non-networked workstations
10. Allow for ease of patching workstations and servers
11. Minimizing administration and operational costs involved in both the infrastructure and the
accounting.
D:\106752060.doc
3
Upgrade Strategy
New Technologies to employ
To utilise the technologies provided by Novell for integrating workflow over the web and resolving
business issues with the current environment. These technologies are but not limited to:
 iFolder (Accessing files on a Netware server over a browser)
 iPrint (Accessing / Installing printers via a browser)
 GroupWise Web access (Checking email, to-do lists, colanders via a browser)
 Zenworks for Desktops v4 (Workstation management)
 eDirectory (The database that drives the network)
 LDAP (Lightweight directory (eDirectory or ActiveDirectory) Access Protocol)
 NAS (Network Attached Storage)
New Network Schematic (Draft)
Canterbury
Gillies Avenue
PORIRUA
Workstation
Workstation
Workstation
Workstation
Workstation
Hub/Switch
Hub/Switch
Router
Router
Hub/Switch
Firewall / Gateway / Cache
ADSL Router
Frame Relay Private Network
Workstation
No VPN / Direct Internet Access
Ghuznee Street
Router
Public Internet
Workstation
Kiakora
External / Internal 56kModem
Hub/Switch
Router
Firewall / Gateway / Cache
Workstation
Server C1
Server C2
Workstation
Server C3
Clustered iFolder/iPrint/GW Web Access / Zfd4 /
Netware 6 Environment
NAS
NAS (Network Attached Storage)
What does this diagram represent? Basically a small portion of a possible network infrastructure
redesign, utilising centralised servers with NAS for enterprise wide connectivity via a web interface into
Netware and its file system/services.
D:\106752060.doc
4
What is not shown fully in the diagram is the secondary gateways or firewalls. If we utilise frame relay
for our network between our “big sites” such as Ghuznee, Abel, Gillies and Canterbury – they can all be
connected via “private” routers, with no secondary gateways, with not too many adverse effects. As soon
as we want to give access to our systems to a public network client (someone on the Internet) then we
have to have a secondary gateway present in front of their access limiting what they can get to on our
private network.
Advantages of Centralisation utilising Clustering and NAS
1.
All Novell servers become clustered and act as one big virtual server (more processing power)
2.
Remote sites can hook into the Novell servers using iFolder and printers using iPrint via the
Internet.
3.
All remote machines (dialup and the like) can be remotely managed via Zenworks for
Desktops 4.
4.
Caching of Internet files at Ghuznee will allow for faster retrieval of files that are required for
more than one machine. (Such as Java initiator downloads).
5.
No requirements to login to a Netware server (rather a website).
6.
iPrint allows for users to install their own printers based on floor maps.
7.
Centralising the servers will cause less network traffic
8.
Removing IPSEC (VPN’s) from our routers will cause less network traffic
9.
iPrint will enable a remote dialup user to print a document to a printer next to the person they
want to send the document too.
10.
NAS allows for two or more servers to share the data array and thus allowing an NT box and a
Netware box to use the same storage arena. This will allow for Reports / Forms / Database /
Intranet box to all store their data on the NAS.
11.
Having all servers utilising the NAS in the central environment will allow for better DR
capabilities to an AK DR Site.
Dis-Advantages of Centralisation utilising Clustering and NAS
1.
iPrint will not work with a non-private link (i.e. a dialup modem connection). (Because it is
NDPS related and NDPS requires communication to the printer, so loss of connectivity to a
printer = problem)
2.
Large Application deployment will be slow on a 56k modem link
3.
Disaster recovery options still need to be addressed by NAS.
4.
Backup needs to be re-addressed (licensing changes, tape units)
5.
No Gateways at private network regional sites. Therefore DHCP could be an issue unless
routers cater for this. (may need gateways as a minimum at every office).
6.
The NAS would require additional hardware to set it up. (These being a NAS Array and
Zerver)
D:\106752060.doc
5
iFolder Diagram
The below diagram illustrates the flexibility a user can have with Novell 6 being utilised as a clustered
NAS environment with iFolder access being provide to both the “private” and the “public” networks.
Any LDAP
directory
User Authentication
Mobile
Matt’s
Folder
Storage
Internet
iFolder Server
Home
Jeff’s
Folder
Firewall
Kiosk
Jeff’s Folder Through a
Browser
Office
Jeff is able to access his data from his home, his office, practically anywhere with a browser. You can
clearly see the advantages of being able to work from any location. This is something our existing
network does not cater for.
Differences between Netware 6 & Citrix
1. Citrix adds the ability to run applications, such as Word, over the Internet on a remote server
instead of running them on the local computer. This allows server administrators to upgrade one
copy of Office only and it effects everyone.
2. Citrix uses intelligent updating of screen layouts for Windows sessions so as to enable minimal
network traffic. I tested Citrix over the Internet, and well this might be true for simple text based
applications, but basically anything multi-media is a waste of time on Citrix over the Internet.
Problem is, most computers are multi-media aware. The effect I believe of using Citrix will be
that of what we had before. Employees having to wait for their computers to do the allotted task,
such as booting up, thereby loosing productivity and painfully revenue. Netware 6 on the other
hand requires the Workstation to still have the requirement of Office installed locally, but we can
patch/upgrade utilising Zenworks application deployment as a form of management.
3. Citrix enjoys being a clustered NAS or NAS environment as well. Thus by nature being a central
solution it enjoys lots of benefits Novell does being central.
D:\106752060.doc
6
Migration Plan
Netware 6 Stages
As Novell 6 can be dropped into our network without having to rip out any other servers, we can migrate
to this environment in a controlled manner thus effectively “staging” the movements to the new
environment over a period of time.
The stages I would foresee are:
1. Building test environment (purchasing additional equipment for this)
2. Testing Clustering & NAS + iFolder etc
3. Drop Netware 6 onto the “HawkesBay” server (as a cluster server) and drop this into our network
with iFolder etc setup on it.
4. Setup a NAS in production and hook into the cluster
5. Upgrade Dixon-Zen1 server to be part of the cluster
At this point the clustered environment holds only 2 servers running in the cluster. This would be a good
time to start migrating some users over for load testing as well as any smaller sites with Netware boxes
that could be freed up to be added into the cluster for additional power.
From here we’d just be slowly eliminating all regional Netware servers as we migrate users over onto the
iFolder regime, effectively supporting two styles of networking so to speak while this transition occurs.
Public Internet Site Migration
Dialup or Public users (those who connect to the internet to access the internal systems) will need to have
a portal to be able to select the services they wish to access across the Internet. As this is generally a web
page hosted on the Internet it is recommended that the “Employee access points” should be obscured
somehow.
One good way of doing this would be to migrate the Internet website over onto our own internal servers
and host it ourselves. It’d doesn’t matter what it’s hosted on, as all the obscurity is there to do, is jump
the employee to the right address for logging into the main portal into iFolder etc.
So by having the Internet site considered as our “Public Web Interface” we could hide the employee login
deeper in the web site. Thereby allowing us to not show such a “Hi, I’m a page you can login into our
private network with… Please hack me.” attitude.
This migration would need to occur sometime around the implementation of the production environment.
The steps involved in this would be:
1.
Get our current Internet website onto the webserver that will be our main site for our Internet
gateway webserver.
2.
Alter the router to change the ports it uses
3.
Ensure the new Internet site contains a jump menu option somewhere to the address of the
portal for iFolder etc.
4.
Change Domain name pointers to our Internet address
5.
Wait patiently for domain name changes to take effect.
D:\106752060.doc
7
NAS Requirements
If we stick with Novell, with the movement towards pulling the servers back locally and clustering them
utilising a NAS for storage, then we gain major benefits in terms of centralised data alone. All employees
can have their data stored on the servers (including dialup users) and thus have it backed up. With a NAS
we also do not have to worry about rebuilding a server if we have run out of disk space to allocate the
volumes, which minimizes downtime and increases our scalability options for future data growth.
The requirements for implementing a NAS is :
1.
Clustered servers
2.
1xFile Zerver
3.
1xFortra JBOD Array
4.
NAS Diagrams
These diagrams are to assist with the understanding of how the network can be progressed to a suitable
level to allow for Disaster recovery and Business continuity.
NAS Without Redundancy
It is important to note that a NAS Array provides redundancy through the RAID capabilities as well as
Snapshot abilities.
Cluster
Server
Server
Ethernet
NAS Fortra JBOD+
File Zerver
With this setup only Ghuznee street would have a Clustered NAS environment.
D:\106752060.doc
8
NAS With AK COLD DR Site
GHUZNEE STREET
GILLIES AVE
Cluster
Server
Cluster
Server
Ethernet
NAS Fortra JBOD+
File Zerver
Server
Frame Relay
10mb or 100mb
Server
Ethernet
NAS Fortra JBOD+
File Zerver
In this environment the NAS JBOD boxes can talk to each other for “cloning” data, or data replication.
This allows us to save on additional licensing costs for Oracle that is stipulated by a “Hot DR Server”
environment, as this technique for replication would be considered cold (not have a requirement for real
time data replication to another server, and thus not requiring the server to be online just the array).
D:\106752060.doc
9
NAS Tape Solutions
You can either have the tape controller attached to the NAS Array via the File Zerver
Connected Directly to
NAS
Cluster
Server
Server
Ethernet
Tape Controller
NAS Fortra JBOD+
File Zerver
Tape
Tape
Tape Library
Or Attached to the Ethernet Hub.
Connected to Network
Cluster
Server
Server
Ethernet
Tape Controller
Tape
NAS Fortra JBOD+
File Zerver
Tape
Tape Library
The tape units will have to be re-addressed for this model. The current dat drives could be reused in this
environment or DLT’s may be a better option.
D:\106752060.doc
10
NAS Strategy
It would be best if we started off small redundancy wise.
 Purchase equipment for test environment

Purchase equipment for production environment without redundancy

Get migration under way

Expand NAS redundancy
Costs Associated




Upgrade licenses for Netware 6 (staggered)
Upgrade licenses for Zenworks 4 (not staggered)
Upgrade licenses for GroupWise 6 (staggered)
NAS Equipment
Initially we’d need hardware for the test environment and initial production environment.
2x Fortra Enterprise JBOD (SCSI) (Disk array unit)
2x Servers (+Hawkesbay Server)
2x Tape controllers
We’d need a total of 3 x Disk arrays, 9 x Servers (Min) for 3x3Clusters, 2 x Tape controllers for a full
implementation with redundancy. Number of DAT drives required is worked out according to data size
being backed up and will have to be reviewed closer to the date as to whether new tape units are required
(DLT).
Concerns

iPrint may not be fully achievable in the short term.

Initial costs may daunt the long term view of this network strategy

Time frames involved in implementation

Maintaining two networks as migration is in progress

Not enough time to research correct costings for all upgrades

DNS/DHCP/Caching issues have not been fully addressed

Costings / options for NAS solutions not fully explored

Staying the way we are is becoming out of the question – mainly because the VPN cannot be
expanded any further.
D:\106752060.doc
11
Recommend Strategy
It would be beneficial to start with testing iFolders capabilities.
Setting up a central cluster of servers using NAS while running iFolder and Zenworks will give us greater
administration capabilities in the areas of:
1.
Server Patching
2.
Workstation application deployment
3.
Remote dialup workstation management
4.
Web access to Files, Printers, Intercare, Email
These all help to bring about greater inter-connectivity, better administration, smoother support.
In short more productivity better administration and maintenance of systems will bring a good return on
investment in terms of total cost of ownership over our network and its operational costs.
D:\106752060.doc
12