OSPF Interface Elements Name
search cancel

OSPF Interface Elements Name

book

Article ID: 40958

calendar_today

Updated On:

Products

CA eHealth

Issue/Introduction

 
Issue:
 
 OSPF interface element  Name is not getting updated even after manual and scheduled Auto-discovery. 
 
Environment:  
 
eHealth 6.3.1.06 on Windows 2008
 
Cause: 
 
For OSPF elements, they use two index file: index1 and index2. While eHealth creates config for OSPF elements, it thinks that OSPF elements are interface elements; so, it uses index1 to find description in ifTable and add to OSPF elements' configurating if exists. Then, because the customer sets parameter: NH_DISCOVER_IF_DESCR_IN_NAME=Yes, eHealth uses ifDescr for OSPF elements if ifDescr exists. 
 
Workaround:
 
There is hotfix for 6.3.1.06 and fix in ehealth 6.3.2.13
 
steps:
 
1. Back up and replace the file: NH_HOME/bin/sys/finder.tcl with the fix file.
 
2. Rediscover the device to update element name.
 
Note: The hot-fix is ONLY used for eHealth6.3.1.06 D0
 
 
 
Additional Information:
 
Rally Defect ticket DE155260
 
 
 

Environment

Release:
Component: EHDISC