… cross-over cable ... if the phones are not auto-MDIX ...

Which means that the ports in the SG-3100 do not support auto-MDI/MDX as well?
Seriously, in a 2017 design?

Have you tried using a cross-over cable there?

You may well need one if the phones are not auto-MDIX and I don't believe those are.

Steve

Crossover cable does the trick. You sir, are a gentleman and a scholar.  8)

Thanks

Have you tried using a cross-over cable there?

You may well need one if the phones are not auto-MDIX and I don't believe those are.

Steve

This is a good point. I will need to test.

You may well need one if the phones are not auto-MDIX and I don't believe those are.

Steve

@VAMike:

@johnkeates:

@networkninja:

Hello,

I just discovered that the SG-3100 LAN ports (1-4) will not link to any Cisco 7940 Gigabit phone. The phone displays "ethernet disconnected", and there are no link lights on the firewall side. If I move the cable to OPT1 it links up fine. Has anyone seen this issue?  Was able to replicate this issue on two different SG-3100s. I moved the LAN to OPT1 to work around this issue, but it would be good to know if there's a solution.

Thanks

Might be a autosense mismatch. If you are running the latest pfSense update, try changing the switch duplex and speed settings.

That's basically never the right thing to do. If you find yourself burning with the need to override the autonegotiation, be aware that you have to do it on both ends or things will really break.

Well, with stupid implementations like some older Cisco phones, sometimes it is. Some of them try to negotiate 1000Mbit + full-duplex on a 100Mbit port. On the other hand, the switch in the SG might be bad. Keep in mind that this kind of configuration is only made when we assume one or more devices in the chain are bad.

I tried two different SG-3100's and two different phones.

@johnkeates:

@networkninja:

Hello,

I just discovered that the SG-3100 LAN ports (1-4) will not link to any Cisco 7940 Gigabit phone. The phone displays "ethernet disconnected", and there are no link lights on the firewall side. If I move the cable to OPT1 it links up fine. Has anyone seen this issue?  Was able to replicate this issue on two different SG-3100s. I moved the LAN to OPT1 to work around this issue, but it would be good to know if there's a solution.

Thanks

Might be a autosense mismatch. If you are running the latest pfSense update, try changing the switch duplex and speed settings.

That's basically never the right thing to do. If you find yourself burning with the need to override the autonegotiation, be aware that you have to do it on both ends or things will really break.

Well, with stupid implementations like some older Cisco phones, sometimes it is. Some of them try to negotiate 1000Mbit + full-duplex on a 100Mbit port. On the other hand, the switch in the SG might be bad. Keep in mind that this kind of configuration is only made when we assume one or more devices in the chain are bad.

@johnkeates:

@networkninja:

Hello,

I just discovered that the SG-3100 LAN ports (1-4) will not link to any Cisco 7940 Gigabit phone. The phone displays "ethernet disconnected", and there are no link lights on the firewall side. If I move the cable to OPT1 it links up fine. Has anyone seen this issue?  Was able to replicate this issue on two different SG-3100s. I moved the LAN to OPT1 to work around this issue, but it would be good to know if there's a solution.

Thanks

Might be a autosense mismatch. If you are running the latest pfSense update, try changing the switch duplex and speed settings.

That's basically never the right thing to do. If you find yourself burning with the need to override the autonegotiation, be aware that you have to do it on both ends or things will really break.

I just looked and even on 2.4.2 I don't see a way to manually set speed and duplex on the 4 switch ports even if I wanted to.

I would try out a small switch between them to ensure that the auto sensing miss match will be gone.
Cisco Small Business SG110-16HP

Did you set up a proper cabling? As shown on the picture below?

Hi Frank,

I did verify the cabling. I have tried this with two different phones and two different SG-3100's and I had the same result. Putting a switch in between one of the LAN ports and the phone does fix the issue. These Cisco phones use Voice VLANs and also support PoE, I wonder if one of those two features is not supported by the Marvell 6000 switch.

Thanks for looking.

@networkninja:

Hello,

I just discovered that the SG-3100 LAN ports (1-4) will not link to any Cisco 7940 Gigabit phone. The phone displays "ethernet disconnected", and there are no link lights on the firewall side. If I move the cable to OPT1 it links up fine. Has anyone seen this issue?  Was able to replicate this issue on two different SG-3100s. I moved the LAN to OPT1 to work around this issue, but it would be good to know if there's a solution.

Thanks

Might be a autosense mismatch. If you are running the latest pfSense update, try changing the switch duplex and speed settings.

That's basically never the right thing to do. If you find yourself burning with the need to override the autonegotiation, be aware that you have to do it on both ends or things will really break.

Did you set up a proper cabling? As shown on the picture below?

Might be a autosense mismatch. If you are running the latest pfSense update, try changing the switch duplex and speed settings.

That would be the first time Auto Sensing doesn't work since the Alix 2D3 days, but next time I have one in front of me I will try that.

Hello,

I just discovered that the SG-3100 LAN ports (1-4) will not link to any Cisco 7940 Gigabit phone. The phone displays "ethernet disconnected", and there are no link lights on the firewall side. If I move the cable to OPT1 it links up fine. Has anyone seen this issue?  Was able to replicate this issue on two different SG-3100s. I moved the LAN to OPT1 to work around this issue, but it would be good to know if there's a solution.

Thanks

Might be a autosense mismatch. If you are running the latest pfSense update, try changing the switch duplex and speed settings.