NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
vesso
Oct 15, 2018Aspirant
Problems with VRRP interface tracking on M4300-28G
Dear community,
I am trying to set up VRRP on two M4100-28G with latest firmware 12.0.7.7.
I have set up 3 IP based VLAN networks and I am trying to run VRRP in all directions.
There is no prob...
- Oct 29, 2018
Firmware is upgraded and I did have proper access to the switch. I just prefer the web GUI instead of CLI. Unfortunately what you suggested isn't working. I kepp getting the same error.
However my colleagues manage to fihish with this problem. The just create another vlan which includes the interface we want to track. Thus one and the same interface is part of two vlans. After this in vvrp tracking they include the vlan which include only the interface we care about and the magic happens.
I would like to close this post as solved!
vesso
Oct 24, 2018Aspirant
HI,
I have tried your solution using the web interface, because I am not able to get CLI access right now.
Unfortunately I got error when I have tried to use the interface instead of vlan when the vrrp is created.
What else can I try?
JohnC_V
Oct 25, 2018NETGEAR Moderator
The manual that I provided also includes the setup for the admin page(GUI). Please make sure that your PC is part of the management VLAN.
Regards,
- vessoOct 25, 2018Aspirant
Thank you for the reply!
Can you please explain me what do you mean when you say that my pc should be on the management VLAN?
I followed exactly the manual that you provided. Plus the hole vrrp setup is quit easy and I got yur point right away. I am did not follow only one of the recomendations that one of the routers must have the same IP address as the Virtual IP address.
Could this be the reason?
While we our discussion is going I saw that there is alredy firmware with number 12.0.7.8 will it make any diference if I switch to it?
- JohnC_VOct 26, 2018NETGEAR Moderator
Switch has a default management VLAN 1. If the management VLAN is changed, then you should connect the PC where the management VLAN is. If you haven't change anything related to management VLAN, then you may connect your PC to any port that is under VLAN 1. You may also upgrade the firmware of the switch so that we may know if it's a kind of bug or something.
Regards,
- vessoOct 29, 2018Aspirant
Firmware is upgraded and I did have proper access to the switch. I just prefer the web GUI instead of CLI. Unfortunately what you suggested isn't working. I kepp getting the same error.
However my colleagues manage to fihish with this problem. The just create another vlan which includes the interface we want to track. Thus one and the same interface is part of two vlans. After this in vvrp tracking they include the vlan which include only the interface we care about and the magic happens.
I would like to close this post as solved!
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!