Table Of Contents
CSG2 Features Supported for Cisco IOS Release 12.4(22)MD1
CSG2 Features Supported for Cisco IOS Release 12.4(22)MD
Determining the Software Version
Prerequisites and Restrictions
Caveats for Cisco IOS Release 12.4(22)MD1
CSG2 Software for Cisco IOS Release 12.4(22)MD1 - Open Caveats
CSG2 Software for Cisco IOS Release 12.4(22)MD1 - Closed Caveats
SAMI Software for Cisco IOS Release 12.4(22)MD1 - Open Caveats
SAMI Software for Cisco IOS Release 12.4(22)MD1 - Closed Caveats
Caveats for Cisco IOS Release 12.4(22)MD
CSG2 Software for Cisco IOS Release 12.4(22)MD - Open Caveats
CSG2 Software for Cisco IOS Release 12.4(22)MD - Closed Caveats
SAMI Software for Cisco IOS Release 12.4(22)MD - Open Caveats
SAMI Software for Cisco IOS Release 12.4(22)MD - Closed Caveats
Documentation and Technical Assistance
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco
Content Services Gateway -
2nd Generation Release 3.0
Cisco IOS Release 12.4(22)MD1
Revised: December 20, 2009
Current Release—12.4(22)MD1
This publication describes the requirements, dependencies, and caveats for the Cisco Content Services Gateway - 2nd Generation, more commonly known as the Content Services Gateway 2 or CSG2.
This publication includes the following information:
•
Prerequisites and Restrictions
•
–
–
–
–
•
–
–
–
–
•
Introduction
The CSG2 is an application that runs on the Service and Application Module for IP (SAMI), a high-speed processing module. The CSG2 provides content-aware billing, service control, traffic analysis, and data mining in a highly scalable, fault-tolerant package. The CSG2 provides the software required by mobile wireless operating companies and other billing, applications, and service customers.
The CSG2 runs on the SAMI, a new-generation high performance service module for the Cisco 7600 series router platforms. The CSG2 is typically located at the edge of a network in an Internet service provider (ISP) point of presence (POP), or Regional Data Center.
Features
This section lists the CSG2 features and the CSG2 release in which the feature was introduced. For full descriptions of all of these features, see the Cisco Content Services Gateway - 2nd Generation Release 3.0 Installation and Configuration Guide.
To see the software part numbers associated with each CSG2 release; the Supervisor hardware required by each CSG2 release; the minimum Cisco IOS release required for new features in each CSG2 release; and the minimum IOS level supported by each CSG2 release, see the "Software Requirements" section.
•
•
CSG2 Features Supported for Cisco IOS Release 12.4(22)MD1
The CSG2 software for Cisco IOS Release 12.4(22)MD1 supports the entire feature set listed in the "CSG2 Features Supported for Cisco IOS Release 12.4(22)MD" section.
In addition, the CSG2 software for Cisco IOS Release 12.4(15)MD3 supports the following new features:
•
For more information, see Closed caveat CSCsq12202.
CSG2 Features Supported for Cisco IOS Release 12.4(22)MD
The CSG2 Release 3.0 software for Cisco IOS Release 12.4(22)MD supports the entire feature set for the CSG2 Release 2.0 software for Cisco IOS Release 12.4(15)MD.
In addition, the CSG2 software for Cisco IOS Release 12.4(22)MD supports the following new features:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
–
–
–
–
System Requirements
This section describes the following memory and software requirements for CSG2:
•
For hardware requirements, such as power supply and environmental requirements, as well as hardware installation instructions, see the Service and Application Module for IP User Guide.
Memory Requirements
The CSG2 memory is not configurable.
The SAMI is available with a default 1 GB memory or an optional 2-GB memory.
Hardware Supported
Use of the CSG2 requires one of the following Cisco 7600 Series Routers and Supervisor Engines, and a module with ports to connect server and client networks:
•
•
•
•
•
•
•
Software Requirements
When referring to this section, keep the following considerations in mind:
•
•
The following table lists the CSG2 and SAMI module part numbers and associated information for each CSG2 release:
Determining the Software Version
To determine the version of Cisco IOS software that is currently running on your Cisco network device, log in to the CSG2 or Supervisor Engine and enter the show version EXEC command.
To show CSG2 versions, log in to the Supervisor Engine and enter the show module command in privileged EXEC mode.
To provide meaningful problem determination information, log in to the CSG2 or Supervisor Engine and enter the show tech-support command in privileged EXEC mode.
Prerequisites and Restrictions
For the latest prerequisites and restrictions for the CSG2, see the "Overview" chapter of the Cisco Content Services Gateway - 2nd Generation Release 3.0 Installation and Configuration Guide.
Caveats for Cisco IOS Release 12.4(22)MD1
This section lists and describes all caveats, both Open and Closed, that affect the CSG2 or SAMI software for Cisco IOS Release 12.4(22)MD1.
•
•
•
•
CSG2 Software for Cisco IOS Release 12.4(22)MD1 - Open Caveats
The following list identifies Open caveats in the CSG2 software for Cisco IOS Release 12.4(22)MD1.
•
With the meter exclude mms wap command configured and AoC enabled on a service, when a subscriber tries to browse with WAP 1.x, the CSG2 consults the quota server with a content authorization request and the quota server then responds with a content authorization response with the action of redirect and the URL to be redirected to. the page does not load on the subscriber's cell phone.
Workaround: Disable the exclude mms option redirect command.
CSG2 Software for Cisco IOS Release 12.4(22)MD1 - Closed Caveats
The following list identifies Closed caveats in the CSG2 software for Cisco IOS Release 12.4(22)MD1:
•
The CSG2 might generate a CDR with a Connection timestamp that is one second earlier than the Service-Start timestamp.
•
When the CSG2 detects an HTTP protocol error, such as non-HTTP traffic hitting content that is configured with parse protocol http, it downgrades to Layer 4 inspection. The CSG2 allows all remaining traffic to pass through, and reports the traffic in the Unassigned Bytes TLV.
To be consistent with the CSG1, after downgrading to Layer 4 inspection the CSG2 should match the current transaction to the catchall policy in the content, if there is one configured. If no catchall policy is configured, then the CSG2 should use the block configuration in the content to determine whether to forward or block the traffic.
•
Configuration rollback does not work for CSG2 maps, policies, and contents.
•
The show interface command returns output from all of the TPs and the CP. When The CSG2 is under stress, the command might take up to 2 minutes to display output.
•
The CSG2 might experience a memory allocation failure on the I/O memory pool of one of its processors with a %SYS-2-MALLOCFAIL error message.
For this problem to occur, all of the following conditions must be met:
–
–
–
•
If a spanning tree loop occurs in an HA network, a standby CSG2 might become stuck in COLD-BULK state for several hours.
•
A session might reset if the CSG2 is unable to count retransmitted or out-of-order packets. This problem can occur if the CSG2 does not have enough resource to count retransmitted or out-of-order packets, or if malformed packets caused packet counting errors.
•
If you use more than one virtual teletype terminal (VTY console) when interacting with the CSG2 (for example, using one VTY to enter show commands and another to enter configuration commands), one of the VTYs might hang and the CSG2 will not allow further configuration commands. The CSG2 issues the following message:
Config failed, CSG being configured by line
You must reboot the CSG2 before continuing.
•
Quota which could not be returned to the quota server is not credited back to the user.
For this problem to occur, all of the following conditions must be met:
–
–
–
•
The following commands specific to the CSG2 appear in the command line interface (CLI), but they are not supported and should not be used:
clear ip csg event-trace packet
debug ip csg event-trace packet
ip csg event-trace packet
show ip csg event-trace packet•
If NTP is not configured or synced with the configured NTP server, the CSG2 consumes all received packets, and even ping commands to local interfaces fail. Debugs show that the CEF receives the packet, but it is consumed by the CSG2.
•
If a user configures a 32-character VRF name, and the VRF is used in a user database, BMA, or quota server definition, the CSG2 might experience buffer overflow problems, due to SNMP queries on the CISCO-CONTENT-SERVICES-MIB.
•
The CSG2 might crash when the debug ip csg qs detail command is configured and a nonstandard Quota Push Request message is received.
•
If the ip csg quota-server retransmit command is set to 5 or lower, and a quota server fails over, the CSG2 might send a Service Reauthorization Request (SRAR) before sending a Service Authorization Request.
•
When the number of users exceeds the licensed value, configured with the ip csg license warning-enable command in global configuration mode, the first syslog message is generated after five minutes:
SAMI 8/3: *Feb 5 09:17:11.555: %CSG-4-CSG_LICENSE_LIMIT_REMINDER_SYSLOG: KUT limit exceeded the license limit: Number of users accessing network concurrently has exceeded the license limit
•
Packet of Disconnect (PoD) can be configured at either the global level or at the billing plan level. Each level should work independently of the other. However, PoD is not working unless the ip csg entries user idle duration pod command is configured in global configuration mode.
•
The CSG2 might experience a slow memory leak when adding attribute map matches.
•
If the CSG2 depleted the RADIUS attribute pool while processing a large number of RADIUS requests at a very high rate, it might fail to proxy RADIUS requests to the RADIUS server, while the "radius attribute" and "radius deny" counters continue to increase.
•
A per-user QoS signaled from the quota server might not be replicated from the active CSG2 to the standby CSG2. If a failover occurs, traffic for that subscriber is either not subject to any QoS or is subject to the configured QoS, if any.
For this problem to occur, all of the following conditions must be met:
–
–
–
•
If the CSG2 is configured for RADIUS endpoint or RADIUS proxy, and the debug ip csg radius command is entered, the CSG2 might reload.
•
The CSG2 might crash with the following messages in the crash information file:
SAMI 4/3: Mar 25 13:58:30.665 ISR: %SYS-6-STACKLOW: Stack for process CSG BGCFG running low, 0/24000
%Software-forced reload
13:58:30 ISR Wed Mar 25 2009: Unexpected exception to CPU: vector 1500, PC = 0x4504A33C, LR = 0x4504A298
-Traceback= 0x4504A33C 0x4504A298 0x4504F6B4 0x4504F844 0x44E40654 0x450A0FCC 0x4504C384 0x4504FA64
For this problem to occur, all of the following conditions must be met:
–
–
–
•
The CSG2 might reload under certain conditions.
For this problem to occur, all of the following conditions must be met:
–
–
–
–
–
•
Under certain RTSP load and stress conditions, some entries remain in the CSG2 User Table. Trying to clear this state results in a traceback.
•
Entering distributed show commands, such as show proc cpu, from a Telnet or Supervisor Engine session into the SAMI module, while the CSG2 is under heavy stress, might cause the CSG2 to hang and fail at CPU 4.
Attempts to change the configuration results in the following message after exiting configuration mode:
%PARSER-6-EXPOSEDLOCKRELEASED: Exclusive configuration lock released from terminal '0' -Process= "CSG config rollback", ipl= 0, pid= 122
•
For a prepaid subscriber with zero quota using a service with zero weight, the CSG2 might generate multiple reauthorization requests within a few seconds.
•
The CSG2 NBAR CDRs might not report the QoS rate-limit TLV or QoS drop TLV.
For this problem to occur, all of the following conditions must be met:
–
–
•
In a stateful redundant CSG2 configuration, the standby CSG2 User Table might not contain all of the subscribers that are present in the active CSG2 User Table.
This problem can occur if the standby CSG2 receives a RADIUS Accounting On or Off message from a GGSN, then receives a RADIUS Accounting Start message from the GGSN before completing processing of the RADIUS Accounting On or Off message.
This problem can also occur if the clear ip csg user command is entered.
•
The CSG2 might encounter a memory leakage that results in a malloc failure of RADIUS attributes and prevents the CSG2 from processing incoming RADIUS requests.
•
Doing Layer 7 WAP inspection, a KUT_CLEANUP_ERROR traceback is dumped to the console when the CSG2 attempts to remove a WAP user from the User Table. the user is not removed from the User Table.
•
If an HTTP packet consists of retransmitted bytes of a previous transaction, and new bytes of a new transaction, a service's "reserved", as displayed in the output of the show ip csg user all detail command, might keep incrementing.
•
When a retransmitted packet has multiple transactions, the reported IP bytes for each transaction in that packet are incorrect.
SAMI Software for Cisco IOS Release 12.4(22)MD1 - Open Caveats
The following list identifies Open caveats in the SAMI software that impact the CSG2 software for Cisco IOS Release 12.4(22)MD1.
•
The show cdp entry * command output is empty.
Workaround: None.
•
The remote console and logging (RCaL) feature on the CSG2 image might not work if the Supervisor Engine's logging listen port and the Power PC's (PPC's) logging main-cpu port are both configured as port 10000.
Workaround: Use the default port 4000 for RCAL, or any port other than 10000.
•
A SAMI processor might crash when you are configuring or unconfiguring iSCSI-related commands.
For this problem to occur, all of the following conditions must be met:
–
–
–
–
On the CSG2, control and traffic are on different processors. The iSCSI configuration and processing are only in the control CPU, and this issue is seen only when the CPU is at about 90%. The control CPU is not likely to ever reach 90%. Therefore, this issue is not likely to occur in the CSG2.
Workaround: None.
•
If you use Ctrl-^ to terminate a remote console and logging (RCAL) execute-on from the Supervisor Engine into the SAMI line control processor (LCP) or PowerPC (PPC), the next RCAL execute-on attempt might fail.
Workaround: Disable logging listen on the Supervisor Engine, then re-enable it.
SAMI Software for Cisco IOS Release 12.4(22)MD1 - Closed Caveats
The following list identifies the Closed caveats in the SAMI software that impact the CSG2 software for Cisco IOS Release 12.4(22)MD1:
•
Cisco IOS Software contains a vulnerability that could allow an attacker to cause a Cisco IOS device to reload by remotely sending a crafted encryption packet. Cisco has released free software updates that address this vulnerability. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-tls.shtml.
•
Cisco IOS devices that are configured with Cisco IOS Zone-Based Policy Firewall Session Initiation Protocol (SIP) inspection are vulnerable to denial of service (DoS) attacks when processing a specific SIP transit packet. Exploitation of the vulnerability could result in a reload of the affected device.
Cisco has released free software updates that address this vulnerability.
Workarounds that mitigate this vulnerability are available within the workarounds section of the posted advisory.
This advisory is posted at the following link:
http://www.cisco.com/warp/public/707/cisco-sa-20090923-ios-fw.shtml
•
Cisco IOS Software with support for Network Time Protocol (NTP) version (v4) contains a vulnerability processing specific NTP packets that will result in a reload of the device. This results in a remote denial of service (DoS) condition on the affected device.
Cisco has released free software updates that address this vulnerability.
Workarounds that mitigate this vulnerability are available and are documented in the workarounds section of the posted advisory.
This advisory is posted at the following link:
http://www.cisco.com/warp/public/707/cisco-sa-20090923-ntp.shtml
•
A vulnerability exists in Cisco IOS software where an unauthenticated attacker could bypass access control policies when the Object Groups for Access Control Lists (ACLs) feature is used. Cisco has released free software updates that address this vulnerability. There are no workarounds for this vulnerability other than disabling the Object Groups for ACLs feature. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-acl.shtml.
•
Multiple Cisco products are affected by denial of service (DoS) vulnerabilities that manipulate the state of Transmission Control Protocol (TCP) connections. By manipulating the state of a TCP connection, an attacker could force the TCP connection to remain in a long-lived state, possibly indefinitely. If enough TCP connections are forced into a long-lived or indefinite state, resources on a system under attack may be consumed, preventing new TCP connections from being accepted. In some cases, a system reboot may be necessary to recover normal system operation. To exploit these vulnerabilities, an attacker must be able to complete a TCP three-way handshake with a vulnerable system.
In addition to these vulnerabilities, Cisco Nexus 5000 devices contain a TCP DoS vulnerability that may result in a system crash. This additional vulnerability was found as a result of testing the TCP state manipulation vulnerabilities.
Cisco has released free software updates for download from the Cisco website that address these vulnerabilities. Workarounds that mitigate these vulnerabilities are available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090908-tcp24.shtml.
•
A vulnerability exists in Cisco IOS software where an unauthenticated attacker could bypass access control policies when the Object Groups for Access Control Lists (ACLs) feature is used. Cisco has released free software updates that address this vulnerability. There are no workarounds for this vulnerability other than disabling the Object Groups for ACLs feature. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-acl.shtml.
•
Cisco IOS Software with support for Network Time Protocol (NTP) version (v4) contains a vulnerability processing specific NTP packets that will result in a reload of the device. This results in a remote denial of service (DoS) condition on the affected device.
Cisco has released free software updates that address this vulnerability.
Workarounds that mitigate this vulnerability are available and are documented in the workarounds section of the posted advisory.
This advisory is posted at the following link:
http://www.cisco.com/warp/public/707/cisco-sa-20090923-ntp.shtml
•
A vulnerability exists in Cisco IOS software where an unauthenticated attacker could bypass access control policies when the Object Groups for Access Control Lists (ACLs) feature is used. Cisco has released free software updates that address this vulnerability. There are no workarounds for this vulnerability other than disabling the Object Groups for ACLs feature. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-acl.shtml.
•
If a packet has an ICMP source and destination IP address that is the same as the PPC interface IP address, the SAMI runs out of I/O memory, and the following message appears:
%SYS-2-MALLOCFAIL: Memory allocation of 1708 bytes failed from 0x45407D18, alignment 32
•
A SAMI processor might crash when removing the ISCSI configuration using the no ip iscsi profile command.
•
The SAMI Status LED is remaining green during shutdown. It should change to orange during shutdown.
•
A vulnerability exists in Cisco IOS software where an unauthenticated attacker could bypass access control policies when the Object Groups for Access Control Lists (ACLs) feature is used. Cisco has released free software updates that address this vulnerability. There are no workarounds for this vulnerability other than disabling the Object Groups for ACLs feature. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-acl.shtml.
•
Cisco devices running affected versions of Cisco IOS Software are vulnerable to a denial of service (DoS) attack if configured for IP tunnels and Cisco Express Forwarding.
Cisco has released free software updates that address this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-tunnels.shtml.
•
Cisco IOS Software configured with Authentication Proxy for HTTP(S), Web Authentication or the consent feature, contains a vulnerability that may allow an unauthenticated session to bypass the authentication proxy server or bypass the consent webpage.
There are no workarounds that mitigate this vulnerability.
This advisory is posted at the following link:
http://www.cisco.com/warp/public/707/cisco-sa-20090923-auth-proxy.shtml
•
A vulnerability exists in Cisco IOS software where an unauthenticated attacker could bypass access control policies when the Object Groups for Access Control Lists (ACLs) feature is used. Cisco has released free software updates that address this vulnerability. There are no workarounds for this vulnerability other than disabling the Object Groups for ACLs feature. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-acl.shtml.
•
The SAMI is not setting the DBUS trust bit to 1, which in turn causes the Cisco 7600 Series Router to remark the DSCP of the packets.
Caveats for Cisco IOS Release 12.4(22)MD
This section lists and describes all caveats, both Open and Closed, that affect the CSG2 or SAMI software for Cisco IOS Release 12.4(22)MD.
•
•
•
•
CSG2 Software for Cisco IOS Release 12.4(22)MD - Open Caveats
The following list identifies Open caveats in the CSG2 software for Cisco IOS Release 12.4(22)MD.
•
Configuration rollback does not work for CSG2 maps, policies, and contents.
Workaround: Instead of rollback, use regular configuration commands to undo previous configuration changes.
•
The show interface command returns output from all of the TPs and the CP. When The CSG2 is under stress, the command might take up to 2 minutes to display output.
Workaround: Reduce the stress to the CSG2 or use the execute all show interface command.
•
The CSG2 might experience a memory allocation failure on the I/O memory pool of one of its processors with a %SYS-2-MALLOCFAIL error message.
For this problem to occur, all of the following conditions must be met:
–
–
–
Workaround: Configure the route, the default route, or the next-hop IP address.
•
If you use more than one virtual teletype terminal (VTY console) when interacting with the CSG2 (for example, using one VTY to enter show commands and another to enter configuration commands), one of the VTYs might hang and the CSG2 will not allow further configuration commands. The CSG2 issues the following message:
Config failed, CSG being configured by line
You must reboot the CSG2 before continuing.
Workaround: Use only one VTY at a time when interacting with the CSG2.
•
Quota which could not be returned to the quota server is not credited back to the user.
For this problem to occur, all of the following conditions must be met:
–
–
–
Workaround: None.
•
With the meter exclude mms wap command configured and AoC enabled on a service, when a subscriber tries to browse with WAP 1.x, the CSG2 consults the quota server with a content authorization request and the quota server then responds with a content authorization response with the action of redirect and the URL to be redirected to. the page does not load on the subscriber's cell phone.
Workaround: Disable the exclude mms option redirect command.
CSG2 Software for Cisco IOS Release 12.4(22)MD - Closed Caveats
The following list identifies Closed caveats in the CSG2 software for Cisco IOS Release 12.4(22)MD:
•
If an idle timer is configured for the User Table, and if thousands of users idle out at the same time, the rate at which the CSG2 can handle incoming RADIUS messages is reduced.
•
When entering CSG2 show commands that collect and display information from all of the CPUs in the CSG2, the output might not break or pause as expected based on the term length configuration. If that happens, long output can scroll off-screen unexpectedly.
This problem does not occur for information gathered from the CP, whether in a distributed command or otherwise.
•
In a prepaid configuration that requires a billing plan from the quota server, if RADIUS Accounting Starts begin arriving at a rate that exceeds the capacity of the CSG2, the CSG2 might drop some of the responses from the quota server.
•
When the CSG2 receives a higher-than-expected rate of RADIUS Accounting Starts with a large number of RADIUS attributes from the Network Access Server (NAS), it might deny the RADIUS requests because it cannot grow the buffer pool fast enough.
•
During Layer 7 inspection for RTSP, the quota server receives an incorrect content authorization request of type 0x08 (RTSP TCP). The request should be of type 0x09. The problem occurs when the RTSP session is transporting data over the control session (interleaved).
•
If you remove a configured billing plan or service using the no option (for example, no ip csg billing), and you then configure a new billing plan or service and assign it to a new transaction, the CSG2 might assign the wrong services to the transaction.
•
If the standby ip command is removed from a protected interface on the standby router, then reapplied, the reapplication fails, and output from the show standby command is empty.
For this problem to occur, one or more of the following conditions must be met:
–
interface gigabitEthernet 0/0.10
no standby 1 ip
standby 5 ip 10.10.30.105
no standby 5 ip
standby 1 ip–
•
If both HTTP and SIP are configured on the same 1 GB SAMI, the CSG2's memory might be depleted. If this occurs, the CSG2 might deny incoming RADIUS requests.
•
TLVs that report units, such as the Qualified Usage TLV, might report a value of 1 (second) when basis second transaction is configured.
•
The output from the show ip csg users all command might include some but not all of the sticky user entries.
•
With a Cisco VPN client and a Cisco VPN concentrator, in a VPN session in IPSec transparent mode, no user traffic flows. The VPN connection is established, but traffic does not flow.
•
While performing Layer 7 parsing of RTSP traffic, the CSG2 might crash if it receives a DESCRIBE message containing a URL that exceeds 512 bytes.
•
The CSG2 reloads with a crash indication.
The CSG2 might reload while performing L7 inspection of IMAP traffic if certain fields within the flow are >256 bytes.
•
If any combination of the following situations occurs:
–
–
–
•
%PLATFORM-1-DP_HM_FAIL: Failed to receive response from Fail to send message to IXP: Msgcode : %d
. Check `sami health-monitoring' configuration and see `show sami health-monitoring' for more infoThereafter, although the interface might be UP on the CP, pings to the interface fail. Packets can be seen leaving the CSG2 from the interface, but data to the interface is not seen by the CP.
•
If multiple quota servers are active, and the user logs off during a quota server failover, the CSG2 might fail to generate a ServiceStop message. This might result in the user session not being billed correctly.
•
The CSG2 allows the configuration of priority values up to 65535 for policies within content rules. However, the underlying code only allows values up to 511. Configuring a priority higher than 511 results in the content rule matching only the default policy.
•
If you configure the following commands:
records granularity service bytes 10240000 seconds 3600ip csg records format fixedThen CDRs for the service might report start and stop dates with years and months in the wrong format.
•
If a service is configured for Advice of Charge, the CSG2 might fail to redirect a user when zero quota is received from the quota server in a Service Authorization Response.
•
CSG might crash when performing Layer 7 SIP inspection. The crash can occur while the CSG2 is parsing an incorrectly formed SIP INVITE request (that is, a SIP INVITE request in which the SDP portion of the message contains extra carriage return and line feed characters).
•
In Cisco CSG2 running R2 image, service reauthorization might not be sent to the quota server during roaming.
For this problem to occur, all of the following conditions must be met:
–
–
–
–
•
When the CSG2 performs Layer 7 SIP parsing on a packet that contains a SIP or SDP header token that exceeds 256 bytes, a DATA CORRUPTION traceback might be displayed on the console.
•
If duration-based billing is configured, and the remaining quota is very large (greater than 2147483647), the CSG2 might not use the upper 4 bytes of the Qualified Remaining Quota TLV.
•
If duration-based billing is configured, and there is a difference between the remaining quota and the quota required for the current transaction, and the last billable timestamp is very large (greater than 2147483647), the CSG might show an incorrect usage value in the SvcReAuthReq message.
•
If a service contains at least one rule (content/policy), the CSG2 does not allow the idle to be reset by entering the idle (CSG2 service) command.
•
A WS-SVC-SAMI-BB-K9 service blade running an c7svcsami-csg-mz or c7svcsami-csgk9-mz image might reload.
For this problem to occur, all of the following conditions must be met:
–
–
–
•
If you have already configured a RADIUS monitor for a RADIUS server address, and you try to configure another RADIUS monitor for that address but for a different port, the CSG2 might not allow you to do so.
SAMI Software for Cisco IOS Release 12.4(22)MD - Open Caveats
The following list identifies Open caveats in the SAMI software that impact the CSG2 software for Cisco IOS Release 12.4(22)MD.
•
The show cdp entry * command output is empty.
Workaround: None.
•
The remote console and logging (RCaL) feature on the CSG2 image might not work if the Supervisor Engine's logging listen port and the Power PC's (PPC's) logging main-cpu port are both configured as port 10000.
Workaround: Use the default port 4000 for RCAL, or any port other than 10000.
•
A SAMI processor might crash when you are configuring or unconfiguring iSCSI-related commands.
For this problem to occur, all of the following conditions must be met:
–
–
–
–
On the CSG2, control and traffic are on different processors. The iSCSI configuration and processing are only in the control CPU, and this issue is seen only when the CPU is at about 90%. The control CPU is not likely to ever reach 90%. Therefore, this issue is not likely to occur in the CSG2.
Workaround: None.
•
If you use Ctrl-^ to terminate a remote console and logging (RCAL) execute-on from the Supervisor Engine into the SAMI line control processor (LCP) or PowerPC (PPC), the next RCAL execute-on attempt might fail.
Workaround: Disable logging listen on the Supervisor Engine, then re-enable it.
SAMI Software for Cisco IOS Release 12.4(22)MD - Closed Caveats
The following list identifies the Closed caveats in the SAMI software that impact the CSG2 software for Cisco IOS Release 12.4(22)MD:
•
When the GGSN is under stress, such as CPU utilization more than 96%, the output of the show process cpu command might be incorrect.
•
When the SAMI image is upgraded from the Supervisor Engine using the upgrade command, it executes correctly, but the output of the show module command displays a module status of Shutdown when it should be Other. When the SAMI comes online, the status is shown correctly as OK.
•
Packet fragments larger than 3,000 bytes are dropped by the SAMI,.
For this problem to occur, all of the following conditions must be met:
–
–
•
The SAMI processors fail to download the configuration from the Supervisor Engine. EOBC traffic does not work. The session from the Supervisor Engine to processors 1-8 does not work.
For this problem to occur, one or more of the following conditions must be true:
–
–
–
–
•
A router functioning as the standby for a Hot Standby Routing Protocol (HSRP) group might reload when it is dissociated from that group and then re-associated with it.
•
If the SAMI bundle is present in the bootflash or sup-bootflash of the Supervisor Engine 32, an EOBC boot of the SAMI might fail and the SAMI might enter power-down state.
•
A vulnerability exists in the Session Initiation Protocol (SIP) implementation in Cisco IOS software that can be exploited remotely to cause a reload of the Cisco IOS device.
Cisco has released free software updates that address this vulnerability. There are no workarounds available to mitigate the vulnerability apart from disabling SIP, if the Cisco IOS device does not need to run SIP for VoIP services. However, mitigation techniques are available to help limit exposure to the vulnerability.
This advisory is posted at the following link:
http://www.cisco.com/warp/public/707/cisco-sa-20090325-sip.shtml.
•
The SAMI processor might hang if it encounters a very rare software error.
•
A vulnerability exists in Cisco IOS software where an unauthenticated attacker could bypass access control policies when the Object Groups for Access Control Lists (ACLs) feature is used. Cisco has released free software updates that address this vulnerability. There are no workarounds for this vulnerability other than disabling the Object Groups for ACLs feature. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-acl.shtml.
•
If there is a hardware failure in the Nitrox module of the card, the PPC Processors boot up fine, but the Boot Log of Processor 0 shows a Loading Nitrox driver failure.
Documentation and Technical Assistance
This section contains the following information:
•
Related Documentation
For more detailed installation and configuration information, see the following publications:
•
•
•
•
•
•
•
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
•
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (0910R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Copyright © 2009 Cisco Systems, Inc. All rights reserved.
Guest