Show, Clear, Debug Commands
Page 1500 7750 SR OS Services Guide
16 2/1/3 65.10
eth-tunnel-66:3 36633 2 2/1/4 66.13
4 1/1/3 66.13
eth-tunnel-67:3 36733 2 3/1/3 16
8 1/1/2 16
eth-tunnel-68:3 36833 2 3/1/3 19
3 3/1/1 19
eth-tunnel-65:4 56554 3 2/1/4 65.11
8 1/1/3 65.11
16 2/1/3 65.11
eth-tunnel-66:4 56654 2 2/1/4 66.14
4 1/1/3 66.14
eth-tunnel-67:4 56754 2 3/1/3 17
8 1/1/2 17
eth-tunnel-68:4 56854 2 3/1/3 20
3 3/1/1 20
eth-tunnel-65:5 66565 3 2/1/4 65.12
8 1/1/3 65.12
16 2/1/3 65.12
eth-tunnel-66:5 66665 2 2/1/4 66.15
4 1/1/3 66.15
eth-tunnel-67:5 66765 2 3/1/3 18
8 1/1/2 18
eth-tunnel-68:5 66865 2 3/1/3 21
3 3/1/1 21
-------------------------------------------------------------------------------
Number of SAPs : 23
This command can also be used to identify SAPs with the “EthTunTagMismatch” flag and can be
used to prevent the flag from occurring before activating paths through the following CLI
example:
*A:Dut-C>config>service>epipe# show service sap-using eth-tunnel | match "-"
-------------------------------------------------------------------------------
eth-tunnel-1 50 1 1/1/2 4030
eth-tunnel-2 51 1 3/1/1 100
eth-tunnel-67 52 2 3/1/3 672
eth-tunnel-1:3 3133 1 1/1/2 4
eth-tunnel-2:3 3233 1 3/1/1 7
eth-tunnel-65:4094 4094 2 - 4094.*
eth-tunnel-1024:4094 4094 1 2/1/1 -
2 3/1/2 -
...
eth-tunnel-65:3 36533 3 2/1/4 65.10
eth-tunnel-66:3 36633 2 2/1/4 66.13
...
SAP eth-tunnel-1024:4094 does not have the eth-tunnel tags configured for the corresponding
paths which causes the SAP to be oper down.
Ethernet tunnel 65 does not have path 2 configured. However, SAP eth-tunnel-65:4094 has a
tag configured for path 2. This is acceptable and allows the operator to pre-provision
tags under the same-fate SAPs before the corresponding path is configured under the Ether-
net tunnel. This is the recommended configuration order so that there is no traffic dis-
ruption on the same-fate SAPs.
SAP eth-tunnel-65:5 currently has tags configured for paths 3, 8 and 16 and is operation-
ally up. Note that if path 2 of Ethernet tunnel 65 was properly configured and active, SAP
eth-tunnel-65:5 would be operationally down since it does not have a corresponding tag for
path 2.
Any other tunnel is fine since it has no dash present in the port or tag location.