L2MS (Layer2 Management Service)
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 manager that performs centralized control and multiple agents that are controlled by the manager.
The SWX2210P functions as an L2MS agent.
The following illustrates how to connect the computer, manager, and agents.
-
L2MS connection method
The L2MS 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 for communication.
This functionality has the following characteristics.
-
Initial settings are not required
Although IP addresses must be specified if using Telnet or SSH, default settings do not need to be specified for agents, because the functionality uses a proprietary protocol 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.
For details on the managers that can manage the SWX2210P, refer to the technical information on each L2MS 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
For manages that can manage the SWX2210P as an agent, see the link below.
3.2. 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
If a firewall is specified between the manager and agents, the firewall settings must allow these L2 frames to pass through.
Also, when using Yamaha LAN Monitor to update the SWX2210P series firmware with L2MS, use the following unicast L2MS.
-
Content of Unicast L2MS Protocol L2 Frames
Item Value Destination MAC
Unicast destination MAC address
Ethertype
0xe813
3.3. 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.
For the settings for query frames to be sent by the manager, refer to the technical information on the manager.
3.4. 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.
-
The agent has not received a query frame for 30 seconds
-
The manager is restarted, or the management status of the L2MS is reset
3.5. 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”.
Each manager is provided with commands and a web GUI for operating the agents.
For detailed operating instructions, refer to the technical information on each manager.
3.6. 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 web GUI.
For details, refer to the technical information on each manager.
The following information is included in notifications from the SWX2210P.
-
Port link up/down status
-
Loop detection
-
Fan stopped due to error
-
Per-port power supply function status
-
Per-device power supply function error
3.7. L2MS filter/non-L2MS filter
By using the L2MS filter function, you can prohibit the transmission and reception of L2MS control frames used for L2MS control.
By using the non-L2MS filter function, you can also restrict the transmission and reception of frames other than L2MS control frames.
The L2MS filter and non-L2MS filter can be set on a per-port basis. When setting them, use the l2ms filter command and non-l2ms filter command, respectively.
3.8. Enabling/disabling L2MS
You can enable/disable L2MS using the l2ms enable and l2ms disable commands.
If L2MS is disabled, L2MS control frames are forwarded in the same way as frames other than L2MS control frames, and they can no longer be managed by the L2MS manager.
L2MS is enabled by default.
3.9. Default IP address
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.
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.
4. Related Commands
Related commands are indicated below.
For details, refer to the Command Reference.
-
Basic interface functions: list of related commands
Operations Operating commands Switch to L2MS mode
l2ms configuration
Enable L2MS function
l2ms enable
Enable sending/receiving L2MS control frames
l2ms filter
Enable sending/receiving frames other than L2MS control frames
non-l2ms filter
Show L2MS information
show l2ms
5. Examples of Command Execution
5.1. L2MS filter setting
-
Disable sending or receiving L2MS control frames at LAN port #1 (port1.1).
Yamaha(config)#interface port1.1 Yamaha(config-if)#l2ms filter enable
5.2. L2MS setting
-
Disable L2MS so that it cannot be managed by the L2MS manager.
Yamaha(config)#l2ms configuration Yamaha(config-l2ms)#l2ms disable
6. Points of Caution
For precautions on using L2MS, refer to the technical information on each manager.
6.1. Use in conjunction with other functionality
6.1.1. Use in conjunction with loop detection functionality
L2MS communication is not possible on ports blocked by loop detection functionality.
6.1.2. Use in conjunction with link aggregation
If link aggregation is used, L2MS communication is considered to be occurring on “the lowest-numbered linked-up LAN 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 LAN 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.
6.1.3. Using switch control commands of router L2MS managers
The switch control commands of router L2MS managers are commands for the SWX2200 series. These commands do not support use on the SWX2210P series.
However, power supply control using the switch control function execute start-poe-supply command and the switch control function execute stop-poe-supply command is supported.
7. SYSLOG Message List
L2MS outputs the following SYSLOG messages.
Output messages appended with the “[ L2MS]” prefix.
Output Level | Message | Meaning |
---|---|---|
Informational |
Start L2MS (agent) |
The L2MS unit is started as an agent. |
Start management by manager (<Manager_MAC_Address>) |
Agent is placed under the control of the manager. |
|
Release from manager (<Manager_MAC_Address>) |
Agent is no longer managed by the manager. |
|
Received config from manager (<Manager_MAC_Address>) |
CONFIG is received from the manager. |
|
Restart for update settings. |
CONFIG received from the manager is reflected and the system is restarted. |
|
Send config to manager (<Manager_MAC_Address>) |
CONFIG is sent to the manager. |