I am looking for an interest feedback on this.
Would ther be an interest of low cost hot pluggable T1 and T3 cards out there??
they dont even need to be hotplug, just get some more choices of T1/E1 cards! hehehe
There are many T1/T3 to Ethernet converters (dummy converters no routing or configurations) available in the market.
we don’t use PCI cards any more because ROS v3 no more support those cards.
The 1st units I “Googled” were $1500… for a Single T…
I was thinking about 1/3 that price…
Or am I missing something…
unit price about $150 to $200
link please.
Yes! We need support for DS3 cards on Mikrotik! Production cards that is!
Matt
I was at the MUM and was told that the SBE T1s dont work under 3.x..
I was sure I had seen them work…
I did some tinkering and guess what THEY WERE CORRECT…
Here is where the plott thickens…
Under 3.0 RC9 the sriver loads and the card Inits fine…
Under 3.9, as soon as the card is enabled, “BOOM” stack trace dump and crash…
The OS is not totaly crashed but VERY close…
Just enough control to reboot…
I was under the understanding that RC9 and 3.X used the same kernal…
I can only asume that the driver version reverted to an older version or something like that…
DS3, T3/E3 Card we have, as well as up to 8 port T1 cards. However, the drivers for most of these have not been updated for the new kernel of MT in V3. So you will need to run 2.9 still for it.
We sell these quite a bit with the E3/T3 Cards.
DS3, T3/E3 Card we have, as well as up to 8 port T1 cards. However, the drivers for most of these have not been updated for the new kernel of MT in V3. So you will need to run 2.9 still for it.
Will the drivers be updated to support these in v3.x in the future? Is it the Sangoma a301 card?
Matt
My buddy has 2 of those SBE cards in 3.2 working fine.
[xxx@xxx] /interface sbe> print
Flags: X - disabled, R - running
0 R name=“CARI” mtu=1500 line-protocol=cisco-hdlc clock-rate=64000
clock-source=external crc32=no long-cable=no scrambler=no
circuit-type=t1 frame-relay-lmi-type=ansi frame-relay-dce=no
chdlc-keepalive=10s
VERY interesting though that the cards don’t show up in sys resource pci print : ?
Sam
Even more interesting…
Then the issue has been “introduced” since then…
I havent heard of a kernal update 3.X (since the betas) so I am guessing it lies in a down reved or courrupt driver…
I have scrounged up a solution that if the drivers are added… (this is a HINT John) (I showed the board to MikroTik at the MUM) …
should allow for a hot plugable T1 / T3 wan solutions…
Imagine a 19" rack mount chassis connected to your RouterOS system via USB 2.0 with multiple slots that you can plug in multiple T1 add T3 cards while the router is running !! you would be able to mix T1 and T3 cards in the same chassis..
Imagine being able to bond multiple T1s together and if a card fails, adding a new card, moving the traffic to the new port,
bringing the link back up to full speed WITHOUT POWERNG OFF !! Take that CISCO..
You would be able to provision new links with out having to have the extra ports sitting in your router idle…
Just add a card when needed, activate the port and off you go !!!
There are also plans to put a LCD for RouterOS monitering and also plans for storage (USB to IDE or SATA) (RouterOS sees USB drives as SATA) also plans for SATA based solidstate RAID in the system… PROXY / CALEA
All this and the kitchen sink as well…
If demand is great enough (and the drivers will work for the USB Ts then I will MFG the rack system)
As we move away from the phone companies, T1/T3 stuff gets less important. You do want to move away from the phone companies right? We have Ethernet uplinks to the Internet now, and I’m glad to be done with T3/T1 gear for that purpose.
i want to move away from the phone company, but in much of the US you can’t yet… I know T1s are legacy but they need to be supported for a while to come.
its getting less important only for you.. For most of us, its impossible…
For me, Im now considering 7 Powerrouters to purchase, just for E3..
In the US and western Canada, T1 and T3 (DS3) are a must have. They are the only interfaces that have a required CIR by LAW and must be returned to service before anything else, even the POTS lines.
I have had to go back to using CISCO in 100s of locations over the last 4 months because of the lack of support on T1 / T3 interfaces in the ROS 3.X series. The loss in sales for RouterOS now counts 573 units and this number will continue to grow!
You can use a small used CISCO with WAN interface modules in them. MLPPP them together. If you need some of the power of RouterOS, you can then add a RouterOS on the back side. More equipment, more rack space, more power usage. But, it is the only way at this time.
We have both T3 and T1 Support, it does work. You can put a DS3 in there as well . Worst case is you run on v2.9 as some of the drivers are older and don’t work with the newer kernal. Some though will work once you get the external clock..
MLPPP is supported in PPPOE, more feed back and we will get it on all interfaces.
That is all well and good, but MLPPP is used for aggregated operations of multi T1s and T3s all over the United States, not just PPPoE interfaces.
Moreover, ROS 2.9.51 + would be ok for most of this work. However the additional work with Firewall / hotspots and a list of other services are not COVERED BY ROS 2.9 series only the 3.X series. Thus leaving many ISPs having to return to their roots. (CISCO)
I know a very large number of ISPs would love to quite using CISCO and go to something that give more bang for the buck.
Right now, the only thing that I can think of is bonding of T1s etc. That can be done with MLPPP once they add it to the feature set for those interfaces. MLPPP on PPPOE just came out in .10, so so be so fast on that.
As far as bang for the buck, I cant think of ANYTHING like this that is cheaper, faster, or better. Unless, of course, you need to bond T1s. Use your Cisco to do that and then let the MT do all of the routing necessary!