s5800 8tf12s Device Management Configuration
s5800 8tf12s Device Management Configuration
Contents
1 Configuring STM.......................................................................................................................... 8
1.1 Overview.......................................................................................................................................................... 8
1.2 Configuration................................................................................................................................................... 9
1.3 Validation......................................................................................................................................................... 9
2 Configuring Syslog..................................................................................................................... 11
2.1 Overview........................................................................................................................................................ 11
2.2 Terminology................................................................................................................................................... 11
2.3.1 Topology.............................................................................................................................................. 13
2.3.2 Configurations......................................................................................................................................13
2.3.3 Validation............................................................................................................................................. 13
2.4.1 Configurations......................................................................................................................................14
2.4.2 Validation............................................................................................................................................. 14
3 Configuring Mirror..................................................................................................................... 16
3.1 Overview........................................................................................................................................................ 16
3.2 Terminology................................................................................................................................................... 16
3.3 Topology.........................................................................................................................................................19
3.4 Configuration................................................................................................................................................. 20
3.5 Validation....................................................................................................................................................... 20
4.2 Terminology................................................................................................................................................... 22
4.3 Topology.........................................................................................................................................................25
FSOS Device Management Configuration Guide
4.4 Configuration................................................................................................................................................. 25
4.5 Validation....................................................................................................................................................... 26
5.1.1 Overview.............................................................................................................................................. 28
5.1.2 Terminology......................................................................................................................................... 28
5.1.3 Topology.............................................................................................................................................. 29
5.1.4 Configuration....................................................................................................................................... 30
5.1.5 Validation............................................................................................................................................. 33
5.2.1 Overview.............................................................................................................................................. 34
5.2.2 Topology.............................................................................................................................................. 35
5.2.3 Configuration....................................................................................................................................... 35
5.2.4 Validation............................................................................................................................................. 36
6.1 Overview........................................................................................................................................................ 37
6.2.1 Configuration....................................................................................................................................... 37
6.2.2 Validation............................................................................................................................................. 38
6.3.1 Configuration....................................................................................................................................... 38
6.3.2 Validation............................................................................................................................................. 38
6.4.2 Validation............................................................................................................................................. 39
6.5.1 Configuration....................................................................................................................................... 40
6.5.2 Validation............................................................................................................................................. 40
6.6.1 Configuration....................................................................................................................................... 41
6.6.2 Validation............................................................................................................................................. 41
6.7.1 Configuration....................................................................................................................................... 42
6.7.2 Validation............................................................................................................................................. 42
6.8.1 Configurations......................................................................................................................................43
6.8.2 Validation............................................................................................................................................. 43
6.9.1 Configurations......................................................................................................................................44
6.9.2 Validation............................................................................................................................................. 44
7 Configuring Bootrom..................................................................................................................45
7.1 Overview........................................................................................................................................................ 45
7.2.1 Configurations......................................................................................................................................45
7.2.2 Validation............................................................................................................................................. 46
7.3.1 Configurations......................................................................................................................................46
7.3.2 Validation............................................................................................................................................. 47
7.4.1 Configurations......................................................................................................................................48
7.4.2 Validation............................................................................................................................................. 48
7.5.1 Configurations......................................................................................................................................49
7.5.2 Validation............................................................................................................................................. 49
7.6.1 Configurations......................................................................................................................................49
7.6.2 Validation............................................................................................................................................. 50
8.1 Overview........................................................................................................................................................ 51
8.2 Configuration................................................................................................................................................. 51
8.3 Validation....................................................................................................................................................... 51
9 Configuring PoE.......................................................................................................................... 53
9.1 Overview........................................................................................................................................................ 53
9.2 Terminology................................................................................................................................................... 54
9.3 Topology.........................................................................................................................................................55
9.4 Configuration................................................................................................................................................. 55
9.5 Validation....................................................................................................................................................... 57
10 Configuring SmartConfig........................................................................................................ 59
10.1 Overview...................................................................................................................................................... 59
10.2 Topology.......................................................................................................................................................61
10.3 Configuration............................................................................................................................................... 61
11 Reboot Logs................................................................................................................................ 63
11.1 Overview...................................................................................................................................................... 63
11.2 Validation..................................................................................................................................................... 63
11.3 Warning........................................................................................................................................................ 64
FSOS Device Management Configuration Guide
Tables
Figures
1 Configuring STM
1.1 Overview
Switch Table Management (STM) is used to configure system resources in the switch to
optimize support for specific features, depending on how the switch is used in the network.
You can select a profile to provide maximum system usage for some functions; for example,
use the default profile to balance resources and use vlan profile to obtain max MAC entries.
To allocate ternary content addressable memory (TCAM) resources for different usages, the
switch STM profile prioritize system resources to optimize support for certain features. You
can select STM templates to optimize these features:
ipv4—The routing template maximizes system resources for unicast routing, typically
required for a router or aggregator in the center of a network.
vlan—The VLAN template supports the maximum number of unicast MAC addresses. It
would typically be selected for a Layer 2 switch.
default—The default template gives balance to all functions.
ipv6- The dual IPv4 and IPv6 templates allow the switch to be used in dual stack
environments (supporting both IPv4 and IPv6). Using the dual stack templates results in
less TCAM capacity allowed for each resource. Do not use them if you plan to forward
8
FSOS Device Management Configuration Guide
1.2 Configuration
Follow these guidelines when selecting and configuring STM profiles.
You must reload the switch for the configuration to take effect.
Use the stm prefer vlan global configuration command only on switches intended for Layer
2 switching with no routing.
Do not use the ipv4 profile if you do not have routing enabled on your switch. The stm
prefer ipv4 global configuration command prevents other features from using the memory
allocated to IPv4 unicast routing in the routing profile.
1.3 Validation
This is an example of an output display for default template.
9
FSOS Device Management Configuration Guide
G.8031 groups : 64
G.8032 rings : 32
number of VLAN class rules:
MAC based VLAN classification : 256
IPv4 based VLAN classification : 512
IPv6 based VLAN classification : 256
number of Dot1x Mac entry:
DOT1X MAC BASED : 256
number of IP unicast routing:
IPv4 host routes : 3072
Indirect IPv4 routes : 6144
IPv4 ECMP groups : 16
IPv4 policy based routes : 32
IPv6 host routes : 1024
Indirect IPv6 routes : 2048
IPv6 ECMP groups : 14
IP Tunnel Peers : 8
number of IP multicast routing:
IPv4 Mcast routes : 511
IPv4 Mcast total members : 2044
IPv6 Mcast routes : 127
IPv6 Mcast total members : 508
number of Security features:
IPv4 source guard entries : 1024
IPv4 ACL/QOS flow entries : 863
IPv6 ACL/QOS flow entries : 127
10
FSOS Device Management Configuration Guide
2 Configuring Syslog
This document is intended to give a usage example for system log feature.
2.1 Overview
The system message logging software can save messages in a log file or direct the messages to
other devices. The system message logging facility has these features:
By default, the switch logs normal but significant system messages to its internal buffer and
sends these messages to the system console. You can specify which system messages should
be saved based on the type of the severity level. The messages are time-stamped to enhance
real-time debugging and management.
You can access the logged system messages using the switch command-line interface (CLI) or
by saving them to a properly configured log server. The switch software saves the log
messages in an internal buffer that can store up to 1000 messages. You can monitor the system
messages remotely by accessing the switch through Telnet or the console port, or by viewing
the logs on a log server.
2.2 Terminology
Logging: Current logging configuration
11
FSOS Device Management Configuration Guide
12
FSOS Device Management Configuration Guide
2.3.1 Topology
2.3.2 Configurations
2.3.3 Validation
And you can check the result by using show logging command:
13
FSOS Device Management Configuration Guide
2.4.1 Configurations
2.4.2 Validation
And you can check the result by using show logging command.
14
FSOS Device Management Configuration Guide
You can use command to check showing Logging Information. When configuring the syslog Servers,
make sure the cables is linked correctly and two computers can ping each other. Before you can send
the system log messages to a log server, you must configure Syslog Software, at the end you can see
the log from your software.
15
FSOS Device Management Configuration Guide
3 Configuring Mirror
3.1 Overview
You can analyze network traffic passing through ports or vlans by using mirror function to
send a copy of the traffic to another port on the switch that has been connected to a Switch
Probe device or other Remote Monitoring (RMON) probe or security device. Mirrors received
or sent (or both) traffic on a source port and received traffic on one or more source ports or
source vlans, to a destination port for analysis.
Only traffic that enters or leaves source ports or traffic that enters source vlans can be
monitored by using mirror; traffic that gets routed to ingress source ports or source vlans
cannot be monitored. For example, if incoming traffic is being monitored, traffic that gets
routed from another vlans to the source vlans is not monitored; however, traffic that is received
on the source vlan and routed to another vlan is monitored.
Mirror does not affect the switching of network traffic on source ports or source vlans; a copy
of the packets received or sent by the source interfaces are sent to the destination interface.
3.2 Terminology
The following describes concepts and terminology associated with mirror configuration.
Mirror Session
A mirror session is an association of a destination port with source ports and source VLANs.
You configure mirror sessions by using parameters that specify the source of network traffic to
monitor. Both switched and routed ports can be configured as mirror sources and destinations.
You can configure up to 3 mirror sessions.
16
FSOS Device Management Configuration Guide
Mirror sessions do not interfere with the normal operation of the switch. However, an
oversubscribed mirror destination, for example, a 10-Mbps port monitoring a 100-Mbps port,
results in dropped or lost packets.
You can configure mirror sessions on disabled ports; however, a mirror session does not
become active unless you enable the destination port and at least one source port or VLAN for
that session.
A mirror session remains inactive after system power-on until the destination port is
operational.
Traffic Types
Receive (RX) mirror: The goal of receive (or ingress) mirror is to monitor as much as possible
packets received by the source interface or VLAN before any modification or processing is
performed by the switch. A copy of each packet received (except these packets: BPDU,
LACPDU, BMGPDU, packets have been discarded by IP-MAC binding check for
Vlan_based mirror, CRC error packets for both Port_based and vlan_based mirror) by the
source is sent to the destination port for that mirror session. You can monitor a series or range
of ingress ports or VLANs in a mirror session. Packets that are modified because of routing are
copied without modification; that is, the original packet is copied. Packets that are modified
because of quality of service (QoS)—for example, modified Differentiated Services Code
Point (DSCP)—are copied with modification. Packets that are modified because of VLAN
translation or VLAN classification is copied with the modification. Some features that can
cause a packet to be dropped during receive processing have no effect on mirror, the
destination port can receive a copy of the packet even if the actual incoming packet is dropped.
These features include ingress ACL, VLAN’s ingress filter, MAC filter, STP, VLAN tag
control, port security, unknown routing packets.
Transmit (TX) mirror: The goal of transmit (or egress) mirror is to monitor as much as possible
packets sent by the source interface after all modification and processing is performed by the
switch. A copy of each packet (except these packets: packets from CPU port for Vlan_based
mirror, mirroring packets for both Port_based and vlan_based mirror) sent by the source is
17
FSOS Device Management Configuration Guide
sent to the destination port for that mirror session. Some features that can cause a packet to be
dropped during transmit processing might have affect on mirror.
Both: In a mirror session, you can monitor a single port for both received and sent packets.
Source Port
A source port (also called a monitored port) is a switched or routed port that you monitor for
network traffic analysis. In a single mirror session, you can monitor source port traffic such as
received (Rx), transmitted (Tx), or bidirectional (both). The switch supports any number of
source ports (up to the maximum number of available ports on the switch) and any number of
source VLANs (up to the maximum number of VLANs supported).
Each source port can be configured with a direction (ingress, egress, or both) to monitor. For
EtherChannel sources, the monitored direction would apply to all the physical ports in the
group.
For VLAN sources, user should create VLAN Interface before configure a vlan source.
Destination Port
Each mirror session must have a destination port (also called a monitoring port) that receives a
copy of traffic from the source ports and VLANs.
18
FSOS Device Management Configuration Guide
It can participate in only one mirror session at a time (a destination port in one mirror session
cannot be a destination port for a second mirror session).
The port does not transmit any traffic except that required for the mirror session.
It does not participate in spanning tree while the mirror session is active.
When it is a destination port, all other normal system function of this port should not work
until mirror destination configure disabled on this port.
The real statues of the speed/duplex might not coincide with the values which are displayed.
3.3 Topology
For example, in the below figure, all traffic on port 1(the source port) is mirrored to port 2(the
destination port). A network analyzer on port 2 receives all network traffic from port 1 without
being physically attached to port 1
19
FSOS Device Management Configuration Guide
3.4 Configuration
3.5 Validation
This example shows how to set up a mirror session, session 1, for monitoring source port
traffic to a destination port. You can use show monitor session to see the configuration.
Session 1
----------
Status : Valid
Type : Local Session
Source Ports :
Receive Only :
Transmit Only :
Both : eth-0-1
Source VLANs :
Receive Only : 10
Transmit Only :
Both :
Destination Port : eth-0-2
21
FSOS Device Management Configuration Guide
4.1 Overview
You can analyze network traffic passing through ports by using mirror function to send several
copies of the traffic to another port on the switch that has been connected to a Switch Probe
device or security device. Mirrors received or sent (or both) traffic on a source port and
received traffic on one or more source port, to several destination ports for analysis.
4.2 Terminology
The following describes concepts and terminology associated with mirror configuration.
Mirror Session
A multi-destination mirror session is an association of a destination port with source ports. You
configure mirror sessions by using parameters that specify the source of network traffic to
monitor. Both switched and routed ports can be configured as mirror sources and destinations.
You can configure up to 1 multi-destination mirror sessions.
Mirror sessions do not interfere with the normal operation of the switch. However, an
oversubscribed mirror destination, for example, a 10-Mbps port monitoring a 100-Mbps port,
results in dropped or lost packets.
You can configure mirror sessions on disabled ports; however, a mirror session does not
become active unless you enable the destination port and at least one source port for that
session.
22
FSOS Device Management Configuration Guide
A mirror session remains inactive after system power-on until the destination port is
operational.
Traffic Types
Receive (RX) mirror: The goal of receive (or ingress) mirror is to monitor as much as possible
packets received by the source interface before any modification or processing is performed
by the switch. A copy of each packet received (except these packets: BPDU, LACPDU,
BMGPDU, packets have been discarded by IP-MAC binding check for Vlan_based mirror,
CRC error packets for both Port_based and vlan_based mirror) by the source is sent to the
destination port for that mirror session. You can monitor a series or range of ingress ports or
VLANs in a mirror session. Packets that are modified because of routing are copied without
modification; that is, the original packet is copied. Packets that are modified because of quality
of service (QoS)—for example, modified Differentiated Services Code Point (DSCP)—are
copied with modification. Packets that are modified because of VLAN translation or VLAN
classification is copied with the modification. Some features that can cause a packet to be
dropped during receive processing have no effect on mirror, the destination port can receive a
copy of the packet even if the actual incoming packet is dropped. These features include
ingress ACL, VLAN’s ingress filter, MAC filter, STP, VLAN tag control, port security,
unknown routing packets.
Transmit (TX) mirror: The goal of transmit (or egress) mirror is to monitor as much as possible
packets sent by the source interface after all modification and processing is performed by the
switch. A copy of each packet (except these packets: packets from CPU port for Vlan_based
mirror, mirroring packets for both Port_based and vlan_based mirror) sent by the source is
sent to the destination port for that mirror session. Some features that can cause a packet to be
dropped during transmit processing might have affect on mirror.
Both: In a mirror session, you can monitor a single port for both received and sent packets.
Source Port
A source port (also called a monitored port) is a switched or routed port that you monitor for
network traffic analysis. In a single mirror session, you can monitor source port traffic such as
23
FSOS Device Management Configuration Guide
received (Rx), transmitted (Tx), or bidirectional (both). The multi-destination mirror only
supports any number of source ports (up to the maximum number of available ports on the
switch).
Each source port can be configured with a direction (ingress, egress, or both) to monitor. For
EtherChannel sources, the monitored direction would apply to all the physical ports in the
group.
Destination Port
A multi-destination mirror session can have several destination ports (also called a monitoring
port) that receives a copy of traffic from the source ports.
It can participate in only one mirror session at a time (a destination port in one mirror session
cannot be a destination port for a second mirror session).
The port does not transmit any traffic except that required for the mirror session.
It does not participate in spanning tree while the mirror session is active.
When it is a destination port, all other normal system function of this port should not work
until mirror destination configure disabled on this port.
24
FSOS Device Management Configuration Guide
The real statues of the speed/duplex might not coincide with the values which are displayed.
4.3 Topology
For example, in figure 4-1, all traffic on port 1(the source port) is mirrored to port 2 and port
3(the destination port). A network analyzer on port 2 and port 3 receives all network traffic
from port 1without being physically attached to port 1
4.4 Configuration
4.5 Validation
This example shows how to set up a mirror session, session 1, for monitoring source port
traffic to a destination port. You can use show monitor session to see the configuration.
Session 1
----------
Status : Valid
Type : Local Session
Source Ports :
Receive Only :
26
FSOS Device Management Configuration Guide
Transmit Only :
Both : eth-0-1
Source VLANs :
Receive Only :
Transmit Only :
Both :
Destination Port : eth-0-2 eth-0-3
27
FSOS Device Management Configuration Guide
5.1.1 Overview
Remote mirror supports source ports, source VLANs, and destination ports on different
switches (or different switch stacks), enabling remote monitoring of multiple switches across
your network.
5.1.2 Terminology
The following describes concepts and terminology associated with remote mirror
configuration.
A remote mirror session is an association of some local source ports and vlans with a remote
destination vlan, which has a specified out-going port.
The concepts of source ports and vlans in a remote mirror source session are as same as the
local mirror.
28
FSOS Device Management Configuration Guide
Monitor traffic packets are inserted a tag with the remote VLAN ID and directed over the
specified out going port to the mirror destination session device.
It is recommended to configure remote mirror's destination port as switch port. Users
should add the destination port to the remote vlan otherwise the mirrored packet can not be
transmitted out.
5.1.3 Topology
The below figure shows source ports on Switch A. The traffic for each remote mirror session is
carried over a user-specified remote mirror VLAN that is dedicated for that remote mirror
session in all participating switches. The remote mirror traffic from the source ports or VLANs
is copied into the remote mirror VLAN and forwarded over trunk ports carrying the remote
mirror VLAN to a destination session monitoring the remote mirror VLAN. Each remote
mirror source switch must have either ports or VLANs as remote mirror sources. The
destination is always a physical port, as same as the local mirror.
29
FSOS Device Management Configuration Guide
5.1.4 Configuration
30
FSOS Device Management Configuration Guide
31
FSOS Device Management Configuration Guide
2. Use access port to get the packet (you needn’t any monitor session on switch B).
3. Use trunk port to get tagged packet (you needn’t any monitor session on switch B).
32
FSOS Device Management Configuration Guide
Use method 2 and method 3 might cause system leaning the Mac of mirrored packets and lead the
FDB table exhausted.
5.1.5 Validation
This example shows how to set up a mirror session, session 1, for monitoring source port
traffic to a destination port. You can use show monitor session to see the configuration.
Session 1
----------
Status : Valid
Type : Remote Session
Source Ports :
Receive Only :
Transmit Only :
Both : eth-0-1
Source VLANs :
Receive Only :
Transmit Only :
Both :
Destination Port : eth-0-2
Destination remote VLAN : 15
33
FSOS Device Management Configuration Guide
Session 1
----------
Status : Valid
Type : Local Session
Source Ports :
Receive Only :
Transmit Only :
Both :
Source VLANs :
Receive Only : 15
Transmit Only :
Both :
Destination Port : eth-0-2
5.2.1 Overview
Mac escape is a sub-feature of remote mirror. It only affects the result of remote mirror.
A Mac escape entry includes a Mac address and a Mac Mask. When Mac escape entries are set,
the packets whose MAC-DA match the entries should not be mirrored to the remote
destination vlan. User can prevent protocol packed mirrored to remote by set some Mac escape
entries.
34
FSOS Device Management Configuration Guide
5.2.2 Topology
5.2.3 Configuration
35
FSOS Device Management Configuration Guide
5.2.4 Validation
This example shows how to set up the mac escape entries. You can use show monitor mac
escape to see the configuration.
-------------------------------------------------------------
monitor rspan mac escape database
-------------------------------------------------------------
count : 2
-------------------------------------------------------------
Mac : 00:cc:12:a9:33:d8
Mask : ff:ff:ff:ff:ff:ff
Mac : 00:cc:15:9e:24:f0
Mask : ff:ff:ff:ff:ff:ff
-------------------------------------------------------------
36
FSOS Device Management Configuration Guide
6.1 Overview
User can manage the switch through the management port. The switch has two management
ports: an Ethernet port and a console port.
6.2.1 Configuration
The default console parameters of switch are:
Before you can assign switch information, make sure you have connected a PC or terminal to
the console port, and configured the PC or terminal software parameters to match the default
console port parameters. After login in the switch, you can modify the console parameters.
37
FSOS Device Management Configuration Guide
6.2.2 Validation
After the above setting, console port parameter has been changed, and the PC or terminal can’t
configure the switch by console port. You must update PC or terminal console speed from 9600
to 19200 to match the new console parameter and can continue configure the switch by console
port.
6.3.1 Configuration
6.3.2 Validation
After the above setting, you can use CLI ‘show management ip address’ or ‘show management
ipv6 address’ to verify the configured management IP address. Also you can ping A.B.C.D
from PC to verify the ip address.
38
FSOS Device Management Configuration Guide
6.4.2 Validation
Switch# show environment
---------------------------------------------------------
Sensor status (Degree Centigrade):
Index Temperature Lower_alarm Upper_alarm Critical_limit
1 49 5 70 85
39
FSOS Device Management Configuration Guide
6.5.1 Configuration
The Tlow, Thigh, Tcrit, Thyst and fan speed rate for each temperature threshold are hard code,
and couldn’t be modified.
6.5.2 Validation
User can change the environment temperature to verify the fan auto management.
40
FSOS Device Management Configuration Guide
---------------------------------------------------------
Sensor status (Degree Centigrade):
Index Temperature Lower_alarm Upper_alarm Critical_limit
1 50 5 75 90
6.6.1 Configuration
This function has no configuration command.
6.6.2 Validation
User can show the power status to verify the power status.
---------------------------------------------------------
Power status:
Index Status Power Type Fans Control
1 PRESENT OK AC - -
2 ABSENT - - - -
3 PRESENT OK DC(PoE) - -
---------------------------------------------------------
41
FSOS Device Management Configuration Guide
6.7.1 Configuration
6.7.2 Validation
User can show the transceiver information to verify this function.
42
FSOS Device Management Configuration Guide
----------------------------------------------------------------------------------------------
---------
Optical High Alarm High Warn Low Warn Low Alarm
Receive Power Threshold Threshold Threshold Threshold
Port (dBm) (dBm) (dBm) (dBm) (dBm)
--------- ------------------ --------------- ----------------- ----------------
----------------
eth-1-2 -12 - 1.00 0.00 -19.00 -20.00
----------------------------------------------------------------------------------------------
---------
6.8.1 Configurations
Switch# copy mgmt-if Copy bootloader image file from tftp server.
tftp://10.10.29.160/bootrom.bin flash:/boot/
Switch# configure terminal Enter global configuration mode.
Switch(config)# update bootrom flash:/boot/ Update bootrom from assigned file
bootrom.bin
Switch#(config)# exit Exit global configuration mode
Switch# reboot Restart device to confirm
6.8.2 Validation
After the above setting, you can show uboot version information of platform:
43
FSOS Device Management Configuration Guide
6.9.1 Configurations
Switch# copy mgmt-if tftp://10.10.29.160/ Copy EPLD image file from tftp server
vme_v1.0 flash:/boot/ vme_v1.0
Switch# configure terminal Enter global configuration mode
Switch(config)# update epld flash:/boot/ Update epld from assigned file
vme_v1.0
Switch(config)# exit Exit global configuration mode
Switch# reboot Restart device to confirm
6.9.2 Validation
After the above setting, then power off and restart the device,you can show epld version
information with command:
......
EPLD Version is 1
BootRom Version is 3.0.2
System serial number is E045GD111005
44
FSOS Device Management Configuration Guide
7 Configuring Bootrom
7.1 Overview
The main function of Bootrom is to initialize the board simply and load the system image to
boot. You can use some necessary commands in bootrom mode.
Bootrom can load the system image both from TFTP server and persistent storage like flash.
Then you can configure the Switch and TFTP server IP address as environment variables in
Bootrom mode for boot the system image.
7.2.1 Configurations
45
FSOS Device Management Configuration Guide
7.2.2 Validation
After the above setting, you can get show information
bootrom:> reset
………………..
TFTP from server 10.10.29.160; our IP address is 10.10.29.118
Filename 'OS-ms-v3.1.9.it.r.bin'.
Load address: 0xaa00000
Loading: octeth0: Up 100 Mbps Full duplex (port 0)
#################################################################
#####################
done
Bytes transferred = 12314539 (bbe7ab hex), 1829 Kbytes/sec
7.3.1 Configurations
Step 1 Boot the system through image OS-ms-v3.1.9.it.r.bin from flash, details information as
follows.
46
FSOS Device Management Configuration Guide
Step 2 Boot the system through image OS-ms-v3.1.9.it.r.bin from flash with default
configuration, details information as follows.
Step 3 Boot the system through image OS-ms-v3.1.9.it.r.bin from flash immediately, details
information as follows.
Step 4 Boot the system through image OS-ms-v3.1.9.it.r.bin from flash with default
configuration immediately, details information as follows.
7.3.2 Validation
After the above setting, you can get show information:
47
FSOS Device Management Configuration Guide
bootrom:> reset
…………
Do you want to revert to the default config file ? [Y|N|E]:Y
### JFFS2 loading '/boot/OS-ms-v3.1.9.it.r.bin' to 0xaa00000
Scanning JFFS2 FS: . done.
### JFFS2 load complete: 12314539 bytes loaded to 0xaa00000
## Booting image at 0aa00000 ...
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
…………
7.4.1 Configurations
Step 1 Set Switch IP address , details information as follows.
7.4.2 Validation
bootrom:> printenv
printenv
bootdelay=5
baudrate=9600
download_baudrate=9600
…………………
stderr=serial
ipaddr=10.10.29.101
ipserver=10.10.29.160
48
FSOS Device Management Configuration Guide
7.5.1 Configurations
bootrom:> upgrade_uboot bootrom.bin upgrade the Bootrom image from TFTP server
7.5.2 Validation
After the above setting, you can get show information:
bootrom:> version
version
7.6.1 Configurations
Step 1 Set Switch gateway IP address , details information as follows.
49
FSOS Device Management Configuration Guide
7.6.2 Validation
After the above setting, you can get show information:
bootrom:> printenv
printenv
bootdelay=5
baudrate=9600
download_baudrate=9600
…………………
stderr=serial
gatewayip=10.10.38.1
netmask=255.255.255.0
50
FSOS Device Management Configuration Guide
8.1 Overview
Bootup diagnostic is used to help user diagnose whether the hardware component of Switch is
working normally, after the Switch is already bootup. The diagnostic item including EPLD,
EEPROM, PHY, MAC and so on.
8.2 Configuration
The configuration of bootup diagnostic is as follow.
8.3 Validation
This example shows how to show the bootup diagnostic result.
#########################################################
Item Name Attribute Result Time(usec)
1 EPLD TEST C Pass 57
2 EEPROM0 TEST C Pass 101262
3 PHY TEST C Pass 1161
51
FSOS Device Management Configuration Guide
52
FSOS Device Management Configuration Guide
9 Configuring PoE
9.1 Overview
The main function of PoE is to pass electrical power safely, along with data, over Ethernet
cabling. The standard is IEEE 802.3at and IEEE 302.3af.
System can support PSE external supplied power to plug or remove suddenly, and can detect
the PSE supplied power status in 6s, then initiate the system PoE function. But we strongly
don’t recommend plugging or removing the PSE supplied power suddenly, as initiating the
system PoE function will make the system busy then impact the performance of the total
system.
If the PoE daughter card is absent, user configuration by CLI will be fail ignoring the status of
PoE power status.
If the PoE card is present, the real behavior of user configuration is based on the PSE supplied
power status. If the PSE supplied power is OK, the configuration will take effect and be stored
in memory. If the PoE power status is off, the configuration will only be stored in memory.
When PoE card is present, if PSE supplied power status change from absence to OK, PoE will
load PoE configuration from memory and PoE can work normally, if PSE supplied power
status change from OK to absence, PoE will save the PoE configuration and PoE can’t work.
When the current PSE voltage is lower than the 44 voltage or higher than the 57voltage,
system should tell user by information. We strongly recommend that PSE supplied voltage is
over 53V.
When the system total consumption is higher or lower than the alarm threshold of PSE budget
at the first time, system will alarm user by information.
53
FSOS Device Management Configuration Guide
Whenever the PD status changed such as powered on, powered off , power error and so on,
system will tell user by information.
When the PD is abnormal or PSE can’t power on the 30 WPD, PSE may repeatedly process the
IEEE standard power up flow. If PD status changes over 25 times in 60s, system will disable
the port to protect PSE and PD, then alarm user by information.
System PSE max budget is up to 739.2W which support 24 ports up to 30W or 48 ports up to
15.4W or mixed situation.
When both PSE and PD have the same PI mode, the PSE can power up PD successfully. PSE
only support alternative A mode which is that pin 1 and pin 2 is form one side of DC, pin 3 and
pin 6 form other side.
Each port can supply DC power and support the length of 100 meters at most, Category 5(and
Cat5e) cabling.
9.2 Terminology
Following is a brief description of terms and concepts used to describe PoE:
54
FSOS Device Management Configuration Guide
9.3 Topology
9.4 Configuration
Configuring PSEdetails
Set PSE power-management and legacy will trigger all the PDs powers off to make the PSE setting
works.
55
FSOS Device Management Configuration Guide
The difference of two power-management mode is that port priority only takes effect in
manual power-management mode.
The legacy PDs are devices that are not standard legacy device and some CISCO PD device.
The power-reserved percentage based on PSE budget is to prevent PD powered off from that
consumption added suddenly leads to PSE overload and detect the consumption of new
connected PD to decide whether the new connected PD will be powered on in system PoE
management rule (e.g.: priority rule).
There may be dangerous situation if PD isn’t connected when port administration is force power
mode.
If the port operating status is “protection off”, you can disable and then enable the port to make port
be normal. If the port operating status is “priority off” or “overload off”, only the PoE system
management automatically can make port be normal and PoE command can’t work well
If the frequency of port status changing times is too high, PSE will disable the PD to protect PD and
PSE from unknown dangerous situation.
The PD that exceeds its power budget will be disconnected due to overload and be punished in
60s time. The PSE will try to power on the overload PD after punish time. If the PD is still
overload, PD will be disconnected and the previous punish time will be add 60s. If the PD
works normal, the previous punish time will be subtracted 60s. The punish time can ascend
step by step till 1 hour, if the PD is always overload when port punish time is over. The punish
time can descend step by step till 0, when the PD is always normal but also port punish time is
exist
56
FSOS Device Management Configuration Guide
In manual PM mode, system supports three port priorities: critical, high and low. A critical port
is the highest priority; high priority is higher than low priority. The higher priority port which
consumption suddenly increased but within the port max budget can snatch system budget
from other port, when PSE is over available budget but within guard reserved budget. The
lower priority port may be powered off, if system is overload.
If several ports belong to the same priority, the lower panel number port has the higher priority.
In auto PM mode, the priority rule is the same to manual PM mode, but port priority doesn’t
take effect and the lower panel number port has the higher priority.
Whether the new connected PD will be powered on is based on port priority rule and PSE
reserved budget.
Time-range supports two modes: periodic and absolute, please refer to time-range command.
If system matches the start time of time-range interval, PSE will power off the PD, If system is
over the end time of time-range interval, PSE will restore the previous poe admin ability.
9.5 Validation
The result of show running-config is as follows.
time-range poeTimeRange
absolute start 12:12:12 Jun 13 2012 end 20:12:12 Jun 13 2012
!
interface eth-0-1
poe admin disable
poe budget 20000
poe admin disable time-range poeTimeRange
!
57
FSOS Device Management Configuration Guide
58
FSOS Device Management Configuration Guide
10 Configuring SmartConfig
10.1 Overview
SmartConfig is a smart method of switch initial configuration. After enabling SmartConfig,
switch will start to download configuration file or image file from tftp server ,if not finding
startup-config file at startup. Then switch will install these file ,and it will reboot itself if had
downloaded image file.
Note that we use deploy file to control the configuration file and image file downloaded by
switch. Switch fetch these file according the deploy file, which is a XML-formated file. The
deploy file named smartdeploy.xml , while its content like below:
<SmartDeploy>
<ftype>init</ftype>
<hostprefix>Bruce</hostprefix>
<defItem>
<option>enable</option>
<image>def.bin</image>
<config>def.cfg</config>
</defItem>
<groups>
59
FSOS Device Management Configuration Guide
<Item>
<type>MAC</type>
<value>001e.0808.9100</value>
<image>FSOS.bin</image>
<config>startup.cfg</config>
</Item>
<Item>
<type>productid</type>
<value>09SWITCH-E48-10</value>
<image>productid.bin</image>
<config>productid.cfg</config>
</Item>
<Item>
<type>SN</type>
<value>E054GD116004</value>
<image>sn.bin</image>
<config>sn.cfg</config>
</Item>
</groups>
</SmartDeploy>
There are three kind of item used by switch to find out image file and configuration file fit
itself. Switch will search fit item according sequence like MAC, SN , productid。We just
specify the file name in the deploy file, and place all these file on tftp server.
60
FSOS Device Management Configuration Guide
10.2 Topology
10.3 Configuration
Configuring Smartconfig
SmartConfig was enable default,so we just make sure there is no startup-config.conf file.
Then switch will start SmartConfig next boot. And we can delete startup-config.conf manually,
so that Smartconfig will work after reboot.
61
FSOS Device Management Configuration Guide
1 Configure smartdeploy.xml file,and place it with image file,configuration file to tftp server.
The directory must be like this :
/--
|--smartconfig/
|--conf/
|--images/
|--smartdeploy.xml
Configuration files should be in conf directory and images should be in images directory.
Smart-Config config:
initial-switch-deployment: on
hostname-prefix: on
62
FSOS Device Management Configuration Guide
11 Reboot Logs
11.1 Overview
FS switch support display reboot logs.Depand on these logs, user can judge the reboot reasons
of a switch.The reboot reasons include Manual Reboot, Power Off or Other Reasons.Also,
user can clear the reboot logs through a command.
11.2 Validation
The following example shows how to display reboot logs :
63
FSOS Device Management Configuration Guide
11.3 Warning
User can find no more than ten reboot logs through this command, to find more reboot logs,
can refer to the following file:flash:/reboot-info/reboot_info.log
64