In a case like this I find it easiest to test by creating a fake prefix list and running the command. Check whether the line was replaced, or if you get an error.
I believe that you get an error, but it's easy to safely test. If it does replace the line there is the chance of a bug which wouldn't be detected in this manner, but it's a good first step if you are wondering about how an ACL or prefix list behaves. Thanks, Josh > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Christian Koch > Sent: Thursday, February 21, 2008 3:34 PM > To: [email protected] > Subject: [c-nsp] Result of Duplicate SEQ on Prefix List > > hi all - > > if by mistake a prefix list was added with the same sequence > number, would > there be any negative result? > > the prefix list would be referenced in a route map which sets > metric for > hsrp-active/standby > > so if i have > > ip prefix-list HSRP-S seq 2 permit 10.10.10.0/27 > > and the following is added by mistake > > ip prefix-list HSRP-S seq 2 permit 10.10.11.0/24 > > would there be any impact? > > the related route maps look like this > ! > route-map ospf-connected permit 5 > match ip address prefix-list HSRP-A > set metric 50 > set metric-type type-1 > ! > route-map ospf-connected permit 10 > match ip address prefix-list HSRP-S > set metric 100 > set metric-type type-1 > ! > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
