24.10.2014 Views

Download complete user manual (PDF). - Brocade

Download complete user manual (PDF). - Brocade

Download complete user manual (PDF). - Brocade

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuring Multicast Source Discovery Protocol (MSDP) 3<br />

Table 23 describes the output from this command.<br />

TABLE 23<br />

This field...<br />

MSDP peer information<br />

Displays...<br />

Total number of MSDP peers<br />

IP Address<br />

State<br />

Keep Alive Time<br />

Hold Time<br />

Keep Alive Message Sent<br />

Keep Alive Message Received<br />

Notifications Sent<br />

Notifications Received<br />

Source-Active Sent<br />

Source-Active Received<br />

Last Connection Reset Reason<br />

Notification Message Error Code<br />

Received<br />

Notification Message Error SubCode<br />

Received<br />

The number of MSDP peers configured on the device<br />

The IP address of the peer’s interface with the device<br />

The state of the MSDP device connection with the peer. The state can be<br />

one of the following:<br />

• CONNECTING – The session is in the active open state.<br />

• ESTABLISHED – The MSDP session is fully up.<br />

• INACTIVE – The session is idle.<br />

• LISTENING – The session is in the passive open state.<br />

The keepalive time, which specifies how often this MSDP device sends<br />

keep alive messages to the neighbor. The keep alive time is 60 seconds<br />

and is not configurable.<br />

The hold time, which specifies how many seconds the MSDP device will<br />

wait for a KEEPALIVE or UPDATE message from an MSDP neighbor<br />

before deciding that the neighbor is dead. The hold time is 90 seconds<br />

and is not configurable.<br />

The number of keepalive messages the MSDP device has sent to the<br />

peer.<br />

The number of keepalive messages the MSDP device has received from<br />

the peer.<br />

The number of notification messages the MSDP device has sent to the<br />

peer.<br />

The number of notification messages the MSDP device has received<br />

from the peer.<br />

The number of source active messages the MSDP device has sent to the<br />

peer.<br />

The number of source active messages the MSDP device has received<br />

from the peer.<br />

The reason the previous session with this neighbor ended.<br />

The MSDP device has received a notification message from the neighbor<br />

that contains an error code corresponding to one of the following errors.<br />

Some errors have subcodes that clarify the reason for the error. Where<br />

applicable, the subcode messages are listed underneath the error code<br />

messages:<br />

• 1 – Message Header Error<br />

• 2 – SA-Request Error<br />

• 3 – SA-Message or SA-Response Error<br />

• 4 – Hold Timer Expired<br />

• 5 – Finite State Machine Error<br />

• 6 – Notification<br />

• 7 – Cease<br />

For information about these errors, refer to section 17 in the Internet<br />

draft describing MSDP, “draft-ietf-msdp-spec”.<br />

See above.<br />

FastIron Ethernet Switch IP Multicast Configuration Guide 119<br />

53-1002638-02

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

Saved successfully!

Ooh no, something went wrong!