D-Link DES-3624 Product Manual - Page 27

Packet Forwarding, Topology Change, Link Change Event, Port Partition, Broadcast Storm

Get D-Link DES-3624 - Switch - Stackable PDF manuals and user guides
UPC - 790069221736
View all D-Link DES-3624 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 27 highlights

Stackable NWay Ethernet Switch User's Guide Topology Change Timer the new root trap is sent out immediately after the Switch's selection as a new root. ♦ Topology Change A Topology Change trap is sent by the Switch when any of its configured ports transitions from the Learning state to the Forwarding state, or from the Forwarding state to the Blocking state. The trap is not sent if a new root trap is sent for the same transition. ♦ Link Change Event This trap is sent whenever the link of a port changes from link up to link down or from link down to link up. ♦ Port Partition This trap is sent whenever a port is partitioned as a result of more than sixty-one collisions on the port (i.e., it is automatically partitioned). The number of collisions that triggers this trap is the same at either 10Mbps or 100Mbps. ♦ Broadcast Storm This trap is sent whenever the port reaches the broadcast storm rising or falling threshold. MIBs Management information and counters are stored in the Switch in the Management Information Base (MIB). The Switch uses the standard MIB-II Management Information Base module. Consequently, values for MIB objects can be retrieved from any SNMP-based network manager software. In addition to the standard MIBII, the Switch also supports its own proprietary enterprise MIB as an extended Management Information Base. These MIBs may also be retrieved by specifying the MIB's Object-Identity (OID) at the network manager. MIB values can be either read-only or read-write. Read-only MIBs variables can be either constants that are programmed into the Switch, or variables that change while the Switch is in operation. Examples of read-only constants are the number of ports and types of ports. Examples of read-only variables are the statistics counters such as the number of errors that have occurred, or how many kilobytes of data have been received and forwarded through a port. Read-write MIBs are variables usually related to user-customized configurations. Examples of these are the Switch's IP Address, Spanning Tree Algorithm parameters, and port status. If you use a third-party vendors' SNMP software to manage the Switch, a diskette listing the Switch's propriety enterprise MIBs can be obtained by request. If your software provides functions to browse or modify MIBs, you can also get the MIB values and change them (if the MIBs' attributes permit the write operation). This process however can be quite involved, since you must know the MIB OIDs and retrieve them one by one. Packet Forwarding The Switch learns the network configuration and uses this information to forward packets. This reduces the traffic congestion on the network, because packets, instead of being transmitted to all segments, are transmitted to the destination only. Example: if Port 1 receives a packet destined for a station on Port 2, the Switch transmits that packet through Port 2 only, and transmits nothing through the other ports. Switch Management Concepts 31

  • 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
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
Stackable NWay Ethernet Switch User’s Guide
Switch Management Concepts
31
Topology Change Timer the new root trap is sent out immediately after the Switch’s selection as a new
root.
♦
Topology Change
A Topology Change trap is sent by the Switch when any of its configured ports
transitions from the Learning state to the Forwarding state, or from the Forwarding state to the
Blocking state. The trap is not sent if a new root trap is sent for the same transition.
♦
Link Change Event
This trap is sent whenever the link of a port changes from link up to link down
or from link down to link up.
♦
Port Partition
This trap is sent whenever a port is partitioned
as a result of more than sixty-one
collisions
on the port (i.e., it is automatically partitioned). The number of collisions that triggers this
trap is the same at either 10Mbps or 100Mbps.
♦
Broadcast Storm
This trap is sent whenever the port reaches the broadcast storm rising or falling
threshold.
MIBs
Management information and counters are stored in the Switch in the Management Information Base (MIB).
The Switch uses the standard MIB-II Management Information Base module. Consequently, values for MIB
objects can be retrieved from any SNMP-based network manager software. In addition to the standard MIB-
II, the Switch also supports its own proprietary enterprise MIB as an extended Management Information
Base. These MIBs may also be retrieved by specifying the MIB’s Object-Identity (OID) at the network
manager. MIB values can be either read-only or read-write.
Read-only MIBs variables can be either constants that are programmed into the Switch, or variables that
change while the Switch is in operation.
Examples of read-only constants are the number of ports and types
of ports.
Examples of read-only variables are the statistics counters such as the number of errors that have
occurred, or how many kilobytes of data have been received and forwarded through a port.
Read-write MIBs are variables usually related to user-customized configurations. Examples of these are the
Switch’s IP Address, Spanning Tree Algorithm parameters, and port status.
If you use a third-party vendors’ SNMP software to manage the Switch, a diskette listing the Switch’s
propriety enterprise MIBs can be obtained by request. If your software provides functions to browse or modify
MIBs, you can also get the MIB values and change them (if the MIBs’ attributes permit the write operation).
This process however can be quite involved, since you must know the MIB OIDs and retrieve them one by
one.
Packet Forwarding
The Switch learns the network configuration and uses this information to forward packets. This reduces the
traffic congestion on the network, because packets, instead of being transmitted to all segments, are
transmitted to the destination only.
Example:
if Port 1 receives a packet destined for a station on Port 2, the
Switch transmits that packet through Port 2 only, and transmits nothing through the other ports.