2.5.2 - Force10 Networks

More documents

Recommendations

Info

Copyright 2008 Force10 Networks All rights reserved. Printed in the USA. March 2008. Force10 Networks® reserves the right to change, modify, revise this publication without notice. Trademarks Force10 Networks® and E-Series® are registered trademarks of Force10 Networks, Inc. Force10, the Force10 logo, E1200, E600, E600i, E300, EtherScale, TeraScale, FTOS, and SFTOS are trademarks of Force10 Networks, Inc. All other brand and product names are registered trademarks or trademarks of their respective holders. Statement of Conditions In the interest of improving internal design, operational function, and/or reliability, Force10 Networks reserves the right to make changes to products described in this document without notice. Force10 Networks does not assume any liability that may occur due to the use or application of the product(s) described herein. USA Federal Communications Commission (FCC) Statement This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC rules. These limits are designated to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy. If it is not installed and used in accordance to the instructions, it may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to take whatever measures necessary to correct the interference at their own expense. Properly shielded and grounded cables and connectors must be used in order to meet FCC emission limits. Force10 Networks is not responsible for any radio or television interference caused by using other than recommended cables and connectors or by unauthorized changes or modifications in the equipment. Unauthorized changes or modification could void the user’s authority to operate the equipment. This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Canadian Department of Communication Statement The digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus set out in the Radio Interference Regulations of the Canadian Department of Communications. Attention: Le present appareil numerique n’ emet pas de perturbations radioelectriques depassant les normes applicables aux appareils numeriques de la Class A prescrites dans le Reglement sur les interferences radioelectriques etabli par le ministere des Communications du Canada. European Union EMC Directive Conformance Statement This product is in conformity with the protection requirements of EU Council Directive 89/336/EEC on the approximation of the laws of the Member States relating to electromagnetic compatibility. Force 10 Networks can not accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended modification of this product, including the fitting of non-Force10 option cards. This product has been tested and found to comply with the limits for Class A Information Technology Equipment according to CISPR 22/ European Standard EN 55022. The limits for Class A equipment were derived for commercial and industrial environments to provide reasonable protection against interference with licensed communication equipment. Warning: This device is a Class A product. In a domestic environment, this device can cause radio interference, in which case, the user may be required to take appropriate measures. VCCI Compliance for Class A Equipment (Japan) This is Class A product based on the standard of the Voluntary Control Council For Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance may arise. When such trouble occurs, the user may be required to take corrective actions.\ Danger: AC Power cords are for use with Force10 Networks equipment only, do not use Force10 Networks AC Power cords with any unauthorized hardware.
SFTOS 2.5.2 adds: • A substantial support interface that is not accessible through the standard CLI modes and is not publicly documented • Support for new S-Series platforms, including the S50N, S50N-DC, and S25P-DC Other Changes to the Document Changes to this book from this edition include: New Features • The major change in this edition is that the SFTOS Web User Interface (Web UI) chapter is removed, because changes to SFTOS 2.5.2.1 were not promulgated to the Web UI, which made some parts of the Web UI unreliable or non-functional. • The ACL chapter now states that both MAC and IP ACLs can be applied to the same interface. Changes to this book from the previous SFTOS 2.5.1 edition include: • ACL chapter: More details on the loopback ACL • STP chapter: Added details on Bridge Max Age parameter to STP CLIs • LAG chapter: Revised LAG Load Distribution section • Troubleshooting chapter: Added example to "Recovering from Switch Stack Problems" SFTOS Configuration Guide, Version 2.5.2.0 3
Page 1: SFTOS Configuration Guide Version 2
Page 5 and 6: Contents New Features . . . . . . .
Page 7 and 8: Chapter 3 Management . . . . . . .
Page 9 and 10: Chapter 9 Spanning Tree . . . . . .
Page 11 and 12: Configuring a Native VLAN . . . . .
Page 13 and 14: List of Figures Figure 1 Using the
Page 15 and 16: Figure 77 Using the show interface
Page 17 and 18: Figure 158 Using the access-list Co
Page 19: Figure 243 Configuring VLANs for OS
Page 22 and 23: Audience This document is intended
Page 24 and 25: Technical Support The iSupport Webs
Page 26 and 27: 26 About this Guide
Page 28 and 29: — Flow Control at the MAC layer:
Page 30 and 31: • HTML-based Management • HTTPS
Page 32 and 33: (Force10 S50) #show port 1/0/2 Figu
Page 34 and 35: 34 SFTOS Features
Page 36 and 37: Setting up a Management Connection
Page 38 and 39: Step Task (continued) 5 Enter Line
Page 40 and 41: Getting Help From the CLI The follo
Page 42 and 43: Showing Network Settings Execute th
Page 44 and 45: Displaying Statistics Privileged Ex
Page 46 and 47: Force10 (Config)#users snmpv3 acces
Page 48 and 49: Enabling Telnet to the Switch Acces
Page 50 and 51: • Enabling Spanning Tree Protocol
Page 52 and 53:
The S-Series switch contains severa
Page 54 and 55:
Downloading a Software Image After
Page 56 and 57:
5. After the transfer is complete,
Page 58 and 59:
An alternative is to use the copy c
Page 60 and 61:
Note that the association of a part
Page 62 and 63:
After installing SFTOS 2.5.1 on the
Page 64 and 65:
When converting from a Routing imag
Page 66 and 67:
Saving the Startup Configuration to
Page 68 and 69:
Chapter 5, Stacking S-Series Switch
Page 70 and 71:
Uploading a Configuration Script to
Page 72 and 73:
Troubleshooting a Downloaded Script
Page 74 and 75:
Listing Configuration Scripts The s
Page 76 and 77:
Changing the Management VLAN from t
Page 78 and 79:
Setting the Host Name Prompt If you
Page 80 and 81:
Setting up SNMP Management Simple N
Page 82 and 83:
Commands to [disable] enable traps
Page 84 and 85:
RMON is an extension of SNMP, and r
Page 86 and 87:
Figure 47 RMON Event Thresholds Fig
Page 88 and 89:
The software clock runs only when t
Page 90 and 91:
Example #5: show sntp server Force1
Page 92 and 93:
• logging history. See Configurin
Page 94 and 95:
Interpreting system log messages Ta
Page 96 and 97:
Displaying the SNMP Trap Log The sh
Page 98 and 99:
Force10 #config Force10 (Config)#lo
Page 100 and 101:
100 System Logs
Page 102 and 103:
• The S50N, S50V, and S25P models
Page 104 and 105:
Management Unit Selection Algorithm
Page 106 and 107:
All of the forwarding protocols run
Page 108 and 109:
Use the member unit switchindex com
Page 110 and 111:
Setting Management Unit Preferences
Page 112 and 113:
Hardware Management Preference The
Page 114 and 115:
Notice, in Figure 67, that show swi
Page 116 and 117:
Using show Commands for Stacking In
Page 118 and 119:
The show stack command shows pretty
Page 120 and 121:
Table 3 Interfaces in the S-Series
Page 122 and 123:
Force10 #show interface 1/0/1 Ports
Page 124 and 125:
Use the show interface ethernet uni
Page 126 and 127:
Physical interfaces can become part
Page 128 and 129:
Enabling an Interface Ports are shu
Page 130 and 131:
The following table describes the e
Page 132 and 133:
If you connect powered devices to a
Page 134 and 135:
Bulk Configuration Bulk configurati
Page 136 and 137:
136 Configuring Interfaces
Page 138 and 139:
Table 6 describes the messages that
Page 140 and 141:
Verifying the DHCP Server Configura
Page 142 and 143:
Configuration Example — DHCP Serv
Page 144 and 145:
Step Command Syntax 2 authenticatio
Page 146 and 147:
Command Syntax Command Mode Purpose
Page 148 and 149:
Force10 #config Force10 (Config)# F
Page 150 and 151:
The scripts provided use OpenSSH (h
Page 152 and 153:
3. Use the show logging command to
Page 154 and 155:
Spanning Tree Protocol (STP, IEEE 8
Page 156 and 157:
Port States RSTP merges states from
Page 158 and 159:
MSTP CLI Management SFTOS supports
Page 160 and 161:
Enabling STP Use the following comm
Page 162 and 163:
The following commands influence wh
Page 164 and 165:
MSTP Configuration Example The foll
Page 166 and 167:
Use the show spanning-tree interfac
Page 168 and 169:
Figure 119 displays the output from
Page 170 and 171:
Figure 123 shows the output of the
Page 172 and 173:
172 Spanning Tree
Page 174 and 175:
• Static configuration is used wh
Page 176 and 177:
Link Aggregation Group (LAG) Comman
Page 178 and 179:
Interface Config mode commands Note
Page 180 and 181:
Basic LAG configuration example Thi
Page 182 and 183:
Using the Interface Range mode If y
Page 184 and 185:
Verify the status of the LAG as dyn
Page 186 and 187:
• Edge device: An edge device han
Page 188 and 189:
Deploying DiffServ The four basic s
Page 190 and 191:
Creating a Policy-Map The second st
Page 192 and 193:
Example (per interface): Force10 #c
Page 194 and 195:
Force10 #show class-map Class Class
Page 196 and 197:
Conform Secondary CoS—The action
Page 198 and 199:
The following is sample output from
Page 200 and 201:
VLAN 10: Finance Layer 3 Switch Por
Page 202 and 203:
Configuring Differentiated Services
Page 204 and 205:
204 Quality of Service
Page 206 and 207:
Note that the order of the rules is
Page 208 and 209:
— show mac access-lists Force10 #
Page 210 and 211:
Protecting the Management Interface
Page 212 and 213:
• An ACL applied to loopback inte
Page 214 and 215:
Use the show storm-control command
Page 216 and 217:
A VLAN is a set of end stations and
Page 218 and 219:
Executing the interface vlan 2-4094
Page 220 and 221:
Example of creating a VLAN and assi
Page 222 and 223:
3. Create VLAN 4 on switch R3 and a
Page 224 and 225:
Example of adding a LAG to a VLAN F
Page 226 and 227:
Example of creating a routed VLAN o
Page 228 and 229:
GARP Timers The following are GARP
Page 230 and 231:
1. Name switch R1, enable GVRP glob
Page 232 and 233:
Configuring a Private Edge VLAN (PV
Page 234 and 235:
Two commands can configure a native
Page 236 and 237:
Figure 186 Validating a Tagged Inte
Page 238 and 239:
. Force10 #show interface ethernet
Page 240 and 241:
DVLAN configuration example The exa
Page 242 and 243:
Configure switch R7: !---------Trun
Page 244 and 245:
Using the show vlan id vlan-id comm
Page 246 and 247:
set igmp maxresponse 1-3599 (typica
Page 248 and 249:
Use the show ip igmp interface unit
Page 250 and 251:
Port Mirroring Commands The followi
Page 252 and 253:
Stopping the mirroring session and
Page 254 and 255:
254 Port Mirroring
Page 256 and 257:
Enabling Routing The S-Series alway
Page 258 and 259:
Port Routing Configuration Example
Page 260 and 261:
IGMP Proxy Configuration The follow
Page 262 and 263:
Verifying the configuration Verify
Page 264 and 265:
RIP Configuration Example The confi
Page 266 and 267:
Border Router Port 0/2 192.150.2.1
Page 268 and 269:
Configuring OSPF on an S-Series ope
Page 270 and 271:
VLAN Routing This section introduce
Page 272 and 273:
3. As above, enable routing on R2:
Page 274 and 275:
5. Execute the show ip ospf command
Page 276 and 277:
1. As done previously, create the V
Page 278 and 279:
3. Use the show vlan id, show ip in
Page 280 and 281:
Port 0/2 192.150.2.1/24 Virtual Rou
Page 282 and 283:
3. Configure the IP address and sub
Page 284 and 285:
Note: In SFTOS 2.3.1.9, these messa
Page 286 and 287:
In addition to issuing the show swi
Page 288 and 289:
Monitoring SFPs The four fiber port
Page 290 and 291:
packets can be routed by the hardwa
Page 292 and 293:
• What was the LED status? (If th
Page 294 and 295:
294 • GVRP — Dynamic VLAN Regis
Page 296 and 297:
296 QoS • RFC 2474 — Definition
Page 298 and 299:
MIBs 298 • RFC 2096: IP forwardin
Page 300 and 301:
300 Force 10 MIBs You can see this
Page 302 and 303:
302
Page 304 and 305:
configuration, restore to factory d
Page 306 and 307:
inlinepower threshold command 132 i
Page 308 and 309:
MIBs, supported industry 298 mirror
Page 310 and 311:
RFC 3768 279 RFC 768 28, 294 RFC 78
Page 312 and 313:
show stack-port command 103 show st
Page 314:
VoIP support 202 VRID 281 VRRP 279
show all

2.5.2 - Force10 Networks

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?