When parameter changes take effect – Brocade TurboIron 24X Series Configuration Guide User Manual
Page 475
Brocade TurboIron 24X Series Configuration Guide
441
53-1003053-01
Basic IP parameters and defaults – Layer 3 Switches
Both methods allow you to filter packets based on Layer 3 and Layer 4 source and destination
information.
ACLs also provide great flexibility by providing the input to various other filtering mechanisms such
as route maps, which are used by BGP4.
IP access policies allow you to configure QoS based on sessions (Layer 4 traffic flows).
Only one of these filtering mechanisms can be enabled on a device at a time. Devices can store
forwarding information for both methods of filtering in the session table.
For configuration information,
Chapter 28, “Configuring Rule-Based IP Access Control Lists”
Basic IP parameters and defaults – Layer 3 Switches
IP is enabled by default. The following IP-based protocols are all disabled by default:
•
Routing protocols:
•
Routing Information Protocol (RIP) – refer to
•
Open Shortest Path First (OSPF) – refer to
Chapter 23, “Configuring OSPF Version 2 (IPv4)”
•
Multicast protocols:
•
Internet Group Membership Protocol (IGMP) – refer to
•
Protocol Independent Multicast Dense (PIM-DM) – refer to
•
Protocol Independent Multicast Sparse (PIM-SM) – refer to
•
Router redundancy protocols:
•
Virtual Router Redundancy Protocol Extended (VRRP-E) – refer to
•
Virtual Router Redundancy Protocol (VRRP) – refer to
Chapter 27, “Configuring VRRP and
The following tables list the Layer 3 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, refer
to 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. You can verify that a dynamic change has taken effect by
displaying the running-config. To display the running-config, enter the show running-config or write
terminal command at any CLI prompt.
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.