02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Storing Last and Bad PDUs<br />

<strong>FTOS</strong> stores <strong>the</strong> last notification sent/received, and <strong>the</strong> last bad PDU received on per peer basis. The last<br />

bad PDU is <strong>the</strong> one that causes a notification to be issued. These PDUs are shown in <strong>the</strong> output of <strong>the</strong><br />

command show ip bgp neighbor, as shown in Figure 363.<br />

Figure 363 Viewing <strong>the</strong> Last Bad PDU from BGP Peers<br />

<strong>Force10</strong>(conf-router_bgp)#do show ip bgp neighbors 1.1.1.2<br />

BGP neighbor is 1.1.1.2, remote AS 2, external link<br />

BGP version 4, remote router ID 2.4.0.1<br />

BGP state ESTABLISHED, in this state <strong>for</strong> 00:00:01<br />

Last read 00:00:00, last write 00:00:01<br />

Hold time is 90, keepalive interval is 30 seconds<br />

Received 1404 messages, 0 in queue<br />

3 opens, 1 notifications, 1394 updates<br />

6 keepalives, 0 route refresh requests<br />

Sent 48 messages, 0 in queue<br />

3 opens, 2 notifications, 0 updates<br />

43 keepalives, 0 route refresh requests<br />

Minimum time between advertisement runs is 30 seconds<br />

Minimum time be<strong>for</strong>e advertisements start is 0 seconds<br />

Capabilities received from neighbor <strong>for</strong> IPv4 Unicast :<br />

MULTIPROTO_EXT(1)<br />

ROUTE_REFRESH(2)<br />

CISCO_ROUTE_REFRESH(128)<br />

Capabilities advertised to neighbor <strong>for</strong> IPv4 Unicast :<br />

MULTIPROTO_EXT(1)<br />

ROUTE_REFRESH(2)<br />

CISCO_ROUTE_REFRESH(128)<br />

For address family: IPv4 Unicast<br />

BGP table version 1395, neighbor version 1394<br />

Prefixes accepted 1 (consume 4 bytes), 0 withdrawn by peer<br />

Prefixes advertised 0, rejected 0, 0 withdrawn from peer<br />

Connections established 3; dropped 2<br />

Last reset 00:00:12, due to Missing well known attribute<br />

Notification History<br />

'UPDATE error/Missing well-known attr' Sent : 1 Recv: 0<br />

'Connection Reset' Sent : 1 Recv: 0<br />

Last notification (len 21) sent 00:26:02 ago<br />

Last PDUs<br />

ffffffff ffffffff ffffffff ffffffff 00160303 03010000<br />

Last notification (len 21) received 00:26:20 ago<br />

ffffffff ffffffff ffffffff ffffffff 00150306 00000000<br />

Last PDU (len 41) received 00:26:02 ago that caused notification to be issued<br />

ffffffff ffffffff ffffffff ffffffff 00290200 00000e01 02040201 00024003 04141414<br />

0218c0a8<br />

01000000<br />

Local host: 1.1.1.1, Local port: 179<br />

Foreign host: 1.1.1.2, Foreign port: 41758<br />

<strong>FTOS</strong> <strong>Configuration</strong> <strong>Guide</strong>, version 7.7.1.0 517

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!