[c-nsp] multicast issue

[Thong Hawk Yen]

Hi,

Our version is video verifier which is specially design for IPTV.  I am not sure if they have a version that do non-video multicast.
You might want to have a look at their range of  product at their homepage at  http://www.exfo.com/

Regards
Amos Thong

________________________________
From: dim0sal [mailto:dim0sal at hotmail.com]
Sent: Wednesday, July 17, 2013 11:53 PM
To: Thong Hawk Yen; cisco-nsp at puck.nether.net
Subject: R: RE: [c-nsp] multicast issue

Hi
Is brixvision suitable also for not iptv mcast flows?
We run financial market mcast flows. ..

Tks



Sent with Mobile


-------- Messaggio originale --------
Da: Thong Hawk Yen <hawk.yen.thong at time.com.my>
Data:
A: R S <dim0sal at hotmail.com>,cisco-nsp at puck.nether.net
Oggetto: RE: [c-nsp] multicast issue


Hi,

We run a BGP NG-MVPN for IPTV content delivery, with Juniper MX480 in the PE layer and Cisco CRS in the P layer. With RSVP-TE P2MP LSP running from the Sender PE ( which is connecting to the multicast upstream HE router ) to the Receiver PE routers ( with downstream GPON IPTV subscribers ).

We have BrixVision IPTV probes at the Sender PE router before the traffic enter our MPLS cloud and the same type of probes at Receiver PE routers.
So far there is no need for IPTV probes along the RSVP-TE P2MP LSP path. This will help to determine the traffic quality in the IP/MPLS core.

At the downstream we have STB probe aka Single Channel Probe from the same brand deployed at the customer's place if there is a picture quality complaint. This will help us to determine issue from receiver PE router through the GPON networks towards the customer home.

We had evaluated Ineoquest before, however we found Brixvision was more suitable to our environment.

In the early stage of deployment we kept our eye on the IAT and MLR on the probe almost everyday. The Brixvision has very detail real time zoomed-in analysis like TS Sync, PAT, CRC and etc per group.

Hope this help.

Regards
Amos Thong

-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of R S
Sent: Wednesday, July 17, 2013 12:53 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] multicast issue

Hi all

Just a brainstorming and your possible help.


I manage a network where multicast is the most important traffic and
sometimes I get issue by customer where they state that some packets are lost...


Does anybody have an idea or can help me in understanding a possible
solution in monitoring traffic in real time manner, maybe with the use of some
software or appliance or whatelse.

In my idea I could monitor traffic on the source and on the destination,
then with  a sort of parsing understand
if it's my network loosing the packets or not...



Any idea ? suggestion ?


tks
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

________________________________

CONFIDENTIALITY
-------------------------
The contents of and any attachments to this email are private and confidential. If you are not the intended recipient or addressee indicated in this message, please notify the sender of the error and destroy the email and any attachments. Please do not reproduce the contents of the email or its attachments as such reproduction is a breach of confidentiality and for which legal action including injunctive relief may be sought against you. If it is your company policy that official communications are not by email, please advise immediately. Any opinions, conclusions and other information in this message that do not relate to the official business of TIME dotCom shall be understood as neither given nor endorsed by TIME dotCom, nor shall TIME dotCom shall be liable (directly or vicariously) for such opinions, statements or communications.

________________________________

CONFIDENTIALITY
-------------------------
The contents of and any attachments to this email are private and confidential. If you are not the intended recipient or addressee indicated in this message, please notify the sender of the error and destroy the email and any attachments. Please do not reproduce the contents of the email or its attachments as such reproduction is a breach of confidentiality and for which legal action including injunctive relief may be sought against you. If it is your company policy that official communications are not by email, please advise immediately. Any opinions, conclusions and other information in this message that do not relate to the official business of TIME dotCom shall be understood as neither given nor endorsed by TIME dotCom, nor shall TIME dotCom shall be liable (directly or vicariously) for such opinions, statements or communications.