Just noticed, looks like they even messed up the IPv4 part in
conjunction with standby IPs ...
e.g.:

    int g0/0/0
    ip add 172.20.0.10 255.255.255.0
    backup-interface g0/0/1
   
    int g0/0/1
    ip add 172.20.0.10 255.255.255.0

This config of course works fine ... attempting to add this:

    int g0/0/0
    standby 1 ip 172.20.0.1

results in:
% 172.20.0.1 overlaps with GigabitEthernet0/0/1

d'oh ... of course, after all it's the _BACKUP_ interface ... using a
different subnet would defeat the meaning of a backup interface ...

Btw, this still works in e.g. 12.4(17a) on a 7200 ...

-garry
_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to