NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Uplink IP
I have another curious issue. I am running multiple switches in my environment and when I look at the connected neighbors every link between the switches has a foreign IP that does not match the IP ...
I got your private message and forwarded the diagnostics file to the higher tier of NETGEAR Support to check it.
I just got feedback and it was confirmed that there are network parameters set to 169.254.0.239. This is the cause on why the switch advertise this as its Mngt IP Address. The only way to clear this is to factory reset the switch and reconfigure it. To reconfigure it, be sure to delete it from NETGEAR Insight then re-add it. Do NOT reload the configuration on the switch but be sure to reconfigure the settings via NETGEAR Insight.
Regards,
DaneA
NETGEAR Community Team
New wrinkle:
Yesterday I performed the following steps:went in and . then di.
1. removed all the switches via the phone app
2. factory reset all switches via the reset button on the switches
3. disconnected a fiber port on the LAG
4. added Core Switch via phone app
This came up with correct IP and all connected neighbors had the correct Mgmt IP
5. Added Leaf Switch
This too came up with correct IP and neighbors
6. Created LAG between Core and Leaf switch 10G sfp+ ports 27 amd 28
after this step the mgmt IP for the leaf switch reports as 169.254.0.239, and the other switch which should show a mgmt ip of 10.0.0.5 attached to port 4 of the core shows 169.254.0.239 for a mgmt IP.
So the question now becomes , Do I RMA the core switch becuase none of the steps I took resolve the issue.
Jeremyse wrote:Do I RMA the core switch becuase none of the steps I took resolve the issue.
No. Clealry a bug ref. the firmware LAG implementation.
schumakuSo basically wait until the next firmware revision? Nice.. At least with Cisco they will create a custom version for me. I guss it helps to have 4000 switches under smart net lol
Does it have any practical impact on the network operations, on the Insight management, or on some 3rd part network discovery and management tool (I know here it can cause a prom of course)? Or is it for now purely cosmetic?
Jeremyse wrote:schumakuSo basically wait until the next firmware revision? Nice..
First Netgear has to admit and understand the issue. It might be "configured" - however not intentionally and explicitly by the user. Much more it looks ot me like an automatic default.
Jeremyse wrote:At least with Cisco they will create a custom version for me. I guss it helps to have 4000 switches under smart net lol
Not a problem on switches with a very different price tag and a 20% p.a. support contract.
All valid points! Cosmetic so far, until it isn't. With this "potential bug" I don't know what I don't know hence the reason for the post. It isn't correct behavior, cosmetically speaking or not and my dhcp server is logging the IPs as invalid on the mgmt VLAN, so there is a problem although I see no impact to the traffic atm..
Thanks for the help everyone!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
