3Com 3C8S5007 - SuperStack II PathBuilder S500..., User Manual

Page: 158 / 190

158 A
PPENDIX
G: C
OMPLETING
T
HE
U
LTRA
-WAN C
ONFIGURATION
# shown below. Note that the ADD command is used to add
# back channels.
# ChannelBaud: This parameter specifies the baud rate (56K or 64K) of
# each timeslot (i.e. channel) mapped to the
# specified path. Default setting is CB64K (64kbits/sec).
# This setting can be changed to CB56K (56kbits/sec) for
# leased-line paths that require 56kbit/sec operation
#
# Some examples on using these commands are as follows:
#
# DELete !T1FATPA -PAth ChannelMap 1,2,3,7,12,23
# ADD !T1FATPA -PAth ChannelMap 1,2,3,7,12,23
# SETDefault !T1FATPA -PAth ChannelBaud = CB56K
# Enable Connectors
SETDefault !T1FAT -PAth ConnControl = Enable
# Assign all timeslots to the connectors
ADD !T1FATPA -PA ChannelMap 1, 2, 3, 4, 5, 6, 7, 8, 9,10
ADD !T1FATPA -PA ChannelMap 11,12,13,14,15,16,17,18,19,20
ADD !T1FATPA -PA ChannelMap 21,22,23,24
SETDefault !T1FATPA -PAth Control = Enable
Example 11.
########################################################################
########################################################################
# ULTRAWAN CONNECTOR CONFIGURATION FILE
# T1 PRI TEMPLATE
# HOW TO CONFIGURE MULTIPLE CONNECTORS SIMULTANEOUSLY
# This example shows how to configure connectors 4A, 4B, 4C, and 4D
# simultaneously by creating an instance group of connectors via the
# Instance Group command. To specify which connectors are
# included in this grouping, just add or delete the according references
# in the Instance Group command. For example, to include only connectors
# 4A and 4C, the command would look like the following:
# Add -SYS InstanceGRoup T1PRI "!4A, !4C" PAth
# Add Instance Group to cover all 4 UltraWAN connectors
###### Note: T1PRI is short for T1, PRI dial
Add -SYS InstanceGroup T1PRI "!4A , !4B , !4C , !4D " PAth
# Connector-level path parameter configuration
# The following parameter settings are only typical example settings.
# Your network-specific settings need to be assigned by consulting the
# connector-level path parameter documentation in the document
# "Using the PathBuilder Switch"