| Benoit,
Ok so I registered it and still get the same results. My real question
is; where the hell is it picking up this entity? If I can show snmp xyz
and get info, why can't I deregister, where is MCC picking up the reference
to this entity ??????
I registered it under a different name, still the same results. I am trying
to get the customer to change the address and register it again, I will have
to wait for him to do this.
Meanwhile I have secured SNMP responses from both the rogue and good devices.
I have broken down the first response of the suspect device and found that
to be good, it is interesting to note that this device is asked twice for
each SNMP response, the good device only once.
I think that the "show snmp central_c all attr" problem is caused by the timeticks
"stamping over" the sysDescr field, as all other fields are shifted down one.
Also the sysDescr field, although garbage, is differing garbage with each show.
First trace, suspect device.
Ethernet packet received at 31-MAY-1995 14:44:54.03 ( 0usec.)
Destination address Source address Protocol type
AA-00-04-00-FC-B5 08-00-90-20-27-75 08-00
NSWWVC CENTRAL_C TCP
Protocol = ARPA_INTERNET, Message type = IP_DATAGRAM
IP_HEADER :
VERSION : 4
IHL : 5
SERVICE_TYPE : 0
TOTAL_LENGTH : 121
IDENTIFICATION : 32153
FRAGMENT_FLAGS : 00 = "Last Fragment", "May Fragment"
FRAGMENT_OFFSET : 0
TIME_TO_LIVE : 16
PROTOCOL : 17
HEADER_CHECKSUM : 9E68
SOURCE_ADDR : 93 45 4 243
DEST_ADDR : 93 45 4 240
NEXT_PROTOCOL :
Protocol = UDP, Message type = UDP_MESSAGE
UDP_DATAGRAM :
SOURCE_PORT : 161
DEST_PORT : 1337
LENGTH : 101
CHECKSUM : 46F5
NEXT_PROTOCOL :
SELECT_OTHER :
30 5B SNMP data sequence length 91d
02 01 00 Integer len 1 version = 0
04 06 70 75 62 6C 69 63 String len 6 community = public
A2 4E Response PDU len 78d
02 01 01 Int. len 1 req. id 1
02 01 00 Int. len 1 error 0
02 01 00 Int. len 1 error index 0
30 43 Sequence of pairs len 67d
30 10 Sequence len 16d
06 08 Object, len 8
2B 06 01 02 01 01 03 00 1.3.6.1.2.1.1.3
43 04 Timeticks len 4
1B 4B 71 58 timeticks
30 18 Sequence len 24d
06 08 Object, len 8
2B 06 01 02 01 01 01 00 1.3.6.1.2.1.1.1
04 0C String len 12d
52 65 74 69 78 20 52 58 37 35 30 30 Retix RX7500
30 15 Sequence len 21d
06 08 Object len 8
2B 06 01 02 01 01 02 00 1.3.6.1.2.1.1.2
06 09 Object len 9
2B 06 01 04 01 48 0E 11 02
1.3.6.1.4.1.72.14.17.2
Ethernet packet received at 31-MAY-1995 14:44:54.04 ( 0usec.)
Destination address Source address Protocol type
AA-00-04-00-FC-B5 08-00-90-20-27-75 08-00
NSWWVC CENTRAL_C TCP
Protocol = ARPA_INTERNET, Message type = IP_DATAGRAM
IP_HEADER :
VERSION : 4
IHL : 5
SERVICE_TYPE : 0
TOTAL_LENGTH : 121
IDENTIFICATION : 32154
FRAGMENT_FLAGS : 00 = "Last Fragment", "May Fragment"
FRAGMENT_OFFSET : 0
TIME_TO_LIVE : 16
PROTOCOL : 17
HEADER_CHECKSUM : 9D68
SOURCE_ADDR : 93 45 4 243
DEST_ADDR : 93 45 4 240
NEXT_PROTOCOL :
Protocol = UDP, Message type = UDP_MESSAGE
UDP_DATAGRAM :
SOURCE_PORT : 161
DEST_PORT : 1337
LENGTH : 101
CHECKSUM : 45F5
NEXT_PROTOCOL :
SELECT_OTHER : 30 5B 02 01 00 04 06 70 75 62 6C 69 63 A2 0[.....public�
4E 02 01 01 02 01 00 02 01 00 30 43 30 10 N.........0C0.
06 08 2B 06 01 02 01 01 03 00 43 04 1B 4B ..+.......C..K
71 59 30 18 06 08 2B 06 01 02 01 01 01 00 qY0...+.......
04 0C 52 65 74 69 78 20 52 58 37 35 30 30 ..Retix RX7500
30 15 06 08 2B 06 01 02 01 01 02 00 06 09 0...+.........
2B 06 01 04 01 48 0E 11 02 +....H...
Ethernet packet received at 31-MAY-1995 14:44:54.04 ( 0usec.)
Destination address Source address Protocol type
AA-00-04-00-FC-B5 08-00-90-20-27-75 08-00
NSWWVC CENTRAL_C TCP
Protocol = ARPA_INTERNET, Message type = IP_DATAGRAM
IP_HEADER :
VERSION : 4
IHL : 5
SERVICE_TYPE : 0
TOTAL_LENGTH : 121
IDENTIFICATION : 32155
FRAGMENT_FLAGS : 00 = "Last Fragment", "May Fragment"
FRAGMENT_OFFSET : 0
TIME_TO_LIVE : 16
PROTOCOL : 17
HEADER_CHECKSUM : 9C68
SOURCE_ADDR : 93 45 4 243
DEST_ADDR : 93 45 4 240
NEXT_PROTOCOL :
Protocol = UDP, Message type = UDP_MESSAGE
UDP_DATAGRAM :
SOURCE_PORT : 161
DEST_PORT : 1337
LENGTH : 101
CHECKSUM : 45F5
NEXT_PROTOCOL :
SELECT_OTHER : 30 5B 02 01 00 04 06 70 75 62 6C 69 63 A2 0[.....public�
4E 02 01 01 02 01 00 02 01 00 30 43 30 10 N.........0C0.
06 08 2B 06 01 02 01 01 03 00 43 04 1B 4B ..+.......C..K
71 59 30 18 06 08 2B 06 01 02 01 01 01 00 qY0...+.......
04 0C 52 65 74 69 78 20 52 58 37 35 30 30 ..Retix RX7500
30 15 06 08 2B 06 01 02 01 01 02 00 06 09 0...+.........
2B 06 01 04 01 48 0E 11 02 +....H...
Ethernet packet received at 31-MAY-1995 14:44:54.05 ( 0usec.)
Destination address Source address Protocol type
AA-00-04-00-FC-B5 08-00-90-20-27-75 08-00
NSWWVC CENTRAL_C TCP
Protocol = ARPA_INTERNET, Message type = IP_DATAGRAM
IP_HEADER :
VERSION : 4
IHL : 5
SERVICE_TYPE : 0
TOTAL_LENGTH : 207
IDENTIFICATION : 32156
FRAGMENT_FLAGS : 00 = "Last Fragment", "May Fragment"
FRAGMENT_OFFSET : 0
TIME_TO_LIVE : 16
PROTOCOL : 17
HEADER_CHECKSUM : 4568
SOURCE_ADDR : 93 45 4 243
DEST_ADDR : 93 45 4 240
NEXT_PROTOCOL :
Protocol = UDP, Message type = UDP_MESSAGE
UDP_DATAGRAM :
SOURCE_PORT : 161
DEST_PORT : 1337
LENGTH : 187
CHECKSUM : 46C3
NEXT_PROTOCOL :
SELECT_OTHER : 30 81 B0 02 01 00 04 06 70 75 62 6C 69 63 0.�.....public
A2 81 A2 02 01 02 02 01 00 02 01 00 30 81 �.�.........0.
96 30 18 06 08 2B 06 01 02 01 01 01 00 04 .0...+........
0C 52 65 74 69 78 20 52 58 37 35 30 30 30 .Retix RX75000
15 06 08 2B 06 01 02 01 01 02 00 06 09 2B ...+.........+
06 01 04 01 48 0E 11 02 30 0D 06 08 2B 06 ....H...0...+.
01 02 01 02 01 00 02 01 0C 30 0D 06 08 2B .........0...+
06 01 02 01 01 04 00 04 01 20 30 15 06 08 ......... 0...
2B 06 01 02 01 01 05 00 04 09 43 45 4E 54 +.........CENT
52 41 4C 5F 43 30 1F 06 08 2B 06 01 02 01 RAL_C0...+....
01 06 00 04 13 57 49 44 43 4F 4D 42 45 20 .....WIDCOMBE
52 41 44 49 4F 20 52 4F 4F 4D 30 0D 06 08 RADIO ROOM0...
2B 06 01 02 01 01 07 00 02 01 04 +..........
Ethernet packet received at 31-MAY-1995 14:44:54.06 ( 0usec.)
Destination address Source address Protocol type
AA-00-04-00-FC-B5 08-00-90-20-27-75 08-00
NSWWVC CENTRAL_C TCP
Protocol = ARPA_INTERNET, Message type = IP_DATAGRAM
IP_HEADER :
VERSION : 4
IHL : 5
SERVICE_TYPE : 0
TOTAL_LENGTH : 207
IDENTIFICATION : 32157
FRAGMENT_FLAGS : 00 = "Last Fragment", "May Fragment"
FRAGMENT_OFFSET : 0
TIME_TO_LIVE : 16
PROTOCOL : 17
HEADER_CHECKSUM : 4468
SOURCE_ADDR : 93 45 4 243
DEST_ADDR : 93 45 4 240
NEXT_PROTOCOL :
Protocol = UDP, Message type = UDP_MESSAGE
UDP_DATAGRAM :
SOURCE_PORT : 161
DEST_PORT : 1337
LENGTH : 187
CHECKSUM : 46C3
NEXT_PROTOCOL :
SELECT_OTHER : 30 81 B0 02 01 00 04 06 70 75 62 6C 69 63 0.�.....public
A2 81 A2 02 01 02 02 01 00 02 01 00 30 81 �.�.........0.
96 30 18 06 08 2B 06 01 02 01 01 01 00 04 .0...+........
0C 52 65 74 69 78 20 52 58 37 35 30 30 30 .Retix RX75000
15 06 08 2B 06 01 02 01 01 02 00 06 09 2B ...+.........+
06 01 04 01 48 0E 11 02 30 0D 06 08 2B 06 ....H...0...+.
01 02 01 02 01 00 02 01 0C 30 0D 06 08 2B .........0...+
06 01 02 01 01 04 00 04 01 20 30 15 06 08 ......... 0...
2B 06 01 02 01 01 05 00 04 09 43 45 4E 54 +.........CENT
52 41 4C 5F 43 30 1F 06 08 2B 06 01 02 01 RAL_C0...+....
01 06 00 04 13 57 49 44 43 4F 4D 42 45 20 .....WIDCOMBE
52 41 44 49 4F 20 52 4F 4F 4D 30 0D 06 08 RADIO ROOM0...
2B 06 01 02 01 01 07 00 02 01 04 +..........
Ethernet packet received at 31-MAY-1995 14:44:54.08 ( 0usec.)
Destination address Source address Protocol type
AA-00-04-00-FC-B5 08-00-90-20-27-75 08-00
NSWWVC CENTRAL_C TCP
Protocol = ARPA_INTERNET, Message type = IP_DATAGRAM
IP_HEADER :
VERSION : 4
IHL : 5
SERVICE_TYPE : 0
TOTAL_LENGTH : 207
IDENTIFICATION : 32158
FRAGMENT_FLAGS : 00 = "Last Fragment", "May Fragment"
FRAGMENT_OFFSET : 0
TIME_TO_LIVE : 16
PROTOCOL : 17
HEADER_CHECKSUM : 4368
SOURCE_ADDR : 93 45 4 243
DEST_ADDR : 93 45 4 240
NEXT_PROTOCOL :
Protocol = UDP, Message type = UDP_MESSAGE
UDP_DATAGRAM :
SOURCE_PORT : 161
DEST_PORT : 1337
LENGTH : 187
CHECKSUM : 46C3
NEXT_PROTOCOL :
SELECT_OTHER : 30 81 B0 02 01 00 04 06 70 75 62 6C 69 63 0.�.....public
A2 81 A2 02 01 02 02 01 00 02 01 00 30 81 �.�.........0.
96 30 18 06 08 2B 06 01 02 01 01 01 00 04 .0...+........
0C 52 65 74 69 78 20 52 58 37 35 30 30 30 .Retix RX75000
15 06 08 2B 06 01 02 01 01 02 00 06 09 2B ...+.........+
06 01 04 01 48 0E 11 02 30 0D 06 08 2B 06 ....H...0...+.
01 02 01 02 01 00 02 01 0C 30 0D 06 08 2B .........0...+
06 01 02 01 01 04 00 04 01 20 30 15 06 08 ......... 0...
2B 06 01 02 01 01 05 00 04 09 43 45 4E 54 +.........CENT
52 41 4C 5F 43 30 1F 06 08 2B 06 01 02 01 RAL_C0...+....
01 06 00 04 13 57 49 44 43 4F 4D 42 45 20 .....WIDCOMBE
52 41 44 49 4F 20 52 4F 4F 4D 30 0D 06 08 RADIO ROOM0...
2B 06 01 02 01 01 07 00 02 01 04 +..........
******************************************************************************************
Good device
******************************************************************************************
Ethernet packet received at 31-MAY-1995 14:51:39.54 ( 0usec.)
Destination address Source address Protocol type
AA-00-04-00-FC-B5 08-00-90-20-35-C0 08-00
NSWWVC CENTRAL_D TCP
Protocol = ARPA_INTERNET, Message type = IP_DATAGRAM
IP_HEADER :
VERSION : 4
IHL : 5
SERVICE_TYPE : 0
TOTAL_LENGTH : 121
IDENTIFICATION : 3549
FRAGMENT_FLAGS : 00 = "Last Fragment", "May Fragment"
FRAGMENT_OFFSET : 0
TIME_TO_LIVE : 16
PROTOCOL : 17
HEADER_CHECKSUM : 59D8
SOURCE_ADDR : 93 45 4 244
DEST_ADDR : 93 45 4 240
NEXT_PROTOCOL :
Protocol = UDP, Message type = UDP_MESSAGE
UDP_DATAGRAM :
SOURCE_PORT : 161
DEST_PORT : 1754
LENGTH : 101
CHECKSUM : 1B01
NEXT_PROTOCOL :
SELECT_OTHER : 30 5B 02 01 00 04 06 70 75 62 6C 69 63 A2 0[.....public�
4E 02 01 01 02 01 00 02 01 00 30 43 30 10 N.........0C0.
06 08 2B 06 01 02 01 01 03 00 43 04 24 F1 ..+.......C.$�
5A 3C 30 18 06 08 2B 06 01 02 01 01 01 00 Z<0...+.......
04 0C 52 65 74 69 78 20 52 58 37 35 30 30 ..Retix RX7500
30 15 06 08 2B 06 01 02 01 01 02 00 06 09 0...+.........
2B 06 01 04 01 48 0E 11 02 +....H...
Ethernet packet received at 31-MAY-1995 14:51:39.56 ( 0usec.)
Destination address Source address Protocol type
AA-00-04-00-FC-B5 08-00-90-20-35-C0 08-00
NSWWVC CENTRAL_D TCP
Protocol = ARPA_INTERNET, Message type = IP_DATAGRAM
IP_HEADER :
VERSION : 4
IHL : 5
SERVICE_TYPE : 0
TOTAL_LENGTH : 207
IDENTIFICATION : 3550
FRAGMENT_FLAGS : 00 = "Last Fragment", "May Fragment"
FRAGMENT_OFFSET : 0
TIME_TO_LIVE : 16
PROTOCOL : 17
HEADER_CHECKSUM : 02D8
SOURCE_ADDR : 93 45 4 244
DEST_ADDR : 93 45 4 240
NEXT_PROTOCOL :
Protocol = UDP, Message type = UDP_MESSAGE
UDP_DATAGRAM :
SOURCE_PORT : 161
DEST_PORT : 1754
LENGTH : 187
CHECKSUM : A4C6
NEXT_PROTOCOL :
SELECT_OTHER : 30 81 B0 02 01 00 04 06 70 75 62 6C 69 63 0.�.....public
A2 81 A2 02 01 02 02 01 00 02 01 00 30 81 �.�.........0.
96 30 18 06 08 2B 06 01 02 01 01 01 00 04 .0...+........
0C 52 65 74 69 78 20 52 58 37 35 30 30 30 .Retix RX75000
15 06 08 2B 06 01 02 01 01 02 00 06 09 2B ...+.........+
06 01 04 01 48 0E 11 02 30 0D 06 08 2B 06 ....H...0...+.
01 02 01 02 01 00 02 01 06 30 0D 06 08 2B .........0...+
06 01 02 01 01 04 00 04 01 20 30 15 06 08 ......... 0...
2B 06 01 02 01 01 05 00 04 09 43 45 4E 54 +.........CENT
52 41 4C 5F 44 30 1F 06 08 2B 06 01 02 01 RAL_D0...+....
01 06 00 04 13 57 49 44 43 4F 4D 42 45 20 .....WIDCOMBE
52 41 44 49 4F 20 52 4F 4F 4D 30 0D 06 08 RADIO ROOM0...
2B 06 01 02 01 01 07 00 02 01 04 +..........
|
| Neal,
> where the hell is it picking up this entity?
try a "show snmp 93.45.4.243"
You may get information for central_c.
>I have broken down the first response of the suspect device and found that
>to be good, it is interesting to note that this device is asked twice for
>each SNMP response, the good device only once.
I think you have found the problem.
If the device is slow, TCPIP_AM UDP timeout expires and there is a retry.
You can try to increase the UDP timeout ( this attribute is in mcc 0 tcpip_am
entity) to avoid retries and check what happens.
Are you running on ULTRIX or VMS ?
Just for my information, how did you get the traces ?
Benoit
|
| Benoit,
The system is VMS.
I will try to get access to the system to try what you have
asked with the IP address.
What you have said about the retransmission may hold water as
the show does *occassionally* work. If indeed this is due to
a timeout, is this not an obsure bug in either MCC or UCX ?
I am getting the customer to upgrade both anyway.
I will try increasing the UDP timeout.
The analyzer program was written, and is maintained by our
networks consultant, John Weir, here at the UK CSC.
Mail him on COMICS::WEIR
The SNMP data was painstakingly decoded by me !!
Neal
|
| Benoit,
No it responds within a couple of seconds, my reasoning behind increasing the
timeout to 60 seconds and retries to one was to make sure that there was no way
MCC could've thought that the device had not responded, even if it thought that,
I wanted to make sure MCC would not retry. I have not been able to take a trace
to see whether we are seeing two responses.
Neal
|