Default Value: By default no loopback interfaces are created on NX-OS devices. This is described in the recommendations for each respective routing protocol. switch(config)# int loopback 0 switch(config-if)# ip address 10.11.11.1 255.255.255.252 In order to use the loopback interface (rather than the closest interface to the routing peer), it must be explicitly configured in the routing protocol. Often smaller subnets can be used for loopbacks, depending on how many potential peers are possible. Addressing the loopback, in particular computing the subnet mask will vary by the organization and application. Solution Creating the loopback interface is a simple process. Impact: Using a loopback interface makes a routing device much less susceptible to intermittent or permanent interface failures. Depending on the error condition, most physical interfaces are susceptible to interface flapping. Loopback interfaces by their nature cannot 'flap' (toggle between up and down states). This means traffic sourced from a loopback interface can take any valid path to establish a routing relationship or to route traffic. Rationale: Loopback interfaces are always up, and so are not dependent on physical interface link state issues (cabling or other link issues for instance). Routing protocol specific configurations are described under the respective routing protocols. This is obviously the shortened version of the address, and all the preceding hexadecimal characters. Therefore, in IPv6, there is only one loopback IP address and that is ::1. This recommendation describes the configuration of the loopback interface. Despite having so many IP addresses available, the IPv6 developers realized that the loopback address range used in IPv4 wasted so many IP addresses. Information The use of a loopback interface is recommended for use in all routing protocols.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |