Hi!
Thanks to @loopodoopo for https://github.com/librenms/librenms/pull/12432/files
I’m dealing with Hardware 7250 IXR-e, Operating System Nokia SR OS (TiMOS) 20.10.R2
I have re-discovered the device but in Device > Routing > MPLS I can’t see anything.
I can go to Routing > MPLS > SAP and I can see all SAP lines. However I can enter on any but there’s no graph, all values are 0
Can anyone give me a track?
Hi @gil.obradors,
7750 and 7250 have different OID’s for SAP traffic, I have only implemented 7750 because this is the bigger part of our network. I believe the following OID’s should be used for 7250:
Sap Ingress Forwarded In-Profile Bytes
.1.3.6.1.4.1.6527.3.1.2.4.3.6.1.12
Sap Egress Forwarded In-Profile Bytes
.1.3.6.1.4.1.6527.3.1.2.4.3.6.1.20
I’m not 100% sure if there are also counters for SAP drops as I have implemented them for 7750. Would you care to create a PR?
ack!
I’m from python and c/c++ , but I’m going to try to create PR!
Many thanks!
Oh, the topic it’s more easy to explain, more difficult to resolve.
I need sapBaseStatsIngressPchipOfferedHiPrioOctets and sapBaseStatsEgressQchipForwardedInProfOctets instead of configured in PR… This will be more complciated to manage, because every customer will have deployed differrents configurations.
Is safe and consistent to add more fields into the graph that you configured? I 'm worried about the data and time that GetBulk will consume. I don’t know the architecture of Librenms for the polling process
Do you think we can introduce this fields in your graph? Is safe?
( I have hundred of SAP lines and I will have more) My other plan is out of librenms with gRPC, but could be fine have this data into Librenms…
What do you think ?
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.3 sapBaseStatsIngressPchipOfferedHiPrioPackets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.4 sapBaseStatsIngressPchipOfferedHiPrioOctets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.19 sapBaseStatsEgressQchipForwardedInProfPackets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.20 sapBaseStatsEgressQchipForwardedInProfOctets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6 sapBaseStatsTable NODE
1.3.6.1.4.1.6527.3.1.2.4.3.6.1 sapBaseStatsEntry NODE
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.1 sapBaseStatsIngressPchipDroppedPackets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.2 sapBaseStatsIngressPchipDroppedOctets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.3 sapBaseStatsIngressPchipOfferedHiPrioPackets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.4 sapBaseStatsIngressPchipOfferedHiPrioOctets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.5 sapBaseStatsIngressPchipOfferedLoPrioPackets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.6 sapBaseStatsIngressPchipOfferedLoPrioOctets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.7 sapBaseStatsIngressQchipDroppedHiPrioPackets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.8 sapBaseStatsIngressQchipDroppedHiPrioOctets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.9 sapBaseStatsIngressQchipDroppedLoPrioPackets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.10 sapBaseStatsIngressQchipDroppedLoPrioOctets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.11 sapBaseStatsIngressQchipForwardedInProfPackets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.12 sapBaseStatsIngressQchipForwardedInProfOctets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.13 sapBaseStatsIngressQchipForwardedOutProfPackets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.14 sapBaseStatsIngressQchipForwardedOutProfOctets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.15 sapBaseStatsEgressQchipDroppedInProfPackets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.16 sapBaseStatsEgressQchipDroppedInProfOctets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.17 sapBaseStatsEgressQchipDroppedOutProfPackets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.18 sapBaseStatsEgressQchipDroppedOutProfOctets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.19 sapBaseStatsEgressQchipForwardedInProfPackets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.20 sapBaseStatsEgressQchipForwardedInProfOctets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.21 sapBaseStatsEgressQchipForwardedOutProfPackets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.22 sapBaseStatsEgressQchipForwardedOutProfOctets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.23 sapBaseStatsCustId LEAF TmnxCustId
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.24 sapBaseStatsIngressPchipOfferedUncoloredPackets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.25 sapBaseStatsIngressPchipOfferedUncoloredOctets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.26 sapBaseStatsAuthenticationPktsDiscarded LEAF Counter32
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.27 sapBaseStatsAuthenticationPktsSuccess LEAF Counter32
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.28 sapBaseStatsLastClearedTime LEAF TimeStamp
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.29 sapBaseStatsIngressCPMPackets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.30 sapBaseStatsIngressCPMPacketsHi LEAF Counter32
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.31 sapBaseStatsIngressCPMPacketsLo LEAF Counter32
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.32 sapBaseStatsIngressCPMOctets LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.33 sapBaseStatsIngressCPMOctetsHi LEAF Counter32
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.34 sapBaseStatsIngressCPMOctetsLo LEAF Counter32
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.35 sapBaseStatsIngPchipRcvdValidPkt LEAF Counter64
1.3.6.1.4.1.6527.3.1.2.4.3.6.1.36 sapBaseStatsIngPchipRcvdValidOct LEAF Counter64rrdtool does not really allow modifications of the structure. The best way to add them is to create a new rrd file. One graph can reference multiple files. Other than organization, there is no downside to multiple files.
Thanks @murrant for the hint!