cancel
Showing results for 
Search instead for 
Did you mean: 

ICX7150-C12P is disconnected

smriti
New Contributor

switch.pngI am unable to connect to the switch in a lennar home. APs are working, switch is not showing as connected in the unleashed portal. 

 

Tried connecting through putty and mobaxterm but unable to connect..

Did an IP scanner and identified the IP with correct MAC address. But somehow unable to connect. I tried to connect directly to the laptop via the USB-C port, but unable to open either telnet/ssh/serial connection.

 

 

12 REPLIES 12

Hi @smriti 

Greetings!!!

Thank you for the response and the information you shared.

Have you tried to log in using the default credentials?

If not, could you please try to log into the Switch on the web browser using the default credentials?

Switch default credentials will be as mentioned below.

Username: super

Password: sp-admin

If the above credentials don’t work, you can try the default credential combinations as well.

If any of the above credentials don’t work, please try to factory reset the RUCKUS ICX-7150-C12P Switch as described in the below VIDEO and once you perform the reset try to login with the above-mentioned default credentials again.

VIDEO link: https://www.youtube.com/watch?v=6jHMTdo_hK4

Please let me know if you have any queries in this regard.

Thank you again. We appreciate your patience and understanding.

 

Best regards,

Imran Sanadi

RUCKUS Lennar Home Community.

smriti
New Contributor

Hello Imran,

Current status - Switch is still shows disconnected from the unleashed.ruckus portal. Inte rnet speed from APs is subpar even though I have 1 GB fiber connection. Ip Scanner doesn't showing the Switch ip in network

I tried reset again and still there is no luck. I tried with the default credentials and it is not working.

However I was able to connect via console and took a boot capture. I am attaching the log here. Please take a look and let me know if you can figure something out from the log.

 

Ruckus Wireless Bootloader: 10.1.15T225 (Jan 30 2019 - 23:08:47 -0800)

Booted from partition 1
DRAM:  Validate Shmoo parameters stored in flash ..... OK

ICX7150-12 (POE), PVT1
SYS CPLD VER: 0x4 Released Ver: 0xa
Writing Shmoo values into flash .....

device 0 offset 0xbfe00, size 0x200
device 0 offset 0x0, size 0xc0000
Enter 'b' to stop at boot monitor:  0
device 0 offset 0x0, size 0xc0000
bootdelay: ===
Booting image from Primary

NAND read: device 0 offset 0x0, size 0x2000000
1 ecc_errors after reading 1b48000:1b48000
iproc_nand_read_page returned 2
NAND read from offset 0 failed -22
 0 bytes read: ERROR
## Loading kernel from FIT Image at 70000200 ...
Bad FIT kernel image format!
ERROR: can't get kernel image!
could not boot from primary, no valid image; trying to boot from secondary
device 0 offset 0x0, size 0xc0000
BOOTING image from Secondary

NAND read: device 0 offset 0x4000000, size 0x2000000
 33554432 bytes read: OK
## Loading kernel from FIT Image at 70000200 ...
   Using 'conf@1' configuration
   Trying 'kernel@2' kernel subimage
     Description:  Ruckus Linux MN VER=08.0.90d
     Type:         Kernel Image
     Compression:  lzma compressed
     Data Start:   0x7024fa14
     Data Size:    2401258 Bytes = 2.3 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x61008000
     Entry Point:  0x61008000
     Hash algo:    crc32
     Hash value:   ac67d750
## Loading kernel from FIT Image at 70000200 ...
   Using 'conf@1' configuration
   Trying 'kernel@2' kernel subimage
     Description:  Ruckus Linux MN VER=08.0.90d
     Type:         Kernel Image
     Compression:  lzma compressed
     Data Start:   0x7024fa14
     Data Size:    2401258 Bytes = 2.3 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x61008000
     Entry Point:  0x61008000
     Hash algo:    crc32
     Hash value:   ac67d750
   Verifying Hash Integrity ... crc32+ OK
## Loading ramdisk from FIT Image at 70000200 ...
   Using 'conf@1' configuration
   Trying 'ramdisk@1' ramdisk subimage
     Description:  Ramdisk -rootfs
     Type:         RAMDisk Image
     Compression:  lzma compressed
     Data Start:   0x704a07b4
     Data Size:    27682307 Bytes = 26.4 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x00000000
     Entry Point:  0x00000000
     Hash algo:    crc32
     Hash value:   011bd5e3
   Verifying Hash Integrity ... crc32+ OK
## Loading fdt from FIT Image at 70000200 ...
   Using 'conf@1' configuration
   Trying 'fdt@3' fdt subimage
     Description:  Flattened Device Tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x7049e55c
     Data Size:    8607 Bytes = 8.4 KiB
     Architecture: ARM
     Hash algo:    crc32
     Hash value:   6fc9a37b
   Verifying Hash Integrity ... crc32+ OK
   Loading fdt from 0x7049e55c to 0x65008000
   Booting using the fdt blob at 0x65008000
   Uncompressing Kernel Image ... OK
   Using Device Tree in place at 65008000, end 6500d19e

Starting kernel ...

Mounting file system...
booting with 4.4 kernel
NAND Type: Micron NAND 2GiB (x 1)
PLATFORM MN
dd cmd: UBI
Config partition mounted
Resource partition is mounted!!
Processing packages from secondary partition
Installed packages are up to date
Starting up system statistics daemon...
Starting systatsd done
Starting up health monitor daemon...
Log Level 7: Daemonized systatsd
Systatsd Logging Env is not set, initializing loglevel to: 7
Setting connection to systemlogger
Starting hmond done
Hmond Logging Env is not set, initializing loglelvel to: I
Setting connection to systemlogger
Backup is fine
Kernel crashdump is disabled.
dma_mem_base: 0x96000000, dma_mem_len: 0x8000000, warm_mem_base: 0x9f500000, warm_mem_len: 0xb00000
Creating TUN device
Starting TPM Infra
Group tss and User tss created
kernel.hostname = localhost
hostname set to localhost
Starting TCSD Daemon
TCSD Up and Running
Enabling time stamp.
Starting the FastIron.
USER=root
boot_partition=sec_partition
HOME=/
GCOV_PREFIX=/fast_iron
ethaddr=dc:ae:eb:2e:7e:0b?
TERM=vt102
PATH=/sbin:/usr/sbin:/bin:/usr/bin
crashkernel=64M@0x70000000
ip=10.14.145.172:10.14.144.14:10.14.144.1:255.255.254.0:MN:eth0:off
SHELL=/bin/sh
PWD=/
i2c-0   i2c             Broadcom iProc I2C adapter              I2C adapter     2
i2c-1   i2c             Broadcom iProc I2C adapter              I2C adapter     2
FIPS Disabled:PORT NOT DISABLED
platform type 90
OS>
Loaded Image SPR08090d from Sec Built on (UTC): Mon Sep 23 07:08:29 2019
Uboot and FI booted from different partitions, Uboot: Primary, FI: Secondary
Auto correcting the cross boot combination... going for auto reboot now
Auto Sampling :    enabled
Min Time      :   250
CPU Sampling d[   67.080146] [BrcdSoftlockup]: root e501cd80 is not a valid rb_tree
isabled.
Stopping health monitor daemon...
Stopped health monitor daemon
Stopping system statistics daemon...
Stopped systatsd.
Saving the configuration and license files...
Backup is fine
The system is going down NOW!
Sent SIGTERM to all processes
[   68.789981] [BrcdSoftlockup]: sim_softwatchdog thread is detached on core=0
Sent SIGKILL to all processes
Requesting system reboot
[   70.690339] reboot: Restarting system
[   70.734236] Asserting GHPIO[7] reset sequence from Kernel ...


Ruckus Wireless Bootloader: 10.1.15T225 (Jan 30 2019 - 23:08:47 -0800)

Booted from partition 2
DRAM:  Validate Shmoo parameters stored in flash ..... OK

ICX7150-12 (POE), PVT1
SYS CPLD VER: 0x4 Released Ver: 0xa

device 0 offset 0xbfe00, size 0x200
device 0 offset 0x0, size 0xc0000
Enter 'b' to stop at boot monitor:  0
device 0 offset 0x0, size 0xc0000
bootdelay: ===
Booting image from Secondary

NAND read: device 0 offset 0x4000000, size 0x2000000
 33554432 bytes read: OK
## Loading kernel from FIT Image at 70000200 ...
   Using 'conf@1' configuration
   Trying 'kernel@2' kernel subimage
     Description:  Ruckus Linux MN VER=08.0.90d
     Type:         Kernel Image
     Compression:  lzma compressed
     Data Start:   0x7024fa14
     Data Size:    2401258 Bytes = 2.3 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x61008000
     Entry Point:  0x61008000
     Hash algo:    crc32
     Hash value:   ac67d750
## Loading kernel from FIT Image at 70000200 ...
   Using 'conf@1' configuration
   Trying 'kernel@2' kernel subimage
     Description:  Ruckus Linux MN VER=08.0.90d
     Type:         Kernel Image
     Compression:  lzma compressed
     Data Start:   0x7024fa14
     Data Size:    2401258 Bytes = 2.3 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x61008000
     Entry Point:  0x61008000
     Hash algo:    crc32
     Hash value:   ac67d750
   Verifying Hash Integrity ... crc32+ OK
## Loading ramdisk from FIT Image at 70000200 ...
   Using 'conf@1' configuration
   Trying 'ramdisk@1' ramdisk subimage
     Description:  Ramdisk -rootfs
     Type:         RAMDisk Image
     Compression:  lzma compressed
     Data Start:   0x704a07b4
     Data Size:    27682307 Bytes = 26.4 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x00000000
     Entry Point:  0x00000000
     Hash algo:    crc32
     Hash value:   011bd5e3
   Verifying Hash Integrity ... crc32+ OK
## Loading fdt from FIT Image at 70000200 ...
   Using 'conf@1' configuration
   Trying 'fdt@3' fdt subimage
     Description:  Flattened Device Tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x7049e55c
     Data Size:    8607 Bytes = 8.4 KiB
     Architecture: ARM
     Hash algo:    crc32
     Hash value:   6fc9a37b
   Verifying Hash Integrity ... crc32+ OK
   Loading fdt from 0x7049e55c to 0x65008000
   Booting using the fdt blob at 0x65008000
   Uncompressing Kernel Image ... OK
   Using Device Tree in place at 65008000, end 6500d19e

Starting kernel ...

Mounting file system...
booting with 4.4 kernel
NAND Type: Micron NAND 2GiB (x 1)
PLATFORM MN
dd cmd: UBI
Config partition mounted
Resource partition is mounted!!
Processing packages from secondary partition
Installed packages are up to date
Starting up system statistics daemon...
Starting systatsd done
Starting up health monitor daemon...
Log Level 7: Daemonized systatsd
Systatsd Logging Env is not set, initializing loglevel to: 7
Setting connection to systemlogger
Starting hmond done
Hmond Logging Env is not set, initializing loglelvel to: I
Setting connection to systemlogger
Backup is fine
Kernel crashdump is disabled.
dma_mem_base: 0x96000000, dma_mem_len: 0x8000000, warm_mem_base: 0x9f500000, warm_mem_len: 0xb00000
Creating TUN device
Starting TPM Infra
Group tss and User tss created
kernel.hostname = localhost
hostname set to localhost
Starting TCSD Daemon
TCSD Up and Running
Enabling time stamp.
Starting the FastIron.
USER=root
boot_partition=sec_partition
HOME=/
GCOV_PREFIX=/fast_iron
ethaddr=dc:ae:eb:2e:7e:0b?
TERM=vt102
PATH=/sbin:/usr/sbin:/bin:/usr/bin
crashkernel=64M@0x70000000
ip=10.14.145.172:10.14.144.14:10.14.144.1:255.255.254.0:MN:eth0:off
SHELL=/bin/sh
PWD=/
i2c-0   i2c             Broadcom iProc I2C adapter              I2C adapter     2
i2c-1   i2c             Broadcom iProc I2C adapter              I2C adapter     2
FIPS Disabled:PORT NOT DISABLED
platform type 90
OS>
Loaded Image SPR08090d from Sec Built on (UTC): Mon Sep 23 07:08:29 2019
Enabling Console Logging
Hotplugger Daemon Initialized ..
External USB disk is not mounted or plugged in.
set_board_level: gi_board_type = 116[   65.729339] linux-kernel-bde: map phys range 0x3200000-0x3240000 to 0xb0b2f000-0xb0b6f000
[   65.973863] linux-kernel-bde: map phys range 0x88100000-0x90100000 to 0xa8b2f000-0xb0b2f000
DMA pool size: 134217728
                        PHY Reset De-asserted
sw_pp_sdk_init:136 ToR init
SOC unit 0 attached to PCI device BCM56160_B0
Firmware version from File: 2.1.1
Pre Parsing Config Data ...

Done with Pre-allocating nexthop id's for Unicast & Openflow
Warning: This operation would close all existing SSH connection.
Parsing Config Data ...
Error! 1/3/1 speed is 1G. A stack-port needs at least 10G speed.
Error! 1/3/2 speed is 1G. A stack-port needs at least 10G speed.
Invalid input ->address 192.168.1.15 255.255.255.0 dynamic
Type ? for a list
Invalid input ->default-gateway 192.168.1.1 dynamic
Type ? for a list

Going to sleep forever...
                         System initialization completed...console going online.
  Copyright (c) Ruckus Networks, Inc. All rights reserved.
    UNIT 1: compiled on Sep 23 2019 at 00:00:25 labeled as SPR08090d
      (32539748 bytes) from Secondary SPR08090d.bin (UFI)
        SW: Version 08.0.90dT213
      Compressed Secondary Boot Code size = 786944, Version:10.1.15T225 (mnz10115)
       Compiled on Thu Jan 31 07:08:55 2019

  HW: Stackable ICX7150-C12-POE
==========================================================================
UNIT 1: SL 1: ICX7150-C12-2X1G POE 12-port Management Module
      Serial  #:FEK3841R1FR
      Software Package: ICX7150_BASE_L3_SOFT_PACKAGE
      Current License: 2X1G
      P-ASIC  0: type B160, rev 11  Chip BCM56160_B0
==========================================================================
UNIT 1: SL 2: ICX7150-2X1GC 2-port 2G Module
==========================================================================
UNIT 1: SL 3: ICX7150-2X10GF 2-port 20G Module
==========================================================================
 1000 MHz ARM processor ARMv7 88 MHz bus
 8192 KB boot flash memory
 2048 MB code flash memory
 1024 MB DRAM
STACKID 1  system uptime is 9 second(s)
The system started at 00:03:42 GMT+00 Sat Jan 01 2000

The system : started=cold start



Press Enter key to login

 Successfully notified stack role 'none' to hmond


Creating certificate, please wait...

SSL Client Certificate is successfully created


Press Enter key to login

PS 1, Internal Power supply  detected.
PS 1, Internal Power supply  is up.
PoE: Stack unit 1 PS 1, Internal Power supply  with 124000 mwatts capacity is up
PoE Info: Adding new 54V capacity of 124000 mW, total capacity is 124000, total free capacity is 124000
PoE Info: PoE module 1 of Unit 1 on ports 1/1/1 to 1/1/12 detected. Initializing....
2000 log entries of PoE Event Trace Log Buffer is allocated on unit 1 for unit 1
PoE Event Trace Logging enabled for unit 1
PoE Info: PoE module 1 of Unit 1 initialization is done.
PoE: Power enabled on port 1/1/1.
PoE: Power enabled on port 1/1/2.
TFTP session timed out
TFTP session timed out
TFTP session timed out
TFTP session timed out
TFTP session timed out
TFTP session timed out
TFTP session timed out
TFTP session timed out
TFTP session timed out
TFTP session timed out


User Access Verification

Please Enter Login Name: super
Please Enter Password:
User login failure.



Press Enter key to login


User Access Verification

Please Enter Login Name: admin
Please Enter Password:
User login failure.



Press Enter key to login


User Access Verification

Please Enter Login Name: admin
Please Enter Password:
User login failure.



Press Enter key to login


User Access Verification

Please Enter Login Name: admin
Please Enter Password:
User login failure.



Press Enter key to login


User Access Verification

Please Enter Login Name: admin
Please Enter Password:
User login failure.



Press Enter key to login


User Access Verification

Please Enter Login Name: admin
Please Enter Password:
User login failure.



Press Enter key to login


User Access Verification

Please Enter Login Name: admin
Please Enter Password:
User login failure.



Press Enter key to login


User Access Verification

Please Enter Login Name: admin
Please Enter Password:
User login failure.



Press Enter key to login


User Access Verification

Please Enter Login Name: admin
Please Enter Password:

 

 

Hi @smriti 

Greetings!!!

Thank you for the response and the update.

If you are unable to access to CLI using the console, please perform the software recovery process as described below.

Below is the Guide and Video Link to perform the Software recovery process:

Please refer to the below guide and Video link: 

https://community.ruckuswireless.com/t5/RUCKUS-Support-for-Lennar-Homes/How-to-perform-a-Software-re...

Video Link: https://www.youtube.com/watch?v=Ql22blH_CGo

Please note, we must use ethernet cable (both ends RJ45 plugs) and USB to type C cable both together as described in steps 2 & 3 in the guide link.

Please let me know if you have any queries in this regard.

Thank you again for your patience.

 

Best regards,

Imran Sanadi

RUCKUS Lennar Home Community.