ARGOMENTO:

Anche la versione c7200-adventerprisek9_sna-mz.150-1.M non è esente da Bug..
9 09:49:53.207: %BGP-3-NOTIFICATION: received from neighbor 10.2.3.2 active 2/3 (BGP identifier wrong) 4 bytes AC100201
R3#
*Dec 9 09:49:53.215: %BGP_SESSION-5-ADJCHANGE: neighbor 10.2.3.2 IPv4 Unicast topology base removed from session BGP Notification received
R3#
*Dec 9 09:49:56.455: %BGP-3-NOTIFICATION: sent to neighbor 10.1.3.1 passive 2/3 (BGP identifier wrong) 4 bytes AC100201
R3#
*Dec 9 09:49:56.459: %BGP-4-MSGDUMP: unsupported or mal-formatted message received from 10.1.3.1:
FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 003A 0104 FE63 00B4 AC10 0201 1D02 0601
0400 0100 0102 0280 0002 0202 0002 0383 0100 0206 4104 0000 FE63
*Dec 9 09:49:57.335: %BGP-3-NOTIFICATION: received from neighbor 10.1.3.1 active 2/3 (BGP identifier wrong) 4 bytes AC100201
R3#
*Dec 9 09:49:57.343: %BGP_SESSION-5-ADJCHANGE: neighbor 10.1.3.1 IPv4 Unicast topology base removed from session BGP Notification received
*Dec 9 09:49:58.291: %BGP-3-NOTIFICATION: received from neighbor 10.3.4.4 active 2/3 (BGP identifier wrong) 4 bytes AC100201
R3#
*Dec 9 09:49:58.299: %BGP_SESSION-5-ADJCHANGE: neighbor 10.3.4.4 IPv4 Unicast topology base removed from session BGP Notification received
*Dec 9 09:49:59.651: %BGP-3-NOTIFICATION: sent to neighbor 10.3.4.4 passive 2/3 (BGP identifier wrong) 4 bytes AC100201

Regalati anche tu un BUG per Natale!

Mi sembra strano che tu abbia tutti questi bug perchè sono abbastanza rari. Prova con i 3750 che sono quelli con cui ho preparato la topologia del corso, trovi tutto in area download. Quei router sono pluritestati, se hai lo stesso problema anche là non si tratta di un bug di IOS ma di qualcos'altro. Il dubbio che mi viene è se hai settato correttamente l'idlepc, te ne accorgi facilmente perchè se utilizzi 6 router dovresti avere la cpu non oltre il 10%.

Errata, intendevo 3725

Martedi 10 Dicembre:
Provo il stw c3725-adventerprisek9-mz.124-15.T10.EXTRACTED...
Nessun problema riscontarto durante il funzionamneto di BGP di R1,R2,R3;R4..
Il momento fatale arriva quando stabilisco una neighbor ship tra R4/R5..l'ennesimo errore che mi si presenta con tutti glia ltri stw testati..compreso il 7200 12.4 e 7200 versione 15
A questo punto mi arrendo..dopo aver speso quasi 3 giorni come Betatester.. Ecco la configurazione dei due Router.
R4#show ip interface brief
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 10.3.4.4 YES NVRAM up up
FastEthernet0/1 10.2.4.4 YES NVRAM up up
FastEthernet1/0 10.4.5.4 YES NVRAM up up
Loopback0 172.16.0.4 YES NVRAM up up
Loopback1 172.16.1.4 YES NVRAM up up
Loopback2 172.16.2.4 YES NVRAM up up

R5#show ip interface brief
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 10.5.6.5 YES NVRAM up up
FastEthernet0/1 unassigned YES NVRAM administratively down down
FastEthernet1/0 10.4.5.5 YES NVRAM up up
Loopback0 172.16.0.4 YES NVRAM up up
Loopback1 172.16.1.4 YES NVRAM up up
Loopback2 172.16.2.4 YES NVRAM up up

R4#show running-config | section bgp
router bgp 65045
no synchronization
bgp log-neighbor-changes
network 172.16.0.4 mask 255.255.255.255
redistribute connected
neighbor EBGP_AS65123 peer-group
neighbor EBGP_AS65123 remote-as 65123
neighbor EBGP_AS65123 weight 65000
neighbor 10.2.4.2 peer-group EBGP_AS65123
neighbor 10.3.4.3 peer-group EBGP_AS65123
neighbor 10.4.5.5 remote-as 65045
distribute-list prefix NO_LINK out
no auto-summary

R5#show running-config | section bgp
router bgp 65045
no synchronization
bgp log-neighbor-changes
neighbor 10.4.5.4 remote-as 65045
no auto-summary

Le neighborship tra R4 e R5 non sale..
R4#show ip bg
R4#show ip bgp s
R4#show ip bgp summary
BGP router identifier 172.16.2.4, local AS number 65045
BGP table version is 10, main routing table version 10
9 network entries using 1080 bytes of memory
12 path entries using 624 bytes of memory
5/4 BGP path/bestpath attribute entries using 620 bytes of memory
1 BGP AS-PATH entries using 24 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
Bitfield cache entries: current 1 (at peak 1) using 32 bytes of memory
BGP using 2380 total bytes of memory
BGP activity 9/0 prefixes, 12/0 paths, scan interval 60 secs

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.2.4.2 4 65123 28 30 10 0 0 00:22:07 3
10.3.4.3 4 65123 30 30 10 0 0 00:22:05 3
10.4.5.5 4 65045 45 45 0 0 0 never Active

R5#show ip bgp s
R5#show ip bgp summary
BGP router identifier 172.16.2.4, local AS number 65045
BGP table version is 1, main routing table version 1

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.4.5.4 4 65045 46 46 0 0 0 never Active

Probabilmente dovuto all'errore già citato sopra:

R5#
*Mar 1 00:23:31.191: %BGP-3-NOTIFICATION: sent to neighbor 10.4.5.4 2/3 (BGP identifier wrong) 4 bytes AC100204
R5# FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 0104 FE15 00B4 AC10 0204 1002 0601 0400 0100 0102 0280 0002 0202 00
R5#
*Mar 1 00:23:59.219: %BGP-3-NOTIFICATION: received from neighbor 10.4.5.4 2/3 (BGP identifier wrong) 4 bytes AC100204

R4#
*Mar 1 00:22:58.435: %BGP-3-NOTIFICATION: sent to neighbor 10.4.5.5 2/3 (BGP identifier wrong) 4 bytes AC100204
R4# FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 0104 FE15 00B4 AC10 0204 1002 0601 0400 0100 0102 0280 0002 0202 00
R4#
*Mar 1 00:23:31.563: %BGP-3-NOTIFICATION: received from neighbor 10.4.5.5 2/3 (BGP identifier wrong) 4 bytes AC100204
R4#
*Mar 1 00:23:59.555: %BGP-3-NOTIFICATION: sent to neighbor 10.4.5.5 2/3 (BGP identifier wrong) 4 bytes AC100204
R4# FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 0104 FE15 00B4 AC10 0204 1002 0601 0400 0100 0102 0280 0002 0202 00
R4#
*Mar 1 00:24:30.151: %BGP-3-NOTIFICATION: sent to neighbor 10.4.5.5 2/3 (BGP identifier wrong) 4 bytes AC100204
R4# FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 0104 FE15 00B4 AC10 0204 1002 0601 0400 0100 0102 0280 0002 0202 00
...

Il problema sta negli ip duplicati, i due router hanno lo stesso router-id che di fatto viene deciso come ospf, dai gli indirizzi corretti alle loopback di R5 e vedrai che la neighborship salirà senza problemi.

Un altro problema risolto, direi che i tuoi lab stanno dando i loro frutti

Grazie della tua pazienza..per un errore tanto madornale e perseverato su più configurazioni.!