Release Notes for Cisco Service Control Operating System (SCOS) Release 3.1.5 LA
Available Languages
Table Of Contents
Release Notes for Cisco Service Control Operating System (SCOS) 3.1.5 LA
Support for VPN subscribers in MPLS L3-VPN and VLAN domains
DSCP (ToS) Marking - Enhanced Model
Classification in VLAN-based environment
SCE reloads when overutilized with massive error dumps to log
RADIUS/DHCP sniffer in SCE might stop functioning for certain flows
SCE might reload in rare cases due to an infinite loop in its scheduler
Problem with fragments classification consumes log assets
Global-Controllers triggers warnings to the log when querying the MIB Group
Bad response to a SNMP query and a Warning in DBG log
TCP Learning did not close flows that started with SYN-ACK
Uni-directional classification for support of asymmetric routing
Subscriber synchronization in cascade setups
SSH activity sometimes ended in an unstable state
Redirect packet was sometimes transmitted on wrong link
Dynamic Signature (DSS) caused a reboot after dozens of consecutive Apply operations
Reload of the SCE due to an expiry of an internal watchdog mechanism
The saving process of application configuration was not resilient to reload
Failure to retrieve support file using FTP
PRPC authentication security level was set to default after RPC adapter restart
Part of the quota information was not exchanged between two cascaded SCE platforms
Subscriber with many mappings did not send all lease time expiration notifications
Link reflection failed to operate after long uptime
Attack-detector port-list showed random numbers in running-config
Potential discard of packet under extreme network conditions
Access violation when configuring anonymous groups
rdrActiveConnectionTrap was not sent after reload of the SCE platform
Link up/down traps were not sent on all ports
MIB object 'pmoduleType' returned wrong value in cascade setups
MIB variable ifMtu returned wrong value for traffic ports
Some rdr-formatter MIB objects returned information only for category 1
SCE reboot during PQI installation
Cannot add VLAN mapping to VPN after removing mapping when subscriber mappings are logged in
While removing all VPNs management operations cannot be performed
SCE-Sniffer RADIUS LEG might not work after PQI installation
Long SSH session cleanup time may result in temporary unavailability
Upgrading the SM causes SCE failover in cascade topology
Problems may be encountered in downgrading from Release 3.1.0 (or higher) to a previous release
Problems may be encountered in downgrading from Release 3.0.5 (or higher) to a previous release
Link failure may be reflected to all ports if a port is flickering due to a HW problem
Subscribers data synchronization is slower when static subscribers are configured
CLI command `IP address' should indicate to the user that a reload of the SCE is required
'no service telnetd' command does not block the Telnet port
Errors on invalid management agent notification during SCE reload
BWC controller gives less bandwidth than configured
Potential memory overrun in cascaded environment with a high number of subscribers
The configured attack threshold is set for each PPC separately
Flow `opened from VAS' is misrouted if there is a FF rule to bypass
Packet Loss during Application Installation or Upgrade
`show snmp MIB pcube-SE-MIB port' returns wrong number of ports
Obtaining Technical Assistance
Contacting TAC by Using the Cisco TAC Website
Release Notes for Cisco Service Control Operating System (SCOS) 3.1.5 LA
Revised: October 8, 2007, OL-14438-04Supports: SCOS 3.1.1
These release notes for the Cisco Service Control Operating System describe the new features and fixes provided in Cisco Release SCOS 3.1.5 LA. These release notes are updated as needed.
For information regarding features added and issues resolved in the 3.0.x train, please refer to Release Notes for Cisco Service Control Operation System (SCOS) 3.0.6.
For a list of the caveats that apply to Cisco Release SCOS 3.1.5 LA, see Open Caveats.
•
Obtaining Technical Assistance
Introduction
SCOS 3.1.5 LA is a maintenance release with features . It includes functional enhancements, as well as fixes of issues that were identified as part of Cisco's on going internal testing and during our interaction with our customers.
This document outlines the functional enhancements and fixes delivered in the SCOS 3.1.5 LA release. It assumes the reader already has a good working knowledge of the Cisco Service Control solution. For additional information, please refer to the online Cisco Service Control Engine documentation .
RELEASE SCOS 3.1.5 LA
Compatibility Information
SCOS 3.1.5 LA may be installed on the following Service Control Engine platforms:
•
•
SCOS 3.1.5 LA is not compatible with the following Service Control Engine platforms:
•
•
Functional Enhancements
•
•
Support for VPN subscribers in MPLS L3-VPN and VLAN domains
Release 3.1.5 LA enhances the capability of SCA BB to allow defining service in an environment where IPv4 addresses overlap.
In releases prior to 3.1.5 LA, the operator could only assign service to the entire VPN or entire VLAN. In 3.1.5 LA, service can be assigned to individual and overlapping IPv4 addresses within the VPN (VLAN or MPLS L3-VPN). The VPN/VLAN represents the way an entire enterprise is managed, while the enhancements in 3.1.5 LA allow specific service to be assigned to an individual within the enterprise, or to a branch office.
As technology varies between VLAN and MPLS-VPN, so the offering and integration models are different for the two. However, for the sake of a unified interface, whenever possible the term VPN will represent either MPLS L3-VPN or VLAN.
A VPN is a named entity, introduced in the same way that a subscriber is introduced, and containing VPN mappings. A VPN may contain several MPLS mappings or a single VLAN mapping.
A VPN-based subscriber contains a set of mappings of the form: IP@VpnName, where IP can be either a single IP address or a range of addresses.
VPN entities can be configured only via the SM. The SCE platform CLI can be used to view VPN-related information, but not to configure the VPNs.
For information on the configuration and management of VPN entities, please refer to the Cisco Service Control Management Suite Subscriber Manager User Guide, Rel 3.1.5 .
For information on the configuration and management of MPLS/VPN-based subscribers, please refer to the Cisco Service Control MPLS/VPN Solution Guide, Rel 3.1.5 .
MPLS L3-VPN
MPLS L3-VPN has gained popularity with ISPs for use in supporting business intranet services.
The SCE platform can be used within an MPLS cloud to address a range of use cases such as monitoring, reporting, and control of different network entities.
The following examples illustrate the supported topologies and integrations, and clarify what can be gained through the MPLS L3-VPN integration.
Examples of MPLS L3-VPN integration
The following examples demonstrate different integration models.
•
•
•
VPN AS A SUBSCRIBER
When an entire VPN represents one enterprise and is to be managed as a single unit, the whole VPN is defined as one subscriber. In this mode, SCA BB can enforce different service rules for different organizations. SCA BB identifies all CPEs (desktops, laptops, cable modems, or any other equipment that can be identified by an IP address) that are tunneled by the same MPLS/VPN as belonging to a specific organization and therefore subject to the same rule.
For example, browsing may be blocked in the extranet for one organization (VPN) and permitted for a different organization (VPN).
BRANCH OFFICE AS A SUBSCRIBER - NEW IN 3.1.5
This capability allows the ISP to set specific services for a branch office that is a part of an organization (part of the VPN). Each branch office is identified and assigned a policy, such as setting bandwidth limitation for browsing as a percentage of the available trunk. SCA BB identifies a group of CPEs (desktops, laptops, cable modems, or any other equipment that can be identified by an IP address) that are part of a VPN as belonging to a specific branch of an organization and being subject to the same rule. In this way, each branch can be assigned a specific rule to accommodate its needs.
MPLS SKIP
The MPLS skip mode must be used to define service for individual CPEs (such as laptops, cable modems, or any other equipment that can be identified by an individual IP address).
Subscriber as CPE using MPLS skip mode is supported as long as IPv4 addresses do not overlap. In cases where the CPE needs to be individually managed, but IPv4 addresses overlap, please consult the BU roadmap for availability of this capability.
Subscriber integration
To enable MPLS L3-VPN awareness, SCA BB integrates with MPLS-L3VPN routing scheme by using the Subscriber Manager (SM). This allows SCA BB to dynamically identify IPv4 subnets being introduced into the VPN and immediately track all traffic to or from those subnets for reporting and control.
VLAN Awareness
Support for IP-VLAN aware provides customers with an additional level of subscriber introduction, coupling between the subscriber network ID and its associated VLAN.
In the three different integration levels, the managed entity (subscriber) varies. The network architect needs to select between the three based on the use case that is required from the SCA BB.
•
•
•
VPN AS A SUBSCRIBER
This capability allows the ISP to globally manage a network entity, such as an enterprise in a VLAN environment. SCA BB can enforce different service rules as required by the different enterprises, such as blocking browsing in the extranet for one organization (VPN) while permitting browsing for a different organization (VPN).
CPE AS A SUBSCRIBER - NEW IN 3.1.5
This capability allows the ISP to set specific services for an individual who is a part of an organization (part of the VPN). Each individual is identified and assigned a policy, such as setting bandwidth limitation for browsing, reflecting their personalized service requirement.
VPN (VLAN) SKIP
This mode is a simple solution where the managed entity (subscriber) is an individual CPE in a VLAN environment. However, since this mode does not differentiate between overlapping IPs, it can be used only when there are no overlapping IPs within the network.
Subscriber integration
The information required to identify a subscriber within a specific VLAN and assign an individual policy must be provided by the Subscriber Manager (SM). Cisco enhanced the capabilities of the SM Radius listener to allow it to extract the subscriber network ID and VLAN. This information is pushed to the SCE for creating the IP-VLAN subscriber instance.
VLAN awareness constraints
•
•
DSCP (ToS) Marking - Enhanced Model
ToS marking is used in IP networks as a means of signaling the type and priority of a flow between network elements. ToS marking is typically done by elements which have an insight into how traffic should be treated throughout the network. Such an element can be the element generating traffic, such as a voice gateway.
SCA BB, being application aware, can allocate bandwidth resources based on the business model and the specific needs of latency sensitive applications.
Releases prior to 3.1.5 support the ability to mark ToS for traffic flowing through the SCE; however prior to 3.1.5, marking couples the ToS that is marked on the traffic with the egress queuing mechanism used by the SCE.
Release 3.1.5 breaks this coupling and allows the operator to define ToS marking as a result of classification per direction and per service.
The SCE platform TOS marking feature enables marking the TOS field in the IP header of each packet according to the policy configured via the SCA BB console.
TOS marking configuration is performed via the SCA BB console. Marking preferences may be defined per service and direction. There are seven different marking options, or the marking of the packet may be preserved unchanged.
ToS marking marks only the six bits of the DSCP annotation, preserving the two lsb (ECN).
The default marking option is not to mark the packet. Since classification may take a few packets to finalize, it is important to note that the first few packets may still be processed under the default option and therefore may not be marked. For information on configuring TOS marking, please refer to the Cisco Service Control Application for Broadband User Guide, Rel 3.1.5 .
DSCP (ToS) Classification
In release 3.1.5, DSCP can be used as one of the classification criteria. That is, a packet carrying a specific marking can be classified to predefined service, such as unlimited bandwidth, or reported. The DSCP classification process takes precedence over other classification mechanisms to allow external devices, such as a voice gateway, to dictate how the flow is treated. DSCP-based classification is an excellent means of marking proprietary managed services that SCA BB would not otherwise be able to recognize.
DSCP classification constraints
Classification decision is based on the beginning of the flow and stays the same for the duration of the flow.
Backward Compatibility
•
MPLS L3-VPN
Note that 3.1.5 LA configuration supports all the use cases described above. For more information, please consult the Cisco Service Control Engine (SCE) Software Configuration Guide and the Cisco Service Control MPLS/VPN Solution Guide .
Classification in VLAN-based environment
The ability of the SCE platform to import subscriber information from or export it to a CSV file is not supported in VLAN classify mode in release 3.1.5LA.
ToS Marking
The concept of mapping traffic portions to a specific ToS value has changed in release 3.1.5LA.
In previous versions of the SCA-BB solution, the mapping was only possible based on the CoS (Diffserv Class of Service) to which the Service was mapped. Starting with 3.1.5LA, it is possible to map each service to one of seven configurable ToS values independently.
The old ToS marking mode is no longer supported.
Resolved Issues
The following issues were resolved in this release.
•
•
•
•
•
•
•
SCE reloads when overutilized with massive error dumps to log
•
The SCE can sometimes be forced to reload due to a watchdog expiry. This can occur under the following conditions:
–
–
•
This issue is fixed in SCOS 3.1.5 LA.
RADIUS/DHCP sniffer in SCE might stop functioning for certain flows
•
The SCE stops provisioning RADIUS transactions on certain flows. This can occur in the following situations:
–
–
This issue is fixed in SCOS 3.1.5 LA.
SCE might reload in rare cases due to an infinite loop in its scheduler
•
A bug in the quota export function may cause a subtask to run forever, which may cause the SCE platform to reload.
This issue is fixed in SCOS 3.1.5 LA.
Problem with fragments classification consumes log assets
•
In rare cases a log message of the following type may appear in the log:
[0x0807:0x006c] FC: Total number of packets equals total number of non first fragments in flow countersThis can cause the following issues:
–
–
This issue is fixed in SCOS 3.1.5 LA.
Global-Controllers triggers warnings to the log when querying the MIB Group
•
When querying the global-controllers MIB group counters, the following warning is printed to the log for any global-controller index above 64 and for every port:
<WARNING>[0x0b80:0x000e] SeMib: globalControllersEntry_lookup droppedCounters.actualNumberOfCounters=64 <= gcIndex=64 (port=1)!. <WARNING>[0x0b80:0x000e] SeMib: globalControllersEntry_lookup droppedCounters.actualNumberOfCounters=64 <= gcIndex=65 (port=1)!. ..... <WARNING>[0x0b80:0x000e] SeMib: globalControllersEntry_lookup droppedCounters.actualNumberOfCounters=64 <= gcIndex=1023 (port=1)!.This issue is fixed in SCOS 3.1.5 LA.
Bad response to a SNMP query and a Warning in DBG log
•
When performing a get operation on port number 2 (a management port in rev G), the following message is added to the debug log:
05/04/07 22:55:47 [000000125119:265:475] | 000 | 0000014556 | 0000000 | <WARNING>[0x0b80:0x0011] SeMib: globalControllersEntry_lookup CARDS_GetLimiterBandwidthCfg failed. Error is: interface number must be between 1 and 4.This warning is generated each time the SNMP query is accepted and it means that the SCE responds to the SNMP query with a gen_error code, instead of either responding with a proper value, or responding with a no_such_instance error.
This issue is fixed in SCOS 3.1.5 LA.
TCP Learning did not close flows that started with SYN-ACK
•
In MPLS/VPN auto-learn mode, upstream SYN-ACK packets of unlearned labels reached the software even though they should not have.
This was relevant mainly when using anonymous subscribers with a range that contained addresses that appeared in one of the VPNs. In this case, anonymous subscribers may have been incorrectly spawned for addresses inside VPNs. Such subscribers saw very little, if any traffic
This issue is fixed in SCOS 3.1.5 LA.
RELEASE SCOS 3.1.0
New Features
•
•
Uni-directional classification for support of asymmetric routing
In a situation in which the routing scheme directs the two directions of a flow to follow different routes, each direction flows through a different SCE platform. The effect of different routing is that each SCE platform can classify only one direction of the flow. The `asymmetric routing' mode enables the SCE platform to handle such traffic, allowing SCA BB to classify traffic based on a single direction and to apply basic reporting and global control features to uni-directional traffic.
See "Asymmetric Routing Topology" in Chapter 7, "Configuring the Connection" , in the Cisco Service Control Engine Software Configuration Guide , and the relevant topics in the Cisco Service Control Application for Broadband User Guide
NetFlow V9
Starting from Release 3.1.0 of SCOS for Cisco Service Control, the product can deliver gathered reporting data over the NetFlow V9 export protocol. This protocol is an industry standard for delivering gathered reporting data for external application for collecting, aggregation, storage, and processing. The NetFlow export protocol enables the Service Control solution to integrate with a wide range of existing data collectors and reporters.
See Chapter 8, "Raw Data Formatting: The RDR Formatter and NetFlow Exporting" in the Cisco Service Control Engine Software Configuration Guide .
Subscriber synchronization in cascade setups
SCOS 3.1.0 enhances support of failover in cascade topologies by adding a synchronization process between the active and the standby SCE platforms. This process keeps the standby SCE platform constantly updated with the latest subscriber-related information (login, logout, and quota updates), in order to minimize information loss in the event of fail-over.
See the section "Synchronizing Subscriber Information in a Cascade System" in Chapter 9, "Managing Subscribers" in the Cisco Service Control Engine Software Configuration Guide .
Compatibility Information
SCOS 3.1.0 may be installed on the following Service Control Engine platforms:
•
•
•
SCOS 3.1.0 is not compatible with the following Service Control Engine platform:
•
Resolved Issues
The following issues were resolved in this release.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
SSH activity sometimes ended in an unstable state
•
During SSH activity, which usually includes session logout and login operations, the system sometimes ended in an unstable state due to file system violation.
This issue is fixed in SCOS 3.1.0.
Redirect packet was sometimes transmitted on wrong link
•
When a flow using different links for upstream and downstream was redirected, the redirect packet to the subscriber was transmitted on the downstream link, but included the source MAC address from the GET packet seen on the upstream link as destination MAC address. This MAC address was sometimes unknown to the device receiving it.
This issue is fixed in SCOS 3.1.0.
Dynamic Signature (DSS) caused a reboot after dozens of consecutive Apply operations
•
Applying a policy using DSS sometimes caused an infinite loop, resulting in a reboot of the SCE platform.
This issue is fixed in SCOS 3.1.0.
Reload of the SCE due to an expiry of an internal watchdog mechanism
•
Under the following conditions, the SCE platform sometimes reloaded due to an expiry of an internal watchdog mechanism:
–
AND
–
This issue is fixed in SCOS 3.1.0.
The saving process of application configuration was not resilient to reload
•
Running configuration of the application was not saved in cases of sudden reboots. In such cases, the SCE platform came up with no application configuration.
This issue is fixed in SCOS 3.1.0.
Failure to retrieve support file using FTP
•
An error occurred when attempting to retrieve a support file using FTP.
The failure to retrieve the support file was caused by a timeout on the FTP server. When the SCE produces the support file (in zip format), it first produces the contents locally and then adds the contents to the zip file. When the support file is created over an FTP connection, there are long periods of no data transfer during the creation of the zip internal data. These long periods of no data transfer can trigger a connection timeout on the FTP server.
This issue is fixed in SCOS 3.1.0.
PRPC authentication security level was set to default after RPC adapter restart
•
The PRPC connection to the SCE failed after restarting the PRPC server.
This occurred when the security level was changed to something other than the default (semi) and the PRPC server was restarted. After the restart, the security level reverts back to the default value.
This issue is fixed in SCOS 3.1.0.
Part of the quota information was not exchanged between two cascaded SCE platforms
•
Part of the quota information was not exchanged between two cascaded SCE platforms. This caused the failover in SCE cascade topology to be stateless with regard to quota.
This issue is fixed in SCOS 3.1.0 (see Subscriber synchronization in cascade setups).
Subscriber with many mappings did not send all lease time expiration notifications
•
A subscriber with many mappings did not send lease time expiration notification on some mappings.
This issue is fixed in SCOS 3.1.0
Link reflection failed to operate after long uptime
•
Link failure reflection sometimes failed to operate on a system with uptime of more than 24 days.
This issue is fixed in SCOS 3.1.0.
Attack-detector port-list showed random numbers in running-config
•
When a port list was configured for an attack-detector, the specified ports were not saved correctly to the running-config. A list of random numbers was saved.
This issue is fixed in SCOS 3.1.0.
Potential discard of packet under extreme network conditions
•
Under certain conditions, the Flow Filter rule used for congestion handling took effect a few mSec too late, allowing some packets to be discarded.
This issue is fixed in SCOS 3.1.0.
Access violation when configuring anonymous groups
•
The following two scenarios sometimes caused an access violation:
–
subscriber anonymous-group name sub1 IP-range 0.0.0.0/32and transmit traffic. Then remove this group and wait for the flow to end.Then configure:
subscriber anonymous-group name sub1 IP-range 0.0.0.0/0and transmit traffic.–
anonymous-group name sub1 IP-range 0.0.0.0/32andanonymous-group name sub2 IP-range 0.0.0.0/0Then remove sub1.
This issue is fixed in SCOS 3.1.0.
destConnectionStatus of the rdr-formatter group was missing in `show snmp MIB pcube-SE-MIB rdr-formatter' command
•
The MIB object destConnectionStatus of the rdr-formatter group was missing in CLI `
show snmp MIB pcube-SE-MIB rdr-formatter' command.This issue is fixed in SCOS 3.1.0.
rdrActiveConnectionTrap was not sent after reload of the SCE platform
•
The proprietary trap ` rdrActiveConnectionTrap ', which should be sent after completing a successful establishment of a connection with the RDR collector, was not sent upon system initialization.
This issue is fixed in SCOS 3.1.0.
Link up/down traps were not sent on all ports
•
The SNMP traps 'link up'/'link down', which should be sent for each port upon system initialization, were sent only on the first four ports of the SCE platform.
This issue is fixed in SCOS 3.1.0.
MIB object 'pmoduleType' returned wrong value in cascade setups
•
The MIB object pmoduleType of PcubeSeMib returned the wrong value in cascade setups, indicating that there were only two GBE ports in the SCE platform.
This issue is fixed in SCOS 3.1.0.
MIB variable ifMtu returned wrong value for traffic ports
•
The MIB-II variable ifMtu returned an incorrect value for the maximum packet size of the SCE platform traffic ports.
This issue is fixed in SCOS 3.1.0.
Some rdr-formatter MIB objects returned information only for category 1
•
Global MIB objects in the RdrFormatterGrp in the PcubeSeMib should indicate total values for all categories of the RDR formatter. Previously these objects contained only the values for Category 1.
This issue is fixed in SCOS 3.1.0.
Limitations and Restrictions
The upgrade to the SCOS 3.1.5 LA release may result in re-initialization of the SCE 1010 or SCE 2020 hardware Bypass module. This re-initialization process may cause a failure of the GBE link where the system stalls for a period of less than 1 sec.
The table below states the various cases when this re-initialization may occur (marked as "Yes").
The SCE platform may experience a reboot when a port scan operation is performed on the SCE platform management port. This reboot is initiated by the SCE platform due to scheduling optimization for detecting failover conditions in periods of less than 1 second in a configuration of two cascaded SCE platforms.
The following is recommended:
•
•
configure/interface linecard 0/0 no watchdog configure/watchdog software-reset disabledOpen Caveats
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
SCE reboot during PQI installation
•
The SCE platform may reload during pqi installation due to an internal sanity check. This problem only occurs if there are many iterations of the pqi installation process (more than 50).
Workaround: None
Cannot add VLAN mapping to VPN after removing mapping when subscriber mappings are logged in
•
When a VLAN mapping is removed from a VPN while subscriber mappings (IP@VPN) on the VPN are logged in, subsequent attempts to add a VLAN mapping to that VPN will fail with an internal error.
Only relevant to VLAN based VPNs scenarios, when not using automatic VLAN, but rather VLANs move from one VPN to another
Workaround: Do not remove VLAN mappings from VPNs while there are subscriber mappings logged in on that VPN.
Upstream label aging disabled
•
In MPLS/VPN Auto-Learn mode, using the default configuration, the upstream labels of both managed VPNs and non-VPNs are not aged, and therefore continue to occupy HW mapping resources.
Workaround : Manually configure an aging timeout interval for upstream aging, using the following commands.
SCE2000>enable 15 (enables root level) SCE2000><root level password> SCE2000#>configure (enters global configuration mode) SCE2000(config)#>interface linecard 0 (enters linecard configuration mode) SCE2000(config if)#>MPLS VPN validity-checks upstream-aging aging-timeout 11 (Configures the aging timeout) SCE2000(config if)#>do copy running-config startup-config (saves the change to the startup configuration)While removing all VPNs management operations cannot be performed
•
When removing all VPNs from the SM using the " --force " option, some management operations cannot be performed on the SCE until the operation completes. This occurs only when removing many VPNs that have active subscriber mappings in the SCE.
Workaround : Instead of removing the VPNs along with their subscriber mappings by using the --force option, remove the subscribers first, and only then remove the VPNs (without the --force option).
SCE-Sniffer RADIUS LEG might not work after PQI installation
•
After installing a SCA BB PQI file on the SCE platform and before applying a service configuration for the first time, the SCE application ignores all open flows. When a service configuration is applied for the first time, the SCE application starts processing new flows. However, older flows that were opened earlier are not processed, and no RDRs are generated for them. RADIUS sniffing is susceptible to this limitation because it is likely that the relevant RADIUS flow would be open before the first time a service configuration is applied
Workaround : The flow should be re-opened by restarting the SCE line-card after the service configuration is applied for the first time.
To restart the line-card through the Network Navigator GUI:
1.
2.
3.
After the line-card is restarted, the RADIUS flow is treated by the SCE application as a new flow, and is processed and reported.
Long SSH session cleanup time may result in temporary unavailability
•
Frequent SSH logouts and logins with less than a minute between a logout operation and login operation, along with other management operations, may result in system memory shortage or loss of the flash file system (which can be accessed again after reboot). These in turn may cause a reload of the SCE platform.
Workaround : Wait at least one minute after logging out from an SSH session before logging in again.
Upgrading the SM causes SCE failover in cascade topology
•
SCE platform performs failover procedure between active and standby SCE platforms in a cascaded pair when the connection to the SM goes down, even if no failover behavior is configured for this situation
Problems may be encountered in downgrading from Release 3.1.0 (or higher) to a previous release
•
When downgrading from SCOS 3.1.0 to previous release, a jvm exception is thrown. The SCE platform fails to downgrade and reboots continuously.
Workaround
–
Uninstall the pqi before downgrading using the following commands:
SCE2000#>configure SCE2000(config)#>in li 0 SCE2000(config if)#>pqi uninstall file <file-name>
Note
copy ftp://username:password@host-ip-address/full path /tffs0/app/install-pqi-name.pqi
–
1.
2.
3.
4.
–
Problems may be encountered in downgrading from Release 3.0.5 (or higher) to a previous release
•
Downgrading from a system running SCOS 3.0.5 (or higher) to a previous SCOS release may be unsuccessful until a second reload is performed. This is due to subscriber database incompatibility between 3.0.5 and previous versions resulting from the increase in the subscriber name size.
Workaround : Clear the subscriber database after package installation of the downgraded version and prior to the reload by deleting all files under the directory /tffs0/system/p3hidden/partydb/ .
RDRV1 destination startup configuration will fail in downgrading from Release 3.1.0 to a previous release
•
When configuring RDR formatter RdrV1 destinations (even when using the old, backward-compatible command syntax), the running-config and hence the startup-config are updated with the new (as of 3.1.0) format of the command, which implicitly states the protocol and transport type.
Due to this behavior, in a downgrade scenario, the startup configuration will fail to configure the RDR formatter destination, since protocol and transport type are not supported. This may result in loosing reports.
Workaround : Configure the RDR formatter again using the old syntax. The details can be derived from the config.txt file under /tffs0/system .
Link failure may be reflected to all ports if a port is flickering due to a HW problem
•
When link reflection on all ports with linecard aware is configured, the link failure may be reflected to all ports (rather than only to the relevant link) if one of the ports that is connected to the failed linecard is flickering due to a hardware problem.
Subscribers data synchronization is slower when static subscribers are configured
•
After the cascade links are up, the active box synchronizes the subscriber database to the standby box at a rate of ~1000 updates/sec. However the standby box can support this login rate only for dynamic subscribers. If there are static subscribers configured, it can take up to an hour to synchronize the subscriber database after the cascade links are up. However, once the standby box is synchronized, new subscribers are replicated to the standby box normally (at a maximal delay of 2 minutes).
CLI command `IP address' should indicate to the user that a reload of the SCE is required
•
After a change is made to the management IP/subnet, the SCE platform CLI should output a message notifying the customer that a reload is required for the changes to take effect.
'no service telnetd' command does not block the Telnet port
•
Disabling the Telnet server of the SCE (using the CLI command '
no service telnetd') disables any new Telnet connection to the SCE platform, but does not block the Telnet port.Workaround : There is no workaround that will enable blocking this specific service at a lower level.
Use the `
ip access-class' command to restrict access to the SCE platform at the IP level. Configuring the SCE platform to deny a certain IP address would prevent communication with that address using any IP-based protocol, including Telnet, FTP, ICMP and SNMP. The basic IP interface is low-level, blocking the IP packets before they reach the higher level services.Errors on invalid management agent notification during SCE reload
•
The following error may appear in the boot log file after an upgrade of the SCE platform from a release prior to 3.0.5 to release 3.0.5 and up:
"Error - Notification <number>does not exist."This occurs because some notification IDs are not valid since release 3.0.5. The fact that this command does not succeed does not cause any harm.
Workaround : Run the CLI command `
copy running-config startup-config'. This removes the old notification IDs from the configuration file.BWC controller gives less bandwidth than configured
•
When BWC has many short UDP flows associated with it, such as eMule flows with very few packets each, the bandwidth given to all flows is slower than configured.
Workaround : Configure Global Controllers to control the bandwidth.
There is no workaround when working with Service Bandwidth Controllers.
Potential memory overrun in cascaded environment with a high number of subscribers
•
Under rare conditions, the standby SCE platform of a cascaded pair crashes and restarts. This may happen in a scenario involving a heavy load of anonymous subscribers in cascade topology.
In such a case, only the standby box is affected, and therefore:
–
–
The configured attack threshold is set for each PPC separately
•
For certain types of attacks, an attack is detected by the SCOS attack-filter module only if it is three times stronger (as measured by flow rate per second) than the configured value.
This happens when the IP address common to all the flows of the attack is on the network side of the SCE platform, so all attacks of type 'single-side-network' have this problem
When the VAS Health Check initializes, the CLI command `show interface linecard 0 VAS-traffic-forwarding VAS server-id <id>' shows the server being UP even if it is actually Down
•
The operative state of a VAS server while the Health Check is in Init state is considered to be Up as shown in the CLI command "
show interface linecard 0 VAS-traffic-forwarding VAS server-id <id>". In addition, during this time, the SCE platform may forward VAS traffic to this server.Flow `opened from VAS' is misrouted if there is a FF rule to bypass
•
When VAS mode is enabled, the system generally assumes that traffic with a VLAN tag is VAS traffic coming from the VAS servers, and therefore forwards it to the non-VAS link.
However, under the following conditions, a flow will be forwarded by the SCE platform on the same link on which it was received and with no VLAN tag: · · ·
–
–
–
•
Packet Loss during Application Installation or Upgrade
•
When a PQI application file is installed or upgraded on the SCE, the SCE may lose a few packets for a few seconds. The overall percentage of this phenomenon is very low.
Workaround : It is advised to perform the upgrade in non peak time.
rdrActiveConnectionTrap is not sent upon re-establishment of connection when forwarding mode is multicast
•
In an environment with several RDR formatter categories and different destinations configured for multicast forwarding, if the connection is lost between one of the destinations and the RDR formatter, when the connection is re-established, the rdrActiveConnectionTrap is not sent.
`show snmp MIB pcube-SE-MIB port' returns wrong number of ports
•
The CLI command `
show snmp MIB pcube-SE-MIB port' returns the wrong number of ports, because Mng port 2 is treated as traffic port instead of 2nd management port.Workaround : Use SNMP browser rather than CLI command.
Obtaining Technical Assistance
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at any time, 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.
To access Cisco.com, go to http://www.cisco.com.
Technical Assistance Center
The Cisco Technical Assistance Center (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.
•
Contacting TAC by Using the Cisco TAC Website
If you have a priority level 3 (P3) orpriority level 4 (P4) problem, contact TAC by going to the TAC website http://www.cisco.com/tac.
P3 and P4 level problems are defined as follows:
•
•
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to http://tools.cisco.com/RPF/register/register.do.
If you cannot resolve your technical issue by using the TAC online resources, Cisco.comregistered users can open a case online by using the TAC Case Open tool at http://www.cisco.com/tac/caseopen.
Contacting TAC by Telephone
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 http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
P1 and P2 level problems are defined as follows:
•
•
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)
This Document Applies to These Products
- Collaboration Endpoints - Retired Products
- Conferencing - Retired Products
- Contact Center - Retired Products
- Optical Networking - Retired Products
- Routers - Retired Products
- Security - Retired Products
- Servers - Unified Computing (UCS) Retired Products
- Storage Networking Retired Products
- Switches - Retired Products
- Video - Retired Products
- Wireless - Retired Products