FI 6248 console setup, invalid subnet mask

[yitung]

After erase configuration from FI 6248 console and setup again...

I failed to enter the subnet mask... Any idea what went wrong??
 

  Enter the configuration method. (console/gui) ? console
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.

  Enter the setup mode; setup newly or restore from backup. (setup/restore) ? setup

  You have chosen to setup a new Fabric interconnect. Continue? (y/n): y

  Enforce strong password? (y/n) [y]: n

  Enter the password for "admin":
  Confirm the password for "admin":

  Is this Fabric interconnect part of a cluster(select 'no' for standalone)? (yes/no) [n]:

  Enter the system name:  FI

  Physical Switch Mgmt0 IP address : 192.168.0.1

  Physical Switch Mgmt0 IPv4 netmask : 255.255.255.0
    Invalid subnet mask.Physical Switch Mgmt0 IPv4 netmask :     Invalid IPv4 form. Should be of form 'X.X.X.X', where each
    letter corresponds to a decimal number between 0 and 255.
  Physical Switch Mgmt0 IPv4 netmask :
  Physical Switch Mgmt0 IPv4 netmask : 255.0.0.0
    Invalid subnet mask.Physical Switch Mgmt0 IPv4 netmask :     Invalid IPv4 form. Should be of form 'X.X.X.X', where each
    letter corresponds to a decimal number between 0 and 255.
  Physical Switch Mgmt0 IPv4 netmask : 255.255.255.0
    Invalid subnet mask.Physical Switch Mgmt0 IPv4 netmask :     Invalid IPv4 form. Should be of form 'X.X.X.X', where each
    letter corresponds to a decimal number between 0 and 255.
  Physical Switch Mgmt0 IPv4 netmask :
  Physical Switch Mgmt0 IPv4 netmask : 255.255.0.0
    Invalid subnet mask.Physical Switch Mgmt0 IPv4 netmask :     Invalid IPv4 form. Should be of form 'X.X.X.X', where each
    letter corresponds to a decimal number between 0 and 255.

[Walter Dey]

Which UCS version ?

Do you really want to setup a standalone configuration ?

Did you try e.g. 192.168.10.1 ?

[yitung]

I'm using ucs-6100-k9-system.5.2.3.N2.2.23d.bin

using 192.168.10.1 still fail to enter subnet mask... I also tried to use an old version: ucs-6100-k9-system.5.0.3.N2.2.03a.bin but no luck...

  Enter the configuration method. (console/gui) ? console
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.

  Enter the setup mode; setup newly or restore from backup. (setup/restore) ? setup

  You have chosen to setup a new Fabric interconnect. Continue? (y/n): y

  Enforce strong password? (y/n) [y]: n

  Enter the password for "admin":

  Confirm the password for "admin":

  Is this Fabric interconnect part of a cluster(select 'no' for standalone)? (yes/no) [n]:

  Enter the system name:  fia

  Physical Switch Mgmt0 IPv4 address : 192.168.10.1

  Physical Switch Mgmt0 IPv4 netmask : 255.255.255.0
    Invalid subnet mask.Physical Switch Mgmt0 IPv4 netmask :

[yitung]

is there a way to bypass the initial setup?? I can break and log into the boot mode and change the int mgmt 0 directly...

[Walter Dey]

Are you connected to the console port ?

What kind of terminal emulation program are you using ?

Was there a configuration before you did a erase configuration ? or is this a brand new FI ?

[yitung]

HI Walter,

Yes, I connected to console.

I tried putty or teraterm.

There was a configuration before. It works very fine before.

It's my internal lab equipment. I just did erase configuration for some other testing. It's NOT a brand new FI.

Anything can help to recover it?? I can't open TAC as it's just internal lab equipment only.

[yitung]

Hi Walter and Saurabh,

It works after rebuild the FI using init system.

Thanks a lot!!

Chris.

[Saurabh Kothari]

Chris,

that did the trick. :)

thanks

[Walter Dey · Accepted solution]

http://jeffsaidso.com/2013/01/when-disaster-strikes/

might be useful as well; just for next time :-)

[yitung]

This is exactly the URL I follow to resolve my issue. :D

Thanks a lot!!

[Saurabh Kothari · Accepted solution]

is this a new setup?  a new FI?

Error occurs because the management file ucs-manager-k9*** didn't load properly. 

I believe the FI needs to be rebuild from scratch, please open a TAC case.

-Saurabh

[yitung]

HI Saurabh,

It is NOT new equipment. It works fine before. I just did erase configuration and want to do some other testing.

It is in my internal lab so no TAC support it.

Do you have any way to rebuild it from scratch?? I can try myself.

Many Thanks!

Chris.