Cisco Prime 1.3 Discovery

I noticed that Prime won't allow anything more that  255.255.240.0 networks. What is the best way to get around this....or what is the best recommendation to setup discovery....

Had the same issue and noticed that the licence count for 100 devices (Eval Limit) was consumed as soon as we added the WLC
On your page https:///webacs/welcomeAction.do#pageId=LicenseCenter_pageId look at how many are taken and if it is in violation.
We added our 500 pak upgraded, and it still didn't fix the issue when re-syncing. We had to remove the device and re-add.
This is now resolved for us.

Similar Messages

  • Cisco Prime LMS - Device discovery

    How do you configure Cisco Prime LMS Device Discovery, so that you can have two credentials sets for specific "special devices" (host based statement) and one for the of the devices (global subnet statement)?
    Thanks in advance.

    Hi,
    Here is the link to the document containing the detailed steps regarding Credential Sets.
    After defining your sets then set up Credential Set Policies.
    Thanks!

  • Device discovery in Cisco Prime LMS 4.1

    Hi,
    im using CISCO PRIME LMS 4.1 for manage my network, i ran a device discovery job using a ping sweep on the ip ranges of my network, ie 192.168.1.0/24, 192.168.2.0/24 and so on... the discovery found all my devices, but it discovered duplicate devices with illegal ip Addresses, ie
    ip                                    device    
    192.168.1.255               S1
    192.168.2.0                    S1
    192.168.2.1                    S1 (the real address)
    all in reachable status.
    i dont undestad why the program adds that repeated illegal addresses.. someone can help me with that issue??
    how can i run the device discovery to avoid this problem?
    Many Thanks.

    Julio,
    Don't let LMS decide on what IP address it will manage the device.
    For example, let LMS do a lookup of the sysname in DNS, then it will use the IP address coming back from the DNS as management IP.
    This is what I do to avoid this.
    But I also feel that LMS should be bright enough to never manage the same device twice. I think Campus DFM or RME will eventually figure out the 2 devices are the same, but they can't "fix" what is wrong in the DCR.
    Cheers,
    Michel

  • WLC 2504 in Cisco Prime Infrastructure 1.2

    Trying to add Cisco 2504 Wireless Controller, Software Version 7.3.101.0, to Cisco Prime Infrastructure
    1.2 (1.2.0.103), License Evaluation, with no success.
    When using Discovery, Discovery Job show Credential Errors: "Error occured due to invalid SNMP credential"
    When Add Device from Device Work Center I get:
    Reachability is "Unknown", Device Type is empty, Collection Status is "Managed with Warnings", with message "SNMP Failure: No Response for SNMP Get request.", Collection Time is empty.
    I've tried with both snmp v2 and v3.
    I've tried to lower "Maximum VarBinds per Get PDU" to 10 or 20, cause I've read similar problem in NCS.

    I solved the same problem 5min ago.!
    select the device and press syc ..that helped me ...

  • Cisco Prime Infra 2.2 + Third Party Inventory and configuration backup

    Hi All,
     I am having a doubt related to Cisco prime solution capability to do a discovery and config backup for non-cisco devices. 
    Requirement is to use Cisco prime to do a discovery, inventory and take configuration backup for non-cisco devices. Is it something possible out of the box ?
    If not possible out of the box, is there any method to do that using any custom API ?
    Can we monitor 3rd party( Non-cisco) devices using Cisco Prime 2.2 ?
    Skr

    Hi,
    Below is supported-device list, check if your device is listed there.
    http://www.cisco.com/c/en/us/support/cloud-systems-management/prime-infrastructure/products-device-support-tables-list.html
    - Ashok
    Please rate the post or mark as correct answer as it will help others looking for similar information

  • Cisco prime 2.2.0 "Telnet/SSH : Unreachable"

    Hi,
    I've installed the Cisco Prime 2.2.0 OVA (VMware) and ran discovery with a Credential Profile.
    some of the device has discovered with complete state and some with Partial Collection Failure state.
    when trying to edit the device (under network inventory) and verify credentials i'm getting the above error "Telnet/SSH : Unreachable", but when SSH from the Cisco Prime CLI with the same credentials all works just fine.
    %SSH-5-SSH2_SESSION: SSH2 Session request from X.X.X.X (tty = 1) using crypto cipher '', hmac '' Failed
    please help...
    10x
    Eyal

    Hi Afroz,
    All of my net devices use AAA for login.
    I'm using credentials profile to discover my devices and some of them has discovered as they should and some of them are partialy discover with the Cisco Prime log it with CLI/ssh issue.
    But when I'm SSH to the partialy discovered device via the Cisco Prime CLI with the same credentials as configured at the credential profile, I'm able to login with no issue.
    Please note - while I'm editing the partialy discovered device and testing the credential via the Prime GUI, it display the error message "Telnet/SSH : Unreachable" - and the device log meeage is %SSH-5-SSH2_SESSION: SSH2 Session request from X.X.X.X (tty = 1) using crypto cipher '', hmac '' Failed.
    What does it mean?
    10x
    Eyal

  • Cisco Prime 2.0 - CLI credential

    Hi PI Experts,
    Is CLI credential mandatory on Cisco Prime?
    What would happen if no dedicated CLI credential were configured on Prime to access Cisco network devices?
    Right now we use TACACS+ to login to Cisco switches and routers and use Radius to login to PI.
    However, our security policy prevents us from either creating a AD account on AD servers or creating a local TACACS+ user account on ACS server for PI appliance.
    So, when we do device discovery, if we want to use SSH/Telnet, we need to put in our own AD user credentials, then remove them after the discovery is done.
    Thanks
    Cedar

    Hi Ceder,
    What would happen if no dedicated CLI credential were configured on Prime to access Cisco network devices?
    why Telenet credentilas are required :
    Telnet Credential
    you can specify the Telnet credentials during discovery so that Prime  Infrastructure can collect the device configurations and fully manage  the devices. If you do not specify Telnet credentials in the discovery  settings, Prime Infrastructure discovers the devices but is unable to  manage the device until you specify the Telnet credentials.
    In  case you are using SSH  on your devices:
    SSH Credential
    For full device support via SSH, you must use SSHv2 with a 1024 bit key. You can configure SSH before running discovery.
    Telnet\SSH , credentilas would be required later on as well to Fetch the config , to push any template on the device etc..
    Thanks-
    Afroz
    [Do rate the useful post]
    ****Ratings Encourages Contributors ****

  • Cisco Prime LMS 4.1 - Do access points use up a node count license?

    Hi Everyone,
    I wish to purchase Cisco Prime LMS 4.1, particularly Cisco part # R-LMS-4.1-500-K9 which support 500 Cisco nodes.
    We have about 360 Cisco switches/routers/ASA/FWs/WLCs so the 500 nodes license would seem to suffice for now & for future growth.
    We also have about 200 lightweight APs that are managed & monitored by our WLC/WCS/Navigator environment.
    According to the device support documentation for LMS, it supports and I assume will auto-discover these APs.
    Does that mean these APs will use up node licenses on LMS even though management of the APs is done by WLC/WCS?  If so is there an easy way to suppress discovery of APs by LMS so we don’t have to purchase extra node licenses for LMS?  Or, does LMS offer additional support features for wireless APs not already offered by WLC/WCS/Navigator?
    Just trying to understand how many network node licenses for LMS I have to purchase.
    Thanks in advance for your help,
    Ian.

    Thanks but I just heard back from my Cisco SE and he assures me that an AP will NOT use up a license.
    I've asked him to verify his answer for me.
    Is your answer based on real world expereince (the best there is)?  That is, are you running Prime LMS 4.1 and does it indeed use up a license for each light-weight AP it discovers & manages?
    Thanks for mentioning options 1-3 but I do not wish to employ any of them.  I don't mind buying the additional licenses for APs ... I just need to know if I have to or not.
    Ian.

  • Cisco Prime LMS device unreachable dont know why

    Hi
    Currently running Cisco Prime LMS v4.2
    I am trying to get some Nexus 7K Switches to work and become reachable.
    They are running  kickstart: version 6.2(2)
                                 system:    version 6.2(2)
    Now as far as I can see i have 2 identical switches but one is unreachable and the other is reachable.
    When i use my snmp tester they both work with the correct V3 auth/priv passwords and the correct ssh
    works on the switches.
    When i go to monitor/Troubleshooting Tools/Troubleshooting Workflows
    Then for the non working one  i get the following fails.... 
    Device Information   Device availability  x
    Collector Status
    Data Collection  Failure
    User Tracking    Failure
    Fault discovery   Failure
    On the working one The above all are a Success.
    Also
    Reachability Details
    Both ping and traceroute work fine on both switches 
    For the life of me I cannot see any difference in the configuration of the two devices.
    Has anyone come across this before ?
    I have attached a copy of the snmp config.
    Thanks
    Steve

    What is the server OS? Windows/Linux or Unix?
    From the server to ping and poll device for SNMP and see if both device works fine?
    SNMP walk is available under :
    Windows : NMSROOT/objects/jt/bin
    Linux/unnix/: /opt/SCOpx/objects/jt/bin
    Example:
    NSROOT/objects/jt/bin/snmpwalk -v2c -c public <ip_add> <OID>
    Try to configure the problematic device for SNMP v2 and try to add it from there and test if it works fine.
    -Thanks
    Vinod

  • Cisco Prime does not update devices in "Device Work Center"

    Hi everyone.
    I have a problem that is bugging me a lot.
    I'm working in Cisco Prime 2.0 and we have a big problem.
    If I run a discovery and find all a lot of switches, the switches is discovered and are fully managed via SSH and SNMP.
    We are using both 2960S, 2960x and a lot of old 2950:s.
    We are replacing all 2950:s to some new 2960 model.
    The big problem is that when we replace the old 2950:s we reuse the same IP-address (so our customly built programs can find them again), Cisco Prime DOES NOT update the model of the switches. The switches are still in the Device Work Center and are still in recognized as a 2950.
    If I mark the switch to view more info in Device Work Center the Unique Device Identifier says that it is a new 2960s/x but the model is still recognized as a 2950 so Prime can obviously find a manage the switch and update "some" info, but not the device itself.
    Does someone have the same problem or do I need to delete all 2950:s and do a new discovery so Prime understand?
    EDIT
    I have now an example.
    Please look at the image.

    Hi,
    I ran into same issue,Yes this is known issue,there is a open defect id and is fixed in upcoming releases.
    I deleted existing devices and rediscovered,but note you will loose all your configurations related to existing deive model.
    Regards

  • New installation of Cisco prime Infrastructure 1.2

    Hi,
    We installed Cisco prime infrastructure 1.2 and discovered our entire LAN swtiches and core L3 Switches.
    In Cisco Prime, we are getting information related to Device and IOS. But intreface ulitilzation information are not avilable.
    we used SNMPv2 RW string and and SSH username for discovery.
    How to get the interface ulitization data ?

    Under Administration > System Settings, then select Monitoring Settings.
    i checked the two options
    Auto monitoring
    Enable deduplication
    But after refresh it is show uncheck, i tried in Google Chrome and Firefox.
    Is this cause the issue of not polling interface netflow???

  • Device Reachable but Unmanaged in Cisco Prime Infrastructure 1.3

    Hi,
    I am running the Eval version of cisco Prime Infrastructure 1.3
    I tried running discovery for WLC and it worked fine where all the controllers were discovered.
    But when i try to discover a Switch, the reachability tab says Reachable but in Collection Status tab it shows Unmanaged.
    When i click on the Unmanaged tab it says " Pre-collection check failed because: "
    I have configured the SNMP correctly.
    Does anyone know why is this happening.
    All the help is greatly appreciated.                   

    Had the same issue and noticed that the licence count for 100 devices (Eval Limit) was consumed as soon as we added the WLC
    On your page https:///webacs/welcomeAction.do#pageId=LicenseCenter_pageId look at how many are taken and if it is in violation.
    We added our 500 pak upgraded, and it still didn't fix the issue when re-syncing. We had to remove the device and re-add.
    This is now resolved for us.

  • Trouble With Cisco Prime Infrastructure 1.3

    Hi,
    I have installed the Evaluation Version Cisco Prime Infrastructure 1.3.
    There are a few problems that i am facing;
    I am trying to push a simple configuration to WLC using Prime Infrastructure. But it is failing as PI doesnot have RW SNMP access.
    My question is that can I use PI to push configs without using SNMP. Like do it using ftp or something.
    Also do the Wired Devices also need SNMP RW access on PI's part.
    2. I tried running discovery for WLC and it worked fine where all the controllers were discovered. But when I try to discover a Switch, the reachability tab says Reachable but in Collection Status tab it shows Unmanaged. When I click on the Unmanaged tab it says " Pre-collection check failed because: ". I have configured the SNMP correctly.
    3. I have the CAD files for all the maps in our environment but when I try to upload it to Prime it converts it into GIF, so the maps are uploaded as plain image with no knowledge of walls and obstacles.
    So we would have to add the walls and obstacles by ourselves. Is there any way it can automatically pick up on the walls and obstacles and thus provide a better way for predicting RF profiles.
    All your help is greatly appreciated.

    TAC Case! Sounds like a bug to me...
    Sent from Cisco Technical Support iPad App

  • Cisco Prime Infrastructure 2.0 - Third Party NetFlow

    Hi,
    is it possible to collect on the Cisco Prime Infrastructure 2.0 NetFlows from Third Party Devices, like a SonicWALL Firewall?
    I mean it is possible to poll SNMP informations from a third party device, so maybe it is also possible to get the NetFlow from this Device?
    Best Regards,
    Sven K.
    Sent from Cisco Technical Support iPad App

    Hi Sven,
    As per my understanding for 3rd party Only below thing are supported:
    The following support level is available with Prime Infrastructure :
    • Auto Discovery of a 3rd party Device
    • Basic Inventory collection
    • Basic lifecycle management of 3rd party device
    • Ability to show traps and syslog for 3rd party devices
    • Device reachability status polling
    • Ability to load new MIBs & to create new monitoring templates
    • For both Cisco and any SNMP device
    More info is available in the link given below:
    http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/1.2/release/notes/cpi_rn.html#wp75765
    Thanks-
    Afroz
    [Do rate the useful post]

  • Cisco Prime Infrastructure version 1.2

    Hello All,
    I want to create a filter for the wireless devices so that they are not automatically get discovered during the discovery process of Cisco Prime. so request you to please provide link/solution through which i can create a XML file which i have to upload on the Cisco Prime server.
    Regards,
    ADM

    Hi Anshuman,
    Maybe we can both learn something here.
    It was my understanding that Wireless Lan Controllers don't get "auto-discovered" during the discovery process.
    I talked with a colleague on the team and that was his impression too.
    Keep in mind--- as WLCs are added, the APs come in when the respective WLC is added.
    thanks, rob

Maybe you are looking for