Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

SRW* switches issues (namely, srw248g4)


Mon, 11/02/2009 - 06:41
Nov 2nd, 2009
User Badges:


Model: Linksys SRW248G4 sw.




Web interface is NOT working with IE8 (though it is said in Release notes, it works with IE5.5+). It works with IE5.5 to IE7 (though there are stilllsome bugs revealling, see below), but not with IE8. If the software gets updated at all the hosts in our LAN, we will not be able to configure the sw...

When I get to the "home.htm" page, the javascript engine tells me that
Line: 40
Error: Object expected

Msxml is installed (and is of the latest version). We have tested it with Windows server 2003 and IE8, with Windows XP and IE8... nothing helps (we have also disabled all the restrictions on active x). It just does not work.

The sw is completely unconfigurable in UNIX-only environment... as it relies at the M$ client side "technology"...

CLI functionality is very poor as it allows one to configure only some basic parameters (IP address, local users for auth). It does NOT allow to setup VLANs,*STP,any Security features, etc.

When trying to configure the sw using IE6-7, there is a bug showing up when  we  try to  add one port to many VLANs ("VLAN to Ports" page) and press "Save". The port seems to be added to VLANs but the error message is instantly showing  up  which says that some error appeared, but it doesn't know the error ID or the reason. This is really annoying. =) :


  Line No. Error Type Value Diagnostic   
       1       null       Unknown value       Might be missing parameters (join1)  in page.


We like the sw, but it is so hard to work with it, not mentioning that we have to install M$ Windows to manage it... We'd like to see it working with IE8+ and Firefox (all 3Com and Allied Telesyn sw do!), and we'd like to see more functionality in CLI interface.


And there is another bug/strange behaviour: when I set up a port to be Trunk, when after that I create a new VLAN, the port is not associated with it automagically: I have to add it MANUALLY! =) While by definition of the Trunk port type: it is assosiated with all but native VLANs in tagged mode automatically... another way, how does it differ from general mode if I HAVE to add newly created VLANs to it manually?



This Document