BMC Communities Banner
Previous Next Up to Discussions in Discovery

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (5 pts)
3 Replies Last post: Nov 5, 2009 12:53 AM by Petrus Johansson  
kramecm Participant
kramecm
9 posts since
May 18, 2007
Currently Being Moderated

Nov 3, 2009 12:59 PM

Network object creation fails - invalid network mask

I am running scans against test network devices in a closed lab.  The task monitor shows everything running smoothly until Network Creation.  At that point, the task monitor indicates an error and the scan stops.  The only logs in the service log that captures any information is the service.network.log (service.network.trace is not turned on nor are the snmp logs).  The message in the log is the following:

.

Error during the network creation process
com.bmc.td.network.builder.NetworkException: Error occured during network objects creation
     at com.bmc.td.network.builder.impl.NetworkBuilder.getNetworkInstances(NetworkBuilder.java:76)
     at com.bmc.td.network.builder.impl.NetworkProcessor.execute(NetworkProcessor.java:42)
     at com.bmc.td.util.taskdispatcher.TaskProcessThread.run(TaskProcessThread.java:82)
Caused by: java.lang.IllegalArgumentException: 255.25.254.0 is not a valid network mask
     at com.bmc.td.dm.core.common.address.IpNetworkAddress.setMask(IpNetworkAddress.java:80)
     at com.bmc.td.dm.core.common.address.IpNetworkAddress.(IpNetworkAddress.java:23)
     at com.bmc.td.network.builder.impl.NetworkBuilder.getSubnet(NetworkBuilder.java:317)
     at com.bmc.td.network.builder.impl.NetworkBuilder.associateDevicesToSubnets(NetworkBuilder.java:235)
     at com.bmc.td.network.builder.impl.NetworkBuilder.getNetworkInstances(NetworkBuilder.java:72)
     ... 2 more
.
Obviously the 255.25.254.0 is not a valid mask, but my question is where is it coming from?  The network guy I am working with insists that this can't 
be coming from the targeted network device.  Also, where can I find documentation to help me turn on additional logs to perhaps capture more 
information that can lead me to a cause?

.

I am currently running TD 1.6 patch 2.  We have been able to successfully scan other network devices with no problems.

Petrus Johansson HotShot
Petrus Johansson
273 posts since
Sep 30, 2008
Currently Being Moderated
1. Nov 4, 2009 1:44 AM in response to: kramecm
Re: Network object creation fails - invalid network mask

My belief is that is comes from one or some of the devices discovered...

Chances are that the device is registred in the Discovery datastore, so query the datastore, look at it´s CI attributes. Somewhere in the datastore a device with 255.25.254.0 as subnet mask probably exists and this errors when you resolve the network topology during this task.

Report Abuse
kramecm Participant
kramecm
9 posts since
May 18, 2007
Currently Being Moderated
2. Nov 4, 2009 1:16 PM in response to: Petrus Johansson
Re: Network object creation fails - invalid network mask

Thanks for the information, Petrus, but neither of the network devices in this scan had the invalid subnet mask in its datastore properties or in any of the related CI's.

 

I also noticed that the copy of the log has covered some of the questions, so I will repeat them here.

 

The envrionment for these network devices (Cisco catalyst 6513 Switches) is a closed lab.  The network analyst I am working with insists the subnet mask tied to these devices is correct, and not the one listed in the error (255.25.254.0).  I am wondering if anyone knows where on the devices this could be coming from.  I am also wondering if there is any specific log file I should activate to capture any information that may be useful to figuring out this problem.

Report Abuse
Petrus Johansson HotShot
Petrus Johansson
273 posts since
Sep 30, 2008
Currently Being Moderated
3. Nov 5, 2009 12:53 AM in response to: kramecm
Re: Network object creation fails - invalid network mask

For enabling/disabling of logs and traces, go to http://<td_server>:8080/visualis/log/admin/index.jsp

In your case, look at enabling service.network.trace since it is during the network creation phase you see the error. Choose "State On" for this trace under domain:perform:host:manager:vm:manager. (Don´t forget to reset and disable the trace when you are done later)

This would give you more input to what´s causing the error...

 

I still believe that it is not coming from any of the devices you are discovering in this discovery task.

What other devices do you have in your datastore? Have you Discovered any other devices (computers, printers, servers etc) on this isolated network in another discovery task? If so, take a look at those devices ip subnet mask as well. During the network creation phase Discovery is trying to build the network for the targeted devices and relate the existing devices in the datastore to the network subnet or equal... If any of those devices, servers, computers in the datastore has a false attribute of ip subnet, you will then see this error...

Report Abuse

More Like This

  • Retrieving data ...