VSM module: A9K-VSM-500 CGN / IPv6 Performance

Hi,
I was wondering if there is more information regarding the VSM performance numbers similar to what is listed on the ISM datasheet for CGN and IPv6 migration features.
http://www.cisco.com/c/en/us/products/collateral/routers/asr-9000-series-aggregation-services-routers/data_sheet_c78-663164.html
ISM:
● Maximum 20 million simultaneous sessions for CGN and DS-Lite, and 15 million simultaneous sessions for NAT64.
● Maximum 1 million sessions set up per second
VSM:
Appreciate your response.
thanks
prashanth

Thanks for the update!   Do you think the CGN numbers will be posted soon?
regards
-P

Similar Messages

  • ASR9001 module A9K-MPA-20X1GE issue

    Hi all!
    Who knows, what does these messages mean?
    LC/0/0/CPU0:Oct 22 10:53:32.120 : envmon_lc[160]: %PLATFORM-ENVMON-4-OPERATION_WARN : Unable to get plug sensor data, error code 'Subsystem(2890)' detected the 'fatal' condition 'Code(0)' 
    RP/0/RSP0/CPU0:Oct 22 10:53:32.860 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:ADMIN DOWN
    LC/0/0/CPU0:Oct 22 10:53:32.862 : lda_server[65]: %PLATFORM-LDA-3-MPA_BAY_SW_ERROR : Unable to initialize MPA in bay: 0, Module has been shutdown due to identify test failure (0x00000000 - No error)  : pkg/bin/lda_server : (PID=40990) :  -Traceback= 4ed5159c 4bf1eed0 4bf1efdc 4d02c28c 4d02a1f4 4ba73a44 4ba71554 4d029ddc 4bada400
    RP/0/RSP0/CPU0:Oct 22 10:53:33.860 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: UNPOWERED
    Is this hardware or software issue? What do you think?
    I think we have faced with hardware issue of module A9K-MPA-20X1GE.
    More outputs:
    RP/0/RSP0/CPU0:asr9001#sh ver
    Tue Oct 22 10:53:46.186 UTC
    Cisco IOS XR Software, Version 4.3.2[Default]
    Copyright (c) 2013 by Cisco Systems, Inc.
    ROM: System Bootstrap, Version 2.01(20130627:172232) [ASR9K ROMMON], 
    asr9001 uptime is 6 minutes
    System image file is "bootflash:disk0/asr9k-os-mbi-4.3.2/0x100000/mbiasr9k-rp.vm"
    cisco ASR9K Series (P4040) processor with 8388608K bytes of memory.
    P4040 processor at 1500MHz, Revision 2.0
    ASR-9001 Chassis
    2 Management Ethernet
    4 TenGigE
    4 DWDM controller(s)
    4 WANPHY controller(s)
    219k bytes of non-volatile configuration memory.
    2880M bytes of hard disk.
    3932144k bytes of disk0: (Sector size 512 bytes).
    Configuration register on node 0/RSP0/CPU0 is 0x102
    Boot device on node 0/RSP0/CPU0 is disk0:
    Package active on node 0/RSP0/CPU0:
    iosxr-infra, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-infra-4.3.2
        Built on Sun Sep  1 19:21:10 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    iosxr-fwding, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-fwding-4.3.2
        Built on Sun Sep  1 19:21:10 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    iosxr-routing, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-routing-4.3.2
        Built on Sun Sep  1 19:21:10 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    iosxr-diags, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-diags-4.3.2
        Built on Sun Sep  1 19:21:10 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    iosxr-ce, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-ce-4.3.2
        Built on Sun Sep  1 19:21:10 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-os-mbi, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-os-mbi-4.3.2
        Built on Sun Sep  1 19:23:39 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-base, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-base-4.3.2
        Built on Sun Sep  1 19:21:14 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-fwding, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fwding-4.3.2
        Built on Sun Sep  1 19:21:14 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-diags-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-diags-supp-4.3.2
        Built on Sun Sep  1 19:21:19 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-scfclient, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-scfclient-4.3.2
        Built on Sun Sep  1 19:21:22 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-cpp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-cpp-4.3.2
        Built on Sun Sep  1 19:21:10 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-ce, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-ce-4.3.2
        Built on Sun Sep  1 19:21:16 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-mini-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mini-px-4.3.2
        Built on Sun Sep  1 19:27:30 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    iosxr-mgbl, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-mgbl-4.3.2
        Built on Sun Sep  1 19:28:25 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-mgbl-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mgbl-supp-4.3.2
        Built on Sun Sep  1 19:28:25 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-mgbl-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mgbl-px-4.3.2
        Built on Sun Sep  1 19:28:37 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-fpd, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fpd-4.3.2
        Built on Sun Sep  1 19:29:15 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-fpd-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fpd-px-4.3.2
        Built on Sun Sep  1 19:29:40 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9K-doc-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9K-doc-supp-4.3.2
        Built on Sun Sep  1 19:29:07 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-doc-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-doc-px-4.3.2
        Built on Sun Sep  1 19:29:14 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    Boot device on node 0/0/CPU0 is mem:
    Package active on node 0/0/CPU0:
    iosxr-infra, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-infra-4.3.2
        Built on Sun Sep  1 19:21:10 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    iosxr-fwding, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-fwding-4.3.2
        Built on Sun Sep  1 19:21:10 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    iosxr-routing, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-routing-4.3.2
        Built on Sun Sep  1 19:21:10 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    iosxr-diags, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-diags-4.3.2
        Built on Sun Sep  1 19:21:10 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    iosxr-ce, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-ce-4.3.2
        Built on Sun Sep  1 19:21:10 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-os-mbi, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-os-mbi-4.3.2
        Built on Sun Sep  1 19:23:39 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-base, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-base-4.3.2
        Built on Sun Sep  1 19:21:14 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-fwding, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fwding-4.3.2
        Built on Sun Sep  1 19:21:14 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-diags-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-diags-supp-4.3.2
        Built on Sun Sep  1 19:21:19 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-scfclient, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-scfclient-4.3.2
        Built on Sun Sep  1 19:21:22 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-cpp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-cpp-4.3.2
        Built on Sun Sep  1 19:21:10 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-ce, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-ce-4.3.2
        Built on Sun Sep  1 19:21:16 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    asr9k-mini-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mini-px-4.3.2
        Built on Sun Sep  1 19:27:30 UTC 2013
        By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
    RP/0/RSP0/CPU0:asr9001#
    RP/0/RSP0/CPU0:asr9001#
    RP/0/RSP0/CPU0:asr9001#
    RP/0/RSP0/CPU0:asr9001#
    RP/0/RSP0/CPU0:asr9001#sh log
    Tue Oct 22 10:54:22.823 UTC
    Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
        Console logging: level warnings, 44 messages logged
        Monitor logging: level debugging, 0 messages logged
        Trap logging: level informational, 0 messages logged
        Buffer logging: level debugging, 148 messages logged
    Log Buffer (307200 bytes):
    RP/0/RSP0/CPU0:Oct 22 10:47:29.090 : init[65540]: %OS-INIT-7-MBI_STARTED : total time 8.814 seconds
    RP/0/RSP0/CPU0:Oct 22 10:47:29.113 : imio[64]: %PLATFORM-IMIO-3-OPERATION_NOTIFY : imio_main: cold start  
    RP/0/RSP0/CPU0:Oct 22 10:48:42.672 : sysmgr[96]: %OS-SYSMGR-5-NOTICE : Card is COLD started 
    RP/0/RSP0/CPU0:Oct 22 10:48:50.075 : init[65540]: %OS-INIT-7-INSTALL_READY : total time 89.801 seconds
    RP/0/RSP0/CPU0:Oct 22 10:48:51.803 : sysmgr[407]: %OS-SYSMGR-6-INFO : Backup system manager is ready 
    RP/0/RSP0/CPU0:Oct 22 10:48:52.088 : sc_reddrv[376]: imio_lance2_init_interrupts:
    RP/0/RSP0/CPU0:Oct 22 10:48:58.262 : sysmgr[96]: %OS-SYSMGR-7-DEBUG : node set to DSC 
    RP/0/RSP0/CPU0:Oct 22 10:49:04.763 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-SYSTEM_COLD_START : System cold start detected.  Resetting Line Cards.
    RP/0/RSP0/CPU0:Oct 22 10:49:06.487 : pwr_mgmt[360]: %PLATFORM-PWR_MGMT-2-MODULE_FAILURE : Power-module 0/PM1/SP failure condition raised : Module input voltage out of range
    RP/0/RSP0/CPU0:Oct 22 10:49:07.565 : online_diag_rsp[427]: %DIAG-DIAG-6-RUN_MINIMUM : ASR9001-RP 0/RSP0/CPU0: Running Minimum Diagnostics...
    RP/0/RSP0/CPU0:Oct 22 10:49:09.369 : envmon[204]: %PLATFORM-ENVMON-4-FANTRAY_RPM : Fan tray RPM warning on slot 0/FT0/SP
    RP/0/RSP0/CPU0:Oct 22 10:49:12.761 : bpe[144]: %PLATFORM-BPE-5-INFO : successfully retrieved i2c eeprom
    RP/0/RSP0/CPU0:Oct 22 10:49:12.969 : shelfmgr[381]: %PLATFORM-SHELFMGR_HAL-7-CAN_INFO : Can API: slot 0 online event.
    RP/0/RSP0/CPU0:Oct 22 10:49:12.991 : shelfmgr[381]: %PLATFORM-SHELFMGR_HAL-3-POWER_SUPPLY_REDUNDANCY : Power Supply Failures are not protected.
    RP/0/RSP0/CPU0:Oct 22 10:49:13.624 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/FT0/SP inserted 
    RP/0/RSP0/CPU0:Oct 22 10:49:13.780 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/PM0/SP inserted 
    RP/0/RSP0/CPU0:Oct 22 10:49:13.788 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/PM1/SP, state: FAILED
    RP/0/RSP0/CPU0:Oct 22 10:49:13.789 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/PM1/SP inserted 
    RP/0/RSP0/CPU0:Oct 22 10:49:13.800 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/RSP0/CPU0, state: IOS XR RUN
    RP/0/RSP0/CPU0:Oct 22 10:49:18.393 : envmon[204]: %PLATFORM-ENVMON-3-OPERATION_ERROR : Failed in envmon lwmconnect.message channel connection failed!,-1 error code 'Subsystem(8191)' detected the 'unknown' condition 'Code(63)': Unknown Error(511) 
    RP/0/RSP0/CPU0:Oct 22 10:49:19.395 : envmon[204]: %PLATFORM-ENVMON-3-OPERATION_FAIL : Failed in envmon_fantray_alarms.7076, error code 'Subsystem(8191)' detected the 'unknown' condition 'Code(63)': Unknown Error(511) 
    RP/0/RSP0/CPU0:Oct 22 10:49:19.395 : envmon[204]: %PLATFORM-ENVMON-2-ENV_CONDITION : Outstanding environmental condition exists in the chassis
    RP/0/RSP0/CPU0:Oct 22 10:49:19.815 : invmgr[250]: lance_client_init: Client already connected
    RP/0/RSP0/CPU0:Oct 22 10:49:20.816 : invmgr[250]: lance_client_init: Client already connected
    RP/0/RSP0/CPU0:Oct 22 10:49:21.817 : invmgr[250]: lance_client_init: Client already connected
    RP/0/RSP0/CPU0:Oct 22 10:49:22.843 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/RSP0/CPU0 inserted 
    RP/0/RSP0/CPU0:Oct 22 10:49:27.313 : sysmgr[96]: %OS-SYSMGR-7-DEBUG : sysmgr_admin_plane_check:SYSMGR_PLANE_ADMIN Notification sent.  
    RP/0/RSP0/CPU0:Oct 22 10:49:32.838 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_DISCOVERY : Node State Discovery complete
    RP/0/RSP0/CPU0:Oct 22 10:49:32.854 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:PRESENT
    RP/0/RSP0/CPU0:Oct 22 10:49:32.905 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/FT0/SP FAN TRAY state:PRESENT
    RP/0/RSP0/CPU0:Oct 22 10:49:32.957 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/0/CPU0 inserted 
    RP/0/RSP0/CPU0:Oct 22 10:49:35.224 : syslog_dev[94]: hsbi_fpd_agent[240]: FPD ltrace_file_name => fpd-agent/hsbi_fpd_agent
    RP/0/RSP0/CPU0:Oct 22 10:49:37.310 : alphadisplay[115]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : Alpha display on node 0/RSP0/CPU0 changed to IOXR in state default 
    RP/0/RSP0/CPU0:Oct 22 10:49:48.759 : syslog_dev[94]: netio[327]: > WARNING (BM) [/ws/akgoswam-bgl/hellhound/nto6.4-XR/cisco/lib/3rdparty/netcomm/NetCommSw/Peripherals/BM/bm.h:352 BmBpidGet]: No Ipc - can't validate bpid.^M
    RP/0/RSP0/CPU0:Oct 22 10:50:02.721 : ipodwdm[275]: %L2-G709-6-INFO : /harddisk:/ipodwdm_log  Already present
    RP/0/RSP0/CPU0:Oct 22 10:50:03.698 : shelfmgr[381]: %PLATFORM-SHELFMGR_HAL-6-BOOT_REQ_RECEIVED : Boot Request from 0/0/CPU0, RomMon Version: 2.1
    RP/0/RSP0/CPU0:Oct 22 10:50:04.481 : shelfmgr[381]: %PLATFORM-MBIMGR-7-IMAGE_VALIDATED : Remote location 0/0/CPU0: : MBI tftp:/disk0/asr9k-os-mbi-4.3.2/lc/mbiasr9k-lc.vm validated
    RP/0/RSP0/CPU0:Oct 22 10:50:04.499 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:MBI-BOOTING
    RP/0/RSP0/CPU0:Oct 22 10:50:07.632 : alphadisplay[115]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : Alpha display on node 0/RSP0/CPU0 changed to ACTV in state default 
    RP/0/RSP0/CPU0:Oct 22 10:50:14.758 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_CLEARED : Clear alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED 
    RP/0/RSP0/CPU0:Oct 22 10:50:14.764 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_GREEN_FAILED 
    RP/0/RSP0/CPU0:Oct 22 10:50:29.223 : placed[346]: LR-PLANE-READY DECLARATION
    RP/0/RSP0/CPU0:Oct 22 10:50:31.360 : envmon[204]: %PLATFORM-ENVMON-4-FANTRAY_RPM_CLEAR : Fan tray RPM warning cleared on slot 0/FT0/SP
    RP/0/RSP0/CPU0:Oct 22 10:50:33.247 : ifmgr[242]: %PKT_INFRA-LINK-5-CHANGED : Interface MgmtEth0/RSP0/CPU0/1, changed state to Administratively Down
    RP/0/RSP0/CPU0:Oct 22 10:50:33.251 : ifmgr[242]: %PKT_INFRA-LINK-3-UPDOWN : Interface MgmtEth0/RSP0/CPU0/0, changed state to Down
    RP/0/RSP0/CPU0:Oct 22 10:50:33.251 : ifmgr[242]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface MgmtEth0/RSP0/CPU0/0, changed state to Down
    RP/0/RSP0/CPU0:Oct 22 10:50:33.257 : cfgmgr-rp[158]: %MGBL-CONFIG-6-OIR_RESTORE : Configuration for node '0/RSP0/0' has been restored.
    RP/0/RSP0/CPU0:Oct 22 10:50:35.006 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/PM1/SP A9K-750W-AC state:PRESENT
    RP/0/RSP0/CPU0:Oct 22 10:50:35.012 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/PM0/SP A9K-750W-AC state:PRESENT
    RP/0/RSP0/CPU0:Oct 22 10:50:35.588 : ifmgr[242]: %PKT_INFRA-LINK-3-UPDOWN : Interface MgmtEth0/RSP0/CPU0/0, changed state to Up
    RP/0/RSP0/CPU0:Oct 22 10:50:35.589 : ifmgr[242]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface MgmtEth0/RSP0/CPU0/0, changed state to Up
    RP/0/RSP0/CPU0:Oct 22 10:51:15.756 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED 
    RP/0/RSP0/CPU0:Oct 22 10:51:15.756 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_CLEARED : Clear alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_GREEN_FAILED 
    RP/0/RSP0/CPU0:Oct 22 10:51:23.316 : dsc[181]: %PLATFORM-DSC_CTRL-6-RACK_STATE :  Rack 1 is now Down 
    RP/0/RSP0/CPU0:Oct 22 10:51:23.321 : gsp[239]: gsp_rack_down_handler: for node:0x1
    RP/0/RSP0/CPU0:Oct 22 10:51:25.396 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:MBI-RUNNING
    LC/0/0/CPU0:10: init[65540]: %OS-INIT-7-MBI_STARTED : total time 5.152 seconds
    LC/0/0/CPU0:Oct 22 10:51:57.119 : sysmgr[91]: %OS-SYSMGR-5-NOTICE : Card is COLD started 
    LC/0/0/CPU0:Oct 22 10:51:57.524 : init[65540]: %OS-INIT-7-INSTALL_READY : total time 38.219 seconds
    LC/0/0/CPU0:Oct 22 10:51:58.119 : sysmgr[341]: %OS-SYSMGR-6-INFO : Backup system manager is ready 
    RP/0/RSP0/CPU0:Oct 22 10:52:11.473 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 UNKNOWN state:UNPOWERED
    RP/0/RSP0/CPU0:Oct 22 10:52:11.896 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:POWER UP
    LC/0/0/CPU0:Oct 22 10:52:12.716 : lda_server[65]: %L2-SPA-5-STATE_CHANGE : SPA in bay 0 type A9K-MPA-20X1GE Initing  
    RP/0/RSP0/CPU0:Oct 22 10:52:13.786 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:INITIALIZED
    LC/0/0/CPU0:Oct 22 10:52:25.265 : prm_server_ty[295]: %PLATFORM-QOSHAL-6-QOS_MODE_CHANGE : Line-card QoS mode set to child-shaping-enabled.
    LC/0/0/CPU0:Oct 22 10:52:25.273 : prm_server_ty[295]: %PLATFORM-QOSHAL-6-QOS_MODE_CHANGE : Line-card QoS mode set to lowburst-disabled.
    LC/0/0/CPU0:Oct 22 10:52:25.402 : lda_server[65]: %PLATFORM-UPGRADE_FPD-4-DOWN_REV : fpga3 instance 0 is down-rev (V0.07), upgrade to (V0.08). Use the "upgrade hw-module fpd" CLI in admin mode.
    LC/0/0/CPU0:Oct 22 10:52:25.632 : sysmgr[91]: %OS-SYSMGR-7-DEBUG : sysmgr_admin_plane_check:SYSMGR_PLANE_ADMIN Notification sent.  
    LC/0/0/CPU0:Oct 22 10:52:27.651 : syslog_dev[89]: hsbi_fpd_agent[198]: FPD ltrace_file_name => fpd-agent/hsbi_fpd_agent
    RP/0/RSP0/CPU0:Oct 22 10:52:37.663 : exec[65727]: %MGBL-exec-3-LOGIN_AUTHEN : Login Authentication failed. Exiting...
    RP/0/RSP0/CPU0:Oct 22 10:52:43.079 : exec[65727]: %SECURITY-login-6-AUTHEN_SUCCESS : Successfully authenticated user 'shopik' from 'console' on 'con0_RSP0_CPU0'
    RP/0/RSP0/CPU0:Oct 22 10:52:46.558 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:OK
    RP/0/RSP0/CPU0:Oct 22 10:52:46.578 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: OK
    RP/0/RSP0/CPU0:Oct 22 10:52:46.583 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/0/0 inserted 
    LC/0/0/CPU0:Oct 22 10:52:58.858 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/3, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:58.863 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/2, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:58.863 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/1, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:58.863 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/0, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/19, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/18, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/17, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/16, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/15, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/14, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/13, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/12, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/11, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/10, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/9, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/8, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/7, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/6, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/5, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/4, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/3, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/2, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/1, changed state to Administratively Down
    LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/0, changed state to Administratively Down
    RP/0/RSP0/CPU0:Oct 22 10:53:00.041 : upgrade_fpd_cli[65763]: %PLATFORM-UPGRADE_FPD-6-STATUS : FPD upgrade started.
    LC/0/0/CPU0:Oct 22 10:53:01.800 : lda_server[65]: %PLATFORM-SCC-2-BAD_ID_HW : Failed Identification Test in 0/130/0 [5/0] The module in 0/130/0 in this router may not be a genuineCisco product.  Cisco warranties and support programs onlyapply to genuine Cisco products.  If Cisco determines thatyour insertion of non-Cisco SPA cards or other modules into aCisco product is the cause of a support issue, Cisco maydeny support under your warranty or under a Cisco supportprogram such as SmartNet.  
    RP/0/RSP0/CPU0:Oct 22 10:53:09.746 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:IOS XR RUN
    RP/0/RSP0/CPU0:Oct 22 10:53:09.755 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/CPU0, state: IOS XR RUN
    LC/0/0/CPU0:Oct 22 10:53:31.822 : lda_server[65]: %PLATFORM-LDA-4-MPA_OIR_QUICK_BACK_TO_BACK_ERROR : OIR operation was performed on MPA in bay:0 while the system is initializing. Recommend waiting for two minutes after EP initialized.
    LC/0/0/CPU0:Oct 22 10:53:31.988 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/19, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.988 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/19, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/18, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/18, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/17, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/17, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/16, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/16, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/15, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/15, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/14, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/14, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/13, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/13, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/12, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/11, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/12, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/11, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/10, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/10, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/9, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/9, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/8, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/8, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/7, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/7, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/6, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/5, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/5, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/4, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/4, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/6, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/3, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/3, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/2, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/2, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/1, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/1, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/0, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/0, changed state to Down
    LC/0/0/CPU0:Oct 22 10:53:32.120 : envmon_lc[160]: %PLATFORM-ENVMON-4-OPERATION_WARN : Unable to get plug sensor data, error code 'Subsystem(2890)' detected the 'fatal' condition 'Code(0)' 
    RP/0/RSP0/CPU0:Oct 22 10:53:32.860 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:ADMIN DOWN
    LC/0/0/CPU0:Oct 22 10:53:32.862 : lda_server[65]: %PLATFORM-LDA-3-MPA_BAY_SW_ERROR : Unable to initialize MPA in bay: 0, Module has been shutdown due to identify test failure (0x00000000 - No error)  : pkg/bin/lda_server : (PID=40990) :  -Traceback= 4ed5159c 4bf1eed0 4bf1efdc 4d02c28c 4d02a1f4 4ba73a44 4ba71554 4d029ddc 4bada400
    RP/0/RSP0/CPU0:Oct 22 10:53:33.860 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: UNPOWERED
    RP/0/RSP0/CPU0:asr9001#
    RP/0/RSP0/CPU0:asr9001#
    RP/0/RSP0/CPU0:asr9001#
    RP/0/RSP0/CPU0:asr9001#
    RP/0/RSP0/CPU0:asr9001#show inventory
    Tue Oct 22 11:01:32.251 UTC
    NAME: "module 0/RSP0/CPU0", DESCR: "ASR 9001, Route Switch Processor with 8GB memory"
    PID: ASR9001-RP, VID: V01 , SN: FOC1728XXXX
    NAME: "module 0/0/CPU0", DESCR: "ASR 9001, Modular Line Card"
    PID: ASR9001-LC, VID: V01 , SN: FOC1728XXXX
    NAME: "module 0/0/0", DESCR: "ASR 9000 20-port 1GE Modular Port Adapter"
    PID: A9K-MPA-20X1GE, VID: V00, SN: FOC1522XXXX
    NAME: "module 0/0/2", DESCR: "ASR 9000 Virtual Module"
    PID: A9K-MODULEv, VID: N/A, SN: N/A

    Bryan,
    We checked the "show hw-module fpd location all" and there is no "yes" in the last column.
    http://pastebin.com/W1wuqYks
    RP/0/RSP0/CPU0:asr9001#sh hw-module fpd location all
    Thu Oct 24 13:40:19.487 UTC
    ===================================== ==========================================
                                          Existing Field Programmable Devices
                                          ==========================================
                                            HW                       Current SW Upg/
    Location     Card Type                Version Type Subtype Inst   Version   Dng?
    ============ ======================== ======= ==== ======= ==== =========== ====
    0/RSP0/CPU0  ASR9001-RP                 1.0   lc   fpga2   0       1.14     No
                                                  lc   cbc     0      22.114    No
                                                  lc   rommon  0       2.01     No
    0/FT0/SP     ASR-9001-FAN               1.0   ft   cbc     7      24.114    No
    0/0/CPU0     ASR9001-LC                 1.0   lc   cbc     0      23.114    No
                                                  lc   fpga2   0       1.18     No
                                                  lc   fpga4   0       2.07     No
                                                  lc   rommon  0       2.01     No

  • Slow performance LR 1.3.1 (Library Module)

    LR 1.2 is running OK on my iMac. A while ago I tried LR 1.3. The upgrade really slowed down performance. Mostly a lag in the sliders and navigation tools in both Library and Develop modules that made it unworkable to me. I changed back to LR 1.2.
    Since I want to import Canon G9 RAW files into LR, I upgraded to LR 1.3.1 recently. Performance of sliders and the navigation tool in the Develop module seems the same as in LR 1.2 (or maybe even a little better). Which means it is OK (workable). It still shows the blur when navigating a 100% zoomed image though. But the navigation tool in the Library module still has the same slow performance as it had in LR 1.3. Unworkable!!! I tried everything: optimizing, new catalog, rendering previews, etc.
    I need the Library module to work smoothly (as in LR 1.2) in order to compare images at 100% zoom. I am afraid I have to go back to LR 1.2 again and find another solution for my Canon G9 RAW files. Most inconvenient. I am very disappointed. Especially, since Adobe showed they CAN get it right with the Develop module in version LR 1.3.1...
    Oh yeah, my system specs:
    iMac 2.16 GHz Intel Core 2 Duo
    3GB 667 Mhz DDR2 SDRAM (2GB + 1GB)
    232,89 GB Harddrive, 113 GB available
    ATI Radeon X1600 128MB
    Mac OS 10.4.11
    Please Adobe, make the Library module run as smoothly as the Develop module in version 1.3.2...

    The preview folder is 2,11 GB big. The .lrcat is 47 MB big.
    I opened a new test catalog. I imported 326 images. After the import I rendered 1:1 previews. It took a long time. Real memory used was between 700-1000MB. Virtual memory used was between 1000-1400MB. When it was done rendering it still keep on using 700MB real memory and 1000MB virtual memory. I had to close LR and restart. Real memory after restart was 75MB real memory and 375 virtual memory.
    But it didn't matter. The lag in the navigation tool of the Library module was still there.
    I noticed that when clicking in the navigation window there was less delay as when I slide the white square in the window (in Library module). In the develop module this seems the other way around. Sliding showed less delay than clicking.
    What's going on here?
    I also have a MacBook. Performance seems much faster than on my iMac overall. After creating a new catalog and rendering 1:1 previews, the lag in the navigation window seems less than before. But it was still there...

  • PERFORM in Z Function Module

    Greetings!
    I'm creating a Z function module and within it I will looping through an internal table and would like to add a PERFORM routine where I pass a couple of data variables from my itab and then within the PERFORM routine take that data with some other coding/validating and fill an internal table from the main function module however when I build the PERFORM routine in the fm include it doesn't recognize my internal table.
    my code looks a little like this in the fm..
    loop at itab...
    perform validate_data using var1 var2 va3.
    endloop.
    Do I need to pass the itab with a CHANGING parameter of the PERFORM call?

    Hi
    U can became the parameters of fm interface as global data:
    In trx SM37 go to EDIT->INTERFACE->GLOBALIZE PARAMETER
    else
    - or u need to use an USING parameter in your FORM in order to transfer the data from z fm to form;
    - or u need to use a workarea defined as global data in order to transfer the data from z fm to form.
    Max

  • Delivered Function Module to perform UOM conversions??

    Hi Gurus,
    Is there any SAP delivered function module that I can use to perform any UOM conversions at all. For eg, Gallons to liters etc.
    Appreciate your inputs.
    Thanks,
    Reddy

    Dinesh and Anil,
    Thanks for your inputs. I ended up using UNIT_CONVERSION_SIMPLE. It met my requirement.
    Regards,
    Reddy

  • Performance testing of a functional module

    Hi
    Based on the input and corresponding expected output parameters we will test a particular functional module
    Here how to check the performance of that functional module
    Output is correct,but is there any standard specified timelimit  for the runtime , Load or it depends upon the complexity of that funct mod.
    Please provide some inputs regarding this
    Regards
    Amuthan M

    http://www.javaperformancetuning.com/tips/webservice.shtml

  • NI 9853 C Series CAN module Synchronization

    OK, this is goning to be long to explain...First  of all Im using a CompactRIO 9004 system with 9104 Chassis and the NI9853 high speed CAN module. Ive been able to perform a loopback test between CAN0 and CAN1 ports of the 9853 module (with standard and extendend IDs). I also have a fully functional CAN network consisting of Microchip hardware, specifically two dsPIC30F4011's with the MCP2551 CAN transceiver and one 18f4553 with an MCP2515 CAN controller and a MCP2515 CAN transceiver, this network also works well within itself (I send messages through the CAN network and the PICs are able to control some servos). Im trying to interface the cRIO and NI9853 with this CAN network, but neither the NI9853 module will successfully transmit or recieve from any of the PICs. Funny thing is that I connect everything to the same physical bus (twisted pair cable with 120ohm terminators) and Im still able to transmit from CAN0 to CAN1 of the NI9853, and also the PICs are able to transmit/recieve within themselves. I think it all has to do with sync issues, the thing is; Ive gone as far as programatically writing the BTR0 and BTR1 registers of the NI9853 module (which has a Phillips SJA1000 CAN controller) to match those used by the Microchip hardware, and still no communication. Im trying to transmit at 1Mbit/s, using 20Mhz clocks on my external CAN network, for this Im using 10 time quantas to represent the nominal bit time, from what I understand from both CAN controller datasheets (MCP2515 and SJA1000) the definition of the segments and the sampling point for the bits is what is of importance (as well as the scaler value), Ive matched both to identical values by manipulating the BTR0 and BTR1 registers of the SJA1000 (NI's 9853) CAN controller. From what I know the FPGA on the cRIO runs at 40Mhz, with this a 20MHz clock for the NI9853 is possible. Here is the thing, when selecting the properties for the 9853 module and selecting a preset from the "Baud Rate" drop-list for any CAN port, if the "Advanced" button is pressed the "Specifiy Baud Rate as Bit Timing Registers" value changes accordingly to the preset value specified in the drop-list, that is, if I select 1000 kbits/s, BTR1 gets the value 0x14 and BTR0 gets 0x00; if I select 500 kbits/s BTR1 gets 0x1C and BTR0 gets 0x00. Also on the same properties window for the 9853, there is a "Module" tab, with a drop-list labeled "Module Clock" the values I can select here are 20Mhz and 10MHz. Turns out that the value of the baud rate as specified in the advanced tab by the bit registers is not affected if I select 10Mhz or 20Mhz; also in order to have a 1000 kbit/s speed with a 0x14 value on BTR1 a 16MHz clock speed should be used (according to the definitions of the SJA1000's datasheet for BTR1 and BTR0). The following images show what Im talking about:      
    Also all documentation I could find regarding nonstandard baud rates on the NI site apparently refers to the CAN controller NI hardware series 1 used (Intels 82527, which actually runs at 16Mhz) from what Ive been able to research this chip has identical Bit timing registers to the ones of the SJA1000 controller, proof of this is the document labeled "How to Configure CAN Ports for Custom Baud Rates" (http://zone.ni.com/devzone/cda/tut/p/id/4304), which shows a map of the registers of Intels chip, and is identical to the one found on the SJA1000s datasheet. On other document titled "How Can I Set Nonstandard Baud Rates in NI-CAN?" (http://digital.ni.com/public.nsf/allkb/CBA1FC627FFA0F8F862564DC0071B3A7?OpenDocument), the same information appears regarding the way the NI-CAN driver handles baud rates (again using Intels chip, which by the way is incorrectly specified to be running at 8Mhz). Using 20Mhz and the BTR1+BTR0 combination 0x1400, the SJA1000 yields 1.25Mbits/s, not even a possible speed on the CAN bus. Bottom line is, I think I cant interface my CAN network with the NI 9853, because of this strange issue. Im just wondering if anybody has any idea how to do this, or at least what is the speed the 9853 module runs on, with this I think I could at least try and find a value to match the 1Mbit on my network. Finally Ive attached the project Im running on the fpga target (Ive set the Module Clock on 20Mhz, disabled auto-start for both CAN ports and specified to run the Baud rate from the time registers using BTR1: 0x34 and BTR0: 0x00 values for the timing registers).   Any help will be appreciated, thanks in advance...
    Attachments:
    CAN Test.zip ‏194 KB

    One final thing, this is the only thing regarding external sync that Ive found so far....its the "NI CAN Product Compatibility and Feature Table" (http://zone.ni.com/devzone/cda/tut/p/id/5859#_ftn1) take a look at the footnote it says a digital module is needed, would it be a digital 9401 module? Ive also got one of those.

  • Crystal Reports performance is too slow

    Dear SDNers,
    I have designed a crystal report which is fetching data from a Z developed function module. From crystal report side, used filters.But while executing report, it is calling the function module multiple times.
    due to this performance is very bad. Why report is calling mutiple times of the function module. Do need to modify from crystal report side or from function module side. Please clarify.
    Regards,
    Venkat

    A similar issue was seen a year ago It was regarding a function module call being executed multiple times from  CR4Ent tool. It involved the usage of sub reports inside that report and the issue was generic for any function module used for testing.
    At that time, the issue was resolved by upgrading to the latest available patch of CR4Ent and also by applying the latest patch at SAP R3 end.
    If you are able to post the exact support package and patch level of CR4Ent and also for the SAP R3 system, then someone can tell whether its the latest or not.
    -Prathamesh

  • Input Help in Dialog Modules

    HI,
    I have to provide F4 help for many fields that are present in tabstrip control(with 5 tabs). I had set the option "Possible entries" in the layout. In the flow logic, I created a module for POV. How would I get the screen element name (i.e., the field) from which F4 was pressed? While debugging, I dont get the field name in SYST and SCREEN table. For each tab, I am thinking of creating of only one module in POV so that I can avoid hardcoding the field name.
    You can use DEMO_DYNPRO_F4_HELP_MODULE report in IDES if required.

    Try this out it worked for me,
    Will post in in 3 halves.
    1.     First half
    MODULE help_zterm INPUT.  "In POV
      PERFORM help_zterm.
    ENDMODULE.                 " HELP_ZTERM  INPUT
    FORM help_zterm .
      DATA: BEGIN OF svbap OCCURS 12,
              tabix LIKE sy-tabix,
            END OF svbap.
      DATA:   BEGIN OF xvbap OCCURS 125.
              INCLUDE STRUCTURE vbapvb.
      DATA:   END OF xvbap.
      DATA: da_display LIKE ddrefstruc-bool.
      DATA: da_value LIKE vbkd-zterm.
      DATA: da_dynpro_program  LIKE sy-repid.
      DATA: da_dynpro_number   LIKE sy-dynnr.
      DATA: BEGIN OF dynpfield_zterm OCCURS 1.
              INCLUDE STRUCTURE dynpread.
      DATA: END OF dynpfield_zterm.
      da_dynpro_program  = sy-repid.
      da_dynpro_number   = sy-dynnr.
      CLEAR dynpfield_zterm.
      REFRESH dynpfield_zterm.
      MOVE 'ZDEALHD-ZTERM' TO dynpfield_zterm-fieldname.  u201DZDEALHD-ZTERM u2013 screen field name
      APPEND dynpfield_zterm.
      CALL FUNCTION 'DYNP_VALUES_READ'     
        EXPORTING
          dyname     = da_dynpro_program
          dynumb     = da_dynpro_number
        TABLES
          dynpfields = dynpfield_zterm
        EXCEPTIONS
          OTHERS     = 11.
      IF sy-subrc <> 0.
        EXIT.
      ELSE.
        READ TABLE dynpfield_zterm WITH KEY fieldname =
                                    dynpfield_zterm-fieldname.
      ENDIF.
      LOOP AT SCREEN.
        CHECK screen-name = 'ZDEALHD-ZTERM' AND
              screen-input = '0'.
       DA_DISPLAY = CHARX.
      ENDLOOP.
      IF dynpfield_zterm-fieldinp EQ space.
       DA_DISPLAY = CHARX.
      ENDIF.
    Call SD Sales BAdI
      DATA:  da_line    LIKE sy-tabix,
             da_core_inactive TYPE xfeld,
             wa_svbap LIKE svbap,
             wa_xvbap LIKE xvbap.
    Determining Cursor
      CLEAR wa_xvbap.
      GET CURSOR LINE da_line.
      IF da_line GE 1.
        READ TABLE svbap INTO wa_svbap INDEX da_line.
        IF sy-subrc = 0.
          READ TABLE xvbap INTO wa_xvbap INDEX wa_svbap-tabix.
        ENDIF.
      ENDIF.
    Will send the second one and third one  in few seconds.
    Edited by: Abhijit Borkar on Jan 7, 2010 9:11 AM

  • Help!  Poor network (LAN) performance with T2000, Solaris 10, GB

    Hi-
    I'm having a problem that I'm hoping someone can help me with.
    We've recently purchased a few of the T2000 boxes, with the ipge (GB) cards in them.
    The problem we're having is that we can't seem to get more than 500 mbit/s performance out of them, at least the way we're measuring them.
    So, I have 2 questions... (a) how can we validate that we are in fact getting GB performance for file downloads, etc. and (b) is there something that we have to do in order to accomplish this if our readings are correct?
    Background:
    What we've done so far is as follows:
    Validate that the connection is indeed GB, full duplex.
    root@conn1 # dladm show-dev
    ipge0 link: unknown speed: 1000 Mbps duplex: full
    ipge1 link: unknown speed: 0 Mbps duplex: unknown
    ipge2 link: unknown speed: 0 Mbps duplex: unknown
    ipge3 link: unknown speed: 0 Mbps duplex: unknown
    root@conn1 #
    We've run a crossover cable between 2 of them to eliminate any "switch" issues from the equation.
    We then ran iperf, as a server on one of them, as a client on the other.
    Server Output:
    root@conn2 # iperf -s
    Server listening on TCP port 5001
    TCP window size: 48.0 KByte (default)
    [  4] local 192.168.1.215 port 5001 connected with 192.168.1.71 port 32795
    [ ID] Interval Transfer Bandwidth
    [  4] 0.0-10.0 sec 598 MBytes 502 Mbits/sec
    Client output:
    root@conn1 # iperf -c 192.168.1.215 -i 1
    Client connecting to 192.168.1.215, TCP port 5001
    TCP window size: 48.0 KByte (default)
    [  3] local 192.168.1.71 port 32795 connected with 192.168.1.215 port 5001
    [ ID] Interval Transfer Bandwidth
    [  3] 0.0- 1.0 sec 57.8 MBytes 485 Mbits/sec
    [  3] 1.0- 2.0 sec 59.9 MBytes 502 Mbits/sec
    [  3] 2.0- 3.0 sec 60.1 MBytes 504 Mbits/sec
    [  3] 3.0- 4.0 sec 59.7 MBytes 501 Mbits/sec
    [  3] 4.0- 5.0 sec 59.9 MBytes 502 Mbits/sec
    [  3] 5.0- 6.0 sec 60.7 MBytes 509 Mbits/sec
    [  3] 6.0- 7.0 sec 60.2 MBytes 505 Mbits/sec
    [  3] 7.0- 8.0 sec 59.9 MBytes 503 Mbits/sec
    [  3] 8.0- 9.0 sec 59.9 MBytes 503 Mbits/sec
    [  3] 9.0-10.0 sec 59.5 MBytes 499 Mbits/sec
    [  3] 0.0-10.0 sec 598 MBytes 501 Mbits/sec
    root@conn1 #
    Thoughts? Help!?
    ...jeff

    Hi,
    We are having issues with our T2000s as well. Same setup. t2000s back to back with a crossover connection. Best we are getting with a single iperf test is..
    # iperf -c 192.168.1.2 -i 1
    Client connecting to 192.168.1.2, TCP port 5001
    TCP window size: 2.00 MByte (default)
    [  3] local 192.168.1.1 port 52643 connected with 192.168.1.2 port 5001
    [ ID] Interval Transfer Bandwidth
    [  3] 0.0- 1.0 sec 27.7 MBytes 232 Mbits/sec
    [  3] 1.0- 2.0 sec 28.8 MBytes 242 Mbits/sec
    [  3] 2.0- 3.0 sec 30.3 MBytes 254 Mbits/sec
    [  3] 3.0- 4.0 sec 26.5 MBytes 222 Mbits/sec
    [  3] 4.0- 5.0 sec 24.3 MBytes 204 Mbits/sec
    [  3] 5.0- 6.0 sec 28.9 MBytes 242 Mbits/sec
    [  3] 6.0- 7.0 sec 28.7 MBytes 241 Mbits/sec
    [  3] 7.0- 8.0 sec 30.6 MBytes 257 Mbits/sec
    [  3] 8.0- 9.0 sec 30.8 MBytes 259 Mbits/sec
    [  3] 9.0-10.0 sec 26.8 MBytes 225 Mbits/sec
    [  3] 0.0-10.0 sec 283 MBytes 237 Mbits/sec
    [  4] local 192.168.1.2 port 5001 connected with 192.168.1.1 port 52643
    [ ID] Interval Transfer Bandwidth
    [  4] 0.0-10.0 sec 283 MBytes 238 Mbits/sec
    Did you ever get an answer to your questions below? Would you be willing to share what you found?
    What settings do you have to get the 500 Mbits/sec? Our servers are fairly well loaded so we think it's just fighting for CPU with everything else. If you run many streams your performance improves a great deal. We've gotten ~800Mbits/sec running 5 or more iperf runs at the same time.
    If you run "intrstat" while you do the single or many iperf runs what does your CPU peg out at? We get about %11 cpu useage from a single iperf run and %35 from 2 CPUs when we do many iperf runs at the same time.
    Thanks,
    -Matt

  • Using subroutines in Function Module

    Hi , experts ,
    I want to know how to use performs in function module,
    If created subroutine must be used in all FM in  Func.Group ?
    if you have  articles about this or any information , I will be glad .
    Please help.
    Regards,
    Tatiana.

    If i am not mistaken you want to use forms in function module.
    To enable forms in function module you have to follow these steps:
    Create a Z include in your function module.
    INCLUDE ZTEST_INCLUDE.
    Inside this include you need to write your form routine which will be accessable from your function module.
    Now you can use perform statement in your funtion module.
    Thnaks & Regards,
    Lalit Mohan Gupta

  • HR Function Modules and HR Macros

    Hi ,
    I have to create one interface program for SAP HR.
    For that I am trying to use Function module HR_READ_INFOTYPE , but I think we should not use LDB PNP if we use this Function module.
    Further I tried to use RP_PROVIDE_FROM_LAST macro also for this LDB is mandatory.
    I need to know which one i can use the Function module or Macros in regards to performance.
    Which one will take more time for execution Function Module or the Macro? If Function Module why ? If Macro why?
    Please help me out becoz am new to SAP HR coding.
    Thanks in Advance

    You can use th get runtime statements in code to find out how much time a part of the source takes to run.
    HR macros are stored in table TRMAC, so you can find out what the source is behind these.
    Kind regards, Rob Dielemans

  • Checkbox in Module Pool Programming

    Hi,
    I got a situation. I need to handle the checkboxes, which are the internal table fields.
    I need to check them, when I click the push button.
    Using the event sy-ucomm, I tried to do. But, normally in a screen, we use to check the checkbox, whereas here I need to check them with the push button.
    Kindly, guys help me out.
    Thanks.

    Hi,
    In PAI of the screen,
    module USER_COMMAND_9001 input.
    when 'SALL'.
        PERFORM USER_COMMAND_9002.
    ... Display the ouput
    endmodule.                 " USER_COMMAND_9001  INPUT.
    form USER_COMMAND_9002.
    LOOP AT I_OUTPUT INTO W_OUTPUT.
           W_OUTPUT-X = 'X'.
           MODIFY I_OUTPUT FROM W_OUTPUT.
    ENDLOOP.
    endform.                    " USER_COMMAND_9002

  • Perform on commit

    Hi,
    can you show me an example of "perform on commit" with variables.

    Hi,
    PERFORM ON COMMIT routines are not executed in the dialog module.
    You must ensure that any subroutines called using ON COMMIT can be delayed until the next COMMIT WORK in the calling program. Remember that the global data of the dialog module is destroyed along with the internal session when control returns to the calling program. Consequently, subroutines called using PERFORM ON COMMIT must not use this global data.
    The statement PERFORM ON COMMIT calls a subroutine in the dialog work process. However, it is not executed until the system reaches the next COMMIT WORK statement. Here, as well, the ABAP statement COMMIT WORK defines the end of the SAP LUW, since all statements in a subroutine called with PERFORM ON COMMIT that make database changes are executed in the
    database LUW of the corresponding dialog step.
    The advantage of this bundling technique against CALL FUNCTION... IN UPDATE TASK is better performance, since the update data does not have to be written into an extra table. The disadvantage, however, is that you cannot pass parameters in a PERFORM... ON COMMIT statement. Data is passed using global variables and ABAP memory. There is a considerable danger of data inconsistency when you use this method to pass data.
    You can also put the CALL FUNCTION IN UPDATE TASK into a subroutine and call the subroutine with:
    <b>PERFORM SUBROUT ON COMMIT.</b>
    If you choose this method, the subroutine is executed at the commit. Thus the request to run the function in the update task is also logged during commit processing. As a result, the parameter values logged with the request are those current at the time of the commit.
    Ex.
    a = 1.
    PERFORM F ON COMMIT.
    a = 2.
    PERFORM F ON COMMIT.
    a = 3.
    COMMIT WORK.
    FORM f.
    CALL FUNCTION 'UPD_FM' IN UPDATE TASK EXPORTING PAR = A.
    ENDFORM.
    In this example, the function module UPD_FM is carried out with the value 3 in PAR. The update task executes the function module only once, despite the two PERFORM ON COMMIT statements. This is because a given function module, logged with the same parameter values, can never be executed more than once in the update task. The subroutine itself, containing the function module call, may not have parameters.
    Regards,
    Bhaskar

  • Passing itab in a perform statement

    Hi Experts,
    In a Fucn Module, I need to write a perform statement and the corresponding FORM lies in an include. I need to pass an internal table(itab) & workarea(wa_itab) in perform as below :
    Declaration of itab:
    types: BEGIN OF ty_out1,
             f1(16) TYPE c,
             f2 TYPE wrbtr,
           END OF ty_out1.
    data : itab type standard table of ty_out1,
              wa_itab type ty_out1,
    PERFORM <form name> tables itab
      USING wa_itab
      test1.
    Dbl click on above perform takes us to an include prog and the form is declared as below -
    what should be the syntax of the FORM in INCLUDE statement.
    Note: I should not use the top include of the main prog for any declarations.
    form search_slash tables ptab2 like itab
                   using wa2_itab like wa_itab
                   test2 .
    Now what should be the syntax of the form above? Is the above right?
    Please suggest
    Thanks
    Dan

    Hi,
    If you want to pass only the internal table with header line,
    then use tables ptab2 structure wa2_itab
    For internal table with header line use:
    tables ptab2 like wa2_itab
    or
    tables ptab2[ ] like wa2_itab.
    Hope this helps.
    Reward if helpful.
    Regards,
    Sipra

Maybe you are looking for

  • Account access and permissions issue

    When I try to synch my iPod, I am informed that I will lose my purchased music because my computer is not authorized. When I attempt to authorize the account in iTunes, I get an error stating that the required file is not found or permissions error.

  • 10.9.2 sleep issue won't wake up.

    When 10.9.2 on my iMac 27 mid 2011 goes to sleep naturally overnite it won't wake. I have to do a reboot with the back button. Is anyone else having this issue?

  • Batch input to transaction VG01

    hi abapers i want to do a batch input to transaction VG01, the problem is that when i have  more than the rows on screen (and this is according to user screen resulotion)  i need  to use page down button how can i avoid this. thanks Amit

  • Audio volume on aluminum 13" vs black 13"

    Is there anyone out there who used to own a black MacBook and now owns an Aluminum 13" MacBook? I'm wondering about the audio volume on the new model. I have a first-gen black MacBook, and the sound doesn't get very loud at all, even at max volume. D

  • TS1538 iPad not turning on. Vertical colored lines followed by a black screen. Help!

    My iPad is a little less than a year old. While playing a game on my iPad, multicolored vertical lines appeared across left side of iPad followed by a black screen. After a few seconds the screen flicked back on....then a few more vertical colored li