No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Knowledge Base

Port conflicts cause SVN3000 virtual gateway can’t add.

Publication Date:  2012-09-14  |   Views:  645  |   Downloads:  0  |   Author:  SU1000722738  |   Document ID:  EKB1000014757


Issue Description

When adding virtual gateway in SVN3000, there will be a tip: IP address and port conflict. 

Alarm Information


Handling Process

1Ccheck the other equipment configuration, there is no equipment which conflict with the SVN address;
2 Check SVN3000 configuration, found that the equipment configuration’s web management address and virtual gateway address are the same, the used port is also the default HTTPS 443 port;
3 Change web management port through using command web-manager IP X.X.X.. X port XX, and then add the virtual gateway, add successfully.

Root Cause

The possible reasons are as follows:
1 SVN and the other equipment in network existence address conflict;
2 Virtual gateway port and other application port conflict.


SVN3000 web management uses the default port 443, if management address and virtual gateway port are consistent, you’d better change web management port. You can also use another address as web management address.