Configuring IP

Basic IP Parameters and Defaults – Routing Switches

IP is enabled by default. The following IP-based protocols are all disabled by default:

•Route exchange protocols

•Routing Information Protocol (RIP) – see “Configuring RIP” on page 7-1

•Open Shortest Path First (OSPF) – see “Configuring OSPF” on page 8-1

•Border Gateway Protocol version 4 (BGP4) – see “Configuring BGP4” on page 10-1

•Multicast protocols

•Internet Group Membership Protocol (IGMP) – see “Changing Global IP Multicast Parameters” on page 9-2

•Protocol Independent Multicast Dense (PIM-DM) – see “PIM Dense Overview” on page 9-4

•Protocol Independent Multicast Sparse (PIM-SM) – see “PIM Sparse Overview” on page 9-12

•Distance Vector Multicast Routing Protocol (DVMRP) – see “DVMRP Overview” on page 9-39

•Router redundancy protocols

•Virtual Router Redundancy Protocol Extended (VRRPE) – see “Configuring VRRP and VRRPE” on page 12-1.

•Virtual Router Redundancy Protocol (VRRP) – see “Configuring VRRP and VRRPE” on page 12-1.

•Standby Router Protocol (SRP) – see “Configuring SRP” on page 13-1

The following tables list the routing switch IP parameters, their default values, and where to find configuration information.

NOTE: For information about parameters in other protocols based on IP, such as RIP, OSPF, and so on, see the configuration chapters for those protocols.

When Parameter Changes Take Effect

Most IP parameters described in this chapter are dynamic. They take effect immediately, as soon as you enter the CLI command or select the Web management interface option. You can verify that a dynamic change has taken effect by displaying the running-config. To display the running-config, enter the show running-configor write terminal command at any CLI prompt. (You cannot display the running-config from the Web management interface.)

To save a configuration change permanently so that the change remains in effect following a system reset or software reload, save the change to the startup-config file.

•To save configuration changes to the startup-config file, enter the write memory command from the Privileged EXEC level of any configuration level of the CLI.

•To save the configuration changes using the Web management interface, select the Save link at the bottom of the dialog. Select Yes when prompted to save the configuration change to the startup-config file on the device’s flash memory. You also can access the dialog for saving configuration changes by clicking on Command in the tree view, then clicking on Save to Flash.

Changes to memory allocation require you to reload the software after you save the changes to the startup-config file. When reloading the software is required to complete a configuration change described in this chapter, the procedure that describes the configuration change includes a step for reloading the software.

6 - 9