1. start fixing the million (or so) broken links in cisco.com ... most of the time finding info within is very-time consuming
2. avoid using a thousand words when a couple of words will give you the message; in other words, keep it simple
... most of the time you feel the tech documentation is written by the marketing department
3. don't invent stupid terms such as Online Insertion & Removal (OIR) for something universally known as hot-swap; you're funny but don't cry later when everybody tells you learning Cisco tech is a steepy process; it is ... definetly
We are sorry there are so many broken links. The doc groups are working to resolve them as they are identified to us in reports, and we get an updated report every week.
Keeping it simple and removing the âfluffâ is important. Tech docs is working on specific guidelines to trim down docs going forward without removing valuable content.
As for Cisco terminology, tech docs also wants clear and concise terms. The reasons behind terminology decisions are not always available to us. However, we do try to work with product teams on terminology as we can.
There are few interoperability issues between 2960x and other vendors.
In this article we will go over the steps on how to debug these issues.
Check the phy id from “show controllers ethernet-controller phy” output.
It appears that you are trying to access end of life information from
Cisco search. We have detected a problem with your script ("eol...) and
would like to help. Please contact email@example.com if you would
Cisco Licensing is pleased to announce the new Licensing Portal. It
provides customers with an enhanced self-service experience by
stream-lining and automating many licensing activities. Please take a
moment to familiarize yourself with the features that ...