[j-nsp] RE : Missing interface ID in RE based sflow export from M7i
david.roy at orange-ftgroup.com
david.roy at orange-ftgroup.com
Sat May 21 12:19:26 EDT 2011
Hi,
Maybe you hit this recent PR :
JUNOS Problem Report Information
NUMBER 598135
SEVERITY major
CATEGORY sw
STATE open
SYNOPSIS CFLOW records have interface index as 0 for any interfaces with index greater than 8192
RELEASE NOTE Maximum number of service IFL's supported on M320 platform are 8192
RESOLVED IN -
ARRIVAL DATE 2011-04-05 18:53:47
LAST MODIFIED 2011-04-19 04:06:36
CLOSE DATE -
Regards,
David
________________________________________
De : juniper-nsp-bounces at puck.nether.net [juniper-nsp-bounces at puck.nether.net] de la part de Samit [janasamit at wlink.com.np]
Date d'envoi : samedi 21 mai 2011 14:07
À : juniper-nsp at puck.nether.net
Objet : [j-nsp] Missing interface ID in RE based sflow export from M7i
Hi,
I am testing the RE based flow export from my Juniper M7i running
9.2R2.15 , for some reason my flow analyzer wrapped up all the flows in
instance 0 interface for all the flows exported, at the same time all
the export from all the Cisco is working and showing up perfectly.
Upon investigating the sflow packets through wireshark, it is found that
all the captured sflow frames from M7i has Input interface and Output
interface information id is "0" thus Interface ID is not exported. Is
this the know issue or are there any configuration miss? any workaround
or fix?
###
Wireshark output:
> pdu 1/29
SrcAddr: 202.xx.xx.xx (202.xx.xx.xx)
DstAddr: 195.xx.xx.xx (195.xx.xx.xx)
NextHop: 125.xx.xx.xx (125.xx.xx.xx)
InputInt: 0 <---------- here...
OutputInt: 0 <---------- here...
Packets: 1
Octets: 48
> [Duration:0.000000000 seconds]
SrcPort: 48129
DstPort: 28158
padding
TCP Flags: 0x00
Protocol: 17
IP Tos: 0x00
####
interfaces {
ge-1/3/0 {
unit 0 {
family inet {
filter {
input all;
output all;
}
address 202.xx.xx.xx/26;
address 202.xx.xx.xx/27;
}
}
}
}
firewall {
filter all {
term all {
then {
sample;
accept;
}
}
}
}
forwarding-options {
sampling {
input {
family inet {
rate 100;
}
}
output {
cflowd 202.xxx.xxx.xxx{
port 2055;
version 5;
}
flow-inactive-timeout 15;
flow-active-timeout 60;
}
}
}
###
Chassis M7i
Midplane REV 05 M7i Midplane
Power Supply 0 Rev 05 AC Power Supply
Routing Engine REV 01 RE-850
CFEB REV 08 Internet Processor II
FPC 0 E-FPC
PIC 0 REV 09 1x G/E, 1000 BASE-SX
FPC 1 E-FPC
PIC 2 BUILTIN 1x Tunnel
PIC 3 REV 08 1x G/E, 1000 BASE
Xcvr 0 SFP-SX
Fan Tray Rear Fan Tray
###
--
Regards
Samit
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
********************************************************************************
IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles
et peuvent etre protegees par la loi.
Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus.
Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message
et tous les fichiers eventuellement attaches.
Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite.
Tout message electronique est susceptible d alteration.
A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie.
De meme, il appartient au destinataire de s assurer de l absence de tout virus.
IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is
intended only for the named recipient(s) above.
If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message.
Any unauthorized view, usage or disclosure ofthis message is prohibited.
Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified.
Additionally the recipient should ensure they are actually virus free.
********************************************************************************
More information about the juniper-nsp
mailing list