DHCP Requests Starts Failing

I have a school with 550 iPads. We are using two 5508 WLCs sharing the number of APs. The DHCP server and the default gateway for the network are on the firewall. The clients are able to get a DCHP. After some time, maybe about longer than a month, the clients are no longer able to get DCHP addresses. A reboot of both controllers takes care of this. Presently we are runing 7.2.110 OS. I am going to upgrade to the latest 7.4.100, and reload tonight.
Any insight you could give me for this effort, would be great.

Thanks. I am gettings these arp errors
*DHCP Proxy DTL Recv Task: Sep 19 17:44:24.507: %DTL-3-ARP_CLIENT_IP_DUPLICATED: dtl_arp.c:1806 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID ac:3c:0b:07:15:d1 and IP Address 172.18.1.156, Old client MAC-ID was 84:29:99:
*DHCP Proxy DTL Recv Task: Sep 19 17:44:23.998: %DTL-3-ARP_CLIENT_IP_DUPLICATED: dtl_arp.c:1806 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 8c:70:5a:74:86:cc and IP Address 172.18.5.76, Old client MAC-ID was 00:23:14:7
*apfReceiveTask: Sep 19 17:44:22.794: %RRM-3-RRM_LOGMSG: rrmChanUtils.c:290 RRM LOG: Airewave Director: Could not find valid channel lists for 802.11bg
*DHCP Proxy DTL Recv Task: Sep 19 17:44:22.540: %DTL-3-ARP_CLIENT_IP_DUPLICATED: dtl_arp.c:1806 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID ac:3c:0b:09:b6:b8 and IP Address 172.18.1.31, Old client MAC-ID was 84:29:99:1
*DHCP Proxy DTL Recv Task: Sep 19 17:44:22.534: %DTL-3-ARP_CLIENT_IP_DUPLICATED: dtl_arp.c:1806 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID 3c:e0:72:cd:19:a0 and IP Address 172.18.0.135, Old client MAC-ID was 84:29:99:
Any idea how to clear them.I have restarted Windows DHCP server

Similar Messages

Java 7 Web start fails to download Java 1.6 version

Sorry for the almost exact duplication of a previous thread, but that was closed (Java 7 Web start fails to download Java 1.6 version
When launching an application requiring Java 1.6 with a Java 1.7 web start it fails when it tries to download 1.6 with the following message:
"Unable to download http://javadl-esd.sun.com/update/1.6.0/1.6.0_29-b11.xml for installation"
Problem only seems to occur on Windows 7 (64 bit), seems fine on Windows XP.
Bug has been raised with Oracle by poster Matt Taylor - http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7168311
Does anybody have any ideas?
Thanks,
Lee.

igor wrote:
Could you please collect and provide more info.
In particular:
0) Explain how exactly you launch JNLP when it does not work.We have a website with a link to a jnlp file. User clicks on the link the jnlp file downloads and installs.
"install the jnlp from the dos window" - do you mean run "javaws applicationURL"?Yes. But actually that only worked because we had already installed a Java 6 version.
When it does not work do you use Deployment Toolkit to embed link into web page?
1) screenshot of the errorHere are links to several screenshots of errors we get:
http://dl.waterford.org/pics/error_install.png
http://dl.waterford.org/pics/error2.png
http://dl.waterford.org/pics/error3.png
Here is a link to the error in the java webstart failure dialog (details):
http://dl.waterford.org/pics/errormsg.txt
2) Enable full trace details (see http://docs.oracle.com/javase/7/docs/webnotes/tsg/TSG-Desktop/html/plugin.html#gcexdf)
and post trace fileHere is a link to the java console with full trace details:
http://dl.waterford.org/pics/javaconsole.txt
3) Install WireShark and see what http requests are made. Please post all request/response pairshttp://dl.waterford.org/pics/packets.pcap
Edited by: 933472 on May 10, 2012 1:30 PM

Start() failed on resource 'jackrabbit': XAER_RMFAIL : Resource manager ...

Hello Group,
We are using Weblogic Version 9.2.3 & facing some problem related to 'jackrabbit' not available. I feel we are facing problem similar to the one mentioned in following link
Re: What causes XAER_RMFAIL : Resource manager is unavailable / unregistered
Following above post, we tried increased the Initial Capacity of this 'jackrabbit' Resource Adapter to 50. Initially it was 1. Although this doesn't change anything. Although it works fine for a few hours but seems like after server has run for a few hours and served some requests it starts showing this exception.
Following is our weblogic-ra.xml file.
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-connector xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<native-libdir></native-libdir>
<jndi-name>repository</jndi-name>
<enable-access-outside-app>true</enable-access-outside-app>
<enable-global-access-to-classes>true</enable-global-access-to-classes>
<security></security>
<outbound-resource-adapter>
<default-connection-properties>
<pool-params></pool-params>
<logging></logging>
</default-connection-properties>
<connection-definition-group>
<connection-factory-interface>javax.jcr.Repository</connection-factory-interface>
<default-connection-properties>
<pool-params>
     <initial-capacity>50</initial-capacity>
     <max-capacity>100</max-capacity>
</pool-params>
<logging></logging>
<properties>
<property>
<name>HomeDir</name>
<value>jackrabbit-preferences</value>
</property>
<property>
<name>ConfigFile</name>
<value>jackrabbit-preferences/repository.xml</value>
</property>
</properties>
</default-connection-properties>
<connection-instance>
<jndi-name>jackrabbit</jndi-name>
<connection-properties>
<pool-params>
     <initial-capacity>50</initial-capacity>
     <max-capacity>250</max-capacity>
</pool-params>
<logging></logging>
<properties>
<property>
<name>HomeDir</name>
<value>jackrabbit-preferences</value>
</property>
</properties>
</connection-properties>
</connection-instance>
</connection-definition-group>
</outbound-resource-adapter>
</weblogic-connector>
Also please find below the exception that we see in the logs.
Caused by: ag.mycompany1.workflow.runtime.DocumentManagementServiceException: null: javax.jcr.RepositoryException: start() failed on resource 'jackrabbit': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'jackrabbit' is unavailable
     at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:1143)
     at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:685)
     at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1181)
     at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1115)
     at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:497)
     at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:429)
     at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:118)
     at weblogic.connector.outbound.ConnectionHandlerBaseImpl.prepareHandle(ConnectionHandlerBaseImpl.java:670)
     at weblogic.connector.outbound.ConnectionHandlerBaseImpl.createConnectionHandle(ConnectionHandlerBaseImpl.java:361)
     at weblogic.connector.outbound.ConnectionInfo.createConnectionHandle(ConnectionInfo.java:411)
     at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:308)
     at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
     at org.apache.jackrabbit.jca.JCARepositoryHandle.login(JCARepositoryHandle.java:98)
     at org.apache.jackrabbit.jca.JCARepositoryHandle.login(JCARepositoryHandle.java:89)
     at com.mycompany2.infinity.bpm.vfs.jcr.spring.JcrSessionFactory.createSession(JcrSessionFactory.java:38)
     at com.mycompany2.infinity.bpm.vfs.jcr.spring.JcrSessionFactoryUtils.getSession(JcrSessionFactoryUtils.java:72)
     at com.mycompany2.infinity.bpm.vfs.jcr.spring.JcrSessionFactory.getSession(JcrSessionFactory.java:33)
     at com.mycompany2.infinity.bpm.vfs.impl.jcr.AbstractJcrDocumentRepositoryService.doWithJcrVfs(AbstractJcrDocumentRepositoryService.java:537)
     at com.mycompany2.infinity.bpm.vfs.impl.jcr.AbstractJcrDocumentRepositoryService.doWithJcrVfs(AbstractJcrDocumentRepositoryService.java:564)
     at com.mycompany2.infinity.bpm.vfs.impl.jcr.AbstractJcrDocumentRepositoryService.retrieveFileContent(AbstractJcrDocumentRepositoryService.java:186)
     at com.mycompany2.infinity.bpm.vfs.impl.AbstractDocumentRepositoryServiceImpl.retrieveFileContent(AbstractDocumentRepositoryServiceImpl.java:46)
     at ag.mycompany1.workflow.runtime.beans.DocumentManagementServiceImpl$5.withVfs(DocumentManagementServiceImpl.java:112)
     at ag.mycompany1.workflow.runtime.beans.DocumentManagementServiceImpl.adaptVfsCall(DocumentManagementServiceImpl.java:417)
     at ag.mycompany1.workflow.runtime.beans.DocumentManagementServiceImpl.retrieveDocumentContent(DocumentManagementServiceImpl.java:108)
     at sun.reflect.GeneratedMethodAccessor826.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at ag.mycompany1.workflow.runtime.beans.interceptors.CallingInterceptor.invoke(CallingInterceptor.java:18)
     at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
     at ag.mycompany1.workflow.runtime.beans.interceptors.POJOExceptionHandler.invoke(POJOExceptionHandler.java:23)
     at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
     at ag.mycompany1.workflow.runtime.beans.interceptors.GuardingInterceptor.invoke(GuardingInterceptor.java:87)
     at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
     at ag.mycompany1.workflow.runtime.beans.interceptors.AbstractLoginInterceptor.performCall(AbstractLoginInterceptor.java:142)
     at ag.mycompany1.workflow.runtime.beans.interceptors.AbstractLoginInterceptor.invoke(AbstractLoginInterceptor.java:80)
     at ag.mycompany1.workflow.runtime.spring.SpringBeanLoginInterceptor.invoke(SpringBeanLoginInterceptor.java:58)
     at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
     at ag.mycompany1.workflow.runtime.spring.SpringSessionInterceptor$1.doInConnection(SpringSessionInterceptor.java:104)
     at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:342)
     at ag.mycompany1.workflow.runtime.spring.SpringSessionInterceptor.invoke(SpringSessionInterceptor.java:52)
     at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
     at ag.mycompany1.workflow.runtime.spring.SpringConfigurationInterceptor.invoke(SpringConfigurationInterceptor.java:94)
     at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
     at ag.mycompany1.workflow.runtime.beans.interceptors.PropertyLayerProviderInterceptor.invoke(PropertyLayerProviderInterceptor.java:85)
     at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
     at ag.mycompany1.workflow.runtime.beans.interceptors.DebugInterceptor.invoke(DebugInterceptor.java:25)
     at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
     at ag.mycompany1.workflow.runtime.spring.SpringTxInterceptor$1.doInTransaction(SpringTxInterceptor.java:62)
     at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:128)
     at ag.mycompany1.workflow.runtime.spring.SpringTxInterceptor.invoke(SpringTxInterceptor.java:47)
     at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.proceed(MethodInvocationImpl.java:95)
     at ag.mycompany1.workflow.runtime.interceptor.MethodInvocationImpl.execute(MethodInvocationImpl.java:55)
     at ag.mycompany1.workflow.runtime.beans.InvocationManager.invoke(InvocationManager.java:46)
     at $Proxy175.retrieveDocumentContent(Unknown Source)
     at ag.mycompany1.workflow.runtime.spring.DocumentManagementServiceBean.retrieveDocumentContent(DocumentManagementServiceBean.java:70)
     at sun.reflect.GeneratedMethodAccessor826.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at ag.mycompany1.workflow.runtime.spring.SpringServiceFactory$SpringServiceInvocationHandler.invoke(SpringServiceFactory.java:159)
     at $Proxy175.retrieveDocumentContent(Unknown Source)
     at com.infinity.bpm.ui.preferences.AbstractDocumentServicePreferencesManager.loadPreferences(AbstractDocumentServicePreferencesManager.java:318)
     at com.infinity.bpm.ui.preferences.AbstractDocumentServicePreferencesManager.getPreferences(AbstractDocumentServicePreferencesManager.java:269)
     at com.infinity.bpm.ui.preferences.AbstractDocumentServicePreferencesManager.getPreferencesEditor(AbstractDocumentServicePreferencesManager.java:133)
     at com.mycompany2.infinity.bpm.bcc.configuration.TrafficLightViewPropertyProvider.<init>(TrafficLightViewPropertyProvider.java:85)
     at com.mycompany2.infinity.bpm.bcc.configuration.TrafficLightViewPropertyProvider.getInstance(TrafficLightViewPropertyProvider.java:103)
     at com.mycompany2.sims.workflow.tlv.TrafficLightDataLoader.persistData(TrafficLightDataLoader.java:129)
     at com.mycompany2.sims.workflow.tlv.TrafficLightDataLoader.loadData(TrafficLightDataLoader.java:73)
     at com.mycompany2.sims.workflow.SyncSettingsBean.reload(SyncSettingsBean.java:73)
     at com.mycompany2.sims.workflow.EnterpriseSettings.isWorklistConfigured(EnterpriseSettings.java:143)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.myfaces.el.PropertyResolverImpl.getProperty(PropertyResolverImpl.java:457)
     at org.apache.myfaces.el.PropertyResolverImpl.getValue(PropertyResolverImpl.java:85)
     at com.sun.facelets.el.LegacyELContext$LegacyELResolver.getValue(LegacyELContext.java:141)
     at com.sun.el.parser.AstValue.getValue(AstValue.java:96)
     at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:183)
     at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71)
     at com.sun.facelets.tag.TagAttribute.getObject(TagAttribute.java:233)
     at com.sun.facelets.tag.TagAttribute.getBoolean(TagAttribute.java:79)
     at com.sun.facelets.tag.jstl.core.ChooseWhenHandler.isTestTrue(ChooseWhenHandler.java:49)
     at com.sun.facelets.tag.jstl.core.ChooseHandler.apply(ChooseHandler.java:67)
     at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:314)
     at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:169)
     at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47)
     at com.sun.facelets.tag.jsf.core.ViewHandler.apply(ViewHandler.java:109)
     at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49)
     at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:25)
     at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95)
     at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:524)
     at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:567)
     at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:182)
     at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
     at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:132)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:140)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:147)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at ag.mycompany1.web.jsf.common.ExceptionFilter.doFilter(ExceptionFilter.java:45)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:290)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:250)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:207)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:161)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at ag.mycompany1.web.jsf.common.LoginFilter.doFilter(LoginFilter.java:250)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3251)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2010)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1916)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
: start() failed on resource 'jackrabbit': XAER_RMFAIL : Resource manager is unavailable
Any help in this regard is highly appreciated. Thanks.

Hi,
Can you please try increase the below MaxXACallMillis setting in Weblogic set 'Maximum Duration of XA Calls' to a bigger value
MaxXACallMillis: Sets the maximum allowed duration (in milliseconds) of XA calls to XA resources. This setting applies to the entire domain.
http://docs.oracle.com/cd/E12840_01/wls/docs103/jta/trxcon.html
The parameter is exposed through administration console: services --> jta --> advanced --> "Maximum Duration of XA Calls:"
Check the below docs for more information
WLS 10.3: Intermittent XA error: XAResource.XAER_RMERR (Doc ID 1118264.1)
Hope it Helps

SMC 4.0 db-start failed

Dear All ,
I try install smc 4.0 on another sun box ,the reason for test CCR problem from on t2000 box ,I use same file which use for install smc on t2000 , but on step es-setup i got the problem (db-start failed).Here the log installation :
Initiating setup for Sun Management Center Agent Component.
This part of the setup process does the Sun Management Center Agent Component setup.
Started /opt/SUNWsymon/lib/sbin/sm_setup_agent.sh at Thu Nov 8 20:16:52 BNT 2007.
Running on SunOS sun240 5.10 Generic_120011-14 sun4u sparc SUNW,Sun-Fire-V240.
Copying snmpd.conf file into /var/opt/SUNWsymon/cfg
Server component also installed locally.
Using this machine as the Sun Management Center server.
---------------------------- WARNING ---------------------------
It appears that agent.snmpPort 161 is already in use.
Sun Management Center 4.0 agent may not be able to run due to this conflict.
There are two ways to correct this conflict:
1. Reconfigure the port that Sun Management Center 4.0 uses.
2. Stop the process that is using the port.
Press RETURN to force default port.
Enter port you would like to use [ 1100 to 65535 ]: 1161
Updating /var/opt/SUNWsymon/cfg/domain-config.x with new port number.
Generating agent security keys.
PKCS11 Utilities package(SUNWcsl) was found.
Encrypted SNMP Communication is supported.
Setup of Agent component is successful.
Starting Sun Management Center database setup...
verifyDatabaseDown: instance is not executing
Database consistency information missing.
Configuring database initialization parameter file
Stopping metadata component
Successfully disabled service sunmc-metadata
Stopping cfgserver component
Successfully disabled service sunmc-cfgserver
Stopping topology component
Successfully disabled service sunmc-topology
Stopping event component
Successfully disabled service sunmc-event
Stopping grouping service
Successfully disabled service sunmc-grouping
Stopping trap component
Successfully disabled service sunmc-trap
Stopping java server
Successfully disabled service sunmc-javaserver
Stopping webserver
Successfully disabled service sunmc-webserver
Stopping agent component
Successfully disabled service sunmc-agent
Stopping platform component
Successfully disabled service sunmc-platform
verifyDatabaseDown: instance is not executing
Failed to enable service sunmc-database
Database setup failed : db-start failed
Updating registry...
As database is not setup, Marking server setup as failed in Registry.
None of the base layers are setup.
No Addon is setup.
Following Addons are not yet setup: Advanced System Monitoring,ELP Config-Reader Monitoring,Desktop,Service Availability Manager,Sun Fire Entry-Level Midrange System,Performance Reporting Manager,Solaris Container Manager,System Reliability Manager,Workgroup Server
Could not finish requested task.
I am already uninstall(use uninstall script ) and reinstall back , but the result is same , Does any one know how to solve this problem ?
Regards
hadi

Greetings,
I've not been able to resolve the topology issues, the recommended fixes have not resolved my issues. Upon un-installaing and re-installing multiple times I'm still not able to get the topology component to initialize correctly. The Management Center does display in the Applications listing in the Java Web Console (3.0.2) however clicking on it and displaying the main page for the Management Center 4.0 displays just a few items in the left nav, and none of the 'Discover Systems' requests make it in the queue or work at all. None of the other Management modules are displayed either. The web start console refuses to connect to the server as well, replying with a 'Server communication error, the server version may be incompatible' error.
I've noticed quite a bit of sql errors in the install, I've not seen anything in the release notes or forums regarding this issue either. Any help on this would be greatly appreciated! SMA and snmpdx are both disabled as well as dmi services.
The server is x86 Dell 2950, Entire install of Solaris 10 U3 11/06. Agent, Server, and Console components are installed and setup.
*/etc/project:*
system:0::::
user.root:1::::
noproject:2::::
default:3::::project.max-shm-memory=(priv,5368708912,deny)
group.staff:10::::
from */var/adm/messages:*
Dec 19 12:19:21 dvall topology[963]: [ID 840589 daemon.alert] syslog Dec 19 12:19:21 topology parsing error in file://localhost/topology-license-d.x;flags=ro(13):
Dec 19 12:19:21 dvall topology[963]: [ID 259113 daemon.alert] syslog Dec 19 12:19:21 topology *** aborting execution ***
install log:
Started ./es-inst at Wed Dec 19 11:50:19 PST 2007.
Running on SunOS dvall 5.10 Generic_125101-07 i86pc i386 i86pc.
This script installs Sun (TM) Sun Management Center 4.0
Installation files source directory: /root/src/SunMC/disk1/image/SunOS/i386
Copying required XML APIs from /root/src/SunMC/disk1/sbin/bin/i386-sun-solaris10 to /var/run/tmp/SunMCInstall/XML/APIs
Enter the directory in which you want to install: [ /opt ] /opt/SunMC/
Installation destination directory: /opt/SunMC
Select the Sun Management Center 4.0 components to install:
3 component(s) are available for your selection:
Do you want to install the Server component (y|n|q) y
Note: The Agent component will be installed automatically.
Do you want to install the Console component (y|n|q) y
Looking for valid JDK.
Found incomplete installation of : "1.6.0_03-b05"
SYMON_JAVAHOME is set to: /usr/java
JDK version is: "1.6.0_03-b05"
JDK check OK.
Looking for Tomcat Webserver.
Webserver check OK.
You must agree to the above license agreement to proceed with installation.
Do you agree (y|n|q) y
Sun Management Center 4.0 can be installed in the following languages:
Traditional Chinese
Simplified Chinese
French
Japanese
Korean
English is installed by default.
Are other languages required (y|n|q) n
Reading Add-On products from image. Please wait...
This can take approximately 3 minutes to complete.
Found: Sun Management Center Integration for Unicenter TNG
Found: Advanced System Monitoring
Found: System Reliability Manager
Found: Generic X86/X64 Config Reader
Found: Solaris Container Manager
Found: Service Availability Manager
Found: Performance Reporting Manager
Checking for applicable products. Please wait...
This can take approximately 2 minutes to complete.
Unable to find package directory for SUNWeshsm
Component script found: check-remote-install.sh
Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/TNG/Solaris_10/Basic//check-remote-install.sh
Return value: 1
Component script found: check-remote-install.sh
Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/TNG/Solaris_10/Basic//check-remote-install.sh
Return value: 1
Component script found: check_TNG_Server.sh
check if TNG Server is installed.
Cannot install the Unicenter TNG addon Server component. CA-TNG is not installed, you should install CA-TNG first.
Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/TNG/Solaris_10/Basic//check_TNG_Server.sh
Return value: 2
Script returned 2. Skipping this component.
Component script found: gca-check.sh
Running: /root/src/SunMC/disk1/image/SunOS/i386/Addons/X86ConfigReader/Solaris_10/Basic//gca-check.sh
Return value: 1
The Sun Management Center 4.0 Production environment will be installed.
The following Add-On Products are applicable for installation.
Advanced System Monitoring
Service Availability Manager
Performance Reporting Manager
Solaris Container Manager
System Reliability Manager
Sun Management Center Integration for Unicenter TNG
Generic X86/X64 Config Reader
Do you want to select all the products (y|n|q) n
Select the products you want to install:
Advanced System Monitoring (y|n|q) y
Service Availability Manager (y|n|q) y
Performance Reporting Manager (y|n|q) y
Solaris Container Manager (y|n|q) y
System Reliability Manager (y|n|q) y
Sun Management Center Integration for Unicenter TNG (y|n|q) n
Generic X86/X64 Config Reader (y|n|q) y
The following Add-On Products will be installed:
Advanced System Monitoring
Service Availability Manager
Performance Reporting Manager
Solaris Container Manager
System Reliability Manager
Generic X86/X64 Config Reader
Do you want to proceed (y|n|q) y
The following Add-On products are covered under license agreement:
You must agree to the above license agreement to proceed with installation.
Do you agree (y|n|q) y
Disk Space Checking....
Installing the components...
Installing... PRODUCT.PE COMPONENT.AGENT
Processing package instance <SUNWescom> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Common Components(i386) 4.0,REV=2.10.2007.10.23
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
Installing Sun Management Center Common Components as <SUNWescom>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
2426 blocks
## Executing postinstall script.
Installation of <SUNWescom> was successful.
Processing package instance <SUNWenesi> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center script localization messages(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
1 package pathname is already properly installed.
Installing Sun Management Center script localization messages as <SUNWenesi>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
683 blocks
Installation of <SUNWenesi> was successful.
Processing package instance <SUNWesagt> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Agent(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
3 package pathnames are already properly installed.
Installing Sun Management Center Agent as <SUNWesagt>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
24750 blocks
## Executing postinstall script.
Installation of <SUNWesagt> was successful.
Processing package instance <SUNWesmib> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Mib Instance Module(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
4 package pathnames are already properly installed.
Installing Sun Management Center Mib Instance Module as <SUNWesmib>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
281 blocks
Installation of <SUNWesmib> was successful.
Processing package instance <SUNWesken> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Kernel Reader Module(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
5 package pathnames are already properly installed.
Installing Sun Management Center Kernel Reader Module as <SUNWesken>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
399 blocks
Installation of <SUNWesken> was successful.
Processing package instance <SUNWesmod> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Agent Modules(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
9 package pathnames are already properly installed.
Installing Sun Management Center Agent Modules as <SUNWesmod>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
235 blocks
Installation of <SUNWesmod> was successful.
Processing package instance <SUNWesae> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Agent System Files(i386) 4.0,REV=2.10.2007.10.15
Using </> as the package base directory.
## Processing package information.
## Processing system information.
9 package pathnames are already properly installed.
Installing Sun Management Center Agent System Files as <SUNWesae>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
28 blocks
## Executing postinstall script.
Installation of <SUNWesae> was successful.
Processing package instance <SUNWesaem> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Event Module for Agent(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
9 package pathnames are already properly installed.
Installing Sun Management Center Event Module for Agent as <SUNWesaem>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
186 blocks
Installation of <SUNWesaem> was successful.
Processing package instance <SUNWesgui> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center GUI Installation(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
7 package pathnames are already properly installed.
Installing Sun Management Center GUI Installation as <SUNWesgui>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
6250 blocks
Installation of <SUNWesgui> was successful.
Processing package instance <SUNWsuagt> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Dynamic Agent Update Agent Components(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
6 package pathnames are already properly installed.
Installing Sun Management Center Dynamic Agent Update Agent Components as <SUNWsuagt>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
152 blocks
Installation of <SUNWsuagt> was successful.
Processing package instance <SUNWesval> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Validation Tool Components(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
4 package pathnames are already properly installed.
Installing Sun Management Center Validation Tool Components as <SUNWesval>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
220 blocks
Installation of <SUNWesval> was successful.
Processing package instance <SUNWesaxp> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Java API for XML Processing (JAXP) v1.1.3(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Java API for XML Processing (JAXP) v1.1.3 as <SUNWesaxp>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
2362 blocks
Installation of <SUNWesaxp> was successful.
Processing package instance <SUNWesmcp> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Module Configuration Propagation(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
8 package pathnames are already properly installed.
Installing Sun Management Center Module Configuration Propagation as <SUNWesmcp>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
249 blocks
Installation of <SUNWesmcp> was successful.
Processing package instance <SUNWeslac> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Local Access(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
3 package pathnames are already properly installed.
Installing Sun Management Center Local Access as <SUNWeslac>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
14 blocks
Installation of <SUNWeslac> was successful.
Processing package instance <SUNWesafm> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center FMA Service Module for Agent(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
5 package pathnames are already properly installed.
Installing Sun Management Center FMA Service Module for Agent as <SUNWesafm>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
92 blocks
Installation of <SUNWesafm> was successful.
Package SUNWservicetagr is already installed on this system.
Validating the Registry entry.
Package SUNWservicetagu is already installed on this system.
Validating the Registry entry.
Package SUNWstosreg is already installed on this system.
Validating the Registry entry.
Installing... PRODUCT.PE COMPONENT.CONSOLE
Package SUNWescom is already installed on this system.
Validating the Registry entry.
Package SUNWenesi is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWescon> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Console(i386) 4.0,REV=2.9.2007.10.16
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
4 package pathnames are already properly installed.
Installing Sun Management Center Console as <SUNWescon>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
6638 blocks
Installation of <SUNWescon> was successful.
Processing package instance <SUNWesjp> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Additional Components(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Additional Components as <SUNWesjp>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
5819 blocks
Installation of <SUNWesjp> was successful.
Package SUNWesaxp is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesclt> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Client API(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Client API as <SUNWesclt>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
1609 blocks
Installation of <SUNWesclt> was successful.
Processing package instance <SUNWesjrm> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Client API support classes(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Client API support classes as <SUNWesjrm>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
663 blocks
Installation of <SUNWesjrm> was successful.
Processing package instance <SUNWenesf> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Console properties(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Console properties as <SUNWenesf>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
557 blocks
## Executing postinstall script.
Installation of <SUNWenesf> was successful.
Package SUNWesgui is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesasc> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Advanced Services Console(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Advanced Services Console as <SUNWesasc>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
156 blocks
Installation of <SUNWesasc> was successful.
Processing package instance <SUNWescix> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Import/Export(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Import/Export as <SUNWescix>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
156 blocks
Installation of <SUNWescix> was successful.
Processing package instance <SUNWsucon> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Dynamic Agent Update Console Components(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Dynamic Agent Update Console Components as <SUNWsucon>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
27 blocks
Installation of <SUNWsucon> was successful.
Processing package instance <SUNWescli> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Command Line Interface(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
5 package pathnames are already properly installed.
Installing Sun Management Center Command Line Interface as <SUNWescli>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
862 blocks
Installation of <SUNWescli> was successful.
Processing package instance <SUNWesclb> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Command Line Interface For BatchMode(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
4 package pathnames are already properly installed.
Installing Sun Management Center Command Line Interface For BatchMode as <SUNWesclb>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
155 blocks
Installation of <SUNWesclb> was successful.
Package SUNWesval is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesmc> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center MCP Console(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
3 package pathnames are already properly installed.
Installing Sun Management Center MCP Console as <SUNWesmc>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
200 blocks
Installation of <SUNWesmc> was successful.
Processing package instance <SUNWescdv> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Console Dataview(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
3 package pathnames are already properly installed.
Installing Sun Management Center Console Dataview as <SUNWescdv>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
354 blocks
Installation of <SUNWescdv> was successful.
Installing... PRODUCT.PE COMPONENT.SERVER
Package SUNWescom is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesbui> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Web Console(sparc) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
3 package pathnames are already properly installed.
Installing Sun Management Center Web Console as <SUNWesbui>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
7789 blocks
Installation of <SUNWesbui> was successful.
Processing package instance <SUNWesbuh> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Help(sparc) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Help as <SUNWesbuh>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
498 blocks
Installation of <SUNWesbuh> was successful.
Package SUNWenesi is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesdb> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Database(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management Center Database as <SUNWesdb>
## Executing preinstall script.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Group smcdbg created
User smcdbu created
## Installing part 1 of 1.
/opt/SunMC/SUNWsymon/base <conflicting pathname not installed>
/opt/SunMC/SUNWsymon/base/bin <conflicting pathname not installed>
/opt/SunMC/SUNWsymon/base/bin/i386-sun-solaris2.10 <conflicting pathname not installed>
/opt/SunMC/SUNWsymon/base/lib <conflicting pathname not installed>
/opt/SunMC/SUNWsymon/base/lib/i386-sun-solaris2.10 <conflicting pathname not installed>
/opt/SunMC/SUNWsymon/lib/sbin <conflicting pathname not installed>
/opt/SunMC/SUNWsymon/sbin <conflicting pathname not installed>
928 blocks
Installation of <SUNWesdb> was successful.
Package SUNWesagt is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWessrv> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Server(i386) 4.0,REV=2.9.2007.10.16
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
12 package pathnames are already properly installed.
Installing Sun Management Center Server as <SUNWessrv>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
10640 blocks
[ verifying class <preserve> ]
Installation of <SUNWessrv> was successful.
Processing package instance <SUNWessa> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Server/Agent(i386) 4.0,REV=2.10.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
10 package pathnames are already properly installed.
Installing Sun Management Center Server/Agent as <SUNWessa>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
2218 blocks
Installation of <SUNWessa> was successful.
Package SUNWesjp is already installed on this system.
Validating the Registry entry.
Package SUNWesaxp is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesse> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Solaris_10/Basic>
Sun Management Center Server System Files(i386) 4.0,REV=2.10.2007.10.15
Using </> as the package base directory.
## Processing package information.
## Processing system information.
5 package pathnames are already properly installed.
Installing Sun Management Center Server System Files as <SUNWesse>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
36 blocks
## Executing postinstall script.
Installation of <SUNWesse> was successful.
Package SUNWesclt is already installed on this system.
Validating the Registry entry.
Package SUNWesjrm is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWmeta> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Metadata Agent(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
3 package pathnames are already properly installed.
Installing Sun Management Center Metadata Agent as <SUNWmeta>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
38 blocks
Installation of <SUNWmeta> was successful.
Package SUNWenesf is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesmdr> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center MDR for Basic Pack(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
4 package pathnames are already properly installed.
Installing Sun Management Center MDR for Basic Pack as <SUNWesmdr>
## Installing part 1 of 1.
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
246 blocks
Installation of <SUNWesmdr> was successful.
Package SUNWesgui is already installed on this system.
Validating the Registry entry.
Processing package instance <SUNWesweb> from </root/src/SunMC/disk1/image/SunOS/i386/PE/Common/Basic>
Sun Management Center Web Console(i386) 4.0,REV=2.9.2007.10.15
Using </opt/SunMC> as the package base directory.
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
Installing Sun Management C

WLC 2106 does not send DHCP request

Hi,
I've several WLC2106 running 4.1(185) and all is working fine.
Now we started to migrate some of them to 4.2(207) but client didn't received anymore DHCP reply.
DHCP server is a Microsoft server with the address configuren under the dynamic interfaces parameter.
With the same config and 4402 all is working fine.
With the same config and 4.1.x with WLC2016 all is working fine.
It seems something changed from 4.2.
Any idea ? Here the log of DEBUG DHCP PACKET
00:22:fb:89:d1:dc DHCP received op BOOTREQUEST (1) (len 312, port 1, encap 0xec03)
00:22:fb:89:d1:dc DHCP processing DHCP DISCOVER (1)
00:22:fb:89:d1:dc DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 0
00:22:fb:89:d1:dc DHCP xid: 0x5cbacd54 (1555746132), secs: 3, flags: 0
00:22:fb:89:d1:dc DHCP chaddr: 00:22:fb:89:d1:dc
00:22:fb:89:d1:dc DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
00:22:fb:89:d1:dc DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
00:22:fb:89:d1:dc DHCP requested ip: 169.254.122.145
00:22:fb:89:d1:dc DHCP successfully bridged packet to DS
00:10:18:3d:9c:2b DHCP received op BOOTREQUEST (1) (len 268, port 1, encap 0xec00)
00:10:18:3d:9c:2b DHCP dropping packet (no mscb) found - (giaddr 0.0.0.0, pktInfo->
Many thanks
Luigi

In 4.1, disabling DHCP proxy did just that, it disabled the "proxy". If you ever look at your dhcp lease of a wireless client, it comes from a dhcp server of 1.1.1.1 (virtual IP of the controller). With proxy disabled, the address will no longer be masked.
In 4.2 and beyond, disabling dhcp proxy actually disables the DHCP Relay that is the process of the controller sending the dhcp requests to a specified server.
So if in 4.1, you had "dhcp proxy" disabled, in 4.2 and beyond, you are actually disabling the relay as well.
If this is indeed the case, enable dhcp proxy, or add an IP Helper adress to your router for this vlan, just like you would normally do for Wired clients.

DHCP wont start automatically

I can't connect to the internet unless I manually go into control panel>administrator tools>services>DHCP and start it manually. I'm hard wired to a link sys router. I'm not sure why the configuration changed
How do I get DHCP to start automatically?
thanks
[Personal Information Removed]

If DHCP service is not starting automatically but you are able to start the service manually, it might be because the service is not set to Automatic. Request you to perform the following steps to set to automatic:
1. Click Start, click in the Start Search box, type services.msc, and then press ENTER.
2. Optionally, export and save a list of the existing settings. To do this, right-click Services, select Export List, and save the settings list.
3. In the details pane, right-click the service that you want to configure, and then click Properties.
4. On the General tab, in Startup type, Select Automatic.
5. Click OK.
6. Restart the system
If the issue do not get resolve, please let me know so that I can suggest another solution.
I am an HP employee.
Regards,
Vidya
Make it easier for other people to find solutions, by marking my answer “Accept as Solution” if it solves your problem.
***Click on "Thumbs up" button to the bottom right side of my post to say thanks!***

OPMN start failed - but I can see opmn -d running via ps -ef

I am trying to figure out why I keep getting the message OPMN start failed when trying to start OPMN. The thing I don't understand is why I can see the processes opmn -d running when I look via ps -ef.
If I run the opmnctl startall command once more then everything comes up and no error messages.
Any Ideas?

I had the same isssue.
Unix Solaris 10, Oracle Application Server 10gr2
After starting the infrastructure database and listener the issuing of opmctl startall (starting HTTP Server, OID, OC4J_SECURITY) failed with opmnctl: opmn start failed from time to time.
In addition, when starting the application server processes (Forms Container...) the processes will rereive a timeout and die later.
Reading the server logs (e.g. $ORACLE_HOME/dcm/logs/emd_logs/log.xml) on the infrastructure but also on the application server delivered :
oracle.ias.repository.schema.SchemaDescription: Unable to establish connection to the Oracle Internet Directory Sever
I came to the impression that the database listener process potentially was not yet fully initialized to receive requests
from the upstarting infrastructure processes due to the fact that the commands will get issued in a startup-script.
Solution : after starting the listener (before starting up the infrastructure processes) I entered sleep 10 (wait 10 seconds) in the startup-script, the problem is gone by now...

Opmnctl:OPMN start failed

hi
I am trying to run opmnctl manually. Bt it is showing error ie:
opmnctl: starting opmn and all managed processes...
opmnctl: opmn start failed
i checked opmn/logs
opmn.log is empty
ons.log shows error ie:
19:22:45 [4] ONS server initiated
19:22:45 [2] 10.209.178.16:6200 - thread create failed
ipm.log showing error ie:
13/06/18 13:53:50 [4] PM state directory exists: /u02/app/orapp/product/10.1.2/opmn/logs/states
13/06/18 13:53:50 [4] PM state file does not exist: /u02/app/orapp/product/10.1.2/opmn/logs/states/.opmndat
13/06/18 13:53:50 [4] OPMN server ready. Request handling enabled.
opmn status:
Unable to connect to opmn.
Opmn may not be up.
plz tell how can i resolve this issue??

apply solution form the below note
adapcctl.sh: exiting with status 150 [ID 1106795.1]
was this working before?
if yes then what changes has been done?
did you run autoconfig?
pleas perform below task
1 - open a new shell and set your apps environment
2 - cd $ADMIN_SCRIPTS_HOME
3 - adopmnctl.sh stop
4 - check if it is really down: ps -ef grep grep opm
5 - delete the following:
rm -fr $INST_TOP/ora/10.1.3/j2ee/oacore/persistence/*
rm -fr $INST_TOP/ora/10.1.3/j2ee/oafm/persistence/*
rm -fr $INST_TOP/ora/10.1.3/j2ee/forms/persistence/*
6 - adopmnctl.sh start
AppsMasti
Sharing is Caring

Oracle.sysman.emSDK.util.jdk.EMException: The opmn request has failed

Hi,
We are having a tough time installing Oracle 9ias on win2k prof. We installed Oracle 9ias infrastructure 9.0.2 on win2k and then installed Oracle 9ias app server on the same machine.While starting the http server of Infrastructure, we got the following error:
oracle.sysman.emSDK.util.jdk.EMException: The opmn request has failed. From opmn: HTTP/1.1 204 No Content Content-Length: 0 Content-Type: text/html Response: 0 of 1 processes started. Check opmn log files such as ipm.log and ons.log for detailed.
We have a 512 MB RAM.It is very difficult to identify the problems from the opmn log files.Can anyone suggest as to where we are going wrong.
Thanks a lot.
Manash

Richard,
How can I get my boss to read this thread? :)
OK, the password. Here is a little known tidbit--don't tell anyone, ok? Your DAD can log in as any user--any user at all (with connect privs). The good thing about the HTMLDB_PUBLIC_USER is that it has the bare minimum permissions, so it is a good safe choice. But, the good news is, the HTMLDB_PUBLIC_USER password is only used by HTMLDB, so you can change it (log in to sqlplus
sql> alter user HTMLDB_PUBLIC_USER identified by mysecretpassword; )
The use mysecretpassword. You will also need to change it in the htmldb marvel.conf if you want to continue to use that mid-tier as well.
You can put the alias for /i/ directly in the httpd.conf. Not sure of your OS, but make sure that the OS level portion has a / not \ for the last two (e.g. windows normally might look like c:\oracle\home\images\ but you want c:\oracle\home/images/ -- just a strange quirk)
Take a look at the other aliases in the httpd.conf to see the syntax.
Also, I usually don't put it directly in the httpd.conf file because I want to make upgrades easier. I usually create an include file and put all of my stuff in there. So I would create anton.conf, put the alias in there, and then put
include anton.conf
in the httpd.conf file
Whew -- a little flattery earns a long drawn out answer!
Anton

ASA DHCP Request incorrect hostname length

I have an ASA 5505 with software version 8.2(1). It is making DHCP requests for IPSec clients that connect to the ASA. The DHCP requests packets the ASA makes have an extra '00' appended to the hostname field, and the length field is the size of the hostname + 1.
The DHCP server is Microsoft Server 2003 and this causes the hostname to be registered with an unknown character which appears as []hostname. Then when server 2003 tries to update the DNS record, it fails because of the invalid character in the hostname.
Is there anyway to have the ASA have the correct length for the hostname field in the DHCP packet, or a workaround that will solve this problem?

I am thinking it may not be option 12 in the DHCP packet, but option 81. I have included a portion of the DHCP request from the ASA below:
   Option: (t=53,l=1) DHCP Message Type = DHCP Request
        Option: (53) DHCP Message Type
        Length: 1
        Value: 03
    Option: (t=57,l=2) Maximum DHCP Message Size = 1152
        Option: (57) Maximum DHCP Message Size
        Length: 2
        Value: 0480
    Option: (t=61,l=42) Client identifier
        Option: (61) Client identifier
        Length: 42
        Value: 00636973636F2D303032312E353537352E636131372D6D79...
    Option: (t=54,l=4) Server Identifier = 192.168.8.3
        Option: (54) Server Identifier
        Length: 4
        Value: C0A80803
    Option: (t=50,l=4) Requested IP Address = 192.168.8.105
        Option: (50) Requested IP Address
        Length: 4
        Value: C0A80869
    Option: (t=12,l=11) Host Name = "myhostname"
        Option: (12) Host Name
        Length: 11
        Value: 6D79686F73746E616D6500
    Option: (t=51,l=4) IP Address Lease Time = 8 days
        Option: (51) IP Address Lease Time
        Length: 4
        Value: 000A8C00
    Option: (t=55,l=6) Parameter Request List
        Option: (55) Parameter Request List
        Length: 6
        Value: 01060F2C0321
        1 = Subnet Mask
        6 = Domain Name Server
        15 = Domain Name
        44 = NetBIOS over TCP/IP Name Server
        3 = Router
        33 = Static Route
    Option: (t=81,l=14) Client Fully Qualified Domain Name
        Option: (81) Client Fully Qualified Domain Name
        Length: 14
        Value: 0400000A6D79686F73746E616D65
        Flags: 0x04
        0000 .... = Reserved flags: 0x00
        .... 0... = Server DDNS: Some server updates
        .... .1.. = Encoding: Binary encoding
        .... ..0. = Server overrides: No override
        .... ...0 = Server: Client
        A-RR result: 0
        PTR-RR result: 0
        Client name: 0A6D79686F73746E616D65
    End Option
    Padding
Notice in option 81 the Client Name has a leading binary value of 0A (which is a new line): 0A6D79686F73746E616D65.
Does CSCsz07757 relate to that? Is there a way to have the ASA not include option 81 as part of the DHCP requests it makes?
Thank you.

Android Phone: DHCP request although static IP configured

I face a strange behavior while connecting to WiFi with my Android phone.
When I configure the WiFi settings to use a static IP at home with a Speedport router from Telekom everything works fine. I get a connection imediately. (Security credentials are WPA2-PSK/AES).
But when I try to connect to a Cisco environment (1142 access points with 5508 controller with the same security credentials as at home) after PSK authentication the phone start with DHCP requests instead of using the configured static IP and I don't get a connection.
First I thought it was of the Android ROM or the device but I tried different ROMs (stocks and customs) and different devices (Defy and Galaxy S). Everytime the same thing.
A laptop or an iPhone can connect without any problem using a static IP.
It seems that the controller or AP sends something to the phone telling it to ignore the static IP settings...
Strange!!!

When you set static IP information on an adapter that disables DHCP for that adapter. It no longer communicates with the DHCP server. The only thing that can go wrong at this point is the IP information you are specifying on the adapter is misconfigured. Don't forget that in static ip config you need to also specify DNS servers.
The DHCP server may or may not detect the static IP on the network depending on the DHCP Server software.
Please remember to Kudo those that help you.
Linksys
Communities Technical Support

RTC-request process failed

Hello:
I have configured collaboration services(RTC,SCF,Groupware)according
to online help.Now I can send instant message and application sharing using EP with other users.But after I logged on my portal,a pop-up window always presented.It prompt me that RTC-request process failed.
Please give me suggestion to solve this problem.
Thanks

Sorry, I wasn't really replying to your problem, I was adding some questions on this topic. I try to better explain my problems, all about Collaboration Launch Pad (CLP).
I've configured the Portal using English as main language, then I've assigned portal roles to users whose logon language is Italian. When these Italian users start application sharing, the popup window for selecting the application to share doesn't responde to "OK", "Cancel" and "Refresh" buttons, the only way to close the popup is to use the "X" button, but this action doesn't allow the user to participate in another real time session unless logging off.
Another problem is about the online status of the Administrator user: when set to "Automatically Detect Status" the icon is "blank", like if it where not possible to determine the status (but this does not occur always).
The last issue: when I try to share an application with another user, the popup window for selecting the application appears to the other user and not to me!!!
After clearing the cache of the browser, many of the problems above do not occur any more, except for the one regarding the language of the user.
Any suggestions?
Pasquale

Your request has failed. please try again later for messaging and web app my verizon

>> Duplicate post removed to comply with the Verizon Wireless Terms of Service Please see Cannot view messaging on computer at my verizon all of a sudden. using messages <<
Message was edited by: Verizon Moderator

I am having the same problem. It started on August 11, 2014. I get the "Your request has failed. Please try again later." message when logging into the Verizon Messaging web application.
Here is what I did to troubleshoot it:
I verified that I can log into the MyVerizon account successfully.
Verified that the feature was set up correctly.
Cleared cache and history on my browser.
Tried two different browsers - same result.
Tried a different computer - same result.
Tried from a mobile device - same result.
It is definitely on the Verizon end. I called their tech support and of course, got no results as usual.
Verizon creates and promotes all these features, you get dependent on using them, and they stop working. Then, of course Verizon can't resolve the issue. I'm shopping around when my contracts are up. For the premium price we pay for Verizon I would expect better stability and support in their service.

DHCP request at system startup via shell script

Hi all,
I administer about 120 macs and a couple of weeks ago the network admin changed the ipv4 network and the dhcp-leases, -ranges.
My macs do not get an ip address when they start up.
It takes about one minute until the request is succeeded.
I am about to write a shell script that starts a dhcp request over the network.
I want to use the same command that the network system pref (Renew DHCP Lease) uses.
I read the bootpd, xinetd, lookupd manual but I am not sure wich one is the correct deamon to use.
Someone can help?
Thanks in advance
Cheers Thorsten

Seen the ipconfig yet?
http://developer.apple.com/documentation/Darwin/Reference/ManPages/man8/ipconfig .8.html
Two ways to renew a lease in Terminal, adjust your enNUMBER accordingly...
sudo ipconfig set en0 BOOTP;sudo ipconfig set en0 DHCP
sudo ifconfig en1 down;sudo ifconfig en1 up

Upgrade phase STARTSAP_NBAS error: SYSTEM START failed

During an upgrade from BW 3.5 to BI 7.0, I get the following error
message in phase STARTSAP_NBAS:
SYSTEM START failed, code -2
-2: the test rfc did not work.
Try to log on to the system with user DDIC
When I try to log on to the system as user DDIC, I get the following
error message:
DB-Error -0
The same thing happens when I try to log on as SAP*. I am certain that
the password I submit is correct. I have not changed this password at
any time.
I have included SAP_BASIS support package 14 into this upgrade, and
this requires kernel version 133 at least (Note 822379). This kernel
was copied into the usr\sap\put\exenew directory before the upgrade
began. However, the system still seems to run on kernel version 111.
I have tried to put the 133 kernel into
F:\usr\sap\BWS\SYS\exe\nuc\NTAMD64 so that it is copied into
F:\usr\sap\BWS\SYS\exe\run during system startup, but then all my work
processes die. The gateway also seems to be down using this kernel.
Please help!
Regards,
Thomas

Hi.
I made a stupid mistake.. the kernel I was using was unicode, but I should use a non-unicode kernel..
Regards,
Thomas

DHCP Requests Starts Failing

Similar Messages

Maybe you are looking for