Policy Framework Configuration Guide - Juniper Networks

More documents

Recommendations

Info

Junos 10.4 Policy Framework Configuration Guide multiple firewall filters to the incoming traffic on an interface. You use an output list to apply multiple firewall filters to the outbound traffic on an interface. You can include up to 16 filters in an input or an output list. See Table 24 on page 186 for a detailed description of each supported application point, the types of firewall filters supported by each application point, and any limitations. Table 24: Firewall Filter Application Points Application Point Filter Type Supported Hierarchy Comments Physical interface—Filter affects packets for all logical interfaces configured on the physical interface. Hierarchical policer you define at the [edit firewall hierarchical-policer hierarchical-policer-name] hierarchy level. [edit interfaces interface-name layer2-policer inputhierarchical-policer] Supported only on Gigabit Ethernet intelligent queuing (IQ2) PICs on the M120, M320 and T Series routers and on Enhanced Queuing Dense Port Concentrators (EQ DPC) on MX Series routers. Logical interface—Filter affects all protocol families configured on the logical interface. Firewall filter you define for the protocol family any at the [edit firewall] hierarchy level. • [edit interfaces interface-name unit unit-number filter input filter-name] • [edit interfaces interface-name unit unit-number output filter-name] Supported only on M320 and T Series routers, on M7i and M10i routers with the enhanced CFEB (CFEB-e) and on 10-Gigabit Ethernet Modular Port Concentrator (MPC), 60-Gigabit Ethernet MPC, 60-Gigabit Ethernet Queuing MPC, and 60-Gigabit Ethernet Enhanced Queuing MPC on MX Series routers. Logical interface—Filter applied affects all protocol families configured on the logical interface. Layer 2 policer you define at: • [edit firewall policer policer-name] hierarchy level for input policers and output policers • [edit firewall three-color-policer policer-name hierarchy level for input three color policers and output three color policers • [edit interfaces interface-name unit unit-number layer2-policer input-policer policer-name] • [edit interfaces interface-name unit unit-number layer2-policer output-policer policer-name] • [edit interfaces interface-name unit unit-number input-three-color policer-name] • [edit interfaces interface-name unit unit-number output-three-color policer-name] MX Series routers do not support layer 2 policers applied to a logical interface. On MX Series routers, layer 2 policers an only be applied as hierarchical policers. Logical interface—Filter applied affects all protocol families configured on the logical interface. Hierarchical policer you define at the [edit firewall hierarchical-policer hierarchical-policer-name] hierarchy level. [edit interfaces interface-name unit unit-number layer2-policer inputhierarchical-policer policer-name] Supported only on Gigabit Ethernet intelligent queuing (IQ2) PICs on the M120, M320 and T Series routers. 186 Copyright © 2010, Juniper Networks, Inc.
Chapter 8: Introduction to Firewall Filters Table 24: Firewall Filter Application Points (continued) Application Point Filter Type Supported Hierarchy Comments Protocol family on interface—Filter is applied to a specific protocol family on the logical interface. Standard firewall filter you define for any of the following protocol families at the [edit firewall family family-name filter filter-name] hierarchy level: any, bridge, ccc, inet, inet6, mpls, and vpls • [edit interfaces interface-name unit unit-number family family-name filter input filter-name] • [edit interfaces interface-name unit unit-number family family-name filter output filter-name] The protocol family bridge is supported only on MX Series routers. • [edit interfaces interface-name unit unit-number family family-name filter input-list [ filter-names ] • [edit interfaces interface-name unit unit-number family family-name filter output-list [ filter-names ] Protocol family on interface—Filter is applied to a specific protocol family on the logical interface. Simple filter you define at the [edit firewall family inet simple-filter filter-name] hierarchy level. [edit interfaces interface-name unit unit-number family inet simple-filter input filter-name] Supported for protocol family inet only on Gigabit Ethernet intelligent queuing (IQ2) PICs on the M120, M320, and T Series routers and on Enhanced Queueing Dense Port Concentrators (EQ DPC) on MX Series routers. Protocol family on interface—Filter is applied to a specific protocol family on the logical interface. Policer applied to incoming or outbound traffic that you define at the [edit firewall policer policer-name] hierarchy level. • [edit interfaces interface-name unit unit-number family family-name input filter-name] • [edit interfaces interface-name unit unit-number family family-name output filter-name] The protocol family bridge is supported only on MX Series routers. The following protocol families are supported: bridge, ccc, inet, inet6, mpls, tcc, and vpls. Copyright © 2010, Juniper Networks, Inc. 187
Page 1 and 2:
Junos ® OS Policy Framework Config
Page 3 and 4:
END USER LICENSE AGREEMENT READ THI
Page 5 and 6:
12. Commercial Computer Software. T
Page 7 and 8:
Abbreviated Table of Contents Part
Page 9 and 10:
Table of Contents About This Guide
Page 11 and 12:
Table of Contents Testing Routing P
Page 13 and 14:
Table of Contents Using Routing Pol
Page 15 and 16:
Table of Contents Configuring Forwa
Page 17 and 18:
Table of Contents Configuring Flow
Page 19 and 20:
Table of Contents interface (Next-H
Page 21 and 22:
List of Figures Part 1 Policy Frame
Page 23 and 24:
List of Tables About This Guide . .
Page 25 and 26:
About This Guide This preface provi
Page 27 and 28:
About This Guide • MX Series •
Page 29 and 30:
About This Guide Table 1: Notice Ic
Page 31 and 32:
About This Guide or are covered und
Page 33 and 34:
PART 1 Policy Framework • Introdu
Page 35 and 36:
CHAPTER 1 Introduction to Policy Fr
Page 37 and 38:
Chapter 1: Introduction to Policy F
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
PART 2 Routing Policies • Introdu
Page 47 and 48:
CHAPTER 2 Introduction to Routing P
Page 49 and 50:
Chapter 2: Introduction to Routing
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
CHAPTER 3 Routing Policy Configurat
Page 69 and 70:
Chapter 3: Routing Policy Configura
Page 71 and 72:
CHAPTER 4 Routing Policy Configurat
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
CHAPTER 5 Extended Match Conditions
Page 129 and 130:
Chapter 5: Extended Match Condition
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168: CHAPTER 6 Extended Actions Configur
Page 169 and 170: Chapter 6: Extended Actions Configu
Page 197 and 198: CHAPTER 7 Summary of Routing Policy
Page 199 and 200: Chapter 7: Summary of Routing Polic
Page 213 and 214: PART 3 Firewall Filters • Introdu
Page 215 and 216: CHAPTER 8 Introduction to Firewall
Page 217: Chapter 8: Introduction to Firewall
Page 221 and 222: Chapter 8: Introduction to Firewall
Page 223 and 224: CHAPTER 9 Firewall Filter Configura
Page 225 and 226: Chapter 9: Firewall Filter Configur
Page 269 and 270:
Chapter 9: Firewall Filter Configur
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
CHAPTER 10 Introduction to Traffic
Page 311 and 312:
Chapter 10: Introduction to Traffic
Page 313 and 314:
Page 315 and 316:
CHAPTER 11 Policer Configuration Si
Page 317 and 318:
Chapter 11: Policer Configuration [
Page 319 and 320:
Chapter 11: Policer Configuration I
Page 321 and 322:
Chapter 11: Policer Configuration C
Page 323 and 324:
Chapter 11: Policer Configuration u
Page 325 and 326:
Chapter 11: Policer Configuration T
Page 327 and 328:
Chapter 11: Policer Configuration
Page 329 and 330:
Chapter 11: Policer Configuration }
Page 331 and 332:
Chapter 11: Policer Configuration N
Page 333 and 334:
Chapter 11: Policer Configuration }
Page 335 and 336:
Page 337 and 338:
Chapter 11: Policer Configuration A
Page 339 and 340:
Chapter 11: Policer Configuration p
Page 341 and 342:
Page 343 and 344:
Chapter 11: Policer Configuration p
Page 345 and 346:
Chapter 11: Policer Configuration c
Page 347 and 348:
CHAPTER 12 Summary of Firewall Filt
Page 349 and 350:
Chapter 12: Summary of Firewall Fil
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
PART 4 Traffic Sampling, Forwarding
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
CHAPTER 15 Traffic Forwarding and M
Page 393 and 394:
Chapter 15: Traffic Forwarding and
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
CHAPTER 16 Summary of Traffic Sampl
Page 417 and 418:
Chapter 16: Summary of Traffic Samp
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
Page 433 and 434:
Page 435 and 436:
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
Page 453 and 454:
Page 455 and 456:
Page 457 and 458:
Page 459 and 460:
Page 461 and 462:
Page 463 and 464:
Page 465 and 466:
Page 467 and 468:
Page 469 and 470:
Page 471 and 472:
Page 473 and 474:
Page 475 and 476:
Page 477 and 478:
Page 479 and 480:
Page 481 and 482:
Page 483 and 484:
Page 485 and 486:
Page 487 and 488:
Page 489 and 490:
Page 491 and 492:
PART 5 Indexes • Index on page 46
Page 493 and 494:
Index Symbols ! in policy expressio
Page 495 and 496:
Index Layer 2 bridging traffic (MX
Page 497 and 498:
Index input statement..............
Page 499 and 500:
Index P P2MP.......................
Page 501 and 502:
Index show policy damping command..
Page 503 and 504:
Index of Statements and Commands A
Page 505 and 506:
Index of Statements and Commands si
show all

Policy Framework Configuration Guide - Juniper Networks

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

Delete template?

Save as template?