c2900-universalk9-mz.SSA.151-2.18.T not recognizing hardware

Version 1
    This document was generated from CDN thread

    Created by: Andrew Benhase on 20-11-2010 01:34:25 AM
    Loaded up new image, reloaded, saw a bunch of nasty looking console messages during boot. IOS 15.1(2.18)T not recognizing the SRE.
     
     
    VIPER#sh vers
    Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.1(2.18)T ENGINEERING WEEKLY BUILD, synced to V150_1_M3_7
    Copyright (c) 1986-2010 by Cisco Systems, Inc.
    Compiled Mon 20-Sep-10 11:53 by datruong
    ROM: System Bootstrap, Version 15.0(1r)M1, RELEASE SOFTWARE (fc1)
    VIPER uptime is 2 minutes
    System returned to ROM by reload at 20:33:55 UTC Wed Oct 27 2010
    System image file is "flash:c2900-universalk9-mz.SSA.151-2.18.T.bin"
    Last reload type: Normal Reload
    Last reload reason: Reload Command

    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    VIPER#sh hard
    Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.1(2.18)T ENGINEERING WEEKLY BUILD, synced to V150_1_M3_7
    Copyright (c) 1986-2010 by Cisco Systems, Inc.
    Compiled Mon 20-Sep-10 11:53 by datruong
    ROM: System Bootstrap, Version 15.0(1r)M1, RELEASE SOFTWARE (fc1)
    VIPER uptime is 2 minutes
    System returned to ROM by reload at 20:33:55 UTC Wed Oct 27 2010
    System image file is "flash:c2900-universalk9-mz.SSA.151-2.18.T.bin"
    Last reload type: Normal Reload
    Last reload reason: Reload Command

    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    If you require further assistance please contact us by sending email to
    export@cisco.com.
    Cisco CISCO2911/K9 (revision 1.0) with 479232K/45056K bytes of memory.
    Processor board ID FTX1351A1DR
    3 Gigabit Ethernet interfaces
    1 Virtual Private Network (VPN) Module
    DRAM configuration is 64 bits wide with parity enabled.
    255K bytes of non-volatile configuration memory.
    254464K bytes of ATA System CompactFlash 0 (Read/Write)

    License Info:
    License UDI:
    -------------------------------------------------
    Device#   PID                   SN
    -------------------------------------------------
    *0        CISCO2911/K9          FTX1351A1DR

    Technology Package License Information for Module:'c2900'
    ----------------------------------------------------------------
    Technology    Technology-package          Technology-package
                  Current       Type          Next reboot
    -----------------------------------------------------------------
    ipbase        ipbasek9      Permanent     ipbasek9
    security      securityk9    Evaluation    securityk9
    uc            None          None          None
    data          datak9        Evaluation    datak9
    Configuration register is 0x2102
    VIPER#
    VIPER#
    VIPER#
    VIPER#sh diag
    Slot 0:
            C2911 Mother board 3GE, integrated VPN and 4W Port adapter, 3 ports
            Port adapter is analyzed
            Port adapter insertion time 00:03:37 ago
            EEPROM contents at hardware discovery:
            PCB Serial Number        : FOC13481FXV
            Hardware Revision        : 1.0
            Part Number              : 73-11833-03
            Top Assy. Part Number    : 800-30797-01
            Board Revision           : B0
            Deviation Number         : 0
            Fab Version              : 03
            Product (FRU) Number     : CISCO2911/K9
            Version Identifier       : V01
            CLEI Code                : COMGM00ARA
            Processor type           : C1
            Chassis Serial Number    : FTX1351A1DR
            Chassis MAC Address      : c47d.4fca.3680
            MAC Address block size   : 80
            Manufacturing Test Data  : 00 00 00 00 00 00 00 00
            EEPROM format version 4
            EEPROM contents (hex):
              0x00: 04 FF C1 8B 46 4F 43 31 33 34 38 31 46 58 56 40
              0x10: 06 18 41 01 00 82 49 2E 39 03 C0 46 03 20 00 78
              0x20: 4D 01 42 42 30 88 00 00 00 00 02 03 CB 8C 43 49
              0x30: 53 43 4F 32 39 31 31 2F 4B 39 89 56 30 31 20 D9
              0x40: 04 40 C1 CB C2 C6 8A 43 4F 4D 47 4D 30 30 41 52
              0x50: 41 09 C1 C2 8B 46 54 58 31 33 35 31 41 31 44 52
              0x60: C3 06 C4 7D 4F CA 36 80 43 00 50 C4 08 00 00 00
              0x70: 00 00 00 00 00 F3 00 03 40 01 25 FF FF FF FF FF
              0x80: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0x90: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xA0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xB0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xC0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xD0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xE0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xF0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
            Internal Power Supply information
            Top Assy. Part Number    : 341-0235-03
            Deviation Number         : 0
            PCB Serial Number        : AZS135010MH
            RMA Test History         : 00
            RMA Number               : 0-0-0-0
            RMA History              : 00
            Version Identifier       : V01
            Product (FRU) Number     : PWR-2911-AC
            CLEI Code                : 0000000000
            Board Revision           : A0
            EEPROM format version 4
            EEPROM contents (hex):
              0x00: 04 FF 40 05 E5 DF 45 01 55 00 EB 03 88 00 00 00
              0x10: 00 C1 8B 41 5A 53 31 33 35 30 31 30 4D 48 03 00
              0x20: 81 00 00 00 00 04 00 89 56 30 31 20 CB 8B 50 57
              0x30: 52 2D 32 39 31 31 2D 41 43 C6 8A 30 30 30 30 30
              0x40: 30 30 30 30 30 F3 00 59 41 00 BE 42 00 05 F8 00
              0x50: 50 01 F4 17 2B 02 EE 1A 7A 03 E8 1B 65 04 E2 1C
              0x60: 47 05 DC 1C C9 06 D6 1D A3 07 D0 1E 54 08 CA 1E
              0x70: E6 09 C4 1F 5C 0A BE 1F BF 0B B8 20 12 0D AC 20
              0x80: 92 0F A0 20 F0 11 94 21 38 13 88 21 6B 17 70 21
              0x90: AE 1B 58 21 D3 1F 40 21 E0 23 28 21 DE 27 10 22
              0xA0: 56 42 41 30 FF FF FF FF FF FF FF FF FF FF FF FF
              0xB0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xC0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xD0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xE0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xF0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
    Slot 1:
            Unknown (type 0) Port adapter
            Port adapter is disabled
            Port adapter insertion time unknown
            EEPROM contents at hardware discovery:
            Hardware revision 0.0           Board revision UNKNOWN
            Serial number     0             Part number    00-0000-00
            Version Identifier              FRU Part Number
            Test history      0x0           RMA number     00-00-00
            EEPROM format version 0
            EEPROM contents (hex):
              0x00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
              0x10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
              0x20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
              0x30: 00 00 00 00 00 00 00 00 00 00 00 00
    VIPER#

    Subject: RE: New Message from Andrew Benhase in Service Ready Engine Virtualization
    Replied by: Radhika Miriyala on 20-11-2010 01:34:25 AM
    Andrew,

    A few questions.

    1)What exactly do you mean by nasty messages?

    2). What image did you have before and was the SRE working ok before?

    3) What is installed on the SRE?



    Thanks,

    Radhika



    From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
    Sent: Wednesday, October 27, 2010 1:45 PM
    To: cdicuser@developer.cisco.com
    Subject: New Message from Andrew Benhase in Service Ready Engine Virtualization - SRE-V Beta Testing: c2900-universalk9-mz.SSA.151-2.18.T not recognizing hardware



    Andrew Benhase has created a new message in the forum "SRE-V Beta Testing":
    --------------------------------------------------------------
    Loaded up new image, reloaded, saw a bunch of nasty looking console messages during boot. IOS 15.1(2.18)T not recognizing the SRE.


    VIPER#sh vers
    Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.1(2.18)T ENGINEERING WEEKLY BUILD, synced to V150_1_M3_7
    Copyright (c) 1986-2010 by Cisco Systems, Inc.
    Compiled Mon 20-Sep-10 11:53 by datruong
    ROM: System Bootstrap, Version 15.0(1r)M1, RELEASE SOFTWARE (fc1)
    VIPER uptime is 2 minutes
    System returned to ROM by reload at 20:33:55 UTC Wed Oct 27 2010
    System image file is "flash:c2900-universalk9-mz.SSA.151-2.18.T.bin"
    Last reload type: Normal Reload
    Last reload reason: Reload Command

    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    VIPER#sh hard
    Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.1(2.18)T ENGINEERING WEEKLY BUILD, synced to V150_1_M3_7
    Copyright (c) 1986-2010 by Cisco Systems, Inc.
    Compiled Mon 20-Sep-10 11:53 by datruong
    ROM: System Bootstrap, Version 15.0(1r)M1, RELEASE SOFTWARE (fc1)
    VIPER uptime is 2 minutes
    System returned to ROM by reload at 20:33:55 UTC Wed Oct 27 2010
    System image file is "flash:c2900-universalk9-mz.SSA.151-2.18.T.bin"
    Last reload type: Normal Reload
    Last reload reason: Reload Command

    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    If you require further assistance please contact us by sending email to
    export@cisco.com.
    Cisco CISCO2911/K9 (revision 1.0) with 479232K/45056K bytes of memory.
    Processor board ID FTX1351A1DR
    3 Gigabit Ethernet interfaces
    1 Virtual Private Network (VPN) Module
    DRAM configuration is 64 bits wide with parity enabled.
    255K bytes of non-volatile configuration memory.
    254464K bytes of ATA System CompactFlash 0 (Read/Write)

    License Info:
    License UDI:
    -------------------------------------------------
    Device#   PID                   SN
    -------------------------------------------------
    *0        CISCO2911/K9          FTX1351A1DR

    Technology Package License Information for Module:'c2900'
    ----------------------------------------------------------------
    Technology    Technology-package          Technology-package
                  Current       Type          Next reboot
    -----------------------------------------------------------------
    ipbase        ipbasek9      Permanent     ipbasek9
    security      securityk9    Evaluation    securityk9
    uc            None          None          None
    data          datak9        Evaluation    datak9
    Configuration register is 0x2102
    VIPER#
    VIPER#
    VIPER#
    VIPER#sh diag
    Slot 0:
            C2911 Mother board 3GE, integrated VPN and 4W Port adapter, 3 ports
            Port adapter is analyzed
            Port adapter insertion time 00:03:37 ago
            EEPROM contents at hardware discovery:
            PCB Serial Number        : FOC13481FXV
            Hardware Revision        : 1.0
            Part Number              : 73-11833-03
            Top Assy. Part Number    : 800-30797-01
            Board Revision           : B0
            Deviation Number         : 0
            Fab Version              : 03
            Product (FRU) Number     : CISCO2911/K9
            Version Identifier       : V01
            CLEI Code                : COMGM00ARA
            Processor type           : C1
            Chassis Serial Number    : FTX1351A1DR
            Chassis MAC Address      : c47d.4fca.3680
            MAC Address block size   : 80
            Manufacturing Test Data  : 00 00 00 00 00 00 00 00
            EEPROM format version 4
            EEPROM contents (hex):
              0x00: 04 FF C1 8B 46 4F 43 31 33 34 38 31 46 58 56 40
              0x10: 06 18 41 01 00 82 49 2E 39 03 C0 46 03 20 00 78
              0x20: 4D 01 42 42 30 88 00 00 00 00 02 03 CB 8C 43 49
              0x30: 53 43 4F 32 39 31 31 2F 4B 39 89 56 30 31 20 D9
              0x40: 04 40 C1 CB C2 C6 8A 43 4F 4D 47 4D 30 30 41 52
              0x50: 41 09 C1 C2 8B 46 54 58 31 33 35 31 41 31 44 52
              0x60: C3 06 C4 7D 4F CA 36 80 43 00 50 C4 08 00 00 00
              0x70: 00 00 00 00 00 F3 00 03 40 01 25 FF FF FF FF FF
              0x80: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0x90: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xA0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xB0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xC0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xD0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xE0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xF0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
            Internal Power Supply information
            Top Assy. Part Number    : 341-0235-03
            Deviation Number         : 0
            PCB Serial Number        : AZS135010MH
            RMA Test History         : 00
            RMA Number               : 0-0-0-0
            RMA History              : 00
            Version Identifier       : V01
            Product (FRU) Number     : PWR-2911-AC
            CLEI Code                : 0000000000
            Board Revision           : A0
            EEPROM format version 4
            EEPROM contents (hex):
              0x00: 04 FF 40 05 E5 DF 45 01 55 00 EB 03 88 00 00 00
              0x10: 00 C1 8B 41 5A 53 31 33 35 30 31 30 4D 48 03 00
              0x20: 81 00 00 00 00 04 00 89 56 30 31 20 CB 8B 50 57
              0x30: 52 2D 32 39 31 31 2D 41 43 C6 8A 30 30 30 30 30
              0x40: 30 30 30 30 30 F3 00 59 41 00 BE 42 00 05 F8 00
              0x50: 50 01 F4 17 2B 02 EE 1A 7A 03 E8 1B 65 04 E2 1C
              0x60: 47 05 DC 1C C9 06 D6 1D A3 07 D0 1E 54 08 CA 1E
              0x70: E6 09 C4 1F 5C 0A BE 1F BF 0B B8 20 12 0D AC 20
              0x80: 92 0F A0 20 F0 11 94 21 38 13 88 21 6B 17 70 21
              0x90: AE 1B 58 21 D3 1F 40 21 E0 23 28 21 DE 27 10 22
              0xA0: 56 42 41 30 FF FF FF FF FF FF FF FF FF FF FF FF
              0xB0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xC0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xD0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xE0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
              0xF0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
    Slot 1:
            Unknown (type 0) Port adapter
            Port adapter is disabled
            Port adapter insertion time unknown
            EEPROM contents at hardware discovery:
            Hardware revision 0.0           Board revision UNKNOWN
            Serial number     0             Part number    00-0000-00
            Version Identifier              FRU Part Number
            Test history      0x0           RMA number     00-00-00
            EEPROM format version 0
            EEPROM contents (hex):
              0x00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
              0x10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
              0x20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
              0x30: 00 00 00 00 00 00 00 00 00 00 00 00
    VIPER#
    --
    To respond to this post, please click the following link:
    <http://developer.cisco.com/group/srev/forums/-/message_boards/message/2687217>
    or simply reply to this email.

    Subject: RE: c2900-universalk9-mz.SSA.151-2.18.T not recognizing hardware
    Replied by: Andrew Benhase on 20-11-2010 01:34:25 AM
    A few answers ;)

    1)What exactly do you mean by nasty messages?
     
    >>>>
    controller I2C bus 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D017B8z 0x21406ECCz
     0x235DE9C0z 0x235DEA6Cz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:42.999: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D017B8z 0x21407EECz 0x235DEAFCz 0x23
    5DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:43.211: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D0187Cz 0x21407AFCz 0x21
    134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:43.211: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018A0z 0x21407AFCz 0x21
    134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:43.211: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D018B8z 0x21407AFCz 0x21
    134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:43.215: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018D8z 0x21407AFCz 0x21
    134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:43.215: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D01920z 0x21407AFCz 0x21
    134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:43.215: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D01944z 0x21407AFCz 0x21
    134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:45.655: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x2160670Cz 0x214339A4z 0x219BBC00z 0x219BBD20z 0x21
    433C08z 0x219BD0CCz 0x21346824z 0x21349384z 0x21134B8Cz 0x21134240z 0x21407F8Cz 0x235DEAFCz 0x235
    DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z
    *Oct 27 19:47:49.411: %PA-3-NOTSUPPORTED: PA in slot1 (Unknown (type 0)) is not supported on this
     image/licenses enabled. Please issue "show diag" CLI command to display the PA information, veri
    fy it is supported and, if applicable, ensure the correct license key is installed. A newer image
     version or license key may be needed.
    *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D0187Cz 0x21407AFCz 0x21
    134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018A0z 0x21407AFCz 0x21
    134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D018B8z 0x21407AFCz 0x21
    134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018D8z 0x21407AFCz 0x21
    134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:49.419: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D01904z 0x21407AFCz 0x21
    134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:49.419: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D01944z 0x21407AFCz 0x21
    134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:59.363: %VPN_HW-6-INFO_LOC: Crypto engine: onboard 0  State changed to: Initialized


    2). What image did you have before and was the SRE working ok before?
     
    THis was never working, I just got it. Swapped out FCS 15.12T for engineering building, rebooting and this is what I got.

    3) What is installed on the SRE?
    Nothing as far as I know, I just got this blade from Anurag.

    Subject: RE: New Message from Andrew Benhase in Service Ready Engine Virtualization
    Replied by: Radhika Miriyala on 20-11-2010 01:34:25 AM
    Hi Andrew,

    We looked at the decode from the trace back and it shows some IO bus issue . I will work with the IOS team and see what is happening but could you try reseating the module again and let us know what it says?



    Thanks,

    Radhika



    From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
    Sent: Wednesday, October 27, 2010 2:23 PM
    To: cdicuser@developer.cisco.com
    Subject: New Message from Andrew Benhase in Service Ready Engine Virtualization - SRE-V Beta Testing: RE: c2900-universalk9-mz.SSA.151-2.18.T not recognizing hardware



    Andrew Benhase has created a new message in the forum "SRE-V Beta Testing":
    --------------------------------------------------------------
    A few answers ;)

    1)What exactly do you mean by nasty messages?

    >>>>
    controller I2C bus 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D017B8z 0x21406ECCz
    0x235DE9C0z 0x235DEA6Cz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:42.999: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D017B8z 0x21407EECz 0x235DEAFCz 0x23
    5DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:43.211: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D0187Cz 0x21407AFCz 0x21
    134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:43.211: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018A0z 0x21407AFCz 0x21
    134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:43.211: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D018B8z 0x21407AFCz 0x21
    134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:43.215: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018D8z 0x21407AFCz 0x21
    134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:43.215: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D01920z 0x21407AFCz 0x21
    134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:43.215: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D01944z 0x21407AFCz 0x21
    134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:45.655: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x2160670Cz 0x214339A4z 0x219BBC00z 0x219BBD20z 0x21
    433C08z 0x219BD0CCz 0x21346824z 0x21349384z 0x21134B8Cz 0x21134240z 0x21407F8Cz 0x235DEAFCz 0x235
    DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z
    *Oct 27 19:47:49.411: %PA-3-NOTSUPPORTED: PA in slot1 (Unknown (type 0)) is not supported on this
    image/licenses enabled. Please issue "show diag" CLI command to display the PA information, veri
    fy it is supported and, if applicable, ensure the correct license key is installed. A newer image
    version or license key may be needed.
    *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D0187Cz 0x21407AFCz 0x21
    134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018A0z 0x21407AFCz 0x21
    134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D018B8z 0x21407AFCz 0x21
    134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018D8z 0x21407AFCz 0x21
    134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:49.419: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D01904z 0x21407AFCz 0x21
    134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:49.419: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D01944z 0x21407AFCz 0x21
    134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    *Oct 27 19:47:59.363: %VPN_HW-6-INFO_LOC: Crypto engine: onboard 0  State changed to: Initialized


    2). What image did you have before and was the SRE working ok before?

    THis was never working, I just got it. Swapped out FCS 15.12T for engineering building, rebooting and this is what I got.

    3) What is installed on the SRE?
    Nothing as far as I know, I just got this blade from Anurag.
    --
    To respond to this post, please click the following link:
    <http://developer.cisco.com/group/srev/forums/-/message_boards/message/2687336>
    or simply reply to this email.

    Subject: Re: New Message from Radhika Miriyala in Service Ready Engine Virtualizatio
    Replied by: Andrew Benhase on 20-11-2010 01:34:25 AM
    Will do.

    Sent from my iPad

    On Oct 27, 2010, at 19:05, "Cisco Developer Community Forums" <cdicuser@developer.cisco.com> wrote:

    > Radhika Miriyala has created a new message in the forum "SRE-V Beta Testing":
    > --------------------------------------------------------------
    > Hi Andrew,
    >
    > We looked at the decode from the trace back and it shows some IO bus issue . I will work with the IOS team and see what is happening but could you try reseating the module again and let us know what it says?
    >
    >
    >
    > Thanks,
    >
    > Radhika
    >
    >
    >
    > From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
    > Sent: Wednesday, October 27, 2010 2:23 PM
    > To: cdicuser@developer.cisco.com
    > Subject: New Message from Andrew Benhase in Service Ready Engine Virtualization - SRE-V Beta Testing: RE: c2900-universalk9-mz.SSA.151-2.18.T not recognizing hardware
    >
    >
    >
    > Andrew Benhase has created a new message in the forum "SRE-V Beta Testing":
    > --------------------------------------------------------------
    > A few answers ;)
    >
    > 1)What exactly do you mean by nasty messages?
    >
    > >>>>
    > controller I2C bus 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D017B8z 0x21406ECCz
    > 0x235DE9C0z 0x235DEA6Cz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:42.999: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D017B8z 0x21407EECz 0x235DEAFCz 0x23
    > 5DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:43.211: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D0187Cz 0x21407AFCz 0x21
    > 134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:43.211: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018A0z 0x21407AFCz 0x21
    > 134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:43.211: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D018B8z 0x21407AFCz 0x21
    > 134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:43.215: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018D8z 0x21407AFCz 0x21
    > 134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:43.215: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D01920z 0x21407AFCz 0x21
    > 134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:43.215: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D01944z 0x21407AFCz 0x21
    > 134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:45.655: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x2160670Cz 0x214339A4z 0x219BBC00z 0x219BBD20z 0x21
    > 433C08z 0x219BD0CCz 0x21346824z 0x21349384z 0x21134B8Cz 0x21134240z 0x21407F8Cz 0x235DEAFCz 0x235
    > DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z
    > *Oct 27 19:47:49.411: %PA-3-NOTSUPPORTED: PA in slot1 (Unknown (type 0)) is not supported on this
    > image/licenses enabled. Please issue "show diag" CLI command to display the PA information, veri
    > fy it is supported and, if applicable, ensure the correct license key is installed. A newer image
    > version or license key may be needed.
    > *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D0187Cz 0x21407AFCz 0x21
    > 134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018A0z 0x21407AFCz 0x21
    > 134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D018B8z 0x21407AFCz 0x21
    > 134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018D8z 0x21407AFCz 0x21
    > 134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:49.419: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D01904z 0x21407AFCz 0x21
    > 134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:49.419: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D01944z 0x21407AFCz 0x21
    > 134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:59.363: %VPN_HW-6-INFO_LOC: Crypto engine: onboard 0 State changed to: Initialized
    >
    >
    > 2). What image did you have before and was the SRE working ok before?
    >
    > THis was never working, I just got it. Swapped out FCS 15.12T for engineering building, rebooting and this is what I got.
    >
    > 3) What is installed on the SRE?
    > Nothing as far as I know, I just got this blade from Anurag.
    > --
    > To respond to this post, please click the following link:
    > <http://developer.cisco.com/group/srev/forums/-/message_boards/message/2687336>
    > or simply reply to this email.
    > --
    > To respond to this post, please click the following link:
    > <http://developer.cisco.com/group/srev/forums/-/message_boards/message/2687495>
    > or simply reply to this email.

    Subject: RE: New Message from Andrew Benhase in Service Ready Engine Virtualization
    Replied by: Ashwin Venkatesan on 20-11-2010 01:34:25 AM
    Hi Andrew,



    Is the  c2900 box a production one ?



    Thanks

    Ashwin



    From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
    Sent: Wednesday, October 27, 2010 7:24 PM
    To: cdicuser@developer.cisco.com
    Subject: New Message from Andrew Benhase in Service Ready Engine Virtualization - SRE-V Beta Testing: Re: New Message from Radhika Miriyala in Service Ready Engine Virtualizatio



    Andrew Benhase has created a new message in the forum "SRE-V Beta Testing":
    --------------------------------------------------------------
    Will do.

    Sent from my iPad

    On Oct 27, 2010, at 19:05, "Cisco Developer Community Forums" <cdicuser@developer.cisco.com> wrote:

    > Radhika Miriyala has created a new message in the forum "SRE-V Beta Testing":
    > --------------------------------------------------------------
    > Hi Andrew,
    >
    > We looked at the decode from the trace back and it shows some IO bus issue . I will work with the IOS team and see what is happening but could you try reseating the module again and let us know what it says?
    >
    >
    >
    > Thanks,
    >
    > Radhika
    >
    >
    >
    > From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
    > Sent: Wednesday, October 27, 2010 2:23 PM
    > To: cdicuser@developer.cisco.com
    > Subject: New Message from Andrew Benhase in Service Ready Engine Virtualization - SRE-V Beta Testing: RE: c2900-universalk9-mz.SSA.151-2.18.T not recognizing hardware
    >
    >
    >
    > Andrew Benhase has created a new message in the forum "SRE-V Beta Testing":
    > --------------------------------------------------------------
    > A few answers ;)
    >
    > 1)What exactly do you mean by nasty messages?
    >
    > >>>>
    > controller I2C bus 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D017B8z 0x21406ECCz
    > 0x235DE9C0z 0x235DEA6Cz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:42.999: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D017B8z 0x21407EECz 0x235DEAFCz 0x23
    > 5DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:43.211: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D0187Cz 0x21407AFCz 0x21
    > 134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:43.211: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018A0z 0x21407AFCz 0x21
    > 134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:43.211: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D018B8z 0x21407AFCz 0x21
    > 134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:43.215: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018D8z 0x21407AFCz 0x21
    > 134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:43.215: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D01920z 0x21407AFCz 0x21
    > 134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:43.215: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D01944z 0x21407AFCz 0x21
    > 134188z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:45.655: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x2160670Cz 0x214339A4z 0x219BBC00z 0x219BBD20z 0x21
    > 433C08z 0x219BD0CCz 0x21346824z 0x21349384z 0x21134B8Cz 0x21134240z 0x21407F8Cz 0x235DEAFCz 0x235
    > DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z
    > *Oct 27 19:47:49.411: %PA-3-NOTSUPPORTED: PA in slot1 (Unknown (type 0)) is not supported on this
    > image/licenses enabled. Please issue "show diag" CLI command to display the PA information, veri
    > fy it is supported and, if applicable, ensure the correct license key is installed. A newer image
    > version or license key may be needed.
    > *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D0187Cz 0x21407AFCz 0x21
    > 134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018A0z 0x21407AFCz 0x21
    > 134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D018B8z 0x21407AFCz 0x21
    > 134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:49.415: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D018D8z 0x21407AFCz 0x21
    > 134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:49.419: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00AC0z 0x21D01904z 0x21407AFCz 0x21
    > 134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:49.419: %IOCTRL-3-I2C_ERROR: I2C R/W Error accessing device on io-controller I2C bu
    > s 1 : I2C Slave Device not found -Traceback= 0x21606E54z 0x21D00A58z 0x21D01944z 0x21407AFCz 0x21
    > 134750z 0x21407F8Cz 0x235DEAFCz 0x235DEBE4z 0x2237CBA8z 0x2237CE48z 0x2357AFF4z 0x2357AFD8z
    > *Oct 27 19:47:59.363: %VPN_HW-6-INFO_LOC: Crypto engine: onboard 0 State changed to: Initialized
    >
    >
    > 2). What image did you have before and was the SRE working ok before?
    >
    > THis was never working, I just got it. Swapped out FCS 15.12T for engineering building, rebooting and this is what I got.
    >
    > 3) What is installed on the SRE?
    > Nothing as far as I know, I just got this blade from Anurag.
    > --
    > To respond to this post, please click the following link:
    > <http://developer.cisco.com/group/srev/forums/-/message_boards/message/2687336>
    > or simply reply to this email.
    > --
    > To respond to this post, please click the following link:
    > <http://developer.cisco.com/group/srev/forums/-/message_boards/message/2687495>
    > or simply reply to this email.
    --
    To respond to this post, please click the following link:
    <http://developer.cisco.com/group/srev/forums/-/message_boards/message/2689038>
    or simply reply to this email.

    Subject: RE: New Message from Andrew Benhase in Service Ready Engine Virtualization
    Replied by: Andrew Benhase on 20-11-2010 01:34:25 AM
    No, the 2900 came from Demo Depot last week.
     
    I powered down, removed and inspected the edge connectors on the card and the backplane of the router. Nothing obvious in terms of damage. The exact same errors come up again.
     
    The router of course boots just fine and operates, but no FRU/hardware/diag information shown for the card. Just seem to be getting these I/O errors.
     
    Open to any ideas...

    Subject: RE: New Message from Andrew Benhase in Service Ready Engine Virtualization
    Replied by: Anurag Gurtu on 20-11-2010 01:34:27 AM
    If you take out the module and reboot the router what happens? Do you see any errors?
     
    If you ignore the errors can you configure IOS side IP addresses and then are able to session into the blade?

    Subject: RE: New Message from Andrew Benhase in Service Ready Engine Virtualization
    Replied by: Andrew Benhase on 20-11-2010 01:34:35 AM
    Anyone have any ideas here? Looking for options.

    Subject: RE: New Message from Andrew Benhase in Service Ready Engine Virtualization
    Replied by: Andrew Benhase on 20-11-2010 01:34:35 AM
    Router works just fine. IOS does not recognize the blade, so no way to session. When i Show Diag | inc FRU - it does not show a recognized blade. So, no commands available.
     
    It seems like the blade is the problem, although I wouldn't rule out the router, however it boots just fine on its own and came straight from DD. Any chance at a replacement blade? I'm short on troubleshooting options...esp if IOS can't get past card init during boot.
     
    If you take out the module and reboot the router what happens? Do you see any errors?
     
    If you ignore the errors can you configure IOS side IP addresses and then are able to session into the blade?


    Subject: RE: New Message from Andrew Benhase in Service Ready Engine Virtualization
    Replied by: Anurag Gurtu on 20-11-2010 01:34:35 AM
    The blade is brand new. Is the router good? Do you have a NME with an adapter that you can try.



    Thanks,



    Anurag Gurtu, CISSP

    Subject: RE: New Message from Andrew Benhase in Service Ready Engine Virtualization
    Replied by: Brett Tiller on 06-12-2010 11:15:39 PM
    Hi Andrew,
     
    Checking in with you.  I spoke to Anurag and I believe this hardware issue has been resolved.  Is that correct?
     
    Thanks,
     
    Brett