One problem I could see with this is that what you choose to map on a given interface is not the same as what actually exists on it. If acknowledging all mapped devices off of an interface stopped it from counting as a down interface in the switch, then we wouldn't hear about it if everything else off of that port also died. That may not mean it isn't an idea worth looking into, but it's something that comes to mind.
Ian Struckhoff
Tech Support
Dartware, LLC
On May 18, 2004, at 11:25 AM, Ashe, James P. wrote:
it would be nice (but maybe very difficult to implement) if parent devices were more knowledgeable about their child devices and didn't cause an unnecessary alarm condition.
�
for example :
�
*[intermapper]----o----[parent]----o----[child]
�
if the child goes down we see
�
*[intermapper]----o----[parent (orange)]--X--o----[child (red)]
�
cool.� we ACK the child now and get...
�
*[intermapper]----o----[parent (orange)]--X--o----[child (blue)]
�
in this case is there any reason for the parent to be in an alarm state for�'link down'�if the child is ACKd and we know the link is down to that child?
�
if there isn't and the parent were allowed to revert to an OK state it could allow the administrator to see another alarm on the device if one is present.
�
what do you think?
�
___________________________________
James P. Ashe
Systems Analyst 2
ETSU Office of Information Technology
[EMAIL PROTECTED]
OIT Help Desk - 423.439.4648
�
