Avaya G430 Manual
  1. Manuals
  2. Brands
  3. Avaya Manuals
  4. Gateway
  5. G430
  6. Manual

Avaya G430 Manual

Administering branch gateway
Hide thumbs Also See for G430:
1
2
3
4
5
6
Table Of Contents
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
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
Table of Contents

Advertisement

Quick Links

See also: Configuration Manual
Administering Avaya G430 Branch
Gateway
Release 6.3
03-603228
Issue 5
October 2013

Advertisement

Table of Contents
loading

Related Manuals for Avaya G430

Summary of Contents for Avaya G430

  • Page 1 Administering Avaya G430 Branch Gateway Release 6.3 03-603228 Issue 5 October 2013...
  • Page 2 Avaya does not guarantee that these links will work all the printing, Avaya assumes no liability for any errors. Avaya reserves the time and has no control over the availability of the linked pages.
  • Page 3 Product provided by Avaya including the selection, arrangement and • Installation documents design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the • System administration documents sui generis rights relating to the protection of databases.
  • Page 4 • IEC 61000-3-2 and IEC 61000-3-3. 2. This equipment returns answer supervision signals on Avaya Inc. is not responsible for any radio or television interference all (DID) calls forwarded back to the PSTN. caused by unauthorized modifications of this equipment or the...
  • Page 5 RJ2GX, FCC Part 68 Supplier’s Declarations of Conformity premises RJ21X, Avaya Inc. in the United States of America hereby certifies that the station RJ11C equipment described in this document and bearing a TIA TSB-168 label identification number complies with the FCC’s Rules and Regulations DID trunk 02RV2.T...
  • Page 6 See the Avaya Support website: http://support.avaya.com for product notices and articles, or to report a problem with your Avaya product. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: http://support.avaya.com, scroll to the bottom of the page, and select Contact Avaya Support.

  • Page 7: Table Of Contents

    SCP protocol support........................47 RADIUS authentication........................48 Special security features........................... 50 The recovery password........................50 Commands used to configure Telnet access................... 50 Gateway secret management......................51 DoS attacks............................52 Managed Security Services......................55 Administering Avaya G430 Branch Gateway October 2013...
  • Page 8 Chapter 6: Standard Local Survivability (SLS)..............Standard Local Survivability (SLS)......................101 Media module compatibility with SLS....................102 SLS features............................. 102 Avaya telephones supported in SLS....................103 Call processing functionality in SLS mode..................104 Call processing functionality not supported by SLS................. 105 Provisioning data..........................106 PIM configuration data........................
  • Page 9 CNA test plugs..........................404 Echo cancellation..........................410 Integrated analog testing – Test and Heal..................412 Service Level Agreement Monitor Agent..................419 Chapter 18: The router......................The router..............................421 Enabling and disabling the router..................... 422 Administering Avaya G430 Branch Gateway October 2013...
  • Page 10 Editing and deleting PBR lists......................596 PBR list commands in context......................597 Policy-based routing application example..................598 Summary of policy-based routing commands.................. 601 Chapter 22: Synchronization..................... Synchronization............................605 Defining a stratum clock source....................... 605 Administering Avaya G430 Branch Gateway October 2013...
  • Page 11 Disassociating a clock source......................607 Enabling and disabling automatic failover and failback..............607 Synchronization status........................607 Appendix A: Traps and MIBs..................... Traps and MIBs............................611 Branch Gateway traps........................611 Branch Gateway MIB files........................ 620 Index............................. Administering Avaya G430 Branch Gateway October 2013...
  • Page 12 Administering Avaya G430 Branch Gateway October 2013...

  • Page 13: Chapter 1: Introduction

    Purpose This document describes the procedure to administer the Branch Gateway. Intended audience The information in this book is intended for use by Avaya technicians, provisioning specialists, business partners, and customers. Document changes since last issue The following changes have been made to this document since the last issue: •...
  • Page 14 Administration Administration for the Avaya Describes how to configure and 03-603228 Branch Gateway G430 manage the G430 after it is already installed. This guide contains detailed information about all the features of the G450 and how to implement them. Avaya Branch Gateway G430...

  • Page 15: Training

    Avaya Mentor videos are available to provide technical content on how to install, configure, and troubleshoot Avaya products. Videos are available on the Avaya support site, listed under the video document type, and on the Avaya-run channel on YouTube. To find videos on the Avaya support site, select the product name, and check the videos checkbox to see a list of available videos.

  • Page 16: Warranty

    Introduction Warranty Avaya provides a 90-day limited warranty on Branch Gateway. To understand the terms of the limited warranty, see the sales agreement or other applicable documentation. In addition, the standard warranty of Avaya and the details regarding support for Branch Gateway in the warranty period is available on the Avaya Support website at https://support.avaya.com...

  • Page 17: Chapter 2: Supported Lan Deployments

    One of the Ethernet LAN ports is configured to be the active primary link, and the other Ethernet LAN port is configured to be on standby (disabled). For information about configuring the Ethernet LAN ports in a port redundancy pair, seePort redundancy on page 333. Administering Avaya G430 Branch Gateway October 2013...

  • Page 18: Port And Switch Redundancy Configuration

    Branch Gateway can be deployed in the LAN using RSTP to provide redundancy. Branch Gateway is connected to an external LAN switch using both the Ethernet LAN ports located on the Branch Gateway’s front panel. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 19: Rstp And Switch Redundancy Configuration

    The advantage of fast RSTP over port redundancy is that it controls the link state based on the best LAN topology using the links’ cost. However, an RSTP convergence time penalty is incurred. Administering Avaya G430 Branch Gateway October 2013...
  • Page 20 Supported LAN deployments Figure 5: RSTP and switch redundancy LAN deployment Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 21: Chapter 3: Configuration Overview

    IP address 192.11.13.6. However, the console device you connect to the Services port requires a specific configuration of its network settings, as explained in Accessing the gateway through the Services port on page 30. Administering Avaya G430 Branch Gateway October 2013...

  • Page 22: Defining The Usb-Modem Interface

    The MGC is a call controller server that controls telephone services on the Branch Gateway. The MGC can be internal or external and either IPv4 or IPv6. For more information, see Defining an interface on page 63 Related topics: Defining other interfaces on page 23 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 23: Configuration Using Cli

    For more information about the Branch Gateway CLI and a complete description of each CLI command, see the Avaya Branch Gateway G430 CLI Reference. Configuration using GUI applications Several Avaya GUI applications enable you to perform some configuration tasks on the Branch Gateway. Use these applications whenever possible, particularly for initial installation and provisioning.

  • Page 24: Configuration Changes And Backups

    101. The Avaya Gxxx Manager You can also use the Avaya Gxxx Manager to configure most features of the Branch Gateway. The Avaya Gxxx Manager is a GUI application. You can access the Avaya Gxxx Manager from Avaya Integrated Management software or from a web browser. Most of the commands that are available through the Branch Gateway CLI are also available through the Avaya Gxxx Manager.

  • Page 25: Firmware Version Control

    This is particularly important when uploading new versions. Related topic Software and firmware upgrades on page 83 Related topics: Using an older firmware version on page 26 Administering Avaya G430 Branch Gateway October 2013...
  • Page 26 About this task Use this procedure if it becomes necessary to use an older firmware version. Procedure 1. Enter set boot bank bank-x 2. Reset the Branch Gateway to use the older version. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 27: Chapter 4: Accessing The Branch Gateway

    Accessing the Gateway ® You can access the Branch Gateway using the CLI, the PIM, and the Avaya Aura Communication Manager. You can manage login permissions by using and configuring usernames and passwords, and by configuring the Branch Gateway to use RADIUS authentication.
  • Page 28 • An SSH connection through a SAL Gateway to the S8300, then a Telnet connection to the gateway using IP address 127.1.1.11. If the Branch Gateway is under service contract with Avaya Services, remote service providers can connect remotely to service the Branch Gateway with Telnet and SSH sessions. For higher security, you can configure the Branch Gateway to authenticate remote service logins using Access Security Gateway (ASG) authentication instead of password authentication.
  • Page 29 Example Example: In the following example, the user enters the vlan 1 interface context and displays help for the bandwidth command. Gxxx-001(super)# interface vlan 1 Gxxx-001(super-if:VLAN 1)# bandwidth ? Administering Avaya G430 Branch Gateway October 2013...
  • Page 30 4. Configure the Internet browser settings of the PC device to disable the proxy server. 5. SSH to 192.11.13.6. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 31 Telnet is disabled on the Branch Gateway by default. To enable Telnet, use the ip telnet command. 5. Open an SSH/Telnet session to the IP address of the USB port on the Branch Gateway. Administering Avaya G430 Branch Gateway October 2013...

  • Page 32: Pim Access

    Management Console is the central infrastructure application that discovers and monitors enabled network devices and runs Avaya Integrated Management applications. PIM must be installed on the same Windows server as Avaya Network Management Console with System View and Avaya Secure Access Administration.

  • Page 33: Avaya Aura ® Communication Manager Access

    Communication Manager software on a server. There ® might be several servers on your network that can control the Gateway. Access Avaya Aura Communication Manager on any server that is a Media Gateway Controller (MGC) for the Gateway. For more information, see Media Gateway Controller configuration on page 67.

  • Page 34: Login Permissions

    When you use Avaya Gxxx Manager or the CLI, your username determines your privilege level. The commands that are available to you during the session depend on your privilege level.
  • Page 35 Security overview Privilege level When you open the Avaya Gxxx Manager or access CLI, you must enter a username. The username that you enter sets your privilege level. The commands that are available to you during the session depend on your privilege level. If you use RADIUS authentication, the RADIUS server sets your privilege level.
  • Page 36 For more information about these commands, see User accounts CLI commands page 38 or Avaya CLI Reference. Commands used to manage password lockout and disabling When you lockout a user account, it remains locked out only for a specific time period. Disabling an account is a strong measure since it requires administrator intervention to re-enable the account.
  • Page 37 For more information about these commands, see User accounts CLI commands page 38 . For information about parameters and default settings, see Avaya G430 CLI Reference. Password expiry management You can force all passwords to expire within a certain period of time after they were created.
  • Page 38 Accessing the Branch Gateway For a full description of the commands and their output fields, see Avaya G430 CLI Reference. User accounts CLI commands All of the following commands manage user accounts. For more information about these commands, see Avaya G430 CLI Reference.

  • Page 39: Service Logins With Asg Authentication

    • Direct connection to the front panel Services port using the “craft” login When ASG authentication is enabled on the Gateway, the Gateway recognizes any login attempts using Avaya Services reserved usernames as service logins, and requests ASG authentication from the user, instead of a static user password.
  • Page 40 ASG authentication can be enabled and disabled on the Branch Gateway and requires an ASG authentication file. The ASG authentication file contains Avaya Services accounts for authenticating users at login as members of Avaya Services. The Branch Gateway is shipped with an ASG authentication file. For information about replacing the authentication file, refer Replacing the ASG authentication file on page 40.
  • Page 41 Examples of configuring ASG authentication You can perform the following ASG configurations: • Block Avaya Services login access, using no login authentication services- logins. This deactivates all Avaya Services logins, including local craft password-based Administering Avaya G430 Branch Gateway...
  • Page 42 (180 and 3). For example, to lockout Avaya Services access to the device for 360 seconds following five failed login attempts: Gxxx-001(super)# login authentication lockout 360 attempt 5 This lockout affects all users locally stored in the gateway, including locally defined user accounts and Avaya Services logins defined in the ASG authentication file.
  • Page 43 ASG authentication CLI commands All of the following commands manage ASG authentication. For more information about these commands, see Avaya G430 Branch Gateway CLI Reference. Command Description copy auth-file ftp Upload the authentication file from the gateway to an...
  • Page 44 Set a policy for locking out access to the gateway after successive failed login attempts lockout login authentication Activate all Avaya Services logins, including local login to the Services port with “craft” login. services-logins no login authentication Deactivate all Avaya Services logins.

  • Page 45: Ssh Protocol Support

    Gateway decrypts the data using the private key. 4. Both sides negotiate and must agree on the same chipper type. The Branch Gateway only supports 3DES-CBC encryption. The user on the client side accepts Administering Avaya G430 Branch Gateway October 2013...
  • Page 46 3. Enter ip ssh to enable SSH authentication. SSH is enabled by default. Disabling SSH on the Gateway Procedure 1. Use the disconnect ssh command to disconnect an existing SSH session. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 47: Scp Protocol Support

    3. Use the show ip ssh command to display SSH configuration information and information about any active SSH sessions. Summary of SSH configuration commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description...

  • Page 48: Radius Authentication

    Branch Gateway searches for your user name and password in its own database first. If it does not find them, it activates RADIUS authentication. For additional information on RADIUS configuration and authentication, go to the Avaya website at http://www.avaya.com/support, and search for the document Avaya RADIUS Configuration Overview.
  • Page 49 Security overview 2. Configure RADIUS authentication on the Branch Gateway. RADIUS authentication configuration commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description clear radius Clear the primary or secondary RADIUS server IP address...

  • Page 50: Special Security Features

    You can enable and disable the Branch Gateway’s ability to establish incoming and outgoing Telnet connections using the following commands. These commands are secured commands and are not displayed together with the running configuration (using the show running- Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 51: Gateway Secret Management

    • ip telnet-services Related topics: Telnet access configuration commands on page 51 Telnet access configuration commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description ip telnet Enable the Branch Gateway to establish an incoming Telnet...

  • Page 52: Dos Attacks

    SYN attack on page 53 SYN cookies on page 53 Configuring SYN cookies on page 54 Commands used to maintain SYN cookies on page 54 SYN cookies configuration commands on page 55 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 53 The hash result is generated from the source IP, source port, destination IP, destination port, and some secret values. The cookie can be verified when receiving a valid third ACK that establishes the connection. Administering Avaya G430 Branch Gateway October 2013...
  • Page 54 20 in last 10 seconds. Commands used to maintain SYN cookies Use the following commands to show and clear SYN cookies statistics: • show tcp syn-cookies • clear tcp syn-cookies Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 55: Managed Security Services

    For more information about these commands, see SYN cookies configuration commands page 55 . For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. SYN cookies configuration commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference.
  • Page 56 MSS notifications are intercepted and, if certain conditions are met, may be forwarded to the Avaya Security Operations Center (SOC) as INADS alarms. The SOC is an Avaya service group that handles DoS alerts, responding as necessary to any DoS attack or related security issue.
  • Page 57 To display the current MSS reporting rate, use the show mss- notification rate command. 4. Ensure that INADS reporting is configured on the active MGC. ® For information about configuring INADS reporting in Avaya Aura Communication ® Manager, see Avaya Aura Communication Manager documentation.
  • Page 58 ACL rule and tagging the ACL with a DoS classification label. Note: For general information about configuring policy rules, refer to Policy lists on page 557. Related topics: Examples for defining a DoS class using ACLs on page 59 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 59 • An example for entering the configuration mode of the interface on which you want to activate the ACL: Gxxx-001(super)# interface vlan 203 • An example for activating the configured ACL for incoming packets on the desired interface: Gxxx-001(super-if:vlan 203)# ip access-group 301 in Done! Administering Avaya G430 Branch Gateway October 2013...
  • Page 60 //activate Access Control list 301 for incoming packets on interface vlan 203: Gxxx-001(super-if:VLAN 203)# ip access-group 301 in Done! MSS configuration CLI commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description composite-operation Edit the specified composite operation.
  • Page 61 Define a new SNMPv3 group, or configure settings for the group snmp-server host Identify an SNMP management server, and specify the kind of messages it receives snmp-server user Configure settings for an SNMPv3 user Administering Avaya G430 Branch Gateway October 2013...
  • Page 62 Accessing the Branch Gateway Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 63: Chapter 5: Basic Device Configuration

    Defining an interface About this task All interfaces on the Gateway must be defined by the administrator, after installation of the Branch Gateway. Procedure 1. Use the interface command to enter the interface context. Administering Avaya G430 Branch Gateway October 2013...

  • Page 64: Primary Management Interface (Pmi) Configuration

    PMI, check with your system administrator. Related topics: Setting the PMI of the Branch Gateway on page 65 Active and configured PMI on page 66 PMI configuration CLI commands on page 66 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 65 • Both the Active and the Configured PMI should be the same IP address. 7. Use the following commands to configure other identification information: • set system contact • set system location • set system name Administering Avaya G430 Branch Gateway October 2013...
  • Page 66 Active PMI6: The IPv6 PMI that the Branch Gateway is currently using, as defined in the running configuration file. PMI configuration CLI commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level Command...

  • Page 67: Example Of Defining A Default Gateway

    Branch Gateway supports both External Call Controllers (ECC) and Internal Call Controllers (ICC). An ICC is an Avaya S8300 Server that you install in the Branch Gateway as a media module. An ECC is an external server that communicates with the Branch Gateway over the network.
  • Page 68 The Branch Gateway must be registered with an MGC in order to provide telephone service. You can set the Branch Gateway’s MGC, and show the current MGC list used to determine the results. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 69 135.6.8.99 and IPv6 address 2001:db8::370:7334 is available, that MGC becomes the Branch Gateway’s MGC. If that server is not available, the Branch Gateway searches for the next MGC on the list, and so on. Gxxx-001(super)# set mgc list 135.6.8.99+2001:db8::370:7334,135.34.54.2,2001:db8::1428:5 Done! Administering Avaya G430 Branch Gateway October 2013...
  • Page 70 IPv4 Address IPv6 Address -------------------- ---------------------------------------------- -- Not Available -- -- Not Available -- -- Not Available -- -- Not Available -- -- Not Available -- -- Not Available -- sls disabled Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 71 Use the set reset-times transition-point command to configure the point at which the primary MGCs in the list end and the LSPs begin. Use the show recovery command to display the reset times. Administering Avaya G430 Branch Gateway October 2013...
  • Page 72 Both the session mgc command and the session icc command open a telnet connection to the MGC. Use the session mgc on an S8300D running VSP. d. To open a connection directly to the Avaya Aura ® Communication Manager System Access Terminal (SAT) application in the MGC, add sat to the command.
  • Page 73 • Use the show icc-monitoring command to display the status of the ICC or Survivable Remote Server monitoring process. Summary of MGC list configuration commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command...

  • Page 74: Dns Resolver

    75 Configuring DNS resolver on page 76 Using DNS resolver to resolve a hostname on page 79 DNS resolver maintenance on page 79 DNS resolver configuration commands on page 79 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 75 It will then start a VPN tunnel with the second main office. Note: VPN is supported in IPv4 only. This typical application is described in full in Failover using DNS on page 536. Administering Avaya G430 Branch Gateway October 2013...
  • Page 76 You can configure up to six DNS servers. Gxxx-001(config-name-server-list:1)# name-server 1 1.1.1.1 Done! Gxxx-001(config-name-server-list:1)# name-server 2 2001:DB8::21F: 3CFF:FE14:6E25 Done! 5. Use the ip domain list command to configure a domain name. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 77 • Assign an index number that ranks the domain name by priority. • Specify the domain name. 6. Repeat Step 5 to configure additional domain names. You can configure up to six domain names. Gxxx-001(config)# ip domain list 1 avaya.com Done! Gxxx-001(config)# ip domain list 2 emea.avaya.com Done! 7.
  • Page 78 Gxxx-001(config-name-server-list:1)# name-server 1 1.1.1.1 Done! Gxxx-001(config-name-server-list:1)# name-server 2 2.2.2.2 Done! Gxxx-001(config-name-server-list:1)# name-server 3 2001:DB8::21F:3CFF:FE14:6E25 Done! Gxxx-001(config-name-server-list:1)# exit Gxxx-001(config)# ip domain list 1 support.avaya.com Done! Gxxx-001(config)# ip domain list 2 global.avaya.com Done! Gxxx-001(config)# ip domain list 3 avaya.com Done! Gxxx-001(config)# ip domain retry 4...
  • Page 79 You can also enable logging messages to a log file or a Syslog server. For a full description of logging on the Branch Gateway, see System logging page 215. DNS resolver configuration commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Administering Avaya G430 Branch Gateway October 2013...
  • Page 80 DHCP or PPP protocols, as well as the list of domain suffixes. show ip Display the DNS resolver’s statistics counters domain statistics show protocol Display the status of a specific management protocol, or all protocols Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 81: Device Status Viewing

    Basic device configuration Device status viewing This section describes the commands used to view the status of the Branch Gateway. For more information about these commands, see Avaya G430 Branch Gateway CLI Reference. Related topics: The show mm command on page 81...
  • Page 82 Basic device configuration • Type of media module • Media module code Device status commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description set utilization Enable CPU utilization measurements show faults Display information about currently active faults...

  • Page 83: Software And Firmware Management

    Software and firmware management You can manage Avaya Branch Gateway software and firmware, either: • Remotely, using an FTP, TFTP, or SCP server, or • Locally, using a USB mass storage device connected to the Avaya Branch Gateway USB port Related topics:...
  • Page 84 • Firmware for media modules Note: You can also use the Branch Gateway to upgrade the firmware and configuration files for IP phones. For details, see Installing and Upgrading the Avaya G430 Branch Gateway Related topics: Firmware bank management on page 84...
  • Page 85 Software and firmware upgrades using FTP/TFTP To upgrade software or firmware, you must obtain an upgrade file from Avaya. Place the file on your FTP or TFTP server. Then, use one of the following commands to upload the file to the Branch Gateway.
  • Page 86 You can upgrade software and firmware using a USB mass storage device. Procedure 1. Obtain an upgrade file from Avaya and place it on your PC. 2. Insert the USB mass storage device into the PC’s USB port, and copy the software or firmware file(s) to the USB mass storage device.
  • Page 87 Sample backup directory after backup on page 92. 2. Obtain the firmware upgrade file(s) from Avaya and place them on your PC. 3. Insert the USB mass storage device into the PC’s USB port, and copy the firmware file(s) to the USB mass storage device as follows: a.
  • Page 88 TFTP server, where file can be any of the following: • announcement-file. Announcements files • capture-file. The packet sniffing buffer • auth-file. Authentication file • capture-file. The packet sniffing buffer Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 89 Basic device configuration • cdr-file. A Call Detail Recording (CDR) file • dhcp-binding. The DHCP binding file Software and firmware management commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description copy file ftp...
  • Page 90 You can use a USB flash drive and a USB externally-powered hub for backups and restores. The Avaya Branch Gateway also supports USB 2.0 high speed (480 Mbits/sec) for faster file transfer between the Branch Gateway and USB mass storage devices.
  • Page 91 You can create multiple backup directories as long as there is space in the USB mass-storage device. Procedure 1. Connect a USB mass-storage device to the Branch Gateway USB port. 2. Type s to commit the current configuration to NVRAM. Administering Avaya G430 Branch Gateway October 2013...
  • Page 92 Configuration file audio.bin Customer-specific VoIP parameters auth-file.cfg Authentication file IPPHONE IP phone scripts and images directory 46xxupgrade.scr 46xxsettings.txt Media modules file directory GWANNC Branch Gateway announcements and music-on-hold file GeorgeAnnouncement.w GeorgiaAnnouncement .wav Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 93 3. Connect the new Branch Gateway to a power source. 4. In the new Branch Gateway, enter show image version to find out which of the two image banks holds the older Branch Gateway firmware version, and what version it is. Administering Avaya G430 Branch Gateway October 2013...
  • Page 94 7. Add the firmware files of the media modules to the USB mass-storage device, as follows: a. From the Avaya support Website, download to your PC the firmware files of the media modules installed in the gateway. For each media module, download all firmware corresponding to the various hardware vintage/suffix versions available for that module.
  • Page 95 9. You can optionally restore or add the Device Manager, as follows: a. From the Avaya support website, download to your PC the firmware file of the Device Manager. b. Insert the USB mass-storage device into the PC’s USB port.
  • Page 96 Embedded web image IPPHONE IP phone scripts and images directory 46xxupgrade.scr 46xxsettings.txt 4601dape1_82.bin 4601dbte1_82.bin Media modules file directory mm722v2.fdl mm714v67.fdl mm711h20v67.fdl mmanalogv67.fdl GWANNC Branch Gateway announcements and music-on-hold file directory DanAnncouncement.wa DanaAnncouncement.w Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 97 Sample backup directory after backup on page 92. 2. From the Avaya support Website, download to your PC the firmware files of the media modules you are adding or upgrading. For each media module, download all firmware corresponding to the various hardware vintage/suffix versions available for that module.
  • Page 98 Thus, secrets do not have to be re-entered if you are copying a configuration file from one Branch Gateway to another. For more information, see Gateway secret management on page 51. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 99 90). Related topics: Configuration file backup and restore commands on page 99 Configuration file backup and restore commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description copy ftp startup- Download a Branch Gateway configuration file from an FTP...
  • Page 100 The dir command also shows the booter file that cannot be changed. You can also use the dir command to list all files in the USB mass-storage device connected to the Branch Gateway. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 101: Chapter 6: Standard Local Survivability (Sls)

    In contrast to the server-based survivability features, SLS operates entirely from the Branch ® Gateway and requires a data set comprised of Avaya Aura Communication Manager translations (survivable ARS analysis and configuration data). This data set is compiled and distributed to a group of devices using the Provisioning and Installation Manager (PIM).

  • Page 102: Media Module Compatibility With Sls

    • Inbound calls from each trunk to pre-configured local analog or IP phones that have registered • Direct inward dialing • Multiple call appearances • Hold and call transfer functions • Contact closure feature • Local call progress tones (dial tone, busy, etc.) Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 103: Avaya Telephones Supported In Sls

    8411B 8411D 8434D The 96xx family and 16xx family of IP phones are not directly referenced in the Branch Gateway CLI. When you administer these phones using the CLI, use the following mapping: Administering Avaya G430 Branch Gateway October 2013...

  • Page 104: Call Processing Functionality In Sls Mode

    Standard Local Survivability (SLS) Table 2: Mapping Avaya 96xx and 16xx IP phones for CLI administration Module name CLI interface name 1603 4610 1608 4610 1616 4620 9610, FW V2.0 + 4606 9620, FW V2.0 + 4610 9630, FW V2.0 + 4620 9640, FW V2.0 +...

  • Page 105: Call Processing Functionality Not Supported By Sls

    • Three party conferences • Last Number Redial • Call Forwarding-Busy/Don’t Answer • No Music On Hold source or announcement playback • Call Center features, including ASAI • Connection Preserving Failover/Failback for Branch Gateways Administering Avaya G430 Branch Gateway October 2013...

  • Page 106: Provisioning Data

    ® Communication Manager provisioning information for the options in the station and trunk media modules is sent through the CCMS channel • Provisioning and Installation Manager (PIM) queries Avaya Aura ® Communication Manager for station/trunk configuration and dial plan routing administration data through SNMP.

  • Page 107: Pim Configuration Data

    Transition Point), ending with SLS, the last choice for the Branch Gateway. When the Link Recovery search settles on the SLS entry in the MGC list, the Branch Gateway registers with SLS (resident on the Branch Gateway) for its call control. Administering Avaya G430 Branch Gateway October 2013...
  • Page 108 'terminal alias', and the password as the registration encryption key. 4. Handles stimuli from all interfaces to establish and remove calls. SLS remains in the Registered state as long as the socket to SLS is open. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 109: Sls Interaction With Specific Branch Gateway Features

    Using the switchhook button on page 112 Call Transfer in SLS mode on page 113 Using contact closure in SLS mode on page 115 Administering IP Softphone in SLS mode on page 116 Administering Avaya G430 Branch Gateway October 2013...
  • Page 110 When a Branch Gateway is in SLS mode, three call appearances, each with limitations, are supported: • The first two call appearances are for incoming or outgoing calls. The first call appearance is the default. • The third call appearance is for outgoing calls only. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 111 Analog telephones on page 111 Analog telephones Newer analog telephones (for example, Avaya 62xx series) have buttons with specific functions for placing a call on Hold: Hold button: A hold function that is local to the telephone Pressing the Hold button causes the analog station to place a hold bridge in both directions at the telephone set.
  • Page 112 This places the call on Hard Hold which prevents you from transferring the call. To return to the call, dial the FAC for Hold. 3. Do one of the following: • Return to the call by dialing the FAC for Hold. The call is re-established. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 113 2. Dial the third party’s number on your phone. 3. You can either: • Wait for the third party to answer and announce the call, then either press the Transfer button again or hang up. Administering Avaya G430 Branch Gateway October 2013...
  • Page 114 Transferring an established call from an analog phone About this task Newer analog phones (for example, Avaya 62xx series) have buttons with specific functions for transferring a call. The switchhook (receiver on/off hook) sends a disconnect signal to the server, and the Transfer/Flash button sends a transfer message to the server.
  • Page 115 If the contact closures are set to manual operation, the FAC operation will not work even though the confirmation tone is heard. However, an event will be logged. Related topics: Contact closure / SLS feature interactions on page 116 Administering Avaya G430 Branch Gateway October 2013...
  • Page 116 Contact closure on page 317. Administering IP Softphone in SLS mode About this task The SLS mode supports shared administrative identity with the Avaya Softphone application, but requires specific station administration. Procedure 1. Access the Communication Manager administrative SAT interface.

  • Page 117: Sls Logging Activities

    • CDR-Informational: is the category (to aid sorting) • 10:46: is the time the call was placed • 00:00: is the duration of the call in hours and minutes or 99:99: if the duration is greater than 99 hours Administering Avaya G430 Branch Gateway October 2013...

  • Page 118: Sls Configuration

    120 Configuring Communication Manager for SLS on page 120 Inherited Class of Restriction (COR) permissions on page 123 Station screen field descriptions for the Branch Gateway on page 124 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 119 172 ISDN Layer 3 country protocols for ISDN Primary Rate service on page 173 Administering BRI parameters on page 174 Trunk group assignment on page 176 Administering trunk-group parameters on page 176 Administering Avaya G430 Branch Gateway October 2013...
  • Page 120 For instructions on configuring SLS in Avaya Aura Communication Manager, see Configuring Communication Manager for SLS on page 120. • Provisioning data from the PIM tool must be gathered from Avaya Aura ® Communication Manager and delivered to the Branch Gateway using PIM. For instructions on gathering...
  • Page 121 Standard Local Survivability (SLS) ® For instructions on accessing the Avaya Aura Communication Manager through the Branch Gateway, see Accessing the registered MGC on page 72. 2. At the SAT, enter change node-names ip to display the IP Node Names screen.
  • Page 122 • Survivable GK Node Name • Survivable COR Inherited Class of Restriction (COR) permissions on page 123 shows the hierarchical relationship among the calling-restriction categories. • Survivable Trunk Dest • 14. Submit the screen. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 123 • locl: (public-network local number call) • op: (operator) • svc: (service) • hnpa: (7-digit NANP call) 3. Toll: Users can only dial these call types: • fnpa: (10-digit NANP call) • natl: (non-NANP call) Administering Avaya G430 Branch Gateway October 2013...
  • Page 124 • Terminal Self-Administration • Enterprise Mobility User • Extension to Cellular • Call Forwarding • Posted Messages • Security Violation Notification • Demand Printing The required security code length is administered system wide. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 125 If TTI is enabled for the system, analog telephones administered with hardware to a virtual extension cannot be changed. For more information about current documentation, product notices, knowledge articles, go to the Avaya Support website at http://support.avaya.com/. Telephone type Model...
  • Page 126 6402 6402 6402D 6402D 6408 6408 6408+ 6408+ 6408D 6408D 6408D+ 6408D+ 6416D+ 6416D+ 6424D+ 6424D+ 7401D 7401D 7401+ 7401+ 7403D 7403D Multi- 7404D 7404D appearance 7405D 7405D digital 7406D 7406D Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 127 7403D IDT2 7406D IP Telephone 4601+ 4601+ Note: When you add a new 4601 IP telephone, you must use the 4601+ station type. This station type enables the Automatic Callback feature. 4602+ 4602+ Administering Avaya G430 Branch Gateway October 2013...
  • Page 128 • 4610SIP with SIP firmware • 4620SIP with SIP firmware • 4620SIP CC (Call Center) • SIP Softphone/Avaya one-X Desktop • Toshiba SP-1020A Note: You must administer any telephone that has SIP firmware Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 129 H.323 or DCP type SoftPhone Native H.323 H.323 Single-connect H.323 or DCP type ISDN-BRI — asai station Any NI-BRI (N1 and N2) telephone NI-BRI 7505D 7505D 7506D 7506D 7507D 7507D 8503D 8503D 8510T 8510T 8520T 8520T Administering Avaya G430 Branch Gateway October 2013...
  • Page 130 Indicates that there is no hardware associated with the port assignment since the switch was set up, and the administrator expects that the extension has a non-IP set. Or, the extension had a non-IP set, and it Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 131 Manager administration tables and obtain the class of service information. PIM module builds a managed database to send for Standard Local Survivability (SLS) on the Branch Gateways. Available for all analog and IP station types. Administering Avaya G430 Branch Gateway October 2013...
  • Page 132 Requires that Call Waiting Indication is disabled. Expansion Module Indicates whether or not this telephone has an expansion module. Enables the administration of the buttons for the expansion module. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 133 Using the CLI to manually configure SLS administration on the gateway on page 139. About this task PIM must be installed on and launched from the Avaya Network Management Console. For information about PIM, see PIM access on page 32.
  • Page 134 10. Use the SLS Update Schedule page to administer up to six SLS updates per day. a. Check the Enable SLS Updates box. b. Set as many as six Daily Updates. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 135 Step on page 0 backs up the PIM database. Avaya encourages users to set a PIM backup schedule or /policy independent of the SLS implementation. If you require the use of the Incoming Call Handling Treatment option for adding or deleting the incoming dial pattern on incoming trunk calls, this route pattern must be modified using the CLI.
  • Page 136 Use this option for non-NANP calls. normal npvt Use this option for national private calls. normal nsvc Use this option for national service calls. normal Use this option for operator calls. attendant Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 137 • The trash can icon is the delete icon that removes the ARS Entry from the table. The Add ARS Entry option may be used to create or edit a maximum of 30 ARS dial pattern entries. Administering Avaya G430 Branch Gateway October 2013...
  • Page 138 Procedure 1. Make any changes to SLS administration desired. 2. While still in SLS mode, enter set sls disable The Branch Gateway responds with the message Survivable Call Engine is disabled. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 139 SLS data set preparation ® It is recommended to plan the SLS coverage and gather information from Avaya Aura Communication Manager before creating the SLS administration data set at the Branch Gateway command line. Strategic selection of the stations and trunks that participate in SLS can ensure that vital communications are spared interruptions caused by network outages.
  • Page 140 Branch Gateway model IP stations G430 You can collect the Communication Manager data using the Communication Manager ® administrative SAT interface. For instructions on accessing the Avaya Aura Communication Manager through the Branch Gateway, see Accessing the registered MGC on page 72.
  • Page 141 6. Gather the necessary information for the following fields: • Extension • Port • Security Code (Optional) - used for the registration of an IP Softphone (RoadWarrior) • Type - as any of the following types: - 2402 Administering Avaya G430 Branch Gateway October 2013...
  • Page 142 - 8434D • Survivable COR • Survivable Trunk Dest • Expansion Module • Name For more information about these fields, see Station screen field descriptions for Media Gateway on page 124. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 143 (IP only) - used for the registration of the IP endpoint • Type — as any of the following types: - 4601 - 4602 - 4602SW - 4606 - 4610SW - 4612 - 4620 - 4620SW - 4621 Administering Avaya G430 Branch Gateway October 2013...
  • Page 144 183. 7. Identify the Branch Gateway modules and check for provisioned trunk ports. 8. At the SAT, enter display port portid, where portid is the trunks port on the target gateway. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 145 Group Type This field specifies the type of trunks associated with this trunk group Outgoing Dial Type The only acceptable values are tone and rotary. If the field is set to automatic or mf, Administering Avaya G430 Branch Gateway October 2013...
  • Page 146 Customer identification of trunk group Codeset to Send Display Describes which Q.931 code-sets are allowed to send Display IEs Codeset to Send National IEs Describes which Q.931 code-sets are allowed to send National supported IEs Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 147 1. At the SAT, enter display ds1 location to display the DS1 administration for a particular circuit pack location. 2. Gather the following DS1 information for each DS1 facility: • Name • Bit-Rate • Signaling Mode • Channel Numbering • Connect • Interface • Side Administering Avaya G430 Branch Gateway October 2013...
  • Page 148 DS1 facility. Accepts up to 15 characters. Note: Avaya BRI stations support only ASCII characters. Non-ASCII characters, such as Eurofont or Kanafont, are displayed incorrectly on a BRI station. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 149 The ETSI and ISO QSIG specifications require that B-channels on an E1 be encoded as 1 to 30 in the Channel ID IE. Prior to the existence of this field, Avaya Communication Manager only used this scheme for Country Protocols 2a (Australia) and 13a (Germany 1TR6). Available only with ISDN-PRI signaling on a private network.
  • Page 150 DS1 link must have complementary settings in this field. Otherwise, the D-channel cannot function. For example, if the Avaya S8XXX server at one end of the link is administered as network, the other end must be administered as user. Available only when this DS1 link is providing an ISDN-PRI connection in a private network.
  • Page 151 Selects the protocol that matches the network service provider’s protocol in countries whose public networks allow multiple layer-3 signaling protocols for ISDN-PRI service. Contact the network service provider to verify that the protocols match. Administering Avaya G430 Branch Gateway October 2013...
  • Page 152 DS1 link must have complementary settings in this field. Otherwise, the D-channel cannot function. For example, if the Avaya S8XXX server at one end of the link is administered as network, the other end must be administered as user. Available only when this DS1 link is providing an ISDN-PRI connection in a private network.
  • Page 153 Valid Entry Usage 1 to 2000 Trunk group number used for channel selection. Associated Signaling Available only if Group Type field is isdn-pri. Valid Entry Usage Enables associated signaling. Enables non-facility associated signaling. Administering Avaya G430 Branch Gateway October 2013...
  • Page 154 • Country Protocol • DCP/Analog Bearer Capability • Companding Mode • TEI • Directory Number A • Directory Number B • SPID-A • SPID-B • Endpt Init • Layer 1 Stable Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 155 Name The name used to identify the circuit pack. Accepts up to 15 alphanumeric characters. Note: Avaya BRI stations support only ASCII characters. Non-ASCII characters, such as Eurofont or Kanafont, are displayed incorrectly on a BRI station. ISDN-BRI Trunk/Interface Determines glare handling.
  • Page 156 2. Scroll to page 5 and determine how the Multinational Locations or Multiple Locations fields are set: • If either of these fields is set to y (enabled), then proceed to Step page 0 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 157 Contact Closure Open Code FAC used to open a contact closure relay. Contact closures control electrical devices remotely. Users use an FAC to activate electrical devices such as electrical door locks. If Contact Administering Avaya G430 Branch Gateway October 2013...
  • Page 158 Answer Hold-Unhold FAC to Hard hold the call. This value must conform to the FACs or dial access codes defined by the dial plan. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 159 SLS only supports two codecs: • G.711 A-law • G.711 U-law General system parameters field descriptions ® For information about the fields on the IP codec set screen, see Avaya Aura Communication Manager Screen Reference. Administering Avaya G430 Branch Gateway October 2013...
  • Page 160 160. Once you discover a match with Route Pattern , use the entries from this row in the ARS Analysis table to complete the following three entries for the SLS Dial-Pattern table: • Min • Max • Dialed String Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 161 To gather the Incoming Call Handling Treatment and ARS Digit Conversion information in Communication Manager, you must first know which trunk groups are assigned to the gateway of interest. After verifying this information, perform the following steps: Administering Avaya G430 Branch Gateway October 2013...
  • Page 162 Japan. blank When Called Number has also been set to blank, so that any length of digits associated with the Called Party IE of the Incoming SETUP message matches this field. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 163 Enter exit to leave the second-level sub-contexts and return to the (super-sls)# context. See Summary of SLS configuration commands on page 187 for a complete hierarchical listing of all SLS CLI commands. Administering Avaya G430 Branch Gateway October 2013...
  • Page 164 Media module compatibility with SLS on page 102 9. Administer the station information. Administering station parameters on page 166. 10. Administer DS1 trunks as required. Refer to Administering DS1 parameters on page 170. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 165 The fac string must be unique and must not conflict with station extension numbers and Trunk Access Codes (TACs). Examples • set fac ars2 *9 • set fac contact-close 8 Administering Avaya G430 Branch Gateway October 2013...
  • Page 166 2. Depending on the class (analog, dcp, or ip, set in Step on page 0 ), enter set type model, where model is a value from Class values in SLS station context page 168. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 167 Standard Local Survivability (SLS) For example, set type ip4620 sets the previously-administered extension “1234567” as an Avaya 4620 IP phone. 3. For analog and dcp classes only (set in Step on page 0 ), enter set port module-port for this station, where module-port is a value in...
  • Page 168 11. Enter exit to leave the station context in SLS. Class values in SLS station context analog dcp2402 ip4601 analog2500 Since there is just one entry, the model is optional; analog2500 is the default value. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 169 Analog station ports* G430 or G450 MM711 8 possible ports MM712 8 possible ports MM714 4 possible ports (ports 1-4) MM714B 4 possible ports (ports 1-4) MM716 24 possible ports MM717 24 possible ports Administering Avaya G430 Branch Gateway October 2013...
  • Page 170 B-channels on an E1 interface, where method is one of the following values: • seq. Sequential codes of B-channels 1-30 in the ISDN Channel Identification • tslot. Timeslot method Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 171 12. Enter set interface-companding type to set the interface to agree with the companding method used by the far-end of the DS1 circuit for SLS mode, where type is one of the following values: Administering Avaya G430 Branch Gateway October 2013...
  • Page 172 Country United States (AT&T mode, also known as 5ESS) Australia (Australia National PRI) Japan Italy Netherlands Singapore Mexico Belgium Saudi Arabia United Kingdom (ETSI) Spain France (ETSI) Germany (ETSI) Czech Republic Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 173 Nortel mode (also known as DMS) Telecordia (NI-2) Country 2 (Australia) Australia National PRI ETSI invalid invalid Country 10 (United DASS Kingdom) ETSI invalid invalid Country 12 (France) French National PRI ETSI invalid invalid Administering Avaya G430 Branch Gateway October 2013...
  • Page 174 4. If the BRI link is employed with ISDN, and the glare-handling convention is specified as peerMaster or peerSlave for the ISDN link (set in Step 3), enter set side side to specify the glare mode: either a or b. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 175 14. If the BRI link is employed with ISDN, enter set layer1-stable {yes | no} to determine whether or not to keep the physical layer active (stable) between calls. Administering Avaya G430 Branch Gateway October 2013...
  • Page 176 1 loop-start establishes an analog loop-start trunk group number 1. Administering trunk-group parameters Procedure 1. Enter trunk-group tgnum group-type, where tgnum is any number from 1 to 2000 and group-type can be one of the following: • loop-start (analog) Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 177 If an MM722 is inserted into slot V2 and an ISDN BRI trunk is to be administered for port 1, then add port v201 adds a BRI trunk for the first physical port of the Administering Avaya G430 Branch Gateway October 2013...
  • Page 178 • blank (use this value to prevent any absorb or insert digit treatment from being applied) • absorb1 • absorb2 • absorb3 • absorb4 • absorb5 • insert1 • insert2 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 179 • preferred. The central office might offer the call request on another available channel 13. For ISDN trunks, enter set digit-handling method to define the order of reception/transmission to be considered with the flow of inbound/outbound: • enbloc-enbloc • enbloc-overlap • overlap-enbloc • overlap-overlap Administering Avaya G430 Branch Gateway October 2013...
  • Page 180 • public. The Numbering Plan Indicator meets the E.164 standard and the Type of Number is national Note: The SLS application is intended to operate into PSTN trunk interfaces. For this reason, the only two choices for network numbering plans identification are public Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 181 Treat Insert ----- ---------- ------ ---- ------------------- ------- ------ t1inband dtmf wink/immediate Name = Willow Street 2 Ports = v201,v202,v203,v204,v205,v206,v207,v208,v209,v210,v211,v212 Incoming-Dest Incoming-Dial Trunk-Hunt ------------- ------------- ---------- ascend The report lists the trunk-group parameters. Administering Avaya G430 Branch Gateway October 2013...
  • Page 182 (FAS) e1-isdn MM710 D-channel is not associated with this facility (NFAS), and the DS1’s signaling-mode is set to isdnext t1-inband MM710 T1 Robbed-bit signaling application e1-inband MM710 E1 CAS signaling application Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 183 The command line prompt changes to sls-sig-group <sgnum>. If you want to remove the signaling group from the SLS administration, enter exit to leave the second-level sig-group context and return to the (super-sls)# context, and then enter clear sig-group sgnum. Administering Avaya G430 Branch Gateway October 2013...
  • Page 184 5. Enter show to check the signaling groups administration. The report lists the signaling groups parameters. For example: Sig-group Tg-Select Assoc-Sig Prime-Dchan Nfas-Modules/Nfas-Id --------- --------- --------- ----------- ------------------------------------- 005v424 6. Enter exit to leave the sig-group context in SLS. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 185 You can either insert or delete digits, but not both. 9. Enter show to check the outbound dial-pattern string administration. The report lists the dial-pattern parameters. For example: Min/Max Trunk Delete/Insert Dialed-String/Deny Length Type Group Digits ------------------ ------ ---- ----- ---------------------- Administering Avaya G430 Branch Gateway October 2013...
  • Page 186 The command line prompt changes to sls-incoming-routing <tgnum>. If you want to remove the incoming routing treatment from the SLS administration, enter Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 187 ------------- ------ ------------- ------ ----- 5381000 enbloc 5381001 enbloc Summary of SLS configuration commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root Level First Level Context Second Level Description Commands Commands Context Commands...
  • Page 188 (stable) between calls in SLS set name Identify the user name for an ISDN facility in SLS set side Specify the glare-handling conditions when the set interface command has Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 189 DS1 channel in SLS clear fac Delete an administered Feature Access Code for clear Delete an entry for a particular incoming routed incoming- string that is associated routing with a given trunk group in Administering Avaya G430 Branch Gateway October 2013...
  • Page 190 Establish the minimum length of the dialed string in length set tgnum Designate the trunk-group number in SLS set type Administer the type of outbound call in SLS Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 191 Identify the user name for a DS1 facility in SLS set protocol- Specify country protocol for countries whose public version networks allow for multiple ISDN Layer 3 country protocols for ISDN Primary Rate service in SLS Administering Avaya G430 Branch Gateway October 2013...
  • Page 192 Specify the dial access code for the attendant feature, and specify the station which serves as the branch office attendant position set date- Set a date format for the SLS data set format Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 193 List the codec set entries for SLS codec-set show last- Display when the last PIM update of SLS data pim-update occurred show max-ip- Display the maximum IP registration administration registrations in the SLS data set Administering Avaya G430 Branch Gateway October 2013...
  • Page 194 Information Channel Selection field does not specify a preferred channel for bearer transport in SLS show List all SLS parameters for this signaling-group station Administer stations for SLS Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 195 Administer the port appropriate for SLS clear tac Remove a trunk access code (TAC) assignment from a trunk group in SLS remove port Remove the port assignment from a trunk group in SLS Administering Avaya G430 Branch Gateway October 2013...
  • Page 196 Elements to the user phone in SLS set dial Define the method for sending outbound digits in set digit- Define how the inbound/ outbound calls handle the handling transmission/reception of the dialed pattern in SLS Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 197 SLS set send- Define whether or not the calling, connected, called, number or busy party’s administered number is sent to the network on outgoing or incoming calls in SLS Administering Avaya G430 Branch Gateway October 2013...
  • Page 198 Specify the trunk-hunting search within a facility in an hunt ISDN trunk group or through a non-ISDN digital trunk group in SLS show List all trunk-group SLS parameters for this trunk- group Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 199: Chapter 7: Ethernet Ports

    Use a crossover network cable when you connect a computer or other endpoint device to the fixed router port. For all other Ethernet ports on the Branch Gateway, you can use either a standard network cable or a crossover network cable to connect any device. Administering Avaya G430 Branch Gateway October 2013...

  • Page 200: Roadmap For Configuring Switch Ethernet Ports

    • SNMP Link Up and Link Down traps. For more information, see SNMP trap configuration on page 309. Summary of switch Ethernet port configuration CLI commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description set port duplex...
  • Page 201 Set the speed of a port or range of ports An error message is generated if you attempt to set the speed when auto-negotiation is enabled. show port edge state Display the edge state of a port Administering Avaya G430 Branch Gateway October 2013...

  • Page 202: Configuring The Wan Ethernet Port

    WAN Ethernet port traffic shaping You can use traffic shaping to determine the data transfer rate on the WAN Ethernet port. To set traffic shaping, use the traffic-shape rate command in the interface context. To Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 203 For instructions on how to configure backup interfaces, see Backup interfaces page 256. Summary of WAN Ethernet port configuration CLI commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level command Command...

  • Page 204: Dhcp Client Configuration

    DHCP client applications on page 205 Configuring the DHCP client on page 205 Examples of DHCP lease release and renew on page 207 Commands used for DHCP client maintenance on page 207 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 205 DHCP client. By default, the client identifier is usually the MAC address of the Branch Gateway FastEthernet interface. • Use the ip dhcp client hostname command to set the hostname for the DHCP client. By default, the DHCP client uses the Branch Gateway’s hostname. Administering Avaya G430 Branch Gateway October 2013...
  • Page 206 A message appears, displaying the IP address and mask assigned by the DHCP server. For example: Gxxx-001(config-if:FastEthernet 10/2)# ip address dhcp Done! Interface FastEthernet 10/2 assigned DHCP address 193.172.104.161, mask 255.255.255.0 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 207 • show ip dhcp-client statistics • clear ip dhcp-client statistics For a description of these commands, see Summary of DHCP client configuration CLI commands on page 208 or the Avaya Branch Gateway G430 CLI Reference Administering Avaya G430 Branch Gateway October 2013...
  • Page 208 Summary of DHCP client configuration CLI commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level Command...

  • Page 209: Lldp Configuration

    The LLDP protocol allows stations attached to a LAN to advertise information about the system (such as, its major capabilities and its management address) and information regarding the station’s point of attachment to the LAN (port ID and VLAN information) to other stations Administering Avaya G430 Branch Gateway October 2013...
  • Page 210 Optional 802.1 TLVs on page 211 Mandatory TLVs • End-of-LDPDU • Chassis ID • Port ID • Time to Live Optional TLVs • Port description • System description • System name Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 211 Gxxx-001(super)# set port lldp tlv 10/3 enable all Done! The device now advertises all mandatory and optional TLVs to neighboring network devices supporting LLDP. 4. If required, change any of the following timing parameters: Administering Avaya G430 Branch Gateway October 2013...
  • Page 212 You can configure only ports 10/3 and 10/4 to support LLDP. Summary of LLDP configuration CLI commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description set lldp re-init-delay Set the delay from when a port is set to LLDP “disable”...
  • Page 213 Display the global LLDP configuration show port lldp config Display port-level LLDP configuration show port lldp vlan- Show the VLANs that are being transmitted on a specific port name config Administering Avaya G430 Branch Gateway October 2013...
  • Page 214 Ethernet ports Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 215: Chapter 8: System Logging

    Configuring a log file on page 220 Configuring a session log on page 223 Logging filter configuration on page 224 Accessing diagnostic logs on page 229 Summary of logging configuration CLI commands on page 230 Administering Avaya G430 Branch Gateway October 2013...

  • Page 216: Types Of Logging Sinks

    You can define up to three Syslog servers with either IPv4 or IPv6 addresses.. Procedure 1. Define the Syslog server by entering set logging server followed by the IP address of the server. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 217 • ftpd. FTP daemon • kern. kernel • alert. Log alert • audi. Log audit • ntp. NTP subsystem • lpr. Printing • sec. Security • syslog. System logging • uucp. Unix-to-Unix copy program Administering Avaya G430 Branch Gateway October 2013...
  • Page 218 You can delete a Syslog server from the Syslog server table. Procedure Enter clear logging server followed by the IP address of the Syslog server you want to delete. For example: Gxxx-001(super)# clear logging server 147.2.3.66 Done! Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 219 Syslog sink default settings Severity: Warning Facility: Local 7 Access level: Read-write Syslog message format Syslog messages are arranged chronologically and have the following format: <34> Oct 11 22:14:15 host LINKDOWN [005ms, SWICHFABRIC-Notification:Port 10/3 Link, ID=1234567890 Administering Avaya G430 Branch Gateway October 2013...

  • Page 220: Configuring A Log File

    230 . For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Configuring a log file About this task A log file is a file of data concerning a system event, saved in the flash memory.
  • Page 221 Gxxx-001 (super)# show logging file content <190>Apr 21 16:28:32 149.49.77.11 -NoTag: -NoUTC 2009 055 1 mediagateway.g430 | 0 coldStart[BOOT-Informational: System boot up from cold reset, ID=N/A <187>Apr 21 16:28:32 149.49.77.11 -NoTag: -NoUTC 2009 525 1 mediagateway.g430 | 0 MSY-TRPMAJNA[VOICE-Error: No Call Controller Found, ID=N/A <190>Apr 21 14:30:25 149.49.77.11 -NoTag: -NoUTC 2009 965 1...
  • Page 222 System logging mediagateway.g430 | 0 BOOT MESSAGE[BOOT-Informational: Booting from bank B with firmware version 29.22.50, ID=N/A <190>Apr 21 14:30:25 149.49.77.11 -NoTag: -NoUTC 2009 965 1 mediagateway.g430 | 0 coldStart[BOOT-Informational: System boot up from cold reset, ID=N/A <187>Apr 21 14:30:25 149.49.77.11 -NoTag: -NoUTC 2009 425 1 mediagateway.g430 | 0 MSY-TRPMAJNA[VOICE-Error: No Call Controller...

  • Page 223: Configuring A Session Log

    The following output is an example of the show logging session condition. command that displays whether session logging is enabled or disabled, and lists all filters defined for session logging. Example Gxxx-001 (super)# show logging session condition Administering Avaya G430 Branch Gateway October 2013...

  • Page 224: Logging Filter Configuration

    225 Severity levels on page 225 Default sink severity levels on page 226 Application filtering on page 226 Syslog server example on page 228 Log file example on page 228 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 225 Gxxx-001(super)# show logging file content critical qos 50 Severity levels Severity level Code Description emergency System is unusable alert Immediate action required critical Critical condition Administering Avaya G430 Branch Gateway October 2013...
  • Page 226 CNA test plugs config Configuration changes dhcp-relay DHCP requests relaying dhcpc DHCP client package dhcps DHCP server package dialer Dialer interface messages dnsc DNS client package Cooling system filesys File system problem (flash) Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 227 Internal TFTP server threshold RMON alarms tracker Object tracker messages USB devices messages usb-modem USB modem messages vj-comp Van Jacobson header compression messages vlan VLAN package voice Voice failures WAN plugged-in expansion Administering Avaya G430 Branch Gateway October 2013...
  • Page 228 ISAKMP application to informational. Finally, the user displays the filter settings. Gxxx-001(super)# set logging session enable Done! Gxxx-001(super)# set logging session condition all Error Done! Gxxx-001(super)# set logging session condition ISAKMP Informational Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 229: Accessing Diagnostic Logs

    2. Enable screen capture logging in your terminal emulation program. 3. Run the show all logs command. 4. Send a copy of the screen capture log file to Avaya through an email or as an attachment. For more information about accessing diagnostic logs, see CLI Reference Avaya Branch Gateway G430, 03-603234.

  • Page 230: Summary Of Logging Configuration Cli Commands

    G450-gloin-031(super)# Summary of logging configuration CLI commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description copy syslog-file ftp...
  • Page 231 Display the filter conditions defined for the Syslog output sink condition show logging session Display the filter conditions defined for message logging to the current console session condition Administering Avaya G430 Branch Gateway October 2013...
  • Page 232 System logging Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 233: Chapter 9: Voip Qos

    RTP and RTCP are the basis of common VoIP traffic. RTP and RTCP run over UDP and incur a 12-byte header on top of other (IP, UDP) headers. Running on PPP or frame relay, these protocols can be compressed. Administering Avaya G430 Branch Gateway October 2013...

  • Page 234: Header Compression Configuration

    • IP Header compression (IPHC) method, as defined by RFC 2507. IPHC-type compression applies to RTP, TCP, and UDP headers. • Van Jacobson (VJ) method, as defined in RFC 1144. VJ compression applies to TCP headers only. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 235 • ip rtp max-time • ip rtp non-tcp-mode IETF mode is not compatible with non-IETF mode. • ip rtp port-range For example: Gxxx-001(config-if:Serial 4/1:1)# ip rtp compression-connections 48 Done! Gxxx-001(config-if:Serial 4/1:1)# ip tcp compression-connections 48 Administering Avaya G430 Branch Gateway October 2013...
  • Page 236 Summary of IPHC header compression CLI commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level command First level command...
  • Page 237 Display header compression statistics for a specific interface. If no interface is header- specified, statistics for all interfaces are compression displayed. Administering Avaya G430 Branch Gateway October 2013...
  • Page 238 The compression method employed is the VJ compression. Note: The ip rtp header-compression command always overrides the ip tcp header-compression command. Both commands enable TCP header compression, but they differ in the methods employed. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 239 Summary of Van Jacobson header compression CLI commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level command...

  • Page 240: Commands Used To Configure Qos Parameters

    Commands used to display and clear header compression statistics For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. • show ip rtp header-compression •...
  • Page 241 Avaya Branch Gateway G430 CLI Reference Avaya Branch Gateway G450 CLI Reference Summary of QoS, RSVP, and RTCP configuration CLI commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. Administering Avaya G430 Branch Gateway...

  • Page 242: Weighted Fair Voip Queuing

    VoIP QoS For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description set qos Permit the setting of VoIP QoS-bearer related parameters for the Media Gateway Processor and VoIP engines. The parameters you bearer define using this command may conflict with the default QoS list (400).
  • Page 243 VoIP QoS Summary of WFVQ configuration CLI commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level Command...

  • Page 244: Priority Queuing

    Summary of priority queueing configuration CLI commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level Command...
  • Page 245 Disable VoIP queueing and re-enable WFVQ voip-queue- Set the maximum query delay for which to estimate the high priority queue size delay necessary to meet the queuing delay. show queueing Display the priority queue configuration Administering Avaya G430 Branch Gateway October 2013...
  • Page 246 VoIP QoS Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 247: Chapter 10: Modems And The Branch Gateway

    For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Note: If you have an Avaya Service contract, no configuration of the USB port is necessary for Services personnel to remotely access the Branch Gateway through a USB modem. Related topics:...
  • Page 248 Summary of CLI commands for configuring the USB port for modem use For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level...
  • Page 249 Display the USB-modem interface parameters, the current status of the USB port, and the interfaces identity of any USB modem connected to the USB port. Administering Avaya G430 Branch Gateway October 2013...
  • Page 250 Modems and the Branch Gateway Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 251: Chapter 11: Wan Interfaces

    Configuring the initial WAN on page 251 Configuring the initial WAN Procedure 1. Use the Fast Ethernet port on the G430 chassis as the endpoint for a WAN line by configuring this interface for PPPoE. Configuring PPPoE on page 252.
  • Page 252 • Dynamic CAC is not enabled on the interface. See Dynamic CAC page 280. • The interface is not part of a primary-backup interface pair. See Backup interfaces on page 256. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 253 9. Optionally, shut down the port and the PPPoE client, if configured, with the shutdown command in the interface context. Summary of PPPoE commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. Administering Avaya G430 Branch Gateway...
  • Page 254 WAN interfaces For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level command Command Description interface Enter the FastEthernet interface context fastethernet encapsulation Change the encapsulation to PPPoE pppoe ip address Configure an IP address and subnet...

  • Page 255: Wan Configuration And Testing Connectivity

    • Use the ping command to send ICMP echo request packets to another node on the network. Each node is periodically pinged and checked if an answer was received. This checks host reachability and network connectivity. Administering Avaya G430 Branch Gateway October 2013...
  • Page 256 WAN interfaces Summary of WAN configuration verification commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description...
  • Page 257 Summary of backup interfaces commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Administering Avaya G430 Branch Gateway...
  • Page 258 Dynamic CAC on page 280. For ® information about IGAR, see Administrator Guide for Avaya Aura Communication Manager. Modem dial backup is a generic data dial backup feature that can carry not only signalling but every type of IP traffic. However, the low bandwidth of an analog modem would be likely to cause congestion.
  • Page 259 282. Modem dial backup uses a modem connected directly to the Branch Gateway’s USB or Console port. The modem can also be used to access the Branch Gateway CLI from a remote Administering Avaya G430 Branch Gateway October 2013...
  • Page 260 Note: Modem dial backup has complex interactions with other configuration modules within the Branch Gateway and on your network. Before configuring modem dial-backup, Avaya recommends reading Application Note - VoIP Network Resiliency. This document discusses the issues of network design for maximum resiliency, capacity planning for optimum performance, configuration options for network devices, strategies for implementing routing across the network, and security concerns.
  • Page 261 247. Configuring modem dial backup Procedure 1. From the general context, use the show interfaces USB-modem command to verify that the modem is connected. You may be required to enable the modem. Administering Avaya G430 Branch Gateway October 2013...
  • Page 262 The Dialer interface dials each number associated with a dialer string, in order, until either a connection is made, or the number configured in the dialer persistent max-attempts command is reached. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 263 MTU 1500 bytes, Bandwidth 28 kbit IPSec PMTU: copy df-bit, Min PMTU is 300 Reliability 1/255 txLoad 255/255 rxLoad 255/255 Encapsulation PPP Link status trap disabled Keepalive track not set Keepalive set (10 sec) Administering Avaya G430 Branch Gateway October 2013...
  • Page 264 9. Enter the context of the interface which the Dialer is to back up, and use the backup interface command to configure the Dialer interface as the backup interface. For example: G430-001(if:Tunnel 1)# backup interface dialer 1 Done! Interface Dialer 1 is now selected as the backup interface to the selected interface.
  • Page 265 PSTN for bearer traffic. For more information on configuring Dynamic CAC, see Dynamic CAC page 280. For more information on configuring IGAR, see Administrator Guide for Avaya ® Aura Communication Manager.
  • Page 266 WAN interfaces Note: In a situation where the same modem is used for inbound Avaya Service calls and outbound dial backup calls, only one call can be active at any time. Note: Refer to www.multitech.com for a listing of modem AT commands used to configure the modem directly.
  • Page 267 WAN interfaces Related topics: Command sequence on page 267 Command sequence explanation on page 269 Command sequence !Step 1 Gxxx-001(super-if:Loopback 1)# exit Gxxx-001(super)# interface loopback 1 Administering Avaya G430 Branch Gateway October 2013...
  • Page 268 Gxxx-001(super)# interface fastethernet 10/2 Gxxx-001(if:fastEthernet 10/2)# backup interface Dialer 1 Done! Gxxx-001(if:fastEthernet 10/2)# exit Gxxx-001(super)# Step 13 Gxxx-001(super)# router ospf Gxxx-001(super router:ospf)# network 149.49.4.4 0.0.0.3 area 0.0.0.5 Done Gxxx-001(super router:ospf)# exit Gxxx-001(super)# Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 269 8. Associate the Dialer interface with its physical port with the dialer modem- interface command. The Dialer interface must be configured to use a physical interface on the device to which the modem is connected. Modem dial backup is supported on the USB port. Administering Avaya G430 Branch Gateway October 2013...
  • Page 270 Certain dialer-related log messages are generated to aid you in troubleshooting problems with modem dial backup. In addition, messages generated by the modem and the PPP session are available to help with troubleshooting modem dial backup issues. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 271: Modem Dial Backup Logging Messages

    Debug: This message provides information that can be useful in debugging certain problems, but requires no action itself. Warning: This message indicates a condition requiring user intervention and troubleshooting. Modem dial backup logging messages Dialer Messages Dialer Messages are messages generated by the Dialer interface. Administering Avaya G430 Branch Gateway October 2013...
  • Page 272 3, the message received would be Dialer 1 string 3 5551314. Dialer 1 timer Debug When the Dialer interface is None required. expired configured with the dialer persistent re-enable command, Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 273 USB modem Informational When the USB modem is None required. was detected discovered by the device and the initialization string is successful, a message is generated indicating that the device is ready to dial. Administering Avaya G430 Branch Gateway October 2013...
  • Page 274 LCP then comes up to pass Link Maintenance packets during the session, and goes down after the maintenance is complete. LCP comes up when a termination Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 275 Summary of modem dial backup commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level Command...
  • Page 276 Enter the FastEthernet, Loopback, or Tunnel interface configuration context (fastethernet | loopback| tunnel) backup Set the Dialer interface as the backup interface for the current interface interface dialer ip default- Define a default gateway (router) gateway Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 277 The destination interface is only declared to be alive if the next hop is also reachable. This feature is critical for mechanisms such as policy-based routing that must guarantee service on a particular path. Administering Avaya G430 Branch Gateway October 2013...
  • Page 278 Figure 9: Branch Gateway with T1 and xDSL lines For example, your branch office might have a G430 that connects to an external router that connects to Headquarters over a T1 line and through an xDSL connection to the Internet. The T1 line is used for voice traffic, while data packets are sent over the xDSL line.
  • Page 279 Summary of ICMP keepalive configuration commands on page 279 For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Example of configuring ICMP keepalive The following example configures ICMP keepalive on interface fastethernet 10/2 to send keepalive packets to IP address 135.64.2.12 using MAC address 11.22.33.44.55.66, at five...
  • Page 280 Note: ® Dynamic CAC works in conjunction with the Avaya Aura Communication Manager Call Admission Control: Bandwidth Limitation (CAC-BL) feature. A related feature is Inter- Gateway Alternate Routing (IGAR), which provides a mechanism to re-route bearer traffic from the WAN to the PSTN under certain configurable conditions.
  • Page 281 Summary of dynamic CAC configuration commands on page 281 or Avaya Branch Gateway G430 CLI Reference . Summary of dynamic CAC configuration commands For more information about these commands, see the Avaya G430 CLI Reference. Root level Command Description command...
  • Page 282 A simple object tracker monitors a single RTR, and its state directly reflects the state of the RTR. A more advanced object tracker is a track list, which Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 283 AND argument, then the state of the list is up if the state of all its objects is up, and down if the state of one or more of its objects is down. Administering Avaya G430 Branch Gateway October 2013...
  • Page 284 You can register either a VPN tunnel or an interface with an object tracker. For more information see the definition of the keepalive-track command in the Avaya Branch Gateway G430 CLI Reference. Note: You cannot configure both DHCP Client and object tracking on the same WAN FastEthernet interface.
  • Page 285 Done! 7. Optionally, configure the RTR parameters that determine when the state of the remote device is considered up or down. If you do not configure these characteristics, their default values are used: Administering Avaya G430 Branch Gateway October 2013...
  • Page 286 Note that a track list is itself an object tracker. Therefore, you can configure track lists containing object trackers which are either simple object trackers, or other track lists. Related topics: Configuring a simple object tracker on page 287 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 287 2. Use the description command to enter a description for the track list. 3. Use the object command to add an object tracker to the list. Note: The object tracker can be a simple one tracking a single RTR, or a track list. Administering Avaya G430 Branch Gateway October 2013...
  • Page 288 Tasks for maintaining object tracking Using the show commands, you can display RTR and Object Tracking configuration, and enable RTR and object tracking logging to a CLI terminal. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 289 For more information about these commands, see Summary of object tracking configuration commands on page 296 or the Avaya Branch Gateway G430 CLI Reference Related topics: Viewing RTR and object trackers logging on page 289 Example of tracking a single remote device...
  • Page 290 2. The second step is to configure an object tracker which tracks the state of RTR 5. For example: Gxxx-001(config)# track 1 rtr 5 Gxxx-001(config-track rtr 1)# description “track rtr-5” Done! Gxxx-001(config-track rtr 1)# exit Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 291 RTR 6. For example: Gxxx-001(config)# track 1 rtr 5 Gxxx-001(config-track rtr 1)# description “track rtr-5” Done! Gxxx-001(config-track rtr 1)# exit Gxxx-001(config)# track 2 rtr 6 Gxxx-001(config-track rtr 2)# description “track rtr-6” Done! Gxxx-001(config-track rtr 2)# exit Administering Avaya G430 Branch Gateway October 2013...
  • Page 292 If the current connection is lost, the Branch Gateway can failover to a backup gateway, and attempt to establish a VPN connection to it. A typical application of this type is described in full in Failover using a peer-group page 542. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 293 4. Register the WAN FastEthernet interface with the track list. 5. Define Loopback 1 as a backup interface for the WAN FastEthernet interface. Administering Avaya G430 Branch Gateway October 2013...
  • Page 294 293), the backup interface command is used to specify a backup interface. This typical application illustrates an alternative to the backup interface command, using policy-based routing (PBR) which configures a routing scheme for specified Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 295 ! Configure next hop list 10 with interface fastethernet 10/2 as the ! first next hop, and the VLAN interface used to connet to the external ! router as the second next hop. ip next-hop-list 10 Administering Avaya G430 Branch Gateway October 2013...
  • Page 296 Summary of object tracking configuration commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 297 Display the global operational status of the RTR feature operationa l- state show track Display tracking information track Configure an object tracker description Set a description for the object tracker Administering Avaya G430 Branch Gateway October 2013...
  • Page 298 Second level Description command command command object Add an object tracker to a track list threshold count Set the upper and lower thresholds for the threshold in the track list command Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 299: Chapter 12: Emergency Transfer Relay (Etr)

    MGC. ETR services are offered on installed MM714B media modules. When ETR is activated, the G430 connects the MM714B’s trunk port 5 to line port 4. All calls are then directed by the analog relays between the outside lines and the analog telephones.

  • Page 300: Summary Of Etr Commands

    A call in progress is terminated when ETR is activated either automatically or manually. Summary of ETR commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description set etr...
  • Page 301 • Module status (in service, out of service, or out of service waiting for off-hook) • Trunk number of the trunk connected to ETR • Line number of the line connected to ETR • Line status (off hook or on hook) Administering Avaya G430 Branch Gateway October 2013...
  • Page 302 Emergency Transfer Relay (ETR) Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 303: Chapter 13: Snmp

    Branch Gateway. Related topics: Agent and manager communication on page 304 SNMP versions on page 305 SNMP trap configuration on page 309 Dynamic trap manager on page 313 SNMP configuration examples on page 315 Administering Avaya G430 Branch Gateway October 2013...

  • Page 304: Agent And Manager Communication

    SNMP management station, to perform the action needed when a trap is detected. Note: For a list of traps and MIBS, see Gateway Traps for the Avaya G250, G350, G450, and G700 Media Gateways. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 305: Snmp Versions

    SNMPv1 or SNMPv2c. In addition, traps are sent to designated trap receivers. Packets with trap information also contain a trap community string. Administering Avaya G430 Branch Gateway October 2013...
  • Page 306 CBC-DES56 protocol for encryption or privacy. An unlimited number of users can access SNMPv3 at the same time. Related topics: SNMP security levels on page 307 snmp-server user command on page 307 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 307 In SNMPv3, each user is mapped to a group. The group maps its users to defined views. These views define sets of access rights, including read, write, and trap or inform notifications the users can receive. Administering Avaya G430 Branch Gateway October 2013...
  • Page 308 WriteView WriteView WriteView WriteCommG NoAuthNoPriv snmpv1 snmpv1 snmpv1 WriteView WriteView WriteView v3ReadOnlyG v3 (USM) AuthNoPriv v3configView v3configVie v3AdminView v3 (USM) AuthPriv v3ReadWriteG v3 (USM) AuthNoPriv v3configView v3configView v3configVie Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 309: Snmp Trap Configuration

    You can add and remove addresses from the trap receivers table. In addition, you can limit the traps sent to specified receivers. You can also enable and disable Administering Avaya G430 Branch Gateway October 2013...
  • Page 310 Various types of SNMP traps can be sent. You can modify the type of trap by setting the notification-list parameter of the snmp-server host command to one of the following types: • all. All traps. This is the default. • generic. Generic traps • hardware. Hardware faults Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 311 Summary of SNMP trap configuration commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level command Command...
  • Page 312 Summary of SNMP access configuration commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description ip snmp...

  • Page 313: Dynamic Trap Manager

    Dynamic trap manager is a special feature that ensures that the Branch Gateway sends traps directly to the currently active MGC. If the MGC fails, dynamic trap manager ensures that traps are sent to the backup MGC. Administering Avaya G430 Branch Gateway October 2013...
  • Page 314 310. Summary of dynamic trap manager configuration commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description...

  • Page 315: Snmp Configuration Examples

    Gxxx-001(super)# set snmp community read-write write SNMP read-write community string set. The following example enables link up/down trap on a LAN port on the G250: G250-001(super)# set port trap 10/3 enable Port 10/3 up/down trap enabled Administering Avaya G430 Branch Gateway October 2013...
  • Page 316 Port 10/4 up/down trap disabled The following example disables Link Up and Link Down traps on a LAN port on the Branch Gateway: Gxxx-001(super)# set port trap 10/5 disable Port 10/5 up/down trap disabled Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 317: Chapter 14: Contact Closure

    ™ It is recommended that you use an Avaya Partner Contact Closure Adjunct for contact closure. For more information, see Overview for the Avaya Branch Gateway G430. An Avaya ™ Partner Contact Closure Adjunct contains two relays, one for each electrical device. You can control each relay in any of the following ways: •...

  • Page 318: Configuring Contact Closure Hardware

    Contact Closure port on the Branch Gateway front panel, labeled CCA. Use a telephone cable with standard RJ-11 connectors. A qualified electrician should connect the electrical devices to the relays on the Avaya ™ Partner Contact Closure Adjunct For information on contact closure specifications, see Overview for the Avaya Branch Gateway G430.
  • Page 319 Procedure Use the set contact-closure admin command with the parameter manual- trigger. In the following example, the command activates contact closure in relay 1 of the Avaya ™ Partner Contact Closure Adjunct . Contact closure remains active until you deactivate it by using the set contact-closure admin command with the parameter manual-off or mgc.
  • Page 320 Contact closure The following example displays the contact closure status of relay 1 of the Avaya ™ Partner Contact Closure Adjunct box. Gxxx-001(super)# show contact-closure MODULE PORT RELAY ADMIN PULSE DURATION (secs) STATUS ------- ----- ------ ---------------- --------------------- ------ 5 secs...

  • Page 321: Chapter 15: Announcement Files

    For information about installing and using a compact flash and increased RAM, refer to Job Aid: Installing the upgrade memory kit in the G450 / G430 Branch Gateway . Avaya Voice Announcement Manager (VAM) can be used to centrally manage announcement files for multiple voice systems, including Branch Gateways.
  • Page 322 Specify the file name of the announcement file in the Branch Gateway announcement directory, followed by the IP address of the remote FTP server, and, optionally, a destination file name, including the full path. Example Gxxx-001(super)# copy announcement-file ftp local_announcement2.wav 192.168.49.10 remote_announcement2.wav Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 323 Gateway announcement directory, using the copy usb announcement-file command. Specify the name of the USB device, followed by the file name of the announcement file on the USB device, and, optionally, a destination file name, including the full path. Administering Avaya G430 Branch Gateway October 2013...
  • Page 324 Display the announcements files stored in the Branch Gateway announcement directory, using the show announcements-files command. Optionally add the keyword brief to display less detail. For example: Gxxx-001(super)# show announcements files Mode: FTP-SERVER/SCP-CLIENT Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 325 For example: Gxxx-001(super)# show upload announcement-file status Module #9 =========== Module Source file : hellosource.wav Destination file : d:\hellodestination.wav Host : 135.64.102.64 Running state : Idle Failure display : (null) Administering Avaya G430 Branch Gateway October 2013...
  • Page 326 =========== Summary of announcement files commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description copy announcement-file ftp...

  • Page 327: Chapter 16: Advanced Switching

    Gateway VLAN table on page 329 Ingress VLAN Security on page 330 ICC-VLAN on page 330 Configuring ICC-VLAN on page 330 VLAN configuration examples on page 331 Summary of VLAN commands on page 332 Administering Avaya G430 Branch Gateway October 2013...
  • Page 328 Bound to Configured: The port supports all the VLANs configured in the switch Statically Bound: The port supports VLANs manually configured on the port The figure on page 329 shows these binding modes. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 329 If this occurs, use the clear vlan command, followed by the name or number of the VLAN you want to delete, to free space in the VLAN table. Any new VLANs configured by you are made known to all the modules in the system. Administering Avaya G430 Branch Gateway October 2013...
  • Page 330 1. Enter the VLAN interface context by using the interface vlan CLI command 2. Enter icc-vlan. Example The following example sets Vlan 2 as the ICC-VLAN: Gxxx-001(super)# interface vlan 2 Gxxx-001(super-if:Vlan 2)# icc-vlan Done! Gxxx-001(super-if:Vlan 2)# exit Gxxx-001(super)# show icc-vlan VLAN 2 Gxxx-001(super)# Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 331 The following example displays a list of the MAC addresses in the CAM of a VLAN: Gxxx-001(super)# show cam vlan 54 Total Matching CAM Entries Displayed = 3 Dest MAC/Route Dest VLAN Destination Ports ------------------- ---- ----------------- Administering Avaya G430 Branch Gateway October 2013...
  • Page 332 VLAN ID VLAN-name ------- -------------------------------- Marketing 2121 Training Total number of VLANs: 4 Summary of VLAN commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 333: Port Redundancy

    Advanced switching For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level command First level Description Command clear port Delete statically configured VLANs from the port static-vlan clear vlan Delete an existing VLAN and its interface, remove...
  • Page 334 If you set this to none, there is no switchback to the primary port when it recovers. In this case, switchback to the primary port only takes place if the secondary port fails. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 335 To configure the two time constants that determine redundancy switchover parameters, use the set port redundancy-intervals command. Displaying port redundancy schemes Procedure To display information about software port redundancy schemes defined for the switch, enter show port redundancy. Administering Avaya G430 Branch Gateway October 2013...
  • Page 336 Switchback interval: 30 Summary of port redundancy commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description...

  • Page 337: Port Mirroring

    338 Port mirroring configuration examples The following example creates a port mirroring pair in the Branch Gateway: G430-001(super)# set port mirror source-port 10/3 mirror-port 10/4 sampling always direction rx Mirroring rx packets from port 10/3 to port 10/4 is enabled...

  • Page 338: Spanning Tree

    Advanced switching Summary of port mirroring commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description clear port mirror...
  • Page 339 Root Bridge (and back) to be changed. • Origination of BPDUs on a port-by-port basis Related topics: Port roles on page 340 RSTP port types on page 340 Administering Avaya G430 Branch Gateway October 2013...
  • Page 340 Ethernet link. RSTP convergence may be faster when switches are connected using point-to-point links. The default setting for all ports – automatic detection of point-to-point link – is sufficient for most networks. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 341 16. The following example configures the time interval between the generation of configuration BPDUs by the root: Gxxx-001(super)# set spantree hello-time 2 bridge hello time is set to 2. Administering Avaya G430 Branch Gateway October 2013...
  • Page 342 10/4 not-connected 4 Summary of spanning tree commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description...

  • Page 343: Port Classification

    With the Branch Gateway, you can classify any port as either regular or valuable. Classifying a port as valuable means that a link fault trap is sent in the event of a link failure. The trap is Administering Avaya G430 Branch Gateway October 2013...
  • Page 344 Summary of port classification commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description set port...

  • Page 345: Chapter 17: Monitoring Applications

    RMON's advanced remote networking capabilities provide the tools needed to monitor and analyze the behavior of segments on a network. In conjunction with an RMON agent, RMON gathers details and logical information about network status, performance, and users running applications on the network. Administering Avaya G430 Branch Gateway October 2013...
  • Page 346 Monitors the port 10/3 every 20 seconds Requested # of time intervals, ie buckets, is 60 Granted # of time intervals, ie buckets, is 60 Sample # 2 began measuring at 0:21:16 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 347 256-511:137, 512-1023:156, 1024-1518:0, Summary of RMON commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description clear rmon...

  • Page 348: Rtp Statistics

    IPv6 addresses. Note: An alternative tool available from Avaya for debugging QoS problems is VMON. VMON is an RTCP QoS reports collector. VMON support, available in all Avaya devices, is the capability of a VoIP device to send a copy of an RTCP message to the IP address of a VMON server.
  • Page 349 355 QoS fault and clear traps on page 357 The trap rate limiter on page 357 Related topics: Viewing RTP statistics thresholds on page 350 RTP statistics thresholds on page 352 Administering Avaya G430 Branch Gateway October 2013...
  • Page 350 Avaya Aura Communication Manager, where it is called “RTCP Report Period”. The RTCP interval is typically 5 to 8 seconds. For information about configuring the ® RTCP interval (RTCP report period), see Administrator Guide for Avaya Aura Communication Manager. Related topics:...
  • Page 351 5 to 8 seconds. The VoIP engine postpones loss estimation until the next interval if the number of packets received is less than the minimum statistic window. The minimum statistic window is configured with Administering Avaya G430 Branch Gateway October 2013...
  • Page 352 Jitter, Remote Jitter, and rtt metrics may help you identify causes when Codec RTT exceeds its threshold. Related topics: Configuring RTP statistics thresholds on page 352 Configuring RTP statistics thresholds Procedure 1. Use the rtp-stat thresholds command to set thresholds on QoS indicators. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 353 Enabling the RTP statistics application Procedure Enter rtp-stat-service. Note: Admin level access is required in order to use the rtp-stat-service command. For example: Gxxx-001# rtp-stat-service The RTP statistics service is enabled (default: disabled) Administering Avaya G430 Branch Gateway October 2013...
  • Page 354 QoS Trap QoS trap status. Possible values: • Enabled. The RTP statistics application is configured to generate QoS traps. • Disabled. The RTP statistics application is not configured to generate QoS traps. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 355 For example, if the event threshold for packet loss is 2, the application generates a trap at the termination of any session in which packet-loss was sampled over its threshold twice or more during the session. Administering Avaya G430 Branch Gateway October 2013...
  • Page 356 For more information about the dynamic trap manager, see Dynamic trap manager on page 313. 4. Enter rtp-stat qos-trap to enable the traps, if not already enabled. For example: Gxxx-001# rtp-stat qos-trap The RTP statistics QoS trap is enabled Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 357 Note: QoS fault traps appear in the Network Management Console Event Log Browser, indicating to the user that there are QoS problems in a specific network device. See the Avaya Network Management Console User Guide . Configuring QoS fault and clear traps Procedure Use the rtp-stat fault command.
  • Page 358 Gxxx-001(super)# show rtp-stat summary Total QoS traps: 23 QoS traps Drop : 0 Qos Fault Engine Active Total Mean Description Uptime Session Session Duration -------------- ----------- ------- ------- -------- ---- internal 04,18:15:15 35/24 01:04:44 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 359 RTP packets Viewing RTP session statistics About this task Using the CLI, you can view a summary of active and terminated sessions and you can view RTP statistics for a given RTP session. Administering Avaya G430 Branch Gateway October 2013...
  • Page 360 Samples: 54 (5 sec) Codec: G723 30mS , Silence-suppression(Tx/Rx) Disabled /Not-Supported Play-Time 272.610sec , Loss 0.0% , Avg-Loss 0.1% , RTT 741mS Avg-RTT 570mS , JBuf-under/overruns 0.1% /0.0% , Jbuf-Delay 22mS Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 361 The following table describes the fields in the show rtp-stat detailed command output according to the numbered labels in the example. Field Label Description From the CLI example Session-ID An arbitrary index number for the Session-ID: 35 session in the session table Administering Avaya G430 Branch Gateway October 2013...
  • Page 362 Multiple sessions belonging to the same conference call can usually be identified by a common conference Notes: • Phone data is received from Avaya ® Aura Communication Manager only if VMON is configured.
  • Page 363 Codec loss is the percentage of time the codec played fill frames due to lack of valid RTP frames. Possible causes include jitter and packet loss. #codec-loss- The codec loss event counter Loss 0.0% #1 events Administering Avaya G430 Branch Gateway October 2013...
  • Page 364 The network RTT event counter RTT 604mS #38 Avg-RTT The average of all network RTT values Avg-RTT 376mS during the session Jitter The network jitter at the RTP Jitter 0mS jitter ms receiver. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 365 DSCP The DSCP of RTP packets DSCP 184 L2Pri The Layer 2 priority of transmitted RTP L2Pri 6 packets (usually 802.1p) RTCP The total number of transmitted RTCP RTCP 62 packets Remote-Statistics: Administering Avaya G430 Branch Gateway October 2013...
  • Page 366 SNMP Trap manager on the MGC. The syslog messages are stored in the messages file on the MGC hard disk. You can view the syslog messages through the Avaya Maintenance Web Interface to debug the QoS problems.
  • Page 367 Monitoring applications Procedure 1. In the Avaya Maintenance Web Interface, enter the Setup log viewing screen. 2. In the Select Log Types list, select Linux syslog. 3. Under Select Event Range, select the date range over which you want to view traps.
  • Page 368 The local extension number and conference ID in avRtpSessionPhone.0 = format <conference ID>:<extension number>. STRING: 69:2011 Conference calls can involve more than one entry in the session table. Multiple sessions belonging Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 369 Description From the trap example to the same conference call can usually be identified by a common conference ID. Notes: • The phone string data is received from Avaya ® Aura Communication Manager if VMON is configured. • If you are not running VMON, you can cause ®...
  • Page 370 RTP session 35, which terminated at 11:13:40 on October 20: Oct 20 11:10:54 LZ-SIT-SR1 snmptrapd[9407]: 135.8.118.252 [135.8.118.252]: TrapsysUpTime.0 = Timeticks: (43131114) 4 days, 23:48:31.14 , snmpTrapOID.0 = OID: avRtpQoSFault , avRtpQoSFaultTh.0 = INTEGER: 1 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 371 QoS clear trap to be sent after a QoS fault trap was sent. Viewing automatic traceroute results About this task The VoIP engine automatically performs UDP traceroutes whenever the RTP statistics application is enabled. Administering Avaya G430 Branch Gateway October 2013...
  • Page 372 HOP ADDRESS The hop IP address DELAY The round trip time per probe packet. Three probe packets are sent per hop address, and the displayed value is the average of the Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 373 //to view the configuration of the application: Gxxx-001(super)# show rtp-stat config RTP Statistic: Enabled QoS Trap: Disabled QoS Fault Trap: Disabled Fault: 0 Clear: 0 QoS Trap Rate Limiter: Token Interval: 10.00 seconds Bucket Size: 5 Administering Avaya G430 Branch Gateway October 2013...
  • Page 374 //to configure an external trap manager as a trap destination in addition to the active MGC: Gxxx-001(super)# snmp-server host 136.9.71.47 traps v1 public //to check SNMP configuration Gxxx-001(super)# show snmp Authentication trap enabled Community-Access Community-String ---------------- ---------------- Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 375 A remote call from analog to IP telephone At 00:39 on December 7, 2004, a call is placed from analog extension 2111 to IP phone extension 2002 in the network described in Four telephones in a sample network page 373. Administering Avaya G430 Branch Gateway October 2013...
  • Page 376 - The received-RTP packet loss event counter indicates that packet loss went over its threshold nine times [4] - The remote packet loss event counter indicates that remote packet loss went over its threshold 14 times [5] Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 377 , Avg-RTT 0mS , Jitter 0mS , Avg-Jitter 0mS , TTL(last/min/max) 64/64/64, Duplicates 0, Seq-Fall 0, DSCP 46, L2Pri 12, RTCP 26 Transmitted-RTP: VLAN 1, DSCP 46, L2Pri 6, RTCP 31 Remote-Statistics: Loss 0.0% #0 Administering Avaya G430 Branch Gateway October 2013...
  • Page 378 //to display the RTP sessions: Gxxx-001 (super)# show rtp sessions QoS Start date and time End Time Type Destination ----- --- ------------------- -------- ------------- -------------- 00011 2004-12-07,00:57:13 00:59:19 G711U 30.30.30.2 00012 2004-12-07,00:39:26 00:41:01 G711U 20.20.20.2 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 379 , L2Pri 12, RTCP 31 Transmitted-RTP: VLAN 1, DSCP 46, L2Pri 6, RTCP 25 --type q to quit or space key to continue-- Remote-Statistics: Loss 0.0% #0, Avg-Loss 0.0%, Jitter 7mS #0, Avg-Jitter 7mS Echo-Cancellation: Administering Avaya G430 Branch Gateway October 2013...
  • Page 380 Received-RTP: Packets 238, Loss 0.0% #0, Avg-Loss 0.0%, RTT 24mS #0, Avg-RTT 21mS, Jitter 0mS #0, Avg-Jitter 0mS, TTL(last/min/max) 0/61/61, Duplicates 0, Seq-Fall 0, DSCP 0, L2Pri 6, RTCP 26 Transmitted-RTP: Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 381 [1] [2]. Summary of RTP statistics commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description...

  • Page 382: Packet Sniffing

    The Branch Gateway’s packet sniffing service gives you full control over the memory usage of the sniffer. You can set a maximum limit for the capture buffer size, configure a circular buffer Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 383 The following streams can never be captured because they are switched by the internal Ethernet switch and not by the CPU: • H.323 Signaling from an IP phone on the LAN to an ICC on the LAN • RTP stream between IP phones on the LAN Administering Avaya G430 Branch Gateway October 2013...
  • Page 384 Since the packet sniffing service presents a potential security breach, the administrator must first enable the service on the Branch Gateway before a user can start capturing packets. Procedure 1. Enter capture-service to enable the packet sniffing service. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 385 You can set the default action as desired. Use the command ip-rule default to set the default action. Note: ARP frames are not IP packets and therefore cannot be filtered by capture lists. However, in a healthy network, the ARP frames rate is relatively low. Administering Avaya G430 Branch Gateway October 2013...
  • Page 386 The composite operation determines the action the rule takes with respect to packets that match the rule criteria, and can be one of the following: • capture • no-capture Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 387 L4 sessions may be blocked by the other L4 session which is blocked. • L3 rules apply to non-initial fragments • L3 rules that include the fragment criteria do not apply to initial fragments or non-fragment packets Administering Avaya G430 Branch Gateway October 2013...
  • Page 388 For example, the following rule is defined to capture all VoIP Bearer packets (DSCP = 46): Gxxx-001(super)# ip capture-list 520 Gxxx-001(super-Capture 520)# ip-rule 20 Gxxx-001(super-Capture 520/ip rule 20)# composite-operation capture Done! Gxxx-001(super-Capture 520/ip rule 20)# dscp 46 Done! Gxxx-001(super-Capture 520/ip rule 20)# Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 389 Single address: Type host, by an IP address, to set a single IP address to which the rule applies. For example: Gxxx-001(super-Capture 520/ip rule 20)# destination-ip host 135.64.104.102 Done! Gxxx-001(super-Capture 520/ip rule 20)# Administering Avaya G430 Branch Gateway October 2013...
  • Page 390 • udp destination-port. The rule applies to UDP packets to ports that match the defined criteria For information about parameters and default settings, see Avaya Branch Gateway G430 CLI Reference. Port name or number range criteria The port name or number range criteria can be any of the following: Range: Type range, followed by two port numbers, to set a range of port numbers to which the rule applies.
  • Page 391 Gxxx-001(super-Capture 520/ip rule 20)# Fragment command To apply the rule to non-initial fragments, enter fragment. You cannot use the fragment command in a rule that includes UDP or TCP source or destination ports. Administering Avaya G430 Branch Gateway October 2013...
  • Page 392 Done! Gxxx-001(super-Capture 511/ip rule default)# exit Gxxx-001(super-Capture 511)# exit Gxxx-001(super)# Viewing the capture list Procedure Use the show ip capture-list command to display the capture list in an easy-to- read format. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 393 Use the following commands to configure packet sniffing settings. These commands are all used from general context, and require read/write access. Procedure 1. Use the capture buffer-mode command to specify the type of buffer to use. The available parameters are: Administering Avaya G430 Branch Gateway October 2013...
  • Page 394 • Use the capture max-frame-size to capture only the first N octets of each frame. This is valuable since it is usually the packets headers that contain the interesting information. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 395 IPSec VPN packets are encrypted packets. The contents of encrypted packets cannot be viewed when captured. However, you can use the capture ipsec command to specify that IPSec VPN packets, handled by the internal VPN Branch Gateway process, should be captured in plain text format. Administering Avaya G430 Branch Gateway October 2013...
  • Page 396 Size of capture file: 266 KB (26.6 %) Note: The number of captured frames can be larger than the number of the frames in the buffer because the capture file may be in cyclic mode. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 397 Ethereal. Related topics: Uploading the capture file to a remote server or USB mass storage device on page 398 Uploading the capture file to an S8300 Server on page 398 Administering Avaya G430 Branch Gateway October 2013...
  • Page 398 2. Open the Avaya Maintenance Web Interface. For instructions on accessing the Avaya Maintenance Web Interface, see Installing and Upgrading the Avaya Branch Gateway G430. 3. In the Avaya Maintenance Web Interface, select FTP under Security in the main menu. 4. Click Start Server .
  • Page 399 Ethereal starts with 00:00, this indicates the packet is a non-Ethernet packet. The dummy Ethernet header is identified by special MAC addresses. Packets sent from a non- Ethernet interface are identified with an SA address in the format 00:01:00:00:xx and a DA Administering Avaya G430 Branch Gateway October 2013...
  • Page 400 580. Summary of packet sniffing commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level First level...
  • Page 401 Set a number to identify a list (used by the rule-manager application) ip-rule Enter an ip-rule context or erase an ip-rule Create or edit a composite operation Administering Avaya G430 Branch Gateway October 2013...
  • Page 402 Show the sniffer status show Show a hex-dump of the captured frames capture- buffer hex show ip Show capture list(s) capture-list show upload View capture file upload status status Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 403: Interface Status Reports

    Down is down (no keepalive) Down FastEthernet 10/3 Down FaultDown is up, line protocol is down Standby FastEthernet 10/3 Dormant DormantDown is in standby mode, line protocol is down Administering Avaya G430 Branch Gateway October 2013...

  • Page 404: Cna Test Plugs

    For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Summary of interface status commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference.
  • Page 405 UDP messages, each with a Time To Live (TTL) value that is one greater than that of the preceding message. Real Time Protocol (RTP): Measures delay, packet loss, and jitter to another test plug by sending a simulated RTP stream that is echoed back. Administering Avaya G430 Branch Gateway October 2013...
  • Page 406 You can configure up to five scheduler addresses. The test plug attempts to register with a scheduler according to its place on the list. By default, no schedulers are configured. At least one scheduler must be configured for registration to be possible. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 407 The following example includes displaying default test plug configuration, configuring the test plug, enabling the test plug service, and displaying test plug configuration and counters. //to display default test plug configuration before performing any //configuration: show cna testplug Gxxx-001(super)# Administering Avaya G430 Branch Gateway October 2013...
  • Page 408 //to exit the test plug context: exit Gxxx-001(super-cna testplug 1)# //to show that scheduler 1 is no longer configured: show cna testplug Gxxx-001(super)# CNA testplug 1 is administratively down, test-plug status is unregistered Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 409 Gxxx-001(cna-testplug 1)# clear counters All CNA test plug counters are cleared. Summary of CNA test plug commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. Administering Avaya G430 Branch Gateway October 2013...

  • Page 410: Echo Cancellation

    Monitoring applications For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level command Command Description cna testplug Enter the CNA testplug configuration context clear Clear the CNA test plug counters counters control-port Set or reset the UDP port on which the CNA...
  • Page 411 411 Summary of echo cancellation commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description...

  • Page 412: Integrated Analog Testing - Test And Heal

    Related topics: Hardware support for integrated analog testing on page 413 Types of tests on page 413 Types of test lines on page 414 Setting up a test profile on page 414 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 413 Each entry in the group balances the hybrid against a different loop impedance. The match test executes a balance test for each set of coefficients and determines which set best matches the loop. Administering Avaya G430 Branch Gateway October 2013...
  • Page 414 3. In the analog-test-profile context, setup the test profile: • Use the set type command to specify what type of test to run, that is, what type of measurements to run. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 415 Remember to start the call before launching the test. • Use the set crosstalk-responder command to specify the responder port for the crosstalk port. Administering Avaya G430 Branch Gateway October 2013...
  • Page 416 As soon as launch is issued, the results of previous measurements on the port are cleared. You can use the cancel command to abort an analog test that is currently running. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 417 • Use the set transmit-gain command to set the transmit-gain on a specific port. Displaying corrections About this task After correcting the balance, receive-gain or transmit-gain, you can view the corrections applied to each port. Administering Avaya G430 Branch Gateway October 2013...
  • Page 418 Summary of integrated analog testing commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root Level First level...

  • Page 419: Service Level Agreement Monitor Agent

    It employs the use of a web-based server application to communicate with agents embedded in the components of IP telephony as well as other sources to reveal how the network contributes to the performance of audio and video applications. Administering Avaya G430 Branch Gateway October 2013...
  • Page 420 Enables or disables the SLA Monitor Agent. monitor set sla- Defines the degree of data captured by the SLA capturemode Monitor Agent. By default, the capture mode is set to “without-payload”. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 421: Chapter 18: The Router

    429 for an explanation of the priority considerations employed by the Branch Gateway to determine the next hop source. Related topics: Enabling and disabling the router on page 422 Interface configuration on page 422 Unnumbered IP interfaces on page 426 Administering Avaya G430 Branch Gateway October 2013...

  • Page 422: Enabling And Disabling The Router

    You can use the CLI to configure interfaces on the router. Related topics: Router interface concepts on page 423 Configuring an IP interface on page 424 Interface configuration examples on page 424 Summary of basic interface configuration commands on page 425 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 423 GRE tunnel. At the end of the GRE tunnel, the encapsulation is removed and the packet is sent to its destination in the network at the far end of the GRE tunnel. For more information, GRE tunneling on page 434. Administering Avaya G430 Branch Gateway October 2013...
  • Page 424 Use the following commands to create VLAN 2 on the switching interface and configure it with IP address 10.30.50.70 and subnet mask 255.255.0.0: Gxxx-001# interface Vlan 2 Gxxx-001(if:Vlan 2)# ip address 10.30.50.70 255.255.0.0 Done! Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 425 The router Summary of basic interface configuration commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level Command...

  • Page 426: Unnumbered Ip Interfaces

    Unnumbered IP on an interface configuration on page 427 Configuring IP on an interface configuration on page 427 Unnumbered IP examples on page 427 Summary of unnumbered IP interface configuration commands on page 428 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 427 Gxxx-001(super)# interface dialer 1 Gxxx-001(super-if:Dialer 1)# dialer string 1 3001 Gxxx-001(super-if:Dialer 1)# dialer persistent delay 1 Gxxx-001(super-if:Dialer 1)# dialer modem-interface USB-modem //to configure IP unnumbered on the Dialer interface, borrowing the IP address from Administering Avaya G430 Branch Gateway October 2013...
  • Page 428 Summary of unnumbered IP interface configuration commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level Command...

  • Page 429: Routing Sources

    RIP are enabled, and DHCP client is configured on the interface with a default router requested from the DHCP server (DHCP option 3), then the default router provided by DHCP is used. 6. Low priority static route (lowest) Administering Avaya G430 Branch Gateway October 2013...

  • Page 430: Routing Table Configuration

    472. Static routes also support load-balancing similar to OSPF. Related topics: Next hops on page 431 Static route types on page 431 Configuring multiple next hops on page 431 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 431 • Enter each next hop individually with its own ip route command Note: If you apply tracking to a static route, you can only configure one next hop for the route. Administering Avaya G430 Branch Gateway October 2013...
  • Page 432 Permanent static routes should not be configured over Layer 2 interfaces that participate in a Primary-Backup pair. For more information on Backup interfaces, see Backup interfaces on page 256. Note: You cannot configure tracking on a permanent static route. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 433 134.66.0.0 16 as a discard route Summary of routing table commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description...

  • Page 434: Gre Tunneling

    GRE tunnels can be configured as next hops on static routes and policy-based routing next hop lists. Packets can also be routed to GRE tunnels dynamically. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 435 • The packet is routed to the Tunnel interface dynamically by a routing protocol (RIP or OSPF) • The packet is routed to the Tunnel interface via policy-based routing. See Policy-based routing on page 587. Administering Avaya G430 Branch Gateway October 2013...
  • Page 436 Using the network shown in Nested tunneling example on page 437 as an illustration, if Router 1 has an entry in its routing table regarding the tunnel’s receiving endpoint, this will cause an Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 437 Gxxx-001(super)# ip distribution access-list-name 1 “list #1” Done! Gxxx-001(super)# ip distribution access-default-action 1 default-action-permit Done! Gxxx-001(super)# ip distribution access-list 1 10 “deny” 192.68.1.0 0.0.0.255 Done! Gxxx-001(super)# router rip Gxxx-001(super router:rip)# distribution-list 1 in FastEthernet 10/3 Done! Administering Avaya G430 Branch Gateway October 2013...
  • Page 438 Use the no form of this command to deactivate the feature. Example The following example configures Tunnel 1 to send keepalive packets every 20 seconds. If the tunnel’s destination interface fails to respond to three consecutive packets, the tunnel’s source Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 439 The tunnel path-mtu-discovery command includes the following parameters: age-timer: How long until the local tunnel endpoint returns the tunnel MTU to its default. The default value of this parameter is 10 minutes. Administering Avaya G430 Branch Gateway October 2013...
  • Page 440 (in seconds) of the interval at which the source interface sends keepalive packets, and the number of retries necessary in order to declare the tunnel down. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 441 438. For a list of additional GRE tunnel CLI commands, refer to Summary of GRE tunneling commands on page 443. GRE tunnel application example This section provides an example of a GRE tunnel application and its configuration. Administering Avaya G430 Branch Gateway October 2013...
  • Page 442 Gxxx-001(super-if:Tunnel 1)# tunnel destination 12.0.0.20 Done! Gxxx-001(super-if:Tunnel 1)# ip address 1.1.1.1 255.255.255.0 Done! Gxxx-001(super-if:Tunnel 1)# exit Gxxx-001(super)# ip route 12.0.0.0 255.255.255.0 11.0.0.1 1 high Gxxx-001(super)# router ospf Gxxx-001(super router:ospf)# network 1.1.1.0 0.0.0.255 area 0.0.0.0 Done! Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 443 Gxxx-001(super)# Summary of GRE tunneling commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level Command Description...

  • Page 444: Dhcp And Bootp Relay

    For information about configuring DHCP server on the Branch Gateway, see DHCP server on page 447. For information about configuring DHCP client on the Branch Gateway, see DHCP client configuration on page 204. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 445 The relay agent handles the DHCP/BOOTP replies as well. The relay agent transmits the replies to the client directly or as broadcast, according to a flag in the reply message. Administering Avaya G430 Branch Gateway October 2013...
  • Page 446 Summary of DHCP and BOOTP relay commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level Command...

  • Page 447: Dhcp Server

    DHCP server mode or DHCP relay mode. For example, you can configure the Branch Gateway to provide DHCP service to voice devices while DHCP requests by data devices are routed to a central remote DHCP server using DHCP relay. Administering Avaya G430 Branch Gateway October 2013...
  • Page 448 Reservation pools may be required for security issues or servers. Overlap between pools is not allowed. You cannot configure a reservation pool on an IP address that falls within the range of another pool. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 449 8. Repeat steps 1 to 7 to configure as many DHCP pools as you require. You can configure up to 32 DHCP pools. By default, all pools are inactive until you activate them. This enables you to modify each pool’s configuration without affecting network devices. Administering Avaya G430 Branch Gateway October 2013...
  • Page 450 2. Use the name command to set the name of the DHCP option (optional). 3. Use the value command to enter the option data type and the option data. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 451 When the DHCP server detects an IP address conflict after attempting to allocate an IP address that is already in use, the server locks the IP address for half an hour by marking the IP address Administering Avaya G430 Branch Gateway October 2013...
  • Page 452 Done! Gxxx-001(super-DHCP 1)# subnet-mask 255.255.255.0 Done! Gxxx-001(super-DHCP 1)# default-router 135.64.20.1 Done! Gxxx-001(super-DHCP 1)# option 176 Gxxx-001(super-DHCP 1/option 176)# name “Avaya IP phone option” Done! Gxxx-001(super-DHCP 1/option 176)# value ascii “MCIPADD=10.10.2.140, MCPORT=1719, TFTPSRVR=10.10.5.188” Done! Gxxx-001(super-DHCP 1/option 176)# exit Gxxx-001(super-DHCP 1)# exit...
  • Page 453 • show ip dhcp-pool • show ip dhcp-server bindings • show ip dhcp-server statistics For more information about these commands, see Summary of DHCP Server commands page 454 or the Avaya Branch Gateway G430 CLI Reference. Administering Avaya G430 Branch Gateway October 2013...
  • Page 454 The router Summary of DHCP Server commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level First level...
  • Page 455 Name the vendor-specific option class- Set a vendor-specific identifier identifier value Set the data type and value of the vendor-specific option ip dhcp- Activate DHCP server server Administering Avaya G430 Branch Gateway October 2013...

  • Page 456: Broadcast Relay

    Procedure Enter ip directed-broadcast to enable directed broadcast forwarding on an interface. Use the no form of this command to disable directed broadcast forwarding on an interface. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 457 IP address remains the limited broadcast address. Summary of broadcast relay commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level Command...

  • Page 458: Arp Table

    MAC addresses that the switch used recently. Dynamic ARP table entries expire after a configurable amount of time. The following diagram shows how a switch adds dynamic ARP table entries: Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 459 The router Adding static ARP table entries Procedure To add static ARP table entries manually, use the arp command. Administering Avaya G430 Branch Gateway October 2013...
  • Page 460 Summary of ARP table commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description Add a permanent entry to the ARP table...

  • Page 461: Proxy Arp

    461 Summary of Proxy ARP commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level Command...

  • Page 462: Rip

    462 Summary of ICMP errors commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description...
  • Page 463 Timer-based – updated every 30 seconds Timer-based – updated every 30 seconds Fixed subnetwork masks VLSM support – subnet information transmitted No security Security (authentication) No provision for external protocols Provision for EGP/BGP (Route tag) Administering Avaya G430 Branch Gateway October 2013...
  • Page 464 You can assign the rules per interface and per direction. You can configure up to 99 RIP distribution access lists on the Branch Gateway. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 465 However, you can configure different IP interfaces of the Branch Gateway with different RIP versions. This configuration is valid as long as all routers on the subnet are configured with the same version. Administering Avaya G430 Branch Gateway October 2013...
  • Page 466 OSPF and static route preferences. Summary of RIP commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level command Command...
  • Page 467 RIP route metric default value. metric distribution- Apply a distribution access list for incoming or outgoing routing list information in route updates or deactivate the list Administering Avaya G430 Branch Gateway October 2013...

  • Page 468: Ospf

    This calculation is based on a topography of the network constructed by each node. Each router sends that portion of the routing table that Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 469 The Branch Gateway supports the ECMP equal-cost multipath (ECMP) feature which allows load balancing by splitting traffic between several equivalent paths. While you can activate OSPF with default values for each interface using a single command, you can configure many of the OSPF parameters. Administering Avaya G430 Branch Gateway October 2013...
  • Page 470 The router Summary of OSPF commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level command Command...
  • Page 471 Used to allow interfaces to be flooded into the OSPF domain as OSPF routes rather than external routes. Note: Use the network command with this command to make the network passive. Administering Avaya G430 Branch Gateway October 2013...

  • Page 472: Route Redistribution

    • OSPF external type 1 metric N to RIP metric (default 1) • OSPF external type 2 metric N to RIP metric (default 1) • Static to OSPF external type 2, metric configurable (default 20) Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 473 Summary of route redistribution commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level Command...

  • Page 474: Vrrp

    You can activate VRRP on an interface using a single command while allowing for the necessary fine-tuning of the many VRRP parameters. For a detailed description of VRRP, see VRRP standards and published literature. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 475 - It has the highest priority (you can configure this parameter) - It has the highest IP address if the previous conditions do not apply • The virtual router IP address needs to be configured as the default gateway on the stations Administering Avaya G430 Branch Gateway October 2013...
  • Page 476 You must perform this manually, if needed. Summary of VRRP commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level Command...

  • Page 477: Fragmentation

    IP fragmentation works as follows: • Each IP packet is divided into fragments • Each fragment becomes its own IP packet • Each packet has same identifier, source, and destination address Administering Avaya G430 Branch Gateway October 2013...
  • Page 478 478 Summary of fragmentation commands For more information about these commands, see the Avaya Branch Gateways G250 and G350 CLI Reference. For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Command Description clear...

  • Page 479: Chapter 19: Ipsec Vpn

    The Branch Gateway IPSec VPN feature is designed to support site-to-site topologies, in which the two peers are gateways. Note: To configure IPSec VPN, you need at least a basic knowledge of IPSec. Refer to the following guide for a suitable introduction: http://www.tcpipguide.com/free/t_IPSecurityIPSecProtocols.htm Administering Avaya G430 Branch Gateway October 2013...

  • Page 480: Overview Of Ipsec Vpn Configuration

    IPSec VPN Overview of IPSec VPN configuration IPSec VPN configuration model The following figure summarizes the components you need to define and the order in which you need to define them. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 481 IPSec VPN Table 5: Figure notes: 1. ISAKMP Policy 2. IPSEC Transform-set 3. ISAKMP Peer or Peer Group Administering Avaya G430 Branch Gateway October 2013...
  • Page 482 Each rule in the crypto list points to a crypto-map. A crypto-map points to a transform-set, and to a peer or peer-group. The peer or peer-group, in turn, point to an ISAKMP policy. IPSec VPN components The following figure describes the relationships among the various VPN components. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 483 You must configure VPN in the order shown in the summary. Commands appearing in bold are mandatory. • ISAKMP policy – crypto isakmp policy on page 486 - description - authentication pre-share - encryption - hash Administering Avaya G430 Branch Gateway October 2013...
  • Page 484 - set peer or set peer-group - set dscp - continuous-channel • IP crypto list – ip crypto-list on page 495 - local-address - ip-rule • description • source-ip • destination-ip • protect crypto map Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 485 ISAKMP policy, it is not mandatory to set the values for that ISAKMP policy since the Branch Gateway contains default ISAKMP policy settings. Related topics: VPN peer coordination on page 486 Configuring ISAKMP policies on page 486 Configuring transform-sets on page 488 Configuring ISAKMP peer information on page 489 Administering Avaya G430 Branch Gateway October 2013...
  • Page 486 Configuring ISAKMP policies About this task An ISAKMP policy defines the IKE phase 1 parameters. Note: You can configure up to 40 ISAKMP policies. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 487 Gxxx-001(config-isakmp:1)# authentication pre-share Done! Gxxx-001(config-isakmp:1)# encryption des Done! Gxxx-001(config-isakmp:1)# hash md5 Done! Gxxx-001(config-isakmp:1)# group 1 Done! Gxxx-001(config-isakmp:1)# lifetime 60000 Done! 3. Exit the ISAKMP policy context with the exit command. For example: Gxxx-001(config-isakmp:1)# exit Gxxx-001# Administering Avaya G430 Branch Gateway October 2013...
  • Page 488 • Use the set security-association lifetime seconds command to set the security association lifetime in seconds. • Use the set security-association lifetime kilobytes command to set the security association lifetime in kilobytes. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 489 If you want to specify the ISAKMP peer by its FQDN name, configure the Branch Gateway as a DNS client. and verify that the peer’s name is listed in a DNS server. DNS resolver on page 74. Administering Avaya G430 Branch Gateway October 2013...
  • Page 490 FQDN that translates to an IP address which is already associated with another ISAKMP peer. For example: Gxxx-001# crypto isakmp peer address 149.49.70.1 Gxxx-001(config-peer:149.49.70.1)# Gxxx-001# crypto isakmp peer fqdn vpn.lnd.ny.avaya.com Gxxx-001(config-peer:vpn.lnd.ny.avaya.com)# 2. Use the description command to enter a description for the peer. For example: Gxxx-001(config-peer:149.49.70.1)# description “New York office”...
  • Page 491 DPD keepalive fails. Gxxx-001(config-peer:149.49.70.1)# keepalive 10 retry 2 Done! 9. Bind peer status to an object tracker that can monitor hosts inside the remote peer’s protected network. Administering Avaya G430 Branch Gateway October 2013...
  • Page 492 Introduction to the failover mechanism on page 529. Note: You can define up to 50 peer-groups. Note: A peer configured as initiate mode none cannot be a member of a peer-group. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 493 If you defined a peer-group, the crypto map can point to the peer-group. The transform-set and ISAKMP policy define how to secure the traffic that matches the ip-rule that points to this crypto map. Important: It is mandatory to create at least one crypto map. Administering Avaya G430 Branch Gateway October 2013...
  • Page 494 0 to 63. The default setting is no set dscp that specifies that the DSCP is copied from the DS field of the original packet. For example: Gxxx-001(config-crypto:1)# set dscp 38 Done! Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 495 2. Specify the local IP address for the IPSec tunnels derived from this crypto list, using the local-address command. The local address can be either the IP address or the name of an IP interface of the device. Important: local-address is a mandatory command. Administering Avaya G430 Branch Gateway October 2013...
  • Page 496 - no protect. Do not protect traffic that matches the source and destination addresses. - protect crypto map crypto-map-id. Protect traffic that matches the source and destination addresses. The specified crypto map specifies Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 497 • For rules whose action is no protect, you can fine-tune the definition of packets that match this rule by using the following commands. For a full description of the commands see Avaya CLI Reference. Note that this fine- tuning is not applicable for rules whose action is protect crypto map.
  • Page 498 For example: G430-001# interface fastethernet 10/2 G430-001(if:FastEthernet 10/2)# no ip crypto-group Done! 2. After modifying IPSec VPN parameters as desired, re-activate the crypto list on the interface using the ip crypto-group crypto-list-id command.
  • Page 499 Note: NAT Traversal is enabled by default. Configure NAT Traversal only if you need to re-enable it after it was disabled, using the no crypto ipsec nat-transparency udp- Administering Avaya G430 Branch Gateway October 2013...
  • Page 500 1. Enter interface context using the interface command. For example: Gxxx-001# interface fastethernet 10/3 Gxxx-001(config-if:FastEthernet 10/3)# 2. Configure the IP address of the interface. You can configure either a static or a dynamic IP address. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 501 For example: Gxxx-001(config-if:FastEthernet 10/3)# ip crypto-group 901 Done! Gxxx-001(config-if:FastEthernet 10/3)# crypto ipsec minimal pmtu 500 Done! Gxxx-001(config-if:FastEthernet 10/3)# crypto ipsec df-bit copy Done! 5. Exit the interface context with the exit command. Administering Avaya G430 Branch Gateway October 2013...
  • Page 502 • show ip active-lists For a description of these commands, see Summary of VPN commands on page 550 For a full description of the commands and their output fields, see Avaya Branch Gateway G430 CLI Reference. Administering Avaya G430 Branch Gateway October 2013...
  • Page 503 For a description of these commands, see Summary of VPN commands on page 550 . For a full description of the commands and their output fields, see Avaya Branch Gateway G430 CLI Reference. Clearing both ISAKMP connection and IPSec SAs Procedure 1.
  • Page 504 Included in the typical installations, are examples of installing VPN hub and spokes, full or partial mesh, and a hub-and-spoke with VPN for data and VoIP control backup. Related topics: Simple VPN topology – VPN hub and spokes on page 505 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 505 507 Dynamic local peer IP on page 509 Continuous channel on page 512 Enabling continuous channel on page 512 Configuring the simple VPN topology Procedure 1. Configure each branch as follows: Administering Avaya G430 Branch Gateway October 2013...
  • Page 506 VPN Policy, this will be any local subnet allowed only if traffic comes over ESP Ingress Default VPN policy Deny Egress Permit Egress Permit Egress ICMP Permit This enables the PMTUD application to work Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 507 Permit exit ip-rule 11 source-ip any destination-ip any ip-protocol udp destination-port eq Ike-nat-t composite-operation permit exit ip-rule 12 source-ip any destination-ip any ip-protocol udp destination-port eq Ike-nat-t-vsu composite-operation permit exit ip-rule 20 Administering Avaya G430 Branch Gateway October 2013...
  • Page 508 Permit exit ip-rule 30 source-ip any destination-ip any ip-protocol icmp composite-operation Permit exit ip-rule 40 desintation-ip any source-ip host <Branch Subnet1> <Branch Subnet1 Mask> composite-operation Permit exit ip-rule 50 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 509 Prerequisites for dynamic local peer IP on page 510 Configuring dynamic local peer IP on a PPPoE interface on page 510 Configuring dynamic local peer IP for a DHCP Client on page 511 Administering Avaya G430 Branch Gateway October 2013...
  • Page 510 Ethernet frames. You can configure PPPoE on the Branch Gateway’s ETH WAN Fast Ethernet port. For more information about PPPoE on the Branch Gateway, see Configuring PPPoE on page 252. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 511 Done! Gxxx-001(config-ACL 302/ip rule 25)# ip-protocol udp Done! Gxxx-001(config-ACL 302/ip rule 25)# udp source-port eq bootpc Done! Gxxx-001(config-ACL 302/ip rule 25)# udp destination-port eq bootps Done! Gxxx-001(config-ACL 302/ip rule 25)# composite-operation permit Done! Administering Avaya G430 Branch Gateway October 2013...
  • Page 512 You can set continuous channel for either or both IKE phase 1 and IKE phase 2, as follows: Procedure 1. To set continuous channel for IKE phase 1, enter continuous-channel when configuring the crypto ISAKMP peer information (see Configuring ISAKMP peer information on page 489). Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 513 • There is a VPN tunnel from each spoke to the VPN hub over the Internet • There is a VPN tunnel from one spoke to another spoke • Only VPN traffic is allowed via the Internet connection Administering Avaya G430 Branch Gateway October 2013...
  • Page 514 IPSec, with the remote peer being the second spoke - Traffic from the local subnets to any IP address -> encrypt, using tunnel mode IPSec, with the remote peer being the main office (VPN hub) Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 515 Description direction value Ingress IKE from Main Office IP to Permit Branch IP Ingress ESP from Main Office IP to Permit Branch IP Ingress IKE from Second Branch IP Permit to Branch IP Administering Avaya G430 Branch Gateway October 2013...
  • Page 516 Permit Branch IP Ingress ESP from First Branch IP to Permit Branch IP Ingress ICMP from any IP address to Permit This enables the PMTUD local tunnel endpoint application to work Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 517 1 set peer <Main Office Public Internet Static IP Address> set transform-set ts1 exit crypto map 2 set peer <Second Branch Office Public Internet Static IP Address> set transform-set ts1 Administering Avaya G430 Branch Gateway October 2013...
  • Page 518 Ike composite-operation Permit exit ip-rule 11 source-ip any destination-ip any ip-protocol udp destination-port eq Ike-nat-t composite-operation permit exit ip-rule 12 source-ip any destination-ip any ip-protocol Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 519 Ike-nat-t-vsu composite-operation permit exit ip-rule 20 source-ip any destination-ip any ip-protocol esp composite-operation Permit exit ip-rule 30 source-ip any destination-ip any ip-protocol icmp composite-operation Permit exit ip-rule 40 Administering Avaya G430 Branch Gateway October 2013...
  • Page 520 1 exit crypto ipsec transform-set ts1 esp-3des esp-sha-hmac set pfs 2 exit crypto map 1 set peer <Main Office Public Internet Static IP Address> set transform-set ts1 exit crypto map 2 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 521 Ike composite-operation Permit exit ip-rule 11 source-ip any destination-ip any ip-protocol udp destination-port eq Ike-nat-t composite-operation permit exit ip-rule 12 source-ip any destination-ip any Administering Avaya G430 Branch Gateway October 2013...
  • Page 522 Ike-nat-t-vsu composite-operation permit exit ip-rule 20 source-ip any destination-ip any ip-protocol esp composite-operation Permit exit ip-rule 30 source-ip any destination-ip any ip-protocol icmp composite-operation Permit Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 523 Main Office for VoIP bearer and as primary VoIP control connection. The layer 3 router is connected to the G430 through a dedicated VLAN interface. • The Broadband Internet connection uses cable or DSL modem, with a static public IP address •...
  • Page 524 For information about using access control lists, see Policy lists page 557. • Policy Based Routing (PBR) is configured as follows on VoIP VLAN and loopback interfaces: - Destination IP = local subnets > Route: DBR Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 525 Local GRE tunnel endpoint to remote GRE tunnel endpoint Permit Egress All allowed services from any local subnet to any IP address Permit Egress Allowed ICMP from local tunnel endpoint to any IP address Permit Administering Avaya G430 Branch Gateway October 2013...
  • Page 526 Ike-nat-t composite-operation permit exit ip-rule 12 source-ip any destination-ip any ip-protocol udp destination-port eq Ike-nat-t-vsu composite-operation permit exit ip-rule 20 source-ip any destination-ip any ip-protocol esp Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 527 Permit exit ip-rule 30 source-ip any destination-ip any ip-protocol icmp exit ip-rule 40 source-ip <Branch data Subnet> <Branch data Subnet Mask> destination-ip composite-operation Permit exit ip-rule 50 Administering Avaya G430 Branch Gateway October 2013...
  • Page 528 ! The following command specifies the Voice bearer dscp 46 next-hop list 1 exit ip-rule 20 ! The following command specifies the Voice Control dscp 34 next-hop list 2 exit ip-rule default next-hop PBR exit exit Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 529: Typical Failover Applications

    VPN peers. On the Branch Gateway, configure that hostname as your remote peer. The Branch Gateway will perform a DNS query in order to resolve the hostname to an IP address before establishing an IKE connection. Administering Avaya G430 Branch Gateway October 2013...
  • Page 530 Redundancy: GRE2 is configured as a backup interface for GRE1, and is activated only when GRE1 is down Load sharing: Both Tunnel interfaces are active. Routing protocols (RIP or OSPF) route traffic to destinations based on route cost and availability, as follows: Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 531 An access control list (ACL) is configured on the Internet interface to allow only the VPN / ICMP traffic. See VPN hub redundancy and load sharing topologies on page 532 for configuration settings. For information about using access control lists, see Policy lists page 557. Administering Avaya G430 Branch Gateway October 2013...
  • Page 532 2 authentication pre-share exit crypto isakmp peer address <Primary Main Office Internet public Static IP Address> pre-shared-key <key1> isakmp-policy 1 exit crypto isakmp peer address <Backup Main Office Internet public Static Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 533 Ike-nat-t-vsu composite-operation permit exit ip-rule 40 source-ip any destination-ip any ip-protocol esp composite-operation Permit exit ip-rule 50 source-ip any destination-ip host <Branch Office Public Internet Static IP Address> Administering Avaya G430 Branch Gateway October 2013...
  • Page 534 <Branch GRE Tunnel end point IP Address> destination-ip host <Primary Main Office GRE Tunnel end point IP Address> composite-operation Permit exit ip-rule 70 source-ip host <Branch GRE Tunnel end point IP Address> Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 535 <Primary Main Offfice GRE Tunnel end point IP Address> 255.255.255.255 FastEthernet 10/3 high ip route <Backup Main Offfice GRE Tunnel end point IP Address> 255.255.255.255 FastEthernet 10/3 high router ospf network 10.10.10.0 0.0.0.3 area 0.0.0.0 network 20.20.20.0 0.0.0.3 area 0.0.0.0 exit Administering Avaya G430 Branch Gateway October 2013...
  • Page 536 The Branch Gateway can sense that a peer is dead when IKE negotiation times-out through DPD keepalives and through object tracking. VPN DNS topology Note: For an explanation of DNS resolver, see DNS resolver on page 74. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 537 Permit DNS traffic to allow clear (unencrypted) DNS traffic b. Permit IKE Traffic (UDP port 500) for VPN control traffic (IKE) c. Permit ESP traffic (IP Protocol ESP) for VPN data traffic (IPSEC) Administering Avaya G430 Branch Gateway October 2013...
  • Page 538 ! Define the Private Subnet2 interface vlan 2 description “Branch Subnet2” ip address 10.0.20.1 255.255.255.0 exit ! Define the Public Subnet interface fastethernet 10/3 ip address 100.0.0.2 255.255.255.0 exit Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 539 5 source-ip destination-ip 123.124.125.126 no protect exit ip-rule 10 source-ip 10.0.10.0 0.0.0.255 destination-ip any protect crypto map 1 exit ip-rule 20 source-ip 10.0.20.0 0.0.0.255 destination-ip any protect crypto map 1 exit exit Administering Avaya G430 Branch Gateway October 2013...
  • Page 540 10.0.20.0 0.0.0.255 composite-operation Permit exit ip-rule default composite-operation deny exit exit ! Define the Egress access control list for the public interface ip access-control-list 302 ip-rule 5 source-ip destination-ip ip-protocol Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 541 ! Activate the crypto list and the access control list on the public interface interface fastethernet 10/3 ip crypto-group 901 ip access-group 301 in ip access-group 302 out exit Administering Avaya G430 Branch Gateway October 2013...
  • Page 542 Define a track list that will monitor (by ICMP) five hosts behind the specific peer. If two or more hosts are not working then the object tracker is down. The Branch Gateway will then pass on to the next peer in the peer group list. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 543 This traffic will be allowed only if it tunnels under the VPN, because of the crypto list. e. Define all other traffic (default rule) as deny in order to protect the device from non-secure traffic Administering Avaya G430 Branch Gateway October 2013...
  • Page 544 ! We wish to check 5 hosts in the Corporate intranet behind the current VPN ! remote peer, and if 2 or more hosts don’t work then keepalive-track will fail , ! and we will move to the next peer in the peer-group Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 545 <Second Main Office VPN address> pre-shared-key <key2> isakmp-policy 1 keepalive-track 1 exit crypto isakmp peer address <Third Main Office VPN address> pre-shared-key <key3> isakmp-policy 1 keepalive-track 1 exit Administering Avaya G430 Branch Gateway October 2013...
  • Page 546 Ike-nat-t composite-operation permit exit ip-rule 12 source-ip any destination-ip any ip-protocol udp destination-port eq Ike-nat-t-vsu composite-operation permit exit ip-rule 20 source-ip destination-ip ip-protocol composite-operation Permit exit ip-rule 30 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 547 Permit exit ip-rule 30 source-ip destination-ip ip-protocol icmp composite-operation Permit exit ip-rule 40 source-ip 10.0.10.0 0.0.0.255 destination-ip composite-operation Permit exit ip-rule 50 source-ip 10.0.20.0 0.0.0.255 destination-ip composite-operation Permit exit Administering Avaya G430 Branch Gateway October 2013...
  • Page 548 4. Coordinating with the VPN Remote peer a.) VPN IKE (Control) Phase 1 Parameters — Encryption • des • 3des • aes • aes-192 • aes-256 — Authentication Hash • sha • md5 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 549 • disable 5. Which packets should be secured a. Protect rules matching options • IP source address • IP destination address b. Bypass rules matching options • IP source address • IP destination address Administering Avaya G430 Branch Gateway October 2013...
  • Page 550 (device is an initiator) • Set self identity to identify the device in the remote peer Summary of VPN commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level First level Second level...
  • Page 551 IKE, which keeps the IKE channel phase1 session always up and running, even if there is no traffic description Enter a description for the ISAKMP peer initiate Specify which IKE Phase-1 mode to use when mode Administering Avaya G430 Branch Gateway October 2013...
  • Page 552 ISAKMP policy to pre-shared secret description Enter a description for the ISAKMP policy encryption Set the encryption algorithm for an ISAKMP policy group Set the Diffie-Hellman group for an ISAKMP policy Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 553 Set the minimal PMTU value that can be applied to an SA ipsec when the Branch Gateway minimal- participates in PMTUD for the pmtu tunnel pertaining to that SA Administering Avaya G430 Branch Gateway October 2013...
  • Page 554 Display the configuration for the specified transform-set or all ipsec transform-sets transform-set show crypto Display crypto ISAKMP peer configuration isakmp peer Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 555 Display all or specific crypto map configurations show ip Display information about a specific policy list or all lists active-lists show ip Display all or specific crypto list configurations crypto-list Administering Avaya G430 Branch Gateway October 2013...
  • Page 556 IPSec VPN Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 557: Chapter 20: Policy Lists

    Types of policy lists There are various policy lists on the Branch Gateway, including access control lists, QoS lists, and Policy-based routing. Related topics: About access control lists on page 558 QoS lists on page 559 Administering Avaya G430 Branch Gateway October 2013...
  • Page 558 IP addresses, protocols, ports, IP fragments, or DSCP values. The following figure illustrates how access control lists are used to control traffic into and out of your network. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 559 Composite operations on page 574. DSCP map: A table that contains DSCP code points and match action pairs. Match actions are pointers to the composite operation table. Refer to DSCP table on page 577. Administering Avaya G430 Branch Gateway October 2013...

  • Page 560: Policy List Management

    You can manage policy lists on the Branch Gateway with CLI commands. You can also manage policy lists throughout your network with Avaya QoS Manager. Avaya QoS Manager is part of Avaya Integrated Management. The following figure illustrates the operation of policy lists on the Branch Gateway:...

  • Page 561: Policy List Configuration

    400-499. The Branch Gateway includes one pre-configured QoS list. The pre-configured QoS list is list number 400. For example, to create a new QoS list 401, enter the following command: ip qos-list 401 Administering Avaya G430 Branch Gateway October 2013...
  • Page 562 577 Defining list identification attributes About this task The policy list attributes including name, owner, and cookie, are used by Avaya QoS Manager software to identify policy lists. Procedure 1. Enter the context of the policy list in which you want to define the attribute.
  • Page 563 Defines a list owner (text string). The default value is list# <listnumber>. cookie Defines a list cookie (integer). The Avaya QoS Manager uses the cookie attribute internally. Normally, you should not change this attribute. show list View the attributes.

  • Page 564: Policy List Attachments

    1. Apply the egress access control list. 2. If the egress access control list does not drop the packet, apply the egress QoS list. The packet exits the Branch Gateway through the interface. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 565 • To attach an access control list to an interface as its egress access control list, enter the interface context and enter ip access-group list number out. Administering Avaya G430 Branch Gateway October 2013...
  • Page 566 You can then change or delete the list. After changing the list, you can reattach the list to the interface. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 567: Device-Wide Policy Lists

    2. Enter one of the following commands, followed by the name of a composite command: • ip-fragments-in. Applies to incoming packets that contain IP fragments • ip-option-in. Applies to incoming packets that contain IP options Administering Avaya G430 Branch Gateway October 2013...

  • Page 568: Policy Rule Configuration

    IP option field. Related topics: Editing and creating rules on page 569 Policy lists rule criteria on page 569 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 569 Specifying a range of IP addresses on page 570 Specifying source and destination port range on page 571 Applying the rule to ICMP type and code on page 572 Specifying TCP establish bit on page 573 Administering Avaya G430 Branch Gateway October 2013...
  • Page 570 • To specify a wildcard, type host, followed by an IP address using wildcards to set a range of IP addresses to which the rule applies • To specify all addresses, type any to apply the rule to all IP addresses Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 571 • To set a range of port numbers to which the rule applies, type range, followed by two port numbers. • To set a port name or port number to which the rule applies, type eq (equal) followed by a port name or number. Administering Avaya G430 Branch Gateway October 2013...
  • Page 572 2. To apply the rule to all ICMP packets except the specified type and code, enter no icmp Example For example, the following command specifies an ICMP echo reply packet for rule 1 in QoS list 401: Gxxx-001(QoS 401/rule 1)# icmp Echo-Reply Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 573 Gxxx-001(super-ACL 301/ip rule 5)# fragment Done! Gxxx-001(super-ACL 301/ip rule 5)# Specifying DSCP Procedure 1. Enter dscp, followed by a DSCP value (from 0 to 63), to apply the rule to all packets with the specified DSCP value. Administering Avaya G430 Branch Gateway October 2013...

  • Page 574: Composite Operations

    The following table lists the pre-configured entries in the composite operation table for rules in an access control list: Name Access Notify Reset Connection Permit forward no trap no reset Deny deny no trap no reset Deny-Notify deny trap all no reset Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 575 Trust-DSCP DSCP Trust-DSCP-CoS DSCP and CoS Each column represents the following: No: A number identifying the operation Name: A name identifying the operation. Use this name to attach the operation to a rule. Administering Avaya G430 Branch Gateway October 2013...
  • Page 576 You must assign a name to the composite operation, because when you attach the composite operation to a rule, you use the name, not the index number, to identify the composite operation. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 577: Dscp Table

    A DSCP value can be mapped to a Class of Service (CoS). Then, for a CoS, rules can be applied to determine priority behavior for packets meeting the criteria for the entire CoS. Administering Avaya G430 Branch Gateway October 2013...
  • Page 578 Gxxx-001(super)# ip qos-list 402 Gxxx-001(super/QoS 402)# composite-operation 12 Gxxx-001(super/QoS 402/CompOp 12)# name dscp5 Done! Gxxx-001(super/QoS 402/CompOp 12)# dscp 5 Done! Gxxx-001(super/QoS 402/CompOp 12)# cos No-Change Done! Gxxx-001(super/QoS 402/CompOp 12)# exit Gxxx-001(super/QoS 402)# dscp-table 7 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 579: Policy List Displays And Tests

    - show list. displays the parameters of the current list, including its rules • In ip access-control-list/ip-rule context: - show composite-operation. Displays the parameters of the composite operation assigned to the current rule - show ip-rule. Displays the parameters of the current rule Administering Avaya G430 Branch Gateway October 2013...
  • Page 580 Specify the number of a policy list, the direction of the packet (in or out), and a source and destination IP address. You may also specify other parameters. For a full list of parameters, see Avaya Branch Gateway G430 CLI Reference. Example...

  • Page 581: Summary Of Access Control List Commands

    • IP protocol is TCP • source TCP port is 1182 • destination TCP port is 20 Summary of access control list commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level Command...
  • Page 582 Display the attributes of the current rule source-ip Apply the current rule to packets from the specified source IP address Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 583: Summary Of Qos List Commands

    Display the attributes of a specific access control list or access- of all access control lists control- list Summary of QoS list commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Administering Avaya G430 Branch Gateway October 2013...
  • Page 584 Enter the DSCP table entry context for a particular DSCP value for the current QoS list composite- Specify the composite operation to execute for operation packets with the specified DSCP value Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 585 Display the attributes of the current rule rule source-ip Apply the current rule to packets from the specified source IP address Apply the current rule to TCP packets with the specified destinatio destination port n-port Administering Avaya G430 Branch Gateway October 2013...
  • Page 586 Display the attributes of the current list, including its rules show ip Display the attributes of a specific QoS list or all QoS lists qos-list Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 587: Chapter 21: Policy-Based Routing

    Telnet, SSH, FTP, DHCP Relay, TFTP, HTTP, NTP, SNMP, H.248, and other types of traffic. The Loopback interface is also used for traffic to and from analog and DCP phones connected to the device via IP phone entities. Administering Avaya G430 Branch Gateway October 2013...

  • Page 588: Applications For Policy-Based Routing

    Bearer packets (DSCP = 46). Policy-based routing sends these packets over the T1 WAN line, and sends other packets over the Internet. This saves bandwidth on the more expensive external Serial interface. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 589: Setting Up Policy-Based Routing

    598. Procedure 1. Define PBR lists. • In general context, enter ip pbr-list followed by a list number in the range 800 to 899. For example: Gxxx-001(super)# ip pbr-list 802 Gxxx-001(super-PBR 802)# Administering Avaya G430 Branch Gateway October 2013...
  • Page 590 3. Define next hop lists. Enter exit twice to return to general context. In general context, define all the next hop lists that you have used in PBR rules. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 591 Done! Gxxx-001(super-next hop list 1)#next-hop-ip 2 172.16.1.221 Done! Gxxx-001(super-next hop list 1)#next-hop-interface 3 Null0 Done! Gxxx-001(super-next hop list 1)# For additional details about next hop lists, see Next hop lists on page 594. Administering Avaya G430 Branch Gateway October 2013...

  • Page 592: Pbr Rules

    • IP protocol, such as TCP, UDP, ICMP, IGMP • Source TCP or UDP port or a range of ports • Destination TCP or UDP port or a range of ports • ICMP type and code Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 593 2. Enter ip-rule followed by the number of the rule you want to modify. For example, to create rule 1, enter ip-rule 1. To view the rules that belong to a PBR list, enter the list’s context and then enter show ip-rule. Administering Avaya G430 Branch Gateway October 2013...

  • Page 594: Next Hop Lists

    For example, to modify next hop list 1, enter ip next-hop-list 1. 2. To show the next hops in an existing list, enter the context of the next hop list and enter show next-hop. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 595 For example, the command no next-hop-interface 3 deletes the third entry from the next hop list. Canceling tracking and keeping the next hop Procedure 1. Enter the context of the next hop list. Administering Avaya G430 Branch Gateway October 2013...

  • Page 596: Editing And Deleting Pbr Lists

    Redefine the parameters of the list. 3. To delete a PBR list, enter exit to return to general context and enter no ip pbr- list followed by the number of the list you want to delete. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 597: Pbr List Commands In Context

    - show ip-rule rule number. Displays the parameters of the specified rule • In next hop list context: - show next-hop. Displays the next hop entries in the current next hop list and their current status Administering Avaya G430 Branch Gateway October 2013...

  • Page 598: Policy-Based Routing Application Example

    41, 43, 44, and 46) to be routed according to next hop list 1. This list directs packets to the T1/ E1 interface. If that interface is down, the packets are dropped. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 599 IP address of the Layer 3 router. If that interface is not available, the next hop list requires the packet to be dropped (Null0). This is because the QoS on the Internet interface is not Administering Avaya G430 Branch Gateway October 2013...
  • Page 600 This allows data traffic to use the E1/T1 interface, but only when the GRE tunnel is not available. Alternatively, the list can be configured without the Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 601: Summary Of Policy-Based Routing Commands

    Policy-based routing supports the ip simulate command for testing policies. Refer to Simulating packets on page 580. Summary of policy-based routing commands For more information about these commands, see the Avaya Branch Gateway G430 CLI Reference. Root level First level...
  • Page 602 Display the details of the next-hop list or of all next-hop lists next-hop- list show ip-rule Display the attributes of a specific rule or all rules Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 603 Display details about a specific PBR list or all PBR lists active- pbr- lists show ip Display information about the specified PBR list pbr-list Administering Avaya G430 Branch Gateway October 2013...
  • Page 604 Policy-based routing Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 605: Chapter 22: Synchronization

    • portID is the port number for an ISDN clock source candidate. The port ID consists of the slot number of the media module and the number of the port. You can set more than one port. For example, v2 1, 3, 5-8. Administering Avaya G430 Branch Gateway October 2013...

  • Page 606: Setting The Synchronization Source

    Branch Gateway chassis as the clock synchronization source. If neither MM710 media module can function as the clock synchronization source, the system defaults to the local clock running on the chassis. Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 607: Disassociating A Clock Source

    - The yellow ACT LED is on for 200 milliseconds and off for 2.8 seconds if the MM710 media module has been specified as a synchronization source and is not receiving a signal, or is receiving a signal that does not meet the minimum requirements for the interface Administering Avaya G430 Branch Gateway October 2013...
  • Page 608 Active None Active Source: v0 Sync Source Switching: Enabled Done! Summary of synchronization commands For more information about these commands, see Avaya Branch Gateway G430 CLI Reference. Command Description clear sync Disassociate a previously specified interface as the primary or...
  • Page 609 Synchronization Command Description show sync Display the status of the primary, secondary, and local clock sources timing Administering Avaya G430 Branch Gateway October 2013...
  • Page 610 Synchronization Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 611: Appendix A: Traps And Mibs

    A warmStart with No trap indicates Changes that the entity (warmStart sending the Trap) protocol is enterprise: reinitializing $E ($e) itself in such a args($#):$* way as to keep both the agent configuration Administering Avaya G430 Branch Gateway October 2013...
  • Page 612 Interface indicates that atus, Down the entity that is ifOperStat (linkDown sending the Trap) protocol enterprise: recognizes a $E ($e) on failure in one of interface communication links represented in Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 613 = $1) configured for sending SNMP Threshold traps fallingAlar alarmInde THRE Warni falling Falling The SNMP trap Alarm Alarm: $2 that is alarmVari HOLD fell below generated able, threshold when an alarm Administering Avaya G430 Branch Gateway October 2013...
  • Page 614 It gives the logical name of the redundant link the identification of the main and secondary ports and the status of the link. The softRedundanc yId defines the instances of the above- Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 615 Activation ChangeE - Active a change in the EntID, vent policy list active list ipPolicy changed to specific for a Activation policy-enabled List, box or module. ipPolicy Activation if Index, ipPolicy Activation Context Administering Avaya G430 Branch Gateway October 2013...
  • Page 616 4DstPort, sent at intervals ipPolicy smaller than AccessCo one minute for ntrolViolat identical information in Establish the varbinds list variables. ipPolicyR uleID, ipPolicyR ule ListID, ipPolicy AccessCo ntrolViolat ionIf Index, ipPolicy Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 617 BUPSActi vity Status WanPhysi ifIndex, Critica Cable An E1/T1/serial ifAdminSt Physical Problem on cable was AlarmOn atus, AlarmOn port $4 disconnected. ifOperStat ifName, Administering Avaya G430 Branch Gateway October 2013...
  • Page 618 AlarmOn interface ifOperStat ifName, ifAlias, dsx1Line Status wanRemo ifIndex, Notific Remote Remote alarms, ifAdminSt ation Remote Alarm on such as AIS, AlarmOff atus, AlarmOff interface was cleared. ifOperStat $4 was cleared Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 619 SensorLo Warning AvEntFan entPhysic TEMP Notific AvEntFa Fan $2 is This trap al Index, ation reports the entPhysic return to al Descr, function of a entPhySe faulty fan. nsor Value, avEntPhy SensorLo Warning Administering Avaya G430 Branch Gateway October 2013...

  • Page 620: Branch Gateway Mib Files

    SensorHi device. Warning, entPhysic ParentRel Branch Gateway MIB files MIB File MIB Module Supported by Branch Gateway Load.MIB LOAD-MIB Q-BRIDGE-MIB.my Q-BRIDGE-MIB ENTITY-MIB.my ENTITY-MIB IP-FORWARD-MIB.my IP-FORWARD-MIB VRRP-MIB.my VRRP-MIB UTILIZATION-MANAGEMENT-MIB.my UTILIZATION-MANAGEMENT-MIB Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 621 OSPF-MIB.my OSPF-MIB Tunnel-MIB.my TUNNEL-MIB Related topics: MIB objects in the Load.MIB file on page 622 MIB objects in the RFC1315-MIB.my file on page 624 MIB objects in the Q-BRIDGE-MIB.my file on page 625 Administering Avaya G430 Branch Gateway October 2013...
  • Page 622 MIB objects in the PPP-IP-NCP-MIB.my file on page 630 MIB objects in the RFC1213-MIB.my file on page 630 MIB objects in the AVAYA-ENTITY-MIB.my file on page 634 MIB objects in the Rnd-MIB.my file on page 634 MIB objects in the XSWITCH-MIB.my file on page 635 MIB objects in the CROUTE-MIB.my file...
  • Page 623 1.3.6.1.4.1.1751.2.53.1.2.1.15 genOpResetSupported 1.3.6.1.4.1.1751.2.53.1.2.1.16 genOpEnableReset 1.3.6.1.4.1.1751.2.53.1.2.1.17 genOpNextBootImageIndex 1.3.6.1.4.1.1751.2.53.1.2.1.18 genOpLastBootImageIndex 1.3.6.1.4.1.1751.2.53.1.2.1.19 genOpFileSystemType 1.3.6.1.4.1.1751.2.53.1.2.1.20 genOpReportSpecificFlags 1.3.6.1.4.1.1751.2.53.1.2.1.21 genOpOctetsReceived 1.3.6.1.4.1.1751.2.53.1.2.1.22 genAppFileId 1.3.6.1.4.1.1751.2.53.2.1.1.1 genAppFileName 1.3.6.1.4.1.1751.2.53.2.1.1.2 genAppFileType 1.3.6.‘1.4.1.1751.2.53.2.1.1.3 genAppFileDescription 1.3.6.1.4.1.1751.2.53.2.1.1.4 genAppFileSize 1.3.6.1.4.1.1751.2.53.2.1.1.5 genAppFileVersionNumber 1.3.6.1.4.1.1751.2.53.2.1.1.6 genAppFileLocation 1.3.6.1.4.1.1751.2.53.2.1.1.7 genAppFileDateStamp 1.3.6.1.4.1.1751.2.53.2.1.1.8 genAppFileRowStatus 1.3.6.1.4.1.1751.2.53.2.1.1.9 Administering Avaya G430 Branch Gateway October 2013...
  • Page 624 1.3.6.1.2.1.10.32.2.1.2 frCircuitState 1.3.6.1.2.1.10.32.2.1.3 frCircuitReceivedFECNs 1.3.6.1.2.1.10.32.2.1.4 frCircuitReceivedBECNs 1.3.6.1.2.1.10.32.2.1.5 frCircuitSentFrames 1.3.6.1.2.1.10.32.2.1.6 frCircuitSentOctets 1.3.6.1.2.1.10.32.2.1.7 frCircuitReceivedFrames 1.3.6.1.2.1.10.32.2.1.8 frCircuitReceivedOctets 1.3.6.1.2.1.10.32.2.1.9 frCircuitCreationTime 1.3.6.1.2.1.10.32.2.1.10 frCircuitLastTimeChange 1.3.6.1.2.1.10.32.2.1.11 frCircuitCommittedBurst 1.3.6.1.2.1.10.32.2.1.12 frCircuitExcessBurst 1.3.6.1.2.1.10.32.2.1.13 frCircuitThroughput 1.3.6.1.2.1.10.32.2.1.14 frErrIfIndex 1.3.6.1.2.1.10.32.3.1.1 frErrType 1.3.6.1.2.1.10.32.3.1.2 frErrData 1.3.6.1.2.1.10.32.3.1.3 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 625 1.3.6.1.2.1.17.7.1.4.2.1.2 dot1qVlanFdbId 1.3.6.1.2.1.17.7.1.4.2.1.3 dot1qVlanCurrentEgressPorts 1.3.6.1.2.1.17.7.1.4.2.1.4 dot1qVlanCurrentUntaggedPorts 1.3.6.1.2.1.17.7.1.4.2.1.5 dot1qVlanStatus 1.3.6.1.2.1.17.7.1.4.2.1.6 dot1qVlanCreationTime 1.3.6.1.2.1.17.7.1.4.2.1.7 dot1qVlanStaticName 1.3.6.1.2.1.17.7.1.4.3.1.1 dot1qVlanStaticEgressPorts 1.3.6.1.2.1.17.7.1.4.3.1.2 dot1qVlanForbiddenEgressPorts 1.3.6.1.2.1.17.7.1.4.3.1.3 dot1qVlanStaticUntaggedPorts 1.3.6.1.2.1.17.7.1.4.3.1.4 dot1qVlanStaticRowStatus 1.3.6.1.2.1.17.7.1.4.3.1.5 dot1qNextFreeLocalVlanIndex 1.3.6.1.2.1.17.7.1.4.4 dot1qPvid 1.3.6.1.2.1.17.7.1.4.5.1.1 dot1qPortAcceptableFrameTypes 1.3.6.1.2.1.17.7.1.4.5.1.2 dot1qPortIngressFiltering 1.3.6.1.2.1.17.7.1.4.5.1.3 dot1qPortGvrpStatus 1.3.6.1.2.1.17.7.1.4.5.1.4 dot1qPortGvrpFailedRegistrations 1.3.6.1.2.1.17.7.1.4.5.1.5 Administering Avaya G430 Branch Gateway October 2013...
  • Page 626 MIB objects in the IP-FORWARD-MIB.my file The following table provides a list of the MIBs in the IP-FORWARD-MIB.my file that are supported by the Branch Gateway and their OIDs: Object ipCidrRouteNumber 1.3.6.1.2.1.4.24.3 ipCidrRouteDest 1.3.6.1.2.1.4.24.4.1.1 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 627 The following table provides a list of the MIBs in the VRRP-MIB.my file that are supported by the Branch Gateway and their OIDs: Object vrrpNodeVersion 1.3.6.1.2.1.68.1.1.1 vrrpOperVrId 1.3.6.1.2.1.68.1.1.3.1.1 vrrpOperVirtualMacAddr 1.3.6.1.2.1.68.1.1.3.1.2 vrrpOperState 1.3.6.1.2.1.68.1.1.3.1.3 vrrpOperAdminState 1.3.6.1.2.1.68.1.1.3.1.4 vrrpOperPriority 1.3.6.1.2.1.68.1.1.3.1.5 vrrpOperIpAddrCount 1.3.6.1.2.1.68.1.1.3.1.6 vrrpOperMasterIpAddr 1.3.6.1.2.1.68.1.1.3.1.7 vrrpOperPrimaryIpAddr 1.3.6.1.2.1.68.1.1.3.1.8 vrrpOperAuthType 1.3.6.1.2.1.68.1.1.3.1.9 Administering Avaya G430 Branch Gateway October 2013...
  • Page 628 1.3.6.1.4.1.6889.2.1.11.1.1.1.1.2 genCpuUtilizationEnableEventGeneration 1.3.6.1.4.1.6889.2.1.11.1.1.1.1.3 genCpuUtilizationHighThreshold 1.3.6.1.4.1.6889.2.1.11.1.1.1.1.4 genCpuAverageUtilization 1.3.6.1.4.1.6889.2.1.11.1.1.1.1.5 genCpuCurrentUtilization 1.3.6.1.4.1.6889.2.1.11.1.1.1.1.6 genCpuUtilizationHistorySampleIndex 1.3.6.1.4.1.6889.2.1.11.1.1.2.1.1 genCpuHistoryUtilization 1.3.6.1.4.1.6889.2.1.11.1.1.2.1.2 genMemUtilizationTotalRAM 1.3.6.1.4.1.6889.2.1.11.1.2.1 genMemUtilizationOperationalImage 1.3.6.1.4.1.6889.2.1.11.1.2.2 genMemUtilizationDynAllocMemUsed 1.3.6.1.4.1.6889.2.1.11.1.2.3.1 genMemUtilizationDynAllocMemMaxUsed 1.3.6.1.4.1.6889.2.1.11.1.2.3.2 genMemUtilizationDynAllocMemAvailable 1.3.6.1.4.1.6889.2.1.11.1.2.3.3 genMemUtilizationAllocationFailures 1.3.6.1.4.1.6889.2.1.11.1.2.4 genMemUtilizationID 1.3.6.1.4.1.6889.2.1.11.1.2.6.1.1 genMemUtilizationPhyRam 1.3.6.1.4.1.6889.2.1.11.1.2.6.1.2 genMemUtilizationPercentUsed 1.3.6.1.4.1.6889.2.1.11.1.2.6.1.3 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 629 The following table provides a list of the MIBs in the RSTP-MIB.my file that are supported by the Branch Gateway and their OIDs: Object dot1dStpVersion 1.3.6.1.2.1.17.2.16 dot1dStpTxHoldCount 1.3.6.1.2.1.17.2.17 dot1dStpPathCostDefault 1.3.6.1.2.1.17.2.18 dot1dStpPortProtocolMigration 1.3.6.1.2.1.17.2.19.1.1 dot1dStpPortAdminEdgePort 1.3.6.1.2.1.17.2.19.1.2 dot1dStpPortOperEdgePort 1.3.6.1.2.1.17.2.19.1.3 dot1dStpPortAdminPointToPoint 1.3.6.1.2.1.17.2.19.1.4 dot1dStpPortOperPointToPoint 1.3.6.1.2.1.17.2.19.1.5 dot1dStpPortAdminPathCost 1.3.6.1.2.1.17.2.19.1.6 Administering Avaya G430 Branch Gateway October 2013...
  • Page 630 1.3.6.1.2.1.10.23.3.2.1.2 MIB objects in the RFC1213-MIB.my file The following table provides a list of the MIBs in the RFC1213-MIB.my file that are supported by the Branch Gateway and their OIDs: Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 631 1.3.6.1.2.1.2.2.1.7 ifOperStatus 1.3.6.1.2.1.2.2.1.8 ifLastChange 1.3.6.1.2.1.2.2.1.9 ifInOctets 1.3.6.1.2.1.2.2.1.10 ifInUcastPkts 1.3.6.1.2.1.2.2.1.11 ifInNUcastPkts 1.3.6.1.2.1.2.2.1.12 ifInDiscards 1.3.6.1.2.1.2.2.1.13 ifInErrors 1.3.6.1.2.1.2.2.1.14 ifInUnknownProtos 1.3.6.1.2.1.2.2.1.15 ifOutOctets 1.3.6.1.2.1.2.2.1.16 ifOutUcastPkts 1.3.6.1.2.1.2.2.1.17 ifOutNUcastPkts 1.3.6.1.2.1.2.2.1.18 ifOutDiscards 1.3.6.1.2.1.2.2.1.19 ifOutErrors 1.3.6.1.2.1.2.2.1.20 ifOutQLen 1.3.6.1.2.1.2.2.1.21 ifSpecific 1.3.6.1.2.1.2.2.1.22 ipForwarding 1.3.6.1.2.1.4.1 Administering Avaya G430 Branch Gateway October 2013...
  • Page 632 1.3.6.1.2.1.4.17 ipFragFails 1.3.6.1.2.1.4.18 ipFragCreates 1.3.6.1.2.1.4.19 ipAdEntAddr 1.3.6.1.2.1.4.20.1.1 ipAdEntIfIndex 1.3.6.1.2.1.4.20.1.2 ipAdEntNetMask 1.3.6.1.2.1.4.20.1.3 ipAdEntBcastAddr 1.3.6.1.2.1.4.20.1.4 ipAdEntReasmMaxSize 1.3.6.1.2.1.4.20.1.5 ipRouteDest 1.3.6.1.2.1.4.21.1.1 ipRouteIfIndex 1.3.6.1.2.1.4.21.1.2 ipRouteMetric1 1.3.6.1.2.1.4.21.1.3 ipRouteMetric2 1.3.6.1.2.1.4.21.1.4 ipRouteMetric3 1.3.6.1.2.1.4.21.1.5 ipRouteMetric4 1.3.6.1.2.1.4.21.1.6 ipRouteNextHop 1.3.6.1.2.1.4.21.1.7 ipRouteType 1.3.6.1.2.1.4.21.1.8 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 633 1.3.6.1.2.1.11.5 snmpInASNParseErrs 1.3.6.1.2.1.11.6 snmpInTooBigs 1.3.6.1.2.1.11.8 snmpInNoSuchNames 1.3.6.1.2.1.11.9 snmpInBadValues 1.3.6.1.2.1.11.10 snmpInReadOnlys 1.3.6.1.2.1.11.11 snmpInGenErrs 1.3.6.1.2.1.11.12 snmpInTotalReqVars 1.3.6.1.2.1.11.13 snmpInTotalSetVars 1.3.6.1.2.1.11.14 snmpInGetRequests 1.3.6.1.2.1.11.15 snmpInGetNexts 1.3.6.1.2.1.11.16 snmpInSetRequests 1.3.6.1.2.1.11.17 snmpInGetResponses 1.3.6.1.2.1.11.18 snmpInTraps 1.3.6.1.2.1.11.19 snmpOutTooBigs 1.3.6.1.2.1.11.20 snmpOutNoSuchNames 1.3.6.1.2.1.11.21 snmpOutBadValues 1.3.6.1.2.1.11.22 Administering Avaya G430 Branch Gateway October 2013...
  • Page 634 1.3.6.1.2.1.11.28 snmpOutTraps 1.3.6.1.2.1.11.29 snmpEnableAuthenTraps 1.3.6.1.2.1.11.30 MIB objects in the AVAYA-ENTITY-MIB.my file The following table provides a list of the MIBs in the AVAYA-ENTITY-MIB.my file that are supported by the Branch Gateway and their OIDs: Object avEntPhySensorHiShutdown 1.3.6.1.4.1.6889.2.1.99.1.1.1 avEntPhySensorHiWarning 1.3.6.1.4.1.6889.2.1.99.1.1.2 avEntPhySensorHiWarningClear 1.3.6.1.4.1.6889.2.1.99.1.1.3...
  • Page 635 1.3.6.1.4.1.81.28.2.1.1.1.47 MIB objects in the CROUTE-MIB.my file The following table provides a list of the MIBs in the CROUTE-MIB.my file that are supported by the Branch Gateway and their OIDs: Object ipGlobalsBOOTPRelayStatus 1.3.6.1.4.1.81.31.1.1.1 Administering Avaya G430 Branch Gateway October 2013...
  • Page 636 1.3.6.1.4.1.81.31.1.2.1.12 ipInterfaceIcmpRedirects 1.3.6.1.4.1.81.31.1.2.1.13 ipInterfaceOperStatus 1.3.6.1.4.1.81.31.1.2.1.14 ipInterfaceDhcpRelay 1.3.6.1.4.1.81.31.1.2.1.15 ripGlobalsRIPEnable 1.3.6.1.4.1.81.31.1.3.1 ripGlobalsLeakOSPFIntoRIP 1.3.6.1.4.1.81.31.1.3.2 ripGlobalsLeakStaticIntoRIP 1.3.6.1.4.1.81.31.1.3.3 ripGlobalsPeriodicUpdateTimer 1.3.6.1.4.1.81.31.1.3.4 ripGlobalsPeriodicInvalidRouteTimer 1.3.6.1.4.1.81.31.1.3.5 ripGlobalsDefaultExportMetric 1.3.6.1.4.1.81.31.1.3.6 ripInterfaceAddr 1.3.6.1.4.1.81.31.1.4.1.1 ripInterfaceMetric 1.3.6.1.4.1.81.31.1.4.1.2 ripInterfaceSplitHorizon 1.3.6.1.4.1.81.31.1.4.1.3 ripInterfaceAcceptDefaultRoute 1.3.6.1.4.1.81.31.1.4.1.4 ripInterfaceSendDefaultRoute 1.3.6.1.4.1.81.31.1.4.1.5 ripInterfaceState 1.3.6.1.4.1.81.31.1.4.1.6 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 637 1.3.6.1.4.1.81.31.1.10.1 distributionListRoutingProtocol 1.3.6.1.4.1.81.31.1.12.1.1 distributionListDirection 1.3.6.1.4.1.81.31.1.12.1.2 distributionListIfIndex 1.3.6.1.4.1.81.31.1.12.1.3 distributionListRouteProtocol 1.3.6.1.4.1.81.31.1.12.1.4 distributionListProtocolSpecific1 1.3.6.1.4.1.81.31.1.12.1.5 distributionListProtocolSpecific2 1.3.6.1.4.1.81.31.1.12.1.6 distributionListProtocolSpecific3 1.3.6.1.4.1.81.31.1.12.1.7 distributionListProtocolSpecific4 1.3.6.1.4.1.81.31.1.12.1.8 distributionListProtocolSpecific5 1.3.6.1.4.1.81.31.1.12.1.9 distributionListAccessListNumber 1.3.6.1.4.1.81.31.1.12.1.10 distributionListEntryStatus 1.3.6.1.4.1.81.31.1.12.1.11 ipVRRPAdminStatus 1.3.6.1.4.1.81.31.1.14.1 iphcIfIndex 1.3.6.1.4.1.81.31.1.15.1.1.1 iphcControlTcpAdminStatus 1.3.6.1.4.1.81.31.1.15.1.1.2 iphcTcpSessions 1.3.6.1.4.1.81.31.1.15.1.1.3 iphcNegotiatedTcpSessions 1.3.6.1.4.1.81.31.1.15.1.1.4 Administering Avaya G430 Branch Gateway October 2013...
  • Page 638 The following table provides a list of the MIBs in the RS-232-MIB.my file that are supported by the Branch Gateway and their OIDs: Object rs232Number 1.3.6.1.2.1.10.33.1 rs232PortIndex 1.3.6.1.2.1.10.33.2.1.1 rs232PortType 1.3.6.1.2.1.10.33.2.1.2 rs232PortInSigNumber 1.3.6.1.2.1.10.33.2.1.3 rs232PortOutSigNumber 1.3.6.1.2.1.10.33.2.1.4 rs232PortInSpeed 1.3.6.1.2.1.10.33.2.1.5 rs232PortOutSpeed 1.3.6.1.2.1.10.33.2.1.6 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 639 1.3.6.1.2.1.10.33.6.1.4 MIB objects in the RIPv2-MIB.my file The following table provides a list of the MIBs in the RIPv2-MIB.my file that are supported by the Branch Gateway and their OIDs: Object rip2GlobalRouteChanges 1.3.6.1.2.1.23.1.1 Administering Avaya G430 Branch Gateway October 2013...
  • Page 640 The following table provides a list of the MIBs in the IF-MIB.my file that are supported by the Branch Gateway and their OIDs: Object ifNumber 1.3.6.1.2.1.2.1 ifIndex 1.3.6.1.2.1.2.2.1.1 ifDescr 1.3.6.1.2.1.2.2.1.2 ifType 1.3.6.1.2.1.2.2.1.3 ifMtu 1.3.6.1.2.1.2.2.1.4 ifSpeed 1.3.6.1.2.1.2.2.1.5 ifPhysAddress 1.3.6.1.2.1.2.2.1.6 ifAdminStatus 1.3.6.1.2.1.2.2.1.7 ifOperStatus 1.3.6.1.2.1.2.2.1.8 ifLastChange 1.3.6.1.2.1.2.2.1.9 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 641 1.3.6.1.2.1.31.1.1.1.2 ifInBroadcastPkts 1.3.6.1.2.1.31.1.1.1.3 ifOutMulticastPkts 1.3.6.1.2.1.31.1.1.1.4 ifOutBroadcastPkts 1.3.6.1.2.1.31.1.1.1.5 ifHCInOctets 1.3.6.1.2.1.31.1.1.1.6 ifHCInUcastPkts 1.3.6.1.2.1.31.1.1.1.7 ifHCInMulticastPkts 1.3.6.1.2.1.31.1.1.1.8 ifHCInBroadcastPkts 1.3.6.1.2.1.31.1.1.1.9 ifHCOutOctets 1.3.6.1.2.1.31.1.1.1.10 ifHCOutUcastPkts 1.3.6.1.2.1.31.1.1.1.11 ifHCOutMulticastPkts 1.3.6.1.2.1.31.1.1.1.12 ifHCOutBroadcastPkts 1.3.6.1.2.1.31.1.1.1.13 ifLinkUpDownTrapEnable 1.3.6.1.2.1.31.1.1.1.14 ifHighSpeed 1.3.6.1.2.1.31.1.1.1.15 ifPromiscuousMode 1.3.6.1.2.1.31.1.1.1.16 ifConnectorPresent 1.3.6.1.2.1.31.1.1.1.17 ifAlias 1.3.6.1.2.1.31.1.1.1.18 Administering Avaya G430 Branch Gateway October 2013...
  • Page 642 The following table provides a list of the MIBs in the POLICY-MIB.MY file that are supported by the Branch Gateway and their OIDs: Object ipPolicyListSlot 1.3.6.1.4.1.81.36.1.1.1 ipPolicyListID 1.3.6.1.4.1.81.36.1.1.2 ipPolicyListName 1.3.6.1.4.1.81.36.1.1.3 ipPolicyListValidityStatus 1.3.6.1.4.1.81.36.1.1.4 ipPolicyListChecksum 1.3.6.1.4.1.81.36.1.1.5 ipPolicyListRowStatus 1.3.6.1.4.1.81.36.1.1.6 ipPolicyListDefaultOperation 1.3.6.1.4.1.81.36.1.1.7 ipPolicyListCookie 1.3.6.1.4.1.81.36.1.1.8 ipPolicyListTrackChanges 1.3.6.1.4.1.81.36.1.1.9 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 643 1.3.6.1.4.1.81.36.2.1.7 ipPolicyRuleProtocol 1.3.6.1.4.1.81.36.2.1.8 ipPolicyRuleL4SrcPortMin 1.3.6.1.4.1.81.36.2.1.9 ipPolicyRuleL4SrcPortMax 1.3.6.1.4.1.81.36.2.1.10 ipPolicyRuleL4DestPortMin 1.3.6.1.4.1.81.36.2.1.11 ipPolicyRuleL4DestPortMax 1.3.6.1.4.1.81.36.2.1.12 ipPolicyRuleEstablished 1.3.6.1.4.1.81.36.2.1.13 ipPolicyRuleOperation 1.3.6.1.4.1.81.36.2.1.14 ipPolicyRuleApplicabilityPrecedence 1.3.6.1.4.1.81.36.2.1.15 ipPolicyRuleApplicabilityStatus 1.3.6.1.4.1.81.36.2.1.16 ipPolicyRuleApplicabilityType 1.3.6.1.4.1.81.36.2.1.17 ipPolicyRuleErrMsg 1.3.6.1.4.1.81.36.2.1.18 ipPolicyRuleStatus 1.3.6.1.4.1.81.36.2.1.19 ipPolicyRuleDSCPOperation 1.3.6.1.4.1.81.36.2.1.20 ipPolicyRuleDSCPFilter 1.3.6.1.4.1.81.36.2.1.21 ipPolicyRuleDSCPFilterWild 1.3.6.1.4.1.81.36.2.1.22 ipPolicyRuleIcmpTypeCode 1.3.6.1.4.1.81.36.2.1.23 Administering Avaya G430 Branch Gateway October 2013...
  • Page 644 1.3.6.1.4.1.81.36.4.1.1 ipPolicyDiffServDSCP 1.3.6.1.4.1.81.36.4.1.2 ipPolicyDiffServOperation 1.3.6.1.4.1.81.36.4.1.3 ipPolicyDiffServName 1.3.6.1.4.1.81.36.4.1.4 ipPolicyDiffServAggIndex 1.3.6.1.4.1.81.36.4.1.5 ipPolicyDiffServApplicabilityPrecedence 1.3.6.1.4.1.81.36.4.1.6 ipPolicyDiffServApplicabilityStatus 1.3.6.1.4.1.81.36.4.1.7 ipPolicyDiffServApplicabilityType 1.3.6.1.4.1.81.36.4.1.8 ipPolicyDiffServErrMsg 1.3.6.1.4.1.81.36.4.1.9 ipPolicyQuerySlot 1.3.6.1.4.1.81.36.5.1.1 ipPolicyQueryListID 1.3.6.1.4.1.81.36.5.1.2 ipPolicyQuerySrcAddr 1.3.6.1.4.1.81.36.5.1.3 ipPolicyQueryDstAddr 1.3.6.1.4.1.81.36.5.1.4 ipPolicyQueryProtocol 1.3.6.1.4.1.81.36.5.1.5 ipPolicyQueryL4SrcPort 1.3.6.1.4.1.81.36.5.1.6 ipPolicyQueryL4DestPort 1.3.6.1.4.1.81.36.5.1.7 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 645 1.3.6.1.4.1.81.36.6.1.4 ipPolicyDiffServControlErrMsg 1.3.6.1.4.1.81.36.6.1.5 ipPolicyAccessControlViolationEntID 1.3.6.1.4.1.81.36.7.1.1 ipPolicyAccessControlViolationSrcAddr 1.3.6.1.4.1.81.36.7.1.2 ipPolicyAccessControlViolationDstAddr 1.3.6.1.4.1.81.36.7.1.3 ipPolicyAccessControlViolationProtocol 1.3.6.1.4.1.81.36.7.1.4 ipPolicyAccessControlViolationL4SrcPort 1.3.6.1.4.1.81.36.7.1.5 ipPolicyAccessControlViolationL4DstPort 1.3.6.1.4.1.81.36.7.1.6 ipPolicyAccessControlViolationEstablished 1.3.6.1.4.1.81.36.7.1.7 ipPolicyAccessControlViolationDSCP 1.3.6.1.4.1.81.36.7.1.8 ipPolicyAccessControlViolationIfIndex 1.3.6.1.4.1.81.36.7.1.9 ipPolicyAccessControlViolationSubCtxt 1.3.6.1.4.1.81.36.7.1.10 ipPolicyAccessControlViolationTime 1.3.6.1.4.1.81.36.7.1.11 ipPolicyAccessControlViolationRuleType 1.3.6.1.4.1.81.36.7.1.12 ipPolicyCompositeOpEntID 1.3.6.1.4.1.81.36.8.1.1 ipPolicyCompositeOpListID 1.3.6.1.4.1.81.36.8.1.2 ipPolicyCompositeOpID 1.3.6.1.4.1.81.36.8.1.3 Administering Avaya G430 Branch Gateway October 2013...
  • Page 646 1.3.6.1.4.1.81.36.9.1.7 ipPolicyDSCPmapApplicabilityType 1.3.6.1.4.1.81.36.9.1.8 ipPolicyDSCPmapErrMsg 1.3.6.1.4.1.81.36.9.1.9 ipPolicyActivationEntID 1.3.6.1.4.1.81.36.10.1.1 ipPolicyActivationifIndex 1.3.6.1.4.1.81.36.10.1.2 ipPolicyActivationSubContext 1.3.6.1.4.1.81.36.10.1.3 ipPolicyActivationSubContextName 1.3.6.1.4.1.81.36.10.1.4 ipPolicyActivationList 1.3.6.1.4.1.81.36.10.1.5 ipPolicyActivationAclList 1.3.6.1.4.1.81.36.10.1.6 ipPolicyActivationQoSList 1.3.6.1.4.1.81.36.10.1.7 ipPolicyActivationSourceNatList 1.3.6.1.4.1.81.36.10.1.8 ipPolicyActivationDestinationNatList 1.3.6.1.4.1.81.36.10.1.9 ipPolicyActivationAntiSpoofignList 1.3.6.1.4.1.81.36.10.1.10 ipPolicyActivationPBRList ipPolicyValidListEntID 1.3.6.1.4.1.81.36.11.1.1.1 ipPolicyValidListIfIndex 1.3.6.1.4.1.81.36.11.1.1.2 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 647 MIB objects in the BRIDGE-MIB.my file The following table provides a list of the MIBs in the BRIDGE-MIB.my file that are supported by the Branch Gateway and their OIDs: Object dot1dBaseBridgeAddress 1.3.6.1.2.1.17.1.1 dot1dBaseNumPorts 1.3.6.1.2.1.17.1.2 dot1dBaseType 1.3.6.1.2.1.17.1.3 Administering Avaya G430 Branch Gateway October 2013...
  • Page 648 1.3.6.1.2.1.17.2.11 dot1dStpBridgeMaxAge 1.3.6.1.2.1.17.2.12 dot1dStpBridgeHelloTime 1.3.6.1.2.1.17.2.13 dot1dStpBridgeForwardDelay 1.3.6.1.2.1.17.2.14 dot1dStpPort 1.3.6.1.2.1.17.2.15.1.1 dot1dStpPortPriority 1.3.6.1.2.1.17.2.15.1.2 dot1dStpPortState 1.3.6.1.2.1.17.2.15.1.3 dot1dStpPortEnable 1.3.6.1.2.1.17.2.15.1.4 dot1dStpPortPathCost 1.3.6.1.2.1.17.2.15.1.5 dot1dStpPortDesignatedRoot 1.3.6.1.2.1.17.2.15.1.6 dot1dStpPortDesignatedCost 1.3.6.1.2.1.17.2.15.1.7 dot1dStpPortDesignatedBridge 1.3.6.1.2.1.17.2.15.1.8 dot1dStpPortDesignatedPort 1.3.6.1.2.1.17.2.15.1.9 dot1dStpPortForwardTransitions 1.3.6.1.2.1.17.2.15.1.10 dot1dTpAgingTime 1.3.6.1.2.1.17.4.2 dot1dTpFdbAddress 1.3.6.1.2.1.17.4.3.1.1 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 649 1.3.6.1.4.1.81.7.9.3.2.1.3 chLntAgTrapsPermMngrId 1.3.6.1.4.1.81.7.9.3.7.1.1 chLntAgTrapsId 1.3.6.1.4.1.81.7.9.3.7.1.2 chLntAgTrapsEnableFlag 1.3.6.1.4.1.81.7.9.3.7.1.3 chLntAgMaxTrapsNumber 1.3.6.1.4.1.81.7.9.3.100 chGroupList 1.3.6.1.4.1.81.7.18 chLogFileGroupId 1.3.6.1.4.1.81.7.22.1.1 chLogFileIndex 1.3.6.1.4.1.81.7.22.1.2 chLogFileName 1.3.6.1.4.1.81.7.22.1.3 chLogFileAbsoluteTime 1.3.6.1.4.1.81.7.22.1.4 chLogFileMessage 1.3.6.1.4.1.81.7.22.1.5 chLogFileEncryptedMessage 1.3.6.1.4.1.81.7.22.1.6 genGroupId 1.3.6.1.4.1.81.8.1.1.1 genGroupSWVersion 1.3.6.1.4.1.81.8.1.1.2 genGroupKernelVersion 1.3.6.1.4.1.81.8.1.1.3 genGroupType 1.3.6.1.4.1.81.8.1.1.4 genGroupDescr 1.3.6.1.4.1.81.8.1.1.5 Administering Avaya G430 Branch Gateway October 2013...
  • Page 650 1.3.6.1.4.1.81.8.1.1.22 genGroupRedunRecovery 1.3.6.1.4.1.81.8.1.1.23 genGroupHWVersion 1.3.6.1.4.1.81.8.1.1.24 genGroupHeight 1.3.6.1.4.1.81.8.1.1.25 genGroupWidth 1.3.6.1.4.1.81.8.1.1.26 genGroupIntrusionControl 1.3.6.1.4.1.81.8.1.1.27 genGroupThresholdStatus 1.3.6.1.4.1.81.8.1.1.28 genGroupEavesdropping 1.3.6.1.4.1.81.8.1.1.29 genGroupMainSWVersion 1.3.6.1.4.1.81.8.1.1.30 genGroupMPSActivityStatus 1.3.6.1.4.1.81.8.1.1.31 genGroupBUPSActivityStatus 1.3.6.1.4.1.81.8.1.1.32 genGroupPrepareCounters 1.3.6.1.4.1.81.8.1.1.33 genGroupPortLastChange 1.3.6.1.4.1.81.8.1.1.34 genGroupIntPortLastChange 1.3.6.1.4.1.81.8.1.1.35 genGroupFaultMask 1.3.6.1.4.1.81.8.1.1.36 genGroupTypeName 1.3.6.1.4.1.81.8.1.1.37 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 651 1.3.6.1.4.1.81.8.1.1.52 genGroupCascadingDownFault 1.3.6.1.4.1.81.8.1.1.53 genGroupPortClassificationMask 1.3.6.1.4.1.81.8.1.1.54 genGroupPSUType 1.3.6.1.4.1.81.8.1.1.55 genGroupPolicyType 1.3.6.1.4.1.81.8.1.1.56 genPortGroupId 1.3.6.1.4.1.81.9.1.1.1 genPortId 1.3.6.1.4.1.81.9.1.1.2 genPortFunctionality 1.3.6.1.4.1.81.9.1.1.3 genPortType 1.3.6.1.4.1.81.9.1.1.4 genPortDescr 1.3.6.1.4.1.81.9.1.1.5 genPortAdminStatus 1.3.6.1.4.1.81.9.1.1.10 genPortFaultMask 1.3.6.1.4.1.81.9.1.1.14 genPortSWRdFault 1.3.6.1.4.1.81.9.1.1.15 genPortVLANMode 1.3.6.1.4.1.81.9.1.1.19 genPortAdminPermission 1.3.6.1.4.1.81.9.1.1.20 genPortName 1.3.6.1.4.1.81.9.1.1.21 genPortClassification 1.3.6.1.4.1.81.9.1.1.22 Administering Avaya G430 Branch Gateway October 2013...
  • Page 652 Branch Gateway and their OIDs: Object cmgHWType 1.3.6.1.4.1.6889.2.9.1.1.1 cmgModelNumber 1.3.6.1.4.1.6889.2.9.1.1.2 cmgDescription 1.3.6.1.4.1.6889.2.9.1.1.3 cmgSerialNumber 1.3.6.1.4.1.6889.2.9.1.1.4 cmgHWVintage 1.3.6.1.4.1.6889.2.9.1.1.5 cmgHWSuffix 1.3.6.1.4.1.6889.2.9.1.1.6 cmgStackPosition 1.3.6.1.4.1.6889.2.9.1.1.7 cmgModuleList 1.3.6.1.4.1.6889.2.9.1.1.8 cmgReset 1.3.6.1.4.1.6889.2.9.1.1.9 cmgHardwareFaultMask 1.3.6.1.4.1.6889.2.9.1.1.10.12 cmgHardwareStatusMask 1.3.6.1.4.1.6889.2.9.1.1.10.13 cmgModuleSlot 1.3.6.1.4.1.6889.2.9.1.1.11.1.1.1 cmgModuleType 1.3.6.1.4.1.6889.2.9.1.1.11.1.1.2 cmgModuleDescription 1.3.6.1.4.1.6889.2.9.1.1.11.1.1.3 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 653 1.3.6.1.4.1.6889.2.9.1.2.1.15 cmgQosControl 1.3.6.1.4.1.6889.2.9.1.2.2.1 cmgRemoteSigDscp 1.3.6.1.4.1.6889.2.9.1.2.2.2 cmgRemoteSig802Priority 1.3.6.1.4.1.6889.2.9.1.2.2.3 cmgLocalSigDscp 1.3.6.1.4.1.6889.2.9.1.2.2.4 cmgLocalSig802Priority 1.3.6.1.4.1.6889.2.9.1.2.2.5 cmgStatic802Vlan 1.3.6.1.4.1.6889.2.9.1.2.2.6 cmgCurrent802Vlan 1.3.6.1.4.1.6889.2.9.1.2.2.7 cmgPrimaryClockSource 1.3.6.1.4.1.6889.2.9.1.2.3.1 cmgSecondaryClockSource 1.3.6.1.4.1.6889.2.9.1.2.3.2 cmgActiveClockSource 1.3.6.1.4.1.6889.2.9.1.2.3.3 cmgRegistrationState 1.3.6.1.4.1.6889.2.9.1.3.1 cmgActiveControllerAddress 1.3.6.1.4.1.6889.2.9.1.3.2 cmgH248LinkStatus 1.3.6.1.4.1.6889.2.9.1.3.3 cmgH248LinkErrorCode 1.3.6.1.4.1.6889.2.9.1.3.4 cmgUseDhcpForMgcList 1.3.6.1.4.1.6889.2.9.1.3.5 cmgStaticControllerHosts 1.3.6.1.4.1.6889.2.9.1.3.6 Administering Avaya G430 Branch Gateway October 2013...
  • Page 654 1.3.6.1.4.1.6889.2.9.1.4.3.3.1 cmgVoipRemoteRetryOnFailure 1.3.6.1.4.1.6889.2.9.1.4.3.3.2 cmgVoipRemoteRetryDelay 1.3.6.1.4.1.6889.2.9.1.4.3.3.3 cmgVoipRemoteRsvpProfile 1.3.6.1.4.1.6889.2.9.1.4.3.3.4 cmgVoipLocalBbeDscp 1.3.6.1.4.1.6889.2.9.1.4.4.1.1 cmgVoipLocalEfDscp 1.3.6.1.4.1.6889.2.9.1.4.4.1.2 cmgVoipLocal802Priority 1.3.6.1.4.1.6889.2.9.1.4.4.1.3 cmgVoipLocalMinRtpPort 1.3.6.1.4.1.6889.2.9.1.4.4.1.4 cmgVoipLocalMaxRtpPort 1.3.6.1.4.1.6889.2.9.1.4.4.1.5 cmgVoipLocalRtcpEnabled 1.3.6.1.4.1.6889.2.9.1.4.4.2.1 cmgVoipLocalRtcpMonitorIpAddress 1.3.6.1.4.1.6889.2.9.1.4.4.2.2 cmgVoipLocalRtcpMonitorPort 1.3.6.1.4.1.6889.2.9.1.4.4.2.3 cmgVoipLocalRtcpReportPeriod 1.3.6.1.4.1.6889.2.9.1.4.4.2.4 cmgVoipLocalRsvpEnabled 1.3.6.1.4.1.6889.2.9.1.4.4.3.1 cmgVoipLocalRetryOnFailure 1.3.6.1.4.1.6889.2.9.1.4.4.3.2 cmgVoipLocalRetryDelay 1.3.6.1.4.1.6889.2.9.1.4.4.3.3 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 655 1.3.6.1.4.1.6889.2.9.1.4.5.1.12 cmgVoipEngineReset 1.3.6.1.4.1.6889.2.9.1.4.5.1.13 cmgVoipFaultMask 1.3.6.1.4.1.6889.2.9.1.4.5.1.14 cmgCcModule 1.3.6.1.4.1.6889.2.9.1.6.1.1.1 cmgCcPort 1.3.6.1.4.1.6889.2.9.1.6.1.1.2 cmgCcRelay 1.3.6.1.4.1.6889.2.9.1.6.1.1.3 cmgCcAdminState 1.3.6.1.4.1.6889.2.9.1.6.1.1.4 cmgCcPulseDuration 1.3.6.1.4.1.6889.2.9.1.6.1.1.5 cmgCcStatus 1.3.6.1.4.1.6889.2.9.1.6.1.1.6 cmgTrapManagerAddress cmgTrapManagerControl cmgTrapManagerMask cmgTrapManagerRowStatus cmgEtrModule 1.3.6.1.4.1.6889.2.9.1.7.1.1.1 cmgEtrAdminState 1.3.6.1.4.1.6889.2.9.1.7.1.1.2 cmgEtrNumberOfPairs 1.3.6.1.4.1.6889.2.9.1.7.1.1.3 cmgEtrStatus 1.3.6.1.4.1.6889.2.9.1.7.1.1.4 cmgEtrCurrentLoopDetect 1.3.6.1.4.1.6889.2.9.1.7.1.1.5 cmgDynCacStatus 1.3.6.1.4.1.6889.2.9.1.8.1 Administering Avaya G430 Branch Gateway October 2013...
  • Page 656 1.3.6.1.2.1.10.32.1.1.8 frDlcmiMaxSupportedVCs 1.3.6.1.2.1.10.32.1.1.9 frDlcmiMulticast 1.3.6.1.2.1.10.32.1.1.10 frDlcmiStatus 1.3.6.1.2.1.10.32.1.1.11 frDlcmiRowStatus 1.3.6.1.2.1.10.32.1.1.12 frCircuitIfIndex 1.3.6.1.2.1.10.32.2.1.1 frCircuitDlci 1.3.6.1.2.1.10.32.2.1.2 frCircuitState 1.3.6.1.2.1.10.32.2.1.3 frCircuitReceivedFECNs 1.3.6.1.2.1.10.32.2.1.4 frCircuitReceivedBECNs 1.3.6.1.2.1.10.32.2.1.5 frCircuitSentFrames 1.3.6.1.2.1.10.32.2.1.6 frCircuitSentOctets 1.3.6.1.2.1.10.32.2.1.7 frCircuitReceivedFrames 1.3.6.1.2.1.10.32.2.1.8 frCircuitReceivedOctets 1.3.6.1.2.1.10.32.2.1.9 frCircuitCreationTime 1.3.6.1.2.1.10.32.2.1.10 frCircuitLastTimeChange 1.3.6.1.2.1.10.32.2.1.11 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 657 The following table provides a list of the MIBs in the IP-MIB.my file that are supported by the Branch Gateway and their OIDs: Object ipForwarding 1.3.6.1.2.1.4.1 ipDefaultTTL 1.3.6.1.2.1.4.2 ipInReceives 1.3.6.1.2.1.4.3 ipInHdrErrors 1.3.6.1.2.1.4.4 ipInAddrErrors 1.3.6.1.2.1.4.5 ipForwDatagrams 1.3.6.1.2.1.4.6 ipInUnknownProtos 1.3.6.1.2.1.4.7 Administering Avaya G430 Branch Gateway October 2013...
  • Page 658 MIB objects in the Load12-MIB.my file The following table provides a list of the MIBs in the Load12-MIB.my file that are supported by the Branch Gateway and their OIDs: Object genOpModuleId 1.3.6.1.4.1.1751.2.53.1.2.1.1 genOpIndex 1.3.6.1.4.1.1751.2.53.1.2.1.2 genOpRunningState 1.3.6.1.4.1.1751.2.53.1.2.1.3 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 659 1.3.6.1.4.1.1751.2.53.1.2.1.15 genOpResetSupported 1.3.6.1.4.1.1751.2.53.1.2.1.16 genOpEnableReset 1.3.6.1.4.1.1751.2.53.1.2.1.17 genOpNextBootImageIndex 1.3.6.1.4.1.1751.2.53.1.2.1.18 genOpLastBootImageIndex 1.3.6.1.4.1.1751.2.53.1.2.1.19 genOpFileSystemType 1.3.6.1.4.1.1751.2.53.1.2.1.20 genOpReportSpecificFlags 1.3.6.1.4.1.1751.2.53.1.2.1.21 genOpOctetsReceived 1.3.6.1.4.1.1751.2.53.1.2.1.22 genAppFileId 1.3.6.1.4.1.1751.2.53.2.1.1.1 genAppFileName 1.3.6.1.4.1.1751.2.53.2.1.1.2 genAppFileType 1.3.6.1.4.1.1751.2.53.2.1.1.3 genAppFileDescription 1.3.6.1.4.1.1751.2.53.2.1.1.4 genAppFileSize 1.3.6.1.4.1.1751.2.53.2.1.1.5 genAppFileVersionNumber 1.3.6.1.4.1.1751.2.53.2.1.1.6 genAppFileLocation 1.3.6.1.4.1.1751.2.53.2.1.1.7 genAppFileDateStamp 1.3.6.1.4.1.1751.2.53.2.1.1.8 genAppFileRowStatus 1.3.6.1.4.1.1751.2.53.2.1.1.9 Administering Avaya G430 Branch Gateway October 2013...
  • Page 660 MIB objects in the WAN-MIB.my file The following table provides a list of the MIBs in the WAN-MIB.my file that are supported by the Banch Gateway and their OIDs: Object ds0BundleMemmbersList 1.3.6.1.4.1.6889.2.1.6.1.1.2.1.1 ds0BundleSpeedFactor 1.3.6.1.4.1.6889.2.1.6.1.1.2.1.2 ds1DeviceMode 1.3.6.1.4.1.6889.2.1.6.2.1.1 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 661 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.15 ifTableXtndBackupCapabilities 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.16 ifTableXtndBackupIf 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.17 ifTableXtndBackupEnableDelay 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.18 ifTableXtndBackupDisableDelay 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.19 ifTableXtndPrimaryIf 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.20 ifTableXtndCarrierDelay 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.21 ifTableXtndDtrRestartDelay 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.22 ifTableXtndDtrPulseTime 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.23 ifTableXtndLoadInterval 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.24 ifTableXtndInputRate 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.25 ifTableXtndOutputRate 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.26 ifTableXtndInputLoad 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.27 ifTableXtndOutputLoad 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.28 ifTableXtndReliability 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.29 ifTableXtndCacBBL 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.31 ifTableXtndCacPriority 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.32 Administering Avaya G430 Branch Gateway October 2013...
  • Page 662 Branch Gateway and their OIDs: Object sysDescr 1.3.6.1.2.1.1.1 sysObjectID 1.3.6.1.2.1.1.2 sysUpTime 1.3.6.1.2.1.1.3 sysContact 1.3.6.1.2.1.1.4 sysName 1.3.6.1.2.1.1.5 sysLocation 1.3.6.1.2.1.1.6 sysServices 1.3.6.1.2.1.1.7 snmpInPkts 1.3.6.1.2.1.11.1 snmpInBadVersions 1.3.6.1.2.1.11.3 snmpInBadCommunityNames 1.3.6.1.2.1.11.4 snmpInBadCommunityUses 1.3.6.1.2.1.11.5 snmpInASNParseErrs 1.3.6.1.2.1.11.6 snmpEnableAuthenTraps 1.3.6.1.2.1.11.30 snmpOutPkts 1.3.6.1.2.1.11.2 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 663 MIB objects in the OSPF-MIB.my file The following table provides a list of the MIBs in the OSPF-MIB.my file that are supported by the Branch Gateway and their OIDs: Object ospfRouterId 1.3.6.1.2.1.14.1.1 ospfAdminStat 1.3.6.1.2.1.14.1.2 ospfVersionNumber 1.3.6.1.2.1.14.1.3 ospfAreaBdrRtrStatus 1.3.6.1.2.1.14.1.4 Administering Avaya G430 Branch Gateway October 2013...
  • Page 664 1.3.6.1.2.1.14.2.1.6 ospfAreaLsaCount 1.3.6.1.2.1.14.2.1.7 ospfAreaLsaCksumSum 1.3.6.1.2.1.14.2.1.8 ospfAreaSummary 1.3.6.1.2.1.14.2.1.9 ospfAreaStatus 1.3.6.1.2.1.14.2.1.10 ospfLsdbAreaId 1.3.6.1.2.1.14.4.1.1 ospfLsdbType 1.3.6.1.2.1.14.4.1.2 ospfLsdbLsid 1.3.6.1.2.1.14.4.1.3 ospfLsdbRouterId 1.3.6.1.2.1.14.4.1.4 ospfLsdbSequence 1.3.6.1.2.1.14.4.1.5 ospfLsdbAge 1.3.6.1.2.1.14.4.1.6 ospfLsdbChecksum 1.3.6.1.2.1.14.4.1.7 ospfLsdbAdvertisement 1.3.6.1.2.1.14.4.1.8 ospfIfIpAddress 1.3.6.1.2.1.14.7.1.1 ospfAddressLessIf 1.3.6.1.2.1.14.7.1.2 ospfIfAreaId 1.3.6.1.2.1.14.7.1.3 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 665 1.3.6.1.2.1.14.7.1.18 ospfIfDemand 1.3.6.1.2.1.14.7.1.19 ospfIfAuthType 1.3.6.1.2.1.14.7.1.20 ospfIfMetricIpAddress 1.3.6.1.2.1.14.8.1.1 ospfIfMetricAddressLessIf 1.3.6.1.2.1.14.8.1.2 ospfIfMetricTOS 1.3.6.1.2.1.14.8.1.3 ospfIfMetricValue 1.3.6.1.2.1.14.8.1.4 ospfIfMetricStatus 1.3.6.1.2.1.14.8.1.5 ospfNbrIpAddr 1.3.6.1.2.1.14.10.1.1 ospfNbrAddressLessIndex 1.3.6.1.2.1.14.10.1.2 ospfNbrRtrId 1.3.6.1.2.1.14.10.1.3 ospfNbrOptions 1.3.6.1.2.1.14.10.1.4 ospfNbrPriority 1.3.6.1.2.1.14.10.1.5 ospfNbrState 1.3.6.1.2.1.14.10.1.6 ospfNbrEvents 1.3.6.1.2.1.14.10.1.7 ospfNbrLsRetransQLen 1.3.6.1.2.1.14.10.1.8 ospfNbmaNbrStatus 1.3.6.1.2.1.14.10.1.9 Administering Avaya G430 Branch Gateway October 2013...
  • Page 666 1.3.6.1.2.1.10.131.1.1.1.1.1 tunnelIfRemoteAddress 1.3.6.1.2.1.10.131.1.1.1.1.2 tunnelIfEncapsMethod 1.3.6.1.2.1.10.131.1.1.1.1.3 tunnelIfTOS 1.3.6.1.2.1.10.131.1.1.1.1.4 tunnelIfHopLimit 1.3.6.1.2.1.10.131.1.1.1.1.5 tunnelConfigLocalAddress 1.3.6.1.2.1.10.131.1.1.2.1.1 tunnelConfigRemoteAddress 1.3.6.1.2.1.10.131.1.1.2.1.2 tunnelConfigEncapsMethod 1.3.6.1.2.1.10.131.1.1.2.1.3 tunnelConfigID 1.3.6.1.2.1.10.131.1.1.2.1.4 tunnelConfigStatus 1.3.6.1.2.1.10.131.1.1.2.1.5 ipTunnelIfIndex 1.3.6.1.4.1.81.31.8.1.1.1 ipTunnelIfChecksum 1.3.6.1.4.1.81.31.8.1.1.2 ipTunnelIfKey 1.3.6.1.4.1.81.31.8.1.1.3 ipTunnelIfkeyMode 1.3.6.1.4.1.81.31.8.1.1.4 ipTunnelIfAgingTimer 1.3.6.1.4.1.81.31.8.1.1.5 ipTunnelIfMTUDiscovery 1.3.6.1.4.1.81.31.8.1.1.6 Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...
  • Page 667 Traps and MIBs Object ipTunnelIfMTU 1.3.6.1.4.1.81.31.8.1.1.7 ipTunnelIfKeepaliveRate 1.3.6.1.4.1.81.31.8.1.1.8 ipTunnelIfKeepaliveRetries 1.3.6.1.4.1.81.31.8.1.1.9 Administering Avaya G430 Branch Gateway October 2013...
  • Page 668 Traps and MIBs Administering Avaya G430 Branch Gateway October 2013 Comments? infodev@avaya.com...

  • Page 669: Index

    ............Avaya G250/G350/G450 Manager User Guide ..Accessing the Branch Gateway ......... Avaya G430 CLI Reference ........Active PMI ..............Avaya G430 Manager User Guide ......add nfas-interface ..........Avaya Services ............add port ............. authenticating logins with ASG ......
  • Page 670 ..........capture start .............. clear tcp syn-cookies counters ........capture stop .............. clear trunk-group ..........captured packets ............clear vlan ............CAS Remote Hold/Answer Hold-Unhold Access Code CLI ........– ..............Administering Avaya G430 Branch Gateway October 2013...
  • Page 671 ASG authentication ....copy auth-file usb ..........rtp-stat qos-trap-rate-limit ........copy capture-file ftp ........set logging session, object tracking ....copy capture-file scp ........set mgc list ............copy capture-file tftp ........set sls ..............Administering Avaya G430 Branch Gateway October 2013...
  • Page 672 Contact Closure Pulse Code ........composite-operation, access control list ....Contexts ..............composite-operation, DSCP table ..... Contexts example ............composite-operation, MSS configuration ....Continuous channel in VPN ........composite-operation, QoS list ......continuous-channel ......Administering Avaya G430 Branch Gateway October 2013...
  • Page 673 Date Format on Terminals ........copy tftp auth-file ............DCP stations data ............. copy tftp EW_archive ..........DCP telephones ............copy tftp module ............DCP/ANALOG Bearer Capability ......copy tftp startup-config ..........decrypted IPSec VPN packets ......... Administering Avaya G430 Branch Gateway October 2013...
  • Page 674 CLI logging, setting logging session conditions . configuring backup routing ......... CLI logging, viewing ........... dynamic IP ............configuring ............dynamic routing ..........determining DHCP option requests ....giving priority to VoIP ......... displaying configuration ........logging ..............Administering Avaya G430 Branch Gateway October 2013...
  • Page 675 Dialer Messages ............Communication Manager, Branch dialer modem-interface ........Gateways and Servers ......dialer order ............Quick Start for Hardware Installation for the Avaya dialer persistent ..........Branch Gateway G430 ......dialer persistent delay ........ domain-name ............ dialer persistent initial delay .......
  • Page 676 Frame relay traffic shaping ........failover ..............displaying configuration ........Fair VoIP queue ............frequency ............fair-queue-limit ............FTP ................fair-voip-queue ............FTP/TFTP used for upgrades ........Fast Ethernet interface ..........configuring PPPoE ..........Administering Avaya G430 Branch Gateway October 2013...
  • Page 677 IPHC method - RTP and TCP header compression, Insert ................. configuring UDP ports range ....Incoming Call Handling Treatment ..... methods ............. Installing and Upgrading the Avaya Branch Gateway overview ............. G430 .............. show ip rtp header-compression ......Integrated analog testing ....
  • Page 678 Loopback ..........ip distribution access-list-name ........ physical .............. ip distribution access-list-owner ........ Serial ..............ip domain list ............setting load calculation intervals ......ip domain lookup ........... switching ............. ip domain name-server-list ........Administering Avaya G430 Branch Gateway October 2013...
  • Page 679 ..............keepalive ICMP, see ICMP keepalive ...... IP stations data ............keepalive-icmp ..........ip tcp compression-connections ......keepalive-icmp failure-retries ......ip tcp header-compression ........keepalive-icmp interval ........IP telephones ............keepalive-icmp source-address ......Administering Avaya G430 Branch Gateway October 2013...
  • Page 680 Logging ............login authentication lockout ......Log file generation ............ login authentication min-password-digit-chars ..log file messages ............login authentication min-password-length .... Logging ..– login authentication min-password-lower-chars ..CLI commands ........... Administering Avaya G430 Branch Gateway October 2013...
  • Page 681 Communication Manager, Branch Modem dial backup ..... Gateways and Servers ......activating with object tracking ......Quick Start for Hardware Installation for the Avaya and dynamic CAC ........Branch Gateway G430 ......as backup interface ..........Master Configuration Key ........
  • Page 682 ............Next hops, see FIPS ..........owner, QoS list ............next-hop ............. next-hop-interface ........next-hop-ip ............next-hop-list .............. next-server ..............Packet sniffing ..... – – – nslookup ..............analyzing capture file ......... Administering Avaya G430 Branch Gateway October 2013...
  • Page 683 IACL ..... password ..............attaching policy lists to an interface ....Password authentication process ....... attaching QoS list to interface at ingress QoS list Password Authentication Protocol ..................Administering Avaya G430 Branch Gateway October 2013...
  • Page 684 ......rule criteria ............switchback ............sequence of device-wide policy list application .. port redundancy schemes ........sequence of policy list application ...... Ports ..... simulated packet properties ......alternate ............. Administering Avaya G430 Branch Gateway October 2013...
  • Page 685 CLI commands ........... Quick Start for Hardware Installation for the Avaya Priority Queuing ............Branch Gateway G430 ........Priority VoIP queuing ..........Quick Start for Hardware Installation for the Avaya G350 priority-queue ............ Branch Gateway ..........Privilege levels ............creating ..............
  • Page 686 Policy ........versions supported ..........Routing Information Protocol ........RIPv1 and RIPv2 differences ........see RIP .............. RMON ............... routing sources ............agent ..............Routing table ............. CLI commands ........... Administering Avaya G430 Branch Gateway October 2013...
  • Page 687 (bri) ........statistics summary report output ......set bearer-capability (ds1) ......... viewing configuration .......... set bit-rate ............viewing QoS traps in messages file ....set boot bank ............rtp-echo-port ............set busy-disconnect ..........Administering Avaya G430 Branch Gateway October 2013...
  • Page 688 ............set japan-disconnect ......... set port edge admin state ......set layer 1-stable ..........set port flowcontrol ........... set length ............set port level ............. set lldp re-init-delay ........... set port lldp ............Administering Avaya G430 Branch Gateway October 2013...
  • Page 689 ............set snmp timeout ............show auth-file info ..........set snmp trap ............show backup status ............ set spantree default-path-cost ........show boot bank ............. set spantree enable/disable ........show bri ..............Administering Avaya G430 Branch Gateway October 2013...
  • Page 690 ........show logging server condition ......show ip arp ............... show logging session condition ......show ip capture-list ........... show login authentication ........ show ip crypto-list ............. show map-class frame-relay ........Administering Avaya G430 Branch Gateway October 2013...
  • Page 691 ..........– show rtp-stat sessions ..........– show rtp-stat summary ........Avaya telephones supported in SLS ....show rtp-stat thresholds ........call processing not supported by SLS ....show rtp-stat traceroute ........call processing supported by SLS ......
  • Page 692 ..........preparing SLS data set, ISDN-BRI trunks data .. snmp-server host ......... provisioning data ..........snmp-server informs ..........registered state process ........snmp-server remote-user ......... states ..............snmp-server user ......... states, registered ..........Administering Avaya G430 Branch Gateway October 2013...
  • Page 693 RIP and OSPF ......see Logging ............types ..............system parameters data ........... station ............... subnet-mask ..........success-retries ..........suggest-key ............tcp destination-port ......support ............... tcp established ..........contact ..............TCP header compression ......... Administering Avaya G430 Branch Gateway October 2013...
  • Page 694 Trunk Group for Channel Selection ......Usernames ............– trunk-group ............... creating ..............tunnel checksum ............managing ............. tunnel destination ..........overview ............... tunnel dscp ............... USP WAN lines ............tunnel key ..............Administering Avaya G430 Branch Gateway October 2013...
  • Page 695 VoIP queuing ............typical installations, enabling continuous channel Weighted Fair VoIP Queuing .................... VoIP Queuing ............typical installations, full or partial mesh ....voip-queue ............typical installations, full solution ......voip-queue-delay ............Administering Avaya G430 Branch Gateway October 2013...
  • Page 696 Dialer interface as backup ........WFVQ ............... dynamic bandwidth reporting ......CLI commands ........... features .............. Weighted Fair VoIP Queuing ......ICMP keepalive ........... WFVQ, see Weighted Fair VoIP Queuing ....initial configuration ..........Administering Avaya G430 Branch Gateway October 2013...

Table of Contents