This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Missing or Incorrect EoL/EoS Data

As a part of the effort to make the EoL/EoS feature (available with NCM 7.2) as useful as possible, we would like to ask you to report any devices where our data is missing, incorrect, or the suggestions are misleading. We will do our best to incorporate your feedback into NCM.

Note: If applicable please provide the EoL/EoS in the following form:

Device Type, System description, end-of-sale date, end-of-support date, Vendor EOL statement URL

Thanks,

Jiri

Parents
  • One big problem with the current implementation of EOL in our environment is the reporting of switch stacks.  You want to be able to configure switch stacks as one element - that's why you stack them.  But EOL needs to be on the individual stack members which may have different EOL dates. (for instance, Cisco 3570-X and 3570-E switches can stack together, be presented in NCM as one unit, but have different EOL dates)

    Please consider breaking out the EOL dates for switch stacks down to the stack member level.

    That said the EoL/EoS info in NCM for the 37xx switch stacks pulls up the ancient 3700 series router as the suggestion.  Here is the correct info for 3750-G, 3560-G, 3750-E, and 3560-E switches:

    Cisco Catalyst 3750G, 3560G, 3750-E, and 3560-E Series Switches; January 30, 2013; January 31, 2018; End-of-Sale and End-of-Life Announcement for the Cisco Catalyst 3750G, 3560G, 3750-E, and 3560-E Series Switches

  • I agree, i am doing so much work on EOL/EOS for the last year all my data is from the Physical Entities (inventory) table/s. This really needs to be considered and is really key for the future.

    Please see myu post here:

Reply Children
No Data