|
|
This chapter describes the procedure for downloading and installing software for the Cisco access servers. The procedures within this chapter may also be applied to other media gateways, depending on specific customer requirements and their configurations.
Cisco IOS software is released in several steps, called trains. After an initial release is created, it is numbered NN.X(1), where NN is the current main release number. For example, at the beginning of 2000, a new release will be introduced, Release 12.0.8.
Table 5-1 describes the Cisco IOS software release trains.
The following list presents a general overview of how different types of trains relate to one another:
In the preceding list, notice that the 12.1 release is the "parent" of the 12.1 T train, which in turn is the parent of the special release. Baseline features and bug fixes are propagated or synchronized to the "child" releases.
After the initial mainline version is released, the engineers continue to fix bugs (also called caveats) in the software. Every 6 to 8 weeks, a new release is introduced, called a maintenance release, in which some preexisting bugs are fixed, and some new bugs might be discovered. Using the Release 12.1(1) example, the second version of the software is numbered Release 12.1(2). About six to eight weeks after Release 12.1(2), more bugs are fixed, and new bugs might be discovered. Then a third version is numbered Release 12.1(3).
The Cisco IOS software releases that undergo this type of revision and numbering process are called mainline maintenance release trains. In mainline maintenance release trains, only bug fixes are incorporated into each new release.
The numbering progression for mainline maintenance releases follows this pattern: Release 12.1(1), 12.1(2), 12.1(3), 12.1(4), and so forth.
Because the software at each mainline maintenance release cycle becomes more and more stable (more and more bugs are fixed), many customers prefer to buy only mainline releases of the Cisco IOS software.
T-train releases are similar to mainline releases in that they fix pre-existing bugs and discover new bugs; however, with each T-train release, new features or enhancements are added as well.
 |
Note You may hear P-trains mentioned. P-trains apply to releases up to Cisco IOS Release 11.2(x), and the T-trains apply to Cisco IOS Release 11.3(x) and later releases. They are essentially the same; Cisco just adopted a new numbering system when Release 11.3 was introduced. |
For example, after an initial Release 12.1(1) (from the previous example), engineers start to develop new features for the 12.1 train. During the six to eight weeks until the next mainline maintenance release, they may create five or six new features and add them to the software. In this new "technology-train" (T-train) version, pre-existing bugs are fixed, new bugs are discovered (as in mainline release), and the two new features are added, and new bugs are discovered from the addition of the two new features. This new version is numbered Release 12.1(1)T to indicate that there are new technology enhancements.
Six to eight weeks after Release 12.1(1)T is introduced, engineers again work on developing new features to add to the last version. At the next release cycle, Release 12.1(2)T is introduced, which has bug fixes, bug discoveries, new features, and new bugs from the addition of the new features. Bug fixes from the parent mainline maintenance release are also incorporated into T-train releases.
The numbering progression of T-train maintenance releases follows this pattern: Release 12.1(1)T, 12.1(2)T, 12.1(3)T, 12.1(4)T, and so forth.
Because the software at each T-train release cycle includes enhancements, some customers prefer to buy these technology train versions of Cisco IOS software. They want to use the newest, "cutting-edge" technologies; other customers prefer to stay away from these technology train versions because they feel that the product is unstable because of new bugs introduced with each technology addition.
While mainline and T-train releases are created by IOS Technology Division engineers for virtually all platforms, SPLOB special releases are created by the engineers in SPLOB to address the needs of customers who require immediate access to new or specialized technologies on a limited number of platforms.
A special train release is derived from a "parent" T-train release to which features are added. Ideally, a special train has only one release, with no upgrades or subsequent maintenance releases. The special train features and bug fixes are incorporated into a later T-train release and special train customers can upgrade to a T-train release. For example, there might be a 12.1(5)XG release but never a 12.1(6)XG release.
However, there are exceptions—specials that continue through several versions in order to improve and expand features for certain customers on certain platforms. Eventually all specials are subsumed by T-train and mainline releases.
Periodically, engineers release a completely new version of software. This version incorporates all of the mainline and T-train maintenance releases with other completely new features, and the entire release number changes.
For example, using the example from above, maybe a year after the initial 12.1(1) release is introduced, all the technology enhancements from 12.0(x)T, 12.1(x)T, 12.2(x)T, 12.3(x)T, and so forth, along with all of the bug fixes from both the mainline and T-train maintenance releases, are combined with completely new features to create a new release: Cisco IOS Release 13.0(1). There is no certain point release that precedes the next major transition (from 11 to 12, or 12 to 13, for example).
When Release 13.0(1) is introduced, the whole cycle begins for the new release. While the new Release 13.x(x) is being developed, the Release 12.x(x) continues to be available as well. Usually, by this point, no new features (or very few features) are introduced in the 12.x(x) T-train. Instead, the engineers concentrate on fixing the bugs.
When the engineers determine that the mainline release software is as stable as possible, the release is given an End of Engineering (EOE) status. This means the engineers no longer work on the software. It is shipped as is.
Finally, when the software release becomes so old (almost to the point of becoming obsolete), it is given an End of Sale (EOS) status. This means that Cisco stops selling the software completely.
To get the most recent versions of software for your application you must go to the Web, specifically to Cisco Connection Online (CCO). Use the following procedure for obtaining your Media Gateway software:
Step 2 Log in with your assigned user name and password.
Step 3 Click Service and Support, then click Software Center.
Step 4 Click Access Software.
Step 5 Click AS5300, or whatever gateway you are using.
Step 6 Select Download the Cisco IOS 12.0 Software for the Cisco AS5300.
Step 7 Select Release 12.0 Upgrade Planner.
A matrix will appear with the available platforms and versions of software.
Step 8 Start in the left column of the matrix and select AS5300.
Step 9 Then select Major Release- 12.06.
Step 10 Continue your selection in the matrix and select IP.
Step 11 Be sure to check the requirements listed for each selection so that you have adequate memory on your machine.
Step 12 Click the Software Agreement box.
Step 13 Select the blue image filename.
Step 14 Copy the file by choosing either ftp or http.
The software will be downloaded to your machine.
Step 15 Save this file to disk.
Now copy your software over to your media gateway.
This section contains Cisco IOS release and VCWare compatibility information, system, and memory requirements.
Cisco VCWare Version 4.04 on the Cisco AS5300 requires the following voice-specific Cisco IOS Plus Images:
The table below contains the memory requirements for the Cisco AS5300 access server feature sets supported by Cisco IOS Releases 12.0(2)XH, 12.03(3)XH, and 12.0(5)T.
| Feature Set | Image Name | Required Flash Memory | Required DRAM Memory | Runs from |
|---|---|---|---|---|
IP Plus | c5300-is-MHz | 16 MB | 64 MB | RAM |
Desktop Plus | c5300-ds-MHz | 8 MB | 64 MB | RAM |
Enterprise Plus | c5300-js-MHz | 8 MB | 64 MB | RAM |
Before installing your Cisco MGW software, you must know what version of software is currently running on your machine.
To verify your current software version, use the following procedure:
Step 2 type sh ver.
Step 3 Look for "system image file" in the output. The last portion of the string identifies which version of the Cisco IOS software is currently running.
Enter your router command line.
Step 2 Enter copy tftp flash:
The file will now be installed in your machine.
You will be asked to identify the name of your IP server.
Step 3 Enter in the name of your server and its IP address.
For access to the CCO version of the Cisco AS5300 Universal Access Server Software Configuration Guide, go to:
For detailed examples of command output, see the Voice over IP for the Cisco AS5300 Configuration Guide. You can find the most up-to-date version of this manual online from either CCO or the CD-ROM.
Posted: Fri Aug 25 14:23:34 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.