These release notes describe resolved and open issues for the Cisco Broadband Operating System (CBOS) Release 2.3.9. Please refer to previous release notes for specific information concerning past releases.
For more detailed information about the information in these release notes, refer to the "Related Documentation" section. Information about electronic documentation can be found in the "Cisco.com" section.
CBOS is the common operating system for Cisco customer premises equipment (CPE). The CBOS is modeled after Cisco IOS software and features a similar command syntax and format. This operating system is bundled with the CPE products listed below and can also be downloaded from Cisco Connection Online.
Caution CBOS 2.3.9 has MD5 password encryption enabled by default.
If you are upgrading from a previous release and you are not using a password, you will not need to use passwords. If you are upgrading but you were using passwords, CBOS 2.3.9 will encrypt those passwords and save them into NVRAM. There is no change visible to the end user.
MD5 password encryption Disabled.
Since the old passwords can not be recovered,
the Enable and Exec passwords have been cleared.
To assign new passwords, use the CLI commands.
You must type "write" to persist encryption mode into memory.
You must then use the write command to make the change permanent. You can then add passwords, but they will not be encrypted.
There is an additional command named show cli command set. Enter this command to view a list of the commands you must set from the command line interface (CLI).
The set filter command information can be found in the Cisco Broadband Operating System 2.4 User Guide. That information applies to all versions of CBOS.
Information on the rfc1483 enable|disable command can be found in the Cisco Broadband Operating System 2.4 User Guide. That information applies to all versions of CBOS.
This section lists resolved issues for CBOS 2.3.9.
CSCds19142
Symptom:
Invalid login attempt via web browser not showing in syslog.
Description:
When an invalid login attempt occurred via the Web Browser, no message was entered into the syslog. This was a security issue, because someone could try to guess a password using the web browser without being noticed.
Resolution:
CBOS now enters a message into the syslog when an invalid login attempt occurs.
CSCdr98772
Symptom:
Unexpected URL parsing error when doing a Get.
Description:
Sending a URL that does not terminate with a space causes CBOS to enter an infinite loop.
Resolution:
Upgrade to release 2.3.9 or higher.
CSCds59206
Symptom:
A series of Rapid TCP Connections limits the number supported.
Description:
A script that repeatedly opens and closes a Telnet session, is unable to continue beyond a couple of thousand connections. Then, further connections are refused and the following message appears in the log: TELNET Warning Max number of clients reached
Resolution:
Upgrade to release 2.3.9 or higher.
CSCds23921
Symptom:
A 65500 ping causes CPE to freeze.
Description:
When pinging directly to a CPE with a 65500-byte ping, the CPE and console connection freeze.
Resolution:
Upgrade to release 2.3.9 or higher.
CSCds16078
Symptom:
Initial sequence numbers.
Description:
There was an issue with initial sequence numbers for a new TCP session.
Resolution:
Upgrade to release 2.3.9 or higher.
CSCdt04882
Symptom:
Password encryption format in NVRAM.
Description:
There was an issue with the way passwords were encrypted in NVRAM.
Resolution:
A set password encryption command was added beginning with release 2.3.9 that can be used to enable or disable encryption. See the "Encryption and Upgrading" section for more information.
CSCdt05853
Symptom:
Support for Intel and AMD flash for 677i platform.
Description:
CBOS monitor needs to automatically detect if the flash used has Intel or AMD firmware for the 677i platform.
Resolution:
Support for automatic recognition of Intel and AMD flash was added.
CSCdt05806
Symptom:
Users are able to set parameters not applicable to 677i platform.
Description:
Users are able to change the parameters that do not apply to 677i even when 677i is used.
Resolution:
Upgrade to release 2.3.5.016 or later.
CSCdt05622
Symptom:
Hiss problem with 675 and 678.
Description:
675 and 678 CPEs had an unacceptable level of hiss (background white noise) problem.
Resolution:
Upgrade to release 2.3.6.0 or later and appropriate firmware.
CSCds13539
Symptom:
The CPE does not generate a DHCPNAK response to client with bad IP address.
Description:
A client PC which has received an IP address from one network fails to receive t he appropriate new IP address from a second and new network when using the DHCP Server function of a 675 and 678 CPE w/ CBOS versions 2.3.5.xxx and 2.4.0.xxx.
Resolution:
Upgrade to release 2.3.8.006 or later.
CSCds20765
Symptom:
Need to close/open interface wan0-1 in order to make RIP work
Description:
A 677 CPE is configured with 2 interfaces, wan0-0/1, with RIP enabled on both interfaces. RIP updates are not sent on either of the interfaces.
Resolution:
Upgrade to release 2.3.9 or later.
CSCds30150
Symptom:
CPE freezes when pinging a host on the Internet with Record Route Count.
Description:
When pinging a host on the internet using the "-r" (record route count) option, the CPE froze.
Resolution:
Upgrade to release 2.3.9 or later.
CSCds30438
Symptom:
CPE goes idle from noise in signal.
Description:
The CPE went into an idle state while in CAP mode.
Resolution:
Upgrade to release 2.3.5 or later.
CSCdr32246
Symptom:
CPE retrain should not reset RS counters.
Description:
When the CPE WAN interface retrained, it reset all the RS counters.
Resolution:
Upgrade to release 2.3.9 or later.
CSCds74567
Symptom:
Continuous large ping packets will cause CPE to enter ROMMON mode.
Description:
When passing 1500 byte PING packets thorough a 675 CPE to an end station behind the Ethernet interface, the CPE would enter ROMMON mode.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr05562
Symptom:
DHCP server pool netmask overrides DHCP pool size command.
Description:
The DHCP server pool netmask overrode the DHCP pool size command.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr11520
Symptom:
DHCP server is handing out addresses on the wrong subnet.
Description:
The DHCP server was assigning addresses to the wrong subnet.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr14476
Symptom:
The 675 CPE returns a false busy with DOH.
Description:
The 675 CPE would remain in busy mode even when there was a DSL port available.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr14919
Symptom:
Acceptance of the enable password at the exec prompt should be an option.
Description:
Previously a feature allowed ISPs to administer a CPE without knowing the exec password. An option to disable this feature was requested.
Resolution:
A set password strict command was added to allow enforcement of strict usage of the exec password.
The CLI syntax is:
set password strict [enabled|disabled]
When this command is set to enabled, only the exec password will be accepted at the exec prompt
When the option is disabled (default), the enable password will also be accepted at the exec password prompt. Because the default NVRAM value for this option is disabled, users do not see the option when they enter the sh nvram command.
The user must already be in enable mode to set the option.
CSCdr18305
Symptom:
The 675 will stop passing traffic if 256 KB packets are passed at over 4 MB.
Description:
A 675 CPE using the SMPLSAR1 would not pass traffic during Smartbits testing if 256 KB packet sizes were run over four MB.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr22889
Symptom:
Transmit hang. Resetting SAR message appears when the 633 CPE is idle.
Description:
The 633 platform with CBOS 2.3.2 and the SMPLSAR2 chip returned a Transmit hang. Resetting SAR. message repeatedly while the CPE was idle.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr28299
Symptom:
CO 673 DHCP relay does not forward DHCP requests to Ethernet.
Description:
The DHCP Relay agent of the 673 configured as CO did not forward DHCP-Request packets to its Ethernet segment.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr28372
Symptom:
SMPLSAR2.675 CBOS 2.3.2 FTP transmit hang.
Description:
The 675 SMPLSAR2 running CBOS 2.3.2.011 would hang when FTP traffic was sent at different provision rates.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr30239
Symptom:
Commander: No warning when DOH enabled.
Description:
When running commander with DOH enabled on the CPE and CO, the number of minutes remaining before idle timeout should have displayed.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr32921
Symptom:
New values for Vendor ID and Vendor Rev. Number are required.
Description:
The Vendor ID needed to be changed to 0x46 (Cisco) from Globespan.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr33039
Symptom:
CBOS and Globespan op states get out of synch.
Description:
The CBOS operational state was shown as "Line Searching", while the Globespan operational state was "Startup training and exchange in progress". The CBOS state should have been "Line Training", not "Line Searching".
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr35815
Symptom:
CPE will detrain/retrain after the idle timeout expires.
Description:
After the 2 minutes idle timeout, the DSL line would go down and stay down based on the CPE log.
Resolution:
Upgrade to release 2.3.5 or later.
CSCdr37414
Symptom:
Multicast IGMP request packets not being forwarded.
Description:
IGMP request packets were not forwarded from a 675 client running cbos2.3.053.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr42472
Symptom:
Issuing a retrain command while the 675 CPE is already training prevents training.
Description:
If users issued the retrain command while the 675 CPE was training, it would go into a loop and prevent training.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr44119
Symptom:
Unable to set VCI 4 until after other VCIs are set.
Description:
While using RFC1483 routing, users were unable to configure wan0-3 to VPIx and VCI 4,. They had to first set VPIx to something other than 4. This problem occurred on any wan0-x interface.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr65180
Symptom:
TX count goes negative, stopping all upstream DSL traffic.
Description:
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr70375
Symptom:
RFC1483 routing mode stops passing traffic.
Description:
When users uploaded a file from a PC on the CPE Ethernet side and changed the DSL line rate on the 6130, the line would retrain and the Tx count on the CPE became very large and traffic would stop.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr76935
Symptom:
stats [bad parameter] returns different responses, including set hlp.
Description:
When users entered the stats command with invalid parameters, inconsistent responses were returned.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdr90942
Symptom:
Telnet freezes when NAT is enabled.
Description:
When NAT was enabled on the 675 CPE, the Telnet session became unstable and froze after 20 to 30 seconds.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdp31484
Symptom:
set filter should have an option to change all rules at once.
Description:
A user requested request an option in the set filter command to allow the user to turn on, off, or reset all filters using a single command.
Resolution:
The existing set filter command was extended to allow the user to specify more than one filter code (index) for some situations.
If the last parameter on the CLI command line is on, off, or reset, these commands are valid.
set filter 0 1 2 3 4 on sets filters 0, 1, 2, 3, and 4 to on state simultaneously.
set filter 3 5 7 9 off sets filters 3, 5, 7, and 9 to the off state simultaneously.
set filter 0 1 2 3 reset resets filters 0, 1, 2 and 3 simultaneously.
Up to 20 filters can be set with one CLI line.
This function is not available if the CLI line ends in parameters other than On, Off, or Reset.
CSCdp44187
Symptom:
G.LITE does not train at rate defined in ITU.992.
Description:
It was reported that G.lite did not train at the rates defined in the ITU G.992 specification.
Resolution:
The G.992 rates referenced were for G.992.1. G.lite is G.992.2. Therefore, the margin used during testing should have been set to 4dB, rather than 6dB.
CSCdp89734
Symptom:
SNMP - Ethernet port status should reflect true status.
Description:
When connecting to the 677 CPE via Telnet and issuing an snmp get command to the Ethernet port on the 677, the status of the Ethernet port was always returned as 1 (UP), regardless of the real status of the port.
Resolution:
Upgrade to release 2.3.9 or later.
CSCdp90463
Symptom:
Enable password will not work after the code upgrade.
Description:
When upgrading from CBOS 2.1.0 to 2.3.0.51, the enable password stopped working.
Resolution:
Upgrade to release 2.3.5 or later.
CSCdr77726
Symptom:
A Cisco 677 CPE device will not train up when using g.lite or g.dmt.
Condition:
When using g.lite or G.dmt on a 627 or 677, a Cisco 677 CPE device will not train up to a Cisco 6260 configured the same way.
Workaround:
Upgrade the ADI firmware to version 3.0. The name of the code required is RTBLD.BNM, available in a special file access area of CCO. You must be a registered CCO user. To download the RTBLD.BNM code, follow these steps:
Step 1 From any browser, log in to www.cisco.com.
Step 2 In Service and Support, select Software Center.
When attempting to use two or more PCs behind a CPE to do a file transfer with Microsoft networking to a Windows 2000 server, only one PC will be able to copy a file at a time.
Condition:
This occurs only under the following conditions:
Microsoft networking is the file transfer mechanism
more than one PC is attempting to do a file transfer at the same time
the CPE is running NAT
the file transfer is attempted from a Windows 2000 server on the far end of the connection.
Workaround:
Allow one PC at a time to do a file transfer using Microsoft networking, or use another file transfer method, such as FTP.
CSCds60974
Symptom:
When the CPE is set up as a DHCP client and is receiving its IP address from a DHCP server behind the terminating router (NRP on a 6400 or a 7200), the CPE may not receive an IP address from the DHCP server.
Condition:
This occurs with RFC1483 routing configured on a CPE which is configured to be a DHCP client and is trying to get DHCP information from a DHCP server over the wan interface. This problem does not apply to PPP routing, as there is no reason to use DHCP client functionality on the CPE in this situation; instead, IPCP should be used to obtain the IP address. It also does not apply if the DHCP server service is running on the 6400/7200; in this case, the CPE can receive an IP address from the DHCP server on the terminating router.
The problem that occurs is that the far-end DHCP server returns the IP address forwarded as a broadcast. The terminating router (6400/7200) receives this broadcast on its ethernet address, then, as it should, does not forward it over the ATM interfaces.
Workarounds:
There are two possible workarounds:
Put an IP helper address on the Ethernet interface of the 6400/7200 that points to the original IP address of the CPE.
Do not to attempt to have the CPE receive an IP address from a DHCP server over the WAN interface. The CPE, which is functioning as a router, should have a static IP address. If necessary, this address can be excluded from the DHCP server.
CSCds82039
Symptom:
When you attempt to set the DHCP relay command to an interface, only the wan0-0 interface is accepted as valid.
Condition:
This condition occurs when you attempt to use the eth0 interface for the DHCP relay command; for example, when SDSL modems are being used in a back-to-back environment.
Workaround:
No action is necessary. When the CPE is in the back-to-back configuration or the CPE mode is set to CO, the DHCP relay requests automatically go out the eth0 interface, even though the sho dhcp relay command shows the relay interface as wan0-0.
CSCds83490
Symptom:
Routing table updates are not received when RIPv2 is used.
Condition:
When the CPE device is configured with RIPv2 on a network with other RIPv2 routers, it does not receive routing table updates.
Workaround:
In addition to RIPv2 configuration, you must enable multicast forwarding on the CPE device. The CPE device cannot recognize multicast addresses if multicast forwarding is not enabled.
CSCds87618
Symptom:
When using multiple VCCs and VIP interfaces with PPP and NAT enabled, the VIP interfaces default to NAT outside interfaces.
Condition:
To use NAT across the VIP interfaces you have to change them to NAT inside interfaces.
Workaround:
Enter the following command:
set interface vip0 inside
or
Do not use NAT when using the VIP interfaces. If you must use NAT, direct all traffic to the wan0-0 interface. The wan0-0 interface remains as a NAT outside interface.
CSCds49083
Symptom:
The mask for ethernet 0 (eth0) can be set to all 255s.
Condition:
When the mask of eth0 is set to 255.255.255.255, the interface will not appear in the routing table and is unusable.
Workaround:
Manually set the mask of eth0 to a number other than all 255s.
CSCds86083
Symptom:
When stats web command is entered on a CPE, the value of the field # of current connections may be artificially high, up to a value of over 4 billion.
Condition:
This problem can occur when a web connection is established to the CPE and left up for a prolonged period of time, such as overnight.
Workaround:
There is no workaround.
CSCds87384
Symptom:
When using multiple PVCs, for example, wan0-1 through wan0-7, and using the stats ip wan0-x command, only wan0-0 will display anything other than 0s for the statistics
Condition:
This occurs when using multiple PVCs and the stats ip command.
Workaround:
Obtain statistics on the amount of traffic by using other commands such as show ppp, show rfc1483, or show int wan0-x.
CSCds87418
Symptom:
When NAT is enabled on a CPE and a global outside IP address has been assigned via the command line interface (CLI) or auto-provisioning, but an IP address is also being received via IPCP, the global outside IP address will be that received via IPCP.
Condition:
This occurs under the following circumstances:
PPP routing is used on the CPE
NAT is enabled on the CPE
A global outside IP address is configured on the CPE from either the CLI or via auto-provisioning for the wan0-0 interface; the wan0-1 through wan0-7 interfaces do not have this issue
The terminating route (6400 NRP or 7200) has been configured to pass an IP address via IPCP to the CPE
Workaround:
There are two possible workarounds:
Configure the global outside IP address on the CPE or have the terminating router pass an IP address via IPCP. This avoids any potential conflicts between the global outside IP address on the wan0-0 interface and the IP address to be received via IPCP.
Use the command line interface to set the following parameter:
set ppp wan0-x ipcpIP address
where x is the applicable interface and IP address is the desired global outside IP address.
CSCds89064
Symptom:
When you try to set a password, any uppercase characters are converted to lowercase. Additionally, note that passwords set in a previous version of CBOS do retain their case after the CPE software is upgraded to Release 2.3.9.
Condition:
This occurs when using uppercase characters for both the exec or enable passwords.
Workaround:
The workaround is to use only lowercase characters.
The show NVRAM command sporadically produces unintelligible results.
Condition:
This occurs occasionally when the command is abbreviated to sh nv.
Workaround:
Issue the complete command show nvram.
CSCdt39336
Symptom:
The minimum number of unique characters is not accepted when setting the precedence value for a default route.
Condition:
When setting up a default route for IP packets having a precedence of 5, it should be possible to specify the route as:
set rou def wan0-0 p 5
The precedence argument requires the first two letters of the word precedence.
Workaround:
Specify IP precedence as:
set route default wan0-0 pr 5
CSCdt30943
Symptom:
When running RIP Version 1 with multiple PVCs which terminate on physically different routers (Cisco 6400 NRPs), the CPE (c675, c678, or c677) toggles all the routes in its routing table from one interface to another as the CPE receives updates from its WAN interfaces.
Condition:
The CPE takes any advertised RIP Routing updates and add them to its routing table without regard to the metric for the advertised route. This can be observed by issuing the show route command in CBOS repeatedly until a new routing update is received by the CPE. The routing table will then point all routes out the interface from which the last routing updates was received.
Workaround:
The workaround is to enable ip split-horizon on each interface that is connected to the CPE. This includes all wan0-x interfaces and any devices attached to the CPE Ethernet interface. The other devices will no longer advertise any routes back to the CPE that it originally learned from.
CSCdt48089
Symptom:
The set web command produces an invalid error message.
Condition:
Typing set web ? produces the following error message along with the help output. Error: Possible parameters
The correct help message is still shown.
Workaround:
There is no workaround.
CSCdt50680
Symptom:
Setting the CPE to RFC1483 routing mode does not initialize the process until the CPE is rebooted.
Condition:
After the user enters the set rfc1483 enable command, the RFC1483 routing process does not initialize.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Attn Document Resource Connection Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-9883
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.
P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Discover All That's Possible, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, PIX, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Voice LAN, Wavelength Router, WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries.
All other brands, names, or trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0101R)
