HP 6125XLG R2306-HP 6125XLG Blade Switch Network Management and Monitoring Con - Page 106

Verifying the configurations, Troubleshooting sFlow configuration

Page 106 highlights

Verifying the configurations # Display the sFlow configuration and operation information. [Sysname-Ten-GigabitEthernet1/1/5] display sflow sFlow datagram version: 5 Global information: Agent IP: 3.3.3.1(CLI) Source address: Collector information: ID IP Port Aging Size VPN-instance Description 1 3.3.3.2 6343 N/A 1400 netserver Port information: Interface CID Interval(s) FID MaxHLen Rate Mode Status XGE1/1/5 1 120 1 128 4000 Random Active The output shows that Ten-GigabitEthernet 1/1/5 enabled with sFlow is active, the counter sampling interval is 120 seconds, and the flow sampling interval is 4000 (one packet is sampled from every 4000 packets). Troubleshooting sFlow configuration The remote sFlow collector cannot receive sFlow packets Symptom The remote sFlow collector cannot receive sFlow packets. Analysis • The sFlow collector is not specified. • sFlow is not configured on the interface. • The IP address of the sFlow collector specified on the sFlow agent is different from that of the remote sFlow collector. • No IP address is configured for the Layer 3 interface that sends sFlow packets, or the IP address is configured, but the UDP datagrams with the IP address being the source cannot reach the sFlow collector. • The physical link between the device and the sFlow collector fails. • The sFlow collector is bound to a non-existent VPN. Solution 1. Check that sFlow is correctly configured by using display sflow. 2. Check that a correct IP address is configured for the device to communicate with the sFlow collector. 3. Check that the physical link between the device and the sFlow collector is up. 4. Check that the bound VPN already exists. 100

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148

100
Verifying the configurations
# Display the sFlow configuration and operation information.
[Sysname-Ten-GigabitEthernet1/1/5] display sflow
sFlow datagram version: 5
Global information:
Agent IP: 3.3.3.1(CLI)
Source address:
Collector information:
ID
IP
Port
Aging
Size VPN-instance Description
1
3.3.3.2
6343
N/A
1400
netserver
Port information:
Interface
CID
Interval(s) FID
MaxHLen Rate
Mode
Status
XGE1/1/5
1
120
1
128
4000
Random
Active
The output shows that Ten-GigabitEthernet 1/1/5 enabled with sFlow is active, the counter
sampling interval is 120 seconds, and the flow sampling interval is 4000 (one packet is sampled
from every 4000 packets).
Troubleshooting sFlow configuration
The remote sFlow collector cannot receive sFlow packets
Symptom
The remote sFlow collector cannot receive sFlow packets.
Analysis
The sFlow collector is not specified.
sFlow is not configured on the interface.
The IP address of the sFlow collector specified on the sFlow agent is different from that of the remote
sFlow collector.
No IP address is configured for the Layer 3 interface that sends sFlow packets, or the IP address is
configured, but the UDP datagrams with the IP address being the source cannot reach the sFlow
collector.
The physical link between the device and the sFlow collector fails.
The sFlow collector is bound to a non-existent VPN.
Solution
1.
Check that sFlow is correctly configured by using
display sflow
.
2.
Check that a correct IP address is configured for the device to communicate with the sFlow
collector.
3.
Check that the physical link between the device and the sFlow collector is up.
4.
Check that the bound VPN already exists.