The /etc/rc file in the root volume contains ifconfig commands to configure network interfaces, including virtual interfaces, at system boot. You can also manually use the ifconfig command when the system is operating.
The ifconfig command syntax is as follows:
ifconfig <interface>
[ [ alias | -alias ] <address> ] [ up | down ]
[ netmask <mask> ] [ broadcast <address> ]
[ mtusize <size> ] [ mediatype <type> ]
[ trusted | untrusted ] [ wins | -wins ]
[ partner | -partner <address> ]
You use the ifconfig command for the following purposes:
The following examples show configuring an Ethernet interface and a virtual interface on a filer:
ifconfig e1 292.9.299.6
ifconfig e2 netmask 255.255.0.0
ifconfig e3 broadcast 292.9.299.255
The interface names on your system might be different, depending on your filer model. For information about interface naming conventions, refer to "Naming conventions for network interfaces."
The following example show configuring an Ethernet interface on a filer:
ifconfig e1 mediatype tp
The media types you can use depend on the type of Ethernet card. The possible types you can enter in the ifconfig command are the same as those you can select when running setup. They are described in the following table.
| Media type | Description |
|---|---|
| 100tx | 100Base-T |
| 100tx-fd | 100Base-T, full-duplex |
| tp | 100Base-T |
| tp-fd | 10Base-T, full-duplex |
| auto | 100Base-T/100Base-TX Ethernet using Auto-Negotiation |
| 1000fx | Gigabit Ethernet |
The following example shows setting the MTU for an FDDI interface:
ifconfig f0 mtusize 1500
The following table lists the default MTU sizes.
| Interface | Default MTU size |
|---|---|
| FDDI | 4352 |
| Ethernet | 1500 |
| Gigabit Ethernet | 1500 |
| ATM | 9188 |
Use a smaller MTU value for an interface if a bridge or router on the attached network cannot break large packets into fragments.
To view the current setting of the MTU value, use the following command:
netstat -i
The following example illustrates how to configure interfaces up and down:
ifconfig e1a up
ifconfig f1 down
ifconfig virt_interface up
Within a cluster, each filer must have one or more interfaces configured with its partner's IP address. The filer uses the interface configured with its partner IP address to serve data while in takeover mode. The following terms relate to IP addresses in clusters.
Partner IP addresses can be configured to use dedicated standby interfaces, or they can be configured to shared interfaces.
Partner IP addresses must be configured to use interfaces on the same subnetwork as the partner.
The following example shows how to configure two filers to assume each other's identities during takeovers using dedicated interfaces.
The following commands entered on the toaster1 console do the following tasks:
ifconfig e1 198.9.200.28
ifconfig e2 partner 198.9.200.38
The following commands entered on the toaster2 console do the following tasks:
ifconfig e1 198.9.200.38
ifconfig e2 partner 198.9.200.28
The following example shows how to configure two filers to assume each other's identities during takeovers using shared interfaces.
The following commands entered on the toaster1 console do the following tasks:
ifconfig e1 198.9.200.28
ifconfig e1 partner 198.9.200.38
The following commands entered on the toaster2 console do the following tasks:
ifconfig e1 198.9.200.38
ifconfig e1 partner 198.9.200.28
If you want changes made with ifconfig to remain in effect after a reboot, include the ifconfig commands in the /etc/rc file.
The following table illustrates examples of how to use the ifconfig command to view interface configuration information.
For more information about the ifconfig command, refer to the na_ifconfig(1) man page.
Copyright © 1999, Network Appliance, Inc. All rights reserved.
Part No. 210-02334
File: net5.htm
Last updated: 04/26/99 08:11:18