8.3. sFlow Command Reference

This section provides the sFlow configuration command descriptions.

8.3.1. Command Hierarchies

  1. sFlow Configuration Commands

To enable sFlow collection, an operator must enable sFlow on physical Ethernet ports in addition to the following configuration. Refer to the Ethernet Port Commands section in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Interface Configuration Guide Interface Configuration Guide for the CLI required to enable sFlow on physical ports.

8.3.1.1. sFlow Configuration Commands

config
— sflow
— egress-counter-map {policer policer-id | queue queue-id} traffic-type {unicast | multicast | broadcast} [create]
— no egress-counter-map {policer policer-id | queue queue-id}
— ingress-counter-map {policer policer-id | queue queue-id} traffic-type {unicast | multicast | broadcast} [create]
— no ingress-counter-map {policer policer-id | queue queue-id}
— receiver receiver-name [create]
— no receiver
— ip-addr-primary ip-address[:port]
— no ip-addr-primary
— ip-addr-backup ip-address[:port]
— no ip-addr-backup`
— max-data-size bytes

8.3.2. Command Descriptions

8.3.2.1. Configuration Commands

The following commands apply to the 7950 XRS, 7750 SR-12e, and 7750 SR-7/12 platforms.

sflow

Syntax 
sflow
Context 
config>sflow
Description 

This command enables context to configured sflow agent parameters.

egress-counter-map

Syntax 
egress-counter-map policer policer-id traffic-type {unicast | multicast | broadcast} [create]
egress-counter-map queue queue-id traffic-type {unicast | multicast | broadcast} [create]
no egress-counter-map policer policer-id
no egress-counter-map queue queue-id
Context 
config>sflow
Description 

This command configures the egress counter map for sFlow. The map must be configured so sFlow agent understands how to interpret data collected against SAP queues and policers. Multiple queues and policers can be mapped to the same traffic-type using separate line entries.

The no form of this command deletes a SAP policy queue/policer from the map.

Parameters 
policer-id—
Specifies the policer ID in a SAP egress QoS policy. If the SAP policy does not have a policer with the specified ID, the map entry will be ignored for this SAP.
Values—
1 to 8

 

queue-id—
Specifies the queue ID in a SAP egress QoS policy. If the SAP policy does not have a queue with the specified ID, the map entry will be ignored for this SAP.
Values—
1 to 8

 

ingress-counter-map

Syntax 
ingress-counter-map policer policer-id traffic-type {unicast | multicast | broadcast} [create]
ingress-counter-map queue queue-id traffic-type {unicast | multicast | broadcast} [create]
no ingress-counter-map policer policer-id
no ingress-counter-map queue queue-id
Context 
config>sflow
Description 

This command configures the ingress counter map for sFlow. The map must be configured so sFlow agent understands how to interpret data collected against SAP queues and policers. Multiple queues/policers can be mapped to the same traffic-type using separate line entries.

The no form of this command deletes a SAP policy queue/policer from the map.

Parameters 
policer-id—
Specifies the policer ID in a SAP ingress QoS policy. If the SAP policy does not have a policer with the specified ID, the map entry will be ignored for this SAP.
Values—
1 to 32

 

queue-id—
Specifies the queue ID in a SAP ingress QoS policy. If the SAP policy does not have a queue with the specified ID, the map entry will be ignored for this SAP.
Values—
1 to 32

 

receiver

Syntax 
receiver receiver-name [create]
no receiver
Context 
config>sflow
Description 

This command creates an sFlow receiver context or enters existing sFlow receiver context for the sFlow agent.

The no form of this command deletes an existing sFlow receiver context.

Parameters 
receiver-names—
String of up to 127 characters.

ip-addr-primary

Syntax 
ip-addr-primary ip-address[:port]
no ip-addr-primary
Context 
config>sflow>receiver
Description 

This command configures primary IPv4 or IPv6 destination address for the sFlow agent to send sFlow datagrams to. Optionally a destination port can also be configured (by default port 6343 is used).

The no form of this command deletes primary sFlow receiver destination.

Parameters 
ip-address—
Specifies the IPv4 or IPv6 address to send the sFlow datagrams.
Values—

a.b.c.d

(IPv4)

x:x:x:x:x:x:x:x

(IPv6)

[x:x:x:x:x:x:x:x]

(IPv6)

x - [0..FFFF]H

 

port—
Specifies the UDP destination port to send the sFlow datagrams.
Values—
1 to 65535

 

ip-addr-backup

Syntax 
ip-addr-backup ip-address[:port]
no ip-addr-backup
Context 
config>sflow>receiver
Description 

This command configures back-up IPv4 or IPv6 destination address for the sFlow agent to send sFlow datagrams to. Optionally a destination port can also be configured (by default port 6343 is used).

The no form of this command deletes backup sFlow receiver destination.

Parameters 
ip-address—
Specifies the IPv4 or IPv6 address to send the sFlow datagrams to.
Values—

a.b.c.d

(IPv4)

x:x:x:x:x:x:x:x

(IPv6)

[x:x:x:x:x:x:x:x]

(IPv6)

x - [0 to FFFF]H

 

port—
Specifies the UDP destination port to send the sFlow datagrams to.
Values—
1 to 65535

 

max-data-size

Syntax 
max-data-size bytes
Context 
config>sflow>receiver
Description 

This configures the maximum data size for sFlow UDP datagrams sent to the collector.

To restore default configuration, execute max-data-size 1400.

Default 

max-data-size 1400

Parameters 
bytes—
Specifies the data size.
Values—
200 to 1500