127.0.0.1 IP address in SNMP trap
Hi,
In Weblogic 9.1, SNMP trap agent address is being sent as 127.0.0.1 IP address. Did anyone see this issue ?
Please let me know how this can be fixed
Thanks --GR
Patch needed - CR278615:
DIAGNOSIS: In the SNMP traps being sent out by WLS, the agent ID always comes out 127.0.0.1. If the trap listener was on a remote machine as the WLS server was, it wouldnt make much sense.
RESOLUTION: Initialize the agent address from the server's configuration.
RELEASE NOTE: SNMP trap data sent out by WebLogic Server Traps used to carry the local loopback address (127.0.0.1) of the SNMP agent machine, that is, the admininstration server machine - instead of its actual network IP address. This problem has been resolved.
Similar Messages
-
CAM Event Log: SNMP trap is received from switch [ ip address ] which is NOT in our database.
We keep getting thousands of entries in the CAM event log like this:
SNMP trap is received from switch [<ip address>] which is NOT in our database.
apparently, these aren't NAC'd switches. Why does the CAM see these and how can they be eliminated from the Event Log?
Thanks,Matt,
Do you switches have the CAM as a host where they are sending traps? Check the running-config of the servers and see if you spot the CAM IP address as one of the snmp-servers.
HTH,
Faisal -
Different Source Address for a SNMP trap paquet
We use a common platform to manage the CISCO routers for several customers. We are using to manage the devices w/ a loopback address as source of snmp paquet.
We use something like this ...
Router(config)#snmp-server host 172.25.1.1 ORATRAP
Router(config)#snmp-server trap-source loopback0
Router(config)#end
Now, there is some customers that request us to receipt the snmp-traps w/ an ip source of their own ip space (192.168.2.x/24).I cannot imagine how this can be achieve?... Please any idea?. Thks. Eduard.Thks., for your help. This is important matter to us. We also working in the idea of snmp track collector close to our own NMC... but this may cost also money... . So, we are going to try another approach first..
Somewhat like this below....
snmp-server enable traps
snmp-server informs
snmp-server source-interface traps
snmp-server source-interface informs
snmp-server host traps version 1 community string publicCust
snmp-server host informs version 2 community string publicBT
For the get's every MNC sends to the declared IP, so We thing that will use the same IP in answer.
I will let you know. Eduard. -
Remove any logging, or snmp trap hosts for the IP addresses in ASA 5550
I want to remove any syslog or snmp trap host related to an ip address for example 10.32.1.10. how can i get that specific line in running configuration related to specific ip address so that i can remove those lines?
Hi,
You can remove the logging host using this command:-
no logging host inside 10.32.1.10
You can check in "show run logging"
For SNMP host ,
no snmp-server host inside 192.0.2.5
Check using show run snmp-server
Thanks and Regards,
Vibhor Amrodia -
Creating SNMP Trap Monitors in 2012 R2
Hello,
For the past week or so I have been attempting to create a MP for my company's UPSs to be monitored in SCOM 2012 R2. I have created a custom MP with custom datasources and objects. All seems to go according to the plan until I attempt to create a SNMP
Trap monitor for those objects. I am able to verify that the device is discovered and is sending the traps successfully with a view. The problem seems to lie within the setup of the monitor. I have followed the steps as much as I can from this page http://technet.microsoft.com/en-us/library/hh563870.aspx
to create a monitor that will be triggered by an incoming trap saying the UPS is on Battery Power.
This is the initial or trigger event information received by SCOM:
<EventData>
<DataItem type="System.SnmpData" time="2014-07-03T08:48:07.6990732-07:00" sourceHealthServiceId="26DF02E5-DEA0-BED0-443B-3605A05D4790">
<Source>10.51.85.40</Source>
<Destination>127.0.0.1</Destination>
<ErrorCode>1</ErrorCode>
<Version>1</Version>
<SnmpVarBinds>
<SnmpVarBind>
<OID>.1.3.6.1.2.1.1.3.0</OID>
<Syntax>67</Syntax>
<Value VariantType="19">17567220</Value>
</SnmpVarBind>
<SnmpVarBind>
<OID>.1.3.6.1.6.3.1.1.4.1.0</OID>
<Syntax>6</Syntax>
<Value VariantType="8">.1.3.6.1.4.1.318.0.5</Value>
</SnmpVarBind>
<SnmpVarBind>
<OID>.1.3.6.1.4.1.318.2.3.3.0</OID>
<Syntax>4</Syntax>
<Value VariantType="8">UPS: On battery power in response to an input power problem.</Value>
</SnmpVarBind>
<SnmpVarBind>
<OID>.1.3.6.1.6.3.1.1.4.3.0</OID>
<Syntax>6</Syntax>
<Value VariantType="8">.1.3.6.1.4.1.318</Value>
</SnmpVarBind>
</SnmpVarBinds>
</DataItem>
</EventData>
This is the event should signal that everything is operating normally once again.
<EventData>
<DataItem type="System.SnmpData" time="2014-07-03T08:48:12.9133769-07:00" sourceHealthServiceId="26DF02E5-DEA0-BED0-443B-3605A05D4790"><Source>10.51.85.40</Source>
<Destination>127.0.0.1</Destination>
<ErrorCode>1</ErrorCode>
<Version>1</Version>
<SnmpVarBinds>
<SnmpVarBind>
<OID>.1.3.6.1.2.1.1.3.0</OID>
<Syntax>67</Syntax>
<Value VariantType="19">17567730</Value>
</SnmpVarBind>
<SnmpVarBind>
<OID>.1.3.6.1.6.3.1.1.4.1.0</OID>
<Syntax>6</Syntax>
<Value VariantType="8">.1.3.6.1.4.1.318.0.9</Value>
</SnmpVarBind>
<SnmpVarBind>
<OID>.1.3.6.1.4.1.318.2.3.3.0</OID>
<Syntax>4</Syntax>
<Value VariantType="8">UPS: No longer on battery power.</Value>
</SnmpVarBind>
<SnmpVarBind>
<OID>.1.3.6.1.6.3.1.1.4.3.0</OID>
<Syntax>6</Syntax>
<Value VariantType="8">.1.3.6.1.4.1.318</Value>
</SnmpVarBind>
</SnmpVarBinds>
</DataItem>
</EventData>
You may notice that these traps are being sent as SNMP v1. I am unable to change that on the UPS so i have modified the monitors to account for that. Here is the code for the monitor:
<UnitMonitor ID="UIGeneratedMonitorc2c65f3c85fe42f48ce8d2580c57bbae" Accessibility="Public" Enabled="true" Target="APC.MP.UPS" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="SNL!System.NetworkManagement.SnmpTrapProvider.2SingleEvent2StateMonitorType" ConfirmDelivery="false">
<Category>Custom</Category>
<AlertSettings AlertMessage="UIGeneratedMonitorc2c65f3c85fe42f48ce8d2580c57bbae_AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UIGeneratedOpStateId2750c1ab2cd14b4a8a8e9f4633eba0b0" MonitorTypeStateID="SecondEventRaised" HealthState="Success" />
<OperationalState ID="UIGeneratedOpStateId5753748399984d08953c1a46895df99c" MonitorTypeStateID="FirstEventRaised" HealthState="Warning" />
</OperationalStates>
<Configuration>
<FirstIP>$Target/Property[Type="SNL!System.NetworkManagement.Node"]/SNMPAddress$</FirstIP>
<FirstVersion>1</FirstVersion>
<FirstOIDProps>
<OIDProp>.1.3.6.1.4.1.318</OIDProp>
</FirstOIDProps>
<FirstExpression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">SnmpVarBinds/SnmpVarBind[OID=".1.3.6.1.6.3.1.1.4.1.0"]/Value</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">.1.3.6.1.4.1.318.0.5</Value>
</ValueExpression>
</SimpleExpression>
</FirstExpression>
<SecondIP>$Target/Property[Type="SNL!System.NetworkManagement.Node"]/SNMPAddress$</SecondIP>
<SecondVersion>1</SecondVersion>
<SecondOIDProps>
<OIDProp>.1.3.6.1.4.1.318</OIDProp>
</SecondOIDProps>
<SecondExpression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">SnmpVarBinds/SnmpVarBind[OID=".1.3.6.1.6.3.1.1.4.1.0"]/Value</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">.1.3.6.1.4.1.318.0.9</Value>
</ValueExpression>
</SimpleExpression>
</SecondExpression>
</Configuration>
</UnitMonitor>
I tried the following things while attempting to troubleshoot this issue:
Leaving First
SnmpTrapProvider and Second
SnmpTrapProvider blank while creating the monitor.
Adding "" and also '' around the value as it is a string and perhaps that was the cause.
Changing the First and Second SNMPTrapProvider to .1.3.6.1.6.3.1.1.4.1.0 since that is the specific OID I am looking for the value of.
Reading every page of the internet and bashing my head on the keyboard.
I am guessing that the issue will reside in the the monitor creation and definition, but I have not found anything that clearly describes how to fill out the SNMP Trap Monitor wizard given the trap info. Especially since the trap I am receiving does
not seem to contain the usual OID with a common Int or string value. Hopefully someone can provide assistance as I am nearing my wits end with this problem.Firstly, thank you Michael Skov, knowing that the First and Second SnmpTrapProvider or <FirstOIDProps> in the xml, needed to be blank got me pointed in the right direction. I figured I would come back and share my final working code snippet in case
others run across a similar issue.
<UnitMonitor ID="UIGeneratedMonitorf9f671e5456c44fd807d6ec2bd09621d" Accessibility="Public" Enabled="true" Target="Disc!APC.Disc.UPS" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="NetworkManagement!System.NetworkManagement.SnmpTrapProvider.2SingleEvent2StateMonitorType" ConfirmDelivery="false">
<Category>Custom</Category>
<AlertSettings AlertMessage="UIGeneratedMonitorf9f671e5456c44fd807d6ec2bd09621d_AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Warning</AlertSeverity>
</AlertSettings>
<OperationalStates>
<OperationalState ID="UIGeneratedOpStateId8700c95344254f87a60c92d30d4a3953" MonitorTypeStateID="SecondEventRaised" HealthState="Success" />
<OperationalState ID="UIGeneratedOpStateId7bf68c6cfe3d4faabe83e630781c7327" MonitorTypeStateID="FirstEventRaised" HealthState="Warning" />
</OperationalStates>
<Configuration>
<FirstIP>$Target/Property[Type="NetworkManagement!System.NetworkManagement.Node"]/SNMPAddress$</FirstIP>
<FirstVersion>1</FirstVersion>
<FirstOIDProps />
<FirstExpression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">SnmpVarBinds/SnmpVarBind[OID=".1.3.6.1.6.3.1.1.4.1.0"]/Value</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">.1.3.6.1.4.1.318.0.5</Value>
</ValueExpression>
</SimpleExpression>
</FirstExpression>
<SecondIP>$Target/Property[Type="NetworkManagement!System.NetworkManagement.Node"]/SNMPAddress$</SecondIP>
<SecondVersion>1</SecondVersion>
<SecondOIDProps />
<SecondExpression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">SnmpVarBinds/SnmpVarBind[OID=".1.3.6.1.6.3.1.1.4.1.0"]/Value</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">.1.3.6.1.4.1.318.0.9</Value>
</ValueExpression>
</SimpleExpression>
</SecondExpression>
</Configuration>
</UnitMonitor> -
LMS 3.2.1 integration with Clarity NMS for snmp trap forwarding
Our client have integrated Clarity NMS to Ciscoworks LMS 3.2.1. So far they are receiving raw alarms/snmp traps but it lacks information/inventory of the originating device. Kindly see sample raw alarms below:
2420: 2011-11-25 12:10:46 Received trap ==> Received SNMPv1 Trap
Community=ciscoworks
Enterprise=1.3.6.1.6.3.1.1.5
Generip trap type=2
Specific Trap Type=0
Trap From=10.220.10.1
Trap ID=1.3.6.1.6.3.1.1.5.2
Trap Time=-1436283373
1.3.6.1.2.1.2.2.1.1.83=83
1.3.6.1.2.1.2.2.1.2.83=GigabitEthernet1/40
1.3.6.1.2.1.2.2.1.3.83=6
1.3.6.1.4.1.9.2.2.1.1.20.83=Lost Carrier
EndTrap
10933: 2011-11-24 11:57:53 Received trap ==> Received SNMPv1 Trap
Community=ciscoworks
Enterprise=1.3.6.1.4.1.9.1.291
Generip trap type=2
Specific Trap Type=0
Trap From=10.220.10.1
Trap ID=1.3.6.1.4.1.9.1.291.2
Trap Time=1628056965
1.3.6.1.2.1.2.2.1.1.8=8
1.3.6.1.2.1.2.2.1.2.8=E1 0/0/0
1.3.6.1.2.1.2.2.1.3.8=18
EndTrap
As you can see, those raw alarms doesn’t contain any information about the originating equipment or the physical card, port related information where those alarms were generated. Instead those alarms received are just NMS level alarms.
How do we resolve this so that the inventory of the equipment would be part of the trap to be received by Clarity from Ciscoworks.Hi,
Is the issue you have the source IP address of the forwarded trap? Per RFC it is the IP of the actual device sending the trap. The originating IP should be contained within the packet. I have included some additional information you may find helpful.
Q. What is the difference between SNMP Raw Trap Forwarding and SNMP Trap alert/event Trap Forwarding? Does DFM support both?
A. You can configure raw trap forwarding at DFM > Other configuration > SNMP Trap forwarding, and processed event/alert trap forwarding at DFM > Notification Services > SNMP Trap Forwarding. Processed trap is "when DFM receives certain SNMP traps, it analyzes the data found in fields (Enterprise/Generic trap identifier/Specific Trap identifier/variable−bindings) of each SNMP trap message, and changes the property value of the object property (if required)". Raw trap is the trap that the device forwards to DFM and DFM has yet to process it. For more information, refer to the DFM User Guide. Yes, DFM supports both ways of trap forwarding.
http://www.cisco.com/en/US/products/sw/cscowork/ps2421/products_qanda_item09186a0080a9b35b.shtml
DFM will only forward SNMP traps from devices in the DFM inventory. It will not change the trap format—it will forward the raw trap in the format in which the trap was received from the device. However, you must enable SNMP on your devices and you must do one of the following:
Configure SNMP to send traps directly to DFM
Integrate SNMP trap receiving with an NMS or a trap daemon
The versions of SNMP traps supported by DFM are described in SNMP and ICMP Polling. For information on forwarding processed and pass-through traps, see Processed and Pass-Through Traps, and Unidentified Traps and Events.
Pass-through traps are traps that DFM receives from devices that are not in the DFM inventory, and DFM has not processed. Forwarding these traps is controlled using Configuration > Other Configurations > SNMP Trap Forwarding. These traps are shown in the Alerts and Activities display because of their relevance to fault monitoring. Pass-through traps are displayed as follows:
As one of the following events:
> InformAlarm
> MinorAlarm
> MajorAlarm
With the device type and the device name from which it was generated.
If DFM does not know which device generated the trap, it ignores the trap. Pass-through traps will be cleared after a default interval of 10 minutes to one hour
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_device_fault_manager/3.2/user/guide/dfm32ug_Book.html -
Cisco WLC 5508 not sending SNMP Traps
Hello Everyone.
I'm having a weird error on our WLC environment. We have an HA with two cisco WLC 5508 and i cannot get SNMP Traps working on a Windows PC running Kiwi Syslog server (free ed.).
I can receive correctly Syslog messages, but not traps.
I Tried also to send SNMP Traps from WLC to a different PC using Linux with snmptrapd and it works fine.
I tried then to send from my Linux box a snmp trap to my Windows PC, and it works fine, but i still cannot receive anything from WLC.
Using Wireshark to detect traffic, i cannot see any packet on udp port 162.
I cannot figure out any problem with my scenario, but i can see the following errors on syslog:
*rmgrTrasport: Mar 30 16:08:22.602: #RMGR-3-INVALID_PING_RESPONSE: rmgr_utils.c:270 Ping response from <my_windows_PC> is invalid. Ip address do not match.
My WLC Version is 7.6.130.0
Thank you for your support.I have gone through your query and found the following fruitful links ,please let me know if it helps and mark it correct answer if it is.
https://www.manageengine.com/network-monitoring/help/userguide/processing_traps.html
https://rscciew.wordpress.com/2014/10/12/snmp-configuration-on-wlc/
Thanks :) -
Is there any way of resolving a 2950 snmp trap to a host name instead of an ip address, ...if possible, where and how is this done?
Thanks!Hello,
do you mean the ´snmp-server host´ command followed by a name instead of an IP address ? That is:
snmp-server host 192.168.1.1
should be
snmp-server host SNMP_SERVER
You could add a local ´ip host´ statement to your router:
ip host 192.168.1.1 SNMP_SERVER
Is that what you are asking ?
Regards,
GP -
SNMP Trap and logical hostname
Consider a case in which a cluster node has two public network interface in a IPMP group and a logical hostname (ip addr) is also assigned to one of the interfaces.
If an SNMP trap is generated from this cluster node, what would be the source IP address in the IP header of the trap?
Is there a way to restrict the source IP addr to one of the interfaces?There is only IPMP group so I'm not sure what you mean by active/standby groups. If your question meant to ask whether the interfaces within the group are in active/standby, the answer is no.
Even if they were active/standby and the trap always travels over the active interface, the question still remains whether the source IP address would be the physical address or the logical address, assuming the logical address is also assigned to the same interface. -
CSCud17778 - memory leak in middle buffers due to snmp traps
The bug details list these as the conditions required to cause the symptom. They don't specify whether these three conditions are an AND or an OR, but I'm assuming that all three must be satisfied:
Conditions:
1) more than one snmp-server hosts are configured
2) "snmp-server enable traps snmp authentication linkdown linkup coldstart warmstart" command is configured
3) some host sending broadcast SNMP traps
What I'm confused about is #3 -- how would that be germane? If some "host" sends SNMP traps to an IP broadcast address, the switch should ignore them because it will not be listening on UDP port 162. If instead of SNMP traps, the host were broadcasting SNMP GETs, that would make it as far as the community string check, which would require buffer storage for the switch SNMP process. And assuming that check failed, the generation of an authentication_failed trap to multiple trap receivers would require more buffers.
Can anyone (especially from the TAC) clarify this?
TIA,
- MartyHi Marty,
Yes, all 3 are required (AND conditions).
Also note for #2, it is really the "authentication" portion of the command.
In this case, I believe the IOS devices is actually looking / listening to these received traps. The receipt of this SNMP trap is definately a required condition to trigger this bug.
Sincerely,
David. -
HI
I am trying to configure IP SLA to send SNMP TRAPS but looks like doing some mistake ..
i have following configured
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-ascii-font-family:Cambria;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Cambria;
mso-hansi-theme-font:minor-latin;}
ip sla monitor 2
type echo protocol ipIcmpEcho 150.1.3.3 source-ipaddr 1.1.98.7
frequency 10!
ip sla monitor schedule 2 start-time now recurring
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-ascii-font-family:Cambria;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Cambria;
mso-hansi-theme-font:minor-latin;}
ip sla reaction-configuration 2 react rtt threshold-type immediate action-type trapOnly
ip sla logging traps
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-ascii-font-family:Cambria;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Cambria;
mso-hansi-theme-font:minor-latin;}
snmp-server community public RO
snmp-server enable traps rtr
snmp-server host 1.1.128.226 public
1.1.98.7 is the loopback ip on my network. To test the snmp traps, i enabled debug snmp packets and shutdown loopback interface (1.1.98.7)
I don't see any snmp message in debug output ..
am i missing something or it is not possible to get traps directly from ip sla .. do i need EEM for this?sorry, it actually worked .. i just gave a restart to ip sla and it worked.
looks like router was already in threshold stage when i was activating reaction-config ..
but i am still confused which command is actualluy generating these traps since i have taken out some of the snmp config out and i stil get traps ..
below is the oputput of traps which i get when i restart ip sla .
*Feb 15 17:10:43.453: SNMP: 150.150.1.1 queue overflow, dropping packet
*Feb 15 17:10:43.453: SNMP: Queuing packet to 150.150.1.1
*Feb 15 17:10:43.453: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 65.65.2.2, gentrap 6, spectrap 3
rttMonCtrlAdminTag.1 =
rttMonHistoryCollectionAddress.1 = 41 41 03 03
rttMonCtrlOperOverThresholdOccurred.1 = 1
*Feb 15 17:10:43.497: SNMP: 150.150.1.1 queue overflow, dropping packet
*Feb 15 17:10:43.501: SNMP: Queuing packet to 150.150.1.1
*Feb 15 17:10:43.501: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 65.65.2.2, gentrap 6, spectrap 5
rttMonCtrlAdminTag.1 =
rttMonHistoryCollectionAddress.1 = 41 41 03 03
rttMonReactVar.1 = 1
rttMonReactOccurred.1 = 1
rttMonReactValue.1 = 12
rttMonReactThresholdRising.1 = 5
rttMonReactThresholdFalling.1 = 1
rttMonEchoAdminLSPSelector.1 = 00 00 00 00
*Feb 15 17:10:43.585: SNMP: 150.150.1.1 queue overflow, dropping packet
*Feb 15 17:10:43.585: SNMP: Queuing packet to 150.150.1.1
*Feb 15 17:10:43.585: SNMP: V1 Trap, ent rttMonNotificationsPrefix, addr 65.65.2.2, gentrap 6, spectrap 5
rttMonCtrlAdminTag.1 =
rttMonHistoryCollectionAddress.1 = 41 41 03 03
rttMonReactVar.1 = 1
rttMonReactOccurred.1 = 1
rttMonReactValue.1 = 12
rttMonReactThresholdRising.1 = 5
rttMonReactThresholdFalling.1 = 1
rttMonEchoAdminLSPSelector.1 = 00 00 00 00
below is my running config and sh ver
R2#sh ver
Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9-M), Version 12.4(24)T1, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Fri 19-Jun-09 15:13 by prod_rel_team
ROM: System Bootstrap, Version 12.4(1r) [hqluong 1r], RELEASE SOFTWARE (fc1)
R2 uptime is 8 hours, 9 minutes
System returned to ROM by power-on
System image file is "flash:c2800nm-adventerprisek9-mz.124-24.T1.bin"
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
Cisco 2811 (revision 53.50) with 237568K/24576K bytes of memory.
Processor board ID FTX0952C333
2 FastEthernet interfaces
4 Serial(sync/async) interfaces
1 Virtual Private Network (VPN) Module
DRAM configuration is 64 bits wide with parity enabled.
239K bytes of non-volatile configuration memory.
62720K bytes of ATA CompactFlash (Read/Write)
Configuration register is 0x2102
R2#
R2#sh run
Building configuration...
Current configuration : 2233 bytes
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname R2
boot-start-marker
boot-end-marker
no aaa new-model
memory-size iomem 10
dot11 syslog
ip source-route
ip cef
ipv6 unicast-routing
ipv6 cef
multilink bundle-name authenticated
voice-card 0
vtp domain 29
vtp mode transparent
archive
log config
hidekeys
interface Loopback0
ip address 65.65.2.2 255.255.255.0
interface FastEthernet0/0
shutdown
duplex auto
speed auto
interface FastEthernet0/1
ip address 65.65.128.193 255.255.255.224
shutdown
duplex auto
speed auto
interface Serial0/2/0
ip address 65.65.13.2 255.255.255.224
encapsulation ppp
clock rate 2000000
interface Serial0/3/0
no ip address
shutdown
router ospf 65
router-id 65.65.2.2
log-adjacency-changes
network 65.65.2.2 0.0.0.0 area 1
network 65.65.13.2 0.0.0.0 area 1
network 65.65.128.193 0.0.0.0 area 1
ip forward-protocol nd
no ip http server
no ip http secure-server
ip sla 1
icmp-echo 65.65.3.3 source-ip 65.65.2.2
request-data-size 1500
frequency 10
ip sla schedule 1 life forever start-time now
ip sla reaction-configuration 1 react rtt threshold-value 5 1 threshold-type immediate action-type trapOnly
snmp-server community public RO
snmp-server host 150.150.1.1 public
control-plane
mgcp fax t38 ecm
mgcp behavior g729-variants static-pt
line con 0
line aux 0
line vty 0 4
login
scheduler allocate 20000 1000
end
R2#
R2# -
Anm 4.1 support for receiving snmp traps from CSS / ACE
Hi
Does anyone have an ANM 4.1 installation that is accepting snmp traps from their CSSes / ACEs?
If I configure CSSes / ACEs to send snmp v1 traps to anm, they never appear in the Monitor -> Events view.
I've tried both the ANM 4.1 Virtual Appliance and ANM 4.1 running on RHEL and it seems that there's nothing listening on udp port 162 to receive the snmp traps.
From the virtual appliance:
admin# show ports
Process : java (5999)
tcp: 0.0.0.0:40000, 0.0.0.0:40001, 127.0.0.1:10023, 0.0.0.0:10443, 0.0.0.0:
10003, 0.0.0.0:10004, 0.0.0.0:8443
udp: 0.0.0.0:39182, 0.0.0.0:10003, 0.0.0.0:6120
Process : rpc.statd (2348)
tcp: 0.0.0.0:834
udp: 0.0.0.0:828, 0.0.0.0:831
Process : mysqld (3125)
tcp: 0.0.0.0:3306
Process : java (5992)
tcp: 0.0.0.0:10444, 0.0.0.0:10445
Process : portmap (2312)
tcp: 0.0.0.0:111
udp: 0.0.0.0:111
Process : monit (2779)
tcp: 0.0.0.0:2812
Process : java (2952)
tcp: :::40002
Process : java (2966)
tcp: :::40003
Process : sshd (2625)
tcp: :::22
Process : ntpd (2606)
udp: 127.0.0.1:123, 0.0.0.0:123, ::1:123, :::123
I notice that port 443 isn't in here and I'm accessing the web interface using this port so perhaps there's something else going on behind the scenes.
Can anyone point me in the right direction to get snmp traps shown as events in ANM 4.1?
Thanks very muchhi.
as per documentation:
http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/application_networking_manager/4.1/user/guide/UG_monitor.html#wp1176870
you need to send snmpv2 to anm. can you try v2 traps and see if it works?
Regards,
Fadi. -
OK, so I'm at wit's end with this one now.
I configured my SNMP items on the controller and let it roll.
I started to watch my SNMP monitor (SNMPc Management Console by CastleRock) and saw some life from my controller. Yay, woot and dance.
I then started narrowing down the SNMP trap controls because I was getting more than what I want/need currently. I really just want to know if an AP falls off the network or if the controller's link drops.
I continued to get alerts that were just not desireable at this point.
The traps were similar to this:
ciscoLwappDot11ClientAssocNacAlert [1] cldcClientMacAddress.0.36.214.60.32.32 (DisplayString): 00:24:d6:3c:20:20 [2] cldcClientWlanProfileName.0.36.214.60.32.32 (DisplayString): Wireless [3] cldcClientIPAddress.0.36.214.60.32.32 (IpAddress): 172.31.19.101 [4] cldcApMacAddress.0.36.214.60.32.32 (DisplayString): 00:08:30:39:6c:80 [5] cldcClientQuarantineVLAN.0.36.214.60.32.32 (Integer): 0 [6] cldcClientAccessVLAN.0.36.214.60.32.32 (Integer): 119
I couldn't find the culprit, so I turned off (unchecked) all trap controls in the web interface and then verified in the CLI with "show trapflags".
I continue to get these same messages.
Any ideas?
Model: AIR-CT5508-K9
Version: 7.2.103.0I went through the entire log (about 2000 lines) and almost all are this same type:
(Cisco Controller) >show traplog
Number of Traps Since Last Reset ............ 323738
Number of Traps Since Log Last Displayed .... 0
Log System Time Trap
0 Mon Mar 11 08:21:49 2013 Client with MAC address 00:24:d6:3c:20:20 has joi
ned profile SC Wireless
1 Mon Mar 11 08:20:16 2013 Client with MAC address 00:24:d6:3c:20:20 has joi
ned profile SC Wireless
2 Mon Mar 11 08:19:09 2013 Client with MAC address 00:24:d6:3c:20:20 has joi
ned profile SC Wireless
3 Mon Mar 11 08:10:21 2013 Client with MAC address cc:af:78:44:7d:2b has joi
ned profile SC Wireless
4 Mon Mar 11 08:10:18 2013 Client with MAC address cc:af:78:44:7d:2b has joi
ned profile SC Wireless
Keep in mind that I have all trap controls disabled.
(Cisco Controller) >show trapflags
Authentication Flag.............................. Disable
Link Up/Down Flag................................ Disable
Multiple Users Flag.............................. Disable
configsave....................................... Disabled
strong-pwd check................................. Disabled
Client Related Traps
802.11 Disassociation........................... Disabled
802.11 Association.............................. Disabled
802.11 Deauthenticate........................... Disabled
802.11 Authenticate Failure..................... Disabled
802.11 Association Failure...................... Disabled
Excluded........................................ Disabled
Authentication.................................. Disabled
Cisco AP
AuthFailure..................................... Disabled
Register........................................ Disabled
InterfaceUp..................................... Disabled
802.11 Security related traps
WEP/WPA Decrypt Error........................... Disabled
IDS Signature Attack............................ Disable
AAA
auth............................................ Disabled
servers......................................... Disabled
rogueap......................................... Disabled
Auto-RF Profiles
Load............................................ Disabled
Noise........................................... Disabled
Interference.................................... Disabled
Coverage........................................ Disabled
Auto-RF Thresholds
tx-power........................................ Disabled
channel......................................... Disabled
Mesh
auth failure.................................... Disabled
child excluded parent........................... Disabled
parent change................................... Disabled
child moved..................................... Disabled
excessive parent change......................... Disabled
onset SNR....................................... Disabled
abate SNR....................................... Disabled
console login................................... Disabled
excessive association........................... Disabled
default bridge group name....................... Disabled
excessive hop count............................. Disabled
excessive children.............................. Disabled
sec backhaul change............................. Disabled
Hopefully I'm just missing something stupid, but it appears all flags are off.
Message was edited by: Casey Hearn
Added "Show TrapFlags" details. -
We are trying to test the snmp trap on IOS-XR for BGP up down, but ASR didn't send out any traps when we brought down the BGP neighbour. When we tested the OSPF, it worked fine. I also tried to use command 'snmp test' to generate the test trap and I got following message, The version is 4.2. Any suggestions? Thanks.
RP/0/RSP0/CPU0:Feb 22 13:58:20.691 : test_trap[65889]: Debug init Done
RP/0/RSP0/CPU0:Feb 22 13:58:21.083 : test_trap[446]: Trap ID: 28
RP/0/RSP0/CPU0:Feb 22 13:58:21.084 : test_trap[446]: make_test_traps: input args 0x0 0x0 (null) (null)
Failed to format BGP Trap
RP/0/RSP0/CPU0:Feb 22 13:58:21.084 : test_trap[446]: get_first_bgp_peer_index: Getting first BGP Peer
RP/0/RSP0/CPU0:Feb 22 13:58:21.104 : test_trap[446]: get_first_bgp_peer_index: Failed to get BGP indices
Current config:
snmp-server host x.x.x.x traps version 2c xxxxxx
snmp-server community encrypted xxxx RO
snmp-server community encrypted yyyy RW
snmp-server traps rf
snmp-server traps bgp cbgp2
snmp-server traps bgp
snmp-server traps ospf state-change neighbor-state-change
snmp-server packetsize 1024
snmp-server trap-source MgmtEth0/RSP0/CPU0/0
snmp-server ifindex persist
Regards. LeoHi,
I am running 4.2.3 and seems like trap generated. also see the snm-server traps bgp commands in running config.
RP/0/RSP0/CPU0:PE2#show vrf mse_1001 detail
Mon Feb 25 14:58:29.027 PST
VRF mse_1001; RD 65002:1001; VPN ID not set
VRF mode: Regular
Description not set
Interfaces:
GigabitEthernet0/3/0/0.1001
Address family IPV4 Unicast
Import VPN route-target communities:
RT:65001:1001
Export VPN route-target communities:
RT:65001:1001
No import route policy
No export route policy
Address family IPV6 Unicast
Import VPN route-target communities:
RT:65001:1001
Export VPN route-target communities:
RT:65001:1001
No import route policy
No export route policy
RP/0/RSP0/CPU0:PE2#show ipv4 vrf mse_1001 interface brief
Mon Feb 25 14:59:16.154 PST
Interface IP-Address Status Protocol
GigabitEthernet0/3/0/0.1001 101.1.1.1 Up Up
RP/0/RSP0/CPU0:PE2#term mon
Mon Feb 25 14:59:33.803 PST
RP/0/RSP0/CPU0:PE2#conf t
Mon Feb 25 14:59:34.894 PST
RP/0/RSP0/CPU0:PE2(config)#int gi0/3/0/0.1001
RP/0/RSP0/CPU0:PE2(config-subif)#shut
RP/0/RSP0/CPU0:PE2(config-subif)#commit
Mon Feb 25 14:59:46.480 PST
LC/0/3/CPU0:Feb 25 14:59:46.617 : bfd_agent[124]: %L2-BFD-6-ADJACENCY_DELETE : Adjacency to neighbor 101.1.1.2 on interface GigabitEthernet0/3/0/0.1001 was deleted
RP/0/RSP0/CPU0:Feb 25 14:59:46.621 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 101.1.1.2 Down - Admin. shutdown (VRF: mse_1001)
RP/0/RSP1/CPU0:Feb 25 14:59:46.620 : bgp[1048]: %ROUTING-BGP-5-NBR_NSR_DISABLED_STANDBY : NSR disabled on neighbor 101.1.1.2 on standby due to Admin. shutdown (VRF: mse_1001)
RP/0/RSP0/CPU0:Feb 25 14:59:46.626 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 1011:1:1::2 Down - Admin. shutdown (VRF: mse_1001)
RP/0/RSP1/CPU0:Feb 25 14:59:46.622 : bgp[1048]: %ROUTING-BGP-5-NBR_NSR_DISABLED_STANDBY : NSR disabled on neighbor 1011:1:1::2 on standby due to Admin. shutdown (VRF: mse_1001)
LC/0/3/CPU0:Feb 25 14:59:46.719 : bfd_agent[124]: %L2-BFD-6-ADJACENCY_DELETE : Adjacency to neighbor 1011:1:1::2 on interface GigabitEthernet0/3/0/0.1001 was deleted
LC/0/3/CPU0:Feb 25 14:59:47.294 : bfd_agent[124]: %L2-BFD-6-SESSION_STATE_DOWN : BFD session to neighbor 1011:1:1::2 on interface GigabitEthernet0/3/0/0.1001 has gone down. Reason: Control timer expired
LC/0/3/CPU0:Feb 25 14:59:47.401 : bfd_agent[124]: %L2-BFD-6-SESSION_STATE_DOWN : BFD session to neighbor 101.1.1.2 on interface GigabitEthernet0/3/0/0.1001 has gone down. Reason: Nbor signalled down
RP/0/RSP0/CPU0:Feb 25 14:59:47.513 : config[65903]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'lab'. Use 'show configuration commit changes 1000000208' to view the changes.
RP/0/RSP0/CPU0:PE2(config-subif)#RP/0/RSP0/CPU0:Feb 25 14:59:47.633 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.2 qlen:0
RP/0/RSP0/CPU0:Feb 25 14:59:47.633 : snmpd[1112]: t8 Queueing trap:bgp.0.2 qlen:1
RP/0/RSP0/CPU0:Feb 25 14:59:47.634 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.8 qlen:2
RP/0/RSP0/CPU0:Feb 25 14:59:47.634 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.6 qlen:3
RP/0/RSP0/CPU0:Feb 25 14:59:47.635 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.1 qlen:4
RP/0/RSP0/CPU0:Feb 25 14:59:47.635 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:5
RP/0/RSP0/CPU0:Feb 25 14:59:47.635 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.8 qlen:6
RP/0/RSP0/CPU0:Feb 25 14:59:47.636 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.6 qlen:7
RP/0/RSP0/CPU0:Feb 25 14:59:47.636 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:8
RP/0/RSP0/CPU0:Feb 25 14:59:47.637 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.2
RP/0/RSP0/CPU0:Feb 25 14:59:47.637 : snmpd[1112]: t13 Processing trap bgp.0.2
RP/0/RSP0/CPU0:Feb 25 14:59:47.638 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.8
RP/0/RSP0/CPU0:Feb 25 14:59:47.638 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.6
RP/0/RSP0/CPU0:Feb 25 14:59:47.638 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.1
RP/0/RSP0/CPU0:Feb 25 14:59:47.639 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.7
RP/0/RSP0/CPU0:Feb 25 14:59:47.639 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.8
RP/0/RSP0/CPU0:Feb 25 14:59:47.639 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.6
RP/0/RSP0/CPU0:Feb 25 14:59:47.640 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.7
RP/0/RSP0/CPU0:PE2(config-subif)#
RP/0/RSP0/CPU0:PE2(config-subif)#end
RP/0/RSP0/CPU0:Feb 25 14:59:55.901 : config[65903]: %MGBL-SYS-5-CONFIG_I : Configured from console by lab on vty0 (223.255.254.249)
RP/0/RSP0/CPU0:PE2#show snmp trap
Mon Feb 25 14:59:59.901 PST
TrapOID Number of Times
bgp.0.2 1
ciscoBgp4MIB.0.1 1
ciscoBgp4MIB.0.2 1
ciscoBgp4MIB.0.6 2
ciscoBgp4MIB.0.7 2
ciscoBgp4MIB.0.8 2
RP/0/RSP0/CPU0:PE2#show running-config snmp-server
Mon Feb 25 15:00:20.221 PST
snmp-server vrf mse_1001
context public
snmp-server community public RW
snmp-server traps bgp cbgp2
snmp-server traps bgp
snmp-server traps vrrp events
snmp-server ifindex persist
RP/0/RSP0/CPU0:PE2#conf t
Mon Feb 25 15:02:35.935 PST
RP/0/RSP0/CPU0:PE2(config)#int gi0/3/0/0.1001
RP/0/RSP0/CPU0:PE2(config-subif)#no shut
RP/0/RSP0/CPU0:PE2(config-subif)#commit
Mon Feb 25 15:02:42.609 PST
RP/0/RSP0/CPU0:Feb 25 15:02:43.369 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 101.1.1.2 Up (VRF: mse_1001)
RP/0/RSP0/CPU0:Feb 25 15:02:43.606 : config[65903]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'lab'. Use 'show configuration commit changes 1000000209' to view the changes.
RP/0/RSP0/CPU0:PE2(config-subif)#LC/0/3/CPU0:Feb 25 15:02:44.223 : bfd_agent[124]: %L2-BFD-6-SESSION_STATE_UP : BFD session to neighbor 101.1.1.2 on interface GigabitEthernet0/3/0/0.1001 is up
RP/0/RSP0/CPU0:Feb 25 15:02:44.286 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.1 qlen:0
RP/0/RSP0/CPU0:Feb 25 15:02:44.286 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:1
RP/0/RSP0/CPU0:Feb 25 15:02:44.287 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.1 qlen:2
RP/0/RSP0/CPU0:Feb 25 15:02:44.287 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:3
RP/0/RSP0/CPU0:Feb 25 15:02:44.288 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.1 qlen:4
RP/0/RSP0/CPU0:Feb 25 15:02:44.289 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:5
RP/0/RSP0/CPU0:Feb 25 15:02:44.289 : snmpd[1112]: t8 Queueing trap:bgp.0.1 qlen:6
RP/0/RSP0/CPU0:Feb 25 15:02:44.290 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.5 qlen:7
RP/0/RSP0/CPU0:Feb 25 15:02:44.291 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.1 qlen:8
RP/0/RSP0/CPU0:Feb 25 15:02:44.291 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:9
RP/0/RSP0/CPU0:Feb 25 15:02:44.292 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.1
RP/0/RSP0/CPU0:Feb 25 15:02:44.292 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
RP/0/RSP0/CPU0:Feb 25 15:02:44.292 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.1
RP/0/RSP0/CPU0:Feb 25 15:02:44.293 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
RP/0/RSP0/CPU0:Feb 25 15:02:44.293 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.1
RP/0/RSP0/CPU0:Feb 25 15:02:44.293 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
RP/0/RSP0/CPU0:Feb 25 15:02:44.293 : snmpd[1112]: t10 Processing trap bgp.0.1
RP/0/RSP0/CPU0:Feb 25 15:02:44.294 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.5
RP/0/RSP0/CPU0:Feb 25 15:02:44.294 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.1
RP/0/RSP0/CPU0:Feb 25 15:02:44.294 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
RP/0/RSP0/CPU0:PE2(config-subif)#
RP/0/RSP0/CPU0:PE2(config-subif)#end
RP/0/RSP0/CPU0:Feb 25 15:02:48.825 : config[65903]: %MGBL-SYS-5-CONFIG_I : Configured from console by lab on vty0 (223.255.254.249)
RP/0/RSP0/CPU0:PE2#conf tRP/0/RSP0/CPU0:Feb 25 15:02:49.418 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:0
RP/0/RSP0/CPU0:Feb 25 15:02:49.419 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:1
RP/0/RSP0/CPU0:Feb 25 15:02:49.420 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
RP/0/RSP0/CPU0:Feb 25 15:02:49.421 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
show running-config snmp-server RP/0/RSP0/CPU0:Feb 25 15:02:50.510 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 1011:1:1::2 Up (VRF: mse_1001)
show snmp trapLC/0/3/CPU0:Feb 25 15:02:51.046 : bfd_agent[124]: %L2-BFD-6-SESSION_STATE_UP : BFD session to neighbor 1011:1:1::2 on interface GigabitEthernet0/3/0/0.1001 is up
RP/0/RSP0/CPU0:Feb 25 15:02:51.516 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:0
RP/0/RSP0/CPU0:Feb 25 15:02:51.516 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.5 qlen:1
RP/0/RSP0/CPU0:Feb 25 15:02:51.517 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:2
RP/0/RSP0/CPU0:Feb 25 15:02:51.519 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
RP/0/RSP0/CPU0:Feb 25 15:02:51.520 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.5
RP/0/RSP0/CPU0:Feb 25 15:02:51.520 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7
Mon Feb 25 15:02:54.118 PST
TrapOID Number of Times
bgp.0.1 1
bgp.0.2 1
ciscoBgp4MIB.0.1 5
ciscoBgp4MIB.0.2 1
ciscoBgp4MIB.0.5 2
ciscoBgp4MIB.0.6 2
ciscoBgp4MIB.0.7 10
ciscoBgp4MIB.0.8 2
RP/0/RSP0/CPU0:PE2#
Thanks
Parthiv -
Snmp traps on switchport security violation
Hi,
I configured switch interface to switchport security in sticky mode with violation is restricted. The snmp traps are continously sending to log server if violation occur. I want to fix the snmp trap only one time if any violation in mac-address. Any suggestion???
Thanks,
AmanI am not sure I understand the question.
From what I understand you have the following assigned to an interface:
switchport port-security mac-address sticky
switchport port-security violation restrict
(some sort of snmp trap command)
You currently are recieving snmp trap alerts more frequently then you want. If this is correct check out this link:
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094a05.shtml
If you still have questions let us know and good luck.
Maybe you are looking for
-
HELP NEEDED. Cannot connect to Music Store.
After upgrading to iTunes 6 I have been unable to connect to the Music Store or download any tracks. Its not my Norton Internet Security and my Windows Firewall is off. In fact, nothing has changed on my PC apart from upgrading iTunes, at which point
-
Danish characters u00E5,u00E6 in Mail Sender Adapater
Hi experts, I have a problem with special characters. I have a txt file with ø,å,æ characters in words. It's sendt as mail attachment, that swapt with PayloadSwapBean and transformed to xml with MessageTransformBean. I get an xml with � signs instead
-
My Iphone 4 is disabled as a result of someone making too many attempts at guessing my passcode. I know my passcode and do NOT want to "restore" my phone. Is there a way for me to use my passcode to unlock it once it has been disabled?
-
Delete namespace and prefix with Seeburger X.400 receiver
Dear experts, I have a problem deleting a namespace and prefixes "ns0" from an XML output. When testing I was using an FTP receiver adapter with the AnonymizerBean which worked perfectly. I referred to: /people/stefan.grube/blog/2007/02/02/remove-nam
-
Convertion string to Calender object
The input string format is "hh-mm-ss". How can I convert to Calender object. Can anybody suggest ? Thanks Pravat