Part No. 215148-D March 2004 4655 Great America Parkway Santa Clara, CA 95054 Release Notes for BayStack Operating System Switching Software (BoSS) 3.
Copyright © 2004 Nortel Networks All rights reserved. March 2004. The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty. Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks Inc.
Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 New features for BoSS, software release 3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Hardware compatibility matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 GBIC compatibility matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Enabling traffic separation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Defaulting to BootP-when-needed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Configuring with NNCLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 ip bootp server command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 default ip bootp server command . . . .
Contents 5 autosave enable command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 no autosave enable command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 default autosave enable command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Downloading image without resetting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Configuring with NNCLI . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Replacing a unit in a stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Command Line Interface (CLI) commands for unit replacement . . . . . . . . . . . . . . 77 RADIUS fallback enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 RADIUS access challenge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Enhanced autotopology display . . . . . . . . . . . . . . .
Introduction These release notes document the new features and known issues of BayStack Operating System Switching Software (BoSS), software release 3.1. New features for BoSS, software release 3.1 These release notes contain information on the following new features for BoSS, software release 3.1: • • • • • • • • • • • • • • • • • • • • • • • “ASCII configuration generator” on page 24 “802.
• • • • • • • • “Enhanced autotopology display” on page 78 “Telnet client support” on page 81 “Display date of manufacture and HW deviation number in WEB/CLI/ Console” on page 80 “50 addresses for IPMGR” on page 80 “Restricted SSH access with IP Manager list” on page 81 “Trap notification when configuration changes saved to NVRAM” on page 82 “Displaying the default interface” on page 82 “User-based policies” on page 83 Hardware compatibility matrix BoSS for Policy Switches Software Version 3.
Table 2 Power cord options and option codes for BayStack switches (continued) Power cord option description Option Code North American power cord E Australia power cord F GBIC compatibility matrix Table 3 lists the Gigabit Interface Converters (GBICs) that are supported by the BoSS for Policy Switches Software Version 3.1.
BayStack 450 support BoSS Software Version 3.1 supports stacks that contain BayStack 450 switches. • • The BayStack 450 units must run BayStack 450 Software Version 4.4.0.6. The BayStack 450 units cannot be stacked with the BayStack 470-48T. Media Dependant Adapter (MDA) compatibility matrix Table 4 lists the MDAs that are supported in the BayStack BPS and the BayStack 460-24T-PWR running BoSS Software Version 3.1.
Software compatibility matrix BoSS Software Version 3.1 for Policy switches compatibility matrix The components for the BoSS Software Version 3.1 are: • • • • • • • BoSS Standard Runtime Image Software Version 3.1.0.78 (boss31078.img) BoSS Secure Runtime Image Software Version 3.1.0.79 (boss31079s.img) BoSS Boot/Diagnostic Software Version 3.0.0.5 (boss3005_diag.bin) Java Device Manager software version 5.7.6.0 (jdm_5760) BoSS Management Information Base (MIB) definition files (bossmibs_3.1.0.52.
• • • • • • • • • • • • 215148-D Device Manager and Web-based management do not include help information for the new 3.1 features. When in mixed stack mode, the user interface does not provide the ability to configure the BayStack 450 to filter unregistered frames. This feature is only available on the BayStack 450 when not stacked with the BayStack BPS, BayStack 470, and BayStack 460.
Trunk ----1 2 3 4 5 6 • • • • • • • Trunk Members ------------------------------[ /1 ][ / 2][ /3 ][ / ] [ [ 2/6 ][ 2/7 ][ / ][ / ] [ [ 3/10 ][ 4/11][ 4/12][ 5/13] [ [ / ][ / ][ / ][ / ] [ [ / ][ / ][ / ][ / ] [ [ / ][ / ][ / ][ / ] [ STP Learning Trunk Mode Trunk Status ------------ --------------- -----------Normal ] Basic [ Disabled ] Normal ] Basic [ Disabled ] Normal ] Basic [ Disabled ] Normal ] Basic [ Disabled ] Normal ] Basic [ Disabled ] Normal ] Basic [ Disabled ] Ensure you assign an
• Queue set 3 has eight queues. The first queue is serviced in an absolute priority fashion. The other seven queues are serviced in a WRR fashion. There are 3 sets of external ports that correspond to the queue sets. The first set of external ports contains the 10/100 Mb/s ports. These interfaces are associated with queue set 1. Each port in this set has a set of 4 queues.
• • Otherwise, if a BayStack 460-24T PWR switch is in the stack, it should be the base unit. Otherwise, the BPS 2000 should be the base unit. Note: The BayStack 470-48T switch cannot join a mixed stack (or one containing the BayStack 450 switch). For information on stacking the BayStack 460, 470 or BPS 2000 with the BayStack 470-48T switch, refer to "Allied stacking" on page 21. Note: The BayStack 450 switch can never be the base unit of a stack.
a Add the new unit to the stack leaving the original base unit unchanged. Do not change the base unit switches on the back. b Power up the stack so that the new unit can learn the IP configuration and stack information. Verify the configuration of the stack. c Turn off power to all units in the stack by unplugging the power cords from each unit. d Change the base unit selector switch on the new unit so that it is now base unit.
• If you initiate a management session with the device through the console port, you may see the following message in your system log. session opened from 127.0.0.1 127.0.0.1 is the loopback address and this message is appropriate since the connection was physically initiated from the console port on the device. (Q00826743) • • • The CLI command "show running-config" will display the configuration parameters that are appropriate for the user that is logged into the device.
• As part of your risk management protocol, please make sure you periodically backup your configuration file. Binary configuration files may be used in conjunction with the Unit Replacement Feature to increase network availability. (Q00593649), (Q00604762), (Q00518226) IGMP issues • • • IGMP reports may appear to be associated with several VLANs. This display issue does not affect IGMP functionality or performance. (Q00623137) When using BoSS 3.
Nortel Networks Command Line Interface (NNCLI) issues • • • The "show stack-info uptime" command does not display the uptime for BayStack 450 Switches. (Q00587447) If you enable port mirroring on a port that has STP enabled, when you disable port mirroring, you must manually re-enable STP support for that port. (Q00617551) You cannot change STP bridge priority, port priority, or path cost using the console interface. Use the NNCLI, web-based management, or Device Manager.
Spanning Tree Protocol (STP) issues • In a stack with a large number of units (e.g. 6 to 8), a large number of VLANs AND a large number of Spanning Tree Groups (STGs), STG configurations may fail to be propagated to the most distant units in the stack. This issue only affects non-default STGs (i.e. STG IDs not equal to 1). When this issue is being experienced, ports on a unit in the stack will fail to send out BPDUs for any affected non-default STGs.
• • • • • • • • • • • • If you add MAC addresses to Security Lists that do not have ports associated with them, and then display the Security Lists, the lists will appear empty until a port is associated with the list. (Q00622842) A mixed stack may reset twice after being booted or rebooted. This may cause a slight delay in booting the stack.
• • • • • • • • • • 215148-D Autotopology packets will not be transmitted on a link that is connected to a DMLT if the unit is reset. Autotopology packets will continue to be received from the units in the stack that were not reset. (Q00633687) If you enter an incorrect password while using RADIUS authentication to restrict management access to the device, the following error message appears: "no response from RADIUS servers".
• • • • Using the Web Interface, you may only change the EAPoL Re-Authentication Field for individual ports. As a workaround, you may use the Console Interface menu system, or the NNCLI. (Q00636903) Using the Web interface, you cannot configure flow control for BS450 in a mixed stack. Use the NNCLI or console interface. (Q00628278) When using SNMP V3, you may only assign a notify-view address to one user. You may not use the same target IP address for multiple users.
ASCII configuration generator The ASCII Configuration Generator (ACG) allows the configuration settings of the switch to be displayed or saved to an external ASCII configuration file made up of a series of CLI commands. This editable ASCII configuration file can then be uploaded to a switch from an external file server. Note: You must reset the switch to the factory default settings before uploading the ACG-generated ASCII configuration file.
show running-config command The show running-config command displays the current running configuration. The syntax for the show running-config command is: show running-config The show running-config command is in the privExec command mode. Note: The show running-config command is available, but its use is restricted, when a user has read-only access. The show running-config command has no parameters or variables. Figure 1 displays sample output from the show running-config command.
Note: The copy config command will copy a binary configuration file to the TFTP server. To store the configuration as an ASCII file, you must use the copy running-config command. The copy running-config command is in the privExec command mode. Table 5 describes the parameters and variables for the copy running-config command. Table 5 copy running-config command parameters and variables Parameters and variables Description address
The configure network command is in the PrivExec mode, Global configuration mode, and Interface configuration mode. Table 6 describes the parameters and variables for the configure network command. Table 6 configure network command parameters and variables Parameters and variables Description address Specifies the TFTP server IP address; enter in dotted-decimal notation. filename Enter the name of the ASCII configuration file you want to copy from the TFTP server.
Figure 3 configure network command output BS470#configure network address 134.177.118.56 filename config.txt Config File [|] BS470#enable Downloaded file successfully, executing . . . BS470#config t Enter configuration commands, one per line. End with CNTL/Z.
configure network load-on-boot command The configure network load-on-boot command is used to configure the switch to automatically download a configuration file when you reboot the switch. The syntax for the configure network load-on-boot command is: configure network load-on-boot {disable|use-bootp| use-config} [address ] filename The configure network load-on-boot command is in the PrivExec mode, Global configuration mode, and Interface configuration mode.
Figure 4 configure network load-on-boot command output BS470#configure network load-on-boot use-config address 134.177.118.56 filename config.txt BS470# 802.3ad Link Aggregation Link Aggregation (LA) allows you to create and manage a trunk group. You can control and configure a trunk group automatically through the use of the Link Aggregation Control Protocol (LACP). The LACP, defined by the IEEE 802.
The first four high priority links are active links and together they form a trunk group. The fifth low priority link remains in standby mode. When one of the active links goes down, the standby link becomes active and is added to the trunk group. LACP supports only one standby link. The failover process is as follows: • • The down link is removed from the trunk group The highest priority standby link is added to the trunk group.
To set port timeout: • • lacp timeout-time [port ] {short | long} default lacp timeout-time [port ] To set LACP system priority: • • lacp system-priority [0-65535] default lacp system-priority CLI Show commands for LACP: • • • • • • • • show show show show show show show lacp lacp aggr lacp port [] lacp port aggregator lacp debug member [portlist] lacp system lacp stats [port ] lacp stats aggregator clear-stats Enabling traffic separation Traffic separation
Defaulting to BootP-when-needed The BootP default value is now BootP-when-needed. This allows you to boot your switch and the system will automatically seek a BootP server for the IP address. Note: If an IP address is assigned to the device and the BootP process times out, the BootP mode remains the default mode of BootP-when-needed. However, if the device does not have an assigned IP address and the BootP process times out, the BootP mode automatically changes to BootP disabled.
Table 8 describes the parameters and variables for the ip bootp server command. Table 8 ip bootp server command parameters and variables Parameters and variables Description last|needed|disable| Specifies when to use BootP: always • always—Always use BootP • disable—never use BootP • last—use BootP or the last known address • needed—use BootP only when needed NOTE: The default value is to use BootP when needed.
default ip bootp server command The default ip bootp server command resets the mode to BootP when needed, which is the default mode. The syntax for the default ip bootp server command is: default ip bootp server The default ip bootp server command is in the config command mode. The default ip bootp server command has no parameters or values. Layer-2 restricted filters The Layer-2 restricted filters feature allows you to configure up to 23 metered policies. BoSS 3.
consumed for the out-of-profile action. Subsequent restricted Layer-2 metered policies will only use one filter for the in-profile-action and they will share the out-of-profile action defined by the first filter. Since only one filter is used for each policy, statistics will only count in-profile traffic. Restricted meters can only be used when the Interface Class Restriction is set to Unrestricted Only. Configuration To configure the BoSS Software Version 3.
IP/BootP configuration retention on downgrade When downgrading a unit with BoSS Software for Policy Switches version 3.0.3 and later, the system will default all configuration, except for the following: • • • Stack operation mode IP configuration BootP mode Previous releases of Policy Switch software retained the Stack Operational Mode only on software downgrade.
You configure this feature by enabling remote logging, specifying the IP address of the remote syslog server, and specifying the severity level of the messages you want sent to the remote server. Configuring with NNCLI You use the CLI to configure remote logging.
Table 9 show logging command parameters and variables Parameters and variables Description serious Displays serious log messages. sort-reverse Displays log messages in reverse chronological order (beginning with most recent). Figure 5 shows the output of the show logging config command.
no logging remote enable command The no logging remote enable command disables sending syslog messages to a remote server. The syntax for the no logging remote enable command is: no remote logging enable The no remote logging enable command is in the config command mode. The no remote logging enable command has no parameters or variables.
no logging remote address command The no logging remote address command clears the IP address of the remote server. The syntax for the no logging remote address command is: no logging remote address The no logging remote address command is in the config command mode. The no logging remote address command has no parameters or variables. logging remote level command The logging remote level command sets the severity level of the logs you send to the remote server.
no logging remote level command The no logging remote level command removes any severity level of the log messages that you send to the remote server; it reverts to None. The syntax for the no logging remote level command is: no logging remote level The no logging remote level command is in the config command mode. The no logging remote level command has no parameters or variables.
• • • SNTP sync events are logged on each sync attempt and pass/fail is indicated. Telnet session open, close, and timeout (Inactivity logout) events are logged. New event for the bsnConfigurationSavedToNvram trap. Generated when a config change written to NVRAM. Syslog enhancements for SSH The following event-triggered messages have been added to the system log to support SSH.
Stacking enhancement Faulty unit and cable detection When the operation mode is pure, the stack manager can detect the scenario whereby a unit appears good to its neighboring units (its up and downstream clocks are good) but the data packets it transmits or receives are corrupted or missing. In such a scenario, the stack falls apart and the ring check does not succeed.
Additional entries in volatile system log Table 12 Log Entry Multiple Base Units Detected, Check Base Unit Switch Explanation More than one unit has its "base unit switch" in the on position. Diagnostic Info Check to make sure only one unit has its "base unit switch" in the on position. Table 13 Log Entry Multiple Base Units Detected in UNP Phase Explanation More than one unit has its "base unit switch" selected or there is a contention in 2 units trying to be the base unit.
Table 16 Log Entry Incompatible interop value, module failed to join stack Explanation module type cannot interoperate with the base unit’s interop value. Diagnostic Info Replace module with another module type that is compatible with the base’s interop value. Table 17 Log Entry Incompatible operational mode, module inactive, module failed to join stack Explanation module has transitioned to inactive state.
Table 19 Explanation The unit did not receive any acknowledgment when it communicates with its downstream unit. Diagnostic Info First, determine whether you have a bad cable or bad downstream unit. If the cable connecting to the OUT stack port is bad, the stack port on both ends of the cable should be wrapped out and the units attached to the cable should still be in stack.
Table 22 215148-D Explanation Informational message declaring that a unit in the stack is booting up. Diagnostic Info This is an informational message. A unit was just inserted or rebooted in the stack. Make sure that you are not rebooting units unnecessary.
Additional entries in non-volatile system log Table 23 Log Entry Stack manager event JOIN STACK (module id = ) Explanation Informational message declaring that the module has joined the stack Diagnostic Info N/A Table 24 Log Entry Stack manager event LEAVE STACK (module id = ) Explanation Informational message declaring that the module has just left the stack. Diagnostic Info This may or may not be a failure depending on the circumstances.
Table 26 Explanation A switch soft reset has occurred when the global reset counter value is . The stack manager issue this soft reset the ring discovery algorithm was not successful after 2 attempts. Diagnostic Info Check to make sure that there is no bad cable or unit. Make sure that you are not resetting or disconnecting units while the ring discovery algorithm is being executed.
Displaying most recent log entry first This option allows you to view the system log with the most recent entry displayed first; the rest of the log entries are listed in reverse chronological order. Configuring with NNCLI You use the show logging command (with sort-reverse option) to sort the system log in reverse chronological order. show logging The show logging command displays the configuration and the current contents of the system event log.
Figure 6 show logging sort-reverse command output BS470_48#show logging sort-reverse Type Time Idx Src Message ---- ----------------------- ---- --- ------I 2003-10-27 20:52:00 GMT 59 Successful connection from IP address: 13 4.177.118.66, access mode: no security I 2003-10-27 20:48:51 GMT 58 Inactivity logout, IP address: 134.177.11 8.
Enabling and disabling autosave You can enable or disable the autosave feature of your unit. Autosave automatically saves your configuration information across reboots. When autosave is disabled, the logging messages sent to non-volatile memory are not saved. Note: You can use the CLI command copy config nvram to force a manual save of the configuration when autosave is disabled. You must use CLI to enable or disable autosave; the default value is enabled.
Figure 7 show autosave command output BS470_48#show autosave Auto Save: Enabled autosave enable command The autosave enable command enables the autosave feature. The syntax for the autosave enable command is: autosave enable The autosave enable command is in the config command mode. The autosave enable command has no parameters or variables. no autosave enable command The no autosave enable command disables the autosave feature.
Downloading image without resetting This feature allows you to upgrade the software without resetting the unit. Note: This feature is not available on the BayStack BPS or on a stack containing a BayStack BPS. Note: After using this feature, the Web interface will not be available until the switch or stack is rebooted. Configuring with NNCLI You use the download command to download the image without rebooting the switch using the CLI. The download command upgrades the software for the BoSS 3.1 version.
Table 31 describes the parameters and variables for the download command. Table 31 download command parameters and variables Parameters and variables Description address Specifies the TFTP server you want to use. Note: If this parameter is omitted, the system goes to the server specified by the tftp-server command. image Enter the name of the software image you want to download.
Using SNTP The Simple Network Time Protocol (SNTP) feature synchronizes the Universal Coordinated Time (UCT) to an accuracy within 1 second. This feature adheres to the IEEE RFC 2030 (MIB is the s5agent). With this feature, the system can obtain the time from any RFC 2030-compliant NTP/SNTP server. Note: If you have trouble using this feature, try various NTP servers. Some NTP servers may be overloaded or currently inoperable.
This section discusses the following topics, which enable you to complete these steps: • • • • • • • • • “show sntp command,” next “show sys-info command” on page 59 “sntp enable command” on page 60 “no sntp enable command” on page 61 “sntp server primary address command” on page 61 “sntp server secondary address command” on page 62 “no sntp server command” on page 62 “sntp sync-now command” on page 63 “sntp sync-interval command” on page 63 show sntp command The show sntp command displays the SNTP in
Figure 9 show sntp command output BS470_48#show sntp SNTP Status: Primary server address: Secondary server address: Sync interval: Last sync source: Primary server sync failures: Secondary server sync failures: Last sync time: Next sync time: Current time: Enabled 47.82.2.10 47.81.2.10 24 hours 47.82.2.10 0 0 2003-10-27 19:32:17 GMT 2003-10-28 19:32:17 GMT 2003-10-27 19:47:35 GMT show sys-info command The show sys-info command displays the current system characteristics.
Figure 10 show sys-info command output BS470_48#show sys-info Operation Mode: Switch MAC Address: 00-04-38-D5-86-40 Reset Count: 0 Last Reset Type: Power Cycle Power Status: Primary Power Autotopology: Enabled GBIC Port 47: None GBIC Port 48: None sysDescr: BayStack 470 - 48T HW:#0D FW:3.0.0.5 SW:v3.1.14 ISVN:2 sysObjectID: 1.3.6.1.4.1.45.3.46.
no sntp enable command The no sntp enable command disables SNTP. The syntax for the no sntp enable command is: no sntp enable The no sntp enable command is in the config command mode. The no sntp enable command has no parameters or variables. sntp server primary address command The sntp server primary address command specifies the IP addresses of the primary NTP server. The syntax for the sntp server primary address command is: sntp server primary address
sntp server secondary address command The sntp server secondary address command specifies the IP addresses of the secondary NTP server. The syntax for the sntp server secondary address command is: sntp server secondary address The sntp server secondary address command is in the config command mode. Table 33 describes the parameters and variables for the sntp server secondary address command.
Table 34 describes the parameters and variables for the no sntp server command. Table 34 no sntp server command parameters and variables Parameters and variables Description Enter the NTP server you want to clear: • primary—clears the IP address for the primary NTP server • secondary—clears the IP address for the secondary NTP server sntp sync-now command The sntp sync-now command forces a manual synchronization with the NTP server.
Table 35 describes the parameters and variables for the sntp sync-interval command. Table 35 sntp sync-interval command parameters and variables Parameters and variables <0-168> Description Enter the number of hours you want for periodic synchronization with the NTP server. NOTE: 0 is boot-time only, and 168 is once a week; the default value is 24 hours. Using DNS to ping and telnet Using the DNS client, you can ping or telnet to a host server or to a host by name.
• “Sample commands” on page 69 show ip dns command The show ip dns command displays the DNS domain name, as well as any configured DNS servers. The syntax for the show ip dns command is: show ip dns The show ip dns command is in the exec command mode. The show ip dns command has no parameters or variables. Figure 11 displays sample output from the show ip dns command. Figure 11 show ip dns command output BS470-48#show ip dns DNS Default Domain name: us.nortel.com DNS Servers - - - - - - 47.82.2.10 0.
The ping command is in the exec command mode. Table 36 describes the parameters and variables for the ping command. Table 36 ping command parameters and variables Parameters and variables Description Specify: • the IP address of the target device in dotted-decimal notation • the hostname of the device to ping (The hostname can be a simple name, such as fred; in this case the DNS domain name, if set, is appended. Or the hostname can be a full hostname, such as fred.ca.nortel.com.
ip name-server command The ip name-server command adds one or more DNS servers’ IP addresses. The syntax for the ip name-server command is: ip name-server The ip name-server command is in the config command mode. Note: You can add up to 3 servers; adding one at a time. Table 37 describes the parameters and variables for the ip name-server command. Table 37 ip name-server command parameters and variables Parameters and variables Description Enter the IP address of a DNS server.
Table 38 describes the parameters and variables for the no ip name-server command. Table 38 no ip name-server command parameters and variables Parameters and variables Description Enter the IP address of a DNS server. The default value is 0.0.0.0. ip domain-name command The ip domain-name command sets the system’s DNS domain name. The syntax for the ip domain-name command is: ip domain-name [] The ip domain-name command is in the config command mode.
no ip domain-name command The no ip domain-name command clears the system’s DNS domain name (sets it to an empty string). The syntax for the no ip domain-name command is: no ip domain-name The no ip domain-name command is in the config command mode. The no ip domain-name command has no parameters or variables. default ip domain-name command The default ip domain-name command clears the system’s DNS domain name (set it to an empty string).
Changing HTTP port number Beginning with software release 3.1, you can configure the HTTP port. This feature provides enhanced security and network access. The default HTTP port typically used to communicate between the Web client and the server is the well-known port 80. With this feature, you can change the HTTP port. You can modify the HTTP port while the switch is running. The HTTP port value is saved in NVRAM, and is saved across reboots of the switch.
Figure 13 show http-port command output BS470_48#show http-port HTTP Port: 80 http-port command The http-port command sets the port number for the HTTP port. The syntax for the http-port command is: http-port <1024-65535> The http-port command is in the config command mode. Table 40 describes the parameters and variables for the http-port command. Table 40 http-port command parameters and variables Parameters and variables Description <1024-65535> Enter the port number you want to be the HTTP port.
The default http-port command has no parameters or variables. Displaying MAC address table by port number You can now filter the MAC Address table by port number. You must use the NNCLI for this feature. show mac-address-table command The show mac-address-table command displays the current contents of the MAC address forwarding database table. The syntax for the show mac-address-table command is: show mac-address-table [vid <1-4094>] [aging-time] [address
Figure 14 show mac-address-table command output BS5510-24T#show mac-address-table Mac Address Table Aging Time: 300 Number of addresses: 22 MAC Address ----------------00-00-81-06-2B-A6 00-04-38-D5-86-40 00-08-74-CC-78-55 00-60-FD-EB-5D-95 00-E0-16-53-28-82 08-00-20-1F-E1-A2 08-00-20-8D-5B-D4 08-00-20-8E-E0-42 08-00-20-A2-48-62 08-00-20-B5-92-EA 08-00-20-C6-7A-6B 08-00-69-0F-3E-40 Source -------Port: 21 Port: Port: Port: Port: Port: Port: Port: Port: Port: Port: 21 21 21 21 21 21 21 21 21 21 MAC Addre
In certain situations, it is useful to be able to auto-negotiate a specific speed and duplex value. In these situations, the switch can allow for attachment at an operating mode other than its highest supported value. For example, if the switch only advertises a 100 Mbps full-duplex capability on a specific link, then the link only goes active if the neighboring device is also capable of auto-negotiating a 100 Mbps full-duplex capability.
Unit replacement Unit replacement allows you to upgrade a standalone unit with the configuration of the inactive unit off-line, before adding it to the stack. This is also called a staging operation. It also allows you to retrieve a single unit configuration from a stack's binary configuration file. The unit can then be inserted into the stack without requiring a reboot of the entire stack.
To replace a failed unit in a stack configuration, and preserve configuration information: 1 Ensure that you have uploaded the stack configuration file to the TFTP server using the management system before a unit fails. 2 Obtain the new BayStack switch you want to insert into the stack to replace the unit that failed. 3 Ensure that the new switch you will be inserting is set to factory default values. You will be configuring this new unit in standalone mode, before inserting it into the stack.
If you are replacing the base unit, remember that the stack will have a temporary base unit. When you replace the unit, the newly replaced unit will not automatically resume as the base unit. You must configure the replaced unit as the base unit, using either the rear-panel Unit Select switch or the front-panel UI button. You may reset the stack to reactivate the new base unit.
When RADIUS password fallback is enabled and the RADIUS server is somehow unavailable or unreachable, you can use the local switch or stack password to login into the switch or stack. When RADIUS password fallback is disabled, you need to specify the RADIUS username and password from the NetLogin screen and you will not be able to login to the switch or stack unless the RADIUS server is configured and reachable in order to authenticate the login and password.
show auto-topology nmm-table command The show autotopology nmm-table command displays the network management module (NMM) table. The Network Management Module table shows the slot number and port number of the remote device used to send out the topology packet. For BayStack stackable switches, the slot number refers to the unit number of the switch in the stack.
Table 42 show autotopology nmm-table command output fields (continued) Field Description MAC Addr MAC Address—The MAC address of the device. Chassis Type Chassis Type—A description of the type of device. BT Backplane Type—The backplane type of the device. BayStack devices always return a value of 12. LS Local Segment—Displays whether the device is on a local segment or not. Possible values are Yes or No. CS Current State—Possible values are NEW, HTBT (heartbeat), and TPCH (topology change).
To remove an IP from the IPMGR list: BPS2000(config)#no ipmgr source-ip ? <1-50> Select the address/mask pair Restricted SSH access with IP Manager list When telnet is enabled and use list is also enabled, the IP Manager list restricts SSH access. Telnet client support The telnet client allows you to telnet to a host or UNIX machine. One telnet client session at a time is supported.
The telnet command is in the exec command mode. Note: You use the telnet command in config mode to configure a telnet session to the switch, while you use the telnet command in exec command mode to establish a telnet session to a remote system. Table 43 describes the parameters and variables for the telnet command. Table 43 telnet command parameters and variables Parameters and variables Description Enter the IP address or the hostname of the device to connect to.
Default interface: Menu User-based policies This feature allows user-specific QoS policy information to be manipulated based on the presence, or lack thereof, of a specific network user. User information is retrieved from the RADIUS Server during EAP authentication and passed to the QoS Agent. The QoS Agent, in turn, notifies OPS of the user's presence if the policy server is currently in-charge of policy configuration.
default eapol user-based-policies enable command The default eapol user-based-policies enable command sets user-based-policies to the default setting. The default setting for user-based-policies is disabled. The syntax for the default eapol user-based-policies enable command is: default eapol user-based-policies enable show eapol The show eapol command shows whether user-based-policies are enabled or disabled.
How to get help If you purchased a service contract for your Nortel Networks product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller for assistance. If you purchased a Nortel Networks service program, contact Nortel Networks Technical Support. To obtain contact information online, go to the www.nortelnetworks.com/cgi-bin/comments/comments.cgi URL, then click on Technical Support.
215148-D
