I recently replaced a Cisco 4510 chassis that had eight FastEthernet line cards with a new Cisco 4510 that uses eight GigabitEthernet line cards.
The new chassis was given the same name and management addresses as the old, along with the same location, snmp strings, passwords, etc.
After doing a rediscovery and listing the resources, NPM still shows the old FastEthernet ports; they're grayed out. The new GigabitEthernet ports are displayed below the old FastEthernet ports.
This is a problem. NPM should automatically remove those old FastEthernet ports, and only display the actually ports present.
I've seen this when replacing other switches and routers. The only way I've seen of getting rid of removed ports is to delete the node in NPM and re-add it. Which ends up causing me to lose all the stats that are so useful for comparing performance changes in the switch, like memory and CPU and latency measurements.
Am I missing something here--is there a way to remove all the old ports without removing the stats for things that are still present, like temp and latency and CPU and memory--without deleting the old node and recreating it? If so, please let me know.
Otherwise, please vote this up. NPM is smart enough to see the new ports, and it can see the old ports are gone. It should automatically remove those old ports when we do a new Discovery of the new switch.
