>From the support side I always advise my customers to also get support from >the vendor. Almost all issues are down to software problems, bar a select few >where the problem is either a typo or lack of planning and understanding the >requirements.
Access to support from vendor is essential but having spares is really good practice too. Not sure on your experience but I am yet to find a company that manages to actually replace a multi-chassis router within 4 hours! Or a 1U switch for that matter! I do subscribe to the KISS principle as well! And accurate documentation on top of KISS! My 2p! Catalin Nocsult Ltd Unified Network Management Solutions Sent from my mobile device > On 23 Jan 2017, at 20:05, Jared Mauch <[email protected]> wrote: > >> On Mon, Jan 23, 2017 at 02:28:37PM -0500, Shawn L wrote: >> I guess it all depends on what you utilize support for. We tend to have >> in-house spares, etc. that we can swap in in the event of a failure. But, >> there are times when you need to talk to someone at TAC to get the bottom >> of an issue. > > These types of issues if not solved by the obligatory > upgrade to the latest software are the big value of direct vendor support. > > If you're doing vanilla IP routing features (and I do mean that, > anything that says MPLS/VPN/VRF, etc.. are not vanilla) you should be fine. > > If you have anything more complex, don't expect it to be easy. > They presume you're doing it wrong, and you must be open to that as a > concept. Remember the KISS principle. > > - Jared > > -- > Jared Mauch | pgp key available via finger from [email protected] > clue++; | http://puck.nether.net/~jared/ My statements are only mine. > _______________________________________________ > 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/
