Spectrum Running and Startup Configs show data reading interruption
Article ID: 189735
Updated On:
Products
CA Spectrum
CA eHealth
Issue/Introduction
Some NCM configuration read stops in the middle of the configuration.
Sometimes "running", other times "startup".
No pattern found to understand how this happens.
If they use the same commands but directly in the devices, no problems are detected when reading the configurations.
Environment
Release : 9.3
Component : Spectrum Core / SpectroSERVER
Resolution
We found that SSH process is terminating at the interface description text.
The # is used for the enable prompt but here also for interface description comments.
Internally SSH process (system process) will open a channel to the device and wait for output buffer to read the data until the next prompt comes i.e # (since in enable prompt value), so for these problematic devices ssh is terminating at between assuming interface description as the end of config which leads to capture incomplete configuration.
Recommended the customer to change interface description text not to use a # symbol.
The # is used for the enable prompt but here also for interface description comments.
Internally SSH process (system process) will open a channel to the device and wait for output buffer to read the data until the next prompt comes i.e # (since in enable prompt value), so for these problematic devices ssh is terminating at between assuming interface description as the end of config which leads to capture incomplete configuration.
Recommended the customer to change interface description text not to use a # symbol.
Feedback
Yes
No
Powered by
