[nsp] atm map-list command

[Charles Sprickman]

On Sat, 29 Mar 2003, Scott Morris wrote:

> Actually, your subinterface has a 'map-group foo' command on it.
> Separate in your config, you have the 'map-list foo' with the statements
> that you indicate.

Yes, that is correct.

> But you are correct that the list would indicate the IP address of the
> other side.  Very similar to the way that 'frame-relay map ip'
> statements map the other side's reachable IP to a DLCI.

What the big question is, is does this actually do anything.  I know if I
leave the map-list out, everything still works.  But the previous admin
was under the impression this would "lock" an IP to a pvc.  From what I'm
seeing, this is not correct.

> If you don't want to use the map-lists, you can map individual pvc's in
> the "new" method.
>
> Interface atm2/0/1.101
>  pvc 4/40
>   encapsulation aal5snap
>   protocol ip 192.168.0.2 broadcast
>  pvc 4/41
>   encapsulation aal5snap
>   protocol ip 192.168.0.3 broadcast

Nifty.  Thanks for the tip!

C

> Etc.
>
>
> Scott Morris, MCSE, CCDP, CCIE³ (R&S/ISP-Dial/Security) #4713, CCNA-WAN
> Switching, Security Specialist, Cable Communications Specialist, IP
> Telephony Support Specialist, IP Telephony Design Specialist, CISSP
> CCSI #21903
> swm at emanon.com
>
>
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Charles
> Sprickman
> Sent: Saturday, March 29, 2003 4:20 AM
> To: cisco-nsp at puck.nether.net
> Subject: [nsp] atm map-list command
>
>
> Hi,
>
> While I've not been able to track it down in the 12.2 config/command
> references (had to resort to outside sources), I'm wondering if my idea
> of what this does is correct.
>
> In the following example, there are a group of adsl customers coming in
> one per pvc on an atm subinterface.  They all have manually-assigned
> static IPs, and the subinterface has a "map-list foo" statement on it,
> with map list "foo" looking like:
>
> ip 192.168.0.2 atm-vc 102 broadcast
> ip 192.168.0.3 atm-vc 103 broadcast
> etc.
>
> This implies that I'm "locking" an IP to a particular PVC, but absent
> the docs (which oddly only list this as a frame relay command for 12.2),
> I'm not positive this is actually doing anything.
>
> Can anyone clarify this issue?
>
> We will, as time permits, be moving all adsl customers to RBE, and I
> assume that at that point this will all be moot.
>
> Thanks,
>
> Charles
>
> --
> Charles Sprickman
> spork at inch.com
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>