ASR1001 supported on RME 4.3

I noticed in RME inventory, my ASR1001 hardware is not recognized.
I checked my Ciscoworks and it only knows ASR1002, 1004, and 1006 routers.
I checked the supported device table for LMS 3.2 and did not find ASR1001.
Is there a separate device package I can download. This is not a deal breaker, but it's unnerving to see the question mark icon next to the name of my router in the Ciscoworks GUI.

Sorry, but it looks like that's all you're going to see in for an ASR 1001 on RME 4.3. You need to be on LMS 4 to get ASR 1001 support.

Similar Messages

  • RME 4.3.1 on new server - 2 issues with Inventory and syslog

    Hi,
    I recently installed new server 2003 with LMS3.2 and after the problems with DevicePackages i resubmitted all device and the device center tasks that was missing now reappeared.
    So I went on and added my two VPN3030 VPN Concentrators.
    This device is supported for RME inventory and syslog
    I got the config-archive running (!) so thats fine (Runs via HTTPS login)
    I have two issues:
    1. I can not get inventory to work .
    I have communication going, and a packet trace/sniff show I have syslog going into RME and i see SNMP GET and respones to/from device
    I see some java error logs in ic_server.log fil
    I have tried with two different LMS32-servers
    I have increased SNMP timeout etc
    I tried deleted the device and rediscover
    log are like this:
    [ Thu Aug 19  10:12:30 CEST 2010 ],ERROR,[Thread-14],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,761, Collection failed for the device : 3748
    com.cisco.nm.xms.xdi.ags.system.CollectionFailed: com.cisco.nm.lib.snmp.lib.SnmpException: SnmpResponseNoSuchName on 10.3.6.2 while performing SnmpWalk(*) at index = 10
        at com.cisco.nm.xms.xdi.pkgs.LibInventory.PortInterfaceAGI_RFC1213_HelperMethods.getIfTableEntriesFromDevice(PortInterfaceAGI_RFC1213_HelperMethods.java:639)
        at com.cisco.nm.xms.xdi.pkgs.SharedInventoryVPN3000.PortInterfaceAGI_RFC1213_Mib.g$eval(PortInterfaceAGI_RFC1213_Mib.java:77)
        at com.cisco.nm.xms.xdi.ags.PortInterfaceAGI.g$eval(PortInterfaceAGI.java:21)
        at com.cisco.nm.xms.xdi.SdiEngine.initAndEvalAGIs(SdiEngine.java:383)
        at com.cisco.nm.xms.xdi.SdiEngine.request(SdiEngine.java:309)
        at com.cisco.nm.xms.xdi.SdiEngine.getDevRepr(SdiEngine.java:302)
        at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:539)
        at java.lang.Thread.run(Thread.java:595)
    [ Thu Aug 19  10:12:30 CEST 2010 ],INFO ,[Thread-14],com.cisco.nm.rmeng.inventory.ics.core.CollectionController,841,Device collection failed for 10.3.6.2
    2.:I can not get syslog into the devices syslog reports
    This is wierder than issue 1: I have two VPN3030, one actually does syslog fine, but one VPN 3030 does not
    I havent done any thing different for the two device ...
    one simply works, one doesnt ...
    I get no syslog msg in device center for one of the device.
    The syslogs ARE infact in the syslog.log
    The syslog msg DO show up, but in Unexpected device report  ...
    The same VPN device does work with my second server so I think this is related to RME database on one specific server.
    But i have tried delete device and rediscover etc ...
    please help ...

    ok - looks like i need TAC again ...
    As for the syslog issue - this happens only for one device on one of my servers ...
    That is what is strange ... So IP is coorect and ok - (they do get syslogs into DevCenter on one server and on other device)
    Thank you for your reply - really nice that you take your time into this forum !

  • Call manager and rme config archive report

    Hi,
    I know that rme does not support the call manager for config archive. It is clear.
    The RME home page show config archive status for failed devices and there are some devices which are not supported by RME config archive.
    I've set this devices to suspended state in RME but config archiv is trying with this devices also.
    This is a financial costumer and the local Financial supervisory authority would like to see all devices config is saving successfully.
    How can i exclude the call manager and similar devices from config archiv process and status reports?
    Regards,

    Hi,
    I would like to qoute from RME help.
    Working With Suspended Devices
    Suspended device state cannot participate in any RME application flows but all historical data pertaining to the device will continue to be maintained by RME.
    Nevertheless the RME is trying to fetch the config from suspended devices!!!
    What is the truth in this thing?
    Regards,

  • RME 4.3.1 & Nexus 7000 device package

    I am have 27 devices that RME reports as "Out-of-Sync", among those some are Nexus 7K devices, with the sysObjectId .1.3.6.1.4.1.9.12.3.1.3.612, which according to the "Supported Device Table for LMS 3.2" is supported in RME 4.3.1.
    Searching for device package with that sysObjectId I get no result in Common Services. However, when performing a "Device Update" with my CCO account, Ciscoworks tells me that "All the available package(s) at source location are already installed."
    What do I have to do to get that device package?

    Hi,
        To check / download the latest RME Device Package for Nexus 7k support, please do the following :
    1. Go to Common Services -> Software Centre -> Device Update and click on the hyperlink for 'CiscoWorls Common Services'
    * You should see 2 packages listed  - Device Data and MDF.
    * The latest versions of these are 1.10 and 1.48 respectively.
    * If you don't have the lateset versions installed, please run an update to install these.
    2. Once you have the most up to date packages for Common Services installed, go to Common Services -> Software Centre -> Device Update and click on the number in the 'Device Type Count' collumn for Resource Manager Essentials.  Filter the list of devices by Package Name = Nexus.
    * Do you see sysObjectId .1.3.6.1.4.1.9.12.3.1.3.612 displayed ?
    * What version of the Nexus device package do you have installed ? (The latest version is 2.5)
    3. Even if you have the latest Nexus package installed, run a device update for RME so that you loaded the latest versions of all packages (I see there were some new updates for shared packages eg LibCommon as recent as 21st January 2011.
        In terms of the devices being reported as 'Out-of-sync' , this means that RME has detected that the running configuration and the startup configuration on the device are different. This could be because RME doesn't have the most recent copy of either config or it is a real situation of the startup and running config being out of sync on the device.  If you go to the Out-of-Sync Summary page, select the Nexus 7k's and click on 'Sync on Device' RME will run a job to login to the devices and execute a copy run start.
    * If your Nexus 7k's are still reported as 'Out-of-Sync' after the job completes then we'll need to investigate further.
    Regards
    Derek Clothier

  • Cat4000-IOS not seen as member of its own vtp domain in CM

    Recently we upgraded to CiscoWorks CD 5 V1. Cat4000-IOS devices are now supported in RME and CM. But in CM Topology Services the Cat4000-IOS devices are not seen as members of their own VTP domain. Instead, each access switch behind the Cat4000-IOS forms a single switch cloud (vtp disconnected domain) and no vtp server is found for that domain.
    The two Cat4000-IOS serve as VTP servers and HSRP-Gateways for five access switches (Cat4000 with CatOS) connected via dot1q-trunks to each Cat4000-IOS.

    I am having the same problem. I followed the link and the document says "A link in a VTP domain is not set to trunk. There are devices in this domain that do not communicate through any trunk." I have checked the devices and they are set up to trunk. In CiscoWorks - topology services, when I run a Logical Discrepancy Report It says the domain is disconnected and it is showing 15 sets. Set one shows my two 6509's, one 4006 & all of the 3524's connected to it. All of the other sets have only one 3524 in each of them. The trunk ports from two of my 4006's to my 6509's are as follows:
    interface Port-channel1
    description Uplink to C_BCAD_2213_6x_1
    switchport
    switchport trunk encapsulation isl
    switchport mode trunk
    no snmp trap link-status
    On one of my other 4006's the trunk port is as follows:
    interface Port-channel4
    switchport
    switchport trunk encapsulation isl
    switchport mode trunk
    description Uplink to C_BCAD_2213_6x_1
    no snmp trap link-status
    As you can see, they are both set up the same.
    Also in Campus Manager, only the 4006 in set 1 & all of the 3524's show up graphically as clients. The two 6509's show up as servers.
    All devices are running VTP version 2. The revision number on all devices is the same (10).

  • Does someone knows about this tool on LMS 3.2?

    I am quoting from the LMS 3.2 Deployment Guide:
    What’s New: Generic Device Support in RME
    Day one device support for network management applications is a continuing challenge. As new hardware platforms
    come to market, device support may be lagging. The CiscoWorks Incremental Device Update team announces
    availability of a new "automated" update tool, providing device support for inventory and configuration functionality
    within Resource Manager Essentials. This tool allows customers to quickly get support for new hardware platforms
    where complete device package support through the Incremental Device Update program has not yet been
    delivered. This new tool can be downloaded from
    http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme andinstalled on the LMS 3.01, 3.1, and 3.2 code base. The following features are enabled for devices using the
    automated update tool:
    Device Management in RME:The Device Manageability Status Report provides details as to whether the device is officially supported or
    managed using automatic IDU.
    Inventory Management in RME:
    ◦System-, port-, memory-, Flash-, and bridge-related information will be queried using Entity or the OCCM
    MIB.
    ◦Support for CDA will be provided.
    ●
    Config Management in RME:
    ◦Sync archive using CLI and TFTP protocols
    ◦Ad-hoc template in NetConfig deployment
    ◦Partial NetShow if MDF association is available
    ◦Raw mode in version summary and version tree
    ◦Partial out-of-sync summary and compare configuration
    ◦Config Editor support for editing in raw mode only
    An announcement regarding similar support capability in Campus Manager and Device Fault Manager will be sent
    when it becomes available.

    You can go to Common Services > Software Center > Device Update, click the the RME link, and search for GenericDev.  If you find it, then you have the package installed.  For any device which has a sysObjectID which RME doesn't recognize with a specific package, this package will be tried instead.
    If you find that the package is not already installed, perform a device update for RME, and download and install all available device packages.

  • FireFace 800 inputs 9/10 in Logic?

    Just having a hard time here. I have mics going into all 4 preamps on the front of my FF800 (analog inputs 7, 8, 9, and 10). In Logic, I have 4 tracks receiving input from the same. Only 7 and 8 show any signal at all. In RME TotalMix, I have signal on all 4. In TotalMix, I am using the factory default preset #1.
    Any experience here? Thanks.

    I just set up a mic on preamp #10 and recorded it in Logic. I didn't change anything in Matrix. I guess this isn't much help, but at least you know someone was able to make it work. I've had excellent tech support from RME. Usually a clear email gets a quick reply with a clear solution. Good luck.

  • Sync Archive fails for CRSs on LMS 3.1

    Hi, I've been trying to collect the configuration of some CRS-1 4-slot but it keeps on failing. These are the only devices I'm missing (out of 2,000). I've tried to tweak the timeout values but it makes no difference. The actual values are set to:
         SNMP Retry = 6
         SNMP Timeout = 90 sec
         Telnet Timeout = 120 sec
         TFTP Timeout = 60 sec
    The protocols I'm using to retrieve the configs are SSH, Telnet, and TFTP. Telnet is disabled on this devices, they use SSH v2 instead. What I get from the job details is:
    *** Device Details for 9R_MCO_NEXTENGO ***
    Protocol ==> Unknown / Not Applicable
    Selected Protocols with order ==> SSH,Telnet,TFTP
    Execution Result:
    CM00139 Could not archive config Cause: Action: Verify that device is managed and credentials are correct. Increase timeout value, if required.
    They are managed by RME, indeed and it has been able to collect their inventory. This CW is installed on Solaris 9. If I try to SSH from the console it prompts me for a password, but if I type in CW server's account password it won't log me in. Then I need to specify my username and I'm able to get access.
         # ssh 10.255.0.41 -l CISWORKS
    Does this looks like an SSH issue? Then it should be able to collect the configs by TFTP. Or are CRSs not fully supported on LMS 3.1? This devices are running IOS XR 3.6.2.
    Thanks in advance.

    This sounds to me like the credentials are misconfigured in DCR.  Go to Common Services > Device and Credentials > Device Management, and re-enter the username and password for this device.  Then see if you can archive the configuration.  The CRS-1 4-slot chassis is supported in RME 4.2.

  • Inventory on 2503 routers

    Hello
    I have recently installed LMS2.6 with all the latest software for each of the components i.e. CiscoWorks Common Services 3.0.5,Ciscoview 6.1.5, Resource Manager Essentials 4.0.5, Ciscoview 6.1.5, Device Fault Manager 2.0.8.
    I have over 600 routers and switches which are being managed by LMS. I have over 100 2500 routers still on the network and the inventory is not being picked up from any of these.
    Does anyone know if this is a known issue?
    Thank You
    Regards
    Donagh

    Hi Donagh.
    The 2500's are indeed supported in RME 4.0.5 (part of LMS 2.6):
    http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/cw2000e/e_4_x/rme405/rme405.htm#wp224855
    You mentioned that you have added several hundred other devices, but just the 2500's have been a problem. Can you please tell me what method you've used to add these? Is there any difference in the community strings on the devices you have added, and those you can't? And finally, can you (from the command line on the LMS server) snmpwalk the 2500's?
    -Joe

  • RME 4.0.3 (Supported devices)

    Hello!
    I have installed LMS 3.2 with RME 4.0.3.
    Apparently from the document
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.2/device_support/table/lms32sdt.html#3.2table
    RME 4.0.3 does not support Cisco Cat6500, Routers 3800, which we have in our network.
    So my question is: how to solve this problem?

    If I'm not mistaken, those tables show newly added support of devices & modules, so cat6500 and 3800 support have been around a lot longer than since RME 4.3. You just have to make sure you update your Device Support packages for those two platforms at Common Services > Software Center > Device Updates.

  • Issues with CWLMS 3.2 RME 4.3.1 cannot fetch vlan.dat off a VSS and 4510.

    Hi,
    I am having a major headache with RME collecting the vlan.dat from a VSS and 4510, the device and credentials work fine, however when archiving the config i get partial success due to vlan failing. You can see in the IC_Services log that it attempts to TFTP the .dat file off which it fails with, i believe vlan fetch is only supported by SSH or telnet
    when you do a CDA test both devices pass on everything..

    managed to log on and please see below, tftp on one device works fine but from the 4510 or vss still fails
    GRA_CHUB_CR_01#copy cat4000_flash: tftp:
    Source filename []? vlan.dat
    Address or name of remote host []? 172.20.220.10
    Destination filename [vlan.dat]?
    %Error opening tftp://172.20.220.10/vlan.dat (Timed out)
    GRA_CHUB_CR_01#
    DAR_R002_AS_01#
    DAR_R002_AS_01#copy flash:vlan.dat tftp:
    Address or name of remote host []? 172.20.220.10
    Destination filename [vlan.dat]?
    616 bytes copied in 0.009 secs (68444 bytes/sec)
    DAR_R002_AS_01#

  • How to make a report in RME to display all POE capable devices

    Hello,
    I need to create a report that will list switches in my network that support POE. Most of our switches are 3750 stack and I know most of them have POE capabilities but whenever I generate the report under RME POE Port Level Report or POE Report it gives me an error that says none of the devices are POE capabled/enabled.
    Does anyone know how to generate this kind of report? I tried making a template but I still couldn't produce the result that I need.
    Thanks in advance.

    HI ,
    CSCsx15486            Bug Details
    RME cannot create Inventory PoE Report for certain switches
    Currently, RME is only able to create PoE Inventory reports for Cat3750 and 3560 switches:
    WS-C3560-24PS - 1.3.6.1.4.1.9.1.563
    WS-C3560-48PS - 1.3.6.1.4.1.9.1.564
    WS-C3560G-24PS - 1.3.6.1.4.1.9.1.614
    WS-C3560G-48PS - 1.3.6.1.4.1.9.1.616
    WS-C3750E-24PD - 1.3.6.1.4.1.9.1.792
    WS-C3750E-48PD - 1.3.6.1.4.1.9.1.791
    WS-C3560E-24PD - 1.3.6.1.4.1.9.1.795
    WS-C3560E-48PD - 1.3.6.1.4.1.9.1.796
    It does not work for other switches.
    Even the 3750G switches are not currently supported. The sysObjectID is:
    .1.3.6.1.4.1.9.1.516
    Thanks--
    Afroj

  • T61p back from depot after 1 month with same problems, phone support no help

    I ordered this on Feb 8. My CC was billed March 5th which is around when I physically got it. I basically troubleshooted it until the end of the month before calling to get it sent for repairs. Got the box for the depot on April 3 and sent it the same day. Got the laptop back just on Monday May 12. Now it still doesn't work, and I'm wondering what the heck to do.
    Problems with the T61p:
    1. Cardbus non functional; The pci/cardbus bridge is detected fine and drivers not a problem. The system doesn't detect any card inserted in the T61p. I have a $100 firewire 800 card I've used without problems in many laptops (I can test in one right now), but this T61p doesn't see it at all. This is not a driver issue for any particular card, but the fact that windows doesn't detect any new hardware when a card is inserted.
    Sent to the depot at the beginning of April and I got it back this Monday. They replaced the mainboard and pcmcia slot (as it says on the slip included). Still having the exact same problem.
    2. Completely unstable with a 1394b expresscard; Since I cannot get the cardbus slot to work, my only option is an expresscard. I am using a studio quality sound interface, Fireface 800 from RME. This is a great piece of hardware that works flawlessly on my 5 year old AMD box. However, on the T61p if I playback audio through it, connected via a SIIG firewire 800 expresscard (high quality, and one of the _only_ 1394b expresscards out there) the system completely locks up in a matter of minutes.
    The main reason for this laptop purchase was for music production with the RME Fireface. It is 100% the T61p causing the problem, not power management issues, driver issues, the SIIG card, or physical connections, etc. You can see my thread at RME from March when I was trying to figure this out:
    http://rme-audio.de/forum/viewtopic.php?pid=11332
    I haven't had a full month of use of this thing. I would very much just like a return at this point. I don't want to wait another month for a depot repair, seeing as the last one didn't resolve anything. If I could get a fully working model of this T61p that would be great, but I see this 14.1" SXGA+ isn't even offered anymore.
    Talking to support is horrible. Last I talked to someone who was technically clueless, saying he would do research and call me back. I call back the next day and there isn't even a record of me talking to anyone...
    Anyone have any advice? I'm coming to the forums because I'm just stuck here with a laptop I can't use, and don't know what to do with...
    EDIT/update:
    I managed to get this number finally (1-866-968-4465) and talked to someone who seemed to actually care. So I've gotten somewhere, I guess the forum post doesn't help much. I'll update the result anyway...
    Message Edited by trancer on 05-16-2008 01:46 PM

    Mine is the siig NN-EC2812-S1 2-port FireWire 800 ExpressCard/54 and the carbus card is a StarTech.com CB1394B3
    Where do you read about chipset compatability probs with siig cards? What would be a better card?
    Edit:
    I could get one of these within a day or so:
    belkin F5U514 $98 CAN
    startech EC1394B2 $119 CAN
    sonnet FW800-E34 $98 CAN
    Know which would be better to try?
    Message Edited by trancer on 05-16-2008 03:06 PM
    Message Edited by trancer on 05-16-2008 03:07 PM
    Message Edited by trancer on 05-16-2008 03:10 PM

  • RME Out of Sync Partially Successfull

    We recently upgraded to LMS 3.2 from 2.6, RME is reporting some devices as out of sync and details are partially successfull failing to fetch the vlan.dat. I've checked device credentials.
    Here is a a snapshot of the device details from one of the devices.
    Protocol ==> SSH
    Selected Protocols with order ==> SSH,Telnet,TFTP,RCP
    Execution Result:
    RUNNING
    Primary Login Succeeded
    / Primary Enable Succeeded
    CM0060 PRIMARY RUNNING Config fetch SUCCESS for , version number 11 archived.
    VLAN
    CM0151 VLAN RUNNING Config fetch failed for  Cause: Couldnot create file in C:\PROGRA~1\CISCOS~1\UPGRAD~1 directory.Couldnot create file in C:\PROGRA~1\CISCOS~1\UPGRAD~1 directory.
    VLAN Config fetch is not supported using TFTP.
    VLAN Config fetch is not supported using RCP.
    Action: Check if protocol is supported by device and required device package is installed. Check device credentials. Increase timeout value, if required.
    What I find strange is 'Couldnot create file in C:\PROGRA~1\CISCOS~1\UPGRAD~1 directory.Couldnot create file in C:\PROGRA~1\CISCOS~1\UPGRAD~1 directory'. We installed LMS in it's own directory under C:\ciscoworks\cscopx so why do only a few devices that fail look like they are pointing to the program files directory and is that the true cause ? Incidently there is a folder in there as we installed another cisco tool for upgrading access points, but I have no idea why RME wants to point there ?

    I uninstalled the upgrade tool wanting to see if the error msg changed and it did.....
    Now it reports "CM0151 VLAN RUNNING Config fetch failed for 142.99.56.75 Cause: Couldnot create file in N/A directory.Couldnot create file in N/A directory."...
    I've attached the regdaemon.xml you requested.

  • RME Fireface 800 in 64 bit Problem

    Using information helpfully provided by Kappy and The Hatter on this forum (see topic https://discussions.apple.com/message/27751034?ac_cid=op123456 if interested) I found that I was able to get my Mac Pro (early 2008) 3,1 to boot in 64 bit mode, and that Logic Pro 9 could also be made to open and work in 64 bit mode.
    I am currently using OSX 10.6.8 Snow Leopard, but am waiting for 10.8 Mountain Lion to be “delivered” (by email) so that I can use Arturia’s  V Collection 4 and their Keylab 61 USB MIDI keyboard controller, both of which require Mountain Lion. V Collection 4 is 64 bit only, which is why I want to use 64 bit.
    It all seems to work except my RME Fireface 800 interface, which is not recognised in 64 bit - red light on the FF800 unit and the associated software will not open. The FF800 works fine when I go back to 32 bit on the Mac Pro.
    Does anyone here know about the issue with 64 bit and the RME Fireface 800 please? Maybe it just needs updated drivers? I have emailed RME and await their reply but it made sense to ask here as well.
    Any help would be much appreciated.
    Thanks
    Steve
    [By the way, I have checked, from very helpful people on this forum, that Mountain Lion is compatible with my Mac Pro, and that the Mac Pro does have 64 bit kernal]

    Just needed to download up-to-date driver and flash firmware. Solved with the help of RME support. :-)

Maybe you are looking for