|
|
This chapter describes the configuration attributes available in basic mode for LightStream 2020 enterprise ATM switches (LS2020 switches) and offers advice on how to set them. Use this chapter as a reference when setting attributes during configuration.
The chapter is organized into sections according to the order in which you configure an LS2020 node: (1) chassis, (2) cards, (3) ports, (4) protocol attributes, (5) PVC end points, and (6) VLI attributes. Within each section, the attributes are arranged in alphabetical order.
The attribute fields accommodate fill-in or multiple choice values. Fill-in fields accept only printable ASCII text, and most accept a limited number of characters. The configurator provides a field box for any value that you have to fill in. The configurator provides either an option button or a radio button for any value that has multiple choice selections. To select a value for either type of button, you simply click on the correct setting.
You can set all the attributes described here using the configurator. The LS2020 switch uses a number of attributes that cannot be configured, and those are not listed here. For example, there are two card status attributes: cardAdminStatus, which is listed in this section, and cardOperStatus, which is not. The cardAdminStatus attribute specifies whether you want a card to be up or down. The cardOperStatus attribute, which is set by the system, indicates the actual status of the card.
Entries in this chapter list interrelationships among attributes, if any exist. Some attributes listed under the Interrelationships heading are given English names like Hello Time, and others are given MIB names such as ls1InfoOperRcvBaudRate. If the English name is provided, that means the referenced attribute is configurable, and you can look it up in this chapter. If the MIB name is provided, the attribute is not configurable through the GUI-based configurator and is not described in this chapter.
This section describes the attributes that you can set from the Chassis Configuration dialog box. These attributes are associated with the switch as a whole, and they include system attributes, IP addresses, and SNMP agent attributes.
Note Remember that, for ease of reference, the attributes are presented in alphabetical order—not in the order in which they appear in the dialog box.
Specifies the vendor's unique identification number for the system. If you do not know the chassis ID, you can use the configurator's Verify function or the show chassis general command in the CLI to display it.
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
Identifies the person responsible for this node and includes information on how to contact him/her. The field holds up to 29 characters.
Specifies the physical location of this node. (For example: telephone closet, 3rd floor.) The field holds up to 29 characters.
Specifies a name for the switch. The field holds up to 39 characters.
Alphanumeric characters (Do not use a name that begins with a number or that contains special characters such as dots, spaces, or quotation marks.) |
|
An IP address is a 32-bit identifier assigned to hosts that use the Internet Protocol. The address is represented by four octets (8-bit fields). In decimal form, an IP address comprises four fields separated by dots; each field contains a value in the range 0 - 255.
An IP address consists of two parts. The first part of the address, called the network number, identifies a network on the internet; the remainder, called the host ID, identifies an individual host on that network. All internal NP IP addresses within the same LS2020 network must have the same network number, and each must have a unique host ID.
Specifies the IP address of the default router for the Ethernet port on the LS2020 NP card. The router is used if the NP communicates with the network management system (NMS) through an Ethernet LAN but the NMS is not directly connected to the LAN. The router provides a route from the NP to the NMS.
The IP address for the default router has the network number for the attached Ethernet LAN (not the network number of the LS2020 network), followed by a host number that is assigned by the network administrator of the Ethernet LAN.
Specifies the IP address for the NP Ethernet port. An Ethernet LAN may be attached to the NP so that management traffic can be carried between the node and an NMS. If an Ethernet LAN is connected to the NP, the NP's Ethernet IP address must be configured. If there is a backup NP, both NPs must be attached to the same Ethernet segment, and the NP's Ethernet IP address is used by whichever NP is primary.
Note Be sure that the NP IP address differs from the primary and secondary addresses. Even the network ID number portion of the address should be different from the network numbers(s) used for the other two. When the software calculates the net ID of the NP IP address, it takes into account the NP IP mask. When it calculates the primary and secondary net IDs, it takes into account the subnet mask.
The NP Ethernet IP address has the network number for the attached Ethernet LAN (not the network number of the LS2020 network), followed by a host number that is assigned by the administrator of the Ethernet LAN.
Note Network management can also be done through a LAN that is connected to an ordinary Ethernet or FDDI edge port on any LS2020 node. The NMS must be directly attached to that LAN or connected to it through a bridged network. If you are using that type of configuration, do not configure any NP Ethernet port IP address or default router address.
Specifies the subnet mask for the NP Ethernet port's IP address. The subnet mask indicates which portion of the IP address is the network number and which portion is the host ID. This mask is the same for all nodes on the Ethernet LAN that is attached to the primary NP. You obtain it from the administrator of that Ethernet LAN.
The IP address of the active NP for the node. Nodes in an LS2020 network use their primary IP addresses to communicate network management traffic to one another. The address can also be used by any external system that has an IP connection to any port of the LS2020 network. If an LS2020 node has two NPs and the active NP fails, the backup becomes primary. The two NPs exchange management IP addresses so that the primary IP address remains with the active NP.
Note Be sure that the primary IP address you use differs from the secondary IP address. The two should, however, have the same network number. (They should be on the same IP network.)
Host IDs are assigned by the administrator of the network. The network number is assigned by the administrator of the internetwork. For a public network on the Internet, the network number is assigned by the Network Information Center (NIC).
Specifies the secondary IP address for the chassis. If a node has a backup NP, it uses its primary and secondary IP addresses to pass network management traffic between the two NPs within the node.
Note Be sure that the secondary IP address you use differs from the primary IP address. The two should, however, have the same network number. (They should be on the same network.)
The secondary IP address is used by the backup NP. All internal IP addresses in an LS2020 network must have the same network number, and each must have a unique host ID.
Specifies the subnet mask used for the IP addresses associated with switch ports (the primary and secondary IP addresses). The subnet mask specifies which portion of the IP address is the network number and which portion is the host ID. This mask is the same for all nodes on a given LS2020 network.
If you plan to handle just one physical LS2020 network under your network ID number (that is, if you do not plan to use subnetting) and the LS2020 network is a class C network, enter 255.255.255.0 as the subnet mask. (The mask is 255.255.0.0 for a class B network with no subnetting, and 255.0.0.0 for a class A network with no subnetting.)
Specifies the lowest priority of traps that are sent from the NP to the CLI and the NMS. Priorities from highest to lowest are operational, informational, trace, and debug. (The default value, Oper, works well in most cases.) See the LightStream 2020 Traps Reference Manual for more information on traps.
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
This parameter specifies the trap log control field. If enabled, the NP logs traps that it receives to the disk. As new traps are added, old traps are deleted. (The default value works well in most cases.)
The attributes listed here support the LS2020 network timing feature, Nettime. Nettime lets you specify a prioritized list of timing sources for each chassis in the LS2020 network.
Specifies, in decreasing order of desirability, up to ten timing sources for the node. The node uses the first available timing source listed in the Preference Table. Three timing sources can be listed:
An LS2020 node uses a given timing source until the source becomes unavailable or until a set nettime reset-level CLI command is issued, triggering a change of timing source. If the node reaches the end of the Preference Table without finding an available timing source, it uses the internal oscillator on the active switch card.
You may find it useful to enter the most desirable timing sources in the table more than once. One strategy, supposing the most desirable timing source is A, is to list sources in the pattern A, B, A, C, A, D, and so on. This causes the node to retry the best timing source after every failure to find a less desirable source, which increases the likelihood that the best source will be used.
Specifies the switch card that will provide the network timing signal for the node.
| MIB name | |
| Field type | |
| Legal values | |
| Default value | |
| Interrelationships |
This section describes attributes associated with function cards.
Note Remember that the attributes are presented in alphabetical order—not in the order in which they appear in the dialog box.
Specifies the desired status of the card. (See also "Port Status" later in this chapter.) The system makes the card's actual status match this value as soon as you do a Send Update operation for the node. Set this attribute to Up in the configuration database; you can change the status temporarily from the CLI.
| MIB name | |
| Field type | |
| Legal values | |
| Default value | |
| Interrelationships |
This parameter specifies the name for an NP or line card. The field holds up to 19 characters. You can leave this field blank if you wish.
Alphanumeric characters (Do not use a name that begins with a number or that contains special characters such as dots, spaces, or quotation marks.) |
|
Specifies the card category (for example, LS-Edge, T3-Trunk).
LS-Edge, LS-Trunk, SAC-Edge, SAC-Trunk, T3-Trunk, E3-Trunk, T3-Edge, E3-Edge, FDDI, Ethernet, Fiber Ethernet, OC3-Trunk, OC3-Edge, T1 CEMAC, E1 CEMAC, NP |
|
This section describes attributes associated with ports. Within this section, attributes are grouped as follows:
Note Configure port 0 on all cards, even if the port will not be used. The card type is derived from the setting for port 0. Configuring an unused port does not affect system operation.
Specifies the name of this port. The field holds up to 19 characters.
Specifies the intended status of the port. The system makes the port's actual status match this value as soon as it can. A port automatically enters testing mode when you load the diagnostics on its parent card. Set this attribute to Up in the database; you can use CLI to change the value for short periods as needed.
| MIB name | |
| Field type | |
| Legal values | |
| Default value | |
| Interrelationships |
The following subsections contain the definitions of all attributes associated with CEMAC, Ethernet, FDDI, and fiber Ethernet ports, which are provided by the PLC. Attributes are listed in alphabetical order.
Each T1 or E1 circuit emulation access card (CEMAC) provides eight constant bit rate interfaces to the LS2020 system at T1 or E1 rates.
Specifies the operational value for cable length used for this port.
After two successive failures to establish a connection from this port, this attribute controls the increase in the waiting period between subsequent retries. When a call set-up fails repeatedly, you can limit the strain on system resources by imposing successively longer waiting periods between retries. The system doubles the call setup retry period (CSRP) between successive call set-up attempts; this attribute specifies the maximum number of times to double the CSRP. When the maximum interval is reached, the system retries at that interval indefinitely. The initial CSRP is specified by the Call Setup Retry attribute.
Suppose, for example, that the CSRP is 5 seconds and the call set-up backoff value is 2. The first call set-up attempt fails. Waiting periods before subsequent attempts will be as follows:
Before 1st retry: 5 seconds (CSRP)
Before 2nd retry: 10 seconds (CSRP doubled)
Before 3rd and later retries: 20 seconds (CSRP doubled twice—the maximum)
| MIB name | |
| Field type | |
| Legal values | |
| Default value | |
| Interrelationships |
Specifies the call setup retry period (CSRP)—the waiting period, in seconds, between the first two attempts to establish a connection from this port. If the second attempt fails, the Call Setup Backoff attribute is invoked, causing subsequent waiting periods to double in length up to a specified maximum.
| MIB name | |
| Field type | |
| Legal values | |
| Default value | |
| Interrelationships |
Specifies the type of clock recovery used by the output processing hardware. To use the Nettime network timing feature, set Clocking Type to SRTS or Synchronous.
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
Specifies whether traffic on the link between the NMS and the LS2020 node is forwarded or blocked. This determines whether inbound frames received on this port are delivered to any NP in the network.
| MIB name | |
| Field type | |
| Legal values | |
| Default values |
Specifies whether traffic on the link between the NMS and the LS2020 node is forwarded or blocked. This determines whether inbound frames received on this port are delivered to any NP in the network.
| MIB name | |
| Field type | |
| Legal values | |
| Default values |
Note Port A and Port B attributes are displayed in one dialog box. The attribute descriptions are the same for each port.
Specifies the bit error rate estimate at which a link connection generates an alarm, expressed in negative powers of 10, for example, 8 means 10-8 (or .00000001%).
Specifies the bit error rate estimate at which a link connection is broken, expressed in negative powers of 10, for example, 7 means 10-7 (or .0000001%).
Specifies the length of the timer (in seconds) that is used in the FDDI SMT Neighbor Notification protocol.
Specifies whether traffic on the link between the NMS and the LS2020 node is forwarded or blocked. This determines whether inbound frames received on this port are delivered to any NP in the network.
| MIB name | |
| Field type | |
| Legal values | |
| Default values |
This subsection contains the definitions of all attributes associated with serial edge and trunk ports provided by the PLC-SAC module. These attributes are found in the SAC-Edge Frame Forwarding, SAC-Edge Frame Relay, and SAC-Trunk Port Configuration dialog boxes. Some attributes apply to only one type of port, and others apply to several. Attributes are listed in alphabetical order.
Specifies, in bits per second, the desired line rate for an edge or trunk port. This rate is in effect only when the interface's DCE/DTE Type is configured as DCE, as DCE-tt-loop (in the configurator), or as dce-internal (in the CLI) and the interface is, therefore, providing the clock signal.
The DCE Bit Rate that a port can support is dependent in part on the length of the data cable connected to the port and on the response time (clock-in to data-out) of the device at the other end of the cable. Due to physical constraints, data rates are generally slower in DCE-tt-loop (self clock) mode than they would be in a reflected clock mode (the DCE or DTE settings). If you encounter errors on a line whose DCE/DTE Type is set to DCE-tt-loop, try setting its DCE Bit Rate to a lower value or using a shorter cable. For detailed information on how to calculate DCE Bit Rate, see the appendix "Clocking on the Serial Access Card."
Note Each SAC port can sustain a maximum throughput of 6,144,000 bps. However, the aggregate throughput across all eight ports on the card will not exceed 24.576 Mbps (4 x 6,144,000 bps). If you configure aggregate bit rates in excess of this maximum, the system issues a warning.
Specifies the desired physical network interface type for a trunk or edge port. If the port is configured as a DCE, the LS2020 port provides the clock signal. If the port is configured as a DTE, the external device connected to the LS2020 port provides the clock signal. The DCE-tt-loop setting is used for connecting to DTEs that do not reflect clock (TT) signals. (The reflecting of clock signals is necessary for full V.35 compliance.)
DCE Bit Rate |
Specifies, in bits per second, the line rate for a trunk or edge port. This rate is in effect only if the port is configured as a DTE and is therefore receiving clock from an external device. If you specify an invalid value, the line card generates a trap.
The DTE Bit Rate that a port can support is dependent in part on the length of the data cable connected to the port. If you encounter errors on a serial line, try setting its DTE Bit Rate to a lower value or using a shorter cable. For more information, see the appendix "Clocking on the Serial Access Card."
Specifies, for frame relay edge ports, the number of status enquiry intervals that pass before the user portion of this frame relay interface (if it is configured as an NNI) issues a full status enquiry message. Local management interface (LMI) parameter reference: nN1/N391.
| MIB name | |
| Field type | |
| Legal values | |
| Default value | |
| Interrelationships |
Specifies, for frame relay edge ports, the data link connection management scheme, or local management interface (LMI), that is active on this frame relay port. "LMI FRIF" is the original LMI; it uses DLCI 1023 for LMI messages. "ITU-TSS Q.933A" was formerly known as CCITT Q.933A; it uses DLCI 0 for LMI messages. "ANSI T1.617D" also uses DLCI 0.
Specifies, for edge ports, the desired maximum frame size for this port, in bytes. (The default value of this attribute, 1536 bytes, is the maximum size of an encapsulated Ethernet frame.)
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
Specifies, for frame relay edge ports, the maximum number of virtual circuits allowed for this interface. This number is usually dictated by the frame relay network.
| MIB name | |
| Field type | |
| Legal values | |
| Default value | |
| Interrelationships |
Note The total of the Max Supported VCs values for all the ports on a card should not exceed the value of the per-card Max VCs attribute, which is limited to 2000. For information on the Max VCs attribute, see the section "Max VCs" in the "Expert Mode" appendix.
Specifies, for frame relay edge ports, the maximum number of unanswered status enquiries the system tolerates before declaring the LMI port unreliable at the network end. (If the LMI port is declared unreliable, all PVCs are reported inactive.) Status enquiries are counted over a number of polling intervals; the default number of such intervals is five. See the entry for "Net Monitored Events" later in this chapter for more information. LMI parameter reference: nN2/N392.
Specifies, for frame relay edge ports, the type of frame relay network interface on this port: UNI for user network interface, NNI for network-to-network interface.
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
Specifies, for frame relay edge ports, the number of status polling intervals over which the Net Error Threshold is counted. If this interface receives the number of errors specified in Net Error Threshold within this number of events, the LMI port is declared unreliable. (If the LMI port is declared unreliable, all PVCs are reported inactive.) LMI parameter reference: nN3/N393.
Specifies, for frame relay edge ports, the maximum number of seconds the system expects to elapse between status enquiry messages from the user end of the frame relay connection. If a status enquiry message does not arrive within this time, and if the system has been configured to report trace-level traps, trap number LCC_3036 is issued. LMI parameter reference: nT2/T392.
| MIB name | |
| Field type | |
| Legal values | |
| Default value | |
| Interrelationships |
Specifies, for frame relay edge ports, the number of seconds between consecutive status enquiries sent by the user portion of a frame relay interface that has an LMI. This attribute is used only when the LS2020 interface is configured as an NNI. LMI parameter reference: nT1/T391.
LMI Type |
Specifies, for frame relay edge ports, the maximum number of unanswered status enquiries the LS2020 system tolerates before it declares the LMI port unreliable at the user side of the interface. (If the LMI port is declared unreliable, all PVCs are reported inactive.) This attribute is used only when the LS2020 interface is configured as an NNI.
LMI Type |
This section contains the definitions of all attributes associated with (1) OC-3c ports provided by the CLC , (2) T3 ports on the 4- and 8-port T3 cards, and (3) E3 ports on the 4-port E3 cards. These attributes are found in the OC3-Trunk and OC3-Edge configuration dialog boxes and in the 4- and 8-port versions of the T3 trunk dialog boxes, and in the 4-port version of the E3 trunk dialog box. Attributes are listed in alphabetical order.
Specifies the length of the cable connected to this T3 or E3 trunk or edge port. If this attribute is set incorrectly, the connection may be noisy, or it may not come up.
After two successive failures to establish a connection from this port, this attribute controls the increase in the waiting period between subsequent retries. When a call set-up fails repeatedly, you can limit the strain on system resources by imposing successively longer waiting periods between retries. The system doubles the call setup retry period (CSRP) between successive call set-up attempts; this attribute specifies the maximum number of times to double the CSRP. When the maximum interval is reached, the system retries at that interval indefinitely. The initial CSRP is specified by the Call Setup Retry attribute.
Suppose, for example, that the CSRP is 5 seconds and the call set-up backoff value is 2. The first call set-up attempt fails. Waiting periods before subsequent attempts will be as follows:
Before 1st retry: 5 seconds (CSRP)
Before 2nd retry: 10 seconds (CSRP doubled)
Before 3rd and later retries: 20 seconds (CSRP doubled twice—the maximum)
| MIB name | |
| Field type | |
| Legal values | |
| Default value | |
| Interrelationships |
Specifies the call setup retry period (CSRP)—the waiting period, in seconds, between the first two attempts to establish a connection from this port. If the second attempt fails, the Call Setup Backoff attribute is invoked, causing subsequent waiting periods to double in length up to a specified maximum.
| MIB name | |
| Field type | |
| Legal values | |
| Default value | |
| Interrelationships |
Specifies whether cell payload scrambling is enabled for this trunk or edge port. Cell payload scrambling is a configurable option for T3/E3 cards, but it should always be enabled for OC-3c cards.
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
Specifies the source of the transmit clock used for this OC-3c, T3, or E3 trunk or edge port. If you specify external, recovered receive clock (clock derived from the receive data input) is used for the transmit clock. If you specify internal, a local timing source (such as an oscillator) on the switch card generates the transmit clock.
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
Specifies the type of DS3 line used on this T3 or E3 trunk port. If necessary, check with your carrier to learn the characteristics of the line it provides. (Clear channel is sometimes referred to as M13.)
Specifies the ATM framing and cell delineation combination in use on this port.
Specifies whether a SONET or an SDH signal is used across this interface (OC-3c only).
Specifies the identifier for the virtual path associated with this trunk card. Enter 0 if you want to disable VPI selection.
This subsection contains the definitions of all attributes associated with low-speed edge and trunk ports provided by the LSC. These attributes are found on the LS-Edge Frame Forwarding, LS-Edge Frame Relay, and LS-Trunk Port Configuration dialog boxes. Some attributes apply to only one type of port, and others apply to several. Attributes are listed in alphabetical order.
Specifies, in bits per second, the desired line rate for an edge or trunk port. This rate is in effect only when the interface is configured as DCE, DCE-tt-loop (in the configurator), or as dce-internal (in the CLI) and is, therefore, providing the clock signal.
The DCE Bit Rate that a port can support is dependent in part on the length of the data cable connected to the port and on the response time (clock-in to data-out) of the device at the other end of the cable. Due to physical constraints, data rates are generally slower in DCE-tt-loop (self clock) mode than they would be in a reflected clock mode (the DCE or DTE settings). If you encounter errors on a line whose DCE/DTE Type is set to DCE-tt-loop, try setting its DCE Bit Rate to a lower value or using a shorter cable.
Note Although the configurator accepts rates above 3,584,000 bps, sustained port throughput cannot exceed that rate.
Specifies the desired physical network interface type for a trunk or edge port. If the port is configured as a DCE, the LS2020 port provides the clock signal. If the port is configured as a DTE, the external device connected to the LS2020 port provides the clock signal. The DCE-tt-loop setting is used for connecting to DTEs that do not reflect clock (TT) signals. (The reflecting of clock signals is necessary for full V.35 compliance.) DCE-tt-loop is not recommended for use on trunk ports.
DCE Bit Rate |
Specifies, in bits per second, the line rate for a trunk or edge port. This rate is in effect only if the port is configured as a DTE and is therefore receiving clock from an external device. If you specify an invalid value, the line card generates a trap.
The DTE Bit Rate that a port can support is dependent in part on the length of the data cable connected to the port. If you encounter errors on a serial line, try setting its DTE Bit Rate to a lower value or using a shorter cable.
Specifies, for frame relay edge ports, the number of status enquiry intervals that pass before the user portion of this frame relay interface (if it is configured as an NNI) issues a full status enquiry message. Local management interface (LMI) parameter reference: nN1/N391.
| MIB name | |
| Field type | |
| Legal values | |
| Default value | |
| Interrelationships |
Specifies, for frame relay edge ports, the data link connection management scheme, or local management interface (LMI), that is active on this frame relay port. "LMI FRIF" is the original LMI; it uses DLCI 1023 for LMI messages. "ITU-TSS Q.933A" was formerly known as CCITT Q.933A; it uses DLCI 0 for LMI messages. "ANSI T1.617D" also uses DLCI 0.
Specifies, for edge ports, the desired maximum frame size for this port, in bytes. (The default value of this attribute, 1536 bytes, is the maximum size of an encapsulated Ethernet frame.)
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
Specifies, for frame relay edge ports, the maximum number of virtual circuits allowed for this interface. This number is usually dictated by the frame relay network.
| MIB name | |
| Field type | |
| Legal values | |
| Default value | |
| Interrelationships |
Note The total of the Max Supported VCs values for all the ports on a card should not exceed the value of the per-card Max VCs attribute, which is limited to 2000. For information on the Max VCs attribute, see the section "Max VCs" in the "Expert Mode" appendix.
Specifies, for frame relay edge ports, the maximum number of unanswered status enquiries the system tolerates before declaring the LMI port unreliable at the network end. (If the LMI port is declared unreliable, all PVCs are reported inactive.) Status enquiries are counted over a number of polling intervals; the default number of such intervals is five. See the entry for "Net Monitored Events" later in this chapter for more information. LMI parameter reference: nN2/N392.
Specifies, for frame relay edge ports, the type of frame relay network interface on this port: UNI for user network interface, NNI for network-to-network interface.
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
Specifies, for frame relay edge ports, the number of status polling intervals over which the Net Error Threshold is counted. If this interface receives the number of errors specified in Net Error Threshold within this number of events, the LMI port is declared unreliable. (If the LMI port is declared unreliable, all PVCs are reported inactive.) LMI parameter reference: nN3/N393.
Specifies, for frame relay edge ports, the maximum number of seconds the system expects to elapse between status enquiry messages from the user end of the frame relay connection. If a status enquiry message does not arrive within this time, and if the system has been configured to report trace-level traps, trap number LCC_3036 is issued. LMI parameter reference: nT2/T392.
| MIB name | |
| Field type | |
| Legal values | |
| Default value | |
| Interrelationships |
Specifies, for frame relay edge ports, the number of seconds between consecutive status enquiries sent by the user portion of a frame relay interface that has an LMI. This attribute is used only when the LS2020 interface is configured as an NNI. LMI parameter reference: nT1/T391.
LMI Type |
Specifies, for frame relay edge ports, the maximum number of unanswered status enquiries the LS2020 system tolerates before it declares the LMI port unreliable at the user side of the interface. (If the LMI port is declared unreliable, all PVCs are reported inactive.) This attribute is used only when the LS2020 interface is configured as an NNI.
LMI Type |
This subsection contains the definitions of all attributes associated with medium-speed edge and trunk ports provided by the MSC. These attributes are found in the configuration dialog boxes for the two-port T3-Trunk, two-port E3-Trunk, T3-Edge, and E3-Edge. Attributes are listed in alphabetical order.
Specifies the length of the cable connected to this T3 or E3 trunk or edge port. If this attribute is set incorrectly, the connection may be noisy, or it may not come up.
Turns cell payload scrambling on or off on this T3 or E3 trunk or edge port. Cell payload scrambling is a technique used for framing support. It rearranges the data portion of a cell to maintain the line synchronization.
Specifies the type of DS3 line used on this T3 trunk or edge port. Check with your carrier to learn the characteristics of the line it provides. (Clear channel is sometimes referred to as M13.)
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
This section describes attributes associated with internetworking. These attributes apply only to switches that use packet line cards (PLCs) in conjunction with FDDI, fiber Ethernet, and Ethernet access cards. The attributes are discussed in five main categories:
This section describes the attributes used to affect the operation and configuration of the LS2020 spanning tree bridge. These attributes are found in the Spanning Tree Configuration dialog box. Attributes are placed in one of two subsections, depending on whether they are system level or port level. Within a subsection, attributes are listed in alphabetical order.
You should be familiar with IEEE 802.1d-1990, MAC Bridges, before you attempt to set any of these attributes. Specifically, you should be familiar with the following terms: root bridge, designated port, spanning tree bridge, Hello Time, Forward Delay, Max Age, bridge priority, bridge ID, path cost, and port ID. Refer to RFC 1493, Definition of Managed Objects for Bridges, for more information on spanning tree bridge attributes.
Specifies the time period, in hundredths of a second, that all bridges use for Forward Delay when this bridge is acting as the root. Forward Delay is the time interval spent while the bridge is in transition between states.
Specifies the time period, in hundredths of a second, that all bridges use for Hello Time when this bridge is root. Hello Time is the time interval between the transmission of consecutive configuration messages sent by a bridge that is the root or is attempting to become the root.
Specifies the time period, in hundredths of a second, that all bridges use for Max Age when this bridge is acting as the root. Max Age is the maximum amount of time that received protocol information is saved before it is discarded. If this attribute is set too high, the network takes longer than necessary to adjust after a topology change. If this attribute is set too low, the spanning tree might occasionally reconfigure unnecessarily, which can cause temporary loss of connectivity in the network.
Specifies the value of the priority portion of the bridge ID (the first two octets of the eight-octet bridge ID). The other six octets of the ID are provided by a read-only MIB attribute: dot1dBaseBridgeAddress. The bridge Priority, along with the Port Priority and Path Cost attributes, is used to manage the spanning tree active topology. The lower the numerical value of the priority attribute, the higher its priority. The bridge with the lowest ID becomes the root bridge. If the priority portion of two IDs is the same, the bridge with the lower address portion of the ID becomes the root.
| MIB name | |
| Field type | |
| Legal values | |
| Default value | |
| Interrelationships |
Specifies the contribution of this port to the path cost of paths towards the spanning tree root that includes this port. The Path Cost, along with port Priority and bridge Priority attributes, is used to manage the spanning tree active topology. The higher the Path Cost value is, the less likely the port is to be chosen as part of the spanning tree.
Specifies the value of the priority field, which is contained in the first octet (in network byte order) of the two-octet port ID. The other octet of the ID is provided by a read-only MIB attribute: dot1dStpPort. The port Priority, along with Path Cost and bridge Priority attributes, is used to manage the spanning tree active topology. The lower the attribute value is, the higher its priority: a lower value makes the port more likely to be set by the protocol in forwarding state when the bridge has two or more ports connected in a loop.
| MIB name | |
| Field type | |
| Legal values | |
| Default value | |
| Interrelationships |
Specifies the status of the port as either enabled or disabled for bridged traffic.
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
This section describes the attributes used to create per-node custom filters. These attributes are found in the Define Filter and Assign Filter dialog boxes. Within a subsection, attributes are listed in alphabetical order.
You can create filters for bridge (based on the MAC layer header field), IP, and IPX traffic. Bridge filters are applied before IP and IPX filters. For that reason, you could have a situation in which a bridge forwards a packet but a subsequent IP or IPX filter blocks it.
Here are the rules that govern the creation and use of custom filters:
| Caution It is extremely important that the limit of 512 filters not be exceeded. |
The attributes associated with custom filters are specified in the LS2020 private MIB; they are not defined in any industry-standard MIBs.
You define a traffic filter by formulating a filter expression, made up of fields, constants, and operators. The fields are different for each of the three types of filter you can use with the node configurator program. Table 4-1 lists the fields you can use with the bridge filter. Table 4-2 lists the fields you can use with the IP filter, and Table 4-3 lists the fields you can use with the IPX filter.
Table 4-1 Fields Used with the Bridge Filter
| Field | Description | Format |
|---|---|---|
Points to remember when entering bridge filters:
To determine the MAC address of an NP for use in a filter, log in to the NP, start CLI, and enter this command:
Table 4-2 Fields Used with the IP Filter
| Field | Description | Format |
|---|---|---|
Dot-separated values in IP addresses are decimal digits without leading zeros. You can enter other constants as sequences of decimal digits (the default) or hex digits (with leading 0x).
Table 4-3 Fields Used with the IPX Filter
| Field | Description | Format |
|---|---|---|
Colon-separated values in IPX addresses ipxDstNd and ipxSrcNd are hex digits entered without a leading 0x, but with leading zeros for one-digit numbers (for example, 1 must be entered as 01). You can enter other values either as sequences of decimal digits (the default) or as hex digits (with leading 0x).
The configurator allows you to enter constants for use in constructing the filter expression. The format of the constant depends on the associated field (or masked field). Constants in defined filters can be entered in decimal or in hexadecimal. The constants default to base decimal. If you want to enter a hexadecimal value, you must use a prefix of 0x.
Use RFC 1340, Assigned Numbers, to determine the appropriate constant for your filter.
Specifies the expression associated with the filter. An expression is a complex condition applied to incoming frames.
The expression gives values for fields in an incoming frame header. If the contents of a field match the value for that field in a filter condition, an action that you select is performed on the frame.
The syntax of a filter expression is loosely modeled after the syntax of general programming languages, such as C. You create a filter expression by entering fields, operators, and constants and using parentheses. Each of these is described in more detail below.
Specifies the identifying integer assigned to this filter. Each filter ID on a chassis must be unique within a filter type.
The configurator provides the operators in the following list for construction of the filter expression.
| Operator | Description |
Note The following points pertain to these operators:
1. The left and right sides of a Boolean operation must evaluate as either true or false. The result of
applying operators in a Boolean expression is true or false.
2. The left side of a comparison operation must be either an arithmetic expression or a field. The
right side must be a constant. The result of applying operators in a comparison expression is true or
false.
3. The left side of an arithmetic operation must be a field (described above), and the right side must
be a constant (described below). The result of applying the operator in an arithmetic expression is a
numerical value to be used by a comparison operator.
Specifies the type of filter being defined.
Specifies the action to be taken if a frame meets the conditions defined by the filter. This is a filter-level attribute. You can specify that the frame be forwarded into the network or blocked. Blocking means that the frame is dropped at the edge. If you do not specify a setting for the filter-level Action attribute, the opposite of the setting for the port-level Default Action attribute is used.
lightStreamBrFilterParmAction |
|
Block if port Default Action = Forward |
|
Specifies the number of broadcast packets per second that this port accepts and attempts to forward. The node discards all broadcast packets above this number.
0 = All broadcast packets are discarded. |
|
Specifies the default action (either forward or block) to be taken for the port if there are no specific port filters or if there is no match with the configured filter(s) for the port. This is a port-level attribute.
Specifies a unique ID for the filter being assigned. (The filter has already been defined.) Each filter ID on a chassis must be unique.
Specifies the precedence assigned to this filter. The lower the priority number, the higher the filter's priority, compared with the priorities of the other filters assigned to the port. Filters are performed in order of priority, with the highest priority filter being performed first. Bridge filter conditions are applied before IP and IPX filter conditions. This means that if a bridge filter condition causes a packet to be forwarded, an IP or IPX filter can then block the packet.
Here are the rules for the assigning of priority:
Specifies the type of filter being assigned.
An expression is evaluated from left to right at both the top level of the expression and within a pair of parentheses. The result of a filter expression is either a Boolean true (if the received packet matches the expression) or a Boolean false (if the received packet does not match). Based on the Action attribute setting and on the default action for the port, the packet is then either blocked or forwarded.
You create a filter expression using the building blocks of fields, operators, constants and parentheses, which have been described above.
The following are some examples of filter syntax:
Example 1—Suppose that you want the network to allow only Local Area Transport (LAT) traffic to be passed between two LANs. You want to create a filter that blocks non-LAT traffic and forwards LAT traffic. You specify the filter this way:
6004 is the hexadecimal value assigned to the LAT protocol type in RFC 1340, Assigned Numbers.
You apply this filter to the ports that you want to use exclusively for LAT traffic with the Action attribute for the filter set to Forward. You also set the Default Action for the port to Block. This combination of settings causes only LAT frames to be forwarded and all others to be blocked.
Example 2—Consider the connections shown in Connections to Be Filtered. Suppose that you want to prohibit end stations xx:xx:xx:xx:xx:xx and yy:yy:yy:yy:yy:yy from communicating with each other. You create a filter for each port that blocks the traffic to the other end station.
You specify the filters this way:
You then assign each filter to the appropriate port and set the Action attribute for the filter to block. You set the Default Action for the port to Forward. This combination of settings prevents communication between the two end stations but allows all other communication.
Example 3—Using the same connections shown in Connections to Be Filtered, suppose that you wanted to allow communication only between end stations xx:xx:xx:xx:xx:xx and yy:yy:yy:yy:yy:yy. You create a filter for each port that allows communication between the two end stations. You specify the filter this way:
You then assign each filter to the appropriate port, but this time you set the Action attribute for the filter to Forward. You set the Default Action for the port to Block. This combination forwards traffic between the two end stations and blocks all other traffic.
This section describes the attributes used to create entries in the static bridge filtering database. These attributes are found in the Static Bridge Configuration dialog box. Attributes are listed here in alphabetical order.
The filtering database matches (1) a MAC destination address, (2) an LS2020 port that can receive the frames with this MAC destination address, and (3) a set of LS2020 ports on which the frames can then be transmitted. In the forwarding process, entries in the filtering database are used to determine if frames with a given MAC destination address should be forwarded to given port(s).
Through the configurator (or the CLI), you can explicitly make an entry in the filtering database; this is called a static bridge filter. You may, for instance, want to make such an entry if you are directing a broadcast to specific ports in order to limit broadcast propagation. You would also make this type of entry if you have an end station that only receives traffic, in which case the bridge cannot learn about the station.
Here are two rules regarding the creation of static bridge filter entries:
You should be familiar with IEEE 802.1d-1990, MAC Bridges, before you attempt to set any of these attributes. Specifically, you should be familiar with the following terms: filtering database, forwarding, MAC destination addresses, receive port, and transmit port. Refer to RFC 1493, Definition of Managed Objects for Bridges, for more information on static filtering attributes.
Specifies the destination MAC address to which this entry in the filtering database applies. The address can be a unicast, multicast, or broadcast address. You can obtain MAC addresses from the appropriate network administrators. To determine the MAC address of an NP for use in a filter, log in to the NP, start CLI, and enter this command:
Both FDDI and Ethernet MAC addresses must be entered in canonical form (least significant bit first). Colon-separated values in MAC addresses are hexadecimal digits entered without a leading 0x but with leading zeros for one-digit numbers (for example, 1 must be written as 01).
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
Specifies the number of an LS2020 interface that must receive the frame in order for this filtering database entry to apply. The interface number comprises the card slot number and the port number.
Specifies the interface numbers of the LS2020 ports that the frames with the associated MAC destination can be transmitted to. You can specify up to eight transmit ports. Transmit ports must be in the same chassis as the receive ports with which they are paired. However, the transmit ports need not be on the same card within the chassis as the receive ports.
HPMS, the High Performance Multicast Service, enables you to distribute LAN traffic from one source to multiple destination points. A multicast group is a list of ports on LS2020 nodes in the network. Once you define the group and assign it to a filter-port pair, LAN traffic intended for group members is delivered on an ATM point-to-multipoint VCC.
HPMS can be used to achieve higher packet flooding performance than the LS2020's general purpose flooding mechanism allows (70 to 100 packets per second, depending on node and network configuration). With adequate network capacity, the multicast feature can support flooding at up to LAN port rates. Any application that generates layer 2 or layer 3 LAN broadcast packets can benefit by using HPMS.
LS2020 group entries enable you to define multicast groups and add members to a group or delete members from a group. Each group member is a uniquely identified port in an LS2020 network. You can define up to 255 multicast groups per LS2020 node. Members of a multicast group can be anywhere in the network; they need not all be on the same LS2020 node.
A multicast group is associated with a port by means of a filter that is defined for that port. For that reason, it is more accurate to speak of the multicast group as being assigned to a filter-port pair. Traffic that matches the filter condition is sent to the port. Only one multicast group can be associated with any given filter on a port, and the action of the filter must be forward.
Note A multicast group should be consistently defined throughout the network. If a group is defined on one node, it should be defined analogously on all nodes in the network, regardless of whether it is used immediately on those nodes or not.
Specifies the name of the chassis where the multicast group is being defined.
1 - 39 characters or a positive integer of eight digits in the range 0 - 99,999,999 |
|
A multicast group consists of listed multicast group members. A member is a uniquely identified port in the LS2020 network.
Each member is defined by the name of the chassis where it belongs, followed by the card number and port number that specify this port. |
|
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
Specifies the multicast group ID assigned to this multicast group.
An Application-Specific Quality of Service (AS/QoS) traffic profile is a named set of attribute values assigned to a given port. Used in conjunction with a custom filter, a traffic profile allows you to control the type of service provided to a LAN flow—for example, you can dedicate bandwidth to the flow or give it higher priority. The profile, which is unique within the network, affects the following parameters for data transmitted from the port where the profile is assigned:
The traffic profile is assigned to a port by means of a filter associated with that port. For that reason, it is more accurate to speak of the traffic profile as being assigned to a filter-port pair.
The system supports a value named "default" for the Max. Rate parameter. The numeric value for "default" is -1.
The system enforces some restrictions on the parameters that make up a traffic profile. The restrictions are in two groups: for profiles that have a nondefault max rate and for profiles that have the default max rate. (See "Max. Rate" later in this chapter for more information on that parameter.)
Here are the restrictions for the nondefault max rate situation:
Here are the restrictions for the situation where the default max rate is being used:
An attempt to set up a traffic profile with an insured rate greater than the capacity of the entry edge port will fail. For example, the software refuses an attempt to set up a traffic profile for an Ethernet port if the profile has a specified insured rate of 50 Mbps.
Traffic profile bandwidth parameters enable you to better manage network bandwidth. One point to consider in this regard has to do with data allocation in ATM cells. Unless a series of LAN frames plus an 80 byte trailer total a value that is a multiple of 48, the last cell used to accommodate the data will be partially empty. For example, a 64-byte Ethernet frame will be segmented into two cells, with the second cell carrying only 16 data bytes.
You should consider this fragmentation loss caused by segmentation when you calculate the circuit bandwidth you need to achieve a given throughput. Consider the following example.
Suppose an application generates 64-byte Ethernet frames and you want to support a transmission rate of 10,000 packets per second. (A 10-Mbps Ethernet can support 14,880 64-byte packets per second.) The network bandwidth you need is calculated this way:
If there were no fragmentation loss, this would be the calculation:
The difference between 7.68 Mbps and 5.12 Mbps can be thought of as resulting from a cell packing factor (1.5 in this case).
When an LS2020 node sets up a circuit for carrying LAN traffic and no traffic profile is specified for the circuit, it uses default parameters, including a cell-packing factor of 1.2. If a traffic profile is used for the circuit, the profile gives the circuit parameters, including a cell-packing factor of 1.0.
Specifies the value in bits per second of the total bandwidth allotted an entity that is assigned this traffic profile.
If you use "default" as the setting for this object, the behavior of the traffic profile depends on how the profile is being used:
Specifies the ID that you assign to this traffic profile.
The attributes described in this section are used by LS2020 software to set up PVCs between two switches or between two ports on the same switch. These attributes are found in the PVC Configuration dialog box.
The two endpoint switches are called Node A and Node B in the configurator. You need to provide the same type of information for Node A and Node B. Node A attributes are for the PVC from Node A to Node B. Node B attributes are for the PVC from Node B to Node A. The configurator allows you to specify the attributes for both nodes at the same time. By supplying this information, you are provisioning for PVCs. (It is legal for Node A to be the same as Node B.)
The endpoint identification attributes (A Card, A Name, and A Port) in this section are named from the Chassis A end of the PVC. On the other end of the PVC (Chassis B), the endpoint attributes are reversed: on Chassis A the cktAdminDestNode and cktAdminDestIfIndex contain the values for the node at the other side of the PVC (Chassis B).
Specifies the LS2020 card at this end of the frame relay, frame forwarding, CEMAC, or ATM UNI virtual circuit.
Specifies, in bits per second (for FR and FF) or cells per second (for ATM UNI), the data throughput from node A to node B that the LS2020 network commits to support under normal network conditions.
Note The following points pertain to the legal and default values listed above:
1. The Insured Rate cannot be higher than the line rate.
2. The Insured Rate cannot be higher than the Max Rate.
3. If the Insured Rate is not 0, it cannot be lower than the minimum shown above.
4. If the Max Rate equals the Insured Rate, only insured traffic is configured for the PVC, and you
must set the Insured Burst equal to the Max Burst.
5. If the Max Rate is less than or equal to the line rate and the Insured Rate equals 0, the PVC is
configured to carry all uninsured (excess) traffic.
6. If the Insured Rate is greater than 0 and less than the Max Rate, the difference between the two
is the Excess Rate, which is used for uninsured traffic.
Specifies the maximum amount of insured plus uninsured data in bits per second (for FR and FF) or cells per second (for ATM UNI) that the LS2020 network will attempt to deliver from node A to node B under normal conditions. The uninsured portion of traffic can be discarded if the network is congested.
Note The following points pertain to the legal and default values listed above:
1. The Max Rate cannot be higher than the line rate.
2. If the Max Rate equals the Insured Rate, only insured traffic is configured for the PVC, and you
must set the Insured Burst equal to the Max Burst.
3. If the Max Rate is less than or equal to the line rate and the Insured Rate equals 0, the PVC is
configured to carry all uninsured (excess) traffic.
4. If the PVC is configured for any excess traffic, LS2020 software can allocate less than the Max
Rate if the link for the circuit does not have enough bandwidth available. LS2020 software can scale
back the Max Rate to be as low as the Insured Rate. (The CLI show port commands display actual
bandwidth allocation.)
Specifies the LS2020 node at this end of the frame relay, frame forwarding, or ATM UNI virtual circuit.
Specifies the LS2020 port at this end of the frame relay, frame forwarding, or ATM UNI virtual circuit.
Specifies the data link connection identifier (DLCI) of the LS2020 port at this end of the frame relay virtual circuit. The DLCI number identifies the VCC and enables you to distinguish one VCC from another. You are not required to use the same DLCI number at both ends of a connection. You can use the same DLCI number in many places in your network; however, all VCCs connecting to a given port must have different DLCI numbers at that port.
DLCIs identify frame relay VCCs. If you are provisioning for UNI VCCs, the configurator requires a VCI number. If you are provisioning for frame forwarding ports, no number is required.
If a port attaches to a device (such as a frame relay router) that also maintains DLCI numbers, the LS2020 DLCI for the corresponding PVC must be the same number. If you are not the system administrator for the attached router, you should obtain the numbers and associated endpoints from that person. Many routers can automatically learn DLCI numbers if you activate LMI on a port and the router is configured for the same type of LMI.
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
Specifies the virtual channel identifier (VCI) at this end of the ATM UNI VCC. The VCI number identifies the VCC and enables you to distinguish one VCC from another. You are not required to use the same VCI number at both ends of a connection. You can use the same VCI number in many places in your network; however, all VCCs connecting to a given port must have different VCI numbers at that port.
If a port attaches to another ATM device that also maintains VCI numbers, the LS2020 VCI for the corresponding PVC must be the same as the number on the other device. If you are not the system administrator for the attached ATM device, you should obtain the numbers and associated end points from that person.
Note VCIs are used to identify ATM UNI VCCs. If you are provisioning for frame relay VCCs, the configurator requires a DLCI number. If you are provisioning for a frame forwarding port, no number is required.
The endpoint identification attributes (B Card, B Name, and B Port) in this section are named from the Chassis B end of the PVC. On the other end of the PVC (Chassis A), the endpoint attributes are reversed: on Chassis B the cktAdminDestNode and cktAdminDestIfIndex contain the values for the node at the other side of the PVC (Chassis A).
Specifies the LS2020 card at this end of the frame relay, frame forwarding, or ATM UNI virtual circuit.
Specifies, in bits per second (for FR and FF) or cells per second (for ATM UNI), the data throughput from node B to Node A that the LS2020 network commits to support under normal network conditions.
Note The following points pertain to the legal and default values listed above:
1. The Insured Rate cannot be higher than the line rate.
2. The Insured Rate cannot be higher than the Max Rate.
3. Unless the Insured Rate is 0, it cannot be lower than the minimum listed above.
4. If the Max Rate equals the Insured Rate, only insured traffic is configured for the PVC, and you
must set the Insured Burst equal to the Max Burst.
5. If the Max Rate is less than or equal to the line rate and if the Insured Rate equals 0, the PVC is
configured to carry only uninsured (excess) traffic.
6. If the Insured Rate is greater than 0 and less than the Max Rate, the difference between the two
is the Excess Rate, which is used for uninsured traffic.
Specifies the maximum amount of insured plus uninsured data in bits per second (for FR and FF) or cells per second (for ATM UNI) that the LS2020 network will attempt to deliver under normal conditions, from node B to node A. The uninsured portion of this traffic may be discarded if the network is congested.
Note The following points pertain to the legal and default values listed above:
1. The Max Rate cannot be higher than the line rate.
2. If the Max Rate equals the Insured Rate, only insured traffic is configured for the PVC, and you
must set the Insured Burst equal to the Max Burst.
3. If the Max Rate is less than or equal to the line rate and the Insured Rate equals 0, the PVC is
configured to carry only uninsured (excess) traffic.
4. If the PVC is configured for any excess traffic, LS2020 software can allocate less than the Max
Rate if the link for the circuit does not have enough bandwidth available. LS2020 software can scale
back the Max Rate to be as low as the Insured Rate. (The CLI show port commands display actual
bandwidth allocation.)
Specifies the LS2020 node at this end of the frame relay, frame forwarding, CEMAC, or ATM UNI virtual circuit, using the node's name.
Specifies the LS2020 port at this end of the frame relay, frame forwarding, CEMAC, or ATM UNI virtual circuit.
Specifies the data link connection identifier (DLCI) of the LS2020 port at this end of the frame relay virtual circuit. The DLCI number is used to identify the VCC and to enable you to distinguish one VCC from another. You are not required to use the same DLCI number at both ends of a connection. You can use the same DLCI number in many places in your network; however, all VCCs connecting to a given port must have different DLCI numbers at that port.
DLCIs identify frame relay VCCs. If you are provisioning for UNI VCCs, the configurator requires a VCI number. If you are provisioning for frame forwarding ports, no number is required.
If a port attaches to a device (such as a frame relay router) that also maintains DLCI numbers, the LS2020 DLCI for the corresponding PVC must be the same as the number on the other device. If you are not the system administrator for the attached router, you should obtain the numbers and associated end points from that person. Many routers can automatically learn DLCI numbers if you activate LMI on that port and the router is configured for the same type of LMI.
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
Specifies the virtual channel identifier (VCI) at this end of the ATM UNI VCC. The VCI number is used to identify the VCC and to enable you to distinguish one VCC from another. You are not required to use the same VCI number at both ends of a connection. You can use the same VCI number in many places in your network; however, all VCCs connecting to a given port must have different VCI numbers at that port.
If a port attaches to another ATM device that also maintains VCI numbers, the LS2020 VCI for the corresponding PVC must be the same as the number on the other device. If you are not the system administrator for the attached ATM device, you should obtain the numbers and associated end points from that person.
Note VCIs are used to identify ATM UNI VCCs. If you are provisioning for frame relay VCCs, the configurator requires a DLCI number. If you are provisioning for a frame forwarding port, no number is required.
You use workgroups to perform automatic specialized filtering, based on MAC source and destination addresses. This feature allows you to specify which interfaces can communicate with each other.
The configuring of workgroups is optional. If you do not assign an interface to any workgroups, the interface automatically belongs to the Default workgroup (ID = 1).
The following attributes are used to create workgroups and to assign interfaces to those workgroups.
The card that contains the interface you are assigning to one or more workgroups.
The node that contains the interface you are assigning to one or more workgroups.
The port number of the interface you are assigning to one or more workgroups.
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
Determines if the interface is included in or excluded from the workgroup(s) in the list. (Read notes before changing this value.)
As a default, an interface is automatically included in the workgroup called Default that has an ID of 1. Therefore, by default, all interfaces are initially included in the same workgroup and can communicate with one another.
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
Note The following points pertain to the legal and default values listed above:
1. An interface can be included in up to seven workgroups or excluded from up to six workgroups.
2. An empty include list is treated as belonging to the Default group and therefore allows
communication with any other ports included in the Default workgroup.
3. An include list restricts communication between interfaces if the interfaces do not have at least
one common workgroup.
4. An empty exclude list allows communication with all ports.
5. An exclude list is the exception because it can stop an interface from communicating with only a
small number of workgroups (no more than six). Use the exclude list if you want to ensure that a port
will always be able to communicate with all (or almost all) of the workgroups. For instance, within
the LS2020 system, all NP management ports belong to an empty exclude list so that each node can
be managed from any physical port on the network. (The NP port's workgroup assignment cannot
be changed.)
The numerical identifier of the workgroup being assigned to the specified port.
| MIB name | |
| Field type | |
| Legal values | |
| Default value |
Note The following points pertain to the legal and default values listed above:
1. Workgroup IDs must be unique within the entire network.
2. The value 1 is assigned to the Default workgroup and cannot be changed.
3. The value 65535 is reserved and cannot be used.
The name of the workgroup being assigned to the specified port.
Posted: Thu Jan 23 11:20:54 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.