CSM has always been catching up with the Device Cli.
Devices have there own limited realms in which they think.
Firewalls for instance think only in terms of security/firewalling.
A Router primarily thinks only in terms of Routing.
An IPS is just literate about the Signatures and logs.
CSM is a confluence where all these various and vivid devices and technologies are exposed as a one single mesh of complicated yet easy to understand Computer Networks.
CSM does posses a vast understanding of the various device technologies, Its the primary moto of the CSM to hide the vividness and variedness of the devices from the users.
To be the CSM CSM has been dreaming for years now CSM seeks the help and support of the devices.
CSM should not only just go through the PRD of its own and suggest enhancements for the device teams.
CSM should:
1. Take up the PRD lists of various devices
2. Analyze the PRDs.
3. Prepare a consolidated PRD listing the various requirements on various devices.
4. Register a proposal with the device teams on the actual design and implementation of the feature listed in this consolidated PRD.
This way CSM can make sure that all the Network devices think in a unified way.
This brings in the added benefit of not dealing with inconsistent behaviors of various devices.
But this model also adds up gargantuan amounts of work on part of CSM.
CSM should expand its knowledge to understand the requirements of customers, not only of CSM but also of various devices.
Having spoken of the additional responsibilities the Management of CSM has to take, lets think of what extra mid-night oil an engineer has to sacrifice.
1. An Engineer should understand the Cisco Devices well.
2. An Engineer has to address the issues customers face with the Cisco Devices, by subscribing to various forums.
3. An Engineer atleast should subscibe the forums on Network Discussions in a read-only mode.
4. An Engineer should get involved in the Customer discussions. Or the Engineer should demand for such a knowledge.
