Table Of Contents
Managing Devices
Introduction
Launching CiscoView
Navigating CiscoView
Selecting a Node
Selecting a Device
Selecting the Node as a Device
Selecting a Card
Selecting a Line or Port
Selecting Categories
Displaying and Modifying Objects
Preparing a Device for a Connection
Example 1, Preparing for an ATM Connection
Configuring the SONET Line
Configuring APS
Configuring Card Redundancy
Configuring a SONET Port
Example 2, Preparing for a Frame Relay Connection
Configuring FRSM Line Categories
Configuring an FRSM Port
Configuring an FRSM Channel
Configuring Logical Ports
Example 3, Preparing for a Circuit Emulation Connection
Configuring a CESM Physical Line
Configuring Dsx 1 Objects
Configuring dsx 3 Objects
Configuring a CESM Port
Configuring a CESM Channel
Configuring CESM Card Redundancy
Create Redundancy
Managing Devices
This chapter describes the Device Management facilities provided within Cisco WAN Manager (CWM)
Contents of this chapter include:
•
Introduction
•Launching CiscoView
•Navigating CiscoView
•Preparing a Device for a Connection
Introduction
The network management functions of CWM can be broadly divided into two main categories.
•Device management — The management of the network nodes and their components.
•Connection management — The management of the connections between the nodes.
Whereas connection management is provided within the main CWM program, device management is provided by a CWM application known as CiscoView.
CiscoView is a web based program and is launched within a CWM server or a CWM client. CiscoView provides the user with access to the numerous managed device objects (configuration settings, interface status, counter values, and so on.) in a Cisco network.
Through its graphical user interface, CiscoView provides accurate pictorial representations of nodes and their cards. These representations combined with a set of point-and-click menus combine to permit the user to manage the device objects. The values of all the object can be displayed and many, but not all, can be modified. In this way, CiscoView permits users to perform tasks such as supporting connections, displaying statistics, and setting up controllers and partitions.
Launching CiscoView
CiscoView is launched from within CWM using the following procedure.
Step 1 Make sure that CWM is running, including the desktop GUI on either a server or client machine.
Step 2 Choose Apps > CiscoView from the Network Topology window of CWM.
The web browser launches CiscoView. The opening CiscoView screen appears in Figure 3-1.
Figure 3-1 CiscoView Opening Screen
When the screen opens, the user can select several administrative tools using the menu on the left side for details.
Step 3 To manage a device, specify the device by entering its node name or IP address in the Select Device field in the top left corner.
Step 4 Press Enter.
Navigating CiscoView
The process of displaying and manipulating device objects is a sequence of successive selections either from a pictorial representation of a device or from a set of object categories in a menu. The process consists of the following steps.
Step 1 Select the network node for the objects that are to be managed.
Step 2 Select a device on the node.
The device can be the node itself, a card in the node, or a physical port (interface) on a card.
Step 3 Select an object category from the menu displayed by the selected device. This action either displays the objects within the category or displays a list of sub-categories (in which case the user makes a further selection). The user may need to select from a sequence of sub-categories before the objects themselves are displayed.
Step 4 When all the appropriate selections have been made, the list of object names and values are displayed and, if permitted, can be modified by the user.
The steps listed above are now described in more detail.
Selecting a Node
As described in the "Introduction", the user performs device management tasks by displaying and modifying objects for a particular device.
Step 1 Specify a node. This is always the first step. The node is specified by the user by entering the nodename or the node's IP address in the Select Device field in the top lefthand corner of the CiscoView opening screen (see Figure 3-1).
Note If a message is displayed about wanting to close the window, select Yes.
If a Plug-in Security message is displayed, select "Grant this Session".
Step 2 When the community string dialog box is displayed, enter the read and write community strings for the node or accept the defaults.
The selected node is displayed on the screen as shown in Figure 3-2. This display may take a few minutes while the system collects data from the selected node. The current activity and a progress bar are displayed while the image is being processed.
Figure 3-2 shows the front view of a Cisco MGX 8850 that has the nodename of M8850_LA.
Figure 3-2 Front View of Node
The purpose of the node's representation is to allow the user to specify an item in the node. Notice that the node's front view is always displayed first. In some cases, the item to be selected can only be seen from the rear of the node. The node's rear view can be displayed as follows:
Step 3 Right- click the dark title portion of the node at the top, above the cards,.
Step 4 Select Rear in the resulting menu.
The rear of the node is displayed as shown in Figure 3-3.
Figure 3-3 Rear View of the Node
Selecting a Device
When the selected node is displayed, the user must select which device (component) of the node is to be managed. The user can select the node itself, a card in the node, or a port.
Selecting the Node as a Device
The user selects the node itself if the objects to be managed pertain to the node as a whole. Examples of these objects are
•allocation of cards to slots in the node
•shelf's serial number
•configuration details of the virtual switch and PNNI controllers
•serial port configuration
A node is selected using the following steps.
Step 1 Right click the dark area of the node above the cards.
This action displays the menu as shown in Figure 3-4.
Figure 3-4 Node Menu
Step 2 Click Configure, this action displays the node categories (described later).
Notice that this menu is the same menu that is used to switch between the front and rear views of the node.
Selecting a Card
The user selects a card when the objects to be managed are associated with a particular card. Examples of these objects are
•SONET interface settings
•Interface partition settings
•Revision numbers of hardware, software, and firmware installed in the card
•Lines, interfaces and ports on the card
A card is selected using the following steps.
Step 1 Right-click in the body of the card to display a popup menu.
Step 2 Click Configure. This action displays the card categories (these categories are described later).
Selecting a Line or Port
The user selects a port when the objects to be managed are associated with a particular port, line, or interface. Examples of these objects are:
•ATM port settings
•ATM virtual port settings
•Ingress cell counters
A port is selected using the following steps:
Step 1 Right- click on a connector (the front view for front card objects, the rear view for back card objects) to display the popup menu.
Step 2 Choose Configure.
Selecting Categories
When the device (node, card, or port) is selected and the Configure item in the menu is clicked, a category screen is displayed.
An example screen for a Cisco MGX 8850 node is shown in Figure 3-5
Figure 3-5 Top Level Categories for a Cisco MGX 8850
The screen allows the user to display and select the device's top level categories. Click the Category drop-down arrow to display a list of the top level categories.
By selecting a top level category, a list of sub-categories for that top level category is then displayed. Figure 3-5 shows that the top level category for the Node has been selected and the sub-categories associated with the Node are listed.
Notice that there is a Node sub-category called PNNI Controller Configuration. By choosing this sub-category, a further sub-category is displayed as shown in Figure 3-6.
Figure 3-6 PNNI Configuration
Using this process, the user chooses a sequence of sub-categories until the objects to be managed are displayed. As an example, the Wan Atm Port Configuration objects are shown in Figure 3-7.
Figure 3-7 Dialog Box Displaying WAN ATM Port Configuration Objects
Displaying and Modifying Objects
As the user chooses successive categories, eventually a dialog box is displayed that shows the actual names and values of the objects in the lowest level sub-category. The format used for displaying object values depends upon whether there can be multiple instances of the objects or not.
When there is multiple instances of the objects. object values are displayed as a row in a table with each column representing the value of one of the objects. Multiple instances of objects, are displayed in a separate row. If the sub-category contained eight objects and twelve instances of the objects the table would consist of eight columns and twelve rows.
If the number of columns or rows is too large for the complete table to be displayed in the dialog box, scroll bars are provided to allow the user to scroll horizontally and vertically.
Using Figure 3-7 as an example, the sub-category named Wan Atm Port Configuration contains the objects of cwsAdminStatus, ifIndexProp, cwsOperStatus, cwsSvcBlocked, and so on. There are several instances of these objects, one for each row of the table.
When there is only one instance of the objects, the object values are shown in a list. Figure 3-8 shows an example a list. In this example the objects are those in the ATM Cell Layer Config category for a SONET line.
Figure 3-8 Example of Values for a Single Instance Object
Some object values are configurable by the user and some are for display only. The rules are
•If an object value is displayed with a white background, the user can enter a new value. Use the mouse, cursor, and keyboard to change the value on the screen.
•If the object value has a gray background and a down arrow to the right of the field, the user can choose a new value by clicking on the drop-down arrow and selecting a value from the popup menu.
•If the object value has a gray background and no down arrow, the object is for display only and cannot be changed by the user.
In Figure 3-7 the user can enter new values for the cwspAdminStatus and cwspSvcBlocked object but cannot change the ifIndesProp and cwspOperStatus objects.
In Figure 3-8 the user can enter new values for Null Cell Header and Null Cell Payload objects, and select new values from a popup menu for HEC Coset Enable and Payload Scrambling objects. The user cannot change the Port Number and Status objects.
To modify a configurable value use the following procedure.
Step 1 If necessary, use the slides to display the first object value to be changed.
Step 2 Check that the object to be changed is configurable.
Step 3 Change the value either by entering new data or using the popup menu (as appropriate).
Note When any value is changed, the Apply button changes from gray to black.
In some cases the user may want to create a new instance of a particular set of objects. When this action is permitted, the display contains a Create button (see Figure 3-7). By clicking the Create button, the user can specify another object instance and specify its value.
Step 4 If other values are to be changed, repeat Steps 1-3 until all desired changes are completed.
Step 5 Click Apply.
Step 6 Click OK.
Preparing a Device for a Connection
This section includes examples of how the device management functions in CiscoView are used. Specifically, these examples cover the preparation required to make
•An ATM connection,
•A frame relay connection
•A circuit emulation connection
Although the connections themselves are made by the connection manager in the main CWM program, certain device configurations at the node, card and port level are required within CiscoView before the connections can be made.
Example 1, Preparing for an ATM Connection
To prepare an ATM port for an ATM connection, the user can setup:
•Configuration details of the SONET line including alarm objects
•APS configuration
•Card redundancy
Note This example assumes an ATM connection on an AXSM card using a SONET line.
Configuring the SONET Line
Step 1 Choose the Resource Partitions category to display its objects as shown in Table 3-6 and Figure 3-9.
Figure 3-9 ATM Resource Partitions Objects
The objects are described in Table 3-1.
.
Table 3-1 ATM Resource Partition Objects
Objects
|
Description
|
Interface
|
Identifies the interface that has resource partitions.
|
Resource Partition
|
Resource partition controller identifier. One interface can have multiple resource partitions on it.
|
Partition Controller
|
Identifies the slot in which the partition controller resides.
|
Min Bw (Egress)
|
Minimum percentage of bandwidth used for this partition in the egress direction. Must be a number between 1 and 1000000. This is not the guaranteed bandwidth. If bandwidth is available, the resource partition will be allocated bandwidth up to this value.
|
Max Bw (Egress)
|
Maximum percentage bandwidth allocated for the resource partition in egress direction. Must be a number between 1 and 1000000. This is not the guaranteed bandwidth. If bandwidth is available, the resource partition will be allocated bandwidth up to this value.
|
Min Bw (Ingress)
|
Minimum percentage of bandwidth used for this partition in the ingress direction. Must be a number between 1 and 1000000. This is not the guaranteed bandwidth. If bandwidth is available, the resource partition will be allocated bandwidth up to this value.
|
Max Bw (Ingress)
|
Maximum percentage bandwidth allocated for the resource partition in ingress direction. Must be a number between 1 and 1000000. This is not the guaranteed bandwidth. If bandwidth is available, the resource partition will be allocated bandwidth up to this value.
|
Lower VPI Range
|
Beginning of the VPI range reserved for this partition. Connections provisioned on this partition must have a VPI greater than or equal to this value.
|
Higher VPI Range
|
End of the VPI range reserved for this partition. Connections provisioned on this partition must have a VPI less than or equal to this value.
|
Lower VCI Range
|
Beginning of the VCI range reserved for this partition. Connections provisioned on this partition must have a VCI greater than or equal to this value.
|
ILMI Enable
|
Enables ILMI signaling on the resource partition.
|
Higher VCI Range
|
End of the VCI range reserved for this partition. Connections provisioned on this partition must have a VCI less than or equal to this value.
|
Min Connection
|
Minimum number of connections that can be configured on this partition.
|
Max Connection
|
Maximum number of connections that can be configured on this partition.
|
VPI Signalling
|
Indicates the VPI on which signaling cells arrive on this resource partition.
|
ILMI Trap Enable
|
Ilmi trap generation can be enabled or disabled using this object. Choose enable or disable from the popup menu.
|
Est Conn Poll Intervals
|
Amount of time (in seconds) between successive transmissions of ILMI messages on this interface for the purpose of detecting establishment of ILMI connectivity.
|
ILMI Connect Poll Intvl
|
Amount of time (in seconds) between successive transmissions of ILMI messages on this interface for the purpose of detecting loss of ILMI connectivity. The distinguished value zero disables ILMI connectivity procedures on this interface.
|
Poll Conn Inact Factor
|
Number of consecutive polls on this interface, which no ILMI response message is received before ILMI connectivity is declared lost.
|
Step 2 To configure a resource partition that already exist, change their values as necessary. Click Apply.
Alternatively to create a new partition. Click Create, enter the details in the resulting table and click OK.
Step 3 When all the objects are correctly configured. Click OK.
To configure a SONET line use the following procedure.
Step 4 Using the front view of the AXSM card, right click the port for which the SONET line is to be configured.
Step 5 Click Configure in the resulting popup menu.
Step 6 Click the Category drop-down arrow to display the available categories.
Step 7 Click the category that the object values are configured. The configurable categories are
•ATM Cell Layer Config
•Sonet Line Config
•Sonet Line Alarm
•Sonet Medium Config
•Sonet Section Alarm
•Sonet Path Alarm
Step 8 Choose the Sonet Line Config category to display its object as shown in Figure 3-10.
Figure 3-10 Sonet Line Config Objects
These objects are described in Table 3-2.
Table 3-2 Sonet Line Config Objects
Object
|
Description
|
Line Number
|
Line number.
|
Speed(Mbps)
|
Line speed in Mbps.
|
Enable
|
Enables/disables the SONET line.
|
Loopback Type
|
Represents the desired loopback configuration of the SONET line. Choose one from the popup menu:
noLoopback—Not in the loopback state.
lineLocal—Signal sent at this line is looped back through the device.
lineRemote—Signal sent does not go through the device but is looped back out.
|
Clock source
|
Source of the transmit clock. Choose one from the popup menu:
loopTiming—Indicates that the recovered receive clock is used as the transmit clock.
localTiming—Indicates that a local clock source is used or that an external clock is attached to the box containing the interface.
|
FrameScramble
|
Enables/disables the Scrambling option in SONET line. Choose enabled or disabled from the popup menu.
|
Line Type
|
Configured line type.
This object can be used to switch between SONET (North America) format and SDH (Europe) format. Sts is SONET format. Stm is SDH format. The line types are as follows:
sonetSts3c: OC3
sonetStm1: European standard OC3
sonetSts12c: OC12
sonetStm4: European standard OC12
sonetSts48c: OC48
sonetStm16: European standard OC48
|
Step 9 To configure the Sonet Line objects, change their values as necessary, click Apply.
Step 10 When all the objects are correctly configured, click OK.
Step 11 Choose the Sonet Medium Config category to display its object as shown in Figure 3-11.
Figure 3-11 Sonet Medium Config Objects
These objects are described in Table 3-3.
Table 3-3 Sonet Medium Config Objects
Object
|
Description
|
Line
|
Line number.
|
Medium Type
|
Identifies whether or not a Sonet or an SDH signal is used across this interface. Can be Sonet or sdh.
|
Time Elapsed
|
Number of seconds, including partial seconds, that have elapsed since the beginning of the mandatory error-measurement period.
|
Valid Intervals
|
Number of previous intervals for which valid data has been stored.
|
Line Coding
|
Line coding for this interface. The B3ZS and CMI are used for electrical SONET/SDH signals (STS-1 and STS-3). The NRZ and the Return to Zero are used for optical SONET/SDH signals.
|
Line Type
|
Line type for the Sonet interface. The line types are short and long range single mode fiber or multi-mode fiber interfaces, and coax and UTP for electrical interfaces. Can be one of the following types.
•sonetOther
•sonetMediumB3Zs
•sonetShortSingleMode
•sonetLongSingleMode
•sonetMultimode
•sonetCoax
•sonetUTP
|
Circuit Id
|
Circuit identifier.
|
Step 12 To configure the Sonet Medium objects, change their values as necessary, click Apply.
Step 13 When all the objects are correctly configured, click OK.
Step 14 Choose the Sonet Line Alarm category to display its object as shown in Figure 3-12.
Figure 3-12 Sonet Line Alarm Objects
The objects are described in Table 3-4.
Table 3-4 AXSM Sonet Line Alarm Objects
Object
|
Description
|
Line Number
|
Line number.
|
cwsLineStatisticalAlarmSeverity
|
Indicates whether exceeding this statistical threshold is considered to be a minor or major severity alarm.
|
Line Curr ES Threshold
|
Threshold for ES1 detection on the working line.
|
Line Total ES Threshold
|
Number of ES encountered by a SONET/SDH Section in the last 24 hours.
|
Line Curr SES Threshold
|
Number of SES2 currently encountered by a SONET/SDH Section.
|
Line Total SES Threshold
|
Number of SES encountered by a SONET/SDH Section in the last 24 hours.
|
Line Curr CV Threshold
|
Number of CV3 encountered by a SONET/SDH Section in the last 24 hours.
|
Line TotalCV Threshold
|
Number of CV currently encountered by a SONET/SDH Section.
|
Line Curr UAS Threshold
|
Number of UAS4 encountered by a SONET/SDH Section in the last 24 hours.
|
Line Total UAS Threshold
|
Total number of UAS encountered by a SONET/SDH Section.
|
Line Alarms
|
Indicates the status of the line. Can be one or more of the following alarms.
•clear
•sonetSectionTotalESs
•sonetSectionTotalSESs
•sonetSectionTotalSEFSs
•sonetSectionTotalCVs
•sonetSectionCurrentESs
•sonetSectionCurrentSESs
•sonetSectionCurrentSEFSs
•sonetSectionCurrentCVs
|
Step 15 To configure the Sonet Line Alarm objects, change their values as necessary, click Apply.
Step 16 When all the objects are correctly configured, click OK.
Step 17 Choose the Sonet Section Alarm category to display its object as shown in Figure 3-13.
Figure 3-13 Sonet Section Alarm Objects
These objects are described in Table 3-5.
Table 3-5 Sonet Section Alarm Objects
Object
|
Description
|
Line
|
Identifies the line type.
|
cwSectionStatisticalAlarmSeverity
|
Indicates whether exceeding this statistical threshold is considered to be a minor or major severity alarm.
|
Sect Curr ES Threshold
|
Indicates the threshold for ES1 , for the current 15-minute interval.
|
Sect Total ES Threshold
|
Indicates the threshold for ES on a 24-hour interval.
|
Sect Curr SES Threshold
|
Indicates the threshold for SES2 on a 15-minute interval.
|
Sect Total SES Threshold
|
Indicates the threshold for SES on a 24-hour interval.
|
Sect Current SEFS Threshold
|
Indicates the threshold for the current 15-minute interval, for SEFS3 .
|
Sect Total SEFS Threshold
|
Indicates the threshold for SEFS on a 24-hour interval.
|
Sect Curr CV Threshold
|
Indicates the threshold for CV4 for the current 15-minute interval.
|
Sect Total CV Threshold
|
Indicates the threshold for CV on a 24-hour interval.
|
Section Alarms
|
Indicates the status of the interface. When an alarm is raised, this would indicate which threshold was exceeded. This object is updated every 15 minutes. Once the current 15-minute window has passed, and there are no errors in the current 15-minute window, the object is cleared from the lower level sonet task. The Section Alarm Status is a bit map represented as a sum, therefore, it can represent multiple defects simultaneously. If none of the bits are set, it indicates no defect. Can be one or more of the following:
•clear
•sonetSectionTotalESs
•sonetSectionTotalSESs
•sonetSectionTotalSEFSs
•sonetSectionTotalCVs
•sonetSectionCurrentESs
•sonetSectionCurrentSESs
•sonetSectionCurrentSEFSs
•sonetSectionCurrentCVs
|
Step 18 To configure the Sonet Section Alarm objects, change their values as necessary, click Apply.
Step 19 When all the objects are correctly configured, click OK.
Step 20 Choose the Sonet Path Alarm category to display its object as shown in Figure 3-14.
Figure 3-14 Sonet Path Alarm Objects
These objects are described in Table 3-6.
Table 3-6 Sonet Path Alarm Objects
Object
|
Description
|
Line Number
|
Identifies the selected line.
|
cwsPathStatisticalAlarmSeverity
|
When any statistical threshold is exceeded, this object is set to major or minor.
|
Path Curr ES Threshold
|
Indicates the errored seconds ES threshold for the current 15-minute interval, above which alarm is generated. This threshold is the same for Far End (remote end of the line) and Near End (this end of the line).
|
Path Total ES Threshold
|
Indicates the 24-hour interval threshold, above which alarm is generated. This threshold is the same for Far End (remote end of the line) and Near End (this end of the line).
|
Path Curr SES Threshold
|
Indicates the SES1 threshold for the current 15-minute interval, above which alarm is generated. This threshold is the same for Far End and Near End.
|
Path Total SES Threshold
|
Indicates the SES for the 24 hour interval, above which alarm is generated. This threshold is the same for Far End and Near End.
|
Path Cur CV Threshold
|
Indicates the CV2 threshold for the current 15-minute interval, above which alarm is generated. This threshold is the same for Far End and Near End.
|
Path Total CV Threshold
|
Indicates the CV for the 24 hour interval threshold, above which alarm is generated. This threshold is the same for Far End and Near End.
|
Path Cur UAS Threshold
|
UAS3 threshold for the current 15-minute interval, (above which alarm is generated). This threshold is the same for Far End and Near End.
|
Path Total UAS Threshold
|
UAS threshold for the 24 hour interval, above which alarm is generated. This threshold is the same for Far End and Near End.
|
Path Alarms
|
Indicates the status of the interface. The cwsPathStatAlarmStatus is a bit map represented as a sum, therefore, it can represent multiple defects simultaneously. If none of the bits are set, it indicates no defect. Can be one of the following alarms.
•sonetPathTotalESs
•sonetPathTotalSESs
•sonetPathTotalCVs
•sonetPathTotalUASs
•sonetPathCurrentESs
•sonetPathCurrentSESs
•sonetPathCurrentCVs
•sonetPathCurrentUASs
•sonetFarEndPathTotalESs
•sonetFarEndPathTotalSESs
•sonetFarEndPathTotalCVs
•sonetFarEndPathTotalUASs
•sonetFarEndPathCurrentESs
•sonetFarEndPathCurrentSESs
•sonetFarEndPathCurrentCVs
•sonetFarEndPathCurrentUASs
|
Step 21 To configure the Sonet Section Alarm objects, change their values as necessary, click Apply.
Step 22 When all the objects are correctly configured, click OK.
Configuring APS
If the SONET line is to have Automatic Protection Switching (APS), it can be enabled and configured using the following procedure.
Step 1 Using the front view of the node, choose the node by right clicking the dark area above the cards.
Step 2 Choose Configure from the resulting pop up menu.
Step 3 Click the Category drop- down arrow to display the node categories.
Step 4 Click the Category drop-down arrow to choose the SONET Line APS category. This action causes the APS object values to be displayed as shown in Figure 3-15.
This is a general purpose screen for any and all ATM connections on the shelf and, therefore, can have multiple instances (one for each ATM connection).
Figure 3-15 SONET APS Objects
Step 5 If no APS instances exist (see Figure 3-15) or if APS has not been previously setup for the ATM connection being configured, click the Create button. This action causes the APS row creation window to be displayed (see Figure 3-16).
Step 6 Enter the details of Primary and Secondary slots, bays, lines and the desired APS mode.
Figure 3-16 APS Row Creation Window
.
Step 7 Click OK. A new row in the SONET Line APS screen is created.
Step 8 In the SONET Line APS screen the remaining objects can be entered.
Step 9 Click OK.
Configuring Card Redundancy
APS protection on a SONET line can be combined with front card redundancy. In this way the ATM link is protected from both line and card failures. A description of the general procedure for configuring card redundancy is included after example 3, later in this chapter.
Configuring a SONET Port
To configure a SONET port, use the following procedure.
Step 1 Using the front view of the shelf, right click the AXSM card on which the port that is to be configured.
Step 2 Click Configure in the popup menu.
Step 3 Click the Category drop-down arrow in the field to display the available port categories. The following categories are
•ATM Virtual Ports
•ATM Virtual Port Ingress Cells
•ATM Virtual Port Egress Cells
•Resource Partitions
Step 4 Choose the ATM Virtual Ports category to display its objects as shown in Table 3-6 and Figure 3-17.
Figure 3-17 ATM Virtual Port Objects
These objects are described in Table 3-7.
Table 3-7 ATM Virtual Port Objects
Object
|
Description
|
Physical Interface
|
Number identifying the physical interface.
|
Virtual Interface
|
Virtual port number.
|
Max Cell Rate
|
Virtual interface's maximum cell rate. This is the maximum bandwidth allocated for the interface. The total bandwidth of connections configured over this interface cannot exceed this value. ATM cell bandwidths for various physical lines are as follows:
•OC48 line: 5651328 cells/sec
•OC12 line: 1412832 cells/sec
•OC3 line: 353208 cells/sec
•T3 line: 96000 cells/sec
•E3 line: 80000 cells/sec
|
Min Cell Rate
|
Virtual interface's minimum cell rate. This is the guaranteed bandwidth allocated for the interface. The sum of caviMinRate of all logical interfaces configured on a single physical line, must not exceed the bandwidth of the physical line. Creation of a row is rejected when the sum of caviMinRate of all existing logical interfaces exceeds the physical line bandwidth. ATM cell bandwidths for various physical lines are as follows:
•OC48 line: 5651328 cells/sec
•OC12 line: 1412832 cells/sec
•OC3 line: 353208 cells/sec
•T3 line: 96000 cells/sec
•E3 line: 80000 cells/sec
|
SCT ID
|
File ID that holds module specific configuration objects for this virtual interface.
|
Interface Type
|
Reflects the format of the cells transmitted by the physical interface. The following formats can be configured:
uni: user port
nni: network port
vnni: virtual network port
vuni: virtual user port
enni: enhanced network port
evuni: enhanced virtual user port
|
VPI No.
|
Virtual Path Interface number. Only applicable for the VNNI interface type.
|
Step 5 To configure existing port objects that already exist, change their values as necessary. Click Apply.
Alternatively, to create a new port, click Create. Enter the configuration details in the resulting screen. Click OK.
Step 6 When all the objects are correctly configured, click OK.
Step 7 Choose the ATM Virtual Port Ingress Cells category to display its objects as shown in Figure 3-18.
Figure 3-18 ATM Virtual Port Ingress Cells Object
These objects are described in Table 3-8.
Table 3-8 ATM Virtual Port Ingress Cells Objects
Object
|
Description
|
Virtual Port
|
Virtual port number.
|
CLP0 Cells
|
Number of CLP-0 cells received from the switch at the traffic management and policing device in the ingress direction.
|
CLP1 Cells
|
Number of CLP-1 cells received from the switch at the traffic management and policing device in the ingress direction.
|
CLP0 Discarded Cells
|
Number of CLP-0 cells discarded due to policing in the ingress direction.
|
CLP1 Discarded Cells
|
Number of CLP-1 cells discarded due to policing in the ingress direction.
|
Step 8 To configure ingress cells, change their values as necessary, click Apply.
Step 9 When all the objects are correctly configured. Click OK.
Step 10 Choose the ATM Virtual Port Egress Cells category to display its objects as shown in Figure 3-19.
Figure 3-19 ATM Virtual Port Egress Cell Objects
These objects are described in Table 3-9.
Table 3-9 ATM Virtual Port Egress Cells Objects
Object
|
Description
|
Virtual Port
|
Virtual port number.
|
CLP0 Cells
|
Number of CLP-0 cells received from the switch at the traffic management and policing device in the egress direction.
|
CLP1 Cells
|
Number of CLP-1 cells received from the switch at the traffic management and policing device in the egress direction
|
CLP0 Discarded Cells
|
Number of CLP-0 cells discarded due to policing in the egress direction.
|
CLP1 Discarded Cells
|
Number of CLP-1 cells discarded due to policing in the egress direction.
|
Step 11 To configure Egress Cells change their values as necessary. Click Apply.
Step 12 When all the objects are correctly configured, click OK.
Step 13 Choose the ATM Cell Layer Config category to display its object as shown in Figure 3-20.
Figure 3-20 ATM Cell Layer Config Objects
These objects are described in Table 3-10.
Table 3-10 ATM Cell Layer Config Objects
Object
|
Description
|
Port Number
|
Port number.
|
Status
|
Displays the status of the port.
|
Null Cell Header
|
First four bytes of the ATM header to be used for Null cells. Generally, idle cells are inserted into a cell stream as a mechanism for rate adaptation between the ATM data link layer and the physical layer. The following fields can be specified in the value of this object:
•Generic flow control
•Payload type
•Cell Loss Priority
The Null Cell Header applies to both transmitted as well as received cells.
|
Null Cell Payload
|
Null Cell Payload definition. The idle cell information field can be specified in this object. It applies to both transmitted as well as received cells. The default value is 106.
|
HEC Coset Enable
|
Use this object to enable or disable the algorithm of Coset Polynomial Addition to do header error check calculations. To enable the algorithm, choose True from the popup menu; to disable it, choose False.
This object applies to transmitted as well as received cells.
|
Payload Scrambling
|
Indicates whether Payload Scrambling is enabled. To enable Payload Scrambling, choose True from the popup menu; to disable it, choose False.
|
Step 14 To configure the ATM Cell Layer objects, change their values as necessary, click Apply.
Step 15 When all the objects are configured correctly. Click OK.
Example 2, Preparing for a Frame Relay Connection
To prepare a port for a circuit emulation connection, the user can setup:
•Line configuration
•Port configuration
•Channel configuration
•Card redundancy
Note This example assumes a Frame Relay connection using an 8-port FRSM card using Dsx-1 lines.
Configuring FRSM Line Categories
To configure FRSM line categories, use the following procedure.
Step 1 Right-click the line or connector (from either the front or rear view of the card) to be configured to display the Line popup menu.
Step 2 Choose Configure in the resulting popup menu.
Step 3 Click the Category drop-down arrow to display the available FRSM line categories. The following categories are
•Physical Line Configuration (dsx1)
•Physical Line Alarm Configuration (dsx1)
•Dsx1 Line Real-Time Counters
•Logical Ports
•Choose the Physical Line Configuration (dsx1) category to display its objects as shown in Figure 3-21.
Figure 3-21 Physical Line Config (dsx1) Objects
The Physical Line Config (dsx1) objects are described in Table 3-11.
Table 3-11 Physical Line Config (dsx1) Objects
Object
|
Description
|
Line Num
|
Line number.
|
Type
|
Line type. Choose one from the popup menu:
•dsx1ESF
•dsx1D4
•dsx1E1
•dsx1E1CRC
•dsx1E1CRC-MF
•dsx1E1MF
•dsc1E1clearchannel
|
Connector
|
Line connector type and the back card type. Can be one of the following connector types.
•db15
•bnc
•rj48
|
Line Enable
|
Turns a line signal on or off with the enable or disable settings. Use modify to change the object setting of a line that has already been enabled.
Note Before you can change any objects for a line, you must set this object to modify.
|
Coding
|
Type of zero code suppression used on the line, that affects a number of its characteristics. Choose one from the popup menu:
•dsx1HDB3
•dsx1JBZS
•dsx1B8ZS
•dsx1AMI
JBZS = Jammed Bit Zero Suppression
|
Length
|
Line length. Choose one from the popup menu:
•lineLength0to110Feet
•lineLength110to220Feet
•lineLength220to330Feet
•lineLength330to440Feet
•lineLength440to550Feet
•lineLength550to660Feet
•lineLength660FeetPlus
•lineLength-75-ohm
•lineLength-120-ohm
•lineLength0to131Feet
•lineLength131to262Feet
•lineLength262to393Feet
•lineLength393to524Feet
•lineLength524to655Feet
•lineLength655FeetPlus
•notRequired
|
Xmt Clock
|
Transmit clock source. Choose one from the popup menu:
•localTiming
•loopTiming
•throughTiming
On a CESM card, only localTiming is supported.
|
Loopback
|
Line loopback configuration of the DS1 interface. Choose one of the following from the popup menu:
•dsx1LocalLoop
•dsx1NoLoop
•dsx1RemoteLoop
|
Code Sent
|
Type of code sent across DS1. Choose one from the popup menu:
•dsx1SendNoCode
•dsx1SendLineCode
•dsx1SendPayLoadCode
•dsx1SendResetCode
•LineUsedTimeslotsBitMap
|
Ds0's Used
|
DS0s used for this line.
|
Loopback code Detect
|
Indicates whether or not detection of line loopback codes is enabled. Choose codeDetectDisabled or codeDetectEnabled from the popup menu.
|
Enable Bert
|
Indicates whether or not BERT is enabled.
|
Step 4 To configure the Physical Line dsx1 objects, change their values as necessary, click Apply.
Step 5 When all the objects are correctly configured, click OK.
Step 6 Click the drop-down arrow on the Physical Line Alarm Config(dsx1) category to display its objects as shown in Figure 3-22.
Figure 3-22 Physical Line Alarm Config (dsx1) Objects
The Physical Line Alarm Config (dsx1) objects are described in Table 3-12.
Table 3-12 Physical Line Alarm Config (dsx1) Objects
Object
|
Description
|
Line Number
|
Line number.
|
Line Alarm State
|
Status of the line alarm. A value of zero indicates no alarms.
|
Line Statistical Alarm State
|
Status of the line statistical alarm. A value of zero indicates no alarms.
|
Setup Severity of Red Alarm
|
Used to set up the severity of RED alarm. When the LOS alarm is detected, the FRSM sends the alarm with the appropriate severity status. Choose major or minor from the popup menu.
|
Setup Severity of RAI Alarm
|
Used to set up the severity of RAI alarm. When the LOS alarm is detected, the FRSM sends the alarm with the appropriate severity status. Choose major or minor from the popup menu.
|
Near-End Alarm Counter (up Counter)
|
Integration counter. The local alarms are LOS and LOF. The default is 6.
|
Near-End Alarm Counter (down Counter)
|
Integration counter. The near-end alarms are LOS and LOF. The default is 1.
|
Near-End Alarm Threshold
|
Determines the value to declare for near-end alarm. A count of 1500 gives 2.5 seconds to declare LOS with an up count value of 6.
|
Far-End Alarm Counter (up Counter)
|
Integration counter. The far-end alarms are AIS and YEL. The default is 6.
|
Far-End Alarm Counter (down counter)
|
Integration counter. The far-end alarms are AIS and YEL. The default is 1.
|
Far-End Alarm Threshold
|
Determines the value to declare for far-end alarm. A count of 1500 gives
2.5 seconds to declare LOS with an up count value of 6.
|
Statistical Alarm Severity
|
Sets up the severity of statistical alarm. When any statistical alarm is detected, the FRSM sends the alarm with appropriate severity status. Choose one from the popup menu:
•major
•minor
•inhibit
|
Step 7 To configure the Physical Line Alarm dsx1 objects, change their values as necessary, click Apply.
Step 8 When all the objects are correctly configured. Click OK.
Step 9 To view the Dsx1 Line Real Time Counters category, click the drop-down arrow to display its objects as shown in Figure 3-23.
Figure 3-23 Dsx1 Line Real-Time Counters Objects
The Dsx1 Line Real Time Counters objects are described in Table 3-13.
Table 3-13 Dsx1 Line Real-Time Counters Objects
Object
|
Description
|
cntLineNumber
|
Line number.
|
Clear Line Counters
|
Resets all the counters with the clear option.
|
rcvLOSCount
|
Number of times the LOS1 is detected with or without integrating to LOS alarm.
|
rcvOOFCount
|
Number of times the yellow alarm is detected with or without integrating to RAI alarm.
|
rcvRAICount
|
Number of times the yellow alarm is detected with or without integrating to RAI alarm.
|
rcvFECount
|
Number of Framing Errors detected.
|
Step 10 To configure the Dsx1 Line Real-Time counters objects, change their values as necessary. Click Apply.
Step 11 When all the objects are correctly configured, click OK.
Configuring an FRSM Port
Perform the following steps to configure a FRSM port.
Step 1 Using the front view of the shelf, right-click the FRSM card for which the FRSM connection that is to be set up.
Step 2 Click Configure in the resulting popup menu.
Step 3 Click the Category drop-down arrow to display the FRSM categories. The configurable categories are:
•Card
•Service Module Features
•FR Port Real-Time Counters
•Ports
•Channels
The Card, Service Module Features, and FR Port Real-Time Counters categories are for informational purposes only and cannot be configured. Preparing for a FRSM connection involves first configuring the port and then configuring the channels.
Step 4 Choose the Ports category to display its objects as shown in Figure 3-24.
Figure 3-24 FRSM Port Category
Details of these objects are shown in Table 3-14.
Table 3-14 FRSM Port Objects
Object
|
Description
|
portNum
|
Logical port number.
Note For T3, only one port is supported.
|
portRowStatus
|
Used to enable, delete, or modify the port. Choose one from the popup menu:
•add
•del
•mod
|
portLineNum
|
Represents the line number to which this port is associated.
Note For T3 only one line is supported.
|
Port type
|
Represents the port type. Choose one from the popup menu:
•structured
•unstructured
•framingOnVcDisconnect
Note An unstructured port allocates all the time slots to framingOnVcDisconnect. T3 card will support only framingOnVcDisconnect.
|
portDs0Config
|
Represents bit map of DS0s for a line. These DS0s are used to form this logical port. Bit 0 represents DS0-1.
|
PortNum of Ds0 Time Slots Configured
|
Number of DS0 time slots configured to this port.
|
PortNumOfSciPerDS0
|
Number of subcircuits in the DS0 time slot.
|
Port Speed (Kbps)
|
Port speed in kbps:
•Max speed for T1—1544
•Max speed for E1—2038
•Max speed for T3—44736
•Max speed for E3—34368
|
Port State
|
Logical port state. Can be
•notConfigured
•active
•remoteLoopback
•failedDueToLine
•failedDueToSignalling
•inactive
•inBert
•farEndRemoteLoopback
|
Step 5 To configure the FRSM port objects, change their values as necessary, click Apply.
Step 6 When all the objects are correctly configured, click OK.
Configuring an FRSM Channel
With the FRSM categories displayed, choose the Channel category. The FRSM Channel Config window appears (see Figure 3-25).
Figure 3-25 FRSM Channel Objects
These objects are described in Table 3-15.
Table 3-15 FRSM Channel Objects
Object
|
Description
|
Channel Number
|
Virtual connection number.
|
ChannelRowStatus
|
Channel row status.
Note Choose modify to change the object settings for a channel which has already been added.
|
ChannelPortNum
|
Refers to the logical ports that are possible on this card, the user must set this variable.
|
Clear Channel button
|
Clears Channel Counters with the clear option.
|
dLCI
|
DLCI1 number of the channel. The user must set this variable. All the connections on the same port should have a unique DLCI number.
|
Egress Q Choose
|
Chooses one of two possible port queues. Can be
•highPriority
•lowPriority
•notSupported (indicates this entry is not used)
|
Ingress Q Depth
|
Sets the maximum depth for queue before it starts dropping cells. It is defined in terms of number of bytes.
|
Ingress Q ECN Threshold
|
Sets the maximum depth for queue before it starts flow control. It is defined in terms of number of bytes.
|
Ingress Q DE Threshold
|
Sets the maximum depth for queue before they become discard eligible. It is defined in terms of number of bytes.
|
Egress Q Depth
|
Sets the maximum depth for queue before it starts dropping the cells. It is defined in terms of number of bytes.
|
Egress Q DE Threshold
|
Sets the maximum depth for queue before they become discard eligible. It is defined in terms of number of bytes.
|
Egress Q ECN Threshold
|
Sets the maximum depth for queue before it starts flow control. It is defined in terms of number of bytes.
|
Enable DE Tagging
|
Enables DE tagging in the ingress direction only. Choose enable or disable from the popup menu. The default is disable.
|
Committed Information Rate (BPS)
|
Defines the Committed Information Rate in bits per second. The default is 2400. The maximum value for E1 is 2048000; the maximum value for T1 is 1536000. CIR has to be less than or equal to the port speed.
|
Burst Committed
|
Defines the Burst Committed. The default value is 5100. If CIR is not 0, Bc cannot be 0. Bc must be 0 if CIR is 0.
|
Burst Excess
|
Defines the Burst Excess. The default value is 5100. If CIR is not 0, BE cannot be 0.
|
Burst Size
|
Default is 100. IBS should be less than or equal to BC when CIR is greater than 0. IBS must be 0 when CIR is 0.
|
Enable ForeSight
|
Sets the ForeSight option. Choose enable or disable from the popup menu. The default is disable.
|
Quiescent Information Rate (CPS)
|
Defines quiescent information rate for ForeSight in cells per second. The default is 10.
|
Minimum Information Rate (CPS)
|
Defines minimum information rate for ForeSight in cells per second. The default is 10.
|
Peak Information Rate (CPS)
|
Defines peak information rate for ForeSight in cells per second. The default is 10.
|
Remote Lpbk State
|
Used to enable or disable the remote loopback for each channel. When you enable this option on a channel, all the cells coming from the network side are looped back towards the network and all the frames coming from the user side are dropped. The default is disabled.
|
Channel Test Type
|
Tests the continuity or delay of a connection, sending specific cell patterns towards the network. The receiving node would loop back when it receives these cells. The test should be done in a few seconds. Use testcon to test the continuity of the connection. Use testdelay for the same test except that it measures the delay through the network.
Choose one from the popup menu:
•testcon
•testdelay
•notest (This is the default.)
To test the delay follow this procedure:
1. Set Channel Test Type to testdelay.
2. Read Channel Test State till it is pass or fail.
3. Read Round-Trip Delay for the delay if it is pass.
Note The Channel Test Type returns to notest when the test is complete.
To test the continuity follow this procedure:
1. Channel Test Type to testcon.
2. Read Channel Test State till it is pass or fail.
Note The Channel Test Type returns to notest when the test is complete.
You cannot choose two tests back to back. Choose one test and wait for it to complete its cycle before choosing another test.
|
Channel Test State
|
State of the test. Can be one of the following states:
•passed
•failed
•inprogress
•notinprogress
When you add a connection, the Channel Test State becomes notinprogress. When you choose any test, it goes to the inprogress state. After it completes the test, failed or passed is displayed.
|
Round-Trip Delay (Milli Secs)
|
Round trip delay in ms. When Channel Test Type is testdelay, the result of the test can be read in chanRTDResult.
When no test is run, 65535 is displayed.
|
Channel Type
|
Sets the channel type. Choose one from the popup menu:
•frNIW—Frame Relay Network Interworking
•frSIW-transparent—Service Interworking without any SDU translation
•frSIW-translate—Service Interworking with SDU translation
•frFUNI—Frame Relay UNI
•frForward—Frame Forwarding
|
Channel FECN Config
|
Sets the FECN2 configuration mapEFCI, valid only for SIW. The FECN bits in frame relay are mapped to explicit EFCI3 bit in the ATM cells. Choose mapEFCI or setEFCIzero from the popup menu.
|
Map CLP Bit
|
Sets the mapping of CLP4 bit. Choose one from the popup menu:
•mapCLP—The DE5 bit is mapped to CLP bit in ATM cell.
•setCLPzero—The DE bit is ignored and CLP bit is set to a constant value.
•setCLPone—The DE bit is ignored and CLP bit is set to a constant value.
|
Map DE Bit
|
Sets the mapping of DE bit. Choose one from the popup menu:
•mapDE—The CLP bit is mapped to DE bit in frame relay.
•setDEzero—The CLP bit is ignored and DE bit is set to a constant value.
•setDEone—The CLP bit is ignored and DE bit is set to a constant value.
•ignoreCLP—Ignores CLP bit and DE bit remains as received.
|
Ingress Percent Util
|
Channel ingress utilized percentage. Can be 1...100.
|
Egress Percent Util
|
Channel egress utilized percentage. Can be 1...100.
|
Egress CIR
|
Channel egress CIR6 . The egress CIR has to be less than or equal to the port speed.
Maximum value for E1 card = 2048000
Maximum value for T1 card = 1536000
|
Override Oversubscription
|
Permits adding a new connection on a port, even if it is oversubscribed. Choose disable or enable from the popup menu.
|
FR Conn Type
|
FR7 channel connection type. Choose pvc or svc from the popup menu.
|
FR CDR Number
|
FR CDR8 key to correlate cell/frame counts, start and end record.
|
Configuring Logical Ports
To configure an FRSM logical port, use the following procedure.
Step 1 Using the front view of the shelf, right-click the port to be configured.
Step 2 Click Configure in the resulting popup menu.
Step 3 Click the Category drop-down arrow to display the available logical port categories.
The following categories are
•Logical Port Configuration (FR Ports)
•FR Port RTCs
•FR Port RTCs (CLLM)
Step 4 Click the drop-down arrow on the Logical Port Configuration (FR Ports) category to display its objects (see Figure 3-26).
Figure 3-26 Logical Port Config (FR Ports) Objects
The Logical Port Config (FR Ports) objects are described in Table 3-16.
Table 3-16 Logical Port Config (FR Ports) Objects
Object
|
Description
|
Port No.
|
Logical port number.
|
Line No.
|
Line number associated with the logical port.
|
Port RowStatus
|
Port row status. Choose delete or modify. Click the Create button to add a port.
|
Port Ds0 Config Bitmap
|
Bitmap of DS0s for a line, used to form this logical port. Bit 0 represents DS0-1.
|
Port Ds0 Speed
|
Port DSO speed in cells per second.
|
Port Flags
|
Number of flags transmitted between Frame Relay frames.
|
EQueue Service Ratio
|
Number of times queue 1 is serviced for every time queue 2 is serviced.
|
Port Speed (kbps)
|
Port DS0 speed in kbps.
|
Port Admin Status
|
Port administrative status. Choose one from the popup menu:
•up
•down
•write-Only —(for display purposes only)
|
Port State
|
Logical port state.
|
portSvcStatus
|
Port SVC status.
|
portSvcShareLcn
|
Indicates whether or not the LCN and VPid address spaces are shared across all the ports.
|
portSvcLcnLow
|
Beginning of the LCN range reserved for SVCs.
|
portSvcLcnHigh
|
End of the LCN range reserved for SVCs.
|
portSvcDlciLow
|
Beginning of the DLCI range reserved for SVCs.
|
portSvcDlciHigh
|
End of the DLCI range reserved for SVCs.
|
Port Type
|
Port type. Choose one from the popup menu:
•structured
•unstructured
•framingOnVcDisconnect
•strau
|
Signaling Protocol Type
|
Signaling protocol type. Choose one from the popup menu:
•other
•no signalling
•strataLMI
•annexAUNI
•annexDUNI
•annexANNI
•annexDNNI
|
Async Updates
|
Enables asynchronous status updates. Choose disable or enable.
|
Link Integrity Timer (Secs)
|
Interval in seconds for NNI to do status polling.
|
Poll Verification Timer (Secs)
|
Interval in seconds for UNI to expect status polling.
|
Status Polling Counter
|
Number of UNI/NNI polling cycles.
|
Error Threshold
|
UNI/NNI error threshold.
|
Event Count
|
UNI/NNI events, always greater than the Error Threshold object.
|
Enhance LMI
|
Indicates whether or not enhanced LMI is enabled on a logical port. Choose disable or enable.
|
CLLM Enable
|
Enables or disables CLLM. Choose disable or enable.
|
CLLM Xmt Status Timer (Milli Secs)
|
Interval in ms for CLLM to send CLLM updates.
|
Port Signaling State
|
Port signaling state.
•Bit 0 = 0 LMI okay or not enabled
•Bit 0 = 1 LMI failed
•Bit 1 = 0 CLLM okay or not enabled
•Bit 1 = 1 CLLM failed
|
Port Oversubscribed
|
Indicates whether or not the port is oversubscribed. Can be true or false.
|
Port Ingress Percent Utilization
|
Percentage of utilization of the port in the ingress direction.
|
Port Egress Percent Utilization
|
Percentage of utilization of the port in the egress direction.
|
Step 5 To configure logical port objects that already exist, change their values as necessary. Click Apply.
To create a new logical port, click Create, and enter the configuration details in the resulting screen. Click OK.
Step 6 When all the objects are correctly configured, click OK.
Step 7 Click the drop-down arrow from the FR Port RTCs category to display its objects as shown in Figure 3-27.
Figure 3-27 FR Port RTCs Objects
The FR Port RTCs objects are described in Table 3-17.
Table 3-17 FR Port RTCs Objects
Object
|
Description
|
cntPortNum
|
Logical port number.
|
rcvPortFrames
|
Total number of frames received in the ingress direction.
|
rcvPortBytes
|
Total number of bytes received in the ingress direction.
|
rcvPortFrames with DE
|
Total number of frames with DE bit set in the ingress direction.
|
rcvPortFECNs
|
Total number of frames with FCNS bit set in the ingress direction.
|
rcvPortBECNs
|
Total number of frames with BECN bit set in the ingress direction.
|
rcvCRCErrFrames
|
Total number of frames discarded in Ingress due to CRC error.
|
rcv Frames DiscAlignmentErr
|
Total number of frames discarded in ingress due to alignment error.
|
rcvFramesDiscIllLen
|
Total number of frames discarded in ingress due to illegal length.
|
rcv Frames IllegalHeader
|
Total number of frames discarded in ingress due to illegal header.
|
rcvFramesAbort
|
Total number of received frames aborted.
|
rcv Frames Unkn DLCI
|
Total number of frames received with an unknown DLCI.
|
rcv Last Unkn DLCI
|
Last unknown DLCI received.
|
rcv Frames Tagged FECN
|
Total number of frames received that were tagged with FECN bit.
|
rcv Frames Tagged BECN
|
Total number of frames received that were tagged with BECN bit.
|
rcv Frames Tagged DE
|
Total number of frames received that were tagged with DE bit.
|
rcv Frames Disc Exceeded Threshold
|
Total number of frames discarded in ingress due to exceeded DE threshold.
|
rcv Kbps AIR
|
Received Average Information Rate in kbps.
|
rcv Buf Not Available
|
Total number of times the receiver is turned off.
|
Xmt Port Frames
|
Total number of frames transmitted.
|
Xmt Port Bytes
|
Total number of bytes transmitted.
|
Xmt Port Frames FECN
|
Total number of frames transmitted with FECN bit already set.
|
Xmt Port Frames BECN
|
Total number of frames transmitted with BECN bit already set.
|
Xmt Port Disc. Exceed Q Depth
|
Total number of bytes discarded in egress due to exceeded queue depth.
|
Xmt PortBytesDiscXceedQDepth
|
Total number of frames discarded in egress due to exceeded queue depth.
|
Xmt Port Frames During LMI Alarm
|
Total number of frames transmitted during LMI logical port alarm.
|
Xmt Port Bytes During LMI Alarm
|
Total number of bytes transmitted during LMI logical port alarm.
|
Xmt Frames Abort
|
Total number of transmit frames aborted.
|
Xmt Frames Underrun
|
Total number of frames discarded due to overrun.
|
Xmt Kbps AIR
|
Transmit Average Information Rate in kbps.
|
Xmt Buf Not Available
|
Total number of times the transmitter is turned off.
|
rcv Frames Discarded due to No Chan
|
Total number of frames received when no channel is set up.
|
rcv Status Inquiry
|
Total number of Status Inquiry messages received.
|
rcv Invalid Request
|
Total number of Invalid Request messages received.
|
rcv UNI Seq. Mismatch
|
Number of times UNI messages with sequence number mismatches were received.
|
Xmt Status
|
Number of times Status Response messages were transmitted.
|
Xmt Async Update
|
Number of times Asynchronous Status messages were transmitted.
|
UNI Signaling Timeout
|
Number of times UNI Status Requests were not received.
|
XMT Status Inquiry
|
Number of Status Inquiry messages transmitted.
|
rcv Async Update
|
Number of times Asynchronous Status messages were received.
|
rcv NNI Seq. Mismatch
|
Number of times NNI messages with sequence number mismatches were received.
|
rcv NNI Signaling Timeout
|
Number of times NNI Status requests were not received.
|
Step 8 To configure FR Port RTC objects, change their values as necessary. Click Apply.
When all the objects are correctly configured, click OK.
Step 9 Click the drop-down arrow from the FR Port RTCs (CLLM) category to display its objects as shown in Figure 3-28.
Figure 3-28 FR Port RTCs (CLLM) Objects
The FR Port RTCs (CLLM) objects are described in Table 3-18.
Table 3-18 FR Port RTCs (CLLM) Objects
Object
|
Description
|
rcv Frames CLLM
|
Number of CLLM frames received.
|
rcv Bytes CLLM
|
Number of CLLM bytes received.
|
xmtFramesCLLM
|
Number of CLLM frames transmitted.
|
xmtBytesCLLM
|
Number of CLLM bytes transmitted.
|
CLLM Failures
|
Number of times an expected CLLM message was not received.
|
Step 10 To configure FR Port RTC (CLLM) objects, change their values as necessary. Click Apply.
Step 11 When all the objects are correctly configured, click OK.
Configuring FRSM Card Redundancy
A description of the general procedure for configuring card redundancy is included after example 3, later in this chapter.
Example 3, Preparing for a Circuit Emulation Connection
To prepare a port for an circuit emulation connection, the user can setup:
•CESM port and channel configuration
•Line configuration
•Card redundancy
Note This example assumes an circuit emulation connection using a DSX 3 line.
Configuring a CESM Physical Line
To configure a physical CESM line, use the following procedure.
Step 1 Using the front or rear view of the shelf and the card on which the line is to be configured, right-click the line or connector.
Step 2 Click Configure in the popup menu.
Step 3 Click the Category drop-down arrow to display the available categories. The following categories are
•Dsx1
•Dsx3
Step 4 Click the category for the line type to be configured.
Step 5 Configure the Dsx1 or Dsx3 objects as appropriate (see following procedures for details).
Configuring Dsx 1 Objects
To configure Dsx1 objects, perform the following steps.
Step 1 When Dsx 1 has been selected, the configurable categories for this line type are displayed. These categories are
•Physical Line Configuration (dsx1)
•Physical Line Alarm Config (dsx1)
Step 2 Click the drop-down arrow for the Physical Line Config(dsx1) category to display the objects as shown in Figure 3-29.
Figure 3-29 Physical Line Config (dsx1) Objects
Details of these objects are described in Table 3-19.
Table 3-19 Physical Line Config (dsx1) Objects
Object
|
Description
|
Line Num
|
Line number.
|
Type
|
Line type. Choose one from the popup menu:
•dsx1ESF
•dsx1D4
•dsx1E1
•dsx1E1CRC
•dsx1E1CRC-MF
•dsx1E1MF
•dsc1E1clearchannel
|
Connector
|
Line connector type and the back card type. Can be one of the following connectors.
•db15
•bnc
•rj48
|
Line Enable
|
Turns a line signal on or off with the enable or disable settings. Use modify to change the object setting of a line that has already been enabled.
Note Before you can change any objects for a line, you must set this object to modify.
|
Coding
|
Type of zero code suppression used on the line, which affects a number of its characteristics. Choose one popup menu:
•dsx1HDB3
•dsx1JBZS
•dsx1B8ZS
•dsx1AMI
JBZS—Jammed Bit Zero Suppression
|
Length
|
Line length. Choose one from the popup menu:
•lineLength0to110Feet
•lineLength110to220Feet
•lineLength220to330Feet
•lineLength330to440Feet
•lineLength440to550Feet
•lineLength550to660Feet
•lineLength660FeetPlus
•lineLength-75-ohm
•lineLength-120-ohm
•lineLength0to131Feet
•lineLength131to262Feet
•lineLength262to393Feet
•lineLength393to524Feet
•lineLength524to655Feet
•lineLength655FeetPlus
•notRequired
|
Xmt Clock
|
Transmit clock source. Choose one from the popup menu:
•localTiming
•loopTiming
•throughTiming
On a CESM card, only localTiming is supported.
|
Loopback
|
Line loopback configuration of the DS1 interface. Choose one from the popup menu:
•dsx1LocalLoop
•dsx1NoLoop
•dsx1RemoteLoop
|
Code Sent
|
Type of code sent across DS1. Choose one from the popup menu:
•dsx1SendNoCode
•dsx1SendLineCode
•dsx1SendPayLoadCode
•dsx1SendResetCode
•LineUsedTimeslotsBitMap
|
Loopback code Detect
|
Indicates whether detection of line loopback codes is enabled. Choose codeDetectDisabled or codeDetectEnabled from the popup menu.
|
Enable Bert
|
Indicates whether BERT is enabled.
|
Step 3 To configure Physical Line objects, change their values as necessary. Click Apply.
Step 4 When all the objects are correctly configured, click OK.
Step 5 Choose the Physical Line Alarm category to display its objects as shown in Figure 3-30.
Figure 3-30 Physical Line Alarm Config (dsx1) Objects
Details of these objects are described in Table 3-20.
Table 3-20 Physical Line Alarm Config (dsx1) Objects
Object
|
Description
|
Line Number
|
Line number.
|
Line Alarm State
|
Status of the line alarm. A value of zero indicates no alarms.
|
Line Statistical Alarm State
|
Status of the line statistical alarm. A value of zero indicates no alarms.
|
Setup Severity of Red Alarm
|
Used to set up the severity of the RED alarm. When the LOS alarm is detected, the FRSM sends the alarm with the appropriate severity status. Choose major or minor from the popup menu.
|
Setup Severity of RAI Alarm
|
Used to set up the severity of the RAI alarm. When the LOS alarm is detected, the FRSM sends the alarm with the appropriate severity status. Choose major or minor from the popup menu.
|
Near-End Alarm Counter (up Counter)
|
Integration counter. The local alarms are LOS and LOF. The default is 6.
|
Near-End Alarm Counter (down Counter)
|
Integration counter. The near-end alarms are LOS and LOF. The default is 1.
|
Near-End Alarm Threshold
|
Determines the value to declare for near-end alarm. A count of 1500 gives 2.5 seconds to declare LOS with an up count value of 6.
|
Far-End Alarm Counter (up Counter)
|
Integration counter. The far-end alarms are AIS and YEL. The default is 6.
|
Far-End Alarm Counter (down Counter)
|
Integration counter. The far-end alarms are AIS and YEL. The default is 1.
|
Far-End Alarm Threshold
|
Determines the value to declare for far-end alarm. A count of 1500 gives 2.5 seconds to declare LOS with an up count value of 6.
|
Statistical Alarm Severity
|
Used to set up the severity of statistical alarm. When any statistical alarm is detected, the FRSM sends the alarm with appropriate severity status. Choose one from the popup menu:
•major
•minor
•inhibit
|
Step 6 To configure Physical Line Alarm objects, change their values as necessary. Click Apply.
Step 7 When all the objects are correctly configured, click OK.
Configuring dsx 3 Objects
To configure dsx3 objects, complete the following procedure:
Step 1 When Dsx 3 has been selected, the configurable categories for this line type are displayed.
The following categories are
•Physical Line Configuration (dsx3)
•Physical Line Alarm Configuration (dsx3)
Step 2 Click the drop-down arrow for the Physical Line Config (dsx 3) category to display its objects as shown in Figure 3-31.
Figure 3-31 Physical Line Config (dsx3) Objects
The Physical Line Configuration (dsx3) objects are described in Table 3-21.
Table 3-21 Physical Line Config (dsx3) Objects
Object
|
Description
|
Line No.
|
Line number.
|
Line Enable
|
Turns a line signal on or off with the enable or disable settings. Use modify to change the object setting of a line that has already been enabled.
Note Before you can change any objects for a line, you must set this object to modify.
|
Line Type
|
Line type. Choose one from the popup menu:
•dsx3CbitParity
•g832-g804
•dsx3M23
•g751
•dsx3Unframed
•e3Unframed
|
Line Coding
|
Line coding. Can be dsx3B3ZS or e3HDB3.
|
Line Length (Feet)
|
Line length. Choose lessThan225 or moreThan225 from the popup menu.
|
Line OOF Criteria
|
Line OOF decision criteria. Can be fBits30f8 or fBits3Of16.
|
Line check AIS Bits
|
Choose checkCbits or ignorebits from the popup menu.
If checkCbits, AIS is declared when 1010 pattern is found and C-bits are all zero. If ignorebits, an AIS condition is declared when the AIS pattern 1010 is detected, regardless of the state of the C-bits.
|
Line Loopback Command
|
Loopback configuration of the DS3/E3 interface. Choose one from the popup menu:
•dsx3NoLoop
•dsx3RemoteLineLoop
•dsx3LocalLineLoop
•dsx3InbndLocalLoopback
|
Line Receive FEAC Validation
|
FEAC1 code validation criteria.
Choose fFEACCodes4Of5 or fFEACCodes8Of10 from the popup menu.
If FEACCodes4Of5 is specified, a valid FEAC codes is declared if four of five codes match. If fFEACCodes8Of10 is specified, a valid FEAC code is declared when eight of ten codes match.
|
Line Transmit FEAC Code
|
Indicates the bit-oriented code to transmit over the FEAC channel. Choose one from the popup menu:
•dsx3SendNoCode
•dsx3SendLineCode
•dsx3SendLineCode
•dsx3SendPayLoadCode
•dsx3SendResetCode
•dsx3SendDS1LoopCode
•dsx3SendSendTestPattern
|
Line XMT Clock Src
|
Line transmit clock source. Choose one from the popup menu:
•backplaneClk
•recoverClk
•localClk
|
Far End Loopback Status
|
Bitmap of the dsx3 FarEnd line loopback status bits.
|
Line Equalizer
|
Determines type of line equalizer. Choose one from the popup menu:
•intrnlequalizer
•extequalizer
|
Step 3 To configure Physical Line objects, change their values as necessary. Click Apply.
Step 4 When all the objects are correctly configured, click OK.
Step 5 Choose the Physical Line Alarm category to display its objects as shown in Figure 3-30.
Figure 3-32 Physical Line Alarm Config (dsx3) Objects
Details of these objects are described in Table 3-22.
Table 3-22 Physical Line Alarm Config (dsx3) Objects
Object
|
Description
|
Line Alarm State
|
Status of the line alarm. A value of zero indicates no alarms.
|
Line Statistical Alarm State
|
Status of the line statistical alarms. A value of zero indicates no alarms.
|
Red Severity
|
Used to set up the severity of RED alarm. When an LOS/LOF alarm is detected, the device sends the alarm with the appropriate alarm status. Can be minor or major.
|
RAI Severity
|
Used to set up the severity of RAI alarm. When the RAI alarm is detected, the device sends the alarm with the appropriate alarm status. Can be minor or major.
|
Near End Alarm Up Count
|
Specifies the increment to the near-end alarm integration counters. The local alarms are LOS and LOF. The default is 6, and the integration counter is incremented by this value every 10 ms when the alarm persists. The counter is decremented by the value of Near End Alarm Down Count while there is no alarm (the counter does not decrement below zero). When the integration counter exceeds dsx3NEAlarmThreshold, an alarm of the severity specified for the particular NE alarm is declared.
|
Near End Alarm Down Count
|
Specifies the decrement to the near-end alarm integration counters. The local alarms are LOS and LOF. The default is 1, and the integration counter is decremented by this value every 10 ms while no alarm persists. The counter is incremented by the value of Near End Alarm Up Count while there is no alarm (the counter does not decrement below zero). When the integration counter reaches zero, any alarm previously declared is removed.
|
Near End Alarm Threshold
|
Determines the value that the alarm integration counter must reach for a near-end alarm to be declared. If the up count is 6, the down count is 1, and the threshold is 1500, an alarm is integrated in 2.5 sec and removed in 15 sec.
|
Far End Alarm Up Count
|
Determines the value that the alarm integration counter must reach for a far-end alarm to be declared. If the up count is 6, the down count is 1, and the threshold is 1500, an alarm is integrated in 2.5 seconds and removed in 15 sec.
|
Far End Alarm Down Count
|
Specifies the decrement to the far-end alarm integration counters. The local alarms are RAI and AIS. The default is 1, and the integration counter is decremented by this value every 10 ms while no alarm persists. The counter is incremented by the value of Far End Alarm Up Count while there is no alarm (the counter does not decrement below zero). When the integration counter decrements to zero, any previously declared alarm is removed.
|
Far End Alarm Threshold
|
Determines the value that the alarm integration counter must reach for a far-end alarm to be declared. If the up count is 6, the down count is 1, and the threshold is 1500, an alarm is integrated in 2.5 sec and removed in 15 sec.
|
Statistical Alarm Severity
|
Used to set up the severity of any of the statistical alarms. When a statistical counter exceeds its specified threshold, the device sends the alarm with the appropriate severity. Can be minor or major.
|
Step 6 To configure Physical Line Alarm objects, change their values as necessary. Click Apply.
Step 7 When all the objects are correctly configured, click OK.
Step 8 Choose the Logical Port Config (CESM Ports) category to display it objects as shown in Figure 3-33.
Figure 3-33 Logical Port Config (CESM Ports) Objects
Details of these objects are described in Table 3-23.
Table 3-23 Logical Port Config (CESM Ports) Objects
Object
|
Description
|
cesPortNum
|
Logical port number.
|
cesPortRowStatus
|
Used to enable, delete, or modify the port. Choose one from the popup menu:
•add
•del
•mod
|
cesPortLineNum
|
Line number.
|
cesPortType
|
Port type. The applicable setting for this card is unstructured.
|
cesPort Ds0 Config
|
Bitmap of DS0s for a line, used to form this logical port. Bit 0 represents DS0-1.
|
cesPortNum of Ds0 Time Slots Configured
|
Number of DS0 time slots configured to this port. If Port Type is "strau," this cannot have more than one DS0 time slot.
|
cesPortNumOfSciPerDS0Slot
|
Number of subcircuits in the DS0 time slot (for strau port types only).
|
Port Speed (Kbps)
|
Port speed in kbps.
|
Step 9 To configure Logical Port Config objects, change their values as necessary. Click Apply.
Step 10 When all the objects are correctly configured, click OK.
Configuring a CESM Port
To configure a CESM port, use the following procedure.
Step 1 Using the front view of the shelf, right-click the CESM port to be configured.
Step 2 Click Configure in the resulting popup menu.
Step 3 Click the Category drop-down arrow to display the available CESM categories. These categories are:
•Card
•Service Module Features
•Ports
•Channels
The Card and Service Module Features categories are for informational purposes only and cannot be configured. Preparing for a CESM connection involves first configuring the port and then configuring the channels.
Step 4 Choose the Ports category to display its objects as shown in Figure 3-34.
Figure 3-34 CESM Port Objects
Details of these objects are described in Table 3-24.
Table 3-24 CESM Port Objects
Object
|
Description
|
cesPortNum
|
Logical port number.
Note For T3, only one port is supported.
|
cesPortRowStatus
|
Used to enable, delete, or modify the port. Choose one from the popup menu:
•add
•del
•mod
|
cesLineNum
|
Represents the line number to which this port is associated.
Note For T3 only one line is supported.
|
cesPortType
|
Represents the port type. Choose one from the popup menu:
•structured
•unstructured
•framingOnVcDisconnect
Note An unstructured port allocates all the time slots to framingOnVcDisconnect. T3 card will support only framingOnVcDisconnect.
|
cesPortDs0Config
|
Represents bit map of DS0s for a line. These DS0s are used to form this logical port. Bit 0 represents DS0-1.
|
PortNum of Ds0 Time Slots Configured
|
Number of DS0 time slots configured to this port.
|
PortNumOfSciPerDS0
|
Number of subcircuits in the DS0 time slot.
|
Port Speed (Kbps)
|
Port speed in kbps:
•Max speed for T1—1544
•Max speed for E1—2038
•Max speed for T3—44736
•Max speed for E3—34368
|
Port State
|
Logical port state. Can be
•notConfigured
•active
•remoteLoopback
•failedDueToLine
•failedDueToSignalling
•inactive
•inBert
•farEndRemoteLoopback
|
Step 5 To configure CESM Port objects, change their values as necessary, click Apply.
Step 6 When all the objects are correctly configured, click OK.
Configuring a CESM Channel
Perform the following steps to configure a CESM channel.
Step 1 Using the front view of the shelf, right- click the CESM card to be configured.
Step 2 Click Configure in the resulting popup menu.
Step 3 Click the Category drop-down arrow to display the available CESM categories.
The following categories are
•Card
•Service Module Features
•Ports
•Channels
The Card and Service Module Features categories are for informational purposes only and cannot be configured. Preparing for a CESM connection involves first configuring the port and then configuring the channels.
Step 4 Choose the Channels category to display its objects as shown in Figure 3-35.
Figure 3-35 CESM Channel Category
Details of these objects are shown in Table 3-25.
Table 3-25 CESM Card/Channels Table Objects
Object
|
Description
|
cescnfChanNum
|
Virtual connection number.
|
cesChannelRowStatus
|
Channel row status.
Note Choose modify to change the object values for a channel.
|
Channel Associated to Port
|
Specifies the port number.
|
MapVpi
|
Value of this object is equal to the VPI used for the emulated circuit represented by this connection.
|
MapVci
|
Specifies the VCI for emulated circuit represented by this VC (voice channel).
In case of CESM-8P, valid range is 32-279. In case of CESM-T3/E3, the valid value is 32.
|
Type Supported By CBR Service
|
Specifies data type supported by the CBR service. Choose unstructured or structured from the popup menu.
Note CESM-8P supports both structured and unstructured mode for T1/E1, but supports only unstructured for T3/E3. CESM-T3 supports only unstructured.
|
CBR Clock Mode
|
Clocking mode of the CBR service. Choose one from the popup menu:
•synchronous
•srts
•adaptive
CESM -T3 supports only synchronous.
|
Whether CAS bits are Carried
|
Specifies if CAS bits are carried by the service. Choose one from the popup menu:
•basic
•e1Cas
•ds1SfCas
•ds1EsfCas
•ccs
Note In CESM-8T1/E1, all channels on a line should have the same value. In T3/E3, only basic will be supported.
|
No. User Octets per Cell
|
Number of user octets per cell, if partial cell fill used.
•0 means partial fill disabled.
•Partial fill will not be supported in unstructured mode.
•Partial fill should be grater than or equal to 20 for CESM-8E1.
•Partial fill should be greater than or equal to 25 for CESM-8T1.
|
Buf Max.Size
|
Maximum size in octets of egress buffer.
In CESM-8T1/E1 and CESM-T3/E3 the maximum buffer size in octets should be at least twice the CDVRxT value. In CESM-8 the MaxBufsize range is as follows:
•T1 structured—9216 bytes
•T1 unstructured—16384 bytes
•E1 structured/unstructured—16384 bytes
•T3/E3 unstructured—16384 bytes
|
Max Cell Delay Variation
|
Maximum cell arrival jitter that the reassembly process will tolerate. Can be one of the following values.
•T1—24 ms.
•E1—32 ms.
•T3—1.5 ms.
•E3—2 ms.
Default values in CESM-8T1/E1 and CESM-T3/E3 are as follows:
•T1 and E1—8000 microsecs.
•T3 and E3—1000 microsecs.
|
Cell Loss Integration Period (Milli secs)
|
Cell loss integration period in ms.
|
cesChanLocRmtLpbkState
|
State of the loopback on cell bus in egress direction. Choose enable or disable.
|
Channel TestType
|
The channel type of test. Choose one from the popup menu:
•testcon—Test continuity
•testdelay—Test delay
•notest—No test is initiated
•testconsti—Test continuity with STI cell format
•testdelaysti—Test delay with STI cell format
|
Channel Test State
|
State of the test. Can be one of the following results.
•passed
•failed
•inprogress
•notinprogress
|
Round Trip Delay (Milli. Secs)
|
Round trip delay in ms.
|
Clear Channel Counters
|
Clears the all counters on the card.
|
Step 5 To configure CESM Channel objects, change their values as necessary. Click Apply.
When all the objects are correctly configured, click OK.
Configuring CESM Card Redundancy
A description of the general procedure for configuring card redundancy is included in the next section of this chapter.
Configuring Card Redundancy
Setting up card redundancy is performed at the shelf level using the following procedure.
Step 1 Display the front view of the shelf for card redundancy to be configured.
Step 2 Right-click the dark area of the node above the cards. This displays the node menu.
Step 3 Click Configure, to display the categories screen for the shelf.
Step 4 Click the Category drop-down arrow to display the available categories. Click Redundancy Info.
The Redundancy Info objects window displays redundancy information for all the cards in the node
(see Figure 3-36).
Figure 3-36 Redundancy Info Objects
The objects are described in Table 3-26.
Table 3-26 Redundancy Info Objects
Object
|
Description
|
PrimarySlot
|
Slot Number of the Primary module that is plugged in.
|
PrimaryState
|
Current State of the Primary module.
|
SecondarySlot
|
Slot Number of the Secondary module that is plugged in.
|
Secondary State
|
Current State of the Secondary module.
|
Redundancy Type
|
Type of redundancy used on the primary module. Can be yCable or 1:N.
|
Covering Slot
|
Slot number of the Primary module covered by the secondary module.
|
Create Redundancy
To create a redundancy on a card, perform the following steps:
Step 1 Click Create in the Redundancy Info screen. The Row Creation window appears (see Figure 3-37).
Figure 3-37 Redundancy Row Creation Window
Step 2 Enter the object values for the primary and secondary slots and the type of redundancy (Ycable or 1:n). Click OK.
