The "proper" way is applying your management ip address to bridge instead of ether1.
See this thread IP address in bridge or etherX which the original poster said both work. But in general you should be applying Layer 3 ip address to an interface, and once a port has been added to the bridge, it should no longer be treated as an interface; that function has been transferred to the bridge interface.
What you have may appear to work when something is plugged into ether1, but you probably won't be able to connect to 10.0.0.3 when a device isn't connected to ether1 and its link is up. However, this is only conjecture, I haven't tried and verified this myself. It is only a guess. If someone does know please speak up. I can find multiple posts where it is advised to apply ip address to interface and not a bridge port (and this makes the most sense to me), but I can't find a definitive case listed where applying to the bridge port will not work. My guess is that if that specific port is "down" then access to to ip address for other bridge members will be lost. But not verified...
However, I don't see this listed in Layer2 misconfiguration