Discussion:
[j-nsp] Multiple flow-servers with inline jflow on MX80
Richard Hesse
2013-07-18 22:26:47 UTC
Permalink
Does anyone know if it's possible to define multiple flow-servers when
doing inline jflow on a MX80? I know it's possible with RE-based sampling,
but I can't see anything in the docs regarding inline jflow.

I tried adding another flow-server but got this failure:

cflowd configuration error
instance "'sample-jflow" family "inet", cannot configure more than 1
ipfix collectors

A single flow-server here works fine, but I might be missing something
special for multiple servers:

flow-server X.X.X.X {
port 9993;
autonomous-system-type origin;
version-ipfix {
template {
ipv4;
}
}
}
flow-server X.X.X.Y {
port 9993;
autonomous-system-type origin;
version-ipfix {
template {
ipv4;
}
}
}
inline-jflow {
source-address Y.Y.Y.Y;
}

TIA,
-richard
louis.poncin
2013-07-19 06:58:28 UTC
Permalink
For any of your MX-series router the limitations are :
- IPFIX (RFC 5101): inline J-flow supported on MPC only => 1 collector only
- Note that only J-flow v5 and v8 are supported on RE => 8 collectors (same for MS-DPC)



-----Message d'origine-----
De?: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] De la part de Richard Hesse
Envoy??: vendredi 19 juillet 2013 00:27
??: juniper-nsp at puck.nether.net
Objet?: [j-nsp] Multiple flow-servers with inline jflow on MX80

Does anyone know if it's possible to define multiple flow-servers when doing inline jflow on a MX80? I know it's possible with RE-based sampling, but I can't see anything in the docs regarding inline jflow.

I tried adding another flow-server but got this failure:

cflowd configuration error
instance "'sample-jflow" family "inet", cannot configure more than 1 ipfix collectors

A single flow-server here works fine, but I might be missing something special for multiple servers:

flow-server X.X.X.X {
port 9993;
autonomous-system-type origin;
version-ipfix {
template {
ipv4;
}
}
}
flow-server X.X.X.Y {
port 9993;
autonomous-system-type origin;
version-ipfix {
template {
ipv4;
}
}
}
inline-jflow {
source-address Y.Y.Y.Y;
}

TIA,
-richard
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
Richard Hesse
2013-07-19 22:32:27 UTC
Permalink
So 1 collector is actually 1 flow server? I read the documentation and it
says 1 instance -- which I took to mean address family. I can understand
having only a single collection instance, but it also seems logical to have
multiple flow servers defined in that instance.

I can get around this with UDP replication strategies, I just would prefer
to do it natively.

-richard
Post by louis.poncin
- IPFIX (RFC 5101): inline J-flow supported on MPC only => 1 collector only
- Note that only J-flow v5 and v8 are supported on RE => 8 collectors (same for MS-DPC)
-----Message d'origine-----
De : juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] De la part
de Richard Hesse
Envoy? : vendredi 19 juillet 2013 00:27
? : juniper-nsp at puck.nether.net
Objet : [j-nsp] Multiple flow-servers with inline jflow on MX80
Does anyone know if it's possible to define multiple flow-servers when
doing inline jflow on a MX80? I know it's possible with RE-based sampling,
but I can't see anything in the docs regarding inline jflow.
cflowd configuration error
instance "'sample-jflow" family "inet", cannot configure more than 1 ipfix collectors
A single flow-server here works fine, but I might be missing something
flow-server X.X.X.X {
port 9993;
autonomous-system-type origin;
version-ipfix {
template {
ipv4;
}
}
}
flow-server X.X.X.Y {
port 9993;
autonomous-system-type origin;
version-ipfix {
template {
ipv4;
}
}
}
inline-jflow {
source-address Y.Y.Y.Y;
}
TIA,
-richard
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and
delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
louis.poncin
2013-07-22 07:08:47 UTC
Permalink
Well yes unfortunately this is it...

De : Richard Hesse [mailto:richard.hesse at weebly.com]
Envoy? : samedi 20 juillet 2013 00:32
Cc : juniper-nsp at puck.nether.net
Objet : Re: [j-nsp] Multiple flow-servers with inline jflow on MX80

So 1 collector is actually 1 flow server? I read the documentation and it says 1 instance -- which I took to mean address family. I can understand having only a single collection instance, but it also seems logical to have multiple flow servers defined in that instance.

I can get around this with UDP replication strategies, I just would prefer to do it natively.

-richard

On Thu, Jul 18, 2013 at 11:58 PM, <louis.poncin at orange.com<mailto:louis.poncin at orange.com>> wrote:
For any of your MX-series router the limitations are :
- IPFIX (RFC 5101): inline J-flow supported on MPC only => 1 collector only
- Note that only J-flow v5 and v8 are supported on RE => 8 collectors (same for MS-DPC)



-----Message d'origine-----
De : juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net<mailto:juniper-nsp-bounces at puck.nether.net>] De la part de Richard Hesse
Envoy? : vendredi 19 juillet 2013 00:27
? : juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>
Objet : [j-nsp] Multiple flow-servers with inline jflow on MX80

Does anyone know if it's possible to define multiple flow-servers when doing inline jflow on a MX80? I know it's possible with RE-based sampling, but I can't see anything in the docs regarding inline jflow.

I tried adding another flow-server but got this failure:

cflowd configuration error
instance "'sample-jflow" family "inet", cannot configure more than 1 ipfix collectors

A single flow-server here works fine, but I might be missing something special for multiple servers:

flow-server X.X.X.X {
port 9993;
autonomous-system-type origin;
version-ipfix {
template {
ipv4;
}
}
}
flow-server X.X.X.Y {
port 9993;
autonomous-system-type origin;
version-ipfix {
template {
ipv4;
}
}
}
inline-jflow {
source-address Y.Y.Y.Y;
}

TIA,
-richard
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net> https://puck.nether.net/mailman/listinfo/juniper-nsp

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>
https://puck.nether.net/mailman/listinfo/juniper-nsp


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
Drew Weaver
2013-07-22 12:51:21 UTC
Permalink
I get the sense that user preferences regarding how *flow works is in the MX platform is not high on their list given all of the bugs related to *flow up to 12.x

-Drew


-----Original Message-----
From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Richard Hesse
Sent: Friday, July 19, 2013 6:32 PM
To: louis.poncin at orange.com
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Multiple flow-servers with inline jflow on MX80

So 1 collector is actually 1 flow server? I read the documentation and it says 1 instance -- which I took to mean address family. I can understand having only a single collection instance, but it also seems logical to have multiple flow servers defined in that instance.

I can get around this with UDP replication strategies, I just would prefer to do it natively.

-richard
Post by louis.poncin
- IPFIX (RFC 5101): inline J-flow supported on MPC only => 1 collector only
- Note that only J-flow v5 and v8 are supported on RE => 8 collectors (same for MS-DPC)
-----Message d'origine-----
De : juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] De la
juniper-nsp at puck.nether.net Objet : [j-nsp] Multiple flow-servers with
inline jflow on MX80
Does anyone know if it's possible to define multiple flow-servers when
doing inline jflow on a MX80? I know it's possible with RE-based
sampling, but I can't see anything in the docs regarding inline jflow.
cflowd configuration error
instance "'sample-jflow" family "inet", cannot configure more than 1 ipfix collectors
A single flow-server here works fine, but I might be missing something
flow-server X.X.X.X {
port 9993;
autonomous-system-type origin;
version-ipfix {
template {
ipv4;
}
}
}
flow-server X.X.X.Y {
port 9993;
autonomous-system-type origin;
version-ipfix {
template {
ipv4;
}
}
}
inline-jflow {
source-address Y.Y.Y.Y;
}
TIA,
-richard
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
______________________________________________________________________
___________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc pas etre diffuses,
exploites ou copies sans autorisation. Si vous avez recu ce message
par erreur, veuillez le signaler a l'expediteur et le detruire ainsi
que les pieces jointes. Les messages electroniques etant susceptibles
d'alteration, Orange decline toute responsabilite si ce message a ete
altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or
privileged information that may be protected by law; they should not
be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and
delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have
been modified, changed or falsified.
Thank you.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Loading...