SpectroSERVER Performance Dumps showing CsPort::check_port and CsPort::check_device

Products

• Spectrum

Issue/Introduction

SpectroSERVER Generated Perfomance dumps, contents have many lines referencing CsPort::check_port // CsPort::check_device 

Example:

#382 0x00007ffbeb466dde in CsPort::check_port(CsPort&) () from /opt/SPECTRUM/lib/../SS/libadcor.so.1
#383 0x00007ffbeb466ea7 in CsPort::check_device(CsPort&) () from /opt/SPECTRUM/lib/../SS/libadcor.so.1
#384 0x00007ffbeb466dde in CsPort::check_port(CsPort&) () from /opt/SPECTRUM/lib/../SS/libadcor.so.1
#385 0x00007ffbeb466ea7 in CsPort::check_device(CsPort&) () from /opt/SPECTRUM/lib/../SS/libadcor.so.1
#386 0x00007ffbeb466dde in CsPort::check_port(CsPort&) () from /opt/SPECTRUM/lib/../SS/libadcor.so.1
#387 0x00007ffbeb466ea7 in CsPort::check_device(CsPort&) () from /opt/SPECTRUM/lib/../SS/libadcor.so.1

Cause

Legacy Landscape Setting for High Port Count Threshold which is default set to 1000. Port Reconfigurations on devices that have more than 1000 ports will generate performance dumps.

This is no longer utilized for Huge Landscapes and can be disabled. 

To confirm discovered device port counts, check <SpectroServerName>_DevPortinfo.txt file in perfcollector results.

Resolution

On the VNM Model, set Handle High Port Count to No



**Note** - This should only be done on landscapes using huge landscape