| Author |
Message |
Carlo
Guest
|
 Posted:
Wed Sep 01, 2004 3:28 am Post subject:
Frame circuit won't come up |
|
|
The routers are ARN's running Image:rev/14.00/1D5. This is a new
frame relay circuit. I ran the inst_arn.bat file, used the default
settings, then added the PVC through SM. It seems like ia am so close
yet the frame circuit will not come up. SBC, the frame provider is
not seeing a LMI signal coming from the router. They suspect a bad
V.35 cable but the router at far end is in the same state. I don't
have any spare cables. The V.35 cables I do have were used for normal
T1 (point to point) circuits. Does Nortel use a different cable for
frame circuits? The CSU/DSU are Paradynes 3162's. Any ideas on what
may be wrong?
Some stats below
$ show sync base
Line WAN
Loc Rem Med
Slot Conn Circuit State MAC Address Number MTU Protocol
Adr Adr Typ
---- ---- -------- -------- ----------------- -------- ---- --------
--- --- ---
1 1 S11_Oak- Up 00-00-A2-FF-2D-2E 00201201 1600 FRM RLAY
STD
landFR
1 entry(s) found
$ show frame stats
Sent Received
Line.LLIndex.DLCI Frames Octets Frames Octets Discard
Drops
----------------- ---------- ---------- ---------- ---------- --------
--------
201201.0.0 8429 118006 11 154 11
0
201201.0.101 0 0 0 0 0
0
2 entries found
$ show frame alerts
Line.LLIndex Circuit Mgt Type Intf Type Status Faults Discard
Drop
---------------- -------- --------- --------- -------- ------ --------
------
201201.0 S11_Oak- AnnexD Normal Fault 2 0
0
landFR
1 entry found
$ show frame service
Line.LLIndex.Cct Circuit Status Num VCs Default Multiline Name
---------------- -------- -------- ------- ------- ---------
-----------------
201201.0.3 S11_Oak- Active 1 Yes No
201201.0.3
landFR
1 entry found |
|
| Back to top |
|
 |
Sam Nash
Guest
|
| Posted:
Wed Sep 01, 2004 6:24 am Post subject:
Re: Frame circuit won't come up |
|
|
Looks like you need to have service record 3 (show frame service output
201201.0.3) defined for DLCI 101. Your show frame stats output
(201201.0.101) indicates the switch is expecting you to answer up for DLCI
101. The non-zero stats on 201201.0.0 indicate you're speaking frame to the
switch. The zero stats on 201201.0.101 indicate your ARN isn't speaking
through DLCI 101 as the switch expects.
Sam
The cable should be the same regardless of whether it's point-to-point or FR
(Nortel #7220).
"Carlo" <da.carlo@gmail.com> wrote in message
news:f41da617.0408311528.7d33ea26@posting.google.com...
| Quote: | The routers are ARN's running Image:rev/14.00/1D5. This is a new
frame relay circuit. I ran the inst_arn.bat file, used the default
settings, then added the PVC through SM. It seems like ia am so close
yet the frame circuit will not come up. SBC, the frame provider is
not seeing a LMI signal coming from the router. They suspect a bad
V.35 cable but the router at far end is in the same state. I don't
have any spare cables. The V.35 cables I do have were used for normal
T1 (point to point) circuits. Does Nortel use a different cable for
frame circuits? The CSU/DSU are Paradynes 3162's. Any ideas on what
may be wrong?
Some stats below
$ show sync base
Line WAN
Loc Rem Med
Slot Conn Circuit State MAC Address Number MTU Protocol
Adr Adr Typ
---- ---- -------- -------- ----------------- -------- ---- --------
--- --- ---
1 1 S11_Oak- Up 00-00-A2-FF-2D-2E 00201201 1600 FRM RLAY
STD
landFR
1 entry(s) found
$ show frame stats
Sent Received
Line.LLIndex.DLCI Frames Octets Frames Octets Discard
Drops
----------------- ---------- ---------- ---------- ---------- --------
--------
201201.0.0 8429 118006 11 154 11
0
201201.0.101 0 0 0 0 0
0
2 entries found
$ show frame alerts
Line.LLIndex Circuit Mgt Type Intf Type Status Faults Discard
Drop
---------------- -------- --------- --------- -------- ------ --------
------
201201.0 S11_Oak- AnnexD Normal Fault 2 0
0
landFR
1 entry found
$ show frame service
Line.LLIndex.Cct Circuit Status Num VCs Default Multiline Name
---------------- -------- -------- ------- ------- ---------
-----------------
201201.0.3 S11_Oak- Active 1 Yes No
201201.0.3
landFR
1 entry found |
|
|
| Back to top |
|
|
Carlo
Guest
|
| Posted:
Wed Sep 01, 2004 7:35 pm Post subject:
Re: Frame circuit won't come up |
|
|
I don't see (know) where in Site Manager you make the connection.
When I select edit circuit - services the window pops up with
201201.0.3 and the PVC is defined for this service. With the command
show fr service the output is 201201.0.3 and is labeled
Line.LLIndex.Cct. For the comamnd show fr stats the outputs are
201201.0.0 and 201201.0.101 and are labeled Line.LLIndex.DLCI. How
would I fix this? Is the fault status anything to be concerned about?
da.carlo@gmail.com (Carlo) wrote in message news:<f41da617.0408311528.7d33ea26@posting.google.com>...
| Quote: | The routers are ARN's running Image:rev/14.00/1D5. This is a new
frame relay circuit. I ran the inst_arn.bat file, used the default
settings, then added the PVC through SM. It seems like ia am so close
yet the frame circuit will not come up. SBC, the frame provider is
not seeing a LMI signal coming from the router. They suspect a bad
V.35 cable but the router at far end is in the same state. I don't
have any spare cables. The V.35 cables I do have were used for normal
T1 (point to point) circuits. Does Nortel use a different cable for
frame circuits? The CSU/DSU are Paradynes 3162's. Any ideas on what
may be wrong?
Some stats below
$ show sync base
Line WAN
Loc Rem Med
Slot Conn Circuit State MAC Address Number MTU Protocol
Adr Adr Typ
---- ---- -------- -------- ----------------- -------- ---- --------
--- --- ---
1 1 S11_Oak- Up 00-00-A2-FF-2D-2E 00201201 1600 FRM RLAY
STD
landFR
1 entry(s) found
$ show frame stats
Sent Received
Line.LLIndex.DLCI Frames Octets Frames Octets Discard
Drops
----------------- ---------- ---------- ---------- ---------- --------
--------
201201.0.0 8429 118006 11 154 11
0
201201.0.101 0 0 0 0 0
0
2 entries found
$ show frame alerts
Line.LLIndex Circuit Mgt Type Intf Type Status Faults Discard
Drop
---------------- -------- --------- --------- -------- ------ --------
------
201201.0 S11_Oak- AnnexD Normal Fault 2 0
0
landFR
1 entry found
$ show frame service
Line.LLIndex.Cct Circuit Status Num VCs Default Multiline Name
---------------- -------- -------- ------- ------- ---------
-----------------
201201.0.3 S11_Oak- Active 1 Yes No
201201.0.3
landFR
1 entry found |
|
|
| Back to top |
|
|
Rick
Guest
|
| Posted:
Thu Sep 02, 2004 4:01 am Post subject:
Re: Frame circuit won't come up |
|
|
Since every receive frame (11) has been discarded, I would verify that the
provider has the LMI type the same as yours which is AnnexD.
Hope this helps,
Rick
"Carlo" <da.carlo@gmail.com> wrote in message
news:f41da617.0409010735.71d90c0a@posting.google.com...
| Quote: | I don't see (know) where in Site Manager you make the connection.
When I select edit circuit - services the window pops up with
201201.0.3 and the PVC is defined for this service. With the command
show fr service the output is 201201.0.3 and is labeled
Line.LLIndex.Cct. For the comamnd show fr stats the outputs are
201201.0.0 and 201201.0.101 and are labeled Line.LLIndex.DLCI. How
would I fix this? Is the fault status anything to be concerned about?
da.carlo@gmail.com (Carlo) wrote in message
news:<f41da617.0408311528.7d33ea26@posting.google.com>...
The routers are ARN's running Image:rev/14.00/1D5. This is a new
frame relay circuit. I ran the inst_arn.bat file, used the default
settings, then added the PVC through SM. It seems like ia am so close
yet the frame circuit will not come up. SBC, the frame provider is
not seeing a LMI signal coming from the router. They suspect a bad
V.35 cable but the router at far end is in the same state. I don't
have any spare cables. The V.35 cables I do have were used for normal
T1 (point to point) circuits. Does Nortel use a different cable for
frame circuits? The CSU/DSU are Paradynes 3162's. Any ideas on what
may be wrong?
Some stats below
$ show sync base
Line WAN
Loc Rem Med
Slot Conn Circuit State MAC Address Number MTU Protocol
Adr Adr Typ
---- ---- -------- -------- ----------------- -------- ---- --------
--- --- ---
1 1 S11_Oak- Up 00-00-A2-FF-2D-2E 00201201 1600 FRM RLAY
STD
landFR
1 entry(s) found
$ show frame stats
Sent Received
Line.LLIndex.DLCI Frames Octets Frames Octets Discard
Drops
----------------- ---------- ---------- ---------- ---------- --------
--------
201201.0.0 8429 118006 11 154 11
0
201201.0.101 0 0 0 0 0
0
2 entries found
$ show frame alerts
Line.LLIndex Circuit Mgt Type Intf Type Status Faults Discard
Drop
---------------- -------- --------- --------- -------- ------ --------
------
201201.0 S11_Oak- AnnexD Normal Fault 2 0
0
landFR
1 entry found
$ show frame service
Line.LLIndex.Cct Circuit Status Num VCs Default Multiline Name
---------------- -------- -------- ------- ------- ---------
-----------------
201201.0.3 S11_Oak- Active 1 Yes No
201201.0.3
landFR
1 entry found |
|
|
| Back to top |
|
|
Carlo
Guest
|
| Posted:
Mon Sep 20, 2004 10:17 pm Post subject:
Re: Frame circuit won't come up |
|
|
The final piece of the puzzle was clocking source on the CSU/DSU.
Everyone was telling me to use external. The service provider was
insisting that the CSU/DSU was bad. I swapped the CSU/DSU with a
known working CSU/DSU being used on a T1 circuit and before I made any
config changes on the CSU/DSU the frame circuit started working. I
compared configurations on the CSU/DSU's and our T1's were using
internal clocking source. All is good for now. Thanks to everyone
for your suggestions and help.
"Rick" <rick.savoy@adelphia.net> wrote in message news:<0fCdnV_TQ699_6vcRVn-qw@adelphia.com>...
| Quote: | Since every receive frame (11) has been discarded, I would verify that the
provider has the LMI type the same as yours which is AnnexD.
Hope this helps,
Rick
"Carlo" <da.carlo@gmail.com> wrote in message
news:f41da617.0409010735.71d90c0a@posting.google.com...
I don't see (know) where in Site Manager you make the connection.
When I select edit circuit - services the window pops up with
201201.0.3 and the PVC is defined for this service. With the command
show fr service the output is 201201.0.3 and is labeled
Line.LLIndex.Cct. For the comamnd show fr stats the outputs are
201201.0.0 and 201201.0.101 and are labeled Line.LLIndex.DLCI. How
would I fix this? Is the fault status anything to be concerned about?
da.carlo@gmail.com (Carlo) wrote in message
news:<f41da617.0408311528.7d33ea26@posting.google.com>...
The routers are ARN's running Image:rev/14.00/1D5. This is a new
frame relay circuit. I ran the inst_arn.bat file, used the default
settings, then added the PVC through SM. It seems like ia am so close
yet the frame circuit will not come up. SBC, the frame provider is
not seeing a LMI signal coming from the router. They suspect a bad
V.35 cable but the router at far end is in the same state. I don't
have any spare cables. The V.35 cables I do have were used for normal
T1 (point to point) circuits. Does Nortel use a different cable for
frame circuits? The CSU/DSU are Paradynes 3162's. Any ideas on what
may be wrong?
Some stats below
$ show sync base
Line WAN
Loc Rem Med
Slot Conn Circuit State MAC Address Number MTU Protocol
Adr Adr Typ
---- ---- -------- -------- ----------------- -------- ---- --------
--- --- ---
1 1 S11_Oak- Up 00-00-A2-FF-2D-2E 00201201 1600 FRM RLAY
STD
landFR
1 entry(s) found
$ show frame stats
Sent Received
Line.LLIndex.DLCI Frames Octets Frames Octets Discard
Drops
----------------- ---------- ---------- ---------- ---------- --------
--------
201201.0.0 8429 118006 11 154 11
0
201201.0.101 0 0 0 0 0
0
2 entries found
$ show frame alerts
Line.LLIndex Circuit Mgt Type Intf Type Status Faults Discard
Drop
---------------- -------- --------- --------- -------- ------ --------
------
201201.0 S11_Oak- AnnexD Normal Fault 2 0
0
landFR
1 entry found
$ show frame service
Line.LLIndex.Cct Circuit Status Num VCs Default Multiline Name
---------------- -------- -------- ------- ------- ---------
-----------------
201201.0.3 S11_Oak- Active 1 Yes No
201201.0.3
landFR
1 entry found |
|
|
| Back to top |
|
|
MC
Guest
|
| Posted:
Tue Sep 21, 2004 2:30 am Post subject:
Re: Frame circuit won't come up |
|
|
On frame circuits you should use clocking from net.
Many CSU/DSU units have three clock sources.
Internal
External
Line (or NET)
External would have required an external clock source be seperately wired to
your CSU/DSU unit.
On some point-to-point lines one end may need to be set to Internal and one
end set to External only if the telco is not providing clocking.
However on services such as frame relay both ends would need to be set to
get it's clocking from the network (or line)
Setting both end's to Internal may work depending on how good and in sync
both end clocks are to each other, but will get slips and cause the frame
circuit to bounce but this is not the recommended way to do it.
"Carlo" <da.carlo@gmail.com> wrote in message
news:f41da617.0409201017.1e09ae4a@posting.google.com...
| Quote: | The final piece of the puzzle was clocking source on the CSU/DSU.
Everyone was telling me to use external. The service provider was
insisting that the CSU/DSU was bad. I swapped the CSU/DSU with a
known working CSU/DSU being used on a T1 circuit and before I made any
config changes on the CSU/DSU the frame circuit started working. I
compared configurations on the CSU/DSU's and our T1's were using
internal clocking source. All is good for now. Thanks to everyone
for your suggestions and help.
"Rick" <rick.savoy@adelphia.net> wrote in message
news:<0fCdnV_TQ699_6vcRVn-qw@adelphia.com>...
Since every receive frame (11) has been discarded, I would verify that
the
provider has the LMI type the same as yours which is AnnexD.
Hope this helps,
Rick
"Carlo" <da.carlo@gmail.com> wrote in message
news:f41da617.0409010735.71d90c0a@posting.google.com...
I don't see (know) where in Site Manager you make the connection.
When I select edit circuit - services the window pops up with
201201.0.3 and the PVC is defined for this service. With the command
show fr service the output is 201201.0.3 and is labeled
Line.LLIndex.Cct. For the comamnd show fr stats the outputs are
201201.0.0 and 201201.0.101 and are labeled Line.LLIndex.DLCI. How
would I fix this? Is the fault status anything to be concerned about?
da.carlo@gmail.com (Carlo) wrote in message
news:<f41da617.0408311528.7d33ea26@posting.google.com>...
The routers are ARN's running Image:rev/14.00/1D5. This is a new
frame relay circuit. I ran the inst_arn.bat file, used the default
settings, then added the PVC through SM. It seems like ia am so
close
yet the frame circuit will not come up. SBC, the frame provider is
not seeing a LMI signal coming from the router. They suspect a bad
V.35 cable but the router at far end is in the same state. I don't
have any spare cables. The V.35 cables I do have were used for
normal
T1 (point to point) circuits. Does Nortel use a different cable for
frame circuits? The CSU/DSU are Paradynes 3162's. Any ideas on what
may be wrong?
Some stats below
$ show sync base
Line WAN
Loc Rem Med
Slot Conn Circuit State MAC Address Number MTU Protocol
Adr Adr Typ
---- ---- -------- -------- ----------------- -------- ---- --------
--- --- ---
1 1 S11_Oak- Up 00-00-A2-FF-2D-2E 00201201 1600 FRM RLAY
STD
landFR
1 entry(s) found
$ show frame stats
Sent Received
Line.LLIndex.DLCI Frames Octets Frames Octets Discard
Drops
----------------- ---------- ---------- ---------- ---------- --------
--------
201201.0.0 8429 118006 11 154
11
0
201201.0.101 0 0 0 0
0
0
2 entries found
$ show frame alerts
Line.LLIndex Circuit Mgt Type Intf Type Status Faults Discard
Drop
---------------- -------- --------- --------- -------- ------ --------
------
201201.0 S11_Oak- AnnexD Normal Fault 2
0
0
landFR
1 entry found
$ show frame service
Line.LLIndex.Cct Circuit Status Num VCs Default Multiline Name
---------------- -------- -------- ------- ------- ---------
-----------------
201201.0.3 S11_Oak- Active 1 Yes No
201201.0.3
landFR
1 entry found |
|
|
| Back to top |
|
|
MC
Guest
|
| Posted:
Sun Sep 26, 2004 1:07 am Post subject:
Re: Frame circuit won't come up |
|
|
Opps the line
| Quote: | On some point-to-point lines one end may need to be set to Internal and
one
end set to External only if the telco is not providing clocking.
Should have said one end internal and one end line/Net |
MC
"MC" <mwclarke1@yahoo.com> wrote in message
news:2qJ3d.182242$%n4.131489@bignews6.bellsouth.net...
| Quote: | On frame circuits you should use clocking from net.
Many CSU/DSU units have three clock sources.
Internal
External
Line (or NET)
External would have required an external clock source be seperately wired
to
your CSU/DSU unit.
On some point-to-point lines one end may need to be set to Internal and
one
end set to External only if the telco is not providing clocking.
However on services such as frame relay both ends would need to be set to
get it's clocking from the network (or line)
Setting both end's to Internal may work depending on how good and in sync
both end clocks are to each other, but will get slips and cause the frame
circuit to bounce but this is not the recommended way to do it.
"Carlo" <da.carlo@gmail.com> wrote in message
news:f41da617.0409201017.1e09ae4a@posting.google.com...
The final piece of the puzzle was clocking source on the CSU/DSU.
Everyone was telling me to use external. The service provider was
insisting that the CSU/DSU was bad. I swapped the CSU/DSU with a
known working CSU/DSU being used on a T1 circuit and before I made any
config changes on the CSU/DSU the frame circuit started working. I
compared configurations on the CSU/DSU's and our T1's were using
internal clocking source. All is good for now. Thanks to everyone
for your suggestions and help.
"Rick" <rick.savoy@adelphia.net> wrote in message
news:<0fCdnV_TQ699_6vcRVn-qw@adelphia.com>...
Since every receive frame (11) has been discarded, I would verify that
the
provider has the LMI type the same as yours which is AnnexD.
Hope this helps,
Rick
"Carlo" <da.carlo@gmail.com> wrote in message
news:f41da617.0409010735.71d90c0a@posting.google.com...
I don't see (know) where in Site Manager you make the connection.
When I select edit circuit - services the window pops up with
201201.0.3 and the PVC is defined for this service. With the
command
show fr service the output is 201201.0.3 and is labeled
Line.LLIndex.Cct. For the comamnd show fr stats the outputs are
201201.0.0 and 201201.0.101 and are labeled Line.LLIndex.DLCI. How
would I fix this? Is the fault status anything to be concerned
about?
da.carlo@gmail.com (Carlo) wrote in message
news:<f41da617.0408311528.7d33ea26@posting.google.com>...
The routers are ARN's running Image:rev/14.00/1D5. This is a new
frame relay circuit. I ran the inst_arn.bat file, used the default
settings, then added the PVC through SM. It seems like ia am so
close
yet the frame circuit will not come up. SBC, the frame provider is
not seeing a LMI signal coming from the router. They suspect a bad
V.35 cable but the router at far end is in the same state. I don't
have any spare cables. The V.35 cables I do have were used for
normal
T1 (point to point) circuits. Does Nortel use a different cable
for
frame circuits? The CSU/DSU are Paradynes 3162's. Any ideas on
what
may be wrong?
Some stats below
$ show sync base
Line WAN
Loc Rem Med
Slot Conn Circuit State MAC Address Number MTU
Protocol
Adr Adr Typ
---- ---- -------- -------- ----------------- -------- ---- --------
--- --- ---
1 1 S11_Oak- Up 00-00-A2-FF-2D-2E 00201201 1600 FRM
RLAY
STD
landFR
1 entry(s) found
$ show frame stats
Sent Received
Line.LLIndex.DLCI Frames Octets Frames Octets
Discard
Drops
----------------- ---------- ---------- ---------- ---------- --------
--------
201201.0.0 8429 118006 11 154
11
0
201201.0.101 0 0 0 0
0
0
2 entries found
$ show frame alerts
Line.LLIndex Circuit Mgt Type Intf Type Status Faults
Discard
Drop
---------------- -------- --------- --------- -------- ------ --------
------
201201.0 S11_Oak- AnnexD Normal Fault 2
0
0
landFR
1 entry found
$ show frame service
Line.LLIndex.Cct Circuit Status Num VCs Default Multiline Name
---------------- -------- -------- ------- ------- ---------
-----------------
201201.0.3 S11_Oak- Active 1 Yes No
201201.0.3
landFR
1 entry found
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in