[cricket-users] Problem with size of UDP packets sent by cricket

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Hi all,

        I have configured 71 OID's in my defaults file for OTA netwrok 
element.  When cricket tries to retrieve data from the destination device it 
gets no response.

Eg: output [30-Nov-2005 17:00:33*] No response from "10.14.4.69" 
[10.14.4.69].portnumber

But when i give a manual snmpwalk it works:

Eg: snmpwalk -v1 -c community name 10.14.4.69:portnumber OID

To analyse the behaviour i monitored the Network for Packet Analysis using 
snoop.

the snoop output while running cricket is like this

  minmsmodel -> 10.14.4.69   UDP D=3162 S=34093 LEN=1381
  minmsmodel -> 10.14.4.69   UDP D=3162 S=34093 LEN=1381
  minmsmodel -> 10.14.4.69   UDP D=3162 S=34093 LEN=1381
  minmsmodel -> 10.14.4.69   UDP D=3162 S=34093 LEN=1381
  minmsmodel -> 10.14.4.69   UDP D=3162 S=34093 LEN=1381

But the snoop output for a single snmpwalk is like

  minmsmodel -> 10.14.4.69   UDP D=3162 S=34071 LEN=56
  10.14.4.69 -> minmsmodel   UDP D=34071 S=3162 LEN=58
  minmsmodel -> 10.14.4.69   UDP D=3162 S=34071 LEN=57
  10.14.4.69 -> minmsmodel   UDP D=34071 S=3162 LEN=59

From both the snoop outputs i see that there is a huge difference is in the 
LEN of the UDP packets.
The size of the UDP packets sent by cricket and a single snmpwalk is 
different. This i believe is mainly because cricket is sending only one UDP 
packet containing all the snmpwalk request for all configured OID's of a 
destination device.

NOW COMING TO THE PROBLEM

My Destination device is not responding for such a large UDP packet... I 
believe it is not parsing through the packet to retrieve and respond for all 
the queries. (Destination device is not under my control, so i cannot do any 
tweaks with this device)

Now I am looking for an workaround to overcome this problem. Is there a way 
in cricket to send only 1 OID at a time (Even if many have been configured) 
to a destination device instead of sending all the OID's at one go (As it is 
now).

I need to know which perl script of cricket can do this magic for me... The 
perl script that collects the OID's and issues a request to the destination 
device. I can know where exactly in the script this is being done, then i 
want to if i can parse the OID and send it one by one. I am not sure about 
the probability of success in this case...

Please let me know if there could be some other work around for this 
problem.

Thanks in advance