For more details, please see ourCookie Policy.


Fibre Channel (SAN)

Reply
Not applicable
Posts: 1
Registered: ‎06-03-2011

Web Management interface inaccessible on Brocade SilkWorm 200E fibre switch

We recently moved a Brocade SilkWorm 200E fibre switch to a new VLAN in our Data Centre.  After the move, the web interface is not accessible anymore.  I can ping the management NIC on the switch, so I know it is online.  I think this may be due to some ACLs on the new network/VLAN.

There are ACLs to allow Ping, HTTP, and HTTPS through.  I'm thinking the ACLs block whatever port the Java switch management uses, but I can not find what port this is in any documentation.

Does anyone know which port the Java switch management app uses?

Super Contributor
Posts: 635
Registered: ‎04-12-2010

Re: Web Management interface inaccessible on Brocade SilkWorm 200E fibre switch

Hi,

are you able to login via ssh or telnet on that switch?

I think a ping test is only useful if you know that the switch IP address on the new VLAN was free and unused before you moved the switch.

As far as I know is that you only need from client to switch:

Port 22  TCP SSH SCP

Port 23 TCP Telnet

Port 80 TCP HTTP

Port 443 TCP HTTPS

Port 161 UDP SNMP

From switch to destination

Port 20 & 21 TCP FTP

Port 123 UDP NTP

Port 1812 UDP RADIUS

Port 1813 UDP RADIUS

As far as I know there are no Java ports required.

A client to DCFM is using some other ports but not the plain Webtools.

I think the best way to get out of this issue is to ask the network/firewall admin to have a look in the log files which sessions are rejected.

Best regards,

Andreas

Join the Broadcom Community

Get quick and easy access to valuable resources across the Broadcom Community Network.