[ietf85-tech] Billo: netdisco question

[Bill Fenner]

I've never seen this behavior before. I agree that it's probably the chassis ID. If the MIB is reporting the chassis ID still, then I don't know what to do. If the MIB is reporting the right thing and netdisco is not finding it, then this is probably the problem that bz pointed out yesterday that "netdisco -r" isn't seeming to work, while "netdisco -R" is. The whole system is built around the idea that "netdisco -r" will work, so I recommend debugging that (e.g., looking at the logs).

  Bill


On Nov 3, 2012, at 4:55 PM, "Bjoern A. Zeeb" <bzeeb-lists at lists.zabbadoz.net> wrote:

> On Sat, 3 Nov 2012, Bjoern A. Zeeb wrote:
> 
>> Hi Billo,
>> 
>> do you have an idea how a mac address can get into remote_id and not be fixed automatically?
>> 
>> netdisco=> SELECT ip,port,creation,descr,up,up_admin,type,duplex,speed,name,mac,mtu,stp,remote_ip,remote_port,remote_id,vlan,pvid,lastchange FROM public.device_port WHERE ip='130.129.1.30' AND remote_id='00:1e:f7:e8:35:00';
>>     ip      |        port         |         creation          |        descr        | up | up_admin |      type       | duplex |  speed   |  name  |        mac        | mtu  |    stp     |  remote_ip   |    remote_port     |     remote_id     | vlan | pvid | lastchange
>> --------------+---------------------+---------------------------+---------------------+----+----------+-----------------+--------+----------+--------+-------------------+------+------------+--------------+--------------------+-------------------+------+------+------------
>> 130.129.1.30 | GigabitEthernet0/10 | 2012-11-03 18:48:55.55141 | GigabitEthernet0/10 | up | up       | ethernet-csmacd | full   | 1.0 Gbps | Gi0/10 | 5c:50:15:75:53:8a | 1500 | forwarding | 130.129.1.25 | GigabitEthernet0/1 | 00:1e:f7:e8:35:00 | 1    |    1 |    8287830
>> 
>> 
>> 
>> CDP seems to know the corrrect data.  It only seems to happen on exactly that one port and of course that is the uplink of the sw-noc to SW-IDF3 which elsewhere is all right.
>> 
>> What's the best way to get this fixed?
> 
> So it seems it was the chassis ID of the neighbour but i am not sure
> why it never updated it to the hostname.
> 
> Anyway for now I did a
> -------
> BEGIN;
> UPDATE public.device_port SET remote_id='SW-IDF3.meeting.ietf.org' WHERE ip='130.129.1.30' AND remote_id='00:1e:f7:e8:35:00';
> SELECT ip,remote_ip,remote_id FROM public.device_port WHERE remote_id is NOT NULL and ip='130.129.1.30';
> COMMIT;
> -------
> 
> to not accidentally kick the NOC off the DHCP and RA again tonight.
> Still interested in a proper fix w/o deleting and rediscovering the device from netdisco.
> 
> /bz
> 
> -- 
> Bjoern A. Zeeb                                 You have to have visions!
>         Stop bit received. Insert coin for new address family.