Description

The following is a working configuration for TCC between GigE and ATM interfaces.

Symptoms


Solution

Topology:

router1--(ATM)---router2--(ge)---router3

The following reveals that the TCC is working as-designed, as ICMP traffic from Farha to Han can be sent and received:

user@router3# run ping 11.11.11.1    
PING 11.11.11.1 (11.11.11.1): 56 data bytes
64 bytes from 11.11.11.1: icmp_seq=0 ttl=64 time=1.034 ms
64 bytes from 11.11.11.1: icmp_seq=1 ttl=64 time=1.007 ms
64 bytes from 11.11.11.1: icmp_seq=2 ttl=64 time=1.008 ms
^C
--- 11.11.11.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.007/1.016/1.034/0.012 ms


The following output shows ICMP traffic being sent and received on router1's ATM interface:
user@router1# run monitor traffic interface at-0/2/0    
verbose output suppressed, use  detail  or  extensive for full protocol decode
Address resolution is ON. Use no-resolve to avoid any reverse lookup delay.
Address resolution timeout is 4s.
Listening on at-0/2/0, capture size 96 bytes

Reverse lookup for 11.11.11.1 failed (check DNS reachability).
Other reverse lookup failures will not be reported.
Use no-resolve to avoid reverse lookups on IP addresses.

09:35:51.451296  In IP 11.11.11.2 > 11.11.11.1: ICMP echo request, id 23073, seq 0, length 64
09:35:51.451352 Out IP 11.11.11.1 > 11.11.11.2: ICMP echo reply, id 23073, seq 0, length 64
09:35:52.451501  In IP 11.11.11.2 > 11.11.11.1: ICMP echo request, id 23073, seq 1, length 64
09:35:52.451557 Out IP 11.11.11.1 > 11.11.11.2: ICMP echo reply, id 23073, seq 1, length 64
09:35:53.452361  In IP 11.11.11.2 > 11.11.11.1: ICMP echo request, id 23073, seq 2, length 64
09:35:53.452415 Out IP 11.11.11.1 > 11.11.11.2: ICMP echo reply, id 23073, seq 2, length 64
^C
6 packets received by filter
0 packets dropped by kernel


The following output on router2 also confirms that the TCC is working as-designed:
user@router2-re0# run show connections extensive 
CCC and TCC connections [Link Monitoring On]
Legend for status (St)              Legend for connection types
UN -- uninitialized                 if-sw:  interface switching
NP -- not present                   rmt-if: remote interface switching
WE -- wrong encapsulation           lsp-sw: LSP switching
DS -- disabled                      tx-p2mp-sw: transmit P2MP switching
Dn -- down                          rx-p2mp-sw: receive P2MP switching
-> -- only outbound conn is up
<- -- only inbound  conn is up      Legend for circuit types
Up -- operational                   intf -- interface
RmtDn -- remote CCC down            tlsp -- transmit LSP
Restart -- restarting               rlsp -- receive LSP


Connection/Circuit                Type        St      Time last up     # Up trans
test                              if-sw       Up      Dec 10 16:34:14           1
  ge-0/2/0.0                        intf  Up
  at-1/0/0.0                        intf  Up
                                                                   # Paths
  Time             Event                Interface/Label            Rcv Xmt
  Dec 10 16:36:24  CCC status update  
  Dec 10 16:36:22  Interface up         ge-0/2/0.0              
  Dec 10 16:36:22  Interface down       ge-0/2/0.0              
  Dec 10 16:34:14  CCC status update  
  Dec 10 16:34:12  Interface up         ge-0/2/0.0              
  Dec 10 16:34:12  Interface up         at-1/0/0.0              
  Dec 10 16:34:12  Interface down       at-1/0/0.0              
  Dec 10 16:34:12  Interface down       ge-0/2/0.0              
  Dec 10 16:34:12  CCC status update  
  Dec 10 16:34:12  Interface down     
  Dec 10 16:34:12  Interface down       ge-0/2/0.0              
  Dec 10 16:34:12  Interface down       ge-0/2/0.0              


The following shows the relevant configuration for each node:
Router1:
interfaces { at-0/2/0 { atm-options { vpi 0; } unit 0 { vci 0.100; family inet { address 11.11.11.1/30; } } } } Router2:
interfaces { ge-0/2/0 { encapsulation ethernet-tcc; unit 0 { family tcc { proxy { inet-address 11.11.11.1; } remote { inet-address 11.11.11.2; } } } } at-1/0/0 { atm-options { vpi 0; } unit 0 { encapsulation atm-tcc-snap; vci 0.100; family tcc; } } } protocols { mpls { interface ge-0/2/0.0; interface at-1/0/0.0; } connections { interface-switch test { interface ge-0/2/0.0; interface at-1/0/0.0; } } } Router3: interfaces { ge-0/1/0 { unit 0 { family inet { address 11.11.11.2/30; } } } }


For additional information on the configuration of TCC, please refer to the URLs listed below.

Related Information