How to Debug Trunk Interfaces - Revision history

Luc Morissette: Updated TDM status link

2023-08-15T12:45:25Z

Updated TDM status link

← Older revision		Revision as of 08:45, 15 August 2023
Line 11:		Line 11:
	In general, cabling makes all the difference when connecting a trunk interface. In most cases, after the local and remote trunk Ports are carefully selected and default configuration is used, cabling is the last thing that can cause a problem.<br>		In general, cabling makes all the difference when connecting a trunk interface. In most cases, after the local and remote trunk Ports are carefully selected and default configuration is used, cabling is the last thing that can cause a problem.<br>

	To check the status of the trunk : [[Toolpack ~~v2.5:Status Menus~~:TDM ~~Lines~~]]		To check the status of the trunk : [[Toolpack:TDMLinesStatus_B\|TDM line status]]

	On the web portal : <br>		On the web portal : <br>

Luc Morissette: Added T1/E1 errors

2020-11-12T21:05:19Z

Added T1/E1 errors

@@ Line 81: / Line 81: @@
 Note: Trunk ports on Tmedia 16 E1 and Tmedia 64E1 with patch panels are not in the same order of connection. Please verify in the respective installation guides.<br>
 == References  ==
 [http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00801069ff.shtml T1 Alarm Troubleshooting]

Nicole Tan: NT: Added note about the Cable Type for ISDN User or Network

2020-06-30T18:39:39Z

NT: Added note about the Cable Type for ISDN User or Network

← Older revision		Revision as of 14:39, 30 June 2020
Line 47:		Line 47:
	*Straight E1 cable (same for T1 and J1): pairs 1-2 and 4-5 must be the twisted pairs. This is different than a ethernet cable. It does not affect the system over short distances.<br>		*Straight E1 cable (same for T1 and J1): pairs 1-2 and 4-5 must be the twisted pairs. This is different than a ethernet cable. It does not affect the system over short distances.<br>
	*Crossover E1 cable: pairs 1-2 and 4-5 must be crossed.<br>		*Crossover E1 cable: pairs 1-2 and 4-5 must be crossed.<br>

			*Note: In the field, for ISDN configuration on T1/E, we found it clearly expects a specific pinout for ports configured for USER side (i.e. straight cables) and NETWORK side (i.e. cross-over).

	2. Only half way is working		2. Only half way is working

Luc Morissette at 07:29, 15 June 2011

2011-06-15T07:29:03Z

← Older revision		Revision as of 03:29, 15 June 2011
Line 15:		Line 15:
	On the web portal : <br>		On the web portal : <br>
	<pre>Status -> TDM lines -> click on the trunk -> Click on extended status -> Refresh now		<pre>Status -> TDM lines -> click on the trunk -> Click on extended status -> Refresh now
	</pre>		</pre>
	Most of these parameters are defined in RFC2495 ([http://www.faqs.org/rfcs/rfc2495.html www.faqs.org/rfcs/rfc2495.html]), but here is a guideline for different errors encountered:		Most of these parameters are defined in RFC2495 ([http://www.faqs.org/rfcs/rfc2495.html www.faqs.org/rfcs/rfc2495.html]), but here is a guideline for different errors encountered:

Line 32:		Line 32:
	You can also reset the status to get fresh information:<br>		You can also reset the status to get fresh information:<br>
	<pre>Click on Reset status -> Refresh now -> Unclick on Reset status -> Refresh now (again)		<pre>Click on Reset status -> Refresh now -> Unclick on Reset status -> Refresh now (again)
	</pre>		</pre>
	<br>		<br>

	You can also test with Trunk Loopbacks. Here is the procedure [[Parameter:~~_Loopback~~\|how to use Loopback]].		You can also test with Trunk Loopbacks. Here is the procedure [[Parameter: Loopback\|how to use Loopback]].


			<br>

	'''Possibles causes of bad cabling:'''<br>		'''Possibles causes of bad cabling:'''<br>
Line 78:		Line 78:
	<br>		<br>

	Note: Trunk ports on Tmedia 16 E1 and Tmedia 64E1 with patch panels are not in the same order of connection. Please verify in the respective installation guides.<br>		Note: Trunk ports on Tmedia 16 E1 and Tmedia 64E1 with patch panels are not in the same order of connection. Please verify in the respective installation guides.<br>

	== References ==		== References ==
	[http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00801069ff.shtml\| T1 Alarm Troubleshooting]
			[http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00801069ff.shtml T1 Alarm Troubleshooting]

Luc Morissette at 07:25, 15 June 2011

2011-06-15T07:25:19Z

← Older revision		Revision as of 03:25, 15 June 2011
Line 79:		Line 79:

	Note: Trunk ports on Tmedia 16 E1 and Tmedia 64E1 with patch panels are not in the same order of connection. Please verify in the respective installation guides.<br>		Note: Trunk ports on Tmedia 16 E1 and Tmedia 64E1 with patch panels are not in the same order of connection. Please verify in the respective installation guides.<br>

			== References ==
			[http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00801069ff.shtml\| T1 Alarm Troubleshooting]

Luc Morissette at 13:11, 11 May 2011

2011-05-11T13:11:44Z

← Older revision		Revision as of 09:11, 11 May 2011
Line 1:		Line 1:
	Connecting a trunk interface should be easy - right? Well it is more complicated than it seems because many conditions have some effect on the final installation.		Connecting a trunk interface should be easy - right? Well it is more complicated than it seems because many conditions have some effect on the final installation.

	Here are some examples:<br>		Here are some examples:<br>

	#Cables<br>		#Cables<br>
	#Port used on Tmedia units<br>		#Port used on Tmedia units<br>
	#Port used on remote device<br>		#Port used on remote device<br>
	#Framing<br>		#Framing<br>
	#Line encoding<br>		#Line encoding<br>

	In general, cabling makes all the difference when connecting a trunk interface. In most cases, after the local and remote trunk Ports are carefully selected and default configuration is used, cabling is the last thing that can cause a problem.<br>		In general, cabling makes all the difference when connecting a trunk interface. In most cases, after the local and remote trunk Ports are carefully selected and default configuration is used, cabling is the last thing that can cause a problem.<br>

	To check the status of the trunk : [[Toolpack v2.5:Status Menus:TDM Lines]]		To check the status of the trunk : [[Toolpack v2.5:Status Menus:TDM Lines]]

	On the web portal : <br>		On the web portal : <br>
			<pre>Status -> TDM lines -> click on the trunk -> Click on extended status -> Refresh now
			</pre>
			Most of these parameters are defined in RFC2495 ([http://www.faqs.org/rfcs/rfc2495.html www.faqs.org/rfcs/rfc2495.html]), but here is a guideline for different errors encountered:

	~~Status~~ -> ~~TDM lines -> click on the trunk -> Click on extended status -> Refresh now~~<br>		1. If you have LOS (Loss of Signal) -> Check cabling<br>

	~~Most~~ of ~~these parameters are defined in RFC2495~~ (~~[http://www.faqs.org/rfcs/rfc2495.html www.faqs.org/rfcs/rfc2495.html]~~)~~, but here is a guideline for different errors encountered:~~		2. If you have LOF/OOF (Loss of Frame) -> Check framing and type of trunk (E1 vs T1)<br>

	1. If you have ~~LOS~~ (~~Loss of Signal~~) -> Check cabling<br>		3. If you have RAI/RRA (Remote Alarm Indication) -> Check cabling<br>

	2. If you have ~~LOF~~/~~OOF~~ (~~Loss of Frame~~) -> ~~Check framing and type of trunk (E1 vs T1)~~<br>		4. If you have RSP/RSN (Receive Slip) -> Clocking is not set correctly<br>

	3. ~~If you have RAI/RRA~~ (~~Remote Alarm Indication~~) -> Check cabling~~<br>~~		5. Other errors, like FEC (Forward Error Correction)  and CVC (Code violations) are usually not critical, but should be verified -> Check cabling

	~~4. If you have RSP/RSN (Receive Slip) -> Clocking is not set correctly~~<br>		<br>

	~~5. Other errors, like FEC (Forward Error Correction)~~&~~nbsp~~; ~~and CVC (Code violations) are usually not critical, but should be verified~~ -> ~~Check cabling~~		You can also reset the status to get fresh information:<br>
			<pre>Click on Reset status -> Refresh now -> Unclick on Reset status -> Refresh now (again)
			</pre>
			<br>

	~~<br>~~		You can also test with Trunk Loopbacks. Here is the procedure [[Parameter:_Loopback\|how to use Loopback]].

	~~You can also reset the status to get fresh information:<br>~~

	~~Click on Reset status -> Refresh now -> Unclick on Reset status  -> Refresh now (again)<br>~~

	<br>		'''Possibles causes of bad cabling:'''<br>

	~~'''Possibles causes of bad cabling:'''~~<br>		1. Straight vs Crossover<br>

	1. ~~Straight vs Crossover~~<br>		Depending on the installation, the cable required can be a straight one or a crossover. Make sure the right one is used in the installation. This is detected with a LOS signal on the line.<br>

	~~Depending on the installation, the cable required can be a straight one or a crossover. Make sure the right one is used in the installation. This is detected with a LOS signal on the line.<br>~~		*Straight E1 cable (same for T1 and J1): pairs 1-2 and 4-5 must be the twisted pairs. This is different than a ethernet cable. It does not affect the system over short distances.<br>

	*Straight E1 cable (same for T1 and J1): pairs 1-2 and 4-5 must be the twisted pairs. This is different than a ethernet cable. It does not affect the system over short distances.<br>
	*Crossover E1 cable: pairs 1-2 and 4-5 must be crossed.<br>		*Crossover E1 cable: pairs 1-2 and 4-5 must be crossed.<br>

	2. Only half way is working		2. Only half way is working

	This is easy to detect as the RAI/RRA alarm will be set on one end (1) and LOS on the other end (2). This means the path from (1) to (2) is down and path from (2) to (1) is up.		This is easy to detect as the RAI/RRA alarm will be set on one end (1) and LOS on the other end (2). This means the path from (1) to (2) is down and path from (2) to (1) is up.

	3. Quality of the cable<br>		3. Quality of the cable<br>

	If the cable is not perfect, it may causes various errors like Code Violations. In general this will not affect the status of the line, but will generate static on the line and may prevent data communication, like HDLC processing for ISDN and SS7. Reference to other status parameters can be found in RFC 2495		If the cable is not perfect, it may causes various errors like Code Violations. In general this will not affect the status of the line, but will generate static on the line and may prevent data communication, like HDLC processing for ISDN and SS7. Reference to other status parameters can be found in RFC 2495

	3. 75 ohms E1 connections<br>		3. 75 ohms E1 connections<br>

	E1 75 ohms/120 ohms conversion requires an external Balun module<br>		E1 75 ohms/120 ohms conversion requires an external Balun module<br>

	<br>		<br>

	'''Default parameters:'''<br>		'''Default parameters:'''<br>

	E1<br>		E1<br>

	*Line encoding is HDB3<br>		*Line encoding is HDB3<br>
	*Framing is AUTO, which supports both MFRAME (multiframe, or with CRC) and STD (doubleframe without CRC)<br>		*Framing is AUTO, which supports both MFRAME (multiframe, or with CRC) and STD (doubleframe without CRC)<br>
	*Line length is SHORT<br>		*Line length is SHORT<br>

	T1/J1<br>		T1/J1<br>

	*Line encoding is B8ZS<br>		*Line encoding is B8ZS<br>
	*Framing is ESF (extended Super Frame)		*Framing is ESF (extended Super Frame)
	*Line length is SHORT		*Line length is SHORT

	<br>		<br>

	Note: Trunk ports on Tmedia 16 E1 and Tmedia 64E1 with patch panels are not in the same order of connection. Please verify in the respective installation guides.<br>		Note: Trunk ports on Tmedia 16 E1 and Tmedia 64E1 with patch panels are not in the same order of connection. Please verify in the respective installation guides.<br>

Lucas Trottier at 19:56, 8 December 2010

2010-12-08T19:56:23Z

← Older revision		Revision as of 15:56, 8 December 2010
Line 11:		Line 11:
	In general, cabling makes all the difference when connecting a trunk interface. In most cases, after the local and remote trunk Ports are carefully selected and default configuration is used, cabling is the last thing that can cause a problem.<br>		In general, cabling makes all the difference when connecting a trunk interface. In most cases, after the local and remote trunk Ports are carefully selected and default configuration is used, cabling is the last thing that can cause a problem.<br>

	To check the status of the trunk on the web portal ~~go here~~:<br>		To check the status of the trunk : [[Toolpack v2.5:Status Menus:TDM Lines]]

			On the web portal : <br>

	Status -> TDM lines -> click on the trunk -> Click on extended status -> Refresh now<br>		Status -> TDM lines -> click on the trunk -> Click on extended status -> Refresh now<br>

Luc Morissette: RFC -> RFC2495

2010-03-05T14:49:14Z

RFC -> RFC2495

← Older revision		Revision as of 10:49, 5 March 2010
Line 50:		Line 50:
	3. Quality of the cable<br>		3. Quality of the cable<br>

	If the cable is not perfect, it may causes various errors like Code Violations. In general this will not affect the status of the line, but will generate static on the line and may prevent data communication, like HDLC processing for ISDN and SS7. Reference to other status parameters can be found in RFC		If the cable is not perfect, it may causes various errors like Code Violations. In general this will not affect the status of the line, but will generate static on the line and may prevent data communication, like HDLC processing for ISDN and SS7. Reference to other status parameters can be found in RFC 2495

	3. 75 ohms E1 connections<br>		3. 75 ohms E1 connections<br>

Luc Morissette: Added "How to Debug Trunk Interfaces"

2010-02-10T21:07:26Z

Added "How to Debug Trunk Interfaces"

New page

Connecting a trunk interface should be easy - right? Well it is more complicated than it seems because many conditions have some effect on the final installation.

Here are some examples: 

#Cables 
#Port used on Tmedia units 
#Port used on remote device 
#Framing 
#Line encoding 

In general, cabling makes all the difference when connecting a trunk interface. In most cases, after the local and remote trunk Ports are carefully selected and default configuration is used, cabling is the last thing that can cause a problem. 

To check the status of the trunk on the web portal go here: 

Status -> TDM lines -> click on the trunk -> Click on extended status -> Refresh now 

Most of these parameters are defined in RFC2495 ([http://www.faqs.org/rfcs/rfc2495.html www.faqs.org/rfcs/rfc2495.html]), but here is a guideline for different errors encountered:

1. If you have LOS (Loss of Signal) -> Check cabling 

2. If you have LOF/OOF (Loss of Frame) -> Check framing and type of trunk (E1 vs T1) 

3. If you have RAI/RRA (Remote Alarm Indication) -> Check cabling 

4. If you have RSP/RSN (Receive Slip) -> Clocking is not set correctly 

5. Other errors, like FEC (Forward Error Correction)  and CVC (Code violations) are usually not critical, but should be verified -> Check cabling

 

You can also reset the status to get fresh information: 

Click on Reset status -> Refresh now -> Unclick on Reset status  -> Refresh now (again) 

 

'''Possibles causes of bad cabling:''' 

1. Straight vs Crossover 

Depending on the installation, the cable required can be a straight one or a crossover. Make sure the right one is used in the installation. This is detected with a LOS signal on the line. 

*Straight E1 cable (same for T1 and J1): pairs 1-2 and 4-5 must be the twisted pairs. This is different than a ethernet cable. It does not affect the system over short distances. 
*Crossover E1 cable: pairs 1-2 and 4-5 must be crossed. 

2. Only half way is working

This is easy to detect as the RAI/RRA alarm will be set on one end (1) and LOS on the other end (2). This means the path from (1) to (2) is down and path from (2) to (1) is up.

3. Quality of the cable 

If the cable is not perfect, it may causes various errors like Code Violations. In general this will not affect the status of the line, but will generate static on the line and may prevent data communication, like HDLC processing for ISDN and SS7. Reference to other status parameters can be found in RFC

3. 75 ohms E1 connections 

E1 75 ohms/120 ohms conversion requires an external Balun module 

 

'''Default parameters:''' 

E1 

*Line encoding is HDB3 
*Framing is AUTO, which supports both MFRAME (multiframe, or with CRC) and STD (doubleframe without CRC) 
*Line length is SHORT 

T1/J1 

*Line encoding is B8ZS 
*Framing is ESF (extended Super Frame)
*Line length is SHORT

 

Note: Trunk ports on Tmedia 16 E1 and Tmedia 64E1 with patch panels are not in the same order of connection. Please verify in the respective installation guides.