Cisco IOS software supports multiple IP addresses per interface. You can specify an unlimited number of secondary addresses. Secondary IP addresses can be used in a variety of situations. The following are the most common applications:
* There might not be enough host addresses for a particular network segment. For example, suppose your subnetting allows up to 254 hosts per logical subnet, but on one physical subnet you must have 300 host addresses. Using secondary IP addresses on the routers or access servers allows you to have two logical subnets using one physical subnet.
* Many older networks were built using Level 2 bridges, and were not subnetted. The judicious use of secondary addresses can aid in the transition to a subnetted, router-based network. Routers on an older, bridged segment can easily be made aware that many subnets are on that segment.
* Two subnets of a single network might otherwise be separated by another network. You can create a single network from subnets that are physically separated by another network by using a secondary address. In these instances, the first network is extended, or layered on top of the second network. Note that a subnet cannot appear on more than one active interface of the router at a time.
Note: If any router on a network segment uses a secondary address, all other routers on that same segment must also use a secondary address from the same network or subnet.
problems, if any, with secondary addresses occur mainly in conjunction with routing protocols, such as OSPF, which cannot establish adjacencies on secondary addresses. Other than that, you can add as many as the software allows you to. I guess the reason why multiple secondary addresses are being used, rather than multiple logical interfaces, is that you do not have to bother with trunking, inter-VLAN routing etc. when using secondary addressing. It is just a simple way of being able to add more hosts. I would be careful, though, to not add to many hosts, since that, and especially with regard to VoIP, can cause problems with delay and dropped packets, which VoIP usually doesn't handle very well.
secondary addressing dependency in routing protocols I would add another aspect to be careful about when configuring secondary addressing: be careful that all routers on the segment agree which subnet is the primary address.
Also be aware that any packet sourced by the router from that interface will use the primary address as the source address and will not ever source anything from the secondary address.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...