Basically this warning is letting you know that once you remove a logical or sub-interface using the no interface command there is the potential for some of the previous configuration to return when re-creating the same interface. This has been an issue with Cisco IOS for years and it has yet to be fixed. ISP routers usually have multiple external paths. Once you’ve removed the interface you’ll notice a warning that not all config may have been removed and may reappear after reactivating the logical-interface/sub-interface. Telnet to router using loopback address, not interface address. %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback1, changed state to down %LINK-5-CHANGED: Interface Loopback1, changed state to administratively down % Not all config may be removed and may reappear after reactivating the logical-interface/sub-interfaces Router(config-if)# no interface loopback 1 Objective 2 request that we remove the Loopback 1 interface, you can remove loopback interfaces by negating the interface command using the no interface loopback # command as shown below If you wanted to do what you describe, then youd simply assign that IP to one of your real interfaces and turn off reverse path filtering and enable ip forwarding so it was reachable from all your real interfaces.
Router(config-if)# ip address 10.233.21.251 255.255.255.0 Loopback is the only interface that behaves that way (in contrast to other dummy interfaces such as tun/tap and bridge interfaces which are routable). As per the objective you’re required to configure the IP address 10.233.21.251/24 on this interface as shown below %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback1, changed state to upĪfter the interface is created you’ll notice the interface changes to state up instantly. Configuration shown below Įnter configuration commands, one per line. To create a loopback interface you need to navigate to global configuration mode and execute the command interface loopback # The interface is created automagically.
0 kommentar(er)
