This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Extreme Networks
- Community List
- Switching & Routing
- ExtremeSwitching (EXOS/Switch Engine)
- FD110 credit card terminal will not link up to an ...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
FD110 credit card terminal will not link up to an EXOS 5520 switch
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
02-13-2021 02:46 PM
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!
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
02-17-2021 06:50 PM
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.
11 REPLIES 11
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
02-13-2021 07:34 PM
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.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
02-13-2021 05:03 PM
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.
