NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
M4300 SFP Port Trunking Issues
Hi all, I recently purchased 2 new M4300 and form a stack. After stacking the SW, I started to setup the switch as normal, the management VLAN, IP, the rest of vlan, subnet of those VLAN. Since i...
Hi Kelvin,
It's a good news that the failover problem resolved.:smileyhappy:
Let's carry on the VRRP scenario.
I have checked the maintenance file just you sent to us.
1) Congratulation！The address (192.168.100.2 ) is the virtual IP address of VRRP on Firewall.
Because this IP have same prefix mac-address header just like (00:00:5E:00:xx:xx).
It's the standard of VRRP for mac-address behavior.
2) Good finding! The "Link state detection” is very useful for VRRP status.
So we need to set the IP for heartbeat on each Firewall that could monitor VRRP all the time.
But 192.168.100.1 is not the heartbeat address for Firewall that is VLAN interface on M4300-Stack.
So Could you set an IP address on Firewall A and B that is not VRRP protocol.
Such as:
192.168.100.10 /24 on Firewall A.
192.168.100.20 /24 on Firewall B.
Then,
Set Link state detection IP address to 192.168.100.20 on Firewall A.
Set Link state detection IP address to 192.168.100.10 on Firewall B.
That will make Firewall detect each other with this configuration.
3) Could you share me the configuration page or command on your Firewall about LAG/Port/IP address/VRRP configuration？
The private message is RECOMMENDED.
I'm not very professional on Firewall of other company.
Just want to help analyze.:smileyhappy:
Look forward to your reply.
Regards,
Daniel.
Hi Kelvin,
Please go to Routing-->IP-->Advance-->IP interface configuration.
The port routing mode can be change to disable or enable in this page.
You can get correct VLAN tag status after set port to Disable of Routing mode.
Maybe there will cause a broadcast storm after set port to layer 2 working mode（disable routing）.
So please beware with loop between layer 2 network.
Otherwise, M4300 don't support MLAG function but VRRP is ready.
Please check configuration example from below link about VRRP function:
How do I configure the Virtual Router Redundancy Protocol (VRRP)
Or the user manual for M4300 about all function maybe you need to check:
M4300 Software Administration Manual
-->Page 156 chapter 10
Regards,
Daniel.
I think I found the solution, it's because the trunking setting. I reset the switch and start over again. instead making the port trunk in "switch - > vlan trunking configuration" (should be "switchport mode trunk" in CLI) , and changed the switchport mode from general to Trunk, it started to be abnormal. if I turn it on, I cannot mark the port as "T" in vlan membership. it's not about the routing I think? But this is so strange, since "switchport mode trunk" and "switchport trunk allowed vlan X" are nearly the standard command in differenct brand of switch? And I assumed that when I trunk those ports, it will be auto labelled the port as "T". In fact, It only allow either one? Since I didn't test it, i don't know which should be the correct approach to getting the trunk work?
In addition, I stacked 2 switches, one of them is standby, so I might be able to just LAG 2 ports in my layer 2 sw and do nothing in layer 3 since it seems to be a "virtual switch"?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
