[c-nsp] unknown interface for ipv6 route in 4.2.3

[Tassos Chatzithomaoglou]

Yes, that's the LAN of the local IX.

interface TenGigE0/2/0/3.290851
 description ** GRIX **
 ipv4 address x.x.x.x/24
 ipv6 address 2001:648:2100::x/48
 flow ipv4 monitor fmm-PEER sampler sm ingress
 dot1q vlan 2908 51

Two hours ago the BGP session was reseted by the peer, so it's working again (unknown
interface has been replaced by the real interface)

RP/0/RP0/CPU0:CRS#sh route ipv6 2001:648::/32
Routing entry for 2001:648::/32
  Known via "bgp 1241", distance 200, metric 0
  Tag 5408, type external
  Installed Jan 30 18:47:22.076 for 02:06:48
  Routing Descriptor Blocks
    fe80::222:83ff:fe42:923d, from 2001:648:2100::1, via TenGigE0/2/0/3.290851
      Route metric is 0
  No advertising protos.


RP/0/RP0/CPU0:CRS#sh cef ipv6 2001:648::/32
2001:648::/32, version 2391, internal 0x14000001 (ptr 0x9d94099c) [1], 0x0 (0x9d1fd758),
0x0 (0x0)
 Updated Jan 30 18:47:22.081
 remote adjacency to TenGigE0/2/0/3.290851
 Prefix Len 32, traffic index 0, precedence routine (0), priority 4
   via fe80::222:83ff:fe42:923d, TenGigE0/2/0/3.290851, 6 dependencies, weight 0, class 0,
bgp-ext [flags 0x6020]
    path-idx 0 [0x9e0162e0 0x0]
    next hop fe80::222:83ff:fe42:923d
    remote adjacency



--
Tassos

Mikael Abrahamsson wrote on 30/1/2013 20:35:
> On Wed, 30 Jan 2013, Tassos Chatzithomaoglou wrote:
>
>> RP/0/RP0/CPU0:CRS#sh route ipv6 2001:648:2100::1
>>
>> Routing entry for 2001:648:2100::/48
>>  Known via "connected", distance 0, metric 0 (connected)
>>  Installed Jan  9 10:07:57.360 for 3w0d
>>  Routing Descriptor Blocks
>>    directly connected, via TenGigE0/2/0/3.290851
>>      Route metric is 0
>>  No advertising protos.
>
> What is the config of TenGigE0/2/0/3.290851 ? Is it really a /48 configured there
> directly on the interface?
>