Version

Appendix B

Virtual Port Configuration Utility

Introduction

Text Configuration File Creation

: Bus Timing
: Configuration Line Syntax

NETWORK T1/E1

: T1/E1 Configuration Options
: Command Line Syntax

Resource Definition Entry

: Command Line Syntax
: Ethernet Connection
: Serial Connection
: TDM Connection

Virtual Port Definition Entry

: Command Line Syntax

Introduction

The Virtual Port configuration utility is used to set the default MVIP and T1/E1 configuration of a TX board with MVIP and/or T1/E1 adapters. This utility is also used to define data channel timeslot assignments from the MVIP or T1/E1 interfaces.
Data channel configuration is controlled by creating a configuration file that is downloaded to the TX board KERNEL when the board is loaded. Note: Each TX board must have its own separate Virtual Port configuration file.
Once data channels are defined in the configuration file and downloaded to the TX board, other NMS communication software products, such as the TelePathX (TPX) TCP/IP Router/Gateway and the SS7 Protocol Stack, may be configured to utilize these channels as communication ports.

Text Configuration File Creation

A text file (the vpdcfg.txt file) is prepared containing a description of the MVIP timing and T1/E1 base configuration, followed by resource definitions (timeslot assignments) and virtual port definitions (application interface to resources). Each resource is assigned a TDM stream, first timeslot, number of timeslots used, and the direction (described in the following section). Example 1 shows a sample vpdcfg.txt file. Individual configuration fields are described in more detail.

Bus Timing

The bus timing entry describes the clocking configuration for the MVIP bus adapter interface. Two timing entries are specified: main clocking and Sec8K clocking.

Configuration Line Syntax

CLOCK:<main mode> SEC8K:<sec8k mode> [<network>]
<main mode> Specifies the mode for the main MVIP bus clock signals (/C4, /F0, C2). Possible values are:

BUS

The TX board MVIP adapter gets its timing signals from the MVIP bus [the DEFAULT].

MASTER

The TX board MVIP adapter drives the MVIP bus clock signals from its internal clock.

SEC8K

The TX board MVIP adapter drives the MVIP bus clock signals using the MVIP bus SEC8K signal as the clock reference input.

NET

The TX board MVIP adapter drives the MVIP bus clock signals using T1/E1 adapter interface (A or B)'s [see NETWORK] 8KHz clock signal as the clock reference input.


<sec8k mode> Specifies the mode for the MVIP bus secondary 8KHz reference signal. Possible values are:

MASTER

The TX board MVIP adapter drives the SEC8K signal from its internal clock.

NET

The TX board MVIP adapter drives the SEC8K signal from T1/E1 adapter interface (A or B)'s [see NETWORK] 8KHz clock signal.

NONE

The TX board MVIP does not output the SEC8K signal to the MVIP bus.

BUS	The TX board MVIP adapter gets its timing signals from the MVIP bus [the DEFAULT].
MASTER	The TX board MVIP adapter drives the MVIP bus clock signals from its internal clock.
SEC8K	The TX board MVIP adapter drives the MVIP bus clock signals using the MVIP bus SEC8K signal as the clock reference input.
NET	The TX board MVIP adapter drives the MVIP bus clock signals using T1/E1 adapter interface (A or B)'s [see NETWORK] 8KHz clock signal as the clock reference input.

MASTER	The TX board MVIP adapter drives the SEC8K signal from its internal clock.
NET	The TX board MVIP adapter drives the SEC8K signal from T1/E1 adapter interface (A or B)'s [see NETWORK] 8KHz clock signal.
NONE	The TX board MVIP does not output the SEC8K signal to the MVIP bus.

NETWORK T1/E1

If NET is specified for either CLOCK or SEC8K, a NETWORK T1/E1 identifier is required. Possible values are:

A

The TX board MVIP adapter drives the CLOCK or SEC8K signal (whichever defined as NET) from T1/E1 adapter interface A's clock signal.

B

The TX board MVIP adapter drives the CLOCK or SEC8K signal (whichever defined as NET) from T1/E1 adapter interface B's clock signal.

A	The TX board MVIP adapter drives the CLOCK or SEC8K signal (whichever defined as NET) from T1/E1 adapter interface A's clock signal.
B	The TX board MVIP adapter drives the CLOCK or SEC8K signal (whichever defined as NET) from T1/E1 adapter interface B's clock signal.

T1/E1 Configuration Options

The T1/E1 configuration line consists of an identifier indicating which T1/E1 circuit (A or B) is being configured, followed by parameters specifying the framing, line encoding, line buildout (T1 only), robbed bit signaling, and loop master (timing source) configuration for this circuit.

Command Line Syntax

<T1/E1> <framing> <encoding> <buildout> <robbed bit> <loop master>
<T1/E1> Indicates the adapter interface being configured. Possible values are:

T1A

T1 adapter A is being configured.

T1B

T1 adapter B is being configured.

E1A

E1 adapter A is being configured.

E1B

E1 adapter B is being configured.
<framing> Determines the framing format to be used for this
circuit. Possible values are: NONE Do not configure this T1/E1 circuit. D4 [T1] D4 (193S) framing. ESF [T1] Extended superframe format. CCS [E1] Frame alignment only (no multiframe alignment). CAS [E1] Standard frame alignment with channel associated signaling (timeslot 16) multiframe alignment (but no CRC4). CCSCRC [E1] Standard frame alignment with CRC4 multiframe alignment (but no CAS). CASCRC [E1] Standard frame alignment with both channel associated signaling (timeslot 16) and CRC4 multiframe alignment.

<encoding> Determines line encoding and zero suppression
mechanism to be used for this circuit.
Possible values are: NONE NOZCS [T1|E1] AMI encoding with no zero code suppression. B7ZS [T1] Bit Seven Zero Stuffing. B8ZS [T1] Bipolar Eight Zero Substitution. HDB3 [E1] High Density Bipolar (order 3) encoding.
<buildout> Determines line buildout to be used for this circuit.
Possible values are: Value T1 E1 0 0-133 Feet. 1 133-266 Feet. 120 Ohm Normal 2 266-399 Feet. 3 399-533 Feet. 120 Ohm with Protection Resistors [Default] 4 533-655 Feet. 5 120 Ohm with 14dB Return Loss 7 Ohm with 27dB Return Loss

<robbed bit> A flag (set to TRUE or FALSE), indicating whether
robbed bit signaling is used by the TX board on this
circuit [T1 only - ignored for E1 circuits].
<loop master> A flag (set to TRUE or FALSE), indicating whether this
interface is the master of loop timing for this circuit.

T1A	T1 adapter A is being configured.
T1B	T1 adapter B is being configured.
E1A	E1 adapter A is being configured.
E1B	E1 adapter B is being configured.

NONE		Do not configure this T1/E1 circuit.
D4	[T1]	D4 (193S) framing.
ESF	[T1]	Extended superframe format.
CCS	[E1]	Frame alignment only (no multiframe alignment).
CAS	[E1]	Standard frame alignment with channel associated signaling (timeslot 16) multiframe alignment (but no CRC4).
CCSCRC	[E1]	Standard frame alignment with CRC4 multiframe alignment (but no CAS).
CASCRC	[E1]	Standard frame alignment with both channel associated signaling (timeslot 16) and CRC4 multiframe alignment.

NONE
NOZCS	[T1\|E1]	AMI encoding with no zero code suppression.
B7ZS	[T1]	Bit Seven Zero Stuffing.
B8ZS	[T1]	Bipolar Eight Zero Substitution.
HDB3	[E1]	High Density Bipolar (order 3) encoding.

Value	T1	E1
0	0-133 Feet.
1	133-266 Feet.	120 Ohm Normal
2	266-399 Feet.
3	399-533 Feet.	120 Ohm with Protection Resistors [Default]
4	533-655 Feet.
5		120 Ohm with 14dB Return Loss
7		Ohm with 27dB Return Loss

Resource Definition Entry

The resource definition entry describes the characteristics of each data channel. The resource number identifies the resource for future virtual port assignments.
If a resource number is indicated that already exists (either due to initial TX board KERNEL setup or previous vpdcfg entry), that resource is re-defined (as long as resource is not currently in use). If the communications channel referenced by a resource definition is already described by a different resource number, the old resource definition is removed (if not in use) allowing the new resource definition to take over.
The TX board KERNEL assigns resources from a base resource number of 256, leaving the range from 1..255 available for definitions from vpdcfg.txt (without the possibility of re-mapping a KERNEL-defined resource).

Command Line Syntax

RES <res #> SCC <hw #> [SHARED] <prot> <rxfrm> <conn> [<conn-specific params>]
<res #> Defines a numeric handle that uniquely identifies the resource. As previously described, overlapping of resource numbers is not allowed. If a resource overlap is detected, the older resource is removed (if not in use), or the new resource definition will fail.
<hw #> Identifies the particular hardware channel number that the resource is defining. The hardware number is specific to the type of hardware being described (previous field [e.g. SCC]).

For TDM,SERIAL, and ETH (Ethernet) resources, the hardware type is always SCC (serial communication controller). The possible hardware numbers are determined by the daughter board configuration on the TX board. The following table shows the hardware number assignments based on daughter board configurations: Ethernet | 4th Serial Tri-Port Slave 360 SCC Hardware Number Availability NO NO NO 1..4 assigned as TDM channels YES NO NO 1 assigned as ETH (or SERIAL) channel 2..4 assigned as TDM channels NO NO YES 1..8 assigned as TDM channels YES YES NO 1 assigned as ETH (or SERIAL) channel 2..4 assigned as SERIAL channels YES NO YES 1 assigned as ETH (or SERIAL) channel 2..8 assigned as TDM channels NO YES YES 1 assigned as TDM channel 2..4 assigned as SERIAL channels 5..8 assigned as TDM channels YES YES YES 1 assigned as ETH (or SERIAL) channel 2..4 assigned as SERIAL channels 5..8 assigned as TDM channels
When a 360 on the TX board is operating in QUICC-32 mode, a different scheme is used for hardware number. In this case, a zero should be specified for hardware number. The communication processor KERNEL interprets the definition as a QUICC-32 resource and assigns the timeslot(s) to the next available QUICC-32 channel slot. This method allows operators to define QUICC-32 configurations without requiring a knowledge of the KERNEL's internal assignment system. Each 360 in QUICC-32 mode can support 32 64Kb timeslots. These can each be a separate resource, or these timeslots can be combined into hyperchannels. The maximum size of a QUICC-32 hyperchannel is 1 megabit (16 timeslots). There can be two of these hyperchannels on a single QUICC32 360.
By specifying SHARED, the resource is configured to allow multiple virtual ports to share the resource, allowing multiple TX board applications to transmit data over the same channel. The definitions of the virtual ports that are sharing a given resource provide an address mapping definition that is used to demultiplex data received over the channel (see Virtual Port Definition Entry).
If SHARED is not specified, the resource defines a channel that does not support virtual port demultiplexing.
<prot> Determines the protocol that will be passing over the
channel. Possible values are: Protocol SHARED allowed Description ETH YES Ethernet frames expected on channel. Demultiplexing based on DIX Ethernet type field (e.g. 800 [IP]; 806 [ARP] ). HDLC YES HDLC frames expected on channel. Demultiplexing based on HDLC address byte. SS7 NO Signaling System 7 frames expected on channel. ASY NO Async protocol expected on channel.

<rxfrm> Determines the maximum frame size for any frame
received over the channel. This value can range from
64 to 4096 bytes.
<conn> Indicates the type of connection represented by the
resource and determines what connection-specific
parameters are expected for the rest of the resource
definition. Possible values are:

ETH

Ethernet connection (see details)

SERIAL

Physical serial connection (see details)

TDM

Time division multiplex connection (see details)

Ethernet \| 4th Serial	Tri-Port	Slave 360	SCC Hardware Number Availability
NO	NO	NO	1..4 assigned as TDM channels
YES	NO	NO	1 assigned as ETH (or SERIAL) channel 2..4 assigned as TDM channels
NO	NO	YES	1..8 assigned as TDM channels
YES	YES	NO	1 assigned as ETH (or SERIAL) channel 2..4 assigned as SERIAL channels
YES	NO	YES	1 assigned as ETH (or SERIAL) channel 2..8 assigned as TDM channels
NO	YES	YES	1 assigned as TDM channel 2..4 assigned as SERIAL channels 5..8 assigned as TDM channels
YES	YES	YES	1 assigned as ETH (or SERIAL) channel 2..4 assigned as SERIAL channels 5..8 assigned as TDM channels

Protocol	SHARED allowed	Description
ETH	YES	Ethernet frames expected on channel. Demultiplexing based on DIX Ethernet type field (e.g. 800 [IP]; 806 [ARP] ).
HDLC	YES	HDLC frames expected on channel. Demultiplexing based on HDLC address byte.
SS7	NO	Signaling System 7 frames expected on channel.
ASY	NO	Async protocol expected on channel.

ETH	Ethernet connection (see details)
SERIAL	Physical serial connection (see details)
TDM	Time division multiplex connection (see details)

Ethernet Connection

ETH indicates an Ethernet connection.
No other parameters are required for an Ethernet connection. The TX board KERNEL loads its Ethernet hardware address from its EEPROM. Note: Ethernet connection type is only supported on serial communication controller 1 (SCC 1).

Serial Connection

SERIAL <baud> [IDLEFL] indicates a physical serial connection. This connection is assigned to serial communication controllers for the tri-port and 4th-serial daughter cards.
<baud> Specifies the baud rate for the connection.
IDLEFL Causes the idle in flags option to be enabled.

Serial connections are limited to serial communication controllers 1..4.

TDM Connection

TDM <st>:<ts>[..<tsend> | /56] indicates a time division multiplexed connection. This connection is used for all channels passing over MVIP and/or T1/E1. See the SCC (serial communication controller) Hardware Number Assignment chart for a breakdown of the serial communication controller hardware numbers that TDM connections are allowed over.
<st> Identifies the MVIP or T1/E1 stream that this channel occupies, where stream n in the range {0..7} selects MVIP streams DSon/DSin, n = 16 selects T1/E1 interface A, and n = 18 selects T1/E1 interface B.
<ts> Identifies the starting timeslot (0-23 for T1, 0-31 for E1 or MVIP) for the channel.
Note: For E1, channel 0 is always used for framing and cannot be used as a data channel. In addition, if the line is configured for channel associated signaling (CAS) then channel 16 is dedicated to signaling and is also unavailable for use as a data channel.
..<tsend> Optionally identifies the ending timeslot for a hyperchannel. If this parameter is not specified, a single timeslot resource is created.
The maximum hyperchannel timeslot range is 24 for T1; 32 for E1 or MVIP.
/56 Optionally identifies the single timeslot as employing the 56 Kbps subrate.

Virtual Port Definition Entry

The virtual port definition entry provides access to a resource. If a resource is SHARED, multiple virtual ports can be assigned to the resource. The demultiplex address set is used to enable the resource handler to route received frames. If a resource is NOT SHARED, only a single virtual port can be associated with the resource.

Command Line Syntax

VPORT <vport #> RES <res #> <prio> [<flags>] <addrs>
<vport #> Provides a numeric handle that uniquely identifies the
given virtual port. TX board applications are
configured to access this virtual port number. Since all
connection control is defined by the resource, an
application needs only the virtual port number to allow
the application to attach.
<res #> Identifies the resource that the virtual port is associated
with. The resource must exist at the time that the
virtual port definition is made.
<prio> Specifies the priority of the given virtual port in
relation to all other virtual ports that are sharing the
same resource. Possible values are:

H

High priority.
The routing of received frames gives highest priority to virtual ports in this category.

M

Medium priority.

L

Low priority.
Virtual port is arranged in routing table such that other virtual ports have the best routing path. Use for background operations.
<flags> Provide optional control of the virtual port behavior.
OW - Indicates that the resource manager overwrites the address byte in outbound frames with the first address specified in the demultiplex address set. This is useful for allowing applications to take advantage of virtual ports without requiring the application to know what address it has been assigned.
<addrs> List 1..4 addresses that the virtual port will receive frames for. The resource manager uses this address set when any frame is received. If the address field (determined by protocol) matches any in the given virtual port address set, the owner of that virtual port is notified.

H	High priority. The routing of received frames gives highest priority to virtual ports in this category.
M	Medium priority.
L	Low priority. Virtual port is arranged in routing table such that other virtual ports have the best routing path. Use for background operations.

Version

Want to send us feedback on our documentation? Email: Tech_Pubs@nmss.com