alexandr_potkin's profile

7 Messages

 • 

170 Points

Mon, Nov 1, 2021 5:17 AM

Ruckus ICX 7150

Hello everyone!

Need help. Some strange with my ICX7150. When I try firmware 09.0 get error with RADIUS TLS. When switch are boots see in log:

cp: can't stat '/.pkg/libpam/etc/*': No such file or directory
Creating TUN device
Creating the first Tap interface
ERROR: Failure in gw add
Starting TPM Infra
Group tss and User tss created
hostname set to Ruckus-ICX
Starting TCSD Daemon in 'fi' namespace
TCSD Up and Running
Enabling time stamp.
Setting Unix datagram queue len.
 Setting TCP keep alive params
Moving app to flash....
could not read config file /etc/radsecproxy.conf
                                                No such file or directory
                                                                         could not read config file /etc/radsecproxy.conf

So can't log in by RADIUS...

Employee

 • 

26 Messages

 • 

392 Points

3 m ago

Hello, alexandr_potkin.

As a workaround, I recommend going back to the original version and restoring the switch to factory defaults, deleting the configuration. Then move to the new version and configure new the switch again.

I would suggest opening a ticket with Ruckus TAC for further digging into this issue.

25 Messages

 • 

598 Points

3 m ago

Please upgrade your switch to  09.0a the  09.0  its not a full image 

7 Messages

 • 

170 Points

3 m ago

Unfortunatelly, all of this methods doesn't work

Employee

 • 

26 Messages

 • 

392 Points

3 m ago

Dear alexandr_potkin, 

Please file a new case with Ruckus TAC.

We'll be happy to look at this deeper.

We'll need the full booting log in a text file for our analysis and some configuration backup.

7 Messages

 • 

170 Points

@orlando_elias

Can You giev me a URL for a TAC, please? 

Employee

 • 

26 Messages

 • 

392 Points

This is the one:

https://support.ruckuswireless.com/

--

Orlando Elias

Ruckus TAC

3 Messages

 • 

80 Points

2 m ago

could not read config file /etc/radsecproxy.conf
                                                No such file or directory
                                                                         Creating TUN device

etc...

Why this messages comes in everytime we rebbot.. ?

7 Messages

 • 

170 Points

@jain_jose Everytime when devices boots

3 Messages

 • 

80 Points

2 m ago

Kernel crashdump is disabled.
cat: can't open '/proc/cmdline': No such file or directory
ln: /lib/libpam.so: File exists
ln: /lib/libpam.so.0: File exists
ln: /lib/libpam_misc.so.0: File exists
ln: /lib/libpam_misc.so: File exists
ln: /lib/libtac.so: File exists
ln: /lib/libtac.so.2: File exists
ln: /lib/libtac.so.2.0.0: File exists
cp: can't stat '/.pkg/libpam/etc/*': No such file or directory
starting console application
could not read config file /etc/radsecproxy.conf
                                                No such file or directory
                                                                         Creating TUN device
Creating the first Tap interface
ERROR: Failure in gw add
Starting TPM Infra
Group tss and User tss created
hostname set to Ruckus-ICX
Starting TCSD Daemon in 'fi' namespace
TCSD Up and Running
Enabling time stamp.
Setting Unix datagram queue len.
 Setting TCP keep alive params
Moving app to flash....
could not read config file /etc/radsecproxy.conf
                                                No such file or directory
                                                                         /.pkg/usr/lib/python3.7/site-packages/google/protobuf/descriptor_pool.py:172: RuntimeWarning: Conflict register for file "conf_archive.proto": START_SESSION is already defined in file "rcm.proto"
Note: enum values appear as siblings of the enum type instead of children of it.
  warnings.warn(warn_msg, RuntimeWarning)
/.pkg/usr/lib/python3.7/site-packages/google/protobuf/descriptor_pool.py:172: RuntimeWarning: Conflict register for file "conf_archive.proto": CONTINUE_SESSION is already defined in file "rcm.proto"
Note: enum values appear as siblings of the enum type instead of children of it.
  warnings.warn(warn_msg, RuntimeWarning)
/.pkg/usr/lib/python3.7/site-packages/google/protobuf/descriptor_pool.py:172: RuntimeWarning: Conflict register for file "conf_archive.proto": END_SESSION is already defined in file "rcm.proto"
Note: enum values appear as siblings of the enum type instead of children of it.
  warnings.warn(warn_msg, RuntimeWarning)
could not read config file /etc/radsecproxy.conf
                                                No such file or directory
                                                                         could not read config file /etc/radsecproxy.conf
                                                                                                                         No such file or directory
                                                                                                                                                  could not read config file /etc/radsecproxy.conf
     No such file or directory
                              Starting the FastIron.
Thu Jan  1 00:04:03 UTC 1970:Starting the FastIron.
rm: can't remove 'dlogger.boot': No such file or directory
                                                          cp: can't stat '/fast_iron/dlogger.boot': No such file or directory

[  270.731041] linux-kernel-bde: map phys range 0x3200000-0x3240000 to 0xb4412000-0xb4452000
[  270.916357] linux-kernel-bde: map phys range 0x88100000-0x90100000 to 0xac300000-0xb4300000
Oct 09 10:18:23:170736:info:fi_debug:debug_logs:0:0:
Loaded Image SPR09000a from Sec Built on (UTC): Sat Oct  9 16:44:43 2021
Oct 09 10:18:40:547080:info:fi_debug:debug_logs:0:0:
Hotplugger Daemon Initialized ..
Oct 09 10:18:40:731508:info:fi_debug:debug_logs:0:0: set_board_level: gi_board_type = 117
Oct 09 10:18:43:409465:info:fi_debug:debug_logs:0:0: PHY Reset De-asserted
Oct 09 10:18:43:409616:info:fi_debug:debug_logs:0:0: sw_pp_sdk_init:141 ToR init
Oct 09 10:18:43:459806:info:fi_debug:debug_logs:0:0: SOC unit 0 attached to PCI device BCM56160_B0
Oct 09 10:18:45:456186:info:fi_debug:debug_logs:0:0: license: SAU option 3 from license file
Oct 09 10:18:45:456485:info:fi_debug:debug_logs:0:0: Info: SendEventCommon: scp task Not inited by FI
Oct 09 10:18:46:344273:info:fi_debug:debug_logs:0:0: Pre Parsing Config Data ...
Oct 09 10:18:46:351309:info:fi_debug:debug_logs:0:0:
Oct 09 10:18:46:354144:info:fi_debug:debug_logs:0:0: Successfully registered appl with the SHMDM
Oct 09 10:18:46:355393:info:fi_debug:debug_logs:1:0: Init start
Oct 09 10:18:48:905078:info:fi_debug:debug_logs:1:0:
Done with Pre-allocating nexthop id's for Unicast & Openflow
Oct 09 10:18:54:243830:info:fi_debug:debug_logs:1:0: Successfully registered mgmt messages.
Oct 09 10:18:54:246538:info:fi_debug:debug_logs:1:0: Successfully registered mgmt callbacks.
Oct 09 10:18:54:249497:info:fi_debug:debug_logs:1:0: Successfully registered pysagt_helper messages.
Oct 09 10:18:54:251931:info:fi_debug:debug_logs:1:0: Successfully registered pyszagt_helper callbacks.
Oct 09 10:18:54:498608:info:fi_debug:debug_logs:1:0: ND6-Init: neighbor table max limit set to 4096
Oct 09 10:18:54:518892:info:fi_debug:debug_logs:1:0: SCP RegisterEvent: Index=0 Event=80
Oct 09 10:18:54:519380:info:fi_debug:debug_logs:1:0: SCP RegisterEvent: Index=1 Event=87
Oct 09 10:18:54:685814:info:fi_debug:debug_logs:1:0: Successfully registered mgmt with the SHMDM
Oct 09 10:18:55:365192:info:fi_debug:debug_logs:1:0: CfgSync HMON Start returned: 7
Oct 09 10:18:55:366198:info:fi_debug:debug_logs:1:0: Cfg Parse Start...
Oct 09 10:18:56:022618:info:fi_debug:debug_logs:1:0: da_mgmt_register_ssrf_client: Registration success
Oct 09 10:18:56:321577:info:fi_debug:debug_logs:1:0: App Rx Event: 79 F1: 0 F2: 0 Sl:0
Register the thread with the shm_init_app call
Oct 09 10:18:57:929074:info:fi_debug:debug_logs:1:1529643795200:
PS 1, Internal Power supply  detected.
Oct 09 10:18:57:929290:info:fi_debug:debug_logs:1:1529643795200: PS 1, Internal Power supply  is up.
Oct 09 10:18:57:929487:info:fi_debug:debug_logs:1:1529643795200: Stack unit 1 Power supply 1 is up
Oct 09 10:19:11:805423:info:fi_debug:debug_logs:1:4808770304: App Rx Event: 136 F1: 1 F2: 0 Sl:0
Oct 09 10:19:11:805566:info:fi_debug:debug_logs:1:4808770304: Cfg Parse Done. All-task initialization completed...final phase of system initialization started.
Oct 09 10:19:11:805654:info:fi_debug:debug_logs:1:4808770304: Parse Time in Secs: 16
Starting config parsing time: [Sat Oct  9 10:18:57 2021]
Starting upgrade ...
Upgrade done with exit status: 0
Config parsing complete: 1.45 percent time: 00:13 parsed: [ver 09.0.00aT213]
DHCP client has been turned off on all other VEs and is running on all interfaces belonging to VE 1
Error - DHCP client on VE default is already enabled
Error [1 1] parsing line: [ip dhcp-client ve default]
Config parsing complete: 100.00 percent time: 00:14 parsed: [end]
Finished config parsing time: [Sat Oct  9 10:19:11 2021] Elapsed time: 00:14
Oct 09 10:19:13:045514:info:fi_debug:debug_logs:1:4808770304:
Successfully notified stack role 'none' to hmond
Oct 09 10:19:13:076148:info:fi_debug:debug_logs:1:4808770304:
Oct 09 10:19:13:191099:info:fi_debug:debug_logs:1:9225372929: Optics detected on 1/3/1
Oct 09 10:19:13:272963:info:fi_debug:debug_logs:1:9225372929: Physical     start:0 ---- end3583
Oct 09 10:19:13:273111:info:fi_debug:debug_logs:1:9225372929: Mgmt         start:24 ---- end24
Oct 09 10:19:13:273196:info:fi_debug:debug_logs:1:9225372929: Virtual      start:3584 ---- end3711
Oct 09 10:19:13:273264:info:fi_debug:debug_logs:1:9225372929: Lpback       start:3712 ---- end3743
Oct 09 10:19:13:273326:info:fi_debug:debug_logs:1:9225372929: Lag          start:3072 ---- end3584
Oct 09 10:19:13:273386:info:fi_debug:debug_logs:1:9225372929: mcast tunn   start:3744 ---- end3775
Oct 09 10:19:13:799150:info:fi_debug:debug_logs:1:4808770304:
******* Starting HMON service for SNMPD *******
Oct 09 10:19:13:864274:info:fi_debug:debug_logs:1:4808770304:
******* Starting HMON service for RMON-Daemon *******
console going online
Press any key to continue..

3 Messages

 • 

80 Points

@jain_jose Its taking too much time to boot casue of this errors.. is thre a fix for the 90.a Firmware ?

Important Announcement