Some monitoring and logging tools report issues they spot by IP addresses. What your CI's let you do is start at that point and then look at the tree of related CI's to see what is behind the IP. If you've populated the CMDB well enough, you could know servers and apps and affected user groups quickly. If you remove your IP endpoints, you'll have to manually look them up to find the server and then return to the CMDB to see the tree again.
If 130K CI's are causing performance issues, it is probably because of the way they are being used rather than their existence in the CMDB. Look to how they are presented to the user. Is someone doing a query that returns them all? Is the UI used too crude to allow chunking or a narrowing of a search? -al -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Koyb P. Liabt Sent: Tuesday, June 18, 2013 10:05 AM To: arslist@ARSLIST.ORG 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"
smime.p7s
Description: S/MIME cryptographic signature
