IBM 867431X Hardware Maintenance Manual - Page 108

your computer, all IBM Netfinity 10/100 Ethernet Security Adapters, and IBM

Get IBM 867431X - Eserver xSeries 330 PDF manuals and user guides View all IBM 867431X manuals
Add to My Manuals
Save this manual to your list of manuals

Page 108 highlights

Note: IEEE 802.1p tagging increases the size of the packets it tags. Some hubs and switches will not recognize the larger packets and will drop them. Check your hub or switch documentation to see if they support 802.1p. (You can configure the switch to strip the tags from the packets and send it on to the next destination as normal traffic). If these devices do not support 802.1p or if you are not sure, use High Priority Queue (HPQ) to prioritize network traffic. The requirements for effectively using IEEE 802.1p tagging are: v The other devices receiving and routing 802.1p tagged packets must support 802.1p. v The adapters on these devices must support 802.1p. The Ethernet controller in your computer, all IBM Netfinity 10/100 Ethernet Security Adapters, and IBM 10/100 Ethernet Server Adapters support 802.1p. v The adapter cannot be assigned to an adapter team. v If you are setting up VLANs and packet tagging on the same adapter, 802.1p/802.1Q Tagging must be enabled on the PROSet Advanced tab. If your network infrastructure devices do not support IEEE 802.1p or you are not sure, you can still define filters and send packets as high priority. While High Priority Queue (HPQ) does not provide the precise priority levels of 802.1p tagging, it does assign traffic as either high or low priority and sends high priority packets first. Therefore, if there are multiple applications on a system sending packets, the packets from the application with a filter are sent out first. HPQ does not change network routing, nor does it add any information to the packets. To assign HPQ, you can specify it using Priority Packet when you create or assign a filter. To effectively use HPQ, the adapter cannot be assigned to an adapter team. Virtual LAN Mode: A virtual LAN (VLAN) is a logical grouping of network devices put together as a LAN, regardless of their physical grouping or collision domains. Using VLANs increases network performance and improves network security. VLANs offer you the ability to group users and devices together into logical workgroups. This can simplify network administration when connecting clients to computers that are geographically dispersed across the building, campus, or enterprise network. Normally, VLANs are configured at the switch and any computer can be a member of one VLAN per installed network adapter. Your Ethernet controller supersedes this by communicating directly with the switch, allowing multiple VLANs on a single network adapter (up to 64 VLANs). To set up VLAN membership, your Ethernet controller must be attached to a switch that has VLAN capability. You also need to use Windows 2000 or Windows NT 4.0 with Service Pack 5.0 or later. Notes: 1. Windows NT versions prior to 4.0 do not support VLANs. 2. VLANs require NT 4.0 with Service Pack 5.0 and the NDIS driver hotfix from Microsoft. 100 Hardware Maintenance Manual: xSeries 330 Type 8674, IntelliStation R Pro Type 6851, and Network Equipment Building System Type 8674

  • 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
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
Note:
IEEE 802.1p tagging increases the size of the packets it tags. Some hubs and
switches will not recognize the larger packets and will drop them. Check
your hub or switch documentation to see if they support 802.1p. (You can
configure the switch to strip the tags from the packets and send it on to the
next destination as normal traffic). If these devices do not support 802.1p or
if you are not sure, use High Priority Queue (HPQ) to prioritize network
traffic.
The requirements for effectively using IEEE 802.1p tagging are:
v
The other devices receiving and routing 802.1p tagged packets must support
802.1p.
v
The adapters on these devices must support 802.1p. The Ethernet controller in
your computer, all IBM Netfinity 10/100 Ethernet Security Adapters, and IBM
10/100 Ethernet Server Adapters support 802.1p.
v
The adapter cannot be assigned to an adapter team.
v
If you are setting up VLANs and packet tagging on the same adapter,
802.1p/802.1Q Tagging must be enabled on the PROSet Advanced tab.
If your network infrastructure devices do not support IEEE 802.1p or you are not
sure, you can still define filters and send packets as high priority. While High
Priority Queue (HPQ) does not provide the precise priority levels of 802.1p
tagging, it does assign traffic as either high or low priority and sends high priority
packets first. Therefore, if there are multiple applications on a system sending
packets, the packets from the application with a filter are sent out first. HPQ does
not change network routing, nor does it add any information to the packets.
To assign HPQ, you can specify it using Priority Packet when you create or assign
a filter.
To effectively use HPQ, the adapter cannot be assigned to an adapter team.
Virtual LAN Mode:
A virtual LAN (VLAN) is a logical grouping of network
devices put together as a LAN, regardless of their physical grouping or collision
domains. Using VLANs increases network performance and improves network
security.
VLANs offer you the ability to group users and devices together into logical
workgroups. This can simplify network administration when connecting clients to
computers that are geographically dispersed across the building, campus, or
enterprise network.
Normally, VLANs are configured at the switch and any computer can be a member
of one VLAN per installed network adapter. Your Ethernet controller supersedes
this by communicating directly with the switch, allowing multiple VLANs on a
single network adapter (up to 64 VLANs).
To set up VLAN membership, your Ethernet controller must be attached to a
switch that has VLAN capability. You also need to use Windows 2000 or Windows
NT 4.0 with Service Pack 5.0 or later.
Notes:
1.
Windows NT versions prior to 4.0 do not support VLANs.
2.
VLANs require NT 4.0 with Service Pack 5.0 and the NDIS driver hotfix from
Microsoft.
100
Hardware Maintenance Manual: xSeries 330 Type 8674, IntelliStation R Pro Type 6851, and Network Equipment Building
System Type 8674