« Back
You are in :
Recent Topics »
Test Automation »
Simulation Toolkit » Connected devices from Routers are not discovered
Dear Pankaj,
I believe you are using the SNMP v3 queries to discover the devices connected to a router. Since there is a problem with the SNMP v3 discovery with a single device, (which is going in another post), we can see this problem after that problem is resolved. Kindly get back if you are NOT using SNMP v3 queries for discovering devices connected to a router.
Thanks,
Mani.
I believe you are using the SNMP v3 queries to discover the devices connected to a router. Since there is a problem with the SNMP v3 discovery with a single device, (which is going in another post), we can see this problem after that problem is resolved. Kindly get back if you are NOT using SNMP v3 queries for discovering devices connected to a router.
Thanks,
Mani.
Hi Mani
I am using SNMPv1 devices all interconnected (R1-R2-R3)with each other but during discovery the connection gets displayed between R1-R3 and R2 does not discover.
Please provide an update.
Thanks
Pankaj
I am using SNMPv1 devices all interconnected (R1-R2-R3)with each other but during discovery the connection gets displayed between R1-R3 and R2 does not discover.
Please provide an update.
Thanks
Pankaj
Dear Pankaj,
As before, please start the Network in DEBUG mode and send us the debug log file. Also send the packet capture of the packet transaction while the discovery process is going on. This will help us to identify the exact problem.
Thanks,
Mani.
As before, please start the Network in DEBUG mode and send us the debug log file. Also send the packet capture of the packet transaction while the discovery process is going on. This will help us to identify the exact problem.
Thanks,
Mani.
Hi Mani
We are just preparing the same kind of network and will be get back to you in a day or two.
Thanks
Pankaj
We are just preparing the same kind of network and will be get back to you in a day or two.
Thanks
Pankaj
Hi Mani
Please find the attached Network log in DEBUG mode, along with the packet captured file and the packaged topology network which we are using for discovery.
Please note that in the topology network, we were not able to discover any of the Router. The latest patch applied over the Simulation Toolkit is 'AdventNet_Simulation_Toolkit_6_0_SP-5_92.ppm'. We are running our Simulation Toolkit over RHEL ES machine.
Please revert
Thanks
Pankaj
Please find the attached Network log in DEBUG mode, along with the packet captured file and the packaged topology network which we are using for discovery.
Please note that in the topology network, we were not able to discover any of the Router. The latest patch applied over the Simulation Toolkit is 'AdventNet_Simulation_Toolkit_6_0_SP-5_92.ppm'. We are running our Simulation Toolkit over RHEL ES machine.
Please revert
Thanks
Pankaj
Hi Pankaj,
During GetBulk operation on ipAdEntAddr node of ipAddrTable there is request time out and the cpu usage is high. We are analyzing the issue will get back to you at the earliest.
Thanks
Muthu
During GetBulk operation on ipAdEntAddr node of ipAddrTable there is request time out and the cpu usage is high. We are analyzing the issue will get back to you at the earliest.
Thanks
Muthu
Hi Pankaj,
Issue is while performing the GetBulk operation on ipRouteTable. For an temporary work around, insert a row in ipRouteTable and try to discover the routers. we will provide the patch for the issue at the earliest.
Thanks
Muthu
Issue is while performing the GetBulk operation on ipRouteTable. For an temporary work around, insert a row in ipRouteTable and try to discover the routers. we will provide the patch for the issue at the earliest.
Thanks
Muthu
Hi Pankaj,
Issue is while performing the GetBulk operation on ipRouteTable which is empty. For an temporary work around, insert a row in ipRouteTable and discover the routers. we will provide the patch for the issue at the earliest.
Thanks
Muthu
Issue is while performing the GetBulk operation on ipRouteTable which is empty. For an temporary work around, insert a row in ipRouteTable and discover the routers. we will provide the patch for the issue at the earliest.
Thanks
Muthu
Hi Muthu
Sorry for the delayed response.
After adding routes in the ipRouteTable of all the three Routers (192.168.10.1, 192.168.10.2, 192.168.10.3), we again performed discovery by providing the 192.168.10.1 IP Address as seed Address. Following was the observation after discovery completed:
1. This time R1 and R3 got discovered (Previously only R1 was getting discovered due to no entry in the ipRouteTable).
2. R2 does not discover.
3. Another IP Address got discovered (192.168.10.9) which is not there in the virtual network and neither we added this IP Address on the host (RHEL ES 5 machine) where we are simulating our virtual network.
Again the link between R1-R3 is shown after discovering the virtual network.
We are attaching the packet capture file and the network log created in DEBUG mode. The zipped file name is 'Router_Network.zip' containing both files.
Please revert.
Thanks
Pankaj
Sorry for the delayed response.
After adding routes in the ipRouteTable of all the three Routers (192.168.10.1, 192.168.10.2, 192.168.10.3), we again performed discovery by providing the 192.168.10.1 IP Address as seed Address. Following was the observation after discovery completed:
1. This time R1 and R3 got discovered (Previously only R1 was getting discovered due to no entry in the ipRouteTable).
2. R2 does not discover.
3. Another IP Address got discovered (192.168.10.9) which is not there in the virtual network and neither we added this IP Address on the host (RHEL ES 5 machine) where we are simulating our virtual network.
Again the link between R1-R3 is shown after discovering the virtual network.
We are attaching the packet capture file and the network log created in DEBUG mode. The zipped file name is 'Router_Network.zip' containing both files.
Please revert.
Thanks
Pankaj
Post Actions
Corp