[j-nsp] access-internal

[Christopher Young]

Sunny,


If there is no access-internal route in the vrf then odds are the
subscriber interface is not actually being created in the vrf. What type
of subscriber is this DHCP or PPPoX? If it's PPPoX make sure that the
profile (if used) authenticates the user and places their IP interface
in the vrf.

Can you send the subscriber interface config, profile config, domain-map
config and a note about which vr/vrf the user is being authenticated in?

Thanks,

Christopher Young
Systems Engineer
Juniper Networks 
JNCIP ERX #9
(978) 973-0574
cyoung at juniper.net
 

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
juniper-nsp-request at puck.nether.net
Sent: Monday, March 31, 2008 12:00 PM
To: juniper-nsp at puck.nether.net
Subject: juniper-nsp Digest, Vol 64, Issue 33

Send juniper-nsp mailing list submissions to
	juniper-nsp at puck.nether.net

To subscribe or unsubscribe via the World Wide Web, visit
	https://puck.nether.net/mailman/listinfo/juniper-nsp
or, via email, send a message with subject or body 'help' to
	juniper-nsp-request at puck.nether.net

You can reach the person managing the list at
	juniper-nsp-owner at puck.nether.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of juniper-nsp digest..."


Today's Topics:

   1. Re: isis adjacencies and isis database entries (Danny McPherson)
   2. access-internal (sunnyday)


----------------------------------------------------------------------

Message: 1
Date: Sun, 30 Mar 2008 10:14:38 -0600
From: Danny McPherson <danny at tcb.net>
Subject: Re: [j-nsp] isis adjacencies and isis database entries
To: snort bsd <snortbsd at yahoo.com.au>
Cc: juniper-nsp <juniper-nsp at puck.nether.net>
Message-ID: <70CDDE8F-2992-4DF0-AC40-6265FCD24588 at tcb.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes


On Mar 28, 2008, at 1:08 PM, snort bsd wrote:
> Hello, all:
>
> Shouldn't the entries in the output of "show isis adjacency" be one- 
> to-one relationship with the neighbor entries in "show isis database  
> details"?

Yes, if it's all the same level, that should be present and
reported in that level's LSP.

> Assume r1 peers with r2, r3 and r4 in level 2 (single connection to  
> each neighbor)
>
> user at r1> show isis database level 2 r1.00-00 detail
> IS-IS level 2 link-state database:
>
> r1.00-00 Sequence: 0x5a92, Checksum: 0xb28c, Lifetime: 65521 secs
>   IS neighbor: r2.00                           Metric:        10
>   IS neighbor: r3.00                           Metric:        10
>   IS neighbor: r4.00                           Metric:        10
>  ...
>
> user at r1> show isis adjacency
> Interface             System         L State        Hold (secs)  SNPA
> ge-1/0/0.0           r2                 2 Up                        18
> ge-2/2/0.0           r3                 2 Up                          
> 23
> so-0/2/0.0           r4                 2 Up                          
> 28
>
>
> but in some cases, they are not. I have one router (say r1), it has  
> adjacency with r2 (on the output of "show isis adjacency) but the r2  
> entry doesn't show up in the output of "show isis database details".
>
> user at r1> show isis adjacency
> Interface             System         L State        Hold (secs)  SNPA
> ge-1/0/0.0           r2                 2 Up                        18
> ge-2/2/0.0           r3                 2 Up                          
> 23
> so-0/2/0.0           r4                 2 Up                          
> 28
>
> user at r1> show isis database level 2 r1.00-00 detail
> IS-IS level 2 link-state database:
>
> r1.00-00 Sequence: 0x5a92, Checksum: 0xb28c, Lifetime: 65521 secs

Umm, this is the same LSP number with the same checksum
as above, and both from r1's LSDB, and the same remaining
lifetime, for that matter.  Was this perhaps at cut/paste error?

Are you suggesting that in this execution of the command the
"IS neighbor" r2.00 entry didn't exist?

>   IS neighbor: r3.00                           Metric:        10
>   IS neighbor: r4.00                           Metric:        10
> ...
>
> but on r2 router, i can see r1 entry on both outputs of "show isis  
> adjacency" and "show isis database details". also the interfaces are  
> taking traffic between r1 and r2. Why is that?

How about a "show isis adjacency" and "show isis database detail"
from both r1 and r2, with raw output.  That should illustrate the delta.

-danny


------------------------------

Message: 2
Date: Mon, 31 Mar 2008 15:12:27 +0300
From: "sunnyday" <cscosunny at gmail.com>
Subject: [j-nsp] access-internal
To: "Juniper-Nsp" <juniper-nsp at puck.nether.net>
Message-ID: <003501c89328$7e8fb020$9b1ea8c0 at mixalis>
Content-Type: text/plain;	charset="iso-8859-1"

Hello
i have a subscriber in a vrf but his ip is not shown in the routing
table as access-internal route why is that?
alla other susbscribers in another vr work fine.

------------------------------

_______________________________________________
juniper-nsp mailing list
juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

End of juniper-nsp Digest, Vol 64, Issue 33
*******************************************