Re: [c-nsp] OSPFv3 Adjacency issues between 2921 and 3750
Hi Pete, thanks for your time. The 3750 does not respond when i try to ping ff02::5. It does however respond to the all-nodes/all-router ll Multicast address. The authentication configuration is only for ospfv2. So i think it will not make any difference.I cant try it without right now. Thanks, Peter On Tue, Jul 3, 2012 at 5:27 AM, Pete Lumbis alum...@gmail.com wrote: Any difference without authentication? Does the 3750 respond to pings to ff02::5? On Mon, Jul 2, 2012 at 4:16 PM, Peter Subnovic cnspmail...@googlemail.com wrote: Dear list members, i am having a somewhat odd issue (again) and i am out of ideas what is causing it. Let's assume the following very simple topology 2921 3750G-24PS All i want is to establish an OSPFv3 Adjacency between these two devices. Here is where the fun (headache) begins: The 2921 is running 15.1(4)M3 and the 3750G is running 12.2(55)SE5. So i configured OSPv3 on both sides on the respective Interfaces and wondered why the adjacency wont come up. After a little bit of troubleshooting it appears that the 3750G does not recognize the hello packets from the 2921. I can see in the debug output that they are received by the switch, but the OSPFv3 Process does not recognize them as such. If you need any additional input or show commands, please dont hesitate to ask. I appreciate all hints/comments. Thanks in advance, Peter ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] OSPFv3 Adjacency issues between 2921 and 3750
Thanks to Pete for the pointer, i was curios why the 3750 does not respond to ff02::5 (the 2921), so i activated the debugging for ipv6 packets again and started to ping ff02::5 from the 2921. Interestingly, i can't see the icmp packets at all (well atleast thats what the debug output is telling me on the 3750). The only thing i can see are the ospf hellos from the 2921... 2921#ping ipv6 ff02::5 size 1280 Output Interface: GigabitEthernet0/1 Type escape sequence to abort. Sending 5, 1280-byte ICMP Echos to FF02::5, timeout is 2 seconds: Packet sent with a source address of FE80::1%GigabitEthernet0/1 Request 0 timed out Request 1 timed out Request 2 timed out Request 3 timed out Request 4 timed out Success rate is 0 percent (0/5) 0 multicast replies and 0 errors. And the debug output on the 3750 looks like this: Jul 3 10:41:10.424 CEST: IPV6: source FE80::1 (GigabitEthernet1/0/24) Jul 3 10:41:10.424 CEST: dest FF02::5 Jul 3 10:41:10.424 CEST: traffic class 224, flow 0x0, len 80+14, prot 89, hops 1, forward to ulp Jul 3 10:41:20.096 CEST: IPV6: source FE80::1 (GigabitEthernet1/0/24) Jul 3 10:41:20.096 CEST: dest FF02::5 Jul 3 10:41:20.096 CEST: traffic class 224, flow 0x0, len 80+14, prot 89, hops 1, forward to ulp Regards, Peter On Tue, Jul 3, 2012 at 10:05 AM, Peter Subnovic cnspmail...@googlemail.comwrote: Hi Pete, thanks for your time. The 3750 does not respond when i try to ping ff02::5. It does however respond to the all-nodes/all-router ll Multicast address. The authentication configuration is only for ospfv2. So i think it will not make any difference.I cant try it without right now. Thanks, Peter On Tue, Jul 3, 2012 at 5:27 AM, Pete Lumbis alum...@gmail.com wrote: Any difference without authentication? Does the 3750 respond to pings to ff02::5? On Mon, Jul 2, 2012 at 4:16 PM, Peter Subnovic cnspmail...@googlemail.com wrote: Dear list members, i am having a somewhat odd issue (again) and i am out of ideas what is causing it. Let's assume the following very simple topology 2921 3750G-24PS All i want is to establish an OSPFv3 Adjacency between these two devices. Here is where the fun (headache) begins: The 2921 is running 15.1(4)M3 and the 3750G is running 12.2(55)SE5. So i configured OSPv3 on both sides on the respective Interfaces and wondered why the adjacency wont come up. After a little bit of troubleshooting it appears that the 3750G does not recognize the hello packets from the 2921. I can see in the debug output that they are received by the switch, but the OSPFv3 Process does not recognize them as such. If you need any additional input or show commands, please dont hesitate to ask. I appreciate all hints/comments. Thanks in advance, Peter ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] OSPFv3 Adjacency issues between 2921 and 3750
Long shot, but don't the 3750s have a certain SDM they need enabled to use IPv6? Chuck -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Peter Subnovic Sent: Tuesday, July 03, 2012 4:46 AM To: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] OSPFv3 Adjacency issues between 2921 and 3750 Thanks to Pete for the pointer, i was curios why the 3750 does not respond to ff02::5 (the 2921), so i activated the debugging for ipv6 packets again and started to ping ff02::5 from the 2921. Interestingly, i can't see the icmp packets at all (well atleast thats what the debug output is telling me on the 3750). The only thing i can see are the ospf hellos from the 2921... 2921#ping ipv6 ff02::5 size 1280 Output Interface: GigabitEthernet0/1 Type escape sequence to abort. Sending 5, 1280-byte ICMP Echos to FF02::5, timeout is 2 seconds: Packet sent with a source address of FE80::1%GigabitEthernet0/1 Request 0 timed out Request 1 timed out Request 2 timed out Request 3 timed out Request 4 timed out Success rate is 0 percent (0/5) 0 multicast replies and 0 errors. And the debug output on the 3750 looks like this: Jul 3 10:41:10.424 CEST: IPV6: source FE80::1 (GigabitEthernet1/0/24) Jul 3 10:41:10.424 CEST: dest FF02::5 Jul 3 10:41:10.424 CEST: traffic class 224, flow 0x0, len 80+14, prot 89, hops 1, forward to ulp Jul 3 10:41:20.096 CEST: IPV6: source FE80::1 (GigabitEthernet1/0/24) Jul 3 10:41:20.096 CEST: dest FF02::5 Jul 3 10:41:20.096 CEST: traffic class 224, flow 0x0, len 80+14, prot 89, hops 1, forward to ulp Regards, Peter On Tue, Jul 3, 2012 at 10:05 AM, Peter Subnovic cnspmail...@googlemail.comwrote: Hi Pete, thanks for your time. The 3750 does not respond when i try to ping ff02::5. It does however respond to the all-nodes/all-router ll Multicast address. The authentication configuration is only for ospfv2. So i think it will not make any difference.I cant try it without right now. Thanks, Peter On Tue, Jul 3, 2012 at 5:27 AM, Pete Lumbis alum...@gmail.com wrote: Any difference without authentication? Does the 3750 respond to pings to ff02::5? On Mon, Jul 2, 2012 at 4:16 PM, Peter Subnovic cnspmail...@googlemail.com wrote: Dear list members, i am having a somewhat odd issue (again) and i am out of ideas what is causing it. Let's assume the following very simple topology 2921 3750G-24PS All i want is to establish an OSPFv3 Adjacency between these two devices. Here is where the fun (headache) begins: The 2921 is running 15.1(4)M3 and the 3750G is running 12.2(55)SE5. So i configured OSPv3 on both sides on the respective Interfaces and wondered why the adjacency wont come up. After a little bit of troubleshooting it appears that the 3750G does not recognize the hello packets from the 2921. I can see in the debug output that they are received by the switch, but the OSPFv3 Process does not recognize them as such. If you need any additional input or show commands, please dont hesitate to ask. I appreciate all hints/comments. Thanks in advance, Peter ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] OSPFv3 Adjacency issues between 2921 and 3750
Hi Chuck, yes you have to configure a specific SDM template (and reboot the device) in order to use IPv6. I have already activated this, otherwise the 3750 does not recognize any IPv6 commands. 3750#show sdm prefer The current template is desktop IPv4 and IPv6 routing template. Thanks for your time. Regards, Peter On Tue, Jul 3, 2012 at 11:43 AM, Chuck Church chuckchu...@gmail.com wrote: Long shot, but don't the 3750s have a certain SDM they need enabled to use IPv6? Chuck -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Peter Subnovic Sent: Tuesday, July 03, 2012 4:46 AM To: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] OSPFv3 Adjacency issues between 2921 and 3750 Thanks to Pete for the pointer, i was curios why the 3750 does not respond to ff02::5 (the 2921), so i activated the debugging for ipv6 packets again and started to ping ff02::5 from the 2921. Interestingly, i can't see the icmp packets at all (well atleast thats what the debug output is telling me on the 3750). The only thing i can see are the ospf hellos from the 2921... 2921#ping ipv6 ff02::5 size 1280 Output Interface: GigabitEthernet0/1 Type escape sequence to abort. Sending 5, 1280-byte ICMP Echos to FF02::5, timeout is 2 seconds: Packet sent with a source address of FE80::1%GigabitEthernet0/1 Request 0 timed out Request 1 timed out Request 2 timed out Request 3 timed out Request 4 timed out Success rate is 0 percent (0/5) 0 multicast replies and 0 errors. And the debug output on the 3750 looks like this: Jul 3 10:41:10.424 CEST: IPV6: source FE80::1 (GigabitEthernet1/0/24) Jul 3 10:41:10.424 CEST: dest FF02::5 Jul 3 10:41:10.424 CEST: traffic class 224, flow 0x0, len 80+14, prot 89, hops 1, forward to ulp Jul 3 10:41:20.096 CEST: IPV6: source FE80::1 (GigabitEthernet1/0/24) Jul 3 10:41:20.096 CEST: dest FF02::5 Jul 3 10:41:20.096 CEST: traffic class 224, flow 0x0, len 80+14, prot 89, hops 1, forward to ulp Regards, Peter On Tue, Jul 3, 2012 at 10:05 AM, Peter Subnovic cnspmail...@googlemail.comwrote: Hi Pete, thanks for your time. The 3750 does not respond when i try to ping ff02::5. It does however respond to the all-nodes/all-router ll Multicast address. The authentication configuration is only for ospfv2. So i think it will not make any difference.I cant try it without right now. Thanks, Peter On Tue, Jul 3, 2012 at 5:27 AM, Pete Lumbis alum...@gmail.com wrote: Any difference without authentication? Does the 3750 respond to pings to ff02::5? On Mon, Jul 2, 2012 at 4:16 PM, Peter Subnovic cnspmail...@googlemail.com wrote: Dear list members, i am having a somewhat odd issue (again) and i am out of ideas what is causing it. Let's assume the following very simple topology 2921 3750G-24PS All i want is to establish an OSPFv3 Adjacency between these two devices. Here is where the fun (headache) begins: The 2921 is running 15.1(4)M3 and the 3750G is running 12.2(55)SE5. So i configured OSPv3 on both sides on the respective Interfaces and wondered why the adjacency wont come up. After a little bit of troubleshooting it appears that the 3750G does not recognize the hello packets from the 2921. I can see in the debug output that they are received by the switch, but the OSPFv3 Process does not recognize them as such. If you need any additional input or show commands, please dont hesitate to ask. I appreciate all hints/comments. Thanks in advance, Peter ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] Netflow + MPLS issue on PE routers
Hello! We are exporting netlfow statistic from our PE routers (C7600). We use flow export v5. Netflow collector is Flow-capture. We observed that statistic which we exported are not correct. Too small amounts of traffic in statistic compared to the actual value PHP is disabled on PE routers (for some reason) so packages have MPLS header. We think this is main cause why we didn't receive properly statistics. But PHP must be disabled for us. My question is: What should we do to recive a correct statistic? Could we enable only flow export v9 to fix that? or maybe Could we enable only ip flow egress per downlink interfaces? If this possible for 7600. What are you think about MPLS-aware NetFlow? Could it to help us? Thanks in advance. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Netflow + MPLS issue on PE routers
On 03/07/2012 11:18, Anrey Teslenko wrote: We observed that statistic which we exported are not correct. Too small amounts of traffic in statistic compared to the actual value This is a FAQ. Please check the cisco-nsp archives for why this is happening. Nick ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Netflow + MPLS issue on PE routers
Hi, This always comes up... Try adding this command mls nde sender should be OK then... Ciao JC -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Anrey Teslenko Sent: Tuesday, July 03, 2012 12:19 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Netflow + MPLS issue on PE routers Hello! We are exporting netlfow statistic from our PE routers (C7600). We use flow export v5. Netflow collector is Flow-capture. We observed that statistic which we exported are not correct. Too small amounts of traffic in statistic compared to the actual value PHP is disabled on PE routers (for some reason) so packages have MPLS header. We think this is main cause why we didn't receive properly statistics. But PHP must be disabled for us. My question is: What should we do to recive a correct statistic? Could we enable only flow export v9 to fix that? or maybe Could we enable only ip flow egress per downlink interfaces? If this possible for 7600. What are you think about MPLS-aware NetFlow? Could it to help us? Thanks in advance. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] OSPFv3 Adjacency issues between 2921 and 3750
On Tue, 2012-07-03 at 05:43 -0400, Chuck Church wrote: Long shot, but don't the 3750s have a certain SDM they need enabled to use IPv6? And on that note, what about MLS QoS on the 3750? I seem to recall having debugged something that turned out to be much (all?) IPv6 traffic ending up in queue 3 or 4, and we have set buffer sizes for these to 0. Does no mls qos make any difference? (If it's enabled of course.) -- Peter ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] OSPFv3 Adjacency issues between 2921 and 3750
Hi Peter, thank you for your suggestion. Unfortunately QoS is disabled on the 3750. 3750#show mls qos QoS is disabled QoS ip packet dscp rewrite is enabled 3750#show mls qos interface g1/0/24 GigabitEthernet1/0/24 QoS is disabled. Kind regards, Peter On Tue, Jul 3, 2012 at 1:49 PM, Peter Rathlev pe...@rathlev.dk wrote: On Tue, 2012-07-03 at 05:43 -0400, Chuck Church wrote: Long shot, but don't the 3750s have a certain SDM they need enabled to use IPv6? And on that note, what about MLS QoS on the 3750? I seem to recall having debugged something that turned out to be much (all?) IPv6 traffic ending up in queue 3 or 4, and we have set buffer sizes for these to 0. Does no mls qos make any difference? (If it's enabled of course.) -- Peter ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Netflow + MPLS issue on PE routers
This command was enabled. Perhaps in my router there is software bug. I have empty counter in NDE, but for flow export counter is not empty sh mls nde Netflow Data Export enabled Exporting flows to yy.yy.yy.yy (nnn) Exporting flows from xx.xx.xx.xx (nnn) Version: 5 Layer2 flow creation is disabled Layer2 flow export is disabled Include Filter not configured Exclude Filter not configured Total Netflow Data Export Packets are: 0 packets, 0 no packets, 0 records sh ip flow export Flow export v5 is enabled for main cache Export source and destination details : VRF ID : Default Source(1) xx.xx.xx.xx (Loopback0) Destination(1) yy.yy.yy.yy (nnn) Version 5 flow records, origin-as 5457 flows exported in 185 udp datagrams 2012/7/3, JC Cockburn ccie15...@gmail.com: Hi, This always comes up... Try adding this command mls nde sender should be OK then... Ciao JC -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Anrey Teslenko Sent: Tuesday, July 03, 2012 12:19 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Netflow + MPLS issue on PE routers Hello! We are exporting netlfow statistic from our PE routers (C7600). We use flow export v5. Netflow collector is Flow-capture. We observed that statistic which we exported are not correct. Too small amounts of traffic in statistic compared to the actual value PHP is disabled on PE routers (for some reason) so packages have MPLS header. We think this is main cause why we didn't receive properly statistics. But PHP must be disabled for us. My question is: What should we do to recive a correct statistic? Could we enable only flow export v9 to fix that? or maybe Could we enable only ip flow egress per downlink interfaces? If this possible for 7600. What are you think about MPLS-aware NetFlow? Could it to help us? Thanks in advance. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Netflow + MPLS issue on PE routers
On 03/07/12 14:44, Anrey Teslenko wrote: This command was enabled. Perhaps in my router there is software bug. I have empty counter in NDE, but for flow export counter is not empty You haven't given enough information to help you. The counters are too small - what does that mean? Be specific. Give an example, and show the interface config / routing topology for the hosts in the example. What linecards are you using? LAN cards, SIP, ES+, what? ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] ME3600X IOS Version
Hi Faruk, The fix for the ddts reported in the SR will be integrated in the following releases, *15.2(2)S2 - August 2012 *15.2(4)S - July 30th 2012 *15.1(2)EY3 - Already posted on CCO Regards, Waris -Original Message- From: faruk.sej...@bhtelecom.ba [mailto:faruk.sej...@bhtelecom.ba] Sent: Monday, July 02, 2012 2:11 PM To: Waris Sagheer (waris) Cc: cisco-nsp@puck.nether.net; cisco-nsp-requ...@puck.nether.net Subject: Re: [c-nsp] ME3600X IOS Version Hi Waris, It is SR 620762785 Tnx in advance Regards, Faruk On 2.7.2012 10:56, Waris Sagheer (waris) wrote: Faruk, Can you send me the SR number for the following issue? It should be fixed in 15.2(2)S too. Let me confirm the release and will get back to you. Regards, Waris -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Faruk Sejdic Sent: Monday, June 25, 2012 4:22 AM To: cisco-nsp@puck.nether.net Cc: cisco-nsp-requ...@puck.nether.net Subject: Re: [c-nsp] ME3600X IOS Version It's hard to say, we're still waiting for right release. :( We already tried all this versions but all of them have serious bugs. Even with new 15.2(2)S1 we hit a bug with Multicast Traffic Failure on EVC Interface In general, if you have EVC on interface configured with IPTV VLAN (mostly multicast traffic) and tried to add this EVC to an other interface multicast stops. Cisco TAC says this should be fixed in 15.2(4)S. :) Regards Faruk I'd recommend 15.2(2)S1. 15.1(2)EY is a branch release which probably won't have a long lifespan now that these switches have been integrated into mainline S code. 15.2(2)S1 has been solidly stable for us with the exception of what appears to be a cosmetic bug in that these messages are printed to the console: Jun 25 17:10:02.164: %SFF8472-3-THRESHOLD_VIOLATION: Te0/2: Rx power high alarm; Operating value: 1.4 dBm, Threshold value: 0.0 dBm. I vaguely recall seeing a DDTS Caveat about this problem too. Otherwise all good, no other issuesand really like the hardware. Reuben On 25/06/2012 5:08 PM, Ivan wrote: Hi, I know the ME3600X has come up quite a lot recently on this list, but as far as I recall and can find, it has been a while since there have been any comments regarding the best/most stable version. I am currently running 151-2.EY but will deploying some more hardware shortly and would be interested what versions others are successfully using, especially 15.2S or 15.2S1. 151-2.EY has been good so far but I am aware of the rapid development on software for this platform and also that there are quite a few issues around. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
[c-nsp] TDMOP solution
Hello Cisco-NSP community: I am looking into product selection for a TDM over IP solution (specifically channelized DS3 M23 framed). Does anyone have any recommends on the Cisco side (or even non-Cisco) for performing TDM circuit transportation over IP ? I did some research and came across a non-Cisco product RAD Data Communications GMUX-2000 which can supposedly perform the TDMOP functions but I have never worked with their gear before so have no previous experience w/ this company and their product. Also I am curious if anyone has any recommendations from the Cisco side (as that is where my experience lies). I would think an MPLS enabled core would be prerequisite in order to tunnel TDM traffic across an IP infrastructure with appropriate translation devices. Thanks, Rich ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] TDMOP solution
hey, I did some research and came across a non-Cisco product RAD Data Communications GMUX-2000 which can supposedly perform the TDMOP functions but I have never worked with their gear before so have no previous experience w/ this company and their product. Stay away from RAD - horrible software quality. Pressing back button in web interface (because CLI is even more horrible) at the wrong time locks up whole management and is resolvable only by box reboot, just as an example. They also don't have full TDMoMPLS implementation for most devices, only static labels. Also I am curious if anyone has any recommendations from the Cisco side (as that is where my experience lies). I would think an MPLS enabled core would be prerequisite in order to tunnel TDM traffic across an IP infrastructure with appropriate translation devices. From Cisco ASR901/903 but I suggest you to consider Alcatel 7705 SAR (which we are using very successfully). Technically MPLS is not needed, there is also pure IP or GRE encapsulation available for some vendors but YMMV regarding interop, MPLS is really the safest way. -- tarko ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] TDMOP solution
Agree with Tarko on RAD, stay away from them. We've been using the Cisco MWR2941 for a while now to transport E1 with CEoMPLS. We're using BITS to synchronise the clock and Sync-E as well as IEEE 1588 v2 (PTP v2) for places where we can't use Sync-E, mostly on leased circuits. You should familiarise yourself with the various clocking methods available, and which you can use or should use. How important that is to you and which protocol you can use depends on how timing sensitive your TDM applications are and what sort of circuits you are running over. The concept works fine, but the MWR2941 has many limitations. The MWR2941 is a toaster, it was built to perform a specific task and does not do much outside of that exact scope, don't expect to be able to use it as a general router. It also can't do anything but E1/T1 so it probably doesn't suit your needs. The ASR901 only does E1/T1 like the MWR2941, it has 16 E1/T1 ports, again like the MWR2941. The ASR903 can do 4*OC-3 (STM-1) or 1*OC-12 (STM-4), not DS3 however so you would need a physical STM-1 interface. You should double and triple-check with Cisco or any other vendor that they support the framing you intend to use as well as any physical interface type and I would get your Cisco or other vendor account manager to lend you a couple of boxes so you can try out what you're going to do in a real environment before committing to anything. I should also point out the ME3600X 24CX which is an ME3600X switch with 16 T1/E1 ports as well as 4 OC-3 ports that can be used for this purpose as well, I believe the software has a bit of catching up to do there, so if you need this right now it might not be able to do everything you need to do right away. Have no experience with other vendors, Tarko pointed out the Alcatel solution, I'm sure more will chime in. Kind regards, Sibbi On 3.7.2012 19:44, Tarko Tikan ta...@lanparty.ee wrote: hey, I did some research and came across a non-Cisco product RAD Data Communications GMUX-2000 which can supposedly perform the TDMOP functions but I have never worked with their gear before so have no previous experience w/ this company and their product. Stay away from RAD - horrible software quality. Pressing back button in web interface (because CLI is even more horrible) at the wrong time locks up whole management and is resolvable only by box reboot, just as an example. They also don't have full TDMoMPLS implementation for most devices, only static labels. Also I am curious if anyone has any recommendations from the Cisco side (as that is where my experience lies). I would think an MPLS enabled core would be prerequisite in order to tunnel TDM traffic across an IP infrastructure with appropriate translation devices. From Cisco ASR901/903 but I suggest you to consider Alcatel 7705 SAR (which we are using very successfully). Technically MPLS is not needed, there is also pure IP or GRE encapsulation available for some vendors but YMMV regarding interop, MPLS is really the safest way. -- tarko ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
