Fibre Channel (SAN)

Reply
Contributor
Posts: 56
Registered: ‎09-14-2009

Chassis is not ready for management now. Please try after some time.

I am having this issue with a 48000 director with FW 6.2.0g after adding it to the Fabric. There are 30 switches in the fabric and all are accessible via telnet.

Webtools works on all but the 48000 which says "Chassis is not ready for management now. Please try after some time." I have seen the post for the 4100 that had the same problem, but never saw that it was solved. Should I do the following

switch:root> /fabos/libexec/webdconfigure 
HTTP attributes (yes, y, no, n): y     set to y
HTTP Restart (yes, y, no, n): y        set to y
HTTP enabled (yes, y, no, n):         is enabled.
ErrorLog Enabled (yes, y, no, n):   
AccessLog Enabled (yes, y, no, n):   
SSLLog Enabled (yes, y, no, n):   
HTTP Port: (1..60000)   
Secure HTTP Port: (1..60000)   
HTTP IsAlive Check Enabled (yes, y, no, n):     is set to yes
HTTP Max HeapSize: (256..1024)   
webtools attributes (yes, y, no, n):   
cal attributes (yes, y, no, n):  

log as root and try "hareboot"

External Moderator
Posts: 4,973
Registered: ‎02-23-2004

Re: Chassis is not ready for management now. Please try after some time.

Your must set the swich as enable and then reboot the switch whit the command "hareboot" after the webdconfigure is change.

TechHelp24
Contributor
Posts: 56
Registered: ‎09-14-2009

Re: Chassis is not ready for management now. Please try after some time.

Just to clarify a couple of things...

The switch did not have to de disabled to do this but all of the steps required being logged in as "root".

The procedure must be done on the active CP.

The fabric was not interupted during this process.

Thanks for the help....

External Moderator
Posts: 4,973
Registered: ‎02-23-2004

Re: Chassis is not ready for management now. Please try after some time.

Andy,

and what say that to me ?

you wrote:

--->>> I have seen the post for the 4100 that had the same problem, ...

exact, the Old Treads you have see here in the community was based on the 4100.

Concerning the 4100 don't have any Standby CP but a single embedded CP was not necessary to "spend here any word" of Active or Standby.

--->>> The switch did not have to de disabled...

According you preview Post, i thought they have set the switch of Disable.

--->>>...all of the steps required being logged in as "root".

exact what is posted in the old threads, "log as root"

TechHelp24
Contributor
Posts: 56
Registered: ‎09-14-2009

Re: Chassis is not ready for management now. Please try after some time.

Not sure what you are trying to say Techhelp....

In the original 4100 post it referenced the "configure" command which as written would have been executed as "admin" and later in the post is says to log in as "root" to execute the "hareboot" command.  The "configure" command does not let you restart the HTTP server but your way did. Since my 48000 does have active and standy CP's, I thought I would make it clear on how to fix this problem when working on a 48000.

Thank you for your help, it did fix the problem.....

Cheers..

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.