B38510 at freescale
Mar 14, 2012, 4:56 AM
Views: 276
Permalink
|
|
Re: Capabilities Not Negotiated] BGPD not sending NOTIFICATION message with Error Subcode Unsupported Optional Parameter
|
|
Hi All,
Please find the problem that we are observing at out lab, please respond if there are any suggestions
Test Setup:
TR2(192.168.1.100)--------(192.168.1.1)TR1
Here, TR1 and TR2 uses quagga routing suite.
Test procedure:
1. Quagga and TR1 are configured as external peers.
2. TR1 does not support Capabilities Negotiation.
3. BGP is started on the routers.
4. Wait for the OPEN messages to be sent and check the packets.
TR1 quagga Configuration:
quagga-router(config-router)# do sh run
Building configuration...
Current configuration:
!
hostname Router
hostname bgpd
log stdout
bgp config-type cisco
hostname quagga-router
!
password zebra
enable password zebra
!
interface eth0
ipv6 nd suppress-ra
!
interface eth1
ipv6 nd suppress-ra
!
interface eth2
ipv6 nd suppress-ra
!
interface lo
!
interface sit0
ipv6 nd suppress-ra
!
router bgp 6300
no synchronization
bgp router-id 3.3.3.3
network 1.1.1.0 mask 255.255.255.0
neighbor 192.168.1.100 remote-as 6200
neighbor 192.168.1.100 dont-capability-negotiate
no auto-summary
!
line vty
!
end
TR2 Quagga Configuration:
router bgp 6200
no synchronization
bgp router-id 2.2.2.2
neighbor 192.168.1.1 remote-as 6300
neighbor 192.168.1.1 strict-capability-match
no auto-summary
!
Please find the attached wireshark captured file between TR2 and TR1.
Issue:
TR2 sent an OPEN message containing the Capabilities Optional Parameter. TR1
doesnot close the connection by sending the NOTIFICATION message with Error
Subcode Unsupported Optional Parameter.
Observation:
TR1 and TR2 has established the BGP session but when BGP Update is sent from
TR1 to TR2, TR2 sends the NOTIFICATION message with Error Subcode Malformed
ASPATH and Malformed Attribute List.
Please find the attached captured wireshark for more details.
Expected Result:
TR2 should send an OPEN message containing the Capabilities Optional Parameter.
TR1 should close the connection sending the NOTIFICATION message with Error
Subcode Unsupported Optional Parameter. Upon receipt of the NOTIFICATION
message, TR2 should attempt to reestablish the connection, without sending the
Capabilities Optional Parameter.
Regards,
-Vamsi
|
Re: Capabilities Not Negotiated] BGPD not sending NOTIFICATION message with Error Subcode Unsupported Optional Parameter
