If you are planning on modeling all the way down to the NIC/IP level there is probably value in keeping them. We had this discussion and decided to stop importing them and their relationships to hosts.
Which brings up another discussion: For every CI there is at least one relationship CI that ties them together. Once you start multiplying them, you may find that you have closer to 500,000 CIs. You can still discover them with ADDM, just don’t sync them with the CMDB. AS stated earlier … if you are having performance issues with a couple of thousand CIs there may be bigger issues. Remedy is scalable to hundreds of millions of CIs as long as it is architected correctly. Are you running a separate database server? Are you running server group with distributed processes? .: Mike T :. From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Koyb P. Liabt Sent: Tuesday, June 18, 2013 12:05 PM To: [email protected] Subject: LAN Endpoint, NICs Remove? ** Hi All, For performance reasons, our Manager is talking about removing all the NIC device CIs info from the CMDB because there are 130,000 NIC CIs that we loaded into the CMDB from another repository. The NIC info we are discovering includes attributes such as: Default Gateway, DHCP Server, DNS domain, IP Address, MAC address, IP Subnets, DHCP Enabled (yes/no), Host Name, IP Enabled, product classification, etc.. Remedy is being used for incident management, change management, asset management, BSM, Analytics, configuration management, SRM, etc… This is still a relatively new implementation and has not matured. I need to communicate the value of keeping this NIC CI data or the value of removing this data. Does anyone have any suggestions? The Manager was asking “Why do we need to see the MAC address/IP Address in Remedy? What value is this for support or our business? – I can go to another system if I need this MAC/IP address. How does this help?” The next step would be to stop discovering NICs /network devices from ADDM also. No one has introduced Remedy to the Network team. The server team has not really been educated on the Remedy tool either. The tool has been mainly used for submitting tickets for incident/change. I explained many points of why we need this data. However I would like to know your thoughts. How is this network data critical/valuable to our business? _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
