Alcatel Unleashed

I have found that errors.

I wonder why this error occurred

1/15 interface is myic phone ... current DHCP being used ..

What should I do???????????????


TUE FEB 18 04:11:35 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 04:11:36 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 04:11:37 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 04:11:39 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 04:11:40 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 04:11:46 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 04:11:47 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 04:11:48 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 04:11:50 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 04:11:50 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 04:11:51 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 04:11:53 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 04:11:54 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 04:11:55 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 04:11:56 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 04:11:58 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 04:11:59 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 04:12:00 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 04:12:01 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 04:12:02 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 04:12:05 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 04:13:45 2014 LLDP warning lldpProcessNetPolicyTLV: Error, Net Policy VLAN ID 4095 invalid/reserved
TUE FEB 18 05:30:23 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:30:24 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:30:24 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:30:29 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:30:32 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:30:34 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:30:34 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:30:37 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:30:39 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:30:39 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:30:41 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:30:42 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:30:44 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:30:53 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:30:54 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:30:55 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:30:56 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:30:58 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:30:59 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:30:59 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:31:01 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:31:04 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:31:05 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:31:07 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:31:08 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:31:09 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:31:09 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:31:14 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:31:19 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:31:21 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:31:24 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:31:27 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:31:29 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:31:29 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:31:34 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:31:58 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:31:59 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:31:59 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:32:03 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:32:04 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:32:05 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:32:09 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:32:11 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:32:12 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:32:14 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:32:14 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:32:15 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:32:19 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:32:19 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:32:20 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:32:22 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:32:24 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:32:24 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:32:26 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:32:28 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:32:29 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:32:45 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:32:47 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:32:49 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:32:49 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:32:50 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:32:52 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:32:54 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:32:54 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:32:59 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:33:03 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:33:04 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:33:04 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:33:08 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:33:09 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:33:09 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:33:11 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:33:13 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:33:14 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:33:15 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:33:17 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:33:19 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:33:19 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:33:21 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:33:22 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:33:23 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:33:24 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:33:25 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 05:33:27 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 05:33:29 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 05:34:25 2014 LLDP warning lldpProcessNetPolicyTLV: Error, Net Policy VLAN ID 4095 invalid/reserved
TUE FEB 18 06:35:31 2014 INTERFACE debug1 1/15: link -
TUE FEB 18 06:35:32 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 09:34:04 2014 TELNET info New telnet connection, Address 10.10.10.2
TUE FEB 18 09:34:05 2014 TELNET info Session 63, Created
TUE FEB 18 09:39:32 2014 TELNET info Session 63, Session Ending
TUE FEB 18 09:59:31 2014 INTERFACE debug1 1/15: link +
TUE FEB 18 09:59:35 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1
TUE FEB 18 09:59:41 2014 LLDP warning lldpProcessNetPolicyTLV: Error, Net Policy VLAN ID 4095 invalid/reserved
TUE FEB 18 10:00:56 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:01:06 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:01:16 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:01:27 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:01:48 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:01:58 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:02:09 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:02:19 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:02:43 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:02:53 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:03:03 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:03:14 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:03:45 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:03:55 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:04:06 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:04:16 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:04:40 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:04:50 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:05:00 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:05:11 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:05:25 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:05:35 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:05:45 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015
TUE FEB 18 10:05:56 2014 IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015

Hi,
there are some different messages:

lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1

Did you have activated LBD at the switch?

Debug 1

Did you have changed the level to debug for more informations (not critical)? I am not sure about the message. Maybe one of the LBD-Ports is activated/deactivated now (connect/disconnect).

1/15: link +/-

= port up/down
Maybe the reason is LBD? or connect/disconnect phone?

lldpProcessNetPolicyTLV: Error, Net Policy VLAN ID 4095 invalid/reserved

did you have activated LLDP-MED with a LLDP policy? it seems that there is a wrong vlan used (or detected). Maybe the reason is wrong default config in phone or PBX. Try to deactivate lldp at the phone if you would not use it.

IP-HELPER error Mac Movement for MacAddr: 0:80:9f:a0:50:59 from port 1025 to port 1015

Did you use ip-helper or dhcp-server at the switch?

What release did you use? Please copy your config for more understanding of the reasons.

regards
Silvio

The answer is in your question.

1. Did you have activated LBD at the switch?

- I had just checked. Check the results .. LBC packet send is Gradually increases..

-> show loopback-detection statistics port 1/15
LBD Port Statistics
LBD Packet Send : 5
Invalid LBD Packet Received : 0

-> show loopback-detection port

Slot/Port Admin State OperState
-------------+---------------+-----------------
1/15 enabled Normal

9F6250-10.10.10.92-> show loopback-detection statistics port 1/15
LBD Port Statistics
LBD Packet Send : 7
Invalid LBD Packet Received : 0

9F6250-10.10.10.92-> show loopback-detection statistics port 1/15
LBD Port Statistics
LBD Packet Send : 9
Invalid LBD Packet Received : 0


2. Did you have changed the level to debug for more informations (not critical)?

- i used command "swlog appid INTERFACE level debug1"

3. did you have activated LLDP-MED with a LLDP policy?

- i not used LLDP-MED ... i don't know LLDP config ..

4. Did you use ip-helper or dhcp-server at the switch?

- PBX is dhcp-server

6250 switch relaese is OS6250-P24 6.6.3.470.R01 ..

5. all config information

-> write terminal
! Stack Manager :
! Chassis :
system daylight savings time disable
! Configuration:
! VLAN :
vlan 1 enable name "VLAN 1"
vlan 111 enable name "VLAN 111"
vlan 111 port default 1/1
vlan 111 port default 1/2
vlan 111 port default 1/3
vlan 111 port default 1/4
vlan 111 port default 1/5
vlan 111 port default 1/6
vlan 111 port default 1/7
vlan 111 port default 1/8
vlan 111 port default 1/9
vlan 111 port default 1/10
vlan 111 port default 1/11
vlan 111 port default 1/12
vlan 111 port default 1/13
vlan 111 port default 1/14
vlan 111 port default 1/15
vlan 111 port default 1/16
vlan 111 port default 1/17
vlan 111 port default 1/18
vlan 111 port default 1/19
vlan 111 port default 1/20
vlan 112 enable name "VLAN 112"
vlan 113 enable name "VLAN 113"
vlan 114 enable name "VLAN 114"
vlan 118 enable name "VLAN 118"
vlan 212 enable name "VLAN 212"
vlan 888 enable name "VLAN 888"
vlan 888 port default 1/21
vlan 888 port default 1/22
vlan 888 port default 1/23
vlan 888 port default 1/24
vlan 999 enable name "VLAN 999"
vlan port mobile 1/1
vlan port mobile 1/2
vlan port mobile 1/3
vlan port mobile 1/4
vlan port mobile 1/5
vlan port mobile 1/6
vlan port mobile 1/7
vlan port mobile 1/8
vlan port mobile 1/9
vlan port mobile 1/10
vlan port mobile 1/11
vlan port mobile 1/12
vlan port mobile 1/13
vlan port mobile 1/14
vlan port mobile 1/15
vlan port mobile 1/16
vlan port mobile 1/17
vlan port mobile 1/18
vlan port mobile 1/19
vlan port mobile 1/20
vlan 118 ip 192.168.118.0 255.255.255.0
vlan 212 mac range 00:80:9f:00:00:00 00:80:9f:ff:ff:ff
! VLAN SL:
! IP :
ip service all
ip interface "VLAN999-MANAGEMENT" address 10.10.10.92 mask 255.255.255.0 vlan 999 ifindex 1
! IPMS :
! AAA :
aaa authentication default "local"
aaa authentication console "local"
! PARTM :
! 802.1x :
! QOS :
! Policy manager :
! Session manager :
session prompt default
! SNMP :
! RIP :
! IPv6 :
! IP multicast :
! IPRM :
ip static-route 0.0.0.0/0 gateway 10.10.10.1 metric 1
! RIPng :
! Health monitor :
health threshold temperature 78
! Interface :
! Udld :
! Port Mapping :
! Link Aggregate :
! VLAN AGG:
! 802.1Q :
vlan 113 802.1q 1/21 "TAG PORT 1/21 VLAN 113"
vlan 114 802.1q 1/21 "TAG PORT 1/21 VLAN 114"
vlan 113 802.1q 1/22 "TAG PORT 1/22 VLAN 113"
vlan 114 802.1q 1/22 "TAG PORT 1/22 VLAN 114"
vlan 113 802.1q 1/23 "TAG PORT 1/23 VLAN 113"
vlan 114 802.1q 1/23 "TAG PORT 1/23 VLAN 114"
vlan 113 802.1q 1/24 "TAG PORT 1/24 VLAN 113"
vlan 114 802.1q 1/24 "TAG PORT 1/24 VLAN 114"
vlan 111 802.1q 1/25 "TAG PORT 1/25 VLAN 111"
vlan 112 802.1q 1/25 "TAG PORT 1/25 VLAN 112"
vlan 113 802.1q 1/25 "TAG PORT 1/25 VLAN 113"
vlan 114 802.1q 1/25 "TAG PORT 1/25 VLAN 114"
vlan 118 802.1q 1/25 "TAG PORT 1/25 VLAN 118"
vlan 212 802.1q 1/25 "TAG PORT 1/25 VLAN 212"
vlan 888 802.1q 1/25 "TAG PORT 1/25 VLAN 888"
vlan 999 802.1q 1/25 "TAG PORT 1/25 VLAN 999"
vlan 111 802.1q 1/26 "TAG PORT 1/26 VLAN 111"
vlan 112 802.1q 1/26 "TAG PORT 1/26 VLAN 112"
vlan 113 802.1q 1/26 "TAG PORT 1/26 VLAN 113"
vlan 114 802.1q 1/26 "TAG PORT 1/26 VLAN 114"
vlan 118 802.1q 1/26 "TAG PORT 1/26 VLAN 118"
vlan 212 802.1q 1/26 "TAG PORT 1/26 VLAN 212"
vlan 888 802.1q 1/26 "TAG PORT 1/26 VLAN 888"
vlan 999 802.1q 1/26 "TAG PORT 1/26 VLAN 999"
! Spanning tree :
bridge mode 1x1
bridge 1x1 1 priority 20000
bridge 1x1 111 priority 20000
bridge 1x1 112 priority 20000
bridge 1x1 113 priority 20000
bridge 1x1 114 priority 20000
bridge 1x1 118 priority 20000
bridge 1x1 212 priority 20000
bridge 1x1 888 priority 20000
bridge 1x1 999 priority 20000
bridge 1x1 1 1/26 path cost 100
bridge 1x1 111 1/26 path cost 100
bridge 1x1 112 1/26 path cost 100
bridge 1x1 113 1/26 path cost 100
bridge 1x1 114 1/26 path cost 100
bridge 1x1 118 1/26 path cost 100
bridge 1x1 212 1/26 path cost 100
bridge 1x1 888 1/26 path cost 100
bridge 1x1 999 1/26 path cost 100
! Bridging :
! Bridging :
! Port mirroring :
! UDP Relay :
ip helper dhcp-snooping enable
ip helper dhcp-snooping option-82 data-insertion disable
ip helper dhcp-snooping mac-address verification disable
ip helper dhcp-snooping binding disable
ip helper dhcp-snooping port 1/25 trust
ip helper dhcp-snooping port 1/26 trust
! System service :
swlog appid INTERFACE level debug1
swlog console level info
! SSH :
! VRRP :
! Web :
! AMAP :
! Lan Power :
lanpower 1 maxpower 225
lanpower start 1
! NTP :
! RDP :
! VLAN STACKING:
! EFM-OAM :
! SAA :
! Loopback-detection :
loopback-detection enable
loopback-detection port 1/15 enable
! ERP :
! TEST-OAM :
! DHL :
! LLDP :
! DHCP Server :

thank you silvio

Hi,
first I would prefer to make an update to a newer release. In 6.6.3 there is actual built 6.6.3.520.

If the messages are after update anymore:
- debug-messages are no big errors (no warning etc.). did anyone disconnect/connect phone at port 1/15 during this time?
You use ALU phones. Please check there the lldp-config direct at the phones - there you can disable lldp.


- I'm wondering about the mac-movement-errors. You didn not use ip helper at the switch. So it could only be the dhcp-snooping. So I would suggest to temporarily deactivate dhcp-snooping.

Have you seen all this messages only once? Or can you see it all the time? Did the switch work before this messages a long time without errors?

regards
Silvio

So what exactly is your problem?
The Error messages? Which one?

Point 1:
the lbd messages?
"TUE FEB 18 04:11:40 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1"
are probably normal as you have configured loopback detection on port 1/15.


Point 2:
Why did you do that? For what purpose?


For mac Movement there was something similar (?) fixed in 483

"PR 181003 Build: 6.6.3.489.R01
Summary: Delay on port activating with LLDP- MED configuration on OS6450.
Explanation:
when IP phone is connected to switch1 on port 1/4 and port 1/24 of switch1 is connected to the
switch2 1/10. when the IP phone gets up, the mac address of the IP phone is getting learned
properly on the port 1/4 of the switch1 and uplink port 1/10 of switch2.then when we connect IP
phone to to the port 1/4 of switch2. the mac address of the IP Phone is not getting on the Port
till the mac on the uplink port gets aged out. Once the mac is getting aged out ,it is get learned
on the connected port.ie the Mac movement is not happening properly when we have connect
to IP phone . So Changes have been done for proper mac movement handling"

I would (as always) update to the latest release (6.6.3.520 OR 6.6.4.208) and see whether this fixes anything.

Please do a
show interface 1/15 an see whether the interface status changes/ last status change time corresponds with you up down messages.

What is connected to 1/25?

to silvio

1. you suggest that lldp-config direct at the phones - there you can disable lldp.

but i not know lldp-config at the phone. how i do config at the phone ??

2. i can see it all the time .. before i do config that loopback-detection port 1/15 enable

a big problem that SIP phone register is disconnect ...




to devnull

TUE FEB 18 04:11:40 2014 INTERFACE debug1 lbdProcessMsg:454 Recieved: LBD_PORT_STATE for slot = 1"

this message is that before i lbd config

1/25 port is up-link port to backbone switch ..

you can change the lldp-settings in network config of the phone (depending from the phone and the image of the phone).
But there are still some more questions open...

regards
Silvio