Prime Infrastructure 1.2 Syslog

Hi,
We are currently working on a solution comprising Cisco Prime Infrastructure 1.2 and we can't understand if Prime Infrastructure can work as a syslog collector, since we can't get it to show us any syslog messages sent from the network devices in its the Alarms & Events section. Is this a normal behavior? Is it necessary to use a remote syslog collector on another machine?
Best regards!

You can edit the file in vi if you're handy with that text editor. I find it much easier to just create a new file like aijaz described above (copied below here) using your favorite local text editor (I use notepad++ in Windows) and name it syslog_sev_filter.xml.
Once you have that, copy it onto the PI server using ftp. You can then drop into the shell rename the current file syslog_sev_filter.xml.old and then copy the new syslog_sev_filter.xml file from your ftp repository to the /opt/CSCOlumos/conf/ directory.
Follow all that with popping back up out of the shell and do "ncs stop" followed with "ncs start" to restart the server and you should now be getting all severity syslog messages in your application.
/opt/CSCOlumos/conf/syslog_sev_filter.xml file (Bold lines have been added here):

Similar Messages

  • Cisco Prime Infrastructure 1.3 Syslog

    Dear all,
    I found some strange on Cisco PI 1.3: 
    Many syslog messages (about interface change status) were sent to PI, however not all message displayed in Event List.
    E.g:    All Syslog Messages from C6504 are not displayed.
              From Switch 3750, some are displayed, some not.
    Even I used Tcpdump on PI and saw that all syslog packets are received on PI's Interface.
    Could anyone help me???
    Regards

    Hello Cuong,
    may be this threat can help you and answer your question.
    https://supportforums.cisco.com/thread/2232711
    Regards
    Bastian

  • 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 *****

  • Syslog Email forwarding on Cisco Prime Infrastructure

    Hi everybody,
    We are performing a migration from LMS 4.2 to Prime Infrastructure 2.1 and we are realizing that some features are not in this new platform.
    I suspect that one of them is syslog forwarding by email. In our old LMS we collect some syslog messages, we filtrate them and we email some of them, based on a criteria. Some of them we email to someone, and some of them are droped.
    Does someone know if this feature is avaliable in Cisco Prime? I think we can collect syslog messages and view them, but we can not process. Am I right?
    Regards and thank you in advance,
    David

    Hi David,
    Yes , unfortunately  so far syslog forwarding is not supported. 
    Also so far only SEV 0.,1 and 2 syslogs are supported in PI. Hoping to have these features in PI 2.2
    Thanks-
    Afroz
    *****Ratings Encourages Contributors ****

  • Is cisco prime infrastructure support / can be run as syslog server?

    Dear All,
    is cisco prime infrastructure support / can be run as syslog server?
    and,
    where i can see network topology diagram, using cisco prime infrastructure?
    many thanks,
    Jerri

    Hello. Cisco Prime LMS will be replaced by Cisco Prime Infrastructure in the near future.
    In the current release of Cisco Prime Infrastructure you can't use topology diagrams. This feature is in roadmap.
    About syslog, you can send syslogs to Cisco Prime Infrastructure, but I don't recommend using it as syslog server. Please see this link for more information https://supportforums.cisco.com/thread/2179520
    Please rate if this helps

  • Syslog Support on Cisc Prime Infrastructure 1.3

    We have Cisco Prime Infrastructur 1.3. Can we configure this as Syslog & if yes where we can view the syslog.

    The general purpose syslog server is not quite baked on PI 1.x. Please refer to this related thread for some related information.
    At this point, I'd advise either a different solution (Prime LMS has a working one) or waiting for PI 2.0 (August) and seeing if they fix it then.

  • Download devices syslogs of Cisco Prime Infrastructure 2.2

    Hello,
    I'm working with Cisco Prime Infrastructure 2.2, wish I could download to my PC syslog captured by PI.

    Hi ,
    In the prime infrastructure Syslogs are directly read from udp port 514 and then filtered , the non SEV1 and SEV2 syslogs will be dropped and will not be entered into db . The syslog messages will not be saved into log files .
    Thanks-
    Afroz
    ***Ratings Encourages Contributors ****

  • Cisco prime Infrastructure alarms by e-mail

    hi all,
    my Cisco PI1.2 not send me a notification e-mail with specific alarm if occurred twice and the first time is not cleared or deleted.
    i.e.
    if a switch is down it send me a notification e-mail, and this switch comes up again but i did not remove the first alarm, the PI not send me a notification.
    please advice
    thanks in advance

    Alarm Status
    Description
    New
    When an event triggers a new alarm or an event is associated with an existing alarm.
    Acknowledged
    When you acknowledge an alarm, the status changes from New to Acknowledged.
    Cleared
    An alarm can be in these statuses:
    Auto-clear from the device—The fault is resolved on the device and an event is triggered for the same. For example, a device-reachable event clears the device-unreachable event. This in-turn, clears the device-unreachable alarm.
    Manual-clear from Prime Infrastructure users: You can manually clear an active alarm without resolving the fault in the network. A clearing event is triggered and this event clears the alarm.
    If the fault continues to exist in the network, a new event and alarm are created subsequently based on the event notification (traps/syslogs).
    This might be the reason, I believe.
    Please refer the following link for better understanding.
    http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/1-2/user/guide/prime_infra_ug/alarms.html
    Hope that helps.

  • Prime Infrastructure 2.0 - Alert on Switch Config Change

    We are in the process of testing out Prime Infrastructure 2.0, is there a way to get an alert when a device's configuration has changed, and send out what has changed in email? I have scheduled Config Archiving for all of my devices, and i can see the config differences when a changes is made in the Prime GUI, but we currently use Kiwi CatTools to send out emails that show what devices had configuration changes and what those changes were, it would be nice if Prime would do that so we could do away with that service. I have looked through all of the reports but do not see anything.

    Hi,
    I know this feature is there is LMS ,where you can configure the AUTOMATED Action based on Syslogs to get an Alert for config change or any other changes ,however I do not see this option available in PI  2.0.
    Syslogs are not compltely supported in 2.0 but in PI 2.1 we should have the complete support for syslogs.
    Thanks-
    Afroz
    [Do rate the useful post]

  • Prime Infrastructure 2.0 sync config tasks

    Hi,
    I'd like to know few things about PI 2.0 config handling:
    1. Can PI save running config to startup config on a scheduled basis? Let's say once a week on all devices.
    2. Can PI save running config to startup config whatsoever?
    3. Can PI download running config when it receives a config trap from device when user enters/exits config mode?
    4. Can PI export running and startup configs to a external location?
    Thanks!

    Hi ,
    1.
    *Scheduled-You can schedule when Prime Infrastructure collects the configurations of
    selected devices and specify recurring collections by selecting Operate > Configuration
    Archives, then clicking Schedule Archive.
    like  minute ..daily etc...
    3. ASAI K ,this feature work on the bases of syslogs .. we do not have complete support in PI 2.0 yet so I think bases on config chnage syslogs or traps ,config will not be fetched.
    4. for tihs check the below thread:
    https://supportforums.cisco.com/message/3975460#3975460
    Thanks-
    Afroz
    [Do rate the useful post]
    ****Ratings Encourages Contributors ****

  • Problem after upgrade a PRIME-NCS-APL-K9 from version 1.1.0.58 to Prime Infrastructure 1.2

    I have upgraded a PRIME-NCS-APL-K9 from version 1.1.0.58 to Prime Infrastructure 1.2
    First I have installed the Path "ncs_patch-1.1.0.58-upgrade-pi_1.2.tar.gz" and then the
    "PI-upgrade-bundle-1.2.0.103.tar.gz".
    after the upgade I have got the Message "Upgrade Successful".
    Now when I start the NCS i get the following error message
    egghead/admin# ncs start
    Starting Network Control System...
    Unable to verify hardware.
    This may take a few minutes...
    Health Monitor is already running.
    Failure during Network Control System startup. Check launchout.log for details.
    In the launchout.log are this messages:
    Starting Health Monitor as a primary
    Checking for Port 8082 availability... OK
    truststore used is /opt/CSCOlumos/conf/truststore
    truststore used is /opt/CSCOlumos/conf/truststore
    Starting Health Montior Web Server...
    Health Monitor Web Server Started.
    Starting Health Monitor Server...
    Health Monitor Server Started.
    Starting Remoting Service: Reporting Server
    Checking for running servers.
    00:00 Check complete. No servers running.
    Starting Server ...
    Starting Remoting Service: Reporting Server
    The Report Server startup script is already running waiting for report server to start
    Starting Remoting Service: Reporting Server
    The Report Server startup script is already running waiting for report server to start
    Starting Remoting Service: Reporting Server
    The Report Server startup script is already running waiting for report server to start
    Starting Remoting Service: Reporting Server
    The Report Server startup script is already running waiting for report server to start
    have anyone an idea whats wrong?
    thank you for your help
    Kurt

    i have  the same problem
    NCS/admin# ncs status
    Health Monitor Server is starting.
    Reporting Server is Starting
    Ftp Server is running
    Database server is running
    Tftp Server is running
    Matlab Server is running
    NMS Server is stopped.
    SAM Daemon is running ...
    DA Daemon is running ...
    Syslog Daemon is running ...
    status
    I try it
    To get it back up and running do the following from the CLI.
    1. Stop the NCS
    2. Run 'ncs db reinitdb'
    3. Start the NCS
    but the status is the same

  • 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 2.0 - no traps/info are pushed from devices

    Good evening,
    I have setup Cisco Prime Infrastructure 2.0 and,  though I have added manually my 4 network cores as devices without any  problem, I can't get a single trap or a single SNMP information to be  pushed into my Cisco Prime Infra.
    Here is my SNMP config on my core :
    snmp-server user *edited* *edited* v3
    snmp-server  group *edited* v3 noauth notify  *tv.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF0F
    snmp-server community *edited* RO
    snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart
    snmp-server enable traps flowmon
    snmp-server enable traps transceiver all
    snmp-server enable traps call-home message-send-fail server-fail
    snmp-server enable traps tty
    snmp-server enable traps rf
    snmp-server enable traps memory
    snmp-server enable traps cpu_threshold
    snmp-server enable traps eigrp
    snmp-server enable traps ospf state-change
    snmp-server enable traps ospf errors
    snmp-server enable traps ospf retransmit
    snmp-server enable traps ospf lsa
    snmp-server enable traps ospf cisco-specific state-change nssa-trans-change
    snmp-server enable traps ospf cisco-specific state-change shamlink interface
    snmp-server enable traps ospf cisco-specific state-change shamlink neighbor
    snmp-server enable traps ospf cisco-specific errors
    snmp-server enable traps ospf cisco-specific retransmit
    snmp-server enable traps ospf cisco-specific lsa
    snmp-server enable traps flex-links status
    snmp-server enable traps fru-ctrl
    snmp-server enable traps entity
    snmp-server enable traps ethernet cfm cc mep-up mep-down cross-connect loop config
    snmp-server enable traps ethernet cfm crosscheck mep-missing mep-unknown service-up
    snmp-server enable traps ether-oam
    snmp-server enable traps aaa_server
    snmp-server enable traps flash insertion removal
    snmp-server enable traps l2tc threshold sys-threshold
    snmp-server enable traps power-ethernet police
    snmp-server enable traps rep
    snmp-server enable traps vswitch dual-active vsl
    snmp-server enable traps udld link-fail-rpt status-change
    snmp-server enable traps vtp
    snmp-server enable traps vlancreate
    snmp-server enable traps vlandelete
    snmp-server enable traps auth-framework sec-violation
    snmp-server enable traps dot1x auth-fail-vlan guest-vlan no-auth-fail-vlan no-guest-vlan
    snmp-server enable traps envmon fan shutdown supply temperature status
    snmp-server enable traps entity-diag boot-up-fail hm-test-recover hm-thresh-reached scheduled-test-fail
    snmp-server enable traps port-security
    snmp-server enable traps ethernet evc status create delete
    snmp-server enable traps energywise
    snmp-server enable traps ipsla
    snmp-server enable traps vstack
    snmp-server enable traps bfd
    snmp-server enable traps bgp
    snmp-server enable traps bulkstat collection transfer
    snmp-server enable traps cef resource-failure peer-state-change peer-fib-state-change inconsistency
    snmp-server enable traps config-copy
    snmp-server enable traps config
    snmp-server enable traps config-ctid
    snmp-server enable traps event-manager
    snmp-server enable traps hsrp
    snmp-server enable traps ipmulticast
    snmp-server enable traps isis
    snmp-server enable traps msdp
    snmp-server enable traps pim neighbor-change rp-mapping-change invalid-pim-message
    snmp-server enable traps bridge newroot topologychange
    snmp-server enable traps stpx inconsistency root-inconsistency loop-inconsistency
    snmp-server enable traps syslog
    snmp-server enable traps isakmp policy add
    snmp-server enable traps isakmp policy delete
    snmp-server enable traps isakmp tunnel start
    snmp-server enable traps isakmp tunnel stop
    snmp-server enable traps ipsec cryptomap add
    snmp-server enable traps ipsec cryptomap delete
    snmp-server enable traps ipsec cryptomap attach
    snmp-server enable traps ipsec cryptomap detach
    snmp-server enable traps ipsec tunnel start
    snmp-server enable traps ipsec tunnel stop
    snmp-server enable traps ipsec too-many-sas
    snmp-server enable traps errdisable
    snmp-server enable traps ethernet cfm alarm
    snmp-server enable traps vlan-membership
    snmp-server enable traps mac-notification change move threshold
    snmp-server enable traps vrfmib vrf-up vrf-down vnet-trunk-up vnet-trunk-down
    snmp-server host *ip-address-edited* version 3 noauth *edited*
    Basically all traps are enabled but absolutely nothing is showing up in my Prime Infra except that my 4 devices are "Reachable".
    Here is a show snmp on the same device :
    sh snmp
    Chassis: *S/N Edited*
    38554534 SNMP packets input
        0 Bad SNMP version errors
        14 Unknown community name
        0 Illegal operation for community name supplied
        0 Encoding errors
        38453185 Number of requested variables
        0 Number of altered variables
        17790703 Get-request PDUs
        20583581 Get-next PDUs
        0 Set-request PDUs
        0 Input queue packet drops (Maximum queue size 1000)
    38490708 SNMP packets output
        0 Too big errors (Maximum packet size 1500)
        0 No such name errors
        0 Bad values errors
        0 General errors
        38371069 Response PDUs
        13 Trap PDUs
    SNMP global trap: enabled
    SNMP agent enabled
    SNMP logging: enabled
        Logging to *edited*, 0/10, 13 sent, 0 dropped.
    Can anyone point out what is wrong or missing in my configuration? I can't seem to single it out myself.
    Thanks
    Jeremy

    Hi Jeremy,
    SNMP traps are shown in the events and alerts section of PI.
    SNMP config looks fine. Can  you run the SNMP debug (debug snmp packets ) .check the logs and see if the device is actually sending the TRAPS to the PI server.
    Thanks-
    Afroz
    [Do rate the useful post]
    ****Ratings Encourages Contributors ****

  • UPS monitoring support with Cisco Prime Infrastructure 1.2

    Dear Members,
    Good day,
    I am having a project implemented wherein i have the UPS power redudancy solution for our network devices.
    Now can anyone gide that is it possible for below :-
    UPS units installed with SNMP cards be monitored via Cisco Prime Infrastructure 1.2 as our monitoring & management solution is Cisco Prime Infrastructure 1.2 ?
    if yes
    Can you guide if following action would be possible to export the below logs from UPS unit to our Cisco Prime Infrastructure 1.2
       a) UPS fault status information
       b) UPS operational status(input power available Y/N)
       c) Battery fault status
       d) Battery charging current
       e) Battery charge level
       f) Output current
    Conclusion is we need to confirm that would it be posible to achieve remote monitoring of these UPS units via our CPI 1.2
    Thanks in Advance for your support & replies to this query.
    Regards,
    Muzammil N.

    Prime Infrastructure 1.2 can manage non-Cisco devices in a limited fashion via SNMP query and trap processing. It cannot import logs and does not have a generic syslog server,
    So if your devices have snmp read only support and can generate SNMP traps for the above you can add them to PI. Follow the manual add device procedure here.

  • CISCO PRIME INFRASTRUCTURE 1.2 NCS ERROR

    Hi everyone,
    can anyone put through on this, i'm having issue starting the ncs server on cisco prime infrastructure 1.2 .below is the message i get when i do show ncs status:
    NGPHC-CPR001/admin# ncs status
    Health Monitor is running, with an error.
    failed to start NCS on startup Health Monitor
    Reporting Server is running
    Ftp Server is running
    Database server is running
    Tftp Server is running
    Matlab Server is running
    NMS Server is stopped.
    SAM Daemon is not running ...
    DA Daemon is not running ...
    Syslog Daemon is not running ...
    status
    thanks.

    Hi Marvin,
    Its has never worked. This is the first time i am installing it.
    I haved done as you adviced but still getting the same error as stated above.
    Please is there another way out.
    thanks.

Maybe you are looking for