IP Subnet Zero

-


When you work with classical subnetting, you always have to eliminate the subnets that contain either all zeros or all ones in the subnet portion. Hence, you always used the formula 2N 2 to define the number of valid subnets created. However, Cisco devices can use those subnets, as long as the command ip subnet-zero is in the configuration. This command is on by default in Cisco IOS Software Release 12.0 and later; if it was turned off for some reason, however, you can re-enable it by using the following command:
Router(config)#ip subnet-zero
 Now you can use the formula 2N rather than 2N - 2.
2NNumber of total subnets created 
2N 2Number of valid subnets createdNo longer needed because you have the ip subnet-zero command enabled
2HNumber of total hosts per subnet 
2H 2Number of valid hosts per subnet 

Comments

Post a Comment

Popular posts from this blog

REVERSE TELNET ON AUX PORT

-
  Requirement :   Need   to   configure   reverse telnet   via   AUX   port. Connect one router's aux port to another device's console port, and telnet to the router.Use reverse telnet to connect to the other device's console via your aux port   Setup   :   Here's how to set it up. 1.       Connect your router's aux port to another device's console port using a Cisco flat crossover cable. 2.       Telnet to your router, enable, and set the aux port up as follows:   R1#conf t R1(config)# line aux 0 R1(config-line)# modem InOut R1(config-line)# transport preferred all R1(config-line)# transport input all R1(config-line)# transport output all R1(config-line)# end 3.       Make sure you have an address on your lo0 interface, and the interface is up. R1#conf t R1(config)#int   lo0 R1(config-if)#ip   add   127.0.0.1 255.255.255.0 Execution : 1)       Come back in enable mode, find out the line number of your AUX port with “show   line”. It will look something l
Read more

Disabling Unneeded Services

-
Step 1: Configure the Physical Interface Because this lab uses only one router, you will simulate an active FastEthernet connection by activating the interface and applying the no keepalive command to initiate an “always up” state, regardless of the existence of a device at the remote end. Normally, you would not use the no keepalive command on a routed interface, except in special circumstances. In this lab, you will use it only for simulation purposes. Configure the R1 physical interface using the IP address shown in the topology diagram. Use the no keepalive command in interface configuration mode, and then use the no shutdown command to activate the interface. Because you have disabled keepalives, the interface status displays as link state (Layer 1) and line protocols state (Layer 2) “up,” even if it is not connected to an external device. R1(config)# interface fastethernet0/0 R1(config-if)# ip address 192.168.10.1 255.255.255.0 R1(config-if)# no keepalive R1(config-if)# no s
Read more