Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 19 replies
  • Subscribers 6 subscribers
  • Views 3702 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RED port goes down

dirkkotte

Hi all,

I have a RED that unexpectedly shuts down one of the ports.
The port was previously connected directly to a device, currently we put a switch between RED and the device.
But the problem persists. Can someone help?
Here are the messages ... what does the "command" mean?

2023:01:08-23:49:29 FIREWALL-2 red_server[13285]: R6000XXXXXXXX8: command '{"data":{"switch_port_status_v2":{"lan3":"Down","lan1":"Down","lan4":"1Gb\/s","lan2":"Down"}},"type":"STATUS"}' 
2023:01:08-23:49:29 FIREWALL-2 red_server[13285]: R6000XXXXXXXX8: PORTSTATE LAN1: Down, LAN2: Down, LAN3: Down, LAN4: 1Gb/s 
2023:01:08-23:49:45 FIREWALL-2 red_server[13285]: R6000XXXXXXXX8: command '{"data":{"switch_port_status_v2":{"lan3":"1Gb\/s","lan1":"Down","lan4":"1Gb\/s","lan2":"Down"}},"type":"STATUS"}' 
2023:01:08-23:49:45 FIREWALL-2 red_server[13285]: R6000XXXXXXXX8: PORTSTATE LAN1: Down, LAN2: Down, LAN3: 1Gb/s, LAN4: 1Gb/s 
2023:01:08-23:51:37 FIREWALL-2 red_server[13285]: R6000XXXXXXXX8: command '{"data":{"switch_port_status_v2":{"lan3":"Down","lan1":"Down","lan4":"1Gb\/s","lan2":"Down"}},"type":"STATUS"}' 
2023:01:08-23:51:37 FIREWALL-2 red_server[13285]: R6000XXXXXXXX8: PORTSTATE LAN1: Down, LAN2: Down, LAN3: Down, LAN4: 1Gb/s 
2023:01:08-23:51:53 FIREWALL-2 red_server[13285]: R6000XXXXXXXX8: command '{"data":{"switch_port_status_v2":{"lan3":"1Gb\/s","lan1":"Down","lan4":"1Gb\/s","lan2":"Down"}},"type":"STATUS"}' 
2023:01:08-23:51:53 FIREWALL-2 red_server[13285]: R6000XXXXXXXX8: PORTSTATE LAN1: Down, LAN2: Down, LAN3: 1Gb/s, LAN4: 1Gb/s 
2023:01:08-23:52:25 FIREWALL-2 red_server[13285]: R6000XXXXXXXX8: command '{"data":{"switch_port_status_v2":{"lan3":"Down","lan1":"Down","lan4":"1Gb\/s","lan2":"Down"}},"type":"STATUS"}' 
2023:01:08-23:52:25 FIREWALL-2 red_server[13285]: R6000XXXXXXXX8: PORTSTATE LAN1: Down, LAN2: Down, LAN3: Down, LAN4: 1Gb/s 
2023:01:08-23:52:41 FIREWALL-2 red_server[13285]: R6000XXXXXXXX8: command '{"data":{"switch_port_status_v2":{"lan3":"1Gb\/s","lan1":"Down","lan4":"1Gb\/s","lan2":"Down"}},"type":"STATUS"}' 
2023:01:08-23:52:41 FIREWALL-2 red_server[13285]: R6000XXXXXXXX8: PORTSTATE LAN1: Down, LAN2: Down, LAN3: 1Gb/s, LAN4: 1Gb/s

Thanks

Dirk



This thread was automatically locked due to age.
Parents
  • 0

    From my understanding "STATUS" is a command to the RED and what you see in "data" is the response.
    So LAN1 and 2 are not connected, LAN4 is solid up and LAN3 is flaky.

    Can you debug from the switch side?
    Maybe LAN3 and LAN4 are in the same broadcast domain and the switch shuts down one because of STP BPDUs received?
    AFAIK there is no way to link RED ports together via LACP or similar.

    I also had this effect once long ago with an EthernetConnect line provided by Deutesche Telekom with N10ETH SDSL devices - here the ethernet port was set by the Telekom to 10FDX with no NWAY auto negotiation in place, a thing the RED doesn't like as well - but this affected the WAN port. The fix here was to add a small switch with two ports connected - fixed at Telekom side and auto negotiation at RED side.

    Also keep in mind, that all LAN ports of the RED come with the same MAC (after all it's a built-in switch), some other Switches don't like it if they see the same MAC on different ports.

Reply
  • 0

    From my understanding "STATUS" is a command to the RED and what you see in "data" is the response.
    So LAN1 and 2 are not connected, LAN4 is solid up and LAN3 is flaky.

    Can you debug from the switch side?
    Maybe LAN3 and LAN4 are in the same broadcast domain and the switch shuts down one because of STP BPDUs received?
    AFAIK there is no way to link RED ports together via LACP or similar.

    I also had this effect once long ago with an EthernetConnect line provided by Deutesche Telekom with N10ETH SDSL devices - here the ethernet port was set by the Telekom to 10FDX with no NWAY auto negotiation in place, a thing the RED doesn't like as well - but this affected the WAN port. The fix here was to add a small switch with two ports connected - fixed at Telekom side and auto negotiation at RED side.

    Also keep in mind, that all LAN ports of the RED come with the same MAC (after all it's a built-in switch), some other Switches don't like it if they see the same MAC on different ports.

Children
No Data
Unfiltered HTML