LMS 3.2.1 - Unreachable Device Report - ICMP problem

Hello,
I use the unreachable device report in CS for checking the basic reachability of the managed devices.
A very useful feature!
But on one LMS installation I have a huge number of "unreachable" devices which are normally reachable via ICMP.
I use only the ICMP check with a timeout of 2 sec and one retry.
Checking the debug for that polling told me that at the beginning of the daily running job all works fine.
CS sends an ICMP to 10 devices and gets response. After that the next 10 devices and so on.
After some cycles it increases the number of parallel workflows to 2, means 2x 10 devices will be polled.
And with that change the problems begin, from my point of view. At this point 2 or 3 devices will be marked as unreachable.
With the next cycle of 2x10 devices 5-8 devices are "unreachable" and then all devices till the end are unreachable.
That sounds like there is an overflow on the application or server which can't handle so much ICMP replies.
Changing the timeout or retries didn't help.
Is there a possibility to fix the parallel requests to 10 without an increase?
Thanks a lot!
Sven

This sounds like #
CSCte60815    DCRDevice Poll using ICMP wrongly shows devices as Unreachable
You may have to use snmp as well to get the correct status.

Similar Messages

  • Unreachable devices report

    Hi,
    I noticed in Cisco Prime 4.2 when we try to look for devices that are unreachable, we went to Reports>Inventory>Management Status>Unreachable Devices, but the devices indicated there are currently Up. We have another Cisco Prime Demo server not connected to the production network, it is monitoring another set of devices. We went to Unreachable Devices report from the Demo server but this time it shows no Unreachable Devices but currently 2 devices were disconnected from the network. How come this report is unreliable? Do know a report tool from Cisco Prime 4.2 that is accurate aside from the Event Monitor?
    Thanks in advance for the help.

    Hi Benjo,
    Yes , it is completely different from them, with poller you are polling devices with different OID's in the background.
    for e.g in the device avaiblity it is using sysuptime ...etc
    check the below link:
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.2/user/guide/lms_monitor/mnt-perf.html#wp1542387
    Thanks-
    Afroj

  • LMS 4.0: Fault Monitoring Device Administration stuck in learning

    Hello Members,
    i have a problem with Fault Monitoring Device Administration. i have two devices which stuck in learning mode for almost forever. When the job is done the devices report an error SNMP timeout. I run a credential verfication job and the credentials for the devices are correct.
    any ideas?
    regards
    alex

    Assuming these are the only four devices using SNMPv3 in LMS, then the engineID is a non-issue.  However, if any other device has the same engineID as those two non-working devices, the problem could still be a duped engineID.  Debugging with logs is fairly complex.  The easiest way to identify the problem is to use a sniffer.  Start a sniffer trace filtering on all traffic to one of the failing devices.  Then, rediscover the device in Fault Monitoring under Admin > Collection Settings > Fault > Fault Monitoring Device Administration.  When it goes to a Questioned state, look at the sniffer trace.
    If you see SNMP report packets indicating an error of notInWindow, that points to the duplicate engineID problem.  ICMP packets without responses points to problems with ping.

  • How to read device report for HP Deskjet 1510

    Hi HP,
    I can see from the software provided with this printer there is this option to print the device reports.
    Please assist on how to read this report because it consist of unknown coding and stuff. 
    I would appreciate if your side can help me on this coz I assume that we can track our usage through this report.
    If this is not the purpose, perhaps you may suggest any other way to get an understandable usage reports? 
    Regards,
    Nadiya
    This question was solved.
    View Solution.

    Hello Nadiya,
    Welcome to the forums
    I understand you are looking for a usage report. The printer will print a test page and you can see the page count on that page, along with the printer information, such as your serial number, etc. If there is anything else you may mean by "usage" please let me know and I will do my best to help.
    Click this link: Fixing Ink Streaks, Faded Prints, and Other Common Print Quality Problems
    In the guide, look under "Solution six: Print and evaluate a test page and troubleshoot defects" and print a test page.
    Take care,
    R a i n b o w 7000I work on behalf of HP
    Click the “Kudos Thumbs Up" at the bottom of this post to say
    “Thanks” for helping!
    Click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution!

  • The recording device reported the media error: Unknown device error. (0x0C,

    Hello
    I have a problem making a DUAL LAYER DVD, i have done anothers before. But now I can't burn it.
    It's a message error.
    (The recording device reported the media error: Unknown device error. (0x0C, 0x00.))
    Next this my Mac configuration.
    Model Name: Mac Pro
    Model Identifier: MacPro3,1
    Processor Name: Quad-Core Intel Xeon
    Processor Speed: 3.2 GHz
    Number Of Processors: 2
    Total Number Of Cores: 8
    L2 Cache (per processor): 12 MB
    Memory: 6 GB
    I have DVD STUDIO PRO 4.2.1, and in the log appears this:
    Starting DVD Build UNTITLED_DISC...
    Compiler Initializing...
    Precompiling Project UNTITLED_DISC
    Compiling VMG Information...
    Created 6 PGCs in VTSM1
    Created 8 PGCs in VMG.
    0 Menu(s) will be created...
    Compiling Menu PGCs...
    Writing VTS010.VOB
    Writing VIDEO_TS.VOB
    1 VTSs and 1 Titles will be created...
    Compiling VTS#1 (Track 1)...
    Writing VTS010.VOB
    Muxing VTS011.VOB
    Done.
    Linking VMG...
    Linking VTS#1...
    Writing VTS#1...
    Writing VMG...
    Writing Layout Info...
    Compile Completed Successfully
    Note: The file ‘UNTITLED_DISC.layout’ found in the ‘VIDEO_TS’ folder is not a DVD-Video file and will not be included in the final disc or DLT.
    Note: The file ‘VOB_DATA.LAY’ found in the ‘VIDEO_TS’ folder is not a DVD-Video file and will not be included in the final disc or DLT.
    Start formatting
    Formatting as Standard DVD
    Simulation mode is off
    Lossless linking is on
    Number of layers is 2
    Doing opposite track path
    Setting layer switch at sector 2053488.
    Doing side 1 of 1
    Playable in region 1,2,3,4,5,6,8
    Disc size is 12 cm
    Disc has no copyright material
    Writing ISO 9660 directories
    Writing UDF 1.02 structures
    Writing files
    The recording device reported the media error: Unknown device error. (0x0C, 0x00.)
    What should be the problem?

    There could be a few reasons, a common one is bad DVDs or a burner going bad.
    [Some threads discussing the error|http://discussions.apple.com/search.jspa?threadID=&q=Therecording+device+reported+the+media+error%3A+Unknown+device+error.+(0x0C%2C0x00.)&objID=f952&dateRange=all&userID=&numResults=15]
    You can try the [arrpoach in this thread|http://discussions.apple.com/thread.jspa?messageID=2453295&#2453295] as s start.
    Take a look at this
    Not sure which brand of DVDs you are using, but [this guide rates brands|http://www.digitalfaq.com/reviews/dvd-media.htm]
    Verbatim are usually good for me for DL.

  • USB Storage Devices report "no media"

    Lately, I've been having a problem with USB memory sticks on my HP laptop running Windows 7 x64.  I've tried a SanDisk Cruzer and a Staples Relay  In each case, when the device is plugged in, it soon appears in Device Manager both under "Disk
    drives" with their respective brand names and under "Universal Serial Bus controllers" as a generic "USB Mass Storage Device".  After a delay, it appears with a drive letter assignment in "My Computer" and is visible
    in "Disk Management".
    However, normally the USB device blinks for a short time and then glows steadily.  In this case, it continued to blink.  
    Furthermore, when the drive letter (H: in this case, because I have two HDD partitions and the DVD/CD device shows as E, F, and G) is opened in Explorer, it shows as empty.  Clicking on New Folder produces the message, "device not available, please
    insert media and try again".  Disk Management reports, "no media".
    After examining various posts, I took the advice of Uninstalling the device from Device Manager (both the branded listing under Disk drives and the generic Mass Storage Device under USB Controllers, and then letting Windows reinstall the drivers.  Within
    a minute or so, the device was working!  Great.
    But then, when I switched to the other USB device, the original problem reappeared.  Again, uninstalling the devices from Device Manager worked.
    But, I obviously don't want to have to uninstall the device every time I wish to use a memory stick.  Any solution?

    Hi
    Maybe try to update your chipset, sm bus controller and update your windows as well
    For update chipset and sm bus controller you can find it at HP website or your chipset manufactured

  • The recording device reported the illegal request: Unknown device

    Has anybody any idea? I am not able to output a dvd-9 (dvd + dl). there is always the message: the recording device reported the illegal request: unknown device. The layersize is ok and the dual layer brake is set.

    I don't have the exact error message with me, but that sounds similar. I bought a new DVR-115 for my Mac Pro and put the existing DVR-112 in the bottom slot. The DVR-115 worked fine for a month or so, then started getting that or a similar error. I replaced it under warranty and soon got the same thing. Then I Googled the error message an found many people having the same problem, even people with PCs. Now I just burn with the DVR-112, not worth resolving. BUT, I could be remembering the error message incorrectly, so Google and see what you get.

  • LMS 4.0.1 - missing device model

    Inventory jobs run successfully, but when running Inventory Detailed Device report, finding information missing under Chassis Model Name. Doing a MIB walk I do find Model name information is available under Standard Entitiy-MIB for the problem devices.
    This is only occuring for Wireless AP 1200 (AIR-AP1232AG-A-K9) and select IOS Routers (870, 1811, and 1841). All other devices, except unsupported ones, are reporting properly.
    I'm just a user of the system, but in talking with Administrators of the system - not finding the answer / cause / fix to resolve.
    Is there something specific that needs to be set for these type of devices in order to pick up the model information?
    Is there some update that would fix this?
    Thanks in advance.

    Due to issues at work, I have not been able to get back to this, but back now.
    Here is a screen shot of the Missing Chassis Model Name information - also attached for readability;
    Here is an excerpt of the ICServer.log that I believe is related to this;
    com.cisco.nm.xms.xdi.DeviceAccessException: SnmpRequestTimeout on 10.111.0.202 while performing SnmpGet at index = -1
    at com.cisco.nm.xms.xdi.DeviceContext.retrieveSysObjectID(DeviceContext.java:258)
    at com.cisco.nm.xms.xdi.DeviceContext.getSysObjectID(DeviceContext.java:218)
    at com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext.getSysObjectID(RMEDeviceContext.java:1067)
    at com.cisco.nm.rmeng.util.rmedaa.RMEDCFactory.createUnpopulatedDC(RMEDCFactory.java:179)
    at com.cisco.nm.rmeng.inventory.ics.util.RMEDeviceContextFactory.getDeviceContext(RMEDeviceContextFactory.java:125)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.getDeviceContext(CollectionController.java:1647)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:499)
    at java.lang.Thread.run(Thread.java:662)
    Caused by:
    com.cisco.nm.lib.snmp.futureapi.SnmpReqTimeoutException: SnmpRequestTimeout on 10.111.0.202 while performing SnmpGet at index = -1
    at com.cisco.nm.lib.snmp.futureapi.SnmpFuture.value(SnmpFuture.java:193)
    at com.cisco.nm.xms.xdi.DeviceContext.retrieveSysObjectID(DeviceContext.java:255)
    at com.cisco.nm.xms.xdi.DeviceContext.getSysObjectID(DeviceContext.java:218)
    at com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext.getSysObjectID(RMEDeviceContext.java:1067)
    at com.cisco.nm.rmeng.util.rmedaa.RMEDCFactory.createUnpopulatedDC(RMEDCFactory.java:179)
    at com.cisco.nm.rmeng.inventory.ics.util.RMEDeviceContextFactory.getDeviceContext(RMEDeviceContextFactory.java:125)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.getDeviceContext(CollectionController.java:1647)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:499)
    at java.lang.Thread.run(Thread.java:662)
    Caused by:
    com.cisco.nm.lib.snmp.futureapi.SnmpReqTimeoutException: SnmpRequestTimeout on 10.111.0.202 while performing SnmpGet at index = -1
    at com.cisco.nm.lib.snmp.futureapi.SnmpFuture.value(SnmpFuture.java:193)
    at com.cisco.nm.xms.xdi.DeviceContext.retrieveSysObjectID(DeviceContext.java:255)
    at com.cisco.nm.xms.xdi.DeviceContext.getSysObjectID(DeviceContext.java:218)
    at com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext.getSysObjectID(RMEDeviceContext.java:1067)
    at com.cisco.nm.rmeng.util.rmedaa.RMEDCFactory.createUnpopulatedDC(RMEDCFactory.java:179)
    at com.cisco.nm.rmeng.inventory.ics.util.RMEDeviceContextFactory.getDeviceContext(RMEDeviceContextFactory.java:125)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.getDeviceContext(CollectionController.java:1647)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:499)
    at java.lang.Thread.run(Thread.java:662)
    com.cisco.nm.xms.xdi.DeviceAccessException: SnmpRequestTimeout on 10.111.0.202 while performing SnmpGet at index = -1
    at com.cisco.nm.xms.xdi.DeviceContext.retrieveSysObjectID(DeviceContext.java:258)
    at com.cisco.nm.xms.xdi.DeviceContext.getSysObjectID(DeviceContext.java:218)
    at com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext.getSysObjectID(RMEDeviceContext.java:1067)
    at com.cisco.nm.rmeng.util.rmedaa.RMEDCFactory.createUnpopulatedDC(RMEDCFactory.java:179)
    at com.cisco.nm.rmeng.inventory.ics.util.RMEDeviceContextFactory.getDeviceContext(RMEDeviceContextFactory.java:125)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.getDeviceContext(CollectionController.java:1647)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:499)
    at java.lang.Thread.run(Thread.java:662)
    Caused by:
    com.cisco.nm.lib.snmp.futureapi.SnmpReqTimeoutException: SnmpRequestTimeout on 10.111.0.202 while performing SnmpGet at index = -1
    at com.cisco.nm.lib.snmp.futureapi.SnmpFuture.value(SnmpFuture.java:193)
    at com.cisco.nm.xms.xdi.DeviceContext.retrieveSysObjectID(DeviceContext.java:255)
    at com.cisco.nm.xms.xdi.DeviceContext.getSysObjectID(DeviceContext.java:218)
    at com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext.getSysObjectID(RMEDeviceContext.java:1067)
    at com.cisco.nm.rmeng.util.rmedaa.RMEDCFactory.createUnpopulatedDC(RMEDCFactory.java:179)
    at com.cisco.nm.rmeng.inventory.ics.util.RMEDeviceContextFactory.getDeviceContext(RMEDeviceContextFactory.java:125)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.getDeviceContext(CollectionController.java:1647)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:499)
    at java.lang.Thread.run(Thread.java:662)
    Caused by:
    com.cisco.nm.lib.snmp.futureapi.SnmpReqTimeoutException: SnmpRequestTimeout on 10.111.0.202 while performing SnmpGet at index = -1
    at com.cisco.nm.lib.snmp.futureapi.SnmpFuture.value(SnmpFuture.java:193)
    at com.cisco.nm.xms.xdi.DeviceContext.retrieveSysObjectID(DeviceContext.java:255)
    at com.cisco.nm.xms.xdi.DeviceContext.getSysObjectID(DeviceContext.java:218)
    at com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext.getSysObjectID(RMEDeviceContext.java:1067)
    at com.cisco.nm.rmeng.util.rmedaa.RMEDCFactory.createUnpopulatedDC(RMEDCFactory.java:179)
    at com.cisco.nm.rmeng.inventory.ics.util.RMEDeviceContextFactory.getDeviceContext(RMEDeviceContextFactory.java:125)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.getDeviceContext(CollectionController.java:1647)
    at com.cisco.nm.rmeng.inventory.ics.core.CollectionController.run(CollectionController.java:499)
    at java.lang.Thread.run(Thread.java:662)
    Let me know if there is anything else needed.
    Thank you.

  • Why is there no devices report?

    I published a landing page to BC from Muse. It has a /phone mobile option. However there is no devices report in BC. It just says "No data to display. Report statistics updated every 2 hours."
    I found one other post about this where people are saying it has never worked. Is this a bug or something that hasn't been fully developed? Pretty annoying either way.
    Thanks

    Hi,
    This was initially a reported bug #3545453 however the decision has been made to remove the feature in the next release.
    Unfortunately I do not have more details to provide on when this may return.
    Kind regards,
    -Sidney

  • IEEE 1934 devices report as being Offline in Capture Mode

    I recently found the need to capture video. I had an OHCI compliant IEEE 1934 card professionally installed. Windows recognizes the card and reports it as working properly. When I connect a Firewire device, windows recognizes a device had been attached and detached when I disconnect which indicates the cables and connections are fine.
    I have three Firewire devices, two of which are on the Device Setup list located in the Capture Preferences of Premiere 2.0. They include:
    JVC HR-DVS2U
    Panasonic AG DVX-100
    My third device is a Cannon ZR45 MC and while I understand only the ZR40 and ZR50 are listed, I figure the functionality would be so similar, that the ZR45 would have at best limited support within Premiere.
    All devices report as being Offline. I’ve read the manual and went through each step more than 4 times with each device and the conclusion is the same. Might there be a step within Windows that I need to perform first?
    Dual Pentium Xeon 2.4Ghz
    Windows XP Pro, Service Pack 2
    3 GB RAM
    Premiere 2.x

    I would like to thank everyone for taking the time to help answer and troubleshoot my problem.
    When researching the web for answers, to include Microsoft’s web site, I discovered many people had the same issues, but for different reasons. Most seemed to stem from service pack or updates received in Vista. Some derived after upgrading from XP Home to XP Pro. I kind of thought this was my issue since all my IEEE devices work with XP home on a very old Sony laptop, but not XP Pro on a rather capable workstation. In the literally hundreds of pages, posts and articles I read through, none of them helped me and according to most who have posted trouble with devices unseen by Windows or offline by any number of different editing aps, there were no fixes. My solution came quite by accident.
    I don’t know if this is typical for all OHCI compliant cards not installed by a computer manufacturer, but the one I have comes with a utility called The Switch. It enables one to use either it’s built in drivers that are used by default, or Windows drivers. When I used The Switch, the Installation Wizard auto detected the Canon, and began installing about 7 drivers at the end of which, Premiere saw and manipulated the cam. I tried the same thing for the JVC. All but one driver (T.V. Tuner) was installed, however Premiere still recognized and controlled the deck. Due to time restraints, I only tried playback, shuttle, pause and stop, but there should be no reason capture won’t work.
    I hope this helps others who are experiencing device offline issues. I urge you to post your solutions even if they are different from mine.

  • Device details for unreachable devices on PI 2.2

    I had a device fail today, got an email alarm from PI telling me. So its nice to see the tool working as it should.
    I needed to fault the device out to Cisco so I needed the serial number so I looked up the device entry in PI "Inventory/Network Device" but the device name was not a hyperlink so when I click on it all I get is the tick in the tick box.
    Surely PI will not stop me seeing device details from a device it has previously gathered the information for if the device becomes unreachable.
    I would have expected access to this information would be most useful at a time of failure.
    Am I looking in the wrong place ?, is the information still stored somewhere else ?
    regards
    Rich

    I expect you have already have the answer to your question, so just in case anybody else comes across this.
    You should still be able to access the 360 view for an unreachable device. Clicking on the IP address in the pop up should provide you with the device information gathered so far.
    Regards,
    Martin

  • VISA - unable to queue operation & device reported an input protocol error.

    To summarise I have two main questions:
    How can I clear the VISA operation queue and what causes an input protocol error during transfer?
    I am using a Tektronix AFG3022B Function Generator with latest firmware connected via USB and LabVIEW 2013 SP1 patch 2 (13.0.1f2) 32bit with NI-VISA 5.4.1.
    If I have a small timeout, say 100ms, and perform a save operation and op complete query on the device (*SAV 1;OPC?), then do up to 10 VISA reads; the first few reads time out (as expected), but then I frequently get the following error:
    -1073807305 (0xBFFF0037) VI_ERROR_INP_PROT_VIOL. "Device reported an input protocol error during transfer."
    Once this occurs, the whole VISA session seems to become unstable and lots of the read operations fail returing this error code and not the timeout error (0xBFFF0015 (VI_ERROR_TMO)).
    This only seems to happen when I do save/recall operations (either internal or to a mass storage device connected to the instrument), all other commands/queries timeout for the first few reads (as expected) then return the value. Do you think this is probably down to poor instrument firmware/hardware? Or am I using the VISA incorrectly? I would have thought that attempting to read VISA data to soon should only generate a timeout error and not a protocol error.
    Reason for small timeouts:
    Instead of setting the timeout to 4 seconds and having no way of cancelling the read operation I set the timeout to 100ms and run a for loop up to 40 times ignoring timout errors unless it's the last loop iteration. This means I can the operation within ~100ms.
    What causes the VISA protocol error? I can't find much information on it.
    Once the protocol error occurs and I keep repeating the *SAV command, I get the following error:
    -1073807303 (0xBFFF0039) VI_ERROR_IN_PROGRESS. "Unable to queue the asynchronous operation because there is already an operation in progress."
    Once this error occurs, how can I force a clear on the VISA queue without unplugging/power cycling the instrument?
    Some NI I/O trace captures attached to show what happens and test VI.
    Using LV2014 SP1
    Attachments:
    VISA problems.zip ‏38 KB

    I thought I would try to duplicate your problems, but I only have a Tektronix TDS Scope that has USB.
    I am a big fan of using *OCP? to sync instruments control and your problem is of interest to me
    This very simple write/read returns the *OPC '1' return char consistently between 175-185 ms. No problem
    Trying your short timeout with a loop, I do not get what I or you expected.
    If I run this with an adequate timeout (something well longer than the needed 185 ms) it returns in between 175-185 ms with one time through the for loop. As expected. No problem.
    BUT! If I try setting the timeout to something below the needed 175 ms like your 100ms...
    Sometimes it works but it takes over 2000 ms to return but only goes though the for loop twice.
    But sometime it does not work at all, taking well over 10 sec to exit out of the for loop with a timeout error.
    I never see the queue error that you are seeing
    How long does it take to do a simple *SAV
    I don’t think the queue error is coming from the instrument. You would have to send the instruments the SYSTEM:ERROR? Request before the instrument would report any of the instruments errors. 
    Be sure to set your Termination Char setting. I prefer to turn it off for the Writes so I control when to send it. But turn it on for the Reads
    Also I noticed from your trace files that you use the *OPC? after a *IDN?. This is not needed as you will know the *IDN? is complete when your received the string back. In fact my Tektronix scope did not like it if I sent it "*IDN?;*OPC?\n". It would not send me anything back, not even the IDN.
    Is the SAV command on your instrument so long that you need to be able to break out of the loop?
    Omar

  • Unespected device report on syslog RME 3.4 VMS

    I am monitoring the logs from a CISCO PIX 506E firewall (6.3.1)on RME 3.4 VMS. I see the logs only on the Unespected device report, when I try to get a Severity summary report from that device I can not. In the RME documentation I found that the syslog for that device, it is supported. The question is: Could I get any syslog report from that device? or not?, if I could, what also do I have to do to get them?.
    The RME is installed on the same machine that the VMS is installed. (Windows 2K Server SP3)

    First, make sure that all of the settings are the same in the configs including Logging server IP, severity, facility.
    Next, make sure that devices are in RME.
    Unexpected Device shows all the devices that are sending logging messages to CiscoWorks but are not configured in RME.
    If you see the logging messages in that report - your device may be managed by a different IP address than the one it is receiving the logging messages from. Perform a reverse NSLOOKUP to determine the IP that CiscoWorks uses for the device. Set the logging source on the device to that IP using the command: logging source-interface interface

  • Purchase History Report a Problem feature

    I was looking at my purchases and clicked the Report a Problem button, but the only thing that happened was that the button disappeared.  Odd.  Were they just joking? . . . "Ha-ha-ha, did you believe that? Just messin' with you. Bye-bye little button."
    Well, ok, they must be serious, but the button just disappeared when I clicked on it, no joke.

    I'm a novice to this community discussion board so bear with me.  I have reported problems with apps in the past and done the steps I have done above and it came up with a drop down list of selected problems you simply chose one and sent it.  This time round though I seem to have been redirected to the Apple Support screen which is a screen with multiple tutitorials, ranging from getting started in itunes, how to load apps etc, different devices I can't seem to figure out how to just report a problem.  I then choose app (which seems to be the closest choice) and I just seem to go in circles.  It's not itunes that is the problem it is the developers of the app as many others have the same problem with the app crashing my next best thing is to wait for an update for the developer to fix the bugs.  Which I hope they read the reviews left by consumers.  Thanks for your reponse though.

  • Why doesn't "report a problem" even respond?

    I purchased a TV series, by mistake the wrong language version, which I only realized once I started watching. I stopped watching and downloaded the right version. I also reported the problem, i.e. downloading what I did not intend to. Automatic response on the website is that the purchase is not eligible for refund. I understand that, I could have copied the series and made some money with it (although I think they are DRM'd anyway). But I have never received an answer to that report - other than the automatic response. Which, byt the way, I think is not in accordance with EU laws concerning remote consumer purchases. Really bad customer service. It is only 30 Euros but the principle is important. I am consdering selling all my Apple devices on eBay for this as well as terminating my iTunes account (not to mention selling the Apple shares I own). There is plenty of competition out there!

    From what you described, you never reported it to anyone, so I'm not sure why you'd expect a response.
    Go to getsupport.apple.com and follow the prompts to report it.  You'll receive a response within 24-48hrs.
    And since you're the one who made the error, I'd relax a little bit before leveling threats in a user to user forum.

Maybe you are looking for