RuggedCom RX1100 用户手册
Appendix A – Setting Up A Repository
Appendix A – Setting Up A Repository
The RuggedCom software upgrade mechanism requires a repository of software to
available. The following instructions detail:
available. The following instructions detail:
•
Requirements for a repository server,
•
Initial set up of a repository,
•
Upgrading the repository to the latest release,
•
Maintain separate releases streams for different groups of routers,
•
Setting up one router to test new releases
•
Configuring the network routers.
Repository Server Requirements
In order to establish a repository you will need a host that is accessible to the routers
that will be upgraded. This host must be able to act as a web server or ftp server. The
host must also be able to access the RuggedCom web site in order to download new
releases of software from RuggedCom.
The server requirements are fairly modest. The principal requirements are for disk
space, bandwidth and the ability to serve an adequate number of http sessions.
Each software release will require approximately 50 Mb of disk space. Note that this
figure includes an entire software image, most upgrades will involve the transfer of
only a small fraction of this amount. A large number of such releases could easily be
stored on a system of only modest capabilities. In practice, only one or two releases
are usually all that need be kept.
The bandwidth requirements are determined by the many factors including the
number of routers, size of upgrade, when the routers upgrade, bandwidth limiting at
each router and network bandwidth capability. Most web servers can serve files to
the limit of the network interface bandwidth, so even a modest (e.g. 486 class
machine) would prove acceptable.
The server should be able to accept at least as many http or ftp connections as there
are upgradable routers in the network. In practice you will configure the routers to
have staggered upgrade times in order to minimize the impact of upgrading on the
network. A large upgrade (or a low bandwidth limiting value at each router) may
cause all the routers to be upgrading at any one time.
that will be upgraded. This host must be able to act as a web server or ftp server. The
host must also be able to access the RuggedCom web site in order to download new
releases of software from RuggedCom.
The server requirements are fairly modest. The principal requirements are for disk
space, bandwidth and the ability to serve an adequate number of http sessions.
Each software release will require approximately 50 Mb of disk space. Note that this
figure includes an entire software image, most upgrades will involve the transfer of
only a small fraction of this amount. A large number of such releases could easily be
stored on a system of only modest capabilities. In practice, only one or two releases
are usually all that need be kept.
The bandwidth requirements are determined by the many factors including the
number of routers, size of upgrade, when the routers upgrade, bandwidth limiting at
each router and network bandwidth capability. Most web servers can serve files to
the limit of the network interface bandwidth, so even a modest (e.g. 486 class
machine) would prove acceptable.
The server should be able to accept at least as many http or ftp connections as there
are upgradable routers in the network. In practice you will configure the routers to
have staggered upgrade times in order to minimize the impact of upgrading on the
network. A large upgrade (or a low bandwidth limiting value at each router) may
cause all the routers to be upgrading at any one time.
Initial Repository Setup
You must create a directory on the web server to hold the releases for the router. The
directory can have any name, such as “ruggedrouter”.
Some administrators like to designate one router to test the impact of new software.
This will require a directory, such as “ruggedroutertest” to be created.
These directory names will be used in examples in the remainder of this section.
Ensure that the web server publishes these directories.
directory can have any name, such as “ruggedrouter”.
Some administrators like to designate one router to test the impact of new software.
This will require a directory, such as “ruggedroutertest” to be created.
These directory names will be used in examples in the remainder of this section.
Ensure that the web server publishes these directories.
RuggedCom 267