Prime infrastructure display issues

dear all,
I have some display problems with Prime 1.3 .. and the same with 1.2 :-)
for example the Discover Devices doesn't display the menu where I can click to launch the quick discovery.It's the case in classic theme but not in lifecycle theme.
It happens with IE with Chrome frame, with firefox and Chrome ..
any idea?
Attached the print screen and what it is supposed to be !!!
thanks in advance,
regards,
vincent

Here is my PI 1.3
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

Similar Messages

Cisco Prime Infrastructure MESH LINK ISSUE

Hi,
a Customer of us has a trouble with cisco Prime Infrastructure 1.2.0.12 and AP mesh link.
There is an huge database ( i suppose the issue can be here ) and when we display some map ( each floor has about 6 RAP and 24 MAP ) we cannot see the MESH information and link draw.
The only way to dipley them is to disable "refresh from network": this way I'm able to show these link..... until a click before.
What i noticied when all was working fine, after i click to some floor:
1) the software started to show the map with normal color and no mesh info displayed ( just ap and coverage cloud )
2) after few time ( less than 1 second ) the map was becoming a little bit lighter and the mesh info was merged to the map
We are missini the second step
Anyone had the same issue ?
best regards
Luigi
PS: I opened a case with WCS version 6.0 ( same issue ) but, after some months, no risult. The last version working fine was WCS 5.2

Just to add some more informations:
- disabling "refreshj from network" ( building properties ) the link and mesh info are showed
- while I'm on a floor, after some refresh, i loose the mesh link draw and, if i click on an AP, i loose also mesh info in the popup. It' s like, after some refresh, the AP are no more recognized as Mesh ( !?!? )
regards
Luigi

Prime Infrastructure 2.1 Client Statistic Report Issues

Hello Community,
I hope you can help with a couple of issues I am seeing on Prime Infrastructure 2.1, running an evaluation 60 day license.
My PI 2.1 build is currently managing a WLC 5508 running 7.4.121.0, which has been added successfully. No configuration changes were applied to the WLCs, other than SNMP community. No AVC or medianet configuration is applied.
When looking in the 'Operate>Client and Users' dashboard; I can see connected clients and if I select one of them, I can see further details like session, security and client statistics (showing traffic and 802.11 metrics). These are the table views that show current values, however, further down I see graphs but they do not contain any information for RSSI, SNR or traffic sent & received (packets or bytes).
Question: Should I see this information under an evaluation license and if so, what could be stopping it?
Also, when I run the reports 'Report>Report Launch Pad' and select 'Client>Client Traffic' or 'Client>Client Throughput' the resulting report contains 0 bps, when I select 'Report By' AP by Floor Area. I have created a single floor area and placed three access points into it.
Out of interest if I do a report of the same type using 'Report By' All or AP by Controller, I do see traffic graphs for 3 out of 333 access points. Just not the access points that are in my floor area. Also the amount of traffic utilization is tiny (less than a kbps) for a WLC with 800 users.
For a 'Client>Client Count' report using AP by Floor Area, I do see the client numbers connected to the WLC/APs in my configured floor area.
Question: Should I see reports for client traffic and throughput under an evaluation license for floor areas and if so, what could be stopping it?
I have checked the background task and the 'Client Statistics' task is enabled and run time is being updated.
Kind regards,
Ian

Hi,
here is an update:
There are more than one Report you need to start to get data for Device, FAN, Power Supply, Module - look at these reports:
Report > Report Launch Pad > Device > Inventory
Report > Report Lauch Pad > Device > Wired Detailed Device Inventory
Report > Report Lauch Pad > Device > Wired Module Detail > Wired Module Detail Report Details
SFPs and GBICs cannot be reported til now - there are working on it.
br,
chris

Prime Infrastructure 2.1 - Fan-Failure SNMP-Trap Issue

Hello,
I am facing the following Prime Infrastructure (v2.1) issue:
- A Fan-Failure SNMP-Trap from a Cisco 3650 switch doesn't appear on Prime, but a Link-Failure from the same switch does.
- The both events appears on Prime with Syslog.
- The command "snmp-server enable traps envmon fan shutdown supply temperature status" is set up.
- The switch is in "Managed" state in PI, I have checked the ACL at the "snmp-server community" command, it is okay.
- I have set up an SNMP-Trace for the switch on PI, but only "SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex" arrived. Please find the log below.
07/02/14 12:39:53.211 TRACE [presence-9] [] Adding attributes for object Fan3KStats[151206060_,1012]
07/02/14 12:39:53.211 TRACE [presence-9] [] Index name : fanIndex
07/02/14 12:39:53.211 TRACE [presence-9] [] Index Value : 1012
07/02/14 12:39:53.211 TRACE [presence-9] [] Device MIB table index: .1012
07/02/14 12:39:53.211 TRACE [presence-9] [] MIB table row index: .1012
07/02/14 12:39:53.211 TRACE [presence-9] []     OID for : fanIndex = 1.3.6.1.2.1.47.1.1.1.1.1.1012
07/02/14 12:39:53.211 TRACE [presence-9] []     OID for : fanOperStatus = 1.3.6.1.4.1.9.9.13.1.4.1.3.1012
07/02/14 12:39:53.211 TRACE [presence-9] [] Get fragment
07/02/14 12:39:53.211 TRACE [presence-9] [] Creating PDU: Get
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.2.1.47.1.1.1.1.1.1010
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.4.1.9.9.13.1.4.1.3.1010
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.2.1.47.1.1.1.1.1.1011
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.4.1.9.9.13.1.4.1.3.1011
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.2.1.47.1.1.1.1.1.1012
07/02/14 12:39:53.211 TRACE [presence-9] []     VarBind OID=1.3.6.1.4.1.9.9.13.1.4.1.3.1012
07/02/14 12:39:53.218 TRACE [presence-9] [] Error Status: 0
07/02/14 12:39:53.218 TRACE [presence-9] [] Error index: 0
07/02/14 12:39:53.218 TRACE [presence-9] [] SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex
07/02/14 12:39:53.218 TRACE [presence-9] []     Setting attribute: fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] []     SnmpInt Value : ?
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, storing result, class=com.cisco.server.managedobjects.bridge.Fan3KStats, attr=fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] [] SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex
07/02/14 12:39:53.218 TRACE [presence-9] []     Setting attribute: fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] []     SnmpInt Value : ?
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, storing result, class=com.cisco.server.managedobjects.bridge.Fan3KStats, attr=fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] [] SNMP Null was returned for class com.cisco.server.managedobjects.bridge.Fan3KStats attribute fanIndex
07/02/14 12:39:53.218 TRACE [presence-9] []     Setting attribute: fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] []     SnmpInt Value : ?
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, storing result, class=com.cisco.server.managedobjects.bridge.Fan3KStats, attr=fanOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes, assembling attributes
07/02/14 12:39:53.218 TRACE [presence-9] []     MIB lookup, OID for: powerSupplyIndex = 1.3.6.1.2.1.47.1.1.1.1.1
07/02/14 12:39:53.218 TRACE [presence-9] []     GetMultiAttributes needs class=com.cisco.server.managedobjects.bridge.PowerSupply3kStats, field=powerSupplyIndex
07/02/14 12:39:53.218 TRACE [presence-9] []     MIB lookup, OID for: powerSupplyOperStatus = 1.3.6.1.4.1.9.9.13.1.5.1.3
07/02/14 12:39:53.218 TRACE [presence-9] []     GetMultiAttributes needs class=com.cisco.server.managedobjects.bridge.PowerSupply3kStats, field=powerSupplyOperStatus
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes invoked
07/02/14 12:39:53.218 TRACE [presence-9] [] GetMultiAttributes building OIDs for next PDU
07/02/14 12:39:53.218 TRACE [presence-9] [] Adding attributes for object PowerSupply3kStats[151206060_,1009]
- The switch sends the SNMP Trap, based on the followings:
Jul 7 13:38:30 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:30 UTC: %PLATFORM_THERMAL-6-FRU_FAN_OIR: Switch 1: System fan 1 removed
Jul 7 13:38:30 UTC: %PLATFORM_THERMAL-1-FRU_FAN_NOT_PRESENT: Switch 1: System fan 1 not present
Jul 7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:30 UTC: SNMP: V2 Trap, reqid 33202, errstat 0, erridx 0
sysUpTime.0 = 576753333
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
ciscoEnvMonFanStatusEntry.3.1010 = 5
Jul 7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:30 UTC: SNMP: V2 Trap, reqid 33203, errstat 0, erridx 0
sysUpTime.0 = 576753333
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
ciscoEnvMonFanStatusEntry.3.1010 = 5
Jul 7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:30 UTC: SNMP: V2 Trap, reqid 33204, errstat 0, erridx 0
sysUpTime.0 = 576753333
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
ciscoEnvMonFanStatusEntry.3.1010 = 5
Jul 7 13:38:30 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:30 UTC: SNMP: V2 Trap, reqid 33205, errstat 0, erridx 0
sysUpTime.0 = 576753333
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, NotExist
ciscoEnvMonFanStatusEntry.3.1010 = 5
Jul 7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:31 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:45 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:51 UTC: %PLATFORM_THERMAL-6-FRU_FAN_OIR: Switch 1: System fan 1 inserted
Jul 7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:54 UTC: SNMP: V2 Trap, reqid 33206, errstat 0, erridx 0
sysUpTime.0 = 576755733
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
ciscoEnvMonFanStatusEntry.3.1010 = 1
Jul 7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:54 UTC: SNMP: V2 Trap, reqid 33207, errstat 0, erridx 0
sysUpTime.0 = 576755733
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
ciscoEnvMonFanStatusEntry.3.1010 = 1
Jul 7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:54 UTC: SNMP: V2 Trap, reqid 33208, errstat 0, erridx 0
sysUpTime.0 = 576755733
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
ciscoEnvMonFanStatusEntry.3.1010 = 1
Jul 7 13:38:54 UTC: SNMP: Queuing packet to IP_ADDRESS
Jul 7 13:38:54 UTC: SNMP: V2 Trap, reqid 33209, errstat 0, erridx 0
sysUpTime.0 = 576755733
snmpTrapOID.0 = ciscoEnvMonMIBNotifications.8
ciscoEnvMonFanStatusEntry.2.1010 = Switch 1 - FAN 1, Normal
ciscoEnvMonFanStatusEntry.3.1010 = 1
Jul 7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
Jul 7 13:38:55 UTC: SNMP: Packet sent via UDP to IP_ADDRESS
It seems like PI and the switch doesn't understand each other concerning the fan...
Thanks for any ideas, comments and feedbacks,
Csaba

I have the very same problem.
The switch has a power supply error (one of the two is down). There is the syslog message in PI about it, but no event has created, so nor alarm is there as well.
When I check the status of the switch in the Device Work Center, and choose the Environment in Device Details I can see that PI has not realized the power supply error.
However when I click on the Sync for this very device the power supply status is updated, but still no event or alarm.
This is the case with the FANs as well.

Cisco Prime Infrastructure patch 2.1.1 - HA issue

Hello,
I have a problem with the Cisco Prime Infrastructure patched to version 2.1.1. I did exactly what Installation Guidelines say:
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-1-1/release/notes/cpi_rn.html
– Install the Prime Infrastructure 2.1.1 patch by using the Administration > Software Updates page on the primary server.
– Restart the primary server.
– Verify that the patch installation is complete. If you find the installation complete, decommission and reinstall the secondary server and add it back to the primary server.
I reinstalled HA server and I'm trying to add it to HA but I get "Failed to authenticate - Primary(xx.xx.xx.xx) and Secondary(xx.xx.xx.xy) PI version does not match"
Can you help me with that? What I'm doing wrong? or maybe this patch is not prepared to work in HA mode?
Regards

Symptom:
The installation instructions of PI 2.1.1 patch in a High Availability environment are not accurate and following these steps will result in the inability to re-pair the Primary and Secondary servers.
Conditions:
If the instructions are followed, then when the user attempts to re-pair the servers, an error will be encountered:
"High Availability Registration Failed - Failed to authenticate - Primary (x.x.x.1) and Secondary (x.x.x.2) PI version does not match".
Instead, the following steps have proved to work correctly:
1. Upload and install patch on primary.
2. Upload and install patch on secondary.
3. Stop NCS services on secondary
4. Stop NCS services on primary
5. Start services on secondary
6. Start services on primary
7. Re-pair HA servers from primary
Workaround:
Workaround 1:
On the secondary, go under root and issue:
# cd /opt/CSCOlumos/bin/
# ./hamode.sh primary
Answer 'yes' when prompted.
Go to admin user and execute
# ncs stop
After the services are stopped:
# ncs start
When the services are back up, login to the secondary GUI as you would login to a primary server
Go under Administration > Software update, upload the patch and install it.
Go to admin user and execute
# ncs stop
After the services are stopped:
# ncs start
When the services are up, go under root and issue:
# cd /opt/CSCOlumos/bin/
# ./hamode.sh secondary
Answer 'yes' when prompted.
Go to admin user and execute
# ncs stop
After the services are stopped:
# ncs start
After the message that services started successfully on the secondary, initiate a new High Availability configuration from the primary. Now the synchronization between the two servers should succeed.
Workaround 2:
Redeploy or reinstall the Primary server, restore the backup which was taken prior to applying the patch, reconfigure the High Availability and continue with the steps described in the Conditions section.
Further Problem Description:
Release Notes have been updated with more precise instructions.
Known Affected Releases:
(1)
2.1(0.0.85)

Configure the syslog of ASA 5512-X for display on Cisco Prime Infrastructure 2.1

Hi, I'm working on implementing the Cisco Prime Infrastructure 2.1 and want to display the syslog about ASA5512-X with Software Version 9.2.
What would be the procedure for configuring?
Thanks in advance.

Hi,
Enable "logging host x.x.x.x " command to enable logging
check the below link:
http://www.cisco.com/c/en/us/td/docs/security/asa/asa91/configuration/general/asa_91_general_config/monitor_syslog.html#68764
FYI: Prime Infrastructure support only SEV 0,1,2 syslogs as of now.
Operate > alarm and events > syslogs
Thanks-
Afroz
****Ratings Encourages Contributors *****

Cisco Prime Infrastructure 1.2 and Aironet 1250 + VSS issues

Hi,
I am new to the NCS implementations and configurations. I have one very specific case with Cisco Prime Infrastructure 1.2 and autonomnous APs and several issues with Cisco VSS on 6500 switches.
So here is the version from Prime:
NCS/admin# show version
Cisco Application Deployment Engine OS Release: 2.0
ADE-OS Build Version: 2.0.1.038
ADE-OS System Architecture: x86_64
Copyright (c) 2005-2010 by Cisco Systems, Inc.
All rights reserved.
Hostname: NCS
Version information of installed applications
Cisco Prime Network Control System
Version : 1.2.1.012
IOS version on our APs (which are autonomnous) is:
AP-N-1>show ver
Cisco IOS Software, C1250 Software (C1250-K9W7-M), Version 12.4(25d)JA1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Thu 11-Aug-11 03:23 by prod_rel_team
Well the issue what we have now is that access point has been added but its not recognized by the NCS prime. I have tried all three versions of SNMP but I get the same result. The SNMP configuration is valid since I use the same for my switching infrastructure. When I enter "debug snmp packets" and "terminal monitor" I can see the SNMP communication between Prime and Aironet 1250 which is standalone.
When I switch to Lifecycle theme and go to Operate > Device Monitor Center I see all devices I have added. The Aironet 1250 is reachable but under collection status I get Managed with Warnings. When I hover over with my mouse I get "None available".
I have successfully added my switching infrastructure in total, which is operating perfectly for Catalyst 2960/3650/3750/4500 series but for 6500 under VSS I have some warnings. The device is recognized by the system which is excellent and all is operational. I get the following errors under Collection Status:
feature_sensor
SNMP request timed out
feature_powerSupplyFanStatus-6k
SNMP request timed out
IdentityCapability
The device is unreachable.
feature_flashdevice
SNMP request timed out
sam_ipsla_feature
The device is unreachable.
What can be done to resolve these issues ? I have attached a screenshot of this particular issue. The affected access point is 172.16.165.241.
Predrag Petrovic

Hi rajeeshp,
Currently I am not allowed to upgrade it because of internal procedures involved in upgrading a specific piece of software (obtaining permissions from various departments). Is it free to upgrade from 1.2 to 1.3 or there is a specific charge for that.
Predrag Petrovic

Cisco prime infrastructure 1.1 issue

hi：
i purchase a R-PI-1.1-K9 with R-PI-1.1-100-K9,but now i find the cisco website can't download Prime infrastructure 1.1 anywhare,only 1.2 and above version exist.but the device base licences(R-PI-1.1-100-K9) is based RI version 1.1.how do we resolve this issue.somebody tell me that R-PI-1.1-100-K9 can use in prime infrastructure 1.2 ,anyone can help me and tell me how to use it and give me the step by step guide,thanks very well.
jerry

A 1.1 license file should work with PI 1.2. See the note at the bottom of Table 3 here.
Hopefully your product was ordered with Software ApplicationSupport with Upgrade (SASU) option. That will further entitle you to upgrade to PI 1.3 and, soon, to PI 2.0. Each release ins incrementally more functional and many bug fixes are incorporated.

CISCO PRIME INFRASTRUCTURE 1.2 CONFIG ISSUE

hello all,
this is my fist time running a cisco prime infrastructure1.2 but it seem not to be working properly as i have errors on it,
I had issues from the very begining and had to write erase the config but the appliance only boots to a blank screen wit a cursor.
can anyone advice on how to restore it back to initial setup
and please whats the effect of the RESET button on the device.
thanks

I don't know if this has been fixed in 2.0 or not. By the looks of the bug it hasn't. However, there is a workaround-
https://tools.cisco.com/bugsearch/search?kw=prime%20infrastructure%20copy%20run%20start&pf=prdNm&sb=anfr&srtBy=byRel&bt=custV
BugID
CSCuf89957
Prime Infrastructure - No option to save running config to startup
Conditions:
Prime Infrastructure 1.2/1.3
Workaround:
Create a Configuration Template that runs either:
"do write mem"
Or for devices which no longer support "write mem", use:
"file prompt quiet
do copy run start
no file prompt quiet"

Prime Infrastructure 2.0 Assurance issue

Hi together,
I have a problem with our Prime Infrastructure 2.0 regarding the assurance features.
The appliance can only handle flows exported from our WLAN controller, but not from any wired device (neither standard netflow nor flexible netflow!).
Flows are received correctly on port 9991 on the PI appliance, I validated that via tcpdump. But the sending devices are not listed on "data sources".
Has anyone experienced the same problems, or even has a solution for the problem explained?
Regards
Sebastian

we need to have Assurance license for NAM to work with PI 2.0. have you installed that ?
Assurance License: Provides access to the Assurance feature set, which provides end-to-end network visibility of application and service performance to help ensure end-user quality of experience. The Assurance feature set also provides the ability to manage and aggregate data and views across multiple Cisco Prime Network Analysis Modules (NAMs). The Assurance license is based on the number of managed NetFlow-enabled interfaces. Assurance licenses are available in bundle sizes of 15, 50, 100, 500, 1000, and 5000 NetFlow-enabled interfaces. The 15 interface license has a restriction that allows you to manage only up to 5 NAMs, whereas the other Assurance license bundles do not place a restriction on the number of NAMs that you can manage. The 15 interface license can only be used standalone and not combined with the Lifecycle licenses. You need to purchase a 50 interface Assurance license or larger to use with other Cisco Prime Infrastructure feature licenses.
Thanks-
Afroz
[Do rate the useful post]

Cisco Prime infrastructure 1.2.1.012 -- HA issue

Hi All
I will explain the background before, our customer using Cisco Prime Infrastructure 1.2.1.012 and do HA. However I got error message wcss1 (in attaced file) from HA configuration. (First I had done HA configuration before and it worked. But I get error message wcss1 after i tested failover on cisco prime). I found bug case CSCud12229 that is same error message. But i still confuse with work around "Workaround:Change the database mode to Read-Write by executing query ?alter database open? or execute the shell script - /opt/CSCOlumos/bin/recover_HADeadLock.sh" anyone understand please help.
And another option I tried to upgrade with version 1.3 also but it have a bug no CSCud80157. It is the problem with HA registration fial so, i would like to ask you all that if i need to do HA on Cisco Prime infrastructure which version i should to install ? coz I saw 1.2 or 1.3 also have a bug with HA
Thanks
V

Hi rajeeshp,
Currently I am not allowed to upgrade it because of internal procedures involved in upgrading a specific piece of software (obtaining permissions from various departments). Is it free to upgrade from 1.2 to 1.3 or there is a specific charge for that.
Predrag Petrovic

Prime Infrastructure v1.3 -- Boot fails, displays debug info

Prime website stopped responding so I logged onto the console (VM) and it had these debug errors on it. I rebooted and received same thing. This happened on a previous install as well.
However, I can SSH to the appliance, but the website doesn't load.
It's currently running on a VMware ESXI v5.0 host. The VM was setup using the PI-VA-1.3.0.20-medium.ova file. It was working fine since Friday, then after a little bit of using it this morning it crashed. It was managing three wireless controllers.

Hi Itregistrations:
The lines depicted are not actual "debugs" as if something had been turned on, they're actually messages thrown to the console by the Linux daemon whose name is "debugd" or debug daemon, that's watching what's going on as the Prime Infrastructure service starts up. They're not helpful at all in diagnosing a problem, but they will stay on screen a long, long time while the service is in the process of starting. Once it does completely start, a login prompt should appear.
What is helpful is connecting to an SSH session, checking the output of "ncs status" to know which of the listed services are running or stopped.
Also, a set of logs generated by running the command "backup-logs repository " is helpful. Logs always help, particularly the hm-0-0.log file that tells what the "mother hen" Health Monitor service encounters as it tries to start up all the subservices. Depending on which subservice is having trouble, the log of that subservice would be the next source of help. For example, if Health Monitor tells the database server to start, but the database server doesn't, one would want to check the dbadmin-0-0.log to see why the database server disobeyed Health Monitor.

Prime Infrastructure issues with collection, dscp, mos, etc

We have a virtual Prime Infrastructure appliance installed. It currently shows collection status managed with warnings for several devices, i.e. Nexus 7k's, cat 3750x. cat 3850x. It is not all stacks though, most are collected accurately only a few are not showing up.
All four of my Nexus 7k's are not collected accurately.
Also when I goto Detail/Voice-video dashboards, I do not get any MOS, DSCP, voice call, IPSLA stats etc etc
Just for clarification we use Microsoft Lync for communications with Polycom phones using dscp 46, so perhaps it is not even possible but I wouod think Prime would be polling off of traffic on the port and look for DSCP values.
I am able to poll IPSLA and mos scores via PRTG.
on many of my ports in Detail Dashboards/Interface "polling enabled" shows as "no" I am not sure why it shows up as no but there is some date being polled.
Is there something simple I am missing? TAC does not seem to know the product and I am unable to find a decent manual. So I am at a loss.
Thanks in advance!

Bump

Polling issue on Prime Infrastructure

Hello all, we are seeing SNMP connection failure as a status for Last Inventory Collection when looking at our monitored devices in PI 2.2. More information is provided stating what failed (various reasons like not collecting CDP information) and possible causes. Possible causes only list an SNMP time and it states to verify the device credentials (which we have done) and verify SNMP response speed from the device. How do I do that? And is there a way to tune PI so it will wait longer for a response before timing out the request?
Please advise and thanks for your help.
Jeff

You can adjust the SNMP settings (including timeout) for Prime at Administration > System Settings > SNMP Settings
Have you installed the 2.2.1 maintenance release? If not, you might want to look at installing it, though be aware of the following if you do:
https://supportforums.cisco.com/discussion/12432566/software-images-page-cisco-prime-infrastructure-22-broken-after-installing

What are the features supported in Cisco Prime Infrastructure for WLAN for autonomous AP's?

What are the features supported in Cisco Prime Infrastructure for WLAN for autonomous AP’s?

• PI provides visibility for autonomous clients within the same list view as lightweight and wired clients (client list page).
• Rogue AP detection for autonomous AP's is not supported (it's supported in CUWN).
• Alarms/events for client authentication issues (e.g. authentication failure) are displayed in PI.
• Config management for autonomous AP's is via CLI template. Config comparison and archiving functionality in PI leverages these same features that were brought in from LMS, so need to defer to others in terms of whether this is a cross-platform feature in PI or is only supported on a subset of platforms. Config comparison/archive is supported in CUWN.PI supports both infrastructure (e.g. AP Tx Power and Channel, busiest AP, AP utilization, etc.) and client (e.g. client count, client sessions, etc.) reports, and there are extensive reports for CUWN

Prime infrastructure display issues

Similar Messages

Maybe you are looking for