Quantcast
Channel: Software Communities : Popular Discussions - Management Extensions
Viewing all 1925 articles
Browse latest View live

Error: Partition already exists and still set at Step 3, something is wrong.

$
0
0

Hi, I'm trying to deploy a Mac OS image, but I get the above error message (in the subject). I've attached the debug log, the Hosts, and Deployment files. Please help.


SCCM inventory File Cleaner scheduled task leaves XML files behind.

$
0
0

Hi All,

 

As per recommendations on other posts I have setup scheduled tasks to run the native File Cleaner batch in order to reduce inventory file growth in the QMX Base Framework install file structure on an SCCM targeted installed.

 

Have tuned the parameters in the script to meet client requirements and these are working AOK.

 

My question is around the .XML files that are left in the host folder post clean-up.

 

Is there a way to extend this script to include the removal of these XML files? These files can be as large as 1.2 Mb on some clients so over time will become a problem for my client.

 

Any help would be greatly appreciated.

 

Regards

 

Josh

QMX management extensions reporting to 2 Ops Mgr Management Groups

$
0
0

Can a Quest Operations manager extension system be configured to communicate with two System Center Operations Manager management groups?

We currently use it to monitor non windows devices in SCOM 2007 R2, and would like to monitor to both the existing Ops Mgr system and a new SCOM 2012 system during a staged migration.

Smart Agent Data File Not Extracted to XML / MIF format

$
0
0

Hi All,

 

I have smart agents running on RedHat hosts that successfully complete inventory when called either manually called or run via the CRON job, however the objects never appear in SCCM.

 

From the framework host I can see the listener on 8002 and additionally can successfully telnet from the client machine.

 

Looking at the path %Program Files%\........\Virtual Agent Library\<OS>\Data I can see that the flat data file for the hosts is being correctly parsed, however the MIF and XML data never appears on the path

%Program Files%\........\Virtual Agent Library\<OS>\<HostName>

 

Any suggestions?

 

Josh

Unable to Register ISV Proxy

$
0
0

Hi all,

 

I am standing up a new SCCM site build and I am recieving the following error after running the SCCM connectivity tests

 

Unable to Register ISV Proxy: CSMSManagementPoint::SignHashHexEncode:CryptAcquireCertificatePrivateKey failed with error -2146885621: Cannot find the certificate and pricate key for decryption.

 

The certificate was exported and registered without error. QMX is installed on the same computer as SCCM.  I can see the certificate in the SCCM Console.

We are running SCCM2007 R3 with QMX base framework 4.0.6.67 on Server 2008R2

 

I compared my settings to my old machine and everything looks to be ok.  Any thoughts?

Description of What this Instrumentation Pack Monitors

$
0
0
Detailed Descrption of what the Instrumentation Pack Monitors out of the box is attached. You can also grab/post scripts that enhance this Instrumentation Pack by following this [add HREF] link to the Decriptions and Download Library page for this Intrumentation Pack.

Click here (insert href...etc.) for a complete decription of what this Instrumentation Pack Monitors

Note that a description was attached in htm that I easily cut and pasted from the old eXc site to a htm file using FrontPage.

http://www.excsoftware.com/version3/version3/Product.aspx?ID=b8a57bb9-9793-43e7-b36e-031f69d6f967

I pasted the entire description at the bottom of this thread, too.

This is an example that is expiring on 2/29

www.alcatel.com
Alcatel MOM/OpsMgr2007 Virtual Agent
Category: Networking
Protocol: SNMP
Cost: $349 / Managed Node
Download

Description:
The Virtual agent for Alcatel supports all SNMP capable Alcatel products. If you would like to expand the virtual agent for additional performance and threshold extraction and monitoring, please contact eXc software support.
eXtracted Data Points
Health Input Utilization %
Health IO Utilization %
Health Mem Utilization %
Health CPU Utilization %
Health Chassis Temperature
Health CPU Temperature


What is Monitored?
Error Alcatel: A Software Trouble report is sent by whatever application encountering a problem during its execution and would want to aware the user of for maintenance purpose. chassisTrapsStrLevel(1.3.6.1.4.1.6486.800.1.3.2.4.2.1)=%1, chassisTrapsStrAppID(1.3.6.1.4.1.6486.800.1.3.2.4.2.2)=%2, chassisTrapsStrSnapID(1.3.6.1.4.1.6486.800.1.3.2.4.2.3)=%3, chassisTrapsStrfileName(1.3.6.1.4.1.6486.800.1.3.2.4.2.4)=%4, chassisTrapsStrfileLineNb(1.3.6.1.4.1.6486.800.1.3.2.4.2.5)=%5, chassisTrapsStrErrorNb(1.3.6.1.4.1.6486.800.1.3.2.4.2.6)=%6, chassisTrapsStrcomments(1.3.6.1.4.1.6486.800.1.3.2.4.2.7)=%7, chassisTrapsStrdataInfo(1.3.6.1.4.1.6486.800.1.3.2.4.2.8)=%8, [ALCATEL-IND1-CHASSIS-MIB.chassisTrapsStr=1.3.6.1.4.1.6486.800.1.3.2.4.1.0.1]
Warning Alcatel: generic trap notifying something changed in the chassis whatever its a failure or not physicalIndex(1.3.6.1.4.1.6486.800.1.3.2.4.2.13)=%1, chassisTrapsObjectType(1.3.6.1.4.1.6486.800.1.3.2.4.2.9)=%2, chassisTrapsObjectNumber(1.3.6.1.4.1.6486.800.1.3.2.4.2.10)=%3, chassisTrapsAlertNumber(1.3.6.1.4.1.6486.800.1.3.2.4.2.11)=%4, chassisTrapsAlertDescr(1.3.6.1.4.1.6486.800.1.3.2.4.2.12)=%5, [ALCATEL-IND1-CHASSIS-MIB.chassisTrapsAlert=1.3.6.1.4.1.6486.800.1.3.2.4.1.0.2]
Warning Alcatel: A status change was detected physicalIndex(1.3.6.1.4.1.6486.800.1.3.2.4.2.13)=%1, chassisTrapsObjectType(1.3.6.1.4.1.6486.800.1.3.2.4.2.9)=%2, chassisTrapsObjectNumber(1.3.6.1.4.1.6486.800.1.3.2.4.2.10)=%3, chasEntPhysOperStatus(1.3.6.1.4.1.6486.800.1.1.1.1.1.1.1.2)=%4, [ALCATEL-IND1-CHASSIS-MIB.chassisTrapsStateChange=1.3.6.1.4.1.6486.800.1.3.2.4.1.0.3]
Error Alcatel: A bindviolation trap occurs whenever a binding rule which has been configured gets violated. gmBindRuleType(1.3.6.1.4.1.6486.800.1.3.2.13.2.1)=%1, gmBindRuleVlanId(1.3.6.1.4.1.6486.800.1.3.2.13.2.2)=%2, gmBindRuleIPAddress(1.3.6.1.4.1.6486.800.1.3.2.13.2.3)=%3, gmBindRuleMacAddress(1.3.6.1.4.1.6486.800.1.3.2.13.2.4)=%4, gmBindRulePortIfIndex(1.3.6.1.4.1.6486.800.1.3.2.13.2.5)=%5, gmBindRuleProtoClass(1.3.6.1.4.1.6486.800.1.3.2.13.2.6)=%6, gmBindRuleEthertype(1.3.6.1.4.1.6486.800.1.3.2.13.2.7)=%7, gmBindRuleDsapSsap(1.3.6.1.4.1.6486.800.1.3.2.13.2.8)=%8, [ALCATEL-IND1-GROUP-MOBILITY-MIB.gmBindRuleViolation=1.3.6.1.4.1.6486.800.1.3.2.13.1.0.1]
Warning Alcatel: Devicelevel rising/falling threshold crossing trap. healthMonRxStatus(1.3.6.1.4.1.6486.800.1.2.1.16.1.1.6.1)=%1, healthMonRxTxStatus(1.3.6.1.4.1.6486.800.1.2.1.16.1.1.6.2)=%2, healthMonMemoryStatus(1.3.6.1.4.1.6486.800.1.2.1.16.1.1.6.3)=%3, healthMonCpuStatus(1.3.6.1.4.1.6486.800.1.2.1.16.1.1.6.4)=%4, healthMonCmmTempStatus(1.3.6.1.4.1.6486.800.1.2.1.16.1.1.6.5)=%5, healthMonCmmCpuTempStatus(1.3.6.1.4.1.6486.800.1.2.1.16.1.1.6.6)=%6, [ALCATEL-IND1-HEALTH-MIB.healthMonDeviceTrap=1.3.6.1.4.1.6486.800.1.3.2.5.0.1]
Warning Alcatel: Modulelevel rising/falling threshold crossing trap. healthModuleSlot(1.3.6.1.4.1.6486.800.1.2.1.16.1.1.2.1.1.1)=%1, healthMonRxStatus(1.3.6.1.4.1.6486.800.1.2.1.16.1.1.6.1)=%2, healthMonRxTxStatus(1.3.6.1.4.1.6486.800.1.2.1.16.1.1.6.2)=%3, healthMonMemoryStatus(1.3.6.1.4.1.6486.800.1.2.1.16.1.1.6.3)=%4, healthMonCpuStatus(1.3.6.1.4.1.6486.800.1.2.1.16.1.1.6.4)=%5, [ALCATEL-IND1-HEALTH-MIB.healthMonModuleTrap=1.3.6.1.4.1.6486.800.1.3.2.5.0.2]
Warning Alcatel: Portlevel rising/falling threshold crossing trap. healthPortSlot(1.3.6.1.4.1.6486.800.1.2.1.16.1.1.3.1.1.1)=%1, healthPortIF(1.3.6.1.4.1.6486.800.1.2.1.16.1.1.3.1.1.2)=%2, healthMonRxStatus(1.3.6.1.4.1.6486.800.1.2.1.16.1.1.6.1)=%3, healthMonRxTxStatus(1.3.6.1.4.1.6486.800.1.2.1.16.1.1.6.2)=%4, [ALCATEL-IND1-HEALTH-MIB.healthMonPortTrap=1.3.6.1.4.1.6486.800.1.3.2.5.0.3]
Error Alcatel: A GMAP update conflict. aipGMAPLastTrapReason(1.3.6.1.4.1.6486.800.1.2.1.9.1.1.1.5)=%1, aipGMAPLastTrapPort(1.3.6.1.4.1.6486.800.1.2.1.9.1.1.1.6)=%2, aipGMAPLastTrapMac(1.3.6.1.4.1.6486.800.1.2.1.9.1.1.1.7)=%3, aipGMAPLastTrapProtocol(1.3.6.1.4.1.6486.800.1.2.1.9.1.1.1.8)=%4, aipGMAPLastTrapVlan(1.3.6.1.4.1.6486.800.1.2.1.9.1.1.1.9)=%5, [ALCATEL-IND1-INTERSWITCH-PROTOCOL-MIB.aipGMAPConflictTrap=1.3.6.1.4.1.6486.800.1.3.2.2.0.1]
Warning Alcatel: An AMAP port status change and reason. aipAMAPLastTrapReason(1.3.6.1.4.1.6486.800.1.2.1.9.1.1.2.4)=%1, aipAMAPLastTrapPort(1.3.6.1.4.1.6486.800.1.2.1.9.1.1.2.5)=%2, [ALCATEL-IND1-INTERSWITCH-PROTOCOL-MIB.aipAMAPStatusTrap=1.3.6.1.4.1.6486.800.1.3.2.1.0.1]
Error Alcatel: The DoS trap indicates that the sending agent has received DoS attack alaDoSType(1.3.6.1.4.1.6486.800.1.2.1.23.1.1.3.1.1.1)=%1, alaDoSDetected(1.3.6.1.4.1.6486.800.1.2.1.23.1.1.3.1.1.2)=%2, [ALCATEL-IND1-IP-MIB.alaDoSTrap=1.3.6.1.4.1.6486.800.1.2.1.23.1.1.5.1]
Security Alcatel: Learned Port Security Violation Trap. lpsTrapSwitchName(1.3.6.1.4.1.6486.800.1.3.2.9.0.2.2.1)=%1, lpsTrapSwitchIpAddr(1.3.6.1.4.1.6486.800.1.3.2.9.0.2.2.2)=%2, lpsTrapSwitchSlice(1.3.6.1.4.1.6486.800.1.3.2.9.0.2.2.3)=%3, lpsTrapSwitchPort(1.3.6.1.4.1.6486.800.1.3.2.9.0.2.2.4)=%4, lpsTrapViolatingMac(1.3.6.1.4.1.6486.800.1.3.2.9.0.2.2.5)=%5, lpsTrapViolationType(1.3.6.1.4.1.6486.800.1.3.2.9.0.2.2.6)=%6, systemServicesDate(1.3.6.1.4.1.6486.800.1.1.1.2.1.1.5.1)=%7, systemServicesTime(1.3.6.1.4.1.6486.800.1.1.1.2.1.1.5.2)=%8, [ALCATEL-IND1-LPS-MIB.lpsViolationTrap=1.3.6.1.4.1.6486.800.1.3.2.9.0.2.1.0.1]
Error Alcatel: Trap Status of Layer 2 pesudoCAM on this Coronado. slPCAMSlotNumber(1.3.6.1.4.1.6486.800.1.2.1.8.1.1.3.1)=%1, slPCAMSliceNumber(1.3.6.1.4.1.6486.800.1.2.1.8.1.1.3.2)=%2, slPCAMStatus(1.3.6.1.4.1.6486.800.1.2.1.8.1.1.3.3)=%3, [ALCATEL-IND1-MAC-ADDRESS-MIB.slPCAMStatusTrap=1.3.6.1.4.1.6486.800.1.3.2.9.0.1]
Error Alcatel: A MAC range overlap was found in the backplane eeprom physicalIndex(1.3.6.1.4.1.6486.800.1.3.2.4.2.13)=%1, chasTrapMacRangeIndex(1.3.6.1.4.1.6486.800.1.3.2.4.2.14)=%2, [ALCATEL-IND1-MAC-SERVER-MIB.chassisTrapsMacOverlap=1.3.6.1.4.1.6486.800.1.1.1.1.3.2.1]
Warning Alcatel: The policyEventNotification allows the switch to notify an NMS when significant events happen. The NMS can then investigate and perform appropriate control functions. Other tables allow the NMS app to zone in on the problem as part of a proactive monitoring system by the NMS application. policyTrapEventDetailString(1.3.6.1.4.1.6486.800.1.3.2.3.2.1)=%1, policyTrapEventCode(1.3.6.1.4.1.6486.800.1.3.2.3.2.2)=%2, [ALCATEL-IND1-POLICY-MIB.policyEventNotification=1.3.6.1.4.1.6486.800.1.3.2.3.1.0.1]
Error Alcatel: When the Ethernet code drops the link because of excessive errors, a Trap is sent. esmPortSlot(1.3.6.1.4.1.6486.800.1.2.1.5.1.1.2.1.1.1)=%1, esmPortIF(1.3.6.1.4.1.6486.800.1.2.1.5.1.1.2.1.1.2)=%2, esmDrvTrapDrops(1.3.6.1.4.1.6486.800.1.2.1.5.1.1.1.1)=%3, ifInErrors(***Error: Could not get OID)=%4, [ALCATEL-IND1-PORT-MIB.esmDrvTrapDropsLink=1.3.6.1.4.1.6486.800.1.3.2.6.0.1]
Error Alcatel: The Mirroring Configuration failed on NI. This trap is sent when any NI fails to configure mirroring. Due to this error, port mirroring session will be terminated. mirmonPrimarySlot(1.3.6.1.4.1.6486.800.1.2.1.19.1.1.3.1)=%1, mirmonPrimaryPort(1.3.6.1.4.1.6486.800.1.2.1.19.1.1.3.2)=%2, mirroringSlot(1.3.6.1.4.1.6486.800.1.2.1.19.1.1.3.3)=%3, mirroringPort(1.3.6.1.4.1.6486.800.1.2.1.19.1.1.3.4)=%4, mirMonErrorNi(1.3.6.1.4.1.6486.800.1.2.1.19.1.1.3.7)=%5, mirMonError(1.3.6.1.4.1.6486.800.1.2.1.19.1.1.3.6)=%6, [ALCATEL-IND1-PORT-MIRRORING-MONITORING-MIB.mirrorConfigError=1.3.6.1.4.1.6486.800.1.3.2.8.0.1]
Warning Alcatel: The Mirroring Configuration is deleted due to the swapping of different NI board type. Port Mirroring session which was active on a slot,cannot continue with the insertion of different NI type in the same slot. mirmonPrimarySlot(1.3.6.1.4.1.6486.800.1.2.1.19.1.1.3.1)=%1, mirmonPrimaryPort(1.3.6.1.4.1.6486.800.1.2.1.19.1.1.3.2)=%2, mirroringSlot(1.3.6.1.4.1.6486.800.1.2.1.19.1.1.3.3)=%3, mirroringPort(1.3.6.1.4.1.6486.800.1.2.1.19.1.1.3.4)=%4, mirMonErrorNi(1.3.6.1.4.1.6486.800.1.2.1.19.1.1.3.7)=%5, [ALCATEL-IND1-PORT-MIRRORING-MONITORING-MIB.mirrorUnlikeNi=1.3.6.1.4.1.6486.800.1.3.2.8.0.3]
Security Alcatel: Authentication Failure Trap is sent each time a user authentication is refused. sessionAccessType(1.3.6.1.4.1.6486.800.1.2.1.7.1.1.1.2.1.2)=%1, sessionUserName(1.3.6.1.4.1.6486.800.1.2.1.7.1.1.1.2.1.4)=%2, sessionUserIpAddress(1.3.6.1.4.1.6486.800.1.2.1.7.1.1.1.2.1.8)=%3, sessionAuthFailure(1.3.6.1.4.1.6486.800.1.3.2.11.2.1)=%4, [ALCATEL-IND1-SESSION-MGR-MIB.sessionAuthenticationTrap=1.3.6.1.4.1.6486.800.1.3.2.11.1.0.1]
Error Alcatel: Two or more slots claim to be the same number. alaStackMgrSlotNINumber(1.3.6.1.4.1.6486.800.1.2.1.24.1.1.1.1.1)=%1, [ALCATEL-IND1-STACK-MANAGER-MIB.alaStackMgrDuplicateSlotTrap=1.3.6.1.4.1.6486.800.1.2.1.24.1.4.0.1]
Error Alcatel: Indicates whether the stack is in loop or not. In case of no loop, alaStackMgrSlotNINumber and alaStackMgrTrapLinkNumber indicate where the Stack is broken alaStackMgrStackStatus(1.3.6.1.4.1.6486.800.1.2.1.24.1.1.3)=%1, alaStackMgrSlotNINumber(1.3.6.1.4.1.6486.800.1.2.1.24.1.1.1.1.1)=%2, alaStackMgrTrapLinkNumber(1.3.6.1.4.1.6486.800.1.2.1.24.1.3.1)=%3, [ALCATEL-IND1-STACK-MANAGER-MIB.alaStackMgrNeighborChangeTrap=1.3.6.1.4.1.6486.800.1.2.1.24.1.4.0.2]
Warning Alcatel: Role Change Trap. Indicates that a new primary or secondary is elected. alaStackMgrPrimary(1.3.6.1.4.1.6486.800.1.2.1.24.1.3.2)=%1, alaStackMgrSecondary(1.3.6.1.4.1.6486.800.1.2.1.24.1.3.3)=%2, [ALCATEL-IND1-STACK-MANAGER-MIB.alaStackMgrRoleChangeTrap=1.3.6.1.4.1.6486.800.1.2.1.24.1.4.0.3]
Error Alcatel: The absorption Trap is sent when a trap has been absorbed at least once. trapAbsorStamp(1.3.6.1.4.1.6486.800.1.2.1.2.1.1.3.1)=%1, trapAbsorTrapId(1.3.6.1.4.1.6486.800.1.2.1.2.1.1.3.2)=%2, trapAbsorCounter(1.3.6.1.4.1.6486.800.1.2.1.2.1.1.3.3)=%3, trapAbsorTime(1.3.6.1.4.1.6486.800.1.2.1.2.1.1.3.4)=%4, [ALCATEL-IND1-TRAP-MGR-MIB.trapAbsorptionTrap=1.3.6.1.4.1.6486.800.1.3.2.12.0.1]
Warning Alcatel: An AMAP port status change and reason. amapLastTrapReason(1.3.6.1.4.1.800.3.1.2.1.8.4)=%1, amapLastTrapPort(1.3.6.1.4.1.800.3.1.2.1.8.5)=%2, [ALCATEL-AMAP-MIB.amapStatusTrap=1.3.6.1.4.1.800.3.1.2.1.8.0.1]
Error Alcatel: An instance of the alarm indicated by alarmActiveModelPointer has been raised against the entity indicated by alarmActiveResourceId. alarmActiveModelPointer(1.3.6.1.4.1.6486.800.1.2.1.26.2.1.2.2.1.13)=%1, alarmActiveResourceId(1.3.6.1.4.1.6486.800.1.2.1.26.2.1.2.2.1.10)=%2, [ALARM-MIB.alarmActiveState=1.3.6.1.4.1.6486.800.1.2.1.26.2.0.2]
Information Alcatel: An instance of the alarm indicated by alarmActiveModelPointer has been cleared against the entity indicated by alarmACtiveResourceId. alarmActiveModelPointer(1.3.6.1.4.1.6486.800.1.2.1.26.2.1.2.2.1.13)=%1, alarmActiveResourceId(1.3.6.1.4.1.6486.800.1.2.1.26.2.1.2.2.1.10)=%2, [ALARM-MIB.alarmClearState=1.3.6.1.4.1.6486.800.1.2.1.26.2.0.3]
Error Alcatel: The BGP Established event is generated when the BGP FSM enters the ESTABLISHED state. bgpPeerLastError(1.3.6.1.2.1.15.3.1.14)=%1, bgpPeerState(1.3.6.1.2.1.15.3.1.2)=%2, [BGP4-MIB.bgpEstablished=1.3.6.1.2.1.15.7.1]
Warning Alcatel: The BGPBackwardTransition Event is generated when the BGP FSM moves from a higher numbered state to a lower numbered state. bgpPeerLastError(1.3.6.1.2.1.15.3.1.14)=%1, bgpPeerState(1.3.6.1.2.1.15.3.1.2)=%2, [BGP4-MIB.bgpBackwardTransition=1.3.6.1.2.1.15.7.2]
Warning Alcatel: A dvmrpNeighborLoss trap signifies the loss of a 2way adjacency with a neighbor. This trap should be generated when the neighbor state changes from active to oneway, ignoring, or down. The trap should be generated only if the router has no other neighbors on the same interface with a lower IP address than itself. dvmrpInterfaceLocalAddress(1.3.6.1.4.1.6486.800.1.2.1.10.7.999.1.1.2.1.2)=%1, dvmrpNeighborState(1.3.6.1.4.1.6486.800.1.2.1.10.7.999.1.1.3.1.12)=%2, [DVMRP-STD-MIB.dvmrpNeighborLoss=1.3.6.1.4.1.6486.800.1.2.1.10.7.999.1.1.7.0.1]
Error Alcatel: A dvmrpNeighborNotPruning trap signifies that a nonpruning neighbor has been detected (in an implementationdependent manner). This trap should be generated at most once per generation ID of the neighbor. For example, it should be generated at the time a neighbor is first heard from if the prune bit is not set in its capabilities. It should also be generated if the local system has the ability to tell that a neighbor which sets the the prune bit in its capabilities is not pruning any branches over an extended period of time. The trap should be generated only if the router has no other neighbors on the same interface with a lower IP address than itself. dvmrpInterfaceLocalAddress(1.3.6.1.4.1.6486.800.1.2.1.10.7.999.1.1.2.1.2)=%1, dvmrpNeighborCapabilities(1.3.6.1.4.1.6486.800.1.2.1.10.7.999.1.1.3.1.8)=%2, [DVMRP-STD-MIB.dvmrpNeighborNotPruning=1.3.6.1.4.1.6486.800.1.2.1.10.7.999.1.1.7.0.2]
Warning Alcatel: This notification is generated when the system enters or leaves the Overload state. The number of times this has be generated and cleared is kept track of by isisSysStatLSPDbaseOloads. isisSystemInstance(1.3.6.1.3.37.1.10.1.1.1)=%1, isisSystemLevel(1.3.6.1.3.37.1.10.1.1.2)=%2, isisSysLevelOverloadState(1.3.6.1.3.37.1.2.1.1.4)=%3, [ISIS-MIB.isisDatabaseOverload=1.3.6.1.3.37.2.0.1]
Warning Alcatel: This notification is generated when one of the manual areaAddresses assigned to this system is ignored when computing routes. The object isisManAreaAddrExistState describes the area that has been dropped. The number of times this event has been generated is counted by isisSysManAddrDropFromAreas. This notification is edge triggered, and should not be regenerated until an address that was used in the previous computation has been dropped. isisSystemInstance(1.3.6.1.3.37.1.10.1.1.1)=%1, isisManAreaAddrExistState(1.3.6.1.3.37.1.1.2.1.2)=%2, [ISIS-MIB.isisManualAddressDrops=1.3.6.1.3.37.2.0.2]
Warning Alcatel: This notification is generated when we find that an LSP that was stored in memory has become corrupted. The number of times this has been generated is counted by isisSysCorrLSPs. We forward an LSP ID. We may have independent knowledge of the ID, but in some implementations there is a chance that the ID itself will be corrupted. isisSystemInstance(1.3.6.1.3.37.1.10.1.1.1)=%1, isisSystemLevel(1.3.6.1.3.37.1.10.1.1.2)=%2, isisTrapLSPID(1.3.6.1.3.37.1.10.1.1.3)=%3, [ISIS-MIB.isisCorruptedLSPDetected=1.3.6.1.3.37.2.0.3]
Warning Alcatel: When the sequence number on an LSP we generate wraps the 32 bit sequence counter, we purge and wait to reannounce this information. This notification describes that event. Since these should not be generated rapidly, we generate an event each time this happens. While the first 6 bytes of the LSPID are ours, the other two contain useful information. isisSystemInstance(1.3.6.1.3.37.1.10.1.1.1)=%1, isisSystemLevel(1.3.6.1.3.37.1.10.1.1.2)=%2, isisTrapLSPID(1.3.6.1.3.37.1.10.1.1.3)=%3, [ISIS-MIB.isisAttemptToExceedMaxSequence=1.3.6.1.3.37.2.0.4]
Warning Alcatel: A notification sent when we receive a PDU with a different value of the System ID Length. This notification includes the an index to identify the circuit where we saw the PDU and the header of the PDU which may help a network manager identify the source of the confusion. This should be an edgetriggered notification. We should not send a second notification about PDUs received from what seem to be the same source. This decision is up to the agent to make, and may be based on the circuit or on some MAC level information. isisSystemInstance(1.3.6.1.3.37.1.10.1.1.1)=%1, isisFieldLen(1.3.6.1.3.37.1.10.1.1.5)=%2, isisCircIfIndex(1.3.6.1.3.37.1.3.1.1.2)=%3, isisPDUFragment(1.3.6.1.3.37.1.10.1.1.4)=%4, [ISIS-MIB.isisIDLenMismatch=1.3.6.1.3.37.2.0.5]
Warning Alcatel: A notification sent when we receive a PDU with a different value of the Maximum Area Addresses. This notification includes the header of the packet, which may help a network manager identify the source of the confusion. This should be an edgetriggered notification. We should not send a second notification about PDUs received from what seem to be the same source. isisSystemInstance(1.3.6.1.3.37.1.10.1.1.1)=%1, isisMaxAreaAddress(1.3.6.1.3.37.1.10.1.1.6)=%2, isisCircIfIndex(1.3.6.1.3.37.1.3.1.1.2)=%3, isisPDUFragment(1.3.6.1.3.37.1.10.1.1.4)=%4, [ISIS-MIB.isisMaxAreaAddressesMismatch=1.3.6.1.3.37.2.0.6]
Warning Alcatel: A notification sent when we receive a PDU with our systemID and zero age. This notification includes the circuit Index if available, which may help a network manager identify the source of the confusion. isisSystemInstance(1.3.6.1.3.37.1.10.1.1.1)=%1, isisSystemLevel(1.3.6.1.3.37.1.10.1.1.2)=%2, isisCircIfIndex(1.3.6.1.3.37.1.3.1.1.2)=%3, isisTrapLSPID(1.3.6.1.3.37.1.10.1.1.3)=%4, [ISIS-MIB.isisOwnLSPPurge=1.3.6.1.3.37.2.0.7]
Warning Alcatel: When we receive an LSP with out System ID and different contents, we may need to reissue the LSP with a higher sequence number. We send this notification if we need to increase the sequence number by more than one. If two Intermediate Systems are configured with the same System ID, this notification will fire. isisSystemInstance(1.3.6.1.3.37.1.10.1.1.1)=%1, isisSystemLevel(1.3.6.1.3.37.1.10.1.1.2)=%2, isisCircIfIndex(1.3.6.1.3.37.1.3.1.1.2)=%3, isisTrapLSPID(1.3.6.1.3.37.1.10.1.1.3)=%4, [ISIS-MIB.isisSequenceNumberSkip=1.3.6.1.3.37.2.0.8]
Warning Alcatel: A notification sent when we receive a PDU with the wrong authentication type field. This notification includes the header of the packet, which may help a network manager identify the source of the confusion. This should be an edgetriggered notification. We should not send a second notification about PDUs received from what seem to be the same source. isisSystemInstance(1.3.6.1.3.37.1.10.1.1.1)=%1, isisSystemLevel(1.3.6.1.3.37.1.10.1.1.2)=%2, isisCircIfIndex(1.3.6.1.3.37.1.3.1.1.2)=%3, isisPDUFragment(1.3.6.1.3.37.1.10.1.1.4)=%4, [ISIS-MIB.isisAuthenticationTypeFailure=1.3.6.1.3.37.2.0.9]
Security Alcatel: A notification sent when we receive a PDU with incorrect authentication information field. This notification includes the header of the packet, which may help a network manager identify the source of the confusion. This should be an edgetriggered notification. We should not send a second notification about PDUs received from what seem to be the same source. isisSystemInstance(1.3.6.1.3.37.1.10.1.1.1)=%1, isisSystemLevel(1.3.6.1.3.37.1.10.1.1.2)=%2, isisCircIfIndex(1.3.6.1.3.37.1.3.1.1.2)=%3, isisPDUFragment(1.3.6.1.3.37.1.10.1.1.4)=%4, [ISIS-MIB.isisAuthenticationFailure=1.3.6.1.3.37.2.0.10]
Warning Alcatel: A notification sent when we receive a Hello PDU from an IS running a different version of the protocol. This notification includes the header of the packet, which may help a network manager identify the source of the confusion. This should be an edgetriggered notification. We should not send a second notification about PDUs received from what seem to be the same source. This decision is up to the agent to make, and may be based on the circuit or on some MAC level information. isisSystemInstance(1.3.6.1.3.37.1.10.1.1.1)=%1, isisSystemLevel(1.3.6.1.3.37.1.10.1.1.2)=%2, isisCircIfIndex(1.3.6.1.3.37.1.3.1.1.2)=%3, isisProtocolVersion(1.3.6.1.3.37.1.10.1.1.7)=%4, isisPDUFragment(1.3.6.1.3.37.1.10.1.1.4)=%5, [ISIS-MIB.isisVersionSkew=1.3.6.1.3.37.2.0.11]
Warning Alcatel: A notification sent when we receive a Hello PDU from an IS which does not share any area address. This notification includes the header of the packet, which may help a network manager identify the source of the confusion. This should be an edgetriggered notification. We should not send a second notification about PDUs received from what seem to be the same source. This decision is up to the agent to make, and may be based on the circuit or on some MAC level information. isisSystemInstance(1.3.6.1.3.37.1.10.1.1.1)=%1, isisSystemLevel(1.3.6.1.3.37.1.10.1.1.2)=%2, isisCircIfIndex(1.3.6.1.3.37.1.3.1.1.2)=%3, isisPDUFragment(1.3.6.1.3.37.1.10.1.1.4)=%4, [ISIS-MIB.isisAreaMismatch=1.3.6.1.3.37.2.0.12]
Warning Alcatel: A notification sent when we receive a Hello PDU from an IS, but do not establish an adjacency for some reason. This should be an edgetriggered notification. We should not send a second notification about PDUs received from the same source. isisSystemInstance(1.3.6.1.3.37.1.10.1.1.1)=%1, isisSystemLevel(1.3.6.1.3.37.1.10.1.1.2)=%2, isisCircIfIndex(1.3.6.1.3.37.1.3.1.1.2)=%3, isisPDUFragment(1.3.6.1.3.37.1.10.1.1.4)=%4, [ISIS-MIB.isisRejectedAdjacency=1.3.6.1.3.37.2.0.13]
Warning Alcatel: A notification sent when we attempt to propagate an LSP which is larger than the dataLinkBlockSize for a circuit. This should be an edgetriggered notification. We should not send a second notification about PDUs received from the same source. isisSystemLevel(1.3.6.1.3.37.1.10.1.1.2)=%1, isisCircIfIndex(1.3.6.1.3.37.1.3.1.1.2)=%2, isisLSPSize(1.3.6.1.3.37.1.10.1.1.8)=%3, isisTrapLSPID(1.3.6.1.3.37.1.10.1.1.3)=%4, [ISIS-MIB.isisLSPTooLargeToPropagate=1.3.6.1.3.37.2.0.14]
Warning Alcatel: A notification sent when a Level 1 LSP or Level 2 LSP is received which is larger than the local value for isisOriginatingBufferSize, or when an LSP is received containing the isisOriginatingBufferSize option and the value in the PDU option field does not match the local value for isisOriginatingBufferSize. We pass up the size from the option field or the size of the LSP that exceeds our configuration. This should be an edgetriggered notification. We should not send a second notification about PDUs received from the same source. isisSystemLevel(1.3.6.1.3.37.1.10.1.1.2)=%1, isisCircIfIndex(1.3.6.1.3.37.1.3.1.1.2)=%2, isisTrapLSPID(1.3.6.1.3.37.1.10.1.1.3)=%3, isisOriginatingBufferSize(1.3.6.1.3.37.1.10.1.1.9)=%4, [ISIS-MIB.isisOriginatingLSPBufferSizeMismatch=1.3.6.1.3.37.2.0.15]
Warning Alcatel: A notification sent when a nonpseudonode segment 0 LSP is received that has no matching protocols supported. This may be because the system does not generate the field, or because there are no common elements. The list of protocols supported should be included in the notification: it may be empty if the TLV is not supported, or if the TLV is empty. This should be an edgetriggered notification. We should not send a second notification about PDUs received from the same source. isisSystemLevel(1.3.6.1.3.37.1.10.1.1.2)=%1, isisCircIfIndex(1.3.6.1.3.37.1.3.1.1.2)=%2, isisProtocolsSupported(1.3.6.1.3.37.1.10.1.1.10)=%3, isisTrapLSPID(1.3.6.1.3.37.1.10.1.1.3)=%4, isisPDUFragment(1.3.6.1.3.37.1.10.1.1.4)=%5, [ISIS-MIB.isisProtocolsSupportedMismatch=1.3.6.1.3.37.2.0.16]
Warning Alcatel: A notification sent when an adjacency changes state, entering or leaving state up. isisSystemLevel(1.3.6.1.3.37.1.10.1.1.2)=%1, isisCircIfIndex(1.3.6.1.3.37.1.3.1.1.2)=%2, isisTrapLSPID(1.3.6.1.3.37.1.10.1.1.3)=%3, isisAdjState(1.3.6.1.3.37.1.10.1.1.11)=%4, [ISIS-MIB.isisAdjacencyChange=1.3.6.1.3.37.2.0.17]
Error Alcatel: This trap is sent whenever a managed repeater MAU enters the jabber state. The agent MUST throttle the generation of consecutive rpMauJabberTraps so that there is at least a fivesecond gap between them. rpMauJabberState(1.3.6.1.2.1.26.1.1.1.8)=%1, [MAU-MIB.rpMauJabberTrap=1.3.6.1.2.1.26.0.1]
Error Alcatel: This trap is sent whenever a managed interface MAU enters the jabber state. The agent MUST throttle the generation of consecutive ifMauJabberTraps so that there is at least a fivesecond gap between them. ifMauJabberState(1.3.6.1.2.1.26.2.1.1.7)=%1, [MAU-MIB.ifMauJabberTrap=1.3.6.1.2.1.26.0.2]
Error Alcatel: A pimNeighborLoss trap signifies the loss of an adjacency with a neighbor. This trap should be generated when the neighbor timer expires, and the router has no other neighbors on the same interface with a lower IP address than itself. pimNeighborIfIndex(1.3.6.1.3.61.1.1.3.1.2)=%1, [PIM-MIB.pimNeighborLoss=1.3.6.1.3.61.1.0.1]
Warning Alcatel: The SNMP trap that is generated when an alarm entry crosses its rising threshold and generates an event that is configured for sending SNMP traps. alarmIndex(1.3.6.1.2.1.16.3.1.1.1)=%1, alarmVariable(1.3.6.1.2.1.16.3.1.1.3)=%2, alarmSampleType(1.3.6.1.2.1.16.3.1.1.4)=%3, alarmValue(1.3.6.1.2.1.16.3.1.1.5)=%4, alarmRisingThreshold(1.3.6.1.2.1.16.3.1.1.7)=%5, [RMON-MIB.risingAlarm=1.3.6.1.2.1.16.0.1]
Warning Alcatel: The SNMP trap that is generated when an alarm entry crosses its falling threshold and generates an event that is configured for sending SNMP traps. alarmIndex(1.3.6.1.2.1.16.3.1.1.1)=%1, alarmVariable(1.3.6.1.2.1.16.3.1.1.3)=%2, alarmSampleType(1.3.6.1.2.1.16.3.1.1.4)=%3, alarmValue(1.3.6.1.2.1.16.3.1.1.5)=%4, alarmFallingThreshold(1.3.6.1.2.1.16.3.1.1.8)=%5, [RMON-MIB.fallingAlarm=1.3.6.1.2.1.16.0.2]
Warning Alcatel: The newMaster trap indicates that the sending agent has transitioned to Master state. vrrpOperMasterIpAddr(1.3.6.1.2.1.68.1.3.1.7)=%1, [VRRP-MIB.vrrpTrapNewMaster=1.3.6.1.2.1.68.0.1]
Security Alcatel: A vrrpAuthFailure trap signifies that a packet has been received from a router whose authentication key or authentication type conflicts with this routers authentication key or authentication type. Implementation of this trap is optional. vrrpTrapPacketSrc(1.3.6.1.2.1.68.1.5)=%1, vrrpTrapAuthErrorType(1.3.6.1.2.1.68.1.6)=%2, [VRRP-MIB.vrrpTrapAuthFailure=1.3.6.1.2.1.68.0.2]
Error Alcatel: This trap signifies that the specified circuit has gone down. ipxCircSysInstance(1.3.6.1.4.1.23.2.5.2.1.1.1)=%1, ipxCircIndex(1.3.6.1.4.1.23.2.5.2.1.1.2)=%2, [IPX.ipxTrapCircuitDown=1.3.6.1.4.1.23.2.5.5.0.1]
Error Alcatel: This trap signifies that the specified circuit has come up. ipxCircSysInstance(1.3.6.1.4.1.23.2.5.2.1.1.1)=%1, ipxCircIndex(1.3.6.1.4.1.23.2.5.2.1.1.2)=%2, [IPX.ipxTrapCircuitUp=1.3.6.1.4.1.23.2.5.5.0.2]
Critical Alcatel: The newRoot trap indicates that the sending agent has become the new root of the Spanning Tree; the trap is sent by a bridge soon after its election as the new root, e.g., upon expiration of the Topology Change Timer immediately subsequent to its election. Implementation of this trap is optional. [BRIDGE-MIB.newRoot=1.3.6.1.2.1.17.0.1]
Warning Alcatel: A topologyChange trap is sent by a bridge when any of its configured ports transitions from the Learning state to the Forwarding state, or from the Forwarding state to the Blocking state. The trap is not sent if a newRoot trap is sent for the same transition. Implementation of this trap is optional. [BRIDGE-MIB.topologyChange=1.3.6.1.2.1.17.0.2]
Warning Alcatel: An entConfigChange notification is generated when the value of entLastChangeTime changes. It can be utilized by an NMS to trigger logical/physical entity table maintenance polls. An agent should not generate more than one entConfigChange notificationevent in a given time interval (five seconds is the suggested default). A notificationevent is the transmission of a single trap or inform PDU to a list of notification destinations. If additional configuration changes occur within the throttling period, then notificationevents for these changes should be suppressed by the agent until the current throttling period expires. At the end of a throttling period, one notificationevent should be generated if any configuration changes occurred since the start of the throttling period. In such a case, another throttling period is started right away. An NMS should periodically check the value of entLastChangeTime to detect any missed entConfigChange notificationevents, e.g., due to throttling or transmission loss. [ENTITY-MIB.entConfigChange=1.3.6.1.2.1.47.2.0.1]
Error Alcatel: A coldStart trap signifies that the SNMPv2 entity, acting in an agent role, is reinitializing itself and that its configuration may have been altered. [SNMPv2-MIB.coldStart=1.3.6.1.6.3.1.1.5.1]
Error Alcatel: A warmStart trap signifies that the SNMPv2 entity, acting in an agent role, is reinitializing itself such that its configuration is unaltered. [SNMPv2-MIB.warmStart=1.3.6.1.6.3.1.1.5.2]
Security Alcatel: An authenticationFailure trap signifies that the SNMPv2 entity, acting in an agent role, has received a protocol message that is not properly authenticated. While all implementations of the SNMPv2 must be capable of generating this trap, the snmpEnableAuthenTraps object indicates whether this trap will be generated. [SNMPv2-MIB.authenticationFailure=1.3.6.1.6.3.1.1.5.5]



For additional information, please contact SystemCenterSales@quest.com
© 2007 Quest Software, Inc. All rights reserved.

Message was edited by: System_Generated

Message was edited by: System_Generated

SNMP traps not generating alerts

$
0
0

We have an EMC NS-20.  When I send test traps to the server that has the EXC software on it, the traps do show up in the log for the node, but no alert is generated in SCOM.

Here is the log entry:

2/18/2009 8:25:36 AM:OAT-NS20:SNMPTrap_UserExit: state=NORMAL returnCode=1
2/18/2009 8:25:36 AM:OAT-NS20: === Found in DB     === START TRAP
2/18/2009 8:25:36 AM:OAT-NS20: __SERVER = <null> of type WMI
2/18/2009 8:25:36 AM:OAT-NS20: __DERIVATION = SnmpExtendedNotification, __ExtrinsicEvent, __Event, __IndicationRelated, __SystemClass of type WMI
2/18/2009 8:25:36 AM:OAT-NS20: __NAMESPACE = <null> of type WMI
2/18/2009 8:25:36 AM:OAT-NS20: __PATH = <null> of type WMI
2/18/2009 8:25:36 AM:OAT-NS20: AgentAddress = 134.139.25.150 of type WMI
2/18/2009 8:25:36 AM:OAT-NS20: __CLASS = SnmpV1ExtendedNotification of type WMI
2/18/2009 8:25:36 AM:OAT-NS20: __GENUS = 2 of type WMI
2/18/2009 8:25:36 AM:OAT-NS20: AgentTransportAddress = 134.139.25.150 of type WMI
2/18/2009 8:25:36 AM:OAT-NS20: AgentTransportProtocol = IP of type WMI
2/18/2009 8:25:36 AM:OAT-NS20: Community = scompublic of type WMI
2/18/2009 8:25:36 AM:OAT-NS20: Identification = 1.3.6.1.4.1.1139.2.0.10 of type WMI
2/18/2009 8:25:36 AM:OAT-NS20: Identification2 = iso.3.6.1.4.1.1139.2.0.10 of type WMI
2/18/2009 8:25:36 AM:OAT-NS20: SECURITY_DESCRIPTOR = <null> of type WMI
2/18/2009 8:25:37 AM:OAT-NS20: TIME_CREATED = 128794479366760504 of type WMI
2/18/2009 8:25:37 AM:OAT-NS20: TimeStamp = 1580363857 of type WMI
2/18/2009 8:25:37 AM:OAT-NS20: __SUPERCLASS = SnmpExtendedNotification of type WMI
2/18/2009 8:25:37 AM:OAT-NS20: __DYNASTY = __SystemClass of type WMI
2/18/2009 8:25:37 AM:OAT-NS20: __RELPATH = <null> of type WMI
2/18/2009 8:25:37 AM:OAT-NS20: __PROPERTY_COUNT = 9 of type WMI
2/18/2009 8:25:37 AM:OAT-NS20:----------------------
2/18/2009 8:25:37 AM:OAT-NS20: 1.3.6.1.4.1.1139.2.1.1.2(iso.3.6.1.4.1.1139.2.1.1.2) = 0 of type INTEGER
2/18/2009 8:25:37 AM:OAT-NS20: 1.3.6.1.4.1.1139.2.1.1.3(iso.3.6.1.4.1.1139.2.1.1.3) = 2 of type INTEGER
2/18/2009 8:25:37 AM:OAT-NS20: 1.3.6.1.4.1.1139.2.1.1.4(iso.3.6.1.4.1.1139.2.1.1.4) = Feb 18 08:17:41 2009 LocalHardwareMonitor:2:0 User Generated Test Message  of type OCTET STRING
2/18/2009 8:25:37 AM:OAT-NS20: 1.3.6.1.3.1057.1(iso.3.6.1.3.1057.1) = 134.139.25.150 of type IpAddress
2/18/2009 8:25:37 AM:OAT-NS20: 1.3.6.1.6.3.1.1.4.3.0(iso.3.6.1.6.3.1.1.4.3.0) = 1.3.6.1.4.1.1139.2 of type OBJECT IDENTIFIER
2/18/2009 8:25:37 AM:OAT-NS20: 1.3.6.1.4.1.1139.2.1.1.1(iso.3.6.1.4.1.1139.2.1.1.1) = -117 of type INTEGER
2/18/2009 8:25:37 AM:OAT-NS20: ===================== END TRAP
2/18/2009 8:25:37 AM:OAT-NS20:

Install everything (SNMP Trap service, WMI SNMP Provider, etc.) on SCOM?


SCCM hierarchy and QMX installation

$
0
0
Hello,

We are using SCCM with a hierarchy based on primary and secondary sites. I was wondering if it is possible to install QMX on a secondary site system server or if it must always be installed on a primary site?

Best regards,

Antoine

MQ extension: inactive channels not detected

$
0
0

Hi,

 

I have defined 5 channels, 3 server channels, 1 sender and 1 receiver channel. 2 server channels are down at the moment, but it's not detect by the extension.

 

When I look at the script, it executes a display chstatus(*) all which only shows the running channel. The inactive channel has been active and was stopped when the MQ extension was running. So I guess it should have save the status somewhere?

 

How can I arrange that the channel that are down are also detected?

 

Thanks,

Dick

Life Line Please, simple connection, big problem.

$
0
0
Here is the deal, help me fix this, I guarantee the purchase of more licenses, seriously.

Justin and I could not figure it out over the last two days, I spent all day today rebuilding the environment thinking I missed something....NOT

Code:
Base Framework:  4.0.0.509
HPUX Ext: v7.0.0.9
Oracle Ext: v7.0.0.11

Point:  it WAS working before the upgrade (now re-install).

The problem, after reinstallation (from the SCOM agent to the BASE Framework and extensions).  After a successful SDK connection test, we try a Oracle DB connection test and can NOT get by the following error:

Connect: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor.

OK, so we go to the db server in question and run these commands.

1. lsnrctl services VendavoDTI    (the Instance/SID)
The command completed Successfully

2. sqlplus tesetuser@VendavoDTI
> Password:  testuser1
> SQL
Connection Good, Credentials Good.

3. SQL > show parameter service_names
service_names                    string                VendavoDTI.dti.com

4. sqlplus testuser/testuser1@VendavoDTI
Successful

5. From the Proxy Server, ping dtidbp20
Successful

The listener.log shows this from my connection attempt

11-NOV-2009 18:31:53 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=VendavoDTI)(CID=(PROGRAM=D:\Program?Files\eXc?Software\WMI?Providers\nonWindows\Virtual?Agent?Library\MOM\Oracle\OracleTestConnection.exe)(HOST=DTIFS02)(USER=sidscp01))) * (ADDRESS=(PROTOCOL=tcp)(HOST=161.16.238.58)(PORT=4583)) * establish * VendavoDTI * 12514
TNS-12514: TNS:listener does not currently know of service requested in connect descriptor

6. tnsping VendavoDTI    (executed on the database server)
OK (60msec)

I attached the tnsnames.ora to this post.

Please....please advise....

Unable to Register ISV Proxy

$
0
0

Hi all,

 

I am standing up a new SCCM site build and I am recieving the following error after running the SCCM connectivity tests

 

Unable to Register ISV Proxy: CSMSManagementPoint::SignHashHexEncode:CryptAcquireCertificatePrivateKey failed with error -2146885621: Cannot find the certificate and pricate key for decryption.

 

The certificate was exported and registered without error. QMX is installed on the same computer as SCCM.  I can see the certificate in the SCCM Console.

We are running SCCM2007 R3 with QMX base framework 4.0.6.67 on Server 2008R2

 

I compared my settings to my old machine and everything looks to be ok.  Any thoughts?

Intergrate SCOM into Foglight

$
0
0

hi

I want to intergrate stats and alerts from SCOM and Grid Control into Foglight is this possible and how do i go about it?

Weblogic configuration

$
0
0

Hello,

 

I have some errors like these :

 

2/07/2013 3:57:55 PM:ncewlint:In file MOM/CommonRoutinesSNMPPerformanceMetrics.js, function ProcessSNMPTable(3), SNMP OID executeQueueRuntimePendingRequestOldestTime does not have a numeric value.The non-numeric value is <Counter64: 1372773474677>

 

When I launch the discovery of the OID on the weblogic servers. Can someone can help with this ?

Error: Partition already exists and still set at Step 3, something is wrong.

$
0
0

Hi, I'm trying to deploy a Mac OS image, but I get the above error message (in the subject). I've attached the debug log, the Hosts, and Deployment files. Please help.


RightFax BrookTrout Channel Monitor

$
0
0
Hi,

Is there a way through SCOM i could collect the below information?
  • Identify potential channel capacity problems before they occur
  • Monitor your RightFax server in real-time
  • Print graphics and collect data for future reference


Thanks,
Y.J.Srinath

Problem with VM disk space alerts

$
0
0
Hi,


I'm getting a lot of " Threshold for Guest Disk usage_critical has been triggered" alerts.
The strange thing is that all my VMs have plenty of free space. Not only can I see that inside the VMs, but RVTools (that queries vCenter) also shows me that all the disks are far away from being full.

The full error is the following:

"Alert description: VMWare3001:  GUEST proxy.domain.local(vm-1056): Threshold for Guest Disk usage_critical has been triggered.  Current value of 95.21 Percent is >  the critical threshold which is set at 95.  VMWare hierarchy parent: Folder Testing(group-v271), Metric details: VMWare Virtual Machine disk usage as a percentage."

Thanks
Message was edited by: rjtd21_828

Message was edited by: rjtd21_828

Not enough storage is available to process this command

$
0
0

Any one ever seen this one ?

 

Not enough storage is available to process this command

 

CScriptManager::CreateProcessForSpecificVirtualAgent could not run Virtual Agent //JOB:LOGS "C:\Program Files\eXc Software\WMI Providers\nonWindows\Virtual Agent Library\MOM\LinuxRedHat\server3_Logs\__VirtualAgentJobs.wsf", reason: Not enough storage is available to process this command.

.

Management pack for SCOM 2007 R2

$
0
0

Can some one please tell me how and where to download the following quest manamnegt packs . I know a  cost is involved but will like a train version first

 

APC - UPS Manangment pack for SCOM 2007 R2

 

MacAfee EPO Managmnet pack for SCOM 2007 R2

 

BES  Blackberry Managment pack for SCOM 2007 R2

 

 

Thnaks

SCCM Ubuntu 10.4

$
0
0

Hi All,

 

I installed QMX, test runs successfully and I can connect to ubuntu using ssh. but when I run the inventory against it runs then it get stuck. see below logs

 

2013/03/27 01:56:38 PM:10.207.1.20:In file CommonRoutines, function SetVariables called with XML file= C:\Program Files (x86)\eXc Software\WMI Providers\nonWindows\Virtual Agent Library\/SMS/_GlobalVariables.xml XSLT file= C:\Program Files (x86)\eXc Software\WMI Providers\nonWindows\Virtual Agent Library\/eXcGUI/GlobalVariables.xslt

2013/03/27 01:56:38 PM:10.207.1.20:In file CommonRoutines, function SetVariables called with XML file= C:\Program Files (x86)\eXc Software\WMI Providers\nonWindows\Virtual Agent Library\/SMS/ConfigMgrGlobalVariables.xml XSLT file= C:\Program Files (x86)\eXc Software\WMI Providers\nonWindows\Virtual Agent Library\/eXcGUI/GlobalVariables.xslt

2013/03/27 01:56:38 PM:10.207.1.20:All.js entered for 10.207.1.20

2013/03/27 01:56:38 PM:10.207.1.20:Running on System Center Configuration Manager version 2012.

2013/03/27 01:56:38 PM:10.207.1.20:Agent = false

2013/03/27 01:56:40 PM:10.207.1.20:SetupVirtualAgent returned 0

2013/03/27 01:56:40 PM:10.207.1.20:In file /SMS/CommonRoutines.js, function SetupSMS, setting up SMS...

2013/03/27 01:56:52 PM:10.207.1.20:SMSCommonRoutines.js.js, ReSubmitting DDR for ResourceID 16777231

2013/03/27 01:56:52 PM:10.207.1.20:File SMS\CommonRoutinesMPAPI.js function SetSMSManagementPointInterface(), informational: eXcSMSManagementPoint instantiated.

2013/03/27 01:56:52 PM:10.207.1.20:File SMS\CommonRoutinesMPAPI.js function SetSMSManagementPointInterface(), strSMSVersion=<SCCM>, strSecurityMode=<Mixed>, MPAPI Host=<http://localhost>, MPAPIPort#=<80>, strCertificateSubjectName=<eXc Software>, strCertificateStore=<MY>

2013/03/27 01:56:52 PM:10.207.1.20:MPAPI_RegisterISVProxyToSCCM: ISV Proxy SMSID=GUID:afd3e936-1567-4357-8971-623d3d1c3e6c

2013/03/27 01:56:52 PM:10.207.1.20:MPAPI_AddDDRToSMSViaManagementPoint: Host 10.207.1.20, SMSResourceGUID=GUID:5B40E66F-8256-4978-A7EA-21BA5E270CE2

2013/03/27 01:56:52 PM:10.207.1.20:SMSCommonRoutines.js.js, VirtualAgent for ResourceID 16777231 is UbuntuLinuxVirtualAgent expected UbuntuLinuxVirtualAgent

2013/03/27 01:56:52 PM:10.207.1.20:SMSCommonRoutines.js, QMX_Directory for ResourceID 16777231 is C:\Program Files (x86)\eXc Software\WMI Providers\nonWindows\Virtual Agent Library\SMS\LinuxUbuntu

2013/03/27 01:56:52 PM:10.207.1.20:Got 10.207.1.20 from ConfigMgr, existing SMS Resource ID=16777231

2013/03/27 01:56:52 PM:10.207.1.20:In file /SMS/CommonRoutines.js, function SetupSMS, setup complete.

2013/03/27 01:56:52 PM:10.207.1.20:HardwareInventory.js entered.

2013/03/27 02:02:30 PM:10.207.1.20:In file CommonRoutines, function SetVariables called with XML file= C:\Program Files (x86)\eXc Software\WMI Providers\nonWindows\Virtual Agent Library\/SMS/_GlobalVariables.xml XSLT file= C:\Program Files (x86)\eXc Software\WMI Providers\nonWindows\Virtual Agent Library\/eXcGUI/GlobalVariables.xslt

2013/03/27 02:02:30 PM:10.207.1.20:In file CommonRoutines, function SetVariables called with XML file= C:\Program Files (x86)\eXc Software\WMI Providers\nonWindows\Virtual Agent Library\/SMS/ConfigMgrGlobalVariables.xml XSLT file= C:\Program Files (x86)\eXc Software\WMI Providers\nonWindows\Virtual Agent Library\/eXcGUI/GlobalVariables.xslt

2013/03/27 02:02:30 PM:10.207.1.20:All.js entered for 10.207.1.20

2013/03/27 02:02:30 PM:10.207.1.20:Running on System Center Configuration Manager version 2012.

2013/03/27 02:02:30 PM:10.207.1.20:Agent = false

2013/03/27 02:02:34 PM:10.207.1.20:SetupVirtualAgent returned 0

2013/03/27 02:02:34 PM:10.207.1.20:In file /SMS/CommonRoutines.js, function SetupSMS, setting up SMS...

2013/03/27 02:02:46 PM:10.207.1.20:SMSCommonRoutines.js.js, ReSubmitting DDR for ResourceID 16777231

2013/03/27 02:02:46 PM:10.207.1.20:File SMS\CommonRoutinesMPAPI.js function SetSMSManagementPointInterface(), informational: eXcSMSManagementPoint instantiated.

2013/03/27 02:02:46 PM:10.207.1.20:File SMS\CommonRoutinesMPAPI.js function SetSMSManagementPointInterface(), strSMSVersion=<SCCM>, strSecurityMode=<Mixed>, MPAPI Host=<http://localhost>, MPAPIPort#=<80>, strCertificateSubjectName=<eXc Software>, strCertificateStore=<MY>

2013/03/27 02:02:46 PM:10.207.1.20:MPAPI_RegisterISVProxyToSCCM: ISV Proxy SMSID=GUID:afd3e936-1567-4357-8971-623d3d1c3e6c

2013/03/27 02:02:46 PM:10.207.1.20:MPAPI_AddDDRToSMSViaManagementPoint: Host 10.207.1.20, SMSResourceGUID=GUID:5B40E66F-8256-4978-A7EA-21BA5E270CE2

2013/03/27 02:02:46 PM:10.207.1.20:SMSCommonRoutines.js.js, VirtualAgent for ResourceID 16777231 is UbuntuLinuxVirtualAgent expected UbuntuLinuxVirtualAgent

2013/03/27 02:02:46 PM:10.207.1.20:SMSCommonRoutines.js, QMX_Directory for ResourceID 16777231 is C:\Program Files (x86)\eXc Software\WMI Providers\nonWindows\Virtual Agent Library\SMS\LinuxUbuntu

2013/03/27 02:02:46 PM:10.207.1.20:Got 10.207.1.20 from ConfigMgr, existing SMS Resource ID=16777231

2013/03/27 02:02:46 PM:10.207.1.20:In file /SMS/CommonRoutines.js, function SetupSMS, setup complete.

2013/03/27 02:02:47 PM:10.207.1.20:HardwareInventory.js entered.

Viewing all 1925 articles
Browse latest View live