Vanguard Applications Ware Software Release Notice Release 6.2.R000. Overview. Introduction

Transcription

1 Page 1 of 99 Vanguard Applications Ware Software Release Notice Release 6.2.R000 Overview Introduction This notice contains update information for Release 6.2.R000 of the operating software for these Vanguard platforms: Vanguard 320 Vanguard 340, 342 Vanguard 6435, 6455 Vanguard 7310, 7330 Release 6.2.R000 does not support the following: Vanguard 100 (supported by Release 5.3M) Vanguard 200 (supported by Release 5.1M) Vanguard 300 (supported by Release 5.4) Vanguard 305 (supported by Release 5.5) Vanguard 311 (supported by Release 5.1M) Vanguard 311 PLUS and 312 PLUS (supported by Release 5.3M) Vanguard 6425/6430/6450 (supported by Release 6.0.R00A) Vanguard 6520 (supported by Release 5.5) Vanguard 6560 (supported by Release 6.0.R00A) PLUS (supported by Release 5.1M) 650D (supported by Release 5.0C) Voice feature on the Vanguard 100 (supported by Release 5.2) This notice supplements the full set of the Vanguard user documentation.

2 Page 2 of 99 Memory Requirements for Release 6.2.R000 SAKs The memory requirements have changed for some Vanguard products supported by Release 6.2.R000 For more information on the memory changes that affect your Vanguard unit, refer to Memory Requirements for Vanguard Applications Ware Release 6.2.R000 section on page 7. Software Access Keys (SAKs) are not generally used with Release 5.2 and later products. Pre-Release 5.2 products, however, still use their SAKs. If you purchased SAKs for an earlier release, they can still be used with this release. In This Notice Topic See Page Applications Ware... 3 Software Upgrade Options... 4 License Upgrades... 6 Memory Requirements for Vanguard Applications Ware Release 6.2.R000 7 Products Supported... 8 New Features... 9 Vanguard 7300 Series Routers - Version 1 and Version Vanguard Feature Comparison Chart Software Configuration Limits Boot Prom Software Updates Software Improvements Known Software Limitations Documentation Supplements User Documentation How to Obtain User Documentation World Wide Web Documentation on the Vanguide 6.2.R000 CD-ROM Vanguide CD-ROM with Vanguard Software Builder Applications Ware for the Vanguard Applications Ware for the Vanguard 340 and Applications Ware for the Vanguard 6435/ Applications Ware for the Vanguard 7300 Series Products Applications Ware Features MIB Downloading Instructions for Non-Vanguard Managed Solutions SNMP Managers Applications Ware RFC Compliance Product Declarations and Regulatory Information... 97

3 Applications Ware Page 3 of 99 Applications Ware Introduction Applications Ware Licenses and Upgrades Default Software Images and Functionality This section explains how the Applications Ware are organized, implemented, and modified. The Applications Ware is divided into three base licenses and three license upgrades for Vanguard products. Customers are required to purchase only one base license and can purchase optional upgrade licenses to the base license: Standard Applications Ware Packages IP+ Applications Ware SNA+ Applications Ware Multi-Service Applications Ware License Upgrades Voice Applications Ware License Upgrade Security Applications Ware License Upgrade AS/400 BSC Applications Ware License Upgrade Note A license refers to both a legal document that allows a customer to use features and to the software that contains the features. Note One base license must be purchased for each hardware platform. Each license contains a large number of software features and functions. In addition, each hardware platform has a default factory image that contains a subset of the full license. In some cases, the default image might not completely meet your needs. You can either create a new Vanguard customer image using the Software Builder application on the Vanguide CD-ROM, or use our Vanguard Customer Ware Program. For details about all features in a particular Applications Ware License, refer to the appropriate section further on in this document.

4 Applications Ware Page 4 of 99 Software Upgrade Options Introduction Step by Step Software Upgrade If you are upgrading the software in your network, do not skip releases. You must upgrade to each intermediate release to ensure the integrity of your configuration memory (CMEM). This upgrade procedure applies to all Vanguard products. Upgrade your software by using the step-by-step upgrade option or use the Software Upgrader application. Both upgrade options are listed below. The step by step software upgrade is the traditional way to upgrade Vanguard devices. The process requires you to step though loading each individual release of Applications Ware, which will update the CMEM configuration file, and then continue through to the desired final release of the Application Ware. Assuming that you want to upgrade your network software from Release 5.4 to Release 6.2.R000, you must follow this example: Step Upgrade From Release To Release (Including any 5.4 point releases) (Including any 5.5 point releases) 5.6.R (Including any 5.6 point releases) 6.0.R00A R00A (Including any 6.0 point releases) 6.1.R R000 (Including any 6.1 point releases) 6.2.R000 Note The Vanguard 7300 Series can be upgraded from 5.4 to Release 6.2.R000 without loading 5.5, or 5.6.

5 Applications Ware Page 5 of 99 Software Upgrader Application The Software Upgrader is a Window-based PC application that eliminates the release-by-release upgrade process, by converting an existing image file to the latest Application Ware release in a single step. Once you have an upgraded CMEM, use Vanguard Configuration Loader to load the CMEM into your Vanguard. The goal of the software is to bring your network up to the most current versions of Applications Ware. You can quickly upgrade all the node s records with minimum downtime. The current version of Software Upgrader, upgrades releases from 4.96 to 6.2. Note Contact a Service Representative to obtain a copy of Software Upgrader. Step Description 1 Save old CMEM and convert it 2 Upgrade Vanguard Software and then default CMEM 3 Load converted CMEM Downgrading to Prior Releases Be aware that downgrading to and from any prior release is not supported and note that problems will occur with the configuration memory. To properly downgrade, the configuration should be defaulted and then restored with the saved CMEM that was running in the prior release. (DRCaa22736)

6 Applications Ware Page 6 of 99 License Upgrades Introduction Voice Upgrade The License Upgrades differ from standard Applications Ware packages in that they do not operate in a stand-alone capacity. For example, if you want the functions available in the SNA+ Applications Ware, you purchase that license and load it into your unit. However, a License Upgrade cannot be loaded into a unit by itself. You must: Purchase one of the standard Applications Ware packages Purchase the License Upgrade Use Software Builder to add the License Upgrade to the standard Applications Ware package The Voice Upgrade adds support for Voice features. The Voice Upgrade must be used with one of the standard Applications Ware packages. Note The Multiservice Applications Ware already contains the Voice features. Therefore, if you have Multiservice, you do not need to purchase the Voice License Upgrade. Security Applications Ware License Upgrade AS/400 BSC Applications Ware License Upgrade The Security Applications Ware License Upgrade adds support for encryption and VPN (Virtual Private Network). The Security Applications Ware License Upgrade must be used with one of the standard Applications Ware packages and the Data Encryption SIMM. VPN provides Triple DES, IPSec (IP Security) and GRE Tunneling (General Router Encryption) for Vanguard 64xx Series and Vanguard 340. The AS/400 BSC Applications Ware License Upgrade adds support for the AS/400 Communication Server feature, and the BSC 3270-to-SNA Conversion feature and the BSC 2780/3780-to-SNA LU0 for the Vanguard 6455 and 7300 Series. The AS/400 BSC License Upgrade must be used with one of the standard Applications Ware packages listed previously.

7 Applications Ware Page 7 of 99 Memory Requirements for Vanguard Applications Ware Release 6.2.R000 Memory Changes for Release 6.2.R000 In order to support the Vanguard Applications Ware Release 6.2.R000, some Vanguard products require memory upgrades. The total memory required for each product at release 6.2.R000 is listed in this table: Product Total Memory Required at Release 6.2.R000 Vanguard 320 8MB or 12 MB DRAM Vanguard MB or 32MB DRAM 4M Flash Vanguard MB Vanguard MB or 32MB DRAM Vanguard MB DRAM Vanguard 7310, M Flash 128M DRAM (Version 1 and 2) Note The table above lists the memory that is shipped. If you intend to use Release 6.2.R000 and your Vanguard unit does not have sufficient memory, please contact your representative to order memory upgrades. Product What to order for Memory Upgrade If your Vanguard unit You must order... currently has... Vanguard 320 4MB DRAM 4MB DRAM or 8MB DRAM upgrade Vanguard MB Vanguard MB Vanguard MB Vanguard MB Vanguard 7310, M Flash 128M DRAM (Version 1 and 2) Note The Vanguard 6425, 6430, 6450, 6520, 6560, 100, 200, 300, 305, 311, 311 PLUS, and 312 PLUS are not supported at Release 6.2.R000 and do not require memory upgrades.

8 Products Supported Page 8 of 99 Products Supported Products Supported for Release 6.2.R000 Products supported by release 6.2.R000: Product Vanguard 320 Vanguard 340 Vanguard 342 Vanguard 6435 and 6455 Vanguard 7310 and 7330 (Version 1 and 2) Support Normal product release. Normal product release. Normal product release. Normal product release. Normal product release. Products Not Supported Release 6.2.R000 is not supported on these products: Product Support Vanguard 100 This product is maintained at 5.3M. Vanguard 200 This product is maintained at 5.1M. Vanguard 300 This product is maintained at 5.4. Vanguard 305This product is maintained at 5.5. Vanguard 311 This product is maintained at 5.1M. Vanguard 31x+ This product is maintained at 5.3M. Vanguard 6425, 6430, This product is maintained at 6.0.R00A. and This product is maintained at 5.1M. 650-D This product is maintained at 5.0c. The battery backup version has been sunset. Vanguard 6520 This product is maintained at 5.5. Vanguard 6560 This product is maintained at 6.0.R00A.

9 New Features Page 9 of 99 New Features Introduction Documentation on the Web Release 6.2.R000 Features The new features available for Release 6.2.R000 are described briefly below. This section also lists where to find user documentation that contains detailed explanations of these features. You can find detailed descriptions of the new Release 6.2.R000 features in the referenced documents at the following web site: Instructions for obtaining on-line and hardcopy versions of the documents that contain detailed explanations of these features appear in the How to Obtain User Documentation section on page 57. These are the new features available with Release 6.2.R000: Vanguard 342 (Second LAN Port) The Vanguard 342 is a flexible, high performance RISC based multiservice router designed for small branch, and home offices that depend on efficiently consolidating serial protocols such as, SNA/SDLC, BSC with LAN traffic over dedicated or switched services. The Vanguard 342 offers cost-effective integrated solutions that simultaneously supports: Data Fax Voice over Frame Relay and Voice over IP Virtual Private Network (VPN) Broadband access Two 10/100BT LAN Ports (The second LAN port is port 8.) The Vanguard 342 includes support for a compression and encryption interface. For more information, refer to the Vanguard 342 Installation Manual (Part Number T0257).

10 New Features Page 10 of 99 Warning Your Vanguard product was designed and certified for use with specific memory option SIMMs. It is IMPORTANT that you install only the devices that are certified for use with your Vanguard product. Installation of an incorrect FLASH SIMM module could result in damage to the SIMM device or your Vanguard Product. Please see the list below for the memory device that is compatible with your hardware platform. Vanguard 340 Compatible FLASH SIMM Devices are as follows: 4-Meg FLASH Devices PN - "EDI7F292MC100BNC" PN - "SM70848XA2JIES2" Vanguard 342 Compatible FLASH SIMM Devices are as follows: 8-Meg FLASH Devices PN - "IW-388DL3-R-120" PN - "CT8M8FJV120.M1M" The FLASH SIMM Device Part Number (PN) can be found in small print on the face of the SIMM device. For further assistance, please call VanguardMS Service. Vanguard Point-to-Point Protocol over Ethernet (PPPoE) Release 6.2 or greater now enables Vanguard 7300 Series, 6435/6455, 340, 342 and 320 to utilize high-speed WAN access applications with broadband modems. A typical environment would be DSL, cable and wireless. For more information, refer to the Point-to-Point Protocol Manual (Part Number T ). Vanguard 6435/6455 Flash and CMEM Increase Release 6.2 and greater allows the Vanguard 6435 and 6455 to increase the FLASH memory and expand the CMEM area. Existing Vanguard 6435 and 6455 s can be updated to 8 Mbyte SIMM as long as the bootprom is also updated. A new bootprom is required to support the 12MB Flash option with the 128 kbyte CMEM. To use 128k CMEM, 8 Mbyte SIMM must be installed and the bootprom updated. Note The 8meg SIMM is not officially supported prior to release 6.2, however it can be installed in a 6455 running a 6.1 release without harm. It will simply be recognized and treated as a "4 Meg SIMM". Once a node is running 6.2 with the presence of an 8meg flash SIMM you cannot downgrade either the software or SIMM size as the configuration will be deleted.

11 New Features Page 11 of 99 Warning Your Vanguard product was designed and certified for use with specific memory option SIMMs. It is IMPORTANT that you install only the devices that are certified for use with your Vanguard product. Installation of an incorrect FLASH SIMM module could result in damage to the SIMM device or your Vanguard Product. Please see the list below for the memory device that is compatible with your hardware platform. Vanguard 6400 Compatible FLASH SIMM Devices are as follows: 4-Meg FLASH Devices PN - "EDI7F292MC100BNC" PN - "SM70848XA2JIES2" 8-Meg FLASH Devices PN - "IW388X1-R-120" PN - "EDI7F492MC120BNC" The FLASH SIMM Device Part Number (PN) can be found in small print on the face of the SIMM device. For further assistance, please call VanguardMS Service. For more information on the Vanguard 6435 and 6455 Series increases, refer to the Installing Flash and CMEM section of the 6435/6455 Installation Manual (Part Number T0166). Vanguard Dynamic Host Configuration Protocol (DHCP) Dynamic Host Configuration Protocol (DHCP) is a communications protocol that allows administrators to automate the assignment of Internet Protocol (IP) addresses in a network. Every unit connected to the Internet needs a unique IP address. This feature enables the Vanguard to act as a DHCP client and request configuration information for a DHCP server. For more information, refer to the Vanguard IP Routing Manual (Part Number T ). Vanguard Ethernet QoS P & Q VLAN Support A Virtual LAN (VLAN) is a switched network that is logically segmented on an organizational basis rather than on a physical or geographical basis. Workstations or servers used by a particular work group team, can be connected to the same VLAN, regardless of their physical connection to the network. For more information, refer to the Vanguard IP Routing Manual (Part Number T ). Vanguard Interoperability with RADIUS Authentication The purpose of Remote Authentication Dial-In User Server (RADIUS) is to enable Vanguard routers to interoperate and support RADIUS attributes. Vanguard routers are able to act as a RADIUS client. For more information, refer to the Vanguard IP Routing Manual (Part Number T ). Vanguard 6455 T1/E1 DC/FC Performance Improvement Increased T1/E1 feature card performance for the Vanguard 6455 is available with Release 6.2 and greater software. For more information, refer to the Vanguard 6435/ 6455 Installation Manual (Part Number T0166).

12 New Features Page 12 of 99 Vanguard V.90 Daughtercard A V.90 Daughtercard provides dial back-up for a customers PPP async applications. The V.90 enables our service organization to dial in to a customer node and get a CTP prompt to configure or debug a customers node. The V.90 Daughtercard connects to the Vanguard 320, 340, 342, 6435 and 6455 through a 68-pin connector. For more information, refer to the Vanguard Daughtercard Guide (Part Number T0020). Release 6.1.S100 and Greater Vanguard 6435 and 6455 Voice Switching Table Entry Increase An increase to the voice switching table entries from 3,000 to 6,000 on the Vanguard 6435/6455 is available with Service Pak 6.1.S100 and greater software. (DRFaa20092) Note Save your CMEM before configuring a large number of entries. If your CMEM becomes too large, you might not be able to save it. (DRCaa23348) All Vanguards - Software Images Using TFTP With Service Pak 6.1.S100 and greater software images, Vanguard Routers may now act as a TFTP server for CMEM and software image transfers. Using TFTP software on a PC, users may now upload the software image the node is currently running to the PC. Another aspect of the feature is a node to node download mechanism, where a single server node can download CMEM and software images to multiple client nodes (up to ten). (DRFaa20656) Note When using a TFTP application to connect to a Vanguard Router running release 6.0.R00A or greater software through its WAN link, use the WAN address instead of the internal or LAN address. (DRFaa21052) For more information regarding the Vanguard TFTP Server, access the Vanguard Managed Solutions Product Documentation web site at: TFTP Server information is included in the Installation and Coldloading Manual (Part Number T0028).

13 New Features Page 13 of Version 1 Enclosure Features Vanguard 7300 Series Routers - Version 1 and Version 2 Release 6.1 Vanguard 7300 Chassis Redesign (Version 2) The Vanguard 7300 Series chassis has been redesigned. The redesigned chassis is referred to as The Vanguard 7300 Series Version 2. Software must be configured to match the chassis type and version. (DRFaa20456) The table below summarizes common and distinct features of each Vanguard Version 1 Series enclosure: Feature Vanguard 7310 Version 1 Vanguard 7330 Version 1 Number of Slots 5 (horizontal) 8 (vertical) Height 3U 8U Rack-mountable Yes Yes Redundant AC and DC Power none Yes, dual power supplies 7300 Version 2 Enclosure Features The table below summarizes common and distinct features of each Vanguard Version 2 Series enclosure: Feature Vanguard 7310 Version 2 Vanguard 7330 Version 2 Number of Slots 5 (horizontal) 8 (horizontal) Height 4U 4U Rack-mountable Yes Yes Redundant AC and DC Power Yes, dual power supplies Yes, dual power supplies Set the Chassis Version Settings When upgrading a 7300 Series Version 1 to release 6.1.R000 or greater, you must set the chassis version setting. If the setting is incorrect (for example, upgrading a Version to 6.1 or greater software) the interface cards will not be recognized by the node in the correct physical slot location. Incorrect settings can be fixed by setting the software Chassis Version through the ZAP diagnostics menu. Note Units shipping from the factory with Release 6.1.R000 or greater will have the version set to match the chassis. Release 6.1.R000 or greater software is required for Vanguard 7310 and 7330 Version 2.

14 New Features Page 14 of 99 Verification Verification can be done by checking the Chassis Version printed at the top right of page one of the Detailed Node Statistics. Node: 7310_1 Address: 100 Date: 13-AUG-2002 Time:15:53:07 Detailed Node Statistics Page: 1 of 11 Product Type: VANGUARD 7310 Chassis Version: 2 Bootprom Revision: V1.50 Figure 1. Page 1 of the Detailed Node Statistics Configuration If a Vanguard 7300 Series Version 1 is set to Version 2 and needs to be configured, use the ZAP menu to set it to Version 1. This is required for the node to work properly. Follow the steps below to set the correct version. Configuring and Setting the Version Step Procedure 1 Load 6.1.R000 or greater on the Vanguard 7300 Series. 2 Reset the node, either by a software cold boot (CTP menu item 7.5) or by pressing the reset button on the CPU card. When the hardware diagnostics program starts executing, type ZAP (upper or lower case). Figure 2 shows the menu that will appear. 3 Change the Chassis version. 4 Reboot. Note Once the Chassis Version is set, it is maintained regardless of the clearing or loading of CMEM. The only way this pararmeter could be lost is if the FLASH is reformatted.

15 New Features Page 15 of 99 Diagnostics ZAP Mode Menu (Rev: 1.6) =============================================================== <ESC> Exit 1 - Force ColdLoad 2 - Activate Current CMEM 3 - Activate Alternate CMEM 4 - Clear All CMEM 5 - Change Chassis Version Selection: 5 Change Chassis Version [1/2]? (Currently set to 1): ==>> or (Currently set to 2) Figure 2. Diagnostics Zap Mode Menu The Vanguard 7300 family of high-performance, redundant, multiservice routers includes Models 7310 and 7330 Version 1 and Version 2 with the following features: CompactPCI architecture designed for carrier class requirements. Rack-mountable 5-slot and 8-slot chassis with AC or DC power. MCP750 processor card with industry-standard peripheral and I/O options. The following table lists Vanguard 7300 high-density port capacities. Port counts are given for both the Vanguard Model 7310 and the Vanguard Model 7330, along with the total port capacity for a typical seven-foot rack of Vanguard 7330 routers. Port Capacities Vanguard 7310Vanguard 7330 Ethernet 55 T1/E1/PRI Voice Channels -- T Voice Channels -- E Serial Ports: X.21, V.35/V.36, EIA232, EIA Token Ring: 2 2 Power Supplies *V1 (1) V2 (2) 2 *Version 1, V1 or Version 2, V2 Note For more information on the Vanguard 7300 Series, refer to the Vanguard 7300 Installation Guide (Part Number T0185) is included on this CD-ROM.

16 Vanguard Feature Comparison Chart Page 16 of 99 Vanguard Feature Comparison Chart Below is the Vanguard Feature Comparison Chart: Feature Vanguard 6560 Vanguard 6450/6455 Vanguard 7300 Dual T1 Network Interface Specification Dual E1 Network Interface Specification Channelized Data Support Connectors: Dual RJ-45 (100 ohm) Framing: SF and ESF Line Coding: AMI, B8ZS, B7ZS Timing Source: Int, Receive T1 CSU: Optional Daughtercard Connectors: Dual RJ-45 (120 ohm) BNC Via Ext Cable Framing: E1_CAS, E1_CAS_CRC, E1_CAS_FEBE Line Coding: HDB3, AMI Timing Source: Int, Receive Protocols Supported: X.25, FR, TBOP, PPP Maximum Number of Channels: 30 Maximum Aggregated rate: Mbps Connectors: Dual RJ-45 (100 ohm) Framing: SF and ESF Line Coding: AMI, B8ZS Timing Source: Int, Receive T1 CSU: Built In Connectors: Dual RJ-45 (120 ohm) - Dual BNC (75 ohm) Framing: E1_CAS, E1_CAS_CRC, E1_CAS_FEBE Line Coding: HDB3, AMI Timing Source: Int, Receive Protocols Supported: X.25, FR, TBOP, PPP Maximum Number of Channels: 24 (T1) Maximum Number of Channels: 31 (E1) Maximum Aggregated rate: Mbps Two card versions: port T1 or E1 (RJ ohm) 2. 8 port T1 or E1 (RJ ohm) E1-75 ohm support Future Node wide CLOCK control T1 Framing: SF & ESF Line Coding: AMI, B8ZS Timing Source: Int, Receive T1 CSU: Built In E1 Framing: E1_CAS, E1_CAS_CRC, E1_CAS_FEBE Line Coding: HDB3, AMI Protocols Supported: X.25, FR, TBOP, PPP Max Number of Channels per T1/E1 port: 24 (T1), 31 (E1) Total No. of channels per card: (T1) 8*24=192, 12*24=288 (E1) 8*31=248, 12*31=372 Total No. of channels per System: (7310 T1) 192*4=768, 288*4=1152 (7310 E1) 248*4=992, 372*4=1488 (7330 T1) 192*7=1344, 288*7=2016 (7330 E1) 248*7=1736, 372*7=2604 Note: all numbers subject to processing capabilities of the 7300.

17 Vanguard Feature Comparison Chart Page 17 of 99 Feature Vanguard 6560 Vanguard 6450/6455 Vanguard 7300 ISDN PRI Data Support Voice Signaling Support Proprietary Features Additional Clocking Features SDLC HPAD/ TPAD LLC2 (SNA) Conversion Switch Types (1): 4ESS, 5ESS, DMS100, DMS250, Siemens, NTT, CCITT, MD110 Switch Variants: AT&T, NT, NI-2, JATE, Net5, 1TR6, VN3 TS014 (Austel) CAS: E&M (Wink, Delay, Immediate Colisee, and Seizure Ack) FXS (Loopstart) FXO (Loopstart) CSS: All Switch Types/Variants included in PRI Data (1) Q.SIG (Master/Slave) Basic Call Supplementary Services Segmentation Transparent CCS Timeslot Bypass CCS Bypass None Protocols: SDLC Characteristics: HDX, FDX, TWA Network:QLLC/X.25/Frame Relay (Annex G) Host Interface:SDLC PTP, SDLC MP, X.25 (IBM NPSI) Physical Interface:V.21, V.24, V.35 Protocols: LLC2, X.25 (QLLC), SDLC, FR (RFC1490) Characteristics: HDX, FDX, TWA Network:QLLC/X.25/Frame Relay (Annex G) Frame Relay (RFC1490) Host Protocols: SDLC PTP, SDLC MP, X.25 (IBM NPSI), LLC2, Frame Relay (RFC1490) LAN: Token Ring (4 or 16 mbps), Ethernet (10 mbps), Ethernet2. WAN Physical Interface: V.21, V.24, V.35 Switch Types (User Side Only): N/A Bundle (T1) NI-1, 4ESS, 5ESS, DMS100 European Bundle (E1) ETSI Asia Bundle (T1) NTT Switch Variants: None Required CAS: E&M (Wink, Delay, Immediate Colisee, and Seizure Ack) FXS (Loopstart) FXO (Loopstart) CCS (2,3,4): N/A Bundle (T1) Q.Sig (Master/Slave) (5) 5ESS (Network/User) (6) NI-1 (Network/User) (6) DMS100 (Network/User) (6) Euro Bundle (E1) ETSI (Network/User) Q.Sig (Master/Slave) (5) Timeslot Bypass Node Wide Network Clock Source Protocols: SDLC Characteristics: HDX, FDX, TWA Network:QLLC/X.25/Frame Relay (Annex G) Host Interface:SDLC PTP, SDLC MP, X.25 (IBM NPSI) Physical Interface:V.21, V.24, V.35 Protocols: LLC2, X.25 (QLLC), SDLC, FR (RFC1490) Characteristics: HDX, FDX, TWA Network:QLLC/X.25/Frame Relay (Annex G) Frame Relay (RFC1490) Host Protocols: SDLC PTP, SDLC MP, X.25 (IBM NPSI), LLC2, Frame Relay (RFC1490) LAN: Token Ring (4 or 16 mbps), Ethernet (10 mbps), Ethernet2. WAN Physical Interface: V.21, V.24, V.35 5) Q.Sig Support now includes Basic Call, Supplementary Services and Segmentation. 6) Enblock Signalling Support only at this time. Switch Types (User Side Only): N/A Bundle (T1) NI-1, 4ESS, 5ESS, DMS100 European Bundle (E1) ETSI Asia Bundle (T1) NTT Switch Variants: None Required CAS: E&M (Wink, Delay, Immediate Colisee, and Seizure Ack) FXS (Loopstart) FXO (Loopstart) CCS (2,3,4): N/A Bundle (T1) Q.Sig (Master/Slave) (5) 5ESS (Network/User) (6) NI-1 (Network/User) (6) DMS100 (Network/User) (6) Euro Bundle (E1) ETSI (Network/User) Q.Sig (Master/Slave) (5) Timeslot Bypass Node Wide Network Clock Management Data Applications: Each Group of 4 T1/E1 ports can synchronize to a different carrier Voice & Data Applications: Each card has to be connected to one carrier Same as 6560 except: Characteristics: no HDX Same as 6560 except: Characteristics: no HDX

18 Vanguard Feature Comparison Chart Page 18 of 99 Feature Vanguard 6560 Vanguard 6450/6455 Vanguard 7300 AS/ Communications Server Other SNA protocols BSC3270 -to- SNA Conversion BSC2780/3780-to- SNA/LU0 Conversion Protocols: LLC2, X.25 (QLLC), SDLC, FR (RFC1490) Characteristics: HDX, FDX, TWA Network:QLLC/X.25/Frame Relay (Annex G) Frame Relay (RFC1490) Host Protocols: LLC2, Frame Relay (RFC1490) LAN: Token Ring (4 or 16 mbps), Ethernet (10 mbps), Ethernet2. WAN Physical Interface: V.21, V.24, V.35 BSC3270 HPAD/TPAD BSC2780/3780 IBM 2260 PAD TCOP TBOP MX25 NCRBSC HPAD/TPAD ALC Pad Scope Protocols: LLC2, X.25 (QLLC), SDLC, FR (RFC1490) Characteristics: HDX, FDX, TWA Network:QLLC/X.25/Frame Relay (Annex G) Frame Relay (RFC1490) Host Protocols: LLC2, Frame Relay (RFC1490) LAN: Token Ring (4 or 16 mbps), Ethernet (10 mbps), Ethernet2. WAN Physical Interface: V.21, V.24, V.35 BSC3270 HPAD/TPAD BSC2780/3780 IBM 2260 PAD TCOP TBOP MX25 NCRBSC HPAD/TPAD ALC Pad Scope Not supported Supported on the Devices Supported Not supported Supported on the Devices Supported Same as 6560 except: Characteristics: no HDX TBOP All others not supported 2,000 Devices Supported 256 Devices Supported Frame Relay FRI, FRA and FRF.12 Supported FRI, FRA and FRF.12 Supported Same as 6450/ except no FRA and FRF.12 support IP/LAN VPN/IPSEC/3DES VPN/IPSEC/3DES Not supported, planned for future. ATM No ATM Support 2 T1 or E1 EDC cards supported on 6455 UBR, VBR and CBR 300 VCCs IP over ATM No AnnexG ATM supported over T3 or E3. UBR, VBR and CBR 4000 VCCs IP over ATM AnnexG over ATM

19 Vanguard Feature Comparison Chart Page 19 of 99 CLI (Command Line Interface) SNMP Feature Vanguard 6560 Vanguard 6450/6455 Vanguard 7300 The following new commands are supported: > getdefault > getdefaultall > getnondefault > getnondefaultall > update CLI instance value: Support HEX instance value Supporting port number: Up to 255 port number The following MIB objects are supported only in 6560/5.5 platform. cdx6500t1e1vgtable cdx6500tdmclktable The following new commands are supported: > getdefault > getdefaultall > getnondefault > getnondefaultall > update CLI instance value: Support HEX instance value Supporting port number: Up to 255 port number The following MIB objects are supported only in 6560/5.5 platform. cdx6500t1e1vgtable cdx6500tdmclktable Commands supported only in 7300: > flash copyimage > flash copycmem > flash activeimage > flash activecmem > flash deleteimage CLI instance value: Support only INTEGER instance value Supporting port number: Up to bit port number The following MIB objects are supported only in 7300 platform. cdx6500pstt1e1tgporttable cdx6500pstt1e1tgtable cdx6500sttdmtgclkgroup 1) All signalling types/variant combinations support user or Network side and T1 or E1. 2) Q.Sig/Euro ISDN support on T1 interfaces is now available in Release 5.5, 5.6, 6.0.R00A, 6.1.R000 and 6.2.R000 3) NTT Signalling support is currently unavailable and is targeted to be added in a future release. 4) Transparent CCS can be supported manually by means of configuring the TBOP data channel for Signalling channel and Voice Bearer channels with None for signalling. Virtual port mapping table entries for voice ports must be TDM-VOICE. 5) Q.Sig Support now includes Basic Call, Supplementary Services and Segmentation. 6) Enblock Signalling Support only at this time.

20 Vanguard Feature Comparison Chart Page 20 of 99 Software Configuration Limits Introduction Configuration Limits This section describes the software configuration limits. This table lists the software configuration limits for: Physical Ports (physical port counts are set by software, not the actual number of physical ports) Frame Relay Sessions Network Services LAN - (IP specific) Voice SNA/IBM Support Software Configuration 7300 Series 6435/55 Physical Port Maximum Limits Physical ports Ethernet ports per node (performance limited at 100MB speed per port) 5 Total LAN ports (Ethernet) per node (not bridge port support count) 5 Devices supported per Ethernet segment (Relevant to Bridge operation) High speed (V.35) serial links per node 56 PRI ports (data only) per node 84 2 T1/E1/PRI voice only ports per node 14 2 T3/E3 ATM ports per node 2 0 Voice circuits per voice server card Number voice calls per node (Number shown is E1 max.) Number voice calls per node (Number shown is T1 max.) Frame Relay Number of DLCIs per FR Port Number of PVCs per FR Annex-G station Number of SVCs per FR Annex-G station Number of Voice SVC per Annex-G station 1515 Number of DLCIs per node 8,000 1,024 Session Number of LCON 2,000 2,000 Number of Virtual Ports (FR, X25, PPP, Voice) 2, Number of multi-link PPP profiles (7300 Series original size was 600) 1,000 60

21 Vanguard Feature Comparison Chart Page 21 of 99 Software Configuration (continued) 7300 Series 6435/55 Number of UDP (sotcp) sessions terminating in the node 2, Number of TCP (sotcp) sessions terminating in the node 2, Number of simultaneous calls per node 8, Network Services Number of Network Services Tables Entries 1, Number of PVCs table entries 8,000 2,000 Number of mnemonic table entries 8,000 2,000 (7300 Series original size - 2,000) Number of Switch Service table entries 1,024 1,024 Number of X25 routing table entries 8,000 2,000 LAN IP (Specific) Routing table size 15,000 4,000 Routing Cache Accelerated/ Aggregated Route cache Number of LCONs 8,000 2,000 (7300 Series original size - 2,000) Number of Interfaces 1, Access Control List table size Policy based routing table size Static ARP table Number of static routes 8,000 8,000 (7300 Series original size - 1,024) MAC Filter Table Entries 1, (7300 Series original size - 300) RIP route control table NAT table size 1, (7300 Series original size - 255) IP Multicast DVMRP Tables size CIDR: RIP aggregate table CIDR: Multihome table size

22 Vanguard Feature Comparison Chart Page 22 of 99 Software Configuration (continued) 7300 Series 6435/55 Voice Number of voice switching table entries: An increase to the voice switching table entries from 3,000 to 6,000 on the 6435 and 6455 platforms is available with Service Pak 6.1.S100 and greater software. Note Save your CMEM before configuring a large number of entries. If your CMEM becomes too large, the node may reset or default its configuration. SNA/IBM Support Number of stations per LAN interface (SLAC) - Note: Two LAN interfaces allowed per node -- 1,000 stations per interface, Number of stations per Node (SLAC) - Note: Two LAN interfaces allowed per node -- 2,000 max stations per node. LLC LAN Conversion Stations: Vanguard 7300 Series - 1,000 per interface, 2,000 per node (Release 6.0 and greater) Vanguard 6435/ per interface, 500 per node Vanguard 340, stations on one port Vanguard per node LLC FRI Conversion Stations: Vanguard 7300 Series - 2,000 per node (Release 6.1 and greater) Vanguard 7300 Series - 1,000 per node (Prior to Release 6.1) Vanguard 340, 342, 6435/ per node Vanguard per node 10,000 6,000 1, , Additional Limits Number of bridge links entries 1,000 1,000 (7300 Series original size - 250) ARP (queue size) Max. number of IPX interfaces+ 1,000 1,000 Number of OSPF routes 7,500 2,048 Max. SVCs per SoTCP session Max. Total Data SVCs (SoTCP) 2,000 1,024 Max. Total Voice SVCs (SoTCP) 2,000 1,024 IP Broadcast Forwarding Table Size UDP Broadcast Forwarding Table Size Outbound Translation Table Entries (7300 Series original size - 1,600) 16,000 1,600

23 Vanguard Feature Comparison Chart Page 23 of 99 Software Configuration (continued) 7300 Series 6435/55 Additional Limits - ATM ATM Stations * Vanguard 6400 Series * Vanguard Not Applicable Maximum FRST Entries * Vanguard 6400 Series * Vanguard Not Applicable SAR Profile * Vanguard 6400 Series - 50 * Vanguard Not Applicable X25 Profile * Vanguard 6400 Series - 50 * Vanguard Not Applicable 4,000 * 4,000 * 500 * 500 * Maximum Compressed Data Connections 500 Additional Limits - LAN Transparent Bridge Forwarding Table Size 16, (7300 Series original size - 8,000) Max. number of OSPF interfaces Max. number of PPP switched links BGP Policy Table 2, BGP to OSPF Import Policy Table 1,024 1,024 BGP Maximum peers QoS Parameter Note The QoS parameter fields can be configured to a maximum of 1,000 or 10,000 (in the case of IP Flow Table Size). 1,000 *

24 Boot Prom Software Updates Page 24 of 99 Boot Prom Software Updates Introduction Software Loader Procomm Procedure This section provides instructions for Coldloading the Boot prom using Software Loader or Procomm Communication software. Software Loader automatically upgrades or downgrades the boot prom. When an image is loaded and it requires a version of bootprom different from the one currently loaded, Software Loader changes the boot prom to successfully load the image. For more information on bootprom-image compatibility, refer to the Bootprom Directory table on page 29. The bootprom can be uploaded and downloaded manually using a communication application such as Procomm. Caution Backup your configuration. Upgrading to a new release could cause configuration loss. If you choose to downgrade to a previous release, you must reload the configuration saved from that release or risk corrupting the configuration. Below is a step procedure on how to coldload the Bootprom using Procomm Communication software. This procedure example was documented using a Vanguard 7300 Series router. Figure 7 on page 30 shows the various product directories. Note Boot Prom revision 1.50 is current for release 6.2.R000, 6.1.R000 and 6.0.R00A software on the Vanguard 7300 Series. 1) To determine the current version of Bootprom loaded on your Vanguard, perform these steps: Step Action a) Access the Console Terminal Program s (CTP) Main Menu. b) Select Option 5, Status/statistics. c) Select Option 1, Node Stat, from the Status/statistics menu. The Node Stats displays the Bootprom Revision: 7300 Series Examples: Version 1.10, 1.11, 1.30, 1.40 or Version Note Refer to the Bootprom Directory table in Step 9.

25 Boot Prom Software Updates Page 25 of 99 Figure 3. Bootprom Revision Example 2) Use the Procomm application to update the Bootprom. Open the Procomm application to get a Data Terminal Window. The settings should be 9.6k, N-8-1, and RAW-ASCII transfer mode. Use a regular Control Terminal Port (CTP) connection. 3) Activate a Force Cold-Load (16.12.y.y): Flash Memory->Force-Cold-Load->yes Cold Boot the node (7.5.y): Boot->Node (cold)->yes A Download Coldloader prompt from the (CTP) displays. 4) Choose an appropriate speed coldloader indicated in the current bank column of the table below. Typically the c73cv115.xrc file is used. Current Bank c73cv115.xrc 115 c73cv192.xrc 19.2 c73cv288.xrc 28.8 c73cv384.xrc 38.4 c73cv576.xrc 57.6 c73cv96.xrc 9.6 Kbps

26 Boot Prom Software Updates Page 26 of 99 5) Download the appropriate coldloader to your PC for the correct Bootprom version, from the following directory example: C:\Vanguard\SFW_IMGS\73*0\COLDLOAD\T10BP1** Note You must use the coldloader from the current bank column of the table in step 4 to load the Bootproms. 6) When using the Procomm application: Select Send File from the Procomm Data Menu Select RAW ASCII transfer mode Select 9600 for the Coldloader speed The following figures show the Procomm application. Note To be sure you are in RAW ASCII transfer mode, when in Procomm, check the setup file. Options->Data Options RAW ASCII Figure 4. Procomm Plus Terminal

27 Boot Prom Software Updates Page 27 of 99 Procomm Setup When Options->Data Options->Transfer Protocol is selected, a Setup menu displays. Select RAW ASCII from the Current Transfer Protocol pull down menu Click the Transfer Protocols button Figure 5. Procomm Setup Menu

28 Boot Prom Software Updates Page 28 of 99 Send File To send a file, open the Procomm application. Under the Data Menu select Send File. This button also Sends Files. Figure 6. Procomm Plus Terminal Send File Send the correct file using one of the enclosed c73 loaders below: c73cv115.xrc for 115 Kbps c73cv288.xrc for 28.8 Kbps c73cv192.xrc for 19.2 Kbps c73cv384.xrc for 38.4 Kbps c73cv576.xrc for 57.6 Kpbs c73cv96.xrc for 9.6 Kbps Note To reduce the download time, Vanguard Managed Solutions recommends c73cv115.xrc for 115 Kbps. 7) Once the download is complete, change the terminal speed to the appropriate coldloader speed chosen in step 4. Download the Bootprom.xrc file. The required Bootprom version (such as T10BP111.xrc) can be acquired from the directory containing the same name: C:\Vanguard\SFW_IMGS\73*0\COLDLOAD\T10BP1** 8) Open the Procomm Plus Terminal Manual application: - Select Send File, under the Procomm Data Menu - Select the correct bootprom version

29 Boot Prom Software Updates Page 29 of 99 9) Choose the correct bootprom directory that includes the coldloaders. The example below shows the 7300 Series Bootprom Directories. \T10BP1** refers to: T10BP110 T10BP111 T10BP130 T10BP140 T10BP150 Bootprom Directory T10BP110 T10BP111 T10BP130 T10BP140 T10BP150 ONS Image Compatibility 5.4.P08A 5.4.P08B 5.4.P08# Note The pound sign # represents a letter from C to Z. 5.4.P0LA, 5.4.P0KA, and 5.4.P0JA Note Bootprom version 1.30 is required to run the 5.4 Point Release L software. The 1.30 version of the bootprom does not work with any earlier 5.4.P08* software. If you have a new CPU card, use bootprom 1.40 or The asterisk * represents a letter from A to Z. 5.4.P0LB Warning Bootprom version 1.40 or greater is required to run with the new CPU cards. 6.0.R00A 6.1.R R000 Bootprom Version or greater 1.40 or greater 1.50 Note The respective.xrc file is contained in the directory with the same name. Example: T10BP140.xrc would be found in the T10BP140 directory. T10BP150.xrc would be found in the T10BP150 directory.

30 Boot Prom Software Updates Page 30 of 99 Directory Example Figure 7 shows a Vanguard 7310 Directory selected. C:\Vanguard\SFW_IMGS\7310\COLDLOAD Note Under the SFW_IMGS directory all the Vanguard products are listed. To select a Vanguard 6455 the path would be: C:\Vanguard\SFW_IMGS\6455\COLDLOAD C: Vanguard SFW_IMGS 7310 COLDLOAD Figure 7. COLDLOAD Directory 10)Once completed, the 7300 shows Restarting. Change your terminal speed immediately back to The unit should automatically reboot and go to ONS, provided that the bootprom and ONS images are compatible.

31 Boot Prom Software Updates Page 31 of 99 Note If the ONS images are not compatible, the node responds by removing the current image and prompts the user with a download coldloader message. If you received this message check the table in step 9. The table contains the correct compatibility information. To load a compatible ONS image, repeat these steps substituting the ONS image instead of the bootprom image instruction in step 8. 11)Upon completion of loading a compatible image, the node restarts. Boot Prom Information for the new Controller Card Any controller card numbered 75836G01 with revision D or greater REQUIRES the new boot prom code and must not be downgraded past You must NOT load an earlier version of boot prom or attempt to load software with a Vanguide CD prior to release 5.4.P0LB. This new card is functionally equivalent to the original card, but does require new boot prom code and coldloaders to operate. This new boot prom code is release 1.40 or greater. The new 1.40 or greater boot prom is fully compatible with the original controller card and all software versions that worked with boot prom revision If you use an older Vanguide CD to load an older image, it attempts to downgrade the boot prom which renders the controller card inoperable and it will have to be replaced. In order to prevent inadvertently loading boot prom revision 1.30 onto a new system controller card, please discard any CD's previous to the 5.4.P0LB CD. For more information, refer to the Vanguard 7300 Controller Card Hardware Advisory Notice (Part Number T ) located on the web at: Also refer to the Boot Prom Software Updates section on page 24 of this Software Release Notice.

32 Boot Prom Software Updates Page 32 of 99 Controller Card Board Assembly Number Location Refer to Figure 8 to locate your board assembly number: Label Figure 8. Board Assembly Number Label Vanguard 7300 CPU Card Upgrade The Vanguard 7300 Series MCP750 (part number 75836G02) system cards are supported by software releases 6.1.T14A and greater. If you have a part number 75836G02 system card and are running older versions of release 6.1, a new 6.1 software patch is required (6.1.T14A). The system cards have a different revision PCI-PCI bridge than previous system cards (part number 75836G01). The new system cards are not being recognized by software older than 6.1.T14A. Software patch 6.1.T14A must be installed when using part number 75836G02. For more information reference the 7300 Hardware Advisory Notice (part number T0258).

33 Software Improvements Page 33 of 99 Software Improvements Introduction Corrected Limitations This section describes specific improvements to the Applications Ware software. It includes: Corrected limitations Customer-initiated Change Requests Central Voice Switching Table - All Products Central Voice Switching Table lookups indicate the wrong entry if a blank entry exists. (DRCaa22754) This is fixed Vanguard 7300 Series, DSP Configuration Crash A DSP failure occurred when using a certain configuration. The failure occurred when using a certain T1/E1 card, DSPM daughtercard and when voice calls were disconnected. (DRCaa23026) This is fixed. Quad FXO ports Booting to the Correct State Intermittently Quad FXO ports may not boot to the correct state during a node boot (cold or warm). This condition can be observed within page three of the ports Detailed Port Statistics. (DRCaa23122) Figure 9. Detailed Port Statistics - Correct State Figure 9 shows that the port statistics page reports the following conditions as the current port state:

34 Software Improvements Page 34 of 99 Rx State = 1000 and Voice State = IDLE_UNCON - This means that the port has booted to the correct state. Figure 10 shows that the port statistics page reports the following conditions as the current port state: Rx State = 0000 and Voice State = IDLE_UNCON - This means that the port has booted to the incorrect state. Figure 10. Detailed Port Statistics - Incorrect State If the Rx State = 0000 this means that: the port has booted to an incorrect state the port is not physically connected to a PBX Station or CO trunk This is fixed. Vanguard 6400 Series Event Log Port Information When a Vanguard 6455 is defaulted with an ISDN data card in slot 1 the node comes up and alarms appear in the event log for ports 51-53, even if a quad card is not installed. (Ports are for the quad FXS/FXO card.) If you have a quad FXS port installed and configured in slot 2, and you remove this card and install a single FXO the log should show a problem. The node comes up, but there is no log that states cannot boot ports because of a hardware mismatch. (DRCaa23067) This is fixed. Vanguard 6455 PRI-DATA and PRI-Voice Alarm Errors Upon completion of a node boot, level one alarms are generated for every virtual port mapping table entry with Virtual Port Type configured as PRI-DATA or PRI-VOICE. Example: (1) JUN :25 Assert 897 vpmt.c (DRCaa22532) This is fixed.

35 Software Improvements Page 35 of 99 Vanguard 340, Vanguard 6400 Series - G.711 Coder Types Do Not Appear Under Voice Port Statistics Voice port statistics do not show that G.711 coders are available in the build. (DRCaa23042) This is fixed. Time Slot Number is always One on the First Page of the Statistics - Vanguard 6400 Series When there are multiple voice calls connected with the same T1/E1 interface, the "Time Slot" value on the first page of the Virtual Port Statistics always shows the time slot number of the first virtual port associated with that T1/E1 interface. (DRCaa22116) This is fixed. Vanguard 6560 QLLC State QLLC state remains at LINK_OPENED after the DCP reconnection timeout. (DRCaa22766) This is fixed. Improper Default Bridge Link/Router Interface Numbers for LAN Ports Vanguard 7300 Series All LAN ports receive the same default bridge link (1) and router interface number (1) when the node is defaulted. (DRCaa21838) This is fixed. NS Strings with Port Number for Primary Ethernet card does not work With dual Ethernet cards, Vanguard 6520, 6560 and 6400 Ethernet cards are unable to handle Network Services Table's Port/Station Identifier if the Primary Ethernet card's strings have port number after LSC-ETH. The strings entered into the Network Services Entry for LLC to SDLC Stations on the first Ethernet ports are limited to: LSC-ETH1, LSC-ETH2,...LSC-ETH250, or LSC-ETH*. (DRFaa15760) This is fixed. Ethernet PMC Installed - Ethernet Port Null - Vanguard 7300 Series The Ethernet port 101 does not work if you load a CMEM that was created on a node that did not have an Ethernet PMC installed, into a node that does. If you attempt to look at the port s statistics the node states that it does not exist. Attempting a port boot indicates it is a NULL port (DRCaa22566) This is fixed. All Vanguards - Directory Limitation when Creating Images Vanguide Application Builder and Service Patches can only be installed under a directory that is no more than eight characters (DOS 8.3 format), since Vanguide Builder calls a third party image LINKER which only supports the directory/file name in DOS 8.3 format. (DRFaa19749) This is fixed.

36 Software Improvements Page 36 of 99 SNABSC HPAD and TPAD Entries - Vanguard 6455, 7300 Series The Destination Control Unit Address and Destination Device Address parameters in the SNABSC entry in HPAD must match one of the following set of parameters of BSC3270 TPAD device table, for the device it is connecting to: (DRCaa22909) 1) BSC Control Unit Address and BSC Device Address. 2) Destination Control Unit Address and Destination Device Address. When placing the call from HPAD, the Destination Control Unit Address and Destination Device Address must match the BSC3270 device table parameters: BSC Control Unit Address and BSC Device Address. When placing the call from TPAD, the Destination Control Unit Address and Destination Device Address must also match the BSC3270 device table parameters: Destination Control Unit Address and Destination Device Address. This is fixed. Single DLCI Multiplexing SNA/IP/IPX Causes Node Crash - All Products RFC1490 Single DLCI Multiplexing and De-Multiplexing SNA/IP/IPX will cause the node to crash. If you configure the string FRISNA-xSy as either a source or destination in the PVC Setup Table and then boot the node, the node will not come up. The node will repeatedly crash. Multiplexing IP and IPX in the same DLCI works fine. (DRFaa16306) This is fixed. Vanguard 7300 Series BGP Initial Configuration The initial configuration of BGP requires a warm boot. (DRFaa19411) This is fixed. Vanguard 7300, 6455 ISDN D-Channel Statistics Reports Statistics are incorrect for a Vanguard 7300 or 6455 node configured for ISDN PRI (5ESS, Network). When you connect the T1 PBX cable to the Interface, and the RED Alarm clears, the D-channel will go ACTIVE and all virtual ports report IDLE. If you do not place a call within one minute the D-Channel reports that it is DOWN and the voice ports report OUT OF SERVICE. If you place a call it will go through This is fixed. Vanguard 320, SoTCP Calls not Connecting SoTCP calls (data or voice) are not connecting if the SoTCP "TCP Keep Alive Timer" is disabled. If enabled, a SoTCP boot does not initialize the timer. A warm boot is required. (DRFaa19651) This is fixed.

37 Software Improvements Page 37 of 99 Customer Initiated Change Requests These Change Requests were reported to Customer Service and interim patch releases were released to fix the problems. These Change Requests are incorporated into Release 6.2.R000, and where applicable, interim patch releases have been replaced by Release 6.2.R000: Change Request (CR#) Limitation Number Release Where Problem Was Reported Interim Patch Release Replaced by Release 6.2 Problem Description DRFaa S T4QA All Vanguards - Node crashes with a no room for LS Node error DRFaa T2JA 5.6.T4FC Vanguard 6400 Series voice problems due to random noise on the line and unclear voice calls DRFaa T44A 6.0.T1PA Vanguard 320 if a call is generated from a ISDN remote end, the port does not send Call Proceeding message to the remote end DRFaa T44A 6.0.T1PA Vanguard 320 is unable to receive calls due to incorrect filtering of the ISDN IEs DRFaa R00A 6.0.T1PA Vanguard 6400 Series echo canceller is not working properly on the 4-port FXO cards DRFaa R00A 5.6.T4JA Vanguard 6400 Series when NAT transfers the RIP v2 routes, it uses the route's network mask. It should use the route's subnet mask DRFaa P02A 6.0.T19C Vanguard 7300 Series table overflow error, router needs to be rebooted DRFaa R00A 6.0.T14A Vanguard 7300 Series voice port hangs in the IDLE_CON state DRFaa T16A 6.0.T1MA Vanguard 6400 block size greater than 2046 cannot cross TPA-X.25 to TPA-TCP. TPA-TCP locks up and needs to be rebooted DRFaa20489 DRFaa S S100 N/A N/A Vanguard 6400 Series node crashes with a Program Exception Encountered error.

38 Software Improvements Page 38 of 99 Change Request (CR#) DRFaa T16E 6.0.T1PA Vanguard 6400 Node crashes frequently when processing digital voice traffic DRFaa T1EA 6.0.T1EB Vanguard 6400 Series problem installing dual E1 into slot two. When using transparent CCS for E1 in slot 2, then booting the TBOP port, E1 crashes DRFaa R00A N/A Vanguard 6400 Series CPU utilization statistics were inaccurate DRFaa20700 DRFaa21067 DRFaa20635 DRFaa20705 DRFaa20779 DRFaa R p019C 6.0.R00A 6.0.T1CA 6.0.S T16C N/A 6.0.T19D N/A 6.0.T1CB 6.0.T16D N/A Vanguard 7300 Series RIP does not accept advertised route. Internally generated subnet routes are taken precedence over RIP routes. Vanguard 340 node crashed with FAULT: Data TLB Miss Exception Encountered DRFaa S100 N/A Vanguard 6435/6455 cannot manage Frame Relay traffic properly DRFaa R T01A Vanguard 340, 6435/6455 Software builder problems occur when Quad FXS/FXO and FT1/ FE1 features are selected DRFaa iR00M 6.0.T1RA Vanguard 6400 Series NAT external dynamic address assignment does not work correctly after idle time DRFaa T2A 6.0.T1SA Vanguard Bisync conversion is not working properly within a single node Limitation Number DRFaa20746 DRFaa21008 Release Where Problem Was Reported 6.0.T15A 6.0.T19C Interim Patch Release Replaced by Release 6.2 N/A 6.1.T13A Problem Description Vanguard 7300 Series node crash with ISI 750 Exception Encountered error.

39 Software Improvements Page 39 of 99 Change Request (CR#) Limitation Number Release Where Problem Was Reported Interim Patch Release Replaced by Release 6.2 Problem Description DRFaa T1QA 6.0.T1QA Vanguard 6400 when a 2780 TPAD and 2780 device bid for the line at the same time a NAK/ ACK loop is generated DRFaa R000 N/A Vanguard 7300 Series SDLC statistics are not displaying correctly DRFaa S100 N/A Vanguard 340 lost CMEM due to attached modem with echo enabled DRFaa aSP1 6.1.T11A Vanguard 7300 Series MIB incorrectly represents an internal IP address DRFaa R000 N/A Vanguard 6400 When a TFTP or Telnet is issued from Vanguard routers, outgoing IP interface is used as IP address source DRFaa T16A 6.0.T16E Vanguard 6400 when using SNMP QoS Statistics Query the node crashes with a Data TLB Miss Exception Encountered error DRFaa R iR00N Vanguard 6400 Code alarms and Debug alarms are enabled DRFaa R iR00N When you have a Quad FXS card installed in port two of a V340 and then go into CLI and do a getdes command it reports NONE for the port DRFaa S100 N/A Vanguard 7300 Series unable to build an image with IP Tunneling.

40 Software Improvements Page 40 of 99 Change Request (CR#) Limitation Number Release Where Problem Was Reported Interim Patch Release Replaced by Release 6.2 Problem Description DRFaa sp1 6.0.T1TA When a STATUS message is received, Telenetworks software records the cause code in NLCB context. The next message to be received is overwritten (corrupted) by Telenetworks because the recorded cause code is not zero DRFaa T16C N/A Vanguard 340 node crashed FER FAULT: Program Exception Encountered DRFaa R000 N/A Vanguard 6400 BRI Dial on demand does not work in an French network DRFaa T19C 6.0.T19D Vanguard 7300 FRI stations are not recovering without a station boot DRFaa R00A N/A All Vanguards - when using route control (none, <list> to block a subnet) the router stops accepting all routes DRFaa21028 N/A N/A Vanguard Terminal does not capture data correctly DRFaa T17A 5.6.T17C Vanguard 340 when using H323, a bit should be initialized as zero before calling H323_RAS SendMsg DRFaa R00A N/A Vanguard 320 NAT Static Port Binding. Port numbers over change DRFaa R00A N/A Vanguard 6455 Ethernet errors running 10 FULL DRFaa S T1XA Vanguard 6400 detailed link statistics not working properly DRFaa T02A 6.1.T02C Vanguard 7300 SoTCP fails with Debug Alarm IDCM invalid packet type 1.

41 Software Improvements Page 41 of 99 Change Request (CR#) Limitation Number Release Where Problem Was Reported Interim Patch Release Replaced by Release 6.2 Problem Description DRFaa iR00U 6.1.T12A Vanguard 7300 cannot run Channelized T1 data using 56K channels with B8ZS and ESF DRFaa T02B 6.1.T02C Vanguard 7300 conditional default route is not being advertised until node boot DRFaa S T13A Vanguard 7300 ATM FRST X.25 profiles does not support Extended Frame and Packet Sequence Counting DRFaa R000 N/A Vanguard 6400 MIB tables not indexed correctly DRFaa R T14A Vanguard 7300 Revision K System Processor cards reset before getting to the OK prompt DRFaa T02B 6.1.T02C Vanguard 7300 PPP single T1 port and 4 T1 MLPPP bundle produce errors on every RIP update DRFaa R T13A Vanguard 7300ATM FRST X.25 profile does not support Window Subtractor DRFaa R T1YA Vanguard 6400 when telco ISDN cables are connected to BRI CD, statistics show layer one state is loop test DRFaa R00A 6.1.T13A Vanguard 7300 AAM Station Down is a medium alarm and it should be a high alarm DRFaa S200 N/A Vanguard 6400 cannot use the IP address of the outbound Interface as the source IP address DRFaa S T13A Vanguard 7300 ATM alarm does not indicate which ATM station the error occurred on.

42 Known Software Limitations Page 42 of 99 Known Software Limitations Introduction RTP Header Compression This section lists limitations known to exist in Release 6.2.R000 Applications Ware software. Vanguard 7300 Default Value for the W Window Packet Parameter In release 6.1 the default value for the W Packet Window parameter for FRI AnnexG station configuration has been changed from 2 to 7. When a 6.1 release software loaded node is connected to a 6.0 release software loaded node is connected to each other via FRI AnnexG with default settings, this causes mismatch in packet layer window size and the connection does not work properly causing large delays or no data going through. (DRFaa20377) Workaround: This is a matter of mismatched configuration and setting the W Packet Window parameter to be the same in the two nodes will allow the connection to work properly. RTP Header Compression Interoperability Between Cisco and Vanguard Managed Solutions Products over Frame Relay Limitations Incompatible Cisco Features- There are a few Cisco proprietary features that must be disabled in order to ensure proper interoperability over Frame Relay links. The table below identifies the incompatible features. Feature tcp header-compression Frame relay end-to-end keepalives Cisco discovery protocol Comments Vanguard Managed Solutions products do not support tcp header compression over Frame Relay. TCP header compression must be disabled on Cisco Frame Relay interfaces. Encapsulation for keep alive packets is Cisco proprietary and as a result is not supported on links between Vanguard Managed Solutions and Cisco nodes. CDP must be disabled on links connected to non-cisco devices. Protocols Not Supported - Vanguard Frame Relay links configured for CENCAP encapsulation do not support Transparent Bridging traffic. Configuration - The Number of Session to be Compressed parameter must not be configured to a value greater than 255 when the encapsulation is configured to CENCAP. Cisco products are limited to 8-bit Context Identifiers (CIDs) over Frame Relay. Configuring a Vanguard node for more than 255 sessions will cause it to use 16-bit CIDs.

43 Known Software Limitations Page 43 of 99 Descriptions Encrypted (SAM) Tunnel Encrypted (SAM) Tunnel over WAN/LAN with (RTP+UDP/UDP)+IP Header compression is not working for certain size UPD-IP packets where IP packet length is greater than 46 (Version 5.5 and 5.6). Compression works for IP packets where the IP packet length is less than 46. (INDaa01629) Workaround: At present, there is no workaround. Node crashes when Bridge is configured on VPN over LAN When you have TB Bridge traffic over the LAN Tunnel (Tunnel over LAN Link), the traffic from TB-1 is transported to TB-2 and from TB-2 to TB-1 over Tunnel. Refer to Figure 11 below: (TB-1) LAN Tunnel (ETH-1) (TB-2) PC Node----ETH BN BN ETH PC Node (BL-2) 100 (BL-1) (BL-1) 200 (BL-2) Figure 11. TB Bridge Traffic over A LAN Tunnel The tunnel carrier ETH-1 does not have Bridge enabled. If the user (by mistake) enables the Bridge Link (BL-1) corresponding to ETH-1 which is the tunnel physical link, the node starts to repeatedly crash until the Bridge Link (BL-1) is disabled. (INDaa01627) Workaround: In the practical scenario, you do not have to enable the Bridge link corresponding to the ETH physical link of Tunnel. To avoid the node crashing, disable the Bridge Link (BL-1) corresponding to the ETH-1 (which is the Tunnel carrier). This workaround does not impact the other functionality's. All the functionality (including Bridge Traffic over LAN Tunnel) will work as usual. Basic Rate Interface (BRI) Boot - Vanguard 6400 Series, Vanguard 320 A BRI interface does not recover with the first BRI interface boot following a node boot. A second BRI interface boot clears and recovers the interface. (DRFaa18340) Workaround: Boot the interface twice. Alarms when Doing Warm or Cold Boot of Release Vanguard 6455 The alarm message "DBG-Error-Module:L3 Function:L3_Go Error:L3_Get_NLCB failed" may display when you boot the node during the handling of the T314_timer expiry. These alarms do not impact the node's functionality. (DRCaa22131) Workaround: At present, there is no workaround. T1 N. American ISDN B-Channels appear IDLE - Vanguard 6400 Series When you look at the detailed PRI statistics with the D-channel connected, all of the associated B-channels are shown to be in an IDLE state, even if some of the channels are not configured in the ISDN interface. (DRCaa22080) Workaround: At present, there is no workaround.

44 Known Software Limitations Page 44 of 99 Digital Voice Server Card - Vanguard 6400 Series T1/E1 Interface 5 will not get initialized if Interface 4 is not configured. T1/E1 Interface 7 will not get initialized if Interface 6 is not configured. (DRCaa21619) Workaround: Always configure both interfaces even if only the second interface on the card is used. Packet Re-construction Statistic Running 8kbps is Inaccurate - Vanguard 6400 Series When the time for packets to reach DSP exceeds the smoothing-delay time, DSP increments the reconstruct packet counter. With 60 voice ports configured and Voice Activity Detection (VAD) turned on, excessive reconstructed packets are reported. (DRCaa21596) Workaround: At present, there is no workaround. Received PRI Voice SETUP messages with Incompatible Coder are Not Rejected - Vanguard 6400 Series If a PRI Voice virtual port is configured incorrectly as U-Law (or A-Law) and receives a SETUP from the PBX with the opposite bearer capability of A-Law (or U_Law), the call is not rejected. When the call goes through, the audio quality is unsatisfactory. (DRFaa15495) Workaround: Be sure to configure the PRI Voice virtual port correctly to match the PBX. PAD Port Dynamic Configuration - Vanguard 6560, 6400 Series When a node is configured for Dynamic Configuration, a PAD port running as a PVC connection cannot switch to SVC mode unless the PAD port is dynamically booted. If you fail to boot the PAD port dynamically, the port reverts to an unusable state and you see these symptoms: The PAD port sends this error message: Cannot forward data, there is no connection. There is no associated PVC entry in the PVC Connection Summary table. The PAD port statistics show Port State as PAD. (DRFaa11231) Workaround: At present, there is no workaround. Configuring the Date in the Vanguard 6400 Series Products In the Vanguard 6400 node record, the range for the Date/Year record is 1988 to Two limitations exists: On the Vanguard 6425, 6430, and 6450, if you enter a date and time beyond Feb 6, 2037, 6:28:10, the node resets the date to an arbitrary date. On the Vanguard 6435 and 6455, if you enter a date between 2088 and 2100, the node subtracts 100 years from the date and set the date to a value between 1988 and (DRFaa11666). Workaround: At present, there is no workaround.

45 Known Software Limitations Page 45 of 99 Vanguard 6560 Input/Output Signal Level - Statistics The statistics for a Vanguard 6560 with a Voice Server Feature Card and a Vanguard 6560 with a DSPM/SM card differ in the display of the Input/Output Signal Level. For a Voice Server Feature Card: The input signal level statistic displays the actual input level on the line. This differs from the DSPM/SM card which displays the input level after gain/loss adjustments. The output signal level statistics displays the power on the line after gain/loss adjustments. This is also true for the DSPM/SM card. (DRCaa21113). Workaround: At present, there is no workaround. CTP Alarms Cause CLI To Lock Up - Vanguard 6400 Series When running a CLI script, the terminal locks up if an alarm comes out while that CLI operation is in progress. (DRFaa13008) Workaround: To avoid this, do not turn alarms on when CLI scripts are being run. If this lockup occurs in a node configured with APAD, press CONTROL+P and then type clr to escape from the CTP. If this lockup occurs in a node configured with ATPAD, type +++ath to escape from the CTP. FAX Statistics in Detailed Voice Port Statistics - Vanguard 6560 These FAX statistics on the second page of the Detailed Voice Port Statistics are not supported by the Voice Server Feature Card: FAX Transmission FAX Transmission Unsupported Format The value for these FAX statistics remains at 0. The number of FAX pages transmitted is provided by FAX page transmitted and FAX page transmission statistics. (DRCaa21172). Workaround: At present, there is no workaround. Encryption Channel Summary Statistics - Vanguard 6400, 6560 and 340 Encryption Channel Summary Statistics can display DATA when the channel claims to be in a NONDATA state. (DRFaa15846) Workaround: At present, there is no workaround. VPN Tunnels with RUIHC Limitation - All Products Configuring the maximum number of Tunnels (255) with RUIHC on each tunnel., causes the node to not come up or reset continually. (DRFaa17913) Workaround: To configure and use the maximum number of tunnels with RUIHC (255) use tunnel boot instead of node boot. In the RUIHC profile configuration of each tunnel have the parameter Number of sessions to be compressed configured to less than 100. Four Digit Virtual Port Number (Destination Subaddress) Vanguard 7300 Series The four digit virtual port number cannot be used as the destination subaddress. Only three digit subaddresses are allowed. (DRCaa22259)

46 Known Software Limitations Page 46 of 99 Workaround: The three digit Hunt Group must be used. If you need to target a virtual port, that virtual port should have a unique Hunt Group value. Software Image Naming Convention is Different - Alternate and Current Vanguard 7300 Series The software image naming convention is different for the Vanguard 7300 platform. In the Vanguard 7300 platform, you are able to boot from the Alternate image and the system shows that it was booted from Alternate. The Alternate image does not become the Current image, as in the other Vanguard products. (DRCaa22270) Note When using the other (non-73xx) Vanguard products, when you boot from Alternate, the Alternate image becomes the Current image. Workaround: At present, there is no workaround. Vanguard 7330 Power Supplies When the Vanguard 7330 Version 1 or a 7310 or 7330 Version 2 is configured with multiple power supplies, each power supply shares the load. If a power supply should enter a failure condition, the second power supply provides power for the entire system. Failure conditions can be determined by viewing the LED on each power supply. Power supply fail conditions are not reported as alarm conditions through the CTP menu or SNMP trap. The only failure indication is the LED associated with the failed power supply. If one of the power supplies fail, you will be operating in a non-redundant mode. (DRCaa22496) Workaround: None. Periodically check the power supply LEDs. RTP+UDP Compression - Vanguard 6455 Compression may not occur on LCONs with RTP and UDP compression enabled, (RTP or RTP+UDP) when non-rtp UDP packets are passed over the LCON. The characteristics of the user data portion of the UDP packet can cause all the transmit compression contexts to be consumed such that no compression occurs. This condition may persist while the non-rtp UDP data is present on the LCON. Once the data is removed, the contexts are released. (DRCaa22524). Workaround: Configure UDP compression only on links which carry RTP and UDP traffic. Limit non-rtp UDP data to a range of ports not configured for RTP compression. Vanguard 7300 Series H.323 Statistics In certain configurations, once a call is established, the PSTN port statistic show that TX and RX pps do not match the H.323 port statistics. The H.323 port pps rate is 1 or 2 pps less than the PSTN port. It should be equal. (DRFaa18071) Workaround: At present, there is no workaround. Vanguard 7300 Series Embedded Web Group Configuration When you configure the voice port interface type (FXS), the next parameter is Signaling Mode. When you change the port interface type to E&M, the next parameter should change to Signal Type. Currently the next menu displayed is Signaling Mode. (DRFaa18769) Workaround: At present, there is no workaround.

47 Known Software Limitations Page 47 of 99 Password Limitation BGP - All Products The Vanguard Router supports limited passwords. Cisco supports MD5. Currently we do not have Authentication compatible with Cisco. MD5 should be supported in the Vanguard products in future releases. (DRFaa18829) Workaround: At present, there is no workaround. Building Older Images Follow the instructions listed in the workaround to revert back to an older build image (if you have installed the Vanguide Application Release 6.0.R00A from the 6.0.R00A CD). (DRFaa18867) Workaround: Start Vanguide Software Builder, insert the older Vanguide release CD (A release before 6.0.R00A, example: 5.6.R000 CD) into CD driver. In Vanguide Software Builder, select the "Settings" menu, then change "CD ROM directory:" to say D:\Motorola (if D is the CD driver letter). Then you are able to build an image for a release before 6.0.R00A BSC Message Size Limitation - Vanguard 6400 Series An error may occur when 3270 BSC handles large message sizes. If a host sends a message that is larger then the 254 characters allowed in a block, when transmitted on the TPAD end, the first block ends with the End of Text Block (ETB). Once there is an acknowledgment received for the first block, the TPAD sends a End of Transmission (EOT) before sending the second block, which ends the message, and has the BSC controller write to the device. This causes an error in some applications as it expects the whole message in multiple blocks before the EOT. (DRFaa18075) Workaround: At present, there is no workaround. Vanguard 7300 Port Speed The "Port Speed:" field in the FRI, PPP, X25, SDLC, and TBOP statistics screen is the configured Port Speed for the Vanguard 7300 Serial Port. If the "Clock Source" parameter in the FRI, PPP, X25, SDLC, or TBOP serial port is set to EXT or EXTLP, the "Port Speed:" field in the FRI, PPP, X25, SDLC, and TBOP statistics screen may not match the speed of the actual clock on the serial line. (DRCaa21740) Workaround: To determine the actual speed on the serial line, an external datascope or protocol analyzer needs to be attached. The "Clock Speed" parameter in the Port Record needs to be configured to the actual Clock Speed that the port is attached to. Improper Configuration for LLC-SDLC-Stations - Vanguard 7300, Vanguard 6400 Series LLC-SDLC-Station Records in the Second Ethernet Station Table become the Records of the First Ethernet Station Table if the First Ethernet port record is deleted. (DRCaa21097) (DRCaa22325) Workaround: The first work around is not to delete the first Ethernet port. The second work around is to re-configure the LLC-SDLC-Station Records with the Ethernet port that has not been deleted.

48 Known Software Limitations Page 48 of 99 Vanguard 7300 Series Call Not Transferred with ALT-Dest set in VST When placing a call from either an FXS, FXO or E&M to H.323 and the destination does not answer the phone (ALT_DEST_NO_ANSER) or the phone is busy (ALT_DEST) and the alternate destination is either an FXS, FXO or E&M, there is no audio. (DRCaa22329) Workaround: At present, there is no workaround. Vanguard 7300 Series Large QoS Parameter Values May Disable QoS Although the QoS Parameter fields can be configured to a maximum of 1000 or (in case of IP Flow Table Size), this is subject to the node s RAM availability. The software checks the node for sufficient RAM to accommodate a QoS parameter configuration. If the node s memory size is less than the requirement for the configuration, the software disables QoS. (DRCaa22432) Workaround: Configure the minimum required parameters for QoS. Incorrect Configuration Can Disable QoS Scheduler Feature Vanguard 7300 Series The sum of the %BW per custom PHB configured in the custom PHB menu must be the same as the %BW for custom PHB configured in the Queueing and Scheduling Profile Parameter. Failing to do so leads to the disabling of the QoS Scheduler feature. For example, if the %BW for custom PHB in the Queueing and Scheduling Profile parameter is set to zero, the %BW per custom PHB must all be zero to satisfy the above condition. (DRCaa22433) Workaround: At present, there is no workaround. Vanguard 7300 Series Using the Same TCP Session for Local and Remote Nodes If the remote node initiates a call using SoTCP and the local node attempts to make a call in the reverse direction over the same TCP session, a new session might be required to make the call. (DRCaa22437) Workaround: Include in the Mapping Table, all possible IP addresses that might be used by a remote destination node. For more information, refer to the Serial Protocol over TCP Manual (Part number T ). Vanguard 7300 Series CLI setscript with T1/VPMT does not Download CLI setscript with T1/VPMT does not download after using the getscript. CLI errors occur because the VPMT is configured before the voice port or the T1 port. (DRFaa16143) Workaround: If the CLI set script file includes the create vpmt statement, move it behind the create virtual port statement. If the set minimum-cpu statement is in the script file, turn on the debug mode. Vanguard 7300 Series H.323 Limitation on Number of Calls When a Vanguard 7300 is configured to use H.323, the total number of voice calls over all H.323 ports is limited to 216. (DRCaa23314) Workaround: Use 6.0S100 or if you require H.323 Supplementary Services Support, a 6.1 based software patch will be available shortly. Please contact your customer service representative.

49 Known Software Limitations Page 49 of 99 Large SDLC-to-LLC2 (SLAC) Calling Addresses - All Products For incoming X.25 calls over Frame Relay SVC, Vanguard network services updates the X.25 table with calling address and station ID, interpreting the calling address as XX...X**. That is, the last two digits are assumed to be sub address and the rest as node address. For calls using large sub addresses, such as SDLC SLAC station calls, this leads to a wrong node address. For example, a calling address of , where 0822 is the sub address, is interpreted as 20008** with 22 as the sub address. (DRFaa16491) Workaround: The sub address must be two digits long, or X.25 calls should be made in one direction only. Vanguard 7330 Data Buffer Performance When the number of Data Buffers used reaches a level above the configured WAN congestion start blocking threshold (default of 89 percent), the throughput of the node may drop to a very low level until the steady state buffer utilization drops below the configured stop blocking WAN congestion threshold (default of 86 percent). A number of factors effect the number of buffers used, including the number of SVCs used and the rate of data transfer through the node. (DRFaa16497) Workaround: Reduce number of connections (SVCs) or traffic through node in order to reduce number of buffers used. V.34 Modem Calls not Connecting - Vanguard 6560, 6400 and 7300 V.34 Modem calls do not consistently connect over Autocall and Transparent connection types. (DRCaa22907) Workaround: At present, there is no workaround. Virtual Links between two OSPF Area Border Routers Fail - Vanguard 7300 Series Virtual links between two OSPF Area Border Routers do not work properly. (DRFaa17076) Workaround: At present, there is no workaround. Voice Server Card Removal - Vanguard 7300 Series If the voice server card is removed from the T1 card and there is a voice configuration in the node, the node will not boot. (DRCaa22978) Workaround: Delete the voice configuration or default the node before removing the voice server card. BGP Global TCP Segment Size and Peer TCP Segment Size Vanguard 6560 The Global TCP segment size is overriding peer TCP segment size if any one peer is configured for zero. (DRFaa19391) Workaround: At present, there is no workaround. Voice Port Loopback Test Output Level - Vanguard 340 and 6400 Series The local voice port loopback test does not display the correct output level. (DRCaa23032) Workaround: At present, there is no workaround.

50 Known Software Limitations Page 50 of 99 Vanguard 6455 Conversion Options in Vanguide Builder When creating an image for the Vanguard 6455 using the Vanguide builder, the LLC-TR and LLC-FR LLC-to-SDLC Conversion options do not appear under the BSC-to-SNA Conversion option. Only LLC-ETH appears and this is automatically selected. (DRFaa19586) Workaround: If the user wishes to create a Vanguard 6455 image that supports either BSC 3270 to SNA Conversion or BSC 2780 to SNA Conversion that runs over a LLC Token Ring session or LLC Frame Relay session, the user should: 1) Select BSC 3270-to-SNA Conversion or BSC 2780-to-SNA Conversion from the BSC-to-SNA Conversion Options 2) Then select LLC Token Ring Conversion and/or LLC Frame Relay Conversion from the IBM SNA Features list. Vanguard 340 Series Audio on the FXS port Passing 6.3k audio on three of the four ports on the quad FXS card causes MIPS errors. MIPS errors are causing static on the output audio. (DRCaa23051) Workaround: At present, there is no workaround. Alarms Can Indicate Poor Voice Quality - Vanguard 6400 Series If you are running G.729 (8kbps), you might see the MED level alarm reported: VOICE-125 DEBUG INFO: OP_ALARM_NFY: Error_indication 0, Error_code c. This could indicate poor voice quality. (DRCaa21755) Workaround: If this alarm message appears and you are experiencing voice quality problems, run G.723 (6.3kb). Vanguard 340 Quad FXS Board Failure A board failure occurs when you place a call between any voice port and a quad FXS voice port, and then enter the diagnostics menu and initiate a Voice Port Loopback test while the call is up. The quad FXS board fails with a background diagnostics failure. (DRCaa23031) Workaround: At present, there is no workaround. Vanguard 340, Vanguard 6400 Series - Rx Offhook/Onhook Filter Timer The Rx Offhook/Onhook Filter Timer is not working correctly on the Quad FXS card. (DRCaa23046) Workaround: At present, there is no workaround. Vanguard Data Compression Not Supported in ATM Bypass Stations LCON's connected to ATM stations via PVC connections will not work properly with Vanguard's Frame Data compression. (DRFaa21038) Workaround: LCON frame data compression is supported through SVC connection via FRST module to ATM station. Vanguard V90 Cannot Establish a PPP connection over a V23 Modulation Mode V23 Modulation Mode is selectable on a PPP modem port, but it is not supported. (DRCaa23442) Workaround: Select a faster modulation mode for PPP.

51 Known Software Limitations Page 51 of 99 Vanguard 7300 NAT Node Reset If a large number of NAT entries are configured each having multiple interfaces, upon a Boot-Router-NAT-ALL the router could reset (with an FER) instead of just booting the NAT entries. (DRFaa20065) Workaround: In order to avoid having the router reset, only configure a single interface per NAT entry. If an entry requires to be applied to multiple interfaces, you may configure multiple entries, but depending on the number of entries the node may reset upon boot. SNABSC Requires a Second Boot SNABSC Requires two LU boots when adding a record. (DRFaa21434) Workaround: To add a new SNABSC device configuration and activate it: 1) Go to Main-Configure-SNA Features Configure-SNA to BSC Conversion Device Table. Configure a new device in a blank entry in "SNA to BSC Conversion Device Configuration." 2) Go to Main-Boot-SNA Features Records Boot-SNA to BSC Conversion Device. Do the boot of the new entry in "Boot SNA to BSC Conversion Device Records" TWICE. 3) At this point, the SNA Host must activate the LU assigned to the new device to start the new session. Vanguard 7300 MAC Address Filter Table Displays an Extra Hyphen The MAC Addresses displayed in the MAC Address filter table are not displaying correctly. (DRCaa23181) Workaround: Ignore the extra hyphen. Node Crash May Occur When Running RADIUS Voice Accounting and H.323 Voice Calls The RADIUS voice accounting data forwarding function should not be used together with H.323 voice calls, it may cause a node crash (DRCaa23452). When running H.323 voice call together with RADIUS, the forwarding of voice accounting data to the RADIUS server should be disabled. Follow the procedure described below: (Accounting data is available through SNMP MIB query.) Main Menu->Configuration->Configure RADIUS->Configure RADIUS Client Entry Number: 1/ [1] Radius Application: Default/ [1] Enable Radius Client: Disabled/enable [1] Authentication Method: Remote-then-Local/ [1] Username/Password Buffer Number: 0/; Storing updated record in configuration memory Entry Number: 2/ [2] Radius Application: Default/Voice-Accounting [2] Enable Radius Client: Disabled/;

52 Known Software Limitations Page 52 of 99 All Vanguards Using Radius and HP Openview - Two RADIUS MIB Files Corrupted Two RADIUS MIB files were corrupted on the 6.2 CD: rfc2618a.mib and rfc2620a.mib. This caused a problem with the HP Openview MIB complier. Workaround: Download the corrected versions of the.mib files from our external web site at: Files "mib62ux.zip" and "mib62pc.zip" contain the Unix and PC 6.2 files.

53 Documentation Supplements Page 53 of 99 Documentation Supplements Introduction Documentation Supplements This section lists supplemental information to the current set of user documentation. Fax Over H.323 Backward Compatibility Fax over H.323 is not backward compatible with pre-5.4 versions of software. Optimum Operation of Voice over an LCON For optimum operation of voice over an LCON the Voice SVC parameter within the LAN Connection Table Configuration Menu should be set to enable.

54 User Documentation Page 54 of 99 User Documentation Organization User documentation supporting the 6.2 Applications Ware is organized as: Vanguard Applications Ware Basic Protocols IP and LAN Feature Protocols SNA Feature Protocols Serial Feature Protocols Multiservice Feature Protocols Multimedia Feature Protocols Each of these sets, which are available on our website, consists of several manuals. The contents of each set and the manual part numbers are described below. Note For information about obtaining these documents, refer to the How to Obtain User Documentation section on page 57. Vanguard Applications Ware Basic Protocols The Vanguard Applications Ware Basic Protocols Manual (Part Number T0106) consists of these manuals: Vanguard Configuration Basics (Part Number T0113) Frame Relay (Part Number T ) Trans Polled Async (Part Number T ) SNMP (Part Number T ) Async Bypass (Part Number T ) SLIP (Part Number T ) TELNET (Part Number T ) Point to Point (Part Number T ) Command Line Interface (Part Number T ) X.25 Configuration Basics (Part Number T0107) Configuration for APAD/ATPAD (Part Number T0110) Bandwidth Management (Part Number T0108)

55 User Documentation Page 55 of 99 IP and LAN Feature Protocols SNA Feature Protocols Serial Feature Protocols The IP and LAN Feature Protocols Manual (Part Number T0100) consists of these manuals: Vanguard Router Basics (Part Number T ) Bridging (Part Number T ) IP Routing (Part Number T ) OSPF (Part Number T ) SIP (Part Number T ) SoTCP (Part Number T ) IPX (Part Number T ) AppleTalk (Part Number T ) Protocol Priority (Part Number T ) Quality of Service (Part Number T ) Asynchronous Transfer Mode (Part Number T ) 7300 Series T3 ATM (Part Number T ) Border Gateway Protocol (BGP-4) (Part Number T ) Ethernet Basics (Part Number T0109) Token Ring Basics (Part Number T0111) The SNA Feature Protocols Manual (T0101) consists of these manuals: BSC 2780/3780 (Part Number T ) BSC 3270 (Part Number T ) IBM 2260 (Part Number T ) SDLC (Part Number T ) XDLC (Part Number T ) AS/400 Communication Server (Part Number T ) BSC 3270-to-SNA Conversion (Part Number T ) BSC 2780/3780-to-SNA LU0 Conversion (Part Number T ) The Serial Feature Protocols Manual (T0102) consists of these manuals: Burroughs Poll/Select (Part Number T ) NCR BSC (Part Number T ) TBOP (Part Number T ) NCCP (Part Number T ) TCOP (Part Number T ) SHDLC (Part Number T ) T3POS (Part Number T ) 3201 (Part Number T ) X.42 (Part Number T )

56 User Documentation Page 56 of 99 TNPP (Part Number T ) TPDU (Part Number T ) SPP (Part Number T ) AC100 (Part Number T ) ALC (Part Number T ) Multi-Service Feature Protocols Multimedia Feature Protocols Alarms and Reports Manual The Multi-Service Feature Protocols Manual (T0103) consists of these manuals: Internal DSD (Part Number T ) Multipoint X.25 (Part Number T ) Frame Data Compressor (Part Number T ) Vanguard 6560/6520 ISDN (Part Number T ) Vanguard ISDN (Part Number T ) Remote DataScope (Part Number T ) SMDS (Part Number T ) Data Encryption (Part Number T ) Virtual Private Network (Part Number T ) The Multimedia Feature Protocols Manual (Part Number T0104) consists of these manuals: Voice Technology Reference Guide (Part Number T ) Vanguard Voice Manual (Part Number T ) Vanguard Voice Hardware Reference Card (Part Number T ) The Vanguard Applications Ware Alarms and Reports Manual (Part Number T0005) is updated for Release 6.2.R000. This manual contains a listing of all alarm and report messages generated by the Vanguard Applications Ware. The manual explains the actions you must perform in order to correct unexpected network situations that might arise while using any of the Applications Ware licenses on Vanguard Products.

57 How to Obtain User Documentation Page 57 of 99 How to Obtain User Documentation Introduction There are two ways to obtain software documentation: Download the most current, up-to-date document files from the On-line Library on our World Wide Web page. Use the electronic navigation and search capability provided on the Vanguide 6.2.R000 CD-ROM. World Wide Web On the Web Finding New Feature Documentation Getting New Documentation From the Web The latest Vanguard user documentation, including detailed descriptions of new features and enhancements, is available on the World Wide Web. Find your information faster and easier when you use the Product Documentation website. Eliminate the need to flip through several documentation updates. For example, suppose feature enhancements are made to ISDN over the course of several software releases. Each release provided a separate document describing the details of those ISDN features. The details of the features are described in the ISDN Manual in context with the rest of the feature information. The full set of Vanguard Documentation is available for download from the Vanguard Managed Solutions Product Documentation website: To read the files, you need a copy of Adobe Acrobat Reader with Search. This application is free from many locations on the World Wide Web. You can define how you use Acrobat with your Web browser.

58 How to Obtain User Documentation Page 58 of 99 Keeping a Set of Manuals Current Keep a current set of documentation for Release 6.2.R000. To download a current printed set acquire a: Connection to the Vanguard Managed Solutions product documentation website: Printer Copy of Adobe Acrobat for your platform Download manuals from the WWW for the desired features you need. Print the files, and replace the pages in your set of documentation with the new version. Documentation on the Vanguide 6.2.R000 CD-ROM Using the Vanguide 6.2.R000 CD-ROM The Vanguide 6.2.R000 CD-ROM contains: All Vanguard Product documentation up to the current shipping release. Default Vanguard Applications Ware software images. The CD-ROM supports Windows and UNIX platforms and includes a free copy of Adobe Acrobat Reader with Search functionality. Acrobat Reader provides a powerful search functionality across the entire volume of titles. Note When installing Acrobat (4.0 or greater) Reader, you may be required to accept the Software Licence Agreement. Acrobat Reader is freeware.

59 Vanguide CD-ROM with Vanguard Software Builder Page 59 of 99 Vanguide CD-ROM with Vanguard Software Builder Introduction Vanguard Software Builder What is Vanguard Software Builder? Detailed Information With Release 5.3, the Vanguide and Vanguide Plus! CD-ROMs are consolidated into one CD-ROM called Vanguide CD-ROM with Software Builder. Vanguard Software Builder is now included on the Vanguide CD-ROM. This software application was previously available as a separate product on the Vanguide Plus! CD-ROM. Vanguard Products come with a factory default Applications Ware software image. However, you can create your own Applications Ware, with a specific mix of features by using Vanguard Software Builder. This application lets you create custom features sets with features and functions suited for your specific needs. The features available for selection depend on the Applications Ware License you purchased. Vanguard Software Builder operates on Windows XP, Windows NT, Windows 2000, 95 or 98 platform. Vanguard Software Builder is part of the Vanguide Application Set. This set also includes the Vanguide Application Manager which provides access to the Software Loader and Software Builder applications. Once Software Builder is installed, you can: Select a specific software release Choose the product which you are loading/configuring Create a name and 2-digit number for the Applications Ware Package you want to create Follow a series of command prompts to select features/protocols for your Package For more information, refer to Vanguard Software Builder Manual (Part Number T0030).

60 Applications Ware for the Vanguard 320 Page 60 of 99 Applications Ware for the Vanguard 320 Introduction Vanguard 320 Applications Ware Vanguard 320 supports Vanguard Managed Solution s broad library of protocols, thereby providing a diverse set of solutions via a single hardware platform. Vanguard 320 offers multiprotocol access, depending on the Applications Ware Package you purchase. Vanguard 320 must be ordered with one of the Applications Ware listed in the tables in this section. Release 6.2.R000 makes available these Applications Ware for the Vanguard 320. Each Package supports a suite of default features. Other features, however, can be added by using Vanguard Software Builder. For more information, refer to the Vanguide CD-ROM with Vanguard Software Builder section on page 59. Note When using Vanguard Software Builder, be sure to make note of the warnings regarding memory limitations. Information about the Applications Wares is divided into two tables. The first table lists each Applications Ware and its file number. The second table lists each Applications Ware and its features (default features as well as non-default features). Applications Ware Name Source Filename Version String Description Filename IP+ Applications Ware 62R000k11.xrc 6.2.R000_@IP+_V320 62R000k11.des SNA+ Applications Ware 62R000k12.xrc 6.2.R000_@SNA+_V320 62R000k12.des Multiservice Applications Ware 62R000k15.xrc 6.2.R000_@MS_V320 62R000k15.des

61 Applications Ware for the Vanguard 320 Page 61 of 99 Vanguard 320 Features IP+ SNA+ Multi- Voice Special Service Network Management SNMP D D D TELNET D D D TFTP D D D CLI D D D Embedded Web HTTPD L L L Async ATPAD D D D APAD L L L ISDN SoftSCC L L L ISDN-NOAM L L L ISDN-EURO L L L ISDN-ASIA L L L Vanguard Voice Relay G.723 D A G.729 L A CVSELP L A H.323 L A Digital Voice /6455 Vanguard T1/E1 Digital Voice Server Voice Options (All Products) Centralized Voice Switch L A VOICE-IP-ENCAPSULATION L A LAN Router IP D D D D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

62 Applications Ware for the Vanguard 320 Page 62 of 99 Vanguard 320 Features (continued) IP+ SNA+ Multi- Service Voice Special Router IPX L L L LAN Option Protocols LLC-Eth D L LLC-TR IPXWAN L L L OSPF L L L BGP-4 Appletalk L L L Bandwidth on Demand (LD-Bal) L L L IP-Multicast D D L Router Proxy D D D Router Discovery L L L Network Address Transl L L L Policy Based Routing L L L RTP Header Compression L L L TR-Bridge ETH-Bridge D D D XLB-Bridge Tunnel L L L IPSEC DHCP Client L L L Radius L L L Network Protocols FRF12 L L L FRA (only for backward compatibility) L L FRI (includes FRA) D D D FR SVC A X.25 D D L D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

63 Applications Ware for the Vanguard 320 Page 63 of 99 Vanguard 320 Features (continued) IP+ SNA+ Multi- Service Voice Special SMDS L MX25 L PPP L L L PPPoE L L L SoTCP (=Voice Relay Enc. In IP) L L L Fractional T1/E1 L L L ATM Protocols ATM Protocols Serial Asynchronous Protocols ASYNC-BYPASS L L L IBM2260 A SLIP L L L TNPP A TNPP-ROUT L X.42 (GSC) A T3POS L L T3POS over TCP L L DATAPAC L L L SPP-PAD A AC100 A Serial Synchronous Protocols SDLC D L XDLC L L TBOP D D A LLC-FR D L SHDLC L L TBOP-BYPASS D L X32 L L L D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

64 Applications Ware for the Vanguard 320 Page 64 of 99 Vanguard 320 Features (continued) IP+ SNA+ Multi- Service Voice Special Serial Character-Oriented Protocols BSC3270 L L BSC2780 L L BSTD A TCOP L L TCOP-BYPASS L L NCRBSC A RS366 L L TPDU Adaptors TPA-TPDU L L TPA-SDLC A TPA-3270 L L TPA-2780 L L TPA-TCP L L TPA-UDP L L Node Features ATCIF (AT Dial/Telnet) L L L LBU L L L DCP D L DSCOPE L L DSD L NCCP L L BCST A NUI L L L QOS Features TOW L L L QoS - Protocol Priority (5.3M) L L L D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

65 Applications Ware for the Vanguard 320 Page 65 of 99 Vanguard 320 Features (continued) IP+ SNA+ Multi- Service QoS - Diff Serv (5.4) D D D Voice Special FRAME Data Comp L L D BSC 3270-to-SNA Conversion BSC 2780/3780-to-SNA LU0 Conv. AS/ Comm. Server Security and VPN Security: Encryption & VPN- DES & 3DES D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

66 Applications Ware for the Vanguard 340 and 342 Page 66 of 99 Applications Ware for the Vanguard 340 and 342 Introduction Vanguard 340 and 342 Applications Ware Vanguard 340 and 342 support Vanguard Managed Solution s broad library of protocols, thereby providing a diverse set of solutions via a single hardware platform. Vanguard 340 and 342 offer multiprotocol access, depending on the Applications Ware Package you purchase. Vanguard 340 and 342 must be ordered with one of the Applications Ware listed in the tables in this section. Release 6.2.R000 makes available these Applications Ware for the Vanguard 340 and 342. Each Package supports a suite of default features. Other features, however, can be added by using Vanguard Software Builder. For more information, refer to the Vanguide CD-ROM with Vanguard Software Builder section on page 59. Note When using Vanguard Software Builder, be sure to make note of the warnings regarding memory limitations. Information about the Applications Wares is divided into two tables. The first table lists each Applications Ware and its file number. The second table lists each Applications Ware and its features (default features as well as non-default features). Applications Ware Name Source Filename Version String Description Filename IP+ Applications Ware 62R000p11.xrc 6.2.R000_@IP+_V340 62R000p11.des SNA+ Applications Ware 62R000p12.xrc 6.2.R000_@SNA+_V340 62R000p12.des Multiservice Applications Ware 62R000p15.xrc 6.2.R000_@MS_V340 62R000p15.des

67 Applications Ware for the Vanguard 340 and 342 Page 67 of 99 Vanguard 340 and 342 Features Network Management IP+ SNA+ Multi- Service SNMP D D D TELNET D D D TFTP D D D CLI D D D Embedded Web HTTPD L L L Async ATPAD D D D APAD L L L ISDN SoftSCC L L L ISDN-NOAM L L L ISDN-EURO L L L ISDN-ASIA L L L Vanguard Voice Relay G.723 & G.711 D A G.729 & G.711 L A CVSELP & G.711 L A H.323 L A Quad FXS D A Quad FXO D A Digital Voice /6455 Vanguard T1/E1 Digital Voice Server Voice Options (All Products) Centralized Voice Switch D A VOICE-IP-ENCAPSULATION L A D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com Voice Security Special

68 Applications Ware for the Vanguard 340 and 342 Page 68 of 99 Vanguard 340 and 342 Features (continued) IP+ SNA+ Multi- Service Voice Security Special LAN Router IP D D D Router IPX L L L LAN Option Protocols LLC-Eth D D LLC-TR IPXWAN L L L OSPF D L L BGP4 L L L Appletalk L L L Bandwidth on Demand (LD-Bal) L L L IP-Multicast D D D Router Proxy D D D Router Discovery L L L Network Address Transl L L L Policy Based Routing L L L RTP Header Compression L L L TR-Bridge ETH-Bridge D D D XLB-Bridge Tunnel L L L IPSEC A DHCP Client L L L Radius L L L Network Protocols FRF12 L L L FRA (only for backward compatibility) L L FRI (includes FRA) D D D D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

69 Applications Ware for the Vanguard 340 and 342 Page 69 of 99 Vanguard 340 and 342 Features (continued) IP+ SNA+ Multi- Service Voice Security Special FR SVC A X.25 D D D SMDS L MX25 L PPP D D D PPPoE L L L SoTCP (=Voice Relay Enc. In IP) L L L Fractional T1/E1 L L L ATM Protocols All Supported ATM Protocols Serial Asynchronous Protocols ASYNC-BYPASS D D D IBM2260 A SLIP D D D TNPP A TNPP-ROUT L X.42 (GSC) A T3POS L L T3POS over TCP L L DATAPAC L L L SPP-PAD A AC100 A Serial Synchronous Protocols SDLC D L XDLC L L TBOP D D A LLC-FR D D SHDLC L L D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

70 Applications Ware for the Vanguard 340 and 342 Page 70 of 99 Vanguard 340 and 342 Features (continued) IP+ SNA+ Multi- Service TBOP-BYPASS D D X32 L L L Serial Character-Oriented Protocols BSC3270 L L BSC2780 L L BSTD TCOP D D TCOP-BYPASS D D NCRBSC RS366 L L TPDU Adaptors TPA-TPDU L L TPA-SDLC TPA-3270 L L TPA-2780 L L TPA-TCP L L TPA-UDP L L Node Features ATCIF (AT Dial/Telnet) L L L LBU D D D DCP D L DSCOPE L L DSD L NCCP L L BCST NUI L L L QOS Features D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com Voice Security Special A A A A

71 Applications Ware for the Vanguard 340 and 342 Page 71 of 99 Vanguard 340 and 342 Features (continued) IP+ SNA+ Multi- Service TOW D D D QoS - Protocol Priority (5.3M) L L L QoS - Diff Serv (5.4) D D D Voice Security Special FRAME Data Comp L L D BSC3270-to-SNA Conversion BSC2780/3780-to-SNA/LU0 Conv. AS/ Comm. Server Security and VPN Security: Encryption & VPN- A DES & 3DES D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

72 Applications Ware for the Vanguard 6435/6455 Page 72 of 99 Applications Ware for the Vanguard 6435/6455 Introduction Vanguard 6345/ 6455 Applications Ware This section provides detailed information about the Applications Ware available for Vanguard 6435 and the Vanguard Release 6.2.R000 makes available the following Applications Ware for the Vanguard 6435/6455. Each Applications Ware supports a suite of default features. Other features, however, can be added by using Vanguard Software Builder. For more information, refer to the Vanguide CD-ROM with Vanguard Software Builder section on page 59. Note When using Vanguard Software Builder, be sure to make note of the warnings regarding memory limitations. Information about the Applications Ware is divided into four tables. The first two tables list each model s Applications Ware and file information. The last two tables list each model s Applications Ware and its default, optional, and add-on features Applications Ware Name Source Filename Version String Description Filename IP+ Applications Ware 62R000q11.xrc 6.2.R000_@IP+_V643562R000q11.des SNA+ Applications Ware 62R000q12.xrc 6.2.R000_@SNA+_V643562R000q12.des Multiservice Applications Ware 62R000q15.xrc 6.2.R000_@MS_V R000q15.des 6455 Applications Ware Name Source Filename Version String Description Filename IP+ Applications Ware 62R000s11.xrc 6.2.R000_@IP+_V R000s11.des SNA+ Applications Ware 62R000s12.xrc 6.2.R000_@SNA+_V R000s12.des Multiservice Applications Ware 62R000s15.xrc 6.2.R000_@MS_V R000s15.des

73 Applications Ware for the Vanguard 6435/6455 Page 73 of 99 Vanguard 6435 Features IP+ SNA+ Multi- Service Network Management SNMP D D D TELNET D D D TFTP D D D CLI D D D Embedded Web (HTTPD) L L L Async ATPAD D D D APAD L L L ISDN SoftSCC ISDN-NOAM L L L ISDN-EURO L L L ISDN-ASIA L L L Voice Security * AS/400 BSC Special Vanguard Voice Relay G.723 & G.711 D A G.729 & G.711 L A CVSELP & G.711 L A H.323 L A Quad FXS D A Quad FXO D A Digital Voice /6455 Vanguard T1/E1 Digital Voice Server Voice Options (All Products) Centralized Voice Switch D A D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. *Note for the 6400 Series: AS/400 BSC - BSC support is available for the Vanguard 6455 only. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

74 Applications Ware for the Vanguard 6435/6455 Page 74 of 99 Vanguard 6435 Features (continued) IP+ SNA+ Multi- Service VOICE-IP-Encapsulation L A Voice Security * AS/400 BSC Special LAN Router IP D D D Router IPX L L L LAN Option Protocols LLC-Eth D D LLC-TR L L IPXWAN L L L OSPF L L L BGP4 L L L Appletalk L L L Bandwidth on Demand (LD-Bal) L L L IP-Multicast D D D Router Proxy D D D Router Discovery L L L Network Address Transl L L L Policy Based Routing L L L RTP Header Compression L L L TR-Bridge Token Ring ETH-Bridge D D D XLB-Bridge L L L Tunnel L L L IPSEC DHCP Client L L L Radius L L L A Network Protocols D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. *Note for the 6400 Series: AS/400 BSC - BSC support is available for the Vanguard 6455 only. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

75 Applications Ware for the Vanguard 6435/6455 Page 75 of 99 Vanguard 6435 Features (continued) IP+ SNA+ Multi- Service FRF12 L L L FRA (only for backward L L compatibility) FRI (includes FRI) D D D FR SVC X.25 D D D SMDS L MX25 L PPP D D D PPPoE L L L SoTCP (=Voice Relay Enc. In IP) L L L Fractional T1/E1 L L L Voice Security * AS/400 BSC Special A ATM Protocols ATM Protocols L Serial Asynchronous Protocols ASYNC-BYPASS D D D IBM2260 A SLIP D D D TNPP A TNPP-ROUT L X.42 (GSC) A T3POS L L T3POS over TCP L L DATAPAC L L L SPP-PAD A AC100 A Serial Synchronous Protocols D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. *Note for the 6400 Series: AS/400 BSC - BSC support is available for the Vanguard 6455 only. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

76 Applications Ware for the Vanguard 6435/6455 Page 76 of 99 Vanguard 6435 Features (continued) IP+ SNA+ Multi- Service SDLC D L XDLC L L TBOP D D A LLC-FR D D SHDLC L L TBOP-BYPASS D D X32 L L L Serial Character-Oriented Protocols BSC3270 L L BSC2780 L L BSTD TCOP D D TCOP-BYPASS D D NCRBSC RS366 L L TPDU Adaptors TPA-TPDU L L TPA-SDLC TPA-3270 L L TPA-2780 L L TPA-TCP L L TPA-UDP L L Voice Security * AS/400 BSC Special A A A Node Features ATCIF (AT Dial/Telnet) L L L LBU D D D DCP D L D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. *Note for the 6400 Series: AS/400 BSC - BSC support is available for the Vanguard 6455 only. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

77 Applications Ware for the Vanguard 6435/6455 Page 77 of 99 Vanguard 6435 Features (continued) DSCOPE L L DSD NCCP L L BCST IP+ SNA+ Multi- Service NUI L L L QOS Features TOW D D D QoS - Protocol Priority (5.3M) L L L QoS - Diff Serv (5.4) D D D FRAME Data Comp L L D BSC 3270-to-SNA Conversion BSC 2780/3780-to-SNA LU0 Conversion AS/ Comm. Server L Voice Security * AS/400 BSC A Special A Security and VPN Security: Encryption & VPN- A DES & 3DES D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. *Note for the 6400 Series: AS/400 BSC - BSC support is available for the Vanguard 6455 only. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

78 Applications Ware for the Vanguard 6435/6455 Page 78 of 99 Vanguard 6455 Features IP+ SNA+ Multi- Service Network Management SNMP D D D TELNET D D D TFTP D D D CLI D D D Embedded Web (HTTPD) L L L Async ATPAD D D D APAD L L L ISDN SoftSCC ISDN-NOAM L L L ISDN-EURO L L L ISDN-ASIA L L L Voice Security * AS/400 BSC Special Vanguard Voice Relay G.723 & G.711 D A G.729 & G.711 L A CVSELP & G.711 L A H.323 L A Quad FXS D A Quad FXO D A Digital Voice /6455 Vanguard T1/E1 Digital Voice Server D A Voice Options (All Products) D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. *Note AS/400 BSC - BSC support is available for the Vanguard 6455 only. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

79 Applications Ware for the Vanguard 6435/6455 Page 79 of 99 Vanguard 6455 Features (continued) IP+ SNA+ Multi- Service Centralized Voice Switch D A VOICE-IP-ENCAPSULATION L A Voice Security * AS/400 BSC Special LAN Router IP D D D Router IPX L L L LAN Option Protocols LLC-Eth D D LLC-TR L L IPXWAN L L L OSPF L L L BGP4 L L L Appletalk L L L Bandwidth on Demand (LD-Bal) L L L IP-Multicast D D D Router Proxy D D D Router Discovery L L L Network Address Transl L L L Policy Based Routing L L L RTP Header Compression L L L TR-Bridge Token Ring L L L ETH-Bridge D D D XLB-Bridge L L L Tunnel L L L IPSEC A DHCP Client L L L Radius L L L D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. *Note AS/400 BSC - BSC support is available for the Vanguard 6455 only. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

80 Applications Ware for the Vanguard 6435/6455 Page 80 of 99 Vanguard 6455 Features (continued) IP+ SNA+ Multi- Service Voice Security * AS/400 BSC Special Network Protocols FRF12 L L L FRA (only for backward L L compatibility) FRI (includes FRA) D D D FR SVC X.25 D D D SMDS L MX25 L PPP D D D PPPoE L L L SoTCP (=Voice Relay Enc. In IP) L L L Fractional T1/E1 L L L A ATM Protocols All Supported ATM Protocols L Serial Asynchronous Protocols ASYNC-BYPASS D D D IBM2260 A SLIP D D D TNPP A TNPP-ROUT L X.42 (GSC) A T3POS L L T3POS over TCP L L DATAPAC L L L SPP-PAD A AC100 A D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. *Note AS/400 BSC - BSC support is available for the Vanguard 6455 only. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

81 Applications Ware for the Vanguard 6435/6455 Page 81 of 99 Vanguard 6455 Features (continued) IP+ SNA+ Multi- Service Voice Security * AS/400 BSC Special Serial Synchronous Protocols SDLC D L XDLC L L TBOP D D A LLC-FR D D SHDLC L L TBOP-BYPASS D D X32 L L L Serial Character- Oriented Protocols BSC3270 L L BSC2780 L L BSTD TCOP D D TCOP-BYPASS D D NCRBSC RS366 L L TPDU Adaptors TPA-TPDU L L TPA-SDLC TPA-3270 L L TPA-2780 L L TPA-TCP L L TPA-UDP L L A A A Node Features ATCIF (AT Dial/Telnet) L L L LBU D D D DCP D L D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. *Note AS/400 BSC - BSC support is available for the Vanguard 6455 only. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

82 Applications Ware for the Vanguard 6435/6455 Page 82 of 99 Vanguard 6455 Features (continued) DSCOPE L L DSD NCCP L L BCST IP+ SNA+ Multi- Service NUI L L L QOS Features TOW D D D QoS - Protocol Priority (5.3M) L L L QoS - Diff Serv (5.4) D D D L Voice Security * AS/400 BSC Special A FRAME Data Comp L L D BSC 3270-to-SNA Conversion BSC 2780/3780-to-SNA LU0 Conversion AS/ Comm. Server A A A Security and VPN Security: Encryption & A VPN- DES & 3DES D: Default License Feature. L: In License; add with Software Builder. A: Add-on Upgrade License Feature P: Premium Feature; contact a representative for more information. *Note AS/400 BSC - BSC support is available for the Vanguard 6455 only. Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com

83 Applications Ware for the Vanguard 7300 Series Products Page 83 of 99 Applications Ware for the Vanguard 7300 Series Products Introduction Vanguard 7300 Applications Ware This section provides detailed information about the Applications Ware available for Vanguard Release 6.2.R000 makes available the following Applications Ware for the Vanguard Each Applications Ware package supports a suite of default features. Other features, however, can be added by using Vanguard Software Builder. Information about the Applications Ware is divided into these two tables: Vanguard 7310 Applications Ware Applications Ware Name Source Filename Version String Description Filename IP+ 62R000t11.xrc 6.2.R000_@IP+_V R000t11.des SNA+ 62R000t12.xrc 6.2.R000_@SNA+_V R000t12.des Multi-Service 62R000t15.xrc 6.2.R000_@MS_V R000t15.des Vanguard 7330 Applications Ware Applications Ware Name Source Filename Version String Description Filename IP+ 62R000u11.xrc 6.2.R000_@IP+_V R000u11.des SNA+ 62R000u12.xrc 6.2.R000_@SNA+_V R000u12.des Multi-Service 62R000u15.xrc 6.2.R000_@MS_V R000u15.des

84 Applications Ware Features Page 84 of 99 Applications Ware Features Introduction This table lists each Applications Ware license and the features it offers: Vanguard 7300 Features IP+ SNA+ Multi- Service Network Management SNMP D D D TELNET D D D TFTP D D D CLI D D D Embedded Web (HTTPD) D D D Async ATPAD D D D ISDN T1/E1/PRI Data (North American in Default) D D D T1/E1/PRI Data (European) L L L T1/E1/PRI Data (Asia) L L L T1/E1/PRI Voice D D D (includes all voice signaling, NA in Default) T1/E1/PRI Voice L L L (includes all voice signaling, Europe) Digital Voice Voice Relay with G and G.729a D D D Voice Relay Encapsulated in IP (SoTCP) D D D H.323 v.2 Standards Based Voice D D D Voice Options (All Products) Centralized Voice Switch D D D VOICE-IP-ENCAPSULATION D D D LAN Router IP D D D Router IPX D D D LAN Option Protocols LLC-Eth D D IPXWAN D D D AS/400 Special

85 Applications Ware Features Page 85 of 99 Vanguard 7300 Features (continued) IP+ SNA+ Multi- Service OSPF D D D BGP4 D D D Bandwidth on Demand (LD-Bal) D D D IP-Multicast D D D Router Proxy D D D Router Discovery D D D Network Address Translation D D D Policy-Based Routing D D D RTP Header Compression D D D Token Ring D D D Eth-Bridge D D D DHCP Client D D D Radius D D D Network Protocols FRF.12 D D D FRI (includes FRA) D D D FR SVC X25 D D D PPP D D D PPPoE L L L SoTCP (Voice Relay Encl. in IP) D D D T1/E1 Interface D D D T3/E3 ATM D Serial Synchronous Protocols SDLC D D TBOP D D LLC-FR D D X32 Node Features ATCIF (AT Dial/Telnet) D D D LBU D D D DCP D D AS/400 Special A

86 Applications Ware Features Page 86 of 99 Vanguard 7300 Features (continued) IP+ SNA+ Multi- Service QOS Features TOW D D D QoS - Diff Serv (5.4) D D D Data Compression D D D SNA Features BSC 3270-to-SNA Conversion D D BSC 2780/3780-to-SNA LU0 Conversion D D AS/ Comm. Server D = in default image for particular license A = add-on feature (part of upgrade license) L = in license Specials - license available from service only - submit end user customer info (including all contact info), unit type and count to: karengarcia@vanguardms.com AS/400 A Special Note Token Ring for the Vanguard 7300 Series is available in 6.0 Point Release 01A or greater.

87 MIB Downloading Instructions for Non-Vanguard Managed Solutions SNMP Managers Page 87 of 99 MIB Downloading Instructions for Non-Vanguard Managed Solutions SNMP Managers Introduction This section lists Vanguard MIB files needed for SNMP management of Vanguard devices when using a non-vanguard Managed Solutions SNMP Network Management System (NMS). Obtaining MIB Files Vanguard MIB files for your non-vanguard Managed Solutions NMS are available from the Vanguide 6.2.R000 CD-ROM. Refer to your Vanguide 6.2.R000 CD-ROM user documentation for the directory location of the MIB files. You can also download MIB files from the internet. The address for the server is: mibs On the internet, there is one ZIP file for the PC and one ZIP file for UNIX. You must unzip the ZIP file to get the MIB files. The contents of these two ZIP files are identical. However, the formats of the files in these two ZIP files are slightly different due to the way PCs and UNIX systems handle text files.depending on the protocols and options provided by the Applications Ware image installed in your node, you might not need all the MIB files.see the Required Files and Loading section below for details on the files you should have to support SNMP management for Vanguard products. Upgrading 9000 OMS to support 6.2 software Install the 9000 OMS version 6.1 from CD first (for details on installation please refer to Software_Release_Notice.pdf on the CD). If you do not have 9000 OMS version 6.1 CD, you need to contact your VanguardMS sales representative to purchase the CD prior to the 9000 OMS release 6.2 installation. 1) Download DFF62.zip from software_and_tools/#9000, unzip the zip file with Winzip to obtain all the 6.2 DFF files and the trap.conf file. 2) Procedure for parsing DFF files into the 9000 OMS database: For the MS Windows system: Parsedff.exe is located in the path /Vanguard/motnm/bin->Parsedff.exe (Parsedff.exe is the executable program for parsing). Gather all the DFF files to be parsed on the desktop or to the path selected. The DFF files match the platforms. Example: MOTNAv6455, MOTNA7310, MOTNA7330, MOTNAv320, MOTNAv340. Make a different folder with the release name to put all the parsed DFF files in. Example: A folder named 6.2dffs. At the DOS prompt, change the directory to the new folder name or to the directory where you chose to keep the parsed DFF files in.

88 MIB Downloading Instructions for Non-Vanguard Managed Solutions SNMP Managers Page 88 of 99 Execute the parsedff program. Example c:\vanguard\motnm\6.2dffs>..\bin\parsedff.exe MOTNAv340.dff..\db\nmdb.db MOTNAv340.dff -> is the dff file to be parsed...\bin\parsedff.exe -> is where the parsedff.exe program is located. Executing this program results in users getting the message parsed successfully. For the Unix system, logon as root Parsedff is located in the path /opt/motnm/tools->parsedff (Parsedff is the executable program for parsing). Gather all the DFF files to be parsed to the path and locations selected. The DFF files match the platforms. Example: MOTNAv6455, MOTNA7310, MOTNA7330, MOTNAv320, MOTNAv340. Make a different folder with the release name to put all the parsed DFF files in. Example: A folder named 6.2dffs. At the shell prompt change the directory to where the new folder name or to the directory you chose to keep the parsed DFF files in. Execute the parsedff program. Example #> /opt/motnm/tools/parsedff MOTNAv340.dff /opt/motnm/db/nmdb.db MOTNAv340.dff -> is the dff file to be parsed. /opt/motnm/tools/parsedff -> that s where the parsedff program is located. Executing this program results in users getting the message parsed successfully. Update trap.conf for HP-OV: For Unix (logon as root), enter, #> /opt/ov/bin/xnmevents -load trap.conf For MS Windows, enter, c:\> \Program Files\HP OpenView\NNM\bin -load trap.conf 3) Download MIB62.zip from and_tools/#9000, unzip the zip file with Winzip to get all the 6.2 MIB files. 4) Load MIB file (e.g. Trap.mib) you need through HP OV MIB loading utility (from HP OV menu Options Load/Unload MIB: SNMP) MIB files changed in release 6.2 for your loading reference: New MIB files: ppp_opt.mib, pppoe_opt.mib, radius_opt.mib, rfc2618a.mib, rfc2620a.mib MIB files with new changes: bridge_opt.mib, cdx_6500.mib, eia_opt.mib, eth_opt.mib, iso3201_opt.mib, pad_opt.mib, router_opt.mib, tr_opt.mib, trap.mib 5) Download Help62.zip from software_and_tools/#9000, and unzip the zip file with Winzip to get 6.2 Help file. 6) To update the 9000 OMS Help file: For Unix (logon as root), enter, #> cp MOTBASEhelp.txt /opt/motnm/data/motbasehelp.txt For MS Windows, enter, c:\> copy MOTBASEhelp.txt c:\vanguard\motnm\data\motbasehelp.txt

89 MIB Downloading Instructions for Non-Vanguard Managed Solutions SNMP Managers Page 89 of 99 Required Files and Loading MIB Files for Options/Protocols The following MIB files are required by your NMS to perform SNMP management of Vanguard products: rfc1213.mib cdx_6500.mib These files must be loaded first and in the order shown. After you load these required files onto your NMS, you can load the MIB files for the options and protocols installed on your Vanguard hardware. See the MIB Files for Options/Protocols section below. This table lists the contents of options and protocol MIB files for Vanguard products. Use this table to determine which MIB files you need to download. Download This MIB File alc.mib bcst.mib bri.mib bridge.mib bsc2780.mib bsc3270.mib bstd.mib cdx_6500.mib de.mib dc.mib dcp.mib dsd.mib e1.mib eia.mib eth.mib frdce.mib frdte.mib fri.mib gcs.mib hub.mib ibm2260.mib If you want this option, protocol, or base MIB software ALC protocol Broadcast ISDN BRI protocol Bridging option BSC2780 protocol BSC3270 protocol Burroughs Poll/Select protocol Required base MIB for Vanguard Products MIBs Data Encryption option Data Compression option Data Connection Protection option Digital Sharing Device Option Physical E1 port EIA protocol (required file for serial protocol support) Ethernet option Frame Relay DCE option Frame Relay DTE option Frame Relay option GSC protocol Ethernet Hub option IBM2260 protocol

90 MIB Downloading Instructions for Non-Vanguard Managed Solutions SNMP Managers Page 90 of 99 Download This MIB File isdn.mib iso3201.mib mx25.mib ncrbsc.mib ns.mib pad.mib ping_opt.mib qos.mib qos_pp.mib rfc.1155.smi rfc1212.smi rfc1213.mib rfc1231.mib rfc1286.mib rfc1315.mib rfc1398.mib rfc1657a.mib rfc1850.mib rfc1903.mib rfc2496a.mib rfc1850a.mi2 rfc1850b.mi2 rfc1903.mi2 router.mib rs366.mib sdlc.mib slac.mib If you want this option, protocol, or base MIB software (continued) ISDN protocol 3201 protocol MX.25 protocol NCR Binary Synchronous protocol Network Service (required file) PAD protocol Remote Ping Option Quality of Service option - QoS-Kit- includes: QoS_CORE, QoS_CLSSIFIER and QoS_SCHEDULER Quality of Service option - QoS-PP (Protocol Priority) includes: QoS_CCM, PACKET_CLASSIFIER and PACKET SCHEDULER Structure and identification of management information Concise MIB definitions MIB-II for managing TCP/IP -based internets IEEE Token Ring MIB Definitions of managed objects for bridges Management Information Base for Frame Relay DTEs Managed objects for Ethernet-type interfaces BGP4 MIB (Converted to SNMP version 1 from the original rfc1657 mib). OSPF MIB (Requires rfc1903.mib and is converted from rfc1850.mi2 to version 1 of SNMP). Textual conventions for version 2 of SNMP (Converted from rfc1903.mi2 to version 1 of SNMP). DS3/E3 Interface Type MIB (Converted to SNMP version 1 from the original rfc2496 mib). OSPF Version 2 MIB OSPF Version 2 MIB (Trap definitions) Textual conventions for version 2 of SNMP Routing option (required file) EIA RS366 support SDLC protocol LLC Ethernet/Frame Relay/Token Ring Conversion option

91 MIB Downloading Instructions for Non-Vanguard Managed Solutions SNMP Managers Page 91 of 99 Download This MIB File spp.mib ss.mib t1e1vg.mib t1.mib t1e1.mib tbop.mib tcop.mib tdlc.mib tftp.mib tdmclk.mib tnpp.mib tow.mib tr.mib v.mib vpmt.mib wan.mib x25.mib xdlc.mib If you want this option, protocol, or base MIB software (continued) SPP protocol Switched Services (required file) Fractional T1E1 Interface option Physical T1 port Virtual T1/E1 port mapping table TBOP protocol TCOP protocol TDLC protocol TFTP option TDM Network Clock option Telocator Network Paging Protocol (TNPP) TOW option Token Ring option Voice Relay option Virtual Port Mapping Table option WAN support (required file) X.25 option XDLC protocol

92 Applications Ware RFC Compliance Page 92 of 99 Applications Ware RFC Compliance Listing This table identifies the RFCs (Request for Comments) with which Vanguard Applications Ware software is compliant. RFC Description 768 User Datagram Protocol. J. Postel. Aug Internet Protocol. J. Postel. Sep Internet Control Message Protocol. J. Postel. Sep Not all messages covered by RFC 792 are supported by Vanguard Applications Ware. 793 Transmission Control Protocol. J. Postel. Sep An Ethernet Address Resolution Protocol-or-Converting network protocol addresses to 48.bit Ethernet Address for Transmission on Ethernet hardware. D.C. Plummer. Nov Telnet Protocol Specification. J. Postel, J.k. Reynolds. May Telnet Suppress Go Ahead Option. J. Postel, J.K. Reynolds. May Standard For The Transmission Of IP Datagrams Over Public Data Networks. J.T. Korb. Sep Standard for the Transmission of IP data grams over Ethernet networks. C. Hornig. Apr Broadcasting Internet Datagrams. J.C. Mogul. Oct Broadcasting Internet datagrams in the presence of subnets. J.C. Mogul. Oct Internet Standard Subnetting Procedure. J.C. Mogul, J. Postel. Aug Proposed Bootstrap protocol (BOOTP) for ARPA-Internet W. Croft, J. Gilmore. Sept

93 Applications Ware RFC Compliance Page 93 of 99 RFC Description (continued) 1009 Requirements for Internet Gateways R.Braden, J. Postel. Jun Standard For The Transmission Of IP Datagrams Over IEEE 802 Networks. J. Postel, J.k. Reynolds. Feb Nonstandard For Transmission Of IP Datagrams Over Serial Lines: SLIP. J.l. Romkey. Jun RIP Version 2 Carrying Additional Information. G. Malkin. January Assigned values used in network protocol implementations. J. Reynolds, J. Postel. Mar Distance Vector Multicast Routing Protocol. D. Waitzman, C Partridge, S. Deering. Nov Telnet Terminal-type Option. J. Vanbokkelen. Feb Host Extensions for IP Multicasting S. Deering. Aug Requirements for Internet hosts - communication layers. R.T. Braden. Oct Requirements for Internet hosts - application and support. R.T. Braden. Oct Compressing TCP/IP headers for low-speed serial links. V.Jacobson. Feb Structure And Identification Of Management Information For TCP/IP-based Internets. M.t. Rose, K. Mccloghrie. May MIB for Network Management of TCP/IP based Internets Simple Network Management Protocol (SNMP). J.D. Case, M. Fedor, M.L. Schoffstall, C. Davin. May Transmission Of IP Datagrams Over The SMDS Service. D.m. Piscitello, J. Lawrence. Mar Concise MIB Definitions. M.t. Rose, K. Mccloghrie. Mar

94 Applications Ware RFC Compliance Page 94 of 99 RFC Description (continued) 1213 Management Information Base For Network Management Of TCP/IP-based Internets:MIB-II. K. Mccloghrie, M.t. Rose. Mar A Convention for Defining Traps for use with the SNMP. M. Rose, Editor, Performance Systems International. March IEEE Token Ring MIB. K. Mccloghrie, R. Fox, E. Decker. May IAB Official Protocol Standards. J. Postel. Aug ICMP Router Discovery Messages. S. Deering. September Definitions Of Managed Objects For Bridges. E. Decker, P. Langille, A. Rijsinghani, K. Mccloghrie. December, Inverse Address Resolution Protocol. T. Bradley, C. Brown. Jan Multiprotocol Interconnect Over Frame Relay. T. Bradley, C. Brown, A. Malis. January Management Information Base for Frame Relay DTEs. C. Brown, F. Baker, C. Carvalho. April 9, PPP Internet Protocol Control Protocol (IPCP). G. McGregor. May PPPAuthentication Protocols B. Lloyd, W. Simpson. Oct Status of Assigned Numbers J. Reynolds, J. Postel. July Type of Service in the Internet Protocol Suite P. Almquist. Jul Multiprotocol Interconnect On X.25 And ISDN In The Packet Mode. A. Malis, D. Robinson, R. Ullmann. August Novell IPX over Various WAN Media (IPXWAN). M. Allen. Sept Definitions Of Managed Objects For The Ethernet-like Interface Types. F. Kastenholz. January Multiprotocol Encapsulation over ATM Adaptation Layer 5 Juha Heinanen, July 1993.

95 Applications Ware RFC Compliance Page 95 of 99 RFC Description (continued) 1490 Multiprotocol Interconnect Over Frame Relay. T. Bradley, C. Brown, & A. Malis. July Applicability Statement For The Implementation Of Classless Inter-Domain Routing (CIDR). Internet Engineering Steering Group, R. Hinden. September An Architecture For IP Address Allocation With CIDR. Y. Rekhter & T. Li. September Classless Inter-Domain Routing (CIDR): an Address Assignment and Aggregation Strategy. V. Fuller, T. Li, J. Yu, & K. Varadhan. September Exchanging Routing Information Across Provider Boundaries in the CIDR Environment. Y. Rekhter & C. Topolcic. September Interoperation between DHCP and BOOTP. R. Droms. Oct Clarifications and Extensions for the Bootstrap Protocol. W. Wimer. Oct Classical IP and ARP over ATM M. Laubach, January OSPF Version 2. J. Moy. Mar The Network Address Translator (NAT). K. Egevang, P. Francis. May The text/enriched MIME Content-type. N. Borenstein. Jan The Point-to-Point Protocol (PPP). W. Simpson, Editor. July Definitions of Managed Objects for SMDS Interfaces Using SMIv2. T. Brown & K. Tesink, Editors. August Assigned Numbers. J. Reynolds, J. Postel. October, Requirements for IP Version 4 Routers. F. Baker. June Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2). J. Case, K. McCloghrie, M. Rose, S. Walbusser. January 1996.

96 Applications Ware RFC Compliance Page 96 of 99 RFC Description (continued) 1918 Address Allocation for Private Internets. Y. Rekhter, B. Moskowitz, D. Karrenberg, G. J. de Groot & E. Lear. February Dynamic Host Configuration Protocol. R. Droms, Bucknell University, March, DHCP Options and BOOTP Vendor Extensions. S. Alexander, Silicon Graphics, Inc., R. Droms, Bucknell University. March Definition: Differentiated Services Field (DS Field) in IPv4/IPv6 Headers. K. Nichols, S. Blake, F. Baker, D. Black. December, An Architecture for Differentiated Services. S. Blake, D. Black, M. Carlson, E. Davies, Z. Wang, W. Weiss. Dec Compressing IP/UDP/RTP Headers for Low-Speed Serial Links. S. Casner, V. Jacobson. Cisco Systems. February The Method for Transmitting PPP over Ethernet (PPPoE). L. Mamakos, K. Lidl, J. Evarts, UNET Technologies Inc., D. Carrel, D. Simone, RedBack Networks Inc., R. Wheeler, RouterWare Incorporated. February Assured Forwarding PHB Group. J. Heinanen, F. Baker, W. Weiss, J. Wroclawski. June, An Expedited Forwarding PHB. V. Jacobson, K. Nichols, K. Poduri. June, Remote Authentication Dial In User Service (RADIUS). C. Rigney, S. Willens, Livingston, A. Rubens, Merit W. Simpson, Daydreamer. June, RADIUS Accounting. C. Rigney, Livingston. June, 2000.

97 Product Declarations and Regulatory Information Page 97 of 99 Product Declarations and Regulatory Information The following sections provide information about standards compliance, safety statements, and Type Approvals. Warnings And Cautions The following special notices apply to all equipment handling procedures in this installation guide. Warning Ports capable of connecting to ports on other apparatus are defined as Safety Extra Low Voltage (SELV). To conform with EN60950, ensure that these ports are only connected to ports of the same type on other apparatus. Les ports qui sont susceptibles d être connectés à des équipements sont désignés comme TBTS. Pour garantir la conformité à la norme EN 60950, n interconnecte ces ports qu avec des ports du même type sur des autres matériels. Anschlusse, die mit anderen Geraten verbindet werden konnen, sind als SELV beschrieben. Um Konformitat mit EN zu versichern, sichern Sie es, daß diese Anschlusse nur mit den des selben Type auf anderen Geraten verbindet werden. CE Marking The mark in the following diagram appears on each Vanguard Series product, and the statement that follows explains its significance. This product is CE marked to indicate compliance with the following European Directives: 1999/5/EC Radio & Telecom Terminal Equipment (R&TTE) 73/23/EEC Low Voltage Directive (Safety) 89/336/EEC EMC Directive