topic Re: FD110 credit card terminal will not link up to an EXOS 5520 switch in ExtremeSwitching (EXOS/Switch Engine)

FD110 credit card terminal will not link up to an EXOS 5520 switch

Keith9 — Sat, 13 Feb 2021 22:46:08 GMT

We have First Data FD110 credit card terminals that will not link up to an EXOS 5520 switch. On a Cisco switch they auto negotiate to 100/full. On an EXOS switch they also auto negotiate to 100/full but the device will not get a DHCP address. The same machine works fine an an X450G2 switch from Extreme.

Whats really unusual is the switch shows a link, but either doing DHCP or Static IP on the credit card terminal, neither will ping out. We are not sure what is so unique about these devices. For now we have to uplink to a Cisco switch just to hold them.

Any idea what the issue could be?

Thanks!

Re: FD110 credit card terminal will not link up to an EXOS 5520 switch

Keith9 — Sun, 14 Feb 2021 01:03:29 GMT

This is also an issue with an AudioCodes MP-118 VOIP Telephony adapter.

The device links on a 5520 but will only achieve IP connectivity through a Cisco.

Re: FD110 credit card terminal will not link up to an EXOS 5520 switch

Keith9 — Sun, 14 Feb 2021 03:34:18 GMT

Add APC UPS’s and PDU’s to this issue.

Auto negotiates at 100.full. They are static IP assigned. Can’t ping from the network, can’t ping from the switch. The switch shows link light and the device shows link light. sh port shows link enabled and active.

I don't understand why these types of devices work fine when plugged into a Cisco 3750 switch stack, but when plugged into a 5520 EXOS switch they don’t work. I compared the config to working X450-G2 switches we have in other offices and its the same. Similar APC UPS’s and PDU’s, AudioCodes MP-118 VOIP adapters and FD110 credit card terminals all work fine into X450-G2’s.

Any idea? I’m perplexed and annoyed we have a cable uplinked to an older 3750v2 switch just for these devices. The switch is going EOL and needs to be removed.

Re: FD110 credit card terminal will not link up to an EXOS 5520 switch

yas1 — Sun, 14 Feb 2021 23:46:43 GMT

Hi Keith,

Do you see MAC addresses on these specific ports (sho fdb port <port>)?

Interestingly i had a similar issue on the new 5520 with a card terminal and a sensor which only works now with static 10/full duplex configuration. However on the old switch it worked with auto negotiation 100/Full.

Have a check with “show port <port> advertise” what the device is advertising to the switch and give it a try to set the port speed/duplex settings manually.

Best regards
Yannick

Re: FD110 credit card terminal will not link up to an EXOS 5520 switch

Keith9 — Mon, 15 Feb 2021 06:11:31 GMT

I recall not seeing a mac address at all on a port where a card terminal was installed.

However the APC gear like PDU’s and rack mount UPS’s do show. Also I can verify the IP with sh iparp command. There’s just no communication at all. Cannot ping or access them at all despite showing 100 full.

Here’s an example of a APC Addressable PDU plugged into port 2:6 of a 5520 switch running EXOS 31.1.1.3 showing linked at 100/full

sh port 2:47 advertised

sh port 2:6 advertised
       10BaseT     100BaseT    100X        1000BaseT   1000X       Pause
Port   Half Full Half Full Half Full Half Full Half Full TX RX Asym
----- ---------- ---------- ---------- ---------- ---------- ------------
*2:6   CLR   CLR   CLR   CLR   ---   ---   ---   CL-   ---   ---   CLR CLR CLR
Flags: (*) Active, (!) Disabled, (C) Capable, (L) Local Advertised, (R) Remote Advertised.

I’m also showing IP to ARP mapping

sh iparp | i 10.40.0.15
VR-Default 10.40.0.15 00:c0:b7:5a:e9:5f 20 NO Default 1 2:6

sh fdb port 2:6
MAC VLAN Name( Tag) Age Flags Port / Virtual Port List
------------------------------------------------------------------------------------------------------
00:c0:b7:5a:e9:5f Default(0001) 0000 d mi 2:6

ping 10.40.0.15
Ping(ICMP) 10.40.0.15: 4 packets, 8 data bytes, interval 1 second(s).
Request timed out
Request timed out
Request timed out
Request timed out

--- 10.40.0.15 ping statistics ---
4 packets transmitted, 0 packets received, 100% loss
round-trip min/avg/max = 0/0/0 ms

So let me try forcing it to 10/full…

configure port 2:6 auto off speed 10 duplex full

ping 10.40.0.15
Ping(ICMP) 10.40.0.15: 4 packets, 8 data bytes, interval 1 second(s).
16 bytes from 10.40.0.15: icmp_seq=0 ttl=255 time=10 ms
16 bytes from 10.40.0.15: icmp_seq=1 ttl=255 time=4.003 ms
16 bytes from 10.40.0.15: icmp_seq=2 ttl=255 time=4.799 ms
16 bytes from 10.40.0.15: icmp_seq=3 ttl=255 time=6.238 ms

--- 10.40.0.15 ping statistics ---
4 packets transmitted, 4 packets received, 0% loss
round-trip min/avg/max = 4/6/10 ms

So now its connected. This is so bizarre. I will open a case with GTAC on Monday morning. You shouldn’t have to run circles around managing port speeds. We didn’t ever have to worry about port speed/duplex settings on Cisco 3750’s, Extreme X690s, or X450-G2’s. The 5520 is supposed to be the newer, better switch. To me this is a step backwards to the 90’s and earlier (having to manage speed and duplex settings). Have to say I’m dissapointed in the 5520. Between this and the inability to use 1000 base T copper SFP’s in the VIM-4X, I wish I would have just gotten the X450-G2’s. They work as expected.

Thanks for your trick on specifying port speeds to 10/full. At least that seems to get PDU’s and UPS’s on line. When I’m in the office Monday I’ll move some of those troublesome devices off the Cisco switch and back to the 5520 and try the port speed there.

Re: FD110 credit card terminal will not link up to an EXOS 5520 switch

Keith9 — Mon, 15 Feb 2021 06:24:57 GMT

Here’s another strange one, so an APC rack mount SmartUPS was showing connected 100/full, but could not ping it. I tried your trick to set it to 10/full and now I can ping it and access its web management page.

However on the switch its shows 10/full,

but on APC’s web UI it says its 10/half.

This is just so bizarre. I requested EXOS 31.2.1.1 (upgrade from 31.1.1.3) so I will load that on later in the week and see if that changes anything.

Re: FD110 credit card terminal will not link up to an EXOS 5520 switch

yas1 — Mon, 15 Feb 2021 22:04:18 GMT

I was also very surprised that only static 10 Mbit worked with these devices. I hope that this is only a bad workaround.. Please keep this thread updated when GTAC provides some information about this.

Re: FD110 credit card terminal will not link up to an EXOS 5520 switch

Keith9 — Mon, 15 Feb 2021 22:29:39 GMT

GTAC Case # (02332940) has been opened for this issue.

Issue persists on two different 5520 stacks in two seperate geographic areas (ruling out hardware).

Both stacks are on 31.1.1.3.

Affected devices:
APC SmartUPS Rack mount UPS ethernet (requires static 10/full)
APC PDU addressable rack mount PDU's (requires static 10/full)
Audiocodes MP-118 VOIP Telephony gateway (requires static 10/full)
Barix extreamer100 audio streaming device (requires static 10/full)
FirstData 110 Credit Card terminal (requires static 10/half)

I was able to remove the Cisco 3750 switch today after finding this out.

Hopefully GTAC can resolve. I do not have this issue on our X690’s or X450G2’s. There is nothing special about these access ports.

Re: FD110 credit card terminal will not link up to an EXOS 5520 switch

Keith9 — Mon, 15 Feb 2021 23:21:14 GMT

Add a Geist Watchdog 1200 1U environment monitor to that list. Requires a hardcoded 10/full.

Re: FD110 credit card terminal will not link up to an EXOS 5520 switch

Keith9 — Tue, 16 Feb 2021 04:07:30 GMT

One more device in our arsenal requires 10/full static assignment.

The newer model Black Epson TI-88v-i thermal receipt printer links up but is not pingable unless the port is set to 10/full.

The older beige Epson TM-T88V that are many years old now do NOT have this problem.

Re: FD110 credit card terminal will not link up to an EXOS 5520 switch

Keith9 — Thu, 18 Feb 2021 01:03:17 GMT

I requested and put xos 31.2.1.1 on 3 stacks of 5520’s last night.

I need more time to test all of the problematic device types, but one of the APC PDU’s that only worked at 10/full is now pingable when changing the port to auto and watching it sync up at 100/full. That's a good start.

I didn’t like 31.1.1.3 anyway. It always said (31.1.1.3) in front of the command prompt. It felt more like an engineering sample than a full release. 31.2.1.1 cleans up the command prompt and it looks like it may have fixed auto port negotiation.

I’ll report back when I do further testing.

Re: FD110 credit card terminal will not link up to an EXOS 5520 switch

Keith9 — Thu, 18 Feb 2021 02:50:46 GMT

Ok after further testing here were my exceptions

configure ports 1:11 auto off speed 10 duplex full WATCHDOG 1200
configure ports 1:21 auto off speed 10 duplex half Mastercard Adv Machine
configure ports 2:3 auto off speed 10 duplex full AUDIOCODES MP-118
configure ports 2:6 auto off speed 10 duplex full PDU UPPER
configure ports 2:9 auto off speed 10 duplex full D101 EPSON Receipt
configure ports 2:22 auto off speed 10 duplex full D106 BARIX AUDIO STREAMER
configure ports 2:47 auto off speed 10 duplex full APC UPS

One by one changed them back to auto

configure ports 1:11 auto on
configure ports 1:21 auto on
configure ports 2:3 auto on
configure ports 2:6 auto on
configure ports 2:9 auto on
configure ports 2:22 auto on
configure ports 2:47 auto on

With each port I checked the log, did a sh port and they came up as 100 / full.

I then pinged again and sh iparp on that port and connectivity remains.

So the answer is to upgrade to XOS 31.2.1.1! Not only does it fix this, but it also cleans up the CLI as it just simply shows the switch’s hostname at the prompt instead of the annoying build number in front of the hostname at the prompt.

It feels like this is a better overall build.

Now we will be eagerly awaiting a future build that supports 1gbps copper sfp’s in the VIM-4X slots, and then we have all the same functionality as the 450-G2 switches we have at other sites. Support is estimating an August GA.

Re: FD110 credit card terminal will not link up to an EXOS 5520 switch

timferroz — Tue, 07 Apr 2026 04:11:59 GMT

This usually happens because those older credit card terminals don’t negotiate properly with newer switches, even if the link shows as 100/full. The port looks up, but actual communication fails, so no DHCP or ping works. That’s why it works on Cisco or older hardware but not on the EXOS 5520. The proper fix is upgrading to XOS 31.2.1.1, since it improves auto-negotiation, otherwise forcing the port to 10/full is a common workaround.

It’s kind of similar to how credit card transactions behave on the banking side. Sometimes everything looks processed on your card, but the system you’re using doesn’t reflect it instantly. I’ve seen that with FAB bank tools too, where the app and backend don’t always sync right away. If you ever check that kind of thing, https://fbbalancecheck.ae/
gives a clearer idea of what’s actually recorded versus what just shows up at first glance.