# Defining a board's switch

Each board in the system that connects to a telephony bus must have a switch definition in the switch fabric. A section defining a particular board starts with a Switch n statement and ends with an End Switch statement.

Fabric
# bus definitions for the switch fabric
Switch 0
# switch 0 definition
End Switch
Switch 1
# switch 1 definition
End Switch
# switch connections
End Fabric

Statements inside a switch definition apply only to that particular board. Each board in the switch fabric must have a unique switch number assigned in the PPX configuration file. These switch numbers must all be unique. The numbers are arbitrary identifiers and are unrelated to the physical board configuration.

The switch-specific section for each board includes the following statements:

- Switch attributes, that describe the switch and the switching driver:

switch_attribute = value

- Telephony bus connection, that defines the bus connected to the switch on the board:

bus name ([bus_specification])

- Inputs and outputs for the board, that defines local resources, such as line interfaces and DSP resources:

Inputs
bus_specification | bus_declaration
End Inputs

The switch-specific region for a board must include the switch attributes, telephony bus connection, and local inputs and outputs.

This topic presents:

- Defining switch attributes

- Specifying the telephony bus

- Defining local resources

## Defining switch attributes

The switch attributes are:

- Switch type

- Switch driver name

- Device number of the board

- Initial switch state

The PPX service uses the switch type to determine the type of switch present on the board:

SwitchType = switch

Valid switch types include:

Switch type | Description
--- | ---
FMIC | Flexible MVIP interface circuit providing a complete enhanced MVIP-90 bus.
HMIC | H.100/MVIP integrated circuit, providing a complete interface to the CT Bus. Note: The HMIC designation is used here in a general sense; it actually represents different chips that implement the HMIC design, for example, the Lucent T8100 chip used on the AG 4000.

The switch driver name is specified by:

DeviceName = switch_driver

The device number is specified by:

DeviceNumber = board_number

The device number specified in the PPX configuration file is the board number assigned to the board. Refer to the NMS OAM System User's Manual for more information on board numbers.

The initial switch state is specified by:

SwitchState = [disabled | enabled]

The presence of SwitchState is optional. If it is not present, it is set to ENABLED by default. Use of this attribute is relevant to the presence of the Hot Swap service within the system. This attribute designates switches on boards that will be inserted into currently unpopulated CompactPCI slots.

The switch attributes for an AG 4040 board are shown in the following example of a PPX configuration file:

[PPX]
Fabric
Bus my_H100_bus # bus definition
CTBUS:0..31:0..127
End Bus
Switch 0 # assigned as switch 0
SwitchType = HMIC # the switch on the AG 4040 is an HMIC
DeviceName = "agsw" # AG board device driver - agsw
DeviceNumber = 1 # the logical board number assigned through OAM
# Bus declaration
# Board inputs
# Board outputs
End Switch
End Fabric

The valid device names (switch drivers) and switch types for NMS boards are shown in the following table:

Board | Device name | Switch type
--- | --- | ---
AG and CG boards | agsw | HMIC
QX 2000/100-4L | qxsw | HMIC
QX 2000/80-4L | qxsw | FMIC
CX 2000/C | cxsw | HMIC

The device number is the logical board number established with the NMS OAM board configuration.

## Specifying the telephony bus

The bus declaration statement specifies the telephony bus connection to the board:

Bus name ([bus_specification])

The bus name must have been previously defined in the bus definition section of the switch fabric.

For example, the H.100 bus is defined once and assigned the name my_H100_bus. my_H100_bus is used in the switch definitions for all boards connected to the H.100 bus.

[PPX]
Fabric
Bus my_H100_bus # H.100 bus definition
CTBUS:0..31:0..127
End Bus
Switch 0 # assigned as switch 0
DeviceName = "agsw" # AG board switch driver - agsw
DeviceNumber = 1 # the logical board number assigned through OAM
SwitchType = HMIC # the switch on the AG Quad is an HMIC
Bus my_H100_bus ( ) # AG 4040 is connected to H.100 bus
# Board inputs
# Board outputs
End Switch
End Fabric

The brackets following the bus name can include a range of timeslots
indicating that the board supports a subset of a defined bus.

In a mixed H.100 and MVIP-90 system (for example, a system with a QX 2000/100-4L and a QX 2000/80-4L) the bus definition includes all streams on the H.100 bus:

Bus my_H100_in_MVIP_mode
CTBUS:0..15:0..31 # streams clocked at 2 MHz, 32 timeslots
CTBUS:16..23:0..63 # streams clocked at 4 MHz, 64 timeslots
CTBUS:24..31:0..127 # streams clocked at 8 MHz, 128 timeslots
End Bus

A QX 2000/100-4L board can connect to all streams on the H.100 bus. In the switch definition for the QX 2000/100-4L board, the bus declaration is:

Bus my_H100_bus ()

The QX 2000/80-4L is an MVIP-90 board and can access only the first 16 streams. The switch definition for the QX 2000/80-4L includes a subset of the H.100 bus:

Bus my_H100_bus (CTBUS:0..15:0..31)

## Defining local resources

Resources such as network interfaces and DSP resources located on the local bus as inputs to the switch (for example, voice stream coming from the telephone network) are specified by:

Inputs
LOCAL:streams[(increment)]:timeslots
End Inputs

Resources located on the local bus as outputs from the switch (for example, voice stream going out to the telephone network) are specified by:

Outputs
LOCAL:streams[(increment)]:timeslots
End Outputs

Typically, local resources on a board are located on consecutive streams. By convention, inputs use even-numbered streams and outputs use odd-numbered streams.

For example, for an AG 4040 board using channel associated signaling, the local resources are:

Information | Local resources
--- | ---
Trunk voice | Trunk 1: Streams 0 (input) and 1 (output), timeslots 0..23 Trunk 2: Streams 4 (input) and 5 (output), timeslots 0..23 Trunk 3: Streams 8 (input) and 9 (output), timeslots 0..23 Trunk 4: Streams 12 (input) and 13 (output), timeslots 0..23
Trunk signaling | Trunk 1: Streams 2 (input) and 3 (output), timeslots 0..23 Trunk 2: Streams 6 (input) and 7 (output), timeslots 0..23 Trunk 3: Streams10 (input) and 11 (output), timeslots 0..23 Trunk 4: Streams 14 (input) and 15 (output), timeslots 0..23
DSP voice | Streams 16 (input) and 17 (output), timeslots 0..127
DSP signaling | Streams 18 (input) and 19 (output), timeslots 0..127

In the PPX configuration file for the AG 4040 board, these local resources are defined as:

[PPX]
Fabric
Bus my_H100_bus # H.100 bus definition
CTBUS:0..31:0..127
End Bus
Switch 0 # assigned as switch 0
DeviceName = "agsw" # AG board device driver - agsw
DeviceNumber = 1 # the logical board number assigned through OAM
SwitchType = HMIC # the switch on the AG 4040 is an HMIC
Bus my_H100_bus () # AG 4040 is connected to H.100 bus
Inputs
LOCAL:0..14(2):0..23 # trunk voice and signaling
LOCAL:16..18(2):0..127 # DSP voice and signaling
End Inputs
Outputs
LOCAL:1..15(2):0..23 # trunk voice and signaling
LOCAL:17..19(2):0..127 # DSP voice and signaling
End Outputs
End Switch
End Fabric