Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 1616 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

XGS LAG problem

Martin Nowak

Hi all,

I have a XGS116 and created a LACP LAG to the L3 core switch. The LAG is working as I can ping from the firewall the core switch and it´s all VLAN interfaces. The strange issue I have is that I can´t ping any other device "behind" the core switch. I added another interface (Port 7) attached to the core switch and from this interface I can ping any VLAN interface on the core switch and also any VLAN device attached to the core as well.

The LAG on the core switch is set up as LAG LACP, trunk, all VLANs. The LAG interface on the XGS have IP address 192.168.1.1. The core switch have 192.168.1.2. Internal VLANs are 10,20,30 and so on. So it´s like 192.168.10.x etc. The core switch VLAN interface IPs are 192.168.x.254.

See below ping tests:

So other words, via the LAG I can only reach the core switch and then it ends here. Via the Port 7 I can reach anything.

Any ideas?



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

    I think there are problems with interface configuration. Can you show us the port-Config of LAG and Port7?

    A short network-sketch would be helpful.

    Do you have one subnet between XG and Switch and other subnets behind the switch or are all VLANS/Subnets connected to the XG? 

  • 0 in reply to dirkkotte

    Sometime you need to sleep over the night and try with fresh mind again. It was my own logical error in the setup. I deleted the LAG and the Port7 configuration and recreated the LAG again. Now it´s working as desired. My bad was to have same IP range assigned to the LAG and other port on the XGS. This way it was not clear which route to use for reaching next hop.

Reply
  • 0 in reply to dirkkotte

    Sometime you need to sleep over the night and try with fresh mind again. It was my own logical error in the setup. I deleted the LAG and the Port7 configuration and recreated the LAG again. Now it´s working as desired. My bad was to have same IP range assigned to the LAG and other port on the XGS. This way it was not clear which route to use for reaching next hop.

Children
No Data