19 Posts

March 13th, 2006 17:00

interface port-channel 1
spanning-tree disable
exit
interface range ethernet g(8-10,14-16)
spanning-tree disable
exit
interface port-channel 1
description LAG_to_Servers
exit
interface ethernet g3
description Uplink_to_DCSW003
exit
interface ethernet g4
description Uplink_to_DCSW004
exit
interface ethernet g5
description Uplink_to_DCSW005
exit
interface ethernet g6
description Uplink_to_DCSW006
exit
interface ethernet g7
description Uplink_to_DCSW007
exit
interface ethernet g8
description Uplink_to_DCSW008
exit
interface ethernet g9
description Uplink_to_DCSW009
exit
interface ethernet g10
description Uplink_to_DCSW010
exit
interface ethernet g15
description Uplink_to_DCFW001
exit
interface ethernet g15
speed 100
exit
interface ethernet g16
description Uplink_to_DCRT001
exit
interface ethernet g16
speed 10
exit
interface ethernet g24
description Uplink_to_Sniffer
exit
interface port-channel 1
switchport mode trunk
exit
interface range ethernet g(3-10)
switchport mode trunk
exit
vlan database
vlan 5,7-21,30,200
exit
interface ethernet g3
switchport trunk allowed vlan add 5
exit
interface ethernet g16
switchport access vlan 7
exit
interface ethernet g11
switchport access vlan 8
exit
interface ethernet g8
switchport trunk allowed vlan add 9
exit
interface ethernet g24
switchport access vlan 10
exit
interface range port-channel 1
switchport trunk allowed vlan add 10
exit
interface range ethernet g(3,5,10)
switchport trunk allowed vlan add 11
exit
interface range ethernet g(3,5,10)
switchport trunk allowed vlan add 12
exit
interface range ethernet g(3,10)
switchport trunk allowed vlan add 13
exit
interface range ethernet g(7,10)
switchport trunk allowed vlan add 14
exit
interface range ethernet g(9-10)
switchport trunk allowed vlan add 15
exit
interface range ethernet g(7,10)
switchport trunk allowed vlan add 16
exit
interface range ethernet g(6,10)
switchport trunk allowed vlan add 17
exit
interface range ethernet g(4-5,10)
switchport trunk allowed vlan add 18
exit
interface range ethernet g(6,10)
switchport trunk allowed vlan add 19
exit
interface range ethernet g(6,10)
switchport trunk allowed vlan add 20
exit
interface range ethernet g(7,10)
switchport trunk allowed vlan add 21
exit
interface ethernet g15
switchport access vlan 200
exit
interface vlan 5
name IS
exit
interface vlan 7
name Router
exit
interface vlan 8
name ipSAN
exit
interface vlan 9
name Printers
exit
interface vlan 10
name Servers
exit
interface vlan 11
name Marketing
exit
interface vlan 12
name Prog_Management
exit
interface vlan 13
name Construc_Admin
exit
interface vlan 14
name Corporate
exit
interface vlan 15
name Interiors
exit
interface vlan 16
name Engineering
exit
interface vlan 17
name Admins
exit
interface vlan 18
name Architects
exit
interface vlan 19
name Execs
exit
interface vlan 20
name Conf_Rooms
exit
interface vlan 21
name Accounting
exit
interface vlan 30
name Contractor
exit
interface vlan 200
name Firewall
exit
interface range ethernet g(1-2)
channel-group 1 mode on
exit
interface vlan 1
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 5
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 7
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 8
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 9
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 10
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 11
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 12
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 13
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 14
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 15
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 16
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 17
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 18
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 19
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 20
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 21
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface vlan 30
no ip igmp snooping mrouter learn-pim-dvmrp
exit
interface range ethernet g(3-10,14-16)
no negotiation
exit
interface port-channel 1
no negotiation
exit
interface vlan 1
ip address 10.51.51.1 255.255.255.0
exit
interface vlan 5
ip address 10.51.5.1 255.255.255.0
exit
interface vlan 7
ip address 10.51.7.2 255.255.255.248
exit
interface vlan 8
ip address 10.51.8.1 255.255.255.0
exit
interface vlan 9
ip address 10.51.9.1 255.255.255.0
exit
interface vlan 10
ip address 10.51.10.1 255.255.255.0
exit
interface vlan 11
ip address 10.51.11.1 255.255.255.0
exit
interface vlan 12
ip address 10.51.12.1 255.255.255.0
exit
interface vlan 13
ip address 10.51.13.1 255.255.255.0
exit
interface vlan 14
ip address 10.51.14.1 255.255.255.0
exit
interface vlan 15
ip address 10.51.15.1 255.255.255.0
exit
interface vlan 16
ip address 10.51.16.1 255.255.255.0
exit
interface vlan 17
ip address 10.51.17.1 255.255.255.0
exit
interface vlan 18
ip address 10.51.18.1 255.255.255.0
exit
interface vlan 19
ip address 10.51.19.1 255.255.255.0
exit
interface vlan 20
ip address 10.51.20.1 255.255.255.0
exit
interface vlan 21
ip address 10.51.21.1 255.255.255.0
exit
interface vlan 30
ip address 172.17.30.2 255.255.255.0
exit
interface vlan 200
ip address 192.168.200.97 255.255.255.248
exit
ip route 0.0.0.0 0.0.0.0 192.168.200.98 
ip route 10.0.0.0 255.0.0.0 10.51.7.1 
ip route 172.16.0.0 255.255.0.0 10.51.7.1 
ip route 172.16.51.0 255.255.255.0 192.168.200.98 
ip route 192.152.137.0 255.255.255.0 10.51.7.1 
ip route 192.168.0.0 255.255.0.0 10.51.7.1 
ip dhcp relay address 10.51.10.100
ip dhcp relay enable
hostname DCSW001
line console
exec-timeout 5
exit
line ssh
exec-timeout 5
exit
line telnet
exec-timeout 5
exit
no ip domain-lookup
no logging console
username admin password 54b53072540eeeb8f8e9343e71f28176 level 15 encrypted
ip ssh server
snmp-server community analog ro 10.1.10.20 view Default
ip https server

March 13th, 2006 17:00

Are you still seeing this problem?  Can you post your config?  I'm assuming you can access from CLI and you can configure from CLI correct?
 
Cuong.

19 Posts

March 13th, 2006 18:00

When I do a show user a user shows up for HTTP that I was never aware of.  How do I disconnect it?

19 Posts

March 13th, 2006 18:00

I can access the switch through SSH and SNMP polls, no problem.  I logged in through SSH again and typed in ip http server and the same error appeared.

March 13th, 2006 18:00

I don't see anything wrong with the config relating to user setup.  Do the other management interfaces work?  Can you get to CLI/SNMP from the same workstation you are trying to access the web?  You still see the error message you posted earlier when trying to change to "ip http server"? 

I just now tried enabling/disabling my web server while the user is connected and processing request (you can see if you have a user connected on HTTP by doing a "show user") and it let me disable the http server fine and re-enable it again.

I'm not sure what the problem you are seeing is.  Any other symptom or information you can provide to reproduce the problem?

Cuong.

March 14th, 2006 12:00

Unfortunately there is no way to get rid of that session.  This problem happens sometime when a session is closed incorrectly because an application crashes or the client system is shutdown abnormally (probably the client workstation connecting to the switch web server).  I've seen this on Unix systems where a socket get stuck if the application that opens the socket dies or is killed.  It probably happens also on Windows but I'm not sure (I'm strictly a Unix programmer :-)).  In cases like this the socket gets stuck and will eventually times out but it may take days on a Unix system (depending on certain setting in the Kernel).  Now the 6024 is not running on Unix, it is running on VxWorks so I'm not sure how long it will be before that socket times out if it ever does.  I will report this problem to the development team in charge of this switch.

BTW, I've been trying to reproduce your connection problem and the error you see but I'm unable to.  I can be logged into the switch and performing all kind of web based queries and operations and yet still be able to disable/enable the web interface on the switch.  I can even perform an operation and then disable the web server in the middle of the operation without any problem.  I wonder if there is something special about the way that socket is stuck.  I'm not sure how to cause a stuck session so I'm not able to observe the condition.

Cuong.

19 Posts

March 14th, 2006 12:00

Thanks for looking into this.  I'm going to schedule a reboot of the switch and see if that clears the extra HTTP session.  I think your diagnosis is spot-on.  Obviously some HTTP session was not closed properly when this switch was first setup.  I will post the results after the reboot is complete.

June 14th, 2007 17:00

Hi,
 
I have 4 6024 switches and I've notice this problem. It started when I setup the OOB port to access the router-switch. I am wondering if Dell will fix this issue some day.
 
Thank you

909 Posts

June 15th, 2007 14:00

The new command is:
 
console# clear ip http sessions
 
This will help you to continue without a reboot.

June 15th, 2007 14:00

Hi,
 
Thank you for your reply. I am running the last version already. The problem is that when I try the command to clear the session, the router crashes... I've tried in two different 6024 I have and both crash with the following message in the log file:
 
 %OS-F-MEMORY: OSMEMG_rn_free: Memory magic is invalid^M ^M ***** FATAL ERROR ***** ^M Reporting Task: GOAH.^M Software Version: 2.0
.0.15 (date  21-Jan-2007 time  12:05:42)^M 0x7be48^M 0x7be68^M 0x7dd18^M 0x405e8c^M 0x2c6a9c^M 0x2c6f64^M 0x2cab74^M 0x2cac7c^M 0x4099f4^M 0xdd42c^M 0xcef10^
M 0xced3c^M 0xccfdc^M 0xccabc^M 0xcca28^M 0xca804^M 0xca748^M 0xd5240^M 0x6156c^M
 
Any ideas?
 
Thanks again.

1 Message

June 14th, 2013 08:00

Although the last message in this thread was written six years ago and no one ever acknowledged the crash information reported in Artur Bittencourt's message, I figured I would update the thread.

 

We have a Dell PowerConnect 6024 where the HTTP, HTTPS, and SSH daemons have all locked up.  I was able to issue the "no ip ssh server" then "ip ssh server" command to fix the SSH problem, but issuing the "no ip http server" and "no ip https server" commands generated the same response that started this thread: "While The embedded web server is busy handling page requests - configuration can not be changed".

 

At the time this thread started, the latest firmware for this switch was 2.0.0.15, A04, released in 2007.  The last version was 2.0.0.19, A05 released in 2009 (although the binary has an embedded date of 05-May-2008):

http://www.dell.com/support/drivers/us/en/04/DriverDetails?driverId=R211151

 

The crash/reboot that Artur previously reported also occurs in 2.0.0.19, A05, so it looks like Dell never fixed this problem.  Here's the command sequence and other data from when I performed the procedure this morning:

 

d6024# show version
SW version    2.0.0.19 ( date  05-May-2008 time  16:33:30 )
Boot version    1.0.0.13 ( date  13-Aug-2003 time  15:28:31 )
HW version    00.01.64

d6024# configure
d6024(config)# no ip https server
While The embedded web server is busy handling page requests - configuration can not be changed
d6024(config)# exit
d6024# show users

   Username       Protocol          Location
--------------- ------------ -----------------------
                    SSH           10.0.0.10

d6024# clear ip http sessions
This command will discontinue all HTTP/S sessions.
Do you want to continue? (Y/N):emotion-45: Y
Please close all browser sessions connected to the device.
Please confirn that all browser sessions connected to the device are closed. (Y/N):emotion-45:

The switch crashed and rebooted itself the moment I typed "y" on the last confirm (misspelled as "confirm") request.

Since I performed the "clear ip http sessions" command from an SSH session rather than the serial console, I didn't see the detailed crash data, however the "show logging file" command included the following:

14-Jun-2013 08:09:58 :%SYSLOG-F-OSFATAL:

EXCEPTION OCCURRED in task WBSR: DATA_STORAGE exception

***** FATAL ERROR *****

This is exception number -1 in this board.

SW Version  :  2.0.0.19
Version Date:  05-May-2008
Version Time:  16:33:30

Although I'm not expecting anymore firmware/software releases for the 6024, I wanted to document this information anyway in case anyone else runs into this situation and doesn't know that the "clear ip http sessions" causes the switch to crash even with the latest firmware (at least while the HTTP/HTTPS server is locked up).  I don't know if the command causes a crash when the HTTP/HTTPS server is not currently locked up.

Josh

 

No Events found!

Top