Hi,
Is anyone aware of a compelling reason why we should not include eth0 in an 802.3ad bond0 (of 4 x 1Gb eth0/1/2/3) on an NB5230 master/media running v2.6.0.1?
Is it officially supported in v2.6.0.1, and also in v2.6.0.2, and going forward long term?
Thanks.
eth0 was reserved by Engineering in versions prior to 2.6.0.2. With this version, they released that reservation.
Per the 2.6.0.2 release notes, it is officially supported as of that version. If I recall correctly on 2.6.0.1, the bond will not finish creation via the CLISH if you use eth0.
I've successfully done it on a 2.6.0.2 system, however, with no issues.
Thank you.
There it is on page 18 of the v2.6.0.2 Release Notes:
"Starting with NetBackup Appliance 2.6.0.2, you can configure and use the eth0/NIC1 port to run backup jobs. If you decide to use this port for backups, you must configure the remote management (IPMI) port to access the appliance."
I'm sure I read the doc a while ago...
...just another example of an 'unknown known" on my part (i.e. forgotten stuff)
:)
Can I re-phrase... Is the use of eth0 for backup data (either standalone - OR - in a bond) officially un-supported in v2.6.0.1 ? If so, do we know why?
eth0 was reserved by Engineering in versions prior to 2.6.0.2. With this version, they released that reservation.
A cheeky finisher of a question...
What symptoms might one expect to experience on an NB5230 if one were to include eth0 in a bond (with either/any of eth1/2/3) in any, otherwise supported, appliance version prior to v2.6.0.2 ?
The configurator won't allow you to put it into a bond, but you could do it from the OS if you know how.
I have included eth0 in 802.3ad bonds since N5200 appliances back in early 2011 - and all from the CLISH
You just need to setup the other (eth1 etc.) network first, then unconfigure eth0, then bond them all - works fine.
The issue you get in the earlier releases is that if you need to make changes to domain, search domain or iP address it seems to query eth0 for certain things and gets confused .. and if you unbond and rebond it will not automatically include eth0 unless specified explicitly so leaves it out then uses the unconfigured port to lookups which no longer works - it then doesn't let you reconfigure eth0 so you get in a mess and have to use YAST to reconfigure it then start again!
But if you leave everything alone it works fine in every version of appliance software .. of course only officially supported in the latest release.
Thanks Mark.
