Monitor RSSI with SNMP

I have project where I have 24 Cisco 2602 AP as a wireless bridge. (12 pcs root bridge and 12 pcs of non-root)
I would like to use "whatsup Gold" to monitor the RSSI on my wireless links.
I have been told that if information is availeble through SNMP, it is possible to monitor in "Whatsup Gold"
I'm a little "green" when we're talking snmp.
Are there someone that can tell me what information I need from my Cisco access points to monitor the RSSI via SNMP
Hope there is a friendly auxiliary will help :-) I have project where I have 24 Cisco 2602 AP as a wireless bridge. (12 pcs root bridge and 12 units of non-root)
I would like to take "whatsup Gold" to overgåge RSSI on my wireless links.
I have been told that if information is tilgångelige via SNMP, it is possible to monitor in "whatsup"
I'm a little "green" when we're talking snmp.
Are there some that can tell me what information I need from my Cisco access points to monitor the RSSI via SNMP
Hope there is a friendly soul that will help :-)
/Lars

Originally Posted by markcasey
Hi
I had a problem with my GMS services
The GroupWise Sync Agent had stopped
Is it possible to monitor the status of this service using SNMP ??
Thanks in advance
Mark
We use snmp with zenoss and it can for example monitor the status of the ports gms uses.
Thomas

Similar Messages

Would like to monitor teaming with snmp

Hello,
I would like to use snmp to monitor the state of teaming/vibe. I can't seem to find much information on the subject in general and none specifically to do with teaming/vibe. Does teaming/vibe have an OID? If not, is there some way I can give it one? It is a java process and I can monitor a process such as java with snmp but I can't differentiate between different java processes such as indexServer and icecore. Any information or links would be appreciated.
Thanks!
Toney.

toneyc,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Monitoring VLANs with SNMP

Can someone remind me how I can monitor a VLAN other than VLAN 1 with SNMP I think it's something along the lines of public@....
Any help would be much appreciated.
Thanks
Jon

The @ represents community string indexing. So if you wanted to get snmp output for VLAN 200 you would do something like this:
snmpwalk -Os -c public@200 -v 2c 10.1.1.1 dot1dTpFdbAddress
Keep in mind the flags I use above are from my specific snmpwalk utility (net-snmp) but you would add the @ to the comm string and then the value to collect the data

Monitoring Cpu with SNMP

Hello,
I'am trying to monitor the CPU usage with snmp.
I found ssCpuRawIdle.0 but each time I do :
# snmpget -v 2c -c public localhost ssCpuRawIdle.0
UCD-SNMP-MIB::ssCpuRawIdle.0 = Counter32: 0
The answer is always 0.
I think is wrong, there must be value, but I cannot interdstand what.
snmpd is running and I can obtain answer with other request.
Thanks in advance fr your help.
Jacques

I will add this to my queue of SNMP bugs.
Incorrect data like this are because OS X looks like FreeBSD to the Net-SNMP project, but OS X has some new APIs/SPIs/KPIs that deprecate or eliminate those used by FreeBSD in an attempt to be a more secure consumer-oriented OS.
Macs. Lotsa macs. All without SNMP.

PRI monitoring problem with SNMP

Hello
I'm having some problems with PRI monitoring.
I'm using cpmDS1ActiveDS0 MIB on a 3800 VoIP gateway with 4 PRI (2x2) (IOS 12.4(4)T1)
1.3.6.1.4.1.9.10.19.1.1.9.1.3.0.0 - I can see PRI 0/0/0 total number of calls
1.3.6.1.4.1.9.10.19.1.1.9.1.3.0.1 - I can see PRI 0/0/1 total number of calls
1.3.6.1.4.1.9.10.19.1.1.9.1.3.1.0 - Error
1.3.6.1.4.1.9.10.19.1.1.9.1.3.1.1 - Error
1.3.6.1.4.1.9.10.19.1.1.9.1.3.0.0.x - Error
1.3.6.1.4.1.9.10.19.1.1.9.1.3.0.1.x - Error
The PRIs that we want to see are 0/1/0 e 0/1/1...... (bad luck!)
Do I need to make some special configuration on the Router?

Have you had any responses to this issue ?
I am running into exactly the same issue and have tried everything I can find to get these individual PRI (count of channels/lines in use) statistics.
Just for the record, here are some of the SNMP OIDs that I have tried (the ISRs do respond to them, only thing is, the data they send back is mostly rubbish...) the output below is from two separate routers, with different versions of IOS running (which is shown in the sysdescr response):
Note that the query in red in the second router was responded to with a valid response in the FIRST router...
All of these OIDs have been suggested at various sites online as useable SNMP OIDs for the ISR, but at other sites, they are suggested to be faulty. I have found no definitive statement for ways to get these stats successfully on the ISR platform (which amazes me.) Output below is using net-snmp to collect the stats.
I welcome any suggestions as to how this can be done reliably for the ISR, and what IOS versions WILL work. (since I am getting way different reponses to the same OIDs on the two versions below).
You'll see that for the second (DC) router below, the values are always Zero.
Yet I can guarantee that the ACTUAL stats are NEVER zero during the time period queried.
Timestamp: 2010-12-27_13:56:31.73
C:\usr\share\snmp\mibs>snmptranslate -On CISCO-POP-MGMT-MIB::cpmActiveDS0s.0
.1.3.6.1.4.1.9.10.19.1.1.4.0
C:\usr\share\snmp\mibs>snmptranslate -On CISCO-POP-MGMT-MIB::cpmDS1ActiveDS0s.0.0
.1.3.6.1.4.1.9.10.19.1.1.9.1.3.0.0
C:\usr\share\snmp\mibs>snmptranslate -On CISCO-POP-MGMT-MIB::cpmISDNCfgBChannelsInUse.0
.1.3.6.1.4.1.9.10.19.1.1.3.0
C:\usr\share\snmp\mibs>snmptranslate -On CISCO-VOICE-DIAL-CONTROL-MIB::cvCallActiveDS0s.0
.1.3.6.1.4.1.9.9.63.1.3.3.0
C:\usr\share\snmp\mibs>snmptranslate -On ISDN-MIB::isdnBearerOperStatus.32
.1.3.6.1.2.1.10.20.1.2.1.1.2.32
From ROUTER2 - HQ:
SNMPv2-MIB::sysDescr.0 = STRING: Cisco IOS Software,
3800 Software (C3825-ADVIPSERVICESK9-M),
Version 12.4(15)T8, RELEASE SOFTWARE (fc3)
CISCO-POP-MGMT-MIB::cpmActiveDS0s.0 = Gauge32: 14
CISCO-POP-MGMT-MIB::cpmDS1ActiveDS0s.0.0 = Gauge32: 14
CISCO-POP-MGMT-MIB::cpmISDNCfgBChannelsInUse.0 = Gauge32: 7
CISCO-VOICE-DIAL-CONTROL-MIB::cvCallActiveDS0s.0 = Gauge32: 7 interfaces
ISDN-MIB::isdnBearerOperStatus.32 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.33 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.34 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.35 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.36 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.37 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.38 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.39 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.40 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.41 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.42 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.43 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.44 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.45 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.46 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.47 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.48 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.49 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.50 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.51 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.52 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.53 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.54 = INTEGER: idle(1)
From ROUTER2 - DC:
SNMPv2-MIB::sysDescr.0 = STRING: Cisco IOS Software,
3800 Software (C3825-ADVIPSERVICESK9-M),
Version 12.4(18), RELEASE SOFTWARE (fc1)
CISCO-POP-MGMT-MIB::cpmActiveDS0s.0 = Gauge32: 0
CISCO-POP-MGMT-MIB::cpmDS1ActiveDS0s.0.0 = Gauge32: 0
CISCO-POP-MGMT-MIB::cpmISDNCfgBChannelsInUse.0 = Gauge32: 0
CISCO-VOICE-DIAL-CONTROL-MIB::cvCallActiveDS0s.0 = No Such Object available on this agent at this OID
ISDN-MIB::isdnBearerOperStatus.32 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.33 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.34 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.35 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.36 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.37 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.38 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.39 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.40 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.41 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.42 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.43 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.44 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.45 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.46 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.47 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.48 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.49 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.50 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.51 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.52 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.53 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.54 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.81 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.82 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.83 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.84 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.85 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.86 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.87 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.88 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.89 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.90 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.91 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.92 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.93 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.94 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.95 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.96 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.97 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.98 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.99 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.100 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.101 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.102 = INTEGER: idle(1)
ISDN-MIB::isdnBearerOperStatus.103 = INTEGER: idle(1)
Timestamp: 2010-12-27_13:56:35.02

Monitoring hardware with SNMP

I am performing a Systems Admin role for 30 Solaris 10 systems (consisting of 67 Solaris zones and domains) at present.
My support team colleagues have installed Nagios (an open source SNMP based monitoring software) to enable alerting should any issues occur.
This works fantastically for our database tables, applications, and even elements such as memory usage, CPU usage, filesystem usage, processes running etc.
However, what this seems to lack is the ability to detect physical hardware failures.
For example, over the past month, I have by pure chance (walking past the systems and seeing error lights, or probing the system for training purposes to the other Sys Admin in my team) discovered two hardware failures, which we are not picking up with Nagios.
These were 1) a hard disk failure - all filesystems on this hard disk were RAID 1 metadevices, so from an filesystem / Nagios POV there was no error.
2) A PSU failure - there is a redundant PSU in this system, so we did not lose the system, and from a functionality POV we did not have any issues.
Each of these errors shows up in the messages files, and also in the hardware probes Sys Admins run, such as prtdiag, or cfgadm for the disk, but Nagios failed to detect them.
So - my question is around whether it is possible to use snmp to query the hardware status on a Solaris 10 system?
I know SunMC is a monitoring suite which uses SNMP tables to query usage and hardware, so know it should be possible - I am just unable to figure out which tables to query, etc.
Help, please!

What we're doing is writing a custom nagios module to scan /var/adm/messages and watch for problems. The hard bit it tuning it so it alerts for real problems and ignores the dross.

Monitoring Messaging with SNMP, anyone?

Hi,
is there anyone (successfully) monitoring his/her Messaging Server through SNMP?
I have 2004Q2 under Solaris 9. I successfully started the Master Agent (.../mps/serverroot/plugins/snmp/magt/magt -p 48472 CONFIG INIT), and an snmpwalk fails when it is stopped (so I am sure no other SNMP deamon is running on the server).
I successfully start subagents following what is written in the SNMP chapter of the Messaging Admin Guide.
An snmpwalk on the public community returns no "JES" MIBs, but only the standard ones.
So, is someone monitoring a JES Messaging server through SNMP? If so, were extra configuration steps necessary?
Thanks

Thanks!
I had everything set-up, but was missing the OID parameter in the snmpwalk query.
For the records, adding "-m ALL" helps snmpwalk to resolve the dotted notation into somewhat meaningful strings, provided MIB files have been installed:
snmpwalk -v 1 -m ALL -c public srvmsg01.csi.it mib-2.27
snmpwalk -v 1 -m ALL -c public srvmsg01.csi.it mib-2.28
("-m ALL" is a quick solution, the single file might be specified for each MIB query, I think)
I am having a look at Big Brother, altought my organization uses MRTG for basic performance monitoring.
Paolo

Monitoring the Cisco ACE module with SNMP

We use 2 redundant Cisco ACE loadbalancer in our datacenter
The models are ACE20-MOD-K9 with software A2(2.0)
Does anybod know how to monitor the environment (cpu, memory) of such a module with snmp?
We were not able to find an applicable MIB for that module.
The CISCO-PROCESS-MIB.oid (ftp://ftp.cisco.com/pub/mibs/oid/CISCO-PROCESS-MIB.oid) seems not to reflect the correct oid's.
What are the correct oid's for cpu and memory?
Where can I find a detailed documentation for snmp-monitoring the cisco ace module?
thanks

Hi Patrik,
to monitor the ACE I use these two MIB's:
ftp://ftp.cisco.com/pub/mibs/v2/CISCO-SLB-MIB.my
ftp://ftp.cisco.com/pub/mibs/v2/CISCO-ENHANCED-SLB-MIB.my
Example for CPU:
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Normale Tabelle";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat: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:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
cpmCPUTotalEntry 1.3.6.1.4.1.9.9.109.1.1.1.1
The resource usage and other interesting things you will find with a MIB browser.
Achim

Monitor with SNMP

Hello,
we would like to monitor client connection by webapp with SNMP.
How can i make this?
Wich OID ?
THKS in adv.

Start here:
http://edocs.bea.com/wls/docs81/snmpman/index.html
And then here:
http://edocs.bea.com/wls/docs81/snmp/index.html
~Ryan Upton
pasbien wrote:
Hello,
we would like to monitor client connection by webapp with SNMP.
How can i make this?
Wich OID ?
THKS in adv.

Using JConsole in combination with SNMP

I have created a simple agent (using version 5 JDK) to handle an MBean. Within this agent I have created two adapters; an HTML and SNMP adapter. The HTML adapter is working fine via the browser (i can execute the operations on the MBean).
Question is; Can I use JConsole to connect to the SNMP adapter?; if not how then?
Code:
public void addSnmpAdapter(int port)
               throws Exception {
          // Register and start the SNMP adapter
          SnmpAdaptorServer snmpAdapter = new SnmpAdaptorServer();
          ObjectName snmpAdapterName = new ObjectName(
                    "MBeanAgent:name=snmpadapter,type=SNMP,port=" + port);
          snmpAdapter.setPort(port);
          mbs.registerMBean(snmpAdapter, snmpAdapterName);
          snmpAdapter.start();
          System.out.println("SnmpAdapter on port " + port);
     }Start command:
java -Dcom.sun.management.jmxremote -Dcom.sun.management.snmp.acl=false -Dcom.sun.management.snmp.port=162 MBeanAgent

Hi Willem,
No you cannot use JConsole to "connect to the SNMP adapter".
JConsole is a JMX Console, not an SNMP console.
What are you trying to do with that SNMP Adaptor anyway?
If you use Java DMK to start an SNMP adapter, and do nothing more,
the adaptor will show you nothing. It is empty. You still need to
generate, implement, and add at least one SNMP MIB to the adaptor.
For more information on this, see the Java DMK documentation.
http://java.sun.com/products/jdmk/jdmk_docs.html
Java SE 5.0 has a built-in SNMP agent that can be started using System
properties on the Java command line. This agent implements a single MIB,
the JVM-MANAGEMENT-MIB, that exposes the JVM Management and Monitoring
data through SNMP.
See here for more info on the JVM SNMP Agent:
What is the JVM SNMP Agent?
http://blogs.sun.com/jmxetc/entry/what_is_the_jvm_snmp
See also here for a discussion of using SNMP versus JMX to monitor your JVMs.
JVM Monitoring: JMX or SNMP?
http://blogs.sun.com/jmxetc/entry/jmx_vs_snmp
Hope this helps,
-- daniel
JMX, SNMP, Java, etc...
http://blogs.sun.com/jmxetc

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.

Monitoring JMX with What's Up Gold v11

I'm not a Java developer but work with a lot of them (I am in IT, not dev). We use What's Up Gold to monitor our servers and applications. We would like to monitor our Java application with What's Up Gold. This includes monitoring Java and Tomcat.
Any help would be appreciated!
We've not been able to even get simple SNMP monitoring going. Would like something more like the JConsole within What's Up Gold.
Thanks,
Chris

Hi,
I am not too sure about how you could possibly plug any of this in "What's Up Gold" as I don't
know this product, but the apache site has some doc about monitoring Tomcat with JMX, using
a JMX ant task on the client side.
http://tomcat.apache.org/tomcat-5.5-doc/monitoring.html
I have also written some example to show how to get at the JVM information using java, or jruby..
See:
http://blogs.sun.com/jmxetc/entry/a_small_program_that_prints
http://blogs.sun.com/jmxetc/entry/how_to_retrieve_jvm_information
http://blogs.sun.com/jmxetc/entry/how_to_retrieve_remote_jvm
Hope this helps,
-- daniel
http://blogs.sun.com/jmxetc

Monitor Ciscoworks using SNMP

Hi All,
I would like to monitor Ciscoworks using SNMP. If there are any documents with regards to this configuration, would appreciate if you can share your inputs. Thanks!
Regards,
Manoj

You can send SNMP traps to many management solutions. Sun would probably recommend Sun Management Center.
http://www.sun.com/software/products/sunmanagementcenter/
HTH

SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

SAP ECC error:'Migration Monitor' exits with error code 103.

Hi All,
I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
I am stuck at the import ABAP.Getting error
ERROR 2008-08-08 16:10:53
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
1) imort_monitor.java.log-->contains
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 0, completed 18, failed 0, total 19.
Loading of 'SAPVIEW' import package: ERROR
Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
2)import_monitor.log
ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPVIEW' import package is interrupted with R3load error.
Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPVIEW.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
INFO: 2008-08-08 16:10:52
All import packages are processed.
WARNING: 2008-08-08 16:10:52
1 error(s) during processing of packages.
INFO: 2008-08-08 16:10:52
Import Monitor is stopped.
3)SAPVIEW.log
error message returned by DbSl:
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001" ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001", T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
DbSlExecute: rc = 103
(SQL error -942)
error message returned by DbSl:
(DB) INFO: disconnected from DB
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
Only SAPDB: SAPSID srvice of SAP DB is only up.
No other services of database are up.And i am not able to up the other services also.
Is it required to up the other services?
If not?
Why this error is occuring?
Any help will be appreciated.
Thanks&Regards
Manisha das

Hello Manisha,
The one of the possible reasons for this is due to lack of H/W.
Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
If the issue is with H/W, then this should fix the issue.
Hope it helps,
Regards,
Satish.

Monitor RSSI with SNMP

Similar Messages

Maybe you are looking for