[c-nsp] AP-1242AG config
Joel Perez
tman701 at gmail.com
Wed Dec 19 15:37:11 EST 2007
Well,
Thanks to everyone who replied and helped me out on this.
I re-did it the way Anamari suggested and they are all working the way they
should be.
Both Vlans give out their respective DHCP leases as they should and now my
7921's register correctly.
I deployed 6 AP's today covering 3 separate floors and so far as of this
email they are all working correctly.
I will now be testing it throughout the week for performance issues related
to my VoIP.
Thanks again,
Joel P
On 12/18/07, Spaunhorst, Anamari <ASpaunhorst at uh.edu> wrote:
>
> Tom,
>
> Try this:
>
> version 12.3
> no service pad
> service timestamps debug datetime msec
> service timestamps log datetime msec
> service password-encryption
> !
> hostname ap
> !
> enable secret 5 $1$/zGH$xzsRGAXFpaqMQdyblohgC.
> !
> ip subnet-zero
> aaa new-model
>
> please let us know,
> Anna
>
>
>
>
>
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Joel Perez
> Sent: Tuesday, December 18, 2007 2:02 PM
> To: Tom Storey
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] AP-1242AG config
>
> Ok, tried removing BVI1 and replace it with another BVI but it isnt
> allowed
> to remove it.
> Also couldnt do "bridge-group 100 route ip" This command is only allowed
> on
> bridge-group 1.
> I ended up having to change the native vlan on the switch trunk port to
> match the IP I wanted to use for BVI1.
> It seems that cisco doesnt let you change BVI1 to match any other vlan
> unless you make that vlan the native vlan.
> For now I can reach the AP to manage it, so its a hack/workaround but
> unless
> im missing something else im stuck with only being able to use the
> native
> vlan as a management interface.
>
> Thanks for the help guys,
>
> Joel P
>
>
> On 12/17/07, Tom Storey <tom at snnap.net> wrote:
> >
> > > Hey Tom,
> > >
> > >
> > > Makes perfect sense. I tried using BVI100 but didn't add
> > > bridge-group 100 route IP.
> > >
> > > That should work exactly the way I need it. Thanks for explanation.
> > >
> > > Joel P.
> > >
> > > -----Original Message-----
> > > From: Tom Storey [mailto:tom at snnap.net]
> > > Sent: Monday, December 17, 2007 7:49 PM
> > > To: Joel P
> > > Cc: cisco-nsp at puck.nether.net
> > > Subject: Re: [c-nsp] AP-1242AG config
> > >
> > >> Hey Guys,
> > >>
> > >> ...
> > >
> > > Assuming that VLAN 100 is to be your native VLAN:
> > >
> > > * Remove interface BVI1
> > > * Remove "bridge-group 1 route ip"
> > > * Add "bridge-group 100 route ip"
> > > * Add interface BVI100 and assign IP
> > >
> > > BVI1 is linked to bridge-group 1. Typically, Fa0 would be bridged to
> > group
> > > 1, but since you are not bridging Fa0 to anything, you need to
> enable
> > > management access via a different VLAN. Using the example above, for
> > > bridge-group 100 you will need an interface by the name of BVI100 to
> > > associate it with bridge-group 100, and thus Fa0.100. You can then
> > assign
> > > an IP address as per the VLAN 100 subnet, and this should allow you
> IP
> > > management access.
> > >
> > > Thats a simple explanation, hopefully it made sense (was a quickie).
> > >
> > >
> >
> > No problems.
> >
> > If youre still stuck, I can forward you a copy of my 1242AG config.
> Ive
> > got a management address on BVI1 which is bridged to Fa0 which sits in
> > VLAN 1, my native VLAN, but it looks as though it might just be that
> you
> > are missing the right combination of commands related to the BVI and
> > bridge-group.
> >
> > Make sure to mail the list if you get it sorted :-)
> >
> > Cheers.
> >
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://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
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list