cancel
Showing results for 
Search instead for 
Did you mean: 

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

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

Keith9
Contributor III

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!

1 ACCEPTED SOLUTION

Keith9
Contributor III

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.

 

View solution in original post

11 REPLIES 11

Keith9
Contributor III

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.

 

Keith9
Contributor III

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.​​​​​​​

Keith9
Contributor III

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. 

Keith9
Contributor III

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

GTM-P2G8KFN