L2MS (Layer2 Management Service)

1. Function Overview

L2MS (Layer2 Management Service) is functionality for managing Yamaha network devices at the layer 2 level.
L2MS consists of one L2MS manager unit (referred to as “manager” below) that performs centralized management and multiple L2MS agent units (referred to as “agents” below) that are controlled from the manager.
Devices can be used as either a manager or agent.

The following illustrates how to connect the computer, manager, and agents.

  • L2MS connection method
    image

Connect the computer to the manager via a serial connection or log in via Telnet or HTTP/HTTPS.
The manager includes commands for managing the agents and a web GUI for specifying the settings or checking the status of agents. These can be used to operate the agents.
The manager is connected to agents via Ethernet cables and uses a proprietary protocol (L2MS) for communication.

This functionality has the following characteristics.

  • Initial settings are not required
    Although IP addresses must be specified if using Telnet or SSH, initial settings do not need to be specified for agents, because the functionality uses a proprietary protocol (L2MS) for communication.
    When Ethernet cables are connected, the manager automatically recognizes subordinate agents.

  • Multiple supported terminals can be controlled simultaneously
    The manager can recognize and control multiple agents simultaneously.

The proprietary communication protocol used by L2MS is the same protocol as used for communication by the switch control functionality supported by Yamaha routers and SWX series and WLX series.
That means both SWX series and WLX series devices can be managed from the manager.

2. Definition of Terms Used

Manager

A manager is a device that manages Yamaha network devices functioning as an agent based on L2MS and switch control functionality.
It manages Yamaha network switches and Yamaha wireless access points within the network.

Agent

A Yamaha network switch or Yamaha wireless access point that is managed by a manager based on L2MS and switch control functionality.
Settings can be checked or changed from the manager.

3. Function Details

3.1. Compatible models

Devices can be used as either an L2MS manager or agent.

If operating as a manager, each manager can control a maximum of 128 agent units.
The following models can be managed as an agent.
As described earlier, any device that supports switch control functionality (agents) can also be controlled.

  • SWX2100 series (SWX2100-8G, SWX2100-16G, SWX2100-24G, SWX2100-5PoE, SWX2100-10PoE)

  • SWX2110 series (SWX2110-5G, SWX2110-8G, SWX2110-16G)

  • SWX2110P series (SWX2110P-8G)

  • SWX2200 series (SWX2200-8G, SWX2200-24G, SWX2200-8PoE)

  • SWX2210 series (SWX2210-8G, SWX2210-16G, SWX2210-24G)

  • SWX2210P series (SWX2210P-10G, SWX2210P-18G, SWX2210P-28G)

  • SWX2220 series (SWX2220-10NT, SWX2220-18NT, SWX2220-26NT)

  • SWX2221P series (SWX2221P-10NT)

  • SWX2220P series (SWX2220P-18NT, SWX2220P-26NT)

  • SWX2300 series (SWX2300-8G, SWX2300-16G, SWX2300-24G)

  • SWX2310 series (SWX2310-10G, SWX2310-18GT, SWX2310-28GT, SWX2310-52GT)

  • SWX2310P series (SWX2310P-10G, SWX2310P-18G, SWX2310P-28GT)

  • SWX2320 series (SWX2320-16MT)

  • SWX2322P series (SWX2322P-16MT)

  • SWX3100 series (SWX3100-10G, SWX3100-18GT)

  • SWX3200 series (SWX3200-28GT, SWX3200-52GT)

  • SWX3220 series (SWX3220-16MT, SWX3220-16TMs)

  • WLX series (WLX202, WLX212, WLX222, WLX302, WLX313, WLX322, WLX323, WLX402, WLX413)

If operated as an agent, the unit is managed by the Yamaha router or Yamaha network switch manager.
For details about compatible Yamaha router models, refer to Switch control functionality of Yamaha routers.

3.2. Usage

The L2MS operation and role are set by the l2ms command.

  • In the case of L2MS managers
    L2MS managers manage the SWX and WLX series switches operating as agents.
    The terminal-watch enable command can be used to periodically acquire and monitor information about computers and other terminals present in the network.

    Yamaha(config)#l2ms configuration
Yamaha(config-l2ms)#l2ms enable
Yamaha(config-l2ms)#l2ms role manager
Yamaha(config-l2ms)#terminal-watch enable

  • In the case of L2MS agents
    The unit is managed by the Yamaha router or Yamaha network switch operating as a manager.

    Yamaha(config)#l2ms configuration
Yamaha(config-l2ms)#l2ms enable
Yamaha(config-l2ms)#l2ms role agent

The show l2ms command can be used to check a current action and role of the agents.

3.3. L2MS protocol

L2MS control is performed using the proprietary protocol L2 frames indicated below.

  • Content of L2MS Protocol L2 Frames

    Item Value

    Destination MAC

    01:a0:de:00:e8:12 to 01:a0:de:00:e8:15

    Ethertype

    0xe812, 0xe813

If a firewall is specified between the manager and agents, the firewall settings must allow these L2 frames to pass through.

3.4. Monitoring agents

Managers monitor subordinate agents by sending query frames at regular intervals.
Agents respond to query frames by sending a response frame to notify the manager that they exist.

The interval between sending query frames is specified using the agent-watch interval command.
Increasing the setting value will decrease the sending frequency, but will lengthen the time for the manager to recognize an agent after it is contacted.
Decreasing the setting value will, conversely, increase the sending frequency, but shorten the time for the manager to recognize an agent after it is contacted.

If the manager does not receive a response frame from an agent after sending the specified number of query frames, the manager will decide that the corresponding agent has gone down.
The number of attempts is specified by the agent-watch down-count command.
If the Ethernet cable connected to the agent is disconnected, in some cases the manager might decide that the agent has gone down sooner than specified by the command.

Specify appropriate setting values for agent-watch interval and agent-watch down-count commands based on the given network environment being used.

3.5. Agent ownership

No agent may be simultaneously controlled by multiple managers.
Therefore, only specify one manager per network.

If an agent receives a query frame after rebooting, that agent will be managed by the manager that sent the query frame.
That relationship is canceled if any of the following occur.

  • A query frame is not received for 30 seconds.

  • The manager is rebooted.

  • The l2ms reset command is executed by the manager.

3.6. Agent operations

If a manager sets a setting for an L2MS-compliant agent or checks its operating status, such actions are referred to as “operating the agent”.
Agents are operated using the LAN map on the web GUI.
To operate an agent, log into the manager web GUI and select the applicable agent in the LAN map.

For more detailed LAN map operating instructions, refer to the web GUI help page.

Note that agents cannot be operated using commands executed by the manager.

The following describes how to operate each operable agent via the LAN map.

3.6.1. Operations for SWX2100 series units

The following operations can be performed for agents.

  • Display the status of the device and ports

  • Show and control the power supply status of ports (PoE-equipped models only)

  • Show/maintain network switch settings (show function settings, update firmware, restart, etc.)

3.6.2. Operations for SWX2110 and SWX2110P series units

The following operations can be performed for agents.

  • Display the status of the device and ports

  • Show and control the power supply status of ports (PoE-equipped models only)

  • Set/maintain network switch settings (change function settings, update firmware, reboot, etc.)

  • Set ports (VLAN tags, etc.)

  • Save and restore config settings

3.6.3. Operations for SWX2200 series units

The following operations can be performed for agents.

  • Display the status of the device and ports

  • Show and control the power supply status of ports (PoE-equipped models only)

  • Set/maintain network switch settings (change function settings, update firmware, reboot, etc.)

  • Save settings to the manager and synchronize settings with settings saved in the manager

If SWX2200 settings are set from the manager, the settings are saved in both the manager and SWX2200 unit.

The settings are saved as a separate file from the manager config file, but the startup-config select command can be used to change the config settings at the same time.

If the SWX2200 unit is managed by the manager, settings in the manager and SWX2200 unit will be kept synchronized.
For details on synchronization of settings, refer to 3.6.7 Synchronizing Settings.

The status of settings in SWX2200 units managed by the manager can be checked using the show l2ms agent-config command.

3.6.4. Operations for SWX2210, SWX2210P, SWX2220, SWX2221P, and SWX2220P series units

The following operations can be performed for agents.

  • Display the status of the device and ports

  • Show and control the power supply status of ports (PoE-equipped models only)

  • Change settings and perform maintenance (changing function settings, rebooting, etc.)

  • Specify port settings (tagged VLAN, multiple VLANs, etc.)

  • Specify link aggregation

  • Change the IP address setting

  • Save and restore config settings

  • Use HTTP proxy functionality to log into the agent GUI.

  • Find this switch (SWX2220/SWX2221P/SWX2220P models only)

If the HTTP proxy functionality is enabled, then it is possible to log into agent GUIs from the manager LAN map.
That eliminates the need to enter a username and password for logging into an agent.

If SWX2210, SWX2210P, SWX2220, SWX2221P, or SWX2220P series units are managed by a manager configured with factory settings, then DHCP client settings are specified automatically.
For more details, refer to “3.6.8. HTTP Proxy Function and Setting IP Addresses.” * The SWX2210 model supports Rev.1.02.10 and later firmware.
* The SWX2210P model supports Rev.1.03.08 and later firmware.

3.6.5. Operations for SWX2300, SWX2310, SWX2310P, SWX2320, SWX2322P, SWX3100, SWX3200, and SWX3220 series units

The following operations can be performed for agents.

  • Display the status of the device and ports

  • Show and control the power supply status of ports (PoE-equipped models only)

  • Change the IP address setting

  • Save and restore the config

  • Saving and restoring the config of the SWX2300 are supported by Rev.2.00.14 and later firmware.

  • Use HTTP proxy functionality to log into the agent GUI.

If the HTTP proxy functionality is enabled, then it is possible to log into agent GUIs from the manager LAN map.
That eliminates the need to enter a username and password for logging into an agent.

If an SWX2300/SWX2310/SWX2310P/SWX2320/SWX2322P/SWX3100/SWX3200/SWX3220 series unit is managed by a manager with factory settings, then DHCP client settings are specified automatically.
For more details, refer to “3.6.8. HTTP Proxy Function and Setting IP Addresses.”

3.6.6. Operations for WLX series units

The following operations can be performed for agents.

  • Display the status of devices, LAN ports, and wireless modules

  • Change the IP address setting

  • Save and restore config settings

  • Use HTTP proxy functionality to log into the agent GUI.

If the HTTP proxy functionality is enabled, then it is possible to log into agent GUIs from the manager LAN map.
That eliminates the need to enter a username and password for logging into an agent.

If a WLX series unit is managed by a manager configured with factory settings, then DHCP client settings are specified automatically.
For more details, refer to “3.6.8. HTTP Proxy Function and Setting IP Addresses.”

3.6.7. Synchronizing settings

If an SWX2200 unit is managed by a manager, then settings held in the manager and SWX2200 unit are kept synchronized.
Synchronization is unidirectional from the manager to the SWX2200 unit, with the SWX2200 unit always operating based on settings in the manager.

When the manager starts managing an SWX2200 unit, it first checks whether the manager and SWX2200 settings match.
If they do not match, the following processes are performed.

  1. All SWX2200 settings are restored to default values.

  2. Function setting values held by the manager are sent to the SWX2200 unit.

The manager periodically monitors the settings of subordinate SWX2200 units and synchronizes them if a discrepancy is detected.

Synchronization may take some time (several tens of seconds to several minutes).
During synchronization, other SWX2200 operations are disabled.
Attempting to specify settings will cause an error without applying the settings to the manager or SWX2200 unit.

3.6.8. HTTP Proxy Function and Setting IP Addresses

The following actions can be performed on SWX2300, SWX2310, SWX2310P, SWX2320, SWX2322P, SWX3100, SWX3200, or SWX3220 series or WLX series models.

In the factory default settings or the status immediately after execution of the cold start command, a fixed IP address is set. (L2MS functions as an agent.)
At this time, if the agent is managed by the manager, the DHCP client setting will automatically be configured.

This is to avoid duplicate IP addresses if multiple agents exist.
Since IP addresses are assigned by the DHCP server within the network, agent web GUIs can be accessed via the HTTP proxy server. However, that requires specifying the http-server enable setting in the agent.
If a DHCP server does not exist in the network, then IP addresses cannot be obtained and agent IP addresses must be specified on the manager LAN map.
Once the IP setting is specified and the startup config has been saved, it will not be automatically specified in the DHCP client thereafter.

3.7. Information notifications from agents

If an agent managed by a manager detects a change or error in its own status, it sends information to notify the manager.

Information sent from the agent is output in the manager SYSLOG or LAN map.
For details on messages output to the SYSLOG, refer to “7. SYSLOG Message List.”

The following information is included in notifications from agents.

  • Information in Notifications from Each Agent to the Manager

    Agent Information sent

    SWX2100 series

    Port link up/down
    Loop detection
    SFP optical RX level error (SWX2100-24G)
    Power supply function status for each port (PoE-equipped models only)
    Power supply function error for each device (PoE-equipped models only)

    SWX2110 series
    SWX2110P series

    Port link up/down
    Loop detection
    Power supply function status for each port (PoE-equipped models only)
    Power supply function error for each device (PoE-equipped models only)

    SWX2200 series SWX2210 series SWX2210P series SWX2220 series SWX2221P series SWX2220P series

    Port link up/down
    Loop detection
    Fan abnormal stop (SWX2200-24G, SWX2200-8PoE, SWX2210P, SWX2220-18NT/26NT, SWX2221P, SWX2220P)
    Power supply function status for each port (PoE-equipped models only)
    Power supply function error for each device (PoE-equipped models only)
    Temperature error (SWX2220-18NT/26NT, SWX2221P, SWX2220P)
    Terminal monitoring status (SWX2220, SWX2221P, SWX2220P)
    L2MS manager duplication (SWX2220, SWX2221P, SWX2220P)

    SWX2300 series

    Port link up/down
    Loop detection
    SFP optical RX level error
    Sending queue usage rate error

    SWX2310 series
    SWX2310P series
    SWX2320 series
    SWX2322P series
    SWX3100 series
    SWX3200 series
    SWX3220 series

    Port link up/down
    Stack port link up/down (stack-compatible models only)
    Loop detection
    SFP optical RX level error
    Sending queue usage rate error
    Power supply function status for each port (PoE-equipped models only)
    Power supply function error for each device (PoE-equipped models only)
    Temperature error (SWX2310-52GT, SWX2310P, SWX3200, SWX2320, SWX2322P, SWX3220)
    Fan error (SWX2310-52GT, SWX2310P, SWX3200, SWX2320, SWX2322P, SWX3220)
    Power supply error (SWX3200)
    Temperature sensor error (SWX2310P)
    Terminal monitoring status (operating or down)
    L2MS manager duplication

    WLX series

    Change in settings of the wireless function

3.8. Monitoring connected terminals

Specifying the terminal-watch enable command in the manager enables functionality for monitoring connected terminals, so that information about terminals connected to the manager and agents can be managed.
The manager manages the following information about connected terminals.

  • If the Manager and Agents are Yamaha Network Switches

    • Terminal MAC address

    • Manager or agent port number to which the terminal is connected

    • Date/time when terminal was detected

  • If the Agent is a Yamaha wireless access point

    • Terminal MAC address

    • SSID to which the terminal is connected

    • Frequency (2.4 or 5 GHz) of terminal connection

    • Date/time when terminal was detected

This information can be viewed using the show l2ms detail command.

The recommended maximum number of terminals managed by this function is 200 units, regardless of network configuration.
Note that more than the recommended number of units in the network could cause LAN map actions on the web GUI to be sluggish or unresponsive.

The manager will search for connected terminals or delete managed terminal information based on changes in the network.

The target and timing of manager searches for connected terminals are indicated below.
If new terminal information is found as a result of the search, it is determined that a terminal was detected.

  • Timing and Object of Terminal Searches

    Timing Terminal

    When the manager port is linked up

    Corresponding port on the manager

    When a new agent is detected

    All ports on the detected agent

    When link-up notification is received from a managed agent

    Corresponding port on the agent

    When the time specified by the terminal-watch interval command elapses

    The manager and all agents

The following indicates what managed terminal information is deleted and when it is deleted if the manager determines that the terminal has disappeared from a network.

  • Terminal for Which Information is Deleted and Deletion Timing

    Timing Terminal

    When the manager port is linked down

    Terminal connected to the corresponding manager port

    When an agent is detected to be down

    All terminals connected to that agent

    When a port link-down notification is received from a managed agent

    Terminal connected to the corresponding agent port

    When a previously-detected terminal is not found in connected terminal search

    Terminals not found

4. Related Commands

Related commands are indicated below.
For details, refer to the Command Reference.

  • List of L2MS-related commands

    Operations Operating commands

    Switch to L2MS mode

    l2ms configuration

    Enable L2MS function

    l2ms enable

    Set role of L2MS function

    l2ms role

    Set agent monitoring time interval

    agent-watch interval

    Set number of times for deciding agent is down

    agent-watch down-count

    Enable terminal management function

    terminal-watch enable

    Set terminal information acquisition interval

    terminal-watch interval

    Set terminal information acquisition interval for terminals below wireless AP

    wireless-terminal-watch interval

    Enable event monitoring function

    event-watch enable

    Set event information acquisition interval

    event-watch interval

    Enable sending/receiving L2MS control frames

    l2ms filter enable

    Set whether to use agent zero-config function

    config-auto-set enable

    Reset agent management

    l2ms reset

    Show L2MS information

    show l2ms

    Show L2MS agent configuration information

    show l2ms agent-config

    Enable snapshot function

    snapshot enable

    Include/remove terminal for snapshot comparison

    snapshot trap terminal

    Create snapshot

    snapshot save

    Delete snapshot

    snapshot delete

    Set LAN map log output

    logging event lan-map

5. Examples of Command Execution

5.1. Monitoring settings for agents

Set the agent monitoring time interval.

Yamaha(config)#l2ms configuration
Yamaha(config-l2ms)#agent-watch interval 8

Set the number of monitoring times before deciding an agent is down.

Yamaha(config)#l2ms configuration
Yamaha(config-l2ms)#agent-watch down-count 7

5.2. Enable terminal management function

Enable the terminal monitoring function.

Yamaha(config)#l2ms configuration
Yamaha(config-l2ms)#terminal-watch enable

Set the time interval for acquiring terminal information.

Yamaha(config)#l2ms configuration
Yamaha(config-l2ms)#terminal-watch interval 3600

Show the terminal information obtained by the manager.

Yamaha>show l2ms detail
Role : Manager

[Manager]
 Number of Terminals   : 0

[Agent]
 Number of Agents      : 2
  [ac44.f230.00a5]
   Model name          : SWX2100-24G
   Device name         : SWX2100-24G_Z5301050WX
   Route               : port2.1
   LinkUp              : 1, 3, 9
     Uplink            : 1
     Downlink          : 3
   Config              : None
   Appear time         : Tue Mar 13 18:43:18 2018
   Number of Terminals : 1
    [bcae.c5a4.7fb3]
     Port              : 9
     Appear time       : Wed Mar 14 14:01:18 2018

  [00a0.deae.b8bf]
   Model name          : SWX2300-24G
   Device name         : SWX2300-24G_S4L000401
   Route               : port2.1-3
   LinkUp              : 1
     Uplink            : 1
     Downlink          : None
   Config              : None
   Appear time         : Tue Mar 13 18:43:18 2018
   Number of Terminals : 0

5.3. Enable sending/receiving L2MS control frames

Disable sending or receiving L2MS control frames at port1.5.

Yamaha(config)#interface port1.5
Yamaha(config-if)#l2ms filter enable

5.4. Enable event monitoring function

Disable the event monitoring function.

Yamaha(config)#l2ms configuration
Yamaha(config-l2ms)#event-watch disable

Set the time interval between acquiring event information.

Yamaha(config)#l2ms configuration
Yamaha(config-l2ms)#event-watch interval 60

5.5. Enabling/disabling the zero-config function

This specifies whether the manager uses the zero-config function for agents.
This setting must be specified in the manager.

Disable the zero config function.

Yamaha(config)#l2ms configuration
Yamaha(config-l2ms)#l2ms enable
Yamaha(config-l2ms)#l2ms role manager
Yamaha(config-l2ms)#config-auto-set disable

6. Points of Caution

6.1. Device configuration

A maximum of 128 agents can be managed.

If the agents are used connected in series, a maximum of 8 agents can be connected from the manager.
Nine or more agents cannot be connected to the manager in series.
If up to 8 agents are connected in series from the manager, then the specified maximum number of managed agents can be controlled.

Connecting nine or more agents in series from the manager could prevent properly recognizing or controlling agents due to delays in L2MS communication or cause the following types of problems.

  • The synchronization process might not function correctly.

  • If agent settings are modified from the GUI, correct execution might not be possible.

If a non-Yamaha switch exists in the L2MS communication route, such as between the manager and an agent, it might not be possible to control the agent correctly.
If you are configuring a network that includes a non-Yamaha switch, verify its operation beforehand.

6.2. Terminal monitoring

The recommended maximum number of managed units in a network is 200 units.
Including more than the recommended maximum number of managed units could cause the LAN map in the Web GUI to become sluggish or unresponsive.
If necessary, disable the terminal management function (terminal-watch disable command).

Terminal searches use the information registered in the FDB (MAC address table) for the applicable devices.
Therefore, depending on when the search is performed, a connected terminal might not be detected or a terminal no longer in the network might be detected.

If a link is detected to be down for a manager or Yamaha network switch port, all information for the terminal connected to that port is deleted even if the terminal is registered in the FDB (MAC address table).

It may take L2MS several seconds to recognize an agent after it is connected to a port.
During that time, the corresponding agent is treated as a terminal.

Yamaha network devices that are not managed as an agent by the manager are treated as terminals.

Terminal searches performed at intervals specified by the terminal-watch interval command search for terminals connected to the manager or all agents, which might take twenty to thirty minutes to complete for some network configurations.
However, other processes are not disabled until terminal searches are completed.

If a non-Yamaha L2 switch is connected to an L2MS-compliant device, the terminals connected to the non-Yamaha L2 switch are detected as terminals connected to the L2MS-compliant device.
However, if a terminal and a Yamaha network switch are connected in parallel to a non-Yamaha L2 switch, the terminal connected to the non-Yamaha L2 switch cannot be detected.

6.3. Use in conjunction with other functionality

6.3.1. Use in conjunction with a VLAN

If using a VLAN, ports used for L2MS communication must be specified as an access port or as a trunk port assigned by the native VLAN.
L2MS communication is not possible via a trunk port not assigned by the native VLAN.

6.3.2. Use in conjunction with mirroring

If the mirroring function is used, L2MS communications sent and received at the monitor port are also copied.
Therefore, L2MS might not function properly if the manager or an agent is connected to a mirror port, so do not connect a manager or an agent to a mirror port.

6.3.3. Use in conjunction with an ACL

L2MS communication is not subject to ACL control.
Although the ACL discards frames that are not specified in the permissions list (tacit rejection), L2MS communications are not subject to ACL control, so frames are forwarded without being discarded.

6.3.4. Use in conjunction with STP or loop detection functionality

L2MS communication is not possible on ports blocked by STP or loop detection functionality.

Link switching by STP could prevent the manager from recognizing the topology correctly, which could prevent finding agents or cause routing errors when agents are found.
In such cases, reset agent management after STP has finished switching the link by executing the l2ms reset command.

If multiple MST instances are operating, L2MS control frames are sent and received on the logical route (tree) formed by CIST (instance #0).

6.3.5. Use in conjunction with link aggregation

If link aggregation is used, L2MS communication is considered to be occurring on “the lowest-numbered linked-up port associated with the logical interface”.
If link aggregation is used in conjunction with the monitoring function for connected terminals and a terminal is discovered at the end of a logical interface connection, then the terminal is considered to be connected to “the lowest-numbered linked-up port associated with the logical interface” and the corresponding port number is shown.

In Configuration 1, L2MS communication is assumed to be occurring between respective ports 1.1.
In Configuration 2, L2MS communication is assumed to be occurring between manager port 1.1 and agent port 1.1.

image

6.3.6. Use in conjunction with the stack function

L2MS functions if even one unit is operating.

Even if the stack function is enabled, it is operated as one standalone unit if it cannot negotiate with a member switch.
L2MS will function even in that case.

  • The L2MS manager can detect L2MS agents.

  • L2MS agents are detected by the L2MS manager.
    However, only devices connected below the standalone switch are detected, while not detecting devices connected to other network switches assumed to be down.

7. SYSLOG Message List

L2MS outputs the following SYSLOG messages.
Output messages appended with the “[ L2MS]” prefix.
SYSLOG messages displayed for units functioning as a manager are also appended with the "route (addr):"prefix.
“_route*” refers to the route and “addr” the agent MAC address (indicated in all lowercase, in the form “xxxx.xxxx.xxxx”).

  • SYSLOG Messages Displayed When the Unit Starts Up or the Operating Mode is Changed

    Category Output Level Message Meaning

    Operation mode

    informational

    Start L2MS(Manager)

    The L2MS unit was started as the manager.

    Start L2MS (agent)

    The L2MS unit is started as an agent.

    L2MS is disabled

    The L2MS did not start because it was disabled in settings.

    L2MS mode change mode_from to mode_to

    The operating mode is changed from mode_from to mode_to.

  • SYSLOG Messages Displayed When Operating as the Manager

    Category Output Level Message Meaning

    Agent management

    informational

    Find agent

    An agent was detected.

    Detect down

    An agent is down.

    Sync start

    informational

    Sync start

    Agent synchronization process was started.

    Sync done

    Agent synchronization process is finished.

    Sync failed

    Agent synchronization process failed.

    debug

    Can’t get param of sync

    Failed to obtain the agent information needed for synchronization process.

    Config Management

    informational

    Received config (file)

    The manager received and saved the config file (file) from the agent.

    Sent config (file)

    The manager sent the config file (file) to the agent.

    Removed config (file)

    The config file (file) was deleted.

    Device management

    debug

    Update device info

    Terminal information for the terminal connected to the agent was updated.

    Fail to update device info

    Failed to update terminal information for the terminal connected to the agent.

    Terminal Information Database Management

    debug

    _path* : Format Version: Not found.

    The format version is not indicated in the terminal information database file path.

    _path* : Format Version: Illegal value.

    An invalid value is included in the format version indicated in the terminal information database file path.

    _path* : Device Information: Illegal value. (line)

    An invalid value is indicated in the device information indicated in the terminal information database file path. (“_line*” line)

    _path* : Device Information: Duplicate device. (line)

    A conflicting device is indicated in device information in the terminal information database file path. (“_line*” line)

    _path* : Character Code: Not Shift_JIS.

    Non-Shift JIS characters are included in the character string code in the terminal information database file path.

    Manager Duplication

    informational

    L2MS manager duplication detected. (addr, port *X_)

    A duplicate L2MS manager was detected. (MAC address, port number where duplication was detected)

    L2MS manager duplication resolved. (addr, port *X_)

    The L2MS manager duplication was resolved. (MAC address, port number where duplication was detected)

  • SYSLOG messages are displayed appended with the prefix “[ LANMAP]” for devices operating as the manager if the logging event lan-map command was executed.

    Category Output Level Message Meaning

    Snapshot function

    informational

    SnapShot: Not found. [Device_Name: " *device_name_", MAC_Address: *addr_]

    There is a Yamaha switch that cannot be found.

    SnapShot: Not found. [MAC_Address: *addr_]

    There is a terminal that cannot be found.

    SnapShot: Unknown. [Device_Name: " *device_name_" , MAC_Address: *addr_]

    There is an unregistered Yamaha switch.

    SnapShot: Unknown. [MAC_Address: *addr_]

    There is an unregistered terminal.

    SnapShot: Route difference. [Device_Name: " *device_name_", Route: *route_(UpLink: *uplink_port_), Route(SnapShot): *route_snapshot_(UpLink: *uplink_port_snapshot_), MAC_Address: *addr_]

    A Yamaha network switch with a different connection port was found.
    The correct route is route_snapshot and the uplink port is *uplink_port_snapshot.

    SnapShot: Route difference. [Route: *route_, Route(SnapShot): *route_snapshot_, MAC_Address: *addr_]

    There is a terminal of a different connection port.
    The correct route is route_snapshot.

    SnapShot: Status recovered. [Device_Name: " *device_name_", MAC_Address: *addr_]

    The state of the Yamaha switch matches the snapshot.

    SnapShot: Status recovered. [MAC_Address: *addr_]

    The terminal status matched the snapshot file.

  • The manager receives the following information notifications from agents.

    Category Output Level Message Meaning

    Link status

    informational

    port N link up(10-hdx)

    Agent port N linked up at 10 Mbps half-duplex.

    port N link up(10-fdx)

    Agent port N linked up at 10 Mbps full-duplex.

    port N link up(100-hdx)

    Agent port N linked up at 100 Mbps full-duplex.

    port N link up(100-fdx)

    Agent port N linked up at 100 Mbps full-duplex.

    port N link up(1000-fdx)

    Agent port N linked up at 1 Gbps full-duplex.

    port N link up(2500-fdx)

    Agent port N linked up at 2.5 Gbps full-duplex.

    port N link up(5000-fdx)

    Agent port N linked up at 5 Gbps full-duplex.

    port N link up(10000-fdx)

    Agent port N linked up at 10 Gbps full-duplex.

    port N link down

    Agent port N linked down.

    stack port(port *N_) link up

    The agent stack port (port *N_) linked up.

    stack port(port *N_) link down

    The agent stack port (port *N_) linked down.

    Loop detection

    informational

    port N loop detect

    A loop has occurred at agent port N.

    sa N loop detect

    A loop has occurred at agent static logical interface # N.

    po N loop detect

    A loop has occurred at agent LACP logical interface # N.

    Wireless Functions

    informational

    Airlink setting changed

    An agent wireless functionality setting was changed.

    PoE

    informational

    port N PoE state(supply-class0)

    Power supply was started to a class0 device at agent port N.

    port N PoE state(supply-class1)

    Power supply was started to a class1 device at agent port N.

    port N PoE state(supply-class2)

    Power supply was started to a class2 device at agent port N.

    port N PoE state(supply-class3)

    Power supply was started to a class3 device at agent port N.

    port N PoE state(supply-class4)

    Power supply was started to a class4 device at agent port N.

    port N PoE state(supply-class5)

    Power supply was started to a class5 device at agent port N.

    port N PoE state(supply-class6)

    Power supply was started to a class6 device at agent port N.

    port N PoE state(supply-class7)

    Power supply was started to a class7 device at agent port N.

    port N PoE state(supply-class8)

    Power supply was started to a class8 device at agent port N.

    port N PoE state(terminate)

    Power supply was stopped at agent port N.

    port N PoE state(overcurrent)

    Power supply was stopped at agent port N because an overcurrent occurred.

    port N PoE state(forced-terminate)

    Power supply was stopped at ports where class 3 (15.4 W) power was supplied by supplying class 4 (30 W) power at agent port N.

    port N PoE state(over-supply)

    Power supply was stopped because the peak power supply rate exceeded the maximum supply capacity at agent port N.

    port N PoE state(over-temperature)

    Power supply was stopped because a temperature error occurred at agent port N.

    port N PoE state(fanlock)

    Power supply was stopped because the fan stopped at agent port N.

    port N PoE state(power-failure)

    Power supply was stopped because the power supply failure occurred at agent port N.

    port N PoE state(class-failure)

    Power supply was stopped because a higher than specified power supply class was detected at agent port N.

    PoE state(over-guardband)

    The agent power supply level entered the guardband range.

    port N PoE state(pd-failure)

    Power supply was stopped because a power input error was detected at agent port N.

    port N PoE state(guardband-restrict)

    Power supply was stopped because a power supply that exceeded the guardband was detected at agent port N.

    PoE state error(over-supply)

    The agent power supply exceeded the maximum power supply capacity.

    PoE state error(stop-supply)

    The agent power supply stopped.

    PoE state error(power-failure)

    An agent power supply error occurred.

    PoE state error(over-temperature, stop)
    Stack N PoE state error(over-temperature, stop)

    Power supply was stopped due to an agent temperature error.
    Power supply was stopped due to an agent (stack ID: *N_) temperature error.

    PoE state error(over-temperature, normal)
    Stack N PoE state error(over-temperature, normal)

    Power supply that stopped due to an agent temperature error was restored.
    Power supply stopped due to an agent (stack ID: *N_) temperature error was restored.

    PoE state error(fanlock, stop)
    Stack N PoE state error(fanlock, stop)

    Power supply was stopped because the agent fan stopped.
    Power supply was stopped because the agent (stack ID: *N_) fan stopped.

    PoE state error(fanlock, normal)
    Stack N PoE state error(fanlock, normal)

    Power supply stopped because an agent fan stopped was restored.
    Power supply stopped because an agent (stack ID: *N_) fan stopped was restored.

    PoE state error(power-failure, stop)
    Stack N PoE state error(power-failure, stop)

    Power supply was stopped due to an agent power supply abnormality.
    Power supply was stopped due to an agent (stack ID: *N_) power supply abnormality.

    SFP Optical RX Level

    informational

    port N SFP RX power(low)

    The SFP optical RX level decreased below the lower limit threshold value at agent port N.

    port N SFP RX power(high)

    The SFP optical RX level exceeded the upper limit threshold value at agent port N.

    port N SFP RX power(normal)

    The SFP optical RX level at agent port N returned to normal.

    Send Queue Usage

    informational

    port N queue Q usage rate(busy)

    The sending load at agent port N is high (QoS transmission queue: *Q_)

    port N queue Q usage rate(full)

    The sending load at agent port N reached the upper limit (QoS transmission queue: *Q_)

    port N queue Q usage rate(recovered)

    The sending load at Agent port N returned to normal (QoS transmission queue: *Q_)

    Terminal Monitoring

    informational

    ping: *ip-address_(description) state(DOWN)

    Ping monitoring indicated *ip-address_(description) has gone down.

    ping: *ip-address_(description) state(UP)

    ping monitoring indicated *ip-address_(description) is now operating.

    ping: *ip-address_(description) state(IDLE)

    ip-address(description) is not being monitored by ping monitoring.

    Frame Counter: *port_(description) state(DOWN)

    Monitoring according to frame reception volume indicates *port_(description) has gone down.

    Frame Counter: *port_(description) state(UP)

    Monitoring according to frame reception volume indicates *port_(description) is now operating.

    Frame Counter: *port_(description) state(IDLE)

    port(description) is not being monitored according to frame reception volume.

    LLDP: *port_(description) state(DOWN)

    LLDP frame monitoring indicates *port_(description) has gone down.

    LLDP: *port_(description) state(UP)

    LLDP frame monitoring indicates *port_(description) is now operating.

    LLDP: *port_(description) state(IDLE)

    port(description) is not being monitored by LLDP frame monitoring.

    Power supply

    informational

    Power voltage(high)
    Stack N Power voltage(high)

    The agent power supply voltage exceeded the upper threshold value.
    The agent (stack ID: *N_) power supply voltage exceeded the upper threshold value.

    Power current(high)
    Stack N Power current(high)

    An overcurrent occurred in the agent power supply.
    An overcurrent occurred in the agent (stack ID: *N_) power supply.

    Fan

    informational

    Fan lock

    The agent fan stopped.

    FAN control(high)
    Stack N FAN control(high)

    The agent fan rpm increased.
    The agent (stack ID: *N_) fan rpm increased.

    FAN control(low)
    Stack N FAN control(low)

    The agent fan rpm decreased.
    The agent (stack ID: *N_) fan rpm decreased.

    FAN X (stop)
    Stack N FAN X (stop)

    The agent fan (FAN *X_) stopped.
    The agent (stack ID: *N_) fan (FAN *X_) stopped.

    FAN X (normal)
    Stack N FAN X (normal)

    The agent fan (FAN *X_) was restored.
    The agent (stack ID: *N_) fan (FAN *X_) was restored.

    Temperature

    informational

    CPU temperature(high)
    Stack N CPU temperature(high)

    The agent CPU temperature exceeded the threshold value.
    The agent (stack ID: *N_) CPU temperature exceeded the threshold value.

    CPU temperature(normal)
    Stack N CPU temperature(normal)

    The agent CPU temperature returned to normal.
    The agent (stack ID: *N_) CPU temperature returned to normal.

    CPU temperature error(alarm)
    Stack N CPU temperature error(alarm)

    An agent CPU temperature error occurred.
    The agent (stack ID: *N_) CPU temperature error occurred.

    CPU temperature error(normal)
    Stack N CPU temperature error(normal)

    The agent CPU temperature error was resolved.
    The agent (stack ID: *N_) CPU temperature error was resolved.

    PHY temperature(high)
    Stack N PHY temperature(high)

    The agent PHY temperature exceeded the threshold value.
    The agent (stack ID: *N_) PHY temperature exceeded the threshold value.

    PHY temperature(normal)
    Stack N PHY temperature(normal)

    The agent PHY temperature returned to normal.
    The agent (stack ID: *N_) PHY temperature returned to normal.

    PHY temperature error(alarm)
    Stack N PHY temperature error(alarm)

    An agent PHY temperature error occurred.
    The agent (stack ID: *N_) PHY temperature error occurred.

    PHY temperature error(normal)
    Stack N PHY temperature error(normal)

    The agent PHY temperature error was resolved.
    The agent (stack ID: *N_) PHY temperature error was resolved.

    SFP temperature(high)
    Stack N SFP temperature(high)

    The agent SFP module temperature exceeded the threshold value.
    The agent (stack ID: *N_) SFP module temperature exceeded the threshold value.

    SFP temperature(normal)
    Stack N SFP temperature(normal)

    The agent SFP module temperature returned to normal.
    The agent (stack ID: *N_) SFP module temperature returned to normal.

    SFP temperature error(alarm)
    Stack N SFP temperature error(alarm)

    An agent SFP module temperature error occurred.
    The agent (stack ID: *N_) SFP module temperature error occurred.

    SFP temperature error(normal)
    Stack N SFP temperature error(normal)

    The agent SFP module temperature error was resolved.
    The agent (stack ID: *N_) SFP module temperature error was resolved.

    Unit temperature(high)
    Stack N Unit temperature(high)

    The agent unit temperature exceeded the threshold value.
    The agent (stack ID: *N_) unit temperature exceeded the threshold value.

    Unit temperature(normal)
    Stack N Unit temperature(normal)

    The agent unit temperature returned to normal.
    The agent (stack ID: *N_) unit temperature returned to normal.

    Unit temperature error(alarm)
    Stack N Unit temperature error(alarm)

    A temperature error occurred in an agent unit.
    The agent (stack ID: *N_) unit temperature error occurred.

    Unit temperature error(normal)
    Stack N Unit temperature error(normal)

    The temperature error in the agent unit was resolved.
    The agent (stack ID: *N_) unit temperature error was resolved.

    PSE temperature(high)
    Stack N PSE temperature(high)

    The agent PSE temperature exceeded the threshold value.
    The agent (stack ID: *N_) PSE temperature exceeded the threshold value.

    PSE temperature(normal)
    Stack N PSE temperature(normal)

    The agent PSE temperature returned to normal.
    The agent (stack ID: *N_) PSE temperature returned to normal.

    PSE temperature error(alarm)
    Stack N PSE temperature error(alarm)

    An agent PSE temperature error occurred.
    The agent (stack ID: *N_) PSE temperature error occurred.

    PSE temperature error(normal)
    Stack N PSE temperature error(normal)

    The agent PSE temperature error was resolved.
    The agent (stack ID: *N_) PSE temperature error was resolved.

    MAC temperature(high)
    Stack N MAC temperature(high)

    The agent MAC temperature exceeded the threshold value.
    The agent (stack ID: *N_) MAC temperature exceeded the threshold value.

    MAC temperature(normal)
    Stack N MAC temperature(normal)

    The agent MAC temperature returned to normal.
    The agent (stack ID: *N_) MAC temperature returned to normal.

    MAC temperature error(alarm)
    Stack N MAC temperature error(alarm)

    An agent MAC temperature error occurred.
    The agent (stack ID: *N_) MAC temperature error occurred.

    MAC temperature error(normal)
    Stack N MAC temperature error(normal)

    The agent MAC temperature error was resolved.
    The agent (stack ID: *N_) MAC temperature error was resolved.

    Thermal sensor(alarm)
    Stack N Thermal sensor(alarm)

    An agent temperature sensor error occurred.
    The agent (stack ID: *N_) temperature sensor error occurred.

    Config Management

    informational

    Executing a config …​ progress % (file)

    Agent config file (file) settings are being restored. (progress%).

    Finished executing a config (file)

    Finished restoring the agent config file (file).

    line: errmsg (file)

    An errmsg error occurred on line line while restoring the agent config file (file).

    Manager Duplication

    informational

    l2ms-manager-duplication(occur). (addr, port *X_)

    A duplicate L2MS manager was detected at an agent. (MAC address, port number where duplication was detected)

    l2ms-manager-duplication(stop). (addr, port *X_)

    The L2MS manager duplication at the agent was resolved. (MAC address, port number where duplication was detected)

    Function

    informational

    unsupported function(function)

    The agent firmware does not support the corresponding protocol.
    The _function* part shows one of the following:
    　Setting info
    　Status l2ms info
    　SFP RX power
    　Qos queue rate
    　Qos queue rate2
    　Terminal monitoring
    　System monitoring
    Note: Only output the first time after the “Find agent” message. The log output is suppressed after the first time.
    These are reset once link down is detected.

  • SYSLOG Messages Displayed When Operating as an Agent

    Category Output Level Message Meaning

    Agent management

    infromational

    Start management by manager(addr)

    Agent is now managed by the manager.

    Release from manager(addr)

    Agent is no longer managed by the manager.

    Restart

    informational

    Restart by manager request.

    This restarts the network switch as requested by a manager.

    Config Management

    infromational

    Sent config to manager (addr)

    Config file was sent to the manager.

    Received config from manager (addr)

    Config file was received from the manager.

    Restart for update settings.

    The unit will restart in order to update the received config file.

    Manager Duplication

    informational

    L2MS manager duplication detected. (addr, port *X_)

    A duplicate L2MS manager was detected. (MAC address, port number where duplication was detected)

    L2MS manager duplication resolved. (addr, port *X_)

    The L2MS manager duplication was resolved. (MAC address, port number where duplication was detected)

8. Related Documentation