Configuring IP Addressing
Loopback Interfaces
N o t e
■
You can use a loopback interface to establish a Telnet session, ping the
switch, and access the switch through SNMP, SSH, and HTTP (web
interface).
■
A loopback IP address can be used by routing protocols. For example,
you can configure the loopback IP address as the router ID used to identify
the switch in an OSPF area. Because the loopback interface is always up,
you ensure that the switch's router ID remains constant and that the OSPF
network is protected from changes caused by downed interfaces.
OSPF does not require that you use an IP address as the router ID. OSPF only
requires the router ID to be a unique value within the autonomous system
(AS). However, if you configure the loopback IP address as the router ID,
OSPF can reach the switch if any switch interface is up. (Normally, OSPF
automatically configures the router ID with the IP address of a switch inter
face. The disadvantage is that if the interface goes down, OSPF can no longer
ping the switch using the router ID even if other interfaces are operational.)
For more information about how to configure a loopback IP address to
participate in an OSPF broadcast area, refer to the section titled “(Optional)
Assigning Loopback Addresses to an Area” in the
Multicast and Routing
Guide
.
Configuring a Loopback Interface
To configure a loopback interface, enter the
interface loopback
command at
the global configuration level of the CLI:
Syntax:
[no] interface loopback <
number
>
Creates a loopback interface, where
<number
> is a value from
1 to 7. Use the
no
form of the command to remove the loopback
interface.
Note:
You cannot remove the default loopback interface
(number 0) with IP address 127.0.0.1.
You can configure up to thirty-two IP addresses on a loopback interface. To
configure an IP address for the loopback interface, enter the
ip address <
ip
address
>
command at the loopback interface configuration level as shown in
the following example.
Note that when you configure an IP address for a loopback interface, you do
not specify a network mask. The default subnet mask 255.255.255.255 is used.
8-16
Summary of Contents for ProCurve 1600M
Page 1: ...Management and Configuration Guide 8200zl ProCurve Switches K 12 XX www procurve com ...
Page 2: ......
Page 3: ...ProCurve Series 8200zl Switches September 2007 K 12 xx Management and Configuration Guide ...
Page 68: ...Using the Menu Interface Where To Go From Here 3 16 ...
Page 110: ...Using the ProCurve Web Browser Interface Status Reporting Features 5 26 ...
Page 152: ...Switch Memory and Configuration Multiple Configuration Files 6 42 ...
Page 220: ...Time Protocols SNTP Messages in the Event Log 9 28 ...
Page 252: ...Port Status and Configuration Uni Directional Link Detection UDLD 10 32 ...
Page 282: ...Power Over Ethernet PoE Operation PoE Operating Notes 11 30 ...
Page 472: ...Redundancy Switch 8212zl Event Log Messages 15 48 ...
Page 584: ...Monitoring and Analyzing Switch Operation Locating a Device B 74 ...
Page 652: ...Troubleshooting Restoring a Flash Image C 68 ...
Page 660: ...MAC Address Management Viewing the MAC Addresses of Connected Devices D 8 ...
Page 666: ...Monitoring Resources When Insufficient Resources Are Available E 6 ...
Page 670: ...Daylight Savings Time on ProCurve Switches F 4 ...
Page 688: ...18 Index ...
Page 689: ......