Reference Guide

ManualsBrandsDell ManualsAccess PlatformsPowerSwitch S5000

521

522

523

524

525

526

527

528

529

530

Parameters

vrf vrf-name (OPTIONAL) Enter the keyword vrf and then the name of

the VRF to view the status of all BGP connections

corresponding to that VRF.

ipv4 multicast (OPTIONAL) Enter the keyword ipv4 followed by the

keyword

multicast to view information related only to ipv4

multicast routes.

ipv4 unicast (OPTIONAL) Enter the keyword ipv4 followed by the

keyword

unicast to view information related only to ipv4

unicast routes.

ipv6 unicast (OPTIONAL) Enter the keyword ipv6 followed by the

keyword unicast to view information related only to ipv6

unicast routes.

Command

Modes

• EXEC

• EXEC Privilege

Command

History

This guide is platform-specific. For command information about other platforms,

refer to the relevant

Dell Networking OS Command Line Reference Guide.

The following is a list of the Dell Networking OS version history for this command.

Version Description

9.7(0.0) Added the ipv4 multicast and ipv6 unicast parameters.

9.0.2.0 Introduced on the S6000.

8.3.19.0 Introduced on the S4820T.

8.3.11.1 Introduced on the Z9000.

8.3.7.0 Introduced on the S4810.

7.8.1.0 Introduced on the S-Series.

7.7.1.0 Introduced on the C-Series.

Usage

Information

In BGP, route attributes are maintained at different locations. When attributes that

correspond to multiple routes change, then attribute counts that the show ip

bgp summary command displays are calculated as summations of attributes

corresponding to all the associated routes. For example, if cluster_id is an attribute

associated with thousand routes that contain exactly the same set of attributes,

then the cluster_id count is 1. If these thousand routes are set with different

attribute values with the same cluster_id, then the cluster_id count is 1000, since

the same value is stored for thousand different attribute records.

The attribute next-hop is a part of the BGP attribute data structure.

If two peers send the same route that contains similar path attributes, then two

entries are maintained in the back-end, as both these entries have different next-

Border Gateway Protocol

527