IPmux ws 4.00.ppt

1
Info Tools FAQ Database Animation Search
TDMoIP
Workshop
A step by step comprehensive guide for
the IPmux/Gmux product family

2
How to use the Slide Show?
This is an interactive slide-show which will guide you
through this workshop.
This presentation features an active button section (the
toolbar on the bottom side of the screen).
In this section you will find all the action buttons related to
the slide you are watching.
Very important:
The C icon stands for a recommendation to be
considered

3
Action Buttons
FAQ
Help !
Database
Animation
Search
Tools
Useful Tools
Special help Screens
Related FAQ’s
Browse the Work Shop
Learn more…
Animation
Navigation

4
Workshop navigation strategy
Main
Path/Road-
map
INFO
INFO
INFO
INFO
INFO
Browsing the interactive workshop only by pressing the Next and
Previous
buttons will keep you on the workshop main road-map, meaning
you will not miss any essential information needed in order to
complete the workshop tasks.
Whenever you decide to browse the workshop for more
information/queries (by pressing the special action buttons
below), you will be led to “Dead-End” sub-paths which will only
allow you to return to the main road without missing any
important slides.

5
General
The purpose of the slideshow guide is to help you successfully
complete
the “TDMoIP” workshop.
The workshop is “task oriented”. You will be asked to complete a
series
of tasks in order to run voice and data applications.
In some of the cases, the guide does not contain the complete
configuration procedures; you will have to find them on your own.
The following tools will help you complete the workshop tasks:
• The slideshow tool
• The booklet on your desk
• One of the trainers

6
Workshop Goals
A. Getting familiar with the TDMoIP concept and terms.
B. Learning the basic and advanced steps of configuration for Gmux,
IPmux-14 and the IPmux-14/SER.
C. Advanced configuration of new CES protocols such as
TDMoMPLS
and HDLCoIP.
D. Learning to use the IPmux in order to troubleshoot network
impairments.
E. Configuring the units via HyperTerminal and also via RADview
Service Center (TDMoIP) graphical interface.

7
Applications & Tasks – Main Application
HBT
ETX-202
Gmux-2000
192.168.100.200
IPmux-14/SER(1)
192.168.100.143
IPmux-14(2)
192.168.100.142
V.35
GbETH
ETH
ETH E1
NMS &
Sniffer
STM-1
TDMoMPLS
IPmux-14(1)
192.168.100.141
ETH E1
TDMoIP
HDLCoIP
E1
IPmux-14/SER(2)
192.168.100.144
V.35
ETH
HDLCoIP
HBT

8
Applications & Tasks – Troubleshooting Application
IPmux-14(1)
HBT
E1 ETH E1
TDMoIP
TDMoIP
IPmux-14(2)
HBT
Network Emulator
ETH

9
What will we do in the workshop?
1. Creating & Troubleshooting Point to Point Unframed TDMoIP
connection.
2. Creating Unframed Point to Point TDMoMPLS connection.
3. Creating Unframed Point to Point HDLCoIP connection.
4. BW occupation comparison: TDMoIP Vs. TDMoMPLS Vs.
HDLCoIP.
5. Creating fractional E1 connection using the Gmux-2000.
6. Creating an STM-1 connection using the Gmux via the Service
Center.
7. Troubleshooting IPmux connection running over network emulator.

10
Task 1
Task 1
Creating & Troubleshooting Point to Point
Unframed TDMoIP connection

11
Unframed E1 connection
In the opening task, you will be asked to configure a basic TDMoIP
Unframed Point-to-Point connection between the Gmux-2000 and the
IPmux-14(1) located on your desk, as shown below:
ETX-202
Gmux-2000
IPmux-14/SER(1)
IPmux-14(2)
V.35
GbETH
ETH
ETH E1
E1
NMS &
Sniffer
STM-1
IPmux-14(1)
ETH E1
TDMoIP
HBT HBT
IPmux-14/SER(2)
V.35
ETH

12
Task 1 – General Description
TDMoIP
CE
Server
1
Fan Tray
1
7
3
STM-1
OC-3
TDMoIP
CE
Ext E1/T1
Clocks
Local
Management
28-196
E1/T1
Ch. STM-1/
OC-3
AC/DC
AC/DC
Power Supply
AC/DC
Power Supply
AC/DC
Power
Inlet
GbE
Control
GbE
PSN I/F
Module
The Gmux is capable of
transmitting up to
196xE1/T1s over GbETH
uplink.
Database
C Reference: Gmux quick Config E1

13
Task 1 Detailed Description
The ETX-202, will be used as the L2 Switch connecting the different
IPmux/Gmux units throughout the entire workshop.
Task connections:
• Gmux to ETX-202 ETH NET1
• IPmux-14(1) to ETX-202 ETH User Port 3
ETX-202
GbETH
E1
IPmux-14(1)
ETH E1
TDMoIP
HBT HBT

14
Task 1 Detailed description
The Unframed E1 link will be created between the Gmux E1 port 1 on slot 1
(S1/P1) and the IPmux-14 E1 Port 1.
ETX-202
GbETH
E1
IPmux-14(1)
ETH E1
TDMoIP
HBT HBT
TDMoIP
Gmux

15
In this task, you will create an Unframed bundle, meaning the IPmux units
will be configured to transmit the entire E1 traffic over the ETH network while
handling the E1 as a 2.048Mbps bit stream.
In Unframed mode the IPmux is totally transparent to the contents of the E1,
transmitted by the HBT testers.
The HBT testers will be connected to:
•Gmux – E1 Slot 1/Port 1
•IPmux-14(1) – E1 port 1
ETX-202
GbETH
E1
IPmux-14(1)
ETH E1
TDMoIP
HBT HBT
TDMoIP
Gmux

16
The ETX-202 however will be rate limiting the ingress traffic on User-3, I.e.
rate limiting the traffic going from the IPmux-14(!) to the Gmux.
The Rate Limit allows only 3Mbps ETH traffic to go through User-3 port
towards the NET1 port.
You will have to consider this fact when setting the TDMoIP bundle
configuration.
ETX-202
GbETH
E1
IPmux-14(1)
ETH E1
TDMoIP
HBT HBT
Gmux-2000

17
Gmux-2000 Initial Setup
We will start by configuring the Gmux-2000 unit.
Use the Hyper Terminal program on the left hand screen to access the
device, set the baud rate for 115,200 and enter:
GMUX-2000
USER NAME: su
PASSWORD: 1234
Press <ESC> to
refresh screen

18
Setting up the HW Configuration
When powering on the Gmux for the first time, the first step will be to load
the device with its HW configuration, meaning recognizing the modules
installed into the chassis.
GMUX-2000
Config>Database tools
1
. Choose DB number[1 - 5] ... (1)
2
. Factory default
3
. Load database
4
. Load hardware
5
. Check sanity
6
. Update database
>
init db, upd db, load db, load hw...
V - view sanity log
ESC-prev.menu; !-main menu; &-exit; @-debug 1 Mngr/s
------------------------------------------------------------------------------
Path
1. Select: 4.Load Hardware
2. Press Y to confirm
3. Select: 6. Update Database
4. Verify the following
message appears: SANITY
OK. DB UPDATED.
C Saving and updating the Gmux Configuration
Info

19
Verifying HW Configuration
After loading the HW modules, verify that indeed all the modules were
recognized correctly by the device:
Path
GMUX-2000
Config>System>Card type
SLOT: PS-1 PS-2 PS-3 CL-1 CL-2
DB : PS-AC -------- -------- CL CL
SLOT: IO/1 IO/2 IO/3 IO/4 IO/5
DB : CES E1 Server E1 --------- --------- ---------
SLOT: IO/6 IO/7 IO/8 IO/9
DB : GBeth --------- --------- STM-2
1. ---------
2. PS-AC
3. PS-DC
FAQ
C Gmux power supply mechanism

20
Host IP & Manager List Configuration
Set the Gmux Host IP address which will be used for the bundle connectivity
and management:
Path
GMUX-2000
Config>System>Host IP
INTERFACE IP ADDRESS IP MASK DEFAULT GATEWAY
ONLINE CL: 0.0.0.0 0.0.0.0 0.0.0.0
GBETH 1/IF 1: 192.168.100.200 255.255.255.0 192.168.100.1
GBETH 1/IF 2: 0.0.0.0 0.0.0.0 0.0.0.0
1. Change cell ... (0.0.0.0)
Press S to save.

21
Manager List
In order to allow the Gmux to be managed via a remote management station
(the RADview Service Center), the NMS IP address should be added to the
manager list:
GMUX-2000
Config>System>Management>Manager list
MNG NUM[1 - 100] ... (1)
1. IP ADDRESS ... (192.168.100.254)
2. NETX HOP ... (0.0.0.0)
3. INTERFACE > (GIG A-IO 6/1)
4. TRAP(FOR MANAGER) (No)
5. VLAN VALID (No)
VLAN ID[0 - 4095] ... (0)
VLAN PRIORITY[0 - 7] ... (0)
1. Press A to add a manager
entry
2. Set the orange parameters
3. Select: 6. Save all

22
Setting Write Privilege
Set the write community to Public in order to be later allow parameters
change using SNMP:
Path
GMUX-2000
Config>System>Management>Authentication/Community
1. Trap community ... (public)
2. Read community ... (public)
3. Write community ... (public)
4. Authentication failure trap > (Off)
5. Save parameters

23
Gmux-2000 Physical Parameters Configuration
The application clocking configuration will be as follows:
The Gmux will be configured to provide the clock for the entire application.
In order to make sure all of its ports will be set for the same clock we will use
the system clock feature.
Internal
(Clock Source)
Adaptive
LBT LBT
ETX-202
GbETH
E1
IPmux-14(1)
ETH E1
TDMoIP
HBT HBT
Gmux-2000

24
Setting up the system clock
Verify that the default System clock mode is indeed Internal:
GMUX-2000
Config>System>Clock source>System A>Master clock
1. Master clock source > (Internal)
Path
C About the System clock feature
Info

25
I/O Settings
You will need to determine through which available GbETH interfaces the
bundles associated with a specific CE module will be transmitted:
GMUX-2000
Config>Physical layer
1. I/O[1 - 9] ... (1)
2. First GbEth IF ... (6/1)
3. Second GbEth IF ... (0/0)
4. Delete all slot's bundles
5. Disconnect all slot's bundles
6. Save slot parameters
Path

26
Gmux-2000 physical port setup
Path
At this point, you will need to configure the E1 port characteristics, such as
Line Type and Clock settings:
GMUX-2000
Config>Physical layer>E1 port - (IO 1: ETX PORT 1 CARD TYPE- CES E1)
1. Channel ID[1 - 28] ... (1)
2. Admin Status (Connected)
3. Idle code[0 - ff] ... (7E)
4. OOS Signaling > (Space)
5. OOS code[0 - ff] ... (FF)
6. Transmit clk source > (system a)
7. Rx Sensitivity > (Short Haul)
8. Bundle number[1 - 2000] ... (0)
9. TS type (NC)
10. Line type > (Unframed G.703)
11. Restoration Time > (CCITT)
12. Save parameters
C Unframed mode Vs. Framed mode
Info

27
Gmux - Creating Bundles
What is a BUNDLE?
The TDM traffic can be divided into bundles.
We take one or several time slots and call them a “BUNDLE”.
When using an E1/T1, the minimum time slots in a bundle is 1 and the
maximum is 32 for E1, or 24 for T1.
Each bundle containing a certain amount of TS gets a unique ID number.
In most IPmux units this ID can be selected by the User from the port’s
number ID pool. However this is not the case on the Gmux.

28
Bundle Connection Configuration Sequence
Unlike the regular IPmux configuration mode, connecting between bundles
and TDM interfaces is final configuration step.
Gmux configuration sequence would be:
1. Setting up the Host IP
2. Setting up the TDM interface characteristics
3. Setting up bundles
4. Connecting the TDM interface with a bundle

29
Bundle Numbers
The freedom to associate bundles to TDM ports means that now bundle ID
numbers are no longer associated with a specific port.
In the regular IPmux units, bundle ID are limited according to the related
port.
For example, on the IPmux-14, the Bundle ID range for E1 port#1 is: 1-32,
for E1port#2 its: 33-64 and so on.
On the Gmux the bundle ID numbers range is only used internally by the
device.

30
Gmux – Creating Bundles
In order to establish the TDMoIP connectivity between the Gmux and the
IPmux-14(1) we need to set the bundle connection parameters.
These parameters define the logical connection between the IPmux/Gmux
units, as shown below:
Path
GMUX-2000
Config>Connection - (BUNDLE 1)
1. Bundle ID[1 - 2000] ... (1)
2. Connection mode > (TDMoIP(CE))
3. PSN type (UDP/IP)
4. Connection configuration []>
5. Save parameters
1. Press X to add a bundle
2. Select: 5. Save parameters
3. Select: 4.Connection
Configuration
C Bundle bundle number concept
Info

31
Path
GMUX-2000
Config>Connection>Connection configuration - (BUNDLE 1)
Connection state Enable
Source CBID 1
Dest CBID 1
| Payload format V2
v TDM byte in frame(x48) 1
Jitter buffer in Ms[0-200] 3
OAM connectivity Enable
Payload type Data
| Far end type UNFRAMED
OOS L bit mode TX OOS and L bit
| Destination IP 192.168.100.141
v Network slot port 6/1
Next hop 0.0.0.0
IP TOS 0
Adaptive clock Disable
VLAN tagging Disable
Set the following Bundle connection parameters and Save:
C CBID concept
Info

32
Gmux – Connecting Bundle to TDM Interface
Path
Now we have a TDM port 1/slot 1 set for Unframed mode and a bundle
ID#1. Now you will need to associate the bundle with the TDM interface.
Please follow the below sequence:
GMUX-2000
Config>TS Assignment
1. Server ss/pp ... (1/1)
2. Assign entire port to bundle >
1. Make sure server card slot 1
port 1, is selected
2. Select: Assign entire port
to bundle

33
Path
GMUX-2000
Config>TS Assignment>Assign entire port to bundle
1. Bundle number[1 - 2000] ... (1)
2. Connect entire port to bundle
3. Disconnect entire port from bundle
1. Select the bundle number:
1
2. Select: 2. Connect entire
port to bundle
3. Wait for: OPERATION
PERFORMED message
4. Select: 4. Save port
assignment
5. Update the DB by
pressing: %
6. Confirm: SANITY OK. DB
UPDATED. Message.
7. The first bundle on the
Gmux is now created.

34
IPmux-14 Configuration
You have finished configuring the Gmux. In order to complete task 1,
configure the IPmux-14(1) at the opposite side:
USER NAME: su
PASSWORD: 1234
ESC - clear; & - exit 1 Mngr/s
-------------------------------------------------------------------------------

35
IPmux-14 Host IP Configuration
Set the Host IP Address for the IPmux-14:
Path Configuration>System>Host IP
1. IP address ... (192.168.100.141)
2. IP mask ... (255.255.255.0)
3. Default gateway ... (-)
4. DHCP (Disable)
Disable the DHCP option
and save before setting the
IP address and Mask

36
IPmux-14 Manager List Configuration
Set the NMS IP address under the device’s Manager List screen and save:
Configuration>System>Management>Manager list
1. Manager IP address ... (192.168.100.254)
2. Link up/down trap (Disable)
3. Alarm trap (Disable)
4. VLAN tagging (Disable)
>
Path

37
IPmux-14 E1 Physical Parameters
Configure the E1 Line Type and verify the correct clock settings:
Configuration>Physical layer>TDM configuration (E1)
Channel ID (1)
1. Admin status (Enable)
2. Transmit clock source > (Adaptive)
3. Trail mode (Termination)
5. Line interface (DSU)
>
Path
The Line Type must be set
according to the settings on
the Gmux – i.e. Unframed
G.703.
The Gmux was configured for
Internal CLK source. In order
to regenerate this CLK on the
IPmux-14 we need to use
Adaptive timing mode

38
IPmux-14 Time Slot allocation to bundles
Unlike the Gmux, the Time Slots are allocated automatically to the first
bundle of the port, when setting the port to work in Unframed mode.
On the IPmux-14, the bundle ID numbers pools are fixed and they are used
as the source bundles IDs of the device:
Port 2
Bundle ID
33-64
Port 1
Bundle ID
1-32
Port 3
Bundle ID
65-96 Port 4
Bundle ID
97-128

39
As mention in the previous slide, setting an Unframed mode for a specific
port disables the ability for manual TS allocation. Therefore the “DS0
bundle” option will not be presented for bundle ID 1.
Path Configuration>Connection
1. Bundle ID[1 - 127] ... (1)
2. Connection mode > (TDMoIP CE)
4. Bundle connection >
1. Select: 4. Bundle
connection

40
IPmux-14 Bundle Connection
You should now set the bundle connection parameters in order to connect it
to the bundle configured on the Gmux, and save:
Bundle connection
TDM channel ID: 1 Bundle ID: 1
1. Destination IP address ... (192.168.100.200)
2. Next hop ... (-)
3. IP TOS[0 - 255] ... (0)
4. Connection status (Enable)
5. Destination bundle[1 - 8063] ... (1)
6. TDM bytes in frame(x48 bytes)[1 - 30] ... (1)
7. Payload format (V2)
8. Far end type > (Unframed/serial)
9. OAM connectivity (Enable)
10. Jitter buffer [msec][0.5 - 200] ... (3.0)
11. Sensitive (Data)
12. OOS mode (Tx OOS)
The Destination bundle is the
Gmux Source CBID of bundle 1
C Payload format V2
Info

41
IPmux-14 – Verify Bundle Status
After you have finished configuring the bundle connection parameters on the
IPmux-14, therefore the bundle should be up and running.
How can you check the bundle connection status?
Monitoring>Status>Connection
Destination IP address: (192.168.100.200)
Next hop MAC address: (0020D2212C15)
Connectivity status: > (OK )
Sequence errors: (0)
Jitter buffer underflows: (0)
Jitter buffer overflows: (0)
1. Bundle ID[1 - 128] ... (1)
What is the connectivity
Status???
OK means that the bundle is up
Path
C Connectivity Status possible states
Info

42
Gmux – Verify Bundle Status
Now check the same monitoring on the Gmux:
What type of errors are present?
Reset the counters by pressing R, are the error counters still increasing?
GMUX-2000
Monitoring>Status>Connection>Bundle counters
1. Bundle ID[1 - 2000] ... (1)
Destination IP address ... (192.168.100.141)
Connectivity Status ... (OK)
Sequence Errors ... (326501)
Jitter buffer Underflows ... (10)
Jitter buffer Overflows ... (0)
Min Jitter buffer Level [Msec] ... (0)
Max Jitter buffer Level [Msec] ... (3)
Frames Tx to PSN ... (1317435)
Frames Rx from PSN ... (984390)
Path
Info
C What is a Sequence Error?

43
Testing – HBT functionality
Set both HBT testers for External mode and press the RUN button.
You should be able to see the bundle connection errors are translated into
bit errors on the HBT tester (Gmux side).
ETX-202
GbETH
E1
IPmux-14(1)
ETH E1
TDMoIP
HBT HBT
Gmux-2000
FAQ
C Learn how does the IPmux/Gmux propagate E1/T1
alarms

44
Troubleshooting Procedure
The reason for the Sequence Error and Underflow events are the insufficient
BW available for the TDMoIP traffic on the IPmux-14 to Gmux direction.
The rate limit cases the lost packets and also the occasional underflows.
You will need to find a way to reduce the TDMoIP throughout to below
3Mbps.
This can be done by changing the TDM bytes per frame value.
Q: What is the minimal TDM bytes value which reduce the BW consumption
to below 3Mbps?
3x48
4x48
5x48
6x48
1
2
3
4
3
4
C Use the tools button to run the
TDMoIP calculator
Tools

45
Solution
You are correct!
The minimal TDM bytes per frame value which will get the TDMoIP
throughput below 3Mbps is 4x48 (results in:2.854Mbps).
Please change the TDM bytes value on both the Gmux and IPmux-14(1)
and recheck the bundle connectivity.
HBT Functionality test:
The HBT should be in sync and the should run without errors.
Info
C About the IPmux throughput calculation and how to use the TDMoIP calculator
FAQ

46
Task 1 – Complete
You have finished setting a basic TDMoIP circuit between two IPmux units.
This circuit will remain configured also during the next two tasks.
Please proceed to Task 2

47
Task 2
Task 2
Creating Unframed Point to Point TDMoMPLS
Connection

48
IPmux-14/SER(2)
V.35
ETH
In the second task you will configure TDMoMPLS point-to-point connection
between the IPmux-14(1) and the IPmux-14(2) units.
ETX-202
Gmux-2000
IPmux-14/SER(1)
IPmux-14(2)
V.35
GbET
H
ETH
ETH E1
E1
NMS &
Sniffer
STM-1
TDMoMPLS
IPmux-14(1)
ETH
E1
TDMoMPLS
HBT
HBT

49
What is TDMoMPLS?
TDMoMPLS is a flavor of the TDMoIP circuit emulation standard.
Basically by using TDMoMPLS we are replacing the UDP and IP headers
used by the TDMoIP format, with a single MPLS header.
By that we are able to save up to 24 bytes (40% !!!) of the traditional
TDMoIP header.
C
R
C
TDM Payload CW MPLS ETH
C
R
C
TDM Payload CW UDP IP ETH
Info
C About the MPLS header

50
The Unframed E1 link will be created between the IPmux-14(1) E1 port 2
and the IPmux-14(2) E1 Port 1.
In this task, the TDM traffic will be encapsulated using the TDMoMPLS
frame format. The header attached to the TDM traffic does not change the
nature of the Unframed operation mode
Task connections:
•IPmux-14(1) to ETX-202 ETH User 3
•IPmux-14(2) to ETX-202 ETH User 4
•HBT to IPmux-14(1) – E1 Port 2
•HBT to IPmux-14(2) – E1 port 1
ETX-202
E1 ETH E1
TDMoMPLS
IPmux-14(1)
HBT HBT
IPmux-14(2)
ETH
TDMoMPLS

51
Task 2- Application Setup
Since we are about to add more traffic on the ETX-202 User port 3, we will
need to disable the Ingress Rate Limit function on this port.
Access the ETX-202 using Username: su and Password:1234 and disable
the Rate Limit on User port 1:
ETX-202
Configuration>Qos>Rate Limitation>Ingress
1. User Port 1 Rate Limitation > (No Limit )
4. User Port 4 Rate Limitation > (No Limit )>
Path

52
IPmux-14(1) Configuration
Now configure the IPmux-14(1) unit.
The same Host IP address and IP Mask which were configured in Task 1 will
be used in Task 2.
The Manager List from Task 1 will be also used for this task.
Reminders:
• Host IP Address: 192.168.100.141/ 255.255.255.0
• Manager List: 192.168.100.254

53
IPmux-14(1) Physical Parameters Configuration
The IPmux-14(1) will be configured to provide the clock for this link.
Internal
(Clock Source)
Adaptive
LBT LBT
Info
ETX-202
E1 ETH E1
TDMoMPLS
IPmux-14(2)
HBT HBT
IPmux-14(1)
ETH
TDMoMPLS
C About clocking

54
Set the IPmux-14(1) E1 port 2 to Unframed mode, as below:
Channel ID (2)
2. Transmit clock source > (Internal)
Press F to
advance to
Channel ID 2
Path

55
IPmux-14(1) Connecting Bundles
After setting the E1 port to Unframed mode, proceed to configure Bundle ID
33 connection parameters:
1. Bundle ID[1 - 127] ... (33)
3. PSN type (MPLS/ETH)
1. Select: 3. PSN type-
MPLS/ETH
2. Select: 4.Bundle Connection

56
Now define the bundle connection parameters:
Path TDM channel ID: 2 Bundle ID: 33
2. Outbound label tagging (Disable)
5. Next hop type (IP )
6. Next hop IP address ... (-)
In this case we use only
one MPLS label, i.e. the
Inner label.
As the Inner Label
contains the Destination
bundle, it will equal:
1 +15=16
(as 1-15 MPLS labels
are
Reserved).

57
IPmux-14(2) Configuration
Now configure the IPmux-14(2) unit.
Host IP and Manager list parameters:
• Host IP Address: 192.168.100.142/ 255.255.255.0
• Manager List: 192.168.100.254
• Authentication/Community: Write=public

58
Set the IPmux-14(2) E1 port 1 to Unframed mode, as below:
Channel ID (1)
Make sure you
configure CH#1
Path

59
After setting the E1 port to Unframed mode, proceed to configure Bundle ID
1 connection parameters:
1. Bundle ID[1 - 127] ... (1)
3. PSN type (MPLS/ETH)
1. Select: 3. PSN type-
MPLS/ETH
Connection

60
Path TDM channel ID: 1 Bundle ID: 1
2. Outbound label tagging (Disable)
5. Next hop type (IP )
6. Next hop IP address ... (-)
13. VLAN tagging (Disable) In this case the inner label will be
33+15=48.
Info
C The OAM feature

61
IPmux-14(2) – Verify Bundle Status
IPmux-14(1&2) the bundle should be up and running.
Quickly browse to the bundle connection status:
1. Bundle ID[1 - 128] ... (33)
Make sure you
are monitoring the
correct bundle ID

62
IPmux-14/SER(2)
V.35
ETH
Testing – HBT functionality
In order to test the second TDMoMPLS circuit using the HBT testers:
Move the HBT tester which was connected to the Gmux to the IPmux-14(2).
ETX-202
Gmux-2000
IPmux-14/SER(1)
IPmux-14(2)
V.35
GbET
H
ETH
ETH E1
E1
NMS &
Sniffer
STM-1
TDMoMPLS
IPmux-14(1)
ETH
E1
TDMoMPLS
HBT
HBT

63
Task 3
Task 3
Creating Unframed Point to Point HDLCoIP
Connection

64
In the third task you will configure HDLCoIP point-to-point connection
between the IPmux-14/SER(1) and the IPmux-14/SER(2).
ETX-202
Gmux-2000
IPmux-14/SER(1)
IPmux-14(2)
V.35
GbET
H
ETH
ETH E1
E1
NMS +
Sniffer
STM-1
IPmux-14(1)
ETH E1
HDLCoIP
IPmux-14/SER(2)
V.35
ETH
HDLCoIP

65
The ETX-202 and the IPmux-14(2), will be used as L2 Switches connecting
the IPmux-14/SER units.
Current task connections:
• IPmux-14/SER(1) – ETX-ETH User 5
• IPmux-14(2) – ETX-ETH User 4
• IPmux-14/SER(2) – IPmux-14(2) User port 1
ETX-202
V.35 ETH
IPmux-14/SER(2)
IPmux-14/SER(1)
ETH
HDLCoIP
IPmux-14(2)
ETH V.35
APD APD
Info
C All about the HDLCoIP/MPLS format

66
The Unframed E1 link will be created between the IPmux-14/SER(1) and the
IPmux-14/SER(2) V.35 ports, using HDLCoIP encapsulation.
ETX-202
V.35 ETH
IPmux-14/SER(1)
ETH
HDLCoIP
IPmux-14(2)
ETH V.35
APD APD
IPmux-14/SER(2)

67
Task 3 – Clocking Configuration
Since we are working in HDLC mode, there is no need to propagated the
clock over the ETH network to the remote site, i.e. to sync both ends to the
same clock.
DCE-Internal DCE-Internal
Info
ETX-202
V.35 ETH
IPmux-14/SER(2)
IPmux-14/SER(1)
ETH
HDLCoIP
IPmux-14(2)
ETH V.35
APD
APD
C Learn more about the IPmux-14/SER ordering options

68
IPmux-14/SER(1) Configuration- Host IP/NMG
Now configure the IPmux-14/SER(1) unit.
• Host IP Address: 192.168.100.143/ 255.255.255.0
• Manager List: 192.168.100.254

69
IPmux-14/SER(1) Physical Parameters Configuration
Set the IPmux-14/SER(1) Serial port, as below:
Configuration>Physical layer>Serial channel
2. Interface type > (V.35)
3. Speed(n x multiplier)[1 - 32] ... (32)
4. Multiplier (64)
5. Transmit clock source > (DCE-Internal)
6. Clock polarity (Invert)
7. CTS (On)
The IPmux-
14/SER(1) will
supply the clock to
the APD device
connected to the
V.35 interface.
Path

70
IPmux-14/SER(1) Connecting Bundles
After setting the V.35 rate, proceed to configure Bundle ID 1 connection
parameters:
Path Connection
1. Bundle ID[1 - 1] ... (1)
2. Connection mode > (HDLC)
4. Bundle connection
1. Select: 2. Connection mode-
HDLC
Connection

71
Bundle connection
2. Next hop ... (-)
3. IP TOS[0 - 255] ... (0)
In HDLC mode there is no TDM bytes
per frame settings. The HDLCoIP
payload size will be set dynamically
according to the length of the HDLC
data needs to be transmitted.

72
IPmux-14/SER(2) Configuration- Host IP/NMG
Now configure the IPmux-14/SER(2) unit.
• Host IP Address: 192.168.100.144/ 255.255.255.0
• Manager List: 192.168.100.254

73
IPmux-14/SER(2) Physical Parameters Configuration
Set the IPmux-14/SER(2) Serial port, as below:
Configuration>Physical layer>Serial channel
2. Interface type > (V.35)
3. Speed(n x multiplier)[1 - 32] ... (32)
4. Multiplier (64)
5. Transmit clock source > (DCE-Internal)
6. Clock polarity (Invert)
7. CTS (On)
The IPmux-
14/SER(2) will
supply the clock to
the device
connected to the
V.35 interface.
Path

74
After setting the V.35 rate, proceed to configure Bundle ID 1 connection
parameters:
Path Connection
1. Bundle ID[1 - 1] ... (1)
2. Connection mode > (HDLC)
4. Bundle connection
1. Select: 2. Connection mode-
HDLC
Connection

75
Bundle connection
2. Next hop ... (-)
3. IP TOS[0 - 255] ... (0)
In HDLC mode there is no TDM bytes
per frame settings. The HDLCoIP
payload size will be set dynamically
according to the length of the HDLC
data needs to be transmitted.
Info
C Setting the IP TOS

76
IPmux-14(2) – Verify Bundle Status
IPmux-14/SER(1)&(2) the bundle should be up and running.
Quickly browse to the bundle connection status:
1. Bundle ID[1 - 128] ... (1)
Make sure you
are monitoring the
correct bundle ID

77
Task 4
Task 4
BW consumption comparison:
TDMoIP Vs. TDMoMPLS Vs. HDLCoIP

78
Measuring ETH Utilization
In this application you will measure the ETH utilization introduced by each
mode of connection:
1. TDMoIP
2. TDMoMPLS
3. HDLCoIP
Each connection is set for the same TDM rate, I.e. 32x64Kbps and same
TDM bytes per frame (excluding the HDLC mode).

79
Calculating ETH Utilization
Please use the TDMoIP calculator in order to estimate the BW utilization
introduced by each mode and fill the table below:
BW
Utilization/pps
rate – calculator
[Mbps]
TDM bytes in
Frame
TDM Rate
Connection mode
1x48
Unframed
TDMoIP
1x48
Unframed
TDMoMPLS
N/A
Dynamic
BW
utilization
32x64Kbps
HDLCoIP

80
Setting the application
In order to test the ETH utilization, we will use set the ETX-202 to
work as a Full-Duplex ETH HUB.
In such case it will not perform any Switching according to MAC
addresses, but will flood every frame entering any port to all other
ports.
This will allow us to connect a monitoring PC to the ETX and
measure the ETH utilization using a Sniffer.

81
Setting the application
In order to set the ETX-202 to work in HUB mode, follow the below
instructions:
Configuration>Bridge
1. VLAN Mode (Unaware)
2. Forwarding Mode (Transparent)
3. Bridge Port >
4. Link Aggregation >
1. Select: Forwarding
Mode-Transparent
2. Save

82
Setting the application - TDMoIP
Start with the TDMoIP connection:
1. Disable the following bundles:
- Bundle ID#1 (TDMoMPLS) IPmux-14(2).
- Bundle ID#1 (HDLCoIP) IPmux-14/SER(1).
2. Set the TDM bytes per frame on the IPmux-14(1) Bundle ID:1 and Gmux
Bundle ID 1 to: 1x48 (4x48 was used due to the rate limit settings on the
ETX-202, in chapter 1).
3. Run the Sniffer program located on the desktop

83
IPmux-14/SER(2)
V.35
ETH
HDLCoIP
Setting the application - TDMoIP
ETX-202
(HUB)
Gmux-2000
IPmux-14/SER(1)
IPmux-14(2)
V.35
GbET
H
ETH
ETH E1
E1
Sniffer
STM-1
TDMoMPLS
IPmux-14(1)
ETH E1
TDMoIP
HDLCoIP

84
Measuring BW - TDMoIP
Goto the Sniffer application and follow the below instructions:
1. Press the
Dashboard icon to
open the Gauges
2. Monitor the
Utilization in % and the
pps rate shown in the
Utilization Gauges
3. Write down the
value in the table on
slide 98
2. Monitor the
Utilization in % and the
pps rate shown in the
Utilization Gauges
3. Write down the
value in the table on
slide 88

85
Setting/Measuring the application - TDMoMPLS
Now measure the TDMoMPLS connection:
1. Disable Bundle ID#1 (TDMoIP) on the IPmux-14(1).
2. Enable Bundle ID#1 (TDMoMPLS) on the IPmux-14(2).
3. Measure the BW utilization/pps using the Sniffer program
4. Write down the value in the table on slide 98
ETX-202
(HUB)
Gmux-2000
IPmux-14/SER(1)
IPmux-14(2)
V.35
GbET
H
ETH
ETH E1
E1
Sniffer
STM-1
TDMoMPLS
IPmux-14(1)
ETH E1
TDMoIP+
TDMoMPLS
HDLCoIP
IPmux-14/SER(2)
V.35
ETH
HDLCoIP

86
Setting/Measuring the application - HDLCoIP
Now measure the HDLCoIP connection (no user traffic):
1. Disable Bundle ID#1 (TDMoIP) on the IPmux-14(2).
2. Enable Bundle ID#1 (HDLCoIP) on the IPmux-14/SER(1).
3. Measure the BW utilization and pps rate using the Sniffer
program
ETX-202
(HUB)
Gmux-2000
IPmux-14/SER(1)
IPmux-14(2)
V.35
GbET
H
ETH
ETH E1
E1
Sniffer
STM-1
TDMoMPLS
IPmux-14(1)
ETH E1
TDMoIP+
TDMoMPLS
HDLCoIP
E1
IPmux-14/SER(2)
V.35
ETH
HDLCoIP

87
Setting/Measuring the application - HDLCoIP
Now measure the HDLCoIP connection, while transmitting traffic:
1. Connect the PC to the APD unit via the COM port ( using the adapter
cable).
2. From the HT select: Transfer>Send text file…
3. Choose the setuplog.txt file located on the desktop and press start.
4. Measure the BW utilization/pps using the Sniffer program
ETX-202
V.35 ETH
IPmux-14/SER(2)
IPmux-14/SER(1)
ETH
HDLCoIP
IPmux-14(2)
ETH V.35
APD APD
DB-9 to RJ-45 converter cable

88
ETH BW - Results
Please fill in the below table with the test results.
BW Utilization
measure
[Mbps]/ pps
rate
BW Utilization
– calculator
[Mbps]
TDM bytes in
Frame
TDM Rate
Connection
mode
5.141
Full-Duplex
pps=5447
1x48
Unframed
TDMoIP
4.270
Full-Duplex
pps =5447
1x48
Unframed
TDMoMPL
S
-No user
traffic=0
- With user
traffic=>0
N/A
32x64Kbp
s
HDLCoIP

89
Task 5
Task 5
Fractional E1 connection + CL Redundancy test

90
E1
IPmux-14/SER(2)
V.35
ETH
HDLCoIP
In this application you will practice the creation of a Framed bundle
between the Gmux-2000 and the IPmux-14(1).
After completing the TDMoIP circuit, you will test CL Redundancy
feature on the Gmux-2000.
ETX-202
Gmux-2000
IPmux-14/SER(1)
IPmux-14(2)
V.35
GbETH
ETH
ETH
E1
NMS +
Sniffer
STM-1
TDMoMPLS
IPmux-14(1)
ETH E1
TDMoIP
HDLCoIP

91
The Framed E1 link (TS 1-10) will be created between the Gmux E1 port 2
on slot 1 (S1/P2) and the IPmux-14 E1 Port 3.
ETX-202
GbETH
E1
IPmux-14(1)
ETH E1
TDMoIP
FAQ
C Downloading uploading Gmux Config files

92
Setting ETX-202
In order to set the ETX-202 to work again in Switching mode, follow
the below instructions:
Configuration>Bridge
1. VLAN Mode (Unaware)
2. Forwarding Mode (Filter)
3. Aging Time(sec)[300 - 4080] ... (300)
4. Static MAC Table []>
5. Erase MAC table
6. Bridge Port >
7. Link Aggregation >
1. Select:
Forwarding Mode-
Filter

93
Gmux-2000 physical port setup
Path
At this point, you will need to configure the E1 port characteristics, such as
Line Type and Clock settings:
GMUX-2000
Config>Physical layer>E1 port - (IO 1: ETX PORT 2 CARD TYPE- CES E1)
1. Channel ID[1 - 28] ... (2)
2. Admin Status (Connected)
3. Idle code[0 - ff] ... (7E)
4. OOS Signaling > (Space)
5. OOS code[0 - ff] ... (FF)
6. Transmit clk source > (system a)
7. Rx Sensitivity > (Short Haul)
8. Bundle number[1 - 2000] ... (0)
9. TS type (NC)
10. Line type > (Framed G.704)
11. Restoration Time > (CCITT)
12. Save parameters
Info
C What is the “Idle Code”?

94
In order to establish the TDMoIP connectivity between the Gmux and the
IPmux-14(1) we need to set the bundle connection parameters.
These parameters define the logical connection between the IPmux/Gmux
units, as shown below:
Path
GMUX-2000
Config>Connection - (BUNDLE 1)
1. Bundle ID[1 - 2000] ... (2)
2. Connection mode > (TDMoIP(CE))
4. Connection configuration []>
5. Save parameters
1. Press X to add a bundle
2. Select: 5. Save parameters
3. Select: 4.Connection
Configuration

95
Path
GMUX-2000
Config>Connection>Connection configuration - (BUNDLE 1)
Connection state Enable
Source CBID 2
Dest CBID 65
| Payload format V2
v TDM byte in frame(x48) 1
Jitter buffer in Ms[0-200] 3
OAM connectivity Enable
Payload type Data
| Far end type E1
OOS L bit mode TX OOS and L bit
| Destination IP 192.168.100.141
v Network slot port 6/1
Next hop 0.0.0.0
IP TOS 0
Adaptive clock Disable
VLAN tagging Disable
Set the following Bundle connection parameters and Save:

96
Path
Now we have a TDM port 2/slot 1 set for Framed mode and a bundle ID#2.
Now you will need to associate the bundle with the TDM interface.
Please follow the below sequence:
GMUX-2000
Config>TS Assignment
1. Server ss/pp ... (1/2)
2. TS assignment []>
3. Assign entire port to bundle >
1. Make sure server card slot 1
port 2 are selected
2. Select: 2. TS assignment

97
Path Config>TS Assignment>TS assignment
TIME SLOT NUM : ts 1 ts 2 ts 3 ts 4 ts 5 ts 6 ts 7 ts 8 ts 9 ts10
Bundle number: 2 2 2 2 2 2 2 2 2 2
TS type: Full Full Full Full Full Full Full Full Full Full
1. Select : 1.Change
cell
2. Enter Bundle ID: 2
and TS type: Full
3. Repeat for TS 1-10
4. Save and Update
the DB.

98
IPmux-14(1) E1 Physical Parameters
Continue with the IPmux-14(1) configuration.
Verify the E1 Line Type and the clock settings:
Path Configuration>Physical layer>TDM configuration (E1)
Channel ID (3)
4. Line type > (Framed G.704)
6. Idle code[0 - ff] ... (7E)
7. Send upon fail (OOS code)
8. OOS code[0 - ff] ... (FF)
>
The Line Type must be set
according to the settings on
the Gmux – i.e. Framed
G.703.
The Gmux was configured for
Internal CLK source. In order
to regenerate this CLK on the
IPmux-14 we need to use
Adaptive timing mode
Info
C What is the “OOS code”?

99
Continue with the manual TS allocation to the bundle:
Path Connection
1. Bundle ID[1 - 127] ... (65)
4. DS0 bundle []>
1. Select: 4.DS0 Bundle

100
Allocate TS 1-10 to bundle ID 65:
Path DS0 bundle
TDM channel ID:3 Bundle ID: 65
+1 +2 +3 +4 +5 +6 +7 +8 +9 +10
TS 0 65 65 65 65 65 65 65 65 65 65
TS 10 0 0 0 0 0 0 0 0 0 0
TS 20 0 0 0 0 0 0 0 0 0 0
TS 30 0
1. Change cell [0 - 1] ... (0)
1. Select: 1.Change Cell
2. Select 1
3. Repeat for TS1-10

101
IPmux-14 Bundle Connection
You should now set the bundle connection parameters in order to connect it
to the bundle configured on the Gmux and Save:
Bundle connection
2. Next hop ... (-)
3. IP TOS[0 - 255] ... (0)
7. Payload format (V2)
8. Far end type > (E1)
The Destination bundle is the
Gmux Source CBID of bundle 2

102
IPmux-14 – Verify Bundle Status
IPmux-14 the bundle should be up and running.
How can you check the bundle connection status?
1. Bundle ID[1 - 128] ... (65)
Animation
Path
C See what is a JB Underflow

103
Gmux – Verify Bundle Status
Now check the same monitoring on the Gmux:
GMUX-2000
Monitoring>Status>Connection>Bundle counters
1. Bundle ID[1 - 2000] ... (1)
Destination IP address ... (192.168.100.141)
Connectivity Status ... (OK)
Sequence Errors ... (0)
Jitter buffer Underflows ... (0)
Jitter buffer Overflows ... (0)
Min Jitter buffer Level [Msec] ... (0)
Max Jitter buffer Level [Msec] ... (3)
Frames Tx to PSN ... (1317435)
Frames Rx from PSN ... (984390)
Animation
Path
C See what is a JB Overflow

104
Testing CL Redundancy
Now test the Gmux CL Redundancy feature:
1. Connect the HBT testers to the Gmux Slot1/port1 and to the IPmux-14
E1 port 1.
2. Set both HBT testers for External mode and press the RUN button.
3. Take out the CL module residing on Slot 1
4. Make sure that the flip which occurred between the CL modules did not
cause any errors on the TDM.
ETX-202
GbETH
E1
IPmux-14(1)
ETH E1
TDMoIP
HBT HBT
Gmux-2000
FAQ-1
C Check the Gmux alarm mechanism/event log
FAQ-2

105
Task 6
Task 6
Creating an STM-1 Connection using the
Service-Center

106
In this application you will practice the creation of an STM-1 to E1
connection between the Gmux-2000 and the IPmux-14(2) via the
RADview service center.
ETX-202
Gmux-2000
IPmux-14/SER(1)
IPmux-14(2)
V.35
GbETH
ETH
ETH E1
E1
NMS +
Sniffer
STM-1
TDMoIP
IPmux-14(1)
ETH E1
IPmux-14/SER(2)
ETH
Info
C Gmux CL OOB port management option

107
TDMoIP
CE
Server
1
Fan Tray
1
7
3
STM-1
OC-3
TDMoIP
CE
Ext E1/T1
Clocks
Local
Management
28-196
E1/T1
Ch. STM-1/
OC-3
AC/DC
AC/DC
Power Supply
AC/DC
Power Supply
AC/DC
Power
Inlet
GbE
Control
GbE
PSN I/F
Module
The Gmux is capable of
transmitting Channelized
STM-1 over GbETH
networks.
In other words, it will
transmit the STM-1 to the
GbETH network in the form
of 63xE1s.
In order to perform the
VC-12s TDMoIP
encapsulation, server
modules are required.
Each server module, can
handle up to 21xE1s.
Three server modules will
populate the full STM-1.

108
You will map the following VC-12: TUG-3(1) TUG-2(1) TU(1) to the remote
E1 on the IPmux-14(2).
We will use the first STM-1 port on the Dual STM-1 module residing on
I/O-9.
The TDMoIP encapsulation will be performed by the E1-SRV Module
residing on I/O-2.
The service will be created using the IPmux management system called
RADview TDMoIP Service Center.
The SC both server and client are located on this PC.

109
About RADview Service Center
The RADview Service Center application is a powerful management
tool for provisioning and monitoring TDM over IP (TDMoIP)
services.
It also offers embedded management capabilities .
The Service Center’s intuitive GUI interface, “point-and-click”
functionality and easy-to-follow wizards increase the efficiency and
accuracy of the service provisioning process.
The SC supports most IPmux configurations, statistics and
diagnostics operations as supported via the local console
management port.

110
ETX-202
IPmux-14/SER(2)
ETH
Gmux-2000
IPmux-14/SER(1)
IPmux-14(2)
V.35
GbETH
ETH
ETH E1
E1
NMS
STM-1
TDMoIP
IPmux-14(1)
ETH E1
Network Management station which will include both the Service Center
server and client is directly connected to the ETX-202.
You will configure the circuit via this NMS.
C Reference: Gmux quick Config STM-1
Database

111
Host IP/Manager Addresses assignment
At this point all the IPmux/Gmux products involved in this application were
already configured with IP Address and a Manager List in previous tasks.
ETX-202
Gmux-2000
192.168.100.200
IPmux-14/SER(1)
192.168.100.143
IPmux-14(2)
192.168.100.142
V.35
GbETH
ETH
ETH E1
E1
NMS
192.168.100.254
STM-1
TDMoIP
IPmux-14(1)
192.168.100.141
ETH E1
TDMoIP
HDLCoIP
IPmux-14/SER(1)
192.168.100.144
ETH
FAQ
C How to order Gmux w/ STM-1

112
Start Server
In this Workshop both the SC Server and Client will reside on the same
station (i.e. PC).
First run the SC Server from the START menu:
START 
All Programs 
Network Manager 
Service Center 
TDMoIP 
Start Server…

113
Start Server
Wait until the Server will be in RAEDY state:

114
Start Client
After the SC Server is running run the SC Client:
START 
All Programs 
Network Manager 
Service Center 
TDMoIP 
Start Client…

115
Logging into the Server
In order to log into the Service Center Server enter the following password:
root

116
Creating a New Service
From the Servers map, double click on the server and open the Services
map:

117
To create a service on the service map select Configuration>Add Service:

118
Under the Create Service window, enter the following parameters:

119
The service you just created will appear on the Services map:

120
Discover Devices
From the Services map, select View>Managed Element Discovery Pool:

121
Discover Devices
From the Managed Elements Discovery Pool window, select:
Configuration> Discover Managed Elements

122
Discover Devices
Enter the starting IP address and press SET:
0.

123
Discover Devices
After the discovery process ends, you should see all the IPmux under the
discovery pool:

124
Adding elements to the service map
Double click on the Service icon, on the Services map, in order to open the
Service map:

125
Drag the IPmux elements from the discovery pool:
To the Service map:

126
All the managed elements should now appear under the Service map:

127
Uploading the Gmux settings
In order to update the SC database with the Gmux running configuration,
there is a need to perform the following actions:
1. Double Click the Gmux
Icon
2. Select the System Row
3. Select: Configuration:
Read…
Card type not updated…

128
Press the OK button to continue with the update process:
Wait for the read process to finish.

129
You can see now that the left Edit side of the Gmux table was updated with
Gmux settings on the right Agent side:
Card type now updated…

130
Discovering Circuits
In order to discover the valid
bundles already configured
between the Gmux/IPmux
units in previous tasks, select:
Configuration>
Discover Circuits
All configured bundle should
now be seen on the Service
map.
Represents number of
bundles configured
between units
Database
C About the SC bundle connection color indication

131
Creating a New Circuit
In order to create the bundle/circuit between the Gmux and the IPmux-14(2)
units, first configure the Gmux physical parameters. Double click the Gmux
icon 192.168.100.200:
1. Mark the I/O-2 row
2. Select: Configuration>Card
Parameters…
3. Check the I/O-6 port under the G-
ETH Exit port.
2
E1/21 Server

132
1. Mark the I/O-2
row
2. Select:
Configuration-
Zoom…

133
On the E1/21 Server Menu
select the Internal E1-1 row
and Goto:
Configuration>Parameters

134
Under the Port Parameters screen set the following:
1. Line Type:
Unframed
(G.703)
2. Transmit Clock
Source: System
3. Press Set

135
Continue to configure the physical STM-1 parameters:
1. Mark the I/O-9
row
2. Select:
Configuration-
Zoom…

136
On the STM-1 Menu select
the External-1 row and Goto:
Configuration> Parameters

137
Under the STM-1 Port Parameters screen set the following:
1. Admin Status:
Enabled
2. Clock Source:
Internal
3. Press Set

138
In order to update the Gmux system with the physical configuration changes
you have just performed, follow the below procedure:
1. Mark: System
row
2. Select: Update…

139
Press OK to continue with the update process (the Service Center DB is
updating the Gmux DB).
Wait for the process to complete.
Press Close.

140
Continue with the Physical configuration settings on the IPmux-14(2) unit.
Double click the IPmux-14(2) icon (192.168.100.142):
1. Mark: CH2
(Slot1) row
2. Select:
Configuration-
Parameters…

141
Set the following
parameter:
1. Line type: Unframed (G.703)
2. Press Set
3. Confirm (press ok) when the
below alert message window
appears

142
After defining the Gmux and IPmux-14 physical parameters, proceed to
configure the bundle connection parameters:
1. Hold the CTRL key and left-
click on the Gmux unit.
2. Hold down the mouse button
and drag the appeared line
towards the other IPmux-
14(2) unit.
3. Release the mouse button.

143
Under the General
screen set:
1. Circuit name:
Seminar_2006
2. Connection Type: VC12-E
3. Connection BW:
Unframed E1
4. After you finish with the
General tab press Primary
Circuit

144
Under the Primary
Circuit screen and
configure:
1. Verify that the parameters
shown in the capture are
configured.
2. After you finish with the
Common. Param. tab
press EP Param. tab.

145
Under the EP
Param. tab set:
1. Gmux
CBID: 3
2. OOS
Payload
Suppressio
n: Enable
3. Press
Mapping
button…

146
Map the first E1 (VC-12) of I/O-2 to the
STM-1 matrix as shown below:
1. Select the following
TU: TUG-3-1/TUG2-
1/TU-1
2. Click and press the
Right mouse
button.
3. Select: Connect
4. Press: Set
5. Go back to the
circuit configuration
and press Set to
create the circuit

147
Once the circuit is created, the following message will appear:
Press Close.
When prompted to configure another bundle, select No.

148
Update Display
In case the bundle line status color comes
up red, access the Circuit List by double
clicking the bundle line and pressing the
Poll button to get an updated status

149
Service Map Completed
After completion, the service map should look as follows:

150
Task 7
Task 7
Configuration and Troubleshooting

151
Configuration and troubleshooting
In the next task you will be asked to create a TDMoIP connection between
the IPmux-14(1) unit and an IPmux-14(2) unit over a network emulator.
You will be provided with some basic configuration parameters and a
description of the application.
However, the task will be more complex than just basic bundle configuration
as we have simulated some problematic network conditions…
Database
C Collecting information for troubleshooting

152
What is exactly required?
You need to configure an Unframed connection between the IPmux-14(1)
unit
and the IPmux-14(2) unit.
You will test the connection using the two HBT tester used in the previous
tasks.
The goal is to identify the problems presented by the
network emulator:
- Packet loss ratio
- Max PDV value
Let’s start…
Info
C About PSN jitter (PDV)

153
Which devices to use?
In order to complete this task you will need the following items on your desk:
• 2 x IPmux-14
• 2 x HBT testers
• 1 x network emulator
• 2 x straight ETH cables
• 1 x mind fully concentrated….

154
The network emulator used in this workshop is a proprietary ETH emulator
developed by RAD.
It is based on a Megaplex-2104 chassis and an the ML-IP module HW.
It is capable of emulating different behaviors of PSN networks impairments.
The Network Emulator was preconfigured by the workshop guide.
About the Network Emulator

155
Preparation actions
1. Disconnect all the cables from the IPmux devices required for this task.
2. Set the IPmux-14(1) to factory default (Except Management).
3. Set the IPmux-14(2) to factory default (Except Management).
Configuration>System>Factory default
1. Full
2. Except management
Configuration will be lost and System will be reset. Continue ??? (Y/N) Y
Please select item <1 to 2>
ESC-prev.menu; !-main menu; &-exit 1 Mngr/s
-------------------------------------------------------------------------------------------
Path

156
Connecting Cables
• IPmux-14(1) ETH port #1 to the NETWORK Emulator ETH port NET1.
• IPmux-14(2) ETH port #1 to NETWORK Emulator ETH port NET2.
• Connect the HBT units to the IPmux-14(1) and IPmux-14(2) E1 port #1.
IPmux-14(1)
HBT
E1 ETH E1
TDMoIP
TDMoIP
IPmux-14(2)
HBT
Network Emulator
ETH

157
Basic IPmux configuration
• IPmux-14(1)
• Host IP Address: 192.168.100.141
• Mask: 255.255.255.0
• CLK: Internal
• Line Type: Unframed
• IPmux-14(2)
• Host IP Address: 192.168.100.142
• Mask: 255.255.255.0
• CLK: Adaptive
• Line Type: Unframed
Conversion
point 1
Host IP addresses
were not erased
during Factory Default

158
What can be said about the “NETWORK”?
The network emulator connecting the IPmux-14 units simulates a L2 ETH
network which two major deficiencies:
1. The network introduce high values of PDV (jitter).
2. The network introduce high ratio of packet loss
Database
C IPmux checkup procedure

159
Bundle Connection Parameters
Based on the requirements presented in the previous slide, set the most
suitable bundle connection parameters in order to attain a valid bundle
connectivity:
Configuration>Connection>Bundle connection
1. Destination IP address ... (???.???.???.???))
2. Next hop ... (0.0.0.0)
3. IP TOS[0 - 255] ... (0)
5. Destination bundle[1 - 8063] ... (??)
6. TDM bytes in frame(x48 bytes)[1 – 30) ... (?)
7. Payload format (??)
8. OAM connectivity (???)
9. Jitter buffer <msec>[3 - 200] ... (??)
10. VLAN tagging (???)
>
Please select item <1 to 10>
D - delete; ? - Help
ESC-prev.menu; !-main menu; &-exit 1 Mngr/s
-------------------------------------------------------------------------------
Path

160
Here comes the problems…
How can you measure the network jitter values using the IPmux?
How can you calculate the packet loss ratio?
This is the time to start some TROUBLESHOOTING!
FAQ
C Calculating IPmux pps rate

161
Hint 1
Use the IPmux JB max Deviation value to estimate the network jitter:
Monitoring>Statistics>Connection…

162
Hint 2
The IPmux can detect TDMoIP packet loss events. The notification for
packet loss event is Sequence Error (SE) event.
What is the rate of the SE counted by the IPmux?
If the rate is too high to measure, try to minimize the pps rate produce by
the IPmux in order to ease the calculation of the packet loss ratio.
Max PDV = ms
Packet loss ratio =
Tools
C The JB deviation tool

163
Thank You!
IPmux Team

IPmux ws 4.00.ppt

Recommended

Recommended

More Related Content

Similar to IPmux ws 4.00.ppt

Similar to IPmux ws 4.00.ppt (20)

Recently uploaded

Recently uploaded (20)

IPmux ws 4.00.ppt