Re: [j-nsp] MACsec interoperability between MX10003 and Cisco ASR 9k?
Hello, Am 24.09.18 um 23:29 schrieb Christian Seitz: > I'm currently trying to find out if somebody has already tested if MACsec can > be used on a 100G port between MX10003 and Cisco ASR 9k (required licenses > will be installed on both routers). Yes, MACsec is a standard, but... ;-) > > Unfortunately Juniper currently has no MX10003 available in the loaner pool. > They have an MX10003 in their lab in Amsterdam, but no ASR 9k. Therefore I > cannot test is by myself and hope somebody else already made some experience. nobody answered this email yet so I would like to answer it myself in case somebody else is interested in this information. Juniper was now able to deliver a loaner so we could test MACsec between the MX10003 and an ASR 9910. As long as your JunOS is recent enough that PR1336834 ("MACSec AES-GCM-256 hashing algorithm is not compatible with other vendors") is fixed and your IOS XR has fixed CSCvg91792 ("STARLORD MACSEC - ARP is not resolved in Octane starlord interop") MACsec just works. I have tested AES-256 between both boxes on a 100G interconnect and unicast and multicast traffic pass the link. Thanks and regards, Chris ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] How to trim the text node of a specific element node in SLAX node-set?
Hi! I need to trim the text node of a specific element node in SLAX. All other elements should remain as in the original node-set. At the moment, I do it like this: $ cat trim_node-set.slax version 1.2; main { var $alphabet := { { { "bbb "; "ccc "; } { "ddd "; "fff "; } } } var $alphabet_trimmed := { { for-each ( $alphabet/letters/consonants ) { { for-each ( * ) { if ( name() == "d" ) { translate(.," ", ""); } else { copy-of .; } } } } } } copy-of $alphabet_trimmed; } $ As seen above, if element node is , then space characters are removed. Output of this script can be seen below: $ slaxproc -g -E trim_node-set.slax bbb ccc ddd fff $ Is there a more elegant way to do this? In addition, if I do the same for rpc-reply, then for some reason, every element node gets the 'xmlns:junos="http://xml.juniper.net/junos/*/junos;' attribute node. Just out of curiosity, why does this happen? As seen in the output above, this does not happen in slaxproc, i.e , and do not get any attribute nodes added. thanks, Martin ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp