Compare Products

Hide

Clear All

VS

Home> Support> Downloads>

Ruijie RG-S6110 Series Switch RGOS11.0(5)B3P2S1 Firmware

2019-12-12 View:
Dasan V8600 Series Switch NOS Release Notes,11.0_4_21

 

 

 

 

S6110-48XS4QXS Series Switch Release Notes,11.0(5)B3P2S1

 


Release Date: Dec 6, 2018

Current Release: RGOS11.0(5)B3P2S1

 

 

 

 

 

 



Contents

This document includes the followingsections:

n Basic Information

n Hardware Supported

n Changes

n Resolved Issues

n OpenIssues

n Limitations

n Related Documentation

n Upgrade Files

n UpgradeTips

n Upgrade Steps

Basic Information

Table 1 Basic Information of the CurrentRelease

Current Release

S6110_RGOS11.0(5)B3P2S1_install.bin

Previous Release

NA

Applicable Product

RG-S6110

Category

Office release

Test Report

 

Hardware Supported

Table 2 Hardware Models and the SupportingReleases

Hardware Model

Version

Description

Release

RG-S6110-48XS4QXS

2.0

Service module

RGOS11.0(5)B3P2S1

 

* The hardware version number is rounded to the first decimal place.The numeral in the second decimal place does not change the supporting release.

Changes

Table 3 shows modified or deleted featuresand command lines based on the baseline version. 

Table 3 Changes to the Baseline Version

Feature

Change Description

Release

Web

Added the support of Web-based and MACC-based configuration based S6220

 

Resolved Issues

1The device name of web page display error.

Open Issues

N/A

* See the bug notices for more details.

Limitations

N/A

RelatedDocumentation

n RG-S6110 Series SwitchHardware Installation and Reference Guide
This manual introduces the functional and physical features of the
RG-S6110 series switch and provides thedevice installation steps, hardware troubleshooting, module technicalspecifications, and specifications and usage guidelines for cables andconnectors.

n RG-S6110 Series SwitchConfiguration Guide, Release RGOS11.0(5)B3P2S1
This manual describes the various network protocols and their implementationprinciples for the
RG-S6110series with the detailed configuration examples.

n RG-S6110 Series SwitchCommand Reference, Release 11.0(5)B3P2S1
This manual describes the configuration commands related to the various networkprotocols supported on the
RG-S6110  series switch 11.0(5)B3P2S1 version in detail, including thecommand mode, parameter description, usage guide, and configuration examples.

Upgrade Files

Table 4 Latest Upgrade Files

Applicable Product

Upgrade File

File Size

MD5

RG-S6110-48XS4QXS

S6110_RGOS11.0(5)B3P2S1_install.bin

123,600,850Bytes

 

66FD4D5215A64315A40AD20AB73E8A11

Upgrade Tips

The following are some tips for upgradingthe RG-S6110 Series Switch RGOS11.0(5)B3P2S1:

n Forcible upgrade ofthe Boot and Uboot programs is required.

n During the upgrade, pay attention to the prompt messages.If failures occur, please save the log and contact us for technical assistance.

n During the upgrade, it is recommended you notpower off or reset the system, or plug/unplug any module.

n Use the show version detail command to checkthe firmware after the upgrade.

Upgrade Steps

The procedure of upgrading the RG-S6110Series Switch 11.0(5)B3P2S1 is described as follows:

Step 1:

Connect the Console port to a PC running HyperTerminal or similaremulation program. Set baud rate to 9600, data bitsto 8, stop bits to 1 and flow control to none.

Step 2:

Connect the switch to the PC with anEthernet cable. Run the TFTPserver on the PC and select the files (such as upgrade files) to be transmitted.

Step 3:

Power up and start the switch. If theswitch can enter the Main program, follow Step 4 Upgrade the main program. Ifthe device cannot enter the Uboot program, please contact us for technicalassistance.

Step 4:

Upgrade the main program.

Ruijie#upgrade download tftp://172.31.61.203/S6110_RGOS11.0(5)B3P2S1_install.bin$

% Copy to /tmp/vsd/0/upgrade_rep/

Please wait for a moment......

Press Ctrl+C to quit

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Begin to upgrade the install packageS6110_RGOS11.0(5)B3P2S1_install.bin...

Ruijie#*Dec  3 10:01:25: %7:

*Dec  3 10:01:25: %7: [Slot 2/0]:Upgrade processing is10%

*Dec  3 10:01:47: %7:

*Dec  3 10:01:47: %7: [Slot 2/0]:Upgrade processing is60%

*Dec  3 10:02:39: %7:

*Dec  3 10:02:39: %7: [Slot 2/0]:Upgrade processing is90%

*Dec  3 10:02:39: %7:

*Dec  3 10:02:39: %7: [Slot 2/0]:

*Dec  3 10:02:39: %7: Upgrade info [OK]

*Dec  3 10:02:40: %7: Bootversion[1.2.17.af01c0f->1.2.17.af01c0f]

*Dec  3 10:02:40: %7: Kernelversion[2.6.32.a7bf074f7a5431->2.6.32.a7bf074f7a5431]

*Dec  3 10:02:40: %7: Rootfsversion[1.0.0.891523b3->1.0.0.efb5544b]

*Dec  3 10:02:40: %7:

*Dec  3 10:02:40: %7: [Slot 2/0]:Reload system to takeeffect!

*Dec  3 10:02:41: %7:

*Dec  3 10:02:41: %7: [Slot 2/0]:Upgrade processing is100%

*Dec  3 10:02:42: %7: [Slot 2/0]

*Dec  3 10:02:42: %7: device_name: s6k

*Dec  3 10:02:42: %7: status:     SUCCESS

Boot SPL 1.2.30-7172482 (Mar 27 2017 - 21:37:15)

 

NAND: Detected flash

 

 

Boot 1.2.35-42ce917f0c-dirty (Feb 05 2018 - 15:57:41)

 

I2C:   ready

DRAM:  508 MiB

NAND:   Micron MT29F2G08ABAEA, chipsize 256 MiB

In:    serial

Out:   serial

Err:   serial

Unlocking L2 Cache ...Done

arm_clk=1000MHz, axi_clk=400MHz, apb_clk=100MHz,arm_periph_clk=500MHz

SETMAC: Setmac operation was performed at 2017-12-0116:20:23 (version: 11.0)

Press Ctrl+C to enter Boot Menu

Creating 1 MTD partitions on "nand0":

0x000001000000-0x000002e00000 : "mtd=6"

UBI: attaching mtd1 to ubi0

UBI: physical eraseblock size:   131072 bytes(128 KiB)

UBI: logical eraseblock size:    126976bytes

UBI: smallest flash I/O unit:    2048

UBI: VID headeroffset:          2048 (aligned2048)

UBI: dataoffset:               4096

UBI: attached mtd1 to ubi0

UBI: MTD devicename:           "mtd=6"

UBI: MTD devicesize:            30 MiB

UBI: number of goodPEBs:        240

UBI: number of badPEBs:         0

UBI: max. allowedvolumes:       128

UBI: wear-leveling threshold:    4096

UBI: number of internal volumes: 1

UBI: number of user volumes:     1

UBI: availablePEBs:            19

UBI: total number of reserved PEBs: 221

UBI: number of PEBs reserved for bad PEB handling: 2

UBI: max/mean erase counter: 2/0

UBIFS: recovery needed

UBIFS: recovery deferred

UBIFS: mounted UBI device 0, volume 0, name"kernel"

UBIFS: mounted read-only

UBIFS: file system size:   26030080 bytes (25420KiB, 24 MiB, 205 LEBs)

UBIFS: journal size:      3682304 bytes (3596 KiB, 3 MiB, 29 LEBs)

UBIFS: media format:      w4/r0 (latest is w4/r0)

UBIFS: default compressor: LZO

UBIFS: reserved for root:  0 bytes (0 KiB)

Loading file '.upgrade' to addr 0x82000000 with size 59(0x0000003b)...

Done

Loading file '.upgrade_zone' to addr 0x82000000 with size15 (0x0000000f)...

Done

Unmounting UBIFS volume kernel!

UBI: mtd1 is detached from ubi0

Creating 1 MTD partitions on "nand0":

0x000002e00000-0x00000f600000 : "mtd=7"

UBI: attaching mtd1 to ubi0

UBI: physical eraseblock size:   131072 bytes(128 KiB)

UBI: logical eraseblock size:    126976bytes

UBI: smallest flash I/O unit:    2048

UBI: VID headeroffset:          2048 (aligned2048)

UBI: data offset:               4096

UBI: attached mtd1 to ubi0

UBI: MTD devicename:           "mtd=7"

UBI: MTD devicesize:            200 MiB

UBI: number of goodPEBs:        1600

UBI: number of badPEBs:         0

UBI: max. allowedvolumes:       128

UBI: wear-leveling threshold:    4096

UBI: number of internal volumes: 1

UBI: number of user volumes:     1

UBI: availablePEBs:            118

UBI: total number of reserved PEBs: 1482

UBI: number of PEBs reserved for bad PEB handling: 16

UBI: max/mean erase counter: 3/0

UBIFS: recovery needed

UBIFS: recovery deferred

UBIFS: mounted UBI device 0, volume 1, name"rootfs"

UBIFS: mounted read-only

UBIFS: file system size:   184242176 bytes(179924 KiB, 175 MiB, 1451 LEBs)

UBIFS: journal size:      9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)

UBIFS: media format:      w4/r0 (latest is w4/r0)

UBIFS: default compressor: LZO

UBIFS: reserved for root:  0 bytes (0 KiB)

ubifsload 0x82000000S19_RGOS11.4(1)B12P10_05142705_install.bin.up.tmp;

Loading file 'S19_RGOS11.4(1)B12P10_05142705_install.bin.up.tmp'to addr 0x82000000 with size 81225404 (0x04d766bc)...

Done

upgrade S19_RGOS11.4(1)B12P10_05142705_install.bin.up.tmpsize 4d766bc..........

Uncompressing 0x4d759ca@0x82000cf2 to 0x69a12fc@0x86d766bc

Uncompressed 0x69a12fc bytes

Move the uncompressed data(0x69a12fc bytes) from 0x86d766bcto 0x82000000.

Get boot addr 0x886d7768,len 0xdc200; kernel addr0x820e2ebc,len 0x440000; rootfs addr 0x82522f38, len 0x5f20000

Package information:

    kernel version:3.10.18.da82d89332c92d

    rootfs version:1.0.0.46f5b5b0

    boot version:1.2.30.7172482

Upgrading boot ...

 

Erasing at 0x2c0000 -- 100% complete.

OK

#

SUCCESS: UPGRADING UBOOT OK.

Erasing Nand...

Erasing at 0x4e0000 -- 100% complete.

Writing to Nand... done

 

Erasing at 0x2de0000 -- 100% complete.

OK

 

Erasing at 0xf5e0000 -- 100% complete.

OK

################################################################################

Unmounting UBIFS volume data!

UBI: mtd1 is detached from ubi0

Creating 1 MTD partitions on "nand0":

0x000001000000-0x000002e00000 : "mtd=6"

UBI: attaching mtd1 to ubi0

UBI: physical eraseblock size:   131072 bytes(128 KiB)

UBI: logical eraseblock size:    126976bytes

UBI: smallest flash I/O unit:    2048

UBI: VID headeroffset:          2048 (aligned2048)

UBI: data offset:               4096

UBI: attached mtd1 to ubi0

UBI: MTD devicename:           "mtd=6"

UBI: MTD devicesize:            30 MiB

UBI: number of goodPEBs:        240

UBI: number of badPEBs:         0

UBI: max. allowedvolumes:       128

UBI: wear-leveling threshold:    4096

UBI: number of internal volumes: 1

UBI: number of user volumes:     1

UBI: availablePEBs:            19

UBI: total number of reserved PEBs: 221

UBI: number of PEBs reserved for bad PEB handling: 2

UBI: max/mean erase counter: 1/0

UBIFS: mounted UBI device 0, volume 0, name"kernel"

UBIFS: mounted read-only

UBIFS: file system size:   26030080 bytes (25420KiB, 24 MiB, 205 LEBs)

UBIFS: journal size:      3682304 bytes (3596 KiB, 3 MiB, 29 LEBs)

UBIFS: media format:      w4/r0 (latest is w4/r0)

UBIFS: default compressor: LZO

UBIFS: reserved for root:  0 bytes (0 KiB)

finding an appropriatekernel...vmlinux-3.10.18.da82d89332c92d

Loading file 'vmlinux-3.10.18.da82d89332c92d' to addr0x82000000 with size 2021509 (0x001ed885)...

Done

current rootfs:1

current kernal name:vmlinux-3.10.18.da82d89332c92d

 

Erasing at 0xfe0000 -- 100% complete.

OK

##

Erasing Nand...

Erasing at 0x4e0000 -- 100% complete.

Writing to Nand... done

 

SUCCESS: UPGRADING OK.

resetting ...

 

 

Boot SPL 1.2.30-7172482 (Mar 27 2017 - 21:37:15)

 

NAND: Detected flash

 

 

Boot 1.2.30-7172482 (Mar 27 2017 - 21:37:15)

 

I2C:   ready

DRAM:  508 MiB

NAND:   Micron MT29F2G08ABAEA, chipsize 256 MiB

In:    serial

Out:   serial

Err:   serial

Unlocking L2 Cache ...Done

arm_clk=1000MHz, axi_clk=400MHz, apb_clk=100MHz,arm_periph_clk=500MHz

SETMAC: Setmac operation was performed at 2017-12-0116:20:23 (version: 11.0)

Press Ctrl+C to enter Boot Menu

Creating 1 MTD partitions on "nand0":

0x000001000000-0x000002e00000 : "mtd=6"

UBI: attaching mtd1 to ubi0

UBI: physical eraseblock size:   131072 bytes(128 KiB)

UBI: logical eraseblock size:    126976bytes

UBI: smallest flash I/O unit:    2048

UBI: VID headeroffset:          2048 (aligned2048)

UBI: dataoffset:               4096

UBI: attached mtd1 to ubi0

UBI: MTD devicename:           "mtd=6"

UBI: MTD devicesize:            30 MiB

UBI: number of goodPEBs:        240

UBI: number of badPEBs:         0

UBI: max. allowedvolumes:       128

UBI: wear-leveling threshold:    4096

UBI: number of internal volumes: 1

UBI: number of user volumes:     1

UBI: availablePEBs:            19

UBI: total number of reserved PEBs: 221

UBI: number of PEBs reserved for bad PEB handling: 2

UBI: max/mean erase counter: 1/0

UBIFS: mounted UBI device 0, volume 0, name"kernel"

UBIFS: mounted read-only

UBIFS: file system size:   26030080 bytes (25420KiB, 24 MiB, 205 LEBs)

UBIFS: journal size:      3682304 bytes (3596 KiB, 3 MiB, 29 LEBs)

UBIFS: media format:      w4/r0 (latest is w4/r0)

UBIFS: default compressor: LZO

UBIFS: reserved for root:  0 bytes (0 KiB)

Unmounting UBIFS volume kernel!

   Uncompressing Kernel Image ... OK

   Loading Device Tree to 823fc000, end 823ff593... OK

 

Starting kernel ...

 

 

*Feb 27 10:33:15: %LOCAL_DP-5-LC_PROB: Board information inthis chassis has been collected.

*Feb 27 10:33:15: %SWITCH-6-INSTALL: Install chassisXS-S1960-48GT4SFP-H on switch 1

*Feb 27 10:33:16: %DP-6-MASTER: Module in slot 0 hastranslated to master.

*Feb 27 10:33:18: %DEV_MONITOR-5-CARD_POWER_ON: The powerenough, card in slot 0 will be controlled to power on automatically.

*Feb 27 10:33:20: %DP-6-POWER_OK: Power 1 ok.

*Feb 27 10:33:20: %DP-6-FAN_OK: Fan 1/1 ok.

~ # *Feb 27 10:33:23: %DP-5-PROB: Board probing hascompleted.

*Feb 27 10:33:23: %DEV_MONITOR-6-DEVICE_INIT: master roleinit.

*Feb 27 10:33:24: %SYSMON-5-WARMSTART: System warmstart.

*Feb 27 10:33:24: %REDUNDANCY-6-STATES_CHANGE: Redundancystates changed: role master, state alone.

*Feb 27 10:34:30: %SYS-4-CPU_HIGH: warning! system cpu usageabove high watermark(85%), current cpu usage 86%

*Feb 27 10:34:30: %SYSMON-4-CPU_WATERMARK_HIGH: TOP 1: pidis 1736, task name is ssa_process, run in core 0, cpu usage 53.8%

*Feb 27 10:34:30: %SYSMON-4-CPU_WATERMARK_HIGH: TOP 2: pidis 1762, task name is ssd_process, run in core 0, cpu usage 45.4%

*Feb 27 10:34:54: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state to up.

*Feb 27 10:34:54: %LINEPROTO-5-UPDOWN: Line protocol onInterface GigabitEthernet 0/1, changed state to up.

*Feb 27 10:34:54: %LLDP-4-CREATEREM: Port GigabitEthernet0/1 created one new neighbor, Chassis ID is 08c6.b315.0141, Port ID is Fa0/7.

*Feb 27 10:34:56: %LINK-3-UPDOWN: Interface GigabitEthernet0/3, changed state to up.

*Feb 27 10:34:56: %LINEPROTO-5-UPDOWN: Line protocol onInterface GigabitEthernet 0/3, changed state to up.

 

*Feb 27 10:34:56: %LLDP-4-CREATEREM: Port GigabitEthernet0/3 created one new neighbor, Chassis ID is 10c3.7bb5.ca1b, Port ID is10c3.7bb5.ca1b.

*Feb 27 10:34:56: %LINEPROTO-5-UPDOWN: Line protocol onInterface VLAN 1, changed state to up.

 

Ruijie#show version detail

System description      : RuijieFull 10G Routing Switch(S6110-48XS4QXS) By Ruijie Networks

System start time       :2017-12-06 12:56:30

Systemuptime           : 0:00:02:52

System hardware version : 2.20

System software version : S6110_RGOS 11.0(5)B3P2S1

System patch number     : NA

System software number  : M12154612062018

System serial number    : G1LB0P900043A

System boot version     :1.2.17.af01c0f(151130)

System core version     :2.6.32.92cff322c38e9e

Module information:

  Slot 0 : RG-S6110-48XS4QXS

    Hardware version    :2.20

    System start time   :2017-12-06 12:56:30

    Bootversion        : 1.2.17.af01c0f(151130)

    Software version    :S6110_RGOS 11.0(5)B3P2S1

    Software number    : M12154612062018

    Serialnumber       : G1LB0P900043A

Step 5:

Use the show version detail commandto verify whether the software version is the latest.

The Main Module programs are upgraded to S6110RGOS11.0(5)B3P2S1. Theupgrading is successful.

How do you like this document ?

Suggestion


(0/255)

Can we contact you to discuss your suggestion?

Privacy Policy
Thank you. We will inform you of our response as soon as possible.
Thank you again for your valuable input!
This page will be closed in 5 s…
Submit

Ruijie Networks websites use cookies to deliver and improve the website experience.

See our cookie policy for further details on how we use cookies and how to change your cookie settings.

Cookie Manager

When you visit any website, the website will store or retrieve the information on your browser. This process is mostly in the form of cookies. Such information may involve your personal information, preferences or equipment, and is mainly used to enable the website to provide services in accordance with your expectations. Such information usually does not directly identify your personal information, but it can provide you with a more personalized network experience. We fully respect your privacy, so you can choose not to allow certain types of cookies. You only need to click on the names of different cookie categories to learn more and change the default settings. However, blocking certain types of cookies may affect your website experience and the services we can provide you.

  • Performance cookies

    Through this type of cookie, we can count website visits and traffic sources in order to evaluate and improve the performance of our website. This type of cookie can also help us understand the popularity of the page and the activity of visitors on the site. All information collected by such cookies will be aggregated to ensure the anonymity of the information. If you do not allow such cookies, we will have no way of knowing when you visited our website, and we will not be able to monitor website performance.

  • Essential cookies

    This type of cookie is necessary for the normal operation of the website and cannot be turned off in our system. Usually, they are only set for the actions you do, which are equivalent to service requests, such as setting your privacy preferences, logging in, or filling out forms. You can set your browser to block or remind you of such cookies, but certain functions of the website will not be available. Such cookies do not store any personally identifiable information.

Accept All

View Cookie Policy Details

Contact Us

Contact Us

How can we help you?

Contact Us

Get an Order help

Contact Us

Get a tech support