This discussion is archived
2 Replies Latest reply: Jan 21, 2013 12:13 AM by AlanGarde RSS

Unable to associate network - Failed to determine the network address reach

AlanGarde Newbie
Currently Being Moderated
I have a simple test deployment of Ops Center -

Single EC with co-located proxy, single network.

I have discovered some servers successfully on various other subnets (which are all routable and un-firewalled from my proxy). It has therefore created those networks. However they are not listed as "Associated Networks" (Administration -> Enterprise Controller -> <EC name>).

If I click on "Associate Networks" and choose one of my discovered subnets the "Associate a network to a Proxy Controller" job fails with

"NetworkTestTask - Failed to determine the reachability of network address X.X.X.0"

This is stopping me deploying OS's to those servers.

ob ID : testec.79
Job Name : 192.168.198.0/23
Job Type : Associate a network to a Proxy Controller.
Job Description : -
Run ID : 1
Status : FAILED
Mode : Actual run
Owner : ocroot
Create Date : 01/17/2013 02:30:57 PM GMT
Start Date : 01/17/2013 02:30:57 PM GMT
Last Updated : 01/17/2013 02:31:01 PM GMT
Execution Order : PARALLEL
Failure Policy : ABORT_ON_ANY_FAILURE


Task : NetworkTestTask
Task Run ID : 488
Target : testec
Status : FAILED
Result : Failed to determine the reachability of network address 192.168.198.0. (81136)
Logs :
01/17/2013 02:30:58 PM GMT INFO Invoking the prepare method of this target. (15018)
01/17/2013 02:30:58 PM GMT INFO Task is posted to the Proxy Controller (testec-8e23e639), from the Enterprise Controller. (15011)
01/17/2013 02:31:00 PM GMT INFO Task is received by the Proxy Controller. (15012)
01/17/2013 02:31:00 PM GMT ERROR Failed to determine the network address reachability of IP address X.X.X.0. (81131)
01/17/2013 02:31:00 PM GMT ERROR Failed to check connectivity to the specified IP address, X.X.X.0 (81130)

Cocao log -

Jan 17, 2013 2:30:58 PM com.sun.scn.jobmanager.common.impl.TaskExecutionThread run
INFO: thr#450:"JM-testec.79.1.323.488_testec-8e23e639/com.sun.hss.domain:name=localhost,type=OperatingSystem" ************* Start Task - NetworkTestTask
TaskID - 323
TaskRunID - 488
Target - testec-8e23e639/com.sun.hss.domain:name=localhost,type=OperatingSystem
JobIDrunID - testec.79.1
RebootPolicy - DEFAULT_REBOOT_POLICY
TimeOut - 180
Jan 17, 2013 2:30:58 PM com.sun.hss.services.proxyservice.impl.tasks.NetworkTestTask testConnectivitySolaris
INFO: thr#450:"JM-testec.79.1.323.488_testec-8e23e639/com.sun.hss.domain:name=localhost,type=OperatingSystem" Exception checking for the reachability of IP address X.X.X.0
com.sun.cacao.invocation.InvocationException: Non-zero exit status
at com.sun.hss.domain.util.spawn.Spawn.execute(Spawn.java:1070)
at com.sun.hss.domain.util.spawn.Spawn.execute(Spawn.java:961)
at com.sun.hss.domain.util.spawn.Spawn.execute(Spawn.java:891)
at com.sun.hss.services.proxyservice.impl.tasks.NetworkTestTask.testConnectivitySolaris(NetworkTestTask.java:183)
at com.sun.hss.services.proxyservice.impl.tasks.NetworkTestTask.run(NetworkTestTask.java:110)
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:597)
at com.sun.scn.jobmanager.common.impl.TaskExecutionThread.run(TaskExecutionThread.java:197)
Jan 17, 2013 2:30:58 PM com.sun.hss.services.proxyservice.impl.tasks.NetworkTestTask run
INFO: thr#450:"JM-testec.79.1.323.488_testec-8e23e639/com.sun.hss.domain:name=localhost,type=OperatingSystem" PRXYMGR Failed to test connectivity to IP address X.X.X.0
Jan 17, 2013 2:30:58 PM com.sun.scn.jobmanager.common.impl.TaskExecutionThread finishTask
INFO: thr#450:"JM-testec.79.1.323.488_testec-8e23e639/com.sun.hss.domain:name=localhost,type=OperatingSystem" ************* End Of Task - NetworkTestTask
TaskID - 323
TaskRunID - 488
Target - testec-8e23e639/com.sun.hss.domain:name=localhost,type=OperatingSystem
JobIDrunID - testec.79.1
Status - FAILED
Result - proxyManager$@!81136$@!X.X.X.0
CauseCode - null


Has anyone come across this?

thanks,

Alan
  • 1. Re: Unable to associate network - Failed to determine the network address reach
    user12617625 Explorer
    Currently Being Moderated
    I take it the network is a 192.168.x.x...this is a known issue, not sure exactly if it is Solaris or OC but the cruxt of the issue is you can't do a "route get <network>" from the proxy. The script included here should fix it, and I think once the network is associated to the proxy, you don't have to worry about it again. If there is a different 192.168 network later you will need to do the same thing.

    cat add_network

    #!/bin/ksh

    ip=`getent hosts $1 | cut -f1`

    network=${ip%.*}.0
    echo "checking $network,..."

    ping $network 5
    if [ $? = 1 ] ; then
    echo "$network is not accessable, exiting..."
    exit 1
    fi

    default_route=`cat /etc/defaultrouter`

    getent netmasks $network
    if [ $? = 2 ] ; then
    echo adding entry $network to /etc/netmasks
    set -x
    print "$network\t255.255.255.0" >> /etc/netmasks
    set +x
    fi

    route get $network
    if [ $? = 3 ] ; then
    echo adding $network to routing table
    set -x
    route -p add $network $default_route 255.255.255.0
    set +x
    fi
  • 2. Re: Unable to associate network - Failed to determine the network address reach
    AlanGarde Newbie
    Currently Being Moderated
    Thankyou!

    Yes, thats it, they are 192.168.X.X networks. I had almost got it right.

    I had suspected the routing table so I had added a route to 192.168.X.X/23 via the defaultrouter and added it to netmasks (our networks are supernetted) but it hadn't worked.

    It seems to be very specific to it needing a route to the /24 part of the network instead so I suspect OC is performing a

    route get 192.168.X.X

    rather than

    route get 192.168.X.X/23

    The former fails when I only had my /23 route, whereas the latter had worked. With a /24 route the former works and OC associates the network.

    I'll raise an SR just to ensure it gets tacked onto the buglist (if it's not already) as that to me looks like a bug (with OC ignoring the netmask defined in OC and Solaris).

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points