Re: IEExpert Vol 2 version 4.1 task 4.4

While the switch/vlan idea is a good one to think about, in this case it
would be a touch more difficult since that's a Serial interface. ;)

Along that same line of thinking though, check out your configuration on
the serial interface. Notice that the IP address (54.1.10.x vs.
54.1.2.x) is different. Do you have a misconfiguration? While the
backbone routers are set per rack as having different address ranges,
for the simplicity of students we have the ability of loading different
racks' configurations (so you can work on previously saved labs even
though your rack number has changed).

Peering to the backbone router, there are numerous configurations to
support multiple labs. Are you learning that address over a different
PVC (it's frame?) on that interface?

As Jared mentioned, some show commands would be a good place to start in
order to track down where that address is coming from and why.

HTH,

*Scott Morris*, CCIE/x4/ (R&S/ISP-Dial/Security/Service Provider) #4713,

JNCIE-M #153, JNCIS-ER, CISSP, et al.

JNCI-M, JNCI-ER

smorris_at_internetworkexpert.com

Internetwork Expert, Inc.

http://www.InternetworkExpert.com

Toll Free: 877-224-8987

Outside US: 775-826-4344

Knowledge is power.

Power corrupts.

Study hard and be Eeeeviiiil......

Jared Scrivener wrote:
> I'm guessing at the lab topology, but can you provide a "sh run int"
> for the interface on both neighbors? This normally occurs when using
> secondary addresses if the primary network doesn't match on both ends.
> Your output would indicate either that, or a misconfigured IP addressing.
>
> Alternatively, you may have misconfigured a switch so that a neighbor
> (you shouldn't expect to see) appears to be in the same VLAN as R6.
> This could be a misconfigured access port, or if you are lucky
> (because it is cooler) you may have managed to VLAN hop (by
> mismatching native VLANs, connecting a trunk to an access port that
> doesn't match the native or running QinQ tunnels that use overlapping
> tags between the inside tag range and the outside tag and then fed the
> outside tag into an access port with the same tag).
>
> Oh, could you explain what you meant by "sh ip eigrp neighbor" is ok?
> I'd like to see the output. If it really is OK, my last solution is
> probably right. If not, one of the first two probably is.
>
> Cheers,
>
> Jared
>
>
>
> On May 6, 2009, at 12:32 AM, kaniyath minha <minha.kaniyath_at_gmail.com>
> wrote:
>
>> Dear
>>
>>
>> I configured straight forward configuration of EIGRP on R6
>>
>> router eigrp 10
>> network 54.1.2.6 0.0.0.0
>>
>> But i am getting an error on my R6 like
>>
>> *Mar 2 02:18:26.565: IP-EIGRP(Default-IP-Routing-Table:10): Neighbor
>> 54.1.10.254 not on common subnet for Serial0/0.
>>
>> Show ip eigrp neighbor is ok.
>>
>> Please help me to solve this issue.
>>
>>
>> Thanks and Regards
>>
>> Kajaleel
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>
>
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found
> at:http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Wed May 06 2009 - 06:55:08 ART