[ietf85-tech] Billo: netdisco question
Bjoern A. Zeeb
bzeeb-lists at lists.zabbadoz.net
Sat Nov 3 11:57:07 PDT 2012
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?
Thanks,
/bz
--
Bjoern A. Zeeb You have to have visions!
Stop bit received. Insert coin for new address family.
More information about the ietf85-tech
mailing list