<div id="gui_en_common_about_page"><div class="search_title" docfname="gui_en_common_about_page" doctitle="About" link="#title-box">About each screen</div><div class="search_word">about each screen</div><div class="display_word">About each screen</div></div><div id="gui_en_common_about_page"><div class="search_title" docfname="gui_en_common_about_page" doctitle="About" link="#dashboard">1. Dashboard</div><div class="search_word">1. dashboard it shows the various system information of this device in visual form. you can check and monitor the following status. interface information system information resource information ( cpu utilization / memoryutilization ) syslog terminal monitoring traffic information ( transmit / reception ) resource information ( graph ) stack information poe power supply</div><div class="display_word">1. Dashboard It shows the various system information of this device in visual form. You can check and monitor the following status. Interface information System information Resource information ( CPU Utilization / MemoryUtilization ) SYSLOG Terminal monitoring Traffic information ( Transmit / Reception ) Resource information ( Graph ) Stack information PoE power supply</div></div><div id="gui_en_common_about_page"><div class="search_title" docfname="gui_en_common_about_page" doctitle="About" link="#lan_map">2. LAN MAP</div><div class="search_word">2. lan map in this page you can view, manage, and make settings for the yamahanetwork devices managed by the lan interface, and any equipment underits management. the lan map is shown only if this unit is operating as a manager.</div><div class="display_word">2. LAN MAP In this page you can view, manage, and make settings for the Yamahanetwork devices managed by the LAN interface, and any equipment underits management. The LAN map is shown only if this unit is operating as a manager.</div></div><div id="gui_en_common_about_page"><div class="search_title" docfname="gui_en_common_about_page" doctitle="About" link="#detail">3. Detailed settings</div><div class="search_word">3. detailed settings in this page you can make detailed network-related settings for this unit. the following items are provided. interface settings physical interface port mirroring link aggregation port authentication port authentication settings server settings authentication management web authentication screen poe l2ms filter tx queue usage monitoring vlan create vlan tag vlan multiple vlan layer 2 functions mac address table spanning tree loop detection pass through dhcp snooping layer 3 functions dns client routing multicast multicast basic settings igmp snooping mld snooping traffic control access list create access list apply access list qos flow control storm control application layer radius server server settings user management managing certificates</div><div class="display_word">3. Detailed settings In this page you can make detailed network-related settings for this unit. The following items are provided. Interface settings Physical interface Port mirroring Link aggregation Port authentication Port authentication settings Server settings Authentication management Web authentication screen PoE L2MS filter Tx queue usage monitoring VLAN Create VLAN Tag VLAN Multiple VLAN Layer 2 functions MAC address table Spanning tree Loop detection Pass through DHCP snooping Layer 3 functions DNS client Routing Multicast Multicast basic settings IGMP snooping MLD snooping Traffic control Access list Create Access list Apply Access list QoS Flow control Storm control Application layer RADIUS server Server settings User management Managing certificates</div></div><div id="gui_en_common_about_page"><div class="search_title" docfname="gui_en_common_about_page" doctitle="About" link="#management">4. Management</div><div class="search_word">4. management in this page you can make settings for this unit, and perform maintenance. the following items are provided. unit settings access management user settings various server settings external devices microsd schedule execution snmp mib community snmpv3 user snmp trap rmon rmon settings event group alarm group sflow lldp mail notification terminal monitoring dante optimization y-unos maintenance command execution system self-diagnostics cable diagnostics update firmware config management summary data management syslog management backup / restoration restart and initialization find this switch</div><div class="display_word">4. Management In this page you can make settings for this unit, and perform maintenance. The following items are provided. Unit settings Access management User settings Various server settings External devices microSD Schedule execution SNMP MIB Community SNMPv3 User SNMP trap RMON RMON settings Event group Alarm group sFlow LLDP Mail notification Terminal monitoring Dante optimization Y-UNOS Maintenance Command execution System self-diagnostics Cable diagnostics Update firmware CONFIG management Summary data management SYSLOG management Backup / Restoration Restart and initialization Find this switch</div></div><div id="gui_en_common_about_page"><div class="search_title" docfname="gui_en_common_about_page" doctitle="About" link="#webconsole">5. CONSOLE</div><div class="search_word">5. console you can access the console screen from the "console" menu. a newbrowser window opens, and a login prompt appears. enter your usernameand password to log in. constraints the key input does not work correctly in safari for macos. please use a browser (chrome, edge, firefox) other than safari. launching multiple web consoles is not supported. if you open a new web console, the current session is disconnected. there are the following restrictions when accessing an l2ms agent’s web console from the lan map via an http proxy. if the l2ms manager is a router, it is not supported. if the l2ms manager is a switch, make sure that the firmware supports the web console. do not launch multiple web consoles. you may temporarily lose access to the web gui of the l2ms manager. about copy and paste you can copy text to the clipboard by pressing "ctrl+c" after selecting the text. "copy" and "paste" functions in the right-click menu are available only on the web console screen. you can paste text from the clipboard by selecting "paste from browser" from the right-click menu.</div><div class="display_word">5. CONSOLE You can access the console screen from the "CONSOLE" menu. A newbrowser window opens, and a login prompt appears. Enter your usernameand password to log in. Constraints The Key input does not work correctly in Safari for macOS. Please use a browser (Chrome, Edge, Firefox) other than Safari. Launching multiple web consoles is not supported. If you open a new web console, the current session is disconnected. There are the following restrictions when accessing an L2MS agent’s web console from the LAN map via an HTTP proxy. If the L2MS manager is a router, it is not supported. If the L2MS manager is a switch, make sure that the firmware supports the web console. Do not launch multiple web consoles. You may temporarily lose access to the Web GUI of the L2MS manager. About copy and paste You can copy text to the clipboard by pressing "Ctrl+C" after selecting the text. "Copy" and "Paste" functions in the right-click menu are available only on the Web Console screen. You can paste text from the clipboard by selecting "Paste from browser" from the right-click menu.</div></div><div id="gui_en_common_about_page"><div class="search_title" docfname="gui_en_common_about_page" doctitle="About" link="#config">6. CONFIG</div><div class="search_word">6. config the results of running the "show running-config" command (a setting of this unit) can be viewed in a web browser or acquired as a text file. viewing config in the "config" menu, press the "show in browser" button. theexecution result of the "show running-config" command is shown in asub-window. to close, press the web browser’s close button. obtaining config as a text file in the "config" menu, press the "obtain as text file" button to start the download automatically. the name of the acquired file is "running-config_yyyymmddhhmmss.txt". yyyy a.d. ( 4 digit ) mm month ( 2 digit ) dd day ( 2 digit ) hh hours ( 2 digit ) mm minutes ( 2 digit ) ss seconds ( 2 digit )</div><div class="display_word">6. CONFIG The results of running the "show running-config" command (a setting of this unit) can be viewed in a web browser or acquired as a text file. Viewing CONFIG In the "CONFIG" menu, press the "Show in browser" button. Theexecution result of the "show running-config" command is shown in asub-window. To close, press the web browser’s close button. Obtaining CONFIG as a text file In the "CONFIG" menu, press the "Obtain as text file" button to start the download automatically. The name of the acquired file is "running-config_YYYYMMDDhhmmss.txt". YYYY A.D. ( 4 Digit ) MM Month ( 2 Digit ) DD Day ( 2 Digit ) hh Hours ( 2 Digit ) mm Minutes ( 2 Digit ) ss Seconds ( 2 Digit )</div></div><div id="gui_en_common_about_page"><div class="search_title" docfname="gui_en_common_about_page" doctitle="About" link="#syslog">7. SYSLOG</div><div class="search_word">7. syslog this feature outputs the log of this unit’s operation status in the order of the oldest occurrence time. in the "syslog" menu, the result of running the show logging command can be viewed in a web browser or acquired as a text file. viewing syslog in the "syslog" menu, press the "show in browser" button. theexecution result of the "show logging" command is shown in a sub-window. to close, press the web browser’s close button. obtaining syslog as a text file in the "syslog" menu, press the "obtain as text file" button to start the download automatically. the name of the acquired file is "running-config_yyyymmddhhmmss.txt". yyyy a.d. ( 4 digit ) mm month ( 2 digit ) dd day ( 2 digit ) hh hours ( 2 digit ) mm minutes ( 2 digit ) ss seconds ( 2 digit ) constraints if the stack function is enabled, only the syslog of the main switch can be displayed.</div><div class="display_word">7. SYSLOG This feature outputs the log of this unit’s operation status in the order of the oldest occurrence time. In the "SYSLOG" menu, the result of running the show logging command can be viewed in a web browser or acquired as a text file. Viewing SYSLOG In the "SYSLOG" menu, press the "Show in browser" button. Theexecution result of the "show logging" command is shown in a sub-window. To close, press the web browser’s close button. Obtaining SYSLOG as a text file In the "SYSLOG" menu, press the "Obtain as text file" button to start the download automatically. The name of the acquired file is "running-config_YYYYMMDDhhmmss.txt". YYYY A.D. ( 4 Digit ) MM Month ( 2 Digit ) DD Day ( 2 Digit ) hh Hours ( 2 Digit ) mm Minutes ( 2 Digit ) ss Seconds ( 2 Digit ) Constraints If the stack function is enabled, only the SYSLOG of the main switch can be displayed.</div></div><div id="gui_en_common_about_page"><div class="search_title" docfname="gui_en_common_about_page" doctitle="About" link="#techinfo">8. TECHINFO</div><div class="search_word">8. techinfo the "show tech-support" command lets you view status information for all of this unit’s functions. in the "techinfo" menu, the results of running the "show tech-support"command can be viewed in a web browser or acquired as a text file. viewing technifo in the "techinfo" menu, press the "show in browser" button. the execution result of the "show tech-support" command is shown. to close, press the web browser’s close button. obtaining technifo as a text file in the "techinfo" menu, press the "obtain as text file" button to start the download automatically. the name of the acquired file is "technifo_yyyymmddhhmmss.txt". yyyy a.d. ( 4 digit ) mm month ( 2 digit ) dd day ( 2 digit ) hh hours ( 2 digit ) mm minutes ( 2 digit ) ss seconds ( 2 digit ) notes it may take some time to obtain technifo. this unit may undergo loading while the information is being acquired.</div><div class="display_word">8. TECHINFO The "show tech-support" command lets you view status information for all of this unit’s functions. In the "TECHINFO" menu, the results of running the "show tech-support"command can be viewed in a web browser or acquired as a text file. Viewing TECHNIFO In the "TECHINFO" menu, press the "Show in browser" button. The execution result of the "show tech-support" command is shown. To close, press the web browser’s close button. Obtaining TECHNIFO as a text file In the "TECHINFO" menu, press the "Obtain as text file" button to start the download automatically. The name of the acquired file is "technifo_YYYYMMDDhhmmss.txt". YYYY A.D. ( 4 Digit ) MM Month ( 2 Digit ) DD Day ( 2 Digit ) hh Hours ( 2 Digit ) mm Minutes ( 2 Digit ) ss Seconds ( 2 Digit ) Notes It may take some time to obtain TECHNIFO. This unit may undergo loading while the information is being acquired.</div></div><div id="gui_en_common_introduction"><div class="search_title" docfname="gui_en_common_introduction" doctitle="Introduction" link="#title-box">Introduction</div><div class="search_word">introduction</div><div class="display_word">Introduction</div></div><div id="gui_en_common_introduction"><div class="search_title" docfname="gui_en_common_introduction" doctitle="Introduction" link="#about_gui">1. What you can do using the Web GUI</div><div class="search_word">1. what you can do using the web gui the web gui lets you perform basic settings and management of theyamaha switch (this unit). the web gui contains the following screensfor you to make settings and perform management. dashboard lan map detailed settings management console config syslog techinfo</div><div class="display_word">1. What you can do using the Web GUI The web GUI lets you perform basic settings and management of theYamaha switch (this unit). The web GUI contains the following screensfor you to make settings and perform management. Dashboard LAN MAP Detailed settings Management CONSOLE CONFIG SYSLOG TECHINFO</div></div><div id="gui_en_common_introduction"><div class="search_title" docfname="gui_en_common_introduction" doctitle="Introduction" link="#environment">2. Operating environment</div><div class="search_word">2. operating environment here we explain the environment that is required in order to use the web gui.</div><div class="display_word">2. Operating environment Here we explain the environment that is required in order to use the web GUI.</div></div><div id="gui_en_common_introduction"><div class="search_title" docfname="gui_en_common_introduction" doctitle="Introduction" link="#recommended_web_browser">2.1. Recommended web browser</div><div class="search_word">2.1. recommended web browser we recommend the following web browser for use with the web gui. windows microsoft edge google chrome mozilla firefox mac apple safari ipados apple safari the latest version of each browser is recommended. microsoft internet explorer is not supported. <note> do not use the "back" or "forward" buttons of the web browser. in some cases, the display layout of a page may become disordered. if this occurs, please access that page once again. <memo> the web gui uses utf-8 character encoding.</div><div class="display_word">2.1. Recommended web browser We recommend the following web browser for use with the web GUI. Windows Microsoft Edge Google Chrome Mozilla Firefox Mac Apple Safari iPadOS Apple Safari The latest version of each browser is recommended. Microsoft Internet Explorer is not supported. <NOTE> Do not use the "Back" or "Forward" buttons of the web browser. In some cases, the display layout of a page may become disordered. If this occurs, please access that page once again. <Memo> The web GUI uses UTF-8 character encoding.</div></div><div id="gui_en_common_introduction"><div class="search_title" docfname="gui_en_common_introduction" doctitle="Introduction" link="#javascript_settings">2.2. JavaScript settings</div><div class="search_word">2.2. javascript settings the web gui uses javascript. if your web browser is set to disablejavascript, you might be unable to use the web gui.if javascript isdisabled, please enable javascript in your web browser before use.</div><div class="display_word">2.2. JavaScript settings The web GUI uses JavaScript. If your web browser is set to disableJavaScript, you might be unable to use the web GUI.If JavaScript isdisabled, please enable JavaScript in your web browser before use.</div></div><div id="gui_en_common_introduction"><div class="search_title" docfname="gui_en_common_introduction" doctitle="Introduction" link="#cookie_settings">2.3. Cookie settings</div><div class="search_word">2.3. cookie settings the web gui uses cookies. if your web browser is set to disablecookies, you might be unable to use the web gui.please allow cookies inyour web browser before use.</div><div class="display_word">2.3. Cookie settings The web GUI uses cookies. If your web browser is set to disablecookies, you might be unable to use the web GUI.Please allow cookies inyour web browser before use.</div></div><div id="gui_en_common_introduction"><div class="search_title" docfname="gui_en_common_introduction" doctitle="Introduction" link="#access_auth">3. User access rights</div><div class="search_word">3. user access rights users who log in to the web gui are divided into two types: generalusers and administrative users. these are referred to as "accesslevels." the differences between the access levels are described below. for general users can view the settings of the unit, operate the web console, and obtain syslog. cannot change the settings. for administrative users can view and change the settings of the unit. can obtain config andtechinfo in addition to operating the web console and obtaining syslog.</div><div class="display_word">3. User access rights Users who log in to the web GUI are divided into two types: generalusers and administrative users. These are referred to as "accesslevels." The differences between the access levels are described below. For general users Can view the settings of the unit, operate the Web console, and obtain SYSLOG. Cannot change the settings. For administrative users Can view and change the settings of the unit. Can obtain CONFIG andTECHINFO in addition to operating the Web console and obtaining SYSLOG.</div></div><div id="gui_en_common_introduction"><div class="search_title" docfname="gui_en_common_introduction" doctitle="Introduction" link="#note">4. Note when using together with command input</div><div class="search_word">4. note when using together with command input settings for this unit can be made not only via the web gui but alsofrom the command console screen by directly entering commands. commandinput allows a broader range of settings than when using the web gui,and also lets you make settings for functions that are not supported inthe web gui. if you use both command input and the web gui to makesettings, be aware that the commands that you input may be overwritten,or the settings may be cleared. <memo> the command console screen contains the following items. management → "maintenance" → "command execution" for details on commands, refer to "command reference."</div><div class="display_word">4. Note when using together with command input Settings for this unit can be made not only via the web GUI but alsofrom the command console screen by directly entering commands. Commandinput allows a broader range of settings than when using the web GUI,and also lets you make settings for functions that are not supported inthe web GUI. If you use both command input and the web GUI to makesettings, be aware that the commands that you input may be overwritten,or the settings may be cleared. <Memo> The command console screen contains the following items. Management → "Maintenance" → "Command execution" For details on commands, refer to "Command reference."</div></div><div id="gui_en_common_introduction"><div class="search_title" docfname="gui_en_common_introduction" doctitle="Introduction" link="#language">5. Language</div><div class="search_word">5. language the web gui allows you to switch the display language.to switch the display language, press the "language switch" button on the top menu, and select a language you want. the supported languages are as follows. japanese english</div><div class="display_word">5. Language The Web GUI allows you to switch the display language.To switch the display language, press the "Language Switch" button on the top menu, and select a language you want. The supported languages are as follows. Japanese English</div></div><div id="gui_en_common_login_logout"><div class="search_title" docfname="gui_en_common_login_logout" doctitle="Login/Logout" link="#title-box">Login/Logout</div><div class="search_word">login/logout</div><div class="display_word">Login/Logout</div></div><div id="gui_en_common_login_logout"><div class="search_title" docfname="gui_en_common_login_logout" doctitle="Login/Logout" link="#login_page">1. Login page</div><div class="search_word">1. login page start your web browser, and access "http://(the ip address you assigned to this unit)/" to display the login page. the following items are shown on the login page. model name ( ex. : swx3220-16mt ) hostname ( name configured using the hostname command ) input box for user name input box for password login button if login fails, the following error messages are displayed. incorrect user name or password incorrect username or password, or login as xxxx is restricted. incorrect password three times in a row blocked upon 3 failed login attempts for xxxx. please try again later. maximum number of sessions have been reached login failed. the maximum number of sessions has been reached. note: refer to " about sessions " for details on sessions.</div><div class="display_word">1. Login page Start your web browser, and access "http://(the IP address you assigned to this unit)/" to display the login page. The following items are shown on the login page. Model name ( Ex. : SWX3220-16MT ) hostname ( Name configured using the hostname command ) Input box for user name Input box for password Login button If login fails, the following error messages are displayed. Incorrect user name or password Incorrect username or password, or login as XXXX is restricted. Incorrect password three times in a row Blocked upon 3 failed login attempts for XXXX. Please try again later. Maximum number of sessions have been reached Login failed. The maximum number of sessions has been reached. Note: Refer to " About sessions " for details on sessions.</div></div><div id="gui_en_common_login_logout"><div class="search_title" docfname="gui_en_common_login_logout" doctitle="Login/Logout" link="#login">2. Login method</div><div class="search_word">2. login method here we explain how to log in to the web gui of this unit. start your web browser, and access the login page. enter the user name and password set by the username command, then press the "login" button. <about users> to access this unit in the factory-set state, log in with the user name "admin" and the password "admin". when logging in as a user without administrative privileges, you will be logged in as a general user. when logging in as a user with administrative privileges, you will be logged in as an administrative user. <about general users and administrative users> general user if you log in as a general user, you will be able to view this unit’ssettings and operating status. you will not be able to make settings for this unit. administrative user if you log in as an administrative user, you will be able to performall web gui operations. you can view the unit’s settings and operatingstatus, and configure the settings for this unit. <about passwords> you must enter the password as single-byte characters. double-bytecharacters may not be used. uppercase and lowercase characters aredistinguished. take care not to forget the password that you assigned. if you have forgotten the password, ask the administrator who set up this unit forthe correct password. <note> you will not be able to properly login if the browser is configured to block cookies. in this case, refer to the "introduction  2. operating environment" section to set up your cookies.</div><div class="display_word">2. Login method Here we explain how to log in to the web GUI of this unit. Start your web browser, and access the login page. Enter the user name and password set by the username command, then press the "Login" button. <About users> To access this unit in the factory-set state, log in with the user name "admin" and the password "admin". When logging in as a user without administrative privileges, you will be logged in as a general user. When logging in as a user with administrative privileges, you will be logged in as an administrative user. <About general users and administrative users> General User If you log in as a general user, you will be able to view this unit’ssettings and operating status. You will not be able to make settings for this unit. Administrative User If you log in as an administrative user, you will be able to performall web GUI operations. You can view the unit’s settings and operatingstatus, and configure the settings for this unit. <About passwords> You must enter the password as single-byte characters. Double-bytecharacters may not be used. Uppercase and lowercase characters aredistinguished. Take care not to forget the password that you assigned. If you have forgotten the password, ask the administrator who set up this unit forthe correct password. <NOTE> You will not be able to properly login if the browser is configured to block cookies. In this case, refer to the "Introduction  2. Operating environment" section to set up your cookies.</div></div><div id="gui_en_common_login_logout"><div class="search_title" docfname="gui_en_common_login_logout" doctitle="Login/Logout" link="#logout">3. Logout method</div><div class="search_word">3. logout method in the upper right of the screen, press the "log out" button to display the "log out" dialog box. press the "login screen" button in the dialog box to go to the login page.</div><div class="display_word">3. Logout method In the upper right of the screen, press the "Log out" button to display the "Log out" dialog box. Press the "Login screen" button in the dialog box to go to the login page.</div></div><div id="gui_en_common_login_logout"><div class="search_title" docfname="gui_en_common_login_logout" doctitle="Login/Logout" link="#session">4. About sessions</div><div class="search_word">4. about sessions if you can successfully login to the web gui, a session will be established between the browser in use and this unit. each time you login from a different browser or device, a new session is established. the session will be maintained until you log out or the session times out. sessions that have been established will time out after five minutes have elapsed from the last data communication. up to four sessions can be established at one time. information for a session can be checked using the "show users" command.</div><div class="display_word">4. About sessions If you can successfully login to the Web GUI, a session will be established between the browser in use and this unit. Each time you login from a different browser or device, a new session is established. The session will be maintained until you log out or the session times out. Sessions that have been established will time out after five minutes have elapsed from the last data communication. Up to four sessions can be established at one time. Information for a session can be checked using the "show users" command.</div></div><div id="gui_en_common_login_logout"><div class="search_title" docfname="gui_en_common_login_logout" doctitle="Login/Logout" link="#change_password">5. Change password of initial administrative user "admin"</div><div class="search_word">5. change password of initial administrative user "admin" if you log in as the initial administrative user "admin" and thepassword is "admin", a screen to change the password will appear. enter the password and set it, then the setting is saved.</div><div class="display_word">5. Change password of initial administrative user "admin" If you log in as the initial administrative user "admin" and thepassword is "admin", a screen to change the password will appear. Enter the password and set it, then the setting is saved.</div></div><div id="gui_en_common_login_logout"><div class="search_title" docfname="gui_en_common_login_logout" doctitle="Login/Logout" link="#select_language">6. Select display language</div><div class="search_word">6. select display language a screen for selecting a language appears right after you log in,only if you log in to the web gui as an administrative user in thefactory-set state. once you select a language, the web gui displays in the language.</div><div class="display_word">6. Select display language A screen for selecting a language appears right after you log in,only if you log in to the Web GUI as an administrative user in thefactory-set state. Once you select a language, the Web GUI displays in the language.</div></div><div id="gui_en_dashboard_dashboard"><div class="search_title" docfname="gui_en_dashboard_dashboard" doctitle="Summary" link="#title-box">Summary</div><div class="search_word">summary</div><div class="display_word">Summary</div></div><div id="gui_en_dashboard_dashboard"><div class="search_title" docfname="gui_en_dashboard_dashboard" doctitle="Summary" link="#help_how_to_use_db">1. Using the dashboard</div><div class="search_word">1. using the dashboard</div><div class="display_word">1. Using the dashboard</div></div><div id="gui_en_dashboard_dashboard"><div class="search_title" docfname="gui_en_dashboard_dashboard" doctitle="Summary" link="#help_how_to_use_db_1">1.1. Summary</div><div class="search_word">1.1. summary what is the dashboard? the page that provides visualization andmonitoring of various system information and status information iscalled the "dashboard." when a parameter being monitored exceeds thethreshold value, it is shown in a warning field, helping you todetermine the cause of a problem or to perform troubleshooting. what is a gadget? each window shown in the dashboard is called a "gadget." a gadget that you want to monitor can be placed anywhere you like. information for each gadget is automatically updated at regular intervals.</div><div class="display_word">1.1. Summary What is the dashboard? The page that provides visualization andmonitoring of various system information and status information iscalled the "dashboard." When a parameter being monitored exceeds thethreshold value, it is shown in a warning field, helping you todetermine the cause of a problem or to perform troubleshooting. What is a gadget? Each window shown in the dashboard is called a "gadget." A gadget that you want to monitor can be placed anywhere you like. Information for each gadget is automatically updated at regular intervals.</div></div><div id="gui_en_dashboard_dashboard"><div class="search_title" docfname="gui_en_dashboard_dashboard" doctitle="Summary" link="#help_how_to_use_db_2">1.2. About the buttons</div><div class="search_word">1.2. about the buttons the dashboard shows the following buttons. about the "stack switch" button if the stack configuration is enabled, the stack switch button will be displayed at upper left. select a stack id to display the stack information selected on the following gadgets. system information resource information interface information resource information ( graph ) power consumption information poe power supply this can only be selected for stacks with active status. the main switch will be selected on the initial screen. information for selected stacks for separated gadgets will be shown per gadget at the next update timing. about the "gadget" button from the "gadget" buttons ( ) in the upper right, select the gadgets that you want to be displayed. about the "warning" button a maximum of 32 warnings are shown, from newest to oldest. each of the displayed gadgets monitors thesituation, and when an abnormal situation or a high load is detected,the "warning" button ( ) flashes and a list of warnings appears under the "warning" button. the list of warnings shows the contents of the currently detected warnings in order of recentness. date and time that the abnormality was detected gadget that detected the abnormality detected content the bar of the gadget that is the object of the warning is also shown with a flashing "warning" button. when the following conditions aresatisfied, the warning will stop being displayed (the conditions differdepending on the detected content). recovered from an abnormal state (for example, the usage ratio or the throughput fell below the threshold) the state was cleared (for example, the settings were changed or the port linked down) the "clear" button ( ) of the warning list was pressed ( * ) (*) note that even if you press the"clear" button so that the warning is not shown in the warning list, itis not the case that the abnormal state has been resolved. if all warning indications disappear, the "warning" button stops flashing, and the warning list disappears. you can press the "warning" button to open or close the warning list. you cannot open the warning list and the warning history list at the same time. about the "history" button the warning history is shown in order of newness, for a maximum of 64 items . the warning history is shown in bold , but warnings that were cleared by the "clear" button in the warning list are shown in thin characters. if there are unconfirmed warning history items that have not been cleared, the lower right of the "history" button ( ) shows the number of those items (in other words the number of warning history items shown in bold) ( ). if this number is displayed, check the contents of the warnings that have occurred in the warning history list. when you press the "ok" button ( ) of each item in the warning history list, it changes to thin characters as a confirmed history item, and the "ok" button disappears. in the warning history list, pressing the "all confirmed" button ( ) changes all history entries to a confirmed state. in the warning history list, pressing the "all deleted" button ( ) deletes all history. you can press the "history" button to open or close the warning history list. you cannot open the warning list and the warning history list at the same time.</div><div class="display_word">1.2. About the buttons The dashboard shows the following buttons. About the "Stack switch" button If the stack configuration is enabled, the stack switch button will be displayed at upper left. Select a stack ID to display the stack information selected on the following gadgets. System information Resource information Interface information Resource information ( Graph ) Power consumption information PoE power supply This can only be selected for stacks with active status. The main switch will be selected on the initial screen. Information for selected stacks for separated gadgets will be shown per gadget at the next update timing. About the "Gadget" button From the "gadget" buttons ( ) in the upper right, select the gadgets that you want to be displayed. About the "Warning" button A maximum of 32 warnings are shown, from newest to oldest. Each of the displayed gadgets monitors thesituation, and when an abnormal situation or a high load is detected,the "Warning" button ( ) flashes and a list of warnings appears under the "Warning" button. The list of warnings shows the contents of the currently detected warnings in order of recentness. Date and time that the abnormality was detected Gadget that detected the abnormality Detected content The bar of the gadget that is the object of the warning is also shown with a flashing "Warning" button. When the following conditions aresatisfied, the warning will stop being displayed (the conditions differdepending on the detected content). Recovered from an abnormal state (for example, the usage ratio or the throughput fell below the threshold) The state was cleared (for example, the settings were changed or the port linked down) The "Clear" button ( ) of the warning list was pressed ( * ) (*) Note that even if you press the"Clear" button so that the warning is not shown in the warning list, itis not the case that the abnormal state has been resolved. If all warning indications disappear, the "Warning" button stops flashing, and the warning list disappears. You can press the "Warning" button to open or close the warning list. You cannot open the warning list and the warning history list at the same time. About the "History" button The warning history is shown in order of newness, for a maximum of 64 items . The warning history is shown in bold , but warnings that were cleared by the "Clear" button in the warning list are shown in thin characters. If there are unconfirmed warning history items that have not been cleared, the lower right of the "History" button ( ) shows the number of those items (in other words the number of warning history items shown in bold) ( ). If this number is displayed, check the contents of the warnings that have occurred in the warning history list. When you press the "OK" button ( ) of each item in the warning history list, it changes to thin characters as a confirmed history item, and the "OK" button disappears. In the warning history list, pressing the "All confirmed" button ( ) changes all history entries to a confirmed state. In the warning history list, pressing the "All deleted" button ( ) deletes all history. You can press the "History" button to open or close the warning history list. You cannot open the warning list and the warning history list at the same time.</div></div><div id="gui_en_dashboard_dashboard"><div class="search_title" docfname="gui_en_dashboard_dashboard" doctitle="Summary" link="#help_how_to_use_gdt">2. Using the gadgets</div><div class="search_word">2. using the gadgets</div><div class="display_word">2. Using the gadgets</div></div><div id="gui_en_dashboard_dashboard"><div class="search_title" docfname="gui_en_dashboard_dashboard" doctitle="Summary" link="#help_how_to_use_gdt_1">2.1. Available gadgets</div><div class="search_word">2.1. available gadgets the following gadgets can be used. system information resource information interface information syslog terminal monitoring traffic information ( transmit / reception ) resource information ( graph ) stack information power consumption information poe power supply</div><div class="display_word">2.1. Available gadgets The following gadgets can be used. System information Resource information Interface information SYSLOG Terminal monitoring Traffic information ( Transmit / Reception ) Resource information ( Graph ) Stack information Power consumption information PoE power supply</div></div><div id="gui_en_dashboard_dashboard"><div class="search_title" docfname="gui_en_dashboard_dashboard" doctitle="Summary" link="#help_how_to_use_gdt_2">2.2. Gadget details</div><div class="search_word">2.2. gadget details each gadget has the following functions. add gadget: press the "gadget" button ( ) in the upper right, select the gadget that you want to use from the gadget list, and then press the "apply" button. gadgets are always added to the far upper left of the dashboard. delete gadget: press the "gadget" button ( ) in the upper right, clear a selection from the gadget list, and then press the "apply" button. you can also delete a gadget by pressing the "close" button ( ) in the upper right of each gadget. move gadget: when you place the mouse over each gadget, the mouse pointer changes to a move symbol, allowing you to drag the gadget to a desired position. candidates for the gadget’s movement destination are shown in gray. the interface information gadget cannot be moved. separate the gadget screen: a "separate" button ( ) is shown in the upper right of each gadget. if you press the "separate" button, that gadget alone is shown in a different window. at this time, the corresponding gadget in the dashboard is indicated as "in separate window." if a gadget is separated, the following occurs. the "separate" button is no longer shown for the separated gadget. when you update the dashboard display, all separated gadgets return to the dashboard and are shown. when you close the dashboard, all separated gadgets are also closed. separated gadgets can also be displayed by specifying a url directly in the browser. when a url has been directly specified, the main switch will be displayed. example) system information gadget: http://192.168.100.1/dashboard/system.html minimize gadget: when you press the minimize icon ( ) in the upper left of each gadget, the icon turns sideways ( ) and the gadget display is minimized. when you press it again, the icon returns to its original downward orientation ( ) and the gadget returns to its original size. save gadget position information: when you add, delete, or move a gadget, or when you minimize and restore it, the position data of the gadget is saved. this information is also saved when the power is turned off and on again. this data is initialized if you return the device to its factory-set state. if a general user logs in, the gadget position information is not saved. auto-update gadget: all gadgets are automatically updated at regular intervals. the update interval differs depending on the gadget. warning display: when an abnormal condition or a high load is detected by a gadget, a flashing "warning" button ( ) is displayed beside the minimize icon of that gadget. the following states will initiate this warning. gadget trigger system information when reboot because of startup is detected when the cpu temperature exceeds 95 °c. when the phy temperature exceeds 112 °c. when the sfp temperature exceeds 76 °c. when the temperature sensor exceeds 50 °c. when the pse temperature exceeds 135 °c. the fan stops. the fan speed increases. resource information when cpu usage exceeds 80 % when memory usage exceeds 80 % interface information an loop occurs. the sfp optical rx level exceeds the upper limit. the sfp optical rx level falls below the lower limit. the poe power supply stops abnormally. an error occurs in the poe power supply control. traffic information the throughput exceeds the link speed of 60 % . stack information the stack port changed state to down. the heartbeat error was detected. this unit was selected as the main switch. syslog when multiple l2ms managers are detected.</div><div class="display_word">2.2. Gadget details Each gadget has the following functions. Add gadget: Press the "Gadget" button ( ) in the upper right, select the gadget that you want to use from the gadget list, and then press the "Apply" button. Gadgets are always added to the far upper left of the dashboard. Delete gadget: Press the "Gadget" button ( ) in the upper right, clear a selection from the gadget list, and then press the "Apply" button. You can also delete a gadget by pressing the "Close" button ( ) in the upper right of each gadget. Move gadget: When you place the mouse over each gadget, the mouse pointer changes to a move symbol, allowing you to drag the gadget to a desired position. Candidates for the gadget’s movement destination are shown in gray. The interface information gadget cannot be moved. Separate the gadget screen: A "Separate" button ( ) is shown in the upper right of each gadget. If you press the "Separate" button, that gadget alone is shown in a different window. At this time, the corresponding gadget in the dashboard is indicated as "In separate window." If a gadget is separated, the following occurs. The "Separate" button is no longer shown for the separated gadget. When you update the dashboard display, all separated gadgets return to the dashboard and are shown. When you close the dashboard, all separated gadgets are also closed. Separated gadgets can also be displayed by specifying a URL directly in the browser. When a URL has been directly specified, the main switch will be displayed. Example) System information gadget: http://192.168.100.1/dashboard/system.html Minimize gadget: When you press the minimize icon ( ) in the upper left of each gadget, the icon turns sideways ( ) and the gadget display is minimized. When you press it again, the icon returns to its original downward orientation ( ) and the gadget returns to its original size. Save gadget position information: When you add, delete, or move a gadget, or when you minimize and restore it, the position data of the gadget is saved. This information is also saved when the power is turned off and on again. This data is initialized if you return the device to its factory-set state. If a general user logs in, the gadget position information is not saved. Auto-update gadget: All gadgets are automatically updated at regular intervals. The update interval differs depending on the gadget. Warning display: When an abnormal condition or a high load is detected by a gadget, a flashing "Warning" button ( ) is displayed beside the minimize icon of that gadget. The following states will initiate this warning. Gadget Trigger System information When reboot because of startup is detected When the CPU temperature exceeds 95 °C. When the PHY temperature exceeds 112 °C. When the SFP temperature exceeds 76 °C. When the temperature sensor exceeds 50 °C. When the PSE temperature exceeds 135 °C. The fan stops. The fan speed increases. Resource information When CPU usage exceeds 80 % When memory usage exceeds 80 % Interface information An loop occurs. The SFP optical Rx level exceeds the upper limit. The SFP optical Rx level falls below the lower limit. The PoE power supply stops abnormally. An error occurs in the PoE power supply control. Traffic information The throughput exceeds the link speed of 60 % . Stack information The stack port changed state to down. The heartbeat error was detected. This unit was selected as the main switch. SYSLOG When multiple L2MS managers are detected.</div></div><div id="gui_en_dashboard_gadget"><div class="search_title" docfname="gui_en_dashboard_gadget" doctitle="About" link="#title-box">About the gadgets</div><div class="search_word">about the gadgets</div><div class="display_word">About the gadgets</div></div><div id="gui_en_dashboard_gadget"><div class="search_title" docfname="gui_en_dashboard_gadget" doctitle="About" link="#help_id_interface">1. Interface information</div><div class="search_word">1. interface information displays the link status of the ports and the poe power supply status. the "port" icon display lets you check the link status of the ports, the poe power supply status, and the bandwidth usage rate. when you move the mouse cursor over the "port" icon, detailed port information is shown. press the "link/act" button to display the link status. press the"power supply status" button to display the poe power supply status.press the "bandwidth usage" button to display the bandwidth usage rate. the "port" icon will display as follows, according to the linkstatus, the poe power supply status, and the bandwidth usage rate. link status:for a lan port icon description link up (port speed 1000base-t) link up (port speed 100base-tx) link up (port speed 10base-t) link down error occurrence (loop detection, shutdown by bpdu guard, shutdown by port-security, the throughput has exceeded link speed 60.) the stp state of the port is discarding. (cist only) it means that the stp is blocking frames even though the link is up. * this icon is overlaid on the link-up icon. link status:for an sfp port icon description link up (port speed 10gbe) link up (port speed 1gbe) link down error occurrence (loop detection, shutdown by bpdu guard, shutdown by port-security, optical rx power error, the throughput hasexceeded link speed 60.) the stp state of the port is discarding. (cist only) it means that the stp is blocking frames even though the link is up. * this icon is overlaid on the link-up icon. link status:stack port icon description link up link down poe supply:for a lan port icon description does not support power supply poe is being supplied (supply class0—​3) poe is being supplied (supply class4) power supply stopped error occurrence (power delivery capacity exceeded, error on the powered device, power supply abnormality) poe supply:for an sfp port icon description does not support power supply bandwidth usage:for a lan port icon explanation link up ( bandwidth usage rate x : 95% ≤ x ≤ 100% ) link up ( bandwidth usage rate x : 85% ≤ x < 95% ) link up ( bandwidth usage rate x : 75% ≤ x < 85% ) link up ( bandwidth usage rate x : 65% ≤ x < 75% ) link up ( bandwidth usage rate x : 55% ≤ x < 65% ) link up ( bandwidth usage rate x : 45% ≤ x < 55% ) link up ( bandwidth usage rate x : 35% ≤ x < 45% ) link up ( bandwidth usage rate x : 25% ≤ x < 35% ) link up ( bandwidth usage rate x : 15% ≤ x < 25% ) link up ( bandwidth usage rate x : 7.5% ≤ x < 15% ) link up ( bandwidth usage rate x : 0% ≤ x < 7.5% ) link down bandwidth usage:for an sfp port icon description link up ( bandwidth usage rate x : 95% ≤ x ≤ 100% ) link up ( bandwidth usage rate x : 85% ≤ x < 95% ) link up ( bandwidth usage rate x : 75% ≤ x < 85% ) link up ( bandwidth usage rate x : 65% ≤ x < 75% ) link up ( bandwidth usage rate x : 55% ≤ x < 65% ) link up ( bandwidth usage rate x : 45% ≤ x < 55% ) link up ( bandwidth usage rate x : 35% ≤ x < 45% ) link up ( bandwidth usage rate x : 25% ≤ x < 35% ) link up ( bandwidth usage rate x : 15% ≤ x < 25% ) link up ( bandwidth usage rate x : 7.5% ≤ x < 15% ) link up ( bandwidth usage rate x : 0% ≤ x < 7.5% ) link down</div><div class="display_word">1. Interface information Displays the link status of the ports and the PoE power supply status. The "Port" icon display lets you check the link status of the ports, the PoE power supply status, and the bandwidth usage rate. When you move the mouse cursor over the "Port" icon, detailed port information is shown. Press the "LINK/ACT" button to display the link status. Press the"Power supply status" button to display the PoE power supply status.Press the "Bandwidth usage" button to display the bandwidth usage rate. The "Port" icon will display as follows, according to the linkstatus, the PoE power supply status, and the bandwidth usage rate. Link status:For a LAN port Icon Description Link up (port speed 1000BASE-T) Link up (port speed 100BASE-TX) Link up (port speed 10BASE-T) Link down Error occurrence (Loop detection, Shutdown by BPDU guard, Shutdown by port-security, The throughput has exceeded link speed 60.) The STP state of the port is discarding. (CIST only) It means that the STP is blocking frames even though the link is up. * This icon is overlaid on the link-up icon. Link status:For an SFP port Icon Description Link up (port speed 10GbE) Link up (port speed 1GbE) Link down Error occurrence (Loop detection, Shutdown by BPDU guard, Shutdown by port-security, Optical RX power error, The throughput hasexceeded link speed 60.) The STP state of the port is discarding. (CIST only) It means that the STP is blocking frames even though the link is up. * This icon is overlaid on the link-up icon. Link status:Stack port Icon Description Link up Link down PoE supply:For a LAN port Icon Description Does not support power supply PoE is being supplied (supply Class0—​3) PoE is being supplied (supply Class4) Power supply stopped Error occurrence (Power delivery capacity exceeded, Error on the Powered Device, Power supply abnormality) PoE supply:For an SFP port Icon Description Does not support power supply Bandwidth usage:For a LAN port Icon Explanation Link up ( Bandwidth usage rate x : 95% ≤ x ≤ 100% ) Link up ( Bandwidth usage rate x : 85% ≤ x < 95% ) Link up ( Bandwidth usage rate x : 75% ≤ x < 85% ) Link up ( Bandwidth usage rate x : 65% ≤ x < 75% ) Link up ( Bandwidth usage rate x : 55% ≤ x < 65% ) Link up ( Bandwidth usage rate x : 45% ≤ x < 55% ) Link up ( Bandwidth usage rate x : 35% ≤ x < 45% ) Link up ( Bandwidth usage rate x : 25% ≤ x < 35% ) Link up ( Bandwidth usage rate x : 15% ≤ x < 25% ) Link up ( Bandwidth usage rate x : 7.5% ≤ x < 15% ) Link up ( Bandwidth usage rate x : 0% ≤ x < 7.5% ) Link down Bandwidth usage:For an SFP port Icon Description Link up ( Bandwidth usage rate x : 95% ≤ x ≤ 100% ) Link up ( Bandwidth usage rate x : 85% ≤ x < 95% ) Link up ( Bandwidth usage rate x : 75% ≤ x < 85% ) Link up ( Bandwidth usage rate x : 65% ≤ x < 75% ) Link up ( Bandwidth usage rate x : 55% ≤ x < 65% ) Link up ( Bandwidth usage rate x : 45% ≤ x < 55% ) Link up ( Bandwidth usage rate x : 35% ≤ x < 45% ) Link up ( Bandwidth usage rate x : 25% ≤ x < 35% ) Link up ( Bandwidth usage rate x : 15% ≤ x < 25% ) Link up ( Bandwidth usage rate x : 7.5% ≤ x < 15% ) Link up ( Bandwidth usage rate x : 0% ≤ x < 7.5% ) Link down</div></div><div id="gui_en_dashboard_gadget"><div class="search_title" docfname="gui_en_dashboard_gadget" doctitle="About" link="#help_id_system">2. System information</div><div class="search_word">2. system information the following information is displayed. device name: display the device name of the switch. firmware revision: firmware revision serial number: serial number of the device this is also shown by a label on the rear of the chassis. mac address: mac address of the device this is also shown by a label on the rear of the chassis. currently-running firmware: the currently started firmware is shown.. when it starts from firmware stored in an external memory, shown like "exec(sd)". currently-running settings file: the currently used config file is shown. select config0 - config4 using the startup-config select command. serial baud rate displays the baud rate of the console port. system time: current device date and time if the date and time are incorrect, set the date and timeeither in the web gui’s "management" → "device settings" page, or by using the clock set command or the ntpdate command. startup time: system startup date and time startup reason: reason for startup start from power-off state, reload command, revision up, etc. if reboot is detected as the startup reason, the background turns red, and a warning indication ( ) occurs. check with the network administrator. in the warning list, press the "clear" button ( ) to clear the warning indication. fan speed : displays the speed of each fan. internal chassis temperature : displays the temperature inside the chassis. sfp optical rx level : displays the sfp optical rx level state and the connection module. poe supply : the display will show whether the poe power supply is enabled. poe supply power : the current supply voltage and the maximum supplied voltage will be displayed.</div><div class="display_word">2. System information The following information is displayed. Device name: Display the device name of the switch. Firmware revision: Firmware revision Serial number: Serial number of the device This is also shown by a label on the rear of the chassis. MAC address: MAC address of the device This is also shown by a label on the rear of the chassis. Currently-running firmware: The currently started firmware is shown.. When it starts from firmware stored in an external memory, shown like "exec(SD)". Currently-running settings file: The currently used CONFIG file is shown. Select config0 - config4 using the startup-config select command. Serial baud rate Displays the baud rate of the console port. System time: Current device date and time If the date and time are incorrect, set the date and timeeither in the Web GUI’s "Management" → "Device settings" page, or by using the clock set command or the ntpdate command. Startup time: System startup date and time Startup reason: Reason for startup Start from power-off state, reload command, revision up, etc. If reboot is detected as the startup reason, the background turns red, and a warning indication ( ) occurs. Check with the network administrator. In the warning list, press the "Clear" button ( ) to clear the warning indication. Fan speed : Displays the speed of each fan. Internal chassis temperature : Displays the temperature inside the chassis. SFP optical RX level : Displays the SFP optical Rx level state and the connection module. PoE supply : The display will show whether the PoE power supply is enabled. PoE supply power : The current supply voltage and the maximum supplied voltage will be displayed.</div></div><div id="gui_en_dashboard_gadget"><div class="search_title" docfname="gui_en_dashboard_gadget" doctitle="About" link="#help_id_resource">3. Resource information</div><div class="search_word">3. resource information this page shows the cpu usage and memory usage. the current values and peak values of cpu usage and memory usage are shown. the number at the right of the meter is the current usage, and the number at the left is the peak value. you can clear the previous peak value from "clear peak values,". peak values are also cleared when you restart the device. when you move the mouse cursor to each meter, the peak value andthe date and time at which the peak value was recorded are shown. if the cpu usage exceeds 80 % , a warning display ( ) is shown. note the date and time at which the peak value was recorded,and from other gadgets, note the traffic and the log that were occurring during that time. if the memory usage exceeds 80 % , a warning display ( ) is shown. note the date and time at which the peak value was recorded,and from other gadgets, note the traffic and the log that were occurring during that time.</div><div class="display_word">3. Resource information This page shows the CPU usage and memory usage. The current values and peak values of CPU usage and memory usage are shown. The number at the right of the meter is the current usage, and the number at the left is the peak value. You can clear the previous peak value from "Clear peak values,". Peak values are also cleared when you restart the device. When you move the mouse cursor to each meter, the peak value andthe date and time at which the peak value was recorded are shown. If the CPU usage exceeds 80 % , a warning display ( ) is shown. Note the date and time at which the peak value was recorded,and from other gadgets, note the traffic and the log that were occurring during that time. If the memory usage exceeds 80 % , a warning display ( ) is shown. Note the date and time at which the peak value was recorded,and from other gadgets, note the traffic and the log that were occurring during that time.</div></div><div id="gui_en_dashboard_gadget"><div class="search_title" docfname="gui_en_dashboard_gadget" doctitle="About" link="#help_id_syslog">4. SYSLOG</div><div class="search_word">4. syslog this shows the most recent syslog. the most recent log is at the top. in the select menu you can change the number of lines that are displayed (default: 10 lines).</div><div class="display_word">4. SYSLOG This shows the most recent SYSLOG. The most recent log is at the top. In the select menu you can change the number of lines that are displayed (default: 10 lines).</div></div><div id="gui_en_dashboard_gadget"><div class="search_title" docfname="gui_en_dashboard_gadget" doctitle="About" link="#help_id_terminal">5. Terminal monitoring</div><div class="search_word">5. terminal monitoring displays a list of monitored devices and the status of each. devices that are determined to be up, down, not started yet ("idle") and all monitored devices ("all") are counted respectively. displays the monitored target, device name, monitoring type and status for each monitored device. point the mouse cursor above a status column to show the status for that monitored device. press the "up", "down", "idle" and "all" buttons to show only the monitored devices for those statuses. when not even one monitored device is registered, "the monitoring devices have not been registered" will be displayed.</div><div class="display_word">5. Terminal monitoring Displays a list of monitored devices and the status of each. Devices that are determined to be up, down, not started yet ("Idle") and all monitored devices ("All") are counted respectively. Displays the monitored target, device name, monitoring type and status for each monitored device. Point the mouse cursor above a status column to show the status for that monitored device. Press the "Up", "Down", "Idle" and "All" buttons to show only the monitored devices for those statuses. When not even one monitored device is registered, "The monitoring devices have not been registered" will be displayed.</div></div><div id="gui_en_dashboard_gadget"><div class="search_title" docfname="gui_en_dashboard_gadget" doctitle="About" link="#help_id_traffic">6. Traffic information</div><div class="search_word">6. traffic information the physical interface traffic is displayed on a graph. there are different gadgets for the transmission traffic and for the reception traffic. use the " live ", " day ", " month " and " year " buttons to change the graph rendered. live traffic can be viewed for the previous two minutes. the graph will be automatically refreshed each second. day displays traffic per hour for the specified date. the day can be set using the day specification box at the top right of the gadget. press the date specification box to display the calendar, and select the day to show the graph for the day specified. a date within one year to the past can be set using the calendar. month displays traffic per day for the specified month. the month can be set using the month specification box at the top right of the gadget. press the month specification box to display the calendar, and select the month to show the graph for the day specified. a past month within one year can be set using the calendar. year displays traffic per month for the specified year. the year can be set using the year specification box at the top right of the gadget. press the year specification box to display the calendar, and select the year to show the graph for the year specified. the year specification box can be used to specify either the current year or the previous year. press the "interface selection" button ( ) to display the "interface selection" dialog box. select the interface to display on the graph, from the "interface selection" dialog box. the average traffic per hour for the interface is rendered on the graph. press the "export as a csv file" button ( ) to display the "traffic information export summary data" dialog. you can export the specified period’s traffic summary data as acsv file in the "traffic information export summary data" dialog. press the "clear summary data" button ( ) to display the "traffic information clear summary data" dialog. you can delete all the traffic summary data in the "traffic information clear summary data" dialog. up to 8 lines can be displayed on the graph usingthe colors blue, salmon pink, yellow, green, gray, sky blue, pink andpurple for a total of 8 colors. these colors are allocated in the order that they are rendered on the graph, from the newest interface numbers onwards. the y-axis upper limit grows with the traffic, from a minimum of 10 [kbps] to a maximum of 10 [gbps]. the information shown below is shown on the graph for the specified period that is rendered. live : current time - time 120 sec. ago (hh:mm:ss format) day : 0 o’clock - 23 o’clock month : 1st - 28th, 29th, 30th, 31st year : jan - dec point the mouse cursor above a line on the graph to show the interface information, date and traffic amount. a legend for the currently displayed graph is shown at the lowermost part of the gadget. using the legend only the lines on the graph that are enabled using the check boxes in the legend will be displayed. deselecting the check boxes will hide the corresponding lines from the graph. this is useful when multiple lines are overlapping or when you wish to temporarily monitor a specific interface only. if the interface you are currently monitoring does not exist,the message "the currently monitored interface is not selected" willdisplay. refresh the screen to restore the rendered time period and the selections on the legend to their defaults, as shown below. rendered period : live legend check boxes : all applied if the traffic exceeds 60% , a warning ( ) will be displayed. if the traffic falls below 50% , the warning will be cancelled. when displaying a gadget in a separate window using the "separate" button ( ) the settings prior to being separated will be reflected in the settings for the interface currently being monitored. the rendered time period and the selections on the legend return to their defaults. the settings for the interface selected in a separated windowwill be reflected in the dashboard gadget when the separated screen isclosed. when directly inputting the url for a separated window and displaying a gadget the rendered time period and the selections on the legend return to their defaults.</div><div class="display_word">6. Traffic information The physical interface traffic is displayed on a graph. There are different gadgets for the transmission traffic and for the reception traffic. Use the " Live ", " Day ", " Month " and " Year " buttons to change the graph rendered. Live Traffic can be viewed for the previous two minutes. The graph will be automatically refreshed each second. Day Displays traffic per hour for the specified date. The day can be set using the day specification box at the top right of the gadget. Press the date specification box to display the calendar, and select the day to show the graph for the day specified. A date within one year to the past can be set using the calendar. Month Displays traffic per day for the specified month. The month can be set using the month specification box at the top right of the gadget. Press the month specification box to display the calendar, and select the month to show the graph for the day specified. A past month within one year can be set using the calendar. Year Displays traffic per month for the specified year. The year can be set using the year specification box at the top right of the gadget. Press the year specification box to display the calendar, and select the year to show the graph for the year specified. The year specification box can be used to specify either the current year or the previous year. Press the "Interface selection" button ( ) to display the "Interface selection" dialog box. Select the interface to display on the graph, from the "Interface selection" dialog box. The average traffic per hour for the interface is rendered on the graph. Press the "Export as a CSV file" button ( ) to display the "Traffic information Export summary data" dialog. You can export the specified period’s traffic summary data as aCSV file in the "Traffic information Export summary data" dialog. Press the "Clear summary data" button ( ) to display the "Traffic information Clear summary data" dialog. You can delete all the traffic summary data in the "Traffic information Clear summary data" dialog. Up to 8 lines can be displayed on the graph usingthe colors blue, salmon pink, yellow, green, gray, sky blue, pink andpurple for a total of 8 colors. These colors are allocated in the order that they are rendered on the graph, from the newest interface numbers onwards. The Y-axis upper limit grows with the traffic, from a minimum of 10 [kbps] to a maximum of 10 [Gbps]. The information shown below is shown on the graph for the specified period that is rendered. Live : Current time - time 120 sec. ago (hh:mm:ss format) Day : 0 o’clock - 23 o’clock Month : 1st - 28th, 29th, 30th, 31st Year : Jan - Dec Point the mouse cursor above a line on the graph to show the interface information, date and traffic amount. A legend for the currently displayed graph is shown at the lowermost part of the gadget. Using the legend Only the lines on the graph that are enabled using the check boxes in the legend will be displayed. Deselecting the check boxes will hide the corresponding lines from the graph. This is useful when multiple lines are overlapping or when you wish to temporarily monitor a specific interface only. If the interface you are currently monitoring does not exist,the message "The currently monitored interface is not selected" willdisplay. Refresh the screen to restore the rendered time period and the selections on the legend to their defaults, as shown below. Rendered period : Live Legend check boxes : All applied If the traffic exceeds 60% , a warning ( ) will be displayed. If the traffic falls below 50% , the warning will be cancelled. When displaying a gadget in a separate window using the "Separate" button ( ) The settings prior to being separated will be reflected in the settings for the interface currently being monitored. The rendered time period and the selections on the legend return to their defaults. The settings for the interface selected in a separated windowwill be reflected in the dashboard gadget when the separated screen isclosed. When directly inputting the URL for a separated window and displaying a gadget The rendered time period and the selections on the legend return to their defaults.</div></div><div id="gui_en_dashboard_gadget"><div class="search_title" docfname="gui_en_dashboard_gadget" doctitle="About" link="#help_id_resource_graph">7. Resource information(Graph)</div><div class="search_word">7. resource information(graph) this shows the cpu usage and memory usage in graph format. use the " live ", " day ", " month " and " year " buttons to change the graph rendered. live usage ratio can be viewed for the previous two minutes. the graph will be automatically refreshed each second. day displays usage ratio per hour for the specified date. the day can be set using the day specification box at the top right of the gadget. press the date specification box to display the calendar, and select the day to show the graph for the day specified. a date within one year to the past can be set using the calendar. month displays usage ratio per day for the specified month. the month can be set using the month specification box at the top right of the gadget. press the month specification box to display the calendar, and select the month to show the graph for the day specified. a past month within one year can be set using the calendar. year displays usage ratio per month for the specified year. the year can be set using the year specification box at the top right of the gadget. press the year specification box to display the calendar, and select the year to show the graph for the year specified. the year specification box can be used to specify either the current year or the previous year. press the "export as a csv file" button ( ) to display the "resource information export summary data" dialog. you can export the specified period’s resouce summary data as acsv file in the "resource information export summary data" dialog. press the "clear summary data" button ( ) to display the "resource information clear summary data" dialog. you can delete all the resouce summary data in the "resource information clear summary data" dialog. the average usage ratio is rendered per hour for the monitored period. the cpu usage is shown on the graph using blue lines, and the memory usage is shown using salmon pink lines. the upper limit for the graph’s y axis is 100 [%]. the information shown below is shown on the graph for the specified period that is rendered. live : current time - time 120 sec. ago (hh:mm:ss format) day : 0 o’clock - 23 o’clock month : 1st - 28th, 29th, 30th, 31st year : jan - dec point the mouse cursor above a line on the graph to show the monitored period, date and time and usage ratio. a legend for the currently displayed graph is shown at the lowermost part of the gadget. using the legend only the lines on the graph that are enabled using the check boxes in the legend will be displayed. deselecting the check boxes will hide the corresponding lines from the graph. refresh the screen to restore the rendered time period and the selections on the legend to their defaults, as shown below. rendered period : live legend check boxes : all applied if the cpu usage exceeds 80% , a warning ( ) will be displayed. if the cpu usage falls below 80% , the warning will be cancelled. if the memory usage exceeds 80% , a warning ( ) will be displayed. if the memory usage falls below 80% , the warning will be cancelled. when displaying a gadget in a separate window using the "separate" button ( ) the rendered time period and the selections on the legend return to their defaults. when directly inputting the url for a separated window and displaying a gadget the rendered time period and the selections on the legend return to their defaults.</div><div class="display_word">7. Resource information(Graph) This shows the CPU usage and memory usage in graph format. Use the " Live ", " Day ", " Month " and " Year " buttons to change the graph rendered. Live Usage ratio can be viewed for the previous two minutes. The graph will be automatically refreshed each second. Day Displays usage ratio per hour for the specified date. The day can be set using the day specification box at the top right of the gadget. Press the date specification box to display the calendar, and select the day to show the graph for the day specified. A date within one year to the past can be set using the calendar. Month Displays usage ratio per day for the specified month. The month can be set using the month specification box at the top right of the gadget. Press the month specification box to display the calendar, and select the month to show the graph for the day specified. A past month within one year can be set using the calendar. Year Displays usage ratio per month for the specified year. The year can be set using the year specification box at the top right of the gadget. Press the year specification box to display the calendar, and select the year to show the graph for the year specified. The year specification box can be used to specify either the current year or the previous year. Press the "Export as a CSV file" button ( ) to display the "Resource information Export summary data" dialog. You can export the specified period’s resouce summary data as aCSV file in the "Resource information Export summary data" dialog. Press the "Clear summary data" button ( ) to display the "Resource information Clear summary data" dialog. You can delete all the resouce summary data in the "Resource information Clear summary data" dialog. The average usage ratio is rendered per hour for the monitored period. The CPU usage is shown on the graph using blue lines, and the memory usage is shown using salmon pink lines. The upper limit for the graph’s Y axis is 100 [%]. The information shown below is shown on the graph for the specified period that is rendered. Live : Current time - time 120 sec. ago (hh:mm:ss format) Day : 0 o’clock - 23 o’clock Month : 1st - 28th, 29th, 30th, 31st Year : Jan - Dec Point the mouse cursor above a line on the graph to show the monitored period, date and time and usage ratio. A legend for the currently displayed graph is shown at the lowermost part of the gadget. Using the legend Only the lines on the graph that are enabled using the check boxes in the legend will be displayed. Deselecting the check boxes will hide the corresponding lines from the graph. Refresh the screen to restore the rendered time period and the selections on the legend to their defaults, as shown below. Rendered period : Live Legend check boxes : All applied If the CPU usage exceeds 80% , a warning ( ) will be displayed. If the CPU usage falls below 80% , the warning will be cancelled. If the memory usage exceeds 80% , a warning ( ) will be displayed. If the memory usage falls below 80% , the warning will be cancelled. When displaying a gadget in a separate window using the "Separate" button ( ) The rendered time period and the selections on the legend return to their defaults. When directly inputting the URL for a separated window and displaying a gadget The rendered time period and the selections on the legend return to their defaults.</div></div><div id="gui_en_dashboard_gadget"><div class="search_title" docfname="gui_en_dashboard_gadget" doctitle="About" link="#help_id_stack">8. Stack information</div><div class="search_word">8. stack information the following information is displayed. stack function displays whether the stack function is enabled. members displays the member switch types and roles. status displays the member switch status. only displayed when the stack function is enabled. subnet on stack port displays a range of ip addresses to use for stacked ports. virtual mac-address displays the mac address used in the stack configuration.</div><div class="display_word">8. Stack information The following information is displayed. Stack function Displays whether the stack function is enabled. Members Displays the member switch types and roles. Status Displays the member switch status. Only displayed when the stack function is enabled. Subnet on stack port Displays a range of IP addresses to use for stacked ports. Virtual MAC-Address Displays the MAC address used in the stack configuration.</div></div><div id="gui_en_dashboard_gadget"><div class="search_title" docfname="gui_en_dashboard_gadget" doctitle="About" link="#help_id_power_consumption">9. Power consumption information</div><div class="search_word">9. power consumption information displays the power consumption of the device on a graph. use the " live ", " day ", " month " and " year " buttons to change the graph rendered. live displays the power consumption [w] per second for the last 2 minutes. the graph will be automatically refreshed each second. day displays the total hourly power consumption [wh] for the specified day. the day can be set using the day specification box at the top right of the gadget. press the date specification box to display the calendar, and select the day to show the graph for the day specified. a date within one year to the past can be set using the calendar. month displays the total daily power consumption [wh] for the specified month. the month can be set using the month specification box at the top right of the gadget. press the month specification box to display the calendar, and select the month to show the graph for the day specified. a past month within one year can be set using the calendar. year displays the total monthly power consumption [wh] for the specified year. the year can be set using the year specification box at the top right of the gadget. press the year specification box to display the calendar, and select the year to show the graph for the year specified. the year specification box can be used to specify either the current year or the previous year. press the "export as a csv file" button ( ) to display the "power consumption information export summary data" dialog. you can export the specified period’s power consumption summarydata as a csv file in the "power consumption information export summarydata" dialog. press the "clear summary data" button ( ) to display the "power consumption information clear summary data" dialog. you can delete all the power consumption summary data in the "power consumption information clear summary data" dialog. the information shown below is shown on the graph for the specified period that is rendered. live : current time - time 120 sec. ago (hh:mm:ss format) day : 0 o’clock - 23 o’clock month : 1st - 28th, 29th, 30th, 31st year : jan - dec point the mouse cursor above a line on the graph to show the date and power consumption. refresh the screen to restore the rendered time period to its default state live . the rendered time period returns to its default in the following cases. when displaying a gadget in a separate window using the "separate" button ( ) when directly inputting the url for a separated window and displaying a gadget the following recommended methods reduce power consumption. decrease the link speed of ports with low bandwidth usage. use the schedule execution function to shut down unused ports and poe power supply at midnight and on holidays.</div><div class="display_word">9. Power consumption information Displays the power consumption of the device on a graph. Use the " Live ", " Day ", " Month " and " Year " buttons to change the graph rendered. Live Displays the power consumption [W] per second for the last 2 minutes. The graph will be automatically refreshed each second. Day Displays the total hourly power consumption [Wh] for the specified day. The day can be set using the day specification box at the top right of the gadget. Press the date specification box to display the calendar, and select the day to show the graph for the day specified. A date within one year to the past can be set using the calendar. Month Displays the total daily power consumption [Wh] for the specified month. The month can be set using the month specification box at the top right of the gadget. Press the month specification box to display the calendar, and select the month to show the graph for the day specified. A past month within one year can be set using the calendar. Year Displays the total monthly power consumption [Wh] for the specified year. The year can be set using the year specification box at the top right of the gadget. Press the year specification box to display the calendar, and select the year to show the graph for the year specified. The year specification box can be used to specify either the current year or the previous year. Press the "Export as a CSV file" button ( ) to display the "Power consumption information Export summary data" dialog. You can export the specified period’s power consumption summarydata as a CSV file in the "Power consumption information Export summarydata" dialog. Press the "Clear summary data" button ( ) to display the "Power consumption information Clear summary data" dialog. You can delete all the power consumption summary data in the "Power consumption information Clear summary data" dialog. The information shown below is shown on the graph for the specified period that is rendered. Live : Current time - time 120 sec. ago (hh:mm:ss format) Day : 0 o’clock - 23 o’clock Month : 1st - 28th, 29th, 30th, 31st Year : Jan - Dec Point the mouse cursor above a line on the graph to show the date and power consumption. Refresh the screen to restore the rendered time period to its default state Live . The rendered time period returns to its default in the following cases. When displaying a gadget in a separate window using the "Separate" button ( ) When directly inputting the URL for a separated window and displaying a gadget The following recommended methods reduce power consumption. Decrease the link speed of ports with low bandwidth usage. Use the Schedule execution function to shut down unused ports and PoE power supply at midnight and on holidays.</div></div><div id="gui_en_dashboard_gadget"><div class="search_title" docfname="gui_en_dashboard_gadget" doctitle="About" link="#help_id_poe_power_supply">10. PoE power supply</div><div class="search_word">10. poe power supply display the poe power supply. the current/maximum power supply, the remaining available powersupply, and the guard band setting values are displayed at the top ofthe meter. the current utilization rate is shown on the right side of the meter, with peak utilization at the top. the arrow at the bottom of the meter indicates the guard bandthreshold value. if the current power supply exceeds the guard bandthreshold value, no additional power can be supplied. when you move the mouse cursor to the meter, the peak value andthe date and time at which the peak value was recorded are shown. you can clear the previous peak value from "clear peak values". peak values are also cleared when you restart the device.</div><div class="display_word">10. PoE power supply Display the PoE power supply. The current/maximum power supply, the remaining available powersupply, and the guard band setting values are displayed at the top ofthe meter. The current utilization rate is shown on the right side of the meter, with peak utilization at the top. The arrow at the bottom of the meter indicates the guard bandthreshold value. If the current power supply exceeds the guard bandthreshold value, no additional power can be supplied. When you move the mouse cursor to the meter, the peak value andthe date and time at which the peak value was recorded are shown. You can clear the previous peak value from "Clear peak values". Peak values are also cleared when you restart the device.</div></div><div id="gui_en_detail_acl_apply"><div class="search_title" docfname="gui_en_detail_acl_apply" doctitle="Apply" link="#title-box">Apply Access list</div><div class="search_word">apply access list</div><div class="display_word">Apply Access list</div></div><div id="gui_en_detail_acl_apply"><div class="search_title" docfname="gui_en_detail_acl_apply" doctitle="Apply" link="#section1">1. Summary</div><div class="search_word">1. summary apply the access list for the interface on this page.</div><div class="display_word">1. Summary Apply the access list for the interface on this page.</div></div><div id="gui_en_detail_acl_apply"><div class="search_title" docfname="gui_en_detail_acl_apply" doctitle="Apply" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for applying the access list.</div><div class="display_word">2. Top page This is the top page for applying the access list.</div></div><div id="gui_en_detail_acl_apply"><div class="search_title" docfname="gui_en_detail_acl_apply" doctitle="Apply" link="#interface_list">2.1. Interface list</div><div class="search_word">2.1. interface list the access list information applied to the interface is displayed. the table items are explained below. i/f displays the interface name. access list (in) the information listed below for the access list applied to the input side of the interface is shown here. id the access list id will be displayed. type the access list type will be displayed. description the description text set in this access list will be displayed. access list (out) information for the access list applied to the input side of the interface is shown here. information similar to the access list (in) will be displayed. press the "setting" button to display the page where you can change the settings of the selected interface. if you press the "specify all" button, the settings can be changed for all interfaces whose check box is selected. if you press the "return to defaults" button, the settings will be initialized on all interfaces whose check boxes are selected.</div><div class="display_word">2.1. Interface list The access list information applied to the interface is displayed. The table items are explained below. I/F Displays the interface name. Access list (IN) The information listed below for the access list applied to the input side of the interface is shown here. ID The access list ID will be displayed. Type The access list type will be displayed. Description The description text set in this access list will be displayed. Access list (OUT) Information for the access list applied to the input side of the interface is shown here. Information similar to the access list (IN) will be displayed. Press the "Setting" button to display the page where you can change the settings of the selected interface. If you press the "Specify all" button, the settings can be changed for all interfaces whose check box is selected. If you press the "Return to defaults" button, the settings will be initialized on all interfaces whose check boxes are selected.</div></div><div id="gui_en_detail_acl_apply"><div class="search_title" docfname="gui_en_detail_acl_apply" doctitle="Apply" link="#select_acl">3. Selection page for access lists to apply</div><div class="search_word">3. selection page for access lists to apply this page is for selecting the access list to apply to the interface. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Selection page for access lists to apply This page is for selecting the access list to apply to the interface. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_acl_apply"><div class="search_title" docfname="gui_en_detail_acl_apply" doctitle="Apply" link="#select_access_list_to_apply">3.1. Select access list to apply</div><div class="search_word">3.1. select access list to apply applicable interface the interface on which the access list will be applied is displayed. access list to apply (in) select the access list to apply to the input side of the interface. press the "select" button to display the file "access list selection" dialog box. on the "access list selection" dialog, you can select the check box for an access list and press the "ok" buttonto select the access list to apply. press the "detail" button in the "access list selection" dialog box to display the targeted access list. in the ipv4 access list which specifies port numbers by range, only one interface can be applied for the entire system. the number of control conditions that can be applied to an interface are 512 for the entire system. applying an access list to one interfacewill decrease a number of applicable control conditions equal to thecontrol conditions included in the access list. for example, when an access list with five specified control conditions is applied to the input side of port1.1,the number of control conditions that can be applied is decreased by 5. note that the number of control conditions that can be actually applied is less than 512, because the controlconditions are also used in the system and other functions. access list to apply (out) select the access list to apply to the output side of the interface. the setting details for the access list (out) to be applied are equivalent to the access list (in) to be applied . ipv4 access lists which specify port numbers by range cannot be applied to the output side. mac access lists cannot be applied to the output side of an interface. access lists cannot be applied to the output side of a logical interface.</div><div class="display_word">3.1. Select access list to apply Applicable interface The interface on which the access list will be applied is displayed. Access list to apply (IN) Select the access list to apply to the input side of the interface. Press the "Select" button to display the file "Access list selection" dialog box. On the "Access list selection" dialog, you can select the check box for an access list and press the "OK" buttonto select the access list to apply. Press the "Detail" button in the "Access list selection" dialog box to display the targeted access list. In the IPv4 access list which specifies port numbers by range, only one interface can be applied for the entire system. The number of control conditions that can be applied to an interface are 512 for the entire system. Applying an access list to one interfacewill decrease a number of applicable control conditions equal to thecontrol conditions included in the access list. For example, when an access list with five specified control conditions is applied to the input side of port1.1,the number of control conditions that can be applied is decreased by 5. Note that the number of control conditions that can be actually applied is less than 512, because the controlconditions are also used in the system and other functions. Access list to apply (OUT) Select the access list to apply to the output side of the interface. The setting details for the access list (OUT) to be applied are equivalent to the access list (IN) to be applied . IPv4 access lists which specify port numbers by range cannot be applied to the output side. MAC access lists cannot be applied to the output side of an interface. Access lists cannot be applied to the output side of a logical interface.</div></div><div id="gui_en_detail_acl_create"><div class="search_title" docfname="gui_en_detail_acl_create" doctitle="Create" link="#title-box">Create Access list</div><div class="search_word">create access list</div><div class="display_word">Create Access list</div></div><div id="gui_en_detail_acl_create"><div class="search_title" docfname="gui_en_detail_acl_create" doctitle="Create" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can create or delete access lists, and change their settings.</div><div class="display_word">1. Summary In this page you can create or delete access lists, and change their settings.</div></div><div id="gui_en_detail_acl_create"><div class="search_title" docfname="gui_en_detail_acl_create" doctitle="Create" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for creating an access list.</div><div class="display_word">2. Top page This is the top page for creating an access list.</div></div><div id="gui_en_detail_acl_create"><div class="search_title" docfname="gui_en_detail_acl_create" doctitle="Create" link="#access_lists">2.1. Access lists</div><div class="search_word">2.1. access lists the information for the access list you created will be displayed. the table items are explained below. id the access list id will be displayed. type the access list type will be displayed. description the description text set in this access list will be displayed. a maximum of 20 items can be displayed for one page. press or or enter a numeric value to switch between pages. you can press the sort switch to sort by each item. press the "new" button to display the page where you can create a new access list. press the "setting" button to show the page where you can change the settings of the selected access list. if you press the "delete" button, all access lists whose check boxes are selected will be deleted. access lists that are applied to class maps cannot be deleted. on this page, you can reference and configure up to 512 access lists.</div><div class="display_word">2.1. Access lists The information for the access list you created will be displayed. The table items are explained below. ID The access list ID will be displayed. Type The access list type will be displayed. Description The description text set in this access list will be displayed. A maximum of 20 items can be displayed for one page. Press or or enter a numeric value to switch between pages. You can press the sort switch to sort by each item. Press the "New" button to display the page where you can create a new access list. Press the "Setting" button to show the page where you can change the settings of the selected access list. If you press the "Delete" button, all access lists whose check boxes are selected will be deleted. Access lists that are applied to class maps cannot be deleted. On this page, you can reference and configure up to 512 access lists.</div></div><div id="gui_en_detail_acl_create"><div class="search_title" docfname="gui_en_detail_acl_create" doctitle="Create" link="#setting_acl">3. Access list settings page</div><div class="search_word">3. access list settings page this page is for creating new access lists, or for changing the settings of existing access lists. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Access list settings page This page is for creating new access lists, or for changing the settings of existing access lists. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_acl_create"><div class="search_title" docfname="gui_en_detail_acl_create" doctitle="Create" link="#access_list_settings">3.1. Access list settings</div><div class="search_word">3.1. access list settings access list select the access list type from the following items. ipv4 access list ipv6 access list mac access list when changing the settings, the access list type cannot be changed. the ipv6 access list settings cannot be configured when the stack function is enabled. access list id set the configurable access list id from the following ranges, according to the access list type. ipv4 access lists 1 - 2000 ipv6 access lists 3001 - 4000 mac access lists 2001 - 3000 when changing the settings, the access list id cannot be changed. description specify the description text using up to 32 single-byte alphanumeric characters and symbols. the "?" character cannot be used in the description text. control conditions specify the control conditions for the access list. up to 256 control conditions can be configured per access list. press the "add" button to display the "control condition settings" dialog. in the "control condition settings"dialog, you can specify conditions for which traffic is permitted anddenied as per the following items. operation select the actions to be taken when the traffic matches the control conditions, shown in the items below. permit deny source address select the source address to be targeted from the following items. all addresses specify host address specifying a network address this cannot be specified for a mac access list. specify host address with wildcard bit specify the address and wildcard mask. this cannot be specified for a ipv6 access list. if the wildcard mask bit is "1," the bit in the same address position will not be checked. when specifying the conditions for subnet 192.168.1.0/24, do so as shown below. address : 192.168.1.0, wildcard mask : 0.0.0.255 when specifying the conditions for vendor code 00-a0-de- - -*, do so as shown below. address : 00a0.de00.0000, wildcard mask : 0000.00ff.ffff destination address the details for the items to be set for the destination address are equivalent to those of the source address . this cannot be specified for a ipv6 access list. protocol select the protocol to be targeted from the following items. all protocols tcp udp icmp specify protocol number input a protocol number from 0 to 255. when selecting tcp or udp as a protocol, specifying the source and destination port numbers. you can specify either a single number or a number range for the port number. input a port number from 0 to 65535. when selecting tcp as a protocol, you can specify the conditions regarding the tcp vendor control flag. if more than one bit is specified, it works under the and condition. packets with all the specified bits set to 1 are targets. for example, you can deny only tcp connections from outside to inside by allowing only packets withack bit or rst bit of 1 for the interface’s direction. in this case, you need to settwo control conditions. one is to allow packets with an ack bit value of 1, and the other is to allow packets with an rst bit value of 1. this cannot be specified for a mac access list or a ipv6 access list. press the "delete" button to delete the corresponding control conditions. press the or icons to change the order in which the control conditions are applied. when evaluating the control conditions,control conditions with earlier numbers will be evaluated first; and ifthe conditions match, the conditions that follow will not be checked.</div><div class="display_word">3.1. Access list settings Access list Select the access list type from the following items. IPv4 access list IPv6 access list MAC access list When changing the settings, the access list type cannot be changed. The IPv6 access list settings cannot be configured when the stack function is enabled. Access list ID Set the configurable access list ID from the following ranges, according to the access list type. IPv4 access lists 1 - 2000 IPv6 access lists 3001 - 4000 MAC access lists 2001 - 3000 When changing the settings, the access list ID cannot be changed. Description Specify the description text using up to 32 single-byte alphanumeric characters and symbols. The "?" character cannot be used in the description text. Control conditions Specify the control conditions for the access list. Up to 256 control conditions can be configured per access list. Press the "Add" button to display the "Control condition settings" dialog. In the "Control condition settings"dialog, you can specify conditions for which traffic is permitted anddenied as per the following items. Operation Select the actions to be taken when the traffic matches the control conditions, shown in the items below. Permit Deny Source address Select the source address to be targeted from the following items. All addresses Specify host address Specifying a network address This cannot be specified for a MAC access list. Specify host address with wildcard bit Specify the address and wildcard mask. This cannot be specified for a IPv6 access list. If the wildcard mask bit is "1," the bit in the same address position will not be checked. When specifying the conditions for subnet 192.168.1.0/24, do so as shown below. Address : 192.168.1.0, Wildcard mask : 0.0.0.255 When specifying the conditions for vendor code 00-A0-DE- - -*, do so as shown below. Address : 00A0.DE00.0000, Wildcard mask : 0000.00FF.FFFF Destination address The details for the items to be set for the destination address are equivalent to those of the source address . This cannot be specified for a IPv6 access list. Protocol Select the protocol to be targeted from the following items. All protocols TCP UDP ICMP Specify protocol number Input a protocol number from 0 to 255. When selecting TCP or UDP as a protocol, specifying the source and destination port numbers. You can specify either a single number or a number range for the port number. Input a port number from 0 to 65535. When selecting TCP as a protocol, you can specify the conditions regarding the TCP vendor control flag. If more than one bit is specified, it works under the AND condition. Packets with all the specified bits set to 1 are targets. For example, you can deny only TCP connections from outside to inside by allowing only packets withACK bit or RST bit of 1 for the interface’s direction. In this case, you need to settwo control conditions. One is to allow packets with an ACK bit value of 1, and the other is to allow packets with an RST bit value of 1. This cannot be specified for a MAC access list or a IPv6 access list. Press the "Delete" button to delete the corresponding control conditions. Press the or icons to change the order in which the control conditions are applied. When evaluating the control conditions,control conditions with earlier numbers will be evaluated first; and ifthe conditions match, the conditions that follow will not be checked.</div></div><div id="gui_en_detail_auth_func"><div class="search_title" docfname="gui_en_detail_auth_func" doctitle="Port" link="#title-box">Port authentication settings</div><div class="search_word">port authentication settings</div><div class="display_word">Port authentication settings</div></div><div id="gui_en_detail_auth_func"><div class="search_title" docfname="gui_en_detail_auth_func" doctitle="Port" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring the port authentication. to use port authentication, you need to configure the system settings and the interface settings. you also need to configure the authentication server in interface settings > port authentication > server settings .</div><div class="display_word">1. Summary This page is for configuring the port authentication. To use port authentication, you need to configure the system settings and the interface settings. You also need to configure the authentication server in Interface settings > Port authentication > Server settings .</div></div><div id="gui_en_detail_auth_func"><div class="search_title" docfname="gui_en_detail_auth_func" doctitle="Port" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the port authentication settings.</div><div class="display_word">2. Top page This is the top page for the port authentication settings.</div></div><div id="gui_en_detail_auth_func"><div class="search_title" docfname="gui_en_detail_auth_func" doctitle="Port" link="#system_settings">2.1. System settings</div><div class="search_word">2.1. system settings displays the port authentication settings for the system. the table items are explained below. 802.1x authentication displays whether 802.1x authentication is enabled or not for the entire system. mac authentication displays whether mac authentication is enabled or not for the entire system. web authentication displays whether web authentication is enabled or not for the entire system. press the "setting" button to display the page for configuring the system settings.</div><div class="display_word">2.1. System settings Displays the port authentication settings for the system. The table items are explained below. 802.1X authentication Displays whether 802.1X authentication is enabled or not for the entire system. MAC authentication Displays whether MAC authentication is enabled or not for the entire system. Web authentication Displays whether web authentication is enabled or not for the entire system. Press the "Setting" button to display the page for configuring the system settings.</div></div><div id="gui_en_detail_auth_func"><div class="search_title" docfname="gui_en_detail_auth_func" doctitle="Port" link="#interface_settings">2.2. Interface settings</div><div class="search_word">2.2. interface settings displays the port authentication settings for the interface. the table items are explained below. i/f displays the interface name. enabled authentication functions displays the enabled authentication functions for the interface. host mode displays the authentication operation mode setting. press the "setting" button to display the page for changing the settings of the selected interface. press the "specify all" button to configure all interfaces with the check box selected. if you press the "return to defaults" button, the settings will be initialized on all interfaces whose check boxes are selected.</div><div class="display_word">2.2. Interface settings Displays the port authentication settings for the interface. The table items are explained below. I/F Displays the interface name. Enabled authentication functions Displays the enabled authentication functions for the interface. Host mode Displays the authentication operation mode setting. Press the "Setting" button to display the page for changing the settings of the selected interface. Press the "Specify all" button to configure all interfaces with the check box selected. If you press the "Return to defaults" button, the settings will be initialized on all interfaces whose check boxes are selected.</div></div><div id="gui_en_detail_auth_func"><div class="search_title" docfname="gui_en_detail_auth_func" doctitle="Port" link="#system">3. System settings page</div><div class="search_word">3. system settings page this page is for configuring the port authentication for the system. you can also change the detailed settings by pressing the "advanced settings" button. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. System settings page This page is for configuring the port authentication for the system. You can also change the detailed settings by pressing the "Advanced settings" button. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_auth_func"><div class="search_title" docfname="gui_en_detail_auth_func" doctitle="Port" link="#system_settings_2">3.1. System settings</div><div class="search_word">3.1. system settings authentication functions to be enabled select the authentication functions to be enabled for the entire system from the following. 802.1x authentication mac authentication web authentication mac address format for mac authentication select the mac address format for mac authentication from the following. delimiter (-), lowercase delimiter (:), lowercase no delimiter, lowercase delimiter (-), uppercase delimiter (:), uppercase no delimiter, uppercase redirect url after successful web authentication specify the destination url for redirecting the authenticated device after successful web authentication. enter up to 256 characters using single-byte alphanumeric characters and symbols, excluding ? symbol. clearing authentication status specify whether or not to clear the authentication status of the device periodically. the input range of the time to clear is from 0 to 23 o’clock. if clearing authentication status is set in the interface settings, the setting in the interface settings takes precedence.</div><div class="display_word">3.1. System settings Authentication functions to be enabled Select the authentication functions to be enabled for the entire system from the following. 802.1X authentication MAC authentication Web authentication MAC address format for MAC authentication Select the MAC address format for MAC authentication from the following. Delimiter (-), Lowercase Delimiter (:), Lowercase No delimiter, Lowercase Delimiter (-), Uppercase Delimiter (:), Uppercase No delimiter, Uppercase Redirect URL after successful web authentication Specify the destination URL for redirecting the authenticated device after successful web authentication. Enter up to 256 characters using single-byte alphanumeric characters and symbols, excluding ? symbol. Clearing authentication status Specify whether or not to clear the authentication status of the device periodically. The input range of the time to clear is from 0 to 23 o’clock. If Clearing authentication status is set in the interface settings, the setting in the interface settings takes precedence.</div></div><div id="gui_en_detail_auth_func"><div class="search_title" docfname="gui_en_detail_auth_func" doctitle="Port" link="#interface">4. Interface settings page</div><div class="search_word">4. interface settings page this page is for configuring the port authentication for the interface. you can also change the detailed settings by pressing the "advanced settings" button. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Interface settings page This page is for configuring the port authentication for the interface. You can also change the detailed settings by pressing the "Advanced settings" button. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_auth_func"><div class="search_title" docfname="gui_en_detail_auth_func" doctitle="Port" link="#interface_settings_2">4.1. Interface settings</div><div class="search_word">4.1. interface settings applicable interface displays the name of the interface whose settings are to be changed. authentication functions to be enabled select authentication functions to be enabled for the interface from the following. 802.1x authentication mac authentication web authentication host mode select the authentication operation mode for the authentication function from the following. single host mode if the device connected to the interface has successfully authenticated, only the device can access. if another device has already authenticated, this device cannot authenticate or access. multi host mode if any device connected to the interface has successfully authenticated, all devices connected to the interface can access. multi supplicant mode ( recommended ) all devices connected to theinterface can individually authenticate, and only the devicessuccessfully authenticated can access. authentication order select which authentication to use first if both 802.1x authentication and mac authentication are enabled. 802.1x authentication first mac authentication first web authentication authenticates when id and password are entered regardless of this setting. mac address registration type after mac authentication select a registration type for authenticated mac addresses to the mac address table. register as dynamic entry register as static entry the aging timer automatically deletes mac addresses registered as dynamic entries from the mac address table. the "clear auth state" or the "authclear-state time" command can delete mac addresses registered as staticentries from the mac address table. guest vlan specify the guest vlan. press the "select" button, and then select a vlan id from the "vlan list" dialog. when a guest vlan is configured, devices that have not successfully authenticated can also access the specified vlan. this cannot be used with web authentication. dynamic vlan specify whether or not to use dynamic vlan. if you set to use dynamic vlan, vlans are dynamically assigned to each device that has successfully authenticated. the vlan to be assigned depends on the authentication server settings. waiting time for a response from device specify the waiting time for a response from the device during authentication. the input range is from 1 to 65535 seconds. authentication restriction period after authentication failure specify the period to restrict authentication after the authentication of a device fails. the input range is from 1 to 65535 seconds. while authentication is restricted, all packets received on the target interface are discarded. re-authentication of authenticated device specify whether or not to periodically re-authenticate the device that has successfully authenticated. the input range of the re-authentication interval is from 300 to 86400 seconds. clearing authentication status specify whether or not to clear the authentication status of the device periodically. the input range of the time to clear is from 0 to 23 o’clock. 802.1x authentication operation mode select the operation mode for 802.1x authentication from the following. operate as authentication interface set as authenticated interface set as unauthenticated interface forwarding control on unauthenticated ports for 802.1x authentication when 802.1x authentication is enabled,specify the communication restriction method for devices that have notsuccessfully authenticated from the following. discard both sending and receiving discard only receiving if any of the following conditions are met, this setting is ignored, and the function operates as discard only receiving . host mode is set to multi-supplicant mode. mac authentication is enabled. if the guest vlan is configured, this setting does not affect the communication restrictions. number of times to send eapol packets specify the maximum number of times to send eapol packets. the input range is from 1 to 10 times.</div><div class="display_word">4.1. Interface settings Applicable interface Displays the name of the interface whose settings are to be changed. Authentication functions to be enabled Select authentication functions to be enabled for the interface from the following. 802.1X authentication MAC authentication Web authentication Host mode Select the authentication operation mode for the authentication function from the following. Single host mode If the device connected to the interface has successfully authenticated, only the device can access. If another device has already authenticated, this device cannot authenticate or access. Multi host mode If any device connected to the interface has successfully authenticated, all devices connected to the interface can access. Multi supplicant mode ( Recommended ) All devices connected to theinterface can individually authenticate, and only the devicessuccessfully authenticated can access. Authentication order Select which authentication to use first if both 802.1X authentication and MAC authentication are enabled. 802.1X authentication first MAC authentication first Web authentication authenticates when ID and Password are entered regardless of this setting. MAC address registration type after MAC authentication Select a registration type for authenticated MAC addresses to the MAC address table. Register as dynamic entry Register as static entry The aging timer automatically deletes MAC addresses registered as dynamic entries from the MAC address table. The "clear auth state" or the "authclear-state time" command can delete MAC addresses registered as staticentries from the MAC address table. Guest VLAN Specify the guest VLAN. Press the "Select" button, and then select a VLAN ID from the "VLAN list" dialog. When a guest VLAN is configured, devices that have not successfully authenticated can also access the specified VLAN. This cannot be used with web authentication. Dynamic VLAN Specify whether or not to use dynamic VLAN. If you set to use dynamic VLAN, VLANs are dynamically assigned to each device that has successfully authenticated. The VLAN to be assigned depends on the authentication server settings. Waiting time for a response from device Specify the waiting time for a response from the device during authentication. The input range is from 1 to 65535 seconds. Authentication restriction period after authentication failure Specify the period to restrict authentication after the authentication of a device fails. The input range is from 1 to 65535 seconds. While authentication is restricted, all packets received on the target interface are discarded. Re-authentication of authenticated device Specify whether or not to periodically re-authenticate the device that has successfully authenticated. The input range of the re-authentication interval is from 300 to 86400 seconds. Clearing authentication status Specify whether or not to clear the authentication status of the device periodically. The input range of the time to clear is from 0 to 23 o’clock. 802.1X authentication operation mode Select the operation mode for 802.1X authentication from the following. Operate as authentication interface Set as authenticated interface Set as unauthenticated interface Forwarding control on unauthenticated ports for 802.1X authentication When 802.1X authentication is enabled,specify the communication restriction method for devices that have notsuccessfully authenticated from the following. Discard both sending and receiving Discard only receiving If any of the following conditions are met, this setting is ignored, and the function operates as Discard only receiving . Host mode is set to multi-supplicant mode. MAC authentication is enabled. If the guest VLAN is configured, this setting does not affect the communication restrictions. Number of times to send EAPOL packets Specify the maximum number of times to send EAPOL packets. The input range is from 1 to 10 times.</div></div><div id="gui_en_detail_auth_manage"><div class="search_title" docfname="gui_en_detail_auth_manage" doctitle="Authentication" link="#title-box">Authentication management</div><div class="search_word">authentication management</div><div class="display_word">Authentication management</div></div><div id="gui_en_detail_auth_manage"><div class="search_title" docfname="gui_en_detail_auth_manage" doctitle="Authentication" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for managing authentication. you can check and delete the authentication information of the device.</div><div class="display_word">1. Summary This page is for managing authentication. You can check and delete the authentication information of the device.</div></div><div id="gui_en_detail_auth_manage"><div class="search_title" docfname="gui_en_detail_auth_manage" doctitle="Authentication" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the authentication management.</div><div class="display_word">2. Top page This is the top page for the authentication management.</div></div><div id="gui_en_detail_auth_manage"><div class="search_title" docfname="gui_en_detail_auth_manage" doctitle="Authentication" link="#authentication_information_of_devices">2.1. Authentication information of devices</div><div class="search_word">2.1. authentication information of devices displays the authentication information for each device. the table items are explained below. port displays the interface to which the device is connected. name displays the name of the device. mac address displays the mac address of the device. authentication method displays the authentication method used to authenticate the device. state displays the authentication status of the device. vlan displays the vlan to which the device belongs. a maximum of 100 items can be displayed for one page. press or or enter a numeric value to switch between pages. you can press the sort switch to sort by each item. press the "update" button to update the device’s authentication information to the latest status. press the "delete" button to delete all authentication information with the check box selected.</div><div class="display_word">2.1. Authentication information of devices Displays the authentication information for each device. The table items are explained below. Port Displays the interface to which the device is connected. Name Displays the name of the device. MAC address Displays the MAC address of the device. Authentication method Displays the authentication method used to authenticate the device. State Displays the authentication status of the device. VLAN Displays the VLAN to which the device belongs. A maximum of 100 items can be displayed for one page. Press or or enter a numeric value to switch between pages. You can press the sort switch to sort by each item. Press the "Update" button to update the device’s authentication information to the latest status. Press the "Delete" button to delete all authentication information with the check box selected.</div></div><div id="gui_en_detail_auth_server"><div class="search_title" docfname="gui_en_detail_auth_server" doctitle="Server" link="#title-box">Server settings</div><div class="search_word">server settings</div><div class="display_word">Server settings</div></div><div id="gui_en_detail_auth_server"><div class="search_title" docfname="gui_en_detail_auth_server" doctitle="Server" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring the authentication server. configure the authentication server for port authentication. to use the built-in radius server as an authenticationserver, you need to configure the built-in radius server in application layer > radius server > server settings . the authentication server can be configured manually as a fixed setting or automatically using the auto-configure via lldpfunction. to enable automatic settings, enable the "auto-configure via lldp function" in management > lldp . then the radius server notified by lldp has configured automatically.</div><div class="display_word">1. Summary This page is for configuring the authentication server. Configure the authentication server for port authentication. To use the built-in RADIUS server as an authenticationserver, you need to configure the built-in RADIUS server in Application layer > RADIUS server > Server settings . The authentication server can be configured manually as a fixed setting or automatically using the auto-configure via LLDPfunction. To enable automatic settings, enable the "auto-configure via LLDP function" in Management > LLDP . Then the RADIUS server notified by LLDP has configured automatically.</div></div><div id="gui_en_detail_auth_server"><div class="search_title" docfname="gui_en_detail_auth_server" doctitle="Server" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the server settings.</div><div class="display_word">2. Top page This is the top page for the Server settings.</div></div><div id="gui_en_detail_auth_server"><div class="search_title" docfname="gui_en_detail_auth_server" doctitle="Server" link="#authentication_radius_server_settings">2.1. Authentication RADIUS server settings</div><div class="search_word">2.1. authentication radius server settings displays the authentication radius server settings. the table items are explained below. address displays the authentication server address. port number displays the authentication server port number. press the "new" button to display the page for configuring a new authentication server. press the "setting" button to display the page for changing the selected authentication server’s settings. press the "delete" button to delete all authentication servers with the check box selected. press the "register" button to configure the auto-configured radius server as a fixed setting. up to eight authentication server settings can be created, including fixed and automatic settings. if both fixed settings and automatic settings are configured, the fixed settings are used first. if you create a new fixed setting under thenumber of authentication server settings reached the maximum, thesetting with the largest lldp receiving port number is deleted from thesettings configured automatically via lldp.</div><div class="display_word">2.1. Authentication RADIUS server settings Displays the authentication RADIUS server settings. The table items are explained below. Address Displays the authentication server address. Port number Displays the authentication server port number. Press the "New" button to display the page for configuring a new authentication server. Press the "Setting" button to display the page for changing the selected authentication server’s settings. Press the "Delete" button to delete all authentication servers with the check box selected. Press the "Register" button to configure the auto-configured RADIUS server as a fixed setting. Up to eight authentication server settings can be created, including fixed and automatic settings. If both fixed settings and automatic settings are configured, the fixed settings are used first. If you create a new fixed setting under thenumber of authentication server settings reached the maximum, thesetting with the largest LLDP receiving port number is deleted from thesettings configured automatically via LLDP.</div></div><div id="gui_en_detail_auth_server"><div class="search_title" docfname="gui_en_detail_auth_server" doctitle="Server" link="#common_detailed_settings">2.2. Common detailed settings</div><div class="search_word">2.2. common detailed settings displays the common detailed settings. the table items are explained below. waiting time for a response per server displays the waiting time for a response per server. number of times to resend requests to server displays the number of times to resend requests to the server. server usage restriction period displays the period for server usage restriction. nas-identifier attribute to be notified to the server displays the nas-identifier attribute to be notified to the server. press the "setting" button to display the page for changing the common detailed settings.</div><div class="display_word">2.2. Common detailed settings Displays the common detailed settings. The table items are explained below. Waiting time for a response per server Displays the waiting time for a response per server. Number of times to resend requests to server Displays the number of times to resend requests to the server. Server usage restriction period Displays the period for server usage restriction. NAS-Identifier attribute to be notified to the server Displays the NAS-Identifier attribute to be notified to the server. Press the "Setting" button to display the page for changing the common detailed settings.</div></div><div id="gui_en_detail_auth_server"><div class="search_title" docfname="gui_en_detail_auth_server" doctitle="Server" link="#radius">3. Authentication RADIUS server settings page</div><div class="search_word">3. authentication radius server settings page this page is for configuring the authentication radius server. you can also change the detailed settings by pressing the "advanced settings" button. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Authentication RADIUS server settings page This page is for configuring the authentication RADIUS server. You can also change the detailed settings by pressing the "Advanced settings" button. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_auth_server"><div class="search_title" docfname="gui_en_detail_auth_server" doctitle="Server" link="#authentication_radius_server_settings_2">3.1. Authentication RADIUS server settings</div><div class="search_word">3.1. authentication radius server settings server type select the authentication server type from the following. use built-in radius server use external radius server if you select use built-in radius server , the following settings are specified with predetermined values. server address server port number shared password with server this item appears only for new settings. server address specify the address of the authentication server. enter the address in one of the following formats. ipv4 address : xxx.xxx.xxx.xxx ipv6 global address : xxxx:xxxx::xxxx:xxxx ipv6 link-local address : fe80::x%vlann to change the setting, you need to start over from a new setting. server port number specify the port number of the authentication server. the input range is from 0 to 65535. shared password with server specify the shared password with the authentication server. enter up to 128 characters using single-byte alphanumeric characters and symbols, excluding ? and space symbols. if you omit the input, the shared password set in the common detailed settings is applied. waiting time for a response from server specify the waiting time for a response from the authentication server. the input range is from 1 to 1000 seconds. if you omit the input, the waiting time for a response per server set in the common detailed settings is applied. number of times to resend requests to server specify the number of times to resend requests to the server when the authentication server’s response times out. the input range is from 0 to 100 times. if you omit the input, the number of times to resend requests to the server set in the common detailed settings is applied.</div><div class="display_word">3.1. Authentication RADIUS server settings Server type Select the authentication server type from the following. Use built-in RADIUS server Use external RADIUS server If you select Use built-in RADIUS server , the following settings are specified with predetermined values. Server address Server port number Shared password with server This item appears only for new settings. Server address Specify the address of the authentication server. Enter the address in one of the following formats. IPv4 address : XXX.XXX.XXX.XXX IPv6 global address : XXXX:XXXX::XXXX:XXXX IPv6 link-local address : fe80::X%vlanN To change the setting, you need to start over from a new setting. Server port number Specify the port number of the authentication server. The input range is from 0 to 65535. Shared password with server Specify the shared password with the authentication server. Enter up to 128 characters using single-byte alphanumeric characters and symbols, excluding ? and space symbols. If you omit the input, the shared password set in the common detailed settings is applied. Waiting time for a response from server Specify the waiting time for a response from the authentication server. The input range is from 1 to 1000 seconds. If you omit the input, the waiting time for a response per server set in the common detailed settings is applied. Number of times to resend requests to server Specify the number of times to resend requests to the server when the authentication server’s response times out. The input range is from 0 to 100 times. If you omit the input, the number of times to resend requests to the server set in the common detailed settings is applied.</div></div><div id="gui_en_detail_auth_server"><div class="search_title" docfname="gui_en_detail_auth_server" doctitle="Server" link="#common">4. Common detailed settings page</div><div class="search_word">4. common detailed settings page this page is for changing the common detailed settings of the authentication server. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Common detailed settings page This page is for changing the common detailed settings of the authentication server. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_auth_server"><div class="search_title" docfname="gui_en_detail_auth_server" doctitle="Server" link="#common_detailed_settings_2">4.1. Common detailed settings</div><div class="search_word">4.1. common detailed settings shared password with server specify the shared password with the authentication server. enter up to 128 characters using single-byte alphanumeric characters and symbols, excluding ? and space symbols. waiting time for a response from server specify the waiting time for a response from the authentication server. the input range is from 1 to 1000 seconds. number of times to resend requests to server specify the number of times to resend requests to the server when the authentication server’s response times out. the input range is from 0 to 100 times. server usage restriction period specify the period to restrict the use ofthe authentication server temporarily for when the server does not reply after resending requests. the input range is from 0 to 1440 minutes. nas-identifier attribute to be notified to the server specify the nas-identifier attribute to be notified to the authentication server. enter up to 253 characters using single-byte alphanumeric characters and symbols, excluding ? symbol.</div><div class="display_word">4.1. Common detailed settings Shared password with server Specify the shared password with the authentication server. Enter up to 128 characters using single-byte alphanumeric characters and symbols, excluding ? and space symbols. Waiting time for a response from server Specify the waiting time for a response from the authentication server. The input range is from 1 to 1000 seconds. Number of times to resend requests to server Specify the number of times to resend requests to the server when the authentication server’s response times out. The input range is from 0 to 100 times. Server usage restriction period Specify the period to restrict the use ofthe authentication server temporarily for when the server does not reply after resending requests. The input range is from 0 to 1440 minutes. NAS-Identifier attribute to be notified to the server Specify the NAS-Identifier attribute to be notified to the authentication server. Enter up to 253 characters using single-byte alphanumeric characters and symbols, excluding ? symbol.</div></div><div id="gui_en_detail_auth_web"><div class="search_title" docfname="gui_en_detail_auth_web" doctitle="Web" link="#title-box">Web authentication screen</div><div class="search_word">web authentication screen</div><div class="display_word">Web authentication screen</div></div><div id="gui_en_detail_auth_web"><div class="search_title" docfname="gui_en_detail_auth_web" doctitle="Web" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for customizing the web authentication screen. you can customize the authentication screen for web authentication. for the specific customization method, please refer to interface control functions > port authentication functions > 3.3.2 customizing the authentication screen in the technical data for this product in yamaha network devices technical documentation .</div><div class="display_word">1. Summary This page is for customizing the web authentication screen. You can customize the authentication screen for web authentication. For the specific customization method, please refer to Interface control functions > Port authentication functions > 3.3.2 Customizing the authentication screen in the technical data for this product in Yamaha Network Devices Technical Documentation .</div></div><div id="gui_en_detail_auth_web"><div class="search_title" docfname="gui_en_detail_auth_web" doctitle="Web" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the web authentication screen.</div><div class="display_word">2. Top page This is the top page for the web authentication screen.</div></div><div id="gui_en_detail_auth_web"><div class="search_title" docfname="gui_en_detail_auth_web" doctitle="Web" link="#customizing_the_web_authentication_screen">2.1. Customizing the web authentication screen</div><div class="search_word">2.1. customizing the web authentication screen displays whether customization has been applied or not. if the customization has been applied, you can disable the customization by pressing the "disable" button. press the "next" button to the right of"download the original files for customization" to download the original files for customization. press the "next" button to the right of "apply the customized files" to open the page to apply the customization.</div><div class="display_word">2.1. Customizing the web authentication screen Displays whether customization has been applied or not. If the customization has been applied, you can disable the customization by pressing the "Disable" button. Press the "Next" button to the right of"Download the original files for customization" to download the original files for customization. Press the "Next" button to the right of "Apply the customized files" to open the page to apply the customization.</div></div><div id="gui_en_detail_auth_web"><div class="search_title" docfname="gui_en_detail_auth_web" doctitle="Web" link="#apply">3. Applying customization page</div><div class="search_word">3. applying customization page this page is for customizing the web authentication screen. select the customized file from "select a file", andpress the "confirm" button. if the information entered in theconfirmation screen is correct, press the "ok" button.</div><div class="display_word">3. Applying customization page This page is for customizing the web authentication screen. Select the customized file from "Select a file", andpress the "Confirm" button. If the information entered in theconfirmation screen is correct, press the "OK" button.</div></div><div id="gui_en_detail_auth_web"><div class="search_title" docfname="gui_en_detail_auth_web" doctitle="Web" link="#applying_customization">3.1. Applying customization</div><div class="search_word">3.1. applying customization logo file (.png) specify the logo file. the file extension has to be .png. header file (.html) specify the header file. the file extension has to be .html. footer file (.html) specify the footer file. the file extension has to be .html. css file (.css) specifies the css file. the file extension has to be .css.</div><div class="display_word">3.1. Applying customization Logo file (.png) Specify the logo file. The file extension has to be .png. Header file (.html) Specify the header file. The file extension has to be .html. Footer file (.html) Specify the footer file. The file extension has to be .html. CSS file (.css) Specifies the CSS file. The file extension has to be .css.</div></div><div id="gui_en_detail_dhcp_snooping"><div class="search_title" docfname="gui_en_detail_dhcp_snooping" doctitle="DHCP" link="#title-box">DHCP snooping</div><div class="search_word">dhcp snooping</div><div class="display_word">DHCP snooping</div></div><div id="gui_en_detail_dhcp_snooping"><div class="search_title" docfname="gui_en_detail_dhcp_snooping" doctitle="DHCP" link="#summary">1. Summary</div><div class="search_word">1. summary this page is for configuring dhcp snooping.</div><div class="display_word">1. Summary This page is for configuring DHCP snooping.</div></div><div id="gui_en_detail_dhcp_snooping"><div class="search_title" docfname="gui_en_detail_dhcp_snooping" doctitle="DHCP" link="#top">2. Top page</div><div class="search_word">2. top page this is the top page of dhcp snooping.</div><div class="display_word">2. Top page This is the top page of DHCP Snooping.</div></div><div id="gui_en_detail_dhcp_snooping"><div class="search_title" docfname="gui_en_detail_dhcp_snooping" doctitle="DHCP" link="#display_binding_database">2.1. Display Binding Database</div><div class="search_word">2.1. display binding database clicking the "next" button will display a page where you can check the information of dhcp clients registered in thebinding database. if the system-wide dhcp snooping feature is disabled, the "next" button cannot be pressed.</div><div class="display_word">2.1. Display Binding Database Clicking the "Next" button will display a page where you can check the information of DHCP clients registered in thebinding database. If the system-wide DHCP snooping feature is disabled, the "Next" button cannot be pressed.</div></div><div id="gui_en_detail_dhcp_snooping"><div class="search_title" docfname="gui_en_detail_dhcp_snooping" doctitle="DHCP" link="#system_settings">2.2. System settings</div><div class="search_word">2.2. system settings displays the dhcp snooping settings in the system. the table items are explained below. dhcp snooping function for the entire system displays whether or not dhcp snooping is enabled for the entire system. mac address verification displays whether or not to enable forwarding dhcp packets with option 82 information via untrusted ports. mac address verification processcompares the source mac address for packets received via an untrustedport with the client hardware address and discards corresponding dhcppackets if the addresses do not match. dhcp packets receiving rate limit the setting for the number of dhcp packets that can be received per second is displayed. option 82 function shows whether option 82 information is to be assigned, inspected, or deleted. forward packets with option 82 displays whether or not to enable forwarding of dhcp packets with option 82 information on the untrusted port. output to syslog displays whether the reason for discarding dhcp packets is output to syslog. pressing the "settings" button will bring up a page where you can configure the system settings.</div><div class="display_word">2.2. System settings Displays the DHCP snooping settings in the system. The table items are explained below. DHCP snooping function for the entire system Displays whether or not DHCP snooping is enabled for the entire system. MAC address verification Displays whether or not to enable forwarding DHCP packets with Option 82 information via untrusted ports. MAC address verification processcompares the source MAC address for packets received via an untrustedport with the client hardware address and discards corresponding DHCPpackets if the addresses do not match. DHCP packets receiving rate limit The setting for the number of DHCP packets that can be received per second is displayed. Option 82 function Shows whether Option 82 information is to be assigned, inspected, or deleted. Forward packets with Option 82 Displays whether or not to enable forwarding of DHCP packets with Option 82 information on the Untrusted port. Output to SYSLOG Displays whether the reason for discarding DHCP packets is output to SYSLOG. Pressing the "Settings" button will bring up a page where you can configure the system settings.</div></div><div id="gui_en_detail_dhcp_snooping"><div class="search_title" docfname="gui_en_detail_dhcp_snooping" doctitle="DHCP" link="#vlan_interface_settings">2.3. VLAN interface settings</div><div class="search_word">2.3. vlan interface settings displays the dhcp snooping function setting for each vlan interface. the table items are explained below. vlan id vlan id is displayed. dhcp snooping function displays whether the dhcp snooping function is enabled for the corresponding vlan id. remote id displays the string assigned to the option 82 remote id. circuit id displays information assigned to the option 82 circuit id. press the "setting" button to access a page where you can change the settings of the selected vlan. press the "specify all" button to configure the settings for all vlan interfaces with the check box selected. press the "return to defaults" button to initialize the settings for all vlan interfaces with the check box selected.</div><div class="display_word">2.3. VLAN interface settings Displays the DHCP snooping function setting for each VLAN interface. The table items are explained below. VLAN ID VLAN ID is displayed. DHCP snooping function Displays whether the DHCP snooping function is enabled for the corresponding VLAN ID. Remote ID Displays the string assigned to the Option 82 remote ID. Circuit ID Displays information assigned to the Option 82 circuit ID. Press the "Setting" button to access a page where you can change the settings of the selected VLAN. Press the "Specify all" button to configure the settings for all VLAN interfaces with the check box selected. Press the "Return to defaults" button to initialize the settings for all VLAN interfaces with the check box selected.</div></div><div id="gui_en_detail_dhcp_snooping"><div class="search_title" docfname="gui_en_detail_dhcp_snooping" doctitle="DHCP" link="#interface_settings">2.4. Interface settings</div><div class="search_word">2.4. interface settings displays the dhcp snooping function setting for each interface. the table items are explained below. port displays the name of port for which the settings is to be changed. port type displays whether the corresponding port is trusted or untrusted. subscriber id displays the string assigned to the option 82 subscriber id. press the "setting" button to display the page for configuring the selected interface. press the "specify all" button to configure the settings for all interfaces with the check box selected. press the "return to defaults" button to initialize the settings for all interfaces with the check box selected.</div><div class="display_word">2.4. Interface settings Displays the DHCP snooping function setting for each interface. The table items are explained below. Port Displays the name of port for which the settings is to be changed. Port type Displays whether the corresponding port is trusted or untrusted. Subscriber ID Displays the string assigned to the Option 82 subscriber ID. Press the "Setting" button to display the page for configuring the selected interface. Press the "Specify all" button to configure the settings for all interfaces with the check box selected. Press the "Return to defaults" button to initialize the settings for all interfaces with the check box selected.</div></div><div id="gui_en_detail_dhcp_snooping"><div class="search_title" docfname="gui_en_detail_dhcp_snooping" doctitle="DHCP" link="#binding_db">3. Display Binding Database page</div><div class="search_word">3. display binding database page this page displays information about dhcp clients registered in the binding database.</div><div class="display_word">3. Display Binding Database page This page displays information about DHCP clients registered in the binding database.</div></div><div id="gui_en_detail_dhcp_snooping"><div class="search_title" docfname="gui_en_detail_dhcp_snooping" doctitle="DHCP" link="#binding_database">3.1. Binding database</div><div class="search_word">3.1. binding database displays information on dhcp clients registered in the binding database. up to 256 items will be displayed. you can search neighbor information from the "search" box. press to execute the search. press to clear the search. you can use regular expressions shown below in search keywords. lowercase and capital letters are treated the same for keywords. syntax explanation a the character "a" abc the characters "abc" [abc] one character, either "a", "b" or "c" [a-c] one character between "a" and "c" [^abc] an arbitrary character that is neither "a", "b" or "c" . an arbitrary character a+ at least one "a" character a* at least zero "a" characters a? zero or one "a" character ^a a string that begins with "a" a$ a string that ends with "a" abc|def|ghi "abc", "def" or "ghi" a{2} two "a" characters (aa) a{2,} two or more "a" characters (aa, aaa, aaaa…​) a{2,3} two to three "a" characters (aa, aaa) \b word breaks, such as spaces \b any character besides \b \d an arbitrary number (same as [0-9]) \d any character besides numbers (same as [^0-9]) \s single breaking character \s any single character besides \s \w alphanumeric characters including underlines (same as [a-za-z0-9_]) \w any character besides \w press to update information to the latest information. the number of search results to display at one time can be selected by pressing "display number" on the "select" menu. press the sort switch to sort by each item. with default settings, results are sorted in ascending order of the vlan id. press the sort switch again to toggle between ascending and descending order.</div><div class="display_word">3.1. Binding database Displays information on DHCP clients registered in the binding database. Up to 256 items will be displayed. You can search neighbor information from the "Search" box. Press to execute the search. Press to clear the search. You can use regular expressions shown below in search keywords. Lowercase and capital letters are treated the same for keywords. Syntax Explanation A The character "A" ABC The characters "ABC" [ABC] One character, either "A", "B" or "C" [A-C] One character between "A" and "C" [^ABC] An arbitrary character that is neither "A", "B" or "C" . An arbitrary character A+ At least one "A" character A* At least zero "A" characters A? Zero or one "A" character ^A A string that begins with "A" A$ A string that ends with "A" ABC|DEF|GHI "ABC", "DEF" or "GHI" A{2} Two "A" characters (AA) A{2,} Two or more "A" characters (AA, AAA, AAAA…​) A{2,3} Two to three "A" characters (AA, AAA) \b Word breaks, such as spaces \B Any character besides \b \d An arbitrary number (same as [0-9]) \D Any character besides numbers (same as [^0-9]) \s Single breaking character \S Any single character besides \s \w Alphanumeric characters including underlines (same as [A-Za-z0-9_]) \W Any character besides \w Press to update information to the latest information. The number of search results to display at one time can be selected by pressing "Display number" on the "Select" menu. Press the sort switch to sort by each item. With default settings, results are sorted in ascending order of the VLAN ID. Press the sort switch again to toggle between ascending and descending order.</div></div><div id="gui_en_detail_dhcp_snooping"><div class="search_title" docfname="gui_en_detail_dhcp_snooping" doctitle="DHCP" link="#system_setting">4. System settings page</div><div class="search_word">4. system settings page this page is for configuring dhcp snooping in the system. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. System settings page This page is for configuring DHCP snooping in the system. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_dhcp_snooping"><div class="search_title" docfname="gui_en_detail_dhcp_snooping" doctitle="DHCP" link="#system_settings_2">4.1. System settings</div><div class="search_word">4.1. system settings dhcp snooping function for the entire system selects whether to enable / disable the dhcp snooping function for the entire system. mac address verification selects whether to enable / disable the mac address verification on the untrusted port. dhcp packets receiving rate limit enters the number of dhcp packets that can be received per second. option 82 function selects whether to enable / disable option 82 information assignment, inspection, and deletion. forward packets with option 82 selects whether to enable / disable forwarding packets with option 82 on the untrusted port. output to syslog selects whether to enable / disable output to syslog.</div><div class="display_word">4.1. System settings DHCP snooping function for the entire system Selects whether to enable / disable the DHCP snooping function for the entire system. MAC address verification Selects whether to enable / disable the MAC address verification on the Untrusted port. DHCP packets receiving rate limit Enters the number of DHCP packets that can be received per second. Option 82 function Selects whether to enable / disable Option 82 information assignment, inspection, and deletion. Forward packets with Option 82 Selects whether to enable / disable forwarding packets with Option 82 on the Untrusted port. Output to SYSLOG Selects whether to enable / disable output to SYSLOG.</div></div><div id="gui_en_detail_dhcp_snooping"><div class="search_title" docfname="gui_en_detail_dhcp_snooping" doctitle="DHCP" link="#vlan_interface_setting">5. VLAN Interface settings page</div><div class="search_word">5. vlan interface settings page this page is for configuring dhcp snooping on the vlan interface. you can also change the detailed settings by pressing the "advanced settings" button. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">5. VLAN Interface settings page This page is for configuring DHCP snooping on the VLAN interface. You can also change the detailed settings by pressing the "Advanced settings" button. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_dhcp_snooping"><div class="search_title" docfname="gui_en_detail_dhcp_snooping" doctitle="DHCP" link="#vlan_interface_settings_2">5.1. VLAN interface settings</div><div class="search_word">5.1. vlan interface settings vlan id displays the vlan id for which the setting is to be changed. dhcp snooping function selects whether to enable/disable the dhcp snooping function for the corresponding vlan id. remote id enters the character string to be assigned to option 82 remote id. enter up to 63 single-byte alphanumeric characters/symbols, excluding the ? symbol. circuit id enters the character string to be assigned to option 82 circuit id. enter up to 63 single-byte alphanumeric characters/symbols, excluding the ? symbol.</div><div class="display_word">5.1. VLAN interface settings VLAN ID Displays the VLAN ID for which the setting is to be changed. DHCP snooping function Selects whether to enable/disable the DHCP snooping function for the corresponding VLAN ID. Remote ID Enters the character string to be assigned to Option 82 remote ID. Enter up to 63 single-byte alphanumeric characters/symbols, excluding the ? symbol. Circuit ID Enters the character string to be assigned to Option 82 circuit ID. Enter up to 63 single-byte alphanumeric characters/symbols, excluding the ? symbol.</div></div><div id="gui_en_detail_dhcp_snooping"><div class="search_title" docfname="gui_en_detail_dhcp_snooping" doctitle="DHCP" link="#interface_setting">6. Interface settings page</div><div class="search_word">6. interface settings page this page is for setting dhcp snooping on the interface. you can also change the detailed settings by pressing the "advanced settings" button. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">6. Interface settings page This page is for setting DHCP snooping on the interface. You can also change the detailed settings by pressing the "Advanced settings" button. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_dhcp_snooping"><div class="search_title" docfname="gui_en_detail_dhcp_snooping" doctitle="DHCP" link="#interface_settings_2">6.1. Interface settings</div><div class="search_word">6.1. interface settings port displays the port name to configure the settings. dhcp snooping function port type subscriber id enters the character string to be assigned to option 82 subscriber id. enter up to 50 single-byte alphanumeric characters/symbols, excluding the ? symbol.</div><div class="display_word">6.1. Interface settings Port Displays the port name to configure the settings. DHCP snooping function Port type Subscriber ID Enters the character string to be assigned to Option 82 subscriber ID. Enter up to 50 single-byte alphanumeric characters/symbols, excluding the ? symbol.</div></div><div id="gui_en_detail_dns_client"><div class="search_title" docfname="gui_en_detail_dns_client" doctitle="DNS" link="#title-box">DNS client</div><div class="search_word">dns client</div><div class="display_word">DNS client</div></div><div id="gui_en_detail_dns_client"><div class="search_title" docfname="gui_en_detail_dns_client" doctitle="DNS" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring the dns client settings.</div><div class="display_word">1. Summary This page is for configuring the DNS client settings.</div></div><div id="gui_en_detail_dns_client"><div class="search_title" docfname="gui_en_detail_dns_client" doctitle="DNS" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the dns client.</div><div class="display_word">2. Top page This is the top page for the DNS client.</div></div><div id="gui_en_detail_dns_client"><div class="search_title" docfname="gui_en_detail_dns_client" doctitle="DNS" link="#dns_client_settings">2.1. DNS client settings</div><div class="search_word">2.1. dns client settings displays the dns client settings. the table items are explained below. dns client functions displays the settings for whether to enable or disable the dns client function. dns server address displays the dns server address settings used during inquiry for name resolution. default domain displays the default domain settings. search domain displays the search domain settings. displays (dhcp) as a suffix for dns server address and domain obtained by dhcp client function. displays (dhcpv6) as a suffix for dns server address and domain obtained by dhcpv6 client function. press the "setting" button to access a page where you can configure the dns client settings.</div><div class="display_word">2.1. DNS client settings Displays the DNS client settings. The table items are explained below. DNS client functions Displays the settings for whether to enable or disable the DNS client function. DNS server address Displays the DNS server address settings used during inquiry for name resolution. Default domain Displays the default domain settings. Search domain Displays the search domain settings. Displays (DHCP) as a suffix for DNS server address and domain obtained by DHCP client function. Displays (DHCPv6) as a suffix for DNS server address and domain obtained by DHCPv6 client function. Press the "Setting" button to access a page where you can configure the DNS client settings.</div></div><div id="gui_en_detail_dns_client"><div class="search_title" docfname="gui_en_detail_dns_client" doctitle="DNS" link="#client">3. DNS client settings page</div><div class="search_word">3. dns client settings page this page is for configuring the dns client settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. DNS client settings page This page is for configuring the DNS client settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_dns_client"><div class="search_title" docfname="gui_en_detail_dns_client" doctitle="DNS" link="#dns_client_settings_2">3.1. DNS client settings</div><div class="search_word">3.1. dns client settings dns client functions select the operation for the dns client function from the following options. enable disable dns server address specify the dns server address. for the server address, either an ipv4 address or an ipv6 address can be specified. up to three server addresses can be specified. default domain specify the default domain. up to 256 characters can be inputted. search domain specify the search domain. up to 256 characters can be inputted. up to six search domains can be specified.</div><div class="display_word">3.1. DNS client settings DNS client functions Select the operation for the DNS client function from the following options. Enable Disable DNS server address Specify the DNS server address. For the server address, either an IPv4 address or an IPv6 address can be specified. Up to three server addresses can be specified. Default domain Specify the default domain. Up to 256 characters can be inputted. Search domain Specify the search domain. Up to 256 characters can be inputted. Up to six search domains can be specified.</div></div><div id="gui_en_detail_fdb"><div class="search_title" docfname="gui_en_detail_fdb" doctitle="MAC" link="#title-box">MAC address table</div><div class="search_word">mac address table</div><div class="display_word">MAC address table</div></div><div id="gui_en_detail_fdb"><div class="search_title" docfname="gui_en_detail_fdb" doctitle="MAC" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can edit the settings of the mac address table function.</div><div class="display_word">1. Summary In this page you can edit the settings of the MAC address table function.</div></div><div id="gui_en_detail_fdb"><div class="search_title" docfname="gui_en_detail_fdb" doctitle="MAC" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the mac address table.</div><div class="display_word">2. Top page This is the top page for the MAC address table.</div></div><div id="gui_en_detail_fdb"><div class="search_title" docfname="gui_en_detail_fdb" doctitle="MAC" link="#basic_settings_for_mac_address_learning_function">2.1. Basic settings for MAC address learning function</div><div class="search_word">2.1. basic settings for mac address learning function the current settings for the mac address learning function are shown when you press the "setting" button, a page where you can change the mac address learning function settings will appear</div><div class="display_word">2.1. Basic settings for MAC address learning function The current settings for the MAC address learning function are shown When you press the "Setting" button, a page where you can change the MAC address learning function settings will appear</div></div><div id="gui_en_detail_fdb"><div class="search_title" docfname="gui_en_detail_fdb" doctitle="MAC" link="#static_mac_address_table_settings">2.2. Static MAC address table settings</div><div class="search_word">2.2. static mac address table settings the static mac address table is shown as a list a maximum of 20 items can be displayed for one page. press or or enter a numeric value to switch between pages. you can press the sort switch to sort by each item. if you press the "new" button, a page appears in which you can create a new static mac address entry. if you press the "setting" button, a page appears in which you can edit the settings of the selected static mac address entry. if you press the "delete" button, all static mac address entries whose check box has a check mark will be deleted up to 512 static mac address entries can be created from the web gui.</div><div class="display_word">2.2. Static MAC address table settings The static MAC address table is shown as a list A maximum of 20 items can be displayed for one page. Press or or enter a numeric value to switch between pages. You can press the sort switch to sort by each item. If you press the "New" button, a page appears in which you can create a new static MAC address entry. If you press the "Setting" button, a page appears in which you can edit the settings of the selected static MAC address entry. If you press the "Delete" button, all static MAC address entries whose check box has a check mark will be deleted Up to 512 static MAC address entries can be created from the Web GUI.</div></div><div id="gui_en_detail_fdb"><div class="search_title" docfname="gui_en_detail_fdb" doctitle="MAC" link="#fdb_basic">3. MAC address learning function basic settings page</div><div class="search_word">3. mac address learning function basic settings page in this page you can make settings for the mac address learning function. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. MAC address learning function basic settings page In this page you can make settings for the MAC address learning function. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_fdb"><div class="search_title" docfname="gui_en_detail_fdb" doctitle="MAC" link="#basic_settings_for_mac_address_learning_function_2">3.1. Basic settings for MAC address learning function</div><div class="search_word">3.1. basic settings for mac address learning function mac address learning function select the mac address learning function from the following items. use mac address learning function don’t use mac address learning function aging time for dynamic entries specify a setting in the range of 10 seconds to 400 seconds. the default value is 300 seconds</div><div class="display_word">3.1. Basic settings for MAC address learning function MAC address learning function Select the MAC address learning function from the following items. Use MAC address learning function Don’t use MAC address learning function Aging time for dynamic entries Specify a setting in the range of 10 seconds to 400 seconds. The default value is 300 seconds</div></div><div id="gui_en_detail_fdb"><div class="search_title" docfname="gui_en_detail_fdb" doctitle="MAC" link="#fdb_static">4. Static MAC address table settings page</div><div class="search_word">4. static mac address table settings page in this page you can make static mac address settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Static MAC address table settings page In this page you can make static MAC address settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_fdb"><div class="search_title" docfname="gui_en_detail_fdb" doctitle="MAC" link="#static_mac_address_settings">4.1. Static MAC address settings</div><div class="search_word">4.1. static mac address settings kind choose from the following items as the type of mac address to be registered in the static mac address table. register a unicast mac address register a multicast mac address destination mac address enter the mac address in the format hhhh.hhhh.hhhh. frame processing from the following items, select the processing for frames sent to the destination mac address. forward frames that are being sent to the destination mac address discard frames that are being sent to the destination mac address if a multi-cast mac address is registered, "forward" is the only frame processing that can be specified destination vlan id select the forwarding-destination vlan id from those that are registered in the vlan database forwarding destination interface if you press the "select" button, the interfaces assigned to the forwarding-destination vlan id are shown as a list place a check mark in the check box of theinterface that you want to use as the forwarding-destination interface,and press the "ok" button if registering a unicast mac address, you can specify one interface if registering a multicast mac address, you can specify multiple interfaces</div><div class="display_word">4.1. Static MAC address settings Kind Choose from the following items as the type of MAC address to be registered in the static MAC address table. Register a unicast MAC address Register a multicast MAC address Destination MAC address Enter the MAC address in the format hhhh.hhhh.hhhh. Frame processing From the following items, select the processing for frames sent to the destination MAC address. Forward frames that are being sent to the destination MAC address Discard frames that are being sent to the destination MAC address If a multi-cast MAC address is registered, "Forward" is the only frame processing that can be specified Destination VLAN ID Select the forwarding-destination VLAN ID from those that are registered in the VLAN database Forwarding destination interface If you press the "Select" button, the interfaces assigned to the forwarding-destination VLAN ID are shown as a list Place a check mark in the check box of theinterface that you want to use as the forwarding-destination interface,and press the "OK" button If registering a unicast MAC address, you can specify one interface If registering a multicast MAC address, you can specify multiple interfaces</div></div><div id="gui_en_detail_flow"><div class="search_title" docfname="gui_en_detail_flow" doctitle="Flow" link="#title-box">Flow control</div><div class="search_word">flow control</div><div class="display_word">Flow control</div></div><div id="gui_en_detail_flow"><div class="search_title" docfname="gui_en_detail_flow" doctitle="Flow" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring flow control (the ieee 802.3x pause frame transmission and reception).</div><div class="display_word">1. Summary This page is for configuring flow control (the IEEE 802.3x PAUSE frame transmission and reception).</div></div><div id="gui_en_detail_flow"><div class="search_title" docfname="gui_en_detail_flow" doctitle="Flow" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for flow control.</div><div class="display_word">2. Top page This is the top page for flow control.</div></div><div id="gui_en_detail_flow"><div class="search_title" docfname="gui_en_detail_flow" doctitle="Flow" link="#system_settings">2.1. System settings</div><div class="search_word">2.1. system settings displays the current setting whether to useflow control (the ieee 802.3x pause frame transmission and reception)for the entire system. press the "setting" button to display the page for configuring the settings. to enable flow control for the entire system, you need to disable the qos function.</div><div class="display_word">2.1. System settings Displays the current setting whether to useflow control (the IEEE 802.3x PAUSE frame transmission and reception)for the entire system. Press the "Setting" button to display the page for configuring the settings. To enable flow control for the entire system, you need to disable the QoS function.</div></div><div id="gui_en_detail_flow"><div class="search_title" docfname="gui_en_detail_flow" doctitle="Flow" link="#interface_settings">2.2. Interface settings</div><div class="search_word">2.2. interface settings displays flow control settings for each lan/sfp port. press the "setting" button to display the page for configuring the selected interface. press the "return to defaults" button to initialize the settings for all interfaces with the check box selected. press the "specify all" button to configure the settings for all interfaces with the check box selected.</div><div class="display_word">2.2. Interface settings Displays flow control settings for each LAN/SFP port. Press the "Setting" button to display the page for configuring the selected interface. Press the "Return to defaults" button to initialize the settings for all interfaces with the check box selected. Press the "Specify all" button to configure the settings for all interfaces with the check box selected.</div></div><div id="gui_en_detail_flow"><div class="search_title" docfname="gui_en_detail_flow" doctitle="Flow" link="#flow_basic">3. System settings page</div><div class="search_word">3. system settings page this page is for configuring flow control (the ieee 802.3x pause frame transmission and reception) for the entire system. once you have entered the settings, press the "confirm" button. if the input information on the confirm page is correct, press the "ok" button.</div><div class="display_word">3. System settings page This page is for configuring flow control (the IEEE 802.3x PAUSE frame transmission and reception) for the entire system. Once you have entered the settings, press the "Confirm" button. If the input information on the confirm page is correct, press the "OK" button.</div></div><div id="gui_en_detail_flow"><div class="search_title" docfname="gui_en_detail_flow" doctitle="Flow" link="#system_settings_2">3.1. System settings</div><div class="search_word">3.1. system settings flow control for entire system you can specify whether to enable or disable flow control for the entire system. even if flow control for the entire system isenabled, flow control does not work for a port whose individual portsetting is disabled. constraints if flow control is enabled, the tail drop function is disabled. however, this excludes the case wherethe stack function is enabled.</div><div class="display_word">3.1. System settings Flow control for entire system You can specify whether to enable or disable flow control for the entire system. Even if flow control for the entire system isenabled, flow control does not work for a port whose individual portsetting is disabled. Constraints If flow control is enabled, the tail drop function is disabled. However, this excludes the case wherethe stack function is enabled.</div></div><div id="gui_en_detail_flow"><div class="search_title" docfname="gui_en_detail_flow" doctitle="Flow" link="#flow_detail">4. Interface settings page</div><div class="search_word">4. interface settings page this page is for configuring flow control (the ieee 802.3x pause frame transmission and reception) for the interface. once you have entered the settings, press the "confirm" button. if the input information on the confirm page is correct, press the "ok" button.</div><div class="display_word">4. Interface settings page This page is for configuring flow control (the IEEE 802.3x PAUSE frame transmission and reception) for the interface. Once you have entered the settings, press the "Confirm" button. If the input information on the confirm page is correct, press the "OK" button.</div></div><div id="gui_en_detail_flow"><div class="search_title" docfname="gui_en_detail_flow" doctitle="Flow" link="#interface_settings_2">4.1. Interface settings</div><div class="search_word">4.1. interface settings flow control specify whether to enable or disable flow control for lan/sfp ports. if it is enabled, pause frames are sent andreceived regardless of whether the target device supports flow control. auto negotiation use auto negotiation to verify that the target device supports flow control. if the target device does not support flow control, pause frames are not sent or received. constraints in the following cases, only receiving pause frames is supported. if the stack function is enabled in the following cases, auto negotiation does not work even if it is enabled. when an sfp+ module is used</div><div class="display_word">4.1. Interface settings Flow control Specify whether to enable or disable flow control for LAN/SFP ports. If it is enabled, Pause frames are sent andreceived regardless of whether the target device supports flow control. Auto negotiation Use auto negotiation to verify that the target device supports flow control. If the target device does not support flow control, Pause frames are not sent or received. Constraints In the following cases, only receiving Pause frames is supported. If the stack function is enabled In the following cases, auto negotiation does not work even if it is enabled. When an SFP+ module is used</div></div><div id="gui_en_detail_igmp"><div class="search_title" docfname="gui_en_detail_igmp" doctitle="IGMP" link="#title-box">IGMP snooping</div><div class="search_word">igmp snooping</div><div class="display_word">IGMP snooping</div></div><div id="gui_en_detail_igmp"><div class="search_title" docfname="gui_en_detail_igmp" doctitle="IGMP" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can edit the settings of the igmp snooping function.</div><div class="display_word">1. Summary In this page you can edit the settings of the IGMP snooping function.</div></div><div id="gui_en_detail_igmp"><div class="search_title" docfname="gui_en_detail_igmp" doctitle="IGMP" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for igmp snooping.</div><div class="display_word">2. Top page This is the top page for IGMP snooping.</div></div><div id="gui_en_detail_igmp"><div class="search_title" docfname="gui_en_detail_igmp" doctitle="IGMP" link="#igmp_snooping_function_settings">2.1. IGMP snooping function settings</div><div class="search_word">2.1. igmp snooping function settings igmp snooping function settings are shown for each vlan id that is defined a maximum of 20 items can be displayed for one page. press or or enter a numeric value to switch between pages. when you press the "setting" button, a pagewhere you can change the igmp snooping function settings for theselected vlan id will appear if you press the "specify all" button, the settings can be changed for all vlan ids whose check box contains a check mark if you press the "return to defaults" button,the settings will be initialized for all vlan ids whose check boxcontains a check mark default settings for the igmp snooping function are as follows igmp snooping function: disabled igmp version: igmpv3 igmp query: no transmission igmp query transmission interval: 125 seconds ttl check: enabled ra check : disabled tos check : disabled multicast router port : none data transfer suppression function for multicast router ports : disabled report suppression function : enabled report forwarding function : disabled fast leave function : disabled</div><div class="display_word">2.1. IGMP snooping function settings IGMP snooping function settings are shown for each VLAN ID that is defined A maximum of 20 items can be displayed for one page. Press or or enter a numeric value to switch between pages. When you press the "Setting" button, a pagewhere you can change the IGMP snooping function settings for theselected VLAN ID will appear If you press the "Specify all" button, the settings can be changed for all VLAN IDs whose check box contains a check mark If you press the "Return to defaults" button,the settings will be initialized for all VLAN IDs whose check boxcontains a check mark Default settings for the IGMP snooping function are as follows IGMP snooping function: Disabled IGMP version: IGMPv3 IGMP query: No transmission IGMP query transmission interval: 125 seconds TTL check: Enabled RA check : Disabled ToS check : Disabled Multicast router port : None Data transfer suppression function for multicast router ports : Disabled Report suppression function : Enabled Report forwarding function : Disabled Fast leave function : Disabled</div></div><div id="gui_en_detail_igmp"><div class="search_title" docfname="gui_en_detail_igmp" doctitle="IGMP" link="#igmp_config">3. IGMP snooping function settings page</div><div class="search_word">3. igmp snooping function settings page in this page you can make various settings for the igmp snooping function. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. IGMP snooping function settings page In this page you can make various settings for the IGMP snooping function. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_igmp"><div class="search_title" docfname="gui_en_detail_igmp" doctitle="IGMP" link="#igmp_snooping_function_settings_2">3.1. IGMP snooping function settings</div><div class="search_word">3.1. igmp snooping function settings vlan id the vlan id for which settings are being made is shown igmp snooping settings enabled ( control transmission of ip multicast packets ) enable igmp snooping. multicast packets are forwarded only to the port to which the terminal you want to receive them is connected. this function monitors (snoops) igmp messages exchanged between receivingterminals and a multicast router. it can suppress the flooding ofmulticast packets and reduce network bandwidth usage. disabled ( flood ip multicast packets ) disable igmp snooping multicast packets are always forwarded to all ports in the same vlan. version select the igmp version from the following items. igmpv3 igmpv2 igmp query no transmission igmp query transmission function is disabled transmit periodically igmp querytransmission function is enabled. the transmission interval can bespecified in the range of 20 seconds to 18000 seconds ttl check select the ttl check from the following items. enabled ( igmp packets other than ttl=1 are discarded ) disabled ( igmp packets other than ttl=1 are corrected to ttl=1 and transmitted ) ra check select the ra check from the following items. disabled ( ra option is added to igmp packets and transmitted ) enabled ( igmp packets without a ra option are discarded ) tos check select the tos check from the following items. disabled ( tos is corrected to 0xc0 in igmp packets and transmitted ) enabled ( igmp packets with invalid tos are discarded ) multicast router port the multicast router port is the interface to which the multicast router is connected. this device automatically learns the interface that receives the igmp queryas the multicast router port. also, you can statically configure themulticast router port. to statically configure multicast routerports, press the "select" button. the interfaces that belong to thespecified vlan id are listed. then, check the check box of the interface to use as the multicast router port, and press the "confirm" button. data transfer suppression function for multicast router ports this function suppresses network traffic load by stopping unnecessary multicast frames transfer to the multicast router port. select from the following items. disable disabling this function causesmulticast frames to be transferred to the multicast router port as wellif any port is receiving igmp report messages. enable enabling this function causesmulticast frames to be transferred to the multicast router port as wellonly when the multicast router port receives igmp report messages. report suppression function this function suppresses the network traffic load between the multicast router and the host. select from the following items. enable enabling this function transfers received igmp report and leave messages to the igmp querier at once. disable disabling this function transfers received igmp report and leave messages to the igmp querier as is without combining them. report forwarding function this function transfers igmp report and leave messages to the port where a switch is connected in the same vlan. the system capabilities informationincluded in the lldp basic management tlv is used to judge whether aswitch is connected to the port or not. select from the following items. enable enabling this function transfersreceived igmp report and leave messages to the multicast router portsand the ports where a switch is connected. disable disabling this function transfers received igmp report and leave messages to the multicast router ports only. fast leave function fast leave function is a function not to check the receiver’s existence in the igmp leave process. this function is effective when only one receiver is connected to the lan/sfp port. select from the following items. disable disable the fast leave function. the igmp leave process sends a group-specific query to check the receivers' existence. enable enable the fast leave function. the igmp leave process does not check the receiver’s existence. if you check the "disable on ports where a switch is conneced" check box, the fast leave function will not be used on ports where the switch is connected.</div><div class="display_word">3.1. IGMP snooping function settings VLAN ID The VLAN ID for which settings are being made is shown IGMP snooping settings Enabled ( Control transmission of IP multicast packets ) Enable IGMP snooping. Multicast packets are forwarded only to the port to which the terminal you want to receive them is connected. This function monitors (snoops) IGMP messages exchanged between receivingterminals and a multicast router. It can suppress the flooding ofmulticast packets and reduce network bandwidth usage. Disabled ( Flood IP multicast packets ) Disable IGMP snooping Multicast packets are always forwarded to all ports in the same VLAN. Version Select the IGMP version from the following items. IGMPv3 IGMPv2 IGMP query No transmission IGMP query transmission function is disabled Transmit periodically IGMP querytransmission function is enabled. The transmission interval can bespecified in the range of 20 seconds to 18000 seconds TTL check Select the TTL check from the following items. Enabled ( IGMP packets other than TTL=1 are discarded ) Disabled ( IGMP packets other than TTL=1 are corrected to TTL=1 and transmitted ) RA check Select the RA check from the following items. Disabled ( RA option is added to IGMP packets and transmitted ) Enabled ( IGMP packets without a RA option are discarded ) ToS check Select the ToS check from the following items. Disabled ( ToS is corrected to 0xc0 in IGMP packets and transmitted ) Enabled ( IGMP packets with invalid ToS are discarded ) Multicast router port The multicast router port is the interface to which the multicast router is connected. This device automatically learns the interface that receives the IGMP queryas the multicast router port. Also, you can statically configure themulticast router port. To statically configure multicast routerports, press the "Select" button. The interfaces that belong to thespecified VLAN ID are listed. Then, check the check box of the interface to use as the multicast router port, and press the "Confirm" button. Data transfer suppression function for multicast router ports This function suppresses network traffic load by stopping unnecessary multicast frames transfer to the multicast router port. Select from the following items. Disable Disabling this function causesmulticast frames to be transferred to the multicast router port as wellif any port is receiving IGMP report messages. Enable Enabling this function causesmulticast frames to be transferred to the multicast router port as wellonly when the multicast router port receives IGMP report messages. Report suppression function This function suppresses the network traffic load between the multicast router and the host. Select from the following items. Enable Enabling this function transfers received IGMP report and leave messages to the IGMP querier at once. Disable Disabling this function transfers received IGMP report and leave messages to the IGMP querier as is without combining them. Report forwarding function This function transfers IGMP report and leave messages to the port where a switch is connected in the same VLAN. The System Capabilities informationincluded in the LLDP Basic Management TLV is used to judge whether aswitch is connected to the port or not. Select from the following items. Enable Enabling this function transfersreceived IGMP report and leave messages to the multicast router portsand the ports where a switch is connected. Disable Disabling this function transfers received IGMP report and leave messages to the multicast router ports only. Fast leave function Fast leave function is a function not to check the receiver’s existence in the IGMP leave process. This function is effective when only one receiver is connected to the LAN/SFP port. Select from the following items. Disable Disable the fast leave function. The IGMP leave process sends a group-specific query to check the receivers' existence. Enable Enable the fast leave function. The IGMP leave process does not check the receiver’s existence. If you check the "Disable on ports where a switch is conneced" check box, the fast leave function will not be used on ports where the switch is connected.</div></div><div id="gui_en_detail_interface"><div class="search_title" docfname="gui_en_detail_interface" doctitle="Physical" link="#title-box">Physical interface</div><div class="search_word">physical interface</div><div class="display_word">Physical interface</div></div><div id="gui_en_detail_interface"><div class="search_title" docfname="gui_en_detail_interface" doctitle="Physical" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for changing the physical interface settings.</div><div class="display_word">1. Summary This page is for changing the physical interface settings.</div></div><div id="gui_en_detail_interface"><div class="search_title" docfname="gui_en_detail_interface" doctitle="Physical" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the physical interface.</div><div class="display_word">2. Top page This is the top page for the physical interface.</div></div><div id="gui_en_detail_interface"><div class="search_title" docfname="gui_en_detail_interface" doctitle="Physical" link="#interface_list">2.1. Interface list</div><div class="search_word">2.1. interface list the current operating status and settings for the physical interface are shown for each interface. the table items are explained below. check box select the check box for bulk settings or to initialize the settings. port displays the interface name. link displays the link status for the interface. displays the port type in parentheses for other ports besides the lan. speed settings displays the speed and communication mode settings. eee displays the operating status of the eee function. description displays the description text that is set for the interface. press the "setting" button to display the page where you can change the settings of the selected interface. if you press the "specify all" button, the settings can be changed for all interfaces whose check box is selected. bulk settings cannot be made by selecting ports of different types. the default settings will be applied to the settings on the physical interface settings page. if you press the "return to defaults" button, the settings will be initialized on all interfaces whose check boxes are selected. each of the default settings are shown below. operation : enable interface description : unset speed/communication mode : automatic mru : 1522 byte eee function : disabled (don’t use power-conservation ethernet function) automatic cross/straight detection : enable</div><div class="display_word">2.1. Interface list The current operating status and settings for the physical interface are shown for each interface. The table items are explained below. Check box Select the check box for bulk settings or to initialize the settings. Port Displays the interface name. Link Displays the link status for the interface. Displays the port type in parentheses for other ports besides the LAN. Speed settings Displays the speed and communication mode settings. EEE Displays the operating status of the EEE function. Description Displays the description text that is set for the interface. Press the "Setting" button to display the page where you can change the settings of the selected interface. If you press the "Specify all" button, the settings can be changed for all interfaces whose check box is selected. Bulk settings cannot be made by selecting ports of different types. The default settings will be applied to the settings on the physical interface settings page. If you press the "Return to defaults" button, the settings will be initialized on all interfaces whose check boxes are selected. Each of the default settings are shown below. Operation : Enable interface Description : Unset Speed/communication mode : Automatic MRU : 1522 Byte EEE function : Disabled (Don’t use power-conservation Ethernet function) Automatic cross/straight detection : Enable</div></div><div id="gui_en_detail_interface"><div class="search_title" docfname="gui_en_detail_interface" doctitle="Physical" link="#if_config">3. Physical interface settings page</div><div class="search_word">3. physical interface settings page this page is for changing physical interface-related settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Physical interface settings page This page is for changing physical interface-related settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_interface"><div class="search_title" docfname="gui_en_detail_interface" doctitle="Physical" link="#physical_interface_settings">3.1. Physical interface settings</div><div class="search_word">3.1. physical interface settings port displays the name of the interface for which settings will be made. operation select from the following interface operations. enable interface disable interface description sets the interface description text. characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . up to 80 characters can be inputted. speed/communication mode select the interface speed and communication method from the following options. for a lan port automatic 1gbps / full duplex 100mbps / full duplex 100mbps / half duplex 10mbps / full duplex 10mbps / half duplex for an sfp port or combo port automatic 1gbps / full duplex for an sfp+ port automatic 10gbps / full duplex mru specify the maximum amount of data that can be received at one time. the input range is 64 - 10240 bytes. eee function eee functions can only be set for the lan port and combo port. select the operation for the eee function from the following options. disable (don’t use power-conservation ethernet function) enable (use power-conservation ethernet function) automatic cross/straight detection select the operation for the automatic cross/straight detection from the following options. enable disable if the automatic cross/straight detection is disabled, mdi is used for the cable connection type.</div><div class="display_word">3.1. Physical interface settings Port Displays the name of the interface for which settings will be made. Operation Select from the following interface operations. Enable interface Disable interface Description Sets the interface description text. Characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . Up to 80 characters can be inputted. Speed/communication mode Select the interface speed and communication method from the following options. For a LAN port Automatic 1Gbps / Full duplex 100Mbps / Full duplex 100Mbps / Half duplex 10Mbps / Full duplex 10Mbps / Half duplex For an SFP port or combo port Automatic 1Gbps / Full duplex For an SFP+ port Automatic 10Gbps / Full duplex MRU Specify the maximum amount of data that can be received at one time. The input range is 64 - 10240 bytes. EEE function EEE functions can only be set for the LAN port and combo port. Select the operation for the EEE function from the following options. Disable (Don’t use power-conservation Ethernet function) Enable (Use power-conservation Ethernet function) Automatic cross/straight detection Select the operation for the automatic cross/straight detection from the following options. Enable Disable If the automatic cross/straight detection is disabled, MDI is used for the cable connection type.</div></div><div id="gui_en_detail_l2msfilter"><div class="search_title" docfname="gui_en_detail_l2msfilter" doctitle="L2MS" link="#title-box">L2MS filter</div><div class="search_word">l2ms filter</div><div class="display_word">L2MS filter</div></div><div id="gui_en_detail_l2msfilter"><div class="search_title" docfname="gui_en_detail_l2msfilter" doctitle="L2MS" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring l2ms filter settings. if you enable l2ms filter, you can block l2ms frames.</div><div class="display_word">1. Summary This page is for configuring L2MS filter settings. If you enable L2MS filter, you can block L2MS frames.</div></div><div id="gui_en_detail_l2msfilter"><div class="search_title" docfname="gui_en_detail_l2msfilter" doctitle="L2MS" link="#section2">2. Top page</div><div class="search_word">2. top page displays a list of l2ms filter settings for interfaces.</div><div class="display_word">2. Top page Displays a list of L2MS filter settings for interfaces.</div></div><div id="gui_en_detail_l2msfilter"><div class="search_title" docfname="gui_en_detail_l2msfilter" doctitle="L2MS" link="#interface_list">2.1. Interface list</div><div class="search_word">2.1. interface list displays the current l2ms filter settings for each interface. press the "setting" button to display the page for configuring the selected interface. press the "specify all" button to configure the settings for all interfaces with the check box selected. press the "return to defaults" button to initialize the settings for all interfaces with the check box selected. the default setting of l2ms filter is "disabled". constraints if the l2ms operation mode is disabled, l2ms filter does not work. l2ms frames are forwarded.</div><div class="display_word">2.1. Interface list Displays the current L2MS filter settings for each interface. Press the "Setting" button to display the page for configuring the selected interface. Press the "Specify all" button to configure the settings for all interfaces with the check box selected. Press the "Return to defaults" button to initialize the settings for all interfaces with the check box selected. The default setting of L2MS filter is "Disabled". Constraints If the L2MS operation mode is disabled, L2MS filter does not work. L2MS frames are forwarded.</div></div><div id="gui_en_detail_l2msfilter"><div class="search_title" docfname="gui_en_detail_l2msfilter" doctitle="L2MS" link="#if_config">3. Interface settings</div><div class="search_word">3. interface settings this page is for configuring l2ms filter for the interface. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Interface settings This page is for configuring L2MS filter for the interface. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_l2msfilter"><div class="search_title" docfname="gui_en_detail_l2msfilter" doctitle="L2MS" link="#interface_settings">3.1. Interface settings</div><div class="search_word">3.1. interface settings l2ms filter specify whether to enable or disable l2ms filter for the target interface. if it is enabled, the filter blocks l2ms frames. if it is disabled, the filter does not block l2ms frames.</div><div class="display_word">3.1. Interface settings L2MS filter Specify whether to enable or disable L2MS filter for the target interface. If it is enabled, the filter blocks L2MS frames. If it is disabled, the filter does not block L2MS frames.</div></div><div id="gui_en_detail_lag"><div class="search_title" docfname="gui_en_detail_lag" doctitle="Link" link="#title-box">Link aggregation</div><div class="search_word">link aggregation</div><div class="display_word">Link aggregation</div></div><div id="gui_en_detail_lag"><div class="search_title" docfname="gui_en_detail_lag" doctitle="Link" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring the link aggregation settings.</div><div class="display_word">1. Summary This page is for configuring the link aggregation settings.</div></div><div id="gui_en_detail_lag"><div class="search_title" docfname="gui_en_detail_lag" doctitle="Link" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for link aggregation.</div><div class="display_word">2. Top page This is the top page for link aggregation.</div></div><div id="gui_en_detail_lag"><div class="search_title" docfname="gui_en_detail_lag" doctitle="Link" link="#system_settings">2.1. System settings</div><div class="search_word">2.1. system settings shows the system settings related to link aggregation. the table items are explained below. lacp system priority displays the lacp priority set in this system. mixed-speed mode displays whether the lacp mixed-speed mode is enabled or not. load balance rules displays the load balance settings. press the "settings" button to show the page for system settings related to link aggregation.</div><div class="display_word">2.1. System settings Shows the system settings related to link aggregation. The table items are explained below. LACP system priority Displays the LACP priority set in this system. Mixed-speed mode Displays whether the LACP mixed-speed mode is enabled or not. Load balance rules Displays the load balance settings. Press the "Settings" button to show the page for system settings related to link aggregation.</div></div><div id="gui_en_detail_lag"><div class="search_title" docfname="gui_en_detail_lag" doctitle="Link" link="#interface_list">2.2. Interface list</div><div class="search_word">2.2. interface list the operating status and settings are shown for the logical interface and the physical interface. the table items are explained below. check box select the check box to delete the logical interface. port displays the interface name. link displays the link status for the interface. lacp status one of the following statuses are displayed for the lacp status of the interface. waiting negotiating communication ok - lacp priority during actual operation, the priority will be displayed. displays a value from 1 to 12 for the priority, calculated based on the lacp priority setting. description displays the description text that is set for the interface. press the "new" button to display a page where you can create new settings for a logical interface. press the "setting" button to display the page where you can change the settings of the selected logical interface. if you press the "delete" button, all logical interfaces whose check boxes are selected will be deleted. when deleting a logical interface, you can specify the physical interface operations after deletion as follows. enable disable up to 127 logical interfaces can be configured. up to 96 static logical interfaces can be configured.</div><div class="display_word">2.2. Interface list The operating status and settings are shown for the logical interface and the physical interface. The table items are explained below. Check box Select the check box to delete the logical interface. Port Displays the interface name. Link Displays the link status for the interface. LACP status One of the following statuses are displayed for the LACP status of the interface. Waiting Negotiating Communication OK - LACP priority During actual operation, the priority will be displayed. Displays a value from 1 to 12 for the priority, calculated based on the LACP priority setting. Description Displays the description text that is set for the interface. Press the "New" button to display a page where you can create new settings for a logical interface. Press the "Setting" button to display the page where you can change the settings of the selected logical interface. If you press the "Delete" button, all logical interfaces whose check boxes are selected will be deleted. When deleting a logical interface, you can specify the physical interface operations after deletion as follows. Enable Disable Up to 127 logical interfaces can be configured. Up to 96 static logical interfaces can be configured.</div></div><div id="gui_en_detail_lag"><div class="search_title" docfname="gui_en_detail_lag" doctitle="Link" link="#system">3. System settings page</div><div class="search_word">3. system settings page this page is for configuring link aggregation-related system settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. System settings page This page is for configuring link aggregation-related system settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_lag"><div class="search_title" docfname="gui_en_detail_lag" doctitle="Link" link="#system_settings_2">3.1. System settings</div><div class="search_word">3.1. system settings lacp system priority specify the lacp system priority. lacp mixed-speed mode select whether to enable the lacp mixed-speed mode from the following. disable when this function is disabled,physical interfaces with different communication speeds belonging to the lacp logical interface cannot communicate at the same time. enable when this function is enabled,physical interfaces with different communication speeds belonging to the lacp logical interface can communicate at the same time. enable this function when you want to aggregate physical interfaces with different communication speedsinto an lacp logical interface. load balance rules the following load balance rules can be selected. destination mac address source mac address destination/source mac address destination ip address source ip address destination/source ip address destination port number source port number destination/source port numbers</div><div class="display_word">3.1. System settings LACP system priority Specify the LACP system priority. LACP mixed-speed mode Select whether to enable the LACP mixed-speed mode from the following. Disable When this function is disabled,physical interfaces with different communication speeds belonging to the LACP logical interface cannot communicate at the same time. Enable When this function is enabled,physical interfaces with different communication speeds belonging to the LACP logical interface can communicate at the same time. Enable this function when you want to aggregate physical interfaces with different communication speedsinto an LACP logical interface. Load balance rules The following load balance rules can be selected. Destination MAC address Source MAC address Destination/source MAC address Destination IP address Source IP address Destination/source IP address Destination port number Source port number Destination/source port numbers</div></div><div id="gui_en_detail_lag"><div class="search_title" docfname="gui_en_detail_lag" doctitle="Link" link="#logical">4. Logical interface settings page</div><div class="search_word">4. logical interface settings page this page is for changing the logical interface settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Logical interface settings page This page is for changing the logical interface settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_lag"><div class="search_title" docfname="gui_en_detail_lag" doctitle="Link" link="#logical_interface_settings">4.1. Logical interface settings</div><div class="search_word">4.1. logical interface settings logical interface when configuring new settings the logical interface type can be selected from the following types. static logical interface lacp logical interface when changing settings displays the selected logical interface name. interface number specifies the interface number. a value from 1 to 96 can be inputted for a static logical interface. a value from 1 to 127 can be inputted for an lacp logical interface. this item will be displayed only when configuring new settings. associated port select the port that will be associated with the logical interface. press the "select" button to display the "physical interface list" dialog box. select the port check box in the "physical interface list" dialog box and press the "ok" button to select the associated port. up to eight ports can be selected for astatic logical interface, and up to 12 ports can be selected for an lacp logical interface. when displaying the dialog box for the"logical interface" item with the lacp logical interface selected, thefollowing settings can be made for each associated port. operation mode active passive lacp priority 1 - 12 lacp timeout 3 seconds 90 seconds operation select from the following logical interface operations. enable interface disable interface description sets the interface description text. characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . up to 80 characters can be inputted.</div><div class="display_word">4.1. Logical interface settings Logical interface When configuring new settings The logical interface type can be selected from the following types. Static logical interface LACP logical interface When changing settings Displays the selected logical interface name. Interface number Specifies the interface number. A value from 1 to 96 can be inputted for a static logical interface. A value from 1 to 127 can be inputted for an LACP logical interface. This item will be displayed only when configuring new settings. Associated port Select the port that will be associated with the logical interface. Press the "Select" button to display the "Physical interface list" dialog box. Select the port check box in the "Physical interface list" dialog box and press the "OK" button to select the associated port. Up to eight ports can be selected for astatic logical interface, and up to 12 ports can be selected for an LACP logical interface. When displaying the dialog box for the"Logical interface" item with the LACP logical interface selected, thefollowing settings can be made for each associated port. Operation mode Active Passive LACP priority 1 - 12 LACP timeout 3 Seconds 90 Seconds Operation Select from the following logical interface operations. Enable interface Disable interface Description Sets the interface description text. Characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . Up to 80 characters can be inputted.</div></div><div id="gui_en_detail_loopdetect"><div class="search_title" docfname="gui_en_detail_loopdetect" doctitle="Loop" link="#title-box">Loop detection</div><div class="search_word">loop detection</div><div class="display_word">Loop detection</div></div><div id="gui_en_detail_loopdetect"><div class="search_title" docfname="gui_en_detail_loopdetect" doctitle="Loop" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring the settings for loop detection. this function monitors whether a loop is occurring bysending its loop detection frame from the port and whether the framereturns to itself or not.</div><div class="display_word">1. Summary This page is for configuring the settings for loop detection. This function monitors whether a loop is occurring bysending its loop detection frame from the port and whether the framereturns to itself or not.</div></div><div id="gui_en_detail_loopdetect"><div class="search_title" docfname="gui_en_detail_loopdetect" doctitle="Loop" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the loop detection.</div><div class="display_word">2. Top page This is the top page for the loop detection.</div></div><div id="gui_en_detail_loopdetect"><div class="search_title" docfname="gui_en_detail_loopdetect" doctitle="Loop" link="#system_settings">2.1. System settings</div><div class="search_word">2.1. system settings displays the system settings of loop detection. the table items are explained below. displays the loop detection settings for the entire system. displays the setting for whether to disable port blocking immediately or periodically after the loop is resolved. displays the setting for automatic recovery from shutdown (errdisable state). press the "setting" button to display the page for configuring the loop detection settings for the entire system. resetting the loop detection status you can immediately resolve the loop detection states (e.g., shutdown) by reset feature.</div><div class="display_word">2.1. System settings Displays the system settings of loop detection. The table items are explained below. Displays the loop detection settings for the entire system. Displays the setting for whether to disable Port Blocking immediately or periodically after the loop is resolved. Displays the setting for automatic recovery from Shutdown (errdisable state). Press the "Setting" button to display the page for configuring the loop detection settings for the entire system. Resetting the loop detection status You can immediately resolve the loop detection states (e.g., Shutdown) by reset feature.</div></div><div id="gui_en_detail_loopdetect"><div class="search_title" docfname="gui_en_detail_loopdetect" doctitle="Loop" link="#interface_settings">2.2. Interface settings</div><div class="search_word">2.2. interface settings displays the settings and operating status of loop detection for each interface. the table items are explained below. check box select the check box for bulk settings or to initialize the settings. port displays the interface name. loop detection displays the settings of loop detection for the interface. port blocking displays the settings of port blocking function. if it is enabled, the function blocks frames when a loop is detected. status displays the operating status of loop detection. operating the loop detection function is operating. detected loop has been detected. communication is continued. blocking blocking the frames. (restart the communication in 5 seconds after the loop has been resolved) shutdown shutting down the port. (restart the communication in 5 minutes after shutting down the port) stopped the loop detection function is stopped. normally, the state becomes "stopped" when the loop detection setting is disabled. if it is stopped by other factors, the following factors are indicated in parentheses. mirror port if it is a port with mirroring settings (mirror port) stp you can use theloop detection function with spanning tree. however, the function worksonly when the spanning tree status of the corresponding port is"forwarding". press the "setting" button to display the page for configuring the selected interface settings. press the "specify all" button to configure the settings for all interfaces with the check box selected. press the "return to defaults" button to initialize the settings for all interfaces with the check box selected. each of the default settings are shown below. loop detection: enabled port blocking: enabled (block frames when a loop is detected) press the "update" button to update the table of interface settings.</div><div class="display_word">2.2. Interface settings Displays the settings and operating status of loop detection for each interface. The table items are explained below. Check box Select the check box for bulk settings or to initialize the settings. Port Displays the interface name. Loop detection Displays the settings of loop detection for the interface. Port Blocking Displays the settings of Port Blocking function. If it is enabled, the function blocks frames when a loop is detected. Status Displays the operating status of loop detection. Operating The loop detection function is operating. Detected Loop has been detected. Communication is continued. Blocking Blocking the frames. (Restart the communication in 5 seconds after the loop has been resolved) Shutdown Shutting down the port. (Restart the communication in 5 minutes after shutting down the port) Stopped The loop detection function is stopped. Normally, the state becomes "Stopped" when the loop detection setting is disabled. If it is stopped by other factors, the following factors are indicated in parentheses. Mirror port If it is a port with mirroring settings (mirror port) STP You can use theloop detection function with spanning tree. However, the function worksonly when the spanning tree status of the corresponding port is"Forwarding". Press the "Setting" button to display the page for configuring the selected interface settings. Press the "Specify all" button to configure the settings for all interfaces with the check box selected. Press the "Return to defaults" button to initialize the settings for all interfaces with the check box selected. Each of the default settings are shown below. Loop detection: Enabled Port Blocking: Enabled (Block frames when a loop is detected) Press the "Update" button to update the table of interface settings.</div></div><div id="gui_en_detail_loopdetect"><div class="search_title" docfname="gui_en_detail_loopdetect" doctitle="Loop" link="#system">3. System settings page</div><div class="search_word">3. system settings page this page is for configuring the interface settings for loop detection. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. System settings page This page is for configuring the interface settings for loop detection. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_loopdetect"><div class="search_title" docfname="gui_en_detail_loopdetect" doctitle="Loop" link="#system_settings_2">3.1. System settings</div><div class="search_word">3.1. system settings specify whether to enable or disable the loop detection function for the entire system. even if set to enable, the loop detection function for an individual port does not work if the port’s setting is disabled. if this function is used with a spanning tree, the spanning tree takes precedence.</div><div class="display_word">3.1. System settings Specify whether to enable or disable the loop detection function for the entire system. Even if set to enable, the loop detection function for an individual port does not work if the port’s setting is disabled. If this function is used with a spanning tree, the spanning tree takes precedence.</div></div><div id="gui_en_detail_loopdetect"><div class="search_title" docfname="gui_en_detail_loopdetect" doctitle="Loop" link="#interface">4. Interface settings page</div><div class="search_word">4. interface settings page this page is for configuring the interface settings for loop detection. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Interface settings page This page is for configuring the interface settings for loop detection. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_loopdetect"><div class="search_title" docfname="gui_en_detail_loopdetect" doctitle="Loop" link="#interface_settings_2">4.1. Interface settings</div><div class="search_word">4.1. interface settings loop detection specify whether to enable or disable the loop detection function for the target interface. however, even if set to enable, the loop detection function does not work in the following cases. (1) the loop detection function for the entire system is disabled. (2) the target interface is a port with mirroring settings. (mirror port) (3) used with spanning tree, and spanning tree status of the target interface is not "forwarding". port blocking specify whether to enable or disable the port blocking function for the target interface. if set to enable, the function blocks frames when a loop is detected.</div><div class="display_word">4.1. Interface settings Loop detection Specify whether to enable or disable the loop detection function for the target interface. However, even if set to enable, the loop detection function does not work in the following cases. (1) The loop detection function for the entire system is disabled. (2) The target interface is a port with mirroring settings. (mirror port) (3) Used with spanning tree, and spanning tree status of the target interface is not "Forwarding". Port Blocking Specify whether to enable or disable the Port Blocking function for the target interface. If set to enable, the function blocks frames when a loop is detected.</div></div><div id="gui_en_detail_mirror"><div class="search_title" docfname="gui_en_detail_mirror" doctitle="Port" link="#title-box">Port mirroring settings</div><div class="search_word">port mirroring settings</div><div class="display_word">Port mirroring settings</div></div><div id="gui_en_detail_mirror"><div class="search_title" docfname="gui_en_detail_mirror" doctitle="Port" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for changing the port mirroring settings.</div><div class="display_word">1. Summary This page is for changing the port mirroring settings.</div></div><div id="gui_en_detail_mirror"><div class="search_title" docfname="gui_en_detail_mirror" doctitle="Port" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the port mirroring settings.</div><div class="display_word">2. Top page This is the top page for the port mirroring settings.</div></div><div id="gui_en_detail_mirror"><div class="search_title" docfname="gui_en_detail_mirror" doctitle="Port" link="#port_mirroring_settings">2.1. Port mirroring settings</div><div class="search_word">2.1. port mirroring settings the current settings for the port mirroring are shown. the table items are explained below. check box select the check box to delete the sniffer port setting. sniffer port displays the interface name of a sniffer port. monitored port displays the interface name of monitored ports. monitoring direction displays the monitoring direction for a monitored port. press the "new" button to display a page where you can create new settings for a sniffer port. press the "setting" button to display the page where you can change the settings of a sniffer port. if you press the "delete" button, all sniffer ports whose check boxes are selected will be deleted. up to 1 sniffer port can be configured.</div><div class="display_word">2.1. Port mirroring settings The current settings for the port mirroring are shown. The table items are explained below. Check box Select the check box to delete the sniffer port setting. Sniffer port Displays the interface name of a sniffer port. Monitored port Displays the interface name of monitored ports. Monitoring direction Displays the monitoring direction for a monitored port. Press the "New" button to display a page where you can create new settings for a sniffer port. Press the "Setting" button to display the page where you can change the settings of a sniffer port. If you press the "Delete" button, all sniffer ports whose check boxes are selected will be deleted. Up to 1 sniffer port can be configured.</div></div><div id="gui_en_detail_mirror"><div class="search_title" docfname="gui_en_detail_mirror" doctitle="Port" link="#mirror">3. Port mirroring settings page</div><div class="search_word">3. port mirroring settings page this page is for changing the port mirroring settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Port mirroring settings page This page is for changing the port mirroring settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_mirror"><div class="search_title" docfname="gui_en_detail_mirror" doctitle="Port" link="#port_mirroring_settings_2">3.1. Port mirroring settings</div><div class="search_word">3.1. port mirroring settings sniffer port when configuring new settings this page is for changing the port mirroring settings. select the interface to operate as a sniffer port. press the "select" button to display the "sniffer port selection" dialog. when changing settings you can select a sniffer port bychecking the port check box and clicking the "ok" button in the "sniffer port selection" dialog. monitored port select the ports that will be monitored from a selected sniffer port. press the "select" button to display the "monitored port selection" dialog. monitored ports can be selected in the"monitored port selection" dialog by placing a checkmark in thecorresponding checkbox, selecting the monitoring direction, and pressing the "ok" button.</div><div class="display_word">3.1. Port mirroring settings Sniffer port When configuring new settings This page is for changing the port mirroring settings. Select the interface to operate as a sniffer port. Press the "Select" button to display the "Sniffer port selection" dialog. When changing settings You can select a sniffer port bychecking the port check box and clicking the "OK" button in the "Sniffer port selection" dialog. Monitored port Select the ports that will be monitored from a selected sniffer port. Press the "Select" button to display the "Monitored port selection" dialog. Monitored ports can be selected in the"Monitored port selection" dialog by placing a checkmark in thecorresponding checkbox, selecting the monitoring direction, and pressing the "OK" button.</div></div><div id="gui_en_detail_mld"><div class="search_title" docfname="gui_en_detail_mld" doctitle="MLD" link="#title-box">MLD snooping</div><div class="search_word">mld snooping</div><div class="display_word">MLD snooping</div></div><div id="gui_en_detail_mld"><div class="search_title" docfname="gui_en_detail_mld" doctitle="MLD" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can edit the settings of the mld snooping.</div><div class="display_word">1. Summary In this page you can edit the settings of the MLD snooping.</div></div><div id="gui_en_detail_mld"><div class="search_title" docfname="gui_en_detail_mld" doctitle="MLD" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for mld snooping.</div><div class="display_word">2. Top page This is the top page for MLD snooping.</div></div><div id="gui_en_detail_mld"><div class="search_title" docfname="gui_en_detail_mld" doctitle="MLD" link="#mld_snooping_settings">2.1. MLD snooping settings</div><div class="search_word">2.1. mld snooping settings mld snooping settings are shown for each vlan id that is defined. a maximum of 20 items can be displayed for one page. press or or enter a numeric value to switch between pages. when you press the "setting" button, a page where you can change the mld snooping settings for the selected vlan id will appear. if you press the "specify all" button, the settings can be changed for all vlan ids whose check box contains a check mark. if you press the "return to defaults" button,the settings will be initialized for all vlan ids whose check boxcontains a check mark. default settings for the mld snooping are as follows. mld snooping : disabled version : mldv2 mld query : no transmission mld query transmission interval : 125 seconds multicast router port : none report suppression function : enabled fast leave function : disabled you cannot configure mld snooping when the stack function is enabled.</div><div class="display_word">2.1. MLD snooping settings MLD snooping settings are shown for each VLAN ID that is defined. A maximum of 20 items can be displayed for one page. Press or or enter a numeric value to switch between pages. When you press the "Setting" button, a page where you can change the MLD snooping settings for the selected VLAN ID will appear. If you press the "Specify all" button, the settings can be changed for all VLAN IDs whose check box contains a check mark. If you press the "Return to defaults" button,the settings will be initialized for all VLAN IDs whose check boxcontains a check mark. Default settings for the MLD snooping are as follows. MLD snooping : Disabled Version : MLDv2 MLD query : No transmission MLD query transmission interval : 125 Seconds Multicast router port : None Report suppression function : Enabled Fast leave function : Disabled You cannot configure MLD snooping when the stack function is enabled.</div></div><div id="gui_en_detail_mld"><div class="search_title" docfname="gui_en_detail_mld" doctitle="MLD" link="#mld_config">3. MLD snooping settings page</div><div class="search_word">3. mld snooping settings page in this page you can make various settings for the mld snooping. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. MLD snooping settings page In this page you can make various settings for the MLD snooping. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_mld"><div class="search_title" docfname="gui_en_detail_mld" doctitle="MLD" link="#mld_snooping_settings_2">3.1. MLD snooping settings</div><div class="search_word">3.1. mld snooping settings vlan id the vlan id for which settings are being made is shown. mld snooping enabled ( control transmission of ipv6 multicast packets ) enable mld snooping multicast packets are forwarded only to the port to which the terminal you want to receive them is connected. this function monitors (snoops) mld messages exchanged between receivingterminals and a multicast router. it can suppress the flooding ofmulticast packets and reduce network bandwidth usage. disabled ( flood ipv6 multicast packets ) disables the mld snooping multicast packets are always forwarded to all ports in the same vlan. version select the mld version from the following items. mldv1 mldv2 mld query no transmission mld query transmission function is disabled. transmit periodically mld querytransmission function is enabled. the transmission interval can bespecified in the range of 20 seconds to 18000 seconds. multicast router port the multicast router port is the interface used to connect multicast routers. this device automatically learns the interface that receives the mld queryas the multicast router port. also, you can statically configure themulticast router port. to statically configure multicast routerports, press the "select" button. the interfaces that belong to thespecified vlan id are listed. then, check the check box of the interface to use as the multicast router port, and press the "confirm" button. report suppression function this function suppresses the network traffic load between the multicast router and the host. select from the following items. enable enabling this function transfers received mld report and leave messages to the mld querier at once. disable disabling this function transfers received mld report and leave messages to the mld querier as is without combining them. fast leave function fast leave function is a function not to check the receiver’s existence in the mld leave process. this function is effective when only one receiver is connected to the lan/sfp port. select from the following items. disable disable the fast leave function. the mld leave process sends a group-specific query to check the receivers' existence. enable enable the fast leave function. the mld leave process does not check the receiver’s existence.</div><div class="display_word">3.1. MLD snooping settings VLAN ID The VLAN ID for which settings are being made is shown. MLD snooping Enabled ( Control transmission of IPv6 multicast packets ) Enable MLD snooping Multicast packets are forwarded only to the port to which the terminal you want to receive them is connected. This function monitors (snoops) MLD messages exchanged between receivingterminals and a multicast router. It can suppress the flooding ofmulticast packets and reduce network bandwidth usage. Disabled ( Flood IPv6 multicast packets ) Disables the MLD snooping Multicast packets are always forwarded to all ports in the same VLAN. Version Select the MLD version from the following items. MLDv1 MLDv2 MLD query No transmission MLD query transmission function is disabled. Transmit periodically MLD querytransmission function is enabled. The transmission interval can bespecified in the range of 20 seconds to 18000 seconds. Multicast router port The multicast router port is the interface used to connect multicast routers. This device automatically learns the interface that receives the MLD queryas the multicast router port. Also, you can statically configure themulticast router port. To statically configure multicast routerports, press the "Select" button. The interfaces that belong to thespecified VLAN ID are listed. Then, check the check box of the interface to use as the multicast router port, and press the "Confirm" button. Report suppression function This function suppresses the network traffic load between the multicast router and the host. Select from the following items. Enable Enabling this function transfers received MLD report and leave messages to the MLD querier at once. Disable Disabling this function transfers received MLD report and leave messages to the MLD querier as is without combining them. Fast leave function Fast leave function is a function not to check the receiver’s existence in the MLD leave process. This function is effective when only one receiver is connected to the LAN/SFP port. Select from the following items. Disable Disable the fast leave function. The MLD leave process sends a group-specific query to check the receivers' existence. Enable Enable the fast leave function. The MLD leave process does not check the receiver’s existence.</div></div><div id="gui_en_detail_multicast"><div class="search_title" docfname="gui_en_detail_multicast" doctitle="Multicast" link="#title-box">Multicast basic settings</div><div class="search_word">multicast basic settings</div><div class="display_word">Multicast basic settings</div></div><div id="gui_en_detail_multicast"><div class="search_title" docfname="gui_en_detail_multicast" doctitle="Multicast" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for basic settings related to multicast. specify processing method for unknown multicast frames. unknown multicast frames are frames destined to addresses not registered in igmp snooping. this product forwards unknown multicast frames to allports as the default setting, which does not matter in low bandwidthenvironments. however, discarding instead of forwarding in highbandwidth environments may be recommended. if you want to discard unknown multicast frames and only forward some multicast frames that use link local addresses such asmdns, you can exclude them from discarding.</div><div class="display_word">1. Summary This page is for basic settings related to multicast. Specify processing method for unknown multicast frames. Unknown multicast frames are frames destined to addresses not registered in IGMP snooping. This product forwards unknown multicast frames to allports as the default setting, which does not matter in low bandwidthenvironments. However, discarding instead of forwarding in highbandwidth environments may be recommended. If you want to discard unknown multicast frames and only forward some multicast frames that use link local addresses such asmDNS, you can exclude them from discarding.</div></div><div id="gui_en_detail_multicast"><div class="search_title" docfname="gui_en_detail_multicast" doctitle="Multicast" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for multicast basic settings.</div><div class="display_word">2. Top page This is the top page for multicast basic settings.</div></div><div id="gui_en_detail_multicast"><div class="search_title" docfname="gui_en_detail_multicast" doctitle="Multicast" link="#system_settings">2.1. System settings</div><div class="search_word">2.1. system settings displays the configuration for unknown multicast frames for the entire system. the table items are explained below. processing method for unknown multicast frames displays the processing method of unknown multicast frames. excluded frames from discarding (for all vlans) displays excluded frames from discarding when configured to discard unknown multicast frames. press the "setting" button to access a page where you can change the settings.</div><div class="display_word">2.1. System settings Displays the configuration for unknown multicast frames for the entire system. The table items are explained below. Processing method for unknown multicast frames Displays the processing method of unknown multicast frames. Excluded frames from discarding (for all VLANs) Displays excluded frames from discarding when configured to discard unknown multicast frames. Press the "Setting" button to access a page where you can change the settings.</div></div><div id="gui_en_detail_multicast"><div class="search_title" docfname="gui_en_detail_multicast" doctitle="Multicast" link="#vlan_interface_settings">2.2. VLAN interface settings</div><div class="search_word">2.2. vlan interface settings displays the configuration for unknown multicast frames for each vlan. the table items are explained below. vlan id vlan id is displayed. unknown multicast frame displays the processing method for unknown multicast frames for the target vlan. excluded frames from discarding displays the frames to be excludedfrom discarding when unknown multicast frames are configured to bediscarded in the target vlan. press the "setting" button to access a page where you can change the settings of the selected vlan. press the "specify all" button to configure the settings for all vlan interfaces with the check box selected. press the "return to defaults" button to initialize the settings for all vlan interfaces with the check box selected.</div><div class="display_word">2.2. VLAN interface settings Displays the configuration for unknown multicast frames for each VLAN. The table items are explained below. VLAN ID VLAN ID is displayed. Unknown multicast frame Displays the processing method for unknown multicast frames for the target VLAN. Excluded frames from discarding Displays the frames to be excludedfrom discarding when unknown multicast frames are configured to bediscarded in the target VLAN. Press the "Setting" button to access a page where you can change the settings of the selected VLAN. Press the "Specify all" button to configure the settings for all VLAN interfaces with the check box selected. Press the "Return to defaults" button to initialize the settings for all VLAN interfaces with the check box selected.</div></div><div id="gui_en_detail_multicast"><div class="search_title" docfname="gui_en_detail_multicast" doctitle="Multicast" link="#system">3. System settings page</div><div class="search_word">3. system settings page this page is for configuring unknown multicast frames for the entire system. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. System settings page This page is for configuring unknown multicast frames for the entire system. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_multicast"><div class="search_title" docfname="gui_en_detail_multicast" doctitle="Multicast" link="#system_settings_2">3.1. System settings</div><div class="search_word">3.1. system settings processing method for unknown multicast frames specify the processing method for unknown multicast frames from below. flood discard excluded frames from discarding (for all vlans) specify the excluded frames from discarding when configured to discard unknown multicast frames. specify the following conditions for excluded frames from discarding. link local address set all addresses in 224.0.0.0/24 and ff02::/112 as the target. this setting is for all vlans. this setting is not included in the number of configurable settings for the entire system.</div><div class="display_word">3.1. System settings Processing method for unknown multicast frames Specify the processing method for unknown multicast frames from below. Flood Discard Excluded frames from discarding (for all VLANs) Specify the excluded frames from discarding when configured to discard unknown multicast frames. Specify the following conditions for excluded frames from discarding. Link local address Set all addresses in 224.0.0.0/24 and ff02::/112 as the target. This setting is for all VLANs. This setting is not included in the number of configurable settings for the entire system.</div></div><div id="gui_en_detail_multicast"><div class="search_title" docfname="gui_en_detail_multicast" doctitle="Multicast" link="#vlan">4. VLAN Interface settings page</div><div class="search_word">4. vlan interface settings page this page is for configuring unknown multicast frames for a vlan interface. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. VLAN Interface settings page This page is for configuring unknown multicast frames for a VLAN interface. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_multicast"><div class="search_title" docfname="gui_en_detail_multicast" doctitle="Multicast" link="#vlan_interface_settings_2">4.1. VLAN interface settings</div><div class="search_word">4.1. vlan interface settings vlan id displays the vlan id for which the setting is to be changed. processing method for unknown multicast frames specify the processing method for unknown multicast frames from below. follow the system setting prefer the interface setting flood discard excluded frames from discarding specify the excluded frames from discarding when configured to discard unknown multicast frames. specify the following conditions for excluded frames from discarding. destination address specify the address type from the following. specify the address enter the ipv4 multicast address into the text box. mdns set 224.0.0.251 as the target. dante set 224.0.0.230 - 233 as the target. ptp set 224.0.1.129 - 132 and 239.254.3.3 as the target. press the icon to add a new row. press the "delete" button to delete the row. you can specify up to 100 addresses to be excluded from the discarding for the entire system. if specifying dante as the address type, one item is counted as four items. if specifying ptp as the address type, one item is counted as five items.</div><div class="display_word">4.1. VLAN interface settings VLAN ID Displays the VLAN ID for which the setting is to be changed. Processing method for unknown multicast frames Specify the processing method for unknown multicast frames from below. Follow the system setting Prefer the interface setting Flood Discard Excluded frames from discarding Specify the excluded frames from discarding when configured to discard unknown multicast frames. Specify the following conditions for excluded frames from discarding. Destination address Specify the address type from the following. Specify the address Enter the IPv4 multicast address into the text box. mDNS Set 224.0.0.251 as the target. Dante Set 224.0.0.230 - 233 as the target. PTP Set 224.0.1.129 - 132 and 239.254.3.3 as the target. Press the icon to add a new row. Press the "Delete" button to delete the row. You can specify up to 100 addresses to be excluded from the discarding for the entire system. If specifying Dante as the address type, one item is counted as four items. If specifying PTP as the address type, one item is counted as five items.</div></div><div id="gui_en_detail_multiple_vlan"><div class="search_title" docfname="gui_en_detail_multiple_vlan" doctitle="Multiple" link="#title-box">Multiple VLAN</div><div class="search_word">multiple vlan</div><div class="display_word">Multiple VLAN</div></div><div id="gui_en_detail_multiple_vlan"><div class="search_title" docfname="gui_en_detail_multiple_vlan" doctitle="Multiple" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can make multiple vlan settings. the multiple vlan function is used to divide ports for oneswitch into different groups and prohibit communication between thegroups. a single port can belong to multiple groups, so that the samenetwork address can be assigned even to different groups. if both the multiple vlan and port-based vlan / tagged vlanare used, communication is not possible between ports that belong todifferent vlans, even if the ports belong to same multiple-vlan group.</div><div class="display_word">1. Summary In this page you can make multiple VLAN settings. The Multiple VLAN function is used to divide ports for oneswitch into different groups and prohibit communication between thegroups. A single port can belong to multiple groups, so that the samenetwork address can be assigned even to different groups. If both the multiple VLAN and port-based VLAN / tagged VLANare used, communication is not possible between ports that belong todifferent VLANs, even if the ports belong to same multiple-VLAN group.</div></div><div id="gui_en_detail_multiple_vlan"><div class="search_title" docfname="gui_en_detail_multiple_vlan" doctitle="Multiple" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for multiple vlans.</div><div class="display_word">2. Top page This is the top page for multiple VLANs.</div></div><div id="gui_en_detail_multiple_vlan"><div class="search_title" docfname="gui_en_detail_multiple_vlan" doctitle="Multiple" link="#tag_vlan_settings">2.1. Tag VLAN settings</div><div class="search_word">2.1. tag vlan settings the multiple vlan group settings are shown for each lan port and logical interface. press the "setting" button to access a page where you can change the settings for the multiple vlan of the selected interface. if you press the "specify all" button, thesettings can be changed for all lan ports and logical interfaces whosecheck box contains a check mark. if you press the "return to defaults" button,the settings will be initialized for all lan ports and logicalinterfaces whose check box contains a check mark. in default settings, no interfaces belong to a group.</div><div class="display_word">2.1. Tag VLAN settings The multiple VLAN group settings are shown for each LAN port and logical interface. Press the "Setting" button to access a page where you can change the settings for the multiple VLAN of the selected interface. If you press the "Specify all" button, thesettings can be changed for all LAN ports and logical interfaces whosecheck box contains a check mark. If you press the "Return to defaults" button,the settings will be initialized for all LAN ports and logicalinterfaces whose check box contains a check mark. In default settings, no interfaces belong to a group.</div></div><div id="gui_en_detail_multiple_vlan"><div class="search_title" docfname="gui_en_detail_multiple_vlan" doctitle="Multiple" link="#mvlan_config">3. Multiple VLAN settings page</div><div class="search_word">3. multiple vlan settings page in this page you can make the multiple vlan settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the setting confirmation screen, press the "ok" button.</div><div class="display_word">3. Multiple VLAN settings page In this page you can make the multiple VLAN settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the setting confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_multiple_vlan"><div class="search_title" docfname="gui_en_detail_multiple_vlan" doctitle="Multiple" link="#multiple_vlan_settings">3.1. Multiple VLAN settings</div><div class="search_word">3.1. multiple vlan settings port the lan port or logical interface for which settings are made is shown group select the vlan groups to join. press the "select" button to display the "multiple vlan group selection" dialog box. groups to join a vlan can be selected byselecting the corresponding checkboxes in the "multiple vlan groupselection" dialog and press the "ok" button.</div><div class="display_word">3.1. Multiple VLAN settings Port The LAN port or logical interface for which settings are made is shown Group Select the VLAN groups to join. Press the "Select" button to display the "Multiple VLAN group selection" dialog box. Groups to join a VLAN can be selected byselecting the corresponding checkboxes in the "Multiple VLAN groupselection" dialog and press the "OK" button.</div></div><div id="gui_en_detail_passthrough"><div class="search_title" docfname="gui_en_detail_passthrough" doctitle="Pass" link="#title-box">Pass through</div><div class="search_word">pass through</div><div class="display_word">Pass through</div></div><div id="gui_en_detail_passthrough"><div class="search_title" docfname="gui_en_detail_passthrough" doctitle="Pass" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can edit the settings of the pass through function. if you enable the pass through function, you can forward special frames that are usually discarded.</div><div class="display_word">1. Summary In this page you can edit the settings of the pass through function. If you enable the pass through function, you can forward special frames that are usually discarded.</div></div><div id="gui_en_detail_passthrough"><div class="search_title" docfname="gui_en_detail_passthrough" doctitle="Pass" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for pass through.</div><div class="display_word">2. Top page This is the top page for pass through.</div></div><div id="gui_en_detail_passthrough"><div class="search_title" docfname="gui_en_detail_passthrough" doctitle="Pass" link="#eap_pass_through_setting">2.1. EAP pass through setting</div><div class="search_word">2.1. eap pass through setting the current setting is shown as to whether the eap pass through is enabled. if the eap pass through is enabled, the device forwards the received eapol frames so that the device can be placedbetween the ieee 802.1x authentication switch and pcs. press the "setting" button to access a page where you can change the settings.</div><div class="display_word">2.1. EAP pass through setting The current setting is shown as to whether the EAP pass through is enabled. If the EAP pass through is enabled, the device forwards the received EAPOL frames so that the device can be placedbetween the IEEE 802.1X authentication switch and PCs. Press the "Setting" button to access a page where you can change the settings.</div></div><div id="gui_en_detail_passthrough"><div class="search_title" docfname="gui_en_detail_passthrough" doctitle="Pass" link="#eap">3. EAP pass through settings page</div><div class="search_word">3. eap pass through settings page in this page you can specify whether the eap pass through is enabled. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. EAP pass through settings page In this page you can specify whether the EAP pass through is enabled. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_passthrough"><div class="search_title" docfname="gui_en_detail_passthrough" doctitle="Pass" link="#eap_pass_through_setting_2">3.1. EAP pass through setting</div><div class="search_word">3.1. eap pass through setting eap pass through enable forwards received eapol frames. disable discards received eapol frames.</div><div class="display_word">3.1. EAP pass through setting EAP pass through Enable Forwards received EAPOL frames. Disable Discards received EAPOL frames.</div></div><div id="gui_en_detail_poe"><div class="search_title" docfname="gui_en_detail_poe" doctitle="PoE" link="#title-box">PoE</div><div class="search_word">poe</div><div class="display_word">PoE</div></div><div id="gui_en_detail_poe"><div class="search_title" docfname="gui_en_detail_poe" doctitle="PoE" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring poe control.</div><div class="display_word">1. Summary This page is for configuring PoE control.</div></div><div id="gui_en_detail_poe"><div class="search_title" docfname="gui_en_detail_poe" doctitle="PoE" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for poe control.</div><div class="display_word">2. Top page This is the top page for PoE control.</div></div><div id="gui_en_detail_poe"><div class="search_title" docfname="gui_en_detail_poe" doctitle="PoE" link="#system_settings">2.1. System settings</div><div class="search_word">2.1. system settings displays the system settings for poe control. the table items are explained below. poe power supply for the entire system guardband press the "setting" button to display the page for configuring the system settings for poe.</div><div class="display_word">2.1. System settings Displays the system settings for PoE control. The table items are explained below. PoE power supply for the entire system Guardband Press the "Setting" button to display the page for configuring the system settings for PoE.</div></div><div id="gui_en_detail_poe"><div class="search_title" docfname="gui_en_detail_poe" doctitle="PoE" link="#interface_settings">2.2. Interface settings</div><div class="search_word">2.2. interface settings displays the poe power supply function settings for the interface. the table items are explained below. port displays the interface name. poe supply displays the poe power supply function settings for the target interface. priority displays the power supply priority for the target interface. description displays the description of the pd device connected to the poe port. press the "return to defaults" button to initialize the settings for all interfaces with the check box selected. press the "specify all" button to configure the settings for all interfaces with the check box selected. press the "setting" button to display the page for configuring the selected interface settings.</div><div class="display_word">2.2. Interface settings Displays the PoE power supply function settings for the interface. The table items are explained below. Port Displays the interface name. PoE supply Displays the PoE power supply function settings for the target interface. Priority Displays the power supply priority for the target interface. Description Displays the description of the PD device connected to the PoE port. Press the "Return to defaults" button to initialize the settings for all interfaces with the check box selected. Press the "Specify all" button to configure the settings for all interfaces with the check box selected. Press the "Setting" button to display the page for configuring the selected interface settings.</div></div><div id="gui_en_detail_poe"><div class="search_title" docfname="gui_en_detail_poe" doctitle="PoE" link="#system">3. System settings page</div><div class="search_word">3. system settings page this page is for configuring poe control for the system. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. System settings page This page is for configuring PoE control for the system. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_poe"><div class="search_title" docfname="gui_en_detail_poe" doctitle="PoE" link="#system_settings_2">3.1. System settings</div><div class="search_word">3.1. system settings poe power supply for the entire system specify whether to enable or disable the poe power supply function for the entire system. even if the poe power supply function for the entire system is enabled, ifeach port’s function is disabled, the poe power supply function for that port is disabled. guardband specify the guardband. the guardband is a margin against the upper limit of the available power supply set to prevent unexpected power outages. if the available power supply falls below the guardband, power does notsupply even if a new pd device is connected to a poe port. if 0w is specified, the guardband does not work.</div><div class="display_word">3.1. System settings PoE power supply for the entire system Specify whether to enable or disable the PoE power supply function for the entire system. Even if the PoE power supply function for the entire system is enabled, ifeach port’s function is disabled, the PoE power supply function for that port is disabled. Guardband Specify the guardband. The guardband is a margin against the upper limit of the available power supply set to prevent unexpected power outages. If the available power supply falls below the guardband, power does notsupply even if a new PD device is connected to a PoE port. If 0W is specified, the guardband does not work.</div></div><div id="gui_en_detail_poe"><div class="search_title" docfname="gui_en_detail_poe" doctitle="PoE" link="#interface">4. Interface settings page</div><div class="search_word">4. interface settings page this page is for configuring poe control for the interface. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Interface settings page This page is for configuring PoE control for the interface. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_poe"><div class="search_title" docfname="gui_en_detail_poe" doctitle="PoE" link="#interface_settings_2">4.1. Interface settings</div><div class="search_word">4.1. interface settings poe supply specify whether to enable or disable the poe power supply function for the target interface. the power supply continues even if the port is in a shutdown state.however, if the poe power supply function for the entire system isdisabled, power is not supplied. priority specify the power supply priority for the target interface. if the total power supply to all ports exceeds the upper limit of theavailable power supply, the port’s power supply with the lowest priority stops. description specify the description of the pd device connected to the poe port.</div><div class="display_word">4.1. Interface settings PoE supply Specify whether to enable or disable the PoE power supply function for the target interface. The power supply continues even if the port is in a shutdown state.However, if the PoE power supply function for the entire system isdisabled, power is not supplied. Priority Specify the power supply priority for the target interface. If the total power supply to all ports exceeds the upper limit of theavailable power supply, the port’s power supply with the lowest priority stops. Description Specify the description of the PD device connected to the PoE port.</div></div><div id="gui_en_detail_qos"><div class="search_title" docfname="gui_en_detail_qos" doctitle="QoS" link="#title-box">QoS</div><div class="search_word">qos</div><div class="display_word">QoS</div></div><div id="gui_en_detail_qos"><div class="search_title" docfname="gui_en_detail_qos" doctitle="QoS" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can edit the settings of the qos (quality of service) function. you can enable/disable the qos function, and change the trust mode.</div><div class="display_word">1. Summary In this page you can edit the settings of the QoS (Quality of Service) function. You can enable/disable the QoS function, and change the trust mode.</div></div><div id="gui_en_detail_qos"><div class="search_title" docfname="gui_en_detail_qos" doctitle="QoS" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for qos.</div><div class="display_word">2. Top page This is the top page for QoS.</div></div><div id="gui_en_detail_qos"><div class="search_title" docfname="gui_en_detail_qos" doctitle="QoS" link="#web_conference_applications_optimization">2.1. Web conference applications optimization</div><div class="search_word">2.1. web conference applications optimization the "next" button starts the procedure to configure the optimal qos settings for the web conference application.</div><div class="display_word">2.1. Web conference applications optimization The "Next" button starts the procedure to configure the optimal QoS settings for the web conference application.</div></div><div id="gui_en_detail_qos"><div class="search_title" docfname="gui_en_detail_qos" doctitle="QoS" link="#system_settings">2.2. System settings</div><div class="search_word">2.2. system settings displays the qos settings for the entire system. the table items are explained below. qos function displays whether the qos function is enabled. cos - transmit queue mapping table displays the transmit queue id settings corresponding to the cos value. dscp - transmit queue mapping table displays the transmit queue id settings corresponding to the dscp value. press the "setting" button to access a page where you can change the settings to enable the qos function, you must disable flow control.</div><div class="display_word">2.2. System settings Displays the QoS settings for the entire system. The table items are explained below. QoS function Displays whether the QoS function is enabled. CoS - transmit queue mapping table Displays the transmit queue ID settings corresponding to the CoS value. DSCP - transmit queue mapping table Displays the transmit queue ID settings corresponding to the DSCP value. Press the "Setting" button to access a page where you can change the settings To enable the QoS function, you must disable flow control.</div></div><div id="gui_en_detail_qos"><div class="search_title" docfname="gui_en_detail_qos" doctitle="QoS" link="#interface_settings">2.3. Interface settings</div><div class="search_word">2.3. interface settings the trust mode setting used by the qos function is shown for each lan/sfp port press the "setting" button to access a page where you can change the settings of the selected lan/sfp port if you press the "specify all" button, the settings can be changed for all lan/sfp ports whose check box contains a check mark if you press the "return to defaults" button,the settings will be initialized for all lan/sfp ports whose check boxcontains a check mark the default trust mode setting for all ports is "cos" the default cos value for all ports is "0" by default. if the settings do not use the qos function, qos function settings cannot be made</div><div class="display_word">2.3. Interface settings The trust mode setting used by the QoS function is shown for each LAN/SFP port Press the "Setting" button to access a page where you can change the settings of the selected LAN/SFP port If you press the "Specify all" button, the settings can be changed for all LAN/SFP ports whose check box contains a check mark If you press the "Return to defaults" button,the settings will be initialized for all LAN/SFP ports whose check boxcontains a check mark The default trust mode setting for all ports is "CoS" The default CoS value for all ports is "0" by default. If the settings do not use the QoS function, QoS function settings cannot be made</div></div><div id="gui_en_detail_qos"><div class="search_title" docfname="gui_en_detail_qos" doctitle="QoS" link="#qos_opti">3. Web conference applications optimization page</div><div class="search_word">3. web conference applications optimization page this page provides optimal qos settings for web conference applications. when you have inputted the settings, press the "confirm" button. if there are no mistakes in the input content confirmation screen, press the "ok" button. the following settings are configured in the optimal settings for web conference application. - enables qos. - set trust mode to dscp for all ports. - assigns the dscp value used by the web conferenceapplication to be optimized to the highest priority outgoing queue. - assigns the dscp value not used by the web conference application to be optimized to the lowest priority outgoing queue. - sets scheduling of all transmit queues to strict priority.</div><div class="display_word">3. Web conference applications optimization page This page provides optimal QoS settings for web conference applications. When you have inputted the settings, press the "Confirm" button. If there are no mistakes in the input content confirmation screen, press the "OK" button. The following settings are configured in the Optimal Settings for Web conference application. - Enables QoS. - Set trust mode to DSCP for all ports. - Assigns the DSCP value used by the web conferenceapplication to be optimized to the highest priority outgoing queue. - Assigns the DSCP value not used by the web conference application to be optimized to the lowest priority outgoing queue. - Sets scheduling of all transmit queues to Strict Priority.</div></div><div id="gui_en_detail_qos"><div class="search_title" docfname="gui_en_detail_qos" doctitle="QoS" link="#web_conference_applications_optimization_2">3.1. Web conference applications optimization</div><div class="search_word">3.1. web conference applications optimization target application select the web conference application to be optimized.</div><div class="display_word">3.1. Web conference applications optimization Target application Select the web conference application to be optimized.</div></div><div id="gui_en_detail_qos"><div class="search_title" docfname="gui_en_detail_qos" doctitle="QoS" link="#qos_basic">4. System settings page</div><div class="search_word">4. system settings page in this page you can specify whether the qos function is used. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button. be aware that if the settings do not use the qos function, all qos-related settings will be cleared.</div><div class="display_word">4. System settings page In this page you can specify whether the QoS function is used. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button. Be aware that if the settings do not use the QoS function, all QoS-related settings will be cleared.</div></div><div id="gui_en_detail_qos"><div class="search_title" docfname="gui_en_detail_qos" doctitle="QoS" link="#system_settings_2">4.1. System settings</div><div class="search_word">4.1. system settings qos function disable the qos function will be disabled. at this time, all qos settings will be cleared. enable the qos function will be enabled. qos-related settings and commands can be executed. cos - transmit queue mapping table configures the transmit queue id settings corresponding to each cos value. the input range of the transmit queue id is 0 to 7, and a larger id has a higher priority for sending frames. if you press the "easy input" button, thefollowing settings can be entered together into the cos - transmit queue mapping table. initialization factory default settings. dscp - transmit queue mapping table configures the transmit queue id settings corresponding to each dscp value. the input range of the transmit queue id is 0 to 7, and a larger id has a higher priority for sending frames. when "display only rfc compliance values"is checked, only rfc-compliant dscp values will be displayed. however,all dscp values will be displayed on the input confirmation screen. if you press the "easy input" button, thefollowing settings can be entered together into the dscp - transmitqueue mapping table. initialization factory default settings. dante optimization assigns dscp values used by dante to the highest priority queue and unused dscp values to the lowest priority queue. web conference applications optimization assigns dscp values used by theweb conference application to the highest priority queue and unused dscp values to the lowest priority queue. please select at least one web conference application.</div><div class="display_word">4.1. System settings QoS function Disable The QoS function will be disabled. At this time, all QoS settings will be cleared. Enable The QoS function will be enabled. QoS-related settings and commands can be executed. CoS - transmit queue mapping table Configures the transmit queue ID settings corresponding to each CoS value. The input range of the transmit queue ID is 0 to 7, and a larger ID has a higher priority for sending frames. If you press the "Easy input" button, thefollowing settings can be entered together into the CoS - transmit queue mapping table. Initialization Factory default settings. DSCP - transmit queue mapping table Configures the transmit queue ID settings corresponding to each DSCP value. The input range of the transmit queue ID is 0 to 7, and a larger ID has a higher priority for sending frames. When "Display only RFC compliance values"is checked, only RFC-compliant DSCP values will be displayed. However,all DSCP values will be displayed on the input confirmation screen. If you press the "Easy input" button, thefollowing settings can be entered together into the DSCP - transmitqueue mapping table. Initialization Factory default settings. Dante optimization Assigns DSCP values used by Dante to the highest priority queue and unused DSCP values to the lowest priority queue. Web conference applications optimization Assigns DSCP values used by theweb conference application to the highest priority queue and unused DSCP values to the lowest priority queue. Please select at least one web conference application.</div></div><div id="gui_en_detail_qos"><div class="search_title" docfname="gui_en_detail_qos" doctitle="QoS" link="#qos_detail">5. Interface settings page</div><div class="search_word">5. interface settings page set the "trust mode" setting which means whether thetransmission queue is determined based on the packet’s cos value or thedscp value or the port priority. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">5. Interface settings page Set the "Trust mode" setting which means whether thetransmission queue is determined based on the packet’s CoS value or theDSCP value or the Port priority. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_qos"><div class="search_title" docfname="gui_en_detail_qos" doctitle="QoS" link="#interface_settings_2">5.1. Interface settings</div><div class="search_word">5.1. interface settings port the lan/sfp port for which settings are made is shown trust mode use cos value to determine transmission queue the packet’s cos value and the "cos - transmission queue id conversion table" are used to determine the transmission queue if the received packet is an untagged packet, the default cos value is applied a default cos value within the 0 - 7 range can be specified. use dscp value to determine transmission queue the packet’s dscp value and the "dscp - transmission queue id conversion table" are used to determine the transmission queue use the priority specified for the port to determine the transmission queue the transmission queue is determined according to the "port priority order" select the transmission queue to be assigned as the port priority order in the range of 0 - 7 higher numbers indicate a higher priority order; with the default settings, 2 is selected the setting can be changed only if the trust mode is set to "port priority" if a policy map is applied to the lan/sfp port, you cannot change the trust mode setting.</div><div class="display_word">5.1. Interface settings Port The LAN/SFP port for which settings are made is shown Trust mode Use CoS value to determine transmission queue The packet’s CoS value and the "CoS - Transmission queue ID conversion table" are used to determine the transmission queue If the received packet is an untagged packet, the default CoS value is applied A default CoS value within the 0 - 7 range can be specified. Use DSCP value to determine transmission queue The packet’s DSCP value and the "DSCP - Transmission queue ID conversion table" are used to determine the transmission queue Use the priority specified for the port to determine the transmission queue The transmission queue is determined according to the "Port priority order" Select the transmission queue to be assigned as the port priority order in the range of 0 - 7 Higher numbers indicate a higher priority order; with the default settings, 2 is selected The setting can be changed only if the trust mode is set to "Port priority" If a policy map is applied to the LAN/SFP port, you cannot change the trust mode setting.</div></div><div id="gui_en_detail_rds_cert"><div class="search_title" docfname="gui_en_detail_rds_cert" doctitle="Managing" link="#title-box">Managing certificates</div><div class="search_word">managing certificates</div><div class="display_word">Managing certificates</div></div><div id="gui_en_detail_rds_cert"><div class="search_title" docfname="gui_en_detail_rds_cert" doctitle="Managing" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for performing certificate-related operations.</div><div class="display_word">1. Summary This page is for performing certificate-related operations.</div></div><div id="gui_en_detail_rds_cert"><div class="search_title" docfname="gui_en_detail_rds_cert" doctitle="Managing" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for certificate operations.</div><div class="display_word">2. Top page This is the top page for certificate operations.</div></div><div id="gui_en_detail_rds_cert"><div class="search_title" docfname="gui_en_detail_rds_cert" doctitle="Managing" link="#mail_notification_settings">2.1. Mail notification settings</div><div class="search_word">2.1. mail notification settings displays e-mail notification-related settings for certificates. the table items are explained below. mail template id for sending certificates displays the mail template id to be used when attaching and sending a client certificate via e-mail. mail template id for certificate period of validity notifications displays the mail template id to beused when attaching and sending a client certificate period of validitynotification via e-mail. timing of period of certificate validity notifications displays the settings for the timing used to send the period of validity notifications for client certificates.</div><div class="display_word">2.1. Mail notification settings Displays e-mail notification-related settings for certificates. The table items are explained below. Mail template ID for sending certificates Displays the mail template ID to be used when attaching and sending a client certificate via e-mail. Mail template ID for certificate period of validity notifications Displays the mail template ID to beused when attaching and sending a client certificate period of validitynotification via e-mail. Timing of period of certificate validity notifications Displays the settings for the timing used to send the period of validity notifications for client certificates.</div></div><div id="gui_en_detail_rds_cert"><div class="search_title" docfname="gui_en_detail_rds_cert" doctitle="Managing" link="#user_list">2.2. User list</div><div class="search_word">2.2. user list displays the certificate information for the radius user. the table items are explained below. check box select the check box to issue, revoke or download a certificate. user id displays the user id for the radius user. name displays the name of the radius user. mail address the radius user e-mail addresses will be displayed. period of validity (settings) displays the certificate’s period of validity for the radius user. period of validity (certificate) displays the period of validity of the client certificate associated with a radius user. if there are multiple client certificates, the certificate with the most recent period of validity will be shown. input the text string in the text box at the top of the table, and press the icon to search for user information. the drop-down list box to the left of the text box lets you select one of the following items to filter the searchparameters even further. none user id name mail address certificates not issued expired certificates certificates soon to expire displays users whose certificates will expire within one month. certificates revoked you cannot specify a search text string when selecting either certificates not issued , expired certificates , certificates soon to expire or certificates revoked . a maximum of 100 items can be displayed for one page. press or or enter a numeric value to switch between pages. you can press the sort switch to sort by each item. press the “issue” button in the “specified users” box to issue certificates for all radius users whose check boxes are selected. you can select the check box for attach certificates issued and send via e-mail that is displayed in the dialog box and press the "ok" button to attach and send the issued certificates via e-mail. the e-mail recipients are the e-mail addresses of each radius user. press the “revoke” button in the “specifiedusers” box to revoke certificates for all radius users whose check boxes are selected. select the certificate which will be revoked from the list below. old certificates new certificates both for users with only one certificate, the certificate is revoked regardless of which of the above is selected. press the “download” button in the “specifiedusers” box to download the certificates for all radius users whose check boxes are selected. press the “send” button in the “specifiedusers” box to attach and send the certificates for all radius userswhose check boxes are selected. press the “download” button in the “all users” box to download the certificates for all radius users. press the “send” button in the “all users” box to attach and send the certificates for all radius users via e-mail. some operations will be restricted for the statuses shown below. the certificate authority does not exist certificate is being issued if a user exists whose certificate has not been issued, a notification will be shown in the blue information box. press the “bulk issue” button to issue client certificates in bulk, for users corresponding to the following. users who have never issued certificate users who was changed password or expire after issued certificate the progress will be shown in the blue information box while the certificates are being issued.</div><div class="display_word">2.2. User list Displays the certificate information for the RADIUS user. The table items are explained below. Check box Select the check box to issue, revoke or download a certificate. User ID Displays the user ID for the RADIUS user. Name Displays the name of the RADIUS user. Mail address The RADIUS user e-mail addresses will be displayed. Period of validity (Settings) Displays the certificate’s period of validity for the RADIUS user. Period of validity (certificate) Displays the period of validity of the client certificate associated with a RADIUS user. If there are multiple client certificates, the certificate with the most recent period of validity will be shown. Input the text string in the text box at the top of the table, and press the icon to search for user information. The drop-down list box to the left of the text box lets you select one of the following items to filter the searchparameters even further. None User ID Name Mail address Certificates not issued Expired certificates Certificates soon to expire Displays users whose certificates will expire within one month. Certificates revoked You cannot specify a search text string when selecting either Certificates not issued , Expired certificates , Certificates soon to expire or Certificates revoked . A maximum of 100 items can be displayed for one page. Press or or enter a numeric value to switch between pages. You can press the sort switch to sort by each item. Press the “Issue” button in the “Specified users” box to issue certificates for all RADIUS users whose check boxes are selected. You can select the check box for Attach certificates issued and send via e-mail that is displayed in the dialog box and press the "OK" button to attach and send the issued certificates via e-mail. The e-mail recipients are the e-mail addresses of each RADIUS user. Press the “Revoke” button in the “Specifiedusers” box to revoke certificates for all RADIUS users whose check boxes are selected. Select the certificate which will be revoked from the list below. Old certificates New certificates Both For users with only one certificate, the certificate is revoked regardless of which of the above is selected. Press the “Download” button in the “Specifiedusers” box to download the certificates for all RADIUS users whose check boxes are selected. Press the “Send” button in the “Specifiedusers” box to attach and send the certificates for all RADIUS userswhose check boxes are selected. Press the “Download” button in the “All users” box to download the certificates for all RADIUS users. Press the “Send” button in the “All users” box to attach and send the certificates for all RADIUS users via e-mail. Some operations will be restricted for the statuses shown below. The certificate authority does not exist Certificate is being issued If a user exists whose certificate has not been issued, a notification will be shown in the blue information box. Press the “Bulk issue” button to issue client certificates in bulk, for users corresponding to the following. Users who have never issued certificate Users who was changed password or expire after issued certificate The progress will be shown in the blue information box while the certificates are being issued.</div></div><div id="gui_en_detail_rds_cert"><div class="search_title" docfname="gui_en_detail_rds_cert" doctitle="Managing" link="#mail_setting">3. Mail notification settings page</div><div class="search_word">3. mail notification settings page this page is for settings related to certificate e-mail notifications. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Mail notification settings page This page is for settings related to certificate e-mail notifications. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_rds_cert"><div class="search_title" docfname="gui_en_detail_rds_cert" doctitle="Managing" link="#mail_notification_settings_2">3.1. Mail notification settings</div><div class="search_word">3.1. mail notification settings mail template id for sending certificates select the mail template id. mail template id for certificate period of validity notifications select the mail template id. timing of period of certificate validity notifications specify the timing of the period of certificate validity notifications. input a value from 1 to 90. up to three can be specified.</div><div class="display_word">3.1. Mail notification settings Mail template ID for sending certificates Select the mail template ID. Mail template ID for certificate period of validity notifications Select the mail template ID. Timing of period of certificate validity notifications Specify the timing of the period of certificate validity notifications. Input a value from 1 to 90. Up to three can be specified.</div></div><div id="gui_en_detail_rds_cert"><div class="search_title" docfname="gui_en_detail_rds_cert" doctitle="Managing" link="#cert_operate">4. Certificate operations page</div><div class="search_word">4. certificate operations page this page is for performing certificate-related operations. enter the contents, and then press the "confirm" button. if there are no mistakes in the input content confirmation screen, press the "ok" button.</div><div class="display_word">4. Certificate operations page This page is for performing certificate-related operations. Enter the contents, and then press the "Confirm" button. If there are no mistakes in the input content confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_rds_cert"><div class="search_title" docfname="gui_en_detail_rds_cert" doctitle="Managing" link="#certificate_operations">4.1. Certificate operations</div><div class="search_word">4.1. certificate operations certificate to operate information for the target certificate for the operation will be displayed. select the check box of the certificate for which the operation is performed. content to execute select the certificate operation from the list below. download certificate attach certificates and send via e-mail set certificate to revoke</div><div class="display_word">4.1. Certificate operations Certificate to operate Information for the target certificate for the operation will be displayed. Select the check box of the certificate for which the operation is performed. Content to execute Select the certificate operation from the list below. Download certificate Attach certificates and send via e-mail Set certificate to revoke</div></div><div id="gui_en_detail_rds_server"><div class="search_title" docfname="gui_en_detail_rds_server" doctitle="Server" link="#title-box">Server settings</div><div class="search_word">server settings</div><div class="display_word">Server settings</div></div><div id="gui_en_detail_rds_server"><div class="search_title" docfname="gui_en_detail_rds_server" doctitle="Server" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for performing operations related to the certificate authority and radius server.</div><div class="display_word">1. Summary This page is for performing operations related to the certificate authority and RADIUS server.</div></div><div id="gui_en_detail_rds_server"><div class="search_title" docfname="gui_en_detail_rds_server" doctitle="Server" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the radius server.</div><div class="display_word">2. Top page This is the top page for the RADIUS server.</div></div><div id="gui_en_detail_rds_server"><div class="search_title" docfname="gui_en_detail_rds_server" doctitle="Server" link="#certificate_authority_management">2.1. Certificate authority management</div><div class="search_word">2.1. certificate authority management press the “next” button to the right of “create certificate authority” to begin the process of creating a certificate authority. press the “next” button to the right of“delete certificate authority” to begin the process of deleting thecertificate authority. press the “next” button to the right of“backup/restoration files and settings related to certificate authority” to begin the process of backing up or restoring.</div><div class="display_word">2.1. Certificate authority management Press the “Next” button to the right of “Create certificate authority” to begin the process of creating a certificate authority. Press the “Next” button to the right of“Delete certificate authority” to begin the process of deleting thecertificate authority. Press the “Next” button to the right of“Backup/restoration files and settings related to certificate authority” to begin the process of backing up or restoring.</div></div><div id="gui_en_detail_rds_server"><div class="search_title" docfname="gui_en_detail_rds_server" doctitle="Server" link="#radius_server_settings">2.2. RADIUS server settings</div><div class="search_word">2.2. radius server settings displays the settings for the radius server. the table items are explained below. radius server usage displays whether a radius server is to be used or not. if a radius server is to be used, the port number will be displayed. interfaces that can access the radius server displays the interfaces that can access the radius server. reauthentication interval configured for authenticator displays the settings for the reauthentication interval configured on the authenticator by the radius server. authentication method displays the authentication method settings used by the radius server.</div><div class="display_word">2.2. RADIUS server settings Displays the settings for the RADIUS server. The table items are explained below. RADIUS server usage Displays whether a RADIUS server is to be used or not. If a RADIUS server is to be used, the port number will be displayed. Interfaces that can access the RADIUS server Displays the interfaces that can access the RADIUS server. Reauthentication interval configured for authenticator Displays the settings for the reauthentication interval configured on the authenticator by the RADIUS server. Authentication method Displays the authentication method settings used by the RADIUS server.</div></div><div id="gui_en_detail_rds_server"><div class="search_title" docfname="gui_en_detail_rds_server" doctitle="Server" link="#radius_client_list">2.3. RADIUS client list</div><div class="search_word">2.3. radius client list displays the radius client settings. the table items are explained below. check box select the check box to delete the radius client settings. ip address displays the radius client address. a maximum of 20 items can be displayed for one page. press or or enter a numeric value to switch between pages. you can press the sort switch to sort by each item. press the “new” button to access a page where you can configure the settings for a new radius client. press the “setting” button to access a page where you can change the selected radius client settings. press the “delete” button to delete all radius clients whose check boxes are selected. on this page, you can configure up to 100 radius clients.</div><div class="display_word">2.3. RADIUS client list Displays the RADIUS client settings. The table items are explained below. Check box Select the check box to delete the RADIUS client settings. IP address Displays the RADIUS client address. A maximum of 20 items can be displayed for one page. Press or or enter a numeric value to switch between pages. You can press the sort switch to sort by each item. Press the “New” button to access a page where you can configure the settings for a new RADIUS client. Press the “Setting” button to access a page where you can change the selected RADIUS client settings. Press the “Delete” button to delete all RADIUS clients whose check boxes are selected. On this page, you can configure up to 100 RADIUS clients.</div></div><div id="gui_en_detail_rds_server"><div class="search_title" docfname="gui_en_detail_rds_server" doctitle="Server" link="#ca_create">3. Certificate authority creation page</div><div class="search_word">3. certificate authority creation page this is the certificate authority creation page. enter the certificate authority name, and then press the "confirm" button. if there are no mistakes in the input content confirmation screen, press the "ok" button. if a certificate authority already exists, you will not be able to create a certificate authority.</div><div class="display_word">3. Certificate authority creation page This is the certificate authority creation page. Enter the certificate authority name, and then press the "Confirm" button. If there are no mistakes in the input content confirmation screen, press the "OK" button. If a certificate authority already exists, you will not be able to create a certificate authority.</div></div><div id="gui_en_detail_rds_server"><div class="search_title" docfname="gui_en_detail_rds_server" doctitle="Server" link="#create_a_certificate_authority">3.1. Create a certificate authority</div><div class="search_word">3.1. create a certificate authority name specifies the certificate authority name. enter from 3 to 32 single-byte alphanumeric characters/symbols, with the following exceptions: \[]/"?space you cannot set the name as default . if this is omitted, the name swx-radius will be automatically set.</div><div class="display_word">3.1. Create a certificate authority Name Specifies the certificate authority name. Enter from 3 to 32 single-byte alphanumeric characters/symbols, with the following exceptions: \[]/"?space You cannot set the name as DEFAULT . If this is omitted, the name swx-radius will be automatically set.</div></div><div id="gui_en_detail_rds_server"><div class="search_title" docfname="gui_en_detail_rds_server" doctitle="Server" link="#ca_delete">4. Certificate authority deletion page</div><div class="search_word">4. certificate authority deletion page this is the certificate authority deletion page. press the "ok" button to delete the certificate authority. deleting the certificate authority will delete all radius-related settings, certificates and so on.</div><div class="display_word">4. Certificate authority deletion page This is the certificate authority deletion page. Press the "OK" button to delete the certificate authority. Deleting the certificate authority will delete all RADIUS-related settings, certificates and so on.</div></div><div id="gui_en_detail_rds_server"><div class="search_title" docfname="gui_en_detail_rds_server" doctitle="Server" link="#backup_restore">5. Backup / Restoration page</div><div class="search_word">5. backup / restoration page this page is for backup/restoration of settings related to certificate authorities. enter the contents, and then press the "confirm" button. if there are no mistakes in the input content confirmation screen, press the "ok" button. the following files and settings will be backed up and restored. certificate authority various certificates radius client settings radius user settings</div><div class="display_word">5. Backup / Restoration page This page is for backup/restoration of settings related to certificate authorities. Enter the contents, and then press the "Confirm" button. If there are no mistakes in the input content confirmation screen, press the "OK" button. The following files and settings will be backed up and restored. Certificate authority Various certificates RADIUS client settings RADIUS user settings</div></div><div id="gui_en_detail_rds_server"><div class="search_title" docfname="gui_en_detail_rds_server" doctitle="Server" link="#backup_restoration">5.1. Backup / Restoration</div><div class="search_word">5.1. backup / restoration content to execute select below whether a content to execute. back up restore import the backup file of a yamaha wireless ap file to restore press the "select a file" button to specify the file to restore. when "import the backup file of a yamaha wireless ap" is selected, specify the file backed up on wlx402 or wlx313. zip file password enter up to 32 single-byte alphanumeric characters/symbols, with the following exceptions: #&^\;|`{} when backing up, enter the password set for the backup file. when restoring or importing the backupfile of a yamaha wireless ap, enter the password set for the backup file when it was backed up. when using a file without a password, restore or import successfully with or without input of password.</div><div class="display_word">5.1. Backup / Restoration Content to execute Select below whether a content to execute. Back up Restore Import the backup file of a Yamaha wireless AP File to restore Press the "Select a file" button to specify the file to restore. When "Import the backup file of a Yamaha wireless AP" is selected, specify the file backed up on WLX402 or WLX313. zip file password Enter up to 32 single-byte alphanumeric characters/symbols, with the following exceptions: #&^\;|`{} When backing up, enter the password set for the backup file. When restoring or importing the backupfile of a Yamaha wireless AP, enter the password set for the backup file when it was backed up. When using a file without a password, restore or import successfully with or without input of password.</div></div><div id="gui_en_detail_rds_server"><div class="search_title" docfname="gui_en_detail_rds_server" doctitle="Server" link="#server_setting">6. RADIUS server settings page</div><div class="search_word">6. radius server settings page in this page you can configure the settings for a radius server. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">6. RADIUS server settings page In this page you can configure the settings for a RADIUS server. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_rds_server"><div class="search_title" docfname="gui_en_detail_rds_server" doctitle="Server" link="#radius_server_settings_2">6.1. RADIUS server settings</div><div class="search_word">6.1. radius server settings radius server usage select below whether a radius server will be used. use don’t use when use is selected, specify the port number. input a port number from 1024 to 65535. when use is selected, a certificate authority is created when the settings are made, if one does not already exist. interfaces that can access the radius server press the "select" button to display the "vlan interface list" dialog box. you can select the port check box in the"vlan interface list" dialog box and press the "ok" button to select the associated interface. up to 7 vlan interfaces can be selected. reauthentication interval configured for authenticator select the reauthentication interval configured on the authenticator from the options below. 3600 seconds 43200 seconds 86400 seconds 604800 seconds authentication method select the authentication method used by the radius server from the methods below. pap peap eap-md5 eap-tls eap-ttls</div><div class="display_word">6.1. RADIUS server settings RADIUS server usage Select below whether a RADIUS server will be used. Use Don’t use When Use is selected, specify the port number. Input a port number from 1024 to 65535. When Use is selected, a certificate authority is created when the settings are made, if one does not already exist. Interfaces that can access the RADIUS server Press the "Select" button to display the "VLAN interface list" dialog box. You can select the port check box in the"VLAN interface list" dialog box and press the "OK" button to select the associated interface. Up to 7 VLAN interfaces can be selected. Reauthentication interval configured for authenticator Select the reauthentication interval configured on the authenticator from the options below. 3600 Seconds 43200 Seconds 86400 Seconds 604800 Seconds Authentication method Select the authentication method used by the RADIUS server from the methods below. PAP PEAP EAP-MD5 EAP-TLS EAP-TTLS</div></div><div id="gui_en_detail_rds_server"><div class="search_title" docfname="gui_en_detail_rds_server" doctitle="Server" link="#client_setting">7. RADIUS client settings page</div><div class="search_word">7. radius client settings page this page is for configuring the radius client settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">7. RADIUS client settings page This page is for configuring the RADIUS client settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_rds_server"><div class="search_title" docfname="gui_en_detail_rds_server" doctitle="Server" link="#radius_client_settings">7.1. RADIUS client settings</div><div class="search_word">7.1. radius client settings ip address specifies the radius client address. enter ipv4 addresses using the xxx.xxx.xxx.xxx format. enter ipv6 addresses using the xxxx:xxxx::xxxx.xxxx format. when the settings are changed, the ip address of the selected radius client will be displayed as text. secret text string specifies the secret text string of the radius client. enter up to 128 single-byte alphanumeric characters/symbols, with the following exceptions: \[]"?space</div><div class="display_word">7.1. RADIUS client settings IP address Specifies the RADIUS client address. Enter IPv4 addresses using the XXX.XXX.XXX.XXX format. Enter IPv6 addresses using the XXXX:XXXX::XXXX.XXXX format. When the settings are changed, the IP address of the selected RADIUS client will be displayed as text. Secret text string Specifies the secret text string of the RADIUS client. Enter up to 128 single-byte alphanumeric characters/symbols, with the following exceptions: \[]"?space</div></div><div id="gui_en_detail_rds_user"><div class="search_title" docfname="gui_en_detail_rds_user" doctitle="User" link="#title-box">User management</div><div class="search_word">user management</div><div class="display_word">User management</div></div><div id="gui_en_detail_rds_user"><div class="search_title" docfname="gui_en_detail_rds_user" doctitle="User" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring the radius user settings.</div><div class="display_word">1. Summary This page is for configuring the RADIUS user settings.</div></div><div id="gui_en_detail_rds_user"><div class="search_title" docfname="gui_en_detail_rds_user" doctitle="User" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for radius users.</div><div class="display_word">2. Top page This is the top page for RADIUS users.</div></div><div id="gui_en_detail_rds_user"><div class="search_title" docfname="gui_en_detail_rds_user" doctitle="User" link="#user_settings">2.1. User settings</div><div class="search_word">2.1. user settings displays the settings for the radius user. the table items are explained below. check box select the check box to delete the radius user settings. user id displays the user id for the radius user. name displays the name of the radius user. authentication method displays the authentication method for the radius user. vlan displays the vlan that can be accessed by the radius user. input the text string in the text box at the top of the table, and press the icon to search for user information. the drop-down list box to the left of the text box lets you select one of the following items to filter the searchparameters even further. none user id name authentication method vlan a maximum of 100 items can be displayed for one page. press or or enter a numeric value to switch between pages. you can press the sort switch to sort by each item. press the “new” button to display a page where you can create new settings for the radius user. press the “setting” button to access a page where you can change the settings of the selected radius user. press the “delete” button to delete the settings for all radius users whose check boxes are selected. press the “import” button to display a page where you can import settings for the radius user. press the “export” button to export the settings for radius users as a csv file. on this page, you can configure up to 2000 radius users.</div><div class="display_word">2.1. User settings Displays the settings for the RADIUS user. The table items are explained below. Check box Select the check box to delete the RADIUS user settings. User ID Displays the user ID for the RADIUS user. Name Displays the name of the RADIUS user. Authentication method Displays the authentication method for the RADIUS user. VLAN Displays the VLAN that can be accessed by the RADIUS user. Input the text string in the text box at the top of the table, and press the icon to search for user information. The drop-down list box to the left of the text box lets you select one of the following items to filter the searchparameters even further. None User ID Name Authentication method VLAN A maximum of 100 items can be displayed for one page. Press or or enter a numeric value to switch between pages. You can press the sort switch to sort by each item. Press the “New” button to display a page where you can create new settings for the RADIUS user. Press the “Setting” button to access a page where you can change the settings of the selected RADIUS user. Press the “Delete” button to delete the settings for all RADIUS users whose check boxes are selected. Press the “Import” button to display a page where you can import settings for the RADIUS user. Press the “Export” button to export the settings for RADIUS users as a CSV file. On this page, you can configure up to 2000 RADIUS users.</div></div><div id="gui_en_detail_rds_user"><div class="search_title" docfname="gui_en_detail_rds_user" doctitle="User" link="#user_setting">3. User settings page</div><div class="search_word">3. user settings page this page is for configuring the radius user settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. User settings page This page is for configuring the RADIUS user settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_rds_user"><div class="search_title" docfname="gui_en_detail_rds_user" doctitle="User" link="#user_settings_2">3.1. User settings</div><div class="search_word">3.1. user settings select an authentication function select the authentication method used by the radius user from the methods below. 802.1x mac web none when the authentication method isselected, the items that must be entered and the items that do not needto be entered for the selected authentication function will becomeclear. when using a yamaha device as the authenticator, we recommend that you select an authentication function. when not specified is selected, all items will become selectable. when using a non-yamaha device as the authenticator, we recommend that you select not specified . when changing the settings, it is not possible to select anything besides not specified . user id specifies the user id for the radius user. specify a text string from 3 to 32 characters. the characters that can be inputted depends on the type of authentication method. for pap, eap-md5, eap-ttls, and peap: single-byte alphanumeric characters/symbols, with the following exceptions: \[]"?space for eap-tls: single-byte alphanumeric characters/symbols, with the following exceptions: \[]/:< >|"?space* you cannot set the name as default . when using mac authentication, input the mac address for the user’s terminal. for the mac address, use one of the following input formats according to the authenticator settings. xx:xx:xx:xx:xx:xx xx-xx-xx-xx-xx-xx xxxxxxxxxxxx when mac authentication isselected for “select an authentication function,” the mac address thatwas entered will be automatically reflected in the “password” and“password (confirm)” fields. password specifies the password for the radius user. enter up to 32 single-byte alphanumeric characters/symbols, with the following exceptions: \[]? when using mac authentication, input the mac address for the user’s terminal. password ( confirm ) to confirm, enter the password once again that you entered in the “password” field. authentication method select the authentication method used to authenticate the radius user from the methods below. pap peap, eap-md5, eap-ttls eap-tls name specifies the name of the radius user. enter up to 32 single-byte alphanumeric characters/symbols, with the following exception: ? terminal mac address input this address when you wish tocontrol access by using a supplicant mac address in addition toauthentication via user id and password. enter the address using the xxxx.xxxx.xxxx format. vlan specifies the vlan to assign to the user via dynamic vlan. input a vlan from 1 to 4094. ssid of connected device for users that are authenticated via a wireless ap, this specifies the ssid that can be used to connect. enter up to 32 single-byte alphanumeric characters/symbols, with the following exceptions: \[] recipient e-mail address for certificates specify the e-mail recipient addresses used when sending client certificates. input up to 256 single-byte alphanumeric characters and single-byte symbols. you cannot use symbols other than _-. and @ . period of certificate validity specifies the period of validity that is set when creating a client certificate. enter the date in yyyy/mm/dd format. dates from the current system date to 2037/12/31 can be entered for the period of validity.</div><div class="display_word">3.1. User settings Select an authentication function Select the authentication method used by the RADIUS user from the methods below. 802.1X MAC Web None When the authentication method isselected, the items that must be entered and the items that do not needto be entered for the selected authentication function will becomeclear. When using a Yamaha device as the authenticator, we recommend that you select an authentication function. When Not specified is selected, all items will become selectable. When using a non-Yamaha device as the authenticator, we recommend that you select Not specified . When changing the settings, it is not possible to select anything besides Not specified . User ID Specifies the user ID for the RADIUS user. Specify a text string from 3 to 32 characters. The characters that can be inputted depends on the type of authentication method. For PAP, EAP-MD5, EAP-TTLS, and PEAP: Single-byte alphanumeric characters/symbols, with the following exceptions: \[]"?space For EAP-TLS: Single-byte alphanumeric characters/symbols, with the following exceptions: \[]/:< >|"?space* You cannot set the name as DEFAULT . When using MAC authentication, input the MAC address for the user’s terminal. For the MAC address, use one of the following input formats according to the authenticator settings. XX:XX:XX:XX:XX:XX XX-XX-XX-XX-XX-XX XXXXXXXXXXXX When MAC authentication isselected for “Select an authentication function,” the MAC address thatwas entered will be automatically reflected in the “Password” and“Password (confirm)” fields. Password Specifies the password for the RADIUS user. Enter up to 32 single-byte alphanumeric characters/symbols, with the following exceptions: \[]? When using MAC authentication, input the MAC address for the user’s terminal. Password ( Confirm ) To confirm, enter the password once again that you entered in the “Password” field. Authentication method Select the authentication method used to authenticate the RADIUS user from the methods below. PAP PEAP, EAP-MD5, EAP-TTLS EAP-TLS Name Specifies the name of the RADIUS user. Enter up to 32 single-byte alphanumeric characters/symbols, with the following exception: ? Terminal MAC address Input this address when you wish tocontrol access by using a supplicant MAC address in addition toauthentication via user ID and password. Enter the address using the XXXX.XXXX.XXXX format. VLAN Specifies the VLAN to assign to the user via dynamic VLAN. Input a VLAN from 1 to 4094. SSID of connected device For users that are authenticated via a wireless AP, this specifies the SSID that can be used to connect. Enter up to 32 single-byte alphanumeric characters/symbols, with the following exceptions: \[] Recipient e-mail address for certificates Specify the e-mail recipient addresses used when sending client certificates. Input up to 256 single-byte alphanumeric characters and single-byte symbols. You cannot use symbols other than _-. and @ . Period of certificate validity Specifies the period of validity that is set when creating a client certificate. Enter the date in YYYY/MM/DD format. Dates from the current system date to 2037/12/31 can be entered for the period of validity.</div></div><div id="gui_en_detail_rds_user"><div class="search_title" docfname="gui_en_detail_rds_user" doctitle="User" link="#user_import">4. User settings import page</div><div class="search_word">4. user settings import page this page is for importing the radius user settings. enter the contents, and then press the "confirm" button. if there are no mistakes in the input content confirmation screen, press the "ok" button. the client certificates for users that were deleted during import will automatically be revoked.</div><div class="display_word">4. User settings import page This page is for importing the RADIUS user settings. Enter the contents, and then press the "Confirm" button. If there are no mistakes in the input content confirmation screen, press the "OK" button. The client certificates for users that were deleted during import will automatically be revoked.</div></div><div id="gui_en_detail_rds_user"><div class="search_title" docfname="gui_en_detail_rds_user" doctitle="User" link="#import_user_settings">4.1. Import user settings</div><div class="search_word">4.1. import user settings file to import select the csv file to import. issue a certificate select below whether to issue a client certificate after the import is completed. issue a certificate for users whose settings have been changed, and send e-mail issue a certificate for users whose settings have been changed do not issue a certificate</div><div class="display_word">4.1. Import user settings File to import Select the CSV file to import. Issue a certificate Select below whether to issue a client certificate after the import is completed. Issue a certificate for users whose settings have been changed, and send e-mail Issue a certificate for users whose settings have been changed Do not issue a certificate</div></div><div id="gui_en_detail_routing"><div class="search_title" docfname="gui_en_detail_routing" doctitle="Routing" link="#title-box">Routing</div><div class="search_word">routing</div><div class="display_word">Routing</div></div><div id="gui_en_detail_routing"><div class="search_title" docfname="gui_en_detail_routing" doctitle="Routing" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring the routing settings.</div><div class="display_word">1. Summary This page is for configuring the routing settings.</div></div><div id="gui_en_detail_routing"><div class="search_title" docfname="gui_en_detail_routing" doctitle="Routing" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for routing.</div><div class="display_word">2. Top page This is the top page for routing.</div></div><div id="gui_en_detail_routing"><div class="search_title" docfname="gui_en_detail_routing" doctitle="Routing" link="#routing_function_basic_settings">2.1. Routing function basic settings</div><div class="search_word">2.1. routing function basic settings the current settings for the routing function are shown. when you press the "setting" button, a page where you can change the routing function settings will appear.</div><div class="display_word">2.1. Routing function basic settings The current settings for the routing function are shown. When you press the "Setting" button, a page where you can change the routing function settings will appear.</div></div><div id="gui_en_detail_routing"><div class="search_title" docfname="gui_en_detail_routing" doctitle="Routing" link="#routing_table">2.2. Routing table</div><div class="search_word">2.2. routing table displays the routing table details. the table items are explained below. check box select the check box to delete static route information. enabled route for the route used in actual communications, enabled will be displayed. for the routes not used for actual communications, disabled will be displayed. kind displays one of the following route information types. static connected destination displays the destination network address for the route information. if the destination is a default gateway, default will be displayed. gateway displays the route information gateway. null is displayed for settings to discard packets. priority displays the administrative distance for route information. press the "new" button to display a page where you can create new settings for static route information. press the "setting" button to display a page where you can change the settings for the selected static route information. if you press the "delete" button, all static route information for which the check boxes are selected will be deleted. a check box and "settings" button is displayed for the static route information entry. up to 128 static route information entries can be displayed. when 128 static route information entries are displayed, the "new" button is disabled.</div><div class="display_word">2.2. Routing table Displays the routing table details. The table items are explained below. Check box Select the check box to delete static route information. Enabled route For the route used in actual communications, Enabled will be displayed. For the routes not used for actual communications, Disabled will be displayed. Kind Displays one of the following route information types. static connected Destination Displays the destination network address for the route information. If the destination is a default gateway, default will be displayed. Gateway Displays the route information gateway. Null is displayed for settings to discard packets. Priority Displays the administrative distance for route information. Press the "New" button to display a page where you can create new settings for static route information. Press the "Setting" button to display a page where you can change the settings for the selected static route information. If you press the "Delete" button, all static route information for which the check boxes are selected will be deleted. A check box and "Settings" button is displayed for the static route information entry. Up to 128 static route information entries can be displayed. When 128 static route information entries are displayed, the "New" button is disabled.</div></div><div id="gui_en_detail_routing"><div class="search_title" docfname="gui_en_detail_routing" doctitle="Routing" link="#basic">3. Routing function basic setting page</div><div class="search_word">3. routing function basic setting page in this page you can specify whether the routing function is used. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Routing function basic setting page In this page you can specify whether the routing function is used. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_routing"><div class="search_title" docfname="gui_en_detail_routing" doctitle="Routing" link="#routing_function_basic_setting_page">3.1. Routing function basic setting page</div><div class="search_word">3.1. routing function basic setting page routing function select the routing function from the following items. use routing function don’t use routing function</div><div class="display_word">3.1. Routing function basic setting page Routing function Select the routing function from the following items. Use routing function Don’t use routing function</div></div><div id="gui_en_detail_routing"><div class="search_title" docfname="gui_en_detail_routing" doctitle="Routing" link="#static">4. Static route information settings page</div><div class="search_word">4. static route information settings page this page is for configuring the static route information settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Static route information settings page This page is for configuring the static route information settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_routing"><div class="search_title" docfname="gui_en_detail_routing" doctitle="Routing" link="#static_route_information_settings">4.1. Static route information settings</div><div class="search_word">4.1. static route information settings destination network when configuring new settings select a destination network from the following networks. specifying a network address input the destination network address. default gateway when changing settings the destination network address is displayed. gateway select from one of the following gateways. specifying an ip address input the gateway ip address. discarding a packet without forwarding priority input the priority. the input range is 1 - 255.</div><div class="display_word">4.1. Static route information settings Destination network When configuring new settings Select a destination network from the following networks. Specifying a network address Input the destination network address. Default gateway When changing settings The destination network address is displayed. Gateway Select from one of the following gateways. Specifying an IP address Input the gateway IP address. Discarding a packet without forwarding Priority Input the priority. The input range is 1 - 255.</div></div><div id="gui_en_detail_storm"><div class="search_title" docfname="gui_en_detail_storm" doctitle="Storm" link="#title-box">Storm control</div><div class="search_word">storm control</div><div class="display_word">Storm control</div></div><div id="gui_en_detail_storm"><div class="search_title" docfname="gui_en_detail_storm" doctitle="Storm" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for changing the storm control settings. if the storm control is enabled, the load on the unitcan be reduced by discarding specific frames received that exceedbandwidth threshold values.</div><div class="display_word">1. Summary This page is for changing the storm control settings. If the storm control is enabled, the load on the unitcan be reduced by discarding specific frames received that exceedbandwidth threshold values.</div></div><div id="gui_en_detail_storm"><div class="search_title" docfname="gui_en_detail_storm" doctitle="Storm" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the storm control settings.</div><div class="display_word">2. Top page This is the top page for the storm control settings.</div></div><div id="gui_en_detail_storm"><div class="search_title" docfname="gui_en_detail_storm" doctitle="Storm" link="#storm_control_settings">2.1. Storm control settings</div><div class="search_word">2.1. storm control settings the current settings for the storm control are shown for each interface. the table items are explained below. check box select the check box for bulk settings or to initialize the settings. port displays the interface name. target frame displays the target frames for storm control. upper limit for bandwidth percent displays the upper limit for the bandwidth percentage. frames received that exceed the upper limit value are discarded. press the "setting" button to display the page where you can change the settings of the selected interface. if you press the "specify all" button, the settings can be changed for all interfaces whose check box is selected. the default settings will be applied to the settings on the storm control settings page. if you press the "return to defaults" button, the settings will be initialized on all interfaces whose check boxes are selected. the storm control is disabled for all ports by default.</div><div class="display_word">2.1. Storm control settings The current settings for the storm control are shown for each interface. The table items are explained below. Check box Select the check box for bulk settings or to initialize the settings. Port Displays the interface name. Target frame Displays the target frames for storm control. Upper limit for bandwidth percent Displays the upper limit for the bandwidth percentage. Frames received that exceed the upper limit value are discarded. Press the "Setting" button to display the page where you can change the settings of the selected interface. If you press the "Specify all" button, the settings can be changed for all interfaces whose check box is selected. The default settings will be applied to the settings on the storm control settings page. If you press the "Return to defaults" button, the settings will be initialized on all interfaces whose check boxes are selected. The storm control is disabled for all ports by default.</div></div><div id="gui_en_detail_storm"><div class="search_title" docfname="gui_en_detail_storm" doctitle="Storm" link="#storm">3. Storm control settings page</div><div class="search_word">3. storm control settings page this page is for storm control settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Storm control settings page This page is for storm control settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_storm"><div class="search_title" docfname="gui_en_detail_storm" doctitle="Storm" link="#interface_settings">3.1. Interface settings</div><div class="search_word">3.1. interface settings port displays the name of the interface for which settings will be made. storm control select the operation for the storm control from the following options. disable enable target frame broadcast frame enables broadcast storm control. multicast frame enables multicast storm control. unicast frame enables control for unicast frames sent from an unknown address. upper limit for bandwidth percent specifies the upper limit value for the bandwidth percentage. upper limit values can be specified to two decimal places. frames received that exceed the upper limit value are discarded. the same upper limit value is applied to all applicable frames.</div><div class="display_word">3.1. Interface settings Port Displays the name of the interface for which settings will be made. Storm control Select the operation for the storm control from the following options. Disable Enable Target frame Broadcast frame Enables broadcast storm control. Multicast frame Enables multicast storm control. Unicast frame Enables control for unicast frames sent from an unknown address. Upper limit for bandwidth percent Specifies the upper limit value for the bandwidth percentage. Upper limit values can be specified to two decimal places. Frames received that exceed the upper limit value are discarded. The same upper limit value is applied to all applicable frames.</div></div><div id="gui_en_detail_stp"><div class="search_title" docfname="gui_en_detail_stp" doctitle="Spanning" link="#title-box">Spanning tree</div><div class="search_word">spanning tree</div><div class="display_word">Spanning tree</div></div><div id="gui_en_detail_stp"><div class="search_title" docfname="gui_en_detail_stp" doctitle="Spanning" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring the spanning tree. if you want to use the spanning tree function, you needto enable both the system settings and the interface settings. if the spanning tree is disabled in the system settings, the spanning tree does not work on all interfaces regardless of theinterface settings.</div><div class="display_word">1. Summary This page is for configuring the spanning tree. If you want to use the spanning tree function, you needto enable both the system settings and the interface settings. If the spanning tree is disabled in the system settings, the spanning tree does not work on all interfaces regardless of theinterface settings.</div></div><div id="gui_en_detail_stp"><div class="search_title" docfname="gui_en_detail_stp" doctitle="Spanning" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the spanning tree.</div><div class="display_word">2. Top page This is the top page for the spanning tree.</div></div><div id="gui_en_detail_stp"><div class="search_title" docfname="gui_en_detail_stp" doctitle="Spanning" link="#system_settings">2.1. System settings</div><div class="search_word">2.1. system settings displays the spanning tree setting for the system. press the "setting" button to display the page for configuring the system settings.</div><div class="display_word">2.1. System settings Displays the spanning tree setting for the system. Press the "Setting" button to display the page for configuring the system settings.</div></div><div id="gui_en_detail_stp"><div class="search_title" docfname="gui_en_detail_stp" doctitle="Spanning" link="#interface_settings">2.2. Interface settings</div><div class="search_word">2.2. interface settings displays the spanning tree setting for each interface. the table items are explained below. i/f displays the interface name. spanning tree function displays whether the spanning tree function is enabled or not on the interface. press the "setting" button to display the page where you can change the settings of the selected interface. if you press the "specify all" button, the settings can be changed for all interfaces whose check box is selected. if you press the "return to defaults" button, the settings will be initialized on all interfaces whose check boxes are selected.</div><div class="display_word">2.2. Interface settings Displays the spanning tree setting for each interface. The table items are explained below. I/F Displays the interface name. Spanning tree function Displays whether the spanning tree function is enabled or not on the interface. Press the "Setting" button to display the page where you can change the settings of the selected interface. If you press the "Specify all" button, the settings can be changed for all interfaces whose check box is selected. If you press the "Return to defaults" button, the settings will be initialized on all interfaces whose check boxes are selected.</div></div><div id="gui_en_detail_stp"><div class="search_title" docfname="gui_en_detail_stp" doctitle="Spanning" link="#system">3. System settings page</div><div class="search_word">3. system settings page this page is for configuring the spanning tree for the system. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. System settings page This page is for configuring the spanning tree for the system. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_stp"><div class="search_title" docfname="gui_en_detail_stp" doctitle="Spanning" link="#system_settings_2">3.1. System settings</div><div class="search_word">3.1. system settings spanning tree function select the spanning tree function setting from the following items. use don’t use</div><div class="display_word">3.1. System settings Spanning tree function Select the spanning tree function setting from the following items. Use Don’t use</div></div><div id="gui_en_detail_stp"><div class="search_title" docfname="gui_en_detail_stp" doctitle="Spanning" link="#interface">4. Interface settings page</div><div class="search_word">4. interface settings page this page is for configuring the spanning tree for the interface. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Interface settings page This page is for configuring the spanning tree for the interface. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_stp"><div class="search_title" docfname="gui_en_detail_stp" doctitle="Spanning" link="#interface_settings_2">4.1. Interface settings</div><div class="search_word">4.1. interface settings applicable interface displays the name of the interface whose settings are to be changed. spanning tree function select the spanning tree function setting from the following items. use don’t use</div><div class="display_word">4.1. Interface settings Applicable interface Displays the name of the interface whose settings are to be changed. Spanning tree function Select the spanning tree function setting from the following items. Use Don’t use</div></div><div id="gui_en_detail_tagvlan"><div class="search_title" docfname="gui_en_detail_tagvlan" doctitle="Tag" link="#title-box">Tag VLAN</div><div class="search_word">tag vlan</div><div class="display_word">Tag VLAN</div></div><div id="gui_en_detail_tagvlan"><div class="search_title" docfname="gui_en_detail_tagvlan" doctitle="Tag" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can make settings for tagged vlans.</div><div class="display_word">1. Summary In this page you can make settings for tagged VLANs.</div></div><div id="gui_en_detail_tagvlan"><div class="search_title" docfname="gui_en_detail_tagvlan" doctitle="Tag" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for tagged vlans.</div><div class="display_word">2. Top page This is the top page for tagged VLANs.</div></div><div id="gui_en_detail_tagvlan"><div class="search_title" docfname="gui_en_detail_tagvlan" doctitle="Tag" link="#tag_vlan_settings">2.1. Tag VLAN settings</div><div class="search_word">2.1. tag vlan settings the various settings for tagged vlans are shown for each lan/sfp port and logical interface "frame types that can be received" isdisplayed according to the operating mode and the vlan settings. (thisitem cannot be set in the settings page.) press the "setting" button to access a page where you can change the settings for the tagged vlan of the selected interface if you press the "specify all" button, thesettings can be changed for all lan/sfp ports and logical interfaceswhose check box contains a check mark if you press the "return to defaults" button,the settings will be initialized for all lan/sfp ports and logicalinterfaces whose check box contains a check mark. default settings for a tagged vlan are as follows operating mode: access assigned vlan: default vlan (vlan id == 1) settings for the lan/sfp port assigned to a private vlan cannot be changed settings for the lan/sfp port assigned to a voice vlan cannot be changed if the operation mode is "trunk," both the native vlan and the trunk vlan are shown as assigned vlans.</div><div class="display_word">2.1. Tag VLAN settings The various settings for tagged VLANs are shown for each LAN/SFP port and logical interface "Frame types that can be received" isdisplayed according to the operating mode and the VLAN settings. (Thisitem cannot be set in the settings page.) Press the "Setting" button to access a page where you can change the settings for the tagged VLAN of the selected interface If you press the "Specify all" button, thesettings can be changed for all LAN/SFP ports and logical interfaceswhose check box contains a check mark If you press the "Return to defaults" button,the settings will be initialized for all LAN/SFP ports and logicalinterfaces whose check box contains a check mark. Default settings for a tagged VLAN are as follows Operating mode: Access Assigned VLAN: Default VLAN (VLAN ID == 1) Settings for the LAN/SFP port assigned to a private VLAN cannot be changed Settings for the LAN/SFP port assigned to a voice VLAN cannot be changed If the operation mode is "Trunk," both the native VLAN and the trunk VLAN are shown as assigned VLANs.</div></div><div id="gui_en_detail_tagvlan"><div class="search_title" docfname="gui_en_detail_tagvlan" doctitle="Tag" link="#tagvlan_config">3. Tagged VLAN settings page</div><div class="search_word">3. tagged vlan settings page in this page you can make various settings related to tagged vlans. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Tagged VLAN settings page In this page you can make various settings related to tagged VLANs. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_tagvlan"><div class="search_title" docfname="gui_en_detail_tagvlan" doctitle="Tag" link="#tag_vlan_settings_2">3.1. Tag VLAN settings</div><div class="search_word">3.1. tag vlan settings port the lan/sfp port or logical interface for which settings are made is shown operation mode access the corresponding port is specified as the access (untagged) port trunk the corresponding port is specified as the trunk (tagged) port accessvlan this item is shown only if the operating mode is "access". from the list, select the access port’s assigned vlan however, the following cannot be selected as access vlan. privatevlan voicevlan vlan for which frame forwarding is invalid nativevlan this item is shown only if the operating mode is "trunk". from the list, select the assignment-destination vlan (native vlan) for untagged frames received from the trunk port. however, the following cannot be selected as native vlan. vlan selected as trunk vlan privatevlan voicevlan vlan for which frame forwarding is invalid trunkvlan this item is shown only if the operating mode is "trunk". specify the assignment-destination vlan (trunk vlan) for tagged frames received at the trunk port. when you press the "select" button, a list of the selectable vlan ids appears in a separate window however, the following cannot be selected as trunk vlan. vlan selected as native vlan privatevlan voicevlan vlan for which frame forwarding is invalid place a check mark in the check box of the vlan id that you want to specify, and press the "ok" button ingress filter select the ingress filter from the following items. this item is shown only if the operating mode is "trunk." enabled ( receive only if the vlan id of the incoming frame is the same as the associated vlan ) disabled ( receive all frames )</div><div class="display_word">3.1. Tag VLAN settings Port The LAN/SFP port or logical interface for which settings are made is shown Operation mode Access The corresponding port is specified as the access (untagged) port Trunk The corresponding port is specified as the trunk (tagged) port AccessVLAN This item is shown only if the operating mode is "Access". From the list, select the access port’s assigned VLAN However, the following cannot be selected as access VLAN. PrivateVLAN VoiceVLAN VLAN for which frame forwarding is invalid NativeVLAN This item is shown only if the operating mode is "Trunk". From the list, select the assignment-destination VLAN (native VLAN) for untagged frames received from the trunk port. However, the following cannot be selected as native VLAN. VLAN selected as trunk VLAN PrivateVLAN VoiceVLAN VLAN for which frame forwarding is invalid TrunkVLAN This item is shown only if the operating mode is "Trunk". Specify the assignment-destination VLAN (trunk VLAN) for tagged frames received at the trunk port. When you press the "Select" button, a list of the selectable VLAN IDs appears in a separate window However, the following cannot be selected as trunk VLAN. VLAN selected as native VLAN PrivateVLAN VoiceVLAN VLAN for which frame forwarding is invalid Place a check mark in the check box of the VLAN ID that you want to specify, and press the "OK" button Ingress filter Select the ingress filter from the following items. This item is shown only if the operating mode is "Trunk." Enabled ( Receive only if the VLAN ID of the incoming frame is the same as the associated VLAN ) Disabled ( Receive all frames )</div></div><div id="gui_en_detail_txqmon"><div class="search_title" docfname="gui_en_detail_txqmon" doctitle="Tx" link="#title-box">Tx queue usage monitoring</div><div class="search_word">tx queue usage monitoring</div><div class="display_word">Tx queue usage monitoring</div></div><div id="gui_en_detail_txqmon"><div class="search_title" docfname="gui_en_detail_txqmon" doctitle="Tx" link="#summary">1. Summary</div><div class="search_word">1. summary this page is for configuring the tx queue usage monitoring function. if you disable this function, notifications about the tx queue are not sent in syslog and mail notifications.</div><div class="display_word">1. Summary This page is for configuring the tx queue usage monitoring function. If you disable this function, notifications about the tx queue are not sent in SYSLOG and mail notifications.</div></div><div id="gui_en_detail_txqmon"><div class="search_title" docfname="gui_en_detail_txqmon" doctitle="Tx" link="#top">2. Top page</div><div class="search_word">2. top page this is the top page for the tx queue usage monitoring.</div><div class="display_word">2. Top page This is the top page for the tx queue usage monitoring.</div></div><div id="gui_en_detail_txqmon"><div class="search_title" docfname="gui_en_detail_txqmon" doctitle="Tx" link="#system_settings">2.1. System settings</div><div class="search_word">2.1. system settings displays the configuration of the tx queue usage monitoring function for the entire system. press the "setting" button to display the page for configuring the system.</div><div class="display_word">2.1. System settings Displays the configuration of the tx queue usage monitoring function for the entire system. Press the "Setting" button to display the page for configuring the system.</div></div><div id="gui_en_detail_txqmon"><div class="search_title" docfname="gui_en_detail_txqmon" doctitle="Tx" link="#interface_settings">2.2. Interface settings</div><div class="search_word">2.2. interface settings displays the configuration of the tx queue usage monitoring function for each port. the table items are explained below. port displays the port name. tx queue usage monitoring displays the configuration of the tx queue usage monitoring function for the target port. press the "setting" button to display the page for configuring the selected port. press the "specify all" button to configure the settings for all ports with the check box selected. press the "return to defaults" button to initialize the settings for all ports with the check box selected.</div><div class="display_word">2.2. Interface settings Displays the configuration of the tx queue usage monitoring function for each port. The table items are explained below. Port Displays the port name. Tx queue usage monitoring Displays the configuration of the tx queue usage monitoring function for the target port. Press the "Setting" button to display the page for configuring the selected port. Press the "Specify all" button to configure the settings for all ports with the check box selected. Press the "Return to defaults" button to initialize the settings for all ports with the check box selected.</div></div><div id="gui_en_detail_txqmon"><div class="search_title" docfname="gui_en_detail_txqmon" doctitle="Tx" link="#system_setting">3. System settings page</div><div class="search_word">3. system settings page this page is for configuring the tx queue usage monitoring function for the system. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. System settings page This page is for configuring the tx queue usage monitoring function for the system. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_txqmon"><div class="search_title" docfname="gui_en_detail_txqmon" doctitle="Tx" link="#system_settings_2">3.1. System settings</div><div class="search_word">3.1. system settings tx queue usage monitoring for the entire system specify whether to enable or disable the tx queue usage monitoring function for the entire system. if this setting is disabled, notifications about the tx queue are not sent. even if the entire system setting isenabled, notifications are not sent about the tx queue of ports whoseindividual setting is disabled.</div><div class="display_word">3.1. System settings Tx queue usage monitoring for the entire system Specify whether to enable or disable the tx queue usage monitoring function for the entire system. If this setting is disabled, notifications about the tx queue are not sent. Even if the entire system setting isenabled, notifications are not sent about the tx queue of ports whoseindividual setting is disabled.</div></div><div id="gui_en_detail_txqmon"><div class="search_title" docfname="gui_en_detail_txqmon" doctitle="Tx" link="#interface_setting">4. Interface settings page</div><div class="search_word">4. interface settings page this page is for configuring the tx queue usage monitoring function for the interface. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Interface settings page This page is for configuring the tx queue usage monitoring function for the interface. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_txqmon"><div class="search_title" docfname="gui_en_detail_txqmon" doctitle="Tx" link="#interface_settings_2">4.1. Interface settings</div><div class="search_word">4.1. interface settings port displays the port name to configure the settings. tx queue usage monitoring specify whether to enable or disable the tx queue usage monitoring function for the target port. if this setting is disabled, notifications about the tx queue of the target port are not sent. even if the individual port setting isenabled, notifications are not sent about the tx queue if the entiresystem setting is disabled.</div><div class="display_word">4.1. Interface settings Port Displays the port name to configure the settings. Tx queue usage monitoring Specify whether to enable or disable the tx queue usage monitoring function for the target port. If this setting is disabled, notifications about the tx queue of the target port are not sent. Even if the individual port setting isenabled, notifications are not sent about the tx queue if the entiresystem setting is disabled.</div></div><div id="gui_en_detail_vlan"><div class="search_title" docfname="gui_en_detail_vlan" doctitle="Create" link="#title-box">Create VLAN</div><div class="search_word">create vlan</div><div class="display_word">Create VLAN</div></div><div id="gui_en_detail_vlan"><div class="search_title" docfname="gui_en_detail_vlan" doctitle="Create" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can create or delete vlans, and change the ip address.</div><div class="display_word">1. Summary In this page you can create or delete VLANs, and change the IP address.</div></div><div id="gui_en_detail_vlan"><div class="search_title" docfname="gui_en_detail_vlan" doctitle="Create" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for creating a vlan.</div><div class="display_word">2. Top page This is the top page for creating a VLAN.</div></div><div id="gui_en_detail_vlan"><div class="search_title" docfname="gui_en_detail_vlan" doctitle="Create" link="#vlan_list">2.1. VLAN list</div><div class="search_word">2.1. vlan list information for the defined vlans is displayed ipv4 primary address is displayed in bold. a maximum of 20 items can be displayed for one page. press or or enter a numeric value to switch between pages. you can press the sort switch to sort by each item. press the "new" button to access a page where you can create a new vlan press the "setting" button to access a page where you can change the settings of the selected vlan if you press the "delete" button, all vlans whose check box has a check mark will be deleted the following vlan cannot be deleted default vlan ( vlan id = 1 ) private vlan up to 256 vlans can be created including the default vlan (vlan id == 1).</div><div class="display_word">2.1. VLAN list Information for the defined VLANs is displayed IPv4 primary address is displayed in bold. A maximum of 20 items can be displayed for one page. Press or or enter a numeric value to switch between pages. You can press the sort switch to sort by each item. Press the "New" button to access a page where you can create a new VLAN Press the "Setting" button to access a page where you can change the settings of the selected VLAN If you press the "Delete" button, all VLANs whose check box has a check mark will be deleted The following VLAN cannot be deleted Default VLAN ( VLAN ID = 1 ) Private VLAN Up to 256 VLANs can be created including the default VLAN (VLAN ID == 1).</div></div><div id="gui_en_detail_vlan"><div class="search_title" docfname="gui_en_detail_vlan" doctitle="Create" link="#vlan_config">3. VLAN settings page</div><div class="search_word">3. vlan settings page in this page you can create a new vlan or edit the settings of an already-defined vlan. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. VLAN settings page In this page you can create a new VLAN or edit the settings of an already-defined VLAN. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_vlan"><div class="search_title" docfname="gui_en_detail_vlan" doctitle="Create" link="#vlan_settings">3.1. VLAN settings</div><div class="search_word">3.1. vlan settings vlan id to create a new vlan, enter the desired vlan id within the valid range (2—​4094) the smallest id of the unregistered vlan ids is entered as the default value if an already-registered vlan id is entered, it is handled as a change in settings when changing the settings, it is not possible to change the vlan id name specify the name of the vlan using up to 32 single-byte alphanumeric characters and symbols. the default vlan (vlan id == 1) cannot be renamed a space and "?" cannot be used in the name of the vlan. frame transmission select frame forwarding from the following items. enable frame transmission disable frame transmission frame forwarding cannot be disabled for the default vlan (vlan id == 1) ipv4 address for ipv4 addresses, you can specify one primary address and up to 4 secondary addresses for each vlan. you can set up to 8 of these addresses on the entire system. you can set this item only for vlans with frame forwarding enabled. set each address as follows. primary address select the ip address setting from the following. not set obtain automatically using dhcp selecting the check box for "setting the link local address when auto-acquire does not work" will enable the auto ip function. the auto ip function can be enabled for only one vlan. you cannot select this item if the stack port is set to use auto ip. you can specify a host name to notify the dhcp server. specify a fixed ip address enter the ip address and subnet mask you can set description or note about the ip address as a label. if you select obtain automatically using dhcp or specify a fixed ip address , the various server configurations are changed for the vlan that you configure as follows. you can access the http server and the telnet server from the vlan interface. (to enable access to the ssh server and the tftp server, you need additional configurations.) no changes are made to the configuration of a server that already has 8 vlan interfaces registered. secondary address enter the following settings in the table. address enter the ip address and subnet mask label you can set description or note about the ip address as a label. press the icon to add a configuration form. press the "delete" button to delete a configuration form. ipv6 address for ipv6 addresses, you can specify up to 5 global addresses and one link-local address for each vlan. you can set up to 8 of these addresses on the entire system. the ipv6 address cannot be configured when the stack function is enabled. select whether the ipv6 address will be enabled or disabled from the following items. disable ipv6 enable ipv6 if you select enable ipv6 , the various server configurations are changed for the vlan that you configure as follows. you can access the http server and the telnet server from the vlan interface. (to enable access to the sshserver and the tftp server, you need additional configurations.) no changes are made to the configuration of a server that already has 8 vlan interfaces registered. set each address as follows. global address enter the following settings in the table. address select from the following items. obtain automatically using ra specify the address specify the address (dhcpv6-pd) obtain automatically using dhcpv6 if you select obtain automatically using ra , you can select whether to operate by dhcpv6 stateless. if you select specify the address , enter the following items. address enter the ip address and subnet mask if you select specify the address (dhcpv6-pd) , enter the following items. prefix name you can select from the prefix names set in dhcpv6-pd client function. low address set the lower part (rest) for the prefix obtained by dhcpv6-pd client. you need to specify "0" for the prefix part obtained by dhcpv6-pd client. enter the ip address and subnet mask configuration notes you cannot specify "obtain automatically using ra" and "obtain automatically using dhcpv6" in global address at the same time. press the icon to add a configuration form. press the "delete" button to delete a configuration form. link local address enter an ip address. dhcpv6-pd client function you can enable dhcpv6-pd client function and configure it to request prefix assignment. you can enable up to 8 interfaces for the entire device. enter a prefix name if you enable this function. prefix name is the name you attach to the prefix assigned by dhcpv6 client. you can use single-byte alphanumeric characters, dot (.), hyphen (-), and underline (_). you can set up to 32 characters. configuration notes you cannot configure settings when ipv6 is disabled. you cannot configure dhcpv6-pd client function when the stack function is enabled. dhcpv6-pd client function cannot be enabled when "obtain automatically using ra (enabled dhcpv6 stateless)" or "obtain automatically using dhcpv6"setting is included in global address. mtu specify the maximum packet length (mtu value) that the vlan interface can send. you can specify up to 7 different values other than the default value for the entire device. the input range of mtu is as follows. 68 - 9216 when ipv6 is disabled 1280 - 9216 when ipv6 is enabled when changing the mtu, adjust the mru aswell. if the received frame exceeds the mru size, the frame is discarded without being forwarded.</div><div class="display_word">3.1. VLAN settings VLAN ID To create a new VLAN, enter the desired VLAN ID within the valid range (2—​4094) The smallest ID of the unregistered VLAN IDs is entered as the default value If an already-registered VLAN ID is entered, it is handled as a change in settings When changing the settings, it is not possible to change the VLAN ID Name Specify the name of the VLAN using up to 32 single-byte alphanumeric characters and symbols. The default VLAN (VLAN ID == 1) cannot be renamed A space and "?" cannot be used in the name of the VLAN. Frame transmission Select frame forwarding from the following items. Enable frame transmission Disable frame transmission Frame forwarding cannot be disabled for the default VLAN (VLAN ID == 1) IPv4 address For IPv4 addresses, you can specify one primary address and up to 4 secondary addresses for each VLAN. You can set up to 8 of these addresses on the entire system. You can set this item only for VLANs with frame forwarding enabled. Set each address as follows. Primary address Select the IP address setting from the following. Not set Obtain automatically using DHCP Selecting the check box for "Setting the link local address when auto-acquire does not work" will enable the Auto IP function. The Auto IP function can be enabled for only one VLAN. You cannot select this item if the stack port is set to use Auto IP. You can specify a host name to notify the DHCP server. Specify a fixed IP address Enter the IP address and subnet mask You can set description or note about the IP address as a label. If you select Obtain automatically using DHCP or Specify a fixed IP address , the various server configurations are changed for the VLAN that you configure as follows. You can access the HTTP server and the TELNET server from the VLAN interface. (To enable access to the SSH server and the TFTP server, you need additional configurations.) No changes are made to the configuration of a server that already has 8 VLAN interfaces registered. Secondary address Enter the following settings in the table. Address Enter the IP address and subnet mask Label You can set description or note about the IP address as a label. Press the icon to add a configuration form. Press the "Delete" button to delete a configuration form. IPv6 address For IPv6 addresses, you can specify up to 5 global addresses and one link-local address for each VLAN. You can set up to 8 of these addresses on the entire system. The IPv6 address cannot be configured when the stack function is enabled. Select whether the IPv6 address will be enabled or disabled from the following items. Disable IPv6 Enable IPv6 If you select Enable IPv6 , the various server configurations are changed for the VLAN that you configure as follows. You can access the HTTP server and the TELNET server from the VLAN interface. (To enable access to the SSHserver and the TFTP server, you need additional configurations.) No changes are made to the configuration of a server that already has 8 VLAN interfaces registered. Set each address as follows. Global address Enter the following settings in the table. Address Select from the following items. Obtain automatically using RA Specify the address Specify the address (DHCPv6-PD) Obtain automatically using DHCPv6 If you select Obtain automatically using RA , you can select whether to operate by DHCPv6 stateless. If you select Specify the address , enter the following items. Address Enter the IP address and subnet mask If you select Specify the address (DHCPv6-PD) , enter the following items. Prefix name You can select from the prefix names set in DHCPv6-PD client function. Low address Set the lower part (rest) for the prefix obtained by DHCPv6-PD client. You need to specify "0" for the prefix part obtained by DHCPv6-PD client. Enter the IP address and subnet mask Configuration notes You cannot specify "Obtain automatically using RA" and "Obtain automatically using DHCPv6" in global address at the same time. Press the icon to add a configuration form. Press the "Delete" button to delete a configuration form. Link local address Enter an IP address. DHCPv6-PD client function You can enable DHCPv6-PD client function and configure it to request prefix assignment. You can enable up to 8 interfaces for the entire device. Enter a prefix name if you enable this function. Prefix name is the name you attach to the prefix assigned by DHCPv6 client. You can use single-byte alphanumeric characters, dot (.), hyphen (-), and underline (_). You can set up to 32 characters. Configuration notes You cannot configure settings when IPv6 is disabled. You cannot configure DHCPv6-PD client function when the stack function is enabled. DHCPv6-PD client function cannot be enabled when "Obtain automatically using RA (Enabled DHCPv6 stateless)" or "Obtain automatically using DHCPv6"setting is included in global address. MTU Specify the maximum packet length (MTU value) that the VLAN interface can send. You can specify up to 7 different values other than the default value for the entire device. The input range of MTU is as follows. 68 - 9216 when IPv6 is disabled 1280 - 9216 when IPv6 is enabled When changing the MTU, adjust the MRU aswell. If the received frame exceeds the MRU size, the frame is discarded without being forwarded.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#title-box">Device list</div><div class="search_word">device list</div><div class="display_word">Device list</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_summary">1. Summary</div><div class="search_word">1. summary in the device list you can view a list of the terminals and agentesmanaged in the lan map, and use the terminal db to centrally manageterminal information.</div><div class="display_word">1. Summary In the device list you can view a list of the terminals and agentesmanaged in the LAN map, and use the terminal DB to centrally manageterminal information.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_device">2. Terminal list</div><div class="search_word">2. terminal list the terminal list page is explained here.</div><div class="display_word">2. Terminal list The terminal list page is explained here.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_device_summary">2.1. Summary</div><div class="search_word">2.1. summary the terminal list page shows a list of the terminals that are managed by the lan map. you can use the list to check the time that a terminalwas detected or the time that it was lost. you can also edit terminalinformation in the list, or register it to the terminal db.</div><div class="display_word">2.1. Summary The terminal list page shows a list of the terminals that are managed by the LAN map. You can use the list to check the time that a terminalwas detected or the time that it was lost. You can also edit terminalinformation in the list, or register it to the terminal DB.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_device_button">2.2. About the buttons</div><div class="search_word">2.2. about the buttons "delete" button delete information of the selected lost terminal from the terminal list. "refresh display" button refresh the terminal list page. "save as csv" button save the terminal list as a csv file. "edit" button edit terminal information. edited information is registered in the terminal db.</div><div class="display_word">2.2. About the buttons "Delete" button Delete information of the selected lost terminal from the terminal list. "Refresh display" button Refresh the terminal list page. "Save as CSV" button Save the terminal list as a CSV file. "Edit" button Edit terminal information. Edited information is registered in the terminal DB.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_device_check">2.3. Checking terminal information</div><div class="search_word">2.3. checking terminal information in the list you can check the terminal information that is managed by the lan map. you can press each item’s sort switch to sort the list. the initial screen is sorted in order of route. lost terminals are shown highlighted in gray. the vlan id item shows (a) for an access vlan or (t) for a trunk vlan. if the port is being used as a port for a private vlan, the vlan id is not shown, and (p) is shown. if the port is being used as a port for a voice vlan, the vlan id is not shown, and (v) is shown.</div><div class="display_word">2.3. Checking terminal information In the list you can check the terminal information that is managed by the LAN map. You can press each item’s Sort switch to sort the list. The initial screen is sorted in order of route. Lost terminals are shown highlighted in gray. The VLAN ID item shows (A) for an access VLAN or (T) for a trunk VLAN. If the port is being used as a port for a private VLAN, the VLAN ID is not shown, and (P) is shown. If the port is being used as a port for a voice VLAN, the VLAN ID is not shown, and (V) is shown.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_device_edit">2.4. Editing terminal information and registering it to the terminal DB</div><div class="search_word">2.4. editing terminal information and registering it to the terminal db you can edit the information for the terminals that are managed bythe lan map. edited information is registered in the terminal db. pressthe "edit" button of the terminal information that you want to edit, and then edit the information. you can edit the following items. type select the type from the selection menu. * this is shown as an icon in the map page and multiple vlan page "connected device view". manufacturer enter the manufacturer name. enter up to 128 single-byte alphanumeric characters or single-byte symbols. model name enter the model name. enter up to 128 single-byte alphanumeric characters or single-byte symbols. device name enter the device name. enter up to 128 single-byte alphanumeric characters or single-byte symbols. os enter the os name. enter up to 128 single-byte alphanumeric characters or single-byte symbols. comment enter up to 128 single-byte alphanumeric characters or single-byte symbols. snapshot select whether the terminal is or is not included in monitoring for the snapshot function. * terminal information that has been registered can also be edited from the terminal db page.. note: when inputting " " " or " , " for parameters where text is inputted, the maximum number of allowable characters will be less than 128.</div><div class="display_word">2.4. Editing terminal information and registering it to the terminal DB You can edit the information for the terminals that are managed bythe LAN map. Edited information is registered in the terminal DB. Pressthe "Edit" button of the terminal information that you want to edit, and then edit the information. You can edit the following items. Type Select the type from the selection menu. * This is shown as an icon in the map page and multiple VLAN page "Connected device view". Manufacturer Enter the manufacturer name. Enter up to 128 single-byte alphanumeric characters or single-byte symbols. Model name Enter the model name. Enter up to 128 single-byte alphanumeric characters or single-byte symbols. Device name Enter the device name. Enter up to 128 single-byte alphanumeric characters or single-byte symbols. OS Enter the OS name. Enter up to 128 single-byte alphanumeric characters or single-byte symbols. Comment Enter up to 128 single-byte alphanumeric characters or single-byte symbols. Snapshot Select whether the terminal is or is not included in monitoring for the snapshot function. * Terminal information that has been registered can also be edited from the terminal DB page.. Note: When inputting " " " or " , " for parameters where text is inputted, the maximum number of allowable characters will be less than 128.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_device_delete">2.5. Deleting a lost terminal</div><div class="search_word">2.5. deleting a lost terminal you can delete information of a lost terminal from the terminal list. select the lost terminal information that you want to delete, and press the "delete" button . the lost terminal information that you selected is deleted.</div><div class="display_word">2.5. Deleting a lost terminal You can delete information of a lost terminal from the terminal list. Select the lost terminal information that you want to delete, and press the "Delete" button . The lost terminal information that you selected is deleted.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_device_csv">2.6. Saving a list to a CSV file</div><div class="search_word">2.6. saving a list to a csv file you can save the terminal list as a csv file. press the "save as csv" button . the terminal list is saved as a csv file.</div><div class="display_word">2.6. Saving a list to a CSV file You can save the terminal list as a CSV file. Press the "Save as CSV" button . The terminal list is saved as a CSV file.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_terminal_db">3. Terminal DB</div><div class="search_word">3. terminal db the terminal db page is explained here.</div><div class="display_word">3. Terminal DB The terminal DB page is explained here.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_terminal_db_summary">3.1. Summary</div><div class="search_word">3.1. summary the terminal db page shows a list of the terminals that areregistered in the terminal db. you can newly register, edit, or deleteterminal information, and import or export terminal db settings.</div><div class="display_word">3.1. Summary The terminal DB page shows a list of the terminals that areregistered in the terminal DB. You can newly register, edit, or deleteterminal information, and import or export terminal DB settings.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_terminal_db_button">3.2. About the buttons</div><div class="search_word">3.2. about the buttons "delete" button delete the selected terminal information from the terminal db. "register new" button newly register terminal information in the terminal db. "refresh display" button refresh the terminal db page display. "import" button apply the terminal db saved on the pc to the manager. "export" button save the terminal db as a csv file. "edit" button you can edit the terminal information that has been registered in the terminal db.</div><div class="display_word">3.2. About the buttons "Delete" button Delete the selected terminal information from the terminal DB. "Register new" button Newly register terminal information in the terminal DB. "Refresh display" button Refresh the terminal DB page display. "Import" button Apply the terminal DB saved on the PC to the manager. "Export" button Save the terminal DB as a CSV file. "Edit" button You can edit the terminal information that has been registered in the terminal DB.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_terminal_db_check">3.3. Checking terminal information</div><div class="search_word">3.3. checking terminal information you can identify the terminal db in the list. you can press each item’s sort switch to sort the list. the initial screen is sorted in order of mac address.</div><div class="display_word">3.3. Checking terminal information You can identify the terminal DB in the list. You can press each item’s Sort switch to sort the list. The initial screen is sorted in order of MAC address.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_terminal_db_add">3.4. Registering new terminal information</div><div class="search_word">3.4. registering new terminal information you can newly register terminal information in the terminal db. press the "register new" button , and enter the content to be registered. you can register the following items. mac address enter the mac address of the terminal. enter single-byte characters delimited by a ":" (example: 00:a0:de:00:00:00). type select the type from the selection menu. * this is shown as an icon in the map page and multiple vlan page "connected device view". manufacturer enter the manufacturer name. enter up to 128 single-byte alphanumeric characters or single-byte symbols. model name enter the model name. enter up to 128 single-byte alphanumeric characters or single-byte symbols. device name enter the device name. enter up to 128 single-byte alphanumeric characters or single-byte symbols. os enter the os name. enter up to 128 single-byte alphanumeric characters or single-byte symbols. comment enter up to 128 single-byte alphanumeric characters or single-byte symbols. snapshot select whether the terminal is or is not included in monitoring for the snapshot function.</div><div class="display_word">3.4. Registering new terminal information You can newly register terminal information in the terminal DB. Press the "Register new" button , and enter the content to be registered. You can register the following items. MAC address Enter the MAC address of the terminal. Enter single-byte characters delimited by a ":" (example: 00:a0:de:00:00:00). Type Select the type from the selection menu. * This is shown as an icon in the map page and multiple VLAN page "Connected device view". Manufacturer Enter the manufacturer name. Enter up to 128 single-byte alphanumeric characters or single-byte symbols. Model name Enter the model name. Enter up to 128 single-byte alphanumeric characters or single-byte symbols. Device name Enter the device name. Enter up to 128 single-byte alphanumeric characters or single-byte symbols. OS Enter the OS name. Enter up to 128 single-byte alphanumeric characters or single-byte symbols. Comment Enter up to 128 single-byte alphanumeric characters or single-byte symbols. Snapshot Select whether the terminal is or is not included in monitoring for the snapshot function.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_terminal_db_edit">3.5. Editing terminal information</div><div class="search_word">3.5. editing terminal information you can edit the terminal information that has been registered in the terminal db. press the "edit" button of the terminal information that you want to edit, and then edit the information. you can edit the following items. type select the type from the selection menu. * this is shown as an icon in the map page and multiple vlan page "connected device view". manufacturer enter the manufacturer name. enter up to 128 single-byte alphanumeric characters or single-byte symbols. model name enter the model name. enter up to 128 single-byte alphanumeric characters or single-byte symbols. device name enter the device name. enter up to 128 single-byte alphanumeric characters or single-byte symbols. os enter the os name. enter up to 128 single-byte alphanumeric characters or single-byte symbols. comment snapshot select whether the terminal is or is not included in monitoring for the snapshot function.</div><div class="display_word">3.5. Editing terminal information You can edit the terminal information that has been registered in the terminal DB. Press the "Edit" button of the terminal information that you want to edit, and then edit the information. You can edit the following items. Type Select the type from the selection menu. * This is shown as an icon in the map page and multiple VLAN page "Connected device view". Manufacturer Enter the manufacturer name. Enter up to 128 single-byte alphanumeric characters or single-byte symbols. Model name Enter the model name. Enter up to 128 single-byte alphanumeric characters or single-byte symbols. Device name Enter the device name. Enter up to 128 single-byte alphanumeric characters or single-byte symbols. OS Enter the OS name. Enter up to 128 single-byte alphanumeric characters or single-byte symbols. Comment Snapshot Select whether the terminal is or is not included in monitoring for the snapshot function.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_terminal_db_delete">3.6. Deleting terminal information</div><div class="search_word">3.6. deleting terminal information you can delete the selected terminal information from the terminaldb. select the terminal that you want to delete, and press the "delete" button . the selected terminal information is deleted.</div><div class="display_word">3.6. Deleting terminal information You can delete the selected terminal information from the terminalDB. Select the terminal that you want to delete, and press the "Delete" button . The selected terminal information is deleted.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_terminal_db_import">3.7. Importing a terminal DB</div><div class="search_word">3.7. importing a terminal db apply the terminal db saved on the pc to the manager. press the "import" button , and use the "select a file" button to select the terminal db. the selected terminal db is applied to the manager. when directly editing the terminal db, use no more than 128 single-byte alphanumeric or symbol characters for each item. a character string that includes multi-byte characters is detected as an empty character string, and a character string that exceeds 128characters is truncated at 128 characters.</div><div class="display_word">3.7. Importing a terminal DB Apply the terminal DB saved on the PC to the manager. Press the "Import" button , and use the "Select a file" button to select the terminal DB. The selected terminal DB is applied to the manager. When directly editing the terminal DB, use no more than 128 single-byte alphanumeric or symbol characters for each item. A character string that includes multi-byte characters is detected as an empty character string, and a character string that exceeds 128characters is truncated at 128 characters.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_terminal_db_export">3.8. Exporting a terminal DB</div><div class="search_word">3.8. exporting a terminal db you can save the terminal db as a csv file. press the "export" button . the terminal db is saved as a csv file.</div><div class="display_word">3.8. Exporting a terminal DB You can save the terminal DB as a CSV file. Press the "Export" button . The terminal DB is saved as a CSV file.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_yamaha">4. Agent list</div><div class="search_word">4. agent list the agent list page is explained here.</div><div class="display_word">4. Agent list The agent list page is explained here.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_yamaha_summary">4.1. Summary</div><div class="search_word">4.1. summary the agent list page shows a list of the agentes that are managed bythe lan map. you can use the list to check the time that a agent wasdetected or the time that it was lost. you can also change the settingsof a agent in the list.</div><div class="display_word">4.1. Summary The agent list page shows a list of the agentes that are managed bythe LAN map. You can use the list to check the time that a agent wasdetected or the time that it was lost. You can also change the settingsof a agent in the list.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_yamaha_button">4.2. About the buttons</div><div class="search_word">4.2. about the buttons "delete" button delete information of the selected lost agent from the agent list. "refresh display" button refresh the agent list page display. "save as csv" button save the agent list as a csv file. "settings" button make agent settings.</div><div class="display_word">4.2. About the buttons "Delete" button Delete information of the selected lost agent from the agent list. "Refresh display" button Refresh the agent list page display. "Save as CSV" button Save the agent list as a CSV file. "Settings" button Make agent settings.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_yamaha_check">4.3. Checking a agent</div><div class="search_word">4.3. checking a agent in the list you can check the agent information that is managed by the lan map. you can press each item’s sort switch to sort the list. the initial screen is sorted in order of route. lost agentes are shown highlighted in gray.</div><div class="display_word">4.3. Checking a agent In the list you can check the agent information that is managed by the LAN map. You can press each item’s Sort switch to sort the list. The initial screen is sorted in order of route. Lost agentes are shown highlighted in gray.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_yamaha_set">4.4. Making agent settings</div><div class="search_word">4.4. making agent settings you can edit the settings for the agentes that are managed by the lan map. settings can be changed on some yamaha switches. press the "settings" button of the agent whose settings you want to change, and then change the settings. you can set the following items. device name specify the device name of the agent. when "default device name" is selected, the default names that are predetermined for each device will be set. normally, this is textthat shows the model name and serial number. when "manual settings" is selected, the device name that wasinputted in the input box right afterwards will be set. input a devicename of up to 32 single-byte characters. the characters that can beinput will differ depending on the target agent. see "6-2. setting and maintaining switches" in "map" fordetails.</div><div class="display_word">4.4. Making agent settings You can edit the settings for the agentes that are managed by the LAN map. Settings can be changed on some Yamaha switches. Press the "Settings" button of the agent whose settings you want to change, and then change the settings. You can set the following items. Device name Specify the device name of the agent. When "Default device name" is selected, the default names that are predetermined for each device will be set. Normally, this is textthat shows the model name and serial number. When "Manual settings" is selected, the device name that wasinputted in the input box right afterwards will be set. Input a devicename of up to 32 single-byte characters. The characters that can beinput will differ depending on the target agent. See "6-2. Setting and maintaining switches" in "Map" fordetails.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_yamaha_delete">4.5. Deleting a lost agent</div><div class="search_word">4.5. deleting a lost agent you can delete information of a lost agent from the agent list.select the lost agent information that you want to delete, and press the "delete" button . the lost agent information that you selected is deleted.</div><div class="display_word">4.5. Deleting a lost agent You can delete information of a lost agent from the agent list.Select the lost agent information that you want to delete, and press the "Delete" button . The lost agent information that you selected is deleted.</div></div><div id="gui_en_lan_map_device_list"><div class="search_title" docfname="gui_en_lan_map_device_list" doctitle="Device" link="#device_list_yamaha_csv">4.6. Saving a list to a CSV file</div><div class="search_word">4.6. saving a list to a csv file you can save the agent list as a csv file. press the "save as csv" button . the agent list is saved as a csv file.</div><div class="display_word">4.6. Saving a list to a CSV file You can save the agent list as a CSV file. Press the "Save as CSV" button . The agent list is saved as a CSV file.</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#title-box">Map</div><div class="search_word">map</div><div class="display_word">Map</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_summary">1. Summary</div><div class="search_word">1. summary this visualizes the network status. you can check the connectionstatus of the devices, and change the settings of a yamaha switch oryamaha wireless ap.</div><div class="display_word">1. Summary This visualizes the network status. You can check the connectionstatus of the devices, and change the settings of a Yamaha switch orYamaha wireless AP.</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_function">2. Structure of the map page</div><div class="search_word">2. structure of the map page the map page provides a "tree view," "device detail and settingsview," and "connected devices view" to show the state of the network.</div><div class="display_word">2. Structure of the map page The map page provides a "Tree view," "Device detail and settingsview," and "Connected devices view" to show the state of the network.</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_tree">2.1. Tree view</div><div class="search_word">2.1. tree view the agent topology starting at the manager is shown in the lowerleft of the screen. network devices of other manufacturers are notshown. in the "tree view," press the "devices" icon to see device information in the "device details and settings view" and "connected devices view."</div><div class="display_word">2.1. Tree view The agent topology starting at the manager is shown in the lowerleft of the screen. Network devices of other manufacturers are notshown. In the "Tree view," press the "Devices" icon to see device information in the "Device details and settings view" and "Connected devices view."</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_detail">2.2. Device details and settings view</div><div class="search_word">2.2. device details and settings view detailed information and device detail images for the manager oragent selected in the "tree view" are shown in the upper part of thescreen.</div><div class="display_word">2.2. Device details and settings view Detailed information and device detail images for the manager oragent selected in the "Tree view" are shown in the upper part of thescreen.</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_list">2.3. Connected devices view</div><div class="search_word">2.3. connected devices view devices that are connected to the manager or agent selected inthe "tree view" are shown in the lower right of the screen. if "devicemanagement" is not enabled in "lan map settings," equipment information(e.g., pc or mobile devices) is not shown. acquisition date and time this is the time at which information was last obtained for equipment that is connected to the manager or agent selected in the"tree view." this is not shown if "device management" is not enabled in"lan map settings." acquire button this obtains information for terminal that is connected tothe manager or agent selected in the "tree view." this is not shown if"device management" is not enabled in "lan map settings." select page page numbers are shown for the list of currently-displayed terminal. press or or enter a numeric value to move between pages. show all button all items of device information are shown in the list.while all are displayed, press this again to return to the previousdisplay. list information is listed for equipment that is connected tothe manager or agent selected in the "tree view." you can press eachitem’s sort switch to sort the list. the initial screen is sorted in order of port. the vlan id item shows (a) for an access vlan or (t) for a trunk vlan. if the port is being used as a port for a private vlan, the vlan id is not shown, and (p) is shown. if the port is being used as a port for a voice vlan, the vlan id is not shown, and (v) is shown.</div><div class="display_word">2.3. Connected devices view Devices that are connected to the manager or agent selected inthe "Tree view" are shown in the lower right of the screen. If "Devicemanagement" is not enabled in "LAN map settings," equipment information(e.g., PC or mobile devices) is not shown. Acquisition date and time This is the time at which information was last obtained for equipment that is connected to the manager or agent selected in the"Tree view." This is not shown if "Device management" is not enabled in"LAN map settings." Acquire button This obtains information for terminal that is connected tothe manager or agent selected in the "Tree view." This is not shown if"Device management" is not enabled in "LAN map settings." Select page Page numbers are shown for the list of currently-displayed terminal. Press or or enter a numeric value to move between pages. Show all button All items of device information are shown in the list.While all are displayed, press this again to return to the previousdisplay. List Information is listed for equipment that is connected tothe manager or agent selected in the "Tree view." You can press eachitem’s Sort switch to sort the list. The initial screen is sorted in order of port. The VLAN ID item shows (A) for an access VLAN or (T) for a trunk VLAN. If the port is being used as a port for a private VLAN, the VLAN ID is not shown, and (P) is shown. If the port is being used as a port for a voice VLAN, the VLAN ID is not shown, and (V) is shown.</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_watch">3. Checking the status of devices</div><div class="search_word">3. checking the status of devices in "device details and settings view" you can view detaileddevice information such as device name and mac address, and also checkthe port link status, power supply status, and wireless communicationstatus. device name mac address port link status power supply status wireless communication status for devices in a stack configuration, you will be able to switch stack id with the toggle button.</div><div class="display_word">3. Checking the status of devices In "Device details and settings view" you can view detaileddevice information such as device name and MAC address, and also checkthe port link status, power supply status, and wireless communicationstatus. Device name MAC address Port link status Power supply status Wireless communication status For devices in a stack configuration, you will be able to switch stack ID with the toggle button.</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_link">3.1. Checking the link status of ports</div><div class="search_word">3.1. checking the link status of ports in "device details and settings view," you can use the "port" icon display to check the link status of the port. if a agent is selected in the "tree view," you can press the "port" icon in the "device details and settings view" to see detailed port information. if a "port" icon shows an ↑, this indicates that the port is an uplink port. the "port" icon is shown as follows depending on the link status. for a lan port icon description link up (port speed 10gbase-t) link up (port speed 5gbase-t) link up (port speed 2.5gbase-t) link up (port speed 1000base-t) link up (port speed 100base-tx) link up (port speed 10base-t) error occurrence link down for an sfp port icon description link up (port speed 10gbe) link up (port speed 1gbe) error occurrence link down for an stack port icon description link up link down</div><div class="display_word">3.1. Checking the link status of ports In "Device details and settings view," you can use the "Port" icon display to check the link status of the port. If a agent is selected in the "Tree view," you can press the "Port" icon in the "Device details and settings view" to see detailed port information. If a "Port" icon shows an ↑, this indicates that the port is an uplink port. The "Port" icon is shown as follows depending on the link status. For a LAN port Icon Description Link up (port speed 10GBASE-T) Link up (port speed 5GBASE-T) Link up (port speed 2.5GBASE-T) Link up (port speed 1000BASE-T) Link up (port speed 100BASE-TX) Link up (port speed 10BASE-T) Error occurrence Link down For an SFP port Icon Description Link up (port speed 10GbE) Link up (port speed 1GbE) Error occurrence Link down For an Stack port Icon Description Link up Link down</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_poe">3.2. Checking the power supply status of a switch that supports PoE</div><div class="search_word">3.2. checking the power supply status of a switch that supports poe in the "tree view," press the "device" icon of a switch that supports poe, and in "device details and settings view," press the "power supply status" button to check the poe power supply status. the "port" icon is shown as follows depending on the power supply status. for the swx2322p series ,swx2310p series, swr2311p series, swx2221p-10nt, swx2220p series, swx2210p series, swx2200-8poe,swx2110p-8g icon description poe is being supplied (supply class0—​3) poe is being supplied (supply class4—​8) poe is not being supplied power supply stopped (error occurred) power supply stopped note: on the swx2200-8poe the power supply class is not displayed in the icon.</div><div class="display_word">3.2. Checking the power supply status of a switch that supports PoE In the "Tree view," press the "Device" icon of a switch that supports PoE, and in "Device details and settings view," press the "Power supply status" button to check the PoE power supply status. The "Port" icon is shown as follows depending on the power supply status. For the SWX2322P Series ,SWX2310P Series, SWR2311P Series, SWX2221P-10NT, SWX2220P Series, SWX2210P Series, SWX2200-8PoE,SWX2110P-8G Icon Description PoE is being supplied (supply Class0—​3) PoE is being supplied (supply Class4—​8) PoE is not being supplied Power supply stopped (error occurred) Power supply stopped Note: On the SWX2200-8PoE the power supply class is not displayed in the icon.</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#for_the_swx2100_10poe_and_swx2100_5poe">3.2.1. For the SWX2100-10PoE and SWX2100-5PoE</div><div class="search_word">3.2.1. for the swx2100-10poe and swx2100-5poe icon description poe is being supplied (supply class0—​4) poe is not being supplied power supply stopped (error occurred) power supply stopped</div><div class="display_word">3.2.1. For the SWX2100-10PoE and SWX2100-5PoE Icon Description PoE is being supplied (supply Class0—​4) PoE is not being supplied Power supply stopped (error occurred) Power supply stopped</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_wireless">3.3. Checking the wireless communication status of a wireless AP</div><div class="search_word">3.3. checking the wireless communication status of a wireless ap in the "tree view," press the "device" icon of a yamaha wireless ap, and in "device details and settings view," press the "wireless" icon to check the wireless communication status. the "wireless" icon is displayed when wireless communication is possible in that frequency band.</div><div class="display_word">3.3. Checking the wireless communication status of a wireless AP In the "Tree view," press the "Device" icon of a Yamaha wireless AP, and in "Device details and settings view," press the "Wireless" icon to check the wireless communication status. The "Wireless" icon is displayed when wireless communication is possible in that frequency band.</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_detect">4. Monitoring network errors</div><div class="search_word">4. monitoring network errors the lan map monitors the network and notifies you of errors. ifan error is detected on the network, a message is displayed below. notification area press the "notice" button to see the messages regarding the current network status. thenotification area is also shown automatically when a new message isadded. if there is a device for which an error was detected, a is shown beside the "device" icon of the tree view, and the device information of "connected device view" is highlighted in red. history area when you press the "history" button , the history of the notification messages is shown.</div><div class="display_word">4. Monitoring network errors The LAN map monitors the network and notifies you of errors. Ifan error is detected on the network, a message is displayed below. Notification area Press the "Notice" button to see the messages regarding the current network status. Thenotification area is also shown automatically when a new message isadded. If there is a device for which an error was detected, a is shown beside the "Device" icon of the Tree view, and the device information of "Connected device view" is highlighted in red. History area When you press the "History" button , the history of the notification messages is shown.</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_switchctl">4.1. Monitoring the operating status and errors of a switch</div><div class="search_word">4.1. monitoring the operating status and errors of a switch in the lan map, when the following operations or error aredetected, a message is displayed in the "notification area" or "historyarea." some messages are displayed in both the "notification area" andthe "history area," and some are displayed in only one. troubleshooting items notification area history area the fan of a yamaha switch is stopped ○ ○ the fan of a yamaha switch has recovered × ○ the fan speed of the yamaha switch has increased ○ ○ the fan speed of the yamaha switch has decreased × ○ the power supply voltage of the yamaha switch has exceeded the upper threshold ○ ○ a line surge has occurred in the power supply of the yamaha switch ○ ○ the temperature ( cpu, phy, sfp module, unit, mac, pse ) of the yamaha switch has exceeded the upper threshold ○ ○ the temperature of the yamaha switch has returned to normal × ○ a loop is occurring at ports of a yamaha switch ○ ○ optical rx level of the sfp port of the yamaha switch has reached an abnormal level ○ ○ optical rx level of the sfp port of the yamaha switch has returned to normal level × ○ transmission queue usage ratio for the port on the yamaha switch is high ○ ○ transmission queue usage ratio for the port on the yamaha switch has returned to normal × ○ the power being supplied from the yamaha switch has entered the guard band range × ○ power is no longer supplied from a port of a yamaha switch × ○ power has begun being supplied from the port of a yamaha switch (for each supply class). × ○ power supplied from a port of a yamaha switch has halted abnormally ○ ○ the power being supplied from a yamaha switch has exceeded the maximum power supply capacity ○ ○ an error occurred in the power supply of a yamaha switch ○ ○ the monitoring device is down ○ ○ the monitoring device is up × ○ the stack port has linked down ○ ○ the stack port has linked up × ○ duplication of l2ms managers has been detected ○ ○ duplication of l2ms managers has been resolved × ○ enable the event monitor function on "lan map settings" toperiodically acquire the current status of the monitoring target event(event information) for the agent. the monitoring target events and compatible agentes are as follows. monitoring target event compatible models changes in optical rx level of the sfp port swx2300 series, swx2310p series, swx2310 series, swr2311p-10g, swr2310 series,swx3100 series, swx3200 series, swx2320 series, swx2322p series, swx3220 series changes in usage ratio for the port transmission queue status notification for device monitoring changes in temperature and fan speed swx2310p series, swr2311p-10g, swx2310-52gt, swx3200 series, swx2320 series, swx2322p series, swx3220 series changes in power voltage swx3200-28gt/52gt normally, since a notification is sent to the manager whenever an event occurs on a agent, the agent event that occurs will be detectedeven if the event monitoring function is disabled. however, we recommend that the event monitoring function be enabled, in case the managercannot receive the notification for some reason.</div><div class="display_word">4.1. Monitoring the operating status and errors of a switch In the LAN map, when the following operations or error aredetected, a message is displayed in the "Notification area" or "Historyarea." Some messages are displayed in both the "Notification area" andthe "History area," and some are displayed in only one. Troubleshooting items Notification area History area The fan of a Yamaha switch is stopped ○ ○ The fan of a Yamaha switch has recovered × ○ The fan speed of the Yamaha switch has increased ○ ○ The fan speed of the Yamaha switch has decreased × ○ The power supply voltage of the Yamaha switch has exceeded the upper threshold ○ ○ A line surge has occurred in the power supply of the Yamaha switch ○ ○ The temperature ( CPU, PHY, SFP module, Unit, MAC, PSE ) of the Yamaha switch has exceeded the upper threshold ○ ○ The temperature of the Yamaha switch has returned to normal × ○ A loop is occurring at ports of a Yamaha switch ○ ○ Optical Rx level of the SFP port of the Yamaha switch has reached an abnormal level ○ ○ Optical Rx level of the SFP port of the Yamaha switch has returned to normal level × ○ Transmission queue usage ratio for the port on the Yamaha switch is high ○ ○ Transmission queue usage ratio for the port on the Yamaha switch has returned to normal × ○ The power being supplied from the Yamaha switch has entered the guard band range × ○ Power is no longer supplied from a port of a Yamaha switch × ○ Power has begun being supplied from the port of a Yamaha switch (for each Supply Class). × ○ Power supplied from a port of a Yamaha switch has halted abnormally ○ ○ The power being supplied from a Yamaha switch has exceeded the maximum power supply capacity ○ ○ An error occurred in the power supply of a Yamaha switch ○ ○ The monitoring device is DOWN ○ ○ The monitoring device is UP × ○ The stack port has linked down ○ ○ The stack port has linked up × ○ Duplication of L2MS managers has been detected ○ ○ Duplication of L2MS managers has been resolved × ○ Enable the event monitor function on "LAN map settings" toperiodically acquire the current status of the monitoring target event(event information) for the agent. The monitoring target events and compatible agentes are as follows. Monitoring target event Compatible models Changes in optical Rx level of the SFP port SWX2300 Series, SWX2310P Series, SWX2310 Series, SWR2311P-10G, SWR2310 Series,SWX3100 Series, SWX3200 Series, SWX2320 Series, SWX2322P Series, SWX3220 Series Changes in usage ratio for the port transmission queue Status notification for device monitoring Changes in temperature and FAN speed SWX2310P Series, SWR2311P-10G, SWX2310-52GT, SWX3200 Series, SWX2320 Series, SWX2322P Series, SWX3220 Series Changes in power voltage SWX3200-28GT/52GT Normally, since a notification is sent to the manager whenever an event occurs on a agent, the agent event that occurs will be detectedeven if the event monitoring function is disabled. However, we recommend that the event monitoring function be enabled, in case the managercannot receive the notification for some reason.</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_snapshot">4.2. Monitoring the network connection status</div><div class="search_word">4.2. monitoring the network connection status in order to monitor the network connection status, enable thesnapshot function using the procedure described "about the lanmap"-"2-4. using the snapshot function" in this help. the snapshot function compares the current network status withthe snapshot, and if there is a difference, determines that a networkerror has been detected. when you press the "snapshot" button , the snapshot management dialog box appears, allowing you to save, export, import, or delete snapshots. save save a snapshot. if "update network connection statusbefore saving" is enabled, the network connection status information isupdated before saving. export the agent snapshot and terminal snapshot are downloaded. import a snapshot saved on the pc is applied to the manager. use the "select a file" button to select a agent snapshot and a terminal snapshot. if you don’t select a terminal snapshot, the existing snapshot is deleted, and an emptyterminal snapshot is created. *if you use an edited snapshot, it might not work correctly. delete delete a snapshot. if the snapshot function is enabled, the agent is always theobject of warnings, but the terminal is the object of warnings if all of the following conditions are fulfilled. the snapshot function’s "include terminals in comparison" is enabled the snapshot function is set to "include in monitoring" on the terminal db if you want all terminals on the network to be excluded fromwarnings, disable the snapshot function’s "include terminals incomparison". if you want only a specific terminal to be excluded fromwarnings, enable the snapshot function’s "include terminals incomparison," and edit the terminal db settings so that the snapshotfunction of the terminal to be excluded from warnings is set to "don’tinclude in monitoring". in the case of a terminal that is excluded fromwarnings, it will not be determined that a network error has beendetected even if there is a difference between the connection status and the snapshot. the snapshot function allows you to check the following operating status and errors. some messages are displayed in both the"notification area" and the "history area," and some are displayed inonly one. troubleshooting items notification area history area an unregistered agent and terminal are connected ○ ○ there is a agent and terminal whose connection ports differ ○ ○ there is a agent and terminal that cannot be found ○ ○ there is a discrepancy between the states of the agent and terminal × ○ a snapshot has not been created ○ × creation of a snapshot has started × ○ creation of a snapshot has finished × ○ a snapshot is being created ○ × creation of a snapshot was interrupted × ○ creation of a snapshot failed × ○</div><div class="display_word">4.2. Monitoring the network connection status In order to monitor the network connection status, enable thesnapshot function using the procedure described "About the LANmap"-"2-4. Using the snapshot function" in this help. The snapshot function compares the current network status withthe snapshot, and if there is a difference, determines that a networkerror has been detected. When you press the "Snapshot" button , the snapshot management dialog box appears, allowing you to save, export, import, or delete snapshots. Save Save a snapshot. If "Update network connection statusbefore saving" is enabled, the network connection status information isupdated before saving. Export The agent snapshot and terminal snapshot are downloaded. Import A snapshot saved on the PC is applied to the manager. Use the "Select a file" button to select a agent snapshot and a terminal snapshot. If you don’t select a terminal snapshot, the existing snapshot is deleted, and an emptyterminal snapshot is created. *If you use an edited snapshot, it might not work correctly. Delete Delete a snapshot. If the snapshot function is enabled, the agent is always theobject of warnings, but the terminal is the object of warnings if all of the following conditions are fulfilled. The snapshot function’s "Include terminals in comparison" is enabled The snapshot function is set to "Include in monitoring" on the terminal DB If you want all terminals on the network to be excluded fromwarnings, disable the snapshot function’s "Include terminals incomparison". If you want only a specific terminal to be excluded fromwarnings, enable the snapshot function’s "Include terminals incomparison," and edit the terminal DB settings so that the snapshotfunction of the terminal to be excluded from warnings is set to "Don’tinclude in monitoring". In the case of a terminal that is excluded fromwarnings, it will not be determined that a network error has beendetected even if there is a difference between the connection status and the snapshot. The snapshot function allows you to check the following operating status and errors. Some messages are displayed in both the"Notification area" and the "History area," and some are displayed inonly one. Troubleshooting items Notification area History area An unregistered agent and terminal are connected ○ ○ There is a agent and terminal whose connection ports differ ○ ○ There is a agent and terminal that cannot be found ○ ○ There is a discrepancy between the states of the agent and terminal × ○ A snapshot has not been created ○ × Creation of a snapshot has started × ○ Creation of a snapshot has finished × ○ A snapshot is being created ○ × Creation of a snapshot was interrupted × ○ Creation of a snapshot failed × ○</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_search">5. Searching for a device</div><div class="search_word">5. searching for a device to search for a device, input the keywords in the search box and press the "search" button. all devices whose information matches the keywords will be shown in "connected devices view". the "device" icon for connected devices matching the keywords inputted in the tree view will be highlighted in blue-gray. to cancel the search, press the "x" button . devices are searched by comparing the keywords with the following device information. route ssid vlan id manufacturer device name comment mac address ip address model name os frequency pressing the "device" icon highlighted blue-gray in the tree view will highlight the devices found in the searchperformed in "connected devices view" in blue-gray. when the searchresults overlap with the red highlights due to error detection, blue-gray-colored results will be given priority. lowercase and capital letters are treated the same for keywords. you can use regular expressions in keywords. below is an example of regular expressions you can use in the lan map. syntax explanation a the character "a" abc the characters "abc" [abc] one character, either "a", "b" or "c" [a-c] one character between "a" and "c" [^abc] an arbitrary character that is neither "a", "b" or "c" . an arbitrary character a+ at least one "a" character a* at least zero "a" characters a? zero or one "a" character ^a a string that begins with "a" a$ a string that ends with "a" abc|def|ghi "abc", "def" or "ghi" a{2} two "a" characters (aa) a{2,} two or more "a" characters (aa, aaa, aaaa…​) a{2,3} two to three "a" characters (aa, aaa) \b word breaks, such as spaces \b any character besides \b \d an arbitrary number (same as [0-9]) \d any character besides numbers (same as [^0-9]) \s single breaking character \s any single character besides \s \w alphanumeric characters including underlines (same as [a-za-z0-9_]) \w any character besides \w</div><div class="display_word">5. Searching for a device To search for a device, input the keywords in the search box and press the "Search" button. All devices whose information matches the keywords will be shown in "Connected devices view". The "Device" icon for connected devices matching the keywords inputted in the tree view will be highlighted in blue-gray. To cancel the search, press the "X" button . Devices are searched by comparing the keywords with the following device information. Route SSID VLAN ID Manufacturer Device name Comment MAC address IP address Model name OS Frequency Pressing the "Device" icon highlighted blue-gray in the tree view will highlight the devices found in the searchperformed in "Connected devices view" in blue-gray. When the searchresults overlap with the red highlights due to error detection, blue-gray-colored results will be given priority. Lowercase and capital letters are treated the same for keywords. You can use regular expressions in keywords. Below is an example of regular expressions you can use in the LAN map. Syntax Explanation A The character "A" ABC The characters "ABC" [ABC] One character, either "A", "B" or "C" [A-C] One character between "A" and "C" [^ABC] An arbitrary character that is neither "A", "B" or "C" . An arbitrary character A+ At least one "A" character A* At least zero "A" characters A? Zero or one "A" character ^A A string that begins with "A" A$ A string that ends with "A" ABC|DEF|GHI "ABC", "DEF" or "GHI" A{2} Two "A" characters (AA) A{2,} Two or more "A" characters (AA, AAA, AAAA…​) A{2,3} Two to three "A" characters (AA, AAA) \b Word breaks, such as spaces \B Any character besides \b \d An arbitrary number (same as [0-9]) \D Any character besides numbers (same as [^0-9]) \s Single breaking character \S Any single character besides \s \w Alphanumeric characters including underlines (same as [A-Za-z0-9_]) \W Any character besides \w</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_setting">6. Setting and managing agentes</div><div class="search_word">6. setting and managing agentes you can set and manage agentes using the buttons that are shown in"device details and settings view." the buttons shown in "device details and settings view" will differ depending on the device that is selected in "tree view."</div><div class="display_word">6. Setting and managing agentes You can set and manage agentes using the buttons that are shown in"Device details and settings view." The buttons shown in "Device details and settings view" will differ depending on the device that is selected in "Tree view."</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_agent">6.1. Managing agentes</div><div class="search_word">6.1. managing agentes if in "tree view" you press the manager’s "device" icon , and in "device details and settings view" press the "agent management" button , the agent management settings dialog box appears, allowing you to view information for each device and set the ip address. the items that can be set and managed for each device are the following. note: the following settings can be made on the swx2110 series,swx2110p series, swx2210 series, swx2210p series, swx222x series, theswx2300 series, the swx2310 series, the swx2310p series, the swr2310series, the swr2311p series, the swx3100 series, the swx3200series,　swx2320 series, swx2322p series, swx3220 series, the wlx202, the wlx212, the wlx222, the wlx302, the wlx313, the wlx322, the wlx323, the wlx402 and the wlx413. ip address settings this configures the ip address. the ip address displayed are agentes at the time that the screen is displayed. the ip address prior to making the settings may be shown, depending on the timing. config save/restore/delete saves, restores or deletes the config. this can be used for bulk operations on multiple agentes as well. specification method this sets the method of specifying the switch. this can be configured on the swx2200 series as well.</div><div class="display_word">6.1. Managing agentes If in "Tree view" you press the manager’s "Device" icon , and in "Device details and settings view" press the "Agent management" button , the agent management settings dialog box appears, allowing you to view information for each device and set the IP address. The items that can be set and managed for each device are the following. Note: The following settings can be made on the SWX2110 Series,SWX2110P Series, SWX2210 Series, SWX2210P Series, SWX222x Series, theSWX2300 Series, the SWX2310 Series, the SWX2310P Series, the SWR2310Series, the SWR2311P Series, the SWX3100 Series, the SWX3200Series,　SWX2320 Series, SWX2322P Series, SWX3220 Series, the WLX202, the WLX212, the WLX222, the WLX302, the WLX313, the WLX322, the WLX323, the WLX402 and the WLX413. IP Address Settings This configures the IP address. The IP address displayed are agentes at the time that the screen is displayed. The IP address prior to making the settings may be shown, depending on the timing. CONFIG Save/Restore/Delete Saves, restores or deletes the CONFIG. This can be used for bulk operations on multiple agentes as well. Specification method This sets the method of specifying the switch. This can be configured on the SWX2200 Series as well.</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_switch">6.2. Setting and maintaining switches</div><div class="search_word">6.2. setting and maintaining switches in the "tree view," press the "device" icon of the yamahaswitch, and in the "device details and settings view," press the button(the name depends on the switch) to see a dialog box or setting screen. here you can make settings for the various functions of theswitch, and perform maintenance such as updating the firmware orrestarting. the items that can be set or viewed, and the maintenancefunctions that can be executed, will differ depending on the model. 【 for the swx2300, swx2310, swx2310p, swr2310, swr2311p, swx3100, swx3200, swx2320, swx2322p and swx3220 series 】 when you press the "open the gui" button , the web setting screen of the switch opens in another window. 【 for the swx222x series, swx2210 series, swx2210p series 】 press the "switch settings and maintenance" button to open the dialog box. device name specify the device name of the switch. when "default device name" is selected, the defaultnames that are predetermined for each device will be set. normally, this is text that shows the model name and serial number. when "manual settings" is selected, the devicename that was inputted in the input box right afterwards will be set.input a device name of up to 32 single-byte characters. you can only use single-byte alphanumeric characters and symbols. led mode this lets you configure the led mode settings. port mirroring this lets you configure the sniffer ports, monitor ports and monitoring direction. qos function this lets you specify whether qos is used. maintenance the following can be executed for a switch. reset the frame counter restart when you press the "open the gui" button , the web setting screen of the switch opens in another window. 【 for the swx2200 series 】 press the "switch settings and maintenance" button to open the dialog box. device name specify the device name of the switch. input a device name of up to 32 single-byte characters.you can only use single-byte alphanumeric characters, hyphens (-) amdunderline characters (_). power conservation the following settings can be made for the power-conservation function. operation mode loop detection the following settings can be made for the loop detection function. mac address movement number threshold action when a loop is detected port mirroring the following settings can be made for the port mirroring function. operation mode sniffer port and monitoring direction maintenance the following can be executed for a switch. reset the frame counter resume supplying power (for a model that provides poe) update firmware restart initialize 【 for the swx2110 series, swx2110p series 】 press the "switch settings and maintenance" button to open the dialog box. device name specify the device name of the switch. input a device name of up to 32 single-byte characters. youcan only use single-byte alphanumeric characters, hyphens (-) amdunderline characters (_). led mode this lets you configure the led mode settings. flow control this lets you specify whether the flow control function is used. loop detection this lets you specify whether the loop detection function is used. eee this lets you specify whether the eee function is used. port mirroring this lets you configure the sniffer ports, monitor ports and monitoring direction. qos this lets you specify whether qos is used. igmp snooping this lets you specify whether the igmp snooping function is used. maintenance the following can be executed for a switch. reset the frame counter update firmware restart initialize 【 for the swx2100 series 】 press the "switch settings and maintenance" button to open the dialog box. device name display the device name of the switch. port common settings display common settings for the ports. link aggregation settings displays the link aggregation type and load balance rules. this item is shown only for the swx2100-24g. maintenance the following can be executed for a switch. reset the frame counter update firmware restart</div><div class="display_word">6.2. Setting and maintaining switches In the "Tree view," press the "Device" icon of the Yamahaswitch, and in the "Device details and settings view," press the button(the name depends on the switch) to see a dialog box or setting screen. Here you can make settings for the various functions of theswitch, and perform maintenance such as updating the firmware orrestarting. The items that can be set or viewed, and the maintenancefunctions that can be executed, will differ depending on the model. 【 For the SWX2300, SWX2310, SWX2310P, SWR2310, SWR2311P, SWX3100, SWX3200, SWX2320, SWX2322P and SWX3220 Series 】 When you press the "Open the GUI" button , the web setting screen of the switch opens in another window. 【 For the SWX222x Series, SWX2210 Series, SWX2210P Series 】 Press the "Switch settings and maintenance" button to open the dialog box. Device name Specify the device name of the switch. When "Default device name" is selected, the defaultnames that are predetermined for each device will be set. Normally, this is text that shows the model name and serial number. When "Manual settings" is selected, the devicename that was inputted in the input box right afterwards will be set.Input a device name of up to 32 single-byte characters. You can only use single-byte alphanumeric characters and symbols. LED mode This lets you configure the LED mode settings. Port mirroring This lets you configure the sniffer ports, monitor ports and monitoring direction. QoS function This lets you specify whether QoS is used. Maintenance The following can be executed for a switch. Reset the frame counter Restart When you press the "Open the GUI" button , the web setting screen of the switch opens in another window. 【 For the SWX2200 Series 】 Press the "Switch settings and maintenance" button to open the dialog box. Device name Specify the device name of the switch. Input a device name of up to 32 single-byte characters.You can only use single-byte alphanumeric characters, hyphens (-) amdunderline characters (_). Power conservation The following settings can be made for the power-conservation function. Operation mode Loop detection The following settings can be made for the loop detection function. MAC address movement number threshold Action when a loop is detected Port mirroring The following settings can be made for the port mirroring function. Operation mode Sniffer port and monitoring direction Maintenance The following can be executed for a switch. Reset the frame counter Resume supplying power (for a model that provides PoE) Update firmware Restart Initialize 【 For the SWX2110 Series, SWX2110P Series 】 Press the "Switch settings and maintenance" button to open the dialog box. Device name Specify the device name of the switch. Input a device name of up to 32 single-byte characters. Youcan only use single-byte alphanumeric characters, hyphens (-) amdunderline characters (_). LED mode This lets you configure the LED mode settings. Flow control This lets you specify whether the flow control function is used. Loop detection This lets you specify whether the loop detection function is used. EEE This lets you specify whether the EEE function is used. Port mirroring This lets you configure the sniffer ports, monitor ports and monitoring direction. QoS This lets you specify whether QoS is used. IGMP snooping This lets you specify whether the IGMP snooping function is used. Maintenance The following can be executed for a switch. Reset the frame counter Update firmware Restart Initialize 【 For the SWX2100 Series 】 Press the "Switch settings and maintenance" button to open the dialog box. Device name Display the device name of the switch. Port common settings Display common settings for the ports. Link aggregation settings Displays the link aggregation type and load balance rules. This item is shown only for the SWX2100-24G. Maintenance The following can be executed for a switch. Reset the frame counter Update firmware Restart</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_port">6.3. Making port settings for a switch</div><div class="search_word">6.3. making port settings for a switch in the tree view, press the "device" icon corresponding to the yamaha switch; and on the detailed image of the device in "devicedetails and settings view," select a port and press the "port settings" button to display the port settings dialog box. if a port is not selected inthe detailed image of the device in "device details and settings view,"you will not be able to configure the port settings. the port settingscan be changed on the smart l2 switch, swx2110 series, and swx2110pseries. 【 for the swx222x series, swx2210 series, swx2210p series 】 the port settings dialog box appears. basic the following settings can be made for basic functions. port operation automatic cross/straight detection speed flow control eee loop detection qos the following settings can be made for qos. trust mode remarking of received packets remarking value tag vlan the following settings can be made for tag vlan. operation mode access vlan id or native vlan id trunk vlan id for ports joined to a logical interface, configure the settings from the link aggregation settings. multiple vlan the following settings can be made for multiple vlan. joined group for ports joined to a logical interface, configure the settings from the link aggregation settings. 【 for the swx2200 series 】 the port settings dialog box appears. basic the following settings can be made for basic functions. port operation automatic cross/straight detection speed link speed downshift flow control loop detection qos the following settings can be made for qos. dscp remarking transmit shaping receive policing port priority tag vlan the following settings can be made for tag vlan. operation mode access vlan id trunk vlan id multiple vlan the following settings can be made for multiple vlan. joined group frame counter the following settings can be made for the frame counter. transmitted frame received frame power supply function (for a model that provides poe) the following settings can be made for the power supply function. poe supply class settings 【 for the swx2110 series, swx2110p series 】 the port settings dialog box appears. basic the following settings can be made for basic functions. port operation automatic cross/straight detection speed l2ms filter tag vlan the following settings can be made for tag vlan. operation mode access vlan id or native vlan id trunk vlan id</div><div class="display_word">6.3. Making port settings for a switch In the tree view, press the "Device" icon corresponding to the Yamaha switch; and on the detailed image of the device in "Devicedetails and settings view," select a port and press the "Port settings" button to display the port settings dialog box. If a port is not selected inthe detailed image of the device in "Device details and settings view,"you will not be able to configure the port settings. The port settingscan be changed on the Smart L2 switch, SWX2110 series, and SWX2110Pseries. 【 For the SWX222x Series, SWX2210 Series, SWX2210P Series 】 The port settings dialog box appears. Basic The following settings can be made for basic functions. Port operation Automatic cross/straight detection Speed Flow control EEE Loop detection QoS The following settings can be made for QoS. Trust mode Remarking of received packets Remarking value Tag VLAN The following settings can be made for tag VLAN. Operation mode Access VLAN ID or native VLAN ID Trunk VLAN ID For ports joined to a logical interface, configure the settings from the link aggregation settings. Multiple VLAN The following settings can be made for multiple VLAN. Joined group For ports joined to a logical interface, configure the settings from the link aggregation settings. 【 For the SWX2200 Series 】 The port settings dialog box appears. Basic The following settings can be made for basic functions. Port operation Automatic cross/straight detection Speed Link speed downshift Flow control Loop detection QoS The following settings can be made for QoS. DSCP remarking Transmit shaping Receive policing Port priority Tag VLAN The following settings can be made for tag VLAN. Operation mode Access VLAN ID Trunk VLAN ID Multiple VLAN The following settings can be made for multiple VLAN. Joined group Frame counter The following settings can be made for the frame counter. Transmitted frame Received frame Power supply function (for a model that provides PoE) The following settings can be made for the power supply function. PoE supply class settings 【 For the SWX2110 Series, SWX2110P Series 】 The port settings dialog box appears. Basic The following settings can be made for basic functions. Port operation Automatic cross/straight detection Speed L2MS filter Tag VLAN The following settings can be made for tag VLAN. Operation mode Access VLAN ID or native VLAN ID Trunk VLAN ID</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_supply">6.4. Performing power supply operations for the switch port</div><div class="search_word">6.4. performing power supply operations for the switch port in the tree view, press the "device" icon corresponding to the yamaha switch; and on the detailed image of the device in "devicedetails and settings view," select a port and press the "port power supply operation" button to display the port power supply settings dialog box. if a port is notselected in the detailed image of the device in "device details andsettings view," and the selected port does not support power supply, you will not be able to perform power supply operations with this port.power supply settings can be configured for each port from the portpower supply operation dialog. this can be set only on the swx2100-10poe, the swx2100-5poe, theswx2110p-8g, the swx2210p series, the swx2221p-10nt, the swx2220pseries, the swx2310p series, the swr2311p series, and the swx2322pseries.</div><div class="display_word">6.4. Performing power supply operations for the switch port In the tree view, press the "Device" icon corresponding to the Yamaha switch; and on the detailed image of the device in "Devicedetails and settings view," select a port and press the "Port power supply operation" button to display the port power supply settings dialog box. If a port is notselected in the detailed image of the device in "Device details andsettings view," and the selected port does not support power supply, you will not be able to perform power supply operations with this port.Power supply settings can be configured for each port from the portpower supply operation dialog. This can be set only on the SWX2100-10PoE, the SWX2100-5PoE, theSWX2110P-8G, the SWX2210P Series, the SWX2221P-10NT, the SWX2220PSeries, the SWX2310P Series, the SWR2311P Series, and the SWX2322PSeries.</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_lag">6.5. Configuring the link aggregation settings</div><div class="search_word">6.5. configuring the link aggregation settings in the tree view, press the "device" icon corresponding to the yamaha switch; and press the "link aggregation settings" button in "device details and settings view" to display the link aggregationsettings dialog box. this lets you configure settings regarding linkaggregation, add a logical interface or configure the vlan settings andso on.</div><div class="display_word">6.5. Configuring the link aggregation settings In the tree view, press the "Device" icon corresponding to the Yamaha switch; and press the "Link aggregation settings" button in "Device details and settings view" to display the link aggregationsettings dialog box. This lets you configure settings regarding linkaggregation, add a logical interface or configure the VLAN settings andso on.</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#this_can_be_set_only_on_the_swx222x_series_and_the_swx2210_series_swx2210p_series">6.6. This can be set only on the SWX222x Series, and the SWX2210 Series, SWX2210P Series.</div><div class="search_word">6.6. this can be set only on the swx222x series, and the swx2210 series, swx2210p series. link aggregation and load balancing rules this lets you configure the load balancing rule settings. interface settings the following settings can be made for the logical interface. link aggregation the following basic settings can be made. logical interface name joined port interface action tag vlan the following settings can be made for tag vlan. operation mode access vlan id or native vlan id trunk vlan id multiple vlan the following settings can be made for multiple vlan. joined group</div><div class="display_word">6.6. This can be set only on the SWX222x Series, and the SWX2210 Series, SWX2210P Series. Link aggregation and load balancing rules This lets you configure the load balancing rule settings. Interface settings The following settings can be made for the logical interface. Link aggregation The following basic settings can be made. Logical interface name Joined port Interface action Tag VLAN The following settings can be made for tag VLAN. Operation mode Access VLAN ID or native VLAN ID Trunk VLAN ID Multiple VLAN The following settings can be made for multiple VLAN. Joined group</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#map_ap">6.7. Wireless AP settings</div><div class="search_word">6.7. wireless ap settings in the "tree view," press the "device" icon of a yamaha wireless ap, and in "device details and settings view," press the "open the gui" button to view the web settings screen of the yamaha wireless ap in a separate window. settings for the yamaha wireless ap can be made from the websettings window.</div><div class="display_word">6.7. Wireless AP settings In the "Tree view," press the "Device" icon of a Yamaha wireless AP, and in "Device details and settings view," press the "Open the GUI" button to view the web settings screen of the Yamaha wireless AP in a separate window. Settings for the Yamaha wireless AP can be made from the websettings window.</div></div><div id="gui_en_lan_map_map"><div class="search_title" docfname="gui_en_lan_map_map" doctitle="Map" link="#findsw">6.8. Find this switch</div><div class="search_word">6.8. find this switch the "find this switch" function uses led and buzzer to notify the user of the device’s location in an easy-to-understand way. press the "device" icon of a yamaha switch in the "tree view" and then pressthe "find this switch" button in "device details and settings view" todisplay the dialog. note that this function is available only for the swx222x series. the dialog shows the current operating status. there is a start/stop button on the right side that allows you to start or stop the notification. notification start dialog you can start notification by selecting the notification method and the notification period. select one or more notification methods. blink the led sound the buzzer notification stop dialog you can stop any notification method.</div><div class="display_word">6.8. Find this switch The "Find this switch" function uses LED and buzzer to notify the user of the device’s location in an easy-to-understand way. Press the "Device" icon of a Yamaha switch in the "Tree view" and then pressthe "Find this switch" button in "Device details and settings view" todisplay the dialog. Note that this function is available only for the SWX222x series. The dialog shows the current operating status. There is a Start/Stop button on the right side that allows you to start or stop the notification. Notification start dialog You can start notification by selecting the notification method and the notification period. Select one or more notification methods. Blink the LED Sound the buzzer Notification stop dialog You can stop any notification method.</div></div><div id="gui_en_lan_map_multiple"><div class="search_title" docfname="gui_en_lan_map_multiple" doctitle="Multiple" link="#title-box">Multiple VLAN</div><div class="search_word">multiple vlan</div><div class="display_word">Multiple VLAN</div></div><div id="gui_en_lan_map_multiple"><div class="search_title" docfname="gui_en_lan_map_multiple" doctitle="Multiple" link="#multi_vlan_summary">1. Summary</div><div class="search_word">1. summary you can divide the ports of a single switch into multiple groups, and block communication between groups. in addition to grouping ports intomultiple groups, a single port can also be joined to multiple groups.for example, a port that is connected to a terminal that mustcommunicate with all groups, such as a server or router, would be joined to each and every group. for multiple vlans, the same ip address is assigned even if the group is different. the agentes for which a multiple vlan can be set, as well as themaximum number of groups that can be set for each agent on this page are shown below. supported agentes maximum number of groups swx2200-24g 24 swx2200-8g 8 swx2200-8poe 8 swx2210-24g 24 swx2210-16g 16 swx2210-8g 8 swx2210p-28g 28 swx2210p-18g 18 swx2210p-10g 10 swx2220-10nt swx2221p-10nt 10 swx2220-18nt swx2220p-18nt 18 swx2220-26nt swx2220p-26nt 26 swx2310p-28gt swx2310p-18g swx2310p-10g 256 swx2310-52gt swx2310-28gt swx2310-18gt swx2310-10g 256 swr2311p-10g 256 swr2310-28gt swr2310-18gt swr2310-10g 256 swx3100-18gt swx3100-10g 256 swx3200-52gt swx3200-28gt 256 swx2320-16mt swx2322p-16mt swx3220-16mt swx3220-16tms 256</div><div class="display_word">1. Summary You can divide the ports of a single switch into multiple groups, and block communication between groups. In addition to grouping ports intomultiple groups, a single port can also be joined to multiple groups.For example, a port that is connected to a terminal that mustcommunicate with all groups, such as a server or router, would be joined to each and every group. For multiple VLANs, the same IP address is assigned even if the group is different. The agentes for which a multiple VLAN can be set, as well as themaximum number of groups that can be set for each agent on this page are shown below. Supported agentes Maximum number of groups SWX2200-24G 24 SWX2200-8G 8 SWX2200-8PoE 8 SWX2210-24G 24 SWX2210-16G 16 SWX2210-8G 8 SWX2210P-28G 28 SWX2210P-18G 18 SWX2210P-10G 10 SWX2220-10NT SWX2221P-10NT 10 SWX2220-18NT SWX2220P-18NT 18 SWX2220-26NT SWX2220P-26NT 26 SWX2310P-28GT SWX2310P-18G SWX2310P-10G 256 SWX2310-52GT SWX2310-28GT SWX2310-18GT SWX2310-10G 256 SWR2311P-10G 256 SWR2310-28GT SWR2310-18GT SWR2310-10G 256 SWX3100-18GT SWX3100-10G 256 SWX3200-52GT SWX3200-28GT 256 SWX2320-16MT SWX2322P-16MT SWX3220-16MT SWX3220-16TMs 256</div></div><div id="gui_en_lan_map_multiple"><div class="search_title" docfname="gui_en_lan_map_multiple" doctitle="Multiple" link="#multi_vlan_structure">2. Multiple VLAN page structure</div><div class="search_word">2. multiple vlan page structure the multiple vlan page consists of three views: tree view, multiple vlan settings view, and connected devices view.</div><div class="display_word">2. Multiple VLAN page structure The multiple VLAN page consists of three views: tree view, multiple VLAN settings view, and connected devices view.</div></div><div id="gui_en_lan_map_multiple"><div class="search_title" docfname="gui_en_lan_map_multiple" doctitle="Multiple" link="#multi_vlan_structure_tree">2.1. Tree view</div><div class="search_word">2.1. tree view these are the same as shown in the map. the agent topology starting at the manager is shown in the lower left of the screen. network devices of other manufacturers are not shown. in the "tree view," press the "devices" icon to see deviceinformation in the "connected devices view". if a agent that supportsmultiple vlans is selected, settings are shown in "multiple vlansettings view".</div><div class="display_word">2.1. Tree view These are the same as shown in the map. The agent topology starting at the manager is shown in the lower left of the screen. Network devices of other manufacturers are not shown. In the "Tree view," press the "Devices" icon to see deviceinformation in the "Connected devices view". If a agent that supportsmultiple VLANs is selected, settings are shown in "Multiple VLANsettings view".</div></div><div id="gui_en_lan_map_multiple"><div class="search_title" docfname="gui_en_lan_map_multiple" doctitle="Multiple" link="#multi_vlan_structure_edit">2.2. Multiple VLAN settings view</div><div class="search_word">2.2. multiple vlan settings view the multiple vlan settings of the agent selected in "tree view" areshown. this is not shown if a manager or agent that does not supportmultiple vlans is selected in "tree view". list of multiple vlan group settings the status of the joined ports for each group of the multiplevlan are shown in the form of a table. the horizontal direction of thetable shows the ports, and the vertical direction shows the groups. in the table, you can press the port icon to change the port join status of the corresponding group. a port icon that is in the joined state will change to the color that corresponds to the group (example: ). if you once again press a port icon that is in the joined state, it returns to the non-joined state. pressing the "port number" button in the upper edge of the table will select the ports of all groups in the port column, and pressing the "group number" button in the left edge of the table will select all ports in the group line. by pressing the "↘" button in the upper left of the table, you can select diagonally staggered ports from the upper left. ports that are not disabled will not be changed status by any specify method. all ports that belong to the logical interface will be showntogether, as displayed on the right side of the table.the logicalinterface type and number will be shown as a two-row label above theport numbers. the logical interface type (sa or po) is shown on the upper row, and the interface number is shown on the bottom row. static link aggregation is shown for "sa", and lacp link aggregation is shown for "po". when operating the group join status of the ports that belong tothe logical interface, the same settings will be applied to all portsbelonging to the same logical interface. ports/groups to display move the slider on the bar to change the ports and groups shown on the screen. the upper bar is for ports, and the lower bar is for groups. the left-hand slider changes the minimum value, and the right-hand slider changes the maximum value. minimized view select the check box to display a minimized view of the port and group icons. when using the minimized view, the arrows for port uplinks and downlinks will not be displayed. "return all groups to the state prior to the change" button return the ports joined to the multiple vlan to the state prior to the change. "ok" button apply the settings of the ports joined to the multiple vlan. these settings will also apply to ports that are hidden. the "multiple vlan group setting list" can be switched between displayed and hidden by pressing the button in the upper left.</div><div class="display_word">2.2. Multiple VLAN settings view The multiple VLAN settings of the agent selected in "Tree view" areshown. This is not shown if a manager or agent that does not supportmultiple VLANs is selected in "Tree view". List of multiple VLAN group settings The status of the joined ports for each group of the multipleVLAN are shown in the form of a table. The horizontal direction of thetable shows the ports, and the vertical direction shows the groups. In the table, you can press the Port icon to change the port join status of the corresponding group. A Port icon that is in the joined state will change to the color that corresponds to the group (example: ). If you once again press a port icon that is in the joined state, it returns to the non-joined state. Pressing the "Port number" button in the upper edge of the table will select the ports of all groups in the Port column, and pressing the "Group number" button in the left edge of the table will select all ports in the Group line. By pressing the "↘" button in the upper left of the table, you can select diagonally staggered ports from the upper left. Ports that are not disabled will not be changed status by any specify method. All ports that belong to the logical interface will be showntogether, as displayed on the right side of the table.The logicalinterface type and number will be shown as a two-row label above theport numbers. The logical interface type (sa or po) is shown on the upper row, and the interface number is shown on the bottom row. Static link aggregation is shown for "sa", and LACP link aggregation is shown for "po". When operating the group join status of the ports that belong tothe logical interface, the same settings will be applied to all portsbelonging to the same logical interface. Ports/groups to display Move the slider on the bar to change the ports and groups shown on the screen. The upper bar is for ports, and the lower bar is for groups. The left-hand slider changes the minimum value, and the right-hand slider changes the maximum value. Minimized view Select the check box to display a minimized view of the port and group icons. When using the minimized view, the arrows for port uplinks and downlinks will not be displayed. "Return all groups to the state prior to the change" button Return the ports joined to the multiple VLAN to the state prior to the change. "OK" button Apply the settings of the ports joined to the multiple VLAN. These settings will also apply to ports that are hidden. The "Multiple VLAN group setting list" can be switched between displayed and hidden by pressing the button in the upper left.</div></div><div id="gui_en_lan_map_multiple"><div class="search_title" docfname="gui_en_lan_map_multiple" doctitle="Multiple" link="#the_contents_of_the_settings_for_a_previously_specified_multiple_vlan_group_are_shown_by_the_switch_graphic_in_the_lower_part_of_multiplevlan_settings_view">2.3. The contents of the settings for a previously-specified multiple VLAN group are shown by the switch graphic in the lower part of "MultipleVLAN settings view".</div><div class="search_word">2.3. the contents of the settings for a previously-specified multiple vlan group are shown by the switch graphic in the lower part of "multiplevlan settings view". group select pulldown menu select the multiple vlan group that is shown by the switch image at the right side. switch image ports that are joined to the group currently selected in the group select pulldown menu are shown.</div><div class="display_word">2.3. The contents of the settings for a previously-specified multiple VLAN group are shown by the switch graphic in the lower part of "MultipleVLAN settings view". Group select pulldown menu Select the multiple VLAN group that is shown by the switch image at the right side. Switch image Ports that are joined to the group currently selected in the group select pulldown menu are shown.</div></div><div id="gui_en_lan_map_multiple"><div class="search_title" docfname="gui_en_lan_map_multiple" doctitle="Multiple" link="#multi_vlan_structure_device">2.4. Connected devices view</div><div class="search_word">2.4. connected devices view these are the same as shown in the map. devices that are connected to the manager or agent selected in the"tree view" are shown in the lower right of the screen. if "devicemanagement" is not enabled in "lan map settings," terminal information(e.g., pc or mobile devices) is not shown. if a switch is selected as a agent, you can check the type of devicethat is connected to each port of the switch, and use this as areference when making multiple vlan group settings. acquisition date this is the time at which information was last obtained forequipment that is connected to the manager or agent selected in the"tree view". this is not shown if "device management" is not enabled in"lan map settings". select page page numbers are shown for the list of currently-displayed terminals. press or or enter a numeric value to move between pages. acquire button this obtains information for terminals that are connected to themanager or agent selected in the "tree view". this is not shown if"device management" is not enabled in "lan map settings". list information is listed for equipment that is connected to themanager or agent selected in the "tree view". you can press each item’s sort switch to sort the list. the initial screen is sorted in order of port. the vlan id item shows (a) for an access vlan or (t) for a trunk vlan. if the port is being used as a port for a private vlan, the vlan id is not shown, and (p) is shown. if the port is being used as a port for a voice vlan, the vlan id is not shown, and (v) is shown.</div><div class="display_word">2.4. Connected devices view These are the same as shown in the map. Devices that are connected to the manager or agent selected in the"Tree view" are shown in the lower right of the screen. If "Devicemanagement" is not enabled in "LAN map settings," terminal information(e.g., PC or mobile devices) is not shown. If a switch is selected as a agent, you can check the type of devicethat is connected to each port of the switch, and use this as areference when making multiple VLAN group settings. Acquisition date This is the time at which information was last obtained forequipment that is connected to the manager or agent selected in the"Tree view". This is not shown if "Device management" is not enabled in"LAN map settings". Select page Page numbers are shown for the list of currently-displayed terminals. Press or or enter a numeric value to move between pages. Acquire button This obtains information for terminals that are connected to themanager or agent selected in the "Tree view". This is not shown if"Device management" is not enabled in "LAN map settings". List Information is listed for equipment that is connected to themanager or agent selected in the "Tree view". You can press each item’s Sort switch to sort the list. The initial screen is sorted in order of port. The VLAN ID item shows (A) for an access VLAN or (T) for a trunk VLAN. If the port is being used as a port for a private VLAN, the VLAN ID is not shown, and (P) is shown. If the port is being used as a port for a voice VLAN, the VLAN ID is not shown, and (V) is shown.</div></div><div id="gui_en_lan_map_multiple"><div class="search_title" docfname="gui_en_lan_map_multiple" doctitle="Multiple" link="#multi_vlan_edit">3. Making settings for multiple VLAN groups</div><div class="search_word">3. making settings for multiple vlan groups to make multiple vlan group settings, first select the switch thatyou want to set from the "tree view". when you make a selection, the"multiple vlan group settings list" appears in the "multiple vlansettings view". when the "multiple vlan group settings list" appears, select theports that you want to join to each group by pressing the corresponding port icon . when making settings, refer to the following tips. when you finish selecting the ports to join, press the "ok" button to apply the settings to the switch and complete the settings. tips when selecting multiple vlan settings you want to select ports efficiently by using the "port number" button in conjunction with the "↘" button you can select ports efficiently. you can use the "port number" button to allow a specificport to communicate with all other ports. for example, the uplink portnormally needs to be able to communicate with all other ports, so it isjoined to all groups; by pressing the "port number" button in the column of the uplink port, you can avoid the trouble of selecting them individually. use the "↘" button when you want to join each port to adifferent group. for example, if you want to block all communicationbetween each downlink port, and allow communication only with the uplink port, press the "port number" button and "↘" button inthe uplink port column; each group is joined to the uplink port and toone downlink port, allowing you to easily obtain the desired settings.such settings are often used for a network in an internet-equippedapartment building. when you want to restrict the ports and groups to configure adjust the bars for the "ports/groups to display" to show only the ports and groups that you need. you want to re-do the settings by pressing the "return all groups to the state prior to change" button you can return the joined port selection state to the state prior to change.</div><div class="display_word">3. Making settings for multiple VLAN groups To make multiple VLAN group settings, first select the switch thatyou want to set from the "Tree view". When you make a selection, the"Multiple VLAN group settings list" appears in the "Multiple VLANsettings view". When the "Multiple VLAN group settings list" appears, select theports that you want to join to each group by pressing the corresponding Port icon . When making settings, refer to the following tips. When you finish selecting the ports to join, press the "OK" button to apply the settings to the switch and complete the settings. Tips when selecting multiple VLAN settings You want to select ports efficiently By using the "Port number" button in conjunction with the "↘" button you can select ports efficiently. You can use the "Port number" button to allow a specificport to communicate with all other ports. For example, the uplink portnormally needs to be able to communicate with all other ports, so it isjoined to all groups; by pressing the "Port number" button in the column of the uplink port, you can avoid the trouble of selecting them individually. Use the "↘" button when you want to join each port to adifferent group. For example, if you want to block all communicationbetween each downlink port, and allow communication only with the uplink port, press the "Port number" button and "↘" button inthe uplink port column; each group is joined to the uplink port and toone downlink port, allowing you to easily obtain the desired settings.Such settings are often used for a network in an Internet-equippedapartment building. When you want to restrict the ports and groups to configure Adjust the bars for the "Ports/groups to display" to show only the ports and groups that you need. You want to re-do the settings By pressing the "Return all groups to the state prior to change" button you can return the joined port selection state to the state prior to change.</div></div><div id="gui_en_lan_map_multiple"><div class="search_title" docfname="gui_en_lan_map_multiple" doctitle="Multiple" link="#multi_vlan_confirm">4. Showing settings for multiple VLAN groups</div><div class="search_word">4. showing settings for multiple vlan groups multiple vlan groups that have already been specified are indicatedby the switch graphic that is shown at the bottom of the "multiple vlansettings view". from the pulldown at the left, select the group that you want to check; the ports that are joined to that group change to thecolor corresponding to the group. the contents of the settings shown here are the settings that have been actually applied to the switch by pressing the "ok" button . the content that is currently being edited in the "multiple vlan group settings list" is not reflected in the display.</div><div class="display_word">4. Showing settings for multiple VLAN groups Multiple VLAN groups that have already been specified are indicatedby the switch graphic that is shown at the bottom of the "Multiple VLANsettings view". From the pulldown at the left, select the group that you want to check; the ports that are joined to that group change to thecolor corresponding to the group. The contents of the settings shown here are the settings that have been actually applied to the switch by pressing the "OK" button . The content that is currently being edited in the "Multiple VLAN group settings list" is not reflected in the display.</div></div><div id="gui_en_lan_map_summary"><div class="search_title" docfname="gui_en_lan_map_summary" doctitle="About" link="#title-box">About the LAN map</div><div class="search_word">about the lan map</div><div class="display_word">About the LAN map</div></div><div id="gui_en_lan_map_summary"><div class="search_title" docfname="gui_en_lan_map_summary" doctitle="About" link="#lanmap_summary">1. Summary</div><div class="search_word">1. summary the lan map shows terminal information for the agent devices (yamahaswitches, yamaha wireless ap) that are connected to the network, providing a visualization of the entire network. you can use the gui toview the agent status and make vlan settings. you can also detectnetwork problems to gather information when troubleshooting a problem. the switch that controls the lan map (this unit) is called the"manager," and the yamaha switches and yamaha wireless ap units that are controlled by the manager are called "agentes."</div><div class="display_word">1. Summary The LAN map shows terminal information for the agent devices (Yamahaswitches, Yamaha wireless AP) that are connected to the network, providing a visualization of the entire network. You can use the GUI toview the agent status and make VLAN settings. You can also detectnetwork problems to gather information when troubleshooting a problem. The switch that controls the LAN map (this unit) is called the"manager," and the Yamaha switches and Yamaha wireless AP units that are controlled by the manager are called "agentes."</div></div><div id="gui_en_lan_map_summary"><div class="search_title" docfname="gui_en_lan_map_summary" doctitle="About" link="#lanmap_how_to_use">2. Using the LAN map</div><div class="search_word">2. using the lan map here we explain how to use the lan map.</div><div class="display_word">2. Using the LAN map Here we explain how to use the LAN map.</div></div><div id="gui_en_lan_map_summary"><div class="search_title" docfname="gui_en_lan_map_summary" doctitle="About" link="#lanmap_button">2.1. About the buttons</div><div class="search_word">2.1. about the buttons snapshot button you can save the current agent and terminal connection status as a snapshot. you can also export, import, or delete snapshots. *in order to use the snapshot function, you must enable the snapshot function from "settings" . *depending on the network structure, it may take several minutesfor saving to be completed. during this time, other processing can still be executed. when exporting a snapshot, please allow pop-ups in your browser settings. notice button messages for the current network are displayed. this notifies you of agent problems such as a stopped fan or a loop that has occurred. history button this displays the history of notification messages. the history can save up to 1000 items. if you press the "delete all" button, all history is deleted. device list button the "device list page" is shown in a separate window. in thedevice list page you can view a list of the terminals and agentesmanaged in the lan map, and manage terminal information. "whole map" button the "whole map page" is shown in a separate window. on the wholemap page, the devices connected to the lan are displayed on the samemap. settings button here you can make settings for the lan map function.</div><div class="display_word">2.1. About the buttons Snapshot button You can save the current agent and terminal connection status as a snapshot. You can also export, import, or delete snapshots. *In order to use the snapshot function, you must enable the snapshot function from "Settings" . *Depending on the network structure, it may take several minutesfor saving to be completed. During this time, other processing can still be executed. When exporting a snapshot, please allow pop-ups in your browser settings. Notice button Messages for the current network are displayed. This notifies you of agent problems such as a stopped fan or a loop that has occurred. History button This displays the history of notification messages. The history can save up to 1000 items. If you press the "Delete all" button, all history is deleted. Device list button The "Device list page" is shown in a separate window. In thedevice list page you can view a list of the terminals and agentesmanaged in the LAN map, and manage terminal information. "Whole map" button The "Whole map page" is shown in a separate window. On the wholemap page, the devices connected to the LAN are displayed on the samemap. Settings button Here you can make settings for the LAN map function.</div></div><div id="gui_en_lan_map_summary"><div class="search_title" docfname="gui_en_lan_map_summary" doctitle="About" link="#lanmap_map_use">2.2. Using the LAN map</div><div class="search_word">2.2. using the lan map to use the lan map, open the "lan map settings" dialog box from the"settings" button, and select the "manager" check box in the basicsettings under "l2ms operation mode". if "l2ms operation mode" is set to "agent" or "do not use", youcannot use the lan map for this unit. if this unit is operating as aagent, use the lan map on the manager that is controlling this unit.</div><div class="display_word">2.2. Using the LAN map To use the LAN map, open the "LAN map settings" dialog box from the"Settings" button, and select the "Manager" check box in the basicsettings under "L2MS operation mode". If "L2MS operation mode" is set to "Agent" or "Do not use", youcannot use the LAN map for this unit. If this unit is operating as aagent, use the LAN map on the manager that is controlling this unit.</div></div><div id="gui_en_lan_map_summary"><div class="search_title" docfname="gui_en_lan_map_summary" doctitle="About" link="#lanmap_change_screen">2.3. Change pages</div><div class="search_word">2.3. change pages the lan map consists mainly of map, tag vlan, and multiple vlan pages. to switch the page that is displayed, use the page selection toggle switch located in the upper part of the screen.</div><div class="display_word">2.3. Change pages The LAN map consists mainly of map, tag VLAN, and multiple VLAN pages. To switch the page that is displayed, use the page selection toggle switch located in the upper part of the screen.</div></div><div id="gui_en_lan_map_summary"><div class="search_title" docfname="gui_en_lan_map_summary" doctitle="About" link="#lanmap_snapshot_use">2.4. Use the snapshot function</div><div class="search_word">2.4. use the snapshot function the snapshot function compares the current network connection stateto the previously saved network connection state (snapshot), and if achange is detected, displays a warning message. to use the snapshotfunction, perform the following operations. use the "settings" button to open the "lan map settings" dialog box, and in the snapshot function settings section, select "use the snapshot function". if you wantterminals to also be included in the comparison, select either "includeall terminals in comparison" or "include only wired terminals incomparison" depending on the terminals that you want to compare. use the "snapshot" button to save the snapshot. if you want to apply an exported snapshot to a manager, import that snapshot.</div><div class="display_word">2.4. Use the snapshot function The snapshot function compares the current network connection stateto the previously saved network connection state (snapshot), and if achange is detected, displays a warning message. To use the snapshotfunction, perform the following operations. Use the "Settings" button to open the "LAN map settings" dialog box, and in the snapshot function settings section, select "Use the snapshot function". If you wantterminals to also be included in the comparison, select either "Includeall terminals in comparison" or "Include only wired terminals incomparison" depending on the terminals that you want to compare. Use the "Snapshot" button to save the snapshot. If you want to apply an exported snapshot to a manager, import that snapshot.</div></div><div id="gui_en_lan_map_summary"><div class="search_title" docfname="gui_en_lan_map_summary" doctitle="About" link="#lanmap_admin_user">3. Differences in what administrative users and general users can do</div><div class="search_word">3. differences in what administrative users and general users can do basically, a general user can only view information, and cannotperform operations that modify settings, manage snapshots, edit oroperate the terminal db and so on. an administrative user can performall operations. the following operations cannot be performed by a general user. agent management using the "settings" button to change lan map settings using the "acquire" button to acquire device information. using the "snapshot" button to manage snapshots editing, deleting, newly registering, importing, and exporting a terminal db procedure for saving a terminal list and agent list in csv format</div><div class="display_word">3. Differences in what administrative users and general users can do Basically, a general user can only view information, and cannotperform operations that modify settings, manage snapshots, edit oroperate the terminal DB and so on. An administrative user can performall operations. The following operations cannot be performed by a general user. Agent management Using the "Settings" button to change LAN map settings Using the "Acquire" button to acquire device information. Using the "Snapshot" button to manage snapshots Editing, deleting, newly registering, importing, and exporting a terminal DB Procedure for saving a terminal list and agent list in CSV format</div></div><div id="gui_en_lan_map_vlan"><div class="search_title" docfname="gui_en_lan_map_vlan" doctitle="Tag" link="#title-box">Tag VLAN</div><div class="search_word">tag vlan</div><div class="display_word">Tag VLAN</div></div><div id="gui_en_lan_map_vlan"><div class="search_title" docfname="gui_en_lan_map_vlan" doctitle="Tag" link="#vlan_summary">1. Summary</div><div class="search_word">1. summary you can create vlans to organize yamaha switches or yamaha wireless aps into groups.</div><div class="display_word">1. Summary You can create VLANs to organize Yamaha switches or Yamaha wireless APs into groups.</div></div><div id="gui_en_lan_map_vlan"><div class="search_title" docfname="gui_en_lan_map_vlan" doctitle="Tag" link="#tagged_vlans_can_be_set_for_the_following_agentes">1.1. Tagged VLANs can be set for the following agentes.</div><div class="search_word">1.1. tagged vlans can be set for the following agentes. yamaha network switch swx2110-5g, swx2110-8g, swx2110-16g, swx2110p-8g swx2200-8g, swx2200-24g, swx2200-8poe swx2210p-10g, swx2210p-18g, swx2210p-28g swx2210-8g, swx2210-16g, swx2210-24g swx2220-10nt, swx2220-18nt, swx2220-26nt swx2221p-10nt, swx2220p-18nt, swx2220p-26nt swx2300-8g, swx2300-16g, swx2300-24g swx2310p-10g, swx2310p-18g, swx2310p-28gt swx2310-10g, swx2310-18gt, swx2310-28gt, swx2310-52gt swr2311p-10g swr2310-10g, swr2310-18gt, swr2310-28gt swx3100-10g, swx3100-18gt swx3200-28gt, swx3200-52gt swx2320-16mt, swx2322p-16mt, swx3220-16mt, swx3220-16tms yamaha wireless access point wlx202 wlx212 wlx222 wlx302 wlx313 wlx322 wlx323 wlx402 wlx413</div><div class="display_word">1.1. Tagged VLANs can be set for the following agentes. Yamaha network switch SWX2110-5G, SWX2110-8G, SWX2110-16G, SWX2110P-8G SWX2200-8G, SWX2200-24G, SWX2200-8PoE SWX2210P-10G, SWX2210P-18G, SWX2210P-28G SWX2210-8G, SWX2210-16G, SWX2210-24G SWX2220-10NT, SWX2220-18NT, SWX2220-26NT SWX2221P-10NT, SWX2220P-18NT, SWX2220P-26NT SWX2300-8G, SWX2300-16G, SWX2300-24G SWX2310P-10G, SWX2310P-18G, SWX2310P-28GT SWX2310-10G, SWX2310-18GT, SWX2310-28GT, SWX2310-52GT SWR2311P-10G SWR2310-10G, SWR2310-18GT, SWR2310-28GT SWX3100-10G, SWX3100-18GT SWX3200-28GT, SWX3200-52GT SWX2320-16MT, SWX2322P-16MT, SWX3220-16MT, SWX3220-16TMs Yamaha wireless access point WLX202 WLX212 WLX222 WLX302 WLX313 WLX322 WLX323 WLX402 WLX413</div></div><div id="gui_en_lan_map_vlan"><div class="search_title" docfname="gui_en_lan_map_vlan" doctitle="Tag" link="#vlan_note">2. Notes</div><div class="search_word">2. notes if a switch of a different manufacturer is connected below amanager, the manager will be unable to recognize the correspondingdevice, and the topology will therefore not be displayed. ifcommunication from the terminal becomes impossible even though the tagvlan settings are correct, it might be that a switch made by anothermanufacturer which is blocking vlan tagged frames is connected below the manager. if a yamaha switch of a model that cannot be determined isconnected below the manager, it might be that the vlan tagged framescannot pass through that device, depending on the settings of thatdevice. configurations that include mst instances in the spanning tree are not supported.</div><div class="display_word">2. Notes If a switch of a different manufacturer is connected below amanager, the manager will be unable to recognize the correspondingdevice, and the topology will therefore not be displayed. Ifcommunication from the terminal becomes impossible even though the tagVLAN settings are correct, it might be that a switch made by anothermanufacturer which is blocking VLAN tagged frames is connected below the manager. If a Yamaha switch of a model that cannot be determined isconnected below the manager, it might be that the VLAN tagged framescannot pass through that device, depending on the settings of thatdevice. Configurations that include MST instances in the spanning tree are not supported.</div></div><div id="gui_en_lan_map_vlan"><div class="search_title" docfname="gui_en_lan_map_vlan" doctitle="Tag" link="#vlan_page">3. Tag VLAN page structure</div><div class="search_word">3. tag vlan page structure</div><div class="display_word">3. Tag VLAN page structure</div></div><div id="gui_en_lan_map_vlan"><div class="search_title" docfname="gui_en_lan_map_vlan" doctitle="Tag" link="#vlan_button">3.1. Button</div><div class="search_word">3.1. button new button create a new vlan group. in order to join a port to a vlan group, the vlan group must first be created. refresh display button obtain topology information and vlan settings information, and redraw the tag vlan group list and the topology. depending on the number of agent units, it may take severalseconds to several tens of seconds for the agent vlan settingsinformation to be reflected.</div><div class="display_word">3.1. Button New button Create a new VLAN group. In order to join a port to a VLAN group, the VLAN group must first be created. Refresh display button Obtain topology information and VLAN settings information, and redraw the tag VLAN group list and the topology. Depending on the number of agent units, it may take severalseconds to several tens of seconds for the agent VLAN settingsinformation to be reflected.</div></div><div id="gui_en_lan_map_vlan"><div class="search_title" docfname="gui_en_lan_map_vlan" doctitle="Tag" link="#vlan_group_list">3.2. Tag VLAN group list</div><div class="search_word">3.2. tag vlan group list display the list of vlan groups that are registered to the manager,and the list of vlan groups that the agent ports have joined. however, the list does not show private vlans or vlan groups for which frame forwarding is disabled. the port color is assigned to each vlan group.</div><div class="display_word">3.2. Tag VLAN group list Display the list of VLAN groups that are registered to the manager,and the list of VLAN groups that the agent ports have joined. However, the list does not show private VLANs or VLAN groups for which frame forwarding is disabled. The port color is assigned to each VLAN group.</div></div><div id="gui_en_lan_map_vlan"><div class="search_title" docfname="gui_en_lan_map_vlan" doctitle="Tag" link="#vlan_topology">3.3. Topology</div><div class="search_word">3.3. topology the topology starting at the manager is shown in the lower part of the screen. by noting the color of the port, you can determine the vlan group to which it is joined.</div><div class="display_word">3.3. Topology The topology starting at the manager is shown in the lower part of the screen. By noting the color of the port, you can determine the VLAN group to which it is joined.</div></div><div id="gui_en_lan_map_vlan"><div class="search_title" docfname="gui_en_lan_map_vlan" doctitle="Tag" link="#vlan_group">4. Make tag VLAN group settings</div><div class="search_word">4. make tag vlan group settings</div><div class="display_word">4. Make tag VLAN group settings</div></div><div id="gui_en_lan_map_vlan"><div class="search_title" docfname="gui_en_lan_map_vlan" doctitle="Tag" link="#vlan_group_new">4.1. Create new</div><div class="search_word">4.1. create new to create a new vlan group, press the "new" button . the following settings can be made. item name description vlan-id set the id of the vlan. name you can assign a name to the vlan id. after input, press the "ok" button to register the vlan group.</div><div class="display_word">4.1. Create new To create a new VLAN group, press the "New" button . The following settings can be made. Item name Description VLAN-ID Set the ID of the VLAN. Name You can assign a name to the VLAN ID. After input, press the "OK" button to register the VLAN group.</div></div><div id="gui_en_lan_map_vlan"><div class="search_title" docfname="gui_en_lan_map_vlan" doctitle="Tag" link="#vlan_group_mod">4.2. 4-2.Change settings</div><div class="search_word">4.2. 4-2.change settings if you want to change the vlan group settings, press the "settings" button located in the column at the right of the "tag vlan group list" . you can edit the name setting.</div><div class="display_word">4.2. 4-2.Change settings If you want to change the VLAN group settings, press the "Settings" button located in the column at the right of the "Tag VLAN group list" . You can edit the name setting.</div></div><div id="gui_en_lan_map_vlan"><div class="search_title" docfname="gui_en_lan_map_vlan" doctitle="Tag" link="#vlan_group_reg">4.3. 4-3.Register</div><div class="search_word">4.3. 4-3.register if a agent port is joined to a vlan group that is not registered to a manager, it is shown as an "unknown" vlan group in "tag vlan group list" . by pressing the "register" button located in the column at the right of "tag vlan group list" , you can register a vlan group to a manager.</div><div class="display_word">4.3. 4-3.Register If a agent port is joined to a VLAN group that is not registered to a manager, it is shown as an "Unknown" VLAN group in "Tag VLAN group list" . By pressing the "Register" button located in the column at the right of "Tag VLAN group list" , you can register a VLAN group to a manager.</div></div><div id="gui_en_lan_map_vlan"><div class="search_title" docfname="gui_en_lan_map_vlan" doctitle="Tag" link="#vlan_group_del">4.4. Delete</div><div class="search_word">4.4. delete if you want to delete a vlan group, press the "delete" button located in the column at the right of the "tag vlan group list" . then press the "ok" button to delete the settings of the specified vlan group and also delete the settings of the vlan group that is applied to the agent.</div><div class="display_word">4.4. Delete If you want to delete a VLAN group, press the "Delete" button located in the column at the right of the "Tag VLAN group list" . Then press the "OK" button to delete the settings of the specified VLAN group and also delete the settings of the VLAN group that is applied to the agent.</div></div><div id="gui_en_lan_map_vlan"><div class="search_title" docfname="gui_en_lan_map_vlan" doctitle="Tag" link="#vlan_join">5. Join a tag VLAN group</div><div class="search_word">5. join a tag vlan group to select a agent port within the topology, press the "select joined port" button button in the right column of "tag vlan group list" . the color of the port indicates the setting status of the vlan group. the following is a depiction of when the port color is set to for a vlan group when selecting the joined ports. lan sfp description this is an access port that is joined to the specified vlan group. this is an access port that is joined to the default vlan group. this is an access port that is joined to the specified vlan group. to determine the joined vlan group, note the color of the port that is assigned in "tag vlan group list". this is a trunk port or hybrid port. this is joined to the specified vlan group. this is a trunk port or hybrid port. this is not joined to the specified vlan group. when you select a port, the color of the port changes, allowing you to join it to the specified vlan group. by re-selecting a port, you can un-join it. when operating the vlan join status of the port that belongs to thelogical interface, the same settings will be applied to all portsbelonging to the same logical interface. after selecting a port, press the "ok" button to apply the setting. if a yamaha switch of a model that cannot be determined isconnected, it might be that the vlan tagged frames cannot pass throughthat device, depending on the settings of that device. automatically joining uplink ports and downlink ports if you join a port to a vlan group, the port that connects fromthe manager to the corresponding agent (uplink/downlink) willautomatically be either a trunk port or a hybrid port. constraints when joining a vlan group the following constraints apply when making swx2300 series,swx2310 series, swx2310p series, swr2310 series, swr2311p series,swx3100 series, swx3200 series, swx2320 series, swx2322p series, swx3220 series settings. if the specified vlan group is used as a private vlan by aagent, a port of the corresponding agent cannot be joined to thespecified vlan group. if a port is specified as a private vlan’s promiscuous port, or as a host port, settings for that port cannot be made. if a port is used by the link aggregation function, settings for that port cannot be made.(only swx2300 series) also, you cannot change the stack port settings for devices in a stack configuration.</div><div class="display_word">5. Join a tag VLAN group To select a agent port within the topology, press the "Select joined port" button button in the right column of "Tag VLAN group list" . The color of the port indicates the setting status of the VLAN group. The following is a depiction of when the port color is set to for a VLAN group when selecting the joined ports. LAN SFP Description This is an access port that is joined to the specified VLAN group. This is an access port that is joined to the default VLAN group. This is an access port that is joined to the specified VLAN group. To determine the joined VLAN group, note the color of the port that is assigned in "Tag VLAN group list". This is a trunk port or hybrid port. This is joined to the specified VLAN group. This is a trunk port or hybrid port. This is not joined to the specified VLAN group. When you select a port, the color of the port changes, allowing you to join it to the specified VLAN group. By re-selecting a port, you can un-join it. When operating the VLAN join status of the port that belongs to thelogical interface, the same settings will be applied to all portsbelonging to the same logical interface. After selecting a port, press the "OK" button to apply the setting. If a Yamaha switch of a model that cannot be determined isconnected, it might be that the VLAN tagged frames cannot pass throughthat device, depending on the settings of that device. Automatically joining uplink ports and downlink ports If you join a port to a VLAN group, the port that connects fromthe manager to the corresponding agent (uplink/downlink) willautomatically be either a trunk port or a hybrid port. Constraints when joining a VLAN group The following constraints apply when making SWX2300 Series,SWX2310 Series, SWX2310P Series, SWR2310 Series, SWR2311P Series,SWX3100 Series, SWX3200 Series, SWX2320 Series, SWX2322P Series, SWX3220 Series settings. If the specified VLAN group is used as a private VLAN by aagent, a port of the corresponding agent cannot be joined to thespecified VLAN group. If a port is specified as a private VLAN’s promiscuous port, or as a host port, settings for that port cannot be made. If a port is used by the link aggregation function, settings for that port cannot be made.(only SWX2300 Series) Also, you cannot change the stack port settings for devices in a stack configuration.</div></div><div id="gui_en_lan_map_vlan"><div class="search_title" docfname="gui_en_lan_map_vlan" doctitle="Tag" link="#vlan_show">6. Show tag VLAN group settings</div><div class="search_word">6. show tag vlan group settings in "tag vlan group list" , colors are assigned to the ports for each vlan group. by noting the color of a agent port in the topology, you can see the vlan group to which it is joined. examples are shown below. lan sfp description this is an access port that is joined to a vlan group other than the default vlan. to determine the joined vlan group, note the color of the port that is assigned in "tag vlan group list". this is a trunk port or hybrid port. this is an access port that is joined to the default vlan group. you can also check the tag vlan group settings from the tool tip that appears when you mouse-over. the items shown in the tool tip are as follows. port number for logical interfaces, the logical interface name and thenumbers of all ports belonging to the logical interface will be shown. sax is the name of the logical interface for a static link aggregation. pox is the name of the lacp virtual interface. port type ( access, trunk, hybrid ) vlan group joined supplementary information related to swx2300 series, swx2310 series,swx2310p series, swr2310 series, swr2311p series, swx3100 series,swx3200 series, swx2320 series, swx2322p series, swx3220 series settings is shown below. about native vlan the uplink/downlink ports are the trunk ports, and the defaultvlan is specified as the native vlan. if the frame received by the trunk port is untagged, the native vlan is the vlan group joined by untaggedframes. about promiscuous ports and host ports of a private vlan if the port is specified as a private vlan’s promiscuous port or a host port, the port type in the tool tip is shown as "private," and the joined vlan group is not shown.</div><div class="display_word">6. Show tag VLAN group settings In "Tag VLAN group list" , colors are assigned to the ports for each VLAN group. By noting the color of a agent port in the topology, you can see the VLAN group to which it is joined. Examples are shown below. LAN SFP Description This is an access port that is joined to a VLAN group other than the default VLAN. To determine the joined VLAN group, note the color of the port that is assigned in "Tag VLAN group list". This is a trunk port or hybrid port. This is an access port that is joined to the default VLAN group. You can also check the tag VLAN group settings from the tool tip that appears when you mouse-over. The items shown in the tool tip are as follows. Port number For logical interfaces, the logical interface name and thenumbers of all ports belonging to the logical interface will be shown. saX is the name of the logical interface for a static link aggregation. poX is the name of the LACP virtual interface. Port type ( Access, Trunk, Hybrid ) VLAN group joined Supplementary information related to SWX2300 Series, SWX2310 Series,SWX2310P Series, SWR2310 Series, SWR2311P Series, SWX3100 Series,SWX3200 Series, SWX2320 Series, SWX2322P Series, SWX3220 Series settings is shown below. About native VLAN The uplink/downlink ports are the trunk ports, and the defaultVLAN is specified as the native VLAN. If the frame received by the trunk port is untagged, the native VLAN is the VLAN group joined by untaggedframes. About promiscuous ports and host ports of a private VLAN If the port is specified as a private VLAN’s promiscuous port or a host port, the port type in the tool tip is shown as "Private," and the joined VLAN group is not shown.</div></div><div id="gui_en_lan_map_whole_map_contents"><div class="search_title" docfname="gui_en_lan_map_whole_map_contents" doctitle="Whole" link="#title-box">Whole map</div><div class="search_word">whole map</div><div class="display_word">Whole map</div></div><div id="gui_en_lan_map_whole_map_contents"><div class="search_title" docfname="gui_en_lan_map_whole_map_contents" doctitle="Whole" link="#whole_map_summary">1. Summary</div><div class="search_word">1. summary the whole map shows all devices connected to the network, using asingle topology.you can switch the topology display range and the device information view, to customize the display and make it easier toview.use the print function to print the whole map displayed, in orderto make use of the map in various network operation management-relatedsituations.</div><div class="display_word">1. Summary The whole map shows all devices connected to the network, using asingle topology.You can switch the topology display range and the device information view, to customize the display and make it easier toview.Use the print function to print the whole map displayed, in orderto make use of the map in various network operation management-relatedsituations.</div></div><div id="gui_en_lan_map_whole_map_contents"><div class="search_title" docfname="gui_en_lan_map_whole_map_contents" doctitle="Whole" link="#whole_map_note">2. Notes</div><div class="search_word">2. notes cookies are used and saved for the whole map view settings.enablecookies on your browser to save the whole map view settings.see the help content supplied with your browser for instructions on how to enablecookies.if you have made changes to the settings but the changes are not reflected when accessing the whole map once more, cookies may bedisabled or have been deleted in your browser. you can confirm the link speed between devices (the link speed ofthe port belonging to higher devices) and link speed, by checking thecolor and shape of the connector lines between the device icons. see the legend at the top right of the screen for how the colors correspond to link speeds. the link speeds of terminals connected to a yamaha wireless ap or agentes for which the type cannot be determined are shown usinggray-colored connector lines.</div><div class="display_word">2. Notes Cookies are used and saved for the whole map view settings.Enablecookies on your browser to save the whole map view settings.See the help content supplied with your browser for instructions on how to enablecookies.If you have made changes to the settings but the changes are not reflected when accessing the whole map once more, cookies may bedisabled or have been deleted in your browser. You can confirm the link speed between devices (the link speed ofthe port belonging to higher devices) and link speed, by checking thecolor and shape of the connector lines between the device icons. See the legend at the top right of the screen for how the colors correspond to link speeds. The link speeds of terminals connected to a Yamaha wireless AP or agentes for which the type cannot be determined are shown usinggray-colored connector lines.</div></div><div id="gui_en_lan_map_whole_map_contents"><div class="search_title" docfname="gui_en_lan_map_whole_map_contents" doctitle="Whole" link="#whole_map_page_button">3. About the buttons</div><div class="search_word">3. about the buttons "top" button used for the focus function.see using the focus function for details. "up" button used for the focus function.see using the focus function for details. "refresh display" button the page will reload. "view settings" button here you can configure the information shown on the whole map.for details, see " switching the device information view ", " displaying/hiding a terminal " and " switching the port information view. " "print preview" button this opens the screen for printing.see " printing the whole map " for details.</div><div class="display_word">3. About the buttons "Top" button Used for the focus function.See Using the focus function for details. "Up" button Used for the focus function.See Using the focus function for details. "Refresh display" button The page will reload. "View settings" button Here you can configure the information shown on the whole map.For details, see " Switching the device information view ", " Displaying/hiding a terminal " and " Switching the port information view. " "Print preview" button This opens the screen for printing.See " Printing the whole map " for details.</div></div><div id="gui_en_lan_map_whole_map_contents"><div class="search_title" docfname="gui_en_lan_map_whole_map_contents" doctitle="Whole" link="#whole_map_mini_map">4. About the mini whole map</div><div class="search_word">4. about the mini whole map the mini whole map is a reduced version of the whole map.use this toget a birds’-eye view of the entire map.you can also use the focusfunction to understand which agent is getting the focus.see using the focus function for details. note: if the total number of managers, agentes and ssids on the whole map exceed 200, the mini whole map will not be displayed.</div><div class="display_word">4. About the mini whole map The mini whole map is a reduced version of the whole map.Use this toget a birds’-eye view of the entire map.You can also use the focusfunction to understand which agent is getting the focus.See Using the focus function for details. Note: If the total number of managers, agentes and SSIDs on the whole map exceed 200, the mini whole map will not be displayed.</div></div><div id="gui_en_lan_map_whole_map_contents"><div class="search_title" docfname="gui_en_lan_map_whole_map_contents" doctitle="Whole" link="#whole_map_devinfo">5. Switching the device information view</div><div class="search_word">5. switching the device information view you can switch the device information shown on the right-hand side of the device icons.you can set the items to be displayed for the agentesand terminals individually.use the following operations to configure the settings. press the "view settings" button at the upper right-hand part of the screen.the view settings screen will display directly below. select the items to view using the drop-down list boxes to theright of the "agent information" and "terminal information" on the viewsettings screen.when these items are selected, the device informationshown at the right of the device icons on the whole map will switch tothe selected item.the settings will automatically be saved at the timing in which they are switched. note: the four drop-down list boxes are lined up verticallycorresponding to the order in which the device information to the rightof the device icons on the whole map is displayed.</div><div class="display_word">5. Switching the device information view You can switch the device information shown on the right-hand side of the device icons.You can set the items to be displayed for the agentesand terminals individually.Use the following operations to configure the settings. Press the "View settings" button at the upper right-hand part of the screen.The view settings screen will display directly below. Select the items to view using the drop-down list boxes to theright of the "agent information" and "terminal information" on the viewsettings screen.When these items are selected, the device informationshown at the right of the device icons on the whole map will switch tothe selected item.The settings will automatically be saved at the timing in which they are switched. Note: The four drop-down list boxes are lined up verticallycorresponding to the order in which the device information to the rightof the device icons on the whole map is displayed.</div></div><div id="gui_en_lan_map_whole_map_contents"><div class="search_title" docfname="gui_en_lan_map_whole_map_contents" doctitle="Whole" link="#agent_information_to_view_can_be_selected_from_the_following">5.1. Agent information to view can be selected from the following.</div><div class="search_word">5.1. agent information to view can be selected from the following. device name mac address model name ip address hide</div><div class="display_word">5.1. Agent information to view can be selected from the following. Device name MAC address Model name IP address Hide</div></div><div id="gui_en_lan_map_whole_map_contents"><div class="search_title" docfname="gui_en_lan_map_whole_map_contents" doctitle="Whole" link="#terminal_information_to_view_can_be_selected_from_the_following">5.2. Terminal information to view can be selected from the following.</div><div class="search_word">5.2. terminal information to view can be selected from the following. ip address manufacturer device name mac address model name comment os hide note: up to 30 single-byte characters are displayed for the deviceinformation. if the text length exceeds 30 single-byte characters, therest of the item will be omitted.</div><div class="display_word">5.2. Terminal information to view can be selected from the following. IP address Manufacturer Device name MAC address Model name Comment OS Hide Note: Up to 30 single-byte characters are displayed for the deviceinformation. If the text length exceeds 30 single-byte characters, therest of the item will be omitted.</div></div><div id="gui_en_lan_map_whole_map_contents"><div class="search_title" docfname="gui_en_lan_map_whole_map_contents" doctitle="Whole" link="#whole_map_terminal">6. Displaying/hiding a terminal</div><div class="search_word">6. displaying/hiding a terminal you can switch between displaying or hiding terminals shown on thewhole map.if you do not need to manage terminals, you can hide theterminals and show only the agentes, making the view easier to read.usethe following operations to configure the settings. press the "view settings" button at the upper right-hand part of the screen.the view settings screen will display directly below. select the check box to the left of the "terminal information"text on the view settings screen to display the terminal, and deselectthe check box to hide the terminal.the settings will automatically besaved at the timing in which they are switched.</div><div class="display_word">6. Displaying/hiding a terminal You can switch between displaying or hiding terminals shown on thewhole map.If you do not need to manage terminals, you can hide theterminals and show only the agentes, making the view easier to read.Usethe following operations to configure the settings. Press the "View settings" button at the upper right-hand part of the screen.The view settings screen will display directly below. Select the check box to the left of the "Terminal information"text on the view settings screen to display the terminal, and deselectthe check box to hide the terminal.The settings will automatically besaved at the timing in which they are switched.</div></div><div id="gui_en_lan_map_whole_map_contents"><div class="search_title" docfname="gui_en_lan_map_whole_map_contents" doctitle="Whole" link="#whole_map_portinfo">7. Switching the port information view</div><div class="search_word">7. switching the port information view you can switch between displaying or hiding the connecting port andvlan information shown on the topology of the whole map.use thefollowing operations to configure the settings. press the "view settings" button at the upper right-hand part of the screen.the view settings screen will display directly below. select the check boxes in "port information" on the viewsettings screen for the "port number" and "vlan-id" to view thisinformation, and deselect the check boxes to hide the information.thesettings will automatically be saved at the timing in which they areswitched.</div><div class="display_word">7. Switching the port information view You can switch between displaying or hiding the connecting port andVLAN information shown on the topology of the whole map.Use thefollowing operations to configure the settings. Press the "View settings" button at the upper right-hand part of the screen.The view settings screen will display directly below. Select the check boxes in "Port information" on the viewsettings screen for the "Port number" and "VLAN-ID" to view thisinformation, and deselect the check boxes to hide the information.Thesettings will automatically be saved at the timing in which they areswitched.</div></div><div id="gui_en_lan_map_whole_map_contents"><div class="search_title" docfname="gui_en_lan_map_whole_map_contents" doctitle="Whole" link="#whole_map_focus">8. Using the focus function</div><div class="search_word">8. using the focus function press the agent icon on the whole map for a focused view of thetopology, including the selected agentes and the devices that theycontrol. focusing on this view will enable the "top" button and the "up" button in the top left part of the screen.press the "top" button to return to a view of the overall topology, centered on the manager.press the "up" button on the top left part of the screen to view the topology, centered onthe agentes or managers one level above.the agentes that are at thecenter of the topology’s focus are shown within a blue border on themini whole map at the right side of the screen, which helps you tounderstand their location.you can also view the "route" in the upperleft part of the screen to confirm the location of a agent.</div><div class="display_word">8. Using the focus function Press the agent icon on the whole map for a focused view of thetopology, including the selected agentes and the devices that theycontrol. Focusing on this view will enable the "Top" button and the "Up" button in the top left part of the screen.Press the "Top" button to return to a view of the overall topology, centered on the manager.Press the "Up" button on the top left part of the screen to view the topology, centered onthe agentes or managers one level above.The agentes that are at thecenter of the topology’s focus are shown within a blue border on themini whole map at the right side of the screen, which helps you tounderstand their location.You can also view the "Route" in the upperleft part of the screen to confirm the location of a agent.</div></div><div id="gui_en_lan_map_whole_map_contents"><div class="search_title" docfname="gui_en_lan_map_whole_map_contents" doctitle="Whole" link="#whole_map_print">9. Printing the whole map</div><div class="search_word">9. printing the whole map using the whole map, you can print the currently viewed whole map from the print preview.use the following operations to print. press the "print preview" button at the upper right part of the screen.the print preview will display in a separate window. check the print preview and press the "print this page" button on the upper part of the screen if everything looks the way you wantit.the browser’s print preview will be displayed.set the paper size toa4 or larger when printing. note: when changing the focus or device information view afterdisplaying the print preview, close the print preview first, makechanges to the focus or device information view on the whole map, andthen press the "print preview" button again to open the print preview.the settings cannot be changed from the print preview. note: when opening a agent configuration series for a topology that is long (in other words, a topology that is too wide to fit) in theprint preview, the width of the topology on the print preview will beadjusted to horizontally accommodate a4-sized paper.</div><div class="display_word">9. Printing the whole map Using the whole map, you can print the currently viewed whole map from the Print preview.Use the following operations to print. Press the "Print preview" button at the upper right part of the screen.The Print preview will display in a separate window. Check the Print preview and press the "Print this page" button on the upper part of the screen if everything looks the way you wantit.The browser’s print preview will be displayed.Set the paper size toA4 or larger when printing. Note: When changing the focus or device information view afterdisplaying the Print preview, close the Print preview first, makechanges to the focus or device information view on the whole map, andthen press the "Print preview" button again to open the Print preview.The settings cannot be changed from the Print preview. Note: When opening a agent configuration series for a topology that is long (in other words, a topology that is too wide to fit) in thePrint preview, the width of the topology on the Print preview will beadjusted to horizontally accommodate A4-sized paper.</div></div><div id="gui_en_lan_map_whole_map_contents"><div class="search_title" docfname="gui_en_lan_map_whole_map_contents" doctitle="Whole" link="#whole_map_ap_terminal">10. Checking the terminals connected to wireless AP</div><div class="search_word">10. checking the terminals connected to wireless ap the terminals connected to a wireless ap will be shown for each ssid on the whole map. note: some devices connected to a wireless ap may not display, depending on the firmware version of the wireless ap. the ssids that are set for the wireless ap are shown as icons underthe wireless ap icon.terminals connected by an ssid are displayed undertheir respective ssid icon.the following information regarding the ssidis displayed to the right of the ssid icon. ssid name frequency band note: the items displayed cannot be switched.</div><div class="display_word">10. Checking the terminals connected to wireless AP The terminals connected to a wireless AP will be shown for each SSID on the whole map. Note: Some devices connected to a wireless AP may not display, depending on the firmware version of the wireless AP. The SSIDs that are set for the wireless AP are shown as icons underthe wireless AP icon.Terminals connected by an SSID are displayed undertheir respective SSID icon.The following information regarding the SSIDis displayed to the right of the SSID icon. SSID name Frequency band Note: The items displayed cannot be switched.</div></div><div id="gui_en_management_bkup_rstr"><div class="search_title" docfname="gui_en_management_bkup_rstr" doctitle="Backup" link="#title-box">Backup / Restoration</div><div class="search_word">backup / restoration</div><div class="display_word">Backup / Restoration</div></div><div id="gui_en_management_bkup_rstr"><div class="search_title" docfname="gui_en_management_bkup_rstr" doctitle="Backup" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for the backup and restoration of the configuration of the entire device. if the device fails, you can restore the backup file to a newly prepared device to restore the settings. the backup file contains the following information. startup-config and its associated information setting values for the startup-config select command setting values for the boot prioritize sd command do not perform any operation (such as the write commandor the erase startup-config command) related to the config whileperforming the backup or restoration on this page. in a stack configuration, you need to back up and restore for each switch.</div><div class="display_word">1. Summary This page is for the backup and restoration of the configuration of the entire device. If the device fails, you can restore the backup file to a newly prepared device to restore the settings. The backup file contains the following information. Startup-config and its associated information Setting values for the startup-config select command Setting values for the boot prioritize sd command Do not perform any operation (such as the write commandor the erase startup-config command) related to the CONFIG whileperforming the backup or restoration on this page. In a stack configuration, you need to back up and restore for each switch.</div></div><div id="gui_en_management_bkup_rstr"><div class="search_title" docfname="gui_en_management_bkup_rstr" doctitle="Backup" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the backup/restoration.</div><div class="display_word">2. Top page This is the top page for the backup/restoration.</div></div><div id="gui_en_management_bkup_rstr"><div class="search_title" docfname="gui_en_management_bkup_rstr" doctitle="Backup" link="#backup">2.1. Backup</div><div class="search_word">2.1. backup press the "next" button to display the page for backing up the system.</div><div class="display_word">2.1. Backup Press the "Next" button to display the page for backing up the system.</div></div><div id="gui_en_management_bkup_rstr"><div class="search_title" docfname="gui_en_management_bkup_rstr" doctitle="Backup" link="#restoration">2.2. Restoration</div><div class="search_word">2.2. restoration press the "next" button to display the page for restoring the system.</div><div class="display_word">2.2. Restoration Press the "Next" button to display the page for restoring the system.</div></div><div id="gui_en_management_bkup_rstr"><div class="search_title" docfname="gui_en_management_bkup_rstr" doctitle="Backup" link="#section3">3. Backup page</div><div class="search_word">3. backup page this page is for downloading the configuration of the entire device as a backup file. press the "ok" button to download the backup file for the device that you are currently accessing. if the stack function is disabled, the execution screen is displayed. press the "ok" button to download thebackup file for the device that you are currently accessing. if the stack function is enabled, theinput screen is displayed. select the device to back up, and press the"confirm" button. then press the "ok" button on the execution screen todownload the selected device’s backup file. the following is an explanation of the screen when the stack function is enabled.</div><div class="display_word">3. Backup page This page is for downloading the configuration of the entire device as a backup file. Press the "OK" button to download the backup file for the device that you are currently accessing. If the stack function is disabled, the execution screen is displayed. Press the "OK" button to download thebackup file for the device that you are currently accessing. If the stack function is enabled, theinput screen is displayed. Select the device to back up, and press the"Confirm" button. Then press the "OK" button on the execution screen todownload the selected device’s backup file. The following is an explanation of the screen when the stack function is enabled.</div></div><div id="gui_en_management_bkup_rstr"><div class="search_title" docfname="gui_en_management_bkup_rstr" doctitle="Backup" link="#backup_2">3.1. Backup</div><div class="search_word">3.1. backup stack id of the device to back up select the stack id of the device to back up. the model name and the serial number of the selected device are displayed.</div><div class="display_word">3.1. Backup Stack ID of the device to back up Select the stack ID of the device to back up. The model name and the serial number of the selected device are displayed.</div></div><div id="gui_en_management_bkup_rstr"><div class="search_title" docfname="gui_en_management_bkup_rstr" doctitle="Backup" link="#section4">4. Restoration page</div><div class="search_word">4. restoration page this page is for restoring the backup configuration of the entire device to this device. when you have entered the settings, press the "confirm"button. if there are no mistakes in the input content confirmationscreen, press the "ok" button. when the restoration is complete, the device automatically restarts.</div><div class="display_word">4. Restoration page This page is for restoring the backup configuration of the entire device to this device. When you have entered the settings, press the "Confirm"button. If there are no mistakes in the input content confirmationscreen, press the "OK" button. When the restoration is complete, the device automatically restarts.</div></div><div id="gui_en_management_bkup_rstr"><div class="search_title" docfname="gui_en_management_bkup_rstr" doctitle="Backup" link="#restoration_2">4.1. Restoration</div><div class="search_word">4.1. restoration backup file select the backup file to restore.</div><div class="display_word">4.1. Restoration Backup file Select the backup file to restore.</div></div><div id="gui_en_management_bkup_rstr"><div class="search_title" docfname="gui_en_management_bkup_rstr" doctitle="Backup" link="#section5">5. Restoration procedure in a stack configuration</div><div class="search_word">5. restoration procedure in a stack configuration when the stack function is enabled, the configuration for the entire device cannot restore from this page. if some of the devices that make up the stack fail and need to replace them, follow the procedure below to restore them. update the firmware of the newly prepared device to the same version as the device to be replaced. after updating the firmware, access this page and restore the configuration you have backed up before for the entire device. after the restoration and restart are complete, turn off the power. then connect the device to the main switch in operation, and turn on the power.</div><div class="display_word">5. Restoration procedure in a stack configuration When the stack function is enabled, the configuration for the entire device cannot restore from this page. If some of the devices that make up the stack fail and need to replace them, follow the procedure below to restore them. Update the firmware of the newly prepared device to the same version as the device to be replaced. After updating the firmware, access this page and restore the configuration you have backed up before for the entire device. After the restoration and restart are complete, turn off the power. Then connect the device to the main switch in operation, and turn on the power.</div></div><div id="gui_en_management_cablediag"><div class="search_title" docfname="gui_en_management_cablediag" doctitle="Cable" link="#title-box">Cable diagnostics</div><div class="search_word">cable diagnostics</div><div class="display_word">Cable diagnostics</div></div><div id="gui_en_management_cablediag"><div class="search_title" docfname="gui_en_management_cablediag" doctitle="Cable" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for diagnosing whether cable failures have occurred. the cable diagnostics can check failures of the lan cables connected to the lan ports of this unit. you can use this to troubleshoot network problems or as a simple cable check when setting up a network. please note that this diagnostics is a simplified function, so it cannot detect as precisely as a specialized device. cables should be longer than 10m for correct diagnostics. the diagnostics does not work correctly if the port is supplying poe power.</div><div class="display_word">1. Summary This page is for diagnosing whether cable failures have occurred. The cable diagnostics can check failures of the LAN cables connected to the LAN ports of this unit. You can use this to troubleshoot network problems or as a simple cable check when setting up a network. Please note that this diagnostics is a simplified function, so it cannot detect as precisely as a specialized device. Cables should be longer than 10m for correct diagnostics. The diagnostics does not work correctly if the port is supplying PoE power.</div></div><div id="gui_en_management_cablediag"><div class="search_title" docfname="gui_en_management_cablediag" doctitle="Cable" link="#section2">2. Top page</div><div class="search_word">2. top page this top page is for cable diagnostics.</div><div class="display_word">2. Top page This top page is for cable diagnostics.</div></div><div id="gui_en_management_cablediag"><div class="search_title" docfname="gui_en_management_cablediag" doctitle="Cable" link="#cable_diagnostics">2.1. Cable diagnostics</div><div class="search_word">2.1. cable diagnostics press the "ok" button to perform the cable diagnostics. the following ports are not able to perform cable diagnostics. the port interface is disabled the port is shut down by loop detection the port is shut down by spanning tree the port is shut down by port security violation the port under diagnostics will temporarily linke down. press the "discard diagnostics results" button to delete the last cable diagnostics results. the cable diagnostics results show the following items. port the port performed diagnostics. result the status of cable connected to lan port. ok : electrically connected. open : a target device is not connected, or the cable is damaged. short : the cable is shorted. distance to the cable failure point if the result is "open" or "short", displays the distance from the lan port to the cable failure point in meters.</div><div class="display_word">2.1. Cable diagnostics Press the "OK" button to perform the cable diagnostics. The following ports are not able to perform cable diagnostics. The port interface is disabled The port is shut down by loop detection The port is shut down by spanning tree The port is shut down by port security violation The port under diagnostics will temporarily linke down. Press the "Discard diagnostics results" button to delete the last cable diagnostics results. The cable diagnostics results show the following items. Port The port performed diagnostics. Result The status of cable connected to LAN port. OK : Electrically connected. Open : A target device is not connected, or the cable is damaged. Short : The cable is shorted. Distance to the cable failure point If the result is "Open" or "Short", displays the distance from the LAN port to the cable failure point in meters.</div></div><div id="gui_en_management_command"><div class="search_title" docfname="gui_en_management_command" doctitle="Command" link="#title-box">Command execution</div><div class="search_word">command execution</div><div class="display_word">Command execution</div></div><div id="gui_en_management_command"><div class="search_title" docfname="gui_en_management_command" doctitle="Command" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can perform operations related to command execution.</div><div class="display_word">1. Summary In this page you can perform operations related to command execution.</div></div><div id="gui_en_management_command"><div class="search_title" docfname="gui_en_management_command" doctitle="Command" link="#section2">2. Command execution page</div><div class="search_word">2. command execution page in this page you can execute commands and acquire the results ofcommand execution. after entering the command in the command entryfield, press the "ok" button to execute the command. if you press the"clear" button, the contents of the command entry field are cleared.</div><div class="display_word">2. Command execution page In this page you can execute commands and acquire the results ofcommand execution. After entering the command in the command entryfield, press the "OK" button to execute the command. If you press the"Clear" button, the contents of the command entry field are cleared.</div></div><div id="gui_en_management_command"><div class="search_title" docfname="gui_en_management_command" doctitle="Command" link="#command_execution">2.1. Command execution</div><div class="search_word">2.1. command execution command input in the command entry field, enter the setting in console command format (abbreviated input is not accepted). you can enter multiple commands together by separating them with line-returns. execution always starts with the specially-privileged exec mode (enable). enter the mode change command each time. for details on commands to enter, refer to the command reference and to the information provided on the network device product information page and yamaha network devices technical documentation . the following commands cannot be entered. ping ping6 telnet ssh ssh-server host key generate reload restart cold start firmware-update execute firmware-update sd execute startup-config select erase startup-config copy running-config startup-config copy startup-config show config show running-config show startup-config show history show tech-support backup system restore system remote-login stack enable stack disable no stack stack subnet no stack subnet boot prioritize sd no boot prioritize sd quit disable logout exit ( when in special privilege exec mode ) copy radius-server local crypto pki generate ca no crypto pki generate ca system-diagnostics on-demand execute command execution result displays the command execution result. success …​ shown if the command executed successfully. error …​ shown if the command you entered could not be executed. prohibited …​ shown if a prohibited command was entered. command execution log the console log is output as the command execution record. the command execution log will not necessarilyalways show the identical result as when the console setting operationwas executed. by pressing the "obtain as text file" button, you can acquire the contents of the command execution log as a text file. the name of the acquired file is "command_yyyymmddhhmmss.txt". yyyy …​ a.d. ( 4 digit ) mm …​ month ( 2 digit ) dd …​ day ( 2 digit ) hh …​ hours ( 2 digit ) mm …​ minutes ( 2 digit ) ss …​ seconds ( 2 digit )</div><div class="display_word">2.1. Command execution Command input In the command entry field, enter the setting in console command format (abbreviated input is not accepted). You can enter multiple commands together by separating them with line-returns. Execution always starts with the specially-privileged EXEC mode (enable). Enter the mode change command each time. For details on commands to enter, refer to the command reference and to the information provided on the Network device product information page and Yamaha Network Devices Technical Documentation . The following commands cannot be entered. ping ping6 telnet ssh ssh-server host key generate reload restart cold start firmware-update execute firmware-update sd execute startup-config select erase startup-config copy running-config startup-config copy startup-config show config show running-config show startup-config show history show tech-support backup system restore system remote-login stack enable stack disable no stack stack subnet no stack subnet boot prioritize sd no boot prioritize sd quit disable logout exit ( When in special privilege EXEC mode ) copy radius-server local crypto pki generate ca no crypto pki generate ca system-diagnostics on-demand execute Command execution result Displays the command execution result. Success …​ Shown if the command executed successfully. Error …​ Shown if the command you entered could not be executed. Prohibited …​ Shown if a prohibited command was entered. Command execution log The console log is output as the command execution record. The command execution log will not necessarilyalways show the identical result as when the console setting operationwas executed. By pressing the "Obtain as text file" button, you can acquire the contents of the command execution log as a text file. The name of the acquired file is "command_YYYYMMDDhhmmss.txt". YYYY …​ A.D. ( 4 Digit ) MM …​ Month ( 2 Digit ) DD …​ Day ( 2 Digit ) hh …​ Hours ( 2 Digit ) mm …​ Minutes ( 2 Digit ) ss …​ Seconds ( 2 Digit )</div></div><div id="gui_en_management_community"><div class="search_title" docfname="gui_en_management_community" doctitle="Community" link="#title-box">Community</div><div class="search_word">community</div><div class="display_word">Community</div></div><div id="gui_en_management_community"><div class="search_title" docfname="gui_en_management_community" doctitle="Community" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring snmp community settings.</div><div class="display_word">1. Summary This page is for configuring SNMP community settings.</div></div><div id="gui_en_management_community"><div class="search_title" docfname="gui_en_management_community" doctitle="Community" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for community.</div><div class="display_word">2. Top page This is the top page for Community.</div></div><div id="gui_en_management_community"><div class="search_title" docfname="gui_en_management_community" doctitle="Community" link="#list_of_communities">2.1. List of communities</div><div class="search_word">2.1. list of communities information for the currently registered community are shown. the table items are explained below. community name registered communities name are shown. access mode access mode set to community are shown. if you press the "new" button, a page appears in which you can create a new community. if you press the "setting" button, a page appears in which you can edit the settings of the selected community. if you press the "delete" button, all communities whose check box has a check mark will be deleted. if you check the "delete from relatedsettings as well" check box in the delete dialog, the following settingis changed with the deletion of the community. deletes the trap destination settings specifying the community to be deleted. deletes the clients that can access the snmp server settings specifying the community to be deleted. up to 16 communities can be registered.</div><div class="display_word">2.1. List of communities Information for the currently registered community are shown. The table items are explained below. Community name Registered communities name are shown. Access mode Access mode set to community are shown. If you press the "New" button, a page appears in which you can create a new community. If you press the "Setting" button, a page appears in which you can edit the settings of the selected community. If you press the "Delete" button, all communities whose check box has a check mark will be deleted. If you check the "Delete from relatedsettings as well" check box in the delete dialog, the following settingis changed with the deletion of the community. Deletes the trap destination settings specifying the community to be deleted. Deletes the clients that can access the SNMP server settings specifying the community to be deleted. Up to 16 communities can be registered.</div></div><div id="gui_en_management_community"><div class="search_title" docfname="gui_en_management_community" doctitle="Community" link="#community">3. Community setting page</div><div class="search_word">3. community setting page this page is for configuring snmp community settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Community setting page This page is for configuring SNMP community settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_community"><div class="search_title" docfname="gui_en_management_community" doctitle="Community" link="#community_settings">3.1. Community settings</div><div class="search_word">3.1. community settings community name sets the community name. characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . up to 32 characters can be inputted. change the settings related to the community accordingly. the following setting is changed accordingly to the change of community settings. change the community name used in the trap destination settings to the changed name. change the community name used in the clients that can access the snmp server settings to the changed name. this item will be displayed only when changing settings. if you check the check box, the "detail display" button will be displayed on the confirmation page. press the "detail display" button to open the dialog with the following information. trap destination settings which the community name to be changed. access mode select the access mode of the community from the list below. readonly only read to mib is allowed. readwrite both read and write to mib are allowed.</div><div class="display_word">3.1. Community settings Community name Sets the community name. Characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . Up to 32 characters can be inputted. Change the settings related to the community accordingly. The following setting is changed accordingly to the change of community settings. Change the community name used in the trap destination settings to the changed name. Change the community name used in the clients that can access the SNMP server settings to the changed name. This item will be displayed only when changing settings. If you check the check box, the "Detail display" button will be displayed on the confirmation page. Press the "Detail display" button to open the dialog with the following information. Trap destination settings which the community name to be changed. Access mode Select the access mode of the community from the list below. ReadOnly Only read to MIB is allowed. ReadWrite Both read and write to MIB are allowed.</div></div><div id="gui_en_management_config"><div class="search_title" docfname="gui_en_management_config" doctitle="CONFIG" link="#title-box">CONFIG management</div><div class="search_word">config management</div><div class="display_word">CONFIG management</div></div><div id="gui_en_management_config"><div class="search_title" docfname="gui_en_management_config" doctitle="CONFIG" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can import and export config. this unit operates in accordance with its config file (settingsdata). a config file consists of a combination of multiple commands.</div><div class="display_word">1. Summary In this page you can import and export CONFIG. This unit operates in accordance with its CONFIG file (settingsdata). A CONFIG file consists of a combination of multiple commands.</div></div><div id="gui_en_management_config"><div class="search_title" docfname="gui_en_management_config" doctitle="CONFIG" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for config management. you can start the process of importing a config, or the process of exporting a config.</div><div class="display_word">2. Top page This is the top page for CONFIG management. You can start the process of importing a CONFIG, or the process of exporting a CONFIG.</div></div><div id="gui_en_management_config"><div class="search_title" docfname="gui_en_management_config" doctitle="CONFIG" link="#import">2.1. Import</div><div class="search_word">2.1. import press the "next" button to display a page where you can import a config.</div><div class="display_word">2.1. Import Press the "Next" button to display a page where you can import a CONFIG.</div></div><div id="gui_en_management_config"><div class="search_title" docfname="gui_en_management_config" doctitle="CONFIG" link="#export">2.2. Export</div><div class="search_word">2.2. export press the "next" button to display a page where you can export a config.</div><div class="display_word">2.2. Export Press the "Next" button to display a page where you can export a CONFIG.</div></div><div id="gui_en_management_config"><div class="search_title" docfname="gui_en_management_config" doctitle="CONFIG" link="#section3">3. Import page</div><div class="search_word">3. import page in this page, a config from the pc can be copied to internal non-volatile memory, updating the config. when you have entered the settings, press the "confirm" button.if there are no mistakes in the input content confirmation screen, press the "ok" button. if the currently used config is the same as theimport-destination config, the unit restarts automatically after theimport has ended successfully. if you want to start up with a config file that is not currently being used, change the setting using the startup-config select command before restarting.</div><div class="display_word">3. Import page In this page, a CONFIG from the PC can be copied to internal non-volatile memory, updating the CONFIG. When you have entered the settings, press the "Confirm" button.If there are no mistakes in the input content confirmation screen, press the "OK" button. If the currently used CONFIG is the same as theimport-destination CONFIG, the unit restarts automatically after theimport has ended successfully. If you want to start up with a CONFIG file that is not currently being used, change the setting using the startup-config select command before restarting.</div></div><div id="gui_en_management_config"><div class="search_title" docfname="gui_en_management_config" doctitle="CONFIG" link="#import_config">3.1. Import CONFIG</div><div class="search_word">3.1. import config import method select the import method from the following options. import all settings (.zip) import information such as a config file and a l2ms agent config together. you cannot be used when using yno manager for access. import a config file (.txt) import a config file. import a l2ms agent config (.bin) import a l2ms agent config. settings to import press the "select a file" button to display the file selection dialog box. you can use the settings obtained on the export page. import-destination select the import-destination config in internal non-volatile memory. cannot be changed when the stack function is enabled. (the currently used config is selected.)</div><div class="display_word">3.1. Import CONFIG Import method Select the import method from the following options. Import all settings (.zip) Import information such as a CONFIG file and a L2MS agent CONFIG together. You cannot be used when using YNO manager for access. Import a CONFIG file (.txt) Import a CONFIG file. Import a L2MS agent CONFIG (.bin) Import a L2MS agent CONFIG. Settings to import Press the "Select a file" button to display the file selection dialog box. You can use the settings obtained on the export page. Import-destination Select the import-destination CONFIG in internal non-volatile memory. Cannot be changed when the stack function is enabled. (The currently used CONFIG is selected.)</div></div><div id="gui_en_management_config"><div class="search_title" docfname="gui_en_management_config" doctitle="CONFIG" link="#section4">4. Export page</div><div class="search_word">4. export page in this page you can copy a config from internal non-volatile memory to the pc. when you have finished entry, check the entered content and press the "ok" button.</div><div class="display_word">4. Export page In this page you can copy a CONFIG from internal non-volatile memory to the PC. When you have finished entry, check the entered content and press the "OK" button.</div></div><div id="gui_en_management_config"><div class="search_title" docfname="gui_en_management_config" doctitle="CONFIG" link="#export_config">4.1. Export CONFIG</div><div class="search_word">4.1. export config export method select the export method from the following options. export all settings (.zip) export information such as a config file and a l2ms agent config together. you cannot be used when using yno manager for access. export a config file (.txt) export a config file. export a l2ms agent config (.bin) export a l2ms agent config. settings to export select the config in internal non-volatile memory that you want to export. cannot be changed when the stack function is enabled. (the currently used config is selected.)</div><div class="display_word">4.1. Export CONFIG Export method Select the export method from the following options. Export all settings (.zip) Export information such as a CONFIG file and a L2MS agent CONFIG together. You cannot be used when using YNO manager for access. Export a CONFIG file (.txt) Export a CONFIG file. Export a L2MS agent CONFIG (.bin) Export a L2MS agent CONFIG. Settings to export Select the CONFIG in internal non-volatile memory that you want to export. Cannot be changed when the stack function is enabled. (The currently used CONFIG is selected.)</div></div><div id="gui_en_management_dante"><div class="search_title" docfname="gui_en_management_dante" doctitle="Dante" link="#title-box">Dante optimization</div><div class="search_word">dante optimization</div><div class="display_word">Dante optimization</div></div><div id="gui_en_management_dante"><div class="search_title" docfname="gui_en_management_dante" doctitle="Dante" link="#section1">1. Summary</div><div class="search_word">1. summary this is the page for operations related to the dante optimization settings. the dante optimization settings can be made manually or by means of auto-configure via lldp.</div><div class="display_word">1. Summary This is the page for operations related to the Dante optimization settings. The Dante optimization settings can be made manually or by means of auto-configure via LLDP.</div></div><div id="gui_en_management_dante"><div class="search_title" docfname="gui_en_management_dante" doctitle="Dante" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for configuring the dante optimization.</div><div class="display_word">2. Top page This is the top page for configuring the Dante optimization.</div></div><div id="gui_en_management_dante"><div class="search_title" docfname="gui_en_management_dante" doctitle="Dante" link="#dante_optimization">2.1. Dante optimization</div><div class="search_word">2.1. dante optimization the current settings for the auto-configure via lldp function are displayed. press "next" button to begin the steps for dante optimization settings. press "setting" button to display the page where the settings for the auto-configure via lldp function can be modified. this function cannot be used when the stack function is enabled.</div><div class="display_word">2.1. Dante optimization The current settings for the auto-configure via LLDP function are displayed. Press "Next" button to begin the steps for Dante optimization settings. Press "Setting" button to display the page where the settings for the auto-configure via LLDP function can be modified. This function cannot be used when the stack function is enabled.</div></div><div id="gui_en_management_dante"><div class="search_title" docfname="gui_en_management_dante" doctitle="Dante" link="#multicast_basic_settings_system">2.2. Multicast basic settings (System)</div><div class="search_word">2.2. multicast basic settings (system) displays the configuration for unknown multicast frames for the entire system. the table items are explained below. processing method for unknown multicast frames displays the processing method of unknown multicast frames. excluded frames from discarding (for all vlans) displays excluded frames from discarding when configured to discard unknown multicast frames.</div><div class="display_word">2.2. Multicast basic settings (System) Displays the configuration for unknown multicast frames for the entire system. The table items are explained below. Processing method for unknown multicast frames Displays the processing method of unknown multicast frames. Excluded frames from discarding (for all VLANs) Displays excluded frames from discarding when configured to discard unknown multicast frames.</div></div><div id="gui_en_management_dante"><div class="search_title" docfname="gui_en_management_dante" doctitle="Dante" link="#multicast_basic_settings_vlan_interface">2.3. Multicast basic settings (VLAN interface)</div><div class="search_word">2.3. multicast basic settings (vlan interface) displays the configuration for unknown multicast frames for each vlan. the table items are explained below. vlan id vlan id is displayed. unknown multicast frame displays the processing method for unknown multicast frames for the target vlan. excluded frames from discarding displays the frames to be excluded fromdiscarding when unknown multicast frames are configured to be discardedin the target vlan.</div><div class="display_word">2.3. Multicast basic settings (VLAN interface) Displays the configuration for unknown multicast frames for each VLAN. The table items are explained below. VLAN ID VLAN ID is displayed. Unknown multicast frame Displays the processing method for unknown multicast frames for the target VLAN. Excluded frames from discarding Displays the frames to be excluded fromdiscarding when unknown multicast frames are configured to be discardedin the target VLAN.</div></div><div id="gui_en_management_dante"><div class="search_title" docfname="gui_en_management_dante" doctitle="Dante" link="#qos_settings">2.4. QoS settings</div><div class="search_word">2.4. qos settings displays the qos settings for the entire system. the table items are explained below. qos function displays whether the qos function is enabled. cos - transmit queue mapping table displays the transmit queue id settings corresponding to the cos value. dscp - transmit queue mapping table displays the transmit queue id settings corresponding to the dscp value.</div><div class="display_word">2.4. QoS settings Displays the QoS settings for the entire system. The table items are explained below. QoS function Displays whether the QoS function is enabled. CoS - transmit queue mapping table Displays the transmit queue ID settings corresponding to the CoS value. DSCP - transmit queue mapping table Displays the transmit queue ID settings corresponding to the DSCP value.</div></div><div id="gui_en_management_dante"><div class="search_title" docfname="gui_en_management_dante" doctitle="Dante" link="#manual">3. Manual settings page</div><div class="search_word">3. manual settings page this is the page for the dante optimization settings. select vlan interfaces, and then press the "confirm"button. if there are no mistakes in the input content of theconfirmation screen, press the "ok" button.</div><div class="display_word">3. Manual settings page This is the page for the Dante optimization settings. Select VLAN interfaces, and then press the "Confirm"button. If there are no mistakes in the input content of theconfirmation screen, press the "OK" button.</div></div><div id="gui_en_management_dante"><div class="search_title" docfname="gui_en_management_dante" doctitle="Dante" link="#manual_settings">3.1. Manual settings</div><div class="search_word">3.1. manual settings vlan interface press the "select" button to display the "vlan interface list" dialog box. you can select vlan interfaces in the "vlan interface list" dialog by checking the check boxes and pressing the "ok" button.</div><div class="display_word">3.1. Manual settings VLAN interface Press the "Select" button to display the "VLAN interface list" dialog box. You can select VLAN interfaces in the "VLAN interface list" dialog by checking the check boxes and pressing the "OK" button.</div></div><div id="gui_en_management_dante"><div class="search_title" docfname="gui_en_management_dante" doctitle="Dante" link="#auto">4. Auto-configure via LLDP function page</div><div class="search_word">4. auto-configure via lldp function page this is the page for setting auto-configure via lldp function. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Auto-configure via LLDP function page This is the page for setting auto-configure via LLDP function. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_dante"><div class="search_title" docfname="gui_en_management_dante" doctitle="Dante" link="#auto_configure_via_lldp_function">4.1. Auto-configure via LLDP function</div><div class="search_word">4.1. auto-configure via lldp function auto-configure via lldp function select whether to enable the auto-configure via lldp function settings, from the options below. enable disable</div><div class="display_word">4.1. Auto-configure via LLDP function Auto-configure via LLDP function Select whether to enable the auto-configure via LLDP function settings, from the options below. Enable Disable</div></div><div id="gui_en_management_find_switch"><div class="search_title" docfname="gui_en_management_find_switch" doctitle="Find" link="#title-box">Find this switch</div><div class="search_word">find this switch</div><div class="display_word">Find this switch</div></div><div id="gui_en_management_find_switch"><div class="search_title" docfname="gui_en_management_find_switch" doctitle="Find" link="#section1">1. Summary</div><div class="search_word">1. summary the "find this switch" function uses the led installed in this product to inform you of the installation location of the productin an easy-to-understand manner. please use it when you want to check the installationlocation of the product or when you want to show the operation target to the workers at the site. while this function is running, the led will be in the following states, respectively. led : the leds on all ports flash orange.</div><div class="display_word">1. Summary The "Find this switch" function uses the LED installed in this product to inform you of the installation location of the productin an easy-to-understand manner. Please use it when you want to check the installationlocation of the product or when you want to show the operation target to the workers at the site. While this function is running, the LED will be in the following states, respectively. LED : The LEDs on all ports flash orange.</div></div><div id="gui_en_management_find_switch"><div class="search_title" docfname="gui_en_management_find_switch" doctitle="Find" link="#section2">2. "Find this switch" execution page</div><div class="search_word">2. "find this switch" execution page this page is for executing the "find this switch" function.</div><div class="display_word">2. "Find this switch" execution page This page is for executing the "Find this switch" function.</div></div><div id="gui_en_management_find_switch"><div class="search_title" docfname="gui_en_management_find_switch" doctitle="Find" link="#find_this_switch">2.1. Find this switch</div><div class="search_word">2.1. find this switch displays the execution status of "find this switch" function. you can start the "find this switch" function by pressing the "start" button when it is stopped. you can stop the "find this switch" function by pressing the "stop" button when it is running. press the "start" button to display the dialog and select the following items to start the notification. notification method select the type of notification from the following. blink the port led blinks the leds on all ports in orange while the function is running. it cannot be selected when the current led mode is off mode. you can configure the led mode in "management → unit settings→ led mode setting". notification period select the time to continue the notification from the following. 30 seconds 1 minutes 3 minutes 5 minutes 10 minutes 1 hours after pressing the "ok" button, the notification will be automatically stopped when the duration of notification expires.</div><div class="display_word">2.1. Find this switch Displays the execution status of "Find this switch" function. You can start the "Find this switch" function by pressing the "Start" button when it is stopped. You can stop the "Find this switch" function by pressing the "Stop" button when it is running. Press the "Start" button to display the dialog and select the following items to start the notification. Notification method Select the Type of notification from the following. Blink the port LED Blinks the LEDs on all ports in orange while the function is running. It cannot be selected when the Current LED mode is OFF mode. You can configure the LED mode in "Management → Unit settings→ LED mode setting". Notification period Select the time to continue the notification from the following. 30 Seconds 1 Minutes 3 Minutes 5 Minutes 10 Minutes 1 Hours After pressing the "OK" button, the notification will be automatically stopped when the Duration of notification expires.</div></div><div id="gui_en_management_firm"><div class="search_title" docfname="gui_en_management_firm" doctitle="Update" link="#title-box">Update firmware</div><div class="search_word">update firmware</div><div class="display_word">Update firmware</div></div><div id="gui_en_management_firm"><div class="search_title" docfname="gui_en_management_firm" doctitle="Update" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can perform operations related to firmware update.</div><div class="display_word">1. Summary In this page you can perform operations related to firmware update.</div></div><div id="gui_en_management_firm"><div class="search_title" docfname="gui_en_management_firm" doctitle="Update" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for firmware update. you can start the procedure for updating the firmware via thenetwork. various settings for updating the firmware via the network aredisplayed.</div><div class="display_word">2. Top page This is the top page for firmware update. You can start the procedure for updating the firmware via thenetwork. Various settings for updating the firmware via the network aredisplayed.</div></div><div id="gui_en_management_firm"><div class="search_title" docfname="gui_en_management_firm" doctitle="Update" link="#firmware_update_information">2.1. Firmware update information</div><div class="search_word">2.1. firmware update information displays the firmware revision and basic settings. displays the firmware revision for the next start-up if a restart is pending after a firmware update. press the "setting" button to access a page where you can change the settings.</div><div class="display_word">2.1. Firmware update information Displays the firmware revision and basic settings. Displays the firmware revision for the next start-up if a restart is pending after a firmware update. Press the "Setting" button to access a page where you can change the settings.</div></div><div id="gui_en_management_firm"><div class="search_title" docfname="gui_en_management_firm" doctitle="Update" link="#update_firmware_from_pc">2.2. Update firmware from PC</div><div class="search_word">2.2. update firmware from pc when you press the "next" button, the procedure for updating the firmware from the pc will be started.</div><div class="display_word">2.2. Update firmware from PC When you press the "Next" button, the procedure for updating the firmware from the PC will be started.</div></div><div id="gui_en_management_firm"><div class="search_title" docfname="gui_en_management_firm" doctitle="Update" link="#update_firmware_via_network">2.3. Update firmware via network</div><div class="search_word">2.3. update firmware via network when you press the "next" button, the procedure for updating the firmware via the network will be started. various settings for updating the firmware via the network are displayed. press the "setting" button to access a page where you can change the settings.</div><div class="display_word">2.3. Update firmware via network When you press the "Next" button, the procedure for updating the firmware via the network will be started. Various settings for updating the firmware via the network are displayed. Press the "Setting" button to access a page where you can change the settings.</div></div><div id="gui_en_management_firm"><div class="search_title" docfname="gui_en_management_firm" doctitle="Update" link="#section3">3. Firmware update basic settings page</div><div class="search_word">3. firmware update basic settings page this page is for configuring the basic settings for the firmware update. when you have entered the settings, press the "confirm" button.if there are no mistakes in the input content confirmation screen, press the "ok" button.</div><div class="display_word">3. Firmware update basic settings page This page is for configuring the basic settings for the firmware update. When you have entered the settings, press the "Confirm" button.If there are no mistakes in the input content confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_firm"><div class="search_title" docfname="gui_en_management_firm" doctitle="Update" link="#firmware_update_basic_settings">3.1. Firmware update basic settings</div><div class="search_word">3.1. firmware update basic settings restart timing after the update specify the restart timing after the firmware update. restart method after the update if you want the system to restart after the firmware update in a stack configuration automatically, you can specify whethereach switch restarts in sequence or simultaneously. this item cannot be configured when the stack function is disabled.</div><div class="display_word">3.1. Firmware update basic settings Restart timing after the update Specify the restart timing after the firmware update. Restart method after the update If you want the system to restart after the firmware update in a stack configuration automatically, you can specify whethereach switch restarts in sequence or simultaneously. This item cannot be configured when the stack function is disabled.</div></div><div id="gui_en_management_firm"><div class="search_title" docfname="gui_en_management_firm" doctitle="Update" link="#section4">4. Update firmware from PC page</div><div class="search_word">4. update firmware from pc page in this page you can specify the firmware file placed on the pcfrom which you are accessing the web gui, and perform the firmwareupdate. in "select file," select the firmware file that you want to usefor the update, and press the "confirm" button. if there are no mistakes in the confirmation screen, press the "ok" button.</div><div class="display_word">4. Update firmware from PC page In this page you can specify the firmware file placed on the PCfrom which you are accessing the web GUI, and perform the firmwareupdate. In "Select file," select the firmware file that you want to usefor the update, and press the "Confirm" button. If there are no mistakes in the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_firm"><div class="search_title" docfname="gui_en_management_firm" doctitle="Update" link="#update_firmware_from_pc_2">4.1. Update firmware from PC</div><div class="search_word">4.1. update firmware from pc specify update file selects the firmware file used for the update restart after the update specify whether or not to restart after the firmware update automatically. the timing for restarting depends on the restart timing after the update in the firmware update basic settings .</div><div class="display_word">4.1. Update firmware from PC Specify update file Selects the firmware file used for the update Restart after the update Specify whether or not to restart after the firmware update automatically. The timing for restarting depends on the Restart timing after the update in the Firmware update basic settings .</div></div><div id="gui_en_management_firm"><div class="search_title" docfname="gui_en_management_firm" doctitle="Update" link="#section5">5. Update firmware via network page</div><div class="search_word">5. update firmware via network page in this page you can download a firmware file from a web server,and perform the firmware update. this function lets you easily performthe entire process of checking for the latest firmware, downloading it,and updating the firmware. when you open the page, the revision of the firmware file on the web server is automatically checked. if the download url is the yamaha website and an updateablefirmware revision is found. the "ok" button displays a guide to thesoftware license agreement website. please read the contents on thewebsite and press the "ok" button if you agree to the terms. press the"ok" button to start downloading the firmware file from the webserver.</div><div class="display_word">5. Update firmware via network page In this page you can download a firmware file from a web server,and perform the firmware update. This function lets you easily performthe entire process of checking for the latest firmware, downloading it,and updating the firmware. When you open the page, the revision of the firmware file on the web server is automatically checked. If the download URL is the Yamaha website and an updateablefirmware revision is found. The "OK" button displays a guide to thesoftware license agreement website. Please read the contents on thewebsite and press the "OK" button if you agree to the terms. Press the"OK" button to start downloading the firmware file from the webserver.</div></div><div id="gui_en_management_firm"><div class="search_title" docfname="gui_en_management_firm" doctitle="Update" link="#update_firmware_via_network_2">5.1. Update firmware via network</div><div class="search_word">5.1. update firmware via network current firmware revision the revision of the currently-used firmware file is shown. firmware revision available for update updatable revisions of the firmware files on the web server are shown. restart after the update specify whether or not to restart after the firmware update automatically. the timing for restarting depends on the restart timing after the update in the firmware update basic settings .</div><div class="display_word">5.1. Update firmware via network Current firmware revision The revision of the currently-used firmware file is shown. Firmware revision available for update Updatable revisions of the firmware files on the web server are shown. Restart after the update Specify whether or not to restart after the firmware update automatically. The timing for restarting depends on the Restart timing after the update in the Firmware update basic settings .</div></div><div id="gui_en_management_firm"><div class="search_title" docfname="gui_en_management_firm" doctitle="Update" link="#section6">6. Update via network settings page</div><div class="search_word">6. update via network settings page in this page you can make various settings for updating the firmware via the network. when you have entered the settings, press the "confirm" button.if there are no mistakes in the input content confirmation screen, press the "ok" button.</div><div class="display_word">6. Update via network settings page In this page you can make various settings for updating the firmware via the network. When you have entered the settings, press the "Confirm" button.If there are no mistakes in the input content confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_firm"><div class="search_title" docfname="gui_en_management_firm" doctitle="Update" link="#update_via_network_settings">6.1. Update via network settings</div><div class="search_word">6.1. update via network settings download source url this is the setting of the url at which the firmware is located. http proxy server this is the http proxy server setting used to download the firmware via the network. revision downgrade this setting permits or forbids rewriting to an older version of firmware. timeout this setting specifies the timeout time during the process of updating the firmware via the network.</div><div class="display_word">6.1. Update via network settings Download source URL This is the setting of the URL at which the firmware is located. HTTP proxy server This is the HTTP proxy server setting used to download the firmware via the network. Revision downgrade This setting permits or forbids rewriting to an older version of firmware. Timeout This setting specifies the timeout time during the process of updating the firmware via the network.</div></div><div id="gui_en_management_lldp"><div class="search_title" docfname="gui_en_management_lldp" doctitle="LLDP" link="#title-box">LLDP</div><div class="search_word">lldp</div><div class="display_word">LLDP</div></div><div id="gui_en_management_lldp"><div class="search_title" docfname="gui_en_management_lldp" doctitle="LLDP" link="#section1">1. Summary</div><div class="search_word">1. summary</div><div class="display_word">1. Summary</div></div><div id="gui_en_management_lldp"><div class="search_title" docfname="gui_en_management_lldp" doctitle="LLDP" link="#this_page_is_for_changing_lldp_settings_and_viewing_neighbor_information_obtained_by_lldp">1.1. This page is for changing LLDP settings and viewing neighbor information obtained by LLDP.</div><div class="search_word">1.1. this page is for changing lldp settings and viewing neighbor information obtained by lldp. * lldp (link layer discovery protocol) is a protocol to collect neighbor information. in this unit, following operations aresupported. unit information is periodically transmitted to neighboring devices. reception of information from neighboring devices. display of received neighbor information.</div><div class="display_word">1.1. This page is for changing LLDP settings and viewing neighbor information obtained by LLDP. * LLDP (Link Layer Discovery Protocol) is a protocol to collect neighbor information. In this unit, following operations aresupported. Unit information is periodically transmitted to neighboring devices. Reception of information from neighboring devices. Display of received neighbor information.</div></div><div id="gui_en_management_lldp"><div class="search_title" docfname="gui_en_management_lldp" doctitle="LLDP" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the lldp.</div><div class="display_word">2. Top page This is the top page for the LLDP.</div></div><div id="gui_en_management_lldp"><div class="search_title" docfname="gui_en_management_lldp" doctitle="LLDP" link="#neighbor_information_list">2.1. Neighbor information list</div><div class="search_word">2.1. neighbor information list pressing the "next" button displays a page where acquired neighbor information can be viewed. the "next" button is disabled if the lldp function is disabled.</div><div class="display_word">2.1. Neighbor information list Pressing the "Next" button displays a page where acquired neighbor information can be viewed. The "Next" button is disabled if the LLDP function is disabled.</div></div><div id="gui_en_management_lldp"><div class="search_title" docfname="gui_en_management_lldp" doctitle="LLDP" link="#system_settings">2.2. System settings</div><div class="search_word">2.2. system settings displays the lldp settings for the system. the table items are explained below. lldp displays whether lldp is enabled or disabled for the entire system. auto-configure via lldp function the current settings for the auto-configure via lldp function are displayed. system name displays the system name to be notified by lldp. system description displays the system description to be notified by lldp. press the "setting" button to display the page for configuring the system.</div><div class="display_word">2.2. System settings Displays the LLDP settings for the system. The table items are explained below. LLDP Displays whether LLDP is enabled or disabled for the entire system. Auto-configure via LLDP function The current settings for the auto-configure via LLDP function are displayed. System name Displays the system name to be notified by LLDP. System description Displays the system description to be notified by LLDP. Press the "Setting" button to display the page for configuring the system.</div></div><div id="gui_en_management_lldp"><div class="search_title" docfname="gui_en_management_lldp" doctitle="LLDP" link="#interface_settings">2.3. Interface settings</div><div class="search_word">2.3. interface settings displays the lldp settings for the interface. the table items are explained below. port displays the interface name. lldp frame transmission and reception displays the lldp frame transmission and reception mode for the target interface. press the "setting" button to display the page for configuring the selected interface. press the "specify all" button to configure the settings for all interfaces with the check box selected. press the "return to defaults" button to initialize the settings for all interfaces with the check box selected.</div><div class="display_word">2.3. Interface settings Displays the LLDP settings for the interface. The table items are explained below. Port Displays the interface name. LLDP frame transmission and reception Displays the LLDP frame transmission and reception mode for the target interface. Press the "Setting" button to display the page for configuring the selected interface. Press the "Specify all" button to configure the settings for all interfaces with the check box selected. Press the "Return to defaults" button to initialize the settings for all interfaces with the check box selected.</div></div><div id="gui_en_management_lldp"><div class="search_title" docfname="gui_en_management_lldp" doctitle="LLDP" link="#neighbor_info_list">3. Neighbor information list page</div><div class="search_word">3. neighbor information list page this page displays a summary of neighbor information obtained by lldp. displays ports where neighbor information was received and part of that information.</div><div class="display_word">3. Neighbor information list page This page displays a summary of neighbor information obtained by LLDP. Displays ports where neighbor information was received and part of that information.</div></div><div id="gui_en_management_lldp"><div class="search_title" docfname="gui_en_management_lldp" doctitle="LLDP" link="#neighbor_information_list_2">3.1. Neighbor information list</div><div class="search_word">3.1. neighbor information list displays a list of neighbor information obtained by lldp. up to 1000 neighbor information is displayed. pressing the "detail" button displays a page for viewing details about the selected neighbor information. you can search neighbor information from the "search" box. press to execute the search. press to clear the search. you can use regular expressions shown below in search keywords. lowercase and capital letters are treated the same for keywords. syntax explanation a the character "a" abc the characters "abc" [abc] one character, either "a", "b" or "c" [a-c] one character between "a" and "c" [^abc] an arbitrary character that is neither "a", "b" or "c" . an arbitrary character a+ at least one "a" character a* at least zero "a" characters a? zero or one "a" character ^a a string that begins with "a" a$ a string that ends with "a" abc|def|ghi “abc”, “def” or “ghi” a{2} two "a" characters (aa) a{2,} two or more "a" characters (aa, aaa, aaaa…​) a{2,3} two to three "a" characters (aa, aaa) \b word breaks, such as spaces \b any character besides \b \d an arbitrary number (same as [0-9]) \d any character besides numbers (same as [^0-9]) \s single breaking character \s any single character besides \s \w alphanumeric characters including underlines (same as [a-za-z0-9_]) \w any character besides \w press to update information to the latest information. the number of search results to display at one time can be selected by pressing "display number" on the "select" menu. if the number of neighbor informationresults exceeds the "display number" setting, the range of neighborinformation results can be changed by pressing . press the sort switch to sort by each item. with default settings, results are sorted in ascending order of the receiving port. press the sort switch again to toggle between ascending and descending order. "receiving ports" are sorted in order of port number. other items are sorted alphabetically based on the character string.</div><div class="display_word">3.1. Neighbor information list Displays a list of neighbor information obtained by LLDP. Up to 1000 neighbor information is displayed. Pressing the "Detail" button displays a page for viewing details about the selected neighbor information. You can search neighbor information from the "Search" box. Press to execute the search. Press to clear the search. You can use regular expressions shown below in search keywords. Lowercase and capital letters are treated the same for keywords. Syntax Explanation A The character "A" ABC The characters "ABC" [ABC] One character, either "A", "B" or "C" [A-C] One character between "A" and "C" [^ABC] An arbitrary character that is neither "A", "B" or "C" . An arbitrary character A+ At least one "A" character A* At least zero "A" characters A? Zero or one "A" character ^A A string that begins with "A" A$ A string that ends with "A" ABC|DEF|GHI “ABC”, “DEF” or “GHI” A{2} Two "A" characters (AA) A{2,} Two or more "A" characters (AA, AAA, AAAA…​) A{2,3} Two to three "A" characters (AA, AAA) \b Word breaks, such as spaces \B Any character besides \b \d An arbitrary number (same as [0-9]) \D Any character besides numbers (same as [^0-9]) \s Single breaking character \S Any single character besides \s \w Alphanumeric characters including underlines (same as [A-Za-z0-9_]) \W Any character besides \w Press to update information to the latest information. The number of search results to display at one time can be selected by pressing "Display number" on the "Select" menu. If the number of neighbor informationresults exceeds the "display number" setting, the range of neighborinformation results can be changed by pressing . Press the sort switch to sort by each item. With default settings, results are sorted in ascending order of the receiving port. Press the sort switch again to toggle between ascending and descending order. "Receiving ports" are sorted in order of port number. Other items are sorted alphabetically based on the character string.</div></div><div id="gui_en_management_lldp"><div class="search_title" docfname="gui_en_management_lldp" doctitle="LLDP" link="#neighbor_info_detail">4. Neighbor information detail page</div><div class="search_word">4. neighbor information detail page this page displays details for neighbor information selected on the neighbor information page.</div><div class="display_word">4. Neighbor information detail page This page displays details for neighbor information selected on the neighbor information page.</div></div><div id="gui_en_management_lldp"><div class="search_title" docfname="gui_en_management_lldp" doctitle="LLDP" link="#details_of_neighbor_information">4.1. Details of neighbor information</div><div class="search_word">4.1. details of neighbor information each information item in the obtained neighbor information is displayed. if obtained neighbor information contains no information for an item, "-" is displayed. for details on the information displayed, refer to yamaha network devices technical documentation .</div><div class="display_word">4.1. Details of neighbor information Each information item in the obtained neighbor information is displayed. If obtained neighbor information contains no information for an item, "-" is displayed. For details on the information displayed, refer to Yamaha Network Devices Technical Documentation .</div></div><div id="gui_en_management_lldp"><div class="search_title" docfname="gui_en_management_lldp" doctitle="LLDP" link="#system_setting">5. System settings page</div><div class="search_word">5. system settings page this page is for configuring the lldp settings for the system. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">5. System settings page This page is for configuring the LLDP settings for the system. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_lldp"><div class="search_title" docfname="gui_en_management_lldp" doctitle="LLDP" link="#system_settings_2">5.1. System settings</div><div class="search_word">5.1. system settings lldp specify whether to enable or disable lldp for the entire system. auto-configure via lldp function specify whether to enable or disable auto-configure via lldp function. system name specify the system name to be notified by lldp. enter up to 255 single-byte alphanumeric characters/symbols, excluding the ? symbol. system description specify the system description to be notified by lldp. enter up to 255 single-byte alphanumeric characters/symbols, excluding the ? symbol.</div><div class="display_word">5.1. System settings LLDP Specify whether to enable or disable LLDP for the entire system. Auto-configure via LLDP function Specify whether to enable or disable Auto-configure via LLDP function. System name Specify the system name to be notified by LLDP. Enter up to 255 single-byte alphanumeric characters/symbols, excluding the ? symbol. System description Specify the system description to be notified by LLDP. Enter up to 255 single-byte alphanumeric characters/symbols, excluding the ? symbol.</div></div><div id="gui_en_management_lldp"><div class="search_title" docfname="gui_en_management_lldp" doctitle="LLDP" link="#interface_setting">6. Interface settings page</div><div class="search_word">6. interface settings page this page is for configuring the lldp settings for the system. you can also change the detailed settings by pressing the "advanced settings" button. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">6. Interface settings page This page is for configuring the LLDP settings for the system. You can also change the detailed settings by pressing the "Advanced settings" button. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_lldp"><div class="search_title" docfname="gui_en_management_lldp" doctitle="LLDP" link="#interface_settings_2">6.1. Interface settings</div><div class="search_word">6.1. interface settings port specify whether to enable or disable lldp for the entire system. lldp frame transmission and reception select the operation for lldp frame transmission and reception from the following options. enabled enables lldp frame transmission and reception. select direction to enable from the following items. transmit & receive transmit receive disabled disables lldp frame transmission and reception. option tlv to send select the information to be sent by lldp from the following items. basic management tlv sends administrative information about the system, such as the system name and the functions it supports. ieee 802.1 tlv sends information about the vlan and link aggregation of the port. ieee 802.3 tlv sends information about the auto negotiation and poe of the port. lldp-med tlv sends information about network policy and extended poe of the port. lldp frame transmission interval specifies the transmission interval of lldp frames in terms of seconds. input a transmission interval of lldp frames from 5 to 3600. hold time (ttl) of device information sent by lldp specify a hold multiplier to decide a hold time ( ttl ). input a hold multiplier from 1 to 100. the upper limit of hold time (ttl) is 65535. fast transmission period setting specify a transmission interval and a send number of lldp frames during the fast transmission period. input a transmission interval from 1 to 3600. input a send number from 1 to 8. time from stop sending lldp frames to reinitialization specify the waiting time from when lldp is disabled to when lldp can be re-enabled on the port. input a time from stop sending lldp frames to reinitialization from 1 to 8. type of management address sent by lldp select management address type from the following items. ip address mac address maximum number of managed devices specifies the maximum number of managed devices. input a maximum number of managed devices from 1 to 1000.</div><div class="display_word">6.1. Interface settings Port Specify whether to enable or disable LLDP for the entire system. LLDP frame transmission and reception Select the operation for LLDP frame transmission and reception from the following options. Enabled Enables LLDP frame transmission and reception. Select direction to enable from the following items. Transmit & Receive Transmit Receive Disabled Disables LLDP frame transmission and reception. Option TLV to send Select the information to be sent by LLDP from the following items. Basic management TLV Sends administrative information about the system, such as the system name and the functions it supports. IEEE 802.1 TLV Sends information about the VLAN and link aggregation of the port. IEEE 802.3 TLV Sends information about the auto negotiation and PoE of the port. LLDP-MED TLV Sends information about network policy and extended PoE of the port. LLDP frame transmission interval Specifies the transmission interval of LLDP frames in terms of seconds. Input a transmission interval of LLDP frames from 5 to 3600. Hold time (TTL) of device information sent by LLDP Specify a hold multiplier to decide a hold time ( TTL ). Input a hold multiplier from 1 to 100. The upper limit of Hold time (TTL) is 65535. Fast transmission period setting Specify a transmission interval and a send number of LLDP frames during the fast transmission period. Input a transmission interval from 1 to 3600. Input a send number from 1 to 8. Time from stop sending LLDP frames to reinitialization Specify the waiting time from when LLDP is disabled to when LLDP can be re-enabled on the port. Input a time from stop sending LLDP frames to reinitialization from 1 to 8. Type of Management address sent by LLDP Select management address type from the following items. IP address MAC address Maximum number of managed devices Specifies the maximum number of managed devices. Input a maximum number of managed devices from 1 to 1000.</div></div><div id="gui_en_management_mail"><div class="search_title" docfname="gui_en_management_mail" doctitle="Mail" link="#title-box">Mail notification</div><div class="search_word">mail notification</div><div class="display_word">Mail notification</div></div><div id="gui_en_management_mail"><div class="search_title" docfname="gui_en_management_mail" doctitle="Mail" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can make settings related to mail notification. when a mail notification is received, mail is automatically sent to theassigned recipient when the specified conditions are met. first use the "new" button in "registered mail server list" toregister the mail server of the recipient. after registering this, usethe "new" button in "mail notification settings list" to make mailnotification settings.</div><div class="display_word">1. Summary In this page you can make settings related to mail notification. When a mail notification is received, mail is automatically sent to theassigned recipient when the specified conditions are met. First use the "New" button in "Registered mail server list" toregister the mail server of the recipient. After registering this, usethe "New" button in "Mail notification settings list" to make mailnotification settings.</div></div><div id="gui_en_management_mail"><div class="search_title" docfname="gui_en_management_mail" doctitle="Mail" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for mail notifications.</div><div class="display_word">2. Top page This is the top page for mail notifications.</div></div><div id="gui_en_management_mail"><div class="search_title" docfname="gui_en_management_mail" doctitle="Mail" link="#list_of_registered_mail_servers">2.1. List of registered mail servers</div><div class="search_word">2.1. list of registered mail servers information for the currently registered mail server (smtp server) is shown. you can use the "new" button at the top of the list to add settings. if you want to change the settings, press the"settings" button located at the right of the table. a page for changing the settings appears, allowing you to change the settings. if you want to delete settings, select the settingthat you want to delete, and press the "delete" button located above the list. a confirmation dialog box appears; press the "delete" button todelete the setting. up to 10 mail servers can be registered.</div><div class="display_word">2.1. List of registered mail servers Information for the currently registered mail server (SMTP server) is shown. You can use the "New" button at the top of the list to add settings. If you want to change the settings, press the"Settings" button located at the right of the table. A page for changing the settings appears, allowing you to change the settings. If you want to delete settings, select the settingthat you want to delete, and press the "Delete" button located above the list. A confirmation dialog box appears; press the "Delete" button todelete the setting. Up to 10 mail servers can be registered.</div></div><div id="gui_en_management_mail"><div class="search_title" docfname="gui_en_management_mail" doctitle="Mail" link="#list_of_mail_notification_settings">2.2. List of mail notification settings</div><div class="search_word">2.2. list of mail notification settings the currently specified mail notification settings are shown. you can use the "new" button at the top of the list to add settings. if you want to change the settings, press the"settings" button located at the right of the table. a page for changing the settings appears, allowing you to change the settings. if you want to delete settings, select the settingthat you want to delete, and press the "delete" button located above the list. a confirmation dialog box appears; press the "delete" button todelete the setting. if you want to do mail sending test, press the "next"button located at "sending test" item. a confirmation dialog boxappears; press the "ok" button to do mail sending test.</div><div class="display_word">2.2. List of mail notification settings The currently specified mail notification settings are shown. You can use the "New" button at the top of the list to add settings. If you want to change the settings, press the"Settings" button located at the right of the table. A page for changing the settings appears, allowing you to change the settings. If you want to delete settings, select the settingthat you want to delete, and press the "Delete" button located above the list. A confirmation dialog box appears; press the "Delete" button todelete the setting. If you want to do mail sending test, press the "Next"button located at "Sending test" item. A confirmation dialog boxappears; press the "OK" button to do mail sending test.</div></div><div id="gui_en_management_mail"><div class="search_title" docfname="gui_en_management_mail" doctitle="Mail" link="#mail_server_setting">3. Mail server settings page</div><div class="search_word">3. mail server settings page this page lets you make settings for the recipient’s mailserver (smtp server). check the items that you specified, and then press the "confirm" button. if there are no mistakes in the input content ofthe confirmation screen, press the "ok" button.</div><div class="display_word">3. Mail server settings page This page lets you make settings for the recipient’s mailserver (SMTP server). Check the items that you specified, and then press the "Confirm" button. If there are no mistakes in the input content ofthe confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_mail"><div class="search_title" docfname="gui_en_management_mail" doctitle="Mail" link="#list_of_registered_mail_servers_2">3.1. List of registered mail servers</div><div class="search_word">3.1. list of registered mail servers id this is the identifying number of the mail server settings. it is assigned automatically. account identification name specify the mail server’s account identification name. for convenience, specify a name that will be easy to recognize. you can use up to 64 single-byte characters. this can be omitted. smtp server address enter the ip address or domain name of the smtp server used when sending mail. you can use up to 64 single-byte characters. smtp server port number enter the smtp server’s port number. if "submission port (port number 587)" is checked, the submission port, which is port number 587, is specified. encrypting smtp this setting determines whether to encrypt smtp with ssl when sending mail. selecting "not encrypt" is to use smtp for sending mail. selecting "encrypt with ssl (over ssl)" is to use smtps (smtp over ssl) for sending mail, so that smtp is encrypted with ssl. it is recommended to set 465 for "smtp server port number". selecting "encrypt with ssl (starttls)" is to use smtps (starttls) for sending mail, so that smtp is encrypted with ssl. for starttls, communication is encrypted only if the smtp server supports encryption using ssl. encryption using ssl is not available when setting an ipv6 address as the smtp server address. smtp authentication select from the drop-down list box whether to authenticate with the smtp server. to authenticate, enter the following settings. user name this setting determines the user name used when authenticating to the smtp server. up to 64 single-byte characters are allowed. password this setting determines the password used when authenticating to the smtp server. up to 64 single-byte characters are allowed.</div><div class="display_word">3.1. List of registered mail servers ID This is the identifying number of the mail server settings. It is assigned automatically. Account identification name Specify the mail server’s account identification name. For convenience, specify a name that will be easy to recognize. You can use up to 64 single-byte characters. This can be omitted. SMTP server address Enter the IP address or domain name of the SMTP server used when sending mail. You can use up to 64 single-byte characters. SMTP server port number Enter the SMTP server’s port number. If "Submission port (port number 587)" is checked, the submission port, which is port number 587, is specified. Encrypting SMTP This setting determines whether to encrypt SMTP with SSL when sending mail. Selecting "Not encrypt" is to use SMTP for sending mail. Selecting "Encrypt with SSL (over SSL)" is to use SMTPS (SMTP over SSL) for sending mail, so that SMTP is encrypted with SSL. It is recommended to set 465 for "SMTP server port number". Selecting "Encrypt with SSL (STARTTLS)" is to use SMTPS (STARTTLS) for sending mail, so that SMTP is encrypted with SSL. For STARTTLS, communication is encrypted only if the SMTP server supports encryption using SSL. Encryption using SSL is not available when setting an IPv6 address as the SMTP server address. SMTP authentication Select from the drop-down list box whether to authenticate with the SMTP server. To authenticate, enter the following settings. User name This setting determines the user name used when authenticating to the SMTP server. Up to 64 single-byte characters are allowed. Password This setting determines the password used when authenticating to the SMTP server. Up to 64 single-byte characters are allowed.</div></div><div id="gui_en_management_mail"><div class="search_title" docfname="gui_en_management_mail" doctitle="Mail" link="#mail_template_setting">4. Mail notification settings page</div><div class="search_word">4. mail notification settings page in this page you can make mail notification settings. you canspecify the transmission source and the recipient address of mailnotifications. check the items that you specified, and then press the"confirm" button. if there are no mistakes in the input content of theconfirmation screen, press the "ok" button.</div><div class="display_word">4. Mail notification settings page In this page you can make mail notification settings. You canspecify the transmission source and the recipient address of mailnotifications. Check the items that you specified, and then press the"Confirm" button. If there are no mistakes in the input content of theconfirmation screen, press the "OK" button.</div></div><div id="gui_en_management_mail"><div class="search_title" docfname="gui_en_management_mail" doctitle="Mail" link="#mail_notification_settings">4.1. Mail notification settings</div><div class="search_word">4.1. mail notification settings id this is the identifying number of the mail notification settings. it is assigned automatically. source (from) specify the sender’s mail address of the mail that will be sent. smtp server: select the smtp server used when sending the mail. mail address: enter the sender’s mail address of the mail that will be sent. you can use up to 256 single-byte characters.however, you cannot use symbols other than underline (_), hyphen (-),dot (.), and at-sign (@). destination (to) enter the recipient’s mail address of the mail that will be sent. you can register up to four items; the mail is sent to all of the registered mail addresses. you can use up to 256 single-byte characters.however, you cannot use symbols other than underline (_), hyphen (-),dot (.), and at-sign (@). this setting does not affect the mail send function of the radius server. subject specify the subject of the mail that will be sent. you can use up to 128 single-byte characters. if you select "use specified subject," the subject name will be the specified subject. this setting does not affect the mail send function of the radius server. notification content the contents of the notification are specified as follows. lan map error detection this notification will be made only if this unit is operating as an l2ms manager. select the lan map events to be notified from the following. device abnormality loop detection sfp optical rx level abnormality transmission queue monitoring poe supply snapshot duplication of l2ms managers status notification for terminal monitoring the change in status monitored by the device monitoring function will be notified. stack error detection failure information of the stack function will be notified. this setting does not affect the mail send function of the radius server. mail transmission wait time specify the time by which mail transmission is delayed after the notification event occurs. if other notification events occur during this wait time, those notifications are combined and sent in a single email. this setting does not affect the mail send function of the radius server.</div><div class="display_word">4.1. Mail notification settings ID This is the identifying number of the mail notification settings. It is assigned automatically. Source (From) Specify the sender’s mail address of the mail that will be sent. SMTP server: Select the SMTP server used when sending the mail. Mail address: Enter the sender’s mail address of the mail that will be sent. You can use up to 256 single-byte characters.However, you cannot use symbols other than underline (_), hyphen (-),dot (.), and at-sign (@). Destination (To) Enter the recipient’s mail address of the mail that will be sent. You can register up to four items; the mail is sent to all of the registered mail addresses. You can use up to 256 single-byte characters.However, you cannot use symbols other than underline (_), hyphen (-),dot (.), and at-sign (@). This setting does not affect the mail send function of the RADIUS server. Subject Specify the subject of the mail that will be sent. You can use up to 128 single-byte characters. If you select "Use specified subject," the subject name will be the specified subject. This setting does not affect the mail send function of the RADIUS server. Notification content The contents of the notification are specified as follows. LAN map error detection This notification will be made only if this unit is operating as an L2MS manager. Select the LAN map events to be notified from the following. Device abnormality Loop detection SFP optical Rx level abnormality Transmission queue monitoring PoE supply Snapshot Duplication of L2MS managers Status notification for terminal monitoring The change in status monitored by the device monitoring function will be notified. Stack error detection Failure information of the stack function will be notified. This setting does not affect the mail send function of the RADIUS server. Mail transmission wait time Specify the time by which mail transmission is delayed after the notification event occurs. If other notification events occur during this wait time, those notifications are combined and sent in a single email. This setting does not affect the mail send function of the RADIUS server.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#title-box">Unit settings</div><div class="search_word">unit settings</div><div class="display_word">Unit settings</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#section1">1. Summary</div><div class="search_word">1. summary various settings can be specified for the unit.</div><div class="display_word">1. Summary Various settings can be specified for the unit.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for unit settings. a description of each setting is shown.</div><div class="display_word">2. Top page This is the top page for unit settings. A description of each setting is shown.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#unit_name_setting">2.1. Unit name setting</div><div class="search_word">2.1. unit name setting displays the unit name that is set. press the "setting" button to access a page where you can change the settings.</div><div class="display_word">2.1. Unit name setting Displays the unit name that is set. Press the "Setting" button to access a page where you can change the settings.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#led_mode_setting">2.2. LED mode setting</div><div class="search_word">2.2. led mode setting displays the led mode that is set. press the "setting" button to access a page where you can change the settings.</div><div class="display_word">2.2. LED mode setting Displays the LED mode that is set. Press the "Setting" button to access a page where you can change the settings.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#time_zone_setting">2.3. Time zone setting</div><div class="search_word">2.3. time zone setting displays the time zone setting. press the "setting" button to access a page where you can change the settings.</div><div class="display_word">2.3. Time zone setting Displays the time zone setting. Press the "Setting" button to access a page where you can change the settings.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#current_date_and_time_setting">2.4. Current date and time setting</div><div class="search_word">2.4. current date and time setting the current date and time specified for this unit are shown. press the "setting" button to access a page where you can change the settings.</div><div class="display_word">2.4. Current date and time setting The current date and time specified for this unit are shown. Press the "Setting" button to access a page where you can change the settings.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#date_and_time_synchronization_setting">2.5. Date and time synchronization setting</div><div class="search_word">2.5. date and time synchronization setting the ntp server that is queried at the specified time and date synchronization interval is shown. press the "next" button to access a page where you can synchronize the time. press the "setting" button to access a page where you can change the settings.</div><div class="display_word">2.5. Date and time synchronization setting The NTP server that is queried at the specified time and date synchronization interval is shown. Press the "Next" button to access a page where you can synchronize the time. Press the "Setting" button to access a page where you can change the settings.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#section3">3. Unit name setting page</div><div class="search_word">3. unit name setting page in this page you can set the unit name. when you have entered the settings, press the "confirm" button.if there are no mistakes in the input content confirmation screen, press the "ok" button.</div><div class="display_word">3. Unit name setting page In this page you can set the unit name. When you have entered the settings, press the "Confirm" button.If there are no mistakes in the input content confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#unit_name_setting_2">3.1. Unit name setting</div><div class="search_word">3.1. unit name setting device name enter an arbitrary character string for use as the hostname. enter up to 63 single-byte alphanumeric characters/symbols, with the following exceptions: ?</div><div class="display_word">3.1. Unit name setting Device name Enter an arbitrary character string for use as the hostname. Enter up to 63 single-byte alphanumeric characters/symbols, with the following exceptions: ?</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#section4">4. LED mode setting page</div><div class="search_word">4. led mode setting page in this page you can set the led mode. when you have entered the settings, press the "confirm" button.if there are no mistakes in the input content confirmation screen, press the "ok" button.</div><div class="display_word">4. LED mode setting page In this page you can set the LED mode. When you have entered the settings, press the "Confirm" button.If there are no mistakes in the input content confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#led_mode_setting_2">4.1. LED mode setting</div><div class="search_word">4.1. led mode setting led mode select the led mode from the following. link/act mode led indicator lights will illuminate, flash, or switch off depending on the lan port status. poe mode led indicator lights will illuminate or switch off depending on the poe supply status. cannot be selected when the stack function is enabled vlan mode led indicator lights will illuminate or switch off depending on the vlan belonging status. cannot be selected when the stack function is enabled status mode led indicator lights will illuminate, flash, or switch off depending on the error status of the following functions. loop detection sfp optical reception level monitoring poe supply cannot be selected when the stack function is enabled off mode led always stays off.</div><div class="display_word">4.1. LED mode setting LED mode Select the LED mode from the following. LINK/ACT mode LED indicator lights will illuminate, flash, or switch OFF depending on the LAN port status. PoE mode LED indicator lights will illuminate or switch OFF depending on the PoE supply status. Cannot be selected when the stack function is enabled VLAN mode LED indicator lights will illuminate or switch OFF depending on the VLAN belonging status. Cannot be selected when the stack function is enabled STATUS mode LED indicator lights will illuminate, flash, or switch OFF depending on the error status of the following functions. Loop detection SFP optical reception level monitoring PoE supply Cannot be selected when the stack function is enabled OFF mode LED always stays off.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#section5">5. Time zone setting page</div><div class="search_word">5. time zone setting page this page is for configuring the settings related to time zone. when you have entered the settings, press the "confirm" button.if there are no mistakes in the input content confirmation screen, press the "ok" button.</div><div class="display_word">5. Time zone setting page This page is for configuring the settings related to time zone. When you have entered the settings, press the "Confirm" button.If there are no mistakes in the input content confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#time_zone_setting_2">5.1. Time zone setting</div><div class="search_word">5.1. time zone setting time zone select the time zone from the following. utc jst difference from gmt ( -12:00 to +13:00 ) daylight saving time select the daylight saving time operation from the following. disable enable time zone during daylight saving time during daylight saving time, the time zone name specified in this item is displayed as the time zone abbreviation. enter up to 7 single-byte alphanumeric characters. daylight saving time period specify the date and time that daylight saving time starts and ends. if you want to execute the specified period only once, select by date and enter the following. date enter in the format yyyy/mm/dd. time enter in the format hh:mm. if you want to execute the specified period annually, select recurring and enter the following. month the input range is from january to december. week select from the following. first second third fourth last day of week select from the following. sunday monday tuesday wednesday thursday friday saturday time enter in the format hh:mm. daylight saving time offset specify the time to advance at the start of daylight saving time. the input range is from 1 to 1440 minutes.</div><div class="display_word">5.1. Time zone setting Time zone Select the time zone from the following. UTC JST Difference from GMT ( -12:00 to +13:00 ) Daylight saving time Select the daylight saving time operation from the following. Disable Enable Time zone during daylight saving time During daylight saving time, the time zone name specified in this item is displayed as the time zone abbreviation. Enter up to 7 single-byte alphanumeric characters. Daylight saving time period Specify the date and time that daylight saving time starts and ends. If you want to execute the specified period only once, select By date and enter the following. Date Enter in the format YYYY/MM/DD. Time Enter in the format hh:mm. If you want to execute the specified period annually, select Recurring and enter the following. Month The input range is from January to December. Week Select from the following. First Second Third Fourth Last Day of week Select from the following. Sunday Monday Tuesday Wednesday Thursday Friday Saturday Time Enter in the format hh:mm. Daylight saving time offset Specify the time to advance at the start of daylight saving time. The input range is from 1 to 1440 minutes.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#section6">6. Current date and time setting page</div><div class="search_word">6. current date and time setting page in this page you can set the current date and time. when you have entered the settings, press the "confirm" button.if there are no mistakes in the input content confirmation screen, press the "ok" button.</div><div class="display_word">6. Current date and time setting page In this page you can set the current date and time. When you have entered the settings, press the "Confirm" button.If there are no mistakes in the input content confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#current_date_and_time_setting_2">6.1. Current date and time setting</div><div class="search_word">6.1. current date and time setting current time in the "year/month/day" box, enter the date in yyyy/mm/dd format. when you move the focus to the box, a calendar is displayed. you can select a date to enter that date in the box. you can also enter this manually. in the "hours:minutes:seconds" box, enter the time in hh:mm:ss format. when you move the focus to the box, a calendar is displayed. you can select a date to enter that date in the box. you can also enter this manually.</div><div class="display_word">6.1. Current date and time setting Current time In the "Year/Month/Day" box, enter the date in YYYY/MM/DD format. When you move the focus to the box, a calendar is displayed. You can select a date to enter that date in the box. You can also enter this manually. In the "hours:minutes:seconds" box, enter the time in hh:mm:ss format. When you move the focus to the box, a calendar is displayed. You can select a date to enter that date in the box. You can also enter this manually.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#section7">7. Date and time synchronization page</div><div class="search_word">7. date and time synchronization page in this page you can synchronize the time with an ntp server. when you press the "ok" button, the time is synchronized with the ntp server that is specified as the query destination.</div><div class="display_word">7. Date and time synchronization page In this page you can synchronize the time with an NTP server. When you press the "OK" button, the time is synchronized with the NTP server that is specified as the query destination.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#section8">8. Date and time synchronization setting page</div><div class="search_word">8. date and time synchronization setting page in this page you can make settings for synchronization with an ntp server. when you have entered the settings, press the "confirm" button.if there are no mistakes in the input content confirmation screen, press the "ok" button.</div><div class="display_word">8. Date and time synchronization setting page In this page you can make settings for synchronization with an NTP server. When you have entered the settings, press the "Confirm" button.If there are no mistakes in the input content confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_main"><div class="search_title" docfname="gui_en_management_main" doctitle="Unit" link="#date_and_time_synchronization_setting_2">8.1. Date and time synchronization setting</div><div class="search_word">8.1. date and time synchronization setting date and time synchronization interval specifies the interval at which time is synchronized with the ntp server. you can choose from the following as the synchronization interval. unused 1 hour — 24 hours the default value is 1 hour ntp server to query enter the host name or ip address of the ntp server that will perform synchronization. up to two ntp servers can be configured.</div><div class="display_word">8.1. Date and time synchronization setting Date and time synchronization interval Specifies the interval at which time is synchronized with the NTP server. You can choose from the following as the synchronization interval. Unused 1 hour — 24 hours The default value is 1 hour NTP server to query Enter the host name or IP address of the NTP server that will perform synchronization. Up to two NTP servers can be configured.</div></div><div id="gui_en_management_mib"><div class="search_title" docfname="gui_en_management_mib" doctitle="MIB" link="#title-box">MIB</div><div class="search_word">mib</div><div class="display_word">MIB</div></div><div id="gui_en_management_mib"><div class="search_title" docfname="gui_en_management_mib" doctitle="MIB" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring mib settings.</div><div class="display_word">1. Summary This page is for configuring MIB settings.</div></div><div id="gui_en_management_mib"><div class="search_title" docfname="gui_en_management_mib" doctitle="MIB" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for mib.</div><div class="display_word">2. Top page This is the top page for MIB.</div></div><div id="gui_en_management_mib"><div class="search_title" docfname="gui_en_management_mib" doctitle="MIB" link="#management_information_settings">2.1. Management information settings</div><div class="search_word">2.1. management information settings the contents of the management information settings are shown. press the "setting" button to access a page where you can change the settings.</div><div class="display_word">2.1. Management information settings The contents of the Management information settings are shown. Press the "Setting" button to access a page where you can change the settings.</div></div><div id="gui_en_management_mib"><div class="search_title" docfname="gui_en_management_mib" doctitle="MIB" link="#management_info">3. Management information setting page</div><div class="search_word">3. management information setting page this page is for configuring management information settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Management information setting page This page is for configuring Management information settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_mib"><div class="search_title" docfname="gui_en_management_mib" doctitle="MIB" link="#management_information_settings_2">3.1. Management information settings</div><div class="search_word">3.1. management information settings administrator information (syscontact) sets the string of administrator information (syscontact). the character string entered here is stored in the mib variable syscontact. characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . up to 255 characters can be inputted. installation site information (syslocation) sets the string of physical location information (syslocation). the character string entered here is stored in the mib variable syslocation. characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . up to 255 characters can be inputted.</div><div class="display_word">3.1. Management information settings Administrator information (sysContact) Sets the string of Administrator information (sysContact). The character string entered here is stored in the MIB variable sysContact. Characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . Up to 255 characters can be inputted. Installation site information (sysLocation) Sets the string of Physical location information (sysLocation). The character string entered here is stored in the MIB variable sysLocation. Characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . Up to 255 characters can be inputted.</div></div><div id="gui_en_management_reboot"><div class="search_title" docfname="gui_en_management_reboot" doctitle="Restart" link="#title-box">Restart and initialization</div><div class="search_word">restart and initialization</div><div class="display_word">Restart and initialization</div></div><div id="gui_en_management_reboot"><div class="search_title" docfname="gui_en_management_reboot" doctitle="Restart" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can restart this unit and return it to the factory-set state.</div><div class="display_word">1. Summary In this page you can restart this unit and return it to the factory-set state.</div></div><div id="gui_en_management_reboot"><div class="search_title" docfname="gui_en_management_reboot" doctitle="Restart" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for restart and initialization. here you can start the process of restarting this unit or returning it to the factory-set state.</div><div class="display_word">2. Top page This is the top page for restart and initialization. Here you can start the process of restarting this unit or returning it to the factory-set state.</div></div><div id="gui_en_management_reboot"><div class="search_title" docfname="gui_en_management_reboot" doctitle="Restart" link="#restart">2.1. Restart</div><div class="search_word">2.1. restart when you press the "next" button, the process of restarting this unit will begin.</div><div class="display_word">2.1. Restart When you press the "Next" button, the process of restarting this unit will begin.</div></div><div id="gui_en_management_reboot"><div class="search_title" docfname="gui_en_management_reboot" doctitle="Restart" link="#initialization">2.2. Initialization</div><div class="search_word">2.2. initialization when you press the "next" button, the process of returning this unit to the factory-set state will begin.</div><div class="display_word">2.2. Initialization When you press the "Next" button, the process of returning this unit to the factory-set state will begin.</div></div><div id="gui_en_management_reboot"><div class="search_title" docfname="gui_en_management_reboot" doctitle="Restart" link="#section3">3. Restart page</div><div class="search_word">3. restart page in this page you can restart this unit. when you press the "ok" button, the unit will restart. if the stack function is disabled, press the "ok" button to restart the unit. if the stack function is enabled, select the device to restartfrom the input screen and press the "confirm" button. then, press the"ok" button on the execute screen to restart the specified device. note that when you execute restart, the settings that were beingchanged will not be saved. in addition, the gui cannot be accessed until restart has completed.</div><div class="display_word">3. Restart page In this page you can restart this unit. When you press the "OK" button, the unit will restart. If the stack function is disabled, press the "OK" button to restart the unit. If the stack function is enabled, select the device to restartfrom the input screen and press the "Confirm" button. Then, press the"OK" button on the execute screen to restart the specified device. Note that when you execute restart, the settings that were beingchanged will not be saved. In addition, the GUI cannot be accessed until restart has completed.</div></div><div id="gui_en_management_reboot"><div class="search_title" docfname="gui_en_management_reboot" doctitle="Restart" link="#section4">4. Initialization page</div><div class="search_word">4. initialization page in this page you can return this unit to its factory-set state. after you have entered the privileged password, press the"confirm" button. confirm the content to be executed, and if you want to return this unit to its factory-set state, press the "ok" button. note that when the unit is returned to its factory-set state, all settings will return to their default values, including the address for accessing the gui. if the stack function is enabled, only the main switch is initialized.</div><div class="display_word">4. Initialization page In this page you can return this unit to its factory-set state. After you have entered the privileged password, press the"Confirm" button. Confirm the content to be executed, and if you want to return this unit to its factory-set state, press the "OK" button. Note that when the unit is returned to its factory-set state, all settings will return to their default values, including the address for accessing the GUI. If the stack function is enabled, only the main switch is initialized.</div></div><div id="gui_en_management_reboot"><div class="search_title" docfname="gui_en_management_reboot" doctitle="Restart" link="#initialization_2">4.1. Initialization</div><div class="search_word">4.1. initialization privileged password to return the unit to its factory-set state, enter the privileged password.</div><div class="display_word">4.1. Initialization Privileged password To return the unit to its factory-set state, enter the privileged password.</div></div><div id="gui_en_management_rmon_alarm"><div class="search_title" docfname="gui_en_management_rmon_alarm" doctitle="Alarm" link="#title-box">Alarm group</div><div class="search_word">alarm group</div><div class="display_word">Alarm group</div></div><div id="gui_en_management_rmon_alarm"><div class="search_title" docfname="gui_en_management_rmon_alarm" doctitle="Alarm" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring rmon alarm group settings. you cannot configure rmon function when the stack function is enabled.</div><div class="display_word">1. Summary This page is for configuring RMON alarm group settings. You cannot configure RMON function when the stack function is enabled.</div></div><div id="gui_en_management_rmon_alarm"><div class="search_title" docfname="gui_en_management_rmon_alarm" doctitle="Alarm" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the rmon alarm group.</div><div class="display_word">2. Top page This is the top page for the RMON alarm group.</div></div><div id="gui_en_management_rmon_alarm"><div class="search_title" docfname="gui_en_management_rmon_alarm" doctitle="Alarm" link="#alarm_group_settings">2.1. Alarm group settings</div><div class="search_word">2.1. alarm group settings displays a list of alarm group settings. the table items are explained below. index displays the index of alarm group. monitoring mib displays the mib specified to be monitored in the alarm group. monitoring port displays the port information of the monitoring mib. press the "new" button to display a page where you can create new settings for the alarm group. press the "setting" button to display a page where you can change the settings of the selected alarm group. if you press the "delete" button, all alarm groups whose check boxes are selected will be deleted. up to 1024 alarm group settings can be displayed.</div><div class="display_word">2.1. Alarm group settings Displays a list of alarm group settings. The table items are explained below. Index Displays the index of alarm group. Monitoring MIB Displays the MIB specified to be monitored in the alarm group. Monitoring port Displays the port information of the monitoring MIB. Press the "New" button to display a page where you can create new settings for the alarm group. Press the "Setting" button to display a page where you can change the settings of the selected alarm group. If you press the "Delete" button, all alarm groups whose check boxes are selected will be deleted. Up to 1024 alarm group settings can be displayed.</div></div><div id="gui_en_management_rmon_alarm"><div class="search_title" docfname="gui_en_management_rmon_alarm" doctitle="Alarm" link="#alarm_settings">3. Alarm group settings page</div><div class="search_word">3. alarm group settings page this page is for configuring rmon alarm group settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Alarm group settings page This page is for configuring RMON alarm group settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_rmon_alarm"><div class="search_title" docfname="gui_en_management_rmon_alarm" doctitle="Alarm" link="#alarm_group_settings_2">3.1. Alarm group settings</div><div class="search_word">3.1. alarm group settings index to create a new alarm group, set the index of the alarm group. the smallest index of unregistered alarm groups is entered as the initial value. the input range is 1 - 65535. an index that is already in use cannot be specified. this cannot be changed when changing the settings. monitoring mib object select mib object to be monitored. you can select a mib from those belonging to the index of ethernet statistics group you have enabled. sampling interval specify the sampling interval in seconds for the monitoring mib values. comparison method between sample value and the threshold select a comparison method between the value obtained by sampling and the threshold. upper threshold specify the upper threshold and event to be executed when the value exceeds the upper threshold. the input range is 1 - 2147483647. you can select an event to execute from registered event groups. lower threshold specify the lower threshold and event to be executed when the value falls below the lower threshold. the input range is 1 - 2147483647. you can select an event to execute from registered event groups. initial event execution timing you can select the upper or lower thresholdfor initial alarm determination when both the upper and lower thresholds are enabled. owner name set the owner name of the alarm group. characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . up to 127 characters can be inputted.</div><div class="display_word">3.1. Alarm group settings Index To create a new alarm group, set the index of the alarm group. The smallest index of unregistered alarm groups is entered as the initial value. The input range is 1 - 65535. An index that is already in use cannot be specified. This cannot be changed when changing the settings. Monitoring MIB object Select MIB object to be monitored. You can select a MIB from those belonging to the index of Ethernet statistics group you have enabled. Sampling interval Specify the sampling interval in seconds for the monitoring MIB values. Comparison method between sample value and the threshold Select a comparison method between the value obtained by sampling and the threshold. Upper threshold Specify the upper threshold and event to be executed when the value exceeds the upper threshold. The input range is 1 - 2147483647. You can select an event to execute from registered event groups. Lower threshold Specify the lower threshold and event to be executed when the value falls below the lower threshold. The input range is 1 - 2147483647. You can select an event to execute from registered event groups. Initial event execution timing You can select the upper or lower thresholdfor initial alarm determination when both the upper and lower thresholds are enabled. Owner name Set the owner name of the alarm group. Characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . Up to 127 characters can be inputted.</div></div><div id="gui_en_management_rmon_event"><div class="search_title" docfname="gui_en_management_rmon_event" doctitle="Event" link="#title-box">Event group</div><div class="search_word">event group</div><div class="display_word">Event group</div></div><div id="gui_en_management_rmon_event"><div class="search_title" docfname="gui_en_management_rmon_event" doctitle="Event" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring rmon event group settings. you cannot configure rmon function when the stack function is enabled.</div><div class="display_word">1. Summary This page is for configuring RMON event group settings. You cannot configure RMON function when the stack function is enabled.</div></div><div id="gui_en_management_rmon_event"><div class="search_title" docfname="gui_en_management_rmon_event" doctitle="Event" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the rmon event group.</div><div class="display_word">2. Top page This is the top page for the RMON event group.</div></div><div id="gui_en_management_rmon_event"><div class="search_title" docfname="gui_en_management_rmon_event" doctitle="Event" link="#event_group_settings">2.1. Event group settings</div><div class="search_word">2.1. event group settings displays a list of event group settings. the table items are explained below. index displays the index of event group. event execution content displays the execution content of event group. trap destination displays snmp community or user specified as trap destination if the event execution content includes "send trap". press the "new" button to display a page where you can create new settings for the event group. press the "setting" button to display a page where you can change the settings of the selected event group. if you press the "delete" button, all event groups whose check boxes are selected will be deleted. up to 128 event group settings can be displayed.</div><div class="display_word">2.1. Event group settings Displays a list of event group settings. The table items are explained below. Index Displays the index of event group. Event execution content Displays the execution content of event group. Trap destination Displays SNMP community or user specified as trap destination if the event execution content includes "Send trap". Press the "New" button to display a page where you can create new settings for the event group. Press the "Setting" button to display a page where you can change the settings of the selected event group. If you press the "Delete" button, all event groups whose check boxes are selected will be deleted. Up to 128 event group settings can be displayed.</div></div><div id="gui_en_management_rmon_event"><div class="search_title" docfname="gui_en_management_rmon_event" doctitle="Event" link="#event_settings">3. Event group settings page</div><div class="search_word">3. event group settings page this page is for configuring rmon event group settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Event group settings page This page is for configuring RMON event group settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_rmon_event"><div class="search_title" docfname="gui_en_management_rmon_event" doctitle="Event" link="#event_group_settings_2">3.1. Event group settings</div><div class="search_word">3.1. event group settings index to create a new event group, set the index of the event group. the smallest index of unregistered event groups is entered as the initial value. the input range is 1 - 65535. an index that is already in use cannot be specified. this cannot be changed when changing the settings. event execution content select an execution content when this event is called. you need to specify the trap destination of event group if the event execution content includes "send trap". trap destination for event group specify the community or user for trap destination of event group. only the community or user specified in the snmp trap destination settings can be selected. description enter a description for the event group. characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . up to 127 characters can be inputted. owner name set the owner name of the event group. characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . up to 127 characters can be inputted.</div><div class="display_word">3.1. Event group settings Index To create a new event group, set the index of the event group. The smallest index of unregistered event groups is entered as the initial value. The input range is 1 - 65535. An index that is already in use cannot be specified. This cannot be changed when changing the settings. Event execution content Select an execution content when this event is called. You need to specify the trap destination of event group if the event execution content includes "Send trap". Trap destination for event group Specify the community or user for trap destination of event group. Only the community or user specified in the SNMP trap destination settings can be selected. Description Enter a description for the event group. Characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . Up to 127 characters can be inputted. Owner name Set the owner name of the event group. Characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . Up to 127 characters can be inputted.</div></div><div id="gui_en_management_rmon_settings"><div class="search_title" docfname="gui_en_management_rmon_settings" doctitle="RMON" link="#title-box">RMON settings</div><div class="search_word">rmon settings</div><div class="display_word">RMON settings</div></div><div id="gui_en_management_rmon_settings"><div class="search_title" docfname="gui_en_management_rmon_settings" doctitle="RMON" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring rmon settings. you can enable or disable the rmon function for the entiresystem, and specify ethernet statistics group and history group forphysical interface. you cannot configure rmon function when the stack function is enabled.</div><div class="display_word">1. Summary This page is for configuring RMON settings. You can enable or disable the RMON function for the entiresystem, and specify Ethernet statistics group and history group forphysical interface. You cannot configure RMON function when the stack function is enabled.</div></div><div id="gui_en_management_rmon_settings"><div class="search_title" docfname="gui_en_management_rmon_settings" doctitle="RMON" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the rmon settings.</div><div class="display_word">2. Top page This is the top page for the RMON settings.</div></div><div id="gui_en_management_rmon_settings"><div class="search_title" docfname="gui_en_management_rmon_settings" doctitle="RMON" link="#system_settings">2.1. System settings</div><div class="search_word">2.1. system settings displays the rmon function settings for the entire system. press the "setting" button to display a page for configuring the system settings.</div><div class="display_word">2.1. System settings Displays the RMON function settings for the entire system. Press the "Setting" button to display a page for configuring the system settings.</div></div><div id="gui_en_management_rmon_settings"><div class="search_title" docfname="gui_en_management_rmon_settings" doctitle="RMON" link="#interface_settings">2.2. Interface settings</div><div class="search_word">2.2. interface settings displays the configuration of each port’s ethernet statistics and history groups. the table items are explained below. port displays the port name. ethernet statistics group settings displays whether the ethernet statistics group for the port is enabled. index displays the index of ethernet statistics group specified for the port. history group settings displays whether the history group for the port is enabled. index displays the index of history group specified for the port. press the "setting" button to display a page for configuring the selected interface settings. press the "return to defaults" button to initialize the settings for all interfaces with the check box selected.</div><div class="display_word">2.2. Interface settings Displays the configuration of each port’s Ethernet statistics and history groups. The table items are explained below. Port Displays the port name. Ethernet statistics group Settings Displays whether the Ethernet statistics group for the port is enabled. Index Displays the index of Ethernet statistics group specified for the port. History group Settings Displays whether the history group for the port is enabled. Index Displays the index of history group specified for the port. Press the "Setting" button to display a page for configuring the selected interface settings. Press the "Return to defaults" button to initialize the settings for all interfaces with the check box selected.</div></div><div id="gui_en_management_rmon_settings"><div class="search_title" docfname="gui_en_management_rmon_settings" doctitle="RMON" link="#sys_settings">3. System settings page</div><div class="search_word">3. system settings page this page is for configuring the rmon function settings for the system. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. System settings page This page is for configuring the RMON function settings for the system. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_rmon_settings"><div class="search_title" docfname="gui_en_management_rmon_settings" doctitle="RMON" link="#system_settings_2">3.1. System settings</div><div class="search_word">3.1. system settings rmon function specify whether to enable or disable the rmon function for the entire system. if this setting is disabled, the following processes are executed. collecting statistics for the ethernet statistics group is stopped. collecting history for the history group is stopped. sampling the alarm group is stopped. if this setting is enabled, the following processes are executed. deletes the previously collected ethernet statistics and restarts the collection. deletes the previously collected history and restarts the collection. deletes the previously collected sampling data and restarts sampling.</div><div class="display_word">3.1. System settings RMON function Specify whether to enable or disable the RMON function for the entire system. If this setting is disabled, the following processes are executed. Collecting statistics for the Ethernet statistics group is stopped. Collecting history for the history group is stopped. Sampling the alarm group is stopped. If this setting is enabled, the following processes are executed. Deletes the previously collected Ethernet statistics and restarts the collection. Deletes the previously collected history and restarts the collection. Deletes the previously collected sampling data and restarts sampling.</div></div><div id="gui_en_management_rmon_settings"><div class="search_title" docfname="gui_en_management_rmon_settings" doctitle="RMON" link="#if_settings">4. Interface settings page</div><div class="search_word">4. interface settings page this page is for configuring rmon settings for the interface. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Interface settings page This page is for configuring RMON settings for the interface. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_rmon_settings"><div class="search_title" docfname="gui_en_management_rmon_settings" doctitle="RMON" link="#interface_settings_2">4.1. Interface settings</div><div class="search_word">4.1. interface settings port displays the port name to configure the settings. ethernet statistics group specify the ethernet statistics group. index set the index of the ethernet statistics group. the input range is 1 - 65535. an index that is already in use cannot be specified. owner name set the owner name of the ethernet statistics group. characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . up to 127 characters can be inputted. press the icon to add an ethernet statistics group. press the "delete" button to delete the ethernet statistics group. you can specify up to 8 ethernet statistics groups. if you check the"delete previously collected statistics" check box, previously collected ethernet statistics will be deleted for already registered indexeswhose settings have not been changed. history group specify the history group. index set the index of the history group. the input range is 1 - 65535. an index that is already in use cannot be specified. number of saved history set the number of saved history of the history group. the input range is 1 - 65535. save interval set the history saving interval of the history group. the input range is 1 - 3600. owner name set the owner name of the history group. characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . up to 127 characters can be inputted. press the icon to add a history group. press the "delete" button to delete the history group. you can specify up to 8 history groups. if you check the "delete previously collected history" check box, previously collectedhistory will be deleted for already registered indexes whose settingshave not been changed.</div><div class="display_word">4.1. Interface settings Port Displays the port name to configure the settings. Ethernet statistics group Specify the Ethernet statistics group. Index Set the index of the Ethernet statistics group. The input range is 1 - 65535. An index that is already in use cannot be specified. Owner name Set the owner name of the Ethernet statistics group. Characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . Up to 127 characters can be inputted. Press the icon to add an Ethernet statistics group. Press the "Delete" button to delete the Ethernet statistics group. You can specify up to 8 Ethernet statistics groups. If you check the"Delete previously collected statistics" check box, previously collected Ethernet statistics will be deleted for already registered indexeswhose settings have not been changed. History group Specify the history group. Index Set the index of the history group. The input range is 1 - 65535. An index that is already in use cannot be specified. Number of saved history Set the number of saved history of the history group. The input range is 1 - 65535. Save interval Set the history saving interval of the history group. The input range is 1 - 3600. Owner name Set the owner name of the history group. Characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . Up to 127 characters can be inputted. Press the icon to add a history group. Press the "Delete" button to delete the history group. You can specify up to 8 history groups. If you check the "Delete previously collected history" check box, previously collectedhistory will be deleted for already registered indexes whose settingshave not been changed.</div></div><div id="gui_en_management_schedule"><div class="search_title" docfname="gui_en_management_schedule" doctitle="Schedule" link="#title-box">Schedule execution</div><div class="search_word">schedule execution</div><div class="display_word">Schedule execution</div></div><div id="gui_en_management_schedule"><div class="search_title" docfname="gui_en_management_schedule" doctitle="Schedule" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can make settings for schedule execution. the schedule execution function of this product has two setting items, schedule template and schedule. schedule template settings allow you to create a templateof detailed settings for processes involved in executing scheduledfunctions and operations, such as the specific functions to be executed, the applicable item involved, and the execution sequence. in schedule settings, you can select when to execute schedules and which templates to execute.</div><div class="display_word">1. Summary In this page you can make settings for schedule execution. The schedule execution function of this product has two setting items, schedule template and schedule. Schedule template settings allow you to create a templateof detailed settings for processes involved in executing scheduledfunctions and operations, such as the specific functions to be executed, the applicable item involved, and the execution sequence. In schedule settings, you can select when to execute schedules and which templates to execute.</div></div><div id="gui_en_management_schedule"><div class="search_title" docfname="gui_en_management_schedule" doctitle="Schedule" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for making settings for schedule execution.</div><div class="display_word">2. Top page This is the top page for making settings for schedule execution.</div></div><div id="gui_en_management_schedule"><div class="search_title" docfname="gui_en_management_schedule" doctitle="Schedule" link="#list_of_schedule_template">2.1. List of schedule template</div><div class="search_word">2.1. list of schedule template information for the currently registered schedule template are shown. the table items are explained below. template id registered schedule template id are shown. status the status of the schedule template are shown. template description description of the schedule template are shown. if you press the "new" button, a page appears in which you can create a new schedule template. if you press the "setting" button, a page appears in which you can edit the settings of the selected schedule template. if you press the "delete" button, all schedule templates whose check box has a check mark will be deleted. up to 10 schedule templates can be registered.</div><div class="display_word">2.1. List of schedule template Information for the currently registered schedule template are shown. The table items are explained below. Template ID Registered schedule template ID are shown. Status The status of the schedule template are shown. Template description Description of the schedule template are shown. If you press the "New" button, a page appears in which you can create a new schedule template. If you press the "Setting" button, a page appears in which you can edit the settings of the selected schedule template. If you press the "Delete" button, all schedule templates whose check box has a check mark will be deleted. Up to 10 schedule templates can be registered.</div></div><div id="gui_en_management_schedule"><div class="search_title" docfname="gui_en_management_schedule" doctitle="Schedule" link="#list_of_schedule">2.2. List of schedule</div><div class="search_word">2.2. list of schedule information for the currently registered schedule are shown. the table items are explained below. schedule id registered schedule id are shown. execution timing the execution timing of the schedule are shown. template to be executed the information about the template to be executed when the schedule executed are shown. if you press the "new" button, a page appears in which you can create a new schedule. if you press the "setting" button, a page appears in which you can edit the settings of the selected schedule. if you press the "delete" button, all schedules whose check box has a check mark will be deleted. up to 10 schedules can be registered.</div><div class="display_word">2.2. List of schedule Information for the currently registered schedule are shown. The table items are explained below. Schedule ID Registered schedule ID are shown. Execution timing The execution timing of the schedule are shown. Template to be executed The information about the template to be executed when the schedule executed are shown. If you press the "New" button, a page appears in which you can create a new schedule. If you press the "Setting" button, a page appears in which you can edit the settings of the selected schedule. If you press the "Delete" button, all schedules whose check box has a check mark will be deleted. Up to 10 schedules can be registered.</div></div><div id="gui_en_management_schedule"><div class="search_title" docfname="gui_en_management_schedule" doctitle="Schedule" link="#template">3. Schedule template settings page</div><div class="search_word">3. schedule template settings page in this page you can create a new schedule template or edit the settings of an already-registered schedule template. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Schedule template settings page In this page you can create a new schedule template or edit the settings of an already-registered schedule template. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_schedule"><div class="search_title" docfname="gui_en_management_schedule" doctitle="Schedule" link="#schedule_template_settings">3.1. Schedule template settings</div><div class="search_word">3.1. schedule template settings template id the id of the schedule template being set is displayed. newly created templates are automatically assigned the lowest unregistered serial number as the template id. template description sets the schedule template description text. enter up to 64 single-byte alphanumeric characters/symbols, excluding the ? symbol. status select template status from the following items. enabled enables the template disabled disables the template the contents of the template are not executed at the time of schedule execution. import source of the schedule execution contents select the import source of the schedule execution contents from the following items. config of the device executes the schedule execution contents saved in config of the device at the time of schedule execution. the schedule execution contents entered on this page are saved in config of the device. script file in sd card loads the schedule execution contents from the script file in sd card at the time of schedule execution. please refer to how to use the script file for specific usage. contents of schedule execution enter the commands to be executed by the scheduled execution. you can enter multiple commands together by separating them with line-returns. specify settings that result in 20 or fewer command lines. schedule execution always starts with the specially-privileged exec mode (enable). for prohibited commands and command details, refer to the command reference and the information provided on the network device product information page and yamaha network devices technical documentation . if you press the "easy input" button, you can quickly enter the corresponding commands for the following functions. shutdown cancel shutdown disable poe power supply enable poe power supply save techinfo into sd card save settings about the linkage function with yamaha wireless ap when disabling the poe power supply to ayamaha wireless ap connected to this unit, you can configure the unit to stop the power supply after the yamaha wireless ap’s shutdown process. to use this linkage function, select thecheck box of "stop power supply after notifying the yamaha wireless ap"when specifying "disable poe power supply" in "easy input". this linkage function works as below. the unit notifies the remaining timeto stop the power supply at the schedule executed. the time is notifiedvia lldp to the powered yamaha wireless ap by the target port. once the notification is received, the yamaha wireless ap executes the shutdown process. the power supplystops 10 minutes later than the schedule execution. this linkage function works when the auto-configure via lldp function is enabled. the auto-configure via lldp function is configured in detailed settings > lldp .</div><div class="display_word">3.1. Schedule template settings Template ID The ID of the schedule template being set is displayed. Newly created templates are automatically assigned the lowest unregistered serial number as the template ID. Template description Sets the schedule template description text. Enter up to 64 single-byte alphanumeric characters/symbols, excluding the ? symbol. Status Select template status from the following items. Enabled Enables the template Disabled Disables the template The contents of the template are not executed at the time of schedule execution. Import source of the schedule execution contents Select the import source of the schedule execution contents from the following items. CONFIG of the device Executes the schedule execution contents saved in CONFIG of the device at the time of schedule execution. The schedule execution contents entered on this page are saved in CONFIG of the device. Script file in SD card Loads the schedule execution contents from the script file in SD card at the time of schedule execution. Please refer to How to use the script file for specific usage. Contents of schedule execution Enter the commands to be executed by the scheduled execution. You can enter multiple commands together by separating them with line-returns. Specify settings that result in 20 or fewer command lines. Schedule execution always starts with the specially-privileged EXEC mode (enable). For prohibited commands and command details, refer to the command reference and the information provided on the Network device product information page and Yamaha Network Devices Technical Documentation . If you press the "Easy input" button, you can quickly enter the corresponding commands for the following functions. Shutdown Cancel shutdown Disable PoE power supply Enable PoE power supply Save TECHINFO into SD card Save settings About the linkage function with Yamaha wireless AP When disabling the PoE power supply to aYamaha wireless AP connected to this unit, you can configure the unit to stop the power supply after the Yamaha wireless AP’s shutdown process. To use this linkage function, select thecheck box of "Stop power supply after notifying the Yamaha wireless AP"when specifying "Disable PoE power supply" in "Easy input". This linkage function works as below. The unit notifies the remaining timeto stop the power supply at the schedule executed. The time is notifiedvia LLDP to the powered Yamaha wireless AP by the target port. Once the notification is received, the Yamaha wireless AP executes the shutdown process. The power supplystops 10 minutes later than the schedule execution. This linkage function works when the auto-configure via LLDP function is enabled. The auto-configure via LLDP function is configured in Detailed Settings > LLDP .</div></div><div id="gui_en_management_schedule"><div class="search_title" docfname="gui_en_management_schedule" doctitle="Schedule" link="#schedule">4. Schedule settings page</div><div class="search_word">4. schedule settings page in this page you can create a new schedule or edit the settings of an already-registered schedule. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Schedule settings page In this page you can create a new schedule or edit the settings of an already-registered schedule. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_schedule"><div class="search_title" docfname="gui_en_management_schedule" doctitle="Schedule" link="#schedule_settings">4.1. Schedule settings</div><div class="search_word">4.1. schedule settings schedule id the id of the schedule being set is displayed. newly created templates are automatically assigned the lowest unregistered serial number as the schedule id. trigger type select the trigger to execute the schedule execution from the following items. time when the time specified in the execution timing arrives, the device executes the schedule execution. event when the event specified in the execution timing occurs, the device executes the schedule execution. execution timing if you select time for trigger type , select the timing to execute the schedule execution. easy input select a typical frequency pattern for the schedule execution timing. period select the periodic pattern of schedule execution from the following items. every day every week every month every year if "every week" is selected, mark the checkbox for the day of the week when the schedule is to be executed. if "every month" is selected, enter the day when the schedule is to be executed in the "day" box. if "every year" is selected, enter the month and the day when the schedule is to be executed in the"month" box and the "day" box. enter numeric values in the "month" and "day" boxes. multiple months/days can be specified as comma-delimited values. (example: enter "10,20" to specify 10 and 20.) a hyphen can be used to indicate a range of values. (example: enter "1-3" to specify 1, 2, and 3.) when you focus on the "month" and "day" boxes, the input form that can be operated with a mouse click is displayed. time in the "hours:minutes:seconds" box, enter the time in hh:mm:ss format. when you focus on the "hours:minutes:seconds" box, an input form that can be operated with a mouse click is displayed. input in command format enter the "date" and "time" in the command format. this allows specifying settings in more detail than the easy input mode. enter the "date" in month/date format. enter the "time" in hh:mm:ss format. for details on command format, refer to the command reference and to the information provided on the network device product information page and yamaha network devices technical documentation . if you select event for trigger type , select the event that triggers to execute the schedule execution. when you start up the device when you start up the device, the device executes the schedule execution. when you attached an sd card when you attached an sd card, the device executes the schedule execution. template to be executed select the template to be executed in the schedule execution.</div><div class="display_word">4.1. Schedule settings Schedule ID The ID of the schedule being set is displayed. Newly created templates are automatically assigned the lowest unregistered serial number as the schedule ID. Trigger type Select the trigger to execute the schedule execution from the following items. Time When the time specified in the execution timing arrives, the device executes the schedule execution. Event When the event specified in the execution timing occurs, the device executes the schedule execution. Execution timing If you select Time for Trigger type , select the timing to execute the schedule execution. Easy input Select a typical frequency pattern for the schedule execution timing. Period Select the periodic pattern of schedule execution from the following items. Every day Every week Every month Every year If "Every week" is selected, mark the checkbox for the day of the week when the schedule is to be executed. If "Every month" is selected, enter the day when the schedule is to be executed in the "Day" box. If "Every year" is selected, enter the month and the day when the schedule is to be executed in the"Month" box and the "Day" box. Enter numeric values in the "Month" and "Day" boxes. Multiple months/days can be specified as comma-delimited values. (Example: Enter "10,20" to specify 10 and 20.) A hyphen can be used to indicate a range of values. (Example: Enter "1-3" to specify 1, 2, and 3.) When you focus on the "Month" and "Day" boxes, the input form that can be operated with a mouse click is displayed. Time In the "Hours:Minutes:Seconds" box, enter the time in hh:mm:ss format. When you focus on the "Hours:Minutes:Seconds" box, an input form that can be operated with a mouse click is displayed. Input in command format Enter the "Date" and "Time" in the command format. This allows specifying settings in more detail than the Easy input mode. Enter the "Date" in MONTH/DATE format. Enter the "Time" in hh:mm:ss format. For details on command format, refer to the command reference and to the information provided on the Network device product information page and Yamaha Network Devices Technical Documentation . If you select Event for Trigger type , select the event that triggers to execute the schedule execution. When you start up the device When you start up the device, the device executes the schedule execution. When you attached an SD card When you attached an SD card, the device executes the schedule execution. Template to be executed Select the template to be executed in the schedule execution.</div></div><div id="gui_en_management_schedule"><div class="search_title" docfname="gui_en_management_schedule" doctitle="Schedule" link="#howto_script">5. How to use the script file</div><div class="search_word">5. how to use the script file if you select the script file in sd card as the importsource of the schedule execution contents in the schedule templatesettings, the contents of the script file are executed at the time ofschedule execution. to use the script file, you need to insert an sd card withthe script file saved in the specified path "/(modelname)/schedule/script.txt" into the device beforehand. you can enter up to 100 lines of commands into the scriptfile. commands after the 101 line are not executed at the time ofschedule execution.</div><div class="display_word">5. How to use the script file If you select the script file in SD card as the importsource of the schedule execution contents in the schedule templatesettings, the contents of the script file are executed at the time ofschedule execution. To use the script file, you need to insert an SD card withthe script file saved in the specified path "/(modelname)/schedule/script.txt" into the device beforehand. You can enter up to 100 lines of commands into the scriptfile. Commands after the 101 line are not executed at the time ofschedule execution.</div></div><div id="gui_en_management_sd"><div class="search_title" docfname="gui_en_management_sd" doctitle="microSD" link="#title-box">microSD</div><div class="search_word">microsd</div><div class="display_word">microSD</div></div><div id="gui_en_management_sd"><div class="search_title" docfname="gui_en_management_sd" doctitle="microSD" link="#section1">1. Summary</div><div class="search_word">1. summary on this page you can perform operations with the microsd card. the microsd card will automatically be mounted when it is inserted into this unit. when removing the microsd card from this unit while the unit is powered on, be sure to unmount the microsd card first. if the stack function is enabled, you can perform operations with the microsd card that is inserted to the main switch.</div><div class="display_word">1. Summary On this page you can perform operations with the microSD card. The microSD card will automatically be mounted when it is inserted into this unit. When removing the microSD card from this unit while the unit is powered on, be sure to unmount the microSD card first. If the stack function is enabled, you can perform operations with the microSD card that is inserted to the main switch.</div></div><div id="gui_en_management_sd"><div class="search_title" docfname="gui_en_management_sd" doctitle="microSD" link="#section2">2. Top page</div><div class="search_word">2. top page this is the microsd top page. displays the mounting status of the microsd card.you canalso begin the steps here for switching the mounting status of themicrosd card.</div><div class="display_word">2. Top page This is the microSD top page. Displays the mounting status of the microSD card.You canalso begin the steps here for switching the mounting status of themicroSD card.</div></div><div id="gui_en_management_sd"><div class="search_title" docfname="gui_en_management_sd" doctitle="microSD" link="#mounting_switch_for_microsd_card">2.1. Mounting switch for microSD card</div><div class="search_word">2.1. mounting switch for microsd card displays the mounting status of the microsd card. press the "next" button to begin the steps for switching the mounting status of the microsd card.</div><div class="display_word">2.1. Mounting switch for microSD card Displays the mounting status of the microSD card. Press the "Next" button to begin the steps for switching the mounting status of the microSD card.</div></div><div id="gui_en_management_sd"><div class="search_title" docfname="gui_en_management_sd" doctitle="microSD" link="#section3">3. microSD card mounting switch page</div><div class="search_word">3. microsd card mounting switch page this page is for switching the microsd card mounting status. press the "ok" button to switch the mounting status of the microsd card. if the microsd card is already mounted, it will be unmounted; and if the microsd card is already unmounted, it will be mounted.</div><div class="display_word">3. microSD card mounting switch page This page is for switching the microSD card mounting status. Press the "OK" button to switch the mounting status of the microSD card. If the microSD card is already mounted, it will be unmounted; and if the microSD card is already unmounted, it will be mounted.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#title-box">Various server settings</div><div class="search_word">various server settings</div><div class="display_word">Various server settings</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can make settings for each type of server.</div><div class="display_word">1. Summary In this page you can make settings for each type of server.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for making settings for each type of server. the current settings are shown for the servers listed below. http server telnet server ssh server tftp server snmp server</div><div class="display_word">2. Top page This is the top page for making settings for each type of server. The current settings are shown for the servers listed below. HTTP server Telnet server SSH server TFTP server SNMP server</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#web_gui_access">2.1. Web GUI access</div><div class="search_word">2.1. web gui access displays the settings for the http server. the table items are explained below. use http server displays whether an http server is to be used or not. if an http server is to be used, the port number will be displayed. use secure http server displays whether a secure http server is to be used or not. if a secure http server is to be used, the port number will be displayed. interfaces that can access the http server displays the interfaces that can access the http server. you can access a management vlan without server settings. clients that can access the http server displays the clients that can access the http server. time until auto logout displays the time for automatic logout. use http proxy displays whether an http proxy server is to be used or not. if an http proxy server is to be used, the timeout interval is displayed.</div><div class="display_word">2.1. Web GUI access Displays the settings for the HTTP server. The table items are explained below. Use HTTP server Displays whether an HTTP server is to be used or not. If an HTTP server is to be used, the port number will be displayed. Use secure HTTP server Displays whether a secure HTTP server is to be used or not. If a secure HTTP server is to be used, the port number will be displayed. Interfaces that can access the HTTP server Displays the interfaces that can access the HTTP server. You can access a management VLAN without server settings. Clients that can access the HTTP server Displays the clients that can access the HTTP server. Time until auto logout Displays the time for automatic logout. Use HTTP proxy Displays whether an HTTP proxy server is to be used or not. If an HTTP proxy server is to be used, the timeout interval is displayed.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#access_via_telnet">2.2. Access via Telnet</div><div class="search_word">2.2. access via telnet displays the settings for the telnet server. the table items are explained below. use telnet server displays whether a telnet server is to be used or not. if a telnet server is to be used, the port number will be displayed. interfaces that can access the telnet server displays the interfaces that can access the telnet server. you can access a management vlan without server settings. clients that can access the telnet server displays the clients that can access the telnet server.</div><div class="display_word">2.2. Access via Telnet Displays the settings for the Telnet server. The table items are explained below. Use Telnet server Displays whether a Telnet server is to be used or not. If a Telnet server is to be used, the port number will be displayed. Interfaces that can access the Telnet server Displays the interfaces that can access the Telnet server. You can access a management VLAN without server settings. Clients that can access the Telnet server Displays the clients that can access the Telnet server.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#access_via_ssh">2.3. Access via SSH</div><div class="search_word">2.3. access via ssh displays the settings for the ssh server. the table items are explained below. use ssh server displays whether an ssh server is to be used or not. if an ssh server is to be used, the port number will be displayed. interfaces that can access the ssh server displays the interfaces that can access the ssh server. you can access a management vlan without server settings. clients that can access the ssh server displays the clients that can access the ssh server. client existence check from ssh server displays whether the ssh server checks for existing clients. if the ssh server is set to checkfor existing clients, this displays the check interval and the number of times checked before disconnecting.</div><div class="display_word">2.3. Access via SSH Displays the settings for the SSH server. The table items are explained below. Use SSH server Displays whether an SSH server is to be used or not. If an SSH server is to be used, the port number will be displayed. Interfaces that can access the SSH server Displays the interfaces that can access the SSH server. You can access a management VLAN without server settings. Clients that can access the SSH server Displays the clients that can access the SSH server. Client existence check from SSH server Displays whether the SSH server checks for existing clients. If the SSH server is set to checkfor existing clients, this displays the check interval and the number of times checked before disconnecting.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#access_via_tftp">2.4. Access via TFTP</div><div class="search_word">2.4. access via tftp displays the settings for the tftp server. the table items are explained below. use tftp server displays whether a tftp server is to be used or not. if a tftp server is to be used, the port number will be displayed. interfaces that can access the tftp server displays the interfaces that can access the tftp server. you can access a management vlan without server settings.</div><div class="display_word">2.4. Access via TFTP Displays the settings for the TFTP server. The table items are explained below. Use TFTP server Displays whether a TFTP server is to be used or not. If a TFTP server is to be used, the port number will be displayed. Interfaces that can access the TFTP server Displays the interfaces that can access the TFTP server. You can access a management VLAN without server settings.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#access_via_snmp">2.5. Access via SNMP</div><div class="search_word">2.5. access via snmp displays the settings for the snmp server. the table items are explained below. clients that can access the snmp server displays the clients that can access the snmp server.</div><div class="display_word">2.5. Access via SNMP Displays the settings for the SNMP server. The table items are explained below. Clients that can access the SNMP server Displays the clients that can access the SNMP server.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#http">3. Web GUI access page</div><div class="search_word">3. web gui access page in this page you can configure the settings for an http server. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Web GUI access page In this page you can configure the settings for an HTTP server. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#web_gui_access_2">3.1. Web GUI access</div><div class="search_word">3.1. web gui access use http server select below whether an http server will be used or not. use don’t use when "use" is selected, specify the port number. input a port number from 1 to 65535. use secure http server select below whether an secure http server will be used or not. use don’t use when "use" is selected, specify the port number. input a port number from 1 to 65535. interfaces that can access the http server press the "select" button to display the "vlan interface list" dialog box. you can select the port check box in the"vlan interface list" dialog box and press the "ok" button to select the associated interface. up to 8 vlan interfaces can be selected. clients that can access the http server select the client access restriction methods from the following options. permit all specify conditions when "specify conditions" is selected, up to 8 conditions can be specified. the conditions are specified as shown below. operation to restrict client access, select from the following operations. permit deny conditional select from the following targets for client access restriction. all addresses specified ip address ip address when "specified ip address" is selected, specify the ip address. the following ip addresses shown below can be specified. ipv4 address example: 192.168.100.1 ipv4 network address example: 192.168.100.0/24 ipv6 address example: fe80::1234:5678 ipv6 network address example: 2001:1234:5678:90ab::0/64 press the icon to add a configuration form. press the "delete" button to delete a configuration form. time until auto logout specify the time for automatic logout. the user is automatically logged out when the time specified in this item elapses since the last access to the web gui. input a time from 1 minute to 49 days 17 hours 2 minutes 23 seconds. use http proxy select below whether an http proxy server will be used or not. use don’t use when "use" is selected, specify the timeout interval. input a timeout interval from 1 to 180.</div><div class="display_word">3.1. Web GUI access Use HTTP server Select below whether an HTTP server will be used or not. Use Don’t use When "Use" is selected, specify the port number. Input a port number from 1 to 65535. Use secure HTTP server Select below whether an secure HTTP server will be used or not. Use Don’t use When "Use" is selected, specify the port number. Input a port number from 1 to 65535. Interfaces that can access the HTTP server Press the "Select" button to display the "VLAN interface list" dialog box. You can select the port check box in the"VLAN interface list" dialog box and press the "OK" button to select the associated interface. Up to 8 VLAN interfaces can be selected. Clients that can access the HTTP server Select the client access restriction methods from the following options. Permit all Specify conditions When "Specify conditions" is selected, up to 8 conditions can be specified. The conditions are specified as shown below. Operation To restrict client access, select from the following operations. Permit Deny Conditional Select from the following targets for client access restriction. All addresses Specified IP address IP address When "Specified IP address" is selected, specify the IP address. The following IP addresses shown below can be specified. IPv4 address Example: 192.168.100.1 IPv4 network address Example: 192.168.100.0/24 IPv6 address Example: fe80::1234:5678 IPv6 network address Example: 2001:1234:5678:90ab::0/64 Press the icon to add a configuration form. Press the "Delete" button to delete a configuration form. Time until auto logout Specify the time for automatic logout. The user is automatically logged out when the time specified in this item elapses since the last access to the Web GUI. Input a time from 1 minute to 49 days 17 hours 2 minutes 23 seconds. Use HTTP proxy Select below whether an HTTP proxy server will be used or not. Use Don’t use When "Use" is selected, specify the timeout interval. Input a timeout interval from 1 to 180.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#telnet">4. Access via Telnet page</div><div class="search_word">4. access via telnet page in this page you can configure the settings for a telnet server. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Access via Telnet page In this page you can configure the settings for a Telnet server. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#access_via_telnet_2">4.1. Access via Telnet</div><div class="search_word">4.1. access via telnet use telnet server select below whether a telnet server will be used or not. use don’t use when "use" is selected, specify the port number. input a port number from 1 to 65535. interfaces that can access the telnet server the setting method for this item is thesame as for the "interfaces that can access the http server" item on the web gui access page. clients that can access the telnet server the setting method for this item is thesame as for the "clients that can access the http server" item on theweb gui access page.</div><div class="display_word">4.1. Access via Telnet Use Telnet server Select below whether a Telnet server will be used or not. Use Don’t use When "Use" is selected, specify the port number. Input a port number from 1 to 65535. Interfaces that can access the Telnet server The setting method for this item is thesame as for the "Interfaces that can access the HTTP server" item on the Web GUI access page. Clients that can access the Telnet server The setting method for this item is thesame as for the "Clients that can access the HTTP server" item on theWeb GUI access page.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#ssh">5. Access via SSH page</div><div class="search_word">5. access via ssh page in this page you can configure the settings for an ssh server. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button. if a host key has not been generated for the ssh server, the host key will be automatically generated when you modify thesettings for using the ssh server.</div><div class="display_word">5. Access via SSH page In this page you can configure the settings for an SSH server. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button. If a host key has not been generated for the SSH server, the host key will be automatically generated when you modify thesettings for using the SSH server.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#access_via_ssh_2">5.1. Access via SSH</div><div class="search_word">5.1. access via ssh use ssh server select below whether an ssh server will be used or not. use don’t use when "use" is selected, specify the port number. input a port number from 1 to 65535. interfaces that can access the ssh server the setting method for this item is thesame as for the "interfaces that can access the http server" item on the web gui access page. clients that can access the ssh server the setting method for this item is thesame as for the "clients that can access the http server" item on theweb gui access page. client existence check from ssh server select below whether the ssh server checks for existing clients. check do not check when "check" is selected, specify the check interval and the number of times checked before disconnecting. input a check interval from 1 to 2147483647. input the number of times checked from 1 to 2147483647.</div><div class="display_word">5.1. Access via SSH Use SSH server Select below whether an SSH server will be used or not. Use Don’t use When "Use" is selected, specify the port number. Input a port number from 1 to 65535. Interfaces that can access the SSH server The setting method for this item is thesame as for the "Interfaces that can access the HTTP server" item on the Web GUI access page. Clients that can access the SSH server The setting method for this item is thesame as for the "Clients that can access the HTTP server" item on theWeb GUI access page. Client existence check from SSH server Select below whether the SSH server checks for existing clients. Check Do not check When "Check" is selected, specify the check interval and the number of times checked before disconnecting. Input a check interval from 1 to 2147483647. Input the number of times checked from 1 to 2147483647.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#tftp">6. Access via TFTP page</div><div class="search_word">6. access via tftp page in this page you can configure the settings for a tftp server. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">6. Access via TFTP page In this page you can configure the settings for a TFTP server. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#access_via_tftp_2">6.1. Access via TFTP</div><div class="search_word">6.1. access via tftp use tftp server select below whether a tftp server will be used or not. use don’t use when "use" is selected, specify the port number. input a port number from 1 to 65535. interfaces that can access the tftp server the setting method for this item is thesame as for the "interfaces that can access the http server" item on the web gui access page.</div><div class="display_word">6.1. Access via TFTP Use TFTP server Select below whether a TFTP server will be used or not. Use Don’t use When "Use" is selected, specify the port number. Input a port number from 1 to 65535. Interfaces that can access the TFTP server The setting method for this item is thesame as for the "Interfaces that can access the HTTP server" item on the Web GUI access page.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#snmp">7. Access via SNMP page</div><div class="search_word">7. access via snmp page in this page you can configure the settings for a snmp server. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">7. Access via SNMP page In this page you can configure the settings for a SNMP server. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_server"><div class="search_title" docfname="gui_en_management_server" doctitle="Various" link="#access_via_snmp_2">7.1. Access via SNMP</div><div class="search_word">7.1. access via snmp clients that can access the snmp server configure clients that can access the snmp server. only predefined communities can be selected for the client community. specify the client ip address by ipv4 or ipv6 address. press the icon to add a client. press the "delete" button to delete the client. you can configure up to 32 clients.</div><div class="display_word">7.1. Access via SNMP Clients that can access the SNMP server Configure clients that can access the SNMP server. Only predefined communities can be selected for the client community. Specify the client IP address by IPv4 or IPv6 address. Press the icon to add a client. Press the "Delete" button to delete the client. You can configure up to 32 clients.</div></div><div id="gui_en_management_sflow"><div class="search_title" docfname="gui_en_management_sflow" doctitle="sFlow" link="#title-box">sFlow</div><div class="search_word">sflow</div><div class="display_word">sFlow</div></div><div id="gui_en_management_sflow"><div class="search_title" docfname="gui_en_management_sflow" doctitle="sFlow" link="#summary">1. Summary</div><div class="search_word">1. summary this page is for configuring sflow settings. this unit operates as a sflow agent. you need to prepare a sflow collector separately.</div><div class="display_word">1. Summary This page is for configuring sFlow settings. This unit operates as a sFlow agent. You need to prepare a sFlow collector separately.</div></div><div id="gui_en_management_sflow"><div class="search_title" docfname="gui_en_management_sflow" doctitle="sFlow" link="#top">2. Top page</div><div class="search_word">2. top page this is the top page for the sflow.</div><div class="display_word">2. Top page This is the top page for the sFlow.</div></div><div id="gui_en_management_sflow"><div class="search_title" docfname="gui_en_management_sflow" doctitle="sFlow" link="#system_settings">2.1. System settings</div><div class="search_word">2.1. system settings displays the sflow settings for the entire system. the table items are explained below. sflow function displays whether to enable or disable the sflow function for the entire system. ip address of agent displays the ip address of sflow agent. ip address of collector displays the ip address of sflow collector. port of collector displays the udp port number of sflow collector. maximum datagram size displays the maximum datagram size sent from sflow agent to sflow collector. press the "setting" button to display the page for configuring the system.</div><div class="display_word">2.1. System settings Displays the sFlow settings for the entire system. The table items are explained below. sFlow function Displays whether to enable or disable the sFlow function for the entire system. IP address of agent Displays the IP address of sFlow agent. IP address of collector Displays the IP address of sFlow collector. Port of collector Displays the UDP port number of sFlow collector. Maximum datagram size Displays the maximum datagram size sent from sFlow agent to sFlow collector. Press the "Setting" button to display the page for configuring the system.</div></div><div id="gui_en_management_sflow"><div class="search_title" docfname="gui_en_management_sflow" doctitle="sFlow" link="#interface_settings">2.2. Interface settings</div><div class="search_word">2.2. interface settings displays the sflow settings for the interface. the table items are explained below. port displays the interface name. packet flow sampling displays sampling rate for packet flow sampling at the target interface. counter sampling displays polling interval for counter sampling at the target interface. press the "setting" button to display the page for configuring the selected interface. press the "specify all" button to configure the settings for all interfaces with the check box selected. press the "return to defaults" button to initialize the settings for all interfaces with the check box selected.</div><div class="display_word">2.2. Interface settings Displays the sFlow settings for the interface. The table items are explained below. Port Displays the interface name. Packet flow sampling Displays sampling rate for packet flow sampling at the target interface. Counter sampling Displays polling interval for counter sampling at the target interface. Press the "Setting" button to display the page for configuring the selected interface. Press the "Specify all" button to configure the settings for all interfaces with the check box selected. Press the "Return to defaults" button to initialize the settings for all interfaces with the check box selected.</div></div><div id="gui_en_management_sflow"><div class="search_title" docfname="gui_en_management_sflow" doctitle="sFlow" link="#system_setting">3. System settings page</div><div class="search_word">3. system settings page this page is for configuring the sflow settings for the system. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. System settings page This page is for configuring the sFlow settings for the system. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_sflow"><div class="search_title" docfname="gui_en_management_sflow" doctitle="sFlow" link="#system_settings_2">3.1. System settings</div><div class="search_word">3.1. system settings sflow function specify whether to enable or disable the sflow function for the entire system. ip address of agent set the ip address of sflow agent. it is used for sflow header of sflow datagram. ipv6 address cannot be specified when the stack function is enabled. ip address of collector set the ip address of sflow collector. ipv6 address cannot be specified when the stack function is enabled. the following ipv4 addresses cannot be specified. all 0 (0.0.0.0) loopback (127.0.0.1) multicast (224.0.0.0 - 239.255.255.255) class e (240.0.0.0 - 255.255.255.255) the following ipv6 addresses cannot be specified. all 0 (::0) loopback (::1) multicast (ff00::) port of collector set the udp port number of sflow collector. maximum datagram size set the maximum datagram size sent from sflow agent to sflow collector.</div><div class="display_word">3.1. System settings sFlow function Specify whether to enable or disable the sFlow function for the entire system. IP address of agent Set the IP address of sFlow agent. It is used for sFlow header of sFlow datagram. IPv6 address cannot be specified when the stack function is enabled. IP address of collector Set the IP address of sFlow collector. IPv6 address cannot be specified when the stack function is enabled. The following IPv4 addresses cannot be specified. All 0 (0.0.0.0) Loopback (127.0.0.1) Multicast (224.0.0.0 - 239.255.255.255) class E (240.0.0.0 - 255.255.255.255) The following IPv6 addresses cannot be specified. All 0 (::0) Loopback (::1) Multicast (FF00::) Port of collector Set the UDP port number of sFlow collector. Maximum datagram size Set the maximum datagram size sent from sFlow agent to sFlow collector.</div></div><div id="gui_en_management_sflow"><div class="search_title" docfname="gui_en_management_sflow" doctitle="sFlow" link="#interface_setting">4. Interface settings page</div><div class="search_word">4. interface settings page this page is for configuring the sflow settings for the interface. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Interface settings page This page is for configuring the sFlow settings for the interface. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_sflow"><div class="search_title" docfname="gui_en_management_sflow" doctitle="sFlow" link="#interface_settings_2">4.1. Interface settings</div><div class="search_word">4.1. interface settings port displays the port name to configure the settings. packet flow sampling select from the following packet flow sampling operations. disable enable sampling rate specify how many packets you want to take sample statistics for each by packet flow sampling. set the appropriate value, paying attention to the following. if you set the value too small, cpu load will be high. the more you increase ports with packet flow sampling enabled, the more cpu load increases. high cpu load might affect precision of information because the unprocessed sampling contents will be discarded. maximum header size specify the maximum header size of ethernet frames to be sampled by packet flow sampling. counter sampling select from the following counter sampling operations. disable enable polling interval specify how many seconds you want to take sample statistics for each by counter sampling.</div><div class="display_word">4.1. Interface settings Port Displays the port name to configure the settings. Packet flow sampling Select from the following packet flow sampling operations. Disable Enable Sampling rate Specify how many packets you want to take sample statistics for each by packet flow sampling. Set the appropriate value, paying attention to the following. If you set the value too small, CPU load will be high. The more you increase ports with packet flow sampling enabled, the more CPU load increases. High CPU load might affect precision of information because the unprocessed sampling contents will be discarded. Maximum header size Specify the maximum header size of Ethernet frames to be sampled by packet flow sampling. Counter sampling Select from the following counter sampling operations. Disable Enable Polling interval Specify how many seconds you want to take sample statistics for each by counter sampling.</div></div><div id="gui_en_management_snmp_user"><div class="search_title" docfname="gui_en_management_snmp_user" doctitle="SNMPv3" link="#title-box">SNMPv3 User</div><div class="search_word">snmpv3 user</div><div class="display_word">SNMPv3 User</div></div><div id="gui_en_management_snmp_user"><div class="search_title" docfname="gui_en_management_snmp_user" doctitle="SNMPv3" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring the settings related to snmpv3 user.</div><div class="display_word">1. Summary This page is for configuring the settings related to SNMPv3 User.</div></div><div id="gui_en_management_snmp_user"><div class="search_title" docfname="gui_en_management_snmp_user" doctitle="SNMPv3" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for snmpv3 user.</div><div class="display_word">2. Top page This is the top page for SNMPv3 User.</div></div><div id="gui_en_management_snmp_user"><div class="search_title" docfname="gui_en_management_snmp_user" doctitle="SNMPv3" link="#mib_view_list">2.1. MIB view list</div><div class="search_word">2.1. mib view list displays the list of registered mib views. the table items are explained below. view name displays the registered mib view name. press the "new" button to display the page for registering a new mib view. press the "setting" button to display the page for changing the selected mib view settings. press the "delete" button to delete the mib views with the check box selected. if you check the "delete from relatedsettings as well" check box in the delete dialog, the following settings are changed with the deletion of the mib view. deletes the mib view settings from the group settings as well. if there are no more readable and writable mibviews, deletes the group settings as well. deletes the user settings belonging to the group to be deleted. deletes the trap destination settings specifying the user to be deleted. you can register up to 16 mib views.</div><div class="display_word">2.1. MIB view list Displays the list of registered MIB views. The table items are explained below. View name Displays the registered MIB view name. Press the "New" button to display the page for registering a new MIB view. Press the "Setting" button to display the page for changing the selected MIB view settings. Press the "Delete" button to delete the MIB views with the check box selected. If you check the "Delete from relatedsettings as well" check box in the delete dialog, the following settings are changed with the deletion of the MIB view. Deletes the MIB view settings from the group settings as well. If there are no more readable and writable MIBviews, deletes the group settings as well. Deletes the user settings belonging to the group to be deleted. Deletes the trap destination settings specifying the user to be deleted. You can register up to 16 MIB views.</div></div><div id="gui_en_management_snmp_user"><div class="search_title" docfname="gui_en_management_snmp_user" doctitle="SNMPv3" link="#group_list">2.2. Group list</div><div class="search_word">2.2. group list displays the list of registered groups. the table items are explained below. group name displays the registered group name. readable mib view displays the mib view that is readable by users who belong to this group. writable mib view displays the mib view that is writable by users who belong to this group. security level displays the security level required for users who belong to this group. press the "new" button to display the page for registering a new group. press the "setting" button to display the page for changing the selected group settings. press the "delete" button to delete the groups with the check box selected. if you check the "delete from relatedsettings as well" check box in the delete dialog, the following settings are changed with the deletion of the group. deletes the user settings belonging to the group to be deleted. deletes the trap destination settings specifying the user to be deleted. you can register up to 16 groups.</div><div class="display_word">2.2. Group list Displays the list of registered groups. The table items are explained below. Group name Displays the registered group name. Readable MIB view Displays the MIB view that is readable by users who belong to this group. Writable MIB view Displays the MIB view that is writable by users who belong to this group. Security level Displays the security level required for users who belong to this group. Press the "New" button to display the page for registering a new group. Press the "Setting" button to display the page for changing the selected group settings. Press the "Delete" button to delete the groups with the check box selected. If you check the "Delete from relatedsettings as well" check box in the delete dialog, the following settings are changed with the deletion of the group. Deletes the user settings belonging to the group to be deleted. Deletes the trap destination settings specifying the user to be deleted. You can register up to 16 groups.</div></div><div id="gui_en_management_snmp_user"><div class="search_title" docfname="gui_en_management_snmp_user" doctitle="SNMPv3" link="#user_list">2.3. User list</div><div class="search_word">2.3. user list displays the list of registered users. the table items are explained below. user name displays the registered user name. group displays the name of the group to which this user belongs. authentication algorithm displays the authentication algorithm that this user uses for communication. encryption algorithm displays the encryption algorithm that this user uses for communication. press the "new" button to display the page for registering a new user. press the "setting" button to display the page for changing the selected user settings. press the "delete" button to delete the users with the check box selected. if you check the "delete from relatedsettings as well" check box in the delete dialog, the following settingis changed with the deletion of the user. deletes the trap destination settings specifying the user to be deleted. you can register up to 16 users.</div><div class="display_word">2.3. User list Displays the list of registered users. The table items are explained below. User name Displays the registered user name. Group Displays the name of the group to which this user belongs. Authentication algorithm Displays the authentication algorithm that this user uses for communication. Encryption algorithm Displays the encryption algorithm that this user uses for communication. Press the "New" button to display the page for registering a new user. Press the "Setting" button to display the page for changing the selected user settings. Press the "Delete" button to delete the users with the check box selected. If you check the "Delete from relatedsettings as well" check box in the delete dialog, the following settingis changed with the deletion of the user. Deletes the trap destination settings specifying the user to be deleted. You can register up to 16 users.</div></div><div id="gui_en_management_snmp_user"><div class="search_title" docfname="gui_en_management_snmp_user" doctitle="SNMPv3" link="#view">3. MIB view settings page</div><div class="search_word">3. mib view settings page this page is for configuring settings related to mib view of snmp. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. MIB view settings page This page is for configuring settings related to MIB view of SNMP. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_snmp_user"><div class="search_title" docfname="gui_en_management_snmp_user" doctitle="SNMPv3" link="#mib_view_settings">3.1. MIB view settings</div><div class="search_word">3.1. mib view settings view name set the mib view name. characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . up to 32 characters can be inputted. change the settings related to the view accordingly. the following setting is changed accordingly to the change of mib view settings. change the mib view name used in the group settings to the changed mib view name. this item will be displayed only when changing settings. if you check the check box, the "detail display" button will be displayed on the confirmation page. press the "detail display" button to open the dialog with the following information. group settings where mib view name to be changed. entry set the mib objects to be allowed access. mib object id specify the mib object id. single-byte numeric characters and dot (.) can be inputted. up to 64 characters can be inputted. type select "include in management(include)" to allow access to the specified mib object id or "excludefrom management (exclude)" to not allow access. press the icon to add an entry. press the "delete" button to delete the entry. you can specify up to 8 entries. you need to specify at least one entry.</div><div class="display_word">3.1. MIB view settings View name Set the MIB view name. Characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . Up to 32 characters can be inputted. Change the settings related to the view accordingly. The following setting is changed accordingly to the change of MIB view settings. Change the MIB view name used in the group settings to the changed MIB view name. This item will be displayed only when changing settings. If you check the check box, the "Detail display" button will be displayed on the confirmation page. Press the "Detail display" button to open the dialog with the following information. Group settings where MIB view name to be changed. Entry Set the MIB objects to be allowed access. MIB object ID Specify the MIB object ID. Single-byte numeric characters and dot (.) can be inputted. Up to 64 characters can be inputted. Type Select "Include in management(include)" to allow access to the specified MIB object ID or "Excludefrom management (exclude)" to not allow access. Press the icon to add an entry. Press the "Delete" button to delete the entry. You can specify up to 8 entries. You need to specify at least one entry.</div></div><div id="gui_en_management_snmp_user"><div class="search_title" docfname="gui_en_management_snmp_user" doctitle="SNMPv3" link="#group">4. Group settings page</div><div class="search_word">4. group settings page this page is for configuring the settings related to groups of snmp. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Group settings page This page is for configuring the settings related to groups of SNMP. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_snmp_user"><div class="search_title" docfname="gui_en_management_snmp_user" doctitle="SNMPv3" link="#group_settings">4.1. Group settings</div><div class="search_word">4.1. group settings group name set the group name. characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . up to 32 characters can be inputted. change the settings related to the group accordingly. the following settings are changed accordingly to the change of group settings. change the group name used in the user settings to the changed group name. this item will be displayed only when changing settings. if you check the check box, the "detail display" button will be displayed on the confirmation page. press the "detail display" button to open the dialog with the following information. group settings for which the group name is changed readable mib view select a mib view that is readable by users who belong to this group. press the "select" button and select a mib view from the "select mib view" dialog. writable mib view select a mib view that is writable by users who belong to this group. press the "select" button and select a mib view from the "select mib view" dialog. security level configure the security level required for users who belong to this group. you cannot use encryption alone without authentication. user authentication for mib access fails if the user settings do not meet the security level of the group.</div><div class="display_word">4.1. Group settings Group name Set the group name. Characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . Up to 32 characters can be inputted. Change the settings related to the group accordingly. The following settings are changed accordingly to the change of group settings. Change the group name used in the user settings to the changed group name. This item will be displayed only when changing settings. If you check the check box, the "Detail display" button will be displayed on the confirmation page. Press the "Detail display" button to open the dialog with the following information. Group settings for which the group name is changed Readable MIB view Select a MIB view that is readable by users who belong to this group. Press the "Select" button and select a MIB view from the "Select MIB view" dialog. Writable MIB view Select a MIB view that is writable by users who belong to this group. Press the "Select" button and select a MIB view from the "Select MIB view" dialog. Security level Configure the security level required for users who belong to this group. You cannot use encryption alone without authentication. User authentication for MIB access fails if the user settings do not meet the security level of the group.</div></div><div id="gui_en_management_snmp_user"><div class="search_title" docfname="gui_en_management_snmp_user" doctitle="SNMPv3" link="#user">5. User settings page</div><div class="search_word">5. user settings page this page is for configuring the settings related to users of snmp. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">5. User settings page This page is for configuring the settings related to users of SNMP. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_snmp_user"><div class="search_title" docfname="gui_en_management_snmp_user" doctitle="SNMPv3" link="#user_settings">5.1. User settings</div><div class="search_word">5.1. user settings user name set the user name. characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . up to 32 characters can be inputted. change the settings related to the user accordingly. the following setting is changed accordingly to the change of user settings. change the user name used in the trap destination settings to the changed user name. change the security level used in the trap destination settings according to this user setting. this item will be displayed only when changing settings. if you check the check box, the "detail display" button will be displayed on the confirmation page. press the "detail display" button to open the dialog with the following information. trap destination settings where user name to be changed trap destination settings where the security level to be changed group select a group to which this user belongs. press the "select" button and select a group from the "select group" dialog. authentication algorithm select an authentication algorithm that this user uses for communication. authentication password enter from 8 to 32 single-byte alphanumeric characters/symbols, excluding the ? symbol. if the setting of the authentication algorithm is "none", this setting is not available. encryption algorithm select a encryption algorithm that this user uses for communication. if the setting of the authentication algorithm is "none", this setting is not available. encryption password enter from 8 to 32 single-byte alphanumeric characters/symbols, excluding the ? symbol. if the setting of the authentication or encryption algorithm is "none", this setting is not available.</div><div class="display_word">5.1. User settings User name Set the user name. Characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . Up to 32 characters can be inputted. Change the settings related to the user accordingly. The following setting is changed accordingly to the change of user settings. Change the user name used in the trap destination settings to the changed user name. Change the security level used in the trap destination settings according to this user setting. This item will be displayed only when changing settings. If you check the check box, the "Detail display" button will be displayed on the confirmation page. Press the "Detail display" button to open the dialog with the following information. Trap destination settings where user name to be changed Trap destination settings where the security level to be changed Group Select a group to which this user belongs. Press the "Select" button and select a group from the "Select group" dialog. Authentication algorithm Select an authentication algorithm that this user uses for communication. Authentication password Enter from 8 to 32 single-byte alphanumeric characters/symbols, excluding the ? symbol. If the setting of the authentication algorithm is "None", this setting is not available. Encryption algorithm Select a encryption algorithm that this user uses for communication. If the setting of the authentication algorithm is "None", this setting is not available. Encryption password Enter from 8 to 32 single-byte alphanumeric characters/symbols, excluding the ? symbol. If the setting of the authentication or encryption algorithm is "None", this setting is not available.</div></div><div id="gui_en_management_stat"><div class="search_title" docfname="gui_en_management_stat" doctitle="Summary" link="#title-box">Summary data management</div><div class="search_word">summary data management</div><div class="display_word">Summary data management</div></div><div id="gui_en_management_stat"><div class="search_title" docfname="gui_en_management_stat" doctitle="Summary" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for performing operations related to the summary data.</div><div class="display_word">1. Summary This page is for performing operations related to the summary data.</div></div><div id="gui_en_management_stat"><div class="search_title" docfname="gui_en_management_stat" doctitle="Summary" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for summary data management. the settings for whether to back up the summary data or not are displayed. here you can start the process of clearing the summary data and exporting summary data to a pc.</div><div class="display_word">2. Top page This is the top page for summary data management. The settings for whether to back up the summary data or not are displayed. Here you can start the process of clearing the summary data and exporting summary data to a PC.</div></div><div id="gui_en_management_stat"><div class="search_title" docfname="gui_en_management_stat" doctitle="Summary" link="#backup_settings_for_summary_data">2.1. Backup settings for summary data</div><div class="search_word">2.1. backup settings for summary data the settings for whether to back up the summary data or not are displayed. press the "setting" button to access a page where you configure the backup settings.</div><div class="display_word">2.1. Backup settings for summary data The settings for whether to back up the summary data or not are displayed. Press the "Setting" button to access a page where you configure the backup settings.</div></div><div id="gui_en_management_stat"><div class="search_title" docfname="gui_en_management_stat" doctitle="Summary" link="#clearing_summary_data">2.2. Clearing summary data</div><div class="search_word">2.2. clearing summary data press the "next" button to begin the process of clearing the summary data.</div><div class="display_word">2.2. Clearing summary data Press the "Next" button to begin the process of clearing the summary data.</div></div><div id="gui_en_management_stat"><div class="search_title" docfname="gui_en_management_stat" doctitle="Summary" link="#export_summary_data">2.3. Export summary data</div><div class="search_word">2.3. export summary data press the "next" button to begin the process of exporting the summary data to a pc.</div><div class="display_word">2.3. Export summary data Press the "Next" button to begin the process of exporting the summary data to a PC.</div></div><div id="gui_en_management_stat"><div class="search_title" docfname="gui_en_management_stat" doctitle="Summary" link="#section3">3. Backup settings page for summary data</div><div class="search_word">3. backup settings page for summary data this page is for configuring the summary data backup settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button. when backup settings are enabled, the summary data will be backed up whenever an sd card has been inserted.</div><div class="display_word">3. Backup settings page for summary data This page is for configuring the summary data backup settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button. When backup settings are enabled, the summary data will be backed up whenever an SD card has been inserted.</div></div><div id="gui_en_management_stat"><div class="search_title" docfname="gui_en_management_stat" doctitle="Summary" link="#backup_settings_for_summary_data_2">3.1. Backup settings for summary data</div><div class="search_word">3.1. backup settings for summary data summary data to be backed up select the summary data to back up from the list below. traffic information resource information power consumption information</div><div class="display_word">3.1. Backup settings for summary data Summary data to be backed up Select the summary data to back up from the list below. Traffic information Resource information Power consumption information</div></div><div id="gui_en_management_stat"><div class="search_title" docfname="gui_en_management_stat" doctitle="Summary" link="#section4">4. Page for clearing summary data</div><div class="search_word">4. page for clearing summary data this page is for clearing the summary data. when you have inputted the settings, press the "confirm" button. if there are no mistakes in the input content confirmation screen, press the "ok" button. when the summary data has been cleared, both the datasaved in internal volatile memory and the data backed up to sd card will be cleared.</div><div class="display_word">4. Page for clearing summary data This page is for clearing the summary data. When you have inputted the settings, press the "Confirm" button. If there are no mistakes in the input content confirmation screen, press the "OK" button. When the summary data has been cleared, both the datasaved in internal volatile memory and the data backed up to SD card will be cleared.</div></div><div id="gui_en_management_stat"><div class="search_title" docfname="gui_en_management_stat" doctitle="Summary" link="#clearing_summary_data_2">4.1. Clearing summary data</div><div class="search_word">4.1. clearing summary data summary data to clear select the summary data to clear from one of the following. traffic information resource information power consumption information</div><div class="display_word">4.1. Clearing summary data Summary data to clear Select the summary data to clear from one of the following. Traffic information Resource information Power consumption information</div></div><div id="gui_en_management_stat"><div class="search_title" docfname="gui_en_management_stat" doctitle="Summary" link="#section5">5. Export page for summary data</div><div class="search_word">5. export page for summary data this page is for exporting summary data. when you have finished inputting, check the inputted content and press the "ok" button. implementing the summary data export will download a zip file. see export file configuration for more information on the configuration of the zip file.</div><div class="display_word">5. Export page for summary data This page is for exporting summary data. When you have finished inputting, check the inputted content and press the "OK" button. Implementing the summary data export will download a ZIP file. See Export file configuration for more information on the configuration of the ZIP file.</div></div><div id="gui_en_management_stat"><div class="search_title" docfname="gui_en_management_stat" doctitle="Summary" link="#export_summary_data_2">5.1. Export summary data</div><div class="search_word">5.1. export summary data summary data to export select the summary data to export from one of the following. traffic information(transmit) traffic information(reception) resource information power consumption information specifying a timespan select the month(s) of the data to be exported. specify the month(s) from the previous year using the drop-down list box.</div><div class="display_word">5.1. Export summary data Summary data to export Select the summary data to export from one of the following. Traffic information(Transmit) Traffic information(Reception) Resource information Power consumption information Specifying a timespan Select the month(s) of the data to be exported. Specify the month(s) from the previous year using the drop-down list box.</div></div><div id="gui_en_management_stat"><div class="search_title" docfname="gui_en_management_stat" doctitle="Summary" link="#section6">6. Export file configuration</div><div class="search_word">6. export file configuration this explains about the folder that will be extracted when decompressing the zip file. the configuration when the october 2017traffic information (received) is exported is shown below. 20171103150412_trf_rx_csv.zip 20171103150412_trf_rx_csv 20171001_trf_rx_hour.csv : 20171031_trf_rx_hour.csv 201710_trf_rx_day.csv this explains about the folder and files after extraction. 20171103150412_trf_rx_csv the csv files with the summary data are contained in this folder. the time of export and data type are used in the folder name. one of the following will be used for the data type, according to the type specified. trf_tx for traffic information (transmission) trf_rx for traffic information (reception) resource for resource information 20171001_trf_rx_hour.csv this is the csv file with the summary data. the date, data type and data unit time will be included in the file name for the target data. the naming convention for the data type is the same as for the folders. one of the following will be used for the data unit time. hour files that are totaled every hour, containing one days’ worth of data day files that are totaled every day, containing one months’ worth of data</div><div class="display_word">6. Export file configuration This explains about the folder that will be extracted when decompressing the ZIP file. The configuration when the October 2017traffic information (received) is exported is shown below. 20171103150412_trf_rx_csv.zip 20171103150412_trf_rx_csv 20171001_trf_rx_hour.csv : 20171031_trf_rx_hour.csv 201710_trf_rx_day.csv This explains about the folder and files after extraction. 20171103150412_trf_rx_csv The CSV files with the summary data are contained in this folder. The time of export and data type are used in the folder name. One of the following will be used for the data type, according to the type specified. trf_tx For traffic information (transmission) trf_rx For traffic information (reception) resource For resource information 20171001_trf_rx_hour.csv This is the CSV file with the summary data. The date, data type and data unit time will be included in the file name for the target data. The naming convention for the data type is the same as for the folders. One of the following will be used for the data unit time. hour Files that are totaled every hour, containing one days’ worth of data day Files that are totaled every day, containing one months’ worth of data</div></div><div id="gui_en_management_sysdiag"><div class="search_title" docfname="gui_en_management_sysdiag" doctitle="System" link="#title-box">System self-diagnostics</div><div class="search_word">system self-diagnostics</div><div class="display_word">System self-diagnostics</div></div><div id="gui_en_management_sysdiag"><div class="search_title" docfname="gui_en_management_sysdiag" doctitle="System" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for finding system failures. the system self-diagnostics function consists of boot-up, on-demand, and health-monitoring diagnostics. boot-up diagnostics verifies whether any failures exist in the system boot-up sequence. performs at system start-up. on-demand diagnostics verifies whether any failures exist in the hardware components (e.g., interface) and memory. the user can perform this at any time. health monitoring diagnostics verifies whether any failures exist in the hardware components (e.g., fan) and temperatures. performs all the time in the background while the system is working.</div><div class="display_word">1. Summary This page is for finding system failures. The system self-diagnostics function consists of boot-up, on-demand, and health-monitoring diagnostics. Boot-up diagnostics Verifies whether any failures exist in the system boot-up sequence. Performs at system start-up. On-demand diagnostics Verifies whether any failures exist in the hardware components (e.g., interface) and memory. The user can perform this at any time. Health monitoring diagnostics Verifies whether any failures exist in the hardware components (e.g., fan) and temperatures. Performs all the time in the background while the system is working.</div></div><div id="gui_en_management_sysdiag"><div class="search_title" docfname="gui_en_management_sysdiag" doctitle="System" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for system self-diagnostics. the top page shows each diagnostics result. open the accordion to display the details of each diagnostics result. in a stack configuration, only the diagnostics results of the main switch are shown. diagnostics results of units other than the main switch are not shown. if you want to check the diagnostics results of units other than the main switch using gui, please refer to procedure to check the diagnostics results in a stack configuration .</div><div class="display_word">2. Top page This is the top page for system self-diagnostics. The top page shows each diagnostics result. Open the accordion to display the details of each diagnostics result. In a stack configuration, only the diagnostics results of the main switch are shown. Diagnostics results of units other than the main switch are not shown. If you want to check the diagnostics results of units other than the main switch using GUI, please refer to Procedure to check the diagnostics results in a stack configuration .</div></div><div id="gui_en_management_sysdiag"><div class="search_title" docfname="gui_en_management_sysdiag" doctitle="System" link="#boot_up_diagnostics">2.1. Boot-up diagnostics</div><div class="search_word">2.1. boot-up diagnostics the boot-up diagnostics performs the following tests. loading test verifies the loading status of software modules. displays "passed" if all modules are loaded successfully or displays "failed" otherwise. the information about modules that failed to load is not displayed. if you want to specify the module that failed to load, find the following errors in the log. "[ hamon]:err: an unexpected error has occurred. (xxxx daemon)" xxxx part shows the module name. rtc test verifies accessing the rtc register. retrieves the time twice from rtc, then displays "passed" if the time has changed or displays "failed" if it is the same. it also displays "failed" if retrieving the time from rtc (reading the register) fails. packet processor test verifies accessing the packet processor register. writes to and reads from the packet processor register, thendisplays "passed" if the values match or displays "failed" if the values do not match. it also displays "failed" if accessing the register fails.</div><div class="display_word">2.1. Boot-up diagnostics The boot-up diagnostics performs the following tests. Loading test Verifies the loading status of software modules. Displays "Passed" if all modules are loaded successfully or displays "Failed" otherwise. The information about modules that failed to load is not displayed. If you want to specify the module that failed to load, find the following errors in the log. "[ HAMON]:err: An unexpected error has occurred. (XXXX daemon)" XXXX part shows the module name. RTC test Verifies accessing the RTC register. Retrieves the time twice from RTC, then displays "Passed" if the time has changed or displays "Failed" if it is the same. It also displays "Failed" if retrieving the time from RTC (reading the register) fails. Packet processor test Verifies accessing the packet processor register. Writes to and reads from the packet processor register, thendisplays "Passed" if the values match or displays "Failed" if the values do not match. It also displays "Failed" if accessing the register fails.</div></div><div id="gui_en_management_sysdiag"><div class="search_title" docfname="gui_en_management_sysdiag" doctitle="System" link="#on_demand_diagnostics">2.2. On-demand diagnostics</div><div class="search_word">2.2. on-demand diagnostics press the "perform diagnostics" button to display the page for performing on-demand diagnostics. press the "discard diagnostics results" button to display the page for discarding the on-demand diagnostics results. you cannot perform on-demand diagnostics if the state of the stack is active. if you want to perform on-demand diagnostics when the stack function is enabled, please refer to procedure to check the diagnostics results in a stack configuration . the on-demand diagnostics performs the following tests. phy test verifies accessing the phy register. writes to and reads from the phy register, then displays if the values match or displays if the values do not match. it also displays if accessing the register fails.</div><div class="display_word">2.2. On-demand diagnostics Press the "Perform diagnostics" button to display the page for performing on-demand diagnostics. Press the "Discard diagnostics results" button to display the page for discarding the on-demand diagnostics results. You cannot perform on-demand diagnostics if the state of the stack is active. If you want to perform on-demand diagnostics when the stack function is enabled, please refer to Procedure to check the diagnostics results in a stack configuration . The on-demand diagnostics performs the following tests. PHY test Verifies accessing the PHY register. Writes to and reads from the PHY register, then displays if the values match or displays if the values do not match. It also displays if accessing the register fails.</div></div><div id="gui_en_management_sysdiag"><div class="search_title" docfname="gui_en_management_sysdiag" doctitle="System" link="#health_monitoring_diagnostics">2.3. Health monitoring diagnostics</div><div class="search_word">2.3. health monitoring diagnostics press to update the results of health-monitoring diagnostics. the health-monitoring diagnostics performs the following tests. temperature test monitors the temperatures below. cpu phy sfp ts pse displays "passed" if the temperature has not exceeded the threshold or displays "failed" otherwise. fan test monitors the fan speed. displays "passed" if the fan speed is normal or displays "failed" if the fan has stopped or the fan speed has increased. temperature sensor test monitors the temperature sensors. displays "passed" if the temperature sensors are working properly or displays "failed" if any error has occurred. poe test monitors the poe power supply status. displays if the poe power supply control is normal or displays if any error has occurred. sfp test monitors the sfp optical rx level. displays if the optical rx level is in the normal range or displays if it is out of the range.</div><div class="display_word">2.3. Health monitoring diagnostics Press to update the results of health-monitoring diagnostics. The health-monitoring diagnostics performs the following tests. Temperature test Monitors the temperatures below. CPU PHY SFP TS PSE Displays "Passed" if the temperature has not exceeded the threshold or displays "Failed" otherwise. Fan test Monitors the fan speed. Displays "Passed" if the fan speed is normal or displays "Failed" if the fan has stopped or the fan speed has increased. Temperature sensor test Monitors the temperature sensors. Displays "Passed" if the temperature sensors are working properly or displays "Failed" if any error has occurred. PoE test Monitors the PoE power supply status. Displays if the PoE power supply control is normal or displays if any error has occurred. SFP test Monitors the SFP optical Rx level. Displays if the optical RX level is in the normal range or displays if it is out of the range.</div></div><div id="gui_en_management_sysdiag"><div class="search_title" docfname="gui_en_management_sysdiag" doctitle="System" link="#exec_on_demand">3. On-demand diagnostics performing page</div><div class="search_word">3. on-demand diagnostics performing page this page is for performing on-demand diagnostics. press the "ok" button to perform the on-demand diagnostics. all ports are shut down while the diagnostics is performing. the unit restarts automatically after performing on-demand diagnostics.</div><div class="display_word">3. On-demand diagnostics performing page This page is for performing on-demand diagnostics. Press the "OK" button to perform the on-demand diagnostics. All ports are shut down while the diagnostics is performing. The unit restarts automatically after performing on-demand diagnostics.</div></div><div id="gui_en_management_sysdiag"><div class="search_title" docfname="gui_en_management_sysdiag" doctitle="System" link="#del_on_demand">4. On-demand diagnostics results discarding page</div><div class="search_word">4. on-demand diagnostics results discarding page this page is for discarding the on-demand diagnostics results. press the "ok" button to discard the on-demand diagnostics results.</div><div class="display_word">4. On-demand diagnostics results discarding page This page is for discarding the on-demand diagnostics results. Press the "OK" button to discard the on-demand diagnostics results.</div></div><div id="gui_en_management_sysdiag"><div class="search_title" docfname="gui_en_management_sysdiag" doctitle="System" link="#procedure_confirm_stack">5. Procedure to check the diagnostics results in a stack configuration</div><div class="search_word">5. procedure to check the diagnostics results in a stack configuration the diagnostics results show only for the unit currently logged in. if you want to check the diagnostics results of all units in the stackconfiguration using gui, perform the following procedures. disconnect the connections between the member switches. access the gui of the unit that you want to show the diagnostics results. (optional) perform on-demand diagnostics.</div><div class="display_word">5. Procedure to check the diagnostics results in a stack configuration The diagnostics results show only for the unit currently logged in. If you want to check the diagnostics results of all units in the stackconfiguration using GUI, perform the following procedures. Disconnect the connections between the member switches. Access the GUI of the unit that you want to show the diagnostics results. (Optional) Perform on-demand diagnostics.</div></div><div id="gui_en_management_syslog"><div class="search_title" docfname="gui_en_management_syslog" doctitle="SYSLOG" link="#title-box">SYSLOG management</div><div class="search_word">syslog management</div><div class="display_word">SYSLOG management</div></div><div id="gui_en_management_syslog"><div class="search_title" docfname="gui_en_management_syslog" doctitle="SYSLOG" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can view and edit the settings of the syslog function. the operation history of this device is output as the syslog (log data) according to the settings of the syslog function. in addition to recording the syslog inside this device, you can also specify adestination address for output to an external host.</div><div class="display_word">1. Summary In this page you can view and edit the settings of the SYSLOG function. The operation history of this device is output as the SYSLOG (log data) according to the settings of the SYSLOG function. In addition to recording the SYSLOG inside this device, you can also specify adestination address for output to an external host.</div></div><div id="gui_en_management_syslog"><div class="search_title" docfname="gui_en_management_syslog" doctitle="SYSLOG" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for syslog management. the current settings for the syslog function are shown.</div><div class="display_word">2. Top page This is the top page for SYSLOG management. The current settings for the SYSLOG function are shown.</div></div><div id="gui_en_management_syslog"><div class="search_title" docfname="gui_en_management_syslog" doctitle="SYSLOG" link="#syslog_settings">2.1. SYSLOG settings</div><div class="search_word">2.1. syslog settings the output-level of syslog that is output, and theheader information and destination address for the syslog transmissionare shown. press the "setting" button to access a page where you can change the settings. you can delete the saved log.</div><div class="display_word">2.1. SYSLOG settings The output-level of SYSLOG that is output, and theheader information and destination address for the SYSLOG transmissionare shown. Press the "Setting" button to access a page where you can change the settings. You can delete the saved log.</div></div><div id="gui_en_management_syslog"><div class="search_title" docfname="gui_en_management_syslog" doctitle="SYSLOG" link="#section3">3. SYSLOG settings page</div><div class="search_word">3. syslog settings page in this page you can make settings for the syslog function. when you have entered the settings, press the "confirm" button.if there are no mistakes in the input content confirmation screen, press the "ok" button. for details on the various syslog types, refer to the command reference.</div><div class="display_word">3. SYSLOG settings page In this page you can make settings for the SYSLOG function. When you have entered the settings, press the "Confirm" button.If there are no mistakes in the input content confirmation screen, press the "OK" button. For details on the various SYSLOG types, refer to the command reference.</div></div><div id="gui_en_management_syslog"><div class="search_title" docfname="gui_en_management_syslog" doctitle="SYSLOG" link="#syslog_settings_2">3.1. SYSLOG settings</div><div class="search_word">3.1. syslog settings syslog type error this setting specifies whether error type syslog is output. info this setting specifies whether info type syslog is output. debug this setting specifies whether debug type syslog is output. syslog transmission header you can configure the header for outputting syslog to external hosts. you can specify whether to include or exclude the timestamp and hostname in the syslog message header. the hostname is stored as the device name of the unit. syslog transmission destination address this is the transmission destination address setting when outputting the syslog to an external host. you can specify up to two ipv4/ipv6 destination addresses. for ipv6 link local addresses, you must also specify the interface to send from. (format: fe80::x%vlann) if no destination address is specified, the syslog is recorded only inside the switch. facility this is the facility setting when outputting the syslog to an external host. select the facility value from 0 - 23.</div><div class="display_word">3.1. SYSLOG settings SYSLOG type ERROR This setting specifies whether ERROR type SYSLOG is output. INFO This setting specifies whether INFO type SYSLOG is output. DEBUG This setting specifies whether DEBUG type SYSLOG is output. SYSLOG transmission Header You can configure the header for outputting SYSLOG to external hosts. You can specify whether to include or exclude the timestamp and hostname in the SYSLOG message header. The hostname is stored as the device name of the unit. SYSLOG transmission destination address This is the transmission destination address setting when outputting the SYSLOG to an external host. You can specify up to two IPv4/IPv6 destination addresses. For IPv6 link local addresses, you must also specify the interface to send from. (Format: fe80::X%vlanN) If no destination address is specified, the SYSLOG is recorded only inside the switch. Facility This is the facility setting when outputting the SYSLOG to an external host. Select the facility value from 0 - 23.</div></div><div id="gui_en_management_terminal"><div class="search_title" docfname="gui_en_management_terminal" doctitle="Terminal" link="#title-box">Terminal monitoring</div><div class="search_word">terminal monitoring</div><div class="display_word">Terminal monitoring</div></div><div id="gui_en_management_terminal"><div class="search_title" docfname="gui_en_management_terminal" doctitle="Terminal" link="#section1">1. Summary</div><div class="search_word">1. summary on this page you can make settings for device monitoring. the device communication status can be monitored by specifying the monitoring target and method. you can also specify the action to be executed when the device status changes. device monitoring settings can be made only from the web gui. although the contents of the device monitoring settingsare not shown in the config file, when an operation (such as "erasestartup-config") is performed on the config file, the same operation isperformed on the device monitoring settings. if the auto-configure via lldp function is enabled, theyamaha wireless ap connected to this unit is automatically monitored bylldp.</div><div class="display_word">1. Summary On this page you can make settings for device monitoring. The device communication status can be monitored by specifying the monitoring target and method. You can also specify the action to be executed when the device status changes. Device monitoring settings can be made only from the Web GUI. Although the contents of the device monitoring settingsare not shown in the CONFIG file, when an operation (such as "erasestartup-config") is performed on the CONFIG file, the same operation isperformed on the device monitoring settings. If the auto-configure via LLDP function is enabled, theYamaha wireless AP connected to this unit is automatically monitored byLLDP.</div></div><div id="gui_en_management_terminal"><div class="search_title" docfname="gui_en_management_terminal" doctitle="Terminal" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for device monitoring.</div><div class="display_word">2. Top page This is the top page for device monitoring.</div></div><div id="gui_en_management_terminal"><div class="search_title" docfname="gui_en_management_terminal" doctitle="Terminal" link="#list_of_monitored_terminals">2.1. List of monitored terminals</div><div class="search_word">2.1. list of monitored terminals the device monitoring status and settings are shown here. the table items are explained below. check box select the check box to delete device monitoring settings. status one of the device monitoring statuses as follows are displayed. idle up down refer to conditions for determining monitored device status for the conditions used to determine the above statuses. include in monitoring displays information for the monitoring target(s). if the monitoring type is "ping", the ip address of the monitored device will be displayed. for monitoring types other than "ping", the interface number will be displayed. device name displays the name of the device being monitored. monitoring type displays one of the following monitoring types for the device being monitored. ping frame reception volume lldp poe supply displays one of the following poe power supply statuses for the device being monitored. power is being supplied (class 0) power is being supplied (class 1) power is being supplied (class 2) power is being supplied (class 3) power is being supplied (class 4) stopped - press the "new" button to display a page where you can create new settings for monitored devices. press the "setting" button to access a page where you can change the settings of the selected device. press the "update" button to update the table. if you press the "delete" button, all monitored devices whose check boxes are selected will be deleted. up to 256 monitored devices can be configured. of these, up to 64 monitored devices with ping can be configured.</div><div class="display_word">2.1. List of monitored terminals The device monitoring status and settings are shown here. The table items are explained below. Check box Select the check box to delete device monitoring settings. Status One of the device monitoring statuses as follows are displayed. IDLE UP DOWN Refer to Conditions for determining monitored device status for the conditions used to determine the above statuses. Include in monitoring Displays information for the monitoring target(s). If the monitoring type is "Ping", the IP address of the monitored device will be displayed. For monitoring types other than "Ping", the interface number will be displayed. Device name Displays the name of the device being monitored. Monitoring type Displays one of the following monitoring types for the device being monitored. Ping Frame reception volume LLDP PoE supply Displays one of the following PoE power supply statuses for the device being monitored. Power is being supplied (Class 0) Power is being supplied (Class 1) Power is being supplied (Class 2) Power is being supplied (Class 3) Power is being supplied (Class 4) Stopped - Press the "New" button to display a page where you can create new settings for monitored devices. Press the "Setting" button to access a page where you can change the settings of the selected device. Press the "Update" button to update the table. If you press the "Delete" button, all monitored devices whose check boxes are selected will be deleted. Up to 256 monitored devices can be configured. Of these, up to 64 monitored devices with ping can be configured.</div></div><div id="gui_en_management_terminal"><div class="search_title" docfname="gui_en_management_terminal" doctitle="Terminal" link="#terminal">3. Monitored device settings page</div><div class="search_word">3. monitored device settings page this page is for configuring the monitored device settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Monitored device settings page This page is for configuring the monitored device settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_terminal"><div class="search_title" docfname="gui_en_management_terminal" doctitle="Terminal" link="#setting_monitored_devices">3.1. Setting monitored devices</div><div class="search_word">3.1. setting monitored devices device name specifies the device name. characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . up to 80 characters can be inputted. monitoring type select from one of the following monitoring methods. ping-based communication monitoring frame reception volume monitoring lldp reception interval monitoring this item cannot be changed when changing the settings. destination ip address for ping specifies the ip address to which a ping message will be transmitted. this item will only be displayed when ping-based communication monitoring is selected for the "monitoring type" item. time waiting for reply specifies the time required to determine whether the ping response has failed. the input range is 1 - 60. this item will only be displayed when ping-based communication monitoring is selected for the "monitoring type" item. number of failures before detecting unavailable device specifies the number of times that the ping response must fail before determining that the monitored device is unavailable. the input range is 1 - 100. this item will only be displayed when ping-based communication monitoring is selected for the "monitoring type" item. port specifies the port for frame monitoring. the input format is portx.yy. this item will only be displayed when frame reception volume monitoring or lldp reception interval monitoring is selected for the "monitoring type" item. monitor start band specifies the bandwidth at which frame reception volume monitoring will start. the input range is 1 - 1000000000. this item will only be displayed when frame reception volume monitoring is selected for the "monitoring type" item. unavailable device detection band specifies the band value for determining that the monitored device is unavailable. the input range is 0 - 999999999. the value specified for this item must be less than the value used for "monitor start band". this item will only be displayed when frame reception volume monitoring is selected for the "monitoring type" item. operation when detecting change in status terminal reboot due to temporary stop of poe power supply the poe power supply for the target port will be temporarily stopped only when the device is detected to be unavailable. target port specifies the port for which the poe power supply will be stopped. the input format is portx.yy. this item will only be displayed when ping-based communication monitoring is selected for the "monitoring type" item. duration of power supply stop specifies the time for which the poe power supply will be stopped. the input range is 1 - 60. snmp trap transmission when a change of status is detected, a trap is notified to the snmp manager. mail notification an e-mail is sent when a change of status is detected. the e-mail server, destination and so on must be configured in order to send e-mail. further, you must select the status notification for device monitoring in the "mail notification settings" as the "notification content". configure the e-mail server and e-mail template on the e-mail notifications page.</div><div class="display_word">3.1. Setting monitored devices Device name Specifies the device name. Characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . Up to 80 characters can be inputted. Monitoring type Select from one of the following monitoring methods. Ping-based communication monitoring Frame reception volume monitoring LLDP reception interval monitoring This item cannot be changed when changing the settings. Destination IP address for ping Specifies the IP address to which a ping message will be transmitted. This item will only be displayed when Ping-based communication monitoring is selected for the "Monitoring type" item. Time waiting for reply Specifies the time required to determine whether the ping response has failed. The input range is 1 - 60. This item will only be displayed when Ping-based communication monitoring is selected for the "Monitoring type" item. Number of failures before detecting unavailable device Specifies the number of times that the ping response must fail before determining that the monitored device is unavailable. The input range is 1 - 100. This item will only be displayed when Ping-based communication monitoring is selected for the "Monitoring type" item. Port Specifies the port for frame monitoring. The input format is portX.YY. This item will only be displayed when Frame reception volume monitoring or LLDP reception interval monitoring is selected for the "Monitoring type" item. Monitor start band Specifies the bandwidth at which frame reception volume monitoring will start. The input range is 1 - 1000000000. This item will only be displayed when Frame reception volume monitoring is selected for the "Monitoring type" item. Unavailable device detection band Specifies the band value for determining that the monitored device is unavailable. The input range is 0 - 999999999. The value specified for this item must be less than the value used for "Monitor start band". This item will only be displayed when Frame reception volume monitoring is selected for the "Monitoring type" item. Operation when detecting change in status Terminal reboot due to temporary stop of PoE power supply The PoE power supply for the target port will be temporarily stopped only when the device is detected to be unavailable. Target port Specifies the port for which the PoE power supply will be stopped. The input format is portX.YY. This item will only be displayed when Ping-based communication monitoring is selected for the "Monitoring type" item. Duration of power supply stop Specifies the time for which the PoE power supply will be stopped. The input range is 1 - 60. SNMP trap transmission When a change of status is detected, a trap is notified to the SNMP manager. Mail notification An e-mail is sent when a change of status is detected. The e-mail server, destination and so on must be configured in order to send e-mail. Further, you must select the Status notification for device monitoring in the "Mail notification settings" as the "notification content". Configure the e-mail server and e-mail template on the E-mail notifications page.</div></div><div id="gui_en_management_terminal"><div class="search_title" docfname="gui_en_management_terminal" doctitle="Terminal" link="#condition">4. Conditions for determining monitored device status</div><div class="search_word">4. conditions for determining monitored device status this explains the conditions for when the monitored device status changes. monitoring with ping if a ping packet transmitted by this unit does not return within the set time waiting for reply , this is counted as one failure, the status is determined by how many failures occur. the conditions for change in status are shown below. idle status initial status determination has not been completed after setting the monitored device. up status ping transmission has not failed continuously for the number of failures before detecting unavailable device that was set. down status ping transmission fails continuously for the number of failures before detecting unavailable device that was set. monitoring according to frame reception volume measures the frame reception volume for the monitoring target and determines the status. the conditions for change in status are shown below. idle status after the monitored device is configured, the frame reception volume for the monitored target port has not once exceeded the monitor start band that was set. up status after the frame reception volume for the monitored target port exceeded the monitor start band that was set, it did not fall below the unavailable device detection band . the frame reception volume for the monitored target port rose above the unavailable device detection band in down status. down status the frame reception volume for the monitored target port fell below the unavailable device detection band in up status. monitoring with lldp status is determined by the lldp frame reception status at the monitored target port. the conditions for change in status are shown below. idle status after the monitored device is configured, no lldp frames have been received at the monitored target port. up status the next lldp frame was able to be received at the monitored target port, within the ttl of the previously accepted lldp frame. an lldp frame could be received in down status at the monitored target port. down status the next lldp frame could not be received at the monitored target port, within the ttl of the previously accepted lldp frame.</div><div class="display_word">4. Conditions for determining monitored device status This explains the conditions for when the monitored device status changes. Monitoring with ping If a ping packet transmitted by this unit does not return within the set time waiting for reply , this is counted as one failure, The status is determined by how many failures occur. The conditions for change in status are shown below. IDLE status Initial status determination has not been completed after setting the monitored device. UP status Ping transmission has not failed continuously for the Number of failures before detecting unavailable device that was set. DOWN status Ping transmission fails continuously for the Number of failures before detecting unavailable device that was set. Monitoring according to frame reception volume Measures the frame reception volume for the monitoring target and determines the status. The conditions for change in status are shown below. IDLE status After the monitored device is configured, the frame reception volume for the monitored target port has not once exceeded the monitor start band that was set. UP status After the frame reception volume for the monitored target port exceeded the monitor start band that was set, it did not fall below the unavailable device detection band . The frame reception volume for the monitored target port rose above the unavailable device detection band in DOWN status. DOWN status The frame reception volume for the monitored target port fell below the unavailable device detection band in UP status. Monitoring with LLDP Status is determined by the LLDP frame reception status at the monitored target port. The conditions for change in status are shown below. IDLE status After the monitored device is configured, no LLDP frames have been received at the monitored target port. UP status The next LLDP frame was able to be received at the monitored target port, within the TTL of the previously accepted LLDP frame. An LLDP frame could be received in DOWN status at the monitored target port. DOWN status The next LLDP frame could not be received at the monitored target port, within the TTL of the previously accepted LLDP frame.</div></div><div id="gui_en_management_trap"><div class="search_title" docfname="gui_en_management_trap" doctitle="SNMP" link="#title-box">SNMP trap</div><div class="search_word">snmp trap</div><div class="display_word">SNMP trap</div></div><div id="gui_en_management_trap"><div class="search_title" docfname="gui_en_management_trap" doctitle="SNMP" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring snmp trap settings.</div><div class="display_word">1. Summary This page is for configuring SNMP trap settings.</div></div><div id="gui_en_management_trap"><div class="search_title" docfname="gui_en_management_trap" doctitle="SNMP" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for snmp trap.</div><div class="display_word">2. Top page This is the top page for SNMP trap.</div></div><div id="gui_en_management_trap"><div class="search_title" docfname="gui_en_management_trap" doctitle="SNMP" link="#trap_type_settings">2.1. Trap type settings</div><div class="search_word">2.1. trap type settings the contents of the settings of trap type are shown. press the "setting" button to access a page where you can change the settings.</div><div class="display_word">2.1. Trap type settings The contents of the settings of trap type are shown. Press the "Setting" button to access a page where you can change the settings.</div></div><div id="gui_en_management_trap"><div class="search_title" docfname="gui_en_management_trap" doctitle="SNMP" link="#list_of_traps_destinations">2.2. List of traps destinations</div><div class="search_word">2.2. list of traps destinations information for the currently registered traps destinations are shown. the table items are explained below. destination address registered traps destination address are shown. version snmp version that used in trap are shown. community / user snmp community name or user name that used in trap are shown. message type snmp message type that used in trap are shown. security level displays the security level required in the user settings for the device to send traps. if you press the "new" button, a page appears in which you can create a new traps destination. if you press the "setting" button, a page appears in which you can edit the settings of the selected traps destination. if you press the "delete" button, all traps destinations whose check box has a check mark will be deleted. up to 8 traps destinations can be registered.</div><div class="display_word">2.2. List of traps destinations Information for the currently registered traps destinations are shown. The table items are explained below. Destination address Registered traps destination address are shown. Version SNMP version that used in trap are shown. Community / User SNMP community name or user name that used in trap are shown. Message type SNMP message type that used in trap are shown. Security level Displays the security level required in the user settings for the device to send traps. If you press the "New" button, a page appears in which you can create a new traps destination. If you press the "Setting" button, a page appears in which you can edit the settings of the selected traps destination. If you press the "Delete" button, all traps destinations whose check box has a check mark will be deleted. Up to 8 traps destinations can be registered.</div></div><div id="gui_en_management_trap"><div class="search_title" docfname="gui_en_management_trap" doctitle="SNMP" link="#trap_type">3. Trap type setting page</div><div class="search_word">3. trap type setting page this page is for configuring trap type settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Trap type setting page This page is for configuring Trap type settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_trap"><div class="search_title" docfname="gui_en_management_trap" doctitle="SNMP" link="#trap_type_settings_2">3.1. Trap type settings</div><div class="search_word">3.1. trap type settings trap type select the trap type to send by snmp agent from the list below. boot from power off state send traps when the power is turned on/off or when firmware is updated. restart without power off send traps when restart by reload command. link down of port send traps when link down of port. link up of port send traps when link up of port. fail authentication send traps when snmp message to non-registered community or user is received. change temperature status send traps when temperature state is changed for example when temperature abnormally detected. change fan status send traps when fan state is changed for example when fan abnormally detected. detect / lose l2ms agent send traps when an l2ms agent is detected or lost. detect / cancel errdisable send traps when the errdisable is detected or canceled. rmon event send traps when the rmon event is executed. change device monitoring status send traps when the device monitoring function detects a change in the device status. detect root of spanning tree / change of topology send traps when a new root bridge is detected or when a topology change is detected. change poe status send traps when poe state is changed. detect / resolve the loop send traps when a loop is detected or resolved.</div><div class="display_word">3.1. Trap type settings Trap type Select the trap type to send by SNMP agent from the list below. Boot from power OFF state Send traps when the power is turned on/off or when firmware is updated. Restart without power OFF Send traps when restart by reload command. Link down of port Send traps when link down of port. Link up of port Send traps when link up of port. Fail authentication Send traps when SNMP message to non-registered community or user is received. Change Temperature status Send traps when Temperature state is changed for example when temperature abnormally detected. Change FAN status Send traps when FAN state is changed for example when FAN abnormally detected. Detect / lose L2MS agent Send traps when an L2MS agent is detected or lost. Detect / cancel ErrDisable Send traps when the ErrDisable is detected or canceled. RMON event Send traps when the RMON event is executed. Change device monitoring status Send traps when the device monitoring function detects a change in the device status. Detect root of spanning tree / change of topology Send traps when a new root bridge is detected or when a topology change is detected. Change PoE status Send traps when PoE state is changed. Detect / resolve the loop Send traps when a loop is detected or resolved.</div></div><div id="gui_en_management_trap"><div class="search_title" docfname="gui_en_management_trap" doctitle="SNMP" link="#trap_host">4. Trap destination setting page</div><div class="search_word">4. trap destination setting page in this page you can create a new trap destination oredit the settings of an already-registered trap destination. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. Trap destination setting page In this page you can create a new trap destination oredit the settings of an already-registered trap destination. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_trap"><div class="search_title" docfname="gui_en_management_trap" doctitle="SNMP" link="#trap_destination_settings">4.1. Trap destination settings</div><div class="search_word">4.1. trap destination settings destination address sets the destination address of traps. for the destination address, either an ipv4 address or an ipv6 address can be specified. for ipv6 link local addresses, you must also specify the interface to send from. (format: fe80::x%vlann) version select the snmp version used by traps. snmpv1 send traps using snmp version 1. snmpv2c send traps using snmp version 2c. snmpv3 send traps using snmp version 3. community / user select the community or users used by traps. click the "select" button to display the "community selection" dialog or "user selection" dialog. list of already-defined community or user is displayed at "community selection" dialog or "user selection" dialog. in the "community selection" dialog or"user selection" dialog, pressing the "select" button enables selectionof communities or users used by traps at the destination where the traps are sent. message type select the snmp message type used by trap. use trap message type that does not require response confirmation to the destination. use inform request message type that require response confirmation to the destination. if snmpv1 is selected as the version, then thte message type cannot be selected. the trap message type is always used for version snmpv1. security level set the security level required in the user settings for the device to send traps. you cannot use encryption alone without authentication. sending traps fails if the user settings do not meet the security level of the trap destination settings.</div><div class="display_word">4.1. Trap destination settings Destination address Sets the destination address of traps. For the destination address, either an IPv4 address or an IPv6 address can be specified. For IPv6 link local addresses, you must also specify the interface to send from. (Format: fe80::X%vlanN) Version Select the SNMP version used by traps. SNMPv1 Send traps using SNMP version 1. SNMPv2c Send traps using SNMP version 2c. SNMPv3 Send traps using SNMP version 3. Community / User Select the community or users used by traps. Click the "Select" button to display the "Community selection" dialog or "User selection" dialog. List of already-defined community or user is displayed at "Community selection" dialog or "User selection" dialog. In the "Community selection" dialog or"User selection" dialog, pressing the "Select" button enables selectionof communities or users used by traps at the destination where the traps are sent. Message type Select the SNMP message type used by trap. Use Trap Message type that does not require response confirmation to the destination. Use Inform Request Message type that require response confirmation to the destination. If SNMPv1 is selected as the version, then thte message type cannot be selected. The Trap message type is always used for version SNMPv1. Security level Set the security level required in the user settings for the device to send traps. You cannot use encryption alone without authentication. Sending traps fails if the user settings do not meet the security level of the trap destination settings.</div></div><div id="gui_en_management_user"><div class="search_title" docfname="gui_en_management_user" doctitle="User" link="#title-box">User settings</div><div class="search_word">user settings</div><div class="display_word">User settings</div></div><div id="gui_en_management_user"><div class="search_title" docfname="gui_en_management_user" doctitle="User" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring the user settings.</div><div class="display_word">1. Summary This page is for configuring the user settings.</div></div><div id="gui_en_management_user"><div class="search_title" docfname="gui_en_management_user" doctitle="User" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the user settings.</div><div class="display_word">2. Top page This is the top page for the user settings.</div></div><div id="gui_en_management_user"><div class="search_title" docfname="gui_en_management_user" doctitle="User" link="#password_settings">2.1. Password settings</div><div class="search_word">2.1. password settings password-related settings are displayed. the table items are explained below. privileged password displays whether the privileged password has been set. encryption the display will show whether password encryption is enabled. press the "setting" button to access the page where you can change the password-related settings.</div><div class="display_word">2.1. Password settings Password-related settings are displayed. The table items are explained below. Privileged password Displays whether the privileged password has been set. Encryption The display will show whether password encryption is enabled. Press the "Setting" button to access the page where you can change the password-related settings.</div></div><div id="gui_en_management_user"><div class="search_title" docfname="gui_en_management_user" doctitle="User" link="#user_account_settings">2.2. User account settings</div><div class="search_word">2.2. user account settings displays a list of user account settings. the table items are explained below. check box select the check box to delete user account settings. user name displays the user name. administrative privileges displays whether the user account has been given administrative privileges. press the "new" button to display the page where you can set up a new user account. press the "setting" button to access a page where you can change the settings of the selected user account. if you press the "delete" button, all user accounts whose check boxes are selected will be deleted. settings can be made for up to 33 user accounts. there must be at least one user configuration that has administrative privileges.</div><div class="display_word">2.2. User account settings Displays a list of user account settings. The table items are explained below. Check box Select the check box to delete user account settings. User name Displays the user name. Administrative privileges Displays whether the user account has been given administrative privileges. Press the "New" button to display the page where you can set up a new user account. Press the "Setting" button to access a page where you can change the settings of the selected user account. If you press the "Delete" button, all user accounts whose check boxes are selected will be deleted. Settings can be made for up to 33 user accounts. There must be at least one user configuration that has administrative privileges.</div></div><div id="gui_en_management_user"><div class="search_title" docfname="gui_en_management_user" doctitle="User" link="#password">3. Password settings page</div><div class="search_word">3. password settings page this page is for making password-related settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. Password settings page This page is for making password-related settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_user"><div class="search_title" docfname="gui_en_management_user" doctitle="User" link="#password_settings_2">3.1. Password settings</div><div class="search_word">3.1. password settings privileged password enter the privileged password that you want to set. you can use up to 32 single-byte alphanumeric characters and symbols. (excluding "'|>?space ) if the password is not changed, select the privileged password not changed check box. if a password has already been set, the privileged password not changed check box will be selected by default. refer to the password strength when deciding on your password, which is displayed as you type. the strength of the password is indicated in four levels from "weakest" to "strongest" based on the following conditions. number of characters types of characters uppercase alphanumeric characters included lowercase alphanumeric characters included numerals included symbols included privileged password ( confirm ) to confirm the password that you entered in the "privileged password" field, enter the password once again. encrypt password select the password encryption settings from the settings shown below. encrypt don’t encrypt you cannot restore a password that has been encrypted. the settings for this field will affect the following passwords. privileged password user account passwords</div><div class="display_word">3.1. Password settings Privileged password Enter the privileged password that you want to set. You can use up to 32 single-byte alphanumeric characters and symbols. (excluding "'|>?space ) If the password is not changed, select the Privileged password not changed check box. If a password has already been set, the Privileged password not changed check box will be selected by default. Refer to the password strength when deciding on your password, which is displayed as you type. The strength of the password is indicated in four levels from "weakest" to "strongest" based on the following conditions. Number of characters Types of characters Uppercase alphanumeric characters included Lowercase alphanumeric characters included Numerals included Symbols included Privileged password ( Confirm ) To confirm the password that you entered in the "Privileged password" field, enter the password once again. Encrypt password Select the password encryption settings from the settings shown below. Encrypt Don’t encrypt You cannot restore a password that has been encrypted. The settings for this field will affect the following passwords. Privileged password User account passwords</div></div><div id="gui_en_management_user"><div class="search_title" docfname="gui_en_management_user" doctitle="User" link="#user">4. User account settings page</div><div class="search_word">4. user account settings page this page is for configuring the user account settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">4. User account settings page This page is for configuring the user account settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_user"><div class="search_title" docfname="gui_en_management_user" doctitle="User" link="#user_account_settings_2">4.1. User account settings</div><div class="search_word">4.1. user account settings user name when configuring new settings specifies the user name to set. single-byte alphanumeric characters can be inputted. up to 32 characters can be inputted. the following text strings cannot be set. lp adm bin ftp gdm man rpc sys xfs halt mail news nscd sync uucp root sshd games daemon gopher nobody ftpuser mtsuser rpcuser mailnull operator shutdown when changing settings shows the selected user account name. new password enter the new password that you want to set. you can use up to 32 single-byte alphanumeric characters and symbols. (excluding "'|>?space ) the operation for password strength is the same as the "privileged password" item in the password settings page. new password ( confirm ) to confirm the password that you entered in the "new password" item, enter the password once again. administrative privileges select from one of the following administrative privileges. do not set set user accounts that have been given administrative privileges can log in as an administrative user when logging into the web gui.</div><div class="display_word">4.1. User account settings User name When configuring new settings Specifies the user name to set. Single-byte alphanumeric characters can be inputted. Up to 32 characters can be inputted. The following text strings cannot be set. lp adm bin ftp gdm man rpc sys xfs halt mail news nscd sync uucp root sshd games daemon gopher nobody ftpuser mtsuser rpcuser mailnull operator shutdown When changing settings Shows the selected user account name. New password Enter the new password that you want to set. You can use up to 32 single-byte alphanumeric characters and symbols. (excluding "'|>?space ) The operation for password strength is the same as the "Privileged password" item in the Password settings page. New password ( Confirm ) To confirm the password that you entered in the "New password" item, enter the password once again. Administrative privileges Select from one of the following administrative privileges. Do not set Set User accounts that have been given administrative privileges can log in as an administrative user when logging into the Web GUI.</div></div><div id="gui_en_management_yunos"><div class="search_title" docfname="gui_en_management_yunos" doctitle="Y-UNOS" link="#title-box">Y-UNOS (Yamaha Unified Network Operation Service)</div><div class="search_word">y-unos (yamaha unified network operation service)</div><div class="display_word">Y-UNOS (Yamaha Unified Network Operation Service)</div></div><div id="gui_en_management_yunos"><div class="search_title" docfname="gui_en_management_yunos" doctitle="Y-UNOS" link="#summary">1. Summary</div><div class="search_word">1. summary this is the page for operations related to the y-unos function. this function is not available when the stack function is enabled.</div><div class="display_word">1. Summary This is the page for operations related to the Y-UNOS function. This function is not available when the stack function is enabled.</div></div><div id="gui_en_management_yunos"><div class="search_title" docfname="gui_en_management_yunos" doctitle="Y-UNOS" link="#top_page">2. Top page</div><div class="search_word">2. top page this is the top page for the y-unos.</div><div class="display_word">2. Top page This is the top page for the Y-UNOS.</div></div><div id="gui_en_management_yunos"><div class="search_title" docfname="gui_en_management_yunos" doctitle="Y-UNOS" link="#system_settings">2.1. System settings</div><div class="search_word">2.1. system settings displays the current status of the y-unos function. press the "setting" button to display a page where you can change the settings of the y-unos function. the button is disabled when the stack function is enabled.</div><div class="display_word">2.1. System settings Displays the current status of the Y-UNOS function. Press the "Setting" button to display a page where you can change the settings of the Y-UNOS function. The button is disabled when the stack function is enabled.</div></div><div id="gui_en_management_yunos"><div class="search_title" docfname="gui_en_management_yunos" doctitle="Y-UNOS" link="#detected_devices_list">2.2. Detected devices list</div><div class="search_word">2.2. detected devices list press the "next" button to display a page where you can check the detected devices' information. the button is disabled when the stack function is enabled.</div><div class="display_word">2.2. Detected devices list Press the "Next" button to display a page where you can check the detected devices' information. The button is disabled when the stack function is enabled.</div></div><div id="gui_en_management_yunos"><div class="search_title" docfname="gui_en_management_yunos" doctitle="Y-UNOS" link="#function_setting">3. System settings page</div><div class="search_word">3. system settings page this page is for configuring the y-unos settings for the system. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. System settings page This page is for configuring the Y-UNOS settings for the system. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_yunos"><div class="search_title" docfname="gui_en_management_yunos" doctitle="Y-UNOS" link="#system_settings_2">3.1. System settings</div><div class="search_word">3.1. system settings y-unos function specify whether to enable or disable the y-unos function.</div><div class="display_word">3.1. System settings Y-UNOS function Specify whether to enable or disable the Y-UNOS function.</div></div><div id="gui_en_management_yunos"><div class="search_title" docfname="gui_en_management_yunos" doctitle="Y-UNOS" link="#detected_devices">4. Detected devices list page</div><div class="search_word">4. detected devices list page this page displays the information of devices detected by the y-unos function.</div><div class="display_word">4. Detected devices list page This page displays the information of devices detected by the Y-UNOS function.</div></div><div id="gui_en_management_yunos"><div class="search_title" docfname="gui_en_management_yunos" doctitle="Y-UNOS" link="#detected_devices_list_2">4.1. Detected devices list</div><div class="search_word">4.1. detected devices list displays the information of devices detected by the y-unos function. up to 128 items will be displayed. you can search neighbor information from the "search" box. press to execute the search. press to clear the search. you can use regular expressions shown below in search keywords. lowercase and capital letters are treated the same for keywords. syntax explanation a the character "a" abc the characters "abc" [abc] one character, either "a", "b" or "c" [a-c] one character between "a" and "c" [^abc] an arbitrary character that is neither "a", "b" or "c" . an arbitrary character a+ at least one "a" character a* at least zero "a" characters a? zero or one "a" character ^a a string that begins with "a" a$ a string that ends with "a" abc|def|ghi "abc", "def" or "ghi" a{2} two "a" characters (aa) a{2,} two or more "a" characters (aa, aaa, aaaa…​) a{2,3} two to three "a" characters (aa, aaa) \b word breaks, such as spaces \b any character besides \b \d an arbitrary number (same as [0-9]) \d any character besides numbers (same as [^0-9]) \s single breaking character \s any single character besides \s \w alphanumeric characters including underlines (same as [a-za-z0-9_]) \w any character besides \w press to update information to the latest information. the number of search results to display at one time can be selected by pressing "display number" on the "select" menu. press the sort switch to sort by each item. with default settings, the list is sorted in ascending order by model name. press the sort switch again to toggle between ascending and descending order.</div><div class="display_word">4.1. Detected devices list Displays the information of devices detected by the Y-UNOS function. Up to 128 items will be displayed. You can search neighbor information from the "Search" box. Press to execute the search. Press to clear the search. You can use regular expressions shown below in search keywords. Lowercase and capital letters are treated the same for keywords. Syntax Explanation A The character "A" ABC The characters "ABC" [ABC] One character, either "A", "B" or "C" [A-C] One character between "A" and "C" [^ABC] An arbitrary character that is neither "A", "B" or "C" . An arbitrary character A+ At least one "A" character A* At least zero "A" characters A? Zero or one "A" character ^A A string that begins with "A" A$ A string that ends with "A" ABC|DEF|GHI "ABC", "DEF" or "GHI" A{2} Two "A" characters (AA) A{2,} Two or more "A" characters (AA, AAA, AAAA…​) A{2,3} Two to three "A" characters (AA, AAA) \b Word breaks, such as spaces \B Any character besides \b \d An arbitrary number (same as [0-9]) \D Any character besides numbers (same as [^0-9]) \s Single breaking character \S Any single character besides \s \w Alphanumeric characters including underlines (same as [A-Za-z0-9_]) \W Any character besides \w Press to update information to the latest information. The number of search results to display at one time can be selected by pressing "Display number" on the "Select" menu. Press the sort switch to sort by each item. With default settings, the list is sorted in ascending order by model name. Press the sort switch again to toggle between ascending and descending order.</div></div><div id="gui_en_proav_proav_multicast"><div class="search_title" docfname="gui_en_proav_proav_multicast" doctitle="Multicast" link="#title-box">Multicast</div><div class="search_word">multicast</div><div class="display_word">Multicast</div></div><div id="gui_en_proav_proav_multicast"><div class="search_title" docfname="gui_en_proav_proav_multicast" doctitle="Multicast" link="#summary_multicast">1. Summary</div><div class="search_word">1. summary the multicast page can be used to configure igmp snooping and checkthe igmp snooping operating status separately for each proav profile. if multicasting via an avoip network, it is generally recommended thatigmp snooping be enabled, but that can lead to trouble if operated withimproper settings. by learning the basic principles of igmp snooping, this page can be used for simple troubleshooting of igmp snooping issues.</div><div class="display_word">1. Summary The Multicast page can be used to configure IGMP snooping and checkthe IGMP snooping operating status separately for each ProAV profile. If multicasting via an AVoIP network, it is generally recommended thatIGMP snooping be enabled, but that can lead to trouble if operated withimproper settings. By learning the basic principles of IGMP snooping, this page can be used for simple troubleshooting of IGMP snooping issues.</div></div><div id="gui_en_proav_proav_multicast"><div class="search_title" docfname="gui_en_proav_proav_multicast" doctitle="Multicast" link="#about_igmp_snooping">2. What’s IGMP snooping</div><div class="search_word">2. what’s igmp snooping igmp snooping is a feature that prevents unnecessary multicast traffic from being forwarded. normally, multicast traffic is flooded to all affiliated ports in the samenetwork, which wastes bandwidth by forwarding multicast traffic to ports where no multicast receiving terminal exists. in contrast, if igmpsnooping is enabled, it saves bandwidth by only forwarding the necessary multicast traffic to ports with a receiving terminal connected. thefollowing example shows the difference between flooding and igmpsnooping, assuming receiving terminal a (rx a) only wants to receivegroup a multicast traffic and receiving terminal b (rx b) only wants toreceive group b multicast traffic. flooding forwards both group a and group b traffic to the port where rx a is connected, but igmp snoopingonly forwards group a traffic to the port where rx a is connected. in the case of flooding in the case of igmp snooping switches with igmp snooping enabled use "igmp query" and "igmp report" to learn which multicast group traffic should be sent to which ports. the following example shows the process flow of processing igmp queries and igmp reports. one representative switch in the network periodically sends igmp queries. the switch that sends the igmp queries is called the "querier" . when the multicast receiving terminal receives an igmp query, itsends an igmp report in response. the igmp report contains informationabout the multicast group traffic that the receiving terminal wants toreceive. the switch learns which multicast group traffic to send to which port by snooping on the content in igmp reports. since learned multicast group information is automatically deletedafter a certain period of time, in order to maintain the correctlearning state one querier must always be present in the same network. if multiple queriers exist in the same network, only one querier isretained and the other switches automatically stop sending queries. note that even if there is no querier, the receiving terminal mayspontaneously send an igmp report, such as when the multicast receivingapplication is started in the receiving terminal. note that ifmulticast group information is learned without a querier present, thecorresponding multicast group traffic might not be forwarded to portswhere other receiving terminals are connected.</div><div class="display_word">2. What’s IGMP snooping IGMP snooping is a feature that prevents unnecessary multicast traffic from being forwarded. Normally, multicast traffic is flooded to all affiliated ports in the samenetwork, which wastes bandwidth by forwarding multicast traffic to ports where no multicast receiving terminal exists. In contrast, if IGMPsnooping is enabled, it saves bandwidth by only forwarding the necessary multicast traffic to ports with a receiving terminal connected. Thefollowing example shows the difference between flooding and IGMPsnooping, assuming receiving terminal A (RX A) only wants to receiveGroup A multicast traffic and receiving terminal B (RX B) only wants toreceive Group B multicast traffic. Flooding forwards both Group A and Group B traffic to the port where RX A is connected, but IGMP snoopingonly forwards Group A traffic to the port where RX A is connected. In the case of flooding In the case of IGMP snooping Switches with IGMP snooping enabled use "IGMP Query" and "IGMP Report" to learn which multicast group traffic should be sent to which ports. The following example shows the process flow of processing IGMP queries and IGMP reports. One representative switch in the network periodically sends IGMP queries. The switch that sends the IGMP queries is called the "Querier" . When the multicast receiving terminal receives an IGMP query, itsends an IGMP report in response. The IGMP report contains informationabout the multicast group traffic that the receiving terminal wants toreceive. The switch learns which multicast group traffic to send to which port by snooping on the content in IGMP reports. Since learned multicast group information is automatically deletedafter a certain period of time, in order to maintain the correctlearning state one querier must always be present in the same network. If multiple queriers exist in the same network, only one querier isretained and the other switches automatically stop sending queries. Note that even if there is no querier, the receiving terminal mayspontaneously send an IGMP report, such as when the multicast receivingapplication is started in the receiving terminal. Note that ifmulticast group information is learned without a querier present, thecorresponding multicast group traffic might not be forwarded to portswhere other receiving terminals are connected.</div></div><div id="gui_en_proav_proav_multicast"><div class="search_title" docfname="gui_en_proav_proav_multicast" doctitle="Multicast" link="#how_to_use_multicast">3. How to use this page</div><div class="search_word">3. how to use this page</div><div class="display_word">3. How to use this page</div></div><div id="gui_en_proav_proav_multicast"><div class="search_title" docfname="gui_en_proav_proav_multicast" doctitle="Multicast" link="#introduction_multicast">3.1. Introduction</div><div class="search_word">3.1. introduction this page can be used as a troubleshooting tool if a problem related to igmp snooping occurs. igmp snooping is enabled when profiles are specified on the proav profile page. in this page, igmp snooping settings can be changed and the igmpsnooping operating status checked separately for each proav profile. first, select a profile from the profile select box in the upper left corner of the page. if a proav profile has not been specified, specify the profile on the proav profiles page.</div><div class="display_word">3.1. Introduction This page can be used as a troubleshooting tool if a problem related to IGMP snooping occurs. IGMP snooping is enabled when profiles are specified on the ProAV profile page. In this page, IGMP snooping settings can be changed and the IGMPsnooping operating status checked separately for each ProAV profile. First, select a profile from the profile select box in the upper left corner of the page. If a ProAV profile has not been specified, specify the profile on the ProAV Profiles page.</div></div><div id="gui_en_proav_proav_multicast"><div class="search_title" docfname="gui_en_proav_proav_multicast" doctitle="Multicast" link="#warning_message">3.2. Warning message</div><div class="search_word">3.2. warning message when igmp snooping is enabled, a warning message appears if the switch detects improper settings. if a warning message appears, review the settings and change them if necessary. warning message display message how to handle warnings the igmp version (v2) specified in the profile does not match the version (v3) of the igmp query received. set the igmp version in the profile to the same version as the igmp query. change the igmp version. query transmission is stopped due to the presence of another querier enable igmp query transmission.</div><div class="display_word">3.2. Warning message When IGMP snooping is enabled, a warning message appears if the switch detects improper settings. If a warning message appears, review the settings and change them if necessary. Warning message Display message How to handle warnings The IGMP version (V2) specified in the profile does not match the version (V3) of the IGMP query received. Set the IGMP version in the profile to the same version as the IGMP query. Change the IGMP version. Query transmission is stopped due to the presence of another querier Enable IGMP query transmission.</div></div><div id="gui_en_proav_proav_multicast"><div class="search_title" docfname="gui_en_proav_proav_multicast" doctitle="Multicast" link="#igmp_snooping_set">3.3. Change IGMP snooping settings</div><div class="search_word">3.3. change igmp snooping settings the following settings related to igmp snooping can be changed for each proav profile igmp snooping settings disabled ( flood ip multicast packets ) disable igmp snooping multicast packets are always forwarded to all ports in the same vlan. enabled ( control transmission of ip multicast packets ) enable igmp snooping. multicast packets are forwarded only to the port to which the terminal you want to receive them is connected. this function monitors (snoops) igmp messages exchanged between receivingterminals and a multicast router. it can suppress the flooding ofmulticast packets and reduce network bandwidth usage. version select the igmp version from the following items. igmpv3 igmpv2 igmp query no transmission igmp query transmission function is disabled transmit periodically igmp query transmission function isenabled. the transmission interval can be specified in the range of 20seconds to 18000 seconds processing method for unknown multicast frames specify the processing method for unknown multicast frames from below. flood discard if igmp snooping is disabled, "flood" is automatically selected.</div><div class="display_word">3.3. Change IGMP snooping settings The following settings related to IGMP snooping can be changed for each ProAV profile IGMP snooping settings Disabled ( Flood IP multicast packets ) Disable IGMP snooping Multicast packets are always forwarded to all ports in the same VLAN. Enabled ( Control transmission of IP multicast packets ) Enable IGMP snooping. Multicast packets are forwarded only to the port to which the terminal you want to receive them is connected. This function monitors (snoops) IGMP messages exchanged between receivingterminals and a multicast router. It can suppress the flooding ofmulticast packets and reduce network bandwidth usage. Version Select the IGMP version from the following items. IGMPv3 IGMPv2 IGMP query No transmission IGMP query transmission function is disabled Transmit periodically IGMP query transmission function isenabled. The transmission interval can be specified in the range of 20seconds to 18000 seconds Processing method for unknown multicast frames Specify the processing method for unknown multicast frames from below. Flood Discard If IGMP snooping is disabled, "Flood" is automatically selected.</div></div><div id="gui_en_proav_proav_multicast"><div class="search_title" docfname="gui_en_proav_proav_multicast" doctitle="Multicast" link="#igmp_snooping_status">3.4. Check IGMP snooping operating status</div><div class="search_word">3.4. check igmp snooping operating status igmp snooping learning status can be checked for each proav profile. if a group is selected in the "multicast group" select box, the corresponding igmp report/query learning status is displayed. mouse-over the port with the learning status displayed to show a tooltip with detailed igmp report/query information. note that if both an igmp report and igmp query is received at the sameport, information about both are displayed in the tooltip. igmp report/query learning status display item port display tooltip information igmp report receiving port receiving port information last received report information （ ip address, version ） igmp query receiving port receiving port information received query information ( ip address, version ) since the learning status for multicast groups changes over time, click the "update" button to update the display. when a multicast group has been learned by an igmp report, the ipaddress of the multicast group is displayed in the "multicast group"select box. traffic being sent to learned multicast groups is only forwarded to igmp report receiving ports. unknown multicast groups are not displayed in the "multicast group" select box. if a proav profile is specified, unknown multicast group traffic is discarded. please change the setting, if you want to flood an unknown multicast group. if a problem that prevents receiving multicast traffic occurs, checkwhether the port indicator where the receiving terminal is connected isilluminated orange (which indicates it is an igmp report receivingport). if the connection port indicator is not orange, the receivingterminal might be connected to a port with a different profile. checkthe profile setting for the port where it is connected. if that doesnot solve the problem, try disabling igmp snooping, but determinewhether the bandwidth is sufficient before disabling igmp snooping.</div><div class="display_word">3.4. Check IGMP snooping operating status IGMP snooping learning status can be checked for each ProAV profile. If a group is selected in the "Multicast Group" select box, the corresponding IGMP report/query learning status is displayed. Mouse-over the port with the learning status displayed to show a tooltip with detailed IGMP report/query information. Note that if both an IGMP report and IGMP query is received at the sameport, information about both are displayed in the tooltip. IGMP report/query learning status Display item Port display Tooltip information IGMP report receiving port Receiving port information Last received report information （ IP address, Version ） IGMP query receiving port Receiving port information Received query information ( IP address, Version ) Since the learning status for multicast groups changes over time, click the "Update" button to update the display. When a multicast group has been learned by an IGMP report, the IPaddress of the multicast group is displayed in the "Multicast Group"select box. Traffic being sent to learned multicast groups is only forwarded to IGMP report receiving ports. Unknown multicast groups are not displayed in the "Multicast Group" select box. If a ProAV profile is specified, unknown multicast group traffic is discarded. Please change the setting, if you want to flood an unknown multicast group. If a problem that prevents receiving multicast traffic occurs, checkwhether the port indicator where the receiving terminal is connected isilluminated orange (which indicates it is an IGMP report receivingport). If the connection port indicator is not orange, the receivingterminal might be connected to a port with a different profile. Checkthe profile setting for the port where it is connected. If that doesnot solve the problem, try disabling IGMP snooping, but determinewhether the bandwidth is sufficient before disabling IGMP snooping.</div></div><div id="gui_en_proav_proav_profile"><div class="search_title" docfname="gui_en_proav_proav_profile" doctitle="ProAV" link="#title-box">ProAV profile</div><div class="search_word">proav profile</div><div class="display_word">ProAV profile</div></div><div id="gui_en_proav_proav_profile"><div class="search_title" docfname="gui_en_proav_proav_profile" doctitle="ProAV" link="#summary_profile">1. Summary</div><div class="search_word">1. summary the proav profile page can be used to configure all settings foroptimizing the avoip network that carries audio and video traffic. in this unit, following proav profiles can be configured. dante dante is an audio networking solution developed by audinate for professional audio applications. a single lan cable is used to bi-directionally communicate informationnecessary for digital audio systems, such as for transmitting multiplechannels of audio signals, clock synchronization signals, and controlsignals. ndi ndi is a new protocol developed by newtek that supports live video production workflows within ip applications. it enables real-time interactive transmission of video, audio, meta data, and other information within typical gigabit ethernet environments. for details on the commands configured by a proav profile, refer to yamaha network devices technical documentation .</div><div class="display_word">1. Summary The ProAV Profile page can be used to configure all settings foroptimizing the AVoIP network that carries audio and video traffic. In this unit, following ProAV profiles can be configured. Dante Dante is an audio networking solution developed by Audinate for professional audio applications. A single LAN cable is used to bi-directionally communicate informationnecessary for digital audio systems, such as for transmitting multiplechannels of audio signals, clock synchronization signals, and controlsignals. NDI NDI is a new protocol developed by Newtek that supports live video production workflows within IP applications. It enables real-time interactive transmission of video, audio, meta data, and other information within typical Gigabit Ethernet environments. For details on the commands configured by a ProAV profile, refer to Yamaha Network Devices Technical Documentation .</div></div><div id="gui_en_proav_proav_profile"><div class="search_title" docfname="gui_en_proav_proav_profile" doctitle="ProAV" link="#how_to_use_profile">2. How to use this page</div><div class="search_word">2. how to use this page</div><div class="display_word">2. How to use this page</div></div><div id="gui_en_proav_proav_profile"><div class="search_title" docfname="gui_en_proav_proav_profile" doctitle="ProAV" link="#introduction_profile">2.1. Introduction</div><div class="search_word">2.1. introduction this page can be used as a kitting tool for configuring optimal avoip network settings. qos, multicast control, and other settings can all be set to optimal valuesat the same time by simply selecting a proav profile. the proav profile configured on this page assumes the unit will be used as a dedicated switch for an avoip network. if building a complex network, such as by combining an avoip network withan existing internal network, specify appropriate settings on the guidetails settings page or by using commands. this page assumes that an ip address is assigned to vlan1. if vlan1 is not assigned an ip address, assign an ip address to vlan1 and access the web gui from a port associated to vlan1. the vlan1 ip address is already specified in factory default settings, so the setting does not need to be changed before use. note that the ports that belong to a logical interface must be removed from the logical interface. if necessary, remove ports from the logical interface, assign a profile, and then reassign ports to the logical interface.</div><div class="display_word">2.1. Introduction This page can be used as a kitting tool for configuring optimal AVoIP network settings. QoS, multicast control, and other settings can all be set to optimal valuesat the same time by simply selecting a ProAV profile. The ProAV profile configured on this page assumes the unit will be used as a dedicated switch for an AVoIP network. If building a complex network, such as by combining an AVoIP network withan existing internal network, specify appropriate settings on the GUIDetails settings page or by using commands. This page assumes that an IP address is assigned to VLAN1. If VLAN1 is not assigned an IP address, assign an IP address to VLAN1 and access the web GUI from a port associated to VLAN1. The VLAN1 IP address is already specified in factory default settings, so the setting does not need to be changed before use. Note that the ports that belong to a logical interface must be removed from the logical interface. If necessary, remove ports from the logical interface, assign a profile, and then reassign ports to the logical interface.</div></div><div id="gui_en_proav_proav_profile"><div class="search_title" docfname="gui_en_proav_proav_profile" doctitle="ProAV" link="#dante_profile">2.2. Set Dante profile</div><div class="search_word">2.2. set dante profile the dante optimization settings is applied. in a dante network, settings vary depending on the network structure.</div><div class="display_word">2.2. Set Dante profile The Dante optimization settings is applied. In a Dante network, settings vary depending on the network structure.</div></div><div id="gui_en_proav_proav_profile"><div class="search_title" docfname="gui_en_proav_proav_profile" doctitle="ProAV" link="#dante_primary">2.2.1. Use as Dante primaly dedecated line</div><div class="search_word">2.2.1. use as dante primaly dedecated line dante primary select this network structure when the switch is used as a dante dedicated primary line. assign all ports to the same network and apply the dante primary profile. note that the only differences from selecting "use as dante secondarydedicated line" are the profile name and color settings. all othersettings are the same.</div><div class="display_word">2.2.1. Use as Dante primaly dedecated line Dante primary Select this network structure when the switch is used as a Dante dedicated primary line. Assign all ports to the same network and apply the Dante primary profile. Note that the only differences from selecting "Use as Dante SecondaryDedicated Line" are the profile name and color settings. All othersettings are the same.</div></div><div id="gui_en_proav_proav_profile"><div class="search_title" docfname="gui_en_proav_proav_profile" doctitle="ProAV" link="#dante_secondary">2.2.2. Use as Dante secondary dedecated line</div><div class="search_word">2.2.2. use as dante secondary dedecated line dante secondary select this network structure when the switch is used as a dante dedicated secondary line. assign all ports to the same network and apply the dante secondary profile. note that the only differences from selecting "use as dante primarydedicated line" are the profile name and color settings. all othersettings are the same.</div><div class="display_word">2.2.2. Use as Dante secondary dedecated line Dante secondary Select this network structure when the switch is used as a Dante dedicated secondary line. Assign all ports to the same network and apply the Dante secondary profile. Note that the only differences from selecting "Use as Dante PrimaryDedicated Line" are the profile name and color settings. All othersettings are the same.</div></div><div id="gui_en_proav_proav_profile"><div class="search_title" docfname="gui_en_proav_proav_profile" doctitle="ProAV" link="#dante_trunk">2.2.3. Bundle Dante primary/secondary lines</div><div class="search_word">2.2.3. bundle dante primary/secondary lines dante primary dante secondary trunk select this network structure when the primary and secondary linesare bundled together for connecting a single lan cable between switches. separate the network between the primary line and the secondary line, and apply a dante profile to both networks. the settings applied are the same for the primary and secondary lines. the trunk port sends and receives both dante primary and secondary traffic bundled together. designate the ports used to connect to other switches and the corresponding ports on the connected switches as trunk ports. to change the default primary, secondary, and trunk assignmentsettings, the horizontal and vertical buttons can be used to togglebetween vertical and horizontal partition configurations in defaultsettings. the horizon button does not appear on models with a single row of ports. primary, secondary, and trunk assignments can be changed manually byclicking on the profile selection button and then clicking on the port. since the gui cannot be accessed from the secondary ports, assign the primary profile or trunk status to the port used to connect the computer to the gui.</div><div class="display_word">2.2.3. Bundle Dante primary/secondary lines Dante primary Dante secondary Trunk Select this network structure when the primary and secondary linesare bundled together for connecting a single LAN cable between switches. Separate the network between the primary line and the secondary line, and apply a Dante profile to both networks. The settings applied are the same for the primary and secondary lines. The trunk port sends and receives both Dante primary and secondary traffic bundled together. Designate the ports used to connect to other switches and the corresponding ports on the connected switches as trunk ports. To change the default primary, secondary, and trunk assignmentsettings, the Horizontal and Vertical buttons can be used to togglebetween vertical and horizontal partition configurations in defaultsettings. The Horizon button does not appear on models with a single row of ports. Primary, secondary, and trunk assignments can be changed manually byclicking on the profile selection button and then clicking on the port. Since the GUI cannot be accessed from the secondary ports, assign the primary profile or trunk status to the port used to connect the computer to the GUI.</div></div><div id="gui_en_proav_proav_profile"><div class="search_title" docfname="gui_en_proav_proav_profile" doctitle="ProAV" link="#dante_redundant">2.2.4. Redundant Dante primary/secondary lines</div><div class="search_word">2.2.4. redundant dante primary/secondary lines dante primary dante secondary select this network structure when configuring redundant primary andsecondary lines and using two lan cables to connect between switches. separate the network between the primary line and the secondary line, and apply a dante profile to both networks. the settings applied are the same for the primary and secondary lines, butin this network configuration, an l2ms filter is applied to ports on the secondary line to prevent loops. note that l2ms agents connected only to a dante secondary port will not be detected by the lan map or yamaha lan monitor. to change the default primary and secondary assignment settings, thehorizontal and vertical buttons can be used to toggle between verticaland horizontal partition configurations in default settings. the horizon button does not appear on models with a single row of ports. primary and secondary assignments can be changed manually by clicking on the profile selection button and then clicking on the port. since the gui cannot be accessed from the secondary ports, assign the primary profile to the port used to connect the computer to the gui.</div><div class="display_word">2.2.4. Redundant Dante primary/secondary lines Dante primary Dante secondary Select this network structure when configuring redundant primary andsecondary lines and using two LAN cables to connect between switches. Separate the network between the primary line and the secondary line, and apply a Dante profile to both networks. The settings applied are the same for the primary and secondary lines, butin this network configuration, an L2MS filter is applied to ports on the secondary line to prevent loops. Note that L2MS agents connected only to a Dante secondary port will not be detected by the LAN map or Yamaha LAN Monitor. To change the default primary and secondary assignment settings, theHorizontal and Vertical buttons can be used to toggle between verticaland horizontal partition configurations in default settings. The Horizon button does not appear on models with a single row of ports. Primary and secondary assignments can be changed manually by clicking on the profile selection button and then clicking on the port. Since the GUI cannot be accessed from the secondary ports, assign the primary profile to the port used to connect the computer to the GUI.</div></div><div id="gui_en_proav_proav_profile"><div class="search_title" docfname="gui_en_proav_proav_profile" doctitle="ProAV" link="#ndi_profile">2.3. Set NDI profile</div><div class="search_word">2.3. set ndi profile the ndi optimization settings is applied. assign all ports to the same network and apply the ndi profile.</div><div class="display_word">2.3. Set NDI profile The NDI optimization settings is applied. Assign all ports to the same network and apply the NDI profile.</div></div><div id="gui_en_proav_proav_profile"><div class="search_title" docfname="gui_en_proav_proav_profile" doctitle="ProAV" link="#multiple_profile">2.4. Set multiple ProAV profiles</div><div class="search_word">2.4. set multiple proav profiles multiple proav profiles can be applied by partitioning the network using vlans. with default settings, vlan1 is assigned to the dante primary line,vlan2 to the dante secondary line, and vlan3 to the ndi network. traffic for all selected profiles is sent/received via the specified trunk port. designate the ports used to connect to other switches and the corresponding ports on the connected switches as trunk ports. the vlan1 is set as the native vlan (untagged) and other vlans are set as the tagged vlan. as a precaution, when connecting the switch to another switch on a trunk,be sure to set the same profile-vlan assignment settings in bothswitches. the vlan assignment for a profile can be changed using the "change vlan" button. note that vlan1 must be assigned to one of the profiles. profile assignments to ports can be changed manually by clicking on the profile selection button and then clicking on the port. since the gui cannot be accessed from ports not affiliated with vlan1 (*),assign the vlan1 profile or trunk status to the port used to connect the computer to the gui. * this page assumes that an ip address is assigned to vlan1.</div><div class="display_word">2.4. Set multiple ProAV profiles Multiple ProAV profiles can be applied by partitioning the network using VLANs. With default settings, VLAN1 is assigned to the Dante primary line,VLAN2 to the Dante secondary line, and VLAN3 to the NDI network. Traffic for all selected profiles is sent/received via the specified trunk port. Designate the ports used to connect to other switches and the corresponding ports on the connected switches as trunk ports. The VLAN1 is set as the native VLAN (untagged) and other VLANs are set as the tagged VLAN. As a precaution, when connecting the switch to another switch on a trunk,be sure to set the same Profile-VLAN assignment settings in bothswitches. The VLAN assignment for a profile can be changed using the "Change VLAN" button. Note that VLAN1 must be assigned to one of the profiles. Profile assignments to ports can be changed manually by clicking on the profile selection button and then clicking on the port. Since the GUI cannot be accessed from ports not affiliated with VLAN1 (*),assign the VLAN1 profile or trunk status to the port used to connect the computer to the GUI. * This page assumes that an IP address is assigned to VLAN1.</div></div><div id="gui_en_proav_proav_profile"><div class="search_title" docfname="gui_en_proav_proav_profile" doctitle="ProAV" link="#return_to_defaults">2.5. Return to defaults</div><div class="search_word">2.5. return to defaults press the "return to defaults" button to initialize the settings ofall vlans for which a profile is set, and all ports will be assigned tovlan1. note that the settings of vlans for which no profile is set will not be initialized.</div><div class="display_word">2.5. Return to defaults Press the "Return to defaults" button to initialize the settings ofall VLANs for which a profile is set, and all ports will be assigned toVLAN1. Note that the settings of VLANs for which no profile is set will not be initialized.</div></div><div id="gui_en_proav_proav_profile"><div class="search_title" docfname="gui_en_proav_proav_profile" doctitle="ProAV" link="#trademark">3. Trademark attributions</div><div class="search_word">3. trademark attributions dante™ is a trademark of audinate pty ltd. ndi® is a registered trademark of vizrt ndi ab.</div><div class="display_word">3. Trademark attributions Dante™ is a trademark of Audinate Pty Ltd. NDI® is a registered trademark of Vizrt NDI AB.</div></div><div id="index"><div class="search_title" docfname="index" doctitle="SWX2310P" link="#swx2310pシリーズ-技術資料">SWX2310P Series Technical Data</div><div class="search_word">swx2310p series technical data thank you for purchasing a yamaha swx2310p series switch. before using the product, be sure to read this manual carefully to ensure the product is installed and settings are configured properly. be sure to observe the warnings and cautions indicated in this manual and use the product correctly and safely.</div><div class="display_word">SWX2310P Series Technical Data Thank you for purchasing a Yamaha SWX2310P series switch. Before using the product, be sure to read this manual carefully to ensure the product is installed and settings are configured properly. Be sure to observe the warnings and cautions indicated in this manual and use the product correctly and safely.</div></div><div id="index"><div class="search_title" docfname="index" doctitle="SWX2310P" link="#このページの使い方">1. How to Use This Page</div><div class="search_word">1. how to use this page select the firmware version. change the “firmware version” at the top of the screen to the version of your device. by default, the latest firmware version is selected. select the item you want to look up. select the item you want to display from the accordion menu on the left side of the screen .</div><div class="display_word">1. How to Use This Page Select the firmware version. Change the “Firmware version” at the top of the screen to the version of your device. By default, the latest firmware version is selected. Select the item you want to look up. Select the item you want to display from the accordion menu on the left side of the screen .</div></div><div id="index"><div class="search_title" docfname="index" doctitle="SWX2310P" link="#スタートアップガイド">2. Startup Guide</div><div class="search_word">2. startup guide this guide describes the setup procedure up to the point swx2310p series settings can start being specified. settings for the swx2310p series can be specified using any of the following four methods. specify settings by executing commands using the console port. specify settings by executing commands using telnet. specify settings by executing commands using ssh. specify settings using a web browser.</div><div class="display_word">2. Startup Guide This guide describes the setup procedure up to the point SWX2310P series settings can start being specified. Settings for the SWX2310P series can be specified using any of the following four methods. Specify settings by executing commands using the CONSOLE port. Specify settings by executing commands using Telnet. Specify settings by executing commands using SSH. Specify settings using a web browser.</div></div><div id="index"><div class="search_title" docfname="index" doctitle="SWX2310P" link="#consoleポートによる設定の開始手順">2.1. Preparation for Specifying Settings via the CONSOLE Port</div><div class="search_word">2.1. preparation for specifying settings via the console port prepare the computer and other items needed for specifying settings. if specifying settings via the console port, use a usb cable or rj-45/db-9 console cable (yrc-rj45) . use a usb cable that supports data transfer via both a usb type a connector and a mini-usb type b (5-pin) connector to connect to the mini-usb console port. charge-only cables cannot be used. terminal software is also needed for controlling the computer serial (com) port. configure communication settings for the console terminal as follows. baud rate: 9600bps data: 8bit parity: none stop bit: 1bit flow control: xon/xoff use a usb cable or an rj-45/db-9 console cable (yrc-rj45) to connect a computer to the product. a usb serial driver must be installed before the mini-usb console port can be used. for details on how to install the usb serial driver, refer to “yamaha network device usb serial driver installation guide.” the yamaha network device usb serial driver installation guide and the installer can be downloaded from the following website. https://network.yamaha.com/support/download/utility/ switch on the unit. the unit takes approximately 70 seconds to start up. immediately after startup, the following is displayed on the serial console screen. yamahal2sw bootrom ver.1.00starting .............................swx2310p-28gt rev.2.02.06 (tue mar 13 08:41:39 2018)  copyright (c) 2018 yamaha corporation. all rights reserved. log in to this unit. for factory default settings, log in by entering “admin” as the default administrative username (and  “admin” as the password). after using “admin” to log in, the password must be changed to specify a new password. username: adminpassword: adminswx2310p-28gt rev.2.02.06 (tue mar 13 08:41:39 2018)  copyright (c) 2018 yamaha corporation. all rights reserved.please change the default password for admin.new password: (1) new password(confirm): (2) saving ...succeeded to write configurationswx2310p> 1 enter the new password. 2 enter the same password again. after that, specify settings as appropriate for the given product operating environment. for details on settings via the serial console, refer to command reference .</div><div class="display_word">2.1. Preparation for Specifying Settings via the CONSOLE Port Prepare the computer and other items needed for specifying settings. If specifying settings via the CONSOLE port, use a USB cable or RJ-45/DB-9 console cable (YRC-RJ45) . Use a USB cable that supports data transfer via both a USB Type A connector and a mini-USB Type B (5-pin) connector to connect to the mini-USB CONSOLE port. Charge-only cables cannot be used. Terminal software is also needed for controlling the computer serial (COM) port. Configure communication settings for the CONSOLE terminal as follows. Baud rate: 9600bps Data: 8bit Parity: None Stop bit: 1bit Flow control: Xon/Xoff Use a USB cable or an RJ-45/DB-9 console cable (YRC-RJ45) to connect a computer to the product. A USB serial driver must be installed before the mini-USB CONSOLE port can be used. For details on how to install the USB serial driver, refer to “Yamaha Network Device USB Serial Driver Installation Guide.” The Yamaha Network Device USB Serial Driver Installation Guide and the installer can be downloaded from the following website. https://network.yamaha.com/support/download/utility/ Switch ON the unit. The unit takes approximately 70 seconds to start up. Immediately after startup, the following is displayed on the serial console screen. YamahaL2SW BootROM Ver.1.00Starting .............................SWX2310P-28GT Rev.2.02.06 (Tue Mar 13 08:41:39 2018)  Copyright (c) 2018 Yamaha Corporation. All Rights Reserved. Log in to this unit. For factory default settings, log in by entering “admin” as the default administrative username (and  “admin” as the password). After using “admin” to log in, the password must be changed to specify a new password. Username: adminPassword: adminSWX2310P-28GT Rev.2.02.06 (Tue Mar 13 08:41:39 2018)  Copyright (c) 2018 Yamaha Corporation. All Rights Reserved.Please change the default password for admin.New Password: (1) New Password(Confirm): (2) Saving ...Succeeded to write configurationSWX2310P> 1 Enter the new password. 2 Enter the same password again. After that, specify settings as appropriate for the given product operating environment. For details on settings via the serial console, refer to Command Reference .</div></div><div id="index"><div class="search_title" docfname="index" doctitle="SWX2310P" link="#telnet-ssh-webブラウザーによる設定の開始手順">2.2. Preparation for Specifying Settings via Telnet, SSH, or a Web Browser</div><div class="search_word">2.2. preparation for specifying settings via telnet, ssh, or a web browser prepare the computer and other items needed for specifying settings. prepare an ethernet cable of category 5 for connecting to the product. to access the unit via telnet or ssh, telnet or ssh terminal software must be installed on the computer. for a list of compatible web browsers, see the website below. http://www.rtpro.yamaha.co.jp/rt/faq/gui/browser.html change the ip address of the computer used to specify settings. the default setting of 192.168.100.240/24 is specified in the unit. change the ip address for the computer used to specify settings so that it includes the segment 192.168.100.0/24 . if a fixed computer ip address is specified, write it down. for instructions on how to change computer ip addresses, refer to the computer instruction manual. use an ethernet cable of category 5 to connect the unit to a computer. switch on the unit. the unit takes approximately 70 seconds to start up. when startup is completed, the indicators for the lan port to which the ethernet cable is connected will light up according to the communication speed and mode. access the unit using the computer for specifying settings. access from a telnet client access the unit (192.168.100.240) using terminal software. when access is successful, a screen that prompts for a username and password is displayed. for factory default settings, log in by entering “admin” as the default administrative username (and  “admin” as the password). after using “admin” to log in, the password must be changed to specify a new password. username: adminpassword: adminswx2310p-28gt rev.2.02.06 (tue mar 13 08:41:39 2018)  copyright (c) 2018 yamaha corporation. all rights reserved.please change the default password for admin.new password: (1) new password(confirm): (2) saving ...succeeded to write configurationswx2310p> 1 enter the new password. 2 enter the same password again. access from an ssh client to access the unit from an ssh client, specify the following unit settings in advance. generate an ssh server host key and enable the ssh server function. swx2310p>enableswx2310p#ssh-server host key generate  (generates host key)swx2310p#configure terminalswx2310p(config)#ssh-server enable     (enables functionality) register a user name and password. swx2310p(config)#username yamaha privilege on password 1a2b3c4d (registers username “yamaha” and password “1a2b3c4d”)swx2310p(config)#exit if specified in advance, save settings as necessary. swx2310p#writesucceeded to write configuration.swx2310p# with the above settings specified, access the unit (192.168.100.240) using terminal software. when access is successful, a screen that prompts for a username and password is displayed. enter the user name and password to enable login. username: yamaha   (if “yamaha” was specified)password: 1a2b3c4d (if “1a2b3c4d” was specified)swx2310p-28gt rev.2.02.06 (tue mar 13 08:41:39 2018)  copyright (c) 2018 yamaha corporation. all rights reserved.swx2310p> note that the product does not support the following ssh server functions. ssh protocol version 1 user authentication other than password authentication (host-based authentication, public-key authentication, challenge–response authentication, gssapi authentication) port forwarding (x11/tcp forwarding) gateway ports permitting blank passwords access from a web browser launch the web browser on the computer for specifying settings and access 192.168.100.240. when access is successful, the following login screen is displayed. if default settings are configured, log in by entering “admin” as the default administrative username (and “admin” as the password). then specify a new password later, when prompted to change the default administrative password. after that, specify settings as appropriate for the given product operating environment. for details on specifying settings from a telnet client or ssh client, refer to command reference . for details on specifying settings via a web browser, refer to help within the gui accessed.</div><div class="display_word">2.2. Preparation for Specifying Settings via Telnet, SSH, or a Web Browser Prepare the computer and other items needed for specifying settings. Prepare an Ethernet cable of category 5 for connecting to the product. To access the unit via Telnet or SSH, Telnet or SSH terminal software must be installed on the computer. For a list of compatible web browsers, see the website below. http://www.rtpro.yamaha.co.jp/RT/FAQ/gui/browser.html Change the IP address of the computer used to specify settings. The default setting of 192.168.100.240/24 is specified in the unit. Change the IP address for the computer used to specify settings so that it includes the segment 192.168.100.0/24 . If a fixed computer IP address is specified, write it down. For instructions on how to change computer IP addresses, refer to the computer instruction manual. Use an Ethernet cable of category 5 to connect the unit to a computer. Switch ON the unit. The unit takes approximately 70 seconds to start up. When startup is completed, the indicators for the LAN port to which the Ethernet cable is connected will light up according to the communication speed and mode. Access the unit using the computer for specifying settings. Access from a Telnet client Access the unit (192.168.100.240) using terminal software. When access is successful, a screen that prompts for a username and password is displayed. For factory default settings, log in by entering “admin” as the default administrative username (and  “admin” as the password). After using “admin” to log in, the password must be changed to specify a new password. Username: adminPassword: adminSWX2310P-28GT Rev.2.02.06 (Tue Mar 13 08:41:39 2018)  Copyright (c) 2018 Yamaha Corporation. All Rights Reserved.Please change the default password for admin.New Password: (1) New Password(Confirm): (2) Saving ...Succeeded to write configurationSWX2310P> 1 Enter the new password. 2 Enter the same password again. Access from an SSH client To access the unit from an SSH client, specify the following unit settings in advance. Generate an SSH server host key and enable the SSH server function. SWX2310P>enableSWX2310P#ssh-server host key generate  (Generates host key)SWX2310P#configure terminalSWX2310P(config)#ssh-server enable     (Enables functionality) Register a user name and password. SWX2310P(config)#username yamaha privilege on password 1a2b3c4d (Registers username “yamaha” and password “1a2b3c4d”)SWX2310P(config)#exit If specified in advance, save settings as necessary. SWX2310P#writeSucceeded to write configuration.SWX2310P# With the above settings specified, access the unit (192.168.100.240) using terminal software. When access is successful, a screen that prompts for a username and password is displayed. Enter the user name and password to enable login. Username: yamaha   (If “yamaha” was specified)Password: 1a2b3c4d (If “1a2b3c4d” was specified)SWX2310P-28GT Rev.2.02.06 (Tue Mar 13 08:41:39 2018)  Copyright (c) 2018 Yamaha Corporation. All Rights Reserved.SWX2310P> Note that the product does not support the following SSH server functions. SSH protocol version 1 User authentication other than password authentication (host-based authentication, public-key authentication, challenge–response authentication, GSSAPI authentication) Port forwarding (X11/TCP forwarding) Gateway ports Permitting blank passwords Access from a web browser Launch the web browser on the computer for specifying settings and access 192.168.100.240. When access is successful, the following login screen is displayed. If default settings are configured, log in by entering “admin” as the default administrative username (and “admin” as the password). Then specify a new password later, when prompted to change the default administrative password. After that, specify settings as appropriate for the given product operating environment. For details on specifying settings from a Telnet client or SSH client, refer to Command Reference . For details on specifying settings via a web browser, refer to Help within the GUI accessed.</div></div><div id="index"><div class="search_title" docfname="index" doctitle="SWX2310P" link="#ファームウェア更新について">3. Updating Firmware</div><div class="search_word">3. updating firmware to ensure reliable operation, we recommend applying the most recent firmware updates, which include new functionality and bug fixes. please verify your system version before applying updates. use the show environment command to check the system version.</div><div class="display_word">3. Updating Firmware To ensure reliable operation, we recommend applying the most recent firmware updates, which include new functionality and bug fixes. Please verify your system version before applying updates. Use the show environment command to check the system version.</div></div><div id="index"><div class="search_title" docfname="index" doctitle="SWX2310P" link="#使用上のご注意">4. Precautions</div><div class="search_word">4. precautions please note that yamaha accepts no responsibility for damage or losses that result from using the product or specifying settings incorrectly. be aware of this in advance. if plugged into a 200 v ac power supply outlet, the customer is responsible for supplying an appropriate power cord. note that yamaha accepts no responsibility for any of various types of damage or losses caused by the power cord. be aware of this in advance. do not touch the inside of ports with fingers or metallic objects, etc. do not install the product where it is exposed to direct sunlight or unusually high temperatures (such as next to a heater). do not use the product in a location subject to sudden changes in ambient temperature. sudden changes in ambient temperature could cause condensation to form on the product. if condensation forms, let it dry for a while before switching on the power supply. before touching this unit, remove static charge from yourself and your clothing. do not place this unit in locations where there is a strong magnetic field. do not connect equipment that generates noise to the same electrical power supply line as this unit. such conditions might cause malfunctions or faulty operation. using the product could cause noise to occur in nearby devices, such as telephones, radios, or televisions. if noise occurs, try relocating or reorienting the product. do not route communication cables near power cords. power cords could induce high voltages that might cause malfunction. unplug the product from the power outlet while not in use. use enhanced category 5 (cat5e) or better lan cable for 1000base-t connections. this product includes a lithium-ion battery for backup power for clock functionality. therefore, the product and its accessories are disposed of in accordance with local laws and regulations. do not install sfp modules other than the ysfp-g-sx, ysfp-g-lx, ysfp-g-sxa, and ysfp-glxa that are sold separately by yamaha into the sfp port. the operation is not guaranteed if any sfp module other than those indicated above is installed. do not install sfp modules other than the ysfp-10g-sr, ysfp-10g-lr, ydac-10g-3m, ydac-10g-1m, ysfp-g-sx, ysfp-g-lx, ysfp-g-sxa, and ysfp-g-lxa that are sold separately by yamaha into the sfp+ port. the operation is not guaranteed if any sfp module other than those indicated above is installed. attach a dust cover to all unused sfp and sfp+ ports. if foreign matter gets inside the port, it could cause a malfunction. keep the dust covers carefully stored so they are not lost. sfp modules and optical fiber cables can have problems with insufficient light input, failure to link up, or other issues due to loss of accuracy caused by connector damage or abrasion, dirty contacts, or other factors. in particular, single mode fiber should be handled especially carefully because it is more prone to suffer such effects than multi mode fiber. clean the contacts before making connections. also, attach the protective cap when not in use.</div><div class="display_word">4. Precautions Please note that Yamaha accepts no responsibility for damage or losses that result from using the product or specifying settings incorrectly. Be aware of this in advance. If plugged into a 200 V AC power supply outlet, the customer is responsible for supplying an appropriate power cord. Note that Yamaha accepts no responsibility for any of various types of damage or losses caused by the power cord. Be aware of this in advance. Do not touch the inside of ports with fingers or metallic objects, etc. Do not install the product where it is exposed to direct sunlight or unusually high temperatures (such as next to a heater). Do not use the product in a location subject to sudden changes in ambient temperature. Sudden changes in ambient temperature could cause condensation to form on the product. If condensation forms, let it dry for a while before switching ON the power supply. Before touching this unit, remove static charge from yourself and your clothing. Do not place this unit in locations where there is a strong magnetic field. Do not connect equipment that generates noise to the same electrical power supply line as this unit. Such conditions might cause malfunctions or faulty operation. Using the product could cause noise to occur in nearby devices, such as telephones, radios, or televisions. If noise occurs, try relocating or reorienting the product. Do not route communication cables near power cords. Power cords could induce high voltages that might cause malfunction. Unplug the product from the power outlet while not in use. Use enhanced category 5 (CAT5e) or better LAN cable for 1000BASE-T connections. This product includes a lithium-ion battery for backup power for clock functionality. Therefore, the product and its accessories are disposed of in accordance with local laws and regulations. Do not install SFP modules other than the YSFP-G-SX, YSFP-G-LX, YSFP-G-SXA, and YSFP-GLXA that are sold separately by Yamaha into the SFP port. The operation is not guaranteed if any SFP module other than those indicated above is installed. Do not install SFP modules other than the YSFP-10G-SR, YSFP-10G-LR, YDAC-10G-3M, YDAC-10G-1M, YSFP-G-SX, YSFP-G-LX, YSFP-G-SXA, and YSFP-G-LXA that are sold separately by Yamaha into the SFP+ port. The operation is not guaranteed if any SFP module other than those indicated above is installed. Attach a dust cover to all unused SFP and SFP+ ports. If foreign matter gets inside the port, it could cause a malfunction. Keep the dust covers carefully stored so they are not lost. SFP modules and optical fiber cables can have problems with insufficient light input, failure to link up, or other issues due to loss of accuracy caused by connector damage or abrasion, dirty contacts, or other factors. In particular, single mode fiber should be handled especially carefully because it is more prone to suffer such effects than multi mode fiber. Clean the contacts before making connections. Also, attach the protective cap when not in use.</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#radius-server">RADIUS server</div><div class="search_word">radius server</div><div class="display_word">RADIUS server</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview the radius server function manages user information and certificates, and performs authentication based on information notified from the client. by combining with mac authentication, 802.1x authentication, and web authentication of this device, the authentication function can be realized with this device alone. also, when authenticating with a device other than this device, this device can be operated as an authentication server. the basic performance of the radius server function and the corresponding authentication method are as follows. basic performance item performance number of radius clients that can be registered 100 number of users that can be registered 2000 key strength 2048 bit signature algorithm sha256 certificate authority name (default value) swx-radius supported authentication methods authentication method application pap mac authentication eap-md5 ieee802.1x authentication, mac authentication, web authentication eap-tls ieee802.1x authentication eap-ttls ieee802.1x authentication peap ieee802.1x authentication</div><div class="display_word">1. Function Overview The RADIUS server function manages user information and certificates, and performs authentication based on information notified from the client. By combining with MAC authentication, 802.1X authentication, and Web authentication of this device, the authentication function can be realized with this device alone. Also, when authenticating with a device other than this device, this device can be operated as an authentication server. The basic performance of the RADIUS server function and the corresponding authentication method are as follows. Basic performance Item Performance Number of RADIUS clients that can be registered 100 Number of users that can be registered 2000 Key strength 2048 bit Signature algorithm SHA256 Certificate Authority name (default value) swx-radius Supported authentication methods Authentication method Application PAP MAC authentication EAP-MD5 IEEE802.1X authentication, MAC authentication, WEB authentication EAP-TLS IEEE802.1X authentication EAP-TTLS IEEE802.1X authentication PEAP IEEE802.1X authentication</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used pki (public key infrastructure) public key infrastructure. includes digital certificates and certificate authorities (cas) using public key cryptography. certificate authority (ca) an organization that guarantees reliability. it is divided into a root certificate authority and an intermediate certificate authority. it has a tree structure with the root certificate authority at the top and an intermediate certificate authority under it. intermediate certificate authority among certificate authorities (cas), indicates a certificate authority whose reliability is guaranteed by a higher-level certificate authority (ca). root certificate authority among certificate authorities (ca), indicates a certificate authority whose reliability is guaranteed by itself. root certificate authority certificate a public key certificate that has the same issuer and subject and has signed its own public key with its own private key. it is the root of a tree-structured certificate. digital certificate data that certifies that the public key issued by the certificate authority is the genuine issuer’s public key. when the issuer makes a certificate request to the certificate authority (ca) together with the public key, the certificate authority (ca) issues a digital certificate after scrutinizing and confirming it. eap-md5 authentication method (message digest algorithm 5) this is an authentication method that uses a user name and password. authenticates by exchanging an md5 hash value instead of a plain text password. eap-tls authentication method (transport layer security) an authentication method used in ieee 802.1x, a type of eap implementation that authenticates by exchanging digital certificates after encrypting the transport layer between the user and the radius server, instead of authenticating with a user id and password. this is defined in rfc2716 and rfc5216. eap-ttls authentication method (tunneled tls) an authentication method used in ieee 802.1x, a type of eap implementation that establishes a tls communication channel using the server’s digital certificate and authenticates the user with a password within the encrypted channel. this is defined in rfc5281. peap authentication method (protected eap) the operating principle is the same as eap-ttls (there is only a difference in the protocol in the encrypted tunnel). a tls communication channel is established using the server’s digital certificate, and the user is authenticated with a password in the encrypted communication channel. it is trusted a certificate indicating that the public key belongs to the issuer has been issued by a trusted third party. radius server the host device that provides the radius server function, in this case, this device. authenticates connected users via a radius server and manages authentication/authorization information such as user ids, passwords, mac addresses, and associated vlans. server certificate a certificate to state that the certificate authority (ca) has proved that the radius server is trusted. radius client also called a nas or an authenticator, it relays between the user connected to the lan/sfp port and the authentication server, and controls access to the lan based on the success or failure of authentication. user a device that connects to a radius client and requests authentication, or a supplicant that is software. it is the minimum unit for identifying the person to be authenticated. there are data required for authentication and authorization, such as a unique user id and password. client certificate (user certificate) this certificate proves that the user described above is trusted by the certificate authority (ca).</div><div class="display_word">2. Definition of Terms Used PKI (Public Key Infrastructure) Public key infrastructure. Includes digital certificates and certificate authorities (CAs) using public key cryptography. Certificate authority (CA) An organization that guarantees reliability. It is divided into a root Certificate Authority and an intermediate Certificate Authority. It has a tree structure with the root Certificate Authority at the top and an intermediate Certificate Authority under it. Intermediate certificate authority Among Certificate Authorities (CAs), indicates a Certificate Authority whose reliability is guaranteed by a higher-level Certificate Authority (CA). Root certificate authority Among Certificate Authorities (CA), indicates a Certificate Authority whose reliability is guaranteed by itself. Root certificate authority certificate A public key certificate that has the same issuer and subject and has signed its own public key with its own private key. It is the root of a tree-structured certificate. Digital certificate Data that certifies that the public key issued by the Certificate Authority is the genuine issuer’s public key. When the issuer makes a certificate request to the Certificate Authority (CA) together with the public key, the Certificate Authority (CA) issues a digital certificate after scrutinizing and confirming it. EAP-MD5 authentication method (Message digest algorithm 5) This is an authentication method that uses a user name and password. Authenticates by exchanging an MD5 hash value instead of a plain text password. EAP-TLS authentication method (Transport Layer Security) An authentication method used in IEEE 802.1X, a type of EAP implementation that authenticates by exchanging digital certificates after encrypting the transport layer between the user and the RADIUS server, instead of authenticating with a user ID and password. This is defined in RFC2716 and RFC5216. EAP-TTLS authentication method (Tunneled TLS) An authentication method used in IEEE 802.1X, a type of EAP implementation that establishes a TLS communication channel using the server’s digital certificate and authenticates the user with a password within the encrypted channel. This is defined in RFC5281. PEAP authentication method (Protected EAP) The operating principle is the same as EAP-TTLS (there is only a difference in the protocol in the encrypted tunnel). A TLS communication channel is established using the server’s digital certificate, and the user is authenticated with a password in the encrypted communication channel. It is trusted A certificate indicating that the public key belongs to the issuer has been issued by a trusted third party. RADIUS server The host device that provides the RADIUS server function, in this case, this device. Authenticates connected users via a RADIUS server and manages authentication/authorization information such as user IDs, passwords, MAC addresses, and associated VLANs. Server certificate A certificate to state that the Certificate Authority (CA) has proved that the RADIUS server is trusted. RADIUS client Also called a NAS or an authenticator, it relays between the user connected to the LAN/SFP port and the authentication server, and controls access to the LAN based on the success or failure of authentication. User A device that connects to a RADIUS client and requests authentication, or a supplicant that is software. It is the minimum unit for identifying the person to be authenticated. There are data required for authentication and authorization, such as a unique user ID and password. Client certificate (user certificate) This certificate proves that the user described above is trusted by the Certificate Authority (CA).</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#ルート認証局">3.1. Root certificate authority</div><div class="search_word">3.1. root certificate authority to use the radius server function, you must first create a root certificate authority. the root certificate authority is used for issuing and managing digital certificates. it can be created with the crypto pki generate ca command. the certificate authority name can be specified in the crypto pki generate ca command argument, if omitted it becomes swx-radius . the following certificates are issued and managed based on the root certificate authority. all certificates have a key strength of 2048 bits and a signature algorithm of sha256. root certificate authority certificate proves that this device is a trusted root certificate authority. issued at the same time that the root certificate authority is created. the expiration date applies from 23:59:59 (jst) on december 31, 2037 from the date of certificate creation. server certificate proves that this device is a trusted server. issued at the same time that the root certificate authority is created. the expiration date applies from 23:59:59 (jst) on december 31, 2037 from the date of certificate creation. client (user) certificate proves that the user is trusted. client revocation certificate proves that the client certificate has been revoked. the root certificate authority is deleted or overwritten by the following operations. it is deleted when the cold start command is executed. it is deleted when the no crypto pki generate ca command is executed. it is deleted when the stack enable command is executed. it is deleted when the stack disable command is executed. it is deleted when the erase startup-config command is executed. it is overwritten when the crypto pki generate ca command is executed again. it is overwritten when the restore system command is executed. it is overwritten when the copy radius-server local command is executed. [red]#it is necessary to keep the root certificate authority installed first consistent, so be careful not to delete it carelessly. # also, please take measures to back up the file in advance, in case it is deleted. once the root ca is deleted, even if the same ca name is set, it will be a different ca from before. if you delete the root certificate authority before backup, you cannot add or revoke the certificate after that. you will have to reissue all the certificates from the beginning. when the root certificate authority is created by the crypto pki generate ca command, it is automatically saved in the internal area, so there is no need to execute the write command.</div><div class="display_word">3.1. Root certificate authority To use the RADIUS server function, you must first create a root Certificate Authority. The root certificate authority is used for issuing and managing digital certificates. It can be created with the crypto pki generate ca command. The certificate authority name can be specified in the crypto pki generate ca command argument, if omitted it becomes swx-radius . The following certificates are issued and managed based on the root Certificate Authority. All certificates have a key strength of 2048 bits and a signature algorithm of SHA256. Root Certificate Authority certificate Proves that this device is a trusted root Certificate Authority. Issued at the same time that the root Certificate Authority is created. The expiration date applies from 23:59:59 (JST) on December 31, 2037 from the date of certificate creation. Server certificate Proves that this device is a trusted server. Issued at the same time that the root Certificate Authority is created. The expiration date applies from 23:59:59 (JST) on December 31, 2037 from the date of certificate creation. Client (user) certificate Proves that the user is trusted. Client revocation certificate Proves that the client certificate has been revoked. The root Certificate Authority is deleted or overwritten by the following operations. It is deleted when the cold start command is executed. It is deleted when the no crypto pki generate ca command is executed. It is deleted when the stack enable command is executed. It is deleted when the stack disable command is executed. It is deleted when the erase startup-config command is executed. It is overwritten when the crypto pki generate ca command is executed again. It is overwritten when the restore system command is executed. It is overwritten when the copy radius-server local command is executed. [red]#It is necessary to keep the root certificate authority installed first consistent, so be careful not to delete it carelessly. # Also, please take measures to back up the file in advance, in case it is deleted. Once the root CA is deleted, even if the same CA name is set, it will be a different CA from before. If you delete the root Certificate Authority before backup, you cannot add or revoke the certificate after that. You will have to reissue all the certificates from the beginning. When the root certificate authority is created by the crypto pki generate ca command, it is automatically saved in the internal area, so there is no need to execute the write command.</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#radiusクライアントの設定">3.2. RADIUS client settings</div><div class="search_word">3.2. radius client settings use the nas command to specify the radius clients that are permitted to access the radius server. you can specify an individual ip address or network address, and up to 100 addresses can be set. radius client operations are verified using the following products. yamaha network switch (swx series) yamaha router (rtx series or nvr series) yamaha wireless access point (wlx series) the settings of the radius client set by the nas command are not displayed in the config by show running-config . there is no need to execute the write command because it is automatically saved in a different area from the config, but it is necessary to execute the radius-server local refresh command to reflect it in the actual operation. use the show radius-server local nas command to confirm the settings.</div><div class="display_word">3.2. RADIUS client settings Use the nas command to specify the RADIUS clients that are permitted to access the RADIUS server. You can specify an individual IP address or network address, and up to 100 addresses can be set. RADIUS client operations are verified using the following products. Yamaha network switch (SWX series) Yamaha router (RTX series or NVR series) Yamaha wireless access point (WLX series) The settings of the RADIUS client set by the nas command are not displayed in the config by show running-config . There is no need to execute the write command because it is automatically saved in a different area from the config, but it is necessary to execute the radius-server local refresh command to reflect it in the actual operation. Use the show radius-server local nas command to confirm the settings.</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#ユーザーの登録">3.3. User registration</div><div class="search_word">3.3. user registration user information for authentication is registered with the user command. up to 2000 records of user information can be registered. items that can be set with the user command are as follows. type item summary/remarks mandatory user id id for uniquely identifying user information password password used in combination with user id if the client certificate is compressed, use this password for decompression. option user name any character string can be set for user identification. mac address compared when the radius client notifies the calling-station-id, and if it does not match, it is not authenticated. ssid compared when the radius client notifies the called-station-id, and if it does not match, it is not authenticated. mail address this is the address for sending the certificate by mail. authentication method the default is eap-tls, so you must specify it if you want to use another authentication method. period of certificate validity this is valid only when the authentication method is eap-tls. if omitted, it will be 23:59:59 on december 31, 2037. the user settings set by the user command are not displayed in the config by show running-config , etc. there is no need to execute the write command because it is automatically saved in a different area from the config, but it is necessary to execute the radius-server local refresh command to reflect it in the actual operation. use the show radius-server local user command to confirm the settings.</div><div class="display_word">3.3. User registration User information for authentication is registered with the user command. Up to 2000 records of user information can be registered. Items that can be set with the user command are as follows. Type Item Summary/Remarks Mandatory User ID ID for uniquely identifying user information Password Password used in combination with user ID If the client certificate is compressed, use this password for decompression. Option User name Any character string can be set for user identification. MAC address Compared when the RADIUS client notifies the Calling-Station-Id, and if it does not match, it is not authenticated. SSID Compared when the RADIUS client notifies the Called-Station-Id, and if it does not match, it is not authenticated. Mail address This is the address for sending the certificate by mail. Authentication method The default is EAP-TLS, so you must specify it if you want to use another authentication method. Period of certificate validity This is valid only when the authentication method is EAP-TLS. If omitted, it will be 23:59:59 on December 31, 2037. The user settings set by the user command are not displayed in the config by show running-config , etc. There is no need to execute the write command because it is automatically saved in a different area from the config, but it is necessary to execute the radius-server local refresh command to reflect it in the actual operation. Use the show radius-server local user command to confirm the settings.</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#認証方式の制限">3.4. Restricting the authentication method</div><div class="search_word">3.4. restricting the authentication method the authentication method can be restricted by the authentication command. the authentication method is not restricted by default, but you can use it when you want to temporarily disable a specific authentication method.</div><div class="display_word">3.4. Restricting the authentication method The authentication method can be restricted by the authentication command. The authentication method is not restricted by default, but you can use it when you want to temporarily disable a specific authentication method.</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#radiusサーバー機能の有効化">3.5. Enabling the RADIUS server function</div><div class="search_word">3.5. enabling the radius server function to enable the radius server function, use the radius-server local enable command. set the radius client and user information, and enable the radius server function after the necessary preparations are completed.</div><div class="display_word">3.5. Enabling the RADIUS server function To enable the RADIUS server function, use the radius-server local enable command. Set the RADIUS client and user information, and enable the RADIUS server function after the necessary preparations are completed.</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#設定内容の動作への反映">3.6. Reflecting settings in operation</div><div class="search_word">3.6. reflecting settings in operation if you add/change/delete the settings related to the radius server, execute the radius-server local refresh command to reflect them in actual operation. the commands reflected in the actual operation by the radius-server local refresh command are as follows. authentication command nas command reauth interval command user command when you add/change/delete settings related to the radius server in web gui, processing equivalent to the radius-server local refresh command is automatically performed.</div><div class="display_word">3.6. Reflecting settings in operation If you add/change/delete the settings related to the RADIUS server, execute the radius-server local refresh command to reflect them in actual operation. The commands reflected in the actual operation by the radius-server local refresh command are as follows. authentication command nas command reauth interval command user command When you add/change/delete settings related to the RADIUS server in Web GUI, processing equivalent to the radius-server local refresh command is automatically performed.</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#クライアント証明書の発行">3.7. Issue client certificate</div><div class="search_word">3.7. issue client certificate use the certificate user command to issue a client certificate to a user who performs authentication using a certificate (a user whose authentication method is eap-tls with the user command). each user can hold up to two client certificates, and issuing a third client certificate will cause the older client certificate to expire. if you specify an individual user id with the certificate user command, a client certificate for the specified user is issued. if you do not specify individual user ids in the certificate user command, client certificates are issued for all users that meet any of the following conditions. conditions for batch issuance of client certificates client certificate has never been issued the password or expiration date has changed since the client certificate was issued it takes about 15 seconds to issue a client certificate. although the certificate user command issues client certificates in the background, be aware that batch issuing client certificates for multiple users can be time consuming. to cancel the issuance of a client certificate partway through, use the certificate abort command. the method to export an issued client certificate is as follows. specify the mail option in the certificate user command the client certificate can be sent to the specified mail address at the same time that the client certificate is issued. the client certificate is zip compressed and can be decompressed with the password of the user command. for details on sending a client certificate by mail, refer to sending a certificate by mail . certificate export sd command you can copy the client certificate of any user or all users to a microsd card to export it. if a client certificate of any user is compressed and exported by the compress option, it can be decompressed with the password of the user command. if the client certificate for all users is compressed and exported together using the compress option, it can be decompressed without a password. certificate export mail command the client certificate of any user or all users can be sent to the mail address set by the user command. the client certificate is zip compressed and can be decompressed with the password of the user command. access the device with web gui the client certificate can be downloaded for any or all users. although it is zip compressed, no password is required for decompression.</div><div class="display_word">3.7. Issue client certificate Use the certificate user command to issue a client certificate to a user who performs authentication using a certificate (a user whose authentication method is EAP-TLS with the user command). Each user can hold up to two client certificates, and issuing a third client certificate will cause the older client certificate to expire. If you specify an individual user ID with the certificate user command, a client certificate for the specified user is issued. If you do not specify individual user IDs in the certificate user command, client certificates are issued for all users that meet any of the following conditions. Conditions for batch issuance of client certificates Client certificate has never been issued The password or expiration date has changed since the client certificate was issued It takes about 15 seconds to issue a client certificate. Although the certificate user command issues client certificates in the background, be aware that batch issuing client certificates for multiple users can be time consuming. To cancel the issuance of a client certificate partway through, use the certificate abort command. The method to export an issued client certificate is as follows. Specify the mail option in the certificate user command The client certificate can be sent to the specified mail address at the same time that the client certificate is issued. The client certificate is ZIP compressed and can be decompressed with the password of the user command. For details on sending a client certificate by mail, refer to Sending a certificate by mail . certificate export sd command You can copy the client certificate of any user or all users to a microSD card to export it. If a client certificate of any user is compressed and exported by the compress option, it can be decompressed with the password of the user command. If the client certificate for all users is compressed and exported together using the compress option, it can be decompressed without a password. certificate export mail command The client certificate of any user or all users can be sent to the mail address set by the user command. The client certificate is ZIP compressed and can be decompressed with the password of the user command. Access the device with Web GUI The client certificate can be downloaded for any or all users. Although it is ZIP compressed, no password is required for decompression.</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#クライアント証明書の失効">3.8. Revoking a client certificate</div><div class="search_word">3.8. revoking a client certificate to prevent authentication for the user who issued the client certificate, you must issue a revocation certificate. when a revocation certificate is issued to any user, the revocation certificate is referenced in the authentication process and reflected in the authentication result. revocation certificates are issued by the following process. execute the certificate revoke id command a revocation certificate is issued for the client certificate with the specified certificate id. execute the certificate revoke user command revocation certificates are issued for all client certificates of the specified user. change the authentication method from eap-tls to other (pap, peap, eap-md5, eap-ttls) with the user command revocation certificates are issued for all client certificates of the target user. if you change the authentication method of the target user to eap-tls again, it will be subject to the issue of client certificates . deletion of user command revocation certificates are issued for all client certificates of the target user. if you register a user again with the same user id as the target user, it will be subject to the issue of client certificates . issue a third client certificate with the certificate user command a revocation certificate is issued for the target user’s older client certificate. importing user information according to importing and exporting user information if a user is deleted due to an import, a revocation certificate is issued for all client certificates of the deleted user.</div><div class="display_word">3.8. Revoking a client certificate To prevent authentication for the user who issued the client certificate, you must issue a revocation certificate. When a revocation certificate is issued to any user, the revocation certificate is referenced in the authentication process and reflected in the authentication result. Revocation certificates are issued by the following process. Execute the certificate revoke id command A revocation certificate is issued for the client certificate with the specified certificate ID. Execute the certificate revoke user command Revocation certificates are issued for all client certificates of the specified user. Change the authentication method from EAP-TLS to other (PAP, PEAP, EAP-MD5, EAP-TTLS) with the user command Revocation certificates are issued for all client certificates of the target user. If you change the authentication method of the target user to EAP-TLS again, it will be subject to the issue of client certificates . Deletion of user command Revocation certificates are issued for all client certificates of the target user. If you register a user again with the same user ID as the target user, it will be subject to the issue of client certificates . Issue a third client certificate with the certificate user command A revocation certificate is issued for the target user’s older client certificate. Importing user information according to Importing and exporting user information If a user is deleted due to an import, a revocation certificate is issued for all client certificates of the deleted user.</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#証明書のメール送信">3.9. Sending a certificate by mail</div><div class="search_word">3.9. sending a certificate by mail to use the client certificate mail transmission described in issuing a client certificate , the following preparations are required in advance. the settings described here are the minimum settings. make the necessary settings according to the usage. set smtp server specify the smtp server with the mail server smtp host command. specify the mail template specify the template id with the mail template command and switch to the template setting mode. specify the mail server id of the smtp server set by the mail server smtp host command with the send server command. specify the sender mail address with the send from command. specify the mail template to use for sending certificate mails specify the id of the mail template created above with the mail send certificate command. the subject and body of the mail are as follows. the format cannot be changed. subject certification publishment body certification is published.name             : [*name parameter of the user command]account          : [*userid parameter of the user command]mac address      : xx:xx:xx:xx:xx:xxexpire           : yyyy/mm/dd</div><div class="display_word">3.9. Sending a certificate by mail To use the client certificate mail transmission described in Issuing a client certificate , the following preparations are required in advance. The settings described here are the minimum settings. Make the necessary settings according to the usage. Set SMTP server Specify the SMTP server with the mail server smtp host command. Specify the mail template Specify the template ID with the mail template command and switch to the template setting mode. Specify the mail server ID of the SMTP server set by the mail server smtp host command with the send server command. Specify the sender mail address with the send from command. Specify the mail template to use for sending certificate mails Specify the ID of the mail template created above with the mail send certificate command. The subject and body of the mail are as follows. The format cannot be changed. Subject Certification Publishment Body Certification is published.Name             : [*NAME parameter of the user command]Account          : [*USERID parameter of the user command]MAC address      : XX:XX:XX:XX:XX:XXExpire           : YYYY/MM/DD</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#設定および証明書の確認">3.10. Checking settings and certificates</div><div class="search_word">3.10. checking settings and certificates checking the radius client settings use the show radius-server local nas command. yamaha# show radius-server local nas 192.168.100.0/24host                                    key--------------------------------------------------------------------------------------------------------192.168.100.0/24                        abcde checking the user settings use the show radius-server local user command. yamaha# show radius-server local usertotal     1userid                           name                             vlan mode--------------------------------------------------------------------------------00a0de000000                     yamaha                              1 eap-md5 yamaha# show radius-server local user detail 00a0de000000total     1userid      : 00a0de000000password    : secretpasswordmode        : eap-md5name        : yamahavlan        :    1 checking the status of client certificate issuance processing use the show radius-server local certificate status command. yamaha# show radius-server local certificate statuscertificate process: xxxx/ zzzz processing... checking the list of client certificates use the show radius-server local certificate list command. yamaha# show radius-server local certificate list detail tarouserid                           certificate number                                enddate---------------------------------------------------------------------------------------------yamaha                           yamaha-df598ee9b44d22cc                           2018/12/31                                 yamaha-df598ee9b44d22cd                           2019/12/31 checking the revocation certificate use the show radius-server local certificate revoke command. yamaha# show radius-server local certificate revokeuserid                           certificate number                                reason---------------------------------------------------------------------------------------------yamaha                           yamaha-df598ee9b44d22cc                           expiredyamaha                           yamaha-df598ee9b44d22cd                           revoked</div><div class="display_word">3.10. Checking settings and certificates Checking the RADIUS client settings Use the show radius-server local nas command. Yamaha# show radius-server local nas 192.168.100.0/24host                                    key--------------------------------------------------------------------------------------------------------192.168.100.0/24                        abcde Checking the user settings Use the show radius-server local user command. Yamaha# show radius-server local userTotal     1userid                           name                             vlan mode--------------------------------------------------------------------------------00a0de000000                     Yamaha                              1 eap-md5 Yamaha# show radius-server local user detail 00a0de000000Total     1userid      : 00a0de000000password    : secretpasswordmode        : eap-md5name        : Yamahavlan        :    1 Checking the status of client certificate issuance processing Use the show radius-server local certificate status command. Yamaha# show radius-server local certificate statuscertificate process: xxxx/ zzzz processing... Checking the list of client certificates Use the show radius-server local certificate list command. Yamaha# show radius-server local certificate list detail Tarouserid                           certificate number                                enddate---------------------------------------------------------------------------------------------Yamaha                           Yamaha-DF598EE9B44D22CC                           2018/12/31                                 Yamaha-DF598EE9B44D22CD                           2019/12/31 Checking the revocation certificate Use the show radius-server local certificate revoke command. Yamaha# show radius-server local certificate revokeuserid                           certificate number                                reason---------------------------------------------------------------------------------------------Yamaha                           Yamaha-DF598EE9B44D22CC                           expiredYamaha                           Yamaha-DF598EE9B44D22CD                           revoked</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#クライアント証明書の期限切れ事前メール通知">3.11. Mail notification of expiration of client certificate</div><div class="search_word">3.11. mail notification of expiration of client certificate a mail notification can be sent before the client certificate expires. the following preparations are required in advance to use advance mail notification. the settings described here are the minimum settings. make the necessary settings according to the usage. set smtp server specify the smtp server with the mail server smtp host command. specify the mail template specify the template id with the mail template command and switch to the template setting mode. specify the mail server id of the smtp server set by the mail server smtp host command with the send server command. specify the sender mail address with the send from command. specify the mail template to use for the certificate expiration advance mail notification specify the id of the mail template created above with the mail send certificate-notify command. specify when to send a certificate expiration advance mail notification specify the number of days before the expiration date to send the mail notification with the mail certificate expire-notify command. confirmation of the certificates that are subject to the client certificate expiration advance mail notification is performed every day at 23:59:59 . the subject and body of the mail are as follows. the format cannot be changed. subject certification expiration body your certificate will expire in [残り日数] days.name             : [*name parameter of the user command]account          : [*userid parameter of the user command]mac address      : xx:xx:xx:xx:xx:xxexpire           : yyyy/mm/dd</div><div class="display_word">3.11. Mail notification of expiration of client certificate A mail notification can be sent before the client certificate expires. The following preparations are required in advance to use advance mail notification. The settings described here are the minimum settings. Make the necessary settings according to the usage. Set SMTP server Specify the SMTP server with the mail server smtp host command. Specify the mail template Specify the template ID with the mail template command and switch to the template setting mode. Specify the mail server ID of the SMTP server set by the mail server smtp host command with the send server command. Specify the sender mail address with the send from command. Specify the mail template to use for the certificate expiration advance mail notification Specify the ID of the mail template created above with the mail send certificate-notify command. Specify when to send a certificate expiration advance mail notification Specify the number of days before the expiration date to send the mail notification with the mail certificate expire-notify command. Confirmation of the certificates that are subject to the client certificate expiration advance mail notification is performed every day at 23:59:59 . The subject and body of the mail are as follows. The format cannot be changed. Subject Certification expiration Body Your certificate will expire in [残り日数] days.Name             : [*NAME parameter of the user command]Account          : [*USERID parameter of the user command]MAC address      : XX:XX:XX:XX:XX:XXExpire           : YYYY/MM/DD</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#ユーザー情報のインポートとエクスポート">3.12. Importing and exporting user information</div><div class="search_word">3.12. importing and exporting user information exporting user information can be exported from the web gui as a csv file. users can be registered collectively by appending them to the exported csv format file. user information exported by this device cannot be imported using a yamaha wireless access point (wlx series). importing user information can be imported from the web gui. when importing user information, client certificates being issued due to the import can be issued at one time as a batch. when importing information for a large number of users, it may take time before the information is reflected in actual operations. user information exported by a yamaha wireless access point (wlx series) can be imported to this device. however, user information cannot be imported if it includes characters that cannot be used in the unit. in that case, add each user separately. for details about characters not allowed by the unit, refer to points of caution .</div><div class="display_word">3.12. Importing and exporting user information Exporting User information can be exported from the web GUI as a CSV file. Users can be registered collectively by appending them to the exported CSV format file. User information exported by this device cannot be imported using a Yamaha wireless access point (WLX series). Importing User information can be imported from the web GUI. When importing user information, client certificates being issued due to the import can be issued at one time as a batch. When importing information for a large number of users, it may take time before the information is reflected in actual operations. User information exported by a Yamaha wireless access point (WLX series) can be imported to this device. However, user information cannot be imported if it includes characters that cannot be used in the unit. In that case, add each user separately. For details about characters not allowed by the unit, refer to Points of Caution .</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#すべてのradiusサーバー関連情報のバックアップとリストア">3.13. Backing up and restoring all RADIUS server related information</div><div class="search_word">3.13. backing up and restoring all radius server related information this device can back up and restore all radius server related information including the root certificate authority. backup by specifying the microsd card as the export destination with the copy radius-server local command, all the radius server related information can be backed up to the microsd card. the same backup can be performed from the web gui. we recommend that you make a backup in case of device failure. the backup file contains the setting information of the following three commands, but does not include the setting information related to other radius server functions. therefore, it is recommended that you back up configuration files along with backup files. crypto pki generate ca command user command nas command not all radius server-related information backed up by this device can be restored using a yamaha wireless access point (wlx series). restoration by specifying the internal config number as the export destination with the copy radius-server local command, the data backed up above can be restored from the microsd card. in addition, the same restoration can be performed from the web gui, and it is possible to restore data obtained with any model of the swx series. note that if you perform restoration while the root certificate authority has been created, the root certificate authority will be overwritten.</div><div class="display_word">3.13. Backing up and restoring all RADIUS server related information This device can back up and restore all RADIUS server related information including the root Certificate Authority. Backup By specifying the microSD card as the export destination with the copy radius-server local command, all the RADIUS server related information can be backed up to the microSD card. The same backup can be performed from the Web GUI. We recommend that you make a backup in case of device failure. The backup file contains the setting information of the following three commands, but does not include the setting information related to other RADIUS server functions. Therefore, it is recommended that you back up configuration files along with backup files. crypto pki generate ca command user command nas command Not all RADIUS server-related information backed up by this device can be restored using a Yamaha wireless access point (WLX series). Restoration By specifying the internal config number as the export destination with the copy radius-server local command, the data backed up above can be restored from the microSD card. In addition, the same restoration can be performed from the Web GUI, and it is possible to restore data obtained with any model of the SWX series. Note that if you perform restoration while the root Certificate Authority has been created, the root Certificate Authority will be overwritten.</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#ヤマハ無線アクセスポイントwlxシリーズでバックアップしたradiusサーバー関連情報のリストア">3.14. Restoring RADIUS server information backed up by a Yamaha wireless access point (WLX series)</div><div class="search_word">3.14. restoring radius server information backed up by a yamaha wireless access point (wlx series) this unit can be used to restore radius server information backed up by a yamaha wireless access point (wlx series). the information can only be restored via the web gui. radius server functions used to operate a yamaha wireless access point (wlx series) can be transferred to the given unit by executing the following procedure. restore the data backed up by a yamaha wireless access point (wlx series) port in the unit. for the wlx402 model, the backed up data (zip file) can be obtained from the radius server settings page on the web gui. for the wlx313 model, the backed up data (zip file) can be obtained from the settings (save/restore) page on the web gui. use the nas command or web gui to specify the radius client. specify the vlan interface to use for radius authentication by the radius-server local interface command or via the web gui. to send an authentication certificate via mail or send prior mail notification about the certificate expiration date, specify mail settings. enable radius server functions using the radius-server local enable command or the web gui. apply the radius information to actual operations using the radius-server local refresh command. the procedure above eliminates the need to reissue a client certificate and can be used to transfer radius server functions to the unit from a yamaha wireless access point (wlx series). if radius server functions are transferred to the unit from a yamaha wireless access point (wlx series), then the revocation certificate expiration date is automatically updated to 20 years from the date/time the functions are received. the following data backed up via a yamaha wireless access point (wlx series) can be restored. root certificate authority root certificate server certificate client certificate revocation certificate user information radius client settings and other information not indicated above are not restored and must be set separately. users with information that includes characters not allowed by the unit cannot be restored. in that case, add each user separately. for details about characters not allowed by the unit, refer to points of caution . certificate authority names can be restored even if they include characters not allowed by the unit. however, disallowed characters are shown converted to the underscore (_) character in config files.</div><div class="display_word">3.14. Restoring RADIUS server information backed up by a Yamaha wireless access point (WLX series) This unit can be used to restore RADIUS server information backed up by a Yamaha wireless access point (WLX series). The information can only be restored via the Web GUI. RADIUS server functions used to operate a Yamaha wireless access point (WLX series) can be transferred to the given unit by executing the following procedure. Restore the data backed up by a Yamaha wireless access point (WLX series) port in the unit. For the WLX402 model, the backed up data (ZIP file) can be obtained from the RADIUS server settings page on the Web GUI. For the WLX313 model, the backed up data (ZIP file) can be obtained from the settings (save/restore) page on the Web GUI. Use the nas command or Web GUI to specify the RADIUS client. Specify the VLAN interface to use for RADIUS authentication by the radius-server local interface command or via the Web GUI. To send an authentication certificate via mail or send prior mail notification about the certificate expiration date, specify mail settings. Enable RADIUS server functions using the radius-server local enable command or the Web GUI. Apply the RADIUS information to actual operations using the radius-server local refresh command. The procedure above eliminates the need to reissue a client certificate and can be used to transfer RADIUS server functions to the unit from a Yamaha wireless access point (WLX series). If RADIUS server functions are transferred to the unit from a Yamaha wireless access point (WLX series), then the revocation certificate expiration date is automatically updated to 20 years from the date/time the functions are received. The following data backed up via a Yamaha wireless access point (WLX series) can be restored. Root certificate authority Root certificate Server certificate Client certificate Revocation certificate User information RADIUS client settings and other information not indicated above are not restored and must be set separately. Users with information that includes characters not allowed by the unit cannot be restored. In that case, add each user separately. For details about characters not allowed by the unit, refer to Points of Caution . Certificate Authority names can be restored even if they include characters not allowed by the unit. However, disallowed characters are shown converted to the underscore (_) character in config files.</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#syslogの出力情報">3.15. SYSLOG output information</div><div class="search_word">3.15. syslog output information the following information is output to the syslog as a radius server function. the prefix is [radiusd] . type message description info radius server started. the radius server function process has started. info radius server stopped. the radius server function process has stopped. info authentication succeeded.: [{ user id }/<via auth-type = { authentication method }>] (from client port { port number } cli { mac address }) user authentication succeeded. info authentication failed.: [{ user id }/<via auth-type = { authentication method }>] (from client port { port number } cli { mac address }) user authentication failed. info mac address is not allowed.user-id:{ user id } mac:{ mac address } user authentication failed because the mac address is incorrect. info connected nas is not allowed.ip:{ ip address } an authentication request was received from an unauthorized radius client.</div><div class="display_word">3.15. SYSLOG output information The following information is output to the SYSLOG as a RADIUS server function. The prefix is [RADIUSD] . Type Message Description INFO RADIUS server started. The RADIUS server function process has started. INFO RADIUS server stopped. The RADIUS server function process has stopped. INFO Authentication succeeded.: [{ User ID }/<via Auth-Type = { Authentication method }>] (from client port { Port number } cli { MAC address }) User authentication succeeded. INFO Authentication failed.: [{ User ID }/<via Auth-Type = { Authentication method }>] (from client port { Port number } cli { MAC address }) User authentication failed. INFO MAC address is not allowed.User-ID:{ User ID } MAC:{ MAC address } User authentication failed because the MAC address is incorrect. INFO Connected NAS is not allowed.IP:{ IP address } An authentication request was received from an unauthorized RADIUS client.</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands radius-server local enable setting of local radius server function radius-server local interface access interface settings crypto pki generate ca generate root certificate authority radius-server local-profile radius configuration mode authentication authentication method setting nas radius client (nas) settings user authentication user settings reauth interval re-authentication interval settings radius-server local refresh set data reflected on local radius server certificate user issue client certificate certificate abort suspend client certificate issuance certificate revoke id revoke client certificate with the specified certificate id certificate revoke user revoke client certificate for specified user certificate export sd export client certificate (sd copy) certificate export mail export client certificate (mail transmission) copy radius-server local copy radius data show radius-server local nas show radius client (nas) show radius-server local user show authentication user information show radius-server local certificate status show issuance status of client certificate show radius-server local certificate list show list of client certificates show radius-server local certificate revoke show revocation list of client certificates</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands radius-server local enable Setting of local RADIUS server function radius-server local interface Access interface settings crypto pki generate ca Generate root Certificate Authority radius-server local-profile RADIUS configuration mode authentication Authentication method setting nas RADIUS client (NAS) settings user Authentication user settings reauth interval Re-authentication interval settings radius-server local refresh Set data reflected on local RADIUS server certificate user Issue client certificate certificate abort Suspend client certificate issuance certificate revoke id Revoke client certificate with the specified certificate ID certificate revoke user Revoke client certificate for specified user certificate export sd Export client certificate (SD copy) certificate export mail Export client certificate (mail transmission) copy radius-server local Copy RADIUS data show radius-server local nas Show RADIUS client (NAS) show radius-server local user Show authentication user information show radius-server local certificate status Show issuance status of client certificate show radius-server local certificate list Show list of client certificates show radius-server local certificate revoke Show revocation list of client certificates</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#設定例">5. Setting Examples</div><div class="search_word">5. setting examples</div><div class="display_word">5. Setting Examples</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#radiusサーバー機能とポート認証機能を同時に利用する場合">5.1. Using RADIUS server functions and port authentication function simultaneously</div><div class="search_word">5.1. using radius server functions and port authentication function simultaneously use a local radius server to configure supplicants a, b, and c to authenticate with mac, ieee802.1x, and web authentication, respectively. enable the local radius server with the network switch and register the user. yamaha# configure terminalyamaha(config)# crypto pki generate cagenerate ca? (y/n): yfinishedyamaha(config)# radius-server local-profileyamaha(config-radius)# user 00a0de000001 00a0de000001 auth peapyamaha(config-radius)# user 8021xuser 8021xpass auth peapyamaha(config-radius)# user webuser webpass auth peapyamaha(config-radius)# exityamaha(config)# radius-server local enableyamaha(config)# exityamaha# radius-server local refresh assign an ip address to vlan #1 for web authentication yamaha# configure terminalyamaha(config)# interface vlan1yamaha(config-if)# ip-address 192.168.100.240/24 enable mac authentication, ieee802.1x authentication, and web authentication on lan port #1. yamaha# configure terminalyamaha(config)# aaa authentication auth-macyamaha(config)# auth-mac auth-user unformatted lower-caseyamaha(config)# aaa authentication dot1xyamaha(config)# aaa authentication auth-webyamaha(config)# interface port1.1yamaha(config-if)# auth host-mode multi-supplicantyamaha(config-if)# auth-mac enableyamaha(config-if)# dot1x port-control autoyamaha(config-if)# auth-web enable set the radius server used for the authentication function. yamaha# configure terminalyamaha(config)# radius-server host 127.0.0.1 key secret_local</div><div class="display_word">5.1. Using RADIUS server functions and port authentication function simultaneously Use a local RADIUS server to configure supplicants A, B, and C to authenticate with MAC, IEEE802.1X, and Web authentication, respectively. Enable the local RADIUS server with the network switch and register the user. Yamaha# configure terminalYamaha(config)# crypto pki generate caGenerate CA? (y/n): yFinishedYamaha(config)# radius-server local-profileYamaha(config-radius)# user 00a0de000001 00a0de000001 auth peapYamaha(config-radius)# user 8021xuser 8021xpass auth peapYamaha(config-radius)# user webuser webpass auth peapYamaha(config-radius)# exitYamaha(config)# radius-server local enableYamaha(config)# exitYamaha# radius-server local refresh Assign an IP address to VLAN #1 for web authentication Yamaha# configure terminalYamaha(config)# interface vlan1Yamaha(config-if)# ip-address 192.168.100.240/24 Enable MAC authentication, IEEE802.1X authentication, and Web authentication on LAN port #1. Yamaha# configure terminalYamaha(config)# aaa authentication auth-macYamaha(config)# auth-mac auth-user unformatted lower-caseYamaha(config)# aaa authentication dot1xYamaha(config)# aaa authentication auth-webYamaha(config)# interface port1.1Yamaha(config-if)# auth host-mode multi-supplicantYamaha(config-if)# auth-mac enableYamaha(config-if)# dot1x port-control autoYamaha(config-if)# auth-web enable Set the RADIUS server used for the authentication function. Yamaha# configure terminalYamaha(config)# radius-server host 127.0.0.1 key secret_local</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#ヤマハルーターのログインユーザーの認証でradiusサーバー機能を利用する場合">5.2. Using RADIUS server functions for authentication of users logging in to a Yamaha router</div><div class="search_word">5.2. using radius server functions for authentication of users logging in to a yamaha router if accessing a yamaha router from a telnet client, user login authentication and administrator privilege authentication are performed by the yamaha network switch radius server. that enables user login using the user id “ user1 ” and password “ password1 ”. users can be promoted to administrator using the password “ admin ”. ■ yamaha network switch settings specify the ip address in the interface. yamaha# configure terminalyamaha(config)# interface vlan1yamaha(config-if)# ip address 192.168.100.240/24yamaha(config-if)# exit generate a root certificate authority. yamaha(config)#crypto pki generate cagenerate ca? (y/n): yfinished specify the radius servers. yamaha(config)# radius-server local-profileyamaha(config-radius)# nas 192.168.100.1 key yamahayamaha(config-radius)# user user1 password1 auth papyamaha(config-radius)# user *administrator admin auth papyamaha(config-radius)# exit specify interfaces to which radius clients can connect. yamaha(config)# radius-server local interface vlan1 enable radius server functions. yamaha(config)# radius-server local enableyamaha(config)#exit apply radius server settings to actual operations. yamaha#radius-server local refreshyamaha# ■ yamaha router settings login radius use onadministrator radius auth onip lan1 address 192.168.100.1/24radius auth onradius auth server 192.168.100.240radius auth port 1812radius secret yamaha</div><div class="display_word">5.2. Using RADIUS server functions for authentication of users logging in to a Yamaha router If accessing a Yamaha router from a TELNET client, user login authentication and administrator privilege authentication are performed by the Yamaha network switch RADIUS server. That enables user login using the user ID “ user1 ” and password “ password1 ”. Users can be promoted to administrator using the password “ admin ”. ■ Yamaha network switch settings Specify the IP address in the interface. Yamaha# configure terminalYamaha(config)# interface vlan1Yamaha(config-if)# ip address 192.168.100.240/24Yamaha(config-if)# exit Generate a root Certificate Authority. Yamaha(config)#crypto pki generate caGenerate CA? (y/n): yFinished Specify the RADIUS servers. Yamaha(config)# radius-server local-profileYamaha(config-radius)# nas 192.168.100.1 key yamahaYamaha(config-radius)# user user1 password1 auth papYamaha(config-radius)# user *administrator admin auth papYamaha(config-radius)# exit Specify interfaces to which RADIUS clients can connect. Yamaha(config)# radius-server local interface vlan1 Enable RADIUS server functions. Yamaha(config)# radius-server local enableYamaha(config)#exit Apply RADIUS server settings to actual operations. Yamaha#radius-server local refreshYamaha# ■ Yamaha router settings login radius use onadministrator radius auth onip lan1 address 192.168.100.1/24radius auth onradius auth server 192.168.100.240radius auth port 1812radius secret yamaha</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#ヤマハ無線アクセスポイントwlxシリーズのmac認証でradiusサーバー機能を利用する場合">5.3. Using RADIUS server functions for MAC authentication of Yamaha wireless access points (WLX series)</div><div class="search_word">5.3. using radius server functions for mac authentication of yamaha wireless access points (wlx series) the yamaha network switch radius server is used to authenticate the mac address of supplicants connected to a yamaha wireless access point. ■ yamaha network switch settings specify the ip address in the interface. yamaha# configure terminalyamaha(config)# interface vlan2yamaha(config-if)# ip address 192.168.200.240/24yamaha(config-if)# exit generate a root certificate authority. yamaha(config)#crypto pki generate cagenerate ca? (y/n): yfinished specify the radius servers. yamaha(config)# radius-server local-profileyamaha(config-radius)# nas 192.168.200.100 key yamahayamaha(config-radius)# user 00a0de000001 00a0de000001 auth pap ssid wlxyamaha(config-radius)# exit specify interfaces permitted to connect to radius clients. yamaha(config)# radius-server local interface vlan2 enable radius server functions. yamaha(config)# radius-server local enableyamaha(config)#exit apply radius server settings to actual operations. yamaha#radius-server local refreshyamaha# ■ yamaha wireless ap (wlx402) settings note: only for settings related to authentication. configure other settings, such as for wireless functions, separately according to the given environment. ip vlan-id 1 address 192.168.200.100/24airlink slect 1airlink ssid wlxairlink radius auth onairlink radius server 192.168.200.240airlink radius secret yamahaairlink enable 1</div><div class="display_word">5.3. Using RADIUS server functions for MAC authentication of Yamaha wireless access points (WLX series) The Yamaha network switch RADIUS server is used to authenticate the MAC address of supplicants connected to a Yamaha wireless access point. ■ Yamaha network switch settings Specify the IP address in the interface. Yamaha# configure terminalYamaha(config)# interface vlan2Yamaha(config-if)# ip address 192.168.200.240/24Yamaha(config-if)# exit Generate a root Certificate Authority. Yamaha(config)#crypto pki generate caGenerate CA? (y/n): yFinished Specify the RADIUS servers. Yamaha(config)# radius-server local-profileYamaha(config-radius)# nas 192.168.200.100 key yamahaYamaha(config-radius)# user 00a0de000001 00a0de000001 auth pap ssid wlxYamaha(config-radius)# exit Specify interfaces permitted to connect to RADIUS clients. Yamaha(config)# radius-server local interface vlan2 Enable RADIUS server functions. Yamaha(config)# radius-server local enableYamaha(config)#exit Apply RADIUS server settings to actual operations. Yamaha#radius-server local refreshYamaha# ■ Yamaha wireless AP (WLX402) settings Note: Only for settings related to authentication. Configure other settings, such as for wireless functions, separately according to the given environment. ip vlan-id 1 address 192.168.200.100/24airlink slect 1airlink ssid wlxairlink radius auth onairlink radius server 192.168.200.240airlink radius secret yamahaairlink enable 1</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#証明書を使ってヤマハ無線アクセスポイントwlxシリーズに接続するためにradiusサーバー機能を利用する場合">5.4. Using RADIUS server functions to connect to a Yamaha wireless access point (WLX series) using a certificate</div><div class="search_word">5.4. using radius server functions to connect to a yamaha wireless access point (wlx series) using a certificate a supplicant with a certificate issued by the yamaha network switch installed is used to authenticate connections to a yamaha wireless access point. ■ yamaha network switch settings specify the ip address in the interface. yamaha(config)# interface vlan2yamaha(config-if)# ip address 192.168.120.240/24yamaha(config-if)# exit generate a root certificate authority. yamaha(config)#crypto pki generate cagenerate ca? (y/n): yfinished specify the radius servers. yamaha(config)# radius-server local-profileyamaha(config-radius)# nas 192.168.120.100 key yamaha1yamaha(config-radius)# nas 192.168.130.100 key yamaha2yamaha(config-radius)# user user1 pass1 ssid wlxayamaha(config-radius)# user user2 pass2 ssid wlxbyamaha(config-radius)# user user3 pass3 ssid wlxcyamaha(config-radius)# user user4 pass4 ssid wlxdyamaha(config-radius)# exit specify interfaces permitted to connect to radius clients. yamaha(config)# radius-server local interface vlan2yamaha(config)# radius-server local interface vlan3 enable radius server functions. yamaha(config)# radius-server local enableyamaha(config)# exit issue client certificates. install the issued certificates in supplicants a to d, respectively. yamaha# certificate user user1yamaha# certificate user user2yamaha# certificate user user3yamaha# certificate user user4 apply radius server settings to actual operations. yamaha# radius-server local refresh ■ yamaha wireless ap1 (wlx402) settings note: only for settings related to authentication. configure other settings, such as for wireless functions, separately according to the given environment. ip vlan-id 2 address 192.168.120.100/24 airlink select 1  airlink ssid wlxa  airlink vlan-id 2  airlink radius auth on  airlink radius server 192.168.120.240  airlink radius secret yamaha1 airlink enable 1 airlink select 2  airlink ssid wlxb  airlink vlan-id 2  airlink radius auth on  airlink radius server 192.168.120.240  airlink radius secret yamaha1 airlink enable 2 ■ yamaha wireless ap2 (wlx402) settings note: only for settings related to authentication. configure other settings, such as for wireless functions, separately according to the given environment. ip vlan-id 3 address 192.168.130.100/24 airlink select 1  airlink ssid wlxc  airlink vlan-id 3  airlink radius auth on  airlink radius server 192.168.130.240  airlink radius secret yamaha2 airlink enable 1 airlink select 2  airlink ssid wlxd  airlink vlan-id 3  airlink radius auth on  airlink radius server 192.168.130.240  airlink radius secret yamaha2 airlink enable 2</div><div class="display_word">5.4. Using RADIUS server functions to connect to a Yamaha wireless access point (WLX series) using a certificate A supplicant with a certificate issued by the Yamaha network switch installed is used to authenticate connections to a Yamaha wireless access point. ■ Yamaha network switch settings Specify the IP address in the interface. Yamaha(config)# interface vlan2Yamaha(config-if)# ip address 192.168.120.240/24Yamaha(config-if)# exit Generate a root Certificate Authority. Yamaha(config)#crypto pki generate caGenerate CA? (y/n): yFinished Specify the RADIUS servers. Yamaha(config)# radius-server local-profileYamaha(config-radius)# nas 192.168.120.100 key yamaha1Yamaha(config-radius)# nas 192.168.130.100 key yamaha2Yamaha(config-radius)# user user1 pass1 ssid wlxAYamaha(config-radius)# user user2 pass2 ssid wlxBYamaha(config-radius)# user user3 pass3 ssid wlxCYamaha(config-radius)# user user4 pass4 ssid wlxDYamaha(config-radius)# exit Specify interfaces permitted to connect to RADIUS clients. Yamaha(config)# radius-server local interface vlan2Yamaha(config)# radius-server local interface vlan3 Enable RADIUS server functions. Yamaha(config)# radius-server local enableYamaha(config)# exit Issue client certificates. Install the issued certificates in supplicants A to D, respectively. Yamaha# certificate user user1Yamaha# certificate user user2Yamaha# certificate user user3Yamaha# certificate user user4 Apply RADIUS server settings to actual operations. Yamaha# radius-server local refresh ■ Yamaha wireless AP1 (WLX402) settings Note: Only for settings related to authentication. Configure other settings, such as for wireless functions, separately according to the given environment. ip vlan-id 2 address 192.168.120.100/24 airlink select 1  airlink ssid wlxA  airlink vlan-id 2  airlink radius auth on  airlink radius server 192.168.120.240  airlink radius secret yamaha1 airlink enable 1 airlink select 2  airlink ssid wlxB  airlink vlan-id 2  airlink radius auth on  airlink radius server 192.168.120.240  airlink radius secret yamaha1 airlink enable 2 ■ Yamaha wireless AP2 (WLX402) settings Note: Only for settings related to authentication. Configure other settings, such as for wireless functions, separately according to the given environment. ip vlan-id 3 address 192.168.130.100/24 airlink select 1  airlink ssid wlxC  airlink vlan-id 3  airlink radius auth on  airlink radius server 192.168.130.240  airlink radius secret yamaha2 airlink enable 1 airlink select 2  airlink ssid wlxD  airlink vlan-id 3  airlink radius auth on  airlink radius server 192.168.130.240  airlink radius secret yamaha2 airlink enable 2</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution in the radius server function, the time of the internal clock of this device is used for processing such as authentication processing and certificate issuance. therefore, it is necessary to always keep the internal clock of this device at the correct time. time synchronization with ntp server is recommended. it is necessary to keep the root certificate authority consistent from its creation, so be careful not to delete it carelessly. if it is deleted, the issued client certificates cannot be used, and client certificates must be reissued for all users. also, almost all settings related to the radius server function will be deleted. even if you create a root certificate authority with the same name on a yamaha network switch of the same model number, that root certificate authority will be a different one. client certificates can only be used with yamaha network switch authentication that has the root certificate authority used at the time of generation. to maintain the same root certificate authority in multiple devices, see backing up and restoring all radius server related information . authentication cannot be performed even if a radius client connects to an ipv6 link-local address. the characters permitted in user or other information by yamaha network switches is different than permitted by yamaha wireless access points (wlx series). those differences are indicated below. (the characters in red are disallowed only by yamaha network switches) item yamaha network switch restrictions yamaha wireless access point restrictions root certificate authority name (ca-name option for crypto pki generate ca command) the following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘/’ ‘[’ ‘]’ ‘?’ ‘ ’ (space) ‘”’ (double quote) the following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘/’ ‘[’ ‘]’ radius client shared password (secret parameter of nas command) the following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘[’ ‘]’ ‘?’ ‘ ’ (space) ‘”’ (double quote) the following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘[’ ‘]’ user id in user information (userid parameter of user command) when the authentication method is eap-tls the following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘/’ ‘[’ ‘]’ ':' ‘<’ ‘*’ ‘>’ ‘|’ ‘?’ ‘ ’ (space) ‘”’ (double quote) the following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘/’ ‘[’ ‘]’ user id in user information (userid parameter of user command) when the authentication method is pap or peap the following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘[’ ‘]’ ‘?’ ‘ ’ (space) ‘”’ (double quote) the following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘[’ ‘]’ password in user information (password parameter of user command) the following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘[’ ‘]’ ‘?’ ‘ ’ (space) ‘”’ (double quote) the following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘[’ ‘]’ name in user information (name option of user command) the following single-byte alphanumeric characters and symbols cannot be used. ‘?’ ‘ ’ (space) ‘”’ (double quote) all single-byte alphanumeric characters and symbols can be used.</div><div class="display_word">6. Points of Caution In the RADIUS server function, the time of the internal clock of this device is used for processing such as authentication processing and certificate issuance. Therefore, it is necessary to always keep the internal clock of this device at the correct time. Time synchronization with NTP server is recommended. It is necessary to keep the root Certificate Authority consistent from its creation, so be careful not to delete it carelessly. If it is deleted, the issued client certificates cannot be used, and client certificates must be reissued for all users. Also, almost all settings related to the RADIUS server function will be deleted. Even if you create a root Certificate Authority with the same name on a Yamaha network switch of the same model number, that root Certificate Authority will be a different one. Client certificates can only be used with Yamaha network switch authentication that has the root Certificate Authority used at the time of generation. To maintain the same root Certificate Authority in multiple devices, see Backing up and restoring all RADIUS server related information . Authentication cannot be performed even if a RADIUS client connects to an IPv6 link-local address. The characters permitted in user or other information by Yamaha network switches is different than permitted by Yamaha wireless access points (WLX series). Those differences are indicated below. (The characters in red are disallowed only by Yamaha network switches) Item Yamaha network switch restrictions Yamaha wireless access point restrictions Root certificate authority name (CA-NAME option for crypto pki generate ca command) The following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘/’ ‘[’ ‘]’ ‘?’ ‘ ’ (space) ‘”’ (double quote) The following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘/’ ‘[’ ‘]’ RADIUS client shared password (SECRET parameter of nas command) The following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘[’ ‘]’ ‘?’ ‘ ’ (space) ‘”’ (double quote) The following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘[’ ‘]’ User ID in user information (USERID parameter of user command) When the authentication method is EAP-TLS The following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘/’ ‘[’ ‘]’ ':' ‘<’ ‘*’ ‘>’ ‘|’ ‘?’ ‘ ’ (space) ‘”’ (double quote) The following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘/’ ‘[’ ‘]’ User ID in user information (USERID parameter of user command) When the authentication method is PAP or PEAP The following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘[’ ‘]’ ‘?’ ‘ ’ (space) ‘”’ (double quote) The following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘[’ ‘]’ Password in user information (PASSWORD parameter of user command) The following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘[’ ‘]’ ‘?’ ‘ ’ (space) ‘”’ (double quote) The following single-byte alphanumeric characters and symbols cannot be used. ‘\’ (backslash) ‘[’ ‘]’ Name in user information (NAME option of user command) The following single-byte alphanumeric characters and symbols cannot be used. ‘?’ ‘ ’ (space) ‘”’ (double quote) All single-byte alphanumeric characters and symbols can be used.</div></div><div id="ap_ap_radius_server"><div class="search_title" docfname="ap_ap_radius_server" doctitle="RADIUS" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation interface control functions: port authentication</div><div class="display_word">7. Related Documentation Interface Control Functions: Port Authentication</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#インターフェース基本機能">Basic Interface Functions</div><div class="search_word">basic interface functions</div><div class="display_word">Basic Interface Functions</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview here we explain the basic interface functions of this product.</div><div class="display_word">1. Function Overview Here we explain the basic interface functions of this product.</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used combo port there are two types of ports to choose from: lan port and sfp port. the lan port and sfp port cannot be used at the same time. if both ports are connected, the sfp port has priority. if there is a valid setting for only the lan port, it will not be applied to the sfp port.</div><div class="display_word">2. Definition of Terms Used Combo port There are two types of ports to choose from: LAN port and SFP port. The LAN port and SFP port cannot be used at the same time. If both ports are connected, the SFP port has priority. If there is a valid setting for only the LAN port, it will not be applied to the SFP port.</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#インターフェースの種類">3.1. Interface types</div><div class="search_word">3.1. interface types this product can handle the five interface types shown in the table below. interface types interface id explanation lan port port this is a physical port of this product. there are three types: a fixed lan port and a removable sfp/sfp+ port. this interface is expressed as port followed by “stack id” + “.” + “port number printed on the chassis.” specifying lan port #1: port1.1 combo port sfp+ port vlan interface vlan this is a user-defined vlan. this interface is expressed as vlan followed by “vlan id”. specifying vlan1: vlan1 static logical interface sa this is the user-defined link aggregation. multiple lan/sfp ports can be grouped together and used as one interface. this interface is expressed as “ sa ” or “ po ,” followed by “logical link id.” specifying the lacp logical interface for logical link id #1: po1 lacp logical interface po</div><div class="display_word">3.1. Interface types This product can handle the five interface types shown in the table below. Interface types Interface ID Explanation LAN port port This is a physical port of this product. There are three types: a fixed LAN port and a removable SFP/SFP+ port. This interface is expressed as port followed by “stack ID” + “.” + “port number printed on the chassis.” Specifying LAN port #1: port1.1 Combo port SFP+ port VLAN interface vlan This is a User-defined VLAN. This interface is expressed as vlan followed by “VLAN ID”. Specifying VLAN1: vlan1 Static logical interface sa This is the User-defined link aggregation. Multiple LAN/SFP ports can be grouped together and used as one interface. This interface is expressed as “ sa ” or “ po ,” followed by “logical link ID.” Specifying the LACP logical interface for logical link ID #1: po1 LACP logical interface po</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#インターフェース制御">3.2. Interface control</div><div class="search_word">3.2. interface control the interface on this product can be controlled as shown in the table below. interface control items control items commands explanation set description description sets the description text for the applicable interface. enable/disable shutdown enables/disables the interface. communication speed/communication mode speed-duplex sets the communication speed and communication mode for the interface. (select from the following values.) - auto negotiation - 10gbps / full duplex - 1gbps / full duplex - 100mbps / full duplex - 100mbps / half duplex - 10mbps / full duplex - 10mbps / half duplex mru mru sets the maximum frame size that can be received by the interface, within a range of 64–10,240 bytes . cross/straight automatic detection (auto mdi/mdi-x function) mdix automatically detects the port type (mdi or mdi-x) of the connected port and the cable type (cross or straight). this function gives the ability to interconnect without dependency. speed downshift - this function automatically reduces the speed and attempts to link when a lan cable that cannot be used with 1000base-t is connected. this function is always enabled for lan ports. (cannot be disabled.) eee eee sets whether to use the energy saving technology for ethernet (eee: energy efficient ethernet). this is standard for ieee 802.3az. command control of the interface is performed as shown on the table below. interface control functionality chart interface name set description enable/disable communication speed/communication mode mru cross/straight automatic detection eee lan port yes yes yes (*1) yes yes yes combo port yes yes yes (*2) yes yes (*3) yes (*3) sfp+ port yes yes yes (*4) yes no no vlan interface yes no no no no no static logical interface yes yes no no no no lacp logical interface yes yes no no no no 1 : the communication speed/communication mode setting for the lan port cannot be selected as *10gbps / full duplex . 2: the communication speed/mode setting for the combo port is either *auto negotiation or 1gbps / full duplex . 3: the settings for the combo port are applied only to lan ports. *4: the communication speed/communication mode setting for the sfp+ port can be either *auto negotiation or 10gbps / full duplex . if 10gbps / full duplex is set and an sfp module is connected, the module will operate at 1gbps / full duplex .</div><div class="display_word">3.2. Interface control The interface on this product can be controlled as shown in the table below. Interface control items Control items Commands Explanation Set description description Sets the description text for the applicable interface. Enable/disable shutdown Enables/disables the interface. Communication speed/communication mode speed-duplex Sets the communication speed and communication mode for the interface. (Select from the following values.) - Auto negotiation - 10Gbps / Full duplex - 1Gbps / Full duplex - 100Mbps / Full duplex - 100Mbps / Half duplex - 10Mbps / Full duplex - 10Mbps / Half duplex MRU mru Sets the maximum frame size that can be received by the interface, within a range of 64–10,240 bytes . Cross/straight automatic detection (Auto MDI/MDI-X function) mdix Automatically detects the port type (MDI or MDI-X) of the connected port and the cable type (cross or straight). This function gives the ability to interconnect without dependency. Speed downshift - This function automatically reduces the speed and attempts to link when a LAN cable that cannot be used with 1000BASE-T is connected. This function is always enabled for LAN ports. (Cannot be disabled.) EEE eee Sets whether to use the energy saving technology for Ethernet (EEE: Energy Efficient Ethernet). This is standard for IEEE 802.3az. Command control of the interface is performed as shown on the table below. Interface control functionality chart Interface name Set description Enable/disable Communication speed/communication mode MRU Cross/straight automatic detection EEE LAN port Yes Yes Yes (*1) Yes Yes Yes Combo port Yes Yes Yes (*2) Yes Yes (*3) Yes (*3) SFP+ port Yes Yes Yes (*4) Yes No No VLAN interface Yes No No No No No Static logical interface Yes Yes No No No No LACP logical interface Yes Yes No No No No 1 : The communication speed/communication mode setting for the LAN port cannot be selected as *10Gbps / Full duplex . 2: The communication speed/mode setting for the combo port is either *auto negotiation or 1Gbps / Full duplex . 3: The settings for the combo port are applied only to LAN ports. *4: The communication speed/communication mode setting for the SFP+ port can be either *auto negotiation or 10Gbps / Full duplex . If 10Gbps / Full duplex is set and an SFP module is connected, the module will operate at 1Gbps / Full duplex .</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#lansfpポートの初期状態">3.3. LAN/SFP port defaults</div><div class="search_word">3.3. lan/sfp port defaults the product lan/sfp ports are in the following state given default settings. all lan/sfp ports function as access ports (ports that handle untagged frames), and belong to the default vlan (vlan #1). the following functions are enabled for the default vlan (vlan #1) to which all lan/sfp ports belong. mstp：multiple spanning tree protocol igmp snooping ipv4 address (192.168.100.240/24) access from a telnet client access from a web client</div><div class="display_word">3.3. LAN/SFP port defaults The product LAN/SFP ports are in the following state given default settings. All LAN/SFP ports function as access ports (ports that handle untagged frames), and belong to the default VLAN (VLAN #1). The following functions are enabled for the default VLAN (VLAN #1) to which all LAN/SFP ports belong. MSTP：Multiple Spanning Tree Protocol IGMP Snooping IPv4 address (192.168.100.240/24) Access from a Telnet client Access from a web client</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#ポートミラーリング">3.4. Port mirroring</div><div class="search_word">3.4. port mirroring this product provides a port mirroring function, which copies the data traffic from a selected lan/sfp port to another specified port. the communication status can be analyzed by collecting the copied packets. the product enables specifying up to one sniffer port. the monitoring direction (send/receive, send only, or receive only) can be selected for monitored ports. the mirror command can be used to set the port mirroring. the port mirroring setting is disabled in default settings.</div><div class="display_word">3.4. Port mirroring This product provides a port mirroring function, which copies the data traffic from a selected LAN/SFP port to another specified port. The communication status can be analyzed by collecting the copied packets. The product enables specifying up to one sniffer port. The monitoring direction (send/receive, send only, or receive only) can be selected for monitored ports. The mirror command can be used to set the port mirroring. The port mirroring setting is disabled in default settings.</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#フレームカウンター">3.5. Frame counter</div><div class="search_word">3.5. frame counter this product counts the number of frames transmitted/received for each lan/sfp port. (this is called a “frame counter”.) to reference the frame counter, use the show frame counter command. the table below shows the display items for the frame counter and their maximum values. received frame counter display items display item explanation maximum value octets number of octets received 18,446,744,073,709,551,615 packets (*1) number of received packets 34,359,738,360 broadcast packets (*2) number of broadcast packets received 4,294,967,295 multicast packets (*2) number of multicast packets received 4,294,967,295 unicast packets (*2) number of unicast packets received 4,294,967,295 undersize packets (*2) number of undersize packets received (packets smaller than 64 octets) 4,294,967,295 oversize packets (*2) number of oversize packets received (packets larger than 1523 octets (*3)) 4,294,967,295 fragments (*2) number of fragment packets received (packets smaller than 64 octets with abnormal crc) 4,294,967,295 jabbers (*2) number of jabber packets received (packets larger than 1523 octets with abnormal crc (*3)) 4,294,967,295 fcs errors (*2) number of fcs error packets received 4,294,967,295 rx errors number of reception errors 4,294,967,295 drop packets (*4) number of packets dropped from the reception buffer 4,294,967,295 (*1)  : the packet value is the total of the (*2) packets. ( 3): this will change, depending on the *mru that is set for the lan/sfp port. (*4): this is shown only if tail drop is disabled. transmitted frame counter display items display item explanation maximum value octets number of octets transmitted 18,446,744,073,709,551,615 packets (*1) number of packets transmitted 12,884,901,885 broadcast packets (*2) number of broadcast packets transmitted 4,294,967,295 multicast packets (*2) number of multicast packets transmitted 4,294,967,295 unicast packets (*2) number of unicast packets received 4,294,967,295 tx errors number of transmission errors 4,294,967,295 collisions number of collision occurrences 4,294,967,295 drop packets(*3) number of tail-dropped transmission packets 536,870,911 (*1)  : the packet value is the total of the (*2) packets. (*3): this is shown only if tail drop is enabled. transmitted/received frame counter display items display item explanation maximum value 64 octet packets number of packets with 64 octet length transmitted/received 4,294,967,295 65–127 octet packets number of packets with 65–127 octet length transmitted/received 4,294,967,295 128–255 octet packets number of packets with 128–255 octet length transmitted/received 4,294,967,295 256–511 octet packets number of packets with 256–511 octet length transmitted/received 4,294,967,295 512–1,023 octet packets number of packets with 512–1,023 octet length transmitted/received 4,294,967,295 1,024 to max octet packets number of packets with 1,024–maximum octet length (*1) transmitted/received 4,294,967,295 (*1): this will change, depending on the mru that is set for the lan/sfp port. the frame counter can also be cleared by using the clear counters command. when you execute the show interface command which shows the status of the lan/sfp ports, information on the number of transmitted and received frames is shown, but this information is shown based on the frame counter information. the number of frames transmitted/received that is displayed using the show interface command and how the frame counter is handled are shown below. number of frames transmitted/received that is displayed by the show interface command, and how the frame counter is handled display item information on the frame counter referred to input packets received frame counter packets bytes received frame counter octets multicast packets received frame counter multicast packets drop packets(*1) received frame counter drop packets output packets transmitted frame counter packets bytes transmitted frame counter octets multicast packets transmitted frame counter multicast packets broadcast packets transmitted frame counter broadcast packets drop packets(*1) transmitted frame counter drop packets (*1): if tail drop is enabled this shows only the transmission information; if it is disabled this shows only the reception information.</div><div class="display_word">3.5. Frame counter This product counts the number of frames transmitted/received for each LAN/SFP port. (This is called a “frame counter”.) To reference the frame counter, use the show frame counter command. The table below shows the display items for the frame counter and their maximum values. Received frame counter display items Display item Explanation Maximum value Octets Number of octets received 18,446,744,073,709,551,615 Packets (*1) Number of received packets 34,359,738,360 Broadcast packets (*2) Number of broadcast packets received 4,294,967,295 Multicast packets (*2) Number of multicast packets received 4,294,967,295 Unicast packets (*2) Number of unicast packets received 4,294,967,295 Undersize packets (*2) Number of undersize packets received (packets smaller than 64 octets) 4,294,967,295 Oversize packets (*2) Number of oversize packets received (packets larger than 1523 octets (*3)) 4,294,967,295 Fragments (*2) Number of fragment packets received (packets smaller than 64 octets with abnormal CRC) 4,294,967,295 Jabbers (*2) Number of jabber packets received (packets larger than 1523 octets with abnormal CRC (*3)) 4,294,967,295 FCS errors (*2) Number of FCS error packets received 4,294,967,295 RX errors Number of reception errors 4,294,967,295 Drop packets (*4) Number of packets dropped from the reception buffer 4,294,967,295 (*1)  : The packet value is the total of the (*2) packets. ( 3): This will change, depending on the *MRU that is set for the LAN/SFP port. (*4): This is shown only if tail drop is disabled. Transmitted frame counter display items Display item Explanation Maximum value Octets Number of octets transmitted 18,446,744,073,709,551,615 Packets (*1) Number of packets transmitted 12,884,901,885 Broadcast packets (*2) Number of broadcast packets transmitted 4,294,967,295 Multicast packets (*2) Number of multicast packets transmitted 4,294,967,295 Unicast packets (*2) Number of unicast packets received 4,294,967,295 TX errors Number of transmission errors 4,294,967,295 Collisions Number of collision occurrences 4,294,967,295 Drop Packets(*3) Number of tail-dropped transmission packets 536,870,911 (*1)  : The packet value is the total of the (*2) packets. (*3): This is shown only if tail drop is enabled. Transmitted/received frame counter display items Display item Explanation Maximum value 64 octet packets Number of packets with 64 octet length transmitted/received 4,294,967,295 65–127 octet packets Number of packets with 65–127 octet length transmitted/received 4,294,967,295 128–255 octet packets Number of packets with 128–255 octet length transmitted/received 4,294,967,295 256–511 octet packets Number of packets with 256–511 octet length transmitted/received 4,294,967,295 512–1,023 octet packets Number of packets with 512–1,023 octet length transmitted/received 4,294,967,295 1,024 to MAX octet packets Number of packets with 1,024–maximum octet length (*1) transmitted/received 4,294,967,295 (*1): This will change, depending on the MRU that is set for the LAN/SFP port. The frame counter can also be cleared by using the clear counters command. When you execute the show interface command which shows the status of the LAN/SFP ports, information on the number of transmitted and received frames is shown, but this information is shown based on the frame counter information. The number of frames transmitted/received that is displayed using the show interface command and how the frame counter is handled are shown below. Number of frames transmitted/received that is displayed by the show interface command, and how the frame counter is handled Display item Information on the frame counter referred to input packets Received frame counter packets bytes Received frame counter octets multicast packets Received frame counter multicast packets drop packets(*1) Received frame counter drop packets output packets Transmitted frame counter packets bytes Transmitted frame counter octets multicast packets Transmitted frame counter multicast packets broadcast packets Transmitted frame counter broadcast packets drop packets(*1) Transmitted frame counter drop packets (*1): If tail drop is enabled this shows only the transmission information; if it is disabled this shows only the reception information.</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#sfpモジュールの受光レベル監視">3.6. SFP module optical receive level monitoring</div><div class="search_word">3.6. sfp module optical receive level monitoring this product provides the function for monitoring the optical receive level of an sfp/sfp+ module connected to the sfp/sfp+ port. if a fault occurs in an sfp/sfp+ module’s optical receive level, this product’s port lamp indications change to a dedicated state, and a syslog message is output. the optical rx power error state can be forcibly cleared by pressing and holding the mode switch for three seconds. when the optical receive level returns to the normal range, this product’s port lamp indications will recover, and a syslog message is output. the syslog message is not output when the corresponding port is linked down or the optical rx power error state is forcibly cleared. the sfp/sfp+ module’s optical receive level monitoring settings can be made using the sfp-monitor command. by default, sfp module optical receive level monitoring is enabled.</div><div class="display_word">3.6. SFP module optical receive level monitoring This product provides the function for monitoring the optical receive level of an SFP/SFP+ module connected to the SFP/SFP+ port. If a fault occurs in an SFP/SFP+ module’s optical receive level, this product’s port lamp indications change to a dedicated state, and a SYSLOG message is output. The optical RX power error state can be forcibly cleared by pressing and holding the MODE switch for three seconds. When the optical receive level returns to the normal range, this product’s port lamp indications will recover, and a SYSLOG message is output. The SYSLOG message is not output when the corresponding port is linked down or the optical RX power error state is forcibly cleared. The SFP/SFP+ module’s optical receive level monitoring settings can be made using the sfp-monitor command. By default, SFP module optical receive level monitoring is enabled.</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#送信キューの使用率監視">3.7. Tx queue usage monitoring</div><div class="search_word">3.7. tx queue usage monitoring if the transmit queue’s usage ratio becomes high (above 60%, above 100%), a syslog message is output. a syslog message is also output when the transmit queue’s usage ratio returns to the normal range (below 50%). the tx queue usage monitoring setting (for the entire system or individual lan/sfp ports) can be set using the tx-queue-monitor command. all tx queue usage monitoring settings are enabled in default settings.</div><div class="display_word">3.7. Tx queue usage monitoring If the transmit queue’s usage ratio becomes high (above 60%, above 100%), a SYSLOG message is output. A SYSLOG message is also output when the transmit queue’s usage ratio returns to the normal range (below 50%). The tx queue usage monitoring setting (for the entire system or individual LAN/SFP ports) can be set using the tx-queue-monitor command. All tx queue usage monitoring settings are enabled in default settings.</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#ifindexの割り当て">4. ifIndex Assignment</div><div class="search_word">4. ifindex assignment ifindex is an id number linked to the interface and used by snmp, dhcp, etc. it is assigned as indicated in the table below. range of ifindex interface assignment assignment rule example 301 - 4394 vlan interface ifindex = 300 + vlan id 301: vlan1 4394: vlan4094 4501 - 4596 static logical interface ifindex = 4500 + static logical interface number 4501: sa1 4596: sa96 4601 - 4727 lacp logical interface ifindex = 4600 + lacp logical interface number 4601: po1 4727: po127 5001 - 6050 lan/sfp port ifindex = 4000 + 1000 × stack id + port number 5001: port1.1 6001: port2.1 6050: port2.50</div><div class="display_word">4. ifIndex Assignment ifIndex is an ID number linked to the interface and used by SNMP, DHCP, etc. It is assigned as indicated in the table below. Range of ifIndex Interface assignment Assignment rule Example 301 - 4394 VLAN interface ifIndex = 300 + VLAN ID 301: vlan1 4394: vlan4094 4501 - 4596 Static logical interface ifIndex = 4500 + static logical interface number 4501: sa1 4596: sa96 4601 - 4727 LACP logical interface ifIndex = 4600 + LACP logical interface number 4601: po1 4727: po127 5001 - 6050 LAN/SFP port ifIndex = 4000 + 1000 × stack ID + port number 5001: port1.1 6001: port2.1 6050: port2.50</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#関連コマンド">5. Related Commands</div><div class="search_word">5. related commands related commands are indicated below. for details on the commands, refer to the command reference. basic interface functions: list of related commands operations operating commands set description description shutdown shutdown set communication speed and communication mode speed-duplex set mru mru set cross/straight automatic detection mdix auto set eee eee show eee capabilities show eee capabilities show eee status information show eee status set port mirroring mirror show port-mirroring status show mirror show interface status show interface show simplified interface status show interface brief show frame counter show frame-counter clear frame counters clear counters show sfp/sfp+ status show ddm status set sfp module optical receive level monitoring sfp-monitor rx-power set tx queue usage monitoring setting (system) tx-queue-monitor usage-rate set tx queue usage monitoring setting (lan/sfp ports) tx-queue-monitor usage-rate show the tx queue usage monitoring setting show tx-queue-monitor resets interface interface reset</div><div class="display_word">5. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Basic interface functions: list of related commands Operations Operating commands Set description description Shutdown shutdown Set communication speed and communication mode speed-duplex Set MRU mru Set cross/straight automatic detection mdix auto Set EEE eee Show EEE capabilities show eee capabilities Show EEE status information show eee status Set port mirroring mirror Show port-mirroring status show mirror Show interface status show interface Show simplified interface status show interface brief Show frame counter show frame-counter Clear frame counters clear counters Show SFP/SFP+ status show ddm status Set SFP module optical receive level monitoring sfp-monitor rx-power Set tx queue usage monitoring setting (system) tx-queue-monitor usage-rate Set tx queue usage monitoring setting (LAN/SFP ports) tx-queue-monitor usage-rate Show the tx queue usage monitoring setting show tx-queue-monitor Resets interface interface reset</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#コマンド実行例">6. Examples of Command Execution</div><div class="search_word">6. examples of command execution</div><div class="display_word">6. Examples of Command Execution</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#lanポートに対する基本設定">6.1. Basic LAN port settings</div><div class="search_word">6.1. basic lan port settings some examples of basic lan port settings are shown below. for details on how to make the settings, refer to the command reference. set the description text for lan port #1 (port1.1). yamaha(config)#interface port1.1yamaha(config-if)#description connected to rtx1200-router disable lan port #1 (port1.1). yamaha(config)#interface port1.1yamaha(config-if)#shutdown enable lan port #1 (port1.1). yamaha(config)#interface port1.1yamaha(config-if)#no shutdown set the communication speed and communication mode for lan port #1 (port1.1) to 100mbps/full . yamaha(config)#interface port1.1yamaha(config-if)#speed-duplex 100-full</div><div class="display_word">6.1. Basic LAN port settings Some examples of basic LAN port settings are shown below. For details on how to make the settings, refer to the Command Reference. Set the description text for LAN port #1 (port1.1). Yamaha(config)#interface port1.1Yamaha(config-if)#description Connected to rtx1200-router Disable LAN port #1 (port1.1). Yamaha(config)#interface port1.1Yamaha(config-if)#shutdown Enable LAN port #1 (port1.1). Yamaha(config)#interface port1.1Yamaha(config-if)#no shutdown Set the communication speed and communication mode for LAN port #1 (port1.1) to 100Mbps/Full . Yamaha(config)#interface port1.1Yamaha(config-if)#speed-duplex 100-full</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#ポートミラーリング設定">6.2. Set port mirroring</div><div class="search_word">6.2. set port mirroring in this example, we will set lan port #1 to monitor the frames transmitted by lan port #4 and the frames transmitted by lan port #5. the roles of the ports are shown below. sniffer port: lan port #1 (port1.1) monitored port: lan port #4 (port1.4), lan port #5 (port1.5) specifies the monitored port for lan port #1 (port 1.1), which is a sniffer port. yamaha(config)#interface port1.1yamaha(config-if)#mirror interface port1.4 direction both (1) yamaha(config-if)#mirror interface port1.5 direction transmit (2) 1 monitor transmitted and received frames 2 monitor transmitted frames checks the port mirroring setting. yamaha#show mirrorsniffer port   monitored port  direction=============  ==============  ==========port1.1        port1.4         bothport1.1        port1.5         transmit</div><div class="display_word">6.2. Set port mirroring In this example, we will set LAN port #1 to monitor the frames transmitted by LAN port #4 and the frames transmitted by LAN port #5. The roles of the ports are shown below. Sniffer port: LAN port #1 (port1.1) Monitored port: LAN port #4 (port1.4), LAN port #5 (port1.5) Specifies the monitored port for LAN port #1 (port 1.1), which is a sniffer port. Yamaha(config)#interface port1.1Yamaha(config-if)#mirror interface port1.4 direction both (1) Yamaha(config-if)#mirror interface port1.5 direction transmit (2) 1 Monitor transmitted and received frames 2 Monitor transmitted frames Checks the port mirroring setting. Yamaha#show mirrorSniffer Port   Monitored Port  Direction=============  ==============  ==========port1.1        port1.4         bothport1.1        port1.5         transmit</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#lansfpポートの情報表示">6.3. Show LAN/SFP port information</div><div class="search_word">6.3. show lan/sfp port information confirm the status of lan port #1 (port1.1). yamaha#show interface port 1.1interface port1.1  link is up  hardware is ethernet  hw addr: 00a0.deae.b89f  description: connected to router  ifindex 5001, mru 1522  speed-duplex: auto(configured), 1000-full(current)  auto mdi/mdix: on  vlan info :    switchport mode        : access    ingress filter         : enable    acceptable frame types : all    default vlan           :    1    configured vlans       :    1  interface counter:    input  packets          : 0           bytes            : 0           multicast packets: 0    output packets          : 0           bytes            : 0           multicast packets: 0           broadcast packets: 0           drop packets     : 0</div><div class="display_word">6.3. Show LAN/SFP port information Confirm the status of LAN port #1 (port1.1). Yamaha#show interface port 1.1Interface port1.1  Link is UP  Hardware is Ethernet  HW addr: 00a0.deae.b89f  Description: Connected to router  ifIndex 5001, MRU 1522  Speed-Duplex: auto(configured), 1000-full(current)  Auto MDI/MDIX: on  Vlan info :    Switchport mode        : access    Ingress filter         : enable    Acceptable frame types : all    Default Vlan           :    1    Configured Vlans       :    1  Interface counter:    input  packets          : 0           bytes            : 0           multicast packets: 0    output packets          : 0           bytes            : 0           multicast packets: 0           broadcast packets: 0           drop packets     : 0</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#注意事項">7. Points of Caution</div><div class="search_word">7. points of caution none</div><div class="display_word">7. Points of Caution None</div></div><div id="interface_interface_basic"><div class="search_title" docfname="interface_interface_basic" doctitle="Basic" link="#関連文書">8. Related Documentation</div><div class="search_word">8. related documentation none</div><div class="display_word">8. Related Documentation None</div></div><div id="interface_interface_lag"><div class="search_title" docfname="interface_interface_lag" doctitle="Link" link="#リンクアグリゲーション">Link aggregation</div><div class="search_word">link aggregation</div><div class="display_word">Link aggregation</div></div><div id="interface_interface_lag"><div class="search_title" docfname="interface_interface_lag" doctitle="Link" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview link aggregation is a function used to combine multiple lan/sfp ports that connect network devices, and handle them as a single logical interface. link aggregation is a technology that is useful when multiple communications occur. communications can be distributed by using a load balance function within the combined lines. if one lan/sfp port fails within the lines that were combined using link aggregation, and communications cannot be made, the other ports will continue communicating. link aggregation function overview the link aggregation functions in this network switch are shown below. link aggregation functions functions provided contents static link aggregation link aggregation for manually setting the lan/sfp ports to combine. this begins to operate as a logical interface when the lan/sfp ports link up. lacp link aggregation link aggregation that uses lacp to combine the lan/sfp ports. this begins to operate as a logical interface when the negotiation via lacp between the connected devices is successful.</div><div class="display_word">1. Function Overview Link aggregation is a function used to combine multiple LAN/SFP ports that connect network devices, and handle them as a single logical interface. Link aggregation is a technology that is useful when multiple communications occur. Communications can be distributed by using a load balance function within the combined lines. If one LAN/SFP port fails within the lines that were combined using link aggregation, and communications cannot be made, the other ports will continue communicating. Link aggregation function overview The link aggregation functions in this network switch are shown below. Link aggregation functions Functions provided Contents Static link aggregation Link aggregation for manually setting the LAN/SFP ports to combine. This begins to operate as a logical interface when the LAN/SFP ports link up. LACP link aggregation Link aggregation that uses LACP to combine the LAN/SFP ports. This begins to operate as a logical interface when the negotiation via LACP between the connected devices is successful.</div></div><div id="interface_interface_lag"><div class="search_title" docfname="interface_interface_lag" doctitle="Link" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used lacp abbreviation for “link aggregation control protocol”. this is a technology standardized in ieee802.1ax-2008, and is also called etherchannel. ieee802.1ax-2008 link aggregation task force load balance this is a function to distribute forwarded frames between the lan/sfp ports that are associated with the logical interface. as a distribution rule, the l2/l3/l4 information within frames is used.</div><div class="display_word">2. Definition of Terms Used LACP Abbreviation for “Link Aggregation Control Protocol”. This is a technology standardized in IEEE802.1AX-2008, and is also called EtherChannel. IEEE802.1AX-2008 Link Aggregation Task Force Load balance This is a function to distribute forwarded frames between the LAN/SFP ports that are associated with the logical interface. As a distribution rule, the L2/L3/L4 information within frames is used.</div></div><div id="interface_interface_lag"><div class="search_title" docfname="interface_interface_lag" doctitle="Link" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="interface_interface_lag"><div class="search_title" docfname="interface_interface_lag" doctitle="Link" link="#スタティックlacp-リンクアグリゲーション-共通仕様">3.1. Static/LACP link aggregation: common specifications</div><div class="search_word">3.1. static/lacp link aggregation: common specifications the common specifications for the static/lacp link aggregation functions of this network switch are shown below. the link aggregation on this network switch can be defined for 127 interfaces, including both static and lacp (126 interfaces for stacks). a single logical interface can be associated with up to eight lan/sfp ports . the settings shown below must be the same for each of the lan/sfp ports contained within. port mode (access/trunk [including native vlan settings]) associated vlan qos trust mode (including port priority and default cos settings) loop detection (enables/disables loop detection and enables/disables port blocking) executes the following process when a lan/sfp port is associated with a logical interface. lan/sfp ports that are linked up will be linked down . the logical interface’s default value will be set to shutdown , in order to safely integrate the logical interface into the system. mstp settings will be discarded and will revert to their defaults. when dissociating a lan/sfp port from the logical link, the mstp settings for the relevant port will revert to their defaults as well. the following operations can be performed for the logical interface. add description text ( description command) enable/disable the interface ( shutdown command) another lan/sfp port cannot be associated with a logical interface in operation. to associate a lan/sfp port, make sure to shut down the logical interface before associating. lan/sfp ports that are associated with a logical interface that is in operation cannot be removed. when dissociating a lan/sfp port, make sure to shut down the logical interface before dissociating. lan/sfp ports that have been dissociated from a logical interface will be in shutdown mode. enable the ports as necessary (using “ no shutdown ”). load balance settings can be made on the logical interface. the rules that can be set for this are shown below. the default value when defining a logical interface is the destination/source mac address . destination mac address source mac address destination/source mac address destination ip address source ip address destination/source ip address destination port number source port number destination/source port numbers</div><div class="display_word">3.1. Static/LACP link aggregation: common specifications The common specifications for the static/LACP link aggregation functions of this network switch are shown below. The link aggregation on this network switch can be defined for 127 interfaces, including both static and LACP (126 interfaces for stacks). A single logical interface can be associated with up to eight LAN/SFP ports . The settings shown below must be the same for each of the LAN/SFP ports contained within. Port mode (access/trunk [including native VLAN settings]) Associated VLAN QoS trust mode (including port priority and default CoS settings) Loop detection (enables/disables loop detection and enables/disables port blocking) Executes the following process when a LAN/SFP port is associated with a logical interface. LAN/SFP ports that are linked up will be linked down . The logical interface’s default value will be set to shutdown , in order to safely integrate the logical interface into the system. MSTP settings will be discarded and will revert to their defaults. When dissociating a LAN/SFP port from the logical link, the MSTP settings for the relevant port will revert to their defaults as well. The following operations can be performed for the logical interface. Add description text ( description command) Enable/disable the interface ( shutdown command) Another LAN/SFP port cannot be associated with a logical interface in operation. To associate a LAN/SFP port, make sure to shut down the logical interface before associating. LAN/SFP ports that are associated with a logical interface that is in operation cannot be removed. When dissociating a LAN/SFP port, make sure to shut down the logical interface before dissociating. LAN/SFP ports that have been dissociated from a logical interface will be in shutdown mode. Enable the ports as necessary (using “ no shutdown ”). Load balance settings can be made on the logical interface. The rules that can be set for this are shown below. The default value when defining a logical interface is the destination/source MAC address . Destination MAC address Source MAC address Destination/source MAC address Destination IP address Source IP address Destination/source IP address Destination port number Source port number Destination/source port numbers</div></div><div id="interface_interface_lag"><div class="search_title" docfname="interface_interface_lag" doctitle="Link" link="#スタティック-リンクアグリゲーション">3.2. Static link aggregation</div><div class="search_word">3.2. static link aggregation the operating specifications for static link aggregation are shown below. an interface number from 1–96 can be assigned to the static logical interface. use the static-channel-group command to associate a lan/sfp port with a static logical link interface. when associating a lan/sfp port with an interface number for which there is no static logical interface, a new logical interface will be generated. when the associated port no longer exists as a result of removing a lan/sfp port from a static logical interface, the relevant logical interface will be deleted. use the show static-channel-group command to show the static logical interface’s status.</div><div class="display_word">3.2. Static link aggregation The operating specifications for static link aggregation are shown below. An interface number from 1–96 can be assigned to the static logical interface. Use the static-channel-group command to associate a LAN/SFP port with a static logical link interface. When associating a LAN/SFP port with an interface number for which there is no static logical interface, a new logical interface will be generated. When the associated port no longer exists as a result of removing a LAN/SFP port from a static logical interface, the relevant logical interface will be deleted. Use the show static-channel-group command to show the static logical interface’s status.</div></div><div id="interface_interface_lag"><div class="search_title" docfname="interface_interface_lag" doctitle="Link" link="#lacp-リンクアグリゲーション">3.3. LACP link aggregation</div><div class="search_word">3.3. lacp link aggregation the operating specifications for lacp link aggregation are shown below. refer to “3.1 static/lacp link aggregation: common specifications” for the common specifications of static link aggregation. an interface number from 1–127 can be assigned to the lacp logical interface. use the channel-group command to associate a lan/sfp port with an lacp logical link interface. when associating an lan/sfp, specify the following operating modes . (it is recommended to specify “active mode”.) active mode the lacp frame will be voluntarily transmitted, and negotiation with the opposing device’s port will begin. passive mode the lacp frame will not be voluntarily transmitted, but will instead be transmitted when a frame is received from the opposing device. when associating a lan/sfp port with an interface number for which there is no lacp logical interface, a new logical interface will be generated. when the associated port no longer exists as a result of removing a lan/sfp port from an lacp logical interface, the relevant logical interface will be deleted. the parameters that influence the operations of the lacp logical interface are shown below. lacp timeout lacp timeout indicates the down time that was determined, when an lacp frame has not been received from the opposing device. specify either “ long” (90 sec.) or “short” (3 sec.) using the lacp timeout command. the lacp timeout value is stored in the lacp frame and transmitted to the opposing device. the opposing device that received the frame will transmit the lacp frames it has stored at intervals equaling 1/3 of the lacp timeout value. the default value when the logical interface is generated is “ long (90 sec.) ”. lacp system priority the lacp system priority is used when deciding which device will control the logical interface , when communicating with the opposing device. the lacp system priority and mac address values (in combination referred to as the system id ) are exchanged with the interfacing device and the device with the highest lacp system priority level is assigned control. if both devices have the same lacp system priority level, the device with the lower mac address is assigned control. the device assigned control determines which lan or sfp ports associated with the logical interface are enabled (activated). lacp system priority values within the range 1 to 65535 can be specified using the lacp system-priority command, where the lower the setting value, the higher the priority level. the default value when the logical interface is generated is set to 32768 (0x8000) . lacp port priority lacp port priority is used to control active/standby for the lan/sfp ports that are associated with the logical interface . if more than the maximum number of lan/sfp ports (8 ports) is associated with a logical interface, then the port status is controlled based on the lacp port priority . if ports have the same lacp port priority , then the port with the lower port number is given priority. if a stack is configured, port numbers for network switches with a lower stack id are prioritized regardless of the port number. for example, port 1.10 is prioritized over port 2.1. lacp port priority values within the range 1 to 65535 can be specified using the lacp port-priority command, where the lower the setting value, the higher the priority level. the default lacp port priority setting is 32768 (0x8000) . lan/sfp ports in half-duplex communication mode do not support lacp link aggregation. half-duplex lan/sfp ports that are associated with an lacp logical interface are never activated. the following describes actions that occur if lan/sfp ports with different communication speeds are located on the same logical interface. to configure link aggregation with a mixture of different communication speeds, enable multi-speed link aggregation. actions if multi-speed link aggregation is enabled ( lacp multi-speed enable ) activate all associated ports (up to a maximum 8 ports), regardless of communication speed. load balancing treats all associated ports as equivalent. that increases the risk of a communication overflow occurring at a slow associated port. if there are more than the maximum 8 lan/sfp ports, higher priority values are assigned to faster associated ports. if the other device cannot accept a different communication speed, then both interacting devices mutually exchange lists of associated ports and activate associated port that can be used by both devices. consequently, the process is limited by the device that cannot accept different communication speeds. actions if multi-speed link aggregation is disabled ( lacp multi-speed disable ) only associated ports with a communication speed the same as the port first linked up are activated. other ports with a different communication speed remain in standby mode. if auto negotiation is enabled, only associated ports with a communication speed that is the same as the negotiation result of the first negotiation will be activated. if links go down for all the ports first linked up, then the link will go down for the lacp logical interface as well. the show etherchannel command can be used to check the lacp logical interface status. the show etherchannel status detail command can be used to check the activation status of associated ports. lacp link aggregation is used even if a stack is configured. however, the following restriction applies. a total of 126 logical interfaces can be defined for both static and lacp.</div><div class="display_word">3.3. LACP link aggregation The operating specifications for LACP link aggregation are shown below. Refer to “3.1 Static/LACP link aggregation: common specifications” for the common specifications of static link aggregation. An interface number from 1–127 can be assigned to the LACP logical interface. Use the channel-group command to associate a LAN/SFP port with an LACP logical link interface. When associating an LAN/SFP, specify the following operating modes . (It is recommended to specify “active mode”.) Active mode The LACP frame will be voluntarily transmitted, and negotiation with the opposing device’s port will begin. Passive mode The LACP frame will not be voluntarily transmitted, but will instead be transmitted when a frame is received from the opposing device. When associating a LAN/SFP port with an interface number for which there is no LACP logical interface, a new logical interface will be generated. When the associated port no longer exists as a result of removing a LAN/SFP port from an LACP logical interface, the relevant logical interface will be deleted. The parameters that influence the operations of the LACP logical interface are shown below. LACP timeout LACP timeout indicates the down time that was determined, when an LACP frame has not been received from the opposing device. Specify either “ Long” (90 sec.) or “Short” (3 sec.) using the lacp timeout command. The LACP timeout value is stored in the LACP frame and transmitted to the opposing device. The opposing device that received the frame will transmit the LACP frames it has stored at intervals equaling 1/3 of the LACP timeout value. The default value when the logical interface is generated is “ Long (90 sec.) ”. LACP system priority The LACP system priority is used when deciding which device will control the logical interface , when communicating with the opposing device. The LACP system priority and MAC address values (in combination referred to as the system ID ) are exchanged with the interfacing device and the device with the highest LACP system priority level is assigned control. If both devices have the same LACP system priority level, the device with the lower MAC address is assigned control. The device assigned control determines which LAN or SFP ports associated with the logical interface are enabled (activated). LACP system priority values within the range 1 to 65535 can be specified using the lacp system-priority command, where the lower the setting value, the higher the priority level. The default value when the logical interface is generated is set to 32768 (0x8000) . LACP port priority LACP port priority is used to control active/standby for the LAN/SFP ports that are associated with the logical interface . If more than the maximum number of LAN/SFP ports (8 ports) is associated with a logical interface, then the port status is controlled based on the LACP port priority . If ports have the same LACP port priority , then the port with the lower port number is given priority. If a stack is configured, port numbers for network switches with a lower stack ID are prioritized regardless of the port number. For example, port 1.10 is prioritized over port 2.1. LACP port priority values within the range 1 to 65535 can be specified using the lacp port-priority command, where the lower the setting value, the higher the priority level. The default LACP port priority setting is 32768 (0x8000) . LAN/SFP ports in half-duplex communication mode do not support LACP link aggregation. Half-duplex LAN/SFP ports that are associated with an LACP logical interface are never activated. The following describes actions that occur if LAN/SFP ports with different communication speeds are located on the same logical interface. To configure link aggregation with a mixture of different communication speeds, enable multi-speed link aggregation. Actions if multi-speed link aggregation is enabled ( lacp multi-speed enable ) Activate all associated ports (up to a maximum 8 ports), regardless of communication speed. Load balancing treats all associated ports as equivalent. That increases the risk of a communication overflow occurring at a slow associated port. If there are more than the maximum 8 LAN/SFP ports, higher priority values are assigned to faster associated ports. If the other device cannot accept a different communication speed, then both interacting devices mutually exchange lists of associated ports and activate associated port that can be used by both devices. Consequently, the process is limited by the device that cannot accept different communication speeds. Actions if multi-speed link aggregation is disabled ( lacp multi-speed disable ) Only associated ports with a communication speed the same as the port first linked up are activated. Other ports with a different communication speed remain in standby mode. If auto negotiation is enabled, only associated ports with a communication speed that is the same as the negotiation result of the first negotiation will be activated. If links go down for all the ports first linked up, then the link will go down for the LACP logical interface as well. The show etherchannel command can be used to check the LACP logical interface status. The show etherchannel status detail command can be used to check the activation status of associated ports. LACP link aggregation is used even if a stack is configured. However, the following restriction applies. A total of 126 logical interfaces can be defined for both static and LACP.</div></div><div id="interface_interface_lag"><div class="search_title" docfname="interface_interface_lag" doctitle="Link" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands set the static logical interface static-channel-group show the static logical interface status show static-channel-group set the lacp logical interface channel-group set lacp system priority lacp system-priority show lacp system priority show lacp sys-id set lacp multi-speed link aggregation lacp multi-speed set lacp timeout lacp timeout clear lacp packet counter clear lacp show lacp packet counter show lacp counters show the status of the lacp logical interface show etherchannel set load balance function rules port-channel load-balance</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Set the static logical interface static-channel-group Show the static logical interface status show static-channel-group Set the LACP logical interface channel-group Set LACP system priority lacp system-priority Show LACP system priority show lacp sys-id Set LACP multi-speed link aggregation lacp multi-speed Set LACP timeout lacp timeout Clear LACP packet counter clear lacp Show LACP packet counter show lacp counters Show the status of the LACP logical interface show etherchannel Set load balance function rules port-channel load-balance</div></div><div id="interface_interface_lag"><div class="search_title" docfname="interface_interface_lag" doctitle="Link" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="interface_interface_lag"><div class="search_title" docfname="interface_interface_lag" doctitle="Link" link="#スタティック論理インターフェースの設定">5.1. Set the static logical interface</div><div class="search_word">5.1. set the static logical interface in this example, we will set link aggregation to use four lan ports, in order to communicate between network switches. static link aggregation is set to static. the logical interface numbers are as follows: switch a: #2, switch b: #5. the lan ports associated with the logical interface are all access ports, and are associated with the vlan #1000. define [switch a] vlan #1000, and associate it with lan ports (#1, #2, #3, #4, #8). together with this, associate lan ports (#1, #2, #3, #4) with logical interface #2. yamaha(config)#vlan databaseyamaha(config-vlan)#vlan 1000 (1) yamaha(config-vlan)#exityamaha(config)#interface port1.8 (2) yamaha(config-if)#switchport access vlan 1000 (3) yamaha(config-if)#interface port1.1 (4) yamaha(config-if)#switchport access vlan 1000 (5) yamaha(config-if)#static-channel-group 2 (6) yamaha(config-if)#interface port1.2yamaha(config-if)#switchport access vlan 1000yamaha(config-if)#static-channel-group 2yamaha(config-if)#interface port1.3yamaha(config-if)#switchport access vlan 1000yamaha(config-if)#static-channel-group 2yamaha(config-if)#interface port1.4yamaha(config-if)#switchport access vlan 1000yamaha(config-if)#static-channel-group 2 1 define vlan #1000 2 set lan port #8 3 set the port as access port and associate it with vlan #1000 4 set lan port #1 5 set the port as access port and associate it with vlan #1000 6 associate it with logical interface #2 confirm the setting status of [switch a] logical interface #2. yamaha#show static-channel-group% static aggregator: sa2% member:   port1.1   port1.2   port1.3   port1.4 define [switch b] vlan #1000, and associate it with lan ports (#1, #2, #3, #4, #7). together with this, associate lan ports (#1, #2, #3, #4) with logical interface #5. yamaha(config)#vlan databaseyamaha(config-vlan)#vlan 1000yamaha(config-vlan)#exityamaha(config)#interface port1.7yamaha(config-if)#switchport access vlan 1000yamaha(config-if)#interface port1.1yamaha(config-if)#switchport access vlan 1000yamaha(config-if)#static-channel-group 5yamaha(config-if)#interface port1.2yamaha(config-if)#switchport access vlan 1000yamaha(config-if)#static-channel-group 5yamaha(config-if)#interface port1.3yamaha(config-if)#switchport access vlan 1000yamaha(config-if)#static-channel-group 5yamaha(config-if)#interface port1.4yamaha(config-if)#switchport access vlan 1000yamaha(config-if)#static-channel-group 5 confirm the setting status of [switch b] logical interface #5. yamaha#show static-channel-group% static aggregator: sa5% member:   port1.1   port1.2   port1.3   port1.4 enable [switch a] logical interface. yamaha(config)#interface sa2 (1) yamaha(config-if)#no shutdown (2) 1 set logical interface #2 2 enable the logical interface enable [switch b] logical interface. yamaha(config)#interface sa5 (1) yamaha(config-if)#no shutdown (2) 1 set logical interface #5 2 enable the logical interface confirm the setting status of [switch a] logical interface. yamaha#show interface sa2interface sa2  link is up (1) hardware is aggregate  ifindex 4502, mru 1522  vlan info :    switchport mode        : access    ingress filter         : enable    acceptable frame types : all    default vlan           : 1000    configured vlans       : 1000  interface counter:    input  packets          : 1020           bytes            : 102432           multicast packets: 1020    output packets          : 15           bytes            : 1845           multicast packets: 15           broadcast packets: 0 1 enabled confirm the setting status of [switch b] logical interface. yamaha#show interface sa5interface sa5  link is up  hardware is aggregate  ifindex 4505, mru 1522  vlan info :    switchport mode        : access    ingress filter         : enable    acceptable frame types : all    default vlan           : 1000    configured vlans       : 1000  interface counter:    input  packets          : 24           bytes            : 2952           multicast packets: 24    output packets          : 2109           bytes            : 211698           multicast packets: 2109           broadcast packets: 0</div><div class="display_word">5.1. Set the static logical interface In this example, we will set link aggregation to use four LAN ports, in order to communicate between network switches. Static link aggregation is set to static. The logical interface numbers are as follows: Switch A: #2, switch B: #5. The LAN ports associated with the logical interface are all access ports, and are associated with the VLAN #1000. Define [switch A] VLAN #1000, and associate it with LAN ports (#1, #2, #3, #4, #8). Together with this, associate LAN ports (#1, #2, #3, #4) with logical interface #2. Yamaha(config)#vlan databaseYamaha(config-vlan)#vlan 1000 (1) Yamaha(config-vlan)#exitYamaha(config)#interface port1.8 (2) Yamaha(config-if)#switchport access vlan 1000 (3) Yamaha(config-if)#interface port1.1 (4) Yamaha(config-if)#switchport access vlan 1000 (5) Yamaha(config-if)#static-channel-group 2 (6) Yamaha(config-if)#interface port1.2Yamaha(config-if)#switchport access vlan 1000Yamaha(config-if)#static-channel-group 2Yamaha(config-if)#interface port1.3Yamaha(config-if)#switchport access vlan 1000Yamaha(config-if)#static-channel-group 2Yamaha(config-if)#interface port1.4Yamaha(config-if)#switchport access vlan 1000Yamaha(config-if)#static-channel-group 2 1 Define VLAN #1000 2 Set LAN port #8 3 Set the port as access port and associate it with VLAN #1000 4 Set LAN port #1 5 Set the port as access port and associate it with VLAN #1000 6 Associate it with logical interface #2 Confirm the setting status of [switch A] logical interface #2. Yamaha#show static-channel-group% Static Aggregator: sa2% Member:   port1.1   port1.2   port1.3   port1.4 Define [switch B] VLAN #1000, and associate it with LAN ports (#1, #2, #3, #4, #7). Together with this, associate LAN ports (#1, #2, #3, #4) with logical interface #5. Yamaha(config)#vlan databaseYamaha(config-vlan)#vlan 1000Yamaha(config-vlan)#exitYamaha(config)#interface port1.7Yamaha(config-if)#switchport access vlan 1000Yamaha(config-if)#interface port1.1Yamaha(config-if)#switchport access vlan 1000Yamaha(config-if)#static-channel-group 5Yamaha(config-if)#interface port1.2Yamaha(config-if)#switchport access vlan 1000Yamaha(config-if)#static-channel-group 5Yamaha(config-if)#interface port1.3Yamaha(config-if)#switchport access vlan 1000Yamaha(config-if)#static-channel-group 5Yamaha(config-if)#interface port1.4Yamaha(config-if)#switchport access vlan 1000Yamaha(config-if)#static-channel-group 5 Confirm the setting status of [switch B] logical interface #5. Yamaha#show static-channel-group% Static Aggregator: sa5% Member:   port1.1   port1.2   port1.3   port1.4 Enable [switch A] logical interface. Yamaha(config)#interface sa2 (1) Yamaha(config-if)#no shutdown (2) 1 Set logical interface #2 2 Enable the logical interface Enable [switch B] logical interface. Yamaha(config)#interface sa5 (1) Yamaha(config-if)#no shutdown (2) 1 Set logical interface #5 2 Enable the logical interface Confirm the setting status of [switch A] logical interface. Yamaha#show interface sa2Interface sa2  Link is UP (1) Hardware is AGGREGATE  ifIndex 4502, MRU 1522  Vlan info :    Switchport mode        : access    Ingress filter         : enable    Acceptable frame types : all    Default Vlan           : 1000    Configured Vlans       : 1000  Interface counter:    input  packets          : 1020           bytes            : 102432           multicast packets: 1020    output packets          : 15           bytes            : 1845           multicast packets: 15           broadcast packets: 0 1 Enabled Confirm the setting status of [switch B] logical interface. Yamaha#show interface sa5Interface sa5  Link is UP  Hardware is AGGREGATE  ifIndex 4505, MRU 1522  Vlan info :    Switchport mode        : access    Ingress filter         : enable    Acceptable frame types : all    Default Vlan           : 1000    Configured Vlans       : 1000  Interface counter:    input  packets          : 24           bytes            : 2952           multicast packets: 24    output packets          : 2109           bytes            : 211698           multicast packets: 2109           broadcast packets: 0</div></div><div id="interface_interface_lag"><div class="search_title" docfname="interface_interface_lag" doctitle="Link" link="#lacp-論理インターフェースの設定">5.2. Setting the LACP logical interface</div><div class="search_word">5.2. setting the lacp logical interface in this example, we will set link aggregation to use four lan ports, in order to communicate between network switches. use lacp for link aggregation. the logical interface numbers are as follows: switch a: #10, switch b: #20. set the switch a logical interface to active status , and the switch b logical interface to passive status . the lan ports associated with the logical interface are all access ports, and are associated with the vlan #1000. for load balance , set the destination/source ip address. define [switch a] vlan #1000, and associate it with lan ports (#1, #2, #3, #4, #8). together with this, associate lan ports (#1, #2, #3, #4) in active status with the logical interface #10 . the logical interface at this point in time will be in shutdown mode. yamaha(config)#vlan databaseyamaha(config-vlan)#vlan 1000 (1) yamaha(config-vlan)#exityamaha(config)#interface port1.8yamaha(config-if)#switchport access vlan 1000 (2) yamaha(config-if)#interface port1.1yamaha(config-if)#switchport access vlan 1000 (3) yamaha(config-if)#channel-group 10 mode active (4) yamaha(config-if)#interface port1.2yamaha(config-if)#switchport access vlan 1000yamaha(config-if)# channel-group 10 mode activeyamaha(config-if)#interface port1.3yamaha(config-if)#switchport access vlan 1000yamaha(config-if)# channel-group 10 mode activeyamaha(config-if)#interface port1.4yamaha(config-if)#switchport access vlan 1000yamaha(config-if)# channel-group 10 mode active 1 define vlan #1000 2 set the port as access port and associate it with vlan #1000 3 set the port as access port and associate it with vlan #1000 4 associate the port with logical interface #10 in active state confirm the setting status of [switch a] logical interface #10. yamaha#show etherchannel% lacp aggregator: po10% member:   port1.1   port1.2   port1.3   port1.4yamaha#show lacp sys-id (1) % system 8000,00-a0-de-ae-b9-1fyamaha#show interface po10interface po10  link is down (2) hardware is aggregate  ifindex 4610, mru 1522  vlan info :    switchport mode        : access    ingress filter         : enable    acceptable frame types : all    default vlan           : 1000    configured vlans       : 1000  interface counter:    input  packets          : 0           bytes            : 0           multicast packets: 0    output packets          : 0           bytes            : 0           multicast packets: 0           broadcast packets: 0 1 check that the lacp system id is set to the default value (0x8000). 2 link is in down define [switch b] vlan #1000, and associate it with lan ports (#1, #2, #3, #4, #7). together with this, associate lan ports (#1, #2, #3, #4) in passive status with the logical interface #20 . the logical interface at this point in time will be in shutdown mode. yamaha(config)#vlan databaseyamaha(config-vlan)#vlan 1000 (1) yamaha(config-vlan)#exityamaha(config)#interface port1.7yamaha(config-if)#switchport access vlan 1000 (2) yamaha(config-if)#interface port1.1yamaha(config-if)#switchport access vlan 1000 (3) yamaha(config-if)#channel-group 20 mode passive (4) yamaha(config-if)#interface port1.2yamaha(config-if)#switchport access vlan 1000yamaha(config-if)# channel-group 20 mode passiveyamaha(config-if)#interface port1.3yamaha(config-if)#switchport access vlan 1000yamaha(config-if)# channel-group 20 mode passiveyamaha(config-if)#interface port1.4yamaha(config-if)#switchport access vlan 1000yamaha(config-if)# channel-group 20 mode passive 1 define vlan #1000 2 set the port as access port and associate it with vlan #1000 3 set the port as access port and associate it with vlan #1000 4 associate the port with logical interface #20 in passive state confirm the setting status of [switch b] logical interface #20. yamaha#show etherchannel% lacp aggregator: po20% member:   port1.1   port1.2   port1.3   port1.4yamaha#show lacp sys-id (1) % system 8000,00-a0-de-ae-b8-7eyamaha#show interface po20interface po20  link is down (2) hardware is aggregate  ifindex 4620, mru 1522  vlan info :    switchport mode        : access    ingress filter         : enable    acceptable frame types : all    default vlan           : 1000    configured vlans       : 1000  interface counter:    input  packets          : 0           bytes            : 0           multicast packets: 0    output packets          : 0           bytes            : 0           multicast packets: 0           broadcast packets: 0 1 check that the lacp system id is set to the default value (0x8000). 2 link down state set the load balance of [switch a] to the destination/source ip address, and enable the interface. yamaha(config)#port-channel load-balance src-dst-ip (1) yamaha(config)#interface po10 (2) yamaha(config-if)#no shutdown (3) 1 set the load balance 2 set logical interface #10 3 enable the logical interface set the load balance of [switch b] to the destination/source ip address, and enable the interface. yamaha(config)#port-channel load-balance src-dst-ip (1) yamaha(config)#interface po20 (2) yamaha(config-if)#no shutdown (3) 1 set the load balance 2 set logical interface #20 3 enable the logical interface confirm the setting status of [switch a] logical interface. link up and confirm whether frames are being sent and received. yamaha#show interface po10interface po10  link is up  hardware is aggregate  ifindex 4610, mru 1522  vlan info :    switchport mode        : access    ingress filter         : enable    acceptable frame types : all    default vlan           : 1000    configured vlans       : 1000  interface counter:    input  packets          : 560           bytes            : 58239           multicast packets: 560    output packets          : 98           bytes            : 12474           multicast packets: 98           broadcast packets: 0yamaha#yamaha#show lacp-counter% traffic statisticsport       lacpdus         marker         pckt err        sent    recv    sent    recv    sent    recv% aggregator po10 , id 4610port1.1      50      47      0       0       0       0port1.2      49      46      0       0       0       0port1.3      49      46      0       0       0       0port1.4      49      46      0       0       0       0 confirm the setting status of [switch b] logical interface. link up and confirm whether frames are being sent and received. yamaha#show interface po20interface po20  link is up  hardware is aggregate  ifindex 4620, mru 1522  vlan info :    switchport mode        : access    ingress filter         : enable    acceptable frame types : all    default vlan           : 1000    configured vlans       : 1000  interface counter:    input  packets          : 78           bytes            : 9914           multicast packets: 78    output packets          : 438           bytes            : 45604           multicast packets: 438           broadcast packets: 0yamaha#yamaha#show lacp-counter% traffic statisticsport       lacpdus         marker         pckt err        sent    recv    sent    recv    sent    recv% aggregator po20 , id 4620port1.1      55      57      0       0       0       0port1.2      54      56      0       0       0       0port1.3      54      56      0       0       0       0port1.4      54      56      0       0       0       0</div><div class="display_word">5.2. Setting the LACP logical interface In this example, we will set link aggregation to use four LAN ports, in order to communicate between network switches. Use LACP for link aggregation. The logical interface numbers are as follows: Switch A: #10, switch B: #20. Set the switch A logical interface to active status , and the switch B logical interface to passive status . The LAN ports associated with the logical interface are all access ports, and are associated with the VLAN #1000. For load balance , set the destination/source IP address. Define [switch A] VLAN #1000, and associate it with LAN ports (#1, #2, #3, #4, #8). Together with this, associate LAN ports (#1, #2, #3, #4) in active status with the logical interface #10 . The logical interface at this point in time will be in shutdown mode. Yamaha(config)#vlan databaseYamaha(config-vlan)#vlan 1000 (1) Yamaha(config-vlan)#exitYamaha(config)#interface port1.8Yamaha(config-if)#switchport access vlan 1000 (2) Yamaha(config-if)#interface port1.1Yamaha(config-if)#switchport access vlan 1000 (3) Yamaha(config-if)#channel-group 10 mode active (4) Yamaha(config-if)#interface port1.2Yamaha(config-if)#switchport access vlan 1000Yamaha(config-if)# channel-group 10 mode activeYamaha(config-if)#interface port1.3Yamaha(config-if)#switchport access vlan 1000Yamaha(config-if)# channel-group 10 mode activeYamaha(config-if)#interface port1.4Yamaha(config-if)#switchport access vlan 1000Yamaha(config-if)# channel-group 10 mode active 1 Define VLAN #1000 2 Set the port as access port and associate it with VLAN #1000 3 Set the port as access port and associate it with VLAN #1000 4 Associate the port with logical interface #10 in active state Confirm the setting status of [switch A] logical interface #10. Yamaha#show etherchannel% Lacp Aggregator: po10% Member:   port1.1   port1.2   port1.3   port1.4Yamaha#show lacp sys-id (1) % System 8000,00-a0-de-ae-b9-1fYamaha#show interface po10Interface po10  Link is DOWN (2) Hardware is AGGREGATE  ifIndex 4610, MRU 1522  Vlan info :    Switchport mode        : access    Ingress filter         : enable    Acceptable frame types : all    Default Vlan           : 1000    Configured Vlans       : 1000  Interface counter:    input  packets          : 0           bytes            : 0           multicast packets: 0    output packets          : 0           bytes            : 0           multicast packets: 0           broadcast packets: 0 1 Check that the LACP system ID is set to the default value (0x8000). 2 Link is in down Define [switch B] VLAN #1000, and associate it with LAN ports (#1, #2, #3, #4, #7). Together with this, associate LAN ports (#1, #2, #3, #4) in passive status with the logical interface #20 . The logical interface at this point in time will be in shutdown mode. Yamaha(config)#vlan databaseYamaha(config-vlan)#vlan 1000 (1) Yamaha(config-vlan)#exitYamaha(config)#interface port1.7Yamaha(config-if)#switchport access vlan 1000 (2) Yamaha(config-if)#interface port1.1Yamaha(config-if)#switchport access vlan 1000 (3) Yamaha(config-if)#channel-group 20 mode passive (4) Yamaha(config-if)#interface port1.2Yamaha(config-if)#switchport access vlan 1000Yamaha(config-if)# channel-group 20 mode passiveYamaha(config-if)#interface port1.3Yamaha(config-if)#switchport access vlan 1000Yamaha(config-if)# channel-group 20 mode passiveYamaha(config-if)#interface port1.4Yamaha(config-if)#switchport access vlan 1000Yamaha(config-if)# channel-group 20 mode passive 1 Define VLAN #1000 2 Set the port as access port and associate it with VLAN #1000 3 Set the port as access port and associate it with VLAN #1000 4 Associate the port with logical interface #20 in passive state Confirm the setting status of [switch B] logical interface #20. Yamaha#show etherchannel% Lacp Aggregator: po20% Member:   port1.1   port1.2   port1.3   port1.4Yamaha#show lacp sys-id (1) % System 8000,00-a0-de-ae-b8-7eYamaha#show interface po20Interface po20  Link is DOWN (2) Hardware is AGGREGATE  ifIndex 4620, MRU 1522  Vlan info :    Switchport mode        : access    Ingress filter         : enable    Acceptable frame types : all    Default Vlan           : 1000    Configured Vlans       : 1000  Interface counter:    input  packets          : 0           bytes            : 0           multicast packets: 0    output packets          : 0           bytes            : 0           multicast packets: 0           broadcast packets: 0 1 Check that the LACP system ID is set to the default value (0x8000). 2 Link down state Set the load balance of [switch A] to the destination/source IP address, and enable the interface. Yamaha(config)#port-channel load-balance src-dst-ip (1) Yamaha(config)#interface po10 (2) Yamaha(config-if)#no shutdown (3) 1 Set the load balance 2 Set logical interface #10 3 Enable the logical interface Set the load balance of [switch B] to the destination/source IP address, and enable the interface. Yamaha(config)#port-channel load-balance src-dst-ip (1) Yamaha(config)#interface po20 (2) Yamaha(config-if)#no shutdown (3) 1 Set the load balance 2 Set logical interface #20 3 Enable the logical interface Confirm the setting status of [switch A] logical interface. Link up and confirm whether frames are being sent and received. Yamaha#show interface po10Interface po10  Link is UP  Hardware is AGGREGATE  ifIndex 4610, MRU 1522  Vlan info :    Switchport mode        : access    Ingress filter         : enable    Acceptable frame types : all    Default Vlan           : 1000    Configured Vlans       : 1000  Interface counter:    input  packets          : 560           bytes            : 58239           multicast packets: 560    output packets          : 98           bytes            : 12474           multicast packets: 98           broadcast packets: 0Yamaha#Yamaha#show lacp-counter% Traffic statisticsPort       LACPDUs         Marker         Pckt err        Sent    Recv    Sent    Recv    Sent    Recv% Aggregator po10 , ID 4610port1.1      50      47      0       0       0       0port1.2      49      46      0       0       0       0port1.3      49      46      0       0       0       0port1.4      49      46      0       0       0       0 Confirm the setting status of [switch B] logical interface. Link up and confirm whether frames are being sent and received. Yamaha#show interface po20Interface po20  Link is UP  Hardware is AGGREGATE  ifIndex 4620, MRU 1522  Vlan info :    Switchport mode        : access    Ingress filter         : enable    Acceptable frame types : all    Default Vlan           : 1000    Configured Vlans       : 1000  Interface counter:    input  packets          : 78           bytes            : 9914           multicast packets: 78    output packets          : 438           bytes            : 45604           multicast packets: 438           broadcast packets: 0Yamaha#Yamaha#show lacp-counter% Traffic statisticsPort       LACPDUs         Marker         Pckt err        Sent    Recv    Sent    Recv    Sent    Recv% Aggregator po20 , ID 4620port1.1      55      57      0       0       0       0port1.2      54      56      0       0       0       0port1.3      54      56      0       0       0       0port1.4      54      56      0       0       0       0</div></div><div id="interface_interface_lag"><div class="search_title" docfname="interface_interface_lag" doctitle="Link" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution a host port that is associated with a private vlan cannot be aggregated as a link aggregation logical interface. if access list settings exist for the received frame of a lan/sfp port, the ports cannot be aggregated as a link aggregation logical interface.</div><div class="display_word">6. Points of Caution A host port that is associated with a private VLAN cannot be aggregated as a link aggregation logical interface. If access list settings exist for the received frame of a LAN/SFP port, the ports cannot be aggregated as a link aggregation logical interface.</div></div><div id="interface_interface_lag"><div class="search_title" docfname="interface_interface_lag" doctitle="Link" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation lan/sfp port control: basic interface settings</div><div class="display_word">7. Related Documentation LAN/SFP Port Control: Basic Interface Settings</div></div><div id="interface_interface_poe"><div class="search_title" docfname="interface_interface_poe" doctitle="PoE" link="#poe制御">PoE Control</div><div class="search_word">poe control</div><div class="display_word">PoE Control</div></div><div id="interface_interface_poe"><div class="search_title" docfname="interface_interface_poe" doctitle="PoE" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview poe (power over ethernet) is a technology that supplies power using an ethernet cable (category 5e or higher). this product complies with ieee 802.3at , which allows the product to supply power to class 4 powered devices. in ieee 802.3at, terms called power supply side (device that supplies power) pse: power sourcing equipment power receiving side (device that receives power): pd: powered device are defined. this product uses alternative a , which uses the signal lines (1, 2, 3, 6) of cables as the power supply method.</div><div class="display_word">1. Function Overview PoE (Power over Ethernet) is a technology that supplies power using an Ethernet cable (category 5e or higher). This product complies with IEEE 802.3at , which allows the product to supply power to Class 4 powered devices. In IEEE 802.3at, terms called Power supply side (device that supplies power) PSE: Power Sourcing Equipment Power receiving side (device that receives power): PD: Powered Device are defined. This product uses Alternative A , which uses the signal lines (1, 2, 3, 6) of cables as the power supply method.</div></div><div id="interface_interface_poe"><div class="search_title" docfname="interface_interface_poe" doctitle="PoE" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used none</div><div class="display_word">2. Definition of Terms Used None</div></div><div id="interface_interface_poe"><div class="search_title" docfname="interface_interface_poe" doctitle="PoE" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="interface_interface_poe"><div class="search_title" docfname="interface_interface_poe" doctitle="PoE" link="#poe-給電機能の有効無効-制御">3.1. PoE power supply function enable/disable control</div><div class="search_word">3.1. poe power supply function enable/disable control ports that support poe power supply of this product (hereinafter referred to as poe ports) are as follows. swx2310p-10g: ports 1 to 8 swx2310p-18g: ports 1 to 16 swx2310p-28gt: ports 1 to 24 this product allows you to enable/disable the power supply function for each port. the power supply function of all the poe ports of this product is enabled as the factory default. if the connected device is a normal ethernet device, the power will not be supplied and the device will operate as a normal ethernet port . this product continues to provide power to pds even if the ports are shut down.</div><div class="display_word">3.1. PoE power supply function enable/disable control Ports that support PoE power supply of this product (hereinafter referred to as PoE ports) are as follows. SWX2310P-10G: ports 1 to 8 SWX2310P-18G: ports 1 to 16 SWX2310P-28GT: ports 1 to 24 This product allows you to enable/disable the power supply function for each port. The power supply function of all the PoE ports of this product is enabled as the factory default. If the connected device is a normal Ethernet device, the power will not be supplied and the device will operate as a normal Ethernet port . This product continues to provide power to PDs even if the ports are shut down.</div></div><div id="interface_interface_poe"><div class="search_title" docfname="interface_interface_poe" doctitle="PoE" link="#給電クラスと同時給電可能なポートの最大数">3.2. Power supply class and maximum number of ports that can be powered simultaneously</div><div class="search_word">3.2. power supply class and maximum number of ports that can be powered simultaneously this product is a power supply device that complies with the poe standards. it can supply up to 30 w of power per port . it automatically detects the connected pd, identifies its power class, and starts the power supply. the following table lists the power classes defined in ieee 802.3at and the guideline for the maximum number of ports that can be simultaneously powered (the number of ports that can be simultaneously connected when each pd consumes power up to its limit). class power of device that receives power (max) power of device that supplies power maximum number of ports that can be powered simultaneously (upper limit of poe power supply) swx2310p-10g(124w) swx2310p-18g(247w) swx2310p-28gt(370w) 0 13.0 w 15.4 w 8 16 24 1 3.84 w 4.0 w 8 16 24 2 6.49 w 7.0 w 8 16 24 3 13.0 w 15.4 w 8 16 24 4 25.5 w 30.0 w 4 (*) 8 (*) 12 (*) (*): depending on the power consumption of the device that receives power, the simultaneous power supply beyond the number of ports listed can be performed.</div><div class="display_word">3.2. Power supply class and maximum number of ports that can be powered simultaneously This product is a power supply device that complies with the PoE standards. It can supply up to 30 W of power per port . It automatically detects the connected PD, identifies its power class, and starts the power supply. The following table lists the power classes defined in IEEE 802.3at and the guideline for the maximum number of ports that can be simultaneously powered (the number of ports that can be simultaneously connected when each PD consumes power up to its limit). Class Power of device that receives power (MAX) Power of device that supplies power Maximum number of ports that can be powered simultaneously (Upper limit of PoE power supply) SWX2310P-10G(124W) SWX2310P-18G(247W) SWX2310P-28GT(370W) 0 13.0 W 15.4 W 8 16 24 1 3.84 W 4.0 W 8 16 24 2 6.49 W 7.0 W 8 16 24 3 13.0 W 15.4 W 8 16 24 4 25.5 W 30.0 W 4 (*) 8 (*) 12 (*) (*): Depending on the power consumption of the device that receives power, the simultaneous power supply beyond the number of ports listed can be performed.</div></div><div id="interface_interface_poe"><div class="search_title" docfname="interface_interface_poe" doctitle="PoE" link="#ガードバンド">3.3. Guard band</div><div class="search_word">3.3. guard band a guardband is a margin set for the maximum power supply to prevent unexpected power outages. if the available power supply amount reaches or falls below the guardband, power supply to a newly connected pd will be suppressed. for example, if the guardband is set to 10 w on the swx2310p-10mt (upper limit of available power supply amount: 124 w), a newly-connected pd is not powered when the total poe supply power of all ports is 114 w or more (when the available power supply amount is 10 w or less). setting this guard band value appropriately can prevent a newly connected pd from stopping the power supply to other pds. this product allows you to set the guardband value within the range of 0 to 30 w , and the value is set to 7 w as the factory default.</div><div class="display_word">3.3. Guard band A guardband is a margin set for the maximum power supply to prevent unexpected power outages. If the available power supply amount reaches or falls below the guardband, power supply to a newly connected PD will be suppressed. For example, if the guardband is set to 10 W on the SWX2310P-10MT (upper limit of available power supply amount: 124 W), a newly-connected PD is not powered when the total PoE supply power of all ports is 114 W or more (when the available power supply amount is 10 W or less). Setting this guard band value appropriately can prevent a newly connected PD from stopping the power supply to other PDs. This product allows you to set the guardband value within the range of 0 to 30 W , and the value is set to 7 W as the factory default.</div></div><div id="interface_interface_poe"><div class="search_title" docfname="interface_interface_poe" doctitle="PoE" link="#給電優先度">3.4. PoE power priority</div><div class="search_word">3.4. poe power priority this product allows you to specify the power supply priority order for each poe port. the priority is critical , high , and low in descending order, and it is set to low for all ports as the factory default. among ports with the same priority setting, the smaller the port number, the higher the priority. the priority goes down in the port number order (1 → 2 → 3…​).</div><div class="display_word">3.4. PoE power priority This product allows you to specify the power supply priority order for each PoE port. The priority is critical , high , and low in descending order, and it is set to low for all ports as the factory default. Among ports with the same priority setting, the smaller the port number, the higher the priority. The priority goes down in the port number order (1 → 2 → 3…​).</div></div><div id="interface_interface_poe"><div class="search_title" docfname="interface_interface_poe" doctitle="PoE" link="#poe給電動作">3.5. PoE power supply actions</div><div class="search_word">3.5. poe power supply actions this product performs the following processes depending on the power consumption. when the total poe supply power of all ports is about to exceed the upper limit of the available poe power supply power supply from poe ports is stopped in the order from the lower priority to ensure that the total poe supply power remains within the upper limit of the available poe power supply. at this time, the mode led status automatically transitions to the status mode, and the speed led of the port to which power supply has been stopped flashes orange. in addition, “portx.x over system power limit” is output to syslog. if the available power supply amount reaches or falls below the guardband power will continue to be supplied to pds that are already being powered. however, power will not be supplied to a newly-connected pd regardless of its poe power priority. at this time, the mode led status automatically transitions to the status mode, and the speed led of the port to which power has not been supplied flashes orange. in addition, “portx.x restricted by guard band” is output to syslog. when the poe supply power of a specific poe port has exceeded the upper limit of the available poe power supply per port power supply to the corresponding poe port will be stopped. power supply to other poe ports will continue. at this time, the mode led status automatically transitions to the status mode, and the speed led of the port to which power supply has been stopped illuminates steady orange. in addition, “portx.x over load” is output to syslog. if the poe supply power is other than the above (within normal range) power supply to pds will continue. at this time, if the mode led status has transitioned to the status mode due to the above factors, the mode led will return to the mode before the automatic transition. in addition, the following processing will be performed if the poe port status or the available power supply amount has changed. when power supply is started “portx.x power on” is output to syslog. when the mode led is in the poe mode, the link led of the port that has started supplying power illuminates steady green. when power supply is stopped “portx.x power off” is output to syslog. when the mode led is in the poe mode, the link led of the port that has stopped supplying power switches off. if the available power supply amount reaches or falls below the guardband “supplying power reached to guard band threshold” is output to syslog. if the available power supply amount recovers from the state on or below the guardband “supplying power fell below guard band threshold” is output to syslog.</div><div class="display_word">3.5. PoE power supply actions This product performs the following processes depending on the power consumption. When the total PoE supply power of all ports is about to exceed the upper limit of the available PoE power supply Power supply from PoE ports is stopped in the order from the lower priority to ensure that the total PoE supply power remains within the upper limit of the available PoE power supply. At this time, the MODE LED status automatically transitions to the STATUS mode, and the SPEED LED of the port to which power supply has been stopped flashes orange. In addition, “portX.X over system power limit” is output to SYSLOG. If the available power supply amount reaches or falls below the guardband Power will continue to be supplied to PDs that are already being powered. However, power will not be supplied to a newly-connected PD regardless of its PoE power priority. At this time, the MODE LED status automatically transitions to the STATUS mode, and the SPEED LED of the port to which power has not been supplied flashes orange. In addition, “portX.X restricted by guard band” is output to SYSLOG. When the PoE supply power of a specific PoE port has exceeded the upper limit of the available PoE power supply per port Power supply to the corresponding PoE port will be stopped. Power supply to other PoE ports will continue. At this time, the MODE LED status automatically transitions to the STATUS mode, and the SPEED LED of the port to which power supply has been stopped illuminates steady orange. In addition, “portX.X over load” is output to SYSLOG. If the PoE supply power is other than the above (within normal range) Power supply to PDs will continue. At this time, if the MODE LED status has transitioned to the STATUS mode due to the above factors, the MODE LED will return to the MODE before the automatic transition. In addition, the following processing will be performed if the PoE port status or the available power supply amount has changed. When power supply is started “portX.X power on” is output to SYSLOG. When the MODE LED is in the PoE mode, the LINK LED of the port that has started supplying power illuminates steady green. When power supply is stopped “portX.X power off” is output to SYSLOG. When the MODE LED is in the PoE mode, the LINK LED of the port that has stopped supplying power switches off. If the available power supply amount reaches or falls below the guardband “Supplying power reached to guard band threshold” is output to SYSLOG. If the available power supply amount recovers from the state on or below the guardband “Supplying power fell below guard band threshold” is output to SYSLOG.</div></div><div id="interface_interface_poe"><div class="search_title" docfname="interface_interface_poe" doctitle="PoE" link="#lldp-による給電設定">3.6. Power supply setting by LLDP</div><div class="search_word">3.6. power supply setting by lldp when the product receives an lldp frame containing the power via mdi tlv from a pd, it automatically changes the power supply action of the poe port according to the received frame setting value. this function only works on poe ports that can receive lldp frames. the power via mdi tlvs and the corresponding actions to be changed are as shown below. power via mdi tlv (ieee802.3) action to be changed power priority poe power priority pd requested power value upper limit of available power supply amount per port</div><div class="display_word">3.6. Power supply setting by LLDP When the product receives an LLDP frame containing the Power via MDI TLV from a PD, it automatically changes the power supply action of the PoE port according to the received frame setting value. This function only works on PoE ports that can receive LLDP frames. The Power via MDI TLVs and the corresponding actions to be changed are as shown below. Power via MDI TLV (IEEE802.3) Action to be changed Power priority PoE power priority PD requested power value Upper limit of available power supply amount per port</div></div><div id="interface_interface_poe"><div class="search_title" docfname="interface_interface_poe" doctitle="PoE" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands set the poe power supply function for the entire system power-inline set the poe power supply function on an interface basis power-inline set the description text for poe ports power-inline description set the poe port priority power-inline priority set a guard band power-inline guardband show poe power supply information show power-inline</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Set the PoE power supply function for the entire system power-inline Set the PoE power supply function on an interface basis power-inline Set the description text for PoE ports power-inline description Set the PoE port priority power-inline priority Set a guard band power-inline guardband Show PoE power supply information show power-inline</div></div><div id="interface_interface_poe"><div class="search_title" docfname="interface_interface_poe" doctitle="PoE" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="interface_interface_poe"><div class="search_title" docfname="interface_interface_poe" doctitle="PoE" link="#poeポートの給電設定">6. PoE Port Power Supply Settings</div><div class="search_word">6. poe port power supply settings specify the settings for the power supply function of port1.8. yamaha(config)#power-inline enable (1) yamaha(config)#interface port1.8yamaha(config-if)#power-inline description "ap1" (2) yamaha(config-if)#power-inline priorty critical (3) yamaha(config-if)#power-inline enable (4) yamaha(config-if)#exityamaha(config)#exit 1 enable the poe supply function for the entire system. * not required if the default settings are used 2 set “ap1” as the poe port description 3 set the priority of the poe port to the highest (critical) 4 enable the poe supply function for the interface. * not required if the default settings are used</div><div class="display_word">6. PoE Port Power Supply Settings Specify the settings for the power supply function of port1.8. Yamaha(config)#power-inline enable (1) Yamaha(config)#interface port1.8Yamaha(config-if)#power-inline description "AP1" (2) Yamaha(config-if)#power-inline priorty critical (3) Yamaha(config-if)#power-inline enable (4) Yamaha(config-if)#exitYamaha(config)#exit 1 Enable the PoE supply function for the entire system. * Not required if the default settings are used 2 Set “AP1” as the PoE port description 3 Set the priority of the PoE port to the highest (critical) 4 Enable the PoE supply function for the interface. * Not required if the default settings are used</div></div><div id="interface_interface_poe"><div class="search_title" docfname="interface_interface_poe" doctitle="PoE" link="#注意事項">7. Points of Caution</div><div class="search_word">7. points of caution none</div><div class="display_word">7. Points of Caution None</div></div><div id="interface_interface_poe"><div class="search_title" docfname="interface_interface_poe" doctitle="PoE" link="#関連文書">8. Related Documentation</div><div class="search_word">8. related documentation led control lldp syslog</div><div class="display_word">8. Related Documentation LED Control LLDP SYSLOG</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#ポート認証機能">Port Authentication Function</div><div class="search_word">port authentication function</div><div class="display_word">Port Authentication Function</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview port authentication is a function that authenticates devices or users. this authenticates a device connected to the lan/sfp port, and permits lan access only for devices that succeeded in authenticating. devices that are not yet authenticated or that failed to authenticate can be denied access to the lan, or permitted to access only a specific vlan.</div><div class="display_word">1. Function Overview Port authentication is a function that authenticates devices or users. This authenticates a device connected to the LAN/SFP port, and permits LAN access only for devices that succeeded in authenticating. Devices that are not yet authenticated or that failed to authenticate can be denied access to the LAN, or permitted to access only a specific VLAN.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used ieee 802.1x the authentication standard used when connecting to the lan. authenticator a device or software that authenticates a supplicant connected to a lan/sfp port. it mediates between the supplicant and the authentication server, controlling access to the lan according to the success or failure of authentication. supplicant a device or software that connects to an authenticator and receives authentication. authentication server a device or software that authenticates a supplicant that is connected via the authenticator. this manages authentication information such as user names, passwords, mac addresses, and associated vlans. eap (extended authentication protocol) this is an authentication protocol that extends ppp, allowing various authentication methods to be used. this is defined in rfc3748. eap over lan (eapol) this is a protocol for conveying eap packets between the supplicant and the authenticator. eap over radius this is a protocol for conveying eap packets between the authenticator and the authentication server (radius server). eap-md5 (message digest algorithm 5) client authentication using user name and password. this uses an md5 hash value to authenticate. eap-tls (transport layer security) this uses the digital certificates of the server and the client to authenticate. with the transport layer encrypted, the digital certificates are exchanged and authenticated. this is defined in rfc2716 and rfc5216. eap-ttls (tunneled tls) this is an extended version of eap-tls. this uses the digital certificate of the server to establish a tls communication route, and within this encrypted communication route uses a password to authenticate the client. this is defined in rfc5281. eap-peap (protected eap) the principle of operation is equivalent to eap-ttls (the only difference is the protocol inside the encrypted tunnel). this uses the digital certificate of the server to establish a tls communication route, and within this encrypted communication route uses a password to authenticate the client.</div><div class="display_word">2. Definition of Terms Used IEEE 802.1X The authentication standard used when connecting to the LAN. Authenticator A device or software that authenticates a supplicant connected to a LAN/SFP port. It mediates between the supplicant and the authentication server, controlling access to the LAN according to the success or failure of authentication. Supplicant A device or software that connects to an authenticator and receives authentication. Authentication server A device or software that authenticates a supplicant that is connected via the authenticator. This manages authentication information such as user names, passwords, MAC addresses, and associated VLANs. EAP (Extended authentication protocol) This is an authentication protocol that extends PPP, allowing various authentication methods to be used. This is defined in RFC3748. EAP over LAN (EAPOL) This is a protocol for conveying EAP packets between the supplicant and the authenticator. EAP over Radius This is a protocol for conveying EAP packets between the authenticator and the authentication server (RADIUS server). EAP-MD5 (Message digest algorithm 5) Client authentication using user name and password. This uses an MD5 hash value to authenticate. EAP-TLS (Transport Layer Security) This uses the digital certificates of the server and the client to authenticate. With the transport layer encrypted, the digital certificates are exchanged and authenticated. This is defined in RFC2716 and RFC5216. EAP-TTLS (Tunneled TLS) This is an extended version of EAP-TLS. This uses the digital certificate of the server to establish a TLS communication route, and within this encrypted communication route uses a password to authenticate the client. This is defined in RFC5281. EAP-PEAP (Protected EAP) The principle of operation is equivalent to EAP-TTLS (the only difference is the protocol inside the encrypted tunnel). This uses the digital certificate of the server to establish a TLS communication route, and within this encrypted communication route uses a password to authenticate the client.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details the operating specifications for port authentication are shown below. as port authentication functions, this product supports ieee 802.1x authentication, mac authentication, and web authentication. the following table shows the distinctive features of each authentication method. mac authentication ieee 802.1x authentication web authentication authenticated element mac address user name and password (eap-md5, eap-ttls, eap-peap) user name and password authenticated object (supplicant) device device or user device or user functions needed by supplicant none ieee 802.1x authentication function web browser operation when authenticating none user name and password entry (eap-md5, eap-ttls, eap-peap) user name and password entry this product assumes a radius server as the authentication server. note that the port authentication function of this product has the following limitations. the number of supplicants that can be authenticated is one for each port in single host mode or multi host mode; for multi supplicant mode, the maximum is 512 for the entire system. it cannot be used on a private vlan port. it cannot be used on a voice vlan port. if port authentication is enabled, a spanning tree topology change will occur according to the authentication result. if you want to avoid this, specify “spanning-tree edgeport” for the authentication port to which the supplicant will be connected. web authentication can be used only in the multi supplicant mode. web authentication cannot be used together with a guest vlan. when using the stack function, a file saved on the main switch is referenced as the web authentication screen customization file. when using the stack function, if a member switch is added, the authentication information of the supplicant connected to the logical interface is cleared. when using the stack function, if the main switch is demoted to a member switch status, authentication information is cleared from connected supplicants. trunk ports can only be used in the multi supplicant mode. trunk ports cannot use dynamic or guest vlans. if you also use the l2ms function on a trunk port, you must set the native vlan to be provided. if the following supplicant vlan is changed by a dynamic vlan, then the authentication function may not work properly. dhcp server l2ms compatible device</div><div class="display_word">3. Function Details The operating specifications for port authentication are shown below. As port authentication functions, this product supports IEEE 802.1X authentication, MAC authentication, and Web authentication. The following table shows the distinctive features of each authentication method. MAC authentication IEEE 802.1X authentication Web authentication Authenticated element MAC address User name and password (EAP-MD5, EAP-TTLS, EAP-PEAP) User name and password Authenticated object (supplicant) Device Device or user Device or user Functions needed by supplicant None IEEE 802.1X authentication function Web browser Operation when authenticating None User name and password entry (EAP-MD5, EAP-TTLS, EAP-PEAP) User name and password entry This product assumes a RADIUS server as the authentication server. Note that the port authentication function of this product has the following limitations. The number of supplicants that can be authenticated is one for each port in single host mode or multi host mode; for multi supplicant mode, the maximum is 512 for the entire system. It cannot be used on a private VLAN port. It cannot be used on a voice VLAN port. If port authentication is enabled, a spanning tree topology change will occur according to the authentication result. If you want to avoid this, specify “spanning-tree edgeport” for the authentication port to which the supplicant will be connected. Web authentication can be used only in the multi supplicant mode. Web authentication cannot be used together with a guest VLAN. When using the stack function, a file saved on the main switch is referenced as the Web Authentication screen customization file. When using the stack function, if a member switch is added, the authentication information of the supplicant connected to the logical interface is cleared. When using the stack function, if the main switch is demoted to a member switch status, authentication information is cleared from connected supplicants. Trunk ports can only be used in the multi supplicant mode. Trunk ports cannot use dynamic or guest VLANs. If you also use the L2MS function on a trunk port, you must set the native VLAN to be provided. If the following supplicant VLAN is changed by a dynamic VLAN, then the authentication function may not work properly. DHCP server L2MS compatible device</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#ieee-8021x認証">3.1. IEEE 802.1X authentication</div><div class="search_word">3.1. ieee 802.1x authentication ieee 802.1x authentication uses eap to authenticate in units of devices or users. the supplicant receiving authentication must support ieee 802.1x authentication. this product operates as an authenticator that communicates with the supplicant via eap over lan and communicates with the radius server via eap over radius. the authentication process itself occurs directly between the supplicant and the radius server. as authentication methods, this product supports eap-md5, eap-tls, eap-ttls, and eap-peap. the features of each authentication method are shown in the following table. client authentication method server authentication method ease of implementation degree of safety eap-md5 user name and password entry no authentication easy low eap-tls client certificate server certificate complex high eap-ttls user name and password entry server certificate medium medium eap-peap user name and password entry server certificate medium medium make settings for the supplicant and the radius server as appropriate for the authentication method you use. the basic procedure for ieee 802.1x authentication is shown in the following diagram. the supplicant is connected to the lan, and transmits a communication start message (eapol-start) message to start authentication. when authentication succeeds, authentication success (success) notification is sent to the supplicant, and the supplicant’s mac address is registered in the fdb, permitting the supplicant to access the network. if authentication fails, an authentication failure (failure) notification is sent to the supplicant, and network access is denied for the supplicant. (even without authentication, it is possible to permit access to a specific vlan if a guest vlan has been specified.)</div><div class="display_word">3.1. IEEE 802.1X authentication IEEE 802.1X authentication uses EAP to authenticate in units of devices or users. The supplicant receiving authentication must support IEEE 802.1X authentication. This product operates as an authenticator that communicates with the supplicant via EAP over LAN and communicates with the RADIUS server via EAP over RADIUS. The authentication process itself occurs directly between the supplicant and the RADIUS server. As authentication methods, this product supports EAP-MD5, EAP-TLS, EAP-TTLS, and EAP-PEAP. The features of each authentication method are shown in the following table. Client authentication method Server authentication method Ease of implementation Degree of safety EAP-MD5 User name and password entry No authentication Easy Low EAP-TLS Client certificate Server certificate Complex High EAP-TTLS User name and password entry Server certificate Medium Medium EAP-PEAP User name and password entry Server certificate Medium Medium Make settings for the supplicant and the RADIUS server as appropriate for the authentication method you use. The basic procedure for IEEE 802.1X authentication is shown in the following diagram. The supplicant is connected to the LAN, and transmits a communication start message (EAPOL-Start) message to start authentication. When authentication succeeds, authentication success (Success) notification is sent to the supplicant, and the supplicant’s MAC address is registered in the FDB, permitting the supplicant to access the network. If authentication fails, an authentication failure (Failure) notification is sent to the supplicant, and network access is denied for the supplicant. (Even without authentication, it is possible to permit access to a specific VLAN if a guest VLAN has been specified.)</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#mac認証">3.2. MAC authentication</div><div class="search_word">3.2. mac authentication mac authentication uses the mac address of a device to authenticate an individual device. since the supplicant does not need any special function to be authenticated, authentication is possible even for devices that do not support ieee 802.1x. the basic procedure for mac authentication is shown in the following diagram. when this product receives any ethernet frame from the supplicant, it queries the radius server with the supplicant’s mac address as the user name and password. eap-md5 is used as the authentication mode between this product and the radius server. when authentication succeeds, the supplicant’s mac address is registered in the fdb, permitting the supplicant to access the network. however, it can be registered as a static entry by specifying mac authenticated static registration (using the auth-mac static command). if authentication fails, the supplicant is denied network access. (even without authentication, it is possible to permit access to a specific vlan if a guest vlan has been specified.) the supplicant’s mac address must be registered as the user name and password in the radius server, in one of the following formats. xx-xx-xx-xx-xx-xx (hyphen delimited) xx:xx:xx:xx:xx:xx (colon delimited) xxxxxxxxxxxx (not delimited) this product lets you use the auth-mac auth-user command to change the format of the mac address query that is made to the radius server. specify the appropriate command according to the format of the mac addresses that are registered in the radius server.</div><div class="display_word">3.2. MAC authentication MAC authentication uses the MAC address of a device to authenticate an individual device. Since the supplicant does not need any special function to be authenticated, authentication is possible even for devices that do not support IEEE 802.1X. The basic procedure for MAC authentication is shown in the following diagram. When this product receives any Ethernet frame from the supplicant, it queries the RADIUS server with the supplicant’s MAC address as the user name and password. EAP-MD5 is used as the authentication mode between this product and the RADIUS server. When authentication succeeds, the supplicant’s MAC address is registered in the FDB, permitting the supplicant to access the network. However, it can be registered as a static entry by specifying MAC authenticated static registration (using the auth-mac static command). If authentication fails, the supplicant is denied network access. (Even without authentication, it is possible to permit access to a specific VLAN if a guest VLAN has been specified.) The supplicant’s MAC address must be registered as the user name and password in the RADIUS server, in one of the following formats. XX-XX-XX-XX-XX-XX (hyphen delimited) XX:XX:XX:XX:XX:XX (colon delimited) XXXXXXXXXXXX (not delimited) This product lets you use the auth-mac auth-user command to change the format of the MAC address query that is made to the RADIUS server. Specify the appropriate command according to the format of the MAC addresses that are registered in the RADIUS server.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#web認証">3.3. Web authentication</div><div class="search_word">3.3. web authentication web authentication is a function that authenticates a user when a user name and password are entered from the supplicant’s web browser. http is supported as the communication method between the web browser and the network switch. because web authentication performs authentication by communicating via http, it is necessary for ip communication between this product and the supplicant to be possible even before authentication. either the dhcp server must assign an ip address to the supplicant, or the supplicant must specify an ip address statically. web authentication operates only in the multi supplicant mode. also, this cannot be used together with a guest vlan. the basic procedure for web authentication is shown in the following diagram. this product queries the radius server using the user name and password that were entered in the supplicant’s web browser. eap-md5 is used as the authentication mode between this product and the radius server. when authentication succeeds, the supplicant’s mac address is registered in the fdb, permitting the supplicant to access the network. if authentication fails, the supplicant is denied network access.</div><div class="display_word">3.3. Web authentication Web authentication is a function that authenticates a user when a user name and password are entered from the supplicant’s web browser. HTTP is supported as the communication method between the web browser and the network switch. Because web authentication performs authentication by communicating via HTTP, it is necessary for IP communication between this product and the supplicant to be possible even before authentication. Either the DHCP server must assign an IP address to the supplicant, or the supplicant must specify an IP address statically. Web authentication operates only in the multi supplicant mode. Also, this cannot be used together with a guest VLAN. The basic procedure for web authentication is shown in the following diagram. This product queries the RADIUS server using the user name and password that were entered in the supplicant’s web browser. EAP-MD5 is used as the authentication mode between this product and the RADIUS server. When authentication succeeds, the supplicant’s MAC address is registered in the FDB, permitting the supplicant to access the network. If authentication fails, the supplicant is denied network access.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#サプリカント側の操作">3.3.1. Operations on the supplicant</div><div class="search_word">3.3.1. operations on the supplicant when the supplicant’s web browser accesses ipv4 tcp port 80, the following authentication screen appears. + image::web-auth-default.png[image,width=700, role=th] to be authenticated, enter a user name and password, and click the [login] button. the supplicant’s mac address is registered in the fdb, permitting the supplicant to access the network. if authentication fails three times in succession, authentication is temporarily restricted.</div><div class="display_word">3.3.1. Operations on the supplicant When the supplicant’s web browser accesses IPv4 TCP port 80, the following authentication screen appears. + image::web-auth-default.png[image,width=700, role=th] To be authenticated, enter a user name and password, and click the [Login] button. The supplicant’s MAC address is registered in the FDB, permitting the supplicant to access the network. If authentication fails three times in succession, authentication is temporarily restricted.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#認証画面のカスタマイズ">3.3.2. Customizing the authentication screen</div><div class="search_word">3.3.2. customizing the authentication screen the displayed content on the web authentication screen (the edited html, css and image files) can be copied to this product, and the following parts can be customized. note that we cannot provide support for how to code in html/css or what formatting to use, or for any troubles that may occur due to modifications to the code. header the header section includes the “header.html” and “style.css” files. edit these files and copy them to this product in order to customize them. image file copy the image provided to this product in order to modify it. input form the display style used for the input form is defined in the “style.css” file. although the text cannot be changed, you can edit the “style.css” file and copy it to this product in order to change the input form’s design. footer the footer section includes the “footer.html” and “style.css” files. edit these files and copy them to this product in order to customize them. the following explains how to modify the web authentication screen.</div><div class="display_word">3.3.2. Customizing the authentication screen The displayed content on the Web authentication screen (the edited HTML, CSS and image files) can be copied to this product, and the following parts can be customized. Note that we cannot provide support for how to code in HTML/CSS or what formatting to use, or for any troubles that may occur due to modifications to the code. Header The header section includes the “header.html” and “style.css” files. Edit these files and copy them to this product in order to customize them. Image file Copy the image provided to this product in order to modify it. Input form The display style used for the input form is defined in the “style.css” file. Although the text cannot be changed, you can edit the “style.css” file and copy it to this product in order to change the input form’s design. Footer The footer section includes the “footer.html” and “style.css” files. Edit these files and copy them to this product in order to customize them. The following explains how to modify the Web authentication screen.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#認証画面カスタマイズ用ファイルの準備">3.3.2.1. Preparing the authentication screen customization files</div><div class="search_word">3.3.2.1. preparing the authentication screen customization files the following files are used to customize the web authentication screen. header.html footer.html logo.png style.css use the web browser to access the “header.html”, “footer.html” and “style.css” files from the network switch. for example if the ip address of the network switch is 192.168.100.240, you can use the following url to access the file from a pc connected to a port on which web authentication is enabled, and then use the browser’s “save as” command to save the file on the pc. http://192.168.100.240/web-auth/header.html http://192.168.100.240/web-auth/footer.html http://192.168.100.240/web-auth/style.css save files with an “.html” or “.css” extension and with utf-8 character encoding specified. for the image file logo.png, prepare a desired image file on the pc, and save it with the file name logo.png. the maximum file size is 1 mb.</div><div class="display_word">3.3.2.1. Preparing the authentication screen customization files The following files are used to customize the Web authentication screen. header.html footer.html logo.png style.css Use the Web browser to access the “header.html”, “footer.html” and “style.css” files from the network switch. For example if the IP address of the network switch is 192.168.100.240, you can use the following URL to access the file from a PC connected to a port on which Web authentication is enabled, and then use the browser’s “Save as” command to save the file on the PC. http://192.168.100.240/web-auth/header.html http://192.168.100.240/web-auth/footer.html http://192.168.100.240/web-auth/style.css Save files with an “.html” or “.css” extension and with UTF-8 character encoding specified. For the image file logo.png, prepare a desired image file on the PC, and save it with the file name logo.png. The maximum file size is 1 MB.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#認証画面カスタマイズ用ファイルの編集">3.3.2.2. Editing the authentication screen customization files</div><div class="search_word">3.3.2.2. editing the authentication screen customization files edit the above-mentioned html and css files as appropriate on your pc. you are free to edit each file in accordance with html and css specifications, but please note the following points. the only image file that can be referenced from the “header.html” and “footer.html” files is “logo.png”. the extension of the html/css file must be “.html” or “.css” and the character encoding must be consistent with utf-8.</div><div class="display_word">3.3.2.2. Editing the authentication screen customization files Edit the above-mentioned HTML and CSS files as appropriate on your PC. You are free to edit each file in accordance with HTML and CSS specifications, but please note the following points. The only image file that can be referenced from the “header.html” and “footer.html” files is “logo.png”. The extension of the HTML/CSS file must be “.html” or “.css” and the character encoding must be consistent with UTF-8.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#認証画面カスタマイズ用ファイルの設置">3.3.2.3. Placing the authentication screen customization files</div><div class="search_word">3.3.2.3. placing the authentication screen customization files when you have prepared the files, place them in /model name/startup-config/web-auth/ on the sd card. after placing the files, use the copy auth-web custom-file command or the copy startup-config command to copy the authentication screen customization files to the network switch. if the following files exist in the folder hierarchy in which the currently-running config is saved, they are used to generate the web authentication screen. you can determine the currently-running config number by using the show environment command. even if the network switch started up using the config on the sd card, you can customize the web authentication screen by placing these files in /model name/startup-config/web-auth/ on the sd card. header.html this is used as the header section referenced from the authentication screen. if this file does not exist, the original “header.html” is used. footer.html this is used as the footer section referenced from the authentication screen. if this file does not exist, the original “footer.html” is used. logo.png this is used as the logo in the upper left of the authentication screen. if this file does not exist, the original yamaha logo is shown. style.css this is used as the “style.css” referenced from the authentication screen. if this file does not exist, the original style.css is used. when you have finished placing the edited files, check the display by using your browser to access the web authentication screen. if you need to make additional changes, edit the files on your pc, and transfer them again.</div><div class="display_word">3.3.2.3. Placing the authentication screen customization files When you have prepared the files, place them in /model name/startup-config/web-auth/ on the SD card. After placing the files, use the copy auth-web custom-file command or the copy startup-config command to copy the authentication screen customization files to the network switch. If the following files exist in the folder hierarchy in which the currently-running CONFIG is saved, they are used to generate the Web authentication screen. You can determine the currently-running CONFIG number by using the show environment command. Even if the network switch started up using the CONFIG on the SD card, you can customize the Web authentication screen by placing these files in /model name/startup-config/web-auth/ on the SD card. header.html This is used as the header section referenced from the authentication screen. If this file does not exist, the original “header.html” is used. footer.html This is used as the footer section referenced from the authentication screen. If this file does not exist, the original “footer.html” is used. logo.png This is used as the logo in the upper left of the authentication screen. If this file does not exist, the original Yamaha logo is shown. style.css This is used as the “style.css” referenced from the authentication screen. If this file does not exist, the original style.css is used. When you have finished placing the edited files, check the display by using your browser to access the Web authentication screen. If you need to make additional changes, edit the files on your PC, and transfer them again.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#カスタマイズのとりやめ">3.3.2.4. Canceling customization</div><div class="search_word">3.3.2.4. canceling customization if you decide to cancel customization of the authentication screen, delete the customization files from the folder in which the currently-running config is saved. you will revert to the original authentication screen. to delete the files, you can use the erase auth-web custom-file command or the erase startup-config command. however, since the erase startup-config command also deletes files such as config.txt, you should first copy files such as config.txt to an sd card etc. as a backup.</div><div class="display_word">3.3.2.4. Canceling customization If you decide to cancel customization of the authentication screen, delete the customization files from the folder in which the currently-running CONFIG is saved. You will revert to the original authentication screen. To delete the files, you can use the erase auth-web custom-file command or the erase startup-config command. However, since the erase startup-config command also deletes files such as config.txt, you should first copy files such as config.txt to an SD card etc. as a backup.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#認証機能の併用">3.4. Using multiple authentication functions</div><div class="search_word">3.4. using multiple authentication functions this product allows using a combination of ieee 802.1x authentication, mac authentication, and/or web authentication at the same port. when network switches are used in combination, each switch is successively authenticated in the authentication order specified using the auth order command. with default settings, ieee 802.1x authentication is prioritized. for web authentication, network switches are authenticated by entering an id and password in the web authentication screen, where the authentication method is changed to web authentication. if multiple authentication methods are used simultaneously, basic operations are as follows. if both ieee 802.1x authentication and mac authentication are used, with ieee 802.1x authentication prioritized if both ieee 802.1x authentication and mac authentication are used, with mac authentication prioritized if both web authentication and ieee 802.1x/mac authentication are used note if authentication succeeds with any one of the methods, authentication has succeeded. if the reauthentication setting is enabled, then reauthentication is performed using the method with which authentication succeeded. if multiple authentication methods are used, forwarding control settings received via an unauthenticated port will be discarded. if both ieee 802.1x authentication and mac authentication are being used and an eapol start signal is received from an unauthenticated supplicant, authentication will switch to ieee 802.1x authentication even if mac authentication is already in progress. if both ieee 802.1x authentication and mac authentication are being used, even if the first authentication method fails, authentication will switch to the next authentication method without entering the restriction period. if both ieee 802.1x authentication and mac authentication are being used and any ethernet frame is received from a supplicant, the product transmits an eap request. if web authentication is also being used, unauthenticated supplicants are registered in fdb as static/discard.</div><div class="display_word">3.4. Using multiple authentication functions This product allows using a combination of IEEE 802.1X authentication, MAC authentication, and/or Web authentication at the same port. When network switches are used in combination, each switch is successively authenticated in the authentication order specified using the auth order command. With default settings, IEEE 802.1X authentication is prioritized. For web authentication, network switches are authenticated by entering an ID and password in the Web Authentication screen, where the authentication method is changed to web authentication. If multiple authentication methods are used simultaneously, basic operations are as follows. If both IEEE 802.1X authentication and MAC authentication are used, with IEEE 802.1X authentication prioritized If both IEEE 802.1X authentication and MAC authentication are used, with MAC authentication prioritized If both web authentication and IEEE 802.1X/MAC authentication are used note If authentication succeeds with any one of the methods, authentication has succeeded. If the reauthentication setting is enabled, then reauthentication is performed using the method with which authentication succeeded. If multiple authentication methods are used, forwarding control settings received via an unauthenticated port will be discarded. If both IEEE 802.1X authentication and MAC authentication are being used and an EAPOL start signal is received from an unauthenticated supplicant, authentication will switch to IEEE 802.1X authentication even if MAC authentication is already in progress. If both IEEE 802.1X authentication and MAC authentication are being used, even if the first authentication method fails, authentication will switch to the next authentication method without entering the restriction period. If both IEEE 802.1X authentication and MAC authentication are being used and any Ethernet frame is received from a supplicant, the product transmits an EAP request. If Web authentication is also being used, unauthenticated supplicants are registered in FDB as static/discard.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#ホストモード">3.5. Host mode</div><div class="search_word">3.5. host mode this product lets you select the host mode for the port authentication function. host mode indicates how an applicable supplicant’s communication will be permitted on the authentication port. this product lets you choose from the following host modes. single host mode this mode permits communication for only one supplicant for each lan/sfp port. communication is permitted only for the first supplicant that successfully authenticates. multi host mode this mode permits communication for multiple supplicants for each lan/sfp port. when a supplicant successfully authenticates and communication is permitted, another supplicant that is connected to the same lan/sfp port and that successfully authenticates is also permitted to communicate on the same vlan. multi supplicant mode this mode permits communication for multiple supplicants for each lan/sfp port. each supplicant is distinguished by its mac address, permitting communication in units of supplicants. when using dynamic vlan functions, you can specify the vlan for each supplicant.</div><div class="display_word">3.5. Host mode This product lets you select the host mode for the port authentication function. Host mode indicates how an applicable supplicant’s communication will be permitted on the authentication port. This product lets you choose from the following host modes. Single host mode This mode permits communication for only one supplicant for each LAN/SFP port. Communication is permitted only for the first supplicant that successfully authenticates. Multi host mode This mode permits communication for multiple supplicants for each LAN/SFP port. When a supplicant successfully authenticates and communication is permitted, another supplicant that is connected to the same LAN/SFP port and that successfully authenticates is also permitted to communicate on the same VLAN. Multi supplicant mode This mode permits communication for multiple supplicants for each LAN/SFP port. Each supplicant is distinguished by its MAC address, permitting communication in units of supplicants. When using dynamic VLAN functions, you can specify the VLAN for each supplicant.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#ダイナミックvlan">3.6. Dynamic VLAN</div><div class="search_word">3.6. dynamic vlan this product supports dynamic vlans using ieee 802.1x, mac, or web authentication. dynamic vlan is a function that changes the authentication port’s associated vlan according to the vlan attribute values in authentication information in notifications received from the radius server. as shown in the illustration above, if a port’s associated vlan is 1, and the received authentication data has a vlan attribute of 10, then following successful authentication, the authentication port’s associated vlan is 10, and communication on vlan 10 is permitted. for the radius server, make settings so that the authentication information sent from the server includes the following attribute values. tunnel-type = vlan (13) tunnel-medium-type = ieee-802 (6) tunnel-private-group-id = vlan id if a dynamic vlan is used, the following actions will occur in respective host modes. single host mode the authentication port’s associated vlan is changed according to the vlan attribute value of the supplicant that successfully authenticates. multi host mode the authentication port’s associated vlan is changed according to the vlan attribute value of the supplicant that successfully authenticates. other supplicants that are connected to the same port are also permitted to communicate on the same vlan. multi supplicant mode the authentication port’s associated vlan is changed according to the vlan attribute value of the supplicant that successfully authenticates. you can specify the vlan for each supplicant.</div><div class="display_word">3.6. Dynamic VLAN This product supports dynamic VLANs using IEEE 802.1X, MAC, or Web authentication. Dynamic VLAN is a function that changes the authentication port’s associated VLAN according to the VLAN attribute values in authentication information in notifications received from the RADIUS server. As shown in the illustration above, if a port’s associated VLAN is 1, and the received authentication data has a VLAN attribute of 10, then following successful authentication, the authentication port’s associated VLAN is 10, and communication on VLAN 10 is permitted. For the RADIUS server, make settings so that the authentication information sent from the server includes the following attribute values. Tunnel-Type = VLAN (13) Tunnel-Medium-Type = IEEE-802 (6) Tunnel-Private-Group-ID = VLAN ID If a dynamic VLAN is used, the following actions will occur in respective host modes. Single host mode The authentication port’s associated VLAN is changed according to the VLAN attribute value of the supplicant that successfully authenticates. Multi host mode The authentication port’s associated VLAN is changed according to the VLAN attribute value of the supplicant that successfully authenticates. Other supplicants that are connected to the same port are also permitted to communicate on the same VLAN. Multi supplicant mode The authentication port’s associated VLAN is changed according to the VLAN attribute value of the supplicant that successfully authenticates. You can specify the VLAN for each supplicant.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#未認証認証失敗ポートのvlan">3.7. VLAN for unauthenticated or failed-authentication ports</div><div class="search_word">3.7. vlan for unauthenticated or failed-authentication ports this product’s ieee 802.1x authentication and mac authentication allow you to specify a guest vlan so that unauthenticated ports or ports that failed authentication will be assigned to a specific vlan. in the multi supplicant mode, you can specify this for each supplicant. this is useful when you want to partially provide functions on a limited network even to a supplicant that has not succeeded in authenticating, as shown in the illustration above.</div><div class="display_word">3.7. VLAN for unauthenticated or failed-authentication ports This product’s IEEE 802.1X authentication and MAC authentication allow you to specify a guest VLAN so that unauthenticated ports or ports that failed authentication will be assigned to a specific VLAN. In the multi supplicant mode, you can specify this for each supplicant. This is useful when you want to partially provide functions on a limited network even to a supplicant that has not succeeded in authenticating, as shown in the illustration above.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#eapパススルー機能">3.8. EAP pass-through function</div><div class="search_word">3.8. eap pass-through function you can switch between enable and disable for eap pass-through and configure whether eapol frames are to be forwarded. the authentication function will be prioritized for interfaces on which the 802.1x authentication function is enabled, and eap pass-through will not be applied.</div><div class="display_word">3.8. EAP pass-through function You can switch between enable and disable for EAP pass-through and configure whether EAPOL frames are to be forwarded. The authentication function will be prioritized for interfaces on which the 802.1X authentication function is enabled, and EAP pass-through will not be applied.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#radiusサーバーに通知する属性値">3.9. Attribute values sent to the RADIUS server</div><div class="search_word">3.9. attribute values sent to the radius server the nas-identifier attribute value can be notified to the radius server. the character string set with the auth radius attribute nas-identifier command is sent to the radius server as the nas-identifier attribute value.</div><div class="display_word">3.9. Attribute values sent to the RADIUS server The NAS-Identifier attribute value can be notified to the RADIUS server. The character string set with the auth radius attribute nas-identifier command is sent to the RADIUS server as the NAS-Identifier attribute value.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands set ieee 802.1x authentication function for the entire system aaa authentication dot1x set mac authentication function for the entire system aaa authentication auth-mac set web authentication function for the entire system aaa authentication auth-web set ieee 802.1x authentication function operating mode dot1x port-control set unauthenticated port forwarding control for ieee 802.1x authentication dot1x control-direction set number of retransmitted eapol packets dot1x max-auth-req set mac authentication function auth-mac enable set mac address format setting for mac authentication auth-mac auth-user mac authenticated static registration setting auth-mac static set web authentication function auth-web enable set redirect-destination url following successful web authentication auth-web redirect-url copy web authentication screen customization files copy auth-web custom-file delete web authentication screen customization files erase auth-web custom-file set host mode auth host-mode authentication order setting auth order set reauthentication auth reauthentication set dynamic vlan auth dynamic-vlan-creation set guest vlan auth guest-vlan set restriction period following failed authentication auth timeout quiet-period set re-authentication interval auth timeout reauth-period set response wait time for the entire radius server auth timeout server-timeout set response wait time for the supplicant auth timeout supp-timeout set radius server host radius-server host set response wait time for a single radius server radius-server timeout set number of times to resend requests to radius server radius-server retransmit set shared password for radius server radius-server key set availability time restriction for radius server radius-server deadtime setting the nas-identifier attribute to notify the radius server auth radius attribute nas-identifier show port authentication status show auth status show radius server setting status show radius-server show supplicant status show auth supplicant show statistical information show auth statistics clear statistical information clear auth statistics clear authentication status clear auth state set time at which authentication state is cleared (system) auth clear-state time set time at which authentication state is cleared (interface) auth clear-state time set eap pass through pass-through eap</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Set IEEE 802.1X authentication function for the entire system aaa authentication dot1x Set MAC authentication function for the entire system aaa authentication auth-mac Set Web authentication function for the entire system aaa authentication auth-web Set IEEE 802.1X authentication function operating mode dot1x port-control Set unauthenticated port forwarding control for IEEE 802.1X authentication dot1x control-direction Set number of retransmitted EAPOL packets dot1x max-auth-req Set MAC authentication function auth-mac enable Set MAC address format setting for MAC authentication auth-mac auth-user MAC authenticated static registration setting auth-mac static Set Web authentication function auth-web enable Set redirect-destination URL following successful Web authentication auth-web redirect-url Copy Web authentication screen customization files copy auth-web custom-file Delete Web authentication screen customization files erase auth-web custom-file Set host mode auth host-mode Authentication order setting auth order Set reauthentication auth reauthentication Set dynamic VLAN auth dynamic-vlan-creation Set guest VLAN auth guest-vlan Set restriction period following failed authentication auth timeout quiet-period Set re-authentication interval auth timeout reauth-period Set response wait time for the entire RADIUS server auth timeout server-timeout Set response wait time for the supplicant auth timeout supp-timeout Set RADIUS server host radius-server host Set response wait time for a single RADIUS server radius-server timeout Set number of times to resend requests to RADIUS server radius-server retransmit Set shared password for RADIUS server radius-server key Set availability time restriction for RADIUS server radius-server deadtime Setting the NAS-Identifier attribute to notify the RADIUS server auth radius attribute nas-identifier Show port authentication status show auth status Show RADIUS server setting status show radius-server Show supplicant status show auth supplicant Show statistical information show auth statistics Clear statistical information clear auth statistics Clear authentication status clear auth state Set time at which authentication state is cleared (system) auth clear-state time Set time at which authentication state is cleared (interface) auth clear-state time Set EAP pass through pass-through eap</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#ieee-8021x認証の設定">5.1. Set IEEE 802.1X authentication</div><div class="search_word">5.1. set ieee 802.1x authentication make settings so that ieee 802.1x authentication can be used. we will use lan port #1 as the authentication port to which the supplicant is connected. we will set the host mode to the multi supplicant mode . we will use vlan #10 as the guest lan . we will use 192.168.100.101 as the ip address of the radius server that is connected. ■ setting procedure define vlan #10 as the guest vlan. yamaha(config)#vlan databaseyamaha(config-vlan)#vlan 10 (1) yamaha(config-vlan)#exit 1 define vlan #10 enable the ieee 802.1x authentication function for the entire system. yamaha(config)#aaa authentication dot1x set ieee 802.1x authentication for lan port #1. yamaha(config)#interface port1.1yamaha(config-if)#dot1x port-control auto (1) yamaha(config-if)#auth host-mode multi-supplicant (2) yamaha(config-if)#auth guest-vlan 10 (3) yamaha(config-if)#exit 1 set the ieee 802.1x authentication operating mode to auto 2 set the host mode to the multi supplicant mode 3 define vlan #10 as the guest vlan set radius server settings. yamaha(config)#radius-server host 192.168.100.101 key test1 (1) 1 set the host to 192.168.100.101 and the shared password to “test1” check radius server settings. yamaha#show radius-serverserver host : 192.168.100.101  authentication port : 1812  secret key          : test1  timeout             : 5 sec  retransmit count    : 3  deadtime            : 0 min check port authentication settings. yamaha#show auth status[system information]  802.1x port-based authentication : enabled  mac-based authentication         : disabled  web-based authentication         : disabled  clear-state time : not configured  redirect url :    not configured  radius server address :    192.168.100.101 (port:1812)[interface information]  interface port1.1 (up)    802.1x authentication   : force authorized (configured:auto)    mac authentication      : disabled (configured:disable)    web authentication      : enabled (configured:disable)    host mode               : multi-supplicant    dynamic vlan creation   : disabled    guest vlan              : enabled (vlan id:10)    reauthentication        : disabled    reauthentication period : 3600 sec    max request             : 2 times    supplicant timeout      : 30 sec    server timeout          : 30 sec    quiet period            : 60 sec    controlled directions   : in (configured:both)    protocol version        : 2    clear-state time        : not configured</div><div class="display_word">5.1. Set IEEE 802.1X authentication Make settings so that IEEE 802.1X authentication can be used. We will use LAN port #1 as the authentication port to which the supplicant is connected. We will set the host mode to the multi supplicant mode . We will use VLAN #10 as the guest LAN . We will use 192.168.100.101 as the IP address of the RADIUS server that is connected. ■ Setting Procedure Define VLAN #10 as the guest VLAN. Yamaha(config)#vlan databaseYamaha(config-vlan)#vlan 10 (1) Yamaha(config-vlan)#exit 1 Define VLAN #10 Enable the IEEE 802.1X authentication function for the entire system. Yamaha(config)#aaa authentication dot1x Set IEEE 802.1X authentication for LAN port #1. Yamaha(config)#interface port1.1Yamaha(config-if)#dot1x port-control auto (1) Yamaha(config-if)#auth host-mode multi-supplicant (2) Yamaha(config-if)#auth guest-vlan 10 (3) Yamaha(config-if)#exit 1 Set the IEEE 802.1X authentication operating mode to auto 2 Set the host mode to the multi supplicant mode 3 Define VLAN #10 as the guest VLAN Set RADIUS server settings. Yamaha(config)#radius-server host 192.168.100.101 key test1 (1) 1 Set the host to 192.168.100.101 and the shared password to “test1” Check RADIUS server settings. Yamaha#show radius-serverServer Host : 192.168.100.101  Authentication Port : 1812  Secret Key          : test1  Timeout             : 5 sec  Retransmit Count    : 3  Deadtime            : 0 min Check port authentication settings. Yamaha#show auth status[System information]  802.1X Port-Based Authentication : Enabled  MAC-Based Authentication         : Disabled  WEB-Based Authentication         : Disabled  Clear-state time : Not configured  Redirect URL :    Not configured  RADIUS server address :    192.168.100.101 (port:1812)[Interface information]  Interface port1.1 (up)    802.1X Authentication   : Force Authorized (configured:auto)    MAC Authentication      : Disabled (configured:disable)    WEB Authentication      : Enabled (configured:disable)    Host mode               : Multi-supplicant    Dynamic VLAN creation   : Disabled    Guest VLAN              : Enabled (VLAN ID:10)    Reauthentication        : Disabled    Reauthentication period : 3600 sec    MAX request             : 2 times    Supplicant timeout      : 30 sec    Server timeout          : 30 sec    Quiet period            : 60 sec    Controlled directions   : In (configured:both)    Protocol version        : 2    Clear-state time        : Not configured</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#mac認証の設定">5.2. Set MAC authentication</div><div class="search_word">5.2. set mac authentication make settings so that mac authentication can be used. we will use lan port #1 as the authentication port to which the supplicant is connected. we will set the host mode to the multi supplicant mode . we will use 192.168.100.101 as the ip address of the radius server that is connected. ■ setting procedure enable the mac authentication function for the entire system. yamaha(config)#aaa authentication auth-mac set mac authentication for lan port #1. yamaha(config)#interface port1.1yamaha(config-if)#auth-mac enable (1) yamaha(config-if)#auth host-mode multi-supplicant (2) yamaha(config-if)#exit 1 enable mac authentication 2 set the host mode to the multi supplicant mode set radius server settings. yamaha(config)#radius-server host 192.168.100.101 key test1 (1) 1 set the host to 192.168.100.101 and the shared password to “test1” check radius server settings. yamaha#show radius-serverserver host : 192.168.100.101  authentication port : 1812  secret key          : test1  timeout             : 5 sec  retransmit count    : 3  deadtime            : 0 min check port authentication settings. yamaha#show auth status[system information]  802.1x port-based authentication : disabled  mac-based authentication         : enabled  web-based authentication         : disabled  clear-state time : not configured  redirect url :    not configured  radius server address :    192.168.100.101 (port:1812)[interface information]  interface port1.1 (up)    802.1x authentication   : force authorized (configured:-)    mac authentication      : enabled (configured:enable)    web authentication      : disabled (configured:disable)    host mode               : multi-supplicant    dynamic vlan creation   : disabled    guest vlan              : disabled    reauthentication        : disabled    reauthentication period : 3600 sec    max request             : 2 times    supplicant timeout      : 30 sec    server timeout          : 30 sec    quiet period            : 60 sec    controlled directions   : in (configured:both)    protocol version        : 2    clear-state time        : not configured    authentication status   : unauthorized</div><div class="display_word">5.2. Set MAC authentication Make settings so that MAC authentication can be used. We will use LAN port #1 as the authentication port to which the supplicant is connected. We will set the host mode to the multi supplicant mode . We will use 192.168.100.101 as the IP address of the RADIUS server that is connected. ■ Setting Procedure Enable the MAC authentication function for the entire system. Yamaha(config)#aaa authentication auth-mac Set MAC authentication for LAN port #1. Yamaha(config)#interface port1.1Yamaha(config-if)#auth-mac enable (1) Yamaha(config-if)#auth host-mode multi-supplicant (2) Yamaha(config-if)#exit 1 Enable MAC authentication 2 Set the host mode to the multi supplicant mode Set RADIUS server settings. Yamaha(config)#radius-server host 192.168.100.101 key test1 (1) 1 Set the host to 192.168.100.101 and the shared password to “test1” Check RADIUS server settings. Yamaha#show radius-serverServer Host : 192.168.100.101  Authentication Port : 1812  Secret Key          : test1  Timeout             : 5 sec  Retransmit Count    : 3  Deadtime            : 0 min Check port authentication settings. Yamaha#show auth status[System information]  802.1X Port-Based Authentication : Disabled  MAC-Based Authentication         : Enabled  WEB-Based Authentication         : Disabled  Clear-state time : Not configured  Redirect URL :    Not configured  RADIUS server address :    192.168.100.101 (port:1812)[Interface information]  Interface port1.1 (up)    802.1X Authentication   : Force Authorized (configured:-)    MAC Authentication      : Enabled (configured:enable)    WEB Authentication      : Disabled (configured:disable)    Host mode               : Multi-supplicant    Dynamic VLAN creation   : Disabled    Guest VLAN              : Disabled    Reauthentication        : Disabled    Reauthentication period : 3600 sec    MAX request             : 2 times    Supplicant timeout      : 30 sec    Server timeout          : 30 sec    Quiet period            : 60 sec    Controlled directions   : In (configured:both)    Protocol version        : 2    Clear-state time        : Not configured    Authentication status   : Unauthorized</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#web認証の設定">5.3. Set Web authentication</div><div class="search_word">5.3. set web authentication make settings so that web authentication can be used. we will use lan port #1 as the authentication port to which the supplicant is connected. we will assume that the ip address of the supplicant is set to 192.168.100.10. we will use 192.168.100.101 as the ip address of the radius server that is connected. ■ setting procedure assign an ip address to the authenticator for ip communication. yamaha(config)#interface valn1yamaha(config-if)#ip address 192.168.100.240/24yamaha(config-if)#exit enable the web authentication function for the entire system. yamaha(config)#aaa authentication auth-web set web authentication for lan port #1. yamaha(config)#interface port1.1yamaha(config-if)#auth host-mode multi-supplicant (1) yamaha(config-if)#auth-web enable (2) yamaha(config-if)#exit 1 set the host mode to the multi supplicant mode 2 enable web authentication set radius server settings. yamaha(config)#radius-server host 192.168.100.101 key test1 (1) 1 set the host to 192.168.100.101 and the shared password to “test1” check radius server settings. yamaha#show radius-serverserver host : 192.168.100.101  authentication port : 1812  secret key          : test1  timeout             : 5 sec  retransmit count    : 3  deadtime            : 0 min check port authentication settings. yamaha#show auth status[system information]  802.1x port-based authentication : disabled  mac-based authentication         : disabled  web-based authentication         : enabled  clear-state time : not configured  redirect url :    not configured  radius server address :    192.168.100.101 (port:1812)[interface information]  interface port1.1 (up)    802.1x authentication   : force authorized (configured:-)    mac authentication      : disabled (configured:disable)    web authentication      : enabled (configured:enable)    host mode               : multi-supplicant    dynamic vlan creation   : disabled    guest vlan              : disabled    reauthentication        : disabled    reauthentication period : 3600 sec    max request             : 2 times    supplicant timeout      : 30 sec    server timeout          : 30 sec    quiet period            : 60 sec    controlled directions   : in (configured:both)    protocol version        : 2    clear-state time        : not configured</div><div class="display_word">5.3. Set Web authentication Make settings so that Web authentication can be used. We will use LAN port #1 as the authentication port to which the supplicant is connected. We will assume that the IP address of the supplicant is set to 192.168.100.10. We will use 192.168.100.101 as the IP address of the RADIUS server that is connected. ■ Setting Procedure Assign an IP address to the authenticator for IP communication. Yamaha(config)#interface valn1Yamaha(config-if)#ip address 192.168.100.240/24Yamaha(config-if)#exit Enable the Web authentication function for the entire system. Yamaha(config)#aaa authentication auth-web Set Web authentication for LAN port #1. Yamaha(config)#interface port1.1Yamaha(config-if)#auth host-mode multi-supplicant (1) Yamaha(config-if)#auth-web enable (2) Yamaha(config-if)#exit 1 Set the host mode to the multi supplicant mode 2 Enable Web authentication Set RADIUS server settings. Yamaha(config)#radius-server host 192.168.100.101 key test1 (1) 1 Set the host to 192.168.100.101 and the shared password to “test1” Check RADIUS server settings. Yamaha#show radius-serverServer Host : 192.168.100.101  Authentication Port : 1812  Secret Key          : test1  Timeout             : 5 sec  Retransmit Count    : 3  Deadtime            : 0 min Check port authentication settings. Yamaha#show auth status[System information]  802.1X Port-Based Authentication : Disabled  MAC-Based Authentication         : Disabled  WEB-Based Authentication         : Enabled  Clear-state time : Not configured  Redirect URL :    Not configured  RADIUS server address :    192.168.100.101 (port:1812)[Interface information]  Interface port1.1 (up)    802.1X Authentication   : Force Authorized (configured:-)    MAC Authentication      : Disabled (configured:disable)    WEB Authentication      : Enabled (configured:enable)    Host mode               : Multi-supplicant    Dynamic VLAN creation   : Disabled    Guest VLAN              : Disabled    Reauthentication        : Disabled    Reauthentication period : 3600 sec    MAX request             : 2 times    Supplicant timeout      : 30 sec    Server timeout          : 30 sec    Quiet period            : 60 sec    Controlled directions   : In (configured:both)    Protocol version        : 2    Clear-state time        : Not configured</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution using dynamic vlan in the multi supplicant mode will consume internal resources. these resources are also used by the acl and qos functions. there may not be enough resources according to the settings. use caution, since communications may not be possible if there are not enough resources, even though authentication might succeed.</div><div class="display_word">6. Points of Caution Using dynamic VLAN in the multi supplicant mode will consume internal resources. These resources are also used by the ACL and QoS functions. There may not be enough resources according to the settings. Use caution, since communications may not be possible if there are not enough resources, even though authentication might succeed.</div></div><div id="interface_interface_port_auth"><div class="search_title" docfname="interface_interface_port_auth" doctitle="Port" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation built-in radius server example using the wlx402 internal radius server</div><div class="display_word">7. Related Documentation Built-in RADIUS Server Example Using the WLX402 Internal Radius server</div></div><div id="interface_interface_port_security"><div class="search_title" docfname="interface_interface_port_security" doctitle="Port" link="#ポートセキュリティー">Port Security Function</div><div class="search_word">port security function</div><div class="display_word">Port Security Function</div></div><div id="interface_interface_port_security"><div class="search_title" docfname="interface_interface_port_security" doctitle="Port" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview port security is a function that limits communication to only permitted terminals, preventing access from illegal terminals.</div><div class="display_word">1. Function Overview Port security is a function that limits communication to only permitted terminals, preventing access from illegal terminals.</div></div><div id="interface_interface_port_security"><div class="search_title" docfname="interface_interface_port_security" doctitle="Port" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used none</div><div class="display_word">2. Definition of Terms Used None</div></div><div id="interface_interface_port_security"><div class="search_title" docfname="interface_interface_port_security" doctitle="Port" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details for ports on which the port security function is enabled, you can pre-register the mac address of a terminal for which you want to permit communication, thereby allowing communication only for permitted terminals. conversely, if there is access from a terminal that is not registered (an illegal terminal), this is considered illegal access, and the packets are discarded. depending on the settings, the corresponding port can also be shut down. the port security function cannot be used simultaneously with the port authentication function.</div><div class="display_word">3. Function Details For ports on which the port security function is enabled, you can pre-register the MAC address of a terminal for which you want to permit communication, thereby allowing communication only for permitted terminals. Conversely, if there is access from a terminal that is not registered (an illegal terminal), this is considered illegal access, and the packets are discarded. Depending on the settings, the corresponding port can also be shut down. The port security function cannot be used simultaneously with the port authentication function.</div></div><div id="interface_interface_port_security"><div class="search_title" docfname="interface_interface_port_security" doctitle="Port" link="#アクセスする端末を制限">3.1. Limiting the terminals that can access</div><div class="search_word">3.1. limiting the terminals that can access simply by enabling the port security function, and using the port-security mac-address command to register the mac addresses of the terminals for which you want to permit communication, you can limit the terminals that are permitted access.</div><div class="display_word">3.1. Limiting the terminals that can access Simply by enabling the port security function, and using the port-security mac-address command to register the MAC addresses of the terminals for which you want to permit communication, you can limit the terminals that are permitted access.</div></div><div id="interface_interface_port_security"><div class="search_title" docfname="interface_interface_port_security" doctitle="Port" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands set port security function port-security enable register permitted mac addresses port-security mac-address set operation for when security violation occurs port-security violation show port security status show port-security status</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Set port security function port-security enable Register permitted MAC addresses port-security mac-address Set operation for when security violation occurs port-security violation Show port security status show port-security status</div></div><div id="interface_interface_port_security"><div class="search_title" docfname="interface_interface_port_security" doctitle="Port" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="interface_interface_port_security"><div class="search_title" docfname="interface_interface_port_security" doctitle="Port" link="#アクセスする端末を制限">5.1. Limiting the terminals that can access</div><div class="search_word">5.1. limiting the terminals that can access manually specify the mac address so that only the permitted terminal can communicate. enable port security on lan port #1. yamaha(config)#interface port1.1yamaha(config-if)#port-security enable register the mac address that you want to permit. yamaha(config)#port-security mac-address 00a0.de00.0001 forward port1.1 vlan 1yamaha(config)#port-security mac-address 00a0.de00.0002 forward port1.1 vlan 1 check the port security status. yamaha#show port-security status port      security  action     status    last violation --------- --------- ---------- --------- --------------------- port1.1   enabled   discard    normal    00a0.de00.0003 port1.2   disabled  discard    normal port1.3   disabled  discard    normal port1.4   disabled  discard    normal port1.5   disabled  discard    normal port1.6   disabled  discard    normal port1.7   disabled  discard    normal port1.8   disabled  discard    normal port1.9   disabled  discard    normal port1.10  disabled  discard    normal</div><div class="display_word">5.1. Limiting the terminals that can access Manually specify the MAC address so that only the permitted terminal can communicate. Enable port security on LAN port #1. Yamaha(config)#interface port1.1Yamaha(config-if)#port-security enable Register the MAC address that you want to permit. Yamaha(config)#port-security mac-address 00A0.DE00.0001 forward port1.1 vlan 1Yamaha(config)#port-security mac-address 00A0.DE00.0002 forward port1.1 vlan 1 Check the port security status. Yamaha#show port-security status Port      Security  Action     Status    Last violation --------- --------- ---------- --------- --------------------- port1.1   Enabled   Discard    Normal    00A0.DE00.0003 port1.2   Disabled  Discard    Normal port1.3   Disabled  Discard    Normal port1.4   Disabled  Discard    Normal port1.5   Disabled  Discard    Normal port1.6   Disabled  Discard    Normal port1.7   Disabled  Discard    Normal port1.8   Disabled  Discard    Normal port1.9   Disabled  Discard    Normal port1.10  Disabled  Discard    Normal</div></div><div id="interface_interface_port_security"><div class="search_title" docfname="interface_interface_port_security" doctitle="Port" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution use the no shutdown command to recover the port that has shut down due to illegal access. the status that can be checked with the show port-security status command will not return to normal until the port links up. (the status will remain in shutdown state.) if the wrong port is specified with the port-security mac-address command, traffic and violation frames will not be correctly detected.</div><div class="display_word">6. Points of Caution Use the no shutdown command to recover the port that has shut down due to illegal access. The status that can be checked with the show port-security status command will not return to normal until the port links up. (The status will remain in shutdown state.) If the wrong port is specified with the port-security mac-address command, traffic and violation frames will not be correctly detected.</div></div><div id="interface_interface_port_security"><div class="search_title" docfname="interface_interface_port_security" doctitle="Port" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation none</div><div class="display_word">7. Related Documentation None</div></div><div id="ipmcast_ipmcast_igmp_snooping"><div class="search_title" docfname="ipmcast_ipmcast_igmp_snooping" doctitle="IGMP" link="#igmp-snooping">IGMP Snooping</div><div class="search_word">igmp snooping</div><div class="display_word">IGMP Snooping</div></div><div id="ipmcast_ipmcast_igmp_snooping"><div class="search_title" docfname="ipmcast_ipmcast_igmp_snooping" doctitle="IGMP" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview igmp snooping is a function to suppress consumption of network bandwidth in a vlan environment, by controlling any surplus multicast flooding. on an l2 switch, since multicast packets are distributed per vlan, if there is even one device in the vlan that wants to receive the multicast packet, the packet will be distributed to all ports within the same vlan. operations during multicast distribution (no igmp snooping) when using the igmp snooping function, the igmp messages exchanged between the receiving device and the multicast router are monitored (snooped), the packet from the relevant group will only be distributed to the port, to which the device that wants to receive the multicast packet is connected. operations during multicast distribution (using igmp snooping)</div><div class="display_word">1. Function Overview IGMP snooping is a function to suppress consumption of network bandwidth in a VLAN environment, by controlling any surplus multicast flooding. On an L2 switch, since multicast packets are distributed per VLAN, if there is even one device in the VLAN that wants to receive the multicast packet, the packet will be distributed to all ports within the same VLAN. Operations during multicast distribution (no IGMP snooping) When using the IGMP snooping function, the IGMP messages exchanged between the receiving device and the multicast router are monitored (snooped), the packet from the relevant group will only be distributed to the port, to which the device that wants to receive the multicast packet is connected. Operations during multicast distribution (using IGMP snooping)</div></div><div id="ipmcast_ipmcast_igmp_snooping"><div class="search_title" docfname="ipmcast_ipmcast_igmp_snooping" doctitle="IGMP" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used igmp (internet group management protocol) this is a protocol to control multicast groups. the multicast router can determine which hosts on the lan are members of the multicast group, and the hosts can communicate which multicast group they belong to. there are three protocol versions, respectively defined by igmpv1 (rfc1112) , igmpv2 (rfc2236) and igmpv3 (rfc3376) . multicast router port this is the lan/sfp port to which the multicast router is connected. the lan/sfp port that receives the igmp general query is automatically acquired as the multicast router port. igmp report suppression function this is a function where the switch controls the data transmission load between the multicast router and the hosts. the messages gathered by this product to perform control are shown below. igmp reports replied to igmp general queries by hosts, sent from the multicast router igmp leave messages notified by the host the report suppression function works with igmpv1/v2/v3. fast leave function if a lan/sfp port receives an igmpv2/v3 leave message, this function immediately disconnects the port from ports receiving multicast traffic (deletes the fdb entry necessary for transmission). normally, when processing igmpv2/v3 messages, if a leave message is received, a group-specific query is transmitted to that port to confirm that the receiver exists, but if the fast leave function is enabled , that action is not performed. for this reason, the fast leave function is effective only when there is a single receiver under the control of the lan/sfp port . the fast leave function operates only when an igmpv2/v3 leave message is received. if the fast leave function is enabled and the auto-assignment option is specified, the port to which the switch is connected under the control of the lan/sfp port will confirm that a receiver exists when a leave message is received. the auto-assignment option allows you to use the fast leave function in a cascaded switch configuration. igmp query transmission function (igmp querier) this is a function to send igmp general and specific queries. it is used to enable the igmp snooping function in an environment without a multicast router. data transfer suppression function for multicast router ports this function controls multicast data being forwarded to the multicast router port. normally, all multicast group data already acquired by the product is forwarded to the multicast router port, but if this function is enabled , then only multicast group data acquired by receiving an igmp report via the multicast router port is forwarded. if unnecessary multicast data flow between switches is restricting bandwidth, the problem can be mitigated by enabling this function in combination with the l2-unknown-mcast discard command. igmp report forwarding function this function forwards igmp join/leave messages to ports to which a switch is connected under the control of the lan/sfp port. by enabling this function, igmp join/leave messages will be forwarded to non-querier switches in a cascaded switch configuration. when using the data transfer suppression function for multicast router ports in an environment where multiple multicast data flow, we recommend that this function be enabled .</div><div class="display_word">2. Definition of Terms Used IGMP (Internet Group Management Protocol) This is a protocol to control multicast groups. The multicast router can determine which hosts on the LAN are members of the multicast group, and the hosts can communicate which multicast group they belong to. There are three protocol versions, respectively defined by IGMPv1 (RFC1112) , IGMPv2 (RFC2236) and IGMPv3 (RFC3376) . Multicast Router Port This is the LAN/SFP port to which the multicast router is connected. The LAN/SFP port that receives the IGMP general query is automatically acquired as the multicast router port. IGMP Report Suppression Function This is a function where the switch controls the data transmission load between the multicast router and the hosts. The messages gathered by this product to perform control are shown below. IGMP reports replied to IGMP general queries by hosts, sent from the multicast router IGMP leave messages notified by the host The report suppression function works with IGMPv1/v2/v3. Fast Leave Function If a LAN/SFP port receives an IGMPv2/v3 leave message, this function immediately disconnects the port from ports receiving multicast traffic (deletes the FDB entry necessary for transmission). Normally, when processing IGMPv2/v3 messages, if a leave message is received, a group-specific query is transmitted to that port to confirm that the receiver exists, but if the fast leave function is enabled , that action is not performed. For this reason, the fast leave function is effective only when there is a single receiver under the control of the LAN/SFP port . The fast leave function operates only when an IGMPv2/v3 leave message is received. If the fast leave function is enabled and the auto-assignment option is specified, the port to which the switch is connected under the control of the LAN/SFP port will confirm that a receiver exists when a leave message is received. The auto-assignment option allows you to use the fast leave function in a cascaded switch configuration. IGMP Query Transmission Function (IGMP Querier) This is a function to send IGMP general and specific queries. It is used to enable the IGMP snooping function in an environment without a multicast router. Data Transfer Suppression Function for Multicast Router Ports This function controls multicast data being forwarded to the multicast router port. Normally, all multicast group data already acquired by the product is forwarded to the multicast router port, but if this function is enabled , then only multicast group data acquired by receiving an IGMP report via the multicast router port is forwarded. If unnecessary multicast data flow between switches is restricting bandwidth, the problem can be mitigated by enabling this function in combination with the l2-unknown-mcast discard command. IGMP Report Forwarding Function This function forwards IGMP Join/Leave messages to ports to which a switch is connected under the control of the LAN/SFP port. By enabling this function, IGMP Join/Leave messages will be forwarded to non-querier switches in a cascaded switch configuration. When using the data transfer suppression function for multicast router ports in an environment where multiple multicast data flow, we recommend that this function be enabled .</div></div><div id="ipmcast_ipmcast_igmp_snooping"><div class="search_title" docfname="ipmcast_ipmcast_igmp_snooping" doctitle="IGMP" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details the operating specifications for igmp snooping are shown below. this product offers snooping functions compatible with igmp v1/v2/v3 . you can use the ip igmp snooping version command to make later versions operate on this product. version settings are made for the vlan interface , and initial settings are for v3 . the difference in operations between the configured version and received frame versions are shown in the table below. if an igmp query whose version is higher than the settings is received, the version will be lowered to the version that was configured, and the query will be forwarded. if an igmp report whose version is higher than the configured version is received, the relevant report will be discarded without being forwarded. if an igmp query and report of a lower version than the specified version is received, it is forwarded unmodified as the received version. the settings to enable/disable igmp snooping are made for the vlan interface . the default value is disabled . the igmp snooping function can handle the following six operations. multicast router port setting igmp report suppression fast leave igmp query transmission suppression of data forwarding to multicast router port igmp report forwarding although the multicast router port is automatically acquired on vlan interfaces where igmp snooping is set to “ enabled ”, the ip igmp snooping mrouter interface command can also be used to make static settings. the show ip igmp snooping mrouter command is used to check multicast router ports that are set for the vlan interface. the igmp report suppression function is specified for vlan interfaces using the ip igmp snooping report-suppression command. the default value is enabled . when transmitting an igmp report or igmp leave message using the report suppression function, the ipv4 address allocated to the vlan interface will be used for the source ipv4 address. (the address will be set and transmitted as “0.0.0.0” if it has not been allocated.) the fast leave function is set for the vlan interface using the ip igmp snooping fast-leave command. the default value is disabled . if the fast leave function is enabled and the auto-assignment option is specified, and a network switch is connected under the control of the lan/sfp port, the fast leave function is automatically disabled on that port. to determine whether or not a switch is connected under the control of the lan/sfp port, the basic management tlv “system capabilities” of the lldp frame received on that port is checked to see if “bridge” is contained in the tlv. therefore, when using the auto-assignment option, enable lldp transmission and reception on both this product and the counterpart switch and add the basic management tlv to the transmitted frames. the igmp query transmission function is supported in order to allow use of igmp snooping in environments that do not have a multicast router. the igmp query transmission function is controlled with the following two parameters. igmp query transmission function enable/disable the ip igmp snooping querier command is used for vlan interfaces. the default value is disabled . igmp query transmission interval this is executed using the ip igmp snooping query-interval command. the transmission interval can be set from 20–18,000 sec., and the default value is 125 sec. when multiple devices transmit queries within a vlan, the query is sent by the device with the lowest ipv4 address within the vlan. when this product receives a query from a device whose ipv4 address is lower than its own, the query transmission function will be halted. the source ipv4 address that is set when a query is transmitted uses the ipv4 address allocated to the vlan interface. if an ipv4 address has not been allocated, an ipv4 address allocated to a different vlan interface is used instead. (if no ipv4 addresses have been allocated to any vlan interfaces, the address will be set and transmitted as “0.0.0.0”.) this product features a function that forces the ttl value of a received igmp packet to change to “1” if the ttl value is invalid (a value other than “1”), instead of discarding the packet. this is defined as the “ttl check function” , and it can be configured for a vlan interface by using the ip igmp snooping check ttl command. the default setting value for the ttl check function is enabled (packets with invalid ttl values are discarded) . this product features a function that adds the ra (router alert) option to an ip header of a received igmpv2/igmpv3 packet that does not contain the ra option and forwards it instead of discarding. this is defined as the “ra check function” , and it can be configured for a vlan interface by using the ip igmp snooping check ra command. the default value of the ra check function is set to disabled (forward packets that do not contain the ra option) . this product features a function that forces the tos (type of field) value of a received igmpv3 packet to change to “0xc0” if the tos value is invalid (a value other than “0xc0”), instead of discarding the packet. this is defined as the “tos check function” , and it can be configured for a vlan interface by using the ip igmp snooping check tos command. the default value of tos check function is set to disabled (forward packets with invalid tos values) . the data transfer suppression function for multicast router ports is specified for vlan interfaces using the ip igmp snooping mrouter-port data-suppression command. the default value is disabled . the igmp report forwarding function is specified using the ip igmp snooping report-forward command for vlan interfaces. the default value is disabled . when this function is enabled and a network switch is connected under the control of the lan/sfp port, igmp join/leave messages will be forwarded to that port. to determine whether or not a switch is connected under the control of the lan/sfp port, the basic management tlv “system capabilities” of the lldp frame received on that port is checked to see if “bridge” is contained in the tlv. therefore, when using this function, enable lldp transmission and reception on both this product and the counterpart switch and add the basic management tlv to the transmitted frames.</div><div class="display_word">3. Function Details The operating specifications for IGMP snooping are shown below. This product offers snooping functions compatible with IGMP v1/v2/v3 . You can use the ip igmp snooping version command to make later versions operate on this product. Version settings are made for the VLAN interface , and initial settings are for v3 . The difference in operations between the configured version and received frame versions are shown in the table below. If an IGMP query whose version is higher than the settings is received, the version will be lowered to the version that was configured, and the query will be forwarded. If an IGMP report whose version is higher than the configured version is received, the relevant report will be discarded without being forwarded. If an IGMP query and report of a lower version than the specified version is received, it is forwarded unmodified as the received version. The settings to enable/disable IGMP snooping are made for the VLAN interface . The default value is disabled . The IGMP snooping function can handle the following six operations. Multicast router port setting IGMP report suppression Fast leave IGMP query transmission Suppression of data forwarding to multicast router port IGMP report forwarding Although the multicast router port is automatically acquired on VLAN interfaces where IGMP snooping is set to “ Enabled ”, the ip igmp snooping mrouter interface command can also be used to make static settings. The show ip igmp snooping mrouter command is used to check multicast router ports that are set for the VLAN interface. The IGMP report suppression function is specified for VLAN interfaces using the ip igmp snooping report-suppression command. The default value is enabled . When transmitting an IGMP report or IGMP leave message using the report suppression function, the IPv4 address allocated to the VLAN interface will be used for the source IPv4 address. (The address will be set and transmitted as “0.0.0.0” if it has not been allocated.) The fast leave function is set for the VLAN interface using the ip igmp snooping fast-leave command. The default value is disabled . If the fast leave function is enabled and the auto-assignment option is specified, and a network switch is connected under the control of the LAN/SFP port, the fast leave function is automatically disabled on that port. To determine whether or not a switch is connected under the control of the LAN/SFP port, the basic management TLV “System Capabilities” of the LLDP frame received on that port is checked to see if “Bridge” is contained in the TLV. Therefore, when using the auto-assignment option, enable LLDP transmission and reception on both this product and the counterpart switch and add the basic management TLV to the transmitted frames. The IGMP query transmission function is supported in order to allow use of IGMP snooping in environments that do not have a multicast router. The IGMP query transmission function is controlled with the following two parameters. IGMP query transmission function Enable/disable The ip igmp snooping querier command is used for VLAN interfaces. The default value is disabled . IGMP query transmission interval This is executed using the ip igmp snooping query-interval command. The transmission interval can be set from 20–18,000 sec., and the default value is 125 sec. When multiple devices transmit queries within a VLAN, the query is sent by the device with the lowest IPv4 address within the VLAN. When this product receives a query from a device whose IPv4 address is lower than its own, the query transmission function will be halted. The source IPv4 address that is set when a query is transmitted uses the IPv4 address allocated to the VLAN interface. If an IPv4 address has not been allocated, an IPv4 address allocated to a different VLAN interface is used instead. (If no IPv4 addresses have been allocated to any VLAN interfaces, the address will be set and transmitted as “0.0.0.0”.) This product features a function that forces the TTL value of a received IGMP packet to change to “1” if the TTL value is invalid (a value other than “1”), instead of discarding the packet. This is defined as the “TTL check function” , and it can be configured for a VLAN interface by using the ip igmp snooping check ttl command. The default setting value for the TTL check function is enabled (packets with invalid TTL values are discarded) . This product features a function that adds the RA (Router Alert) option to an IP header of a received IGMPv2/IGMPv3 packet that does not contain the RA option and forwards it instead of discarding. This is defined as the “RA check function” , and it can be configured for a VLAN interface by using the ip igmp snooping check ra command. The default value of the RA check function is set to Disabled (forward packets that do not contain the RA option) . This product features a function that forces the ToS (Type of field) value of a received IGMPv3 packet to change to “0xc0” if the ToS value is invalid (a value other than “0xc0”), instead of discarding the packet. This is defined as the “ToS check function” , and it can be configured for a VLAN interface by using the ip igmp snooping check tos command. The default value of ToS check function is set to Disabled (forward packets with invalid ToS values) . The data transfer suppression function for multicast router ports is specified for VLAN interfaces using the ip igmp snooping mrouter-port data-suppression command. The default value is disabled . The IGMP report forwarding function is specified using the ip igmp snooping report-forward command for VLAN interfaces. The default value is disabled . When this function is enabled and a network switch is connected under the control of the LAN/SFP port, IGMP Join/Leave messages will be forwarded to that port. To determine whether or not a switch is connected under the control of the LAN/SFP port, the basic management TLV “System Capabilities” of the LLDP frame received on that port is checked to see if “Bridge” is contained in the TLV. Therefore, when using this function, enable LLDP transmission and reception on both this product and the counterpart switch and add the basic management TLV to the transmitted frames.</div></div><div id="ipmcast_ipmcast_igmp_snooping"><div class="search_title" docfname="ipmcast_ipmcast_igmp_snooping" doctitle="IGMP" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands enable/disable igmp snooping ip igmp snooping set igmp snooping fast-leave ip igmp snooping fast-leave multicast router port setting ip igmp snooping mrouter interface set the query transmission function ip igmp snooping querier set igmp query transmission interval ip igmp snooping query-interval set igmp snooping ttl check ip igmp snooping check ttl set igmp snooping ra check ip igmp snooping check ra set igmp snooping tos check ip igmp snooping check tos set igmp version ip igmp snooping version set igmp report suppression function ip igmp snooping report-suppression set the data transfer suppression function for multicast router ports ip igmp snooping mrouter-port data-suppression set igmp report forwarding function ip igmp snooping report-forward set the processing method for unknown multicast frames in the system l2-unknown-mcast set forwarding of linked local multicasting addresses in the system l2-unknown-mcast forward link-local set the processing method for unknown multicast frames at vlan interfaces l2-unknown-mcast set forwarding of multicasting frames at vlan interfaces l2-mcast flood show multicast router port information show ip igmp snooping mrouter show igmp multicast receiver information show ip igmp snooping groups show igmp related information for an interface show ip igmp snooping interface clear igmp group membership entries clear ip igmp snooping</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Enable/disable IGMP snooping ip igmp snooping Set IGMP snooping fast-leave ip igmp snooping fast-leave Multicast router port setting ip igmp snooping mrouter interface Set the query transmission function ip igmp snooping querier Set IGMP query transmission interval ip igmp snooping query-interval Set IGMP snooping TTL check ip igmp snooping check ttl Set IGMP snooping RA check ip igmp snooping check ra Set IGMP snooping ToS check ip igmp snooping check tos Set IGMP version ip igmp snooping version Set IGMP report suppression function ip igmp snooping report-suppression Set the data transfer suppression function for multicast router ports ip igmp snooping mrouter-port data-suppression Set IGMP report forwarding function ip igmp snooping report-forward Set the processing method for unknown multicast frames in the system l2-unknown-mcast Set forwarding of linked local multicasting addresses in the system l2-unknown-mcast forward link-local Set the processing method for unknown multicast frames at VLAN interfaces l2-unknown-mcast Set forwarding of multicasting frames at VLAN interfaces l2-mcast flood Show multicast router port information show ip igmp snooping mrouter Show IGMP multicast receiver information show ip igmp snooping groups Show IGMP related information for an interface show ip igmp snooping interface Clear IGMP group membership entries clear ip igmp snooping</div></div><div id="ipmcast_ipmcast_igmp_snooping"><div class="search_title" docfname="ipmcast_ipmcast_igmp_snooping" doctitle="IGMP" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="ipmcast_ipmcast_igmp_snooping"><div class="search_title" docfname="ipmcast_ipmcast_igmp_snooping" doctitle="IGMP" link="#igmp-snooping-の設定マルチキャストルーターあり">5.1. IGMP snooping settings (with multicast router)</div><div class="search_word">5.1. igmp snooping settings (with multicast router) in an environment with a multicast router, enable the igmp snooping function and join a multicast group. data is distributed only to pc1 and pc3. set lan ports #1–#4 as access ports and associate them with vlan #10 . since there is a multicast router, leave the igmp query transmission function as “disabled” . set multicast router port acquisition to automatic acquisition only. (a static setting is not used.) enable the fast leave function . define vlan #10, and set igmp snooping. yamaha(config)# vlan databaseyamaha(config-vlan)#vlan 10 (1) yamaha(config-vlan)#exityamaha(config)#interface vlan10yamaha(config-if)#ip igmp snooping enable (2) yamaha(config-if)#no ip igmp snooping querier (3) yamaha(config-if)#ip igmp snooping fast-leave (4) 1 define vlan #10 2 enable igmp snooping for vlan #10 3 disable the igmp query transmission function for vlan #10 4 enable the igmp fast leave function for vlan #10 igmp snooping is enabled and igmp query transmission is disabled in default settings, so there is no need to specify those settings. set lan ports #1–#4 as access ports, and associate them with vlan #10. yamaha(config)# interface port1.1yamaha(config-if)# switchport mode accessyamaha(config-if)# switchport access vlan 10 (1) 1 configure the settings above for lan ports #2–#4 as well. confirm the multicast router port information. (it should be connected to lan port #1.) yamaha#show ip igmp snooping mrouter vlan10vlan    interface             ip-address    expires10      port1.1(dynamic)         192.168.100.216        00:00:49 confirm the information for the multicast recipient. yamaha#show ip igmp snooping groupsigmp snooping group membershipgroup source list: (r - remote, s - static)vlan   group/source address    interface      flags   uptime     expires  last reporter   version10     239.0.0.1                port1.2        r      00:00:13   00:00:41 192.168.100.2    v310     239.0.0.1                port1.4        r      00:00:02   00:00:48 192.168.100.4    v3</div><div class="display_word">5.1. IGMP snooping settings (with multicast router) In an environment with a multicast router, enable the IGMP snooping function and join a multicast group. Data is distributed only to PC1 and PC3. Set LAN ports #1–#4 as access ports and associate them with VLAN #10 . Since there is a multicast router, leave the IGMP query transmission function as “disabled” . Set multicast router port acquisition to automatic acquisition only. (A static setting is not used.) Enable the fast leave function . Define VLAN #10, and set IGMP snooping. Yamaha(config)# vlan databaseYamaha(config-vlan)#vlan 10 (1) Yamaha(config-vlan)#exitYamaha(config)#interface vlan10Yamaha(config-if)#ip igmp snooping enable (2) Yamaha(config-if)#no ip igmp snooping querier (3) Yamaha(config-if)#ip igmp snooping fast-leave (4) 1 Define VLAN #10 2 Enable IGMP Snooping for VLAN #10 3 Disable the IGMP query transmission function for VLAN #10 4 Enable the IGMP fast leave function for VLAN #10 IGMP snooping is enabled and IGMP query transmission is disabled in default settings, so there is no need to specify those settings. Set LAN ports #1–#4 as access ports, and associate them with VLAN #10. Yamaha(config)# interface port1.1Yamaha(config-if)# switchport mode accessYamaha(config-if)# switchport access vlan 10 (1) 1 Configure the settings above for LAN ports #2–#4 as well. Confirm the multicast router port information. (It should be connected to LAN port #1.) Yamaha#show ip igmp snooping mrouter vlan10VLAN    Interface             IP-address    Expires10      port1.1(dynamic)         192.168.100.216        00:00:49 Confirm the information for the multicast recipient. Yamaha#show ip igmp snooping groupsIGMP Snooping Group MembershipGroup source list: (R - Remote, S - Static)Vlan   Group/Source Address    Interface      Flags   Uptime     Expires  Last Reporter   Version10     239.0.0.1                port1.2        R      00:00:13   00:00:41 192.168.100.2    V310     239.0.0.1                port1.4        R      00:00:02   00:00:48 192.168.100.4    V3</div></div><div id="ipmcast_ipmcast_igmp_snooping"><div class="search_title" docfname="ipmcast_ipmcast_igmp_snooping" doctitle="IGMP" link="#igmp-snooping-の設定マルチキャストルーターなし">5.2. IGMP snooping settings (without multicast router)</div><div class="search_word">5.2. igmp snooping settings (without multicast router) in an environment without a multicast router, enable the igmp snooping function and join a multicast group. data is distributed only to pc1 and pc3. switch #a set lan ports #1–#2 as access ports and associate them with vlan #10 . enable the igmp query transmission function . set the igmp query transmission interval to 20 sec . switch #b set lan ports #1–#4 as access ports and associate them with vlan #10 . set multicast router port acquisition to automatic acquisition only. (a static setting is not used.) enable the fast leave function . since there is a device that sets invalid ttl values in igmp packets, disable the ttl check function . [switch #a] define vlan #10, and set igmp snooping. yamaha(config)# vlan databaseyamaha(config-vlan)#vlan 10 (1) yamaha(config-vlan)#exityamaha(config)#interface vlan10yamaha(config-if)#ip igmp snooping enable (2) yamaha(config-if)#ip igmp snooping querier (3) yamaha(config-if)#ip igmp snooping query-interval 20 (4) 1 define vlan #10 2 enable igmp snooping for vlan #10 3 enable the igmp query transmission function for vlan #10 4 set the igmp query transmission interval for vlan #10 to 20 sec. since igmp snooping is enabled by default, we do not need to set this specifically. [switch #a] set lan ports #1–#2 as access ports, and associate them with vlan #10. yamaha(config)# interface port1.1yamaha(config-if)# switchport mode accessyamaha(config-if)# switchport access vlan 10 (1) 1 configure the settings above for lan port #2 as well. [switch #b] define vlan #10, and set igmp snooping. yamaha(config)# vlan databaseyamaha(config-vlan)#vlan 10 (1) yamaha(config-vlan)#exityamaha(config)#interface vlan10yamaha(config-if)#ip igmp snooping enable (2) yamaha(config-if)#no ip igmp snooping querier (3) yamaha(config-if)#no ip igmp snooping check ttl (4) yamaha(config-if)#ip igmp snooping fast-leave (5) 1 define vlan #10 2 enable igmp snooping for vlan #10 3 disable the igmp query transmission function for vlan #10 4 disable the ttl check function for vlan #10 5 enable the igmp fast leave function for vlan #10 igmp snooping is enabled and igmp query transmission is disabled in default settings, so there is no need to specify those settings. [switch #b] set lan ports #1–#4 as access ports, and associate them with vlan #10. yamaha(config)# interface port1.1yamaha(config-if)# switchport mode accessyamaha(config-if)# switchport access vlan 10 (1) 1 configure the settings above for lan ports #2–#4 as well. [switch #b] check the multicast router port information. (it should be connected to lan port #1.) yamaha#show ip igmp snooping mrouter vlan10vlan    interface             ip-address    expires10      port1.1(dynamic)         192.168.100.216        00:00:49 [switch #b] check the multicast receiver information. yamaha#show ip igmp snooping groupsigmp snooping group membershipgroup source list: (r - remote, s - static)vlan   group/source address    interface      flags   uptime     expires  last reporter   version10     239.0.0.1                port1.2        r      00:00:13   00:00:41 192.168.100.2    v310     239.0.0.1                port1.4        r      00:00:02   00:00:48 192.168.100.4    v3</div><div class="display_word">5.2. IGMP snooping settings (without multicast router) In an environment without a multicast router, enable the IGMP snooping function and join a multicast group. Data is distributed only to PC1 and PC3. Switch #A Set LAN ports #1–#2 as access ports and associate them with VLAN #10 . Enable the IGMP query transmission function . Set the IGMP query transmission interval to 20 sec . Switch #B Set LAN ports #1–#4 as access ports and associate them with VLAN #10 . Set multicast router port acquisition to automatic acquisition only. (A static setting is not used.) Enable the fast leave function . Since there is a device that sets invalid TTL values in IGMP packets, disable the TTL check function . [Switch #A] Define VLAN #10, and set IGMP snooping. Yamaha(config)# vlan databaseYamaha(config-vlan)#vlan 10 (1) Yamaha(config-vlan)#exitYamaha(config)#interface vlan10Yamaha(config-if)#ip igmp snooping enable (2) Yamaha(config-if)#ip igmp snooping querier (3) Yamaha(config-if)#ip igmp snooping query-interval 20 (4) 1 Define VLAN #10 2 Enable IGMP Snooping for VLAN #10 3 Enable the IGMP query transmission function for VLAN #10 4 Set the IGMP query transmission interval for VLAN #10 to 20 sec. Since IGMP snooping is enabled by default, we do not need to set this specifically. [Switch #A] Set LAN ports #1–#2 as access ports, and associate them with VLAN #10. Yamaha(config)# interface port1.1Yamaha(config-if)# switchport mode accessYamaha(config-if)# switchport access vlan 10 (1) 1 Configure the settings above for LAN port #2 as well. [Switch #B] Define VLAN #10, and set IGMP snooping. Yamaha(config)# vlan databaseYamaha(config-vlan)#vlan 10 (1) Yamaha(config-vlan)#exitYamaha(config)#interface vlan10Yamaha(config-if)#ip igmp snooping enable (2) Yamaha(config-if)#no ip igmp snooping querier (3) Yamaha(config-if)#no ip igmp snooping check ttl (4) Yamaha(config-if)#ip igmp snooping fast-leave (5) 1 Define VLAN #10 2 Enable IGMP Snooping for VLAN #10 3 Disable the IGMP query transmission function for VLAN #10 4 Disable the TTL check function for VLAN #10 5 Enable the IGMP fast leave function for VLAN #10 IGMP snooping is enabled and IGMP query transmission is disabled in default settings, so there is no need to specify those settings. [Switch #B] Set LAN ports #1–#4 as access ports, and associate them with VLAN #10. Yamaha(config)# interface port1.1Yamaha(config-if)# switchport mode accessYamaha(config-if)# switchport access vlan 10 (1) 1 Configure the settings above for LAN ports #2–#4 as well. [Switch #B] Check the multicast router port information. (It should be connected to LAN port #1.) Yamaha#show ip igmp snooping mrouter vlan10VLAN    Interface             IP-address    Expires10      port1.1(dynamic)         192.168.100.216        00:00:49 [Switch #B] Check the multicast receiver information. Yamaha#show ip igmp snooping groupsIGMP Snooping Group MembershipGroup source list: (R - Remote, S - Static)Vlan   Group/Source Address    Interface      Flags   Uptime     Expires  Last Reporter   Version10     239.0.0.1                port1.2        R      00:00:13   00:00:41 192.168.100.2    V310     239.0.0.1                port1.4        R      00:00:02   00:00:48 192.168.100.4    V3</div></div><div id="ipmcast_ipmcast_igmp_snooping"><div class="search_title" docfname="ipmcast_ipmcast_igmp_snooping" doctitle="IGMP" link="#igmp-snooping-の設定双方向でデータ配信する場合">5.3. IGMP snooping settings (If distributing data in both directions)</div><div class="search_word">5.3. igmp snooping settings (if distributing data in both directions) in a configuration with two switches, both switches are connected to a multicast server and computer. each computer frequently switches between participating multicast groups to minimize the interruption time. switch #a set lan ports #1–#4 as access ports and associate them with vlan #10 . enable the igmp query transmission function . set the igmp query transmission interval to 20 sec . enable the fast leave function and perform the following operations in order to confirm the existence of multiple multicast receivers under the control of the counterpart switch. enable lldp transmission and reception and add the basic management tlv to the transmitted frames . enable the auto-assignment option . disable the igmp report suppression function . increasing the number of multicast servers or data distributions could cause port bandwidth restrictions, so the data transfer suppression function for multicast router ports is enabled to only forward the minimum data necessary. also, unknown multicast frames are set to be discarded . to forward igmp reports to non-queriers, perform the following operations. enable lldp transmission and reception and add the basic management tlv to the transmitted frames . enable the igmp report forwarding function . switch #b set lan ports #1–#4 as access ports and associate them with vlan #10 . set multicast router port acquisition to automatic acquisition only. (a static setting is not used.) enable the fast leave function and perform the following operations in order to confirm the existence of multiple multicast receivers under the control of the counterpart switch. enable lldp transmission and reception and add the basic management tlv to the transmitted frames . enable the auto-assignment option . disable the igmp report suppression function . increasing the number of multicast servers or data distributions could cause port bandwidth restrictions, so the data transfer suppression function for multicast router ports is enabled to only forward the minimum data necessary. also, unknown multicast frames are set to be discarded . [switch #a] define vlan #10, and set igmp snooping. yamaha(config)# vlan databaseyamaha(config-vlan)#vlan 10 (1) yamaha(config-vlan)#exityamaha(config)#interface vlan10yamaha(config-if)#ip igmp snooping enable (2) yamaha(config-if)#ip igmp snooping querier (3) yamaha(config-if)#ip igmp snooping query-interval 20 (4) yamaha(config-if)#ip igmp snooping fast-leave auto-assignment (5) yamaha(config-if)#ip igmp snooping report-suppression disable (6) yamaha(config-if)#ip igmp snooping mrouter-port data-suppression enable (7) yamaha(config-if)#ip igmp snooping report-forward enable (8) 1 define vlan #10 2 enable igmp snooping for vlan #10 3 enable the igmp query transmission function for vlan #10 4 set the igmp query transmission interval for vlan #10 to 20 sec. 5 enable the fast leave function and auto-assignment option for vlan #10 6 disable the report suppression function for vlan #10 7 enable the data transfer suppression function for multicast router ports for vlan #10 8 enable the report forwarding function for vlan #10 since igmp snooping is enabled by default, we do not need to set this specifically. [switch #a] set lan ports #1–#4 as access ports, and associate them with vlan #10. yamaha(config)# interface port1.1yamaha(config-if)# switchport mode accessyamaha(config-if)# switchport access vlan 10 (1) 1 configure the settings above for lan ports #2–#4 as well. [switch #a] discard unknown multicast frames. yamaha(config)#l2-unknown-mcast discard [switch #a] enable lldp transmission and reception for lan port #1 and add the basic management tlv to the transmitted frames. yamaha(config)# lldp runyamaha(config)# interface port1.1yamaha(config-if)# lldp-agentyamaha(lldp-agent)# set lldp enable txrxyamaha(lldp-agent)# tlv-select basic-mgmt [switch #b] define vlan #10, and set igmp snooping. yamaha(config)# vlan databaseyamaha(config-vlan)#vlan 10 (1) yamaha(config-vlan)#exityamaha(config)#interface vlan10yamaha(config-if)#ip igmp snooping enable (2) yamaha(config-if)#no ip igmp snooping querier (3) yamaha(config-if)#ip igmp snooping fast-leave auto-assignment (4) yamaha(config-if)#ip igmp snooping report-suppression disable (5) yamaha(config-if)#ip igmp snooping mrouter-port data-suppression enable (6) yamaha(config-if)#ip igmp snooping report-forward enable (7) 1 define vlan #10 2 enable igmp snooping for vlan #10 3 disable the igmp query transmission function for vlan #10 4 enable the fast leave function and auto-assignment option for vlan #10 5 disable the report suppression function for vlan #10 6 enable the data transfer suppression function for multicast router ports for vlan #10 7 enable the report forwarding function for vlan #10 igmp snooping is enabled and igmp query transmission is disabled in default settings, so there is no need to specify those settings. [switch #b] set lan ports #1–#4 as access ports, and associate them with vlan #10. yamaha(config)# interface port1.1yamaha(config-if)# switchport mode accessyamaha(config-if)# switchport access vlan 10 (1) 1 configure the settings above for lan ports #2–#4 as well. [switch #b] discard unknown multicast frames. yamaha(config)#l2-unknown-mcast discard [switch #b] enable lldp transmission and reception for lan port #1 and add the basic management tlv to the transmitted frames. yamaha(config)# lldp runyamaha(config)# interface port1.1yamaha(config-if)# lldp-agentyamaha(lldp-agent)# set lldp enable txrxyamaha(lldp-agent)# tlv-select basic-mgmt [switch #a] check the multicast receiver information. yamaha#show ip igmp snooping groupsigmp snooping group membershipgroup source list: (r - remote, s - static)vlan   group/source address    interface      flags   uptime     expires  last reporter   version10     239.0.0.1                port1.1        r      00:00:02   00:00:48 192.168.100.3     v310     239.0.0.2                port1.1        r      00:00:02   00:00:48 192.168.100.4     v310     239.0.0.3                port1.3        r      00:00:04   00:00:46 192.168.100.1     v310     239.0.0.1                port1.4        r      00:00:03   00:00:47 192.168.100.2     v3 [switch #b] check the multicast router port information. (it should be connected to lan port #1.) yamaha#show ip igmp snooping mrouter vlan10vlan    interface                 ip-address    expires10      port1.1(dynamic)          192.168.100.240        00:00:25 [switch #b] check the multicast receiver information. yamaha#show ip igmp snooping groupsigmp snooping group membershipgroup source list: (r - remote, s - static)vlan   group/source address    interface      flags   uptime     expires  last reporter   version10     239.0.0.1                port1.1        r      00:00:03   00:00:47 192.168.100.2     v310     239.0.0.3                port1.1        r      00:00:04   00:00:46 192.168.100.1     v310     239.0.0.1                port1.3        r      00:00:02   00:00:48 192.168.100.3     v310     239.0.0.2                port1.4        r      00:00:02   00:00:48 192.168.100.4     v3</div><div class="display_word">5.3. IGMP snooping settings (If distributing data in both directions) In a configuration with two switches, both switches are connected to a multicast server and computer. Each computer frequently switches between participating multicast groups to minimize the interruption time. Switch #A Set LAN ports #1–#4 as access ports and associate them with VLAN #10 . Enable the IGMP query transmission function . Set the IGMP query transmission interval to 20 sec . Enable the fast leave function and perform the following operations in order to confirm the existence of multiple multicast receivers under the control of the counterpart switch. Enable LLDP transmission and reception and add the basic management TLV to the transmitted frames . Enable the auto-assignment option . Disable the IGMP report suppression function . Increasing the number of multicast servers or data distributions could cause port bandwidth restrictions, so the data transfer suppression function for multicast router ports is enabled to only forward the minimum data necessary. Also, unknown multicast frames are set to be discarded . To forward IGMP reports to non-queriers, perform the following operations. Enable LLDP transmission and reception and add the basic management TLV to the transmitted frames . Enable the IGMP report forwarding function . Switch #B Set LAN ports #1–#4 as access ports and associate them with VLAN #10 . Set multicast router port acquisition to automatic acquisition only. (A static setting is not used.) Enable the fast leave function and perform the following operations in order to confirm the existence of multiple multicast receivers under the control of the counterpart switch. Enable LLDP transmission and reception and add the basic management TLV to the transmitted frames . Enable the auto-assignment option . Disable the IGMP report suppression function . Increasing the number of multicast servers or data distributions could cause port bandwidth restrictions, so the data transfer suppression function for multicast router ports is enabled to only forward the minimum data necessary. Also, unknown multicast frames are set to be discarded . [Switch #A] Define VLAN #10, and set IGMP snooping. Yamaha(config)# vlan databaseYamaha(config-vlan)#vlan 10 (1) Yamaha(config-vlan)#exitYamaha(config)#interface vlan10Yamaha(config-if)#ip igmp snooping enable (2) Yamaha(config-if)#ip igmp snooping querier (3) Yamaha(config-if)#ip igmp snooping query-interval 20 (4) Yamaha(config-if)#ip igmp snooping fast-leave auto-assignment (5) Yamaha(config-if)#ip igmp snooping report-suppression disable (6) Yamaha(config-if)#ip igmp snooping mrouter-port data-suppression enable (7) Yamaha(config-if)#ip igmp snooping report-forward enable (8) 1 Define VLAN #10 2 Enable IGMP Snooping for VLAN #10 3 Enable the IGMP query transmission function for VLAN #10 4 Set the IGMP query transmission interval for VLAN #10 to 20 sec. 5 Enable the fast leave function and auto-assignment option for VLAN #10 6 Disable the report suppression function for VLAN #10 7 Enable the data transfer suppression function for multicast router ports for VLAN #10 8 Enable the report forwarding function for VLAN #10 Since IGMP snooping is enabled by default, we do not need to set this specifically. [Switch #A] Set LAN ports #1–#4 as access ports, and associate them with VLAN #10. Yamaha(config)# interface port1.1Yamaha(config-if)# switchport mode accessYamaha(config-if)# switchport access vlan 10 (1) 1 Configure the settings above for LAN ports #2–#4 as well. [Switch #A] Discard unknown multicast frames. Yamaha(config)#l2-unknown-mcast discard [Switch #A] Enable LLDP transmission and reception for LAN port #1 and add the basic management TLV to the transmitted frames. Yamaha(config)# lldp runYamaha(config)# interface port1.1Yamaha(config-if)# lldp-agentYamaha(lldp-agent)# set lldp enable txrxYamaha(lldp-agent)# tlv-select basic-mgmt [Switch #B] Define VLAN #10, and set IGMP snooping. Yamaha(config)# vlan databaseYamaha(config-vlan)#vlan 10 (1) Yamaha(config-vlan)#exitYamaha(config)#interface vlan10Yamaha(config-if)#ip igmp snooping enable (2) Yamaha(config-if)#no ip igmp snooping querier (3) Yamaha(config-if)#ip igmp snooping fast-leave auto-assignment (4) Yamaha(config-if)#ip igmp snooping report-suppression disable (5) Yamaha(config-if)#ip igmp snooping mrouter-port data-suppression enable (6) Yamaha(config-if)#ip igmp snooping report-forward enable (7) 1 Define VLAN #10 2 Enable IGMP Snooping for VLAN #10 3 Disable the IGMP query transmission function for VLAN #10 4 Enable the fast leave function and auto-assignment option for VLAN #10 5 Disable the report suppression function for VLAN #10 6 Enable the data transfer suppression function for multicast router ports for VLAN #10 7 Enable the report forwarding function for VLAN #10 IGMP snooping is enabled and IGMP query transmission is disabled in default settings, so there is no need to specify those settings. [Switch #B] Set LAN ports #1–#4 as access ports, and associate them with VLAN #10. Yamaha(config)# interface port1.1Yamaha(config-if)# switchport mode accessYamaha(config-if)# switchport access vlan 10 (1) 1 Configure the settings above for LAN ports #2–#4 as well. [Switch #B] Discard unknown multicast frames. Yamaha(config)#l2-unknown-mcast discard [Switch #B] Enable LLDP transmission and reception for LAN port #1 and add the basic management TLV to the transmitted frames. Yamaha(config)# lldp runYamaha(config)# interface port1.1Yamaha(config-if)# lldp-agentYamaha(lldp-agent)# set lldp enable txrxYamaha(lldp-agent)# tlv-select basic-mgmt [Switch #A] Check the multicast receiver information. Yamaha#show ip igmp snooping groupsIGMP Snooping Group MembershipGroup source list: (R - Remote, S - Static)Vlan   Group/Source Address    Interface      Flags   Uptime     Expires  Last Reporter   Version10     239.0.0.1                port1.1        R      00:00:02   00:00:48 192.168.100.3     V310     239.0.0.2                port1.1        R      00:00:02   00:00:48 192.168.100.4     V310     239.0.0.3                port1.3        R      00:00:04   00:00:46 192.168.100.1     V310     239.0.0.1                port1.4        R      00:00:03   00:00:47 192.168.100.2     V3 [Switch #B] Check the multicast router port information. (It should be connected to LAN port #1.) Yamaha#show ip igmp snooping mrouter vlan10VLAN    Interface                 IP-address    Expires10      port1.1(dynamic)          192.168.100.240        00:00:25 [Switch #B] Check the multicast receiver information. Yamaha#show ip igmp snooping groupsIGMP Snooping Group MembershipGroup source list: (R - Remote, S - Static)Vlan   Group/Source Address    Interface      Flags   Uptime     Expires  Last Reporter   Version10     239.0.0.1                port1.1        R      00:00:03   00:00:47 192.168.100.2     V310     239.0.0.3                port1.1        R      00:00:04   00:00:46 192.168.100.1     V310     239.0.0.1                port1.3        R      00:00:02   00:00:48 192.168.100.3     V310     239.0.0.2                port1.4        R      00:00:02   00:00:48 192.168.100.4     V3</div></div><div id="ipmcast_ipmcast_igmp_snooping"><div class="search_title" docfname="ipmcast_ipmcast_igmp_snooping" doctitle="IGMP" link="#igmp-snooping-の設定複数のマルチキャスト環境をvlanで分離する場合">5.4. IGMP snooping settings (for separating multiple multicast environments with VLANs)</div><div class="search_word">5.4. igmp snooping settings (for separating multiple multicast environments with vlans) using a single network switch, multicast environments are reconfigured with synchronized times and data streams separated by vlans. vlan #1 is used for management , vlan #10 for time synchronization , and vlan #20 for streaming . entire system the entire system is configured to always forward linked local multicasting addresses . vlan #1 lan port #1 is set as the access port associated to vlan #1 . enable the igmp query transmission function . vlan #10 lan ports #3 to #4 are set as access ports associated to vlan #10 . to minimize any interruptions in ptp packet streams (224.0.1.129 to 224.0.1.132), the vlan is always kept flooded . enable the igmp query transmission function . vlan #20 lan ports #5 to #8 are set as access ports associated to vlan #20 . this discards unknown multicast frames to prevent restricting bandwidth due to unnecessary multicasting in vlan #20. enable the igmp query transmission function . set the igmp query transmission interval to 20 sec . enable the fast leave function . configure the entire system to always forward linked local multicasting addresses. yamaha(config)#l2-unknown-mcast forward link-local specify igmp snooping for vlan #1. yamaha(config)#interface vlan1yamaha(config-if)#ip igmp snooping enable (1) yamaha(config-if)#ip igmp snooping querier (2) 1 enable igmp snooping for vlan #1 2 enable the igmp query transmission function for vlan #1 since igmp snooping is enabled by default, we do not need to set this specifically. define vlan #10 and specify igmp snooping and multicast forwarding. yamaha(config)# vlan databaseyamaha(config-vlan)#vlan 10 (1) yamaha(config-vlan)#exityamaha(config)#interface vlan10yamaha(config-if)#l2-mcast flood 224.0.1.129 (2) yamaha(config-if)#l2-mcast flood 224.0.1.130 (3) yamaha(config-if)#l2-mcast flood 224.0.1.131 (4) yamaha(config-if)#l2-mcast flood 224.0.1.132 (5) yamaha(config-if)#ip igmp snooping enable (6) yamaha(config-if)#ip igmp snooping querier (7) 1 define vlan #10 2 always flood 224.0.1.129 on vlan #10 3 always flood 224.0.1.130 on vlan #10 4 always flood 224.0.1.131 on vlan #10 5 always flood 224.0.1.132 on vlan #10 6 enable igmp snooping for vlan #10 7 enable the igmp query transmission function for vlan #10 since igmp snooping is enabled by default, we do not need to set this specifically. set lan ports #3–#4 as access ports, and associate them with vlan #10. yamaha(config)# interface port1.3yamaha(config-if)# switchport mode accessyamaha(config-if)# switchport access vlan 10 (1) 1 configure the settings above for lan port #4 as well. define vlan #20 and specify igmp snooping and multicast forwarding. yamaha(config)# vlan databaseyamaha(config-vlan)#vlan 20 (1) yamaha(config-vlan)#exityamaha(config)#interface vlan20yamaha(config-if)#l2-unknown-mcast discard (2) yamaha(config-if)#ip igmp snooping enable (3) yamaha(config-if)#ip igmp snooping query-interval 20 (4) yamaha(config-if)#ip igmp snooping querier (5) yamaha(config-if)#ip igmp snooping fast-leave (6) 1 define vlan #20 2 discard unknown multicast on vlan #20 3 enable igmp snooping for vlan #20 4 set the igmp query transmission interval for vlan #20 to 20 sec. 5 enable the igmp query transmission function for vlan #20 6 enable the fast leave function for vlan #20 since igmp snooping is enabled by default, we do not need to set this specifically. [switch #a] set lan ports #5–#8 as access ports, and associate them with vlan #20. yamaha(config)# interface port1.5yamaha(config-if)# switchport mode accessyamaha(config-if)# switchport access vlan 20 (1) 1 configure the settings above for lan ports #6–#8 as well. confirm the information for the multicast recipient. ptp packets (224.0.1.129 to 224.0.1.132) are not listed because they are always kept flooded at that time. yamaha#show ip igmp snooping groupsigmp snooping group membershipgroup source list: (r - remote, s - static)vlan   group/source address    interface      flags   uptime     expires  last reporter   version20     239.0.0.1                port1.6        r      00:00:02   00:00:48 192.168.100.1     v320     239.0.0.2                port1.8        r      00:00:02   00:00:48 192.168.100.2     v3</div><div class="display_word">5.4. IGMP snooping settings (for separating multiple multicast environments with VLANs) Using a single network switch, multicast environments are reconfigured with synchronized times and data streams separated by VLANs. VLAN #1 is used for management , VLAN #10 for time synchronization , and VLAN #20 for streaming . Entire system The entire system is configured to always forward linked local multicasting addresses . VLAN #1 LAN port #1 is set as the access port associated to VLAN #1 . Enable the IGMP query transmission function . VLAN #10 LAN ports #3 to #4 are set as access ports associated to VLAN #10 . To minimize any interruptions in PTP packet streams (224.0.1.129 to 224.0.1.132), the VLAN is always kept flooded . Enable the IGMP query transmission function . VLAN #20 LAN ports #5 to #8 are set as access ports associated to VLAN #20 . This discards unknown multicast frames to prevent restricting bandwidth due to unnecessary multicasting in VLAN #20. Enable the IGMP query transmission function . Set the IGMP query transmission interval to 20 sec . Enable the fast leave function . Configure the entire system to always forward linked local multicasting addresses. Yamaha(config)#l2-unknown-mcast forward link-local Specify IGMP snooping for VLAN #1. Yamaha(config)#interface vlan1Yamaha(config-if)#ip igmp snooping enable (1) Yamaha(config-if)#ip igmp snooping querier (2) 1 Enable IGMP snooping for VLAN #1 2 Enable the IGMP query transmission function for VLAN #1 Since IGMP snooping is enabled by default, we do not need to set this specifically. Define VLAN #10 and specify IGMP snooping and multicast forwarding. Yamaha(config)# vlan databaseYamaha(config-vlan)#vlan 10 (1) Yamaha(config-vlan)#exitYamaha(config)#interface vlan10Yamaha(config-if)#l2-mcast flood 224.0.1.129 (2) Yamaha(config-if)#l2-mcast flood 224.0.1.130 (3) Yamaha(config-if)#l2-mcast flood 224.0.1.131 (4) Yamaha(config-if)#l2-mcast flood 224.0.1.132 (5) Yamaha(config-if)#ip igmp snooping enable (6) Yamaha(config-if)#ip igmp snooping querier (7) 1 Define VLAN #10 2 Always flood 224.0.1.129 on VLAN #10 3 Always flood 224.0.1.130 on VLAN #10 4 Always flood 224.0.1.131 on VLAN #10 5 Always flood 224.0.1.132 on VLAN #10 6 Enable IGMP Snooping for VLAN #10 7 Enable the IGMP query transmission function for VLAN #10 Since IGMP snooping is enabled by default, we do not need to set this specifically. Set LAN ports #3–#4 as access ports, and associate them with VLAN #10. Yamaha(config)# interface port1.3Yamaha(config-if)# switchport mode accessYamaha(config-if)# switchport access vlan 10 (1) 1 Configure the settings above for LAN port #4 as well. Define VLAN #20 and specify IGMP snooping and multicast forwarding. Yamaha(config)# vlan databaseYamaha(config-vlan)#vlan 20 (1) Yamaha(config-vlan)#exitYamaha(config)#interface vlan20Yamaha(config-if)#l2-unknown-mcast discard (2) Yamaha(config-if)#ip igmp snooping enable (3) Yamaha(config-if)#ip igmp snooping query-interval 20 (4) Yamaha(config-if)#ip igmp snooping querier (5) Yamaha(config-if)#ip igmp snooping fast-leave (6) 1 Define VLAN #20 2 Discard unknown multicast on VLAN #20 3 Enable IGMP snooping for VLAN #20 4 Set the IGMP query transmission interval for VLAN #20 to 20 sec. 5 Enable the IGMP query transmission function for VLAN #20 6 Enable the fast leave function for VLAN #20 Since IGMP snooping is enabled by default, we do not need to set this specifically. [Switch #A] Set LAN ports #5–#8 as access ports, and associate them with VLAN #20. Yamaha(config)# interface port1.5Yamaha(config-if)# switchport mode accessYamaha(config-if)# switchport access vlan 20 (1) 1 Configure the settings above for LAN ports #6–#8 as well. Confirm the information for the multicast recipient. PTP packets (224.0.1.129 to 224.0.1.132) are not listed because they are always kept flooded at that time. Yamaha#show ip igmp snooping groupsIGMP Snooping Group MembershipGroup source list: (R - Remote, S - Static)Vlan   Group/Source Address    Interface      Flags   Uptime     Expires  Last Reporter   Version20     239.0.0.1                port1.6        R      00:00:02   00:00:48 192.168.100.1     V320     239.0.0.2                port1.8        R      00:00:02   00:00:48 192.168.100.2     V3</div></div><div id="ipmcast_ipmcast_igmp_snooping"><div class="search_title" docfname="ipmcast_ipmcast_igmp_snooping" doctitle="IGMP" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution if you want to change the handling of unknown multicast frames, use the l2-unknown-mcast command. when a topology change is detected, if you want to send a query regardless of the normal transmission interval, set the l2-mcast snooping tcn-query command.</div><div class="display_word">6. Points of Caution If you want to change the handling of unknown multicast frames, use the l2-unknown-mcast command. When a topology change is detected, if you want to send a query regardless of the normal transmission interval, set the l2-mcast snooping tcn-query command.</div></div><div id="ipmcast_ipmcast_igmp_snooping"><div class="search_title" docfname="ipmcast_ipmcast_igmp_snooping" doctitle="IGMP" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation layer 2 function: vlan</div><div class="display_word">7. Related Documentation Layer 2 Function: VLAN</div></div><div id="ipmcast_ipmcast_mld_snooping"><div class="search_title" docfname="ipmcast_ipmcast_mld_snooping" doctitle="MLD" link="#mld-snooping">MLD Snooping</div><div class="search_word">mld snooping</div><div class="display_word">MLD Snooping</div></div><div id="ipmcast_ipmcast_mld_snooping"><div class="search_title" docfname="ipmcast_ipmcast_mld_snooping" doctitle="MLD" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview mld snooping is a function to suppress consumption of network bandwidth in an ipv6 vlan environment, by controlling any surplus multicast flooding. on an l2 switch, since multicast packets are distributed per vlan, if there is even one device in the vlan that wants to receive the multicast packet, the packet will be distributed to all ports within the same vlan. operations during multicast distribution (no mld snooping) when using the mld snooping function, the mld messages exchanged between the receiving device and the multicast router are monitored (snooped), the packet from the relevant group will only be distributed to the port, to which the device that wants to receive the multicast packet is connected. operations during multicast distribution (using mld snooping)</div><div class="display_word">1. Function Overview MLD snooping is a function to suppress consumption of network bandwidth in an IPv6 VLAN environment, by controlling any surplus multicast flooding. On an L2 switch, since multicast packets are distributed per VLAN, if there is even one device in the VLAN that wants to receive the multicast packet, the packet will be distributed to all ports within the same VLAN. Operations during multicast distribution (no MLD snooping) When using the MLD snooping function, the MLD messages exchanged between the receiving device and the multicast router are monitored (snooped), the packet from the relevant group will only be distributed to the port, to which the device that wants to receive the multicast packet is connected. Operations during multicast distribution (using MLD snooping)</div></div><div id="ipmcast_ipmcast_mld_snooping"><div class="search_title" docfname="ipmcast_ipmcast_mld_snooping" doctitle="MLD" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used mld (multicast listener discovery) this is a protocol to control multicast groups using ipv6 (a sub-protocol of icmpv6). the multicast router can determine which hosts on the lan are members of the multicast group, and the hosts can communicate which multicast group they belong to. there are two protocol versions, respectively defined by mldv1 (rfc2710) , and mldv2 (rfc3810) . multicast router port this is the lan/sfp port to which the multicast router is connected. the lan/sfp port that receives the mld general query is automatically acquired as the multicast router port. mld report suppression function this is a function where the l2 switch controls the data transmission load between the multicast router and the hosts. the messages gathered by this product to perform control are shown below. mld reports replied to mld general queries by hosts, sent from the multicast router mld done messages notified by the host and mld reports (leave) the report suppression function works with mldv1/v2. mld fast leave function this function allows for the lan/sfp port that received an mldv1 done and an mldv2 report (leave) to immediately stop receiving multicasts (deleting the necessary fdb entry). previously, when an mldv1 done message and an mldv2 report (leave) was received in the course of mld leave processing, a group-specific query was sent to check for the existence of a receiver; but if the fast leave function is enabled , this operation is not performed. for this reason, the fast leave function is effective only when there is a single receiver under the control of the lan/sfp port . mld query transmission function (mld querier) this is a function to send mld general and specific queries. it is used to enable the mld snooping function in an environment without a multicast router.</div><div class="display_word">2. Definition of Terms Used MLD (Multicast Listener Discovery) This is a protocol to control multicast groups using IPv6 (a sub-protocol of ICMPv6). The multicast router can determine which hosts on the LAN are members of the multicast group, and the hosts can communicate which multicast group they belong to. There are two protocol versions, respectively defined by MLDv1 (RFC2710) , and MLDv2 (RFC3810) . Multicast Router Port This is the LAN/SFP port to which the multicast router is connected. The LAN/SFP port that receives the MLD general query is automatically acquired as the multicast router port. MLD Report Suppression Function This is a function where the L2 switch controls the data transmission load between the multicast router and the hosts. The messages gathered by this product to perform control are shown below. MLD reports replied to MLD general queries by hosts, sent from the multicast router MLD Done messages notified by the host and MLD reports (Leave) The report suppression function works with MLDv1/v2. MLD Fast Leave Function This function allows for the LAN/SFP port that received an MLDv1 Done and an MLDv2 report (Leave) to immediately stop receiving multicasts (deleting the necessary FDB entry). Previously, when an MLDv1 Done message and an MLDv2 report (Leave) was received in the course of MLD leave processing, a group-specific query was sent to check for the existence of a receiver; but if the fast leave function is enabled , this operation is not performed. For this reason, the fast leave function is effective only when there is a single receiver under the control of the LAN/SFP port . MLD Query Transmission Function (MLD Querier) This is a function to send MLD general and specific queries. It is used to enable the MLD snooping function in an environment without a multicast router.</div></div><div id="ipmcast_ipmcast_mld_snooping"><div class="search_title" docfname="ipmcast_ipmcast_mld_snooping" doctitle="MLD" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details the operating specifications for mld snooping are shown below. this product offers snooping functions compatible with mld v1/v2 . you can use the ipv6 mld snooping version command to make later versions work on this product. version settings are made for the vlan interface , and initial settings are for v2 . the difference in operations between the configured version and received frame versions are shown in the table below. if an mld query whose version is higher than the settings is received, the version will be lowered to the version that was configured, and the query will be forwarded. if an mld report whose version is higher than the configured version is received, the relevant report will be discarded without being forwarded. the settings to enable/disable mld snooping are made for the vlan interface . the initial setting for the default vlan (vlan #1) and the initial setting after a vlan is generated are both disabled . the mld snooping function can handle the following four operations. multicast router port setting mld report suppression mld fast leave mld query transmission although the multicast router port is automatically acquired on vlan interfaces where mld snooping is set to “ enabled ”, the ipv6 mld snooping mrouter interface command can also be used to make static settings. the show ipv6 mld snooping mrouter command is used to check multicast router ports that are set for the vlan interface. the mld report suppression function is specified for vlan interfaces using the ipv6 mld snooping report-suppression command. the default value is enabled . when transmitting an mld report or mld leave message using the report suppression function, the ipv6 link local address allocated to the vlan interface will be used for the source ipv6 address. (the address will be set and transmitted as “::” if it has not been allocated.) the mld fast leave function is set for the vlan interface using the ipv6 mld snooping fast-leave command. the initial setting for the default vlan (vlan #1) and the initial setting after a vlan is generated are both disabled . the mld query transmission function is supported in order to allow use of mld snooping in environments that do not have a multicast router. the mld query transmission function controls the following two parameters. mld query transmission function enable/disable the ipv6 mld snooping querier command is used for vlan interfaces. the initial setting for the default vlan (vlan #1) and the initial setting after a vlan is generated are both disabled . mld query transmission interval this is set using the ipv6 mld snooping query-interval command. the transmission interval can be set from 20–18,000 sec., and the default value is 125 sec. when multiple devices transmit queries within a vlan, the query is sent by the device with the lowest ipv6 address within the vlan. when this product receives a query from a device whose ipv6 address is lower than its own, the query transmission function will be halted. the source ipv6 address that is set when a query is transmitted uses the ipv6 link local address allocated to the vlan interface. if an ipv6 link local address has not been allocated, an ipv6 link local address allocated to a different vlan interface is used instead. (if no ipv6 link local addresses have been allocated to any vlan interfaces, the query is not transmitted.) in this product, if the hop limit of a received mld packet is invalid (other than 1), the mld packet will be discarded. in this product, if a received mld packet does not contain the router alert option, the mld packet will be discarded.</div><div class="display_word">3. Function Details The operating specifications for MLD snooping are shown below. This product offers snooping functions compatible with MLD v1/v2 . You can use the ipv6 mld snooping version command to make later versions work on this product. Version settings are made for the VLAN interface , and initial settings are for v2 . The difference in operations between the configured version and received frame versions are shown in the table below. If an MLD query whose version is higher than the settings is received, the version will be lowered to the version that was configured, and the query will be forwarded. If an MLD report whose version is higher than the configured version is received, the relevant report will be discarded without being forwarded. The settings to enable/disable MLD snooping are made for the VLAN interface . The initial setting for the default VLAN (VLAN #1) and the initial setting after a VLAN is generated are both disabled . The MLD snooping function can handle the following four operations. Multicast router port setting MLD report suppression MLD fast leave MLD query transmission Although the multicast router port is automatically acquired on VLAN interfaces where MLD snooping is set to “ Enabled ”, the ipv6 mld snooping mrouter interface command can also be used to make static settings. The show ipv6 mld snooping mrouter command is used to check multicast router ports that are set for the VLAN interface. The MLD report suppression function is specified for VLAN interfaces using the ipv6 mld snooping report-suppression command. The default value is enabled . When transmitting an MLD report or MLD leave message using the report suppression function, the IPv6 link local address allocated to the VLAN interface will be used for the source IPv6 address. (The address will be set and transmitted as “::” if it has not been allocated.) The MLD fast leave function is set for the VLAN interface using the ipv6 mld snooping fast-leave command. The initial setting for the default VLAN (VLAN #1) and the initial setting after a VLAN is generated are both disabled . The MLD query transmission function is supported in order to allow use of MLD snooping in environments that do not have a multicast router. The MLD query transmission function controls the following two parameters. MLD query transmission function Enable/disable The ipv6 mld snooping querier command is used for VLAN interfaces. The initial setting for the default VLAN (VLAN #1) and the initial setting after a VLAN is generated are both disabled . MLD query transmission interval This is set using the ipv6 mld snooping query-interval command. The transmission interval can be set from 20–18,000 sec., and the default value is 125 sec. When multiple devices transmit queries within a VLAN, the query is sent by the device with the lowest IPv6 address within the VLAN. When this product receives a query from a device whose IPv6 address is lower than its own, the query transmission function will be halted. The source iPv6 address that is set when a query is transmitted uses the IPv6 link local address allocated to the VLAN interface. If an IPv6 link local address has not been allocated, an IPv6 link local address allocated to a different VLAN interface is used instead. (If no IPv6 link local addresses have been allocated to any VLAN interfaces, the query is not transmitted.) In this product, if the Hop Limit of a received MLD packet is invalid (other than 1), the MLD packet will be discarded. In this product, if a received MLD packet does not contain the Router Alert option, the MLD packet will be discarded.</div></div><div id="ipmcast_ipmcast_mld_snooping"><div class="search_title" docfname="ipmcast_ipmcast_mld_snooping" doctitle="MLD" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands enable/disable mld snooping ipv6 mld snooping set mld snooping fast-leave ipv6 mld snooping fast-leave multicast router port setting ipv6 mld snooping mrouter interface set the query transmission function ipv6 mld snooping querier set the mld query transmission interval ipv6 mld snooping query-interval set the mld version ipv6 mld snooping version set the mld report suppression function ipv6 mld snooping report-suppression show multicast router port information show ipv6 mld snooping mrouter show mld multicast recipient information show ipv6 mld snooping groups show mld related information for an interface show ipv6 mld snooping interface clear the mld group membership entries clear ipv6 mld snooping</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Enable/disable MLD snooping ipv6 mld snooping Set MLD snooping fast-leave ipv6 mld snooping fast-leave Multicast router port setting ipv6 mld snooping mrouter interface Set the query transmission function ipv6 mld snooping querier Set the MLD query transmission interval ipv6 mld snooping query-interval Set the MLD version ipv6 mld snooping version Set the MLD report suppression function ipv6 mld snooping report-suppression Show multicast router port information show ipv6 mld snooping mrouter Show MLD multicast recipient information show ipv6 mld snooping groups Show MLD related information for an interface show ipv6 mld snooping interface Clear the MLD group membership entries clear ipv6 mld snooping</div></div><div id="ipmcast_ipmcast_mld_snooping"><div class="search_title" docfname="ipmcast_ipmcast_mld_snooping" doctitle="MLD" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="ipmcast_ipmcast_mld_snooping"><div class="search_title" docfname="ipmcast_ipmcast_mld_snooping" doctitle="MLD" link="#mld-snooping-の設定マルチキャストルーターあり">5.1. MLD snooping settings (with multicast router)</div><div class="search_word">5.1. mld snooping settings (with multicast router) in an environment with a multicast router, enable the mld snooping function and join a multicast group. data is distributed only to pc1 and pc3. set lan ports #1–#4 as access ports and associate them with vlan #10 . since there is a multicast router, leave the mld query transmission function as “disabled” . set multicast router port acquisition to automatic acquisition only. (a static setting is not used.) enable the mld fast leave function . ■ setting procedure define vlan #10, and set mld snooping. yamaha(config)# vlan databaseyamaha(config-vlan)#vlan 10 (1) yamaha(config-vlan)#exityamaha(config)#interface vlan10yamaha(config-if)#ipv6 enable (2) yamaha(config-if)#ipv6 mld snooping (3) yamaha(config-if)#no ipv6 mld snooping querier (4) yamaha(config-if)#ipv6 mld snooping fast-leave (5) 1 define vlan #10 2 enable the ipv6 function for vlan #10 3 enable mld snooping for vlan #10 4 disable the mld query transmission function for vlan #10 5 enable the mld fast leave function for vlan #10 mld snooping is enabled and the mld query transmission function is disabled in default settings, so there is no need to specify those settings. set lan ports #1–#4 as access ports, and associate them with vlan #10. yamaha(config)# interface port1.1yamaha(config-if)# switchport mode accessyamaha(config-if)# switchport access vlan 10 (1) 1 configure the settings above for lan ports #2–#4 as well. confirm the multicast router port information. (it should be connected to lan port #1.) yamaha#show ipv6 mld snooping mrouter vlan10vlan    interface             ip-address    expires10      port1.1(dynamic)         fe80::2a0:deff:feae:b879        00:00:43 confirm the information for the multicast recipient. yamaha#show ipv6 mld snooping groupsmld connected group membershipvlan   group address                           interface            uptime   expires  last reporter10     ff15::1                                 port1.2              00:00:13 00:00:41 fe80::a00:27ff:fe8b:87e210     ff15::1                                 port1.4              00:00:02 00:00:48 fe80::a00:27ff:fe8b:87e4</div><div class="display_word">5.1. MLD snooping settings (with multicast router) In an environment with a multicast router, enable the MLD snooping function and join a multicast group. Data is distributed only to PC1 and PC3. Set LAN ports #1–#4 as access ports and associate them with VLAN #10 . Since there is a multicast router, leave the MLD query transmission function as “disabled” . Set multicast router port acquisition to automatic acquisition only. (A static setting is not used.) Enable the MLD fast leave function . ■ Setting Procedure Define VLAN #10, and set MLD snooping. Yamaha(config)# vlan databaseYamaha(config-vlan)#vlan 10 (1) Yamaha(config-vlan)#exitYamaha(config)#interface vlan10Yamaha(config-if)#ipv6 enable (2) Yamaha(config-if)#ipv6 mld snooping (3) Yamaha(config-if)#no ipv6 mld snooping querier (4) Yamaha(config-if)#ipv6 mld snooping fast-leave (5) 1 Define VLAN #10 2 Enable the IPv6 function for VLAN #10 3 Enable MLD Snooping for VLAN #10 4 Disable the MLD query transmission function for VLAN #10 5 Enable the MLD fast leave function for VLAN #10 MLD snooping is enabled and the MLD query transmission function is disabled in default settings, so there is no need to specify those settings. Set LAN ports #1–#4 as access ports, and associate them with VLAN #10. Yamaha(config)# interface port1.1Yamaha(config-if)# switchport mode accessYamaha(config-if)# switchport access vlan 10 (1) 1 Configure the settings above for LAN ports #2–#4 as well. Confirm the multicast router port information. (It should be connected to LAN port #1.) Yamaha#show ipv6 mld snooping mrouter vlan10VLAN    Interface             IP-address    Expires10      port1.1(dynamic)         fe80::2a0:deff:feae:b879        00:00:43 Confirm the information for the multicast recipient. Yamaha#show ipv6 mld snooping groupsMLD Connected Group MembershipVlan   Group Address                           Interface            Uptime   Expires  Last Reporter10     ff15::1                                 port1.2              00:00:13 00:00:41 fe80::a00:27ff:fe8b:87e210     ff15::1                                 port1.4              00:00:02 00:00:48 fe80::a00:27ff:fe8b:87e4</div></div><div id="ipmcast_ipmcast_mld_snooping"><div class="search_title" docfname="ipmcast_ipmcast_mld_snooping" doctitle="MLD" link="#mld-snooping-の設定マルチキャストルーターなし">5.2. MLD snooping settings (without multicast router)</div><div class="search_word">5.2. mld snooping settings (without multicast router) in an environment without a multicast router, enable the mld snooping function and join a multicast group. data is distributed only to pc1 and pc3. switch #a set lan ports #1–#2 as access ports and associate them with vlan #10 . enable the mld query transmission function . set the mld query transmission interval to* 20 sec*. switch #b set lan ports #1–#4 as access ports and associate them with vlan #10 . set multicast router port acquisition to automatic acquisition only. (a static setting is not used.) enable the mld fast leave function . [switch #a] define vlan #10, and set mld snooping. yamaha(config)# vlan databaseyamaha(config-vlan)#vlan 10 (1) yamaha(config-vlan)#exityamaha(config)#interface vlan10yamaha(config-if)#ipv6 enable (2) yamaha(config-if)#ipv6 mld snooping (3) yamaha(config-if)#ipv6 mld snooping querier (4) yamaha(config-if)#ipv6 mld snooping query-interval 20 (5) 1 define vlan #10 2 enable the ipv6 function for vlan #10 3 enable mld snooping for vlan #10 4 enable the mld query transmission function for vlan #10 5 set the mld query transmission interval for vlan #10 to 20 sec. since mld snooping is enabled by default, we do not need to set this specifically. [switch #a] set lan ports #1–#2 as access ports, and associate them with vlan #10. yamaha(config)# interface port1.1yamaha(config-if)# switchport mode accessyamaha(config-if)# switchport access vlan 10 (1) 1 configure the settings above for lan port #2 as well. [switch #b] define vlan #10, and set mld snooping. yamaha(config)# vlan databaseyamaha(config-vlan)#vlan 10 (1) yamaha(config-vlan)#exityamaha(config)#interface vlan10yamaha(config-if)#ipv6 enable (2) yamaha(config-if)#ipv6 mld snooping (3) yamaha(config-if)#no ipv6 mld snooping querier (4) yamaha(config-if)#ipv6 mld snooping fast-leave (5) 1 define vlan #10 2 enable the ipv6 function for vlan #10 3 enable mld snooping for vlan #10 4 disable the mld query transmission function for vlan #10 5 enable the mld fast leave function for vlan #10 mld snooping is enabled and the mld query transmission function is disabled in default settings, so there is no need to specify those settings. [switch #b] set lan ports #1–#4 as access ports, and associate them with vlan #10. yamaha(config)# interface port1.1yamaha(config-if)# switchport mode accessyamaha(config-if)# switchport access vlan 10 (1) 1 configure the settings above for lan ports #2–#4 as well. [switch #b] check the multicast router port information. (it should be connected to lan port #1.) yamaha#show ipv6 mld snooping mrouter vlan10vlan    interface             ip-address    expires10      port1.1(dynamic)         fe80::2a0:deff:feae:b879        00:00:43 [switch #b] check the multicast receiver information. yamaha#show ipv6 mld snooping groupsmld connected group membershipvlan   group address                           interface            uptime   expires  last reporter10     ff15::1                                 port1.2              00:00:13 00:00:41 fe80::a00:27ff:fe8b:87e210     ff15::1                                 port1.4              00:00:02 00:00:48 fe80::a00:27ff:fe8b:87e4</div><div class="display_word">5.2. MLD snooping settings (without multicast router) In an environment without a multicast router, enable the MLD snooping function and join a multicast group. Data is distributed only to PC1 and PC3. Switch #A Set LAN ports #1–#2 as access ports and associate them with VLAN #10 . Enable the MLD query transmission function . Set the MLD query transmission interval to* 20 sec*. Switch #B Set LAN ports #1–#4 as access ports and associate them with VLAN #10 . Set multicast router port acquisition to automatic acquisition only. (A static setting is not used.) Enable the MLD fast leave function . [Switch #A] Define VLAN #10, and set MLD snooping. Yamaha(config)# vlan databaseYamaha(config-vlan)#vlan 10 (1) Yamaha(config-vlan)#exitYamaha(config)#interface vlan10Yamaha(config-if)#ipv6 enable (2) Yamaha(config-if)#ipv6 mld snooping (3) Yamaha(config-if)#ipv6 mld snooping querier (4) Yamaha(config-if)#ipv6 mld snooping query-interval 20 (5) 1 Define VLAN #10 2 Enable the IPv6 function for VLAN #10 3 Enable MLD Snooping for VLAN #10 4 Enable the MLD query transmission function for VLAN #10 5 Set the MLD query transmission interval for VLAN #10 to 20 sec. Since MLD snooping is enabled by default, we do not need to set this specifically. [Switch #A] Set LAN ports #1–#2 as access ports, and associate them with VLAN #10. Yamaha(config)# interface port1.1Yamaha(config-if)# switchport mode accessYamaha(config-if)# switchport access vlan 10 (1) 1 Configure the settings above for LAN port #2 as well. [Switch #B] Define VLAN #10, and set MLD snooping. Yamaha(config)# vlan databaseYamaha(config-vlan)#vlan 10 (1) Yamaha(config-vlan)#exitYamaha(config)#interface vlan10Yamaha(config-if)#ipv6 enable (2) Yamaha(config-if)#ipv6 mld snooping (3) Yamaha(config-if)#no ipv6 mld snooping querier (4) Yamaha(config-if)#ipv6 mld snooping fast-leave (5) 1 Define VLAN #10 2 Enable the IPv6 function for VLAN #10 3 Enable MLD Snooping for VLAN #10 4 Disable the MLD query transmission function for VLAN #10 5 Enable the MLD fast leave function for VLAN #10 MLD snooping is enabled and the MLD query transmission function is disabled in default settings, so there is no need to specify those settings. [Switch #B] Set LAN ports #1–#4 as access ports, and associate them with VLAN #10. Yamaha(config)# interface port1.1Yamaha(config-if)# switchport mode accessYamaha(config-if)# switchport access vlan 10 (1) 1 Configure the settings above for LAN ports #2–#4 as well. [Switch #B] Check the multicast router port information. (It should be connected to LAN port #1.) Yamaha#show ipv6 mld snooping mrouter vlan10VLAN    Interface             IP-address    Expires10      port1.1(dynamic)         fe80::2a0:deff:feae:b879        00:00:43 [Switch #B] Check the multicast receiver information. Yamaha#show ipv6 mld snooping groupsMLD Connected Group MembershipVlan   Group Address                           Interface            Uptime   Expires  Last Reporter10     ff15::1                                 port1.2              00:00:13 00:00:41 fe80::a00:27ff:fe8b:87e210     ff15::1                                 port1.4              00:00:02 00:00:48 fe80::a00:27ff:fe8b:87e4</div></div><div id="ipmcast_ipmcast_mld_snooping"><div class="search_title" docfname="ipmcast_ipmcast_mld_snooping" doctitle="MLD" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution if you want to change the handling of unknown multicast frames, use the l2-unknown-mcast command. when a topology change is detected, if you want to send a query regardless of the normal transmission interval, set the l2-mcast snooping tcn-query command. if the stack function is enabled, this will be disabled regardless of the mld snooping settings.</div><div class="display_word">6. Points of Caution If you want to change the handling of unknown multicast frames, use the l2-unknown-mcast command. When a topology change is detected, if you want to send a query regardless of the normal transmission interval, set the l2-mcast snooping tcn-query command. If the stack function is enabled, this will be disabled regardless of the MLD snooping settings.</div></div><div id="ipmcast_ipmcast_mld_snooping"><div class="search_title" docfname="ipmcast_ipmcast_mld_snooping" doctitle="MLD" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation layer 2 function: vlan layer 3 functions: basic ipv6 settings</div><div class="display_word">7. Related Documentation Layer 2 Function: VLAN Layer 3 Functions: Basic IPv6 Settings</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#dhcpスヌーピング">DHCP Snooping</div><div class="search_word">dhcp snooping</div><div class="display_word">DHCP Snooping</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview the dhcp snooping function monitors dhcp messages exchanged between the dhcp server and clients to filter out any invalid dhcp messages. using the function can be expected to improve security in the following ways. deters assignment of ip addresses from invalid dhcp servers. deters releasing ip addresses from invalid dhcp clients or detecting multiple ip addresses. deters spoofed mac addresses. deters spoofed option 82 actions.</div><div class="display_word">1. Function Overview The DHCP snooping function monitors DHCP messages exchanged between the DHCP server and clients to filter out any invalid DHCP messages. Using the function can be expected to improve security in the following ways. Deters assignment of IP addresses from invalid DHCP servers. Deters releasing IP addresses from invalid DHCP clients or detecting multiple IP addresses. Deters spoofed MAC addresses. Deters spoofed Option 82 actions.</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used trusted port ports for which dhcp message filtering by dhcp snooping is disabled. it connects to a trusted dhcp server. untrusted port ports for which dhcp message filtering by dhcp snooping is enabled. it connects to dhcp clients. ifindex interface id number. for ifindex allocation, refer to basic interface functions .</div><div class="display_word">2. Definition of Terms Used Trusted port Ports for which DHCP message filtering by DHCP snooping is disabled. It connects to a trusted DHCP server. Untrusted port Ports for which DHCP message filtering by DHCP snooping is enabled. It connects to DHCP clients. IfIndex Interface ID number. For IfIndex allocation, refer to Basic Interface Functions .</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#dhcpスヌーピングの有効化">3.1. Enabling DHCP snooping</div><div class="search_word">3.1. enabling dhcp snooping to enable dhcp snooping, execute the ip dhcp snooping enable command in the global configuration mode. in addition, the ip dhcp snooping enable command must be executed in the interface mode for vlans where dhcp snooping is to be enabled. the status of system settings for the dhcp snooping function can be checked using the show ip dhcp snooping command. the interface setting status for the dhcp snooping function can be checked using the show ip dhcp snooping interface command.</div><div class="display_word">3.1. Enabling DHCP snooping To enable DHCP snooping, execute the ip dhcp snooping enable command in the global configuration mode. In addition, the ip dhcp snooping enable command must be executed in the interface mode for VLANs where DHCP snooping is to be enabled. The status of system settings for the DHCP snooping function can be checked using the show ip dhcp snooping command. The interface setting status for the DHCP snooping function can be checked using the show ip dhcp snooping interface command.</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#バインディングデータベース">3.2. Binding database</div><div class="search_word">3.2. binding database if dhcp snooping is enabled, messages between the dhcp server and dhcp client can be monitored to build a binding database. when the dhcp server assigns an ip address, the following dhcp client information is registered in the binding database. id numbers of vlans that received dhcp message from dhcp client interface information for dhcp messages received from dhcp client dhcp client mac address dhcp client ip address lease time entry information for the binding database can be checked using the show ip dhcp snooping binding command. registered entry information is deleted when the entry lease time is finished or when a dhcp release message is received from the dhcp client. the binding database can be cleared using the clear ip dhcp snooping binding command. a maximum of 512 entries can be registered in the binding database.</div><div class="display_word">3.2. Binding database If DHCP snooping is enabled, messages between the DHCP server and DHCP client can be monitored to build a binding database. When the DHCP server assigns an IP address, the following DHCP client information is registered in the binding database. ID numbers of VLANs that received DHCP message from DHCP client Interface information for DHCP messages received from DHCP client DHCP client MAC address DHCP client IP address Lease time Entry information for the binding database can be checked using the show ip dhcp snooping binding command. Registered entry information is deleted when the entry lease time is finished or when a DHCP release message is received from the DHCP client. The binding database can be cleared using the clear ip dhcp snooping binding command. A maximum of 512 entries can be registered in the binding database.</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#dhcpスヌーピングのポート種別">3.3. DHCP snooping by port type</div><div class="search_word">3.3. dhcp snooping by port type the ip dhcp snooping trust command can be used for dhcp snooping at two types of lan/sfp ports, either “trusted” or “untrusted” ports. trusted ports connect to trusted dhcp servers, whereas untrusted ports connect dhcp clients. the actions specified for each are described below. trusted port dhcp messages are forwarded without filtering. untrusted port dhcp packets sent from a dhcp server are discarded. if a mac address is registered in the binding database and the following dhcp packets are received from a different interface than the registered interface, then the corresponding dhcp packets are discarded. ip address release request (dhcp release) notification that a duplicate ip address was detected (dhcp decline) if mac address verification is enabled, the mac address of the dhcp packet sender is compared to the client hardware address (chaddr). if the addresses do not match, then the corresponding dhcp packets are discarded. if option 82 is enabled and dhcp packets received from a dhcp client are already appended with option 82 information, then the corresponding dhcp packets are discarded. at untrusted ports, mac address verification is enabled by default, but can be disabled using the ip dhcp snooping verify mac-address command. if a dhcp agent needs to be connected to an untrusted port, mac address verification must be disabled because the dhcp agent will overwrite the mac address of dhcp clients sending dhcp packets.</div><div class="display_word">3.3. DHCP snooping by port type The ip dhcp snooping trust command can be used for DHCP snooping at two types of LAN/SFP ports, either “trusted” or “untrusted” ports. Trusted ports connect to trusted DHCP servers, whereas untrusted ports connect DHCP clients. The actions specified for each are described below. Trusted port DHCP messages are forwarded without filtering. Untrusted port DHCP packets sent from a DHCP server are discarded. If a MAC address is registered in the binding database and the following DHCP packets are received from a different interface than the registered interface, then the corresponding DHCP packets are discarded. IP address release request (DHCP release) Notification that a duplicate IP address was detected (DHCP decline) If MAC address verification is enabled, the MAC address of the DHCP packet sender is compared to the client hardware address (chaddr). If the addresses do not match, then the corresponding DHCP packets are discarded. If Option 82 is enabled and DHCP packets received from a DHCP client are already appended with Option 82 information, then the corresponding DHCP packets are discarded. At untrusted ports, MAC address verification is enabled by default, but can be disabled using the ip dhcp snooping verify mac-address command. If a DHCP agent needs to be connected to an untrusted port, MAC address verification must be disabled because the DHCP agent will overwrite the MAC address of DHCP clients sending DHCP packets.</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#option-82">3.4. Option 82</div><div class="search_word">3.4. option 82 if option 82 is enabled when dhcp snooping is enabled, then option 82 information is appended to dhcp packets received from dhcp clients at untrusted ports. if a dhcp client is connected directly to an untrusted port, option 82 information is deleted from return packets sent from the dhcp server to the dhcp client before forwarding. option 82 is enabled by default. the following option 82 information is appended to packets. remote-id with default settings, packets are appended with the mac address for the given unit. format: suboption type=2, remote-id type=0 (default) the ip dhcp snooping information option format remote-id command can be used to append remote-id values with any string (single-byte characters or symbols) up to 63 characters long. format: suboption type=2, remote-id type=1 circuit-id with default settings, dhcp packets received from dhcp clients are appended with vlan id and ifindex information. format: suboption type=1, circuit-id type=2 (default) the ip dhcp snooping information option format-type circuit-id command can be used to change circuit-id information to vlan id and port number information for dhcp packets received from dhcp clients. for physical ports, “module” values are appended with the stack number or with a “1” setting for standalone or non-stack-compatible models. for logical ports, fixed static “0x11” and lacp “0x12” settings are specified. “port” values are appended with the physical port number. format: suboption type=1, circuit-id type=0 any character string (single-byte characters or symbols) up to 63 characters long can also be specified for circuit-id values. format: suboption type=1, circuit-id type=1 subscriber-id not appended with default settings. the ip dhcp snooping subscriber-id command can be used to specify any string (single-byte characters or symbols) up to 50 characters long for subscriber-id values at applicable ports and include the string in option 82 information. if option 82 is enabled and a dhcp packet already appended with option 82 information is received at an untrusted port, that packet is discarded to deter spoofing of option 82 information. in order to connect a dhcp relay agent appended with option 82 to an untrusted port, the ip dhcp snooping information option allow-untrusted command must be executed to allow forwarding dhcp packets that include option 82 at untrusted ports.</div><div class="display_word">3.4. Option 82 If Option 82 is enabled when DHCP snooping is enabled, then Option 82 information is appended to DHCP packets received from DHCP clients at untrusted ports. If a DHCP client is connected directly to an untrusted port, Option 82 information is deleted from return packets sent from the DHCP server to the DHCP client before forwarding. Option 82 is enabled by default. The following Option 82 information is appended to packets. Remote-ID With default settings, packets are appended with the MAC address for the given unit. Format: Suboption type=2, Remote-ID type=0 (Default) The ip dhcp snooping information option format remote-id command can be used to append Remote-ID values with any string (single-byte characters or symbols) up to 63 characters long. Format: Suboption type=2, Remote-ID type=1 Circuit-ID With default settings, DHCP packets received from DHCP clients are appended with VLAN ID and IfIndex information. Format: Suboption type=1, Circuit-ID type=2 (Default) The ip dhcp snooping information option format-type circuit-id command can be used to change circuit-ID information to VLAN ID and port number information for DHCP packets received from DHCP clients. For physical ports, “Module” values are appended with the stack number or with a “1” setting for standalone or non-stack-compatible models. For logical ports, fixed static “0x11” and LACP “0x12” settings are specified. “Port” values are appended with the physical port number. Format: Suboption type=1, Circuit-ID type=0 Any character string (single-byte characters or symbols) up to 63 characters long can also be specified for Circuit-ID values. Format: Suboption type=1, Circuit-ID type=1 Subscriber-ID Not appended with default settings. The ip dhcp snooping subscriber-id command can be used to specify any string (single-byte characters or symbols) up to 50 characters long for subscriber-ID values at applicable ports and include the string in Option 82 information. If Option 82 is enabled and a DHCP packet already appended with Option 82 information is received at an untrusted port, that packet is discarded to deter spoofing of Option 82 information. In order to connect a DHCP relay agent appended with Option 82 to an untrusted port, the ip dhcp snooping information option allow-untrusted command must be executed to allow forwarding DHCP packets that include Option 82 at untrusted ports.</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#dhcpパケットのレート制限">3.5. DHCP packet rate limits</div><div class="search_word">3.5. dhcp packet rate limits if dhcp snooping is enabled, the ip dhcp snooping limit rate command can be used to specify the maximum number of dhcp packets that can be received per second by the overall system. if more than the maximum dhcp packets allowed by the limit rate are received, all dhcp packets that exceed the limit rate are discarded. a limit rate is not specified in default settings.</div><div class="display_word">3.5. DHCP packet rate limits If DHCP snooping is enabled, the ip dhcp snooping limit rate command can be used to specify the maximum number of DHCP packets that can be received per second by the overall system. If more than the maximum DHCP packets allowed by the limit rate are received, all DHCP packets that exceed the limit rate are discarded. A limit rate is not specified in default settings.</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#dhcpスヌーピングの統計情報">3.6. DHCP snooping statistical information</div><div class="search_word">3.6. dhcp snooping statistical information statistics about dhcp packets discarded by dhcp snooping can be checked using the show ip dhcp snooping statistics command. however, that statistical information does not include statistics on dhcp packets discarded due to the limit rate. the statistical information can be deleted using the clear ip dhcp snooping statistics command.</div><div class="display_word">3.6. DHCP snooping statistical information Statistics about DHCP packets discarded by DHCP snooping can be checked using the show ip dhcp snooping statistics command. However, that statistical information does not include statistics on DHCP packets discarded due to the limit rate. The statistical information can be deleted using the clear ip dhcp snooping statistics command.</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#syslogへの出力">3.7. SYSLOG output</div><div class="search_word">3.7. syslog output if dhcp packets are discarded due to a dhcp snooping inspection of dhcp packets received, the reason for discarding the packets can be included in info level syslog output. the syslog output enable/disable setting can be specified using the ip dhcp snooping logging command. syslog output is enabled in default settings. the following syslog messages are output. level output conditions syslog message info dhcp server packet received at untrusted port. 2022/07/21 09:00:00: [dhcpsn]:inf: dhcp dropped due to prohibited message type, vlan 1, port1.1, dhcpoffer, 1234.4567.abcd info dhcp release/decline request was received from an unregistered interface. 2022/07/21 09:00:00: [dhcpsn]:inf: dhcp dropped due to source interface mismatch, vlan 1, port1.1, dhcprelease, 5c5a.c7d6.9e1e info sender mac and chaddr information do not match. 2022/07/21 09:00:00: [dhcpsn]:inf: dhcp dropped due to source mac mismatch, vlan 1, port1.1, dhcpinform, 001c.4321.abcd info packet appended with option 82 was received at untrusted port. 2022/07/21 09:00:00: [dhcpsn]:inf: dhcp dropped due to option82 value, vlan 1, port1.1, dhcpinform, 5c5a.c7d6.9e1e</div><div class="display_word">3.7. SYSLOG output If DHCP packets are discarded due to a DHCP snooping inspection of DHCP packets received, the reason for discarding the packets can be included in INFO level SYSLOG output. The SYSLOG output enable/disable setting can be specified using the ip dhcp snooping logging command. SYSLOG output is enabled in default settings. The following SYSLOG messages are output. Level Output conditions SYSLOG Message INFO DHCP server packet received at untrusted port. 2022/07/21 09:00:00: [DHCPSN]:inf: DHCP dropped due to prohibited message type, VLAN 1, port1.1, DHCPOFFER, 1234.4567.abcd INFO DHCP RELEASE/DECLINE request was received from an unregistered interface. 2022/07/21 09:00:00: [DHCPSN]:inf: DHCP dropped due to source interface mismatch, VLAN 1, port1.1, DHCPRELEASE, 5c5a.c7d6.9e1e INFO Sender MAC and chaddr information do not match. 2022/07/21 09:00:00: [DHCPSN]:inf: DHCP dropped due to source mac mismatch, VLAN 1, port1.1, DHCPINFORM, 001c.4321.abcd INFO Packet appended with Option 82 was received at untrusted port. 2022/07/21 09:00:00: [DHCPSN]:inf: DHCP dropped due to option82 value, VLAN 1, port1.1, DHCPINFORM, 5c5a.c7d6.9e1e</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. operations operating commands enable/disable setting for dhcp snooping (system) ip dhcp snooping enable/disable enable/disable setting for dhcp snooping (vlan) ip dhcp snooping enable/disable dhcp snooping port type setting ip dhcp snooping trust enable/disable setting for mac address verification ip dhcp snooping verify mac-address enable/disable enable/disable setting for option 82 ip dhcp snooping information option enable/disable setting for allowing packets appended with option 82 to be received at untrusted ports ip dhcp snooping information option allow-untrusted remote-id setting for option 82 ip dhcp snooping information option format remote-id circuit-id setting for option 82 ip dhcp snooping information option format-type circuit-id subscriber-id setting ip dhcp snooping subscriber-id dhcp packet receiving limit rate setting ip dhcp snooping limit rate enable/disable setting for syslog output when dhcp packets are discarded ip dhcp snooping logging enable/disable shows dhcp snooping system setting information show ip dhcp snooping shows dhcp snooping interface settings information show ip dhcp snooping interface display binding database show ip dhcp snooping binding shows dhcp snooping statistical information show ip dhcp snooping statistics clears binding database clear ip dhcp snooping binding clears dhcp snooping statistical information clear ip dhcp snooping statistics</div><div class="display_word">4. Related Commands Related commands are indicated below. Operations Operating commands Enable/disable setting for DHCP snooping (system) ip dhcp snooping enable/disable Enable/disable setting for DHCP snooping (VLAN) ip dhcp snooping enable/disable DHCP snooping port type setting ip dhcp snooping trust Enable/disable setting for MAC address verification ip dhcp snooping verify mac-address enable/disable Enable/disable setting for Option 82 ip dhcp snooping information option enable/disable Setting for allowing packets appended with Option 82 to be received at untrusted ports ip dhcp snooping information option allow-untrusted Remote-ID setting for Option 82 ip dhcp snooping information option format remote-id Circuit-ID setting for Option 82 ip dhcp snooping information option format-type circuit-id Subscriber-ID setting ip dhcp snooping subscriber-id DHCP packet receiving limit rate setting ip dhcp snooping limit rate Enable/disable setting for SYSLOG output when DHCP packets are discarded ip dhcp snooping logging enable/disable Shows DHCP snooping system setting information show ip dhcp snooping Shows DHCP snooping interface settings information show ip dhcp snooping interface Display Binding Database show ip dhcp snooping binding Shows DHCP snooping statistical information show ip dhcp snooping statistics Clears binding database clear ip dhcp snooping binding Clears DHCP snooping statistical information clear ip dhcp snooping statistics</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#信頼するインターフェースを指定">5.1. Designating trusted interfaces</div><div class="search_word">5.1. designating trusted interfaces this specifies trusted interfaces (lan port #1) for connecting dhcp servers. yamaha(config)#interface port1.1yamaha(config-if)#ip dhcp snooping trustyamaha(config-if)#exit</div><div class="display_word">5.1. Designating trusted interfaces This specifies trusted interfaces (LAN port #1) for connecting DHCP servers. Yamaha(config)#interface port1.1Yamaha(config-if)#ip dhcp snooping trustYamaha(config-if)#exit</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#dhcpスヌーピングの有効化">5.2. Enabling DHCP snooping</div><div class="search_word">5.2. enabling dhcp snooping this enables dhcp snooping for the system and vlan #1. yamaha(config)#ip dhcp snooping enableyamaha(config)#interface vlan1yamaha(config-if)#ip dhcp snooping enableyamaha(config-if)#exit</div><div class="display_word">5.2. Enabling DHCP snooping This enables DHCP snooping for the system and VLAN #1. Yamaha(config)#ip dhcp snooping enableYamaha(config)#interface vlan1Yamaha(config-if)#ip dhcp snooping enableYamaha(config-if)#exit</div></div><div id="layer2_layer2_dhcp_snooping"><div class="search_title" docfname="layer2_layer2_dhcp_snooping" doctitle="DHCP" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution none</div><div class="display_word">6. Points of Caution None</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#フォワーディングデータベースfdb">Forwarding Database (FDB)</div><div class="search_word">forwarding database (fdb)</div><div class="display_word">Forwarding Database (FDB)</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview the forwarding database (subsequently referred to as the fdb) manages the combination of destination mac addresses, transmission ports, and vlans. this product uses the fdb to determine the forwarding destination port for the received frames. enable/disable acquisition function hold time adjustment for fdb entries acquired timeout clear for fdb entries acquired manual registration of fdb entries (static entries)</div><div class="display_word">1. Function Overview The Forwarding Database (subsequently referred to as the FDB) manages the combination of destination MAC addresses, transmission ports, and VLANs. This product uses the FDB to determine the forwarding destination port for the received frames. Enable/disable acquisition function Hold Time adjustment for FDB entries acquired Timeout clear for FDB entries acquired Manual registration of FDB entries (static entries)</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used fdb abbreviation of “forwarding data base.” this database manages the combination of destination mac address, transmission port, and vlan. fdb entry this is data registered in the fdb, and consists of multiple elements.</div><div class="display_word">2. Definition of Terms Used FDB Abbreviation of “Forwarding Data Base.” This database manages the combination of destination MAC address, transmission port, and VLAN. FDB entry This is data registered in the FDB, and consists of multiple elements.</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#fdbエントリー">3.1. FDB entry</div><div class="search_word">3.1. fdb entry on this product, the contents listed in the table below are registered as a single entry in the fdb. up to 16,384 addresses can be registered, including addresses registered via automatic acquisition and manual registration. element managed description mac address device mac addresses can be either unicast or multicast. vlan-id (fid) the vlan id to which the device belongs. this is a value from 1–4094. forwarding destination interface id the interface on which the device exists. lan/sfp ports are static/lacp logical interfaces. action the processing method for frames addressed to the device. there are two processing methods, “discard” and “forward”. entry registration type dynamic entries registered through automatic acquisition static entries registered manually via commands multicast entries acquired by igmp/mld snooping</div><div class="display_word">3.1. FDB entry On this product, the contents listed in the table below are registered as a single entry in the FDB. Up to 16,384 addresses can be registered, including addresses registered via automatic acquisition and manual registration. Element managed Description MAC address Device MAC addresses can be either unicast or multicast. VLAN-ID (FID) The VLAN ID to which the device belongs. This is a value from 1–4094. Forwarding destination interface ID The interface on which the device exists. LAN/SFP ports are static/LACP logical interfaces. Action The processing method for frames addressed to the device. There are two processing methods, “discard” and “forward”. Entry registration type dynamic Entries registered through automatic acquisition static Entries registered manually via commands multicast Entries acquired by IGMP/MLD Snooping</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#macアドレス">3.1.1. MAC address</div><div class="search_word">3.1.1. mac address this is one of the fdb key items; the vlan-id and mac address are combined to become the record key. operation differs depending on whether the mac address is unicast or multicast. unicast since the forwarding destination interface id must be uniquely determined for a given record key, duplication is not allowed. (multiple combinations of the same vlan-id and mac address do not exist.) multicast multiple forwarding destination interface ids may exist for a given key record. in this case, frames are sent to multiple forwarding destination interface ids. the mac addresses of all received frames can be acquired, and the source mac address is acquired and registered in the fdb. however, if the transmission source mac address is multicast, this is considered an invalid frame and is discarded without being registered. each vlan interface created internally consumes one fdb entry. automatically acquired mac address information is maintained until the ageing timeout. if multiple multicast mac addresses are specified, all are considered as one in this case. vlan  port    mac             fwd      type    timeout   1  port1.1 0100.0000.1000  forward  static       0   1  port1.2 0100.0000.1000  forward  static       0   1  port1.3 0100.0000.1000  forward  static       0   1  port1.4 0100.0000.1000  forward  static       0   1  port1.5 0100.0000.1000  forward  static       0   1  port1.6 0100.0000.1000  forward  static       0</div><div class="display_word">3.1.1. MAC address This is one of the FDB key items; the VLAN-ID and MAC address are combined to become the record key. Operation differs depending on whether the MAC address is unicast or multicast. Unicast Since the forwarding destination interface ID must be uniquely determined for a given record key, duplication is not allowed. (Multiple combinations of the same VLAN-ID and MAC address do not exist.) Multicast Multiple forwarding destination interface IDs may exist for a given key record. In this case, frames are sent to multiple forwarding destination interface IDs. The MAC addresses of all received frames can be acquired, and the source MAC address is acquired and registered in the FDB. However, if the transmission source MAC address is multicast, this is considered an invalid frame and is discarded without being registered. Each VLAN interface created internally consumes one FDB entry. Automatically acquired MAC address information is maintained until the ageing timeout. If multiple multicast MAC addresses are specified, all are considered as one in this case. VLAN  port    mac             fwd      type    timeout   1  port1.1 0100.0000.1000  forward  static       0   1  port1.2 0100.0000.1000  forward  static       0   1  port1.3 0100.0000.1000  forward  static       0   1  port1.4 0100.0000.1000  forward  static       0   1  port1.5 0100.0000.1000  forward  static       0   1  port1.6 0100.0000.1000  forward  static       0</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#vlan-id">3.1.2. VLAN-ID</div><div class="search_word">3.1.2. vlan-id mac address acquisition is done per vlan, and the mac address and vlan are managed in the fdb as a pair. for different vlans, identical mac addresses are also acquired.</div><div class="display_word">3.1.2. VLAN-ID MAC address acquisition is done per VLAN, and the MAC address and VLAN are managed in the FDB as a pair. For different VLANs, identical MAC addresses are also acquired.</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#転送先インターフェースid">3.1.3. Forwarding destination interface ID</div><div class="search_word">3.1.3. forwarding destination interface id the following ids are registered. lan/sfp port (port) static/lacp logical interface (sa,po)</div><div class="display_word">3.1.3. Forwarding destination interface ID The following IDs are registered. LAN/SFP port (port) Static/LACP logical interface (sa,po)</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#アクション">3.1.4. Action</div><div class="search_word">3.1.4. action this defines the action for a received frame that matches a key record. if the mac address is unicast, the actions are as follows. forward ... forward to the forwarding destination interface id. discard ... discard without forwarding. if the mac address is multicast, the actions are as follows. forward ... forward to the forwarding destination interface id. discard ... cannot be specified. (the discard setting cannot be made if the mac address is multicast.)</div><div class="display_word">3.1.4. Action This defines the action for a received frame that matches a key record. If the MAC address is unicast, the actions are as follows. forward ... Forward to the forwarding destination interface ID. discard ... Discard without forwarding. If the MAC address is multicast, the actions are as follows. forward ... Forward to the forwarding destination interface ID. discard ... Cannot be specified. (The discard setting cannot be made if the MAC address is multicast.)</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#登録種別">3.1.5. Registration type</div><div class="search_word">3.1.5. registration type dynamic …​ registered and deleted automatically. the registration result does not remain in the config settings file. static …​ registered and deleted manually, and therefore remains in the config settings file. multicast …​ automatically registered and deleted by the igmp/mld snooping function. the registration result does not remain in the config settings file.</div><div class="display_word">3.1.5. Registration type dynamic …​ Registered and deleted automatically. The registration result does not remain in the config settings file. static …​ Registered and deleted manually, and therefore remains in the config settings file. multicast …​ Automatically registered and deleted by the IGMP/MLD snooping function. The registration result does not remain in the config settings file.</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#macアドレスの自動学習">3.2. Automatic MAC address acquisition</div><div class="search_word">3.2. automatic mac address acquisition automatic mac address acquisition refers to the active creation and registration of fdb entries based on the information for the source mac address of the received frame and the information for the reception port. entries registered through automatic acquisition are called “dynamic entries”. a timer (ageing time) is used to monitor individual entries. entries for mac addresses that have not received frames within a certain amount of time will be automatically deleted from fdb entries by an aging timer. this prevents invalid device entries from being left over in the fdb due to power shutoff, being moved and so on. if a frame is received within the specified amount of time, the monitoring timer will be reset. the control specifications for automatic acquisition are shown below. automatic mac address acquisition can be enabled or disabled using the mac-address-table learning command. the setting is enabled by default. if automatic acquisition is changed from enabled to disabled, all dynamic entries that have been learned will be deleted . the acquisition function “disable” setting is useful when you want to flood all ports with all received frames. aging timer settings for dynamic entries are specified using mac-address-table ageing-time command. this value is set to 300 seconds by default. the actual time when entries are deleted by the aging time occurs within double the seconds specified as the timer setting value. clear the dynamic entries that have been acquired by using the clear mac-address-table dynamic command. the entire contents of the fdb can be cleared at once; or a vlan number can be specified and all mac addresses acquired by that vlan can be cleared from the fdb. specifying the port number will clear all mac addresses from the fdb that were acquired from that port. use the show mac-address-table command to check the automatic acquisition status.</div><div class="display_word">3.2. Automatic MAC address acquisition Automatic MAC address acquisition refers to the active creation and registration of FDB entries based on the information for the source MAC address of the received frame and the information for the reception port. Entries registered through automatic acquisition are called “dynamic entries”. A timer (ageing time) is used to monitor individual entries. Entries for MAC addresses that have not received frames within a certain amount of time will be automatically deleted from FDB entries by an aging timer. This prevents invalid device entries from being left over in the FDB due to power shutoff, being moved and so on. If a frame is received within the specified amount of time, the monitoring timer will be reset. The control specifications for automatic acquisition are shown below. Automatic MAC address acquisition can be enabled or disabled using the mac-address-table learning command. The setting is enabled by default. If automatic acquisition is changed from enabled to disabled, all dynamic entries that have been learned will be deleted . The acquisition function “disable” setting is useful when you want to flood all ports with all received frames. Aging timer settings for dynamic entries are specified using mac-address-table ageing-time command. This value is set to 300 seconds by default. The actual time when entries are deleted by the aging time occurs within double the seconds specified as the timer setting value. Clear the dynamic entries that have been acquired by using the clear mac-address-table dynamic command. The entire contents of the FDB can be cleared at once; or a VLAN number can be specified and all MAC addresses acquired by that VLAN can be cleared from the FDB. Specifying the port number will clear all MAC addresses from the FDB that were acquired from that port. Use the show mac-address-table command to check the automatic acquisition status.</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#macアドレスの手動設定">3.3. MAC address manual setting</div><div class="search_word">3.3. mac address manual setting in addition to automatic acquisition using received frames, mac addresses can be set on this product by using user commands. entries that have been registered by using commands are called “static entries”. the specifications for manual settings are shown below. use the mac-address-table static command to register static entries. when registering static entries, dynamic acquisition will not be performed on the corresponding mac addresses. entries that have already been acquired will be deleted from the fdb, and will be registered as static entries. use the no mac-address-table static command to delete static entries. either “forward” or “discard” can be specified for the destination mac address of a received frame. when forwarding is specified, either the lan/sfp port forwarding destination or the static/lacp logical interface can be specified. when discarding is specified, frames received by the mac address will not be forwarded to any port, and will be discarded. if registering a multicast mac address, you cannot specify “discard.” also, the following mac addresses cannot be registered. 0000.0000.0000 0100.5e00.0000～0100.5eff.ffff 0180.c200.0000–0180.c200.000f 0180.c200.0020–0180.c200.002f 3333.0000.0000～3333.ffff.ffff ffff.ffff.ffff</div><div class="display_word">3.3. MAC address manual setting In addition to automatic acquisition using received frames, MAC addresses can be set on this product by using user commands. Entries that have been registered by using commands are called “static entries”. The specifications for manual settings are shown below. Use the mac-address-table static command to register static entries. When registering static entries, dynamic acquisition will not be performed on the corresponding MAC addresses. Entries that have already been acquired will be deleted from the FDB, and will be registered as static entries. Use the no mac-address-table static command to delete static entries. Either “forward” or “discard” can be specified for the destination MAC address of a received frame. When forwarding is specified, either the LAN/SFP port forwarding destination or the static/LACP logical interface can be specified. When discarding is specified, frames received by the MAC address will not be forwarded to any port, and will be discarded. If registering a multicast MAC address, you cannot specify “discard.” Also, the following MAC addresses cannot be registered. 0000.0000.0000 0100.5e00.0000～0100.5eff.ffff 0180.c200.0000–0180.c200.000f 0180.c200.0020–0180.c200.002f 3333.0000.0000～3333.ffff.ffff ffff.ffff.ffff</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands operations operating commands enable/disable the mac address learning function mac-address-table learning set dynamic entry ageing time mac-address-table ageing-time delete dynamic entries clear mac-address-table dynamic register static entries mac-address-table static delete static entries no mac-address-table static view the mac address table show mac-address-table</div><div class="display_word">4. Related Commands Operations Operating commands Enable/disable the MAC address learning function mac-address-table learning Set dynamic entry ageing time mac-address-table ageing-time Delete dynamic entries clear mac-address-table dynamic Register static entries mac-address-table static Delete static entries no mac-address-table static View the MAC address table show mac-address-table</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#fdbの参照">5.1. Referring to the FDB</div><div class="search_word">5.1. referring to the fdb yamaha#show mac-address-tablevlan  port     mac             fwd      type     timeout   1  port1.2  00a0.de11.2233  forward  static        0   1  port1.1  1803.731e.8c2b  forward  dynamic     300   1  port1.1  782b.cbcb.218d  forward  dynamic     300</div><div class="display_word">5.1. Referring to the FDB Yamaha#show mac-address-tableVLAN  port     mac             fwd      type     timeout   1  port1.2  00a0.de11.2233  forward  static        0   1  port1.1  1803.731e.8c2b  forward  dynamic     300   1  port1.1  782b.cbcb.218d  forward  dynamic     300</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#ダイナミックエントリーの削除">5.2. Delete dynamic entries</div><div class="search_word">5.2. delete dynamic entries deleting an fdb entry registered in the fdb (mac address 00:a0:de:11:22:33) yamaha#clear mac-address-table dynamic address 00a0.de11.2233</div><div class="display_word">5.2. Delete dynamic entries Deleting an FDB entry registered in the FDB (MAC address 00:a0:de:11:22:33) Yamaha#clear mac-address-table dynamic address 00a0.de11.2233</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#ダイナミックエントリー-エージング時間の変更">5.3. Changing the dynamic entry ageing time</div><div class="search_word">5.3. changing the dynamic entry ageing time this example shows how to change the dynamic entry ageing time to 400 seconds. yamaha(config)#mac-address-table ageing-time 400</div><div class="display_word">5.3. Changing the dynamic entry ageing time This example shows how to change the dynamic entry ageing time to 400 seconds. Yamaha(config)#mac-address-table ageing-time 400</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#スタティックエントリーの登録">5.4. Register static entries</div><div class="search_word">5.4. register static entries this example shows how frames addressed to a device associated with vlan #10 (mac address 00:a0:de:11:22:33) can be forwarded to lan port 2 (port1.2). yamaha(config)#mac-address-table static 00a0.de11.2233 forward port1.2 vlan 10 this example shows how to discard the frames sent to a device associated with vlan #10 (mac address 00:a0:de:11:22:33). specifying the interface name (“port1.2” in the example) will have no effect on operations. since this cannot be omitted, specify the lan/sfp port. yamaha(config)#mac-address-table static 00a0.de11.2233 discard port1.2 vlan 10</div><div class="display_word">5.4. Register static entries This example shows how frames addressed to a device associated with VLAN #10 (MAC address 00:a0:de:11:22:33) can be forwarded to LAN port 2 (port1.2). Yamaha(config)#mac-address-table static 00a0.de11.2233 forward port1.2 vlan 10 This example shows how to discard the frames sent to a device associated with VLAN #10 (MAC address 00:a0:de:11:22:33). Specifying the interface name (“port1.2” in the example) will have no effect on operations. Since this cannot be omitted, specify the LAN/SFP port. Yamaha(config)#mac-address-table static 00a0.de11.2233 discard port1.2 vlan 10</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#スタティックエントリーの削除">5.5. Delete static entries</div><div class="search_word">5.5. delete static entries this example shows how to delete the forwarding settings sent to a device associated with vlan #10 (mac address 00:a0:de:11:22:33). yamaha(config)#no mac-address-table static 00a0.de11.2233 forward port1.2 vlan 10</div><div class="display_word">5.5. Delete static entries This example shows how to delete the forwarding settings sent to a device associated with VLAN #10 (MAC address 00:a0:de:11:22:33). Yamaha(config)#no mac-address-table static 00a0.de11.2233 forward port1.2 vlan 10</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution if the l2-unknown-mcast command is configured to discard unknown multicast frames, using the mac-address-table static command to passively forward a multicast mac address will have no effect when registered.</div><div class="display_word">6. Points of Caution If the l2-unknown-mcast command is configured to discard unknown multicast frames, using the mac-address-table static command to passively forward a multicast MAC address will have no effect when registered.</div></div><div id="layer2_layer2_fdb"><div class="search_title" docfname="layer2_layer2_fdb" doctitle="Forwarding" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation none</div><div class="display_word">7. Related Documentation None</div></div><div id="layer2_layer2_loop_detect"><div class="search_title" docfname="layer2_layer2_loop_detect" doctitle="Unique" link="#独自ループ検出">Unique Loop Detection</div><div class="search_word">unique loop detection</div><div class="display_word">Unique Loop Detection</div></div><div id="layer2_layer2_loop_detect"><div class="search_title" docfname="layer2_layer2_loop_detect" doctitle="Unique" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product offers a proprietary system to detect whether there is a loop in the network environment that was configured. this sends a proprietary loop detection frame from lan/sfp ports and logical interfaces (hereinafter “loop detection-compatible interfaces”) to monitor whether that same frame returns or not. if the transmitted frame returns, the system determines that there is a loop in the port in question.</div><div class="display_word">1. Function Overview This product offers a proprietary system to detect whether there is a loop in the network environment that was configured. This sends a proprietary loop detection frame from LAN/SFP ports and logical interfaces (hereinafter “loop detection-compatible interfaces”) to monitor whether that same frame returns or not. If the transmitted frame returns, the system determines that there is a loop in the port in question.</div></div><div id="layer2_layer2_loop_detect"><div class="search_title" docfname="layer2_layer2_loop_detect" doctitle="Unique" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used ldf (loop detection frame) this is a yamaha proprietary ethernet frame that is used to detect loops.</div><div class="display_word">2. Definition of Terms Used LDF (Loop Detection Frame) This is a Yamaha proprietary Ethernet frame that is used to detect loops.</div></div><div id="layer2_layer2_loop_detect"><div class="search_title" docfname="layer2_layer2_loop_detect" doctitle="Unique" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="layer2_layer2_loop_detect"><div class="search_title" docfname="layer2_layer2_loop_detect" doctitle="Unique" link="#ループ検出-動作仕様">3.1. Loop detection operating specifications</div><div class="search_word">3.1. loop detection operating specifications the loop detection specifications for this product are shown below. the loop detection functionality in this product can be enabled/disabled for the entire system or for specific loop detection-compatible interfaces. to activate loop detection at all loop detection-compatible interfaces, the loop detection function must be enabled for the entire system. use the loop-detect command in global configuration mode for the system-wide setting. to activate loop detection at only specific loop detection-compatible interfaces, the loop-detect command must be used in the interface mode. the default settings for the loop detection function are as shown below. (in the initial state, this function is not operating.) system-wide setting: disabled setting for loop detection-compatible interfaces: enabled if both loop detection and spanning tree protocol settings are set to enabled for the entire system, the spanning tree protocol is prioritized over the loop detection-compatible interface setting. if the loop detection function is enabled for this product, the following operations are performed. loop detection frames (hereafter “ldf”) are sent every two seconds from linked-up loop detection-compatible interfaces. however, the loop detection function is disabled at ports with mirroring specified (mirror ports). if an ldf sent from a port is received by that same port, a loop is determined to have occurred and the port that received the ldf performs the following actions. port shutdown if an ldf is sent and received at the same loop detection-compatible interface, the corresponding port is shut down. the linkup will be made five minutes after shutdown, and ldf transmission will resume. (if a loop has occurred, this operation will repeat.) when a linkup to the relevant port is desired within five minutes of monitored time, the no shutdown command is used. port blocking in any of the following cases, the port that received the ldf will block all non-ldf frames. an ldf sent from a logical interface was received at a lan/sfp port an ldf sent from a static logical interface was received at an lacp logical interface sending or receiving interfaces are the same type and the interface with the higher number received an ldf the ldf will be transmitted periodically, but ldf will not be forwarded from other devices. if a blocked loop detection-compatible interface does not detect an ldf sent from itself for 5 seconds, then the loop is considered resolved and normal communications are resumed. port detected in any of the following cases, the port that received the ldf will continue normal communications because other ports are blocked. an ldf sent from a lan/sfp port was received at a logical interface an ldf sent from an lacp logical interface was received at a static logical interface sending and receiving interfaces are the same type and the interface with the smaller number received an ldf when a loop is detected, the port lamp display on this product changes to a dedicated status, and the following syslog message is output. [loop]: inf: detected loop! : port1.1, 1.3 …​ , sa1,3 …​, po1,3 <1> the port lamp display on this product is restored as communications are resumed after the loop is resolved, and the following syslog message is output. [loop]: inf: recovered loop! : port1.1, 1.3 … , sa1,3 …, po1,3 … shutdown and blocking actions at loop detection-compatible interfaces that have detected a loop can be overridden to perform “loop detected” actions. use the loop-detect blocking disable command for this setting. if this setting is “enabled”, port blocking will be implemented on the next largest port number. (shutdown operations will not occur.) a force-clear can be performed on the loop detection status (detected, blocking) by using the loop-detect reset command. (on models equipped with a [mode] button, this can be also done by holding down the [mode] button for three seconds.) if a linkdown has occurred on the port where a loop has been detected, the detection status will be cleared. (the port lamp display is restored, and the following syslog message is outputted.) the status of the loop detection function can be checked using the show loop-detect command. the following is displayed. system enable/disable status loop detection status display (status for a single loop detection-compatible interface) when an ldf is received by a loop detection-compatible interface when the loop detection function is disabled, frames received from all other ports will be forwarded as-is. however, forwarding is disabled at ports with mirroring specified (mirror ports). in the following kinds of situations, loops in hubs that are connected to this product might not be detected. loops are being detected in a connected hub loop detection frames are not being forwarded by a connected hub</div><div class="display_word">3.1. Loop detection operating specifications The loop detection specifications for this product are shown below. The loop detection functionality in this product can be enabled/disabled for the entire system or for specific loop detection-compatible interfaces. To activate loop detection at all loop detection-compatible interfaces, the loop detection function must be enabled for the entire system. Use the loop-detect command in global configuration mode for the system-wide setting. To activate loop detection at only specific loop detection-compatible interfaces, the loop-detect command must be used in the interface mode. The default settings for the loop detection function are as shown below. (In the initial state, this function is not operating.) System-wide setting: Disabled Setting for loop detection-compatible interfaces: Enabled If both loop detection and spanning tree protocol settings are set to enabled for the entire system, the spanning tree protocol is prioritized over the loop detection-compatible interface setting. If the loop detection function is enabled for this product, the following operations are performed. Loop detection frames (hereafter “LDF”) are sent every two seconds from linked-up loop detection-compatible interfaces. However, the loop detection function is disabled at ports with mirroring specified (mirror ports). If an LDF sent from a port is received by that same port, a loop is determined to have occurred and the port that received the LDF performs the following actions. Port Shutdown If an LDF is sent and received at the same loop detection-compatible interface, the corresponding port is shut down. The linkup will be made five minutes after shutdown, and LDF transmission will resume. (If a loop has occurred, this operation will repeat.) When a linkup to the relevant port is desired within five minutes of monitored time, the no shutdown command is used. Port Blocking In any of the following cases, the port that received the LDF will block all non-LDF frames. An LDF sent from a logical interface was received at a LAN/SFP port An LDF sent from a static logical interface was received at an LACP logical interface Sending or receiving interfaces are the same type and the interface with the higher number received an LDF The LDF will be transmitted periodically, but LDF will not be forwarded from other devices. If a blocked loop detection-compatible interface does not detect an LDF sent from itself for 5 seconds, then the loop is considered resolved and normal communications are resumed. Port Detected In any of the following cases, the port that received the LDF will continue normal communications because other ports are blocked. An LDF sent from a LAN/SFP port was received at a logical interface An LDF sent from an LACP logical interface was received at a static logical interface Sending and receiving interfaces are the same type and the interface with the smaller number received an LDF When a loop is detected, the port lamp display on this product changes to a dedicated status, and the following SYSLOG message is output. [LOOP]: inf: Detected Loop! : port1.1, 1.3 …​ , sa1,3 …​, po1,3 <1> The port lamp display on this product is restored as communications are resumed after the loop is resolved, and the following SYSLOG message is output. [LOOP]: inf: Recovered Loop! : port1.1, 1.3 … , sa1,3 …, po1,3 … Shutdown and blocking actions at loop detection-compatible interfaces that have detected a loop can be overridden to perform “loop detected” actions. Use the loop-detect blocking disable command for this setting. If this setting is “enabled”, port blocking will be implemented on the next largest port number. (Shutdown operations will not occur.) A force-clear can be performed on the loop detection status (detected, blocking) by using the loop-detect reset command. (On models equipped with a [MODE] button, this can be also done by holding down the [MODE] button for three seconds.) If a linkdown has occurred on the port where a loop has been detected, the detection status will be cleared. (The port lamp display is restored, and the following syslog message is outputted.) The status of the loop detection function can be checked using the show loop-detect command. The following is displayed. System Enable/disable status Loop detection status display (status for a single loop detection-compatible interface) When an LDF is received by a loop detection-compatible interface when the loop detection function is disabled, frames received from all other ports will be forwarded as-is. However, forwarding is disabled at ports with mirroring specified (mirror ports). In the following kinds of situations, loops in hubs that are connected to this product might not be detected. Loops are being detected in a connected hub Loop detection frames are not being forwarded by a connected hub</div></div><div id="layer2_layer2_loop_detect"><div class="search_title" docfname="layer2_layer2_loop_detect" doctitle="Unique" link="#ループ検出例">3.2. Loop detection examples</div><div class="search_word">3.2. loop detection examples the following shows examples of loop detection in this product. loop detection examples loop detection case configuration example loop detection status 1 a loop is detected when a port receives the ldf that it has transmitted. port1.1: shutdown 2 when loops are detected in multiple ports on the same terminal, the port with the largest number is blocked. port1.1: detected port1.3: blocking 3 the loop is avoided by blocking multiple ports. the blocking port is selected using the same rules as case 2. port1.1: detected port1.2: blocking port1.3: blocking 4 when loops are detected in multiple groups, the port with the largest number in each group port1.1: detected, port1.2: blocking port1.3: detected, port1.4: blocking 5 when a loop occurs between two switches, one of the switches detects the loop. ○when detected in port1.3 of switch #a port1.1: detected, port1.3: blocking ○when detected in port1.7 of switch #b port1.5: detected, port1.7: blocking 6 out of the six ports that are connected by cable, the port for which the loop is most quickly detected is the one that is blocked. ○when detected in port1.2 of switch #a port1.1: detected, port1.2: blocking + ○when detected in port1.4 of switch #b port1.3: detected, port1.4: blocking ○when detected in port1.6 of switch #c port1.5: detected, port1.6: blocking 7 because the ldf transmitted from each port returns to these ports, port1.5 and port1.6 will both shut down. port1.5: shutdown port1.6: shutdown 8 port1.6 of switch #b is blocked. depending on the timing, port1.1 of switch #a will shut down; but the loop in port1.1 of switch #a is resolved by blocking port1.6 of switch #b. switch #a port1.1: shutdown switch #b port1.5: detected switch #b port1.6: blocking</div><div class="display_word">3.2. Loop detection examples The following shows examples of loop detection in this product. Loop detection examples Loop detection case Configuration example Loop detection status 1 A loop is detected when a port receives the LDF that it has transmitted. port1.1: Shutdown 2 When loops are detected in multiple ports on the same terminal, the port with the largest number is blocked. port1.1: Detected port1.3: Blocking 3 The loop is avoided by blocking multiple ports. The blocking port is selected using the same rules as case 2. port1.1: Detected port1.2: Blocking port1.3: Blocking 4 When loops are detected in multiple groups, the port with the largest number in each group port1.1: Detected, port1.2: Blocking port1.3: Detected, port1.4: Blocking 5 When a loop occurs between two switches, one of the switches detects the loop. ○When detected in port1.3 of switch #A port1.1: Detected, port1.3: Blocking ○When detected in port1.7 of switch #B port1.5: Detected, port1.7: Blocking 6 Out of the six ports that are connected by cable, the port for which the loop is most quickly detected is the one that is blocked. ○When detected in port1.2 of switch #A port1.1: Detected, port1.2: Blocking + ○When detected in port1.4 of switch #B port1.3: Detected, port1.4: Blocking ○When detected in port1.6 of switch #C port1.5: Detected, port1.6: Blocking 7 Because the LDF transmitted from each port returns to these ports, port1.5 and port1.6 will both shut down. port1.5: Shutdown port1.6: Shutdown 8 Port1.6 of switch #B is blocked. Depending on the timing, port1.1 of switch #A will shut down; but the loop in port1.1 of switch #A is resolved by blocking port1.6 of switch #B. Switch #A port1.1: Shutdown Switch #B port1.5: Detected Switch #B port1.6: Blocking</div></div><div id="layer2_layer2_loop_detect"><div class="search_title" docfname="layer2_layer2_loop_detect" doctitle="Unique" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands enable/disable loop detection function (system) loop-detect enable/disable enable/disable loop detection function (interface) loop-detect enable/disable set port blocking for loop detection loop-detect blocking enable/disable set port blocking duration time when a loop is detected loop-detect blocking interval reset the loop detection status loop-detect reset refer to the setting status of loop detection show loop-detect</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Enable/disable loop detection function (system) loop-detect enable/disable Enable/disable loop detection function (interface) loop-detect enable/disable Set port blocking for loop detection loop-detect blocking enable/disable Set port blocking duration time when a loop is detected loop-detect blocking interval Reset the loop detection status loop-detect reset Refer to the setting status of loop detection show loop-detect</div></div><div id="layer2_layer2_loop_detect"><div class="search_title" docfname="layer2_layer2_loop_detect" doctitle="Unique" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution this example detects any loops occurring on this product using the following configuration, when the loop detection function is enabled. [example 1] loop occurring within this product [example 2] loop occurring in a third-party hub connected to this product this sets lan ports #1 and #3 to detect loops. ■ setting procedure enable the loop detection function for the entire system. yamaha(config)#loop-detect enable (1) 1 enable the loop detection function for the entire system enable the loop detection function for lan ports #1 and #3. yamaha(config)#interface port1.1yamaha(config-if)#spanning-tree disable (1) yamaha(config-if)#loop-detect enable (2) yamaha(config-if)#loop-detect blocking enable (3) (also perform the above settings for lan port #3.) 1 disable the spanning tree function for each lan port 2 enable the loop detection function for each lan port 3 enables blocking the loop detection function for each lan port and blocking are both enabled by default, so there is no need to set them. confirm that the loop detection function has been set. confirm whether the loop detection function is enabled(*) for lan ports #1 and #3. yamaha>show loop-detectloop-detect: enableport      loop-detect    port-blocking           status-------------------------------------------------------port1.1        enable(*)        enable           normalport1.2        enable           enable           normalport1.3        enable(*)        enable           normalport1.4        enable           enable           normalport1.5        enable           enable           normalport1.6        enable           enable           normalport1.7        enable           enable           normalport1.8        enable           enable           normalport1.9        enable           enable           normal   :             :                :                :-------------------------------------------------------(*): indicates that the feature is enabled. if a loop has been detected, the loop detection status can be checked. in the case of example 1: yamaha>show loop-detectloop-detect: enableport      loop-detect    port-blocking           status-------------------------------------------------------port1.1        enable(*)        enable         detected (1) port1.2        enable           enable           normalport1.3        enable(*)        enable         blocking (2) port1.4        enable           enable           normalport1.5        enable           enable           normalport1.6        enable           enable           normalport1.7        enable           enable           normalport1.8        enable           enable           normalport1.9        enable           enable           normal   :             :                :                :-------------------------------------------------------(*): indicates that the feature is enabled. 1 lan port #1 enters the detected status 2 lan port #3 enters the blocking status in the case of example 2: yamaha>show loop-detectloop-detect: enableport      loop-detect    port-blocking           status-------------------------------------------------------port1.1        enable(*)        enable         shutdown (1) port1.2        enable           enable           normalport1.3        enable(*)        enable           normalport1.4        enable           enable           normalport1.5        enable           enable           normalport1.6        enable           enable           normalport1.7        enable           enable           normalport1.8        enable           enable           normalport1.9        enable           enable           normal   :             :                :                :-------------------------------------------------------(*): indicates that the feature is enabled. 1 lan port #1 goes into the shutdown state</div><div class="display_word">5. Examples of Command Execution This example detects any loops occurring on this product using the following configuration, when the loop detection function is enabled. [Example 1] Loop occurring within this product [Example 2] Loop occurring in a third-party hub connected to this product This sets LAN ports #1 and #3 to detect loops. ■ Setting Procedure Enable the loop detection function for the entire system. Yamaha(config)#loop-detect enable (1) 1 Enable the loop detection function for the entire system Enable the loop detection function for LAN ports #1 and #3. Yamaha(config)#interface port1.1Yamaha(config-if)#spanning-tree disable (1) Yamaha(config-if)#loop-detect enable (2) Yamaha(config-if)#loop-detect blocking enable (3) (Also perform the above settings for LAN port #3.) 1 Disable the spanning tree function for each LAN port 2 Enable the loop detection function for each LAN port 3 Enables blocking The loop detection function for each LAN port and blocking are both enabled by default, so there is no need to set them. Confirm that the loop detection function has been set. Confirm whether the loop detection function is enabled(*) for LAN ports #1 and #3. Yamaha>show loop-detectloop-detect: Enableport      loop-detect    port-blocking           status-------------------------------------------------------port1.1        enable(*)        enable           Normalport1.2        enable           enable           Normalport1.3        enable(*)        enable           Normalport1.4        enable           enable           Normalport1.5        enable           enable           Normalport1.6        enable           enable           Normalport1.7        enable           enable           Normalport1.8        enable           enable           Normalport1.9        enable           enable           Normal   :             :                :                :-------------------------------------------------------(*): Indicates that the feature is enabled. If a loop has been detected, the loop detection status can be checked. In the case of example 1: Yamaha>show loop-detectloop-detect: Enableport      loop-detect    port-blocking           status-------------------------------------------------------port1.1        enable(*)        enable         Detected (1) port1.2        enable           enable           Normalport1.3        enable(*)        enable         Blocking (2) port1.4        enable           enable           Normalport1.5        enable           enable           Normalport1.6        enable           enable           Normalport1.7        enable           enable           Normalport1.8        enable           enable           Normalport1.9        enable           enable           Normal   :             :                :                :-------------------------------------------------------(*): Indicates that the feature is enabled. 1 LAN port #1 enters the detected status 2 LAN port #3 enters the blocking status In the case of example 2: Yamaha>show loop-detectloop-detect: Enableport      loop-detect    port-blocking           status-------------------------------------------------------port1.1        enable(*)        enable         Shutdown (1) port1.2        enable           enable           Normalport1.3        enable(*)        enable           Normalport1.4        enable           enable           Normalport1.5        enable           enable           Normalport1.6        enable           enable           Normalport1.7        enable           enable           Normalport1.8        enable           enable           Normalport1.9        enable           enable           Normal   :             :                :                :-------------------------------------------------------(*): Indicates that the feature is enabled. 1 LAN port #1 goes into the shutdown state</div></div><div id="layer2_layer2_loop_detect"><div class="search_title" docfname="layer2_layer2_loop_detect" doctitle="Unique" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution all lan/sfp ports included in the same logical interface must have the same loop detection setting (enabled, disabled, or blocked). lan/sfp ports with different loop detection settings cannot be included in the same logical interface. loop detection settings cannot be specified for lan/sfp ports included in a logical interface.</div><div class="display_word">6. Points of Caution All LAN/SFP ports included in the same logical interface must have the same loop detection setting (enabled, disabled, or blocked). LAN/SFP ports with different loop detection settings cannot be included in the same logical interface. Loop detection settings cannot be specified for LAN/SFP ports included in a logical interface.</div></div><div id="layer2_layer2_loop_detect"><div class="search_title" docfname="layer2_layer2_loop_detect" doctitle="Unique" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation spanning tree led control</div><div class="display_word">7. Related Documentation Spanning Tree LED Control</div></div><div id="layer2_layer2_multiple_vlan"><div class="search_title" docfname="layer2_layer2_multiple_vlan" doctitle="Multiple" link="#マルチプルvlan">Multiple VLAN</div><div class="search_word">multiple vlan</div><div class="display_word">Multiple VLAN</div></div><div id="layer2_layer2_multiple_vlan"><div class="search_title" docfname="layer2_layer2_multiple_vlan" doctitle="Multiple" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview on a multiple vlan, by associating a port with a multiple vlan group, you can block traffic from ports that do not belong to the same multiple vlan group. you can also join a single port to multiple vlan groups. by using this function, it is easy to handle requests to block only traffic between terminals, such as the example below. example of using multiple vlans</div><div class="display_word">1. Function Overview On a multiple VLAN, by associating a port with a multiple VLAN group, you can block traffic from ports that do not belong to the same multiple VLAN group. You can also join a single port to multiple VLAN groups. By using this function, it is easy to handle requests to block only traffic between terminals, such as the example below. Example of using multiple VLANs</div></div><div id="layer2_layer2_multiple_vlan"><div class="search_title" docfname="layer2_layer2_multiple_vlan" doctitle="Multiple" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used none</div><div class="display_word">2. Definition of Terms Used None</div></div><div id="layer2_layer2_multiple_vlan"><div class="search_title" docfname="layer2_layer2_multiple_vlan" doctitle="Multiple" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="layer2_layer2_multiple_vlan"><div class="search_title" docfname="layer2_layer2_multiple_vlan" doctitle="Multiple" link="#動作仕様">3.1. Operating specifications</div><div class="search_word">3.1. operating specifications use the switchport multiple-vlan group command to configure a multiple vlan group. multiple vlans can be configured as lan/sfp ports and link aggregation logical interfaces. if you wish to configure a multiple vlan group for a trunk port, this will be applied to all relevant vlans that belong to the port in question. the multiple vlan group settings will also be applied to a multicast frame. this can be used together with the following functions. control of traffic enable/disable for these functions is set according to the multiple vlan group settings. port-based vlan/tagged vlan/voice vlan port authentication a multiple vlan can contain up to 256 groups. use the show vlan multiple-vlan group command to confirm the setting status for the interface of each multiple vlan group.</div><div class="display_word">3.1. Operating specifications Use the switchport multiple-vlan group command to configure a multiple VLAN group. Multiple VLANs can be configured as LAN/SFP ports and link aggregation logical interfaces. If you wish to configure a multiple VLAN group for a trunk port, this will be applied to all relevant VLANs that belong to the port in question. The multiple VLAN group settings will also be applied to a multicast frame. This can be used together with the following functions. Control of traffic enable/disable for these functions is set according to the multiple VLAN group settings. Port-based VLAN/tagged VLAN/voice VLAN Port authentication A multiple VLAN can contain up to 256 groups. Use the show vlan multiple-vlan group command to confirm the setting status for the interface of each multiple VLAN group.</div></div><div id="layer2_layer2_multiple_vlan"><div class="search_title" docfname="layer2_layer2_multiple_vlan" doctitle="Multiple" link="#マルチプルvlanグループ間の通信例">3.2. Examples of traffic between multiple VLAN groups</div><div class="search_word">3.2. examples of traffic between multiple vlan groups example of traffic for a multiple vlan group when using multiple vlan group settings (group #1 through #4) as shown in the diagram above, enabling/disabling traffic between specific ports a/b and the reasons for such as shown in the table below. port number a (group) port number b (group) traffic enable/disable reason port1.1 (group 1) port1.2 (group 2) disabled the multiple vlan group is different port1.1 (group 1) port1.3 (group 1) enabled associated with multiple vlan group #1 port1.2 (group 2) port1.4 (group 2) enabled associated with multiple vlan group #2 port1.5 (group 3) port1.7 (group 3,4) enabled associated with multiple vlan group #3 port1.6 (no group) port1.8 (group 4) disabled the multiple vlan group is different port1.7 (group 3,4) port1.8 (group 4) enabled associated with multiple vlan group #4 also, traffic can be established between ports that are not associated with a multiple vlan group, so long as it is within the same vlan.</div><div class="display_word">3.2. Examples of traffic between multiple VLAN groups Example of traffic for a multiple VLAN group When using multiple VLAN group settings (Group #1 through #4) as shown in the diagram above, enabling/disabling traffic between specific ports A/B and the reasons for such as shown in the table below. Port number A (group) Port number B (group) Traffic enable/disable Reason port1.1 (Group 1) port1.2 (Group 2) Disabled The multiple VLAN group is different port1.1 (Group 1) port1.3 (Group 1) Enabled Associated with multiple VLAN group #1 port1.2 (Group 2) port1.4 (Group 2) Enabled Associated with multiple VLAN group #2 port1.5 (Group 3) port1.7 (Group 3,4) Enabled Associated with multiple VLAN group #3 port1.6 (no group) port1.8 (Group 4) Disabled The multiple VLAN group is different port1.7 (Group 3,4) port1.8 (Group 4) Enabled Associated with multiple VLAN group #4 Also, traffic can be established between ports that are not associated with a multiple VLAN group, so long as it is within the same VLAN.</div></div><div id="layer2_layer2_multiple_vlan"><div class="search_title" docfname="layer2_layer2_multiple_vlan" doctitle="Multiple" link="#vlan間ルーティング可能な場合の通信例">3.3. Communication example when inter-VLAN routing is possible</div><div class="search_word">3.3. communication example when inter-vlan routing is possible example of inter-vlan routing communication inter-vlan routing is possible with l3 switches with routing enabled. in inter-vlan routing, packets that are routed by hardware can be controlled by multiple vlan groups. when using multiple vlan group settings (group #1 through #2) as shown in the diagram above, enabling/disabling traffic between specific ports a/b and the reasons for such as shown in the table below. port number a (group) port number b (group) traffic enable/disable reason port1.3 (group 1) port1.5 (group 1) enabled associated with multiple vlan group #1 port1.4 (group 1) port1.8 (group 2) disabled the multiple vlan group is different</div><div class="display_word">3.3. Communication example when inter-VLAN routing is possible Example of inter-VLAN routing communication Inter-VLAN routing is possible with L3 switches with routing enabled. In inter-VLAN routing, packets that are routed by hardware can be controlled by multiple VLAN groups. When using multiple VLAN group settings (Group #1 through #2) as shown in the diagram above, enabling/disabling traffic between specific ports A/B and the reasons for such as shown in the table below. Port number A (group) Port number B (group) Traffic enable/disable Reason port1.3 (Group 1) port1.5 (Group 1) Enabled Associated with multiple VLAN group #1 port1.4 (Group 1) port1.8 (Group 2) Disabled The multiple VLAN group is different</div></div><div id="layer2_layer2_multiple_vlan"><div class="search_title" docfname="layer2_layer2_multiple_vlan" doctitle="Multiple" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands multiple vlan group settings switchport multiple-vlan group settings for the name of multiple vlan group multiple-vlan group name set ympi frame transmission function when multiple vlans are specified multiple-vlan transfer ympi show multiple vlans show vlan multiple-vlan</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Multiple VLAN group settings switchport multiple-vlan group Settings for the name of multiple VLAN group multiple-vlan group name Set YMPI frame transmission function when multiple VLANs are specified multiple-vlan transfer ympi Show multiple VLANs show vlan multiple-vlan</div></div><div id="layer2_layer2_multiple_vlan"><div class="search_title" docfname="layer2_layer2_multiple_vlan" doctitle="Multiple" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="layer2_layer2_multiple_vlan"><div class="search_title" docfname="layer2_layer2_multiple_vlan" doctitle="Multiple" link="#マルチプルvlanの設定例1">5.1. Multiple VLAN settings example 1</div><div class="search_word">5.1. multiple vlan settings example 1 this configures multiple vlan settings to achieve the following. hosts connected to ports 1–7 will connect to the internet and other external lines, through the line to which port 8 is connected communications between hosts connected to ports 1–4 are blocked communications between hosts connected to ports 5–7 are permitted communications between hosts connected to ports 1–4 and ports 5–7 are blocked the multiple vlan group settings are as follows. port1.1: associated with multiple vlan group #1 port1.2: associated with multiple vlan group #2 port1.3: associated with multiple vlan group #3 port1.4: associated with multiple vlan group #4 port1.5: associated with multiple vlan group #5 port1.6: associated with multiple vlan group #5 port1.7: associated with multiple vlan group #5 port1.8: associated with multiple vlan groups #1, #2, #3, #4, and #5 this sets the name of multiple vlan group #1 to “network1”. yamaha(config)# multiple-vlan group 1 name network1 (1) 1 settings for the name of multiple vlan group #1 this sets the name of multiple vlan group #5 to “network5”. yamaha(config)# multiple-vlan group 5 name network5 (1) 1 settings for the name of multiple vlan group #5 associates port1.1 through port1.4 with multiple vlan groups #1 through #4 respectively. yamaha(config)# interface port1.1 (1) yamaha(config-if)# switchport multiple-vlan group 1 (2) yamaha(config-if)# exityamaha(config)# interface port1.2 (3) yamaha(config-if)# switchport multiple-vlan group 2 (4) yamaha(config-if)# exityamaha(config)# interface port1.3 (5) yamaha(config-if)# switchport multiple-vlan group 3 (6) yamaha(config-if)# exityamaha(config)# interface port1.4 (7) yamaha(config-if)# switchport multiple-vlan group 4 (8) yamaha(config-if)# exit 1 switch to interface mode 2 configure multiple vlan group 3 switch to interface mode 4 configure multiple vlan group 5 switch to interface mode 6 configure multiple vlan group 7 switch to interface mode 8 configure multiple vlan group this associates port1.5 through port1.7 with multiple vlan group #5. yamaha(config)# interface port1.5-7 (1) yamaha(config-if)# switchport multiple-vlan group 5 (2) yamaha(config-if)# exit 1 switch to interface mode 2 specify multiple vlan group this associates port1.8 with multiple vlan groups #1, #2, #3, #4, #5. yamaha(config)# interface port1.8 (1) yamaha(config-if)# switchport multiple-vlan group 1-5 (2) yamaha(config-if)# exit 1 switch to interface mode 2 specify multiple vlan group this checks the multiple vlan group settings. yamaha>show vlan multiple-vlangroup id  name                            member ports======== ================================ ======================1        network1                         port1.1 port1.82        group0002                        port1.2 port1.83        group0003                        port1.3 port1.84        group0004                        port1.4 port1.85        network5                         port1.5 port1.6                                          port1.7 port1.8</div><div class="display_word">5.1. Multiple VLAN settings example 1 This configures multiple VLAN settings to achieve the following. Hosts connected to ports 1–7 will connect to the Internet and other external lines, through the line to which port 8 is connected Communications between hosts connected to ports 1–4 are blocked Communications between hosts connected to ports 5–7 are permitted Communications between hosts connected to ports 1–4 and ports 5–7 are blocked The multiple VLAN group settings are as follows. port1.1: Associated with multiple VLAN group #1 port1.2: Associated with multiple VLAN group #2 port1.3: Associated with multiple VLAN group #3 port1.4: Associated with multiple VLAN group #4 port1.5: Associated with multiple VLAN group #5 port1.6: Associated with multiple VLAN group #5 port1.7: Associated with multiple VLAN group #5 port1.8: Associated with multiple VLAN groups #1, #2, #3, #4, and #5 This sets the name of multiple VLAN group #1 to “Network1”. Yamaha(config)# multiple-vlan group 1 name Network1 (1) 1 Settings for the name of multiple VLAN group #1 This sets the name of multiple VLAN group #5 to “Network5”. Yamaha(config)# multiple-vlan group 5 name Network5 (1) 1 Settings for the name of multiple VLAN group #5 Associates port1.1 through port1.4 with multiple VLAN groups #1 through #4 respectively. Yamaha(config)# interface port1.1 (1) Yamaha(config-if)# switchport multiple-vlan group 1 (2) Yamaha(config-if)# exitYamaha(config)# interface port1.2 (3) Yamaha(config-if)# switchport multiple-vlan group 2 (4) Yamaha(config-if)# exitYamaha(config)# interface port1.3 (5) Yamaha(config-if)# switchport multiple-vlan group 3 (6) Yamaha(config-if)# exitYamaha(config)# interface port1.4 (7) Yamaha(config-if)# switchport multiple-vlan group 4 (8) Yamaha(config-if)# exit 1 Switch to interface mode 2 Configure multiple VLAN group 3 Switch to interface mode 4 Configure multiple VLAN group 5 Switch to interface mode 6 Configure multiple VLAN group 7 Switch to interface mode 8 Configure multiple VLAN group This associates port1.5 through port1.7 with multiple VLAN group #5. Yamaha(config)# interface port1.5-7 (1) Yamaha(config-if)# switchport multiple-vlan group 5 (2) Yamaha(config-if)# exit 1 Switch to interface mode 2 Specify multiple VLAN group This associates port1.8 with multiple VLAN groups #1, #2, #3, #4, #5. Yamaha(config)# interface port1.8 (1) Yamaha(config-if)# switchport multiple-vlan group 1-5 (2) Yamaha(config-if)# exit 1 Switch to interface mode 2 Specify multiple VLAN group This checks the multiple VLAN group settings. Yamaha>show vlan multiple-vlanGROUP ID  Name                            Member ports======== ================================ ======================1        Network1                         port1.1 port1.82        GROUP0002                        port1.2 port1.83        GROUP0003                        port1.3 port1.84        GROUP0004                        port1.4 port1.85        Network5                         port1.5 port1.6                                          port1.7 port1.8</div></div><div id="layer2_layer2_multiple_vlan"><div class="search_title" docfname="layer2_layer2_multiple_vlan" doctitle="Multiple" link="#マルチプルvlanの設定例2">5.2. Multiple VLAN settings example 2</div><div class="search_word">5.2. multiple vlan settings example 2 this configures multiple vlan settings to achieve the following. hosts connected to ports 1 to 7 will connect to the internet and other external lines, through the line to which port 8 is connected hosts connected to ports 1 to 7 are associated with vlan #2 and assigned an ip address using the dhcp server functions the ip address for vlan #2 is 192.168.110.240/24 and the range of assigned addresses is from 192.168.110.2 to 192.168.110.191/24 communication is blocked between hosts connected to ports 1 to 7 the multiple vlan group settings are as follows. port1.1: associated with multiple vlan group #1 port1.2: associated with multiple vlan group #2 port1.3: associated with multiple vlan group #3 port1.4: associated with multiple vlan group #4 port1.5: associated with multiple vlan group #5 port1.6: associated with multiple vlan group #6 port1.7: associated with multiple vlan group #7 port1.8: associated with multiple vlan groups #1, #2, #3, #4, #5, #6, and #7 assign ports port1.1 to port1.7 to vlan #2. yamaha(config)# interface port1.1-7yamaha(config-if)# switchport access vlan 2yamaha(config-if)# yamaha(config)# interface vlan2yamaha(config-if)# ip address 192.168.110.240/24 create the dhcp pool “pool_vlan2”. yamaha(config)# dhcp pool pool_vlan2yamaha(config-dhcp) (1) 1 switch to the dhcp mode specify the vlan #2 network portion 192.168.110.0/24 in the dhcp pool. yamaha(config-dhcp)# network 192.168.110.0/24 specify the address assignment range from 192.168.110.2 to 192.168.110.191 in the dhcp pool. yamaha(config-dhcp)# range 192.168.110.2 192.168.110.191 specify the default gateway to be notified in dhcp option settings and specify the dns server in the dhcp pool. yamaha(config-dhcp)# default-router 192.168.110.240 (1) yamaha(config-dhcp)# dns-server 192.168.110.1 (2) yamaha(config-dhcp)# exit (3) 1 the default gateway address is 192.168.110.240 (its own address) 2 the dns server address is 192.168.110.1 3 exit the dhcp mode activate the dhcp server functions for vlan2. yamaha(config)# interface vlan2 (1) yamaha(config-if)# dhcp-server enable (2) yamaha(config-if)# exit (3) 1 switch to interface mode 2 enable the dhcp server functions for the interface 3 exit the interface mode activate the dhcp server functions for the entire system. yamaha(config)# dhcp-server enable (1) 1 enable the dhcp server functions for the entire system associate port1.1 through port1.7 with multiple vlan groups #1 through #7 respectively. yamaha(config)# interface port1.1 (1) yamaha(config-if)# switchport multiple-vlan group 1 (2) yamaha(config-if)# exityamaha(config)# interface port1.2 (3) yamaha(config-if)# switchport multiple-vlan group 2 (4) yamaha(config-if)# exityamaha(config)# interface port1.3 (5) yamaha(config-if)# switchport multiple-vlan group 3 (6) yamaha(config-if)# exityamaha(config)# interface port1.4 (7) yamaha(config-if)# switchport multiple-vlan group 4 (8) yamaha(config-if)# exityamaha(config)# interface port1.5 (9) yamaha(config-if)# switchport multiple-vlan group 5 (10) yamaha(config-if)# exityamaha(config)# interface port1.6 (11) yamaha(config-if)# switchport multiple-vlan group 6 (12) yamaha(config-if)# exityamaha(config)# interface port1.7 (13) yamaha(config-if)# switchport multiple-vlan group 7 (14) yamaha(config-if)# exit 1 switch to interface mode 2 configure multiple vlan group 3 switch to interface mode 4 configure multiple vlan group 5 switch to interface mode 6 configure multiple vlan group 7 switch to interface mode 8 configure multiple vlan group 9 switch to interface mode 10 configure multiple vlan group 11 switch to interface mode 12 configure multiple vlan group 13 switch to interface mode 14 configure multiple vlan group associate port1.8 with multiple vlan groups #1 to #7. yamaha(config)# interface port1.8 (1) yamaha(config-if)# switchport multiple-vlan group 1-7 (2) yamaha(config-if)# exit 1 switch to interface mode 2 specify multiple vlan group this checks the multiple vlan group settings. yamaha>show vlan multiple-vlangroup id  name                            member ports======== ================================ ======================1        group0001                        port1.1 port1.82        group0002                        port1.2 port1.83        group0003                        port1.3 port1.84        group0004                        port1.4 port1.85        group0005                        port1.5 port1.86        group0006                        port1.6 port1.87        group0007                        port1.7 port1.8</div><div class="display_word">5.2. Multiple VLAN settings example 2 This configures multiple VLAN settings to achieve the following. Hosts connected to ports 1 to 7 will connect to the Internet and other external lines, through the line to which port 8 is connected Hosts connected to ports 1 to 7 are associated with VLAN #2 and assigned an IP address using the DHCP server functions The IP address for VLAN #2 is 192.168.110.240/24 and the range of assigned addresses is from 192.168.110.2 to 192.168.110.191/24 Communication is blocked between hosts connected to ports 1 to 7 The multiple VLAN group settings are as follows. port1.1: Associated with multiple VLAN group #1 port1.2: Associated with multiple VLAN group #2 port1.3: Associated with multiple VLAN group #3 port1.4: Associated with multiple VLAN group #4 port1.5: Associated with multiple VLAN group #5 port1.6: Associated with multiple VLAN group #6 port1.7: Associated with multiple VLAN group #7 port1.8: Associated with multiple VLAN groups #1, #2, #3, #4, #5, #6, and #7 Assign ports port1.1 to port1.7 to VLAN #2. Yamaha(config)# interface port1.1-7Yamaha(config-if)# switchport access vlan 2Yamaha(config-if)# Yamaha(config)# interface vlan2Yamaha(config-if)# ip address 192.168.110.240/24 Create the DHCP pool “pool_vlan2”. Yamaha(config)# dhcp pool pool_vlan2Yamaha(config-dhcp) (1) 1 Switch to the DHCP mode Specify the VLAN #2 network portion 192.168.110.0/24 in the DHCP pool. Yamaha(config-dhcp)# network 192.168.110.0/24 Specify the address assignment range from 192.168.110.2 to 192.168.110.191 in the DHCP pool. Yamaha(config-dhcp)# range 192.168.110.2 192.168.110.191 Specify the default gateway to be notified in DHCP option settings and specify the DNS server in the DHCP pool. Yamaha(config-dhcp)# default-router 192.168.110.240 (1) Yamaha(config-dhcp)# dns-server 192.168.110.1 (2) Yamaha(config-dhcp)# exit (3) 1 The default gateway address is 192.168.110.240 (its own address) 2 The DNS server address is 192.168.110.1 3 Exit the DHCP mode Activate the DHCP server functions for vlan2. Yamaha(config)# interface vlan2 (1) Yamaha(config-if)# dhcp-server enable (2) Yamaha(config-if)# exit (3) 1 Switch to interface mode 2 Enable the DHCP server functions for the interface 3 Exit the interface mode Activate the DHCP server functions for the entire system. Yamaha(config)# dhcp-server enable (1) 1 Enable the DHCP server functions for the entire system Associate port1.1 through port1.7 with multiple VLAN groups #1 through #7 respectively. Yamaha(config)# interface port1.1 (1) Yamaha(config-if)# switchport multiple-vlan group 1 (2) Yamaha(config-if)# exitYamaha(config)# interface port1.2 (3) Yamaha(config-if)# switchport multiple-vlan group 2 (4) Yamaha(config-if)# exitYamaha(config)# interface port1.3 (5) Yamaha(config-if)# switchport multiple-vlan group 3 (6) Yamaha(config-if)# exitYamaha(config)# interface port1.4 (7) Yamaha(config-if)# switchport multiple-vlan group 4 (8) Yamaha(config-if)# exitYamaha(config)# interface port1.5 (9) Yamaha(config-if)# switchport multiple-vlan group 5 (10) Yamaha(config-if)# exitYamaha(config)# interface port1.6 (11) Yamaha(config-if)# switchport multiple-vlan group 6 (12) Yamaha(config-if)# exitYamaha(config)# interface port1.7 (13) Yamaha(config-if)# switchport multiple-vlan group 7 (14) Yamaha(config-if)# exit 1 Switch to interface mode 2 Configure multiple VLAN group 3 Switch to interface mode 4 Configure multiple VLAN group 5 Switch to interface mode 6 Configure multiple VLAN group 7 Switch to interface mode 8 Configure multiple VLAN group 9 Switch to interface mode 10 Configure multiple VLAN group 11 Switch to interface mode 12 Configure multiple VLAN group 13 Switch to interface mode 14 Configure multiple VLAN group Associate port1.8 with multiple VLAN groups #1 to #7. Yamaha(config)# interface port1.8 (1) Yamaha(config-if)# switchport multiple-vlan group 1-7 (2) Yamaha(config-if)# exit 1 Switch to interface mode 2 Specify multiple VLAN group This checks the multiple VLAN group settings. Yamaha>show vlan multiple-vlanGROUP ID  Name                            Member ports======== ================================ ======================1        GROUP0001                        port1.1 port1.82        GROUP0002                        port1.2 port1.83        GROUP0003                        port1.3 port1.84        GROUP0004                        port1.4 port1.85        GROUP0005                        port1.5 port1.86        GROUP0006                        port1.6 port1.87        GROUP0007                        port1.7 port1.8</div></div><div id="layer2_layer2_multiple_vlan"><div class="search_title" docfname="layer2_layer2_multiple_vlan" doctitle="Multiple" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution the points of caution regarding this function are as follows. the function cannot be used in conjunction with a private vlan. the multiple vlan group to associate with a link aggregation logical interface must be the same. a multiple vlan group is only applicable to forwarding between ports. voluntary packets will not be affected by the settings of a multiple vlan group. even if a multiple vlan is configured, communication may not work correctly due to the following influences. block status of spanning tree igmp snooping/mld snooping status blocked status of loop detection in inter-vlan routing, multiple vlan communication restrictions are applied only to packets routed by hardware processing. restrictions do not apply to inter-vlan routing through the cpu. ympi frames are transmitted for managing yamaha wireless access points if multiple vlans are specified. therefore, even if there are multiple yamaha wireless access points associated with different multiple vlan groups, the cluster management function or the wireless lan controller function can be used.</div><div class="display_word">6. Points of Caution The points of caution regarding this function are as follows. The function cannot be used in conjunction with a private VLAN. The multiple VLAN group to associate with a link aggregation logical interface must be the same. A multiple VLAN group is only applicable to forwarding between ports. Voluntary packets will not be affected by the settings of a multiple VLAN group. Even if a multiple VLAN is configured, communication may not work correctly due to the following influences. Block status of spanning tree IGMP snooping/MLD snooping status Blocked status of loop detection In inter-VLAN routing, multiple VLAN communication restrictions are applied only to packets routed by hardware processing. Restrictions do not apply to inter-VLAN routing through the CPU. YMPI frames are transmitted for managing Yamaha wireless access points if multiple VLANs are specified. Therefore, even if there are multiple Yamaha wireless access points associated with different multiple VLAN groups, the cluster management function or the wireless LAN controller function can be used.</div></div><div id="layer2_layer2_multiple_vlan"><div class="search_title" docfname="layer2_layer2_multiple_vlan" doctitle="Multiple" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation vlan</div><div class="display_word">7. Related Documentation VLAN</div></div><div id="layer2_layer2_stp"><div class="search_title" docfname="layer2_layer2_stp" doctitle="Spanning" link="#スパニングツリー">Spanning Tree</div><div class="search_word">spanning tree</div><div class="display_word">Spanning Tree</div></div><div id="layer2_layer2_stp"><div class="search_title" docfname="layer2_layer2_stp" doctitle="Spanning" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview the spanning tree is a function that maintains redundancies in the network routes while preventing loops. normally, the l2 switch floods the adjacent network switch with the broadcast packets. if the network is constructed as a loop, the network switches will flood each other, causing the loop to occur. this results in a major degradation of bandwidth and cpu resources in the network switches. the spanning tree determines the roles of each port and establishes a network construction where the broadcast packets do not keep traveling around, for networks that contain physical loops as well. when there are problems linking, the problem is detected and the tree is reconstructed in order to restore the system. this product supports stp, rstp, and mstp. spanning tree function overview</div><div class="display_word">1. Function Overview The spanning tree is a function that maintains redundancies in the network routes while preventing loops. Normally, the L2 switch floods the adjacent network switch with the broadcast packets. If the network is constructed as a loop, the network switches will flood each other, causing the loop to occur. This results in a major degradation of bandwidth and CPU resources in the network switches. The spanning tree determines the roles of each port and establishes a network construction where the broadcast packets do not keep traveling around, for networks that contain physical loops as well. When there are problems linking, the problem is detected and the tree is reconstructed in order to restore the system. This product supports STP, RSTP, and MSTP. Spanning tree function overview</div></div><div id="layer2_layer2_stp"><div class="search_title" docfname="layer2_layer2_stp" doctitle="Spanning" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used stp：spanning tree protocol (802.1d) the spanning tree protocol (stp) exchanges bpdu (bridge protocol data unit) messages, in order to avoid loops. this product supports ieee802.1d and rfc4188 . rstp：rapid spanning tree protocol (802.1w) the rapid spanning tree protocol (rstp) is an extension of stp. it can recover the spanning tree more quickly than stp, when the network architecture has changed or when there is a problem linking. this product supports ieee802.1w and rfc4318 . mstp：multiple spanning tree protocol (802.1s) multiple spanning tree protocol (mstp) is a further extension of stp and rstp. it groups the vlan into instances, and constructs a spanning tree for each group. this can be used to distribute load within the network routes. this product supports ieee802.1s .</div><div class="display_word">2. Definition of Terms Used STP：Spanning Tree Protocol (802.1d) The spanning tree protocol (STP) exchanges BPDU (bridge protocol data unit) messages, in order to avoid loops. This product supports IEEE802.1d and RFC4188 . RSTP：Rapid Spanning Tree Protocol (802.1w) The rapid spanning tree protocol (RSTP) is an extension of STP. It can recover the spanning tree more quickly than STP, when the network architecture has changed or when there is a problem linking. This product supports IEEE802.1w and RFC4318 . MSTP：Multiple Spanning Tree Protocol (802.1s) Multiple spanning tree protocol (MSTP) is a further extension of STP and RSTP. It groups the VLAN into instances, and constructs a spanning tree for each group. This can be used to distribute load within the network routes. This product supports IEEE802.1s .</div></div><div id="layer2_layer2_stp"><div class="search_title" docfname="layer2_layer2_stp" doctitle="Spanning" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details this product supports the following functions in order to flexibly handle the construction of routes based on mstp. setting priority set bridge priority set port priority set path cost set timeout set forward delay time set maximum aging time specify edge port (port fast settings) bpdu guard bpdu filtering route guard</div><div class="display_word">3. Function Details This product supports the following functions in order to flexibly handle the construction of routes based on MSTP. Setting priority Set bridge priority Set port priority Set path cost Set timeout Set forward delay time Set maximum aging time Specify edge port (Port Fast settings) BPDU guard BPDU filtering Route guard</div></div><div id="layer2_layer2_stp"><div class="search_title" docfname="layer2_layer2_stp" doctitle="Spanning" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands set spanning tree for the system spanning-tree shutdown set forward delay time spanning-tree forward-time set maximum aging time spanning-tree max-age set bridge priority spanning-tree priority set spanning tree for an interface spanning-tree set interface link type spanning-tree link-type set interface bpdu filtering spanning-tree bpdu-filter set interface bpdu guard spanning-tree bpdu-guard set interface path cost spanning-tree path-cost set interface priority spanning-tree priority set edge port for interface spanning-tree edgeport show spanning tree status show spanning-tree show spanning tree bpdu statistics show spanning-tree statistics clear protocol compatibility mode clear spanning-tree detected protocols move to mst mode spanning-tree mst configuration generate mst instance instance set vlan for mst instance instance vlan set priority of mst instance instance priority set mst region name region set revision number of mst region revision set mst instance for interface spanning-tree instance set interface priority for mst instance spanning-tree instance priority set interface path cost for mst instance spanning-tree instance path-cost show mst region information show spanning-tree mst config show mstp information show spanning-tree mst show mst instance information show spanning-tree mst instance</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Set spanning tree for the system spanning-tree shutdown Set forward delay time spanning-tree forward-time Set maximum aging time spanning-tree max-age Set bridge priority spanning-tree priority Set spanning tree for an interface spanning-tree Set interface link type spanning-tree link-type Set interface BPDU filtering spanning-tree bpdu-filter Set interface BPDU guard spanning-tree bpdu-guard Set interface path cost spanning-tree path-cost Set interface priority spanning-tree priority Set edge port for interface spanning-tree edgeport Show spanning tree status show spanning-tree Show spanning tree BPDU statistics show spanning-tree statistics Clear protocol compatibility mode clear spanning-tree detected protocols Move to MST mode spanning-tree mst configuration Generate MST instance instance Set VLAN for MST instance instance vlan Set priority of MST instance instance priority Set MST region name region Set revision number of MST region revision Set MST instance for interface spanning-tree instance Set interface priority for MST instance spanning-tree instance priority Set interface path cost for MST instance spanning-tree instance path-cost Show MST region information show spanning-tree mst config Show MSTP information show spanning-tree mst Show MST instance information show spanning-tree mst instance</div></div><div id="layer2_layer2_stp"><div class="search_title" docfname="layer2_layer2_stp" doctitle="Spanning" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="layer2_layer2_stp"><div class="search_title" docfname="layer2_layer2_stp" doctitle="Spanning" link="#mstp-設定例">5.1. MSTP setting example</div><div class="search_word">5.1. mstp setting example use this product to realize the architecture shown in the diagram below. in this example, mst instances are used to construct the spanning tree. a different route is set for each mst instance (vlan), in order to distribute network load. the lan port that is connected to the pc is set as the edge port. ■ setting procedure [switch #a] define vlan #2 and vlan #3. yamaha(config)#vlan databaseyamaha(config-vlan)#vlan 2 (1) yamaha(config-vlan)#vlan 3 (2) yamaha(config-vlan)#exit 1 define vlan #2 2 define vlan #3 [switch #a] set the cist priority. yamaha(config)#spanning-tree priority 8192 (1) 1 set cist priority to 8192 [switch #a] set the mst. yamaha(config)#spanning-tree mst configurationyamaha(config-mst)#region sample (1) yamaha(config-mst)#revision 1 (2) yamaha(config-mst)#instance 2 vlan 2 (3) yamaha(config-mst)#instance 3 vlan 3 (4) yamaha(config-mst)#exit 1 set the mst region name to “sample” 2 set the mst revision number to 1 3 define mst instance #2 and associate it with vlan #2 4 define mst instance #3 and associate it with vlan #3 [switch #a] set lan ports #1–#2 as trunk ports, and associate them with vlan #2–#3. also, set the mst instances #2–#3. yamaha(config)#interface port1.1yamaha(config-if)#switchport mode trunk (1) yamaha(config-if)#switchport trunk allowed vlan add 2,3 (2) yamaha(config-if)#spanning-tree instance 2 (3) yamaha(config-if)#spanning-tree instance 3 (4) yamaha(config-if)#exit(also perform the above settings for lan port #2.) 1 set the ports as trunk port 2 associate the ports with vlan #2 and #3 3 set mst instance #2 4 set mst instance #3 [switch #a] set lan port #3 as the access port, and associate it with vlan #2. also, set the mst instance #2, and make it an edge port. yamaha(config)#interface port1.3yamaha(config-if)#switchport mode access (1) yamaha(config-if)#switchport access vlan 2 (2) yamaha(config-if)#spanning-tree instance 2 (3) yamaha(config-if)#spanning-tree edgeport (4) yamaha(config-if)#exit 1 set the port as access port 2 associate it with vlan #2 3 set mst instance #2 4 set it as edge port [switch #a] set lan port #4 as the access port, and associate it with vlan #3. also, set the mst instance #3, and make it an edge port. yamaha(config)#interface port1.4yamaha(config-if)#switchport mode access (1) yamaha(config-if)#switchport access vlan 3 (2) yamaha(config-if)#spanning-tree instance 3 (3) yamaha(config-if)#spanning-tree edgeport (4) yamaha(config-if)#exit 1 set the port as access port 2 associate it with vlan #3 3 set mst instance #3 4 set it as edge port [switch #b] define vlan #2 and vlan #3. yamaha(config)#vlan databaseyamaha(config-vlan)#vlan 2 (1) yamaha(config-vlan)#vlan 3 (2) yamaha(config-vlan)#exit 1 define vlan #2 2 define vlan #3 [switch #b] set the cist priority. yamaha(config)#spanning-tree priority 16384 (1) 1 set cist priority to 16384 [switch #b] set the mst. yamaha(config)#spanning-tree mst configurationyamaha(config-mst)#region sample (1) yamaha(config-mst)#revision 1 (2) yamaha(config-mst)#instance 2 vlan 2 (3) yamaha(config-mst)#instance 2 priority 8192 (4) yamaha(config-mst)#instance 3 vlan 3 (5) yamaha(config-mst)#instance 3 priority 16384 (6) yamaha(config-mst)#exit 1 set the mst region name to “sample” 2 set the mst revision number to 1 3 define mst instance #2 and associate it with vlan #2 4 set the priority of mst instance #2 to 8192 5 define mst instance #3 and associate it with vlan #3 6 set the priority of mst instance #3 to 16384 [switch #b] set lan ports #1–#2 as trunk ports, and associate them with vlan #2–#3. also, set the mst instances #2–#3. yamaha(config)#interface port1.1yamaha(config-if)#switchport mode trunk (1) yamaha(config-if)#switchport trunk allowed vlan add 2,3 (2) yamaha(config-if)#spanning-tree instance 2 (3) yamaha(config-if)#spanning-tree instance 3 (4) yamaha(config-if)#exit(also perform the above settings for lan port #2.) 1 set the ports as trunk port 2 associate the ports with vlan #2 and #3 3 set mst instance #2 4 set mst instance #3 [switch #b] set lan port #3 as the access port, and associate it with vlan #2. also, set the mst instance #2, and make it an edge port. yamaha(config)#interface port1.3yamaha(config-if)#switchport mode access (1) yamaha(config-if)#switchport access vlan 2 (2) yamaha(config-if)#spanning-tree instance 2 (3) yamaha(config-if)#spanning-tree edgeport (4) yamaha(config-if)#exit (5) 1 set the port as access port 2 associate it with vlan #2 3 set mst instance #2 4 set it as edge port 5 configure the settings above for lan port #4 as well. [switch #c] define vlan #2 and vlan #3. yamaha(config)#vlan databaseyamaha(config-vlan)#vlan 2 (1) yamaha(config-vlan)#vlan 3 (2) yamaha(config-vlan)#exit 1 define vlan #2 2 define vlan #3 [switch #c] set the mst. yamaha(config)#spanning-tree mst configurationyamaha(config-mst)#region sample (1) yamaha(config-mst)#revision 1 (2) yamaha(config-mst)#instance 2 vlan 2 (3) yamaha(config-mst)#instance 2 priority 16384 (4) yamaha(config-mst)#instance 3 vlan 3 (5) yamaha(config-mst)#instance 3 priority 8192 (6) yamaha(config-mst)#exit 1 set the mst region name to “sample” 2 set the mst revision number to 1 3 define mst instance #2 and associate it with vlan #2 4 set the priority of mst instance #2 to 16384 5 define mst instance #3 and associate it with vlan #3 6 set the priority of mst instance #3 to 8192 [switch #c] set lan ports #1–#2 as trunk ports, and associate them with vlan #2–#3. also, set the mst instances #2–#3. yamaha(config)#interface port1.1yamaha(config-if)#switchport mode trunk (1) yamaha(config-if)#switchport trunk allowed vlan add 2,3 (2) yamaha(config-if)#spanning-tree instance 2 (3) yamaha(config-if)#spanning-tree instance 3 (4) yamaha(config-if)#exit(also perform the above settings for lan port #2.) 1 set the ports as trunk port 2 associate the ports with vlan #2 and #3 3 set mst instance #2 4 set mst instance #3 [switch #c] set lan port #3 as the access port, and associate it with vlan #3. also, set the mst instance #3, and make it an edge port. yamaha(config)#interface port1.3yamaha(config-if)#switchport mode access (1) yamaha(config-if)#switchport access vlan 3 (2) yamaha(config-if)#spanning-tree instance 3 (3) yamaha(config-if)#spanning-tree edgeport (4) yamaha(config-if)#exit (5) 1 set the port as access port 2 associate it with vlan #3 3 set mst instance #3 4 set it as edge port 5 configure the settings above for lan port #4 as well. connect the lan cable. [switch #a] check the cist architecture. yamaha>show spanning-tree |include root id% default: cist root id 200100a0deaeb920 (1) % default: cist reg root id 200100a0deaeb920yamaha>show spanning-tree |include role%   port1.1: port number 905 - ifindex 5001 - port id 0x8389 - role designated - state forwarding%   port1.2: port number 906 - ifindex 5002 - port id 0x838a - role designated - state forwarding%   port1.3: port number 907 - ifindex 5003 - port id 0x838b - role designated - state forwarding%   port1.4: port number 908 - ifindex 5004 - port id 0x838c - role designated - state forwarding%   port1.5: port number 909 - ifindex 5005 - port id 0x838d - role disabled - state discarding%   port1.6: port number 910 - ifindex 5006 - port id 0x838e - role disabled - state discarding%   port1.7: port number 911 - ifindex 5007 - port id 0x838f - role disabled - state discarding%   port1.8: port number 912 - ifindex 5008 - port id 0x8390 - role disabled - state discarding%   port1.9: port number 913 - ifindex 5009 - port id 0x8391 - role disabled - state discarding%   port1.10: port number 914 - ifindex 5010 - port id 0x8392 - role disabled - state discarding 1 switch #a with the higher priority becomes the root bridge of the cist. [switch #b] check the cist architecture. yamaha>show spanning-tree |include root id% default: cist root id 200100a0deaeb920 (1) % default: cist reg root id 200100a0deaeb920yamaha>show spanning-tree |include role%   port1.1: port number 905 - ifindex 5001 - port id 0x8389 - role rootport - state forwarding%   port1.2: port number 906 - ifindex 5002 - port id 0x838a - role designated - state forwarding%   port1.3: port number 907 - ifindex 5003 - port id 0x838b - role designated - state forwarding%   port1.4: port number 908 - ifindex 5004 - port id 0x838c - role designated - state forwarding%   port1.5: port number 909 - ifindex 5005 - port id 0x838d - role disabled - state discarding%   port1.6: port number 910 - ifindex 5006 - port id 0x838e - role disabled - state discarding%   port1.7: port number 911 - ifindex 5007 - port id 0x838f - role disabled - state discarding%   port1.8: port number 912 - ifindex 5008 - port id 0x8390 - role disabled - state discarding%   port1.9: port number 913 - ifindex 5009 - port id 0x8391 - role disabled - state discarding%   port1.10: port number 914 - ifindex 5010 - port id 0x8392 - role disabled - state discarding 1 switch #a with the higher priority becomes the root bridge of the cist. [switch #c] check the cist architecture. yamaha>show spanning-tree |include root id% default: cist root id 200100a0deaeb920 (1) % default: cist reg root id 200100a0deaeb920yamaha>show spanning-tree |include role%   port1.1: port number 905 - ifindex 5001 - port id 0x8389 - role alternate - state discarding (2) %   port1.2: port number 906 - ifindex 5002 - port id 0x838a - role rootport - state forwarding%   port1.3: port number 907 - ifindex 5003 - port id 0x838b - role designated - state forwarding%   port1.4: port number 908 - ifindex 5004 - port id 0x838c - role designated - state forwarding%   port1.5: port number 909 - ifindex 5005 - port id 0x838d - role disabled - state discarding%   port1.6: port number 910 - ifindex 5006 - port id 0x838e - role disabled - state discarding%   port1.7: port number 911 - ifindex 5007 - port id 0x838f - role disabled - state discarding%   port1.8: port number 912 - ifindex 5008 - port id 0x8390 - role disabled - state discarding%   port1.9: port number 913 - ifindex 5009 - port id 0x8391 - role disabled - state discarding%   port1.10: port number 914 - ifindex 5010 - port id 0x8392 - role disabled - state discarding 1 switch #a with the higher priority becomes the root bridge of the cist. 2 the lan #1 port of switch #c with the lower priority becomes the alternate port of the cist. [switch #a] check the architecture of mst instance #2. yamaha>show spanning-tree mst instance 2 |include root id% default: msti root id 200200a0deaeb879 (1) yamaha>show spanning-tree mst instance 2 |include role%   port1.1: port number 905 - ifindex 5001 - port id 0x8389 - role rootport - state forwarding%   port1.2: port number 906 - ifindex 5002 - port id 0x838a - role alternate - state discarding (2) %   port1.3: port number 907 - ifindex 5003 - port id 0x838b - role designated - state forwarding 1 switch #b with the higher priority becomes the root bridge of mst instance #2. 2 the lan #2 port of switch #a with the lower priority becomes the alternate port of mst instance #2. [switch #b] check the architecture of mst instance #2. yamaha>show spanning-tree mst instance 2 |include root id% default: msti root id 200200a0deaeb879 (1) yamaha>show spanning-tree mst instance 2 |include role%   port1.1: port number 905 - ifindex 5001 - port id 0x8389 - role designated - state forwarding%   port1.2: port number 906 - ifindex 5002 - port id 0x838a - role designated - state forwarding%   port1.3: port number 907 - ifindex 5003 - port id 0x838b - role designated - state forwarding%   port1.4: port number 908 - ifindex 5004 - port id 0x838c - role designated - state forwarding 1 switch #b with the higher priority becomes the root bridge of mst instance #2. [switch #c] check the architecture of mst instance #2. yamaha>show spanning-tree mst instance 2 |include root id% default: msti root id 200200a0deaeb879 (1) yamaha>show spanning-tree mst instance 2 |include role%   port1.1: port number 905 - ifindex 5001 - port id 0x8389 - role rootport - state forwarding%   port1.2: port number 906 - ifindex 5002 - port id 0x838a - role designated - state forwarding 1 switch #b with the higher priority becomes the root bridge of mst instance #2. [switch #a] check the architecture of mst instance #3. yamaha>show spanning-tree mst instance 3 |include root id% default: msti root id 200300a0deaeb83d (1) yamaha>show spanning-tree mst instance 3 |include role%   port1.1: port number 905 - ifindex 5001 - port id 0x8389 - role alternate - state discarding (2) %   port1.2: port number 906 - ifindex 5002 - port id 0x838a - role rootport - state forwarding%   port1.4: port number 908 - ifindex 5004 - port id 0x838c - role designated - state forwarding 1 switch #c with the higher priority becomes the root bridge of mst instance #3. 2 the lan #1 port of switch #a with the lower priority becomes the alternate port of mst instance #3. [switch #b] check the architecture of mst instance #3. yamaha>show spanning-tree mst instance 3 |include root id% default: msti root id 200300a0deaeb83d (1) yamaha>show spanning-tree mst instance 3 |include role%   port1.1: port number 905 - ifindex 5001 - port id 0x8389 - role designated - state forwarding%   port1.2: port number 906 - ifindex 5002 - port id 0x838a - role rootport - state forwarding 1 switch #c with the higher priority becomes the root bridge of mst instance #3. [switch #c] check the architecture of mst instance #3. yamaha>show spanning-tree mst instance 3 |include root id% default: msti root id 200300a0deaeb83d (1) yamaha>show spanning-tree mst instance 3 |include role%   port1.1: port number 905 - ifindex 5001 - port id 0x8389 - role designated - state forwarding%   port1.2: port number 906 - ifindex 5002 - port id 0x838a - role designated - state forwarding%   port1.3: port number 907 - ifindex 5003 - port id 0x838b - role designated - state forwarding%   port1.4: port number 908 - ifindex 5004 - port id 0x838c - role designated - state forwarding 1 switch #c with the higher priority becomes the root bridge of mst instance #3.</div><div class="display_word">5.1. MSTP setting example Use this product to realize the architecture shown in the diagram below. In this example, MST instances are used to construct the spanning tree. A different route is set for each MST instance (VLAN), in order to distribute network load. The LAN port that is connected to the PC is set as the edge port. ■ Setting Procedure [Switch #A] Define VLAN #2 and VLAN #3. Yamaha(config)#vlan databaseYamaha(config-vlan)#vlan 2 (1) Yamaha(config-vlan)#vlan 3 (2) Yamaha(config-vlan)#exit 1 Define VLAN #2 2 Define VLAN #3 [Switch #A] Set the CIST priority. Yamaha(config)#spanning-tree priority 8192 (1) 1 Set CIST priority to 8192 [Switch #A] Set the MST. Yamaha(config)#spanning-tree mst configurationYamaha(config-mst)#region Sample (1) Yamaha(config-mst)#revision 1 (2) Yamaha(config-mst)#instance 2 vlan 2 (3) Yamaha(config-mst)#instance 3 vlan 3 (4) Yamaha(config-mst)#exit 1 Set the MST region name to “Sample” 2 Set the MST revision number to 1 3 Define MST instance #2 and associate it with VLAN #2 4 Define MST instance #3 and associate it with VLAN #3 [Switch #A] Set LAN ports #1–#2 as trunk ports, and associate them with VLAN #2–#3. Also, set the MST instances #2–#3. Yamaha(config)#interface port1.1Yamaha(config-if)#switchport mode trunk (1) Yamaha(config-if)#switchport trunk allowed vlan add 2,3 (2) Yamaha(config-if)#spanning-tree instance 2 (3) Yamaha(config-if)#spanning-tree instance 3 (4) Yamaha(config-if)#exit(Also perform the above settings for LAN port #2.) 1 Set the ports as trunk port 2 Associate the ports with VLAN #2 and #3 3 Set MST instance #2 4 Set MST instance #3 [Switch #A] Set LAN port #3 as the access port, and associate it with VLAN #2. Also, set the MST instance #2, and make it an edge port. Yamaha(config)#interface port1.3Yamaha(config-if)#switchport mode access (1) Yamaha(config-if)#switchport access vlan 2 (2) Yamaha(config-if)#spanning-tree instance 2 (3) Yamaha(config-if)#spanning-tree edgeport (4) Yamaha(config-if)#exit 1 Set the port as access port 2 Associate it with VLAN #2 3 Set MST instance #2 4 Set it as edge port [Switch #A] Set LAN port #4 as the access port, and associate it with VLAN #3. Also, set the MST instance #3, and make it an edge port. Yamaha(config)#interface port1.4Yamaha(config-if)#switchport mode access (1) Yamaha(config-if)#switchport access vlan 3 (2) Yamaha(config-if)#spanning-tree instance 3 (3) Yamaha(config-if)#spanning-tree edgeport (4) Yamaha(config-if)#exit 1 Set the port as access port 2 Associate it with VLAN #3 3 Set MST instance #3 4 Set it as edge port [Switch #B] Define VLAN #2 and VLAN #3. Yamaha(config)#vlan databaseYamaha(config-vlan)#vlan 2 (1) Yamaha(config-vlan)#vlan 3 (2) Yamaha(config-vlan)#exit 1 Define VLAN #2 2 Define VLAN #3 [Switch #B] Set the CIST priority. Yamaha(config)#spanning-tree priority 16384 (1) 1 Set CIST priority to 16384 [Switch #B] Set the MST. Yamaha(config)#spanning-tree mst configurationYamaha(config-mst)#region Sample (1) Yamaha(config-mst)#revision 1 (2) Yamaha(config-mst)#instance 2 vlan 2 (3) Yamaha(config-mst)#instance 2 priority 8192 (4) Yamaha(config-mst)#instance 3 vlan 3 (5) Yamaha(config-mst)#instance 3 priority 16384 (6) Yamaha(config-mst)#exit 1 Set the MST region name to “Sample” 2 Set the MST revision number to 1 3 Define MST instance #2 and associate it with VLAN #2 4 Set the priority of MST instance #2 to 8192 5 Define MST instance #3 and associate it with VLAN #3 6 Set the priority of MST instance #3 to 16384 [Switch #B] Set LAN ports #1–#2 as trunk ports, and associate them with VLAN #2–#3. Also, set the MST instances #2–#3. Yamaha(config)#interface port1.1Yamaha(config-if)#switchport mode trunk (1) Yamaha(config-if)#switchport trunk allowed vlan add 2,3 (2) Yamaha(config-if)#spanning-tree instance 2 (3) Yamaha(config-if)#spanning-tree instance 3 (4) Yamaha(config-if)#exit(Also perform the above settings for LAN port #2.) 1 Set the ports as trunk port 2 Associate the ports with VLAN #2 and #3 3 Set MST instance #2 4 Set MST instance #3 [Switch #B] Set LAN port #3 as the access port, and associate it with VLAN #2. Also, set the MST instance #2, and make it an edge port. Yamaha(config)#interface port1.3Yamaha(config-if)#switchport mode access (1) Yamaha(config-if)#switchport access vlan 2 (2) Yamaha(config-if)#spanning-tree instance 2 (3) Yamaha(config-if)#spanning-tree edgeport (4) Yamaha(config-if)#exit (5) 1 Set the port as access port 2 Associate it with VLAN #2 3 Set MST instance #2 4 Set it as edge port 5 Configure the settings above for LAN port #4 as well. [Switch #C] Define VLAN #2 and VLAN #3. Yamaha(config)#vlan databaseYamaha(config-vlan)#vlan 2 (1) Yamaha(config-vlan)#vlan 3 (2) Yamaha(config-vlan)#exit 1 Define VLAN #2 2 Define VLAN #3 [Switch #C] Set the MST. Yamaha(config)#spanning-tree mst configurationYamaha(config-mst)#region Sample (1) Yamaha(config-mst)#revision 1 (2) Yamaha(config-mst)#instance 2 vlan 2 (3) Yamaha(config-mst)#instance 2 priority 16384 (4) Yamaha(config-mst)#instance 3 vlan 3 (5) Yamaha(config-mst)#instance 3 priority 8192 (6) Yamaha(config-mst)#exit 1 Set the MST region name to “Sample” 2 Set the MST revision number to 1 3 Define MST instance #2 and associate it with VLAN #2 4 Set the priority of MST instance #2 to 16384 5 Define MST instance #3 and associate it with VLAN #3 6 Set the priority of MST instance #3 to 8192 [Switch #C] Set LAN ports #1–#2 as trunk ports, and associate them with VLAN #2–#3. Also, set the MST instances #2–#3. Yamaha(config)#interface port1.1Yamaha(config-if)#switchport mode trunk (1) Yamaha(config-if)#switchport trunk allowed vlan add 2,3 (2) Yamaha(config-if)#spanning-tree instance 2 (3) Yamaha(config-if)#spanning-tree instance 3 (4) Yamaha(config-if)#exit(Also perform the above settings for LAN port #2.) 1 Set the ports as trunk port 2 Associate the ports with VLAN #2 and #3 3 Set MST instance #2 4 Set MST instance #3 [Switch #C] Set LAN port #3 as the access port, and associate it with VLAN #3. Also, set the MST instance #3, and make it an edge port. Yamaha(config)#interface port1.3Yamaha(config-if)#switchport mode access (1) Yamaha(config-if)#switchport access vlan 3 (2) Yamaha(config-if)#spanning-tree instance 3 (3) Yamaha(config-if)#spanning-tree edgeport (4) Yamaha(config-if)#exit (5) 1 Set the port as access port 2 Associate it with VLAN #3 3 Set MST instance #3 4 Set it as edge port 5 Configure the settings above for LAN port #4 as well. Connect the LAN cable. [Switch #A] Check the CIST architecture. Yamaha>show spanning-tree |include Root Id% Default: CIST Root Id 200100a0deaeb920 (1) % Default: CIST Reg Root Id 200100a0deaeb920Yamaha>show spanning-tree |include Role%   port1.1: Port Number 905 - Ifindex 5001 - Port Id 0x8389 - Role Designated - State Forwarding%   port1.2: Port Number 906 - Ifindex 5002 - Port Id 0x838a - Role Designated - State Forwarding%   port1.3: Port Number 907 - Ifindex 5003 - Port Id 0x838b - Role Designated - State Forwarding%   port1.4: Port Number 908 - Ifindex 5004 - Port Id 0x838c - Role Designated - State Forwarding%   port1.5: Port Number 909 - Ifindex 5005 - Port Id 0x838d - Role Disabled - State Discarding%   port1.6: Port Number 910 - Ifindex 5006 - Port Id 0x838e - Role Disabled - State Discarding%   port1.7: Port Number 911 - Ifindex 5007 - Port Id 0x838f - Role Disabled - State Discarding%   port1.8: Port Number 912 - Ifindex 5008 - Port Id 0x8390 - Role Disabled - State Discarding%   port1.9: Port Number 913 - Ifindex 5009 - Port Id 0x8391 - Role Disabled - State Discarding%   port1.10: Port Number 914 - Ifindex 5010 - Port Id 0x8392 - Role Disabled - State Discarding 1 Switch #A with the higher priority becomes the root bridge of the CIST. [Switch #B] Check the CIST architecture. Yamaha>show spanning-tree |include Root Id% Default: CIST Root Id 200100a0deaeb920 (1) % Default: CIST Reg Root Id 200100a0deaeb920Yamaha>show spanning-tree |include Role%   port1.1: Port Number 905 - Ifindex 5001 - Port Id 0x8389 - Role Rootport - State Forwarding%   port1.2: Port Number 906 - Ifindex 5002 - Port Id 0x838a - Role Designated - State Forwarding%   port1.3: Port Number 907 - Ifindex 5003 - Port Id 0x838b - Role Designated - State Forwarding%   port1.4: Port Number 908 - Ifindex 5004 - Port Id 0x838c - Role Designated - State Forwarding%   port1.5: Port Number 909 - Ifindex 5005 - Port Id 0x838d - Role Disabled - State Discarding%   port1.6: Port Number 910 - Ifindex 5006 - Port Id 0x838e - Role Disabled - State Discarding%   port1.7: Port Number 911 - Ifindex 5007 - Port Id 0x838f - Role Disabled - State Discarding%   port1.8: Port Number 912 - Ifindex 5008 - Port Id 0x8390 - Role Disabled - State Discarding%   port1.9: Port Number 913 - Ifindex 5009 - Port Id 0x8391 - Role Disabled - State Discarding%   port1.10: Port Number 914 - Ifindex 5010 - Port Id 0x8392 - Role Disabled - State Discarding 1 Switch #A with the higher priority becomes the root bridge of the CIST. [Switch #C] Check the CIST architecture. Yamaha>show spanning-tree |include Root Id% Default: CIST Root Id 200100a0deaeb920 (1) % Default: CIST Reg Root Id 200100a0deaeb920Yamaha>show spanning-tree |include Role%   port1.1: Port Number 905 - Ifindex 5001 - Port Id 0x8389 - Role Alternate - State Discarding (2) %   port1.2: Port Number 906 - Ifindex 5002 - Port Id 0x838a - Role Rootport - State Forwarding%   port1.3: Port Number 907 - Ifindex 5003 - Port Id 0x838b - Role Designated - State Forwarding%   port1.4: Port Number 908 - Ifindex 5004 - Port Id 0x838c - Role Designated - State Forwarding%   port1.5: Port Number 909 - Ifindex 5005 - Port Id 0x838d - Role Disabled - State Discarding%   port1.6: Port Number 910 - Ifindex 5006 - Port Id 0x838e - Role Disabled - State Discarding%   port1.7: Port Number 911 - Ifindex 5007 - Port Id 0x838f - Role Disabled - State Discarding%   port1.8: Port Number 912 - Ifindex 5008 - Port Id 0x8390 - Role Disabled - State Discarding%   port1.9: Port Number 913 - Ifindex 5009 - Port Id 0x8391 - Role Disabled - State Discarding%   port1.10: Port Number 914 - Ifindex 5010 - Port Id 0x8392 - Role Disabled - State Discarding 1 Switch #A with the higher priority becomes the root bridge of the CIST. 2 The LAN #1 port of Switch #C with the lower priority becomes the alternate port of the CIST. [Switch #A] Check the architecture of MST instance #2. Yamaha>show spanning-tree mst instance 2 |include Root Id% Default: MSTI Root Id 200200a0deaeb879 (1) Yamaha>show spanning-tree mst instance 2 |include Role%   port1.1: Port Number 905 - Ifindex 5001 - Port Id 0x8389 - Role Rootport - State Forwarding%   port1.2: Port Number 906 - Ifindex 5002 - Port Id 0x838a - Role Alternate - State Discarding (2) %   port1.3: Port Number 907 - Ifindex 5003 - Port Id 0x838b - Role Designated - State Forwarding 1 Switch #B with the higher priority becomes the root bridge of MST instance #2. 2 The LAN #2 port of Switch #A with the lower priority becomes the alternate port of MST instance #2. [Switch #B] Check the architecture of MST instance #2. Yamaha>show spanning-tree mst instance 2 |include Root Id% Default: MSTI Root Id 200200a0deaeb879 (1) Yamaha>show spanning-tree mst instance 2 |include Role%   port1.1: Port Number 905 - Ifindex 5001 - Port Id 0x8389 - Role Designated - State Forwarding%   port1.2: Port Number 906 - Ifindex 5002 - Port Id 0x838a - Role Designated - State Forwarding%   port1.3: Port Number 907 - Ifindex 5003 - Port Id 0x838b - Role Designated - State Forwarding%   port1.4: Port Number 908 - Ifindex 5004 - Port Id 0x838c - Role Designated - State Forwarding 1 Switch #B with the higher priority becomes the root bridge of MST instance #2. [Switch #C] Check the architecture of MST instance #2. Yamaha>show spanning-tree mst instance 2 |include Root Id% Default: MSTI Root Id 200200a0deaeb879 (1) Yamaha>show spanning-tree mst instance 2 |include Role%   port1.1: Port Number 905 - Ifindex 5001 - Port Id 0x8389 - Role Rootport - State Forwarding%   port1.2: Port Number 906 - Ifindex 5002 - Port Id 0x838a - Role Designated - State Forwarding 1 Switch #B with the higher priority becomes the root bridge of MST instance #2. [Switch #A] Check the architecture of MST instance #3. Yamaha>show spanning-tree mst instance 3 |include Root Id% Default: MSTI Root Id 200300a0deaeb83d (1) Yamaha>show spanning-tree mst instance 3 |include Role%   port1.1: Port Number 905 - Ifindex 5001 - Port Id 0x8389 - Role Alternate - State Discarding (2) %   port1.2: Port Number 906 - Ifindex 5002 - Port Id 0x838a - Role Rootport - State Forwarding%   port1.4: Port Number 908 - Ifindex 5004 - Port Id 0x838c - Role Designated - State Forwarding 1 Switch #C with the higher priority becomes the root bridge of MST instance #3. 2 The LAN #1 port of Switch #A with the lower priority becomes the alternate port of MST instance #3. [Switch #B] Check the architecture of MST instance #3. Yamaha>show spanning-tree mst instance 3 |include Root Id% Default: MSTI Root Id 200300a0deaeb83d (1) Yamaha>show spanning-tree mst instance 3 |include Role%   port1.1: Port Number 905 - Ifindex 5001 - Port Id 0x8389 - Role Designated - State Forwarding%   port1.2: Port Number 906 - Ifindex 5002 - Port Id 0x838a - Role Rootport - State Forwarding 1 Switch #C with the higher priority becomes the root bridge of MST instance #3. [Switch #C] Check the architecture of MST instance #3. Yamaha>show spanning-tree mst instance 3 |include Root Id% Default: MSTI Root Id 200300a0deaeb83d (1) Yamaha>show spanning-tree mst instance 3 |include Role%   port1.1: Port Number 905 - Ifindex 5001 - Port Id 0x8389 - Role Designated - State Forwarding%   port1.2: Port Number 906 - Ifindex 5002 - Port Id 0x838a - Role Designated - State Forwarding%   port1.3: Port Number 907 - Ifindex 5003 - Port Id 0x838b - Role Designated - State Forwarding%   port1.4: Port Number 908 - Ifindex 5004 - Port Id 0x838c - Role Designated - State Forwarding 1 Switch #C with the higher priority becomes the root bridge of MST instance #3.</div></div><div id="layer2_layer2_stp"><div class="search_title" docfname="layer2_layer2_stp" doctitle="Spanning" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution stp and rstp on this product are supported by backward-compatibility provided by mstp .</div><div class="display_word">6. Points of Caution STP and RSTP on this product are supported by backward-compatibility provided by MSTP .</div></div><div id="layer2_layer2_stp"><div class="search_title" docfname="layer2_layer2_stp" doctitle="Spanning" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation layer 2 function: vlan stp ieee802.1d rfc4188 rstp ieee802.1w rfc4318 mstp ieee802.1s</div><div class="display_word">7. Related Documentation Layer 2 Function: VLAN STP IEEE802.1d RFC4188 RSTP IEEE802.1w RFC4318 MSTP IEEE802.1s</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#vlan">VLAN</div><div class="search_word">vlan</div><div class="display_word">VLAN</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview vlan (virtual lan) is technology that allows a lan to be constructed virtually, without regard to the physical structure of connections. this product lets you use vlans to divide the lan into multiple broadcast domains . the vlans that are supported by this product are shown below. vlan types summary port-based vlan groups that can communicate are configured for each lan/sfp port. tagged vlan groups that can communicate are identified, based on the fixed-length tag information appended to the ethernet frame. multiple and different vlans can be made to communicate by means of one lan/sfp port. private vlan groups that can communicate within the same vlan can be divided up. it consists of the following three types of vlans: - primary vlan - isolated vlan - community vlan multiple vlan each lan/sfp port can be divided into multiple groups that can communicate. refer to this information for multiple vlans. voice vlan this allows audio and data to be handled separately on an access port.</div><div class="display_word">1. Function Overview VLAN (Virtual LAN) is technology that allows a LAN to be constructed virtually, without regard to the physical structure of connections. This product lets you use VLANs to divide the LAN into multiple broadcast domains . The VLANs that are supported by this product are shown below. VLAN types Summary Port-based VLAN Groups that can communicate are configured for each LAN/SFP port. Tagged VLAN Groups that can communicate are identified, based on the fixed-length tag information appended to the Ethernet frame. Multiple and different VLANs can be made to communicate by means of one LAN/SFP port. Private VLAN Groups that can communicate within the same VLAN can be divided up. It consists of the following three types of VLANs: - Primary VLAN - Isolated VLAN - Community VLAN Multiple VLAN Each LAN/SFP port can be divided into multiple groups that can communicate. Refer to this information for multiple VLANs. Voice VLAN This allows audio and data to be handled separately on an access port.</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used broadcast domain this is a range in which broadcast frames can be delivered in a network, such as an ethernet. devices that are connected by relaying a data link layer (mac layer), such as switching hubs, can belong to the same broadcast domain. a broadcast domain generally refers to the network in an ethernet.</div><div class="display_word">2. Definition of Terms Used Broadcast domain This is a range in which broadcast frames can be delivered in a network, such as an Ethernet. Devices that are connected by relaying a data link layer (MAC layer), such as switching hubs, can belong to the same broadcast domain. A broadcast domain generally refers to the network in an Ethernet.</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#vlan-idの定義">3.1. Defining a VLAN ID</div><div class="search_word">3.1. defining a vlan id on product, a maximum of 255 vlans can be defined, with vlan ids ranging from 2–4094. (id #1 is used as the default vlan id.) vlan ids are defined using the vlan command, after the vlan database command is used to enter vlan mode. for details, refer to the command reference.</div><div class="display_word">3.1. Defining a VLAN ID On product, a maximum of 255 VLANs can be defined, with VLAN IDs ranging from 2–4094. (ID #1 is used as the default VLAN ID.) VLAN IDs are defined using the vlan command, after the vlan database command is used to enter VLAN mode. For details, refer to the Command Reference.</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#lansfpポートに対するvlan設定">3.2. VLAN settings for the LAN/SFP ports</div><div class="search_word">3.2. vlan settings for the lan/sfp ports the following settings must be configured after defining the vlans to use, in order to make use of vlan on this product. set lan/sfp port mode settings set associated vlan for lan/sfp ports the lan/sfp ports on this product are set to one of the following modes. access port this is a port that handles untagged frames. it can be associated with one vlan. trunk port this is a port that handles both tagged and untagged frames. it can be associated with multiple vlans, and is mainly used to connect switches to one another. this product only supports ieee 802.1q. (cisco isl is not supported.) use the switchport mode command to set the lan/sfp port mode. when setting the trunk port, use the input filter (“ingress-filter”) to control whether frames not belonging to the specified vlan id will be handled. input filter enabled: only frames set to the specified vlan id will be handled. input filter disabled: frames with any vlan id will be handled. use the show interface switchport command to check the lan/sfp port setting mode. use the switchport access vlan command to set which vlans belong to the access port. use the switchport trunk allowed vlan command to set which vlans belong to the trunk port. as the trunk port can be associated with multiple vlans, use the “all”, “none”, “except”, “add” and “remove” settings as shown below. add adds the specified vlan id. vlan ids that can be added are limited by the ids that are defined by the vlan mode. remove deletes the specified vlan id. all adds all vlan ids specified by the vlan mode. the vlan ids added by the vlan mode can also be added after this command is executed. none the trunk port will not be associated with any vlan. except adds all other vlan ids except for the ones specified. the vlan ids added by the vlan mode can also be added after this command is executed. a vlan that uses untagged frames (native vlan) can be specified for the trunk port. tagged audio frames can be transferred by specifying a voice vlan for an access port. use the show vlan command to check which vlans belong to a lan/sfp port.</div><div class="display_word">3.2. VLAN settings for the LAN/SFP ports The following settings must be configured after defining the VLANs to use, in order to make use of VLAN on this product. Set LAN/SFP port mode settings Set associated VLAN for LAN/SFP ports The LAN/SFP ports on this product are set to one of the following modes. Access port This is a port that handles untagged frames. It can be associated with one VLAN. Trunk port This is a port that handles both tagged and untagged frames. It can be associated with multiple VLANs, and is mainly used to connect switches to one another. This product only supports IEEE 802.1Q. (Cisco ISL is not supported.) Use the switchport mode command to set the LAN/SFP port mode. When setting the trunk port, use the input filter (“ingress-filter”) to control whether frames not belonging to the specified VLAN ID will be handled. Input filter enabled: Only frames set to the specified VLAN ID will be handled. Input filter disabled: Frames with any VLAN ID will be handled. Use the show interface switchport command to check the LAN/SFP port setting mode. Use the switchport access vlan command to set which VLANs belong to the access port. Use the switchport trunk allowed vlan command to set which VLANs belong to the trunk port. As the trunk port can be associated with multiple VLANs, use the “all”, “none”, “except”, “add” and “remove” settings as shown below. add Adds the specified VLAN ID. VLAN IDs that can be added are limited by the IDs that are defined by the VLAN mode. remove Deletes the specified VLAN ID. all Adds all VLAN IDs specified by the VLAN mode. The VLAN IDs added by the VLAN mode can also be added after this command is executed. none The trunk port will not be associated with any VLAN. except Adds all other VLAN IDs except for the ones specified. The VLAN IDs added by the VLAN mode can also be added after this command is executed. A VLAN that uses untagged frames (native VLAN) can be specified for the trunk port. Tagged audio frames can be transferred by specifying a voice VLAN for an access port. Use the show vlan command to check which VLANs belong to a LAN/SFP port.</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#vlanに対するアクセス制御">3.3. VLAN access control</div><div class="search_word">3.3. vlan access control this product provides an vlan access map function, to control access to the vlan. the vlan access map can be associated with a standard/extended ip access control list and a mac address control list as vlan id filtering parameters. the vlan access map is operated using the commands shown below. create vlan access map: vlan access-map command set vlan access map parameters: match access-list command assign vlan access map: vlan filter command show vlan access map: show vlan access-map command</div><div class="display_word">3.3. VLAN access control This product provides an VLAN access map function, to control access to the VLAN. The VLAN access map can be associated with a standard/extended IP access control list and a MAC address control list as VLAN ID filtering parameters. The VLAN access map is operated using the commands shown below. Create VLAN access map: vlan access-map command Set VLAN access map parameters: match access-list command Assign VLAN access map: vlan filter command Show VLAN access map: show vlan access-map command</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#デフォルトvlan">3.4. Default VLAN</div><div class="search_word">3.4. default vlan the default vlan is vlan #1 (vlan1), which exists in this switch by default. as the default vlan is a special vlan, it always exists and cannot be deleted. the following operations can be used to automatically delete the relevant port from the default vlan. setting the vlan for an access port setting any vlan other than the default as the native vlan for the trunk port setting the native vlan for the trunk port to “none”</div><div class="display_word">3.4. Default VLAN The default VLAN is VLAN #1 (vlan1), which exists in this switch by default. As the default VLAN is a special VLAN, it always exists and cannot be deleted. The following operations can be used to automatically delete the relevant port from the default VLAN. Setting the VLAN for an access port Setting any VLAN other than the default as the native VLAN for the trunk port Setting the native VLAN for the trunk port to “none”</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#ネイティブvlan">3.5. Native VLAN</div><div class="search_word">3.5. native vlan a native vlan is a vlan that associates untagged frames received by the lan/sfp port that was set as a trunk port. defining an lan/sfp port as a trunk port will set the default vlan (vlan #1) as the native vlan. use the switchport trunk native vlan command when specifying a certain vlan as the native vlan. if you do not want to handle untagged frames on the lan/sfp port, you can set the native vlan to none. (specify “none” with the “ switchport trunk native vlan ” command.)</div><div class="display_word">3.5. Native VLAN A native VLAN is a VLAN that associates untagged frames received by the LAN/SFP port that was set as a trunk port. Defining an LAN/SFP port as a trunk port will set the default VLAN (VLAN #1) as the native VLAN. Use the switchport trunk native vlan command when specifying a certain VLAN as the native VLAN. If you do not want to handle untagged frames on the LAN/SFP port, you can set the native VLAN to none. (Specify “none” with the “ switchport trunk native vlan ” command.)</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#プライベートvlan">3.6. Private VLAN</div><div class="search_word">3.6. private vlan this product can configure a private vlan for further dividing up groups that can communicate within the same subnet. the operating specifications are shown below. a private vlan contains the following three vlan types. primary vlan this is the parent vlan of the secondary vlan. only one primary vlan can be set per private vlan. isolated vlan this is a kind of secondary vlan, which only sends traffic to a primary vlan. only one primary vlan can be set per private vlan. community vlan this is a kind of secondary vlan, which only sends traffic to vlans in the same community and to a primary vlan. multiple community vlans can be set for each private vlan. a primary vlan may contain multiple promiscuous ports. access ports, trunk ports, or static/lacp logical interfaces are the ports that can be used as promiscuous ports. only access ports can be used as host ports for a secondary vlan (isolated vlan, community vlan). a secondary vlan (isolated vlan, community vlan) can be associated with one primary vlan. use the switchport private-vlan mapping command to create the association. an isolated vlan can be associated with multiple promiscuous ports contained within a private vlan. a community vlan can be associated with multiple promiscuous ports contained within a private vlan.</div><div class="display_word">3.6. Private VLAN This product can configure a private VLAN for further dividing up groups that can communicate within the same subnet. The operating specifications are shown below. A private VLAN contains the following three VLAN types. Primary VLAN This is the parent VLAN of the secondary VLAN. Only one primary VLAN can be set per private VLAN. Isolated VLAN This is a kind of secondary VLAN, which only sends traffic to a primary VLAN. Only one primary VLAN can be set per private VLAN. Community VLAN This is a kind of secondary VLAN, which only sends traffic to VLANs in the same community and to a primary VLAN. Multiple community VLANs can be set for each private VLAN. A primary VLAN may contain multiple promiscuous ports. Access ports, trunk ports, or static/LACP logical interfaces are the ports that can be used as promiscuous ports. Only access ports can be used as host ports for a secondary VLAN (isolated VLAN, community VLAN). A secondary VLAN (isolated VLAN, community VLAN) can be associated with one primary VLAN. Use the switchport private-vlan mapping command to create the association. An isolated VLAN can be associated with multiple promiscuous ports contained within a private VLAN. A community VLAN can be associated with multiple promiscuous ports contained within a private VLAN.</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#ボイスvlan">3.7. Voice VLAN</div><div class="search_word">3.7. voice vlan voice vlan is a function that can prevent audio from being adversely affected even when ip phone voice traffic is mixed with pc data traffic. some ip phones have two ports: a port for connection to the network switch and a port for connection to the pc. by connecting the network switch to the ip phone, and the ip phone to the pc, it is possible to use one port of the network switch to handle the ip phone audio traffic and the pc’s data traffic. using the voice vlan function in this type of configuration allows the audio data and the pc data to be separated so that noise is less likely to occur on the ip phone, or to handle the audio data with a higher priority. voice vlan settings are made by the switchport voice vlan command. set one of the following to be handled as voice traffic. frames with the 802.1p tag priority tag frames (802.1p tags with a vlan id of 0 and only the cos value specified) untagged frames when tagged frames are handled as voice traffic, untagged frames are handled as data traffic. by using lldp, this product can automatically apply settings to a connected ip telephone. the conditions for making automatic settings are as follows. lldp-med tlv transmission is enabled on the port for which voice vlan is enabled. the connected ip phone supports settings via lldp-med. if the above conditions are satisfied, and when an ip phone is connected to the corresponding port, voice vlan information (tagged/untagged, vlan id, the cos value to be used, dscp value) are notified according to the network policy tlv of lldp-med when an ip phone is connected to the corresponding port. the ip phone will transmit voice data according to the information that was provided to it from this unit. the cos value specified for the ip phone is set by the switchport voice cos command, and the dscp value is set by the switchport voice dscp command. in order to give priority to handling voice traffic, qos settings (enable qos, set trust mode) according to the ip phone settings are also required. the limitations of voice vlan are as follows. it can be used only on a physical interface port that is assigned as an access port. it cannot be used on a link aggregation logical interface or on a vlan logical interface. the voice vlan function and the port authentication function cannot be used together.</div><div class="display_word">3.7. Voice VLAN Voice VLAN is a function that can prevent audio from being adversely affected even when IP phone voice traffic is mixed with PC data traffic. Some IP phones have two ports: a port for connection to the network switch and a port for connection to the PC. By connecting the network switch to the IP phone, and the IP phone to the PC, it is possible to use one port of the network switch to handle the IP phone audio traffic and the PC’s data traffic. Using the voice VLAN function in this type of configuration allows the audio data and the PC data to be separated so that noise is less likely to occur on the IP phone, or to handle the audio data with a higher priority. Voice VLAN settings are made by the switchport voice vlan command. Set one of the following to be handled as voice traffic. Frames with the 802.1p tag Priority tag frames (802.1p tags with a VLAN ID of 0 and only the CoS value specified) Untagged frames When tagged frames are handled as voice traffic, untagged frames are handled as data traffic. By using LLDP, this product can automatically apply settings to a connected IP telephone. The conditions for making automatic settings are as follows. LLDP-MED TLV transmission is enabled on the port for which voice VLAN is enabled. The connected IP phone supports settings via LLDP-MED. If the above conditions are satisfied, and when an IP phone is connected to the corresponding port, voice VLAN information (tagged/untagged, VLAN ID, the CoS value to be used, DSCP value) are notified according to the Network Policy TLV of LLDP-MED when an IP phone is connected to the corresponding port. The IP phone will transmit voice data according to the information that was provided to it from this unit. The CoS value specified for the IP phone is set by the switchport voice cos command, and the DSCP value is set by the switchport voice dscp command. In order to give priority to handling voice traffic, QoS settings (enable QoS, set trust mode) according to the IP phone settings are also required. The limitations of voice VLAN are as follows. It can be used only on a physical interface port that is assigned as an access port. It cannot be used on a link aggregation logical interface or on a VLAN logical interface. The voice VLAN function and the port authentication function cannot be used together.</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands</div><div class="display_word">4. Related Commands</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#関連コマンド一覧">4.1. List of related commands</div><div class="search_word">4.1. list of related commands related commands are indicated below. operations operating commands enter vlan mode vlan database define vlan interface, or change a predefined vlan vlan define a private vlan private-vlan set the secondary vlan for a private vlan private-vlan association create vlan access map vlan access-map set vlan access map parameters match assign vlan access map to vlan vlan filter set access port (untagged port) switchport mode access set associated vlan of an access port (untagged port) switchport access vlan set trunk port (tagged port) switchport mode trunk set associated vlan for trunk port (tagged port) switchport trunk allowed vlan set native vlan for trunk port (tagged port) switchport trunk native vlan set ports for private vlan (promiscuous port, host port) switchport mode private-vlan configure vlan for private vlan port and host port switchport private-vlan host-association configure vlan for private vlan port and promiscuous port switchport private-vlan mapping configure voice vlan switchport voice vlan set cos value for voice vlan switchport voice cos set dscp value for voice vlan switchport voice dscp show vlan information show vlan show private vlan information show vlan private-vlan show vlan access map show vlan access-map show vlan access map filter show vlan filter</div><div class="display_word">4.1. List of related commands Related commands are indicated below. Operations Operating commands Enter VLAN mode vlan database Define VLAN interface, or change a predefined VLAN vlan Define a private VLAN private-vlan Set the secondary VLAN for a private VLAN private-vlan association Create VLAN access map vlan access-map Set VLAN access map parameters match Assign VLAN access map to VLAN vlan filter Set access port (untagged port) switchport mode access Set associated VLAN of an access port (untagged port) switchport access vlan Set trunk port (tagged port) switchport mode trunk Set associated VLAN for trunk port (tagged port) switchport trunk allowed vlan Set native VLAN for trunk port (tagged port) switchport trunk native vlan Set ports for private VLAN (promiscuous port, host port) switchport mode private-vlan Configure VLAN for private VLAN port and host port switchport private-vlan host-association Configure VLAN for private VLAN port and promiscuous port switchport private-vlan mapping Configure voice VLAN switchport voice vlan Set CoS value for voice VLAN switchport voice cos Set DSCP value for voice VLAN switchport voice dscp Show VLAN information show vlan Show private VLAN information show vlan private-vlan Show VLAN access map show vlan access-map Show VLAN access map filter show vlan filter</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#ポートベースvlan-の設定">5.1. Port-based VLAN settings</div><div class="search_word">5.1. port-based vlan settings in this example, a port-based vlan is configured for this product in order to allow communication between hosts a–b and hosts c–d. the lan port settings for this product are as follows. lan ports #1 and #2: set as access port, and associated with vlan #1000 lan ports #3 and #4: set as access port, and associated with vlan #2000 ■ setting procedure switch to vlan mode using the vlan database command, and define two vlans using the vlan command. yamaha(config)# vlan database (1) yamaha(config-vlan)# vlan 1000 (2) yamaha(config-vlan)# vlan 2000 (3) yamaha(config-if)# exit 1 switch to vlan mode 2 create vlan #1000 3 create vlan #2000 set lan ports #1–2 as access ports, and associate them with vlan #1000. yamaha(config)# interface port1.1-2 (1) yamaha(config-if)# switchport mode access (2) yamaha(config-if)# switchport access vlan 1000 (3) yamaha(config-if)# exit 1 switch to interface mode 2 set the ports as access port 3 define a vlan id set lan ports #3–4 as access ports, and associate them with vlan #2000. yamaha(config)# interface port1.3-4yamaha(config-if)# switchport mode accessyamaha(config-if)# switchport access vlan 2000yamaha(config-if)# exit confirm the vlan settings. yamaha#show vlan brief(u)-untagged, (t)-taggedvlan id  name            state   member ports======= ================ ======= ===============================1       default          active  port1.5(u) port1.6(u)                                 port1.7(u) port1.8(u)1000    vlan1000         active  port1.1(u) port1.2(u)2000    vlan2000         active  port1.3(u) port1.4(u)</div><div class="display_word">5.1. Port-based VLAN settings In this example, a port-based VLAN is configured for this product in order to allow communication between hosts A–B and hosts C–D. The LAN port settings for this product are as follows. LAN ports #1 and #2: Set as access port, and associated with VLAN #1000 LAN ports #3 and #4: Set as access port, and associated with VLAN #2000 ■ Setting Procedure Switch to VLAN mode using the vlan database command, and define two VLANs using the vlan command. Yamaha(config)# vlan database (1) Yamaha(config-vlan)# vlan 1000 (2) Yamaha(config-vlan)# vlan 2000 (3) Yamaha(config-if)# exit 1 Switch to VLAN mode 2 Create VLAN #1000 3 Create VLAN #2000 Set LAN ports #1–2 as access ports, and associate them with VLAN #1000. Yamaha(config)# interface port1.1-2 (1) Yamaha(config-if)# switchport mode access (2) Yamaha(config-if)# switchport access vlan 1000 (3) Yamaha(config-if)# exit 1 Switch to interface mode 2 Set the ports as access port 3 Define a VLAN ID Set LAN ports #3–4 as access ports, and associate them with VLAN #2000. Yamaha(config)# interface port1.3-4Yamaha(config-if)# switchport mode accessYamaha(config-if)# switchport access vlan 2000Yamaha(config-if)# exit Confirm the VLAN settings. Yamaha#show vlan brief(u)-Untagged, (t)-TaggedVLAN ID  Name            State   Member ports======= ================ ======= ===============================1       default          ACTIVE  port1.5(u) port1.6(u)                                 port1.7(u) port1.8(u)1000    VLAN1000         ACTIVE  port1.1(u) port1.2(u)2000    VLAN2000         ACTIVE  port1.3(u) port1.4(u)</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#タグvlan-の設定">5.2. Tagged VLAN settings</div><div class="search_word">5.2. tagged vlan settings in this example, a tagged vlan is configured between #a and #b of this product, in order to communicate between hosts a–b and hosts c–d. the lan port settings for #a and #b of this product are as follows. lan port #1: set as access port, and associated with vlan #1000 lan port #2: set as access port, and associated with vlan #2000 lan port #3: set as trunk port, and associated with lan #1000 and vlan #2000 [switch #a/#b] define vlan. yamaha(config)#vlan database (1) yamaha(config-vlan)#vlan 1000 (2) yamaha(config-vlan)#vlan 2000 (3) 1 switch to vlan mode 2 define vlan #1000 3 define vlan #2000 [switch #a/#b] set lan port #1 as the access port, and associate it with vlan #1000. yamaha(config)#interface port1.1 (1) yamaha(config-if)#switchport mode access (2) yamaha(config-if)#switchport access vlan 1000 (3) yamaha(config-if)#exit 1 switch to interface mode 2 set the ports as access port 3 associate it with vlan #1000 [switch #a/#b] set lan port #2 as the access port, and associate it with vlan #2000. yamaha(config)#interface port1.2 (1) yamaha(config-if)#switchport mode access (2) yamaha(config-if)#switchport access vlan 2000 (3) yamaha(config-if)#exit 1 switch to interface mode 2 set the ports as access port 3 associate it with vlan #2000 [switch #a/#b] set lan port #3 as a trunk port, and associate it with vlan #1000/#2000. yamaha(config)#interface port1.3 (1) yamaha(config-if)#switchport mode trunk (2) yamaha(config-if)#switchport trunk allowed vlan add 1000 (3) yamaha(config-if)#switchport trunk allowed vlan add 2000 (4) yamaha(config-if)#exit 1 switch to interface mode 2 set the port as trunk port 3 add vlan #1000 4 add vlan #2000 confirm the vlan settings. yamaha#show vlan brief(u)-untagged, (t)-taggedvlan id  name                            state   member ports======= ================================ ======= ======================1       default                          active  port1.3(u)1000    vlan1000                         active  port1.1(u) port1.3(t)2000    vlan2000                         active  port1.2(u) port1.3(t)</div><div class="display_word">5.2. Tagged VLAN settings In this example, a tagged VLAN is configured between #A and #B of this product, in order to communicate between hosts A–B and hosts C–D. The LAN port settings for #A and #B of this product are as follows. LAN port #1: Set as access port, and associated with VLAN #1000 LAN port #2: Set as access port, and associated with VLAN #2000 LAN port #3: Set as trunk port, and associated with LAN #1000 and VLAN #2000 [Switch #A/#B] Define VLAN. Yamaha(config)#vlan database (1) Yamaha(config-vlan)#vlan 1000 (2) Yamaha(config-vlan)#vlan 2000 (3) 1 Switch to vlan mode 2 Define VLAN #1000 3 Define VLAN #2000 [Switch #A/#B] Set LAN port #1 as the access port, and associate it with VLAN #1000. Yamaha(config)#interface port1.1 (1) Yamaha(config-if)#switchport mode access (2) Yamaha(config-if)#switchport access vlan 1000 (3) Yamaha(config-if)#exit 1 Switch to interface mode 2 Set the ports as access port 3 Associate it with VLAN #1000 [Switch #A/#B] Set LAN port #2 as the access port, and associate it with VLAN #2000. Yamaha(config)#interface port1.2 (1) Yamaha(config-if)#switchport mode access (2) Yamaha(config-if)#switchport access vlan 2000 (3) Yamaha(config-if)#exit 1 Switch to interface mode 2 Set the ports as access port 3 Associate it with VLAN #2000 [Switch #A/#B] Set LAN port #3 as a trunk port, and associate it with VLAN #1000/#2000. Yamaha(config)#interface port1.3 (1) Yamaha(config-if)#switchport mode trunk (2) Yamaha(config-if)#switchport trunk allowed vlan add 1000 (3) Yamaha(config-if)#switchport trunk allowed vlan add 2000 (4) Yamaha(config-if)#exit 1 Switch to interface mode 2 Set the port as trunk port 3 Add VLAN #1000 4 Add VLAN #2000 Confirm the VLAN settings. Yamaha#show vlan brief(u)-Untagged, (t)-TaggedVLAN ID  Name                            State   Member ports======= ================================ ======= ======================1       default                          ACTIVE  port1.3(u)1000    VLAN1000                         ACTIVE  port1.1(u) port1.3(t)2000    VLAN2000                         ACTIVE  port1.2(u) port1.3(t)</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#プライベートvlan-の設定">5.3. Private VLAN settings</div><div class="search_word">5.3. private vlan settings this example makes private vlan settings for this product, to achieve the following. hosts connected to ports 1–7 will connect to the internet and other external lines, through the line to which port 8 is connected communications between hosts connected to ports 1–4 are blocked (isolated vlan: vlan #21) communications between hosts connected to ports 5–7 are permitted (community vlan: vlan #22) communications between hosts connected to ports 1–4 and ports 5–7 are blocked define the vlan id to be used for the private vlan. yamaha(config)# vlan database (1) yamaha(config-vlan)# vlan 2 (2) yamaha(config-vlan)# vlan 21yamaha(config-vlan)# vlan 22yamaha(config-vlan)# private-vlan 2 primary (3) yamaha(config-vlan)# private-vlan 21 isolated (4) yamaha(config-vlan)# private-vlan 22 community (5) yamaha(config-vlan)# private-vlan 2 association add 21 (6) yamaha(config-vlan)# private-vlan 2 association add 22yamaha(config-vlan)# exit 1 switch to vlan mode 2 create vlan 3 configure primary vlan 4 configure isolated vlan 5 configure community vlan 6 associate the ports with primary vlan configure the isolated vlan (vlan #21) for lan ports 1–4. yamaha(config)#interface port1.1-4 (1) yamaha(config-if)#switchport mode access (2) yamaha(config-if)#switchport access vlan 21 (3) yamaha(config-if)#switchport mode private-vlan host (4) yamaha(config-if)#switchport private-vlan host-association 2 add 21yamaha(config-if)#exit 1 switch to interface mode 2 set the ports as access port 3 associate the ports with vlan #21 4 set the ports as private vlan host port configure the community vlan (vlan #22) for lan ports 5–7. yamaha(config)#interface port1.5-7 (1) yamaha(config-if)#switchport mode access (2) yamaha(config-if)#switchport access vlan 22 (3) yamaha(config-if)#switchport mode private-vlan host (4) yamaha(config-if)#switchport private-vlan host-association 2 add 22yamaha(config-if)#exit 1 switch to interface mode 2 set the ports as access port 3 associate the ports with vlan #22 4 set the ports as private vlan host port configure the primary vlan (vlan #2) for lan port 8. (promiscuous port) yamaha(config)#interface port1.8 (1) yamaha(config-if)#switchport mode access (2) yamaha(config-if)#switchport access vlan 2 (3) yamaha(config-if)#switchport mode private-vlan promiscuous (4) yamaha(config-if)#switchport private-vlan mapping 2 add 21yamaha(config-if)#switchport private-vlan mapping 2 add 22yamaha(config-if)#exit 1 switch to interface mode 2 set the ports as access port 3 associate the ports with vlan #2 4 set the ports as private vlan promiscuous port confirm the vlan settings. yamaha#show vlan brief(u)-untagged, (t)-taggedvlan id  name                            state   member ports======= ================================ ======= ======================1       default                          active2       vlan0002                         active  port1.8(u)21      vlan0021                         active  port1.1(u) port1.2(u)                                                 port1.3(u) port1.4(u)22      vlan0022                         active  port1.5(u) port1.6(u)                                                 port1.7(u)yamaha#show vlan private-vlan primary        secondary          type          interfaces -------        ---------       ----------      ----------       2              21          isolated       port1.1 port1.2                                                 port1.3 port1.4       2              22         community       port1.5 port1.6                                                 port1.7</div><div class="display_word">5.3. Private VLAN settings This example makes private VLAN settings for this product, to achieve the following. Hosts connected to ports 1–7 will connect to the Internet and other external lines, through the line to which port 8 is connected Communications between hosts connected to ports 1–4 are blocked (isolated VLAN: VLAN #21) Communications between hosts connected to ports 5–7 are permitted (community VLAN: VLAN #22) Communications between hosts connected to ports 1–4 and ports 5–7 are blocked Define the VLAN ID to be used for the private VLAN. Yamaha(config)# vlan database (1) Yamaha(config-vlan)# vlan 2 (2) Yamaha(config-vlan)# vlan 21Yamaha(config-vlan)# vlan 22Yamaha(config-vlan)# private-vlan 2 primary (3) Yamaha(config-vlan)# private-vlan 21 isolated (4) Yamaha(config-vlan)# private-vlan 22 community (5) Yamaha(config-vlan)# private-vlan 2 association add 21 (6) Yamaha(config-vlan)# private-vlan 2 association add 22Yamaha(config-vlan)# exit 1 Switch to VLAN mode 2 Create VLAN 3 Configure primary VLAN 4 Configure isolated VLAN 5 Configure community VLAN 6 Associate the ports with primary VLAN Configure the isolated VLAN (VLAN #21) for LAN ports 1–4. Yamaha(config)#interface port1.1-4 (1) Yamaha(config-if)#switchport mode access (2) Yamaha(config-if)#switchport access vlan 21 (3) Yamaha(config-if)#switchport mode private-vlan host (4) Yamaha(config-if)#switchport private-vlan host-association 2 add 21Yamaha(config-if)#exit 1 Switch to interface mode 2 Set the ports as access port 3 Associate the ports with VLAN #21 4 Set the ports as private VLAN host port Configure the community VLAN (VLAN #22) for LAN ports 5–7. Yamaha(config)#interface port1.5-7 (1) Yamaha(config-if)#switchport mode access (2) Yamaha(config-if)#switchport access vlan 22 (3) Yamaha(config-if)#switchport mode private-vlan host (4) Yamaha(config-if)#switchport private-vlan host-association 2 add 22Yamaha(config-if)#exit 1 Switch to interface mode 2 Set the ports as access port 3 Associate the ports with VLAN #22 4 Set the ports as private VLAN host port Configure the primary VLAN (VLAN #2) for LAN port 8. (Promiscuous port) Yamaha(config)#interface port1.8 (1) Yamaha(config-if)#switchport mode access (2) Yamaha(config-if)#switchport access vlan 2 (3) Yamaha(config-if)#switchport mode private-vlan promiscuous (4) Yamaha(config-if)#switchport private-vlan mapping 2 add 21Yamaha(config-if)#switchport private-vlan mapping 2 add 22Yamaha(config-if)#exit 1 Switch to interface mode 2 Set the ports as access port 3 Associate the ports with VLAN #2 4 Set the ports as private VLAN promiscuous port Confirm the VLAN settings. Yamaha#show vlan brief(u)-Untagged, (t)-TaggedVLAN ID  Name                            State   Member ports======= ================================ ======= ======================1       default                          ACTIVE2       VLAN0002                         ACTIVE  port1.8(u)21      VLAN0021                         ACTIVE  port1.1(u) port1.2(u)                                                 port1.3(u) port1.4(u)22      VLAN0022                         ACTIVE  port1.5(u) port1.6(u)                                                 port1.7(u)Yamaha#show vlan private-vlan PRIMARY        SECONDARY          TYPE          INTERFACES -------        ---------       ----------      ----------       2              21          isolated       port1.1 port1.2                                                 port1.3 port1.4       2              22         community       port1.5 port1.6                                                 port1.7</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#ボイスvlan-の設定">5.4. Voice VLAN settings</div><div class="search_word">5.4. voice vlan settings make voice vlan settings for this product, and implement the following. connect an ip phone to port 1. connect a pc to the other lan port of the ip phone. using lldp-med, make the following settings from this product for the ip phone. as voice traffic for the ip phone, transmit and receive 802.1q tagged frames of vlan #2. untagged frames are transmitted and received as pc data traffic. use a cos value of 6 when transmitting and receiving voice traffic. define the vlan id used by the voice vlan. yamaha(config)# vlan database (1) yamaha(config-vlan)# vlan 2 (2) yamaha(config-vlan)# exit 1 switch to vlan mode 2 create vlan set voice vlan for lan port #1. yamaha(config)#interface port1.1 (1) yamaha(config-if)#switchport mode access (2) yamaha(config-if)#switchport voice vlan 2 (3) yamaha(config-if)#switchport voice cos 6 (4) yamaha(config-if)#exit 1 switch to interface mode 2 set the ports as access port 3 configure voice traffic as tagged frames for vlan #2 4 set the cos value for voice traffic to 6 set qos for lan port #1. yamaha(config)#qos enable (1) yamaha(config)#interface port1.1 (2) yamaha(config-if)#qos trust cos (3) yamaha(config-if)#exit 1 enable qos 2 switch to interface mode 3 set trust mode to cos set lldp-med transmission and reception for lan port #1. yamaha(config)#interface port1.1 (1) yamaha(config-if)#lldp-agent (2) yamaha(lldp-agent)#tlv-select med (3) yamaha(lldp-agent)#set lldp enable txrx (4) yamaha(lldp-agent)#exityamaha(config-if)#exityamaha(config)#lldp run (5) yamaha(config)#exit 1 switch to interface mode 2 create lldp agent, mode transition 3 set lldp-med tlv 4 set lldp transmission/reception mode 5 enable lldp function</div><div class="display_word">5.4. Voice VLAN settings Make voice VLAN settings for this product, and implement the following. Connect an IP phone to port 1. Connect a PC to the other LAN port of the IP phone. Using LLDP-MED, make the following settings from this product for the IP phone. As voice traffic for the IP phone, transmit and receive 802.1q tagged frames of VLAN #2. Untagged frames are transmitted and received as PC data traffic. Use a CoS value of 6 when transmitting and receiving voice traffic. Define the VLAN ID used by the voice VLAN. Yamaha(config)# vlan database (1) Yamaha(config-vlan)# vlan 2 (2) Yamaha(config-vlan)# exit 1 Switch to VLAN mode 2 Create VLAN Set voice VLAN for LAN port #1. Yamaha(config)#interface port1.1 (1) Yamaha(config-if)#switchport mode access (2) Yamaha(config-if)#switchport voice vlan 2 (3) Yamaha(config-if)#switchport voice cos 6 (4) Yamaha(config-if)#exit 1 Switch to interface mode 2 Set the ports as access port 3 Configure voice traffic as tagged frames for VLAN #2 4 Set the CoS value for voice traffic to 6 Set QoS for LAN port #1. Yamaha(config)#qos enable (1) Yamaha(config)#interface port1.1 (2) Yamaha(config-if)#qos trust cos (3) Yamaha(config-if)#exit 1 Enable QoS 2 Switch to interface mode 3 Set trust mode to CoS Set LLDP-MED transmission and reception for LAN port #1. Yamaha(config)#interface port1.1 (1) Yamaha(config-if)#lldp-agent (2) Yamaha(lldp-agent)#tlv-select med (3) Yamaha(lldp-agent)#set lldp enable txrx (4) Yamaha(lldp-agent)#exitYamaha(config-if)#exitYamaha(config)#lldp run (5) Yamaha(config)#exit 1 Switch to interface mode 2 Create LLDP agent, mode transition 3 Set LLDP-MED TLV 4 Set LLDP transmission/reception mode 5 Enable LLDP function</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution a host port that is associated with a private vlan cannot be aggregated as a link aggregation logical interface; this limitation is specific to host ports.</div><div class="display_word">6. Points of Caution A host port that is associated with a private VLAN cannot be aggregated as a link aggregation logical interface; this limitation is specific to host ports.</div></div><div id="layer2_layer2_vlan"><div class="search_title" docfname="layer2_layer2_vlan" doctitle="VLAN" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation multiple vlan</div><div class="display_word">7. Related Documentation Multiple VLAN</div></div><div id="layer3_layer3_ip_common"><div class="search_title" docfname="layer3_layer3_ip_common" doctitle="IPv4/IPv6" link="#ipv4ipv6共通設定">IPv4/IPv6 Common Settings</div><div class="search_word">ipv4/ipv6 common settings</div><div class="display_word">IPv4/IPv6 Common Settings</div></div><div id="layer3_layer3_ip_common"><div class="search_title" docfname="layer3_layer3_ip_common" doctitle="IPv4/IPv6" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product is compatible with the following network environment settings that are common to ipv4 and ipv6 , mainly for the purpose of maintenance (configuring the settings of the switch). dns client settings equal cost multipath settings</div><div class="display_word">1. Function Overview This product is compatible with the following network environment settings that are common to IPv4 and IPv6 , mainly for the purpose of maintenance (configuring the settings of the switch). DNS client settings Equal cost multipath settings</div></div><div id="layer3_layer3_ip_common"><div class="search_title" docfname="layer3_layer3_ip_common" doctitle="IPv4/IPv6" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used none</div><div class="display_word">2. Definition of Terms Used None</div></div><div id="layer3_layer3_ip_common"><div class="search_title" docfname="layer3_layer3_ip_common" doctitle="IPv4/IPv6" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="layer3_layer3_ip_common"><div class="search_title" docfname="layer3_layer3_ip_common" doctitle="IPv4/IPv6" link="#dns-クライアントの設定">3.1. DNS client settings</div><div class="search_word">3.1. dns client settings this product supports dns (domain name system) clients . if an fqdn (fully qualified domain name) has been set for an ntp server or a syslog server, an inquiry is made to the dns server to retrieve the ipv4/ipv6 address. this product provides the following dns client control functions. set ip address of the dns server set default domain name set search domain list inquiries to the dns server are enabled by default, and the setting can be changed by using the dns-client enable/disable command.</div><div class="display_word">3.1. DNS client settings This product supports DNS (Domain Name System) clients . If an FQDN (Fully Qualified Domain Name) has been set for an NTP server or a syslog server, an inquiry is made to the DNS server to retrieve the IPv4/IPv6 address. This product provides the following DNS client control functions. Set IP address of the DNS server Set default domain name Set search domain list Inquiries to the DNS server are enabled by default, and the setting can be changed by using the dns-client enable/disable command.</div></div><div id="layer3_layer3_ip_common"><div class="search_title" docfname="layer3_layer3_ip_common" doctitle="IPv4/IPv6" link="#dns-サーバーのipアドレス設定">3.1.1. Set IP address of the DNS server</div><div class="search_word">3.1.1. set ip address of the dns server up to three ip addresses can be set for the dns server, using the methods shown below. manual setting using the dns-client name-server command this lets you specify the ipv4/ipv6 address. automatic setting via dhcp the highest default gateway value takes priority if there is more than one. automatic setting via dhcpv6 if specifying multiple settings, the most recent is prioritized. link local addresses notified by dhcpv6 cannot be specified. if both dhcp and dhcpv6 are used, both settings will be overwritten when dns server addresses are obtained. this product always gives priority to the information that was set via commands . check the configured dns servers by using the show dns-client command.</div><div class="display_word">3.1.1. Set IP address of the DNS server Up to three IP addresses can be set for the DNS server, using the methods shown below. Manual setting using the dns-client name-server command This lets you specify the IPv4/IPv6 address. Automatic setting via DHCP The highest default gateway value takes priority if there is more than one. Automatic setting via DHCPv6 If specifying multiple settings, the most recent is prioritized. Link local addresses notified by DHCPv6 cannot be specified. If both DHCP and DHCPv6 are used, both settings will be overwritten when DNS server addresses are obtained. This product always gives priority to the information that was set via commands . Check the configured DNS servers by using the show dns-client command.</div></div><div id="layer3_layer3_ip_common"><div class="search_title" docfname="layer3_layer3_ip_common" doctitle="IPv4/IPv6" link="#デフォルトドメインの設定">3.1.2. Set default domain name</div><div class="search_word">3.1.2. set default domain name only one default domain can be set using the methods shown below. the domain can be specified using up to 256 characters . manual setting using the dns-client domain-name command automatic setting via dhcp the highest default gateway value takes priority if there is more than one. just as with dns server ip addresses, this product prioritizes information specified with commands . check the default domain that was set by using the show dns-client command. the use of a default domain is only allowed if there are no listings in the search domain list.</div><div class="display_word">3.1.2. Set default domain name Only one default domain can be set using the methods shown below. The domain can be specified using up to 256 characters . Manual setting using the dns-client domain-name command Automatic setting via DHCP The highest default gateway value takes priority if there is more than one. Just as with DNS server IP addresses, this product prioritizes information specified with commands . Check the default domain that was set by using the show dns-client command. The use of a default domain is only allowed if there are no listings in the search domain list.</div></div><div id="layer3_layer3_ip_common"><div class="search_title" docfname="layer3_layer3_ip_common" doctitle="IPv4/IPv6" link="#検索ドメインリストの設定">3.1.3. Set search domain list</div><div class="search_word">3.1.3. set search domain list this product uses a search domain list to manage the domain names used when inquiring with the dns. up to six domain names can be set on the search domain list using the method below. manual setting using the dns-client domain-list command automatic setting via dhcpv6 if specifying multiple settings, the most recent is prioritized. just as with dns server ip addresses, this product prioritizes information specified with commands . the search domain list that has been set can be checked using the show dns-client command. the search domain list must be within 256 characters total for all domain names registered .</div><div class="display_word">3.1.3. Set search domain list This product uses a search domain list to manage the domain names used when inquiring with the DNS. Up to six domain names can be set on the search domain list using the method below. Manual setting using the dns-client domain-list command Automatic setting via DHCPv6 If specifying multiple settings, the most recent is prioritized. Just as with DNS server IP addresses, this product prioritizes information specified with commands . The search domain list that has been set can be checked using the show dns-client command. The search domain list must be within 256 characters total for all domain names registered .</div></div><div id="layer3_layer3_ip_common"><div class="search_title" docfname="layer3_layer3_ip_common" doctitle="IPv4/IPv6" link="#等コストマルチパスの設定">3.2. Equal cost multipath settings</div><div class="search_word">3.2. equal cost multipath settings this product supports equal-cost multi-path settings using the following functions. ipv4 static routing ipv6 static routing ripv1, ripv2, ripng (only on compatible models) ospfv2, ospfv3 (only on compatible models) if multiple routes to the same destination are registered in the rib, these multiple routes will be reflected in the fib. up to eight routes leading to the same destination can be registered in the fib. the default setting is four routes . the number of equal-cost multi-paths that can be registered may be changed using the maximum-paths command. the changes to the settings will not be reflected in actual operations until rebooting. use the port-channel load-balance command to configure the load balance rules for equal-cost multi-path destinations. caution must be used when changing the load balance rule settings using the port-channel load-balance command, as this has an impact on how link aggregation works.</div><div class="display_word">3.2. Equal cost multipath settings This product supports equal-cost multi-path settings using the following functions. IPv4 static routing IPv6 static routing RIPv1, RIPv2, RIPng (only on compatible models) OSPFv2, OSPFv3 (only on compatible models) If multiple routes to the same destination are registered in the RIB, these multiple routes will be reflected in the FIB. Up to eight routes leading to the same destination can be registered in the FIB. The default setting is four routes . The number of equal-cost multi-paths that can be registered may be changed using the maximum-paths command. The changes to the settings will not be reflected in actual operations until rebooting. Use the port-channel load-balance command to configure the load balance rules for equal-cost multi-path destinations. Caution must be used when changing the load balance rule settings using the port-channel load-balance command, as this has an impact on how link aggregation works.</div></div><div id="layer3_layer3_ip_common"><div class="search_title" docfname="layer3_layer3_ip_common" doctitle="IPv4/IPv6" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. function types operations operating commands dns client settings dns client settings dns-client enable/disable set dns server address dns-client name-server set default domain name dns-client domain-name set search domain list dns-client domain-list show dns client settings show dns-client equal cost multipath settings set the number of equal-cost multi-paths that can be registered maximum-paths display the number of equal-cost multi-paths that can be registered show ip route summary show ipv6 route summary set load balance function rules port-channel load-balance</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Function types Operations Operating commands DNS client settings DNS client settings dns-client enable/disable Set DNS server address dns-client name-server Set default domain name dns-client domain-name Set search domain list dns-client domain-list Show DNS client settings show dns-client Equal cost multipath settings Set the number of equal-cost multi-paths that can be registered maximum-paths Display the number of equal-cost multi-paths that can be registered show ip route summary show ipv6 route summary Set load balance function rules port-channel load-balance</div></div><div id="layer3_layer3_ip_common"><div class="search_title" docfname="layer3_layer3_ip_common" doctitle="IPv4/IPv6" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="layer3_layer3_ip_common"><div class="search_title" docfname="layer3_layer3_ip_common" doctitle="IPv4/IPv6" link="#dnsクライアントの設定">5.1. DNS client settings</div><div class="search_word">5.1. dns client settings set dns client settings for this product to prepare an environment for dns queries. specify 192.168.100.1 and 192.168.100.2 as the ip addresses of the servers for dns queries. specify example.com as the default domain used for dns queries. ■ setting procedure enable the dns query functionality. yamaha(config)#dns-client enable since this is specified as the default value, we do not need to set this specifically. specify the dns servers. yamaha(config)#dns-client name-server 192.168.100.1yamaha(config)#dns-client name-server 192.168.100.2 set the default domain. yamaha(config)#dns-client domain-name example.com check the dns client information that was set. yamaha#show dns-clientdns client is enabled default domain  : example.com domain list     : name servers    : 192.168.100.1 192.168.100.2 * - values assigned by dhcp or dhcpv6 client.</div><div class="display_word">5.1. DNS client settings Set DNS client settings for this product to prepare an environment for DNS queries. Specify 192.168.100.1 and 192.168.100.2 as the IP addresses of the servers for DNS queries. Specify example.com as the default domain used for DNS queries. ■ Setting Procedure Enable the DNS query functionality. Yamaha(config)#dns-client enable Since this is specified as the default value, we do not need to set this specifically. Specify the DNS servers. Yamaha(config)#dns-client name-server 192.168.100.1Yamaha(config)#dns-client name-server 192.168.100.2 Set the default domain. Yamaha(config)#dns-client domain-name example.com Check the DNS client information that was set. Yamaha#show dns-clientDNS client is enabled Default domain  : example.com Domain list     : Name Servers    : 192.168.100.1 192.168.100.2 * - Values assigned by DHCP or DHCPv6 Client.</div></div><div id="layer3_layer3_ip_common"><div class="search_title" docfname="layer3_layer3_ip_common" doctitle="IPv4/IPv6" link="#等コストマルチパス">5.2. Equal-cost multi-paths</div><div class="search_word">5.2. equal-cost multi-paths this changes the number of equal-cost multi-paths that can be registered to “5”. also, the source and destination ip addresses are used as load balance rules. set the number of equal-cost multi-paths that can be registered yamaha(config)#maximum-paths 5% system reboot is required for new maximum-path value to take effect. a reboot is required to apply the settings. set the source and destination ip addresses as load balance rules. yamaha(config)#port-channel load-balance src-dst-ip check the current number of equal-cost multi-paths that can be registered. yamaha(config)#show ip route summaryip routing table name is default-ip-routing-table(0)ip routing table maximum-paths   : 5route source    networksconnected       3rip             2total           5</div><div class="display_word">5.2. Equal-cost multi-paths This changes the number of equal-cost multi-paths that can be registered to “5”. Also, the source and destination IP addresses are used as load balance rules. Set the number of equal-cost multi-paths that can be registered Yamaha(config)#maximum-paths 5% System Reboot is required for new Maximum-Path value to take effect. A reboot is required to apply the settings. Set the source and destination IP addresses as load balance rules. Yamaha(config)#port-channel load-balance src-dst-ip Check the current number of equal-cost multi-paths that can be registered. Yamaha(config)#show ip route summaryIP routing table name is Default-IP-Routing-Table(0)IP routing table maximum-paths   : 5Route Source    Networksconnected       3rip             2Total           5</div></div><div id="layer3_layer3_ip_common"><div class="search_title" docfname="layer3_layer3_ip_common" doctitle="IPv4/IPv6" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution none</div><div class="display_word">6. Points of Caution None</div></div><div id="layer3_layer3_ip_common"><div class="search_title" docfname="layer3_layer3_ip_common" doctitle="IPv4/IPv6" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation none</div><div class="display_word">7. Related Documentation None</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#ipv4基本設定">Basic IPv4 Settings</div><div class="search_word">basic ipv4 settings</div><div class="display_word">Basic IPv4 Settings</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product is compatible with the following ipv4 network environment settings , mainly for the purpose of maintenance (configuring the settings of the switch). ipv4 address settings route information settings arp table settings mtu settings</div><div class="display_word">1. Function Overview This product is compatible with the following IPv4 network environment settings , mainly for the purpose of maintenance (configuring the settings of the switch). IPv4 address settings Route information settings ARP table settings MTU settings</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used ipv4 link local address this is an address that is only valid within the same segment, within the range of 169.254.0.0/16 to 169.254.255.255/16 .</div><div class="display_word">2. Definition of Terms Used IPv4 Link Local Address This is an address that is only valid within the same segment, within the range of 169.254.0.0/16 to 169.254.255.255/16 .</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#ipv4アドレスの設定">3.1. IPv4 address settings</div><div class="search_word">3.1. ipv4 address settings this product lets you specify the ipv4 address and subnet mask for a vlan interface . as the setting method, both fixed settings and automatic settings via dhcp are supported. to set the fixed/automatic ipv4 address, use the ip address command. the following actions occur if addresses are specified automatically by dhcp. the hostname option (option code 12) can be added to the discover/request message. the lease time requested to the dhcp server is fixed at 72 hours . (the actual lease time will depend on the setting of the dhcp server.) if the no ip address command is executed with automatic settings, a release message for the ipv4 address obtained is sent to the dhcp server. the information obtained from the dhcp server can be checked using the show dhcp lease . for ipv4 addresses, 1 primary address and 4 secondary addresses can be specified per vlan interface . a maximum of 8 ipv4 addresses can be specified for the entire system . the ipv4 address that is allocated to a vlan interface can be checked using the show ip interface command. in the initial state, 192.168.100.240/24 is fixed for the default vlan (vlan #1) .</div><div class="display_word">3.1. IPv4 address settings This product lets you specify the IPv4 address and subnet mask for a VLAN interface . As the setting method, both fixed settings and automatic settings via DHCP are supported. To set the fixed/automatic IPv4 address, use the ip address command. The following actions occur if addresses are specified automatically by DHCP. The HostName option (option code 12) can be added to the Discover/Request message. The lease time requested to the DHCP server is fixed at 72 hours . (The actual lease time will depend on the setting of the DHCP server.) If the no ip address command is executed with automatic settings, a release message for the IPv4 address obtained is sent to the DHCP server. The information obtained from the DHCP server can be checked using the show dhcp lease . For IPv4 addresses, 1 primary address and 4 secondary addresses can be specified per VLAN interface . A maximum of 8 IPv4 addresses can be specified for the entire system . The IPv4 address that is allocated to a VLAN interface can be checked using the show ip interface command. In the initial state, 192.168.100.240/24 is fixed for the default VLAN (VLAN #1) .</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#auto-ip機能">3.2. Auto IP function</div><div class="search_word">3.2. auto ip function as part of the ipv4 address setting functionality, this product provides an auto ip function which automatically generates ipv4 link local addresses based on the mac address. the auto ip function only works when an ipv4 address has not been allocated from the dhcp server. (the ipv4 address must be set to “dhcp” as a prerequisite.) this function confirms whether the automatically-generated ipv4 link local address does not already exist on the network via arp. if it has been confirmed that the address does not already exist, the generated address will start to be used. if the ipv4 address was allocated from the dhcp server after the ipv4 link local address was determined via auto ip, the ipv4 link local address is discarded, and the ip address obtained from the dhcp server is used. to enable the auto ip function, use the auto-ip enable command. the auto ip function can be enabled for only one vlan interface . in the initial state, the default vlan (vlan #1) is enabled.</div><div class="display_word">3.2. Auto IP function As part of the IPv4 address setting functionality, this product provides an auto IP function which automatically generates IPv4 link local addresses based on the MAC address. The auto IP function only works when an IPv4 address has not been allocated from the DHCP server. (The IPv4 address must be set to “DHCP” as a prerequisite.) This function confirms whether the automatically-generated IPv4 link local address does not already exist on the network via ARP. If it has been confirmed that the address does not already exist, the generated address will start to be used. If the IPv4 address was allocated from the DHCP server after the IPv4 link local address was determined via auto IP, the IPv4 link local address is discarded, and the IP address obtained from the DHCP server is used. To enable the Auto IP function, use the auto-ip enable command. The Auto IP function can be enabled for only one VLAN interface . In the initial state, the default VLAN (VLAN #1) is enabled.</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#ルート情報の設定">3.3. Route information settings</div><div class="search_word">3.3. route information settings this product refers to a routing table when sending syslog messages and when sending out voluntary ipv4 packets as an ipv4 host for ntp-based time adjustments and so on. this product uses the following functions to perform the routing table operations. set vlan interface route information set default gateway set static route information show route information</div><div class="display_word">3.3. Route information settings This product refers to a routing table when sending syslog messages and when sending out voluntary IPv4 packets as an IPv4 host for NTP-based time adjustments and so on. This product uses the following functions to perform the routing table operations. Set VLAN interface route information Set default gateway Set static route information Show route information</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#vlanインターフェースのルート情報">3.3.1. Route information for VLAN interfaces</div><div class="search_word">3.3.1. route information for vlan interfaces when an ipv4 address is set for a vlan interface, this product automatically sets the correspondence between the network address and vlan id as route information. when releasing ipv4 addresses set for the vlan interface, the above settings will be deleted.</div><div class="display_word">3.3.1. Route information for VLAN interfaces When an IPv4 address is set for a VLAN interface, this product automatically sets the correspondence between the network address and VLAN ID as route information. When releasing IPv4 addresses set for the VLAN interface, the above settings will be deleted.</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#デフォルトゲートウェイの設定">3.3.2. Set default gateway</div><div class="search_word">3.3.2. set default gateway the destination for ipv4 packets sent to network addresses that are not set in the routing table can be set as the default gateway on this product. to set the default gateway, use the ip route command. to show the default gateway, use the show ip route command.</div><div class="display_word">3.3.2. Set default gateway The destination for IPv4 packets sent to network addresses that are not set in the routing table can be set as the default gateway on this product. To set the default gateway, use the ip route command. To show the default gateway, use the show ip route command.</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#スタティックルート情報の設定">3.3.3. Set static route information</div><div class="search_word">3.3.3. set static route information a static route to the destination network address (the gateway address to which packets will be sent) can be set on this product. static route information is set using the ip route command. static route information is displayed using the show ip route command.</div><div class="display_word">3.3.3. Set static route information A static route to the destination network address (the gateway address to which packets will be sent) can be set on this product. Static route information is set using the ip route command. Static route information is displayed using the show ip route command.</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#経路表と経路選択">3.3.4. Routing table and route selection</div><div class="search_word">3.3.4. routing table and route selection you will use the following two types of table to specify routing information. rib (routing information base: ip routing table) fib (forwarding information base: ip forwarding table) the roles of each are explained below. rib rib (routing information base: ip routing table) is a database that stores various routing information. a route is registered in the rib in the following cases. when an ipv4 address is assigned to a vlan interface when a static route or a default gateway are specified manually when a default gateway is learned via a dhcp message to check the rib, use the show ip route database command. fib fib (forwarding information base: ip forwarding table) is a database that is referenced when deciding how to forward ip packets. of the routes that are registered in the rib, the fib registers only the route that is determined to be “optimal” and is actually used for forwarding packets. the conditions by which a route is determined to be optimal are as follows. the corresponding vlan interface is in the link up state if multiple routes to the same destination are registered in the rib, only one is decided in the following order of priority a manually specified route takes priority over a route learned via a dhcp message. a route whose gateway has a higher ip address value takes priority to check the fib, use the show ip route command.</div><div class="display_word">3.3.4. Routing table and route selection You will use the following two types of table to specify routing information. RIB (Routing Information Base: IP routing table) FIB (Forwarding Information Base: IP forwarding table) The roles of each are explained below. RIB RIB (Routing Information Base: IP routing table) is a database that stores various routing information. A route is registered in the RIB in the following cases. When an IPv4 address is assigned to a VLAN interface When a static route or a default gateway are specified manually When a default gateway is learned via a DHCP message To check the RIB, use the show ip route database command. FIB FIB (Forwarding Information Base: IP forwarding table) is a database that is referenced when deciding how to forward IP packets. Of the routes that are registered in the RIB, the FIB registers only the route that is determined to be “optimal” and is actually used for forwarding packets. The conditions by which a route is determined to be optimal are as follows. The corresponding VLAN interface is in the link up state If multiple routes to the same destination are registered in the RIB, only one is decided in the following order of priority A manually specified route takes priority over a route learned via a DHCP message. A route whose gateway has a higher IP address value takes priority To check the FIB, use the show ip route command.</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#arp-テーブルの設定">3.4. ARP table settings</div><div class="search_word">3.4. arp table settings when sending ipv4 packets, this product uses arp (address resolution protocol) to obtain the mac addresses from the ipv4 addresses. the correspondence between ipv4 address and mac address is saved in the arp table with the following specifications. the arp entries saved in the arp table manage the following information. ipv4 address mac address vlan interface up to 508 entries are stored in the arp table, including dynamic and static entries. with the default settings, dynamic entries saved in the arp table are maintained for 300 sec . the entry timeout value can be changed using the arp-ageing-timeout command. dynamic entries saved in the arp table can be cleared regardless of the timeout value, by using the clear arp-cache command. settings for the static entries in the arp table are made using the arp command. up to 255 items can be registered. use the show arp command to check the arp table.</div><div class="display_word">3.4. ARP table settings When sending IPv4 packets, this product uses ARP (Address Resolution Protocol) to obtain the MAC addresses from the IPv4 addresses. The correspondence between IPv4 address and MAC address is saved in the ARP table with the following specifications. The ARP entries saved in the ARP table manage the following information. IPv4 address MAC address VLAN interface Up to 508 entries are stored in the ARP table, including dynamic and static entries. With the default settings, dynamic entries saved in the ARP table are maintained for 300 sec . The entry timeout value can be changed using the arp-ageing-timeout command. Dynamic entries saved in the ARP table can be cleared regardless of the timeout value, by using the clear arp-cache command. Settings for the static entries in the ARP table are made using the arp command. Up to 255 items can be registered. Use the show arp command to check the ARP table.</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#mtuの設定">3.5. MTU settings</div><div class="search_word">3.5. mtu settings this product enables mtu values to be specified for vlan interfaces . use the mtu command to set mtu values. the default mtu value is 1500 bytes , but setting values ranging from 68 bytes to 9216 bytes can be specified. however, the setting range for vlan interfaces with “ipv6 enable” specified is from 1280 bytes to 9216 bytes . a maximum of seven mtu values, besides the default value, can be specified. to route received packets, use the following steps. if the ipv4 header “total length” field value for ipv4 packets exceeds the mtu value, then packets are forwarded divided into parts (ip fragments). ipv4 packets appended with a df (don’t fragment) bit are discarded without being divided into ip fragments and an icmp error (fragmentation needed) is returned. if the ipv6 header “payload length” field value for ipv6 packets exceeds the mtu value, then an icmpv6 error (packet too big) is returned and the packet is discarded. packets larger than the maximum receivable frame size specified by the mru command are not routed. to forward extra large frames, use the mru command to adjust the maximum receivable frame size setting as necessary. *if divided (ip fragmentation) for forwarding, then software is used for forwarding, which limits the forwarding speed and also dramatically increases the cpu usage rate. * it is recommended that the mtu command be used to set a frame size large enough to forward extra-large frames without dividing them (ip fragmentation). this product forwards packets according to the following steps. if the ipv4/ipv6 packet size sent is larger than the mtu value for the vlan interface where packets are being sent, then packets are divided (ip fragmentation) based on the mtu value.</div><div class="display_word">3.5. MTU settings This product enables MTU values to be specified for VLAN interfaces . Use the mtu command to set MTU values. The default MTU value is 1500 bytes , but setting values ranging from 68 bytes to 9216 bytes can be specified. However, the setting range for VLAN interfaces with “ipv6 enable” specified is from 1280 bytes to 9216 bytes . A maximum of seven MTU values, besides the default value, can be specified. To route received packets, use the following steps. If the IPv4 header “Total Length” field value for IPv4 packets exceeds the MTU value, then packets are forwarded divided into parts (IP fragments). IPv4 packets appended with a DF (don’t fragment) bit are discarded without being divided into IP fragments and an ICMP error (fragmentation needed) is returned. If the IPv6 header “Payload Length” field value for IPv6 packets exceeds the MTU value, then an ICMPv6 error (packet too big) is returned and the packet is discarded. Packets larger than the maximum receivable frame size specified by the mru command are not routed. To forward extra large frames, use the mru command to adjust the maximum receivable frame size setting as necessary. *If divided (IP fragmentation) for forwarding, then software is used for forwarding, which limits the forwarding speed and also dramatically increases the CPU usage rate. * It is recommended that the mtu command be used to set a frame size large enough to forward extra-large frames without dividing them (IP fragmentation). This product forwards packets according to the following steps. If the IPv4/IPv6 packet size sent is larger than the MTU value for the VLAN interface where packets are being sent, then packets are divided (IP fragmentation) based on the MTU value.</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. function types operations operating commands ipv4 address settings ipv4 address settings ip address show ipv4 address show ip interface set dynamic ipv4 address by dhcp client ip address dhcp show dhcp client status show dhcp lease enable/disable auto ip function auto-ip enable/disable route information settings set default gateway ip route show default gateway show ip route set static route information ip route show static route information show ip route show route information show ip route arp table settings show arp table show arp set the dynamic entry hold time arp-ageing-timeout clear dynamic entries clear arp-cache set static entry arp mtu settings mtu settings mtu</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Function types Operations Operating commands IPv4 address settings IPv4 address settings ip address Show IPv4 address show ip interface Set dynamic IPv4 address by DHCP client ip address dhcp Show DHCP client status show dhcp lease Enable/disable Auto IP function auto-ip enable/disable Route information settings Set default gateway ip route Show default gateway show ip route Set static route information ip route Show static route information show ip route Show route information show ip route ARP table settings Show ARP table show arp Set the dynamic entry hold time arp-ageing-timeout Clear dynamic entries clear arp-cache Set static entry arp MTU settings MTU settings mtu</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#ipv4ネットワーク環境の設定-dhcp">5.1. IPv4 network environment settings (DHCP)</div><div class="search_word">5.1. ipv4 network environment settings (dhcp) in this example, the ipv4 addresses are set on this product, and an environment is set up for accessing the unit from a remote terminal. maintenance for this product is done using the default vlan (vlan #1). the ipv4 address is set automatically by dhcp for the default vlan (vlan #1). web/tftp access permission is given from a host connected to vlan #1. check the ipv4 address that is currently set. if the default settings are still in effect, the fixed ipv4 address (192.168.100.240/24) is set. yamaha#show ip interface briefinterface            ip-address                status                protocolvlan1                192.168.100.240/24        up                    up specify dhcp for the default vlan (vlan #1). yamaha#configure terminalenter configuration commands, one per line.  end with cntl/z.yamaha(config)#interface vlan1yamaha(config-if)#ip address dhcp check the information that was provided by the dhcp server. yamaha(config-if)#endyamaha#show dhcp leaseinterface vlan1--------------------------------------------------------------------------------ip address:                   192.168.1.3expires:                      yyyy/mm/dd 05:08:41renew:                        yyyy/mm/dd 19:08:41rebind:                       yyyy/mm/dd 02:38:41server:options:  subnet-mask                 255.255.255.0  default-gateway             192.168.1.1  dhcp-lease-time             72000  domain-name-servers         192.168.1.1  dhcp-server-identifier      192.168.1.1  domain-name                 xxx.xxxxx.xx.xx set the default vlan (vlan #1) to permit access from http servers and tftp servers. access using a remote host over the web after settings are made. yamaha(config)#http-server interface vlan1 (1) yamaha(config)#tftp-server interface vlan1 (2) 1 http server access permission 2 tftp server access permission</div><div class="display_word">5.1. IPv4 network environment settings (DHCP) In this example, the IPv4 addresses are set on this product, and an environment is set up for accessing the unit from a remote terminal. Maintenance for this product is done using the default VLAN (VLAN #1). The IPv4 address is set automatically by DHCP for the default VLAN (VLAN #1). Web/TFTP access permission is given from a host connected to VLAN #1. Check the IPv4 address that is currently set. If the default settings are still in effect, the fixed IPv4 address (192.168.100.240/24) is set. Yamaha#show ip interface briefInterface            IP-Address                Status                Protocolvlan1                192.168.100.240/24        up                    up Specify DHCP for the default VLAN (VLAN #1). Yamaha#configure terminalEnter configuration commands, one per line.  End with CNTL/Z.Yamaha(config)#interface vlan1Yamaha(config-if)#ip address dhcp Check the information that was provided by the DHCP server. Yamaha(config-if)#endYamaha#show dhcp leaseInterface vlan1--------------------------------------------------------------------------------IP Address:                   192.168.1.3Expires:                      YYYY/MM/DD 05:08:41Renew:                        YYYY/MM/DD 19:08:41Rebind:                       YYYY/MM/DD 02:38:41Server:Options:  subnet-mask                 255.255.255.0  default-gateway             192.168.1.1  dhcp-lease-time             72000  domain-name-servers         192.168.1.1  dhcp-server-identifier      192.168.1.1  domain-name                 xxx.xxxxx.xx.xx Set the default VLAN (VLAN #1) to permit access from HTTP servers and TFTP servers. Access using a remote host over the Web after settings are made. Yamaha(config)#http-server interface vlan1 (1) Yamaha(config)#tftp-server interface vlan1 (2) 1 HTTP server access permission 2 TFTP server access permission</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution none</div><div class="display_word">6. Points of Caution None</div></div><div id="layer3_layer3_ipv4_basic"><div class="search_title" docfname="layer3_layer3_ipv4_basic" doctitle="Basic" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation layer 2 function: vlan maintenance and operation functions: remote access control yamaha rtpro: what is arp?</div><div class="display_word">7. Related Documentation Layer 2 Function: VLAN Maintenance and Operation Functions: Remote Access Control Yamaha RTpro: What is ARP?</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#ipv6基本設定">Basic IPv6 Settings</div><div class="search_word">basic ipv6 settings</div><div class="display_word">Basic IPv6 Settings</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product is compatible with the following ipv6 network environment settings , mainly for the purpose of maintenance (configuring the switch settings). ipv6 address settings route information settings neighbor cache table settings mtu settings dhcpv6-pd client settings</div><div class="display_word">1. Function Overview This product is compatible with the following IPv6 network environment settings , mainly for the purpose of maintenance (configuring the switch settings). IPv6 address settings Route information settings Neighbor cache table settings MTU settings DHCPv6-PD client settings</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used ra (router advertisement) this is a system that automatically sets address information and network settings on the ipv6 network for devices of the network that is associated with a router. ipv6 address the ipv6 address is 128 bits expressed as hexadecimal. the address is divided into eight fields delimited by “:” with 16 bits in each field. 2001:02f8:0000:0000:1111:2222:0000:4444 the expression can be abbreviated according to the following rules. if the beginning of a field is a zero, the zero can be omitted. a field that consists of four zeros can be abbreviated as a single zero. multiple fields consisting only of consecutive zeros can be abbreviated as “::” in only one location for the entire address . applying these rules to the above address, we get the following. 2001:2f8::1111:2222:0:4444 ipv6 link-local address this is an address that is only valid within the same segment, and is in the following range. [start] fe80:0000:0000:0000:0000:0000:0000:0000 [end] fe80:0000:0000:0000:ffff:ffff:ffff:ffff</div><div class="display_word">2. Definition of Terms Used RA (Router Advertisement) This is a system that automatically sets address information and network settings on the IPv6 network for devices of the network that is associated with a router. IPv6 address The IPv6 address is 128 bits expressed as hexadecimal. The address is divided into eight fields delimited by “:” with 16 bits in each field. 2001:02f8:0000:0000:1111:2222:0000:4444 The expression can be abbreviated according to the following rules. If the beginning of a field is a zero, the zero can be omitted. A field that consists of four zeros can be abbreviated as a single zero. Multiple fields consisting only of consecutive zeros can be abbreviated as “::” in only one location for the entire address . Applying these rules to the above address, we get the following. 2001:2f8::1111:2222:0:4444 IPv6 link-local address This is an address that is only valid within the same segment, and is in the following range. [Start] FE80:0000:0000:0000:0000:0000:0000:0000 [End] FE80:0000:0000:0000:FFFF:FFFF:FFFF:FFFF</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#ipv6アドレスの設定">3.1. IPv6 address settings</div><div class="search_word">3.1. ipv6 address settings this product lets you specify the ipv6 address and prefix length for a vlan interface . the setting method supports either fixed settings , setting addresses automatically via ras (router advertisement) , or setting addresses automatically by dhcpv6 . in order to specify an ipv6 address, ipv6 functionality must be enabled for the corresponding vlan interface. to enable ipv6 functionality, use the ipv6 enable command. when ipv6 functionality is enabled, an ipv6 link local address is automatically assigned. to set a fixed/automatic ipv6 address, use the ipv6 address command. the following actions occur if addresses are specified automatically by dhcpv6. executing the ipv6 address dhcp command enables the dhcpv6 stateful actions (ia_na). if the no ipv6 address dhcp command is executed with addresses specified automatically, a message is sent to the dhcpv6 server indicating that the ipv6 addresses acquired were released. the information obtained from the dhcpv6 server is checked using the show ipv6 dhcp interface command. specifying stateless as the parameter for the ipv6 address autoconfig command used to specify addresses automatically by ra (router advertisements) enables dhcpv6 stateless actions. for ipv6 addresses, up to 5 global addresses (including automatically specified addresses and ipv6 addresses specified by a dhcpv6 client or using dhcpv6-pd) and 1 link local address can be specified per vlan interface . a maximum of 8 ipv6 addresses can be specified for the entire system . the ipv6 address that is allocated to a vlan interface can be checked using the show ipv6 interface command.</div><div class="display_word">3.1. IPv6 address settings This product lets you specify the IPv6 address and prefix length for a VLAN interface . The setting method supports either fixed settings , setting addresses automatically via RAs (router advertisement) , or setting addresses automatically by DHCPv6 . In order to specify an IPv6 address, IPv6 functionality must be enabled for the corresponding VLAN interface. To enable IPv6 functionality, use the ipv6 enable command. When IPv6 functionality is enabled, an IPv6 link local address is automatically assigned. To set a fixed/automatic IPv6 address, use the ipv6 address command. The following actions occur if addresses are specified automatically by DHCPv6. Executing the ipv6 address dhcp command enables the DHCPv6 stateful actions (IA_NA). If the no ipv6 address dhcp command is executed with addresses specified automatically, a message is sent to the DHCPv6 server indicating that the IPv6 addresses acquired were released. The information obtained from the DHCPv6 server is checked using the show ipv6 dhcp interface command. Specifying stateless as the parameter for the ipv6 address autoconfig command used to specify addresses automatically by RA (router advertisements) enables DHCPv6 stateless actions. For IPv6 addresses, up to 5 global addresses (including automatically specified addresses and IPv6 addresses specified by a DHCPv6 client or using DHCPv6-PD) and 1 link local address can be specified per VLAN interface . A maximum of 8 IPv6 addresses can be specified for the entire system . The IPv6 address that is allocated to a VLAN interface can be checked using the show ipv6 interface command.</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#ルート情報の設定">3.2. Route information settings</div><div class="search_word">3.2. route information settings this product refers to a routing table when sending syslog messages and when sending out voluntary ipv6 packets as an ipv6 host for ntp-based time adjustments and so on. this product uses the following functions to perform the routing table operations. set vlan interface route information set default gateway set static route information show route information</div><div class="display_word">3.2. Route information settings This product refers to a routing table when sending syslog messages and when sending out voluntary IPv6 packets as an IPv6 host for NTP-based time adjustments and so on. This product uses the following functions to perform the routing table operations. Set VLAN interface route information Set default gateway Set static route information Show route information</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#vlanインターフェースのルート情報">3.2.1. Route information for VLAN interfaces</div><div class="search_word">3.2.1. route information for vlan interfaces when setting an ipv6 address on this product for a vlan interface, the correspondence between the network address and vlan id is automatically set as route information. when releasing ipv6 addresses set for the vlan interface, the above settings will be deleted.</div><div class="display_word">3.2.1. Route information for VLAN interfaces When setting an IPv6 address on this product for a VLAN interface, the correspondence between the network address and VLAN ID is automatically set as route information. When releasing IPv6 addresses set for the VLAN interface, the above settings will be deleted.</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#デフォルトゲートウェイの設定">3.2.2. Set default gateway</div><div class="search_word">3.2.2. set default gateway the destination for ipv6 packets sent to network addresses that are not set in the routing table can be set as the default gateway on this product. to set the default gateway, use the ipv6 route command. to show the default gateway, use the show ipv6 route command. when ipv6 address dhcp , ipv6 dhcp client pd , or ipv6 address autoconfig commands are specified, device addresses to which ras were sent are automatically added to the default gateway. automatic default gateway registration by ras can be enabled/disabled using the ipv6 nd accept-ra-default-routes command.</div><div class="display_word">3.2.2. Set default gateway The destination for IPv6 packets sent to network addresses that are not set in the routing table can be set as the default gateway on this product. To set the default gateway, use the ipv6 route command. To show the default gateway, use the show ipv6 route command. When ipv6 address dhcp , ipv6 dhcp client pd , or ipv6 address autoconfig commands are specified, device addresses to which RAs were sent are automatically added to the default gateway. Automatic default gateway registration by RAs can be enabled/disabled using the ipv6 nd accept-ra-default-routes command.</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#スタティックルート情報の設定">3.2.3. Set static route information</div><div class="search_word">3.2.3. set static route information a static route to the destination network address (the gateway address to which packets will be sent) can be set on this product. static route information is set using the ipv6 route command. static route information is displayed using the show ipv6 route command.</div><div class="display_word">3.2.3. Set static route information A static route to the destination network address (the gateway address to which packets will be sent) can be set on this product. Static route information is set using the ipv6 route command. Static route information is displayed using the show ipv6 route command.</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#経路表と経路選択">3.2.4. Routing table and route selection</div><div class="search_word">3.2.4. routing table and route selection you will use the following two types of table to specify routing information. rib (routing information base: ip routing table) fib (forwarding information base: ip forwarding table) the roles of each are explained below. rib rib (routing information base: ip routing table) is a database that stores various routing information. a route is registered in the rib in the following cases. when an ipv6 address is assigned to a vlan interface when a static route or a default gateway are specified manually to check the rib, use the show ipv6 route database command. fib fib (forwarding information base: ip forwarding table) is a database that is referenced when deciding how to forward ip packets. of the routes that are registered in the rib, the fib registers only the route that is determined to be “optimal” and is actually used for forwarding packets. the conditions by which a route is determined to be optimal are as follows. the corresponding vlan interface is in the link up state if multiple routes to the same destination are registered in the rib, only one is decided in the following order of priority a route whose gateway has a higher ip address value takes priority to check the fib, use the show ipv6 route command.</div><div class="display_word">3.2.4. Routing table and route selection You will use the following two types of table to specify routing information. RIB (Routing Information Base: IP routing table) FIB (Forwarding Information Base: IP forwarding table) The roles of each are explained below. RIB RIB (Routing Information Base: IP routing table) is a database that stores various routing information. A route is registered in the RIB in the following cases. When an IPv6 address is assigned to a VLAN interface When a static route or a default gateway are specified manually To check the RIB, use the show ipv6 route database command. FIB FIB (Forwarding Information Base: IP forwarding table) is a database that is referenced when deciding how to forward IP packets. Of the routes that are registered in the RIB, the FIB registers only the route that is determined to be “optimal” and is actually used for forwarding packets. The conditions by which a route is determined to be optimal are as follows. The corresponding VLAN interface is in the link up state If multiple routes to the same destination are registered in the RIB, only one is decided in the following order of priority A route whose gateway has a higher IP address value takes priority To check the FIB, use the show ipv6 route command.</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#neighbor-キャッシュテーブルの設定">3.3. Neighbor cache table settings</div><div class="search_word">3.3. neighbor cache table settings when sending ipv6 packets, this product uses neighbor discovery protocol to obtain the mac addresses from the ipv6 addresses. the correspondence between ipv6 address and mac address is saved in the neighbor cache table with the following specifications. the neighbor cache entries saved in the neighbor cache table manage the following information. ipv6 address mac address vlan interface up to 128 entries are stored in the neighbor cache table, including dynamic and static entries. dynamic entries saved in the neighbor cache table can be cleared by using the clear ipv6 neighbors command. settings for the static entries in the neighbor cache table are made using the ipv6 neighbor command. up to 63 items can be registered. use the show ipv6 neighbor command to check the neighbor cache table.</div><div class="display_word">3.3. Neighbor cache table settings When sending IPv6 packets, this product uses Neighbor Discovery Protocol to obtain the MAC addresses from the IPv6 addresses. The correspondence between IPv6 address and MAC address is saved in the neighbor cache table with the following specifications. The neighbor cache entries saved in the neighbor cache table manage the following information. IPv6 address MAC address VLAN interface Up to 128 entries are stored in the neighbor cache table, including dynamic and static entries. Dynamic entries saved in the neighbor cache table can be cleared by using the clear ipv6 neighbors command. Settings for the static entries in the neighbor cache table are made using the ipv6 neighbor command. Up to 63 items can be registered. Use the show ipv6 neighbor command to check the neighbor cache table.</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#mtuの設定">3.4. MTU settings</div><div class="search_word">3.4. mtu settings this product enables mtu values to be specified for vlan interfaces . use the mtu command to set mtu values. the default mtu value is 1500 bytes , but setting values ranging from 68 bytes to 9216 bytes can be specified. however, the setting range for vlan interfaces with “ipv6 enable” specified is from 1280 bytes to 9216 bytes . a maximum of seven mtu values, besides the default value, can be specified. to route received packets, use the following steps. if the ipv4 header “total length” field value for ipv4 packets exceeds the mtu value, then packets are forwarded divided into parts (ip fragments). ipv4 packets appended with a df (don’t fragment) bit are discarded without being divided into ip fragments and an icmp error (fragmentation needed) is returned. if the ipv6 header “payload length” field value for ipv6 packets exceeds the mtu value, then an icmpv6 error (packet too big) is returned and the packet is discarded. packets larger than the maximum receivable frame size specified by the mru command are not routed. to forward extra large frames, use the mru command to adjust the maximum receivable frame size setting as necessary. *if divided (ip fragmentation) for forwarding, then software is used for forwarding, which limits the forwarding speed and also dramatically increases the cpu usage rate. * it is recommended that the mtu command be used to set a frame size large enough to forward extra-large frames without dividing them (ip fragmentation). this product forwards packets according to the following steps. if the ipv4/ipv6 packet size sent is larger than the mtu value for the vlan interface where packets are being sent, then packets are divided (ip fragmentation) based on the mtu value.</div><div class="display_word">3.4. MTU settings This product enables MTU values to be specified for VLAN interfaces . Use the mtu command to set MTU values. The default MTU value is 1500 bytes , but setting values ranging from 68 bytes to 9216 bytes can be specified. However, the setting range for VLAN interfaces with “ipv6 enable” specified is from 1280 bytes to 9216 bytes . A maximum of seven MTU values, besides the default value, can be specified. To route received packets, use the following steps. If the IPv4 header “Total Length” field value for IPv4 packets exceeds the MTU value, then packets are forwarded divided into parts (IP fragments). IPv4 packets appended with a DF (don’t fragment) bit are discarded without being divided into IP fragments and an ICMP error (fragmentation needed) is returned. If the IPv6 header “Payload Length” field value for IPv6 packets exceeds the MTU value, then an ICMPv6 error (packet too big) is returned and the packet is discarded. Packets larger than the maximum receivable frame size specified by the mru command are not routed. To forward extra large frames, use the mru command to adjust the maximum receivable frame size setting as necessary. *If divided (IP fragmentation) for forwarding, then software is used for forwarding, which limits the forwarding speed and also dramatically increases the CPU usage rate. * It is recommended that the mtu command be used to set a frame size large enough to forward extra-large frames without dividing them (IP fragmentation). This product forwards packets according to the following steps. If the IPv4/IPv6 packet size sent is larger than the MTU value for the VLAN interface where packets are being sent, then packets are divided (IP fragmentation) based on the MTU value.</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#dhcpv6-pdクライアントの設定">3.5. DHCPv6-PD client settings</div><div class="search_word">3.5. dhcpv6-pd client settings this product enables dhcpv6-pd clients to be specified for vlan interfaces . prefixes can be obtained from a dhcpv6-pd server for specifying addresses or reassigning the user’s own dhcpv6 server. executing the ipv6 dhcp client pd and prefixname commands will enable dhcpv6-pd stateful actions (ia_pd). prefixes obtained with the prefixname command can be used for the following. using the ipv6 address pd command to specify ipv6 addresses using the prefixes obtained. using the range command in the dhcpv6 mode to specify the range of ipv6 addresses to be dynamically assigned in the dhcpv6 server using the prefixes obtained (only on models compatible with dhcpv6 server). using the prefix-delegation command in the dhcpv6 mode to reassign prefixes to the dhcpv6 server using the prefixes obtained (only on models compatible with dhcpv6 server). the information obtained from the dhcpv6 server is checked using the show ipv6 dhcp interface command.</div><div class="display_word">3.5. DHCPv6-PD client settings This product enables DHCPv6-PD clients to be specified for VLAN interfaces . Prefixes can be obtained from a DHCPv6-PD server for specifying addresses or reassigning the user’s own DHCPv6 server. Executing the ipv6 dhcp client pd and prefixname commands will enable DHCPv6-PD stateful actions (IA_PD). Prefixes obtained with the prefixname command can be used for the following. Using the ipv6 address pd command to specify IPv6 addresses using the prefixes obtained. Using the range command in the DHCPv6 mode to specify the range of IPv6 addresses to be dynamically assigned in the DHCPv6 server using the prefixes obtained (only on models compatible with DHCPv6 server). Using the prefix-delegation command in the DHCPv6 mode to reassign prefixes to the DHCPv6 server using the prefixes obtained (only on models compatible with DHCPv6 server). The information obtained from the DHCPv6 server is checked using the show ipv6 dhcp interface command.</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. function types operations operating commands ipv6 address settings enable/disable ipv6 addresses ipv6 enable/disable ipv6 address settings ipv6 address specifies ipv6 addresses using dhcpv6-pd. ipv6 address pd show ipv6 address show ipv6 interface set ra setting for ipv6 address ipv6 address autoconfig specifies ipv6 addresses dynamically using a dhcpv6 client. ipv6 address dhcp dhcpv6-pd client settings ipv6 dhcp client pd specifies automatic registration of default gateways using an ra. ipv6 nd accept-ra-default-routes displays status of dhcpv6 client. show ipv6 dhcp interface resets dhcpv6 client. clear ipv6 dhcp client setting for nd prefix received when setting dhcpv6 client settings ipv6 dhcp client nd-prefix route information settings set default gateway ipv6 route show default gateway show ipv6 route set static route information ipv6 route show static route information show ipv6 route show route information show ipv6 route neighbor cache settings set static neighbor cache entry ipv6 neighbors show neighbor cache table show ipv6 neighbors clear neighbor cache table clear ipv6 neighbors mtu settings mtu settings mtu</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Function types Operations Operating commands IPv6 address settings Enable/disable IPv6 addresses ipv6 enable/disable IPv6 address settings ipv6 address Specifies IPv6 addresses using DHCPv6-PD. ipv6 address pd Show IPv6 address show ipv6 interface Set RA setting for IPv6 address ipv6 address autoconfig Specifies IPv6 addresses dynamically using a DHCPv6 client. ipv6 address dhcp DHCPv6-PD client settings ipv6 dhcp client pd Specifies automatic registration of default gateways using an RA. ipv6 nd accept-ra-default-routes Displays status of DHCPv6 client. show ipv6 dhcp interface Resets DHCPv6 client. clear ipv6 dhcp client Setting for ND prefix received when setting DHCPv6 client settings ipv6 dhcp client nd-prefix Route information settings Set default gateway ipv6 route Show default gateway show ipv6 route Set static route information ipv6 route Show static route information show ipv6 route Show route information show ipv6 route Neighbor cache settings Set static neighbor cache entry ipv6 neighbors Show neighbor cache table show ipv6 neighbors Clear neighbor cache table clear ipv6 neighbors MTU settings MTU settings mtu</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#ipv6ネットワーク環境の設定-固定設定">5.1. Setting up an IPv6 network environment (fixed settings)</div><div class="search_word">5.1. setting up an ipv6 network environment (fixed settings) in this example, the ipv6 addresses are manually set on this product, and an environment is set up for accessing the unit from a remote terminal. maintenance for this product is done using the default vlan (vlan #1). the ipv6 address is set manually for the default vlan (vlan #1). web/tftp access permission is given from a host connected to vlan #1. this sets 2001:db8:1::2/64 for the default vlan (vlan #1). yamaha#configure terminalenter configuration commands, one per line.  end with cntl/z.yamaha(config)#interface vlan1yamaha(config-if)#ipv6 enable (1) yamaha(config-if)#ipv6 address 2001:db8:1::2/64 (2) 1 enable ipv6 2 specify an ipv6 address check the ipv6 address that was set. yamaha(config-if)#endyamaha#show ipv6 interface briefinterface        ip-address                                  status                protocolvlan1            2001:db8:1::2/64                            up                    up                 fe80::2a0:deff:fe:2/64 set the default vlan (vlan #1) to permit access from http servers and tftp servers. access using a remote host over the web after settings are made. yamaha(config)#http-server interface vlan1 (1) yamaha(config)#tftp-server interface vlan1 (2) 1 http server access permission 2 tftp server access permission</div><div class="display_word">5.1. Setting up an IPv6 network environment (fixed settings) In this example, the IPv6 addresses are manually set on this product, and an environment is set up for accessing the unit from a remote terminal. Maintenance for this product is done using the default VLAN (VLAN #1). The IPv6 address is set manually for the default VLAN (VLAN #1). Web/TFTP access permission is given from a host connected to VLAN #1. This sets 2001:db8:1::2/64 for the default VLAN (VLAN #1). Yamaha#configure terminalEnter configuration commands, one per line.  End with CNTL/Z.Yamaha(config)#interface vlan1Yamaha(config-if)#ipv6 enable (1) Yamaha(config-if)#ipv6 address 2001:db8:1::2/64 (2) 1 Enable IPv6 2 Specify an IPv6 address Check the IPv6 address that was set. Yamaha(config-if)#endYamaha#show ipv6 interface briefInterface        IP-Address                                  Status                Protocolvlan1            2001:db8:1::2/64                            up                    up                 fe80::2a0:deff:fe:2/64 Set the default VLAN (VLAN #1) to permit access from HTTP servers and TFTP servers. Access using a remote host over the Web after settings are made. Yamaha(config)#http-server interface vlan1 (1) Yamaha(config)#tftp-server interface vlan1 (2) 1 HTTP server access permission 2 TFTP server access permission</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#ipv6ネットワーク環境の設定-raによる自動設定">5.2. Setting up an IPv6 network environment (automatic settings using RA)</div><div class="search_word">5.2. setting up an ipv6 network environment (automatic settings using ra) in this example, the ipv6 addresses are automatically set on this product, and an environment is set up for accessing the unit from a remote terminal. maintenance for this product is done using the default vlan (vlan #1). the ipv6 address is set automatically by ra for the default vlan (vlan #1). web/tftp access permission is given from a host connected to vlan #1. specify ra for the default vlan (vlan #1). yamaha#configure terminalenter configuration commands, one per line.  end with cntl/z.yamaha(config)#interface vlan1yamaha(config-if)#ipv6 enable (1) yamaha(config-if)#ipv6 address autoconfig (2) 1 enable ipv6 2 set up ra check the ipv6 address that was obtained from ra. yamaha(config-if)#endyamaha#show ipv6 interface briefinterface        ip-address                                  status                protocolvlan1            2001:db8::2a0:deff:fe:2/64                  up                    up                 fe80::2a0:deff:fe:2/64 set the default vlan (vlan #1) to permit access from http servers and tftp servers. access using a remote host over the web after settings are made. yamaha(config)#http-server interface vlan1 (1) yamaha(config)#tftp-server interface vlan1 (2) 1 http server access permission 2 tftp server access permission</div><div class="display_word">5.2. Setting up an IPv6 network environment (automatic settings using RA) In this example, the IPv6 addresses are automatically set on this product, and an environment is set up for accessing the unit from a remote terminal. Maintenance for this product is done using the default VLAN (VLAN #1). The IPv6 address is set automatically by RA for the default VLAN (VLAN #1). Web/TFTP access permission is given from a host connected to VLAN #1. Specify RA for the default VLAN (VLAN #1). Yamaha#configure terminalEnter configuration commands, one per line.  End with CNTL/Z.Yamaha(config)#interface vlan1Yamaha(config-if)#ipv6 enable (1) Yamaha(config-if)#ipv6 address autoconfig (2) 1 Enable IPv6 2 Set up RA Check the IPv6 address that was obtained from RA. Yamaha(config-if)#endYamaha#show ipv6 interface briefInterface        IP-Address                                  Status                Protocolvlan1            2001:db8::2a0:deff:fe:2/64                  up                    up                 fe80::2a0:deff:fe:2/64 Set the default VLAN (VLAN #1) to permit access from HTTP servers and TFTP servers. Access using a remote host over the Web after settings are made. Yamaha(config)#http-server interface vlan1 (1) Yamaha(config)#tftp-server interface vlan1 (2) 1 HTTP server access permission 2 TFTP server access permission</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#ipv6ネットワーク環境の設定-dhcpv6">5.3. IPv6 network environment setting (DHCPv6)</div><div class="search_word">5.3. ipv6 network environment setting (dhcpv6) in this example, the ipv6 addresses are set on this product, and an environment is set up for accessing the unit from a remote terminal. maintenance for this product is done using the default vlan (vlan #1). the ipv6 address is set automatically by dhcpv6 for the default vlan (vlan #1). web/tftp access permission is given from a host connected to vlan #1. specify dhcpv6 for the default vlan (vlan #1). yamaha#configure terminalenter configuration commands, one per line.  end with cntl/z.yamaha(config)#interface vlan1yamaha(config-if)#ipv6 enable (1) yamaha(config-if)#ipv6 address dhcp (2) 1 enable ipv6 2 set dhcpv6 check the ipv6 address information obtained by dhcpv6. yamaha(config-if)#endyamaha#show ipv6 interface briefinterface       ipv6-address                                admin-status  link-statusvlan1          *2001:db8:1:aa10::dd37/128                fe80::ae44:f2ff:fe84:efdd/64                up            up set the default vlan (vlan #1) to permit access from http servers and tftp servers. access using a remote host over the web after settings are made. yamaha(config)#http-server interface vlan1 (1) yamaha(config)#tftp-server interface vlan1 (2) 1 http server access permission 2 tftp server access permission</div><div class="display_word">5.3. IPv6 network environment setting (DHCPv6) In this example, the IPv6 addresses are set on this product, and an environment is set up for accessing the unit from a remote terminal. Maintenance for this product is done using the default VLAN (VLAN #1). The IPv6 address is set automatically by DHCPv6 for the default VLAN (VLAN #1). Web/TFTP access permission is given from a host connected to VLAN #1. Specify DHCPv6 for the default VLAN (VLAN #1). Yamaha#configure terminalEnter configuration commands, one per line.  End with CNTL/Z.Yamaha(config)#interface vlan1Yamaha(config-if)#ipv6 enable (1) Yamaha(config-if)#ipv6 address dhcp (2) 1 Enable IPv6 2 Set DHCPv6 Check the IPv6 address information obtained by DHCPv6. Yamaha(config-if)#endYamaha#show ipv6 interface briefInterface       IPv6-Address                                Admin-Status  Link-Statusvlan1          *2001:db8:1:aa10::dd37/128                fe80::ae44:f2ff:fe84:efdd/64                up            up Set the default VLAN (VLAN #1) to permit access from HTTP servers and TFTP servers. Access using a remote host over the Web after settings are made. Yamaha(config)#http-server interface vlan1 (1) Yamaha(config)#tftp-server interface vlan1 (2) 1 HTTP server access permission 2 TFTP server access permission</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#ipv6ネットワーク環境の設定-dhcpv6-pd">5.4. IPv6 network environment settings (DHCPv6-PD)</div><div class="search_word">5.4. ipv6 network environment settings (dhcpv6-pd) in this example, the ipv6 addresses are set on this product, and an environment is set up for accessing the unit from a remote terminal. maintenance for this product is done using the default vlan (vlan #1). dhcpv6-pd is specified for vlan #100 and prefixes are obtained. the ipv6 address is specified using a prefix obtained by dhcpv6-pd for the default vlan (vlan #1). web/tftp access permission is given from a host connected to vlan #1. specify dhcpv6-pd for vlan #100. yamaha#configure terminalenter configuration commands, one per line.  end with cntl/z.yamaha(config)#interface vlan100yamaha(config-if)#ipv6 enableyamaha(config-if)#ipv6 dhcp client pd pd_vlan100           ... (obtain a prefix using the name pd_vlan100)yamaha(config-if)#end check the prefix information obtained by dhcpv6-pd. yamaha#show ipv6 dhcp interfaceinterface vlan100  client type        : ia_pd  prefix name        : pd_vlan100  prefix             : 2001:db8:1:aaf0::/60 (1) iaid               : 0f28924a  duid               : 000100010000000000a0de000000  preferred lifetime : 604800  valid lifetime     : 2592000  expires            : 2023/4/19 08:08:04 1 obtain 2001:db8:1:aaf0::/60 specify an ipv6 address for the default vlan (vlan #1). use the prefix obtained by dhcpv6-pd to specify 2001:db8:1:aaf2::1/64. yamaha#configure terminalenter configuration commands, one per line.  end with cntl/z.yamaha(config)#interface vlan1yamaha(config-if)#ipv6 enable (1) yamaha(config-if)#ipv6 address pd pd_vlan100 ::2:0:0:0:1/64 (2) 1 enable ipv6 2 specify an ipv6 address check the ipv6 address that was set. yamaha(config-if)#endyamaha#show ipv6 interface briefinterface       ip-address                                  admin-status  link-statusvlan1          *2001:db8:1:aaf2::1/64                fe80::ae44:f2ff:fe84:efdd/64                up            up set the default vlan (vlan #1) to permit access from http servers and tftp servers. access using a remote host over the web after settings are made. yamaha(config)#http-server interface vlan1 (1) yamaha(config)#tftp-server interface vlan1 (2) 1 http server access permission 2 tftp server access permission</div><div class="display_word">5.4. IPv6 network environment settings (DHCPv6-PD) In this example, the IPv6 addresses are set on this product, and an environment is set up for accessing the unit from a remote terminal. Maintenance for this product is done using the default VLAN (VLAN #1). DHCPv6-PD is specified for VLAN #100 and prefixes are obtained. The IPv6 address is specified using a prefix obtained by DHCPv6-PD for the default VLAN (VLAN #1). Web/TFTP access permission is given from a host connected to VLAN #1. Specify DHCPv6-PD for VLAN #100. Yamaha#configure terminalEnter configuration commands, one per line.  End with CNTL/Z.Yamaha(config)#interface vlan100Yamaha(config-if)#ipv6 enableYamaha(config-if)#ipv6 dhcp client pd PD_VLAN100           ... (Obtain a prefix using the name PD_VLAN100)Yamaha(config-if)#end Check the prefix information obtained by DHCPv6-PD. Yamaha#show ipv6 dhcp interfaceInterface vlan100  Client Type        : IA_PD  Prefix name        : PD_VLAN100  prefix             : 2001:db8:1:aaf0::/60 (1) IAID               : 0f28924a  DUID               : 000100010000000000a0de000000  preferred lifetime : 604800  valid lifetime     : 2592000  expires            : 2023/4/19 08:08:04 1 Obtain 2001:db8:1:aaf0::/60 Specify an IPv6 address for the default VLAN (VLAN #1). Use the prefix obtained by DHCPv6-PD to specify 2001:db8:1:aaf2::1/64. Yamaha#configure terminalEnter configuration commands, one per line.  End with CNTL/Z.Yamaha(config)#interface vlan1Yamaha(config-if)#ipv6 enable (1) Yamaha(config-if)#ipv6 address pd PD_VLAN100 ::2:0:0:0:1/64 (2) 1 Enable IPv6 2 Specify an IPv6 address Check the IPv6 address that was set. Yamaha(config-if)#endYamaha#show ipv6 interface briefInterface       IP-Address                                  Admin-Status  Link-Statusvlan1          *2001:db8:1:aaf2::1/64                fe80::ae44:f2ff:fe84:efdd/64                up            up Set the default VLAN (VLAN #1) to permit access from HTTP servers and TFTP servers. Access using a remote host over the Web after settings are made. Yamaha(config)#http-server interface vlan1 (1) Yamaha(config)#tftp-server interface vlan1 (2) 1 HTTP server access permission 2 TFTP server access permission</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution if opposing dhcpv6 server settings are changed while dhcpv6 client functionality is being used, the setting changes may not be applied properly in the dhcpv6 client. if that occurs, use the clear ipv6 dhcp client command to reset the dhcpv6 client. the dhcpv6 client for this product does not support the following operations. requesting an sol_max_rt option for solicit messages sent by a dhcpv6 client. overwriting sol_max_rt parameter settings inside a dhcpv6 client after a sol_max_rt option is received. note that sol_max_rt parameters inside a dhcpv6 client remain active for a fixed 120 seconds. requesting an inf_max_rt option for request messages sent by a dhcpv6 client. overwriting inf_max_rt parameter settings inside a dhcpv6 client after an inf_max_rt option is received. note that inf_max_rt parameters inside a dhcpv6 client remain active for a fixed 120 seconds.</div><div class="display_word">6. Points of Caution If opposing DHCPv6 server settings are changed while DHCPv6 client functionality is being used, the setting changes may not be applied properly in the DHCPv6 client. If that occurs, use the clear ipv6 dhcp client command to reset the DHCPv6 client. The DHCPv6 client for this product does not support the following operations. Requesting an SOL_MAX_RT option for solicit messages sent by a DHCPv6 client. Overwriting SOL_MAX_RT parameter settings inside a DHCPv6 client after a SOL_MAX_RT option is received. Note that SOL_MAX_RT parameters inside a DHCPv6 client remain active for a fixed 120 seconds. Requesting an INF_MAX_RT option for request messages sent by a DHCPv6 client. Overwriting INF_MAX_RT parameter settings inside a DHCPv6 client after an INF_MAX_RT option is received. Note that INF_MAX_RT parameters inside a DHCPv6 client remain active for a fixed 120 seconds.</div></div><div id="layer3_layer3_ipv6_basic"><div class="search_title" docfname="layer3_layer3_ipv6_basic" doctitle="Basic" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation layer 2 function: vlan maintenance and operation functions: remote access control yamaha rtpro: what is arp?</div><div class="display_word">7. Related Documentation Layer 2 Function: VLAN Maintenance and Operation Functions: Remote Access Control Yamaha RTpro: What is ARP?</div></div><div id="layer3_layer3_static_routing"><div class="search_title" docfname="layer3_layer3_static_routing" doctitle="Static" link="#スタティックルーティング">Static Routing</div><div class="search_word">static routing</div><div class="display_word">Static Routing</div></div><div id="layer3_layer3_static_routing"><div class="search_title" docfname="layer3_layer3_static_routing" doctitle="Static" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview in this product, static routing (static route information) can be used for route control in ip networks. an administrator can explicitly register route information by entering a command. you can set both static routes for ipv4 networks and static routes for ipv6 networks. there are the following two types of static route information. type description vlan interface route information route information automatically registered by setting the ip address using the ip/ipv6 address command static route information route information registered by route setting by ip/ipv6 route command use the show ip/ipv6 route command to display the routing table.</div><div class="display_word">1. Function Overview In this product, static routing (static route information) can be used for route control in IP networks. An administrator can explicitly register route information by entering a command. You can set both static routes for IPv4 networks and static routes for IPv6 networks. There are the following two types of static route information. Type Description VLAN interface route information Route information automatically registered by setting the IP address using the ip/ipv6 address command Static route information Route information registered by route setting by ip/ipv6 route command Use the show ip/ipv6 route command to display the routing table.</div></div><div id="layer3_layer3_static_routing"><div class="search_title" docfname="layer3_layer3_static_routing" doctitle="Static" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used none</div><div class="display_word">2. Definition of Terms Used None</div></div><div id="layer3_layer3_static_routing"><div class="search_title" docfname="layer3_layer3_static_routing" doctitle="Static" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="layer3_layer3_static_routing"><div class="search_title" docfname="layer3_layer3_static_routing" doctitle="Static" link="#vlanインターフェースルート情報">3.1. VLAN interface route information</div><div class="search_word">3.1. vlan interface route information route information that is automatically registered by setting the ip address using the ip/ipv6 address command. it is the route information of the network directly connected to this product and is associated with the interface. set 192.168.100.1/24 as the ip address for the vlan1 interface and display the routing table. yamaha(config)# interface vlan1yamaha(config-if)# ip address 192.168.100.1/24yamaha(config-if)# exityamaha(config)# exityamaha#show ip routecodes: c - connected, s - static       * - candidate defaultc       192.168.100.0/24 is directly connected, vlan1gateway of last resort is not set</div><div class="display_word">3.1. VLAN interface route information Route information that is automatically registered by setting the IP address using the ip/ipv6 address command. It is the route information of the network directly connected to this product and is associated with the interface. Set 192.168.100.1/24 as the IP address for the VLAN1 interface and display the routing table. Yamaha(config)# interface vlan1Yamaha(config-if)# ip address 192.168.100.1/24Yamaha(config-if)# exitYamaha(config)# exitYamaha#show ip routeCodes: C - connected, S - static       * - candidate defaultC       192.168.100.0/24 is directly connected, vlan1Gateway of last resort is not set</div></div><div id="layer3_layer3_static_routing"><div class="search_title" docfname="layer3_layer3_static_routing" doctitle="Static" link="#スタティックルート情報">3.2. Static route information</div><div class="search_word">3.2. static route information route information registered by route setting by ip/ipv6 route command. you can statically set a route to a specific network or set a default gateway. when setting the default gateway, specify 0.0.0.0/0 as the destination network. up to 128 ipv4 static routes with the ip route command can be set. up to 32 ipv6 static routes with the ipv6 route command can be set. set the gateway for the route addressed to 172.16.0.0/16 to 192.168.100.254 and display the routing table. yamaha(config)# ip route 172.16.0.0/24 192.168.100.254yamaha(config)# exityamaha# show ip routecodes: c - connected, s - static       * - candidate defaults       172.16.0.0/24 [1/0] via 192.168.100.254, vlan1c       192.168.100.0/24 is directly connected, vlan1gateway of last resort is not set set 192.168.100.200 as the default gateway and display the routing table. yamaha(config)# ip route 0.0.0.0/0 192.168.100.200yamaha(config)# exityamaha# show ip routecodes: c - connected, s - static       * - candidate defaultgateway of last resort is 192.168.100.200 to network 0.0.0.0s*      0.0.0.0/0 [1/0] via 192.168.100.200, vlan1s       172.16.0.0/24 [1/0] via 192.168.100.254, vlan1c       192.168.100.0/24 is directly connected, vlan1</div><div class="display_word">3.2. Static route information Route information registered by route setting by ip/ipv6 route command. You can statically set a route to a specific network or set a default gateway. When setting the default gateway, specify 0.0.0.0/0 as the destination network. Up to 128 IPv4 static routes with the ip route command can be set. Up to 32 IPv6 static routes with the ipv6 route command can be set. Set the gateway for the route addressed to 172.16.0.0/16 to 192.168.100.254 and display the routing table. Yamaha(config)# ip route 172.16.0.0/24 192.168.100.254Yamaha(config)# exitYamaha# show ip routeCodes: C - connected, S - static       * - candidate defaultS       172.16.0.0/24 [1/0] via 192.168.100.254, vlan1C       192.168.100.0/24 is directly connected, vlan1Gateway of last resort is not set Set 192.168.100.200 as the default gateway and display the routing table. Yamaha(config)# ip route 0.0.0.0/0 192.168.100.200Yamaha(config)# exitYamaha# show ip routeCodes: C - connected, S - static       * - candidate defaultGateway of last resort is 192.168.100.200 to network 0.0.0.0S*      0.0.0.0/0 [1/0] via 192.168.100.200, vlan1S       172.16.0.0/24 [1/0] via 192.168.100.254, vlan1C       192.168.100.0/24 is directly connected, vlan1</div></div><div id="layer3_layer3_static_routing"><div class="search_title" docfname="layer3_layer3_static_routing" doctitle="Static" link="#経路表の表示">3.3. Display of routing table</div><div class="search_word">3.3. display of routing table there are two routing tables: an ip forwarding table (fib) in which only route information actually used for packet forwarding is registered, and an ip routing table (rib) in which all route information is registered. all vlan interface route information and static route information are registered in the ip routing table. within this, only the route information that is actually used in the packet forwarding process is registered in the ip forwarding table. use the show ip/ipv6 route command to display the ip forwarding table and the ip routing table. in the routing table, vlan interface route information and static route information are displayed as follows. type display vlan interface route information c - connected static route information s - static if no option is specified for show ip/ipv6 route, the ip forwarding table is displayed. you can display the ip routing table by specifying the database option with show ip/ipv6 route. you can also display summary information and specific route information only by specifying other options. option description ip address display route information used when forwarding packets to the specified ip address. ip address and prefix display route information that matches the specified information. database display all configured route information (ip routing table). summary display ip routing table summary information for details on how to use the show ip route command, refer to the command reference.</div><div class="display_word">3.3. Display of routing table There are two routing tables: an IP forwarding table (FIB) in which only route information actually used for packet forwarding is registered, and an IP routing table (RIB) in which all route information is registered. All VLAN interface route information and static route information are registered in the IP routing table. Within this, only the route information that is actually used in the packet forwarding process is registered in the IP forwarding table. Use the show ip/ipv6 route command to display the IP forwarding table and the IP routing table. In the routing table, VLAN interface route information and static route information are displayed as follows. Type Display VLAN interface route information C - connected Static route information S - static If no option is specified for show ip/ipv6 route, the IP forwarding table is displayed. You can display the IP routing table by specifying the database option with show ip/ipv6 route. You can also display summary information and specific route information only by specifying other options. Option Description IP address Display route information used when forwarding packets to the specified IP address. IP address and prefix Display route information that matches the specified information. database Display all configured route information (IP routing table). summary Display IP routing table summary information For details on how to use the show ip route command, refer to the command reference.</div></div><div id="layer3_layer3_static_routing"><div class="search_title" docfname="layer3_layer3_static_routing" doctitle="Static" link="#ルート情報の優先度管理距離">3.4. Route information priority (management distance)</div><div class="search_word">3.4. route information priority (management distance) route information has a priority commonly called administrative distance. this is used to determine which is prioritized when route information to the same destination is registered with vlan interface route information and static route information. the priority of route information can be applied not only to static routing but also to dynamic routing. the priority of static routing route information can be specified in the range of 1 to 255 using the option at the end of the ip route command. the smaller the value, the higher the priority. in the initial state, the priority is as follows. type initial priority how to change priority vlan interface route information none (overrides any other route information) settings cannot be changed. static route information 1 it can be specified in the range of 1 to 255 by the option at the end of the ip/ipv6 route command.</div><div class="display_word">3.4. Route information priority (management distance) Route information has a priority commonly called Administrative Distance. This is used to determine which is prioritized when route information to the same destination is registered with VLAN interface route information and static route information. The priority of route information can be applied not only to static routing but also to dynamic routing. The priority of static routing route information can be specified in the range of 1 to 255 using the option at the end of the ip route command. The smaller the value, the higher the priority. In the initial state, the priority is as follows. Type Initial priority How to change priority VLAN interface route information None (overrides any other route information) Settings cannot be changed. Static route information 1 It can be specified in the range of 1 to 255 by the option at the end of the ip/ipv6 route command.</div></div><div id="layer3_layer3_static_routing"><div class="search_title" docfname="layer3_layer3_static_routing" doctitle="Static" link="#ルーティング機能の有効化">3.5. Enabling the routing function</div><div class="search_word">3.5. enabling the routing function use the ip/ipv6 forwarding command to enable/disable the routing function. in the initial state, the routing function is enabled for both ipv4 and ipv6.</div><div class="display_word">3.5. Enabling the routing function Use the ip/ipv6 forwarding command to enable/disable the routing function. In the initial state, the routing function is enabled for both IPv4 and IPv6.</div></div><div id="layer3_layer3_static_routing"><div class="search_title" docfname="layer3_layer3_static_routing" doctitle="Static" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. list of related commands function types operations operating commands route information settings set static route information ip route / ipv6 route show static route information show ip route / show ipv6 route show route information show ip route / show ipv6 route routing function settings routing function settings ip forwarding / ipv6 forwarding routing function status display show ip forwarding / show ipv6 forwarding</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. List of related commands Function types Operations Operating commands Route information settings Set static route information ip route / ipv6 route Show static route information show ip route / show ipv6 route Show route information show ip route / show ipv6 route Routing function settings Routing function settings ip forwarding / ipv6 forwarding Routing function status display show ip forwarding / show ipv6 forwarding</div></div><div id="layer3_layer3_static_routing"><div class="search_title" docfname="layer3_layer3_static_routing" doctitle="Static" link="#注意事項">5. Points of Caution</div><div class="search_word">5. points of caution none</div><div class="display_word">5. Points of Caution None</div></div><div id="layer3_layer3_static_routing"><div class="search_title" docfname="layer3_layer3_static_routing" doctitle="Static" link="#関連文書">6. Related Documentation</div><div class="search_word">6. related documentation none</div><div class="display_word">6. Related Documentation None</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#本製品で使われるオープンソースソフトウェアのライセンスについて">About Licenses of Open Source Software Used in This Product</div><div class="search_word">about licenses of open source software used in this product</div><div class="display_word">About Licenses of Open Source Software Used in This Product</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#オープンソースソフトウェア一覧">1. List of Open Source Software</div><div class="search_word">1. list of open source software the open source software used in this product and their licenses are shown in the table below. open source software and licenses open source software license busybox gplv2 bzip2 bsd-style civetweb mit csvjson.js mit d3 3-clause bsd dynatree mit/gplv2 e2fsprogs gplv2 explorercanvas apache 2.0 expat mit freeradius gplv2 glib lgplv2 iptables gplv2 isc dhcp isc jqcanvas mit jqplot mit/gplv2 jquery mit jquery blockui plugin mit/gpl jquery cookie plugin mit jquery datetimepicker plugin mit jquery file upload plugin mit jquery iframe transport plugin mit jquery lined textarea plugin mit jquery migrate mit jquery ui mit jquery ui touch punch mit/gplv2 jquery ui widget mit jquery ui ympicker mit/gplv2 jquery xdomainrequest transport plugin mit libcurl mit/x derivate libevent 3-clause bsd libffi mit libintl lgplv2 linux gplv2 linux-pam linux-pam lzo gplv2 mtd-utils gplv2 net-snmp net-snmp ntp ntp openssh openssh openssl openssl powertip mit ptpd 2-clause bsd rsync gplv3 shellinabox gplv2 tablednd plug-in for jquery mit the html5 shiv mit/gplv2 tokyocabinet lgplv2 unbound 3-clause bsd, isc, mit unzip info-zip zip info-zip zlib zlib about gpl/lgpl licensed software this product includes software licensed under the gnu general public license (gpl) or gnu lesser general public license (lgpl). customers may obtain the source code of the software and reproduce, distribute, and modify it in accordance with the gpl or lgpl. any portion of the source code of this product that is licensed under the gpl or lgpl may be provided by yamaha (for a period of five years from the final shipment date). yamaha shall not be liable for any damages arising from changes, additions, deletions, or other actions to the software of this product made by a third party other than yamaha (or a party authorized by yamaha). reuse of source codes provided by yamaha is not guaranteed. yamaha shall not be liable for the source codes. software other than those licensed under the gpl/lgpl this product uses open source software in accordance with the license conditions provided by the copyright holders. yamaha shall not be liable for the source codes.</div><div class="display_word">1. List of Open Source Software The open source software used in this product and their licenses are shown in the table below. Open source software and licenses Open source software License busybox GPLv2 bzip2 BSD-style civetweb MIT csvjson.js MIT D3 3-clause BSD Dynatree MIT/GPLv2 e2fsprogs GPLv2 ExplorerCanvas Apache 2.0 expat MIT FreeRADIUS GPLv2 glib LGPLv2 iptables GPLv2 ISC DHCP ISC jqCanvas MIT jqPlot MIT/GPLv2 jQuery MIT jQuery blockUI plugin MIT/GPL jQuery Cookie Plugin MIT jQuery DateTimePicker plugin MIT jQuery File Upload Plugin MIT jQuery Iframe Transport Plugin MIT jQuery Lined TextArea plugin MIT jQuery Migrate MIT jQuery UI MIT jQuery UI Touch Punch MIT/GPLv2 jQuery UI Widget MIT jQuery UI Ympicker MIT/GPLv2 jQuery XDomainRequest Transport Plugin MIT libcurl MIT/X derivate libevent 3-clause BSD libffi MIT libintl LGPLv2 linux GPLv2 Linux-PAM Linux-PAM lzo GPLv2 mtd-utils GPLv2 net-snmp net-snmp ntp ntp openssh OpenSSH openssl OpenSSL PowerTip MIT PTPd 2-clause BSD rsync GPLv3 shellinabox GPLv2 TableDnD plug-in for JQuery MIT The HTML5 Shiv MIT/GPLv2 tokyocabinet LGPLv2 Unbound 3-clause BSD, ISC, MIT UnZip Info-ZIP zip Info-ZIP zlib zlib About GPL/LGPL licensed software This product includes software licensed under the GNU General Public License (GPL) or GNU Lesser General Public License (LGPL). Customers may obtain the source code of the software and reproduce, distribute, and modify it in accordance with the GPL or LGPL. Any portion of the source code of this product that is licensed under the GPL or LGPL may be provided by Yamaha (for a period of five years from the final shipment date). Yamaha shall not be liable for any damages arising from changes, additions, deletions, or other actions to the software of this product made by a third party other than Yamaha (or a party authorized by Yamaha). Reuse of source codes provided by Yamaha is not guaranteed. Yamaha shall not be liable for the source codes. Software other than those licensed under the GPL/LGPL This product uses open source software in accordance with the license conditions provided by the copyright holders. Yamaha shall not be liable for the source codes.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#ライセンス条文一覧">2. List of License Terms</div><div class="search_word">2. list of license terms</div><div class="display_word">2. List of License Terms</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#gplv2">2.1. GPLv2</div><div class="search_word">2.1. gplv2 gnu general public license                       version 2, june 1991 copyright (c) 1989, 1991 free software foundation, inc., 51 franklin street, fifth floor, boston, ma 02110-1301 usa everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.                            preamble  the licenses for most software are designed to take away yourfreedom to share and change it.  by contrast, the gnu general publiclicense is intended to guarantee your freedom to share and change freesoftware--to make sure the software is free for all its users.  thisgeneral public license applies to most of the free softwarefoundation's software and to any other program whose authors commit tousing it.  (some other free software foundation software is covered bythe gnu lesser general public license instead.)  you can apply it toyour programs, too.  when we speak of free software, we are referring to freedom, notprice.  our general public licenses are designed to make sure that youhave the freedom to distribute copies of free software (and charge forthis service if you wish), that you receive source code or can get itif you want it, that you can change the software or use pieces of itin new free programs; and that you know you can do these things.  to protect your rights, we need to make restrictions that forbidanyone to deny you these rights or to ask you to surrender the rights.these restrictions translate to certain responsibilities for you if youdistribute copies of the software, or if you modify it.  for example, if you distribute copies of such a program, whethergratis or for a fee, you must give the recipients all the rights thatyou have.  you must make sure that they, too, receive or can get thesource code.  and you must show them these terms so they know theirrights.  we protect your rights with two steps: (1) copyright the software, and(2) offer you this license which gives you legal permission to copy,distribute and/or modify the software.  also, for each author's protection and ours, we want to make certainthat everyone understands that there is no warranty for this freesoftware.  if the software is modified by someone else and passed on, wewant its recipients to know that what they have is not the original, sothat any problems introduced by others will not reflect on the originalauthors' reputations.  finally, any free program is threatened constantly by softwarepatents.  we wish to avoid the danger that redistributors of a freeprogram will individually obtain patent licenses, in effect making theprogram proprietary.  to prevent this, we have made it clear that anypatent must be licensed for everyone's free use or not licensed at all.  the precise terms and conditions for copying, distribution andmodification follow.                    gnu general public license   terms and conditions for copying, distribution and modification  0. this license applies to any program or other work which containsa notice placed by the copyright holder saying it may be distributedunder the terms of this general public license.  the "program", below,refers to any such program or work, and a "work based on the program"means either the program or any derivative work under copyright law:that is to say, a work containing the program or a portion of it,either verbatim or with modifications and/or translated into anotherlanguage.  (hereinafter, translation is included without limitation inthe term "modification".)  each licensee is addressed as "you".activities other than copying, distribution and modification are notcovered by this license; they are outside its scope.  the act ofrunning the program is not restricted, and the output from the programis covered only if its contents constitute a work based on theprogram (independent of having been made by running the program).whether that is true depends on what the program does.  1. you may copy and distribute verbatim copies of the program'ssource code as you receive it, in any medium, provided that youconspicuously and appropriately publish on each copy an appropriatecopyright notice and disclaimer of warranty; keep intact all thenotices that refer to this license and to the absence of any warranty;and give any other recipients of the program a copy of this licensealong with the program.you may charge a fee for the physical act of transferring a copy, andyou may at your option offer warranty protection in exchange for a fee.  2. you may modify your copy or copies of the program or any portionof it, thus forming a work based on the program, and copy anddistribute such modifications or work under the terms of section 1above, provided that you also meet all of these conditions:    a) you must cause the modified files to carry prominent notices    stating that you changed the files and the date of any change.    b) you must cause any work that you distribute or publish, that in    whole or in part contains or is derived from the program or any    part thereof, to be licensed as a whole at no charge to all third    parties under the terms of this license.    c) if the modified program normally reads commands interactively    when run, you must cause it, when started running for such    interactive use in the most ordinary way, to print or display an    announcement including an appropriate copyright notice and a    notice that there is no warranty (or else, saying that you provide    a warranty) and that users may redistribute the program under    these conditions, and telling the user how to view a copy of this    license.  (exception: if the program itself is interactive but    does not normally print such an announcement, your work based on    the program is not required to print an announcement.)these requirements apply to the modified work as a whole.  ifidentifiable sections of that work are not derived from the program,and can be reasonably considered independent and separate works inthemselves, then this license, and its terms, do not apply to thosesections when you distribute them as separate works.  but when youdistribute the same sections as part of a whole which is a work basedon the program, the distribution of the whole must be on the terms ofthis license, whose permissions for other licensees extend to theentire whole, and thus to each and every part regardless of who wrote it.thus, it is not the intent of this section to claim rights or contestyour rights to work written entirely by you; rather, the intent is toexercise the right to control the distribution of derivative orcollective works based on the program.in addition, mere aggregation of another work not based on the programwith the program (or with a work based on the program) on a volume ofa storage or distribution medium does not bring the other work underthe scope of this license.  3. you may copy and distribute the program (or a work based on it,under section 2) in object code or executable form under the terms ofsections 1 and 2 above provided that you also do one of the following:    a) accompany it with the complete corresponding machine-readable    source code, which must be distributed under the terms of sections    1 and 2 above on a medium customarily used for software interchange; or,    b) accompany it with a written offer, valid for at least three    years, to give any third party, for a charge no more than your    cost of physically performing source distribution, a complete    machine-readable copy of the corresponding source code, to be    distributed under the terms of sections 1 and 2 above on a medium    customarily used for software interchange; or,    c) accompany it with the information you received as to the offer    to distribute corresponding source code.  (this alternative is    allowed only for noncommercial distribution and only if you    received the program in object code or executable form with such    an offer, in accord with subsection b above.)the source code for a work means the preferred form of the work formaking modifications to it.  for an executable work, complete sourcecode means all the source code for all modules it contains, plus anyassociated interface definition files, plus the scripts used tocontrol compilation and installation of the executable.  however, as aspecial exception, the source code distributed need not includeanything that is normally distributed (in either source or binaryform) with the major components (compiler, kernel, and so on) of theoperating system on which the executable runs, unless that componentitself accompanies the executable.if distribution of executable or object code is made by offeringaccess to copy from a designated place, then offering equivalentaccess to copy the source code from the same place counts asdistribution of the source code, even though third parties are notcompelled to copy the source along with the object code.  4. you may not copy, modify, sublicense, or distribute the programexcept as expressly provided under this license.  any attemptotherwise to copy, modify, sublicense or distribute the program isvoid, and will automatically terminate your rights under this license.however, parties who have received copies, or rights, from you underthis license will not have their licenses terminated so long as suchparties remain in full compliance.  5. you are not required to accept this license, since you have notsigned it.  however, nothing else grants you permission to modify ordistribute the program or its derivative works.  these actions areprohibited by law if you do not accept this license.  therefore, bymodifying or distributing the program (or any work based on theprogram), you indicate your acceptance of this license to do so, andall its terms and conditions for copying, distributing or modifyingthe program or works based on it.  6. each time you redistribute the program (or any work based on theprogram), the recipient automatically receives a license from theoriginal licensor to copy, distribute or modify the program subject tothese terms and conditions.  you may not impose any furtherrestrictions on the recipients' exercise of the rights granted herein.you are not responsible for enforcing compliance by third parties tothis license.  7. if, as a consequence of a court judgment or allegation of patentinfringement or for any other reason (not limited to patent issues),conditions are imposed on you (whether by court order, agreement orotherwise) that contradict the conditions of this license, they do notexcuse you from the conditions of this license.  if you cannotdistribute so as to satisfy simultaneously your obligations under thislicense and any other pertinent obligations, then as a consequence youmay not distribute the program at all.  for example, if a patentlicense would not permit royalty-free redistribution of the program byall those who receive copies directly or indirectly through you, thenthe only way you could satisfy both it and this license would be torefrain entirely from distribution of the program.if any portion of this section is held invalid or unenforceable underany particular circumstance, the balance of the section is intended toapply and the section as a whole is intended to apply in othercircumstances.it is not the purpose of this section to induce you to infringe anypatents or other property right claims or to contest validity of anysuch claims; this section has the sole purpose of protecting theintegrity of the free software distribution system, which isimplemented by public license practices.  many people have madegenerous contributions to the wide range of software distributedthrough that system in reliance on consistent application of thatsystem; it is up to the author/donor to decide if he or she is willingto distribute software through any other system and a licensee cannotimpose that choice.this section is intended to make thoroughly clear what is believed tobe a consequence of the rest of this license.  8. if the distribution and/or use of the program is restricted incertain countries either by patents or by copyrighted interfaces, theoriginal copyright holder who places the program under this licensemay add an explicit geographical distribution limitation excludingthose countries, so that distribution is permitted only in or amongcountries not thus excluded.  in such case, this license incorporatesthe limitation as if written in the body of this license.  9. the free software foundation may publish revised and/or new versionsof the general public license from time to time.  such new versions willbe similar in spirit to the present version, but may differ in detail toaddress new problems or concerns.each version is given a distinguishing version number.  if the programspecifies a version number of this license which applies to it and "anylater version", you have the option of following the terms and conditionseither of that version or of any later version published by the freesoftware foundation.  if the program does not specify a version number ofthis license, you may choose any version ever published by the free softwarefoundation.  10. if you wish to incorporate parts of the program into other freeprograms whose distribution conditions are different, write to the authorto ask for permission.  for software which is copyrighted by the freesoftware foundation, write to the free software foundation; we sometimesmake exceptions for this.  our decision will be guided by the two goalsof preserving the free status of all derivatives of our free software andof promoting the sharing and reuse of software generally.                            no warranty  11. because the program is licensed free of charge, there is no warrantyfor the program, to the extent permitted by applicable law.  except whenotherwise stated in writing the copyright holders and/or other partiesprovide the program "as is" without warranty of any kind, either expressedor implied, including, but not limited to, the implied warranties ofmerchantability and fitness for a particular purpose.  the entire risk asto the quality and performance of the program is with you.  should theprogram prove defective, you assume the cost of all necessary servicing,repair or correction.  12. in no event unless required by applicable law or agreed to in writingwill any copyright holder, or any other party who may modify and/orredistribute the program as permitted above, be liable to you for damages,including any general, special, incidental or consequential damages arisingout of the use or inability to use the program (including but not limitedto loss of data or data being rendered inaccurate or losses sustained byyou or third parties or a failure of the program to operate with any otherprograms), even if such holder or other party has been advised of thepossibility of such damages.                     end of terms and conditions            how to apply these terms to your new programs  if you develop a new program, and you want it to be of the greatestpossible use to the public, the best way to achieve this is to make itfree software which everyone can redistribute and change under these terms.  to do so, attach the following notices to the program.  it is safestto attach them to the start of each source file to most effectivelyconvey the exclusion of warranty; and each file should have at leastthe "copyright" line and a pointer to where the full notice is found.    <one line to give the program's name and a brief idea of what it does.>    copyright (c) <year>  <name of author>    this program is free software; you can redistribute it and/or modify    it under the terms of the gnu general public license as published by    the free software foundation; either version 2 of the license, or    (at your option) any later version.    this program is distributed in the hope that it will be useful,    but without any warranty; without even the implied warranty of    merchantability or fitness for a particular purpose.  see the    gnu general public license for more details.    you should have received a copy of the gnu general public license along    with this program; if not, write to the free software foundation, inc.,    51 franklin street, fifth floor, boston, ma 02110-1301 usa.also add information on how to contact you by electronic and paper mail.if the program is interactive, make it output a short notice like thiswhen it starts in an interactive mode:    gnomovision version 69, copyright (c) year name of author    gnomovision comes with absolutely no warranty; for details type `show w'.    this is free software, and you are welcome to redistribute it    under certain conditions; type `show c' for details.the hypothetical commands `show w' and `show c' should show the appropriateparts of the general public license.  of course, the commands you use maybe called something other than `show w' and `show c'; they could even bemouse-clicks or menu items--whatever suits your program.you should also get your employer (if you work as a programmer) or yourschool, if any, to sign a "copyright disclaimer" for the program, ifnecessary.  here is a sample; alter the names:  yoyodyne, inc., hereby disclaims all copyright interest in the program  `gnomovision' (which makes passes at compilers) written by james hacker.  <signature of ty coon>, 1 april 1989  ty coon, president of vicethis general public license does not permit incorporating your program intoproprietary programs.  if your program is a subroutine library, you mayconsider it more useful to permit linking proprietary applications with thelibrary.  if this is what you want to do, use the gnu lesser generalpublic license instead of this license.</div><div class="display_word">2.1. GPLv2 GNU GENERAL PUBLIC LICENSE                       Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.                            Preamble  The licenses for most software are designed to take away yourfreedom to share and change it.  By contrast, the GNU General PublicLicense is intended to guarantee your freedom to share and change freesoftware--to make sure the software is free for all its users.  ThisGeneral Public License applies to most of the Free SoftwareFoundation's software and to any other program whose authors commit tousing it.  (Some other Free Software Foundation software is covered bythe GNU Lesser General Public License instead.)  You can apply it toyour programs, too.  When we speak of free software, we are referring to freedom, notprice.  Our General Public Licenses are designed to make sure that youhave the freedom to distribute copies of free software (and charge forthis service if you wish), that you receive source code or can get itif you want it, that you can change the software or use pieces of itin new free programs; and that you know you can do these things.  To protect your rights, we need to make restrictions that forbidanyone to deny you these rights or to ask you to surrender the rights.These restrictions translate to certain responsibilities for you if youdistribute copies of the software, or if you modify it.  For example, if you distribute copies of such a program, whethergratis or for a fee, you must give the recipients all the rights thatyou have.  You must make sure that they, too, receive or can get thesource code.  And you must show them these terms so they know theirrights.  We protect your rights with two steps: (1) copyright the software, and(2) offer you this license which gives you legal permission to copy,distribute and/or modify the software.  Also, for each author's protection and ours, we want to make certainthat everyone understands that there is no warranty for this freesoftware.  If the software is modified by someone else and passed on, wewant its recipients to know that what they have is not the original, sothat any problems introduced by others will not reflect on the originalauthors' reputations.  Finally, any free program is threatened constantly by softwarepatents.  We wish to avoid the danger that redistributors of a freeprogram will individually obtain patent licenses, in effect making theprogram proprietary.  To prevent this, we have made it clear that anypatent must be licensed for everyone's free use or not licensed at all.  The precise terms and conditions for copying, distribution andmodification follow.                    GNU GENERAL PUBLIC LICENSE   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION  0. This License applies to any program or other work which containsa notice placed by the copyright holder saying it may be distributedunder the terms of this General Public License.  The "Program", below,refers to any such program or work, and a "work based on the Program"means either the Program or any derivative work under copyright law:that is to say, a work containing the Program or a portion of it,either verbatim or with modifications and/or translated into anotherlanguage.  (Hereinafter, translation is included without limitation inthe term "modification".)  Each licensee is addressed as "you".Activities other than copying, distribution and modification are notcovered by this License; they are outside its scope.  The act ofrunning the Program is not restricted, and the output from the Programis covered only if its contents constitute a work based on theProgram (independent of having been made by running the Program).Whether that is true depends on what the Program does.  1. You may copy and distribute verbatim copies of the Program'ssource code as you receive it, in any medium, provided that youconspicuously and appropriately publish on each copy an appropriatecopyright notice and disclaimer of warranty; keep intact all thenotices that refer to this License and to the absence of any warranty;and give any other recipients of the Program a copy of this Licensealong with the Program.You may charge a fee for the physical act of transferring a copy, andyou may at your option offer warranty protection in exchange for a fee.  2. You may modify your copy or copies of the Program or any portionof it, thus forming a work based on the Program, and copy anddistribute such modifications or work under the terms of Section 1above, provided that you also meet all of these conditions:    a) You must cause the modified files to carry prominent notices    stating that you changed the files and the date of any change.    b) You must cause any work that you distribute or publish, that in    whole or in part contains or is derived from the Program or any    part thereof, to be licensed as a whole at no charge to all third    parties under the terms of this License.    c) If the modified program normally reads commands interactively    when run, you must cause it, when started running for such    interactive use in the most ordinary way, to print or display an    announcement including an appropriate copyright notice and a    notice that there is no warranty (or else, saying that you provide    a warranty) and that users may redistribute the program under    these conditions, and telling the user how to view a copy of this    License.  (Exception: if the Program itself is interactive but    does not normally print such an announcement, your work based on    the Program is not required to print an announcement.)These requirements apply to the modified work as a whole.  Ifidentifiable sections of that work are not derived from the Program,and can be reasonably considered independent and separate works inthemselves, then this License, and its terms, do not apply to thosesections when you distribute them as separate works.  But when youdistribute the same sections as part of a whole which is a work basedon the Program, the distribution of the whole must be on the terms ofthis License, whose permissions for other licensees extend to theentire whole, and thus to each and every part regardless of who wrote it.Thus, it is not the intent of this section to claim rights or contestyour rights to work written entirely by you; rather, the intent is toexercise the right to control the distribution of derivative orcollective works based on the Program.In addition, mere aggregation of another work not based on the Programwith the Program (or with a work based on the Program) on a volume ofa storage or distribution medium does not bring the other work underthe scope of this License.  3. You may copy and distribute the Program (or a work based on it,under Section 2) in object code or executable form under the terms ofSections 1 and 2 above provided that you also do one of the following:    a) Accompany it with the complete corresponding machine-readable    source code, which must be distributed under the terms of Sections    1 and 2 above on a medium customarily used for software interchange; or,    b) Accompany it with a written offer, valid for at least three    years, to give any third party, for a charge no more than your    cost of physically performing source distribution, a complete    machine-readable copy of the corresponding source code, to be    distributed under the terms of Sections 1 and 2 above on a medium    customarily used for software interchange; or,    c) Accompany it with the information you received as to the offer    to distribute corresponding source code.  (This alternative is    allowed only for noncommercial distribution and only if you    received the program in object code or executable form with such    an offer, in accord with Subsection b above.)The source code for a work means the preferred form of the work formaking modifications to it.  For an executable work, complete sourcecode means all the source code for all modules it contains, plus anyassociated interface definition files, plus the scripts used tocontrol compilation and installation of the executable.  However, as aspecial exception, the source code distributed need not includeanything that is normally distributed (in either source or binaryform) with the major components (compiler, kernel, and so on) of theoperating system on which the executable runs, unless that componentitself accompanies the executable.If distribution of executable or object code is made by offeringaccess to copy from a designated place, then offering equivalentaccess to copy the source code from the same place counts asdistribution of the source code, even though third parties are notcompelled to copy the source along with the object code.  4. You may not copy, modify, sublicense, or distribute the Programexcept as expressly provided under this License.  Any attemptotherwise to copy, modify, sublicense or distribute the Program isvoid, and will automatically terminate your rights under this License.However, parties who have received copies, or rights, from you underthis License will not have their licenses terminated so long as suchparties remain in full compliance.  5. You are not required to accept this License, since you have notsigned it.  However, nothing else grants you permission to modify ordistribute the Program or its derivative works.  These actions areprohibited by law if you do not accept this License.  Therefore, bymodifying or distributing the Program (or any work based on theProgram), you indicate your acceptance of this License to do so, andall its terms and conditions for copying, distributing or modifyingthe Program or works based on it.  6. Each time you redistribute the Program (or any work based on theProgram), the recipient automatically receives a license from theoriginal licensor to copy, distribute or modify the Program subject tothese terms and conditions.  You may not impose any furtherrestrictions on the recipients' exercise of the rights granted herein.You are not responsible for enforcing compliance by third parties tothis License.  7. If, as a consequence of a court judgment or allegation of patentinfringement or for any other reason (not limited to patent issues),conditions are imposed on you (whether by court order, agreement orotherwise) that contradict the conditions of this License, they do notexcuse you from the conditions of this License.  If you cannotdistribute so as to satisfy simultaneously your obligations under thisLicense and any other pertinent obligations, then as a consequence youmay not distribute the Program at all.  For example, if a patentlicense would not permit royalty-free redistribution of the Program byall those who receive copies directly or indirectly through you, thenthe only way you could satisfy both it and this License would be torefrain entirely from distribution of the Program.If any portion of this section is held invalid or unenforceable underany particular circumstance, the balance of the section is intended toapply and the section as a whole is intended to apply in othercircumstances.It is not the purpose of this section to induce you to infringe anypatents or other property right claims or to contest validity of anysuch claims; this section has the sole purpose of protecting theintegrity of the free software distribution system, which isimplemented by public license practices.  Many people have madegenerous contributions to the wide range of software distributedthrough that system in reliance on consistent application of thatsystem; it is up to the author/donor to decide if he or she is willingto distribute software through any other system and a licensee cannotimpose that choice.This section is intended to make thoroughly clear what is believed tobe a consequence of the rest of this License.  8. If the distribution and/or use of the Program is restricted incertain countries either by patents or by copyrighted interfaces, theoriginal copyright holder who places the Program under this Licensemay add an explicit geographical distribution limitation excludingthose countries, so that distribution is permitted only in or amongcountries not thus excluded.  In such case, this License incorporatesthe limitation as if written in the body of this License.  9. The Free Software Foundation may publish revised and/or new versionsof the General Public License from time to time.  Such new versions willbe similar in spirit to the present version, but may differ in detail toaddress new problems or concerns.Each version is given a distinguishing version number.  If the Programspecifies a version number of this License which applies to it and "anylater version", you have the option of following the terms and conditionseither of that version or of any later version published by the FreeSoftware Foundation.  If the Program does not specify a version number ofthis License, you may choose any version ever published by the Free SoftwareFoundation.  10. If you wish to incorporate parts of the Program into other freeprograms whose distribution conditions are different, write to the authorto ask for permission.  For software which is copyrighted by the FreeSoftware Foundation, write to the Free Software Foundation; we sometimesmake exceptions for this.  Our decision will be guided by the two goalsof preserving the free status of all derivatives of our free software andof promoting the sharing and reuse of software generally.                            NO WARRANTY  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTYFOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHENOTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIESPROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSEDOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK ASTO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THEPROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,REPAIR OR CORRECTION.  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITINGWILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/ORREDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISINGOUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITEDTO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BYYOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHERPROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THEPOSSIBILITY OF SUCH DAMAGES.                     END OF TERMS AND CONDITIONS            How to Apply These Terms to Your New Programs  If you develop a new program, and you want it to be of the greatestpossible use to the public, the best way to achieve this is to make itfree software which everyone can redistribute and change under these terms.  To do so, attach the following notices to the program.  It is safestto attach them to the start of each source file to most effectivelyconvey the exclusion of warranty; and each file should have at leastthe "copyright" line and a pointer to where the full notice is found.    <one line to give the program's name and a brief idea of what it does.>    Copyright (C) <year>  <name of author>    This program is free software; you can redistribute it and/or modify    it under the terms of the GNU General Public License as published by    the Free Software Foundation; either version 2 of the License, or    (at your option) any later version.    This program is distributed in the hope that it will be useful,    but WITHOUT ANY WARRANTY; without even the implied warranty of    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the    GNU General Public License for more details.    You should have received a copy of the GNU General Public License along    with this program; if not, write to the Free Software Foundation, Inc.,    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.Also add information on how to contact you by electronic and paper mail.If the program is interactive, make it output a short notice like thiswhen it starts in an interactive mode:    Gnomovision version 69, Copyright (C) year name of author    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.    This is free software, and you are welcome to redistribute it    under certain conditions; type `show c' for details.The hypothetical commands `show w' and `show c' should show the appropriateparts of the General Public License.  Of course, the commands you use maybe called something other than `show w' and `show c'; they could even bemouse-clicks or menu items--whatever suits your program.You should also get your employer (if you work as a programmer) or yourschool, if any, to sign a "copyright disclaimer" for the program, ifnecessary.  Here is a sample; alter the names:  Yoyodyne, Inc., hereby disclaims all copyright interest in the program  `Gnomovision' (which makes passes at compilers) written by James Hacker.  <signature of Ty Coon>, 1 April 1989  Ty Coon, President of ViceThis General Public License does not permit incorporating your program intoproprietary programs.  If your program is a subroutine library, you mayconsider it more useful to permit linking proprietary applications with thelibrary.  If this is what you want to do, use the GNU Lesser GeneralPublic License instead of this License.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#gplv3">2.2. GPLv3</div><div class="search_word">2.2. gplv3 gnu general public license                       version 3, 29 june 2007 copyright (c) 2007 free software foundation, inc. < http://fsf.org/> everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.                            preamble  the gnu general public license is a free, copyleft license forsoftware and other kinds of works.  the licenses for most software and other practical works are designedto take away your freedom to share and change the works.  by contrast,the gnu general public license is intended to guarantee your freedom toshare and change all versions of a program--to make sure it remains freesoftware for all its users.  we, the free software foundation, use thegnu general public license for most of our software; it applies also toany other work released this way by its authors.  you can apply it toyour programs, too.  when we speak of free software, we are referring to freedom, notprice.  our general public licenses are designed to make sure that youhave the freedom to distribute copies of free software (and charge forthem if you wish), that you receive source code or can get it if youwant it, that you can change the software or use pieces of it in newfree programs, and that you know you can do these things.  to protect your rights, we need to prevent others from denying youthese rights or asking you to surrender the rights.  therefore, you havecertain responsibilities if you distribute copies of the software, or ifyou modify it: responsibilities to respect the freedom of others.  for example, if you distribute copies of such a program, whethergratis or for a fee, you must pass on to the recipients the samefreedoms that you received.  you must make sure that they, too, receiveor can get the source code.  and you must show them these terms so theyknow their rights.  developers that use the gnu gpl protect your rights with two steps:(1) assert copyright on the software, and (2) offer you this licensegiving you legal permission to copy, distribute and/or modify it.  for the developers' and authors' protection, the gpl clearly explainsthat there is no warranty for this free software.  for both users' andauthors' sake, the gpl requires that modified versions be marked aschanged, so that their problems will not be attributed erroneously toauthors of previous versions.  some devices are designed to deny users access to install or runmodified versions of the software inside them, although the manufacturercan do so.  this is fundamentally incompatible with the aim ofprotecting users' freedom to change the software.  the systematicpattern of such abuse occurs in the area of products for individuals touse, which is precisely where it is most unacceptable.  therefore, wehave designed this version of the gpl to prohibit the practice for thoseproducts.  if such problems arise substantially in other domains, westand ready to extend this provision to those domains in future versionsof the gpl, as needed to protect the freedom of users.  finally, every program is threatened constantly by software patents.states should not allow patents to restrict development and use ofsoftware on general-purpose computers, but in those that do, we wish toavoid the special danger that patents applied to a free program couldmake it effectively proprietary.  to prevent this, the gpl assures thatpatents cannot be used to render the program non-free.  the precise terms and conditions for copying, distribution andmodification follow.                       terms and conditions  0. definitions.  "this license" refers to version 3 of the gnu general public license.  "copyright" also means copyright-like laws that apply to other kinds ofworks, such as semiconductor masks.  "the program" refers to any copyrightable work licensed under thislicense.  each licensee is addressed as "you".  "licensees" and"recipients" may be individuals or organizations.  to "modify" a work means to copy from or adapt all or part of the workin a fashion requiring copyright permission, other than the making of anexact copy.  the resulting work is called a "modified version" of theearlier work or a work "based on" the earlier work.  a "covered work" means either the unmodified program or a work basedon the program.  to "propagate" a work means to do anything with it that, withoutpermission, would make you directly or secondarily liable forinfringement under applicable copyright law, except executing it on acomputer or modifying a private copy.  propagation includes copying,distribution (with or without modification), making available to thepublic, and in some countries other activities as well.  to "convey" a work means any kind of propagation that enables otherparties to make or receive copies.  mere interaction with a user througha computer network, with no transfer of a copy, is not conveying.  an interactive user interface displays "appropriate legal notices"to the extent that it includes a convenient and prominently visiblefeature that (1) displays an appropriate copyright notice, and (2)tells the user that there is no warranty for the work (except to theextent that warranties are provided), that licensees may convey thework under this license, and how to view a copy of this license.  ifthe interface presents a list of user commands or options, such as amenu, a prominent item in the list meets this criterion.  1. source code.  the "source code" for a work means the preferred form of the workfor making modifications to it.  "object code" means any non-sourceform of a work.  a "standard interface" means an interface that either is an officialstandard defined by a recognized standards body, or, in the case ofinterfaces specified for a particular programming language, one thatis widely used among developers working in that language.  the "system libraries" of an executable work include anything, otherthan the work as a whole, that (a) is included in the normal form ofpackaging a major component, but which is not part of that majorcomponent, and (b) serves only to enable use of the work with thatmajor component, or to implement a standard interface for which animplementation is available to the public in source code form.  a"major component", in this context, means a major essential component(kernel, window system, and so on) of the specific operating system(if any) on which the executable work runs, or a compiler used toproduce the work, or an object code interpreter used to run it.  the "corresponding source" for a work in object code form means allthe source code needed to generate, install, and (for an executablework) run the object code and to modify the work, including scripts tocontrol those activities.  however, it does not include the work'ssystem libraries, or general-purpose tools or generally available freeprograms which are used unmodified in performing those activities butwhich are not part of the work.  for example, corresponding sourceincludes interface definition files associated with source files forthe work, and the source code for shared libraries and dynamicallylinked subprograms that the work is specifically designed to require,such as by intimate data communication or control flow between thosesubprograms and other parts of the work.  the corresponding source need not include anything that userscan regenerate automatically from other parts of the correspondingsource.  the corresponding source for a work in source code form is thatsame work.  2. basic permissions.  all rights granted under this license are granted for the term ofcopyright on the program, and are irrevocable provided the statedconditions are met.  this license explicitly affirms your unlimitedpermission to run the unmodified program.  the output from running acovered work is covered by this license only if the output, given itscontent, constitutes a covered work.  this license acknowledges yourrights of fair use or other equivalent, as provided by copyright law.  you may make, run and propagate covered works that you do notconvey, without conditions so long as your license otherwise remainsin force.  you may convey covered works to others for the sole purposeof having them make modifications exclusively for you, or provide youwith facilities for running those works, provided that you comply withthe terms of this license in conveying all material for which you donot control copyright.  those thus making or running the covered worksfor you must do so exclusively on your behalf, under your directionand control, on terms that prohibit them from making any copies ofyour copyrighted material outside their relationship with you.  conveying under any other circumstances is permitted solely underthe conditions stated below.  sublicensing is not allowed; section 10makes it unnecessary.  3. protecting users' legal rights from anti-circumvention law.  no covered work shall be deemed part of an effective technologicalmeasure under any applicable law fulfilling obligations under article11 of the wipo copyright treaty adopted on 20 december 1996, orsimilar laws prohibiting or restricting circumvention of suchmeasures.  when you convey a covered work, you waive any legal power to forbidcircumvention of technological measures to the extent such circumventionis effected by exercising rights under this license with respect tothe covered work, and you disclaim any intention to limit operation ormodification of the work as a means of enforcing, against the work'susers, your or third parties' legal rights to forbid circumvention oftechnological measures.  4. conveying verbatim copies.  you may convey verbatim copies of the program's source code as youreceive it, in any medium, provided that you conspicuously andappropriately publish on each copy an appropriate copyright notice;keep intact all notices stating that this license and anynon-permissive terms added in accord with section 7 apply to the code;keep intact all notices of the absence of any warranty; and give allrecipients a copy of this license along with the program.  you may charge any price or no price for each copy that you convey,and you may offer support or warranty protection for a fee.  5. conveying modified source versions.  you may convey a work based on the program, or the modifications toproduce it from the program, in the form of source code under theterms of section 4, provided that you also meet all of these conditions:    a) the work must carry prominent notices stating that you modified    it, and giving a relevant date.    b) the work must carry prominent notices stating that it is    released under this license and any conditions added under section    7.  this requirement modifies the requirement in section 4 to    "keep intact all notices".    c) you must license the entire work, as a whole, under this    license to anyone who comes into possession of a copy.  this    license will therefore apply, along with any applicable section 7    additional terms, to the whole of the work, and all its parts,    regardless of how they are packaged.  this license gives no    permission to license the work in any other way, but it does not    invalidate such permission if you have separately received it.    d) if the work has interactive user interfaces, each must display    appropriate legal notices; however, if the program has interactive    interfaces that do not display appropriate legal notices, your    work need not make them do so.  a compilation of a covered work with other separate and independentworks, which are not by their nature extensions of the covered work,and which are not combined with it such as to form a larger program,in or on a volume of a storage or distribution medium, is called an"aggregate" if the compilation and its resulting copyright are notused to limit the access or legal rights of the compilation's usersbeyond what the individual works permit.  inclusion of a covered workin an aggregate does not cause this license to apply to the otherparts of the aggregate.  6. conveying non-source forms.  you may convey a covered work in object code form under the termsof sections 4 and 5, provided that you also convey themachine-readable corresponding source under the terms of this license,in one of these ways:    a) convey the object code in, or embodied in, a physical product    (including a physical distribution medium), accompanied by the    corresponding source fixed on a durable physical medium    customarily used for software interchange.    b) convey the object code in, or embodied in, a physical product    (including a physical distribution medium), accompanied by a    written offer, valid for at least three years and valid for as    long as you offer spare parts or customer support for that product    model, to give anyone who possesses the object code either (1) a    copy of the corresponding source for all the software in the    product that is covered by this license, on a durable physical    medium customarily used for software interchange, for a price no    more than your reasonable cost of physically performing this    conveying of source, or (2) access to copy the    corresponding source from a network server at no charge.    c) convey individual copies of the object code with a copy of the    written offer to provide the corresponding source.  this    alternative is allowed only occasionally and noncommercially, and    only if you received the object code with such an offer, in accord    with subsection 6b.    d) convey the object code by offering access from a designated    place (gratis or for a charge), and offer equivalent access to the    corresponding source in the same way through the same place at no    further charge.  you need not require recipients to copy the    corresponding source along with the object code.  if the place to    copy the object code is a network server, the corresponding source    may be on a different server (operated by you or a third party)    that supports equivalent copying facilities, provided you maintain    clear directions next to the object code saying where to find the    corresponding source.  regardless of what server hosts the    corresponding source, you remain obligated to ensure that it is    available for as long as needed to satisfy these requirements.    e) convey the object code using peer-to-peer transmission, provided    you inform other peers where the object code and corresponding    source of the work are being offered to the general public at no    charge under subsection 6d.  a separable portion of the object code, whose source code is excludedfrom the corresponding source as a system library, need not beincluded in conveying the object code work.  a "user product" is either (1) a "consumer product", which means anytangible personal property which is normally used for personal, family,or household purposes, or (2) anything designed or sold for incorporationinto a dwelling.  in determining whether a product is a consumer product,doubtful cases shall be resolved in favor of coverage.  for a particularproduct received by a particular user, "normally used" refers to atypical or common use of that class of product, regardless of the statusof the particular user or of the way in which the particular useractually uses, or expects or is expected to use, the product.  a productis a consumer product regardless of whether the product has substantialcommercial, industrial or non-consumer uses, unless such uses representthe only significant mode of use of the product.  "installation information" for a user product means any methods,procedures, authorization keys, or other information required to installand execute modified versions of a covered work in that user product froma modified version of its corresponding source.  the information mustsuffice to ensure that the continued functioning of the modified objectcode is in no case prevented or interfered with solely becausemodification has been made.  if you convey an object code work under this section in, or with, orspecifically for use in, a user product, and the conveying occurs aspart of a transaction in which the right of possession and use of theuser product is transferred to the recipient in perpetuity or for afixed term (regardless of how the transaction is characterized), thecorresponding source conveyed under this section must be accompaniedby the installation information.  but this requirement does not applyif neither you nor any third party retains the ability to installmodified object code on the user product (for example, the work hasbeen installed in rom).  the requirement to provide installation information does not include arequirement to continue to provide support service, warranty, or updatesfor a work that has been modified or installed by the recipient, or forthe user product in which it has been modified or installed.  access to anetwork may be denied when the modification itself materially andadversely affects the operation of the network or violates the rules andprotocols for communication across the network.  corresponding source conveyed, and installation information provided,in accord with this section must be in a format that is publiclydocumented (and with an implementation available to the public insource code form), and must require no special password or key forunpacking, reading or copying.  7. additional terms.  "additional permissions" are terms that supplement the terms of thislicense by making exceptions from one or more of its conditions.additional permissions that are applicable to the entire program shallbe treated as though they were included in this license, to the extentthat they are valid under applicable law.  if additional permissionsapply only to part of the program, that part may be used separatelyunder those permissions, but the entire program remains governed bythis license without regard to the additional permissions.  when you convey a copy of a covered work, you may at your optionremove any additional permissions from that copy, or from any part ofit.  (additional permissions may be written to require their ownremoval in certain cases when you modify the work.)  you may placeadditional permissions on material, added by you to a covered work,for which you have or can give appropriate copyright permission.  notwithstanding any other provision of this license, for material youadd to a covered work, you may (if authorized by the copyright holders ofthat material) supplement the terms of this license with terms:    a) disclaiming warranty or limiting liability differently from the    terms of sections 15 and 16 of this license; or    b) requiring preservation of specified reasonable legal notices or    author attributions in that material or in the appropriate legal    notices displayed by works containing it; or    c) prohibiting misrepresentation of the origin of that material, or    requiring that modified versions of such material be marked in    reasonable ways as different from the original version; or    d) limiting the use for publicity purposes of names of licensors or    authors of the material; or    e) declining to grant rights under trademark law for use of some    trade names, trademarks, or service marks; or    f) requiring indemnification of licensors and authors of that    material by anyone who conveys the material (or modified versions of    it) with contractual assumptions of liability to the recipient, for    any liability that these contractual assumptions directly impose on    those licensors and authors.  all other non-permissive additional terms are considered "furtherrestrictions" within the meaning of section 10.  if the program as youreceived it, or any part of it, contains a notice stating that it isgoverned by this license along with a term that is a furtherrestriction, you may remove that term.  if a license document containsa further restriction but permits relicensing or conveying under thislicense, you may add to a covered work material governed by the termsof that license document, provided that the further restriction doesnot survive such relicensing or conveying.  if you add terms to a covered work in accord with this section, youmust place, in the relevant source files, a statement of theadditional terms that apply to those files, or a notice indicatingwhere to find the applicable terms.  additional terms, permissive or non-permissive, may be stated in theform of a separately written license, or stated as exceptions;the above requirements apply either way.  8. termination.  you may not propagate or modify a covered work except as expresslyprovided under this license.  any attempt otherwise to propagate ormodify it is void, and will automatically terminate your rights underthis license (including any patent licenses granted under the thirdparagraph of section 11).  however, if you cease all violation of this license, then yourlicense from a particular copyright holder is reinstated (a)provisionally, unless and until the copyright holder explicitly andfinally terminates your license, and (b) permanently, if the copyrightholder fails to notify you of the violation by some reasonable meansprior to 60 days after the cessation.  moreover, your license from a particular copyright holder isreinstated permanently if the copyright holder notifies you of theviolation by some reasonable means, this is the first time you havereceived notice of violation of this license (for any work) from thatcopyright holder, and you cure the violation prior to 30 days afteryour receipt of the notice.  termination of your rights under this section does not terminate thelicenses of parties who have received copies or rights from you underthis license.  if your rights have been terminated and not permanentlyreinstated, you do not qualify to receive new licenses for the samematerial under section 10.  9. acceptance not required for having copies.  you are not required to accept this license in order to receive orrun a copy of the program.  ancillary propagation of a covered workoccurring solely as a consequence of using peer-to-peer transmissionto receive a copy likewise does not require acceptance.  however,nothing other than this license grants you permission to propagate ormodify any covered work.  these actions infringe copyright if you donot accept this license.  therefore, by modifying or propagating acovered work, you indicate your acceptance of this license to do so.  10. automatic licensing of downstream recipients.  each time you convey a covered work, the recipient automaticallyreceives a license from the original licensors, to run, modify andpropagate that work, subject to this license.  you are not responsiblefor enforcing compliance by third parties with this license.  an "entity transaction" is a transaction transferring control of anorganization, or substantially all assets of one, or subdividing anorganization, or merging organizations.  if propagation of a coveredwork results from an entity transaction, each party to thattransaction who receives a copy of the work also receives whateverlicenses to the work the party's predecessor in interest had or couldgive under the previous paragraph, plus a right to possession of thecorresponding source of the work from the predecessor in interest, ifthe predecessor has it or can get it with reasonable efforts.  you may not impose any further restrictions on the exercise of therights granted or affirmed under this license.  for example, you maynot impose a license fee, royalty, or other charge for exercise ofrights granted under this license, and you may not initiate litigation(including a cross-claim or counterclaim in a lawsuit) alleging thatany patent claim is infringed by making, using, selling, offering forsale, or importing the program or any portion of it.  11. patents.  a "contributor" is a copyright holder who authorizes use under thislicense of the program or a work on which the program is based.  thework thus licensed is called the contributor's "contributor version".  a contributor's "essential patent claims" are all patent claimsowned or controlled by the contributor, whether already acquired orhereafter acquired, that would be infringed by some manner, permittedby this license, of making, using, or selling its contributor version,but do not include claims that would be infringed only as aconsequence of further modification of the contributor version.  forpurposes of this definition, "control" includes the right to grantpatent sublicenses in a manner consistent with the requirements ofthis license.  each contributor grants you a non-exclusive, worldwide, royalty-freepatent license under the contributor's essential patent claims, tomake, use, sell, offer for sale, import and otherwise run, modify andpropagate the contents of its contributor version.  in the following three paragraphs, a "patent license" is any expressagreement or commitment, however denominated, not to enforce a patent(such as an express permission to practice a patent or covenant not tosue for patent infringement).  to "grant" such a patent license to aparty means to make such an agreement or commitment not to enforce apatent against the party.  if you convey a covered work, knowingly relying on a patent license,and the corresponding source of the work is not available for anyoneto copy, free of charge and under the terms of this license, through apublicly available network server or other readily accessible means,then you must either (1) cause the corresponding source to be soavailable, or (2) arrange to deprive yourself of the benefit of thepatent license for this particular work, or (3) arrange, in a mannerconsistent with the requirements of this license, to extend the patentlicense to downstream recipients.  "knowingly relying" means you haveactual knowledge that, but for the patent license, your conveying thecovered work in a country, or your recipient's use of the covered workin a country, would infringe one or more identifiable patents in thatcountry that you have reason to believe are valid.  if, pursuant to or in connection with a single transaction orarrangement, you convey, or propagate by procuring conveyance of, acovered work, and grant a patent license to some of the partiesreceiving the covered work authorizing them to use, propagate, modifyor convey a specific copy of the covered work, then the patent licenseyou grant is automatically extended to all recipients of the coveredwork and works based on it.  a patent license is "discriminatory" if it does not include withinthe scope of its coverage, prohibits the exercise of, or isconditioned on the non-exercise of one or more of the rights that arespecifically granted under this license.  you may not convey a coveredwork if you are a party to an arrangement with a third party that isin the business of distributing software, under which you make paymentto the third party based on the extent of your activity of conveyingthe work, and under which the third party grants, to any of theparties who would receive the covered work from you, a discriminatorypatent license (a) in connection with copies of the covered workconveyed by you (or copies made from those copies), or (b) primarilyfor and in connection with specific products or compilations thatcontain the covered work, unless you entered into that arrangement,or that patent license was granted, prior to 28 march 2007.  nothing in this license shall be construed as excluding or limitingany implied license or other defenses to infringement that mayotherwise be available to you under applicable patent law.  12. no surrender of others' freedom.  if conditions are imposed on you (whether by court order, agreement orotherwise) that contradict the conditions of this license, they do notexcuse you from the conditions of this license.  if you cannot convey acovered work so as to satisfy simultaneously your obligations under thislicense and any other pertinent obligations, then as a consequence you maynot convey it at all.  for example, if you agree to terms that obligate youto collect a royalty for further conveying from those to whom you conveythe program, the only way you could satisfy both those terms and thislicense would be to refrain entirely from conveying the program.  13. use with the gnu affero general public license.  notwithstanding any other provision of this license, you havepermission to link or combine any covered work with a work licensedunder version 3 of the gnu affero general public license into a singlecombined work, and to convey the resulting work.  the terms of thislicense will continue to apply to the part which is the covered work,but the special requirements of the gnu affero general public license,section 13, concerning interaction through a network will apply to thecombination as such.  14. revised versions of this license.  the free software foundation may publish revised and/or new versions ofthe gnu general public license from time to time.  such new versions willbe similar in spirit to the present version, but may differ in detail toaddress new problems or concerns.  each version is given a distinguishing version number.  if theprogram specifies that a certain numbered version of the gnu generalpublic license "or any later version" applies to it, you have theoption of following the terms and conditions either of that numberedversion or of any later version published by the free softwarefoundation.  if the program does not specify a version number of thegnu general public license, you may choose any version ever publishedby the free software foundation.  if the program specifies that a proxy can decide which futureversions of the gnu general public license can be used, that proxy'spublic statement of acceptance of a version permanently authorizes youto choose that version for the program.  later license versions may give you additional or differentpermissions.  however, no additional obligations are imposed on anyauthor or copyright holder as a result of your choosing to follow alater version.  15. disclaimer of warranty.  there is no warranty for the program, to the extent permitted byapplicable law.  except when otherwise stated in writing the copyrightholders and/or other parties provide the program "as is" without warrantyof any kind, either expressed or implied, including, but not limited to,the implied warranties of merchantability and fitness for a particularpurpose.  the entire risk as to the quality and performance of the programis with you.  should the program prove defective, you assume the cost ofall necessary servicing, repair or correction.  16. limitation of liability.  in no event unless required by applicable law or agreed to in writingwill any copyright holder, or any other party who modifies and/or conveysthe program as permitted above, be liable to you for damages, including anygeneral, special, incidental or consequential damages arising out of theuse or inability to use the program (including but not limited to loss ofdata or data being rendered inaccurate or losses sustained by you or thirdparties or a failure of the program to operate with any other programs),even if such holder or other party has been advised of the possibility ofsuch damages.  17. interpretation of sections 15 and 16.  if the disclaimer of warranty and limitation of liability providedabove cannot be given local legal effect according to their terms,reviewing courts shall apply local law that most closely approximatesan absolute waiver of all civil liability in connection with theprogram, unless a warranty or assumption of liability accompanies acopy of the program in return for a fee.                     end of terms and conditions            how to apply these terms to your new programs  if you develop a new program, and you want it to be of the greatestpossible use to the public, the best way to achieve this is to make itfree software which everyone can redistribute and change under these terms.  to do so, attach the following notices to the program.  it is safestto attach them to the start of each source file to most effectivelystate the exclusion of warranty; and each file should have at leastthe "copyright" line and a pointer to where the full notice is found.    <one line to give the program's name and a brief idea of what it does.>    copyright (c) <year>  <name of author>    this program is free software: you can redistribute it and/or modify    it under the terms of the gnu general public license as published by    the free software foundation, either version 3 of the license, or    (at your option) any later version.    this program is distributed in the hope that it will be useful,    but without any warranty; without even the implied warranty of    merchantability or fitness for a particular purpose.  see the    gnu general public license for more details.    you should have received a copy of the gnu general public license    along with this program.  if not, see < http://www.gnu.org/licenses/>.also add information on how to contact you by electronic and paper mail.  if the program does terminal interaction, make it output a shortnotice like this when it starts in an interactive mode:    <program>  copyright (c) <year>  <name of author>    this program comes with absolutely no warranty; for details type `show w'.    this is free software, and you are welcome to redistribute it    under certain conditions; type `show c' for details.the hypothetical commands `show w' and `show c' should show the appropriateparts of the general public license.  of course, your program's commandsmight be different; for a gui interface, you would use an "about box".  you should also get your employer (if you work as a programmer) or school,if any, to sign a "copyright disclaimer" for the program, if necessary.for more information on this, and how to apply and follow the gnu gpl, see< http://www.gnu.org/licenses/>.  the gnu general public license does not permit incorporating your programinto proprietary programs.  if your program is a subroutine library, youmay consider it more useful to permit linking proprietary applications withthe library.  if this is what you want to do, use the gnu lesser generalpublic license instead of this license.  but first, please read< http://www.gnu.org/philosophy/why-not-lgpl.html>.</div><div class="display_word">2.2. GPLv3 GNU GENERAL PUBLIC LICENSE                       Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. < http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.                            Preamble  The GNU General Public License is a free, copyleft license forsoftware and other kinds of works.  The licenses for most software and other practical works are designedto take away your freedom to share and change the works.  By contrast,the GNU General Public License is intended to guarantee your freedom toshare and change all versions of a program--to make sure it remains freesoftware for all its users.  We, the Free Software Foundation, use theGNU General Public License for most of our software; it applies also toany other work released this way by its authors.  You can apply it toyour programs, too.  When we speak of free software, we are referring to freedom, notprice.  Our General Public Licenses are designed to make sure that youhave the freedom to distribute copies of free software (and charge forthem if you wish), that you receive source code or can get it if youwant it, that you can change the software or use pieces of it in newfree programs, and that you know you can do these things.  To protect your rights, we need to prevent others from denying youthese rights or asking you to surrender the rights.  Therefore, you havecertain responsibilities if you distribute copies of the software, or ifyou modify it: responsibilities to respect the freedom of others.  For example, if you distribute copies of such a program, whethergratis or for a fee, you must pass on to the recipients the samefreedoms that you received.  You must make sure that they, too, receiveor can get the source code.  And you must show them these terms so theyknow their rights.  Developers that use the GNU GPL protect your rights with two steps:(1) assert copyright on the software, and (2) offer you this Licensegiving you legal permission to copy, distribute and/or modify it.  For the developers' and authors' protection, the GPL clearly explainsthat there is no warranty for this free software.  For both users' andauthors' sake, the GPL requires that modified versions be marked aschanged, so that their problems will not be attributed erroneously toauthors of previous versions.  Some devices are designed to deny users access to install or runmodified versions of the software inside them, although the manufacturercan do so.  This is fundamentally incompatible with the aim ofprotecting users' freedom to change the software.  The systematicpattern of such abuse occurs in the area of products for individuals touse, which is precisely where it is most unacceptable.  Therefore, wehave designed this version of the GPL to prohibit the practice for thoseproducts.  If such problems arise substantially in other domains, westand ready to extend this provision to those domains in future versionsof the GPL, as needed to protect the freedom of users.  Finally, every program is threatened constantly by software patents.States should not allow patents to restrict development and use ofsoftware on general-purpose computers, but in those that do, we wish toavoid the special danger that patents applied to a free program couldmake it effectively proprietary.  To prevent this, the GPL assures thatpatents cannot be used to render the program non-free.  The precise terms and conditions for copying, distribution andmodification follow.                       TERMS AND CONDITIONS  0. Definitions.  "This License" refers to version 3 of the GNU General Public License.  "Copyright" also means copyright-like laws that apply to other kinds ofworks, such as semiconductor masks.  "The Program" refers to any copyrightable work licensed under thisLicense.  Each licensee is addressed as "you".  "Licensees" and"recipients" may be individuals or organizations.  To "modify" a work means to copy from or adapt all or part of the workin a fashion requiring copyright permission, other than the making of anexact copy.  The resulting work is called a "modified version" of theearlier work or a work "based on" the earlier work.  A "covered work" means either the unmodified Program or a work basedon the Program.  To "propagate" a work means to do anything with it that, withoutpermission, would make you directly or secondarily liable forinfringement under applicable copyright law, except executing it on acomputer or modifying a private copy.  Propagation includes copying,distribution (with or without modification), making available to thepublic, and in some countries other activities as well.  To "convey" a work means any kind of propagation that enables otherparties to make or receive copies.  Mere interaction with a user througha computer network, with no transfer of a copy, is not conveying.  An interactive user interface displays "Appropriate Legal Notices"to the extent that it includes a convenient and prominently visiblefeature that (1) displays an appropriate copyright notice, and (2)tells the user that there is no warranty for the work (except to theextent that warranties are provided), that licensees may convey thework under this License, and how to view a copy of this License.  Ifthe interface presents a list of user commands or options, such as amenu, a prominent item in the list meets this criterion.  1. Source Code.  The "source code" for a work means the preferred form of the workfor making modifications to it.  "Object code" means any non-sourceform of a work.  A "Standard Interface" means an interface that either is an officialstandard defined by a recognized standards body, or, in the case ofinterfaces specified for a particular programming language, one thatis widely used among developers working in that language.  The "System Libraries" of an executable work include anything, otherthan the work as a whole, that (a) is included in the normal form ofpackaging a Major Component, but which is not part of that MajorComponent, and (b) serves only to enable use of the work with thatMajor Component, or to implement a Standard Interface for which animplementation is available to the public in source code form.  A"Major Component", in this context, means a major essential component(kernel, window system, and so on) of the specific operating system(if any) on which the executable work runs, or a compiler used toproduce the work, or an object code interpreter used to run it.  The "Corresponding Source" for a work in object code form means allthe source code needed to generate, install, and (for an executablework) run the object code and to modify the work, including scripts tocontrol those activities.  However, it does not include the work'sSystem Libraries, or general-purpose tools or generally available freeprograms which are used unmodified in performing those activities butwhich are not part of the work.  For example, Corresponding Sourceincludes interface definition files associated with source files forthe work, and the source code for shared libraries and dynamicallylinked subprograms that the work is specifically designed to require,such as by intimate data communication or control flow between thosesubprograms and other parts of the work.  The Corresponding Source need not include anything that userscan regenerate automatically from other parts of the CorrespondingSource.  The Corresponding Source for a work in source code form is thatsame work.  2. Basic Permissions.  All rights granted under this License are granted for the term ofcopyright on the Program, and are irrevocable provided the statedconditions are met.  This License explicitly affirms your unlimitedpermission to run the unmodified Program.  The output from running acovered work is covered by this License only if the output, given itscontent, constitutes a covered work.  This License acknowledges yourrights of fair use or other equivalent, as provided by copyright law.  You may make, run and propagate covered works that you do notconvey, without conditions so long as your license otherwise remainsin force.  You may convey covered works to others for the sole purposeof having them make modifications exclusively for you, or provide youwith facilities for running those works, provided that you comply withthe terms of this License in conveying all material for which you donot control copyright.  Those thus making or running the covered worksfor you must do so exclusively on your behalf, under your directionand control, on terms that prohibit them from making any copies ofyour copyrighted material outside their relationship with you.  Conveying under any other circumstances is permitted solely underthe conditions stated below.  Sublicensing is not allowed; section 10makes it unnecessary.  3. Protecting Users' Legal Rights From Anti-Circumvention Law.  No covered work shall be deemed part of an effective technologicalmeasure under any applicable law fulfilling obligations under article11 of the WIPO copyright treaty adopted on 20 December 1996, orsimilar laws prohibiting or restricting circumvention of suchmeasures.  When you convey a covered work, you waive any legal power to forbidcircumvention of technological measures to the extent such circumventionis effected by exercising rights under this License with respect tothe covered work, and you disclaim any intention to limit operation ormodification of the work as a means of enforcing, against the work'susers, your or third parties' legal rights to forbid circumvention oftechnological measures.  4. Conveying Verbatim Copies.  You may convey verbatim copies of the Program's source code as youreceive it, in any medium, provided that you conspicuously andappropriately publish on each copy an appropriate copyright notice;keep intact all notices stating that this License and anynon-permissive terms added in accord with section 7 apply to the code;keep intact all notices of the absence of any warranty; and give allrecipients a copy of this License along with the Program.  You may charge any price or no price for each copy that you convey,and you may offer support or warranty protection for a fee.  5. Conveying Modified Source Versions.  You may convey a work based on the Program, or the modifications toproduce it from the Program, in the form of source code under theterms of section 4, provided that you also meet all of these conditions:    a) The work must carry prominent notices stating that you modified    it, and giving a relevant date.    b) The work must carry prominent notices stating that it is    released under this License and any conditions added under section    7.  This requirement modifies the requirement in section 4 to    "keep intact all notices".    c) You must license the entire work, as a whole, under this    License to anyone who comes into possession of a copy.  This    License will therefore apply, along with any applicable section 7    additional terms, to the whole of the work, and all its parts,    regardless of how they are packaged.  This License gives no    permission to license the work in any other way, but it does not    invalidate such permission if you have separately received it.    d) If the work has interactive user interfaces, each must display    Appropriate Legal Notices; however, if the Program has interactive    interfaces that do not display Appropriate Legal Notices, your    work need not make them do so.  A compilation of a covered work with other separate and independentworks, which are not by their nature extensions of the covered work,and which are not combined with it such as to form a larger program,in or on a volume of a storage or distribution medium, is called an"aggregate" if the compilation and its resulting copyright are notused to limit the access or legal rights of the compilation's usersbeyond what the individual works permit.  Inclusion of a covered workin an aggregate does not cause this License to apply to the otherparts of the aggregate.  6. Conveying Non-Source Forms.  You may convey a covered work in object code form under the termsof sections 4 and 5, provided that you also convey themachine-readable Corresponding Source under the terms of this License,in one of these ways:    a) Convey the object code in, or embodied in, a physical product    (including a physical distribution medium), accompanied by the    Corresponding Source fixed on a durable physical medium    customarily used for software interchange.    b) Convey the object code in, or embodied in, a physical product    (including a physical distribution medium), accompanied by a    written offer, valid for at least three years and valid for as    long as you offer spare parts or customer support for that product    model, to give anyone who possesses the object code either (1) a    copy of the Corresponding Source for all the software in the    product that is covered by this License, on a durable physical    medium customarily used for software interchange, for a price no    more than your reasonable cost of physically performing this    conveying of source, or (2) access to copy the    Corresponding Source from a network server at no charge.    c) Convey individual copies of the object code with a copy of the    written offer to provide the Corresponding Source.  This    alternative is allowed only occasionally and noncommercially, and    only if you received the object code with such an offer, in accord    with subsection 6b.    d) Convey the object code by offering access from a designated    place (gratis or for a charge), and offer equivalent access to the    Corresponding Source in the same way through the same place at no    further charge.  You need not require recipients to copy the    Corresponding Source along with the object code.  If the place to    copy the object code is a network server, the Corresponding Source    may be on a different server (operated by you or a third party)    that supports equivalent copying facilities, provided you maintain    clear directions next to the object code saying where to find the    Corresponding Source.  Regardless of what server hosts the    Corresponding Source, you remain obligated to ensure that it is    available for as long as needed to satisfy these requirements.    e) Convey the object code using peer-to-peer transmission, provided    you inform other peers where the object code and Corresponding    Source of the work are being offered to the general public at no    charge under subsection 6d.  A separable portion of the object code, whose source code is excludedfrom the Corresponding Source as a System Library, need not beincluded in conveying the object code work.  A "User Product" is either (1) a "consumer product", which means anytangible personal property which is normally used for personal, family,or household purposes, or (2) anything designed or sold for incorporationinto a dwelling.  In determining whether a product is a consumer product,doubtful cases shall be resolved in favor of coverage.  For a particularproduct received by a particular user, "normally used" refers to atypical or common use of that class of product, regardless of the statusof the particular user or of the way in which the particular useractually uses, or expects or is expected to use, the product.  A productis a consumer product regardless of whether the product has substantialcommercial, industrial or non-consumer uses, unless such uses representthe only significant mode of use of the product.  "Installation Information" for a User Product means any methods,procedures, authorization keys, or other information required to installand execute modified versions of a covered work in that User Product froma modified version of its Corresponding Source.  The information mustsuffice to ensure that the continued functioning of the modified objectcode is in no case prevented or interfered with solely becausemodification has been made.  If you convey an object code work under this section in, or with, orspecifically for use in, a User Product, and the conveying occurs aspart of a transaction in which the right of possession and use of theUser Product is transferred to the recipient in perpetuity or for afixed term (regardless of how the transaction is characterized), theCorresponding Source conveyed under this section must be accompaniedby the Installation Information.  But this requirement does not applyif neither you nor any third party retains the ability to installmodified object code on the User Product (for example, the work hasbeen installed in ROM).  The requirement to provide Installation Information does not include arequirement to continue to provide support service, warranty, or updatesfor a work that has been modified or installed by the recipient, or forthe User Product in which it has been modified or installed.  Access to anetwork may be denied when the modification itself materially andadversely affects the operation of the network or violates the rules andprotocols for communication across the network.  Corresponding Source conveyed, and Installation Information provided,in accord with this section must be in a format that is publiclydocumented (and with an implementation available to the public insource code form), and must require no special password or key forunpacking, reading or copying.  7. Additional Terms.  "Additional permissions" are terms that supplement the terms of thisLicense by making exceptions from one or more of its conditions.Additional permissions that are applicable to the entire Program shallbe treated as though they were included in this License, to the extentthat they are valid under applicable law.  If additional permissionsapply only to part of the Program, that part may be used separatelyunder those permissions, but the entire Program remains governed bythis License without regard to the additional permissions.  When you convey a copy of a covered work, you may at your optionremove any additional permissions from that copy, or from any part ofit.  (Additional permissions may be written to require their ownremoval in certain cases when you modify the work.)  You may placeadditional permissions on material, added by you to a covered work,for which you have or can give appropriate copyright permission.  Notwithstanding any other provision of this License, for material youadd to a covered work, you may (if authorized by the copyright holders ofthat material) supplement the terms of this License with terms:    a) Disclaiming warranty or limiting liability differently from the    terms of sections 15 and 16 of this License; or    b) Requiring preservation of specified reasonable legal notices or    author attributions in that material or in the Appropriate Legal    Notices displayed by works containing it; or    c) Prohibiting misrepresentation of the origin of that material, or    requiring that modified versions of such material be marked in    reasonable ways as different from the original version; or    d) Limiting the use for publicity purposes of names of licensors or    authors of the material; or    e) Declining to grant rights under trademark law for use of some    trade names, trademarks, or service marks; or    f) Requiring indemnification of licensors and authors of that    material by anyone who conveys the material (or modified versions of    it) with contractual assumptions of liability to the recipient, for    any liability that these contractual assumptions directly impose on    those licensors and authors.  All other non-permissive additional terms are considered "furtherrestrictions" within the meaning of section 10.  If the Program as youreceived it, or any part of it, contains a notice stating that it isgoverned by this License along with a term that is a furtherrestriction, you may remove that term.  If a license document containsa further restriction but permits relicensing or conveying under thisLicense, you may add to a covered work material governed by the termsof that license document, provided that the further restriction doesnot survive such relicensing or conveying.  If you add terms to a covered work in accord with this section, youmust place, in the relevant source files, a statement of theadditional terms that apply to those files, or a notice indicatingwhere to find the applicable terms.  Additional terms, permissive or non-permissive, may be stated in theform of a separately written license, or stated as exceptions;the above requirements apply either way.  8. Termination.  You may not propagate or modify a covered work except as expresslyprovided under this License.  Any attempt otherwise to propagate ormodify it is void, and will automatically terminate your rights underthis License (including any patent licenses granted under the thirdparagraph of section 11).  However, if you cease all violation of this License, then yourlicense from a particular copyright holder is reinstated (a)provisionally, unless and until the copyright holder explicitly andfinally terminates your license, and (b) permanently, if the copyrightholder fails to notify you of the violation by some reasonable meansprior to 60 days after the cessation.  Moreover, your license from a particular copyright holder isreinstated permanently if the copyright holder notifies you of theviolation by some reasonable means, this is the first time you havereceived notice of violation of this License (for any work) from thatcopyright holder, and you cure the violation prior to 30 days afteryour receipt of the notice.  Termination of your rights under this section does not terminate thelicenses of parties who have received copies or rights from you underthis License.  If your rights have been terminated and not permanentlyreinstated, you do not qualify to receive new licenses for the samematerial under section 10.  9. Acceptance Not Required for Having Copies.  You are not required to accept this License in order to receive orrun a copy of the Program.  Ancillary propagation of a covered workoccurring solely as a consequence of using peer-to-peer transmissionto receive a copy likewise does not require acceptance.  However,nothing other than this License grants you permission to propagate ormodify any covered work.  These actions infringe copyright if you donot accept this License.  Therefore, by modifying or propagating acovered work, you indicate your acceptance of this License to do so.  10. Automatic Licensing of Downstream Recipients.  Each time you convey a covered work, the recipient automaticallyreceives a license from the original licensors, to run, modify andpropagate that work, subject to this License.  You are not responsiblefor enforcing compliance by third parties with this License.  An "entity transaction" is a transaction transferring control of anorganization, or substantially all assets of one, or subdividing anorganization, or merging organizations.  If propagation of a coveredwork results from an entity transaction, each party to thattransaction who receives a copy of the work also receives whateverlicenses to the work the party's predecessor in interest had or couldgive under the previous paragraph, plus a right to possession of theCorresponding Source of the work from the predecessor in interest, ifthe predecessor has it or can get it with reasonable efforts.  You may not impose any further restrictions on the exercise of therights granted or affirmed under this License.  For example, you maynot impose a license fee, royalty, or other charge for exercise ofrights granted under this License, and you may not initiate litigation(including a cross-claim or counterclaim in a lawsuit) alleging thatany patent claim is infringed by making, using, selling, offering forsale, or importing the Program or any portion of it.  11. Patents.  A "contributor" is a copyright holder who authorizes use under thisLicense of the Program or a work on which the Program is based.  Thework thus licensed is called the contributor's "contributor version".  A contributor's "essential patent claims" are all patent claimsowned or controlled by the contributor, whether already acquired orhereafter acquired, that would be infringed by some manner, permittedby this License, of making, using, or selling its contributor version,but do not include claims that would be infringed only as aconsequence of further modification of the contributor version.  Forpurposes of this definition, "control" includes the right to grantpatent sublicenses in a manner consistent with the requirements ofthis License.  Each contributor grants you a non-exclusive, worldwide, royalty-freepatent license under the contributor's essential patent claims, tomake, use, sell, offer for sale, import and otherwise run, modify andpropagate the contents of its contributor version.  In the following three paragraphs, a "patent license" is any expressagreement or commitment, however denominated, not to enforce a patent(such as an express permission to practice a patent or covenant not tosue for patent infringement).  To "grant" such a patent license to aparty means to make such an agreement or commitment not to enforce apatent against the party.  If you convey a covered work, knowingly relying on a patent license,and the Corresponding Source of the work is not available for anyoneto copy, free of charge and under the terms of this License, through apublicly available network server or other readily accessible means,then you must either (1) cause the Corresponding Source to be soavailable, or (2) arrange to deprive yourself of the benefit of thepatent license for this particular work, or (3) arrange, in a mannerconsistent with the requirements of this License, to extend the patentlicense to downstream recipients.  "Knowingly relying" means you haveactual knowledge that, but for the patent license, your conveying thecovered work in a country, or your recipient's use of the covered workin a country, would infringe one or more identifiable patents in thatcountry that you have reason to believe are valid.  If, pursuant to or in connection with a single transaction orarrangement, you convey, or propagate by procuring conveyance of, acovered work, and grant a patent license to some of the partiesreceiving the covered work authorizing them to use, propagate, modifyor convey a specific copy of the covered work, then the patent licenseyou grant is automatically extended to all recipients of the coveredwork and works based on it.  A patent license is "discriminatory" if it does not include withinthe scope of its coverage, prohibits the exercise of, or isconditioned on the non-exercise of one or more of the rights that arespecifically granted under this License.  You may not convey a coveredwork if you are a party to an arrangement with a third party that isin the business of distributing software, under which you make paymentto the third party based on the extent of your activity of conveyingthe work, and under which the third party grants, to any of theparties who would receive the covered work from you, a discriminatorypatent license (a) in connection with copies of the covered workconveyed by you (or copies made from those copies), or (b) primarilyfor and in connection with specific products or compilations thatcontain the covered work, unless you entered into that arrangement,or that patent license was granted, prior to 28 March 2007.  Nothing in this License shall be construed as excluding or limitingany implied license or other defenses to infringement that mayotherwise be available to you under applicable patent law.  12. No Surrender of Others' Freedom.  If conditions are imposed on you (whether by court order, agreement orotherwise) that contradict the conditions of this License, they do notexcuse you from the conditions of this License.  If you cannot convey acovered work so as to satisfy simultaneously your obligations under thisLicense and any other pertinent obligations, then as a consequence you maynot convey it at all.  For example, if you agree to terms that obligate youto collect a royalty for further conveying from those to whom you conveythe Program, the only way you could satisfy both those terms and thisLicense would be to refrain entirely from conveying the Program.  13. Use with the GNU Affero General Public License.  Notwithstanding any other provision of this License, you havepermission to link or combine any covered work with a work licensedunder version 3 of the GNU Affero General Public License into a singlecombined work, and to convey the resulting work.  The terms of thisLicense will continue to apply to the part which is the covered work,but the special requirements of the GNU Affero General Public License,section 13, concerning interaction through a network will apply to thecombination as such.  14. Revised Versions of this License.  The Free Software Foundation may publish revised and/or new versions ofthe GNU General Public License from time to time.  Such new versions willbe similar in spirit to the present version, but may differ in detail toaddress new problems or concerns.  Each version is given a distinguishing version number.  If theProgram specifies that a certain numbered version of the GNU GeneralPublic License "or any later version" applies to it, you have theoption of following the terms and conditions either of that numberedversion or of any later version published by the Free SoftwareFoundation.  If the Program does not specify a version number of theGNU General Public License, you may choose any version ever publishedby the Free Software Foundation.  If the Program specifies that a proxy can decide which futureversions of the GNU General Public License can be used, that proxy'spublic statement of acceptance of a version permanently authorizes youto choose that version for the Program.  Later license versions may give you additional or differentpermissions.  However, no additional obligations are imposed on anyauthor or copyright holder as a result of your choosing to follow alater version.  15. Disclaimer of Warranty.  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BYAPPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHTHOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTYOF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAMIS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OFALL NECESSARY SERVICING, REPAIR OR CORRECTION.  16. Limitation of Liability.  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITINGWILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYSTHE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANYGENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THEUSE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OFDATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRDPARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OFSUCH DAMAGES.  17. Interpretation of Sections 15 and 16.  If the disclaimer of warranty and limitation of liability providedabove cannot be given local legal effect according to their terms,reviewing courts shall apply local law that most closely approximatesan absolute waiver of all civil liability in connection with theProgram, unless a warranty or assumption of liability accompanies acopy of the Program in return for a fee.                     END OF TERMS AND CONDITIONS            How to Apply These Terms to Your New Programs  If you develop a new program, and you want it to be of the greatestpossible use to the public, the best way to achieve this is to make itfree software which everyone can redistribute and change under these terms.  To do so, attach the following notices to the program.  It is safestto attach them to the start of each source file to most effectivelystate the exclusion of warranty; and each file should have at leastthe "copyright" line and a pointer to where the full notice is found.    <one line to give the program's name and a brief idea of what it does.>    Copyright (C) <year>  <name of author>    This program is free software: you can redistribute it and/or modify    it under the terms of the GNU General Public License as published by    the Free Software Foundation, either version 3 of the License, or    (at your option) any later version.    This program is distributed in the hope that it will be useful,    but WITHOUT ANY WARRANTY; without even the implied warranty of    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the    GNU General Public License for more details.    You should have received a copy of the GNU General Public License    along with this program.  If not, see < http://www.gnu.org/licenses/>.Also add information on how to contact you by electronic and paper mail.  If the program does terminal interaction, make it output a shortnotice like this when it starts in an interactive mode:    <program>  Copyright (C) <year>  <name of author>    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.    This is free software, and you are welcome to redistribute it    under certain conditions; type `show c' for details.The hypothetical commands `show w' and `show c' should show the appropriateparts of the General Public License.  Of course, your program's commandsmight be different; for a GUI interface, you would use an "about box".  You should also get your employer (if you work as a programmer) or school,if any, to sign a "copyright disclaimer" for the program, if necessary.For more information on this, and how to apply and follow the GNU GPL, see< http://www.gnu.org/licenses/>.  The GNU General Public License does not permit incorporating your programinto proprietary programs.  If your program is a subroutine library, youmay consider it more useful to permit linking proprietary applications withthe library.  If this is what you want to do, use the GNU Lesser GeneralPublic License instead of this License.  But first, please read< http://www.gnu.org/philosophy/why-not-lgpl.html>.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#lgplv2">2.3. LGPLv2</div><div class="search_word">2.3. lgplv2 gnu lesser general public license                       version 2.1, february 1999 copyright (c) 1991, 1999 free software foundation, inc. 51 franklin street, fifth floor, boston, ma  02110-1301  usa everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.[this is the first released version of the lesser gpl.  it also counts as the successor of the gnu library public license, version 2, hence the version number 2.1.]                            preamble  the licenses for most software are designed to take away yourfreedom to share and change it.  by contrast, the gnu general publiclicenses are intended to guarantee your freedom to share and changefree software--to make sure the software is free for all its users.  this license, the lesser general public license, applies to somespecially designated software packages--typically libraries--of thefree software foundation and other authors who decide to use it.  youcan use it too, but we suggest you first think carefully about whetherthis license or the ordinary general public license is the betterstrategy to use in any particular case, based on the explanations below.  when we speak of free software, we are referring to freedom of use,not price.  our general public licenses are designed to make sure thatyou have the freedom to distribute copies of free software (and chargefor this service if you wish); that you receive source code or can getit if you want it; that you can change the software and use pieces ofit in new free programs; and that you are informed that you can dothese things.  to protect your rights, we need to make restrictions that forbiddistributors to deny you these rights or to ask you to surrender theserights.  these restrictions translate to certain responsibilities foryou if you distribute copies of the library or if you modify it.  for example, if you distribute copies of the library, whether gratisor for a fee, you must give the recipients all the rights that we gaveyou.  you must make sure that they, too, receive or can get the sourcecode.  if you link other code with the library, you must providecomplete object files to the recipients, so that they can relink themwith the library after making changes to the library and recompilingit.  and you must show them these terms so they know their rights.  we protect your rights with a two-step method: (1) we copyright thelibrary, and (2) we offer you this license, which gives you legalpermission to copy, distribute and/or modify the library.  to protect each distributor, we want to make it very clear thatthere is no warranty for the free library.  also, if the library ismodified by someone else and passed on, the recipients should knowthat what they have is not the original version, so that the originalauthor's reputation will not be affected by problems that might beintroduced by others.  finally, software patents pose a constant threat to the existence ofany free program.  we wish to make sure that a company cannoteffectively restrict the users of a free program by obtaining arestrictive license from a patent holder.  therefore, we insist thatany patent license obtained for a version of the library must beconsistent with the full freedom of use specified in this license.  most gnu software, including some libraries, is covered by theordinary gnu general public license.  this license, the gnu lessergeneral public license, applies to certain designated libraries, andis quite different from the ordinary general public license.  we usethis license for certain libraries in order to permit linking thoselibraries into non-free programs.  when a program is linked with a library, whether statically or usinga shared library, the combination of the two is legally speaking acombined work, a derivative of the original library.  the ordinarygeneral public license therefore permits such linking only if theentire combination fits its criteria of freedom.  the lesser generalpublic license permits more lax criteria for linking other code withthe library.  we call this license the "lesser" general public license because itdoes less to protect the user's freedom than the ordinary generalpublic license.  it also provides other free software developers lessof an advantage over competing non-free programs.  these disadvantagesare the reason we use the ordinary general public license for manylibraries.  however, the lesser license provides advantages in certainspecial circumstances.  for example, on rare occasions, there may be a special need toencourage the widest possible use of a certain library, so that it becomesa de-facto standard.  to achieve this, non-free programs must beallowed to use the library.  a more frequent case is that a freelibrary does the same job as widely used non-free libraries.  in thiscase, there is little to gain by limiting the free library to freesoftware only, so we use the lesser general public license.  in other cases, permission to use a particular library in non-freeprograms enables a greater number of people to use a large body offree software.  for example, permission to use the gnu c library innon-free programs enables many more people to use the whole gnuoperating system, as well as its variant, the gnu/linux operatingsystem.  although the lesser general public license is less protective of theusers' freedom, it does ensure that the user of a program that islinked with the library has the freedom and the wherewithal to runthat program using a modified version of the library.  the precise terms and conditions for copying, distribution andmodification follow.  pay close attention to the difference between a"work based on the library" and a "work that uses the library".  theformer contains code derived from the library, whereas the latter mustbe combined with the library in order to run.                  gnu lesser general public license   terms and conditions for copying, distribution and modification  0. this license agreement applies to any software library or otherprogram which contains a notice placed by the copyright holder orother authorized party saying it may be distributed under the terms ofthis lesser general public license (also called "this license").each licensee is addressed as "you".  a "library" means a collection of software functions and/or dataprepared so as to be conveniently linked with application programs(which use some of those functions and data) to form executables.  the "library", below, refers to any such software library or workwhich has been distributed under these terms.  a "work based on thelibrary" means either the library or any derivative work undercopyright law: that is to say, a work containing the library or aportion of it, either verbatim or with modifications and/or translatedstraightforwardly into another language.  (hereinafter, translation isincluded without limitation in the term "modification".)  "source code" for a work means the preferred form of the work formaking modifications to it.  for a library, complete source code meansall the source code for all modules it contains, plus any associatedinterface definition files, plus the scripts used to control compilationand installation of the library.  activities other than copying, distribution and modification are notcovered by this license; they are outside its scope.  the act ofrunning a program using the library is not restricted, and output fromsuch a program is covered only if its contents constitute a work basedon the library (independent of the use of the library in a tool forwriting it).  whether that is true depends on what the library doesand what the program that uses the library does.  1. you may copy and distribute verbatim copies of the library'scomplete source code as you receive it, in any medium, provided thatyou conspicuously and appropriately publish on each copy anappropriate copyright notice and disclaimer of warranty; keep intactall the notices that refer to this license and to the absence of anywarranty; and distribute a copy of this license along with thelibrary.  you may charge a fee for the physical act of transferring a copy,and you may at your option offer warranty protection in exchange for afee.  2. you may modify your copy or copies of the library or any portionof it, thus forming a work based on the library, and copy anddistribute such modifications or work under the terms of section 1above, provided that you also meet all of these conditions:    a) the modified work must itself be a software library.    b) you must cause the files modified to carry prominent notices    stating that you changed the files and the date of any change.    c) you must cause the whole of the work to be licensed at no    charge to all third parties under the terms of this license.    d) if a facility in the modified library refers to a function or a    table of data to be supplied by an application program that uses    the facility, other than as an argument passed when the facility    is invoked, then you must make a good faith effort to ensure that,    in the event an application does not supply such function or    table, the facility still operates, and performs whatever part of    its purpose remains meaningful.    (for example, a function in a library to compute square roots has    a purpose that is entirely well-defined independent of the    application.  therefore, subsection 2d requires that any    application-supplied function or table used by this function must    be optional: if the application does not supply it, the square    root function must still compute square roots.)these requirements apply to the modified work as a whole.  ifidentifiable sections of that work are not derived from the library,and can be reasonably considered independent and separate works inthemselves, then this license, and its terms, do not apply to thosesections when you distribute them as separate works.  but when youdistribute the same sections as part of a whole which is a work basedon the library, the distribution of the whole must be on the terms ofthis license, whose permissions for other licensees extend to theentire whole, and thus to each and every part regardless of who wroteit.thus, it is not the intent of this section to claim rights or contestyour rights to work written entirely by you; rather, the intent is toexercise the right to control the distribution of derivative orcollective works based on the library.in addition, mere aggregation of another work not based on the librarywith the library (or with a work based on the library) on a volume ofa storage or distribution medium does not bring the other work underthe scope of this license.  3. you may opt to apply the terms of the ordinary gnu general publiclicense instead of this license to a given copy of the library.  to dothis, you must alter all the notices that refer to this license, sothat they refer to the ordinary gnu general public license, version 2,instead of to this license.  (if a newer version than version 2 of theordinary gnu general public license has appeared, then you can specifythat version instead if you wish.)  do not make any other change inthese notices.  once this change is made in a given copy, it is irreversible forthat copy, so the ordinary gnu general public license applies to allsubsequent copies and derivative works made from that copy.  this option is useful when you wish to copy part of the code ofthe library into a program that is not a library.  4. you may copy and distribute the library (or a portion orderivative of it, under section 2) in object code or executable formunder the terms of sections 1 and 2 above provided that you accompanyit with the complete corresponding machine-readable source code, whichmust be distributed under the terms of sections 1 and 2 above on amedium customarily used for software interchange.  if distribution of object code is made by offering access to copyfrom a designated place, then offering equivalent access to copy thesource code from the same place satisfies the requirement todistribute the source code, even though third parties are notcompelled to copy the source along with the object code.  5. a program that contains no derivative of any portion of thelibrary, but is designed to work with the library by being compiled orlinked with it, is called a "work that uses the library".  such awork, in isolation, is not a derivative work of the library, andtherefore falls outside the scope of this license.  however, linking a "work that uses the library" with the librarycreates an executable that is a derivative of the library (because itcontains portions of the library), rather than a "work that uses thelibrary".  the executable is therefore covered by this license.section 6 states terms for distribution of such executables.  when a "work that uses the library" uses material from a header filethat is part of the library, the object code for the work may be aderivative work of the library even though the source code is not.whether this is true is especially significant if the work can belinked without the library, or if the work is itself a library.  thethreshold for this to be true is not precisely defined by law.  if such an object file uses only numerical parameters, datastructure layouts and accessors, and small macros and small inlinefunctions (ten lines or less in length), then the use of the objectfile is unrestricted, regardless of whether it is legally a derivativework.  (executables containing this object code plus portions of thelibrary will still fall under section 6.)  otherwise, if the work is a derivative of the library, you maydistribute the object code for the work under the terms of section 6.any executables containing that work also fall under section 6,whether or not they are linked directly with the library itself.  6. as an exception to the sections above, you may also combine orlink a "work that uses the library" with the library to produce awork containing portions of the library, and distribute that workunder terms of your choice, provided that the terms permitmodification of the work for the customer's own use and reverseengineering for debugging such modifications.  you must give prominent notice with each copy of the work that thelibrary is used in it and that the library and its use are covered bythis license.  you must supply a copy of this license.  if the workduring execution displays copyright notices, you must include thecopyright notice for the library among them, as well as a referencedirecting the user to the copy of this license.  also, you must do oneof these things:    a) accompany the work with the complete corresponding    machine-readable source code for the library including whatever    changes were used in the work (which must be distributed under    sections 1 and 2 above); and, if the work is an executable linked    with the library, with the complete machine-readable "work that    uses the library", as object code and/or source code, so that the    user can modify the library and then relink to produce a modified    executable containing the modified library.  (it is understood    that the user who changes the contents of definitions files in the    library will not necessarily be able to recompile the application    to use the modified definitions.)    b) use a suitable shared library mechanism for linking with the    library.  a suitable mechanism is one that (1) uses at run time a    copy of the library already present on the user's computer system,    rather than copying library functions into the executable, and (2)    will operate properly with a modified version of the library, if    the user installs one, as long as the modified version is    interface-compatible with the version that the work was made with.    c) accompany the work with a written offer, valid for at    least three years, to give the same user the materials    specified in subsection 6a, above, for a charge no more    than the cost of performing this distribution.    d) if distribution of the work is made by offering access to copy    from a designated place, offer equivalent access to copy the above    specified materials from the same place.    e) verify that the user has already received a copy of these    materials or that you have already sent this user a copy.  for an executable, the required form of the "work that uses thelibrary" must include any data and utility programs needed forreproducing the executable from it.  however, as a special exception,the materials to be distributed need not include anything that isnormally distributed (in either source or binary form) with the majorcomponents (compiler, kernel, and so on) of the operating system onwhich the executable runs, unless that component itself accompaniesthe executable.  it may happen that this requirement contradicts the licenserestrictions of other proprietary libraries that do not normallyaccompany the operating system.  such a contradiction means you cannotuse both them and the library together in an executable that youdistribute.  7. you may place library facilities that are a work based on thelibrary side-by-side in a single library together with other libraryfacilities not covered by this license, and distribute such a combinedlibrary, provided that the separate distribution of the work based onthe library and of the other library facilities is otherwisepermitted, and provided that you do these two things:    a) accompany the combined library with a copy of the same work    based on the library, uncombined with any other library    facilities.  this must be distributed under the terms of the    sections above.    b) give prominent notice with the combined library of the fact    that part of it is a work based on the library, and explaining    where to find the accompanying uncombined form of the same work.  8. you may not copy, modify, sublicense, link with, or distributethe library except as expressly provided under this license.  anyattempt otherwise to copy, modify, sublicense, link with, ordistribute the library is void, and will automatically terminate yourrights under this license.  however, parties who have received copies,or rights, from you under this license will not have their licensesterminated so long as such parties remain in full compliance.  9. you are not required to accept this license, since you have notsigned it.  however, nothing else grants you permission to modify ordistribute the library or its derivative works.  these actions areprohibited by law if you do not accept this license.  therefore, bymodifying or distributing the library (or any work based on thelibrary), you indicate your acceptance of this license to do so, andall its terms and conditions for copying, distributing or modifyingthe library or works based on it.  10. each time you redistribute the library (or any work based on thelibrary), the recipient automatically receives a license from theoriginal licensor to copy, distribute, link with or modify the librarysubject to these terms and conditions.  you may not impose any furtherrestrictions on the recipients' exercise of the rights granted herein.you are not responsible for enforcing compliance by third parties withthis license.  11. if, as a consequence of a court judgment or allegation of patentinfringement or for any other reason (not limited to patent issues),conditions are imposed on you (whether by court order, agreement orotherwise) that contradict the conditions of this license, they do notexcuse you from the conditions of this license.  if you cannotdistribute so as to satisfy simultaneously your obligations under thislicense and any other pertinent obligations, then as a consequence youmay not distribute the library at all.  for example, if a patentlicense would not permit royalty-free redistribution of the library byall those who receive copies directly or indirectly through you, thenthe only way you could satisfy both it and this license would be torefrain entirely from distribution of the library.if any portion of this section is held invalid or unenforceable under anyparticular circumstance, the balance of the section is intended to apply,and the section as a whole is intended to apply in other circumstances.it is not the purpose of this section to induce you to infringe anypatents or other property right claims or to contest validity of anysuch claims; this section has the sole purpose of protecting theintegrity of the free software distribution system which isimplemented by public license practices.  many people have madegenerous contributions to the wide range of software distributedthrough that system in reliance on consistent application of thatsystem; it is up to the author/donor to decide if he or she is willingto distribute software through any other system and a licensee cannotimpose that choice.this section is intended to make thoroughly clear what is believed tobe a consequence of the rest of this license.  12. if the distribution and/or use of the library is restricted incertain countries either by patents or by copyrighted interfaces, theoriginal copyright holder who places the library under this license may addan explicit geographical distribution limitation excluding those countries,so that distribution is permitted only in or among countries not thusexcluded.  in such case, this license incorporates the limitation as ifwritten in the body of this license.  13. the free software foundation may publish revised and/or newversions of the lesser general public license from time to time.such new versions will be similar in spirit to the present version,but may differ in detail to address new problems or concerns.each version is given a distinguishing version number.  if the libraryspecifies a version number of this license which applies to it and"any later version", you have the option of following the terms andconditions either of that version or of any later version published bythe free software foundation.  if the library does not specify alicense version number, you may choose any version ever published bythe free software foundation.  14. if you wish to incorporate parts of the library into other freeprograms whose distribution conditions are incompatible with these,write to the author to ask for permission.  for software which iscopyrighted by the free software foundation, write to the freesoftware foundation; we sometimes make exceptions for this.  ourdecision will be guided by the two goals of preserving the free statusof all derivatives of our free software and of promoting the sharingand reuse of software generally.                            no warranty  15. because the library is licensed free of charge, there is nowarranty for the library, to the extent permitted by applicable law.except when otherwise stated in writing the copyright holders and/orother parties provide the library "as is" without warranty of anykind, either expressed or implied, including, but not limited to, theimplied warranties of merchantability and fitness for a particularpurpose.  the entire risk as to the quality and performance of thelibrary is with you.  should the library prove defective, you assumethe cost of all necessary servicing, repair or correction.  16. in no event unless required by applicable law or agreed to inwriting will any copyright holder, or any other party who may modifyand/or redistribute the library as permitted above, be liable to youfor damages, including any general, special, incidental orconsequential damages arising out of the use or inability to use thelibrary (including but not limited to loss of data or data beingrendered inaccurate or losses sustained by you or third parties or afailure of the library to operate with any other software), even ifsuch holder or other party has been advised of the possibility of suchdamages.                     end of terms and conditions           how to apply these terms to your new libraries  if you develop a new library, and you want it to be of the greatestpossible use to the public, we recommend making it free software thateveryone can redistribute and change.  you can do so by permittingredistribution under these terms (or, alternatively, under the terms of theordinary general public license).  to apply these terms, attach the following notices to the library.  it issafest to attach them to the start of each source file to most effectivelyconvey the exclusion of warranty; and each file should have at least the"copyright" line and a pointer to where the full notice is found.    <one line to give the library's name and a brief idea of what it does.>    copyright (c) <year>  <name of author>    this library is free software; you can redistribute it and/or    modify it under the terms of the gnu lesser general public    license as published by the free software foundation; either    version 2.1 of the license, or (at your option) any later version.    this library is distributed in the hope that it will be useful,    but without any warranty; without even the implied warranty of    merchantability or fitness for a particular purpose.  see the gnu    lesser general public license for more details.    you should have received a copy of the gnu lesser general public    license along with this library; if not, write to the free software    foundation, inc., 51 franklin street, fifth floor, boston, ma  02110-1301  usaalso add information on how to contact you by electronic and paper mail.you should also get your employer (if you work as a programmer) or yourschool, if any, to sign a "copyright disclaimer" for the library, ifnecessary.  here is a sample; alter the names:  yoyodyne, inc., hereby disclaims all copyright interest in the  library `frob' (a library for tweaking knobs) written by james random hacker.  <signature of ty coon>, 1 april 1990  ty coon, president of vicethat's all there is to it!</div><div class="display_word">2.3. LGPLv2 GNU LESSER GENERAL PUBLIC LICENSE                       Version 2.1, February 1999 Copyright (C) 1991, 1999 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.[This is the first released version of the Lesser GPL.  It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.]                            Preamble  The licenses for most software are designed to take away yourfreedom to share and change it.  By contrast, the GNU General PublicLicenses are intended to guarantee your freedom to share and changefree software--to make sure the software is free for all its users.  This license, the Lesser General Public License, applies to somespecially designated software packages--typically libraries--of theFree Software Foundation and other authors who decide to use it.  Youcan use it too, but we suggest you first think carefully about whetherthis license or the ordinary General Public License is the betterstrategy to use in any particular case, based on the explanations below.  When we speak of free software, we are referring to freedom of use,not price.  Our General Public Licenses are designed to make sure thatyou have the freedom to distribute copies of free software (and chargefor this service if you wish); that you receive source code or can getit if you want it; that you can change the software and use pieces ofit in new free programs; and that you are informed that you can dothese things.  To protect your rights, we need to make restrictions that forbiddistributors to deny you these rights or to ask you to surrender theserights.  These restrictions translate to certain responsibilities foryou if you distribute copies of the library or if you modify it.  For example, if you distribute copies of the library, whether gratisor for a fee, you must give the recipients all the rights that we gaveyou.  You must make sure that they, too, receive or can get the sourcecode.  If you link other code with the library, you must providecomplete object files to the recipients, so that they can relink themwith the library after making changes to the library and recompilingit.  And you must show them these terms so they know their rights.  We protect your rights with a two-step method: (1) we copyright thelibrary, and (2) we offer you this license, which gives you legalpermission to copy, distribute and/or modify the library.  To protect each distributor, we want to make it very clear thatthere is no warranty for the free library.  Also, if the library ismodified by someone else and passed on, the recipients should knowthat what they have is not the original version, so that the originalauthor's reputation will not be affected by problems that might beintroduced by others.  Finally, software patents pose a constant threat to the existence ofany free program.  We wish to make sure that a company cannoteffectively restrict the users of a free program by obtaining arestrictive license from a patent holder.  Therefore, we insist thatany patent license obtained for a version of the library must beconsistent with the full freedom of use specified in this license.  Most GNU software, including some libraries, is covered by theordinary GNU General Public License.  This license, the GNU LesserGeneral Public License, applies to certain designated libraries, andis quite different from the ordinary General Public License.  We usethis license for certain libraries in order to permit linking thoselibraries into non-free programs.  When a program is linked with a library, whether statically or usinga shared library, the combination of the two is legally speaking acombined work, a derivative of the original library.  The ordinaryGeneral Public License therefore permits such linking only if theentire combination fits its criteria of freedom.  The Lesser GeneralPublic License permits more lax criteria for linking other code withthe library.  We call this license the "Lesser" General Public License because itdoes Less to protect the user's freedom than the ordinary GeneralPublic License.  It also provides other free software developers Lessof an advantage over competing non-free programs.  These disadvantagesare the reason we use the ordinary General Public License for manylibraries.  However, the Lesser license provides advantages in certainspecial circumstances.  For example, on rare occasions, there may be a special need toencourage the widest possible use of a certain library, so that it becomesa de-facto standard.  To achieve this, non-free programs must beallowed to use the library.  A more frequent case is that a freelibrary does the same job as widely used non-free libraries.  In thiscase, there is little to gain by limiting the free library to freesoftware only, so we use the Lesser General Public License.  In other cases, permission to use a particular library in non-freeprograms enables a greater number of people to use a large body offree software.  For example, permission to use the GNU C Library innon-free programs enables many more people to use the whole GNUoperating system, as well as its variant, the GNU/Linux operatingsystem.  Although the Lesser General Public License is Less protective of theusers' freedom, it does ensure that the user of a program that islinked with the Library has the freedom and the wherewithal to runthat program using a modified version of the Library.  The precise terms and conditions for copying, distribution andmodification follow.  Pay close attention to the difference between a"work based on the library" and a "work that uses the library".  Theformer contains code derived from the library, whereas the latter mustbe combined with the library in order to run.                  GNU LESSER GENERAL PUBLIC LICENSE   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION  0. This License Agreement applies to any software library or otherprogram which contains a notice placed by the copyright holder orother authorized party saying it may be distributed under the terms ofthis Lesser General Public License (also called "this License").Each licensee is addressed as "you".  A "library" means a collection of software functions and/or dataprepared so as to be conveniently linked with application programs(which use some of those functions and data) to form executables.  The "Library", below, refers to any such software library or workwhich has been distributed under these terms.  A "work based on theLibrary" means either the Library or any derivative work undercopyright law: that is to say, a work containing the Library or aportion of it, either verbatim or with modifications and/or translatedstraightforwardly into another language.  (Hereinafter, translation isincluded without limitation in the term "modification".)  "Source code" for a work means the preferred form of the work formaking modifications to it.  For a library, complete source code meansall the source code for all modules it contains, plus any associatedinterface definition files, plus the scripts used to control compilationand installation of the library.  Activities other than copying, distribution and modification are notcovered by this License; they are outside its scope.  The act ofrunning a program using the Library is not restricted, and output fromsuch a program is covered only if its contents constitute a work basedon the Library (independent of the use of the Library in a tool forwriting it).  Whether that is true depends on what the Library doesand what the program that uses the Library does.  1. You may copy and distribute verbatim copies of the Library'scomplete source code as you receive it, in any medium, provided thatyou conspicuously and appropriately publish on each copy anappropriate copyright notice and disclaimer of warranty; keep intactall the notices that refer to this License and to the absence of anywarranty; and distribute a copy of this License along with theLibrary.  You may charge a fee for the physical act of transferring a copy,and you may at your option offer warranty protection in exchange for afee.  2. You may modify your copy or copies of the Library or any portionof it, thus forming a work based on the Library, and copy anddistribute such modifications or work under the terms of Section 1above, provided that you also meet all of these conditions:    a) The modified work must itself be a software library.    b) You must cause the files modified to carry prominent notices    stating that you changed the files and the date of any change.    c) You must cause the whole of the work to be licensed at no    charge to all third parties under the terms of this License.    d) If a facility in the modified Library refers to a function or a    table of data to be supplied by an application program that uses    the facility, other than as an argument passed when the facility    is invoked, then you must make a good faith effort to ensure that,    in the event an application does not supply such function or    table, the facility still operates, and performs whatever part of    its purpose remains meaningful.    (For example, a function in a library to compute square roots has    a purpose that is entirely well-defined independent of the    application.  Therefore, Subsection 2d requires that any    application-supplied function or table used by this function must    be optional: if the application does not supply it, the square    root function must still compute square roots.)These requirements apply to the modified work as a whole.  Ifidentifiable sections of that work are not derived from the Library,and can be reasonably considered independent and separate works inthemselves, then this License, and its terms, do not apply to thosesections when you distribute them as separate works.  But when youdistribute the same sections as part of a whole which is a work basedon the Library, the distribution of the whole must be on the terms ofthis License, whose permissions for other licensees extend to theentire whole, and thus to each and every part regardless of who wroteit.Thus, it is not the intent of this section to claim rights or contestyour rights to work written entirely by you; rather, the intent is toexercise the right to control the distribution of derivative orcollective works based on the Library.In addition, mere aggregation of another work not based on the Librarywith the Library (or with a work based on the Library) on a volume ofa storage or distribution medium does not bring the other work underthe scope of this License.  3. You may opt to apply the terms of the ordinary GNU General PublicLicense instead of this License to a given copy of the Library.  To dothis, you must alter all the notices that refer to this License, sothat they refer to the ordinary GNU General Public License, version 2,instead of to this License.  (If a newer version than version 2 of theordinary GNU General Public License has appeared, then you can specifythat version instead if you wish.)  Do not make any other change inthese notices.  Once this change is made in a given copy, it is irreversible forthat copy, so the ordinary GNU General Public License applies to allsubsequent copies and derivative works made from that copy.  This option is useful when you wish to copy part of the code ofthe Library into a program that is not a library.  4. You may copy and distribute the Library (or a portion orderivative of it, under Section 2) in object code or executable formunder the terms of Sections 1 and 2 above provided that you accompanyit with the complete corresponding machine-readable source code, whichmust be distributed under the terms of Sections 1 and 2 above on amedium customarily used for software interchange.  If distribution of object code is made by offering access to copyfrom a designated place, then offering equivalent access to copy thesource code from the same place satisfies the requirement todistribute the source code, even though third parties are notcompelled to copy the source along with the object code.  5. A program that contains no derivative of any portion of theLibrary, but is designed to work with the Library by being compiled orlinked with it, is called a "work that uses the Library".  Such awork, in isolation, is not a derivative work of the Library, andtherefore falls outside the scope of this License.  However, linking a "work that uses the Library" with the Librarycreates an executable that is a derivative of the Library (because itcontains portions of the Library), rather than a "work that uses thelibrary".  The executable is therefore covered by this License.Section 6 states terms for distribution of such executables.  When a "work that uses the Library" uses material from a header filethat is part of the Library, the object code for the work may be aderivative work of the Library even though the source code is not.Whether this is true is especially significant if the work can belinked without the Library, or if the work is itself a library.  Thethreshold for this to be true is not precisely defined by law.  If such an object file uses only numerical parameters, datastructure layouts and accessors, and small macros and small inlinefunctions (ten lines or less in length), then the use of the objectfile is unrestricted, regardless of whether it is legally a derivativework.  (Executables containing this object code plus portions of theLibrary will still fall under Section 6.)  Otherwise, if the work is a derivative of the Library, you maydistribute the object code for the work under the terms of Section 6.Any executables containing that work also fall under Section 6,whether or not they are linked directly with the Library itself.  6. As an exception to the Sections above, you may also combine orlink a "work that uses the Library" with the Library to produce awork containing portions of the Library, and distribute that workunder terms of your choice, provided that the terms permitmodification of the work for the customer's own use and reverseengineering for debugging such modifications.  You must give prominent notice with each copy of the work that theLibrary is used in it and that the Library and its use are covered bythis License.  You must supply a copy of this License.  If the workduring execution displays copyright notices, you must include thecopyright notice for the Library among them, as well as a referencedirecting the user to the copy of this License.  Also, you must do oneof these things:    a) Accompany the work with the complete corresponding    machine-readable source code for the Library including whatever    changes were used in the work (which must be distributed under    Sections 1 and 2 above); and, if the work is an executable linked    with the Library, with the complete machine-readable "work that    uses the Library", as object code and/or source code, so that the    user can modify the Library and then relink to produce a modified    executable containing the modified Library.  (It is understood    that the user who changes the contents of definitions files in the    Library will not necessarily be able to recompile the application    to use the modified definitions.)    b) Use a suitable shared library mechanism for linking with the    Library.  A suitable mechanism is one that (1) uses at run time a    copy of the library already present on the user's computer system,    rather than copying library functions into the executable, and (2)    will operate properly with a modified version of the library, if    the user installs one, as long as the modified version is    interface-compatible with the version that the work was made with.    c) Accompany the work with a written offer, valid for at    least three years, to give the same user the materials    specified in Subsection 6a, above, for a charge no more    than the cost of performing this distribution.    d) If distribution of the work is made by offering access to copy    from a designated place, offer equivalent access to copy the above    specified materials from the same place.    e) Verify that the user has already received a copy of these    materials or that you have already sent this user a copy.  For an executable, the required form of the "work that uses theLibrary" must include any data and utility programs needed forreproducing the executable from it.  However, as a special exception,the materials to be distributed need not include anything that isnormally distributed (in either source or binary form) with the majorcomponents (compiler, kernel, and so on) of the operating system onwhich the executable runs, unless that component itself accompaniesthe executable.  It may happen that this requirement contradicts the licenserestrictions of other proprietary libraries that do not normallyaccompany the operating system.  Such a contradiction means you cannotuse both them and the Library together in an executable that youdistribute.  7. You may place library facilities that are a work based on theLibrary side-by-side in a single library together with other libraryfacilities not covered by this License, and distribute such a combinedlibrary, provided that the separate distribution of the work based onthe Library and of the other library facilities is otherwisepermitted, and provided that you do these two things:    a) Accompany the combined library with a copy of the same work    based on the Library, uncombined with any other library    facilities.  This must be distributed under the terms of the    Sections above.    b) Give prominent notice with the combined library of the fact    that part of it is a work based on the Library, and explaining    where to find the accompanying uncombined form of the same work.  8. You may not copy, modify, sublicense, link with, or distributethe Library except as expressly provided under this License.  Anyattempt otherwise to copy, modify, sublicense, link with, ordistribute the Library is void, and will automatically terminate yourrights under this License.  However, parties who have received copies,or rights, from you under this License will not have their licensesterminated so long as such parties remain in full compliance.  9. You are not required to accept this License, since you have notsigned it.  However, nothing else grants you permission to modify ordistribute the Library or its derivative works.  These actions areprohibited by law if you do not accept this License.  Therefore, bymodifying or distributing the Library (or any work based on theLibrary), you indicate your acceptance of this License to do so, andall its terms and conditions for copying, distributing or modifyingthe Library or works based on it.  10. Each time you redistribute the Library (or any work based on theLibrary), the recipient automatically receives a license from theoriginal licensor to copy, distribute, link with or modify the Librarysubject to these terms and conditions.  You may not impose any furtherrestrictions on the recipients' exercise of the rights granted herein.You are not responsible for enforcing compliance by third parties withthis License.  11. If, as a consequence of a court judgment or allegation of patentinfringement or for any other reason (not limited to patent issues),conditions are imposed on you (whether by court order, agreement orotherwise) that contradict the conditions of this License, they do notexcuse you from the conditions of this License.  If you cannotdistribute so as to satisfy simultaneously your obligations under thisLicense and any other pertinent obligations, then as a consequence youmay not distribute the Library at all.  For example, if a patentlicense would not permit royalty-free redistribution of the Library byall those who receive copies directly or indirectly through you, thenthe only way you could satisfy both it and this License would be torefrain entirely from distribution of the Library.If any portion of this section is held invalid or unenforceable under anyparticular circumstance, the balance of the section is intended to apply,and the section as a whole is intended to apply in other circumstances.It is not the purpose of this section to induce you to infringe anypatents or other property right claims or to contest validity of anysuch claims; this section has the sole purpose of protecting theintegrity of the free software distribution system which isimplemented by public license practices.  Many people have madegenerous contributions to the wide range of software distributedthrough that system in reliance on consistent application of thatsystem; it is up to the author/donor to decide if he or she is willingto distribute software through any other system and a licensee cannotimpose that choice.This section is intended to make thoroughly clear what is believed tobe a consequence of the rest of this License.  12. If the distribution and/or use of the Library is restricted incertain countries either by patents or by copyrighted interfaces, theoriginal copyright holder who places the Library under this License may addan explicit geographical distribution limitation excluding those countries,so that distribution is permitted only in or among countries not thusexcluded.  In such case, this License incorporates the limitation as ifwritten in the body of this License.  13. The Free Software Foundation may publish revised and/or newversions of the Lesser General Public License from time to time.Such new versions will be similar in spirit to the present version,but may differ in detail to address new problems or concerns.Each version is given a distinguishing version number.  If the Libraryspecifies a version number of this License which applies to it and"any later version", you have the option of following the terms andconditions either of that version or of any later version published bythe Free Software Foundation.  If the Library does not specify alicense version number, you may choose any version ever published bythe Free Software Foundation.  14. If you wish to incorporate parts of the Library into other freeprograms whose distribution conditions are incompatible with these,write to the author to ask for permission.  For software which iscopyrighted by the Free Software Foundation, write to the FreeSoftware Foundation; we sometimes make exceptions for this.  Ourdecision will be guided by the two goals of preserving the free statusof all derivatives of our free software and of promoting the sharingand reuse of software generally.                            NO WARRANTY  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NOWARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OROTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANYKIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THELIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUMETHE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO INWRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFYAND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOUFOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL ORCONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THELIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEINGRENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR AFAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IFSUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCHDAMAGES.                     END OF TERMS AND CONDITIONS           How to Apply These Terms to Your New Libraries  If you develop a new library, and you want it to be of the greatestpossible use to the public, we recommend making it free software thateveryone can redistribute and change.  You can do so by permittingredistribution under these terms (or, alternatively, under the terms of theordinary General Public License).  To apply these terms, attach the following notices to the library.  It issafest to attach them to the start of each source file to most effectivelyconvey the exclusion of warranty; and each file should have at least the"copyright" line and a pointer to where the full notice is found.    <one line to give the library's name and a brief idea of what it does.>    Copyright (C) <year>  <name of author>    This library is free software; you can redistribute it and/or    modify it under the terms of the GNU Lesser General Public    License as published by the Free Software Foundation; either    version 2.1 of the License, or (at your option) any later version.    This library is distributed in the hope that it will be useful,    but WITHOUT ANY WARRANTY; without even the implied warranty of    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU    Lesser General Public License for more details.    You should have received a copy of the GNU Lesser General Public    License along with this library; if not, write to the Free Software    Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USAAlso add information on how to contact you by electronic and paper mail.You should also get your employer (if you work as a programmer) or yourschool, if any, to sign a "copyright disclaimer" for the library, ifnecessary.  Here is a sample; alter the names:  Yoyodyne, Inc., hereby disclaims all copyright interest in the  library `Frob' (a library for tweaking knobs) written by James Random Hacker.  <signature of Ty Coon>, 1 April 1990  Ty Coon, President of ViceThat's all there is to it!</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#isc">2.4. ISC</div><div class="search_word">2.4. isc text of the isc license:copyright c 2004-2013 by internet systems consortium, inc. (“isc”)copyright c 1995-2003 by internet software consortiumpermission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.the software is provided “as is” and isc disclaims all warranties with regard to this software including all implied warranties of merchantability and fitness. in no event shall isc be liable for any special, direct, indirect, or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of this software.</div><div class="display_word">2.4. ISC Text of the ISC License:Copyright c 2004-2013 by Internet Systems Consortium, Inc. (“ISC”)Copyright c 1995-2003 by Internet Software ConsortiumPermission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.THE SOFTWARE IS PROVIDED “AS IS” AND ISC DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#apache-license-version-20">2.5. Apache License Version 2.0</div><div class="search_word">2.5. apache license version 2.0 apache license                           version 2.0, january 2004                        http://www.apache.org/licenses/   terms and conditions for use, reproduction, and distribution   1. definitions.      "license" shall mean the terms and conditions for use, reproduction,      and distribution as defined by sections 1 through 9 of this document.      "licensor" shall mean the copyright owner or entity authorized by      the copyright owner that is granting the license.      "legal entity" shall mean the union of the acting entity and all      other entities that control, are controlled by, or are under common      control with that entity. for the purposes of this definition,      "control" means (i) the power, direct or indirect, to cause the      direction or management of such entity, whether by contract or      otherwise, or (ii) ownership of fifty percent (50%) or more of the      outstanding shares, or (iii) beneficial ownership of such entity.      "you" (or "your") shall mean an individual or legal entity      exercising permissions granted by this license.      "source" form shall mean the preferred form for making modifications,      including but not limited to software source code, documentation      source, and configuration files.      "object" form shall mean any form resulting from mechanical      transformation or translation of a source form, including but      not limited to compiled object code, generated documentation,      and conversions to other media types.      "work" shall mean the work of authorship, whether in source or      object form, made available under the license, as indicated by a      copyright notice that is included in or attached to the work      (an example is provided in the appendix below).      "derivative works" shall mean any work, whether in source or object      form, that is based on (or derived from) the work and for which the      editorial revisions, annotations, elaborations, or other modifications      represent, as a whole, an original work of authorship. for the purposes      of this license, derivative works shall not include works that remain      separable from, or merely link (or bind by name) to the interfaces of,      the work and derivative works thereof.      "contribution" shall mean any work of authorship, including      the original version of the work and any modifications or additions      to that work or derivative works thereof, that is intentionally      submitted to licensor for inclusion in the work by the copyright owner      or by an individual or legal entity authorized to submit on behalf of      the copyright owner. for the purposes of this definition, "submitted"      means any form of electronic, verbal, or written communication sent      to the licensor or its representatives, including but not limited to      communication on electronic mailing lists, source code control systems,      and issue tracking systems that are managed by, or on behalf of, the      licensor for the purpose of discussing and improving the work, but      excluding communication that is conspicuously marked or otherwise      designated in writing by the copyright owner as "not a contribution."      "contributor" shall mean licensor and any individual or legal entity      on behalf of whom a contribution has been received by licensor and      subsequently incorporated within the work.   2. grant of copyright license. subject to the terms and conditions of      this license, each contributor hereby grants to you a perpetual,      worldwide, non-exclusive, no-charge, royalty-free, irrevocable      copyright license to reproduce, prepare derivative works of,      publicly display, publicly perform, sublicense, and distribute the      work and such derivative works in source or object form.   3. grant of patent license. subject to the terms and conditions of      this license, each contributor hereby grants to you a perpetual,      worldwide, non-exclusive, no-charge, royalty-free, irrevocable      (except as stated in this section) patent license to make, have made,      use, offer to sell, sell, import, and otherwise transfer the work,      where such license applies only to those patent claims licensable      by such contributor that are necessarily infringed by their      contribution(s) alone or by combination of their contribution(s)      with the work to which such contribution(s) was submitted. if you      institute patent litigation against any entity (including a      cross-claim or counterclaim in a lawsuit) alleging that the work      or a contribution incorporated within the work constitutes direct      or contributory patent infringement, then any patent licenses      granted to you under this license for that work shall terminate      as of the date such litigation is filed.   4. redistribution. you may reproduce and distribute copies of the      work or derivative works thereof in any medium, with or without      modifications, and in source or object form, provided that you      meet the following conditions:      (a) you must give any other recipients of the work or          derivative works a copy of this license; and      (b) you must cause any modified files to carry prominent notices          stating that you changed the files; and      (c) you must retain, in the source form of any derivative works          that you distribute, all copyright, patent, trademark, and          attribution notices from the source form of the work,          excluding those notices that do not pertain to any part of          the derivative works; and      (d) if the work includes a "notice" text file as part of its          distribution, then any derivative works that you distribute must          include a readable copy of the attribution notices contained          within such notice file, excluding those notices that do not          pertain to any part of the derivative works, in at least one          of the following places: within a notice text file distributed          as part of the derivative works; within the source form or          documentation, if provided along with the derivative works; or,          within a display generated by the derivative works, if and          wherever such third-party notices normally appear. the contents          of the notice file are for informational purposes only and          do not modify the license. you may add your own attribution          notices within derivative works that you distribute, alongside          or as an addendum to the notice text from the work, provided          that such additional attribution notices cannot be construed          as modifying the license.      you may add your own copyright statement to your modifications and      may provide additional or different license terms and conditions      for use, reproduction, or distribution of your modifications, or      for any such derivative works as a whole, provided your use,      reproduction, and distribution of the work otherwise complies with      the conditions stated in this license.   5. submission of contributions. unless you explicitly state otherwise,      any contribution intentionally submitted for inclusion in the work      by you to the licensor shall be under the terms and conditions of      this license, without any additional terms or conditions.      notwithstanding the above, nothing herein shall supersede or modify      the terms of any separate license agreement you may have executed      with licensor regarding such contributions.   6. trademarks. this license does not grant permission to use the trade      names, trademarks, service marks, or product names of the licensor,      except as required for reasonable and customary use in describing the      origin of the work and reproducing the content of the notice file.   7. disclaimer of warranty. unless required by applicable law or      agreed to in writing, licensor provides the work (and each      contributor provides its contributions) on an "as is" basis,      without warranties or conditions of any kind, either express or      implied, including, without limitation, any warranties or conditions      of title, non-infringement, merchantability, or fitness for a      particular purpose. you are solely responsible for determining the      appropriateness of using or redistributing the work and assume any      risks associated with your exercise of permissions under this license.   8. limitation of liability. in no event and under no legal theory,      whether in tort (including negligence), contract, or otherwise,      unless required by applicable law (such as deliberate and grossly      negligent acts) or agreed to in writing, shall any contributor be      liable to you for damages, including any direct, indirect, special,      incidental, or consequential damages of any character arising as a      result of this license or out of the use or inability to use the      work (including but not limited to damages for loss of goodwill,      work stoppage, computer failure or malfunction, or any and all      other commercial damages or losses), even if such contributor      has been advised of the possibility of such damages.   9. accepting warranty or additional liability. while redistributing      the work or derivative works thereof, you may choose to offer,      and charge a fee for, acceptance of support, warranty, indemnity,      or other liability obligations and/or rights consistent with this      license. however, in accepting such obligations, you may act only      on your own behalf and on your sole responsibility, not on behalf      of any other contributor, and only if you agree to indemnify,      defend, and hold each contributor harmless for any liability      incurred by, or claims asserted against, such contributor by reason      of your accepting any such warranty or additional liability.   end of terms and conditions   appendix: how to apply the apache license to your work.      to apply the apache license to your work, attach the following      boilerplate notice, with the fields enclosed by brackets "[]"      replaced with your own identifying information. (don't include      the brackets!)  the text should be enclosed in the appropriate      comment syntax for the file format. we also recommend that a      file or class name and description of purpose be included on the      same "printed page" as the copyright notice for easier      identification within third-party archives.   copyright [yyyy] [name of copyright owner]   licensed under the apache license, version 2.0 (the "license");   you may not use this file except in compliance with the license.   you may obtain a copy of the license at       http://www.apache.org/licenses/license-2.0   unless required by applicable law or agreed to in writing, software   distributed under the license is distributed on an "as is" basis,   without warranties or conditions of any kind, either express or implied.   see the license for the specific language governing permissions and   limitations under the license.</div><div class="display_word">2.5. Apache License Version 2.0 Apache License                           Version 2.0, January 2004                        http://www.apache.org/licenses/   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION   1. Definitions.      "License" shall mean the terms and conditions for use, reproduction,      and distribution as defined by Sections 1 through 9 of this document.      "Licensor" shall mean the copyright owner or entity authorized by      the copyright owner that is granting the License.      "Legal Entity" shall mean the union of the acting entity and all      other entities that control, are controlled by, or are under common      control with that entity. For the purposes of this definition,      "control" means (i) the power, direct or indirect, to cause the      direction or management of such entity, whether by contract or      otherwise, or (ii) ownership of fifty percent (50%) or more of the      outstanding shares, or (iii) beneficial ownership of such entity.      "You" (or "Your") shall mean an individual or Legal Entity      exercising permissions granted by this License.      "Source" form shall mean the preferred form for making modifications,      including but not limited to software source code, documentation      source, and configuration files.      "Object" form shall mean any form resulting from mechanical      transformation or translation of a Source form, including but      not limited to compiled object code, generated documentation,      and conversions to other media types.      "Work" shall mean the work of authorship, whether in Source or      Object form, made available under the License, as indicated by a      copyright notice that is included in or attached to the work      (an example is provided in the Appendix below).      "Derivative Works" shall mean any work, whether in Source or Object      form, that is based on (or derived from) the Work and for which the      editorial revisions, annotations, elaborations, or other modifications      represent, as a whole, an original work of authorship. For the purposes      of this License, Derivative Works shall not include works that remain      separable from, or merely link (or bind by name) to the interfaces of,      the Work and Derivative Works thereof.      "Contribution" shall mean any work of authorship, including      the original version of the Work and any modifications or additions      to that Work or Derivative Works thereof, that is intentionally      submitted to Licensor for inclusion in the Work by the copyright owner      or by an individual or Legal Entity authorized to submit on behalf of      the copyright owner. For the purposes of this definition, "submitted"      means any form of electronic, verbal, or written communication sent      to the Licensor or its representatives, including but not limited to      communication on electronic mailing lists, source code control systems,      and issue tracking systems that are managed by, or on behalf of, the      Licensor for the purpose of discussing and improving the Work, but      excluding communication that is conspicuously marked or otherwise      designated in writing by the copyright owner as "Not a Contribution."      "Contributor" shall mean Licensor and any individual or Legal Entity      on behalf of whom a Contribution has been received by Licensor and      subsequently incorporated within the Work.   2. Grant of Copyright License. Subject to the terms and conditions of      this License, each Contributor hereby grants to You a perpetual,      worldwide, non-exclusive, no-charge, royalty-free, irrevocable      copyright license to reproduce, prepare Derivative Works of,      publicly display, publicly perform, sublicense, and distribute the      Work and such Derivative Works in Source or Object form.   3. Grant of Patent License. Subject to the terms and conditions of      this License, each Contributor hereby grants to You a perpetual,      worldwide, non-exclusive, no-charge, royalty-free, irrevocable      (except as stated in this section) patent license to make, have made,      use, offer to sell, sell, import, and otherwise transfer the Work,      where such license applies only to those patent claims licensable      by such Contributor that are necessarily infringed by their      Contribution(s) alone or by combination of their Contribution(s)      with the Work to which such Contribution(s) was submitted. If You      institute patent litigation against any entity (including a      cross-claim or counterclaim in a lawsuit) alleging that the Work      or a Contribution incorporated within the Work constitutes direct      or contributory patent infringement, then any patent licenses      granted to You under this License for that Work shall terminate      as of the date such litigation is filed.   4. Redistribution. You may reproduce and distribute copies of the      Work or Derivative Works thereof in any medium, with or without      modifications, and in Source or Object form, provided that You      meet the following conditions:      (a) You must give any other recipients of the Work or          Derivative Works a copy of this License; and      (b) You must cause any modified files to carry prominent notices          stating that You changed the files; and      (c) You must retain, in the Source form of any Derivative Works          that You distribute, all copyright, patent, trademark, and          attribution notices from the Source form of the Work,          excluding those notices that do not pertain to any part of          the Derivative Works; and      (d) If the Work includes a "NOTICE" text file as part of its          distribution, then any Derivative Works that You distribute must          include a readable copy of the attribution notices contained          within such NOTICE file, excluding those notices that do not          pertain to any part of the Derivative Works, in at least one          of the following places: within a NOTICE text file distributed          as part of the Derivative Works; within the Source form or          documentation, if provided along with the Derivative Works; or,          within a display generated by the Derivative Works, if and          wherever such third-party notices normally appear. The contents          of the NOTICE file are for informational purposes only and          do not modify the License. You may add Your own attribution          notices within Derivative Works that You distribute, alongside          or as an addendum to the NOTICE text from the Work, provided          that such additional attribution notices cannot be construed          as modifying the License.      You may add Your own copyright statement to Your modifications and      may provide additional or different license terms and conditions      for use, reproduction, or distribution of Your modifications, or      for any such Derivative Works as a whole, provided Your use,      reproduction, and distribution of the Work otherwise complies with      the conditions stated in this License.   5. Submission of Contributions. Unless You explicitly state otherwise,      any Contribution intentionally submitted for inclusion in the Work      by You to the Licensor shall be under the terms and conditions of      this License, without any additional terms or conditions.      Notwithstanding the above, nothing herein shall supersede or modify      the terms of any separate license agreement you may have executed      with Licensor regarding such Contributions.   6. Trademarks. This License does not grant permission to use the trade      names, trademarks, service marks, or product names of the Licensor,      except as required for reasonable and customary use in describing the      origin of the Work and reproducing the content of the NOTICE file.   7. Disclaimer of Warranty. Unless required by applicable law or      agreed to in writing, Licensor provides the Work (and each      Contributor provides its Contributions) on an "AS IS" BASIS,      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or      implied, including, without limitation, any warranties or conditions      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A      PARTICULAR PURPOSE. You are solely responsible for determining the      appropriateness of using or redistributing the Work and assume any      risks associated with Your exercise of permissions under this License.   8. Limitation of Liability. In no event and under no legal theory,      whether in tort (including negligence), contract, or otherwise,      unless required by applicable law (such as deliberate and grossly      negligent acts) or agreed to in writing, shall any Contributor be      liable to You for damages, including any direct, indirect, special,      incidental, or consequential damages of any character arising as a      result of this License or out of the use or inability to use the      Work (including but not limited to damages for loss of goodwill,      work stoppage, computer failure or malfunction, or any and all      other commercial damages or losses), even if such Contributor      has been advised of the possibility of such damages.   9. Accepting Warranty or Additional Liability. While redistributing      the Work or Derivative Works thereof, You may choose to offer,      and charge a fee for, acceptance of support, warranty, indemnity,      or other liability obligations and/or rights consistent with this      License. However, in accepting such obligations, You may act only      on Your own behalf and on Your sole responsibility, not on behalf      of any other Contributor, and only if You agree to indemnify,      defend, and hold each Contributor harmless for any liability      incurred by, or claims asserted against, such Contributor by reason      of your accepting any such warranty or additional liability.   END OF TERMS AND CONDITIONS   APPENDIX: How to apply the Apache License to your work.      To apply the Apache License to your work, attach the following      boilerplate notice, with the fields enclosed by brackets "[]"      replaced with your own identifying information. (Don't include      the brackets!)  The text should be enclosed in the appropriate      comment syntax for the file format. We also recommend that a      file or class name and description of purpose be included on the      same "printed page" as the copyright notice for easier      identification within third-party archives.   Copyright [yyyy] [name of copyright owner]   Licensed under the Apache License, Version 2.0 (the "License");   you may not use this file except in compliance with the License.   You may obtain a copy of the License at       http://www.apache.org/licenses/LICENSE-2.0   Unless required by applicable law or agreed to in writing, software   distributed under the License is distributed on an "AS IS" BASIS,   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.   See the License for the specific language governing permissions and   limitations under the License.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#bzip2">2.6. bzip2</div><div class="search_word">2.6. bzip2 this program, "bzip2", the associated library "libbzip2", and alldocumentation, are copyright (c) 1996-2010 julian r seward.  allrights reserved.redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditionsare met:1. redistributions of source code must retain the above copyright   notice, this list of conditions and the following disclaimer.2. the origin of this software must not be misrepresented; you must   not claim that you wrote the original software.  if you use this   software in a product, an acknowledgment in the product   documentation would be appreciated but is not required.3. altered source versions must be plainly marked as such, and must   not be misrepresented as being the original software.4. the name of the author may not be used to endorse or promote   products derived from this software without specific prior written   permission.this software is provided by the author ``as is'' and any expressor implied warranties, including, but not limited to, the impliedwarranties of merchantability and fitness for a particular purposeare disclaimed.  in no event shall the author be liable for anydirect, indirect, incidental, special, exemplary, or consequentialdamages (including, but not limited to, procurement of substitutegoods or services; loss of use, data, or profits; or businessinterruption) however caused and on any theory of liability,whether in contract, strict liability, or tort (includingnegligence or otherwise) arising in any way out of the use of thissoftware, even if advised of the possibility of such damage.julian seward, jseward@bzip.orgbzip2/libbzip2 version 1.0.6 of 6 september 2010</div><div class="display_word">2.6. bzip2 This program, "bzip2", the associated library "libbzip2", and alldocumentation, are copyright (C) 1996-2010 Julian R Seward.  Allrights reserved.Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditionsare met:1. Redistributions of source code must retain the above copyright   notice, this list of conditions and the following disclaimer.2. The origin of this software must not be misrepresented; you must   not claim that you wrote the original software.  If you use this   software in a product, an acknowledgment in the product   documentation would be appreciated but is not required.3. Altered source versions must be plainly marked as such, and must   not be misrepresented as being the original software.4. The name of the author may not be used to endorse or promote   products derived from this software without specific prior written   permission.THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESSOR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSEARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDINGNEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.Julian Seward, jseward@bzip.orgbzip2/libbzip2 version 1.0.6 of 6 September 2010</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#civetweb">2.7. civetweb</div><div class="search_word">2.7. civetweb copyright (c) 2013-2018 the civetweb developers (credits.md)copyright (c) 2004-2013 sergey lyubkacopyright (c) 2013 no face press, llc (thomas davis)copyright (c) 2013 f-secure corporationpermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "software"), to deal in the software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the software, and to permit persons to whom the software is furnished to do so, subject to the following conditions:the above copyright notice and this permission notice shall be included in all copies or substantial portions of the software.the software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. in no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software.</div><div class="display_word">2.7. civetweb Copyright (c) 2013-2018 The CivetWeb developers (CREDITS.md)Copyright (c) 2004-2013 Sergey LyubkaCopyright (c) 2013 No Face Press, LLC (Thomas Davis)Copyright (c) 2013 F-Secure CorporationPermission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#csvjsonjs">2.8. csvjson.js</div><div class="search_word">2.8. csvjson.js copyright (c) 2014 aaron snoswell permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "software"), to deal in the software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the software, and to permit persons to whom the software is furnished to do so, subject to the following conditions: the above copyright notice and this permission notice shall be included in all copies or substantial portions of the software. the software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. in no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software.</div><div class="display_word">2.8. csvjson.js Copyright (c) 2014 Aaron Snoswell Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#d3">2.9. D3</div><div class="search_word">2.9. d3 copyright 2010-2016 mike bostockall rights reserved.redistribution and use in source and binary forms, with or without modification,are permitted provided that the following conditions are met:* redistributions of source code must retain the above copyright notice, this  list of conditions and the following disclaimer.* redistributions in binary form must reproduce the above copyright notice,  this list of conditions and the following disclaimer in the documentation  and/or other materials provided with the distribution.* neither the name of the author nor the names of contributors may be used to  endorse or promote products derived from this software without specific prior  written permission.this software is provided by the copyright holders and contributors "as is" andany express or implied warranties, including, but not limited to, the impliedwarranties of merchantability and fitness for a particular purpose aredisclaimed. in no event shall the copyright owner or contributors be liable forany direct, indirect, incidental, special, exemplary, or consequential damages(including, but not limited to, procurement of substitute goods or services;loss of use, data, or profits; or business interruption) however caused and onany theory of liability, whether in contract, strict liability, or tort(including negligence or otherwise) arising in any way out of the use of thissoftware, even if advised of the possibility of such damage.</div><div class="display_word">2.9. D3 Copyright 2010-2016 Mike BostockAll rights reserved.Redistribution and use in source and binary forms, with or without modification,are permitted provided that the following conditions are met:* Redistributions of source code must retain the above copyright notice, this  list of conditions and the following disclaimer.* Redistributions in binary form must reproduce the above copyright notice,  this list of conditions and the following disclaimer in the documentation  and/or other materials provided with the distribution.* Neither the name of the author nor the names of contributors may be used to  endorse or promote products derived from this software without specific prior  written permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" ANDANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FORANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ONANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#isc-dhcp">2.10. ISC DHCP</div><div class="search_word">2.10. isc dhcp copyright (c) 2004-2016 by internet systems consortium, inc. ("isc")copyright (c) 1995-2003 by internet software consortiumpermission to use, copy, modify, and distribute this software for anypurpose with or without fee is hereby granted, provided that the abovecopyright notice and this permission notice appear in all copies.the software is provided "as is" and isc disclaims all warrantieswith regard to this software including all implied warranties ofmerchantability and fitness.  in no event shall isc be liable forany special, direct, indirect, or consequential damages or any damageswhatsoever resulting from loss of use, data or profits, whether in anaction of contract, negligence or other tortious action, arising outof or in connection with the use or performance of this software.  internet systems consortium, inc.  950 charter street  redwood city, ca 94063  <info@isc.org>  https://www.isc.org/</div><div class="display_word">2.10. ISC DHCP Copyright (c) 2004-2016 by Internet Systems Consortium, Inc. ("ISC")Copyright (c) 1995-2003 by Internet Software ConsortiumPermission to use, copy, modify, and distribute this software for anypurpose with or without fee is hereby granted, provided that the abovecopyright notice and this permission notice appear in all copies.THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIESWITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS.  IN NO EVENT SHALL ISC BE LIABLE FORANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGESWHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN ANACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUTOF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.  Internet Systems Consortium, Inc.  950 Charter Street  Redwood City, CA 94063  <info@isc.org>  https://www.isc.org/</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#dynatree">2.11. Dynatree</div><div class="search_word">2.11. dynatree jquery.dynatree.jsdynamic tree view control, with support for lazy loading of branches.copyright (c) 2006-2013, martin wendt (http://wwwendt.de)dual licensed under the mit or gpl version 2 licenses.http://code.google.com/p/dynatree/wiki/licenseinfo</div><div class="display_word">2.11. Dynatree jquery.dynatree.jsDynamic tree view control, with support for lazy loading of branches.Copyright (c) 2006-2013, Martin Wendt (http://wwWendt.de)Dual licensed under the MIT or GPL Version 2 licenses.http://code.google.com/p/dynatree/wiki/LicenseInfo</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#explorercanvas">2.12. ExplorerCanvas</div><div class="search_word">2.12. explorercanvas copyright 2006 google inc.licensed under the apache license, version 2.0 (the "license");you may not use this file except in compliance with the license.you may obtain a copy of the license at  http://www.apache.org/licenses/license-2.0unless required by applicable law or agreed to in writing, softwaredistributed under the license is distributed on an "as is" basis,without warranties or conditions of any kind, either express or implied.see the license for the specific language governing permissions andlimitations under the license.</div><div class="display_word">2.12. ExplorerCanvas Copyright 2006 Google Inc.Licensed under the Apache License, Version 2.0 (the "License");you may not use this file except in compliance with the License.You may obtain a copy of the License at  http://www.apache.org/licenses/LICENSE-2.0Unless required by applicable law or agreed to in writing, softwaredistributed under the License is distributed on an "AS IS" BASIS,WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.See the License for the specific language governing permissions andlimitations under the License.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#expat">2.13. expat</div><div class="search_word">2.13. expat copyright (c) 1998-2000 thai open source software center ltd and clark coopercopyright (c) 2001-2017 expat maintainerspermission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the"software"), to deal in the software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the software, and topermit persons to whom the software is furnished to do so, subject tothe following conditions:the above copyright notice and this permission notice shall be includedin all copies or substantial portions of the software.the software is provided "as is", without warranty of any kind,express or implied, including but not limited to the warranties ofmerchantability, fitness for a particular purpose and noninfringement.in no event shall the authors or copyright holders be liable for anyclaim, damages or other liability, whether in an action of contract,tort or otherwise, arising from, out of or in connection with thesoftware or the use or other dealings in the software.</div><div class="display_word">2.13. expat Copyright (c) 1998-2000 Thai Open Source Software Center Ltd and Clark CooperCopyright (c) 2001-2017 Expat maintainersPermission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the"Software"), to deal in the Software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the Software, and topermit persons to whom the Software is furnished to do so, subject tothe following conditions:The above copyright notice and this permission notice shall be includedin all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANYCLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THESOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#jqcanvas">2.14. jqCanvas</div><div class="search_word">2.14. jqcanvas the mit licensecopyright (c) 2008 david kwast <david *dot* kwast *at* gmail>permission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "software"), to dealin the software without restriction, including without limitation the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the software, and to permit persons to whom the software isfurnished to do so, subject to the following conditions:the above copyright notice and this permission notice shall be included inall copies or substantial portions of the software.the software is provided "as is", without warranty of any kind, express orimplied, including but not limited to the warranties of merchantability,fitness for a particular purpose and noninfringement. in no event shall theauthors or copyright holders be liable for any claim, damages or otherliability, whether in an action of contract, tort or otherwise, arising from,out of or in connection with the software or the use or other dealings inthe software.</div><div class="display_word">2.14. jqCanvas The MIT LicenseCopyright (c) 2008 David Kwast <david *dot* kwast *at* gmail>Permission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "Software"), to dealin the Software without restriction, including without limitation the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software isfurnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included inall copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS INTHE SOFTWARE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#jqplot">2.15. jqPlot</div><div class="search_word">2.15. jqplot title: jqplot chartspure javascript plotting plugin for jquery.about: versionversion: 1.0.4revision: 1121about: copyright & licensecopyright (c) 2009-2012 chris leonellojqplot is currently available for use in all personal or commercial projectsunder both the mit and gpl version 2.0 licenses. this means that you canchoose the license that best suits your project and use it accordingly.see <gpl version 2> and <mit license> contained within this distribution for further information.the author would appreciate an email letting him know of any substantialuse of jqplot.  you can reach the author at: chris at jqplot dot comor see http://www.jqplot.com/info.php.  this is, of course, not required.if you are feeling kind and generous, consider supporting the project bymaking a donation at: http://www.jqplot.com/donate.php.sprintf functions contained in jqplot.sprintf.js by ash searle:    version 2007.04.27    author ash searle    http://hexmen.com/blog/2007/03/printf-sprintf/    http://hexmen.com/js/sprintf.js    the author (ash searle) has placed this code in the public domain:    "this code is unrestricted: you are free to use it however you like."</div><div class="display_word">2.15. jqPlot Title: jqPlot ChartsPure JavaScript plotting plugin for jQuery.About: Versionversion: 1.0.4revision: 1121About: Copyright & LicenseCopyright (c) 2009-2012 Chris LeonellojqPlot is currently available for use in all personal or commercial projectsunder both the MIT and GPL version 2.0 licenses. This means that you canchoose the license that best suits your project and use it accordingly.See <GPL Version 2> and <MIT License> contained within this distribution for further information.The author would appreciate an email letting him know of any substantialuse of jqPlot.  You can reach the author at: chris at jqplot dot comor see http://www.jqplot.com/info.php.  This is, of course, not required.If you are feeling kind and generous, consider supporting the project bymaking a donation at: http://www.jqplot.com/donate.php.sprintf functions contained in jqplot.sprintf.js by Ash Searle:    version 2007.04.27    author Ash Searle    http://hexmen.com/blog/2007/03/printf-sprintf/    http://hexmen.com/js/sprintf.js    The author (Ash Searle) has placed this code in the public domain:    "This code is unrestricted: you are free to use it however you like."</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#jquery">2.16. jQuery</div><div class="search_word">2.16. jquery jquery javascript library v1.9.1http://jquery.com/includes sizzle.jshttp://sizzlejs.com/copyright 2005, 2012 jquery foundation, inc. and other contributorsreleased under the mit licensehttp://jquery.org/licensedate: 2013-2-4</div><div class="display_word">2.16. jQuery jQuery JavaScript Library v1.9.1http://jquery.com/Includes Sizzle.jshttp://sizzlejs.com/Copyright 2005, 2012 jQuery Foundation, Inc. and other contributorsReleased under the MIT licensehttp://jquery.org/licenseDate: 2013-2-4</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#jquery-blockui-plugin">2.17. jQuery blockUI plugin</div><div class="search_word">2.17. jquery blockui plugin copyright c 2007-2013 m. alsup.the blockui plugin is dual licensed under the mit and gpl licenses.you may use either license. the mit license is recommended for most projects because it is simple and easy to understand and it places almost no restrictions on what you can do with the plugin.if the gpl suits your project better you are also free to use the plugin under that license.you do not have to do anything special to choose one license or the other and you don't have to notify anyone which license you are using. you are free to use the blockui plugin in commercial projects as long as the copyright header is left intact.</div><div class="display_word">2.17. jQuery blockUI plugin Copyright c 2007-2013 M. Alsup.The BlockUI plugin is dual licensed under the MIT and GPL licenses.You may use either license. The MIT license is recommended for most projects because it is simple and easy to understand and it places almost no restrictions on what you can do with the plugin.If the GPL suits your project better you are also free to use the plugin under that license.You do not have to do anything special to choose one license or the other and you don't have to notify anyone which license you are using. You are free to use the BlockUI plugin in commercial projects as long as the copyright header is left intact.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#jquery-cookie-plugin">2.18. jQuery Cookie Plugin</div><div class="search_word">2.18. jquery cookie plugin copyright 2014 klaus hartlpermission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the"software"), to deal in the software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the software, and topermit persons to whom the software is furnished to do so, subject tothe following conditions:the above copyright notice and this permission notice shall beincluded in all copies or substantial portions of the software.the software is provided "as is", without warranty of any kind,express or implied, including but not limited to the warranties ofmerchantability, fitness for a particular purpose andnoninfringement. in no event shall the authors or copyright holders beliable for any claim, damages or other liability, whether in an actionof contract, tort or otherwise, arising from, out of or in connectionwith the software or the use or other dealings in the software.</div><div class="display_word">2.18. jQuery Cookie Plugin Copyright 2014 Klaus HartlPermission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the"Software"), to deal in the Software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the Software, and topermit persons to whom the Software is furnished to do so, subject tothe following conditions:The above copyright notice and this permission notice shall beincluded in all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BELIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTIONOF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTIONWITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#jquery-datetimepicker-plugin">2.19. jQuery DateTimePicker plugin</div><div class="search_word">2.19. jquery datetimepicker plugin copyright (c) 2013 http://xdsoft.netpermission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "software"), to dealin the software without restriction, including without limitation the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the software, and to permit persons to whom the software isfurnished to do so, subject to the following conditions:the above copyright notice and this permission notice shall be included inall copies or substantial portions of the software.the software is provided "as is", without warranty of any kind, express orimplied, including but not limited to the warranties of merchantability,fitness for a particular purpose and noninfringement. in no event shall theauthors or copyright holders be liable for any claim, damages or otherliability, whether in an action of contract, tort or otherwise, arising from,out of or in connection with the software or the use or other dealings inthe software.</div><div class="display_word">2.19. jQuery DateTimePicker plugin Copyright (c) 2013 http://xdsoft.netPermission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "Software"), to dealin the Software without restriction, including without limitation the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software isfurnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included inall copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS INTHE SOFTWARE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#jquery-file-upload-plugin-jquery-iframe-transport-plugin-jquery-xdomainrequest-transport-plugin">2.20. jQuery File Upload Plugin / jQuery Iframe Transport Plugin / jQuery XDomainRequest Transport Plugin</div><div class="search_word">2.20. jquery file upload plugin / jquery iframe transport plugin / jquery xdomainrequest transport plugin mit licensecopyright c 2010 sebastian tschan, https://blueimp.netpermission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "software"), to dealin the software without restriction, including without limitation the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the software, and to permit persons to whom the software isfurnished to do so, subject to the following conditions:the above copyright notice and this permission notice shall be included in allcopies or substantial portions of the software.the software is provided "as is", without warranty of any kind, express orimplied, including but not limited to the warranties of merchantability,fitness for a particular purpose and noninfringement. in no event shall theauthors or copyright holders be liable for any claim, damages or otherliability, whether in an action of contract, tort or otherwise, arising from,out of or in connection with the software or the use or other dealings in thesoftware.</div><div class="display_word">2.20. jQuery File Upload Plugin / jQuery Iframe Transport Plugin / jQuery XDomainRequest Transport Plugin MIT LicenseCopyright c 2010 Sebastian Tschan, https://blueimp.netPermission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "Software"), to dealin the Software without restriction, including without limitation the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software isfurnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included in allcopies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THESOFTWARE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#jquery-lined-textarea-plugin">2.21. jQuery Lined TextArea plugin</div><div class="search_word">2.21. jquery lined textarea plugin open source initiative osi - the mit license:licensingthe mit licensecopyright (c) 2010 alan williamson http://alan.blog-city.com/permission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "software"), to dealin the software without restriction, including without limitation the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the software, and to permit persons to whom the software isfurnished to do so, subject to the following conditions:the above copyright notice and this permission notice shall be included inall copies or substantial portions of the software.the software is provided "as is", without warranty of any kind, express orimplied, including but not limited to the warranties of merchantability,fitness for a particular purpose and noninfringement. in no event shall theauthors or copyright holders be liable for any claim, damages or otherliability, whether in an action of contract, tort or otherwise, arising from,out of or in connection with the software or the use or other dealings inthe software.http://www.opensource.org/licenses/mit-license.php</div><div class="display_word">2.21. jQuery Lined TextArea plugin Open Source Initiative OSI - The MIT License:LicensingThe MIT LicenseCopyright (c) 2010 Alan Williamson http://alan.blog-city.com/Permission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "Software"), to dealin the Software without restriction, including without limitation the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software isfurnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included inall copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS INTHE SOFTWARE.http://www.opensource.org/licenses/mit-license.php</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#jquery-migrate">2.22. jQuery Migrate</div><div class="search_word">2.22. jquery migrate copyright jquery foundation and other contributors, https://jquery.org/this software consists of voluntary contributions made by manyindividuals. for exact contribution history, see the revision historyavailable at https://github.com/jquery/jquery-migratethe following license applies to all parts of this software except asdocumented below:====permission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the"software"), to deal in the software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the software, and topermit persons to whom the software is furnished to do so, subject tothe following conditions:the above copyright notice and this permission notice shall beincluded in all copies or substantial portions of the software.the software is provided "as is", without warranty of any kind,express or implied, including but not limited to the warranties ofmerchantability, fitness for a particular purpose andnoninfringement. in no event shall the authors or copyright holders beliable for any claim, damages or other liability, whether in an actionof contract, tort or otherwise, arising from, out of or in connectionwith the software or the use or other dealings in the software.====all files located in the node_modules and external directories areexternally maintained libraries used by this software which have theirown licenses; we recommend you read them, as their terms may differ fromthe terms above.</div><div class="display_word">2.22. jQuery Migrate Copyright jQuery Foundation and other contributors, https://jquery.org/This software consists of voluntary contributions made by manyindividuals. For exact contribution history, see the revision historyavailable at https://github.com/jquery/jquery-migrateThe following license applies to all parts of this software except asdocumented below:====Permission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the"Software"), to deal in the Software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the Software, and topermit persons to whom the Software is furnished to do so, subject tothe following conditions:The above copyright notice and this permission notice shall beincluded in all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BELIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTIONOF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTIONWITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.====All files located in the node_modules and external directories areexternally maintained libraries used by this software which have theirown licenses; we recommend you read them, as their terms may differ fromthe terms above.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#jquery-ui">2.23. jQuery UI</div><div class="search_word">2.23. jquery ui copyright jquery foundation and other contributors, https://jquery.org/this software consists of voluntary contributions made by manyindividuals. for exact contribution history, see the revision historyavailable at https://github.com/jquery/jquery-uithe following license applies to all parts of this software except asdocumented below:====permission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the"software"), to deal in the software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the software, and topermit persons to whom the software is furnished to do so, subject tothe following conditions:the above copyright notice and this permission notice shall beincluded in all copies or substantial portions of the software.the software is provided "as is", without warranty of any kind,express or implied, including but not limited to the warranties ofmerchantability, fitness for a particular purpose andnoninfringement. in no event shall the authors or copyright holders beliable for any claim, damages or other liability, whether in an actionof contract, tort or otherwise, arising from, out of or in connectionwith the software or the use or other dealings in the software.====copyright and related rights for sample code are waived via cc0. samplecode is defined as all source code contained within the demos directory.cc0: http://creativecommons.org/publicdomain/zero/1.0/====all files located in the node_modules and external directories areexternally maintained libraries used by this software which have theirown licenses; we recommend you read them, as their terms may differ fromthe terms above.</div><div class="display_word">2.23. jQuery UI Copyright jQuery Foundation and other contributors, https://jquery.org/This software consists of voluntary contributions made by manyindividuals. For exact contribution history, see the revision historyavailable at https://github.com/jquery/jquery-uiThe following license applies to all parts of this software except asdocumented below:====Permission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the"Software"), to deal in the Software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the Software, and topermit persons to whom the Software is furnished to do so, subject tothe following conditions:The above copyright notice and this permission notice shall beincluded in all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BELIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTIONOF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTIONWITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.====Copyright and related rights for sample code are waived via CC0. Samplecode is defined as all source code contained within the demos directory.CC0: http://creativecommons.org/publicdomain/zero/1.0/====All files located in the node_modules and external directories areexternally maintained libraries used by this software which have theirown licenses; we recommend you read them, as their terms may differ fromthe terms above.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#jquery-ui-touch-punch">2.24. jQuery UI Touch Punch</div><div class="search_word">2.24. jquery ui touch punch jquery ui touch punch 0.2.3copyright 2011 2014, dave furferodual licensed under the mit or gpl version 2 licenses.depends: jquery.ui.widget.js jquery.ui.mouse.js</div><div class="display_word">2.24. jQuery UI Touch Punch jQuery UI Touch Punch 0.2.3Copyright 2011 2014, Dave FurferoDual licensed under the MIT or GPL Version 2 licenses.Depends: jquery.ui.widget.js jquery.ui.mouse.js</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#jquery-ui-ympicker">2.25. jQuery UI Ympicker</div><div class="search_word">2.25. jquery ui ympicker jquery ui ympicker 1.8.21copyright 2012, authors.txt (http://jqueryui.com/about)dual licensed under the mit or gpl version 2 licenses.http://jquery.org/licensehttp://docs.jquery.com/ui/ympickerdepends:    jquery.ui.core.js</div><div class="display_word">2.25. jQuery UI Ympicker jQuery UI Ympicker 1.8.21Copyright 2012, AUTHORS.txt (http://jqueryui.com/about)Dual licensed under the MIT or GPL Version 2 licenses.http://jquery.org/licensehttp://docs.jquery.com/UI/YmpickerDepends:    jquery.ui.core.js</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#libcurl">2.26. libcurl</div><div class="search_word">2.26. libcurl copyright and permission noticecopyright (c) 1996 - 2014, daniel stenberg, <daniel@haxx.se>.all rights reserved.permission to use, copy, modify, and distribute this software for any purposewith or without fee is hereby granted, provided that the above copyrightnotice and this permission notice appear in all copies.the software is provided "as is", without warranty of any kind, express orimplied, including but not limited to the warranties of merchantability,fitness for a particular purpose and noninfringement of third party rights. inno event shall the authors or copyright holders be liable for any claim,damages or other liability, whether in an action of contract, tort orotherwise, arising from, out of or in connection with the software or the useor other dealings in the software.except as contained in this notice, the name of a copyright holder shall notbe used in advertising or otherwise to promote the sale, use or other dealingsin this software without prior written authorization of the copyright holder.</div><div class="display_word">2.26. libcurl COPYRIGHT AND PERMISSION NOTICECopyright (c) 1996 - 2014, Daniel Stenberg, <daniel@haxx.se>.All rights reserved.Permission to use, copy, modify, and distribute this software for any purposewith or without fee is hereby granted, provided that the above copyrightnotice and this permission notice appear in all copies.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. INNO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OROTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USEOR OTHER DEALINGS IN THE SOFTWARE.Except as contained in this notice, the name of a copyright holder shall notbe used in advertising or otherwise to promote the sale, use or other dealingsin this Software without prior written authorization of the copyright holder.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#libevent">2.27. libevent</div><div class="search_word">2.27. libevent libevent is available for use under the following license, commonly knownas the 3-clause (or "modified") bsd license:==============================copyright (c) 2000-2007 niels provos <provos@citi.umich.edu>copyright (c) 2007-2012 niels provos and nick mathewsonredistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditionsare met:1. redistributions of source code must retain the above copyright   notice, this list of conditions and the following disclaimer.2. redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.3. the name of the author may not be used to endorse or promote products   derived from this software without specific prior written permission.this software is provided by the author ``as is'' and any express orimplied warranties, including, but not limited to, the implied warrantiesof merchantability and fitness for a particular purpose are disclaimed.in no event shall the author be liable for any direct, indirect,incidental, special, exemplary, or consequential damages (including, butnot limited to, procurement of substitute goods or services; loss of use,data, or profits; or business interruption) however caused and on anytheory of liability, whether in contract, strict liability, or tort(including negligence or otherwise) arising in any way out of the use ofthis software, even if advised of the possibility of such damage.==============================portions of libevent are based on works by others, also made available bythem under the three-clause bsd license above.  the copyright notices areavailable in the corresponding source files; the license is as above.  here'sa list:log.c:   copyright (c) 2000 dug song <dugsong@monkey.org>   copyright (c) 1993 the regents of the university of california.strlcpy.c:   copyright (c) 1998 todd c. miller <todd.miller@courtesan.com>win32select.c:   copyright (c) 2003 michael a. davis <mike@datanerds.net>evport.c:   copyright (c) 2007 sun microsystemsht-internal.h:   copyright (c) 2002 christopher clarkminheap-internal.h:   copyright (c) 2006 maxim yegorushkin <maxim.yegorushkin@gmail.com>==============================the arc4module is available under the following, sometimes called the"openbsd" license:   copyright (c) 1996, david mazieres <dm@uun.org>   copyright (c) 2008, damien miller <djm@openbsd.org>   permission to use, copy, modify, and distribute this software for any   purpose with or without fee is hereby granted, provided that the above   copyright notice and this permission notice appear in all copies.   the software is provided "as is" and the author disclaims all warranties   with regard to this software including all implied warranties of   merchantability and fitness. in no event shall the author be liable for   any special, direct, indirect, or consequential damages or any damages   whatsoever resulting from loss of use, data or profits, whether in an   action of contract, negligence or other tortious action, arising out of   or in connection with the use or performance of this software.==============================the windows timer code is based on code from libutp, which isdistributed under this license, sometimes called the "mit" license.copyright (c) 2010 bittorrent, inc.permission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "software"), to dealin the software without restriction, including without limitation the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the software, and to permit persons to whom the software isfurnished to do so, subject to the following conditions:the above copyright notice and this permission notice shall be included inall copies or substantial portions of the software.the software is provided "as is", without warranty of any kind, express orimplied, including but not limited to the warranties of merchantability,fitness for a particular purpose and noninfringement. in no event shall theauthors or copyright holders be liable for any claim, damages or otherliability, whether in an action of contract, tort or otherwise, arising from,out of or in connection with the software or the use or other dealings inthe software.</div><div class="display_word">2.27. libevent Libevent is available for use under the following license, commonly knownas the 3-clause (or "modified") BSD license:==============================Copyright (c) 2000-2007 Niels Provos <provos@citi.umich.edu>Copyright (c) 2007-2012 Niels Provos and Nick MathewsonRedistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditionsare met:1. Redistributions of source code must retain the above copyright   notice, this list of conditions and the following disclaimer.2. Redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.3. The name of the author may not be used to endorse or promote products   derived from this software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIESOF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUTNOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OFTHIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.==============================Portions of Libevent are based on works by others, also made available bythem under the three-clause BSD license above.  The copyright notices areavailable in the corresponding source files; the license is as above.  Here'sa list:log.c:   Copyright (c) 2000 Dug Song <dugsong@monkey.org>   Copyright (c) 1993 The Regents of the University of California.strlcpy.c:   Copyright (c) 1998 Todd C. Miller <Todd.Miller@courtesan.com>win32select.c:   Copyright (c) 2003 Michael A. Davis <mike@datanerds.net>evport.c:   Copyright (c) 2007 Sun Microsystemsht-internal.h:   Copyright (c) 2002 Christopher Clarkminheap-internal.h:   Copyright (c) 2006 Maxim Yegorushkin <maxim.yegorushkin@gmail.com>==============================The arc4module is available under the following, sometimes called the"OpenBSD" license:   Copyright (c) 1996, David Mazieres <dm@uun.org>   Copyright (c) 2008, Damien Miller <djm@openbsd.org>   Permission to use, copy, modify, and distribute this software for any   purpose with or without fee is hereby granted, provided that the above   copyright notice and this permission notice appear in all copies.   THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES   WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF   MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR   ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES   WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN   ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF   OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.==============================The Windows timer code is based on code from libutp, which isdistributed under this license, sometimes called the "MIT" license.Copyright (c) 2010 BitTorrent, Inc.Permission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "Software"), to dealin the Software without restriction, including without limitation the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software isfurnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included inall copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS INTHE SOFTWARE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#libffi">2.28. libffi</div><div class="search_word">2.28. libffi libffi - copyright (c) 1996-2014  anthony green, red hat, inc and others.see source files for details.permission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the``software''), to deal in the software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the software, and topermit persons to whom the software is furnished to do so, subject tothe following conditions:the above copyright notice and this permission notice shall beincluded in all copies or substantial portions of the software.the software is provided ``as is'', without warranty of any kind,express or implied, including but not limited to the warranties ofmerchantability, fitness for a particular purpose and noninfringement.in no event shall the authors or copyright holders be liable for anyclaim, damages or other liability, whether in an action of contract,tort or otherwise, arising from, out of or in connection with thesoftware or the use or other dealings in the software.</div><div class="display_word">2.28. libffi libffi - Copyright (c) 1996-2014  Anthony Green, Red Hat, Inc and others.See source files for details.Permission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the``Software''), to deal in the Software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the Software, and topermit persons to whom the Software is furnished to do so, subject tothe following conditions:The above copyright notice and this permission notice shall beincluded in all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED ``AS IS'', WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANYCLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THESOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#net-snmp">2.29. net-snmp</div><div class="search_word">2.29. net-snmp various copyrights apply to this package, listed in various separateparts below.  please make sure that you read all the parts.---- part 1: cmu/ucd copyright notice: (bsd like) -----       copyright 1989, 1991, 1992 by carnegie mellon university          derivative work - 1996, 1998-2000copyright 1996, 1998-2000 the regents of the university of california             all rights reservedpermission to use, copy, modify and distribute this software and itsdocumentation for any purpose and without fee is hereby granted,provided that the above copyright notice appears in all copies andthat both that copyright notice and this permission notice appear insupporting documentation, and that the name of cmu and the regents ofthe university of california not be used in advertising or publicitypertaining to distribution of the software without specific writtenpermission.cmu and the regents of the university of california disclaim allwarranties with regard to this software, including all impliedwarranties of merchantability and fitness.  in no event shall cmu orthe regents of the university of california be liable for any special,indirect or consequential damages or any damages whatsoever resultingfrom the loss of use, data or profits, whether in an action ofcontract, negligence or other tortious action, arising out of or inconnection with the use or performance of this software.---- part 2: networks associates technology, inc copyright notice (bsd) -----copyright (c) 2001-2003, networks associates technology, incall rights reserved.redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:*  redistributions of source code must retain the above copyright notice,   this list of conditions and the following disclaimer.*  redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.*  neither the name of the networks associates technology, inc nor the   names of its contributors may be used to endorse or promote   products derived from this software without specific prior written   permission.this software is provided by the copyright holders and contributors ``asis'' and any express or implied warranties, including, but not limited to,the implied warranties of merchantability and fitness for a particularpurpose are disclaimed.  in no event shall the copyright holders orcontributors be liable for any direct, indirect, incidental, special,exemplary, or consequential damages (including, but not limited to,procurement of substitute goods or services; loss of use, data, or profits;or business interruption) however caused and on any theory of liability,whether in contract, strict liability, or tort (including negligence orotherwise) arising in any way out of the use of this software, even ifadvised of the possibility of such damage.---- part 3: cambridge broadband ltd. copyright notice (bsd) -----portions of this code are copyright (c) 2001-2003, cambridge broadband ltd.all rights reserved.redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:*  redistributions of source code must retain the above copyright notice,   this list of conditions and the following disclaimer.*  redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.*  the name of cambridge broadband ltd. may not be used to endorse or   promote products derived from this software without specific prior   written permission.this software is provided by the copyright holder ``as is'' and anyexpress or implied warranties, including, but not limited to, theimplied warranties of merchantability and fitness for a particularpurpose are disclaimed.  in no event shall the copyright holder beliable for any direct, indirect, incidental, special, exemplary, orconsequential damages (including, but not limited to, procurement ofsubstitute goods or services; loss of use, data, or profits; orbusiness interruption) however caused and on any theory of liability,whether in contract, strict liability, or tort (including negligenceor otherwise) arising in any way out of the use of this software, evenif advised of the possibility of such damage.---- part 4: sun microsystems, inc. copyright notice (bsd) -----copyright c 2003 sun microsystems, inc., 4150 network circle, santa clara,california 95054, u.s.a. all rights reserved.use is subject to license terms below.this distribution may include materials developed by third parties.sun, sun microsystems, the sun logo and solaris are trademarks or registeredtrademarks of sun microsystems, inc. in the u.s. and other countries.redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:*  redistributions of source code must retain the above copyright notice,    this list of conditions and the following disclaimer.*  redistributions in binary form must reproduce the above copyright    notice, this list of conditions and the following disclaimer in the    documentation and/or other materials provided with the distribution.*  neither the name of the sun microsystems, inc. nor the    names of its contributors may be used to endorse or promote    products derived from this software without specific prior written    permission.this software is provided by the copyright holders and contributors ``asis'' and any express or implied warranties, including, but not limited to,the implied warranties of merchantability and fitness for a particularpurpose are disclaimed.  in no event shall the copyright holders orcontributors be liable for any direct, indirect, incidental, special,exemplary, or consequential damages (including, but not limited to,procurement of substitute goods or services; loss of use, data, or profits;or business interruption) however caused and on any theory of liability,whether in contract, strict liability, or tort (including negligence orotherwise) arising in any way out of the use of this software, even ifadvised of the possibility of such damage.---- part 5: sparta, inc copyright notice (bsd) -----copyright (c) 2003-2009, sparta, incall rights reserved.redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:*  redistributions of source code must retain the above copyright notice,   this list of conditions and the following disclaimer.*  redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.*  neither the name of sparta, inc nor the names of its contributors may   be used to endorse or promote products derived from this software   without specific prior written permission.this software is provided by the copyright holders and contributors ``asis'' and any express or implied warranties, including, but not limited to,the implied warranties of merchantability and fitness for a particularpurpose are disclaimed.  in no event shall the copyright holders orcontributors be liable for any direct, indirect, incidental, special,exemplary, or consequential damages (including, but not limited to,procurement of substitute goods or services; loss of use, data, or profits;or business interruption) however caused and on any theory of liability,whether in contract, strict liability, or tort (including negligence orotherwise) arising in any way out of the use of this software, even ifadvised of the possibility of such damage.---- part 6: cisco/buptnic copyright notice (bsd) -----copyright (c) 2004, cisco, inc and information networkcenter of beijing university of posts and telecommunications.all rights reserved.redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:*  redistributions of source code must retain the above copyright notice,   this list of conditions and the following disclaimer.*  redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.*  neither the name of cisco, inc, beijing university of posts and   telecommunications, nor the names of their contributors may   be used to endorse or promote products derived from this software   without specific prior written permission.this software is provided by the copyright holders and contributors ``asis'' and any express or implied warranties, including, but not limited to,the implied warranties of merchantability and fitness for a particularpurpose are disclaimed.  in no event shall the copyright holders orcontributors be liable for any direct, indirect, incidental, special,exemplary, or consequential damages (including, but not limited to,procurement of substitute goods or services; loss of use, data, or profits;or business interruption) however caused and on any theory of liability,whether in contract, strict liability, or tort (including negligence orotherwise) arising in any way out of the use of this software, even ifadvised of the possibility of such damage.---- part 7: fabasoft r&d software gmbh & co kg copyright notice (bsd) -----copyright (c) fabasoft r&d software gmbh & co kg, 2003oss@fabasoft.comauthor: bernhard penzredistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:*  redistributions of source code must retain the above copyright notice,   this list of conditions and the following disclaimer.*  redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.*  the name of fabasoft r&d software gmbh & co kg or any of its subsidiaries,   brand or product names may not be used to endorse or promote products   derived from this software without specific prior written permission.this software is provided by the copyright holder ``as is'' and anyexpress or implied warranties, including, but not limited to, theimplied warranties of merchantability and fitness for a particularpurpose are disclaimed.  in no event shall the copyright holder beliable for any direct, indirect, incidental, special, exemplary, orconsequential damages (including, but not limited to, procurement ofsubstitute goods or services; loss of use, data, or profits; orbusiness interruption) however caused and on any theory of liability,whether in contract, strict liability, or tort (including negligenceor otherwise) arising in any way out of the use of this software, evenif advised of the possibility of such damage.---- part 8: apple inc. copyright notice (bsd) -----copyright (c) 2007 apple inc. all rights reserved.redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditionsare met:1.  redistributions of source code must retain the above copyrightnotice, this list of conditions and the following disclaimer.2.  redistributions in binary form must reproduce the abovecopyright notice, this list of conditions and the followingdisclaimer in the documentation and/or other materials providedwith the distribution.3.  neither the name of apple inc. ("apple") nor the names of itscontributors may be used to endorse or promote products derivedfrom this software without specific prior written permission.this software is provided by apple and its contributors "as is" andany express or implied warranties, including, but not limited to,the implied warranties of merchantability and fitness for aparticular purpose are disclaimed. in no event shall apple or itscontributors be liable for any direct, indirect, incidental,special, exemplary, or consequential damages (including, but notlimited to, procurement of substitute goods or services; loss ofuse, data, or profits; or business interruption) however caused andon any theory of liability, whether in contract, strict liability,or tort (including negligence or otherwise) arising in any way outof the use of this software, even if advised of the possibility ofsuch damage.---- part 9: sciencelogic, llc copyright notice (bsd) -----copyright (c) 2009, sciencelogic, llcall rights reserved.redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions aremet:*  redistributions of source code must retain the above copyright notice,   this list of conditions and the following disclaimer.*  redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.*  neither the name of sciencelogic, llc nor the names of its   contributors may be used to endorse or promote products derived   from this software without specific prior written permission.this software is provided by the copyright holders and contributors``as is'' and any express or implied warranties, including, but notlimited to, the implied warranties of merchantability and fitness fora particular purpose are disclaimed.  in no event shall the copyrightholders or contributors be liable for any direct, indirect,incidental, special, exemplary, or consequential damages (including,but not limited to, procurement of substitute goods or services; lossof use, data, or profits; or business interruption) however caused andon any theory of liability, whether in contract, strict liability, ortort (including negligence or otherwise) arising in any way out of theuse of this software, even if advised of the possibility of suchdamage.</div><div class="display_word">2.29. net-snmp Various copyrights apply to this package, listed in various separateparts below.  Please make sure that you read all the parts.---- Part 1: CMU/UCD copyright notice: (BSD like) -----       Copyright 1989, 1991, 1992 by Carnegie Mellon University          Derivative Work - 1996, 1998-2000Copyright 1996, 1998-2000 The Regents of the University of California             All Rights ReservedPermission to use, copy, modify and distribute this software and itsdocumentation for any purpose and without fee is hereby granted,provided that the above copyright notice appears in all copies andthat both that copyright notice and this permission notice appear insupporting documentation, and that the name of CMU and The Regents ofthe University of California not be used in advertising or publicitypertaining to distribution of the software without specific writtenpermission.CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALLWARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS.  IN NO EVENT SHALL CMU ORTHE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL,INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTINGFROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OFCONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR INCONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.---- Part 2: Networks Associates Technology, Inc copyright notice (BSD) -----Copyright (c) 2001-2003, Networks Associates Technology, IncAll rights reserved.Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:*  Redistributions of source code must retain the above copyright notice,   this list of conditions and the following disclaimer.*  Redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.*  Neither the name of the Networks Associates Technology, Inc nor the   names of its contributors may be used to endorse or promote   products derived from this software without specific prior written   permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``ASIS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT HOLDERS ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) -----Portions of this code are copyright (c) 2001-2003, Cambridge Broadband Ltd.All rights reserved.Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:*  Redistributions of source code must retain the above copyright notice,   this list of conditions and the following disclaimer.*  Redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.*  The name of Cambridge Broadband Ltd. may not be used to endorse or   promote products derived from this software without specific prior   written permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANYEXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT HOLDER BELIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OFSUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; ORBUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCEOR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVENIF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.---- Part 4: Sun Microsystems, Inc. copyright notice (BSD) -----Copyright c 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara,California 95054, U.S.A. All rights reserved.Use is subject to license terms below.This distribution may include materials developed by third parties.Sun, Sun Microsystems, the Sun logo and Solaris are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the U.S. and other countries.Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:*  Redistributions of source code must retain the above copyright notice,    this list of conditions and the following disclaimer.*  Redistributions in binary form must reproduce the above copyright    notice, this list of conditions and the following disclaimer in the    documentation and/or other materials provided with the distribution.*  Neither the name of the Sun Microsystems, Inc. nor the    names of its contributors may be used to endorse or promote    products derived from this software without specific prior written    permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``ASIS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT HOLDERS ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.---- Part 5: Sparta, Inc copyright notice (BSD) -----Copyright (c) 2003-2009, Sparta, IncAll rights reserved.Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:*  Redistributions of source code must retain the above copyright notice,   this list of conditions and the following disclaimer.*  Redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.*  Neither the name of Sparta, Inc nor the names of its contributors may   be used to endorse or promote products derived from this software   without specific prior written permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``ASIS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT HOLDERS ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.---- Part 6: Cisco/BUPTNIC copyright notice (BSD) -----Copyright (c) 2004, Cisco, Inc and Information NetworkCenter of Beijing University of Posts and Telecommunications.All rights reserved.Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:*  Redistributions of source code must retain the above copyright notice,   this list of conditions and the following disclaimer.*  Redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.*  Neither the name of Cisco, Inc, Beijing University of Posts and   Telecommunications, nor the names of their contributors may   be used to endorse or promote products derived from this software   without specific prior written permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``ASIS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT HOLDERS ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.---- Part 7: Fabasoft R&D Software GmbH & Co KG copyright notice (BSD) -----Copyright (c) Fabasoft R&D Software GmbH & Co KG, 2003oss@fabasoft.comAuthor: Bernhard PenzRedistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions are met:*  Redistributions of source code must retain the above copyright notice,   this list of conditions and the following disclaimer.*  Redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.*  The name of Fabasoft R&D Software GmbH & Co KG or any of its subsidiaries,   brand or product names may not be used to endorse or promote products   derived from this software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANYEXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT HOLDER BELIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OFSUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; ORBUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCEOR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVENIF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.---- Part 8: Apple Inc. copyright notice (BSD) -----Copyright (c) 2007 Apple Inc. All rights reserved.Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditionsare met:1.  Redistributions of source code must retain the above copyrightnotice, this list of conditions and the following disclaimer.2.  Redistributions in binary form must reproduce the abovecopyright notice, this list of conditions and the followingdisclaimer in the documentation and/or other materials providedwith the distribution.3.  Neither the name of Apple Inc. ("Apple") nor the names of itscontributors may be used to endorse or promote products derivedfrom this software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY APPLE AND ITS CONTRIBUTORS "AS IS" ANDANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL APPLE OR ITSCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OFUSE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED ANDON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUTOF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OFSUCH DAMAGE.---- Part 9: ScienceLogic, LLC copyright notice (BSD) -----Copyright (c) 2009, ScienceLogic, LLCAll rights reserved.Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions aremet:*  Redistributions of source code must retain the above copyright notice,   this list of conditions and the following disclaimer.*  Redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.*  Neither the name of ScienceLogic, LLC nor the names of its   contributors may be used to endorse or promote products derived   from this software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHTHOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSSOF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED ANDON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, ORTORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THEUSE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCHDAMAGE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#ntp">2.30. ntp</div><div class="search_word">2.30. ntp this file is automatically generated from html/copyright.html  copyright notice   jpg "clone me," says dolly sheepishly.   last update: 17-jan-2015 00:16 utc     *________________________________________________________________   the following copyright notice applies to all files collectively   called the network time protocol version 4 distribution. unless   specifically declared otherwise in an individual file, this entire   notice applies as if the text was explicitly included in the file.************************************************************************                                                                     ** copyright (c) university of delaware 1992-2015                      **                                                                     ** permission to use, copy, modify, and distribute this software and   ** its documentation for any purpose with or without fee is hereby     ** granted, provided that the above copyright notice appears in all    ** copies and that both the copyright notice and this permission       ** notice appear in supporting documentation, and that the name        ** university of delaware not be used in advertising or publicity      ** pertaining to distribution of the software without specific,        ** written prior permission. the university of delaware makes no       ** representations about the suitability this software for any         ** purpose. it is provided "as is" without express or implied          ** warranty.                                                           **                                                                     ************************************************************************   content starting in 2011 from harlan stenn, danny mayer, and martin   burnicki is:************************************************************************                                                                     ** copyright (c) network time foundation 2011-2015                     **                                                                     ** all rights reserved                                                 **                                                                     ** redistribution and use in source and binary forms, with or without  ** modification, are permitted provided that the following conditions  ** are met:                                                            ** 1. redistributions of source code must retain the above copyright   **    notice, this list of conditions and the following disclaimer.    ** 2. redistributions in binary form must reproduce the above          **    copyright notice, this list of conditions and the following      **    disclaimer in the documentation and/or other materials provided  **    with the distribution.                                           **                                                                     ** this software is provided by the authors ``as is'' and any express  ** or implied warranties, including, but not limited to, the implied   ** warranties of merchantability and fitness for a particular purpose  ** are disclaimed. in no event shall the authors or contributors be    ** liable for any direct, indirect, incidental, special, exemplary, or ** consequential damages (including, but not limited to, procurement   ** of substitute goods or services; loss of use, data, or profits; or  ** business interruption) however caused and on any theory of          ** liability, whether in contract, strict liability, or tort           ** (including negligence or otherwise) arising in any way out of the   ** use of this software, even if advised of the possibility of such    ** damage.                                                             ************************************************************************   the following individuals contributed in part to the network time   protocol distribution version 4 and are acknowledged as authors of   this work.    1. [1]takao abe <takao_abe@xurb.jp> clock driver for jjy receivers    2. [2]mark andrews <mark_andrews@isc.org> leitch atomic clock       controller    3. [3]bernd altmeier <altmeier@atlsoft.de> hopf elektronik serial       line and pci-bus devices    4. [4]viraj bais <vbais@mailman1.intel.com> and [5]clayton kirkwood       <kirkwood@striderfm.intel.com> port to windowsnt 3.5    5. [6]michael barone <michael,barone@lmco.com> gpsvme fixes    6. [7]karl berry <karl@owl.hq.ileaf.com> syslog to file option    7. [8]greg brackley <greg.brackley@bigfoot.com> major rework of winnt       port. clean up recvbuf and iosignal code into separate modules.    8. [9]marc brett <marc.brett@westgeo.com> magnavox gps clock driver    9. [10]piete brooks <piete.brooks@cl.cam.ac.uk> msf clock driver,       trimble parse support   10. [11]nelson b bolyard <nelson@bolyard.me> update and complete       broadcast and crypto features in sntp   11. [12]jean-francois boudreault       <jean-francois.boudreault@viagenie.qc.ca> ipv6 support   12. [13]reg clemens <reg@dwf.com> oncore driver (current maintainer)   13. [14]steve clift <clift@ml.csiro.au> omega clock driver   14. [15]casey crellin <casey@csc.co.za> vxworks (tornado) port and       help with target configuration   15. [16]sven dietrich <sven_dietrich@trimble.com> palisade reference       clock driver, nt adj. residuals, integrated greg's winnt port.   16. [17]john a. dundas iii <dundas@salt.jpl.nasa.gov> apple a/ux port   17. [18]torsten duwe <duwe@immd4.informatik.uni-erlangen.de> linux       port   18. [19]dennis ferguson <dennis@mrbill.canet.ca> foundation code for       ntp version 2 as specified in rfc-1119   19. [20]john hay <jhay@icomtek.csir.co.za> ipv6 support and testing   20. [21]dave hart <davehart@davehart.com> general maintenance, windows       port interpolation rewrite   21. [22]claas hilbrecht <neoclock4x@linum.com> neoclock4x clock driver   22. [23]glenn hollinger <glenn@herald.usask.ca> goes clock driver   23. [24]mike iglesias <iglesias@uci.edu> dec alpha port   24. [25]jim jagielski <jim@jagubox.gsfc.nasa.gov> a/ux port   25. [26]jeff johnson <jbj@chatham.usdesign.com> massive prototyping       overhaul   26. [27]hans lambermont <hans.lambermont@nl.origin-it.com> or       [28]<h.lambermont@chello.nl> ntpsweep   27. [29]poul-henning kamp <phk@freebsd.org> oncore driver (original       author)   28. [30]frank kardel [31]<kardel (at) ntp (dot) org> parse <generic>       (driver 14 reference clocks), streams modules for parse, support       scripts, syslog cleanup, dynamic interface handling   29. [32]johannes maximilian kuehn <kuehn@ntp.org> rewrote sntp to       comply with ntpv4 specification, ntpq saveconfig   30. [33]william l. jones <jones@hermes.chpc.utexas.edu> rs/6000 aix       modifications, hpux modifications   31. [34]dave katz <dkatz@cisco.com> rs/6000 aix port   32. [35]craig leres <leres@ee.lbl.gov> 4.4bsd port, ppsclock, magnavox       gps clock driver   33. [36]george lindholm <lindholm@ucs.ubc.ca> sunos 5.1 port   34. [37]louis a. mamakos <louie@ni.umd.edu> md5-based authentication   35. [38]lars h. mathiesen <thorinn@diku.dk> adaptation of foundation       code for version 3 as specified in rfc-1305   36. [39]danny mayer <mayer@ntp.org>network i/o, windows port, code       maintenance   37. [40]david l. mills <mills@udel.edu> version 4 foundation,       precision kernel; clock drivers: 1, 3, 4, 6, 7, 11, 13, 18, 19,       22, 36   38. [41]wolfgang moeller <moeller@gwdgv1.dnet.gwdg.de> vms port   39. [42]jeffrey mogul <mogul@pa.dec.com> ntptrace utility   40. [43]tom moore <tmoore@fievel.daytonoh.ncr.com> i386 svr4 port   41. [44]kamal a mostafa <kamal@whence.com> sco openserver port   42. [45]derek mulcahy <derek@toybox.demon.co.uk> and [46]damon       hart-davis <d@hd.org> arcron msf clock driver   43. [47]rob neal <neal@ntp.org> bancomm refclock and config/parse code       maintenance   44. [48]rainer pruy <rainer.pruy@informatik.uni-erlangen.de>       monitoring/trap scripts, statistics file handling   45. [49]dirce richards <dirce@zk3.dec.com> digital unix v4.0 port   46. [50]wilfredo sanchez <wsanchez@apple.com> added support for       netinfo   47. [51]nick sayer <mrapple@quack.kfu.com> sunos streams modules   48. [52]jack sasportas <jack@innovativeinternet.com> saved a lot of       space on the stuff in the html/pic/ subdirectory   49. [53]ray schnitzler <schnitz@unipress.com> unixware1 port   50. [54]michael shields <shields@tembel.org> usno clock driver   51. [55]jeff steinman <jss@pebbles.jpl.nasa.gov> datum pts clock       driver   52. [56]harlan stenn <harlan@pfcs.com> gnu automake/autoconfigure       makeover, various other bits (see the changelog)   53. [57]kenneth stone <ken@sdd.hp.com> hp-ux port   54. [58]ajit thyagarajan <ajit@ee.udel.edu>ip multicast/anycast       support   55. [59]tomoaki tsuruoka <tsuruoka@nc.fukuoka-u.ac.jp>trak clock       driver   56. [60]brian utterback <brian.utterback@oracle.com> general codebase,       solaris issues   57. [61]loganaden velvindron <loganaden@gmail.com> sandboxing       (libseccomp) support   58. [62]paul a vixie <vixie@vix.com> truetime gps driver, generic       truetime clock driver   59. [63]ulrich windl <ulrich.windl@rz.uni-regensburg.de> corrected and       validated html documents according to the html dtd     *________________________________________________________________references   1. mailto:%20takao_abe@xurb.jp   2. mailto:%20mark_andrews@isc.org   3. mailto:%20altmeier@atlsoft.de   4. mailto:%20vbais@mailman1.intel.co   5. mailto:%20kirkwood@striderfm.intel.com   6. mailto:%20michael.barone@lmco.com   7. mailto:%20karl@owl.hq.ileaf.com   8. mailto:%20greg.brackley@bigfoot.com   9. mailto:%20marc.brett@westgeo.com  10. mailto:%20piete.brooks@cl.cam.ac.uk  11. mailto:%20nelson@bolyard.me  12. mailto:%20jean-francois.boudreault@viagenie.qc.ca  13. mailto:%20reg@dwf.com  14. mailto:%20clift@ml.csiro.au  15. mailto:%20casey@csc.co.za  16. mailto:%20sven_dietrich@trimble.com  17. mailto:%20dundas@salt.jpl.nasa.gov  18. mailto:%20duwe@immd4.informatik.uni-erlangen.de  19. mailto:%20dennis@mrbill.canet.ca  20. mailto:%20jhay@icomtek.csir.co.za  21. mailto:%20davehart@davehart.com  22. mailto:%20neoclock4x@linum.com  23. mailto:%20glenn@herald.usask.ca  24. mailto:%20iglesias@uci.edu  25. mailto:%20jagubox.gsfc.nasa.gov  26. mailto:%20jbj@chatham.usdesign.com  27. mailto:%20hans.lambermont@nl.origin-it.com  28. mailto:h.lambermont@chello.nl  29. mailto:%20phk@freebsd.org  30. http://www4.informatik.uni-erlangen.de/%7ekardel  31. mailto:%20kardel%20%28at%29%20ntp%20%28dot%29%20org  32. mailto:kuehn@ntp.org  33. mailto:%20jones@hermes.chpc.utexas.edu  34. mailto:%20dkatz@cisco.com  35. mailto:%20leres@ee.lbl.gov  36. mailto:%20lindholm@ucs.ubc.ca  37. mailto:%20louie@ni.umd.edu  38. mailto:%20thorinn@diku.dk  39. mailto:%20mayer@ntp.org  40. mailto:%20mills@udel.edu  41. mailto:%20moeller@gwdgv1.dnet.gwdg.de  42. mailto:%20mogul@pa.dec.com  43. mailto:%20tmoore@fievel.daytonoh.ncr.com  44. mailto:%20kamal@whence.com  45. mailto:%20derek@toybox.demon.co.uk  46. mailto:%20d@hd.org  47. mailto:%20neal@ntp.org  48. mailto:%20rainer.pruy@informatik.uni-erlangen.de  49. mailto:%20dirce@zk3.dec.com  50. mailto:%20wsanchez@apple.com  51. mailto:%20mrapple@quack.kfu.com  52. mailto:%20jack@innovativeinternet.com  53. mailto:%20schnitz@unipress.com  54. mailto:%20shields@tembel.org  55. mailto:%20pebbles.jpl.nasa.gov  56. mailto:%20harlan@pfcs.com  57. mailto:%20ken@sdd.hp.com  58. mailto:%20ajit@ee.udel.edu  59. mailto:%20tsuruoka@nc.fukuoka-u.ac.jp  60. mailto:%20brian.utterback@oracle.com  61. mailto:%20loganaden@gmail.com  62. mailto:%20vixie@vix.com  63. mailto:%20ulrich.windl@rz.uni-regensburg.de</div><div class="display_word">2.30. ntp This file is automatically generated from html/copyright.html  Copyright Notice   jpg "Clone me," says Dolly sheepishly.   Last update: 17-Jan-2015 00:16 UTC     *________________________________________________________________   The following copyright notice applies to all files collectively   called the Network Time Protocol Version 4 Distribution. Unless   specifically declared otherwise in an individual file, this entire   notice applies as if the text was explicitly included in the file.************************************************************************                                                                     ** Copyright (c) University of Delaware 1992-2015                      **                                                                     ** Permission to use, copy, modify, and distribute this software and   ** its documentation for any purpose with or without fee is hereby     ** granted, provided that the above copyright notice appears in all    ** copies and that both the copyright notice and this permission       ** notice appear in supporting documentation, and that the name        ** University of Delaware not be used in advertising or publicity      ** pertaining to distribution of the software without specific,        ** written prior permission. The University of Delaware makes no       ** representations about the suitability this software for any         ** purpose. It is provided "as is" without express or implied          ** warranty.                                                           **                                                                     ************************************************************************   Content starting in 2011 from Harlan Stenn, Danny Mayer, and Martin   Burnicki is:************************************************************************                                                                     ** Copyright (c) Network Time Foundation 2011-2015                     **                                                                     ** All Rights Reserved                                                 **                                                                     ** Redistribution and use in source and binary forms, with or without  ** modification, are permitted provided that the following conditions  ** are met:                                                            ** 1. Redistributions of source code must retain the above copyright   **    notice, this list of conditions and the following disclaimer.    ** 2. Redistributions in binary form must reproduce the above          **    copyright notice, this list of conditions and the following      **    disclaimer in the documentation and/or other materials provided  **    with the distribution.                                           **                                                                     ** THIS SOFTWARE IS PROVIDED BY THE AUTHORS ``AS IS'' AND ANY EXPRESS  ** OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED   ** WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE  ** ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE    ** LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR ** CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT   ** OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR  ** BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF          ** LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT           ** (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE   ** USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH    ** DAMAGE.                                                             ************************************************************************   The following individuals contributed in part to the Network Time   Protocol Distribution Version 4 and are acknowledged as authors of   this work.    1. [1]Takao Abe <takao_abe@xurb.jp> Clock driver for JJY receivers    2. [2]Mark Andrews <mark_andrews@isc.org> Leitch atomic clock       controller    3. [3]Bernd Altmeier <altmeier@atlsoft.de> hopf Elektronik serial       line and PCI-bus devices    4. [4]Viraj Bais <vbais@mailman1.intel.com> and [5]Clayton Kirkwood       <kirkwood@striderfm.intel.com> port to WindowsNT 3.5    5. [6]Michael Barone <michael,barone@lmco.com> GPSVME fixes    6. [7]Karl Berry <karl@owl.HQ.ileaf.com> syslog to file option    7. [8]Greg Brackley <greg.brackley@bigfoot.com> Major rework of WINNT       port. Clean up recvbuf and iosignal code into separate modules.    8. [9]Marc Brett <Marc.Brett@westgeo.com> Magnavox GPS clock driver    9. [10]Piete Brooks <Piete.Brooks@cl.cam.ac.uk> MSF clock driver,       Trimble PARSE support   10. [11]Nelson B Bolyard <nelson@bolyard.me> update and complete       broadcast and crypto features in sntp   11. [12]Jean-Francois Boudreault       <Jean-Francois.Boudreault@viagenie.qc.ca> IPv6 support   12. [13]Reg Clemens <reg@dwf.com> Oncore driver (Current maintainer)   13. [14]Steve Clift <clift@ml.csiro.au> OMEGA clock driver   14. [15]Casey Crellin <casey@csc.co.za> vxWorks (Tornado) port and       help with target configuration   15. [16]Sven Dietrich <sven_dietrich@trimble.com> Palisade reference       clock driver, NT adj. residuals, integrated Greg's Winnt port.   16. [17]John A. Dundas III <dundas@salt.jpl.nasa.gov> Apple A/UX port   17. [18]Torsten Duwe <duwe@immd4.informatik.uni-erlangen.de> Linux       port   18. [19]Dennis Ferguson <dennis@mrbill.canet.ca> foundation code for       NTP Version 2 as specified in RFC-1119   19. [20]John Hay <jhay@icomtek.csir.co.za> IPv6 support and testing   20. [21]Dave Hart <davehart@davehart.com> General maintenance, Windows       port interpolation rewrite   21. [22]Claas Hilbrecht <neoclock4x@linum.com> NeoClock4X clock driver   22. [23]Glenn Hollinger <glenn@herald.usask.ca> GOES clock driver   23. [24]Mike Iglesias <iglesias@uci.edu> DEC Alpha port   24. [25]Jim Jagielski <jim@jagubox.gsfc.nasa.gov> A/UX port   25. [26]Jeff Johnson <jbj@chatham.usdesign.com> massive prototyping       overhaul   26. [27]Hans Lambermont <Hans.Lambermont@nl.origin-it.com> or       [28]<H.Lambermont@chello.nl> ntpsweep   27. [29]Poul-Henning Kamp <phk@FreeBSD.ORG> Oncore driver (Original       author)   28. [30]Frank Kardel [31]<kardel (at) ntp (dot) org> PARSE <GENERIC>       (driver 14 reference clocks), STREAMS modules for PARSE, support       scripts, syslog cleanup, dynamic interface handling   29. [32]Johannes Maximilian Kuehn <kuehn@ntp.org> Rewrote sntp to       comply with NTPv4 specification, ntpq saveconfig   30. [33]William L. Jones <jones@hermes.chpc.utexas.edu> RS/6000 AIX       modifications, HPUX modifications   31. [34]Dave Katz <dkatz@cisco.com> RS/6000 AIX port   32. [35]Craig Leres <leres@ee.lbl.gov> 4.4BSD port, ppsclock, Magnavox       GPS clock driver   33. [36]George Lindholm <lindholm@ucs.ubc.ca> SunOS 5.1 port   34. [37]Louis A. Mamakos <louie@ni.umd.edu> MD5-based authentication   35. [38]Lars H. Mathiesen <thorinn@diku.dk> adaptation of foundation       code for Version 3 as specified in RFC-1305   36. [39]Danny Mayer <mayer@ntp.org>Network I/O, Windows Port, Code       Maintenance   37. [40]David L. Mills <mills@udel.edu> Version 4 foundation,       precision kernel; clock drivers: 1, 3, 4, 6, 7, 11, 13, 18, 19,       22, 36   38. [41]Wolfgang Moeller <moeller@gwdgv1.dnet.gwdg.de> VMS port   39. [42]Jeffrey Mogul <mogul@pa.dec.com> ntptrace utility   40. [43]Tom Moore <tmoore@fievel.daytonoh.ncr.com> i386 svr4 port   41. [44]Kamal A Mostafa <kamal@whence.com> SCO OpenServer port   42. [45]Derek Mulcahy <derek@toybox.demon.co.uk> and [46]Damon       Hart-Davis <d@hd.org> ARCRON MSF clock driver   43. [47]Rob Neal <neal@ntp.org> Bancomm refclock and config/parse code       maintenance   44. [48]Rainer Pruy <Rainer.Pruy@informatik.uni-erlangen.de>       monitoring/trap scripts, statistics file handling   45. [49]Dirce Richards <dirce@zk3.dec.com> Digital UNIX V4.0 port   46. [50]Wilfredo Sanchez <wsanchez@apple.com> added support for       NetInfo   47. [51]Nick Sayer <mrapple@quack.kfu.com> SunOS streams modules   48. [52]Jack Sasportas <jack@innovativeinternet.com> Saved a Lot of       space on the stuff in the html/pic/ subdirectory   49. [53]Ray Schnitzler <schnitz@unipress.com> Unixware1 port   50. [54]Michael Shields <shields@tembel.org> USNO clock driver   51. [55]Jeff Steinman <jss@pebbles.jpl.nasa.gov> Datum PTS clock       driver   52. [56]Harlan Stenn <harlan@pfcs.com> GNU automake/autoconfigure       makeover, various other bits (see the ChangeLog)   53. [57]Kenneth Stone <ken@sdd.hp.com> HP-UX port   54. [58]Ajit Thyagarajan <ajit@ee.udel.edu>IP multicast/anycast       support   55. [59]Tomoaki TSURUOKA <tsuruoka@nc.fukuoka-u.ac.jp>TRAK clock       driver   56. [60]Brian Utterback <brian.utterback@oracle.com> General codebase,       Solaris issues   57. [61]Loganaden Velvindron <loganaden@gmail.com> Sandboxing       (libseccomp) support   58. [62]Paul A Vixie <vixie@vix.com> TrueTime GPS driver, generic       TrueTime clock driver   59. [63]Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> corrected and       validated HTML documents according to the HTML DTD     *________________________________________________________________References   1. mailto:%20takao_abe@xurb.jp   2. mailto:%20mark_andrews@isc.org   3. mailto:%20altmeier@atlsoft.de   4. mailto:%20vbais@mailman1.intel.co   5. mailto:%20kirkwood@striderfm.intel.com   6. mailto:%20michael.barone@lmco.com   7. mailto:%20karl@owl.HQ.ileaf.com   8. mailto:%20greg.brackley@bigfoot.com   9. mailto:%20Marc.Brett@westgeo.com  10. mailto:%20Piete.Brooks@cl.cam.ac.uk  11. mailto:%20nelson@bolyard.me  12. mailto:%20Jean-Francois.Boudreault@viagenie.qc.ca  13. mailto:%20reg@dwf.com  14. mailto:%20clift@ml.csiro.au  15. mailto:%20casey@csc.co.za  16. mailto:%20Sven_Dietrich@trimble.COM  17. mailto:%20dundas@salt.jpl.nasa.gov  18. mailto:%20duwe@immd4.informatik.uni-erlangen.de  19. mailto:%20dennis@mrbill.canet.ca  20. mailto:%20jhay@icomtek.csir.co.za  21. mailto:%20davehart@davehart.com  22. mailto:%20neoclock4x@linum.com  23. mailto:%20glenn@herald.usask.ca  24. mailto:%20iglesias@uci.edu  25. mailto:%20jagubox.gsfc.nasa.gov  26. mailto:%20jbj@chatham.usdesign.com  27. mailto:%20Hans.Lambermont@nl.origin-it.com  28. mailto:H.Lambermont@chello.nl  29. mailto:%20phk@FreeBSD.ORG  30. http://www4.informatik.uni-erlangen.de/%7ekardel  31. mailto:%20kardel%20%28at%29%20ntp%20%28dot%29%20org  32. mailto:kuehn@ntp.org  33. mailto:%20jones@hermes.chpc.utexas.edu  34. mailto:%20dkatz@cisco.com  35. mailto:%20leres@ee.lbl.gov  36. mailto:%20lindholm@ucs.ubc.ca  37. mailto:%20louie@ni.umd.edu  38. mailto:%20thorinn@diku.dk  39. mailto:%20mayer@ntp.org  40. mailto:%20mills@udel.edu  41. mailto:%20moeller@gwdgv1.dnet.gwdg.de  42. mailto:%20mogul@pa.dec.com  43. mailto:%20tmoore@fievel.daytonoh.ncr.com  44. mailto:%20kamal@whence.com  45. mailto:%20derek@toybox.demon.co.uk  46. mailto:%20d@hd.org  47. mailto:%20neal@ntp.org  48. mailto:%20Rainer.Pruy@informatik.uni-erlangen.de  49. mailto:%20dirce@zk3.dec.com  50. mailto:%20wsanchez@apple.com  51. mailto:%20mrapple@quack.kfu.com  52. mailto:%20jack@innovativeinternet.com  53. mailto:%20schnitz@unipress.com  54. mailto:%20shields@tembel.org  55. mailto:%20pebbles.jpl.nasa.gov  56. mailto:%20harlan@pfcs.com  57. mailto:%20ken@sdd.hp.com  58. mailto:%20ajit@ee.udel.edu  59. mailto:%20tsuruoka@nc.fukuoka-u.ac.jp  60. mailto:%20brian.utterback@oracle.com  61. mailto:%20loganaden@gmail.com  62. mailto:%20vixie@vix.com  63. mailto:%20Ulrich.Windl@rz.uni-regensburg.de</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#openssh">2.31. OpenSSH</div><div class="search_word">2.31. openssh this file is part of the openssh software.the licences which components of this software fall under are asfollows.  first, we will summarize and say that all componentsare under a bsd licence, or a licence more free than that.openssh contains no gpl code.1)     * copyright (c) 1995 tatu ylonen <ylo@cs.hut.fi>, espoo, finland     *                    all rights reserved     *     * as far as i am concerned, the code i have written for this software     * can be used freely for any purpose.  any derived versions of this     * software must be clearly marked as such, and if the derived work is     * incompatible with the protocol description in the rfc file, it must be     * called by a name other than "ssh" or "secure shell".    [tatu continues]     *  however, i am not implying to give any licenses to any patents or     * copyrights held by third parties, and the software includes parts that     * are not under my direct control.  as far as i know, all included     * source code is used in accordance with the relevant license agreements     * and can be used freely for any purpose (the gnu license being the most     * restrictive); see below for details.    [however, none of that term is relevant at this point in time.  all of    these restrictively licenced software components which he talks about    have been removed from openssh, i.e.,     - rsa is no longer included, found in the openssl library     - idea is no longer included, its use is deprecated     - des is now external, in the openssl library     - gmp is no longer used, and instead we call bn code from openssl     - zlib is now external, in a library     - the make-ssh-known-hosts script is no longer included     - tss has been removed     - md5 is now external, in the openssl library     - rc4 support has been replaced with arc4 support from openssl     - blowfish is now external, in the openssl library    [the licence continues]    note that any information and cryptographic algorithms used in this    software are publicly available on the internet and at any major    bookstore, scientific library, and patent office worldwide.  more    information can be found e.g. at "http://www.cs.hut.fi/crypto".    the legal status of this program is some combination of all these    permissions and restrictions.  use only at your own responsibility.    you will be responsible for any legal consequences yourself; i am not    making any claims whether possessing or using this is legal or not in    your country, and i am not taking any responsibility on your behalf.                no warranty    because the program is licensed free of charge, there is no warranty    for the program, to the extent permitted by applicable law.  except when    otherwise stated in writing the copyright holders and/or other parties    provide the program "as is" without warranty of any kind, either expressed    or implied, including, but not limited to, the implied warranties of    merchantability and fitness for a particular purpose.  the entire risk as    to the quality and performance of the program is with you.  should the    program prove defective, you assume the cost of all necessary servicing,    repair or correction.    in no event unless required by applicable law or agreed to in writing    will any copyright holder, or any other party who may modify and/or    redistribute the program as permitted above, be liable to you for damages,    including any general, special, incidental or consequential damages arising    out of the use or inability to use the program (including but not limited    to loss of data or data being rendered inaccurate or losses sustained by    you or third parties or a failure of the program to operate with any other    programs), even if such holder or other party has been advised of the    possibility of such damages.2)    the 32-bit crc compensation attack detector in deattack.c was    contributed by core sdi s.a. under a bsd-style license.     * cryptographic attack detector for ssh - source code     *     * copyright (c) 1998 core sdi s.a., buenos aires, argentina.     *     * all rights reserved. redistribution and use in source and binary     * forms, with or without modification, are permitted provided that     * this copyright notice is retained.     *     * this software is provided ``as is'' and any express or implied     * warranties are disclaimed. in no event shall core sdi s.a. be     * liable for any direct, indirect, incidental, special, exemplary or     * consequential damages resulting from the use or misuse of this     * software.     *     * ariel futoransky <futo@core-sdi.com>     * < http://www.core-sdi.com>3)    ssh-keyscan was contributed by david mazieres under a bsd-style    license.     * copyright 1995, 1996 by david mazieres <dm@lcs.mit.edu>.     *     * modification and redistribution in source and binary forms is     * permitted provided that due credit is given to the author and the     * openbsd project by leaving this copyright notice intact.4)    the rijndael implementation by vincent rijmen, antoon bosselaers    and paulo barreto is in the public domain and distributed    with the following license:     * @version 3.0 (december 2000)     *     * optimised ansi c code for the rijndael cipher (now aes)     *     * @author vincent rijmen <vincent.rijmen@esat.kuleuven.ac.be>     * @author antoon bosselaers <antoon.bosselaers@esat.kuleuven.ac.be>     * @author paulo barreto <paulo.barreto@terra.com.br>     *     * this code is hereby placed in the public domain.     *     * this software is provided by the authors ''as is'' and any express     * or implied warranties, including, but not limited to, the implied     * warranties of merchantability and fitness for a particular purpose     * are disclaimed.  in no event shall the authors or contributors be     * liable for any direct, indirect, incidental, special, exemplary, or     * consequential damages (including, but not limited to, procurement of     * substitute goods or services; loss of use, data, or profits; or     * business interruption) however caused and on any theory of liability,     * whether in contract, strict liability, or tort (including negligence     * or otherwise) arising in any way out of the use of this software,     * even if advised of the possibility of such damage.5)    one component of the ssh source code is under a 3-clause bsd license,    held by the university of california, since we pulled these parts from    original berkeley code.     * copyright (c) 1983, 1990, 1992, 1993, 1995     *      the regents of the university of california.  all rights reserved.     *     * redistribution and use in source and binary forms, with or without     * modification, are permitted provided that the following conditions     * are met:     * 1. redistributions of source code must retain the above copyright     *    notice, this list of conditions and the following disclaimer.     * 2. redistributions in binary form must reproduce the above copyright     *    notice, this list of conditions and the following disclaimer in the     *    documentation and/or other materials provided with the distribution.     * 3. neither the name of the university nor the names of its contributors     *    may be used to endorse or promote products derived from this software     *    without specific prior written permission.     *     * this software is provided by the regents and contributors ``as is'' and     * any express or implied warranties, including, but not limited to, the     * implied warranties of merchantability and fitness for a particular purpose     * are disclaimed.  in no event shall the regents or contributors be liable     * for any direct, indirect, incidental, special, exemplary, or consequential     * damages (including, but not limited to, procurement of substitute goods     * or services; loss of use, data, or profits; or business interruption)     * however caused and on any theory of liability, whether in contract, strict     * liability, or tort (including negligence or otherwise) arising in any way     * out of the use of this software, even if advised of the possibility of     * such damage.6)    remaining components of the software are provided under a standard    2-term bsd licence with the following names as copyright holders:    markus friedl    theo de raadt    niels provos    dug song    aaron campbell    damien miller    kevin steves    daniel kouril    wesley griffin    per allansson    nils nordman    simon wilkinson    portable openssh additionally includes code from the following copyright    holders, also under the 2-term bsd license:    ben lindstrom    tim rice    andre lucas    chris adams    corinna vinschen    cray inc.    denis parker    gert doering    jakob schlyter    jason downs    juha yrjola    michael stone    networks associates technology, inc.    solar designer    todd c. miller    wayne schroeder    william jones    darren tucker    sun microsystems    the sco group    daniel walsh    red hat, inc    simon vallet / genoscope     * redistribution and use in source and binary forms, with or without     * modification, are permitted provided that the following conditions     * are met:     * 1. redistributions of source code must retain the above copyright     *    notice, this list of conditions and the following disclaimer.     * 2. redistributions in binary form must reproduce the above copyright     *    notice, this list of conditions and the following disclaimer in the     *    documentation and/or other materials provided with the distribution.     *     * this software is provided by the author ``as is'' and any express or     * implied warranties, including, but not limited to, the implied warranties     * of merchantability and fitness for a particular purpose are disclaimed.     * in no event shall the author be liable for any direct, indirect,     * incidental, special, exemplary, or consequential damages (including, but     * not limited to, procurement of substitute goods or services; loss of use,     * data, or profits; or business interruption) however caused and on any     * theory of liability, whether in contract, strict liability, or tort     * (including negligence or otherwise) arising in any way out of the use of     * this software, even if advised of the possibility of such damage.8) portable openssh contains the following additional licenses:    a) md5crypt.c, md5crypt.h     * "the beer-ware license" (revision 42):     * <phk@login.dknet.dk> wrote this file.  as long as you retain this     * notice you can do whatever you want with this stuff. if we meet     * some day, and you think this stuff is worth it, you can buy me a     * beer in return.   poul-henning kamp    b) snprintf replacement    * copyright patrick powell 1995    * this code is based on code written by patrick powell    * (papowell@astart.com) it may be used for any purpose as long as this    * notice remains intact on all source code distributions    c) compatibility code (openbsd-compat)       apart from the previously mentioned licenses, various pieces of code       in the openbsd-compat/ subdirectory are licensed as follows:       some code is licensed under a 3-term bsd license, to the following       copyright holders:    todd c. miller    theo de raadt    damien miller    eric p. allman    the regents of the university of california    constantin s. svintsoff    * redistribution and use in source and binary forms, with or without    * modification, are permitted provided that the following conditions    * are met:    * 1. redistributions of source code must retain the above copyright    *    notice, this list of conditions and the following disclaimer.    * 2. redistributions in binary form must reproduce the above copyright    *    notice, this list of conditions and the following disclaimer in the    *    documentation and/or other materials provided with the distribution.    * 3. neither the name of the university nor the names of its contributors    *    may be used to endorse or promote products derived from this software    *    without specific prior written permission.    *    * this software is provided by the regents and contributors ``as is'' and    * any express or implied warranties, including, but not limited to, the    * implied warranties of merchantability and fitness for a particular purpose    * are disclaimed.  in no event shall the regents or contributors be liable    * for any direct, indirect, incidental, special, exemplary, or consequential    * damages (including, but not limited to, procurement of substitute goods    * or services; loss of use, data, or profits; or business interruption)    * however caused and on any theory of liability, whether in contract, strict    * liability, or tort (including negligence or otherwise) arising in any way    * out of the use of this software, even if advised of the possibility of    * such damage.       some code is licensed under an isc-style license, to the following       copyright holders:    internet software consortium.    todd c. miller    reyk floeter    chad mynhier    * permission to use, copy, modify, and distribute this software for any    * purpose with or without fee is hereby granted, provided that the above    * copyright notice and this permission notice appear in all copies.    *    * the software is provided "as is" and todd c. miller disclaims all    * warranties with regard to this software including all implied warranties    * of merchantability and fitness. in no event shall todd c. miller be liable    * for any special, direct, indirect, or consequential damages or any damages    * whatsoever resulting from loss of use, data or profits, whether in an action    * of contract, negligence or other tortious action, arising out of or in    * connection with the use or performance of this software.       some code is licensed under a mit-style license to the following       copyright holders:    free software foundation, inc.    * permission is hereby granted, free of charge, to any person obtaining a  *    * copy of this software and associated documentation files (the            *    * "software"), to deal in the software without restriction, including      *    * without limitation the rights to use, copy, modify, merge, publish,      *    * distribute, distribute with modifications, sublicense, and/or sell       *    * copies of the software, and to permit persons to whom the software is    *    * furnished to do so, subject to the following conditions:                 *    *                                                                          *    * the above copyright notice and this permission notice shall be included  *    * in all copies or substantial portions of the software.                   *    *                                                                          *    * the software is provided "as is", without warranty of any kind, express  *    * or implied, including but not limited to the warranties of               *    * merchantability, fitness for a particular purpose and noninfringement.   *    * in no event shall the above copyright holders be liable for any claim,   *    * damages or other liability, whether in an action of contract, tort or    *    * otherwise, arising from, out of or in connection with the software or    *    * the use or other dealings in the software.                               *    *                                                                          *    * except as contained in this notice, the name(s) of the above copyright   *    * holders shall not be used in advertising or otherwise to promote the     *    * sale, use or other dealings in this software without prior written       *    * authorization.                                                           *    ****************************************************************************/</div><div class="display_word">2.31. OpenSSH This file is part of the OpenSSH software.The licences which components of this software fall under are asfollows.  First, we will summarize and say that all componentsare under a BSD licence, or a licence more free than that.OpenSSH contains no GPL code.1)     * Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland     *                    All rights reserved     *     * As far as I am concerned, the code I have written for this software     * can be used freely for any purpose.  Any derived versions of this     * software must be clearly marked as such, and if the derived work is     * incompatible with the protocol description in the RFC file, it must be     * called by a name other than "ssh" or "Secure Shell".    [Tatu continues]     *  However, I am not implying to give any licenses to any patents or     * copyrights held by third parties, and the software includes parts that     * are not under my direct control.  As far as I know, all included     * source code is used in accordance with the relevant license agreements     * and can be used freely for any purpose (the GNU license being the most     * restrictive); see below for details.    [However, none of that term is relevant at this point in time.  All of    these restrictively licenced software components which he talks about    have been removed from OpenSSH, i.e.,     - RSA is no longer included, found in the OpenSSL library     - IDEA is no longer included, its use is deprecated     - DES is now external, in the OpenSSL library     - GMP is no longer used, and instead we call BN code from OpenSSL     - Zlib is now external, in a library     - The make-ssh-known-hosts script is no longer included     - TSS has been removed     - MD5 is now external, in the OpenSSL library     - RC4 support has been replaced with ARC4 support from OpenSSL     - Blowfish is now external, in the OpenSSL library    [The licence continues]    Note that any information and cryptographic algorithms used in this    software are publicly available on the Internet and at any major    bookstore, scientific library, and patent office worldwide.  More    information can be found e.g. at "http://www.cs.hut.fi/crypto".    The legal status of this program is some combination of all these    permissions and restrictions.  Use only at your own responsibility.    You will be responsible for any legal consequences yourself; I am not    making any claims whether possessing or using this is legal or not in    your country, and I am not taking any responsibility on your behalf.                NO WARRANTY    BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY    FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN    OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES    PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED    OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF    MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS    TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE    PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,    REPAIR OR CORRECTION.    IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING    WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR    REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,    INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING    OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED    TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY    YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER    PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE    POSSIBILITY OF SUCH DAMAGES.2)    The 32-bit CRC compensation attack detector in deattack.c was    contributed by CORE SDI S.A. under a BSD-style license.     * Cryptographic attack detector for ssh - source code     *     * Copyright (c) 1998 CORE SDI S.A., Buenos Aires, Argentina.     *     * All rights reserved. Redistribution and use in source and binary     * forms, with or without modification, are permitted provided that     * this copyright notice is retained.     *     * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED     * WARRANTIES ARE DISCLAIMED. IN NO EVENT SHALL CORE SDI S.A. BE     * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY OR     * CONSEQUENTIAL DAMAGES RESULTING FROM THE USE OR MISUSE OF THIS     * SOFTWARE.     *     * Ariel Futoransky <futo@core-sdi.com>     * < http://www.core-sdi.com>3)    ssh-keyscan was contributed by David Mazieres under a BSD-style    license.     * Copyright 1995, 1996 by David Mazieres <dm@lcs.mit.edu>.     *     * Modification and redistribution in source and binary forms is     * permitted provided that due credit is given to the author and the     * OpenBSD project by leaving this copyright notice intact.4)    The Rijndael implementation by Vincent Rijmen, Antoon Bosselaers    and Paulo Barreto is in the public domain and distributed    with the following license:     * @version 3.0 (December 2000)     *     * Optimised ANSI C code for the Rijndael cipher (now AES)     *     * @author Vincent Rijmen <vincent.rijmen@esat.kuleuven.ac.be>     * @author Antoon Bosselaers <antoon.bosselaers@esat.kuleuven.ac.be>     * @author Paulo Barreto <paulo.barreto@terra.com.br>     *     * This code is hereby placed in the public domain.     *     * THIS SOFTWARE IS PROVIDED BY THE AUTHORS ''AS IS'' AND ANY EXPRESS     * OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED     * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE     * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE     * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR     * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF     * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR     * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,     * WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE     * OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,     * EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.5)    One component of the ssh source code is under a 3-clause BSD license,    held by the University of California, since we pulled these parts from    original Berkeley code.     * Copyright (c) 1983, 1990, 1992, 1993, 1995     *      The Regents of the University of California.  All rights reserved.     *     * Redistribution and use in source and binary forms, with or without     * modification, are permitted provided that the following conditions     * are met:     * 1. Redistributions of source code must retain the above copyright     *    notice, this list of conditions and the following disclaimer.     * 2. Redistributions in binary form must reproduce the above copyright     *    notice, this list of conditions and the following disclaimer in the     *    documentation and/or other materials provided with the distribution.     * 3. Neither the name of the University nor the names of its contributors     *    may be used to endorse or promote products derived from this software     *    without specific prior written permission.     *     * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND     * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE     * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE     * ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE     * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL     * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS     * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)     * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT     * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY     * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF     * SUCH DAMAGE.6)    Remaining components of the software are provided under a standard    2-term BSD licence with the following names as copyright holders:    Markus Friedl    Theo de Raadt    Niels Provos    Dug Song    Aaron Campbell    Damien Miller    Kevin Steves    Daniel Kouril    Wesley Griffin    Per Allansson    Nils Nordman    Simon Wilkinson    Portable OpenSSH additionally includes code from the following copyright    holders, also under the 2-term BSD license:    Ben Lindstrom    Tim Rice    Andre Lucas    Chris Adams    Corinna Vinschen    Cray Inc.    Denis Parker    Gert Doering    Jakob Schlyter    Jason Downs    Juha Yrjola    Michael Stone    Networks Associates Technology, Inc.    Solar Designer    Todd C. Miller    Wayne Schroeder    William Jones    Darren Tucker    Sun Microsystems    The SCO Group    Daniel Walsh    Red Hat, Inc    Simon Vallet / Genoscope     * Redistribution and use in source and binary forms, with or without     * modification, are permitted provided that the following conditions     * are met:     * 1. Redistributions of source code must retain the above copyright     *    notice, this list of conditions and the following disclaimer.     * 2. Redistributions in binary form must reproduce the above copyright     *    notice, this list of conditions and the following disclaimer in the     *    documentation and/or other materials provided with the distribution.     *     * THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR     * IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES     * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.     * IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,     * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT     * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,     * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY     * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT     * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF     * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.8) Portable OpenSSH contains the following additional licenses:    a) md5crypt.c, md5crypt.h     * "THE BEER-WARE LICENSE" (Revision 42):     * <phk@login.dknet.dk> wrote this file.  As long as you retain this     * notice you can do whatever you want with this stuff. If we meet     * some day, and you think this stuff is worth it, you can buy me a     * beer in return.   Poul-Henning Kamp    b) snprintf replacement    * Copyright Patrick Powell 1995    * This code is based on code written by Patrick Powell    * (papowell@astart.com) It may be used for any purpose as long as this    * notice remains intact on all source code distributions    c) Compatibility code (openbsd-compat)       Apart from the previously mentioned licenses, various pieces of code       in the openbsd-compat/ subdirectory are licensed as follows:       Some code is licensed under a 3-term BSD license, to the following       copyright holders:    Todd C. Miller    Theo de Raadt    Damien Miller    Eric P. Allman    The Regents of the University of California    Constantin S. Svintsoff    * Redistribution and use in source and binary forms, with or without    * modification, are permitted provided that the following conditions    * are met:    * 1. Redistributions of source code must retain the above copyright    *    notice, this list of conditions and the following disclaimer.    * 2. Redistributions in binary form must reproduce the above copyright    *    notice, this list of conditions and the following disclaimer in the    *    documentation and/or other materials provided with the distribution.    * 3. Neither the name of the University nor the names of its contributors    *    may be used to endorse or promote products derived from this software    *    without specific prior written permission.    *    * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND    * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE    * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE    * ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE    * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL    * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS    * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)    * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT    * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY    * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF    * SUCH DAMAGE.       Some code is licensed under an ISC-style license, to the following       copyright holders:    Internet Software Consortium.    Todd C. Miller    Reyk Floeter    Chad Mynhier    * Permission to use, copy, modify, and distribute this software for any    * purpose with or without fee is hereby granted, provided that the above    * copyright notice and this permission notice appear in all copies.    *    * THE SOFTWARE IS PROVIDED "AS IS" AND TODD C. MILLER DISCLAIMS ALL    * WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES    * OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL TODD C. MILLER BE LIABLE    * FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES    * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION    * OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN    * CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.       Some code is licensed under a MIT-style license to the following       copyright holders:    Free Software Foundation, Inc.    * Permission is hereby granted, free of charge, to any person obtaining a  *    * copy of this software and associated documentation files (the            *    * "Software"), to deal in the Software without restriction, including      *    * without limitation the rights to use, copy, modify, merge, publish,      *    * distribute, distribute with modifications, sublicense, and/or sell       *    * copies of the Software, and to permit persons to whom the Software is    *    * furnished to do so, subject to the following conditions:                 *    *                                                                          *    * The above copyright notice and this permission notice shall be included  *    * in all copies or substantial portions of the Software.                   *    *                                                                          *    * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS  *    * OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF               *    * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.   *    * IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,   *    * DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR    *    * OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR    *    * THE USE OR OTHER DEALINGS IN THE SOFTWARE.                               *    *                                                                          *    * Except as contained in this notice, the name(s) of the above copyright   *    * holders shall not be used in advertising or otherwise to promote the     *    * sale, use or other dealings in this Software without prior written       *    * authorization.                                                           *    ****************************************************************************/</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#openssl">2.32. OpenSSL</div><div class="search_word">2.32. openssl license issues  ==============  the openssl toolkit stays under a dual license, i.e. both the conditions of  the openssl license and the original ssleay license apply to the toolkit.  see below for the actual license texts. actually both licenses are bsd-style  open source licenses. in case of any license issues related to openssl  please contact openssl-core@openssl.org.  openssl license  ---------------/* ==================================================================== * copyright (c) 1998-2011 the openssl project.  all rights reserved. * * redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. redistributions of source code must retain the above copyright *    notice, this list of conditions and the following disclaimer. * * 2. redistributions in binary form must reproduce the above copyright *    notice, this list of conditions and the following disclaimer in *    the documentation and/or other materials provided with the *    distribution. * * 3. all advertising materials mentioning features or use of this *    software must display the following acknowledgment: *    "this product includes software developed by the openssl project *    for use in the openssl toolkit. (http://www.openssl.org/)" * * 4. the names "openssl toolkit" and "openssl project" must not be used to *    endorse or promote products derived from this software without *    prior written permission. for written permission, please contact *    openssl-core@openssl.org. * * 5. products derived from this software may not be called "openssl" *    nor may "openssl" appear in their names without prior written *    permission of the openssl project. * * 6. redistributions of any form whatsoever must retain the following *    acknowledgment: *    "this product includes software developed by the openssl project *    for use in the openssl toolkit (http://www.openssl.org/)" * * this software is provided by the openssl project ``as is'' and any * expressed or implied warranties, including, but not limited to, the * implied warranties of merchantability and fitness for a particular * purpose are disclaimed.  in no event shall the openssl project or * its contributors be liable for any direct, indirect, incidental, * special, exemplary, or consequential damages (including, but * not limited to, procurement of substitute goods or services; * loss of use, data, or profits; or business interruption) * however caused and on any theory of liability, whether in contract, * strict liability, or tort (including negligence or otherwise) * arising in any way out of the use of this software, even if advised * of the possibility of such damage. * ==================================================================== * * this product includes cryptographic software written by eric young * (eay@cryptsoft.com).  this product includes software written by tim * hudson (tjh@cryptsoft.com). * */ original ssleay license -----------------------/* copyright (c) 1995-1998 eric young (eay@cryptsoft.com) * all rights reserved. * * this package is an ssl implementation written * by eric young (eay@cryptsoft.com). * the implementation was written so as to conform with netscapes ssl. * * this library is free for commercial and non-commercial use as long as * the following conditions are aheared to.  the following conditions * apply to all code found in this distribution, be it the rc4, rsa, * lhash, des, etc., code; not just the ssl code.  the ssl documentation * included with this distribution is covered by the same copyright terms * except that the holder is tim hudson (tjh@cryptsoft.com). * * copyright remains eric young's, and as such any copyright notices in * the code are not to be removed. * if this package is used in a product, eric young should be given attribution * as the author of the parts of the library used. * this can be in the form of a textual message at program startup or * in documentation (online or textual) provided with the package. * * redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. redistributions of source code must retain the copyright *    notice, this list of conditions and the following disclaimer. * 2. redistributions in binary form must reproduce the above copyright *    notice, this list of conditions and the following disclaimer in the *    documentation and/or other materials provided with the distribution. * 3. all advertising materials mentioning features or use of this software *    must display the following acknowledgement: *    "this product includes cryptographic software written by *     eric young (eay@cryptsoft.com)" *    the word 'cryptographic' can be left out if the rouines from the library *    being used are not cryptographic related :-). * 4. if you include any windows specific code (or a derivative thereof) from *    the apps directory (application code) you must include an acknowledgement: *    "this product includes software written by tim hudson (tjh@cryptsoft.com)" * * this software is provided by eric young ``as is'' and * any express or implied warranties, including, but not limited to, the * implied warranties of merchantability and fitness for a particular purpose * are disclaimed.  in no event shall the author or contributors be liable * for any direct, indirect, incidental, special, exemplary, or consequential * damages (including, but not limited to, procurement of substitute goods * or services; loss of use, data, or profits; or business interruption) * however caused and on any theory of liability, whether in contract, strict * liability, or tort (including negligence or otherwise) arising in any way * out of the use of this software, even if advised of the possibility of * such damage. * * the licence and distribution terms for any publically available version or * derivative of this code cannot be changed.  i.e. this code cannot simply be * copied and put under another distribution licence * [including the gnu public licence.] */</div><div class="display_word">2.32. OpenSSL LICENSE ISSUES  ==============  The OpenSSL toolkit stays under a dual license, i.e. both the conditions of  the OpenSSL License and the original SSLeay license apply to the toolkit.  See below for the actual license texts. Actually both licenses are BSD-style  Open Source licenses. In case of any license issues related to OpenSSL  please contact openssl-core@openssl.org.  OpenSSL License  ---------------/* ==================================================================== * Copyright (c) 1998-2011 The OpenSSL Project.  All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of source code must retain the above copyright *    notice, this list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright *    notice, this list of conditions and the following disclaimer in *    the documentation and/or other materials provided with the *    distribution. * * 3. All advertising materials mentioning features or use of this *    software must display the following acknowledgment: *    "This product includes software developed by the OpenSSL Project *    for use in the OpenSSL Toolkit. (http://www.openssl.org/)" * * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to *    endorse or promote products derived from this software without *    prior written permission. For written permission, please contact *    openssl-core@openssl.org. * * 5. Products derived from this software may not be called "OpenSSL" *    nor may "OpenSSL" appear in their names without prior written *    permission of the OpenSSL Project. * * 6. Redistributions of any form whatsoever must retain the following *    acknowledgment: *    "This product includes software developed by the OpenSSL Project *    for use in the OpenSSL Toolkit (http://www.openssl.org/)" * * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR * PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE OpenSSL PROJECT OR * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED * OF THE POSSIBILITY OF SUCH DAMAGE. * ==================================================================== * * This product includes cryptographic software written by Eric Young * (eay@cryptsoft.com).  This product includes software written by Tim * Hudson (tjh@cryptsoft.com). * */ Original SSLeay License -----------------------/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) * All rights reserved. * * This package is an SSL implementation written * by Eric Young (eay@cryptsoft.com). * The implementation was written so as to conform with Netscapes SSL. * * This library is free for commercial and non-commercial use as long as * the following conditions are aheared to.  The following conditions * apply to all code found in this distribution, be it the RC4, RSA, * lhash, DES, etc., code; not just the SSL code.  The SSL documentation * included with this distribution is covered by the same copyright terms * except that the holder is Tim Hudson (tjh@cryptsoft.com). * * Copyright remains Eric Young's, and as such any Copyright notices in * the code are not to be removed. * If this package is used in a product, Eric Young should be given attribution * as the author of the parts of the library used. * This can be in the form of a textual message at program startup or * in documentation (online or textual) provided with the package. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the copyright *    notice, this list of conditions and the following disclaimer. * 2. Redistributions in binary form must reproduce the above copyright *    notice, this list of conditions and the following disclaimer in the *    documentation and/or other materials provided with the distribution. * 3. All advertising materials mentioning features or use of this software *    must display the following acknowledgement: *    "This product includes cryptographic software written by *     Eric Young (eay@cryptsoft.com)" *    The word 'cryptographic' can be left out if the rouines from the library *    being used are not cryptographic related :-). * 4. If you include any Windows specific code (or a derivative thereof) from *    the apps directory (application code) you must include an acknowledgement: *    "This product includes software written by Tim Hudson (tjh@cryptsoft.com)" * * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * * The licence and distribution terms for any publically available version or * derivative of this code cannot be changed.  i.e. this code cannot simply be * copied and put under another distribution licence * [including the GNU Public Licence.] */</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#powertip">2.33. PowerTip</div><div class="search_word">2.33. powertip copyright (c) 2018 steven benner (http://stevenbenner.com/)permission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the"software"), to deal in the software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the software, and topermit persons to whom the software is furnished to do so, subject tothe following conditions:the above copyright notice and this permission notice shall beincluded in all copies or substantial portions of the software.the software is provided "as is", without warranty of any kind,express or implied, including but not limited to the warranties ofmerchantability, fitness for a particular purpose andnoninfringement. in no event shall the authors or copyright holders beliable for any claim, damages or other liability, whether in an actionof contract, tort or otherwise, arising from, out of or in connectionwith the software or the use or other dealings in the software.</div><div class="display_word">2.33. PowerTip Copyright (c) 2018 Steven Benner (http://stevenbenner.com/)Permission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the"Software"), to deal in the Software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the Software, and topermit persons to whom the Software is furnished to do so, subject tothe following conditions:The above copyright notice and this permission notice shall beincluded in all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BELIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTIONOF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTIONWITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#ptpd">2.34. PTPd</div><div class="search_word">2.34. ptpd copyright (c) 2015      wojciech owczarek.copyright (c) 2014      perseus telecom.copyright (c) 2013-2014 harlan stenn,                        george n. neville-neil,                        wojciech owczarek,                        jan breuer.copyright (c) 2011-2012 george v. neville-neil,                        steven kreuzer,                        martin burnicki,                        jan breuer,                        wojciech owczarek,                        gael mace,                        alexandre van kempen,                        inaqui delgado,                        rick ratzel,                        national instruments.copyright (c) 2009-2010 george v. neville-neil,                        steven kreuzer,                        martin burnicki,                        jan breuer,                        gael mace,                        alexandre van kempen.copyright (c) 2005-2008 kendall correll, aidan williamsall rights reservedredistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions aremet:1. redistributions of source code must retain the above copyright notice,   this list of conditions and the following disclaimer.2. redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.this software is provided by the authors ``as is'' and any express orimplied warranties, including, but not limited to, the impliedwarranties of merchantability and fitness for a particular purpose aredisclaimed. in no event shall the authors or contributors be liablefor any direct, indirect, incidental, special, exemplary, orconsequential damages (including, but not limited to, procurement ofsubstitute goods or services; loss of use, data, or profits; orbusiness interruption) however caused and on any theory of liability,whether in contract, strict liability, or tort (including negligenceor otherwise) arising in any way out of the use of this software, evenif advised of the possibility of such damage.</div><div class="display_word">2.34. PTPd Copyright (c) 2015      Wojciech Owczarek.Copyright (c) 2014      Perseus Telecom.Copyright (c) 2013-2014 Harlan Stenn,                        George N. Neville-Neil,                        Wojciech Owczarek,                        Jan Breuer.Copyright (c) 2011-2012 George V. Neville-Neil,                        Steven Kreuzer,                        Martin Burnicki,                        Jan Breuer,                        Wojciech Owczarek,                        Gael Mace,                        Alexandre Van Kempen,                        Inaqui Delgado,                        Rick Ratzel,                        National Instruments.Copyright (c) 2009-2010 George V. Neville-Neil,                        Steven Kreuzer,                        Martin Burnicki,                        Jan Breuer,                        Gael Mace,                        Alexandre Van Kempen.Copyright (c) 2005-2008 Kendall Correll, Aidan WilliamsAll Rights ReservedRedistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditions aremet:1. Redistributions of source code must retain the above copyright notice,   this list of conditions and the following disclaimer.2. Redistributions in binary form must reproduce the above copyright   notice, this list of conditions and the following disclaimer in the   documentation and/or other materials provided with the distribution.THIS SOFTWARE IS PROVIDED BY THE AUTHORS ``AS IS'' AND ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLEFOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OFSUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; ORBUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCEOR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVENIF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#tablednd-plug-in-for-jquery">2.35. TableDnD plug-in for JQuery</div><div class="search_word">2.35. tablednd plug-in for jquery copyright (c) denis howlett <denish@isocra.com>copyright 2012 nick lombard - nickl- and other contributorshttps://github.com/isocra/tabledndpermission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the"software"), to deal in the software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the software, and topermit persons to whom the software is furnished to do so, subject tothe following conditions:the above copyright notice and this permission notice shall beincluded in all copies or substantial portions of the software.the software is provided "as is", without warranty of any kind,express or implied, including but not limited to the warranties ofmerchantability, fitness for a particular purpose andnoninfringement. in no event shall the authors or copyright holders beliable for any claim, damages or other liability, whether in an actionof contract, tort or otherwise, arising from, out of or in connectionwith the software or the use or other dealings in the software.</div><div class="display_word">2.35. TableDnD plug-in for JQuery Copyright (c) Denis Howlett <denish@isocra.com>Copyright 2012 Nick Lombard - nickl- and other contributorshttps://github.com/isocra/TableDnDPermission is hereby granted, free of charge, to any person obtaininga copy of this software and associated documentation files (the"Software"), to deal in the Software without restriction, includingwithout limitation the rights to use, copy, modify, merge, publish,distribute, sublicense, and/or sell copies of the Software, and topermit persons to whom the Software is furnished to do so, subject tothe following conditions:The above copyright notice and this permission notice shall beincluded in all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ANDNONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BELIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTIONOF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTIONWITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#the-html5-shiv">2.36. The HTML5 Shiv</div><div class="search_word">2.36. the html5 shiv copyright (c) 2014 alexander farkas (afarkas).this software is licensed under a dual license system (mit or gpl version 2).this means you are free to choose with which of both licenses (mit orgpl version 2) you want to use this library.</div><div class="display_word">2.36. The HTML5 Shiv Copyright (c) 2014 Alexander Farkas (aFarkas).This software is licensed under a dual license system (MIT or GPL version 2).This means you are free to choose with which of both licenses (MIT orGPL version 2) you want to use this library.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#unbound">2.37. Unbound</div><div class="search_word">2.37. unbound copyright (c) 2007, nlnet labs. all rights reserved.this software is open source.redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditionsare met:redistributions of source code must retain the above copyright notice,this list of conditions and the following disclaimer.redistributions in binary form must reproduce the above copyright notice,this list of conditions and the following disclaimer in the documentationand/or other materials provided with the distribution.neither the name of the nlnet labs nor the names of its contributors maybe used to endorse or promote products derived from this software withoutspecific prior written permission.this software is provided by the copyright holders and contributorsas is and any express or implied warranties, including, but notlimited to, the implied warranties of merchantability and fitness fora particular purpose are disclaimed. in no event shall the copyrightholder or contributors be liable for any direct, indirect, incidental,special, exemplary, or consequential damages (including, but not limitedto, procurement of substitute goods or services; loss of use, data, orprofits; or business interruption) however caused and on any theory ofliability, whether in contract, strict liability, or tort (includingnegligence or otherwise) arising in any way out of the use of thissoftware, even if advised of the possibility of such damage.</div><div class="display_word">2.37. Unbound Copyright (c) 2007, NLnet Labs. All rights reserved.This software is open source.Redistribution and use in source and binary forms, with or withoutmodification, are permitted provided that the following conditionsare met:Redistributions of source code must retain the above copyright notice,this list of conditions and the following disclaimer.Redistributions in binary form must reproduce the above copyright notice,this list of conditions and the following disclaimer in the documentationand/or other materials provided with the distribution.Neither the name of the NLNET LABS nor the names of its contributors maybe used to endorse or promote products derived from this software withoutspecific prior written permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORSAS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHTHOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITEDTO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, ORPROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OFLIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDINGNEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#info-zip">2.38. Info-ZIP</div><div class="search_word">2.38. info-zip copyright (c) 1990-2009 info-zip.  all rights reserved.for the purposes of this copyright and license, "info-zip" is defined asthe following set of individuals:   mark adler, john bush, karl davis, harald denker, jean-michel dubois,   jean-loup gailly, hunter goatley, ed gordon, ian gorman, chris herborth,   dirk haase, greg hartwig, robert heath, jonathan hudson, paul kienitz,   david kirschbaum, johnny lee, onno van der linden, igor mandrichenko,   steve p. miller, sergio monesi, keith owens, george petrov, greg roelofs,   kai uwe rommel, steve salisbury, dave smith, steven m. schweda,   christian spieler, cosmin truta, antoine verheijen, paul von behren,   rich wales, mike white.this software is provided "as is," without warranty of any kind, expressor implied.  in no event shall info-zip or its contributors be held liablefor any direct, indirect, incidental, special or consequential damagesarising out of the use of or inability to use this software.permission is granted to anyone to use this software for any purpose,including commercial applications, and to alter it and redistribute itfreely, subject to the above disclaimer and the following restrictions:    1. redistributions of source code (in whole or in part) must retain       the above copyright notice, definition, disclaimer, and this list       of conditions.    2. redistributions in binary form (compiled executables and libraries)       must reproduce the above copyright notice, definition, disclaimer,       and this list of conditions in documentation and/or other materials       provided with the distribution.  additional documentation is not needed       for executables where a command line license option provides these and       a note regarding this option is in the executable's startup banner.  the       sole exception to this condition is redistribution of a standard       unzipsfx binary (including sfxwiz) as part of a self-extracting archive;       that is permitted without inclusion of this license, as long as the       normal sfx banner has not been removed from the binary or disabled.    3. altered versions--including, but not limited to, ports to new operating       systems, existing ports with new graphical interfaces, versions with       modified or added functionality, and dynamic, shared, or static library       versions not from info-zip--must be plainly marked as such and must not       be misrepresented as being the original source or, if binaries,       compiled from the original source.  such altered versions also must not       be misrepresented as being info-zip releases--including, but not       limited to, labeling of the altered versions with the names "info-zip"       (or any variation thereof, including, but not limited to, different       capitalizations), "pocket unzip," "wiz" or "maczip" without the       explicit permission of info-zip.  such altered versions are further       prohibited from misrepresentative use of the zip-bugs or info-zip       e-mail addresses or the info-zip url(s), such as to imply info-zip       will provide support for the altered versions.    4. info-zip retains the right to use the names "info-zip," "zip," "unzip,"       "unzipsfx," "wiz," "pocket unzip," "pocket zip," and "maczip" for its       own source and binary releases.</div><div class="display_word">2.38. Info-ZIP Copyright (c) 1990-2009 Info-ZIP.  All rights reserved.For the purposes of this copyright and license, "Info-ZIP" is defined asthe following set of individuals:   Mark Adler, John Bush, Karl Davis, Harald Denker, Jean-Michel Dubois,   Jean-loup Gailly, Hunter Goatley, Ed Gordon, Ian Gorman, Chris Herborth,   Dirk Haase, Greg Hartwig, Robert Heath, Jonathan Hudson, Paul Kienitz,   David Kirschbaum, Johnny Lee, Onno van der Linden, Igor Mandrichenko,   Steve P. Miller, Sergio Monesi, Keith Owens, George Petrov, Greg Roelofs,   Kai Uwe Rommel, Steve Salisbury, Dave Smith, Steven M. Schweda,   Christian Spieler, Cosmin Truta, Antoine Verheijen, Paul von Behren,   Rich Wales, Mike White.This software is provided "as is," without warranty of any kind, expressor implied.  In no event shall Info-ZIP or its contributors be held liablefor any direct, indirect, incidental, special or consequential damagesarising out of the use of or inability to use this software.Permission is granted to anyone to use this software for any purpose,including commercial applications, and to alter it and redistribute itfreely, subject to the above disclaimer and the following restrictions:    1. Redistributions of source code (in whole or in part) must retain       the above copyright notice, definition, disclaimer, and this list       of conditions.    2. Redistributions in binary form (compiled executables and libraries)       must reproduce the above copyright notice, definition, disclaimer,       and this list of conditions in documentation and/or other materials       provided with the distribution.  Additional documentation is not needed       for executables where a command line license option provides these and       a note regarding this option is in the executable's startup banner.  The       sole exception to this condition is redistribution of a standard       UnZipSFX binary (including SFXWiz) as part of a self-extracting archive;       that is permitted without inclusion of this license, as long as the       normal SFX banner has not been removed from the binary or disabled.    3. Altered versions--including, but not limited to, ports to new operating       systems, existing ports with new graphical interfaces, versions with       modified or added functionality, and dynamic, shared, or static library       versions not from Info-ZIP--must be plainly marked as such and must not       be misrepresented as being the original source or, if binaries,       compiled from the original source.  Such altered versions also must not       be misrepresented as being Info-ZIP releases--including, but not       limited to, labeling of the altered versions with the names "Info-ZIP"       (or any variation thereof, including, but not limited to, different       capitalizations), "Pocket UnZip," "WiZ" or "MacZip" without the       explicit permission of Info-ZIP.  Such altered versions are further       prohibited from misrepresentative use of the Zip-Bugs or Info-ZIP       e-mail addresses or the Info-ZIP URL(s), such as to imply Info-ZIP       will provide support for the altered versions.    4. Info-ZIP retains the right to use the names "Info-ZIP," "Zip," "UnZip,"       "UnZipSFX," "WiZ," "Pocket UnZip," "Pocket Zip," and "MacZip" for its       own source and binary releases.</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#zlib">2.39. zlib</div><div class="search_word">2.39. zlib zlib.h -- interface of the 'zlib' general purpose compression libraryversion 1.2.8, april 28th, 2013copyright (c) 1995-2013 jean-loup gailly and mark adlerthis software is provided 'as-is', without any express or impliedwarranty.  in no event will the authors be held liable for any damagesarising from the use of this software.permission is granted to anyone to use this software for any purpose,including commercial applications, and to alter it and redistribute itfreely, subject to the following restrictions:1. the origin of this software must not be misrepresented; you must not   claim that you wrote the original software. if you use this software   in a product, an acknowledgment in the product documentation would be   appreciated but is not required.2. altered source versions must be plainly marked as such, and must not be   misrepresented as being the original software.3. this notice may not be removed or altered from any source distribution.jean-loup gailly        mark adlerjloup@gzip.org          madler@alumni.caltech.edu</div><div class="display_word">2.39. zlib zlib.h -- interface of the 'zlib' general purpose compression libraryversion 1.2.8, April 28th, 2013Copyright (C) 1995-2013 Jean-loup Gailly and Mark AdlerThis software is provided 'as-is', without any express or impliedwarranty.  In no event will the authors be held liable for any damagesarising from the use of this software.Permission is granted to anyone to use this software for any purpose,including commercial applications, and to alter it and redistribute itfreely, subject to the following restrictions:1. The origin of this software must not be misrepresented; you must not   claim that you wrote the original software. If you use this software   in a product, an acknowledgment in the product documentation would be   appreciated but is not required.2. Altered source versions must be plainly marked as such, and must not be   misrepresented as being the original software.3. This notice may not be removed or altered from any source distribution.Jean-loup Gailly        Mark Adlerjloup@gzip.org          madler@alumni.caltech.edu</div></div><div id="license"><div class="search_title" docfname="license" doctitle="About" link="#linux-pam">2.40. Linux-PAM</div><div class="search_word">2.40. linux-pam unless otherwise *explicitly* stated the following text describes thelicensed conditions under which the contents of this linux-pam releasemay be distributed:-------------------------------------------------------------------------redistribution and use in source and binary forms of linux-pam, withor without modification, are permitted provided that the followingconditions are met:1. redistributions of source code must retain any existing copyright   notice, and this entire permission notice in its entirety,   including the disclaimer of warranties.2. redistributions in binary form must reproduce all prior and current   copyright notices, this list of conditions, and the following   disclaimer in the documentation and/or other materials provided   with the distribution.3. the name of any author may not be used to endorse or promote   products derived from this software without their specific prior   written permission.alternatively, this product may be distributed under the terms of thegnu general public license, in which case the provisions of the gnugpl are required instead of the above restrictions.  (this clause isnecessary due to a potential conflict between the gnu gpl and therestrictions contained in a bsd-style copyright.)this software is provided ``as is'' and any express or impliedwarranties, including, but not limited to, the implied warranties ofmerchantability and fitness for a particular purpose are disclaimed.in no event shall the author(s) be liable for any direct, indirect,incidental, special, exemplary, or consequential damages (including,but not limited to, procurement of substitute goods or services; lossof use, data, or profits; or business interruption) however caused andon any theory of liability, whether in contract, strict liability, ortort (including negligence or otherwise) arising in any way out of theuse of this software, even if advised of the possibility of suchdamage.-------------------------------------------------------------------------</div><div class="display_word">2.40. Linux-PAM Unless otherwise *explicitly* stated the following text describes thelicensed conditions under which the contents of this Linux-PAM releasemay be distributed:-------------------------------------------------------------------------Redistribution and use in source and binary forms of Linux-PAM, withor without modification, are permitted provided that the followingconditions are met:1. Redistributions of source code must retain any existing copyright   notice, and this entire permission notice in its entirety,   including the disclaimer of warranties.2. Redistributions in binary form must reproduce all prior and current   copyright notices, this list of conditions, and the following   disclaimer in the documentation and/or other materials provided   with the distribution.3. The name of any author may not be used to endorse or promote   products derived from this software without their specific prior   written permission.ALTERNATIVELY, this product may be distributed under the terms of theGNU General Public License, in which case the provisions of the GNUGPL are required INSTEAD OF the above restrictions.  (This clause isnecessary due to a potential conflict between the GNU GPL and therestrictions contained in a BSD-style copyright.)THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL THE AUTHOR(S) BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSSOF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED ANDON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, ORTORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THEUSE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCHDAMAGE.-------------------------------------------------------------------------</div></div><div id="notice_notice_login_security"><div class="search_title" docfname="notice_notice_login_security" doctitle="Login" link="#ログインセキュリティー">Login Security</div><div class="search_word">login security</div><div class="display_word">Login Security</div></div><div id="notice_notice_login_security"><div class="search_title" docfname="notice_notice_login_security" doctitle="Login" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product includes the following user account management improvements as countermeasures for ensuring cyber security. to eliminate the risk of malicious cyber-attacks and ensure the product is used safely, be sure to read this document carefully and specify an appropriate user password before use. for more information, refer to user account management . mandatory administrator registration at least one administrator account must be registered for this product. therefore, a default administrative user (username: admin and password: admin) has been specified for logging in to the product the first time. when first logging into the switch, specify admin as the username and password. after logging in using the default administrative user account, the user is prompted to change the password setting. stricter limits on guest user operations if the privileged password (administrative password) has not been changed from the default setting, the following operations that use the privileged password (administrative password) will be restricted. users without administrator rights cannot transition to the privileged exec mode. factory settings cannot be restored using cli/ gui operations. cannot accept connections as a tftp server. to perform the above operations, change the privileged password (administrative password). countermeasure for brute-force attacks as a countermeasure against brute-force attacks, login restrictions are applied after a login fails. if an incorrect password is entered three successive times when logging into the switch via the console, web gui, or other means, login is disabled for one minute thereafter, even if the correct password is entered. if the password is entered incorrectly, wait at least one minute before trying to login again.</div><div class="display_word">1. Function Overview This product includes the following user account management improvements as countermeasures for ensuring cyber security. To eliminate the risk of malicious cyber-attacks and ensure the product is used safely, be sure to read this document carefully and specify an appropriate user password before use. For more information, refer to User Account Management . Mandatory administrator registration At least one administrator account must be registered for this product. Therefore, a default administrative user (username: admin and password: admin) has been specified for logging in to the product the first time. When first logging into the switch, specify admin as the username and password. After logging in using the default administrative user account, the user is prompted to change the password setting. Stricter limits on guest user operations If the privileged password (administrative password) has not been changed from the default setting, the following operations that use the privileged password (administrative password) will be restricted. Users without administrator rights cannot transition to the privileged EXEC mode. Factory settings cannot be restored using CLI/ GUI operations. Cannot accept connections as a TFTP server. To perform the above operations, change the privileged password (administrative password). Countermeasure for Brute-Force Attacks As a countermeasure against brute-force attacks, login restrictions are applied after a login fails. If an incorrect password is entered three successive times when logging into the switch via the console, web GUI, or other means, login is disabled for one minute thereafter, even if the correct password is entered. If the password is entered incorrectly, wait at least one minute before trying to login again.</div></div><div id="notice_notice_login_security"><div class="search_title" docfname="notice_notice_login_security" doctitle="Login" link="#対象機種とリビジョン">2. Applicable Models and Revisions</div><div class="search_word">2. applicable models and revisions user account management has been improved in the following models and revisions. models revisions swx3220-16mt swx3220-16tms rev.4.02.10 or later swx3200-52gt swx3200-28gt rev.4.00.25 or later swx3100-18gt swx3100-10g rev.4.01.29 or later swx2322p-16mt rev.2.06.10 or later swx2320-16mt rev.2.05.10 or later swx2310-52gt swx2310-28gt swx2310-18gt swx2310-10g rev.2.04.11 or later swr2310-28gt swr2310-18gt swr2310-10g rev.2.04.12 or later swx2310p-28gt swx2310p-18g swx2310p-10g rev.2.02.24 or later swr2311p-10g rev.2.02.25 or later swp2-10smf swp2-10mmf rev.2.03.16 or later</div><div class="display_word">2. Applicable Models and Revisions User account management has been improved in the following models and revisions. Models Revisions SWX3220-16MT SWX3220-16TMs Rev.4.02.10 or later SWX3200-52GT SWX3200-28GT Rev.4.00.25 or later SWX3100-18GT SWX3100-10G Rev.4.01.29 or later SWX2322P-16MT Rev.2.06.10 or later SWX2320-16MT Rev.2.05.10 or later SWX2310-52GT SWX2310-28GT SWX2310-18GT SWX2310-10G Rev.2.04.11 or later SWR2310-28GT SWR2310-18GT SWR2310-10G Rev.2.04.12 or later SWX2310P-28GT SWX2310P-18G SWX2310P-10G Rev.2.02.24 or later SWR2311P-10G Rev.2.02.25 or later SWP2-10SMF SWP2-10MMF Rev.2.03.16 or later</div></div><div id="notice_notice_login_security"><div class="search_title" docfname="notice_notice_login_security" doctitle="Login" link="#ファームウェア更新時の注意点">3. Precautions When Updating Firmware</div><div class="search_word">3. precautions when updating firmware if the firmware is updated with stronger user account management functionality, be sure to register an administrator account according to the following procedure before using the switch. register the administrator account with the previous firmware running, which has not been updated with stronger user account management functionality. if an administrator account already exists, then no account registration is necessary. however, if a password was not specified for the administrator account, be sure to specify a password. it is not a problem if the user name for the administrator account is the default “admin”. yamaha>enableyamaha#configure terminalyamaha(config)#username (username) privilege on password (password) create a guest user if necessary, create a guest user. if using the username command, create it with the privilege option disabled (off). yamaha(config)#username (username) privilege off password (password) change the privileged password (administrative password) to change the privileged password (administrative password) using a command, use the enable password command. yamaha(config)#enable password (special privileged access password) update the firmware to the version with a countermeasure taken update the firmware to the version with a countermeasure taken in accordance with firmware update .</div><div class="display_word">3. Precautions When Updating Firmware If the firmware is updated with stronger user account management functionality, be sure to register an administrator account according to the following procedure before using the switch. Register the administrator account with the previous firmware running, which has not been updated with stronger user account management functionality. If an administrator account already exists, then no account registration is necessary. However, if a password was not specified for the administrator account, be sure to specify a password. It is not a problem if the user name for the administrator account is the default “admin”. Yamaha>enableYamaha#configure terminalYamaha(config)#username (username) privilege on password (password) Create a guest user If necessary, create a guest user. If using the username command, create it with the privilege option disabled (off). Yamaha(config)#username (username) privilege off password (password) Change the privileged password (administrative password) To change the privileged password (administrative password) using a command, use the enable password command. Yamaha(config)#enable password (special privileged access password) Update the firmware to the version with a countermeasure taken Update the firmware to the version with a countermeasure taken in accordance with Firmware Update .</div></div><div id="notice_notice_login_security"><div class="search_title" docfname="notice_notice_login_security" doctitle="Login" link="#関連文書">4. Related Documentation</div><div class="search_word">4. related documentation user account management remote access control firmware update</div><div class="display_word">4. Related Documentation User account management Remote Access Control Firmware Update</div></div><div id="oam_oam_adecia_security"><div class="search_title" docfname="oam_oam_adecia_security" doctitle="Linking" link="#adeciaとのセキュリティ連携">Linking Security to the ADECIA System</div><div class="search_word">linking security to the adecia system</div><div class="display_word">Linking Security to the ADECIA System</div></div><div id="oam_oam_adecia_security"><div class="search_title" docfname="oam_oam_adecia_security" doctitle="Linking" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview as conferencing systems are increasingly assigned ip values, it has become essential to have security functions for preventing unauthorized access to the network. yamaha’s adecia one-stop sound solution for teleconferencing uses technology (device authentication) with a solid track record in the it industry to ensure the system is robust in terms of security risks. this product functions in combination with the adecia system to ensure even users unfamiliar with it technologies can easily utilize the security functionality. more specifically, product security functions can be enabled via the graphic user interface (gui) for the teleconferencing processor, which is a component of the adecia system. (for more details about teleconferencing processor specifications, refer to adecia product information .) if the product security function is enabled, devices not registered as authenticated cannot access the network. the product achieves linked security using the following three functions. automatic recognition of adecia components the teleconferencing processor gui automatically displays information about applicable network switches being controlled. remote network switch control from the teleconferencing processor, enable device authentication of the network switch. status notification from network switches a notification is sent to the teleconferencing processor if unauthorized access is detected by a network switch.</div><div class="display_word">1. Function Overview As conferencing systems are increasingly assigned IP values, it has become essential to have security functions for preventing unauthorized access to the network. Yamaha’s ADECIA one-stop sound solution for teleconferencing uses technology (device authentication) with a solid track record in the IT industry to ensure the system is robust in terms of security risks. This product functions in combination with the ADECIA system to ensure even users unfamiliar with IT technologies can easily utilize the security functionality. More specifically, product security functions can be enabled via the graphic user interface (GUI) for the teleconferencing processor, which is a component of the ADECIA system. (For more details about teleconferencing processor specifications, refer to ADECIA Product Information .) If the product security function is enabled, devices not registered as authenticated cannot access the network. The product achieves linked security using the following three functions. Automatic recognition of ADECIA components The teleconferencing processor GUI automatically displays information about applicable network switches being controlled. Remote network switch control From the teleconferencing processor, enable device authentication of the network switch. Status notification from network switches A notification is sent to the teleconferencing processor if unauthorized access is detected by a network switch.</div></div><div id="oam_oam_adecia_security"><div class="search_title" docfname="oam_oam_adecia_security" doctitle="Linking" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used adecia the adecia is a sound system equipped with microphones and speaker systems optimized for rooms/classrooms where teleconferencing or lectures will be conducted. the adecia system includes the following components. teleconferencing processor that handles routing within the system, audio processing, and connection to the computer where teleconferencing application software is installed network switches for connecting to respective components dante-compatible microphone dante-compatible speaker system dante dante is a digital audio network specification developed by the audinate corporation. yamaha unified network operation service (y-unos) y-unos is a service for linking devices via the network. also, network switches are linked to adecia security functionality by compliance with y-unos. this product and teleconferencing processors in adecia components support the y-unos service.</div><div class="display_word">2. Definition of Terms Used ADECIA The ADECIA is a sound system equipped with microphones and speaker systems optimized for rooms/classrooms where teleconferencing or lectures will be conducted. The ADECIA system includes the following components. Teleconferencing processor that handles routing within the system, audio processing, and connection to the computer where teleconferencing application software is installed Network switches for connecting to respective components Dante-compatible microphone Dante-compatible speaker system Dante Dante is a digital audio network specification developed by the Audinate Corporation. Yamaha Unified Network Operation Service (Y-UNOS) Y-UNOS is a service for linking devices via the network. Also, network switches are linked to ADECIA security functionality by compliance with Y-UNOS. This product and teleconferencing processors in ADECIA components support the Y-UNOS service.</div></div><div id="oam_oam_adecia_security"><div class="search_title" docfname="oam_oam_adecia_security" doctitle="Linking" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_adecia_security"><div class="search_title" docfname="oam_oam_adecia_security" doctitle="Linking" link="#adeciaコンポーネントの自動認識">3.1. Automatic recognition of ADECIA components</div><div class="search_word">3.1. automatic recognition of adecia components this product automatically recognizes y-unos-compatible devices within the same network (maintenance vlan) as the product. security links to the adecia system utilize this functionality for the following. the gui for the teleconferencing processor displays a list of network switches where security is specified. the gui for the teleconferencing processor displays a list of devices subject to device authentication (devices with permission for connecting to the network). the network switch determines which teleconferencing processor is notified of unauthorized access.</div><div class="display_word">3.1. Automatic recognition of ADECIA components This product automatically recognizes Y-UNOS-compatible devices within the same network (maintenance VLAN) as the product. Security links to the ADECIA system utilize this functionality for the following. The GUI for the teleconferencing processor displays a list of network switches where security is specified. The GUI for the teleconferencing processor displays a list of devices subject to device authentication (devices with permission for connecting to the network). The network switch determines which teleconferencing processor is notified of unauthorized access.</div></div><div id="oam_oam_adecia_security"><div class="search_title" docfname="oam_oam_adecia_security" doctitle="Linking" link="#スイッチの遠隔制御">3.2. Remote network switch control</div><div class="search_word">3.2. remote network switch control this product can use y-unos functionality to apply settings from other devices connected to the same network (maintenance vlan). to link security, the following settings are applied to individual network switches by commands from the teleconferencing processor. note that those settings are configured automatically by the security linking function for all devices at the same time, so users do not need to think about each setting. generate root certificate authority specify authenticated users (devices) set local radius server function set host mode (all interfaces) set mac authentication function (all interfaces) set radius server host set mac authentication function for the entire system</div><div class="display_word">3.2. Remote network switch control This product can use Y-UNOS functionality to apply settings from other devices connected to the same network (maintenance VLAN). To link security, the following settings are applied to individual network switches by commands from the teleconferencing processor. Note that those settings are configured automatically by the security linking function for all devices at the same time, so users do not need to think about each setting. Generate root certificate authority Specify authenticated users (devices) Set local RADIUS server function Set host mode (all interfaces) Set MAC authentication function (all interfaces) Set RADIUS server host Set MAC authentication function for the entire system</div></div><div id="oam_oam_adecia_security"><div class="search_title" docfname="oam_oam_adecia_security" doctitle="Linking" link="#スイッチからの状態通知">3.3. Status notification from network switches</div><div class="search_word">3.3. status notification from network switches this product can use y-unos functionality to notify other devices connected to the same network (maintenance vlan) about its own status. to link security, this product can notify all teleconferencing processors if invalid access to the product occurred (an unregistered device was connected).</div><div class="display_word">3.3. Status notification from network switches This product can use Y-UNOS functionality to notify other devices connected to the same network (maintenance VLAN) about its own status. To link security, this product can notify all teleconferencing processors if invalid access to the product occurred (an unregistered device was connected).</div></div><div id="oam_oam_adecia_security"><div class="search_title" docfname="oam_oam_adecia_security" doctitle="Linking" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for command details, refer to the command reference. operations operating commands enable/disable the security linking function (y-unos) y-unos show y-unos status show y-unos</div><div class="display_word">4. Related Commands Related commands are indicated below. For command details, refer to the command reference. Operations Operating commands Enable/disable the security linking function (Y-UNOS) y-unos Show Y-UNOS status show y-unos</div></div><div id="oam_oam_adecia_security"><div class="search_title" docfname="oam_oam_adecia_security" doctitle="Linking" link="#セキュリティ連携の初期設定">5. Security Linking Default Settings</div><div class="search_word">5. security linking default settings if security is linked to the adecia system, use the most recent firmware to apply security linking settings. for information about how to update the firmware and apply settings, refer to linking security to adecia in the product technical information site for yamaha network switch products.</div><div class="display_word">5. Security Linking Default Settings If security is linked to the ADECIA system, use the most recent firmware to apply security linking settings. For information about how to update the firmware and apply settings, refer to Linking security to ADECIA in the product technical information site for Yamaha network switch products.</div></div><div id="oam_oam_adecia_security"><div class="search_title" docfname="oam_oam_adecia_security" doctitle="Linking" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution be sure to configure default settings for security linking before the above functionality is first used. do not change settings during use, such as by using product commands or the gui. the functionality might not function properly if the settings are changed. be sure to remove the microsd card after default settings for security linking are executed. if the microsd card left inserted, the firmware update and configuration will be applied the next time the product is started. this function cannot be used if the stack function is enabled. disable the stack function before using this function. beware that the functionality for automatic sd card booting (firmware and system configuration) will not function if the stack function is enabled.</div><div class="display_word">6. Points of Caution Be sure to configure default settings for security linking before the above functionality is first used. Do not change settings during use, such as by using product commands or the GUI. The functionality might not function properly if the settings are changed. Be sure to remove the microSD card after default settings for security linking are executed. If the microSD card left inserted, the firmware update and configuration will be applied the next time the product is started. This function cannot be used if the stack function is enabled. Disable the stack function before using this function. Beware that the functionality for automatic SD card booting (firmware and system configuration) will not function if the stack function is enabled.</div></div><div id="oam_oam_adecia_security"><div class="search_title" docfname="oam_oam_adecia_security" doctitle="Linking" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation use of external memory firmware update stack function yamaha network switch product technical information site—linking security to adecia yamaha network switch product technical information site—firmware information adecia product information</div><div class="display_word">7. Related Documentation Use of External Memory Firmware Update Stack Function Yamaha network switch product technical information site—Linking security to ADECIA Yamaha network switch product technical information site—Firmware information ADECIA Product Information</div></div><div id="oam_oam_boot_info"><div class="search_title" docfname="oam_oam_boot_info" doctitle="Boot" link="#起動情報の管理">Boot Information Management</div><div class="search_word">boot information management</div><div class="display_word">Boot Information Management</div></div><div id="oam_oam_boot_info"><div class="search_title" docfname="oam_oam_boot_info" doctitle="Boot" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview as system boot information, this product manages the information shown in the table below. management item description system startup time time that the system booted up running firmware information firmware version currently running, and date generated firmware information for previous startup version and generated date of the firmware for the previous startup reason for boot reason why the system booted up. the following are recorded: * startup due to power-on * restart due to the reload command * restart due to the cold start command * restart due to the startup-config select command * restart due to the boot prioritize sd command * restart due to the restore system command * restart due to the stack enable command * restart due to firmware updates * restart due to memory exhaustion * restart due to kernel panic * restart due to abnormal termination of process this product stores the current boot information and information on the previous four boots, for a total of five boot records.</div><div class="display_word">1. Function Overview As system boot information, this product manages the information shown in the table below. Management item Description System startup time Time that the system booted up Running firmware information Firmware version currently running, and date generated Firmware information for previous startup Version and generated date of the firmware for the previous startup Reason for boot Reason why the system booted up. The following are recorded: * Startup due to power-on * Restart due to the reload command * Restart due to the cold start command * Restart due to the startup-config select command * Restart due to the boot prioritize sd command * Restart due to the restore system command * Restart due to the stack enable command * Restart due to firmware updates * Restart due to memory exhaustion * Restart due to kernel panic * Restart due to abnormal termination of process This product stores the current boot information and information on the previous four boots, for a total of five boot records.</div></div><div id="oam_oam_boot_info"><div class="search_title" docfname="oam_oam_boot_info" doctitle="Boot" link="#関連コマンド">2. Related Commands</div><div class="search_word">2. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands show boot information show boot clear boot information clear boot list</div><div class="display_word">2. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Show boot information show boot Clear boot information clear boot list</div></div><div id="oam_oam_boot_info"><div class="search_title" docfname="oam_oam_boot_info" doctitle="Boot" link="#コマンド実行例">3. Examples of Command Execution</div><div class="search_word">3. examples of command execution</div><div class="display_word">3. Examples of Command Execution</div></div><div id="oam_oam_boot_info"><div class="search_title" docfname="oam_oam_boot_info" doctitle="Boot" link="#起動情報の表示">3.1. Show boot information</div><div class="search_word">3.1. show boot information this shows the current boot information. yamaha>show boot 0 running exec: swx2310p rev.2.02.02 (tue dec  5 11:37:39 2017)previous exec: swx2310p rev.2.02.02 (tue dec  5 11:37:39 2017)restart by reload command this shows a list of the boot history. yamaha>show boot listno. date       time     info--- ---------- -------- -------------------------------------------------  0 2018/03/15 09:50:29 restart by reload command  1 2018/03/14 20:24:40 power-on boot--- ---------- -------- -------------------------------------------------</div><div class="display_word">3.1. Show boot information This shows the current boot information. Yamaha>show boot 0 Running EXEC: SWX2310P Rev.2.02.02 (Tue Dec  5 11:37:39 2017)Previous EXEC: SWX2310P Rev.2.02.02 (Tue Dec  5 11:37:39 2017)Restart by reload command This shows a list of the boot history. Yamaha>show boot listNo. Date       Time     Info--- ---------- -------- -------------------------------------------------  0 2018/03/15 09:50:29 Restart by reload command  1 2018/03/14 20:24:40 Power-on boot--- ---------- -------- -------------------------------------------------</div></div><div id="oam_oam_boot_info"><div class="search_title" docfname="oam_oam_boot_info" doctitle="Boot" link="#起動情報のクリア">3.2. Clear boot information</div><div class="search_word">3.2. clear boot information this clears the boot information. yamaha#clear boot list</div><div class="display_word">3.2. Clear boot information This clears the boot information. Yamaha#clear boot list</div></div><div id="oam_oam_boot_info"><div class="search_title" docfname="oam_oam_boot_info" doctitle="Boot" link="#注意事項">4. Points of Caution</div><div class="search_word">4. points of caution none.</div><div class="display_word">4. Points of Caution None.</div></div><div id="oam_oam_boot_info"><div class="search_title" docfname="oam_oam_boot_info" doctitle="Boot" link="#関連文書">5. Related Documentation</div><div class="search_word">5. related documentation none.</div><div class="display_word">5. Related Documentation None.</div></div><div id="oam_oam_cable_diag"><div class="search_title" docfname="oam_oam_cable_diag" doctitle="Cable" link="#ケーブル診断">Cable Diagnostics</div><div class="search_word">cable diagnostics</div><div class="display_word">Cable Diagnostics</div></div><div id="oam_oam_cable_diag"><div class="search_title" docfname="oam_oam_cable_diag" doctitle="Cable" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview the cable diagnostic function can be used to easily check whether or not the lan cable connected to the lan port has a faulty connection/circuit. it can be used to troubleshoot network problems or as an easy way to check cables when setting up networks.</div><div class="display_word">1. Function Overview The cable diagnostic function can be used to easily check whether or not the LAN cable connected to the LAN port has a faulty connection/circuit. It can be used to troubleshoot network problems or as an easy way to check cables when setting up networks.</div></div><div id="oam_oam_cable_diag"><div class="search_title" docfname="oam_oam_cable_diag" doctitle="Cable" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used tdr (time domain reflector) the tdr is used to measure the length of lan cables or the location of damage based on the reflected signals from a pulse signal sent through the lan cables.</div><div class="display_word">2. Definition of Terms Used TDR (Time Domain Reflector) The TDR is used to measure the length of LAN cables or the location of damage based on the reflected signals from a pulse signal sent through the LAN cables.</div></div><div id="oam_oam_cable_diag"><div class="search_title" docfname="oam_oam_cable_diag" doctitle="Cable" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_cable_diag"><div class="search_title" docfname="oam_oam_cable_diag" doctitle="Cable" link="#ケーブル診断方法">3.1. How to diagnose cables</div><div class="search_word">3.1. how to diagnose cables the cable diagnostic function can easily diagnose lan cables using the time domain reflection (tdr) method. cable diagnostics is started by executing the cable-diagnostics tdr execute interface command. if the show cable-diagnostics tdr command is executed after the diagnostics process is finished, the following diagnostic results are displayed. item description cable status the following cable states can be detected. * ok: the cable is electrically connected. * open: either no device is connected on the opposite end or the cable is faulty. * short: a short circuit occurred. results are displayed for each pair. distance to the cable failure point if the cable status is “open” or “short”, then the distance to the fault is displayed. results are displayed for each pair. results from executing cable diagnostics the previous time can be checked using the show cable-diagnostics tdr command. only the immediately previous diagnostic results are retained and then overwritten the next time the cable diagnostics command is executed again. the immediately previous results can be deleted using the clear cable-diagnostics tdr command.</div><div class="display_word">3.1. How to diagnose cables The cable diagnostic function can easily diagnose LAN cables using the time domain reflection (TDR) method. Cable diagnostics is started by executing the cable-diagnostics tdr execute interface command. If the show cable-diagnostics tdr command is executed after the diagnostics process is finished, the following diagnostic results are displayed. Item Description Cable status The following cable states can be detected. * OK: The cable is electrically connected. * Open: Either no device is connected on the opposite end or the cable is faulty. * Short: A short circuit occurred. Results are displayed for each pair. Distance to the cable failure point If the cable status is “Open” or “Short”, then the distance to the fault is displayed. Results are displayed for each pair. Results from executing cable diagnostics the previous time can be checked using the show cable-diagnostics tdr command. Only the immediately previous diagnostic results are retained and then overwritten the next time the cable diagnostics command is executed again. The immediately previous results can be deleted using the clear cable-diagnostics tdr command.</div></div><div id="oam_oam_cable_diag"><div class="search_title" docfname="oam_oam_cable_diag" doctitle="Cable" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for command details, refer to the command reference. operations operating commands perform the cable diagnostics cable-diagnostics tdr execute interface display cable diagnostics show cable-diagnostics tdr clear cable diagnostic results clear cable-diagnostics tdr the following commands included in smart switches can be used in the same way as the commands above. test cable-diagnostics tdr interface show test cable-diagnostics tdr clear test cable-diagnostics tdr</div><div class="display_word">4. Related Commands Related commands are indicated below. For command details, refer to the command reference. Operations Operating commands Perform the cable diagnostics cable-diagnostics tdr execute interface Display cable diagnostics show cable-diagnostics tdr Clear cable diagnostic results clear cable-diagnostics tdr The following commands included in smart switches can be used in the same way as the commands above. test cable-diagnostics tdr interface show test cable-diagnostics tdr clear test cable-diagnostics tdr</div></div><div id="oam_oam_cable_diag"><div class="search_title" docfname="oam_oam_cable_diag" doctitle="Cable" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="oam_oam_cable_diag"><div class="search_title" docfname="oam_oam_cable_diag" doctitle="Cable" link="#ケーブル診断の実行">5.1. Perform the cable diagnostics</div><div class="search_word">5.1. perform the cable diagnostics diagnose of the lan cable connected to port 1.1 as follows. yamaha# test cable-diagnostics tdr interface port1.1the port will be temporarily down during test. continue? (y/n): y% to check result, enter "show cable-diagnostics tdr"</div><div class="display_word">5.1. Perform the cable diagnostics Diagnose of the LAN cable connected to port 1.1 as follows. Yamaha# test cable-diagnostics tdr interface port1.1The port will be temporarily down during test. Continue? (y/n): y% To check result, enter "show cable-diagnostics tdr"</div></div><div id="oam_oam_cable_diag"><div class="search_title" docfname="oam_oam_cable_diag" doctitle="Cable" link="#前回の診断結果の確認">5.2. Checking previous diagnostic results</div><div class="search_word">5.2. checking previous diagnostic results display the previous diagnostic results as follows. yamaha# show test cable-diagnostics tdrlast run on tue may 31 18:12:13 2022port      pair  status  fault distance-------------------------------------------port1.1   1     ok      -          2     ok      -          3     open    15  m          4     open    15  m</div><div class="display_word">5.2. Checking previous diagnostic results Display the previous diagnostic results as follows. Yamaha# show test cable-diagnostics tdrLast run on Tue May 31 18:12:13 2022Port      Pair  Status  Fault distance-------------------------------------------port1.1   1     OK      -          2     OK      -          3     Open    15  m          4     Open    15  m</div></div><div id="oam_oam_cable_diag"><div class="search_title" docfname="oam_oam_cable_diag" doctitle="Cable" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution this function performs simplified diagnostics. note that it cannot be used for precision diagnosis of more specialized equipment. cables 10 m or longer can be diagnosed. cables shorter than 10 m cannot be diagnosed in some cases. communication is temporarily stopped during cable diagnostics. diagnostics cannot be performed if a shutdown command is specified for a corresponding port or the port is shut down either because a loop was detected or for any other reason. diagnostics cannot be performed properly in some cases if the port on the opposite end is linked at a speed less than 1 gbps. diagnostics cannot be performed properly if poe power is supplied at a corresponding port. if a stack is configured, commands cannot be executed from member switches in the stack.</div><div class="display_word">6. Points of Caution This function performs simplified diagnostics. Note that it cannot be used for precision diagnosis of more specialized equipment. Cables 10 m or longer can be diagnosed. Cables shorter than 10 m cannot be diagnosed in some cases. Communication is temporarily stopped during cable diagnostics. Diagnostics cannot be performed if a shutdown command is specified for a corresponding port or the port is shut down either because a loop was detected or for any other reason. Diagnostics cannot be performed properly in some cases if the port on the opposite end is linked at a speed less than 1 Gbps. Diagnostics cannot be performed properly if PoE power is supplied at a corresponding port. If a stack is configured, commands cannot be executed from member switches in the stack.</div></div><div id="oam_oam_cable_diag"><div class="search_title" docfname="oam_oam_cable_diag" doctitle="Cable" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation none</div><div class="display_word">7. Related Documentation None</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#筐体情報の表示">Show Chassis Information</div><div class="search_word">show chassis information</div><div class="display_word">Show Chassis Information</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product provides the following functionality that can be used to obtain product information, operating information, and so on. use commands to show chassis information obtain technical support information remotely save technical support information on external memory technical support information includes a wide variety of data analysis information, including not only product information and operating information for this product, but also configuration information and process operating status information. the functions can be used to show all information for a device at the same time.</div><div class="display_word">1. Function Overview This product provides the following functionality that can be used to obtain product information, operating information, and so on. Use commands to show chassis information Obtain technical support information remotely Save technical support information on external memory Technical support information includes a wide variety of data analysis information, including not only product information and operating information for this product, but also configuration information and process operating status information. The functions can be used to show all information for a device at the same time.</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#機能詳細">2. Function Details</div><div class="search_word">2. function details</div><div class="display_word">2. Function Details</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#コマンドによる筐体情報の表示">2.1. Use commands to show chassis information</div><div class="search_word">2.1. use commands to show chassis information this function shows chassis information by entering a command in the console. the following chassis information can be shown. display item explanation commands inventory information shows information for this product, such as inventory name, model number, and product id. if an sfp module has been inserted, the inventory information for the module will also be shown. show inventory operating information shows the operating information for this product’s programs, such as running software information, cpu usage, memory usage, boot time. show environment process list shows the system summary information and a list of running processes. show process memory usage status shows the memory usage status for each process. show memory disk usage status shows the usage status of the disks used in the system. show disk-usage technical support information shows all available operating information as data analysis information necessary for technical support. if the stack function is enabled, technical support information is shown for member switches in addition to information for the main switch. show tech-support</div><div class="display_word">2.1. Use commands to show chassis information This function shows chassis information by entering a command in the console. The following chassis information can be shown. Display item Explanation Commands Inventory information Shows information for this product, such as inventory name, model number, and product ID. If an SFP module has been inserted, the inventory information for the module will also be shown. show inventory Operating information Shows the operating information for this product’s programs, such as running software information, CPU usage, memory usage, boot time. show environment Process list Shows the system summary information and a list of running processes. show process Memory usage status Shows the memory usage status for each process. show memory Disk usage status Shows the usage status of the disks used in the system. show disk-usage Technical support information Shows all available operating information as data analysis information necessary for technical support. If the stack function is enabled, technical support information is shown for member switches in addition to information for the main switch. show tech-support</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#製品情報の表示">2.1.1. Show inventory information</div><div class="search_word">2.1.1. show inventory information product information for the main unit and sfp module can be shown using the show inventory command. product information includes the following information. name (name) description (descr) vendor name (vendor) product id (pid) version id (vid) serial number (sn)</div><div class="display_word">2.1.1. Show inventory information Product information for the main unit and SFP module can be shown using the show inventory command. Product information includes the following information. Name (NAME) Description (DESCR) Vendor Name (Vendor) Product ID (PID) Version ID (VID) Serial number (SN)</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#稼動情報の表示">2.1.2. Show operating information</div><div class="search_word">2.1.2. show operating information system operating status can be shown using the show environment command. the system operating status includes the following information. boot version firmware revision serial number mac address cpu usage ratio memory usage ratio fan operating status fan rpm firmware file startup config file setting the automatic sd card booting function serial baud rate startup time current time elapsed time from boot unit temperature status unit temperature</div><div class="display_word">2.1.2. Show operating information System operating status can be shown using the show environment command. The system operating status includes the following information. Boot version Firmware revision Serial number MAC address CPU usage ratio Memory usage ratio Fan operating status Fan RPM Firmware file Startup config file Setting the automatic SD card booting function Serial baud rate Startup time Current time Elapsed time from boot Unit temperature status Unit temperature</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#技術サポート情報の表示">2.1.3. Show technical support information</div><div class="search_word">2.1.3. show technical support information technical support information can be shown using the show tech-support command. technical support information includes results from executing the following commands. when the stack function is enabled, technical support information for all devices in the stack configuration is shown. however, the commands executed on the main switch and member switches are different. for details, refer to the command list. list of commands to be executed commands stacking disabled stacking enabled main switch member switch show running-config yes yes yes show startup-config yes yes yes show stack yes (*1) yes (*1) yes (*1) show environment yes yes yes show system-diagnostics yes yes yes show clock detail yes yes - show disk-usage yes yes yes show inventory yes yes yes show boot all yes yes yes show boot prioritize sd yes yes yes show logging yes yes yes show process yes yes yes show memory yes yes yes show users yes yes yes show interface yes yes - show frame-counter yes yes - show vlan brief yes yes - show spanning-tree mst detail yes yes - show etherchannel status detail yes yes - show loop-detect yes yes - show mac-address-table yes yes - show l2ms detail yes yes - show qos queue-counters yes yes - show ddm status yes yes yes show errdisable yes yes - show auth status yes yes - show auth supplicant yes yes - show power-inline yes yes - show error port-led yes yes - show ip interface brief yes yes - show ip forwarding yes yes - show ipv6 interface brief yes yes - show ipv6 forwarding yes yes - show ip route yes yes - show ip route database yes yes - show ipv6 route yes yes - show ipv6 route database yes yes - show arp yes yes - show ipv6 neighbors yes yes - show ip igmp snooping groups yes yes - show ip igmp snooping interface yes yes - show ipv6 mld snooping groups yes yes - show ipv6 mld snooping interface yes yes - show ip dhcp snooping binding yes yes - show ip dhcp snooping statistics yes yes - show radius-server local certificate status yes yes - show radius-server local nas yes yes - show radius-server local user yes yes - show radius-server local certificate list yes yes - show radius-server local certificate revoke yes yes - show sflow yes yes - show sflow sampling yes yes - *1 this command is only included in stack-compatible models.</div><div class="display_word">2.1.3. Show technical support information Technical support information can be shown using the show tech-support command. Technical support information includes results from executing the following commands. When the stack function is enabled, technical support information for all devices in the stack configuration is shown. However, the commands executed on the main switch and member switches are different. For details, refer to the command list. List of commands to be executed Commands Stacking disabled Stacking enabled Main switch Member switch show running-config Yes Yes Yes show startup-config Yes Yes Yes show stack Yes (*1) Yes (*1) Yes (*1) show environment Yes Yes Yes show system-diagnostics Yes Yes Yes show clock detail Yes Yes - show disk-usage Yes Yes Yes show inventory Yes Yes Yes show boot all Yes Yes Yes show boot prioritize sd Yes Yes Yes show logging Yes Yes Yes show process Yes Yes Yes show memory Yes Yes Yes show users Yes Yes Yes show interface Yes Yes - show frame-counter Yes Yes - show vlan brief Yes Yes - show spanning-tree mst detail Yes Yes - show etherchannel status detail Yes Yes - show loop-detect Yes Yes - show mac-address-table Yes Yes - show l2ms detail Yes Yes - show qos queue-counters Yes Yes - show ddm status Yes Yes Yes show errdisable Yes Yes - show auth status Yes Yes - show auth supplicant Yes Yes - show power-inline Yes Yes - show error port-led Yes Yes - show ip interface brief Yes Yes - show ip forwarding Yes Yes - show ipv6 interface brief Yes Yes - show ipv6 forwarding Yes Yes - show ip route Yes Yes - show ip route database Yes Yes - show ipv6 route Yes Yes - show ipv6 route database Yes Yes - show arp Yes Yes - show ipv6 neighbors Yes Yes - show ip igmp snooping groups Yes Yes - show ip igmp snooping interface Yes Yes - show ipv6 mld snooping groups Yes Yes - show ipv6 mld snooping interface Yes Yes - show ip dhcp snooping binding Yes Yes - show ip dhcp snooping statistics Yes Yes - show radius-server local certificate status Yes Yes - show radius-server local nas Yes Yes - show radius-server local user Yes Yes - show radius-server local certificate list Yes Yes - show radius-server local certificate revoke Yes Yes - show sflow Yes Yes - show sflow sampling Yes Yes - *1 This command is only included in stack-compatible models.</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#技術サポート情報のリモート取得">2.2. Obtain technical support information remotely</div><div class="search_word">2.2. obtain technical support information remotely technical support information (output results from show tech-support) can be obtained from the product by remote access via the web gui or tftp.</div><div class="display_word">2.2. Obtain technical support information remotely Technical support information (output results from show tech-support) can be obtained from the product by remote access via the Web GUI or TFTP.</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#web-gui">2.2.1. Web GUI</div><div class="search_word">2.2.1. web gui in order to operate this product’s http server, use the steps shown below to set up a network environment that allows remote access. decide on the vlan that will be used for maintenance. set the ipv4 address on the maintenance vlan. set it using the ip address command. permit access from the maintenance vlan to the http server. to specify a different vlan than for management interface command settings, use the http-server interface command. execute the following operations by accessing the web gui. show technical support information on the web gui in the “techinfo” menu, press the “show in browser” button. the execution result of the “show tech-support” command is shown. to close, press the web browser’s close button. obtain technical support information from the web gui in the “techinfo” menu, press the “obtain as text file” button to start the download automatically. the file is saved with a file name in the following format. techinfo_yyyymmddhhmmss.txt (where “yyyymmddhhmmss” is the date/time the command was executed)</div><div class="display_word">2.2.1. Web GUI In order to operate this product’s HTTP server, use the steps shown below to set up a network environment that allows remote access. Decide on the VLAN that will be used for maintenance. Set the IPv4 address on the maintenance VLAN. Set it using the ip address command. Permit access from the maintenance VLAN to the HTTP server. To specify a different VLAN than for management interface command settings, use the http-server interface command. Execute the following operations by accessing the Web GUI. Show technical support information on the Web GUI In the “TECHINFO” menu, press the “Show in browser” button. The execution result of the “show tech-support” command is shown. To close, press the web browser’s close button. Obtain technical support information from the Web GUI In the “TECHINFO” menu, press the “Obtain as text file” button to start the download automatically. The file is saved with a file name in the following format. techinfo_YYYYMMDDhhmmss.txt (where “YYYYMMDDhhmmss” is the date/time the command was executed)</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#tftp">2.2.2. TFTP</div><div class="search_word">2.2.2. tftp in order to operate this product’s tftp server, use the steps shown below to set up a network environment that allows remote access. decide on the vlan that will be used for maintenance. set the ipv4 address on the maintenance vlan. set it using the ip address command. permit access from the maintenance vlan to the tftp server. to specify a different vlan than for management interface command settings, use the tftp-server interface command. if using a tftp client, specify techinfo in the remote path for obtaining technical support information.</div><div class="display_word">2.2.2. TFTP In order to operate this product’s TFTP server, use the steps shown below to set up a network environment that allows remote access. Decide on the VLAN that will be used for maintenance. Set the IPv4 address on the maintenance VLAN. Set it using the ip address command. Permit access from the maintenance VLAN to the TFTP server. To specify a different VLAN than for management interface command settings, use the tftp-server interface command. If using a TFTP client, specify techinfo in the remote path for obtaining technical support information.</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#技術サポート情報の外部メモリへの保存">2.3. Save technical support information on external memory</div><div class="search_word">2.3. save technical support information on external memory you can use the copy tech-support sd command to save this product’s *technical support information (the output result of “show tech-support”) *on an sd card. before executing this command, you must insert an sd card. the information is saved in the sd card with the following file name. /swx2310p/techsupport/yyyymmddhhmmss_techsupport.txt (where “yyyymmddhhmmss” is the date/time the command was executed)</div><div class="display_word">2.3. Save technical support information on external memory You can use the copy tech-support sd command to save this product’s *technical support information (the output result of “show tech-support”) *on an SD card. Before executing this command, you must insert an SD card. The information is saved in the SD card with the following file name. /swx2310p/techsupport/YYYYMMDDHHMMSS_techsupport.txt (where “YYYYMMDDHHMMSS” is the date/time the command was executed)</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#関連コマンド">3. Related Commands</div><div class="search_word">3. related commands related commands are indicated below. for command details, refer to the command reference. operations operating commands show inventory information show inventory show operating information show environment process list show process memory usage status show memory disk usage status show disk-usage show technical support information show tech-support save technical support information copy tech-support sd</div><div class="display_word">3. Related Commands Related commands are indicated below. For command details, refer to the command reference. Operations Operating commands Show inventory information show inventory Show operating information show environment Process list show process Memory usage status show memory Disk usage status show disk-usage Show technical support information show tech-support Save technical support information copy tech-support sd</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#コマンド実行例">4. Examples of Command Execution</div><div class="search_word">4. examples of command execution</div><div class="display_word">4. Examples of Command Execution</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#製品情報の表示">4.1. Show inventory information</div><div class="search_word">4.1. show inventory information the following shows product information for the main unit and sfp module. yamaha>show inventoryname: l2 poe switchdescr: swx2310p-10gvendor: yamahapid: swx2310p-10gvid: 0000sn: s00000000name: sfp1descr: 1000base-lxvendor: yamahapid: ysfp-g-lxvid: 0000sn: 00000000000name: sfp2descr: 1000base-sxvendor: yamahapid: ysfp-g-sxvid: 0000sn: 00000000000</div><div class="display_word">4.1. Show inventory information The following shows product information for the main unit and SFP module. Yamaha>show inventoryNAME: L2 POE switchDESCR: SWX2310P-10GVendor: YamahaPID: SWX2310P-10GVID: 0000SN: S00000000NAME: SFP1DESCR: 1000BASE-LXVendor: YAMAHAPID: YSFP-G-LXVID: 0000SN: 00000000000NAME: SFP2DESCR: 1000BASE-SXVendor: YAMAHAPID: YSFP-G-SXVID: 0000SN: 00000000000</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#稼動情報の表示">4.2. Show operating information</div><div class="search_word">4.2. show operating information the following shows the system operating status. yamaha>show environmentswx2310p-10g bootrom ver.1.00swx2310p rev.2.02.02 (tue dec  5 11:37:39 2017)main=swx2310p-10g ver=00 serial=s00000000 mac-address=00a0.de00.0000cpu:   7%(5sec)   8%(1min)   8%(5min)    memory:  18% usedfan status: normalfan speed: fan1=4444rpm fan2=4444rpm fan3=4444rpmstartup firmware: exec0startup configuration file: config0auto-apply: enableserial baudrate: 9600boot time: 2018/01/01 11:13:44 +09:00current time: 2018/01/02 16:19:43 +09:00elapsed time from boot: 1days 05:06:04temperature status: normaltemperature: 28 degree cyamaha></div><div class="display_word">4.2. Show operating information The following shows the system operating status. Yamaha>show environmentSWX2310P-10G BootROM Ver.1.00SWX2310P Rev.2.02.02 (Tue Dec  5 11:37:39 2017)main=SWX2310P-10G ver=00 serial=S00000000 MAC-Address=00a0.de00.0000CPU:   7%(5sec)   8%(1min)   8%(5min)    Memory:  18% usedFan status: NormalFan speed: FAN1=4444RPM FAN2=4444RPM FAN3=4444RPMStartup firmware: exec0Startup Configuration file: config0Auto-apply: EnableSerial Baudrate: 9600Boot time: 2018/01/01 11:13:44 +09:00Current time: 2018/01/02 16:19:43 +09:00Elapsed time from boot: 1days 05:06:04Temperature status: NormalTemperature: 28 degree CYamaha></div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#技術サポート情報の表示">4.3. Show technical support information</div><div class="search_word">4.3. show technical support information the following shows technical support information. yamaha#show tech-support## information for yamaha technical support#*** show running-config ***!!  - running configuration -!  current time:  fri jan 1 00:00:00 jst 2021!dns-client enable!vlan database vlan 2 name vlan0002 vlan 3 name vlan0003!interface port1.1 switchport switchport mode access...*** show startup-config ***...*** show stack ***...*** show environment ***...*** show disk-usage ***.........## end of information for yamaha technical support#</div><div class="display_word">4.3. Show technical support information The following shows technical support information. Yamaha#show tech-support## Information for Yamaha Technical Support#*** show running-config ***!!  - Running Configuration -!  Current Time:  Fri Jan 1 00:00:00 JST 2021!dns-client enable!vlan database vlan 2 name VLAN0002 vlan 3 name VLAN0003!interface port1.1 switchport switchport mode access...*** show startup-config ***...*** show stack ***...*** show environment ***...*** show disk-usage ***.........## End of Information for Yamaha Technical Support#</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#注意事項">5. Points of Caution</div><div class="search_word">5. points of caution none</div><div class="display_word">5. Points of Caution None</div></div><div id="oam_oam_chassis_info"><div class="search_title" docfname="oam_oam_chassis_info" doctitle="Show" link="#関連文書">6. Related Documentation</div><div class="search_word">6. related documentation none</div><div class="display_word">6. Related Documentation None</div></div><div id="oam_oam_cis_speaker"><div class="search_title" docfname="oam_oam_cis_speaker" doctitle="Dante" link="#dante最適設定機能">Dante Optimization Setting Function</div><div class="search_word">dante optimization setting function</div><div class="display_word">Dante Optimization Setting Function</div></div><div id="oam_oam_cis_speaker"><div class="search_title" docfname="oam_oam_cis_speaker" doctitle="Dante" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview the dante setting optimization function makes it easy to build the optimal environment for dante digital audio networks. the function allows users to easily configure all dante settings at the same time without having to think about individual dante settings (such as qos, igmp snooping, disable flow control, and disable eee settings).</div><div class="display_word">1. Function Overview The Dante setting optimization function makes it easy to build the optimal environment for Dante digital audio networks. The function allows users to easily configure all Dante settings at the same time without having to think about individual Dante settings (such as QoS, IGMP snooping, disable flow control, and disable EEE settings).</div></div><div id="oam_oam_cis_speaker"><div class="search_title" docfname="oam_oam_cis_speaker" doctitle="Dante" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used dante dante is a digital audio network specification developed by the audinate corporation. adecia adecia is yamaha’s teleconferencing system. it connects processors, microphones, and speakers used for teleconferencing via a lan (dante). adecia components devices (teleconferencing processors, microphones, and speaker system) included in adecia systems. lldp protocol for passing device information to neighboring devices.</div><div class="display_word">2. Definition of Terms Used Dante Dante is a digital audio network specification developed by the Audinate Corporation. ADECIA ADECIA is Yamaha’s teleconferencing system. It connects processors, microphones, and speakers used for teleconferencing via a LAN (Dante). ADECIA Components Devices (teleconferencing processors, microphones, and speaker system) included in ADECIA systems. LLDP Protocol for passing device information to neighboring devices.</div></div><div id="oam_oam_cis_speaker"><div class="search_title" docfname="oam_oam_cis_speaker" doctitle="Dante" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details dante settings can be optimized by the following two methods. automatic optimization settings using lldp automatically applies optimized settings by receiving lldp frames independently from adecia components. manual optimization settings via the web gui applies optimized settings from the proav settings page indicated in the web gui of this product. the settings that can be collectively specified at the same time using the dante setting optimization function are listed below. for automatic setting optimization using lldp, the applicable settings will differ depending on the adecia component firmware version. object of setting function commands applicability lldp (adecia v2.5 or earlier) lldp (adecia v2.8 or later) web gui enable qos qos enable yes yes yes optimize transmission queue by dscp value qos dscp-queue 8 2 yes yes yes qos dscp-queue 26 3 - yes yes qos dscp-queue 34 4 - yes yes qos dscp-queue 46 5 yes yes yes qos dscp-queue 48 5 - yes yes qos dscp-queue 56 7 yes yes yes qos dscp-queue [not indicated above] 0 yes yes yes no qos wrr-weight [0 to 7] - yes yes always forward linked local multicasts l2-unknown-mcast forward link-local - yes yes enable lldp lldp run - - yes vlan interface disable shutdown no shutdown - - yes flood unknown multicasts l2-unknown-mcast flood - yes yes enable igmp snooping ip igmp snooping enable yes yes yes set igmp snooping version ip igmp snooping version 3 yes yes yes enable igmp snooping fast-leave function ip igmp snooping fast-leave auto-assignment - yes yes enable igmp query transmission function ip igmp snooping querier yes yes yes set igmp query transmission interval ip igmp snooping query-interval 30 yes yes yes disable igmp report-suppression function ip igmp snooping report-suppression disable - yes yes enable igmp report forwarding function ip igmp snooping report-forward enable - yes yes disable igmp packet ttl value checking function ip igmp snooping check ttl disable yes yes yes disable igmp packet ra checking function ip igmp snooping check ra disable - yes yes disable igmp packet tos checking function ip igmp snooping check tos disable - yes yes enable data transfer suppression function for multicast router ports ip igmp snooping mrouter-port data-suppression enable - yes yes set always forwarding ptp packets l2-mcast flood 224.0.1.129 - yes yes l2-mcast flood 224.0.1.130 - yes yes l2-mcast flood 224.0.1.131 - yes yes l2-mcast flood 224.0.1.132 - yes yes l2-mcast flood 239.254.3.3 - yes yes lan/sfp port set qos trust mode to dscp qos trust dscp yes yes yes disable flow control flowcontrol disable yes yes yes disable eee eee disable yes yes yes set mru mru 1522 - yes yes set l2ms filter l2ms filter disable - - yes set bpdu filter spanning-tree bpdu-filter disable - - yes create lldp agent lldp-agent - - yes enable lldp transmission and reception set lldp enable txrx - yes yes set basic management tlv tlv-select basic-mgmt - yes</div><div class="display_word">3. Function Details Dante settings can be optimized by the following two methods. Automatic optimization settings using LLDP Automatically applies optimized settings by receiving LLDP frames independently from ADECIA components. Manual optimization settings via the Web GUI Applies optimized settings from the ProAV settings page indicated in the web GUI of this product. The settings that can be collectively specified at the same time using the Dante setting optimization function are listed below. For automatic setting optimization using LLDP, the applicable settings will differ depending on the ADECIA component firmware version. Object of setting Function Commands Applicability LLDP (ADECIA V2.5 or earlier) LLDP (ADECIA V2.8 or later) Web GUI Enable QoS qos enable Yes Yes Yes Optimize transmission queue by DSCP value qos dscp-queue 8 2 Yes Yes Yes qos dscp-queue 26 3 - Yes Yes qos dscp-queue 34 4 - Yes Yes qos dscp-queue 46 5 Yes Yes Yes qos dscp-queue 48 5 - Yes Yes qos dscp-queue 56 7 Yes Yes Yes qos dscp-queue [not indicated above] 0 Yes Yes Yes no qos wrr-weight [0 to 7] - Yes Yes Always forward linked local multicasts l2-unknown-mcast forward link-local - Yes Yes Enable LLDP lldp run - - Yes VLAN interface Disable shutdown no shutdown - - Yes Flood unknown multicasts l2-unknown-mcast flood - Yes Yes Enable IGMP snooping ip igmp snooping enable Yes Yes Yes Set IGMP snooping version ip igmp snooping version 3 Yes Yes Yes Enable IGMP snooping fast-leave function ip igmp snooping fast-leave auto-assignment - Yes Yes Enable IGMP query transmission function ip igmp snooping querier Yes Yes Yes Set IGMP query transmission interval ip igmp snooping query-interval 30 Yes Yes Yes Disable IGMP report-suppression function ip igmp snooping report-suppression disable - Yes Yes Enable IGMP report forwarding function ip igmp snooping report-forward enable - Yes Yes Disable IGMP packet TTL value checking function ip igmp snooping check ttl disable Yes Yes Yes Disable IGMP packet RA checking function ip igmp snooping check ra disable - Yes Yes Disable IGMP packet ToS checking function ip igmp snooping check tos disable - Yes Yes Enable data transfer suppression function for multicast router ports ip igmp snooping mrouter-port data-suppression enable - Yes Yes Set always forwarding PTP packets l2-mcast flood 224.0.1.129 - Yes Yes l2-mcast flood 224.0.1.130 - Yes Yes l2-mcast flood 224.0.1.131 - Yes Yes l2-mcast flood 224.0.1.132 - Yes Yes l2-mcast flood 239.254.3.3 - Yes Yes LAN/SFP port Set QoS trust mode to DSCP qos trust dscp Yes Yes Yes Disable flow control flowcontrol disable Yes Yes Yes Disable EEE eee disable Yes Yes Yes Set MRU mru 1522 - Yes Yes Set L2MS filter l2ms filter disable - - Yes Set BPDU filter spanning-tree bpdu-filter disable - - Yes Create LLDP agent lldp-agent - - Yes Enable LLDP transmission and reception set lldp enable txrx - Yes Yes Set basic management TLV tlv-select basic-mgmt - Yes</div></div><div id="oam_oam_cis_speaker"><div class="search_title" docfname="oam_oam_cis_speaker" doctitle="Dante" link="#lldpによる自動最適設定">3.1. Automatic optimization settings using LLDP</div><div class="search_word">3.1. automatic optimization settings using lldp settings optimized for dante can be applied automatically by receiving lldp frames created independently by adecia components. automatic optimization settings via lldp are set by the lldp auto-setting command. by default, this product is set to enable automatic optimization settings via lldp. adecia components transmit yamaha-proprietary lldp frames that contain the following contents. eee (energy-efficient ethernet) disable setting flow control disable setting diffserve base qos setting igmp snooping settings if this function is enabled and a corresponding lldp frame is received, then the settings are automatically applied to the running-config settings for the overall system, for the vlan interface that received the frame, and for the lan/sfp port where the lldp frame was received. however, the function is disabled if even one of the automatically specified settings differs from factory settings. if you save using the copy running-config startup-config command or the write command, the settings are also applied to the startup-config that is used for the next and subsequent startups. even if the port to which the device is connected experiences a link-down state after automatic optimization settings, the automatically added settings are maintained. this function can be used only for a physical interface (lan/sfp port). it cannot be used with a link aggregated logical interface. in addition, lan/sfp port modes can only be used at access ports. they cannot be used at trunk ports. this function cannot be used if the stack function is enabled on models that support it. in order to use this function, reception of lldp frames must be enabled. for this reason, check in advance that the following settings have been made. enable lldp functionality for the overall system using the lldp run command. create lldp agents at applicable interfaces using the lldp-agent command. specify the lldp frame transmit/receive mode using the set lldp command. lldp frame transmission and reception are enabled in product default settings.</div><div class="display_word">3.1. Automatic optimization settings using LLDP Settings optimized for Dante can be applied automatically by receiving LLDP frames created independently by ADECIA components. Automatic optimization settings via LLDP are set by the lldp auto-setting command. By default, this product is set to enable automatic optimization settings via LLDP. ADECIA components transmit Yamaha-proprietary LLDP frames that contain the following contents. EEE (Energy-Efficient Ethernet) disable setting Flow control disable setting Diffserve base QoS setting IGMP snooping settings If this function is enabled and a corresponding LLDP frame is received, then the settings are automatically applied to the running-config settings for the overall system, for the VLAN interface that received the frame, and for the LAN/SFP port where the LLDP frame was received. However, the function is disabled if even one of the automatically specified settings differs from factory settings. If you save using the copy running-config startup-config command or the write command, the settings are also applied to the startup-config that is used for the next and subsequent startups. Even if the port to which the device is connected experiences a link-down state after automatic optimization settings, the automatically added settings are maintained. This function can be used only for a physical interface (LAN/SFP port). It cannot be used with a link aggregated logical interface. In addition, LAN/SFP port modes can only be used at access ports. They cannot be used at trunk ports. This function cannot be used if the stack function is enabled on models that support it. In order to use this function, reception of LLDP frames must be enabled. For this reason, check in advance that the following settings have been made. Enable LLDP functionality for the overall system using the lldp run command. Create LLDP agents at applicable interfaces using the lldp-agent command. Specify the LLDP frame transmit/receive mode using the set lldp command. LLDP frame transmission and reception are enabled in product default settings.</div></div><div id="oam_oam_cis_speaker"><div class="search_title" docfname="oam_oam_cis_speaker" doctitle="Dante" link="#web-guiからの手動最適設定">3.2. Manual optimization settings via the Web GUI</div><div class="search_word">3.2. manual optimization settings via the web gui for information on how to apply the dante optimization settings using the web gui, refer to the proav setting function .</div><div class="display_word">3.2. Manual optimization settings via the Web GUI For information on how to apply the Dante optimization settings using the web GUI, refer to the ProAV setting function .</div></div><div id="oam_oam_cis_speaker"><div class="search_title" docfname="oam_oam_cis_speaker" doctitle="Dante" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands set dante automatic optimization settings function using lldp lldp auto-setting enable lldp function lldp run create lldp agent lldp-agent set lldp transmission/reception mode set lldp set basic management tlv tlv-select basic-mgmt set flow control (system) flowcontrol set flow control (interface) flowcontrol enable qos qos set dscp - transmission queue id conversion table qos dscp-queue set egress queue scheduling qos wrr-weight set qos trust mode qos trust shutdown shutdown set forwarding multicast frames l2-mcast flood set forwarding unknown multicasts l2-unknown-mcast enable/disable igmp snooping ip igmp snooping set igmp snooping version ip igmp snooping version set igmp snooping fast-leave ip igmp snooping fast-leave set igmp query transmission function ip igmp snooping querier set igmp query transmission interval ip igmp snooping query-interval set igmp packet ttl value checking function ip igmp snooping check ttl set igmp packet ra checking function ip igmp snooping check ra set igmp packet tos checking function ip igmp snooping check tos set igmp report suppression function ip igmp snooping report-suppression enable igmp report forwarding function ip igmp snooping report-forward enable transfer suppression function for multicast router ports ip igmp snooping mrouter-port data-suppression set l2ms filter l2ms filter set bpdu filter spanning-tree bpdu-filter set eee eee set mru mru</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Set Dante automatic optimization settings function using LLDP lldp auto-setting Enable LLDP function lldp run Create LLDP agent lldp-agent Set LLDP transmission/reception mode set lldp Set basic management TLV tlv-select basic-mgmt Set flow control (system) flowcontrol Set flow control (interface) flowcontrol Enable QoS qos Set DSCP - transmission queue ID conversion table qos dscp-queue Set egress queue scheduling qos wrr-weight Set QoS trust mode qos trust Shutdown shutdown Set forwarding multicast frames l2-mcast flood Set forwarding unknown multicasts l2-unknown-mcast Enable/disable IGMP snooping ip igmp snooping Set IGMP snooping version ip igmp snooping version Set IGMP snooping fast-leave ip igmp snooping fast-leave Set IGMP query transmission function ip igmp snooping querier Set IGMP query transmission interval ip igmp snooping query-interval Set IGMP packet TTL value checking function ip igmp snooping check ttl Set IGMP packet RA checking function ip igmp snooping check ra Set IGMP packet ToS checking function ip igmp snooping check tos Set IGMP report suppression function ip igmp snooping report-suppression Enable IGMP report forwarding function ip igmp snooping report-forward Enable transfer suppression function for multicast router ports ip igmp snooping mrouter-port data-suppression Set L2MS filter l2ms filter Set BPDU filter spanning-tree bpdu-filter Set EEE eee Set MRU mru</div></div><div id="oam_oam_cis_speaker"><div class="search_title" docfname="oam_oam_cis_speaker" doctitle="Dante" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="oam_oam_cis_speaker"><div class="search_title" docfname="oam_oam_cis_speaker" doctitle="Dante" link="#lldpによる自動最適設定">5.1. Automatic optimization settings using LLDP</div><div class="search_word">5.1. automatic optimization settings using lldp enable automatic optimization settings using lldp. enable lldp transmission and reception on port1.1. yamaha#configure terminalyamaha(config)#interface port1.1yamaha(config-if)#lldp-agent (1) yamaha(lldp-agent)#set lldp enable txrx (2) yamaha(lldp-agent)#exityamaha(config-if)#exityamaha(config)#lldp run (3) yamaha(config)#lldp auto-setting enable (4) 1 create lldp agent, mode transition 2 set lldp transmission/reception mode 3 enable lldp function 4 enable automatic optimization settings using lldp</div><div class="display_word">5.1. Automatic optimization settings using LLDP Enable automatic optimization settings using LLDP. Enable LLDP transmission and reception on port1.1. Yamaha#configure terminalYamaha(config)#interface port1.1Yamaha(config-if)#lldp-agent (1) Yamaha(lldp-agent)#set lldp enable txrx (2) Yamaha(lldp-agent)#exitYamaha(config-if)#exitYamaha(config)#lldp run (3) Yamaha(config)#lldp auto-setting enable (4) 1 Create LLDP agent, mode transition 2 Set LLDP transmission/reception mode 3 Enable LLDP function 4 Enable automatic optimization settings using LLDP</div></div><div id="oam_oam_cis_speaker"><div class="search_title" docfname="oam_oam_cis_speaker" doctitle="Dante" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution using lldp to specify settings automatically this function can be used only for a physical interface (lan/sfp port). it cannot be used with a link aggregated logical interface. lan/sfp port modes can only be used at access ports. they cannot be used at trunk ports. this function cannot be used if the stack function is enabled on models that support it. this functionality is disabled if even one of the automatically specified settings differs from factory settings.</div><div class="display_word">6. Points of Caution Using LLDP to specify settings automatically This function can be used only for a physical interface (LAN/SFP port). It cannot be used with a link aggregated logical interface. LAN/SFP port modes can only be used at access ports. They cannot be used at trunk ports. This function cannot be used if the stack function is enabled on models that support it. This functionality is disabled if even one of the automatically specified settings differs from factory settings.</div></div><div id="oam_oam_cis_speaker"><div class="search_title" docfname="oam_oam_cis_speaker" doctitle="Dante" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation proav setting function lldp qos flow control igmp snooping basic interface functions spanning tree l2ms adecia product information</div><div class="display_word">7. Related Documentation ProAV Setting Function LLDP QoS Flow Control IGMP Snooping Basic Interface Functions Spanning Tree L2MS ADECIA Product Information</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#コンフィグ管理">Config Management</div><div class="search_word">config management</div><div class="display_word">Config Management</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product uses the following config information to maintain the value of settings. config type description user operations possible running config (running-config) the currently-running setting values. managed in ram. view / save to startup config startup config (startup-config) saved setting values. five config files are maintained in rom, and one on the sd card. when the system starts up, either the config from rom that is selected by the startup-config select command or the config from the sd card is loaded. one configuration on the sd card is controlled in the “/swx2310p/startup-config” folder. view / delete / copy default config (default-config) the default setting values. managed in rom. no operations possible</div><div class="display_word">1. Function Overview This product uses the following config information to maintain the value of settings. Config type Description User operations possible Running config (running-config) The currently-running setting values. Managed in RAM. View / Save to startup config Startup config (startup-config) Saved setting values. Five config files are maintained in ROM, and one on the SD card. When the system starts up, either the config from ROM that is selected by the startup-config select command or the config from the SD card is loaded. One configuration on the SD card is controlled in the “/swx2310p/startup-config” folder. View / Delete / Copy Default config (default-config) The default setting values. Managed in ROM. No operations possible</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used none</div><div class="display_word">2. Definition of Terms Used None</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#ランニングコンフィグ">3.1. Running config</div><div class="search_word">3.1. running config running-config is the settings that are currently operating; since it is maintained in ram, it is destroyed at reboot. on this product, commands executed in configuration mode are immediately applied to running-config, and the unit operates according to these settings. the contents of running-config can be viewed by using the show running-config command.</div><div class="display_word">3.1. Running config running-config is the settings that are currently operating; since it is maintained in RAM, it is destroyed at reboot. On this product, commands executed in configuration mode are immediately applied to running-config, and the unit operates according to these settings. The contents of running-config can be viewed by using the show running-config command.</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#スタートアップコンフィグ">3.2. Startup config</div><div class="search_word">3.2. startup config startup-config is settings that are saved in flash rom or on the sd card, and the contents are preserved through reboot. when this product is started, the settings of startup-config are applied as the initial settings of running-config. this product can maintain five startup configs in flash rom and one startup config on the sd card. the startup-config in the unit’s flash rom is managed with an id of 0 to 4, and the config on the sd card is managed with the keyword “sd”. to specify which of the five types of config in the unit’s flash rom are used, use the startup-config select command. by default, sd is used. when executing the startup-config select command, the user selects whether to restart. if you don’t restart, no change occurs in the command setting. if you choose to restart, the unit restarts with the startup-config of the id specified by the user’s command. when updating from firmware rev.2.02.09 or earlier to firmware rev.2.02.10 or later, if startup-config select 0 is specified, the setting value will automatically be changed to startup-config select sd . therefore, if you are using the system with a microsd card containing config inserted, be aware that the system will boot from the sd card. this does not apply if you execute the startup-config select command with firmware rev.2.02.10 or later and then downgrade to firmware rev.2.02.09 or earlier. for easier management, you can use the startup-config description command to give each config a description (explanatory text) . if you attempt to start up in a state where startup-config does not exist, such as after executing the cold start command, the default-config is automatically applied. the running-config settings can be saved in startup-config by the copy running-config startup-config command or the write command. the contents of startup-config can be erased by the erase startup-config command, viewed by the show startup-config command, and copied by the copy startup-config command.</div><div class="display_word">3.2. Startup config startup-config is settings that are saved in flash ROM or on the SD card, and the contents are preserved through reboot. When this product is started, the settings of startup-config are applied as the initial settings of running-config. This product can maintain five startup configs in flash ROM and one startup config on the SD card. The startup-config in the unit’s flash ROM is managed with an ID of 0 to 4, and the config on the SD card is managed with the keyword “sd”. To specify which of the five types of config in the unit’s flash ROM are used, use the startup-config select command. By default, sd is used. When executing the startup-config select command, the user selects whether to restart. If you don’t restart, no change occurs in the command setting. If you choose to restart, the unit restarts with the startup-config of the ID specified by the user’s command. When updating from firmware Rev.2.02.09 or earlier to firmware Rev.2.02.10 or later, if startup-config select 0 is specified, the setting value will automatically be changed to startup-config select sd . Therefore, if you are using the system with a microSD card containing CONFIG inserted, be aware that the system will boot from the SD card. This does not apply if you execute the startup-config select command with firmware Rev.2.02.10 or later and then downgrade to firmware Rev.2.02.09 or earlier. For easier management, you can use the startup-config description command to give each config a Description (explanatory text) . If you attempt to start up in a state where startup-config does not exist, such as after executing the cold start command, the default-config is automatically applied. The running-config settings can be saved in startup-config by the copy running-config startup-config command or the write command. The contents of startup-config can be erased by the erase startup-config command, viewed by the show startup-config command, and copied by the copy startup-config command.</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#デフォルトコンフィグ">3.3. Default config</div><div class="search_word">3.3. default config default-config contains settings saved in internal flash rom that are needed for this product to operate minimally as a switch. like startup-config, the contents are preserved even after a restart. the factory settings are maintained as default-config. if startup-config does not exist when the system starts, default-config is copied to startup-config, and applied to running-config. the contents of default-config cannot be viewed.</div><div class="display_word">3.3. Default config default-config contains settings saved in internal flash ROM that are needed for this product to operate minimally as a switch. Like startup-config, the contents are preserved even after a restart. The factory settings are maintained as default-config. If startup-config does not exist when the system starts, default-config is copied to startup-config, and applied to running-config. The contents of default-config cannot be viewed.</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#起動時のコンフィグファイルの決定">3.4. Deciding the config file at startup</div><div class="search_word">3.4. deciding the config file at startup the following describes the flow for deciding the config file used when this product starts up. the startup-config select command setting value is referenced to determine the startup-config that will be used. if the startup-config select command has specified sd , and an sd card on which startup-config is saved is not inserted, then startup-config #0 is selected. if the startup-config that is determined exists, the corresponding data is applied as running-config in ram. if the startup-config determined according to the value of the startup-config select command does not exist in rom, then default-config is applied to ram. if startup using the config in the sd card fails, the following message is shown in the console and in syslog. loading config0 because can't read config in sd card.</div><div class="display_word">3.4. Deciding the config file at startup The following describes the flow for deciding the config file used when this product starts up. The startup-config select command setting value is referenced to determine the startup-config that will be used. If the startup-config select command has specified sd , and an SD card on which startup-config is saved is not inserted, then startup-config #0 is selected. If the startup-config that is determined exists, the corresponding data is applied as running-config in RAM. If the startup-config determined according to the value of the startup-config select command does not exist in ROM, then default-config is applied to RAM. If startup using the config in the SD card fails, the following message is shown in the console and in SYSLOG. Loading config0 because can't read config in SD card.</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#tftpによるコンフィグファイルの制御">3.5. Controlling the config file via TFTP</div><div class="search_word">3.5. controlling the config file via tftp if this product’s tftp server function is enabled, a tftp client installed on a pc or other remote terminal can be used to perform the following. acquire the currently running running-config and startup-config apply a previously prepared settings file as startup-config in order for the tftp server to function correctly, an ip address must be specified for the vlan. the settings files can be acquired/set from a remote terminal in binary mode. specify the following as the remote path of the acquisition source/transmission destination of the settings files. also, specify the administrative password in the form “/password” appended to the end of the remote path. however, the config file cannot be obtained or specified if the default administrative password is still specified. the administrative password setting must be changed in advance. the startup-config settings are applied as running-config after the system is restarted. target config target file remote path get (get) setting (put) automatic restart running-config config file (.txt) config yes yes - startup-config # 0 config file (.txt) config0 yes yes - all settings (.zip) config0-all yes yes - startup-config # 1 config file (.txt) config1 yes yes - all settings (.zip) config1-all yes yes - startup-config # 2 config file (.txt) config2 yes yes - all settings (.zip) config2-all yes yes - startup-config # 3 config file (.txt) config3 yes yes - all settings (.zip) config3-all yes yes - startup-config # 4 config file (.txt) config4 yes yes - all settings (.zip) config4-all yes yes - startup-config # sd config file (.txt) configsd yes yes - all settings (.zip) configsd-all yes yes - if you want to restart the system automatically after applying the settings file, specify the following remote path. the currently running configuration is applicable. target config target file remote path get (get) setting (put) automatic restart currently running startup-config config file (.txt) reconfig - yes yes when applying (put) a settings file, make sure that the target config and the target file type are correct. if an incorrect file is specified, the contents cannot be reflected correctly. for running-config, you need to add the following to the beginning of the settings file. !! switch configuration!</div><div class="display_word">3.5. Controlling the config file via TFTP If this product’s TFTP server function is enabled, a TFTP client installed on a PC or other remote terminal can be used to perform the following. Acquire the currently running running-config and startup-config Apply a previously prepared settings file as startup-config In order for the TFTP server to function correctly, an IP address must be specified for the VLAN. The settings files can be acquired/set from a remote terminal in binary mode. Specify the following as the remote path of the acquisition source/transmission destination of the settings files. Also, specify the administrative password in the form “/PASSWORD” appended to the end of the remote path. However, the config file cannot be obtained or specified if the default administrative password is still specified. The administrative password setting must be changed in advance. The startup-config settings are applied as running-config after the system is restarted. Target CONFIG Target file Remote path Get (GET) Setting (PUT) Automatic restart running-config CONFIG file (.txt) config Yes Yes - startup-config # 0 CONFIG file (.txt) config0 Yes Yes - All settings (.zip) config0-all Yes Yes - startup-config # 1 CONFIG file (.txt) config1 Yes Yes - All settings (.zip) config1-all Yes Yes - startup-config # 2 CONFIG file (.txt) config2 Yes Yes - All settings (.zip) config2-all Yes Yes - startup-config # 3 CONFIG file (.txt) config3 Yes Yes - All settings (.zip) config3-all Yes Yes - startup-config # 4 CONFIG file (.txt) config4 Yes Yes - All settings (.zip) config4-all Yes Yes - startup-config # SD CONFIG file (.txt) configsd Yes Yes - All settings (.zip) configsd-all Yes Yes - If you want to restart the system automatically after applying the settings file, specify the following remote path. The currently running configuration is applicable. Target CONFIG Target file Remote path Get (GET) Setting (PUT) Automatic restart Currently running startup-config CONFIG file (.txt) reconfig - Yes Yes When applying (PUT) a settings file, make sure that the target CONFIG and the target file type are correct. If an incorrect file is specified, the contents cannot be reflected correctly. For running-config, you need to add the following to the beginning of the settings file. !! Switch Configuration!</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details, refer to the command reference. operations operating commands save running config copy running-config startup-config save running config write copy startup config copy startup-config erase startup config erase startup-config show startup config show startup-config select startup config startup-config select set description for startup config startup-config description</div><div class="display_word">4. Related Commands Related commands are indicated below. For details, refer to the Command Reference. Operations Operating commands Save running config copy running-config startup-config Save running config write Copy startup config copy startup-config Erase startup config erase startup-config Show startup config show startup-config Select startup config startup-config select Set description for startup config startup-config description</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#スタートアップコンフィグの選択">5.1. Select startup config</div><div class="search_word">5.1. select startup config select startup-config #1 and restart the system. yamaha#startup-config description 1 test (1) yamaha#startup-config select 1 (2) reboot system? (y/n): y (3) 1 set the description “test” to startup-config #1 2 select startup-config #1 3 restart the system</div><div class="display_word">5.1. Select startup config Select startup-config #1 and restart the system. Yamaha#startup-config description 1 TEST (1) Yamaha#startup-config select 1 (2) reboot system? (y/n): y (3) 1 Set the description “TEST” to startup-config #1 2 Select startup-config #1 3 Restart the system</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#ランニングコンフィグの保存">5.2. Save running config</div><div class="search_word">5.2. save running config save running-config. yamaha#copy running-config startup-configsuceeded to write configurationyamaha#</div><div class="display_word">5.2. Save running config Save running-config. Yamaha#copy running-config startup-configSuceeded to write configurationYamaha#</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#スタートアップコンフィグのコピー">5.3. Copy startup config</div><div class="search_word">5.3. copy startup config copy startup-config #2 to the sd card. yamaha#copy startup-config 2 sd (1) suceeded to copy configurationyamaha#show startup-config sd (2) !!  last modified: tue mar 13 17:34:02 jst 2018!dns-client enable!interface port1.1 switchport switchport mode access no shutdown!... 1 copy startup-config #2 to the sd card 2 show startup-config on the sd card</div><div class="display_word">5.3. Copy startup config Copy startup-config #2 to the SD card. Yamaha#copy startup-config 2 sd (1) Suceeded to copy configurationYamaha#show startup-config sd (2) !!  Last Modified: Tue Mar 13 17:34:02 JST 2018!dns-client enable!interface port1.1 switchport switchport mode access no shutdown!... 1 Copy startup-config #2 to the SD card 2 Show startup-config on the SD card</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#スタートアップコンフィグの消去">5.4. Erase startup config</div><div class="search_word">5.4. erase startup config erase startup-config from the sd card. yamaha#erase startup-config sd (1) suceeded to erase configurationyamaha# 1 erase startup-config in the sd card</div><div class="display_word">5.4. Erase startup config Erase startup-config from the SD card. Yamaha#erase startup-config sd (1) Suceeded to erase configurationYamaha# 1 Erase startup-config in the SD card</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution none</div><div class="display_word">6. Points of Caution None</div></div><div id="oam_oam_config"><div class="search_title" docfname="oam_oam_config" doctitle="Config" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation use of external memory</div><div class="display_word">7. Related Documentation Use of External Memory</div></div><div id="oam_oam_default"><div class="search_title" docfname="oam_oam_default" doctitle="Default" link="#初期設定一覧">Default Settings List</div><div class="search_word">default settings list swx2310p series default settings are indicated below. system-wide default settings category setting parameter setting value console console timeout 600 sec number of vtys 8 number of lines displayed 24 password default administrative user user name: admin password: admin administrative password admin encrypt password not encrypted time management time zone jst (utc＋9.0) ntp server none ntp update cycle once per hour snmp action disabled rmon action enabled sflow action disabled syslog debug level log output off information level log output on error level log output on syslog server none firmware update download url firmware-update url http://www.rtpro.yamaha.co.jp/firmware/revision-up/swx2310p.bin permit downward revision prohibit timeout 300 sec lldp action enabled automatic setting function enabled l2ms action enabled role agent stacking action disabled stack id 1 ip address range used for stack port auto ip access control telnet server status start telnet server access allow only vlan #1 ssh server status do not start tftp server status do not start http server status start http server access allow only vlan #1 secure http server status do not start maintenance vlan vlan interface vlan #1 interface control link aggregation none port authentication disabled port security disabled poe supply enabled layer 2 functions automatic mac address acquisition enabled automatic mac address acquisition aging time 300 sec spanning tree enabled unique loop detection disabled multiple vlan none layer 3 functions static routing none routing between vlans disabled policy-based routing - ospf - rip - vrrp - ip multicast igmp snooping disabled mld snooping disabled igmp - pim - dns client action enabled traffic control qos disabled qos (dscp - transmission queue id conversion table) none flow control (ieee 802.3x) disabled acl none ap layer functionality dhcp server - dhcpv6 server - dhcp relay - dns relay - radius server disabled webgui language setting japanese default settings for each lan/sfp port category setting parameter setting value basic settings speed/communication mode setting auto cross/straight automatic detection enabled mru 1,522 byte port description none eee disabled port mode access associated vlan id 1 (default vlan) l2ms l2ms filter disabled l2 switching spanning tree enabled unique loop detection enabled traffic control qos trust mode cos flow control (ieee 802.3x) disabled storm control disabled lldp agent transmit/receive mode transmit and receive poe supply power supply actions enabled poe power priority low settings for default vlan (vlan1) category setting parameter setting value layer 3 functions ipv4 address 192.168.100.240/24 ip multicast multicast frame forwarding 239.192.128.250 (for y-unos) igmp snooping action disabled querier disabled fast-leave disabled check ttl enabled check ra disabled check tos disabled report-suppression enabled report-foward disabled mrouter-port data-suppression disabled mld snooping action disabled querier disabled fast-leave disabled</div><div class="display_word">Default Settings List SWX2310P series default settings are indicated below. System-wide default settings Category Setting Parameter Setting value Console Console timeout 600 sec Number of VTYs 8 Number of lines displayed 24 Password Default administrative user User name: admin Password: admin Administrative password admin Encrypt password Not encrypted Time Management Time zone JST (UTC＋9.0) NTP server None NTP update cycle Once per hour SNMP Action Disabled RMON Action Enabled sFlow Action Disabled SYSLOG debug level log output OFF information level log output ON error level log output ON SYSLOG server None Firmware Update Download URL firmware-update url http://www.rtpro.yamaha.co.jp/firmware/revision-up/swx2310p.bin Permit downward revision Prohibit Timeout 300 sec LLDP Action Enabled Automatic setting function Enabled L2MS Action Enabled Role Agent Stacking Action Disabled Stack ID 1 IP address range used for stack port Auto IP Access control Telnet server status Start Telnet server access Allow only VLAN #1 SSH server status Do not start TFTP server status Do not start HTTP server status Start HTTP server access Allow only VLAN #1 Secure HTTP server status Do not start Maintenance VLAN VLAN interface VLAN #1 Interface control Link aggregation None Port authentication Disabled Port security Disabled PoE supply Enabled Layer 2 functions Automatic MAC address acquisition Enabled Automatic MAC address acquisition aging time 300 sec Spanning tree Enabled Unique Loop Detection Disabled Multiple VLAN None Layer 3 functions Static routing None Routing between VLANs Disabled Policy-based routing - OSPF - RIP - VRRP - IP multicast IGMP snooping Disabled MLD snooping Disabled IGMP - PIM - DNS client Action Enabled Traffic control QoS Disabled QoS (DSCP - Transmission queue ID conversion table) None Flow control (IEEE 802.3x) Disabled ACL None AP layer functionality DHCP server - DHCPv6 server - DHCP relay - DNS relay - RADIUS server Disabled WebGUI Language setting Japanese Default settings for each LAN/SFP port Category Setting Parameter Setting value Basic settings Speed/communication mode setting auto Cross/straight automatic detection Enabled MRU 1,522 Byte Port description None EEE Disabled Port Mode Access Associated VLAN ID 1 (default VLAN) L2MS L2MS filter Disabled L2 switching Spanning tree Enabled Unique Loop Detection Enabled Traffic control QoS trust mode CoS Flow control (IEEE 802.3x) Disabled Storm Control Disabled LLDP agent Transmit/receive mode Transmit and receive PoE supply Power supply actions Enabled PoE power priority Low Settings for default VLAN (vlan1) Category Setting Parameter Setting value Layer 3 functions IPv4 address 192.168.100.240/24 IP multicast Multicast frame forwarding 239.192.128.250 (for Y-UNOS) IGMP Snooping Action Disabled Querier Disabled Fast-Leave Disabled Check TTL Enabled Check RA Disabled Check ToS Disabled Report-Suppression Enabled Report-Foward Disabled Mrouter-Port Data-Suppression Disabled MLD Snooping Action Disabled Querier Disabled Fast-Leave Disabled</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#ファームウェア更新">Firmware Update</div><div class="search_word">firmware update</div><div class="display_word">Firmware Update</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product offers the following two firmware update functions, in order to correct problems in the program and to add new functionality. firmware updates can be transmitted and applied to this product from a remote terminal such as a computer. this product’s built-in http client can access an http server, to download and apply the latest firmware. a firmware update placed on the sd card can be applied to this product. these update functions can be used to upgrade or downgrade the version of firmware used on this product. during firmware updating, all port leds flash green , regardless of the led display mode setting. when a stack is configured, the updated firmware is written simultaneously to the stack main and member switches. when successfully finished writing the updated firmware, the system is automatically rebooted in order to apply the new firmware . for instructions on how to specify rebooting the system, refer to reboot after writing .</div><div class="display_word">1. Function Overview This product offers the following two firmware update functions, in order to correct problems in the program and to add new functionality. Firmware updates can be transmitted and applied to this product from a remote terminal such as a computer. This product’s built-in HTTP client can access an HTTP server, to download and apply the latest firmware. A firmware update placed on the SD card can be applied to this product. These update functions can be used to upgrade or downgrade the version of firmware used on this product. During firmware updating, all port LEDs flash green , regardless of the LED display mode setting. When a stack is configured, the updated firmware is written simultaneously to the stack main and member switches. When successfully finished writing the updated firmware, the system is automatically rebooted in order to apply the new firmware . For instructions on how to specify rebooting the system, refer to Reboot after writing .</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used none</div><div class="display_word">2. Definition of Terms Used None</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#更新ファームウェア送付による更新">3.1. Update by transmitting the firmware update</div><div class="search_word">3.1. update by transmitting the firmware update this function transmits firmware updates to this product from a remote terminal, such as a computer, and applies it as boot firmware. the update process is executed using a tftp client or the web gui .</div><div class="display_word">3.1. Update by transmitting the firmware update This function transmits firmware updates to this product from a remote terminal, such as a computer, and applies it as boot firmware. The update process is executed using a TFTP client or the Web GUI .</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#tftpクライアントを使用したファームウェア更新">3.1.1. Using a TFTP client to update the firmware</div><div class="search_word">3.1.1. using a tftp client to update the firmware firmware can be updated by using a tftp client installed on a computer or other remote terminal to transmit the updated firmware to this device. in order to operate this product’s tftp server, use the steps shown below to set up a network environment that allows remote access. decide on the vlan that will be used for maintenance. set the ipv4 address on the maintenance vlan. set it using the ip address command. permit access from the maintenance vlan to the tftp server. use the tftp-server interface command or the management interface command to specify that setting. enable the tftp server. enable the server using the tftp-server enable command. follow the rules below when sending the firmware update using the tftp client. set the transmission mode to “ binary mode ”. as shown in the table below, specify the remote path to which the firmware update is sent. specify the administrative password in the form “/password” at the end of the remote path. however, the firmware update cannot be applied if the administrative password is still set to the default setting. the administrative password setting must be changed in advance. when updating firmware that uses tftp clients, the following three types of updates are possible. updated firmware type remote path internal firmware exec if there is no problem with the firmware update that was sent, the firmware update will be saved.</div><div class="display_word">3.1.1. Using a TFTP client to update the firmware Firmware can be updated by using a TFTP client installed on a computer or other remote terminal to transmit the updated firmware to this device. In order to operate this product’s TFTP server, use the steps shown below to set up a network environment that allows remote access. Decide on the VLAN that will be used for maintenance. Set the IPv4 address on the maintenance VLAN. Set it using the ip address command. Permit access from the maintenance VLAN to the TFTP server. Use the tftp-server interface command or the management interface command to specify that setting. Enable the TFTP server. Enable the server using the tftp-server enable command. Follow the rules below when sending the firmware update using the TFTP client. Set the transmission mode to “ binary mode ”. As shown in the table below, specify the remote path to which the firmware update is sent. Specify the administrative password in the form “/PASSWORD” at the end of the remote path. However, the firmware update cannot be applied if the administrative password is still set to the default setting. The administrative password setting must be changed in advance. When updating firmware that uses TFTP clients, the following three types of updates are possible. Updated firmware Type Remote path Internal firmware exec If there is no problem with the firmware update that was sent, the firmware update will be saved.</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#web-gui-ローカルファイル指定によるファームウェア更新">3.1.2. Updating the firmware by specifying a local file in the Web GUI</div><div class="search_word">3.1.2. updating the firmware by specifying a local file in the web gui specify the firmware update located on the terminal accessing the web gui, and apply it to this product. this function does not do a version comparison with the existing firmware, and will overwrite the specified firmware regardless of version. to update firmware by specifying a local file, click [maintenance] - [firmware update] in the web gui on the computer. (refer to the part shown in a red frame on the screenshot below.) refer to the help contents within the gui for the specific operation method. initial screen on the web gui for updating firmware using a computer</div><div class="display_word">3.1.2. Updating the firmware by specifying a local file in the Web GUI Specify the firmware update located on the terminal accessing the Web GUI, and apply it to this product. This function does not do a version comparison with the existing firmware, and will overwrite the specified firmware regardless of version. To update firmware by specifying a local file, click [Maintenance] - [Firmware update] in the Web GUI on the computer. (Refer to the part shown in a red frame on the screenshot below.) Refer to the help contents within the GUI for the specific operation method. Initial screen on the Web GUI for updating firmware using a computer</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#httpクライアントを使用した更新">3.2. Using an HTTP client to update the firmware</div><div class="search_word">3.2. using an http client to update the firmware this method of firmware update uses an http client to obtain the firmware update from a specified url, and then apply it to this product. this function assumes that the firmware version will be upgraded. downgrading to a previous version will only be permitted if “revision-down” is allowed. the firmware cannot be rewritten with the same version of firmware. this function cannot be used when the stack is enabled. an http client can be used to update the firmware using the methods below. use the firmware-update command in the cli (command-line interface). execute update firmware via network in the web gui. updating the firmware with an http client is done by using the settings value shown in the table below. setting parameter explanation download source url sets the source url from which the firmware is downloaded. a url of up to 255 characters in length can be set. the input format is “\http://ipv4/ipv6 address of the server” or “\http://hostname/path name”. if an ipv6 address is specified, it must be enclosed in square brackets like “[ipv6 address]”. if the server port number is other than 80, it must be specified within the url in the form “\http://ip address of the server:port number/path name” or “\http://hostname:port number/path name”. default value settings are specified in the following location. http://www.rtpro.yamaha.co.jp/firmware/revision-up/swx2310p.bin proxy server url specifies the proxy server to use for updating firmware. specify it either as an ipv4/ipv6 address or fqdn. fqdns can be up to 255 characters long. no proxy server is specified in default settings. proxy servers must be specified as an ipv4/ipv6 address or in the form “\http://hostname/path name port number”. if an ipv6 address is specified, it must be enclosed in square brackets like “[ipv6 address]”. permit downward revision sets whether the current version of firmware can be downgraded to a previous version. the default value is “don’t allow”. overwriting the firmware with the same version of firmware is not permitted. timeout specifies the timer for monitoring the completion of the processes shown below. * version check of old and new firmware * the download monitoring timer from the specified url can be specified from 100 seconds to 86,400 seconds , and the initial setting is set to 300 seconds . for instructions on using the firmware-update command, refer to “ examples of command execution ” or the “ command reference ”. to update firmware over the network using the web gui, execute [maintenance] - [firmware update] on the web gui. (refer to the part shown in a red frame on the screenshot below.) refer to the help contents within the gui for the specific operation method. initial web gui screen for updating firmware via the network</div><div class="display_word">3.2. Using an HTTP client to update the firmware This method of firmware update uses an HTTP client to obtain the firmware update from a specified URL, and then apply it to this product. This function assumes that the firmware version will be upgraded. Downgrading to a previous version will only be permitted if “revision-down” is allowed. The firmware cannot be rewritten with the same version of firmware. This function cannot be used when the stack is enabled. An HTTP client can be used to update the firmware using the methods below. Use the firmware-update command in the CLI (command-line interface). Execute update firmware via network in the Web GUI. Updating the firmware with an HTTP client is done by using the settings value shown in the table below. Setting parameter Explanation Download source URL Sets the source URL from which the firmware is downloaded. A URL of up to 255 characters in length can be set. The input format is “\http://IPv4/IPv6 address of the server” or “\http://hostname/path name”. If an IPv6 address is specified, it must be enclosed in square brackets like “[IPv6 address]”. If the server port number is other than 80, it must be specified within the URL in the form “\http://IP address of the server:port number/path name” or “\http://hostname:port number/path name”. Default value settings are specified in the following location. http://www.rtpro.yamaha.co.jp/firmware/revision-up/swx2310p.bin Proxy Server URL Specifies the proxy server to use for updating firmware. Specify it either as an IPv4/IPv6 address or FQDN. FQDNs can be up to 255 characters long. No proxy server is specified in default settings. Proxy servers must be specified as an IPv4/IPv6 address or in the form “\http://hostname/path name port number”. If an IPv6 address is specified, it must be enclosed in square brackets like “[IPv6 address]”. Permit downward revision Sets whether the current version of firmware can be downgraded to a previous version. The default value is “Don’t allow”. Overwriting the firmware with the same version of firmware is not permitted. Timeout Specifies the timer for monitoring the completion of the processes shown below. * Version check of old and new firmware * The download monitoring timer from the specified URL can be specified from 100 seconds to 86,400 seconds , and the initial setting is set to 300 seconds . For instructions on using the firmware-update command, refer to “ Examples of Command Execution ” or the “ Command Reference ”. To update firmware over the network using the Web GUI, execute [Maintenance] - [Firmware update] on the Web GUI. (Refer to the part shown in a red frame on the screenshot below.) Refer to the help contents within the GUI for the specific operation method. Initial Web GUI Screen for Updating Firmware via the Network</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#sdカードを使用した更新">3.3. Update using an SD card</div><div class="search_word">3.3. update using an sd card the firmware stored on the sd card inserted in the unit will be applied as the updated firmware. this update is performed from the cli (command-line interface) using the firmware-update sd execute command. if a stack was configured, commands can only be executed from the main switch in the stack. after entering the firmware update confirmation, the update will continue even if the sd card is removed. to unmount the sd card when executing the command, enter “n” in the confirmation of continued sd card mounting status, or specify the “sd-unmount” option with the command. if the system is rebooted with the sd card inserted in the main unit, the system will be booted using the firmware in the sd card, as specified by the boot prioritize sd command. file path in sd card /swx2310p/firmware/swx2310p.bin</div><div class="display_word">3.3. Update using an SD card The firmware stored on the SD card inserted in the unit will be applied as the updated firmware. This update is performed from the CLI (Command-line interface) using the firmware-update sd execute command. If a stack was configured, commands can only be executed from the main switch in the stack. After entering the firmware update confirmation, the update will continue even if the SD card is removed. To unmount the SD card when executing the command, enter “N” in the confirmation of continued SD card mounting status, or specify the “sd-unmount” option with the command. If the system is rebooted with the SD card inserted in the main unit, the system will be booted using the firmware in the SD card, as specified by the boot prioritize sd command. File path in SD card /swx2310p/firmware/swx2310p.bin</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#書き込み後の再起動">3.4. Reboot after writing</div><div class="search_word">3.4. reboot after writing when successfully finished writing the firmware update, the system is automatically rebooted. however, the system is not rebooted if the “no-reboot” option is specified for firmware-update execute or firmware-update sd execute commands. if the firmware-update reload-time command is specified without specifying the “no-reboot” option, then the system is rebooted according to the reboot time setting. the revision after the next reboot can be confirmed by executing the show firmware-update command. if a stack is configured, the firmware update method can be selected using the firmware-update reload-method command. how to simultaneously update member switches in a configuration how to update without stopping network services for an operation overview of the firmware update methods, refer to firmware update in the stack public technical data .</div><div class="display_word">3.4. Reboot after writing When successfully finished writing the firmware update, the system is automatically rebooted. However, the system is not rebooted if the “no-reboot” option is specified for firmware-update execute or firmware-update sd execute commands. If the firmware-update reload-time command is specified without specifying the “no-reboot” option, then the system is rebooted according to the reboot time setting. The revision after the next reboot can be confirmed by executing the show firmware-update command. If a stack is configured, the firmware update method can be selected using the firmware-update reload-method command. How to simultaneously update member switches in a configuration How to update without stopping network services For an operation overview of the firmware update methods, refer to Firmware Update in the stack public technical data .</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details, refer to the command reference. operations operating commands set firmware update site firmware-update url set proxy server firmware-update http-proxy execute firmware update firmware-update execute set firmware download timeout duration firmware-update timeout permit downward revision firmware-update revision-down show firmware update function settings show firmware-update execute firmware update from sd card firmware-update sd execute set firmware update reboot time firmware-update reload-time set the firmware update restart method during stack configuration firmware-update reload-method</div><div class="display_word">4. Related Commands Related commands are indicated below. For details, refer to the Command Reference. Operations Operating commands Set firmware update site firmware-update url Set proxy server firmware-update http-proxy Execute firmware update firmware-update execute Set firmware download timeout duration firmware-update timeout Permit downward revision firmware-update revision-down Show firmware update function settings show firmware-update Execute firmware update from SD card firmware-update sd execute Set firmware update reboot time firmware-update reload-time Set the firmware update restart method during stack configuration firmware-update reload-method</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#httpクライアントを使用した更新">5.1. Using an HTTP client to update the firmware</div><div class="search_word">5.1. using an http client to update the firmware in this example, the firmware update is stored on the local http server, and this product is set to manage the firmware in order to perform the update. change the download url to http://192.168.100.1/swx2310p.bin . the downward revision setting is left disabled . the timeout value is left at 300 sec . a reboot time is not specified, but the system is rebooted immediately after updates . the download url is changed, and the firmware update settings are confirmed. yamaha(config)#firmware-update url http://192.168.100.1/swx3210p.bin (1) yamaha(config)#exit    yamaha#show firmware-update (2) url:http://192.168.100.1/swx2310p.bin    http-proxy: -    timeout: 300 (seconds)    revision-down: disable    firmware revision for next boot: -    reload-time: -    reload-method: normal 1 set download source url 2 show firmware update function settings the firmware update is executed. yamaha#firmware-update execute (1) found the new revision firmware    current revision: rev.2.02.01    new revision:     rev.2.02.03    downloading...    update to this firmware? (y/n)y (2) updating...    finish (3) 1 execute firmware update 2 enter y 3 the system automatically reboots pressing “ctrl+c” during the firmware update process will interrupt the update. yamaha#firmware-update execute    found the new revision firmware    current revision: rev.2.02.01    new revision:     rev.2.02.03    downloading... (1) ^ccanceled the firmware download 1 press the ctrl and c keys</div><div class="display_word">5.1. Using an HTTP client to update the firmware In this example, the firmware update is stored on the local HTTP server, and this product is set to manage the firmware in order to perform the update. Change the download URL to http://192.168.100.1/swx2310p.bin . The downward revision setting is left disabled . The timeout value is left at 300 sec . A reboot time is not specified, but the system is rebooted immediately after updates . The download URL is changed, and the firmware update settings are confirmed. Yamaha(config)#firmware-update url http://192.168.100.1/swx3210p.bin (1) Yamaha(config)#exit    Yamaha#show firmware-update (2) url:http://192.168.100.1/swx2310p.bin    http-proxy: -    timeout: 300 (seconds)    revision-down: Disable    firmware revision for next boot: -    reload-time: -    reload-method: Normal 1 Set download source URL 2 Show firmware update function settings The firmware update is executed. Yamaha#firmware-update execute (1) Found the new revision firmware    Current Revision: Rev.2.02.01    New Revision:     Rev.2.02.03    Downloading...    Update to this firmware? (y/n)y (2) Updating...    Finish (3) 1 Execute firmware update 2 Enter y 3 The system automatically reboots Pressing “CTRL+C” during the firmware update process will interrupt the update. Yamaha#firmware-update execute    Found the new revision firmware    Current Revision: Rev.2.02.01    New Revision:     Rev.2.02.03    Downloading... (1) ^CCanceled the firmware download 1 Press the Ctrl and C keys</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#httpクライアントを使用した更新プロキシー環境下">5.2. Using an HTTP client to update the firmware (in a proxy server environment)</div><div class="search_word">5.2. using an http client to update the firmware (in a proxy server environment) this updates the firmware by specifying a proxy server. the initial download url setting is left unchanged. the proxy server is set to http://192.168.100.1:8080 . the downward revision setting is left disabled . the timeout value is left at 300 sec . a reboot time is not specified, but the system is rebooted immediately after updates . specify the http proxy settings and confirm the firmware update settings. yamaha(config)#firmware-update http-proxy http://192.168.100.1 8080 (1) yamaha(config)#exit    yamaha#show firmware-update (2) url: http://www.rtpro.yamaha.co.jp/firmware/revision-up/swx3220.bin    http-proxy: http://192.168.100.1:8080    timeout: 300 (seconds)    revision-down: disable    firmware revision for next boot: -    reload-time: -    reload-method: normal 1 set http proxy 2 show firmware update function settings the firmware update is executed. yamaha#firmware-update execute (1) found the new revision firmware    current revision: rev.2.02.01    new revision:     rev.2.02.03    downloading...    update to this firmware? (y/n)y (2) updating...    finish (3) 1 execute firmware update 2 enter y 3 the system automatically reboots</div><div class="display_word">5.2. Using an HTTP client to update the firmware (in a proxy server environment) This updates the firmware by specifying a proxy server. The initial download URL setting is left unchanged. The proxy server is set to http://192.168.100.1:8080 . The downward revision setting is left disabled . The timeout value is left at 300 sec . A reboot time is not specified, but the system is rebooted immediately after updates . Specify the HTTP proxy settings and confirm the firmware update settings. Yamaha(config)#firmware-update http-proxy http://192.168.100.1 8080 (1) Yamaha(config)#exit    Yamaha#show firmware-update (2) url: http://www.rtpro.yamaha.co.jp/firmware/revision-up/swx3220.bin    http-proxy: http://192.168.100.1:8080    timeout: 300 (seconds)    revision-down: Disable    firmware revision for next boot: -    reload-time: -    reload-method: Normal 1 Set HTTP proxy 2 Show firmware update function settings The firmware update is executed. Yamaha#firmware-update execute (1) Found the new revision firmware    Current Revision: Rev.2.02.01    New Revision:     Rev.2.02.03    Downloading...    Update to this firmware? (y/n)y (2) Updating...    Finish (3) 1 Execute firmware update 2 Enter y 3 The system automatically reboots</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#sdカードを使用した更新">5.3. Update using an SD card</div><div class="search_word">5.3. update using an sd card in this example, the firmware update is placed on an sd card inserted in the unit, and this product is set to manage the firmware in order to perform the update. this is an example of a two-stack configuration. change the reboot time to 23:30 . change the reboot method to reboot the stack main and member switches sequentially . change the reboot time and reboot method. yamaha(config)#firmware-update reload-time 23 30 (1) yamaha(config)#firmware-update reload-method sequential (2) yamaha(config)#exit 1 set the reboot time 2 set the reboot method insert the sd card into the main switch in the stack and execute the firmware update. yamaha#firmware-update sd execute (1) update the firmware.    current revision: rev.2.02.01    new revision:     rev.2.02.03    update to this firmware? (y/n)y (2) continue without unmounting the sd card? (y/n)n (3) unmounted the sd card.  pull out the sd card.    updating...    finish    yamaha#    (reboots at specified reboot time) 1 execute firmware update 2 enter y 3 enter n the stack member firmware is updated at the same time as the stack main switch, but the members are rebooted after the firmware in the stack main switch has been rebooted. the following log history is displayed on stack member consoles. (press enter on the stack main. the firmware is received and the update starts.)    receiving exec file...    testing received file...    writing to nonvolatile memory...    done.    (wait for restart of stack main then reboot) after checking the version of the update firmware, you can enter “n” to cancel. yamaha#firmware-update sd execute (1) update the firmware.    current revision: rev.2.02.01    new revision:     rev.2.02.03    update to this firmware? (y/n)n (2) yamaha# 1 execute firmware update 2 enter n</div><div class="display_word">5.3. Update using an SD card In this example, the firmware update is placed on an SD card inserted in the unit, and this product is set to manage the firmware in order to perform the update. This is an example of a two-stack configuration. Change the reboot time to 23:30 . Change the reboot method to reboot the stack main and member switches sequentially . Change the reboot time and reboot method. Yamaha(config)#firmware-update reload-time 23 30 (1) Yamaha(config)#firmware-update reload-method sequential (2) Yamaha(config)#exit 1 Set the reboot time 2 Set the reboot method Insert the SD card into the main switch in the stack and execute the firmware update. Yamaha#firmware-update sd execute (1) Update the firmware.    Current Revision: Rev.2.02.01    New Revision:     Rev.2.02.03    Update to this firmware? (y/n)y (2) Continue without unmounting the SD card? (y/n)n (3) Unmounted the SD card.  Pull out the SD card.    Updating...    Finish    Yamaha#    (Reboots at specified reboot time) 1 Execute firmware update 2 Enter y 3 Enter n The stack member firmware is updated at the same time as the stack main switch, but the members are rebooted after the firmware in the stack main switch has been rebooted. The following log history is displayed on stack member consoles. (Press ENTER on the stack main. The firmware is received and the update starts.)    Receiving exec file...    Testing received file...    Writing to Nonvolatile memory...    Done.    (Wait for restart of stack main then reboot) After checking the version of the update firmware, you can enter “n” to cancel. Yamaha#firmware-update sd execute (1) Update the firmware.    Current Revision: Rev.2.02.01    New Revision:     Rev.2.02.03    Update to this firmware? (y/n)n (2) Yamaha# 1 Execute firmware update 2 Enter n</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution if the system is rebooted or the power is turned off during firmware update, the update will be interrupted and the system will start with the firmware before the update operation.</div><div class="display_word">6. Points of Caution If the system is rebooted or the power is turned off during firmware update, the update will be interrupted and the system will start with the firmware before the update operation.</div></div><div id="oam_oam_firm_up"><div class="search_title" docfname="oam_oam_firm_up" doctitle="Firmware" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation maintenance and operation functions: led control</div><div class="display_word">7. Related Documentation Maintenance and Operation Functions: LED Control</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#l2ms-layer2-management-service">L2MS (Layer2 Management Service)</div><div class="search_word">l2ms (layer2 management service)</div><div class="display_word">L2MS (Layer2 Management Service)</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#機能概要">1. Function Overview</div><div class="search_word">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 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.</div><div class="display_word">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 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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">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.</div><div class="display_word">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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#対応機種">3.1. Compatible models</div><div class="search_word">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 .</div><div class="display_word">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 .</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#使用方法">3.2. Usage</div><div class="search_word">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 configurationyamaha(config-l2ms)#l2ms enableyamaha(config-l2ms)#l2ms role manageryamaha(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 configurationyamaha(config-l2ms)#l2ms enableyamaha(config-l2ms)#l2ms role agent the show l2ms command can be used to check a current action and role of the agents.</div><div class="display_word">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 configurationYamaha(config-l2ms)#l2ms enableYamaha(config-l2ms)#l2ms role managerYamaha(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 configurationYamaha(config-l2ms)#l2ms enableYamaha(config-l2ms)#l2ms role agent The show l2ms command can be used to check a current action and role of the agents.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#l2msのプロトコル">3.3. L2MS protocol</div><div class="search_word">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.</div><div class="display_word">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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#エージェントの監視">3.4. Monitoring agents</div><div class="search_word">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.</div><div class="display_word">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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#エージェントの占有">3.5. Agent ownership</div><div class="search_word">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.</div><div class="display_word">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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#エージェントの操作">3.6. Agent operations</div><div class="search_word">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.</div><div class="display_word">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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#swx2100シリーズに対する操作">3.6.1. Operations for SWX2100 series units</div><div class="search_word">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.)</div><div class="display_word">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.)</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#swx2110swx2110pシリーズに対する操作">3.6.2. Operations for SWX2110 and SWX2110P series units</div><div class="search_word">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</div><div class="display_word">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</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#swx2200シリーズに対する操作">3.6.3. Operations for SWX2200 series units</div><div class="search_word">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.</div><div class="display_word">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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#swx2210swx2210pswx2220swx2221pswx2220pシリーズに対する操作">3.6.4. Operations for SWX2210, SWX2210P, SWX2220, SWX2221P, and SWX2220P series units</div><div class="search_word">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.</div><div class="display_word">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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#swx2300swx2310swx2310pswx2320swx2322pswx3100swx3200swx3220シリーズに対する操作">3.6.5. Operations for SWX2300, SWX2310, SWX2310P, SWX2320, SWX2322P, SWX3100, SWX3200, and SWX3220 series units</div><div class="search_word">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.”</div><div class="display_word">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.”</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#wlxシリーズに対する操作">3.6.6. Operations for WLX series units</div><div class="search_word">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.”</div><div class="display_word">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.”</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#設定の同期">3.6.7. Synchronizing settings</div><div class="search_word">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. all swx2200 settings are restored to default values. 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.</div><div class="display_word">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. All SWX2200 settings are restored to default values. 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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#http-proxy機能およびipアドレスの設定について">3.6.8. HTTP Proxy Function and Setting IP Addresses</div><div class="search_word">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.</div><div class="display_word">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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#エージェントからの情報通知">3.7. Information notifications from agents</div><div class="search_word">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</div><div class="display_word">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</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#接続端末の監視">3.8. Monitoring connected terminals</div><div class="search_word">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</div><div class="display_word">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</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#関連コマンド">4. Related Commands</div><div class="search_word">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</div><div class="display_word">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</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#エージェントの監視設定">5.1. Monitoring settings for agents</div><div class="search_word">5.1. monitoring settings for agents set the agent monitoring time interval. yamaha(config)#l2ms configurationyamaha(config-l2ms)#agent-watch interval 8 set the number of monitoring times before deciding an agent is down. yamaha(config)#l2ms configurationyamaha(config-l2ms)#agent-watch down-count 7</div><div class="display_word">5.1. Monitoring settings for agents Set the agent monitoring time interval. Yamaha(config)#l2ms configurationYamaha(config-l2ms)#agent-watch interval 8 Set the number of monitoring times before deciding an agent is down. Yamaha(config)#l2ms configurationYamaha(config-l2ms)#agent-watch down-count 7</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#端末の管理機能の設定">5.2. Enable terminal management function</div><div class="search_word">5.2. enable terminal management function enable the terminal monitoring function. yamaha(config)#l2ms configurationyamaha(config-l2ms)#terminal-watch enable set the time interval for acquiring terminal information. yamaha(config)#l2ms configurationyamaha(config-l2ms)#terminal-watch interval 3600 show the terminal information obtained by the manager. yamaha>show l2ms detailrole : 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</div><div class="display_word">5.2. Enable terminal management function Enable the terminal monitoring function. Yamaha(config)#l2ms configurationYamaha(config-l2ms)#terminal-watch enable Set the time interval for acquiring terminal information. Yamaha(config)#l2ms configurationYamaha(config-l2ms)#terminal-watch interval 3600 Show the terminal information obtained by the manager. Yamaha>show l2ms detailRole : 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</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#l2ms制御フレームの送受信設定">5.3. Enable sending/receiving L2MS control frames</div><div class="search_word">5.3. enable sending/receiving l2ms control frames disable sending or receiving l2ms control frames at port1.5. yamaha(config)#interface port1.5yamaha(config-if)#l2ms filter enable</div><div class="display_word">5.3. Enable sending/receiving L2MS control frames Disable sending or receiving L2MS control frames at port1.5. Yamaha(config)#interface port1.5Yamaha(config-if)#l2ms filter enable</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#イベント監視機能の設定">5.4. Enable event monitoring function</div><div class="search_word">5.4. enable event monitoring function disable the event monitoring function. yamaha(config)#l2ms configurationyamaha(config-l2ms)#event-watch disable set the time interval between acquiring event information. yamaha(config)#l2ms configurationyamaha(config-l2ms)#event-watch interval 60</div><div class="display_word">5.4. Enable event monitoring function Disable the event monitoring function. Yamaha(config)#l2ms configurationYamaha(config-l2ms)#event-watch disable Set the time interval between acquiring event information. Yamaha(config)#l2ms configurationYamaha(config-l2ms)#event-watch interval 60</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#ゼロコンフィグ機能の使用の有無">5.5. Enabling/disabling the zero-config function</div><div class="search_word">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 configurationyamaha(config-l2ms)#l2ms enableyamaha(config-l2ms)#l2ms role manageryamaha(config-l2ms)#config-auto-set disable</div><div class="display_word">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 configurationYamaha(config-l2ms)#l2ms enableYamaha(config-l2ms)#l2ms role managerYamaha(config-l2ms)#config-auto-set disable</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution</div><div class="display_word">6. Points of Caution</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#機器構成について">6.1. Device configuration</div><div class="search_word">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.</div><div class="display_word">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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#端末の監視について">6.2. Terminal monitoring</div><div class="search_word">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.</div><div class="display_word">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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#他機能との併用について">6.3. Use in conjunction with other functionality</div><div class="search_word">6.3. use in conjunction with other functionality</div><div class="display_word">6.3. Use in conjunction with other functionality</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#vlanとの併用">6.3.1. Use in conjunction with a VLAN</div><div class="search_word">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.</div><div class="display_word">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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#ミラーリングとの併用">6.3.2. Use in conjunction with mirroring</div><div class="search_word">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.</div><div class="display_word">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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#aclとの併用">6.3.3. Use in conjunction with an ACL</div><div class="search_word">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.</div><div class="display_word">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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#stpループ検出機能との併用">6.3.4. Use in conjunction with STP or loop detection functionality</div><div class="search_word">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).</div><div class="display_word">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).</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#リンクアグリゲーションとの併用">6.3.5. Use in conjunction with link aggregation</div><div class="search_word">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.</div><div class="display_word">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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#スタック機能との併用">6.3.6. Use in conjunction with the stack function</div><div class="search_word">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.</div><div class="display_word">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.</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#syslogメッセージ一覧">7. SYSLOG Message List</div><div class="search_word">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)</div><div class="display_word">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)</div></div><div id="oam_oam_l2ms"><div class="search_title" docfname="oam_oam_l2ms" doctitle="L2MS" link="#関連文書">8. Related Documentation</div><div class="search_word">8. related documentation switch control functions of yamaha routers</div><div class="display_word">8. Related Documentation Switch control functions of Yamaha routers</div></div><div id="oam_oam_ladm"><div class="search_title" docfname="oam_oam_ladm" doctitle="Terminal" link="#端末監視">Terminal Monitoring</div><div class="search_word">terminal monitoring</div><div class="display_word">Terminal Monitoring</div></div><div id="oam_oam_ladm"><div class="search_title" docfname="oam_oam_ladm" doctitle="Terminal" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview the terminal monitoring function checks the dead-or-alive state of specific terminals connected to the network switch. the operating specifications for the terminal monitoring function are shown below. terminal monitoring function overview example of an l2ms manager with an l3 switch and an l2ms agent with an intelligent l2 poe switch as dead/alive monitoring methods, the following three types are provided. ping-based communication monitoring ping (icmp echo request/reply) is issued at regular intervals to a terminal that has an ip address, and the terminal is determined to be down if there is no longer a response. the user can specify the ping response wait time and the number of failures before the connection is determined to be down. frame reception volume monitoring the frame reception volume is monitored at regular intervals for an individual port, and the terminal is determined to be down if the traffic falls below a specified volume. the user can specify the monitoring start threshold value and the threshold value at which a down condition is determined. monitoring starts when the traffic exceeds the monitoring start threshold value, and a down condition is determined when the traffic falls below the down decision threshold. lldp reception interval monitoring the lldp received at regular intervals by an individual port is monitored. using the ttl which is a required item in the data portion of an lldp packet, a down condition is determined if lldp is not received within the ttl interval. if monitoring detects a terminal fault (down), the following processing is automatically performed. alert display in the dashboard screen an indication that a fault (down) occurred for the monitored terminal is displayed in the alert screen of the dashboard. alert shown in lan map screen if the network switch monitoring the terminal is an l2ms manager lan map notification and history information are used to indicate an error (down) occurred in a monitored terminal. if the network switch monitoring the terminal is an l2ms agent the l2ms trap function is used to notify the l2ms manager. when the l2ms manager receives a notification, it uses the lan map screen to indicate an error (down) occurred in a monitored terminal. by the user’s choice , the following operations can be applied in parallel. fault detection notification by mail notification that a monitored terminal has experienced a fault is sent to the desired recipient. notification to an snmp manager a trap is sent to the snmp manager specified by a command. restart of a terminal due to temporary stop of poe supply if a down condition is detected on a port to which poe power is being supplied, poe power supply is temporarily turned off in an attempt to recover the monitored terminal.</div><div class="display_word">1. Function Overview The terminal monitoring function checks the dead-or-alive state of specific terminals connected to the network switch. The operating specifications for the terminal monitoring function are shown below. Terminal monitoring function overview Example of an L2MS manager with an L3 switch and an L2MS agent with an intelligent L2 PoE switch As dead/alive monitoring methods, the following three types are provided. Ping-based communication monitoring Ping (ICMP Echo request/reply) is issued at regular intervals to a terminal that has an IP address, and the terminal is determined to be down if there is no longer a response. The user can specify the ping response wait time and the number of failures before the connection is determined to be down. Frame reception volume monitoring The frame reception volume is monitored at regular intervals for an individual port, and the terminal is determined to be down if the traffic falls below a specified volume. The user can specify the monitoring start threshold value and the threshold value at which a down condition is determined. Monitoring starts when the traffic exceeds the monitoring start threshold value, and a down condition is determined when the traffic falls below the down decision threshold. LLDP reception interval monitoring The LLDP received at regular intervals by an individual port is monitored. Using the TTL which is a required item in the data portion of an LLDP packet, a down condition is determined if LLDP is not received within the TTL interval. If monitoring detects a terminal fault (down), the following processing is automatically performed. Alert display in the dashboard screen An indication that a fault (down) occurred for the monitored terminal is displayed in the alert screen of the dashboard. Alert shown in LAN map screen If the network switch monitoring the terminal is an L2MS manager LAN map notification and history information are used to indicate an error (down) occurred in a monitored terminal. If the network switch monitoring the terminal is an L2MS agent The L2MS trap function is used to notify the L2MS manager. When the L2MS manager receives a notification, it uses the LAN map screen to indicate an error (down) occurred in a monitored terminal. By the user’s choice , the following operations can be applied in parallel. Fault detection notification by mail Notification that a monitored terminal has experienced a fault is sent to the desired recipient. Notification to an SNMP manager A trap is sent to the SNMP manager specified by a command. Restart of a terminal due to temporary stop of PoE supply If a down condition is detected on a port to which PoE power is being supplied, PoE power supply is temporarily turned off in an attempt to recover the monitored terminal.</div></div><div id="oam_oam_ladm"><div class="search_title" docfname="oam_oam_ladm" doctitle="Terminal" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used none</div><div class="display_word">2. Definition of Terms Used None</div></div><div id="oam_oam_ladm"><div class="search_title" docfname="oam_oam_ladm" doctitle="Terminal" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_ladm"><div class="search_title" docfname="oam_oam_ladm" doctitle="Terminal" link="#ping-icmp-echo-request-reply-による監視">3.1. Monitoring by ping (ICMP Echo request/reply)</div><div class="search_word">3.1. monitoring by ping (icmp echo request/reply) specifications for terminal monitoring by ping are given below. the interval of icmp echo request transmission from the network switch is fixed at 5 sec . the icmp echo request that is transmitted has the following format. as the id field of the icmp header, the unique id assigned to each monitored terminal is specified. as the sequence field of the icmp header, a number that is sequentially incremented from 0 is specified. the validity of the icmp echo reply is checked as follows. whether the id field of the icmp header contains the id that was specified when sending the request whether the sequence field of the icmp header contains the sequence number that was specified when sending the request the wait time for icmp echo reply can be changed in the range of 1–60 sec , and the default is 2 sec . the number of failures to receive the icmp echo reply from the monitored terminal after which a fault is determined can be set in the range of 1–100 , and the default is twice . monitoring with ping can be done for a maximum of 64 units . if sending a mail notification or snmp trap is enabled, they are sent in the following cases. when a terminal is detected to be down (sent every 24 hours while down) when a terminal is detected to be up (sent when monitoring is started or restored)</div><div class="display_word">3.1. Monitoring by ping (ICMP Echo request/reply) Specifications for terminal monitoring by ping are given below. The interval of ICMP Echo request transmission from the network switch is fixed at 5 sec . The ICMP Echo request that is transmitted has the following format. As the ID field of the ICMP header, the unique ID assigned to each monitored terminal is specified. As the sequence field of the ICMP header, a number that is sequentially incremented from 0 is specified. The validity of the ICMP Echo reply is checked as follows. Whether the ID field of the ICMP header contains the ID that was specified when sending the request Whether the sequence field of the ICMP header contains the sequence number that was specified when sending the request The wait time for ICMP Echo reply can be changed in the range of 1–60 sec , and the default is 2 sec . The number of failures to receive the ICMP Echo reply from the monitored terminal after which a fault is determined can be set in the range of 1–100 , and the default is twice . Monitoring with ping can be done for a maximum of 64 units . If sending a mail notification or SNMP trap is enabled, they are sent in the following cases. When a terminal is detected to be down (sent every 24 hours while down) When a terminal is detected to be up (sent when monitoring is started or restored)</div></div><div id="oam_oam_ladm"><div class="search_title" docfname="oam_oam_ladm" doctitle="Terminal" link="#フレーム受信量による監視">3.2. Monitoring according to frame reception volume</div><div class="search_word">3.2. monitoring according to frame reception volume the way in which this device monitors according to frame reception volume is described below. at one-second intervals, the number of octets received at the port is referenced, and the number of octets received during one second is calculated. all ports are the object of observation. using the number of octets received during one second and the link speed, the reception throughput (bps) and reception ratio (%) are calculated. monitoring according to frame reception volume starts when the monitoring start threshold value (bps) specified by the user is exceeded. after monitoring has started, a fault (down) is detected if the volume falls below the down detection threshold value (bps) specified by the user . if sending a mail notification or snmp trap is enabled, they are sent in the following cases. when a terminal is detected to be down when a terminal is detected to be up (sent when monitoring is started or restored)</div><div class="display_word">3.2. Monitoring according to frame reception volume The way in which this device monitors according to frame reception volume is described below. At one-second intervals, the number of octets received at the port is referenced, and the number of octets received during one second is calculated. All ports are the object of observation. Using the number of octets received during one second and the link speed, the reception throughput (bps) and reception ratio (%) are calculated. Monitoring according to frame reception volume starts when the monitoring start threshold value (bps) specified by the user is exceeded. After monitoring has started, a fault (down) is detected if the volume falls below the down detection threshold value (bps) specified by the user . If sending a mail notification or SNMP trap is enabled, they are sent in the following cases. When a terminal is detected to be down When a terminal is detected to be up (sent when monitoring is started or restored)</div></div><div id="oam_oam_ladm"><div class="search_title" docfname="oam_oam_ladm" doctitle="Terminal" link="#lldp-による監視">3.3. Monitoring with LLDP</div><div class="search_word">3.3. monitoring with lldp using the ttl which is a required item in the data portion of an lldp frame, a down condition is determined if lldp is not received within the ttl time. monitoring starts when an lldp frame is first received. this monitoring can be specified individually by port. if sending a mail notification or snmp trap is enabled, they are sent in the following cases. when a terminal is detected to be down when a terminal is detected to be up (sent when monitoring is started or restored) when a terminal stopped lldp functionality</div><div class="display_word">3.3. Monitoring with LLDP Using the TTL which is a required item in the data portion of an LLDP frame, a down condition is determined if LLDP is not received within the TTL time. Monitoring starts when an LLDP frame is first received. This monitoring can be specified individually by port. If sending a mail notification or SNMP trap is enabled, they are sent in the following cases. When a terminal is detected to be down When a terminal is detected to be up (sent when monitoring is started or restored) When a terminal stopped LLDP functionality</div></div><div id="oam_oam_ladm"><div class="search_title" docfname="oam_oam_ladm" doctitle="Terminal" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands this function does not support settings via commands.</div><div class="display_word">4. Related Commands This function does not support settings via commands.</div></div><div id="oam_oam_ladm"><div class="search_title" docfname="oam_oam_ladm" doctitle="Terminal" link="#web-gui-による設定">5. Settings via the Web GUI</div><div class="search_word">5. settings via the web gui terminal monitoring settings can be done from [advanced settings]-[terminal monitoring] of the web gui. details on the settings in each screen can be referenced via the web gui help.</div><div class="display_word">5. Settings via the Web GUI Terminal monitoring settings can be done from [Advanced settings]-[Terminal monitoring] of the Web GUI. Details on the settings in each screen can be referenced via the Web GUI help.</div></div><div id="oam_oam_ladm"><div class="search_title" docfname="oam_oam_ladm" doctitle="Terminal" link="#端末監視-トップページ">5.1. Terminal monitoring top page</div><div class="search_word">5.1. terminal monitoring top page the top page of terminal monitoring is shown below. if you want to newly add a terminal for monitoring, press the new icon. if you want to change a currently-specified monitored terminal, press the [ setting ] button in the list. if you want to delete a currently-specified monitored terminal, select the check box of that terminal, and press the [ delete ] button. if you want to ascertain the current state of the monitored terminal for which you are making settings, press the [ update ] button to acquire the latest state.</div><div class="display_word">5.1. Terminal monitoring top page The top page of terminal monitoring is shown below. If you want to newly add a terminal for monitoring, press the New icon. If you want to change a currently-specified monitored terminal, press the [ Setting ] button in the list. If you want to delete a currently-specified monitored terminal, select the check box of that terminal, and press the [ Delete ] button. If you want to ascertain the current state of the monitored terminal for which you are making settings, press the [ Update ] button to acquire the latest state.</div></div><div id="oam_oam_ladm"><div class="search_title" docfname="oam_oam_ladm" doctitle="Terminal" link="#監視端末の新規追加変更">5.2. Adding or modifying a monitored terminal</div><div class="search_word">5.2. adding or modifying a monitored terminal the method for adding a new monitored terminal, or for making changes, is shown below for each method of monitoring. monitoring by ping frame reception volume monitoring lldp reception interval monitoring restart terminal by controlling poe supply can be specified only for models that support poe supply. use the traffic observation function when deciding the monitoring start threshold value and the down detection threshold value settings for frame reception volume monitoring. if you want mail notification to be sent in the event of a fault, you must separately make mail notification settings . for details, refer to technical reference: [maintenance and operation functions] - [mail notification] and to web gui help: [management] - [mail notification] .</div><div class="display_word">5.2. Adding or modifying a monitored terminal The method for adding a new monitored terminal, or for making changes, is shown below for each method of monitoring. Monitoring by ping Frame reception volume monitoring LLDP reception interval monitoring Restart terminal by controlling PoE supply can be specified only for models that support PoE supply. Use the traffic observation function when deciding the monitoring start threshold value and the down detection threshold value settings for frame reception volume monitoring. If you want mail notification to be sent in the event of a fault, you must separately make mail notification settings . For details, refer to Technical reference: [Maintenance and operation functions] - [Mail notification] and to Web GUI help: [Management] - [Mail notification] .</div></div><div id="oam_oam_ladm"><div class="search_title" docfname="oam_oam_ladm" doctitle="Terminal" link="#監視端末の状態確認">5.3. Checking the state of a monitored terminal</div><div class="search_word">5.3. checking the state of a monitored terminal the state of a specified monitored terminal can be checked in the terminal monitoring gadget of the dashboard . for each monitored terminal, this shows the monitoring target, model name, monitoring type, and status. the following three states are shown as the state of the monitored terminal. idle : monitoring is not yet being performed: up : the monitored terminal is operating correctly: down : the monitored terminal is not operating correctly: point the mouse cursor above a status column to show the status for that monitored terminal. if you click the [ idle ] , [ up ], or [ down ] button in the upper part of the dashboard, only the monitored terminals that are in the corresponding state are shown. (the [ all ] button shows terminals of all states.) if not even one monitor terminal is registered, the display indicates “no monitored terminals are registered.”</div><div class="display_word">5.3. Checking the state of a monitored terminal The state of a specified monitored terminal can be checked in the terminal monitoring gadget of the dashboard . For each monitored terminal, this shows the monitoring target, model name, monitoring type, and status. The following three states are shown as the state of the monitored terminal. Idle : Monitoring is not yet being performed: Up : The monitored terminal is operating correctly: Down : The monitored terminal is not operating correctly: Point the mouse cursor above a status column to show the status for that monitored terminal. If you click the [ Idle ] , [ Up ], or [ Down ] button in the upper part of the dashboard, only the monitored terminals that are in the corresponding state are shown. (The [ All ] button shows terminals of all states.) If not even one monitor terminal is registered, the display indicates “No monitored terminals are registered.”</div></div><div id="oam_oam_ladm"><div class="search_title" docfname="oam_oam_ladm" doctitle="Terminal" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution none</div><div class="display_word">6. Points of Caution None</div></div><div id="oam_oam_ladm"><div class="search_title" docfname="oam_oam_ladm" doctitle="Terminal" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation performance observations</div><div class="display_word">7. Related Documentation Performance Observations</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#led制御">LED Control</div><div class="search_word">led control</div><div class="display_word">LED Control</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product includes the following leds and button on the main unit. led and button types led type description power led indicates the power supply status. microsd led indicates the microsd card connection and usage status. port led indicate the lan/sfp cable connection and usage status. mode button switches the led mode. stack id display led (7seg led) displays the stack number. only installed in the swx2310p-28gt. the layout of the leds and button is shown below.</div><div class="display_word">1. Function Overview This product includes the following LEDs and button on the main unit. LED and button types LED type Description POWER LED Indicates the power supply status. microSD LED Indicates the microSD card connection and usage status. Port LED Indicate the LAN/SFP cable connection and usage status. MODE button Switches the LED mode. Stack ID display LED (7SEG LED) Displays the stack number. Only installed in the SWX2310P-28GT. The layout of the LEDs and button is shown below.</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used legend of port led illumination port led illumination mentioned in subsequent explanations are illustrated below. legend of port led illumination</div><div class="display_word">2. Definition of Terms Used Legend of port LED illumination Port LED illumination mentioned in subsequent explanations are illustrated below. Legend of port LED illumination</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#power-led">3.1. POWER LED</div><div class="search_word">3.1. power led the power led lamp indicates the product power supply status. the power supply status indicated by each power led illumination mode is described below. power supply status indicated by each power led illumination mode power led illumination mode status unlit power is off. flashing green power is on and system is starting up. steady green power is on and system is operating normally. steady orange power is on and an error has occurred in the system. when the following errors are detected, the power indicator illuminates steady orange. check the error that was detected and take the appropriate actions. fan stopped the fan that exhausts heat generated by the product has stopped. immediately stop using the product and be sure to contact the dealer for inspection or service. temperature error inside the product the temperature inside the product is abnormal. review the ambient conditions where installed and install the product correctly so that internal temperature is appropriate. you can use the show environment command to check temperature and fan errors.</div><div class="display_word">3.1. POWER LED The POWER LED lamp indicates the product power supply status. The power supply status indicated by each POWER LED illumination mode is described below. Power supply status indicated by each POWER LED illumination mode POWER LED illumination mode Status Unlit Power is off. Flashing green Power is on and system is starting up. Steady green Power is on and system is operating normally. Steady orange Power is on and an error has occurred in the system. When the following errors are detected, the POWER indicator illuminates steady orange. Check the error that was detected and take the appropriate actions. Fan stopped The fan that exhausts heat generated by the product has stopped. Immediately stop using the product and be sure to contact the dealer for inspection or service. Temperature error inside the product The temperature inside the product is abnormal. Review the ambient conditions where installed and install the product correctly so that internal temperature is appropriate. You can use the show environment command to check temperature and fan errors.</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#sd-led">3.2. SD LED</div><div class="search_word">3.2. sd led the sd led lamp indicates the microsd card connection and usage status. the connection status indicated by each sd led illumination mode is described below. connection status indicated by each sd led illumination mode sd led illumination mode status unlit not available, because a microsd card is not inserted or unmounted. flashing green the microsd card is being accessed. steady green a microsd card is inserted and available for use. do not remove the microsd card while flashing green, because the microsd card is being accessed.</div><div class="display_word">3.2. SD LED The SD LED lamp indicates the microSD card connection and usage status. The connection status indicated by each SD LED illumination mode is described below. Connection status indicated by each SD LED illumination mode SD LED illumination mode Status Unlit Not available, because a microSD card is not inserted or unmounted. Flashing green The microSD card is being accessed. Steady green A microSD card is inserted and available for use. Do not remove the microSD card while flashing green, because the microSD card is being accessed.</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#ポートled">3.3. Port LED</div><div class="search_word">3.3. port led</div><div class="display_word">3.3. Port LED</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#表示モードと表示モードの切り替え">3.3.1. Indicator modes and switching between them</div><div class="search_word">3.3.1. indicator modes and switching between them this product offers the following five display modes. mode name mode led illumination status function overview link/act mode the left led of lan/sfp ports indicates the link status and the right led indicates the connection speed. poe mode indicates the power supply status of the poe power supply port. vlan mode indicates the vlan ids set for the lan/sfp ports. status mode displays the error status of the lan/sfp ports. off mode switches off lan/sfp port leds to minimize power consumption. the display mode can be switched using the mode button. the flowchart below shows how to switch the indicator mode. switching the indicator mode (when the default led mode is the link/act mode) the display mode after system startup and the display mode after error is resolved depend on the default led mode setting. if an error is detected by the following functions, the port leds automatically switch to the status mode. loop detection sfp optical reception level monitoring poe supply even if you press the mode button when an error is detected, the product will remain in the status mode. (no further action will be accepted until all errors have been resolved.) when you press and hold the mode button for three seconds in this status, all error conditions are reset and the leds switch to the indications according to the default led mode settings. (for details, refer to led indications in status mode .)</div><div class="display_word">3.3.1. Indicator modes and switching between them This product offers the following five display modes. Mode name MODE LED illumination status Function Overview LINK/ACT mode The left LED of LAN/SFP ports indicates the link status and the right LED indicates the connection speed. PoE mode Indicates the power supply status of the PoE power supply port. VLAN mode Indicates the VLAN IDs set for the LAN/SFP ports. STATUS mode Displays the error status of the LAN/SFP ports. OFF mode Switches off LAN/SFP port LEDs to minimize power consumption. The display mode can be switched using the MODE button. The flowchart below shows how to switch the indicator mode. Switching the indicator mode (when the default LED mode is the LINK/ACT mode) The display mode after system startup and the display mode after error is resolved depend on the default LED mode setting. If an error is detected by the following functions, the port LEDs automatically switch to the STATUS mode. Loop detection SFP optical reception level monitoring PoE supply Even if you press the MODE button when an error is detected, the product will remain in the STATUS mode. (No further action will be accepted until all errors have been resolved.) When you press and hold the MODE button for three seconds in this status, all error conditions are reset and the LEDs switch to the indications according to the default LED mode settings. (For details, refer to LED indications in STATUS mode .)</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#linkact-モード時のled表示">3.3.2. LED indications in LINK/ACT mode</div><div class="search_word">3.3.2. led indications in link/act mode in the link/act mode, port leds are illuminated as shown below. lan/sfp port link status lan/sfp port connection speed the link status led indications are shown below. lan/sfp port link status led indications while link is down while link is up while forwarding data lan port (off) (steady green) (flashing green) sfp port (off) (steady green) (flashing green) the connection speed led indications are shown below. connection speed led indications for lan/sfp ports 10m link 100m link 1000m link 10000m link lan port (off) (steady orange) (steady green) (none) sfp port (none) (none) (steady green) (steady green)</div><div class="display_word">3.3.2. LED indications in LINK/ACT mode In the LINK/ACT mode, port LEDs are illuminated as shown below. LAN/SFP port link status LAN/SFP port connection speed The link status LED indications are shown below. LAN/SFP port link status LED indications While link is down While link is up While forwarding data LAN port (Off) (Steady green) (Flashing green) SFP port (Off) (Steady green) (Flashing green) The connection speed LED indications are shown below. Connection speed LED indications for LAN/SFP ports 10M Link 100M Link 1000M Link 10000M Link LAN port (Off) (Steady orange) (Steady green) (None) SFP port (None) (None) (Steady green) (Steady green)</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#poe-モード時のled表示">3.3.3. LED indications in PoE mode</div><div class="search_word">3.3.3. led indications in poe mode in the poe mode, the power supply status is indicated on the port led of the port capable of poe supply (hereinafter referred to as poe port). in the stack configuration, the display mode cannot be changed to the poe mode. the power supply ports for each model are as follows. power supply port by model model name power supply port swx2310p-10g ports #1 to #8 swx2310p-18g ports #1 to #16 swx2310p-28gt ports #1 to #24 the led indications in the poe mode are shown below. power supply port led indications no power supply power is being supplied lan port (off) (steady green)</div><div class="display_word">3.3.3. LED indications in PoE mode In the PoE mode, the power supply status is indicated on the port LED of the port capable of PoE supply (hereinafter referred to as PoE port). In the stack configuration, the display mode cannot be changed to the PoE mode. The power supply ports for each model are as follows. Power supply port by model Model name Power supply port SWX2310P-10G Ports #1 to #8 SWX2310P-18G Ports #1 to #16 SWX2310P-28GT Ports #1 to #24 The LED indications in the PoE mode are shown below. Power supply port LED indications No power supply Power is being supplied LAN port (Off) (Steady green)</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#vlan-モード時のled表示">3.3.4. LED indications in VLAN mode</div><div class="search_word">3.3.4. led indications in vlan mode in the vlan mode, the port leds indicate the vlan association status. in the stack configuration, the display mode cannot be changed to the vlan mode. the port led illumination statuses are shown below. port led illumination statuses in vlan mode lan/sfp port vlan association status port led illumination status the port is not associated with any vlan (off) the port is associated with one vlan the six lowest vlan ids are indicated in specific illumination patterns. all vlan ids from the 7th lowest one are indicated in an identical illumination pattern. the port is associated with multiple vlans (the port leds on the left and right are lit in steady orange) the default vlan (vlan #1) is excluded from the subject of indication. it is not counted as an associated vlan. the vlan association status does not depend on the link status of each lan/sfp port. ports in the link-down status are also included in the subject of indication. vlan ids in the subject of indication are only those with associated lan/sfp ports. those for which only the vlan ids are defined (without associated lan/sfp ports) are excluded from the subject of indication.</div><div class="display_word">3.3.4. LED indications in VLAN mode In the VLAN mode, the port LEDs indicate the VLAN association status. In the stack configuration, the display mode cannot be changed to the VLAN mode. The port LED illumination statuses are shown below. Port LED illumination statuses in VLAN mode LAN/SFP port VLAN association status Port LED illumination status The port is not associated with any VLAN (Off) The port is associated with one VLAN The six lowest VLAN IDs are indicated in specific illumination patterns. All VLAN IDs from the 7th lowest one are indicated in an identical illumination pattern. The port is associated with multiple VLANs (The port LEDs on the left and right are lit in steady orange) The default VLAN (VLAN #1) is excluded from the subject of indication. It is not counted as an associated VLAN. The VLAN association status does not depend on the link status of each LAN/SFP port. Ports in the link-down status are also included in the subject of indication. VLAN IDs in the subject of indication are only those with associated LAN/SFP ports. Those for which only the VLAN IDs are defined (without associated LAN/SFP ports) are excluded from the subject of indication.</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#status-モード時のled表示">3.3.5. LED indications in STATUS mode</div><div class="search_word">3.3.5. led indications in status mode in status mode, the port leds indicate the status of errors generated by the following product functions. loop detection sfp optical reception level monitoring poe supply port led indications in error status normal state loop detection or sfp optical rx level abnormality pd error poe system limit poe port limit lan port (off) (left led flashing orange) (left led steady orange) (right led flashing orange) (right led steady orange) sfp port (off) (left led flashing orange) (none) (none) (none) when the product detects an error, it overrides the current mode and switches to status mode. the following conditions trigger an error in respective functions. loop detection loop was detected, so port was blocked loop was detected, so port was shut down sfp optical reception level monitoring sfp optical reception level fell below the normal range sfp optical reception level exceeded the normal range poe supply power supply stopped because the port limit (maximum power supply per port) exceeded power supply to low priority ports stopped because the system limit (maximum power supply of the entire system) exceeded a pd error was detected the cause of the error can be checked using the show error port-led command. during active errors in the status mode, leds will automatically switch to the default led mode in the following states. all of the following errors were resolved. blocked status due to loop detection is resolved. shutdown status due to loop detection is resolved. the monitoring time elapsed after the shutdown due to loop detection. the unit linked up after the no shutdown command was executed during shutdown due to loop detection. sfp optical reception level recovered. the poe port error was resolved. press and hold the mode button (for three seconds) to forcibly reset (clear) the error status.</div><div class="display_word">3.3.5. LED indications in STATUS mode In STATUS mode, the port LEDs indicate the status of errors generated by the following product functions. Loop detection SFP optical reception level monitoring PoE supply Port LED indications in error status Normal state Loop detection or SFP optical Rx level abnormality PD error PoE system limit PoE port limit LAN port (Off) (Left LED flashing orange) (Left LED steady orange) (Right LED flashing orange) (Right LED steady orange) SFP port (Off) (Left LED flashing orange) (None) (None) (None) When the product detects an error, it overrides the current mode and switches to STATUS mode. The following conditions trigger an error in respective functions. Loop detection Loop was detected, so port was blocked Loop was detected, so port was shut down SFP optical reception level monitoring SFP optical reception level fell below the normal range SFP optical reception level exceeded the normal range PoE supply Power supply stopped because the port limit (maximum power supply per port) exceeded Power supply to low priority ports stopped because the system limit (maximum power supply of the entire system) exceeded A PD error was detected The cause of the error can be checked using the show error port-led command. During active errors in the STATUS mode, LEDs will automatically switch to the default LED mode in the following states. All of the following errors were resolved. Blocked status due to loop detection is resolved. Shutdown status due to loop detection is resolved. The monitoring time elapsed after the shutdown due to loop detection. The unit linked up after the no shutdown command was executed during shutdown due to loop detection. SFP optical reception level recovered. The PoE port error was resolved. Press and hold the MODE button (for three seconds) to forcibly reset (clear) the error status.</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#offモードのled表示">3.3.6. LED indication for OFF mode</div><div class="search_word">3.3.6. led indication for off mode if the default led mode is the off mode, the port leds remain off regardless of the link status. even if the default led mode is off, if an error occurs then the mode automatically switches to the status mode and displays the error status.</div><div class="display_word">3.3.6. LED indication for OFF mode If the default LED mode is the OFF mode, the port LEDs remain off regardless of the link status. Even if the default LED mode is OFF, if an error occurs then the mode automatically switches to the STATUS mode and displays the error status.</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#システム起動後のledモードの変更">3.3.7. Changing the LED mode after system startup</div><div class="search_word">3.3.7. changing the led mode after system startup this product enables the led mode after system startup (the default led mode) to be changed. the initial default led mode is set to link/act mode, but it can be changed using the led-mode default command. however, the led mode cannot be changed in the stack configuration. you can check the default led mode and the currently displayed led mode using the show led-mode command. if an active error is resolved in the status mode, the mode is switched back to the default led mode.</div><div class="display_word">3.3.7. Changing the LED mode after system startup This product enables the LED mode after system startup (the default LED mode) to be changed. The initial default LED mode is set to LINK/ACT mode, but it can be changed using the led-mode default command. However, the LED mode cannot be changed in the stack configuration. You can check the default LED mode and the currently displayed LED mode using the show led-mode command. If an active error is resolved in the STATUS mode, the mode is switched back to the default LED mode.</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#その他のポートled表示">3.3.8. Other port LED indications</div><div class="search_word">3.3.8. other port led indications regardless of the led mode status, all port leds will illuminate as indicated below during startup initialization and firmware updates. other port led indications updating firmware initializing lan port (flashing green) (off) sfp port (flashing green) (steady orange)</div><div class="display_word">3.3.8. Other port LED indications Regardless of the LED mode status, all port LEDs will illuminate as indicated below during startup initialization and firmware updates. Other port LED indications Updating firmware Initializing LAN port (Flashing green) (Off) SFP port (Flashing green) (Steady orange)</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#スタックid表示-led">3.4. Stack ID display LED</div><div class="search_word">3.4. stack id display led the stack id display led (7seg led) installed on the swx2310p-28gt displays the stack id in the stack configuration after the startup countdown is displayed. if a stack is not configured, the number ‘1’ is displayed. if an error occurs while a stack is configured, the letter ’e’ is displayed to indicate the error. if the default led mode is the off mode, the stack id display led is also switched off.</div><div class="display_word">3.4. Stack ID display LED The stack ID display LED (7SEG LED) installed on the SWX2310P-28GT displays the stack ID in the stack configuration after the startup countdown is displayed. If a stack is not configured, the number ‘1’ is displayed. If an error occurs while a stack is configured, the letter ’E’ is displayed to indicate the error. If the default LED mode is the OFF mode, the stack ID display LED is also switched off.</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands show lan/sfp port status show interface show loop detection setting status show loop-detect show vlan information show vlan brief set default led mode led-mode default show led mode show led-mode show port error status show error port-led</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Show LAN/SFP port status show interface Show loop detection setting status show loop-detect Show VLAN information show vlan brief Set default LED mode led-mode default Show LED mode show led-mode Show port error status show error port-led</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#lansfp-ポートの状態確認">5.1. Checking LAN/SFP port status</div><div class="search_word">5.1. checking lan/sfp port status use the show interface command to check the lan/sfp port status. yamaha#show interfaceshow interfaceinterface port1.1  link is up  hardware is ethernet  hw addr: ac44.f23d.0b2c  ifindex 5001, mru 1522  speed-duplex: auto(configured), 1000-full(current)  auto mdi/mdix: on  vlan info :    switchport mode        : access    ingress filter         : enable    acceptable frame types : all    default vlan           :    1    configured vlans       :    1  interface counter:    input  packets          : 317111           bytes            : 31387581           multicast packets: 317074    output packets          : 162694           bytes            : 220469213           multicast packets: 162310           broadcast packets: 149           drop packets     : 0  ：(shows information for all lan ports)</div><div class="display_word">5.1. Checking LAN/SFP port status Use the show interface command to check the LAN/SFP port status. Yamaha#show interfaceshow interfaceInterface port1.1  Link is UP  Hardware is Ethernet  HW addr: ac44.f23d.0b2c  ifIndex 5001, MRU 1522  Speed-Duplex: auto(configured), 1000-full(current)  Auto MDI/MDIX: on  Vlan info :    Switchport mode        : access    Ingress filter         : enable    Acceptable frame types : all    Default Vlan           :    1    Configured Vlans       :    1  Interface counter:    input  packets          : 317111           bytes            : 31387581           multicast packets: 317074    output packets          : 162694           bytes            : 220469213           multicast packets: 162310           broadcast packets: 149           drop packets     : 0  ：(Shows information for all LAN ports)</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#lansfp-ポート-ループ検出状態の確認">5.2. Checking LAN/SFP port loop detection status</div><div class="search_word">5.2. checking lan/sfp port loop detection status check the lan/sfp port loop detection status. yamaha#show loop-detectloop-detect: enableloop-detect: enableport      loop-detect    port-blocking           status-------------------------------------------------------port1.1        enable           enable           normalport1.2        enable           enable           normalport1.3        enable           enable           normalport1.4        enable           enable           normalport1.5        enable           enable           normalport1.6        enable           enable           normalport1.7        enable           enable           normalport1.8        enable           enable           normalport1.9        enable           enable           normalport1.10       enable           enable           normal-------------------------------------------------------(*): indicates that the feature is enabled.</div><div class="display_word">5.2. Checking LAN/SFP port loop detection status Check the LAN/SFP port loop detection status. Yamaha#show loop-detectloop-detect: Enableloop-detect: Enableport      loop-detect    port-blocking           status-------------------------------------------------------port1.1        enable           enable           Normalport1.2        enable           enable           Normalport1.3        enable           enable           Normalport1.4        enable           enable           Normalport1.5        enable           enable           Normalport1.6        enable           enable           Normalport1.7        enable           enable           Normalport1.8        enable           enable           Normalport1.9        enable           enable           Normalport1.10       enable           enable           Normal-------------------------------------------------------(*): Indicates that the feature is enabled.</div></div><div id="oam_oam_led"><div class="search_title" docfname="oam_oam_led" doctitle="LED" link="#初期ledモードの設定">5.3. Set default LED mode</div><div class="search_word">5.3. set default led mode set the default led mode to the off mode. yamaha#configure terminalyamaha(config)#led-mode default off (1) yamaha(config)#exityamaha#show led-mode (2) default mode : offcurrent mode : off 1 set default led mode 2 show led mode</div><div class="display_word">5.3. Set default LED mode Set the default LED mode to the OFF mode. Yamaha#configure terminalYamaha(config)#led-mode default off (1) Yamaha(config)#exitYamaha#show led-mode (2) default mode : offcurrent mode : off 1 Set default LED mode 2 Show LED mode</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#lldp">LLDP</div><div class="search_word">lldp</div><div class="display_word">LLDP</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview lldp is a protocol for passing device management information between a device and its neighboring devices. this is a simple protocol in which a device unidirectionally advertises its own information and neighbor devices receive this information. however, since lldp-compliant devices maintain the information received from neighbor devices as mib objects, the user can access this information via snmp and ascertain what type of devices are connected to which interfaces are. this protocol is also used for negotiation between devices that support poe (power over ethernet).</div><div class="display_word">1. Function Overview LLDP is a protocol for passing device management information between a device and its neighboring devices. This is a simple protocol in which a device unidirectionally advertises its own information and neighbor devices receive this information. However, since LLDP-compliant devices maintain the information received from neighbor devices as MIB objects, the user can access this information via SNMP and ascertain what type of devices are connected to which interfaces are. This protocol is also used for negotiation between devices that support PoE (Power Over Ethernet).</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used lldp link layer discovery protocol. this is defined in ieee 802.1ab. lldp-med lldp for media endpont devices. this is defined in ansi/tia-1057.</div><div class="display_word">2. Definition of Terms Used LLDP Link Layer Discovery Protocol. This is defined in IEEE 802.1AB. LLDP-MED LLDP for Media Endpont Devices. This is defined in ANSI/TIA-1057.</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#動作仕様">3.1. Operating specifications</div><div class="search_word">3.1. operating specifications</div><div class="display_word">3.1. Operating specifications</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#基本仕様">3.1.1. Basic specifications</div><div class="search_word">3.1.1. basic specifications this product supports the following operations. lldp frames are transmitted from any lan/sfp port to convey information about the device itself. lldp frames are received at any lan/sfp port to obtain information about neighboring devices. information transmitted via lldp about the device itself, and information obtained via lldp about neighbor devices, etc., can be referenced via snmp. lldp sends and receives information using type, length, and value (tlv) attributes. for details on the tlv information sent by this product, refer to tlv list . this product’s lldp supports the following mibs of snmp. for details, refer to 3.3 supported mibs . lldp-mib lldp-ext-dot3-mib lldp-v2-mib lldp-ext-dot3-v2-mib lldp-ext-med-mib the following settings are required in order to use the lldp function. enable lldp functionality for the overall system using the lldp run command. create lldp agents at applicable interfaces using the lldp-agent command. specify the lldp frame transmit/receive mode using the set lldp command. the lldp function is enabled in default settings for this product. lldp frames are always transmitted without tags, regardless of the vlan settings of the transmitting switch port. they are also transmitted without tags from a trunk port without a native vlan. when lldp is used for poe negotiation, it is necessary to configure the port to which the poe powered device is connected so that lldp can be transmitted and received.</div><div class="display_word">3.1.1. Basic specifications This product supports the following operations. LLDP frames are transmitted from any LAN/SFP port to convey information about the device itself. LLDP frames are received at any LAN/SFP port to obtain information about neighboring devices. Information transmitted via LLDP about the device itself, and information obtained via LLDP about neighbor devices, etc., can be referenced via SNMP. LLDP sends and receives information using Type, Length, and Value (TLV) attributes. For details on the TLV information sent by this product, refer to TLV list . This product’s LLDP supports the following MIBs of SNMP. For details, refer to 3.3 Supported MIBs . LLDP-MIB LLDP-EXT-DOT3-MIB LLDP-V2-MIB LLDP-EXT-DOT3-V2-MIB LLDP-EXT-MED-MIB The following settings are required in order to use the LLDP function. Enable LLDP functionality for the overall system using the lldp run command. Create LLDP agents at applicable interfaces using the lldp-agent command. Specify the LLDP frame transmit/receive mode using the set lldp command. The LLDP function is enabled in default settings for this product. LLDP frames are always transmitted without tags, regardless of the VLAN settings of the transmitting switch port. They are also transmitted without tags from a trunk port without a native VLAN. When LLDP is used for PoE negotiation, it is necessary to configure the port to which the PoE powered device is connected so that LLDP can be transmitted and received.</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#送信情報の設定">3.1.2. Transmitted information settings</div><div class="search_word">3.1.2. transmitted information settings use the following commands to specify the lldp frames that are transmitted from the device itself. there are also some tlvs (required tlvs) that are transmitted regardless of the settings of the following commands. tlv-select basic-mgmt command (basic management tlv) tlv-select ieee-8021-org-specific command (ieee 802.1 tlv) tlv-select ieee-8023-org-specific command (ieee 802.3 tlv) tlv-select med command (lldp-med tlv) the system name and description that are transmitted in the basic management tlvs are specified by the lldp system-name command and the lldp system-description command. the type of management address is set management-address-tlv command.</div><div class="display_word">3.1.2. Transmitted information settings Use the following commands to specify the LLDP frames that are transmitted from the device itself. There are also some TLVs (required TLVs) that are transmitted regardless of the settings of the following commands. tlv-select basic-mgmt command (basic management TLV) tlv-select ieee-8021-org-specific command (IEEE 802.1 TLV) tlv-select ieee-8023-org-specific command (IEEE 802.3 TLV) tlv-select med command (LLDP-MED TLV) The system name and description that are transmitted in the basic management TLVs are specified by the lldp system-name command and the lldp system-description command. The type of management address is set management-address-tlv command.</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#送信タイマーの設定">3.1.3. Transmission timer setting</div><div class="search_word">3.1.3. transmission timer setting lldp frame transmission interval is specified by the set timer msg-tx-interval command. the multiplier for calculating the hold time (ttl) for device information is set by the set msg-tx-hold command. the ttl for lldp transmission is the result of the following calculation. the default is 121 seconds. ttl = ( value set by the “set timer msg-tx-interval” command ) × ( value set by the “set msg-tx-hold” command ) + 1 (second) when a neighbor device is connected to a lan/sfp port for which lldp frame transmission is enabled, lldp frames are transmitted rapidly at a fixed interval according to the high-speed transmission interval setting. the transmission interval and the number of transmissions for high speed transmission are set by the set timer msg-fast-tx command and the set tx-fast-init . if the set lldp command is used to change the setting from a state in which lldp frame transmission is enabled to a state in which the frame transmission is disabled, this product transmits a shut-down frame, notifying the neighbor device that lldp frame transmission has stopped. subsequently, even if lldp frame transmission is once again enabled, lldp frame transmission to the neighbor device is stopped for a time. the stopped duration until the next transmission occurs after transmitting the shutdown frame is set by the set timer reinit-delay command.</div><div class="display_word">3.1.3. Transmission timer setting LLDP frame transmission interval is specified by the set timer msg-tx-interval command. The multiplier for calculating the hold time (TTL) for device information is set by the set msg-tx-hold command. The TTL for LLDP transmission is the result of the following calculation. The default is 121 seconds. TTL = ( value set by the “set timer msg-tx-interval” command ) × ( value set by the “set msg-tx-hold” command ) + 1 (second) When a neighbor device is connected to a LAN/SFP port for which LLDP frame transmission is enabled, LLDP frames are transmitted rapidly at a fixed interval according to the high-speed transmission interval setting. The transmission interval and the number of transmissions for high speed transmission are set by the set timer msg-fast-tx command and the set tx-fast-init . If the set lldp command is used to change the setting from a state in which LLDP frame transmission is enabled to a state in which the frame transmission is disabled, this product transmits a shut-down frame, notifying the neighbor device that LLDP frame transmission has stopped. Subsequently, even if LLDP frame transmission is once again enabled, LLDP frame transmission to the neighbor device is stopped for a time. The stopped duration until the next transmission occurs after transmitting the shutdown frame is set by the set timer reinit-delay command.</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#最大接続台数の設定">3.1.4. Maximum connected devices setting</div><div class="search_word">3.1.4. maximum connected devices setting the maximum number of connected devices that can be managed by the corresponding port is set by the set too-many-neighbors limit command. the default value for the maximum number of connected devices is 5 devices .</div><div class="display_word">3.1.4. Maximum connected devices setting The maximum number of connected devices that can be managed by the corresponding port is set by the set too-many-neighbors limit command. The default value for the maximum number of connected devices is 5 devices .</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#lldp情報の確認">3.1.5. Checking LLDP information</div><div class="search_word">3.1.5. checking lldp information lldp interface settings and received information about neighbor devices can be checked by using the show lldp interface command or the show lldp neighbors command. to clear the lldp frame counter, use the clear lldp counters command.</div><div class="display_word">3.1.5. Checking LLDP information LLDP interface settings and received information about neighbor devices can be checked by using the show lldp interface command or the show lldp neighbors command. To clear the LLDP frame counter, use the clear lldp counters command.</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#lldpを利用したその他の機能">3.1.6. Other functions using LLDP</div><div class="search_word">3.1.6. other functions using lldp access point link this function sends and receives proprietary lldp frames between yamaha network switches and yamaha wireless access points to automatically perform specific processes, such as specifying settings based on information in the lldp notifications or saving log data. ap link function setting is specified using the lldp auto-setting command. for details, refer to lldp automatic setting (access point link) . dante optimization setting this function automatically specifies settings optimized for the dante digital audio network. the dante optimization settings function is set using the lldp auto-setting command. for more information, refer to dante optimization settings function . lldp reception interval monitoring this function monitors whether specific connected terminals are live or dead. for details, refer to terminal monitoring . voice vlan with the voice vlan function, lldp-med can be used to specify voice traffic settings for ip telephony. for details, refer to vlan .</div><div class="display_word">3.1.6. Other functions using LLDP Access point link This function sends and receives proprietary LLDP frames between Yamaha network switches and Yamaha wireless access points to automatically perform specific processes, such as specifying settings based on information in the LLDP notifications or saving log data. AP link function setting is specified using the lldp auto-setting command. For details, refer to LLDP Automatic Setting (Access Point Link) . Dante optimization setting This function automatically specifies settings optimized for the Dante digital audio network. The Dante optimization settings function is set using the lldp auto-setting command. For more information, refer to Dante Optimization Settings Function . LLDP reception interval monitoring This function monitors whether specific connected terminals are live or dead. For details, refer to Terminal Monitoring . Voice VLAN With the voice VLAN function, LLDP-MED can be used to specify voice traffic settings for IP telephony. For details, refer to VLAN .</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#tlv一覧">3.2. TLV list</div><div class="search_word">3.2. tlv list the tlvs supported by this product are listed below. required tlvs basic management tlvs ieee 802.1 tlv ieee 802.3 tlv lldp-med tlv for detailed specifications of each tlv, refer to ieee 802.1ab (lldp) and ansi/tia-1057 (lldp-med). the tlvs that are transmitted by this product are explained below.</div><div class="display_word">3.2. TLV list The TLVs supported by this product are listed below. Required TLVs Basic management TLVs IEEE 802.1 TLV IEEE 802.3 TLV LLDP-MED TLV For detailed specifications of each TLV, refer to IEEE 802.1AB (LLDP) and ANSI/TIA-1057 (LLDP-MED). The TLVs that are transmitted by this product are explained below.</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#必須tlv">3.2.1. Required TLVs</div><div class="search_word">3.2.1. required tlvs if lldp frame transmission is enabled, these tlvs are always transmitted. three tlvs are transmitted: chassis id, port id, and ttl. the required tlvs are listed below. type description length value (only fixed values are listed) chassis id chassis id 6 bytes mac address of the device port id port id 7 to 8 bytes port name (portx.x) time to live (ttl) hold time of device information (sec) 2 bytes</div><div class="display_word">3.2.1. Required TLVs If LLDP frame transmission is enabled, these TLVs are always transmitted. Three TLVs are transmitted: chassis ID, port ID, and TTL. The required TLVs are listed below. Type Description Length Value (only fixed values are listed) Chassis ID Chassis ID 6 bytes MAC address of the device Port ID Port ID 7 to 8 bytes Port name (portX.X) Time To Live (TTL) Hold time of device information (sec) 2 bytes</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#基本管理tlv">3.2.2. Basic management TLVs</div><div class="search_word">3.2.2. basic management tlvs these tlvs are transmitted if lldp frame transmission is enabled and the tlv-select basic-mgmt command is specified. system-related management information is transmitted, such as name, system capabilities, and address. the basic management tlvs are listed below. type description length value (only fixed values are listed) port description port description string 0 to 255 bytes system name system name string default: hostname 0 to 255 bytes system description system description string default: model name + firmware revision 0 to 255 bytes system capabilities capabilities supported by the system 2 bytes 0x0004（bridge） enabled system capabilities 2 bytes 0x0004（bridge） management address management address ip address (4 bytes) or mac address (6 bytes) 4 or 6 bytes interface sub-type 1 byte 0x02 (ifindex) interface number 4 byte ifindex value</div><div class="display_word">3.2.2. Basic management TLVs These TLVs are transmitted if LLDP frame transmission is enabled and the tlv-select basic-mgmt command is specified. System-related management information is transmitted, such as name, system capabilities, and address. The basic management TLVs are listed below. Type Description Length Value (only fixed values are listed) Port Description Port description string 0 to 255 bytes System Name System name string Default: Hostname 0 to 255 bytes System Description System description string Default: Model name + Firmware revision 0 to 255 bytes System Capabilities Capabilities supported by the system 2 bytes 0x0004（bridge） Enabled system capabilities 2 bytes 0x0004（bridge） Management Address Management address IP address (4 bytes) or MAC address (6 bytes) 4 or 6 bytes Interface sub-type 1 byte 0x02 (ifIndex) Interface number 4 Byte ifIndex value</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#ieee-8021-tlv">3.2.3. IEEE 802.1 TLV</div><div class="search_word">3.2.3. ieee 802.1 tlv these tlvs are transmitted if lldp frame transmission is enabled and the tlv-select ieee-8021-org-specific command is specified. these transmit information such as vlan and link aggregation for the corresponding port. the ieee 802.1 tlvs are listed below. type description length value (only fixed values are listed) port vlan id port vlan number 2 bytes port and protocol vlan id protocol vlan support and enable/disable 1 byte 0x00 (no support) protocol vlan number 2 bytes 0x0000 protocol identity byte string that identifies the protocol 0 to 255 bytes link aggregation aggregation capability and status 1 byte ifindex number of aggregation logical interface 4 byte vlan name name of the vlan to which the port belongs 0 to 32 bytes</div><div class="display_word">3.2.3. IEEE 802.1 TLV These TLVs are transmitted if LLDP frame transmission is enabled and the tlv-select ieee-8021-org-specific command is specified. These transmit information such as VLAN and link aggregation for the corresponding port. The IEEE 802.1 TLVs are listed below. Type Description Length Value (only fixed values are listed) Port VLAN ID Port VLAN number 2 bytes Port and Protocol VLAN ID Protocol VLAN support and enable/disable 1 byte 0x00 (no support) Protocol VLAN number 2 bytes 0x0000 Protocol Identity Byte string that identifies the protocol 0 to 255 bytes Link Aggregation Aggregation capability and status 1 byte ifIndex number of aggregation logical interface 4 Byte VLAN Name Name of the VLAN to which the port belongs 0 to 32 bytes</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#ieee-8023-tlv">3.2.4. IEEE 802.3 TLV</div><div class="search_word">3.2.4. ieee 802.3 tlv these tlvs are transmitted if lldp frame transmission is enabled and the tlv-select ieee-8023-org-specific command is specified. auto negotiation support information, poe information, etc. for the corresponding port are transmitted. the ieee 802.3 tlvs are listed below. type description length value (only fixed values are listed) mac/phy configuration/status auto negotiation support, and whether enabled or disabled 1 byte supported communication method for auto negotiation 2 bytes operational mau type data signaling rate and duplex mode (ietf rfc 4836) 2 bytes power via mdi mdi power support status 1 byte pse power pair selection of wiring to be used for power supply 1 byte 0x01 (signal line) power class class0 to class4 1 byte power type pse device/pd device 2 bit 0b00 (pse device) power source primary/secondary 2 bit 0b01 (primary) priority 2 bit power required from pd device (in units of 0.1 watts) 2 bytes power supply of pse device (in units of 0.1 watts) 2 bytes link aggregation aggregation capability and status 1 byte ifindex number of aggregation logical interface 4 byte maximum frame size maximum frame size 2 bytes</div><div class="display_word">3.2.4. IEEE 802.3 TLV These TLVs are transmitted if LLDP frame transmission is enabled and the tlv-select ieee-8023-org-specific command is specified. Auto negotiation support information, PoE information, etc. for the corresponding port are transmitted. The IEEE 802.3 TLVs are listed below. Type Description Length Value (only fixed values are listed) MAC/PHY Configuration/Status Auto negotiation support, and whether enabled or disabled 1 byte Supported communication method for auto negotiation 2 bytes Operational MAU Type Data signaling rate and duplex mode (IETF RFC 4836) 2 bytes Power Via MDI MDI power support status 1 byte PSE power pair Selection of wiring to be used for power supply 1 byte 0x01 (signal line) Power class Class0 to Class4 1 byte Power type PSE Device/PD Device 2 bit 0b00 (PSE Device) Power source Primary/Secondary 2 bit 0b01 (Primary) Priority 2 bit Power required from PD device (in units of 0.1 watts) 2 bytes Power supply of PSE device (in units of 0.1 watts) 2 bytes Link Aggregation Aggregation capability and status 1 byte ifIndex number of aggregation logical interface 4 Byte Maximum Frame Size Maximum frame size 2 bytes</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#lldp-med-tlv">3.2.5. LLDP-MED TLV</div><div class="search_word">3.2.5. lldp-med tlv these tlvs are transmitted if lldp frame transmission is enabled and the tlv-select med command is specified. these are used to transmit information about network policy and extended poe of the port. the lldp-med tlvs are listed below. type description length value (only fixed values are listed) lldp-med capabilities transmittable lldp-med tlvs 2 bytes 0x000b (lldp-med capabilities, network policy, extended power-via-mdi tlv ) device type 1 byte 0x04 (network connectivity) network policy application type 1 byte 0x01 (voice) voice vlan information 3 byte extended power-via-mdi power type pse device/pd device 2 bit 0b00 (pse device) power source primary/secondary 2 bit 0b01 (primary) power priority 4 bit power required from pd (in units of 0.1 watts) 2 bytes network policy is only transmitted via the port specified by voice vlan.</div><div class="display_word">3.2.5. LLDP-MED TLV These TLVs are transmitted if LLDP frame transmission is enabled and the tlv-select med command is specified. These are used to transmit information about network policy and extended PoE of the port. The LLDP-MED TLVs are listed below. Type Description Length Value (only fixed values are listed) LLDP-MED Capabilities Transmittable LLDP-MED TLVs 2 bytes 0x000B (LLDP-MED Capabilities, Network Policy, Extended Power-via-MDI TLV ) Device type 1 byte 0x04 (Network Connectivity) Network Policy Application type 1 byte 0x01 (Voice) Voice VLAN information 3 Byte Extended Power-via-MDI Power type PSE Device/PD Device 2 bit 0b00 (PSE Device) Power source Primary/Secondary 2 bit 0b01 (Primary) Power priority 4 bit Power required from PD (in units of 0.1 watts) 2 bytes Network policy is only transmitted via the port specified by Voice VLAN.</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#サポートmib">3.3. Supported MIBs</div><div class="search_word">3.3. supported mibs refer to the following snmp mib reference for information on the mibs that are supported. snmp mib reference</div><div class="display_word">3.3. Supported MIBs Refer to the following SNMP MIB Reference for information on the MIBs that are supported. SNMP MIB Reference</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands enable lldp function lldp run set system description text string lldp system-description set system name lldp system-name create lldp agent lldp-agent set lldp transmission/reception mode set lldp set the type of management address set management-address-tlv set basic management tlv tlv-select basic-mgmt set ieee-802.1 tlv tlv-select ieee-8021-org-specific set ieee-802.3 tlv tlv-select ieee-8023-org-specific set lldp-med tlv tlv-select med set the lldp frame transmission interval set timer msg-tx-interval set duration to stop transmission following lldp transmission stop until transmission is once again possible set timer reinit-delay set the multiplier for calculating the hold time (ttl) for device information set msg-tx-hold set lldp frame transmission interval for high-speed transmission term set timer msg-fast-tx set number of lldp frames transmitted for high-speed transmission term set tx-fast-init set the maximum number of connected devices that can be managed by each port set too-many-neighbors limit show interface status show lldp interface show connected device information for all interfaces show lldp neighbors clear lldp frame counters clear lldp counters set dante optimization setting function and ap link function using lldp lldp auto-setting</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Enable LLDP function lldp run Set system description text string lldp system-description Set system name lldp system-name Create LLDP agent lldp-agent Set LLDP transmission/reception mode set lldp Set the type of management address set management-address-tlv Set basic management TLV tlv-select basic-mgmt Set IEEE-802.1 TLV tlv-select ieee-8021-org-specific Set IEEE-802.3 TLV tlv-select ieee-8023-org-specific Set LLDP-MED TLV tlv-select med Set the LLDP frame transmission interval set timer msg-tx-interval Set duration to stop transmission following LLDP transmission stop until transmission is once again possible set timer reinit-delay Set the multiplier for calculating the hold time (TTL) for device information set msg-tx-hold Set LLDP frame transmission interval for high-speed transmission term set timer msg-fast-tx Set number of LLDP frames transmitted for high-speed transmission term set tx-fast-init Set the maximum number of connected devices that can be managed by each port set too-many-neighbors limit Show interface status show lldp interface Show connected device information for all interfaces show lldp neighbors Clear LLDP frame counters clear lldp counters Set Dante optimization setting function and AP link function using LLDP lldp auto-setting</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#lldpフレームの送受信の設定">5.1. Set LLDP frame transmission/reception</div><div class="search_word">5.1. set lldp frame transmission/reception for port1.1, enable lldp frame transmission/reception. basic management tlvs, ieee 802.1 tlvs, ieee 802.3 tlvs, and lldp-med tlvs are transmitted. set the lldp frame transmission interval to 60 seconds. set the lldp frame ttl to 181 seconds. set “switch1” as the name of the transmitting system. specify 10 as the maximum number of connected devices managed by the port. yamaha#configure terminalyamaha(confif)#lldp system-name switch1 (1) yamaha(config)#interface port1.1yamaha(config-if)#lldp-agent (2) yamaha(lldp-agent)#tlv-select basic-mgmt (3) yamaha(lldp-agent)#tlv-select ieee-8021-org-specific (4) yamaha(lldp-agent)#tlv-select ieee-8023-org-specific (5) yamaha(lldp-agent)#tlv-select med (6) yamaha(lldp-agent)#set timer msg-tx-interval 60 (7) yamaha(lldp-agent)#set msg-tx-hold 3 (8) yamaha(lldp-agent)#set too-many-neighbors limit 10 (9) yamaha(lldp-agent)#set lldp enable txrx (10) yamaha(lldp-agent)#exityamaha(config-if)#exityamaha(config)#lldp run (11) yamaha(config)#exit 1 set system name 2 create lldp agent, mode transition 3 set basic management tlv 4 set ieee 802.1 tlv 5 set ieee 802.3 tlv 6 set lldp-med tlv 7 set transmission interval 8 set multiplier for ttl calculation: ttl = 60 x 3 + 1 = 181 seconds 9 maximum connected devices setting 10 set lldp transmission/reception mode 11 enable lldp function</div><div class="display_word">5.1. Set LLDP frame transmission/reception For port1.1, enable LLDP frame transmission/reception. Basic management TLVs, IEEE 802.1 TLVs, IEEE 802.3 TLVs, and LLDP-MED TLVs are transmitted. Set the LLDP frame transmission interval to 60 seconds. Set the LLDP frame TTL to 181 seconds. Set “SWITCH1” as the name of the transmitting system. Specify 10 as the maximum number of connected devices managed by the port. Yamaha#configure terminalYamaha(confif)#lldp system-name SWITCH1 (1) Yamaha(config)#interface port1.1Yamaha(config-if)#lldp-agent (2) Yamaha(lldp-agent)#tlv-select basic-mgmt (3) Yamaha(lldp-agent)#tlv-select ieee-8021-org-specific (4) Yamaha(lldp-agent)#tlv-select ieee-8023-org-specific (5) Yamaha(lldp-agent)#tlv-select med (6) Yamaha(lldp-agent)#set timer msg-tx-interval 60 (7) Yamaha(lldp-agent)#set msg-tx-hold 3 (8) Yamaha(lldp-agent)#set too-many-neighbors limit 10 (9) Yamaha(lldp-agent)#set lldp enable txrx (10) Yamaha(lldp-agent)#exitYamaha(config-if)#exitYamaha(config)#lldp run (11) Yamaha(config)#exit 1 Set system name 2 Create LLDP agent, mode transition 3 Set basic management TLV 4 Set IEEE 802.1 TLV 5 Set IEEE 802.3 TLV 6 Set LLDP-MED TLV 7 Set transmission interval 8 Set multiplier for TTL calculation: TTL = 60 x 3 + 1 = 181 seconds 9 Maximum connected devices setting 10 Set LLDP transmission/reception mode 11 Enable LLDP function</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#lldp-インターフェース状態の表示">5.2. Show LLDP interface status</div><div class="search_word">5.2. show lldp interface status show the port1.1 lldp interface information. yamaha#show lldp interface port1.1 (1) agent mode                    : nearest bridgeenable (tx/rx)                : y/ymessage fast transmit time    : 1message transmission interval : 30reinitialization delay        : 2med enabled                   : ydevice type                   : network_connectivitylldp agent traffic statistics  total frames transmitted       : 0 1 show interface information</div><div class="display_word">5.2. Show LLDP interface status Show the port1.1 LLDP interface information. Yamaha#show lldp interface port1.1 (1) Agent Mode                    : Nearest bridgeEnable (tx/rx)                : Y/YMessage fast transmit time    : 1Message transmission interval : 30Reinitialization delay        : 2MED Enabled                   : YDevice Type                   : NETWORK_CONNECTIVITYLLDP Agent traffic statistics  Total frames transmitted       : 0 1 Show interface information</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#lldp-接続機器の情報の表示">5.3. Show LLDP connected device information</div><div class="search_word">5.3. show lldp connected device information show lldp connected device information. yamaha#show lldp neighbors (1) interface name           : port1.1system name              : swx3100-10gsystem description       : swx3100 rev.4.01.02 (mon dec  4 12:33:18 2017)port description         : port1.3system capabilities      : l2 switchinginterface numbering      : 2interface number         : 5003oid number               :management mac address   : ac44.f230.0000mandatory tlvs  chassis id type    ip address           : 0.0.0.0  port id type    interface name       : port1.3  ttl (time to live)     : 418021 origin specific tlvs  port vlan id                : 1  pp vlan id                  : 0  remote vlans configured    vlan id                   : 1    vlan name                 : default  remote protocols advertised :    multiple spanning tree protocol  remote vid usage digestt    : 0  remote management vlan      : 0  link aggregation status     :  link aggregation port id    :8023 origin specific tlvs  autonego support            : supported enabled  autonego capability         : 27649  operational mau type        : 30  power via mdi capability (raw data)    mdi power support         : 0x0    pse power pair            : 0x0    power class               : 0x0    type/source/priority      : 0x0    pd requested power value  : 0x0    pse allocated power value : 0x0  link aggregation status     :  link aggregation port id    :  max frame size              : 1522lldp-med tlvs  med capabilities            :    capabilities    network policy  med capabilities dev type   : end point class-3  med application type        : reserved  med vlan id                 : 0  med tag/untag               : untagged  med l2 priority             : 0  med dscp val                : 0  med location data format    : ecs elin    latitude res      : 0    latitude          : 0    longitude res     : 0    longitude         : 0    at                : 0    altitude res      : 0    altitude          : 0    datum             : 0    lci length        : 0    what              : 0    country code      : 0    ca type           : 0  med inventory 1 show connected device information</div><div class="display_word">5.3. Show LLDP connected device information Show LLDP connected device information. Yamaha#show lldp neighbors (1) Interface Name           : port1.1System Name              : SWX3100-10GSystem Description       : SWX3100 Rev.4.01.02 (Mon Dec  4 12:33:18 2017)Port Description         : port1.3System Capabilities      : L2 SwitchingInterface Numbering      : 2Interface Number         : 5003OID Number               :Management MAC Address   : ac44.f230.0000Mandatory TLVs  CHASSIS ID TYPE    IP ADDRESS           : 0.0.0.0  PORT ID TYPE    INTERFACE NAME       : port1.3  TTL (Time To Live)     : 418021 ORIGIN SPECIFIC TLVs  Port Vlan id                : 1  PP Vlan id                  : 0  Remote VLANs Configured    VLAN ID                   : 1    VLAN Name                 : default  Remote Protocols Advertised :    Multiple Spanning Tree Protocol  Remote VID Usage Digestt    : 0  Remote Management Vlan      : 0  Link Aggregation Status     :  Link Aggregation Port ID    :8023 ORIGIN SPECIFIC TLVs  AutoNego Support            : Supported Enabled  AutoNego Capability         : 27649  Operational MAU Type        : 30  Power via MDI Capability (raw data)    MDI power support         : 0x0    PSE power pair            : 0x0    Power class               : 0x0    Type/source/priority      : 0x0    PD requested power value  : 0x0    PSE allocated power value : 0x0  Link Aggregation Status     :  Link Aggregation Port ID    :  Max Frame Size              : 1522LLDP-MED TLVs  MED Capabilities            :    Capabilities    Network Policy  MED Capabilities Dev Type   : End Point Class-3  MED Application Type        : Reserved  MED Vlan id                 : 0  MED Tag/Untag               : Untagged  MED L2 Priority             : 0  MED DSCP Val                : 0  MED Location Data Format    : ECS ELIN    Latitude Res      : 0    Latitude          : 0    Longitude Res     : 0    Longitude         : 0    AT                : 0    Altitude Res      : 0    Altitude          : 0    Datum             : 0    LCI length        : 0    What              : 0    Country Code      : 0    CA type           : 0  MED Inventory 1 Show connected device information</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution none</div><div class="display_word">6. Points of Caution None</div></div><div id="oam_oam_lldp"><div class="search_title" docfname="oam_oam_lldp" doctitle="LLDP" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation snmp terminal monitoring dante optimization settings poe control vlan lldp automatic setting (access point link)</div><div class="display_word">7. Related Documentation SNMP Terminal Monitoring Dante Optimization Settings PoE Control VLAN LLDP Automatic Setting (Access Point Link)</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#lldp自動設定ap連携">LLDP Automatic Setting (Access Point Link)</div><div class="search_word">lldp automatic setting (access point link)</div><div class="display_word">LLDP Automatic Setting (Access Point Link)</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview the lldp automatic setting specifies sending/receiving proprietary lldp frames between yamaha network switches and yamaha wireless access points to automatically perform specific processes, such as specifying settings based on information in lldp notifications or saving log data. the following functionality can be achieved by lldp automatic settings. radius server automatic settings this automatically specifies information about radius servers currently operating at the yamaha wireless access point in the yamaha network switch. that makes it easy to configure an authentication function in yamaha wireless access points as a radius server or in yamaha network switches as a radius client. yamaha wireless access point dead/alive monitoring this uses lldp to automatically monitor whether yamaha wireless access points connected to the product are dead or alive. log saving before yamaha wireless access points stop it can be used to save log data up to immediately prior to shutting off power to yamaha wireless access points by sending a notification before shutting off poe power supply from a yamaha network switch to a yamaha wireless access point. to determine yamaha network switch and wireless access point models that support lldp automatic setting function, refer to the following. technical reference: lldp automatic setting examples</div><div class="display_word">1. Function Overview The LLDP automatic setting specifies sending/receiving proprietary LLDP frames between Yamaha network switches and Yamaha wireless access points to automatically perform specific processes, such as specifying settings based on information in LLDP notifications or saving log data. The following functionality can be achieved by LLDP automatic settings. RADIUS server automatic settings This automatically specifies information about RADIUS servers currently operating at the Yamaha wireless access point in the Yamaha network switch. That makes it easy to configure an authentication function in Yamaha wireless access points as a RADIUS server or in Yamaha network switches as a RADIUS client. Yamaha wireless access point dead/alive monitoring This uses LLDP to automatically monitor whether Yamaha wireless access points connected to the product are dead or alive. Log saving before Yamaha wireless access points stop It can be used to save log data up to immediately prior to shutting off power to Yamaha wireless access points by sending a notification before shutting off PoE power supply from a Yamaha network switch to a Yamaha wireless access point. To determine Yamaha network switch and wireless access point models that support LLDP automatic setting function, refer to the following. Technical reference: LLDP automatic setting examples</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used</div><div class="display_word">2. Definition of Terms Used</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#lldp">2.1. LLDP</div><div class="search_word">2.1. lldp link layer discovery protocol. this is defined in ieee 802.1ab.</div><div class="display_word">2.1. LLDP Link Layer Discovery Protocol. This is defined in IEEE 802.1AB.</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#基本仕様">3.1. Basic specifications</div><div class="search_word">3.1. basic specifications if lldp automatic setting function is enabled, proprietary lldp frames will be sent and received between yamaha network switches and yamaha wireless access points. lldp automatic settings are specified using the lldp auto-setting command. lldp automatic setting function is enabled in default settings. in order to use this function, reception of lldp frames must be enabled. for this reason, check in advance that the following settings have been made. enable lldp functionality for the overall system using the lldp run command. create lldp agents at applicable interfaces using the lldp-agent command. specify the lldp frame transmit/receive mode using the set lldp command. lldp frame transmission and reception are enabled in product default settings.</div><div class="display_word">3.1. Basic specifications If LLDP automatic setting function is enabled, proprietary LLDP frames will be sent and received between Yamaha network switches and Yamaha wireless access points. LLDP automatic settings are specified using the lldp auto-setting command. LLDP automatic setting function is enabled in default settings. In order to use this function, reception of LLDP frames must be enabled. For this reason, check in advance that the following settings have been made. Enable LLDP functionality for the overall system using the lldp run command. Create LLDP agents at applicable interfaces using the lldp-agent command. Specify the LLDP frame transmit/receive mode using the set lldp command. LLDP frame transmission and reception are enabled in product default settings.</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#radiusサーバーの自動設定">3.2. RADIUS server automatic settings</div><div class="search_word">3.2. radius server automatic settings this function automatically specifies information in the product about radius servers currently operating at yamaha wireless access points (clusters). that makes it easy to configure an authentication function in yamaha wireless access points as a radius server or in yamaha network switches as a radius client. authentication settings for each port on the product must be set manually by the user based on the given environment. for details about the settings, refer to port authentication function in the technical reference.</div><div class="display_word">3.2. RADIUS server automatic settings This function automatically specifies information in the product about RADIUS servers currently operating at Yamaha wireless access points (clusters). That makes it easy to configure an authentication function in Yamaha wireless access points as a RADIUS server or in Yamaha network switches as a RADIUS client. Authentication settings for each port on the product must be set manually by the user based on the given environment. For details about the settings, refer to Port authentication function in the technical reference.</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#ヤマハ無線apが送信するradiusサーバー情報">3.2.1. RADIUS server information sent by Yamaha wireless access points</div><div class="search_word">3.2.1. radius server information sent by yamaha wireless access points yamaha wireless access points send radius server information based on the following criteria. lldp and lldp automatic settings are enabled cluster functionality is enabled cluster leader aps are functioning as a radius server cluster follower aps are functioning as radius client that connects to a leader ap radius server. for details about yamaha wireless access point settings, refer to the yamaha wireless access point technical reference . if the criteria for sending information are satisfied, yamaha wireless access points send notifications with the following radius server information at lldp regular intervals. ip address of the radius server udp port number for radius server authentication shared password for communicating with radius server</div><div class="display_word">3.2.1. RADIUS server information sent by Yamaha wireless access points Yamaha wireless access points send RADIUS server information based on the following criteria. LLDP and LLDP automatic settings are enabled Cluster functionality is enabled Cluster leader APs are functioning as a RADIUS server Cluster follower APs are functioning as RADIUS client that connects to a leader AP RADIUS server. For details about Yamaha wireless access point settings, refer to the Yamaha wireless access point technical reference . If the criteria for sending information are satisfied, Yamaha wireless access points send notifications with the following RADIUS server information at LLDP regular intervals. IP address of the RADIUS server UDP port number for RADIUS server authentication Shared password for communicating with RADIUS server</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#radiusサーバーエントリー管理">3.2.2. RADIUS server entry control</div><div class="search_word">3.2.2. radius server entry control if the product lldp automatic setting function is enabled and radius server information is received from a yamaha wireless access point, then a radius-server host command with an optional dynamic string added to the end is automatically specified in the running-config. in the remaining explanation below, the radius-server host command appended by an optional dynamic string is referred to as a “dynamic entry”, whereas the manually specified radius-server host command is referred to as a “static entry”. dynamic entries appended with the optional dynamic string are not saved in the startup-config file, even if the write command is executed. after dynamic entry is set by automatic settings, static entry can be set by manually deleting the dynamic option. however, static entry cannot be changed to dynamic entry by manually adding the dynamic option. example of dynamic entry of radius-server host command radius-server host 192.168.100.241 auth-port 1234 key example dynamic dynamic entries specified by lldp automatic settings are appended with lldp reception port number and term of validity information. if identical radius server information is received from multiple ports, the radius server information received from the port with the smallest port number is retained. the ttl (time to live) value included in the received lldp frame is specified as the term of validity. the default ttl value for lldp frames sent from yamaha wireless access points is 120 seconds. if new radius server information is received within ttl seconds, then the term of validity is updated, whereas if new radius server information is not received within ttl seconds, then the dynamic entry is deleted. however, if an lldp shutdown frame with ttl = 0 is received, then the dynamic entry is immediately deleted. you can check the radius server information with the show radius-server command. an asterisk (*) will be added to the automatically specified radius server host, and the lldp reception port number (lldp received port) and term of validity (expires) information will be displayed. example of using the show radius-server command to show dynamic entry information swx#show radius-serverserver host : 192.168.100.241* lldp received port : port1.2 expires : 00:00:33 authentication port : 1234 secret key : example timeout : 10 sec retransmit count : 5 deadtime : 0 min* - assigned by lldp. a total of up to 8 radius server information entries, including dynamic and static entries, can be specified for the product. using static entries is prioritized over using dynamic entries. therefore, even if the maximum number of radius server information entries are already specified, new static entries can be specified if there are any dynamic entries among existing entries. in that case, the dynamic entry with the highest lldp reception port number is deleted.</div><div class="display_word">3.2.2. RADIUS server entry control If the product LLDP automatic setting function is enabled and RADIUS server information is received from a Yamaha wireless access point, then a radius-server host command with an optional dynamic string added to the end is automatically specified in the running-config. In the remaining explanation below, the radius-server host command appended by an optional dynamic string is referred to as a “dynamic entry”, whereas the manually specified radius-server host command is referred to as a “static entry”. Dynamic entries appended with the optional dynamic string are not saved in the startup-config file, even if the write command is executed. After dynamic entry is set by automatic settings, static entry can be set by manually deleting the dynamic option. However, static entry cannot be changed to dynamic entry by manually adding the dynamic option. Example of Dynamic Entry of radius-server host Command radius-server host 192.168.100.241 auth-port 1234 key EXAMPLE dynamic Dynamic entries specified by LLDP automatic settings are appended with LLDP reception port number and term of validity information. If identical RADIUS server information is received from multiple ports, the RADIUS server information received from the port with the smallest port number is retained. The TTL (Time to Live) value included in the received LLDP frame is specified as the term of validity. The default TTL value for LLDP frames sent from Yamaha wireless access points is 120 seconds. If new RADIUS server information is received within TTL seconds, then the term of validity is updated, whereas if new RADIUS server information is not received within TTL seconds, then the dynamic entry is deleted. However, if an LLDP shutdown frame with TTL = 0 is received, then the dynamic entry is immediately deleted. You can check the RADIUS server information with the show radius-server command. An asterisk (*) will be added to the automatically specified RADIUS server host, and the LLDP reception port number (LLDP Received port) and term of validity (Expires) information will be displayed. Example of using the show radius-server command to show dynamic entry information SWX#show radius-serverServer Host : 192.168.100.241* LLDP Received port : port1.2 Expires : 00:00:33 Authentication Port : 1234 Secret Key : EXAMPLE Timeout : 10 sec Retransmit Count : 5 Deadtime : 0 min* - Assigned by LLDP. A total of up to 8 RADIUS server information entries, including dynamic and static entries, can be specified for the product. Using static entries is prioritized over using dynamic entries. Therefore, even if the maximum number of RADIUS server information entries are already specified, new static entries can be specified if there are any dynamic entries among existing entries. In that case, the dynamic entry with the highest LLDP reception port number is deleted.</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#注意事項">3.2.3. Points of Caution</div><div class="search_word">3.2.3. points of caution if the above functionality is used, note the following precautions. connection to yamaha wireless access point unit to enable automatic setting of radius server information, yamaha network switches must be connected directly to a yamaha wireless access point that support lldp automatic setting functionality. for yamaha network switches not directly connected to a yamaha wireless access point, specify radius server settings manually. command input mode restrictions when the stack function is enabled if the stack function is enabled, users permitted to transition to the global configuration mode are restricted. for details, refer to stack function . because settings automatically transition to the global configuration mode if radius server settings are received by lldp from a yamaha wireless access point and applied, users that are already in the global configuration mode via the console or who are in an individual configuration mode are forced to transition to the privileged exec mode. characters permitted in shared passwords for communicating with radius servers question mark and space characters cannot be used. do not use those characters when setting shared passwords (radius server, client, or secret) for yamaha wireless access point units. set response wait time for the entire radius server if multiple radius servers are configured, set the auth timeout server-timeout command setting value, which sets the total wait time for all radius servers, to a value equal to or larger than the product of the radius-server timeout command setting value times the radius-server retransmit command setting value plus one times the number of radius servers. for command details, refer to the command reference.</div><div class="display_word">3.2.3. Points of Caution If the above functionality is used, note the following precautions. Connection to Yamaha wireless access point unit To enable automatic setting of RADIUS server information, Yamaha network switches must be connected directly to a Yamaha wireless access point that support LLDP automatic setting functionality. For Yamaha network switches not directly connected to a Yamaha wireless access point, specify RADIUS server settings manually. Command input mode restrictions when the stack function is enabled If the stack function is enabled, users permitted to transition to the global configuration mode are restricted. For details, refer to Stack Function . Because settings automatically transition to the global configuration mode if RADIUS server settings are received by LLDP from a Yamaha wireless access point and applied, users that are already in the global configuration mode via the console or who are in an individual configuration mode are forced to transition to the privileged EXEC mode. Characters permitted in shared passwords for communicating with RADIUS servers Question mark and space characters cannot be used. Do not use those characters when setting shared passwords (RADIUS server, client, or secret) for Yamaha wireless access point units. Set response wait time for the entire RADIUS server If multiple RADIUS servers are configured, set the auth timeout server-timeout command setting value, which sets the total wait time for all RADIUS servers, to a value equal to or larger than the product of the radius-server timeout command setting value times the radius-server retransmit command setting value plus one times the number of RADIUS servers. For command details, refer to the command reference.</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#ヤマハ無線apの死活監視">3.3. Yamaha wireless access point dead/alive monitoring</div><div class="search_word">3.3. yamaha wireless access point dead/alive monitoring when a yamaha network switch receives a request from a yamaha wireless access point to start dead/alive monitoring, it automatically starts monitoring by lldp whether the yamaha wireless access point is dead or alive. yamaha wireless access points send dead/alive monitoring requests based on the following criteria. lldp and lldp automatic settings are enabled if the dead/alive monitoring request is received with the lldp automatic setting function enabled in the yamaha network switch, then an lldp reception interval monitoring setting is registered for the lldp reception port. at ports where the setting is registered, the alive/dead status is monitored by lldp. if no lldp signals are received/sent for a certain period, the poe power supply is temporarily (5 seconds) switched off to try and restore the yamaha wireless access point. also, a notification will be issued when a communication interruption is detected in snmp traps and l2ms traps. for details, refer to the technical reference for terminal monitoring .</div><div class="display_word">3.3. Yamaha wireless access point dead/alive monitoring When a Yamaha network switch receives a request from a Yamaha wireless access point to start dead/alive monitoring, it automatically starts monitoring by LLDP whether the Yamaha wireless access point is dead or alive. Yamaha wireless access points send dead/alive monitoring requests based on the following criteria. LLDP and LLDP automatic settings are enabled If the dead/alive monitoring request is received with the LLDP automatic setting function enabled in the Yamaha network switch, then an LLDP reception interval monitoring setting is registered for the LLDP reception port. At ports where the setting is registered, the alive/dead status is monitored by LLDP. If no LLDP signals are received/sent for a certain period, the PoE power supply is temporarily (5 seconds) switched off to try and restore the Yamaha wireless access point. Also, a notification will be issued when a communication interruption is detected in SNMP traps and L2MS traps. For details, refer to the technical reference for terminal monitoring .</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#注意事項">3.3.1. Points of Caution</div><div class="search_word">3.3.1. points of caution if the above functionality is used, note the following precautions. if dead/alive monitoring is no longer necessary, such as after the yamaha wireless access point connection port was changed, manually delete the settings that became unnecessary after the yamaha wireless access point connection port was changed.</div><div class="display_word">3.3.1. Points of Caution If the above functionality is used, note the following precautions. If dead/alive monitoring is no longer necessary, such as after the Yamaha wireless access point connection port was changed, manually delete the settings that became unnecessary after the Yamaha wireless access point connection port was changed.</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#ヤマハ無線ap停止前のログ保存">3.4. Log saving before Yamaha wireless access points stop</div><div class="search_word">3.4. log saving before yamaha wireless access points stop the scheduling function can be used to operate the product so that poe power to a wireless access point is shut off only during a specified period. because that suddenly shuts off power to the wireless access point, unsaved log data is normally lost, but this model is able to save that yamaha wireless access point log data by using lldp to notify the device about the poe power shutoff timing. power supply shutoff timing notices are sent if the power-inline disable delay command was used at a given lan port to specify a poe power shutoff delay time (delay option). if the web gui is used to select the “stop power supply after notifying the yamaha wireless ap” setting for the easy schedule template settings function, the setting for shutting off the power 10 minutes after executing the schedule ( power-inline disable delay 600 command) is registered. if the following criteria are satisfied at a port with power shutoff being delayed, the lldp transmission interval is overridden and changed to 30 seconds. the lldp transmission interval setting must be greater than 30 seconds. lldp and lldp automatic settings are enabled however, if the power supply is already shut off or the power-inline enable command was used to cancel the power supply shutoff delay, then the lldp transmission interval will revert to the original setting value. if the lldp transmission interval is overridden and changed to 30 seconds by this function, then an asterisk is appended to the lldp transmission interval value shown by the show lldp interface command. example of lldp transmission interval shown by the show lldp interface command swx#show lldp interface port1.2agent mode                    : nearest bridgeenable (tx/rx)                : y/ymessage fast transmit time    : 1message transmission interval : 30*reinitialization delay        : 2med enabled                   : ydevice type                   : network_connectivitylldp agent traffic statistics  total frames transmitted       : 0  total entries aged             : 0  total frames received          : 0  total frames received in error : 0  total frames discarded         : 0  total discarded tlvs           : 0  total unrecognised tlvs        : 0* - assigned by lldp.</div><div class="display_word">3.4. Log saving before Yamaha wireless access points stop The scheduling function can be used to operate the product so that PoE power to a wireless access point is shut off only during a specified period. Because that suddenly shuts off power to the wireless access point, unsaved log data is normally lost, but this model is able to save that Yamaha wireless access point log data by using LLDP to notify the device about the PoE power shutoff timing. Power supply shutoff timing notices are sent if the power-inline disable delay command was used at a given LAN port to specify a PoE power shutoff delay time (delay option). If the Web GUI is used to select the “Stop power supply after notifying the Yamaha wireless AP” setting for the easy schedule template settings function, the setting for shutting off the power 10 minutes after executing the schedule ( power-inline disable delay 600 command) is registered. If the following criteria are satisfied at a port with power shutoff being delayed, the LLDP transmission interval is overridden and changed to 30 seconds. The LLDP transmission interval setting must be greater than 30 seconds. LLDP and LLDP automatic settings are enabled However, if the power supply is already shut off or the power-inline enable command was used to cancel the power supply shutoff delay, then the LLDP transmission interval will revert to the original setting value. If the LLDP transmission interval is overridden and changed to 30 seconds by this function, then an asterisk is appended to the LLDP transmission interval value shown by the show lldp interface command. Example of LLDP transmission interval shown by the show lldp interface command SWX#show lldp interface port1.2Agent Mode                    : Nearest bridgeEnable (tx/rx)                : Y/YMessage fast transmit time    : 1Message transmission interval : 30*Reinitialization delay        : 2MED Enabled                   : YDevice Type                   : NETWORK_CONNECTIVITYLLDP Agent traffic statistics  Total frames transmitted       : 0  Total entries aged             : 0  Total frames received          : 0  Total frames received in error : 0  Total frames discarded         : 0  Total discarded TLVs           : 0  Total unrecognised TLVs        : 0* - Assigned by LLDP.</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details, refer to the command reference. operations operating commands enable lldp automatic settings lldp auto-setting enable lldp function lldp run create lldp agent lldp-agent set lldp transmission/reception mode set lldp set lldp frame transmission interval set timer msg-tx-interval set radius server host radius-server host set response wait time for a single radius server radius-server timeout set number of times to resend requests to radius server radius-server retransmit show radius server setting status show radius-server set response wait time for the entire radius server auth timeout server-timeout set the poe power supply function (interface) power-inline show interface status show lldp interface</div><div class="display_word">4. Related Commands Related commands are indicated below. For details, refer to the Command Reference. Operations Operating commands Enable LLDP automatic settings lldp auto-setting Enable LLDP function lldp run Create LLDP agent lldp-agent Set LLDP transmission/reception mode set lldp Set LLDP frame transmission interval set timer msg-tx-interval Set RADIUS server host radius-server host Set response wait time for a single RADIUS server radius-server timeout Set number of times to resend requests to RADIUS server radius-server retransmit Show RADIUS server setting status show radius-server Set response wait time for the entire RADIUS server auth timeout server-timeout Set the PoE power supply function (interface) power-inline Show interface status show lldp interface</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#設定例">5. Setting Examples</div><div class="search_word">5. setting examples for instructions on how to configure respective yamaha network switch and wireless access point settings, refer to the following. technical reference: lldp automatic setting examples</div><div class="display_word">5. Setting Examples For instructions on how to configure respective Yamaha network switch and wireless access point settings, refer to the following. Technical reference: LLDP automatic setting examples</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution see the precautions indicated for each function.</div><div class="display_word">6. Points of Caution See the precautions indicated for each function.</div></div><div id="oam_oam_lldp_auto_setting"><div class="search_title" docfname="oam_oam_lldp_auto_setting" doctitle="LLDP" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation lldp radius server port authentication function terminal monitoring poe control schedule function stack function technical reference: lldp automatic setting examples</div><div class="display_word">7. Related Documentation LLDP RADIUS server Port Authentication Function Terminal Monitoring PoE Control Schedule Function Stack Function Technical reference: LLDP automatic setting examples</div></div><div id="oam_oam_mail"><div class="search_title" docfname="oam_oam_mail" doctitle="Mail" link="#メール通知">Mail Notification</div><div class="search_word">mail notification</div><div class="display_word">Mail Notification</div></div><div id="oam_oam_mail"><div class="search_title" docfname="oam_oam_mail" doctitle="Mail" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview the mail notification function sends mail notifications of information detected by the l2ms function or terminal monitoring function. by specifying the following settings, mail notifications can be sent with information detected by various functions. specify settings for the mail server used to send mails. specify the mail template.</div><div class="display_word">1. Function Overview The mail notification function sends mail notifications of information detected by the L2MS function or terminal monitoring function. By specifying the following settings, mail notifications can be sent with information detected by various functions. Specify settings for the mail server used to send mails. Specify the mail template.</div></div><div id="oam_oam_mail"><div class="search_title" docfname="oam_oam_mail" doctitle="Mail" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used mail template the mail template defines the collection of information needed for sending mail. mail server to use sender mail address recipient mail address subject of mail notification content transmission wait time</div><div class="display_word">2. Definition of Terms Used Mail Template The mail template defines the collection of information needed for sending mail. Mail server to use Sender mail address Recipient mail address Subject of mail Notification content Transmission wait time</div></div><div id="oam_oam_mail"><div class="search_title" docfname="oam_oam_mail" doctitle="Mail" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_mail"><div class="search_title" docfname="oam_oam_mail" doctitle="Mail" link="#動作">3.1. Action</div><div class="search_word">3.1. action after mail server settings and mail template settings have been configured correctly, the mail notification function will enter the send-standby state whenever a notification event occurs for a function that supports mail notification. when the mail notification function is in the send-standby state, the function will wait until the specified mail transmission wait time specified in each mail template elapses. when the mail transmission wait time has elapsed, the mail notification function combines the information for notification events that occurred during the wait time into a single mail and sends it to the recipient.</div><div class="display_word">3.1. Action After mail server settings and mail template settings have been configured correctly, the mail notification function will enter the send-standby state whenever a notification event occurs for a function that supports mail notification. When the mail notification function is in the send-standby state, the function will wait until the specified mail transmission wait time specified in each mail template elapses. When the mail transmission wait time has elapsed, the mail notification function combines the information for notification events that occurred during the wait time into a single mail and sends it to the recipient.</div></div><div id="oam_oam_mail"><div class="search_title" docfname="oam_oam_mail" doctitle="Mail" link="#メールサーバーの設定">3.2. Mail server settings</div><div class="search_word">3.2. mail server settings settings can be specified in the list of registered mail servers displayed by clicking [detailed settings] - [mail notification] in the web gui. to display the mail server settings , click the new button or the setting button for existing settings. in mail server settings , make the following settings. account identification name name for uniquely identifying the mail server settings. this setting may be omitted. smtp server address smtp server port number encrypting smtp selects either “smtp over ssl” or “starttls” as the encryption method. smtp authentication to use smtp authentication, enter the username and password.</div><div class="display_word">3.2. Mail server settings Settings can be specified in the List of Registered Mail Servers displayed by clicking [Detailed settings] - [mail notification] in the web GUI. To display the Mail server settings , click the New button or the Setting button for existing settings. In Mail server settings , make the following settings. Account identification name Name for uniquely identifying the mail server settings. This setting may be omitted. SMTP server address SMTP server port number Encrypting SMTP Selects either “SMTP over SSL” or “STARTTLS” as the encryption method. SMTP authentication To use SMTP authentication, enter the username and password.</div></div><div id="oam_oam_mail"><div class="search_title" docfname="oam_oam_mail" doctitle="Mail" link="#メールテンプレートの設定">3.3. Specify the mail template</div><div class="search_word">3.3. specify the mail template mail template settings can be specified by clicking [detailed settings] - [mail notification] in the web gui to display the list of mail notification settings . press the new button or the setting button for an existing setting to display mail notification settings . in mail notification settings , specify the following settings. source (from) destination (to) subject if the use default subject box is checked, then the mail subject will always be in the form notification from (device name) . notification content error types can be specified in detail for lan map error detection , so that only the specified type of notifications are output. mail transmission wait time</div><div class="display_word">3.3. Specify the mail template Mail template settings can be specified by clicking [Detailed settings] - [mail notification] in the web GUI to display the List of mail notification settings . Press the New button or the Setting button for an existing setting to display mail notification settings . In mail notification settings , specify the following settings. Source (From) Destination (To) Subject If the Use default subject box is checked, then the mail subject will always be in the form Notification from (device name) . Notification content Error types can be specified in detail for LAN map error detection , so that only the specified type of notifications are output. Mail transmission wait time</div></div><div id="oam_oam_mail"><div class="search_title" docfname="oam_oam_mail" doctitle="Mail" link="#メール通知に対応している機能">3.4. Functions that support mail notification</div><div class="search_word">3.4. functions that support mail notification the following functions support mail notification. lan map the following notification events can be included in mail notifications. category type event description device abnormality fan error fan lock fan stopped fan speed fan rotation speed increased fan stop a specific fan stopped power supply abnormality power voltage power supply voltage exceeded the upper threshold value power supply overcurrent occurred in power supply temperature anomaly cpu temperature cpu temperature error phy temperature phy temperature error sfp temperature sfp module temperature error unit temperature unit temperature error pse temperature pse temperature error mac temperature mac temperature error yamaha network switch temperature (cpu, phy, sfp module, main unit, pse, or mac temperature) exceeded the upper threshold value the yamaha network switch temperature returned to normal thermal sensor invalid a yamaha network switch temperature sensor error occurred loop detection loop was detected loop detect loop was detected at a port the loop detected at the port was resolved sfp optical rx level abnormality sfp optical input level error sfp rx power sfp optical input level exceeded the threshold value sfp optical input level returned to the normal range transmission queue monitoring sending queue usage ratio error queue usage rate sending queue usage ratio increased sending queue usage ratio reached upper limit sending queue usage ratio returned to normal value poe supply temperature anomaly over temperature power supply stopped due to a temperature anomaly maximum power supply capacity was exceeded over supply the power supply exceeded the maximum supply capacity power supply abnormality power failure the power supply source malfunctioned power supply stopped due to a power supply class error class failure power supply was stopped because a class greater than the power supply class setting was detected at the power supply port power supply stopped due to a class4 power supply forced terminate power supply to a port that was being supplied class3 (15.4 w) power was stopped due to a class4 (30 w) power supply at the port power supply stopped due to overcurrent over current power supply stopped because an excessive current was supplied to a port power supply stopped because power supply capacity was exceeded poe state error(over-supply) the power supply exceeded the maximum supply capacity maximum power supply capacity exceeded has been resolved power supply stopped due to temperature error poe state error(over-temperature) power supply stopped due to a temperature anomaly power supply stop due to temperature error was resolved power supply stopped due to stoppage of fan poe state error(fanlock) power supply stopped because the fan stopped power supply stop due to stopped fan was resolved power supply stopped due to power supply abnormality poe state error(power-failure) power supply stopped due to a poe power supply abnormality snapshot invalid device connected illegal equipment(snapshot) device not registered in snapshot was detected invalid device connection was resolved connection port mismatch port mismatch(snapshot) device with a connection port that differs from snapshot was detected connection port mismatch was resolved device lost disappearance equipment(snapshot) a device registered in the snapshot is not connected device loss was resolved l2ms manager duplication l2ms manager duplication l2ms manager duplication a duplicate l2ms manager was detected terminal monitoring function the following notification events can be included in mail notifications. category type description ping monitoring up detection terminal up was detected down detection terminal down was detected frame reception volume monitoring up detection terminal up was detected down detection terminal down was detected lldp monitoring up detection terminal up was detected down detection terminal down was detected stack function the following notification events can be included in mail notifications. type description stack port link down the stack port connected to the member switch went link-down heartbeat error detection a member switch heartbeat error was detected member switch was upgraded a member switch was upgraded to a main switch</div><div class="display_word">3.4. Functions that support mail notification The following functions support mail notification. LAN MAP The following notification events can be included in mail notifications. Category Type Event Description Device abnormality Fan error Fan Lock Fan stopped Fan speed Fan rotation speed increased Fan stop A specific fan stopped Power supply abnormality Power voltage Power supply voltage exceeded the upper threshold value Power supply Overcurrent occurred in power supply Temperature anomaly CPU temperature CPU temperature error PHY temperature PHY temperature error SFP temperature SFP module temperature error Unit temperature Unit temperature error PSE temperature PSE temperature error MAC temperature MAC temperature error Yamaha network switch temperature (CPU, PHY, SFP module, main unit, PSE, or MAC temperature) exceeded the upper threshold value The Yamaha network switch temperature returned to normal Thermal Sensor invalid A Yamaha network switch temperature sensor error occurred Loop Detection Loop was detected Loop Detect Loop was detected at a port The loop detected at the port was resolved SFP optical Rx level abnormality SFP optical input level error SFP RX Power SFP optical input level exceeded the threshold value SFP optical input level returned to the normal range Transmission Queue Monitoring Sending queue usage ratio error Queue Usage Rate Sending queue usage ratio increased Sending queue usage ratio reached upper limit Sending queue usage ratio returned to normal value PoE supply Temperature anomaly Over Temperature Power supply stopped due to a temperature anomaly Maximum power supply capacity was exceeded Over Supply The power supply exceeded the maximum supply capacity Power supply abnormality Power Failure The power supply source malfunctioned Power supply stopped due to a power supply class error Class Failure Power supply was stopped because a class greater than the power supply class setting was detected at the power supply port Power supply stopped due to a class4 power supply Forced Terminate Power supply to a port that was being supplied class3 (15.4 W) power was stopped due to a class4 (30 W) power supply at the port Power supply stopped due to overcurrent Over Current Power supply stopped because an excessive current was supplied to a port Power supply stopped because power supply capacity was exceeded PoE state error(over-supply) The power supply exceeded the maximum supply capacity Maximum power supply capacity exceeded has been resolved Power supply stopped due to temperature error PoE state error(over-temperature) Power supply stopped due to a temperature anomaly Power supply stop due to temperature error was resolved Power supply stopped due to stoppage of fan PoE state error(fanlock) Power supply stopped because the fan stopped Power supply stop due to stopped fan was resolved Power supply stopped due to power supply abnormality PoE state error(power-failure) Power supply stopped due to a PoE power supply abnormality Snapshot Invalid device connected Illegal Equipment(SnapShot) Device not registered in snapshot was detected Invalid device connection was resolved Connection port mismatch Port Mismatch(SnapShot) Device with a connection port that differs from snapshot was detected Connection port mismatch was resolved Device lost Disappearance Equipment(SnapShot) A device registered in the snapshot is not connected Device loss was resolved L2MS Manager Duplication L2MS Manager Duplication L2MS manager duplication A duplicate L2MS manager was detected Terminal monitoring function The following notification events can be included in mail notifications. Category Type Description Ping monitoring Up detection Terminal up was detected Down detection Terminal down was detected Frame reception volume monitoring Up detection Terminal up was detected Down detection Terminal down was detected LLDP monitoring Up detection Terminal up was detected Down detection Terminal down was detected Stack function The following notification events can be included in mail notifications. Type Description Stack port link down The stack port connected to the member switch went link-down Heartbeat error detection A member switch heartbeat error was detected Member switch was upgraded A member switch was upgraded to a main switch</div></div><div id="oam_oam_mail"><div class="search_title" docfname="oam_oam_mail" doctitle="Mail" link="#メール本文の例">3.5. Mail body example</div><div class="search_word">3.5. mail body example the body of a notification mail includes content such as the following. for details, refer to the technical reference for each function. up to 100 items can be included in one notification mail. model: swx2310p-28gt                 * model namerevision: rev.2.02.02                * firmware versionname: swx2310p-28gt_xxxxxxxx         * host nametime: 2017/06/13 11:42:56            * mail transmission timetemplate id: 1                       * mail template id<<<<<<<<<<<<<<<<<<<<<<<<    lan map information    >>>>>>>>>>>>>>>>>>>>>>>>>[sfp rx power]  type                                device_name  mac_address                         err_port  route  state============================================================================(detected: 2017/06/13 10:09:40  recovered: 2017/06/13 10:10:10)  swx2310p-10g                        swx2310p-10g_s4k000398  00a0.deae.b89c                      1.9  port1.7(uplink:1.5)  low----------------------------------------------------------------------------[queue usage rate]  type                                device_name  mac_address                         err_port  route  state============================================================================(detected: 2017/06/13 10:15:42  recovered: 2017/06/13 10:17:24)  swx2310p-10g                        swx2310p-10g_s4k000398  00a0.deae.b89c                      1.6  port1.7(uplink:1.5)  full(queue:2)----------------------------------------------------------------------------[fan lock]  type                                device_name  mac_address  route============================================================================(detected: 2017/06/13 10:28:43  recovered: ----/--/-- --:--:--)  swx2200-8poe                        swx2200-8poe_s45000345  00a0.de83.4146  port1.5(uplink:2)----------------------------------------------------------------------------(detected: 2017/06/13 10:42:13  recovered: 2017/06/13 10:42:22)  swx2200-24g                         swx2200-24g_x00000344  00a0.de2a.dbbb  port1.1(uplink:23)----------------------------------------------------------------------------<<<<<<<<<<<<<<<<<<    terminal monitoring information    >>>>>>>>>>>>>>>>>>>[via ping] date                      status    ip address        description---------------------------------------------------------------------------- 2017/06/13 thu 10:42:56   up        192.168.100.155   ip_camera_1 2017/06/13 thu 10:51:00   down      192.168.100.155   ip_camera_1 2017/06/13 thu 10:54:02   up        192.168.100.10    wireless_ap_1 2017/06/13 thu 11:29:27   up        192.168.100.155   ip_camera_1 2017/06/13 thu 11:30:31   down      192.168.100.10    wireless_ap_1[via bandwidth usage] date                      status    interface         description---------------------------------------------------------------------------- 2017/06/13 thu 10:45:43   up        port1.4           ip_camera_2 2017/06/13 thu 10:45:56   up        port1.6           note_pc_1 2017/06/13 thu 10:50:00   down      port1.6           note_pc_1 2017/06/13 thu 10:53:27   down      port1.4           ip_camera_2[via lldp] date                      status    interface         description---------------------------------------------------------------------------- 2017/06/13 thu 10:53:56   up        port1.3           note_pc_2 2017/06/13 thu 11:11:54   down      port1.3           note_pc_2 2017/06/13 thu 11:14:24   up        port1.3           note_pc_2<<<<<<<<<<<<<<<<<<<<<<<<<<    stack information    >>>>>>>>>>>>>>>>>>>>>>>>> date                      information---------------------------------------------------------------------------- 2017/06/13 thu 10:53:44   the stack port changed state to down. (port1.27) 2017/06/13 thu 10:53:46   promoted to a main. (old main id : 1) 2017/06/13 thu 10:59:10   occurred the heartbeat error. (id : 1)</div><div class="display_word">3.5. Mail body example The body of a notification mail includes content such as the following. For details, refer to the technical reference for each function. Up to 100 items can be included in one notification mail. Model: SWX2310P-28GT                 * Model nameRevision: Rev.2.02.02                * Firmware versionName: SWX2310P-28GT_XXXXXXXX         * Host nameTime: 2017/06/13 11:42:56            * Mail transmission timeTemplate ID: 1                       * Mail template ID<<<<<<<<<<<<<<<<<<<<<<<<    Lan Map Information    >>>>>>>>>>>>>>>>>>>>>>>>>[SFP RX Power]  Type                                Device_Name  MAC_Address                         Err_Port  Route  State============================================================================(Detected: 2017/06/13 10:09:40  Recovered: 2017/06/13 10:10:10)  SWX2310P-10G                        SWX2310P-10G_S4K000398  00a0.deae.b89c                      1.9  port1.7(UpLink:1.5)  Low----------------------------------------------------------------------------[Queue Usage Rate]  Type                                Device_Name  MAC_Address                         Err_Port  Route  State============================================================================(Detected: 2017/06/13 10:15:42  Recovered: 2017/06/13 10:17:24)  SWX2310P-10G                        SWX2310P-10G_S4K000398  00a0.deae.b89c                      1.6  port1.7(UpLink:1.5)  Full(Queue:2)----------------------------------------------------------------------------[Fan Lock]  Type                                Device_Name  MAC_Address  Route============================================================================(Detected: 2017/06/13 10:28:43  Recovered: ----/--/-- --:--:--)  SWX2200-8PoE                        SWX2200-8PoE_S45000345  00a0.de83.4146  port1.5(UpLink:2)----------------------------------------------------------------------------(Detected: 2017/06/13 10:42:13  Recovered: 2017/06/13 10:42:22)  SWX2200-24G                         SWX2200-24G_X00000344  00a0.de2a.dbbb  port1.1(UpLink:23)----------------------------------------------------------------------------<<<<<<<<<<<<<<<<<<    Terminal Monitoring Information    >>>>>>>>>>>>>>>>>>>[via Ping] Date                      Status    IP Address        Description---------------------------------------------------------------------------- 2017/06/13 Thu 10:42:56   UP        192.168.100.155   IP_Camera_1 2017/06/13 Thu 10:51:00   DOWN      192.168.100.155   IP_Camera_1 2017/06/13 Thu 10:54:02   UP        192.168.100.10    Wireless_AP_1 2017/06/13 Thu 11:29:27   UP        192.168.100.155   IP_Camera_1 2017/06/13 Thu 11:30:31   DOWN      192.168.100.10    Wireless_AP_1[via Bandwidth Usage] Date                      Status    Interface         Description---------------------------------------------------------------------------- 2017/06/13 Thu 10:45:43   UP        port1.4           IP_Camera_2 2017/06/13 Thu 10:45:56   UP        port1.6           Note_PC_1 2017/06/13 Thu 10:50:00   DOWN      port1.6           Note_PC_1 2017/06/13 Thu 10:53:27   DOWN      port1.4           IP_Camera_2[via LLDP] Date                      Status    Interface         Description---------------------------------------------------------------------------- 2017/06/13 Thu 10:53:56   UP        port1.3           Note_PC_2 2017/06/13 Thu 11:11:54   DOWN      port1.3           Note_PC_2 2017/06/13 Thu 11:14:24   UP        port1.3           Note_PC_2<<<<<<<<<<<<<<<<<<<<<<<<<<    Stack Information    >>>>>>>>>>>>>>>>>>>>>>>>> Date                      Information---------------------------------------------------------------------------- 2017/06/13 Thu 10:53:44   The stack port changed state to down. (port1.27) 2017/06/13 Thu 10:53:46   Promoted to a main. (Old main ID : 1) 2017/06/13 Thu 10:59:10   Occurred the heartbeat error. (ID : 1)</div></div><div id="oam_oam_mail"><div class="search_title" docfname="oam_oam_mail" doctitle="Mail" link="#lanマップの通知内容">3.5.1. Content of LAN map notifications</div><div class="search_word">3.5.1. content of lan map notifications notification content of each event the content of lan map notification mails differs depending on the event type. the content of notifications for each event type is indicated below. event type device_name mac_address comment stack_id err_port fan_number route route(snapshot) state fan lock yes no no no no yes no no fan speed no yes no no yes no no fan stop no yes no yes yes no no power voltage power supply no yes no no yes no no cpu temperature cpu temperature error phy temperature phy temperature error sfp temperature sfp module temperature error unit temperature unit temperature error pse temperature pse temperature error mac temperature mac temperature error thermal sensor invalid no yes no no yes no no loop detect no no yes no yes no no sfp rx power no no yes no yes no yes over temperature over supply power failure no no no no yes no no class failure forced terminate over current no no yes no yes no no poe state error(over-supply) poe state error(over-temperature) poe state error(fanlock) poe state error(power-failure) no yes no no yes no no illegal equipment(snapshot) yes no no no yes no no port mismatch(snapshot) yes no no no yes yes no disappearance equipment(snapshot) yes no no no no yes no l2ms manager duplication yes no yes no yes no no detailed content of notification a detailed description of the various information included in notifications is indicated below. notification content example: description detected detected: 2021/10/01 8:25:40 indicates the date/time the error occurred. recovered recovered: 2021/10/01 10:09:40 indicates the date/time the error was resolved. type swx2310p-28gt indicates the model name. device_name swx2310p-28gt_xxxxxxxxxx indicates the device name. mac_address ac44.f2xx.xxxx indicates the mac address. comment snapshot: comment indicates comments specified in the lan map device list. l2ms manager duplication: ac44.f2xx.xxxx indicates the mac address of duplicate l2ms managers. stack_id 1 indicates the stack id. err_port 1.5 indicates the port number where the error occurred. fan_number 1 indicates the fan number where the error occurred. route port1.20(uplink:1.2) indicates routing information for applicable devices. route(snapshot) port1.20(uplink:1.2) indicates routing information on the snapshot for applicable devices. state sfp optical rx level abnormality: low indicates sfp optical input level as either “low” or “high”. transmission queue monitoring: full (queue: 2) indicates either “busy” or “full” as the transmission queue usage status and the transmission queue number.</div><div class="display_word">3.5.1. Content of LAN map notifications Notification content of each event The content of LAN map notification mails differs depending on the event type. The content of notifications for each event type is indicated below. Event Type Device_Name MAC_Address Comment Stack_ID Err_Port Fan_number Route Route(SnapShot) State Fan Lock Yes No No No No Yes No No Fan speed No Yes No No Yes No No Fan stop No Yes No Yes Yes No No Power voltage Power supply No Yes No No Yes No No CPU temperature CPU temperature error PHY temperature PHY temperature error SFP temperature SFP module temperature error Unit temperature Unit temperature error PSE temperature PSE temperature error MAC temperature MAC temperature error Thermal Sensor invalid No Yes No No Yes No No Loop Detect No No Yes No Yes No No SFP RX Power No No Yes No Yes No Yes Over Temperature Over Supply Power Failure No No No No Yes No No Class Failure Forced Terminate Over Current No No Yes No Yes No No PoE state error(over-supply) PoE state error(over-temperature) PoE state error(fanlock) PoE state error(power-failure) No Yes No No Yes No No Illegal Equipment(SnapShot) Yes No No No Yes No No Port Mismatch(SnapShot) Yes No No No Yes Yes No Disappearance Equipment(SnapShot) Yes No No No No Yes No L2MS manager duplication Yes No Yes No Yes No No Detailed content of notification A detailed description of the various information included in notifications is indicated below. Notification content Example: Description Detected Detected: 2021/10/01 8:25:40 Indicates the date/time the error occurred. Recovered Recovered: 2021/10/01 10:09:40 Indicates the date/time the error was resolved. Type SWX2310P-28GT Indicates the model name. Device_Name SWX2310P-28GT_XXXXXXXXXX Indicates the device name. MAC_Address ac44.f2xx.xxxx Indicates the MAC address. Comment Snapshot: Comment Indicates comments specified in the LAN map device list. L2MS manager duplication: ac44.f2xx.xxxx Indicates the MAC address of duplicate L2MS managers. Stack_ID 1 Indicates the stack ID. Err_Port 1.5 Indicates the port number where the error occurred. Fan_number 1 Indicates the fan number where the error occurred. Route port1.20(UpLink:1.2) Indicates routing information for applicable devices. Route(SnapShot) port1.20(UpLink:1.2) Indicates routing information on the snapshot for applicable devices. State SFP optical Rx level abnormality: Low Indicates SFP optical input level as either “Low” or “High”. Transmission queue monitoring: Full (Queue: 2) Indicates either “Busy” or “Full” as the transmission queue usage status and the transmission queue number.</div></div><div id="oam_oam_mail"><div class="search_title" docfname="oam_oam_mail" doctitle="Mail" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands smtp mail server setting mail server smtp host smtp mail server name setting mail server smtp name mail notification trigger setting mail notify trigger mail sending template setting mode mail template mail sending server id setting send server mail sender address setting send from mail recipient address setting send to mail subject setting send subject mail wait time setting send notify wait-time mail certificate setting mail send certificate mail certificate notification setting mail send certificate-notify certificate expiration date notification timing setting mail certificate expire-notify show mail information show mail information</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands SMTP mail server setting mail server smtp host SMTP mail server name setting mail server smtp name Mail notification trigger setting mail notify trigger Mail sending template setting mode mail template Mail sending server ID setting send server Mail sender address setting send from Mail recipient address setting send to Mail subject setting send subject Mail wait time setting send notify wait-time Mail certificate setting mail send certificate Mail certificate notification setting mail send certificate-notify Certificate expiration date notification timing setting mail certificate expire-notify Show mail information show mail information</div></div><div id="oam_oam_mail"><div class="search_title" docfname="oam_oam_mail" doctitle="Mail" link="#注意事項">5. Points of Caution</div><div class="search_word">5. points of caution the following are precautions related to smtp authentication. the smtp authentication only supports the login method. plain, cram-md5, and other methods are not supported. precautions for using firmware not compatible with the mail notification function. if the firmware is updated from a version that does not support a command to a version that does support the command, commands specified in the web gui are directly carried over as command settings. to revert to the firmware version that does not support the commands, any changes to settings made using the firmware that does support the commands are not migrated and must be specified again after restoring the older version. if no settings were changed, then the current settings can be maintained. the following are precautions related to lan map error detection. errors are indicated in notifications as active until the error is resolved, even if the error notification is disabled without resolving the error. specifically, even after a notification is disabled, an mail is sent after the error is resolved and is included in mails about the occurrence of other errors.</div><div class="display_word">5. Points of Caution The following are precautions related to SMTP authentication. The SMTP authentication only supports the LOGIN method. PLAIN, CRAM-MD5, and other methods are not supported. Precautions for using firmware not compatible with the mail notification function. If the firmware is updated from a version that does not support a command to a version that does support the command, commands specified in the web GUI are directly carried over as command settings. To revert to the firmware version that does not support the commands, any changes to settings made using the firmware that does support the commands are not migrated and must be specified again after restoring the older version. If no settings were changed, then the current settings can be maintained. The following are precautions related to LAN map error detection. Errors are indicated in notifications as active until the error is resolved, even if the error notification is disabled without resolving the error. Specifically, even after a notification is disabled, an mail is sent after the error is resolved and is included in mails about the occurrence of other errors.</div></div><div id="oam_oam_mail"><div class="search_title" docfname="oam_oam_mail" doctitle="Mail" link="#関連文書">6. Related Documentation</div><div class="search_word">6. related documentation l2ms control terminal monitoring stacking</div><div class="display_word">6. Related Documentation L2MS Control Terminal Monitoring Stacking</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#パフォーマンスの観測">Performance Observations</div><div class="search_word">performance observations</div><div class="display_word">Performance Observations</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product provides a mechanism for constantly observing the system’s performance. an overview of the function is given below. this product constantly observes the following three types of data. resource usage amount: cpu and memory usage amount traffic volume: the volume of communication port bandwidth used (transmission/reception) power consumption: estimated based on the link speed, poe power supply level, and fan rpm based on the results of observation, one year’s worth of the following change data is accumulated inside this product. hourly change : change for each hour (e.g. 0:00, 1:00, ...) daily change : change for each day of each month (e.g. 1/1, 1/2, ...) weekly change : change for each day of the week (e.g. sun, mon, ...) monthly change : change for each month (e.g. jan, feb, ...) the accumulated data can be backed up to an sd card. * by accessing this product via the web gui, the maintenance personnel can view the various types of change data including live data in the dashboard, and can also acquire the accumulated result in a pc. since the acquired data is in *csv format , it can also be manipulated using spreadsheet software on a pc. maintenance personnel can use this functionality for the following purposes. determine the short-term communication status predict long-term network equipment demand notice wasteful power consumption by determining current power consumption levels</div><div class="display_word">1. Function Overview This product provides a mechanism for constantly observing the system’s performance. An overview of the function is given below. This product constantly observes the following three types of data. Resource usage amount: CPU and memory usage amount Traffic volume: The volume of communication port bandwidth used (transmission/reception) Power consumption: Estimated based on the link speed, PoE power supply level, and fan RPM Based on the results of observation, one year’s worth of the following change data is accumulated inside this product. Hourly change : Change for each hour (e.g. 0:00, 1:00, ...) Daily change : Change for each day of each month (e.g. 1/1, 1/2, ...) Weekly change : Change for each day of the week (e.g. SUN, MON, ...) Monthly change : Change for each month (e.g. Jan, Feb, ...) The accumulated data can be backed up to an SD card. * By accessing this product via the Web GUI, the maintenance personnel can view the various types of change data including live data in the dashboard, and can also acquire the accumulated result in a PC. Since the acquired data is in *CSV format , it can also be manipulated using spreadsheet software on a PC. Maintenance personnel can use this functionality for the following purposes. Determine the short-term communication status Predict long-term network equipment demand Notice wasteful power consumption by determining current power consumption levels</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used none</div><div class="display_word">2. Definition of Terms Used None</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#リソーストラフィック使用量の観測">3.1. Resource and traffic usage observation</div><div class="search_word">3.1. resource and traffic usage observation starting immediately after boot, this device automatically observes the cpu and memory and the transmit/receive throughput of each port every second. * the observed data is *normalized using a moving average , and one year of data is saved in ram .</div><div class="display_word">3.1. Resource and traffic usage observation Starting immediately after boot, this device automatically observes the CPU and memory and the transmit/receive throughput of each port every second. * The observed data is *normalized using a moving average , and one year of data is saved in RAM .</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#観測データのバックアップ">3.2. Observation data backup</div><div class="search_word">3.2. observation data backup backup of observation data can be specified only in the web gui. backup of observation data assumes that an sd card is inserted in this device. if backup is enabled, the most recent hour of observation data every hour starting at the point it was enabled (e.g., 1:00, 2:00 ...) is saved on the sd card. the saved data is dedicated binary data of this device. the save-destination on the sd card and the file name of the backup data file are as follows. resource information hourly change data /[model name]/data/resource/yyyymm_smsys_res_monitor_hour.bin daily change data (data for each day) /[model name]/data/resource/yyyymm_smsys_res_monitor_day.bin weekly change data /[model name]/data/resource/yyyymm_smsys_res_monitor_week.bin monthly change data /[model name]/data/resource/yyyy_smsys_res_monitor_month.bin traffic information hourly change data /[model name]/data/trf/yyyymm_trf_bandwidth_hour.bin daily change data /[model name]/data/trf/yyyymm_trf_bandwidth_day.bin weekly change data /[model name]/data/trf/yyyymm_trf_bandwidth_week.bin monthly change data /[model name]/data/trf/yyyy_trf_bandwidth_month.bin power consumption information hourly change data /[model name]/data/power/yyyymm_smsys_pwr_monitor_hour.bin daily change data /[model name]/data/power/yyyymm_smsys_pwr_monitor_day.bin weekly change data /[model name]/data/power/yyyymm_smsys_pwr_monitor_week.bin monthly change data /[model name]/data/power/yyyy_smsys_pwr_monitor_month.bin [model name] is the following. for the swx2320-16mt: swx2320 for the swx2322p-16m: swx2322p for the swx3220-16mt/16tms: swx3220 for the swx3200-28gt/52gt: swx3200 for the swx3100-10g/18gt: swx3100 for the swx2310p-10g/18g/28gt: swx2310p for the swx2310-10g/18gt/28gt/52gt: swx2310 yyyy: year, mm: month will be set. since this is a proprietary yamaha format, it cannot be referenced.</div><div class="display_word">3.2. Observation data backup Backup of observation data can be specified only in the Web GUI. Backup of observation data assumes that an SD card is inserted in this device. If backup is enabled, the most recent hour of observation data every hour starting at the point it was enabled (e.g., 1:00, 2:00 ...) is saved on the SD card. The saved data is dedicated binary data of this device. The save-destination on the SD card and the file name of the backup data file are as follows. Resource information Hourly change data /[model name]/data/resource/YYYYMM_smsys_res_monitor_hour.bin Daily change data (data for each day) /[model name]/data/resource/YYYYMM_smsys_res_monitor_day.bin Weekly change data /[model name]/data/resource/YYYYMM_smsys_res_monitor_week.bin Monthly change data /[model name]/data/resource/YYYY_smsys_res_monitor_month.bin Traffic information Hourly change data /[model name]/data/trf/YYYYMM_trf_bandwidth_hour.bin Daily change data /[model name]/data/trf/YYYYMM_trf_bandwidth_day.bin Weekly change data /[model name]/data/trf/YYYYMM_trf_bandwidth_week.bin Monthly change data /[model name]/data/trf/YYYY_trf_bandwidth_month.bin Power consumption information Hourly change data /[model name]/data/power/YYYYMM_smsys_pwr_monitor_hour.bin Daily change data /[model name]/data/power/YYYYMM_smsys_pwr_monitor_day.bin Weekly change data /[model name]/data/power/YYYYMM_smsys_pwr_monitor_week.bin Monthly change data /[model name]/data/power/YYYY_smsys_pwr_monitor_month.bin [Model name] is the following. For the SWX2320-16MT: swx2320 For the SWX2322P-16M: swx2322p For the SWX3220-16MT/16TMs: swx3220 For the SWX3200-28GT/52GT: swx3200 For the SWX3100-10G/18GT: swx3100 For the SWX2310P-10G/18G/28GT: swx2310p For the SWX2310-10G/18GT/28GT/52GT: swx2310 YYYY: Year, MM: month will be set. Since this is a proprietary Yamaha format, it cannot be referenced.</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#観測データのエクスポートデータ">3.3. Observation data export</div><div class="search_word">3.3. observation data export observation data can be exported to a computer only via the web gui. data is exported as *multiple csv files compressed in zip format. * the structure of the compressed files are given below. when resource observation data is exported zip file name: yyyymmddhhmmss_resource_csv.zip folder structure yyyymmddhhmmss_resource_csv    +- 20170922_resource_hour.csv (1) +-     :    +- 20170925_resource_hour.csv (2) +- 201709_resource_day.csv (3) 1 cpu, memory, and hourly change data for september 22, 2017 2 cpu, memory, and hourly change data for september 25, 2017 3 cpu, memory, and daily change data for september 2017 when transmission traffic observation data is exported zip file name: yyyymmddhhmmss_trf_tx_csv.zip folder structure yyyymmddhhmmss_trf_tx_csv    +- 20170922_trf_tx_hour.csv (1) +-     :    +- 20170925_trf_tx_hour.csv (2) +- 201709_trf_tx_day.csv (3) 1 transmission traffic and hourly change data for september 22, 2017 2 transmission traffic and hourly change data for september 25, 2017 3 transmission traffic and daily change data for september 2017 when reception traffic observation data is exported zip file name: yyyymmddhhmmss_trf_rx_csv.zip folder structure yyyymmddhhmmss_trf_rx_csv    +- 20170922_trf_rx_hour.csv (1) +-     :    +- 20170925_trf_rx_hour.csv (2) +- 201709_trf_rx_day.csv (3) 1 reception traffic and hourly change data for september 22, 2017 2 reception traffic and hourly change data for september 25, 2017 3 reception traffic and daily change data for september 2017 if power consumption observation data was exported zip file name: yyyymmddhhmmss_pwr_csv.zip folder structure yyyymmddhhmmss_pwr_csv    +- 20170922_pwr_hour.csv (1) +-     :    +- 20170925_pwr_hour.csv (2) +- 201709_pwr_day.csv (3) 1 power consumption and hourly change data for september 22, 2017 2 power consumption and hourly change data for september 25, 2017 3 power consumption and daily change data for september 2017 yyyymmddhhmmss specifies the date and time when the data was exported (date and time the file was created).</div><div class="display_word">3.3. Observation data export Observation data can be exported to a computer only via the web GUI. Data is exported as *multiple CSV files compressed in zip format. * The structure of the compressed files are given below. When resource observation data is exported zip file name: YYYYMMDDhhmmss_resource_csv.zip Folder structure YYYYMMDDhhmmss_resource_csv    +- 20170922_resource_hour.csv (1) +-     :    +- 20170925_resource_hour.csv (2) +- 201709_resource_day.csv (3) 1 CPU, memory, and hourly change data for September 22, 2017 2 CPU, memory, and hourly change data for September 25, 2017 3 CPU, memory, and daily change data for September 2017 When transmission traffic observation data is exported zip file name: YYYYMMDDhhmmss_trf_tx_csv.zip Folder structure YYYYMMDDhhmmss_trf_tx_csv    +- 20170922_trf_tx_hour.csv (1) +-     :    +- 20170925_trf_tx_hour.csv (2) +- 201709_trf_tx_day.csv (3) 1 Transmission traffic and hourly change data for September 22, 2017 2 Transmission traffic and hourly change data for September 25, 2017 3 Transmission traffic and daily change data for September 2017 When reception traffic observation data is exported zip file name: YYYYMMDDhhmmss_trf_rx_csv.zip Folder structure YYYYMMDDhhmmss_trf_rx_csv    +- 20170922_trf_rx_hour.csv (1) +-     :    +- 20170925_trf_rx_hour.csv (2) +- 201709_trf_rx_day.csv (3) 1 Reception traffic and hourly change data for September 22, 2017 2 Reception traffic and hourly change data for September 25, 2017 3 Reception traffic and daily change data for September 2017 If power consumption observation data was exported zip file name: YYYYMMDDhhmmss_pwr_csv.zip Folder structure YYYYMMDDhhmmss_pwr_csv    +- 20170922_pwr_hour.csv (1) +-     :    +- 20170925_pwr_hour.csv (2) +- 201709_pwr_day.csv (3) 1 Power consumption and hourly change data for September 22, 2017 2 Power consumption and hourly change data for September 25, 2017 3 Power consumption and daily change data for September 2017 YYYYMMDDhhmmss specifies the date and time when the data was exported (date and time the file was created).</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands this function does not support settings via commands.</div><div class="display_word">4. Related Commands This function does not support settings via commands.</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#web-gui-による設定">5. Settings via the Web GUI</div><div class="search_word">5. settings via the web gui performance observation can be controlled from the following pages of the web gui. viewing the resource usage amount this can be viewed in the [dashboard] item [resource information (graph)] . viewing the traffic usage amount this can be viewed in the [dashboard] item [traffic information (graph)] . viewing power consumption data data can be viewed in the [power consumption information (graph)] field on the [dashboard] . backing up, clearing, or exporting observation data select [management] and then settings can be specified in the [maintenance] - [summary data management] field. (data can also be cleared or exported using the menu buttons ( ) in each [dashboard] gadget.) details on how to view and make settings in each screen can be referenced via the web gui help.</div><div class="display_word">5. Settings via the Web GUI Performance observation can be controlled from the following pages of the Web GUI. Viewing the resource usage amount This can be viewed in the [Dashboard] item [Resource information (graph)] . Viewing the traffic usage amount This can be viewed in the [Dashboard] item [Traffic information (graph)] . Viewing power consumption data Data can be viewed in the [Power consumption information (graph)] field on the [Dashboard] . Backing up, clearing, or exporting observation data Select [Management] and then settings can be specified in the [Maintenance] - [Summary data management] field. (Data can also be cleared or exported using the menu buttons ( ) in each [Dashboard] gadget.) Details on how to view and make settings in each screen can be referenced via the Web GUI help.</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#リソース使用量の参照">5.1. Viewing the resource usage amount</div><div class="search_word">5.1. viewing the resource usage amount the resource information (graph) screen is shown below. example when live is selected for resource information (graph) the graph rendering can be changed using the following buttons. current situation: live the various current usage ratios are obtained at one-second intervals and shown on the graph. hourly change: day the various usage ratios for the specified day are shown at one-hour intervals on the graph. to specify the day, use the day-specifying box in the upper right of the gadget. daily change: month the various usage ratios for the specified month are shown at one-day intervals. to specify the month, use the month-specifying box in the upper right of the gadget. monthly change: year the various usage ratios for the specified year are shown at one-month intervals. to specify the year, use the select box in the upper right of the gadget. it is not currently possible to reference changes in the day of the week. if the cpu and memory usage ratios exceed 80% , then *a warning message is shown on the dashboard. * if the ratio falls below 80% after having exceeded 80%, the warning is automatically cleared.</div><div class="display_word">5.1. Viewing the resource usage amount The resource information (graph) screen is shown below. Example when Live is selected for resource information (graph) The graph rendering can be changed using the following buttons. Current situation: Live The various current usage ratios are obtained at one-second intervals and shown on the graph. Hourly change: Day The various usage ratios for the specified day are shown at one-hour intervals on the graph. To specify the day, use the day-specifying box in the upper right of the gadget. Daily change: Month The various usage ratios for the specified month are shown at one-day intervals. To specify the month, use the month-specifying box in the upper right of the gadget. Monthly change: Year The various usage ratios for the specified year are shown at one-month intervals. To specify the year, use the select box in the upper right of the gadget. It is not currently possible to reference changes in the day of the week. If the CPU and memory usage ratios exceed 80% , then *a warning message is shown on the dashboard. * If the ratio falls below 80% after having exceeded 80%, the warning is automatically cleared.</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#トラフィック使用量の参照">5.2. Viewing the traffic usage amount</div><div class="search_word">5.2. viewing the traffic usage amount the traffic usage amount (graph) screen is shown below. example of when traffic usage amount (graph) day is selected / example of reception traffic the traffic usage amount of each port can be shown separately for transmission and reception . the graph rendering can be changed using the following buttons. current situation: live the various current usage ratios are obtained at one-second intervals and shown on the graph. the most recent two minutes of the obtained data is held and rendered on the graph. hourly change: day the various usage ratios for the specified day are shown at one-hour intervals on the graph. to specify the day, use the day-specifying box in the upper right of the gadget. daily change: month the various usage ratios for the specified month are shown at one-day intervals. to specify the month, use the month-specifying box in the upper right of the gadget. monthly change: year the various usage ratios for the specified year are shown at one-month intervals. to specify the year, use the select box in the upper right of the gadget. it is not currently possible to reference changes in the day of the week. to select the interface to be shown, click the [interface selection] menu button ( ) and then select the interface in the following screen. if the traffic usage ratio exceeds 60%, a warning message is shown on the dashboard. if the ratio falls below 50% after having exceeded 60%, the warning is automatically cleared.</div><div class="display_word">5.2. Viewing the traffic usage amount The traffic usage amount (graph) screen is shown below. Example of when traffic usage amount (graph) Day is selected / Example of reception traffic The traffic usage amount of each port can be shown separately for transmission and reception . The graph rendering can be changed using the following buttons. Current situation: Live The various current usage ratios are obtained at one-second intervals and shown on the graph. The most recent two minutes of the obtained data is held and rendered on the graph. Hourly change: Day The various usage ratios for the specified day are shown at one-hour intervals on the graph. To specify the day, use the day-specifying box in the upper right of the gadget. Daily change: Month The various usage ratios for the specified month are shown at one-day intervals. To specify the month, use the month-specifying box in the upper right of the gadget. Monthly change: Year The various usage ratios for the specified year are shown at one-month intervals. To specify the year, use the select box in the upper right of the gadget. It is not currently possible to reference changes in the day of the week. To select the interface to be shown, click the [Interface selection] menu button ( ) and then select the interface in the following screen. If the traffic usage ratio exceeds 60%, a warning message is shown on the dashboard. If the ratio falls below 50% after having exceeded 60%, the warning is automatically cleared.</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#消費電力量の参照">5.3. Viewing power consumption data</div><div class="search_word">5.3. viewing power consumption data the power consumption information (graph) screen is shown below. example of power consumption information (graph) when live is selected. the graph rendering can be changed using the following buttons. current situation: live this shows the current power consumption levels measured at one-second intervals. hourly change: day this shows the power consumption levels on the specified date at one-hour intervals. to specify the day, use the day-specifying box in the upper right of the gadget. daily change: month this shows the power consumption levels during the specified month at one-day intervals. to specify the month, use the month-specifying box in the upper right of the gadget. monthly change: year this shows the power consumption levels during the specified year at one-month intervals. to specify the year, use the select box in the upper right of the gadget. it is not currently possible to reference changes in the day of the week. the following recommended methods reduce power consumption. decrease the link speed of ports with low bandwidth usage. use the schedule execution function to shut down unused ports and poe power supply at midnight and on holidays.</div><div class="display_word">5.3. Viewing power consumption data The power consumption information (graph) screen is shown below. Example of power consumption information (graph) when Live is selected. The graph rendering can be changed using the following buttons. Current situation: Live This shows the current power consumption levels measured at one-second intervals. Hourly change: Day This shows the power consumption levels on the specified date at one-hour intervals. To specify the day, use the day-specifying box in the upper right of the gadget. Daily change: Month This shows the power consumption levels during the specified month at one-day intervals. To specify the month, use the month-specifying box in the upper right of the gadget. Monthly change: Year This shows the power consumption levels during the specified year at one-month intervals. To specify the year, use the select box in the upper right of the gadget. It is not currently possible to reference changes in the day of the week. The following recommended methods reduce power consumption. Decrease the link speed of ports with low bandwidth usage. Use the Schedule execution function to shut down unused ports and PoE power supply at midnight and on holidays.</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#観測データのバックアップクリアエクスポート">5.4. Backing up, clearing, or exporting observation data</div><div class="search_word">5.4. backing up, clearing, or exporting observation data backup, clearing, and exporting of observation data is performed from [management] - [maintenance] - [summary data management] . (data can also be cleared or exported using the menu buttons ( ) in each [dashboard] gadget.) the [summary data management] screen is shown below. summary data management screen (top page)</div><div class="display_word">5.4. Backing up, clearing, or exporting observation data Backup, clearing, and exporting of observation data is performed from [Management] - [Maintenance] - [Summary data management] . (Data can also be cleared or exported using the menu buttons ( ) in each [Dashboard] gadget.) The [Summary data management] screen is shown below. Summary data management screen (top page)</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#観測データのバックアップ設定">5.4.1. Observation data backup settings</div><div class="search_word">5.4.1. observation data backup settings make the observation data backup settings from [top page] - [backup settings for summary data] . the screen that appears after you press the [settings] button is shown below. observation data backup settings screen place a check mark in the check box of the summary data for which you want to enable backup, and then press the [confirm] button. after you press the button, the following screen appears. if you decide to cancel this setting, press the [back] button in each screen.</div><div class="display_word">5.4.1. Observation data backup settings Make the observation data backup settings from [Top page] - [Backup settings for summary data] . The screen that appears after you press the [Settings] button is shown below. Observation data backup settings screen Place a check mark in the check box of the summary data for which you want to enable backup, and then press the [Confirm] button. After you press the button, the following screen appears. If you decide to cancel this setting, press the [Back] button in each screen.</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#観測データのクリア">5.4.2. Clearing observation data</div><div class="search_word">5.4.2. clearing observation data clear the observation data from [top page] - [clearing summary data] . (data can also be cleared using the menu buttons ( ) in each [dashboard] gadget.) the screen that appears after you press the [next] button is shown below. clear observation data screen in the select box, choose the summary data to be cleared and then click the [confirm] button. after you press the button, the following screen appears. to cancel the operation, click the [back] button displayed in each screen.</div><div class="display_word">5.4.2. Clearing observation data Clear the observation data from [Top page] - [Clearing summary data] . (Data can also be cleared using the menu buttons ( ) in each [Dashboard] gadget.) The screen that appears after you press the [Next] button is shown below. Clear observation data screen In the select box, choose the summary data to be cleared and then click the [Confirm] button. After you press the button, the following screen appears. To cancel the operation, click the [Back] button displayed in each screen.</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#観測データのエクスポート">5.4.3. Exporting observation data</div><div class="search_word">5.4.3. exporting observation data export the observation data from [top page] - [export summary data] in the summary data management. (data can also be exported using the menu buttons ( ) in each [dashboard] gadget.) the screen that appears after you press the [next] button is shown below. observation data export screen in the select box, choose the observation data to be exported to the computer used to access the web gui. then select the time period of observation data to be exported. after selecting the period, click the [ok] button to download the zip file. to cancel the operation, click the [back] button.</div><div class="display_word">5.4.3. Exporting observation data Export the observation data from [Top page] - [Export summary data] in the summary data management. (Data can also be exported using the menu buttons ( ) in each [Dashboard] gadget.) The screen that appears after you press the [Next] button is shown below. Observation data export screen In the select box, choose the observation data to be exported to the computer used to access the web GUI. Then select the time period of observation data to be exported. After selecting the period, click the [OK] button to download the zip file. To cancel the operation, click the [Back] button.</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution none</div><div class="display_word">6. Points of Caution None</div></div><div id="oam_oam_performance"><div class="search_title" docfname="oam_oam_performance" doctitle="Performance" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation none</div><div class="display_word">7. Related Documentation None</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#proav設定">ProAV Settings</div><div class="search_word">proav settings</div><div class="display_word">ProAV Settings</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview from the web gui “proav settings” page, you can perform simple gui operations to collectively configure optimal settings for avoip networks on which to transmit audio and video traffic such as dante and ndi. the following proav profiles can be set on this product. dante ndi this technical reference explains the details on the commands that are set when a proav profile is applied, as well as kitting (initial setup) and troubleshooting. for details on how to use the web gui “proav settings” page, refer to ###.</div><div class="display_word">1. Function Overview From the web GUI “ProAV Settings” page, you can perform simple GUI operations to collectively configure optimal settings for AVoIP networks on which to transmit audio and video traffic such as Dante and NDI. The following ProAV profiles can be set on this product. Dante NDI This technical reference explains the details on the commands that are set when a ProAV profile is applied, as well as kitting (initial setup) and troubleshooting. For details on how to use the web GUI “ProAV Settings” page, refer to ###.</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used dante dante is a professional audio networking solution developed by audinate, inc. a single lan cable can be used to carry out bidirectional communication of all the information required for a digital audio system, such as multi-channel audio transmission, clock synchronization signals, and control signals. ndi ndi is a new protocol developed by newtek, inc. to support live video production workflows over ip. in a typical gigabit ethernet environment, this protocol enables real-time mutual transmission of information such as video, audio, and metadata. yamaha lan monitor yamaha lan monitor is a computer application that allows you to monitor and control yamaha network switch information and connected devices on your computer.</div><div class="display_word">2. Definition of Terms Used Dante Dante is a professional audio networking solution developed by Audinate, Inc. A single LAN cable can be used to carry out bidirectional communication of all the information required for a digital audio system, such as multi-channel audio transmission, clock synchronization signals, and control signals. NDI NDI is a new protocol developed by Newtek, Inc. to support live video production workflows over IP. In a typical Gigabit Ethernet environment, this protocol enables real-time mutual transmission of information such as video, audio, and metadata. Yamaha LAN Monitor Yamaha LAN Monitor is a computer application that allows you to monitor and control Yamaha network switch information and connected devices on your computer.</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#proavプロファイル詳細">3. Details on ProAV Profiles</div><div class="search_word">3. details on proav profiles</div><div class="display_word">3. Details on ProAV Profiles</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#danteプロファイル">3.1. Dante profiles</div><div class="search_word">3.1. dante profiles the following commands are collectively applied by dante profiles. list of commands applied by dante profiles object of setting function commands entire system disable flow control flowcontrol disable enable qos qos enable optimize transmission queue by dscp value qos dscp-queue 8 2 qos dscp-queue 26 3 qos dscp-queue 34 4 qos dscp-queue 46 5 qos dscp-queue 48 5 qos dscp-queue 56 7 qos dscp-queue [not indicated above] 0 no qos wrr-weight [0 to 7] always forward linked local multicasts l2-unknown-mcast forward link-local enable lldp lldp run enable ptp ptp enable vlan interface set profile type proav profile-type dante-primary/dante-secondary cancel shutdown no shutdown flood unknown multicasts l2-unknown-mcast flood always forward ptp packets l2-mcast flood 224.0.1.129 l2-mcast flood 224.0.1.130 l2-mcast flood 224.0.1.131 l2-mcast flood 224.0.1.132 l2-mcast flood 239.254.3.3 enable igmp snooping ip igmp snooping enable set igmp snooping version ip igmp snooping version 3 enable igmp snooping fast-leave function ip igmp snooping fast-leave auto-assignment enable igmp query transmission function ip igmp snooping querier set igmp query transmission interval ip igmp snooping query-interval 30 disable igmp report-suppression function ip igmp snooping report-suppression disable enable igmp report forwarding function ip igmp snooping report-forward enable disable igmp packet ttl value checking function ip igmp snooping check ttl disable disable igmp packet ra checking function ip igmp snooping check ra disable disable igmp packet tos checking function ip igmp snooping check tos disable enable data transfer suppression function for multicast router ports ip igmp snooping mrouter-port data-suppression enable lan/sfp port disable flow control flowcontrol disable set mru mru 1522 set qos trust mode to dscp qos trust dscp set l2ms filter l2ms filter disable / enable (*1) set bpdu filter spanning-tree bpdu-filter disable / enable (*2) disable eee eee disable enable lldp transmission and reception lldp-agent set lldp enable txrx tlv-select basic-mgmt enable ptp ptp enable details on the settings are as follows: disable flow control disabling flow control ensures that transmission and reception of dante traffic continue even when the bandwidth is congested. enable qos by enabling qos , the priority is given to dante traffic forwarding. by optimizing transmission queues by dscp value , dscp values related to dante traffic are assigned to high-priority transmission queues. by setting the qos trust mode to dscp , the priority control is performed by referring to the dscp values. enable igmp snooping by enabling igmp snooping , multicast traffic is forwarded only to ports where multicast receivers exist, and unnecessary traffic is not forwarded. set the igmp snooping version to igmpv3 . in a network configuration using multiple switches, if the switches have different versions, a warning message will be displayed on the “multicast page” of the proav gui. when using a dante network, set the version to igmpv3. by enabling the igmp snooping fast leave function , multicast traffic forwarding stops immediately when a multicast receiver stops receiving it. when a multicast receiver switches between audio and video, the multicast traffic before the switching can be prevented from causing noise. by enabling the auto-assignment option of the fast leave function , fast leave is not performed on ports connecting switches in a network configuration using multiple switches. this prevents immediate stop of multicast traffic forwarding when receivers who want to receive the multicast traffic still exist on the opposing switch. enable the igmp query transmission function (querier function) . when igmp snooping is used, a querier must exist on the same network. if there are multiple queriers on the same network, the querier with the smallest ip address becomes the representative querier, and the other queriers automatically stop transmitting queries. by setting the igmp query transmission interval to 30 seconds , the igmp snooping learning state can converge more quickly. by disabling the igmp report suppression function , igmp reports are forwarded directly without being proxied in a network configuration using multiple switches. by enabling the igmp report suppression function , igmp reports are forwarded directly without being proxied in a network configuration using multiple switches. by disabling the igmp packet ttl value/ra/tos checking function , even if an invalid igmp packet is received, the information is appropriately corrected and the igmp packet is forwarded. by enabling the data transfer suppression function for multicast router ports , you can conserve the bandwidth between switches in a network configuration using multiple switches. normally, all multicast traffic is forwarded to the multicast router port regardless of existence of a multicast receiver. therefore, in a bidirectional transmission environment, unnecessary multicast traffic consumes the bandwidth between switches. by using this function, multicast traffic is forwarded only if a multicast receiver exists on the opposing switch, thereby conserving the bandwidth between switches. always forward control-use multicast packets by always forwarding linked local multicasts , control packets such as mdns used by dante are always forwarded when igmp snooping is enabled. by always forwarding ptp packets , control packets for time synchronization used by dante are always forwarded when igmp snooping is enabled. by flooding unknown multicasts , multicast traffic without a receiver is forwarded when igmp snooping is enabled. disable jumbo frames by setting the mru to 1522 bytes , jumbo frame forwarding is disabled. disable eee disabling the power saving function prevents the function from affecting data transfer performance. enable lldp enabling lldp transmission and reception enables the igmp snooping fast leave function and the igmp report forwarding function . this is because these two igmp functions operate by using lldp to determine whether the opposing device is a switch. set l2ms filter (*1) only if the dante network is configured as a redundant dante primary/secondary configuration, the l2ms filter is enabled on the dante secondary port. l2ms refers to a yamaha-original control packet used to monitor and control yamaha switches with integrated management applications such as yamaha lan monitor. in the redundant configuration, the switches are connected with two cables, a primary cable and a secondary cable. therefore, enabling the l2ms filter prevents control packets from looping and causing congestion. in addition, in network configurations other than the redundant configuration, the l2ms filter is disabled . set bpdu filter (*2) only if the dante network is configured as a redundant dante primary/secondary configuration, the bpdu filter is enabled on the dante secondary port. in a redundant configuration, the network switches are connected with two cables, a primary cable and a secondary cable. therefore, enabling the bpdu filter prevents port blocking. in addition, in network configurations other than the redundant configuration, the bpdu filter is disabled . set profile type this setting is used as an identifier to identify the profile type in the proav gui.</div><div class="display_word">3.1. Dante profiles The following commands are collectively applied by Dante profiles. List of commands applied by Dante profiles Object of setting Function Commands Entire system Disable flow control flowcontrol disable Enable QoS qos enable Optimize transmission queue by DSCP value qos dscp-queue 8 2 qos dscp-queue 26 3 qos dscp-queue 34 4 qos dscp-queue 46 5 qos dscp-queue 48 5 qos dscp-queue 56 7 qos dscp-queue [not indicated above] 0 no qos wrr-weight [0 to 7] Always forward linked local multicasts l2-unknown-mcast forward link-local Enable LLDP lldp run Enable PTP ptp enable VLAN interface Set profile type proav profile-type dante-primary/dante-secondary Cancel shutdown no shutdown Flood unknown multicasts l2-unknown-mcast flood Always forward PTP packets l2-mcast flood 224.0.1.129 l2-mcast flood 224.0.1.130 l2-mcast flood 224.0.1.131 l2-mcast flood 224.0.1.132 l2-mcast flood 239.254.3.3 Enable IGMP snooping ip igmp snooping enable Set IGMP snooping version ip igmp snooping version 3 Enable IGMP snooping fast-leave function ip igmp snooping fast-leave auto-assignment Enable IGMP query transmission function ip igmp snooping querier Set IGMP query transmission interval ip igmp snooping query-interval 30 Disable IGMP report-suppression function ip igmp snooping report-suppression disable Enable IGMP report forwarding function ip igmp snooping report-forward enable Disable IGMP packet TTL value checking function ip igmp snooping check ttl disable Disable IGMP packet RA checking function ip igmp snooping check ra disable Disable IGMP packet ToS checking function ip igmp snooping check tos disable Enable data transfer suppression function for multicast router ports ip igmp snooping mrouter-port data-suppression enable LAN/SFP port Disable flow control flowcontrol disable Set MRU mru 1522 Set QoS trust mode to DSCP qos trust dscp Set L2MS filter l2ms filter disable / enable (*1) Set BPDU filter spanning-tree bpdu-filter disable / enable (*2) Disable EEE eee disable Enable LLDP transmission and reception lldp-agent set lldp enable txrx tlv-select basic-mgmt Enable PTP ptp enable Details on the settings are as follows: Disable flow control Disabling flow control ensures that transmission and reception of Dante traffic continue even when the bandwidth is congested. Enable QoS By enabling QoS , the priority is given to Dante traffic forwarding. By optimizing transmission queues by DSCP value , DSCP values related to Dante traffic are assigned to high-priority transmission queues. By setting the QoS trust mode to DSCP , the priority control is performed by referring to the DSCP values. Enable IGMP snooping By enabling IGMP snooping , multicast traffic is forwarded only to ports where multicast receivers exist, and unnecessary traffic is not forwarded. Set the IGMP snooping version to IGMPv3 . In a network configuration using multiple switches, if the switches have different versions, a warning message will be displayed on the “Multicast page” of the ProAV GUI. When using a Dante network, set the version to IGMPv3. By enabling the IGMP snooping fast leave function , multicast traffic forwarding stops immediately when a multicast receiver stops receiving it. When a multicast receiver switches between audio and video, the multicast traffic before the switching can be prevented from causing noise. By enabling the auto-assignment option of the fast leave function , fast leave is not performed on ports connecting switches in a network configuration using multiple switches. This prevents immediate stop of multicast traffic forwarding when receivers who want to receive the multicast traffic still exist on the opposing switch. Enable the IGMP query transmission function (querier function) . When IGMP snooping is used, a querier must exist on the same network. If there are multiple queriers on the same network, the querier with the smallest IP address becomes the representative querier, and the other queriers automatically stop transmitting queries. By setting the IGMP query transmission interval to 30 seconds , the IGMP snooping learning state can converge more quickly. By disabling the IGMP report suppression function , IGMP reports are forwarded directly without being proxied in a network configuration using multiple switches. By enabling the IGMP report suppression function , IGMP reports are forwarded directly without being proxied in a network configuration using multiple switches. By disabling the IGMP packet TTL value/RA/ToS checking function , even if an invalid IGMP packet is received, the information is appropriately corrected and the IGMP packet is forwarded. By enabling the data transfer suppression function for multicast router ports , you can conserve the bandwidth between switches in a network configuration using multiple switches. Normally, all multicast traffic is forwarded to the multicast router port regardless of existence of a multicast receiver. Therefore, in a bidirectional transmission environment, unnecessary multicast traffic consumes the bandwidth between switches. By using this function, multicast traffic is forwarded only if a multicast receiver exists on the opposing switch, thereby conserving the bandwidth between switches. Always forward control-use multicast packets By always forwarding linked local multicasts , control packets such as mDNS used by Dante are always forwarded when IGMP snooping is enabled. By always forwarding PTP packets , control packets for time synchronization used by Dante are always forwarded when IGMP snooping is enabled. By flooding unknown multicasts , multicast traffic without a receiver is forwarded when IGMP snooping is enabled. Disable jumbo frames By setting the MRU to 1522 bytes , jumbo frame forwarding is disabled. Disable EEE Disabling the power saving function prevents the function from affecting data transfer performance. Enable LLDP Enabling LLDP transmission and reception enables the IGMP snooping fast leave function and the IGMP report forwarding function . This is because these two IGMP functions operate by using LLDP to determine whether the opposing device is a switch. Set L2MS filter (*1) Only if the Dante network is configured as a redundant Dante primary/secondary configuration, the L2MS filter is enabled on the Dante secondary port. L2MS refers to a Yamaha-original control packet used to monitor and control Yamaha switches with integrated management applications such as Yamaha LAN Monitor. In the redundant configuration, the switches are connected with two cables, a primary cable and a secondary cable. Therefore, enabling the L2MS filter prevents control packets from looping and causing congestion. In addition, in network configurations other than the redundant configuration, the L2MS filter is disabled . Set BPDU filter (*2) Only if the Dante network is configured as a redundant Dante primary/secondary configuration, the BPDU filter is enabled on the Dante secondary port. In a redundant configuration, the network switches are connected with two cables, a primary cable and a secondary cable. Therefore, enabling the BPDU filter prevents port blocking. In addition, in network configurations other than the redundant configuration, the BPDU filter is disabled . Set profile type This setting is used as an identifier to identify the profile type in the ProAV GUI.</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#ndiプロファイル">3.2. NDI profiles</div><div class="search_word">3.2. ndi profiles the following commands are collectively applied by ndi profiles. list of commands applied by ndi profiles object of setting function commands entire system enable flow control flowcontrol enable disable qos qos disable always forward linked local multicasts l2-unknown-mcast forward link-local enable lldp lldp run disable ptp ptp disable vlan interface set profile type proav profile-type ndi cancel shutdown no shutdown flood unknown multicasts l2-unknown-mcast flood enable igmp snooping ip igmp snooping enable set igmp snooping version ip igmp snooping version 2 enable igmp snooping fast-leave function ip igmp snooping fast-leave auto-assignment enable igmp query transmission function ip igmp snooping querier set igmp query transmission interval ip igmp snooping query-interval 125 disable igmp report-suppression function ip igmp snooping report-suppression disable enable igmp report forwarding function ip igmp snooping report-forward enable disable igmp packet ttl value checking function ip igmp snooping check ttl disable disable igmp packet ra checking function ip igmp snooping check ra disable disable igmp packet tos checking function ip igmp snooping check tos disable enable data transfer suppression function for multicast router ports ip igmp snooping mrouter-port data-suppression enable lan/sfp port enable flow control flowcontrol both set mru mru 1522 disable l2ms filter l2ms filter disable disable eee eee disable enable lldp transmission and reception lldp-agent set lldp enable txrx tlv-select basic-mgmt enable ptp ptp disable details on the settings are as follows: enable flow control by enabling flow control , when the bandwidth becomes congested, traffic transmission is temporarily stopped until the congestion clears, preventing packet loss. disable qos by disabling qos , packets will be forwarded without priority control. enable igmp snooping by enabling igmp snooping , multicast traffic is forwarded only to ports where multicast receivers exist, and unnecessary traffic is not forwarded. set the igmp snooping version to igmpv2 . in a network configuration using multiple switches, if the switches have different versions, a warning message will be displayed on the “multicast page” of the proav gui. when using an ndi network, set the version to igmpv2. by enabling the igmp snooping fast leave function , multicast traffic forwarding stops immediately when a multicast receiver stops receiving it. when a multicast receiver switches between audio and video, the multicast traffic before the switching can be prevented from causing noise. by enabling the auto-assignment option of the fast leave function , fast leave is not performed on ports connecting switches in a network configuration using multiple switches. this prevents immediate stop of multicast traffic forwarding when receivers who want to receive the multicast traffic still exist on the opposing switch. enable the igmp query transmission function (querier function) . when igmp snooping is used, a querier must exist on the same network. if there are multiple queriers on the same network, the querier with the smallest ip address becomes the representative querier, and the other queriers automatically stop transmitting queries. set the igmp query interval value to the default of 125 seconds . by disabling the igmp report suppression function , igmp reports are forwarded directly without being proxied in a network configuration using multiple switches. by enabling the igmp report suppression function , igmp reports are forwarded directly without being proxied in a network configuration using multiple switches. by disabling the igmp packet ttl value/ra/tos checking function , even if an invalid igmp packet is received, the information is appropriately corrected and the igmp packet is forwarded. by enabling the data transfer suppression function for multicast router ports , you can conserve the bandwidth between switches in a network configuration using multiple switches. normally, all multicast traffic is forwarded to the multicast router port regardless of existence of a multicast receiver. therefore, in a bidirectional transmission environment, unnecessary multicast traffic consumes the bandwidth between switches. by using this function, multicast traffic is forwarded only if a multicast receiver exists on the opposing switch, thereby conserving the bandwidth between switches. disable jumbo frames by setting the mru to 1522 bytes , jumbo frame forwarding is disabled. disable eee disabling the power saving function prevents the function from affecting data transfer performance. enable lldp enabling lldp transmission and reception enables the igmp snooping fast leave function and the igmp report forwarding function . this is because these two igmp functions operate by using lldp to determine whether the opposing device is a switch. set profile type this setting is used as an identifier to identify the profile type in the proav gui.</div><div class="display_word">3.2. NDI profiles The following commands are collectively applied by NDI profiles. List of commands applied by NDI profiles Object of setting Function Commands Entire system Enable flow control flowcontrol enable Disable QoS qos disable Always forward linked local multicasts l2-unknown-mcast forward link-local Enable LLDP lldp run Disable PTP ptp disable VLAN interface Set profile type proav profile-type ndi Cancel shutdown no shutdown Flood unknown multicasts l2-unknown-mcast flood Enable IGMP snooping ip igmp snooping enable Set IGMP snooping version ip igmp snooping version 2 Enable IGMP snooping fast-leave function ip igmp snooping fast-leave auto-assignment Enable IGMP query transmission function ip igmp snooping querier Set IGMP query transmission interval ip igmp snooping query-interval 125 Disable IGMP report-suppression function ip igmp snooping report-suppression disable Enable IGMP report forwarding function ip igmp snooping report-forward enable Disable IGMP packet TTL value checking function ip igmp snooping check ttl disable Disable IGMP packet RA checking function ip igmp snooping check ra disable Disable IGMP packet ToS checking function ip igmp snooping check tos disable Enable data transfer suppression function for multicast router ports ip igmp snooping mrouter-port data-suppression enable LAN/SFP port Enable flow control flowcontrol both Set MRU mru 1522 Disable L2MS filter l2ms filter disable Disable EEE eee disable Enable LLDP transmission and reception lldp-agent set lldp enable txrx tlv-select basic-mgmt Enable PTP ptp disable Details on the settings are as follows: Enable flow control By enabling flow control , when the bandwidth becomes congested, traffic transmission is temporarily stopped until the congestion clears, preventing packet loss. Disable QoS By disabling QoS , packets will be forwarded without priority control. Enable IGMP snooping By enabling IGMP snooping , multicast traffic is forwarded only to ports where multicast receivers exist, and unnecessary traffic is not forwarded. Set the IGMP snooping version to IGMPv2 . In a network configuration using multiple switches, if the switches have different versions, a warning message will be displayed on the “Multicast page” of the ProAV GUI. When using an NDI network, set the version to IGMPv2. By enabling the IGMP snooping fast leave function , multicast traffic forwarding stops immediately when a multicast receiver stops receiving it. When a multicast receiver switches between audio and video, the multicast traffic before the switching can be prevented from causing noise. By enabling the auto-assignment option of the fast leave function , fast leave is not performed on ports connecting switches in a network configuration using multiple switches. This prevents immediate stop of multicast traffic forwarding when receivers who want to receive the multicast traffic still exist on the opposing switch. Enable the IGMP query transmission function (querier function) . When IGMP snooping is used, a querier must exist on the same network. If there are multiple queriers on the same network, the querier with the smallest IP address becomes the representative querier, and the other queriers automatically stop transmitting queries. Set the IGMP query interval value to the default of 125 seconds . By disabling the IGMP report suppression function , IGMP reports are forwarded directly without being proxied in a network configuration using multiple switches. By enabling the IGMP report suppression function , IGMP reports are forwarded directly without being proxied in a network configuration using multiple switches. By disabling the IGMP packet TTL value/RA/ToS checking function , even if an invalid IGMP packet is received, the information is appropriately corrected and the IGMP packet is forwarded. By enabling the data transfer suppression function for multicast router ports , you can conserve the bandwidth between switches in a network configuration using multiple switches. Normally, all multicast traffic is forwarded to the multicast router port regardless of existence of a multicast receiver. Therefore, in a bidirectional transmission environment, unnecessary multicast traffic consumes the bandwidth between switches. By using this function, multicast traffic is forwarded only if a multicast receiver exists on the opposing switch, thereby conserving the bandwidth between switches. Disable jumbo frames By setting the MRU to 1522 bytes , jumbo frame forwarding is disabled. Disable EEE Disabling the power saving function prevents the function from affecting data transfer performance. Enable LLDP Enabling LLDP transmission and reception enables the IGMP snooping fast leave function and the IGMP report forwarding function . This is because these two IGMP functions operate by using LLDP to determine whether the opposing device is a switch. Set profile type This setting is used as an identifier to identify the profile type in the ProAV GUI.</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#複数プロファイル併用時の設定">3.3. Settings for using multiple profiles</div><div class="search_word">3.3. settings for using multiple profiles on the “custom” page of the proav profile, you can set any profile for each port. depending on the profile combination, conflicts in settings may occur, resulting in differences in settings compared to the case where a single profile is used.</div><div class="display_word">3.3. Settings for using multiple profiles On the “Custom” page of the ProAV profile, you can set any profile for each port. Depending on the profile combination, conflicts in settings may occur, resulting in differences in settings compared to the case where a single profile is used.</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#プロファイル併用時">3.3.1. When multiple profiles are used</div><div class="search_word">3.3.1. when multiple profiles are used list of commands that are applied when multiple profiles are used object of setting function dante profiles ndi profiles entire system disable flow control flowcontrol disable enable qos qos enable optimize transmission queue by dscp value qos dscp-queue 8 2 qos dscp-queue 26 3 qos dscp-queue 34 4 qos dscp-queue 46 5 qos dscp-queue 48 5 qos dscp-queue 56 7 qos dscp-queue [not indicated above] 0 no qos wrr-weight [0 to 7] always forward linked local multicasts l2-unknown-mcast forward link-local enable lldp lldp run enable ptp ptp enable vlan interface set profile type proav profile-type dante-primary/dante-secondary + proav profile-type ndi cancel shutdown no shutdown + no shutdown flood unknown multicasts l2-unknown-mcast flood + l2-unknown-mcast flood enable igmp snooping ip igmp snooping enable + ip igmp snooping enable set igmp snooping version ip igmp snooping version 3 + ip igmp snooping version 2 enable igmp snooping fast-leave function ip igmp snooping fast-leave auto-assignment + ip igmp snooping fast-leave auto-assignment enable igmp query transmission function ip igmp snooping querier + ip igmp snooping querier set igmp query transmission interval ip igmp snooping query-interval 30 + ip igmp snooping query-interval 125 disable igmp report-suppression function ip igmp snooping report-suppression disable + ip igmp snooping report-suppression disable enable igmp report forwarding function ip igmp snooping report-forward enable + ip igmp snooping report-forward enable disable igmp packet ttl value checking function ip igmp snooping check ttl disable + ip igmp snooping check ttl disable disable igmp packet ra checking function ip igmp snooping check ra disable + ip igmp snooping check ra disable disable igmp packet tos checking function ip igmp snooping check tos disable + ip igmp snooping check tos disable enable data transfer suppression function for multicast router ports ip igmp snooping mrouter-port data-suppression enable ip igmp snooping mrouter-port data-suppression enable always forward ptp packets l2-mcast flood 224.0.1.129 - l2-mcast flood 224.0.1.130 l2-mcast flood 224.0.1.131 l2-mcast flood 224.0.1.132 l2-mcast flood 239.254.3.3 lan/sfp port set flow control flowcontrol disable flowcontrol both set mru mru 1522 + mru 1522 set qos trust mode qos trust dscp + qos trust port-priority qos port-priority-queue 2 set l2ms filter l2ms filter disable + l2ms filter disable disable eee eee disable + eee disable enable lldp transmission and reception lldp-agent set lldp enable txrx tlv-select basic-mgmt + lldp-agent set lldp enable txrx tlv-select basic-mgmt differences between using multiple profiles and using a single profile are as follows: flow control to enable qos, flow control is disabled for the entire system. qos qos is enabled for the entire system. the transmission queues are optimized based on the dscp values across the entire system. for ports with a dante profile applied, by setting the qos trust mode to dscp , the priority control is performed by referring to the dscp values. for ports with an ndi profile applied, by setting the qos trust mode to port priority and fixing the transmission queue to 2 (default) , the packet forwarding priority control is not performed.</div><div class="display_word">3.3.1. When multiple profiles are used List of commands that are applied when multiple profiles are used Object of setting Function Dante profiles NDI profiles Entire system Disable flow control flowcontrol disable Enable QoS qos enable Optimize transmission queue by DSCP value qos dscp-queue 8 2 qos dscp-queue 26 3 qos dscp-queue 34 4 qos dscp-queue 46 5 qos dscp-queue 48 5 qos dscp-queue 56 7 qos dscp-queue [not indicated above] 0 no qos wrr-weight [0 to 7] Always forward linked local multicasts l2-unknown-mcast forward link-local Enable LLDP lldp run Enable PTP ptp enable VLAN interface Set profile type proav profile-type dante-primary/dante-secondary + proav profile-type ndi Cancel shutdown no shutdown + no shutdown Flood unknown multicasts l2-unknown-mcast flood + l2-unknown-mcast flood Enable IGMP snooping ip igmp snooping enable + ip igmp snooping enable Set IGMP snooping version ip igmp snooping version 3 + ip igmp snooping version 2 Enable IGMP snooping fast-leave function ip igmp snooping fast-leave auto-assignment + ip igmp snooping fast-leave auto-assignment Enable IGMP query transmission function ip igmp snooping querier + ip igmp snooping querier Set IGMP query transmission interval ip igmp snooping query-interval 30 + ip igmp snooping query-interval 125 Disable IGMP report-suppression function ip igmp snooping report-suppression disable + ip igmp snooping report-suppression disable Enable IGMP report forwarding function ip igmp snooping report-forward enable + ip igmp snooping report-forward enable Disable IGMP packet TTL value checking function ip igmp snooping check ttl disable + ip igmp snooping check ttl disable Disable IGMP packet RA checking function ip igmp snooping check ra disable + ip igmp snooping check ra disable Disable IGMP packet ToS checking function ip igmp snooping check tos disable + ip igmp snooping check tos disable Enable data transfer suppression function for multicast router ports ip igmp snooping mrouter-port data-suppression enable ip igmp snooping mrouter-port data-suppression enable Always forward PTP packets l2-mcast flood 224.0.1.129 - l2-mcast flood 224.0.1.130 l2-mcast flood 224.0.1.131 l2-mcast flood 224.0.1.132 l2-mcast flood 239.254.3.3 LAN/SFP port Set flow control flowcontrol disable flowcontrol both Set MRU mru 1522 + mru 1522 Set QoS trust mode qos trust dscp + qos trust port-priority qos port-priority-queue 2 Set L2MS filter l2ms filter disable + l2ms filter disable Disable EEE eee disable + eee disable Enable LLDP transmission and reception lldp-agent set lldp enable txrx tlv-select basic-mgmt + lldp-agent set lldp enable txrx tlv-select basic-mgmt Differences between using multiple profiles and using a single profile are as follows: Flow control To enable QoS, flow control is disabled for the entire system. QoS QoS is enabled for the entire system. The transmission queues are optimized based on the DSCP values across the entire system. For ports with a Dante profile applied, by setting the QoS trust mode to DSCP , the priority control is performed by referring to the DSCP values. For ports with an NDI profile applied, by setting the QoS trust mode to port priority and fixing the transmission queue to 2 (default) , the packet forwarding priority control is not performed.</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#キッティングとトラブルシューティング">4. Kitting and Troubleshooting</div><div class="search_word">4. kitting and troubleshooting by utilizing the “yamaha lan monitor”, an integrated management tool for yamaha network devices, you can easily perform kitting (initial setup) and troubleshooting. yamaha lan monitor can be downloaded for free. for details on how to install and use yamaha lan monitor, refer to the user guide.</div><div class="display_word">4. Kitting and Troubleshooting By utilizing the “Yamaha LAN Monitor”, an integrated management tool for Yamaha network devices, you can easily perform kitting (initial setup) and troubleshooting. Yamaha LAN Monitor can be downloaded for free. For details on how to install and use Yamaha LAN Monitor, refer to the user guide.</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#キッティング-ipアドレスを意識せずに初期設定する">4.1. [Kitting] Initial setup without having to think about IP addresses</div><div class="search_word">4.1. [kitting] initial setup without having to think about ip addresses normally, when using two or more switches in a network, you must appropriately set the ip address of each switch to avoid ip address duplication. however, if you have a closed avoip network that does not need to be connected to an external network, you can use the auto ip function of the switches to automatically assign link local addresses. by combining a yamaha switch in the factory default settings with yamaha lan monitor, you can easily apply the proav profile without having to think about setting ip addresses. as a preliminary step, install yamaha lan monitor on your computer and set the ip address of the network adapter used by the computer to “acquire automatically”. this procedure allows the computer to operate with a link local address. (*if a dhcp server exists, the ip address can be acquired via dhcp. however, since a closed avoip network is assumed this time, the explanation of dhcp is omitted.) connect multiple switches in the factory default settings, connect the computer to a port on any switch, and start yamaha lan monitor. when you start it, the following screen will appear. make sure that the correct network adapter of the computer is selected in the upper left corner of the screen and that the ip address of the computer is a link local address starting with “169.254. . ” you can check the ip address by clicking the switch icon on yamaha lan monitor. the default ip address of the yamaha switch is “192.168.100.240/24”. *when the switch is placed under the management of yamaha lan monitor in its factory default settings (state without any changes to its settings), the address will automatically switch to a link local address. * if the ip address of the switch starts with “169.254. . ”, the switch is operating with a link local address. if the address remains as “192.168.100.240”, wait a while until it switches to a link local address, and then refresh the display. *note that, if the yamaha switch settings have already been changed from the default settings, the switch will not automatically switch to a link local address. *if the address does not switch to the link local address after a while, reset the switch to its default settings. with this product, you can physically initialize the settings by turning on the power while holding down the led mode button on the front of the chassis, and then releasing the button when all port leds turn orange. once you have confirmed that the ip address of the switch has changed to a link local address, click the “web gui” button. the computer browser automatically opens and displays the web gui of the switch. on the web gui login screen, enter the username “admin” and password “admin”. after selecting the language, you will be asked to change your password. set a password of your choice. once you have logged in to the web gui, click the “proav settings” button in the global menu at the top of the screen. the “proav profile” page will appear as shown below. finally, apply the proav profile on the settings page. the proav profile setup is now completed.</div><div class="display_word">4.1. [Kitting] Initial setup without having to think about IP addresses Normally, when using two or more switches in a network, you must appropriately set the IP address of each switch to avoid IP address duplication. However, if you have a closed AVoIP network that does not need to be connected to an external network, you can use the Auto IP function of the switches to automatically assign link local addresses. By combining a Yamaha switch in the factory default settings with Yamaha LAN Monitor, you can easily apply the ProAV profile without having to think about setting IP addresses. As a preliminary step, install Yamaha LAN Monitor on your computer and set the IP address of the network adapter used by the computer to “Acquire automatically”. This procedure allows the computer to operate with a link local address. (*If a DHCP server exists, the IP address can be acquired via DHCP. However, since a closed AVoIP network is assumed this time, the explanation of DHCP is omitted.) Connect multiple switches in the factory default settings, connect the computer to a port on any switch, and start Yamaha LAN Monitor. When you start it, the following screen will appear. Make sure that the correct network adapter of the computer is selected in the upper left corner of the screen and that the IP address of the computer is a link local address starting with “169.254. . ” You can check the IP address by clicking the switch icon on Yamaha LAN Monitor. The default IP address of the Yamaha switch is “192.168.100.240/24”. *When the switch is placed under the management of Yamaha LAN Monitor in its factory default settings (state without any changes to its settings), the address will automatically switch to a link local address. * If the IP address of the switch starts with “169.254. . ”, the switch is operating with a link local address. If the address remains as “192.168.100.240”, wait a while until it switches to a link local address, and then refresh the display. *Note that, if the Yamaha switch settings have already been changed from the default settings, the switch will not automatically switch to a link local address. *If the address does not switch to the link local address after a while, reset the switch to its default settings. With this product, you can physically initialize the settings by turning on the power while holding down the LED MODE button on the front of the chassis, and then releasing the button when all port LEDs turn orange. Once you have confirmed that the IP address of the switch has changed to a link local address, click the “Web GUI” button. The computer browser automatically opens and displays the web GUI of the switch. On the web GUI login screen, enter the username “admin” and password “admin”. After selecting the language, you will be asked to change your password. Set a password of your choice. Once you have logged in to the web GUI, click the “ProAV Settings” button in the global menu at the top of the screen. The “ProAV Profile” page will appear as shown below. Finally, apply the ProAV profile on the settings page. The ProAV profile setup is now completed.</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#キッティング-複数のヤマハスイッチに同一設定を一括適用する">4.2. [Kitting] Applying the same settings to multiple Yamaha switches at once</div><div class="search_word">4.2. [kitting] applying the same settings to multiple yamaha switches at once yamaha lan monitor can distribute configuration files (config files) to multiple yamaha switches at once. if you are using link local addresses as the ip addresses and want to apply the same settings to all switches, you can efficiently configure the settings for multiple switches. note that, if the switch is operated with a fixed ip address, you will need to reconfigure the ip address setting to prevent ip address duplication. follow the steps in 4.1 to apply the proav profile to one switch. click on the “list” tab at the top of the screen. a list of detected yamaha switches will be displayed. click the “config import/export” tab at the top of the screen. additionally, check the switch to which the proav profile has already been applied, and click the “config export” button. the “config export” dialog will appear. select the directory in which you want to save the config file and click the “execute” button. the dialog will display the progress and result of the export. click the “ok” button when the export is completed. additionally, check the switch to which you want to apply the proav profile, and click the “config import” button. if you want to apply the profile to multiple switches, check multiple check boxes. the “config import” dialog will appear. select the config file saved in the previous step as an import file, and click the “execute” button. you can specify a config file for each selected switch, or you can specify the same config file for all selected switches. in an environment where different models of switches are used, specify the appropriate config file for each model. the dialog will display the progress and result of the import. click the “ok” button when the import is completed. the switch that receives config will automatically reboot and the new settings will be applied after the bootup. you can also update the firmware on multiple yamaha switches at once by following the similar procedure using the “firmware update” button. in this way, yamaha lan monitor can be used as a kitting tool for multi-device environments, so please make use of it.</div><div class="display_word">4.2. [Kitting] Applying the same settings to multiple Yamaha switches at once Yamaha LAN Monitor can distribute configuration files (CONFIG files) to multiple Yamaha switches at once. If you are using link local addresses as the IP addresses and want to apply the same settings to all switches, you can efficiently configure the settings for multiple switches. Note that, if the switch is operated with a fixed IP address, you will need to reconfigure the IP address setting to prevent IP address duplication. Follow the steps in 4.1 to apply the ProAV profile to one switch. Click on the “List” tab at the top of the screen. A list of detected Yamaha switches will be displayed. Click the “Config Import/Export” tab at the top of the screen. Additionally, check the switch to which the ProAV profile has already been applied, and click the “Config export” button. The “Config export” dialog will appear. Select the directory in which you want to save the CONFIG file and click the “Execute” button. The dialog will display the progress and result of the export. Click the “OK” button when the export is completed. Additionally, check the switch to which you want to apply the ProAV profile, and click the “Config import” button. If you want to apply the profile to multiple switches, check multiple check boxes. The “Config import” dialog will appear. Select the CONFIG file saved in the previous step as an import file, and click the “Execute” button. You can specify a CONFIG file for each selected switch, or you can specify the same CONFIG file for all selected switches. In an environment where different models of switches are used, specify the appropriate CONFIG file for each model. The dialog will display the progress and result of the import. Click the “OK” button when the import is completed. The switch that receives CONFIG will automatically reboot and the new settings will be applied after the bootup. You can also update the firmware on multiple Yamaha switches at once by following the similar procedure using the “Firmware Update” button. In this way, Yamaha LAN Monitor can be used as a kitting tool for multi-device environments, so please make use of it.</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#トラブルシューティング-ネットワークの状態を確認する">4.3. [Troubleshooting] Checking the network status</div><div class="search_word">4.3. [troubleshooting] checking the network status by using yamaha lan monitor, you can visualize the connection configuration of the entire network, and also check traffic bandwidth usage and poe power supply status. click the switch icon. “port status” is selected by default, which displays real-time link status on the front panel at the top of the screen. the tree view at the bottom left of the screen allows you to check the current network connection configuration, and the connected device view at the bottom right of the screen allows you to see which devices are connected to which ports. to check the traffic bandwidth usage, click the “bandwidth usage (%)” button. the bandwidth utilization of each port is displayed as the percentage against the link speed. when the bandwidth utilization is close to its upper limit, the port icon appears yellow, orange, or red. to check the poe power supply status, click “poe power supply status (class)”. the power supply class is displayed for ports that are supplying power, and the device details view in the upper left corner of the screen shows the total power supply and the power supply of each port.</div><div class="display_word">4.3. [Troubleshooting] Checking the network status By using Yamaha LAN Monitor, you can visualize the connection configuration of the entire network, and also check traffic bandwidth usage and PoE power supply status. Click the switch icon. “Port Status” is selected by default, which displays real-time link status on the front panel at the top of the screen. The tree view at the bottom left of the screen allows you to check the current network connection configuration, and the connected device view at the bottom right of the screen allows you to see which devices are connected to which ports. To check the traffic bandwidth usage, click the “Bandwidth Usage (%)” button. The bandwidth utilization of each port is displayed as the percentage against the link speed. When the bandwidth utilization is close to its upper limit, the port icon appears yellow, orange, or red. To check the PoE power supply status, click “PoE Power Supply Status (Class)”. The power supply class is displayed for ports that are supplying power, and the device details view in the upper left corner of the screen shows the total power supply and the power supply of each port.</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#トラブルシューティング-dante機器の状態を確認する">4.4. [Troubleshooting] Checking the Dante device status</div><div class="search_word">4.4. [troubleshooting] checking the dante device status yamaha lan monitor allows you to check the status of dante devices and open dante controller with one click if it is installed on your computer. note that, in order to view dante devices, dante control and monitoring and dante discovery must be installed when yamaha lan monitor is installed. with a dante device connected to the yamaha switch, click on the dante device icon. you can monitor the status of the primary and secondary ports, the number of transmission and reception flows, etc. you can also check information such as whether the operating mode of the dante device is “redundant mode” or “daisy chain mode”. dante controller can be started by clicking the “dante controller” button in the top right or center of the screen. (dante controller must be installed beforehand.) you can seamlessly switch between yamaha lan monitor and dante controller on a single computer, making troubleshooting more efficient.</div><div class="display_word">4.4. [Troubleshooting] Checking the Dante device status Yamaha LAN Monitor allows you to check the status of Dante devices and open Dante Controller with one click if it is installed on your computer. Note that, in order to view Dante devices, Dante Control and Monitoring and Dante Discovery must be installed when Yamaha LAN Monitor is installed. With a Dante device connected to the Yamaha switch, click on the Dante device icon. You can monitor the status of the primary and secondary ports, the number of transmission and reception flows, etc. You can also check information such as whether the operating mode of the Dante device is “redundant mode” or “daisy chain mode”. Dante Controller can be started by clicking the “Dante Controller” button in the top right or center of the screen. (Dante Controller must be installed beforehand.) You can seamlessly switch between Yamaha LAN Monitor and Dante Controller on a single computer, making troubleshooting more efficient.</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#注意事項">5. Points of Caution</div><div class="search_word">5. points of caution the settings configured collectively in proav settings are intended for use when this product is used as a switch dedicated to the avoip network. when building a complex network, such as mixing an existing in-house network with an avoip network, use the gui advanced settings pages and commands to appropriately configure the settings. when applying the proav profile, ports that belong to a logical interface must be detached from the logical interface. if necessary, first detach the ports from the logical interface, assign the profile, and then re-attach them to the logical interface. the proav profile assumes an avoip network consisting only of yamaha network switches. note that, when the igmp snooping function is used in a multi-vendor environment, determination of the opposing device via lldp may not work. if the stack function is enabled on a model that supports the stack function, the proav settings cannot be used.</div><div class="display_word">5. Points of Caution The settings configured collectively in ProAV settings are intended for use when this product is used as a switch dedicated to the AVoIP network. When building a complex network, such as mixing an existing in-house network with an AVoIP network, use the GUI advanced settings pages and commands to appropriately configure the settings. When applying the ProAV profile, ports that belong to a logical interface must be detached from the logical interface. If necessary, first detach the ports from the logical interface, assign the profile, and then re-attach them to the logical interface. The ProAV profile assumes an AVoIP network consisting only of Yamaha network switches. Note that, when the IGMP snooping function is used in a multi-vendor environment, determination of the opposing device via LLDP may not work. If the stack function is enabled on a model that supports the stack function, the ProAV settings cannot be used.</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#関連文書">6. Related Documentation</div><div class="search_word">6. related documentation none.</div><div class="display_word">6. Related Documentation None.</div></div><div id="oam_oam_proav"><div class="search_title" docfname="oam_oam_proav" doctitle="ProAV" link="#商標名称について">7. Trademarks and Trade Names</div><div class="search_word">7. trademarks and trade names dante™ is a registered trademark of audinate pty ltd. ndi® is a registered trademark of vizrt ndi ab.</div><div class="display_word">7. Trademarks and Trade Names Dante™ is a registered trademark of Audinate Pty Ltd. NDI® is a registered trademark of Vizrt NDI AB.</div></div><div id="oam_oam_remote_control"><div class="search_title" docfname="oam_oam_remote_control" doctitle="Remote" link="#リモートアクセス制御">Remote Access Control</div><div class="search_word">remote access control</div><div class="display_word">Remote Access Control</div></div><div id="oam_oam_remote_control"><div class="search_title" docfname="oam_oam_remote_control" doctitle="Remote" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product lets you restrict access to the following applications that implement network services. telnet server ssh server http server / https server tftp server snmp server</div><div class="display_word">1. Function Overview This product lets you restrict access to the following applications that implement network services. TELNET server SSH server HTTP server / HTTPS server TFTP server SNMP server</div></div><div id="oam_oam_remote_control"><div class="search_title" docfname="oam_oam_remote_control" doctitle="Remote" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used none</div><div class="display_word">2. Definition of Terms Used None</div></div><div id="oam_oam_remote_control"><div class="search_title" docfname="oam_oam_remote_control" doctitle="Remote" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details the following four functions are provided to limit access to network services. control whether to leave the service in question running in the background on the system (start/stop control) change reception port number limit access destinations for services currently running limit the source ip addresses that can access services currently running the following functions that correspond to each network service are shown in the table below. network service access control network service start/stop control change reception port number access destination restriction access source restriction telnet server yes yes yes yes ssh server yes yes yes yes http server https server yes yes yes yes tftp server yes yes yes no snmp server × (always booted) × (always 161) no yes multiple instances of a network service cannot be started. if the start control is applied to the same service that is currently running, the service will restart. consequently, any connected sessions will be disconnected . limiting access destinations for network services is done for the vlan interface . sources permitted to access network services can be restricted by specifying access source ip address and access permit/deny settings. the default settings for the network services are shown in the table below. network service start/stop status reception port number access destination restriction access source restriction telnet server run 23 only default maintenance vlan (vlan #1) permitted allow all ssh server stop 22 only default maintenance vlan (vlan #1) permitted allow all http server run 80 only default maintenance vlan (vlan #1) permitted allow all https server stop 443 tftp server stop 69 only default maintenance vlan (vlan #1) permitted allow all snmp server run 161 allow all allow all</div><div class="display_word">3. Function Details The following four functions are provided to limit access to network services. Control whether to leave the service in question running in the background on the system (start/stop control) Change reception port number Limit access destinations for services currently running Limit the source IP addresses that can access services currently running The following functions that correspond to each network service are shown in the table below. Network service access control Network service Start/stop control Change reception port number Access destination restriction Access source restriction TELNET server Yes Yes Yes Yes SSH server Yes Yes Yes Yes HTTP server HTTPS server Yes Yes Yes Yes TFTP server Yes Yes Yes No SNMP server × (Always booted) × (Always 161) No Yes Multiple instances of a network service cannot be started. If the start control is applied to the same service that is currently running, the service will restart. Consequently, any connected sessions will be disconnected . Limiting access destinations for network services is done for the VLAN interface . Sources permitted to access network services can be restricted by specifying access source IP address and access permit/deny settings. The default settings for the network services are shown in the table below. Network service Start/stop status Reception port number Access destination restriction Access source restriction TELNET server run 23 Only default maintenance VLAN (VLAN #1) permitted Allow all SSH server stop 22 Only default maintenance VLAN (VLAN #1) permitted Allow all HTTP server run 80 Only default maintenance VLAN (VLAN #1) permitted Allow all HTTPS server stop 443 TFTP server stop 69 Only default maintenance VLAN (VLAN #1) permitted Allow all SNMP server run 161 Allow all Allow all</div></div><div id="oam_oam_remote_control"><div class="search_title" docfname="oam_oam_remote_control" doctitle="Remote" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details, refer to the command reference. network service operations operating commands common maintenance vlan management interface telnet server start/stop telnet-server change reception port number telnet-server enable (use argument to specify port number) access control telnet-server interface ip address access control telnet-server access show settings show telnet-server ssh server start/stop ssh-server change reception port number ssh-server enable (use argument to specify port number) access control ssh-server interface ip address access control ssh-server access check whether client is alive ssh-server client alive show settings show ssh-server generate host key ssh-server host key generate clear host key clear ssh-server host key show public key show ssh-server host key http server start/stop http server http-server change http server’s reception port number http-server enable (use argument to specify port number) start/stop https server http-server secure change https server’s reception port number http-server secure enable (use argument to specify port number) access control http-server interface ip address access control http-server access show settings show http-server tftp server start/stop tftp-server access control tftp-server interface snmp server access control by ip address and community name snmp-server access</div><div class="display_word">4. Related Commands Related commands are indicated below. For details, refer to the Command Reference. Network service Operations Operating commands Common Maintenance VLAN management interface TELNET server Start/stop telnet-server Change reception port number telnet-server enable (use argument to specify port number) Access control telnet-server interface IP address access control telnet-server access Show settings show telnet-server SSH server Start/stop ssh-server Change reception port number ssh-server enable (use argument to specify port number) Access control ssh-server interface IP address access control ssh-server access Check whether client is alive ssh-server client alive Show settings show ssh-server Generate host key ssh-server host key generate Clear host key clear ssh-server host key Show public key show ssh-server host key HTTP server Start/stop HTTP server http-server Change HTTP server’s reception port number http-server enable (use argument to specify port number) Start/stop HTTPS server http-server secure Change HTTPS server’s reception port number http-server secure enable (use argument to specify port number) Access control http-server interface IP address access control http-server access Show settings show http-server TFTP server Start/stop tftp-server Access control tftp-server interface SNMP server Access control by IP address and community name snmp-server access</div></div><div id="oam_oam_remote_control"><div class="search_title" docfname="oam_oam_remote_control" doctitle="Remote" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="oam_oam_remote_control"><div class="search_title" docfname="oam_oam_remote_control" doctitle="Remote" link="#telnetサーバーに対するアクセス制御">5.1. TELNET server access control</div><div class="search_word">5.1. telnet server access control this example restricts access to the telnet server. change the telnet server’s reception port to 1024. change the maintenance vlan to vlan #1000 and allow access. access from other than the maintenance vlan is denied. connection to the telnet server is allowed only by clients from 192.168.100.1. if you specify telnet-server access, access from ip addresses that do not meet the conditions is denied. yamaha(config)#telnet-server enable 1024 (1) yamaha(config)#management interface vlan1000 (2) yamaha(config)#telnet-server access permit 192.168.100.1 (3) yamaha(config)#endyamaha#show telnet-server (4) service:enableport:1024management interface(vlan):1000interface(vlan):noneaccess:    permit 192.168.100.1 1 change the reception port to 1024 and reboot the telnet server 2 allow access from vlan #1000 as the maintenance vlan 3 allow access only from 192.168.100.1 4 check the settings</div><div class="display_word">5.1. TELNET server access control This example restricts access to the TELNET server. Change the TELNET server’s reception port to 1024. Change the maintenance VLAN to VLAN #1000 and allow access. Access from other than the maintenance VLAN is denied. Connection to the TELNET server is allowed only by clients from 192.168.100.1. If you specify telnet-server access, access from IP addresses that do not meet the conditions is denied. Yamaha(config)#telnet-server enable 1024 (1) Yamaha(config)#management interface vlan1000 (2) Yamaha(config)#telnet-server access permit 192.168.100.1 (3) Yamaha(config)#endYamaha#show telnet-server (4) Service:EnablePort:1024Management interface(vlan):1000Interface(vlan):NoneAccess:    permit 192.168.100.1 1 Change the reception port to 1024 and reboot the TELNET server 2 Allow access from VLAN #1000 as the maintenance VLAN 3 Allow access only from 192.168.100.1 4 Check the settings</div></div><div id="oam_oam_remote_control"><div class="search_title" docfname="oam_oam_remote_control" doctitle="Remote" link="#sshサーバーに対するアクセス制御">5.2. SSH server access control</div><div class="search_word">5.2. ssh server access control this example restricts access to the ssh server. generate the ssh server host key. register a user name and password. login from an ssh client is possible only for a registered user and password. change the ssh server’s reception port to 1024. change the maintenance vlan to vlan #1000 and permit access to vlan #2 . consequently, access is only permitted from vlan #1000 and from vlan #2 on the maintenance vlan. if you specify ssh-server access, access from ip addresses that do not meet the conditions is denied. yamaha#ssh-server host key generate (1) yamaha#show ssh-server host key (2) ssh-dss (omitted)ssh-rsa (omitted)yamaha#yamaha#configure terminalenter configuration commands, one per line.  end with cntl/z.yamaha(config)#username user1 password pw1 (3) yamaha(config)#ssh-server enable 1024 (4) yamaha(config)#management interface vlan1000 (5) yamaha(config)#ssh-server interface vlan2 (6) yamaha(config)#endyamaha#show ssh-serverr (7) service:enableport:1024hostkey:generatedclient alive :disablemanagement interface(vlan):1000interface(vlan):2access:noneyamaha# 1 create a host key 2 check contents of the key 3 register a username and password. 4 change the reception port to 1024 and reboot the ssh server 5 allow access from #1000 as the maintenance vlan 6 allow access from vlan #2 7 check the settings</div><div class="display_word">5.2. SSH server access control This example restricts access to the SSH server. Generate the SSH server host key. Register a user name and password. Login from an SSH client is possible only for a registered user and password. Change the SSH server’s reception port to 1024. Change the maintenance VLAN to VLAN #1000 and permit access to VLAN #2 . Consequently, access is only permitted from VLAN #1000 and from VLAN #2 on the maintenance VLAN. If you specify ssh-server access, access from IP addresses that do not meet the conditions is denied. Yamaha#ssh-server host key generate (1) Yamaha#show ssh-server host key (2) ssh-dss (Omitted)ssh-rsa (Omitted)Yamaha#Yamaha#configure terminalEnter configuration commands, one per line.  End with CNTL/Z.Yamaha(config)#username user1 password pw1 (3) Yamaha(config)#ssh-server enable 1024 (4) Yamaha(config)#management interface vlan1000 (5) Yamaha(config)#ssh-server interface vlan2 (6) Yamaha(config)#endYamaha#show ssh-serverr (7) Service:EnablePort:1024Hostkey:GeneratedClient alive :DisableManagement interface(vlan):1000Interface(vlan):2Access:NoneYamaha# 1 Create a host key 2 Check contents of the key 3 Register a username and password. 4 Change the reception port to 1024 and reboot the SSH server 5 Allow access from #1000 as the maintenance VLAN 6 Allow access from VLAN #2 7 Check the settings</div></div><div id="oam_oam_remote_control"><div class="search_title" docfname="oam_oam_remote_control" doctitle="Remote" link="#httpサーバーに対するアクセス制限">5.3. HTTP server access restrictions</div><div class="search_word">5.3. http server access restrictions this example restricts access to the http server. change the http server reception port to 8000 and permit access from vlan #2 . that permits access only from the default maintenance vlans vlan #1 and vlan #2 . connection to the http server is allowed only by clients from 192.168.100.1. if you specify http-server access, access from ip addresses that do not meet the conditions is denied. yamaha(config)#http-server enable 8000 (1) yamaha(config)#http-server interface vlan2 (2) yamaha(config)#http-server access permit 192.168.100.1 (3) yamaha(config)#endyamaha#show http-server (4) http :enable(8000)https:disablemanagement interface(vlan):1interface(vlan):2access:    permit 192.168.100.1 1 change the reception port to 8000 and reboot the http server 2 allow access from vlan #2 3 allow access only from 192.168.100.1 4 check the settings</div><div class="display_word">5.3. HTTP server access restrictions This example restricts access to the HTTP server. Change the HTTP server reception port to 8000 and permit access from VLAN #2 . That permits access only from the default maintenance VLANs VLAN #1 and VLAN #2 . Connection to the HTTP server is allowed only by clients from 192.168.100.1. If you specify http-server access, access from IP addresses that do not meet the conditions is denied. Yamaha(config)#http-server enable 8000 (1) Yamaha(config)#http-server interface vlan2 (2) Yamaha(config)#http-server access permit 192.168.100.1 (3) Yamaha(config)#endYamaha#show http-server (4) HTTP :Enable(8000)HTTPS:DisableManagement interface(vlan):1Interface(vlan):2Access:    permit 192.168.100.1 1 Change the reception port to 8000 and reboot the HTTP server 2 Allow access from VLAN #2 3 Allow access only from 192.168.100.1 4 Check the settings</div></div><div id="oam_oam_remote_control"><div class="search_title" docfname="oam_oam_remote_control" doctitle="Remote" link="#tftpサーバーに対するアクセス制限">5.4. TFTP server access restrictions</div><div class="search_word">5.4. tftp server access restrictions this example restricts access to the tftp server. change the tftp server reception port to 2048 and permit access from vlan #10 . allow access only from the default maintenance vlans vlan #1 and vlan #10 . yamaha(config)#tftp-server enable 2048 (1) yamaha(config)#tftp-server interface vlan10 (2) 1 change the reception port to 2048 and reboot the tftp server 2 allow access from vlan #10</div><div class="display_word">5.4. TFTP server access restrictions This example restricts access to the TFTP server. Change the TFTP server reception port to 2048 and permit access from VLAN #10 . Allow access only from the default maintenance VLANs VLAN #1 and VLAN #10 . Yamaha(config)#tftp-server enable 2048 (1) Yamaha(config)#tftp-server interface vlan10 (2) 1 Change the reception port to 2048 and reboot the TFTP server 2 Allow access from VLAN #10</div></div><div id="oam_oam_remote_control"><div class="search_title" docfname="oam_oam_remote_control" doctitle="Remote" link="#snmpサーバーに対するアクセス制限">5.5. SNMP server access restrictions</div><div class="search_word">5.5. snmp server access restrictions this restricts access to the snmp server. access to “public” communities is restricted to clients from 192.168.100.0/24. in addition, access to “private” communities is restricted to clients from 192.168.100.1. yamaha(config)#snmp-server access permit 192.168.100.0/24 community public (1) yamaha(config)#snmp-server access permit 192.168.100.1 community private (2) 1 the community name “public” allows access only from 192.168.100.0/24 2 the community name “private” allows access only from 192.168.100.1</div><div class="display_word">5.5. SNMP server access restrictions This restricts access to the SNMP server. Access to “public” communities is restricted to clients from 192.168.100.0/24. In addition, access to “private” communities is restricted to clients from 192.168.100.1. Yamaha(config)#snmp-server access permit 192.168.100.0/24 community public (1) Yamaha(config)#snmp-server access permit 192.168.100.1 community private (2) 1 The community name “public” allows access only from 192.168.100.0/24 2 The community name “private” allows access only from 192.168.100.1</div></div><div id="oam_oam_remote_control"><div class="search_title" docfname="oam_oam_remote_control" doctitle="Remote" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution if the password (admin) for the default administrative user admin is left unchanged, then the following restrictions are applied. network switches cannot be accessed by telnet, ssh, http, or https from a network segment other than the maintenance vlan. the following restrictions apply if a tftp server is accessed from a tftp client. access is denied if the privileged password (administrative password) is still set to the default setting. privileged passwords (administrative passwords) must be changed in advance. if the primary and secondary addresses for a vlan being accessed are the same segment, then the ipv4 secondary address cannot be accessed. if accessing the vlan with an ipv6 address, then only the ipv6 address specified last can be accessed. because the internal address is reset if the network switch is started, that means only the bottom ipv6 address listed in the order they were configured can be accessed. only the ip address of the vlan with the closest routing to the tftp client can be accessed. for example, a tftp client located on vlan 1 cannot access vlan 2 ip addresses for the network switch.</div><div class="display_word">6. Points of Caution If the password (admin) for the default administrative user admin is left unchanged, then the following restrictions are applied. Network switches cannot be accessed by TELNET, SSH, HTTP, or HTTPS from a network segment other than the maintenance VLAN. The following restrictions apply if a TFTP server is accessed from a TFTP client. Access is denied if the privileged password (administrative password) is still set to the default setting. Privileged passwords (administrative passwords) must be changed in advance. If the primary and secondary addresses for a VLAN being accessed are the same segment, then the IPv4 secondary address cannot be accessed. If accessing the VLAN with an IPv6 address, then only the IPv6 address specified last can be accessed. Because the internal address is reset if the network switch is started, that means only the bottom IPv6 address listed in the order they were configured can be accessed. Only the IP address of the VLAN with the closest routing to the TFTP client can be accessed. For example, a TFTP client located on VLAN 1 cannot access VLAN 2 IP addresses for the network switch.</div></div><div id="oam_oam_remote_control"><div class="search_title" docfname="oam_oam_remote_control" doctitle="Remote" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation user account management</div><div class="display_word">7. Related Documentation User account management</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#rmon">RMON</div><div class="search_word">rmon</div><div class="display_word">RMON</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview by making settings for the rmon (remote network monitering) function, you can monitor and record the traffic volume and error occurrences for each interface. since the settings for the rmon function and the data obtained by the rmon function are held as an mib, they can be retrieved and edited from the snmp manager. the rmon function of this product supports the following groups defined in rfc2819. ethernet statistics group history group alarm group event group</div><div class="display_word">1. Function Overview By making settings for the RMON (Remote network MONitering) function, you can monitor and record the traffic volume and error occurrences for each interface. Since the settings for the RMON function and the data obtained by the RMON function are held as an MIB, they can be retrieved and edited from the SNMP manager. The RMON function of this product supports the following groups defined in RFC2819. Ethernet statistics group History group Alarm group Event group</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used rmon mib mib for the rmon function, defined in rfc2819 ethernet statistics group mib group defined as group 1 of the rmon mib. this holds a table for monitoring ethernet statistical information. the information in the table includes counters for the number of packets, the number of errors, etc. the etherstatstable is the applicable mib for this product. history group mib group defined as group 2 of the rmon mib. at a specified interval, it measures the same information as the ethernet statistics group, and has a table for saving the history of this information. the mibs relevant for this product are the historycontroltable and the etherhistorytable. alarm group mib group defined as group 3 of the rmon mib. at the specified interval, the statistical information of the ethernet statistics group is compared with the threshold values. if the sampled values exceed the threshold values, the event defined for the event group is generated. the alarmtable is the applicable mib for this product. event group mib group defined as group 9 of the rmon mib. this is the action taken in response when the alarm group conditions are met. the eventtable is the applicable mib for this product.</div><div class="display_word">2. Definition of Terms Used RMON MIB MIB for the RMON function, defined in RFC2819 Ethernet statistics group MIB group defined as group 1 of the RMON MIB. This holds a table for monitoring Ethernet statistical information. The information in the table includes counters for the number of packets, the number of errors, etc. The etherStatsTable is the applicable MIB for this product. History group MIB group defined as group 2 of the RMON MIB. At a specified interval, it measures the same information as the Ethernet statistics group, and has a table for saving the history of this information. The MIBs relevant for this product are the historyControlTable and the etherHistoryTable. Alarm group MIB group defined as group 3 of the RMON MIB. At the specified interval, the statistical information of the Ethernet statistics group is compared with the threshold values. If the sampled values exceed the threshold values, the event defined for the event group is generated. The alarmTable is the applicable MIB for this product. Event group MIB group defined as group 9 of the RMON MIB. This is the action taken in response when the alarm group conditions are met. The eventTable is the applicable MIB for this product.</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details the operating specifications for operation of the rmon function are shown below.</div><div class="display_word">3. Function Details The operating specifications for operation of the RMON function are shown below.</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#グループ共通">3.1. Common between groups</div><div class="search_word">3.1. common between groups the specifications common between groups are given below. in order to enable the rmon function on this product, the system-wide rmon function must be enabled. use the rmon command to make settings. this is enabled by default. you can also set this by using the private mib ysrmonsetting(1.3.6.1.4.1.1182.3.7.1).</div><div class="display_word">3.1. Common between groups The specifications common between groups are given below. In order to enable the RMON function on this product, the system-wide RMON function must be enabled. Use the rmon command to make settings. This is enabled by default. You can also set this by using the private MIB ysrmonSetting(1.3.6.1.4.1.1182.3.7.1).</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#イーサネット統計情報グループ">3.2. Ethernet statistics group</div><div class="search_word">3.2. ethernet statistics group the operating specifications for the ethernet statistics group are given below. make settings by using the rmon statistics command on an interface. starting at the point at which you specified the rmon statistics command, statistical information is collected, and the etherstatstable of the rmon mib will be available for retrieval. this can be specified for a physical interface. a maximum of eight rmon statistics commands can be specified for the same interface. if an rmon statistics command is deleted, the collected statistical information is also deleted. if an rmon statistics command is overwritten, the previously collected statistical information is deleted, and collection is started once again. if the rmon function is disabled system-wide, collection of statistical information is halted. if the rmon function is subsequently enabled system-wide, the previously collected statistical information is deleted, and collection is started once again. the supported oids in the ethernet statistics group are as follows. rmon(1.3.6.1.2.1.16)  +- statistics(1.3.6.1.2.1.16.1)      +- etherstatstable(1.3.6.1.2.1.16.1.1)              + etherstatsentry(1.3.6.1.2.1.16.1.1.1) { etherstatsindex }                  +- etherstatsindex(1.3.6.1.2.1.16.1.1.1.1)         (read-only)                  +- etherstatsdatasource(1.3.6.1.2.1.16.1.1.1.2)    (read-create)                  |interface being monitored                  +- etherstatsdropevents(1.3.6.1.2.1.16.1.1.1.3)    (read-only)                  |number of packets dropped                  +- etherstatsoctets(1.3.6.1.2.1.16.1.1.1.4)        (read-only)                  |number of octets received                  +- etherstatspkts(1.3.6.1.2.1.16.1.1.1.5)          (read-only)                  |number of packets received                  +- etherstatsbroadcastpkts(1.3.6.1.2.1.16.1.1.1.6) (read-only)                  |number of broadcast packets received                  +- etherstatsmulticastpkts(1.3.6.1.2.1.16.1.1.1.7) (read-only)                  |number of multicast packets received                  +- etherstatscrcalignerrors(1.3.6.1.2.1.16.1.1.1.8)(read-only)                  |number of fcs error packets received                  +- etherstatsundersizepkts(1.3.6.1.2.1.16.1.1.1.9) (read-only)                  |number of undersize packets received (packets smaller than 64 octets)                  +- etherstatsoversizepkts(1.3.6.1.2.1.16.1.1.1.10) (read-only)                  |number of oversize packets received (packets larger than 1518 octets)                  +- etherstatsfragments(1.3.6.1.2.1.16.1.1.1.11)    (read-only)                  |number of fragment packets received                  |(packets smaller than 64 octets with abnormal fcs)                  +- etherstatsjabbers(1.3.6.1.2.1.16.1.1.1.12)      (read-only)                  |number of jabber packets received                  |(packets larger than 1518 octets with abnormal fcs)                  +- etherstatscollisions(1.3.6.1.2.1.16.1.1.1.13)   (read-only)                  |number of collisions                  +- etherstatsowner(1.3.6.1.2.1.16.1.1.1.20)        (read-create)                  |name of owner                  +- etherstatsstatus(1.3.6.1.2.1.16.1.1.1.21)       (read-create)                        status of statistical group</div><div class="display_word">3.2. Ethernet statistics group The operating specifications for the Ethernet statistics group are given below. Make settings by using the rmon statistics command on an interface. Starting at the point at which you specified the rmon statistics command, statistical information is collected, and the etherStatsTable of the RMON MIB will be available for retrieval. This can be specified for a physical interface. A maximum of eight rmon statistics commands can be specified for the same interface. If an rmon statistics command is deleted, the collected statistical information is also deleted. If an rmon statistics command is overwritten, the previously collected statistical information is deleted, and collection is started once again. If the RMON function is disabled system-wide, collection of statistical information is halted. If the RMON function is subsequently enabled system-wide, the previously collected statistical information is deleted, and collection is started once again. The supported OIDs in the Ethernet statistics group are as follows. rmon(1.3.6.1.2.1.16)  +- statistics(1.3.6.1.2.1.16.1)      +- etherStatsTable(1.3.6.1.2.1.16.1.1)              + etherStatsEntry(1.3.6.1.2.1.16.1.1.1) { etherStatsIndex }                  +- etherStatsIndex(1.3.6.1.2.1.16.1.1.1.1)         (read-only)                  +- etherStatsDataSource(1.3.6.1.2.1.16.1.1.1.2)    (read-create)                  |Interface being monitored                  +- etherStatsDropEvents(1.3.6.1.2.1.16.1.1.1.3)    (read-only)                  |Number of packets dropped                  +- etherStatsOctets(1.3.6.1.2.1.16.1.1.1.4)        (read-only)                  |Number of octets received                  +- etherStatsPkts(1.3.6.1.2.1.16.1.1.1.5)          (read-only)                  |Number of packets received                  +- etherStatsBroadcastPkts(1.3.6.1.2.1.16.1.1.1.6) (read-only)                  |Number of broadcast packets received                  +- etherStatsMulticastPkts(1.3.6.1.2.1.16.1.1.1.7) (read-only)                  |Number of multicast packets received                  +- etherStatsCRCAlignErrors(1.3.6.1.2.1.16.1.1.1.8)(read-only)                  |Number of FCS error packets received                  +- etherStatsUndersizePkts(1.3.6.1.2.1.16.1.1.1.9) (read-only)                  |Number of undersize packets received (packets smaller than 64 octets)                  +- etherStatsOversizePkts(1.3.6.1.2.1.16.1.1.1.10) (read-only)                  |Number of oversize packets received (packets larger than 1518 octets)                  +- etherStatsFragments(1.3.6.1.2.1.16.1.1.1.11)    (read-only)                  |Number of fragment packets received                  |(packets smaller than 64 octets with abnormal FCS)                  +- etherStatsJabbers(1.3.6.1.2.1.16.1.1.1.12)      (read-only)                  |Number of jabber packets received                  |(packets larger than 1518 octets with abnormal FCS)                  +- etherStatsCollisions(1.3.6.1.2.1.16.1.1.1.13)   (read-only)                  |Number of collisions                  +- etherStatsOwner(1.3.6.1.2.1.16.1.1.1.20)        (read-create)                  |Name of owner                  +- etherStatsStatus(1.3.6.1.2.1.16.1.1.1.21)       (read-create)                        Status of statistical group</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#履歴グループ">3.3. History group</div><div class="search_word">3.3. history group the operating specifications for the history group are shown below. make settings by using the rmon history command on an interface. starting at the point at which you specified the rmon history command, historical information is collected at the specified interval, and the etherhistorytable of the rmon mib will be available for retrieval. this can be specified for a physical interface. a maximum of eight rmon history commands can be specified for the same interface. if an rmon history command is deleted, the collected historical information is also deleted. if an rmon history command is overwritten, the previously collected historical information is deleted, and collection is started once again. if the rmon function is disabled system-wide, collection of historical information is halted. if the rmon function is subsequently enabled system-wide, the previously collected historical information is deleted, and collection is started once again. the supported oids in the ethernet history group are as follows. rmon(1.3.6.1.2.1.16)  +- history(1.3.6.1.2.1.16.2)      +- historycontroltable(1.3.6.1.2.1.16.2.1)      |+ historycontrolentry(1.3.6.1.2.1.16.2.1.1) { historycontrolindex }      |+- historycontrolindex(1.3.6.1.2.1.16.2.1.1.1)           (read-only)      |+- historycontroldatasource(1.3.6.1.2.1.16.2.1.1.2)      (read-create)      ||interface being monitored      |+- historycontrolbucketsrequested(1.3.6.1.2.1.16.2.1.1.3)(read-create)      ||number of history group history saves requested      |+- historycontrolbucketsgranted(1.3.6.1.2.1.16.2.1.1.4)  (read-only)      ||number of history group histories saved      |+- historycontrolinterval(1.3.6.1.2.1.16.2.1.1.5)        (read-create)      ||interval at which history group histories are saved      |+- historycontrolowner(1.3.6.1.2.1.16.2.1.1.6)           (read-create)      ||name of owner      |+- historycontrolstatus(1.3.6.1.2.1.16.2.1.1.7)          (read-create)      |history group status      |      +- etherhistorytable(1.3.6.1.2.1.16.2.2)              + etherhistoryentry(1.3.6.1.2.1.16.2.2.1) { etherhistoryindex, etherhistorysampleindex }                  +- etherhistoryindex(1.3.6.1.2.1.16.2.2.1.1)         (read-only)                  +- etherhistorysampleindex(1.3.6.1.2.1.16.2.2.1.2)   (read-only)                  +- etherhistoryintervalstart(1.3.6.1.2.1.16.2.2.1.3) (read-only)                  |interval at which history group histories are saved                  +- etherhistorydropevents(1.3.6.1.2.1.16.2.2.1.4)    (read-only)                  |number of packets dropped                  +- etherhistoryoctets(1.3.6.1.2.1.16.2.2.1.5)        (read-only)                  |number of octets received                  +- etherhistorypkts(1.3.6.1.2.1.16.2.2.1.6)          (read-only)                  |number of packets received                  +- etherhistorybroadcastpkts(1.3.6.1.2.1.16.2.2.1.7) (read-only)                  |number of broadcast packets received                  +- etherhistorymulticastpkts(1.3.6.1.2.1.16.2.2.1.8) (read-only)                  |number of multicast packets received                  +- etherhistorycrcalignerrors(1.3.6.1.2.1.16.2.2.1.9)(read-only)                  |number of fcs error packets received                  +- etherhistoryundersizepkts(1.3.6.1.2.1.16.2.2.1.10)(read-only)                  |number of undersize packets received (packets smaller than 64 octets)                  +- etherhistoryoversizepkts(1.3.6.1.2.1.16.2.2.1.11) (read-only)                  |number of oversize packets received (packets larger than 1518 octets)                  +- etherhistoryfragments(1.3.6.1.2.1.16.2.2.1.12)    (read-only)                  |ﾌnumber of fragment packets received                  |(packets smaller than 64 octets with abnormal fcs)                  +- etherhistoryjabbers(1.3.6.1.2.1.16.2.2.1.13)      (read-only)                  |number of jabber packets received                  |(packets larger than 1518 octets with abnormal fcs)                  +- etherhistorycollisions(1.3.6.1.2.1.16.2.2.1.14)   (read-only)                  |number of collisions                  +- etherhistoryutilization(1.3.6.1.2.1.16.2.2.1.15)  (read-only)                        estimated value of network usage ratio</div><div class="display_word">3.3. History group The operating specifications for the history group are shown below. Make settings by using the rmon history command on an interface. Starting at the point at which you specified the rmon history command, historical information is collected at the specified interval, and the etherHistoryTable of the RMON MIB will be available for retrieval. This can be specified for a physical interface. A maximum of eight rmon history commands can be specified for the same interface. If an rmon history command is deleted, the collected historical information is also deleted. If an rmon history command is overwritten, the previously collected historical information is deleted, and collection is started once again. If the RMON function is disabled system-wide, collection of historical information is halted. If the RMON function is subsequently enabled system-wide, the previously collected historical information is deleted, and collection is started once again. The supported OIDs in the Ethernet history group are as follows. rmon(1.3.6.1.2.1.16)  +- history(1.3.6.1.2.1.16.2)      +- historyControlTable(1.3.6.1.2.1.16.2.1)      |+ historyControlEntry(1.3.6.1.2.1.16.2.1.1) { historyControlIndex }      |+- historyControlIndex(1.3.6.1.2.1.16.2.1.1.1)           (read-only)      |+- historyControlDataSource(1.3.6.1.2.1.16.2.1.1.2)      (read-create)      ||Interface being monitored      |+- historyControlBucketsRequested(1.3.6.1.2.1.16.2.1.1.3)(read-create)      ||Number of history group history saves requested      |+- historyControlBucketsGranted(1.3.6.1.2.1.16.2.1.1.4)  (read-only)      ||Number of history group histories saved      |+- historyControlInterval(1.3.6.1.2.1.16.2.1.1.5)        (read-create)      ||Interval at which history group histories are saved      |+- historyControlOwner(1.3.6.1.2.1.16.2.1.1.6)           (read-create)      ||Name of owner      |+- historyControlStatus(1.3.6.1.2.1.16.2.1.1.7)          (read-create)      |History group status      |      +- etherHistoryTable(1.3.6.1.2.1.16.2.2)              + etherHistoryEntry(1.3.6.1.2.1.16.2.2.1) { etherHistoryIndex, etherHistorySampleIndex }                  +- etherHistoryIndex(1.3.6.1.2.1.16.2.2.1.1)         (read-only)                  +- etherHistorySampleIndex(1.3.6.1.2.1.16.2.2.1.2)   (read-only)                  +- etherHistoryIntervalStart(1.3.6.1.2.1.16.2.2.1.3) (read-only)                  |Interval at which history group histories are saved                  +- etherHistoryDropEvents(1.3.6.1.2.1.16.2.2.1.4)    (read-only)                  |Number of packets dropped                  +- etherHistoryOctets(1.3.6.1.2.1.16.2.2.1.5)        (read-only)                  |Number of octets received                  +- etherHistoryPkts(1.3.6.1.2.1.16.2.2.1.6)          (read-only)                  |Number of packets received                  +- etherHistoryBroadcastPkts(1.3.6.1.2.1.16.2.2.1.7) (read-only)                  |Number of broadcast packets received                  +- etherHistoryMulticastPkts(1.3.6.1.2.1.16.2.2.1.8) (read-only)                  |Number of multicast packets received                  +- etherHistoryCRCAlignErrors(1.3.6.1.2.1.16.2.2.1.9)(read-only)                  |Number of FCS error packets received                  +- etherHistoryUndersizePkts(1.3.6.1.2.1.16.2.2.1.10)(read-only)                  |Number of undersize packets received (packets smaller than 64 octets)                  +- etherHistoryOversizePkts(1.3.6.1.2.1.16.2.2.1.11) (read-only)                  |Number of oversize packets received (packets larger than 1518 octets)                  +- etherHistoryFragments(1.3.6.1.2.1.16.2.2.1.12)    (read-only)                  |フNumber of fragment packets received                  |(packets smaller than 64 octets with abnormal FCS)                  +- etherHistoryJabbers(1.3.6.1.2.1.16.2.2.1.13)      (read-only)                  |Number of jabber packets received                  |(packets larger than 1518 octets with abnormal FCS)                  +- etherHistoryCollisions(1.3.6.1.2.1.16.2.2.1.14)   (read-only)                  |Number of collisions                  +- etherHistoryUtilization(1.3.6.1.2.1.16.2.2.1.15)  (read-only)                        Estimated value of network usage ratio</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#アラームグループ">3.4. Alarm group</div><div class="search_word">3.4. alarm group the operating specifications for the alarm group are shown below. use the rmon alarm command to make settings. from the point that the rmon alarm command is specified, sampling occurs at the specified interval. if an rmon alarm command is overwritten, the previous sampling data is deleted, and sampling is started once again. if the rmon function is disabled system-wide, sampling is halted. if the rmon function is subsequently enabled system-wide, the previous sampling data is deleted, and sampling is started once again. only etherstatsentry(.1.3.6.1.2.1.16.1.1.1) mib objects that have a counter type can be specified as the object of alarm group monitoring. if the ethernet statistics group used by the rmon alarm command is deleted, the rmon alarm command is also deleted. if the event group used by the rmon alarm command is deleted, the rmon alarm command is also deleted. the supported oids in the alarm group are as follows. rmon(1.3.6.1.2.1.16)  +- alarm(1.3.6.1.2.1.16.3)      +- alarmtable(1.3.6.1.2.1.16.3.1)              + alarmentry(1.3.6.1.2.1.16.3.1.1) { alarmindex }                  +- alarmindex(1.3.6.1.2.1.16.3.1.1.1)              (read-only)                  +- alarminterval(1.3.6.1.2.1.16.3.1.1.2)           (read-create)                  |sampling interval                  +- alarmvariable(1.3.6.1.2.1.16.3.1.1.3)           (read-create)                  |mib object to be monitored                  +- alarmsampletype(1.3.6.1.2.1.16.3.1.1.4)         (read-create)                  |sampling type                  +- alarmvalue(1.3.6.1.2.1.16.3.1.1.5)              (read-only)                  |estimated value                  +- alarmstartupalarm(1.3.6.1.2.1.16.3.1.1.6)       (read-create)                  |threshold value used for first alarm determination                  +- alarmrisingthreshold(1.3.6.1.2.1.16.3.1.1.7)    (read-create)                  |upper threshold value                  +- alarmfallingthreshold(1.3.6.1.2.1.16.3.1.1.8)   (read-create)                  |lower threshold value                  +- alarmrisingeventindex(1.3.6.1.2.1.16.3.1.1.9)   (read-create)                  |event index when crossing upper limit                  +- alarmfallingeventindex(1.3.6.1.2.1.16.3.1.1.10) (read-create)                  |event index when crossing lower limit                  +- alarmowner(1.3.6.1.2.1.16.3.1.1.11)             (read-create)                  |name of owner                  +- alarmstatus(1.3.6.1.2.1.16.3.1.1.12)            (read-create)                        alarm group status alarm detection is determined by an upper threshold value and a lower threshold value. if the threshold value is crossed, the specified event is executed. if an alarm is detected, the alarm will not be detected again until the value crosses the opposite threshold. the following cases are explained as examples. at point 1, the upper threshold value is crossed, so an alarm is detected. the threshold value that is used for the very first decision can be specified by startup. in the example above, we will assume that the startup value is “1” (using only the upper threshold value (risingalarm)) or “3” (using both the upper threshold value and the lower threshold value (risingorfallingalarm)). at point 2, an alarm is not detected. at point 3, the upper threshold value is crossed, but since the opposite threshold was not previously crossed, an alarm is not detected. at point 4, the lower threshold value is crossed, and since the upper threshold was previously crossed, an alarm is detected. at point 5, the lower threshold value is exceeded, but since the opposite upper threshold was not previously crossed, an alarm is not detected. at point 6, the upper threshold value is crossed, and since the lower threshold was previously crossed, an alarm is detected.</div><div class="display_word">3.4. Alarm group The operating specifications for the alarm group are shown below. Use the rmon alarm command to make settings. From the point that the rmon alarm command is specified, sampling occurs at the specified interval. If an rmon alarm command is overwritten, the previous sampling data is deleted, and sampling is started once again. If the RMON function is disabled system-wide, sampling is halted. If the RMON function is subsequently enabled system-wide, the previous sampling data is deleted, and sampling is started once again. Only etherStatsEntry(.1.3.6.1.2.1.16.1.1.1) MIB objects that have a counter type can be specified as the object of alarm group monitoring. If the Ethernet statistics group used by the rmon alarm command is deleted, the rmon alarm command is also deleted. If the event group used by the rmon alarm command is deleted, the rmon alarm command is also deleted. The supported OIDs in the alarm group are as follows. rmon(1.3.6.1.2.1.16)  +- alarm(1.3.6.1.2.1.16.3)      +- alarmTable(1.3.6.1.2.1.16.3.1)              + alarmEntry(1.3.6.1.2.1.16.3.1.1) { alarmIndex }                  +- alarmIndex(1.3.6.1.2.1.16.3.1.1.1)              (read-only)                  +- alarmInterval(1.3.6.1.2.1.16.3.1.1.2)           (read-create)                  |Sampling interval                  +- alarmVariable(1.3.6.1.2.1.16.3.1.1.3)           (read-create)                  |MIB object to be monitored                  +- alarmSampleType(1.3.6.1.2.1.16.3.1.1.4)         (read-create)                  |Sampling type                  +- alarmValue(1.3.6.1.2.1.16.3.1.1.5)              (read-only)                  |Estimated value                  +- alarmStartupAlarm(1.3.6.1.2.1.16.3.1.1.6)       (read-create)                  |Threshold value used for first alarm determination                  +- alarmRisingThreshold(1.3.6.1.2.1.16.3.1.1.7)    (read-create)                  |Upper threshold value                  +- alarmFallingThreshold(1.3.6.1.2.1.16.3.1.1.8)   (read-create)                  |Lower threshold value                  +- alarmRisingEventIndex(1.3.6.1.2.1.16.3.1.1.9)   (read-create)                  |Event index when crossing upper limit                  +- alarmFallingEventIndex(1.3.6.1.2.1.16.3.1.1.10) (read-create)                  |Event index when crossing lower limit                  +- alarmOwner(1.3.6.1.2.1.16.3.1.1.11)             (read-create)                  |Name of owner                  +- alarmStatus(1.3.6.1.2.1.16.3.1.1.12)            (read-create)                        Alarm group status Alarm detection is determined by an upper threshold value and a lower threshold value. If the threshold value is crossed, the specified event is executed. If an alarm is detected, the alarm will not be detected again until the value crosses the opposite threshold. The following cases are explained as examples. At point 1, the upper threshold value is crossed, so an alarm is detected. The threshold value that is used for the very first decision can be specified by STARTUP. In the example above, we will assume that the STARTUP value is “1” (using only the upper threshold value (risingAlarm)) or “3” (using both the upper threshold value and the lower threshold value (risingOrFallingAlarm)). At point 2, an alarm is not detected. At point 3, the upper threshold value is crossed, but since the opposite threshold was not previously crossed, an alarm is not detected. At point 4, the lower threshold value is crossed, and since the upper threshold was previously crossed, an alarm is detected. At point 5, the lower threshold value is exceeded, but since the opposite upper threshold was not previously crossed, an alarm is not detected. At point 6, the upper threshold value is crossed, and since the lower threshold was previously crossed, an alarm is detected.</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#イベントグループ">3.5. Event group</div><div class="search_word">3.5. event group the operating specifications for the event group are shown below. use the rmon event command to make settings. the following operations can be specified for the event group. record to log send snmp trap record to log and send snmp trap if trap transmission is specified, the following snmp commands must be set in order to transmit the snmp trap. snmp-server host snmp-server enable trap rmon the following operations will be carried out when specifying trap transmission. snmpv1､snmpv2c only the traps for which the community name specified using the rmon event command, and for which the community name specified by the snmp-server host command are matching will be transmitted. snmpv3 only the traps for which the community name specified using the rmon event command, and for which the user name specified by the snmp-server host command are matching will be transmitted. the supported oids in the event group are as follows. rmon(1.3.6.1.2.1.16)  +- event(1.3.6.1.2.1.16.9)      +- eventtable(1.3.6.1.2.1.16.9.1)              + evententry(1.3.6.1.2.1.16.9.1.1) { eventindex }                  +- eventindex(1.3.6.1.2.1.16.9.1.1.1)        (read-only)                  +- eventdescription(1.3.6.1.2.1.16.9.1.1.2)  (read-create)                  |event description                  +- eventtype(1.3.6.1.2.1.16.9.1.1.3)         (read-create)                  |event type                  +- eventcommunity(1.3.6.1.2.1.16.9.1.1.4)    (read-create)                  |community name                  +- eventlasttimesent(1.3.6.1.2.1.16.9.1.1.5) (read-only)                  |event execution time                  +- eventowner(1.3.6.1.2.1.16.9.1.1.6)        (read-create)                  |name of owner                  +- eventstatus(1.3.6.1.2.1.16.9.1.1.7)       (read-create)                        event group status</div><div class="display_word">3.5. Event group The operating specifications for the event group are shown below. Use the rmon event command to make settings. The following operations can be specified for the event group. Record to log Send SNMP trap Record to log and send SNMP trap If trap transmission is specified, the following SNMP commands must be set in order to transmit the SNMP trap. snmp-server host snmp-server enable trap rmon The following operations will be carried out when specifying trap transmission. SNMPv1、SNMPv2c Only the traps for which the community name specified using the rmon event command, and for which the community name specified by the snmp-server host command are matching will be transmitted. SNMPv3 Only the traps for which the community name specified using the rmon event command, and for which the user name specified by the snmp-server host command are matching will be transmitted. The supported OIDs in the event group are as follows. rmon(1.3.6.1.2.1.16)  +- event(1.3.6.1.2.1.16.9)      +- eventTable(1.3.6.1.2.1.16.9.1)              + eventEntry(1.3.6.1.2.1.16.9.1.1) { eventIndex }                  +- eventIndex(1.3.6.1.2.1.16.9.1.1.1)        (read-only)                  +- eventDescription(1.3.6.1.2.1.16.9.1.1.2)  (read-create)                  |Event description                  +- eventType(1.3.6.1.2.1.16.9.1.1.3)         (read-create)                  |Event type                  +- eventCommunity(1.3.6.1.2.1.16.9.1.1.4)    (read-create)                  |Community name                  +- eventLastTimeSent(1.3.6.1.2.1.16.9.1.1.5) (read-only)                  |Event execution time                  +- eventOwner(1.3.6.1.2.1.16.9.1.1.6)        (read-create)                  |Name of owner                  +- eventStatus(1.3.6.1.2.1.16.9.1.1.7)       (read-create)                        Event group status</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#snmpマネージャーのsetrequestによる設定">3.6. Setting by SetRequest from an SNMP manager</div><div class="search_word">3.6. setting by setrequest from an snmp manager the same content as the commands of each group can be specified by using setrequest from an snmp manager. the procedure for making settings from an snmp manager is as follows. as an example, we explain how to make new settings for the ethernet statistics information (etherstatstable) group to port1.1 using index number 1. similar operations can be used to make settings for a supported mib on other groups. make snmp settings to allow the mib to be written. for details, refer to snmp . for etherstatsstatus.1, specify “2” (createrequest). the “.1” of etherstatsstatus.1 is the etherstatstable index. for etherstatsdatasource.1, specify ifindex.5001 as the interface to be monitored. ifindex.5001 indicates port1.1. specifying “owner” is optional, but if you do, specify the text string in etherstatsowner.1. for etherstatsstatus, specify “1” (valid). when you perform the above steps, the following commands are specified for port1.1. we assume that “rmon” was set as the “owner” setting. rmon statistics 1 owner rmon below we show how to disable the rmon function system-wide from the snmp manager. make snmp settings to allow the mib to be written. for details, refer to snmp . for ysrmonsetting(1.3.6.1.4.1.1182.3.7.1), specify “2” (disabled). when you perform the above steps, the following commands are specified. rmon disable to specify enable, set ysrmonsetting(1.3.6.1.4.1.1182.3.7.1) to “1” (enabled).</div><div class="display_word">3.6. Setting by SetRequest from an SNMP manager The same content as the commands of each group can be specified by using SetRequest from an SNMP manager. The procedure for making settings from an SNMP manager is as follows. As an example, we explain how to make new settings for the Ethernet statistics information (etherStatsTable) group to port1.1 using index number 1. Similar operations can be used to make settings for a supported MIB on other groups. Make SNMP settings to allow the MIB to be written. For details, refer to SNMP . For etherStatsStatus.1, specify “2” (createRequest). The “.1” of etherStatsStatus.1 is the etherStatsTable index. For etherStatsDataSource.1, specify ifIndex.5001 as the interface to be monitored. ifIndex.5001 indicates port1.1. Specifying “owner” is optional, but if you do, specify the text string in etherStatsOwner.1. For etherStatsStatus, specify “1” (valid). When you perform the above steps, the following commands are specified for port1.1. We assume that “RMON” was set as the “owner” setting. rmon statistics 1 owner RMON Below we show how to disable the RMON function system-wide from the SNMP manager. Make SNMP settings to allow the MIB to be written. For details, refer to SNMP . For ysrmonSetting(1.3.6.1.4.1.1182.3.7.1), specify “2” (disabled). When you perform the above steps, the following commands are specified. rmon disable To specify enable, set ysrmonSetting(1.3.6.1.4.1.1182.3.7.1) to “1” (enabled).</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands enable the rmon function rmon set rmon ethernet statistics group rmon statistics set rmon history group rmon history set rmon event group rmon event set rmon alarm group rmon alarm show rmon function status show rmon show rmon ethernet statistics group status show rmon statistics show rmon history group status show rmon history show rmon event group status show rmon event show rmon alarm group status show rmon alarm clear rmon ethernet statistics group counters rmon clear counters</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Enable the RMON function rmon Set RMON Ethernet statistics group rmon statistics Set RMON history group rmon history Set RMON event group rmon event Set RMON alarm group rmon alarm Show RMON function status show rmon Show RMON Ethernet statistics group status show rmon statistics Show RMON history group status show rmon history Show RMON event group status show rmon event Show RMON alarm group status show rmon alarm Clear RMON Ethernet statistics group counters rmon clear counters</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#イーサネット統計情報グループの設定">5.1. Setting an Ethernet statistics group</div><div class="search_word">5.1. setting an ethernet statistics group make ethernet statistics group settings for port 1.1, and from the snmp manager, retrieve the mib of the ethernet statistical information group. ■ setting procedure enable the ethernet statistics group setting for port1.1. the index of the ethernet statistics group is “1.” yamaha(config)#interface port1.1yamaha(config-if)#rmon statistics 1 (1) 1 enable the ethernet statistics group settings from the snmp manager, make snmp settings that the mib of the ethernet statistics group can be retrieved. in this example, we use “private” access on snmpv1 or snmpv2c. yamaha(config)#snmp-server community private rw (1) 1 set the readable/writable community name as “private”. from the snmp manger, it will be possible to retrieve the etherstatstable(.1.3.6.1.2.1.16.1.1) with the community name “private.”</div><div class="display_word">5.1. Setting an Ethernet statistics group Make Ethernet statistics group settings for port 1.1, and from the SNMP manager, retrieve the MIB of the Ethernet statistical information group. ■ Setting Procedure Enable the Ethernet statistics group setting for port1.1. The index of the Ethernet statistics group is “1.” Yamaha(config)#interface port1.1Yamaha(config-if)#rmon statistics 1 (1) 1 Enable the Ethernet statistics group settings From the SNMP manager, make SNMP settings that the MIB of the Ethernet statistics group can be retrieved. In this example, we use “private” access on SNMPv1 or SNMPv2c. Yamaha(config)#snmp-server community private rw (1) 1 Set the readable/writable community name as “private”. From the SNMP manger, it will be possible to retrieve the etherStatsTable(.1.3.6.1.2.1.16.1.1) with the community name “private.”</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#履歴グループの設定">5.2. Setting a history group</div><div class="search_word">5.2. setting a history group make settings for the history group of port1.1 and retrieve the mib of the history group from the snmp manager. ■ setting procedure enable the port1.1 history group setting. the index of the history group is “1.” yamaha(config)#interface port1.1yamaha(config-if)#rmon history 1 (1) 1 enable the history group settings from the snmp manager, make snmp settings that the mib of the history group can be retrieved. in this example, we use “private” access on snmpv1 or snmpv2c. yamaha(config)#snmp-server community private rw (1) 1 set the readable/writable community name as “private”. from the snmp manger, it will be possible to retrieve the etherhistorytable(.1.3.6.1.2.1.16.2.2) with the community name “private.”</div><div class="display_word">5.2. Setting a history group Make settings for the history group of port1.1 and retrieve the MIB of the history group from the SNMP manager. ■ Setting Procedure Enable the port1.1 history group setting. The index of the history group is “1.” Yamaha(config)#interface port1.1Yamaha(config-if)#rmon history 1 (1) 1 Enable the history group settings From the SNMP manager, make SNMP settings that the MIB of the history group can be retrieved. In this example, we use “private” access on SNMPv1 or SNMPv2c. Yamaha(config)#snmp-server community private rw (1) 1 Set the readable/writable community name as “private”. From the SNMP manger, it will be possible to retrieve the etherHistoryTable(.1.3.6.1.2.1.16.2.2) with the community name “private.”</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#アラームイベントグループの設定">5.3. Setting an alarm event group</div><div class="search_word">5.3. setting an alarm event group use the alarm group to monitor the statistical information values of the ethernet statistics group. the conditions for monitoring are as follows. the mib to be monitored is port1.1’s etherstatspkts(.1.3.6.1.2.1.16.1.1.1.5). the sampling interval is 180 seconds. the sampling type is delta. the upper threshold value is 2000. the lower threshold value is 1000. when the above monitoring conditions are matched, the following event group is executed. record to log and send snmp trap community name is “rmon” ■ setting procedure make the required settings for snmp trap transmission. yamaha(config)#snmp-server host 192.168.100.3 traps version 2c rmon (1) yamaha(config)#snmp-server enable trap rmon (2) 1 set the trap destination 2 enable transmission of traps for the rmon function make event group settings. the index of the event group is “1.” yamaha(config)#rmon event 1 log-trap rmon (1) 1 enable the event group settings in order to set the alarm group’s monitoring target mib object, enable the port1.1 ethernet statistics group setting. the index of the ethernet statistics group is “1.” yamaha(config)#interface port1.1yamaha(config-if)#rmon statistics 1 (1) 1 enable the ethernet statistics group settings set the alarm group with the listed conditions. the index of the alarm group is “1.” yamaha(config)#rmon alarm 1 etherstatspkts.1 interval 180 delta rising-threshold 3000 event 1 falling-threshold 2000 event 1 (1) 1 enable an alarm group</div><div class="display_word">5.3. Setting an alarm event group Use the alarm group to monitor the statistical information values of the Ethernet statistics group. The conditions for monitoring are as follows. The MIB to be monitored is port1.1’s etherStatsPkts(.1.3.6.1.2.1.16.1.1.1.5). The sampling interval is 180 seconds. The sampling type is delta. The upper threshold value is 2000. The lower threshold value is 1000. When the above monitoring conditions are matched, the following event group is executed. Record to log and send SNMP trap Community name is “RMON” ■ Setting Procedure Make the required settings for SNMP trap transmission. Yamaha(config)#snmp-server host 192.168.100.3 traps version 2c RMON (1) Yamaha(config)#snmp-server enable trap rmon (2) 1 Set the trap destination 2 Enable transmission of traps for the RMON function Make event group settings. The index of the event group is “1.” Yamaha(config)#rmon event 1 log-trap RMON (1) 1 Enable the event group settings In order to set the alarm group’s monitoring target MIB object, enable the port1.1 Ethernet statistics group setting. The index of the Ethernet statistics group is “1.” Yamaha(config)#interface port1.1Yamaha(config-if)#rmon statistics 1 (1) 1 Enable the Ethernet statistics group settings Set the alarm group with the listed conditions. The index of the alarm group is “1.” Yamaha(config)#rmon alarm 1 etherStatsPkts.1 interval 180 delta rising-threshold 3000 event 1 falling-threshold 2000 event 1 (1) 1 Enable an alarm group</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution none</div><div class="display_word">6. Points of Caution None</div></div><div id="oam_oam_rmon"><div class="search_title" docfname="oam_oam_rmon" doctitle="RMON" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation maintenance and operation functions: snmp</div><div class="display_word">7. Related Documentation Maintenance and Operation Functions: SNMP</div></div><div id="oam_oam_schedule"><div class="search_title" docfname="oam_oam_schedule" doctitle="Schedule" link="#スケジュール機能">Schedule Function</div><div class="search_word">schedule function</div><div class="display_word">Schedule Function</div></div><div id="oam_oam_schedule"><div class="search_title" docfname="oam_oam_schedule" doctitle="Schedule" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview scheduling functionality is used to execute specific processes when any particular time or event occurs. this functionality enables the following types of actions using a yamaha network switch. apply qos to a specific vlan only during a specific period. supplies poe power to wireless lan access points only during the specified period. periodically saves “tech-support” information in microsd memory.</div><div class="display_word">1. Function Overview Scheduling functionality is used to execute specific processes when any particular time or event occurs. This functionality enables the following types of actions using a Yamaha network switch. Apply QoS to a specific VLAN only during a specific period. Supplies PoE power to wireless LAN access points only during the specified period. Periodically saves “tech-support” information in microSD memory.</div></div><div id="oam_oam_schedule"><div class="search_title" docfname="oam_oam_schedule" doctitle="Schedule" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used trigger general term for conditions/criteria, such as that the internal clock time matches a specified time or that a specific event occurs. time trigger condition that the internal clock time matches a specified time. event trigger condition that a specific event occurs. action action executed when a trigger is activated.</div><div class="display_word">2. Definition of Terms Used Trigger General term for conditions/criteria, such as that the internal clock time matches a specified time or that a specific event occurs. Time Trigger Condition that the internal clock time matches a specified time. Event Trigger Condition that a specific event occurs. Action Action executed when a trigger is activated.</div></div><div id="oam_oam_schedule"><div class="search_title" docfname="oam_oam_schedule" doctitle="Schedule" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details scheduling functionality involves specifying “triggers” and actions, which are the two parameter settings for executing specific process “actions” when a particular specified time or event trigger occurs.</div><div class="display_word">3. Function Details Scheduling functionality involves specifying “triggers” and actions, which are the two parameter settings for executing specific process “actions” when a particular specified time or event trigger occurs.</div></div><div id="oam_oam_schedule"><div class="search_title" docfname="oam_oam_schedule" doctitle="Schedule" link="#時刻トリガー">3.1. Time Trigger</div><div class="search_word">3.1. time trigger time triggers can be specified in terms of year, month, day, hour, minute, and second. time triggers are specified using the schedule command. available setting parameters are indicated below. type specification method setting value example date month 1-12 one specific month (such as only december) 12 multiple specific months (such as only january and february) 1,2 range from specific month to december (such as february to december) 2- range from specific month to specific month (such as february to july) 2-7 range from january to specific month (such as january to july) -7 every month * day 1-31 one specific day (such as day 1 only) 1 multiple specific days (such as days 1 and 2 only) 1,2 range from specific day to last day (such as day 2 to month-end) 2- range from specific day to specific day (such as days 2 to 7) 2-7 range from day 1 to specific day (such as days 1 to 7) -7 every day * specific day-of-week only (such as monday only) mon multiple specific days of the week only (such as saturday and sundays only) sat,sun range from specific day-of-week to specific day-of-week (such as monday to friday) mon-fri range from sunday to specific day-of-the-week (such as sunday to friday) -fri hours, minutes, seconds hours 0-23 specific hour only (such as 23:00 only) 23 multiple specific hours only (such as 01:00 and 22:00 only) 1,22 range from specific hour to 23:00 (such as 02:00 to 23:00) 2- range from specific hour to specific hour (such as 02:00 to 21:00) 2-21 range from hour 00:00 to specific hour (such as 00:00 to 21:00) -21 each hour * minutes 0-59 one specific minute only (such as minute 59 only) 59 multiple specific minutes only (such as minutes 1 and 50 only) 1,50 range from specific minute to minute 59 (such as minutes 2 to 59) 2- range from specific minute to specific minute (such as minutes 2 to 50) 2-50 range from minute 0 to specific minute (such as minutes 0 to 50) -50 each minute * seconds 0-59 one specific second only (such as second 59 only) this setting may be omitted. 59</div><div class="display_word">3.1. Time Trigger Time triggers can be specified in terms of year, month, day, hour, minute, and second. Time triggers are specified using the schedule command. Available setting parameters are indicated below. Type Specification method Setting value example Date Month 1-12 One specific month (such as only December) 12 Multiple specific months (such as only January and February) 1,2 Range from specific month to December (such as February to December) 2- Range from specific month to specific month (such as February to July) 2-7 Range from January to specific month (such as January to July) -7 Every month * Day 1-31 One specific day (such as day 1 only) 1 Multiple specific days (such as days 1 and 2 only) 1,2 Range from specific day to last day (such as day 2 to month-end) 2- Range from specific day to specific day (such as days 2 to 7) 2-7 Range from day 1 to specific day (such as days 1 to 7) -7 Every day * Specific day-of-week only (such as Monday only) mon Multiple specific days of the week only (such as Saturday and Sundays only) sat,sun Range from specific day-of-week to specific day-of-week (such as Monday to Friday) mon-fri Range from Sunday to specific day-of-the-week (such as Sunday to Friday) -fri Hours, minutes, seconds Hours 0-23 Specific hour only (such as 23:00 only) 23 Multiple specific hours only (such as 01:00 and 22:00 only) 1,22 Range from specific hour to 23:00 (such as 02:00 to 23:00) 2- Range from specific hour to specific hour (such as 02:00 to 21:00) 2-21 Range from hour 00:00 to specific hour (such as 00:00 to 21:00) -21 Each hour * Minutes 0-59 One specific minute only (such as minute 59 only) 59 Multiple specific minutes only (such as minutes 1 and 50 only) 1,50 Range from specific minute to minute 59 (such as minutes 2 to 59) 2- Range from specific minute to specific minute (such as minutes 2 to 50) 2-50 Range from minute 0 to specific minute (such as minutes 0 to 50) -50 Each minute * Seconds 0-59 One specific second only (such as second 59 only) This setting may be omitted. 59</div></div><div id="oam_oam_schedule"><div class="search_title" docfname="oam_oam_schedule" doctitle="Schedule" link="#イベントトリガー">3.2. Event Trigger</div><div class="search_word">3.2. event trigger either of the following events can be specified as an event trigger. time triggers are specified using the schedule command. events that can be specified are indicated below. type description startup action is executed when startup occurs. sd-attached action is executed when a microsd card is inserted.</div><div class="display_word">3.2. Event Trigger Either of the following events can be specified as an event trigger. Time triggers are specified using the schedule command. Events that can be specified are indicated below. Type Description startup Action is executed when startup occurs. sd-attached Action is executed when a microSD card is inserted.</div></div><div id="oam_oam_schedule"><div class="search_title" docfname="oam_oam_schedule" doctitle="Schedule" link="#アクション">3.3. Action</div><div class="search_word">3.3. action processes executed when a time trigger or event trigger is activated are called actions. to specify actions, use the schedule template command to switch to the schedule template mode and then specify the action using the cli-command or script command. the following two actions are available. action command for settings description executes specified command cli-command command executes the specified commands in ascending order of id numbers. executes specified script script command executes the character strings in the first 100 lines of the specified file /(model name)/schedule/script.txt in external memory (microsd) as a command.</div><div class="display_word">3.3. Action Processes executed when a time trigger or event trigger is activated are called actions. To specify actions, use the schedule template command to switch to the schedule template mode and then specify the action using the cli-command or script command. The following two actions are available. Action Command for settings Description Executes specified command cli-command command Executes the specified commands in ascending order of ID numbers. Executes Specified Script script command Executes the character strings in the first 100 lines of the specified file /(model name)/schedule/script.txt in external memory (microSD) as a command.</div></div><div id="oam_oam_schedule"><div class="search_title" docfname="oam_oam_schedule" doctitle="Schedule" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operating mode commands description global configuration mode schedule specifies a schedule template id that specifies the trigger and defines the action. schedule template specifies the schedule template id and switches to the schedule template mode. schedule template mode description specifies description of the schedule template. action enables/disables the schedule template. use disable to temporarily disable schedule function. cli-command defines command executed when trigger is activated.</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operating mode Commands Description Global configuration mode schedule Specifies a schedule template ID that specifies the trigger and defines the action. schedule template Specifies the schedule template ID and switches to the schedule template mode. Schedule template mode description Specifies description of the schedule template. action Enables/disables the schedule template. Use disable to temporarily disable schedule function. cli-command Defines command executed when trigger is activated.</div></div><div id="oam_oam_schedule"><div class="search_title" docfname="oam_oam_schedule" doctitle="Schedule" link="#設定例">5. Setting Examples</div><div class="search_word">5. setting examples</div><div class="display_word">5. Setting Examples</div></div><div id="oam_oam_schedule"><div class="search_title" docfname="oam_oam_schedule" doctitle="Schedule" link="#特定の時間帯だけ無線lanアクセスポイントにpoe給電する場合">5.1. Supplying PoE power to wireless LAN access points only during specified hours</div><div class="search_word">5.1. supplying poe power to wireless lan access points only during specified hours supply poe power to wireless lan access points connected to port1.1 and port1.2 on weekdays only between 8:00 and 17:00. yamaha#yamaha# configure terminalyamaha(config)# schedule 1 time */mon-fri 8:00:00 1yamaha(config)# schedule template 1yamaha(config-schedule)# cli-command 1 configure terminalyamaha(config-schedule)# cli-command 2 interface port1.1-2yamaha(config-schedule)# cli-command 3 power-inline enableyamaha(config-schedule)# exityamaha(config)#yamaha(config)# schedule 2 time */mon-fri 17:00:00 2yamaha(config)# schedule template 2yamaha(config-schedule)# cli-command 1 configure terminalyamaha(config-schedule)# cli-command 2 interface port1.1-2yamaha(config-schedule)# cli-command 3 power-inline disableyamaha(config-schedule)# endyamaha#</div><div class="display_word">5.1. Supplying PoE power to wireless LAN access points only during specified hours Supply PoE power to wireless LAN access points connected to port1.1 and port1.2 on weekdays only between 8:00 and 17:00. Yamaha#Yamaha# configure terminalYamaha(config)# schedule 1 time */mon-fri 8:00:00 1Yamaha(config)# schedule template 1Yamaha(config-schedule)# cli-command 1 configure terminalYamaha(config-schedule)# cli-command 2 interface port1.1-2Yamaha(config-schedule)# cli-command 3 power-inline enableYamaha(config-schedule)# exitYamaha(config)#Yamaha(config)# schedule 2 time */mon-fri 17:00:00 2Yamaha(config)# schedule template 2Yamaha(config-schedule)# cli-command 1 configure terminalYamaha(config-schedule)# cli-command 2 interface port1.1-2Yamaha(config-schedule)# cli-command 3 power-inline disableYamaha(config-schedule)# endYamaha#</div></div><div id="oam_oam_schedule"><div class="search_title" docfname="oam_oam_schedule" doctitle="Schedule" link="#microsd挿入時に内部情報を取得">5.2. Obtaining internal information when microSD memory is inserted</div><div class="search_word">5.2. obtaining internal information when microsd memory is inserted automatically saves tech-support in microsd memory when microsd card is inserted. yamaha#yamaha# configure terminalyamaha(config)# schedule 1 event sd-attached 1yamaha(config)# schedule template 1yamaha(config-schedule)# cli-command 1 copy tech-support sdyamaha(config-schedule)# endyamaha#</div><div class="display_word">5.2. Obtaining internal information when microSD memory is inserted Automatically saves tech-support in microSD memory when microSD card is inserted. Yamaha#Yamaha# configure terminalYamaha(config)# schedule 1 event sd-attached 1Yamaha(config)# schedule template 1Yamaha(config-schedule)# cli-command 1 copy tech-support sdYamaha(config-schedule)# endYamaha#</div></div><div id="oam_oam_schedule"><div class="search_title" docfname="oam_oam_schedule" doctitle="Schedule" link="#実行禁止コマンド">6. Unavailable Commands</div><div class="search_word">6. unavailable commands the following commands cannot be executed for the schedule function. backup system baudrate select boot prioritize sd / no boot prioritize sd certificate user commands that begin with “clock” cold start copy radius-server local crypto pki generate ca / no crypto pki generate ca disable enable password exit firmware-update execute firmware-update sd execute logout commands that begin with “ntpdate” or “no ntpdate” password / no password password-encryption / no password-encryption ping /ping6 quit reload remote-login restart restore system schedule / no schedule schedule template / no schedule template commands that begin with “show” ssh ssh-server host key generate commands that begin with “stack” or “no stack” startup-config select / no startup-config select telnet traceroute / traceroute6</div><div class="display_word">6. Unavailable Commands The following commands cannot be executed for the schedule function. backup system baudrate select boot prioritize sd / no boot prioritize sd certificate user Commands that begin with “clock” cold start copy radius-server local crypto pki generate ca / no crypto pki generate ca disable enable password exit firmware-update execute firmware-update sd execute logout Commands that begin with “ntpdate” or “no ntpdate” password / no password password-encryption / no password-encryption ping /ping6 quit reload remote-login restart restore system schedule / no schedule schedule template / no schedule template Commands that begin with “show” ssh ssh-server host key generate Commands that begin with “stack” or “no stack” startup-config select / no startup-config select telnet traceroute / traceroute6</div></div><div id="oam_oam_schedule"><div class="search_title" docfname="oam_oam_schedule" doctitle="Schedule" link="#syslog">7. SYSLOG</div><div class="search_word">7. syslog the schedule function outputs the following syslog messages. level output description info [schedule]:inf:id:x command is done the schedule template id:x command was executed when the trigger was activated. [schedule]:inf:id:x script is done the schedule template id:x script was executed when the trigger was activated. error [schedule]:err:id:x cmd[id][command] is prohibited to execute execution of the prohibited command command in schedule template id:x was suppressed. [schedule]:err:id:x cmd[id][command] is failed to execute command failed in schedule template id:x due to invalid command format or inappropriate parameter setting. [schedule]:err:id:x microsd is not mounted script execution failed at schedule template id:x because microsd was not inserted. [schedule]:err:id:x failed to get the schedule forlder path script execution failed at schedule template id:x because the expected directory containing the script was not found. [schedule]:err:id:x script is not found script execution failed at schedule template id:x because the script file was not found. [schedule]:err:id:x failed to add action to queue action failed at schedule template id:x because action was discarded due to the many actions waiting for execution in the queue.</div><div class="display_word">7. SYSLOG The schedule function outputs the following SYSLOG messages. Level Output Description Info [SCHEDULE]:inf:ID:X command is done The schedule template ID:X command was executed when the trigger was activated. [SCHEDULE]:inf:ID:X script is done The schedule template ID:X script was executed when the trigger was activated. Error [SCHEDULE]:err:ID:X cmd[ID][COMMAND] is prohibited to execute Execution of the prohibited command COMMAND in schedule template ID:X was suppressed. [SCHEDULE]:err:ID:X cmd[ID][COMMAND] is failed to execute Command failed in schedule template ID:X due to invalid command format or inappropriate parameter setting. [SCHEDULE]:err:ID:X microSD is not mounted Script execution failed at schedule template ID:X because microSD was not inserted. [SCHEDULE]:err:ID:X failed to get the schedule forlder path Script execution failed at schedule template ID:X because the expected directory containing the script was not found. [SCHEDULE]:err:ID:X script is not found Script execution failed at schedule template ID:X because the script file was not found. [SCHEDULE]:err:ID:X failed to add action to queue Action failed at schedule template ID:X because action was discarded due to the many actions waiting for execution in the queue.</div></div><div id="oam_oam_schedule"><div class="search_title" docfname="oam_oam_schedule" doctitle="Schedule" link="#注意事項">8. Points of Caution</div><div class="search_word">8. points of caution when actions are executed, the cli-command executes actions in ascending id number order. when actions are executed, even if a command specified by the cli-command results in an execution error, the remaining commands are executed. if both a cli-command and script command are specified in the same schedule template, then the script command is executed and the cli-command is not executed. if multiple triggers are activated simultaneously, then actions are executed in ascending order of schedule template id number. the following precautions apply for devices that include a stack. a “startup” event trigger was not activated in stack member switches. a “sd-attached” event trigger was not activated in stack member switches. the trigger is not activated if a stack is enabled and is in the standalone state. if the trigger activation time elapses due to the time setting being set manually by the clock set command or being changed by ntp, then any existing triggers scheduled to be activated within 59 seconds of when the current time setting was changed will be activated. if the trigger activation time was changed backward manually by the clock set command or by ntp, then the time triggers are checked again starting from the time to which it was set back. this function can be used to periodically save the configuration, but periodic rewriting will consume rom capacity more quickly. rom failures due to frequent rewriting are not warranted for free repairs, even if they occur during the warranty period.</div><div class="display_word">8. Points of Caution When actions are executed, the cli-command executes actions in ascending ID number order. When actions are executed, even if a command specified by the cli-command results in an execution error, the remaining commands are executed. If both a cli-command and script command are specified in the same schedule template, then the script command is executed and the cli-command is not executed. If multiple triggers are activated simultaneously, then actions are executed in ascending order of schedule template ID number. The following precautions apply for devices that include a stack. A “startup” event trigger was not activated in stack member switches. A “sd-attached” event trigger was not activated in stack member switches. The trigger is not activated if a stack is enabled and is in the standalone state. If the trigger activation time elapses due to the time setting being set manually by the clock set command or being changed by NTP, then any existing triggers scheduled to be activated within 59 seconds of when the current time setting was changed will be activated. If the trigger activation time was changed backward manually by the clock set command or by NTP, then the time triggers are checked again starting from the time to which it was set back. This function can be used to periodically save the configuration, but periodic rewriting will consume ROM capacity more quickly. ROM failures due to frequent rewriting are not warranted for free repairs, even if they occur during the warranty period.</div></div><div id="oam_oam_schedule"><div class="search_title" docfname="oam_oam_schedule" doctitle="Schedule" link="#関連文書">9. Related Documentation</div><div class="search_word">9. related documentation none</div><div class="display_word">9. Related Documentation None</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#外部メモリの利用">Use of External Memory</div><div class="search_word">use of external memory</div><div class="display_word">Use of External Memory</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product provides the following functions using external memory. sd card boot (firmware, config) the system can be started using a firmware file and config file from an sd card. applying sd card booting automatically (firmware, config) the firmware and config file used for sd card booting can be applied the next time the product is booted, even if the sd card is unavailable. firmware update this unit’s firmware can be updated by loading a firmware file from an sd card. saving and copying a config file the running-config that is currently running on the system can be saved to an sd card, and config files can be copied from the sd card to the unit’s flash rom or from the unit’s flash rom to the sd card. saving a log file by executing the save logging command you can back up the log file to an sd card. saving technical support information technical support information (the result of executing the show tech-support command) can be saved to an sd card. saving statistical information observations of resource information and traffic information are backed up regularly. this statistical information can be saved as a csv format file. backing up and restoring system information system information (including configurations) can be backed up to an sd card. backed up system information can be restored into the unit’s flash rom.</div><div class="display_word">1. Function Overview This product provides the following functions using external memory. SD card boot (firmware, config) The system can be started using a firmware file and config file from an SD card. Applying SD card booting automatically (firmware, config) The firmware and config file used for SD card booting can be applied the next time the product is booted, even if the SD card is unavailable. Firmware Update This unit’s firmware can be updated by loading a firmware file from an SD card. Saving and copying a config file The running-config that is currently running on the system can be saved to an SD card, and config files can be copied from the SD card to the unit’s flash ROM or from the unit’s flash ROM to the SD card. Saving a log file By executing the save logging command you can back up the log file to an SD card. Saving technical support information Technical support information (the result of executing the show tech-support command) can be saved to an SD card. Saving statistical information Observations of resource information and traffic information are backed up regularly. This statistical information can be saved as a CSV format file. Backing up and restoring system information System information (including configurations) can be backed up to an SD card. Backed up system information can be restored into the unit’s flash ROM.</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used none</div><div class="display_word">2. Definition of Terms Used None</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#利用可能な外部メモリ">3.1. External memory that can be used</div><div class="search_word">3.1. external memory that can be used requirements for external memory that can be used are as follows. card type: microsd card / microsdhc card file format: fat16/fat32</div><div class="display_word">3.1. External memory that can be used Requirements for external memory that can be used are as follows. Card type: microSD card / microSDHC card File format: FAT16/FAT32</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#フォルダ構成">3.2. Folder structure</div><div class="search_word">3.2. folder structure the sd card must contain the following folder structure. device name   +-- firmware          firmware file storage folder              |              |              +-- startup-config    startup config storage folder              |              |              +-- log               syslog storage folder              |              |              +-- techsupport       technical support information storage folder              |              |              +-- data              system-wide folder              |              |              +-- backup-system     system backup folder</div><div class="display_word">3.2. Folder structure The SD card must contain the following folder structure. Device name   +-- firmware          Firmware file storage folder              |              |              +-- startup-config    Startup config storage folder              |              |              +-- log               SYSLOG storage folder              |              |              +-- techsupport       Technical support information storage folder              |              |              +-- data              System-wide folder              |              |              +-- backup-system     System backup folder</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#sdカードのマウントアンマウント">3.3. Mounting and unmounting the SD card</div><div class="search_word">3.3. mounting and unmounting the sd card if the sd card is inserted when starting up or after startup, it is automatically mounted and becomes available. to prevent loss of files, execute the unmount sd command or execute the unmount operation from the web gui before removing the sd card. if the sd card is unmounted, it cannot be used. if you want to once again use the sd card after executing the unmount sd command, you must execute the following. remove and reinsert the sd card execute the mount sd command execute mount from the web gui</div><div class="display_word">3.3. Mounting and unmounting the SD card If the SD card is inserted when starting up or after startup, it is automatically mounted and becomes available. To prevent loss of files, execute the unmount sd command or execute the unmount operation from the Web GUI before removing the SD card. If the SD card is unmounted, it cannot be used. If you want to once again use the SD card after executing the unmount sd command, you must execute the following. Remove and reinsert the SD card Execute the mount sd command Execute mount from the Web GUI</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#sdカードブートファームウェアコンフィグ">3.4. SD card boot (firmware, config)</div><div class="search_word">3.4. sd card boot (firmware, config) the system can be started using a firmware file and config file from an sd card. in order to use sd card boot, the following conditions must be satisfied. sd card using a firmware file the sd card is connected when the system starts up. the following files exist in the sd card. /swx2310p/firmware/swx2310p.bin boot prioritize sd enable is set. boot prioritize sd enable is set in the factory default setting. sd card boot using a config file the sd card is connected when the system starts up. the following files exist in the sd card. /swx2310p/startup-config/config.txt startup-config select sd is set. startup-config select sd is set in the factory default setting. the file used for sd card booting can also be automatically saved to internal flash rom memory using the automatic sd card booting function (see automatic sd card booting ). you can use the show environment command to check whether sd card boot was successful. in the case of sd card boot using a firmware file, “startup firmware” will indicate “exec(sd).” in the case of sd card boot using a config file, “startup configuration” will indicate “config(sd).” in the case of sd card boot using a config file, executing the write and copy running-config startup-config commands will update the config file on the sd card. if sd card boot using a config file fails, startup config #0 is loaded. also, the following message is shown in the console and in syslog. loading config0 because can't read config in sd card.</div><div class="display_word">3.4. SD card boot (firmware, config) The system can be started using a firmware file and config file from an SD card. In order to use SD card boot, the following conditions must be satisfied. SD card using a firmware file The SD card is connected when the system starts up. The following files exist in the SD card. /swx2310p/firmware/swx2310p.bin boot prioritize sd enable is set. boot prioritize sd enable is set in the factory default setting. SD card boot using a config file The SD card is connected when the system starts up. The following files exist in the SD card. /swx2310p/startup-config/config.txt startup-config select sd is set. startup-config select sd is set in the factory default setting. The file used for SD card booting can also be automatically saved to internal flash ROM memory using the automatic SD card booting function (see Automatic SD card booting ). You can use the show environment command to check whether SD card boot was successful. In the case of SD card boot using a firmware file, “Startup Firmware” will indicate “exec(SD).” In the case of SD card boot using a config file, “Startup Configuration” will indicate “config(SD).” In the case of SD card boot using a config file, executing the write and copy running-config startup-config commands will update the config file on the SD card. If SD card boot using a config file fails, startup config #0 is loaded. Also, the following message is shown in the console and in SYSLOG. Loading config0 because can't read config in SD card.</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#sdカードブート自動適用ファームウェアコンフィグ">3.5. Applying SD card booting automatically (firmware, config)</div><div class="search_word">3.5. applying sd card booting automatically (firmware, config) the firmware and config used for sd card booting can be automatically saved to internal flash rom memory. this function can be used to easily install previously prepared firmware and config files in newly purchased devices (with factory settings).</div><div class="display_word">3.5. Applying SD card booting automatically (firmware, config) The firmware and config used for SD card booting can be automatically saved to internal flash ROM memory. This function can be used to easily install previously prepared firmware and config files in newly purchased devices (with factory settings).</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#自動適用のための事前準備">3.5.1. Preparations before using automatic saving</div><div class="search_word">3.5.1. preparations before using automatic saving in order to use this function, the following conditions must be satisfied. sd card booting is enabled by either of the following methods. (for details, see sd card booting .) the boot prioritize sd enable command is specified and firmware is installed with an appropriate path for sd cards. startup-config select sd is specified and the config file is installed with an appropriate path. the automatic sd card booting function is enabled. the automatic sd card booting function can be enabled using the boot auto-apply enable command. (this function is enabled in the factory default settings) the show environment command “boot auto-apply” display results can be used to confirm whether the function is enabled or disabled. prepare a file for automatically applying the automatic sd card booting function. if firmware is applied automatically prepare an auto-apply.txt file (empty text file) in the firmware folder in the sd card. /swx2310p/firmware/auto-apply.txt if a config file is applied automatically prepare an auto-apply.txt file (empty text file) in the startup-config folder in the sd card. /swx2310p/startup-config/auto-apply.txt</div><div class="display_word">3.5.1. Preparations before using automatic saving In order to use this function, the following conditions must be satisfied. SD card booting is enabled by either of the following methods. (For details, see SD card booting .) The boot prioritize sd enable command is specified and firmware is installed with an appropriate path for SD cards. startup-config select sd is specified and the config file is installed with an appropriate path. The automatic SD card booting function is enabled. The automatic SD card booting function can be enabled using the boot auto-apply enable command. (This function is enabled in the factory default settings) The show environment command “boot auto-apply” display results can be used to confirm whether the function is enabled or disabled. Prepare a file for automatically applying the automatic SD card booting function. If firmware is applied automatically Prepare an auto-apply.txt file (empty text file) in the firmware folder in the SD card. /swx2310p/firmware/auto-apply.txt If a config file is applied automatically Prepare an auto-apply.txt file (empty text file) in the startup-config folder in the SD card. /swx2310p/startup-config/auto-apply.txt</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#自動適用の手順">3.5.2. Procedure for automatic SD card booting</div><div class="search_word">3.5.2. procedure for automatic sd card booting use the following procedure to automatically apply sd card booting. implement preparations. (see preparations before using automatic saving ) insert the sd card and boot the network switch. when sd card booting is finished, automatically save the specified file in internal flash memory. (booting by automatic sd card booting takes longer than normal.) save the results from automatic sd card booting. (see automatic sd card booting results .) automatically unmount the sd card. automatically switch off the microsd led.</div><div class="display_word">3.5.2. Procedure for automatic SD card booting Use the following procedure to automatically apply SD card booting. Implement preparations. (See Preparations before using automatic saving ) Insert the SD card and boot the network switch. When SD card booting is finished, automatically save the specified file in internal flash memory. (Booting by automatic SD card booting takes longer than normal.) Save the results from automatic SD card booting. (See Automatic SD card booting results .) Automatically unmount the SD card. Automatically switch off the microSD LED.</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#自動適用の結果">3.5.3. Automatic SD card booting results</div><div class="search_word">3.5.3. automatic sd card booting results automatic sd card booting results are saved in the sd card. file name and directory path log /swx2310p/startup-config/auto-apply-result.txt serial: date and time: result /swx2310p/firmware/auto-apply-result.txt serial: date and time: result</div><div class="display_word">3.5.3. Automatic SD card booting results Automatic SD card booting results are saved in the SD card. File name and directory path Log /swx2310p/startup-config/auto-apply-result.txt Serial: Date and time: Result /swx2310p/firmware/auto-apply-result.txt Serial: Date and time: Result</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#コンフィグの適用先">3.5.4. Location for saving config file</div><div class="search_word">3.5.4. location for saving config file to change the config location to a user-specified config id, rename the auto-apply.txt file created, as indicated below. if no config location is specified, the default config id of 0 is applied. file name and directory path config id /swx2310p/startup-config/auto-apply.txt 0 /swx2310p/startup-config/auto-apply0.txt 0 /swx2310p/startup-config/auto-apply1.txt 1 /swx2310p/startup-config/auto-apply2.txt 2 /swx2310p/startup-config/auto-apply3.txt 3 /swx2310p/startup-config/auto-apply4.txt 4</div><div class="display_word">3.5.4. Location for saving config file To change the config location to a user-specified config ID, rename the auto-apply.txt file created, as indicated below. If no config location is specified, the default config ID of 0 is applied. File name and directory path Config ID /swx2310p/startup-config/auto-apply.txt 0 /swx2310p/startup-config/auto-apply0.txt 0 /swx2310p/startup-config/auto-apply1.txt 1 /swx2310p/startup-config/auto-apply2.txt 2 /swx2310p/startup-config/auto-apply3.txt 3 /swx2310p/startup-config/auto-apply4.txt 4</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#注意事項">3.5.5. Points of Caution</div><div class="search_word">3.5.5. points of caution note the following precautions when using this function. when the automatic sd card booting is successful, the function is automatically disabled. to avoid it being disabled automatically, the character string “keep” must be included at the top of the auto-apply.txt file created, as shown below. keep this function is disabled if the stack function is enabled. if the sd card does not contain an auto-apply.txt file, the function is disabled. if the device was not booted from the sd card, the automatic sd card booting function will fail even if an auto-apply.txt file exists. refer to sd card booting to confirm that the file in the sd card and the sd card booting function are enabled. if automatic sd card booting fails, only the sd card will be unmounted without automatically disabling the function. to prevent malfunction, be sure to delete the auto-apply.txt file if the automatic sd card booting function is not used.</div><div class="display_word">3.5.5. Points of Caution Note the following precautions when using this function. When the automatic SD card booting is successful, the function is automatically disabled. To avoid it being disabled automatically, the character string “keep” must be included at the top of the auto-apply.txt file created, as shown below. keep This function is disabled if the stack function is enabled. If the SD card does not contain an auto-apply.txt file, the function is disabled. If the device was not booted from the SD card, the automatic SD card booting function will fail even if an auto-apply.txt file exists. Refer to SD card booting to confirm that the file in the SD card and the SD card booting function are enabled. If automatic SD card booting fails, only the SD card will be unmounted without automatically disabling the function. To prevent malfunction, be sure to delete the auto-apply.txt file if the automatic SD card booting function is not used.</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#ファームウェア更新">3.6. Firmware Update</div><div class="search_word">3.6. firmware update this unit’s firmware can be updated by loading a firmware file from an sd card. in order to use this function, the following conditions apply. the following files exist in the sd card. /swx2310p/firmware/swx2310p.bin if the above file exists on the inserted sd card, executing the firmware-update sd execute command updates the firmware in flash rom using the firmware in the sd card. when the firmware-update sd execute command is executed, the user will be asked whether to maintain the mounted state of the sd card when the firmware file has finished loading. remove the sd card as necessary after it is unmounted. note that if the sd card is left inserted during the automatic reboot in conjunction with firmware update, the system will start up with the firmware file on the sd card. the firmware in member switches of a stack configuration can also be updated by executing the firmware-update sd execute command from the main switch.</div><div class="display_word">3.6. Firmware Update This unit’s firmware can be updated by loading a firmware file from an SD card. In order to use this function, the following conditions apply. The following files exist in the SD card. /swx2310p/firmware/swx2310p.bin If the above file exists on the inserted SD card, executing the firmware-update sd execute command updates the firmware in flash ROM using the firmware in the SD card. When the firmware-update sd execute command is executed, the user will be asked whether to maintain the mounted state of the SD card when the firmware file has finished loading. Remove the SD card as necessary after it is unmounted. Note that if the SD card is left inserted during the automatic reboot in conjunction with firmware update, the system will start up with the firmware file on the SD card. The firmware in member switches of a stack configuration can also be updated by executing the firmware-update sd execute command from the main switch.</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#コンフィグファイルの保存コピー">3.7. Saving and copying a config file</div><div class="search_word">3.7. saving and copying a config file the running-config that is currently running on the system can be saved to an sd card. (the copy running-config startup-config command and the write command) you can copy the config file from the sd card to internal flash rom, or from internal flash rom to the sd card. (the copy startup-config command) the contents of startup-config in the sd card can be erased or viewed. (the erase startup-config command and the show startup-config command) the following folder in the sd card is affected. /swx2310p/startup-config</div><div class="display_word">3.7. Saving and copying a config file The running-config that is currently running on the system can be saved to an SD card. (The copy running-config startup-config command and the write command) You can copy the config file from the SD card to internal flash ROM, or from internal flash ROM to the SD card. (The copy startup-config command) The contents of startup-config in the SD card can be erased or viewed. (The erase startup-config command and the show startup-config command) The following folder in the SD card is affected. /swx2310p/startup-config</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#ログファイルの保存">3.8. Saving a log file</div><div class="search_word">3.8. saving a log file by executing the save logging command you can back up the log file to an sd card. the logging backup sd command enables syslog backup to the sd card. if syslog backup to the sd card is enabled, executing the save logging command will save the following log file with its save date to the sd card. /swx2310p/log/yyyymmdd_log.txt *yyyymmdd=year month day the log files in the sd card cannot be viewed or erased.</div><div class="display_word">3.8. Saving a log file By executing the save logging command you can back up the log file to an SD card. The logging backup sd command enables SYSLOG backup to the SD card. If SYSLOG backup to the SD card is enabled, executing the save logging command will save the following log file with its save date to the SD card. /swx2310p/log/YYYYMMDD_log.txt *YYYYMMDD=year month day The log files in the SD card cannot be viewed or erased.</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#技術サポート情報の保存">3.9. Saving technical support information</div><div class="search_word">3.9. saving technical support information technical support information (the result of executing the show tech-support command) can be saved to an sd card. executing the copy tech-support sd command will save the following technical support information file with its save date to the sd card. /swx2310p/techsupport/yyyymmddhhmmss_techsupport.txt *yyyymmdd=year month day, hhmmss=hours minutes seconds the technical support information files in the sd card cannot be viewed or erased. if the copy tech-support sd command is executed from the main switch in a stack configuration, a file containing technical support information for member switches is saved.</div><div class="display_word">3.9. Saving technical support information Technical support information (the result of executing the show tech-support command) can be saved to an SD card. Executing the copy tech-support sd command will save the following technical support information file with its save date to the SD card. /swx2310p/techsupport/YYYYMMDDHHMMSS_techsupport.txt *YYYYMMDD=year month day, HHMMSS=hours minutes seconds The technical support information files in the SD card cannot be viewed or erased. If the copy tech-support sd command is executed from the main switch in a stack configuration, a file containing technical support information for member switches is saved.</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#統計情報の保存">3.10. Saving statistical information</div><div class="search_word">3.10. saving statistical information observations of resource information and traffic information are backed up regularly. to enable backup of statistical information to the sd card, you must make settings via the web gui in [administration]–[maintenance]–[summary data management]. this statistical information for the observed data can be saved via the web gui as a csv format file.</div><div class="display_word">3.10. Saving statistical information Observations of resource information and traffic information are backed up regularly. To enable backup of statistical information to the SD card, you must make settings via the Web GUI in [Administration]–[Maintenance]–[Summary data management]. This statistical information for the observed data can be saved via the Web GUI as a CSV format file.</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#システム情報のバックアップリストア">3.11. Backing up and restoring system information</div><div class="search_word">3.11. backing up and restoring system information this unit’s system information can be backed up to an sd card, and the backed up system information can be restored to a desired network switch. with an sd card connected to this unit, executing the backup system command will create a system information backup in the following folder. /swx2310p/backup-system if the file swx2310p.bin exists in the /swx2310p/firmware/ folder when backup is executed, it is backed up as a firmware file. to restore the backed up system information, connect the sd card containing the system information backup to the desired network switch, and execute the restore system command. if the firmware file was backed up, a firmware update is also performed using that file. when restore is completed, the system will restart. the system information backup contains the following. settings associated with the unit startup-config #0 - #4 and associated information setting values for the startup-config select command setting values for the boot prioritize sd command firmware file only if the specified folder of the sd card contained a firmware file when the backup was executed. for this reason, when replacing a unit due to malfunction or another reason, the replacement unit can be returned to the same condition as the original unit simply by restoring the backed up system information. do not edit or delete the backed up system information.</div><div class="display_word">3.11. Backing up and restoring system information This unit’s system information can be backed up to an SD card, and the backed up system information can be restored to a desired network switch. With an SD card connected to this unit, executing the backup system command will create a system information backup in the following folder. /swx2310p/backup-system If the file swx2310p.bin exists in the /swx2310p/firmware/ folder when backup is executed, it is backed up as a firmware file. To restore the backed up system information, connect the SD card containing the system information backup to the desired network switch, and execute the restore system command. If the firmware file was backed up, a firmware update is also performed using that file. When restore is completed, the system will restart. The system information backup contains the following. Settings associated with the unit startup-config #0 - #4 and associated information Setting values for the startup-config select command Setting values for the boot prioritize sd command Firmware file Only if the specified folder of the SD card contained a firmware file when the backup was executed. For this reason, when replacing a unit due to malfunction or another reason, the replacement unit can be returned to the same condition as the original unit simply by restoring the backed up system information. Do not edit or delete the backed up system information.</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#関連コマンド一覧">4. List of related commands</div><div class="search_word">4. list of related commands related commands are indicated below. for details, refer to the command reference. operations operating commands mount sd card mount sd unmount sd card unmount sd set sd card backup of log logging backup sd back up log save logging saving technical support information copy tech-support sd save running config copy running-config startup-config save running config write copy startup config copy startup-config erase startup config erase startup-config show startup config show startup-config back up system information backup system restore system information restore system</div><div class="display_word">4. List of related commands Related commands are indicated below. For details, refer to the Command Reference. Operations Operating commands Mount SD card mount sd Unmount SD card unmount sd Set SD card backup of log logging backup sd Back up log save logging Saving technical support information copy tech-support sd Save running config copy running-config startup-config Save running config write Copy startup config copy startup-config Erase startup config erase startup-config Show startup config show startup-config Back up system information backup system Restore system information restore system</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#sdカードのアンマウント">5.1. Unmount SD card</div><div class="search_word">5.1. unmount sd card unmount the sd card. yamaha>unmount sd</div><div class="display_word">5.1. Unmount SD card Unmount the SD card. Yamaha>unmount sd</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#sdカードのマウント">5.2. Mount SD card</div><div class="search_word">5.2. mount sd card mount the sd card. yamaha>mount sd</div><div class="display_word">5.2. Mount SD card Mount the SD card. Yamaha>mount sd</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#ログファイルのバックアップ">5.3. Back up log file</div><div class="search_word">5.3. back up log file by executing the save logging command you can back up the log file to the sd card as well. yamaha(config)#logging backup sd enable (1) yamaha(config)#exityamaha#save logging (2) 1 enable sd card backup of logs 2 back up logs</div><div class="display_word">5.3. Back up log file By executing the save logging command you can back up the log file to the SD card as well. Yamaha(config)#logging backup sd enable (1) Yamaha(config)#exitYamaha#save logging (2) 1 Enable SD card backup of logs 2 Back up logs</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#技術サポート情報の保存">5.4. Saving technical support information</div><div class="search_word">5.4. saving technical support information save technical support information. yamaha#copy tech-support sd</div><div class="display_word">5.4. Saving technical support information Save technical support information. Yamaha#copy tech-support sd</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution none</div><div class="display_word">6. Points of Caution None</div></div><div id="oam_oam_sd"><div class="search_title" docfname="oam_oam_sd" doctitle="Use" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation config management syslog firmware update performance observations</div><div class="display_word">7. Related Documentation Config Management SYSLOG Firmware Update Performance Observations</div></div><div id="oam_oam_sflow"><div class="search_title" docfname="oam_oam_sflow" doctitle="sFlow" link="#sflow">sFlow</div><div class="search_word">sflow</div><div class="display_word">sFlow</div></div><div id="oam_oam_sflow"><div class="search_title" docfname="oam_oam_sflow" doctitle="sFlow" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview sflow is technology for monitoring traffic. rather than monitoring all packets in traffic flow, sflow can monitor traffic information statistically based on sampling only a specific percent of packets. sflow monitoring is configured with sflow agents and sflow collectors. sflow agent monitors traffic by sampling and creates sflow information. sends sflow datagrams, which store sflow information, to the sflow collector. sflow collector receives sflow datagrams, which store sflow information, sent from the sflow agent. collects and analyzes the sflow information from datagrams indicated above. sflow agents can perform two types of sflow sampling. either one or both of the following types of information is stored in sflow datagrams. packet flow sampling this samples a specified percent of packets sent and received at the interface. counter sampling this samples data from the interface counter at regular intervals. this product functions as an sflow agent. the sflow collector must be supplied separately. this product is compatible with sflow version 5 ( https://sflow.org/sflow_version_5.txt ).</div><div class="display_word">1. Function Overview sFlow is technology for monitoring traffic. Rather than monitoring all packets in traffic flow, sFlow can monitor traffic information statistically based on sampling only a specific percent of packets. sFlow monitoring is configured with sFlow agents and sFlow collectors. sFlow agent Monitors traffic by sampling and creates sFlow information. Sends sFlow datagrams, which store sFlow information, to the sFlow collector. sFlow collector Receives sFlow datagrams, which store sFlow information, sent from the sFlow agent. Collects and analyzes the sFlow information from datagrams indicated above. sFlow agents can perform two types of sFlow sampling. Either one or both of the following types of information is stored in sFlow datagrams. Packet flow sampling This samples a specified percent of packets sent and received at the interface. Counter sampling This samples data from the interface counter at regular intervals. This product functions as an sFlow agent. The sFlow collector must be supplied separately. This product is compatible with sFlow Version 5 ( https://sflow.org/sflow_version_5.txt ).</div></div><div id="oam_oam_sflow"><div class="search_title" docfname="oam_oam_sflow" doctitle="sFlow" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used sflow agent after monitoring traffic by sampling and creating sflow information, the sflow agent sends the sflow information to an sflow collector. this product functions as an sflow agent. sflow collector the sflow collector collects and analyzes the sflow information received from sflow agents. packet flow sampling this sampling method samples a specific percent of the total packets sent and received at the interface. counter sampling this sampling method obtains interface counter values at regular intervals. sflow datagram sflow datagrams are udp packets that store the information sflow agents obtain by sampling. they are sent from sflow agents to sflow collectors.</div><div class="display_word">2. Definition of Terms Used sFlow agent After monitoring traffic by sampling and creating sFlow information, the sFlow agent sends the sFlow information to an sFlow collector. This product functions as an sFlow agent. sFlow collector The sFlow collector collects and analyzes the sFlow information received from sFlow agents. Packet flow sampling This sampling method samples a specific percent of the total packets sent and received at the interface. Counter sampling This sampling method obtains interface counter values at regular intervals. sFlow datagram sFlow datagrams are UDP packets that store the information sFlow agents obtain by sampling. They are sent from sFlow agents to sFlow collectors.</div></div><div id="oam_oam_sflow"><div class="search_title" docfname="oam_oam_sflow" doctitle="sFlow" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details the operating specifications for sflow functionality are indicated below. use the sflow enable command to enable sflow functionality. the default setting is sflow disable (disabled). use the sflow agent command to specify the following sflow agent settings. ip address ipv4 address ipv6 address the ip address specified using this command is used in the sflow header of sflow datagrams. no setting is specified in default settings. use the sflow collector command to specify the following sflow collector settings. ip address ipv4 address ipv6 address udp port number the default value is 6343. sflow datagrams are sent to the ip address and udp port number specified using this command. no setting is specified in default settings. only one sflow collector can be specified for this product. sampling is not started unless this command is specified. packet flow sampling operations are described below. the sflow sampling-rate command is used to specify the sampling rate at physical ports and sample packet flow at the corresponding ports. no setting is specified in default settings. the sampling rate is specified as the number of packets from which one packet is sampled. for example, for a sampling rate setting of 1000, one packet is sampled from each 1000 packets that are sent or received at the corresponding port. sent and received packets are sampled separately. packets are individually sampled at each port. use the sflow max-header-size command to specify the maximum header size value for ethernet frames being sampled during packet flow sampling. the default value is 128. specifying the sampling rate using the sflow sampling-rate command results in the following actions. the new sampling rate will be applied after sampling at the previous sampling rate setting is finished. counter sampling actions are described below. if the sflow polling-interval command is used to specify the polling interval for a physical port, counter sampling is performed at that port. no setting is specified in default settings. the polling interval setting specifies the number of seconds between counter sampling. for example, if a polling interval value of 30 is specified, counter information for the corresponding port is sampled once every 30 seconds. packets are individually sampled at each port. this product sends the following types of sflow datagrams. use the sflow collector max-datagram-size command to specify the maximum sflow datagram size. sflow datagrams from packet flow sampling store the following information for sflow version 5. raw packet header(enterprise = 0, format = 1) sflow datagrams from counter sampling store the following information for sflow version 5. generic interface counters(enterprise = 0, format = 1) ethernet interface counters(enterprise = 0, format = 2) disabled counters include a maximum counter value. (for 32-bit counters, sflow datagrams store the “0xffffffff” value.)</div><div class="display_word">3. Function Details The operating specifications for sFlow functionality are indicated below. Use the sflow enable command to enable sFlow functionality. The default setting is sflow disable (disabled). Use the sflow agent command to specify the following sFlow agent settings. IP address IPv4 address IPv6 address The IP address specified using this command is used in the sFlow header of sFlow datagrams. No setting is specified in default settings. Use the sflow collector command to specify the following sFlow collector settings. IP address IPv4 address IPv6 address UDP port number The default value is 6343. sFlow datagrams are sent to the IP address and UDP port number specified using this command. No setting is specified in default settings. Only one sFlow collector can be specified for this product. Sampling is not started unless this command is specified. Packet flow sampling operations are described below. The sflow sampling-rate command is used to specify the sampling rate at physical ports and sample packet flow at the corresponding ports. No setting is specified in default settings. The sampling rate is specified as the number of packets from which one packet is sampled. For example, for a sampling rate setting of 1000, one packet is sampled from each 1000 packets that are sent or received at the corresponding port. Sent and received packets are sampled separately. Packets are individually sampled at each port. Use the sflow max-header-size command to specify the maximum header size value for Ethernet frames being sampled during packet flow sampling. The default value is 128. Specifying the sampling rate using the sflow sampling-rate command results in the following actions. The new sampling rate will be applied after sampling at the previous sampling rate setting is finished. Counter sampling actions are described below. If the sflow polling-interval command is used to specify the polling interval for a physical port, counter sampling is performed at that port. No setting is specified in default settings. The polling interval setting specifies the number of seconds between counter sampling. For example, if a polling interval value of 30 is specified, counter information for the corresponding port is sampled once every 30 seconds. Packets are individually sampled at each port. This product sends the following types of sFlow datagrams. Use the sflow collector max-datagram-size command to specify the maximum sFlow datagram size. sFlow datagrams from packet flow sampling store the following information for sFlow version 5. Raw Packet Header(enterprise = 0, format = 1) sFlow datagrams from counter sampling store the following information for sFlow version 5. Generic Interface Counters(enterprise = 0, format = 1) Ethernet Interface Counters(enterprise = 0, format = 2) Disabled counters include a maximum counter value. (For 32-bit counters, sFlow datagrams store the “0xFFFFFFFF” value.)</div></div><div id="oam_oam_sflow"><div class="search_title" docfname="oam_oam_sflow" doctitle="sFlow" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands enables sflow functionality sflow sets sflow agents sflow agent sets sflow collectors sflow collector sets the maximum sflow datagram size sflow collector max-datagram-size sets the sampling rate for packet flow sampling sflow sampling-rate sets the maximum ethernet frame header size for packet flow sampling sflow max-header-size sets the polling interval for counter sampling sflow polling-interval displays the sflow status show sflow displays the sflow sampling information show sflow sampling</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Enables sFlow functionality sflow Sets sFlow agents sflow agent Sets sFlow collectors sflow collector Sets the maximum sFlow datagram size sflow collector max-datagram-size Sets the sampling rate for packet flow sampling sflow sampling-rate Sets the maximum Ethernet frame header size for packet flow sampling sflow max-header-size Sets the polling interval for counter sampling sflow polling-interval Displays the sFlow status show sflow Displays the sFlow sampling information show sflow sampling</div></div><div id="oam_oam_sflow"><div class="search_title" docfname="oam_oam_sflow" doctitle="sFlow" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution the following samples packets by sflow packet flow sampling and counter sampling at port 1.1. set the ip address for the sflow agent. yamaha(config)#sflow agent 192.168.100.240 set the ip address for the sflow collector. yamaha(config)#sflow collector 192.168.100.2 set the sampling rate for packet flow sampling at the applicable port. yamaha(config)#interface port1.1yamaha(config-if)#sflow sampling-rate 1000 set the polling interval for counter sampling at the applicable port. yamaha(config)#interface port1.1yamaha(config-if)#sflow polling-interval 30 enable sflow. yamaha(config)#sflow enable</div><div class="display_word">5. Examples of Command Execution The following samples packets by sFlow packet flow sampling and counter sampling at port 1.1. Set the IP address for the sFlow agent. Yamaha(config)#sflow agent 192.168.100.240 Set the IP address for the sFlow collector. Yamaha(config)#sflow collector 192.168.100.2 Set the sampling rate for packet flow sampling at the applicable port. Yamaha(config)#interface port1.1Yamaha(config-if)#sflow sampling-rate 1000 Set the polling interval for counter sampling at the applicable port. Yamaha(config)#interface port1.1Yamaha(config-if)#sflow polling-interval 30 Enable sFlow. Yamaha(config)#sflow enable</div></div><div id="oam_oam_sflow"><div class="search_title" docfname="oam_oam_sflow" doctitle="sFlow" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution sflow is not compatible with management information bases (mib). in stack configurations, the show sflow sampling command does not synchronize sampling information between the main and member switches in the stack. in environments with high communication volumes, the following might occur if a small value is specified for the sflow sampling-rate command. in such cases, consider changing the sflow sampling-rate command value. higher cpu usage rate values are displayed using the show environment command. the “sflow drop sampling count” value displayed by the show sflow command is included in count values. if that value is counted, packets sampled by packet flow sampling dropped because they cannot be processed due to the high load. (* the sampling is actually dropped in this case, not the packets themselves.) since the values vary depending on the number of sampling-target ports and whether or not other functions are operating, recommended values cannot simply be suggested. however, as a guideline, the sflow sampling-rate command values that are unlikely to cause sflow drops even when all ports are in use are described below. when using a 1g interface …​ 2000 (1/2000) when using a 10g interface …​ 10000 (1/10000)</div><div class="display_word">6. Points of Caution sFlow is not compatible with management information bases (MIB). In stack configurations, the show sflow sampling command does not synchronize sampling information between the main and member switches in the stack. In environments with high communication volumes, the following might occur if a small value is specified for the sflow sampling-rate command. In such cases, consider changing the sflow sampling-rate command value. Higher CPU usage rate values are displayed using the show environment command. The “sFlow Drop Sampling Count” value displayed by the show sflow command is included in count values. If that value is counted, packets sampled by packet flow sampling dropped because they cannot be processed due to the high load. (* The sampling is actually dropped in this case, not the packets themselves.) Since the values vary depending on the number of sampling-target ports and whether or not other functions are operating, recommended values cannot simply be suggested. However, as a guideline, the sflow sampling-rate command values that are unlikely to cause sFlow drops even when all ports are in use are described below. When using a 1G interface …​ 2000 (1/2000) When using a 10G interface …​ 10000 (1/10000)</div></div><div id="oam_oam_sflow"><div class="search_title" docfname="oam_oam_sflow" doctitle="sFlow" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation none</div><div class="display_word">7. Related Documentation None</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#snmp">SNMP</div><div class="search_word">snmp</div><div class="display_word">SNMP</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview setting snmp (simple network management protocol) makes it possible to monitor and change network management information for snmp management software. in this instance, this product will operate as an snmp agent. this product supports communication using snmpv1, snmpv2c, and snmpv3. in terms of management information bases (mib), it supports rfc1213 (mib-ii) and private mibs (yamaha switches). snmpv1 and snmpv2 protocols send notification of the group name (referred to as a “community”) to recipients and only communicate between hosts that belong to that same community. in that case, different community names can be specified for two access modes, either the read-only or read-write mode. in this way, community names function as a kind of password, but they carry inherent security risks because they must be sent over a network using plain text. the use of snmpv3 is recommended when more secure communications are required. snmpv3 offers communication content authentication and encryption. snmpv3 does away with the concept of community and instead uses security models called “usm” (user-based security model) and “vacm” (view-based access control model). these models provide a higher level of security. snmp messages that notify the status of this product are called “traps”. this product transmits standard snmp traps. in snmpv1, trap requests that do not ask for an answer with the confirmation of receipt from the recipient are specified as the notification message format. however, with snmpv2c and snmpv3, either an “inform” request asking for an answer from the recipient, or a trap request can be selected. since this product does not specifically specify a default community name value for read-only and transmission traps used for snmpv1 and snmpv2c protocols, be sure to specify an appropriate community name. however, as described above, community names are sent over the network in plain text, so be careful to never use a login password or administrator password as the community name. by default, no access is possible in each snmp version. the transmission host for the trap is not set, so traps will not be sent anywhere. this product can restrict access to the snmp server. specifying access restrictions can restrict access from unintended hosts.</div><div class="display_word">1. Function Overview Setting SNMP (Simple Network Management Protocol) makes it possible to monitor and change network management information for SNMP management software. In this instance, this product will operate as an SNMP agent. This product supports communication using SNMPv1, SNMPv2c, and SNMPv3. In terms of management information bases (MIB), it supports RFC1213 (MIB-II) and private MIBs (Yamaha switches). SNMPv1 and SNMPv2 protocols send notification of the group name (referred to as a “community”) to recipients and only communicate between hosts that belong to that same community. In that case, different community names can be specified for two access modes, either the read-only or read-write mode. In this way, community names function as a kind of password, but they carry inherent security risks because they must be sent over a network using plain text. The use of SNMPv3 is recommended when more secure communications are required. SNMPv3 offers communication content authentication and encryption. SNMPv3 does away with the concept of community and instead uses security models called “USM” (User-based Security Model) and “VACM” (View-based Access Control Model). These models provide a higher level of security. SNMP messages that notify the status of this product are called “traps”. This product transmits standard SNMP traps. In SNMPv1, trap requests that do not ask for an answer with the confirmation of receipt from the recipient are specified as the notification message format. However, with SNMPv2c and SNMPv3, either an “inform” request asking for an answer from the recipient, or a trap request can be selected. Since this product does not specifically specify a default community name value for read-only and transmission traps used for SNMPv1 and SNMPv2c protocols, be sure to specify an appropriate community name. However, as described above, community names are sent over the network in plain text, so be careful to never use a login password or administrator password as the community name. By default, no access is possible in each SNMP version. The transmission host for the trap is not set, so traps will not be sent anywhere. This product can restrict access to the SNMP server. Specifying access restrictions can restrict access from unintended hosts.</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used none</div><div class="display_word">2. Definition of Terms Used None</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details the main characteristics of each snmp version and the router setting policies are explained below. for specific examples of settings, see “examples of command execution” below.</div><div class="display_word">3. Function Details The main characteristics of each SNMP version and the router setting policies are explained below. For specific examples of settings, see “Examples of Command Execution” below.</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#snmpv1">3.1. SNMPv1</div><div class="search_word">3.1. snmpv1 this is authentication between the snmp manager and agent by using community names. the controlling device (this product) is divided and managed by zones called “communities”. accessing the mib objects community names specified using the snmp-server community command are used to permit access. access is possible from a vlan interface whose ip address has been specified. snmp traps the status of switches can be sent to hosts specified using the snmp-server host command. the snmp-server enable trap command is used to specify the kind of trap to send. the snmp-server startup-trap-delay command is used to specify when to send the trap during startup.</div><div class="display_word">3.1. SNMPv1 This is authentication between the SNMP manager and agent by using community names. The controlling device (this product) is divided and managed by zones called “communities”. Accessing the MIB objects Community names specified using the snmp-server community command are used to permit access. Access is possible from a VLAN interface whose IP address has been specified. SNMP traps The status of switches can be sent to hosts specified using the snmp-server host command. The snmp-server enable trap command is used to specify the kind of trap to send. The snmp-server startup-trap-delay command is used to specify when to send the trap during startup.</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#snmpv2c">3.2. SNMPv2c</div><div class="search_word">3.2. snmpv2c as with snmpv1, community names are used for authentication between the snmp manager and agents. the snmp-server community command is used to specify the community names used to access switches by snmpv2c. the “getbulk” and “inform” requests are also now supported from this version. these requests are used to efficiently retrieve multiple mib objects, and to confirm replies to notification packets sent from this product. accessing the mib objects community names specified using the snmp-server community command are used to permit access. access is possible from a vlan interface whose ip address has been specified. snmp traps the status of switches can be sent to hosts specified using the snmp-server host command. also, the settings of this command can be used to select whether the transmitted message format is a trap or inform request. inform requests are used to request confirmation of reply to the recipient. the snmp-server startup-trap-delay command is used to specify when to send the trap during startup.</div><div class="display_word">3.2. SNMPv2c As with SNMPv1, community names are used for authentication between the SNMP manager and agents. The snmp-server community command is used to specify the community names used to access switches by SNMPv2c. The “GetBulk” and “Inform” requests are also now supported from this version. These requests are used to efficiently retrieve multiple MIB objects, and to confirm replies to notification packets sent from this product. Accessing the MIB objects Community names specified using the snmp-server community command are used to permit access. Access is possible from a VLAN interface whose IP address has been specified. SNMP traps The status of switches can be sent to hosts specified using the snmp-server host command. Also, the settings of this command can be used to select whether the transmitted message format is a trap or inform request. Inform requests are used to request confirmation of reply to the recipient. The snmp-server startup-trap-delay command is used to specify when to send the trap during startup.</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#snmpv3">3.3. SNMPv3</div><div class="search_word">3.3. snmpv3 in addition to all of the functions offered in snmpv2, snmpv3 offers more robust security functions. snmpv3 can authenticate and encrypt snmp packets sent across the network to protect packets from eavesdropping, spoofing, falsification, replay attacks, and other risks and achieve security levels not possible with snmpv1 or snmpv2c functionality, such as community names or snmp manager ip addresses. security snmpv3 offers the following security functions. usm (user-based security model) usm is a model for maintaining security at the message level. it offers authentication and encryption based on shared key cryptography and prevents falsification of message streams. security level the security level can be specified using the parameter settings for the group to which users belong. security levels are classified based on a combination of authentication and encryption, as indicated below. noauthnopriv : no authentication or encryption authnopriv : authentication only authpriv : authentication and encryption user authentication for authentication, hmac is used in the procedure to authenticate the integrity (whether data has been falsified or not) and the source. a hash is used in the authentication key to confirm whether the message has been falsified, and whether the sender is the user themselves. both hmac-md5-96 and hmac-sha-96 are supported as hash algorithms. encryption with snmpv3, snmp messages are encrypted for the purpose of preventing leakage of managed information. both the des-cbc and aes128-cfb encryption schemes are supported. the snmp-server user command can be used to specify usernames, corresponding group names, user authentication methods, encryption methods, and passwords. the necessary authentication and encryption settings can be made according to the security level specified in the group settings. vacm (view-based access control model) vacm is a model for controlling access to snmp messages. group with vacm, the access policies mentioned below are defined per group, not per user. use the snmp-server user command with the optional “group” setting to specify user group affiliation. the mib views set here that are accessible to the specified groups can be configured. mib view with snmpv3, a collection of accessible mib objects can be defined for each group. when defined, the collection of mib objects is called the “mib view”. the “mib view” is expressed as a collected view sub-tree that shows the object id tree. use the snmp-server view command to specify the mib view. whether the mib view should be included or excluded in each view sub-tree can be selected. access policy with vacm, set the mib view that will permit reading and writing for each group. use the snmp-server group command to set the group name, security level, and mib view. the mib view is the mib view specified using the snmp-server view command. snmp traps the status of switches can be sent to hosts specified using the snmp-server host command. in order to transmit a trap, the snmp-server user command must first be used to configure the user. also, the settings of this command can be used to select whether the transmitted message format is a trap or inform request. inform requests are used to request confirmation of reply to the recipient. the snmp-server startup-trap-delay command is used to specify when to send the trap during startup.</div><div class="display_word">3.3. SNMPv3 In addition to all of the functions offered in SNMPv2, SNMPv3 offers more robust security functions. SNMPv3 can authenticate and encrypt SNMP packets sent across the network to protect packets from eavesdropping, spoofing, falsification, replay attacks, and other risks and achieve security levels not possible with SNMPv1 or SNMPv2c functionality, such as community names or SNMP manager IP addresses. Security SNMPv3 offers the following security functions. USM (User-based Security Model) USM is a model for maintaining security at the message level. It offers authentication and encryption based on shared key cryptography and prevents falsification of message streams. Security level The security level can be specified using the parameter settings for the group to which users belong. Security levels are classified based on a combination of authentication and encryption, as indicated below. noAuthNoPriv : No authentication or encryption AuthNoPriv : Authentication only AuthPriv : authentication and encryption User authentication For authentication, HMAC is used in the procedure to authenticate the integrity (whether data has been falsified or not) and the source. A hash is used in the authentication key to confirm whether the message has been falsified, and whether the sender is the user themselves. Both HMAC-MD5-96 and HMAC-SHA-96 are supported as hash algorithms. Encryption With SNMPv3, SNMP messages are encrypted for the purpose of preventing leakage of managed information. Both the DES-CBC and AES128-CFB encryption schemes are supported. The snmp-server user command can be used to specify usernames, corresponding group names, user authentication methods, encryption methods, and passwords. The necessary authentication and encryption settings can be made according to the security level specified in the group settings. VACM (View-based Access Control Model) VACM is a model for controlling access to SNMP messages. Group With VACM, the access policies mentioned below are defined per group, not per user. Use the snmp-server user command with the optional “group” setting to specify user group affiliation. The MIB views set here that are accessible to the specified groups can be configured. MIB view With SNMPv3, a collection of accessible MIB objects can be defined for each group. When defined, the collection of MIB objects is called the “MIB view”. The “MIB view” is expressed as a collected view sub-tree that shows the object ID tree. Use the snmp-server view command to specify the MIB view. Whether the MIB view should be included or excluded in each view sub-tree can be selected. Access policy With VACM, set the MIB view that will permit reading and writing for each group. Use the snmp-server group command to set the group name, security level, and MIB view. The MIB view is the MIB view specified using the snmp-server view command. SNMP traps The status of switches can be sent to hosts specified using the snmp-server host command. In order to transmit a trap, the snmp-server user command must first be used to configure the user. Also, the settings of this command can be used to select whether the transmitted message format is a trap or inform request. Inform requests are used to request confirmation of reply to the recipient. The snmp-server startup-trap-delay command is used to specify when to send the trap during startup.</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#snmpサーバーへのアクセス制限">3.4. Restricting SNMP server access</div><div class="search_word">3.4. restricting snmp server access hosts able to access the product’s snmp server can be specified using the snmp-server access command. access from unintended hosts can be restricted by only allowing access from the intended snmp manager. default settings accept access from all hosts. specify access restrictions based on the operating environment. for more information about access restrictions, refer to remote access control .</div><div class="display_word">3.4. Restricting SNMP server access Hosts able to access the product’s SNMP server can be specified using the snmp-server access command. Access from unintended hosts can be restricted by only allowing access from the intended SNMP manager. Default settings accept access from all hosts. Specify access restrictions based on the operating environment. For more information about access restrictions, refer to Remote Access Control .</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#プライベートmib">3.5. Private MIBs</div><div class="search_word">3.5. private mibs this product supports yamahasw, which is a proprietary private mib for switch management. this private mib allows the obtaining of information for yamaha’s proprietary functions, and for more detailed information about the switch. for information about supported private mibs and how to obtain private mibs, refer to snmp mib reference .</div><div class="display_word">3.5. Private MIBs This product supports yamahaSW, which is a proprietary private MIB for switch management. This private MIB allows the obtaining of information for Yamaha’s proprietary functions, and for more detailed information about the switch. For information about supported private MIBs and how to obtain private MIBs, refer to SNMP MIB Reference .</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands set host that receives snmp notifications snmp-server host set how long to wait for notification messages to be transmitted when starting up the system. snmp-server startup-trap-delay set notification type to transmit snmp-server enable trap set system contact snmp-server contact set system location snmp-server location set snmp community snmp-server community set snmp view snmp-server view set snmp group snmp-server group set snmp user snmp-server user specify snmp server access settings snmp-server access show snmp community information show snmp community show snmp view settings show snmp view show snmp group settings show snmp group show snmp user settings show snmp user</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Set host that receives SNMP notifications snmp-server host Set how long to wait for notification messages to be transmitted when starting up the system. snmp-server startup-trap-delay Set notification type to transmit snmp-server enable trap Set system contact snmp-server contact Set system location snmp-server location Set SNMP community snmp-server community Set SNMP view snmp-server view Set SNMP group snmp-server group Set SNMP user snmp-server user Specify SNMP server access settings snmp-server access Show SNMP community information show snmp community Show SNMP view settings show snmp view Show SNMP group settings show snmp group Show SNMP user settings show snmp user</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#snmpv1-設定例">5.1. SNMPv1 setting example</div><div class="search_word">5.1. snmpv1 setting example this example makes snmpv1-based network monitoring possible under the following conditions. set the read-only community name “public”. set the trap destination as “192.168.100.11”, and set trap community name to “snmptrapname”. hosts that can access communities named “public” are restricted to only 192.168.100.0/24. yamaha(config)# snmp-server community public ro                  　          ... 1yamaha(config)# snmp-server host 192.168.100.11 traps version 1 snmptrapname ... 2yamaha(config)# snmp-server access permit 192.168.100.0/24 community public  ... 3</div><div class="display_word">5.1. SNMPv1 setting example This example makes SNMPv1-based network monitoring possible under the following conditions. Set the read-only community name “public”. Set the trap destination as “192.168.100.11”, and set trap community name to “snmptrapname”. Hosts that can access communities named “public” are restricted to only 192.168.100.0/24. Yamaha(config)# snmp-server community public ro                  　          ... 1Yamaha(config)# snmp-server host 192.168.100.11 traps version 1 snmptrapname ... 2Yamaha(config)# snmp-server access permit 192.168.100.0/24 community public  ... 3</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#snmpv2c-設定例">5.2. SNMPv2c setting example</div><div class="search_word">5.2. snmpv2c setting example this example makes snmpv2c-based network monitoring possible under the following conditions. set the readable/writable community name as “private”. specify the notification message destination as “192.168.100.12”, the notification type as “inform” request format, and the notification destination community name as “snmpinformsname”. hosts that can access communities named “private” are restricted to only 192.168.100.12. yamaha(config)# snmp-server community private rw                  　               ...1yamaha(config)# snmp-server host 192.168.100.12 informs version 2c snmpinformsname ...2yamaha(config)# snmp-server access permit 192.168.100.12 community private         ...3</div><div class="display_word">5.2. SNMPv2c setting example This example makes SNMPv2c-based network monitoring possible under the following conditions. Set the readable/writable community name as “private”. Specify the notification message destination as “192.168.100.12”, the notification type as “inform” request format, and the notification destination community name as “snmpinformsname”. Hosts that can access communities named “private” are restricted to only 192.168.100.12. Yamaha(config)# snmp-server community private rw                  　               ...1Yamaha(config)# snmp-server host 192.168.100.12 informs version 2c snmpinformsname ...2Yamaha(config)# snmp-server access permit 192.168.100.12 community private         ...3</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#snmpv3-設定例">5.3. SNMPv3 setting example</div><div class="search_word">5.3. snmpv3 setting example this example makes snmpv3-based network monitoring possible under the following conditions. specify the view that shows the internet node (1.3.6.1) and below as “most”. specify the view that shows the mib-2 node (1.3.6.1.2.1) and below as “standard”. create the user group “admins” and assign full access rights to the “most” view for all users in the “admins” group. create the user group “users” and assign read-only access rights for the “standard” view to users in the “users” group. create an “admin1” user that belongs to the “admins” group. set the password to “passwd1234”, using the “hmac-sha-96” authentication algorithm. set the encryption password to “passwd1234”, using the “aes128-cfb” encryption algorithm. create an “user1” user that belongs to the “users” group. set the password to “passwd5678”, using the “hmac-sha-96” authentication algorithm. send notifications in trap format (without response confirmation) to 192.168.10.3. send notifications in inform request format to 192.168.20.3. yamaha(config)# snmp-server view most 1.3.6.1 include                                  ... 1yamaha(config)# snmp-server view standard 1.3.6.1.2.1 include                          ... 2yamaha(config)# snmp-server group admins priv read most write most                     ... 3yamaha(config)# snmp-server group users auth read standard                             ... 4yamaha(config)# snmp-server user admin1 admins auth sha passwd1234 priv aes passwd1234 ... 5yamaha(config)# snmp-server user user1 users auth sha passwd5678                       ... 6yamaha(config)# snmp-server host 192.168.10.13 traps version 3 priv admin1             ... 7yamaha(config)# snmp-server host 192.168.20.13 informs version 3 priv admin1           ... 8</div><div class="display_word">5.3. SNMPv3 setting example This example makes SNMPv3-based network monitoring possible under the following conditions. Specify the view that shows the internet node (1.3.6.1) and below as “most”. Specify the view that shows the mib-2 node (1.3.6.1.2.1) and below as “standard”. Create the user group “admins” and assign full access rights to the “most” view for all users in the “admins” group. Create the user group “users” and assign read-only access rights for the “standard” view to users in the “users” group. Create an “admin1” user that belongs to the “admins” group. Set the password to “passwd1234”, using the “HMAC-SHA-96” authentication algorithm. Set the encryption password to “passwd1234”, using the “AES128-CFB” encryption algorithm. Create an “user1” user that belongs to the “users” group. Set the password to “passwd5678”, using the “HMAC-SHA-96” authentication algorithm. Send notifications in trap format (without response confirmation) to 192.168.10.3. Send notifications in inform request format to 192.168.20.3. Yamaha(config)# snmp-server view most 1.3.6.1 include                                  ... 1Yamaha(config)# snmp-server view standard 1.3.6.1.2.1 include                          ... 2Yamaha(config)# snmp-server group admins priv read most write most                     ... 3Yamaha(config)# snmp-server group users auth read standard                             ... 4Yamaha(config)# snmp-server user admin1 admins auth sha passwd1234 priv aes passwd1234 ... 5Yamaha(config)# snmp-server user user1 users auth sha passwd5678                       ... 6Yamaha(config)# snmp-server host 192.168.10.13 traps version 3 priv admin1             ... 7Yamaha(config)# snmp-server host 192.168.20.13 informs version 3 priv admin1           ... 8</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution check the snmp version that can be used with the snmp manager beforehand. it is necessary to configure this product in accordance with the snmp version that will be used. this product is not compatible with the following functions related to snmpv3. proxy function access to mib objects after the snmpv2 subtree (1.3.6.1.6). changing snmpv3-related settings via snmp is also not supported. character string specifications for the community name, username, password, and group name are as follows. when enclosed in single or double quotation marks, the character string in the single or double quotation marks is used. the case where there is a character string outside the single or double quotation marks is not supported. if a character string is enclosed in single or double quotation marks, the single or double quotation marks on both ends are not included in the character count. the group name is assigned to the character string used with the snmp-server user command. it is not assigned to the character string used with the snmp-server group command. the use of \ is not supported. the use of only single or double quotation marks is not supported. snmp server access restrictions specified using the snmp-server access command only apply to snmpv1 and snmpv2c access. they do not apply to snmpv3 access.</div><div class="display_word">6. Points of Caution Check the SNMP version that can be used with the SNMP manager beforehand. It is necessary to configure this product in accordance with the SNMP version that will be used. This product is not compatible with the following functions related to SNMPv3. Proxy function Access to MIB objects after the SNMPv2 subtree (1.3.6.1.6). Changing SNMPv3-related settings via SNMP is also not supported. Character string specifications for the community name, username, password, and group name are as follows. When enclosed in single or double quotation marks, the character string in the single or double quotation marks is used. The case where there is a character string outside the single or double quotation marks is not supported. If a character string is enclosed in single or double quotation marks, the single or double quotation marks on both ends are not included in the character count. The group name is assigned to the character string used with the snmp-server user command. It is not assigned to the character string used with the snmp-server group command. The use of \ is not supported. The use of only single or double quotation marks is not supported. SNMP server access restrictions specified using the snmp-server access command only apply to SNMPv1 and SNMPv2c access. They do not apply to SNMPv3 access.</div></div><div id="oam_oam_snmp"><div class="search_title" docfname="oam_oam_snmp" doctitle="SNMP" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation yamaha rtpro snmp yamaha rtpro private mib snmp mib reference</div><div class="display_word">7. Related Documentation Yamaha RTpro SNMP Yamaha RTpro Private MIB SNMP MIB Reference</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#スタック機能">Stack Function</div><div class="search_word">stack function</div><div class="display_word">Stack Function</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview the stack function connects multiple network switches and operates them as a single virtual network switch . the features of the stack are shown below. realizing the redundancy with high usage efficiency there are two methods for configuring networks without a single point of failure (spof). either configure networks with vrrps and stps or using stacks and link aggregation . by using the stack, unlike vrrp, there is no standby network switch, so you can increase the usage efficiency of the network switch while ensuring redundancy. easy port expansion you can easily increase the number of available ports by adding network switches. stack overview the stack function is disabled in default factory settings.</div><div class="display_word">1. Function Overview The stack function connects multiple network switches and operates them as a single virtual network switch . The features of the stack are shown below. Realizing the redundancy with high usage efficiency There are two methods for configuring networks without a single point of failure (SPOF). Either configure networks with VRRPs and STPs or using stacks and link aggregation . By using the stack, unlike VRRP, there is no standby network switch, so you can increase the usage efficiency of the network switch while ensuring redundancy. Easy port expansion You can easily increase the number of available ports by adding network switches. Stack overview The stack function is disabled in default factory settings.</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used member switch a network switch that makes up the stack. each switch is identified by a stack id. stack id an id that identifies the member switches that make up the stack. the stack id can be set from 1 to the maximum number of stacks that can be configured (currently 2). main switch the main switch is selected from among member switches for managing other member switches. given default settings, the switch with stack id 1 operates as the main switch. virtual switch a single logical switch consisting of multiple member switches using the stack function. stack port sfp+ slot used to connect the network switches that make up the stack. stack link a connection between member switches that make up a stack.</div><div class="display_word">2. Definition of Terms Used Member switch A network switch that makes up the stack. Each switch is identified by a stack ID. Stack ID An ID that identifies the member switches that make up the stack. The stack ID can be set from 1 to the maximum number of stacks that can be configured (currently 2). Main switch The main switch is selected from among member switches for managing other member switches. Given default settings, the switch with stack ID 1 operates as the main switch. Virtual switch A single logical switch consisting of multiple member switches using the stack function. Stack port SFP+ slot used to connect the network switches that make up the stack. Stack link A connection between member switches that make up a stack.</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#スタックの構成">3.1. Stack configuration</div><div class="search_word">3.1. stack configuration the configurations that can be stacked for each model are shown below. only configurations with two units of the same model are supported. however, considering that stacks should reduce the impact of failures, make sure stacks are always configured with two stack links. swx2310p-28gt stack configuration swx3200-28gt stack configuration swx3200-52gt stack configuration</div><div class="display_word">3.1. Stack configuration The configurations that can be stacked for each model are shown below. Only configurations with two units of the same model are supported. However, considering that stacks should reduce the impact of failures, make sure stacks are always configured with two stack links. SWX2310P-28GT stack configuration SWX3200-28GT stack configuration SWX3200-52GT stack configuration</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#メンバースイッチ間の接続">3.2. Connection between member switches</div><div class="search_word">3.2. connection between member switches when the stack function is enabled, the following sfp+ slots are switched to stack ports for connecting between members. swx2310p-28gt : ports 27 and 28 swx3200-28gt : ports 27 and 28 swx3200-52gt : ports 51 and 52 unlike normal communication ports, stack ports are used only for communication between member switches. connection between member switches is only possible with a direct connection cable (ydac-10g-1m/3m) or an sfp+ module (ysfp-10g-sr/lr) provided by yamaha. when connecting with another company’s product, the stack link will be forced down. stack ports are connected to the lower and higher number ports on member switches.</div><div class="display_word">3.2. Connection between member switches When the stack function is enabled, the following SFP+ slots are switched to stack ports for connecting between members. SWX2310P-28GT : Ports 27 and 28 SWX3200-28GT : Ports 27 and 28 SWX3200-52GT : Ports 51 and 52 Unlike normal communication ports, stack ports are used only for communication between member switches. Connection between member switches is only possible with a direct connection cable (YDAC-10G-1M/3M) or an SFP+ module (YSFP-10G-SR/LR) provided by Yamaha. When connecting with another company’s product, the stack link will be forced down. Stack ports are connected to the lower and higher number ports on member switches.</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#メインスイッチの選出とmacアドレスの付与">3.3. Main switch selection and MAC address assignment</div><div class="search_word">3.3. main switch selection and mac address assignment the rules for main switch selection and mac address assignment are indicated below. note that the mac address used in the stack configuration is applied according to the following rules in order to eliminate the impact on communication. in the default stack configuration, the mac address of the main switch (switch with id 1) is used as the mac address of the virtual switch. if a member switch other than the main switch is disconnected (due to an error) during stack configuration, then the virtual switch will continue to use the specified mac address. if the main switch is disconnected (due to an error) during stack configuration, the virtual switch will continue to use the specified mac address. in other words, the mac address of the network switch that is not included in the stack configuration is used. even if a network switch other than the failed switch (a network switch with a different mac address) is installed as a member switch, the virtual switch will continue to use the specified mac address. if you want to reconfigure the stack with the current configuration status, restart the virtual switch at the same time to perform reconstruction. (the stack with id 1 becomes the main switch and the virtual switch uses the mac address of the main switch.) main switch selection and mac address assignment no stack configuration main switch selection rule 1 initial composition the stack with id 1 specified is selected as the main switch. in that case, the mac address of stack id 1 is used as the virtual switch mac address. 2 fault occurrence if an error occurs in the main switch, the member switch with the smallest stack id number is selected as the main switch. in that case, the virtual switch retains the mac address of stack id 1. 3 abnormal state recovery if a network switch with a failure is reinstalled in the stack, the switch currently selected as the main switch will continue to function as the main switch. in that case, the virtual switch mac address remains the mac address of stack id 1 where the failure occurred.</div><div class="display_word">3.3. Main switch selection and MAC address assignment The rules for main switch selection and MAC address assignment are indicated below. Note that the MAC address used in the stack configuration is applied according to the following rules in order to eliminate the impact on communication. In the default stack configuration, the MAC address of the main switch (switch with ID 1) is used as the MAC address of the virtual switch. If a member switch other than the main switch is disconnected (due to an error) during stack configuration, then the virtual switch will continue to use the specified MAC address. If the main switch is disconnected (due to an error) during stack configuration, the virtual switch will continue to use the specified MAC address. In other words, the MAC address of the network switch that is not included in the stack configuration is used. Even if a network switch other than the failed switch (a network switch with a different MAC address) is installed as a member switch, the virtual switch will continue to use the specified MAC address. If you want to reconfigure the stack with the current configuration status, restart the virtual switch at the same time to perform reconstruction. (The stack with ID 1 becomes the main switch and the virtual switch uses the MAC address of the main switch.) Main switch selection and MAC address assignment No Stack configuration Main switch selection rule 1 Initial composition The stack with ID 1 specified is selected as the main switch. In that case, the MAC address of stack ID 1 is used as the virtual switch MAC address. 2 Fault occurrence If an error occurs in the main switch, the member switch with the smallest stack ID number is selected as the main switch. In that case, the virtual switch retains the MAC address of stack ID 1. 3 Abnormal state recovery If a network switch with a failure is reinstalled in the stack, the switch currently selected as the main switch will continue to function as the main switch. In that case, the virtual switch MAC address remains the MAC address of stack ID 1 where the failure occurred.</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#仮想スイッチに対する操作">3.4. Operations on virtual switches</div><div class="search_word">3.4. operations on virtual switches operations on virtual switches in a stack configuration are basically controlled from the main switch. the specifications related to operation are shown below. logging in to a virtual switch always logs into the main switch. * if necessary, the *remote-login command can be used to log into another member switch. prompt when logging into the main switch yamaha> prompt when logging into a member switch yamaha-2> (1) 1 the stack id number is indicated after the host name. the configuration (running-config, startup-config) for the virtual switch is always synchronized between member switches. when finished configuring settings, be sure to save the running-config settings using the write command. note, however, that the write command can only be executed from the main switch. when operating a virtual switch, the information stored in the l2/l3 network switch (e.g. fdb learning information, arp cache, etc.) is automatically synchronized. there is no need for the user to be aware of this. to view the virtual switch log, log in and then execute the show logging command. in that state, the log shown is for the main switch. to view the log for a member switch, use the remote-login command to log into the applicable member switch and view the corresponding log.</div><div class="display_word">3.4. Operations on virtual switches Operations on virtual switches in a stack configuration are basically controlled from the main switch. The specifications related to operation are shown below. Logging in to a virtual switch always logs into the main switch. * If necessary, the *remote-login command can be used to log into another member switch. Prompt when logging into the main switch Yamaha> Prompt when logging into a member switch Yamaha-2> (1) 1 The stack ID number is indicated after the host name. The configuration (running-config, startup-config) for the virtual switch is always synchronized between member switches. When finished configuring settings, be sure to save the running-config settings using the write command. Note, however, that the write command can only be executed from the main switch. When operating a virtual switch, the information stored in the L2/L3 network switch (e.g. FDB learning information, ARP cache, etc.) is automatically synchronized. There is no need for the user to be aware of this. To view the virtual switch log, log in and then execute the show logging command. In that state, the log shown is for the main switch. To view the log for a member switch, use the remote-login command to log into the applicable member switch and view the corresponding log.</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#スタック構成時のスイッチの状態">3.5. Network switch status when stacking</div><div class="search_word">3.5. network switch status when stacking the member switch manages the status in the stack configuration as follows. that status can be viewed using the show stack command. setting a state in which one or more stack port links are up, and the settings necessary for stacking between member switches are performed. specifically, the configuration is automatically ascertained between member switches. active a state in which automatic recognition of the configuration between member switches is completed, various settings are synchronized, and virtualization is performed by multiple member switches. virtualization is performed by two or more switches. inactive a state in which a failure has occurred and the virtual switch has been removed. all communication ports, including stack ports, are forcibly shut down and communication is disabled. (closed state) standalone the stack function is enabled, but since negotiation cannot be performed with the member switch, it is operating on one unit. transition to this state occurs when there is no opposing switch temporarily, such as during initial installation. in this state, the stack id must be enabled, so it is operated with the specified id setting . standalone(separated) same status as standalone status indicated above. however, it remembers that a stack was once configured and retains main switch selection information that can be used when reconfiguring the stack. disable the stack function is disabled. in this state, the stack is operated with the id number forcibly set to 1 (even if the stack id was set to a value other than 1 ).</div><div class="display_word">3.5. Network switch status when stacking The member switch manages the status in the stack configuration as follows. That status can be viewed using the show stack command. Setting A state in which one or more stack port links are up, and the settings necessary for stacking between member switches are performed. Specifically, the configuration is automatically ascertained between member switches. Active A state in which automatic recognition of the configuration between member switches is completed, various settings are synchronized, and virtualization is performed by multiple member switches. Virtualization is performed by two or more switches. Inactive A state in which a failure has occurred and the virtual switch has been removed. All communication ports, including stack ports, are forcibly shut down and communication is disabled. (Closed state) Standalone The stack function is enabled, but since negotiation cannot be performed with the member switch, it is operating on one unit. Transition to this state occurs when there is no opposing switch temporarily, such as during initial installation. In this state, the stack ID must be enabled, so it is operated with the specified ID setting . Standalone(separated) Same status as Standalone status indicated above. However, it remembers that a stack was once configured and retains main switch selection information that can be used when reconfiguring the stack. Disable The stack function is disabled. In this state, the stack is operated with the ID number forcibly set to 1 (even if the stack ID was set to a value other than 1 ).</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#異常状態の検出と措置">3.6. Detection and measures for abnormal conditions</div><div class="search_word">3.6. detection and measures for abnormal conditions when a member switch in the stack configuration detects an error, it tries to resolve it autonomously within the virtual switch so that the network service is not affected. this switch monitors the following abnormal conditions. abnormality detection on the local node does not meet stack configuration conditions (stack id error, firmware version error) stack link error (down detection) fan stopped thermal sensor abnormality (only for the swx2310p-28gt) voltage value error current value error connection node error detection heartbeat frame reception timeout heartbeat is a function to check whether member switches are operating normally. if the heartbeat frame is not received for a certain period (currently 4 seconds), it is determined that an error has occurred in the member switch. the operation when an error is detected is shown below. detected node detected content operation after detection state after detection remarks main switch setting error abnormal stack id or firmware version as a virtual switch, it is determined that processing cannot be continued, and the network port and stack link are forcibly taken down and disconnected from the stack configuration. inactive stack link down one of the two links down the status of the main switch is maintained, but two-way communication is achieved via one link. active both links down the status of the main switch is maintained. standalone(separated) possible double-main status hw error fan stopped, thermal abnormality, voltage/current value error in this state, it is determined that the network switch cannot continue to be treated as the main switch, so the network ports and stack links are forcibly disabled to disconnect the switch from the stack configuration. inactive heartbeat error notifications from member switches stopped continues to be operated as the main switch. standalone(separated) or active if there is only one remaining configuration, standalone (separated) non-main member switch setting error abnormal stack id or firmware version as a virtual switch, it is determined that processing cannot be continued, and the network port and stack link are forcibly taken down and disconnected from the stack configuration. inactive stack link down one of the two links down the member switch status is maintained, but two-way communication is achieved with one switch. active both links down upgraded to a main switch to continue service. standalone(separated) possible double-main status hw error fan stopped, thermal abnormality, voltage/current value error in this state, it is determined that the network switch cannot continue to be treated as a member switch, so the network ports and stack links are forcibly disabled to disconnect the switch from the stack configuration. inactive heartbeat error notifications from the main switch stopped upgraded to a main switch to continue service. standalone(separated) or active if there is only one remaining configuration, standalone (separated)</div><div class="display_word">3.6. Detection and measures for abnormal conditions When a member switch in the stack configuration detects an error, it tries to resolve it autonomously within the virtual switch so that the network service is not affected. This switch monitors the following abnormal conditions. Abnormality detection on the local node Does not meet stack configuration conditions (stack ID error, firmware version error) Stack link error (down detection) Fan stopped Thermal sensor abnormality (only for the SWX2310P-28GT) Voltage value error Current value error Connection node error detection Heartbeat frame reception timeout Heartbeat is a function to check whether member switches are operating normally. If the heartbeat frame is not received for a certain period (currently 4 seconds), it is determined that an error has occurred in the member switch. The operation when an error is detected is shown below. Detected node Detected content Operation after detection State after detection Remarks Main switch Setting error Abnormal stack ID or firmware version As a virtual switch, it is determined that processing cannot be continued, and the network port and stack link are forcibly taken down and disconnected from the stack configuration. Inactive Stack link down One of the two links down The status of the main switch is maintained, but two-way communication is achieved via one link. Active Both links down The status of the main switch is maintained. Standalone(separated) Possible double-main status HW error Fan stopped, thermal abnormality, voltage/current value error In this state, it is determined that the network switch cannot continue to be treated as the main switch, so the network ports and stack links are forcibly disabled to disconnect the switch from the stack configuration. Inactive Heartbeat error Notifications from member switches stopped Continues to be operated as the main switch. Standalone(separated) or Active If there is only one remaining configuration, Standalone (separated) Non-main member switch Setting error Abnormal stack ID or firmware version As a virtual switch, it is determined that processing cannot be continued, and the network port and stack link are forcibly taken down and disconnected from the stack configuration. Inactive Stack link down One of the two links down The member switch status is maintained, but two-way communication is achieved with one switch. Active Both links down Upgraded to a main switch to continue service. Standalone(separated) Possible double-main status HW error Fan stopped, thermal abnormality, voltage/current value error In this state, it is determined that the network switch cannot continue to be treated as a member switch, so the network ports and stack links are forcibly disabled to disconnect the switch from the stack configuration. Inactive Heartbeat error Notifications from the main switch stopped Upgraded to a main switch to continue service. Standalone(separated) or Active If there is only one remaining configuration, Standalone (separated)</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details, refer to the command reference. operations operating commands setting stack functions stack changing the stack id number stack renumber setting the ip address range used for stack ports stack subnet show stack information show stack</div><div class="display_word">4. Related Commands Related commands are indicated below. For details, refer to the Command Reference. Operations Operating commands Setting stack functions stack Changing the stack ID number stack renumber Setting the IP address range used for stack ports stack subnet Show stack information show stack</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#スタックの初期設定">5. Stack Initial Settings</div><div class="search_word">5. stack initial settings the initial setting flow for stack configuration is shown below. preparation of necessary equipment member switch settings connecting member switches</div><div class="display_word">5. Stack Initial Settings The initial setting flow for stack configuration is shown below. Preparation of necessary equipment Member switch settings Connecting member switches</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#必要機材の準備">5.1. Preparation of necessary equipment</div><div class="search_word">5.1. preparation of necessary equipment prepare the equipment necessary to configure the stack. member switch prepare the member switches for stack configuration. for the stackable configurations, refer to 3.1 stack configuration . stack port connection cable determine and prepare the interfaces to connect the member switches. use direct connection cables to configure stacks within a rack and sfp+ modules to configure them across longer distances, such as between floors or buildings. for more details, refer to 3.2 connection between member switches . external memory (sd card) it is recommended to use external memory to save backup data such as configs and logs during stack operation. by using external memory, you can use it to recover the config if a failure occurs.</div><div class="display_word">5.1. Preparation of necessary equipment Prepare the equipment necessary to configure the stack. Member switch Prepare the member switches for stack configuration. For the stackable configurations, refer to 3.1 Stack configuration . Stack port connection cable Determine and prepare the interfaces to connect the member switches. Use direct connection cables to configure stacks within a rack and SFP+ modules to configure them across longer distances, such as between floors or buildings. For more details, refer to 3.2 Connection between member switches . External memory (SD card) It is recommended to use external memory to save backup data such as configs and logs during stack operation. By using external memory, you can use it to recover the config if a failure occurs.</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#メンバースイッチの設定">5.2. Member switch settings</div><div class="search_word">5.2. member switch settings set the member switches that constitute the stack. consider the following before you begin configuration. determining stack ids to be assigned to member switches stack ids to be assigned to member switches must be statically determined . during initial settings, stack id: 1 will be the main switch. determining the save destination for the startup config determine the save destination for the startup config during stack configuration. select 0 to 4 in the flash rom as the save destination and indicate in the description that it is for saving stack information. after reviewing, configure member switches individually according to the following procedure. starting the member switches start the member switches individually and access them from the serial console. checking and updating the firmware version use the show environment command to check the current firmware version. yamaha> show environmentswx3200-52gt bootrom ver.1.00swx3200-52gt rev.4.00.05 (fri mar  9 09:34:05 2018) (1) main=swx3200-52gt ver=00 serial=s00000000 mac-address=00a0.de00.0000... 1 check the firmware version use the rtpro site to check the most recent version released. if the public firmware version of the relevant switch is newer than the firmware that is running, update it. it is recommended that the firmware version in member switches be updated to the latest version with fixes for known issues . given default settings, firmware updating using an sd card is enabled. refer to firmware update for how to update using an sd card. setting the save destination for the startup config use the startup-config select command to select the configuration used for stack operations. at this time, it is recommended to set the description to use for the config during stack operation. yamaha> enableyamaha# startup-config description 2 stack (1) yamaha# startup-config select 2 (2) reboot system? (y/n): y (3) 1 set the description “stack” to startup-config #2 2 select startup-config #2 3 restart the system setting the stack id check the network switch status with show stack to confirm that the stack function is disabled. also check the stack id. the default stack id setting is 1 . yamaha> enableyamaha#yamaha# show stackstack: disableconfigured id        : 1subnet on stack port : auto-ipvirtual mac-address  : 00a0.de00.0000id  model          status      role     serial       mac-address------------------------------------------------------------------------interface    status------------------------------------------------------------------------yamaha# if necessary, change the stack id number using the stack renumber command. yamaha(config)# stack 1 renumber 2 (1) yamaha(config)# do show stackstack: disableconfigured id        : 2subnet on stack port : auto-ipvirtual mac-address  : 00a0.de00.0000id  model          status      role     serial       mac-address------------------------------------------------------------------------interface    status------------------------------------------------------------------------yamaha# 1 change the stack id number from #1 to #2 enabling the stack function enable the stack function using the stack enable command. after entering the command, reboot the device. default-config is applied after rebooting is finished. yamaha(config)#stack enable (1) reset configuration and reboot system? (y/n): y (2) 1 enable the stack function 2 restart the system after rebooting, check the network switch status with show stack to confirm that the stack function is enabled. also check the save destination of the startup config. yamaha> enableyamaha#yamaha# show stackstack: enable (1) configured id        : 1running id           : 1status               : standalonesubnet on stack port : auto-ipvirtual mac-address  : 00a0.de00.0000id  model          status      role     serial       mac-address------------------------------------------------------------------------1   swx3200-52gt   standalone  main     s000000000   00a0.de00.0000... (because it is operating with one unit, it is standalone main)interface    status------------------------------------------------------------------------port1.51     downport1.52     downyamaha>show environmentswx3200-52gt bootrom ver.1.00swx3200-52gt rev.4.00.05 (fri mar  9 09:34:05 2018)main=swx3200-52gt ver=00 serial=s00000000 mac-address=00a0.de00.0000cpu:   2%(5sec)   2%(1min)   1%(5min)    memory:  10% usedfan status: normalfan speed: fan1=4000rpm fan2=3870rpmstartup firmware: exec0startup configuration file: config2 (2) serial baudrate: 9600boot time: 2018/01/01 11:06:36 +09:00current time: 2018/01/02 16:12:23 +09:00elapsed time from boot: 1days 05:05:49temperature status: normaltemperature: 37 degree cvoltage: 11.99v    current: 0.741a 1 the stack function is enabled 2 confirm that the specified startup config is correctly applied.</div><div class="display_word">5.2. Member switch settings Set the member switches that constitute the stack. Consider the following before you begin configuration. Determining stack IDs to be assigned to member switches Stack IDs to be assigned to member switches must be statically determined . During initial settings, stack ID: 1 will be the main switch. Determining the save destination for the startup config Determine the save destination for the startup config during stack configuration. Select 0 to 4 in the flash ROM as the save destination and indicate in the description that it is for saving stack information. After reviewing, configure member switches individually according to the following procedure. Starting the member switches Start the member switches individually and access them from the serial console. Checking and updating the firmware version Use the show environment command to check the current firmware version. Yamaha> show environmentSWX3200-52GT BootROM Ver.1.00SWX3200-52GT Rev.4.00.05 (Fri Mar  9 09:34:05 2018) (1) main=SWX3200-52GT ver=00 serial=S00000000 MAC-Address=00a0.de00.0000... 1 Check the firmware version Use the RTpro site to check the most recent version released. If the public firmware version of the relevant switch is newer than the firmware that is running, update it. It is recommended that the firmware version in member switches be updated to the latest version with fixes for known issues . Given default settings, firmware updating using an SD card is enabled. Refer to Firmware update for how to update using an SD card. Setting the save destination for the startup config Use the startup-config select command to select the configuration used for stack operations. At this time, it is recommended to set the description to use for the config during stack operation. Yamaha> enableYamaha# startup-config description 2 Stack (1) Yamaha# startup-config select 2 (2) reboot system? (y/n): y (3) 1 Set the description “Stack” to startup-config #2 2 Select startup-config #2 3 Restart the system Setting the stack ID Check the network switch status with show stack to confirm that the stack function is disabled. Also check the stack ID. The default stack ID setting is 1 . Yamaha> enableYamaha#Yamaha# show stackStack: DisableConfigured ID        : 1Subnet on stack port : Auto-ipVirtual MAC-Address  : 00a0.de00.0000ID  Model          Status      Role     Serial       MAC-Address------------------------------------------------------------------------Interface    Status------------------------------------------------------------------------Yamaha# If necessary, change the stack ID number using the stack renumber command. Yamaha(config)# stack 1 renumber 2 (1) Yamaha(config)# do show stackStack: DisableConfigured ID        : 2Subnet on stack port : Auto-ipVirtual MAC-Address  : 00a0.de00.0000ID  Model          Status      Role     Serial       MAC-Address------------------------------------------------------------------------Interface    Status------------------------------------------------------------------------Yamaha# 1 Change the stack ID number from #1 to #2 Enabling the stack function Enable the stack function using the stack enable command. After entering the command, reboot the device. Default-config is applied after rebooting is finished. Yamaha(config)#stack enable (1) reset configuration and reboot system? (y/n): y (2) 1 Enable the stack function 2 Restart the system After rebooting, check the network switch status with show stack to confirm that the stack function is enabled. Also check the save destination of the startup config. Yamaha> enableYamaha#Yamaha# show stackStack: Enable (1) Configured ID        : 1Running ID           : 1Status               : StandaloneSubnet on stack port : Auto-ipVirtual MAC-Address  : 00a0.de00.0000ID  Model          Status      Role     Serial       MAC-Address------------------------------------------------------------------------1   SWX3200-52GT   Standalone  Main     S000000000   00a0.de00.0000... (Because it is operating with one unit, it is Standalone Main)Interface    Status------------------------------------------------------------------------port1.51     downport1.52     downYamaha>show environmentSWX3200-52GT BootROM Ver.1.00SWX3200-52GT Rev.4.00.05 (Fri Mar  9 09:34:05 2018)main=SWX3200-52GT ver=00 serial=S00000000 MAC-Address=00a0.de00.0000CPU:   2%(5sec)   2%(1min)   1%(5min)    Memory:  10% usedFan status: NormalFan speed: FAN1=4000RPM FAN2=3870RPMStartup firmware: exec0Startup Configuration file: config2 (2) Serial Baudrate: 9600Boot time: 2018/01/01 11:06:36 +09:00Current time: 2018/01/02 16:12:23 +09:00Elapsed time from boot: 1days 05:05:49Temperature status: NormalTemperature: 37 degree CVoltage: 11.99V    Current: 0.741A 1 The stack function is enabled 2 Confirm that the specified startup config is correctly applied.</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#メンバースイッチの接続">5.3. Connecting member switches</div><div class="search_word">5.3. connecting member switches connect stack-enabled network switches using direct connection cables or sfp+ modules . for connection instructions refer to connection between member switches . the member switches can be connected with either the power turned on or off . after connecting the member switches, check the system status using the show stack command. yamaha# show stackstack: enableconfigured id        : 1running id           : 1status               : activesubnet on stack port : auto-ipvirtual mac-address  : 00a0.de00.0000id  model          status      role     serial       mac-address------------------------------------------------------------------------1   swx3200-52gt   active      main     s000000000   00a0.de00.0000... (switch with stack id 1 is main)2   swx3200-52gt   active      member   s000000000   00a0.de00.0000... (switch with stack id 2 is member)interface    status------------------------------------------------------------------------port1.51     upport1.52     upport2.51     upport2.52     up use the backup system command to back up the initial setting status of the member switch to the sd card. by saving the following firmware files in the indicated folder on the sd card, both settings and firmware can be backed up during backup execution. swx2310p-28gt: [folder]/swx2310p/firmware, [firmware file]swx2310p.bin swx3200-28gt and swx3200-52gt: [folder]/swx3200/firmware, [firmware file]swx3200.bin yamaha> enableyamaha# backup system (1) succeeded to backup system files and firmware file.yamaha# remote-login 2 (2) entering character modeescape character is '^]'.swx3200-52gt rev.4.00.xx  copyright (c) 2018 yamaha corporation. all rights reserved.yamaha-2> enableyamaha-2# backup system (3) succeeded to backup system files and firmware file. 1 copy all main switch settings to the sd card 2 remotely log in to a member switch (stack id: 2) 3 copy all the settings for member switch (stack id: 2) to the sd card this completes the initial stack settings. install the virtual switch in the network to be used and perform the settings required for operation. after completing the settings required for operation, backup should be performed in case of an abnormality, just as with the initial settings.</div><div class="display_word">5.3. Connecting member switches Connect stack-enabled network switches using direct connection cables or SFP+ modules . For connection instructions refer to Connection between member switches . The member switches can be connected with either the power turned on or off . After connecting the member switches, check the system status using the show stack command. Yamaha# show stackStack: EnableConfigured ID        : 1Running ID           : 1Status               : ActiveSubnet on stack port : Auto-ipVirtual MAC-Address  : 00a0.de00.0000ID  Model          Status      Role     Serial       MAC-Address------------------------------------------------------------------------1   SWX3200-52GT   Active      Main     S000000000   00a0.de00.0000... (Switch with stack ID 1 is main)2   SWX3200-52GT   Active      Member   S000000000   00a0.de00.0000... (Switch with stack ID 2 is member)Interface    Status------------------------------------------------------------------------port1.51     upport1.52     upport2.51     upport2.52     up Use the backup system command to back up the initial setting status of the member switch to the SD card. By saving the following firmware files in the indicated folder on the SD card, both settings and firmware can be backed up during backup execution. SWX2310P-28GT: [Folder]/swx2310p/firmware, [Firmware file]swx2310p.bin SWX3200-28GT and SWX3200-52GT: [Folder]/swx3200/firmware, [Firmware file]swx3200.bin Yamaha> enableYamaha# backup system (1) Succeeded to backup system files and firmware file.Yamaha# remote-login 2 (2) Entering character modeEscape character is '^]'.SWX3200-52GT Rev.4.00.XX  Copyright (c) 2018 Yamaha Corporation. All Rights Reserved.Yamaha-2> enableYamaha-2# backup system (3) Succeeded to backup system files and firmware file. 1 Copy all main switch settings to the SD card 2 Remotely log in to a member switch (Stack ID: 2) 3 Copy all the settings for member switch (stack ID: 2) to the SD card This completes the initial stack settings. Install the virtual switch in the network to be used and perform the settings required for operation. After completing the settings required for operation, backup should be performed in case of an abnormality, just as with the initial settings.</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#メンバースイッチの交換">6. Exchanging Member Switches</div><div class="search_word">6. exchanging member switches the following describes how to replace a member switch after a fault occurs in a configuration with two swx3200-52gt switches. the following shows each case of using and not using an sd card.</div><div class="display_word">6. Exchanging Member Switches The following describes how to replace a member switch after a fault occurs in a configuration with two SWX3200-52GT switches. The following shows each case of using and not using an SD card.</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#sdカードを使用した交換手順">6.1. Exchange procedure using an SD card</div><div class="search_word">6.1. exchange procedure using an sd card member switches are exchanged by backup/restore using an sd card. exchange procedure in normal operation after completing the setting to the member switches, back up the system information to the sd card in consideration of failure. to back up system information, execute the backup system command. before backing up the system information, also backup the firmware by saving the swx3200.bin file (firmware file) in the /swx3200/firmware folder in the sd card. fault occurrence assume that an error occurs in the member switch with stack id 2. fault recovery prepare the member switches to be exchanged and connect the sd card that contains the backup of the failed switches. apply the firmware and system information by executing the restore system command. after they are applied, turn off the power, connect to the network switch currently functioning as the main switch, and turn on the power to restore the stack configuration.</div><div class="display_word">6.1. Exchange procedure using an SD card Member switches are exchanged by backup/restore using an SD card. Exchange procedure In normal operation After completing the setting to the member switches, back up the system information to the SD card in consideration of failure. To back up system information, execute the backup system command. Before backing up the system information, also backup the firmware by saving the swx3200.bin file (firmware file) in the /swx3200/firmware folder in the SD card. Fault occurrence Assume that an error occurs in the member switch with stack ID 2. Fault recovery Prepare the member switches to be exchanged and connect the SD card that contains the backup of the failed switches. Apply the firmware and system information by executing the restore system command. After they are applied, turn off the power, connect to the network switch currently functioning as the main switch, and turn on the power to restore the stack configuration.</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#sdカードを使用しない交換手順">6.2. Exchange procedure without using an SD card</div><div class="search_word">6.2. exchange procedure without using an sd card exchange the member switches without using an sd card. at the start of operation after installation of the member switches is completed, store the same revision firmware as the firmware written in the member switches on a pc, etc. record the serial number, config id being used, and stack id of each member switch. yamaha> show environmentswx3200-52gt bootrom ver.1.00swx3200 rev.4.00.05 (fri mar  9 09:34:05 2018)main=swx3200-52gt ver=00 serial=s00000000 mac-address=00a0.de00.0000 (1) cpu:   2%(5sec)   2%(1min)   1%(5min)    memory:  10% usedfan status: normalfan speed: fan1=4000rpm fan2=3870rpm fan3=3870rpm fan4=4000rpmstartup firmware: exec0startup configuration file: config1 (2) serial baudrate: 9600boot time: 2018/01/01 11:06:36 +09:00current time: 2018/01/02 16:12:23 +09:00elapsed time from boot: 1days 05:05:49temperature status: normaltemperature: 37 degree cvoltage: 11.99v    current: 0.741ayamaha>yamaha> show stackstack: enableconfigured id        : 1 (3) running id           : 1status               : activesubnet on stack port : auto-ipvirtual mac-address  : 00a0.de00.0000id  model          status      role     serial       mac-address------------------------------------------------------------------------1   swx3200-52gt   active      main     s000000000   00a0.de00.00002   swx3200-52gt   active      member   s000000000   00a0.de00.0000interface    status------------------------------------------------------------------------port1.51     upport1.52     upport2.51     upport2.52     up 1 serial number 2 config id 3 stack id fault occurrence assume that an error occurs in the member switch with stack id 2. fault recovery prepare the member switches to be exchanged and write the saved firmware. start the member switches and change the config id used at startup. if the config id used at the start of operation was 0, there is no need to change the config id. yamaha> enableyamaha# startup-config select 1reboot system? (y/n): y after rebooting, enable the stack function. for the stack id to be set, refer to the member switch serial number and stack id recorded at the start of operation. yamaha> enableyamaha# configure terminalyamaha(config)# stack 1 renumber 2 (1) yamaha(config)# stack enable (2) reset configuration and reboot system? (y/n): y 1 set stack id 2 2 enable the stack function after enabling the stack function, turn off the power, connect to the network switch functioning as the main switch, and turn on the power to restore the stack configuration.</div><div class="display_word">6.2. Exchange procedure without using an SD card Exchange the member switches without using an SD card. At the start of operation After installation of the member switches is completed, store the same revision firmware as the firmware written in the member switches on a PC, etc. Record the serial number, config ID being used, and stack ID of each member switch. Yamaha> show environmentSWX3200-52GT BootROM Ver.1.00SWX3200 Rev.4.00.05 (Fri Mar  9 09:34:05 2018)main=SWX3200-52GT ver=00 serial=S00000000 MAC-Address=00a0.de00.0000 (1) CPU:   2%(5sec)   2%(1min)   1%(5min)    Memory:  10% usedFan status: NormalFan speed: FAN1=4000RPM FAN2=3870RPM FAN3=3870RPM FAN4=4000RPMStartup firmware: exec0Startup Configuration file: config1 (2) Serial Baudrate: 9600Boot time: 2018/01/01 11:06:36 +09:00Current time: 2018/01/02 16:12:23 +09:00Elapsed time from boot: 1days 05:05:49Temperature status: NormalTemperature: 37 degree CVoltage: 11.99V    Current: 0.741AYamaha>Yamaha> show stackStack: EnableConfigured ID        : 1 (3) Running ID           : 1Status               : ActiveSubnet on stack port : Auto-ipVirtual MAC-Address  : 00a0.de00.0000ID  Model          Status      Role     Serial       MAC-Address------------------------------------------------------------------------1   SWX3200-52GT   Active      Main     S000000000   00a0.de00.00002   SWX3200-52GT   Active      Member   S000000000   00a0.de00.0000Interface    Status------------------------------------------------------------------------port1.51     upport1.52     upport2.51     upport2.52     up 1 Serial number 2 Config ID 3 Stack ID Fault occurrence Assume that an error occurs in the member switch with stack ID 2. Fault recovery Prepare the member switches to be exchanged and write the saved firmware. Start the member switches and change the config ID used at startup. If the config ID used at the start of operation was 0, there is no need to change the config ID. Yamaha> enableYamaha# startup-config select 1reboot system? (y/n): y After rebooting, enable the stack function. For the stack ID to be set, refer to the member switch serial number and stack ID recorded at the start of operation. Yamaha> enableYamaha# configure terminalYamaha(config)# stack 1 renumber 2 (1) Yamaha(config)# stack enable (2) reset configuration and reboot system? (y/n): y 1 Set stack ID 2 2 Enable the stack function After enabling the stack function, turn off the power, connect to the network switch functioning as the main switch, and turn on the power to restore the stack configuration.</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#ファームウェア更新">7. Firmware Update</div><div class="search_word">7. firmware update the following two methods are provided for updating the firmware during stack configuration. method to update member switches during configuration simultaneously (parallel update) method to update without stopping network services (sequential update) parallel update is an effective method if you have enough time to allow a service outage. however, *during stack configuration, it is recommended that updates be performed sequentially without a service outage. * note that firmware updates during stack configuration are supported only for the following. update based on using a tftp client or web gui to send the firmware update update using an sd card if the firmware is updated while the sd card is inserted, sd card boot may be performed when restarting. the sd card boot can be disabled with the boot prioritize sd command. yamaha> enableyamaha# boot prioritize sd disable (1) reboot system? (y/n): y 1 disable sd card boot for more information, refer to firmware update .</div><div class="display_word">7. Firmware Update The following two methods are provided for updating the firmware during stack configuration. Method to update member switches during configuration simultaneously (parallel update) Method to update without stopping network services (sequential update) Parallel update is an effective method if you have enough time to allow a service outage. However, *during stack configuration, it is recommended that updates be performed sequentially without a service outage. * Note that firmware updates during stack configuration are supported only for the following. Update based on using a TFTP client or web GUI to send the firmware update Update using an SD card If the firmware is updated while the SD card is inserted, SD card boot may be performed when restarting. The SD card boot can be disabled with the boot prioritize sd command. Yamaha> enableYamaha# boot prioritize sd disable (1) reboot system? (y/n): y 1 Disable SD card boot For more information, refer to Firmware Update .</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#ファームウェアのパラレル更新">7.1. Firmware parallel update</div><div class="search_word">7.1. firmware parallel update firmware parallel update updates the firmware of the member switches in the stack configuration at the same time. the service will be stopped because the entire virtual switch is restarted for the update. note the following points when performing parallel update. confirm that the firmware update method is set to normal ( firmware-update reload-method command). confirm that the firmware update application time is set to the specified time ( firmware-update reload-time command). an overview of parallel update is shown below. parallel update process flow</div><div class="display_word">7.1. Firmware parallel update Firmware parallel update updates the firmware of the member switches in the stack configuration at the same time. The service will be stopped because the entire virtual switch is restarted for the update. Note the following points when performing parallel update. Confirm that the firmware update method is set to normal ( firmware-update reload-method command). Confirm that the firmware update application time is set to the specified time ( firmware-update reload-time command). An overview of parallel update is shown below. Parallel update process flow</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#ファームウェアのシーケンシャル更新">7.2. Firmware sequential update</div><div class="search_word">7.2. firmware sequential update firmware serial update updates the firmware of the member switches in the stack configuration sequentially. this update does not involve any service outage because the entire virtual switch does not need to be rebooted for the update. (* refer to section 6 in points of caution .) when performing a sequential update, note the following points. confirm that the firmware update method is set to sequential ( firmware-update reload-method command). confirm that the firmware update application time is set to the specified time ( firmware-update reload-time command). an overview of sequential update is shown below. sequential update process flow</div><div class="display_word">7.2. Firmware sequential update Firmware serial update updates the firmware of the member switches in the stack configuration sequentially. This update does not involve any service outage because the entire virtual switch does not need to be rebooted for the update. (* Refer to section 6 in Points of Caution .) When performing a sequential update, note the following points. Confirm that the firmware update method is set to sequential ( firmware-update reload-method command). Confirm that the firmware update application time is set to the specified time ( firmware-update reload-time command). An overview of sequential update is shown below. Sequential update process flow</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#注意事項">8. Points of Caution</div><div class="search_word">8. points of caution when the stack function is enabled, the following functions cannot be used. rmon ipv6 vrrp mld snooping when the stack function is enabled, it can be used as a function, but some restrictions occur. mirroring function mirroring between member switches is not possible. flow control pause frame cannot be transmitted. back pressure function when communicating via the stack port, jam signals are not transmitted. port led only for the swx2310p-28gt, the led does not blink in link/act mode. sfp optical reception level monitoring the optical reception level of the stack port is not monitored. link aggregation the maximum number of logical interfaces is reduced by one. mode button when a stack is configured with the swx2310p-28gt switches, control using the mode button is disabled . as with the swx3200-28gt/52gt switches, this network switch automatically transitions to status mode when a loop occurs. command line input the users who can transition to global configuration mode are limited. when the console side is in global configuration mode and the telnet side transitions to global configuration mode, the console side automatically transitions to privileged exec mode. console, telnet, ssh, remote login, and gui settings are exclusively controlled. it is not possible to log in from the main switch and other member switch consoles at the same time. dhcp client if the stack function is enabled and the auto ip function is used on the stack port, the dhcp client cannot be used. startup-config select command do not use the startup-config select command while the stack is configured. it may become impossible to configure correctly. to switch the config using the startup-config select command, disconnect the direct attach cable and cancel the stack configuration before executing. when the stack function is enabled, make sure that the stack configuration is configured before setting functions with commands or the gui. if the stack is not configured correctly, the settings may not be reflected correctly. the write command and copy running-config startup-config command can be executed only on the main switch (in an active state). they cannot be executed on a member switch or an incorrectly configured stack. when the stack function is enabled, the stack control packets use transmission queues #7 and #6, so do not assign other packets to transmission queues #7 and #6. when qos is enabled, transmission queues #7 and #6 are assigned by default in the cos-transmission queue id conversion table, so change the assignment. when the stack function is enabled, the initial setting for the transmission queue specification for frames transmitted from the network switch unit is transmission queue #6. do not change the transmission queue specification setting for frames transmitted from the network switch unit from the initial setting. if there is a difference between the settings (startup-config) in the main switch and in a member switch during stack configuration, the member switch settings are changed and the switch is rebooted. if there is a difference between the stack port ip address range settings for the main switch and a member switch during stack configuration, communication between stacks cannot be performed properly.</div><div class="display_word">8. Points of Caution When the stack function is enabled, the following functions cannot be used. RMON IPv6 VRRP MLD snooping When the stack function is enabled, it can be used as a function, but some restrictions occur. Mirroring function Mirroring between member switches is not possible. Flow control Pause frame cannot be transmitted. Back pressure function When communicating via the stack port, jam signals are not transmitted. Port LED Only for the SWX2310P-28GT, the LED does not blink in Link/Act mode. SFP optical reception level monitoring The optical reception level of the stack port is not monitored. Link aggregation The maximum number of logical interfaces is reduced by one. MODE button When a stack is configured with the SWX2310P-28GT switches, control using the MODE button is disabled . As with the SWX3200-28GT/52GT switches, this network switch automatically transitions to STATUS mode when a loop occurs. Command line input The users who can transition to global configuration mode are limited. When the console side is in global configuration mode and the telnet side transitions to global configuration mode, the console side automatically transitions to privileged EXEC mode. Console, telnet, ssh, remote login, and GUI settings are exclusively controlled. It is not possible to log in from the main switch and other member switch consoles at the same time. DHCP client If the stack function is enabled and the Auto IP function is used on the stack port, the DHCP client cannot be used. startup-config select command Do not use the startup-config select command while the stack is configured. It may become impossible to configure correctly. To switch the config using the startup-config select command, disconnect the direct attach cable and cancel the stack configuration before executing. When the stack function is enabled, make sure that the stack configuration is configured before setting functions with commands or the GUI. If the stack is not configured correctly, the settings may not be reflected correctly. The write command and copy running-config startup-config command can be executed only on the main switch (in an active state). They cannot be executed on a member switch or an incorrectly configured stack. When the stack function is enabled, the stack control packets use transmission queues #7 and #6, so do not assign other packets to transmission queues #7 and #6. When QoS is enabled, transmission queues #7 and #6 are assigned by default in the CoS-transmission queue ID conversion table, so change the assignment. When the stack function is enabled, the initial setting for the transmission queue specification for frames transmitted from the network switch unit is transmission queue #6. Do not change the transmission queue specification setting for frames transmitted from the network switch unit from the initial setting. If there is a difference between the settings (startup-config) in the main switch and in a member switch during stack configuration, the member switch settings are changed and the switch is rebooted. If there is a difference between the stack port IP address range settings for the main switch and a member switch during stack configuration, communication between stacks cannot be performed properly.</div></div><div id="oam_oam_stack"><div class="search_title" docfname="oam_oam_stack" doctitle="Stack" link="#関連文書">9. Related Documentation</div><div class="search_word">9. related documentation firmware update</div><div class="display_word">9. Related Documentation Firmware Update</div></div><div id="oam_oam_syslog"><div class="search_title" docfname="oam_oam_syslog" doctitle="SYSLOG" link="#syslog">SYSLOG</div><div class="search_word">syslog</div><div class="display_word">SYSLOG</div></div><div id="oam_oam_syslog"><div class="search_title" docfname="oam_oam_syslog" doctitle="SYSLOG" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product provides the syslog functions shown below as a means to ascertain the operating state. functions to collect, reference, and delete the log that is accumulated inside this product functions for output to the console simultaneously with logging functions for transmitting to a previously-registered notification destination (syslog server) simultaneously with logging logging, output to console, and notifications to the syslog server are performed according to the output level specified by the user. processing occurs only for the permitted messages. logging occurs in ram, and is automatically backed up to flash rom or can be backed up manually. when backing up manually, you can also back up to an sd card at the same time. notifications to the syslog server are done simultaneously with logging, but only if a syslog server has been registered.</div><div class="display_word">1. Function Overview This product provides the SYSLOG functions shown below as a means to ascertain the operating state. Functions to collect, reference, and delete the log that is accumulated inside this product Functions for output to the console simultaneously with logging Functions for transmitting to a previously-registered notification destination (SYSLOG server) simultaneously with logging Logging, output to console, and notifications to the SYSLOG server are performed according to the output level specified by the user. Processing occurs only for the permitted messages. Logging occurs in RAM, and is automatically backed up to flash ROM or can be backed up manually. When backing up manually, you can also back up to an SD card at the same time. Notifications to the SYSLOG server are done simultaneously with logging, but only if a SYSLOG server has been registered.</div></div><div id="oam_oam_syslog"><div class="search_title" docfname="oam_oam_syslog" doctitle="SYSLOG" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used none</div><div class="display_word">2. Definition of Terms Used None</div></div><div id="oam_oam_syslog"><div class="search_title" docfname="oam_oam_syslog" doctitle="SYSLOG" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details the syslog function is described below. logging occurs in ram, and can accumulate up to 10,000 items. backup to flash rom can be performed by the following means. automatic backup performed every hour since system boot manual backup performed by the save logging command backup performed when the write command is executed successfully the accumulated logs can be viewed by the show logging command. it can also be deleted by the clear logging command. the show logging command shows the information in ram. the log information for this product is based on the premise that the information in ram and flash rom always matches. (when the system starts, the log information in flash rom is applied to ram, and the service is started. the log information in ram is not deleted following execution of a backup.) log transmission occurs only if the notification destination (syslog server) has been registered. you can use the logging host command to register up to two notification destinations. specify the notification destination either by ip address or fqdn. as the port number of the notification destination, the default port number 514 is used. (this setting cannot be freely set by the user.) the logging facility command can be used to specify the facility value of log notifications. the factory default setting is local0(16). the logging format command can be used to change the format of log notifications to not include the header portion (timestamp and hostname). the following are log examples. without the format specified (no logging format) <134>jan  1 00:00:00 yamaha [     imi]:inf: configuration file is saved in "config0" with the format specified (logging format legacy) <134>[     imi]:inf: configuration file is saved in "config0" the level of log that is transmitted (syslog priority) can be set using the logging trap command. this product allows you to enable or disable output for each level of log. with the factory settings, the output-level enables only information and error. the logging backup sd command enables syslog backup to the sd card. if syslog backup to the sd card is enabled, executing the save logging command will save the dated log file to the sd card.</div><div class="display_word">3. Function Details The SYSLOG function is described below. Logging occurs in RAM, and can accumulate up to 10,000 items. Backup to Flash ROM can be performed by the following means. Automatic backup performed every hour since system boot Manual backup performed by the save logging command Backup performed when the write command is executed successfully The accumulated logs can be viewed by the show logging command. It can also be deleted by the clear logging command. The show logging command shows the information in RAM. The log information for this product is based on the premise that the information in RAM and flash ROM always matches. (When the system starts, the log information in flash ROM is applied to RAM, and the service is started. The log information in RAM is not deleted following execution of a backup.) Log transmission occurs only if the notification destination (SYSLOG server) has been registered. You can use the logging host command to register up to two notification destinations. Specify the notification destination either by IP address or FQDN. As the port number of the notification destination, the default port number 514 is used. (This setting cannot be freely set by the user.) The logging facility command can be used to specify the facility value of log notifications. The factory default setting is local0(16). The logging format command can be used to change the format of log notifications to not include the header portion (timestamp and hostname). The following are log examples. Without the format specified (no logging format) <134>Jan  1 00:00:00 Yamaha [     IMI]:inf: Configuration file is saved in "config0" With the format specified (logging format legacy) <134>[     IMI]:inf: Configuration file is saved in "config0" The level of log that is transmitted (SYSLOG priority) can be set using the logging trap command. This product allows you to enable or disable output for each level of log. With the factory settings, the output-level enables only Information and Error. The logging backup sd command enables SYSLOG backup to the SD card. If SYSLOG backup to the SD card is enabled, executing the save logging command will save the dated log file to the SD card.</div></div><div id="oam_oam_syslog"><div class="search_title" docfname="oam_oam_syslog" doctitle="SYSLOG" link="#関連コマンド一覧">4. List of related commands</div><div class="search_word">4. list of related commands related commands are indicated below. for details, refer to the command reference. function name command name set log output level logging trap set log console output logging stdout set log notification destination (syslog server) logging host change the log notification format logging format back up log save logging clear log clear logging show log show logging set sd card backup of log logging backup sd set the logging facility value logging facility</div><div class="display_word">4. List of related commands Related commands are indicated below. For details, refer to the Command Reference. Function name Command name Set log output level logging trap Set log console output logging stdout Set log notification destination (SYSLOG server) logging host Change the log notification format logging format Back up log save logging Clear log clear logging Show log show logging Set SD card backup of log logging backup sd Set the logging facility value logging facility</div></div><div id="oam_oam_syslog"><div class="search_title" docfname="oam_oam_syslog" doctitle="SYSLOG" link="#コマンド設定例">5. Examples of Command Settings</div><div class="search_word">5. examples of command settings enable debug-level log output, and start log output to the syslog server (192.168.1.100) with a facility value of 10. also output informational-level log to the console. yamaha(config)# logging trap debug (1) yamaha(config)# logging facility 10 (2) yamaha(config)# logging host 192.168.1.100 (3) yamaha(config)# logging stdout info (4) 1 enable the debug-level log output 2 set the facility value to 10 3 register a syslog server 4 output an informational-level log to the console stop notifications to the syslog server. yamaha(config)# no logging host save and show the accumulated log information. yamaha# save logging (1) yamaha# show logging (2) 2018/03/08 20:42:46: [ session]:inf: login succeeded as (noname) for http: 192.168.1.402018/03/09 10:06:42: [     nsm]:inf: interface port1.11 changed state to down2018/03/09 10:09:48: [ session]:inf: logout timer expired as (noname) from http: 192.168.1.402018/03/09 16:19:36: [     nsm]:inf: interface port1.17 changed state to up : 1 save the log in ram to rom 2 show the accumulated logs clear the accumulated log information. yamaha# clear logging (1) yamaha# show logging (2) (3) 1 clear all accumulated logs 2 show the logs 3 nothing is shown because they have been erased</div><div class="display_word">5. Examples of Command Settings Enable debug-level log output, and start log output to the SYSLOG server (192.168.1.100) with a facility value of 10. Also output informational-level log to the console. Yamaha(config)# logging trap debug (1) Yamaha(config)# logging facility 10 (2) Yamaha(config)# logging host 192.168.1.100 (3) Yamaha(config)# logging stdout info (4) 1 Enable the debug-level log output 2 Set the facility value to 10 3 Register a SYSLOG server 4 Output an informational-level log to the console Stop notifications to the SYSLOG server. Yamaha(config)# no logging host Save and show the accumulated log information. Yamaha# save logging (1) Yamaha# show logging (2) 2018/03/08 20:42:46: [ SESSION]:inf: Login succeeded as (noname) for HTTP: 192.168.1.402018/03/09 10:06:42: [     NSM]:inf: Interface port1.11 changed state to down2018/03/09 10:09:48: [ SESSION]:inf: Logout timer expired as (noname) from HTTP: 192.168.1.402018/03/09 16:19:36: [     NSM]:inf: Interface port1.17 changed state to up : 1 Save the log in RAM to ROM 2 Show the accumulated logs Clear the accumulated log information. Yamaha# clear logging (1) Yamaha# show logging (2) (3) 1 Clear all accumulated logs 2 Show the logs 3 Nothing is shown because they have been erased</div></div><div id="oam_oam_syslog"><div class="search_title" docfname="oam_oam_syslog" doctitle="SYSLOG" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution none</div><div class="display_word">6. Points of Caution None</div></div><div id="oam_oam_syslog"><div class="search_title" docfname="oam_oam_syslog" doctitle="SYSLOG" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation none</div><div class="display_word">7. Related Documentation None</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#システム自己診断">System Self-Diagnostics</div><div class="search_word">system self-diagnostics</div><div class="display_word">System Self-Diagnostics</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product includes system self-diagnostic function. the system self-diagnostic function detects the following types of errors. startup process errors hardware component errors interface (ethernet port) rtc sfp fan poe controller thermal sensor temperature anomaly</div><div class="display_word">1. Function Overview This product includes system self-diagnostic function. The system self-diagnostic function detects the following types of errors. Startup process errors Hardware component errors Interface (Ethernet port) RTC SFP Fan PoE controller Thermal sensor Temperature anomaly</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used rtc（real-time clock） device used to manage time poe controller device used for poe (power over ethernet) control. pse（power sourcing equipment） a device that supplies power. on this page it is considered synonymous with poe controller. packet processor device used to process packets.</div><div class="display_word">2. Definition of Terms Used RTC（Real-Time Clock） Device used to manage time PoE Controller Device used for PoE (power over Ethernet) control. PSE（Power Sourcing Equipment） A device that supplies power. On this page it is considered synonymous with PoE controller. Packet Processor Device used to process packets.</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#診断">3.1. Diagnostics</div><div class="search_word">3.1. diagnostics three types of system self-diagnostic functionality, either boot-up diagnostics, on-demand diagnostics, or health monitoring diagnostics, are available depending on when diagnostics are performed. the features of each type are indicated below. boot-up diagnostics automatically executes whenever the system starts up. detects startup process errors and hardware component errors (rtc, etc.). on-demand diagnostics can be executed at user-specified times set using the system-diagnostics on-demand execute command. detects hardware component (interface) errors. all ports are shut down during diagnostics and the system is restarted when finished. health monitoring diagnostics running continuously in the background during system operation detects hardware component errors (fan errors, etc.) and temperature abnormalities. health monitoring diagnostics results are displayed via the gui and led indicators (only some test results are indicated via the led indicators). each diagnosis runs multiple tests. the tests performed for each diagnosis are indicated below. for a detailed list of tests performed, refer to test details . test type boot-up diagnostics on-demand diagnostics health monitoring diagnostics loading test yes rtc test yes packet processor test yes phy test yes thermal test yes fan test yes thermal sensor test yes poe test yes sfp test yes</div><div class="display_word">3.1. Diagnostics Three types of system self-diagnostic functionality, either boot-up diagnostics, on-demand diagnostics, or health monitoring diagnostics, are available depending on when diagnostics are performed. The features of each type are indicated below. Boot-up diagnostics Automatically executes whenever the system starts up. Detects startup process errors and hardware component errors (RTC, etc.). On-demand diagnostics Can be executed at user-specified times set using the system-diagnostics on-demand execute command. Detects hardware component (interface) errors. All ports are shut down during diagnostics and the system is restarted when finished. Health monitoring diagnostics Running continuously in the background during system operation Detects hardware component errors (fan errors, etc.) and temperature abnormalities. Health monitoring diagnostics results are displayed via the GUI and LED indicators (only some test results are indicated via the LED indicators). Each diagnosis runs multiple tests. The tests performed for each diagnosis are indicated below. For a detailed list of tests performed, refer to Test Details . Test Type Boot-up diagnostics On-demand diagnostics Health monitoring diagnostics Loading Test Yes RTC Test Yes Packet Processor Test Yes PHY Test Yes Thermal Test Yes Fan Test Yes Thermal Sensor Test Yes PoE Test Yes SFP Test Yes</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#診断結果表示">3.2. Diagnostic results displayed</div><div class="search_word">3.2. diagnostic results displayed diagnostic results can be checked using the show system-diagnostics command. though the system is automatically restarted after on-demand diagnostics, diagnostic results can be confirmed after restarting.</div><div class="display_word">3.2. Diagnostic results displayed Diagnostic results can be checked using the show system-diagnostics command. Though the system is automatically restarted after on-demand diagnostics, diagnostic results can be confirmed after restarting.</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#オンデマンド診断結果削除">3.3. Deleting on-demand diagnostics results</div><div class="search_word">3.3. deleting on-demand diagnostics results on-demand diagnostics results can be deleted using the clear system-diagnostics on-demand command.</div><div class="display_word">3.3. Deleting on-demand diagnostics results On-demand diagnostics results can be deleted using the clear system-diagnostics on-demand command.</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#テスト詳細">4. Test Details</div><div class="search_word">4. test details details about each test item are indicated below.</div><div class="display_word">4. Test Details Details about each test item are indicated below.</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#loading-test">4.1. Loading Test</div><div class="search_word">4.1. loading test this verifies the loading status of software modules. a “pass” result is output if all modules are successfully loaded, whereas a “fail” result is output if even one module fails to load. the show system-diagnostics command does not indicate information about modules that failed to load. to identify which module failed to load, use the show logging command to search the following log. note: xxxx part shows the module name. [   hamon]:err: an unexpected error has occurred. (xxxx deamon)</div><div class="display_word">4.1. Loading Test This verifies the loading status of software modules. A “Pass” result is output if all modules are successfully loaded, whereas a “Fail” result is output if even one module fails to load. The show system-diagnostics command does not indicate information about modules that failed to load. To identify which module failed to load, use the show logging command to search the following log. Note: XXXX part shows the module name. [   HAMON]:err: An unexpected error has occurred. (XXXX deamon)</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#rtc-test">4.2. RTC Test</div><div class="search_word">4.2. rtc test this verifies access to the rtc register. a time value is obtained from the rtc two times, resulting in “pass” if the time value changed or “fail” if the time values are identical. a “fail” result also occurs if the test fails to obtain a time value from the rtc (or load the register).</div><div class="display_word">4.2. RTC Test This verifies access to the RTC register. A time value is obtained from the RTC two times, resulting in “Pass” if the time value changed or “Fail” if the time values are identical. A “Fail” result also occurs if the test fails to obtain a time value from the RTC (or load the register).</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#packet-processor-test">4.3. Packet Processor Test</div><div class="search_word">4.3. packet processor test this verifies accessing the packet processor register. a “pass” result occurs if the value written in the packet processor register matches the loaded value, whereas a “fail” result occurs if the values do not match. a “fail” result also occurs if the test fails to access the register.</div><div class="display_word">4.3. Packet Processor Test This verifies accessing the packet processor register. A “Pass” result occurs if the value written in the packet processor register matches the loaded value, whereas a “Fail” result occurs if the values do not match. A “Fail” result also occurs if the test fails to access the register.</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#phy-test">4.4. PHY Test</div><div class="search_word">4.4. phy test this verifies access to the phy register. a “pass” result occurs if the value written in the phy register matches the loaded value, whereas a “fail” result occurs if the values do not match. a “fail” result also occurs if the test fails to access the register.</div><div class="display_word">4.4. PHY Test This verifies access to the PHY register. A “Pass” result occurs if the value written in the PHY register matches the loaded value, whereas a “Fail” result occurs if the values do not match. A “Fail” result also occurs if the test fails to access the register.</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#thermal-test">4.5. Thermal Test</div><div class="search_word">4.5. thermal test this monitors the cpu, phy, sfp module, thermal sensor (chassis), and pse temperatures. if the temperature exceeds a threshold value, a warning is indicated.</div><div class="display_word">4.5. Thermal Test This monitors the CPU, PHY, SFP module, thermal sensor (chassis), and PSE temperatures. If the temperature exceeds a threshold value, a warning is indicated.</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#fan-test">4.6. Fan Test</div><div class="search_word">4.6. fan test this monitors the fan speed. it indicates a warning if the fan stops rotating or the rotation speed increases.</div><div class="display_word">4.6. Fan Test This monitors the fan speed. It indicates a warning if the fan stops rotating or the rotation speed increases.</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#thermal-sensor-test">4.7. Thermal Sensor Test</div><div class="search_word">4.7. thermal sensor test this monitors the thermal sensors. it indicates a warning if a thermal sensor abnormality has been detected.</div><div class="display_word">4.7. Thermal Sensor Test This monitors the thermal sensors. It indicates a warning if a thermal sensor abnormality has been detected.</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#poe-test">4.8. PoE Test</div><div class="search_word">4.8. poe test this monitors the poe power supply status. it indicates a warning if an error occurs in the poe power supply control.</div><div class="display_word">4.8. PoE Test This monitors the PoE power supply status. It indicates a warning if an error occurs in the PoE power supply control.</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#sfp-test">4.9. SFP Test</div><div class="search_word">4.9. sfp test this monitors the sfp module optical input level. it generates a warning if the optical input level exceeds a certain range.</div><div class="display_word">4.9. SFP Test This monitors the SFP module optical input level. It generates a warning if the optical input level exceeds a certain range.</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#関連コマンド">5. Related Commands</div><div class="search_word">5. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands display system self-diagnostic results show system-diagnostics execute on-demand diagnostics system-diagnostics on-demand execute discard on-demand diagnostics results clear system-diagnostics on-demand</div><div class="display_word">5. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Display system self-diagnostic results show system-diagnostics Execute on-demand diagnostics system-diagnostics on-demand execute Discard on-demand diagnostics results clear system-diagnostics on-demand</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#コマンド実行例">6. Examples of Command Execution</div><div class="search_word">6. examples of command execution</div><div class="display_word">6. Examples of Command Execution</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#システム自己診断結果の表示">6.1. Display system self-diagnostic results</div><div class="search_word">6.1. display system self-diagnostic results check the system self-diagnostics results as follows. yamaha#show system-diagnosticstest results: (p = pass, f = fail, u = untested, n = normal, w = warning)- bootup  loading test: pass  rtc test: pass  packet processor test: pass- on-demandlast on-demand diagnostics information: date     : 2021/07/07 09:00:00 +09:00 bootrom  : ver.1.01 firmware : rev.2.02.23  phy test:    port   1   2   3   4   5   6   7   8   9  10  11  12  13  14  15  16    --------------------------------------------------------------------           p   p   p   p   p   p   p   p   p   p   p   p   p   p   p   p    port  17  18    ------------           p   p- health monitoring  thermal test:    cpu: normal, phy: normal, sfp: normal, ts: normal, pse: normal  fan test: normal  thermal sensor test: normal  poe test:    port   1   2   3   4   5   6   7   8   9  10  11  12  13  14  15  16    --------------------------------------------------------------------           n   n   n   n   n   n   n   n   n   n   n   n   n   n   n   n  sfp test:    port  17  18    ------------           n   n</div><div class="display_word">6.1. Display system self-diagnostic results Check the system self-diagnostics results as follows. Yamaha#show system-diagnosticsTest results: (P = Pass, F = Fail, U = Untested, N = Normal, W = Warning)- Bootup  Loading Test: Pass  RTC Test: Pass  Packet Processor Test: Pass- On-demandLast on-demand diagnostics information: Date     : 2021/07/07 09:00:00 +09:00 BootROM  : Ver.1.01 Firmware : Rev.2.02.23  PHY Test:    Port   1   2   3   4   5   6   7   8   9  10  11  12  13  14  15  16    --------------------------------------------------------------------           P   P   P   P   P   P   P   P   P   P   P   P   P   P   P   P    Port  17  18    ------------           P   P- Health monitoring  Thermal Test:    CPU: Normal, PHY: Normal, SFP: Normal, TS: Normal, PSE: Normal  Fan Test: Normal  Thermal Sensor Test: Normal  PoE Test:    Port   1   2   3   4   5   6   7   8   9  10  11  12  13  14  15  16    --------------------------------------------------------------------           N   N   N   N   N   N   N   N   N   N   N   N   N   N   N   N  SFP Test:    Port  17  18    ------------           N   N</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#オンデマンド診断の実行">6.2. Performing on-demand diagnostics</div><div class="search_word">6.2. performing on-demand diagnostics perform on-demand diagnostics as follows. yamaha#system-diagnostics on-demand executethe system will be rebooted after diagnostics. continue ? (y/n) yon-demand diagnostics completed (pass). reboot immediately...</div><div class="display_word">6.2. Performing on-demand diagnostics Perform on-demand diagnostics as follows. Yamaha#system-diagnostics on-demand executeThe system will be rebooted after diagnostics. Continue ? (y/n) yon-demand diagnostics completed (pass). reboot immediately...</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#オンデマンド診断結果の削除">6.3. Discard on-demand diagnostics results</div><div class="search_word">6.3. discard on-demand diagnostics results delete the on-demand diagnostic results as follows. yamaha#clear system-diagnostics on-demand</div><div class="display_word">6.3. Discard on-demand diagnostics results Delete the on-demand diagnostic results as follows. Yamaha#clear system-diagnostics on-demand</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#注意事項">7. Points of Caution</div><div class="search_word">7. points of caution all ports are automatically shut down and restarted whenever on-demand diagnostics are performed. therefore, use particular caution before executing on-demand diagnostics while the system is being operated. on-demand diagnostics are only executed if the stack status is standalone or disabled. to perform on-demand diagnostics when a stack is configured, first disconnect the connections between member switches. if online diagnostics are performed remotely, such as via telnet or the web console, simplified results cannot be displayed before restarting because all ports are shut down during diagnostics. use the show system-diagnostics command to check diagnostic results after restarting.</div><div class="display_word">7. Points of Caution All ports are automatically shut down and restarted whenever on-demand diagnostics are performed. Therefore, use particular caution before executing on-demand diagnostics while the system is being operated. On-demand diagnostics are only executed if the stack status is standalone or disabled. To perform on-demand diagnostics when a stack is configured, first disconnect the connections between member switches. If online diagnostics are performed remotely, such as via Telnet or the web console, simplified results cannot be displayed before restarting because all ports are shut down during diagnostics. Use the show system-diagnostics command to check diagnostic results after restarting.</div></div><div id="oam_oam_system_diag"><div class="search_title" docfname="oam_oam_system_diag" doctitle="System" link="#関連文書">8. Related Documentation</div><div class="search_word">8. related documentation none</div><div class="display_word">8. Related Documentation None</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#時刻管理">Time Management</div><div class="search_word">time management</div><div class="display_word">Time Management</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product provides the functions shown below for managing the date and time. manual (user-configured) date/time information setting function automatic date/time setting information function via network time zone setting function function for setting “daylight saving time” (dst or “daylight time”) settings</div><div class="display_word">1. Function Overview This product provides the functions shown below for managing the date and time. Manual (user-configured) date/time information setting function Automatic date/time setting information function via network Time zone setting function Function for setting “daylight saving time” (DST or “daylight time”) settings</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used utc（coordinated universal time） this is an official time used when recording worldwide times. utc is used as a basis to determine standard time in all countries around the world. for instance, japan (jst, or japan standard time) is nine hours ahead of coordinated universal time, and is thus shown as “+0900 (jst)”. sntp（simple network time protocol） this is a simple protocol to correct clocks by using sntp packets. this protocol is defined in rfc4330.</div><div class="display_word">2. Definition of Terms Used UTC（Coordinated Universal Time） This is an official time used when recording worldwide times. UTC is used as a basis to determine standard time in all countries around the world. For instance, Japan (JST, or Japan standard time) is nine hours ahead of Coordinated Universal Time, and is thus shown as “+0900 (JST)”. SNTP（Simple Network Time Protocol） This is a simple protocol to correct clocks by using SNTP packets. This protocol is defined in RFC4330.</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#日付時刻の手動設定">3.1. Manually setting the date and time</div><div class="search_word">3.1. manually setting the date and time use the clock set command to directly enter clock setting values.</div><div class="display_word">3.1. Manually setting the date and time Use the clock set command to directly enter clock setting values.</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#日付時刻の自動設定">3.2. Automatically setting the date and time</div><div class="search_word">3.2. automatically setting the date and time date and time information is collected from a specified time server, and set in this product. defined in rfc4330, sntp (simple network time protocol) is used as a communication protocol. up to two time servers can be specified using an ipv4 address, ipv6 address, or fully qualified domain name (fqdn). port number 123 is used for the sntp client. (this setting cannot be changed by the user.) the ntpdate command can be used to select one of two methods for automatically setting date and time settings. one-shot update (a function to update when a command is inputted) interval update (a function to update in a 1–24-hour cycle from command input) if clock settings are synchronized with two time servers specified, queries are processed in the order they are displayed by the show ntpdate command, which is ntp server 1 and then ntp server 2. queries to ntp server 2 are only processed if synchronization with ntp server 1 fails. given default settings, one hour is specified as the interval update cycle. however, when the default time cannot be set right after booting up the system, the time server will be queried in a one-minute cycle, regardless of the interval cycle time. synchronization with the time server operates with one sampling (the frequency of replies from the server) and with a timeout of 1 second. synchronization is blocked during command execution, and an error message is outputted if a timeout occurs.</div><div class="display_word">3.2. Automatically setting the date and time Date and time information is collected from a specified time server, and set in this product. Defined in RFC4330, SNTP (Simple Network Time Protocol) is used as a communication protocol. Up to two time servers can be specified using an IPv4 address, IPv6 address, or fully qualified domain name (FQDN). Port number 123 is used for the SNTP client. (This setting cannot be changed by the user.) The ntpdate command can be used to select one of two methods for automatically setting date and time settings. One-shot update (a function to update when a command is inputted) Interval update (a function to update in a 1–24-hour cycle from command input) If clock settings are synchronized with two time servers specified, queries are processed in the order they are displayed by the show ntpdate command, which is NTP server 1 and then NTP server 2. Queries to NTP server 2 are only processed if synchronization with NTP server 1 fails. Given default settings, one hour is specified as the interval update cycle. However, when the default time cannot be set right after booting up the system, the time server will be queried in a one-minute cycle, regardless of the interval cycle time. Synchronization with the time server operates with one sampling (the frequency of replies from the server) and with a timeout of 1 second. Synchronization is blocked during command execution, and an error message is outputted if a timeout occurs.</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#タイムゾーンの設定">3.3. Time zone setting</div><div class="search_word">3.3. time zone setting in order to manage the time for the region considered as the “base of daily life”, the “clock timezone” command is used to manage the time zone of the users, and reflect this into the time. the time zone can be set in ±1 hour increments for coordinated universal time (utc), from -12 hours to +13 hours. the default time zone value for this product is +9.0 .</div><div class="display_word">3.3. Time zone setting In order to manage the time for the region considered as the “base of daily life”, the “clock timezone” command is used to manage the time zone of the users, and reflect this into the time. The time zone can be set in ±1 hour increments for Coordinated Universal Time (UTC), from -12 hours to +13 hours. The default time zone value for this product is +9.0 .</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#サマータイムの設定">3.4. Daylight saving time setting</div><div class="search_word">3.4. daylight saving time setting users can set “daylight saving time” (dst or “daylight time”) settings using the clock summer-time command. the following parameter settings are specified. time zone name the time zone name is displayed when daylight saving time is in effect. start and end times of daylight saving time you can specify the time in one of two ways: recurring if daylight saving time occurs every year for the same period, then this specifies the week and day of the month it occurs. specific dates this specifies the specific dates daylight saving time is applied. offset this specifies how long (minutes) to extend the daylight saving time period. the setting range is from 1 to 1440 minutes. the setting value is 60 minutes unless specified otherwise. overlapping daylight saving time periods cannot be specified. daylight saving time settings can be checked using the show clock detail command.</div><div class="display_word">3.4. Daylight saving time setting Users can set “daylight saving time” (DST or “daylight time”) settings using the clock summer-time command. The following parameter settings are specified. Time zone name The time zone name is displayed when daylight saving time is in effect. Start and end times of daylight saving time You can specify the time in one of two ways: Recurring If daylight saving time occurs every year for the same period, then this specifies the week and day of the month it occurs. Specific dates This specifies the specific dates daylight saving time is applied. Offset This specifies how long (minutes) to extend the daylight saving time period. The setting range is from 1 to 1440 minutes. The setting value is 60 minutes unless specified otherwise. Overlapping daylight saving time periods cannot be specified. Daylight saving time settings can be checked using the show clock detail command.</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details, refer to the command reference. operations operating commands set clock manually clock set time zone setting clock timezone set daylight saving time settings (recurring) clock summer-time recurring set daylight saving time settings (specific date) clock summer-time date show current time show clock set ntp server ntpdate server synchronize time from ntp server (one-shot update) ntpdate oneshot synchronize time from ntp server (update interval) ntpdate interval show ntp server time synchronization settings show ntpdate</div><div class="display_word">4. Related Commands Related commands are indicated below. For details, refer to the Command Reference. Operations Operating commands Set clock manually clock set Time zone setting clock timezone Set daylight saving time settings (recurring) clock summer-time recurring Set daylight saving time settings (specific date) clock summer-time date Show current time show clock Set NTP server ntpdate server Synchronize time from NTP server (one-shot update) ntpdate oneshot Synchronize time from NTP server (update interval) ntpdate interval Show NTP server time synchronization settings show ntpdate</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#時刻の手動設定">5.1. Set clock manually</div><div class="search_word">5.1. set clock manually in this example, the time zone is set to jst and the current time is set to 2014.01.21 15:50:59 . yamaha#configure terminalyamaha(config)#clock timezone jst (1) yamaha(config)#exityamaha#clock set 15:50:59 jan 21 2014 (2) yamaha#show clock (3) 15:50:59 jst tue jan 21 2014 1 time zone setting 2 time settings 3 show current time</div><div class="display_word">5.1. Set clock manually In this example, the time zone is set to JST and the current time is set to 2014.01.21 15:50:59 . Yamaha#configure terminalYamaha(config)#clock timezone JST (1) Yamaha(config)#exitYamaha#clock set 15:50:59 Jan 21 2014 (2) Yamaha#show clock (3) 15:50:59 JST Tue Jan 21 2014 1 Time zone setting 2 Time settings 3 Show current time</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#時刻の自動設定">5.2. Automatically setting the time</div><div class="search_word">5.2. automatically setting the time in this example, the time zone is set to +9.00 and the local address 192.168.1.1 and ntp.nict.jp are specified as the ntp servers. also, the ntp server update cycle is changed to once every 24 hours . yamaha#configure terminalyamaha(config)#clock timezone +9:00 (1) yamaha(config)#ntpdate server ipv4 192.168.1.1 (2) yamaha(config)#ntpdate server name ntp.nict.jp (3) yamaha(config)#ntpdate interval 24 (4) yamaha(config)#exityamaha#show clock (5) 10:03:20 +9:00 mon dec 12 2016yamaha#show ntpdate (6) ntp server 1 : 192.168.100.1ntp server 2 : ntp.nict.jpadjust time : mon dec 12 10:03:15 2016 + interval 24 hourssync server : 192.168.100.1 1 time zone setting 2 set ntp server 3 set ntp server 4 set ntp server update cycle to 24 hours 5 show current time 6 show ntp time synchronization settings</div><div class="display_word">5.2. Automatically setting the time In this example, the time zone is set to +9.00 and the local address 192.168.1.1 and ntp.nict.jp are specified as the NTP servers. Also, the NTP server update cycle is changed to once every 24 hours . Yamaha#configure terminalYamaha(config)#clock timezone +9:00 (1) Yamaha(config)#ntpdate server ipv4 192.168.1.1 (2) Yamaha(config)#ntpdate server name ntp.nict.jp (3) Yamaha(config)#ntpdate interval 24 (4) Yamaha(config)#exitYamaha#show clock (5) 10:03:20 +9:00 Mon Dec 12 2016Yamaha#show ntpdate (6) NTP server 1 : 192.168.100.1NTP server 2 : ntp.nict.jpadjust time : Mon Dec 12 10:03:15 2016 + interval 24 hourssync server : 192.168.100.1 1 Time zone setting 2 Set NTP server 3 Set NTP server 4 Set NTP server update cycle to 24 hours 5 Show current time 6 Show NTP time synchronization settings</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#サマータイムの設定">5.3. Daylight saving time setting</div><div class="search_word">5.3. daylight saving time setting</div><div class="display_word">5.3. Daylight saving time setting</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#繰り返し">5.3.1. Recurring</div><div class="search_word">5.3.1. recurring in this example, daylight saving time is set to occur every year starting from 2 am on the second sunday of march to 2 am on the first sunday of november. yamaha#configure terminalyamaha(config)#clock summer-time jdt recurring 2 sun mar 2:00 1 sun nov 2:00 (1) yamaha(config)#exityamaha#show clock detail (2) fri jan  1 00:00:20 jst 2021summer time  type   : recurring  offset : 60 (min)  from   : sun mar 14 02:00:00 jst 2021 (3) to     : sun nov 7 02:00:00 jdt 2021 1 daylight saving time setting 2 check the daylight saving time settings 3 show the actual dates of the next (or currently in effect) daylight saving time period</div><div class="display_word">5.3.1. Recurring In this example, daylight saving time is set to occur every year starting from 2 AM on the second Sunday of March to 2 AM on the first Sunday of November. Yamaha#configure terminalYamaha(config)#clock summer-time JDT recurring 2 Sun Mar 2:00 1 Sun Nov 2:00 (1) Yamaha(config)#exitYamaha#show clock detail (2) Fri Jan  1 00:00:20 JST 2021Summer Time  Type   : Recurring  Offset : 60 (min)  From   : Sun Mar 14 02:00:00 JST 2021 (3) To     : Sun Nov 7 02:00:00 JDT 2021 1 Daylight saving time setting 2 Check the daylight saving time settings 3 Show the actual dates of the next (or currently in effect) daylight saving time period</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#日付指定">5.3.2. Specific dates</div><div class="search_word">5.3.2. specific dates in this example, the settings specify starting daylight saving time at 2 am on march 14, 2021, and ending it on november 7, 2021. yamaha#configure terminalyamaha(config)#clock summer-time jdt date mar 14 2021 2:00 nov 7 2021 2:00 (1) yamaha(config)#exityamaha#show clock detail (2) fri jan  1 00:02:54 jst 2021summer time  type   : date  offset : 60 (min)  from   : sun mar 14 02:00:00 jst 2021  to     : sun nov 7 02:00:00 jdt 2021 1 daylight saving time setting 2 check the daylight saving time settings</div><div class="display_word">5.3.2. Specific dates In this example, the settings specify starting daylight saving time at 2 AM on March 14, 2021, and ending it on November 7, 2021. Yamaha#configure terminalYamaha(config)#clock summer-time JDT date Mar 14 2021 2:00 Nov 7 2021 2:00 (1) Yamaha(config)#exitYamaha#show clock detail (2) Fri Jan  1 00:02:54 JST 2021Summer Time  Type   : Date  Offset : 60 (min)  From   : Sun Mar 14 02:00:00 JST 2021  To     : Sun Nov 7 02:00:00 JDT 2021 1 Daylight saving time setting 2 Check the daylight saving time settings</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution none</div><div class="display_word">6. Points of Caution None</div></div><div id="oam_oam_time"><div class="search_title" docfname="oam_oam_time" doctitle="Time" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation rfc 4330: simple network time protocol (sntp) version 4 for ipv4, ipv6 and osi</div><div class="display_word">7. Related Documentation RFC 4330: Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#ユーザーアカウント管理">User Account Management</div><div class="search_word">user account management</div><div class="display_word">User Account Management</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product provides the functions shown below for managing user accounts. functions for setting user information functions for user authentication by user name and password</div><div class="display_word">1. Function Overview This product provides the functions shown below for managing user accounts. Functions for setting user information Functions for user authentication by user name and password</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used default administrative user users with administrator rights specified in default factory settings. username: admin and password: admin administrative user users with administrator rights. administrative users are users with the privilege option switched on using the username command. guest user users without administrator rights and that require entering the privileged password (administrative password) in order to access the privileged exec mode. guest users are users with the privilege option switched off using the username command. privileged password (administrative password) the password used to assign administrator rights and specified using the enable password command. unnamed user users with a blank username setting. rev. 2.02.23 or earlier firmware versions permitted using unnamed user accounts under factory default settings, but unnamed user accounts were eliminated for newer firmware versions with stronger user account management functionality.</div><div class="display_word">2. Definition of Terms Used Default Administrative User Users with administrator rights specified in default factory settings. Username: admin and password: admin Administrative User Users with administrator rights. Administrative users are users with the privilege option switched on using the username command. Guest User Users without administrator rights and that require entering the privileged password (administrative password) in order to access the privileged EXEC mode. Guest users are users with the privilege option switched off using the username command. Privileged Password (Administrative Password) The password used to assign administrator rights and specified using the enable password command. Unnamed User Users with a blank username setting. Rev. 2.02.23 or earlier firmware versions permitted using unnamed user accounts under factory default settings, but unnamed user accounts were eliminated for newer firmware versions with stronger user account management functionality.</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#ユーザーアカウント機能の設定">3.1. User account function settings</div><div class="search_word">3.1. user account function settings</div><div class="display_word">3.1. User account function settings</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#ユーザー情報の設定">3.1.1. User information settings</div><div class="search_word">3.1.1. user information settings use the username command to specify the following user information. user name password assignment of administrator rights with factory default settings, the administrative username and password are both “admin”.</div><div class="display_word">3.1.1. User information settings Use the username command to specify the following user information. User name Password Assignment of administrator rights With factory default settings, the administrative username and password are both “admin”.</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#特権パスワード管理パスワードの設定">3.1.2. Setting the privileged password (administrative password)</div><div class="search_word">3.1.2. setting the privileged password (administrative password) the privileged password (administrative password) is set using the enable password command. privileged passwords (administrative passwords) are used for the following applications. to initialize devices to transition users without administrator rights to the privileged exec mode by using the console to use a tftp client to send a config file or firmware to the switch the factory default privileged password (default administrative password) setting is admin , but the operations described above cannot be performed if the privileged password (default administrative password) is set to the default setting. to perform any of those operations, change the privileged password (administrative password) in advance.</div><div class="display_word">3.1.2. Setting the privileged password (administrative password) The privileged password (administrative password) is set using the enable password command. Privileged passwords (administrative passwords) are used for the following applications. To initialize devices To transition users without administrator rights to the privileged EXEC mode by using the console To use a TFTP client to send a config file or firmware to the switch The factory default privileged password (default administrative password) setting is admin , but the operations described above cannot be performed if the privileged password (default administrative password) is set to the default setting. To perform any of those operations, change the privileged password (administrative password) in advance.</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#管理者権限">3.1.3. Administrator rights</div><div class="search_word">3.1.3. administrator rights user login operations can be restricted depending on whether or not the user has administrator rights. users with administrator rights can change device settings or update firmware. users without administrator rights can only view device information without changing any settings. specifically, the following differences apply depending on whether or not the user has administrator rights. console web gui administrative user (with rights) guest user (without rights) administrative user (with rights) guest user (without rights) show device information yes yes yes yes view settings yes no yes limited (*1) change settings yes no yes no restart or initialize devices yes no yes no update firmware yes no yes no *1: cannot view passwords or other security-related settings. once the enable command is executed and the privileged password (administrative password) is entered, the privileged exec mode can be accessed to perform operations equivalent to an administrative user, even if logged in as a guest user. for information about the rights required to execute each command, refer to the command reference.</div><div class="display_word">3.1.3. Administrator rights User login operations can be restricted depending on whether or not the user has administrator rights. Users with administrator rights can change device settings or update firmware. Users without administrator rights can only view device information without changing any settings. Specifically, the following differences apply depending on whether or not the user has administrator rights. Console Web GUI Administrative user (with rights) Guest user (without rights) Administrative user (with rights) Guest user (without rights) Show device information Yes Yes Yes Yes View settings Yes No Yes Limited (*1) Change settings Yes No Yes No Restart or initialize devices Yes No Yes No Update firmware Yes No Yes No *1: Cannot view passwords or other security-related settings. Once the enable command is executed and the privileged password (administrative password) is entered, the privileged EXEC mode can be accessed to perform operations equivalent to an administrative user, even if logged in as a guest user. For information about the rights required to execute each command, refer to the command reference.</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#パスワードの暗号化">3.1.4. Encrypt password</div><div class="search_word">3.1.4. encrypt password specified passwords can be encrypted using the password-encryption command. to encrypt a password, specify the password-encryption enable setting. once a password has been encrypted, it cannot be restored to an unencrypted character string state, even by specifying the password-encryption disable setting. encryption applies to the passwords specified by the following commands. enable password command username command</div><div class="display_word">3.1.4. Encrypt password Specified passwords can be encrypted using the password-encryption command. To encrypt a password, specify the password-encryption enable setting. Once a password has been encrypted, it cannot be restored to an unencrypted character string state, even by specifying the password-encryption disable setting. Encryption applies to the passwords specified by the following commands. enable password command username command</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#ユーザーの認証">3.2. User authentication</div><div class="search_word">3.2. user authentication</div><div class="display_word">3.2. User authentication</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#コンソールにログインする場合">3.2.1. When logging in to the console</div><div class="search_word">3.2.1. when logging in to the console when the following login prompt appears after connecting to the console, log in by entering the specified username and password. username:password: for factory default settings, log in by entering “admin” as the default administrative username (and  “admin” as the password). after using “admin” to log in, the password must be changed to specify a new password. username: adminpassword: (1) swx2310p-28gt rev.2.02.06 (tue mar 13 08:41:39 2018)  copyright (c) 2015-2016 yamaha corporation. all rights reserved.please change the default password for admin.new password: (2) new password(confirm): (3) saving ...succeeded to write configuration 1 enter “admin” 2 enter the new password. 3 enter the same password again. if an incorrect password is entered three successive times, login by that same user is restricted for one minute. username: userpassword:% incorrect username or password, or login as user is restricted.password:% incorrect username or password, or login as user is restricted.password:% incorrect username or password, or blocked upon 3 failed login attempts for user.% please try again later. if a login restriction occurs, the following message is output in the info level syslog. connection method output message serial console login access from serial console as {username} was restricted telnet login access from telnet as {username} was restricted: {ip address} ssh login access from ssh as {user name} was restricted: {ip address} web gui login access from http as {username} was restricted: {ip address} note that if a user with a login restriction enters an incorrect password again, the remaining time until the restriction is cancelled is reset to one minute again.</div><div class="display_word">3.2.1. When logging in to the console When the following login prompt appears after connecting to the console, log in by entering the specified username and password. Username:Password: For factory default settings, log in by entering “admin” as the default administrative username (and  “admin” as the password). After using “admin” to log in, the password must be changed to specify a new password. Username: adminPassword: (1) SWX2310P-28GT Rev.2.02.06 (Tue Mar 13 08:41:39 2018)  Copyright (c) 2015-2016 Yamaha Corporation. All Rights Reserved.Please change the default password for admin.New Password: (2) New Password(Confirm): (3) Saving ...Succeeded to write configuration 1 Enter “admin” 2 Enter the new password. 3 Enter the same password again. If an incorrect password is entered three successive times, login by that same user is restricted for one minute. Username: UserPassword:% Incorrect username or password, or login as User is restricted.Password:% Incorrect username or password, or login as User is restricted.Password:% Incorrect username or password, or blocked upon 3 failed login attempts for User.% Please try again later. If a login restriction occurs, the following message is output in the INFO level SYSLOG. Connection method Output message Serial console Login access from serial console as {username} was restricted TELNET Login access from TELNET as {username} was restricted: {IP address} SSH Login access from SSH as {user name} was restricted: {IP address} Web GUI Login access from HTTP as {username} was restricted: {IP address} Note that if a user with a login restriction enters an incorrect password again, the remaining time until the restriction is cancelled is reset to one minute again.</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#webguiにログインする場合">3.2.2. When logging in to the web GUI</div><div class="search_word">3.2.2. when logging in to the web gui when the following login form appears after accessing the web gui, log in by entering the specified username and password. for factory default settings, log in by entering “admin” as the default administrative username (and  “admin” as the password). if prompted to change the password after using “admin” to log in, specify a new password.</div><div class="display_word">3.2.2. When logging in to the web GUI When the following login form appears after accessing the web GUI, log in by entering the specified username and password. For factory default settings, log in by entering “admin” as the default administrative username (and  “admin” as the password). If prompted to change the password after using “admin” to log in, specify a new password.</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#ログインパスワードを忘れてしまった場合の対処方法">3.3. What to do if you forget your login password</div><div class="search_word">3.3. what to do if you forget your login password if the product is rebooted connected to the serial console and “i” (uppercase letter i) is entered during the booting process, the product can be rebooted with factory default settings. note that the function is disabled if sd card booting is used. bootrom - x.xxbooting from spi flashswx2310p-28gt bootrom ver.1.00      #### enter “i” as soon as the boot rom version is displayed. ####initialize or not ?(y/n) yloading config0 because can't read config in sd card.starting ..............................................loading configuration ... done!swx2310p-28gt rev.2.02.06 (tue mar 13 08:41:39 2018)  copyright (c) 2015-2016 yamaha corporation. all rights reserved.</div><div class="display_word">3.3. What to do if you forget your login password If the product is rebooted connected to the serial console and “I” (uppercase letter I) is entered during the booting process, the product can be rebooted with factory default settings. Note that the function is disabled if SD card booting is used. BootROM - X.XXBooting from SPI flashSWX2310P-28GT BootROM Ver.1.00      #### Enter “I” as soon as the boot ROM version is displayed. ####Initialize or not ?(y/n) yLoading config0 because can't read config in SD card.Starting ..............................................Loading configuration ... Done!SWX2310P-28GT Rev.2.02.06 (Tue Mar 13 08:41:39 2018)  Copyright (c) 2015-2016 Yamaha Corporation. All Rights Reserved.</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details, refer to the command reference. operations operating commands setting the privileged password (administrative password) enable password encrypt password password-encryption set user username show user information show users</div><div class="display_word">4. Related Commands Related commands are indicated below. For details, refer to the Command Reference. Operations Operating commands Setting the privileged password (administrative password) enable password Encrypt password password-encryption Set user username Show user information show users</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#ユーザーを追加する">5.1. Adding a user</div><div class="search_word">5.1. adding a user the following example assigns administrator rights to the user “ yamaha ” and specifies the password “ yamaha_pass ”. yamaha#configure terminalenter configuration commands, one per line.  end with cntl/z.yamaha(config)#username yamaha privilege on password yamaha_passyamaha(config)#exityamaha#exitusername: yamahapassword:swx2310p-28gt rev.2.02.06 (tue mar 13 08:41:39 2018)  copyright (c) 2015-2016 yamaha corporation. all rights reserved.yamaha>enableyamaha#</div><div class="display_word">5.1. Adding a user The following example assigns administrator rights to the user “ yamaha ” and specifies the password “ yamaha_pass ”. Yamaha#configure terminalEnter configuration commands, one per line.  End with CNTL/Z.Yamaha(config)#username yamaha privilege on password yamaha_passYamaha(config)#exitYamaha#exitUsername: yamahaPassword:SWX2310P-28GT Rev.2.02.06 (Tue Mar 13 08:41:39 2018)  Copyright (c) 2015-2016 Yamaha Corporation. All Rights Reserved.Yamaha>enableYamaha#</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution if no administrative user (user with administrator rights) exists in startup-config when the product is booted, then a default administrative user (with username “admin” and password “admin”) will be added automatically. for example, that would occur in the following case. product is booted with factory default settings configured firmware is updated to a newer version than rev. 2.02.23 after the product was operated using rev. 2.02.23 or older firmware and only unnamed users. if a user with no password is specified in startup-config when the product is booted, then a password with the same character string as the username will be added automatically. for example, that would occur in the following case. firmware is updated to a newer version than rev. 2.02.23 after rev. 2.02.23 or older firmware was used to specify users with no password. settings configured with rev. 2.02.23 or earlier firmware version username yamaha1username yamaha2 privilege on settings after updating firmware to a newer version than rev. 2.02.23 username yamaha1 password yamaha1username yamaha2 privilege on password yamaha2 if the password (admin) for the default administrative user admin is left unchanged, then the following restrictions are applied. network switches cannot be accessed by telnet, ssh, http, or https from a network segment other than the maintenance vlan. login by users other than the default administrative user is not permitted. username: yamahapassword:% please login as user "admin". the following commands cannot be executed. similar setting changes cannot be performed via the web gui either. ip address / no ip address note: only “ip address dhcp” can be executed. auto-ip / no auto-ip ipv6 / no ipv6 ipv6 address / no ipv6 address management interface / no management interface</div><div class="display_word">6. Points of Caution If no administrative user (user with administrator rights) exists in startup-config when the product is booted, then a default administrative user (with username “admin” and password “admin”) will be added automatically. For example, that would occur in the following case. Product is booted with factory default settings configured Firmware is updated to a newer version than Rev. 2.02.23 after the product was operated using Rev. 2.02.23 or older firmware and only unnamed users. If a user with no password is specified in startup-config when the product is booted, then a password with the same character string as the username will be added automatically. For example, that would occur in the following case. Firmware is updated to a newer version than Rev. 2.02.23 after Rev. 2.02.23 or older firmware was used to specify users with no password. Settings configured with Rev. 2.02.23 or earlier firmware version username yamaha1username yamaha2 privilege on Settings after updating firmware to a newer version than Rev. 2.02.23 username yamaha1 password yamaha1username yamaha2 privilege on password yamaha2 If the password (admin) for the default administrative user admin is left unchanged, then the following restrictions are applied. Network switches cannot be accessed by TELNET, SSH, HTTP, or HTTPS from a network segment other than the maintenance VLAN. Login by users other than the default administrative user is not permitted. Username: yamahaPassword:% Please login as user "admin". The following commands cannot be executed. Similar setting changes cannot be performed via the web GUI either. ip address / no ip address Note: Only “ip address dhcp” can be executed. auto-ip / no auto-ip ipv6 / no ipv6 ipv6 address / no ipv6 address management interface / no management interface</div></div><div id="oam_oam_user_account"><div class="search_title" docfname="oam_oam_user_account" doctitle="User" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation remote access control</div><div class="display_word">7. Related Documentation Remote Access Control</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#snmp-mibリファレンス">SNMP MIB Reference</div><div class="search_word">snmp mib reference</div><div class="display_word">SNMP MIB Reference</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#snmp-mib一覧">1. SNMP MIB List</div><div class="search_word">1. snmp mib list the snmp mibs that are supported by this product are shown below.</div><div class="display_word">1. SNMP MIB List The SNMP MIBs that are supported by this product are shown below.</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#mibツリー">1.1. MIB tree</div><div class="search_word">1.1. mib tree the mib tree for mib groups that are supported by this product are shown below. iso(1)   |   +--std(0)   ||   |+--iso8802(8802)   ||   |+--ieee802dot1(1)   ||   |+--ieee802dot1mibs(1)   ||   |+--ieee8021paemib(1)           (port authentication information)   ||   |+--lldpmib(2)   ||   |+--lldpobjects(1)           (lldp information)   |   +--member-body(2)   ||   |+--us(840)   ||   |+--802dot3(10006)   ||   |+--snmpmibs(300)   ||   |+--lagmib(43)         (lacp link aggregation information)   |   +--org(3)      |      +--dod(6)      ||      |+--internet(1)      ||      |+--mgmt(2)      |||      ||+--mib-2(1)      |||      ||+--system(1)             (system information)      |||      ||+--interfaces(2)         (interface information)      |||      ||+--at(3)                 (mapping information for network addresses and physical addresses)      |||      ||+--rmon(16)              (rmon information)      |||      ||+--dot1dbridge(17)       (dot1dbridge information)      |||      ||+--ifmib(31)             (additional information for interface)      |||      ||+--entitymib(47)         (entity information)      |||      ||+--powerethernetmib(105) (poe information)      ||      |+--private(4)      ||      |+--enterprises(1)      ||      |+--yamaha(1182)      ||      |+--yamahasw(3)                  (private mib yamaha switch information)      ||      |+--yamahaswhardware(1)       (hardware information)      ||      |+--yamahaswfirmware(2)       (firmware information)      ||      |+--yamahaswl2ms(5)           (l2ms information)      ||      |+--yamahaswerrdisable(6)     (error detection function information)      ||      |+--yamahaswrmon(7)           (rmon information)      ||      |+--yamahaswtermmon(8)        (terminal monitoring information)      ||      |+--yamahaswbridge(9)         (dot1dbridge information)      ||      |+--yamahaswpowerethernet(10) (poe information)      ||      |+--yamahaswloopdetect(11)    (loop detection information)      |      +--ieee(111)         |         +--standards-association-numbers-series-standards(2)            |            +--lan-man-stds(802)               |               +--ieee802dot1(1)                  |                  +--ieee802dot1mibs(1)                     |                     +--lldpv2mib(13)            (lldp information)</div><div class="display_word">1.1. MIB tree The MIB tree for MIB groups that are supported by this product are shown below. iso(1)   |   +--std(0)   ||   |+--iso8802(8802)   ||   |+--ieee802dot1(1)   ||   |+--ieee802dot1mibs(1)   ||   |+--ieee8021paeMIB(1)           (port authentication information)   ||   |+--lldpMIB(2)   ||   |+--lldpObjects(1)           (LLDP information)   |   +--member-body(2)   ||   |+--us(840)   ||   |+--802dot3(10006)   ||   |+--snmpmibs(300)   ||   |+--lagMIB(43)         (LACP link aggregation information)   |   +--org(3)      |      +--dod(6)      ||      |+--internet(1)      ||      |+--mgmt(2)      |||      ||+--mib-2(1)      |||      ||+--system(1)             (system information)      |||      ||+--interfaces(2)         (interface information)      |||      ||+--at(3)                 (mapping information for network addresses and physical addresses)      |||      ||+--rmon(16)              (RMON information)      |||      ||+--dot1dBridge(17)       (dot1dBridge information)      |||      ||+--ifMIB(31)             (additional information for interface)      |||      ||+--entityMIB(47)         (entity information)      |||      ||+--powerEthernetMIB(105) (PoE information)      ||      |+--private(4)      ||      |+--enterprises(1)      ||      |+--yamaha(1182)      ||      |+--yamahaSW(3)                  (private MIB Yamaha switch information)      ||      |+--yamahaSWHardware(1)       (hardware information)      ||      |+--yamahaSWFirmware(2)       (firmware information)      ||      |+--yamahaSWL2ms(5)           (L2MS information)      ||      |+--yamahaSWErrDisable(6)     (error detection function information)      ||      |+--yamahaSWRmon(7)           (RMON information)      ||      |+--yamahaSWTermMon(8)        (terminal monitoring information)      ||      |+--yamahaSWBridge(9)         (dot1dBridge information)      ||      |+--yamahaSWPowerEthernet(10) (PoE information)      ||      |+--yamahaSWLoopDetect(11)    (Loop detection information)      |      +--ieee(111)         |         +--standards-association-numbers-series-standards(2)            |            +--lan-man-stds(802)               |               +--ieee802dot1(1)                  |                  +--ieee802dot1mibs(1)                     |                     +--lldpV2MIB(13)            (LLDP information)</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#標準mib一覧">1.2. Standard MIB list</div><div class="search_word">1.2. standard mib list the standard mibs that are supported are shown below. mib group summary ieee8021paemib group port authentication information lldpmib group lldp information lagmib group lacp link aggregation information system group system information interface group interface information at group mapping information for physical addresses and network addresses rmon group rmon information dot1dbridge group dot1dbridge information ifmib group additional information for interface entitymib group entity information powerethernetmib group poe information</div><div class="display_word">1.2. Standard MIB list The standard MIBs that are supported are shown below. MIB group Summary ieee8021paeMIB group Port authentication information lldpMIB group LLDP information lagMIB group LACP link aggregation information system group System information interface group Interface information at group Mapping information for physical addresses and network addresses rmon group RMON information dot1dBridge group dot1dBridge information ifMIB group Additional information for interface entityMIB group Entity information powerEthernetMIB group PoE information</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#プライベートmib一覧">1.3. Private MIB list</div><div class="search_word">1.3. private mib list private mibs that are supported are shown below. all of this information is related to yamaha switches. mib group summary yamahaswhardware group hardware information yamahaswfirmware group firmware information yamahaswl2ms group l2ms information yamahaswerrdisable group error detection function information yamahaswrmon group rmon information yamahaswtermmon group terminal monitoring information yamahaswbridge group dot1dbridge information yamahaswpowerethernet group poe information yamahaswloopdetect group loop detection information</div><div class="display_word">1.3. Private MIB list Private MIBs that are supported are shown below. All of this information is related to Yamaha switches. MIB group Summary yamahaSWHardware group Hardware information yamahaSWFirmware group Firmware information yamahaSWL2ms group L2MS information yamahaSWErrDisable group Error detection function information yamahaSWRmon group RMON information yamahaSWTermMon group Terminal monitoring information yamahaSWBridge group dot1dBridge information yamahaSWPowerEthernet group PoE information yamahaSWLoopDetect group Loop detection information</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#標準mibトラップ一覧">1.4. Standard MIB trap list</div><div class="search_word">1.4. standard mib trap list the standard mib traps that are supported are shown below. trap summary coldstart power off/on notification warmstart reload notification linkdown linkdown notification linkup linkup notification authenticationfailure notification of failed authentication risingalarm notification that rmon upper threshold value has been exceeded fallingalarm notification that rmon lower threshold value has been exceeded newroot notification that new root for bridge has been detected topologychange notification when a change in topology has been detected pethpseportonoffnotification poe port status change notification pethmainpowerusageonnotification notification that the power consumption has exceeded the threshold value pethmainpowerusageoffnotification notification that the power consumption has fallen below the threshold value</div><div class="display_word">1.4. Standard MIB trap list The standard MIB traps that are supported are shown below. Trap Summary coldStart Power OFF/ON notification warmStart Reload notification linkDown Linkdown notification linkUp Linkup notification authenticationFailure Notification of failed authentication risingAlarm Notification that RMON upper threshold value has been exceeded fallingAlarm Notification that RMON lower threshold value has been exceeded newRoot Notification that new root for bridge has been detected topologyChange Notification when a change in topology has been detected pethPsePortOnOffNotification PoE port status change notification pethMainPowerUsageOnNotification Notification that the power consumption has exceeded the threshold value pethMainPowerUsageOffNotification Notification that the power consumption has fallen below the threshold value</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#プライベートmibトラップ一覧">1.5. Private MIB trap list</div><div class="search_word">1.5. private mib trap list private mibs traps that are supported are shown below. trap summary yshtemperaturestatusnormaltrap normal temperature status notification yshtemperaturestatuswarningtrap warning temperature status notification yshtemperaturestatuserrortrap error temperature status notification yshfanstoppedtrap fan stopped notification yshfanspeeduptrap increased fan rpm notification yshfanspeeddowntrap decreased fan rpm notification yshtemperaturesensorinvalidtrap notification that a thermal sensor abnormality has occurred ysl2msfindagent notification that l2ms agent was detected ysl2msdetectdown notification that l2ms agent was lost ysedtrap notification of detect/cancel for error detection function ystmiftermtrap notification of terminal monitoring (port) detection ystmiptermtrap notification of terminal monitoring (ip address) detection yspesupplyporttrap power supply start notification yspeterminateporttrap power supply stop notification yspeguardbandstatetrap guard band status change notification yspeporterrortrap poe port error detection/removal notification yspeunitfailuretrap poe unit power supply abnormality notification ysldportdetectlooptrap loop detection notification (port) ysldportresolvelooptrap loop detection cancellation notification (port) ysldlagdetectlooptrap loop detection notification (logical interface) ysldlagresolvelooptrap loop detection cancellation notification (logical interface)</div><div class="display_word">1.5. Private MIB trap list Private MIBs traps that are supported are shown below. Trap Summary yshTemperatureStatusNormalTrap Normal temperature status notification yshTemperatureStatusWarningTrap Warning temperature status notification yshTemperatureStatusErrorTrap Error temperature status notification yshFanStoppedTrap Fan stopped notification yshFanSpeedUpTrap Increased fan RPM notification yshFanSpeedDownTrap Decreased fan RPM notification yshTemperatureSensorInvalidTrap Notification that a thermal sensor abnormality has occurred ysl2msFindAgent Notification that L2MS agent was detected ysl2msDetectDown Notification that L2MS agent was lost ysedTrap Notification of detect/cancel for error detection function ystmIfTermTrap Notification of terminal monitoring (port) detection ystmIpTermTrap Notification of terminal monitoring (IP address) detection yspeSupplyPortTrap Power supply start notification yspeTerminatePortTrap Power supply stop notification yspeGuardBandStateTrap Guard band status change notification yspePortErrorTrap PoE port error detection/removal notification yspeUnitFailureTrap PoE unit power supply abnormality notification ysldPortDetectLoopTrap Loop detection notification (port) ysldPortResolveLoopTrap Loop detection cancellation notification (port) ysldLagDetectLoopTrap Loop detection notification (logical interface) ysldLagResolveLoopTrap Loop detection cancellation notification (logical interface)</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used mib access classification the mib access type used in subsequent explanations is described below. mib access classification access name description r/o access to the mib is read-only r/w access to the mib is read-write r/nw although the access to the mib is read-write as per the standards, it is read-only on this product r/c access to the mib is read-create r/nc although the access to the mib is read-create as per the standards, it is read-only on this product n/a the mib cannot be retrieved note: may be used as additional information for traps (variable-bindings) ifindex this is the id number linked to the interface. for information about ifindex assignments, refer to the following technical reference. basic interface functions</div><div class="display_word">2. Definition of Terms Used MIB access classification The MIB access type used in subsequent explanations is described below. MIB access classification Access name Description R/O Access to the MIB is read-only R/W Access to the MIB is read-write R/NW Although the access to the MIB is read-write as per the standards, it is read-only on this product R/C Access to the MIB is read-create R/NC Although the access to the MIB is read-create as per the standards, it is read-only on this product N/A The MIB cannot be retrieved Note: May be used as additional information for traps (variable-bindings) ifIndex This is the ID number linked to the interface. For information about ifIndex assignments, refer to the following technical reference. Basic Interface Functions</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#プライベートmib入手方法">3. Obtaining a Private MIB</div><div class="search_word">3. obtaining a private mib private mib files may be acquired from here .</div><div class="display_word">3. Obtaining a Private MIB Private MIB files may be acquired from here .</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#標準mib">4. Standard MIBs</div><div class="search_word">4. standard mibs standard mibs that are supported by this product are shown below.</div><div class="display_word">4. Standard MIBs Standard MIBs that are supported by this product are shown below.</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#ieee8021paemibグループ">4.1. ieee8021paeMIB group</div><div class="search_word">4.1. ieee8021paemib group this mib is related to port authentication information. the syntax defined for the ieee8021paemib group is shown below. syntax defined in the ieee8021paemib group syntax definition paecontrolleddirections integer * both(0) * in(1) paecontrolledportstatus integer * authorized(1) * unauthorized(2) paecontrolledportcontrol integer * forceunauthorized(1) * auto(2) * forceauthorized(3) the ieee8021paemib group is divided into subgroups such as those shown below. ieee8021paemib(1)     |     +--paemibobjects(1)        |        +--dot1xpaesystem(1)        |        +--dot1xpaeauthenticator(2) dot1xpaesystem group mib name oid access syntax description dot1xpaesystemauthcontrol 1.0.8802.1.1.1.1.1.1 r/nw integer * enabled(1) * disabled(2) setting value for authentication function at the system level dot1xpaeporttable 1.0.8802.1.1.1.1.1.2 n/a system-level information table dot1xpaeportentry 1.0.8802.1.1.1.1.1.2.1 n/a index * dot1xpaeportnumber dot1xpaeportnumber 1.0.8802.1.1.1.1.1.2.1.1 n/a interfaceindex port numbers for which the authentication function is enabled dot1xpaeportprotocolversion 1.0.8802.1.1.1.1.1.2.1.2 r/o unsigned32 protocol version (2, fixed) dot1xpaeportcapabilities 1.0.8802.1.1.1.1.1.2.1.3 r/o bits pae functions supported by the port (0, fixed) dot1xpaeportinitialize 1.0.8802.1.1.1.1.1.2.1.4 r/nw truthvalue initialization control for ports (2, fixed) dot1xpaeportreauthenticate dot1xpaeauthenticator group mib name oid access syntax description dot1xauthconfigtable 1.0.8802.1.1.1.1.2.1 n/a structural object table for authenticator pae for each port dot1xauthconfigentry 1.0.8802.1.1.1.1.2.1.1 n/a index * dot1xpaeportnumber dot1xauthadmincontrolleddirections 1.0.8802.1.1.1.1.2.1.1.3 r/nw paecontrolleddirections packet forwarding operation in an unauthenticated state, controlled by management dot1xauthopercontrolleddirections 1.0.8802.1.1.1.1.2.1.1.4 r/o paecontrolleddirections packet forwarding operation in an unauthenticated state, controlled by operation dot1xauthauthcontrolledportstatus 1.0.8802.1.1.1.1.2.1.1.5 r/o paecontrolledportstatus port authentication status dot1xauthauthcontrolledportcontrol 1.0.8802.1.1.1.1.2.1.1.6 r/nw paecontrolledportcontrol setting value for 802.1x authentication operating mode dot1xauthquietperiod 1.0.8802.1.1.1.1.2.1.1.7 r/nw unsigned32 setting value for authentication restriction period dot1xauthsupptimeout 1.0.8802.1.1.1.1.2.1.1.9 r/nw unsigned32 response wait time setting value for the supplicant dot1xauthservertimeout 1.0.8802.1.1.1.1.2.1.1.10 r/nw unsigned32 setting value for server response wait time dot1xauthmaxreq 1.0.8802.1.1.1.1.2.1.1.11 r/nw unsigned32 setting value for number of times eapol packets are retransmitted dot1xauthreauthperiod 1.0.8802.1.1.1.1.2.1.1.12 r/nw unsigned32 setting value for re-authentication interval dot1xauthreauthenabled 1.0.8802.1.1.1.1.2.1.1.13 r/nw truthvalue setting value for reauthentication function dot1xauthkeytxenabled 1.0.8802.1.1.1.1.2.1.1.14 r/nw truthvalue constant value (2, fixed) used by authenticator pae state machine dot1xauthstatstable 1.0.8802.1.1.1.1.2.2 n/a statistical data object table for authenticator pae associated with each port dot1xauthstatsentry 1.0.8802.1.1.1.1.2.2.1 n/a index * dot1xpaeportnumber dot1xautheapolframesrx 1.0.8802.1.1.1.1.2.2.1.1 r/o counter32 no. of eapol frames that are received, all valid types dot1xautheapolframestx 1.0.8802.1.1.1.1.2.2.1.2 r/o counter32 no. of eapol frames that are transmitted, all types dot1xautheapolstartframesrx 1.0.8802.1.1.1.1.2.2.1.3 r/o counter32 no. of eapol start frames received dot1xautheapollogoffframesrx 1.0.8802.1.1.1.1.2.2.1.4 r/o counter32 no. of eapol logoff frames received dot1xautheapolrespidframesrx 1.0.8802.1.1.1.1.2.2.1.5 r/o counter32 no. of eap response/identity frames received dot1xautheapolrespframesrx 1.0.8802.1.1.1.1.2.2.1.6 r/o counter32 no. of valid eap response frames, excepting eap response/identity frames received dot1xautheapolreqidframestx 1.0.8802.1.1.1.1.2.2.1.7 r/o counter32 no. of eap request/identity frames transmitted dot1xautheapolreqframestx 1.0.8802.1.1.1.1.2.2.1.8 r/o counter32 no. of eap request frames, excepting eap request/identity frames transmitted dot1xauthinvalideapolframesrx 1.0.8802.1.1.1.1.2.2.1.9 r/o counter32 no. of frames within received eapol frames, for which frame type has not been approved dot1xautheaplengtherrorframesrx 1.0.8802.1.1.1.1.2.2.1.10 r/o counter32 no. of received eapol frames, for which the packet body length is invalid dot1xauthlasteapolframeversion 1.0.8802.1.1.1.1.2.2.1.11 r/o unsigned32 protocol version numbers for most recently received eapol frames dot1xauthlasteapolframesource 1.0.8802.1.1.1.1.2.2.1.12 r/o macaddress source mac address of eapol frames most recently received</div><div class="display_word">4.1. ieee8021paeMIB group This MIB is related to port authentication information. The syntax defined for the ieee8021paeMIB group is shown below. Syntax defined in the ieee8021paeMIB group Syntax Definition PaeControlledDirections INTEGER * both(0) * in(1) PaeControlledPortStatus INTEGER * authorized(1) * unauthorized(2) PaeControlledPortControl INTEGER * forceUnauthorized(1) * auto(2) * forceAuthorized(3) The ieee8021paeMIB group is divided into subgroups such as those shown below. ieee8021paeMIB(1)     |     +--paeMIBObjects(1)        |        +--dot1xPaeSystem(1)        |        +--dot1xPaeAuthenticator(2) dot1xPaeSystem group MIB name OID Access Syntax Description dot1xPaeSystemAuthControl 1.0.8802.1.1.1.1.1.1 R/NW INTEGER * enabled(1) * disabled(2) Setting value for authentication function at the system level dot1xPaePortTable 1.0.8802.1.1.1.1.1.2 N/A System-level information table dot1xPaePortEntry 1.0.8802.1.1.1.1.1.2.1 N/A INDEX * dot1xPaePortNumber dot1xPaePortNumber 1.0.8802.1.1.1.1.1.2.1.1 N/A InterfaceIndex Port numbers for which the authentication function is enabled dot1xPaePortProtocolVersion 1.0.8802.1.1.1.1.1.2.1.2 R/O Unsigned32 Protocol version (2, fixed) dot1xPaePortCapabilities 1.0.8802.1.1.1.1.1.2.1.3 R/O BITS PAE functions supported by the port (0, fixed) dot1xPaePortInitialize 1.0.8802.1.1.1.1.1.2.1.4 R/NW TruthValue Initialization control for ports (2, fixed) dot1xPaePortReauthenticate dot1xPaeAuthenticator group MIB name OID Access Syntax Description dot1xAuthConfigTable 1.0.8802.1.1.1.1.2.1 N/A Structural object table for Authenticator PAE for each port dot1xAuthConfigEntry 1.0.8802.1.1.1.1.2.1.1 N/A INDEX * dot1xPaePortNumber Dot1xAuthAdminControlledDirections 1.0.8802.1.1.1.1.2.1.1.3 R/NW PaeControlledDirections Packet forwarding operation in an unauthenticated state, controlled by management dot1xAuthOperControlledDirections 1.0.8802.1.1.1.1.2.1.1.4 R/O PaeControlledDirections Packet forwarding operation in an unauthenticated state, controlled by operation dot1xAuthAuthControlledPortStatus 1.0.8802.1.1.1.1.2.1.1.5 R/O PaeControlledPortStatus Port authentication status dot1xAuthAuthControlledPortControl 1.0.8802.1.1.1.1.2.1.1.6 R/NW PaeControlledPortControl Setting value for 802.1X authentication operating mode dot1xAuthQuietPeriod 1.0.8802.1.1.1.1.2.1.1.7 R/NW Unsigned32 Setting value for authentication restriction period dot1xAuthSuppTimeout 1.0.8802.1.1.1.1.2.1.1.9 R/NW Unsigned32 Response wait time setting value for the supplicant dot1xAuthServerTimeout 1.0.8802.1.1.1.1.2.1.1.10 R/NW Unsigned32 Setting value for server response wait time dot1xAuthMaxReq 1.0.8802.1.1.1.1.2.1.1.11 R/NW Unsigned32 Setting value for number of times EAPOL packets are retransmitted dot1xAuthReAuthPeriod 1.0.8802.1.1.1.1.2.1.1.12 R/NW Unsigned32 Setting value for re-authentication interval dot1xAuthReAuthEnabled 1.0.8802.1.1.1.1.2.1.1.13 R/NW TruthValue Setting value for reauthentication function dot1xAuthKeyTxEnabled 1.0.8802.1.1.1.1.2.1.1.14 R/NW TruthValue Constant value (2, fixed) used by Authenticator PAE state machine dot1xAuthStatsTable 1.0.8802.1.1.1.1.2.2 N/A Statistical data object table for Authenticator PAE associated with each port dot1xAuthStatsEntry 1.0.8802.1.1.1.1.2.2.1 N/A INDEX * dot1xPaePortNumber dot1xAuthEapolFramesRx 1.0.8802.1.1.1.1.2.2.1.1 R/O Counter32 No. of EAPOL frames that are received, all valid types dot1xAuthEapolFramesTx 1.0.8802.1.1.1.1.2.2.1.2 R/O Counter32 No. of EAPOL frames that are transmitted, all types dot1xAuthEapolStartFramesRx 1.0.8802.1.1.1.1.2.2.1.3 R/O Counter32 No. of EAPOL Start frames received dot1xAuthEapolLogoffFramesRx 1.0.8802.1.1.1.1.2.2.1.4 R/O Counter32 No. of EAPOL Logoff frames received dot1xAuthEapolRespIdFramesRx 1.0.8802.1.1.1.1.2.2.1.5 R/O Counter32 No. of EAP Response/Identity frames received dot1xAuthEapolRespFramesRx 1.0.8802.1.1.1.1.2.2.1.6 R/O Counter32 No. of valid EAP Response frames, excepting EAP Response/Identity frames received dot1xAuthEapolReqIdFramesTx 1.0.8802.1.1.1.1.2.2.1.7 R/O Counter32 No. of EAP Request/Identity frames transmitted dot1xAuthEapolReqFramesTx 1.0.8802.1.1.1.1.2.2.1.8 R/O Counter32 No. of EAP Request frames, excepting EAP Request/Identity frames transmitted dot1xAuthInvalidEapolFramesRx 1.0.8802.1.1.1.1.2.2.1.9 R/O Counter32 No. of frames within received EAPOL frames, for which frame type has not been approved dot1xAuthEapLengthErrorFramesRx 1.0.8802.1.1.1.1.2.2.1.10 R/O Counter32 No. of received EAPOL frames, for which the packet body length is invalid dot1xAuthLastEapolFrameVersion 1.0.8802.1.1.1.1.2.2.1.11 R/O Unsigned32 Protocol version numbers for most recently received EAPOL frames dot1xAuthLastEapolFrameSource 1.0.8802.1.1.1.1.2.2.1.12 R/O MacAddress Source MAC address of EAPOL frames most recently received</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#lldpmibグループ">4.2. lldpMIB group</div><div class="search_word">4.2. lldpmib group this mib is related to lldp information. this product handles the following two mib groups involved in the lldp. lldpmib group (mib defined in ieee std 802.1ab-2005) lldpv2mib group (mib defined in ieee std 802.1ab-2009) though both mibs handle the lldp in the same way, both are supported to provide compatibility with other models. some mibs refer to the same value. the syntax defined for the lldpmib group is shown below. syntax defined in the lldpmib group syntax definition lldpchassisidsubtype integer * chassiscomponent(1) * interfacealias(2) * portcomponent(3) * macaddress(4) * networkaddress(5) * interfacename(6) * local(7) lldpchassisid octet string (size (1..255)) lldpportidsubtype integer * interfacealias(1) * portcomponent(2) * macaddress(3) * networkaddress(4) * interfacename(5) * agentcircuitid(6) * local(7) lldpportid octet string (size (1..255)) lldpsystemcapabilitiesmap bits * other(0) * repeater(1) * bridge(2) * wlanaccesspoint(3) * router(4) * telephone(5) * docsiscabledevice(6) * stationonly(7) lldpportnumber integer32 (1..4096) lldppowerportclass integer * pclasspse(1) * pclasspd(2) lldpxmeddeviceclass integer * notdefined(0) * endpointclass1(1) * endpointclass2(2) * endpointclass3(3) * networkconnectivity(4) lldpxmedcapabilities integer * capabilities(0) * networkpolicy(1) * location(2) * extendedpse(3) * extendedpd(4) * inventory(5) lldpmanaddress octet string (size (1..31)) lldpmanaddrifsubtype integer * unknown(1) * ifindex(2) * systemportnumber(3) the lldpmib group is divided into subgroups, such as shown below. lldpobjects(1)     |     +--lldpconfiguration(1)     |     +--lldpstatistics(2)     |     +--lldplocalsystemdata(3)     |     +--lldpremotesystemsdata(4)     |     +--lldpextensions(5)        |        +--lldpxdot3mib(4623)        ||        |+--lldpxdot3objects(1)        ||        |+--lldpxdot3config(1)        ||        |+--lldpxdot3localdata(2)        ||        |+--lldpxdot3remotedata(3)        |        +--lldpxmedmib(4795)           |           +--lldpxmedobjects(1)              |              +--lldpxmedconfig(1)              |              +--lldpxmedlocaldata(2)              |              +--lldpxmedremotedata(3) lldpconfiguration group mib name oid access syntax description lldpportconfigtable 1.0.8802.1.1.2.1.1.6 n/a table of information for each port lldpportconfigentry 1.0.8802.1.1.2.1.1.6.1 n/a index * lldpportconfigportnum lldpportconfigadminstatus 1.0.8802.1.1.2.1.1.6.1.2 r/nw integer * txonly(1) * rxonly(2) * txandrx(3) * disabled(4) lldp transmission/reception status lldpportconfignotificationenable 1.0.8802.1.1.2.1.1.6.1.3 r/nw truthval lldp notification status lldpportconfigtlvstxenable 1.0.8802.1.1.2.1.1.6.1.4 r/nw bits * portdesc(0) * sysname(1) * sysdesc(2) * syscap(3) basic management tlv transmission item lldpstatistics group mib name oid access syntax description lldpstatsremtableslastchangetime 1.0.8802.1.1.2.1.2.1 r/o timeticks time from system initialization until remote data update lldpstatsremtablesinserts 1.0.8802.1.1.2.1.2.2 r/o integer (0..4294967295) total number of entries added to the remote device management table lldpstatsremtablesdeletes 1.0.8802.1.1.2.1.2.3 r/o integer (0..4294967295) total number of entries deleted from the remote device management table lldpstatsremtablesdrops 1.0.8802.1.1.2.1.2.4 r/o integer (0..4294967295) total number of entries that could not be specified in the remote device management table lldpstatsremtablesageouts 1.0.8802.1.1.2.1.2.5 r/o integer (0..4294967295) total number of entries that exceeded the ttl time (aged out) and were deleted from the remote device management table lldpstatstxporttable 1.0.8802.1.1.2.1.2.6 n/a table of information for each port lldpstatstxportentry 1.0.8802.1.1.2.1.2.6.1 n/a index * lldpstatstxportnum lldpstatstxportnum 1.0.8802.1.1.2.1.2.6.1.1 n/a lldpportnumber lldpstatstxportframestotal 1.0.8802.1.1.2.1.2.6.1.2 r/o integer (0..4294967295) total number of lldp frames transmitted lldpstatsrxporttable 1.0.8802.1.1.2.1.2.7 n/a table of information for each port lldpstatsrxportentry 1.0.8802.1.1.2.1.2.7.1 n/a index * lldpstatsrxportnum lldpstatsrxportnum 1.0.8802.1.1.2.1.2.7.1.1 n/a lldpportnumber lldpstatsrxportframesdiscardedtotal 1.0.8802.1.1.2.1.2.7.1.2 r/o integer (0..4294967295) number of lldp frames discarded lldpstatsrxportframeserrors 1.0.8802.1.1.2.1.2.7.1.3 r/o integer (0..4294967295) number of error frames received lldpstatsrxportframestotal 1.0.8802.1.1.2.1.2.7.1.4 r/o integer (0..4294967295) number of lldp frames received lldpstatsrxporttlvsdiscardedtotal 1.0.8802.1.1.2.1.2.7.1.5 r/o integer (0..4294967295) number of tlvs discarded lldpstatsrxporttlvsunrecognizedtotal 1.0.8802.1.1.2.1.2.7.1.6 r/o integer (0..4294967295) number of unrecognized tlvs received lldpstatsrxportageoutstotal 1.0.8802.1.1.2.1.2.7.1.7 r/o integer (0..4294967295) number of entries that aged-out lldplocalsystemdata group mib name oid access syntax description lldplocchassisidsubtype 1.0.8802.1.1.2.1.3.1 r/o lldpchassisidsubtype subtype of chassis id lldplocchassisid 1.0.8802.1.1.2.1.3.2 r/o lldpchassisid chassis id lldplocsysname 1.0.8802.1.1.2.1.3.3 r/o snmpadminstring (size (0..255)) system name lldplocsysdesc 1.0.8802.1.1.2.1.3.4 r/o snmpadminstring (size (0..255)) system description lldplocsyscapsupported 1.0.8802.1.1.2.1.3.5 r/o lldpsystemcapabilitiesmap functions supported by the system lldplocsyscapenabled 1.0.8802.1.1.2.1.3.6 r/o lldpsystemcapabilitiesmap functions enabled by the system lldplocporttable 1.0.8802.1.1.2.1.3.7 n/a table of information for each port lldplocportentry 1.0.8802.1.1.2.1.3.7.1 n/a index * lldplocportnum lldplocportnum 1.0.8802.1.1.2.1.3.7.1.1 n/a lldpportnumber lldplocportidsubtype 1.0.8802.1.1.2.1.3.7.1.2 r/o lldpportidsubtype subtype of port id lldplocportid 1.0.8802.1.1.2.1.3.7.1.3 r/o octet string (size (1..255)) port id lldplocportdesc 1.0.8802.1.1.2.1.3.7.1.4 r/o snmpadminstring (size (0..255)) port description lldplocmanaddrtable 1.0.8802.1.1.2.1.3.8 n/a table of local system management addresses lldplocmanaddrentry 1.0.8802.1.1.2.1.3.8.1 n/a index * lldpv2locmanaddrsubtype * lldplocmanaddr lldplocmanaddrsubtype 1.0.8802.1.1.2.1.3.8.1.1 n/a addressfamilynumbers sub-type for management address lldplocmanaddr 1.0.8802.1.1.2.1.3.8.1.2 n/a lldpmanaddress management address lldplocmanaddrlen 1.0.8802.1.1.2.1.3.8.1.3 r/o integer32 management address length lldplocmanaddrifsubtype 1.0.8802.1.1.2.1.3.8.1.4 r/o lldpmanaddrifsubtype interface sub-type lldplocmanaddrifid 1.0.8802.1.1.2.1.3.8.1.5 r/o integer32 interface id lldpremotesystemsdata group mib name oid access syntax description lldpremtable 1.0.8802.1.1.2.1.4.1 n/a table of information for each port lldprementry 1.0.8802.1.1.2.1.4.1.1 n/a index * lldpremtimemark * lldpremlocalportnum * lldpremindex lldpremtimemark 1.0.8802.1.1.2.1.4.1.1.1 n/a timefilter lldpremlocalportnum 1.0.8802.1.1.2.1.4.1.1.2 n/a lldpportnumber lldpremindex 1.0.8802.1.1.2.1.4.1.1.3 n/a integer32 (1..2147483647) lldpremchassisidsubtype 1.0.8802.1.1.2.1.4.1.1.4 r/o lldpchassisidsubtype subtype of the remote device chassis id lldpremchassisid 1.0.8802.1.1.2.1.4.1.1.5 r/o snmpadminstring (size (0..255)) chassis id of remote device lldpremportidsubtype 1.0.8802.1.1.2.1.4.1.1.6 r/o lldpportidsubtype subtype of the remote device port id lldpremportid 1.0.8802.1.1.2.1.4.1.1.7 r/o octet string (size (1..255)) port id of remote device lldpremportdesc 1.0.8802.1.1.2.1.4.1.1.8 r/o snmpadminstring (size (0..255)) description of remote device port lldpremsysname 1.0.8802.1.1.2.1.4.1.1.9 r/o snmpadminstring (size (0..255)) system name of remote device lldpremsysdesc 1.0.8802.1.1.2.1.4.1.1.10 r/o snmpadminstring (size (0..255)) system description of remote device lldpremsyscapsupported 1.0.8802.1.1.2.1.4.1.1.11 r/o lldpsystemcapabilitiesmap functionality supported by the remote device system lldpremsyscapenabled 1.0.8802.1.1.2.1.4.1.1.12 r/o lldpsystemcapabilitiesmap functionality enabled in the remote device system lldpremmanaddrtable 1.0.8802.1.1.2.1.4.2 n/a lldpremmanaddrentry 1.0.8802.1.1.2.1.4.2.1 n/a index * lldpremtimemark * lldpremlocalportnum * lldpremindex * lldpremmanaddrsubtype * lldpremmanaddr lldpremmanaddrsubtype 1.0.8802.1.1.2.1.4.2.1.1 n/a lldpportnumber lldpremmanaddr 1.0.8802.1.1.2.1.4.2.1.2 n/a lldpremmanaddrifsubtype 1.0.8802.1.1.2.1.4.2.1.3 r/o integer * unknown(1) * ifindex(2) * systemportnumber(3) subtype of remote device interface lldpremmanaddrifid 1.0.8802.1.1.2.1.4.2.1.4 r/o integer32 interface id of remote device lldpremmanaddroid 1.0.8802.1.1.2.1.4.2.1.5 r/o object identifier oid of the remote device management address lldpremunknowntlvtable 1.0.8802.1.1.2.1.4.3 n/a lldpremunknowntlventry 1.0.8802.1.1.2.1.4.3.1 n/a index * lldpremtimemark * lldpremlocalportnum * lldpremindex * lldpremunknowntlvtype lldpremunknowntlvtype 1.0.8802.1.1.2.1.4.3.1.1 n/a lldpportnumber lldpremunknowntlvinfo 1.0.8802.1.1.2.1.4.3.1.2 r/o lldpportnumber latest undefined tlv information for remote device lldpremorgdefinfotable 1.0.8802.1.1.2.1.4.4 n/a lldpremorgdefinfoentry 1.0.8802.1.1.2.1.4.4.1 n/a index * lldpremtimemark * lldpremlocalportnum * lldpremindex * lldpremorgdefinfooui * lldpremorgdefinfosubtype * lldpremorgdefinfoindex lldpremorgdefinfooui 1.0.8802.1.1.2.1.4.4.1.1 n/a lldpremorgdefinfosubtype 1.0.8802.1.1.2.1.4.4.1.2 n/a lldpremorgdefinfoindex 1.0.8802.1.1.2.1.4.4.1.3 n/a lldpremorgdefinfo 1.0.8802.1.1.2.1.4.4.1.4 r/o octet string (size (0..507)) index of undefined tlv information for remote device (limited to ieee802.1 and ieee802.3) lldpxdot3localdata group mib name oid access syntax description lldpxdot3locpowertable 1.0.8802.1.1.2.1.5.4623.1.2.2 n/a table of information for each port lldpxdot3locpowerentry 1.0.8802.1.1.2.1.5.4623.1.2.2.1 n/a index * lldplocportnum lldpxdot3locpowerportclass 1.0.8802.1.1.2.1.5.4623.1.2.2.1.1 r/o lldppowerportclass pse or pd status lldpxdot3locpowermdisupported 1.0.8802.1.1.2.1.5.4623.1.2.2.1.2 r/o truthvalue power supply capability support lldpxdot3locpowermdienabled 1.0.8802.1.1.2.1.5.4623.1.2.2.1.3 r/o truthvalue enables/disables the power supply capability lldpxdot3locpowerpaircontrolable 1.0.8802.1.1.2.1.5.4623.1.2.2.1.4 r/o truthvalue ability to select the signal line to be used for power supply lldpxdot3locpowerpairs 1.0.8802.1.1.2.1.5.4623.1.2.2.1.5 r/o integer32 (1|2) * signal(1) * spare(2) signal line to be used for power supply lldpxdot3locpowerclass 1.0.8802.1.1.2.1.5.4623.1.2.2.1.6 r/o integer32 (1|2|3|4|5) * class0(1) * class1(2) * class2(3) * class3(4) * class4(5) port power class lldpxdot3remotedata group mib name oid access syntax description lldpxdot3rempowertable 1.0.8802.1.1.2.1.5.4623.1.3.2 n/a table of information for each port lldpxdot3rempowerentry 1.0.8802.1.1.2.1.5.4623.1.3.2.1 n/a index * lldpremtimemark * lldpremlocalportnum * lldpremindex lldpxdot3rempowerportclass 1.0.8802.1.1.2.1.5.4623.1.3.2.1.1 r/o lldppowerportclass remote device status whether it is pse or pd lldpxdot3rempowermdisupported 1.0.8802.1.1.2.1.5.4623.1.3.2.1.2 r/o truthvalue remote device power supply capability support lldpxdot3rempowermdienabled 1.0.8802.1.1.2.1.5.4623.1.3.2.1.3 r/o truthvalue enables/disables the remote device power supply capability lldpxdot3rempowerpaircontrolable 1.0.8802.1.1.2.1.5.4623.1.3.2.1.4 r/o truthvalue ability to select the signal line to be used for power supply of remote device lldpxdot3rempowerpairs 1.0.8802.1.1.2.1.5.4623.1.3.2.1.5 r/o integer32 (1|2) * signal(1) * spare(2) signal line to be used for power supply of remote device lldpxdot3rempowerclass 1.0.8802.1.1.2.1.5.4623.1.3.2.1.6 r/o integer32 (1|2|3|4|5) * class0(1) * class1(2) * class2(3) * class3(4) * class4(5) remote device port power class lldpxmedconfig group mib name oid access syntax description lldpxmedlocdeviceclass 1.0.8802.1.1.2.1.5.4795.1.1.1 r/o lldpxmeddeviceclass local device class lldpxmedportconfigtable 1.0.8802.1.1.2.1.5.4795.1.1.2 n/a table of information for each port lldpxmedportconfigentry 1.0.8802.1.1.2.1.5.4795.1.1.2.1 n/a index * port number lldpxmedportcapsupported 1.0.8802.1.1.2.1.5.4795.1.1.2.1.1 r/o lldpxmedcapabilities tlv transmission items supported by lldp-med lldpxmedportconfigtlvstxenable 1.0.8802.1.1.2.1.5.4795.1.1.2.1.2 r/nw lldpxmedcapabilities tlv items sent as lldp-med lldpxmedportconfignotifenable 1.0.8802.1.1.2.1.5.4795.1.1.2.1.3 r/nw truthvalue lldp-med notification status lldpxmedfaststartrepeatcount 1.0.8802.1.1.2.1.5.4795.1.1.3 r/nw unsigned32 (1..10) lldp-med fast transmission count lldpxmedlocaldata group mib name oid access syntax description lldpxmedlocxpoedevicetype 1.0.8802.1.1.2.1.5.4795.1.2.10 r/o integer * unknown(1) * psedevice(2) * pddevice(3) * none(4) pse or pd status lldpxmedlocxpoepseporttable 1.0.8802.1.1.2.1.5.4795.1.2.11 n/a pse information table for each port lldpxmedlocxpoepseportentry 1.0.8802.1.1.2.1.5.4795.1.2.11.1 n/a index * lldplocportnum lldpxmedlocxpoepseportpowerav 1.0.8802.1.1.2.1.5.4795.1.2.11.1.1 r/o gauge32 (0..1023) power supply from the port (in units of 0.1 w) lldpxmedlocxpoepseportpdpriority 1.0.8802.1.1.2.1.5.4795.1.2.11.1.2 r/o integer * unknown(1) * critical(2) * high(3) * low(4) port power supply priority order lldpxmedlocxpoepsepowersource 1.0.8802.1.1.2.1.5.4795.1.2.12 r/o integer * unknown(1) * primary(2) * backup(3) own power source lldpxmedlocxpoepdpowerreq 1.0.8802.1.1.2.1.5.4795.1.2.13 r/o integer32 (0..1023) power requirement for pse (in units of 0.1 w) lldpxmedlocxpoepdpowersource 1.0.8802.1.1.2.1.5.4795.1.2.14 r/o integer * unknown(1) * frompse(2) * local * localandpse(4) type of own power source notified to the pse lldpxmedlocxpoepdpowerpriority 1.0.8802.1.1.2.1.5.4795.1.2.15 r/o integer * unknown(1) * critical(2) * high(3) * low(4) power supply priority requirement of the own device notified to the pse lldpxmedremotedata group mib name oid access syntax description lldpxmedremxpoetable 1.0.8802.1.1.2.1.5.4795.1.3.5 n/a remote device information table lldpxmedremxpoeentry 1.0.8802.1.1.2.1.5.4795.1.3.5.1 n/a index * lldpremtimemark * lldpremlocalportnum * lldpremindex lldpxmedremxpoedevicetype 1.0.8802.1.1.2.1.5.4795.1.3.5.1.1 r/o integer * unknown(1) * psedevice(2) * pddevice(3) * none(4) indicates whether the remote device is pse or pd lldpxmedremxpoepsetable 1.0.8802.1.1.2.1.5.4795.1.3.6 n/a pse information table for remote device lldpxmedremxpoepseentry 1.0.8802.1.1.2.1.5.4795.1.3.6.1 n/a index * lldpremtimemark * lldpremlocalportnum * lldpremindex lldpxmedremxpoepsepowerav 1.0.8802.1.1.2.1.5.4795.1.3.6.1.1 r/o integer(0..1023) power requirement of remote device (in units of 0.1 w) lldpxmedremxpoepsepowersource 1.0.8802.1.1.2.1.5.4795.1.3.6.1.2 r/o integer * unknown(1) * frompse(2) * local(3) * localandpse(4) power supply type of remote device lldpxmedremxpoepdpowerpriority 1.0.8802.1.1.2.1.5.4795.1.3.6.1.3 r/o integer * unknown(1) * critical(2) * high(3) * low(4) power supply priority of remote device lldpxmedremxpoepdtable 1.0.8802.1.1.2.1.5.4795.1.3.7 n/a pse information table for remote device lldpxmedremxpoepdentry 1.0.8802.1.1.2.1.5.4795.1.3.7.1 n/a index * lldpremtimemark * lldpremlocalportnum * lldpremindex lldpxmedremxpoepdpowerreq 1.0.8802.1.1.2.1.5.4795.1.3.7.1.1 r/o integer(0..1023) power requirement of remote device (in units of 0.1 w) lldpxmedremxpoepdpowersource 1.0.8802.1.1.2.1.5.4795.1.3.7.1.2 r/o integer * unknown(1) * frompse(2) * local(3) * localandpse(4) power supply type of remote device lldpxmedremxpoepdpowerpriority 1.0.8802.1.1.2.1.5.4795.1.3.7.1.3 r/o integer * unknown(1) * critical(2) * high(3) * low(4) power supply priority of remote device the lldpv2mib group is divided into subgroups, such as shown below. lldpv2mib(13)     |     +--lldpv2objects(1)        |        +--lldpv2configuration(1)        |        +--lldpv2statistics(2)        |        +--lldpv2localsystemdata(3)        |        +--lldpv2remotesystemsdata(4)        |        +--lldpv2extensions(5)           |           +--lldpv2xdot3mib(4623)              |              +--lldpv2xdot3objects(1)                 |                 +--lldpv2xdot3localdata(2)                 |                 +--lldpv2xdot3remotedata(3) lldpv2configuration group mib name oid access syntax description lldpv2portconfigtable 1.3.111.2.802.1.1.13.1.1.8 n/a table for managing transmitted information for each port lldpv2portconfigentry 1.3.111.2.802.1.1.13.1.1.8.1 n/a index * lldpv2portconfigifindex * lldpv2portconfigdestaddressindex lldpv2portconfigifindex 1.3.111.2.802.1.1.13.1.1.8.1.1 n/a interfaceindex index for each port lldpv2portconfigdestaddressindex 1.3.111.2.802.1.1.13.1.1.8.1.2 n/a lldpv2destaddresstableindex destination mac address index lldpv2portconfigadminstatus 1.3.111.2.802.1.1.13.1.1.8.1.3 r/o integer * txonly(1) * rxonly(2) * txandrx(3) * disabled(4) lldp transmission/reception status lldpv2portconfignotificationenable 1.3.111.2.802.1.1.13.1.1.8.1.4 r/o truthvalue lldp notification status lldpv2portconfigtlvstxenable 1.3.111.2.802.1.1.13.1.1.8.1.5 r/o bits * portdesc(0) * sysname(1) * sysdesc(2) * syscap(3) basic management tlv transmission item lldpv2destaddresstable 1.3.111.2.802.1.1.13.1.1.9 n/a table of mac addresses used by lldp lldpv2destaddresstableentry 1.3.111.2.802.1.1.13.1.1.9.1 n/a index * lldpv2addresstableindex lldpv2addresstableindex 1.3.111.2.802.1.1.13.1.1.9.1.1 n/a lldpv2destaddresstableindex destination mac address index lldpv2destmacaddress 1.3.111.2.802.1.1.13.1.1.9.1.2 r/o macaddress mac address used for lldp transmission lldpv2statistics group mib name oid access syntax description lldpv2statsremtableslastchangetime 1.3.111.2.802.1.1.13.1.2.1 r/o timestamp time from system initialization until remote data update lldpv2statsremtablesinserts 1.3.111.2.802.1.1.13.1.2.2 r/o zerobasedcounter32 total number of entries added to device management table lldpv2statsremtablesdeletes 1.3.111.2.802.1.1.13.1.2.3 r/o zerobasedcounter32 total number of entries deleted from device management table lldpv2statsremtablesdrops 1.3.111.2.802.1.1.13.1.2.4 r/o zerobasedcounter32 total number of entries that could not be set to device management table lldpv2statsremtablesageouts 1.3.111.2.802.1.1.13.1.2.5 r/o zerobasedcounter32 total number of entries that exceeded ttl time (aged out) and were deleted from device management table lldpv2statstxporttable 1.3.111.2.802.1.1.13.1.2.6 n/a table of statistical information for lldp transmission lldpv2statstxportentry 1.3.111.2.802.1.1.13.1.2.6.1 n/a index * lldpv2statstxifinde * lldpv2statstxdestmacaddress lldpv2statstxifindex 1.3.111.2.802.1.1.13.1.2.6.1.1 n/a interfaceindex port index lldpv2statstxdestmacaddress 1.3.111.2.802.1.1.13.1.2.6.1.2 n/a lldpv2destaddresstableindex destination mac address index lldpv2statstxportframestotal 1.3.111.2.802.1.1.13.1.2.6.1.3 r/o counter32 total number of lldp frames transmitted lldpv2statstxlldpdulengtherrors 1.3.111.2.802.1.1.13.1.2.6.1.4 r/o counter32 total no. of lldp frame length errors lldpv2statsrxporttable 1.3.111.2.802.1.1.13.1.2.7 n/a table of statistical information for lldp reception lldpv2statsrxportentry 1.3.111.2.802.1.1.13.1.2.7.1 n/a index * lldpv2statsrxdestifindex * lldpv2statsrxdestmacaddress lldpv2statsrxdestifindex 1.3.111.2.802.1.1.13.1.2.7.1.1 n/a interfaceindex port index lldpv2statsrxdestmacaddress 1.3.111.2.802.1.1.13.1.2.7.1.2 n/a lldpv2destaddresstableindex destination mac address index lldpv2statsrxportframesdiscardedtotal 1.3.111.2.802.1.1.13.1.2.7.1.3 r/o counter32 number of lldp frames discarded lldpv2statsrxportframeserrors 1.3.111.2.802.1.1.13.1.2.7.1.4 r/o counter32 number of error frames received lldpv2statsrxportframestotal 1.3.111.2.802.1.1.13.1.2.7.1.5 r/o counter32 number of lldp frames received lldpv2statsrxporttlvsdiscardedtotal 1.3.111.2.802.1.1.13.1.2.7.1.6 r/o counter32 number of lldp frames discarded lldpv2statsrxporttlvsunrecognizedtotal 1.3.111.2.802.1.1.13.1.2.7.1.7 r/o counter32 number of unrecognized tlvs received lldpv2statsrxportageoutstotal 1.3.111.2.802.1.1.13.1.2.7.1.8 r/o zerobasedcounter32 number of entries that aged-out lldpv2localsystemdata group mib name oid access syntax description lldpv2locchassisidsubtype 1.3.111.2.802.1.1.13.1.3.1 r/o lldpv2chassisidsubtype subtype of chassis id lldpv2locchassisid 1.3.111.2.802.1.1.13.1.3.2 r/o lldpv2chassisid chassis id lldpv2locsysname 1.3.111.2.802.1.1.13.1.3.3 r/o snmpadminstring (size (0..255)) system name lldpv2locsysdesc 1.3.111.2.802.1.1.13.1.3.4 r/o snmpadminstring (size (0..255)) system description lldpv2locsyscapsupported 1.3.111.2.802.1.1.13.1.3.5 r/o lldpv2systemcapabilitiesmap functions supported by the system lldpv2locsyscapenabled 1.3.111.2.802.1.1.13.1.3.6 r/o lldpv2systemcapabilitiesmap functions enabled by the system lldpv2locporttable 1.3.111.2.802.1.1.13.1.3.7 n/a table of local port information lldpv2locportentry 1.3.111.2.802.1.1.13.1.3.7.1 n/a index * lldpv2locportifindex lldpv2locportifindex 1.3.111.2.802.1.1.13.1.3.7.1.1 n/a interfaceindex port index lldpv2locportidsubtype 1.3.111.2.802.1.1.13.1.3.7.1.2 r/o lldpv2portidsubtype subtype of port id lldpv2locportid 1.3.111.2.802.1.1.13.1.3.7.1.3 r/o lldpv2portid port id lldpv2locportdesc 1.3.111.2.802.1.1.13.1.3.7.1.4 r/o snmpadminstring (size (0..255)) port description lldpv2locmanaddrtable 1.3.111.2.802.1.1.13.1.3.8 n/a table of local system management addresses lldpv2locmanaddrentry 1.3.111.2.802.1.1.13.1.3.8.1 n/a index * lldpv2locmanaddrsubtype * lldpv2locmanaddr lldpv2locmanaddrsubtype 1.3.111.2.802.1.1.13.1.3.8.1.1 n/a addressfamilynumbers sub-type for management address lldpv2locmanaddr 1.3.111.2.802.1.1.13.1.3.8.1.2 n/a lldpv2manaddress management address lldpv2locmanaddrlen 1.3.111.2.802.1.1.13.1.3.8.1.3 r/o unsigned32 management address length lldpv2locmanaddrifsubtype 1.3.111.2.802.1.1.13.1.3.8.1.4 r/o lldpv2manaddrifsubtype interface sub-type lldpv2locmanaddrifid 1.3.111.2.802.1.1.13.1.3.8.1.5 r/o unsigned32 interface id lldpv2remotesystemsdata group mib name oid access syntax description lldpv2remtable 1.3.111.2.802.1.1.13.1.4.1 n/a table of information for connected remote devices lldpv2rementry 1.3.111.2.802.1.1.13.1.4.1.1 n/a index * lldpv2remtimemark * lldpv2remlocalifindex * lldpv2remlocaldestmacaddress * lldpv2remindex lldpv2remtimemark 1.3.111.2.802.1.1.13.1.4.1.1.1 n/a timefilter time filter for lldpv2rementry lldpv2remlocalifindex 1.3.111.2.802.1.1.13.1.4.1.1.2 n/a interfaceindex port index lldpv2remlocaldestmacaddress 1.3.111.2.802.1.1.13.1.4.1.1.3 n/a lldpv2destaddresstableindex destination mac address lldpv2remindex 1.3.111.2.802.1.1.13.1.4.1.1.4 n/a unsigned32(1..2147483647) remote system index lldpv2remchassisidsubtype 1.3.111.2.802.1.1.13.1.4.1.1.5 r/o lldpv2chassisidsubtype subtype of chassis id lldpv2remchassisid 1.3.111.2.802.1.1.13.1.4.1.1.6 r/o lldpv2chassisid chassis id lldpv2remportidsubtype 1.3.111.2.802.1.1.13.1.4.1.1.7 r/o lldpv2portidsubtype subtype of port id lldpv2remportid 1.3.111.2.802.1.1.13.1.4.1.1.8 r/o lldpv2portid port id lldpv2remportdesc 1.3.111.2.802.1.1.13.1.4.1.1.9 r/o snmpadminstring (size (0..255)) port description lldpv2remsysname 1.3.111.2.802.1.1.13.1.4.1.1.10 r/o snmpadminstring (size (0..255)) system name lldpv2remsysdesc 1.3.111.2.802.1.1.13.1.4.1.1.11 r/o snmpadminstring (size (0..255)) system description lldpv2remsyscapsupported 1.3.111.2.802.1.1.13.1.4.1.1.12 r/o lldpv2systemcapabilitiesmap functions supported by the system lldpv2remsyscapenabled 1.3.111.2.802.1.1.13.1.4.1.1.13 r/o lldpv2systemcapabilitiesmap functions enabled on the system lldpv2remremotechanges 1.3.111.2.802.1.1.13.1.4.1.1.14 r/o truthvalue flag indicating that a change in the mib occurred on the remote device lldpv2remtoomanyneighbors 1.3.111.2.802.1.1.13.1.4.1.1.15 r/o truthvalue flag indicating that the number of connected remote devices exceeded the limit of the management table lldpv2remmanaddrtable 1.3.111.2.802.1.1.13.1.4.2 n/a table of remote system management addresses lldpv2remmanaddrentry 1.3.111.2.802.1.1.13.1.4.2.1 n/a index * lldpv2remtimemark * lldpv2remlocalifindex * lldpv2remlocaldestmacaddress * lldpv2remindex * lldpv2remmanaddrsubtype * lldpv2remmanaddr lldpv2remmanaddrsubtype 1.3.111.2.802.1.1.13.1.4.2.1.1 n/a addressfamilynumbers sub-type for management address lldpv2remmanaddr 1.3.111.2.802.1.1.13.1.4.2.1.2 n/a lldpv2manaddress remote system management addresses lldpv2remmanaddrifsubtype 1.3.111.2.802.1.1.13.1.4.2.1.3 r/o lldpv2manaddrifsubtype interface sub-type lldpv2remmanaddrifid 1.3.111.2.802.1.1.13.1.4.2.1.4 r/o unsigned32 interface id lldpv2remmanaddroid 1.3.111.2.802.1.1.13.1.4.2.1.5 r/o object identifier oid of management address lldpv2remunknowntlvtable 1.3.111.2.802.1.1.13.1.4.3 n/a table of undefined tlv information lldpv2remunknowntlventry 1.3.111.2.802.1.1.13.1.4.3.1 n/a index * lldpv2remtimemark * lldpv2remlocalifindex * lldpv2remlocaldestmacaddress * lldpv2remindex * lldpv2remunknowntlvtype lldpv2remunknowntlvtype 1.3.111.2.802.1.1.13.1.4.3.1.1 n/a unsigned32(9..126) undefined tlv types lldpv2remunknowntlvinfo 1.3.111.2.802.1.1.13.1.4.3.1.2 r/o octet string (size (0..511)) information for undefined tlvs lldpv2remorgdefinfotable 1.3.111.2.802.1.1.13.1.4.4 n/a table for oui information lldpv2remorgdefinfoentry 1.3.111.2.802.1.1.13.1.4.4.1 n/a index * lldpv2remtimemark * lldpv2remlocalifindex * lldpv2remlocaldestmacaddress * lldpv2remindex * lldpv2remorgdefinfooui * lldpv2remorgdefinfosubtype * lldpv2remorgdefinfoindex lldpv2remorgdefinfooui 1.3.111.2.802.1.1.13.1.4.4.1.1 n/a octet string (size (3)) oui information for remote system lldpv2remorgdefinfosubtype 1.3.111.2.802.1.1.13.1.4.4.1.2 n/a unsigned32(1..255) oui information sub-type for remote system lldpv2remorgdefinfoindex 1.3.111.2.802.1.1.13.1.4.4.1.3 n/a unsigned32(1..2147483647) index for oui information and oui information sub-types lldpv2remorgdefinfo 1.3.111.2.802.1.1.13.1.4.4.1.4 r/o octet string (size (0..507)) information defined for each organization lldpv2xdot3localdata group mib name oid access syntax description lldpv2xdot3locpowertable 1.3.111.2.802.1.1.13.1.5.4623.1.2.2 n/a poe information table for each port lldpv2xdot3locpowerentry 1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1 n/a index * lldpv2locportifindex lldpv2xdot3locpowerportclass 1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.1 r/o lldpv2powerportclass pse or pd status lldpv2xdot3locpowermdisupported 1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.2 r/o truthvalue power supply capability support status lldpv2xdot3locpowermdienabled 1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.3 r/o truthvalue enables/disables the power supply capability lldpv2xdot3locpowerpaircontrolable 1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.4 r/o truthvalue ability to select wiring to be used for power supply lldpv2xdot3locpowerpairs 1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.5 r/o unsigned32(1|2) selection of wiring to be used for power supply lldpv2xdot3locpowerclass 1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.6 r/o unsigned32(1|2|3|4|5) power class lldpv2xdot3remotedata group mib name oid access syntax description lldpv2xdot3rempowertable 1.3.111.2.802.1.1.13.1.5.4623.1.3.2 n/a poe information for remote system lldpv2xdot3rempowerentry 1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1 n/a index * lldpv2remtimemark * lldpv2remlocalifindex * lldpv2remlocaldestmacaddress * lldpv2remindex lldpv2xdot3rempowerportclass 1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.1 r/o lldpv2powerportclass pse or pd status lldpv2xdot3rempowermdisupported 1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.2 r/o truthvalue power supply capability support lldpv2xdot3rempowermdienabled 1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.3 r/o truthvalue enables/disables the power supply capability lldpv2xdot3rempowerpaircontrolable 1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.4 r/o truthvalue ability to select the signal line to be used for power supply lldpv2xdot3rempowerpairs 1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.5 r/o unsigned32(1|2) signal line to be used for power supply lldpv2xdot3rempowerclass 1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.6 r/o unsigned32(1|2|3|4|5) port power class</div><div class="display_word">4.2. lldpMIB group This MIB is related to LLDP information. This product handles the following two MIB groups involved in the LLDP. lldpMIB group (MIB defined in IEEE Std 802.1AB-2005) lldpV2MIB group (MIB defined in IEEE Std 802.1AB-2009) Though both MIBs handle the LLDP in the same way, both are supported to provide compatibility with other models. Some MIBs refer to the same value. The syntax defined for the lldpMIB group is shown below. Syntax defined in the lldpMIB group Syntax Definition LldpChassisIdSubtype INTEGER * chassisComponent(1) * interfaceAlias(2) * portComponent(3) * macAddress(4) * networkAddress(5) * interfaceName(6) * local(7) LldpChassisId OCTET STRING (SIZE (1..255)) LldpPortIdSubtype INTEGER * interfaceAlias(1) * portComponent(2) * macAddress(3) * networkAddress(4) * interfaceName(5) * agentCircuitId(6) * local(7) LldpPortId OCTET STRING (SIZE (1..255)) LldpSystemCapabilitiesMap BITS * other(0) * repeater(1) * bridge(2) * wlanAccessPoint(3) * router(4) * telephone(5) * docsisCableDevice(6) * stationOnly(7) LldpPortNumber INTEGER32 (1..4096) LldpPowerPortClass INTEGER * pClassPSE(1) * pClassPD(2) LldpXMedDeviceClass INTEGER * notDefined(0) * endpointClass1(1) * endpointClass2(2) * endpointClass3(3) * networkConnectivity(4) LldpXMedCapabilities INTEGER * capabilities(0) * networkPolicy(1) * location(2) * extendedPSE(3) * extendedPD(4) * inventory(5) LldpManAddress OCTET STRING (SIZE (1..31)) LldpManAddrIfSubtype INTEGER * unknown(1) * ifIndex(2) * systemPortNumber(3) The lldpMIB group is divided into subgroups, such as shown below. lldpObjects(1)     |     +--lldpConfiguration(1)     |     +--lldpStatistics(2)     |     +--lldpLocalSystemData(3)     |     +--lldpRemoteSystemsData(4)     |     +--lldpExtensions(5)        |        +--lldpXdot3MIB(4623)        ||        |+--lldpXdot3Objects(1)        ||        |+--lldpXdot3Config(1)        ||        |+--lldpXdot3LocalData(2)        ||        |+--lldpXdot3RemoteData(3)        |        +--lldpXMedMIB(4795)           |           +--lldpXMedObjects(1)              |              +--lldpXMedConfig(1)              |              +--lldpXMedLocalData(2)              |              +--lldpXMedRemoteData(3) lldpConfiguration group MIB name OID Access Syntax Description lldpPortConfigTable 1.0.8802.1.1.2.1.1.6 N/A Table of information for each port lldpPortConfigEntry 1.0.8802.1.1.2.1.1.6.1 N/A INDEX * lldpPortConfigPortNum lldpPortConfigAdminStatus 1.0.8802.1.1.2.1.1.6.1.2 R/NW INTEGER * txOnly(1) * rxOnly(2) * txAndRx(3) * disabled(4) LLDP transmission/reception status lldpPortConfigNotificationEnable 1.0.8802.1.1.2.1.1.6.1.3 R/NW TruthVal LLDP notification status lldpPortConfigTLVsTxEnable 1.0.8802.1.1.2.1.1.6.1.4 R/NW BITS * portDesc(0) * sysName(1) * sysDesc(2) * sysCap(3) Basic management TLV transmission item lldpStatistics group MIB name OID Access Syntax Description lldpStatsRemTablesLastChangeTime 1.0.8802.1.1.2.1.2.1 R/O TimeTicks Time from system initialization until remote data update lldpStatsRemTablesInserts 1.0.8802.1.1.2.1.2.2 R/O INTEGER (0..4294967295) Total number of entries added to the remote device management table lldpStatsRemTablesDeletes 1.0.8802.1.1.2.1.2.3 R/O INTEGER (0..4294967295) Total number of entries deleted from the remote device management table lldpStatsRemTablesDrops 1.0.8802.1.1.2.1.2.4 R/O INTEGER (0..4294967295) Total number of entries that could not be specified in the remote device management table lldpStatsRemTablesAgeouts 1.0.8802.1.1.2.1.2.5 R/O INTEGER (0..4294967295) Total number of entries that exceeded the TTL time (aged out) and were deleted from the remote device management table lldpStatsTxPortTable 1.0.8802.1.1.2.1.2.6 N/A Table of information for each port lldpStatsTxPortEntry 1.0.8802.1.1.2.1.2.6.1 N/A INDEX * lldpStatsTxPortNum lldpStatsTxPortNum 1.0.8802.1.1.2.1.2.6.1.1 N/A LldpPortNumber lldpStatsTxPortFramesTotal 1.0.8802.1.1.2.1.2.6.1.2 R/O INTEGER (0..4294967295) Total number of LLDP frames transmitted lldpStatsRxPortTable 1.0.8802.1.1.2.1.2.7 N/A Table of information for each port lldpStatsRxPortEntry 1.0.8802.1.1.2.1.2.7.1 N/A INDEX * lldpStatsRxPortNum lldpStatsRxPortNum 1.0.8802.1.1.2.1.2.7.1.1 N/A LldpPortNumber lldpStatsRxPortFramesDiscardedTotal 1.0.8802.1.1.2.1.2.7.1.2 R/O INTEGER (0..4294967295) Number of LLDP frames discarded lldpStatsRxPortFramesErrors 1.0.8802.1.1.2.1.2.7.1.3 R/O INTEGER (0..4294967295) Number of error frames received lldpStatsRxPortFramesTotal 1.0.8802.1.1.2.1.2.7.1.4 R/O INTEGER (0..4294967295) Number of LLDP frames received lldpStatsRxPortTLVsDiscardedTotal 1.0.8802.1.1.2.1.2.7.1.5 R/O INTEGER (0..4294967295) Number of TLVs discarded lldpStatsRxPortTLVsUnrecognizedTotal 1.0.8802.1.1.2.1.2.7.1.6 R/O INTEGER (0..4294967295) Number of unrecognized TLVs received lldpStatsRxPortAgeoutsTotal 1.0.8802.1.1.2.1.2.7.1.7 R/O INTEGER (0..4294967295) Number of entries that aged-out lldpLocalSystemData group MIB name OID Access Syntax Description lldpLocChassisIdSubtype 1.0.8802.1.1.2.1.3.1 R/O LldpChassisIdSubtype Subtype of chassis ID lldpLocChassisId 1.0.8802.1.1.2.1.3.2 R/O LldpChassisId Chassis ID lldpLocSysName 1.0.8802.1.1.2.1.3.3 R/O SnmpAdminString (SIZE (0..255)) System name lldpLocSysDesc 1.0.8802.1.1.2.1.3.4 R/O SnmpAdminString (SIZE (0..255)) System description lldpLocSysCapSupported 1.0.8802.1.1.2.1.3.5 R/O LldpSystemCapabilitiesMap Functions supported by the system lldpLocSysCapEnabled 1.0.8802.1.1.2.1.3.6 R/O LldpSystemCapabilitiesMap Functions enabled by the system lldpLocPortTable 1.0.8802.1.1.2.1.3.7 N/A Table of information for each port lldpLocPortEntry 1.0.8802.1.1.2.1.3.7.1 N/A INDEX * lldpLocPortNum lldpLocPortNum 1.0.8802.1.1.2.1.3.7.1.1 N/A LldpPortNumber lldpLocPortIdSubtype 1.0.8802.1.1.2.1.3.7.1.2 R/O LldpPortIdSubtype Subtype of port ID lldpLocPortId 1.0.8802.1.1.2.1.3.7.1.3 R/O OCTET STRING (SIZE (1..255)) Port ID lldpLocPortDesc 1.0.8802.1.1.2.1.3.7.1.4 R/O SnmpAdminString (SIZE (0..255)) Port description lldpLocManAddrTable 1.0.8802.1.1.2.1.3.8 N/A Table of local system management addresses lldpLocManAddrEntry 1.0.8802.1.1.2.1.3.8.1 N/A INDEX * lldpV2LocManAddrSubtype * lldpLocManAddr lldpLocManAddrSubtype 1.0.8802.1.1.2.1.3.8.1.1 N/A AddressFamilyNumbers Sub-type for management address lldpLocManAddr 1.0.8802.1.1.2.1.3.8.1.2 N/A LldpManAddress Management address lldpLocManAddrLen 1.0.8802.1.1.2.1.3.8.1.3 R/O Integer32 Management address length lldpLocManAddrIfSubtype 1.0.8802.1.1.2.1.3.8.1.4 R/O LldpManAddrIfSubtype Interface sub-type lldpLocManAddrIfId 1.0.8802.1.1.2.1.3.8.1.5 R/O Integer32 Interface ID lldpRemoteSystemsData group MIB name OID Access Syntax Description lldpRemTable 1.0.8802.1.1.2.1.4.1 N/A Table of information for each port lldpRemEntry 1.0.8802.1.1.2.1.4.1.1 N/A INDEX * lldpRemTimeMark * lldpRemLocalPortNum * lldpRemIndex lldpRemTimeMark 1.0.8802.1.1.2.1.4.1.1.1 N/A TimeFilter lldpRemLocalPortNum 1.0.8802.1.1.2.1.4.1.1.2 N/A LldpPortNumber lldpRemIndex 1.0.8802.1.1.2.1.4.1.1.3 N/A INTEGER32 (1..2147483647) lldpRemChassisIdSubtype 1.0.8802.1.1.2.1.4.1.1.4 R/O LldpChassisIdSubtype Subtype of the remote device chassis ID lldpRemChassisId 1.0.8802.1.1.2.1.4.1.1.5 R/O SnmpAdminString (SIZE (0..255)) Chassis ID of remote device lldpRemPortIdSubtype 1.0.8802.1.1.2.1.4.1.1.6 R/O LldpPortIdSubtype Subtype of the remote device port ID lldpRemPortId 1.0.8802.1.1.2.1.4.1.1.7 R/O OCTET STRING (SIZE (1..255)) Port ID of remote device lldpRemPortDesc 1.0.8802.1.1.2.1.4.1.1.8 R/O SnmpAdminString (SIZE (0..255)) Description of remote device port lldpRemSysName 1.0.8802.1.1.2.1.4.1.1.9 R/O SnmpAdminString (SIZE (0..255)) System name of remote device lldpRemSysDesc 1.0.8802.1.1.2.1.4.1.1.10 R/O SnmpAdminString (SIZE (0..255)) System description of remote device lldpRemSysCapSupported 1.0.8802.1.1.2.1.4.1.1.11 R/O LldpSystemCapabilitiesMap Functionality supported by the remote device system lldpRemSysCapEnabled 1.0.8802.1.1.2.1.4.1.1.12 R/O LldpSystemCapabilitiesMap Functionality enabled in the remote device system lldpRemManAddrTable 1.0.8802.1.1.2.1.4.2 N/A lldpRemManAddrEntry 1.0.8802.1.1.2.1.4.2.1 N/A INDEX * lldpRemTimeMark * lldpRemLocalPortNum * lldpRemIndex * lldpRemManAddrSubtype * lldpRemManAddr lldpRemManAddrSubtype 1.0.8802.1.1.2.1.4.2.1.1 N/A LldpPortNumber lldpRemManAddr 1.0.8802.1.1.2.1.4.2.1.2 N/A lldpRemManAddrIfSubtype 1.0.8802.1.1.2.1.4.2.1.3 R/O INTEGER * unknown(1) * ifIndex(2) * systemPortNumber(3) Subtype of remote device interface lldpRemManAddrIfId 1.0.8802.1.1.2.1.4.2.1.4 R/O Integer32 Interface ID of remote device lldpRemManAddrOID 1.0.8802.1.1.2.1.4.2.1.5 R/O OBJECT IDENTIFIER OID of the remote device management address lldpRemUnknownTLVTable 1.0.8802.1.1.2.1.4.3 N/A lldpRemUnknownTLVEntry 1.0.8802.1.1.2.1.4.3.1 N/A INDEX * lldpRemTimeMark * lldpRemLocalPortNum * lldpRemIndex * lldpRemUnknownTLVType lldpRemUnknownTLVType 1.0.8802.1.1.2.1.4.3.1.1 N/A LldpPortNumber lldpRemUnknownTLVInfo 1.0.8802.1.1.2.1.4.3.1.2 R/O LldpPortNumber Latest undefined TLV information for remote device lldpRemOrgDefInfoTable 1.0.8802.1.1.2.1.4.4 N/A lldpRemOrgDefInfoEntry 1.0.8802.1.1.2.1.4.4.1 N/A INDEX * lldpRemTimeMark * lldpRemLocalPortNum * lldpRemIndex * lldpRemOrgDefInfoOUI * lldpRemOrgDefInfoSubtype * lldpRemOrgDefInfoIndex lldpRemOrgDefInfoOUI 1.0.8802.1.1.2.1.4.4.1.1 N/A lldpRemOrgDefInfoSubtype 1.0.8802.1.1.2.1.4.4.1.2 N/A lldpRemOrgDefInfoIndex 1.0.8802.1.1.2.1.4.4.1.3 N/A lldpRemOrgDefInfo 1.0.8802.1.1.2.1.4.4.1.4 R/O OCTET STRING (SIZE (0..507)) Index of undefined TLV information for remote device (Limited to IEEE802.1 and IEEE802.3) lldpXdot3LocalData group MIB name OID Access Syntax Description lldpXdot3LocPowerTable 1.0.8802.1.1.2.1.5.4623.1.2.2 N/A Table of information for each port lldpXdot3LocPowerEntry 1.0.8802.1.1.2.1.5.4623.1.2.2.1 N/A INDEX * lldpLocPortNum lldpXdot3LocPowerPortClass 1.0.8802.1.1.2.1.5.4623.1.2.2.1.1 R/O LldpPowerPortClass PSE or PD status lldpXdot3LocPowerMDISupported 1.0.8802.1.1.2.1.5.4623.1.2.2.1.2 R/O TruthValue Power supply capability support lldpXdot3LocPowerMDIEnabled 1.0.8802.1.1.2.1.5.4623.1.2.2.1.3 R/O TruthValue Enables/disables the power supply capability lldpXdot3LocPowerPairControlable 1.0.8802.1.1.2.1.5.4623.1.2.2.1.4 R/O TruthValue Ability to select the signal line to be used for power supply lldpXdot3LocPowerPairs 1.0.8802.1.1.2.1.5.4623.1.2.2.1.5 R/O INTEGER32 (1|2) * signal(1) * spare(2) Signal line to be used for power supply lldpXdot3LocPowerClass 1.0.8802.1.1.2.1.5.4623.1.2.2.1.6 R/O INTEGER32 (1|2|3|4|5) * class0(1) * class1(2) * class2(3) * class3(4) * class4(5) Port power class lldpXdot3RemoteData group MIB name OID Access Syntax Description lldpXdot3RemPowerTable 1.0.8802.1.1.2.1.5.4623.1.3.2 N/A Table of information for each port lldpXdot3RemPowerEntry 1.0.8802.1.1.2.1.5.4623.1.3.2.1 N/A INDEX * lldpRemTimeMark * lldpRemLocalPortNum * lldpRemIndex lldpXdot3RemPowerPortClass 1.0.8802.1.1.2.1.5.4623.1.3.2.1.1 R/O LldpPowerPortClass Remote device status whether it is PSE or PD lldpXdot3RemPowerMDISupported 1.0.8802.1.1.2.1.5.4623.1.3.2.1.2 R/O TruthValue Remote device power supply capability support lldpXdot3RemPowerMDIEnabled 1.0.8802.1.1.2.1.5.4623.1.3.2.1.3 R/O TruthValue Enables/disables the remote device power supply capability lldpXdot3RemPowerPairControlable 1.0.8802.1.1.2.1.5.4623.1.3.2.1.4 R/O TruthValue Ability to select the signal line to be used for power supply of remote device lldpXdot3RemPowerPairs 1.0.8802.1.1.2.1.5.4623.1.3.2.1.5 R/O INTEGER32 (1|2) * signal(1) * spare(2) Signal line to be used for power supply of remote device lldpXdot3RemPowerClass 1.0.8802.1.1.2.1.5.4623.1.3.2.1.6 R/O INTEGER32 (1|2|3|4|5) * class0(1) * class1(2) * class2(3) * class3(4) * class4(5) Remote device port power class lldpXMedConfig group MIB name OID Access Syntax Description lldpXMedLocDeviceClass 1.0.8802.1.1.2.1.5.4795.1.1.1 R/O LldpXMedDeviceClass Local device class lldpXMedPortConfigTable 1.0.8802.1.1.2.1.5.4795.1.1.2 N/A Table of information for each port lldpXMedPortConfigEntry 1.0.8802.1.1.2.1.5.4795.1.1.2.1 N/A INDEX * Port number lldpXMedPortCapSupported 1.0.8802.1.1.2.1.5.4795.1.1.2.1.1 R/O LldpXMedCapabilities TLV transmission items supported by LLDP-MED lldpXMedPortConfigTLVsTxEnable 1.0.8802.1.1.2.1.5.4795.1.1.2.1.2 R/NW LldpXMedCapabilities TLV items sent as LLDP-MED lldpXMedPortConfigNotifEnable 1.0.8802.1.1.2.1.5.4795.1.1.2.1.3 R/NW TruthValue LLDP-MED notification status lldpXMedFastStartRepeatCount 1.0.8802.1.1.2.1.5.4795.1.1.3 R/NW Unsigned32 (1..10) LLDP-MED fast transmission count lldpXMedLocalData group MIB name OID Access Syntax Description lldpXMedLocXPoEDeviceType 1.0.8802.1.1.2.1.5.4795.1.2.10 R/O INTEGER * unknown(1) * pseDevice(2) * pdDevice(3) * none(4) PSE or PD status lldpXMedLocXPoEPSEPortTable 1.0.8802.1.1.2.1.5.4795.1.2.11 N/A PSE information table for each port lldpXMedLocXPoEPSEPortEntry 1.0.8802.1.1.2.1.5.4795.1.2.11.1 N/A INDEX * lldpLocPortNum lldpXMedLocXPoEPSEPortPowerAv 1.0.8802.1.1.2.1.5.4795.1.2.11.1.1 R/O Gauge32 (0..1023) Power supply from the port (in units of 0.1 W) lldpXMedLocXPoEPSEPortPDPriority 1.0.8802.1.1.2.1.5.4795.1.2.11.1.2 R/O INTEGER * unknown(1) * critical(2) * high(3) * low(4) Port power supply priority order lldpXMedLocXPoEPSEPowerSource 1.0.8802.1.1.2.1.5.4795.1.2.12 R/O INTEGER * unknown(1) * primary(2) * backup(3) Own power source lldpXMedLocXPoEPDPowerReq 1.0.8802.1.1.2.1.5.4795.1.2.13 R/O INTEGER32 (0..1023) Power requirement for PSE (in units of 0.1 W) lldpXMedLocXPoEPDPowerSource 1.0.8802.1.1.2.1.5.4795.1.2.14 R/O INTEGER * unknown(1) * fromPSE(2) * local * localAndPSE(4) Type of own power source notified to the PSE lldpXMedLocXPoEPDPowerPriority 1.0.8802.1.1.2.1.5.4795.1.2.15 R/O INTEGER * unknown(1) * critical(2) * high(3) * low(4) Power supply priority requirement of the own device notified to the PSE lldpXMedRemoteData group MIB name OID Access Syntax Description lldpXMedRemXPoETable 1.0.8802.1.1.2.1.5.4795.1.3.5 N/A Remote device information table lldpXMedRemXPoEEntry 1.0.8802.1.1.2.1.5.4795.1.3.5.1 N/A INDEX * lldpRemTimeMark * lldpRemLocalPortNum * lldpRemIndex lldpXMedRemXPoEDeviceType 1.0.8802.1.1.2.1.5.4795.1.3.5.1.1 R/O INTEGER * unknown(1) * pseDevice(2) * pdDevice(3) * none(4) Indicates whether the remote device is PSE or PD lldpXMedRemXPoEPSETable 1.0.8802.1.1.2.1.5.4795.1.3.6 N/A PSE information table for remote device lldpXMedRemXPoEPSEEntry 1.0.8802.1.1.2.1.5.4795.1.3.6.1 N/A INDEX * lldpRemTimeMark * lldpRemLocalPortNum * lldpRemIndex lldpXMedRemXPoEPSEPowerAv 1.0.8802.1.1.2.1.5.4795.1.3.6.1.1 R/O Integer(0..1023) Power requirement of remote device (in units of 0.1 W) lldpXMedRemXPoEPSEPowerSource 1.0.8802.1.1.2.1.5.4795.1.3.6.1.2 R/O INTEGER * unknown(1) * fromPSE(2) * local(3) * localAndPSE(4) Power supply type of remote device lldpXMedRemXPoEPDPowerPriority 1.0.8802.1.1.2.1.5.4795.1.3.6.1.3 R/O INTEGER * unknown(1) * critical(2) * high(3) * low(4) Power supply priority of remote device lldpXMedRemXPoEPDTable 1.0.8802.1.1.2.1.5.4795.1.3.7 N/A PSE information table for remote device lldpXMedRemXPoEPDEntry 1.0.8802.1.1.2.1.5.4795.1.3.7.1 N/A INDEX * lldpRemTimeMark * lldpRemLocalPortNum * lldpRemIndex lldpXMedRemXPoEPDPowerReq 1.0.8802.1.1.2.1.5.4795.1.3.7.1.1 R/O Integer(0..1023) Power requirement of remote device (in units of 0.1 W) lldpXMedRemXPoEPDPowerSource 1.0.8802.1.1.2.1.5.4795.1.3.7.1.2 R/O INTEGER * unknown(1) * fromPSE(2) * local(3) * localAndPSE(4) Power supply type of remote device lldpXMedRemXPoEPDPowerPriority 1.0.8802.1.1.2.1.5.4795.1.3.7.1.3 R/O INTEGER * unknown(1) * critical(2) * high(3) * low(4) Power supply priority of remote device The lldpV2MIB group is divided into subgroups, such as shown below. lldpV2MIB(13)     |     +--lldpV2Objects(1)        |        +--lldpV2Configuration(1)        |        +--lldpV2Statistics(2)        |        +--lldpV2LocalSystemData(3)        |        +--lldpV2RemoteSystemsData(4)        |        +--lldpV2Extensions(5)           |           +--lldpV2Xdot3MIB(4623)              |              +--lldpV2Xdot3Objects(1)                 |                 +--lldpV2Xdot3LocalData(2)                 |                 +--lldpV2Xdot3RemoteData(3) lldpV2Configuration group MIB name OID Access Syntax Description lldpV2PortConfigTable 1.3.111.2.802.1.1.13.1.1.8 N/A Table for managing transmitted information for each port lldpV2PortConfigEntry 1.3.111.2.802.1.1.13.1.1.8.1 N/A INDEX * lldpV2PortConfigIfIndex * lldpV2PortConfigDestAddressIndex lldpV2PortConfigIfIndex 1.3.111.2.802.1.1.13.1.1.8.1.1 N/A InterfaceIndex Index for each port lldpV2PortConfigDestAddressIndex 1.3.111.2.802.1.1.13.1.1.8.1.2 N/A LldpV2DestAddressTableIndex Destination MAC address index lldpV2PortConfigAdminStatus 1.3.111.2.802.1.1.13.1.1.8.1.3 R/O INTEGER * txOnly(1) * rxOnly(2) * txAndRx(3) * disabled(4) LLDP transmission/reception status lldpV2PortConfigNotificationEnable 1.3.111.2.802.1.1.13.1.1.8.1.4 R/O TruthValue LLDP notification status lldpV2PortConfigTLVsTxEnable 1.3.111.2.802.1.1.13.1.1.8.1.5 R/O BITS * portDesc(0) * sysName(1) * sysDesc(2) * sysCap(3) Basic management TLV transmission item lldpV2DestAddressTable 1.3.111.2.802.1.1.13.1.1.9 N/A Table of MAC addresses used by LLDP lldpV2DestAddressTableEntry 1.3.111.2.802.1.1.13.1.1.9.1 N/A INDEX * lldpV2AddressTableIndex lldpV2AddressTableIndex 1.3.111.2.802.1.1.13.1.1.9.1.1 N/A LldpV2DestAddressTableIndex Destination MAC address index lldpV2DestMacAddress 1.3.111.2.802.1.1.13.1.1.9.1.2 R/O MacAddress MAC address used for LLDP transmission lldpV2Statistics group MIB name OID Access Syntax Description lldpV2StatsRemTablesLastChangeTime 1.3.111.2.802.1.1.13.1.2.1 R/O TimeStamp Time from system initialization until remote data update lldpV2StatsRemTablesInserts 1.3.111.2.802.1.1.13.1.2.2 R/O ZeroBasedCounter32 Total number of entries added to device management table lldpV2StatsRemTablesDeletes 1.3.111.2.802.1.1.13.1.2.3 R/O ZeroBasedCounter32 Total number of entries deleted from device management table lldpV2StatsRemTablesDrops 1.3.111.2.802.1.1.13.1.2.4 R/O ZeroBasedCounter32 Total number of entries that could not be set to device management table lldpV2StatsRemTablesAgeouts 1.3.111.2.802.1.1.13.1.2.5 R/O ZeroBasedCounter32 Total number of entries that exceeded TTL time (aged out) and were deleted from device management table lldpV2StatsTxPortTable 1.3.111.2.802.1.1.13.1.2.6 N/A Table of statistical information for LLDP transmission lldpV2StatsTxPortEntry 1.3.111.2.802.1.1.13.1.2.6.1 N/A INDEX * lldpV2StatsTxIfInde * lldpV2StatsTxDestMACAddress lldpV2StatsTxIfIndex 1.3.111.2.802.1.1.13.1.2.6.1.1 N/A InterfaceIndex Port index lldpV2StatsTxDestMACAddress 1.3.111.2.802.1.1.13.1.2.6.1.2 N/A LldpV2DestAddressTableIndex Destination MAC address index lldpV2StatsTxPortFramesTotal 1.3.111.2.802.1.1.13.1.2.6.1.3 R/O Counter32 Total number of LLDP frames transmitted lldpV2StatsTxLLDPDULengthErrors 1.3.111.2.802.1.1.13.1.2.6.1.4 R/O Counter32 Total no. of LLDP frame length errors lldpV2StatsRxPortTable 1.3.111.2.802.1.1.13.1.2.7 N/A Table of statistical information for LLDP reception lldpV2StatsRxPortEntry 1.3.111.2.802.1.1.13.1.2.7.1 N/A INDEX * lldpV2StatsRxDestIfIndex * lldpV2StatsRxDestMACAddress LldpV2StatsRxDestIfIndex 1.3.111.2.802.1.1.13.1.2.7.1.1 N/A InterfaceIndex Port index lldpV2StatsRxDestMACAddress 1.3.111.2.802.1.1.13.1.2.7.1.2 N/A LldpV2DestAddressTableIndex Destination MAC address index lldpV2StatsRxPortFramesDiscardedTotal 1.3.111.2.802.1.1.13.1.2.7.1.3 R/O Counter32 Number of LLDP frames discarded lldpV2StatsRxPortFramesErrors 1.3.111.2.802.1.1.13.1.2.7.1.4 R/O Counter32 Number of error frames received lldpV2StatsRxPortFramesTotal 1.3.111.2.802.1.1.13.1.2.7.1.5 R/O Counter32 Number of LLDP frames received lldpV2StatsRxPortTLVsDiscardedTotal 1.3.111.2.802.1.1.13.1.2.7.1.6 R/O Counter32 Number of LLDP frames discarded lldpV2StatsRxPortTLVsUnrecognizedTotal 1.3.111.2.802.1.1.13.1.2.7.1.7 R/O Counter32 Number of unrecognized TLVs received lldpV2StatsRxPortAgeoutsTotal 1.3.111.2.802.1.1.13.1.2.7.1.8 R/O ZeroBasedCounter32 Number of entries that aged-out lldpV2LocalSystemData group MIB name OID Access Syntax Description lldpV2LocChassisIdSubtype 1.3.111.2.802.1.1.13.1.3.1 R/O LldpV2ChassisIdSubtype Subtype of chassis ID lldpV2LocChassisId 1.3.111.2.802.1.1.13.1.3.2 R/O LldpV2ChassisId Chassis ID lldpV2LocSysName 1.3.111.2.802.1.1.13.1.3.3 R/O SnmpAdminString (SIZE (0..255)) System name lldpV2LocSysDesc 1.3.111.2.802.1.1.13.1.3.4 R/O SnmpAdminString (SIZE (0..255)) System description lldpV2LocSysCapSupported 1.3.111.2.802.1.1.13.1.3.5 R/O LldpV2SystemCapabilitiesMap Functions supported by the system lldpV2LocSysCapEnabled 1.3.111.2.802.1.1.13.1.3.6 R/O LldpV2SystemCapabilitiesMap Functions enabled by the system lldpV2LocPortTable 1.3.111.2.802.1.1.13.1.3.7 N/A Table of local port information lldpV2LocPortEntry 1.3.111.2.802.1.1.13.1.3.7.1 N/A INDEX * lldpV2LocPortIfIndex lldpV2LocPortIfIndex 1.3.111.2.802.1.1.13.1.3.7.1.1 N/A InterfaceIndex Port index lldpV2LocPortIdSubtype 1.3.111.2.802.1.1.13.1.3.7.1.2 R/O LldpV2PortIdSubtype Subtype of port ID lldpV2LocPortId 1.3.111.2.802.1.1.13.1.3.7.1.3 R/O LldpV2PortId Port ID lldpV2LocPortDesc 1.3.111.2.802.1.1.13.1.3.7.1.4 R/O SnmpAdminString (SIZE (0..255)) Port description lldpV2LocManAddrTable 1.3.111.2.802.1.1.13.1.3.8 N/A Table of local system management addresses lldpV2LocManAddrEntry 1.3.111.2.802.1.1.13.1.3.8.1 N/A INDEX * lldpV2LocManAddrSubtype * lldpV2LocManAddr lldpV2LocManAddrSubtype 1.3.111.2.802.1.1.13.1.3.8.1.1 N/A AddressFamilyNumbers Sub-type for management address lldpV2LocManAddr 1.3.111.2.802.1.1.13.1.3.8.1.2 N/A LldpV2ManAddress Management address lldpV2LocManAddrLen 1.3.111.2.802.1.1.13.1.3.8.1.3 R/O Unsigned32 Management address length lldpV2LocManAddrIfSubtype 1.3.111.2.802.1.1.13.1.3.8.1.4 R/O LldpV2ManAddrIfSubtype Interface sub-type lldpV2LocManAddrIfId 1.3.111.2.802.1.1.13.1.3.8.1.5 R/O Unsigned32 Interface ID lldpV2RemoteSystemsData group MIB name OID Access Syntax Description lldpV2RemTable 1.3.111.2.802.1.1.13.1.4.1 N/A Table of information for connected remote devices lldpV2RemEntry 1.3.111.2.802.1.1.13.1.4.1.1 N/A INDEX * lldpV2RemTimeMark * lldpV2RemLocalIfIndex * lldpV2RemLocalDestMACAddress * lldpV2RemIndex lldpV2RemTimeMark 1.3.111.2.802.1.1.13.1.4.1.1.1 N/A TimeFilter Time filter for lldpV2RemEntry lldpV2RemLocalIfIndex 1.3.111.2.802.1.1.13.1.4.1.1.2 N/A InterfaceIndex Port index lldpV2RemLocalDestMACAddress 1.3.111.2.802.1.1.13.1.4.1.1.3 N/A LldpV2DestAddressTableIndex Destination MAC address lldpV2RemIndex 1.3.111.2.802.1.1.13.1.4.1.1.4 N/A Unsigned32(1..2147483647) Remote system index lldpV2RemChassisIdSubtype 1.3.111.2.802.1.1.13.1.4.1.1.5 R/O LldpV2ChassisIdSubtype Subtype of chassis ID lldpV2RemChassisId 1.3.111.2.802.1.1.13.1.4.1.1.6 R/O LldpV2ChassisId Chassis ID lldpV2RemPortIdSubtype 1.3.111.2.802.1.1.13.1.4.1.1.7 R/O LldpV2PortIdSubtype Subtype of port ID lldpV2RemPortId 1.3.111.2.802.1.1.13.1.4.1.1.8 R/O LldpV2PortId Port ID lldpV2RemPortDesc 1.3.111.2.802.1.1.13.1.4.1.1.9 R/O SnmpAdminString (SIZE (0..255)) Port description lldpV2RemSysName 1.3.111.2.802.1.1.13.1.4.1.1.10 R/O SnmpAdminString (SIZE (0..255)) System name lldpV2RemSysDesc 1.3.111.2.802.1.1.13.1.4.1.1.11 R/O SnmpAdminString (SIZE (0..255)) System description lldpV2RemSysCapSupported 1.3.111.2.802.1.1.13.1.4.1.1.12 R/O LldpV2SystemCapabilitiesMap Functions supported by the system lldpV2RemSysCapEnabled 1.3.111.2.802.1.1.13.1.4.1.1.13 R/O LldpV2SystemCapabilitiesMap Functions enabled on the system lldpV2RemRemoteChanges 1.3.111.2.802.1.1.13.1.4.1.1.14 R/O TruthValue Flag indicating that a change in the MIB occurred on the remote device lldpV2RemTooManyNeighbors 1.3.111.2.802.1.1.13.1.4.1.1.15 R/O TruthValue Flag indicating that the number of connected remote devices exceeded the limit of the management table lldpV2RemManAddrTable 1.3.111.2.802.1.1.13.1.4.2 N/A Table of remote system management addresses lldpV2RemManAddrEntry 1.3.111.2.802.1.1.13.1.4.2.1 N/A INDEX * lldpV2RemTimeMark * lldpV2RemLocalIfIndex * lldpV2RemLocalDestMACAddress * lldpV2RemIndex * lldpV2RemManAddrSubtype * lldpV2RemManAddr lldpV2RemManAddrSubtype 1.3.111.2.802.1.1.13.1.4.2.1.1 N/A AddressFamilyNumbers Sub-type for management address lldpV2RemManAddr 1.3.111.2.802.1.1.13.1.4.2.1.2 N/A LldpV2ManAddress Remote system management addresses lldpV2RemManAddrIfSubtype 1.3.111.2.802.1.1.13.1.4.2.1.3 R/O LldpV2ManAddrIfSubtype Interface sub-type lldpV2RemManAddrIfId 1.3.111.2.802.1.1.13.1.4.2.1.4 R/O Unsigned32 Interface ID lldpV2RemManAddrOID 1.3.111.2.802.1.1.13.1.4.2.1.5 R/O OBJECT IDENTIFIER OID of management address lldpV2RemUnknownTLVTable 1.3.111.2.802.1.1.13.1.4.3 N/A Table of undefined TLV information lldpV2RemUnknownTLVEntry 1.3.111.2.802.1.1.13.1.4.3.1 N/A INDEX * lldpV2RemTimeMark * lldpV2RemLocalIfIndex * lldpV2RemLocalDestMACAddress * lldpV2RemIndex * lldpV2RemUnknownTLVType lldpV2RemUnknownTLVType 1.3.111.2.802.1.1.13.1.4.3.1.1 N/A Unsigned32(9..126) Undefined TLV types lldpV2RemUnknownTLVInfo 1.3.111.2.802.1.1.13.1.4.3.1.2 R/O OCTET STRING (SIZE (0..511)) Information for undefined TLVs lldpV2RemOrgDefInfoTable 1.3.111.2.802.1.1.13.1.4.4 N/A Table for OUI information lldpV2RemOrgDefInfoEntry 1.3.111.2.802.1.1.13.1.4.4.1 N/A INDEX * lldpV2RemTimeMark * lldpV2RemLocalIfIndex * lldpV2RemLocalDestMACAddress * lldpV2RemIndex * lldpV2RemOrgDefInfoOUI * lldpV2RemOrgDefInfoSubtype * lldpV2RemOrgDefInfoIndex lldpV2RemOrgDefInfoOUI 1.3.111.2.802.1.1.13.1.4.4.1.1 N/A OCTET STRING (SIZE (3)) OUI information for remote system lldpV2RemOrgDefInfoSubtype 1.3.111.2.802.1.1.13.1.4.4.1.2 N/A Unsigned32(1..255) OUI information sub-type for remote system lldpV2RemOrgDefInfoIndex 1.3.111.2.802.1.1.13.1.4.4.1.3 N/A Unsigned32(1..2147483647) Index for OUI information and OUI information sub-types lldpV2RemOrgDefInfo 1.3.111.2.802.1.1.13.1.4.4.1.4 R/O OCTET STRING (SIZE (0..507)) Information defined for each organization lldpV2Xdot3LocalData group MIB name OID Access Syntax Description lldpV2Xdot3LocPowerTable 1.3.111.2.802.1.1.13.1.5.4623.1.2.2 N/A POE information table for each port lldpV2Xdot3LocPowerEntry 1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1 N/A INDEX * lldpV2LocPortIfIndex lldpV2Xdot3LocPowerPortClass 1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.1 R/O LldpV2PowerPortClass PSE or PD status lldpV2Xdot3LocPowerMDISupported 1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.2 R/O TruthValue Power supply capability support status lldpV2Xdot3LocPowerMDIEnabled 1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.3 R/O TruthValue Enables/disables the power supply capability lldpV2Xdot3LocPowerPairControlable 1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.4 R/O TruthValue Ability to select wiring to be used for power supply lldpV2Xdot3LocPowerPairs 1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.5 R/O Unsigned32(1|2) Selection of wiring to be used for power supply lldpV2Xdot3LocPowerClass 1.3.111.2.802.1.1.13.1.5.4623.1.2.2.1.6 R/O Unsigned32(1|2|3|4|5) Power class lldpV2Xdot3RemoteData group MIB name OID Access Syntax Description lldpV2Xdot3RemPowerTable 1.3.111.2.802.1.1.13.1.5.4623.1.3.2 N/A POE information for remote system lldpV2Xdot3RemPowerEntry 1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1 N/A INDEX * lldpV2RemTimeMark * lldpV2RemLocalIfIndex * lldpV2RemLocalDestMACAddress * lldpV2RemIndex lldpV2Xdot3RemPowerPortClass 1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.1 R/O LldpV2PowerPortClass PSE or PD status lldpV2Xdot3RemPowerMDISupported 1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.2 R/O TruthValue Power supply capability support lldpV2Xdot3RemPowerMDIEnabled 1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.3 R/O TruthValue Enables/disables the power supply capability lldpV2Xdot3RemPowerPairControlable 1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.4 R/O TruthValue Ability to select the signal line to be used for power supply lldpV2Xdot3RemPowerPairs 1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.5 R/O Unsigned32(1|2) Signal line to be used for power supply lldpV2Xdot3RemPowerClass 1.3.111.2.802.1.1.13.1.5.4623.1.3.2.1.6 R/O Unsigned32(1|2|3|4|5) Port power class</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#lagmibグループ">4.3. lagMIB group</div><div class="search_word">4.3. lagmib group this mib is related to lacp link aggregation information. the syntax defined for the lagmib group is shown below. syntax defined in the lagmib group syntax definition lacpkey integer (1..127) note: although this is integer (0..65535) as per the standards, on this product it is in the range of integer (1..127) lacpstate bits * lacpactivity(0) * lacptimeout(1) * aggregation(2) * synchronization(3) * collecting(4) * distributing(5) * defaulted(6) * expired(7) churnstate integer * nochurn(1) * churn(2) * churnmonitor(3) the lagmib group is divided into subgroups such as those shown below. lagmib(43)     |     +--lagmibobjects(1)         |         +--dot3adagg(1)         |         +--dot3adaggport(2)         |         +--dot3adtableslastchanged(3) dot3adagg group mib name oid access syntax description dot3adaggtable 1.2.840.10006.300.43.1.1.1 n/a lacp information table for system dot3adaggentry 1.2.840.10006.300.43.1.1.1.1 n/a index * dot3adaggindex dot3adaggindex 1.2.840.10006.300.43.1.1.1.1.1 n/a interfaceindex lacp logical interface number dot3adaggmacaddress 1.2.840.10006.300.43.1.1.1.1.2 r/o macaddress mac address for lacp logical interface dot3adaggactorsystempriority 1.2.840.10006.300.43.1.1.1.1.3 r/nw integer (1..65535) note: although this is integer (0..65535) as per the standards, on this product it is in the range of integer (1..65535) same applies to other priority-related lagmib lacp system priority for this device dot3adaggactorsystemid 1.2.840.10006.300.43.1.1.1.1.4 r/nw macaddress lacp system id for the device itself dot3adaggaggregateorindividual 1.2.840.10006.300.43.1.1.1.1.5 r/o truthvalue whether operating as aggregate (true) or as individual links (alternate waiting ports) (false) dot3adaggactoradminkey 1.2.840.10006.300.43.1.1.1.1.6 r/nw lacpkey admin key (identifier id for the lacp logical interface) used in managing this device + “used in managing” means the setting values for admin properties or the config value. same applies to other lagmib dot3adaggactoroperkey 1.2.840.10006.300.43.1.1.1.1.7 r/o lacpkey admin key (identifier id for the lacp logical interface) used in operation, for this device + “used in operating” means the current values of the current operation, which are exchanged by the lacp protocol. same applies to other lagmib dot3adaggpartnersystemid 1.2.840.10006.300.43.1.1.1.1.8 r/o macaddress lacp system id of the opposing device dot3adaggpartnersystempriority 1.2.840.10006.300.43.1.1.1.1.9 r/o integer (1..65535) lacp system priority for the opposing device dot3adaggpartneroperkey 1.2.840.10006.300.43.1.1.1.1.10 r/o lacpkey admin key (identifier id for the lacp logical interface) used in operation, for the opposing device dot3adaggcollectormaxdelay 1.2.840.10006.300.43.1.1.1.1.11 r/nw integer (0..65535) delay time from when the lacp packet is received to the time it is reflected in operation dot3adaggportlisttable 1.2.840.10006.300.43.1.1.2 n/a lacp port list table for the system dot3adaggportlistentry 1.2.840.10006.300.43.1.1.2.1 n/a index * dot3adaggindex dot3adaggportlistports 1.2.840.10006.300.43.1.1.2.1.1 r/o portlist list of ports used by the lacp. shown as an interface (port) bitmap. bits are assigned in the following order starting from the most significant bit: port1.1 …​ port1.51, port1.52, port2.1 …​ port2.51, port2.52 for example, if port1.4 and port2.4 are used, the following value in hexadecimal will be indicated. 10 00 00 00 00 00 01 00 00 00 00 00 00 dot3adaggport group mib name oid access syntax description dot3adaggporttable 1.2.840.10006.300.43.1.2.1 n/a table of information for ports used by the lacp dot3adaggportentry 1.2.840.10006.300.43.1.2.1.1 n/a index * dot3adaggportindex dot3adaggportindex 1.2.840.10006.300.43.1.2.1.1.1 n/a interfaceindex port interface number dot3adaggportactorsystempriority 1.2.840.10006.300.43.1.2.1.1.2 r/nw integer (1..65535) lacp system priority for this device dot3adaggportactorsystemid 1.2.840.10006.300.43.1.2.1.1.3 r/o macaddress lacp system id for the device itself dot3adaggportactoradminkey 1.2.840.10006.300.43.1.2.1.1.4 r/nw lacpkey admin key (identifier id for the lacp logical interface) used in managing this device dot3adaggportactoroperkey 1.2.840.10006.300.43.1.2.1.1.5 r/nw lacpkey admin key (identifier id for the lacp logical interface) used in operation, for this device dot3adaggportpartneradminsystempriority 1.2.840.10006.300.43.1.2.1.1.6 r/nw integer (1..65535) lacp system priority used in management, for the opposing device dot3adaggportpartneropersystempriority 1.2.840.10006.300.43.1.2.1.1.7 r/o integer (1..65535) lacp system priority used in operation, for the opposing device dot3adaggportpartneradminsystemid 1.2.840.10006.300.43.1.2.1.1.8 r/nw macaddress lacp system id used in management, for the opposing device dot3adaggportpartneropersystemid 1.2.840.10006.300.43.1.2.1.1.9 r/o macaddress lacp system id used in operation, for the opposing device dot3adaggportpartneradminkey 1.2.840.10006.300.43.1.2.1.1.10 r/nw lacpkey admin key (identifier id for the lacp logical interface) used in management, for the opposing device dot3adaggportpartneroperkey 1.2.840.10006.300.43.1.2.1.1.11 r/o lacpkey admin key (identifier id for the lacp logical interface) used in operation, for the opposing device dot3adaggportselectedaggid 1.2.840.10006.300.43.1.2.1.1.12 r/o interfaceindex logical interface number selected by the port dot3adaggportattachedaggid 1.2.840.10006.300.43.1.2.1.1.13 r/o interfaceindex logical interface number connected to the port dot3adaggportactorport 1.2.840.10006.300.43.1.2.1.1.14 r/o integer (0..65535) physical interface number of this device dot3adaggportactorportpriority 1.2.840.10006.300.43.1.2.1.1.15 r/nw integer (0..65535) port priority for physical interface of this device dot3adaggportpartneradminport 1.2.840.10006.300.43.1.2.1.1.16 r/nw integer (0..65535) physical interface number used in management, for the opposing device dot3adaggportpartneroperport 1.2.840.10006.300.43.1.2.1.1.17 r/o integer (0..65535) physical interface number used in operation, for the opposing device dot3adaggportpartneradminportpriority 1.2.840.10006.300.43.1.2.1.1.18 r/nw integer (1..65535) port priority of physical interface used in management, for the opposing device dot3adaggportpartneroperportpriority 1.2.840.10006.300.43.1.2.1.1.19 r/o integer (1..65535) port priority for physical interface used in operation, for the opposing device dot3adaggportactoradminstate 1.2.840.10006.300.43.1.2.1.1.20 r/nw lacpstate actor_state used in management, for this device + actor_state is a status variable that shows internal transitions dot3adaggportactoroperstate 1.2.840.10006.300.43.1.2.1.1.21 r/o lacpstate actor_state used in operation, for this device dot3adaggportpartneradminstate 1.2.840.10006.300.43.1.2.1.1.22 r/nw lacpstate actor_state used in management, for the opposing device dot3adaggportpartneroperstate 1.2.840.10006.300.43.1.2.1.1.23 r/o lacpstate actor_state used in operation, for the opposing device dot3adaggportaggregateorindividual 1.2.840.10006.300.43.1.2.1.1.24 r/o truthvalue whether aggregate (true), or individual physical interfaces (alternate waiting ports) (false) dot3adaggportstatstable 1.2.840.10006.300.43.1.2.2 n/a table of statistical information for ports used by the lacp dot3adaggportstatsentry 1.2.840.10006.300.43.1.2.2.1 n/a index * dot3adaggportindex dot3adaggportstatslacpdusrx 1.2.840.10006.300.43.1.2.2.1.1 r/o counter32 no. of correct lacpdu received by the physical interface dot3adaggportstatsmarkerpdusrx 1.2.840.10006.300.43.1.2.2.1.2 r/o counter32 no. of correct marker frames received by the physical interface dot3adaggportstatsmarkerresponsepdusrx 1.2.840.10006.300.43.1.2.2.1.3 r/o counter32 no. of correct marker response frames received by the physical interface dot3adaggportstatsunknownrx 1.2.840.10006.300.43.1.2.2.1.4 r/o counter32 no. of unknown frames received by the physical interface dot3adaggportstatsillegalrx 1.2.840.10006.300.43.1.2.2.1.5 r/o counter32 no. of frames received by the physical interface on which the ethertype was 0x8809 but the pdu was invalid dot3adaggportstatslacpdustx 1.2.840.10006.300.43.1.2.2.1.6 r/o counter32 no. of lacpdu transmitted from physical interface dot3adaggportstatsmarkerpdustx 1.2.840.10006.300.43.1.2.2.1.7 r/o counter32 no. of marker frames transmitted from physical interface dot3adaggportstatsmarkerresponsepdustx 1.2.840.10006.300.43.1.2.2.1.8 r/o counter32 no. of marker response frames transmitted from physical interface dot3adaggportdebugtable 1.2.840.10006.300.43.1.2.3 n/a debug information table for ports used by the lacp dot3adaggportdebugentry 1.2.840.10006.300.43.1.2.3.1 n/a index * dot3adaggportindex dot3adaggportdebugrxstate 1.2.840.10006.300.43.1.2.3.1.1 r/o integer * current(1) * expired(2) * defaulted(3) * initialize(4) * lacpdisabled(5) * portdisabled(6) status of lacp protocol “receive machine” transition variable dot3adaggportdebuglastrxtime 1.2.840.10006.300.43.1.2.3.1.2 r/o timeticks internal time when logical interface last received data dot3adaggportdebugmuxstate 1.2.840.10006.300.43.1.2.3.1.3 r/o integer * detached(1) * waiting(2) * attached(3) * collecting(4) * distributing(5) * collecting_distributing(6) status of lacp protocol “mux machine” transition variable dot3adaggportdebugmuxreason 1.2.840.10006.300.43.1.2.3.1.4 r/o displaystring reason why most recent lacp protocol “mux machine” transition variable was changed dot3adaggportdebugactorchurnstate 1.2.840.10006.300.43.1.2.3.1.5 r/o churnstate status of “churn detection” transition variable for lacp protocol of this device dot3adaggportdebugpartnerchurnstate 1.2.840.10006.300.43.1.2.3.1.6 r/o churnstate status of lacp protocol “churn detection” transition variable for the opposing device dot3adaggportdebugactorchurncount 1.2.840.10006.300.43.1.2.3.1.7 r/o counter32 no. of times that the lacp protocol “churn detection” status variable changed to actor_churn status dot3adaggportdebugpartnerchurncount 1.2.840.10006.300.43.1.2.3.1.8 r/o counter32 no. of times that lacp protocol “churn detection” status variable changed to partner_churn status dot3adaggportdebugactorsynctransitioncount 1.2.840.10006.300.43.1.2.3.1.9 r/o counter32 no. of times that lacp protocol “mux machine” status variable of this device changed to in_sync status dot3adaggportdebugpartnersynctransitioncount 1.2.840.10006.300.43.1.2.3.1.10 r/o counter32 no. of times that the lacp protocol “mux machine” status variable of the opposing device changed to in_sync status dot3adaggportdebugactorchangecount 1.2.840.10006.300.43.1.2.3.1.11 r/o counter32 no. of times that the lag id of this device was changed dot3adaggportdebugpartnerchangecount 1.2.840.10006.300.43.1.2.3.1.12 r/o counter32 no. of times that the lag id of the opposing device was changed dot3adtableslastchanged group mib name oid access syntax description dot3adtableslastchanged 1.2.840.10006.300.43.1.3 r/o timeticks most recent time in which dot3adaggtable, dot3adaggportlisttable, or dot3adaggporttable was changed note: this is always “0” on this product</div><div class="display_word">4.3. lagMIB group This MIB is related to LACP link aggregation information. The syntax defined for the lagMIB group is shown below. Syntax defined in the lagMIB group Syntax Definition LacpKey INTEGER (1..127) Note: Although this is INTEGER (0..65535) as per the standards, on this product it is in the range of INTEGER (1..127) LacpState BITS * lacpActivity(0) * lacpTimeout(1) * aggregation(2) * synchronization(3) * collecting(4) * distributing(5) * defaulted(6) * expired(7) ChurnState INTEGER * noChurn(1) * churn(2) * churnMonitor(3) The lagMIB group is divided into subgroups such as those shown below. lagMIB(43)     |     +--lagMIBObjects(1)         |         +--dot3adAgg(1)         |         +--dot3adAggPort(2)         |         +--dot3adTablesLastChanged(3) dot3adAgg group MIB name OID Access Syntax Description dot3adAggTable 1.2.840.10006.300.43.1.1.1 N/A LACP information table for system dot3adAggEntry 1.2.840.10006.300.43.1.1.1.1 N/A INDEX * dot3adAggIndex dot3adAggIndex 1.2.840.10006.300.43.1.1.1.1.1 N/A InterfaceIndex LACP logical interface number dot3adAggMACAddress 1.2.840.10006.300.43.1.1.1.1.2 R/O MacAddress MAC address for LACP logical interface dot3adAggActorSystemPriority 1.2.840.10006.300.43.1.1.1.1.3 R/NW INTEGER (1..65535) Note: Although this is INTEGER (0..65535) as per the standards, on this product it is in the range of INTEGER (1..65535) Same applies to other priority-related lagMIB LACP system priority for this device dot3adAggActorSystemID 1.2.840.10006.300.43.1.1.1.1.4 R/NW MacAddress LACP system ID for the device itself dot3adAggAggregateOrIndividual 1.2.840.10006.300.43.1.1.1.1.5 R/O TruthValue Whether operating as Aggregate (true) or as individual links (alternate waiting ports) (false) dot3adAggActorAdminKey 1.2.840.10006.300.43.1.1.1.1.6 R/NW LacpKey ADMIN Key (identifier ID for the LACP logical interface) used in managing this device + “Used in managing” means the setting values for ADMIN properties or the config value. Same applies to other lagMIB dot3adAggActorOperKey 1.2.840.10006.300.43.1.1.1.1.7 R/O LacpKey ADMIN Key (identifier ID for the LACP logical interface) used in operation, for this device + “Used in operating” means the current values of the current operation, which are exchanged by the LACP protocol. Same applies to other lagMIB dot3adAggPartnerSystemID 1.2.840.10006.300.43.1.1.1.1.8 R/O MacAddress LACP system ID of the opposing device dot3adAggPartnerSystemPriority 1.2.840.10006.300.43.1.1.1.1.9 R/O INTEGER (1..65535) LACP system priority for the opposing device dot3adAggPartnerOperKey 1.2.840.10006.300.43.1.1.1.1.10 R/O LacpKey ADMIN Key (identifier ID for the LACP logical interface) used in operation, for the opposing device dot3adAggCollectorMaxDelay 1.2.840.10006.300.43.1.1.1.1.11 R/NW INTEGER (0..65535) Delay time from when the LACP packet is received to the time it is reflected in operation dot3adAggPortListTable 1.2.840.10006.300.43.1.1.2 N/A LACP port list table for the system dot3adAggPortListEntry 1.2.840.10006.300.43.1.1.2.1 N/A INDEX * dot3adAggIndex dot3adAggPortListPorts 1.2.840.10006.300.43.1.1.2.1.1 R/O PortList List of ports used by the LACP. Shown as an interface (port) bitmap. Bits are assigned in the following order starting from the most significant bit: port1.1 …​ port1.51, port1.52, port2.1 …​ port2.51, port2.52 For example, if port1.4 and port2.4 are used, the following value in hexadecimal will be indicated. 10 00 00 00 00 00 01 00 00 00 00 00 00 dot3adAggPort group MIB name OID Access Syntax Description dot3adAggPortTable 1.2.840.10006.300.43.1.2.1 N/A Table of information for ports used by the LACP dot3adAggPortEntry 1.2.840.10006.300.43.1.2.1.1 N/A INDEX * dot3adAggPortIndex dot3adAggPortIndex 1.2.840.10006.300.43.1.2.1.1.1 N/A InterfaceIndex Port interface number dot3adAggPortActorSystemPriority 1.2.840.10006.300.43.1.2.1.1.2 R/NW INTEGER (1..65535) LACP system priority for this device dot3adAggPortActorSystemID 1.2.840.10006.300.43.1.2.1.1.3 R/O MacAddress LACP system ID for the device itself dot3adAggPortActorAdminKey 1.2.840.10006.300.43.1.2.1.1.4 R/NW LacpKey ADMIN Key (identifier ID for the LACP logical interface) used in managing this device dot3adAggPortActorOperKey 1.2.840.10006.300.43.1.2.1.1.5 R/NW LacpKey ADMIN Key (identifier ID for the LACP logical interface) used in operation, for this device dot3adAggPortPartnerAdminSystemPriority 1.2.840.10006.300.43.1.2.1.1.6 R/NW INTEGER (1..65535) LACP system priority used in management, for the opposing device dot3adAggPortPartnerOperSystemPriority 1.2.840.10006.300.43.1.2.1.1.7 R/O INTEGER (1..65535) LACP system priority used in operation, for the opposing device dot3adAggPortPartnerAdminSystemID 1.2.840.10006.300.43.1.2.1.1.8 R/NW MacAddress LACP system ID used in management, for the opposing device dot3adAggPortPartnerOperSystemID 1.2.840.10006.300.43.1.2.1.1.9 R/O MacAddress LACP system ID used in operation, for the opposing device dot3adAggPortPartnerAdminKey 1.2.840.10006.300.43.1.2.1.1.10 R/NW LacpKey ADMIN Key (identifier ID for the LACP logical interface) used in management, for the opposing device dot3adAggPortPartnerOperKey 1.2.840.10006.300.43.1.2.1.1.11 R/O LacpKey ADMIN Key (identifier ID for the LACP logical interface) used in operation, for the opposing device dot3adAggPortSelectedAggID 1.2.840.10006.300.43.1.2.1.1.12 R/O InterfaceIndex Logical interface number selected by the port dot3adAggPortAttachedAggID 1.2.840.10006.300.43.1.2.1.1.13 R/O InterfaceIndex Logical interface number connected to the port dot3adAggPortActorPort 1.2.840.10006.300.43.1.2.1.1.14 R/O INTEGER (0..65535) Physical interface number of this device dot3adAggPortActorPortPriority 1.2.840.10006.300.43.1.2.1.1.15 R/NW INTEGER (0..65535) Port priority for physical interface of this device dot3adAggPortPartnerAdminPort 1.2.840.10006.300.43.1.2.1.1.16 R/NW INTEGER (0..65535) Physical interface number used in management, for the opposing device dot3adAggPortPartnerOperPort 1.2.840.10006.300.43.1.2.1.1.17 R/O INTEGER (0..65535) Physical interface number used in operation, for the opposing device dot3adAggPortPartnerAdminPortPriority 1.2.840.10006.300.43.1.2.1.1.18 R/NW INTEGER (1..65535) Port priority of physical interface used in management, for the opposing device dot3adAggPortPartnerOperPortPriority 1.2.840.10006.300.43.1.2.1.1.19 R/O INTEGER (1..65535) Port priority for physical interface used in operation, for the opposing device dot3adAggPortActorAdminState 1.2.840.10006.300.43.1.2.1.1.20 R/NW LacpState Actor_State used in management, for this device + Actor_State is a status variable that shows internal transitions dot3adAggPortActorOperState 1.2.840.10006.300.43.1.2.1.1.21 R/O LacpState Actor_State used in operation, for this device dot3adAggPortPartnerAdminState 1.2.840.10006.300.43.1.2.1.1.22 R/NW LacpState Actor_State used in management, for the opposing device dot3adAggPortPartnerOperState 1.2.840.10006.300.43.1.2.1.1.23 R/O LacpState Actor_State used in operation, for the opposing device dot3adAggPortAggregateOrIndividual 1.2.840.10006.300.43.1.2.1.1.24 R/O TruthValue Whether Aggregate (true), or individual physical interfaces (alternate waiting ports) (false) dot3adAggPortStatsTable 1.2.840.10006.300.43.1.2.2 N/A Table of statistical information for ports used by the LACP dot3adAggPortStatsEntry 1.2.840.10006.300.43.1.2.2.1 N/A INDEX * dot3adAggPortIndex dot3adAggPortStatsLACPDUsRx 1.2.840.10006.300.43.1.2.2.1.1 R/O Counter32 No. of correct LACPDU received by the physical interface dot3adAggPortStatsMarkerPDUsRx 1.2.840.10006.300.43.1.2.2.1.2 R/O Counter32 No. of correct marker frames received by the physical interface dot3adAggPortStatsMarkerResponsePDUsRx 1.2.840.10006.300.43.1.2.2.1.3 R/O Counter32 No. of correct marker response frames received by the physical interface dot3adAggPortStatsUnknownRx 1.2.840.10006.300.43.1.2.2.1.4 R/O Counter32 No. of unknown frames received by the physical interface dot3adAggPortStatsIllegalRx 1.2.840.10006.300.43.1.2.2.1.5 R/O Counter32 No. of frames received by the physical interface on which the EtherType was 0x8809 but the PDU was invalid dot3adAggPortStatsLACPDUsTx 1.2.840.10006.300.43.1.2.2.1.6 R/O Counter32 No. of LACPDU transmitted from physical interface dot3adAggPortStatsMarkerPDUsTx 1.2.840.10006.300.43.1.2.2.1.7 R/O Counter32 No. of marker frames transmitted from physical interface dot3adAggPortStatsMarkerResponsePDUsTx 1.2.840.10006.300.43.1.2.2.1.8 R/O Counter32 No. of marker response frames transmitted from physical interface dot3adAggPortDebugTable 1.2.840.10006.300.43.1.2.3 N/A Debug information table for ports used by the LACP dot3adAggPortDebugEntry 1.2.840.10006.300.43.1.2.3.1 N/A INDEX * dot3adAggPortIndex dot3adAggPortDebugRxState 1.2.840.10006.300.43.1.2.3.1.1 R/O INTEGER * current(1) * expired(2) * defaulted(3) * initialize(4) * lacpDisabled(5) * portDisabled(6) Status of LACP protocol “Receive machine” transition variable dot3adAggPortDebugLastRxTime 1.2.840.10006.300.43.1.2.3.1.2 R/O TimeTicks Internal time when logical interface last received data dot3adAggPortDebugMuxState 1.2.840.10006.300.43.1.2.3.1.3 R/O INTEGER * detached(1) * waiting(2) * attached(3) * collecting(4) * distributing(5) * collecting_distributing(6) Status of LACP protocol “Mux machine” transition variable dot3adAggPortDebugMuxReason 1.2.840.10006.300.43.1.2.3.1.4 R/O DisplayString Reason why most recent LACP protocol “Mux machine” transition variable was changed dot3adAggPortDebugActorChurnState 1.2.840.10006.300.43.1.2.3.1.5 R/O ChurnState Status of “Churn Detection” transition variable for LACP protocol of this device dot3adAggPortDebugPartnerChurnState 1.2.840.10006.300.43.1.2.3.1.6 R/O ChurnState Status of LACP protocol “Churn Detection” transition variable for the opposing device dot3adAggPortDebugActorChurnCount 1.2.840.10006.300.43.1.2.3.1.7 R/O Counter32 No. of times that the LACP protocol “Churn Detection” status variable changed to ACTOR_CHURN status dot3adAggPortDebugPartnerChurnCount 1.2.840.10006.300.43.1.2.3.1.8 R/O Counter32 No. of times that LACP protocol “Churn Detection” status variable changed to PARTNER_CHURN status dot3adAggPortDebugActorSyncTransitionCount 1.2.840.10006.300.43.1.2.3.1.9 R/O Counter32 No. of times that LACP protocol “Mux machine” status variable of this device changed to IN_SYNC status dot3adAggPortDebugPartnerSyncTransitionCount 1.2.840.10006.300.43.1.2.3.1.10 R/O Counter32 No. of times that the LACP protocol “Mux machine” status variable of the opposing device changed to IN_SYNC status dot3adAggPortDebugActorChangeCount 1.2.840.10006.300.43.1.2.3.1.11 R/O Counter32 No. of times that the LAG ID of this device was changed dot3adAggPortDebugPartnerChangeCount 1.2.840.10006.300.43.1.2.3.1.12 R/O Counter32 No. of times that the LAG ID of the opposing device was changed dot3adTablesLastChanged group MIB name OID Access Syntax Description dot3adTablesLastChanged 1.2.840.10006.300.43.1.3 R/O TimeTicks Most recent time in which Dot3adAggTable, dot3adAggPortListTable, or dot3adAggPortTable was changed Note: This is always “0” on this product</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#systemグループ">4.4. system group</div><div class="search_word">4.4. system group this mib is related to system information. system group mib name oid access syntax description sysdescr 1.3.6.1.2.1.1.1 r/o displaystring (size (0..255)) the description of the device. device name and firmware revision sysobjectid 1.3.6.1.2.1.1.2 r/o object identifier device oid that is defined by yamaha’s private mib sysuptimeinstance 1.3.6.1.2.1.1.3 r/o timeticks elapsed time from boot syscontact 1.3.6.1.2.1.1.4 r/w displaystring (size (0..255)) administrator contact information setting value for snmp-server contact command sysname 1.3.6.1.2.1.1.5 r/w displaystring (size (0..255)) administrative name setting value for hostname command syslocation 1.3.6.1.2.1.1.6 r/w displaystring (size (0..255)) device location setting value for snmp-server location command sysservices 1.3.6.1.2.1.1.7 r/o integer (0..127) value that indicates services the device supports</div><div class="display_word">4.4. system group This MIB is related to system information. system group MIB name OID Access Syntax Description sysDescr 1.3.6.1.2.1.1.1 R/O DisplayString (SIZE (0..255)) The description of the device. Device name and firmware revision sysObjectID 1.3.6.1.2.1.1.2 R/O OBJECT IDENTIFIER Device OID that is defined by Yamaha’s private MIB sysUpTimeInstance 1.3.6.1.2.1.1.3 R/O TimeTicks Elapsed time from boot sysContact 1.3.6.1.2.1.1.4 R/W DisplayString (SIZE (0..255)) Administrator contact information Setting value for snmp-server contact command sysName 1.3.6.1.2.1.1.5 R/W DisplayString (SIZE (0..255)) Administrative name Setting value for hostname command sysLocation 1.3.6.1.2.1.1.6 R/W DisplayString (SIZE (0..255)) Device location Setting value for snmp-server location command sysServices 1.3.6.1.2.1.1.7 R/O INTEGER (0..127) Value that indicates services the device supports</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#interfaceグループ">4.5. interface group</div><div class="search_word">4.5. interface group this mib is related to interface information. interface group mib name oid access syntax description ifnumber 1.3.6.1.2.1.2.1 r/o integer32 no. of interfaces iftable 1.3.6.1.2.1.2.2 n/a table of interface information counters with a vlan ifindex value count the total traffic of all physical ports associated to the vlan ifentry 1.3.6.1.2.1.2.2.1 n/a index * ifindex ifindex 1.3.6.1.2.1.2.2.1.1 r/o interfaceindex interface id number ifdescr 1.3.6.1.2.1.2.2.1.2 r/o displaystring (size (0..255)) description of the interface. interface name iftype 1.3.6.1.2.1.2.2.1.3 r/o ianaiftype * ethernetcsmacd(6) * l3ipvlan(136), etc. types of interfaces ifmtu 1.3.6.1.2.1.2.2.1.4 r/o integer32 maximum frame size that can be transmitted/received ifspeed 1.3.6.1.2.1.2.2.1.5 r/o gauge32 interface speed ifphysaddress 1.3.6.1.2.1.2.2.1.6 r/o physaddress mac address ifadminstatus 1.3.6.1.2.1.2.2.1.7 r/w integer * up(1) * down(2) desirable interface status ifoperstatus 1.3.6.1.2.1.2.2.1.8 r/o integer * up(1) * down(2) current status of interface iflastchange 1.3.6.1.2.1.2.2.1.9 r/o timeticks time when the interface changed to the current status (elapsed time from boot) ifinoctets 1.3.6.1.2.1.2.2.1.10 r/o counter32 total no. of octets received ifinucastpkts 1.3.6.1.2.1.2.2.1.11 r/o counter32 no. of unicast packets notified to higher protocol ifinnucastpkts 1.3.6.1.2.1.2.2.1.12 r/o counter32 number of non-unicast packets notified to higher protocol ifindiscards 1.3.6.1.2.1.2.2.1.13 r/o counter32 no. of packets that were discarded, despite no errors detected ifinerrors 1.3.6.1.2.1.2.2.1.14 r/o counter32 no. of packets not notified to higher protocol due to errors ifinunknownprotos 1.3.6.1.2.1.2.2.1.15 r/o counter32 no. of discarded packets, due to an unsupported protocol ifoutoctets 1.3.6.1.2.1.2.2.1.16 r/o counter32 total no. of octets transmitted ifoutucastpkts 1.3.6.1.2.1.2.2.1.17 r/o counter32 no. of unicast packets requested for transmission by a higher protocol ifoutnucastpkts 1.3.6.1.2.1.2.2.1.18 r/o counter32 no. of non-unicast packets requested for transmission by a higher protocol ifoutdiscards 1.3.6.1.2.1.2.2.1.19 r/o counter32 no. of packets that were discarded for transmission, despite no errors detected ifouterrors 1.3.6.1.2.1.2.2.1.20 r/o counter32 no. of packets not transmitted due to errors ifspecific 1.3.6.1.2.1.2.2.1.22 r/o object identifier reference to mib that defines interface media characteristics + if no reference exists, this will be 0.0</div><div class="display_word">4.5. interface group This MIB is related to interface information. interface group MIB name OID Access Syntax Description ifNumber 1.3.6.1.2.1.2.1 R/O Integer32 No. of interfaces ifTable 1.3.6.1.2.1.2.2 N/A Table of interface information Counters with a VLAN ifIndex value count the total traffic of all physical ports associated to the VLAN ifEntry 1.3.6.1.2.1.2.2.1 N/A INDEX * ifIndex ifIndex 1.3.6.1.2.1.2.2.1.1 R/O InterfaceIndex Interface ID number ifDescr 1.3.6.1.2.1.2.2.1.2 R/O DisplayString (SIZE (0..255)) Description of the interface. Interface name ifType 1.3.6.1.2.1.2.2.1.3 R/O IANAifType * ethernetCsmacd(6) * l3ipvlan(136), etc. Types of interfaces ifMtu 1.3.6.1.2.1.2.2.1.4 R/O Integer32 Maximum frame size that can be transmitted/received ifSpeed 1.3.6.1.2.1.2.2.1.5 R/O Gauge32 Interface speed ifPhysAddress 1.3.6.1.2.1.2.2.1.6 R/O PhysAddress MAC address ifAdminStatus 1.3.6.1.2.1.2.2.1.7 R/W INTEGER * up(1) * down(2) Desirable interface status ifOperStatus 1.3.6.1.2.1.2.2.1.8 R/O INTEGER * up(1) * down(2) Current status of interface ifLastChange 1.3.6.1.2.1.2.2.1.9 R/O TimeTicks Time when the interface changed to the current status (elapsed time from boot) ifInOctets 1.3.6.1.2.1.2.2.1.10 R/O Counter32 Total no. of octets received ifInUcastPkts 1.3.6.1.2.1.2.2.1.11 R/O Counter32 No. of unicast packets notified to higher protocol ifInNUcastPkts 1.3.6.1.2.1.2.2.1.12 R/O Counter32 Number of non-unicast packets notified to higher protocol ifInDiscards 1.3.6.1.2.1.2.2.1.13 R/O Counter32 No. of packets that were discarded, despite no errors detected ifInErrors 1.3.6.1.2.1.2.2.1.14 R/O Counter32 No. of packets not notified to higher protocol due to errors ifInUnknownProtos 1.3.6.1.2.1.2.2.1.15 R/O Counter32 No. of discarded packets, due to an unsupported protocol ifOutOctets 1.3.6.1.2.1.2.2.1.16 R/O Counter32 Total no. of octets transmitted ifOutUcastPkts 1.3.6.1.2.1.2.2.1.17 R/O Counter32 No. of unicast packets requested for transmission by a higher protocol ifOutNUcastPkts 1.3.6.1.2.1.2.2.1.18 R/O Counter32 No. of non-unicast packets requested for transmission by a higher protocol ifOutDiscards 1.3.6.1.2.1.2.2.1.19 R/O Counter32 No. of packets that were discarded for transmission, despite no errors detected ifOutErrors 1.3.6.1.2.1.2.2.1.20 R/O Counter32 No. of packets not transmitted due to errors ifSpecific 1.3.6.1.2.1.2.2.1.22 R/O OBJECT IDENTIFIER Reference to MIB that defines interface media characteristics + If no reference exists, this will be 0.0</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#atグループ">4.6. at group</div><div class="search_word">4.6. at group this mib is related to mapping information for physical addresses and network addresses. at group mib name oid access syntax description attable 1.3.6.1.2.1.3.1 n/a table of mapping information for physical addresses and network addresses atentry 1.3.6.1.2.1.3.1.1 n/a index * atifindex * atnetaddress atifindex 1.3.6.1.2.1.3.1.1.1 r/nw integer ifindex for the corresponding interface atphysaddress 1.3.6.1.2.1.3.1.1.2 r/nw physaddress physical address atnetaddress 1.3.6.1.2.1.3.1.1.3 r/nw networkaddress ip address corresponding to the physical address</div><div class="display_word">4.6. at group This MIB is related to mapping information for physical addresses and network addresses. at group MIB name OID Access Syntax Description atTable 1.3.6.1.2.1.3.1 N/A Table of mapping information for physical addresses and network addresses atEntry 1.3.6.1.2.1.3.1.1 N/A INDEX * atIfIndex * atNetAddress atIfIndex 1.3.6.1.2.1.3.1.1.1 R/NW INTEGER ifIndex for the corresponding interface atPhysAddress 1.3.6.1.2.1.3.1.1.2 R/NW PhysAddress Physical address atNetAddress 1.3.6.1.2.1.3.1.1.3 R/NW NetworkAddress IP address corresponding to the physical address</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#rmonグループ">4.7. rmon group</div><div class="search_word">4.7. rmon group this mib is related to rmon information. the syntax defined for the rmon group is shown below. syntax defined in the rmon group syntax definition ownerstring octet string (size (0..127)) entrystatus integer * valid(1) * createrequest(2) * undercreation(3) * invalid(4) the rmon group is divided into subgroups such as those shown below. rmon(16)      |      +--statistics(1)      |      +--history(2)      |      +--alarm(3)      |      +--event(9) statistics group mib name oid access syntax description etherstatstable 1.3.6.1.2.1.16.1.1 n/a table of statistical information for ethernet etherstatsentry 1.3.6.1.2.1.16.1.1.1 n/a index * etherstatsindex etherstatsindex 1.3.6.1.2.1.16.1.1.1.1 r/o integer32 (1..65535) index of entries etherstatsdatasource 1.3.6.1.2.1.16.1.1.1.2 r/c object identifier interface being monitored etherstatsdropevents 1.3.6.1.2.1.16.1.1.1.3 r/o counter32 number of drop packets etherstatsoctets 1.3.6.1.2.1.16.1.1.1.4 r/o counter32 number of octets received etherstatspkts 1.3.6.1.2.1.16.1.1.1.5 r/o counter32 number of received packets etherstatsbroadcastpkts 1.3.6.1.2.1.16.1.1.1.6 r/o counter32 number of broadcast packets received etherstatsmulticastpkts 1.3.6.1.2.1.16.1.1.1.7 r/o counter32 number of multicast packets received etherstatscrcalignerrors 1.3.6.1.2.1.16.1.1.1.8 r/o counter32 number of fcs error packets received etherstatsundersizepkts 1.3.6.1.2.1.16.1.1.1.9 r/o counter32 number of undersize packets received (packets smaller than 64 octets) etherstatsoversizepkts 1.3.6.1.2.1.16.1.1.1.10 r/o counter32 number of oversize packets received (packets larger than 1518 octets) etherstatsfragments 1.3.6.1.2.1.16.1.1.1.11 r/o counter32 number of fragment packets received (packets smaller than 64 octets with abnormal fcs) etherstatsjabbers 1.3.6.1.2.1.16.1.1.1.12 r/o counter32 number of jabber packets received (packets larger than 1518 octets with abnormal fcs) etherstatscollisions 1.3.6.1.2.1.16.1.1.1.13 r/o counter32 number of collisions etherstatsowner 1.3.6.1.2.1.16.1.1.1.20 r/c ownerstring owner name etherstatsstatus 1.3.6.1.2.1.16.1.1.1.21 r/c entrystatus status of statistical group history group mib name oid access syntax description historycontroltable 1.3.6.1.2.1.16.2.1 n/a table of control information for the history group historycontrolentry 1.3.6.1.2.1.16.2.1.1 n/a index * historycontrolindex historycontrolindex 1.3.6.1.2.1.16.2.1.1.1 r/o integer32 (1..65535) index of entries historycontroldatasource 1.3.6.1.2.1.16.2.1.1.2 r/c object identifier interface being monitored historycontrolbucketsrequested 1.3.6.1.2.1.16.2.1.1.3 r/c integer32 (1..65535) number of history group history saves requested historycontrolbucketsgranted 1.3.6.1.2.1.16.2.1.1.4 r/o integer32 (1..65535) number of history group histories saved historycontrolinterval 1.3.6.1.2.1.16.2.1.1.5 r/c integer32 (1..3600) interval at which history group histories are saved historycontrolowner 1.3.6.1.2.1.16.2.1.1.6 r/c ownerstring owner name historycontrolstatus 1.3.6.1.2.1.16.2.1.1.7 r/c entrystatus history group status etherhistorytable 1.3.6.1.2.1.16.2.2 n/a table of history information etherhistoryentry 1.3.6.1.2.1.16.2.2.1 n/a index * etherhistoryindex * etherhistorysampleindex etherhistoryindex 1.3.6.1.2.1.16.2.2.1.1 r/o integer32 (1..65535) same value as the index value of historycontrolindex etherhistorysampleindex 1.3.6.1.2.1.16.2.2.1.2 r/o integer32 (1..2147483647) index of history entries etherhistoryintervalstart 1.3.6.1.2.1.16.2.2.1.3 r/o timeticks interval at which history group histories are saved etherhistorydropevents 1.3.6.1.2.1.16.2.2.1.4 r/o counter32 number of drop packets etherhistoryoctets 1.3.6.1.2.1.16.2.2.1.5 r/o counter32 number of octets received etherhistorypkts 1.3.6.1.2.1.16.2.2.1.6 r/o counter32 number of received packets etherhistorybroadcastpkts 1.3.6.1.2.1.16.2.2.1.7 r/o counter32 number of broadcast packets received etherhistorymulticastpkts 1.3.6.1.2.1.16.2.2.1.8 r/o counter32 number of multicast packets received etherhistorycrcalignerrors 1.3.6.1.2.1.16.2.2.1.9 r/o counter32 number of fcs error packets received etherhistoryundersizepkts 1.3.6.1.2.1.16.2.2.1.10 r/o counter32 number of undersize packets received (packets smaller than 64 octets) etherhistoryoversizepkts 1.3.6.1.2.1.16.2.2.1.11 r/o counter32 number of oversize packets received (packets larger than 1518 octets) etherhistoryfragments 1.3.6.1.2.1.16.2.2.1.12 r/o counter32 number of fragment packets received (packets smaller than 64 octets with abnormal fcs) etherhistoryjabbers 1.3.6.1.2.1.16.2.2.1.13 r/o counter32 number of jabber packets received (packets larger than 1518 octets with abnormal fcs) etherhistorycollisions 1.3.6.1.2.1.16.2.2.1.14 r/o counter32 number of collisions etherhistoryutilization 1.3.6.1.2.1.16.2.2.1.15 r/o integer32 (0..10000) estimated value of network usage ratio alarm group mib name oid access syntax description alarmtable 1.3.6.1.2.1.16.3.1 n/a table of information for the alarm group alarmentry 1.3.6.1.2.1.16.3.1.1 n/a index * alarmindex alarmindex 1.3.6.1.2.1.16.3.1.1.1 r/o integer32 (1..65535) index of entries alarminterval 1.3.6.1.2.1.16.3.1.1.2 r/c integer32 sampling interval alarmvariable 1.3.6.1.2.1.16.3.1.1.3 r/c object identifier mib object to be monitored alarmsampletype 1.3.6.1.2.1.16.3.1.1.4 r/c integer * absolutevalue(1) * deltavalue(2) sampling type alarmvalue 1.3.6.1.2.1.16.3.1.1.5 r/o integer32 estimated value alarmstartupalarm 1.3.6.1.2.1.16.3.1.1.6 r/c integer * risingalarm(1) * fallingalarm(2) * risingorfallingalarm(3) threshold value used for first alarm determination alarmrisingthreshold 1.3.6.1.2.1.16.3.1.1.7 r/c integer32 upper threshold value alarmfallingthreshold 1.3.6.1.2.1.16.3.1.1.8 r/c integer32 lower threshold value alarmrisingeventindex 1.3.6.1.2.1.16.3.1.1.9 r/c integer32 (0..65535) event index when crossing upper limit alarmfallingeventindex 1.3.6.1.2.1.16.3.1.1.10 r/c integer32 (0..65535) event index when crossing lower limit alarmowner 1.3.6.1.2.1.16.3.1.1.11 r/c ownerstring owner name alarmstatus 1.3.6.1.2.1.16.3.1.1.12 r/c entrystatus alarm group status event group mib name oid access syntax description eventtable 1.3.6.1.2.1.16.9.1 n/a table of information for event group evententry 1.3.6.1.2.1.16.9.1.1 n/a index * eventindex eventindex 1.3.6.1.2.1.16.9.1.1.1 r/o integer32 (1..65535) index of entries eventdescription 1.3.6.1.2.1.16.9.1.1.2 r/c displaystring (size (0..127)) event description eventtype 1.3.6.1.2.1.16.9.1.1.3 r/c integer * none(1) * log(2) * snmptrap(3) * logandtrap(4) event type eventcommunity 1.3.6.1.2.1.16.9.1.1.4 r/c octet string (size (0..127)) community name eventlasttimesent 1.3.6.1.2.1.16.9.1.1.5 r/o timeticks event execution time eventowner 1.3.6.1.2.1.16.9.1.1.6 r/c ownerstring owner name eventstatus 1.3.6.1.2.1.16.9.1.1.7 r/c entrystatus event group status</div><div class="display_word">4.7. rmon group This MIB is related to RMON information. The syntax defined for the rmon group is shown below. Syntax defined in the rmon group Syntax Definition OwnerString OCTET STRING (SIZE (0..127)) EntryStatus INTEGER * valid(1) * createRequest(2) * underCreation(3) * invalid(4) The rmon group is divided into subgroups such as those shown below. rmon(16)      |      +--statistics(1)      |      +--history(2)      |      +--alarm(3)      |      +--event(9) statistics group MIB name OID Access Syntax Description etherStatsTable 1.3.6.1.2.1.16.1.1 N/A Table of statistical information for Ethernet etherStatsEntry 1.3.6.1.2.1.16.1.1.1 N/A INDEX * etherStatsIndex etherStatsIndex 1.3.6.1.2.1.16.1.1.1.1 R/O Integer32 (1..65535) Index of entries etherStatsDataSource 1.3.6.1.2.1.16.1.1.1.2 R/C OBJECT IDENTIFIER Interface being monitored etherStatsDropEvents 1.3.6.1.2.1.16.1.1.1.3 R/O Counter32 Number of drop packets etherStatsOctets 1.3.6.1.2.1.16.1.1.1.4 R/O Counter32 Number of octets received etherStatsPkts 1.3.6.1.2.1.16.1.1.1.5 R/O Counter32 Number of received packets etherStatsBroadcastPkts 1.3.6.1.2.1.16.1.1.1.6 R/O Counter32 Number of broadcast packets received etherStatsMulticastPkts 1.3.6.1.2.1.16.1.1.1.7 R/O Counter32 Number of multicast packets received etherStatsCRCAlignErrors 1.3.6.1.2.1.16.1.1.1.8 R/O Counter32 Number of FCS error packets received etherStatsUndersizePkts 1.3.6.1.2.1.16.1.1.1.9 R/O Counter32 Number of undersize packets received (packets smaller than 64 octets) etherStatsOversizePkts 1.3.6.1.2.1.16.1.1.1.10 R/O Counter32 Number of oversize packets received (packets larger than 1518 octets) etherStatsFragments 1.3.6.1.2.1.16.1.1.1.11 R/O Counter32 Number of fragment packets received (packets smaller than 64 octets with abnormal FCS) etherStatsJabbers 1.3.6.1.2.1.16.1.1.1.12 R/O Counter32 Number of jabber packets received (packets larger than 1518 octets with abnormal FCS) etherStatsCollisions 1.3.6.1.2.1.16.1.1.1.13 R/O Counter32 Number of collisions etherStatsOwner 1.3.6.1.2.1.16.1.1.1.20 R/C OwnerString Owner name etherStatsStatus 1.3.6.1.2.1.16.1.1.1.21 R/C EntryStatus Status of statistical group history group MIB name OID Access Syntax Description historyControlTable 1.3.6.1.2.1.16.2.1 N/A Table of control information for the history group historyControlEntry 1.3.6.1.2.1.16.2.1.1 N/A INDEX * historyControlIndex historyControlIndex 1.3.6.1.2.1.16.2.1.1.1 R/O Integer32 (1..65535) Index of entries historyControlDataSource 1.3.6.1.2.1.16.2.1.1.2 R/C OBJECT IDENTIFIER Interface being monitored historyControlBucketsRequested 1.3.6.1.2.1.16.2.1.1.3 R/C Integer32 (1..65535) Number of history group history saves requested historyControlBucketsGranted 1.3.6.1.2.1.16.2.1.1.4 R/O Integer32 (1..65535) Number of history group histories saved historyControlInterval 1.3.6.1.2.1.16.2.1.1.5 R/C Integer32 (1..3600) Interval at which history group histories are saved historyControlOwner 1.3.6.1.2.1.16.2.1.1.6 R/C OwnerString Owner name historyControlStatus 1.3.6.1.2.1.16.2.1.1.7 R/C EntryStatus History group status etherHistoryTable 1.3.6.1.2.1.16.2.2 N/A Table of history information etherHistoryEntry 1.3.6.1.2.1.16.2.2.1 N/A INDEX * etherHistoryIndex * etherHistorySampleIndex etherHistoryIndex 1.3.6.1.2.1.16.2.2.1.1 R/O Integer32 (1..65535) Same value as the index value of historyControlIndex etherHistorySampleIndex 1.3.6.1.2.1.16.2.2.1.2 R/O Integer32 (1..2147483647) Index of history entries etherHistoryIntervalStart 1.3.6.1.2.1.16.2.2.1.3 R/O TimeTicks Interval at which history group histories are saved etherHistoryDropEvents 1.3.6.1.2.1.16.2.2.1.4 R/O Counter32 Number of drop packets etherHistoryOctets 1.3.6.1.2.1.16.2.2.1.5 R/O Counter32 Number of octets received etherHistoryPkts 1.3.6.1.2.1.16.2.2.1.6 R/O Counter32 Number of received packets etherHistoryBroadcastPkts 1.3.6.1.2.1.16.2.2.1.7 R/O Counter32 Number of broadcast packets received etherHistoryMulticastPkts 1.3.6.1.2.1.16.2.2.1.8 R/O Counter32 Number of multicast packets received etherHistoryCRCAlignErrors 1.3.6.1.2.1.16.2.2.1.9 R/O Counter32 Number of FCS error packets received etherHistoryUndersizePkts 1.3.6.1.2.1.16.2.2.1.10 R/O Counter32 Number of undersize packets received (packets smaller than 64 octets) etherHistoryOversizePkts 1.3.6.1.2.1.16.2.2.1.11 R/O Counter32 Number of oversize packets received (packets larger than 1518 octets) etherHistoryFragments 1.3.6.1.2.1.16.2.2.1.12 R/O Counter32 Number of fragment packets received (packets smaller than 64 octets with abnormal FCS) etherHistoryJabbers 1.3.6.1.2.1.16.2.2.1.13 R/O Counter32 Number of jabber packets received (packets larger than 1518 octets with abnormal FCS) etherHistoryCollisions 1.3.6.1.2.1.16.2.2.1.14 R/O Counter32 Number of collisions etherHistoryUtilization 1.3.6.1.2.1.16.2.2.1.15 R/O Integer32 (0..10000) Estimated value of network usage ratio alarm group MIB name OID Access Syntax Description alarmTable 1.3.6.1.2.1.16.3.1 N/A Table of information for the alarm group alarmEntry 1.3.6.1.2.1.16.3.1.1 N/A INDEX * alarmIndex alarmIndex 1.3.6.1.2.1.16.3.1.1.1 R/O Integer32 (1..65535) Index of entries alarmInterval 1.3.6.1.2.1.16.3.1.1.2 R/C Integer32 Sampling interval alarmVariable 1.3.6.1.2.1.16.3.1.1.3 R/C OBJECT IDENTIFIER MIB object to be monitored alarmSampleType 1.3.6.1.2.1.16.3.1.1.4 R/C INTEGER * absoluteValue(1) * deltaValue(2) Sampling type alarmValue 1.3.6.1.2.1.16.3.1.1.5 R/O Integer32 Estimated value alarmStartupAlarm 1.3.6.1.2.1.16.3.1.1.6 R/C INTEGER * risingAlarm(1) * fallingAlarm(2) * risingOrFallingAlarm(3) Threshold value used for first alarm determination alarmRisingThreshold 1.3.6.1.2.1.16.3.1.1.7 R/C Integer32 Upper threshold value alarmFallingThreshold 1.3.6.1.2.1.16.3.1.1.8 R/C Integer32 Lower threshold value alarmRisingEventIndex 1.3.6.1.2.1.16.3.1.1.9 R/C Integer32 (0..65535) Event index when crossing upper limit alarmFallingEventIndex 1.3.6.1.2.1.16.3.1.1.10 R/C Integer32 (0..65535) Event index when crossing lower limit alarmOwner 1.3.6.1.2.1.16.3.1.1.11 R/C OwnerString Owner name alarmStatus 1.3.6.1.2.1.16.3.1.1.12 R/C EntryStatus Alarm group status event group MIB name OID Access Syntax Description eventTable 1.3.6.1.2.1.16.9.1 N/A Table of information for event group eventEntry 1.3.6.1.2.1.16.9.1.1 N/A INDEX * eventIndex eventIndex 1.3.6.1.2.1.16.9.1.1.1 R/O Integer32 (1..65535) Index of entries eventDescription 1.3.6.1.2.1.16.9.1.1.2 R/C DisplayString (SIZE (0..127)) Event description eventType 1.3.6.1.2.1.16.9.1.1.3 R/C INTEGER * none(1) * log(2) * snmptrap(3) * logandtrap(4) Event type eventCommunity 1.3.6.1.2.1.16.9.1.1.4 R/C OCTET STRING (SIZE (0..127)) Community name eventLastTimeSent 1.3.6.1.2.1.16.9.1.1.5 R/O TimeTicks Event execution time eventOwner 1.3.6.1.2.1.16.9.1.1.6 R/C OwnerString Owner name eventStatus 1.3.6.1.2.1.16.9.1.1.7 R/C EntryStatus Event group status</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#dot1dbridgeグループ">4.8. dot1dBridge group</div><div class="search_word">4.8. dot1dbridge group this mib is related to dot1dbridge information. the syntax defined in the dot1dbridge group is shown below. syntax defined in the dot1dbridge group syntax definition bridgeid octet string (size (8)) timeout integer32 portlist octet string vlanindex unsigned32 vlanid integer32 (1..4094) the dot1dbridge group is divided into subgroups such as those shown below. dot1dbridge(17)      |      +--dot1dbase(1)      |      +--dot1dstp(2)      |      +--dot1dtp(4)      |      +--dot1dstatic(5)      |      +--qbridgemib(7)         |         +--qbridgemibobjects(1)            |            +--dot1qbase(1)            |            +--dot1qtp(2)            |            +--dot1qvlan(4) dot1dbase group mib name oid access syntax description dot1dbasebridgeaddress 1.3.6.1.2.1.17.1.1 r/o macaddress mac address of bridge dot1dbasenumports 1.3.6.1.2.1.17.1.2 r/o integer32 no. of ports for bridge dot1dbasetype 1.3.6.1.2.1.17.1.3 r/o integer * unknown(1) * transparent-only(2) * sourceroute-only(3) * srt(4) type of bridging executable by the bridge dot1dbaseporttable 1.3.6.1.2.1.17.1.4 n/a table of port information for bridge dot1dbaseportentry 1.3.6.1.2.1.17.1.4.1 n/a index * dot1dbaseport dot1dbaseport 1.3.6.1.2.1.17.1.4.1.1 r/o integer32 (1..65535) port number dot1dbaseportifindex 1.3.6.1.2.1.17.1.4.1.2 r/o interfaceindex instance value for ifindex, defined by the if-mib of the interface corresponding to the port dot1dbaseportcircuit 1.3.6.1.2.1.17.1.4.1.3 r/o object identifier identifier used when the value of dot1dbaseportifindex is the same port in the bridge dot1dbaseportdelayexceededdiscards 1.3.6.1.2.1.17.1.4.1.4 r/o counter32 no. of frames discarded at the port due to a bridge forwarding delay note: this is always “0” on this product dot1dbaseportmtuexceededdiscards 1.3.6.1.2.1.17.1.4.1.5 r/o counter32 no. of frames discarded at the port due to excessive size note: this is always “0” on this product dot1dstp group mib name oid access syntax description dot1dstpprotocolspecification 1.3.6.1.2.1.17.2.1 r/o integer * unknown(1) * declb100(2) * ieee8021d(3) spanning tree protocol version dot1dstppriority 1.3.6.1.2.1.17.2.2 r/nw integer32 (0..65535) bridge priority value dot1dstptimesincetopologychange 1.3.6.1.2.1.17.2.3 r/o timeticks time elapsed since detecting a change in topology dot1dstptopchanges 1.3.6.1.2.1.17.2.4 r/o counter32 no. of times a change in topology has been detected dot1dstpdesignatedroot 1.3.6.1.2.1.17.2.5 r/o bridgeid root bridge identifier of spanning tree dot1dstprootcost 1.3.6.1.2.1.17.2.6 r/o integer32 path cost to root bridge dot1dstprootport 1.3.6.1.2.1.17.2.7 r/o integer32 port number with the lowest cost from bridge to root bridge dot1dstpmaxage 1.3.6.1.2.1.17.2.8 r/o timeout maximum time elapsed for spanning tree protocol information (in units of 1/100 sec.) dot1dstphellotime 1.3.6.1.2.1.17.2.9 r/o timeout bpdu transmission interval (in units of 1/100 sec.) dot1dstpholdtime 1.3.6.1.2.1.17.2.10 r/o integer32 minimum transmission interval for configuration bpdu (in units of 1/100 sec.) dot1dstpforwarddelay 1.3.6.1.2.1.17.2.11 r/o timeout forward delay time (in units of 1/100 sec.) dot1dstpbridgemaxage 1.3.6.1.2.1.17.2.12 r/nw timeout (600..4000) setting value for maximum elapsed time dot1dstpbridgehellotime 1.3.6.1.2.1.17.2.13 r/nw timeout (100..1000) setting value for bpdu transmission interval dot1dstpbridgeforwarddelay 1.3.6.1.2.1.17.2.14 r/nw timeout (400..3000) setting value for forward delay time dot1dstpporttable 1.3.6.1.2.1.17.2.15 n/a table of port information for spanning tree protocol dot1dstpportentry 1.3.6.1.2.1.17.2.15.1 n/a index * dot1dstpport dot1dstpport 1.3.6.1.2.1.17.2.15.1.1 r/o integer32 (1..65535) port number for spanning tree protocol dot1dstpportpriority 1.3.6.1.2.1.17.2.15.1.2 r/nw integer32 (0..255) port priority value dot1dstpportstate 1.3.6.1.2.1.17.2.15.1.3 r/o integer * disabled(1) * blocking(2) * listening(3) * learning(4) * forwarding(5) * broken(6) port status dot1dstpportenable 1.3.6.1.2.1.17.2.15.1.4 r/nw integer * enabled(1) * disabled(2) port enabled/disabled status dot1dstpportpathcost 1.3.6.1.2.1.17.2.15.1.5 r/nw integer32 (1..65535) path cost value for port dot1dstpportdesignatedroot 1.3.6.1.2.1.17.2.15.1.6 r/o bridgeid root bridge identifier of configuration bpdu dot1dstpportdesignatedcost 1.3.6.1.2.1.17.2.15.1.7 r/o integer32 path cost value for specified port dot1dstpportdesignatedbridge 1.3.6.1.2.1.17.2.15.1.8 r/o bridgeid specified bridge identifier dot1dstpportdesignatedport 1.3.6.1.2.1.17.2.15.1.9 r/o octet string (size (2)) port identifier for specified bridge dot1dstpportforwardtransitions 1.3.6.1.2.1.17.2.15.1.10 r/o counter32 no. of times that port switched from acquisition status to forwarding status dot1dstpportpathcost32 1.3.6.1.2.1.17.2.15.1.11 r/nw integer32 (1..200000000) path cost value for ports complying with ieee 802.1t dot1dstpversion 1.3.6.1.2.1.17.2.16 r/nw integer * stpcompatible(0) * rstp(2) spanning tree protocol version dot1dstptxholdcount 1.3.6.1.2.1.17.2.17 r/nw integer32 (1..10) forward hold count value dot1dstpextporttable 1.3.6.1.2.1.17.2.19 n/a table of port information for rstp dot1dstpextportentry 1.3.6.1.2.1.17.2.19.1 n/a augments * dot1dstpportentry dot1dstpportprotocolmigration 1.3.6.1.2.1.17.2.19.1.1 r/nw truthvalue writing “true(1)” to this object will cause the bpdu of the port to be forcibly transmitted note: this is always “false(2)” when read dot1dstpportadminedgeport 1.3.6.1.2.1.17.2.19.1.2 r/nw truthvalue setting value for edge port dot1dstpportoperedgeport 1.3.6.1.2.1.17.2.19.1.3 r/o truthvalue current value for edge port dot1dstpportadminpointtopoint 1.3.6.1.2.1.17.2.19.1.4 r/nw integer * forcetrue(0) * forcefalse(1) * auto(2) setting value for point-to-point of the port dot1dstpportoperpointtopoint 1.3.6.1.2.1.17.2.19.1.5 r/o truthvalue current value for point-to-point of the port dot1dstpportadminpathcost 1.3.6.1.2.1.17.2.19.1.6 r/nw integer32 (0..200000000) setting value for path cost of port dot1dtp group mib name oid access syntax description dot1dtplearnedentrydiscards 1.3.6.1.2.1.17.4.1 r/o counter32 amount of forwarding information that was discarded due to having exceeded the upper save limit of the forwarding database dot1dtpagingtime 1.3.6.1.2.1.17.4.2 r/nw integer32 (10..1000000) timeout duration for aging out forwarding information that was actively acquired dot1dtpfdbtable 1.3.6.1.2.1.17.4.3 n/a table of unicast entries that have forwarding or filtering information dot1dtpfdbentry 1.3.6.1.2.1.17.4.3.1 n/a index * dot1dtpfdbaddress dot1dtpfdbaddress 1.3.6.1.2.1.17.4.3.1.1 r/o macaddress unicast mac addresses that have forwarding or filtering information dot1dtpfdbport 1.3.6.1.2.1.17.4.3.1.2 r/o integer32 port number of port that transmitted a frame with a source address that is the same as the instance value, corresponding to the dot1dtpfdbaddress dot1dtpfdbstatus 1.3.6.1.2.1.17.4.3.1.3 r/o integer * other(1) * invalid(2) * learned(3) * self(4) * mgmt(5) mac address table status dot1dtpporttable 1.3.6.1.2.1.17.4.4 n/a table for all port information that is associated with a transparent bridge dot1dtpportentry 1.3.6.1.2.1.17.4.4.1 n/a index * dot1dtpport dot1dtpport 1.3.6.1.2.1.17.4.4.1.1 r/o integer32 (1..65535) port numbers that include transparent bridge management information dot1dtpportmaxinfo 1.3.6.1.2.1.17.4.4.1.2 r/o integer32 maximum size of information fields transmitted/received by a port dot1dtpportinframes 1.3.6.1.2.1.17.4.4.1.3 r/o counter32 no. of frames received by a port dot1dtpportoutframes 1.3.6.1.2.1.17.4.4.1.4 r/o counter32 no. of frames transmitted by a port dot1dtpportindiscards 1.3.6.1.2.1.17.4.4.1.5 r/o counter32 no. of frames that are valid for reception, which were discarded during forwarding dot1dstatic group mib name oid access syntax description dot1dstatictable 1.3.6.1.2.1.17.5.1 n/a table of filtering information that was registered statically dot1dstaticentry 1.3.6.1.2.1.17.5.1.1 n/a index * dot1dstaticaddress * dot1dstaticreceiveport dot1dstaticaddress 1.3.6.1.2.1.17.5.1.1.1 r/nc macaddress destination mac address for which filtering information is applied dot1dstaticreceiveport 1.3.6.1.2.1.17.5.1.1.2 r/nc integer32 (0..65535) reception port no. on which filtering information is applied dot1dstaticallowedtogoto 1.3.6.1.2.1.17.5.1.1.3 r/nc octet string (size (0..512)) set of ports on which to transmit frames to which filtering information was applied dot1dstaticstatus 1.3.6.1.2.1.17.5.1.1.4 r/nc integer * other(1) * invalid(2) * permanent(3) * deleteonreset(4) * deleteontimeout(5) application status for filtering information dot1qbase group mib name oid access syntax description dot1qvlanversionnumber 1.3.6.1.2.1.17.7.1.1.1 r/o integer * version1(1) ieee 802.1q version information dot1qmaxvlanid 1.3.6.1.2.1.17.7.1.1.2 r/o vlanid maximum no. of ieee 802.1q vlan ids dot1qmaxsupportedvlans 1.3.6.1.2.1.17.7.1.1.3 r/o unsigned32 maximum no. of ieee 802.1q vlans dot1qnumvlans 1.3.6.1.2.1.17.7.1.1.4 r/o unsigned32 no. of ieee 802.1q vlans used dot1qtp group mib name oid access syntax description dot1qfdbtable 1.3.6.1.2.1.17.7.1.2.1 n/a filtering table dot1qfdbentry 1.3.6.1.2.1.17.7.1.2.1.1 n/a index * dot1qfdbid dot1qfdbid 1.3.6.1.2.1.17.7.1.2.1.1.1 n/a unsigned32 identifier for filtering database dot1qfdbdynamiccount 1.3.6.1.2.1.17.7.1.2.1.1.2 r/o counter32 no. of active entries in filtering database dot1qtpfdbtable 1.3.6.1.2.1.17.7.1.2.2 n/a table of information for unicast entries that have transparent bridge forwarding or filtering information dot1qtpfdbentry 1.3.6.1.2.1.17.7.1.2.2.1 n/a index * dot1qfdbid * dot1qtpfdbaddress dot1qtpfdbaddress 1.3.6.1.2.1.17.7.1.2.2.1.1 n/a macaddress unicast mac addresses that have transparent bridge forwarding or filtering information dot1qtpfdbport 1.3.6.1.2.1.17.7.1.2.2.1.2 r/o integer32 (0..65535) port number of port that transmitted a frame with a source address that is the same as the instance value, corresponding to the transparent bridge dot1qtpfdbaddress dot1qtpfdbstatus 1.3.6.1.2.1.17.7.1.2.2.1.3 r/o integer * other(1) * invalid(2) * learned(3) * self(4) * mgmt(5) transparent bridge mac address table status dot1qvlan group mib name oid access syntax description dot1qvlannumdeletes 1.3.6.1.2.1.17.7.1.4.1 r/o counter32 no. of vlan entries that were deleted dot1qvlancurrenttable 1.3.6.1.2.1.17.7.1.4.2 n/a table of vlan entry information dot1qvlancurrententry 1.3.6.1.2.1.17.7.1.4.2.1 n/a index * dot1qvlantimemark * dot1qvlanindex dot1qvlantimemark 1.3.6.1.2.1.17.7.1.4.2.1.1 n/a timefilter time filter for vlan entries dot1qvlanindex 1.3.6.1.2.1.17.7.1.4.2.1.2 n/a vlanindex vlan id dot1qvlanfdbid 1.3.6.1.2.1.17.7.1.4.2.1.3 r/o unsigned32 filtering database used by vlan dot1qvlancurrentegressports 1.3.6.1.2.1.17.7.1.4.2.1.4 r/o portlist set of ports that output vlan traffic as untagged or tagged frames dot1qvlancurrentuntaggedports 1.3.6.1.2.1.17.7.1.4.2.1.5 r/o portlist set of ports that transmit vlan traffic as untagged frames dot1qvlanstatus 1.3.6.1.2.1.17.7.1.4.2.1.6 r/o integer * other(1) * permanent(2) * dynamicgvrp(3) vlan status dot1qvlancreationtime 1.3.6.1.2.1.17.7.1.4.2.1.7 r/o timeticks sysuptime value when creating vlan dot1qvlanstatictable 1.3.6.1.2.1.17.7.1.4.3 n/a table of vlan static setting information dot1qvlanstaticentry 1.3.6.1.2.1.17.7.1.4.3.1 n/a index * dot1qvlanindex dot1qvlanstaticname 1.3.6.1.2.1.17.7.1.4.3.1.1 r/nc snmpadminstring (size (0..32)) name assigned to vlan dot1qvlanstaticegressports 1.3.6.1.2.1.17.7.1.4.3.1.2 r/nc portlist set of ports assigned to vlan output list dot1qvlanforbiddenegressports 1.3.6.1.2.1.17.7.1.4.3.1.3 r/nc portlist set of ports prohibited from being included in the vlan output list dot1qvlanstaticuntaggedports 1.3.6.1.2.1.17.7.1.4.3.1.4 r/nc portlist set of ports that transmit vlan output traffic as untagged frames dot1qvlanstaticrowstatus 1.3.6.1.2.1.17.7.1.4.3.1.5 r/nc rowstatus vlan entry status dot1qnextfreelocalvlanindex 1.3.6.1.2.1.17.7.1.4.4 r/o integer32 (0|4096..2147483647) next vlan id that can be used dot1qportvlantable 1.3.6.1.2.1.17.7.1.4.5 n/a table of vlan setting information for each port dot1qportvlanentry 1.3.6.1.2.1.17.7.1.4.5.1 n/a augments * dot1dbaseportentry dot1qpvid 1.3.6.1.2.1.17.7.1.4.5.1.1 r/nw vlanindex vlan ids assigned to untagged or priority tag frames dot1qportacceptableframetypes 1.3.6.1.2.1.17.7.1.4.5.1.2 r/nw integer * admitall(1) * admitonlyvlantagged(2) frame types permitted for reception on the port dot1qportingressfiltering 1.3.6.1.2.1.17.7.1.4.5.1.3 r/nw truthvalue filtering of received frames on a port</div><div class="display_word">4.8. dot1dBridge group This MIB is related to dot1dBridge information. The syntax defined in the dot1dBridge group is shown below. Syntax defined in the dot1dBridge group Syntax Definition BridgeId OCTET STRING (SIZE (8)) Timeout Integer32 PortList OCTET STRING VlanIndex Unsigned32 VlanId Integer32 (1..4094) The dot1dBridge group is divided into subgroups such as those shown below. dot1dBridge(17)      |      +--dot1dBase(1)      |      +--dot1dStp(2)      |      +--dot1dTp(4)      |      +--dot1dStatic(5)      |      +--qBridgeMIB(7)         |         +--qBridgeMIBObjects(1)            |            +--dot1qBase(1)            |            +--dot1qTp(2)            |            +--dot1qVlan(4) dot1dBase group MIB name OID Access Syntax Description dot1dBaseBridgeAddress 1.3.6.1.2.1.17.1.1 R/O MacAddress MAC address of bridge dot1dBaseNumPorts 1.3.6.1.2.1.17.1.2 R/O Integer32 No. of ports for bridge dot1dBaseType 1.3.6.1.2.1.17.1.3 R/O INTEGER * unknown(1) * transparent-only(2) * sourceroute-only(3) * srt(4) Type of bridging executable by the bridge dot1dBasePortTable 1.3.6.1.2.1.17.1.4 N/A Table of port information for bridge dot1dBasePortEntry 1.3.6.1.2.1.17.1.4.1 N/A INDEX * dot1dBasePort dot1dBasePort 1.3.6.1.2.1.17.1.4.1.1 R/O Integer32 (1..65535) Port number dot1dBasePortIfIndex 1.3.6.1.2.1.17.1.4.1.2 R/O InterfaceIndex Instance value for ifIndex, defined by the IF-MIB of the interface corresponding to the port dot1dBasePortCircuit 1.3.6.1.2.1.17.1.4.1.3 R/O OBJECT IDENTIFIER Identifier used when the value of dot1dBasePortIfIndex is the same port in the bridge dot1dBasePortDelayExceededDiscards 1.3.6.1.2.1.17.1.4.1.4 R/O Counter32 No. of frames discarded at the port due to a bridge forwarding delay Note: This is always “0” on this product dot1dBasePortMtuExceededDiscards 1.3.6.1.2.1.17.1.4.1.5 R/O Counter32 No. of frames discarded at the port due to excessive size Note: This is always “0” on this product dot1dStp group MIB name OID Access Syntax Description dot1dStpProtocolSpecification 1.3.6.1.2.1.17.2.1 R/O INTEGER * unknown(1) * decLb100(2) * ieee8021d(3) Spanning tree protocol version dot1dStpPriority 1.3.6.1.2.1.17.2.2 R/NW Integer32 (0..65535) Bridge priority value dot1dStpTimeSinceTopologyChange 1.3.6.1.2.1.17.2.3 R/O TimeTicks Time elapsed since detecting a change in topology dot1dStpTopChanges 1.3.6.1.2.1.17.2.4 R/O Counter32 No. of times a change in topology has been detected dot1dStpDesignatedRoot 1.3.6.1.2.1.17.2.5 R/O BridgeId Root bridge identifier of spanning tree dot1dStpRootCost 1.3.6.1.2.1.17.2.6 R/O Integer32 Path cost to root bridge dot1dStpRootPort 1.3.6.1.2.1.17.2.7 R/O Integer32 Port number with the lowest cost from bridge to root bridge dot1dStpMaxAge 1.3.6.1.2.1.17.2.8 R/O Timeout Maximum time elapsed for spanning tree protocol information (in units of 1/100 sec.) dot1dStpHelloTime 1.3.6.1.2.1.17.2.9 R/O Timeout BPDU transmission interval (in units of 1/100 sec.) dot1dStpHoldTime 1.3.6.1.2.1.17.2.10 R/O Integer32 Minimum transmission interval for Configuration BPDU (in units of 1/100 sec.) dot1dStpForwardDelay 1.3.6.1.2.1.17.2.11 R/O Timeout Forward delay time (in units of 1/100 sec.) dot1dStpBridgeMaxAge 1.3.6.1.2.1.17.2.12 R/NW Timeout (600..4000) Setting value for maximum elapsed time dot1dStpBridgeHelloTime 1.3.6.1.2.1.17.2.13 R/NW Timeout (100..1000) Setting value for BPDU transmission interval dot1dStpBridgeForwardDelay 1.3.6.1.2.1.17.2.14 R/NW Timeout (400..3000) Setting value for forward delay time dot1dStpPortTable 1.3.6.1.2.1.17.2.15 N/A Table of port information for spanning tree protocol dot1dStpPortEntry 1.3.6.1.2.1.17.2.15.1 N/A INDEX * dot1dStpPort dot1dStpPort 1.3.6.1.2.1.17.2.15.1.1 R/O Integer32 (1..65535) Port number for spanning tree protocol dot1dStpPortPriority 1.3.6.1.2.1.17.2.15.1.2 R/NW Integer32 (0..255) Port priority value dot1dStpPortState 1.3.6.1.2.1.17.2.15.1.3 R/O INTEGER * disabled(1) * blocking(2) * listening(3) * learning(4) * forwarding(5) * broken(6) Port status dot1dStpPortEnable 1.3.6.1.2.1.17.2.15.1.4 R/NW INTEGER * enabled(1) * disabled(2) Port enabled/disabled status dot1dStpPortPathCost 1.3.6.1.2.1.17.2.15.1.5 R/NW Integer32 (1..65535) Path cost value for port dot1dStpPortDesignatedRoot 1.3.6.1.2.1.17.2.15.1.6 R/O BridgeId Root bridge identifier of configuration BPDU dot1dStpPortDesignatedCost 1.3.6.1.2.1.17.2.15.1.7 R/O Integer32 Path cost value for specified port dot1dStpPortDesignatedBridge 1.3.6.1.2.1.17.2.15.1.8 R/O BridgeId Specified bridge identifier dot1dStpPortDesignatedPort 1.3.6.1.2.1.17.2.15.1.9 R/O OCTET STRING (SIZE (2)) Port identifier for specified bridge dot1dStpPortForwardTransitions 1.3.6.1.2.1.17.2.15.1.10 R/O Counter32 No. of times that port switched from acquisition status to forwarding status dot1dStpPortPathCost32 1.3.6.1.2.1.17.2.15.1.11 R/NW Integer32 (1..200000000) Path cost value for ports complying with IEEE 802.1t dot1dStpVersion 1.3.6.1.2.1.17.2.16 R/NW INTEGER * stpCompatible(0) * rstp(2) Spanning tree protocol version dot1dStpTxHoldCount 1.3.6.1.2.1.17.2.17 R/NW Integer32 (1..10) Forward hold count value dot1dStpExtPortTable 1.3.6.1.2.1.17.2.19 N/A Table of port information for RSTP dot1dStpExtPortEntry 1.3.6.1.2.1.17.2.19.1 N/A AUGMENTS * dot1dStpPortEntry dot1dStpPortProtocolMigration 1.3.6.1.2.1.17.2.19.1.1 R/NW TruthValue Writing “true(1)” to this object will cause the BPDU of the port to be forcibly transmitted Note: This is always “false(2)” when read dot1dStpPortAdminEdgePort 1.3.6.1.2.1.17.2.19.1.2 R/NW TruthValue Setting value for edge port dot1dStpPortOperEdgePort 1.3.6.1.2.1.17.2.19.1.3 R/O TruthValue Current value for edge port dot1dStpPortAdminPointToPoint 1.3.6.1.2.1.17.2.19.1.4 R/NW INTEGER * forceTrue(0) * forceFalse(1) * auto(2) Setting value for point-to-point of the port dot1dStpPortOperPointToPoint 1.3.6.1.2.1.17.2.19.1.5 R/O TruthValue Current value for point-to-point of the port dot1dStpPortAdminPathCost 1.3.6.1.2.1.17.2.19.1.6 R/NW Integer32 (0..200000000) Setting value for path cost of port dot1dTp group MIB name OID Access Syntax Description dot1dTpLearnedEntryDiscards 1.3.6.1.2.1.17.4.1 R/O Counter32 Amount of forwarding information that was discarded due to having exceeded the upper save limit of the forwarding database dot1dTpAgingTime 1.3.6.1.2.1.17.4.2 R/NW Integer32 (10..1000000) Timeout duration for aging out forwarding information that was actively acquired dot1dTpFdbTable 1.3.6.1.2.1.17.4.3 N/A Table of unicast entries that have forwarding or filtering information dot1dTpFdbEntry 1.3.6.1.2.1.17.4.3.1 N/A INDEX * dot1dTpFdbAddress dot1dTpFdbAddress 1.3.6.1.2.1.17.4.3.1.1 R/O MacAddress Unicast MAC addresses that have forwarding or filtering information dot1dTpFdbPort 1.3.6.1.2.1.17.4.3.1.2 R/O Integer32 Port number of port that transmitted a frame with a source address that is the same as the instance value, corresponding to the dot1dTpFdbAddress dot1dTpFdbStatus 1.3.6.1.2.1.17.4.3.1.3 R/O INTEGER * other(1) * invalid(2) * learned(3) * self(4) * mgmt(5) MAC address table status dot1dTpPortTable 1.3.6.1.2.1.17.4.4 N/A Table for all port information that is associated with a transparent bridge dot1dTpPortEntry 1.3.6.1.2.1.17.4.4.1 N/A INDEX * dot1dTpPort dot1dTpPort 1.3.6.1.2.1.17.4.4.1.1 R/O Integer32 (1..65535) Port numbers that include transparent bridge management information dot1dTpPortMaxInfo 1.3.6.1.2.1.17.4.4.1.2 R/O Integer32 Maximum size of information fields transmitted/received by a port dot1dTpPortInFrames 1.3.6.1.2.1.17.4.4.1.3 R/O Counter32 No. of frames received by a port dot1dTpPortOutFrames 1.3.6.1.2.1.17.4.4.1.4 R/O Counter32 No. of frames transmitted by a port dot1dTpPortInDiscards 1.3.6.1.2.1.17.4.4.1.5 R/O Counter32 No. of frames that are valid for reception, which were discarded during forwarding dot1dStatic group MIB name OID Access Syntax Description dot1dStaticTable 1.3.6.1.2.1.17.5.1 N/A Table of filtering information that was registered statically dot1dStaticEntry 1.3.6.1.2.1.17.5.1.1 N/A INDEX * dot1dStaticAddress * dot1dStaticReceivePort dot1dStaticAddress 1.3.6.1.2.1.17.5.1.1.1 R/NC MacAddress Destination MAC address for which filtering information is applied dot1dStaticReceivePort 1.3.6.1.2.1.17.5.1.1.2 R/NC Integer32 (0..65535) Reception port no. on which filtering information is applied dot1dStaticAllowedToGoTo 1.3.6.1.2.1.17.5.1.1.3 R/NC OCTET STRING (SIZE (0..512)) Set of ports on which to transmit frames to which filtering information was applied dot1dStaticStatus 1.3.6.1.2.1.17.5.1.1.4 R/NC INTEGER * other(1) * invalid(2) * permanent(3) * deleteOnReset(4) * deleteOnTimeout(5) Application status for filtering information dot1qBase group MIB name OID Access Syntax Description dot1qVlanVersionNumber 1.3.6.1.2.1.17.7.1.1.1 R/O INTEGER * version1(1) IEEE 802.1Q version information dot1qMaxVlanId 1.3.6.1.2.1.17.7.1.1.2 R/O VlanId Maximum no. of IEEE 802.1Q VLAN IDs dot1qMaxSupportedVlans 1.3.6.1.2.1.17.7.1.1.3 R/O Unsigned32 Maximum no. of IEEE 802.1Q VLANs dot1qNumVlans 1.3.6.1.2.1.17.7.1.1.4 R/O Unsigned32 No. of IEEE 802.1Q VLANs used dot1qTp group MIB name OID Access Syntax Description dot1qFdbTable 1.3.6.1.2.1.17.7.1.2.1 N/A Filtering table dot1qFdbEntry 1.3.6.1.2.1.17.7.1.2.1.1 N/A INDEX * dot1qFdbId dot1qFdbId 1.3.6.1.2.1.17.7.1.2.1.1.1 N/A Unsigned32 Identifier for filtering database dot1qFdbDynamicCount 1.3.6.1.2.1.17.7.1.2.1.1.2 R/O Counter32 No. of active entries in filtering database dot1qTpFdbTable 1.3.6.1.2.1.17.7.1.2.2 N/A Table of information for unicast entries that have transparent bridge forwarding or filtering information dot1qTpFdbEntry 1.3.6.1.2.1.17.7.1.2.2.1 N/A INDEX * dot1qFdbId * dot1qTpFdbAddress dot1qTpFdbAddress 1.3.6.1.2.1.17.7.1.2.2.1.1 N/A MacAddress Unicast MAC addresses that have transparent bridge forwarding or filtering information dot1qTpFdbPort 1.3.6.1.2.1.17.7.1.2.2.1.2 R/O Integer32 (0..65535) Port number of port that transmitted a frame with a source address that is the same as the instance value, corresponding to the transparent bridge dot1qTpFdbAddress dot1qTpFdbStatus 1.3.6.1.2.1.17.7.1.2.2.1.3 R/O INTEGER * other(1) * invalid(2) * learned(3) * self(4) * mgmt(5) Transparent bridge MAC address table status dot1qVlan group MIB name OID Access Syntax Description dot1qVlanNumDeletes 1.3.6.1.2.1.17.7.1.4.1 R/O Counter32 No. of VLAN entries that were deleted dot1qVlanCurrentTable 1.3.6.1.2.1.17.7.1.4.2 N/A Table of VLAN entry information dot1qVlanCurrentEntry 1.3.6.1.2.1.17.7.1.4.2.1 N/A INDEX * dot1qVlanTimeMark * dot1qVlanIndex dot1qVlanTimeMark 1.3.6.1.2.1.17.7.1.4.2.1.1 N/A TimeFilter Time filter for VLAN entries dot1qVlanIndex 1.3.6.1.2.1.17.7.1.4.2.1.2 N/A VlanIndex VLAN ID dot1qVlanFdbId 1.3.6.1.2.1.17.7.1.4.2.1.3 R/O Unsigned32 Filtering database used by VLAN dot1qVlanCurrentEgressPorts 1.3.6.1.2.1.17.7.1.4.2.1.4 R/O PortList Set of ports that output VLAN traffic as untagged or tagged frames dot1qVlanCurrentUntaggedPorts 1.3.6.1.2.1.17.7.1.4.2.1.5 R/O PortList Set of ports that transmit VLAN traffic as untagged frames dot1qVlanStatus 1.3.6.1.2.1.17.7.1.4.2.1.6 R/O INTEGER * other(1) * permanent(2) * dynamicGvrp(3) VLAN status dot1qVlanCreationTime 1.3.6.1.2.1.17.7.1.4.2.1.7 R/O TimeTicks sysUpTime value when creating VLAN dot1qVlanStaticTable 1.3.6.1.2.1.17.7.1.4.3 N/A Table of VLAN static setting information dot1qVlanStaticEntry 1.3.6.1.2.1.17.7.1.4.3.1 N/A INDEX * dot1qVlanIndex dot1qVlanStaticName 1.3.6.1.2.1.17.7.1.4.3.1.1 R/NC SnmpAdminString (SIZE (0..32)) Name assigned to VLAN dot1qVlanStaticEgressPorts 1.3.6.1.2.1.17.7.1.4.3.1.2 R/NC PortList Set of ports assigned to VLAN output list dot1qVlanForbiddenEgressPorts 1.3.6.1.2.1.17.7.1.4.3.1.3 R/NC PortList Set of ports prohibited from being included in the VLAN output list dot1qVlanStaticUntaggedPorts 1.3.6.1.2.1.17.7.1.4.3.1.4 R/NC PortList Set of ports that transmit VLAN output traffic as untagged frames dot1qVlanStaticRowStatus 1.3.6.1.2.1.17.7.1.4.3.1.5 R/NC RowStatus VLAN entry status dot1qNextFreeLocalVlanIndex 1.3.6.1.2.1.17.7.1.4.4 R/O Integer32 (0|4096..2147483647) Next VLAN ID that can be used dot1qPortVlanTable 1.3.6.1.2.1.17.7.1.4.5 N/A Table of VLAN setting information for each port dot1qPortVlanEntry 1.3.6.1.2.1.17.7.1.4.5.1 N/A AUGMENTS * dot1dBasePortEntry dot1qPvid 1.3.6.1.2.1.17.7.1.4.5.1.1 R/NW VlanIndex VLAN IDs assigned to untagged or priority tag frames dot1qPortAcceptableFrameTypes 1.3.6.1.2.1.17.7.1.4.5.1.2 R/NW INTEGER * admitAll(1) * admitOnlyVlanTagged(2) Frame types permitted for reception on the port dot1qPortIngressFiltering 1.3.6.1.2.1.17.7.1.4.5.1.3 R/NW TruthValue Filtering of received frames on a port</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#ifmibグループ">4.9. ifMIB group</div><div class="search_word">4.9. ifmib group this mib is related to additional information for the interface. the ifmib group is divided into subgroups such as those shown below. ifmib(31)      |      +--ifmibobjects(1) ifmibobjects group mib name oid access syntax description ifxtable 1.3.6.1.2.1.31.1.1 n/a table of additional interface information counters with a vlan ifindex value count the total traffic of all physical ports associated to the vlan ifxentry 1.3.6.1.2.1.31.1.1.1 n/a augments * ifentry ifname 1.3.6.1.2.1.31.1.1.1.1 r/o displaystring interface name ifinmulticastpkts 1.3.6.1.2.1.31.1.1.1.2 r/o counter32 number of multicast packets notified to higher protocol ifinbroadcastpkts 1.3.6.1.2.1.31.1.1.1.3 r/o counter32 number of broadcast packets notified to higher protocol ifoutmulticastpkts 1.3.6.1.2.1.31.1.1.1.4 r/o counter32 number of multicast packets requested for transmission by a higher protocol ifoutbroadcastpkts 1.3.6.1.2.1.31.1.1.1.5 r/o counter32 number of broadcast packets requested for transmission by a higher protocol ifhcinoctets 1.3.6.1.2.1.31.1.1.1.6 r/o counter64 total number of octets received 64-bit version of ifinoctets ifhcoutoctets 1.3.6.1.2.1.31.1.1.1.10 r/o counter64 total number of octets sent 64-bit version of ifoutoctets ifhighspeed 1.3.6.1.2.1.31.1.1.1.15 r/o gauge32 the speed of the interface. mbps ifalias 1.3.6.1.2.1.31.1.1.1.18 r/nw displaystring (size (0..64)) alias name of the interface * if the description command is set for the interface, that value will be used. * if the description command is not set, an empty character string will be set. * if a character string exceeding 64 characters set in the description command, only the first 64 characters are returned.</div><div class="display_word">4.9. ifMIB group This MIB is related to additional information for the interface. The ifMIB group is divided into subgroups such as those shown below. ifMIB(31)      |      +--ifMIBObjects(1) ifMIBObjects group MIB name OID Access Syntax Description ifXTable 1.3.6.1.2.1.31.1.1 N/A Table of additional interface information Counters with a VLAN ifIndex value count the total traffic of all physical ports associated to the VLAN ifXEntry 1.3.6.1.2.1.31.1.1.1 N/A AUGMENTS * ifEntry ifName 1.3.6.1.2.1.31.1.1.1.1 R/O DisplayString Interface name ifInMulticastPkts 1.3.6.1.2.1.31.1.1.1.2 R/O Counter32 Number of multicast packets notified to higher protocol ifInBroadcastPkts 1.3.6.1.2.1.31.1.1.1.3 R/O Counter32 Number of broadcast packets notified to higher protocol ifOutMulticastPkts 1.3.6.1.2.1.31.1.1.1.4 R/O Counter32 Number of multicast packets requested for transmission by a higher protocol ifOutBroadcastPkts 1.3.6.1.2.1.31.1.1.1.5 R/O Counter32 Number of broadcast packets requested for transmission by a higher protocol ifHCInOctets 1.3.6.1.2.1.31.1.1.1.6 R/O Counter64 Total number of octets received 64-bit version of ifInOctets ifHCOutOctets 1.3.6.1.2.1.31.1.1.1.10 R/O Counter64 Total number of octets sent 64-bit version of ifOutOctets ifHighSpeed 1.3.6.1.2.1.31.1.1.1.15 R/O Gauge32 The speed of the interface. Mbps ifAlias 1.3.6.1.2.1.31.1.1.1.18 R/NW DisplayString (SIZE (0..64)) Alias name of the interface * If the description command is set for the interface, that value will be used. * If the description command is not set, an empty character string will be set. * If a character string exceeding 64 characters set in the description command, only the first 64 characters are returned.</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#entitymibグループ">4.10. entityMIB group</div><div class="search_word">4.10. entitymib group this mib is related to entity information the syntax defined in the entitymib group is shown below. syntax defined in the entitymib group syntax definition physicalindex integer32 (1..2147483647) the entitymib group is divided into subgroups such as those shown below. entitymib(47)      |      +--entitymibobjects(1)         |         +--entityphysical(1) entityphysical group mib name oid access syntax description entphysicaltable 1.3.6.1.2.1.47.1.1.1 n/a table of entity information entphysicalentry 1.3.6.1.2.1.47.1.1.1.1 n/a index * entphysicalindex entphysicalindex 1.3.6.1.2.1.47.1.1.1.1.1 n/a physicalindex index of entities stack id this can be obtained with stack id 1 if stack was not configured. entphysicalserialnum 1.3.6.1.2.1.47.1.1.1.1.11 r/nw snmpadminstring (size (0..32)) serial number of device</div><div class="display_word">4.10. entityMIB group This MIB is related to entity information The syntax defined in the entityMIB group is shown below. Syntax defined in the entityMIB group Syntax Definition PhysicalIndex Integer32 (1..2147483647) The entityMIB group is divided into subgroups such as those shown below. entityMIB(47)      |      +--entityMIBObjects(1)         |         +--entityPhysical(1) entityPhysical group MIB name OID Access Syntax Description entPhysicalTable 1.3.6.1.2.1.47.1.1.1 N/A Table of entity information entPhysicalEntry 1.3.6.1.2.1.47.1.1.1.1 N/A INDEX * entPhysicalIndex entPhysicalIndex 1.3.6.1.2.1.47.1.1.1.1.1 N/A PhysicalIndex Index of entities Stack ID This can be obtained with stack ID 1 if stack was not configured. entPhysicalSerialNum 1.3.6.1.2.1.47.1.1.1.1.11 R/NW SnmpAdminString (SIZE (0..32)) Serial number of device</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#powerethernetmibグループ">4.11. powerEthernetMIB group</div><div class="search_word">4.11. powerethernetmib group this mib is related to poe information. the powerethernetmib group is divided into subgroups such as those shown below. powerethernetmib(105)      |      +--pethobjects(1)         |         +--pethmainpseobjects(3)         |         +--pethnotificationcontrol(4) pethobjects group mib name oid access syntax description pethpseporttable 1.3.6.1.2.1.105.1.1 n/a table of port information for poe pethpseportentry 1.3.6.1.2.1.105.1.1.1 n/a index * pethpseportgroupindex * pethpseportindex pethpseportgroupindex 1.3.6.1.2.1.105.1.1.1.1 n/a integer32 (1..2147483647) identifier for power supply device group stack id this can be obtained with stack id 1 if stack was not configured. pethpseportindex 1.3.6.1.2.1.105.1.1.1.2 n/a integer32 (1..2147483647) identifier of the port in pethpseportgroupindex port number pethpseportadminenable 1.3.6.1.2.1.105.1.1.1.3 r/w truthvalue enables/disables the power supply function pethpseportpowerpairscontrolability 1.3.6.1.2.1.105.1.1.1.4 r/o truthvalue possible/not possible to switch the power supply target pair (fixed to false(2)) pethpseportpowerpairs 1.3.6.1.2.1.105.1.1.1.5 r/nw integer * signal(1) * spare(2) type of power supply target pair (fixed to signal(1)) pethpseportdetectionstatus 1.3.6.1.2.1.105.1.1.1.6 r/o integer * disabled(1) * searching(2) * deliveringpower(3) * fault(4) * test(5) * otherfault(6) power receiving device detection status fault(4) and test(5) are not used pethpseportpowerpriority 1.3.6.1.2.1.105.1.1.1.7 r/w integer * critical(1) * high(2) * low(3) port power supply priority order pethpseporttype 1.3.6.1.2.1.105.1.1.1.9 r/w snmpadminstring (size (0..64)) description about power supply port setting value of the power-inline description command pethpseportpowerclassifications 1.3.6.1.2.1.105.1.1.1.10 r/o integer * class0(1) * class1(2) * class2(3) * class3(4) * class4(5) information on the power supply class of the connected device * if no poe device is connected, this value will be class0(1) * if a device of class5 or higher is connected, this value will be class4(5) pethmainpseobjects group mib name oid access syntax description pethmainpsetable 1.3.6.1.2.1.105.1.3.1 n/a table of main power supply unit information for power supply device pethmainpseentry 1.3.6.1.2.1.105.1.3.1.1 n/a index * pethmainpsegroupindex pethmainpsegroupindex 1.3.6.1.2.1.105.1.3.1.1.1 n/a integer32 (1..2147483647) identifier for power supply device group stack id this can be obtained with stack id 1 if stack was not configured. pethmainpsepower 1.3.6.1.2.1.105.1.3.1.1.2 r/o gauge32 (1..65535) total power of the power supply device (watts) pethmainpseoperstatus 1.3.6.1.2.1.105.1.3.1.1.3 r/o integer * on(1) * off(2) * faulty(3) power supply device control status pethmainpseconsumptionpower 1.3.6.1.2.1.105.1.3.1.1.4 r/o gauge32 power consumption of the power supply device (watts) pethmainpseusagethreshold 1.3.6.1.2.1.105.1.3.1.1.5 r/nw integer32 (1..99) power consumption threshold value (percentage) for alarm notification + this product calculates this mib value from the guardband value. the relational formula is as follows: pethmainpseusagethreshold = round (100 * (pethmainpsepower - guard band value) / pethmainpsepower) the minimum value that can be specified is calculated using the following formula. minimum = round ((pethmainpsepower - 30) / pethmainpsepower) note: round indicates rounding off to the nearest whole number. if the calculation result is 100, the value of this mib will be regarded as 99. pethnotificationcontrol group mib name oid access syntax description pethnotificationcontroltable 1.3.6.1.2.1.105.1.4.1 n/a table of notification information display/control information for power supply devices pethnotificationcontrolentry 1.3.6.1.2.1.105.1.4.1.1 n/a index * pethnotificationcontrolgroupindex pethnotificationcontrolgroupindex 1.3.6.1.2.1.105.1.4.1.1.1 n/a integer32 (1..2147483647) identifier for notification information group stack id this can be obtained with stack id 1 if stack was not configured. pethnotificationcontrolenable 1.3.6.1.2.1.105.1.4.1.1.2 r/w truthvalue control of notification function. * true(1): allows notifications * false(2): prohibits notifications corresponds to the powerethernet parameter of the snmp-server enable trap command</div><div class="display_word">4.11. powerEthernetMIB group This MIB is related to PoE information. The powerEthernetMIB group is divided into subgroups such as those shown below. powerEthernetMIB(105)      |      +--pethObjects(1)         |         +--pethMainPseObjects(3)         |         +--pethNotificationControl(4) pethObjects group MIB name OID Access Syntax Description pethPsePortTable 1.3.6.1.2.1.105.1.1 N/A Table of port information for PoE pethPsePortEntry 1.3.6.1.2.1.105.1.1.1 N/A INDEX * pethPsePortGroupIndex * pethPsePortIndex pethPsePortGroupIndex 1.3.6.1.2.1.105.1.1.1.1 N/A Integer32 (1..2147483647) Identifier for power supply device group Stack ID This can be obtained with stack ID 1 if stack was not configured. pethPsePortIndex 1.3.6.1.2.1.105.1.1.1.2 N/A Integer32 (1..2147483647) Identifier of the port in pethPsePortGroupIndex Port number pethPsePortAdminEnable 1.3.6.1.2.1.105.1.1.1.3 R/W TruthValue Enables/disables the power supply function pethPsePortPowerPairsControlAbility 1.3.6.1.2.1.105.1.1.1.4 R/O TruthValue Possible/not possible to switch the power supply target pair (fixed to false(2)) pethPsePortPowerPairs 1.3.6.1.2.1.105.1.1.1.5 R/NW INTEGER * signal(1) * spare(2) Type of power supply target pair (fixed to signal(1)) pethPsePortDetectionStatus 1.3.6.1.2.1.105.1.1.1.6 R/O INTEGER * disabled(1) * searching(2) * deliveringPower(3) * fault(4) * test(5) * otherFault(6) Power receiving device detection status fault(4) and test(5) are not used pethPsePortPowerPriority 1.3.6.1.2.1.105.1.1.1.7 R/W INTEGER * critical(1) * high(2) * low(3) Port power supply priority order pethPsePortType 1.3.6.1.2.1.105.1.1.1.9 R/W SnmpAdminString (SIZE (0..64)) Description about power supply port Setting value of the power-inline description command pethPsePortPowerClassifications 1.3.6.1.2.1.105.1.1.1.10 R/O INTEGER * class0(1) * class1(2) * class2(3) * class3(4) * class4(5) Information on the power supply class of the connected device * If no PoE device is connected, this value will be class0(1) * If a device of class5 or higher is connected, this value will be class4(5) pethMainPseObjects group MIB name OID Access Syntax Description pethMainPseTable 1.3.6.1.2.1.105.1.3.1 N/A Table of main power supply unit information for power supply device pethMainPseEntry 1.3.6.1.2.1.105.1.3.1.1 N/A INDEX * pethMainPseGroupIndex pethMainPseGroupIndex 1.3.6.1.2.1.105.1.3.1.1.1 N/A Integer32 (1..2147483647) Identifier for power supply device group Stack ID This can be obtained with stack ID 1 if stack was not configured. pethMainPsePower 1.3.6.1.2.1.105.1.3.1.1.2 R/O Gauge32 (1..65535) Total power of the power supply device (watts) pethMainPseOperStatus 1.3.6.1.2.1.105.1.3.1.1.3 R/O INTEGER * on(1) * off(2) * faulty(3) Power supply device control status pethMainPseConsumptionPower 1.3.6.1.2.1.105.1.3.1.1.4 R/O Gauge32 Power consumption of the power supply device (watts) pethMainPseUsageThreshold 1.3.6.1.2.1.105.1.3.1.1.5 R/NW Integer32 (1..99) Power consumption threshold value (percentage) for alarm notification + This product calculates this MIB value from the guardband value. The relational formula is as follows: pethMainPseUsageThreshold = ROUND (100 * (pethMainPsePower - Guard band value) / pethMainPsePower) The minimum value that can be specified is calculated using the following formula. Minimum = ROUND ((pethMainPsePower - 30) / pethMainPsePower) Note: ROUND indicates rounding off to the nearest whole number. If the calculation result is 100, the value of this MIB will be regarded as 99. pethNotificationControl group MIB name OID Access Syntax Description pethNotificationControlTable 1.3.6.1.2.1.105.1.4.1 N/A Table of notification information display/control information for power supply devices pethNotificationControlEntry 1.3.6.1.2.1.105.1.4.1.1 N/A INDEX * pethNotificationControlGroupIndex pethNotificationControlGroupIndex 1.3.6.1.2.1.105.1.4.1.1.1 N/A Integer32 (1..2147483647) Identifier for notification information group Stack ID This can be obtained with stack ID 1 if stack was not configured. pethNotificationControlEnable 1.3.6.1.2.1.105.1.4.1.1.2 R/W TruthValue Control of notification function. * true(1): Allows notifications * false(2): Prohibits notifications Corresponds to the powerethernet parameter of the snmp-server enable trap command</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#プライベートmib">5. Private MIBs</div><div class="search_word">5. private mibs the private mibs that are supported by this product are shown below.</div><div class="display_word">5. Private MIBs The private MIBs that are supported by this product are shown below.</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#yamahaswhardwareグループ">5.1. yamahaSWHardware group</div><div class="search_word">5.1. yamahaswhardware group this mib is related to hardware information for yamaha switches. yamahaswhardware group mib name oid access syntax description yshmemorysize 1.3.6.1.4.1.1182.3.1.2 r/o integer memory size yshflashromsize 1.3.6.1.4.1.1182.3.1.3 r/o integer flashrom size yshmemoryutil 1.3.6.1.4.1.1182.3.1.4 r/o gauge (0..100) memory usage ratio yshcpuutil5sec 1.3.6.1.4.1.1182.3.1.5 r/o gauge (0..100) cpu usage ratio (5-second average) yshcpuutil1min 1.3.6.1.4.1.1182.3.1.6 r/o gauge (0..100) cpu usage ratio (1-minute average) yshcpuutil5min 1.3.6.1.4.1.1182.3.1.7 r/o gauge (0..100) cpu usage ratio (5-minute average) yshstacktable 1.3.6.1.4.1.1182.3.1.19 n/a table of hardware information for each member switch + this can only be obtained when a stack is configured. yshstackentry 1.3.6.1.4.1.1182.3.1.19.1 n/a index * yshstackid yshstackid 1.3.6.1.4.1.1182.3.1.19.1.1 n/a integer (1..2147483647) stack id yshstackmemorysize 1.3.6.1.4.1.1182.3.1.19.1.2 r/o integer memory size yshstackflashromsize 1.3.6.1.4.1.1182.3.1.19.1.3 r/o integer flashrom size yshstackmemoryutil 1.3.6.1.4.1.1182.3.1.19.1.4 r/o gauge (0..100) memory usage ratio yshstackcpuutil5sec 1.3.6.1.4.1.1182.3.1.19.1.5 r/o gauge (0..100) cpu usage ratio (5-second average) yshstackcpuutil1min 1.3.6.1.4.1.1182.3.1.19.1.6 r/o gauge (0..100) cpu usage ratio (1-minute average) yshstackcpuutil5min 1.3.6.1.4.1.1182.3.1.19.1.7 r/o gauge (0..100) cpu usage ratio (5-minute average) yshenabletemperaturetrap 1.3.6.1.4.1.1182.3.1.20 r/w integer * enabled(1) * disabled(2) setting value that determines whether snmp traps based on temperature information are notified yshtemperaturetable 1.3.6.1.4.1.1182.3.1.21 n/a temperature information table yshtemperatureentry 1.3.6.1.4.1.1182.3.1.21.1 n/a index * yshtemperaturestackid * yshtemperaturedevicetype * yshtemperaturedeviceindex yshtemperaturestackid 1.3.6.1.4.1.1182.3.1.21.1.1 n/a integer (1..2147483647) stack id this can be obtained with stack id 1 if stack was not configured. yshtemperaturedevicetype 1.3.6.1.4.1.1182.3.1.21.1.2 n/a integer * cpu(1) * phy(2) * sfp(3) * thermal-sensor(4) * pse(5) * mac(6) device type yshtemperaturedeviceindex 1.3.6.1.4.1.1182.3.1.21.1.3 n/a integer (1..2147483647) index for each device + for example, index values are 1 and 2 for devices with two cpus yshtemperaturevalue 1.3.6.1.4.1.1182.3.1.21.1.4 r/o gauge device temperature + if the device temperature was not measured, this is “0” yshtemperaturestatustable 1.3.6.1.4.1.1182.3.1.22 n/a temperature status table yshtemperaturestatusentry 1.3.6.1.4.1.1182.3.1.22.1 n/a index * yshtemperaturestatusstackid * yshtemperaturestatusdevicetype yshtemperaturestatusstackid 1.3.6.1.4.1.1182.3.1.22.1.1 n/a integer (1..2147483647) stack id this can be obtained with stack id 1 if stack was not configured. yshtemperaturestatusdevicetype 1.3.6.1.4.1.1182.3.1.22.1.2 n/a integer * cpu(1) * phy(2) * sfp(3) * thermal-sensor(4) * pse(5) * mac(6) device type yshtemperaturestatus 1.3.6.1.4.1.1182.3.1.22.1.3 r/o integer * normal(1) * warning(2) * error(3) temperature status * “normal” when normal * “warning” indicates temperature over high threshold value * “error” indicates temperature exceeded alarm temperature yshtemperaturestatusnormalthreshold 1.3.6.1.4.1.1182.3.1.22.1.4 n/a gauge threshold value for determining normal status note: only used for trap notifications yshtemperaturestatuswarningthreshold 1.3.6.1.4.1.1182.3.1.22.1.5 n/a gauge threshold value for determining warning status note: only used for trap notifications yshtemperaturestatuserrorthreshold 1.3.6.1.4.1.1182.3.1.22.1.6 n/a gauge threshold value for determining error status note: only used for trap notifications yshenablefantrap 1.3.6.1.4.1.1182.3.1.23 r/w integer * enabled(1) * disabled(2) setting value for determining whether snmp traps based on fan information are notified yshfantable 1.3.6.1.4.1.1182.3.1.24 n/a fan information table yshfanentry 1.3.6.1.4.1.1182.3.1.24.1 n/a index * yshfanstackid * yshfanindex yshfanstackid 1.3.6.1.4.1.1182.3.1.24.1.1 n/a integer (1..2147483647) stack id this can be obtained with stack id 1 if stack was not configured. yshfanindex 1.3.6.1.4.1.1182.3.1.24.1.2 n/a integer (1..2147483647) index for each fan + for example, index values will be 1 and 2 for devices with two fans yshfanrpm 1.3.6.1.4.1.1182.3.1.24.1.3 r/o gauge fan rpm yshfanstatus 1.3.6.1.4.1.1182.3.1.24.1.4 r/o integer * normal(1) * stopped(2) fan status yshfanspeedstatustable 1.3.6.1.4.1.1182.3.1.25 n/a fan rpm status table yshfanspeedstatusentry 1.3.6.1.4.1.1182.3.1.25.1 n/a index * yshfanspeedstatusstackid yshfanspeedstatusstackid 1.3.6.1.4.1.1182.3.1.25.1.1 n/a integer (1..2147483647) stack id this can be obtained with stack id 1 if stack was not configured. yshfanspeedstatus 1.3.6.1.4.1.1182.3.1.25.1.2 r/o integer * low(1) * middle(2) * high(3) * max-speed(4) * middle-high(5) * high-alarm(6) fan rpm status</div><div class="display_word">5.1. yamahaSWHardware group This MIB is related to hardware information for Yamaha switches. yamahaSWHardware group MIB name OID Access Syntax Description yshMemorySize 1.3.6.1.4.1.1182.3.1.2 R/O INTEGER Memory size yshFlashROMSize 1.3.6.1.4.1.1182.3.1.3 R/O INTEGER FlashROM size yshMemoryUtil 1.3.6.1.4.1.1182.3.1.4 R/O Gauge (0..100) Memory usage ratio yshCpuUtil5sec 1.3.6.1.4.1.1182.3.1.5 R/O Gauge (0..100) CPU usage ratio (5-second average) yshCpuUtil1min 1.3.6.1.4.1.1182.3.1.6 R/O Gauge (0..100) CPU usage ratio (1-minute average) yshCpuUtil5min 1.3.6.1.4.1.1182.3.1.7 R/O Gauge (0..100) CPU usage ratio (5-minute average) yshStackTable 1.3.6.1.4.1.1182.3.1.19 N/A Table of hardware information for each member switch + This can only be obtained when a stack is configured. yshStackEntry 1.3.6.1.4.1.1182.3.1.19.1 N/A INDEX * yshStackId yshStackId 1.3.6.1.4.1.1182.3.1.19.1.1 N/A INTEGER (1..2147483647) Stack ID yshStackMemorySize 1.3.6.1.4.1.1182.3.1.19.1.2 R/O INTEGER Memory size yshStackFlashROMSize 1.3.6.1.4.1.1182.3.1.19.1.3 R/O INTEGER FlashROM size yshStackMemoryUtil 1.3.6.1.4.1.1182.3.1.19.1.4 R/O Gauge (0..100) Memory usage ratio yshStackCpuUtil5sec 1.3.6.1.4.1.1182.3.1.19.1.5 R/O Gauge (0..100) CPU usage ratio (5-second average) yshStackCpuUtil1min 1.3.6.1.4.1.1182.3.1.19.1.6 R/O Gauge (0..100) CPU usage ratio (1-minute average) yshStackCpuUtil5min 1.3.6.1.4.1.1182.3.1.19.1.7 R/O Gauge (0..100) CPU usage ratio (5-minute average) yshEnableTemperatureTrap 1.3.6.1.4.1.1182.3.1.20 R/W INTEGER * enabled(1) * disabled(2) Setting value that determines whether SNMP traps based on temperature information are notified yshTemperatureTable 1.3.6.1.4.1.1182.3.1.21 N/A Temperature information table yshTemperatureEntry 1.3.6.1.4.1.1182.3.1.21.1 N/A INDEX * yshTemperatureStackId * yshTemperatureDeviceType * yshTemperatureDeviceIndex yshTemperatureStackId 1.3.6.1.4.1.1182.3.1.21.1.1 N/A INTEGER (1..2147483647) Stack ID This can be obtained with stack ID 1 if stack was not configured. yshTemperatureDeviceType 1.3.6.1.4.1.1182.3.1.21.1.2 N/A INTEGER * cpu(1) * phy(2) * sfp(3) * thermal-sensor(4) * pse(5) * mac(6) Device type yshTemperatureDeviceIndex 1.3.6.1.4.1.1182.3.1.21.1.3 N/A INTEGER (1..2147483647) Index for each device + For example, index values are 1 and 2 for devices with two CPUs yshTemperatureValue 1.3.6.1.4.1.1182.3.1.21.1.4 R/O Gauge Device temperature + If the device temperature was not measured, this is “0” yshTemperatureStatusTable 1.3.6.1.4.1.1182.3.1.22 N/A Temperature status table yshTemperatureStatusEntry 1.3.6.1.4.1.1182.3.1.22.1 N/A INDEX * yshTemperatureStatusStackId * yshTemperatureStatusDeviceType yshTemperatureStatusStackId 1.3.6.1.4.1.1182.3.1.22.1.1 N/A INTEGER (1..2147483647) Stack ID This can be obtained with stack ID 1 if stack was not configured. yshTemperatureStatusDeviceType 1.3.6.1.4.1.1182.3.1.22.1.2 N/A INTEGER * cpu(1) * phy(2) * sfp(3) * thermal-sensor(4) * pse(5) * mac(6) Device type yshTemperatureStatus 1.3.6.1.4.1.1182.3.1.22.1.3 R/O INTEGER * normal(1) * warning(2) * error(3) Temperature status * “Normal” when normal * “Warning” indicates temperature over High threshold value * “Error” indicates temperature exceeded alarm temperature yshTemperatureStatusNormalThreshold 1.3.6.1.4.1.1182.3.1.22.1.4 N/A Gauge Threshold value for determining Normal status Note: Only used for trap notifications yshTemperatureStatusWarningThreshold 1.3.6.1.4.1.1182.3.1.22.1.5 N/A Gauge Threshold value for determining Warning status Note: Only used for trap notifications yshTemperatureStatusErrorThreshold 1.3.6.1.4.1.1182.3.1.22.1.6 N/A Gauge Threshold value for determining Error status Note: Only used for trap notifications yshEnableFanTrap 1.3.6.1.4.1.1182.3.1.23 R/W INTEGER * enabled(1) * disabled(2) Setting value for determining whether SNMP traps based on fan information are notified yshFanTable 1.3.6.1.4.1.1182.3.1.24 N/A Fan information table yshFanEntry 1.3.6.1.4.1.1182.3.1.24.1 N/A INDEX * yshFanStackId * yshFanIndex yshFanStackId 1.3.6.1.4.1.1182.3.1.24.1.1 N/A INTEGER (1..2147483647) Stack ID This can be obtained with stack ID 1 if stack was not configured. yshFanIndex 1.3.6.1.4.1.1182.3.1.24.1.2 N/A INTEGER (1..2147483647) Index for each fan + For example, index values will be 1 and 2 for devices with two fans yshFanRpm 1.3.6.1.4.1.1182.3.1.24.1.3 R/O Gauge Fan RPM yshFanStatus 1.3.6.1.4.1.1182.3.1.24.1.4 R/O INTEGER * normal(1) * stopped(2) Fan status yshFanSpeedStatusTable 1.3.6.1.4.1.1182.3.1.25 N/A Fan RPM status table yshFanSpeedStatusEntry 1.3.6.1.4.1.1182.3.1.25.1 N/A INDEX * yshFanSpeedStatusStackId yshFanSpeedStatusStackId 1.3.6.1.4.1.1182.3.1.25.1.1 N/A INTEGER (1..2147483647) Stack ID This can be obtained with stack ID 1 if stack was not configured. yshFanSpeedStatus 1.3.6.1.4.1.1182.3.1.25.1.2 R/O INTEGER * low(1) * middle(2) * high(3) * max-speed(4) * middle-high(5) * high-alarm(6) Fan RPM status</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#yamahaswfirmwareグループ">5.2. yamahaSWFirmware group</div><div class="search_word">5.2. yamahaswfirmware group this mib is related to firmware information for yamaha switches. yamahaswfirmware group mib name oid access syntax description ysfconfigfile 1.3.6.1.4.1.1182.3.2.2 r/o displaystring (size (0..255)) startup config ysfrevision 1.3.6.1.4.1.1182.3.2.3 r/o displaystring (size (0..255)) firmware version ysfuptime 1.3.6.1.4.1.1182.3.2.4 r/o timeticks elapsed time from boot ysfrestart 1.3.6.1.4.1.1182.3.2.11 r/w integer * nothing(1) * restart(2) the system will reboot when the “restart” value is written ysfstacktable 1.3.6.1.4.1.1182.3.2.12 n/a table of firmware information for each member switch + this can only be obtained when a stack is configured. ysfstackentry 1.3.6.1.4.1.1182.3.2.12.1 n/a index * ysfstackid ysfstackid 1.3.6.1.4.1.1182.3.2.12.1.1 n/a integer (1..2147483647) stack id ysfstackuptime 1.3.6.1.4.1.1182.3.2.12.1.2 r/o timeticks elapsed time from boot</div><div class="display_word">5.2. yamahaSWFirmware group This MIB is related to firmware information for Yamaha switches. yamahaSWFirmware group MIB name OID Access Syntax Description ysfConfigFile 1.3.6.1.4.1.1182.3.2.2 R/O DisplayString (SIZE (0..255)) Startup config ysfRevision 1.3.6.1.4.1.1182.3.2.3 R/O DisplayString (SIZE (0..255)) Firmware version ysfUpTime 1.3.6.1.4.1.1182.3.2.4 R/O TimeTicks Elapsed time from boot ysfRestart 1.3.6.1.4.1.1182.3.2.11 R/W INTEGER * nothing(1) * restart(2) The system will reboot when the “restart” value is written ysfStackTable 1.3.6.1.4.1.1182.3.2.12 N/A Table of firmware information for each member switch + This can only be obtained when a stack is configured. ysfStackEntry 1.3.6.1.4.1.1182.3.2.12.1 N/A INDEX * ysfStackId ysfStackId 1.3.6.1.4.1.1182.3.2.12.1.1 N/A INTEGER (1..2147483647) Stack ID ysfStackUpTime 1.3.6.1.4.1.1182.3.2.12.1.2 R/O TimeTicks Elapsed time from boot</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#yamahaswl2msグループ">5.3. yamahaSWL2ms group</div><div class="search_word">5.3. yamahaswl2ms group this mib is related to l2ms information for yamaha network switches. yamahaswl2ms group mib name oid access syntax description ysl2msnumber 1.3.6.1.4.1.1182.3.5.1 n/a integer number of switches that can be recognized note: used only with trap notifications ysl2msenabletrap 1.3.6.1.4.1.1182.3.5.2 r/w integer * enabled(1) * disabled(2) setting value for determining whether snmp traps due to l2ms information are notified ysl2mstable 1.3.6.1.4.1.1182.3.5.3 n/a table of information for devices connected via l2ms ysl2msentry 1.3.6.1.4.1.1182.3.5.3.1 n/a index * ysl2msindex ysl2msindex 1.3.6.1.4.1.1182.3.5.3.1.1 n/a displaystring (size (0..6)) mac address of device note: used only with trap notifications ysl2msproduct 1.3.6.1.4.1.1182.3.5.3.1.2 n/a integer * generic(1) * swx2200-8g(2) * swx2200-24g(3) * swx2200-8poe(4) model of device note: used only with trap notifications ysl2msphysaddress 1.3.6.1.4.1.1182.3.5.3.1.5 n/a displaystring (size (0..6)) mac address of device note: used only with trap notifications ysl2msroute 1.3.6.1.4.1.1182.3.5.3.1.11 n/a displaystring (size (0..64)) route information to device note: used only with trap notifications</div><div class="display_word">5.3. yamahaSWL2ms group This MIB is related to L2MS information for Yamaha network switches. yamahaSWL2ms group MIB name OID Access Syntax Description ysl2msNumber 1.3.6.1.4.1.1182.3.5.1 N/A INTEGER Number of switches that can be recognized Note: Used only with trap notifications ysl2msEnableTrap 1.3.6.1.4.1.1182.3.5.2 R/W INTEGER * enabled(1) * disabled(2) Setting value for determining whether SNMP traps due to L2MS information are notified ysl2msTable 1.3.6.1.4.1.1182.3.5.3 N/A Table of information for devices connected via L2MS ysl2msEntry 1.3.6.1.4.1.1182.3.5.3.1 N/A INDEX * ysl2msIndex ysl2msIndex 1.3.6.1.4.1.1182.3.5.3.1.1 N/A DisplayString (SIZE (0..6)) MAC address of device Note: Used only with trap notifications ysl2msProduct 1.3.6.1.4.1.1182.3.5.3.1.2 N/A INTEGER * generic(1) * swx2200-8g(2) * swx2200-24g(3) * swx2200-8poe(4) Model of device Note: Used only with trap notifications ysl2msPhysAddress 1.3.6.1.4.1.1182.3.5.3.1.5 N/A DisplayString (SIZE (0..6)) MAC address of device Note: Used only with trap notifications ysl2msRoute 1.3.6.1.4.1.1182.3.5.3.1.11 N/A DisplayString (SIZE (0..64)) Route information to device Note: Used only with trap notifications</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#yamahaswerrdisableグループ">5.4. yamahaSWErrDisable group</div><div class="search_word">5.4. yamahaswerrdisable group this mib is related to error detection function information for yamaha network switches. yamahaswerrdisable group mib name oid access syntax description ysedconfigtable 1.3.6.1.4.1.1182.3.6.1 n/a table of setting information for the error detection function ysedconfigentry 1.3.6.1.4.1.1182.3.6.1.1 n/a index * ysedconfigindex ysedconfigindex 1.3.6.1.4.1.1182.3.6.1.1.1 n/a integer (1..2147483647) table index + corresponds to the ysedconfigfunction value ysedconfigfunction 1.3.6.1.4.1.1182.3.6.1.1.2 r/o integer * bpduguard(1) * loopdetect(2) functions that are enabled for error detection ysedconfigautorecovery 1.3.6.1.4.1.1182.3.6.1.1.3 r/w integer * enabled(1) * disabled(2) setting for automatic recovery from error disable state ysedconfigrecoveryinterval 1.3.6.1.4.1.1182.3.6.1.1.4 r/w integer (10..1000000) frequency (seconds) at which to attempt automatic recovery from error disable state ysedenabletrap 1.3.6.1.4.1.1182.3.6.2 r/w integer * enabled(1) * disabled(2) setting value for determining whether snmp traps due to error detection functions are notified ysediftable 1.3.6.1.4.1.1182.3.6.3 n/a table of information for the error detection function ysedifentry 1.3.6.1.4.1.1182.3.6.3.1 n/a index * ysedifindex ysedifindex 1.3.6.1.4.1.1182.3.6.3.1.1 n/a integer (1..2147483647) interface index ysedifstatus 1.3.6.1.4.1.1182.3.6.3.1.2 r/o integer * normal(1) * bpduguard(2) * loopdetect(3) * portsecurity(4) error disable state of port</div><div class="display_word">5.4. yamahaSWErrDisable group This MIB is related to error detection function information for Yamaha network switches. yamahaSWErrDisable group MIB name OID Access Syntax Description ysedConfigTable 1.3.6.1.4.1.1182.3.6.1 N/A Table of setting information for the error detection function ysedConfigEntry 1.3.6.1.4.1.1182.3.6.1.1 N/A INDEX * ysedConfigIndex ysedConfigIndex 1.3.6.1.4.1.1182.3.6.1.1.1 N/A INTEGER (1..2147483647) Table index + Corresponds to the ysedConfigFunction value ysedConfigFunction 1.3.6.1.4.1.1182.3.6.1.1.2 R/O INTEGER * bpduguard(1) * loopdetect(2) Functions that are enabled for error detection ysedConfigAutoRecovery 1.3.6.1.4.1.1182.3.6.1.1.3 R/W INTEGER * enabled(1) * disabled(2) Setting for automatic recovery from Error Disable state ysedConfigRecoveryInterval 1.3.6.1.4.1.1182.3.6.1.1.4 R/W INTEGER (10..1000000) Frequency (seconds) at which to attempt automatic recovery from Error Disable state ysedEnableTrap 1.3.6.1.4.1.1182.3.6.2 R/W INTEGER * enabled(1) * disabled(2) Setting value for determining whether SNMP traps due to error detection functions are notified ysedIfTable 1.3.6.1.4.1.1182.3.6.3 N/A Table of information for the error detection function ysedIfEntry 1.3.6.1.4.1.1182.3.6.3.1 N/A INDEX * ysedIfIndex ysedIfIndex 1.3.6.1.4.1.1182.3.6.3.1.1 N/A INTEGER (1..2147483647) Interface index ysedIfStatus 1.3.6.1.4.1.1182.3.6.3.1.2 R/O INTEGER * normal(1) * bpduguard(2) * loopdetect(3) * portsecurity(4) Error Disable state of port</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#yamahaswrmonグループ">5.5. yamahaSWRmon group</div><div class="search_word">5.5. yamahaswrmon group this mib is related to rmon information for yamaha network switches. yamahaswrmon group mib name oid access syntax description ysrmonsetting 1.3.6.1.4.1.1182.3.7.1 r/w integer * enabled(1) * disabled(2) enabled/disabled setting of rmon function ysrmonenabletrap 1.3.6.1.4.1.1182.3.7.2 r/w integer * enabled(1) * disabled(2) setting value for determining whether snmp traps due to rmon functions are notified</div><div class="display_word">5.5. yamahaSWRmon group This MIB is related to RMON information for Yamaha network switches. yamahaSWRmon group MIB name OID Access Syntax Description ysrmonSetting 1.3.6.1.4.1.1182.3.7.1 R/W INTEGER * enabled(1) * disabled(2) Enabled/disabled setting of RMON function ysrmonEnableTrap 1.3.6.1.4.1.1182.3.7.2 R/W INTEGER * enabled(1) * disabled(2) Setting value for determining whether SNMP traps due to RMON functions are notified</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#yamahaswtermmonグループ">5.6. yamahaSWTermMon group</div><div class="search_word">5.6. yamahaswtermmon group this mib is related to terminal monitoring information for yamaha network switches. yamahaswtermmon group mib name oid access syntax description ystmenabletrap 1.3.6.1.4.1.1182.3.8.1 r/w integer * enabled(1) * disabled(2) setting value for determining whether snmp traps due to terminal monitoring functions are notified ystmiftermtable 1.3.6.1.4.1.1182.3.8.3 n/a table of terminal monitoring functions targeted at ports ystmiftermentry 1.3.6.1.4.1.1182.3.8.3.1 n/a index * ystmiftermindex ystmiftermindex 1.3.6.1.4.1.1182.3.8.3.1.1 n/a integer (1..2147483647) ifindex note: used only with trap notifications ystmiftermdescr 1.3.6.1.4.1.1182.3.8.3.1.2 n/a displaystring (size (0..255)) terminal monitoring description note: used only with trap notifications ystmiftermstatus 1.3.6.1.4.1.1182.3.8.3.1.3 n/a integer * up(1) * down(2) * idle(3) terminal monitoring status note: used only with trap notifications ystmiptermtable 1.3.6.1.4.1.1182.3.8.4 n/a table of terminal monitoring functions targeted at ip addresses ystmiptermentry 1.3.6.1.4.1.1182.3.8.4.1 n/a index ystmiptermindex ystmiptermindex 1.3.6.1.4.1.1182.3.8.4.1.1 n/a ipaddress ip address of monitored target note: used only with trap notifications ystmiptermdescr 1.3.6.1.4.1.1182.3.8.4.1.2 n/a displaystring (size (0..255)) terminal monitoring description note: used only with trap notifications ystmiptermstatus 1.3.6.1.4.1.1182.3.8.4.1.3 n/a integer * up(1) * down(2) * idle(3) terminal monitoring status note: used only with trap notifications</div><div class="display_word">5.6. yamahaSWTermMon group This MIB is related to terminal monitoring information for Yamaha network switches. yamahaSWTermMon group MIB name OID Access Syntax Description ystmEnableTrap 1.3.6.1.4.1.1182.3.8.1 R/W INTEGER * enabled(1) * disabled(2) Setting value for determining whether SNMP traps due to terminal monitoring functions are notified ystmIfTermTable 1.3.6.1.4.1.1182.3.8.3 N/A Table of terminal monitoring functions targeted at ports ystmIfTermEntry 1.3.6.1.4.1.1182.3.8.3.1 N/A INDEX * ystmIfTermIndex ystmIfTermIndex 1.3.6.1.4.1.1182.3.8.3.1.1 N/A INTEGER (1..2147483647) ifIndex Note: Used only with trap notifications ystmIfTermDescr 1.3.6.1.4.1.1182.3.8.3.1.2 N/A DisplayString (SIZE (0..255)) Terminal monitoring description Note: Used only with trap notifications ystmIfTermStatus 1.3.6.1.4.1.1182.3.8.3.1.3 N/A INTEGER * up(1) * down(2) * idle(3) Terminal monitoring status Note: Used only with trap notifications ystmIpTermTable 1.3.6.1.4.1.1182.3.8.4 N/A Table of terminal monitoring functions targeted at IP addresses ystmIpTermEntry 1.3.6.1.4.1.1182.3.8.4.1 N/A INDEX ystmIpTermIndex ystmIpTermIndex 1.3.6.1.4.1.1182.3.8.4.1.1 N/A IpAddress IP address of monitored target Note: Used only with trap notifications ystmIpTermDescr 1.3.6.1.4.1.1182.3.8.4.1.2 N/A DisplayString (SIZE (0..255)) Terminal monitoring description Note: Used only with trap notifications ystmIpTermStatus 1.3.6.1.4.1.1182.3.8.4.1.3 N/A INTEGER * up(1) * down(2) * idle(3) Terminal monitoring status Note: Used only with trap notifications</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#yamahaswbridgeグループ">5.7. yamahaSWBridge group</div><div class="search_word">5.7. yamahaswbridge group this mib is related to dot1dbridge information on yamaha network switches. yamahaswbridge group mib name oid access syntax description ysbridgeenabletrap 1.3.6.1.4.1.1182.3.9.1 r/w integer * enabled(1) * disabled(2) setting value for determining whether snmp traps due to dot1dbridge information are notified</div><div class="display_word">5.7. yamahaSWBridge group This MIB is related to dot1dBridge information on Yamaha network switches. yamahaSWBridge group MIB name OID Access Syntax Description ysbridgeEnableTrap 1.3.6.1.4.1.1182.3.9.1 R/W INTEGER * enabled(1) * disabled(2) Setting value for determining whether SNMP traps due to dot1dBridge information are notified</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#yamahaswpowerethernetグループ">5.8. yamahaSWPowerEthernet group</div><div class="search_word">5.8. yamahaswpowerethernet group this mib is related to poe information for yamaha switches. yamahaswpowerethernet group mib name oid access syntax description yspeenabletrap 1.3.6.1.4.1.1182.3.10.1 r/w integer * enabled(1) * disabled(2) setting value for determining whether snmp traps due to poe information are notified yspeunitsupplysetting 1.3.6.1.4.1.1182.3.10.2 r/w integer * enabled(1) * disabled(2) enables/disables the power supply function yspeunittable 1.3.6.1.4.1.1182.3.10.3 n/a table of device poe information yspeunitentry 1.3.6.1.4.1.1182.3.10.3.1 n/a index * yspeunitstackid yspeunitstackid 1.3.6.1.4.1.1182.3.10.3.1.1 n/a integer (1..2147483647) stack id this can be obtained with stack id 1 if stack was not configured. yspeunitsupplypower 1.3.6.1.4.1.1182.3.10.3.1.2 r/o gauge32 power supply for the entire device yspeunitpowerfailure 1.3.6.1.4.1.1182.3.10.3.1.3 r/o integer * normal(1) * failure(2) device power supply error yspeunitguardbandstatus 1.3.6.1.4.1.1182.3.10.3.1.4 r/o integer * not_operating(1) * operating(2) guard band status not_operating(1): not operating state where the available power supply is greater than the guard band, and the guard band does not limit the power supply operating(2): operating state where the available power supply is smaller than the guard band, and the guard band limits the power supply yspeunitguardbandvalue 1.3.6.1.4.1.1182.3.10.3.1.5 r/w gauge32 (0..90000) guard band value (mw) yspeporttable 1.3.6.1.4.1.1182.3.10.4 n/a table of port information for poe yspeportentry 1.3.6.1.4.1.1182.3.10.4.1 n/a index * yspeportstackid * yspeportindex yspeportstackid 1.3.6.1.4.1.1182.3.10.4.1.1 n/a integer (1..2147483647) stack id this can be obtained with stack id 1 if stack was not configured. yspeportindex 1.3.6.1.4.1.1182.3.10.4.1.2 n/a integer (1..2147483647) port index for power supply port. port numbers are used yspeportdescr 1.3.6.1.4.1.1182.3.10.4.1.3 r/w displaystring (size (0..64)) description about power supply port + setting value of the power-inline description command yspeportsupplysetting 1.3.6.1.4.1.1182.3.10.4.1.4 r/w integer * enabled(1) * disabled(2) enables/disables the power supply function yspeportdetectclass 1.3.6.1.4.1.1182.3.10.4.1.5 r/o integer * na(1) * class0(2) * class1(3) * class2(4) * class3(5) * class4(6) * class5(7) * class6(8) * class7(9) * class8(10) power supply class information for connected devices yspeportsupplystate 1.3.6.1.4.1.1182.3.10.4.1.6 r/o integer * none(1) * supply-class0(2) * supply-class1(3) * supply-class2(4) * supply-class3(5) * supply-class4(6) * terminate(7) * overcurrent(8) * forced-terminate(9) * over-supply(10) * over-temp(11) * fanlock(12) * power-failure(13) * class-failure(14) * over-guardband(15) * pd-failure(16) * guardband-restrict(17) * supply-class5(18) * supply-class6(19) * supply-class7(20) * supply-class8(21) port power supply status * if the power supply function of the port is enabled and no poe device is connected, this value is terminate(7) * if the power supply function of the port is disabled, this value is none(1) yspeportsupplypower 1.3.6.1.4.1.1182.3.10.4.1.7 r/o gauge32 port power consumption (mw) yspeportpowerpriority 1.3.6.1.4.1.1182.3.10.4.1.8 r/w integer * critical(1) * high(2) * low(3) port power supply priority order</div><div class="display_word">5.8. yamahaSWPowerEthernet group This MIB is related to PoE information for Yamaha switches. yamahaSWPowerEthernet group MIB name OID Access Syntax Description yspeEnableTrap 1.3.6.1.4.1.1182.3.10.1 R/W INTEGER * enabled(1) * disabled(2) Setting value for determining whether SNMP traps due to PoE information are notified yspeUnitSupplySetting 1.3.6.1.4.1.1182.3.10.2 R/W INTEGER * enabled(1) * disabled(2) Enables/disables the power supply function yspeUnitTable 1.3.6.1.4.1.1182.3.10.3 N/A Table of device PoE information yspeUnitEntry 1.3.6.1.4.1.1182.3.10.3.1 N/A INDEX * yspeUnitStackId yspeUnitStackId 1.3.6.1.4.1.1182.3.10.3.1.1 N/A INTEGER (1..2147483647) Stack ID This can be obtained with stack ID 1 if stack was not configured. yspeUnitSupplyPower 1.3.6.1.4.1.1182.3.10.3.1.2 R/O Gauge32 Power supply for the entire device yspeUnitPowerFailure 1.3.6.1.4.1.1182.3.10.3.1.3 R/O INTEGER * normal(1) * failure(2) Device power supply error yspeUnitGuardBandStatus 1.3.6.1.4.1.1182.3.10.3.1.4 R/O INTEGER * not_operating(1) * operating(2) Guard band status not_operating(1): Not operating State where the available power supply is greater than the guard band, and the guard band does not limit the power supply operating(2): Operating State where the available power supply is smaller than the guard band, and the guard band limits the power supply yspeUnitGuardBandValue 1.3.6.1.4.1.1182.3.10.3.1.5 R/W Gauge32 (0..90000) Guard band value (mW) yspePortTable 1.3.6.1.4.1.1182.3.10.4 N/A Table of port information for PoE yspePortEntry 1.3.6.1.4.1.1182.3.10.4.1 N/A INDEX * yspePortStackId * yspePortIndex yspePortStackId 1.3.6.1.4.1.1182.3.10.4.1.1 N/A INTEGER (1..2147483647) Stack ID This can be obtained with stack ID 1 if stack was not configured. yspePortIndex 1.3.6.1.4.1.1182.3.10.4.1.2 N/A INTEGER (1..2147483647) Port index for power supply port. Port numbers are used yspePortDescr 1.3.6.1.4.1.1182.3.10.4.1.3 R/W DisplayString (SIZE (0..64)) Description about power supply port + Setting value of the power-inline description command yspePortSupplySetting 1.3.6.1.4.1.1182.3.10.4.1.4 R/W INTEGER * enabled(1) * disabled(2) Enables/disables the power supply function yspePortDetectClass 1.3.6.1.4.1.1182.3.10.4.1.5 R/O INTEGER * na(1) * class0(2) * class1(3) * class2(4) * class3(5) * class4(6) * class5(7) * class6(8) * class7(9) * class8(10) Power supply class information for connected devices yspePortSupplyState 1.3.6.1.4.1.1182.3.10.4.1.6 R/O INTEGER * none(1) * supply-class0(2) * supply-class1(3) * supply-class2(4) * supply-class3(5) * supply-class4(6) * terminate(7) * overcurrent(8) * forced-terminate(9) * over-supply(10) * over-temp(11) * fanlock(12) * power-failure(13) * class-failure(14) * over-guardband(15) * pd-failure(16) * guardband-restrict(17) * supply-class5(18) * supply-class6(19) * supply-class7(20) * supply-class8(21) Port power supply status * If the power supply function of the port is enabled and no PoE device is connected, this value is terminate(7) * If the power supply function of the port is disabled, this value is none(1) yspePortSupplyPower 1.3.6.1.4.1.1182.3.10.4.1.7 R/O Gauge32 Port power consumption (mW) yspePortPowerPriority 1.3.6.1.4.1.1182.3.10.4.1.8 R/W INTEGER * critical(1) * high(2) * low(3) Port power supply priority order</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#yamahaswloopdetectグループ">5.9. yamahaSWLoopDetect group</div><div class="search_word">5.9. yamahaswloopdetect group this mib is related to loop detection information for yamaha switches. yamahaswloopdetect group mib name oid access syntax description ysldenabletrap 1.3.6.1.4.1.1182.3.11.1 r/w integer * enabled(1) * disabled(2) whether or not trap sends notification ysldsystemadmin 1.3.6.1.4.1.1182.3.11.2 r/w integer * enabled(1) * disabled(2) enables/disables loop detection for the entire system ysldsystemblockingrecoveryinterval 1.3.6.1.4.1.1182.3.11.6 r/w integer (0｜10..3600) time (seconds) for a blocked interface to be automatically restored after resolving a loop ysldsystemstatusreset 1.3.6.1.4.1.1182.3.11.7 r/w integer * nothing(1) * reset(2) reset the loop detection status ysldporttable 1.3.6.1.4.1.1182.3.11.8 n/a table of loop detection information for each port ysldportentry 1.3.6.1.4.1.1182.3.11.8.1 n/a index * ysldportstackid * ysldportindex ysldportstackid 1.3.6.1.4.1.1182.3.11.8.1.1 n/a integer (1..2147483647) stack id this can be obtained with stack id 1 if stack was not configured. ysldportindex 1.3.6.1.4.1.1182.3.11.8.1.2 n/a integer (1..2147483647) port number ysldportadmin 1.3.6.1.4.1.1182.3.11.8.1.3 r/w integer * enabled(1) * disabled(2) enables/disables loop detection at ports ysldportstatus 1.3.6.1.4.1.1182.3.11.8.1.4 r/o integer * disabled(1) * normal(2) * detected(3) * blocked(4) * shutdown(5) loop detection status * disabled(1): the loop detection function is disabled * normal(2): no loop is detected * detected(3): a loop is detected * blocked(4): a loop is detected and the port is blocked * shutdown(5): a loop is detected, so the port is shut down ysldportblocking 1.3.6.1.4.1.1182.3.11.8.1.5 r/w integer * enabled(1) * disabled(2) sets whether or not to block port if a loop occurs ysldlagtable 1.3.6.1.4.1.1182.3.11.9 n/a table of logical interface loop detection information for each link aggregation ysldlagentry 1.3.6.1.4.1.1182.3.11.9.1 n/a index * ysldlagindex ysldlagindex 1.3.6.1.4.1.1182.3.11.9.1.1 n/a integer (1..2147483647) ifindex for link aggregation logical interface ysldlagadmin 1.3.6.1.4.1.1182.3.11.9.1.2 r/w integer * enabled(1) * disabled(2) loop detection for link aggregation logical interface enabled/disabled ysldlagstatus 1.3.6.1.4.1.1182.3.11.9.1.3 r/o integer * disabled(1) * normal(2) * detected(3) * blocked(4) * shutdown(5) loop detection status * disabled(1): the loop detection function is disabled * normal(2): no loop is detected * detected(3): a loop is detected * blocked(4): a loop is detected and the logical interface is blocked * shutdown(5): a loop is detected and the logical interface is shut down ysldlagblocking 1.3.6.1.4.1.1182.3.11.9.1.4 r/w integer * enabled(1) * disabled(2) sets whether or not to block the logical interface if a loop occurs</div><div class="display_word">5.9. yamahaSWLoopDetect group This MIB is related to loop detection information for Yamaha switches. yamahaSWLoopDetect group MIB name OID Access Syntax Description ysldEnableTrap 1.3.6.1.4.1.1182.3.11.1 R/W INTEGER * enabled(1) * disabled(2) Whether or not trap sends notification ysldSystemAdmin 1.3.6.1.4.1.1182.3.11.2 R/W INTEGER * enabled(1) * disabled(2) Enables/disables loop detection for the entire system ysldSystemBlockingRecoveryInterval 1.3.6.1.4.1.1182.3.11.6 R/W INTEGER (0｜10..3600) Time (seconds) for a blocked interface to be automatically restored after resolving a loop ysldSystemStatusReset 1.3.6.1.4.1.1182.3.11.7 R/W INTEGER * nothing(1) * reset(2) Reset the loop detection status ysldPortTable 1.3.6.1.4.1.1182.3.11.8 N/A Table of loop detection information for each port ysldPortEntry 1.3.6.1.4.1.1182.3.11.8.1 N/A INDEX * ysldPortStackId * ysldPortIndex ysldPortStackId 1.3.6.1.4.1.1182.3.11.8.1.1 N/A INTEGER (1..2147483647) Stack ID This can be obtained with stack ID 1 if stack was not configured. ysldPortIndex 1.3.6.1.4.1.1182.3.11.8.1.2 N/A INTEGER (1..2147483647) Port number ysldPortAdmin 1.3.6.1.4.1.1182.3.11.8.1.3 R/W INTEGER * enabled(1) * disabled(2) Enables/disables loop detection at ports ysldPortStatus 1.3.6.1.4.1.1182.3.11.8.1.4 R/O INTEGER * disabled(1) * normal(2) * detected(3) * blocked(4) * shutdown(5) Loop detection status * disabled(1): The loop detection function is disabled * normal(2): No loop is detected * detected(3): A loop is detected * blocked(4): A loop is detected and the port is blocked * shutdown(5): A loop is detected, so the port is shut down ysldPortBlocking 1.3.6.1.4.1.1182.3.11.8.1.5 R/W INTEGER * enabled(1) * disabled(2) Sets whether or not to block port if a loop occurs ysldLagTable 1.3.6.1.4.1.1182.3.11.9 N/A Table of logical interface loop detection information for each link aggregation ysldLagEntry 1.3.6.1.4.1.1182.3.11.9.1 N/A INDEX * ysldLagIndex ysldLagIndex 1.3.6.1.4.1.1182.3.11.9.1.1 N/A INTEGER (1..2147483647) ifIndex for link aggregation logical interface ysldLagAdmin 1.3.6.1.4.1.1182.3.11.9.1.2 R/W INTEGER * enabled(1) * disabled(2) Loop detection for link aggregation logical interface enabled/disabled ysldLagStatus 1.3.6.1.4.1.1182.3.11.9.1.3 R/O INTEGER * disabled(1) * normal(2) * detected(3) * blocked(4) * shutdown(5) Loop detection status * disabled(1): The loop detection function is disabled * normal(2): No loop is detected * detected(3): A loop is detected * blocked(4): A loop is detected and the logical interface is blocked * shutdown(5): A loop is detected and the logical interface is shut down ysldLagBlocking 1.3.6.1.4.1.1182.3.11.9.1.4 R/W INTEGER * enabled(1) * disabled(2) Sets whether or not to block the logical interface if a loop occurs</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#標準mibトラップ">6. Standard MIB Traps</div><div class="search_word">6. standard mib traps standard mib traps that are supported by this product are shown below.</div><div class="display_word">6. Standard MIB Traps Standard MIB traps that are supported by this product are shown below.</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#rfc1157で規定されているトラップ">6.1. Traps defined by RFC1157</div><div class="search_word">6.1. traps defined by rfc1157 these are traps defined by rfc1157. trap name oid additional information for trap (variable-bindings) description coldstart 1.3.6.1.6.3.1.1.5.1 none notification on power off/on and during firmware updates warmstart 1.3.6.1.6.3.1.1.5.2 none notification while the reload command is being executed linkdown 1.3.6.1.6.3.1.1.5.3 ifindex ifadminstatus ifoperstatus notification during linkdown linkup 1.3.6.1.6.3.1.1.5.4 ifindex ifadminstatus ifoperstatus notification during linkup authenticationfailure 1.3.6.1.6.3.1.1.5.5 none notification when receiving an snmp message that has an incorrect community name</div><div class="display_word">6.1. Traps defined by RFC1157 These are traps defined by RFC1157. Trap name OID Additional information for trap (variable-bindings) Description coldStart 1.3.6.1.6.3.1.1.5.1 None Notification on power OFF/ON and during firmware updates warmStart 1.3.6.1.6.3.1.1.5.2 None Notification while the reload command is being executed linkDown 1.3.6.1.6.3.1.1.5.3 ifIndex ifAdminStatus ifOperStatus Notification during linkdown linkUp 1.3.6.1.6.3.1.1.5.4 ifIndex ifAdminStatus ifOperStatus Notification during linkup authenticationFailure 1.3.6.1.6.3.1.1.5.5 None Notification when receiving an SNMP message that has an incorrect community name</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#rmonグループのトラップ">6.2. rmon group trap</div><div class="search_word">6.2. rmon group trap this trap is related to rmon information. trap name oid additional information for trap (variable-bindings) description risingalarm 1.3.6.1.2.1.16.0.1 alarmindex alarmvariable alarmsampletype alarmvalue alarmrisingthreshold notification that upper threshold value has been exceeded fallingalarm 1.3.6.1.2.1.16.0.2 alarmindex alarmvariable alarmsampletype alarmvalue alarmfallingthreshold notification that lower threshold value has been exceeded</div><div class="display_word">6.2. rmon group trap This trap is related to RMON information. Trap name OID Additional information for trap (variable-bindings) Description risingAlarm 1.3.6.1.2.1.16.0.1 alarmIndex alarmVariable alarmSampleType alarmValue alarmRisingThreshold Notification that upper threshold value has been exceeded fallingAlarm 1.3.6.1.2.1.16.0.2 alarmIndex alarmVariable alarmSampleType alarmValue alarmFallingThreshold Notification that lower threshold value has been exceeded</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#dot1dbridgeグループのトラップ">6.3. dot1dBridge group trap</div><div class="search_word">6.3. dot1dbridge group trap this trap is related to dot1dbridge information. trap name oid additional information for trap (variable-bindings) description newroot 1.3.6.1.2.1.17.0.1 none notification that a new root for bridge has been detected topologychange 1.3.6.1.2.1.17.0.2 none notification that a change in topology has been detected</div><div class="display_word">6.3. dot1dBridge group trap This trap is related to dot1dBridge information. Trap name OID Additional information for trap (variable-bindings) Description newRoot 1.3.6.1.2.1.17.0.1 None Notification that a new root for bridge has been detected topologyChange 1.3.6.1.2.1.17.0.2 None Notification that a change in topology has been detected</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#powerethernetmibグループのトラップ">6.4. powerEthernetMIB group trap</div><div class="search_word">6.4. powerethernetmib group trap this trap is related to poe information. trap name oid additional information for trap (variable-bindings) description pethpseportonoffnotification 1.3.6.1.2.1.105.0.1 pethpseportdetectionstatus notification that the poe port status has changed pethmainpowerusageonnotification 1.3.6.1.2.1.105.0.2 pethmainpseconsumptionpower notification that the power consumption goes from below the threshold value to on or above the threshold value + pethmainpseusagethreshold is used as the threshold value pethmainpowerusageoffnotification 1.3.6.1.2.1.105.0.3 pethmainpseconsumptionpower notification that the power consumption goes from on or above the threshold value to below the threshold value + pethmainpseusagethreshold is used as the threshold value</div><div class="display_word">6.4. powerEthernetMIB group trap This trap is related to PoE information. Trap name OID Additional information for trap (variable-bindings) Description pethPsePortOnOffNotification 1.3.6.1.2.1.105.0.1 pethPsePortDetectionStatus Notification that the PoE port status has changed pethMainPowerUsageOnNotification 1.3.6.1.2.1.105.0.2 pethMainPseConsumptionPower Notification that the power consumption goes from below the threshold value to on or above the threshold value + pethMainPseUsageThreshold is used as the threshold value pethMainPowerUsageOffNotification 1.3.6.1.2.1.105.0.3 pethMainPseConsumptionPower Notification that the power consumption goes from on or above the threshold value to below the threshold value + pethMainPseUsageThreshold is used as the threshold value</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#プライベートmibトラップ">7. Private MIB Traps</div><div class="search_word">7. private mib traps the private mib traps that are supported by this product are shown below.</div><div class="display_word">7. Private MIB Traps The private MIB traps that are supported by this product are shown below.</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#yamahaswhardwareグループのトラップ">7.1. yamahaSWHardware group trap</div><div class="search_word">7.1. yamahaswhardware group trap this trap is related to hardware information for yamaha switches. trap name oid additional information for trap (variable-bindings) description yshtemperaturestatusnormaltrap 1.3.6.1.4.1.1182.3.1.0.5 yshtemperaturestatusstackid yshtemperaturestatusdevicetype yshtemperaturestatus yshtemperaturestatusnormalthreshold yshtemperaturevalue notification when temperature status returns to “normal” yshtemperaturestatuswarningtrap 1.3.6.1.4.1.1182.3.1.0.6 yshtemperaturestatusstackid yshtemperaturestatusdevicetype yshtemperaturestatus yshtemperaturestatuswarningthreshold yshtemperaturevalue notification when temperature status changes to “warning” yshtemperaturestatuserrortrap 1.3.6.1.4.1.1182.3.1.0.7 yshtemperaturestatusstackid yshtemperaturestatusdevicetype yshtemperaturestatus yshtemperaturestatuserrorthreshold yshtemperaturevalue notification when temperature status changes to “error” yshfanstoppedtrap 1.3.6.1.4.1.1182.3.1.0.8 yshfanstackid yshfanindex notification when fan stops yshfanspeeduptrap 1.3.6.1.4.1.1182.3.1.0.9 yshfanspeedstatusstackid yshfanspeedstatus notification when fan rpm increases (when rpm reaches the “high” value) yshfanspeeddowntrap 1.3.6.1.4.1.1182.3.1.0.10 yshfanspeedstatusstackid yshfanspeedstatus notification when fan rpm decreases (when “high” rpm status is canceled) yshtemperaturesensorinvalidtrap 1.3.6.1.4.1.1182.3.1.0.13 yshtemperaturestatusstackid notification that a thermal sensor abnormality has occurred</div><div class="display_word">7.1. yamahaSWHardware group trap This trap is related to hardware information for Yamaha switches. Trap name OID Additional information for trap (variable-bindings) Description yshTemperatureStatusNormalTrap 1.3.6.1.4.1.1182.3.1.0.5 yshTemperatureStatusStackId yshTemperatureStatusDeviceType yshTemperatureStatus yshTemperatureStatusNormalThreshold yshTemperatureValue Notification when temperature status returns to “Normal” yshTemperatureStatusWarningTrap 1.3.6.1.4.1.1182.3.1.0.6 yshTemperatureStatusStackId yshTemperatureStatusDeviceType yshTemperatureStatus yshTemperatureStatusWarningThreshold yshTemperatureValue Notification when temperature status changes to “Warning” yshTemperatureStatusErrorTrap 1.3.6.1.4.1.1182.3.1.0.7 yshTemperatureStatusStackId yshTemperatureStatusDeviceType yshTemperatureStatus yshTemperatureStatusErrorThreshold yshTemperatureValue Notification when temperature status changes to “Error” yshFanStoppedTrap 1.3.6.1.4.1.1182.3.1.0.8 yshFanStackId yshFanIndex Notification when fan stops yshFanSpeedUpTrap 1.3.6.1.4.1.1182.3.1.0.9 yshFanSpeedStatusStackId yshFanSpeedStatus Notification when fan RPM increases (when RPM reaches the “High” value) yshFanSpeedDownTrap 1.3.6.1.4.1.1182.3.1.0.10 yshFanSpeedStatusStackId yshFanSpeedStatus Notification when fan RPM decreases (when “High” RPM status is canceled) yshTemperatureSensorInvalidTrap 1.3.6.1.4.1.1182.3.1.0.13 yshTemperatureStatusStackId Notification that a thermal sensor abnormality has occurred</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#yamahaswl2msグループのトラップ">7.2. yamahaSWL2ms group trap</div><div class="search_word">7.2. yamahaswl2ms group trap this trap is related to l2ms information for yamaha network switches. trap name oid additional information for trap (variable-bindings) description ysl2msfindagent 1.3.6.1.4.1.1182.3.5.0.1 ysl2msnumber ysl2msproduct ysl2msphysaddress ysl2msroute notification sent when l2ms agent is detected ysl2msdetectdown 1.3.6.1.4.1.1182.3.5.0.2 ysl2msnumber ysl2msproduct ysl2msphysaddress ysl2msroute notification sent when l2ms agent is lost</div><div class="display_word">7.2. yamahaSWL2ms group trap This trap is related to L2MS information for Yamaha network switches. Trap name OID Additional information for trap (variable-bindings) Description ysl2msFindAgent 1.3.6.1.4.1.1182.3.5.0.1 ysl2msNumber ysl2msProduct ysl2msPhysAddress ysl2msRoute Notification sent when L2MS agent is detected ysl2msDetectDown 1.3.6.1.4.1.1182.3.5.0.2 ysl2msNumber ysl2msProduct ysl2msPhysAddress ysl2msRoute Notification sent when L2MS agent is lost</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#yamahaswerrdisableグループのトラップ">7.3. yamahaSWErrDisable group trap</div><div class="search_word">7.3. yamahaswerrdisable group trap this trap is related to error detection function information for yamaha network switches. trap name oid additional information for trap (variable-bindings) description ysedtrap 1.3.6.1.4.1.1182.3.6.0.1 ysedifstatus notification when errordisable is detected/cancelled</div><div class="display_word">7.3. yamahaSWErrDisable group trap This trap is related to error detection function information for Yamaha network switches. Trap name OID Additional information for trap (variable-bindings) Description ysedTrap 1.3.6.1.4.1.1182.3.6.0.1 ysedIfStatus Notification when ErrorDisable is detected/cancelled</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#yamahaswtermmonグループのトラップ">7.4. yamahaSWTermMon group trap</div><div class="search_word">7.4. yamahaswtermmon group trap this trap is related to terminal monitoring information for yamaha network switches. trap name oid additional information for trap (variable-bindings) description ystmiftermtrap 1.3.6.1.4.1.1182.3.8.0.1 ystmiftermdescr ystmiftermstatus notification when terminal monitoring is detected ystmiptermtrap 1.3.6.1.4.1.1182.3.8.0.2 ystmiptermdescr ystmiptermstatus notification when ip address terminal monitoring is detected</div><div class="display_word">7.4. yamahaSWTermMon group trap This trap is related to terminal monitoring information for Yamaha network switches. Trap name OID Additional information for trap (variable-bindings) Description ystmIfTermTrap 1.3.6.1.4.1.1182.3.8.0.1 ystmIfTermDescr ystmIfTermStatus Notification when terminal monitoring is detected ystmIpTermTrap 1.3.6.1.4.1.1182.3.8.0.2 ystmIpTermDescr ystmIpTermStatus Notification when IP address terminal monitoring is detected</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#yamahaswpowerethernetグループのトラップ">7.5. yamahaSWPowerEthernet group trap</div><div class="search_word">7.5. yamahaswpowerethernet group trap this trap is related to poe information for yamaha switches. trap name oid additional information for trap (variable-bindings) description yspesupplyporttrap 1.3.6.1.4.1.1182.3.10.0.1 yspeportstackid yspeportindex yspeportdescr yspeportsupplystate notification that the power supply to the poe device has started yspeterminateporttrap 1.3.6.1.4.1.1182.3.10.0.2 yspeportstackid yspeportindex yspeportdescr yspeportsupplystate notification that the power supply to the poe device has stopped yspeguardbandstatetrap 1.3.6.1.4.1.1182.3.10.0.3 yspeunitstackid yspeunitsupplypower yspeunitguardbandstatus yspeunitguardbandvalue notification when the guard band status changes yspeporterrortrap 1.3.6.1.4.1.1182.3.10.0.4 yspeportstackid yspeportindex yspeportdescr yspeportsupplystate notification that a poe port error has been detected or resolved yspeunitfailuretrap 1.3.6.1.4.1.1182.3.10.0.5 yspeunitstackid yspeunitpowerfailure notification that a poe unit power supply abnormality has been detected</div><div class="display_word">7.5. yamahaSWPowerEthernet group trap This trap is related to PoE information for Yamaha switches. Trap name OID Additional information for trap (variable-bindings) Description yspeSupplyPortTrap 1.3.6.1.4.1.1182.3.10.0.1 yspePortStackId yspePortIndex yspePortDescr yspePortSupplyState Notification that the power supply to the PoE device has started yspeTerminatePortTrap 1.3.6.1.4.1.1182.3.10.0.2 yspePortStackId yspePortIndex yspePortDescr yspePortSupplyState Notification that the power supply to the PoE device has stopped yspeGuardBandStateTrap 1.3.6.1.4.1.1182.3.10.0.3 yspeUnitStackId yspeUnitSupplyPower yspeUnitGuardBandStatus yspeUnitGuardBandValue Notification when the guard band status changes yspePortErrorTrap 1.3.6.1.4.1.1182.3.10.0.4 yspePortStackId yspePortIndex yspePortDescr yspePortSupplyState Notification that a PoE port error has been detected or resolved yspeUnitFailureTrap 1.3.6.1.4.1.1182.3.10.0.5 yspeUnitStackId yspeUnitPowerFailure Notification that a PoE unit power supply abnormality has been detected</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#yamahaswloopdetectグループのトラップ">7.6. yamahaSWLoopDetect group trap</div><div class="search_word">7.6. yamahaswloopdetect group trap this trap is related to loop detection information for yamaha switches. trap name oid additional information for trap (variable-bindings) description ysldportdetectlooptrap 1.3.6.1.4.1.1182.3.11.0.1 ysldportstackid ysldportindex ysldportstatus sends notification when a loop is detected at a port ysldportresolvelooptrap 1.3.6.1.4.1.1182.3.11.0.2 ysldportstackid ysldportindex ysldportstatus sends notification when loop is resolved ysldlagdetectlooptrap 1.3.6.1.4.1.1182.3.11.0.3 ysldlagindex ysldlagstatus sends notification if loop is detected at a link aggregation logical interface ysldlagresolvelooptrap 1.3.6.1.4.1.1182.3.11.0.4 ysldlagindex ysldlagstatus sends notification when a loop is resolved at a link aggregation logical interface</div><div class="display_word">7.6. yamahaSWLoopDetect group trap This trap is related to loop detection information for Yamaha switches. Trap name OID Additional information for trap (variable-bindings) Description ysldPortDetectLoopTrap 1.3.6.1.4.1.1182.3.11.0.1 ysldPortStackId ysldPortIndex ysldPortStatus Sends notification when a loop is detected at a port ysldPortResolveLoopTrap 1.3.6.1.4.1.1182.3.11.0.2 ysldPortStackId ysldPortIndex ysldPortStatus Sends notification when loop is resolved ysldLagDetectLoopTrap 1.3.6.1.4.1.1182.3.11.0.3 ysldLagIndex ysldLagStatus Sends notification if loop is detected at a link aggregation logical interface ysldLagResolveLoopTrap 1.3.6.1.4.1.1182.3.11.0.4 ysldLagIndex ysldLagStatus Sends notification when a loop is resolved at a link aggregation logical interface</div></div><div id="other_other_snmp_mib"><div class="search_title" docfname="other_other_snmp_mib" doctitle="SNMP" link="#注意事項">8. Points of Caution</div><div class="search_word">8. points of caution the 64-bit counter mib can be read and written by snmpv2c and snmpv3 requests. those mibs cannot be read or written by snmpv1 requests.</div><div class="display_word">8. Points of Caution The 64-bit counter MIB can be read and written by SNMPv2c and SNMPv3 requests. Those MIBs cannot be read or written by SNMPv1 requests.</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#acl">ACL</div><div class="search_word">acl</div><div class="display_word">ACL</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview the access list (acl) is a conditional statement that determines whether to permit or to deny the frame. if the access list is applied to the interface, only the permitted frame will be transferred, and the denied frame will be discarded. as this allows for only specified frames to be selected for transfer, this feature is primarily used for security purposes. this product supports three access list types, as shown in the table below. access list type access list type deciding criteria access list id purpose of use ipv4 access list source ipv4 address destination ipv4 address ip protocol type 1–2000 filters access from specific hosts and networks. filters specific ip protocol types such as tcp/udp. ipv6 access list source ipv6 address 3001–4000 filters access from specific hosts and networks. mac access list source mac address destination mac address 2001–3000 filters access and data transfer from specific devices.</div><div class="display_word">1. Function Overview The access list (ACL) is a conditional statement that determines whether to permit or to deny the frame. If the access list is applied to the interface, only the permitted frame will be transferred, and the denied frame will be discarded. As this allows for only specified frames to be selected for transfer, this feature is primarily used for security purposes. This product supports three access list types, as shown in the table below. Access list type Access list type Deciding criteria Access list ID Purpose of use IPv4 access list Source IPv4 address Destination IPv4 address IP protocol type 1–2000 Filters access from specific hosts and networks. Filters specific IP protocol types such as TCP/UDP. IPv6 access list Source IPv6 address 3001–4000 Filters access from specific hosts and networks. MAC access list Source MAC address Destination MAC address 2001–3000 Filters access and data transfer from specific devices.</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used acl abbreviation of “ access control list ”. wildcard mask information that specifies which portion of the specified ipv4 address or mac address is read. this is used when specifying a range of ipv4 addresses or mac addresses as acl conditions. when the wildcard mask bit is “0” : check the corresponding bit when the wildcard mask bit is “1” : do not check the corresponding bit examples of settings using wildcard masks are shown below. (the underlined portion is the wildcard mask.) to specify conditions for subnet 192.168.1.0/24 : 192.168.1.0 0.0.0.255 (specified in decimal) to specify conditions for vendor code 00-a0-de- - - *: 00a0.de00.0000 0000.00ff.ffff (specified in hexadecimal)</div><div class="display_word">2. Definition of Terms Used ACL Abbreviation of “ Access Control List ”. Wildcard mask Information that specifies which portion of the specified IPv4 address or MAC address is read. This is used when specifying a range of IPv4 addresses or MAC addresses as ACL conditions. When the wildcard mask bit is “0” : check the corresponding bit When the wildcard mask bit is “1” : do not check the corresponding bit Examples of settings using wildcard masks are shown below. (The underlined portion is the wildcard mask.) To specify conditions for subnet 192.168.1.0/24 : 192.168.1.0 0.0.0.255 (specified in decimal) To specify conditions for vendor code 00-A0-DE- - - *: 00A0.DE00.0000 0000.00FF.FFFF (specified in hexadecimal)</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#アクセスリストの生成">3.1. Generate access list</div><div class="search_word">3.1. generate access list access lists for the number of ids in each access list number can be generated. (refer to the table in 1 function overview .) a maximum of 256 control conditions can be registered per access list. if the registered control conditions are not satisfied, forwarding occurs as usual.</div><div class="display_word">3.1. Generate access list Access lists for the number of IDs in each access list number can be generated. (Refer to the table in 1 Function Overview .) A maximum of 256 control conditions can be registered per access list. If the registered control conditions are not satisfied, forwarding occurs as usual.</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#インターフェースへの適用">3.2. Applying to the interface</div><div class="search_word">3.2. applying to the interface the following table shows how access lists are applied to the input/output interfaces of this product. note that one access list can be applied to the in and out respectively for an interface. status of access list application to the interface access list type lan/sfp port vlan interface static/lacp logical interface in out in out in out ipv4 access list yes yes (*) yes yes (*) yes no ipv6 access list yes yes yes yes yes no mac access list yes no yes no yes no (*) as a limitation, an ipv4 access list that specifies a range of port numbers cannot be applied to the output (out) side of an interface. the number of access lists that can be applied to the interface depends on the number of control parameters that are registered in the access lists. on this product, a maximum of 512 control conditions can be registered to the interface. applying an access list to the interface will use resources “equivalent to the number of control conditions that are registered in the access list” . however, control conditions may also be used internally within the system in some cases, and use resources accordingly.</div><div class="display_word">3.2. Applying to the interface The following table shows how access lists are applied to the input/output interfaces of this product. Note that one access list can be applied to the IN and OUT respectively for an interface. Status of access list application to the interface Access list type LAN/SFP port VLAN interface Static/LACP logical interface in out in out in out IPv4 access list Yes Yes (*) Yes Yes (*) Yes No IPv6 access list Yes Yes Yes Yes Yes No MAC access list Yes No Yes No Yes No (*) As a limitation, an IPv4 access list that specifies a range of port numbers cannot be applied to the output (out) side of an interface. The number of access lists that can be applied to the interface depends on the number of control parameters that are registered in the access lists. On this product, a maximum of 512 control conditions can be registered to the interface. Applying an access list to the interface will use resources “equivalent to the number of control conditions that are registered in the access list” . However, control conditions may also be used internally within the system in some cases, and use resources accordingly.</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#lansfpポートおよび論理インターフェースに対する設定">3.3. Settings for the LAN/SFP port and logical interface</div><div class="search_word">3.3. settings for the lan/sfp port and logical interface the steps for applying an access list to a lan/sfp port and to a logical interface are shown below. decide on the filtering parameters, and generate the access list. add explanatory text as necessary. check the access list. apply the access list to the lan/sfp port and logical interface. check the applied access list. a list of operation commands is given below. access list operating commands (when applied to the lan/sfp port and logical interface) access list type generate access list check access list apply access list check applied access list ipv4 access list access-list show access-list access-group show access-group ipv6 access list access-list show access-list access-group show access-group mac access list access-list show access-list access-group show access-group</div><div class="display_word">3.3. Settings for the LAN/SFP port and logical interface The steps for applying an access list to a LAN/SFP port and to a logical interface are shown below. Decide on the filtering parameters, and generate the access list. Add explanatory text as necessary. Check the access list. Apply the access list to the LAN/SFP port and logical interface. Check the applied access list. A list of operation commands is given below. Access list operating commands (when applied to the LAN/SFP port and logical interface) Access list type Generate access list Check access list Apply access list Check applied access list IPv4 access list access-list show access-list access-group show access-group IPv6 access list access-list show access-list access-group show access-group MAC access list access-list show access-list access-group show access-group</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#vlanインターフェースに対する設定">3.4. VLAN interface settings</div><div class="search_word">3.4. vlan interface settings the steps for applying access lists to the vlan interface are shown below. decide on the filtering parameters, and generate the access list. add explanatory text as necessary. check the access list. generate the vlan access map. set the access list for the vlan access map. check the vlan access map. apply the vlan access map to the vlan. check the vlan access map that was applied. the operations in steps 1 and 2 are the same as those shown in 3.2. the following is a list of operating commands for steps 3. and later. vlan access map operating command access list type vlan access map generation settings for access list used with vlan access map vlan access map confirmation vlan access map application confirmation of the applied vlan access map ipv4 access list vlan access-map match access-list show vlan access-map vlan filter show vlan filter ipv6 access list vlan access-map match access-list show vlan access-map vlan filter show vlan filter mac access list vlan access-map match access-list show vlan access-map vlan filter show vlan filter</div><div class="display_word">3.4. VLAN interface settings The steps for applying access lists to the VLAN interface are shown below. Decide on the filtering parameters, and generate the access list. Add explanatory text as necessary. Check the access list. Generate the VLAN access map. Set the access list for the VLAN access map. Check the VLAN access map. Apply the VLAN access map to the VLAN. Check the VLAN access map that was applied. The operations in steps 1 and 2 are the same as those shown in 3.2. The following is a list of operating commands for steps 3. and later. VLAN access map operating command Access list type VLAN access map generation Settings for access list used with VLAN access map VLAN access map confirmation VLAN access map application Confirmation of the applied VLAN access map IPv4 access list vlan access-map match access-list show vlan access-map vlan filter show vlan filter IPv6 access list vlan access-map match access-list show vlan access-map vlan filter show vlan filter MAC access list vlan access-map match access-list show vlan access-map vlan filter show vlan filter</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands apply ipv4 access list access-group generate ipv4 access list access-list add ipv4 access list explanatory text access-list description apply ipv4 access list access-group generate ipv6 access list access-list add ipv6 access list explanatory text access-list description apply ipv6 access list access-group generate mac access list access-list add mac access list explanatory text access-list description apply mac access list access-group show generated access list show access-list show access list applied to interface show access-group create vlan access map vlan access-map set vlan access map parameters match assign vlan access map to vlan vlan filter show vlan access map show vlan access-map show vlan access map filter show vlan filter</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Apply IPv4 access list access-group Generate IPv4 access list access-list Add IPv4 access list explanatory text access-list description Apply IPv4 access list access-group Generate IPv6 access list access-list Add IPv6 access list explanatory text access-list description Apply IPv6 access list access-group Generate MAC access list access-list Add MAC access list explanatory text access-list description Apply MAC access list access-group Show generated access list show access-list Show access list applied to interface show access-group Create VLAN access map vlan access-map Set VLAN access map parameters match Assign VLAN access map to VLAN vlan filter Show VLAN access map show vlan access-map Show VLAN access map filter show vlan filter</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#ipv4アクセスリストの設定">5.1. IPv4 access list settings</div><div class="search_word">5.1. ipv4 access list settings</div><div class="display_word">5.1. IPv4 access list settings</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#lanポートへの適用例">5.1.1. Example of application to a LAN port</div><div class="search_word">5.1.1. example of application to a lan port ■ specify host set lan port #1 so that access is only permitted from host: 192.168.1.1 to host: 10.1.1.1 . with #123 as the access list id, add ipv4-acl-ex as access list explanatory text using. generate and confirm access list #123 . yamaha(config)#access-list 123 permit any host 192.168.1.1 host 10.1.1.1 (1) yamaha(config)#access-list 123 deny any any anyyamaha(config)#access-list 123 description ipv4-acl-ex (2) yamaha(config)#endyamaha#yamaha#show access-list 123 (3) ipv4 access list 123    10 permit any host 192.168.1.1 host 10.1.1.1    20 deny any any anyyamaha# 1 generate access list 2 add access list explanatory text 3 check access list apply access list #123 to lan port #1 . yamaha(config)#interface port1.1yamaha(config-if)#access-group 123 in (1) yamaha(config-if)#endyamaha#yamaha#show access-group (2) interface port1.1 : ipv4 access group 123 in 1 apply access list 2 check access list settings to change the access list (delete or add a setting), application of the list to the lan port must be temporarily canceled. for the setting indicated above, delete the setting that allows access from host: 192.168.1.1 to host: 10.1.1.1 and add a setting that allows access from host: 192.168.1.1 to host: 10.1.1.2 . temporarily cancel the application of access list #123 from lan port #1 . yamaha(config)#interface port1.1yamaha(config-if)#no access-group 123 in (1) 1 cancel the application of the access list delete, add, and then check the setting in access list #123 . yamaha(config)#no access-list 123 10 (1) yamaha(config)#access-list 123 10 permit any host 192.168.1.1 host 10.1.1.2 (2) yamaha(config)#endyamaha#yamaha#show access-list 123 (3) ipv4 access list 123    10 permit any host 192.168.1.1 host 10.1.1.2    20 deny any any any 1 remove the setting from the access list 2 add the setting to the access list 3 check access list apply access list #123 to lan port #1 again. yamaha(config)#interface port1.1yamaha(config-if)#access-group 123 in (1) 1 apply access list ■ specify network set lan port #1 so that access is only permitted from network: 192.168.1.0/24 to host: 10.1.1.1 . with #123 as the access list id, add ipv4-acl-ex as access list explanatory text using. generate and confirm access list #123 . yamaha(config)#access-list 123 permit any 192.168.1.0 0.0.0.255 host 10.1.1.1 (1) yamaha(config)#access-list 123 deny any any anyyamaha(config)#access-list 123 description ipv4-acl-ex (2) yamaha(config)#endyamaha#yamaha#show ip access-list (3) ipv4 access list 123    10 permit any 192.168.1.0/24 host 10.1.1.1    20 deny any any anyyamaha# 1 generate access list 2 add access list explanatory text 3 check acl apply access list #123 to lan port #1 . yamaha(config)#interface port1.1yamaha(config-if)#access-group 123 in (1) yamaha(config-if)#endyamaha#yamaha#show access-group (2) interface port1.1 : ipv4 access group 123 in 1 apply access list 2 check access list settings to change the access list (delete or add a setting), application of the list to the lan port must be temporarily canceled. the specific procedure is the same as for specifying a host.</div><div class="display_word">5.1.1. Example of application to a LAN port ■ Specify host Set LAN port #1 so that access is only permitted from host: 192.168.1.1 to host: 10.1.1.1 . With #123 as the access list ID, add IPV4-ACL-EX as access list explanatory text using. Generate and confirm access list #123 . Yamaha(config)#access-list 123 permit any host 192.168.1.1 host 10.1.1.1 (1) Yamaha(config)#access-list 123 deny any any anyYamaha(config)#access-list 123 description IPV4-ACL-EX (2) Yamaha(config)#endYamaha#Yamaha#show access-list 123 (3) IPv4 access list 123    10 permit any host 192.168.1.1 host 10.1.1.1    20 deny any any anyYamaha# 1 Generate access list 2 Add access list explanatory text 3 Check access list Apply access list #123 to LAN port #1 . Yamaha(config)#interface port1.1Yamaha(config-if)#access-group 123 in (1) Yamaha(config-if)#endYamaha#Yamaha#show access-group (2) Interface port1.1 : IPv4 access group 123 in 1 Apply access list 2 Check access list settings To change the access list (delete or add a setting), application of the list to the LAN port must be temporarily canceled. For the setting indicated above, delete the setting that allows access from host: 192.168.1.1 to host: 10.1.1.1 and add a setting that allows access from host: 192.168.1.1 to host: 10.1.1.2 . Temporarily cancel the application of access list #123 from LAN port #1 . Yamaha(config)#interface port1.1Yamaha(config-if)#no access-group 123 in (1) 1 Cancel the application of the access list Delete, add, and then check the setting in access list #123 . Yamaha(config)#no access-list 123 10 (1) Yamaha(config)#access-list 123 10 permit any host 192.168.1.1 host 10.1.1.2 (2) Yamaha(config)#endYamaha#Yamaha#show access-list 123 (3) IPv4 access list 123    10 permit any host 192.168.1.1 host 10.1.1.2    20 deny any any any 1 Remove the setting from the access list 2 Add the setting to the access list 3 Check access list Apply access list #123 to LAN port #1 again. Yamaha(config)#interface port1.1Yamaha(config-if)#access-group 123 in (1) 1 Apply access list ■ Specify network Set LAN port #1 so that access is only permitted from network: 192.168.1.0/24 to host: 10.1.1.1 . With #123 as the access list ID, add IPV4-ACL-EX as access list explanatory text using. Generate and confirm access list #123 . Yamaha(config)#access-list 123 permit any 192.168.1.0 0.0.0.255 host 10.1.1.1 (1) Yamaha(config)#access-list 123 deny any any anyYamaha(config)#access-list 123 description IPV4-ACL-EX (2) Yamaha(config)#endYamaha#Yamaha#show ip access-list (3) IPv4 access list 123    10 permit any 192.168.1.0/24 host 10.1.1.1    20 deny any any anyYamaha# 1 Generate access list 2 Add access list explanatory text 3 Check ACL Apply access list #123 to LAN port #1 . Yamaha(config)#interface port1.1Yamaha(config-if)#access-group 123 in (1) Yamaha(config-if)#endYamaha#Yamaha#show access-group (2) Interface port1.1 : IPv4 access group 123 in 1 Apply access list 2 Check access list settings To change the access list (delete or add a setting), application of the list to the LAN port must be temporarily canceled. The specific procedure is the same as for specifying a host.</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#vlanインターフェースへの適用例">5.1.2. Example of application to the VLAN interface</div><div class="search_word">5.1.2. example of application to the vlan interface ■ specify host set vlan #1000 so that access is only permitted from host: 192.168.1.1 to host: 10.1.1.1 . we will use access list id #123 . the vlan access map to be used will be vam-002 , and access list #123 will be set. generate and confirm access list #123 . yamaha(config)#access-list 123 permit any host 192.168.1.1 host 10.1.1.1 (1) yamaha(config)#access-list 123 deny any any anyyamaha(config)#endyamaha#yamaha#show access-list 123 (2) ipv4 access list 123    10 permit any host 192.168.1.1 host 10.1.1.1    20 deny any any any 1 generate access list 2 check access list generate vlan access map vam-002 , and set access list #123 . yamaha(config)#vlan access-map vam-002 (1) yamaha(config-vlan-access-map)#match access-list 123 (2) yamaha(config-vlan-access-map)#endyamaha#yamaha#show vlan access-map (3) vlan access-map vam-002    match ipv4 access-list 123 1 vlan access map generation 2 register the access list 3 check the settings for vlan access map and access list apply vlan access map vam-002 to vlan #1000 , and confirm the status. yamaha(config)#vlan filter vam-002 1000 in (1) yamaha(config)#endyamaha#yamaha#show vlan filter (2) vlan filter vam-002 is applied to vlan 1000 in 1 apply the vlan access map to the vlan 2 check the settings for vlan access map to change the access list (delete or add a setting), it is necessary to temporarily cancel applying the list to the vlan interface and the setting in the vlan access map. for the setting indicated above, delete the setting that allows access from host: 192.168.1.1 to host: 10.1.1.1 and add a setting that allows access from host: 192.168.1.1 to host: 10.1.1.2 . temporarily cancel vlan access map vam-002 from being applied to vlan #1000 . yamaha(config)#no vlan filter vam-002 1000 in (1) 1 cancel the application of a vlan access map from a vlan temporarily cancel the access list #123 setting in vlan access map vam-002 . yamaha(config)#vlan access-map vam-002 (1) yamaha(config-vlan-access-map)#no match access-list 123 (2) 1 change the vlan access map 2 cancel the registration of access list delete, add, and then check the setting in access list #123 . yamaha(config)#no access-list 123 10 (1) yamaha(config)#access-list 123 10 permit any host 192.168.1.1 host 10.1.1.2 (2) yamaha(config)#endyamaha#yamaha#show access-list 123 (3) ipv4 access list 123    10 permit any host 192.168.1.1 host 10.1.1.2    20 deny any any any 1 remove the setting from the access list 2 add the setting to the access list 3 check access list specify the access list #123 setting in vlan access map vam-002 again. yamaha(config)#vlan access-map vam-002 (1) yamaha(config-vlan-access-map)#match access-list 123 (2) 1 change the vlan access map 2 register the access list apply vlan access map vam-002 to vlan #1000 again. yamaha(config)#vlan filter vam-002 1000 in (1) 1 apply the vlan access map to the vlan ■ specify network set vlan #1000 so that access is only permitted from network: 192.168.1.0/24 to host: 10.1.1.1 . we will use access list id #123 . the vlan access map to be used will be vam-002 , and access list #123 will be set. generate and confirm access list #123 . yamaha(config)#access-list 123 permit any 192.168.1.0 0.0.0.255 host 10.1.1.1 (1) yamaha(config)#access-list 123 deny any any anyyamaha(config)#endyamaha#yamaha#show access-list 123 (2) ipv4 access list 123    10 permit any 192.168.1.0/24 host 10.1.1.1    20 deny any any any 1 generate access list 2 check access list generate vlan access map vam-002 , and set access list #123 . yamaha(config)#vlan access-map vam-002 (1) yamaha(config-vlan-access-map)#match access-list 123 (2) yamaha(config-vlan-access-map)#endyamaha#yamaha#show vlan access-map (3) vlan access-map vam-002    match ipv4 access-list 123 1 vlan access map generation 2 register the access list 3 check the settings for vlan access map and access list apply vlan access map vam-002 to vlan #1000 , and confirm the status. yamaha(config)#vlan filter vam-002 1000 in (1) yamaha(config)#endyamaha#yamaha#show vlan filter (2) vlan filter vam-002 is applied to vlan 1000 in 1 apply the vlan access map to the vlan 2 check the settings for vlan access map to change the access list (delete or add a setting), it is necessary to temporarily cancel applying the list to the vlan interface and the setting in the vlan access map. the specific procedure is the same as for specifying a host.</div><div class="display_word">5.1.2. Example of application to the VLAN interface ■ Specify host Set VLAN #1000 so that access is only permitted from host: 192.168.1.1 to host: 10.1.1.1 . We will use access list ID #123 . The VLAN access map to be used will be VAM-002 , and access list #123 will be set. Generate and confirm access list #123 . Yamaha(config)#access-list 123 permit any host 192.168.1.1 host 10.1.1.1 (1) Yamaha(config)#access-list 123 deny any any anyYamaha(config)#endYamaha#Yamaha#show access-list 123 (2) IPv4 access list 123    10 permit any host 192.168.1.1 host 10.1.1.1    20 deny any any any 1 Generate access list 2 Check access list Generate VLAN access map VAM-002 , and set access list #123 . Yamaha(config)#vlan access-map VAM-002 (1) Yamaha(config-vlan-access-map)#match access-list 123 (2) Yamaha(config-vlan-access-map)#endYamaha#Yamaha#show vlan access-map (3) Vlan access-map VAM-002    match ipv4 access-list 123 1 VLAN access map generation 2 Register the access list 3 Check the settings for VLAN access map and access list Apply VLAN access map VAM-002 to VLAN #1000 , and confirm the status. Yamaha(config)#vlan filter VAM-002 1000 in (1) Yamaha(config)#endYamaha#Yamaha#show vlan filter (2) Vlan filter VAM-002 is applied to vlan 1000 in 1 Apply the VLAN access map to the VLAN 2 Check the settings for VLAN access map To change the access list (delete or add a setting), it is necessary to temporarily cancel applying the list to the VLAN interface and the setting in the VLAN access map. For the setting indicated above, delete the setting that allows access from host: 192.168.1.1 to host: 10.1.1.1 and add a setting that allows access from host: 192.168.1.1 to host: 10.1.1.2 . Temporarily cancel VLAN access map VAM-002 from being applied to VLAN #1000 . Yamaha(config)#no vlan filter VAM-002 1000 in (1) 1 Cancel the application of a VLAN access map from a VLAN Temporarily cancel the access list #123 setting in VLAN access map VAM-002 . Yamaha(config)#vlan access-map VAM-002 (1) Yamaha(config-vlan-access-map)#no match access-list 123 (2) 1 Change the VLAN access map 2 Cancel the registration of access list Delete, add, and then check the setting in access list #123 . Yamaha(config)#no access-list 123 10 (1) Yamaha(config)#access-list 123 10 permit any host 192.168.1.1 host 10.1.1.2 (2) Yamaha(config)#endYamaha#Yamaha#show access-list 123 (3) IPv4 access list 123    10 permit any host 192.168.1.1 host 10.1.1.2    20 deny any any any 1 Remove the setting from the access list 2 Add the setting to the access list 3 Check access list Specify the access list #123 setting in VLAN access map VAM-002 again. Yamaha(config)#vlan access-map VAM-002 (1) Yamaha(config-vlan-access-map)#match access-list 123 (2) 1 Change the VLAN access map 2 Register the access list Apply VLAN access map VAM-002 to VLAN #1000 again. Yamaha(config)#vlan filter VAM-002 1000 in (1) 1 Apply the VLAN access map to the VLAN ■ Specify network Set VLAN #1000 so that access is only permitted from network: 192.168.1.0/24 to host: 10.1.1.1 . We will use access list ID #123 . The VLAN access map to be used will be VAM-002 , and access list #123 will be set. Generate and confirm access list #123 . Yamaha(config)#access-list 123 permit any 192.168.1.0 0.0.0.255 host 10.1.1.1 (1) Yamaha(config)#access-list 123 deny any any anyYamaha(config)#endYamaha#Yamaha#show access-list 123 (2) IPv4 access list 123    10 permit any 192.168.1.0/24 host 10.1.1.1    20 deny any any any 1 Generate access list 2 Check access list Generate VLAN access map VAM-002 , and set access list #123 . Yamaha(config)#vlan access-map VAM-002 (1) Yamaha(config-vlan-access-map)#match access-list 123 (2) Yamaha(config-vlan-access-map)#endYamaha#Yamaha#show vlan access-map (3) Vlan access-map VAM-002    match ipv4 access-list 123 1 VLAN access map generation 2 Register the access list 3 Check the settings for VLAN access map and access list Apply VLAN access map VAM-002 to VLAN #1000 , and confirm the status. Yamaha(config)#vlan filter VAM-002 1000 in (1) Yamaha(config)#endYamaha#Yamaha#show vlan filter (2) Vlan filter VAM-002 is applied to vlan 1000 in 1 Apply the VLAN access map to the VLAN 2 Check the settings for VLAN access map To change the access list (delete or add a setting), it is necessary to temporarily cancel applying the list to the VLAN interface and the setting in the VLAN access map. The specific procedure is the same as for specifying a host.</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#片方向からのtcp通信のみ許可する-tcpフラグの使用例">5.1.3. Allowing only TCP communication from one direction (example using TCP flags)</div><div class="search_word">5.1.3. allowing only tcp communication from one direction (example using tcp flags) given vlan10 and vlan20, this example controls tcp communication so that it occurs in one direction. communication from vlan10 to vlan20 is possible by telnet, etc. communication from vlan20 to vlan10 is not possible by telnet, etc. generate access list #1 . specify settings that only allow ipv4 tcp packets with an ack or rst flag. yamaha(config)#access-list 1 permit tcp any any ack (1) yamaha(config)#access-list 1 permit tcp any any rstyamaha(config)#access-list 1 deny any any anyyamaha(config)#endyamaha#yamaha#show access-list (2) ipv4 access list 1    10 permit tcp any any ack    20 permit tcp any any rst    30 deny any any any 1 configure access list settings 2 check access list settings generate vlan access map vam-established and specify access list #1 . yamaha(config)#vlan access-map vam-established (1) yamaha(config-vlan-access-map)#match access-list 1 (2) yamaha(config-vlan-access-map)#endyamaha#yamaha#show vlan access-map (3) vlan access-map vam-established    match ipv4 access-list 1 1 vlan access map generation 2 register the access list 3 check the settings for vlan access map apply vlan access map vam-established to vlan #20 . yamaha(config)#vlan filter vam-established 20 in (1) yamaha(config)#endyamaha#yamaha#show vlan filter (2) vlan filter vam-established is applied to vlan 20 in 1 apply the vlan access map to the vlan 2 check the status of application to the vlan</div><div class="display_word">5.1.3. Allowing only TCP communication from one direction (example using TCP flags) Given VLAN10 and VLAN20, this example controls TCP communication so that it occurs in one direction. Communication from VLAN10 to VLAN20 is possible by Telnet, etc. Communication from VLAN20 to VLAN10 is not possible by Telnet, etc. Generate access list #1 . Specify settings that only allow IPv4 TCP packets with an ACK or RST flag. Yamaha(config)#access-list 1 permit tcp any any ack (1) Yamaha(config)#access-list 1 permit tcp any any rstYamaha(config)#access-list 1 deny any any anyYamaha(config)#endYamaha#Yamaha#show access-list (2) IPv4 access list 1    10 permit tcp any any ack    20 permit tcp any any rst    30 deny any any any 1 Configure access list settings 2 Check access list settings Generate VLAN access map VAM-ESTABLISHED and specify access list #1 . Yamaha(config)#vlan access-map VAM-ESTABLISHED (1) Yamaha(config-vlan-access-map)#match access-list 1 (2) Yamaha(config-vlan-access-map)#endYamaha#Yamaha#show vlan access-map (3) Vlan access-map VAM-ESTABLISHED    match ipv4 access-list 1 1 VLAN access map generation 2 Register the access list 3 Check the settings for VLAN access map Apply VLAN access map VAM-ESTABLISHED to VLAN #20 . Yamaha(config)#vlan filter VAM-ESTABLISHED 20 in (1) Yamaha(config)#endYamaha#Yamaha#show vlan filter (2) Vlan filter VAM-ESTABLISHED is applied to vlan 20 in 1 Apply the VLAN access map to the VLAN 2 Check the status of application to the VLAN</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#ipv6アクセスリストの設定">5.2. IPv6 access list settings</div><div class="search_word">5.2. ipv6 access list settings</div><div class="display_word">5.2. IPv6 access list settings</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#lanポートへの適用例">5.2.1. Example of application to a LAN port</div><div class="search_word">5.2.1. example of application to a lan port ■ specify host set lan port #1 so that it only allows access from host: 2001:db8::1 . with #3001 as the access list id, add ipv6-acl-ex as access list explanatory text using. generate and confirm access list #3001 . yamaha(config)#access-list 3001 permit 2001:db8::1/128 (1) yamaha(config)#access-list 3001 deny anyyamaha(config)#access-list 3001 description ipv6-acl-ex (2) yamaha(config)#endyamaha#yamaha#show access-list 3001 (3) ipv6 access list 3001    10 permit 2001:db8::1/128    20 deny any 1 generate access list 2 add access list explanatory text 3 check access list apply access list #3001 to lan port #1 . yamaha(config)#interface port1.1yamaha(config-if)#access-group 3000 in (1) yamaha(config-if)#endyamaha#yamaha#show access-group (2) interface port1.1 : ipv6 access group 3001 in 1 apply access list 2 check access list settings to change the access list (delete or add a setting), application of the list to the lan port must be temporarily canceled. for the specific procedure, refer to example of application to a lan port in ipv4 access list settings . ■ specify network set lan port #1 so that it only allows access from network: 2001:db8::/64 . with #3001 as the access list id, add ipv6-acl-ex as access list explanatory text using. generate and confirm access list #3001 . yamaha(config)#access-list 3001 permit 2001:db8::/64 (1) yamaha(config)#access-list 3001 deny anyyamaha(config)#access-list 3001 description ipv6-acl-ex (2) yamaha(config)#endyamaha# show access-list 3001 (3) ipv6 access list 3001    10 permit 2001:db8::/64    20 deny any 1 generate access list 2 add access list explanatory text 3 check access list apply access list #3001 to lan port #1 . yamaha(config)#interface port1.1yamaha(config-if)#access-group 3001 in (1) yamaha(config-if)#endyamaha#yamaha#show access-group (2) interface port1.1 : ipv6 access group 3001 in 1 apply access list 2 check access list settings to change the access list (delete or add a setting), application of the list to the lan port must be temporarily canceled. for the specific procedure, refer to example of application to a lan port in ipv4 access list settings .</div><div class="display_word">5.2.1. Example of application to a LAN port ■ Specify host Set LAN port #1 so that it only allows access from host: 2001:db8::1 . With #3001 as the access list ID, add IPV6-ACL-EX as access list explanatory text using. Generate and confirm access list #3001 . Yamaha(config)#access-list 3001 permit 2001:db8::1/128 (1) Yamaha(config)#access-list 3001 deny anyYamaha(config)#access-list 3001 description IPV6-ACL-EX (2) Yamaha(config)#endYamaha#Yamaha#show access-list 3001 (3) IPv6 access list 3001    10 permit 2001:db8::1/128    20 deny any 1 Generate access list 2 Add access list explanatory text 3 Check access list Apply access list #3001 to LAN port #1 . Yamaha(config)#interface port1.1Yamaha(config-if)#access-group 3000 in (1) Yamaha(config-if)#endYamaha#Yamaha#show access-group (2) Interface port1.1 : IPv6 access group 3001 in 1 Apply access list 2 Check access list settings To change the access list (delete or add a setting), application of the list to the LAN port must be temporarily canceled. For the specific procedure, refer to Example of application to a LAN port in IPv4 access list settings . ■ Specify network Set LAN port #1 so that it only allows access from network: 2001:db8::/64 . With #3001 as the access list ID, add IPV6-ACL-EX as access list explanatory text using. Generate and confirm access list #3001 . Yamaha(config)#access-list 3001 permit 2001:db8::/64 (1) Yamaha(config)#access-list 3001 deny anyYamaha(config)#access-list 3001 description IPV6-ACL-EX (2) Yamaha(config)#endYamaha# show access-list 3001 (3) IPv6 access list 3001    10 permit 2001:db8::/64    20 deny any 1 Generate access list 2 Add access list explanatory text 3 Check access list Apply access list #3001 to LAN port #1 . Yamaha(config)#interface port1.1Yamaha(config-if)#access-group 3001 in (1) Yamaha(config-if)#endYamaha#Yamaha#show access-group (2) Interface port1.1 : IPv6 access group 3001 in 1 Apply access list 2 Check access list settings To change the access list (delete or add a setting), application of the list to the LAN port must be temporarily canceled. For the specific procedure, refer to Example of application to a LAN port in IPv4 access list settings .</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#vlanインターフェースへの適用例">5.2.2. Example of application to the VLAN interface</div><div class="search_word">5.2.2. example of application to the vlan interface ■ specify host set vlan #1000 so that it only allows access from host: 2001:db8::1 . we will use access list id #3001 . the vlan access map to be used will be vam-001 , and access list #3001 will be set. generate and confirm access list #3001 . yamaha(config)#access-list 3001 permit 2001:db8::1/128 (1) yamaha(config)#access-list 3001 deny anyyamaha(config)#endyamaha#yamaha#show access-list 3001 (2) ipv6 access list 3001    10 permit 2001:db8::1/128    20 deny any 1 generate access list 2 check access list generate vlan access map vam-001 , and set access list #3001 . yamaha(config)#vlan access-map vam-001 (1) yamaha(config-vlan-access-map)#match access-list 3001 (2) yamaha(config-vlan-access-map)#endyamaha#yamaha#show vlan access-map (3) vlan access-map vam-001    match ipv6 access-list 3001 1 vlan access map generation 2 configure access list settings 3 check the settings for vlan access map and access list apply vlan access map vam-001 to vlan #1000 , and confirm the status. yamaha(config)#vlan filter vam-001 1000 in (1) yamaha(config)#endyamaha#yamaha#show vlan filter (2) vlan filter vam-001 is applied to vlan 1000 in 1 apply the vlan access map to the vlan 2 check the settings for vlan access map to change the access list (delete or add a setting), it is necessary to temporarily cancel applying the list to the vlan interface and the setting in the vlan access map. for the specific procedure, refer to example of application to the vlan interface in ipv4 access list settings . ■ specify network set vlan #1000 so that it only allows access from network: 2001:db8::/64 . we will use access list id #3001 . the vlan access map to be used will be vam-001 , and access list #3001 will be set. generate and confirm access list #2 . yamaha(config)#access-list 3001 permit 2001:db8::/64 (1) yamaha(config)#access-list 3001 deny anyyamaha(config)#endyamaha#yamaha#show access-list 3001 (2) ipv6 access list 3001    10 permit 2001:db8::/64    20 deny any 1 generate access list 2 check access list generate vlan access map vam-001 , and set access list #3001 . yamaha(config)#vlan access-map vam-001 (1) yamaha(config-vlan-access-map)#match access-list 3001 (2) yamaha(config-vlan-access-map)#endyamaha#yamaha#show vlan access-map (3) vlan access-map vam-001    match ipv6 access-list 3001 1 vlan access map generation 2 configure access list settings 3 check the settings for vlan access map and access list apply vlan access map vam-001 to vlan #1000 , and confirm the status. yamaha(config)#vlan filter vam-001 1000 in (1) yamaha(config)#endyamaha#yamaha#show vlan filter (2) vlan filter vam-001 is applied to vlan 1000 in 1 apply the vlan access map to the vlan 2 check the settings for vlan access map to change the access list (delete or add a setting), it is necessary to temporarily cancel applying the list to the vlan interface and the setting in the vlan access map. for the specific procedure, refer to example of application to the vlan interface in ipv4 access list settings .</div><div class="display_word">5.2.2. Example of application to the VLAN interface ■ Specify host Set VLAN #1000 so that it only allows access from host: 2001:db8::1 . We will use access list ID #3001 . The VLAN access map to be used will be VAM-001 , and access list #3001 will be set. Generate and confirm access list #3001 . Yamaha(config)#access-list 3001 permit 2001:db8::1/128 (1) Yamaha(config)#access-list 3001 deny anyYamaha(config)#endYamaha#Yamaha#show access-list 3001 (2) IPv6 access list 3001    10 permit 2001:db8::1/128    20 deny any 1 Generate access list 2 Check access list Generate VLAN access map VAM-001 , and set access list #3001 . Yamaha(config)#vlan access-map VAM-001 (1) Yamaha(config-vlan-access-map)#match access-list 3001 (2) Yamaha(config-vlan-access-map)#endYamaha#Yamaha#show vlan access-map (3) Vlan access-map VAM-001    match ipv6 access-list 3001 1 VLAN access map generation 2 Configure access list settings 3 Check the settings for VLAN access map and access list Apply VLAN access map VAM-001 to VLAN #1000 , and confirm the status. Yamaha(config)#vlan filter VAM-001 1000 in (1) Yamaha(config)#endYamaha#Yamaha#show vlan filter (2) Vlan filter VAM-001 is applied to vlan 1000 in 1 Apply the VLAN access map to the VLAN 2 Check the settings for VLAN access map To change the access list (delete or add a setting), it is necessary to temporarily cancel applying the list to the VLAN interface and the setting in the VLAN access map. For the specific procedure, refer to Example of application to the VLAN interface in IPv4 access list settings . ■ Specify network Set VLAN #1000 so that it only allows access from network: 2001:db8::/64 . We will use access list ID #3001 . The VLAN access map to be used will be VAM-001 , and access list #3001 will be set. Generate and confirm access list #2 . Yamaha(config)#access-list 3001 permit 2001:db8::/64 (1) Yamaha(config)#access-list 3001 deny anyYamaha(config)#endYamaha#Yamaha#show access-list 3001 (2) IPv6 access list 3001    10 permit 2001:db8::/64    20 deny any 1 Generate access list 2 Check access list Generate VLAN access map VAM-001 , and set access list #3001 . Yamaha(config)#vlan access-map VAM-001 (1) Yamaha(config-vlan-access-map)#match access-list 3001 (2) Yamaha(config-vlan-access-map)#endYamaha#Yamaha#show vlan access-map (3) Vlan access-map VAM-001    match ipv6 access-list 3001 1 VLAN access map generation 2 Configure access list settings 3 Check the settings for VLAN access map and access list Apply VLAN access map VAM-001 to VLAN #1000 , and confirm the status. Yamaha(config)#vlan filter VAM-001 1000 in (1) Yamaha(config)#endYamaha#Yamaha#show vlan filter (2) Vlan filter VAM-001 is applied to vlan 1000 in 1 Apply the VLAN access map to the VLAN 2 Check the settings for VLAN access map To change the access list (delete or add a setting), it is necessary to temporarily cancel applying the list to the VLAN interface and the setting in the VLAN access map. For the specific procedure, refer to Example of application to the VLAN interface in IPv4 access list settings .</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#macアクセスリストの設定">5.3. MAC access list settings</div><div class="search_word">5.3. mac access list settings</div><div class="display_word">5.3. MAC access list settings</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#lanポートへの適用例">5.3.1. Example of application to a LAN port</div><div class="search_word">5.3.1. example of application to a lan port ■ specify host set lan port #1 so that it only denies access from host: 00-a0-de-12-34-56 . with #2001 as the access list id, add mac-acl-ex as access list explanatory text using. generate and confirm access list #2001 . yamaha(config)#access-list 2001 deny host 00a0.de12.3456 any (1) yamaha(config)#access-list 2001 description mac-acl-ex (2) yamaha(config)#endyamaha#yamaha#show access-list 2001 (3) mac access list 2001    10 deny host 00a0.de12.3456 any 1 generate access list 2 add access list explanatory text 3 check access list apply access list #2001 to lan port #1 . yamaha(config)#interface port1.1yamaha(config-if)#access-group 2001 in (1) yamaha(config-if)#endyamaha#yamaha#show access-group (2) interface port1.1 : mac access group 2001 in 1 apply access list 2 check access list settings to change the access list (delete or add a setting), application of the list to the lan port must be temporarily canceled. for the specific procedure, refer to example of application to a lan port in ipv4 access list settings . ■ specify vendor set lan port #1 so that it only denies access from vendor code: 00-a0-de- - - * (00-a0-de-00-00-00 to 00-a0-de-ff-ff-ff). with #2001 as the access list id, add mac-acl-ex as access list explanatory text using. generate and confirm access list #2001 . yamaha(config)#access-list 2001 deny 00a0.de00.0000 0000.00ff.ffff any (1) yamaha(config)#access-list 2001 description mac-acl-ex (2) yamaha(config)#endyamaha#yamaha#show access-list 2001 (3) mac access list 2001    10 deny 00a0.de00.0000 0000.00ff.ffff any 1 generate access list 2 add access list explanatory text 3 check access list apply access list #2001 to lan port #1 . yamaha(config)#interface port1.1yamaha(config-if)#access-group 2001 in (1) yamaha(config-if)#endyamaha#yamaha#show access-group (2) interface port1.1 : mac access group 2001 in 1 apply access list 2 check access list settings to change the access list (delete or add a setting), it is necessary to temporarily cancel applying the list to the vlan interface and the setting in the vlan access map. for the specific procedure, refer to example of application to a lan port in ipv4 access list settings .</div><div class="display_word">5.3.1. Example of application to a LAN port ■ Specify host Set LAN port #1 so that it only denies access from host: 00-A0-DE-12-34-56 . With #2001 as the access list ID, add MAC-ACL-EX as access list explanatory text using. Generate and confirm access list #2001 . Yamaha(config)#access-list 2001 deny host 00a0.de12.3456 any (1) Yamaha(config)#access-list 2001 description MAC-ACL-EX (2) Yamaha(config)#endYamaha#Yamaha#show access-list 2001 (3) MAC access list 2001    10 deny host 00A0.DE12.3456 any 1 Generate access list 2 Add access list explanatory text 3 Check access list Apply access list #2001 to LAN port #1 . Yamaha(config)#interface port1.1Yamaha(config-if)#access-group 2001 in (1) Yamaha(config-if)#endYamaha#Yamaha#show access-group (2) Interface port1.1 : MAC access group 2001 in 1 Apply access list 2 Check access list settings To change the access list (delete or add a setting), application of the list to the LAN port must be temporarily canceled. For the specific procedure, refer to Example of application to a LAN port in IPv4 access list settings . ■ Specify vendor Set LAN port #1 so that it only denies access from vendor code: 00-A0-DE- - - * (00-A0-DE-00-00-00 to 00-A0-DE-FF-FF-FF). With #2001 as the access list ID, add MAC-ACL-EX as access list explanatory text using. Generate and confirm access list #2001 . Yamaha(config)#access-list 2001 deny 00a0.de00.0000 0000.00ff.ffff any (1) Yamaha(config)#access-list 2001 description MAC-ACL-EX (2) Yamaha(config)#endYamaha#Yamaha#show access-list 2001 (3) MAC access list 2001    10 deny 00A0.DE00.0000 0000.00FF.FFFF any 1 Generate access list 2 Add access list explanatory text 3 Check access list Apply access list #2001 to LAN port #1 . Yamaha(config)#interface port1.1Yamaha(config-if)#access-group 2001 in (1) Yamaha(config-if)#endYamaha#Yamaha#show access-group (2) Interface port1.1 : MAC access group 2001 in 1 Apply access list 2 Check access list settings To change the access list (delete or add a setting), it is necessary to temporarily cancel applying the list to the VLAN interface and the setting in the VLAN access map. For the specific procedure, refer to Example of application to a LAN port in IPv4 access list settings .</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#vlanインターフェースへの適用例">5.3.2. Example of application to the VLAN interface</div><div class="search_word">5.3.2. example of application to the vlan interface ■ specify host set vlan #1000 so that it only denies access from host: 00-a0-de-12-34-56 . with #2001 as the access list id, add mac-acl-ex as access list explanatory text using. the vlan access map to be used will be vam-003 , and access list #2001 will be set. generate and confirm access list #2000 . yamaha(config)#access-list 2001 deny host 00a0.de12.3456 any (1) yamaha(config)#access-list 2001 description mac-acl-ex (2) yamaha(config)#endyamaha#yamaha#show access-list (3) mac access list 2001    10 deny host 00a0.de12.3456 any 1 generate access list #2001 2 add access list explanatory text 3 check access list generate vlan access map vam-003 , and set access list #2001 . yamaha(config)# vlan access-map vam-003 (1) yamaha(config-vlan-access-map)# match access-list 2001 (2) yamaha(config-vlan-access-map)# endyamaha#yamaha#show vlan access-map (3) vlan access-map vam-003    match mac access-list 2001 1 vlan access map generation 2 register the access list 3 check the settings for vlan access map and access list apply vlan access map vam-003 to vlan #1000 , and confirm the status. yamaha(config)#vlan filter vam-003 1000 in (1) yamaha(config)#endyamaha#yamaha#show vlan filter (2) vlan filter vam-003 is applied to vlan 1000 in 1 apply the vlan access map to the vlan 2 check the settings for vlan access map to change the access list (delete or add a setting), it is necessary to temporarily cancel applying the list to the vlan interface and the setting in the vlan access map. for the specific procedure, refer to example of application to the vlan interface in ipv4 access list settings . ■ specify vendor set vlan #1000 so that it only denies access from vendor code: 00-a0-de- - - * (00-a0-de-00-00-00 to 00-a0-de-ff-ff-ff). with #2001 as the access list id, add mac-acl-ex as access list explanatory text using. the vlan access map to be used will be vam-003 , and access list #2001 will be set. generate and confirm access list #2001 . yamaha(config)#access-list 2001 deny 00a0.de00.0000 0000.00ff.ffff any (1) yamaha(config)#access-list 2001 description mac-acl-ex (2) yamaha(config)#endyamaha#yamaha#show access-list 2001 (3) mac access list 2001    10 deny 00a0.de00.0000 0000.00ff.ffff any 1 generate access list #2001 2 add access list explanatory text 3 check access list generate vlan access map vam-003 , and set access list #2001 . yamaha(config)# vlan access-map vam-003 (1) yamaha(config-vlan-access-map)# match access-list 2001 (2) yamaha(config-vlan-access-map)# endyamaha#yamaha#show vlan access-map (3) vlan access-map vam-003    match mac access-list 2001 1 vlan access map generation 2 register the access list 3 check the settings for vlan access map and access list apply vlan access map vam-003 to vlan #1000 , and confirm the status. yamaha(config)#vlan filter vam-003 1000 in (1) yamaha(config)#endyamaha#yamaha#show vlan filter (2) vlan filter vam-003 is applied to vlan 1000 in 1 apply the vlan access map to the vlan 2 check the settings for vlan access map to change the access list (delete or add a setting), it is necessary to temporarily cancel applying the list to the vlan interface and the setting in the vlan access map. for the specific procedure, refer to example of application to the vlan interface in ipv4 access list settings .</div><div class="display_word">5.3.2. Example of application to the VLAN interface ■ Specify host Set VLAN #1000 so that it only denies access from host: 00-A0-DE-12-34-56 . With #2001 as the access list ID, add MAC-ACL-EX as access list explanatory text using. The VLAN access map to be used will be VAM-003 , and access list #2001 will be set. Generate and confirm access list #2000 . Yamaha(config)#access-list 2001 deny host 00a0.de12.3456 any (1) Yamaha(config)#access-list 2001 description MAC-ACL-EX (2) Yamaha(config)#endYamaha#Yamaha#show access-list (3) MAC access list 2001    10 deny host 00A0.DE12.3456 any 1 Generate access list #2001 2 Add access list explanatory text 3 Check access list Generate VLAN access map VAM-003 , and set access list #2001 . Yamaha(config)# vlan access-map VAM-003 (1) Yamaha(config-vlan-access-map)# match access-list 2001 (2) Yamaha(config-vlan-access-map)# endYamaha#Yamaha#show vlan access-map (3) Vlan access-map VAM-003    match mac access-list 2001 1 VLAN access map generation 2 Register the access list 3 Check the settings for VLAN access map and access list Apply VLAN access map VAM-003 to VLAN #1000 , and confirm the status. Yamaha(config)#vlan filter VAM-003 1000 in (1) Yamaha(config)#endYamaha#Yamaha#show vlan filter (2) Vlan filter VAM-003 is applied to vlan 1000 in 1 Apply the VLAN access map to the VLAN 2 Check the settings for VLAN access map To change the access list (delete or add a setting), it is necessary to temporarily cancel applying the list to the VLAN interface and the setting in the VLAN access map. For the specific procedure, refer to Example of application to the VLAN interface in IPv4 access list settings . ■ Specify vendor Set VLAN #1000 so that it only denies access from vendor code: 00-A0-DE- - - * (00-A0-DE-00-00-00 to 00-A0-DE-FF-FF-FF). With #2001 as the access list ID, add MAC-ACL-EX as access list explanatory text using. The VLAN access map to be used will be VAM-003 , and access list #2001 will be set. Generate and confirm access list #2001 . Yamaha(config)#access-list 2001 deny 00a0.de00.0000 0000.00ff.ffff any (1) Yamaha(config)#access-list 2001 description MAC-ACL-EX (2) Yamaha(config)#endYamaha#Yamaha#show access-list 2001 (3) MAC access list 2001    10 deny 00A0.DE00.0000 0000.00FF.FFFF any 1 Generate access list #2001 2 Add access list explanatory text 3 Check access list Generate VLAN access map VAM-003 , and set access list #2001 . Yamaha(config)# vlan access-map VAM-003 (1) Yamaha(config-vlan-access-map)# match access-list 2001 (2) Yamaha(config-vlan-access-map)# endYamaha#Yamaha#show vlan access-map (3) Vlan access-map VAM-003    match mac access-list 2001 1 VLAN access map generation 2 Register the access list 3 Check the settings for VLAN access map and access list Apply VLAN access map VAM-003 to VLAN #1000 , and confirm the status. Yamaha(config)#vlan filter VAM-003 1000 in (1) Yamaha(config)#endYamaha#Yamaha#show vlan filter (2) Vlan filter VAM-003 is applied to vlan 1000 in 1 Apply the VLAN access map to the VLAN 2 Check the settings for VLAN access map To change the access list (delete or add a setting), it is necessary to temporarily cancel applying the list to the VLAN interface and the setting in the VLAN access map. For the specific procedure, refer to Example of application to the VLAN interface in IPv4 access list settings .</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution lan/sfp ports for which an access list is configured for received frames cannot belong to a logical interface. access list settings for received frames on an interface cannot be applied to a lan/sfp port that belongs to a logical interface. if access list settings exist for the received frame of a lan/sfp port that belongs to a logical interface in startup config, the settings for the most recent port number will be applied to the logical interface. conditions might not be determined correctly for fragment packets. specifically, if layer 4 information (source port number, destination port number, and various tcp flags) is included in the conditions, correct information cannot be determined because the information is not included in the second and subsequent fragment packets. if there is a possibility of processing fragment packets, do not include layer 4 information in the conditions.</div><div class="display_word">6. Points of Caution LAN/SFP ports for which an access list is configured for received frames cannot belong to a logical interface. Access list settings for received frames on an interface cannot be applied to a LAN/SFP port that belongs to a logical interface. If access list settings exist for the received frame of a LAN/SFP port that belongs to a logical interface in startup config, the settings for the most recent port number will be applied to the logical interface. Conditions might not be determined correctly for fragment packets. Specifically, if layer 4 information (source port number, destination port number, and various TCP flags) is included in the conditions, correct information cannot be determined because the information is not included in the second and subsequent fragment packets. If there is a possibility of processing fragment packets, do not include layer 4 information in the conditions.</div></div><div id="traffic_traffic_acl"><div class="search_title" docfname="traffic_traffic_acl" doctitle="ACL" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation layer 2 function: vlan</div><div class="display_word">7. Related Documentation Layer 2 Function: VLAN</div></div><div id="traffic_traffic_flow_control"><div class="search_title" docfname="traffic_traffic_flow_control" doctitle="Flow" link="#フロー制御">Flow Control</div><div class="search_word">flow control</div><div class="display_word">Flow Control</div></div><div id="traffic_traffic_flow_control"><div class="search_title" docfname="traffic_traffic_flow_control" doctitle="Flow" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview a switching hub initially stores received frames in memory and then performs relay processing. when many frames are sent at the same time and relay processing cannot keep up (a congested state), exceeding the available memory capacity for storage, the frames to be relayed are discarded. this product includes the following two functions to help mitigate such congestion. when ports are operating at full duplex: ieee 802.3x flow control can be enabled. when ports are operating at half duplex: the back pressure function will always be enabled.</div><div class="display_word">1. Function Overview A switching hub initially stores received frames in memory and then performs relay processing. When many frames are sent at the same time and relay processing cannot keep up (a congested state), exceeding the available memory capacity for storage, the frames to be relayed are discarded. This product includes the following two functions to help mitigate such congestion. When ports are operating at full duplex: IEEE 802.3x flow control can be enabled. When ports are operating at half duplex: the back pressure function will always be enabled.</div></div><div id="traffic_traffic_flow_control"><div class="search_title" docfname="traffic_traffic_flow_control" doctitle="Flow" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used bit time on a 10base network, the speed is 10mbps , so 1 bit time = 100 nsec. in the same way, the bit time on 100base is 10 nsec, and on 1000base is 1 nsec. jam signal in half-duplex communications, where data cannot be transmitted and received at the same time, there is a possibility of data collision. the transmitting device monitors the possibility of data collision during transmission. when possible data collision is detected, the device stops transmitting and sends a jam signal. after the jam signal is sent, the device waits for a random interval before resuming transmission. although undefined in ieee, jam signals that use a 32-digit alternating “1” and “0” bit sequence (such as “10101010101010101010101010101010”) are often used.</div><div class="display_word">2. Definition of Terms Used Bit Time On a 10BASE network, the speed is 10Mbps , so 1 bit time = 100 nsec. In the same way, the bit time on 100BASE is 10 nsec, and on 1000BASE is 1 nsec. Jam Signal In half-duplex communications, where data cannot be transmitted and received at the same time, there is a possibility of data collision. The transmitting device monitors the possibility of data collision during transmission. When possible data collision is detected, the device stops transmitting and sends a jam signal. After the jam signal is sent, the device waits for a random interval before resuming transmission. Although undefined in IEEE, jam signals that use a 32-digit alternating “1” and “0” bit sequence (such as “10101010101010101010101010101010”) are often used.</div></div><div id="traffic_traffic_flow_control"><div class="search_title" docfname="traffic_traffic_flow_control" doctitle="Flow" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="traffic_traffic_flow_control"><div class="search_title" docfname="traffic_traffic_flow_control" doctitle="Flow" link="#ieee-8023x-フロー制御">3.1. IEEE 802.3x flow control</div><div class="search_word">3.1. ieee 802.3x flow control for full duplex communication, the mac control protocol with ieee802.3x option can be used. the mac control frame in the diagram below is used for flow control. mac control frame the following flow control operations are performed, based on the restriction start threshold and the restriction cancel threshold. flow control: processing flow this product can be used for either transmitting or receiving mac control frames. the operations for each are shown below. mac control frame transmission processing frames are stored in the received buffer. when the number of the frames exceeds the restriction start threshold, a pause frame with a pause time of 65535 is sent. when the overflow in the received buffer is resolved, and the number of the frames falls below the restriction cancel threshold, a pause frame with a pause time of 0 is sent. mac control frame reception processing when a pause frame with a pause time of 1–65535 is received, the transmission processing will be stopped if the corresponding bit time has elapsed, or if the a pause frame with a pause time of 0 has been received. use the flowcontrol command to enable or disable the flow control (when transmitting/receiving mac control frames). this setting can be made for the system and for each transmitting/receiving lan/sfp port, and is set to “disable” by factory default. in order to enable flow control for an individual port, flow control must be enabled for the system. the tail drop function is disabled when flow control is enabled in the system, except when the stack function is enabled. if the qos function is enabled, flow control cannot be enabled . when the stack function is enabled, only pause frames can be received.</div><div class="display_word">3.1. IEEE 802.3x flow control For full duplex communication, the MAC control protocol with IEEE802.3x option can be used. The MAC control frame in the diagram below is used for flow control. MAC control frame The following flow control operations are performed, based on the restriction start threshold and the restriction cancel threshold. Flow control: processing flow This product can be used for either transmitting or receiving MAC control frames. The operations for each are shown below. MAC control frame transmission processing Frames are stored in the received buffer. When the number of the frames exceeds the restriction start threshold, a PAUSE frame with a pause time of 65535 is sent. When the overflow in the received buffer is resolved, and the number of the frames falls below the restriction cancel threshold, a PAUSE frame with a pause time of 0 is sent. MAC control frame reception processing When a PAUSE frame with a pause time of 1–65535 is received, the transmission processing will be stopped if the corresponding bit time has elapsed, or if the a PAUSE frame with a pause time of 0 has been received. Use the flowcontrol command to enable or disable the flow control (when transmitting/receiving MAC control frames). This setting can be made for the system and for each transmitting/receiving LAN/SFP port, and is set to “disable” by factory default. In order to enable flow control for an individual port, flow control must be enabled for the system. The tail drop function is disabled when flow control is enabled in the system, except when the stack function is enabled. If the Qos function is enabled, flow control cannot be enabled . When the stack function is enabled, only Pause frames can be received.</div></div><div id="traffic_traffic_flow_control"><div class="search_title" docfname="traffic_traffic_flow_control" doctitle="Flow" link="#バックプレッシャー">3.2. Back pressure</div><div class="search_word">3.2. back pressure this product sends a jam signal whenever the receiving buffer of a lan port is about to overflow. with this, the sender waits for a random amount of time as per the csma/cd, and then sends the frames. when the lan port is operating at half duplex , the back pressure function will always be enabled . in addition, when the stack is enabled, jam signals are not sent for communication via the stack port. back pressure processing flow</div><div class="display_word">3.2. Back pressure This product sends a jam signal whenever the receiving buffer of a LAN port is about to overflow. With this, the sender waits for a random amount of time as per the CSMA/CD, and then sends the frames. When the LAN port is operating at half duplex , the back pressure function will always be enabled . In addition, when the stack is enabled, jam signals are not sent for communication via the stack port. Back pressure processing flow</div></div><div id="traffic_traffic_flow_control"><div class="search_title" docfname="traffic_traffic_flow_control" doctitle="Flow" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details, refer to the command reference. operations operating commands set (system) flow control (ieee 802.3x pause send/receive) flowcontrol set (interface) flow control (ieee 802.3x pause send/receive) flowcontrol show flow control operating status show flowcontrol</div><div class="display_word">4. Related Commands Related commands are indicated below. For details, refer to the Command Reference. Operations Operating commands Set (system) flow control (IEEE 802.3x PAUSE send/receive) flowcontrol Set (interface) flow control (IEEE 802.3x PAUSE send/receive) flowcontrol Show flow control operating status show flowcontrol</div></div><div id="traffic_traffic_flow_control"><div class="search_title" docfname="traffic_traffic_flow_control" doctitle="Flow" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution enable flow control on lan port #1. after the function is enabled, check the flow control operating status. yamaha(config)#flowcontrol enableyamaha(config)#interface port1.1yamaha(config-if)#flowcontrol bothyamaha(config-if)#endyamaha#show flowcontrol port1.1port        flowcontrol       rxpause txpause---------   -----------       ------- -------port1.1     both                    0      64</div><div class="display_word">5. Examples of Command Execution Enable flow control on LAN port #1. After the function is enabled, check the flow control operating status. Yamaha(config)#flowcontrol enableYamaha(config)#interface port1.1Yamaha(config-if)#flowcontrol bothYamaha(config-if)#endYamaha#show flowcontrol port1.1Port        FlowControl       RxPause TxPause---------   -----------       ------- -------port1.1     Both                    0      64</div></div><div id="traffic_traffic_flow_control"><div class="search_title" docfname="traffic_traffic_flow_control" doctitle="Flow" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution none</div><div class="display_word">6. Points of Caution None</div></div><div id="traffic_traffic_flow_control"><div class="search_title" docfname="traffic_traffic_flow_control" doctitle="Flow" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation none</div><div class="display_word">7. Related Documentation None</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#qos">QoS</div><div class="search_word">qos</div><div class="display_word">QoS</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview qos (quality of service) is a technology for reserving a specified bandwidth for communications over a network, guaranteeing a fixed speed of communication. application data is classified and grouped, and then forwarded by group priority level, referring to the dscp in the ip header or the cos in the ieee802.1q tag.</div><div class="display_word">1. Function Overview QoS (Quality of Service) is a technology for reserving a specified bandwidth for communications over a network, guaranteeing a fixed speed of communication. Application data is classified and grouped, and then forwarded by group priority level, referring to the DSCP in the IP header or the CoS in the IEEE802.1Q tag.</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used cos (ieee 802.1p class of service) this expresses priority as a 3-bit field in the vlan tag header, with a value from 0–7. also called 802.1p user priority. ip precedence this expresses priority as a 3-bit field in the tos field of the ip header, with a value from 0–7. used to indicate the traffic class of the frame in question, for the device that receives the frame. dscp (diffserv code point) this expresses priority as a 6-bit field in the tos field of the ip header, with a value from 0–63. since dscp uses the same tos field as ip precedence, it is compatible with ip-precedence. used to indicate the traffic class of the frame in question, for the device that receives the frame. default cos this is the cos value that is assigned to an untagged frame for the purpose of internal processing. transmission queue this product has eight transmission queues per port. the transmission queues are numbered from id 0–7, with larger id numbers being given higher priority. trust mode this indicates what will be the basis for deciding (trusting) the transmission queue id. the cos value or dscp value of the received frames can be used to differentiate them, or a priority order specified for each receiving port can be applied. settings can be configured for each lan/sfp port and logical interface. note that the settings for lan/sfp ports that belong to a logical interface cannot be changed. the default status (when qos is enabled) is set to “cos”. transmission queue id conversion table this is a conversion table used when deciding on the transmission queue id from either the cos value or the dscp value. there are two kinds of transmission queue id conversion tables, the cos-transmission queue id conversion table and the dscp-transmission queue id conversion table. each kind is used with its own trust mode. mapping can be freely changed by the user. port priority this is the priority order assigned for each reception port. if the trust mode is “port priority,” frames received at that port are placed in the transmission queue according to the port’s priority setting. class map this defines the conditions by which packets are classified into traffic classes. packets can be associated and used with policy maps, and qos processing (pre-marking, transmission queue specification, metering/policing/remarking) per traffic class can be defined. policy map this is an element for performing a qos processing series on the receiving port. this cannot be used by itself, but rather is associated and used with 1–8 class maps. when a policy map is applied to a lan/sfp port and logical interface, traffic is classified per class map that is associated with the policy map for the packets received on the relevant port. also, qos processing (pre-marking, transmission queue specification, metering/policing/remarking) set per traffic class can be performed. policer this is a group series of metering/policing/remarking settings. there are two types of policers, an individual policer for metering that targets one traffic class, and a group policer that meters multiple traffic classes by putting them together.</div><div class="display_word">2. Definition of Terms Used CoS (IEEE 802.1p Class of Service) This expresses priority as a 3-bit field in the VLAN tag header, with a value from 0–7. Also called 802.1p user priority. IP Precedence This expresses priority as a 3-bit field in the TOS field of the IP header, with a value from 0–7. Used to indicate the traffic class of the frame in question, for the device that receives the frame. DSCP (Diffserv Code Point) This expresses priority as a 6-bit field in the TOS field of the IP header, with a value from 0–63. Since DSCP uses the same TOS field as IP precedence, it is compatible with IP-Precedence. Used to indicate the traffic class of the frame in question, for the device that receives the frame. Default CoS This is the CoS value that is assigned to an untagged frame for the purpose of internal processing. Transmission queue This product has eight transmission queues per port. The transmission queues are numbered from ID 0–7, with larger ID numbers being given higher priority. Trust mode This indicates what will be the basis for deciding (trusting) the transmission queue ID. The CoS value or DSCP value of the received frames can be used to differentiate them, or a priority order specified for each receiving port can be applied. Settings can be configured for each LAN/SFP port and logical interface. Note that the settings for LAN/SFP ports that belong to a logical interface cannot be changed. The default status (when QoS is enabled) is set to “CoS”. Transmission queue ID conversion table This is a conversion table used when deciding on the transmission queue ID from either the CoS value or the DSCP value. There are two kinds of transmission queue ID conversion tables, the CoS-transmission queue ID conversion table and the DSCP-transmission queue ID conversion table. Each kind is used with its own trust mode. Mapping can be freely changed by the user. Port priority This is the priority order assigned for each reception port. If the trust mode is “port priority,” frames received at that port are placed in the transmission queue according to the port’s priority setting. Class map This defines the conditions by which packets are classified into traffic classes. Packets can be associated and used with policy maps, and QoS processing (pre-marking, transmission queue specification, metering/policing/remarking) per traffic class can be defined. Policy map This is an element for performing a QoS processing series on the receiving port. This cannot be used by itself, but rather is associated and used with 1–8 class maps. When a policy map is applied to a LAN/SFP port and logical interface, traffic is classified per class map that is associated with the policy map for the packets received on the relevant port. Also, QoS processing (pre-marking, transmission queue specification, metering/policing/remarking) set per traffic class can be performed. Policer This is a group series of metering/policing/remarking settings. There are two types of policers, an individual policer for metering that targets one traffic class, and a group policer that meters multiple traffic classes by putting them together.</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details</div><div class="display_word">3. Function Details</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#qos-の有効無効制御">3.1. Enabling or disabling QoS control</div><div class="search_word">3.1. enabling or disabling qos control when shipped from the factory, the qos control of this product is set to disable . to enable qos control, use the qos enable command. to disable this, use the no qos command. most qos control commands cannot be executed if qos is not enabled. the qos function status can be checked using the show qos command. in order to enable qos control, the system’s flow control must be disabled.</div><div class="display_word">3.1. Enabling or disabling QoS control When shipped from the factory, the QoS control of this product is set to disable . To enable QoS control, use the qos enable command. To disable this, use the no qos command. Most QoS control commands cannot be executed if QoS is not enabled. The QoS function status can be checked using the show qos command. In order to enable QoS control, the system’s flow control must be disabled.</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#qos-処理フロー">3.2. QoS processing flow</div><div class="search_word">3.2. qos processing flow the qos processing flow is shown below.</div><div class="display_word">3.2. QoS processing flow The QoS processing flow is shown below.</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#送信キューの割り当て">3.3. Transmission queue assignments</div><div class="search_word">3.3. transmission queue assignments when this product receives a frame, it determines the initial value of the transmission queue id according to the cos value or dscp value within the frame and the port priority of the reception port. of the factors such as the frame’s cos value, dscp value, and port priority, the port’s trust mode determines which factor will be the basis for determining the transmission queue. the trust mode can be changed by the qos trust command. the default value (when qos is enabled) is set to cos . the transmission queue is assigned per trust mode , using the following rules. when trust mode is “cos” when the received frame is a frame with a vlan tag, the cos value within the tag is used to determine the transmission queue id. when the received frame is a frame without a vlan tag, the default cos that is managed by this product is used to determine the transmission queue id. the default setting (when qos is enabled) and the default cos are set to “ 0 ”. the setting can be changed using the qos cos command. conversion from the cos value to the transmission queue id is performed by the cos-transmission queue id conversion table. one such table is maintained by the system, and with the default settings (when qos is enabled), the settings are as follows. the setting can be changed using the qos cos-queue command. cos value transmission queue id traffic type 0 2 best effort 1 0 background 2 1 standard(spare) 3 3 excellent effort(business critical) 4 4 controlled load(streaming multimedia) 5 5 video(interactive media) less than 100 msec latency and jitter 6 6 voice(interactive media) less than 10 msec latency and jitter 7 7 network control(reserved traffic) when trust mode is “dscp” the dscp value in the ip header is used to determine the transmission queue id. conversion from the dscp value to the transmission queue id is performed by the dscp-transmission queue id conversion table. one such table is maintained by the system, and with the default settings (when qos is enabled), the settings are as follows. the setting can be changed using the qos dscp-queue command. dscp value transmission queue id traffic type 0 - 7 2 best effort 8 –15 0 background 16 - 23 1 standard(spare) 24 - 31 3 excellent effort(business critical) 32 - 39 4 controlled load(streaming multimedia) 40 - 47 5 video(interactive media) less than 100 msec latency and jitter 48 - 55 6 voice(interactive media) less than 10 msec latency and jitter 56 - 63 7 network control(reserved traffic) when trust mode is “port priority” the transmission queue id is determined by the port priority . by default (when qos is enabled), port priority is set to 2 . the setting can be changed using the qos port-priority-queue command. if the trust mode is “cos” or “dscp,” the transmission queue id might be reassigned due to qos processing (see below) by the policy map. in this case, the new transmission queue id is reassigned based on the transmission queue id conversion table that corresponds to the port’s trust mode. pre-marking refer to “ pre-marking ” for details. specify transmission queue when the trust mode is “cos”, specify the cos value that corresponds to the transmission queue id, using the set cos-queue command. when the trust mode is “dscp”, specify the dscp value that corresponds to the transmission queue id, using the set dscp-queue command. remark refer to metering/policing/remarking for details. if the trust mode is “port priority,” the transmission queue id cannot be changed by the policy map’s qos processing. (it is not possible to apply a policy map that includes pre-marking, transmission queue specification, and remarking settings.)</div><div class="display_word">3.3. Transmission queue assignments When this product receives a frame, it determines the initial value of the transmission queue ID according to the CoS value or DSCP value within the frame and the port priority of the reception port. Of the factors such as the frame’s CoS value, DSCP value, and port priority, the port’s trust mode determines which factor will be the basis for determining the transmission queue. The trust mode can be changed by the qos trust command. The default value (when QoS is enabled) is set to CoS . The transmission queue is assigned per trust mode , using the following rules. When trust mode is “CoS” When the received frame is a frame with a VLAN tag, the CoS value within the tag is used to determine the transmission queue ID. When the received frame is a frame without a VLAN tag, the default CoS that is managed by this product is used to determine the transmission queue ID. The default setting (when QoS is enabled) and the default CoS are set to “ 0 ”. The setting can be changed using the qos cos command. Conversion from the CoS value to the transmission queue ID is performed by the CoS-transmission queue ID conversion table. One such table is maintained by the system, and with the default settings (when QoS is enabled), the settings are as follows. The setting can be changed using the qos cos-queue command. CoS value Transmission queue ID Traffic Type 0 2 Best Effort 1 0 Background 2 1 Standard(spare) 3 3 Excellent Effort(Business Critical) 4 4 Controlled Load(Streaming Multimedia) 5 5 Video(Interactive Media) less than 100 msec latency and jitter 6 6 Voice(Interactive Media) less than 10 msec latency and jitter 7 7 Network Control(Reserved Traffic) When trust mode is “DSCP” The DSCP value in the IP header is used to determine the transmission queue ID. Conversion from the DSCP value to the transmission queue ID is performed by the DSCP-transmission queue ID conversion table. One such table is maintained by the system, and with the default settings (when QoS is enabled), the settings are as follows. The setting can be changed using the qos dscp-queue command. DSCP value Transmission queue ID Traffic Type 0 - 7 2 Best Effort 8 –15 0 Background 16 - 23 1 Standard(spare) 24 - 31 3 Excellent Effort(Business Critical) 32 - 39 4 Controlled Load(Streaming Multimedia) 40 - 47 5 Video(Interactive Media) less than 100 msec latency and jitter 48 - 55 6 Voice(Interactive Media) less than 10 msec latency and jitter 56 - 63 7 Network Control(Reserved Traffic) When trust mode is “port priority” The transmission queue ID is determined by the port priority . By default (when QoS is enabled), port priority is set to 2 . The setting can be changed using the qos port-priority-queue command. If the trust mode is “CoS” or “DSCP,” the transmission queue ID might be reassigned due to QoS processing (see below) by the policy map. In this case, the new transmission queue ID is reassigned based on the transmission queue ID conversion table that corresponds to the port’s trust mode. Pre-marking Refer to “ Pre-marking ” for details. Specify transmission queue When the trust mode is “CoS”, specify the CoS value that corresponds to the transmission queue ID, using the set cos-queue command. When the trust mode is “DSCP”, specify the DSCP value that corresponds to the transmission queue ID, using the set dscp-queue command. Remark Refer to Metering/policing/remarking for details. If the trust mode is “port priority,” the transmission queue ID cannot be changed by the policy map’s QoS processing. (It is not possible to apply a policy map that includes pre-marking, transmission queue specification, and remarking settings.)</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#送信キューの割り当てスイッチ本体から送信されるフレーム">3.4. Transmission queue assignments (frames sent from the network switch unit)</div><div class="search_word">3.4. transmission queue assignments (frames sent from the network switch unit) as an exception to the transmission queue assignments, frames sent from the network switch unit (cpu) are automatically assigned the transmission queue determined by the system . (they are not given transmission queue assignments based on the trust mode .) the qos queue sent-from-cpu command can be used to change the transmission queue that is assigned, and by default the transmission queue id is set to 7 .</div><div class="display_word">3.4. Transmission queue assignments (frames sent from the network switch unit) As an exception to the transmission queue assignments, frames sent from the network switch unit (CPU) are automatically assigned the transmission queue determined by the system . (They are not given transmission queue assignments based on the trust mode .) The qos queue sent-from-cpu command can be used to change the transmission queue that is assigned, and by default the transmission queue ID is set to 7 .</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#トラフィック分類">3.5. Traffic classification</div><div class="search_word">3.5. traffic classification traffic classification is a function to classify received frames, based on a class map that defines the conditions of the ip header, tcp header, and so on. the conditions that can be classified and the commands for settings are shown in the table below. conditions that can be classified, and commands for settings classification condition condition-setting command class map setting command number that can be registered per class map source/destination mac address access-list (*note 3) match access-list 1 source/destination ip address 1 ip protocol type (*note 1) 1 ethernet frame type number match ethertype 1 cos value for vlan tag header match cos 8 precedence value for ip header match ip-precedence 8 dscp value for ip header match ip-dscp 8 vlan id (*note 2) match vlan, match vlan-range 30 (*note 1) ipv6 is not subject to classification by ip protocol type. (*note 2) does not include isolated or community vlans in a private vlan. (*note 3) up to 39 conditions can be set in the access list for traffic classification. traffic is classified per class map . one classification condition type can be set for one class map . policer-based qos processing (metering/policing/remarking) and pre-marking, as well as specifying the transmission queue can be done for frames that match the conditions. if classification conditions are not specified, all frames are classified into the corresponding traffic class. for classification based on cos, ip precedence, dscp, and the vlan id, multiple classifications can be made for one class map. associating multiple class maps to a policy map will make it possible to classify complex traffic for the receiving port. up to eight class maps can be associated to one policy map . information for the class map that was set can be confirmed using the show class-map command. information for the policy map that was set can be confirmed using the show policy-map command. use the show qos map-status command to check the port to which the policy map is applied, and the policy map to which the class map is associated.</div><div class="display_word">3.5. Traffic classification Traffic classification is a function to classify received frames, based on a class map that defines the conditions of the IP header, TCP header, and so on. The conditions that can be classified and the commands for settings are shown in the table below. Conditions that can be classified, and commands for settings Classification condition Condition-setting command Class map setting command Number that can be registered per class map Source/destination MAC address access-list (*Note 3) match access-list 1 Source/destination IP address 1 IP protocol type (*Note 1) 1 Ethernet frame type number match ethertype 1 CoS value for VLAN tag header match cos 8 Precedence value for IP header match ip-precedence 8 DSCP value for IP header match ip-dscp 8 VLAN ID (*Note 2) match vlan, match vlan-range 30 (*Note 1) IPv6 is not subject to classification by IP protocol type. (*Note 2) Does not include isolated or community VLANs in a private VLAN. (*Note 3) Up to 39 conditions can be set in the access list for traffic classification. Traffic is classified per class map . One classification condition type can be set for one class map . Policer-based QoS processing (metering/policing/remarking) and pre-marking, as well as specifying the transmission queue can be done for frames that match the conditions. If classification conditions are not specified, all frames are classified into the corresponding traffic class. For classification based on CoS, IP precedence, DSCP, and the VLAN ID, multiple classifications can be made for one class map. Associating multiple class maps to a policy map will make it possible to classify complex traffic for the receiving port. Up to eight class maps can be associated to one policy map . Information for the class map that was set can be confirmed using the show class-map command. Information for the policy map that was set can be confirmed using the show policy-map command. Use the show qos map-status command to check the port to which the policy map is applied, and the policy map to which the class map is associated.</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#プレマーキング">3.6. Pre-marking</div><div class="search_word">3.6. pre-marking pre-marking is a function to change (assign) the cos, ip precedence, and dscp values for received frames classified into traffic classes. pre-marking is set using the policy map and class mode commands shown below. pre-marking setting commands pre-marking target command for settings cos set cos ip precedence set ip-precedence dscp set ip-dscp the dscp values that can be premarked include the value recommended in the rfc and those not found in the rfc, for a total of four . (this rule also applies to dscp values that are used in remarking.) only one pre-marking setting can be made for a class map . this cannot be used together when specifying a transmission queue (set cos-queue, set ip-dscp-queue). when pre-marking, the transmission queue will be reassigned based on the changed value and the transmission queue id conversion table that corresponds to the trust mode.</div><div class="display_word">3.6. Pre-marking Pre-marking is a function to change (assign) the CoS, IP precedence, and DSCP values for received frames classified into traffic classes. Pre-marking is set using the policy map and class mode commands shown below. Pre-marking setting commands Pre-marking target Command for settings CoS set cos IP Precedence set ip-precedence DSCP set ip-dscp The DSCP values that can be premarked include the value recommended in the RFC and those not found in the RFC, for a total of four . (This rule also applies to DSCP values that are used in remarking.) Only one pre-marking setting can be made for a class map . This cannot be used together when specifying a transmission queue (set cos-queue, set ip-dscp-queue). When pre-marking, the transmission queue will be reassigned based on the changed value and the transmission queue ID conversion table that corresponds to the trust mode.</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#メータリングポリシングリマーキング">3.7. Metering/policing/remarking</div><div class="search_word">3.7. metering/policing/remarking bandwidth can be controlled by measuring the bandwidth used, and discarding or reprioritizing packets according to the measurement results. the processing series for metering, policing and remarking is done per “ policer ”. processing summary for bandwidth control process name summary metering this measures how much bandwidth is being taken up by the classified traffic based on the traffic rate and burst size, and classifies this into three bandwidth classes (green, yellow and red). actions such as discarding (policing) and remarking can be specified for each classified bandwidth class. policing the bandwidth usage can be kept within a certain amount by discarding frames, using bandwidth class information. remark the cos, ip precedence, and dscp values for a frame can be changed using the bandwidth class information. metering, policing, and remarking cannot be performed for the following logical interfaces. logical interfaces grouped by ports 1 to 24, 49, and 50 (ports in the blue frame below) and ports 25 to 48, 51, and 52 (ports in the green frame below) on swx3200-52gt logical interface grouped across the member switches that make up the stack (green i/f below)</div><div class="display_word">3.7. Metering/policing/remarking Bandwidth can be controlled by measuring the bandwidth used, and discarding or reprioritizing packets according to the measurement results. The processing series for metering, policing and remarking is done per “ policer ”. Processing summary for bandwidth control Process name Summary Metering This measures how much bandwidth is being taken up by the classified traffic based on the traffic rate and burst size, and classifies this into three bandwidth classes (green, yellow and red). Actions such as discarding (policing) and remarking can be specified for each classified bandwidth class. Policing The bandwidth usage can be kept within a certain amount by discarding frames, using bandwidth class information. Remark The CoS, IP precedence, and DSCP values for a frame can be changed using the bandwidth class information. Metering, policing, and remarking cannot be performed for the following logical interfaces. Logical interfaces grouped by Ports 1 to 24, 49, and 50 (ports in the blue frame below) and Ports 25 to 48, 51, and 52 (ports in the green frame below) on SWX3200-52GT Logical interface grouped across the member switches that make up the stack (green I/F below)</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#ポリサーの種類">3.7.1. Policer types</div><div class="search_word">3.7.1. policer types there are two types of policers: an individual policer that performs metering/policing/remarking on one traffic class, and an aggregate policer that performs these actions on multiple aggregated traffic classes. individual policer metering/policing/remarking is done per traffic class. the settings are specified using police and remark-map commands in the policy map/class mode. aggregate policer metering/policing/remarking is done on multiple traffic classes, which are aggregated. the aggregate policer can be created using the aggregate-police command, and the content can be specified by the aggregate policer mode’s police command and remark-map command. to apply a created aggregate policer to a traffic class, use the police-aggregate command. the commands used to make settings for an individual policer and an aggregate policer respectively are as follows. content of setting individual policer aggregate policer create policer - aggregate-police policer settings (metering/policing/remarking) police single-rate, police twin-rate (policy map class mode) police single-rate, police twin-rate (aggregate policer mode) apply policer to traffic class police-aggregate detailed remarking settings remark-map (policy map/class mode) remark-map (aggregate policer mode)</div><div class="display_word">3.7.1. Policer types There are two types of policers: an individual policer that performs metering/policing/remarking on one traffic class, and an aggregate policer that performs these actions on multiple aggregated traffic classes. Individual policer Metering/policing/remarking is done per traffic class. The settings are specified using police and remark-map commands in the policy map/class mode. Aggregate policer Metering/policing/remarking is done on multiple traffic classes, which are aggregated. The aggregate policer can be created using the aggregate-police command, and the content can be specified by the aggregate policer mode’s police command and remark-map command. To apply a created aggregate policer to a traffic class, use the police-aggregate command. The commands used to make settings for an individual policer and an aggregate policer respectively are as follows. Content of setting Individual policer Aggregate policer Create policer - aggregate-police Policer settings (Metering/policing/remarking) police single-rate, police twin-rate (Policy map class mode) police single-rate, police twin-rate (Aggregate policer mode) Apply policer to traffic class police-aggregate Detailed remarking settings remark-map (Policy map/class mode) remark-map (Aggregate policer mode)</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#メータリングの設定">3.7.2. Metering settings</div><div class="search_word">3.7.2. metering settings there are two types of metering: single rate policer (rfc2697) and twin rate policer (rfc2698). the type of metering to use and the control parameters are specified using the police command (policy map/class mode or aggregate policer mode). single rate policer (rfc2697) single rate policers separate the frames within a traffic class into three bandwidth classes: “green” (conforming) , “yellow” (exceeding) or “red” (violating) , based on the traffic rate (cir) and burst size (cbs, ebs) . single rage policer control parameters if the burst size was not set appropriately, the throughput might decrease in some cases. parameter explanation cir (committed information rate) this is the amount of tokens that is periodically stored in buckets. the amount can be specified in the range of 1–102,300,000 kbps. cbs (committed burst size) this is the amount of traffic that can be removed at one time from the first token bucket (a conforming token bucket). the amount can be specified in the range of 11–2,097,120 kbyte. ebs (exceed burst size) this is the amount of traffic that can be removed at one time from the second token bucket (an exceeding token bucket). the amount can be specified in the range of 11–2,097,120 kbyte. twin rate policer (rfc2698) twin rate policers separate the frames within a traffic class into three bandwidth classes: “green” (conforming) , “yellow” (exceeding) or “red” (violating) , based on the traffic rate (cir, pir) and burst size (cbs, pbs) . twin rage policer control parameters if the burst size was not set appropriately, the throughput might decrease in some cases. parameter explanation cir (committed information rate) this is the amount of tokens periodically stored in the second token bucket (confirming token bucket). the amount can be specified in the range of 1–102,300,000 kbps. pir (peak information rate) this is the amount of tokens periodically stored in the first token bucket (peak token bucket). the amount can be specified in the range of 1–102,300,000 kbps. however, a value smaller than the cir cannot be specified. cbs (committed burst size) this is the amount of token traffic that can be removed at one time from the conforming token bucket. the amount can be specified in the range of 11–2,097,120 kbyte. pbs (peak burst size) this is the amount of token traffic that can be removed at one time from the peak token bucket. the amount can be specified in the range of 11–2,097,120 kbyte.</div><div class="display_word">3.7.2. Metering settings There are two types of metering: single rate policer (RFC2697) and twin rate policer (RFC2698). The type of metering to use and the control parameters are specified using the police command (policy map/class mode or aggregate policer mode). Single rate policer (RFC2697) Single rate policers separate the frames within a traffic class into three bandwidth classes: “green” (conforming) , “yellow” (exceeding) or “red” (violating) , based on the traffic rate (CIR) and burst size (CBS, EBS) . Single rage policer control parameters If the burst size was not set appropriately, the throughput might decrease in some cases. Parameter Explanation CIR (Committed Information Rate) This is the amount of tokens that is periodically stored in buckets. The amount can be specified in the range of 1–102,300,000 kbps. CBS (Committed Burst Size) This is the amount of traffic that can be removed at one time from the first token bucket (a conforming token bucket). The amount can be specified in the range of 11–2,097,120 kByte. EBS (Exceed Burst Size) This is the amount of traffic that can be removed at one time from the second token bucket (an exceeding token bucket). The amount can be specified in the range of 11–2,097,120 kByte. Twin rate policer (RFC2698) Twin rate policers separate the frames within a traffic class into three bandwidth classes: “green” (conforming) , “yellow” (exceeding) or “red” (violating) , based on the traffic rate (CIR, PIR) and burst size (CBS, PBS) . Twin rage policer control parameters If the burst size was not set appropriately, the throughput might decrease in some cases. Parameter Explanation CIR (Committed Information Rate) This is the amount of tokens periodically stored in the second token bucket (confirming token bucket). The amount can be specified in the range of 1–102,300,000 kbps. PIR (Peak Information Rate) This is the amount of tokens periodically stored in the first token bucket (peak token bucket). The amount can be specified in the range of 1–102,300,000 kbps. However, a value smaller than the CIR cannot be specified. CBS (Committed Burst Size) This is the amount of token traffic that can be removed at one time from the conforming token bucket. The amount can be specified in the range of 11–2,097,120 kByte. PBS (Peak Burst Size) This is the amount of token traffic that can be removed at one time from the peak token bucket. The amount can be specified in the range of 11–2,097,120 kByte.</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#メータリングアクションポリシングリマーキングの設定">3.7.3. Metering action (policing/remarking) settings</div><div class="search_word">3.7.3. metering action (policing/remarking) settings to specify the action for a bandwidth class that was categorized by metering, use the police command (in policy map/class mode or aggregate policer mode). this product lets you define the following actions for each bandwidth class. specifying bandwidth class actions bandwidth class forward discard remark green yes no no yellow yes yes ○ (only one or the other) red no yes detailed remarking settings are specified using the remark-map command (policy map/class mode or aggregate policer mode). as with pre-marking, remarking to dscp values can use the value recommended by rfc (refer to separate table 1. “standard phb (rfc recommended value)” and those not found in the rfc, for total of four . when remarking, the transmission queue will be reassigned based on the changed value and the transmission queue id conversion table that corresponds to the trust mode. if metering is not done, all frames that have been classified into traffic classes will be handled as the green bandwidth class.</div><div class="display_word">3.7.3. Metering action (policing/remarking) settings To specify the action for a bandwidth class that was categorized by metering, use the police command (in policy map/class mode or aggregate policer mode). This product lets you define the following actions for each bandwidth class. Specifying bandwidth class actions Bandwidth class Forward Discard Remark Green Yes No No Yellow Yes Yes ○ (only one or the other) Red No Yes Detailed remarking settings are specified using the remark-map command (policy map/class mode or aggregate policer mode). As with pre-marking, remarking to DSCP values can use the value recommended by RFC (refer to separate table 1. “Standard PHB (RFC recommended value)” and those not found in the RFC, for total of four . When remarking, the transmission queue will be reassigned based on the changed value and the transmission queue ID conversion table that corresponds to the trust mode. If metering is not done, all frames that have been classified into traffic classes will be handled as the green bandwidth class.</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#送信キューへの格納">3.8. Storing in the transmission queue</div><div class="search_word">3.8. storing in the transmission queue frames are stored in the transmission queue that is finally determined through a series of qos processing. in order to resolve transmission queue congestion, this product provides a system to select and discard frames. this product uses the tail drop method to resolve overflow in the transmission queue. when the threshold values shown below for the bandwidth class that is classified by metering have been exceeded, the frame in question will be discarded. frames discarded by tail drop are counted by the frame counter. bandwidth class tail drop threshold value (%) green + yellow 100% red 60% tail drop is disabled only if the stack function is disabled and flow control is enabled. it is not possible to change the threshold value. the usage of the transmission queue can be checked using the show qos queue-counters command. the number of packets discarded by tail drop can be checked using the show interface, show frame-counter command.</div><div class="display_word">3.8. Storing in the transmission queue Frames are stored in the transmission queue that is finally determined through a series of QoS processing. In order to resolve transmission queue congestion, this product provides a system to select and discard frames. This product uses the tail drop method to resolve overflow in the transmission queue. When the threshold values shown below for the bandwidth class that is classified by metering have been exceeded, the frame in question will be discarded. Frames discarded by tail drop are counted by the frame counter. Bandwidth class Tail drop threshold value (%) Green + Yellow 100% Red 60% Tail drop is disabled only if the stack function is disabled and flow control is enabled. It is not possible to change the threshold value. The usage of the transmission queue can be checked using the show qos queue-counters command. The number of packets discarded by tail drop can be checked using the show interface, show frame-counter command.</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#スケジューリング">3.9. Scheduling</div><div class="search_word">3.9. scheduling scheduling is used to determine what rules are used to send out the frames that are stored in the transmission queue. appropriate control of the scheduling along with the system to control congestion will help ensure qos. (inappropriate scheduling will result in degradation of qos.) this product supports two types of scheduling for the transmission queue, the strict priority system (sp) and the weighted round-robin (wrr) system. sp and wrr can also be integrated in the interface and used together. (when doing so, sp will be given priority during processing.) strict priority system (sp: strict priority) the higher the queue priority, the higher the transmission priority. when a frame is stored in a high-priority queue, it can never be transmitted from a lower-priority queue. weighted round-robin system (wrr: weighted round robin) each queue is assigned a weight and transmits frames accordingly. a weight of 1–32 can be set. frames can also be transmitted from a lower-priority queue, within a specified percentage. the transmission queue settings are made for the entire system, not for each interface. use the qos wrr-weight command to set the weight. the default setting (when qos is enabled) and the scheduling setting is “ sp ” for all queues.</div><div class="display_word">3.9. Scheduling Scheduling is used to determine what rules are used to send out the frames that are stored in the transmission queue. Appropriate control of the scheduling along with the system to control congestion will help ensure QoS. (Inappropriate scheduling will result in degradation of QoS.) This product supports two types of scheduling for the transmission queue, the strict priority system (SP) and the weighted round-robin (WRR) system. SP and WRR can also be integrated in the interface and used together. (When doing so, SP will be given priority during processing.) Strict priority system (SP: Strict Priority) The higher the queue priority, the higher the transmission priority. When a frame is stored in a high-priority queue, it can never be transmitted from a lower-priority queue. Weighted round-robin system (WRR: Weighted Round Robin) Each queue is assigned a weight and transmits frames accordingly. A weight of 1–32 can be set. Frames can also be transmitted from a lower-priority queue, within a specified percentage. The transmission queue settings are made for the entire system, not for each interface. Use the qos wrr-weight command to set the weight. The default setting (when QoS is enabled) and the scheduling setting is “ SP ” for all queues.</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#シェーピング">3.10. Shaping</div><div class="search_word">3.10. shaping if a frame is forwarded from a broadband network to a narrowband network at the same transmission speed when connecting to a network with different bandwidth, the frame cannot be forwarded, which may result in insufficient bandwidth. shaping is a function that monitors the frame transmission speed, and restricts the forwarding rate to a specific amount by temporarily buffering frames with a speed that exceeds the limit, and then transmitting them. shaping on this product is realized by using a single token bucket. single token bucket shaping can be specified for individual ports and for individual queues, respectively using the following commands. object of shaping command for settings by port traffic-shape rate by transmission queue traffic-shape queue rate specify the upper limit of the transmission rate (cir) and the burst size (bc). upper limit of transmission rate (cir): can be specified from 18 to 1,000,000 kbps . burst size (bc): can be specified from 4 to 16,000 kbyte . however, this is specified in 4 kbyte units. if shaping is used both by queue and by port, shaping by port is applied after shaping by queue. the default setting (when qos is enabled) and the shaping setting is “ disable ” for all ports and all queues.</div><div class="display_word">3.10. Shaping If a frame is forwarded from a broadband network to a narrowband network at the same transmission speed when connecting to a network with different bandwidth, the frame cannot be forwarded, which may result in insufficient bandwidth. Shaping is a function that monitors the frame transmission speed, and restricts the forwarding rate to a specific amount by temporarily buffering frames with a speed that exceeds the limit, and then transmitting them. Shaping on this product is realized by using a single token bucket. Single token bucket Shaping can be specified for individual ports and for individual queues, respectively using the following commands. Object of shaping Command for settings By port traffic-shape rate By transmission queue traffic-shape queue rate Specify the upper limit of the transmission rate (CIR) and the burst size (BC). Upper limit of transmission rate (CIR): Can be specified from 18 to 1,000,000 kbps . Burst size (BC): Can be specified from 4 to 16,000 kbyte . However, this is specified in 4 Kbyte units. If shaping is used both by queue and by port, shaping by port is applied after shaping by queue. The default setting (when QoS is enabled) and the shaping setting is “ disable ” for all ports and all queues.</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#web会議アプリケーション向け最適設定">3.11. Optimizing web conference application settings</div><div class="search_word">3.11. optimizing web conference application settings qos settings for web conference application software can be configured easily via the web gui. by merely using simple operations to select the web conference application to use, communication can be prioritized for that web conference application, such as zoom meetings or microsoft teams. page for optimizing web conference application settings optimizing web conference application settings involves configuring the following settings. enable qos. set the trust mode for all ports to dscp. assign the dscp value for the web conference application to be optimized to a high-priority sending queue. the dscp values used for web conference applications are indicated below. to use the web conference application settings to change the dscp value used by the web conference application to a non-default value, use the qos dscp-queue command to change the link between the dscp value and sending queue. zoom meetings 56 (audio) 40 (video/screen sharing) microsoft teams 46 (audio) 34 (video) 18 (application/screen sharing) assign the dscp value not used by the web conference application being optimized to the lowest-priority sending queue. change the scheduling mode for all sending queues to the absolute priority method. this web conference application setting optimization function includes functionality for configuring qos settings for individual switches. to fully maximize the benefits of qos settings, they must be configured for the entire network, including the router, at the same time. if the dscp value for the web conference application was changed to a non-default value, also change the dscp sending queue assignment settings separately.</div><div class="display_word">3.11. Optimizing web conference application settings QoS settings for web conference application software can be configured easily via the Web GUI. By merely using simple operations to select the web conference application to use, communication can be prioritized for that web conference application, such as Zoom Meetings or Microsoft Teams. Page for optimizing web conference application settings Optimizing web conference application settings involves configuring the following settings. Enable QoS. Set the trust mode for all ports to DSCP. Assign the DSCP value for the web conference application to be optimized to a high-priority sending queue. The DSCP values used for web conference applications are indicated below. To use the web conference application settings to change the DSCP value used by the web conference application to a non-default value, use the qos dscp-queue command to change the link between the DSCP value and sending queue. Zoom Meetings 56 (Audio) 40 (Video/Screen sharing) Microsoft Teams 46 (Audio) 34 (Video) 18 (Application/Screen sharing) Assign the DSCP value not used by the web conference application being optimized to the lowest-priority sending queue. Change the scheduling mode for all sending queues to the absolute priority method. This web conference application setting optimization function includes functionality for configuring QoS settings for individual switches. To fully maximize the benefits of QoS settings, they must be configured for the entire network, including the router, at the same time. If the DSCP value for the web conference application was changed to a non-default value, also change the DSCP sending queue assignment settings separately.</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#別表1-標準-phb-rfc-推奨値">3.12. Separate table 1: Standard PHB (RFC recommended value)</div><div class="search_word">3.12. separate table 1: standard phb (rfc recommended value) phb dscp value rfc default 0 rfc2474 cs (class selector) cs0 0 rfc2474 cs1 8 cs2 16 cs3 24 cs4 32 cs5 40 cs6 48 cs7 56 af (assured forwarding) af11 10 rfc2597 af12 12 af13 14 af21 18 af22 20 af23 22 af31 26 af32 28 af33 30 af41 34 af42 36 af43 38 ef (expedited forwarding) 46 rfc2598</div><div class="display_word">3.12. Separate table 1: Standard PHB (RFC recommended value) PHB DSCP value RFC Default 0 RFC2474 CS (Class Selector) CS0 0 RFC2474 CS1 8 CS2 16 CS3 24 CS4 32 CS5 40 CS6 48 CS7 56 AF (Assured Forwarding) AF11 10 RFC2597 AF12 12 AF13 14 AF21 18 AF22 20 AF23 22 AF31 26 AF32 28 AF33 30 AF41 34 AF42 36 AF43 38 EF (Expedited Forwarding) 46 RFC2598</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details, refer to the command reference. operations operating commands enabling or disabling qos control qos enable set default cos qos cos change trust mode qos trust generate policy map for received frames policy-map apply policy map for received frames service-policy input show status of qos function setting show qos show qos information for lan/sfp port show qos interface show egress queue usage ratio show qos queue-counters show policy map information show policy-map show map status show qos map-status set cos-transmission queue id conversion table qos cos-queue set dscp-transmission queue id conversion table qos dscp-queue set port priority order qos port-priority-queue set priority order of frames sent from the network switch unit qos queue sent-from-cpu generate class map (traffic category conditions) class-map associate class map class set traffic classification conditions (access-group) match access-list set traffic classification conditions (cos) match cos set traffic classification conditions (tos precedence) match ip-precedence set traffic classification conditions (dscp) match ip-dscp set traffic classification conditions (ethernet type) match ethertype set traffic classification conditions (vlan id) match vlan set traffic classification conditions (vlan id range) match vlan-range show class map information show class-map set pre-marking (cos) set cos set pre-marking (tos precedence) set ip-precedence set pre-marking (dscp) set ip-dscp set individual policer / aggregate policer (single rate) police signle-rate set individual policer / aggregate policer (twin rate) police twin-rate set remarking for individual policer / aggregate policer remark-map create aggregate policer aggregate-police show aggregate policer show aggregate-police apply aggregate policer police-aggregate show metering counter show qos metering-counters clear metering counter clear qos metering-counters set egress queue (cos-queue) set cos-queue set egress queue (dscp-queue) set ip-dscp-queue set egress queue scheduling qos wrr-weight set traffic shaping (individual port) traffic-shape rate set traffic shaping (individual queue) traffic-shape queue rate</div><div class="display_word">4. Related Commands Related commands are indicated below. For details, refer to the Command Reference. Operations Operating commands Enabling or disabling QoS control qos enable Set default CoS qos cos Change trust mode qos trust Generate policy map for received frames policy-map Apply policy map for received frames service-policy input Show status of QoS function setting show qos Show QoS information for LAN/SFP port show qos interface Show egress queue usage ratio show qos queue-counters Show policy map information show policy-map Show map status show qos map-status Set CoS-transmission queue ID conversion table qos cos-queue Set DSCP-transmission queue ID conversion table qos dscp-queue Set port priority order qos port-priority-queue Set priority order of frames sent from the network switch unit qos queue sent-from-cpu Generate class map (traffic category conditions) class-map Associate class map class Set traffic classification conditions (access-group) match access-list Set traffic classification conditions (CoS) match cos Set traffic classification conditions (TOS precedence) match ip-precedence Set traffic classification conditions (DSCP) match ip-dscp Set traffic classification conditions (Ethernet Type) match ethertype Set traffic classification conditions (VLAN ID) match vlan Set traffic classification conditions (VLAN ID range) match vlan-range Show class map information show class-map Set pre-marking (CoS) set cos Set pre-marking (TOS precedence) set ip-precedence Set pre-marking (DSCP) set ip-dscp Set individual policer / aggregate policer (single rate) police signle-rate Set individual policer / aggregate policer (twin rate) police twin-rate Set remarking for individual policer / aggregate policer remark-map Create aggregate policer aggregate-police Show aggregate policer show aggregate-police Apply aggregate policer police-aggregate Show metering counter show qos metering-counters Clear metering counter clear qos metering-counters Set egress queue (CoS-Queue) set cos-queue Set egress queue (DSCP-Queue) set ip-dscp-queue Set egress queue scheduling qos wrr-weight Set traffic shaping (individual port) traffic-shape rate Set traffic shaping (individual queue) traffic-shape queue rate</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution</div><div class="display_word">5. Examples of Command Execution</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#dscp-値を使用した優先制御sp">5.1. Priority control (SP) using DSCP values</div><div class="search_word">5.1. priority control (sp) using dscp values this example allocates the transmission queue based on the dscp value of the frame, for priority control (sp). when the dscp = 56, 46, 8, 0 frame is received, large frames for dscp values from lan port #3 will be processed with priority by sp priority control. dscp priority control (sp): setting example prioritizing the input frame is done as follows. dscp = 56 frame is set at priority level 7 dscp = 46 frame is set at priority level 5 dscp = 8 frame is set at priority level 1 dscp = 0 frame is set at priority level 0 enable qos and set the trust mode for the reception ports (lan ports #1 and #2). yamaha(config)#qos enable (1) yamaha(config)#interface port1.1 (2) yamaha(config-if)#qos trust dscp (3) yamaha(config-if)#exityamaha(config)#interface port1.2 (4) yamaha(config-if)#qos trust dscp (5) yamaha(config-if)#exit 1 enable qos 2 setting for lan port #1 3 change the trust mode to dscp 4 setting for lan port #2 5 change the trust mode to dscp set the dscp - transmission queue id conversion table. as the transmission queue id corresponding to dscp value = 46, 56 is the default, there is no need to make this setting, but it is listed for purposes of clarity. yamaha(config)#qos dscp-queue 56 7 (1) yamaha(config)#qos dscp-queue 46 5 (2) yamaha(config)#qos dscp-queue 8 1 (3) yamaha(config)#qos dscp-queue 0 0 (4) 1 store frames with dscp = 56 in transmission queue #7 2 store frames with dscp = 46 in transmission queue #5 3 store frames with dscp = 8 in transmission queue #1 4 store frames with dscp = 0 in transmission queue #0 this sets the scheduling method per transmission queue. as this is the default, there is no need to make this setting, but it is listed for purposes of clarity. yamaha(config)# no qos wrr-weight 7 (1) yamaha(config)# no qos wrr-weight 5 (2) yamaha(config)# no qos wrr-weight 1 (3) yamaha(config)# no qos wrr-weight 0 (4) 1 queue: 7 sp method 2 queue: 5 sp method 3 queue: 1 sp method 4 queue: 0 sp method</div><div class="display_word">5.1. Priority control (SP) using DSCP values This example allocates the transmission queue based on the DSCP value of the frame, for priority control (SP). When the DSCP = 56, 46, 8, 0 frame is received, large frames for DSCP values from LAN port #3 will be processed with priority by SP priority control. DSCP priority control (SP): setting example Prioritizing the input frame is done as follows. DSCP = 56 frame is set at priority level 7 DSCP = 46 frame is set at priority level 5 DSCP = 8 frame is set at priority level 1 DSCP = 0 frame is set at priority level 0 Enable QoS and set the trust mode for the reception ports (LAN ports #1 and #2). Yamaha(config)#qos enable (1) Yamaha(config)#interface port1.1 (2) Yamaha(config-if)#qos trust dscp (3) Yamaha(config-if)#exitYamaha(config)#interface port1.2 (4) Yamaha(config-if)#qos trust dscp (5) Yamaha(config-if)#exit 1 Enable QoS 2 Setting for LAN port #1 3 Change the trust mode to DSCP 4 Setting for LAN port #2 5 Change the trust mode to DSCP Set the DSCP - transmission queue ID conversion table. As the transmission queue ID corresponding to DSCP value = 46, 56 is the default, there is no need to make this setting, but it is listed for purposes of clarity. Yamaha(config)#qos dscp-queue 56 7 (1) Yamaha(config)#qos dscp-queue 46 5 (2) Yamaha(config)#qos dscp-queue 8 1 (3) Yamaha(config)#qos dscp-queue 0 0 (4) 1 Store frames with DSCP = 56 in transmission queue #7 2 Store frames with DSCP = 46 in transmission queue #5 3 Store frames with DSCP = 8 in transmission queue #1 4 Store frames with DSCP = 0 in transmission queue #0 This sets the scheduling method per transmission queue. As this is the default, there is no need to make this setting, but it is listed for purposes of clarity. Yamaha(config)# no qos wrr-weight 7 (1) Yamaha(config)# no qos wrr-weight 5 (2) Yamaha(config)# no qos wrr-weight 1 (3) Yamaha(config)# no qos wrr-weight 0 (4) 1 Queue: 7 SP method 2 Queue: 5 SP method 3 Queue: 1 SP method 4 Queue: 0 SP method</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#アクセスリストを使用した優先制御spwrr">5.2. Priority control (SP+WRR) using an access list</div><div class="search_word">5.2. priority control (sp+wrr) using an access list this example classifies traffic by using the source ip address, and sets the priority control (wrr). priority control (sp+wrr) setting example classification conditions and priority setting for input frames the packet from 192.168.10.2 is classified as traffic a , and is set with a priority level of 7 during packet transmission the packet from 192.168.20.2 is classified as traffic b , and is set with a priority level of 6 during packet transmission the packet from 192.168.30.2 is classified as traffic c , and is set with a priority level of 5 during packet transmission the packet from 192.168.40.2 is classified as traffic d , and is set with a priority level of 4 during packet transmission the packet from 192.168.50.2 is classified as traffic e , and is set with a priority level of 3 during packet transmission the packet from 192.168.60.2 is classified as traffic f , and is set with a priority level of 2 during packet transmission the packet from 192.168.70.2 is classified as traffic g , and is set with a priority level of 1 during packet transmission the packet from 192.168.80.2 is classified as traffic h , and is set with a priority level of 0 during packet transmission scheduling method configure the settings in a combination of sp and wrr. queue id method weight (%) 7 sp - 6 sp - 5 sp - 4 wrr 8 (40.0%) 3 wrr 6 (30.0%) 2 wrr 3 (15.0%) 1 wrr 2 (10.0%) 0 wrr 1 (5.0%) this enables qos, defines the access lists for traffic a–h, and defines the traffic classes that will be set in the lan ports. yamaha(config)#qos enable (1) yamaha(config)#access-list 1 permit any 192.168.10.2 0.0.0.0 any (2) yamaha(config)#class-map cmap-ayamaha(config-cmap)#match access-list 1yamaha(config-cmap)#exityamaha(config)#access-list 2 permit any 192.168.20.2 0.0.0.0 any (3) yamaha(config)#class-map cmap-byamaha(config-cmap)#match access-list 2yamaha(config-cmap)#exityamaha(config)#access-list 3 permit any 192.168.30.2 0.0.0.0 any (4) yamaha(config)#class-map cmap-cyamaha(config-cmap)#match access-list 3yamaha(config-cmap)#exityamaha(config)#access-list 4 permit any 192.168.40.2 0.0.0.0 any (5) yamaha(config)#class-map cmap-dyamaha(config-cmap)#match access-list 4yamaha(config-cmap)#exityamaha(config)#access-list 5 permit any 192.168.50.2 0.0.0.0 any (6) yamaha(config)#class-map cmap-eyamaha(config-cmap)#match access-list 5yamaha(config-cmap)#exityamaha(config)#access-list 6 permit any 192.168.60.2 0.0.0.0 any (7) yamaha(config)#class-map cmap-fyamaha(config-cmap)#match access-list 6yamaha(config-cmap)#exityamaha(config)#access-list 7 permit any 192.168.70.2 0.0.0.0 any (8) yamaha(config)#class-map cmap-gyamaha(config-cmap)#match access-list 7yamaha(config-cmap)#exityamaha(config)#access-list 8 permit any 192.168.80.2 0.0.0.0 any (9) yamaha(config)#class-map cmap-hyamaha(config-cmap)#match access-list 8yamaha(config-cmap)#exit 1 enable qos 2 traffic a 3 traffic b 4 traffic c 5 traffic d 6 traffic e 7 traffic f 8 traffic g 9 traffic h this reverts the cos - transmission queue id conversion table to the default setting. yamaha(config)#no qos cos-queue 0yamaha(config)#no qos cos-queue 1yamaha(config)#no qos cos-queue 2yamaha(config)#no qos cos-queue 3yamaha(config)#no qos cos-queue 4yamaha(config)#no qos cos-queue 5yamaha(config)#no qos cos-queue 6yamaha(config)#no qos cos-queue 7 generate and apply the policy to lan port #1 (port1.1). this sets a transmission queue with cos value 7 to traffic-a, and a transmission queue with cos value 6 to traffic-b. yamaha(config)#policy-map pmap1yamaha(config-pmap)#class cmap-ayamaha(config-pmap-c)#set cos-queue 7 (1) yamaha(config-pmap-c)#exityamaha(config-pmap)#class cmap-byamaha(config-pmap-c)#set cos-queue 6 (2) yamaha(config-pmap-c)#exityamaha(config-pmap)#exityamaha(config)#interface port1.1 (3) yamaha(config-if)#service-policy input pmap1 (4) yamaha(config-if)# exit 1 traffic-a is given local priority 7 2 traffic-b is given local priority 6 3 lan port #1 4 apply the policy to received frames generate and apply the policy to lan port #2 (port1.2). this sets a transmission queue with cos value 5 to traffic-c, and a transmission queue with cos value 4 to traffic-d. yamaha(config)#policy-map pmap2yamaha(config-pmap)#class cmap-cyamaha(config-pmap-c)#set cos-queue 5 (1) yamaha(config-pmap-c)#exityamaha(config-pmap)#class cmap-dyamaha(config-pmap-c)#set cos-queue 4 (2) yamaha(config-pmap-c)#exityamaha(config-pmap)#exityamaha(config)#interface port1.2 (3) yamaha(config-if)#service-policy input pmap2 (4) yamaha(config-if)# exit 1 traffic-c is given local priority 5 2 traffic-d is given local priority 4 3 lan port #2 4 apply the policy to received frames generate and apply the policy to lan port #3 (port1.3). this sets a transmission queue with cos value 3 to traffic-e, and a transmission queue with cos value 0 to traffic-f. yamaha(config)#policy-map pmap3yamaha(config-pmap)#class cmap-eyamaha(config-pmap-c)#set cos-queue 3 (1) yamaha(config-pmap-c)#exityamaha(config-pmap)#class cmap-fyamaha(config-pmap-c)#set cos-queue 0 (2) yamaha(config-pmap-c)#exityamaha(config-pmap)#exityamaha(config)#interface port1.3 (3) yamaha(config-if)#service-policy input pmap3 (4) yamaha(config-if)# exit 1 traffic-e is given local priority 3 2 traffic-f is given local priority 2 3 lan port #3 4 apply the policy to received frames generate and apply the policy to lan port #4 (port1.4). this sets a transmission queue with cos value 2 to traffic-g, and a transmission queue with cos value 1 to traffic-h. yamaha(config)#policy-map pmap4yamaha(config-pmap)#class cmap-gyamaha(config-pmap-c)#set cos-queue 2 (1) yamaha(config-pmap-c)#exityamaha(config-pmap)#class cmap-hyamaha(config-pmap-c)#set cos-queue 1 (2) yamaha(config-pmap-c)#exityamaha(config-pmap)#exityamaha(config)#interface port1.4 (3) yamaha(config-if)#service-policy input pmap4 (4) yamaha(config-if)#exit 1 traffic-g is given local priority 1 2 traffic-h is given local priority 0 3 lan port #4 4 apply the policy to received frames this sets the scheduling method for the transmission queue. as the queue ids 5, 6, and 7 are the defaults, there is no need to make this setting, but it is listed for purposes of clarity. yamaha(config)#qos wrr-weight 0 1 (1) yamaha(config)#qos wrr-weight 1 2 (2) yamaha(config)#qos wrr-weight 2 3 (3) yamaha(config)#qos wrr-weight 3 6 (4) yamaha(config)#qos wrr-weight 4 8 (5) yamaha(config)#no qos wrr-weight 5 (6) yamaha(config)#no qos wrr-weight 6 (7) yamaha(config)#no qos wrr-weight 7 (8) 1 transmission queue 0: wrr method, weight of 1 2 transmission queue 1: wrr method, weight of 2 3 transmission queue 2: wrr method, weight of 3 4 transmission queue 3: wrr method, weight of 6 5 transmission queue 4: wrr method, weight of 8 6 transmission queue 5: sp method 7 transmission queue 6: sp method 8 transmission queue 7: sp method</div><div class="display_word">5.2. Priority control (SP+WRR) using an access list This example classifies traffic by using the source IP address, and sets the priority control (WRR). Priority control (SP+WRR) setting example Classification conditions and priority setting for input frames The packet from 192.168.10.2 is classified as traffic A , and is set with a priority level of 7 during packet transmission The packet from 192.168.20.2 is classified as traffic B , and is set with a priority level of 6 during packet transmission The packet from 192.168.30.2 is classified as traffic C , and is set with a priority level of 5 during packet transmission The packet from 192.168.40.2 is classified as traffic D , and is set with a priority level of 4 during packet transmission The packet from 192.168.50.2 is classified as traffic E , and is set with a priority level of 3 during packet transmission The packet from 192.168.60.2 is classified as traffic F , and is set with a priority level of 2 during packet transmission The packet from 192.168.70.2 is classified as traffic G , and is set with a priority level of 1 during packet transmission The packet from 192.168.80.2 is classified as traffic H , and is set with a priority level of 0 during packet transmission Scheduling method Configure the settings in a combination of SP and WRR. Queue ID Method Weight (%) 7 SP - 6 SP - 5 SP - 4 WRR 8 (40.0%) 3 WRR 6 (30.0%) 2 WRR 3 (15.0%) 1 WRR 2 (10.0%) 0 WRR 1 (5.0%) This enables QoS, defines the access lists for traffic A–H, and defines the traffic classes that will be set in the LAN ports. Yamaha(config)#qos enable (1) Yamaha(config)#access-list 1 permit any 192.168.10.2 0.0.0.0 any (2) Yamaha(config)#class-map cmap-AYamaha(config-cmap)#match access-list 1Yamaha(config-cmap)#exitYamaha(config)#access-list 2 permit any 192.168.20.2 0.0.0.0 any (3) Yamaha(config)#class-map cmap-BYamaha(config-cmap)#match access-list 2Yamaha(config-cmap)#exitYamaha(config)#access-list 3 permit any 192.168.30.2 0.0.0.0 any (4) Yamaha(config)#class-map cmap-CYamaha(config-cmap)#match access-list 3Yamaha(config-cmap)#exitYamaha(config)#access-list 4 permit any 192.168.40.2 0.0.0.0 any (5) Yamaha(config)#class-map cmap-DYamaha(config-cmap)#match access-list 4Yamaha(config-cmap)#exitYamaha(config)#access-list 5 permit any 192.168.50.2 0.0.0.0 any (6) Yamaha(config)#class-map cmap-EYamaha(config-cmap)#match access-list 5Yamaha(config-cmap)#exitYamaha(config)#access-list 6 permit any 192.168.60.2 0.0.0.0 any (7) Yamaha(config)#class-map cmap-FYamaha(config-cmap)#match access-list 6Yamaha(config-cmap)#exitYamaha(config)#access-list 7 permit any 192.168.70.2 0.0.0.0 any (8) Yamaha(config)#class-map cmap-GYamaha(config-cmap)#match access-list 7Yamaha(config-cmap)#exitYamaha(config)#access-list 8 permit any 192.168.80.2 0.0.0.0 any (9) Yamaha(config)#class-map cmap-HYamaha(config-cmap)#match access-list 8Yamaha(config-cmap)#exit 1 Enable QoS 2 Traffic A 3 Traffic B 4 Traffic C 5 Traffic D 6 Traffic E 7 Traffic F 8 Traffic G 9 Traffic H This reverts the CoS - transmission queue ID conversion table to the default setting. Yamaha(config)#no qos cos-queue 0Yamaha(config)#no qos cos-queue 1Yamaha(config)#no qos cos-queue 2Yamaha(config)#no qos cos-queue 3Yamaha(config)#no qos cos-queue 4Yamaha(config)#no qos cos-queue 5Yamaha(config)#no qos cos-queue 6Yamaha(config)#no qos cos-queue 7 Generate and apply the policy to LAN port #1 (port1.1). This sets a transmission queue with CoS value 7 to traffic-A, and a transmission queue with CoS value 6 to traffic-B. Yamaha(config)#policy-map pmap1Yamaha(config-pmap)#class cmap-AYamaha(config-pmap-c)#set cos-queue 7 (1) Yamaha(config-pmap-c)#exitYamaha(config-pmap)#class cmap-BYamaha(config-pmap-c)#set cos-queue 6 (2) Yamaha(config-pmap-c)#exitYamaha(config-pmap)#exitYamaha(config)#interface port1.1 (3) Yamaha(config-if)#service-policy input pmap1 (4) Yamaha(config-if)# exit 1 Traffic-A is given local priority 7 2 Traffic-B is given local priority 6 3 LAN port #1 4 Apply the policy to received frames Generate and apply the policy to LAN port #2 (port1.2). This sets a transmission queue with CoS value 5 to traffic-C, and a transmission queue with CoS value 4 to traffic-D. Yamaha(config)#policy-map pmap2Yamaha(config-pmap)#class cmap-CYamaha(config-pmap-c)#set cos-queue 5 (1) Yamaha(config-pmap-c)#exitYamaha(config-pmap)#class cmap-DYamaha(config-pmap-c)#set cos-queue 4 (2) Yamaha(config-pmap-c)#exitYamaha(config-pmap)#exitYamaha(config)#interface port1.2 (3) Yamaha(config-if)#service-policy input pmap2 (4) Yamaha(config-if)# exit 1 Traffic-C is given local priority 5 2 Traffic-D is given local priority 4 3 LAN port #2 4 Apply the policy to received frames Generate and apply the policy to LAN port #3 (port1.3). This sets a transmission queue with CoS value 3 to traffic-E, and a transmission queue with CoS value 0 to traffic-F. Yamaha(config)#policy-map pmap3Yamaha(config-pmap)#class cmap-EYamaha(config-pmap-c)#set cos-queue 3 (1) Yamaha(config-pmap-c)#exitYamaha(config-pmap)#class cmap-FYamaha(config-pmap-c)#set cos-queue 0 (2) Yamaha(config-pmap-c)#exitYamaha(config-pmap)#exitYamaha(config)#interface port1.3 (3) Yamaha(config-if)#service-policy input pmap3 (4) Yamaha(config-if)# exit 1 Traffic-E is given local priority 3 2 Traffic-F is given local priority 2 3 LAN port #3 4 Apply the policy to received frames Generate and apply the policy to LAN port #4 (port1.4). This sets a transmission queue with CoS value 2 to traffic-G, and a transmission queue with CoS value 1 to traffic-H. Yamaha(config)#policy-map pmap4Yamaha(config-pmap)#class cmap-GYamaha(config-pmap-c)#set cos-queue 2 (1) Yamaha(config-pmap-c)#exitYamaha(config-pmap)#class cmap-HYamaha(config-pmap-c)#set cos-queue 1 (2) Yamaha(config-pmap-c)#exitYamaha(config-pmap)#exitYamaha(config)#interface port1.4 (3) Yamaha(config-if)#service-policy input pmap4 (4) Yamaha(config-if)#exit 1 Traffic-G is given local priority 1 2 Traffic-H is given local priority 0 3 LAN port #4 4 Apply the policy to received frames This sets the scheduling method for the transmission queue. As the queue IDs 5, 6, and 7 are the defaults, there is no need to make this setting, but it is listed for purposes of clarity. Yamaha(config)#qos wrr-weight 0 1 (1) Yamaha(config)#qos wrr-weight 1 2 (2) Yamaha(config)#qos wrr-weight 2 3 (3) Yamaha(config)#qos wrr-weight 3 6 (4) Yamaha(config)#qos wrr-weight 4 8 (5) Yamaha(config)#no qos wrr-weight 5 (6) Yamaha(config)#no qos wrr-weight 6 (7) Yamaha(config)#no qos wrr-weight 7 (8) 1 Transmission queue 0: WRR method, weight of 1 2 Transmission queue 1: WRR method, weight of 2 3 Transmission queue 2: WRR method, weight of 3 4 Transmission queue 3: WRR method, weight of 6 5 Transmission queue 4: WRR method, weight of 8 6 Transmission queue 5: SP method 7 Transmission queue 6: SP method 8 Transmission queue 7: SP method</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#ポート優先トラストモードを使用した優先制御">5.3. Priority control using port priority trust mode</div><div class="search_word">5.3. priority control using port priority trust mode the transmission queue is determined according to the port priority order that is specified for each reception port. priority control using port priority: setting example set priority for each reception port set lan port #1 (port1.1) to priority order 6 . set lan port #2 (port1.2) to priority order 4 . set lan port #3 (port1.3) to priority order 2 . enable qos and set the trust mode for the reception ports (lan ports #1, #2, and #3). yamaha(config)#qos enable (1) yamaha(config)#interface port1.1 (2) yamaha(config-if)#qos trust port-priority (3) yamaha(config-if)#qos port-priority-queue 6 (4) yamaha(config-if)#exityamaha(config)#interface port1.2 (5) yamaha(config-if)#qos trust port-priority (9) yamaha(config-if)#qos port-priority-queue 4 (7) yamaha(config-if)#exityamaha(config)#interface port1.3 (8) yamaha(config-if)#qos trust port-priority (9) yamaha(config-if)#qos port-priority-queue 2 (10) yamaha(config-if)#exit 1 enable qos 2 setting for lan port #1 3 change the trust mode to “port priority” 4 set the port priority to 6 5 setting for lan port #2 6 change the trust mode to “port priority” 7 set the port priority to 4 8 setting for lan port #3 9 change the trust mode to “port priority” 10 set the port priority to 2</div><div class="display_word">5.3. Priority control using port priority trust mode The transmission queue is determined according to the port priority order that is specified for each reception port. Priority control using port priority: setting example Set priority for each reception port Set LAN port #1 (port1.1) to priority order 6 . Set LAN port #2 (port1.2) to priority order 4 . Set LAN port #3 (port1.3) to priority order 2 . Enable QoS and set the trust mode for the reception ports (LAN ports #1, #2, and #3). Yamaha(config)#qos enable (1) Yamaha(config)#interface port1.1 (2) Yamaha(config-if)#qos trust port-priority (3) Yamaha(config-if)#qos port-priority-queue 6 (4) Yamaha(config-if)#exitYamaha(config)#interface port1.2 (5) Yamaha(config-if)#qos trust port-priority (9) Yamaha(config-if)#qos port-priority-queue 4 (7) Yamaha(config-if)#exitYamaha(config)#interface port1.3 (8) Yamaha(config-if)#qos trust port-priority (9) Yamaha(config-if)#qos port-priority-queue 2 (10) Yamaha(config-if)#exit 1 Enable QoS 2 Setting for LAN port #1 3 Change the trust mode to “port priority” 4 Set the port priority to 6 5 Setting for LAN port #2 6 Change the trust mode to “port priority” 7 Set the port priority to 4 8 Setting for LAN port #3 9 Change the trust mode to “port priority” 10 Set the port priority to 2</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#アクセスリストを使用した帯域制御ツインレート個別ポリサー">5.4. Bandwidth control using access list (twin rate / individual policer)</div><div class="search_word">5.4. bandwidth control using access list (twin rate / individual policer) this example sets bandwidth control by using the source ip address. a twin rate policer and an individual policer are used for metering. bandwidth control setting example classification conditions and bandwidth limits for input frames packets from 192.168.10.2 are classified as traffic a packets, with a committed information rate (cir) (guaranteed reception rate) of 25 mbps. packets from 192.168.20.2 are classified as traffic b packets, with a committed information rate (cir) (guaranteed reception rate) of 15 mbps. packets from 192.168.30.2 are classified as traffic c packets, with a committed information rate (cir) (guaranteed reception rate) of 10 mbps. enable qos, define the access lists for traffic a–c, and define the traffic classes that will be set for the lan ports. yamaha(config)#qos enable (1) yamaha(config)#access-list 1 permit any 192.168.10.2 0.0.0.0 any (2) yamaha(config)#class-map cmap-ayamaha(config-cmap)#match access-list 1yamaha(config-cmap)#exityamaha(config)#access-list 2 permit any 192.168.20.2 0.0.0.0 any (3) yamaha(config)#class-map cmap-byamaha(config-cmap)#match access-list 2yamaha(config-cmap)#exityamaha(config)#access-list 3 permit any 192.168.30.2 0.0.0.0 any (4) yamaha(config)#class-map cmap-cyamaha(config-cmap)#match access-list 3yamaha(config-cmap)#exit 1 enable qos 2 traffic a 3 traffic b 4 traffic c generate and apply the policy to lan port #1 (port1.1). individually specify metering for traffic a through traffic c. in the twin rate policer, bandwidth for green can be allocated (guaranteed) by discarding yellow and red. yamaha(config)#policy-map pmap1yamaha(config-pmap)#class cmap-a (1) yamaha(config-pmap-c)#police twin-rate 25000 25000 156 50 yellow-action drop red-action dropyamaha(config-pmap-c)#exityamaha(config-pmap)#class cmap-b (2) yamaha(config-pmap-c)#police twin-rate 15000 15000 93 50 yellow-action drop red-action dropyamaha(config-pmap-c)#exityamaha(config-pmap)#class cmap-c (3) yamaha(config-pmap-c)#police twin-rate 10000 10000 62 50 yellow-action drop red-action dropyamaha(config-pmap-c)#exityamaha(config-pmap)#exityamaha(config)#interface port1.1 (4) yamaha(config-if)#service-policy input pmap1 (5) yamaha(config-if)#exit 1 traffic-a metering setting 2 traffic-b metering setting 3 traffic-c metering setting 4 lan port 1 5 apply the policy to received frames the metering setting values are shown below. metering type: twin rate policer traffic-a: cir, pir (25,000 kbps), cbs (156 kbyte), pbs (50 kbyte) traffic-b: cir, pir (15,000 kbps), cbs (93 kbyte), pbs (50 kbyte) traffic-c: cir, pir (10,000 kbps), cbs (62 kbyte), pbs (50 kbyte) the following calculation is used to find the cbs, with a round-trip time of 0.05 sec. cbs = cir (bps) ÷ 8 (bit) × 0.05 (second)</div><div class="display_word">5.4. Bandwidth control using access list (twin rate / individual policer) This example sets bandwidth control by using the source IP address. A twin rate policer and an individual policer are used for metering. Bandwidth control setting example Classification conditions and bandwidth limits for input frames Packets from 192.168.10.2 are classified as traffic A packets, with a committed information rate (CIR) (guaranteed reception rate) of 25 Mbps. Packets from 192.168.20.2 are classified as traffic B packets, with a committed information rate (CIR) (guaranteed reception rate) of 15 Mbps. Packets from 192.168.30.2 are classified as traffic C packets, with a committed information rate (CIR) (guaranteed reception rate) of 10 Mbps. Enable QoS, define the access lists for traffic A–C, and define the traffic classes that will be set for the LAN ports. Yamaha(config)#qos enable (1) Yamaha(config)#access-list 1 permit any 192.168.10.2 0.0.0.0 any (2) Yamaha(config)#class-map cmap-AYamaha(config-cmap)#match access-list 1Yamaha(config-cmap)#exitYamaha(config)#access-list 2 permit any 192.168.20.2 0.0.0.0 any (3) Yamaha(config)#class-map cmap-BYamaha(config-cmap)#match access-list 2Yamaha(config-cmap)#exitYamaha(config)#access-list 3 permit any 192.168.30.2 0.0.0.0 any (4) Yamaha(config)#class-map cmap-CYamaha(config-cmap)#match access-list 3Yamaha(config-cmap)#exit 1 Enable QoS 2 Traffic A 3 Traffic B 4 Traffic C Generate and apply the policy to LAN port #1 (port1.1). Individually specify metering for traffic A through traffic C. In the twin rate policer, bandwidth for green can be allocated (guaranteed) by discarding yellow and red. Yamaha(config)#policy-map pmap1Yamaha(config-pmap)#class cmap-A (1) Yamaha(config-pmap-c)#police twin-rate 25000 25000 156 50 yellow-action drop red-action dropYamaha(config-pmap-c)#exitYamaha(config-pmap)#class cmap-B (2) Yamaha(config-pmap-c)#police twin-rate 15000 15000 93 50 yellow-action drop red-action dropYamaha(config-pmap-c)#exitYamaha(config-pmap)#class cmap-C (3) Yamaha(config-pmap-c)#police twin-rate 10000 10000 62 50 yellow-action drop red-action dropYamaha(config-pmap-c)#exitYamaha(config-pmap)#exitYamaha(config)#interface port1.1 (4) Yamaha(config-if)#service-policy input pmap1 (5) Yamaha(config-if)#exit 1 Traffic-A metering setting 2 Traffic-B metering setting 3 Traffic-C metering setting 4 LAN port 1 5 Apply the policy to received frames The metering setting values are shown below. Metering type: Twin rate policer Traffic-A: CIR, PIR (25,000 kbps), CBS (156 kbyte), PBS (50 kbyte) Traffic-B: CIR, PIR (15,000 kbps), CBS (93 kbyte), PBS (50 kbyte) Traffic-C: CIR, PIR (10,000 kbps), CBS (62 kbyte), PBS (50 kbyte) The following calculation is used to find the CBS, with a round-trip time of 0.05 sec. CBS = CIR (bps) ÷ 8 (bit) × 0.05 (second)</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#アクセスリストを使用した帯域制御シングルレート集約ポリサー">5.5. Bandwidth control using access list (single rate / aggregate policer)</div><div class="search_word">5.5. bandwidth control using access list (single rate / aggregate policer) this example sets bandwidth control by using the source ip address. a single rate policer and an aggregate policer are used for metering. bandwidth control setting example classification conditions and bandwidth limits for input frames packets from 192.168.10.2 are classified as traffic a . packets from 192.168.20.2 are classified as traffic b . packets from 192.168.30.2 are classified as traffic c . the reception rate is restricted to 25 mbps for traffic a, b, and c collectively. bandwidth class “yellow” is remarked as dscp = 0, and sent with low priority. enable qos, define the access lists for traffic a–c, and define the traffic classes that will be set for the lan ports. yamaha(config)#qos enable (1) yamaha(config)#access-list 1 permit any 192.168.10.2 0.0.0.0 any (2) yamaha(config)#class-map cmap-ayamaha(config-cmap)#match access-list 1yamaha(config-cmap)#exityamaha(config)#access-list 2 permit any 192.168.20.2 0.0.0.0 any (3) yamaha(config)#class-map cmap-byamaha(config-cmap)#match access-list 2yamaha(config-cmap)#exityamaha(config)#access-list 3 permit any 192.168.30.2 0.0.0.0 any (4) yamaha(config)#class-map cmap-cyamaha(config-cmap)#match access-list 3yamaha(config-cmap)#exit 1 enable qos 2 traffic a 3 traffic b 4 traffic c set the dscp–transmission queue id conversion table. assign the lowest-priority transmission queue to the dscp value (0) used for remarking “yellow.” yamaha(config)#qos dscp-queue 0 0 create an aggregate policer. yamaha(config)#aggregate-police agp1 (1) yamaha(config-agg-policer)#police single-rate 25000 156 50 yellow-action remark red-action dropyamaha(config-agg-policer)#remark-map yellow ip-dscp 0yamaha(config-agg-policer)#exit 1 create an aggregate policer the aggregate policer’s metering setting values are as follows. metering type: single rate policer remark “yellow” to dscp value = 0 cir (25,000 kbps), cbs (156 kbyte), ebs (50 kbyte) the following calculation is used to find the cbs, with a round-trip time of 0.05 sec. cbs = cir (bps) ÷ 8 (bit) × 0.05 (second) generate and apply the policy to lan port #1 (port1.1). specify metering (aggregate policer) for the aggregated traffic of a through c. yamaha(config)#policy-map pmap1yamaha(config-pmap)#class cmap-a (1) yamaha(config-pmap-c)#police-aggregate agp1yamaha(config-pmap-c)#exityamaha(config-pmap)#class cmap-b (2) yamaha(config-pmap-c)#police-aggregate agp1yamaha(config-pmap-c)#exityamaha(config-pmap)#class cmap-c (3) yamaha(config-pmap-c)#police-aggregate agp1yamaha(config-pmap-c)#exityamaha(config-pmap)#exityamaha(config)#interface port1.1 (4) yamaha(config-if)#service-policy input pmap1 (5) yamaha(config-if)#exit 1 traffic-a metering setting 2 traffic-b metering setting 3 traffic-c metering setting 4 lan port 1 5 apply the policy to received frames</div><div class="display_word">5.5. Bandwidth control using access list (single rate / aggregate policer) This example sets bandwidth control by using the source IP address. A single rate policer and an aggregate policer are used for metering. Bandwidth control setting example Classification conditions and bandwidth limits for input frames Packets from 192.168.10.2 are classified as traffic A . Packets from 192.168.20.2 are classified as traffic B . Packets from 192.168.30.2 are classified as traffic C . The reception rate is restricted to 25 Mbps for traffic A, B, and C collectively. Bandwidth class “yellow” is remarked as DSCP = 0, and sent with low priority. Enable QoS, define the access lists for traffic A–C, and define the traffic classes that will be set for the LAN ports. Yamaha(config)#qos enable (1) Yamaha(config)#access-list 1 permit any 192.168.10.2 0.0.0.0 any (2) Yamaha(config)#class-map cmap-AYamaha(config-cmap)#match access-list 1Yamaha(config-cmap)#exitYamaha(config)#access-list 2 permit any 192.168.20.2 0.0.0.0 any (3) Yamaha(config)#class-map cmap-BYamaha(config-cmap)#match access-list 2Yamaha(config-cmap)#exitYamaha(config)#access-list 3 permit any 192.168.30.2 0.0.0.0 any (4) Yamaha(config)#class-map cmap-CYamaha(config-cmap)#match access-list 3Yamaha(config-cmap)#exit 1 Enable QoS 2 Traffic A 3 Traffic B 4 Traffic C Set the DSCP–transmission queue ID conversion table. Assign the lowest-priority transmission queue to the DSCP value (0) used for remarking “yellow.” Yamaha(config)#qos dscp-queue 0 0 Create an aggregate policer. Yamaha(config)#aggregate-police agp1 (1) Yamaha(config-agg-policer)#police single-rate 25000 156 50 yellow-action remark red-action dropYamaha(config-agg-policer)#remark-map yellow ip-dscp 0Yamaha(config-agg-policer)#exit 1 Create an aggregate policer The aggregate policer’s metering setting values are as follows. Metering type: Single rate policer Remark “yellow” to DSCP value = 0 CIR (25,000 kbps), CBS (156 kbyte), EBS (50 kbyte) The following calculation is used to find the CBS, with a round-trip time of 0.05 sec. CBS = CIR (bps) ÷ 8 (bit) × 0.05 (second) Generate and apply the policy to LAN port #1 (port1.1). Specify metering (aggregate policer) for the aggregated traffic of A through C. Yamaha(config)#policy-map pmap1Yamaha(config-pmap)#class cmap-A (1) Yamaha(config-pmap-c)#police-aggregate agp1Yamaha(config-pmap-c)#exitYamaha(config-pmap)#class cmap-B (2) Yamaha(config-pmap-c)#police-aggregate agp1Yamaha(config-pmap-c)#exitYamaha(config-pmap)#class cmap-C (3) Yamaha(config-pmap-c)#police-aggregate agp1Yamaha(config-pmap-c)#exitYamaha(config-pmap)#exitYamaha(config)#interface port1.1 (4) Yamaha(config-if)#service-policy input pmap1 (5) Yamaha(config-if)#exit 1 Traffic-A metering setting 2 Traffic-B metering setting 3 Traffic-C metering setting 4 LAN port 1 5 Apply the policy to received frames</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution lan/sfp ports that use settings different from those shown below cannot be aggregated as a logical interface. also, as for the settings shown below for a lan/sfp port that belongs to a logical interface in startup config, the settings for the most recent port number will be applied to the logical interface. trust mode default cos port priority lan/sfp ports on which policy maps have been applied cannot belong to a logical interface. policy maps cannot be applied to a lan/sfp port that belongs to a logical interface. however, if a policy map exists for a lan/sfp port associated to a logical interface in startup config, the settings for the most recent port number will be applied to the logical interface. conditions might not be determined correctly for fragment packets. specifically, if layer 4 information (source port number, destination port number, and various tcp flags) is included in the conditions, correct information cannot be determined because the information is not included in the second and subsequent fragment packets. if there is a possibility of processing fragment packets, do not include layer 4 information in the conditions.</div><div class="display_word">6. Points of Caution LAN/SFP ports that use settings different from those shown below cannot be aggregated as a logical interface. Also, as for the settings shown below for a LAN/SFP port that belongs to a logical interface in startup config, the settings for the most recent port number will be applied to the logical interface. Trust mode Default CoS Port priority LAN/SFP ports on which policy maps have been applied cannot belong to a logical interface. Policy maps cannot be applied to a LAN/SFP port that belongs to a logical interface. However, if a policy map exists for a LAN/SFP port associated to a logical interface in startup config, the settings for the most recent port number will be applied to the logical interface. Conditions might not be determined correctly for fragment packets. Specifically, if layer 4 information (source port number, destination port number, and various TCP flags) is included in the conditions, correct information cannot be determined because the information is not included in the second and subsequent fragment packets. If there is a possibility of processing fragment packets, do not include layer 4 information in the conditions.</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation none</div><div class="display_word">7. Related Documentation None</div></div><div id="traffic_traffic_qos"><div class="search_title" docfname="traffic_traffic_qos" doctitle="QoS" link="#商標名称について">8. Trademarks and Trade Names</div><div class="search_word">8. trademarks and trade names zoom is a trademark or registered trademark of zoom video communications, inc. in the united states and other countries. microsoft teams is a trademark or registered trademark of microsoft corporation in the united states and other countries.</div><div class="display_word">8. Trademarks and Trade Names Zoom is a trademark or registered trademark of Zoom Video Communications, Inc. in the United States and other countries. Microsoft Teams is a trademark or registered trademark of Microsoft Corporation in the United States and other countries.</div></div><div id="traffic_traffic_storm"><div class="search_title" docfname="traffic_traffic_storm" doctitle="Storm" link="#ストーム制御">Storm Control</div><div class="search_word">storm control</div><div class="display_word">Storm Control</div></div><div id="traffic_traffic_storm"><div class="search_title" docfname="traffic_traffic_storm" doctitle="Storm" link="#機能概要">1. Function Overview</div><div class="search_word">1. function overview this product provides a storm control function as a countermeasure against l2 loops and dos attacks. broadcast frames, multicast frames, and unicast frames addressed to an unknown destination (dlf) are monitored for each lan/sfp port, and frames that exceed a preset threshold value are discarded. this prevents such frames from taking up bandwidth on the lan/sfp port. using this along with the unique loop detection and storm control functions enhances the precision of loop detection (avoiding such frames in the first place) .</div><div class="display_word">1. Function Overview This product provides a storm control function as a countermeasure against L2 loops and DoS attacks. Broadcast frames, multicast frames, and unicast frames addressed to an unknown destination (dlf) are monitored for each LAN/SFP port, and frames that exceed a preset threshold value are discarded. This prevents such frames from taking up bandwidth on the LAN/SFP port. Using this along with the unique loop detection and storm control functions enhances the precision of loop detection (avoiding such frames in the first place) .</div></div><div id="traffic_traffic_storm"><div class="search_title" docfname="traffic_traffic_storm" doctitle="Storm" link="#用語の定義">2. Definition of Terms Used</div><div class="search_word">2. definition of terms used broadcast storm/multicast storm this means a situation where frames addressed for broadcast or multicast are continuously forwarded. in this situation, the switch floods all ports except for the reception port with the broadcast or multicast. when this is received by another switch, all ports except for the reception port are flooded in the same way. when this continues, it can lead to the following symptoms. bandwidth is taken up by the broadcast frames/multicast frames the switch’s cpu load increases, making normal operations difficult devices connected to the switch become unable to communicate unicast storm this means a situation where frames addressed to an unknown unicast destination (dlf: destination lookup failure) are continuously forwarded. when the mac address of the receiving device has not been registered in the arp table, all ports on the switch except for the reception port are flooded. this leads to the same symptoms occurring as with a broadcast storm or multicast storm.</div><div class="display_word">2. Definition of Terms Used Broadcast Storm/Multicast Storm This means a situation where frames addressed for broadcast or multicast are continuously forwarded. In this situation, the switch floods all ports except for the reception port with the broadcast or multicast. When this is received by another switch, all ports except for the reception port are flooded in the same way. When this continues, it can lead to the following symptoms. Bandwidth is taken up by the broadcast frames/multicast frames The switch’s CPU load increases, making normal operations difficult Devices connected to the switch become unable to communicate Unicast Storm This means a situation where frames addressed to an unknown unicast destination (dlf: Destination Lookup Failure) are continuously forwarded. When the MAC address of the receiving device has not been registered in the ARP table, all ports on the switch except for the reception port are flooded. This leads to the same symptoms occurring as with a broadcast storm or multicast storm.</div></div><div id="traffic_traffic_storm"><div class="search_title" docfname="traffic_traffic_storm" doctitle="Storm" link="#機能詳細">3. Function Details</div><div class="search_word">3. function details the operating specifications for storm control are shown below. the storm control function can be enabled for lan/sfp ports. the setting is disabled for all ports by default. storm control on this product can be specified as a tolerance percentage for the bandwidth of the lan/sfp ports that receive broadcast frames, multicast frames, and unicast frames addressed to an unknown destination. (control can be made in two decimal points. specifying 100% is the same as disabling the storm function.) the bandwidth tolerance is common for all frames, and the user can select the applicable frames. this setting is made using the storm-control command. the following syslog will be outputted at the time that storm control is enabled or disabled . enabled: [ storm]:inf: storm-control enable (port:port1.1, type:b m u, level:50. 0%) disabled: [ storm]:inf: storm-control disable (port:port1.1) when frames exceeding the permitted bandwidth are received, the excessive frames are discarded. use the show storm-control command to check the storm control information set for the lan/sfp port.</div><div class="display_word">3. Function Details The operating specifications for storm control are shown below. The storm control function can be enabled for LAN/SFP ports. The setting is disabled for all ports by default. Storm control on this product can be specified as a tolerance percentage for the bandwidth of the LAN/SFP ports that receive broadcast frames, multicast frames, and unicast frames addressed to an unknown destination. (Control can be made in two decimal points. Specifying 100% is the same as disabling the storm function.) The bandwidth tolerance is common for all frames, and the user can select the applicable frames. This setting is made using the storm-control command. The following SYSLOG will be outputted at the time that storm control is enabled or disabled . Enabled: [ STORM]:inf: storm-control ENABLE (port:port1.1, type:B M U, level:50. 0%) Disabled: [ STORM]:inf: storm-control DISABLE (port:port1.1) When frames exceeding the permitted bandwidth are received, the excessive frames are discarded. Use the show storm-control command to check the storm control information set for the LAN/SFP port.</div></div><div id="traffic_traffic_storm"><div class="search_title" docfname="traffic_traffic_storm" doctitle="Storm" link="#関連コマンド">4. Related Commands</div><div class="search_word">4. related commands related commands are indicated below. for details on the commands, refer to the command reference. operations operating commands set storm control storm-control show storm control reception upper limit show storm-control</div><div class="display_word">4. Related Commands Related commands are indicated below. For details on the commands, refer to the Command Reference. Operations Operating commands Set storm control storm-control Show storm control reception upper limit show storm-control</div></div><div id="traffic_traffic_storm"><div class="search_title" docfname="traffic_traffic_storm" doctitle="Storm" link="#コマンド実行例">5. Examples of Command Execution</div><div class="search_word">5. examples of command execution in this example, the receivable l2 broadcast packets for lan port 1 are restricted to a port bandwidth of 30%. storm control command setting: example yamaha(config)#interface port1.1yamaha(config-if)#storm-control broadcast level 30 (1) yamaha(config-if)#endyamaha#yamaha#show storm-controlport        bcastlevel    mcastlevel    ucastlevelport1.1       30.00%       100.00%       100.00%port1.2      100.00%       100.00%       100.00%port1.3      100.00%       100.00%       100.00%port1.4      100.00%       100.00%       100.00%port1.5      100.00%       100.00%       100.00%port1.6      100.00%       100.00%       100.00%port1.7      100.00%       100.00%       100.00%port1.8      100.00%       100.00%       100.00%port1.9      100.00%       100.00%       100.00% 1 limit broadcast to 30% of bandwidth</div><div class="display_word">5. Examples of Command Execution In this example, the receivable L2 broadcast packets for LAN port 1 are restricted to a port bandwidth of 30%. Storm control command setting: example Yamaha(config)#interface port1.1Yamaha(config-if)#storm-control broadcast level 30 (1) Yamaha(config-if)#endYamaha#Yamaha#show storm-controlPort        BcastLevel    McastLevel    UcastLevelport1.1       30.00%       100.00%       100.00%port1.2      100.00%       100.00%       100.00%port1.3      100.00%       100.00%       100.00%port1.4      100.00%       100.00%       100.00%port1.5      100.00%       100.00%       100.00%port1.6      100.00%       100.00%       100.00%port1.7      100.00%       100.00%       100.00%port1.8      100.00%       100.00%       100.00%port1.9      100.00%       100.00%       100.00% 1 Limit broadcast to 30% of bandwidth</div></div><div id="traffic_traffic_storm"><div class="search_title" docfname="traffic_traffic_storm" doctitle="Storm" link="#注意事項">6. Points of Caution</div><div class="search_word">6. points of caution none</div><div class="display_word">6. Points of Caution None</div></div><div id="traffic_traffic_storm"><div class="search_title" docfname="traffic_traffic_storm" doctitle="Storm" link="#関連文書">7. Related Documentation</div><div class="search_word">7. related documentation layer 2 function: unique loop detection</div><div class="display_word">7. Related Documentation Layer 2 Function: Unique Loop Detection</div></div><div id="gui_en_detail_basic"><div class="search_title" docfname="gui_en_detail_basic" doctitle="Basic" link="#title-box">Basic settings</div><div class="search_word">basic settings</div><div class="display_word">Basic settings</div></div><div id="gui_en_detail_basic"><div class="search_title" docfname="gui_en_detail_basic" doctitle="Basic" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring the basic settings.</div><div class="display_word">1. Summary This page is for configuring the basic settings.</div></div><div id="gui_en_detail_basic"><div class="search_title" docfname="gui_en_detail_basic" doctitle="Basic" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the basic settings.</div><div class="display_word">2. Top page This is the top page for the basic settings.</div></div><div id="gui_en_detail_basic"><div class="search_title" docfname="gui_en_detail_basic" doctitle="Basic" link="#ipv4_settings">2.1. IPv4 settings</div><div class="search_word">2.1. ipv4 settings shows the ipv4 settings. the table items are explained below. ipv4 address displays the ipv4 address setting. ipv4 default gateway displays the ipv4 default gateway setting. press the “setting” button to show the page for ipv4 settings.</div><div class="display_word">2.1. IPv4 settings Shows the IPv4 settings. The table items are explained below. IPv4 address Displays the IPv4 address setting. IPv4 default gateway Displays the IPv4 default gateway setting. Press the “Setting” button to show the page for IPv4 settings.</div></div><div id="gui_en_detail_basic"><div class="search_title" docfname="gui_en_detail_basic" doctitle="Basic" link="#ipv6_settings">2.2. IPv6 settings</div><div class="search_word">2.2. ipv6 settings shows the ipv6 settings. the table items are explained below. ipv6 address displays the ipv6 address setting. ipv6 default gateway displays the ipv6 default gateway settings. press the “setting” button to show the page for ipv6 settings.</div><div class="display_word">2.2. IPv6 settings Shows the IPv6 settings. The table items are explained below. IPv6 address Displays the IPv6 address setting. IPv6 default gateway Displays the IPv6 default gateway settings. Press the “Setting” button to show the page for IPv6 settings.</div></div><div id="gui_en_detail_basic"><div class="search_title" docfname="gui_en_detail_basic" doctitle="Basic" link="#ipv4">3. IPv4 settings page</div><div class="search_word">3. ipv4 settings page this page is for configuring ipv4 settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the setting confirmation screen, press the "ok" button.</div><div class="display_word">3. IPv4 settings page This page is for configuring IPv4 settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the setting confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_basic"><div class="search_title" docfname="gui_en_detail_basic" doctitle="Basic" link="#ipv4_settings_2">3.1. IPv4 settings</div><div class="search_word">3.1. ipv4 settings vlan id from the list, select the vlan to assign ipv4 address. however, the vlan for which frame forwarding is invalid cannot be selected. ipv4 address select the ip address from the following items. only a vlan for which frame forwarding is valid can be specified for this item. only one vlan interfaces can be configured for an ipv4 address. obtain automatically using dhcp when auto-acquire does not work, the link local address is automatically configured by the auto ip function. specify a fixed ip address enter the ip address and subnet mask. ipv4 default gateway specify an ip address for the ipv4 default gateway. if omitted when dhcp is used, the default gateway obtained by dhcp is used.</div><div class="display_word">3.1. IPv4 settings VLAN ID From the list, select the VLAN to assign IPv4 address. However, the VLAN for which frame forwarding is invalid cannot be selected. IPv4 address Select the IP address from the following items. Only a VLAN for which frame forwarding is valid can be specified for this item. Only one VLAN interfaces can be configured for an IPv4 address. Obtain automatically using DHCP When auto-acquire does not work, the link local address is automatically configured by the Auto IP function. Specify a fixed IP address Enter the IP address and subnet mask. IPv4 default gateway Specify an IP address for the IPv4 default gateway. If omitted when DHCP is used, the default gateway obtained by DHCP is used.</div></div><div id="gui_en_detail_basic"><div class="search_title" docfname="gui_en_detail_basic" doctitle="Basic" link="#ipv6">4. IPv6 settings page</div><div class="search_word">4. ipv6 settings page this page is for configuring ipv6 settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the setting confirmation screen, press the "ok" button.</div><div class="display_word">4. IPv6 settings page This page is for configuring IPv6 settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the setting confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_basic"><div class="search_title" docfname="gui_en_detail_basic" doctitle="Basic" link="#ipv6_settings_2">4.1. IPv6 settings</div><div class="search_word">4.1. ipv6 settings vlan id from the list, select the vlan to assign ipv6 address. however, the vlan for which frame forwarding is invalid cannot be selected. ipv6 address only one vlan interfaces can be configured for an ipv6 address. select whether the ipv6 address will be enabled or disabled from the following items. disable ipv6 enable ipv6 for global addresses, select from the following items. not set obtain automatically using ra specify a fixed ip address enter the ip address and subnet mask. set the link local address. ipv6 default gateway specify an ipv6 address for the ipv6 default gateway. if omitted when ra is used, the default gateway obtained by ra is used.</div><div class="display_word">4.1. IPv6 settings VLAN ID From the list, select the VLAN to assign IPv6 address. However, the VLAN for which frame forwarding is invalid cannot be selected. IPv6 address Only one VLAN interfaces can be configured for an IPv6 address. Select whether the IPv6 address will be enabled or disabled from the following items. Disable IPv6 Enable IPv6 For global addresses, select from the following items. Not set Obtain automatically using RA Specify a fixed IP address Enter the IP address and subnet mask. Set the link local address. IPv6 default gateway Specify an IPv6 address for the IPv6 default gateway. If omitted when RA is used, the default gateway obtained by RA is used.</div></div><div id="gui_en_detail_dns"><div class="search_title" docfname="gui_en_detail_dns" doctitle="DNS" link="#title-box">DNS client</div><div class="search_word">dns client</div><div class="display_word">DNS client</div></div><div id="gui_en_detail_dns"><div class="search_title" docfname="gui_en_detail_dns" doctitle="DNS" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for configuring the dns client settings.</div><div class="display_word">1. Summary This page is for configuring the DNS client settings.</div></div><div id="gui_en_detail_dns"><div class="search_title" docfname="gui_en_detail_dns" doctitle="DNS" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the dns client.</div><div class="display_word">2. Top page This is the top page for the DNS client.</div></div><div id="gui_en_detail_dns"><div class="search_title" docfname="gui_en_detail_dns" doctitle="DNS" link="#dns_client_settings">2.1. DNS client settings</div><div class="search_word">2.1. dns client settings displays the dns client settings. the table items are explained below. dns client functions displays the settings for whether to enable or disable the dns client function. dns server address displays the dns server address settings used during inquiry for name resolution. default domain displays the default domain settings. search domain displays the search domain settings. press the "setting" button to access a page where you can configure the dns client settings.</div><div class="display_word">2.1. DNS client settings Displays the DNS client settings. The table items are explained below. DNS client functions Displays the settings for whether to enable or disable the DNS client function. DNS server address Displays the DNS server address settings used during inquiry for name resolution. Default domain Displays the default domain settings. Search domain Displays the search domain settings. Press the "Setting" button to access a page where you can configure the DNS client settings.</div></div><div id="gui_en_detail_dns"><div class="search_title" docfname="gui_en_detail_dns" doctitle="DNS" link="#client">3. DNS client settings page</div><div class="search_word">3. dns client settings page this page is for configuring the dns client settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the setting confirmation screen, press the "ok" button.</div><div class="display_word">3. DNS client settings page This page is for configuring the DNS client settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the setting confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_dns"><div class="search_title" docfname="gui_en_detail_dns" doctitle="DNS" link="#dns_client_settings_2">3.1. DNS client settings</div><div class="search_word">3.1. dns client settings dns client functions select the operation for the dns client function from the following options. enable disable dns server address specify the dns server address. for the server address, either an ipv4 address or an ipv6 address can be specified. up to three server addresses can be specified. default domain specify the default domain. up to 255 characters can be inputted. search domain specify the search domain. up to 255 characters can be inputted. up to six search domains can be specified.</div><div class="display_word">3.1. DNS client settings DNS client functions Select the operation for the DNS client function from the following options. Enable Disable DNS server address Specify the DNS server address. For the server address, either an IPv4 address or an IPv6 address can be specified. Up to three server addresses can be specified. Default domain Specify the default domain. Up to 255 characters can be inputted. Search domain Specify the search domain. Up to 255 characters can be inputted. Up to six search domains can be specified.</div></div><div id="gui_en_detail_flow_control"><div class="search_title" docfname="gui_en_detail_flow_control" doctitle="Flow" link="#title-box">Flow control</div><div class="search_word">flow control</div><div class="display_word">Flow control</div></div><div id="gui_en_detail_flow_control"><div class="search_title" docfname="gui_en_detail_flow_control" doctitle="Flow" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can edit the settings of the flow control. you can enable/disable the flow control. if the flow control is enabled, frame discarding can be controlled when a network is congested.</div><div class="display_word">1. Summary In this page you can edit the settings of the flow control. You can enable/disable the flow control. If the flow control is enabled, frame discarding can be controlled when a network is congested.</div></div><div id="gui_en_detail_flow_control"><div class="search_title" docfname="gui_en_detail_flow_control" doctitle="Flow" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for flow control.</div><div class="display_word">2. Top page This is the top page for flow control.</div></div><div id="gui_en_detail_flow_control"><div class="search_title" docfname="gui_en_detail_flow_control" doctitle="Flow" link="#flow_control_basic_settings">2.1. Flow control basic settings</div><div class="search_word">2.1. flow control basic settings the current setting is shown as to whether the flow control is used. press the "setting" button to access a page where you can change the settings.</div><div class="display_word">2.1. Flow control basic settings The current setting is shown as to whether the flow control is used. Press the "Setting" button to access a page where you can change the settings.</div></div><div id="gui_en_detail_flow_control"><div class="search_title" docfname="gui_en_detail_flow_control" doctitle="Flow" link="#flow_control_settings">2.2. Flow control settings</div><div class="search_word">2.2. flow control settings the flow control setting is shown for each lan port. press the "setting" button to access a page where you can change the settings of the selected lan port. if you press the "specify all" button, the settings can be changed for all lan ports whose check box contains a check mark. if you press the "return to defaults" button, the settings will be initialized for all lan ports whose check box contains a check mark. the default flow control setting for all ports is "disabled". if the settings do not use the flow control for the entire system, flow control settings for each lan port cannot be made.</div><div class="display_word">2.2. Flow control settings The flow control setting is shown for each LAN port. Press the "Setting" button to access a page where you can change the settings of the selected LAN port. If you press the "Specify all" button, the settings can be changed for all LAN ports whose check box contains a check mark. If you press the "Return to defaults" button, the settings will be initialized for all LAN ports whose check box contains a check mark. The default flow control setting for all ports is "Disabled". If the settings do not use the flow control for the entire system, flow control settings for each LAN port cannot be made.</div></div><div id="gui_en_detail_flow_control"><div class="search_title" docfname="gui_en_detail_flow_control" doctitle="Flow" link="#flow_control_system">3. Flow control basic settings page</div><div class="search_word">3. flow control basic settings page in this page you can specify whether the flow control is used for the entire system. enter the settings, and then press the "confirm" button. if there are no mistakes in the setting confirmation screen, press the "ok" button.</div><div class="display_word">3. Flow control basic settings page In this page you can specify whether the flow control is used for the entire system. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the setting confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_flow_control"><div class="search_title" docfname="gui_en_detail_flow_control" doctitle="Flow" link="#flow_control_basic_settings_2">3.1. Flow control basic settings</div><div class="search_word">3.1. flow control basic settings flow control don’t use flow control the flow control will be disabled for the entire system. use flow control the flow control will be enabled for the entire system.</div><div class="display_word">3.1. Flow control basic settings Flow control Don’t use flow control The flow control will be disabled for the entire system. Use flow control The flow control will be enabled for the entire system.</div></div><div id="gui_en_detail_flow_control"><div class="search_title" docfname="gui_en_detail_flow_control" doctitle="Flow" link="#flow_control_if">4. Flow control settings page</div><div class="search_word">4. flow control settings page in this page you can specify whether the flow control is used for the selected interface. enter the settings, and then press the "confirm" button. if there are no mistakes in the setting confirmation screen, press the "ok" button.</div><div class="display_word">4. Flow control settings page In this page you can specify whether the flow control is used for the selected interface. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the setting confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_flow_control"><div class="search_title" docfname="gui_en_detail_flow_control" doctitle="Flow" link="#flow_control_settings_2">4.1. Flow control settings</div><div class="search_word">4.1. flow control settings port the lan port for which settings are made is shown. flow control disabled the flow control will be disabled for the selected interface. enabled the flow control will be enabled for the selected interface.</div><div class="display_word">4.1. Flow control settings Port The LAN port for which settings are made is shown. Flow control Disabled The flow control will be disabled for the selected interface. Enabled The flow control will be enabled for the selected interface.</div></div><div id="gui_en_detail_igmp_snooping"><div class="search_title" docfname="gui_en_detail_igmp_snooping" doctitle="IGMP" link="#title-box">IGMP snooping</div><div class="search_word">igmp snooping</div><div class="display_word">IGMP snooping</div></div><div id="gui_en_detail_igmp_snooping"><div class="search_title" docfname="gui_en_detail_igmp_snooping" doctitle="IGMP" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can edit the settings of the igmp snooping function.</div><div class="display_word">1. Summary In this page you can edit the settings of the IGMP snooping function.</div></div><div id="gui_en_detail_igmp_snooping"><div class="search_title" docfname="gui_en_detail_igmp_snooping" doctitle="IGMP" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for igmp snooping.</div><div class="display_word">2. Top page This is the top page for IGMP snooping.</div></div><div id="gui_en_detail_igmp_snooping"><div class="search_title" docfname="gui_en_detail_igmp_snooping" doctitle="IGMP" link="#igmp_snooping_function_settings">2.1. IGMP snooping function settings</div><div class="search_word">2.1. igmp snooping function settings igmp snooping function settings are shown for each vlan id that is defined a maximum of 20 items can be displayed for one page. press or or enter a numeric value to switch between pages. when you press the "setting" button, a page where you can change the igmp snooping function settings for the selected vlan id will appear if you press the "specify all" button, the settings can be changed for all vlan ids whose check box contains a check mark if you press the "return to defaults" button, the settings will be initialized for all vlan ids whose check box contains a check mark default settings for the igmp snooping function are as follows igmp snooping function: enabled igmp version: igmpv3 igmp query: no transmission igmp query transmission interval: 125 seconds ttl check: enabled ra check : disabled tos check : disabled multicast router port : none data transfer suppression function for multicast router ports : disabled report suppression function : enabled report forwarding function : disabled fast leave function : disabled</div><div class="display_word">2.1. IGMP snooping function settings IGMP snooping function settings are shown for each VLAN ID that is defined A maximum of 20 items can be displayed for one page. Press or or enter a numeric value to switch between pages. When you press the "Setting" button, a page where you can change the IGMP snooping function settings for the selected VLAN ID will appear If you press the "Specify all" button, the settings can be changed for all VLAN IDs whose check box contains a check mark If you press the "Return to defaults" button, the settings will be initialized for all VLAN IDs whose check box contains a check mark Default settings for the IGMP snooping function are as follows IGMP snooping function: Enabled IGMP version: IGMPv3 IGMP query: No transmission IGMP query transmission interval: 125 seconds TTL check: Enabled RA check : Disabled ToS check : Disabled Multicast router port : None Data transfer suppression function for multicast router ports : Disabled Report suppression function : Enabled Report forwarding function : Disabled Fast leave function : Disabled</div></div><div id="gui_en_detail_igmp_snooping"><div class="search_title" docfname="gui_en_detail_igmp_snooping" doctitle="IGMP" link="#igmp_config">3. IGMP snooping function settings page</div><div class="search_word">3. igmp snooping function settings page in this page you can make various settings for the igmp snooping function. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. IGMP snooping function settings page In this page you can make various settings for the IGMP snooping function. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_igmp_snooping"><div class="search_title" docfname="gui_en_detail_igmp_snooping" doctitle="IGMP" link="#igmp_snooping_function_settings_2">3.1. IGMP snooping function settings</div><div class="search_word">3.1. igmp snooping function settings vlan id the vlan id for which settings are being made is shown igmp snooping settings enabled ( control transmission of ip multicast packets ) enable igmp snooping. multicast packets are forwarded only to the port to which the terminal you want to receive them is connected. this function monitors (snoops) igmp messages exchanged between receiving terminals and a multicast router. it can suppress the flooding of multicast packets and reduce network bandwidth usage. disabled ( flood ip multicast packets ) disable igmp snooping multicast packets are always forwarded to all ports in the same vlan. version select the igmp version from the following items. igmpv3 igmpv2 igmp query no transmission igmp query transmission function is disabled transmit periodically igmp query transmission function is enabled. the transmission interval can be specified in the range of 20 seconds to 18000 seconds ttl check select the ttl check from the following items. enabled ( igmp packets other than ttl=1 are discarded ) disabled ( igmp packets other than ttl=1 are corrected to ttl=1 and transmitted ) ra check select the ra check from the following items. disabled ( ra option is added to igmp packets and transmitted ) enabled ( igmp packets without a ra option are discarded ) tos check select the tos check from the following items. disabled ( tos is corrected to 0xc0 in igmp packets and transmitted ) enabled ( igmp packets with invalid tos are discarded ) multicast router port the multicast router port is the interface to which the multicast router is connected. this device automatically learns the interface that receives the igmp query as the multicast router port. also, you can statically configure the multicast router port. to statically configure multicast router ports, press the "select" button. the interfaces that belong to the specified vlan id are listed. then, check the check box of the interface to use as the multicast router port, and press the "confirm" button. data transfer suppression function for multicast router ports this function suppresses network traffic load by stopping unnecessary multicast frames transfer to the multicast router port. select from the following items. disable disabling this function causes multicast frames to be transferred to the multicast router port as well if any port is receiving igmp report messages. enable enabling this function causes multicast frames to be transferred to the multicast router port as well only when the multicast router port receives igmp report messages. report suppression function this function suppresses the network traffic load between the multicast router and the host. select from the following items. enable enabling this function transfers received igmp report and leave messages to the igmp querier at once. disable disabling this function transfers received igmp report and leave messages to the igmp querier as is without combining them. report forwarding function this function transfers igmp report and leave messages to the port where a switch is connected in the same vlan. the system capabilities information included in the lldp basic management tlv is used to judge whether a switch is connected to the port or not. select from the following items. enable enabling this function transfers received igmp report and leave messages to the multicast router ports and the ports where a switch is connected. disable disabling this function transfers received igmp report and leave messages to the multicast router ports only. fast leave function fast leave function is a function not to check the receiver’s existence in the igmp leave process. this function is effective when only one receiver is connected to the lan/sfp port. select from the following items. disable disable the fast leave function. the igmp leave process sends a group-specific query to check the receivers' existence. enable enable the fast leave function. the igmp leave process does not check the receiver’s existence. when the "disable on ports where a switch is connected" is checked, the fast leave function is not used on the port where a switch is connected.</div><div class="display_word">3.1. IGMP snooping function settings VLAN ID The VLAN ID for which settings are being made is shown IGMP snooping settings Enabled ( Control transmission of IP multicast packets ) Enable IGMP snooping. Multicast packets are forwarded only to the port to which the terminal you want to receive them is connected. This function monitors (snoops) IGMP messages exchanged between receiving terminals and a multicast router. It can suppress the flooding of multicast packets and reduce network bandwidth usage. Disabled ( Flood IP multicast packets ) Disable IGMP snooping Multicast packets are always forwarded to all ports in the same VLAN. Version Select the IGMP version from the following items. IGMPv3 IGMPv2 IGMP query No transmission IGMP query transmission function is disabled Transmit periodically IGMP query transmission function is enabled. The transmission interval can be specified in the range of 20 seconds to 18000 seconds TTL check Select the TTL check from the following items. Enabled ( IGMP packets other than TTL=1 are discarded ) Disabled ( IGMP packets other than TTL=1 are corrected to TTL=1 and transmitted ) RA check Select the RA check from the following items. Disabled ( RA option is added to IGMP packets and transmitted ) Enabled ( IGMP packets without a RA option are discarded ) ToS check Select the ToS check from the following items. Disabled ( ToS is corrected to 0xc0 in IGMP packets and transmitted ) Enabled ( IGMP packets with invalid ToS are discarded ) Multicast router port The multicast router port is the interface to which the multicast router is connected. This device automatically learns the interface that receives the IGMP query as the multicast router port. Also, you can statically configure the multicast router port. To statically configure multicast router ports, press the "Select" button. The interfaces that belong to the specified VLAN ID are listed. Then, check the check box of the interface to use as the multicast router port, and press the "Confirm" button. Data transfer suppression function for multicast router ports This function suppresses network traffic load by stopping unnecessary multicast frames transfer to the multicast router port. Select from the following items. Disable Disabling this function causes multicast frames to be transferred to the multicast router port as well if any port is receiving IGMP report messages. Enable Enabling this function causes multicast frames to be transferred to the multicast router port as well only when the multicast router port receives IGMP report messages. Report suppression function This function suppresses the network traffic load between the multicast router and the host. Select from the following items. Enable Enabling this function transfers received IGMP report and leave messages to the IGMP querier at once. Disable Disabling this function transfers received IGMP report and leave messages to the IGMP querier as is without combining them. Report forwarding function This function transfers IGMP report and leave messages to the port where a switch is connected in the same VLAN. The System Capabilities information included in the LLDP Basic Management TLV is used to judge whether a switch is connected to the port or not. Select from the following items. Enable Enabling this function transfers received IGMP report and leave messages to the multicast router ports and the ports where a switch is connected. Disable Disabling this function transfers received IGMP report and leave messages to the multicast router ports only. Fast leave function Fast leave function is a function not to check the receiver’s existence in the IGMP leave process. This function is effective when only one receiver is connected to the LAN/SFP port. Select from the following items. Disable Disable the fast leave function. The IGMP leave process sends a group-specific query to check the receivers' existence. Enable Enable the fast leave function. The IGMP leave process does not check the receiver’s existence. When the "Disable on ports where a switch is connected" is checked, the fast leave function is not used on the port where a switch is connected.</div></div><div id="gui_en_detail_loop_detect"><div class="search_title" docfname="gui_en_detail_loop_detect" doctitle="Loop" link="#title-box">Loop detection</div><div class="search_word">loop detection</div><div class="display_word">Loop detection</div></div><div id="gui_en_detail_loop_detect"><div class="search_title" docfname="gui_en_detail_loop_detect" doctitle="Loop" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can edit the settings of the loop detection. this function monitors whether a loop is occurring by sending its loop detection frame from the port and whether the frame returns to itself or not.</div><div class="display_word">1. Summary In this page you can edit the settings of the loop detection. This function monitors whether a loop is occurring by sending its loop detection frame from the port and whether the frame returns to itself or not.</div></div><div id="gui_en_detail_loop_detect"><div class="search_title" docfname="gui_en_detail_loop_detect" doctitle="Loop" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for loop detection.</div><div class="display_word">2. Top page This is the top page for loop detection.</div></div><div id="gui_en_detail_loop_detect"><div class="search_title" docfname="gui_en_detail_loop_detect" doctitle="Loop" link="#loop_detection_basic_settings">2.1. Loop detection basic settings</div><div class="search_word">2.1. loop detection basic settings displays the system settings of loop detection. resetting the loop detection status you can immediately resolve the loop detection states (e.g., blocking) by reset feature. the table items are explained below. displays the loop detection settings for the entire system. displays the blocking interval after a loop is detected. press the "setting" button to access a page where you can change the settings.</div><div class="display_word">2.1. Loop detection basic settings Displays the system settings of loop detection. Resetting the loop detection status You can immediately resolve the loop detection states (e.g., Blocking) by reset feature. The table items are explained below. Displays the loop detection settings for the entire system. Displays the blocking interval after a loop is detected. Press the "Setting" button to access a page where you can change the settings.</div></div><div id="gui_en_detail_loop_detect"><div class="search_title" docfname="gui_en_detail_loop_detect" doctitle="Loop" link="#loop_detection_settings">2.2. Loop detection settings</div><div class="search_word">2.2. loop detection settings the loop detection setting and current loop detection status is shown for each lan port. press the "setting" button to access a page where you can change the settings of the selected lan port. if you press the "specify all" button, the settings can be changed for all lan ports whose check box contains a check mark. pressing the "update" button will reacquire the current loop detection status for all lan ports. if you press the "return to defaults" button, the settings will be initialized for all lan ports whose check box contains a check mark. the default loop detection setting for all ports is "enabled". if the settings do not use the loop detection for the entire system, loop detection settings for each lan port cannot be made.</div><div class="display_word">2.2. Loop detection settings The loop detection setting and current loop detection status is shown for each LAN port. Press the "Setting" button to access a page where you can change the settings of the selected LAN port. If you press the "Specify all" button, the settings can be changed for all LAN ports whose check box contains a check mark. Pressing the "Update" button will reacquire the current loop detection status for all LAN ports. If you press the "Return to defaults" button, the settings will be initialized for all LAN ports whose check box contains a check mark. The default loop detection setting for all ports is "Enabled". If the settings do not use the loop detection for the entire system, loop detection settings for each LAN port cannot be made.</div></div><div id="gui_en_detail_loop_detect"><div class="search_title" docfname="gui_en_detail_loop_detect" doctitle="Loop" link="#loop_detect_system">3. Loop detection basic settings page</div><div class="search_word">3. loop detection basic settings page in this page you can specify whether the loop detection is used for the entire system and the blocking interval. enter the settings, and then press the "confirm" button. if there are no mistakes in the setting confirmation screen, press the "ok" button.</div><div class="display_word">3. Loop detection basic settings page In this page you can specify whether the loop detection is used for the entire system and the blocking interval. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the setting confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_loop_detect"><div class="search_title" docfname="gui_en_detail_loop_detect" doctitle="Loop" link="#loop_detection_basic_settings_2">3.1. Loop detection basic settings</div><div class="search_word">3.1. loop detection basic settings loop detection for the entire system enable the loop detection will be enabled for the entire system. disable the loop detection will be disabled for the entire system. blocking interval auto when a loop is resolved, the loop detection state automatically returns to "normal". specify interval even if the loop has already been resolved, the loop detection status keeps "blocking" for the specified period from the time when the loop was detected.</div><div class="display_word">3.1. Loop detection basic settings Loop detection for the entire system Enable The loop detection will be enabled for the entire system. Disable The loop detection will be disabled for the entire system. Blocking interval Auto When a loop is resolved, the loop detection state automatically returns to "Normal". Specify interval Even if the loop has already been resolved, the loop detection status keeps "Blocking" for the specified period from the time when the loop was detected.</div></div><div id="gui_en_detail_loop_detect"><div class="search_title" docfname="gui_en_detail_loop_detect" doctitle="Loop" link="#loop_detect_if">4. Loop detection settings page</div><div class="search_word">4. loop detection settings page in this page you can specify whether the loop detection is used for the selected interface. enter the settings, and then press the "confirm" button. if there are no mistakes in the setting confirmation screen, press the "ok" button.</div><div class="display_word">4. Loop detection settings page In this page you can specify whether the loop detection is used for the selected interface. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the setting confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_loop_detect"><div class="search_title" docfname="gui_en_detail_loop_detect" doctitle="Loop" link="#loop_detection_settings_2">4.1. Loop detection settings</div><div class="search_word">4.1. loop detection settings port the lan port for which settings are made is shown loop detection enabled the loop detection will be enabled for the selected interface. disabled the loop detection will be disabled for the selected interface.</div><div class="display_word">4.1. Loop detection settings Port The LAN port for which settings are made is shown Loop detection Enabled The loop detection will be enabled for the selected interface. Disabled The loop detection will be disabled for the selected interface.</div></div><div id="gui_en_detail_mirroring"><div class="search_title" docfname="gui_en_detail_mirroring" doctitle="Port" link="#title-box">Port mirroring</div><div class="search_word">port mirroring</div><div class="display_word">Port mirroring</div></div><div id="gui_en_detail_mirroring"><div class="search_title" docfname="gui_en_detail_mirroring" doctitle="Port" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for changing the port mirroring settings.</div><div class="display_word">1. Summary This page is for changing the port mirroring settings.</div></div><div id="gui_en_detail_mirroring"><div class="search_title" docfname="gui_en_detail_mirroring" doctitle="Port" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the port mirroring settings.</div><div class="display_word">2. Top page This is the top page for the port mirroring settings.</div></div><div id="gui_en_detail_mirroring"><div class="search_title" docfname="gui_en_detail_mirroring" doctitle="Port" link="#port_mirroring_settings">2.1. Port mirroring settings</div><div class="search_word">2.1. port mirroring settings the current settings for the port mirroring are shown. the table items are explained below. check box select the check box to delete the sniffer port setting. sniffer port displays the interface name of a sniffer port. monitored port displays the interface name of monitored ports. monitoring direction displays the monitoring direction for a monitored port. press the "new" button to display a page where you can create new settings for a sniffer port. press the "setting" button to display the page where you can change the settings of a sniffer port. if you press the "delete" button, all sniffer ports whose check boxes are selected will be deleted. up to 4 sniffer ports can be configured. monitored ports that are already monitored cannot be monitored from another sniffer port. sniffer ports cannot be monitored from another sniffer port.</div><div class="display_word">2.1. Port mirroring settings The current settings for the port mirroring are shown. The table items are explained below. Check box Select the check box to delete the sniffer port setting. Sniffer port Displays the interface name of a sniffer port. Monitored port Displays the interface name of monitored ports. Monitoring direction Displays the monitoring direction for a monitored port. Press the "New" button to display a page where you can create new settings for a sniffer port. Press the "Setting" button to display the page where you can change the settings of a sniffer port. If you press the "Delete" button, all sniffer ports whose check boxes are selected will be deleted. Up to 4 sniffer ports can be configured. Monitored ports that are already monitored cannot be monitored from another sniffer port. Sniffer ports cannot be monitored from another sniffer port.</div></div><div id="gui_en_detail_mirroring"><div class="search_title" docfname="gui_en_detail_mirroring" doctitle="Port" link="#mirroring_set">3. Port mirroring settings page</div><div class="search_word">3. port mirroring settings page this page is for changing the port mirroring settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the setting confirmation screen, press the "ok" button.</div><div class="display_word">3. Port mirroring settings page This page is for changing the port mirroring settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the setting confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_mirroring"><div class="search_title" docfname="gui_en_detail_mirroring" doctitle="Port" link="#port_mirroring_settings_2">3.1. Port mirroring settings</div><div class="search_word">3.1. port mirroring settings sniffer port when configuring new settings from the list, select the interface for a sniffer port. other interfaces that are already monitored and sniffer ports are not displayed in the list. when changing settings displays the interface name of the selected sniffer port. monitored port select the ports that will be monitored from a selected sniffer port. press the "select" button to display the “monitored port selection” dialog. monitored ports can be selected in the “monitored port selection” dialog by placing a checkmark in the corresponding checkbox, selecting the monitoring direction, and pressing the “ok” button.</div><div class="display_word">3.1. Port mirroring settings Sniffer port When configuring new settings From the list, select the interface for a sniffer port. Other interfaces that are already monitored and sniffer ports are not displayed in the list. When changing settings Displays the interface name of the selected sniffer port. Monitored port Select the ports that will be monitored from a selected sniffer port. Press the "Select" button to display the “Monitored port selection” dialog. Monitored ports can be selected in the “Monitored port selection” dialog by placing a checkmark in the corresponding checkbox, selecting the monitoring direction, and pressing the “OK” button.</div></div><div id="gui_en_detail_mld_snooping"><div class="search_title" docfname="gui_en_detail_mld_snooping" doctitle="MLD" link="#title-box">MLD snooping</div><div class="search_word">mld snooping</div><div class="display_word">MLD snooping</div></div><div id="gui_en_detail_mld_snooping"><div class="search_title" docfname="gui_en_detail_mld_snooping" doctitle="MLD" link="#section1">1. Summary</div><div class="search_word">1. summary in this page you can edit the settings of the mld snooping.</div><div class="display_word">1. Summary In this page you can edit the settings of the MLD snooping.</div></div><div id="gui_en_detail_mld_snooping"><div class="search_title" docfname="gui_en_detail_mld_snooping" doctitle="MLD" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for mld snooping.</div><div class="display_word">2. Top page This is the top page for MLD snooping.</div></div><div id="gui_en_detail_mld_snooping"><div class="search_title" docfname="gui_en_detail_mld_snooping" doctitle="MLD" link="#mld_snooping_settings">2.1. MLD snooping settings</div><div class="search_word">2.1. mld snooping settings mld snooping settings are shown for each vlan id that is defined. a maximum of 20 items can be displayed for one page. press or or enter a numeric value to switch between pages. when you press the "setting" button, a page where you can change the mld snooping settings for the selected vlan id will appear. if you press the "specify all" button, the settings can be changed for all vlan ids whose check box contains a check mark. if you press the "return to defaults" button, the settings will be initialized for all vlan ids whose check box contains a check mark. default settings for the mld snooping are as follows. mld snooping : disabled version : mldv2 mld query : no transmission mld query transmission interval : 125 seconds multicast router port : none report suppression function : enabled fast leave function : disabled</div><div class="display_word">2.1. MLD snooping settings MLD snooping settings are shown for each VLAN ID that is defined. A maximum of 20 items can be displayed for one page. Press or or enter a numeric value to switch between pages. When you press the "Setting" button, a page where you can change the MLD snooping settings for the selected VLAN ID will appear. If you press the "Specify all" button, the settings can be changed for all VLAN IDs whose check box contains a check mark. If you press the "Return to defaults" button, the settings will be initialized for all VLAN IDs whose check box contains a check mark. Default settings for the MLD snooping are as follows. MLD snooping : Disabled Version : MLDv2 MLD query : No transmission MLD query transmission interval : 125 Seconds Multicast router port : None Report suppression function : Enabled Fast leave function : Disabled</div></div><div id="gui_en_detail_mld_snooping"><div class="search_title" docfname="gui_en_detail_mld_snooping" doctitle="MLD" link="#mld_config">3. MLD snooping settings page</div><div class="search_word">3. mld snooping settings page in this page you can make various settings for the mld snooping. enter the settings, and then press the "confirm" button. if there are no mistakes in the input content of the confirmation screen, press the "ok" button.</div><div class="display_word">3. MLD snooping settings page In this page you can make various settings for the MLD snooping. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the input content of the confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_mld_snooping"><div class="search_title" docfname="gui_en_detail_mld_snooping" doctitle="MLD" link="#mld_snooping_settings_2">3.1. MLD snooping settings</div><div class="search_word">3.1. mld snooping settings vlan id the vlan id for which settings are being made is shown. mld snooping enabled ( control transmission of ipv6 multicast packets ) enable mld snooping multicast packets are forwarded only to the port to which the terminal you want to receive them is connected. this function monitors (snoops) mld messages exchanged between receiving terminals and a multicast router. it can suppress the flooding of multicast packets and reduce network bandwidth usage. disabled ( flood ipv6 multicast packets ) disables the mld snooping multicast packets are always forwarded to all ports in the same vlan. version select the mld version from the following items. mldv1 mldv2 mld query no transmission mld query transmission function is disabled. transmit periodically mld query transmission function is enabled. the transmission interval can be specified in the range of 20 seconds to 18000 seconds. multicast router port the multicast router port is the interface used to connect multicast routers. this device automatically learns the interface that receives the mld query as the multicast router port. also, you can statically configure the multicast router port. to statically configure multicast router ports, press the "select" button. the interfaces that belong to the specified vlan id are listed. then, check the check box of the interface to use as the multicast router port, and press the "confirm" button. report suppression function this function suppresses the network traffic load between the multicast router and the host. select from the following items. enable enabling this function transfers received mld report and leave messages to the mld querier at once. disable disabling this function transfers received mld report and leave messages to the mld querier as is without combining them. fast leave function fast leave function is a function not to check the receiver’s existence in the mld leave process. this function is effective when only one receiver is connected to the lan/sfp port. select from the following items. disable disable the fast leave function. the mld leave process sends a group-specific query to check the receivers' existence. enable enable the fast leave function. the mld leave process does not check the receiver’s existence.</div><div class="display_word">3.1. MLD snooping settings VLAN ID The VLAN ID for which settings are being made is shown. MLD snooping Enabled ( Control transmission of IPv6 multicast packets ) Enable MLD snooping Multicast packets are forwarded only to the port to which the terminal you want to receive them is connected. This function monitors (snoops) MLD messages exchanged between receiving terminals and a multicast router. It can suppress the flooding of multicast packets and reduce network bandwidth usage. Disabled ( Flood IPv6 multicast packets ) Disables the MLD snooping Multicast packets are always forwarded to all ports in the same VLAN. Version Select the MLD version from the following items. MLDv1 MLDv2 MLD query No transmission MLD query transmission function is disabled. Transmit periodically MLD query transmission function is enabled. The transmission interval can be specified in the range of 20 seconds to 18000 seconds. Multicast router port The multicast router port is the interface used to connect multicast routers. This device automatically learns the interface that receives the MLD query as the multicast router port. Also, you can statically configure the multicast router port. To statically configure multicast router ports, press the "Select" button. The interfaces that belong to the specified VLAN ID are listed. Then, check the check box of the interface to use as the multicast router port, and press the "Confirm" button. Report suppression function This function suppresses the network traffic load between the multicast router and the host. Select from the following items. Enable Enabling this function transfers received MLD report and leave messages to the MLD querier at once. Disable Disabling this function transfers received MLD report and leave messages to the MLD querier as is without combining them. Fast leave function Fast leave function is a function not to check the receiver’s existence in the MLD leave process. This function is effective when only one receiver is connected to the LAN/SFP port. Select from the following items. Disable Disable the fast leave function. The MLD leave process sends a group-specific query to check the receivers' existence. Enable Enable the fast leave function. The MLD leave process does not check the receiver’s existence.</div></div><div id="gui_en_detail_poe_control"><div class="search_title" docfname="gui_en_detail_poe_control" doctitle="PoE" link="#title-box">PoE</div><div class="search_word">poe</div><div class="display_word">PoE</div></div><div id="gui_en_detail_poe_control"><div class="search_title" docfname="gui_en_detail_poe_control" doctitle="PoE" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for changing the poe control settings.</div><div class="display_word">1. Summary This page is for changing the PoE control settings.</div></div><div id="gui_en_detail_poe_control"><div class="search_title" docfname="gui_en_detail_poe_control" doctitle="PoE" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the poe control settings.</div><div class="display_word">2. Top page This is the top page for the PoE control settings.</div></div><div id="gui_en_detail_poe_control"><div class="search_title" docfname="gui_en_detail_poe_control" doctitle="PoE" link="#poe_control_basic_settings">2.1. PoE control basic settings</div><div class="search_word">2.1. poe control basic settings the current settings of the poe control for the entire system are show. press the "setting" button to access a page where you can change the settings.</div><div class="display_word">2.1. PoE control basic settings The current settings of the PoE control for the entire system are show. Press the "Setting" button to access a page where you can change the settings.</div></div><div id="gui_en_detail_poe_control"><div class="search_title" docfname="gui_en_detail_poe_control" doctitle="PoE" link="#poe_control_settings">2.2. PoE control settings</div><div class="search_word">2.2. poe control settings poe control settings are shown for each interface that supports poe power supply. press the "setting" button to access a page where you can change the settings of the selected interface. if you press the "specify all" button, the settings can be changed for all interfaces whose check box contains a check mark. if you press the "return to defaults" button, the settings will be initialized for all interfaces whose check box contains a check mark. the default poe power supply setting is "enabled" and the default power priority setting is "low" for all interfaces that support poe power supply. if the poe control settings is disabled for the entire system, the poe control settings for each interface cannot be made.</div><div class="display_word">2.2. PoE control settings PoE control settings are shown for each interface that supports PoE power supply. Press the "Setting" button to access a page where you can change the settings of the selected interface. If you press the "Specify all" button, the settings can be changed for all interfaces whose check box contains a check mark. If you press the "Return to defaults" button, the settings will be initialized for all interfaces whose check box contains a check mark. The default PoE power supply setting is "Enabled" and the default power priority setting is "Low" for all interfaces that support PoE power supply. If the PoE control settings is disabled for the entire system, the PoE control settings for each interface cannot be made.</div></div><div id="gui_en_detail_poe_control"><div class="search_title" docfname="gui_en_detail_poe_control" doctitle="PoE" link="#poe_control_system">3. PoE control basic settings page</div><div class="search_word">3. poe control basic settings page in this page you can enable/disable poe power supply for the entire system and set the guard band. enter the settings, and then press the "confirm" button. if there are no mistakes in the setting confirmation screen, press the "ok" button.</div><div class="display_word">3. PoE control basic settings page In this page you can enable/disable PoE power supply for the entire system and set the guard band. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the setting confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_poe_control"><div class="search_title" docfname="gui_en_detail_poe_control" doctitle="PoE" link="#poe_control_basic_settings_2">3.1. PoE control basic settings</div><div class="search_word">3.1. poe control basic settings poe power supply for entire system enabled the poe power supply will be enabled for the entire system. disabled the poe power supply will be disabled for the entire system. guard band the guard band specifies the tolerance for the maximum power supply specified to avoid unintended power supply interruptions. the default guard band setting is "7" w, and the input range is 0 - 30.</div><div class="display_word">3.1. PoE control basic settings PoE power supply for entire system Enabled The PoE power supply will be enabled for the entire system. Disabled The PoE power supply will be disabled for the entire system. Guard band The guard band specifies the tolerance for the maximum power supply specified to avoid unintended power supply interruptions. The default guard band setting is "7" W, and the input range is 0 - 30.</div></div><div id="gui_en_detail_poe_control"><div class="search_title" docfname="gui_en_detail_poe_control" doctitle="PoE" link="#poe_control_if">4. PoE control settings page</div><div class="search_word">4. poe control settings page in this page you can enable/disable poe power supply and set power priority for the selected interface. enter the settings, and then press the "confirm" button. if there are no mistakes in the setting confirmation screen, press the "ok" button.</div><div class="display_word">4. PoE control settings page In this page you can enable/disable PoE power supply and set power priority for the selected interface. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the setting confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_poe_control"><div class="search_title" docfname="gui_en_detail_poe_control" doctitle="PoE" link="#poe_control_settings_2">4.1. PoE control settings</div><div class="search_word">4.1. poe control settings port the interface for which settings are made is shown. poe power supply enabled the poe power supply will be enabled for the selected interface. disabled the poe power supply will be disabled for the selected interface. power priority select power priority from the following items. low high critical in descending order, the priority levels are critical , high , or low . if interfaces have the same priority setting, the interface with the lower interface number is prioritized. explanation sets the description text for the interface which supports poe power supply. characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . up to 64 characters can be inputted.</div><div class="display_word">4.1. PoE control settings Port The interface for which settings are made is shown. PoE power supply Enabled The PoE power supply will be enabled for the selected interface. Disabled The PoE power supply will be disabled for the selected interface. Power priority Select power priority from the following items. Low High Critical In descending order, the priority levels are Critical , High , or Low . If interfaces have the same priority setting, the interface with the lower interface number is prioritized. Explanation Sets the description text for the interface which supports PoE power supply. Characters that can be inputted include single-byte alphanumeric characters and symbols, excluding ? . Up to 64 characters can be inputted.</div></div><div id="gui_en_detail_storm_control"><div class="search_title" docfname="gui_en_detail_storm_control" doctitle="Storm" link="#title-box">Storm control</div><div class="search_word">storm control</div><div class="display_word">Storm control</div></div><div id="gui_en_detail_storm_control"><div class="search_title" docfname="gui_en_detail_storm_control" doctitle="Storm" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for changing the storm control settings. if the storm control is enabled, the load on the unit can be reduced by discarding specific frames received that exceed bandwidth threshold values.</div><div class="display_word">1. Summary This page is for changing the storm control settings. If the storm control is enabled, the load on the unit can be reduced by discarding specific frames received that exceed bandwidth threshold values.</div></div><div id="gui_en_detail_storm_control"><div class="search_title" docfname="gui_en_detail_storm_control" doctitle="Storm" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the storm control settings.</div><div class="display_word">2. Top page This is the top page for the storm control settings.</div></div><div id="gui_en_detail_storm_control"><div class="search_title" docfname="gui_en_detail_storm_control" doctitle="Storm" link="#storm_control_settings">2.1. Storm control settings</div><div class="search_word">2.1. storm control settings the current settings for the storm control are shown for each interface. the table items are explained below. check box select the check box for bulk settings or to initialize the settings. port displays the interface name. target frame displays the target frames for storm control. upper limit for bandwidth percent displays the upper limit for the bandwidth percentage. frames received that exceed the upper limit value are discarded. press the "setting" button to display the page where you can change the settings of the selected interface. if you press the "specify all" button, the settings can be changed for all interfaces whose check box is selected. the default settings will be applied to the settings on the storm control settings page. if you press the "return to defaults" button, the settings will be initialized on all interfaces whose check boxes are selected. the storm control is disabled for all ports by default.</div><div class="display_word">2.1. Storm control settings The current settings for the storm control are shown for each interface. The table items are explained below. Check box Select the check box for bulk settings or to initialize the settings. Port Displays the interface name. Target frame Displays the target frames for storm control. Upper limit for bandwidth percent Displays the upper limit for the bandwidth percentage. Frames received that exceed the upper limit value are discarded. Press the "Setting" button to display the page where you can change the settings of the selected interface. If you press the "Specify all" button, the settings can be changed for all interfaces whose check box is selected. The default settings will be applied to the settings on the storm control settings page. If you press the "Return to defaults" button, the settings will be initialized on all interfaces whose check boxes are selected. The storm control is disabled for all ports by default.</div></div><div id="gui_en_detail_storm_control"><div class="search_title" docfname="gui_en_detail_storm_control" doctitle="Storm" link="#storm_control_setting">3. Storm control settings page</div><div class="search_word">3. storm control settings page this page is for storm control settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the setting confirmation screen, press the "ok" button.</div><div class="display_word">3. Storm control settings page This page is for storm control settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the setting confirmation screen, press the "OK" button.</div></div><div id="gui_en_detail_storm_control"><div class="search_title" docfname="gui_en_detail_storm_control" doctitle="Storm" link="#storm_control_settings_2">3.1. Storm control settings</div><div class="search_word">3.1. storm control settings port displays the name of the interface for which settings will be made. storm control select the operation for the storm control from the following options. disabled enabled target frame broadcast frame enables broadcast storm control. multicast frame enables multicast storm control. unicast frame enables control for unicast frames sent from an unknown address. upper limit for bandwidth percent specifies the upper limit value for the bandwidth percentage. upper limit values can be specified to two decimal places. frames received that exceed the upper limit value are discarded. the same upper limit value is applied to all applicable frames.</div><div class="display_word">3.1. Storm control settings Port Displays the name of the interface for which settings will be made. Storm control Select the operation for the storm control from the following options. Disabled Enabled Target frame Broadcast frame Enables broadcast storm control. Multicast frame Enables multicast storm control. Unicast frame Enables control for unicast frames sent from an unknown address. Upper limit for bandwidth percent Specifies the upper limit value for the bandwidth percentage. Upper limit values can be specified to two decimal places. Frames received that exceed the upper limit value are discarded. The same upper limit value is applied to all applicable frames.</div></div><div id="gui_en_management_cable_diagnostics"><div class="search_title" docfname="gui_en_management_cable_diagnostics" doctitle="Cable" link="#title-box">Cable diagnostics</div><div class="search_word">cable diagnostics</div><div class="display_word">Cable diagnostics</div></div><div id="gui_en_management_cable_diagnostics"><div class="search_title" docfname="gui_en_management_cable_diagnostics" doctitle="Cable" link="#section1">1. Summary</div><div class="search_word">1. summary the cable diagnostic function can be used to easily check whether or not the lan cable connected to the lan port has a faulty connection/circuit. it can be used to troubleshoot network problems or as an easy way to check cables when setting up networks.</div><div class="display_word">1. Summary The cable diagnostic function can be used to easily check whether or not the LAN cable connected to the LAN port has a faulty connection/circuit. It can be used to troubleshoot network problems or as an easy way to check cables when setting up networks.</div></div><div id="gui_en_management_cable_diagnostics"><div class="search_title" docfname="gui_en_management_cable_diagnostics" doctitle="Cable" link="#section2">2. Cable diagnostics page</div><div class="search_word">2. cable diagnostics page in this page you can diagnose cables. to diagnose a cable, select the port and press the "execute" button. press the "clear" button to clear the diagnostic results shown.</div><div class="display_word">2. Cable diagnostics page In this page you can diagnose cables. To diagnose a cable, select the port and press the "Execute" button. Press the "Clear" button to clear the diagnostic results shown.</div></div><div id="gui_en_management_cable_diagnostics"><div class="search_title" docfname="gui_en_management_cable_diagnostics" doctitle="Cable" link="#cable_diagnostics">2.1. Cable diagnostics</div><div class="search_word">2.1. cable diagnostics port port diagnosed is displayed. result the status of the cable connected to the lan port is displayed. ok : the cable is electrically connected. open : either a device is not connected on the opposite end or the cable is faulty. short : a short-circuit occurred. distance to cable fault if "open" or "short" is indicated in results, then the distance from the lan port to the cable fault is displayed in meters. estimated cable length if "ok" is indicated in results, then the estimated cable length is displayed in meters. estimated cable length is undetermined when the opposite port is linking up at a link speed of less than 1g or shutdown.</div><div class="display_word">2.1. Cable diagnostics Port Port diagnosed is displayed. Result The status of the cable connected to the LAN port is displayed. OK : The cable is electrically connected. Open : Either a device is not connected on the opposite end or the cable is faulty. Short : A short-circuit occurred. Distance to cable fault If "Open" or "Short" is indicated in results, then the distance from the LAN port to the cable fault is displayed in meters. Estimated cable length If "OK" is indicated in results, then the estimated cable length is displayed in meters. Estimated cable length is undetermined when the opposite port is linking up at a link speed of less than 1G or shutdown.</div></div><div id="gui_en_management_l2ms"><div class="search_title" docfname="gui_en_management_l2ms" doctitle="L2MS" link="#title-box">L2MS settings</div><div class="search_word">l2ms settings</div><div class="display_word">L2MS settings</div></div><div id="gui_en_management_l2ms"><div class="search_title" docfname="gui_en_management_l2ms" doctitle="L2MS" link="#section1">1. Summary</div><div class="search_word">1. summary this page is for changing the l2ms settings. l2ms ( layer2 management service ) is a function for managing yamaha network devices at the layer 2 level. these settings can be used to enable/disable l2ms units or specify frame input permission settings using l2ms filters.</div><div class="display_word">1. Summary This page is for changing the L2MS settings. L2MS ( Layer2 Management Service ) is a function for managing Yamaha network devices at the layer 2 level. These settings can be used to enable/disable L2MS units or specify frame input permission settings using L2MS filters.</div></div><div id="gui_en_management_l2ms"><div class="search_title" docfname="gui_en_management_l2ms" doctitle="L2MS" link="#section2">2. Top page</div><div class="search_word">2. top page this is the top page for the l2ms settings.</div><div class="display_word">2. Top page This is the top page for the L2MS settings.</div></div><div id="gui_en_management_l2ms"><div class="search_title" docfname="gui_en_management_l2ms" doctitle="L2MS" link="#l2ms_settings">2.1. L2MS settings</div><div class="search_word">2.1. l2ms settings the current settings of the l2ms are show. press the "setting" button to access a page where you can change the settings.</div><div class="display_word">2.1. L2MS settings The current settings of the L2MS are show. Press the "Setting" button to access a page where you can change the settings.</div></div><div id="gui_en_management_l2ms"><div class="search_title" docfname="gui_en_management_l2ms" doctitle="L2MS" link="#l2ms_filter_settings">2.2. L2MS filter settings</div><div class="search_word">2.2. l2ms filter settings the current settings for the l2ms filter are shown for each interface. the table items are explained below. check box select the check box for bulk settings or to initialize the settings. port displays the interface name. rejection of l2ms frame displays the filter setting for blocking l2ms frames. rejection of non-l2ms frame displays the filter settings for blocking non-l2ms frames. press the "setting" button to display the page where you can change the settings of the selected interface. if you press the "specify all" button, the settings can be changed for all interfaces whose check box is selected. the default settings will be applied to the settings on the l2ms filter settings page. if you press the "return to defaults" button, the settings will be initialized on all interfaces whose check boxes are selected. each of the default settings are shown below. rejection of l2ms frame : disabled rejection of non-l2ms frame : disabled</div><div class="display_word">2.2. L2MS filter settings The current settings for the L2MS filter are shown for each interface. The table items are explained below. Check box Select the check box for bulk settings or to initialize the settings. Port Displays the interface name. Rejection of L2MS frame Displays the filter setting for blocking L2MS frames. Rejection of Non-L2MS frame Displays the filter settings for blocking non-L2MS frames. Press the "Setting" button to display the page where you can change the settings of the selected interface. If you press the "Specify all" button, the settings can be changed for all interfaces whose check box is selected. The default settings will be applied to the settings on the L2MS filter settings page. If you press the "Return to defaults" button, the settings will be initialized on all interfaces whose check boxes are selected. Each of the default settings are shown below. Rejection of L2MS frame : Disabled Rejection of Non-L2MS frame : Disabled</div></div><div id="gui_en_management_l2ms"><div class="search_title" docfname="gui_en_management_l2ms" doctitle="L2MS" link="#l2ms_setting">3. L2MS settings page</div><div class="search_word">3. l2ms settings page in this page you can enable/disable l2ms. enter the settings, and then press the "confirm" button. if there are no mistakes in the setting confirmation screen, press the "ok" button.</div><div class="display_word">3. L2MS settings page In this page you can enable/disable L2MS. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the setting confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_l2ms"><div class="search_title" docfname="gui_en_management_l2ms" doctitle="L2MS" link="#l2ms_settings_2">3.1. L2MS settings</div><div class="search_word">3.1. l2ms settings l2ms enabled l2ms will be enabled. this device functions as an l2ms agent and can be controlled by the l2ms manager. disabled l2ms will be disabled. l2ms frames can be transmitted in the same manner as non-l2ms frames, but cannot be controlled by the l2ms manager.</div><div class="display_word">3.1. L2MS settings L2MS Enabled L2MS will be enabled. This device functions as an L2MS agent and can be controlled by the L2MS manager. Disabled L2MS will be disabled. L2MS frames can be transmitted in the same manner as non-L2MS frames, but cannot be controlled by the L2MS manager.</div></div><div id="gui_en_management_l2ms"><div class="search_title" docfname="gui_en_management_l2ms" doctitle="L2MS" link="#l2ms_filter_setting">4. L2MS filter settings page</div><div class="search_word">4. l2ms filter settings page this page is for l2ms filter settings. enter the settings, and then press the "confirm" button. if there are no mistakes in the setting confirmation screen, press the "ok" button.</div><div class="display_word">4. L2MS filter settings page This page is for L2MS filter settings. Enter the settings, and then press the "Confirm" button. If there are no mistakes in the setting confirmation screen, press the "OK" button.</div></div><div id="gui_en_management_l2ms"><div class="search_title" docfname="gui_en_management_l2ms" doctitle="L2MS" link="#l2ms_filter_settings_2">4.1. L2MS filter settings</div><div class="search_word">4.1. l2ms filter settings port displays the name of the interface for which settings will be made. rejection of l2ms frame select the operation for the filter for blocking l2ms frames from the following options. disabled enabled rejection of non-l2ms frame select the operation for the filter for blocking non-l2ms frames from the following options. disabled enabled if both filters are enabled, all frames are rejected at the interface. be aware that it will no longer be possible to access the gui form a port where the non-l2ms filter is enabled.</div><div class="display_word">4.1. L2MS filter settings Port Displays the name of the interface for which settings will be made. Rejection of L2MS frame Select the operation for the filter for blocking L2MS frames from the following options. Disabled Enabled Rejection of Non-L2MS frame Select the operation for the filter for blocking non-L2MS frames from the following options. Disabled Enabled If both filters are enabled, all frames are rejected at the interface. Be aware that it will no longer be possible to access the GUI form a port where the non-L2MS filter is enabled.</div></div><div id="gui_en_proav_multicast"><div class="search_title" docfname="gui_en_proav_multicast" doctitle="Multicast" link="#title-box">Multicast</div><div class="search_word">multicast</div><div class="display_word">Multicast</div></div><div id="gui_en_proav_multicast"><div class="search_title" docfname="gui_en_proav_multicast" doctitle="Multicast" link="#summary_multicast">1. Summary</div><div class="search_word">1. summary the multicast page can be used to configure igmp snooping and check the igmp snooping operating status separately for each proav profile. if multicasting via an avoip network, it is generally recommended that igmp snooping be enabled, but that can lead to trouble if operated with improper settings. by learning the basic principles of igmp snooping, this page can be used for simple troubleshooting of igmp snooping issues.</div><div class="display_word">1. Summary The Multicast page can be used to configure IGMP snooping and check the IGMP snooping operating status separately for each ProAV profile. If multicasting via an AVoIP network, it is generally recommended that IGMP snooping be enabled, but that can lead to trouble if operated with improper settings. By learning the basic principles of IGMP snooping, this page can be used for simple troubleshooting of IGMP snooping issues.</div></div><div id="gui_en_proav_multicast"><div class="search_title" docfname="gui_en_proav_multicast" doctitle="Multicast" link="#about_igmp_snooping">2. What’s IGMP snooping</div><div class="search_word">2. what’s igmp snooping igmp snooping is a feature that prevents unnecessary multicast traffic from being forwarded. normally, multicast traffic is flooded to all affiliated ports in the same network, which wastes bandwidth by forwarding multicast traffic to ports where no multicast receiving terminal exists. in contrast, if igmp snooping is enabled, it saves bandwidth by only forwarding the necessary multicast traffic to ports with a receiving terminal connected. the following example shows the difference between flooding and igmp snooping, assuming receiving terminal a (rx a) only wants to receive group a multicast traffic and receiving terminal b (rx b) only wants to receive group b multicast traffic. flooding forwards both group a and group b traffic to the port where rx a is connected, but igmp snooping only forwards group a traffic to the port where rx a is connected. in the case of flooding in the case of igmp snooping switches with igmp snooping enabled use "igmp query" and "igmp report" to learn which multicast group traffic should be sent to which ports. the following example shows the process flow of processing igmp queries and igmp reports. one representative switch in the network periodically sends igmp queries. the switch that sends the igmp queries is called the "querier" . when the multicast receiving terminal receives an igmp query, it sends an igmp report in response. the igmp report contains information about the multicast group traffic that the receiving terminal wants to receive. the switch learns which multicast group traffic to send to which port by snooping on the content in igmp reports. since learned multicast group information is automatically deleted after a certain period of time, in order to maintain the correct learning state one querier must always be present in the same network. if multiple queriers exist in the same network, only one querier is retained and the other switches automatically stop sending queries. note that even if there is no querier, the receiving terminal may spontaneously send an igmp report, such as when the multicast receiving application is started in the receiving terminal. note that if multicast group information is learned without a querier present, the corresponding multicast group traffic might not be forwarded to ports where other receiving terminals are connected.</div><div class="display_word">2. What’s IGMP snooping IGMP snooping is a feature that prevents unnecessary multicast traffic from being forwarded. Normally, multicast traffic is flooded to all affiliated ports in the same network, which wastes bandwidth by forwarding multicast traffic to ports where no multicast receiving terminal exists. In contrast, if IGMP snooping is enabled, it saves bandwidth by only forwarding the necessary multicast traffic to ports with a receiving terminal connected. The following example shows the difference between flooding and IGMP snooping, assuming receiving terminal A (RX A) only wants to receive Group A multicast traffic and receiving terminal B (RX B) only wants to receive Group B multicast traffic. Flooding forwards both Group A and Group B traffic to the port where RX A is connected, but IGMP snooping only forwards Group A traffic to the port where RX A is connected. In the case of flooding In the case of IGMP snooping Switches with IGMP snooping enabled use "IGMP Query" and "IGMP Report" to learn which multicast group traffic should be sent to which ports. The following example shows the process flow of processing IGMP queries and IGMP reports. One representative switch in the network periodically sends IGMP queries. The switch that sends the IGMP queries is called the "Querier" . When the multicast receiving terminal receives an IGMP query, it sends an IGMP report in response. The IGMP report contains information about the multicast group traffic that the receiving terminal wants to receive. The switch learns which multicast group traffic to send to which port by snooping on the content in IGMP reports. Since learned multicast group information is automatically deleted after a certain period of time, in order to maintain the correct learning state one querier must always be present in the same network. If multiple queriers exist in the same network, only one querier is retained and the other switches automatically stop sending queries. Note that even if there is no querier, the receiving terminal may spontaneously send an IGMP report, such as when the multicast receiving application is started in the receiving terminal. Note that if multicast group information is learned without a querier present, the corresponding multicast group traffic might not be forwarded to ports where other receiving terminals are connected.</div></div><div id="gui_en_proav_multicast"><div class="search_title" docfname="gui_en_proav_multicast" doctitle="Multicast" link="#how_to_use_multicast">3. How to use this page</div><div class="search_word">3. how to use this page</div><div class="display_word">3. How to use this page</div></div><div id="gui_en_proav_multicast"><div class="search_title" docfname="gui_en_proav_multicast" doctitle="Multicast" link="#introduction_multicast">3.1. Introduction</div><div class="search_word">3.1. introduction this page can be used as a troubleshooting tool if a problem related to igmp snooping occurs. igmp snooping is enabled when profiles are specified on the proav profile page. in this page, igmp snooping settings can be changed and the igmp snooping operating status checked separately for each proav profile. first, select a profile from the profile select box in the upper left corner of the page. if a proav profile has not been specified, specify the profile on the proav profiles page.</div><div class="display_word">3.1. Introduction This page can be used as a troubleshooting tool if a problem related to IGMP snooping occurs. IGMP snooping is enabled when profiles are specified on the ProAV profile page. In this page, IGMP snooping settings can be changed and the IGMP snooping operating status checked separately for each ProAV profile. First, select a profile from the profile select box in the upper left corner of the page. If a ProAV profile has not been specified, specify the profile on the ProAV Profiles page.</div></div><div id="gui_en_proav_multicast"><div class="search_title" docfname="gui_en_proav_multicast" doctitle="Multicast" link="#warning_message">3.2. Warning message</div><div class="search_word">3.2. warning message when igmp snooping is enabled, a warning message appears if the switch detects improper settings. if a warning message appears, review the settings and change them if necessary. warning message display message how to handle warnings the igmp version (v2) specified in the profile does not match the version (v3) of the igmp query received. set the igmp version in the profile to the same version as the igmp query. change the igmp version. query transmission is stopped due to the presence of another querier enable igmp query transmission.</div><div class="display_word">3.2. Warning message When IGMP snooping is enabled, a warning message appears if the switch detects improper settings. If a warning message appears, review the settings and change them if necessary. Warning message Display message How to handle warnings The IGMP version (V2) specified in the profile does not match the version (V3) of the IGMP query received. Set the IGMP version in the profile to the same version as the IGMP query. Change the IGMP version. Query transmission is stopped due to the presence of another querier Enable IGMP query transmission.</div></div><div id="gui_en_proav_multicast"><div class="search_title" docfname="gui_en_proav_multicast" doctitle="Multicast" link="#igmp_snooping_set">3.3. Change IGMP snooping settings</div><div class="search_word">3.3. change igmp snooping settings the following settings related to igmp snooping can be changed for each proav profile igmp snooping settings disabled ( flood ip multicast packets ) disable igmp snooping multicast packets are always forwarded to all ports in the same vlan. enabled ( control transmission of ip multicast packets ) enable igmp snooping. multicast packets are forwarded only to the port to which the terminal you want to receive them is connected. this function monitors (snoops) igmp messages exchanged between receiving terminals and a multicast router. it can suppress the flooding of multicast packets and reduce network bandwidth usage. version select the igmp version from the following items. igmpv3 igmpv2 igmp query no transmission igmp query transmission function is disabled transmit periodically igmp query transmission function is enabled. the transmission interval can be specified in the range of 20 seconds to 18000 seconds processing method for unknown multicast frames specify the processing method for unknown multicast frames from below. flood discard if igmp snooping is disabled, "flood" is automatically selected.</div><div class="display_word">3.3. Change IGMP snooping settings The following settings related to IGMP snooping can be changed for each ProAV profile IGMP snooping settings Disabled ( Flood IP multicast packets ) Disable IGMP snooping Multicast packets are always forwarded to all ports in the same VLAN. Enabled ( Control transmission of IP multicast packets ) Enable IGMP snooping. Multicast packets are forwarded only to the port to which the terminal you want to receive them is connected. This function monitors (snoops) IGMP messages exchanged between receiving terminals and a multicast router. It can suppress the flooding of multicast packets and reduce network bandwidth usage. Version Select the IGMP version from the following items. IGMPv3 IGMPv2 IGMP query No transmission IGMP query transmission function is disabled Transmit periodically IGMP query transmission function is enabled. The transmission interval can be specified in the range of 20 seconds to 18000 seconds Processing method for unknown multicast frames Specify the processing method for unknown multicast frames from below. Flood Discard If IGMP snooping is disabled, "Flood" is automatically selected.</div></div><div id="gui_en_proav_multicast"><div class="search_title" docfname="gui_en_proav_multicast" doctitle="Multicast" link="#igmp_snooping_status">3.4. Check IGMP snooping operating status</div><div class="search_word">3.4. check igmp snooping operating status igmp snooping learning status can be checked for each proav profile. if a group is selected in the "multicast group" select box, the corresponding igmp report/query learning status is displayed. mouse-over the port with the learning status displayed to show a tooltip with detailed igmp report/query information. note that if both an igmp report and igmp query is received at the same port, information about both are displayed in the tooltip. igmp report/query learning status display item port display tooltip information igmp report receiving port receiving port information last received report information （ ip address, version ） igmp query receiving port receiving port information received query information ( ip address, version ) since the learning status for multicast groups changes over time, click the "update" button to update the display. when a multicast group has been learned by an igmp report, the ip address of the multicast group is displayed in the "multicast group" select box. traffic being sent to learned multicast groups is only forwarded to igmp report receiving ports. unknown multicast groups are not displayed in the "multicast group" select box. if a proav profile is specified, unknown multicast group traffic is discarded. please change the setting, if you want to flood an unknown multicast group. if a problem that prevents receiving multicast traffic occurs, check whether the port indicator where the receiving terminal is connected is illuminated orange (which indicates it is an igmp report receiving port). if the connection port indicator is not orange, the receiving terminal might be connected to a port with a different profile. check the profile setting for the port where it is connected. if that does not solve the problem, try disabling igmp snooping, but determine whether the bandwidth is sufficient before disabling igmp snooping.</div><div class="display_word">3.4. Check IGMP snooping operating status IGMP snooping learning status can be checked for each ProAV profile. If a group is selected in the "Multicast Group" select box, the corresponding IGMP report/query learning status is displayed. Mouse-over the port with the learning status displayed to show a tooltip with detailed IGMP report/query information. Note that if both an IGMP report and IGMP query is received at the same port, information about both are displayed in the tooltip. IGMP report/query learning status Display item Port display Tooltip information IGMP report receiving port Receiving port information Last received report information （ IP address, Version ） IGMP query receiving port Receiving port information Received query information ( IP address, Version ) Since the learning status for multicast groups changes over time, click the "Update" button to update the display. When a multicast group has been learned by an IGMP report, the IP address of the multicast group is displayed in the "Multicast Group" select box. Traffic being sent to learned multicast groups is only forwarded to IGMP report receiving ports. Unknown multicast groups are not displayed in the "Multicast Group" select box. If a ProAV profile is specified, unknown multicast group traffic is discarded. Please change the setting, if you want to flood an unknown multicast group. If a problem that prevents receiving multicast traffic occurs, check whether the port indicator where the receiving terminal is connected is illuminated orange (which indicates it is an IGMP report receiving port). If the connection port indicator is not orange, the receiving terminal might be connected to a port with a different profile. Check the profile setting for the port where it is connected. If that does not solve the problem, try disabling IGMP snooping, but determine whether the bandwidth is sufficient before disabling IGMP snooping.</div></div><div id="gui_en_proav_profile"><div class="search_title" docfname="gui_en_proav_profile" doctitle="ProAV" link="#title-box">ProAV profile</div><div class="search_word">proav profile</div><div class="display_word">ProAV profile</div></div><div id="gui_en_proav_profile"><div class="search_title" docfname="gui_en_proav_profile" doctitle="ProAV" link="#summary_profile">1. Summary</div><div class="search_word">1. summary the proav profile page can be used to configure all settings for optimizing the avoip network that carries audio and video traffic. in this unit, following proav profiles can be configured. dante dante is an audio networking solution developed by audinate for professional audio applications. a single lan cable is used to bi-directionally communicate information necessary for digital audio systems, such as for transmitting multiple channels of audio signals, clock synchronization signals, and control signals. ndi ndi is a new protocol developed by newtek that supports live video production workflows within ip applications. it enables real-time interactive transmission of video, audio, meta data, and other information within typical gigabit ethernet environments. for details on the commands configured by a proav profile, refer to network device technical information page .</div><div class="display_word">1. Summary The ProAV Profile page can be used to configure all settings for optimizing the AVoIP network that carries audio and video traffic. In this unit, following ProAV profiles can be configured. Dante Dante is an audio networking solution developed by Audinate for professional audio applications. A single LAN cable is used to bi-directionally communicate information necessary for digital audio systems, such as for transmitting multiple channels of audio signals, clock synchronization signals, and control signals. NDI NDI is a new protocol developed by Newtek that supports live video production workflows within IP applications. It enables real-time interactive transmission of video, audio, meta data, and other information within typical Gigabit Ethernet environments. For details on the commands configured by a ProAV profile, refer to Network device technical information page .</div></div><div id="gui_en_proav_profile"><div class="search_title" docfname="gui_en_proav_profile" doctitle="ProAV" link="#how_to_use_profile">2. How to use this page</div><div class="search_word">2. how to use this page</div><div class="display_word">2. How to use this page</div></div><div id="gui_en_proav_profile"><div class="search_title" docfname="gui_en_proav_profile" doctitle="ProAV" link="#introduction_profile">2.1. Introduction</div><div class="search_word">2.1. introduction this page can be used as a kitting tool for configuring optimal avoip network settings. qos, multicast control, and other settings can all be set to optimal values at the same time by simply selecting a proav profile. the proav profile configured on this page assumes the unit will be used as a dedicated switch for an avoip network. if building a complex network, such as by combining an avoip network with an existing internal network, specify appropriate settings on the gui details settings page or by using commands. this page assumes that an ip address is assigned to vlan1. if vlan1 is not assigned an ip address, assign an ip address to vlan1 and access the web gui from a port associated to vlan1. the vlan1 ip address is already specified in factory default settings, so the setting does not need to be changed before use.</div><div class="display_word">2.1. Introduction This page can be used as a kitting tool for configuring optimal AVoIP network settings. QoS, multicast control, and other settings can all be set to optimal values at the same time by simply selecting a ProAV profile. The ProAV profile configured on this page assumes the unit will be used as a dedicated switch for an AVoIP network. If building a complex network, such as by combining an AVoIP network with an existing internal network, specify appropriate settings on the GUI Details settings page or by using commands. This page assumes that an IP address is assigned to VLAN1. If VLAN1 is not assigned an IP address, assign an IP address to VLAN1 and access the web GUI from a port associated to VLAN1. The VLAN1 IP address is already specified in factory default settings, so the setting does not need to be changed before use.</div></div><div id="gui_en_proav_profile"><div class="search_title" docfname="gui_en_proav_profile" doctitle="ProAV" link="#dante_profile">2.2. Set Dante profile</div><div class="search_word">2.2. set dante profile the dante optimization settings is applied. in a dante network, settings vary depending on the network structure.</div><div class="display_word">2.2. Set Dante profile The Dante optimization settings is applied. In a Dante network, settings vary depending on the network structure.</div></div><div id="gui_en_proav_profile"><div class="search_title" docfname="gui_en_proav_profile" doctitle="ProAV" link="#dante_primary">2.2.1. Use as Dante primaly dedecated line</div><div class="search_word">2.2.1. use as dante primaly dedecated line dante primary (vlan 1) select this network structure when the switch is used as a dante dedicated primary line and there is no need to partition the network with vlans. assign all ports to the same network as vlan1 and apply the dante primary profile. note that the only differences from selecting "use as dante secondary dedicated line "are the profile name and color settings. all other settings are the same.</div><div class="display_word">2.2.1. Use as Dante primaly dedecated line Dante primary (VLAN 1) Select this network structure when the switch is used as a Dante dedicated primary line and there is no need to partition the network with VLANs. Assign all ports to the same network as VLAN1 and apply the Dante primary profile. Note that the only differences from selecting "Use as Dante Secondary Dedicated Line "are the profile name and color settings. All other settings are the same.</div></div><div id="gui_en_proav_profile"><div class="search_title" docfname="gui_en_proav_profile" doctitle="ProAV" link="#dante_secondary">2.2.2. Use as Dante secondary dedecated line</div><div class="search_word">2.2.2. use as dante secondary dedecated line dante secondary (vlan 1) select this network structure when the switch is used as a dante dedicated secondary line and there is no need to partition the network with vlans. assign all ports to the same network as vlan1 and apply the dante secondary profile. note that the only differences from selecting "use as dante primary dedicated line "are the profile name and color settings. all other settings are the same.</div><div class="display_word">2.2.2. Use as Dante secondary dedecated line Dante secondary (VLAN 1) Select this network structure when the switch is used as a Dante dedicated secondary line and there is no need to partition the network with VLANs. Assign all ports to the same network as VLAN1 and apply the Dante secondary profile. Note that the only differences from selecting "Use as Dante Primary Dedicated Line "are the profile name and color settings. All other settings are the same.</div></div><div id="gui_en_proav_profile"><div class="search_title" docfname="gui_en_proav_profile" doctitle="ProAV" link="#dante_trunk">2.2.3. Bundle Dante primary/secondary lines</div><div class="search_word">2.2.3. bundle dante primary/secondary lines dante primary (vlan 1) dante secondary (vlan 2) trunk (all) select this network structure when the primary and secondary lines are bundled together for connecting a single lan cable between switches. assign the primary line to vlan1 and the secondary line to vlan2, and apply a dante profile to both vlans. the settings applied are the same for the primary (vlan1) and secondary (vlan2) lines. the trunk port sends and receives both dante primary and secondary traffic bundled together. designate the ports used to connect to other switches and the corresponding ports on the connected switches as trunk ports. the primary line (vlan1) is set as the native vlan (untagged) and the secondary line (vlan2) is set as the tagged vlan. as a precaution, when connecting the switch to another switch on a trunk, be sure to set the same profile-vlan assignment settings in both switches. to change the default primary, secondary, and trunk assignment settings, the horizontal and vertical buttons can be used to toggle between vertical and horizontal partition configurations in default settings. the horizon button does not appear on models with a single row of ports. primary, secondary, and trunk assignments can be changed manually by clicking on the profile selection button and then clicking on the port. since the gui cannot be accessed from the secondary ports (*), assign the primary profile or trunk status to the port used to connect the computer to the gui. * this page assumes that an ip address is assigned to vlan1.</div><div class="display_word">2.2.3. Bundle Dante primary/secondary lines Dante primary (VLAN 1) Dante secondary (VLAN 2) Trunk (ALL) Select this network structure when the primary and secondary lines are bundled together for connecting a single LAN cable between switches. Assign the primary line to VLAN1 and the secondary line to VLAN2, and apply a Dante profile to both VLANs. The settings applied are the same for the primary (VLAN1) and secondary (VLAN2) lines. The trunk port sends and receives both Dante primary and secondary traffic bundled together. Designate the ports used to connect to other switches and the corresponding ports on the connected switches as trunk ports. The primary line (VLAN1) is set as the native VLAN (untagged) and the secondary line (VLAN2) is set as the tagged VLAN. As a precaution, when connecting the switch to another switch on a trunk, be sure to set the same Profile-VLAN assignment settings in both switches. To change the default primary, secondary, and trunk assignment settings, the Horizontal and Vertical buttons can be used to toggle between vertical and horizontal partition configurations in default settings. The Horizon button does not appear on models with a single row of ports. Primary, secondary, and trunk assignments can be changed manually by clicking on the profile selection button and then clicking on the port. Since the GUI cannot be accessed from the secondary ports (*), assign the primary profile or trunk status to the port used to connect the computer to the GUI. * This page assumes that an IP address is assigned to VLAN1.</div></div><div id="gui_en_proav_profile"><div class="search_title" docfname="gui_en_proav_profile" doctitle="ProAV" link="#dante_redundant">2.2.4. Redundant Dante primary/secondary lines</div><div class="search_word">2.2.4. redundant dante primary/secondary lines dante ﾌﾟﾗｲﾏﾘｰ (vlan 1) dante ｾｶﾝﾀﾞﾘｰ (vlan 2) select this network structure when configuring redundant primary and secondary lines and using two lan cables to connect between switches. assign the primary line to vlan1 and the secondary line to vlan2, and apply a dante profile to both vlans. the settings applied are the same for the primary (vlan1) and secondary (vlan2) lines, but in this network configuration, an l2ms filter is applied to ports on the secondary line (vlan2) to prevent loops. note that l2ms agents connected only to a dante secondary port will not be detected by the lan map or yamaha lan monitor. to change the default primary and secondary assignment settings, the horizontal and vertical buttons can be used to toggle between vertical and horizontal partition configurations in default settings. the horizon button does not appear on models with a single row of ports. primary and secondary assignments can be changed manually by clicking on the profile selection button and then clicking on the port. since the gui cannot be accessed from the secondary ports (*), assign the primary profile to the port used to connect the computer to the gui. * this page assumes that an ip address is assigned to vlan1.</div><div class="display_word">2.2.4. Redundant Dante primary/secondary lines Dante プライマリー (VLAN 1) Dante セカンダリー (VLAN 2) Select this network structure when configuring redundant primary and secondary lines and using two LAN cables to connect between switches. Assign the primary line to VLAN1 and the secondary line to VLAN2, and apply a Dante profile to both VLANs. The settings applied are the same for the primary (VLAN1) and secondary (VLAN2) lines, but in this network configuration, an L2MS filter is applied to ports on the secondary line (VLAN2) to prevent loops. Note that L2MS agents connected only to a Dante secondary port will not be detected by the LAN map or Yamaha LAN Monitor. To change the default primary and secondary assignment settings, the Horizontal and Vertical buttons can be used to toggle between vertical and horizontal partition configurations in default settings. The Horizon button does not appear on models with a single row of ports. Primary and secondary assignments can be changed manually by clicking on the profile selection button and then clicking on the port. Since the GUI cannot be accessed from the secondary ports (*), assign the primary profile to the port used to connect the computer to the GUI. * This page assumes that an IP address is assigned to VLAN1.</div></div><div id="gui_en_proav_profile"><div class="search_title" docfname="gui_en_proav_profile" doctitle="ProAV" link="#ndi_profile">2.3. Set NDI profile</div><div class="search_word">2.3. set ndi profile the ndi optimization settings is applied. assign all ports to the same network as vlan1 and apply the ndi profile.</div><div class="display_word">2.3. Set NDI profile The NDI optimization settings is applied. Assign all ports to the same network as VLAN1 and apply the NDI profile.</div></div><div id="gui_en_proav_profile"><div class="search_title" docfname="gui_en_proav_profile" doctitle="ProAV" link="#multiple_profile">2.4. Set multiple ProAV profiles</div><div class="search_word">2.4. set multiple proav profiles multiple proav profiles can be applied by partitioning the network using vlans. with default settings, vlan1 is assigned to the dante primary line, vlan2 to the dante secondary line, and vlan3 to the ndi network. traffic for all selected profiles is sent/received via the specified trunk port. designate the ports used to connect to other switches and the corresponding ports on the connected switches as trunk ports. the vlan1 is set as the native vlan (untagged) and other vlans are set as the tagged vlan. as a precaution, when connecting the switch to another switch on a trunk, be sure to set the same profile-vlan assignment settings in both switches. the vlan assignment for a profile can be changed using the "change vlan "button. note that vlan1 must be assigned to one of the profiles. profile assignments to ports can be changed manually by clicking on the profile selection button and then clicking on the port. since the gui cannot be accessed from ports not affiliated with vlan1 (*), assign the vlan1 profile or trunk status to the port used to connect the computer to the gui. * this page assumes that an ip address is assigned to vlan1.</div><div class="display_word">2.4. Set multiple ProAV profiles Multiple ProAV profiles can be applied by partitioning the network using VLANs. With default settings, VLAN1 is assigned to the Dante primary line, VLAN2 to the Dante secondary line, and VLAN3 to the NDI network. Traffic for all selected profiles is sent/received via the specified trunk port. Designate the ports used to connect to other switches and the corresponding ports on the connected switches as trunk ports. The VLAN1 is set as the native VLAN (untagged) and other VLANs are set as the tagged VLAN. As a precaution, when connecting the switch to another switch on a trunk, be sure to set the same Profile-VLAN assignment settings in both switches. The VLAN assignment for a profile can be changed using the "Change VLAN "button. Note that VLAN1 must be assigned to one of the profiles. Profile assignments to ports can be changed manually by clicking on the profile selection button and then clicking on the port. Since the GUI cannot be accessed from ports not affiliated with VLAN1 (*), assign the VLAN1 profile or trunk status to the port used to connect the computer to the GUI. * This page assumes that an IP address is assigned to VLAN1.</div></div><div id="gui_en_proav_profile"><div class="search_title" docfname="gui_en_proav_profile" doctitle="ProAV" link="#trademark">3. Trademark attributions</div><div class="search_word">3. trademark attributions dante ™is a trademark of audinate pty ltd. ndi ®is a registered trademark of vizrt ndi ab.</div><div class="display_word">3. Trademark attributions Dante ™is a trademark of Audinate Pty Ltd. NDI ®is a registered trademark of Vizrt NDI AB.</div></div>