Snmp/bgp traps
Hi
Is there anyway of limiting the type of traps to be sent to a particular SNMP management station? When I enable snmp-server enable trap ds1 e.g., I would only like that type of trap to go to SNMP Server A and not SNMP Server B. Can't think of any way myself?
Regards
Mary
Hi Farrukh
When I type the command snmp-server host 10.50.1.228 traps snmp ? , I get the traps below but not linkup linkdown. The router is running flash:c2800nm-entservicesk9-mz.124-7a.bin. Output of what I see below.
Router_A#(config)#snmp-server host 10.50.1.228 traps snmp ?
atm Allow SNMP atm traps
bgp Allow BGP state change traps
bstun Allow bstun event traps
bulkstat Allow Data-Collection-MIB traps
cnpd Allow NBAR Protocol Discovery traps
config Allow SNMP config traps
config-copy Allow SNMP config-copy traps
cpu Allow cpu related traps
dlsw Allow dlsw traps
dnis Allow SNMP DNIS traps
ds0-busyout Allow ds0-busyout traps
ds1 Allow SNMP ds1 traps
ds1-loopback Allow ds1-loopback traps
ds3 Allow SNMP ds3 traps
dsp Allow SNMP DSP traps
dspu Allow dspu event traps
eigrp Allow SNMP EIGRP traps
entity Allow SNMP entity traps
envmon Allow environmental monitor traps
event-manager Allow SNMP Embedded Event Manager traps
flash Allow SNMP FLASH traps
frame-relay Allow SNMP frame-relay traps
hsrp Allow SNMP HSRP traps
icsudsu Allow SNMP ICSUDSU traps
ipmobile Allow SNMP ipmobile traps
ipmulticast Allow SNMP ipmulticast traps
isdn Allow SNMP ISDN traps
l2tun-session Allow SNMP L2 tunnel protocol traps
mpls-ldp Allow SNMP MPLS label distribution protocol traps
mpls-traffic-eng Allow SNMP MPLS traffic engineering traps
mpls-vpn Allow SNMP MPLS Virtual Private Network traps
msdp Allow SNMP MSDP traps
mvpn Allow Multicast Virtual Private Network traps
ospf Allow OSPF traps
pim Allow SNMP PIM traps
rsrb Allow rsrb event traps
rsvp Allow RSVP flow change traps
rtr Allow SNMP Response Time Reporter traps
sdlc Allow sdlc event traps
sdllc Allow sdllc event traps
snmp Allow SNMP-type notifications
stun Allow stun event traps
syslog Allow SNMP syslog traps
tty Allow TCP connection traps
udp-port The notification host's UDP port number
voice Allow SNMP Voice traps
vrrp Allow SNMP vrrp traps
vsimaster Allow SNMP vsimaster traps
vtp Allow SNMP VTP traps
x25 Allow x25 event traps
xgcp Allow XGCP protocol traps
Any ideas?
Regards
Mary
Similar Messages
-
I trying to enable snmp traps on the CSM-S in order to get notification through HP Openview Network Node Manager that a 'fault tolerant' event has taken place. I am running 2.1(5) code.
I found the command reference for the CSMS 2.x code:
http://www.cisco.com/en/US/customer/docs/interfaces_modules/services_modules/csms/2.1.1/command/reference/s.html#wp1057213
There is a reference to the command: snmp enable traps slb ft
This is supposed to send an SNMP trap when the CSM transitions from standby to active after detecting a failure in its fault tolerant peer.
This example shows how to enable fault tolerant traps:
Cat6k-2(config-module-csm)# snmp enable traps slb ft
This command is not available in CSM configuration mode. In fact, there are no snmp commands at all in the CSM config mode.
Do I have to enable something globally on the 6500 first?The "config" trap enables the ciscoConfigManEvent notification, which triggers when you exit configuration mode or do a SNMP set.
The "config-copy" and "copy-config" traps are the same thing on different platforms, and enables the ccCopyCompletion trap, and triggers when a configuratio copy operation via SNMP completes.
The "config-ctid" trap enables either the ccmCTIDRolledOver or ciscoConfigManCTIDNotifyGroup, which appears to be related to the configuration change tracking identifier feature. -
Hi,
We are trying to configure SNMP V3 trap on our routers and switches. I can able send V3 trap to our NMS, but it is mentioned that we need contextengine and contextname to process the trap.
We have configured a simple TRAP configuration without aut and priv.
How can i find the context information.Is this is configurable.How ?
Here is my trap configuration
snmp-server user TRAP TRAP v3
snmp-server group TRAP v3 noauth notify *tv.FFFFFFFF.FFFFFFFF.FFFFFFFF.FFFFFFFF0F
snmp-server host 10.4.x.x version 3 noauth TRAP
Thx
-uthayYou don't need context information for sending traps. Your NMS will need to know the SNMP engineID of the agent, however. You can find that with the "show snmp engine" command. You will then need to configure your NMS with the agent's engineID and authentication/privacy parameters.
-
Hey Guys,
Can someone explain to me - or point me in the direction - where I may be better able to determine the difference between the following taps.
config Enable SNMP config traps
config-copy Enable SNMP config-copy traps
config-ctid Enable SNMP config-ctid traps
copy-config Enable SNMP config-copy traps
Thanks
NikThe "config" trap enables the ciscoConfigManEvent notification, which triggers when you exit configuration mode or do a SNMP set.
The "config-copy" and "copy-config" traps are the same thing on different platforms, and enables the ccCopyCompletion trap, and triggers when a configuratio copy operation via SNMP completes.
The "config-ctid" trap enables either the ccmCTIDRolledOver or ciscoConfigManCTIDNotifyGroup, which appears to be related to the configuration change tracking identifier feature. -
Hi all
By using snmp4j packege I have written a trap listener code for snmpV3, but am not able to catch any trap. In etherial i am getting snmp trap.
Could anyone please tell me whats wrong with my program...
public class V3trapListen {
public V3trapListen() { }
public synchronized void start(String address) throws Exception {
UdpAddress listenAddress = new UdpAddress(address);
ThreadPool threadPool = ThreadPool.create("DispatcherPool", 2);//1
MessageDispatcher mtDispatcher =
new MultiThreadedMessageDispatcher(threadPool,
new MessageDispatcherImpl());//2
// add message processing models
mtDispatcher.addMessageProcessingModel(new MPv1());
mtDispatcher.addMessageProcessingModel(new MPv2c());
mtDispatcher.addMessageProcessingModel(new MPv3());
// add default security models
SecurityProtocols.getInstance().addDefaultProtocols();
Snmp snmp = new Snmp(mtDispatcher);
CommunityTarget target = new CommunityTarget();
if(target != null) {
target.setCommunity(new OctetString("public"));
target.setAddress(listenAddress);
target.setVersion(SnmpConstants.version3);
} else {
System.out.println("Unable to create Target object");
System.exit(-1);
CommandResponder trapPrinter = new CommandResponder() {
public void processPdu(CommandResponderEvent e) {
PDU command = e.getPDU();
if (command != null) {
System.out.println("\n"+e.getPDU());
if (snmp.addNotificationListener(listenAddress, trapPrinter)) {
snmp.listen();
System.out.println("snmp.addNotificationListener returned TRUE ");
System.out.println("Waiting for [trap] on "+listenAddress.toString());
try {
this.wait();
catch(InterruptedException ex) {
System.out.println("Caught InterruptException: "+ex.toString());
catch(Exception ex) {
System.out.println("CaughtException: "+ex.toString());
} else {
System.out.println("snmp.addNotificationListener returned FALSE");
System.out.println("TestListener closing...");
regards
sanjayI use Ciscoworks LMS to send me emails when a given syslog arrives. (syslog, automated Actions)
It can also take SNMP TRAPS, not sure if it can actually send you email when it gets a specific TRAP, but i guess it can.
Any linux server with the right basic tools will also do the same.
castlerock SNMPc is a very good SNMP tool, and can search and email among other things.
Also gives you a Red,amber, green view and polls devices f.x. for a given service, like a TCP port.
highly customizable. -
Problems understanding SNMP OIDs/Traps
Dear Community,
i would be very glad if you could help me with this thopic...i seem to have some trouble understanding it...
Here an example:
2010-01-18 06:28:44 Unknown alert received from device ber-be-swt01.is24-rz.de of type SwCiscoIOS. Device Time 82+21:21:53. (Trap type 1.3.6.1.4.1.9.9.43.2.0.1.6.0)\nTrap var bind data: \nOID: 1.3.6.1.4.1.9.9.43.1.1.6.1.3.738 Value: 1\nOID: 1.3.6.1.4.1.9.9.43.1.1.6.1.4.738 Value: 4\nOID: 1.3.6.1.4.1.9.9.43.1.1.6.1.5.738 Value: 2\nOID: 1.3.6.1.6.3.18.1.3.0 Value: 10.3.32.2
Ok. Let's take the trap type:
1.3.6.1.4.1.9.9.43.2.0.1.6.0
Searching with SNMP Object Navigator (http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en) i only get as far as:
1.3.6.1.4.1.9.9.43.2.0.1 -> ...6.0 is unkown.
If i search for the OID
1.3.6.1.4.1.9.9.43.1.1.6.1.3.738 for example
i get the following:
1.3.6.1.4.1.9.9.43.1.1.6.1.3 -> ...738 is unknown.
This happens with a lot of OIDs for me (not just these ones). If i understand the OID correctly, this could be a command from the command line which forced this trap.
So what's the .738 for? Why couldn't it be recognised by the search-function?
In advance i like to thank you for any feedback.
Sven SchlingloffTry using my search and translate tool at http://jaguar.ir.miami.edu/~marcus/snmptrans.html . If you do, you will see that 1.3.6.1.4.1.9.9.43.2.0.1.6.0 translates to ciscoConfigManEvent. The OID 1.3.6.1.4.1.9.9.43.1.1.6.1.3.738 translates to ccmHistoryEventCommandSource. However, ccmHistoryEventCommandSource'd OID is 1.3.6.1.4.1.9.9.43.1.1.6.1.3. The .738 is the specific instance. The definition of ccmHistoryEventCommandSource is:
"The source of the command that instigated the event."
This object comes from the ccmHistoryEventTable which is indexed by the ccmHistoryEventIndex object. The definition of that object is:
"A monotonically increasing integer for the sole
purpose of indexing events. When it reaches the
maximum value, an extremely unlikely event, the agent
wraps the value back to 1 and may flush existing
entries."
So, the 738 is simply a unique number which identifies this particular history event. -
HI,
Cisco 7600 running "c7600s72033-advipservicesk9-mz.122-33.SRE6.bin"
what i'm trying to do is get the bgp peer state using the OID .1.3.6.1.2.1.15.3.1.2 , however , i only get the ipv4 adresses , is there a way i can get the ipv6 peer states via snmp?
SNMPv2-SMI::mib-2.15.3.1.2.192.168.0.200 = INTEGER: 6
i've put the generic output of a snmp walk against de device , with generic ip "192.168.0.200"
Thx in advance for your time.bump
-
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 trapping PRI channels up/down
Hi guys.
I am re-configuring some routers to generate traps for our new monitoring tool.
I have noticed that after I applied the snmp trap configs that we are getting traps for PRI channels (30 voice channels), which I wouldn´t like to. This happens when users are using the voice channels on demand. When they hang up, the used channel goes down and I get a trap.
Basically, regargint the controller, the only interface that I must monitor is the signaling one (my case is the channel 0/3/0:15) or if the entire controller goes down.
Below, the snmp trap config:
snmp-server ifindex persist
snmp-server trap-source Loopback0
snmp-server enable traps snmp linkdown linkup coldstart warmstart
snmp-server enable traps envmon
snmp-server enable traps isdn layer2
snmp-server enable traps isdn chan-not-avail
snmp-server enable traps isdn ietf
snmp-server enable traps bgp
snmp-server enable traps hsrp
snmp-server enable traps ipsla
snmp-server enable traps voice poor-qov
Could you please help me to figure out how I can solve this?
Also, if you guys have any other advises and more ways to monitor the voice environment.
Thanks in advanceDuplicate post.
Go HERE. -
3750 sw is not sending SSH login failure SNMP trap
Hi experts,
I want to make my switch send trap when failed SSH login is detected. I found the "login Enhancement" feature and enabled the trap and logging for the failed attempt.
3750# sh run | in login
aaa authentication login default local
login delay 1
login on-failure
3750# sh login
A login delay of 1 seconds is applied.
No Quiet-Mode access list has been configured.
All failed login is logged and generate SNMP traps.
Router NOT enabled to watch for login Attacks
Then I enabled all the traps except the one for the syslog (because I don't want all the log messages are sent as SNMP traps...)
(config)# snmp-server enable traps
(config)# no snmp-server enable traps syslog
(config)# snmp-server host 10.1.1.1 mysnmpkey
Now when I try to login with incorrect password I do see the log but I don't receive the trap...
Nov 23 12:39:27: %SEC_LOGIN-4-LOGIN_FAILED: Login failed [user: admin] [Source: 10.1.1.1] [localport: 22] [Reason: Login Authentication Failed] at 12:39:27 EST Wed Nov 23 2011
Of course when I enable the "syslog" trap I see something but that's more just for this log message
Any idea why??
My 3750-24TS-E is running
Cisco IOS Software, C3750 Software (C3750-IPSERVICESK9-M), Version 12.2(55)SE3, RELEASE SOFTWARE (fc1)
Thanks!
DifanHey Smitesh thanks for the reply. However my switch doesn't support the aaa_server trap...
#snmp-server enable traps ?
auth-framework Enable SNMP CISCO-AUTH-FRAMEWORK-MIB traps
bgp Enable BGP traps
Mine is a 3750 switch. Is this command for routers?
Thanks,
Difan -
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 -
Hi & Thanks for read it,
I would like to design SNMP event, traps in order to be managed by SNMP Network management platform, like HP OpenView, or other.
It's possible to generate a trap in pl/sql or via enterprise manager on procedure event?
Anyone have test log4plsql for send traps?
Anyone know if it's possible to send traps via OS COMMAND on ORACLE?
ThanksI don't want to use oracle MIB. I want to use my own
MIB.
For example I want to send a trap if process of ETL
fails.I am not expert of SNMP setup but looks like Oracle SNMP support in this respect is kinda limited. Hope others may have better idea. -
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,
CsabaI 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 1.4 SNMP Traps are not converted into Alarms
Hi everybody,
I just configured SNMP Traps on a Cisco Catalyst 3750-x to send to our Cisco Prime Infrastructure 1.4 Appliance.
Now I forced the Switch to send some traps (Power off a Power Supply, Interface errdisable). The only events I see in Alarms & Events on PI is the same information message everytime:
Configuration management event has been recorded in ccmHistoryEventTable.
I think the forced traps should be converted into alarms? Why can't I see them?
Thanks,
MarcOk, I started debugging as you said. I get the following output:
Mar 13 09:28:13.711: SNMP: V2 Trap, reqid 11689, errstat 0, erridx 0
sysUpTime.0 = 198609846
snmpTrapOID.0 = ciscoSyslogMIB.2.0.1
clogHistoryEntry.2.1688 = PM
clogHistoryEntry.3.1688 = 5
clogHistoryEntry.4.1688 = ERR_RECOVER
clogHistoryEntry.5.1688 = Attempting to recover from bpduguard err-disable state on Gi1/0/13
clogHistoryEntry.6.1688 = 198609844
Mar 13 09:28:13.737: SNMP: Queuing packet to xx.xx.xx.xx
Looks like the Switch is sending SNMP Traps from the ciscoSyslogMIB. Is this why PI can't show the Traps and convert it into a alarm?
After this test I configured logging (syslog) to the PI. Now the errors are showed but still not converted into alarms. I just want to be notified by email when such errors occurs.
Thanks,
Marc -
NAC SNMP MAC notification traps not being sent
I have the switch set up for mac notification, and the switch has the below config. But no mac notification traps get sent to the CAM.
interface GigabitEthernet1/0/24 switchport access vlan 800 switchport mode access snmp trap mac-notification added spanning-tree portfast!snmp-server community **** ROsnmp-server community **** RWsnmp-server enable traps snmp linkdown linkupsnmp-server enable traps MAC-Notificationsnmp-server enable traps stpx root-inconsistency loop-inconsistencysnmp-server host 10.101.90.20 version 2c **** snmp-server host 10.101.90.20 **** MAC-Notification snmp
Below is a debug of snmp packets when a host it connected to the switch on port 1/0/24
1y29w: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/24, changed state to up1y29w: SNMP: Queuing packet to 10.101.90.201y29w: SNMP: V2 Trap, reqid 62, errstat 0, erridx 0 sysUpTime.0 = 648642685 snmpTrapOID.0 = snmpTraps.4 ifIndex.10124 = 10124 ifDescr.10124 = GigabitEthernet1/0/24 ifType.10124 = 6 lifEntry.20.10124 = up1y29w: SNMP: Queuing packet to 10.101.90.201y29w: SNMP: V1 Trap, ent products.516, addr 10.202.1.2, gentrap 3, spectrap 0 ifIndex.10124 = 10124 ifDescr.10124 = GigabitEthernet1/0/24 ifType.10124 = 6 lifEntry.20.10124 = up1y29w: SNMP: Packet sent via UDP to 10.101.90.201y29w: SNMP: Packet sent via UDP to 10.101.90.201y29w: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/24, changed state to up
Am I missing something in the config or something?Hello,
Please post your SNMP receiver config on the CAM. Also, can you do a capture on the CAM to see if you're seeing the packets getting there?
To do the capture, in a SSH session, use this command: tcpdump -ieth0 'host ' -s0 -wcapture.pcap
Once you've captured the success/failure, hit Ctrl-C to kill the capture. You can then use WINSCP or any other SCP program to get that file off of the CAM for further analysis.
HTH,
Faisal
Maybe you are looking for
-
Exit Code 7 during early installation process of Creative Suite 5.5 Design Premium
I'm unable to install this software. I'm getting the errors below. I'm running Win 7 Home Premium 64. Does anyone have an idea what I could do next. I tried Safe Mode installation with the same negative results Thanks. Exit Code: 7 -------
-
Copy text with formatting in acrobat api
Is it possible to copy the text with formatting via plugin api to a file?please provide methods or samples to achieve this functionality.
-
White boxes appear around drop shadows in PDF's
I'm exporting a file from InDesign CS3 that contains several graphics that have a drop shadow applied to them (added in InDesign NOT Illustrator). When I view the PDF, there are white boxes that appear behind the graphics with the drop shadows. I nee
-
Use Select Value in JSp on same Page
Sir, In my Jsp page there is one dropdown,sir i want to get that select value in same page so that i can display data on same page below the dropdown based on the <select> value. Is it possible to do this things. Plz reply Soon. Thanks, Regards, Ashi
-
Question on Prefix Indexing preference
Hi, I tried using the prefix index and substring index preferences in index creation and the results are not produced as expected. Here in my case, The table has the below records, id txt 1 coca cola 2 pepsi coca cola The preference used is begin ctx