Circuit Emulation over IP

Unanswered Question
May 29th, 2008

I have a NM-CEM-4TE1 installed and would like to know if I can run 4 point-to-point circuits to a single location and utilize all 6MB of bandwidth as a single pipe.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 1 (3 ratings)
Loading.
b.mcmurry Thu, 05/29/2008 - 13:16

This will not work with the CEM T1 card. The current scenario is running circuit emulation over IP on one T1. I wnat to add three more for a total of four and utilize 6MB of bandwidth for CEoIP

Paolo Bevilacqua Thu, 05/29/2008 - 17:00

May be I didn't I didn't understood your question, can you explain in different words what you need to do, what is connected to what.

b.mcmurry Mon, 06/09/2008 - 06:59

I have 4 T1 circuits that are Point-To-Point circuits. I have two routers with the config below. I have not been able to bring up the connection using CEMoIP. Is there something I am missing.

"ROUTER A"

controller T1 1/0

framing esf

cem-group 0 timeslots 1-24

clock source internal

cablelength long 0db

!

controller T1 1/1

framing esf

cem-group 0 timeslots 1-24

clock source internal

cablelength long 0db

!

controller T1 1/2

framing esf

cem-group 0 timeslots 1-24

clock source internal

cablelength long 0db

!

controller T1 1/3

framing esf

cem-group 0 timeslots 1-24

clock source internal

cablelength long 0db

!

cem 1/0/0

xconnect 192.168.20.1 0 encapsulation udp

local ip addr 192.168.10.1

local udp port 15901

remote udp port 15902

!

cem 1/1/0

xconnect 192.168.20.1 0 encapsulation udp

local ip addr 192.168.10.1

local udp port 15903

remote udp port 15904

!

cem 1/2/0

xconnect 192.168.20.1 0 encapsulation udp

local ip addr 192.168.10.1

local udp port 15905

remote udp port 15906

!

cem 1/3/0

xconnect 192.168.20.1 0 encapsulation udp

local ip addr 192.168.10.1

local udp port 15907

remote udp port 15908

!

interface Loopback1

ip address 192.168.10.1 255.255.255.255

!

******************************************************************************

"ROUTER B"

controller T1 1/0

framing esf

cem-group 0 timeslots 1-24

clock source adaptive 0 closed-loop

cablelength long 0db

!

controller T1 1/1

framing esf

cem-group 0 timeslots 1-24

clock source adaptive 0 closed-loop

cablelength long 0db

!

controller T1 1/2

framing esf

cem-group 0 timeslots 1-24

clock source adaptive 0 closed-loop

cablelength long 0db

!

controller T1 1/3

framing esf

cem-group 0 timeslots 1-24

clock source adaptive 0 closed-loop

cablelength long 0db

!

cem 1/0/0

xconnect 192.168.10.1 0 encapsulation udp

local ip addr 192.168.20.1

local udp port 15902

remote udp port 15901

!

cem 1/1/0

xconnect 192.168.10.1 0 encapsulation udp

local ip addr 192.168.20.1

local udp port 15904

remote udp port 15903

!

cem 1/2/0

xconnect 192.168.10.1 0 encapsulation udp

local ip addr 192.168.20.1

local udp port 15906

remote udp port 15905

!

cem 1/3/0

xconnect 192.168.20.1 0 encapsulation udp

local ip addr 192.168.10.1

local udp port 15908

remote udp port 15907

!

interface Loopback1

ip address 192.168.20.1 255.255.255.255

*********************************************

Paolo Bevilacqua Mon, 06/09/2008 - 07:14

Hi, if you're trying to connect the two routers over the WAN T1 circuits, using the CEM interfaces, I don't think is not possible to do so.

To confirm that, confirm that is not possible to configure a channel-group under controller T1.

The CEM interfaces can be used only to connect devices for which you want to provide CEM services, and not as WAN interface for general network connectivity.

Paolo Bevilacqua Mon, 06/09/2008 - 07:28

Hi, as mentioned before, the point is that the T1 controllers for the CEM card are meant to to be connected to device for which you are providing CEM.

It cannot be used for general WAN connectivity as you can note that by lack of any IP-configurable interface.

Paolo Bevilacqua Mon, 06/09/2008 - 10:01

The mentioned product appears to be equivalent to the NM that provided circuit emulation services within the familiar IOS infrastructure.

The point here is that from my understanding, a "wrong use" was attempted for the CEM interfaces.

Actions

This Discussion