Its pretty shweet to see an entire subnet bound to a network interface of a server. Yup, it shows 29 usable IPv4 addresses! But now its time to bite fingernails, and once they're all sufficiently bleeding, cross said fingers, endure the pain, and whitenuckle the keyboard as we hope the server comes back up talking to the network, as the network bridge is about to be configured, and only one IP will be bound to the server's interface, leaving the other 28 IPs for virtual machines, which will attach to the bridge.
@adam Well, good luck getting that br0 up and running, changing network config over ssh is always a fun thing to do. Not sure if your server has an IPMI interface, but if it does I’d highly suggest configuring that first, especially Serial Over LAN. This way you’ll still have access to the server even if your NIC fails to come up after your changes.
@robin_kipp Definitely a good point there. They claim it has a dedicated IPMI interface, but the only access I'm finding so far is a stupid, inaccessible, useless web-based console interface. But I think your point is just so true and valid, that I probably should put in a support ticket and get the serial over LAN configured, if they'll let me do that, prior to rebooting with the bridge config.
@adam And as for setting up SOL, that’s something you would need to do on the server. I unfortunately can’t remember the exact steps, but it comes down to figuring out which TTY device the IPMI controller is bound to, and then setting up console redirection to that device.