|
|
This chapter describes how to use the web console, a GUI for changing the switch configuration and monitoring switch activity. This chapter includes instructions for the most common configuration tasks.
Before continuing with this chapter, you should have read the information in the "Overview of the Web Console" section.
To display the Basic System Configuration Page (Figure 4-1), click Home on the action bar. You can also display this page by entering the IP address or domain name server of the switch in the URL field, as described in the "Assigning IP Information to the Switch" section. This page acts as the home page for the switch web console.
Use this page to:
To operate the switch with its default settings, an IP address must first be assigned to the switch. The IP address is assigned from the [I] option on the Menu Console Logon Screen. The following information (used by network management applications to identify the switch on a network topology map) is also typically assigned but not required.
Step 1 Enter a name (up to 255 characters) to be used for the switch.
Step 2 Enter the location (up to 255 characters) of the switch.
Step 3 Enter the name (up to 255 characters) of the person responsible for the switch.
Step 4 Click Apply.
A switch password is optional. Follow these steps to enter a password:
Step 1 In the Assign/Change Password field, enter a character string (4 to 8 characters).
Step 2 In the Reconfirm Password field, reenter the same string.
Step 3 Click Apply.
If a password has already been defined, enter the password at the prompt when you first access the switch using the web console. The Basic System Configuration Page is redisplayed only after you enter the correct password.
If the Authorization Failed. Retry? message appears, check that you are using the correct password, and reenter it.
If you have forgotten the password, see the "Recovering from a Lost or Forgotten Password" section.
For information about changing the password, see the "Deleting and Changing the Password to the Switch" section.
This page has an image of the switch that reflects the activity of the LEDs on the switch front panel at the last poll interval. Generally, a green LED means proper functioning, and amber means a problem or malfunction. When an LED is off, the switch or a function is inactive. For information about using the LEDs and the Mode button to monitor the switch, see the "LEDs and Mode Button" section.
Click the Telnet hotlink to display the Menu Console Logon Screen.
If you need assistance from Cisco, the following resources are available:
To display the Port Management Page (Figure 4-2), click Port on the action bar, or click the port image on the Basic System Configuration Page. Use this page to:
Click Module Management to display and change the settings for the installed modules and module ports.
To enable or disable a port, select or deselect the check box in the Status column, and click Apply. The default is Enabled (check box is selected).
To confirm the action, click Home on the action bar to display the switch image. The port LED for a disabled port is amber.
The current state of each fixed port is shown in the grayed-out field in the Status column. Port status is a system-wide indicator of the state of a port. Security violations, management intervention, or actions of the Spanning-Tree Protocol can change the port status. Each port is always in one of the states listed in Table 4-1:
| Port Status | Definition |
|---|---|
Port can transmit and receive data. | |
Port is disabled by management action. The port must be manually reenabled. | |
Suspended due to the absence of a linkbeat. This is usually because the attached station is disconnected or powered-down. Port automatically returns to enabled state when the condition causing the suspension is removed. | |
Suspended because attached station is jabbering. Port automatically returns to enabled state when the condition causing the suspension is removed. | |
Suspended due to address violation. Port automatically returns to enabled state when the condition causing the suspension is removed. | |
Disabled because port failed self-test. Port must be manually enabled. | |
Disabled due to address violation. Port must be manually enabled. | |
Port is currently in the reset state. |
Select the duplex mode from the drop-down menu in the Duplex Mode column for the port, and click Apply. The default setting for the 10BaseT ports is half duplex.
Full-duplex operation is simultaneous transmission of data in both directions across a link. For example, 10BaseTX ports operating in full-duplex mode can provide up to 20 Mbps of bandwidth across the switched link. You can use full-duplex connections (either 10 Mbps or 100 Mbps) to enhance transmission speeds between other switches or routers that support full-duplex operation. A likely full-duplex scenario would be to connect a 100BaseT port to a server with a 100BaseT adapter configured for full-duplex operation.
To confirm your changes, follow these steps:
Step 1 Click Home on the action bar to display the image of the switch.
Step 2 Click the Mode button until the FDUP LED lights. If the port status LED is off, the port is running in half duplex. If the port status LED is green, the port is running in full duplex.
If you cannot confirm the actions you requested, return to the Port Management Page and make the changes again.
To enable flooding, select the unicast and multicast check boxes for the port, and click Apply. To disable flooding, deselect these check boxes for the port, and click Apply.
By default, the switch forwards to all ports (floods) unicast and multicast packets with unknown MAC addresses. As there are some configurations where this flooding is unnecessary, you can disable the flooding of unicast and multicast packets on a per-port basis. To control flooding, the switch forwards, floods, and filters packets in accordance with the IEEE 802.1d specification.
The switch forwards each packet according to the source address stored in the switch address table that matches the destination address of the packet. If the port a packet is received on has both the packet source and destination addresses on it, the packet is filtered (not forwarded).
If the switch cannot match a destination address of a packet with a source address in its address table, the switch floods the packet with the unknown destination address to all ports. Broadcast packets are always flooded to all ports.
For example, when the switch receives a unicast packet with a destination address that it has not learned, the default is to flood it to all ports. On ports with only statically assigned addresses or single stations attached, there are no unknown destinations and flooding would serve no purpose. In this case, you can disable flooding on a per-port basis.
In another example, when the switch receives a multicast packet, you can use the Address Table Management Page or SNMP to register multicast addresses and specify to which ports these packets are to be forwarded. You can also disable the normal flooding of unregistered multicast packets on a per-port basis. Besides reducing unnecessary traffic, these features open up the possibility of using multicast packets for dedicated groupcast applications such as broadcast video.
The switch also supports source-port filtering. This enhanced filtering capability only forwards packets to destinations when they are received on specified ports. These destinations are referred to as restricted static addresses. You can assign restricted static address from the Address Table Management Page.
To display the Detailed Port Statistics Page (Figure 4-3) report on a particular port, click Stats... for that port.
To display the Detailed Port Statistics Page (Figure 4-3), click Stats... from the Port Management Page or the Module Management Page. Use this page to display the receive and transmit port statistics and to help identify performance or connectivity problems, which are indicated under the Errors heading.
Table 4-2, Table 4-3, and Table 4-3 describe the error headings on the page.
| Error | Description |
|---|---|
FCS errors | Number of frames received on a particular interface that are an integral number of octets in length but do not pass the Frame Check Sequence (FCS) test. |
Alignment error | Number of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS test. |
Giant frames | Number of frames received on a particular interface that exceed the permitted frame size. |
Address violations | Number of times this secured port receives a source address that duplicates a static address configured on another port plus the number of times a source address was seen on this port that does not match any addresses secured for the port. |
Number of times the port detects a collision on a particular interface later than 512 bit-times into the transmission of a packet. | |
Excessive defaults | Number of frames the port defers transmission for an excessive period of time. |
Number of times the jabber function was invoked because a frame received from this port exceeded a certain time duration. |
| Error | Description |
|---|---|
FCS errors | Number of frames received on a particular interface that are an integral number of octets in length but do not pass the Frame Check Sequence (FCS) test. |
Invalid data length | Number of FDDI packets that have not been completely received. |
Error flag set | E indicator of the FDDI frame status is set. |
Bad IP header | Bad data in the IP header. |
Address violations | Number of times this secured port receives a source address that duplicates a static address configured on another port plus the number of times a source address was seen on this port that does not match any addresses secured for the port. |
| Error | Description |
|---|---|
CRC errors | Number of frames received on the ATM interface with AAL5 CRC error. |
Cell HEC errors | Number of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. |
Giant frames | Number of frames received on a particular interface exceeding the maximum frame size. |
Address violations | Number of times a port receives a source address that duplicates a static address configured on another port plus the number of times a source address was seen on this port that does not match any addresses secured for the port. |
To display the Address Table Management Page (see Figure 4-4), click Address on the action bar. Use this page to manage the address tables that the switch uses to forward traffic between ports. The address tables list the destination MAC address, the module number, and the port number. You can also specify how a port filters and forwards unmatched unicast addresses and nonregistered multicast addresses. Although multicast address registrations are configured elsewhere, you can use this menu to specify additional source-port filtering on the multicast addresses.
Flooding is the forwarding of unicast and multicast packets with unknown destination addresses to all ports. In certain applications, flooding might be unnecessary and undesirable. To control flooding, the switch forwards, floods, and filters packets in accordance with the IEEE 802.1d specification.
The switch forwards each packet according to the source address stored in the switch address table that matches the destination address of the packet. If the port a packet is received on has both the packet source and destination addresses on it, the packet is filtered (not forwarded).
If the switch cannot match a destination address of a packet with a source address in its address table, the switch floods the packet with the unknown destination address to all ports. Broadcast packets are always flooded to all ports.
For example, when the switch receives a unicast packet with a destination address that it has not learned, the default is to flood it to all ports. On ports with only statically assigned addresses or single stations attached, there are no unknown destinations and flooding would serve no purpose. In this case, you can disable flooding on a per-port basis.
In another example, when the switch receives a multicast packet, you can use the Address Table Management Page or SNMP to register multicast addresses and specify to which ports these packets are to be forwarded. You can also disable the normal flooding of unregistered multicast packets on a per-port basis. Besides reducing unnecessary traffic, these features open up the possibility of using multicast packets for dedicated groupcast applications such as broadcast video.
The switch also supports source-port filtering. This enhanced filtering capability only forwards packets to destinations when they are received on specified ports. These destinations are referred to as restricted static addresses. You can assign restricted static (permanent) addresses from the Address Table Management Page.
To define how long addresses that have not been seen should be retained by the switch, specify in the Aging Time field the number of seconds (10 to 1,000,000) after which an unused dynamic address is automatically removed from the list, and click Apply. The default is 300.
To delete an address from the Dynamic Address Table, select the address you want to delete, and click Remove.
You can manually enter addresses into the address table, including static addresses. Because static addresses do not age, you must manually remove them. Static addressing also allows for a measure of security in that access to a port can be restricted. See the "Port Security Table Page" section for more information.
To add an address to the table, select the port from the scroll list, specify the MAC address of that port in the MAC Address field, and click Add. The address is added immediately to the running (current) configuration and to NVRAM. To delete an address from the table, select the address you want to delete, and click Remove.
The Permanent Unicast Address Table contains addresses that an administrator has specifically assigned to certain ports. Unlike dynamic addresses, these addresses are not aged-out. When addressing security is enabled on a port, the permanent addresses statically assigned by an administrator (and possibly other addresses that are sticky-learned) determine which hosts can connect to a port. Sticky-learned addresses are learned and made permanent by the switch.
To register an address, select the port from the scroll list, enter the MAC address of that port in the MAC Address field, and click Register. To delete an address from the table, select the address you want to delete, and click Unregister.
The Permanent Multicast Address Table lists the registered multicast addresses that have been assigned to each port on the switch.
To display the Port Security Table Page (Figure 4-5), click Port Security Table from the Address Table Management Page. Use this page to enable port security on a port and to define the size of the address table for secured ports.
Limiting the number of devices that can connect to a secure port can have the following advantages:
The following fields validate port security or indicate security violations:
To enable port security on a port, select the check box in the Security column, and click Apply. The default is Disabled (check box is not selected).
On the following web console pages, you can specify the action the switch takes when packets with unauthorized addresses arrive on the port.
A secure port can have from 1 to 132 secure addresses associated with it. Setting the address table to have one address ensures the attached device has the full bandwidth of the port.
Enter a number from 1 to 132 in the Maximum Secure Addresses column, and click Apply.
Secured ports restrict the use of a port to a user-defined group of stations. When you assign static addresses to a secure port, the switch does not forward any packets with source addresses outside that group. If you define the address table of a secure port to contain only one address, the workstation or server attached to that port is guaranteed the full bandwidth of the port.
The number of devices on a secured port can range from 1 to 132. The addresses for the devices on a secure port are statically assigned by an administrator or sticky-learned. Sticky-learning takes place when the address table for a secured port does not contain a full complement of static addresses. The port sticky-learns the source address of incoming packets and automatically assigns them as static addresses.
Secured ports generate address-security violations under the following conditions:
When a security violation occurs, the port can be suspended or disabled. When a port is disabled, you must manually reenable the port. When a port is suspended, it is reenabled when a packet containing a valid address is received. You can also choose to ignore the violation and keep the port enabled. You can define the action taken by the switch either by using the System Management Page or by using the MIB objects.
To display the SNMP Management Page (see Figure 4-6), click SNMP on the action bar. Use this page to perform the following tasks:
You can use SNMP management, based on the Catalyst 2820 MIB, to specify management stations authorized to set configuration parameters and to receive traps. Up to four management stations can set MIB objects, and up to three stations can receive traps. If no management station is specified, any SNMP station can set parameters if the correct write community string accompanies the request. However, once a write-manager IP address is defined, only an explicitly specified management station can issue set operations. Once a management station has been assigned, it receives all traps issued by the switch.
Community strings serve as passwords for SNMP messages.
To define the SNMP agent read community string, enter up to 32 characters in the Read Community String field, and click Apply. The default is Public.
To define the write community string for the switch, enter up to 32 characters in the Write Community String field, and click Apply. The default is Private.
To enable or disable trap generation, use the following check boxes, and click Apply.
A trap manager community string can contain 32 characters. You can specify the IP address for the trap manager in dotted quad format (nnn.nnn.nnn.nnn). You can specify the name of the trap manager if the switch is connected to a domain name server.
Continue with further definitions for the second, third, and fourth traps, as needed.
For more information about traps, see the "Using FTP to Access the MIB Files" section.
Up to four IP addresses or host names of stations can issue write requests to the switch. Enter the IP address or host name of that station in the IP Address/Hostname field, and click Add. To delete a manager from the Write Manager scroll list, select the write manager, and click Remove.
To display the Spanning-Tree Management Page (Figure 4-7), click STP on the action bar. Use this page to change parameters for the Spanning-Tree Protocol (STP), an industry standard for avoiding loops in switched networks. The first part of the page displays the current spanning-tree operating parameter values received from the root bridge, spanning-tree settings for the current root switch, and the settings this switch is to use when it becomes the root switch. The second part of this page is used to define port-level parameters.
Spanning-Tree Protocol is enabled by default (check box is selected). To disable Spanning-Tree Protocol, deselect Enable Spanning Tree, and click Apply.
The following parameters are read-only and could be defined on another switch.
To change the spanning-tree parameters that this switch would use as the root switch, change the following parameters, and click Apply.
To change the spanning-tree parameters for a port, change the following parameters, and click Apply.
To display the CDP Management Page (see Figure 4-8), click CDP on the action bar. Use this page to enable CDP for the switch, set the global CDP parameters, and display information about neighboring devices.
Cisco Discovery Protocol (CDP) is a device-discovery protocol that the switch uses to maintain information about neighboring devices. Network-management applications that support CDP can then use this information to discover those devices. By gathering information about the types of devices in the network, the links between those devices, and the number of interfaces within each device, CDP enables network management applications to display a topological map of the network. Detailed information about the connections between devices is also available.
The CDP Neighbors list shows the devices with which this switch is exchanging CDP messages.
To Telnet to a neighbor, the neighbor must have Telnet support. Select the neighbor from the scroll list, and click Telnet.
To display detailed information about a neighbor, select it from the scroll list, and click Details....
In the Packet Hold Time field, specify the number of seconds (5 to 255) that the switch keeps the CDP neighbor information, and click Apply. The default is 180.
To enable CDP on one or more ports, select the port from the CDP Disabled scroll list, and click Enable.
To display the SPAN Configuration Page (Figure 4-9), click SPAN on the action bar. Use this page to do the following:
Frame capturing cannot take place until all three of these parameters have been set.
You can route a copy of incoming and outgoing port traffic to a monitor port for analysis and troubleshooting. When a port is selected as the monitor port, it sends out only traffic seen on the ports defined in the port capture list.
You can monitor traffic on a given port by forwarding incoming and outgoing traffic on the port to another port. Any port can be defined as the monitor port, and any combination of ports can be monitored.
To enable port monitoring, change the following parameters, and click Apply.
To enable frame capturing on the monitoring port, select the Capturing frames to the Monitor check box, and click Apply. The default is Disabled (check box is not selected).
Select the port to which captured frames are to be sent, and click Apply. The default is None.
To select ports to be monitored, select the port listed in the Ports Not Monitored scroll list, and click Add to move to the ports to the Ports Monitored scroll list.
To remove ports from the Ports Monitored scroll list, select the ports you want to remove from the Ports Monitored scroll list, and then click Remove.
To display the Console and Upgrade Configuration Page (Figure 4-10), click Console on the action bar. Use this page to set the console port parameters and to upgrade the switch firmware.
After connecting the console port of the switch to a management station or modem, set the following default characteristics of the console port to match the characteristics of the management station or modem, and click Apply.
Set the following parameters to define the call features, and click Apply:
The Switch Version field displays the firmware version currently used by the switch. You can download the latest switch firmware from a TFTP server or from a TFTP client.
To download the switch firmware from a TFTP server, follow these steps:
Step 1 Enter the IP address or name of the TFTP server in the Server: IP Address or Name of TFTP Server field.
Step 2 Enter the upgrade file name in the Filename for Firmware Upgrades field.
Step 3 Click System TFTP Upgrade to download the upgrade file from the TFTP server to the switch.
To download the switch firmware from a TFTP client, follow these steps:
Step 1 Select Accept Upgrade Transfer from Other Hosts.
Step 2 From the client management station, establish a TFTP session with the IP address of the switch. Make sure the client station is in binary transfer mode.
Step 3 Download the upgrade file from the client station to the switch, using the TFTP user interface or the appropriate command for the put operation (such as, put upgrade _ filename.
The Module Version field displays the Catalyst 2820 FDDI and ATM module firmware versions currently used by the switch. The firmware for the FDDI and ATM modules is different from the switch firmware. If your switch has an FDDI or ATM module, you can download the latest module firmware from a TFTP server or from a TFTP client.
To download the FDDI or ATM module firmware from a TFTP server, follow these steps:
Step 1 Enter the IP address or name of the TFTP server in the Server: IP Address or Name of TFTP Server field.
Step 2 Enter the upgrade file name in the Filename for Firmware Upgrades field.
Step 3 Depending on which expansion slot the module is in, click Module (slot A or B) TFTP Upgrade to download the upgrade file from the TFTP server to the module.
To download the FDDI or ATM module firmware from a TFTP client, follow these steps:
Step 1 Select Accept Upgrade Transfer from Other Hosts.
Step 2 From the client management station, establish a TFTP session with the IP address of the switch. Make sure the client station is in binary transfer mode.
Step 3 Download the upgrade file from the client station to the module, using the TFTP user interface or the appropriate command for the put operation (such as, put upgrade _ filename).
If there are two FDDI or two ATM modules installed, and you are downloading from a TFTP client, the following rules apply:
To display the Statistics Reports Page (Figure 4-11), click Statistics on the action bar. Use this page to reset the statistics of all ports and to display the summary exception and utilization statistics.
To reset statistics for a port, select the port from the Selected Port scroll list, and click Reset Port Statistics.
To reset the statistics for all ports, click Reset All Statistics.
This report displays the number of receive and transmit errors for each port.
This report displays the number of frames received, forwarded, and transmitted for each port.
To display the System Management Page (Figure 4-12), click System on the action bar. Use this page to define the switch system-wide parameters and configure broadcast storm control.
After you set the following IP parameters for the switch, click Apply:
To improve switch performance and set flood or traffic control, set the following parameters, and click Apply:
| Switching Mode | 10 Mbps to 10 Mbps | 10 Mbps to 100 Mbps | 100 Mbps to 100 Mbps | 100 Mbps to 10 Mbps |
|---|---|---|---|---|
FragmentFree (cut-through) | 70 microsec | - | 9 microsec | 10 microsec |
Store-and-forward1 | 7 microsec | 7 microsec | 3 microsec | 3 microsec |
| 1Although this table shows store-and-forward experiencing the lowest latency, the figures do not include the time it takes to receive the packet, which varies according to the packet size. |
If a password has been defined, and you want to delete it, click Clear Password.
If you want to change the password, click Clear Password. Then, from the Basic System Configuration Page (the Home page), follow these steps:
Step 1 Enter a character string (4 to 8 characters) in the Assign/Change Password field.
Step 2 Enter the same character string in the Reconfirm Password field, and click Apply.
To inhibit the forwarding of broadcast packets when an excessive number of them arrive from a given port, change the following settings, and click Apply:
To display the CGMP Management Page (Figure 4-13), click CGMP on the action bar. Use this page to enable Cisco Group Management Protocol (CGMP) and list the IP multicast addresses currently being handled by CGMP.
CGMP reduces the unnecessary flooding of IP multicast packets by limiting the transmission of these packets to only the CGMP clients that should receive them. CGMP manages multicast traffic by allowing directed switching of IP multicast traffic within a network. CGMP offers the following benefits:
CGMP filtering requires a network connection from the switch to a router running CGMP. When CGMP is enabled, it automatically identifies the ports to which the CGMP-capable router is attached. CGMP is enabled by default and supports a maximum of 64 IP multicast group registrations.
For information on IP multicast, including Internet Group Management Protocol (IGMP), refer to RFC 1112.
For additional information about CGMP and multicast addresses, see the "System Management Page" section and the "Address Table Management Page" section.
To enable CGMP, select the check box, and click Apply. The default is Enabled (check box is selected).
In the Router Hold Time field, specify the number of seconds (5 to 900) the switch waits before removing all IP multicast groups learned from CGMP, and click Apply. The default is 300.
The Router Hold Time field displays the number of seconds (between 5 and 900) the switch waits for keepalive messages before deleting CGMP-learned multicast groups. Multicast routers that support CGMP periodically send CGMP join messages to advertise themselves to switches within a network. A receiving switch saves the information and sets a timer equal to the router hold time. The timer is updated every time the switch receives a CGMP join message advertising itself. When the last CGMP-capable router goes down, the switch discards the multicast-group information from the router.
The IP Multicast Address Table lists the IP multicast addresses currently controlled by CGMP and the destination ports that will receive multicast traffic to this address.
To display the Module Management Page (Figure 4-14), click Module on the action bar. Use this page to set the parameters for the installed modules and module ports and display the statistics of the module ports.
To enable or disable a module, select or deselect Enabled in the Module Status field.
To enable or disable a module port, select or deselect Enabled in the Status column, and click Apply. The default is Enabled (check box is selected).
The current state of each fixed port is shown in the grayed-out field in the Status column. Port status is a system-wide indicator of the state of a port. Security violations, management intervention, or actions of the Spanning-Tree Protocol can change the port status. Each port is always in one of the states listed in Table 4-6
| Port Status | Definition |
|---|---|
Port can transmit and receive data. | |
Port is disabled by management action. The port must be manually reenabled. | |
Suspended due to the absence of a linkbeat, ring, or ATM network. This is usually because the attached station is disconnected or powered-down. Port automatically returns to enabled state when the condition causing the suspension is removed. | |
Suspended due to nontrunking ATM module. | |
Suspended because attached station is jabbering. Port automatically returns to enabled state when the condition causing the suspension is removed. | |
Suspended due to address violation. Port automatically returns to enabled state when the condition causing the suspension is removed. | |
Disabled because port failed self-test. Port must be manually enabled. | |
Disabled due to address violation. Port must be manually enabled. | |
Port is currently in the reset state. |
To change the settings of the installed modules and module ports, change the following parameters, and click Apply:
Select the port, and click Stats....
Click Basic FDDI Settings.
To display the Basic FDDI Settings Page (Figure 4-15), click Basic FDDI Settings on the Module Management Page. Use this page to display the most common FDDI settings.
Table 4-7 describes the MAC and SMT information fields on this page:
| Field | Description |
|---|---|
SMT version | Version number of this particular Station Management (SMT) implementation. |
MIB version | Version number of this FDDI MIB implementation. |
Number of MACs | Number of MACs that this FDDI entity implements. |
Non master ports | Number of ports on the FDDI module. Non-master ports are any ports other than the M type. |
ECM state | Current status of the ECM (entity coordination management) state machine. The ECM handles the management and coordination of all of the ports in the node. During normal operation, this has the value In. The other possible values, Out, Trace, Leave, Path_test, Insert, Check, or Deinsert, can indicate that the ECM state machine has detected an error. |
Upstream neighbor | Station address of the upstream neighbor. |
Station address | Station address of the FDDI module. |
Downstream neighbor | Station address of the downstream neighbor. |
Optical bypass | If an optical bypass device is attached to the FDDI module, this item is Present; otherwise it is Not Present. |
Attachment state | Current attachment configuration for the module. The normal state, Thru, indicates that both ports are connected to the ring. The value Isolated indicates that both expansion ports A and B are disconnected from the ring, Wrap_A indicates that only expansion port A is connected to the ring, and Wrap_B indicates that only port B is connected to the ring. |
Table 4-7 describes the port information fields on this page:
| Field | Description |
|---|---|
Connection policy | Types of connections that are not allowed for a port. For example, if port types A and S are listed under expansion port A, then port A of the FDDI module cannot be connected to an A port or an S port on another station. |
Neighbor type | Port type to which each port is currently attached. Possible values are A, B, S, M, and NONE. |
Connection policy (rejects) | Path into which each port is currently inserted. The value will be Primary, Secondary, or Isolated. |
Available paths | Possible paths into which each port can theoretically be inserted. This value will always be Primary+Secondary; for FDDI SAS, the value will be Primary. |
PMD class | Class of the PMD (physical layer media dependent). The value is multimode or twisted-pair. |
PCM state | Current state of the PCM (physical connection management) state machine. The PCM covers the management of the physical connection between the port and the connected port on the adjacent node. The possible values are Off, Break, Trace, Connect, Next, Signal, Join, Verify, Active, and Maint. |
Link error alarm activated | If this value sets to True, the link error rate for the port has exceeded the alarm threshold. |
Link confidence test failures | Count of the number of consecutive times the link confidence test has failed. |
Link error monitor rejections | Link-error monitoring count of the number of times that a link has been rejected. |
Aggregate link error count | Aggregate count of link-error monitoring errors. This count is reset only at initialization. |
|
|