Errata

"Because of this you'' need to use a vt (tunnel) interface or vrf-table-label .... both of which result in the packet being looped back around for a second lookup ...."

---------
Suggest replacing the text with something like this - which, of course, should be verified.

vrf-table-label does *not* loop traffic a second time through the PFE, which is the reason there is, practically speaking, no performance hit and no performance limit like there is with tunnel-services and vt interfaces.

Instead, table-label maps the inner label to an lsi unit "interface." As traffic proceeds through the Trio chipset, the outer label is popped and a separate chip performs the IP lookup, all for a single pass through Trio.

Unlike a vt, the lsi is really a configuration construct - there is no corresponding physical or virtual interface and no consumption of extra resources from the PFE.

In Chapter 7: Trio Inline Services, the J-Flow section, the stanza on pg. 597 has four errors which become apparent to the reader in the paragraph at the end stating "the only difference between the two sampling instances PEERING and TRANSIT is the inline-jflow source-address."

In the "forwarding-options" stanza, the IP addresses of the flow-server and the source-address appear to have been switched. It appears as if the addresses should read [PEERING] flow-server 10.7.255.3 and source-address 192.0.1.122, and also the [TRANSIT] section should read flow-server 10.7.255.3 and source-address 192.0.2.123.

On line two of the second code section, the command to "check to see if a connection to the flow collector has been made" is listed as:
request pfe execute target fpc0 command "show pfe manager service_thread jflow stat".

In 11.4R6.6 on an MX80, the command is:
"show pfe manager service-thread jflow stat". I cannot independently confirm that "service_thread" is applicable in any other Junos version, but a Google search for that argument as part of this command produces no results.

"CE1 is connected via IEEE802.3ad to PE1:ae1 and PE1:ae2" should be "CE1 is connected via IEEE802.3ad to PE1:ae1 and PE2:ae1"

"Both R1 and R2 have three aggregated PAGE RANGE W / 2 SUBs: Ethernet interfaces" should be "Both R1 and R2 have three aggregated Ethernet interfaces".

"The two sessions are to be expected: a session going to R3 and another going to R4" should be "The two sessions are to be expected: a session going to R3 and another going to R2". Because R1 connected only R2 and R3, not R4.