27.11.2012 Views

IronPort - advanced configuration guide

IronPort - advanced configuration guide

IronPort - advanced configuration guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

NIC Pairing and VLANs<br />

NIC Pair Naming<br />

7-4<br />

Cisco <strong>IronPort</strong> AsyncOS 7.6 for Email Advanced Configuration Guide<br />

Chapter 7 Advanced Network Configuration<br />

NIC pairing is not available on C1x appliances or M-Series appliances. Some C3x, C6x, and X10x<br />

appliances contain a fiber optic network interface option. If available, you will see two additional<br />

ethernet interfaces (Data 3 and Data 4) in the list of available interfaces on these appliances. These<br />

gigabit fiber optic interfaces can be paired with the copper (Data 1, Data 2, and Management) interfaces<br />

in a heterogeneous <strong>configuration</strong>.<br />

VLANs (see Virtual Local Area Networks (VLANs), page 7-8) are only allowed on the primary<br />

interface.<br />

When creating NIC pairs, you must specify a name to use to refer to the pair. NIC pairs created in<br />

versions of AsyncOS prior to version 4.5 will automatically receive the default name of ‘Pair 1’<br />

following an upgrade.<br />

Any alerts generated regarding NIC pairing will reference the specific NIC pair by name.<br />

Configuring and Testing NIC Pairing/Teaming<br />

NIC Pairing and Existing Listeners<br />

Once you have verified your ethernet media setting, use the etherconfig command to configure NIC<br />

pairing. You will be prompted for a name to use to refer to the pair.<br />

The failover sub-command switches the active interface. The system will not automatically switch<br />

back to the primary NIC when it comes back on line and the backup interface will remain active in that<br />

case until you explicitly switch the system back over to the primary NIC (by using the failover<br />

command) or unless the backup NIC has a failure. See Using the failover Subcommand for NIC Pairing,<br />

page 7-6.<br />

Use the delete subcommand to remove NIC pairs.<br />

When configuring NIC pairing, keep in mind that all <strong>configuration</strong> changes require a commit, except for<br />

failover. The failover command force a failover during the next polling interval which is every 15<br />

seconds once NIC pairing <strong>configuration</strong> has been committed.<br />

If you enable NIC pairing on an interface that has listeners assigned to it, you are prompted to either<br />

delete, reassign, or disable all listeners assigned to the backup interface.<br />

OL-25137-01

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!