Se le ct Bond from the T ype me nu Additional type s pe cific configuration options are appe nde d to the form.

5. Spe cify the ge ne ral inte rface s e ttings . The applicable configuration options are the s ame as for the phys ical inte rface s de s cribe d in Se ction 14.4.1, “Adding a Phys ical Inte rface ”. Bonde d inte rface s us e IDs in the form of bond0 in the Identifier fie ld. It is s ufficie nt if you s pe cify a s ingle MAC addre s s in the MAC address fie ld.

6. Spe cify the configuration options s pe cific to bonde d inte rface s :

Mode: Se le ct the bonding mode that de fine s a policy for fault tole rance and load balancing. Se e Table 14.1, “Bonding Mode s Available in Re d Hat Sate llite ” for a brie f de s cription of individual bonding mode s .

Attached devices: Spe cify a comma s e parate d lis t of ide ntifie rs of attache d de vice s . The s e can be phys ical inte rface s or VLANs .

Bond options: Spe cify a s pace s e parate d lis t of configuration options , for e xample miimon=100. The re are s e ve ral configuration options you can s pe cify for the bonde d inte rface , s e e Re d Hat Ente rpris e Linux 7 Ne tworking Guide for de tails .

7. Click OK to s ave the inte rface configuration. The n click Submit to apply the change s to the hos t.

T able 14.1. Bo nding Mo des Available in Red Hat Sat ellit e

Bo nding Mo de

Descript io n

balance -rr Trans mis s ions are re ce ive d and s e nt out s e que ntially on e ach bonde d inte rface .

active -backup Trans mis s ions are re ce ive d and s e nt out via the firs t available bonde d inte rface . Anothe r bonde d inte rface is only us e d if the active bonde d inte rface fails .

balance -xor Trans mis s ions are bas e d on the s e le cte d has h policy. In this mode , traffic de s tine d for s pe cific pe e rs will always be s e nt ove r the s ame inte rface .

broadcas t All trans mis s ions are s e nt on all bonde d inte rface s .

802.a3 Cre ate s aggre gation groups that s hare the s ame s e ttings . Trans mits and re ce ive s on all inte rface s in the active group.

balance -tlb The outgoing traffic is dis tribute d according to the curre nt load on e ach bonde d inte rface .

balance -alb Re ce ive load balancing is achie ve d through Addre s s Re s olution Protocol (ARP) ne gotiation.

14.4.4. Adding a Baseboard Management Cont roller (BMC) Int erface

Prerequisit es

Ens ure the following pre re quis ite s are s atis fie d be fore proce e ding:

BMC is e nable d on the Caps ule . If re quire d, s e e Proce dure 14.12, “To Enable BMC Powe r Manage me nt on an Exis ting Caps ule :”.

The ipmitool package is ins talle d.

You know the MAC addre s s , IP addre s s , and othe r de tails of the BMC inte rface on the hos t, and the appropriate cre de ntials for that inte rface .

Note

You only ne e d the MAC addre s s for the BMC inte rface if the BMC inte rface is manage d. This is s o that it can cre ate a DHCP re s e rvation.

Pro cedure 14.12. T o Enable BMC Po wer Management o n an Exist ing Capsule:

1. Ens ure the following line s e xis t in the /etc/foreman-proxy/settings.d/bmc.yml file . Cre ate the file if ne ce s s ary.

:enabled: true

:bmc_default_provider: your_bmc_provider 2. Re s tart the foreman-proxy s e rvice :

# service foreman-proxy restart 3. Re fre s h the fe ature s for the Caps ule .

a. Log in to the Sate llite we b UI, and navigate to Inf rast ruct ure → Capsules. b. Ide ntify the Caps ule whos e fe ature s you ne e d to re fre s h. In the drop-down

lis t on the right, click Refresh features. The lis t of fe ature s in the Features column s hould now include BMC.

Pro cedure 14.13. T o Add a BMC Int erf ace:

1. Navigate to Ho st s → All ho st s to vie w available hos ts . 2. Click Edit ne xt to the hos t you want to e dit.

3. On the Network tab, click Add Interface.

4. Se le ct BMC from the T ype me nu. Type -s pe cific configuration options are appe nde d