cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1064
Views
0
Helpful
3
Replies

Duplicated IPs on switch from WLC in SSO mode

Vachy
Level 1
Level 1

Hello,

 

We got some interesting problem. We are using HP 7506 Stack Switch in IRF. With this switch are WLCs 5520 connected. WLCs are configured in SSO. Every WLC are only with one 'Ten-Gigabit' port connected.

RP port goes already through central HP switch but with another port and VLAN.

WLC got almost all VLANs with a tag. The management interface is in the VLAN 400. Only VLAN1 is untaged. I tested also HYBRID config, but problem was always same.

 

My problem is that time by time comes to switch's log this message:

 

%Jan 20 10:17:41:772 2018 CORE ARP/5/ARP_DUPLICATE_IPADDR_DETECT: -Chassis=2-Slot=2; Detected an IP address conflict. The device with MAC address 006b-f161-20af connected to Ten-GigabitEthernet2/2/0/6 in VLAN 400 and the device with MAC address 006b-f161-20b0 connected to Ten-GigabitEthernet2/2/0/6 in VLAN 400 are using the same IP address 10.140.0.198.

OR

 

%Jan 19 14:47:59:014 2018 CORE ARP/5/ARP_DUPLICATE_IPADDR_DETECT: -Chassis=1-Slot=2; Detected an IP address conflict. The device with MAC address 006b-f1cd-5059 connected to Ten-GigabitEthernet1/2/0/6 in VLAN 1 and the device with MAC address 006b-f1cd-505a connected to Ten-GigabitEthernet1/2/0/6 in VLAN 1 are using the same IP address 10.110.20.25.

 

The report comes quite often and in my opinion has nothing to do with the SSO exchange. He always comes to the port where MASTER unit is. 2/2/0/6 or 1/2/0/6.

 

All mac addresses always belong to one WLC.

 

[CORE]dis mac-address interface t 1/2/0/6
MAC ADDR VLAN ID STATE PORT INDEX AGING TIME(s)
006b-f1cd-5059 1 Learned Ten-GigabitEthernet1/2/0/6 AGING
006b-f1cd-505a 1 Learned Ten-GigabitEthernet1/2/0/6 AGING
3010-b3da-2839 1 Learned Ten-GigabitEthernet1/2/0/6 AGING
787b-8a31-98f9 1 Learned Ten-GigabitEthernet1/2/0/6 AGING
acfd-ce32-119e 1 Learned Ten-GigabitEthernet1/2/0/6 AGING
dca9-0415-d2b3 1 Learned Ten-GigabitEthernet1/2/0/6 AGING
64cc-2ed2-1173 301 Learned Ten-GigabitEthernet1/2/0/6 AGING
7c0b-c629-2897 301 Learned Ten-GigabitEthernet1/2/0/6 AGING
e05f-4572-0f4b 301 Learned Ten-GigabitEthernet1/2/0/6 AGING
e850-8ba3-488e 301 Learned Ten-GigabitEthernet1/2/0/6 AGING
ec10-7b32-9131 301 Learned Ten-GigabitEthernet1/2/0/6 AGING
f4f1-5ade-4359 301 Learned Ten-GigabitEthernet1/2/0/6 AGING
006b-f1cd-5059 400 Learned Ten-GigabitEthernet1/2/0/6 AGING
006b-f1cd-505a 400 Learned Ten-GigabitEthernet1/2/0/6 AGING

--- 14 mac address(es) found ---

[CORE]dis mac-address interface t 2/2/0/6
MAC ADDR VLAN ID STATE PORT INDEX AGING TIME(s)
006b-f161-20af 400 Learned Ten-GigabitEthernet2/2/0/6 AGING
006b-f161-20b0 400 Learned Ten-GigabitEthernet2/2/0/6 AGING

 

 

Port CONFIG (PVID is 1):

 

interface Ten-GigabitEthernet1/2/0/6
port link-mode bridge
port link-type trunk
port trunk permit vlan 1 to 99 101 to 198 200 to 404 406 to 4094
stp loop-protection

 

Port Status:

 

Ten-GigabitEthernet1/2/0/6 current state: UP
IP Packet Frame Type: PKTFMT_ETHNT_2, Hardware Address: 4431-92e8-b775
Loopback is not set
Media type is optical fiber,Port hardware type is 10G_BASE_SR_SFP
10Gbps-speed mode, full-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
Flow-control is not enabled
The Maximum Frame Length is 10000
Broadcast MAX-ratio: 100%
Unicast MAX-ratio: 100%
Multicast MAX-ratio: 100%
Allow jumbo frame to pass
PVID: 1
Mdi type: auto
Port link-type: trunk
VLAN passing : 1(default vlan), 2, 5-6, 8, 10-11, 20-24, 26-32, 35, 40, 98, 101-110, 200, 210, 300-302, 400-404, 406-446, 777
VLAN permitted: 1(default vlan), 2-99, 101-198, 200-404, 406-4094
Trunk port encapsulation: IEEE 802.1q
Port priority: 0
Last clearing of counters: Never
Peak value of input: 16026435 bytes/sec, at 2018-01-16 07:05:22
Peak value of output: 25376019 bytes/sec, at 2018-01-19 09:02:26
Last 300 seconds input: 66 packets/sec 48219 bytes/sec 0%
Last 300 seconds output: 415 packets/sec 92454 bytes/sec 0%
Input (total): 685624297 packets, 531097338435 bytes
684263972 unicasts, 757412 broadcasts, 602910 multicasts, 0 pauses
Input (normal): 685624294 packets, - bytes
684263972 unicasts, 757412 broadcasts, 602910 multicasts, 0 pauses
Input: 0 input errors, 0 runts, 0 giants, 0 throttles
0 CRC, 0 frame, - overruns, 0 aborts
- ignored, - parity errors
Output (total): 37987820062 packets, 9927634482320 bytes
1510447561 unicasts, 4181926400 broadcasts, 32295446101 multicasts, 0 pauses
Output (normal): 37987820062 packets, - bytes
1510447561 unicasts, 4181926400 broadcasts, 32295446101 multicasts, 0 pauses
Output: 0 output errors, - underruns, - buffer failures
0 aborts, 0 deferred, 0 collisions, 0 late collisions
0 lost carrier, - no carrier

 

 

Do you have some experience with it? I have a LOG full of DUPLICIT messages. I can filter it out, but I think something is wrong somewhere.

 

Thanks

1 Accepted Solution

Accepted Solutions

The solution is quite simple, we came upon it by accident. Just put another SPF + transciever into the second free slot in WLC. It must not be plugged in network. From this time was DUPLICITY away.

View solution in original post

3 Replies 3

Hi

Those IP address above are configured on the WLC ? On which interface?

 When in SSO wlc share an vIP but the management interface IP address is different. 

 Don't make too much  sense this conflict.

 

 

 

-If I helped you somehow, please, rate it as useful.-

Yes - Interfaces in Log with errors are:

 

10.140.0.195     - VLAN 400 - Tag (Management)

10.140.0.197-8 - VLAN 400 - Tag (Redundancy MGMT)

10.110.20.25     - VLAN 1 - UnTag (Interface)

 

Rest VLANs 8, 301, 408 are Tagged and this IPs figured no in Logs.

What is interesting, that SNMP Traps and Syslog for WLC working best through VLAN1 and not through MGMT interface. Maybe it has something to do with it.

 

The solution is quite simple, we came upon it by accident. Just put another SPF + transciever into the second free slot in WLC. It must not be plugged in network. From this time was DUPLICITY away.