Hello, I’m trying to setup a multi switch system in a daisy chain and on each end I have a layer3 connection to ISP cloud. Third location uses the same ISP cloud with layer3 connection. So the problem is we are have static routes on each and need to use a sort of redundant solution when there’s a break between switches or at either end of the daisy chain.
Please help or repost Ray A. Williams > On Aug 3, 2018, at 05:56, Bradley Ordner <[email protected]> wrote: > > Hi, > > I’m interested in how you go, we are planning a cold boot upgrade from > 7.2.0(1) (D1) to 8.2. We seem to have some BFD and Mac sec bugs. > > We attempted an ISSU update a few months back to a later 7 code and it > failed. We only have one 7K chassis per DC so can’t risk another crash. > > Do you need to update any EPLDs? the only new feature we want to use is OTV > loopbacks as join interfaces. > > Brad > > Sent from my iPhone > >> On 3 Aug 2018, at 4:26 pm, Tristan Gulyas <[email protected]> wrote: >> >> Hi all, >> >> We're testing 8.2 for the same reason (security fixes). So far, so good! >> Multi-campus LAN, 7706s for distribution, border and core routing. >> >> Tristan >> >>> On 1 Aug 2018, at 6:12 am, Charles Spurgeon <[email protected]> >>> wrote: >>> >>> * Nick Griffin <[email protected]> [2018-07-30 10:25:21 -0500]: >>>> Looking to upgrade some 7ks from 6.2.12 to something 7.2 or 7.3 to >>> support the peering of layer 3 devices across vpc port >>> channels. Looking to see what code versions others are using that >>> have proven to be stable. >>> >>> We've been running 7.3 but are moving to 8.2 to resolve the vulns >>> announced here: >>> https://tools.cisco.com/security/center/viewErp.x?alertId=ERP-67770 >>> >>> Some of the vulns listed were fixed as of 7.3(2)D1(2) and some aren't >>> fixed until 8.1/8.2 code. >>> >>> 7.3(2)D1(2) has been stable for us for 198 days of runtime on a pair >>> of 7710s with sup2e in a data center with VPC (traditional multi-tier >>> design). >>> >>> Currently we have been smoke testing 8.2 in the lab to replace the 7.3 >>> code on the next maintenance window. >>> >>> -Charles >>> _______________________________________________ >>> 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/ > _______________________________________________ > 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/
