CSM 2.0 bugs

Hi,
I would like to start something like a "CSM 2.0 bug list" thread. I started to test the new version and the first bug I encountered is IMHO quite a critical one (and obvious one). Its nice that the new version has a new tab thats named "Service Packs", yet SMUs that are covered by installed service packs are still marked es "not installed" instead of "superceeded", which is very bad. Not that I want to criticize tools that come for free too much, but sometimes I really wonder if anyone thinks these thing through before they are released.

Second bug: I ecountered the same problem which was already reported:
https://supportforums.cisco.com/discussion/12172116/csm20-smu-download-fails
Though I got no email yet, so I am not sure how to solve this. Any ideas?

Similar Messages

  • Hitting the know bug CSCso59571 in CSM 3.3

    Hi,
    I am hitting the known bug CSCso59571 in CSM 3.3 and when I try to resolve the bug by entering the following command
    pdreg -r Apache -e "NMSROOT\MDC\Apache\Apache.exe" -f "-d NMSROOT\MDC\Apache -D SSL" -d TomcatMonitor
    It says path NOT found, I tried entering "C:\Progra~1\CSCOpx", but still it doesn't work.
    Can I get any help on this ?

    I assume you first entered the pdreg -u command to unregister Apache:
    pdreg -u Apache
    After doing that, the command you want to run (assuming CSM is installed into C:\PROGRA~1\CSCOpx) is:
    pdreg -r Apache -e "C:\PROGRA~1\CSCOpx\MDC\Apache\Apache.exe" -f "-d C:\PROGRA~1\CSCOpx\MDC\Apache -D SSL" -d TomcatMonitor
    Note: if CSM is installed in another directory, you must use the path to its installation location instead of C:\PROGRA~1\CSCOpx.

  • CSM 3.3.1 - deployment bug? after installing SP1&SP2

    Hi all,
    I've recently installed CSM 3.3.1 with SP1 and SP2 and I've encountered quite serious (for me) problem. Has  anyone met strange situations after installing service packs?
    When I discover new device (i.e. router with 15.1 ios version) and make changes in ZBF policy, CSM deploys new configuration and everything seems to be fine. I must stress that only seems.
    When for example I want to make only small changes to that device (by adding new username ans password) I make "preview configuration" and I see that CSM deletes part of ZBF policy - 10 of 12 zone-pair. For example for some reasons manager makes "no service-policy ...." in zone-pair. When I do another "preview configuration" (after adding another username) it deletes those empty zone-pairs. I thoung maybe naming doesn't suit it and I need to recreate all policy through CSM - nooooo. It did not help. Still it tried to delete some of policy.
    Even when I created all ZBF policies from CSM Ive got situation when in one preview config it removes security-policy from zone-pair and after deployment in second preview it adds these security-policies to previous zone-pair. Its happaning in a  loop.
    Or another strange behaviour is when I add new username it does sth like this:
    In "preview configuration" there is
    policy-map type inspect CSM_ZBF_POLICY_MAP_1
    no class class-default
    class class-default
        drop
    while in GUI in CSM there is action inspect defined.
    I've looked through bugtool, but with no success, so need any help.
    regards

    hi,
    thx for interest,
    I didn't open the TAC case casue I didn't have much time for it, however the issue is resolved. It occured that SP2 to CSM was problematic. Right now I've got 3.3.1 version with SP1 and everything works just fine. To make sure that it was it, I installed then SP2 and the problem started again.
    I don't have configuration saved but actually there wasn't much of it. It was a fresh system and only 1 or 2 devices ware added so I suppose it should be easy to restore the situation.
    if you got any new info please let me know
    regards
    Przemek

  • Problem with Syncing configuration to our CSM

    Recently we have had problems syncing between our pair of redundant CSM's.
    Here is the behavior we observe when we run the command on one of our 6500.
    ! config 6500-2
    module ContentSwitchingModule 2
    ft group 1 vlan 4
      priority 10 alt 20
    ! config 6500-1
    module ContentSwitchingModule 2
    ft group 1 vlan 4
    6500-2#hw-module csm 2 standby config-sync
    After we run this command on 6500-2 the log shows that the sync happens and the CSM config is deleted on 6500-1 and then nothing happens.
    Here is the exact logout on each of the 6500.
    6500-2(ACTIVE)
    May 28 17:45:11.353 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Active: Bulk sync started
    May 28 17:45:11.369 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Active: Sending configurations to Standby CSM, this may take several minutes!
    May 28 17:45:12.749 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Active: Sending configuration to Standby CSM
    May 28 17:45:14.869 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Active: Sending configuration to Standby CSM
    May 28 17:45:24.345 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Active: Manual bulk sync completed
    May 28 17:45:24.349 est: %CSM_SLB-4-REDUNDANCY_WARN: Module 2 FT warning: Config Sync does not save Standby running-config to startup-config
    6500-1(STANDBY)
    May 28 17:45:17.088 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Standby: Started clearing configuration
    May 28 17:45:17.088 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Standby: Completed clearing configuration
    May 28 17:45:17.096 est: %CSM_SLB-4-REDUNDANCY_WARN: Module 2 FT warning: Standby: Config Sync does not save running-config to startup-config
    May 28 17:45:17.100 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Standby: Previous configuration are being deleted from supervisor
    May 28 17:45:17.104 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Standby: Previous configuration being deleted on Standby CSM
    May 28 17:45:17.104 est: %CSM_SLB-6-REDUNDANCY_INFO: Module 2 FT info: Standby: New configuration are being configured
    As you can see the configuration ends up being deleted from the STANDBY and the new configuration never gets configured to 6500-1(STANDBY).
    We have tried replacing the SUP engine however this did not help.  We will try to replace the CSM next.  If anyone can shed some light on why this would happen I would apreciate it.

    Hi
    pls check for IOS bug CSCtd09117  and CSCsx64648

  • What is the current way of managing the CSM using a GUI?

    Hi, My customer is using CiscoView device manager 1.1 for the content switching module but it's a nightmare and full of bugs, it's also end of life.
    Does anyone know the current way of monitoring or configuring the Content Switching Module?
    Many Thanks in advance
    Dom

    Hi Dom,
    I believe what you are looking for is called the Cisco Application Networking Manager 3.0.  This is the GUI configuration, management, and monitoring tool for the Application Control Engine (ACE), but also supports the managment of CSS, CSM, CSM-S, and GSS.  See the link for more details.
    Also, it should be noted that both the CSM and CSM-S have recently been announced End-of-Life.  The ACE would be your path after the CSM.  See the link for more details on that too.
    Hope this helps,
    Sean

  • CSM not load-balancing properly

    Folks,
    I'm seeing that CSM is not loadbalancing properly to all the servers in the serverfarm.
    I simulated a failover of one of the servers TS05 and brought it back. After coming online, CSM sent no traffic to that server, as shown below:
    C7606-1#show mod csm 1 serverfarms name WHTTP detail | i OPER
    TS01-RADIO, weight = 8, OPERATIONAL, conns = 2
    TS02-RADIO, weight = 8, OPERATIONAL, conns = 4
    TS03-RADIO, weight = 8, OPERATIONAL, conns = 2
    TS04-RADIO, weight = 8, OPERATIONAL, conns = 4
    TS05-RADIO, weight = 8, OPERATIONAL, conns = 0
    TS06-RADIO, weight = 8, OPERATIONAL, conns = 1
    C7606-1#show mod csm 1 serverfarms name WHTTP detail | i OPER
    TS01-RADIO, weight = 8, OPERATIONAL, conns = 1
    TS02-RADIO, weight = 8, OPERATIONAL, conns = 3
    TS03-RADIO, weight = 8, OPERATIONAL, conns = 1
    TS04-RADIO, weight = 8, OPERATIONAL, conns = 3
    TS05-RADIO, weight = 8, OPERATIONAL, conns = 0
    TS06-RADIO, weight = 8, OPERATIONAL, conns = 1
    C7606-1#show mod csm 1 serverfarms name WHTTP detail | i OPER
    TS01-RADIO, weight = 8, OPERATIONAL, conns = 2
    TS02-RADIO, weight = 8, OPERATIONAL, conns = 4
    TS03-RADIO, weight = 8, OPERATIONAL, conns = 1
    TS04-RADIO, weight = 8, OPERATIONAL, conns = 3
    TS05-RADIO, weight = 8, OPERATIONAL, conns = 0
    TS06-RADIO, weight = 8, OPERATIONAL, conns = 1
    C7606-1#show mod csm 1 serverfarms name WHTTP detail | i OPER
    TS01-RADIO, weight = 8, OPERATIONAL, conns = 2
    TS02-RADIO, weight = 8, OPERATIONAL, conns = 1
    TS03-RADIO, weight = 8, OPERATIONAL, conns = 0
    TS04-RADIO, weight = 8, OPERATIONAL, conns = 2
    TS05-RADIO, weight = 8, OPERATIONAL, conns = 0
    TS06-RADIO, weight = 8, OPERATIONAL, conns = 2
    C7606-1#show mod csm 1 serverfarms name WHTTP detail | i OPER
    TS01-RADIO, weight = 8, OPERATIONAL, conns = 2
    TS02-RADIO, weight = 8, OPERATIONAL, conns = 1
    TS03-RADIO, weight = 8, OPERATIONAL, conns = 1
    TS04-RADIO, weight = 8, OPERATIONAL, conns = 2
    TS05-RADIO, weight = 8, OPERATIONAL, conns = 0
    TS06-RADIO, weight = 8, OPERATIONAL, conns = 3
    C7606-1#show mod csm 1 serverfarms name WHTTP detail | i OPER
    TS01-RADIO, weight = 8, OPERATIONAL, conns = 2
    TS02-RADIO, weight = 8, OPERATIONAL, conns = 1
    TS03-RADIO, weight = 8, OPERATIONAL, conns = 1
    TS04-RADIO, weight = 8, OPERATIONAL, conns = 2
    TS05-RADIO, weight = 8, OPERATIONAL, conns = 0
    TS06-RADIO, weight = 8, OPERATIONAL, conns = 4
    My config is attached with this post:
    Can there be anything wrong with my VARIABLES?
    C7606-1#show mod csm 1 variable | i SLOW
    REAL_SLOW_START_ENABLE 1
    C7606-1#

    Folks - I upgraded the code to 4.2(6) and thought that bug CSCei26434 was solved, but still see the same error where CSM is not balancing properly.
    No Traffic Running:
    ===================
    C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
    TS01-RADIO, weight = 8, OPERATIONAL, conns = 0
    TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
    C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
    TS01-RADIO, weight = 8, OPERATIONAL, conns = 0
    TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
    C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
    TS01-RADIO, weight = 8, OPERATIONAL, conns = 0
    TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
    Started Traffic
    ===============
    C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
    TS01-RADIO, weight = 8, OPERATIONAL, conns = 60
    TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
    C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
    TS01-RADIO, weight = 8, OPERATIONAL, conns = 101
    TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
    C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
    TS01-RADIO, weight = 8, OPERATIONAL, conns = 188
    TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
    The newly ALIVE server passed the probe test:
    =============================================
    C7606-1#show mod csm 1 probe detail | inc 102
    192.168.122.102:1813 RADIUS RADIUS (default) OPERABLE
    192.168.122.102:9202 WSP_SCL WSP_SCL (default) OPERABLE
    192.168.122.102:9201 WSP_CO WSP_CO (default) OPERABLE
    192.168.122.102:9200 WSP_CL WSP_CL (default) OPERABLE
    192.168.122.102:8080 WHTTP WHTTP (default) OPERABLE
    192.168.122.102:8080 TP_8080 TP_8080 (default) OPERABLE
    192.168.122.102:7080 PUSH_WWW PUSH_WWW (default) OPERABLE
    Still no connections:
    =====================
    C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
    TS01-RADIO, weight = 8, OPERATIONAL, conns = 583
    TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
    C76061#
    Brought another server on-line:
    ================================
    C7606-1#
    1w4d: %CSM_SLB-6-RSERVERSTATE: Module 1 server state changed: SLB-NETMGT: TCP health probe re-activated server 192.168.122.106:8080 in serverfarm 'WHTTP'
    1w4d: %CSM_SLB-6-RSERVERSTATE: Module 1 server state changed: SLB-NETMGT: TCP health probe re-activated server 192.168.122.106:8080 in serverfarm 'TP_8080'
    1w4d: %CSM_SLB-6-RSERVERSTATE: Module 1 server state changed: SLB-NETMGT: TCP health probe re-activated server 192.168.122.106:7080 in serverfarm 'PUSH_WWW'
    1w4d: %CSM_SLB-6-RSERVERSTATE: Module 1 server state changed: SLB-NETMGT: UDP health probe re-activated server 192.168.122.106:9200 in serverfarm 'WSP_CL'
    1w4d: %CSM_SLB-6-RSERVERSTATE: Module 1 server state changed: SLB-NETMGT: UDP health probe re-activated server 192.168.122.106:1813 in serverfarm 'RADIUS'
    1w4d: %CSM_SLB-6-RSERVERSTATE: Module 1 server state changed: SLB-NETMGT: UDP health probe re-activated server 192.168.122.106:9201 in serverfarm 'WSP_CO'
    C7606-1#
    C7606-1#
    1w4d: %CSM_SLB-6-RSERVERSTATE: Module 1 server state changed: SLB-NETMGT: UDP health probe re-activated server 192.168.122.106:9202 in serverfarm '
    No connections to the NEW Server even
    ======================================
    C7606-1#show mod csm 1 serverfarms name WHTTP detail | inc OPER
    TS01-RADIO, weight = 8, OPERATIONAL, conns = 2988
    TS02-RADIO, weight = 8, OPERATIONAL, conns = 0
    TS06-RADIO, weight = 8, OPERATIONAL, conns = 0

  • Firmware bug w/Intel Mini

    Greetings to all.
    There is currently a bug in the Mini's firmware that poses as a slight problem for me. I'm sure some people are aware of this, but Apple has yet to present a solution.
    Problem:
    While booting a Legacy OS, such as Linux (Grub/LILO), or Windows, the EFI firmware's Legacy BIOS (CSM) hangs when a monitor is NOT connected.
    This appears to be a glitch in the VGA Rom BIOS that the CSM uses to allow legacy OS's to initialize and use the i950 Graphics Chipset.
    This does not appear to be DDC related, as a KVM allows the system to boot a Legacy OS, even though a KVM provides no such signals.
    It also isn't OS related. We are talking about EFI/CSM here, not Mac OS X or Linux. It's strictly a firmware issue with the Legacy OS code sitting inside EFI.
    Why hasn't Apple fixed this? I'm sure it's a trivial problem- just about every other computer out there (regardless of using EFI or not) can and will boot if no monitor is attached.
    There are some of us who would like to run Mini's in server configurations as they are excellent machines that borderline on uber-powerful embedded platforms. I don't think it's out of line to ask that the firmware correctly handle a situation where one might be booting Linux or Windows without a monitor attached.
    It is possible to resolve this issue via using a monitor "terminator" to provide a dummy signal that a monitor is attached, but I'm sure the solution is equally as simple on Apple's part (if a monitor isn't detected, continue to boot anyways!).
    -SC

    If you join the Apple Developer Connection (there is a free option), you can submit bugs directly to Apple. That might be a better way to handle this issue.
    http://developer.apple.com/bugreporter/
    -Doug

  • CSM 4.7 Report Manager User Report Issue

    Hi,
    Since we upgraded CSM 4.7 from 4.6, suddenly Report Manager is unable to generate VPN User Report, same as Connection Profile Report and VPN Device Usage Report, error message shows below. However, under FW-Summary Botnet (Top Destination, Top Services, Top Sources) those reports are fine. If I ran older than the time we upgraded 4.7 (like last week, last month) I could get the data, only right after the upgrade, no data since then. We opened a TAC ticket, but they could not resolve it and said it is a known bug, also applied patch which did not work either. In Event Manager, it has all the event logs, and Configuration Manager seems to show Event Manager setting correct as well. Anyone has encounter this issue and has solution? Please help, thank you!
    ***Error Message***
    No Records Found
    - Event Manager may be down or no data received from Device

    Hi @shawng001,
    I have installed the CSM 4.7 on my VM windows 2008 server pack2, i am getting the logs from my devices like ASA firewall and Router. But i am unable to generate report logs and mail alerts. I hope you can help me in this...........
    Thanks in advance....
    @udaychalla 

  • Adding a new FWSM context through CSM

    Hi,
    I have a Multi-Context FWSM ver 4.0 and a CSM ver 3.3.1 to manage it.
    I need to know is there any know issue when creating a new context through the CSM UI !!!
    By the way, the devices (FWSM and CSM) user accounts are managed by an ACS ver 4.2
    Best regards,
    Akram

    Hi Akram.
    here is the user guide section on how to add contexts on the latest csm 4.0.1:
    http://www.cisco.com/en/US/docs/security/security_management/cisco_security_manager/security_manager/4.0.1/user/guide/pxcontexts.html
    For known open bugs list affecting this version, you can check the release notes:
    http://www.cisco.com/en/US/docs/security/security_management/cisco_security_manager/security_manager/4.0.1/release/notes/csmrn401.html#wp835872
    from that list, i see CSCtd60804 affects 4.0.1 . this can be a problem if you are deploying to an active/active setup.
    Regards,
    Fadi.
    Does this answer your question? if yes, please mark it as resolved.

  • CSM does not show rule numbers when using sections?

    I started using sections in access rules within CSM 4.2 but all the rules that are within these section do not show anymore the rule number in the list.
    Can this be changed? Is this a bug?

    The numbers are shown, but you have to expand the column. Somehow cisco makes the no. column to small to see the numbers in a section by default. And they replace the numbers with a dot or two as soon as it is too small to display the numbers.

  • CSM IPS Manager doesn't display IPS sensors.

    I am doing inital configuration of the CSM v3.0 The IPS sensor 4250xl that I have added to CSM doesn't show up in the IPS Manager. Moreover, the Devices->Sensor window doesn't appear to be displayed correctly - there is a browser icon indicating missing content.
    Any ideas what may be the issue. Thanks.

    You might be running into a bug here. The bug-Id is:CSCsa83631

  • CSM Displaying incorrect information

    On our current infastructure we have a number of Vservers built , utilising vserver SSO-GP-443
    serverfarm SSO-GP-SY-443 backup SSO-GP-NW-443
    Both server farms show up and available until we fail the primary server farm, when this happens the Vserver shows as below
    SSO-GP-443 SLB TCP 172.27.117.25/32:443 ALL OUTOFSERVICE 1
    Although on testing, traffic is passed to the servers and the display may be purely cosmetic, but we would like this confirmed and also if its a known bug , if this is the case when this bug will be fixed
    c6slb-apc.4-2-4.bin CSM Code
    s72033-advipservicesk9_wan-mz.122-18.SXF5.bin Switch Code

    If the data is incorrect, the system generates error messages and displays the page on which the error occurs.
    http://www.cisco.com/en/US/products/ps6498/products_user_guide_chapter09186a00806b79f3.html#wp1055751

  • FWSM and CSM (Load Balance) in the same chassi

    Folks,
    Is there any type of best practice (you ** must ** do like this) when you are going to implement the FWSM and the CSM modules on the same 6509 chassi ?
    PS: The CSM is not doing FW loadbalance, it is doing loadbalance to servers located in a DMZ
    PATH:
    (outside) FWSM (inside) -> MSFC -> (inside) PIX (dmz) -> CSM  , CSM -> (dmz) PIX (inside) -> MSFC -> (inside) FWSM
    My main doubts:
    1) FWSM using multi-context, Is there any integration problem with CSM ?
    2) FWSM and CSS in routed mode, Is there any integration problem with both modules ?
    3) Is it really necessary to operate the FWSM module in bus mode when using CSM in the same chassi (fabric switching-mode force bus) ?
    Cisco Says:
    "The CSM line card operates in bus mode. When using the CSM in conjunction with the FWSM line card,
    Cisco recommends forcing the FWSM to operate in bus mode using the
    fabric switching-mode force bus command. When service modules such as the CSM and the FWSM
    operate in bus mode, traffic from DFC-enabled line cards still use the fabric connection."
    In past it was a workaround due a bug, but I have found this recommendadon and know I am a little confused.
    Tks !!!

    Luis-
    You will want to used a routed mode on the CSM so that the Firewall contexts don't see eachothers MAC Addresses for any traffic not destine to to a VIP.  On the CSM VLANs, you will want to create alias IPs to use as the next hop destination between contexts for non-VIP traffic. Other than that, the CSM has no concept of contexts, so as long as the traffic is symetric when it flows through the CSM VLANs, it will be happy.
    Regards,
    Chris

  • CSM Deployment to a 2811 Failure

    Hi,
    I manage 213 2811s with CSM and there is one site that fails everytime I go to deploy changes to it. It fails with, "Failed to parse response from device. Cause: Upload configuration failed since the CT response from device XXXX is malformed. JDOM exception while parsing XML input stream."
    I have tried reimporting the policies but I get the same error on deployment. Any ideas?

    I tried to look it up in the Bug Toolkit and it says it is only available to Cisco employees. The router in question is running c2800nm-advsecurityk9-mz.124-15.T1.bin with 12.4(13r)T ROM. What version fixes it?

  • Adding GSS on top of existing CSM deployment

    Hi there,
    I have an existing CSM deployment that is performing L4 load-balancing for a number of serverfarms. Each farm is presented as it's own VIP, so no VIP has multiple farms on different ports.
    I'm trying to add a GSS in front of this and I'd like to be able to have the GSS read load information from the CSM.  To accomplish this I've enabled CAPP on my CSM, and created a shared Keepalive that points to one of the internal addresses for the CSM (not a VIP address).  I've assigned this shared keepalive to two Answers, providing the VIP address of the service, and performing KAL-AP keepalives by Tag value.  In my vserver I've added the 'domain <TAG>' and entered in the matching Tag on the KAL-AP KeepAlive section of the Answer setup screen.
    With these steps completed, when I look at the Answer status under Monitoring > Answers > Answer Status,  the GSS always sees it as 'Offline (Load:255)'.  I've verified that the CAPP communication is successful by watching the stats on both the GSS Answer Keepalive stats page, and by the output of 'show mod csm x capp'.  It seems like the communication is working just fine.  Any ideas why the GSS isn't marking my Answers available?
    I'm using GSS 3.2.0.0.15 and CSM 4.3(5).
    Thanks in advance!
    Brandon

    Hi Chris,
    Thanks for the reply.  I ended up opening a TAC case to troubleshoot, and found I was running into the following bug:
    CSCsi70659 CSM sends vserver load of 255 for KAL-AP by tag
    Symptom:
    When CAPP UDP is enabled on the CSM, the CSM will return a load of 255 for vservers that are being probed by a KAL-AP keepalive.
    Workaround:
    Perform a 'no inservice' followed by an 'inservice' on the vserver.
    I executed the workaround and now my GSS is correctly pulling load information from the CSM.
    Thanks,
    Brandon

Maybe you are looking for