Writing /app/www/public/data/meta/onboarding/snmpmanager/troubleshooting_-_adding_port_number_to_ips_in_load_sheets.meta failed
onboarding:snmpmanager:troubleshooting_-_adding_port_number_to_ips_in_load_sheets

Troubleshooting - Adding port numbers to IPs in load sheets

Author: Michelle McCausland

Example Customer Request

Support,
  Pat has modified one of our load sheets to reflect port 8080 as part of the IP address. 
  This approach appears to allow us to link directly to the unit GUI, and also perform an alarm audit on the controller. 
  Would including this port as part of the IP address impact anything else being performed in the background? 
  I do not believe Errigal actively pings Commscope equipment so Hopefully this could provide a short term solution.   

Solution

Adding port 8080 to IP address can't solve issue because of the login process.

Currently it is hardcoded to use port 80.

Thus login URL SnmpManager generate would look like 'http://10.20.30.40:8080:80/“ if port number is in IP address field in network element.

Other disadvantage including port in URL is that it could break trap handling.

Our trap handing checks source IP address of the trap to determine Hub (except AIMOS alarm).

onboarding/snmpmanager/troubleshooting_-_adding_port_number_to_ips_in_load_sheets.txt · Last modified: 2021/06/25 10:09 (external edit)