Avaya G250 Administration Manual
  1. Manuals
  2. Brands
  3. Avaya Manuals
  4. Gateway
  5. Media Gateway G250
  6. Administration manual

Avaya G250 Administration Manual

Media gateways
Hide thumbs Also See for G250:
1
2
Table Of Contents
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
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
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
Table of Contents

Advertisement

Quick Links

Download this manual See also: Technical White Paper, Maintenance Manual
Administration for the Avaya G250
and Avaya G350 Media Gateways
03-300436
Issue 5
June 2008

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the G250 and is the answer not in the manual?

Questions and answers

Related Manuals for Avaya G250

Summary of Contents for Avaya G250

  • Page 1 Administration for the Avaya G250 and Avaya G350 Media Gateways 03-300436 Issue 5 June 2008...
  • Page 2 Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya website: http://www.avaya.com/support...

  • Page 3: Table Of Contents

    Chapter 1: Introduction ......G250 and G350 contents .......
  • Page 4 Accessing the CLI via a modem connection to the S8300 ... Accessing Avaya IW ........
  • Page 5 Configuring the Primary Management Interface (PMI) ....Setting the PMI of the G250/G350......
  • Page 6 Configuring the MGC list ......Setting the G250/G350’s MGC......
  • Page 7 SLS service........Avaya phones supported in SLS ......
  • Page 8 Chapter 6: Configuring Ethernet ports ....Ethernet ports on the G250 ......
  • Page 9 Contents Optional TLVs ....... . . 802.1 TLVs (optional) ......LLDP configuration .
  • Page 10 Summary of E1/T1 ports configuration commands ... . . Configuring the Avaya MM342 USP WAN media module ... . USP default settings ......
  • Page 11 Contents Summary of USP port configuration commands ....Configuring PPP ........Summary of PPP configuration commands .
  • Page 12 Load detection ........How the G250/G350 detects a powered device (PD) ....
  • Page 13 Multi VLAN binding ....... . G250/G350 VLAN table ......
  • Page 14 Configuring QoS fault and clear traps ....Configuring the trap rate limiter ..... . . 14 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 15 Contents Analyzing RTP statistics output ......Viewing RTP statistics summary reports ....Viewing RTP session statistics .
  • Page 16 CNA tests ........Configuring the G250/G350 test plug for registration ....
  • Page 17 Contents Via-interface static route ......Permanent static route ......Discard route.
  • Page 18 Chapter 19: Configuring IPSec VPN ....549 G250/G350 R2.2 VPN capabilities......
  • Page 19 Contents Prerequisites ........IPSec VPN configuration overview ..... . Coordinating with the VPN peer .
  • Page 20 Summary of QoS list commands ......20 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 21 Chapter 23: FIPS....... 687 G250 image and interfaces ......
  • Page 22 Appendix A: Traps and MIBs ......743 G250/G350 traps ........
  • Page 23 Contents MIB files in the IF-MIB.my file ......MIB files in the DS0BUNDLE-MIB.my file ....MIB files in the RFC1406-MIB.my file .
  • Page 24 Contents 24 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 25: About This Book

    Downloading this book and updates from the web You can download the latest version of the Administration for the Avaya G250 and Avaya G350 Media Gateways from the Avaya website. You must have access to the Internet, and a copy of Acrobat Reader must be installed on your personal computer.

  • Page 26: Related Resources

    Maintenance Alarms for Avaya Communication Manager, 03-300430 Media Gateways and Servers Maintenance Commands for Avaya Communication Manager, 03-300431 Media Gateways and Servers Maintenance Procedures for Avaya Communication Manager, 03-300432 Media Gateways and Servers 26 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 27: Technical Assistance

    Toll fraud, call Avaya Toll Fraud Intervention at 1-800-643-2353 ● International For all international resources, contact your local Avaya authorized dealer for additional help. Trademarks All trademarks identified by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.

  • Page 28: Sending Us Comments

    E-mail, send your comments to: ● document@avaya.com Fax, send your comments to: ● 1-303-538-1741 Mention the name and number of this book, Administration for the Avaya G250 and Avaya G350 Media Gateways, 03-300436. 28 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 29: Chapter 1: Introduction

    – telephone exchange and data networking. The G250 and G350 each feature a VoIP engine, WAN router, and Power over Ethernet LAN switch. The G350 provides full support for legacy DCP and analog telephones.

  • Page 30: G250 And G350 Support Information

    ISDN BRI trunks ● G250 with WAN media module You can also add a plug-in WAN media module to the G250 for support of E1/T1 and USP WAN data lines. 30 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 31: G250 Available Models

    Analog model (G250-Analog). The G250-Analog includes four analog trunk ports, two ● analog line ports, a Fast Ethernet WAN port, and eight PoE LAN ports. BRI model (G250-BRI). The G250-BRI replaces three out of four of the G250’s fixed ● analog trunk ports with two ISDN BRI trunk ports.
  • Page 32 Introduction 32 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 33: Chapter 2: Configuration Overview

    39. Defining the Console interface The first thing you should do when configuring a new G250/G350 is to assign an IP address to the Console interface. It is not necessary to include a subnet mask. 1. Enter interface console to enter the Console context.

  • Page 34: Defining The Usb-Modem Interface

    Configuration overview Defining the USB-modem interface If you intend to use a USB modem to connect to the G250/G350, you should also assign an IP address to the USB-modem interface. It is not necessary to include a subnet mask. 1. Enter interface usb-modem to enter the USB-modem context.

  • Page 35: Configuration Using Cli

    Configuration using CLI Configuration using CLI You can use the Avaya G250/G350 Media Gateway CLI to manage the G250/G350. The CLI is a command prompt interface that enables you to type commands and view responses. For instructions on how to access the G250/G350 CLI, see Accessing the CLI on page 39.

  • Page 36: Saving Configuration Changes

    Configuration overview You can also use the Avaya G350 Manager to configure most features of the G250/G350. The Avaya G350 Manager is a GUI application. You can access the Avaya G350 Manager from Avaya Integrated Management software or from a web browser. Most of the commands that are available through the G250/G350 CLI are also available through the Avaya G350 Manager.

  • Page 37: Firmware Version Control

    If it becomes necessary to use the older version, you can enter set boot bank bank-x and then reset the G250/G350 to use the older version. This is particularly important when uploading new versions.
  • Page 38 Configuration overview 38 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 39: Chapter 3: Accessing The Avaya G250/G350 Media Gateway

    Chapter 3: Accessing the Avaya G250/G350 Media Gateway You can access the Avaya G250/G350 Media Gateway using the CLI, the IW, the GIW, the PIM, and the Avaya Communication Manager. You can manage login permissions by using and configuring usernames and passwords, and by configuring the G250/G350 to use SSH, SCP, RADIUS authentication, and the 802.1x protocol.

  • Page 40: Cli Contexts

    In the following example, the user enters the vlan 1 interface context and displays help for the bandwidth command. G350-001(super)# interface vlan 1 G350-001(super-if:VLAN 1)# bandwidth ? Bandwidth commands: ---------------------------------------------------------------------- Syntax: bandwidth <kilobytes size> <kilobytes size> : integer (1-10000000) Example: bandwidth 1000 40 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 41: Accessing Cli Via Local Network

    Accessing the CLI Accessing CLI via local network Access the CLI from a computer on the same local network as the Avaya G250/G350 Media Gateway by using SSH or, if telnet is active, any standard telnet program. Use the IP address of any G250/G350 interface for the host address.

  • Page 42: Accessing The Cli Via Modem

    PPP network connection from a modem at the remote location. You can use either a USB modem connected to the USB port on the front panel of the G250/G350 or a serial modem connected to the Console port on the front panel of the G250/G350. You must only use an approved Avaya serial cable.

  • Page 43: Accessing The Cli Via A Serial Modem

    Accessing the CLI via a serial modem 1. Connect a modem to the Console port on the front panel of the Avaya G250/G350 Media Gateway. Use an RJ-45 serial cable to connect the modem. 2. Make sure the Console port is properly configured for modem use.

  • Page 44: Accessing The Cli Via A Modem Connection To The S8300

    USB modem connected to one of the USB ports on the front panel of the S8300. The G250/G350 supports the Multitech MultiModem USB, MT5634ZBA-USB-V92. Note: In order to access the CLI via the S8300, the PMI of the G250/G350 must be Note: configured. See Configuring the Primary Management Interface (PMI) page 90.

  • Page 45: Access And Run The Avaya Iw Using A Laptop Computer

    Accessing Avaya IW Access and run the Avaya IW using a laptop computer 1. Connect a laptop computer to the Services port of the S8300, using a crossover cable. 2. Make sure the laptop is configured as described in Connecting a console device to the Services port on page 41.
  • Page 46 16. In the section Force password/key change on next login select no. 17. Click Submit. The system informs you the login is added successfully. 18. Click the Launch Installation Wizard link on the home page. The Avaya IW Overview screen appears. Figure 1: Avaya IW Overview screen...

  • Page 47: Accessing Giw

    G250/G350 that does not include an S8300 Server. You can use the GIW to perform initial configuration of the G250/G350 and to upgrade software and firmware. Specifically, you can perform the following tasks with the GIW:...

  • Page 48: Accessing Pim

    Accessing the Avaya G250/G350 Media Gateway Figure 2: GIW Overview screen For step-by-step instructions on how to configure the G250/G350 using the GIW, see Installing and Upgrading the Avaya G250 Media Gateway, 03-300434 or Installing and Upgrading the Avaya G350 Media Gateway, 03-300394.

  • Page 49: Accessing Avaya Communication Manager

    G250/G350 Media Gateway provides. Run the Avaya Communication Manager software on a server. There might be several servers on your network that can control the Avaya G250/G350 Media Gateway. Access Avaya Communication Manager on any server that is a Media Gateway Controller (MGC) for the Avaya G250/G350 Media Gateway.

  • Page 50: Managing Users Accounts

    Privilege level When you open the Avaya G350 Manager or access the 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 51: Configuring Usernames

    Avaya Services logins are deactivated. The logins are "rasaccess", "sroot", "init", "inads", and "craft". The login "dadmin" is reserved for an Avaya business partner remote services account, which can be defined for ASG authentication. For information about ASG authentication, refer...

  • Page 52: Managing Password Lockout And Disabling

    2. Enter copy running-config startup-config so that the new password will take effect. The new password you enter must match the password policies described in Managing password length and contents on page 51. 52 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 53: Displaying User Account Information

    Summary of user account CLI commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 3: User accounts CLI commands...

  • Page 54: Authenticating Service Logins With Access Security Gateway (Asg) Authentication

    1. Download the ASG authentication file for the gateway from the Authentication File System (AFS) application on the RFA information page to an FTP, SCP, or TFTP server, as described in Installing and Upgrading the Avaya G250 Media Gateway, 03-300434 and Installing and Upgrading the Avaya G350 Media Gateway, 03-300394.

  • Page 55: Replacing The Asg Authentication File

    Upgrading the Avaya G250 Media Gateway, 03-300434 or Installing and Upgrading the Avaya G350 Media Gateway, 03-300394. 4. For connection to Avaya Services via embedded VPN service, set up the VPN service for Services to connect. Replacing the ASG authentication file In case of any problems with the ASG authentication file, you can download a newer authentication file from the Authentication File System (AFS).
  • Page 56 USB mass storage device and source-filename is the full name and path of the authentication file. The authentication file is downloaded. You can view the download status using show download auth-file status. 56 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 57: 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 authenticated login. To reactivate, use login authentication services-logins. Set the time the gateway waits for user response to authentication requests before timing ●...

  • Page 58: Displaying Asg Authentication Information

    Use no login authentication lockout to return the lockout time and lockout attempt threshold to their default values (180 and 3). For example, to lockout Avaya Services access to the device for 360 seconds following five failed login attempts:...

  • Page 59: Summary Of Asg Authentication Cli Commands

    Summary of ASG authentication CLI Commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 4: ASG authentication CLI command Command Description copy auth-file ftp Upload the authentication file from the gateway to an...

  • Page 60: Ssh Protocol Support

    The G250/G350 supports two concurrent SSH users. Establishing an SSH session can be done by RSA authentication, or password authentication. To determine which of these ways is used on your G250/G350, enter show ip ssh. 60 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 61: Rsa Authentication Process

    ● called a fingerprint). The public key is always 16 bytes long. This public key is displayed. The G250/G350 sends the public key to the client computer. This public key is used by the ● client to encrypt the data it sends to the G250/G350. The G250/G350 decrypts the data using the private key.

  • Page 62: Summary Of Ssh Configuration Commands

    In addition to data transfer via an SSH session, the SSH protocol is used to support SCP for secure file transfer. When using SCP, the G250/G350 is the client, and an SCP server must be installed on the management station. After users are defined on the SCP server, the G250/G350 acts as an SCP client.

  • Page 63: Scp Configuration

    RADIUS authentication If your network has a RADIUS server, you can configure the G250/G350 to use RADIUS authentication. A RADIUS server provides centralized authentication service for many devices on a network. When you use RADIUS authentication, you do not need to configure usernames and passwords on the G250/G350.

  • Page 64: Changing Radius Parameters

    3. Use the set radius authentication server command to set the IP address of the primary or secondary RADIUS Authentication server. For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Changing RADIUS parameters...

  • Page 65: Summary Of Radius Authentication Configuration Commands

    LAN port and of preventing access to that port in cases where the authentication process fails. On the G350, you can enable 802.1x on the MM314 and MM316 media modules’ 10/100 Ethernet ports. On the G250, you can enable 802.1x on the eight Ethernet LAN PoE ports located on the G250’s front panel.

  • Page 66: Authentication Modes

    Supplicant. An entity (the host) at one end of a point-to-point LAN segment that is ● requesting authentication Authenticator. An entity (in this case the G250/G350) at the other end of a point-to-point ● LAN segment that facilitates authentication of the Supplicant Authentication (RADIUS) Server.

  • Page 67: 802.1X Modes

    LAN and WAN port on the chassis nor the uplink port in the MM314 (10/100/1G copper) and MM316 (10/100/1G copper) media modules support 802.1x. On the G250, you can enable 802.1x on the eight Ethernet LAN PoE ports located on the G250’s front panel. 802.1x is not supported on the G250-DCP model.
  • Page 68 When authentication is completed, the Supplicant receives a Permit/Deny notification. ● Authentication fails if: ● - the Supplicant fails to respond to requests from the Authenticator 68 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 69 - The user supplied incorrect login information 5. Enter set dot1x port-mode, followed by an authentication mode, to specify the mode of authentication for all G250/G350 ports: port-based (single supplicant) or MAC-based (multi supplicants). For example: G350-001(super)# set dot1x port mode mac-based-authentication If you specify MAC-based authentication, enter set dot1x max-supp-per-port, followed by a number from 1 to 8, to specify the supported number of supplicants per port.

  • Page 70: Manual Re-Authentication

    ● set the authenticator-to-supplicant retransmission timeout period (the time for the G250/G350 to wait for a reply from the Authenticated Station) for all ports on which 802.1x is enabled. 70 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 71: Displaying 802.1X Parameters

    Use the set dot1x lldp tlv command to specify that if LLDP is enabled, then upon ● 802.1x authentication of a supplicant, the G250/G350 transmits the port LLDP information (PVID, Port VLAN) in the LLDP packet sent to the supplicant.
  • Page 72 The time, in seconds, after which the port connection should be re-authenticated Server Timeout The amount of time, in seconds, the G250/G350 waits for a response from the RADIUS server 1 of 2 72 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 73 Supplicants the G250/G350 Authenticating The number of supplicants connected to the Supplicants G250/G350 being authenticated (not authenticated yet) 2 of 2 Use the show port dot1x supp-mac command to display all the port dot1x ● supplicant MAC addresses. To display the supplicant MAC addresses for a particular port, type the module and port numbers after the command.

  • Page 74: Summary Of 802.1X Configuration Commands

    --------- --------------- ------------------- 1d-80-00-00-00-00 Summary of 802.1x configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 9: 802.1x configuration commands Command Description Return the 802.1x values to default and disable the 802.1x...
  • Page 75 Set the authenticator-to-supplicant retransmission timeout period set dot1x (the time for the G250/G350 to wait for a reply from the supp-timeout Authenticated Station) for all ports on which 802.1x is enabled Globally enable or disable 802.1x authentication on all ports set...

  • Page 76: Special Security Features

    The G250/G350 includes a special recovery password. The purpose of the recovery password is to enable the system administrator to access the G250/G350 in the event that the regular password is forgotten. You can only use the recovery password when accessing the G250/G350 via a direct connection to the Console port or Services port.

  • Page 77: Summary Of Recovery Password Commands

    Enabling and disabling telnet access You can enable and disable the G250/G350’s ability to establish incoming and outgoing telnet connections, using the following commands. You can only use these commands when accessing the G250/G350 via a direct connection to the Console port.

  • Page 78: Summary Of Telnet Access Configuration Commands

    Accessing the Avaya G250/G350 Media Gateway Summary of Telnet access configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 11: Telnet access configuration commands Command Description Enable the G250/G350 to establish an incoming telnet...

  • Page 79: Configuring The Master Configuration Key

    Enabling SYN cookies The G250/G350 provides various TCP/IP services and is therefore exposed to a myriad of TCP/IP based DoS attacks. DoS (Denial of Service) attacks refers to a wide range of malicious attacks that can cause a denial of one or more services provided by a targeted host.

  • Page 80: Configuring Syn Cookies

    2. Copy the running configuration to the start-up configuration using the copy running-config startup-config command. 3. Reset the device using the reset command. SYN cookies are now enabled on the device. 80 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 81: Maintaining Syn Cookies

    Managed Security Services (MSS) Media Gateway IP interfaces and gateway applications such as WAN routers, PoE switches, and VPN devices can be at risk for DoS attacks. The G250/G350 identifies predefined or custom-defined traffic patterns as suspected attacks and generates SNMP notifications, referred to as Managed Security Services (MSS) notifications.

  • Page 82: Mss Reporting Mechanism

    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 83 3. Use the set mss-notification rate command to modify the MSS reporting rate, if necessary. The default is 300 seconds. The G250/G350 counts events for each DoS class for the duration of the interval. At the end of each interval, if the count of each class of DoS events surpasses a defined threshold, the G250/G350 generates an MSS notification, reporting on the event type, event parameters, and the number of occurrences.

  • Page 84: Dos Attack Classifications

    For all routable packets, the Gateway report reception of IP spoofed packets UNKNOW_L4_IP_PROTOCOL Packets with unknown (unsupported or administratively closed) protocol in IP packet with TO-ME interface as a destination UNATHENTICATED_ACCESS Failure to authenticate services 84 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 85: Defining Custom Dos Classifications

    Special security features Defining custom DoS classifications You can define custom DoS attack classifications using access control list (ACL) rules. ACL rules control which packets are authorized to pass through an interface. A custom DoS class is defined by configuring criteria for an ACL rule and tagging the ACL with a DoS classification label.
  • Page 86 8. Enter the configuration mode of the interface on which you want to activate the ACL. For example: G350-001(super)# interface vlan 203 9. Activate the configured ACL for incoming packets on the desired interface. For example: G350-001(super-if:vlan 203)# ip access-group 301 in Done! 86 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 87: Example

    Special security features Example The following example demonstrates the configuration of MSS notifications using ACL rules. In this example, smurf packets (ICMP packets that are sent to a limited broadcast destination) arriving at interface VLAN 203 are defined as a DoS attack to be reported in MSS notifications. //create and enter the configuration mode of access control list 301: G350-001(super)# ip access-control-list 301 //create and enter the configuration mode of ip rule 1:...

  • Page 88: Summary Of Mss Configuration Cli Commands

    Accessing the Avaya G250/G350 Media Gateway Summary of MSS configuration CLI commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 15: MSS configuration CLI commands Command Description Edit the specified composite operation. If the composite...

  • Page 89: Chapter 4: Basic Device Configuration

    Backup and restore the G250/G350 ● Defining an interface All interfaces on the G250 and G350 must be defined by the administrator, after installation of the G250/G350. 1. Use the interface command to enter the interface context. Some types of interfaces require an identifier as a parameter.

  • Page 90: Configuring The Primary Management Interface (Pmi)

    G250/G350 automatically becomes the PMI. You can subsequently assign any IP interface to be the PMI. The PMI is used as the IP address of the G250/G350 for the following management functions: Registration of the G250/G350 to an MGC ●...

  • Page 91: Summary Of Pmi Configuration Cli Commands

    ● defined in the startup configuration file If you use this command after you reset the G250/G350, both the Active and the Configured PMI should be the same IP address. 7. Use the following commands to configure other identification information: Use the set system contact command to set the contact information for the ●...

  • Page 92: Defining The Default Gateway

    Basic device configuration Defining the default gateway The G250/G350 uses a default gateway to connect to outside networks that are not listed on the G250/G350’s routing table. To define a default gateway, use the ip default-gateway command, followed by either the IP address or name (type and number) of the interface you want to define as the default gateway.

  • Page 93: Survivability And Migration Options

    Several options exist to minimize network disruption in the event that connectivity between the G250/G350 and the server or media gateway controller (MGC) is lost. MGC list. You must register the G250/G350 with at least one, and up to four, MGCs. The ●...

  • Page 94: Configuring The Mgc List

    291. Configuring the MGC list The G250/G350 must be registered with an MGC in order to provide telephone service. You can set the G250/G350’s MGC, and show the current MGC list used to determine the results. 94 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 95: Setting The G250/G350'S Mgc

    Configuring the Media Gateway Controller (MGC) Setting the G250/G350’s MGC Use the set mgc list command to set the G250/G350’s MGC. You can enter the IP addresses of up to four MGCs with the set mgc list command. The first MGC on the list is the primary MGC.

  • Page 96: Showing The Current Mgc List

    G250/G350’s search for the primary MGC and the other MGCs on its MGC list, respectively. 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.

  • Page 97: Accessing The Registered Mgc

    In this example, in the event of a connection loss with the registered MGC, the G250/G350 searches for the primary MGC on its MGC list for 20 minutes. If the G250/G350 does not establish a connection with the primary MGC within this time, it searches for the other MGCs on the list for a total of 40 minutes.

  • Page 98: Summary Of Mgc List Configuration Commands

    Basic device configuration Summary of MGC list configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 19: MGC list configuration commands Command Description Remove one or more MGCs from the MGC list...

  • Page 99: Dns Resolver Features

    - Dialer interface - Serial interface The most common application of this configuration is for connecting the G250/G350 to the Internet and getting the DNS server information from the ISP. Therefore, interfaces configured to automatically learn the DNS servers in the system are usually the FastEthernet with PPPoE interface and the Dialer interface.

  • Page 100: Configuring Dns Resolver

    3. Add a DNS server to the DNS servers list using the name-server command. Configure the following: Assign an index number that ranks the DNS server by priority ● Specify the IP address of the DNS server ● 100 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 101 Specify the domain name ● 6. Repeat Step 5 to configure additional domain names. You can configure up to six domain names. G350-001(config)# ip domain list 1 avaya.com Done! G350-001(config)# ip domain list 2 emea.avaya.com Done! 7. Optionally, configure the number of DNS query retries, using the ip domain retry command.
  • Page 102 Basic device configuration Important: If either DHCP Client or PPP are configured in the G250/G350, you do not need Important: to configure DNS resolver because the DNS resolver is enabled by default. In addition, the DHCP Client and PPP discover DNS servers automatically, so the list of DNS servers will include the automatically-learned DNS servers.

  • Page 103: Dns Resolver Configuration Example

    G350-001(config-name-server-list:1)# name-server 1 1.1.1.1 Done! G350-001(config-name-server-list:1)# name-server 2 2.2.2.2 Done! G350-001(config-name-server-list:1)# name-server 3 3.3.3.3 Done! G350-001(config-name-server-list:1)# exit G350-001(config)# ip domain list 1 support.avaya.com Done! G350-001(config)# ip domain list 2 global.avaya.com Done! G350-001(config)# ip domain list 3 avaya.com Done! G350-001(config)# ip domain retry 4...

  • Page 104: Clearing Dns Resolver Counters

    You can also enable logging messages to a log file or a Syslog server. For a full Note: description of logging on the G250/G350, see Configuring logging on page 229. 104 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 105: Summary Of Dns Resolver Configuration Commands

    DNS resolver Summary of DNS resolver configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 20: DNS resolver configuration commands Root level Command Description command Clear the DNS resolver’s statistics counters...

  • Page 106: Viewing The Status Of The Device

    Basic device configuration Viewing the status of the device To view the status of the Avaya G250/G350 Media Gateway, use the following commands:For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Enter show faults to view information about currently active faults.

  • Page 107: Summary Of Device Status Commands

    Viewing the status of the device Enter show temp to view the temperature of the G250/G350 CPU. This command also ● displays the high and low temperatures that will trigger a temperature warning. Use the show timeout command to display the amount of time in minutes the terminal ●...

  • Page 108: Software And Firmware Management

    ● File transfer The Avaya G250/G350 Media Gateway can be a client for the FTP and TFTP protocols. Use either a USB device or the FTP or TFTP protocols to transfer files between the Avaya G250/G350 Media Gateway and other devices. You can use file transfer to: Install software and firmware upgrades on the G250/G350 ●...

  • Page 109: Software And Firmware Upgrades

    To use FTP/TFTP file transfer, you need to have an FTP server or TFTP server on your network. Note: If you use an FTP server, the G250/G350 prompts you for a username and Note: password when you enter a command to transfer a file. Also, when opening an FTP connection to the S8300, all anonymous FTP file transfers are restricted to the /pub directory.

  • Page 110: Upgrading Software And Firmware Using Ftp/Tftp

    Loading firmware from the non-default bank You can use the ASB button on the G250/G350 front panel to load firmware from a bank other than the default bank during startup: 1. Press and hold the reset button.

  • Page 111: Upgrading Software And Firmware Using A Usb Mass Storage Device

    Use the copy tftp SW_imageB command to upgrade the G250/G350 firmware into ● Bank B from a TFTP server. Use the copy tftp EW_archive command to upgrade the Java applet for Avaya G350 ● Manager software from a TFTP server.
  • Page 112 Basic device configuration 3. Remove the USB storage device from the PC, and insert it in the G250/G350 USB port. 4. Copy the software or firmware file(s) to the G250/G350 using one of the following commands: Use the copy usb SW_imageA command to upgrade the G250/G350 firmware into ●...

  • Page 113: Uploading Software And Firmware From The Gateway

    Copy media modules’ firmware files to the MM subdirectory. d. Copy IP phone firmware files to the IPPHONE subdirectory. 4. Remove the USB mass storage device from the PC, and insert it in the G250/G350 USB port. 5. Enter restore usb usbdevice0 backup-name, where backup-name is the root directory path and name on the USB mass storage device.

  • Page 114: Summary Of Software And Firmware Management Commands

    A Call Detail Recording (CDR) file ● dhcp-binding. The DHCP binding file ● Summary of software and firmware management commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 22: Software and firmware management CLI commands Command Description...
  • Page 115 Upgrade the startup configuration file from the USB mass copy usb storage device startup-config Upgrade the G250/G350 firmware into Bank A or into Bank B, copy usb SW_image from the USB mass storage device List all files in the USB mass storage device connected to the...

  • Page 116: Backing Up And Restoring The G250/G350 Using A Usb Mass Storage Device

    Backing up and restoring the G250/G350 using a USB mass storage device The G250/G350 USB port supports a USB flash drive and a USB externally powered hub. The port also supports USB 2.0 high speed (480 Mbits/sec) for faster file transfer between the media gateway and USB mass storage devices.

  • Page 117: Backing Up Administration And Configuration Files Using A Usb Mass Storage Device

    Back up the gateway regularly to a USB mass storage device. This backup can be very helpful in restoring the gateway’s configuration if it becomes faulty, or in restoring the entire gateway. 1. Connect a USB mass storage device to the G250/G350 USB port. 2. Type s to commit the current configuration to NVRAM.

  • Page 118: Restoring Backed Up Configuration And Administration Files To A Gateway Using A Usb Mass Storage Device

    Restoring backed up configuration and administration files to a gateway using a USB mass storage device 1. Make sure you have a backup of the G250/G350 on a USB mass storage device. Refer to Backing up administration and configuration files using a USB mass storage device page 117.

  • Page 119: Replicating A G250/G350 Using A Usb Mass Storage Device

    Table 24, to enable a successful restore. 1. Make sure you have a backup of the faulty G250/G350 on a USB mass storage device. Refer to Backing up administration and configuration files using a USB mass storage device on page 117.
  • Page 120 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 121 Software and firmware management Table 24: Backup file and directory naming convention on a USB mass storage device Root directory Sub-directory Files Comments Customer-specific VoIP audio.bin parameters VPN license file vpn_license.cfg Authentication file auth-file.cfg Gateway image g350_sw_24_21_1.bin g250_sw_24_21_1.bin Embedded web image g350_emweb_3_0_5.bin (for G350 only) IP phone scripts and...

  • Page 122: Replacing/Adding/Upgrading Media Modules Using A Usb Mass Storage Device

    Installing and Upgrading the Avaya G250 Media Gateway, 03-300434 or Installing and Upgrading the Avaya G350 Media Gateway, 03-300394. 17. Update the S8300 on the new G250/G350 with the serial number of the new gateway, otherwise the gateway is not able to register in the Avaya Communication Manager. See Administrator’s Guide for Avaya Communication Manager, 555-233-506.

  • Page 123: Additional Usb Commands

    Use the show usb command to display the USB devices connected to the gateway. ● Summary of USB backup, restore, and replication commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 25: USB backup, restore, and replication CLI commands...

  • Page 124: Backing Up And Restoring Configuration Files

    A configuration file is a data file that contains a complete set of configuration settings for the Avaya G250/G350 Media Gateway. You can use configuration files to back up and restore the configuration of the G250/G350. You can back up either the running configuration or the startup configuration to the server as a configuration file.

  • Page 125: Backing Up/Restoring A Configuration File Using Ftp/Tftp/Scp

    Use the copy ftp startup-config command to restore a configuration file from an ● FTP server. The configuration file becomes the startup configuration on the G250/G350. Use the copy tftp startup-config command to restore a configuration file from a ●...

  • Page 126: Summary Of Configuration File Backup And Restore Commands

    Basic device configuration Summary of configuration file backup and restore commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 26: Configuration file backup and restore CLI commands Command Description Download a G250/G350 configuration file from an FTP server to...

  • Page 127: Listing The Files On The Avaya G250/G350 Media Gateway

    Listing the files on the Avaya G250/G350 Media Gateway Use the dir command to list all G250/G350 files. When you list the files, you can see the version numbers of the software components. The dir command also shows the booter file, which cannot be changed.
  • Page 128 Basic device configuration 128 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 129: Chapter 5: Configuring Standard Local Survivability (Sls)

    Configuring SLS on page 88. Media module compatibility with SLS SLS works on the G250/G350 and its media modules only if they satisfy the minimum hardware vintage and firmware version requirements listed in Table Table 17: G250/G350 media module firmware version required to support SLS...

  • Page 130: Sls Service

    ISDN BRI/PRI trunk interfaces supported on the G250-DS1, G250-BRI, and G350 ● gateways Non-ISDN digital DS1 trunk interfaces supported on the G250-DS1 and G350 gateways ● Outbound dialing through the local PSTN (local trunk gateway) from analog, DCP, and IP ●...

  • Page 131: Avaya Phones Supported In Sls

    Auto fallback to primary MGC ● IP station registration ● Avaya phones supported in SLS Table 29: Avaya phones supported in SLS Analog 2500 2402 4601 2410 4602 2420 4602sw 6402 4610sw 6402D 4612 6408 4620 6408+ 4620sw (default) 6408D (default)

  • Page 132: Call Processing In Sls Mode

    The Spice (96xx) family and Sage (16xx) family of IP phones are not directly referenced in the G250/G350 CLI. When you administer these phones via the CLI, use the following mapping: Table 30: Mapping Avaya 96xx and 16xx IP phones for CLI administration...

  • Page 133: Call Processing Not Supported By Sls

    Important: SLS permits 911 calls, but the specific location information is not transmitted to Important: the Public Service Answering Point (PSAP). Only the general trunk-identifying information is transmitted. Emergency personnel will have a general location associated with the trunk (for example, a building address), but nothing more specific (for example, a room or office number).

  • Page 134: Provisioning Data

    Connection Preserving Failover/Failback for H.248 Gateways ● Provisioning data SLS requires that the G250/G350 has connected to an MGC at least once and has received provisioning information, including: Avaya Communication Manager port information sent through the H.248 control channel: ●...

  • Page 135: Pim Configuration Data

    RAM (NVRAM) on the G250/G350. After the initial data collection, PIM retains a copy of the data set for each G250/G350. This set is compared with subsequent data sets to determine if anything has...

  • Page 136: Entering Sls Mode

    Using PIM to manage SLS administration on the gateway on page 151. If PIM is unavailable, the SLS data set can be manually configured in the G250/G350 CLI. For information on configuring SLS, both manually and via PIM, see Configuring SLS on page 146.

  • Page 137: Teardown

    The G250/G350 closes the SLS socket after maintenance determines that it has ● completed an H.248 registration with the primary MGC. SLS determines that it needs to unregister with the G250/G350 due to internal error ● conditions. Teardown state activities 1.

  • Page 138: Multiple Call Appearances In Sls Mode

    User A, which is sent to the first call appearance. In this situation, a subsequent inbound call to User A will be denied (busy) because the first and third call appearances are in use, and the second call appearance is only available for outbound calls. 138 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 139: Hold In Sls Mode

    Pressing the held Call Appearance button ● Analog phones Newer analog phones (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 phone ●...

  • Page 140: Call Transfer In Sls Mode

    Does not support E-911 calls ● Does not support the Conference button on any phone ● Does not support trunk-to-trunk transfer (for example, for voice messaging) ● 140 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 141 Transferring an established call from an analog phone 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 142: Using Contact Closure In Sls Mode

    Interdigit timing rules apply to the contact closure feature, so if you pause too long during ● the FAC key sequence, the feature times out. Call appearances are not released (available for calls) until you hang up. ● 142 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 143: Ip Softphone Shared Administrative Identity In Sls Mode

    The SLS mode supports shared administrative identity with the Avaya Softphone application, but requires specific station administration. 1. Access the CM administrative SAT interface. For instructions on accessing the Avaya Communication Manager through the G250/G350, see Accessing the registered MGC page 97.

  • Page 144: Sls Logging Activities

    NVRAM or directed to an external server for later processing. It includes data for: Merged outgoing Trunk Access Codes (TACs), indicating successfully completed dialing ● Successfully completed ARS calls, as shown in Figure 6 ● 144 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 145: Example Of Cdr Log Entries And Format

    Note: The Syslog information is stored in a memory file that is configured as a FIFO Note: with a length of 50 KB. Once the last entry in the memory is full, the newest log event overwrites the oldest entry. This provides for a storage of 667 call records that may be saved during SLS operation.

  • Page 146: Example Of Cdr Log With Contact Closure

    Configuring SLS SLS is included as part of the resident gateway firmware package that is installed as part of the G250/G350 gateway firmware upgrade. However, for SLS to function correctly, the following conditions must be met: Avaya Communication Manager must be configured for SLS and Auto Fallback. For ●...

  • Page 147: Configuring Communication Manager For Sls

    Using PIM to manage SLS administration on the gateway on page 151. If PIM is not available, the G250/G350 can be manually configured for SLS and Auto Fallback via the CLI. See Using the CLI to manually configure SLS administration on the gateway on page 157.
  • Page 148 11. Verify the following fields: Name field (20 characters maximum) must match the administered name of the ● gateway (see Step 2 of Configuring the SLS data through the CLI on page 173). 148 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 149 Configuring SLS Max Survivable IP Ext field only appears when the Type field is G250 or G350. The ● current maximum product limits enforced by the SLS gateway’s firmware module are: G250. A limit of 12 ● G350. A limit of 72 ●...
  • Page 150 5. Emergency: Users can only dial the emergency external number Survivable Trunk Dest? Enables stations to receive/not receive incoming trunk calls ● in survivable mode (default is receive). PIM extracts the Communication Manager 150 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 151: Using Pim To Manage Sls Administration On The Gateway

    Communication Manager translations (dial plan analysis and destination routing instructions) and delivers them to the G250/G350. If PIM is not available, this translation subset (the SLS data set) can be created manually, using the procedure described in...
  • Page 152 The Add ARS Entry option may be used to create/edit a maximum of 30 ARS dial pattern entries. 9. If this gateway has not been previously provisioned, click Add ARS Entry to open the ARS Entry page (Figure 10). 152 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 153 Configuring SLS Figure 10: SLS ARS Entry page 10. Use the SLS ARS Entry page (Figure 10) to administer an Automatic Route Selection in SLS. Refer to Table Table 32: SLS ARS Entry page field options Field Description Dialed String The maximum length of the dialed string is 18 characters.
  • Page 154 (for example, a building address), but nothing more specific (for example, a room or office number). Also, if a 911 call disconnects for any reason, emergency personnel cannot reliably call the originator back. 154 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 155 Configuring SLS 11. Use the SLS Update Schedule page (Figure 11) to administer up to six SLS updates per day. Figure 11: SLS Update Schedule page a. Check the Enable SLS Updates box. b. Set as many as six Daily Updates. Note: The Daily Updates must be at least four hours apart.

  • Page 156: Enabling And Disabling Sls

    PIM wizard screens. Enabling and disabling SLS To enable SLS on the G250/G350, enter set sls enable. The G250/G350 responds with the message Survivable Call Engine is enabled. To disable SLS on the G250/G350, enter set sls disable. The G250/G350 responds with the message Survivable Call Engine is disabled.

  • Page 157: Activating Changes In Sls

    The SLS is enabled on the G250/G350 through its CLI ● S8300 is not serving as an LSP ● G250/G350 is not subtending to another external server (including ESS or another LSP in ● another gateway) Issue 5 June 2008...

  • Page 158: Planning And Preparing The Sls Data Set

    Configuring Standard Local Survivability (SLS) Planning and preparing the SLS data set It is recommended to plan the SLS coverage and gather information from Avaya Communication Manager before creating the SLS administration data set at the 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 159 Configuring SLS Collecting analog stations data 1. At the SAT, enter list media-gateway to display a list of administered gateways. 2. Look for one of the following supported gateways in the Type field: G250/G250-BRI/G250-DCP/G250-DS1 ● G350 ● 3. Once you know the media gateway of interest, match the gateway model with the analog...
  • Page 160 The system displays the extension number assigned to the port. 5. Once you know the extension, enter display station extension to display the Station form for this extension. 160 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 161 Configuring SLS 6. Gather the necessary information from Table Table 37: DCP station form data to assemble for SLS Page Field Name Notes Extension Port The port address correlates the DCP stations that belong to a particular media gateway. If the port ID includes the media gateway number, then it is accepted.
  • Page 162 Extension Security Code (IP only) This value is the shared secret between Communication Manager and the media gateway used for the registration of the IP endpoint 1 of 2 162 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 163 CM to look for physical port matches in the various trunk SAT forms in order to discover what translation information is needed. 4. Identify the analog trunk ports: G250. Ports V305, V306 ● G250-BRI. Ports V302, V303 ●...
  • Page 164 This value is only necessary if the Dial Access? field is set to y. If that field is set to n, the TAC value is not pushed down to the media gateway. 1 of 3 164 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 165 Configuring SLS Table 39: Trunk group data to assemble for SLS (continued) Page Field Name Notes Port There may be more than one port within a trunk group definition that pertains to a given media gateway Digit Treatment This only applies for DID analog trunks or for DS1 tie trunks.
  • Page 166 Field Name Notes Name Descriptive name often of the Service Provider or destination of the DS1 facility Bit-Rate Selects the maximum transmission rate of the DS1 facility 1 of 2 166 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 167 Configuring SLS Table 40: DS1 circuit pack data to assemble for SLS (continued) Page Field Name Notes Signaling Mode Selects the signaling method deployed on the given DS1 facility Channel E1 interface for ETSI and QSIG require sequential Numbering encoding from 1 to 30 This field appears when Signaling Mode = isdn-pri Bit Rate = 2.048...
  • Page 168 Trunk Board This is needed only if the Associated Signaling is set to no. This does not apply to SLS on the G250. Specifies the gateway port ID where the D-channel is located. For the gateways, the first component is the three digit gateway number, followed by a ‘v’, and one numeric...
  • Page 169 Configuring SLS Table 42: ISDN-BRI administration data to assemble for SLS (continued) Page Field Name Notes Side QSIG glare handling, when the interface field is peerSlave Country Protocol Specifies the Layer 3 signaling protocol used by the country-specific service provider DCP/Analog Bearer Sets the Information Transfer capability in the Capability...
  • Page 170 3. Once you have determined the media gateway of interest, note its IP-Network-Region. 4. At the SAT, enter display ip-network-region n, where n is the gateway’s administered IP-Network-Region. Read the Codec-set field value from the IP Network Region form. 170 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 171 Configuring SLS 5. At the SAT, enter display ip-codec-set n, where n is the Codec-set field value from the IP Network Region form. The report lists the supported codes in the Audio Codec field (summarized in Table 44). Note: SLS only supports G.711 mu/A-law. Note: 6.
  • Page 172 1. At the SAT, enter display inc-call-handling-trmt trunk-group n, where n is an administered trunk group. 2. For each entry, read the values of the following fields (see Table 46): 172 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 173: Configuring The Sls Data Through The Cli

    Configuring SLS Called Number ● Called Length ● ● Insert ● Table 46: Incoming call handling data to gather for SLS CM Form Page Field Name Notes Incoming Call Called Number Dial string entry that is used to Handling Treatment match a pattern on inbound trunk calls Incoming Call...
  • Page 174 SLS administration of the gateway. 5. If you want to change the maximum allowable IP registrations from the default, enter set max-ip-registrations n, where n is from 1 to 12 for the G250 and from 1 to 72 for the G350.
  • Page 175 * ana-imm1t2l is an integrated module and does not require configuration. 9. Administer the station information. Refer to Administering Station parameters page 177. 10. Administer DS1 trunks as required (for G250-DS1 and G350 only). Refer to Administering DS1 parameters on page 181.
  • Page 176 SLS by entering set sls disable, and then re-enable it by entering set sls enable. This will cause the SLS application to resynchronize its administrative database with the gateway's CLI command database. 176 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 177: Administering Station Parameters

    Configuring SLS 21. At the gateway command prompt, enter copy running-config startup-config to save the changes. Administering Station parameters 1. At the gateway command prompt, enter station extension class to enter a second-level sub-context to administer each phone that you want covered by SLS. In this command, extension is a 1-13 digit numeric string that may begin with 0, and class is analog, dcp, or ip.
  • Page 178 Note: This command is only required for stations that support physical media module Note: ports. If the class is ip (set in Step 1), you cannot run this command. 178 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 179 Examples set port v305 sets the previously-administered analog station "1234567" to the ● fifth physical analog station port on the G250-Analog gateway’s media module. set port v401 sets the previously-administered dcp station "1234567" to the first ● physical DCP station port on the G250-DCP gateway’s media module.
  • Page 180 ‘aaa.bbb.ccc.ddd’ Note: For currently-registered IP phones or IP Softphones, the IP address is displayed. Note: 11. Enter exit to leave the station context in SLS. 180 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 181: Administering Ds1 Parameters

    Configuring SLS Administering DS1 parameters 1. Enter ds1 slot-address, where slot-address is any permitted port. The command line prompt changes to super-sls/ds1-<port-address>. If you want to remove the ds1 trunk from the SLS administration, enter exit to leave the second-level ds1 context and return to the (super-sls)# context, and then enter clear ds1 slot-address.
  • Page 182 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) 1 of 2 182 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 183 Configuring SLS Table 50: ISDN Layer 3 country codes (continued) Country Country Code Germany (ETSI) Czech Republic Russia Argentina Greece China Hong Kong Thailand Macedonia Poland Brazil Nordic countries South Africa ETSI (no use of RESTART message) etsi QSIG qsig 2 of 2 10.
  • Page 184 11. If the DS1 link is employed with ISDN, enter set bearer-capability bearer to set the Information Transfer Rate field of the Bearer Capability IE, where bearer is one of the following values: 3khz. 3.1 kHz audio encoding ● speech. Speech encoding ● 184 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 185: Administering Bri Parameters

    Configuring SLS 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: alaw. A-law companding ● ulaw.
  • Page 186 (stable) between calls. Some European countries require that the physical layer is deactivated when there is no active call. 186 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 187: Administering Trunk-Group Parameters

    Configuring SLS 15. Enter show to check the BRI administration. The report lists the BRI parameters. For example: Name = BRI-SLS1 Interface Side Country Bearer Compand Endpt-Init Layer1-Stable --------- ---- -------- ------ ------- ---------- ------------- v401 user country1 speech ulaw Dir-NumberA Dir-NumberB Spid-A Spid-B ----------- ----------- -------------- --------------...
  • Page 188 Configuring Standard Local Survivability (SLS) The maximum limits for a given trunk type are defined by the built-in ports on the G250 family members and are defined by the slot-configuration assignment for the G350. The maximum number of ports allowed per interface module is defined in...
  • Page 189 Configuring SLS Table 53: G350 SLS group type assignments (continued) Group type Media module Number of Description of trunks that may be ports/channels assigned loop-start MM714 Ports 5, 6, 7, 8 ground-start MM714 Ports 1, 2, 3, 4 MM716 Ports 1-24 MM720 Eight physical ports, each offering B1 and B2 channels...
  • Page 190 Configuring Standard Local Survivability (SLS) 4. Enter add port module port sig-group to specify the port (for G250/G350) or media module port (for G350) that is compatible with the device and/or media module (see Table 54 for G250 analog trunks,...
  • Page 191 5,6,7,8 ground-start MM714 ports 1,2,3,4 MM716 ports 1-24 2 of 2 Table 56: Trunk port values in SLS trunk-group context for the G250 (Digital Trunks) G250 Model BRI Trunks DS1 Trunks group-type parameter is bri group-type parameter is: t1-isdn ●...
  • Page 192 V304 administers an analog loop-start trunk through port V304 on either ● the G250-Analog or the G250-DCP. Example add port v401 adds a BRI trunk for the first physical port of the G250-BRI’s media ● module to a trunk group using one B-channel of the BRI link. Note: You cannot mix BRI and PRI trunks within the same trunk group.
  • Page 193 Configuring SLS wink-immediate ● wink-auto ● ● immediate-immediate ● auto-auto ● auto-wink 7. For an analog DID trunk group or DS1 non-ISDN tie trunk group, enter set digit-treatment digit-treat, where digit-treat can be one of the following values: blank (use this value to prevent any absorb or insert digit treatment from being ●...
  • Page 194 The number is not sent to the network for incoming or outgoing calls ● yes. The number is sent to the network for incoming or outgoing calls ● restricted. The number is sent to the network as ”Presentation restricted” ● 194 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 195 Configuring SLS Note: For this release, specify method as no, since sending a Calling Party Number is Note: a future feature. 17. For ISDN trunks, enter set numbering-format type to specify the numbering plan for this trunk in Standard Local Survivability (SLS). The numbering plan encodes the Numbering Plan Indicator and Type of Number fields in the Calling/Connected Party Number IE in the ISDN protocol.

  • Page 196: Administering Signaling-Group Parameters

    Configuring Standard Local Survivability (SLS) The following example shows a G250-BRI that has all four trunk members assigned to ● one trunk-group: Group Type Dial Supervision Treat Insert ----- ---------- ------ ---- ------------------- ------- ------ Name = Willow Street 2...

  • Page 197: Administering Dial-Pattern Parameters

    Configuring SLS 4. If your trunk is provisioned without a D-channel for signaling, enter set associated-signaling no to use Non-Facility Associated Signaling (NFAS). Note: NFAS is primarily a feature for ISDN-T1 connections offered by service providers Note: in North America and Hong Kong. However, it can also be used on private-network connections, and in that context it is possible to set up NFAS using ISDN-E1 interfaces.
  • Page 198 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 ------------------ ------ ---- ----- ---------------------- 5381000/n locl 1/303 5385000/n locl 1/720 198 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 199: Administering Incoming-Routing Parameters

    Configuring SLS 10. Enter exit to leave the dial-pattern context in SLS. Administering incoming-routing parameters The incoming-routing parameters are useful for mapping DNIS numbers directly into the station extension numbers when the Service Provider's DNIS plan does not directly reflect the station extension number length used in the gateway’s dial plan.

  • Page 200: Summary Of Sls Configuration Commands

    ----- 5381000 enbloc 5381001 enbloc Summary of SLS configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 58: SLS CLI command hierarchy Root Level First Level Context Second Level Context Description...
  • Page 201 Configuring SLS Table 58: SLS CLI command hierarchy (continued) Root Level First Level Context Second Level Context Description Commands Commands Commands set interface-companding Set the interface to agree with the companding method used by the far-end of the DS1 circuit for SLS mode set layer1-stable Determine whether or not to keep...
  • Page 202 SLS show List all dial-pattern SLS parameters Administer DS1 trunks for SLS set bearer-capability Set the Information Transfer Rate field of the Bearer Capability IE in 3 of 9 202 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 203 Configuring SLS Table 58: SLS CLI command hierarchy (continued) Root Level First Level Context Second Level Context Description Commands Commands Commands set bit-rate Set the maximum transmission rate for the DS1 facility in SLS set channel-numbering Select the channel-numbering method for B-channels on an E1 interface in SLS set connect Specify the equipment at the far-end...
  • Page 204 List the administered DS1 parameters for SLS show extension Display extension-specific SLS data parameters. Note: It is preferable to use the show station command 5 of 9 204 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 205 PIM lockout feature show sig-group List all administered signaling groups in SLS show slot-config Define the slot and the board administration in the G250/G350 for show station Display extension-specific SLS data parameters show trunk-group Display trunk group administration in...
  • Page 206 Specify whether the ISDN trunk group will operate by declaring the service type explicitly on a call-by-call basis 7 of 9 206 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 207 Configuring SLS Table 58: SLS CLI command hierarchy (continued) Root Level First Level Context Second Level Context Description Commands Commands Commands set cbc-parameter Specify the type of service or feature being declared in the Network Services Facility information element set cbc-service-feature Define what class of service is being specified, as part of the scocs service declared in the Network...

  • Page 208: Up-Converting Sls Data To Release 4.X

    The gateway saves the Release 4.x converted translations in startup-config. 4. Enter reset. This command makes sure that the new translation file command set is being executed and prevents spurious error messages from occasionally being displayed. 208 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 209: Down-Converting Release 4.X Sls Data To Release 3.X

    Configuring SLS Down-converting Release 4.x SLS data to release 3.x If you have a Release 4.x SLS administration data set in which stations are administered with station numbers greater than seven digits, and you wish to apply that data set to Release 3.1-level firmware on a gateway, you must re-administer the stations with extension numbers not exceeding seven digits.
  • Page 210 Configuring Standard Local Survivability (SLS) 210 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 211: Chapter 6: Configuring Ethernet Ports

    Avaya G350 Media Gateways. Ethernet ports on the G250 The switch and router on the Avaya G250 Media Gateway have various Ethernet ports. Ethernet ports on the G250 Media Gateway switch The switch on the Avaya G250 Media Gateway has the following Ethernet port: Eight 10/100 Mbps fixed switch ports on the front panel (ports 10/3 –...

  • Page 212: Ethernet Ports On The G350

    Use a crossover network cable when you connect a computer or other endpoint device to the fixed router port. For the other Ethernet ports on the G250, you can use either a standard network cable or a crossover network cable to connect any device.

  • Page 213: Configuring Switch Ethernet Ports

    361. Switch Ethernet port commands Use the following commands for basic configuration of switch Ethernet ports. For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Use the set port auto-negotiation-flowcontrol-advertisement command ●...
  • Page 214 Use the set port speed command to configure the speed of a port or range of ports. In ● auto-negotiation mode, the port’s speed is determined by auto-negotiation. An error message is generated if you attempt to set the speed when auto-negotiation is enabled. 214 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 215: Summary Of Switch Ethernet Port Configuration Cli Commands

    Configuring switch Ethernet ports Summary of switch Ethernet port configuration CLI commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 59: Switch Ethernet port configuration CLI commands Command Description Set the flow control advertisement for the specified...

  • Page 216: Configuring The Wan Ethernet Port

    The traffic shape rate is determined in bits. The bandwidth is determined in Note: kilobytes. For information on traffic shaping in general, see Configuring QoS parameters on page 252. 216 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 217: Backup Interfaces

    Use the speed command to set the port speed. ● Summary of WAN Ethernet port configuration CLI commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 60: WAN Ethernet port configuration CLI commands...

  • Page 218: Configuring Dhcp Client

    DHCP client-server protocol. The DHCP server grants the G250/G350 DHCP client an IP address for a fixed amount of time, called the lease. After the lease expires, the G250/G350 DHCP client is required to stop using the IP address. The G250/G350 DHCP client periodically sends requests to the server to renew or extend the lease.

  • Page 219: Dhcp Client Applications

    Configuring DHCP client DHCP client applications The typical application of DHCP client in the G250/G350 involves requesting and receiving an IP address from the service provider’s DHCP server, to enable a broadband Internet connection via cable modem. Figure 13: Fixed connection to broadband Internet using G250/G350 as DHCP client DHCP client configuration 1.
  • Page 220 A message appears, displaying the IP address and mask assigned by the DHCP server. For example: G350-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 220 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 221: Releasing And Renewing A Dhcp Lease

    Subnet Mask : 255.255.255.0 Default Router : 193.172.104.162 DHCP Server : 192.100.106.163 DNS Server : 192.100.106.101 Domain Name : avaya.com Lease Received (D:H:M:S) : 0:0:10:0 Lease Remains (D:H:M:S) : 0:0:9:32 Lease Rebind (D:H:M:S) : 0:0:8:45 Lease Renew (D:H:M:S) : 0:0:5:0...

  • Page 222: Maintaining Dhcp Client

    Interface FastEthernet 10/2 assigned DHCP address 193.172.104.161, mask 255.255.255.0 Maintaining DHCP client For a full description of the commands and their output fields see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Use the show ip dhcp-client command to show the configuration of the DHCP ●...

  • Page 223: Summary Of Dhcp Client Configuration Cli Commands

    Configuring DHCP client Summary of DHCP client configuration CLI commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 61: DHCP client configuration CLI commands Root level Command Description command Clear the DHCP client statistics counters...

  • Page 224: Configuring Lldp

    MIB. You can enable (Rx-only, TX-only, and Rx or Tx) or disable LLDP mode of operation on a per-port basis. 224 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 225: Supported Tlvs

    Configuring LLDP Supported TLVs Mandatory TLVs End-of-LDPDU ● Chassis ID ● Port ID ● Time to Live ● Optional TLVs Port description ● System description ● System name ● System capabilities ● Management address ● 802.1 TLVs (optional) VLAN name ●...

  • Page 226: Displaying Lldp Configuration

    Use the show port lldp config command to display port-level LLDP configuration. ● Use the show port lldp vlan-name config command to show the statically bound ● VLANs that the port transmits in the VLAN Name TLV. 226 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 227: Supported Ports For Lldp

    Configuring LLDP Supported ports for LLDP Only designated ports can be configured to support LLDP. For the G250, module 10, ports 3-10. This includes all Ethernet LAN ports on the G250 ● connecting directly to the chassis. Note: On the G250-DCP, only ports 3 and 4 are Ethernet LAN ports.
  • Page 228 Command Description Display port-level LLDP configuration show port lldp config Show the VLANs that are being transmitted on a show port lldp vlan-name specific port config 2 of 2 228 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 229: Chapter 7: Configuring Logging

    System logging is a method of collecting system messages generated by system events. The Avaya G250/G350 Media Gateway includes a logging package that collects system messages in several output types. Each of these types is called a sink. When the system generates a logging message, the message can be sent to each sink that you have enabled.

  • Page 230: Configuring A Syslog Server

    Clock daemon ● mail. Electronic mail ● local0 – local7. For local use ● ftpd. FTP daemon ● kern. kernel ● alert. Log alert ● audi. Log audit ● 230 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 231: Disabling Syslog Servers

    Configuring a Syslog server ntp. NTP subsystem ● lpr. Printing ● sec. Security ● syslog. System logging ● uucp. Unix-to-Unix copy program ● news. Usenet news ● user. User process ● 4. Optionally, limit access to the Syslog server output by typing the set logging server access-level command, followed by an access level (read-only, read-write, or admin) and the IP address of the Syslog server.

  • Page 232: Displaying The Status Of The Syslog Server

    SWICHFABRIC-Notification: Port 10/3 Link in this ● 005ms, example), detailing the milliseconds, the application being logged, the severity level, the message text, and an Authentication File Identification number (AFID). 232 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 233: Copying A Syslog File

    Configuring a log file Copying a syslog file You can copy the syslog file from the gateway to another location via FTP, SCP, or TFTP, or locally to a USB mass storage device. Use the copy syslog-file ftp command to copy the syslog file to a remote server ●...

  • Page 234: Displaying Log File Messages

    Displaying conditions defined for the file output sink Enter show logging file condition. For example: G350-001(super)# show logging file condition ****************************************************** *** Message logging configuration of FILE sink *** Sink Is Enabled Sink default severity: Informational 234 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 235: Log File Message Format

    Configuring a session log Log file message format Log file messages appear in first-in, last-out order. They have the following format: 01/18/2005,10:55:09:CLI-Notification: root: set port disable 10/6 01/18/2005,10:49:03:SWITCHFABRIC-Notification: Port Connection Lost on Module 10 port 5 Each message provides the following information: The date and time (if available) ●...

  • Page 236: Displaying How The Session Logging Is Configured

    The user enabling the log will only see entered commands with a user-level no Note: higher than the user’s own privileges. For example, a user with read-write privileges will not see entered commands having an admin user level. 236 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 237: Configuring Logging Filters

    Configuring logging filters Configuring logging filters You can use filters to reduce the number of collected and transmitted messages. The filtering options are based on message classification by severity for each application. For a specified sink, you can define the threshold severity level for message output for each application. Messages pertaining to the specified applications, that have a severity level stronger than or equal to the defined threshold, are sent to the specified sink.

  • Page 238: Severity Levels

    Message that only appears during debugging Sinks default severity levels Syslog. Warning ● Log file. Informational ● Session ● - Session from terminal. Informational - Session from telnet/ssh. Warning 238 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 239: Applications To Be Filtered

    Configuring logging filters Applications to be filtered Filters can be defined for any application listed in Table Table 65: Logging applications Application Description Address Resolution Protocol mechanism System startup failures boot Call Detail Recording. Registers the active calls in SLS mode.

  • Page 240: Syslog Server Example

    WAN plugged-in expansion 2 of 2 Syslog server example The following example defines a Syslog server with the following properties: IP address 147.2.3.66 ● Logging of messages enabled ● 240 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 241: Log File Example

    Configuring logging filters Output to the Kernel facility ● Only messages that can be viewed by read-write level users are received ● Filter restricts receipt of messages from all applications to those less severe than error ● G350-001(super)# set logging server 147.2.3.66 Done! G350-001(super)# set logging server enable 147.2.3.66 Done!

  • Page 242: Session Log Example

    ! Severity Override ------------------------------------------- ISAKMP ! Informational Summary of Logging configuration CLI commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 66: Logging configuration CLI commands Command Description Copy the syslog file to a remote server using FTP...
  • Page 243 Summary of Logging configuration CLI commands Table 66: Logging configuration CLI commands (continued) Command Description Delete the message log file being stored in non-volatile clear logging file memory (NVRAM), including the history log, and open a new, empty log file Delete the specified Syslog message server from the clear logging server Syslog server table...
  • Page 244 Configuring logging 244 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 245: Chapter 8: Configuring Voip Qos

    Configuring RTP and RTCP on page 245. You can use many types of telephones and trunks that do not directly support VoIP. The Avaya G250/G350 Media Gateway translates voice and signalling data between VoIP and the system used by the telephones and trunks.

  • Page 246: Header Compression Configuration Options

    Configuring VoIP QoS The G250/G350 offers both RTP header compression, for reducing the amount of bandwidth needed for voice traffic, and TCP and UDP header compression, for reducing the amount of bandwidth needed for non-voice traffic. For header compression purposes, any UDP packet with an even destination port within a user-configurable range of ports, is considered an RTP packet.

  • Page 247: Configuring Iphc

    Configuring header compression Note: Non-IETF encapsulation is compatible with other vendors. Note: Configuring IPHC IHPC applies to RTP, TCP, and UDP headers. Note: You cannot specify IPHC for a Frame Relay non-IETF interface. Note: 1. Optionally, configure header compression parameters. If you do not configure these parameters, their default values are used.
  • Page 248 To disable IPHC on an interface, use the no form of the command you employed (in the interface context): no ip rtp header-compression or no ip tcp header-compression. 248 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 249: Summary Of Iphc Header Compression Cli Commands

    Configuring header compression Summary of IPHC header compression CLI commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 68: IPHC configuration CLI commands Root level command First level command Description Clear IP RTP header compression statistics for...

  • Page 250: Configuring Vj Header Compression

    The ip tcp header-compression iphc-format command always Note: overrides the ip tcp header-compression command, and activates IPHC-type compression. For example: G350-001# interface dialer 1 G350-001(config-if:Dialer 1)# ip tcp header-compression Done! 250 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 251: Summary Of Van Jacobson Header Compression Cli Commands

    Displaying and clearing header compression statistics For a full description of the commands and their output fields, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Use the show ip rtp header-compression command to display the RTP header ●...

  • Page 252: Configuring Qos Parameters

    ● The source can be either local, in which case the user configures the values locally on the G250/G350, or remote, in which case the values are obtained from the G250/G350’s registered MGC. Use the set qos signal command to provide the means to set up QoS parameters for ●...

  • Page 253: Configuring Rtcp Qos Parameters

    Use the show qos-rtcp command to display QoS, RSVP, and RTCP parameters. ● Summary of QoS, RSVP, and RTCP configuration CLI commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 70: QoS, RSVP and RTCP configuration CLI commands...

  • Page 254: Weighted Fair Voip Queuing (Wfvq)

    The no form of the fair-voip-queue command does not exist. If you enter the Note: command no fair-voip-queue, it will actually enable WFVQ if WFVQ is not already enabled. 254 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 255: Summary Of Wfvq Configuration Cli Commands

    Use the show queue command to display information about the real-time status of output ● queues for the current interface. Summary of WFVQ configuration CLI commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 71: WFVQ configuration CLI commands Root level...

  • Page 256: Priority Queueing

    ● estimate the high priority queue size necessary to meet the queuing delay for a specific VoIP codec. Use the show queueing command to display the queueing configuration. ● 256 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 257: Summary Of Priority Queueing Configuration Cli Commands

    Priority queueing Summary of priority queueing configuration CLI commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 72: Priority queueing configuration CLI commands Root level Command Description command Enter the Serial, FastEthernet, or...
  • Page 258 Configuring VoIP QoS 258 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 259: Chapter 9: Configuring The G250 And G350 For Modem Use

    You can connect either a USB or a serial modem to the Avaya G250/G350 Media Gateway. A USB modem must be connected to the USB port on the G250 or G350 chassis. A serial modem must be connected to the Console port (CONSOLE) on the G250 or G350 chassis.
  • Page 260 - chap. Challenge Handshake Authentication Protocol. An encrypted password is sent for authentication. To configure this password, use the ppp chap-secret command. Note: If the G250/G350 firmware is replaced by an earlier firmware version, the ppp Note: chap-secret is erased, and must be re-configured.

  • Page 261: Summary Of Cli Commands For Configuring The Usb Port For Modem Use

    Configuring the USB port for modem use Summary of CLI commands for configuring the USB port for modem use For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 73: USB port configuration for modem use, CLI commands...

  • Page 262: Configuring The Console Port For Modem Use

    Enter async mode interactive to set the Console port to use modem mode every time an Avaya proprietary modem cable is plugged into the Console port. If you do not want the Console port to automatically detect when a modem is connected to it, enter async mode terminal to disable interactive mode.

  • Page 263: Summary Of Cli Commands For Configuring The Console Port For Modem Use

    ● Summary of CLI commands for configuring the Console port for modem use For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 74: Console port configuration for modem use, CLI commands Root level...

  • Page 264: Configuring The Console Device To Connect To The Console Port

    Console port uses the following settings: baud = 9600 ● data bits = 8 ● parity = none ● stop bits = 1 ● flow control = hardware ● 264 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 265: Chapter 10: Configuring Wan Interfaces

    You can use an MM340 E1/T1 media module or an MM342 USP media module as an endpoint for a WAN line on both the G250 and the G350. You can also use the Fast Ethernet port on the G250/G350 chassis as the endpoint for a WAN line by configuring the FastEthernet interface for PPP over Ethernet (PPPoE).

  • Page 266: Serial Interface Overview

    WAN media module. Serial interfaces support PPP and frame relay encapsulation protocols. The G350 supports multiple channel groups on the same E1/T1 interface. In contrast, the G250 only supports a single channel group. If a G250 user attempts to create more than one channel group, an error message appears.

  • Page 267: E1/T1 Port Channel Group

    Serial interface overview E1/T1 port channel group Figure 15 illustrates an E1/T1 port channel group. All data from the channel group is encapsulated using frame relay protocol. The data is sent via a frame relay Serial interface and sub-interfaces over the multiple IP interfaces defined using Data Link Connection Identifier (DLCI).

  • Page 268: Frame Relay Multipoint Topology Support

    The Avaya G250/G350 Media Gateway supports point-to-point frame relay connections. To enable you to use the G250/G350 as an endpoint in a Point to Multi-Point (PTMP) topology, the G250/G350 supports inverse ARP replies. The G250/G350 responds to inverse ARP queries received on frame relay sub-interfaces with the proper inverse ARP replies.

  • Page 269: Configuring The Avaya Mm340 E1/T1 Wan Media Module

    2. Enter show ds-mode to check whether the G250/G350 is configured for E1 or T1 operation. 3. Use the ds-mode command to set the mode of the G250/G350 to E1 or T1. Changing the line type requires resetting the module. The default value is T1.
  • Page 270 8. Use the interface serial command to enter the Serial interface context. Specify the slot number of the media module, the port number, the channel group number, and optionally, the IP interface number. 270 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 271 Initial WAN configuration Note: The WAN media module in a G250 must always be in slot number 2. The G250 Note: only supports a single channel group. If you do not specify an IP interface number for the first Serial interface that you define on a channel group, the G250/G350 automatically assigns IP interface number 0.

  • Page 272: E1/T1 Default Settings

    Use the loopback diag command to activate or deactivate an inward diagnostic ● loopback signal on the controller interface. Use the loopback local command to activate or deactivate a local line or payload ● loopback signal on the controller interface. 272 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 273: Summary Of E1/T1 Ports Configuration Commands

    This command is applicable only to a T1 line. Summary of E1/T1 ports configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 76: E1/T1 port configuration CLI commands...

  • Page 274: Configuring The Avaya Mm342 Usp Wan Media Module

    IP interface number. Note: The WAN media module in a G250 must always be in slot number 2. Note: If you do not specify an IP interface number for the first Serial interface that you define on a port, the G250/G350 automatically assigns IP interface number 0.
  • Page 275 The transmitter-delay command is usually used when the DCE equipment Note: that is connected directly to the G250/G350, or the router on the WAN have a receive buffer that is not large enough to hold the traffic sent by the G250/G350.

  • Page 276: Usp Default Settings

    Encoding Bandwidth 2,048 kbps Line-up indicator signal Summary of USP port configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 78: USP port configuration CLI commands Root level command Command Description...

  • Page 277: Configuring Ppp

    - ppp timeout ncp. Set the maximum time to wait for the network layer to negotiate. If this time is exceeded, the G250/G350 restarts the PPP session. - ppp timeout retry. Set the maximum time to wait for a response during PPP negotiation.

  • Page 278: Summary Of Ppp Configuration Commands

    Configuring WAN interfaces Summary of PPP configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 79: PPP configuration CLI commands Root level command Command Description Enter Serial interface or sub interface...

  • Page 279: Configuring Pppoe

    Initial WAN configuration A typical broadband access network is based on ADSL modems configured as transparent Ethernet bridges. ADSL modems use ATM protocol, and the transparent bridging is done to a well known ATM VC. On the other side of the telephone line is a device called a DSLAM. The DSLAM terminates the ADSL physical layer, collects the ATM cells from the various ADSL subscribers, and places them on the SP ATM infrastructure.
  • Page 280 PPPoE client terminates the PPPoE tunnel. - pppoe-client persistent delay. Set the interval between pppoe-client dial attempts. - pppoe-client persistent max-attempts. Limit the number of consecutive connection establishment retires 280 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 281 For more information on the PPoE commands, see Table 6. If the G250/G350 is connected to the Internet via the FastEthernet interface configured for PPPoE, and you define a VPN tunnel which specifies remote hosts by name, it is recommended to use the ppp ipcp dns request command. The command requests the list of available DNS servers from the remote peer during the PPP/IPCP session.

  • Page 282: Summary Of Pppoe Commands

    Configuring WAN interfaces Summary of PPPoE commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 80: PPPoE CLI commands Root level command Command Description Enter the FastEthernet interface interface context fastethernet Change the encapsulation to PPPoE...

  • Page 283: Configuring Frame Relay

    Configuring frame relay 1. Ensure that the port is configured on the media module: - For an E1/T1 port, see Configuring the Avaya MM340 E1/T1 WAN media module page 269 - For a USP port, see Configuring the Avaya MM342 USP WAN media module page 274 2.
  • Page 284 2 on the USP media module in slot number 4, on port number 1, with IP interface number 1 Note: The WAN media module in a G250 must always be in slot number 2. The G250 Note: only supports a single channel group.

  • Page 285: Resetting And Displaying Frame Relay Interface Counters

    Use the show interfaces command to display interface configuration and statistics for a specific interface or for all interfaces. Summary of frame relay commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 81: Frame relay CLI commands...

  • Page 286: Verifying The Wan Configuration And Testing Connectivity

    For all serial interfaces (E1/T1 and USB-modem), use the show interfaces serial command to verify that the interface and line protocol are both up. For example: Serial x/y:z is up, line protocol is up 286 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 287 ● Enter show startup-config to display the configuration loaded at startup. ● Use the ping command to send ICMP echo request packets from the G250/G350 to the ● interface Serial peer IP address and verify that it responds. Use the ping command to send ICMP echo request packets to another node on the ●...

  • Page 288: Summary Of Wan Configuration Verification Commands

    Configuring WAN interfaces Summary of WAN configuration verification commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 82: WAN configuration verification CLI commands Command Description Check host reachability and network connectivity ping...

  • Page 289: Backup Interfaces

    Backup interfaces Backup interfaces You can configure backup relations between a pair of any Layer 2 Serial interfaces. A backup interface is activated when the primary interface fails. The backup interface is deactivated when the primary interface is restored. A PPP session, frame relay interface, frame relay sub-interface, Dialer interface, FastEthernet interface, or Loopback interface can serve as a backup interface to any other Serial interface on the same module, including interfaces on different serial ports.

  • Page 290: Interface Backup Relations Rules

    You can also use this command to set a delay before reverting back to the primary interface. For example, the following command causes the G250/G350 to switch immediately to the backup interface in the event of primary interface failure, and to delay 60 seconds before...

  • Page 291: Summary Of Backup Interfaces Commands

    Modem dial backup The modem dial backup feature allows the Avaya G250/G350 Media Gateway to utilize a modem to provide redundant connectivity between a G250/G350 and IP phones in a small branch office and their primary Media Gateway Controller (MGC) at the headquarters or a regional branch office.
  • Page 292 Dialer interface. This can be performed using access control lists (ACL), QoS lists, and Weighted Fair Queuing (WFQ) priority schemes. The administrator should apply these tools in both the G250/G350 and the Remote Access Server (RAS). For information on ACL and QoS lists, see Configuring policy on page 637.
  • Page 293 Modem dial backup uses a modem connected directly to the G250/G350’s USB or Console port. The modem can also be used to access the G250/G350 CLI from a remote location. The modem cannot do both at the same time. For information about remote access to the...

  • Page 294: Typical Installations

    Dialer and the primary interfaces are not expected to be up at the same time, the RAS server can use passive-OSPF-interface and the G250/G350 can use static via routes. The G250/G350 can call an ISP RAS (which is likely to assign it a dynamic IP address) ●...

  • Page 295: Configuring Modem Dial Backup

    Make sure policy is configured properly at the RAS server to ensure that signaling Note: has priority over regular traffic. For modem configuration instructions, see Configuring the G250 and G350 for modem use page 259. Note: It is recommended to use the maximum UART speed for the serial modem Note: (115400 BAUD).
  • Page 296 By default, redialing is disabled. For example: G350-001(if:dialer 1)# dialer persistent Done! G350-001(if:dialer 1)# dialer persistent delay 10 Done! 296 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 297 Modem dial backup Use the dialer wait-for-ipcp command to set the maximum time the dialer ● waits between dialing a number to successfully establishing PPP/IPCP. The default is 45 seconds. For example: G350-001(if:dialer 1)# dialer wait-for-ipcp 100 Done! 7. Configure an authentication method and parameters (if required): - For PAP authenticating, enter ppp pap sent-username followed by a username and password.
  • Page 298 10. From the general context, use the ip default-gateway dialer command to configure backup routing. The following example configures a simple low priority via static route: G350-001(super)# ip default-gateway dialer 1 1 low Done! 298 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 299: Modem Dial Backup Interactions With Other Features

    Backup interfaces on page 289. The G250/G350’s Console port is an RJ-45 asynchronous port that can be used to support ● the modem for dial backup. Thus, the Dialer can utilize the same serial modem that is used for remote access to the device.

  • Page 300: Configuration Example

    The branch office is connected to the corporate network using a G250/G350. IP phone users in the branch office connect to an MGC located in the headquarters data center, and an RAS is located in the headquarters data center, with multiple phone lines available for dial access.
  • Page 301 Modem dial backup Figure 19 shows the network topology. Figure 19: Modem dial backup configuration example Issue 5 June 2008...

  • Page 302: Command Sequence

    G250-001(super-if:Dialer 1)# dialer string 2 7325213412 Done! G250-001(super-if:Dialer 1)# dialer modem-interface console Done! G250-001(super-if:Dialer 1)# ip unnumbered 1 Loopback 1 Done! G250-001(super-if:Dialer 1)# ip access-group 305 out Done! G250-001(super-if:Dialer 1)# exit G250-001(super)# 302 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 303: Command Sequence Explanation

    Done! G250-001(if:serial 3/1:1)# exit G250-001(super)# Step 13 G250-001(super)# router ospf G250-001(super router:ospf)# network 149.49.4.4 0.0.0.3 area 0.0.0.5 Done G250-001(super router:ospf)# exit G250-001(super)# Command sequence explanation 1. Assign an IP address to the Loopback interface for use with modem dial backup using the interface loopback command.
  • Page 304 OSPF area 5. This configuration allows filtering to take place at the border points and minimizes topology updates on the headquarters data center routers. For more information on configuring OSPF routing, see Configuring OSPF on page 536. 304 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 305: Modem Dial Backup Maintenance

    Modem dial backup Modem dial backup maintenance The G250/G350 generates specific log messages for Dialer interface activity when configured to do so. 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.
  • Page 306 Dialer are no longer being met, and that the Dialer can be brought down. 1 of 6 306 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 307 Modem dial backup Table 84: Modem dial backup logging messages (continued) Log Message Severity Possible cause Action Dialer 1 string Informational The value of <string_ID> is None required. <string_ID> equal to the ID of the string <dialer_string> configured using the dialer string command.
  • Page 308 USB modem attempts Check modem ● to dial and has an incorrect configuration for initialization string. The attempt proper initialization to dial fails. string. 3 of 6 308 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 309 Modem dial backup Table 84: Modem dial backup logging messages (continued) Log Message Severity Possible cause Action Modem cable Warning This message is generated Troubleshooting steps: unplugged when a Dialer interface is Check modem ● defined, but no modem cable is cable connection detected as being connected to to serial port and...
  • Page 310 PAP authentication request. CHAP Debug This message is sent when the None required. passed/failed authenticating station responds to the CHAP authentication request. 5 of 6 310 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 311 Modem dial backup Table 84: Modem dial backup logging messages (continued) Log Message Severity Possible cause Action IPCP Up/Down Debug PPP uses IPCP to define the IP None required. characteristics of the session. IP packets cannot be exchanged until IPCP is in the Up state. IPCP IP reject Warning This message is generated...

  • Page 312: Summary Of Modem Dial Backup Commands

    Configuring WAN interfaces Summary of modem dial backup commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 85: Modem dial backup CLI commands Root level Command Description command Enter the Dialer interface configuration...

  • Page 313: Icmp Keepalive

    ICMP keepalive Table 85: Modem dial backup CLI commands (continued) Root level Command Description command Enable requesting DNS information from the ppp ipcp dns remote peer during the PPP/IPCP session request Enter the Console, FastEthernet, interface Loopback, Serial, or Tunnel interface (fastethernet| configuration context loopback|...
  • Page 314 Figure 20: G250/G350 with T1 and xDSL lines For example, your branch office may have a G250 or G350 that connects to the Headquarters over a T1 line and via an xDSL connection to the Internet. The T1 line is used for voice traffic, while data packets are sent over the xDSL line.

  • Page 315: Enabling The Icmp Keepalive Feature

    Defining the ICMP keepalive parameters Use the following commands to define the ICMP keepalive parameters. For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Use the keepalive-icmp timeout command to set the timeout (in seconds) for ●...

  • Page 316: Example Of Configuring Icmp Keepalive

    G350-001(super-if:FastEthernet 10/2)# keepalive-icmp failure-retries 3 G350-001(super-if:FastEthernet 10/2)# keepalive-icmp success-retries 2 Done! Summary of ICMP keepalive configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 86: ICMP keepalive CLI commands Root level...

  • Page 317: Dynamic Cac

    Dynamic Call Admission Control (CAC) provides enhanced control over WAN bandwidth. When Dynamic CAC is enabled on an interface, the G250/G350 informs the MGC of the actual bandwidth of the interface and instructs the MGC to block calls when the bandwidth is exhausted.

  • Page 318: Enabling Dynamic Cac And Setting Maximum Bandwidth

    (optional). If dynamic CAC is activated on more than one active ● interface, the G250/G350 reports the bearer bandwidth limit of the interface with the highest activation priority. You can set the activation priority to any number from 1 to 255.

  • Page 319: Summary Of Dynamic Cac Configuration Commands

    Object tracking Summary of dynamic CAC configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 87: Dynamic CAC CLI commands Root level Command Description command Enter the Dialer, Serial, Loopback, interface...

  • Page 320: Object Tracking Configuration

    You can register either a VPN tunnel or an interface with an object tracker. For Note: more information see the definition of the keepalive-track command in the Avaya G250 and Avaya G350 CLI Reference, 03-300437. 320 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 321: Configuring Rtr

    Object tracking Note: You cannot configure both DHCP Client and object tracking on the WAN Note: FastEthernet interface. You can however configure tracking on the DHCP client default route. For more information on DHCP Client see Configuring DHCP client on page 218. Configuring RTR For each remote device whose state you wish to monitor: 1.
  • Page 322 The next-hop command is disabled by default. Use the next-hop command when the G250/G350 is connected to a remote device via more than one interface, and you wish to monitor the state of one specific interface. When you specify the next-hop as the interface you wish to monitor, you ensure that the RTR will probe that interface.

  • Page 323: Configuring Object Tracking

    50 as the unique ID for this object tracker. For example: G250-001(config)# track 1 rtr 5 G250-001(config-track rtr 1)# 2. Use the description command to enter a description for the object tracker. For example: G250-001(config-track rtr 1)# description "track rtr-5" Done! Issue 5 June 2008...
  • Page 324 The state of the object tracker will change from up to down if 1 or less hosts are up ● G350-001(config-track list 10)# threshold count up 2 down 1 Done! 324 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 325: Object Tracking Maintenance

    Object tracking Note: Object trackers operate indefinitely once they are defined. To stop the operation Note: of an object tracker, use the no track command to delete the object tracker. Figure 21: Object tracking configuration workflow type frequency dscp next-hop source-address wait-interval fail-retries...

  • Page 326: Viewing Rtr And Object Trackers Logging

    3. Use the set logging session condition tracker command to view all object tracker messages of level Info and above. For example: G350-001# set logging session condition tracker Info Done! CLI-Notification: write: set logging session condition tracker Info 326 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 327: Example Of Tracking A Single Remote Device

    G350-001(config)# rtr-schedule 5 start-time now life forever 2. The second step is to configure an object tracker which tracks the state of RTR 5. For example: G250-001(config)# track 1 rtr 5 G250-001(config-track rtr 1)# description "track rtr-5" Done! G250-001(config-track rtr 1)# exit Issue 5 June 2008...

  • Page 328: Example Of Tracking A Group Of Devices

    G350-001(config-rtr tcp 6)# frequency 500 milliseconds Done! G350-001(config-rtr tcp 6)# dscp 34 Done! G350-001(config-rtr tcp 6)# next-hop interface fastethernet 10/2 mac-address 00:01:02:03:04:05 Done! G350-001(config)# rtr-schedule 6 start-time now life forever G350-001(config-rtr tcp 6)# exit 328 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 329: Typical Object Tracking Applications

    2. The second step is to configure several object trackers. In this case, object tracker 1 tracks the state of RTR 5, and object tracker 2 tracks the state of RTR 6. For example: G250-001(config)# track 1 rtr 5 G250-001(config-track rtr 1)# description "track rtr-5" Done! G250-001(config-track rtr 1)# exit G250-001(config)# track 2 rtr 6 G250-001(config-track rtr 2)# description "track rtr-6"...

  • Page 330: Typical Application - Vpn Failover Using Object Tracking

    Typical application – VPN failover using object tracking In this application, the G250/G350 is connected to a remote site through an IPSec VPN tunnel. The remote site can be reached through two or more VPN gateways that can back each other up, such as a main gateway and a backup gateway.
  • Page 331 Object tracking 3. Define a track list consisting of all four object trackers, and configure it so that if all object trackers are up, the track list is up, and if two or less of the object trackers are up, the track list is down.
  • Page 332 ! Assign the serial 3/1:1 interface to be the backup interface for ! interface WAN FastEthernet 10/2. interface fastethernet 10/2 backup interface Serial 3/1:1 backup delay 0 60 exit 332 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 333: Typical Application - Interface Backup Via Policy-Based Routing

    Object tracking Typical application – interface backup via policy-based routing In the previous typical application (see Typical application – backup for the WAN FastEthernet interface on page 330), 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 traffic based on configured characteristics of the traffic.

  • Page 334: Typical Application - Tracking The Dhcp Client Default Route

    HQ peer. When the object tracker is up, the DHCP default route may be used. When the object tracker is down, the DHCP default route is not used for routing and traffic is routed to alternate routes. 334 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 335 Object tracking Note: If several default routers are learned from a specific interface, the object tracker Note: tracks only the first one. ! Apply DHCP client on the WAN Fast Ethernet interface fastethernet 10/2 ip address dhcp exit ! Configure the RTRs and object trackers. ! Use the next-hop command to ensure that the RTR is sent over the ! next hop it is monitoring, which is the WAN Fast Ethernet running ! DHCP client.

  • Page 336: Summary Of Object Tracking Configuration Commands

    Configuring WAN interfaces Summary of object tracking configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 88: Object tracking CLI commands Root level First level Second level Description command command command Enter Respond Time Reports (RTR) configuration mode.

  • Page 337: Frame Relay Encapsulation Features

    Set the upper and lower thresholds for threshold the threshold in the track list command count 2 of 2 Frame relay encapsulation features The Avaya G250/G350 Media Gateway supports the following frame relay encapsulation features: Frame relay traffic shaping and FRF.12 fragmentation ● Priority DLCI ●...

  • Page 338: Configuring Map Classes

    Use the fragment command to turn FRF.12 fragmentation on or off and to configure the fragment size. Displaying configured map classes Use the show map-class frame-relay command to display a table of all configured map-classes. 338 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 339: Summary Of Frame Relay Traffic Shaping Commands

    Priority DLCI Summary of frame relay traffic shaping commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 89: Frame relay traffic shaping CLI commands Root level command Command Description Enter the Serial interface or sub...

  • Page 340: Summary Of Priority Dlci Commands

    DLCI, it is recommended to verify that the primary DLCI is set as the High Priority DLCI in the Priority DLCI group. On the Avaya G250/G350 Media Gateway, OSPF is mapped by default to the High Priority DLCI. For better network reliability, it is recommended to verify that the same configuration exists on the other side of the frame relay connection.

  • Page 341: Ppp Voip Configuration

    Priority DLCI PPP VoIP configuration Figure 25 illustrates a common PPP VoIP configuration between two sites connected over a WAN: Figure 25: PPP VoIP configuration over WAN Site A connection details Site A contains four IP phones and a G350 with S8300 and one MM342 media module. The MM342 media module connects the G350 to the WAN via a USP 128 Kbps V.35 interface.

  • Page 342: Site B Connection Details

    The Primary management interface has changed. Please copy the running configuration to the start-up configuration file, and reset the device. G350-001(if:Loopback 1)# exit G350-001# copy running-config startup-config G350-001# reset 342 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 343 Priority DLCI VLAN interface configuration: ● G350-001# interface Vlan 1 G350-001(if:Vlan 1)# ip address 149.49.54.24 Done! G350-001(if:Vlan 1)# exit G350-001# interface Vlan 2 G350-001(if:Vlan 2)# ip address 11.11.11.1 24 Done! G350-001(if:Vlan 2)# exit Serial interface configuration: ● G350-001# interface serial 4/1 G350-001(if:Serial 4/1)# ip address 2.2.2.1 24 G350-001(if:Serial 4/1)# mtu 300 Note:...

  • Page 344: Configuration Example For Site B

    G350-001(if:Serial 4/1:1)# ip rtp compression-connections 20 G350-001(if:Serial 4/1:1)# ip rtp port-range 2048 3028 G350-001(if:Serial 4/1:1)# exit Static routes configuration: ● G350-001# ip route 1.1.1.0 24 serial 4/1:1 G350-001# ip route 11.11.11.0 24 serial 4/1:1 344 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 345: Chapter 11: Configuring Poe

    Power is supplied to a port only after it has detected that a suitable Powered Device (PD) is connected to the port. The MM314 and MM316 PoE media modules and the G250 look for an IEEE 802.3af-compliant signature from the device that indicates that the device requires power.

  • Page 346: Plug And Play Operation

    In addition, if the PoE module in the G350 is removed and replaced with a module of the same type, the port power configuration of the module is retained. 346 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 347: Powering Devices

    PD tries to draw more than the maximum allowed power per port, power is denied. The G250 has 92 W of power available for PDs. Each port can supply up to 18.8 W by default. If a PD tries to draw more than the maximum allowed power per port, power is denied.

  • Page 348: Poe Configuration Examples

    Powering priority on port 10/3 was set to High. Configuring PoE priority on a G350 port: G350-001(super)# set port powerinline priority 6/14 high Powering priority on port 6/14 was set to High. 348 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 349 6/22 Fault telephone 6/23 Delivering Power telephone Displaying PoE information for the G250: G250-003(super)# show powerinline Actual powerinline power consumption is 4 W. Powerinline power consumption trap threshold is 90 (98%) Watts. Powerline traps are enabled Port Inline Powering...

  • Page 350: Summary Of Poe Commands

    Configuring PoE Summary of PoE commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 91: PoE CLI commands Command Description Enable or disable the load detection process on the port set port powerinline...

  • Page 351: Chapter 12: Configuring Emergency Transfer Relay (Etr)

    LINE 1 when the problem ends, the call continues. The fixed trunk port and analog line ports do not start to operate until the active call ends. The ETR for each of the G250/G350 models closes the tip/ring contacts for the ports listed in Table...

  • Page 352: Setting Etr State

    (3/1 in the G250, 7/1 in the G350) and the first analog line port (3/2 in the G250, 7/2 in the G350). The other analog line port (3/3 in the G250, 7/3 in the G350) will also be disabled.

  • Page 353: Viewing Etr State

    Line number of the line connected to ETR ● Line status (off hook or on hook) ● Summary of ETR commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 93: ETR configuration CLI commands Command Description...
  • Page 354 Configuring Emergency Transfer Relay (ETR) 354 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 355: Chapter 13: Configuring Snmp

    They allow SNMP managers to communicate with agents to configure, get statistics and information, and receive alerts from network devices. You can use any SNMP-compatible network management system to monitor and control a G250/G350. Agent and manager communication There are several ways that the SNMP manager and the agent communicate.

  • Page 356: Snmp Versions

    ● SNMPv3 ● The G250/G350 supports all three versions. The implementation of SNMPv3 on the G250/G350 is backwards compatible. That is, an agent that supports SNMPv3 will also support SNMPv1 and SNMPv2c. 356 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 357: Snmpv1

    SNMP versions SNMPv1 SNMPv1 uses community strings to limit access rights. Each SNMP device is assigned to a read community and a write community. To communicate with a device, you must send an SNMP packet with the relevant community name. By default, if you communicate with a device using only the read community, you are assigned the security name ReadCommN.

  • Page 358: Users

    Use the no form of the snmp-server user command to remove a user and its mapping to a specified group. If you do not specify a group, the no form of the snmp-server user command removes the user from all groups. 358 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 359: Groups

    The group maps its users to views based on the security model and level with which the user is communicating with the G250/G350. Within a group, the following combinations of security model and level can be mapped to views: SNMPv1 security model and NoAuthNoPriv security level ●...

  • Page 360: Creating An Snmpv3 Group

    OIDs to the list or exclude OIDs from a list of all of the OIDs in the G250/G350’s MIB tree. You can use wildcards to include or exclude an entire branch of OIDs in the MIB tree, using an asterisk instead of the specific node. For a list of MIBs...

  • Page 361: Configuring Snmp Traps

    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 link up/down traps on specified G250/G350 interfaces. Use the following commands to configure the trap receivers table: Note: You need an Admin privilege level to use the SNMP commands.

  • Page 362: Notification Types

    Ethernet port fault notifications ● sw-redundancy. Software redundancy notifications ● temperature. Temperature warning notifications ● cam-change. Changes in CAM notifications ● 13-events. Duplicate IP, VLAN violations ● policy. Policy change notifications ● 362 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 363: Summary Of Snmp Trap Configuration Commands

    ● supply. Main and backup power supply notifications ● Summary of SNMP trap configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 95: SNMP trap configuration CLI commands Root level command...

  • Page 364: Configuring Snmp Access

    2 of 2 Configuring SNMP access Use the ip snmp command to enable SNMP access to the G250/G350. Use the no form ● of this command to disable SNMP access to the G250/G350. Use the set snmp retries command to set the number of times to attempt to ●...

  • Page 365: Summary Of Snmp Access Configuration Commands

    You need an Admin privilege level to use the SNMP commands. Note: Summary of SNMP access configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 96: SNMP access configuration CLI commands...

  • Page 366: Configuring Dynamic Trap Manager

    2 of 2 Configuring dynamic trap manager Dynamic trap manager is a special feature that ensures that the G250/G350 sends traps directly to the currently active MGC. If the MGC fails, dynamic trap manager ensures that traps are sent to the backup MGC.

  • Page 367: Summary Of Dynamic Trap Manager Configuration Commands

    Use the clear dynamic-trap-manager command to remove administration of the dynamic trap manager. Summary of dynamic trap manager configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 97: Dynamic trap manager configuration CLI commands...

  • Page 368: Snmp Configuration Examples

    G350-001# snmp-server user johnny ReadWriteG v3 auth md5 katmandu priv des56 ktamatan The following example creates an admin user: G350-001# snmp-server user johnny v3AdminG v3 auth md5 katmandu priv des56 ktamatan 368 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 369 The following example sets the SNMPv1 read-write community: G350-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...
  • Page 370 Configuring SNMP 370 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 371: Chapter 14: Configuring Contact Closure

    1. Connect an Avaya Partner Contact Closure Adjunct™ to the Contact Closure port on the Avaya G250/G350 Media Gateway front panel. The Contact Closure port is labeled CCA on both the G250 and the G350 front panels. Use a telephone cable with standard RJ-11 connectors.

  • Page 372: Contact Closure Software Configuration

    1. Enter the set contact-closure admin command. In the following example, the command sets contact closure to work in relay 1 of the Avaya Partner Contact Closure Adjunct™ when activated by the call controller. set contact-closure admin 10/1:1 mgc 2.

  • Page 373: Showing Contact Closure Status

    Showing contact closure status In the following example, the command deactivates contact closure in relay 2 of the Avaya Partner Contact Closure Adjunct™. Contact closure will not operate, even automatically, until you use the set contact-closure admin command to change the status of contact closure to mgc or manual-trigger.
  • Page 374 Set the length of time for the relay to return to normal after the call controller triggers the relay contact-closure pulse-duration Display the status of one or all contact closure relays show contact-closure 2 of 2 374 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 375: Chapter 15: Transferring And Managing Announcement Files

    The G250/G350 stores announcement files in an internal announcement directory. The G250/G350 supports up to 256 announcement files, totalling up to 15 minutes of audio for announcements and music on hold. Recording, storing, and playing announcement files is controlled by Avaya CM.
  • Page 376 ● announcement-file ftp command. Specify the file name of the announcement file in the G250/G350 announcement directory, followed by the IP address of the remote FTP server, and, optionally, a destination file name, including the full path. For example: G350-001(super)# copy announcement-file ftp local_announcement2.wav 192.168.49.10 remote_announcement2.wav...
  • Page 377 Announcement file operations Display the announcements files stored in the G250/G350 announcement directory, using ● the show announcements-files command. Optionally add the keyword brief to display less detail. For example: G350-001(super)# show announcements files Mode: FTP-SERVER/SCP-CLIENT File Description Size (Bytes) Date ---- ---------------- ------------- ------------ ----------------- 46xxupgrade.scr...

  • Page 378: Summary Of Announcement Files Commands

    Transferring and managing announcement files Summary of announcement files commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 100: Announcement file CLI commands Command Description Upload an announcement file to a remote FTP...

  • Page 379: Chapter 16: Configuring Advanced Switching

    You can configure advanced switching on the switch ports of the Avaya G250 and Avaya G350 Media Gateways. In the G250, the switch ports are the ETH LAN PoE ports located on the front panel. For the G350, switch ports are located on the Avaya MM314 Media Module and the Avaya MM316 Media Module, either (or neither) of which may be installed.

  • Page 380: Multi Vlan Binding

    VLAN for privacy. The whole building has a shared high-speed connection to the ISP. In order to accomplish this, the G250/G350 enables multiple VLANs per port. The available Port Multi-VLAN binding modes are: Bound to Configured.

  • Page 381: G250/G350 Vlan Table

    Unassigned packets receive the PVID of the port and are therefore allowed to enter. ICC-VLAN When the G250/G350 includes an ICC, the ICC connects to the G250/G350 via an internal switch. By default, the ICC is connected on Vlan 1. The VLAN to which the ICC connects is called the ICC-VLAN.

  • Page 382: Vlan Cli Commands

    Use the show vlan command to display the VLANs configured in the switch ● VLAN configuration examples The following example deletes a statically bound VLAN from a port: G350-001(super)# clear port static-vlan 10/3 34 VLAN 34 is unbound from port 10/3 382 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 383 Configuring VLANs The following example deletes a VLAN and its interface: G350-001(super)# clear vlan 34 This command will assign all ports on VLAN 34 to their default in the entire management domain – do you want to continue (Y/N)? y All ports on VLAN-id assigned to default VLAN.
  • Page 384 10/3 is bind to all configured VLANs The following example displays VLAN tagging information: G350-001(super)# show trunk Port Mode Binding mode Native VLAN ------ ----- ------------------------- ----------- 10/3 dot1q bound to configured VLANs 54 384 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 385: Summary Of Vlan Commands

    ------- -------------------------------- Marketing 2121 Training Total number of VLANs: 4 Summary of VLAN commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 101: VLAN CLI commands Root level First level Description command...

  • Page 386: Configuring Port Redundancy (G350 Only)

    Ethernet ports (1-24) and the Gigabit Ethernet port (51) on the MM314 Media Module or the Ethernet ports (1-40) and the Gigabit Ethernet port (51) on the MM316 Media Module. Note: Port redundancy is not supported on the G250. Note: 386 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 387: Secondary Port Activation

    Port redundancy CLI commands The following commands are used to configure port redundancy. For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Use the set port redundancy enable/disable command to globally enable or ●...

  • Page 388: Port Redundancy Configuration Examples

    The following example displays port redundancy information: G350-001(super)# show port redundancy Redundancy Name Primary Port Secondary Port Status ----------------- -------------- ---------------- -------- Monitor primary Minimum Time between Switchovers: 60 Switchback interval: 30 388 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 389: Summary Of Port Redundancy Commands

    You can define one source port and one destination port on each G250/G350 for received (Rx), transmitted (Tx), or transmitted and received (both) traffic.

  • Page 390: Port Mirroring Cli Commands

    Configuring advanced switching Port mirroring CLI commands The following commands are used to configure port mirroring on the G250/G350. For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Use the set port mirror command to define a port mirroring pair in the switch ●...

  • Page 391: Summary Of Port Mirroring Commands

    Configuring spanning tree (G350 only) Summary of port mirroring commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 103: Port mirroring CLI commands Command Description Delete a port mirroring pair clear port mirror...

  • Page 392: Spanning Tree Per Port

    Designated port. The corresponding port on the remote bridge of the local root port ● Alternate port. An alternate route to the root ● Backup port. An alternate route to the network segment ● 392 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 393 Configuring spanning tree (G350 only) The RSTP algorithm usually makes it possible to change port roles rapidly through its fast topology change propagation mechanism. For example, a port in the blocking state can be assigned the role of alternate port. When the backbone of the network fails, the port can rapidly be changed to forwarding.

  • Page 394: Spanning Tree Cli Commands

    Use the set spantree tx-hold-count command to set the value in packets used by ● the spanning tree in order to limit the maximum number of BPDUs transmitted during a hello-time period. 394 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 395: Spanning Tree Configuration Examples

    Configuring spanning tree (G350 only) Use the set spantree version command to set the version of the spanning tree ● protocol. Use the show spantree command to display spanning-tree information. ● Spanning tree configuration examples The following example enables spanning tree on a port: G350-001(super)# set port spantree enable 6/5 port 6/5 was enabled on spantree The following example disables spanning tree on a port:...
  • Page 396 4. The following example configures the version of spanning tree to use on the device: G350-001(super)# set spantree version rapid-spanning-tree Spanning tree version is set to rapid spanning tree. 396 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 397 Configuring spanning tree (G350 only) The following example displays spanning tree information: G350-001(super)# show spantree Spanning tree state is enabled Designated Root: 00-40-0d-92-22-81 Designated Root Priority: 32768 Designated Root Cost: 19 Designated Root Port: 6/24 Root Max Age: 20 Hello Time: 2 Root Forward Delay: 15 Bridge ID MAC ADDR: 00-04-0d-29-c4-ca Bridge ID priority: 36864...

  • Page 398: Summary Of Spanning Tree Commands

    Configuring advanced switching Summary of spanning tree commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 104: Spanning tree CLI commands Command Description Assign or de-assign RSTP edge-port admin state to a...

  • Page 399: Port Classification

    Port classification With the G250/G350, 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 sent even when the port is disabled.
  • Page 400 Configuring advanced switching The following example displays the port classification of all ports on the G250: G250-003(super)# show port classification Port Port Classification -------- ------------------------- 10/3 regular 10/4 valuable 10/5 regular 10/6 valuable 10/7 regular 10/8 regular 10/9 regular 10/10...

  • Page 401: Summary Of Port Classification Commands

    Port classification Summary of port classification commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 105: Port classification CLI commands Command Description Set the port classification to either regular or valuable set port classification...
  • Page 402 Configuring advanced switching 402 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 403: Chapter 17: Configuring Monitoring Applications

    RMON agent on the management station. You can configure RMON for switching on the Avaya G350 Media Gateway. The G250/G350 uses RMON I, which analyzes the MAC layer (Layer 2 in the OSI seven-layer model). You can also configure a port to raise an SNMP trap whenever the port fails.

  • Page 404: Rmon Cli Commands

    6, recording activity over 60 intervals (buckets) of 20 seconds each. G350-001(super)# rmon history 80 6/24 interval 20 buckets 60 owner root history index 80 was created successfully 404 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 405 Configuring RMON The following example displays information about an RMON alarm entry: G350-001(super)# show rmon alarm 1 alarm alarm 1 is active, owned by root Monitors ifEntry.1.16777216 every 20 seconds Taking delta samples, last value was 0 Rising threshold is 10000, assigned to event # 32 Falling threshold is 1000, assigned to event # 32 On startup enable rising or_falling alarms The following example displays information about an RMON event entry:...

  • Page 406: Summary Of Rmon Commands

    Configuring monitoring applications Summary of RMON commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 106: RMON CLI commands Command Description Clear RMON statistics clear rmon statistics Create or delete an RMON alarm entry...
  • Page 407 An alternative tool available from Avaya for debugging QoS problems is VMON. Note: 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 408: Configuring The Rtp Statistics Application

    The RTP statistics application samples the VoIP engine every RTCP interval, which is configured in Avaya 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 Communication Manager, 03-300509.
  • Page 409 Configuring and analyzing RTP statistics Note: All CLI commands described in this section are available in the general context of Note: the CLI. Viewing the configured thresholds 1. Enter show rtp-stat thresholds. For example: G350-001(super)# show rtp-stat thresholds Item Threshold Event Threshold -------------------- -------------...

  • Page 410: Configuring Rtp Statistics Thresholds

    QoS in your network. Optimal values are different for each network. Configure any thresholds that are not already configured as you require them. See Viewing RTP statistics thresholds on page 408. 410 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 411: Enabling And Resetting The Rtp Statistics Application

    Configuring and analyzing RTP statistics For a description of each metric, see Table 107. The Codec metrics, Codec loss and Codec RTT are useful for evaluating the actual user experience. The other metrics are useful for identifying network problems that contribute to QoS problems experienced by the user. For example, the Codec RTT metric indicates the overall delay experienced by the user.

  • Page 412: Viewing Application Configuration

    QoS Trap Rate Limiter: Token Interval: 10.00 seconds Bucket Size: 5 Session Table: Size: 128 Reserved: 64 Min Stat Win: 50 Table 108 describes the output of the show rtp-stat config command. 412 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 413 Configuring and analyzing RTP statistics Table 108: RTP statistics application configuration Name Description RTP Statistic Status of the RTP statistics application. Possible values: Enabled. The application is enabled. ● Disabled. The application is disabled. ● QoS Trap QoS trap status. Possible values: Enabled.

  • Page 414: Configuring Qos Traps

    Enabling QoS traps 1. View the RTP statistic thresholds and modify their configurations as necessary. See Viewing RTP statistics thresholds on page 408 and Configuring RTP statistics thresholds on page 410. 414 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 415 Configuring and analyzing RTP statistics 2. If you need to modify the minimum statistic window, use the rtp-stat min-stat-win command. For example: G350-001(super)# rtp-stat min-stat-win 50 Done! The minimum statistic window is the minimum number of observed RTP sequence increments for which the application evaluates packet loss. The VoIP engine evaluates the current received packet loss every RTCP interval.

  • Page 416: Configuring Qos Fault And Clear Traps

    2000 hundredths of a second (20 seconds) and the bucket is limited to a maximum size of 10 tokens. 416 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 417: Analyzing Rtp Statistics Output

    See Configuring QoS fault and clear traps on page 416. Engine ID The ID of the VoIP engine. Since the G250/G350 has one VoIP engine, one line appears in the table. Description Description of the VoIP engine 1 of 2...

  • Page 418: Viewing Rtp Session Statistics

    G723 135.8.76.107 00033 2004-10-20,10:58:21 10:59:06 G723 135.8.76.107 00034 2004-10-20,11:08:40 G729 135.8.76.64 00035 2004-10-20,11:09:07 G723 135.8.76.107 An asterisk (*) in the QoS column indicates that the session had QoS problems. 418 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 419 Configuring and analyzing RTP statistics The show rtp-stat detailed command displays detailed information about a specified active or terminated RTP session, including the QoS metrics reported by the RTP statistics application. For example: G350-001(super)# show rtp-stat detailed 35 Session-ID: 35 Status: Terminated , QOS: Faulted , EngineId: 0...
  • Page 420 Start-Time: 2004-10-20,11:09:07 End-Time The end time of the RTP session End-Time: 2004-10-20,11:13:40 Duration The duration of the RTP session Duration: 00:04:33 CName format: gwt@<MGP-address> CName: gwp@135.8.118.252 1 of 6 420 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 421 Multiple sessions belonging to the same conference call can usually be identified by a common conference ID. Notes: Phone data is received from Avaya ● Communication Manager only if VMON is configured. If you are not running VMON, you ●...
  • Page 422 0.1%/0.0% codec loss Jbuf-delay The last jitter buffer delay Jbuf-Delay 22mS Max-Jbuf-Delay The maximum jitter buffer delay during Max-Jbuf-Delay 60mS the session 3 of 6 422 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 423 Configuring and analyzing RTP statistics Table 110: Detailed CLI output per RTP session (continued) Field Label Description From the CLI example Received RTP: Packets The total number of received packets Packets 9236 Loss The last sampled value of network RTP Loss 0.0% packet loss loss%...
  • Page 424 The network jitter experienced by the Jitter 0mS remote RTP receiver rem-jitter #rem-jitter-ev The number of samples that were over Jitter 0mS #0 the remote jitter threshold 5 of 6 424 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 425: Viewing Qos Traps, Qos Fault Traps, And Qos Clear Traps

    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. 1. In the Avaya Maintenance Web Interface, enter the Setup log viewing screen.

  • Page 426: Analyzing Qos Trap Output

    The date on which the trap was received Oct 20 The time at which the trap was received 11:13:40 The IP address of the local MGP 135.8.118.252 1 of 4 426 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 427 Multiple sessions belonging to the same conference call can usually be identified by a common conference ID. Notes: The phone string data is received from Avaya ● Communication Manager if VMON is configured. If you are not running VMON, you can cause ●...
  • Page 428 The minimum and maximum TTL values sampled in TTL 63-63 the session A counter that increments each time two Dup 0 consecutive RTP packets with the sample RTP sequence number are received 3 of 4 428 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 429: Analyzing Qos Fault And Clear Trap Output

    Configuring and analyzing RTP statistics Table 111: QoS Trap output fields (continued) Label Description From the trap example A counter that increments each time an RTP packet Fall 0 with a sequence number less than the last known sequence is received The average network loss experienced by the Rem{Loss 0.0% #0 Jtr #0}...
  • Page 430 INTEGER: 0 boundary. That is, the reduced number of active sessions with QoS faults that causes a QoS clear trap to be sent after a QoS fault trap was sent. 430 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 431: Viewing Automatic Traceroute Results

    Description Session ID The RTP statistics index for the RTP session From The IP address of the G250/G350 The IP address of the session destination (in this case, a destination within the specified subnet) The time the traceroute is performed...

  • Page 432: Rtp Statistics Examples

    Figure 29 shows the locations of four telephone extensions in an example network. Telephones with extensions 2004 and 2111 are connected to the local gateway G250/G350-001. Extensions 2002 and 2101 are connected to the remote gateway G250/G350-002. Figure 29: Four telephones in a sample network...
  • Page 433 Configuring and analyzing RTP statistics At the site of the local gateway “G250/G350-001”, the administrator enabled and configured the RTP-MIB application as follows: //to enable the RTP statistics application: G350-001(super)# rtp-stat-service //to view the configuration of the application: G350-001(super)# show rtp-stat config...
  • Page 434 //to configure the minimum statistics window for evaluating packet loss: G350-001(super)# rtp-stat min-stat-win 50 //to configure an external trap manager as a trap destination in addition to the active MGC: G350-001(super)# snmp-server host 136.9.71.47 traps v1 public 434 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 435 Configuring and analyzing RTP statistics //to check SNMP configuration G350-001(super)# show snmp Authentication trap enabled Community-Access Community-String ---------------- ---------------- read-only ***** read-write ***** SNMPv3 Notifications Status ----------------------------- Traps: Enabled Informs: Enabled Retries: 3 Timeout: 3 seconds SNMP-Rec-Address Model Level Notification Trap/Inform User name ---------------- ----- ------- --------------- ----------- ------------------- 135.9.77.47 v1 noauth all trap ReadCommN UDP port: 162 DM 136.9.71.47 v1 noauth all trap WriteCommN...

  • Page 436: A Call Over The Wan From An Analog Phone To An Ip Phone

    2002 (see Figure 30) in the network described in Configuring the RTP statistics application for a sample network on page 432. Figure 30: Remote call from analog to IP phone 436 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 437 Configuring and analyzing RTP statistics The RTP statistics application is configured as described in Configuring the RTP statistics application for a sample network on page 432. The callers complain after the call that there were QoS problems during the call. The administrator investigates as follows: //to see if the RTP statistics application registered QoS problems for the call: G350-001(super)# show rtp sessions QoS Start date and time End Time Type...

  • Page 438: A Local Call Between An Ip And An Analog Phone

    31) in the network described in Configuring the RTP statistics application for a sample network on page 432. The call is finished at 00:59:19. Figure 31: Local call from analog to IP phone 438 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 439 Configuring and analyzing RTP statistics After the call is ended, the administrator uses the CLI to view the QoS statistics: //to see if there were QoS problems registered during the session G350-001(super)# show rtp sessions last 1 Start date and time End Time Type Destination ----- --- ------------------- -------- ---------...

  • Page 440: A Remote Call Over The Wan From An Ip Phone To An Ip Phone

    30.30.30.2 Sessions 13 and 14 both belong to the call, since two VoIP channels are used by an unshuffled call between two IP phones: one channel between each telephone and the G250/G350 VoIP engine. 440 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 441 Configuring and analyzing RTP statistics Session 13 has QoS problems. //to display details of session 13: G350-001(super)# show rtp-stat detailed 13 Session-ID: 13 Status: Terminated, QOS: Faulted, EngineId: 0 Start-Time: 2004-12-07,01:02:45, End-Time: 2004-12-07,01:05:15 Duration: 00:02:30 CName: gwp@30.30.30.1 Phone: 202:2004 Local-Address: 30.30.30.1:2329 SSRC 3510756141 Remote-Address: 20.20.20.2:2329 SSRC 1372162 (0) Samples: 30 (5 sec) Codec:...
  • Page 442 --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: Loss 49dB #0, Len 32mS RSVP: Status Disabled, Failures 0 442 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 443: A Conference Call

    Configuring and analyzing RTP statistics A conference call A conference call is placed between IP phone extension 1003, analog phone extension 80900, and IP phone extension 80886. The call is established by calling from extension 1003 to extension 80900, and then using the conference function on extension 1003 to add 80886 (see Figure 33).
  • Page 444 Status: Active, QOS: Ok, EngineId: 0 Start-Time: 2004-12-23,09:55:20, End-Time: - Duration: 00:00:50 CName: gwp@33.33.33.33 Phone: 140 :80886:1003 Local-Address: 33.33.33.33:61175 SSRC 3702564610 Remote-Address: 149.49.41.50:61175 SSRC 15161893 (0) Samples: 10 (5 sec) 444 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 445: Summary Of Rtp Statistics Commands

    [1] [2]. Summary of RTP statistics commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 114: RTP statistics application CLI commands...

  • Page 446: Configuring And Analyzing Packet Sniffing

    PPP. Non-Ethernet packets are wrapped in a dummy Ethernet header to allow them to be viewed in a libpcap format. Thus, the G250/G350 allows you to analyze packets on all the interfaces of the device.

  • Page 447: What Can Be Captured

    Configuring and analyzing packet sniffing The G250/G350’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 so that older information is overwritten when the buffer fills up, and specify a maximum number of bytes to capture for each packet.

  • Page 448: Configuring Packet Sniffing

    Enabling packet sniffing Since the packet sniffing service presents a potential security breach, the administrator must first enable the service on the G250/G350 before a user can start capturing packets. Enter capture-service to enable the packet sniffing service. Note:...

  • Page 449: Creating A Capture List

    A capture list contains an ordered list of rules and actions. A rule specifies criteria against which packets are tested. The action tells the G250/G350 whether to capture or not capture packets matching the rule criteria. Only packets that match the specified criteria and have an action of capture are captured to the capture file.
  • Page 450 You can use the following rule criteria commands. These commands are described in more detail below. dscp ● ● ip protocol ● source ip address ● destination ip address tcp source-port ● ● tcp destination-port ● udp source-port ● udp destination-port 450 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 451 Configuring and analyzing packet sniffing icmp ● fragment ● Note: You can also use the description command in the rule context to add a Note: description of the rule. DSCP Use the dscp command, followed by a DSCP value (from 0 to 63) to apply the rule to all packets with the specified DSCP value.
  • Page 452 The rule applies to UDP packets from ports that match the defined ● criteria udp destination-port. The rule applies to UDP packets to ports that match the ● defined criteria 452 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 453 Configuring and analyzing packet sniffing 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 ●...
  • Page 454 G350-001(super-Capture 520/ip rule 20)# Fragment 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. 454 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 455 Configuring and analyzing packet sniffing Capture list example The following commands create a capture list that captures all traffic from subnet 135.122.50.149 255.255.255.254 to an ECC at address 135.122.50.171, except telnet: G350-001(super)# ip capture-list 511 G350-001(super-Capture 511)# name "list #511" Done! ! Rules 10 and 15 provide that telnet packets are not captured.

  • Page 456: Viewing The Capture List

    Applying a capture list To apply a capture list, use the capture filter-group command from the general context. For example, to set the G250/G350 to use capture list 511 on interfaces in which packet sniffing is enabled, specify the following command:...

  • Page 457: Configuring Packet Sniffing Settings

    This command will clear the capture buffer - do you want to continue (Y/N)? y Done! G350-001(super)# Note: When you change the maximum frame size, the G250/G350 clears the capture Note: buffer. Enter clear capture-buffer to clear the capture buffer. ●...

  • Page 458: Starting The Packet Sniffing Service

    However, you can use the capture ipsec command to specify that IPSec VPN packets, handled by the internal VPN gateway process, should be captured in plain text format. 458 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 459: Analyzing Captured Packets

    Configuring and analyzing packet sniffing Analyzing captured packets Analyze the captured packets by stopping the packet sniffing service, uploading the capture file, and analyzing the capture file. Stopping the packet sniffing service Enter capture stop to stop the packet sniffing service. You must stop the service in order to upload a capture file.

  • Page 460: Uploading The Capture File

    WAN problem, you can upload the capture file to an S8300 Server and view it using Tethereal, which is a command-line version of Ethereal. 460 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 461 Maintenance Web Interface, see Installing and Upgrading the Avaya G250 Media Gateway, 03-300434 or Installing and Upgrading the Avaya G350 Media Gateway, 03-300394. 3. In the Avaya Maintenance Web Interface, select FTP under Security in the main menu. 4. Click Start Server. 5. Log into the G250/G350.

  • Page 462: Analyzing The Capture File

    For example, you can display only packets with a specific source address, or only those received from a specific interface. See Identifying the interface on page 463. Figure 34 shows a sample Ethereal screen. 462 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 463 Figure 34: Sample Ethereal screen Identifying the interface The G250/G350’s packet sniffing service can capture also non-Ethernet packets, such as frame-relay and PPP, into the capture file. This is achieved by wrapping non-Ethernet packets in a dummy Ethernet header to allow the packets to be stored in a libpcap format. This enables you to analyze packets on all the device interfaces.

  • Page 464: Simulating Packets

    Serial interface on the media module in slot number 4, on port number 1, with channel group number 2 Simulating packets Capture lists support the IP simulate command. Refer to Simulating packets on page 657. 464 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 465: Summary Of Packet Sniffing Commands

    Configuring and analyzing packet sniffing Summary of packet sniffing commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 115: Packet sniffing CLI commands Root level First level Second level Description command command...
  • Page 466 IP address Set 'ip-protocol' to TCP and an equation on the destination port destination- port Set 'ip-protocol' to TCP and an equation on the source port source-port 2 of 3 466 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 467: Reporting On Interface Status

    Reporting on interface status Table 115: Packet sniffing CLI commands (continued) Root level First level Second level Description command command command Set 'ip-protocol' to UDP and an equation on the destination port destination- port Set 'ip-protocol' to UDP and an equation on the source port source-port Name a capture list...

  • Page 468: Summary Of Interface Status Commands

    For detailed specifications of CLI commands, refer to Avaya G250 and Avaya G350 CLI Reference, 03-300437. Summary of interface status commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437.

  • Page 469: Configuring And Monitoring Cna Test Plugs

    Configuring and monitoring CNA test plugs Configuring and monitoring CNA test plugs The Converged Network Analyzer (CNA) is a distributed system for real-time monitoring of IP networks, using active measurements. The CNA supports various network tests including connectivity tests with pings, topology tests with traceroute, and QoS tests with synthetic RTP streams.

  • Page 470: Cna Tests

    Any changes you make to the test plug configuration, such as changing scheduler addresses or port numbers, only take effect when you cause the test plug to disconnect from the scheduler and register again. 470 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 471: Configuring The G250/G350 Test Plug For Registration

    Configuring and monitoring CNA test plugs Configuring the G250/G350 test plug for registration From the G250/G350 CLI, you can configure the G250/G350 test plug to register with a CNA scheduler. 1. Use the cna-testplug command to enter the testplug context. For example:...
  • Page 472 The test plug attempts to register with the first scheduler on the scheduler list. You can use the show cna testplug command to see if the test plug is registered and to view test plug statistics counters. 472 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 473: Cna Test Plug Configuration Example

    Configuring and monitoring CNA test plugs CNA test plug configuration example 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: G350-001(super)# show cna testplug CNA testplug 1 is administratively down, test-plug status is unregistered...
  • Page 474 Test rate limiter: Maximum 60 tests in 10 seconds Last Test: traceroute to 135.64.103.107 Result: ip1=149.49.75.178 ip2=135.64.103.107 ttl_len = 4 Test Count Failed Cancelled ---------- ------ ------ --------- traceroute ping tcpconnect merge 474 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 475: Resetting The Cna Test Plug Counters

    G350-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 Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 119: CNA test plug CLI commands Root level command...
  • Page 476 Root level command Command Description Enable or disable the CNA test plug service on cna-testplug-service the gateway Display CNA test plug configuration and show cna testplug statistics 2 of 2 476 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 477: Configuring Echo Cancellation

    However, the best echo cancellation policy varies depending on each specific call configuration. The G250/G350 has an internal table for determining which VoIP engine and analog card echo cancellers to enable on a case-by-case basis. This table is consulted when the default auto mode is specified in the echo cancellation CLI commands.

  • Page 478: Summary Of Echo Cancellation Commands

    Use the show echo-cancellation command to display current settings for echo ● cancellers within the G250/G350. Summary of echo cancellation commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 120: Echo cancellation CLI commands Command...

  • Page 479: Integrated Analog Testing - Test And Heal

    MM714 hardware vintage 10 and above ● MM716 ● The embedded analog media module in the G250, and in the G350 hardware vintage 6 ● and above For detailed information about accepted values and recommended corrections, see Users Guide to the Integrated Analog Trunk Measurements, 132167.

  • Page 480: Types Of Test Lines

    Sends a 2804 Hz tone at -16 dBm for 9 seconds ● Remains quiet for 30 second ● Sends a 2225 Hz tone (progress tone) at -16 dBm for half a second ● Forces disconnect ● 480 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 481: Setting Up A Test Profile

    Once you set up a test profile, you can run it whenever necessary using the single launch command. In the G350, you can define up to 30 profiles; in the G250, you can define up to five profiles. 1. Enter analog-test to enter the analog-test context.

  • Page 482: Displaying And Clearing Profiles

    You can use the cancel command to abort an analog test that is currently running. Displaying test results In the analog-test context, use the show result command to display the result of the ● latest measurements performed for a particular profile. 482 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 483: Healing Trunks

    Integrated analog testing – Test and Heal In the analog-test-profile context, use the show result command to display the ● results of the latest measurements performed by the test profile. If a test did not succeed, the output indicates the reason for the test failure. Healing trunks You can manually tune three parameters on each analog trunk port: balance, receive-gain, and transmit gain.

  • Page 484: Summary Of Integrated Analog Testing Commands

    Configuring monitoring applications Summary of integrated analog testing commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 121: Integrated analog testing CLI commands Root Level First level Second level command Description Commands...
  • Page 485 Integrated analog testing – Test and Heal Table 121: Integrated analog testing CLI commands (continued) Root Level First level Second level command Description Commands command Display the results of the show result latest measurement obtained by this test profile Set the balance on a specific set balance port Set the receive-gain on a...
  • Page 486 Configuring monitoring applications 486 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 487: Chapter 18: Configuring The Router

    Chapter 18: Configuring the router The Avaya G250 and Avaya G350 Media Gateways each have an internal router. You can configure the following routing features on the router: Interfaces ● Unnumbered IP interfaces ● Routing table ● GRE tunneling ●...

  • Page 488: Router Interface Concepts

    The switching interface supports VLANs. By default, the switching interface is associated with the first VLAN (Vlan 1). When you configure the G250/G350 without an external VPN or firewall, Vlan 1 is used to connect the internal G250/G350 router to the internal G250/G350 switch. If an external firewall or VPN is connected to the Fast Ethernet port, it is important to disable Vlan 1 to prevent a direct flow of packets from the WAN to the LAN.

  • Page 489: Layer 2 Logical Interfaces

    VLAN (on the Switching Interface). The G250/G350 switch can have multiple VLANs ● defined within its switching fabric. Both the G250 and the G350 router support up to eight VLANs that can be configured over their internal switching interface connections.

  • Page 490: Interface Configuration Examples

    Use the show interface brief command to display a summary of the configuration information for a specific interface or for all of the interfaces. Summary of basic interface configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 122: Basic interface configuration CLI commands...
  • Page 491 Configuring interfaces Table 122: Basic interface configuration CLI commands (continued) Root level Command Description command Assign an IP address and mask to an interface ip address or delete an interface Set the administrative state of an IP interface ip admin-state Update the interface broadcast address ip broadcast- address...

  • Page 492: Configuring Unnumbered Ip Interfaces

    Modem dial-backup requires unnumbered IP to be configured on the Dialer interface of the branch gateway and at both the default and the backup dialing destinations. 492 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 493: Configuring Unnumbered Ip On An Interface

    G250-001(super-if:Dialer 1)# dialer persistent delay 1 G250-001(super-if:Dialer 1)# dialer modem-interface USB-modem //to configure IP unnumbered on the Dialer interface, borrowing the IP address from vlan interface 1, configured above: G250-001(super-if:Dialer 1)# ip unnumbered 1 Vlan 1 G250-001(super-if:Dialer 1)# exit G250-001(super)# ! Issue 5 June 2008...

  • Page 494: Summary Of Unnumbered Ip Interface Configuration Commands

    LOCAL 180.0.0.0 Loopback 1 180.0.0.1 LOCAL Summary of unnumbered IP interface configuration commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 123: Unnumbered IP interface configuration CLI commands Root level Command Description...

  • Page 495: Routing Sources

    Routing sources Routing sources The G250/G350 router supports both static and dynamic routing per interface. You can configure static routes with two levels of priority, high and low, and you can enable and configure Open Shortest Path First (OSPF) and Routing Information Protocol (RIP) dynamic routing protocols.

  • Page 496: Configuring Next Hops

    Next-hop IP address. Specifies the IP address of a router as a next hop. The next hop ● router must belong to one of the directly attached networks for which the Avaya G250/G350 Media Gateway has an IP interface. Static route types Two kinds of static routes can be configured: High Preference static routes.

  • Page 497: Deleting A Route And Its Next Hops

    Configuring the routing table Note: If you apply tracking to a static route, you can only configure one next hop for the Note: route. Next hops can only be added to an existing static route if they have the same preference and metric as the currently defined next hops.

  • Page 498: Permanent Static Route

    218. Permanent static route The Avaya G250/G350 Media Gateway enables you to configure a static route as a permanent route. Configuring this option prevents the static route from becoming inactive when the underlying Layer 2 interface is down. This prevents routing table updates from being sent each time an interface goes up or down when there is a fluctuating Layer 2 interface on the static route.

  • Page 499: Routing Table Commands

    Enter traceroute, followed by an IP address, to trace the route an IP packet would ● follow to the specified IP address. The G250/G350 traces the route by launching UDP probe packets with a small TTL, then listening for an ICMP time exceeded reply from a gateway.

  • Page 500: Summary Of Routing Table Commands

    Configuring the router Summary of routing table commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 124: Routing table CLI commands Command Description Delete all the dynamic routing entries from the routing table...

  • Page 501: Configuring Gre Tunneling

    Configuring GRE tunneling Configuring GRE tunneling Generic Routing Encapsulation (GRE) is a multi-carrier protocol that encapsulates packets with an IP header and enables them to pass through the Internet via a GRE tunnel. A GRE tunnel is a virtual interface in which two routers serve as endpoints. The first router encapsulates the packet and sends it over the Internet to a router at the far end of the GRE tunnel.

  • Page 502: Preventing Nested Tunneling In Gre Tunnels

    In addition to checking for nested tunneling, the G250/G350 prevents loops in connection with GRE tunnels by preventing the same packet from being encapsulated more than once in the G250/G350.

  • Page 503: Recommendations On Avoiding Nested Tunneling

    Configuring GRE tunneling Using the network shown in Figure 35 as an illustration, if Router 1 has an entry in its routing table regarding the tunnel’s receiving endpoint, this will cause an internal route in which all packets exiting the tunnel will be redirected back into the tunnel itself. Figure 35: Nested tunneling example Recommendations on avoiding nested tunneling Announce policy.

  • Page 504: Optional Gre Tunnel Features

    The keepalive command includes the following parameters: seconds. The length, in seconds, of the interval at which the source interface sends ● keepalive packets. The default value is 10. 504 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 505: Dynamic Mtu Discovery

    Configuring GRE tunneling retries. The number of retries after which the source interface declares that the tunnel is ● down. The default value is 3. 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 interface concludes that the tunnel is down.

  • Page 506: Setting Up A Gre Tunnel

    The Avaya G250/G350 Media Gateway does not check whether the configured Note: tunnel source IP address is an existing IP address registered with the G250/G350 router. 4. In most cases, it is recommended to configure keepalive in the tunnel so that the tunnel’s source interface can determine and inform the host if the tunnel is down.

  • Page 507: Additional Gre Tunnel Parameters

    Additional GRE tunnel parameters Use the following commands to configure additional GRE tunnel parameters. For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Use the tunnel checksum command in the GRE Tunnel interface context to add a ●...

  • Page 508: Gre Tunnel Application Example

    Internet. Instead, Router 1 receives the packet from host 1, looks up the packet’s destination address in its routing table, and determines that the next hop to the destination address is the remote end of the GRE tunnel. 508 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 509 Configuring GRE tunneling Router 1 encapsulates the packet with a GRE header and a new IP header that assigns the IP address of Router 2 (12.0.0.20) as the destination IP address and the IP address of Router 1 (11.0.0.10) as the source IP address. When the packet arrives at Router 2, which is the end point of the GRE tunnel, Router 2 removes the outer IP header and the GRE header and sends the packet to its original destination at IP address (8.0.0.2).

  • Page 510: Summary Of Gre Tunneling Commands

    Configuring the router Summary of GRE tunneling commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 125: GRE tunneling CLI commands Root level Command Description command Enter tunnel interface configuration context, interface...

  • Page 511: Configuring Dhcp And Bootp Relay

    DHCP and BOOTP packets. The router also relays replies from the server back to the client. The G250/G350 can alternatively function as a DHCP server, providing DHCP service to local devices. For information about configuring DHCP server on the G250/G350, see...

  • Page 512: Dhcp/Bootp Relay

    Note: protocols. When there is more than one IP interface on a VLAN, the G250/G350 chooses the lowest IP address on this VLAN when relaying DHCP/BOOTP requests. The DHCP/BOOTP server then uses this address to decide the network from which to allocate the address. When there are multiple networks configured, the G250/G350 performs a round-robin selection process.

  • Page 513: Dhcp/Bootp Relay Commands

    Summary of DHCP and BOOTP relay commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 126: DHCP and BOOTP relay CLI commands...

  • Page 514: Configuring Dhcp Server

    DHCP requests by data devices are routed to a central remote DHCP server using DHCP relay. The Avaya G250/G350 Media Gateway can function as a DHCP server or as a DHCP client, or both simultaneously. For information about configuring DHCP client on the G250/G350, see Configuring DHCP client on page 218.

  • Page 515: Typical Dhcp Server Application

    Create a minimum of two dynamic pools: at least one pool for data devices (PCs) and at least one pool for voice devices (IP phones). The G250/G350 also supports reservation pools, which map hardware addresses/client identifiers to specific IP addresses.

  • Page 516: Dhcp Server Cli Configuration

    256 IP addresses, you must first use the no start ip address and no end ip address commands before configuring the new start and end IP addresses. 516 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 517: Configuring Options

    Configuring DHCP server Configuring Options DHCP options are various types of network configuration information that the DHCP client can receive from the DHCP server. The G250/G350 supports all DHCP options. The most common options used for IP phones are listed in Table 127.

  • Page 518: Configuring Vendor-Specific Options

    Use the next-server command to specify the IP address of the next server in the boot ● process of a DHCP client. Use the server-name command to specify the optional server name in the boot process ● of a DHCP client. 518 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 519: Dhcp Pool Configuration Examples

    Done! G350-001(super-DHCP 1)# subnet-mask 255.255.255.0 Done! G350-001(super-DHCP 1)# default-router 135.64.20.1 Done! G350-001(super-DHCP 1)# option 176 G350-001(super-DHCP 1/option 176)# name "Avaya IP phone option" Done! G350-001(super-DHCP 1/option 176)# value ascii "MCIPADD=10.10.2.140, MCPORT=1719, TFTPSRVR=10.10.5.188" Done! G350-001(super-DHCP 1/option 176)# exit G350-001(super-DHCP 1)# exit...
  • Page 520 The following example configures a vendor-specific option for DHCP pool 5: G350-001(super-DHCP 5)# vendor-specific-option 1 G350-001(super-DHCP 5/vendor specific 1)# class-identifier "ccp.avaya.com" Done! G350-001(super-DHCP 5/vendor specific 1)# value raw ascii "gfdgfd" Done! G350-001(super-DHCP 5/vendor specific 1)# exit G350-001(super-DHCP 5)# 520 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 521: Displaying Dhcp Server Information

    Configuring DHCP server The following example defines a reservation pool for data devices: G350-001(super)# ip dhcp pool 3 G350-001(super-DHCP 3)# name "Data 1 Server" Done! G350-001(super-DHCP 3)# start-ip-addr 135.64.20.61 Done! G350-001(super-DHCP 3)# end-ip-addr 135.64.20.61 Done! G350-001(super-DHCP 3)# subnet-mask 27 Done! G350-001(super-DHCP 3)# client identifier 01:11:22:33:44:55:66 Done! G350-001(super-DHCP 3)# default-router 135.64.20.33...

  • Page 522: Summary Of Dhcp Server Commands

    Configuring the router Summary of DHCP Server commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 128: DHCP server CLI commands Root level First level Second level Description command command command Delete IP address binding...
  • Page 523 Configuring DHCP server Table 128: DHCP server CLI commands (continued) Root level First level Second level Description command command command Set the end IP address of the end-ip-addr range of available IP addresses that the DHCP server may assign to clients Configure the lease period for IP lease address assignment...

  • Page 524: Configuring Broadcast Relay

    For each interface on the Avaya G250/G350 Media Gateway, you can configure whether the G250/G350 forwards directed broadcast packets to the network address or subnet mask address of the interface.

  • Page 525: Netbios Rebroadcast

    Network Basic Input Output System (NetBIOS) is a protocol for sharing resources among desktop computers on a LAN. You can configure the Avaya G250/G350 Media Gateway to relay NetBIOS UDP broadcast packets. This feature is used for applications such as WINS that use broadcast but might need to communicate with stations on other subnetworks or VLANs.

  • Page 526: Configuring The Arp Table

    Static ARP table entries do not expire. You add static ARP table entries manually using the arp command. For example, to add a static ARP table entry for station 192.168.7.8 with MAC address 00:40:0d:8c:2a:01, use the following command: G350-001# arp 192.168.7.8 00:40:0d:8c:2a:01 526 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 527 Configuring the ARP table Dynamic ARP table entries are mappings between IP addresses and 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: Use the no arp command to remove static and dynamic entries from the ARP table.

  • Page 528: Arp Table Commands

    Use the show ip reverse-arp command to display the IP address of a host, based on ● a known MAC address. Summary of ARP table commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 130: ARP table CLI commands Command...

  • Page 529: Enabling Proxy Arp

    Proxy ARP can help devices on a subnet to reach remote subnets without the need to configure routing or a default gateway. To enable proxy ARP on a G250/G350 interface, enter ip proxy-arp. Use the no form of this command to disable proxy ARP on an interface.

  • Page 530: Configuring Icmp Errors

    Enter show ip icmp to display the status (enabled or disabled) of ICMP error messages. ● Summary of ICMP errors commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 132: ICMP errors CLI commands...

  • Page 531: Ripv1

    Internet. However the very simplicity of RIP has a disadvantage. This protocol does not take into account network bandwidth, physical cost, and data priority. The Avaya G250/G350 Media Gateway supports two versions of RIP: RIPv1 ●...

  • Page 532: Rip Distribution Access Lists

    You can assign the rules per interface and per direction. Up to 99 RIP distribution access lists can be configured on the Avaya G250/G350 Media Gateway. For example, to configure RIP distribution access list number 10 permitting distribution and learning of network 10.10.0.0, do the following:...

  • Page 533: Rip Limitations

    That is, RIPv1 and RIPv2 routers should not be configured on the same subnetwork. However, you can configure different IP interfaces of the G250/G350 with different RIP versions. This configuration is valid as long as all routers on the subnet are configured with the same version.

  • Page 534: Summary Of Rip Commands

    Use the timers basic command to set RIP timers. Use the no form of this command to ● set the RIP timers to their default values. Summary of RIP commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 134: RIP CLI commands Root level command...
  • Page 535 Configuring RIP Table 134: RIP CLI commands (continued) Root level command Command Description Set the authentication string used ip rip on the interface authentication Specify the type of authentication ip rip used in RIP v2 packets authentication mode Enable learning of the default route ip rip received by the RIP protocol.

  • Page 536: Configuring Ospf

    (topography). You can configure route redistribution between OSPF, RIP, and static routes. With route redistribution, you can configure the G250/G350 to redistribute routes learned from one protocol into the domain of the other routing protocol. For more information, see Route redistribution page 541.

  • Page 537: Ospf Dynamic Cost

    The G250/G350 can be installed in the OSPF backbone area (area 0.0.0.0) or in any OSPF area that is part of a multiple areas network. However, the G250/G350 cannot be configured to be an OSPF area border router itself.
  • Page 538 Use the show ip ospf database command to display lists of information related to the ● OSPF database for a specific router. Use the show ip ospf interface command to display the OSPF-related interface ● information. 538 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 539: Summary Of Ospf Commands

    ● calculation. Use the no form of this command to restore the default value. Summary of OSPF commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 135: OSPF CLI commands Root level command...
  • Page 540 Display the OSPF-related interface show ip ospf information interface Display OSPF neighbor show ip ospf information on a per-interface neighbor basis Display OSPF parameters and show ip protocols statistics 2 of 2 540 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 541: Route Redistribution

    Static routes are, by default, redistributed to RIP and OSPF. The G250/G350 allows the user to globally disable redistribution of static routes to RIP, and separately to globally disable redistribution of static routes to OSPF. In addition you can configure, on a per static route basis, whether the route is to be redistributed to RIP and OSPF, and what metric to use (in the range of 1-15).

  • Page 542: Summary Of Route Redistribution Commands

    Router RIP or Router OSPF contexts. This value is used for all types of redistributed routes, regardless of the protocol from which the route was learned. Summary of route redistribution commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 136: Route redistribution CLI commands...

  • Page 543: Vrrp Configuration Example

    Configuring VRRP The concept underlying VRRP is that a router can back up other routers, in addition to performing its primary routing functions. This redundancy is achieved by introducing the concept of a virtual router. A virtual router is a routing entity associated with multiple physical routers.

  • Page 544: Vrrp Commands

    There is one main router on IP subnet 20.20.20.0, such as a G350, C363T, C364T, or any router that supports VRRP, and a backup router. You can configure more backup routers. The G250/G350 itself must have an interface on the IP subnetwork, for example, ●...

  • Page 545: Summary Of Vrrp Commands

    VRRP routing. Use the show ip vrrp command to display VRRP information. ● Summary of VRRP commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 137: VRRP CLI commands Root level Command...

  • Page 546: Configuring Fragmentation

    2 of 2 Configuring fragmentation The G250/G350 supports IP fragmentation and reassembly. The G250/G350 router can fragment and reassemble IP packets according to RFC 791. This feature allows the router to send and receive large IP packets where the underlying data link protocol constrains the Maximum Transport Unit (MTU).

  • Page 547: Fragmentation Commands

    Enter show fragment to display information regarding fragmented IP packets that are ● destined to a router. Summary of fragmentation commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 138: Fragmentation CLI commands Command...
  • Page 548 Configuring the router 548 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 549: Chapter 19: Configuring Ipsec Vpn

    IPSec SAs secure the actual traffic between the protected networks behind the peers, while the IKE SA only secures the key exchanges that generate the IPSec SAs between the peers. The G250/G350 IPSec VPN feature is designed to support site-to-site topologies, in which the two peers are gateways.

  • Page 550: G250/G350 R3.0 Vpn Capabilities

    Object tracking on page 319. NAT Traversal ● The G250/G350 supports both IETF NAT-T methods and the standard method, as well as Avaya’s proprietary method Stronger encryption algorithms (AES with 192 bit key and AES with 256 bit key) ●...

  • Page 551: G250/G350 R3.1 Vpn Capabilities

    G250/G350 R3.1 VPN capabilities R3.1 VPN supports the following, in addition to the R3.0 capabilities: Support for configurations in which the G250/G350 acts as a regional VPN hub for ● dynamically addressed peers. This is achieved by supporting Aggressive Mode as a responder in an IKE Phase-1 negotiation.

  • Page 552: Overview Of Ipsec Vpn Configuration

    The basic IPSec VPN building blocks define how to secure packets, as follows: ISAKMP policies. Define parameters for IKE phase 1 negotiation ● Transform-sets. Define parameters for IKE phase 2 negotiation ● 552 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 553 Once the building blocks are defined, IPSec VPN is implemented using a crypto list. The crypto list defines, for the interface to which it applies, which packets should be secured and how, as follows: 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.

  • Page 554: Summary Of Configuration Steps

    - isakmp-policy - pre-shared-key - initiate mode - self-identity - keepalive - keepalive-track - continuous-channel (Optional) ISAKMP peer group – crypto isakmp peer-group ● - description - set peer 554 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 555 Crypto map – crypto map ● - description - set transform-set - set peer or set peer-group - set dscp - continuous-channel IP crypto list – ip crypto-list ● - local-address - ip-rule description ● source-ip ● destination-ip ● ● protect crypto map ip-protocol ●...

  • Page 556: Configuring A Site-To-Site Ipsec Vpn

    Installing the VPN license file To enable IPSec VPN you must obtain and install a VPN license. For information on obtaining a VPN license, see Installing and Upgrading the Avaya G250 Media Gateway, 03-300434 or Installing and Upgrading the Avaya G350 Media Gateway, 03-300394.

  • Page 557: Configuring Ipsec Vpn

    Installing the VPN license file on page 556. IPSec VPN configuration overview To configure a site-to-site IPSec VPN, two devices (the G250/G350 and a peer Gateway) must be configured symmetrically. In some cases, you may wish to configure global VPN parameters (see...

  • Page 558: Configuring Isakmp Policies

    Possible values are md5 and sha (default). Use the group command to set the Diffie-Hellman group for the ISAKMP policy. ● Possible values are 1 (default), 2, 5 and 14. 558 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 559: Configuring Transform-Sets

    Configuring a site-to-site IPSec VPN Use the lifetime command to set the lifetime of the ISAKMP SA, in seconds. The ● range of values is 60-86,400 seconds (default is 86,400). For example: G350-001(config-isakmp:1)# description "lincroft ike" Done! G350-001(config-isakmp:1)# authentication pre-share Done! G350-001(config-isakmp:1)# encryption des Done!
  • Page 560 G350-001(config-transform:ts1)# set security-association lifetime seconds 7200 Done! G350-001(config-transform:ts1)# set security-association lifetime kilobytes 268435456 G350-001(config-transform:ts1)# mode tunnel Done! 3. Exit the crypto transform-set context with the exit command. G350-001(config-transform:ts1)# exit G350-001# 560 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 561: Configuring Isakmp Peer Information

    Note: If you wish to specify the ISAKMP peer by its FQDN name, you must configure Note: the G250/G350 as a DNS client (see DNS resolver on page 98), and verify that the peer’s name is listed in a DNS server.
  • Page 562 GNpi1odGNBrB5z4GJL G350-001(config-peer:149.49.70.1)# pre-shared-key Done! Alternatively, you can obtain a cryptographic-grade random key from the G250/G350 with the suggest-key command, and then enter it using the pre-shared-key command. The suggested key-length can vary from 8-127 alphanumeric characters, or from 8-64 bytes represented in hexadecimal notation. The default length is 32 characters.
  • Page 563 (for more information on continuous-channel see Enabling continuous channel page 585). 7. Specify the branch device (G250/G350) by its address or by the FQDN name that identifies the G250/G350 in the remote peer, using the self-identity command. For example: G350-001(config-peer:149.49.70.1)# self-identity address Done! G350-001(config-peer:149.49.70.1)# self-identity fqdn vpn.avaya.com...

  • Page 564: Configuring An Isakmp Peer-Group

    (and to create the peer-group if it does not exist). For example: G350-001# crypto isakmp peer-group NY-VPN-group G350-001(config-peer-grp:NY-VPN-group)# 2. Use the description command to enter a description for the ISAKMP peer-group. For example: G350-001(config-peer-grp:NY-VPN-group)# description “Avaya peer group” Done! 564 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 565: Configuring Crypto Maps

    Configuring a site-to-site IPSec VPN 3. Add a peer to the list of peers in the group, using the set peer command: Specify the peer’s name or address. ● Optionally enter an index number, specifying the relative position of the peer within the ●...
  • Page 566 IPSec. For more information on continuous-channel Enabling continuous channel on page 585. For example: G350-001(config-crypto:1)# continuous-channel Done! 7. Exit crypto map context with the exit command. For example: G350-001(config-crypto:1)# exit G350-001# 566 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 567: Configuring Crypto Lists

    A crypto list is an ordered list of ip-rules that control which traffic requires IPSec protection and which does not, based on IP groups (source and destination IP addresses and wildcard). A crypto list is activated on an interface. The G250/G350 can have multiple crypto lists activated on different interfaces.
  • Page 568 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 568 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 569: Deactivating Crypto Lists To Modify Ipsec Vpn Parameters

    Configuring a site-to-site IPSec VPN commands see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Note that this fine-tuning is not applicable for rules whose action is protect crypto map. - ip-protocol. Specify the IP protocol to match. - tcp. Specify the TCP settings to match.

  • Page 570: Configuring And Assigning An Access Control List

    IP addresses. An organization with a single public IP address can use a NAT device to connect multiple computers to the Internet sharing a single public IP address. However, NAT causes compatibility problems for many types of network applications, including VPN. 570 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 571 NAT translation alive in the NAT device, and not let it age-out due to periods of inactivity. Set the NAT Traversal keepalive interval on the G250/G350 to be less than the NAT translation aging time on the NAT device. For example:...

  • Page 572: Assigning A Crypto List To An Interface

    The crypto ipsec minimal-pmtu command is intended for advanced users only. ● It sets the minimal PMTU value which can be applied to an SA when the G250/G350 participates in Path MTU Discovery (PMTUD) for the tunnel pertaining to that SA.

  • Page 573: Ipsec Vpn Maintenance

    Displaying IPSec VPN configuration You can use the following show commands to display IPSec VPN configuration. For a full description of the commands and their output fields see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Use the show crypto ipsec transform-set command to display configuration for a ●...

  • Page 574: Displaying Ipsec Vpn Status

    Note: recommended order of operations is: First clear the IPSec SAs with the clear crypto sa all command, then clear the ISAKMP SA with the clear crypto isakmp command. 574 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 575: Ipsec Vpn Logging

    IPSec VPN maintenance IPSec VPN logging IPSec VPN logging allows you to view the start and finish of IKE phase 1 and IKE phase 2 negotiations. Most importantly, it displays the configuration of both peers, so that you can pinpoint the problem in case of a mismatch between the IPSec VPN configuration of the peers. Note: For more information about logging, see Configuring logging on page...

  • Page 576: Typical Installations

    The Broadband Internet connection uses cable or DSL modem, with a static public IP ● address There is a VPN tunnel from each spoke to the VPN hub over the Internet ● Only VPN traffic is allowed via the Internet connection ● 576 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 577: Configuring The Simple Vpn Topology

    Typical installations Figure 41: Simple VPN topology: VPN hub and spokes Configuring the simple VPN topology 1. Configure each branch as follows: The default gateway is the Internet interface ● VPN policy is configured on the Internet interface egress as follows: ●...
  • Page 578 This enables the PMTUD application to work Egress All allowed services Permit This traffic is tunnelled from any IP address using VPN to any local subnet Egress Default Deny 578 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 579: Configuration Example

    Typical installations Configuration example crypto isakmp policy 1 encryption aes hash sha group 2 exit crypto isakmp peer address <Main Office Public Internet Static IP Address> pre-shared-key <secret key> isakmp-policy 1 exit crypto ipsec transform-set ts1 esp-3des esp-sha-hmac set pfs 2 exit crypto map 1 set peer <Main OfficeMain Office Public Internet Static IP...
  • Page 580 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 580 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 581 Typical installations 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 desintation-ip any source-ip host <Branch Subnet1> <Branch Subnet1 Mask> composite-operation Permit exit ip-rule 50 destination-ip any source-ip host <Branch Subnet2>...

  • Page 582: Using Dynamic Local Peer Ip

    IP addresses to computers wishing to communicate over IP. These temporary addresses are called dynamic IP addresses. The G250/G350 IPSec VPN feature provides dynamic local peer IP address support. To work with dynamic local peer IP, you must first configure some prerequisites and then instruct the G250/G350 to learn the IP address dynamically using either PPPoE or DHCP client.
  • Page 583 PPP over Ethernet (PPPoE) is a client-server protocol used for carrying Note: PPP-encapsulated data over Ethernet frames. You can configure PPPoE on the G250/G350’s ETH WAN Fast Ethernet port. For more information about PPPoE on the G250/G350, see Configuring PPPoE on page 279.
  • Page 584 ! Activate the Ingress and Egress ACLs on the FastEthernet Interface G350-001(config)# interface fastethernet 10/2 G350-001(config-if:FastEthernet 10/2)# ip access-group 301 in Done! G350-001(config-if:FastEthernet 10/2)# ip access-group 302 out Done! 584 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 585: Enabling Continuous Channel

    However, there are advantages to keeping the connection continuously alive, such as eliminating the waiting time necessary to construct a new IPSec VPN connection. The G250/G350 IPSec VPN feature supports continuous channel, which maintains a continuous IPSec VPN connection. That means that when you activate the ip crypto-group command on the defined interface, the IPSec VPN tunnel is immediately started, even if no traffic is traversing the interface and the timeouts have expired.

  • Page 586: Full Or Partial Mesh

    ● There is a VPN tunnel from one spoke to another spoke ● Only VPN traffic is allowed via the Internet connection ● Figure 42: Full or partial mesh 586 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 587 Typical installations Configuring the mesh VPN topology 1. Configure Branch Office 1 as follows: The default gateway is the Internet interface ● VPN policy is configured on the Internet interface egress as follows: ● Traffic from the local subnets to the second spoke subnets -> encrypt, using tunnel ●...
  • Page 588 Traffic ACL parameter Description direction value Ingress IKE from Main Office IP to Permit Branch IP Ingress ESP from Main Office IP to Permit Branch IP 1 of 2 588 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 589 Typical installations Table 141: Configuring the mesh VPN topology – Branch Office 2 (continued) Traffic ACL parameter Description direction value Ingress IKE from First Branch IP to Permit Branch IP Ingress ESP from First Branch IP to Permit Branch IP Ingress ICMP from any IP address to Permit...
  • Page 590 <Second Branch Subnet1> <Second Branch Subnet1 Mask> protect crypto map 2 exit ip-rule 3 source-ip <Branch Subnet1> <Branch Subnet1 Mask> destination-ip <Second Branch Subnet2> <Second Branch Subnet2 Mask> protect crypto map 2 exit 590 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 591 Typical installations ip-rule 4 source-ip <Branch Subnet2> <Branch Subnet2 Mask> destination-ip <Second Branch Subnet2> <Second Branch Subnet2 Mask> protect crypto map 2 exit ip-rule 10 source-ip <Branch Subnet1> <Branch Subnet1 Mask> destination-ip protect crypto map 1 exit ip-rule 20 source-ip <Branch Subnet2> <Branch Subnet2 Mask> destination-ip protect crypto map 1 exit...
  • Page 592 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 composite-operation Permit exit 592 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 593 Typical installations 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 destination-ip any source-ip host <Branch Subnet2> <Branch Subnet2 Mask> composite-operation Permit exit ip-rule default composite-operation deny...
  • Page 594 <First Branch Subnet1> <Second Branch Subnet1 Mask> protect crypto map 2 exit ip-rule 3 source-ip <Branch Subnet1> <Branch Subnet1 Mask> destination-ip <First Branch Subnet2> <Second Branch Subnet2 Mask> protect crypto map 2 exit 594 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 595 Typical installations ip-rule 4 source-ip <Branch Subnet2> <Branch Subnet2 Mask> destination-ip <First Branch Subnet2> <Second Branch Subnet2 Mask> protect crypto map 2 exit ip-rule 10 source-ip <Branch Subnet1> <Branch Subnet1 Mask> destination-ip protect crypto map 1 exit ip-rule 20 source-ip <Branch Subnet2> <Branch Subnet2 Mask> destination-ip protect crypto map 1 exit...
  • Page 596 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 composite-operation Permit exit 596 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 597 Typical installations 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 destination-ip any source-ip host <Branch Subnet2> <Branch Subnet2 Mask> composite-operation Permit exit ip-rule default composite-operation deny...

  • Page 598: Full Solution: Hub And Spoke With Vpn

    The local hosts access the Internet directly through the local broadband connection ● The PSTN connection backs up the voice bearer ● Figure 43: Full solution: hub-and-spoke with VPN for data and VoIP control backup 598 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 599 Typical installations Configuring hub-and-spoke with VPN for data and VoIP control backup 1. Configure the Branch Office as follows: The default gateway is the Internet interface ● VPN policy is configured on the Internet interface egress as follows: ● Traffic from the local GRE tunnel endpoint to the remote GRE tunnel endpoint -> encrypt, using IPSec tunnel mode, with the remote peer being the Main Office.
  • Page 600 - Destination IP = branch VoIP subnet(s) or GW address (PMI), DSCP = control -> Route: 1. WAN 2. DBR ACM is configured to route voice calls through PSTN when the main VoIP trunk is ● down 600 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 601 Typical installations Configuration example crypto isakmp policy 1 encryption aes hash sha group 2 authentication pre-share exit crypto isakmp peer address <Main Office Internet public Static IP Address> pre-shared-key <key1> isakmp-policy 1 exit crypto ipsec transform-set ts1 esp-3des esp-sha-hmac exit crypto map 1 set peer <Main Office Internet public Static IP Address>...
  • Page 602 <Branch voice Subnet> <Branch voice Subnet Mask> composite-operation Permit exit ip-rule default composite-operation deny exit exit ip access-control-list 302 ip-rule 10 source-ip any destination-ip any ip-protocol udp udp destination-port eq Ike composite-operation Permit exit 602 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 603 Typical installations 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 source-ip any destination-ip any ip-protocol esp composite-operation Permit exit ip-rule 30 source-ip any...
  • Page 604 ! 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 604 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 605: Typical Failover Applications

    IP address before establishing an IKE connection. Your DNS server should be able to provide an IP address of a living host. The G250/G350 will perform a new DNS query and try to re-establish the VPN connection to the newly provided IP address whenever it senses that the currently active remote peer stops responding.

  • Page 606: Failover Using Gre

    ● Failover using GRE A branch with a G250/G350 can connect to two or more VPN hub sites, in a way that will provide either redundancy or load sharing. In this topology, the G250/G350 is connected through its 10/100 WAN Ethernet port to a DSL modem.
  • Page 607 Typical installations Figure 44: Hub and spoke with hub redundancy/load sharing using GRE Configuring VPN hub redundancy and load sharing topologies using GRE 1. Configure the Branch Office as follows: VPN policy is configured on the Internet interface egress as follows: ●...
  • Page 608 ● modifications The GRE Tunnel interface is configured for the branch ● Dynamic routing (OSPF or RIP) is configured to run over the GRE interface to the ● branch 608 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 609 Typical installations Configuration example crypto isakmp policy 1 encryption aes hash sha group 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 IP Address>...
  • Page 610 Permit exit ip-rule 50 source-ip any destination-ip host <Branch Office Public Internet Static IP Address> ip-protocol icmp composite-operation Permit exit ip-rule 60 source-ip any destination-ip any composite-operation Permit exit 610 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 611 Typical installations ip-rule 70 source-ip host <Backup Main Office GRE Tunnel end point IP Address> destination-ip host <Branch GRE Tunnel end point IP Address> composite-operation Permit exit ip-rule default composite-operation deny exit exit ip access-control-list 302 ip-rule 30 source-ip any destination-ip any ip-protocol udp udp destination-port eq Ike...
  • Page 612 Tunnel 2 keepalive 10 3 tunnel source <Branch GRE Tunnel end point IP Address> tunnel destination <Backup Main Office GRE Tunnel end point IP Address> ip address 20.20.20.1 255.255.255.252 exit 612 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 613: Failover Using Dns

    VPN peers. On the G250/G350 configure that hostname as your remote peer. The G250/G350 will perform a DNS query in order to resolve the hostname to an IP address before establishing an IKE connection. Your DNS server should be able to provide an IP address of a living host.
  • Page 614 Permit IKE Traffic (UDP port 500) for VPN control traffic (IKE) ● Permit ESP traffic (IP Protocol ESP) for VPN data traffic (IPSEC) ● Permit ICMP traffic, to support PMTU application support, for a better fragmentation ● process 614 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 615 Typical installations For each private subnet, add a permit rule, with the destination being the private ● subnet and the source being any. This traffic will be allowed only if it tunnels under the VPN, because of the crypto list. Define all other traffic (default rule) as deny in order to protect the device from ●...
  • Page 616 ! that is accessible without VPN. ip domain name-server-list 1 name-server 1 123.124.125.126 exit ! Define the IKE Entity crypto isakmp policy 1 encryption aes hash sha group 2 authentication pre-share exit 616 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 617 Typical installations ! Define the remote peer as FQDN (DNS Name) crypto isakmp peer fqdn main-vpn.avaya.com pre-shared-key <key1> isakmp-policy 1 exit ! Define the IPSEC Entity crypto ipsec transform-set ts1 esp-3des esp-sha-hmac exit ! Define the VPN Tunnel crypto map 1 set peer main-vpn.avaya.com...
  • Page 618 Permit exit ip-rule 30 source-ip destination-ip ip-protocol icmp composite-operation Permit exit ip-rule 40 source-ip destination-ip 10.0.10.0 0.0.0.255 composite-operation Permit exit ip-rule 50 source-ip destination-ip 10.0.20.0 0.0.0.255 composite-operation Permit exit 618 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 619 Typical installations 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 udp destination-port eq dns composite-operation Permit exit ip-rule 10 source-ip destination-ip ip-protocol udp destination-port eq Ike composite-operation Permit exit...
  • Page 620 ! Activate the crypto list and the access control list on the public interface interface fastethernet 10/2 ip crypto-group 901 ip access-group 301 in ip access-group 302 out exit 620 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 621: Failover Using A Peer-Group

    Typical installations Failover using a peer-group The failover VPN topology utilizes a peer-group which lists a group of redundant peers. At any point in time, only one peer is active and acting as the remote peer. An object tracker monitors the state of the active peer.
  • Page 622 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 G250/G350 will then pass on to the next peer in the peer group list.
  • Page 623 Typical installations Permit ICMP traffic, to support PMTU application support, for a better fragmentation ● process For each private subnet, add a permit rule, with the destination being the private ● subnet, and the source being any. This traffic will be allowed only if it tunnels under the VPN, because of the crypto list.
  • Page 624 10.0.20.1 255.255.255.0 exit ! Define the Public Subnet interface fastethernet 10/2 ip address 100.0.0.2 255.255.255.0 exit ! Define the default gateway the public interfce ip default-gateway 100.0.0.1 624 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 625 Typical installations ! 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 rtr 1 type echo protocol ipIcmpEcho <host1 IP>...
  • Page 626 "Fast Ethernet 10/2.0" 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 626 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 627 Typical installations ! Define the Ingress access control list for the public interface ip access-control-list 301 ip-rule 10 source-ip destination-ip ip-protocol udp destination-port eq 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...
  • Page 628 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 ip-rule default composite-operation deny exit exit 628 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 629: Checklist For Configuring Site-To-Site Ipsec Vpn

    301 in ip access-group 302 out exit Checklist for configuring site-to-site IPSec VPN Table 144 to gather the information for simple G250/G350 site-to-site IPSec VPN. Table 144: Checklist for configuring site-to-site IPSec VPN Parameter Possible values Actual value 1.
  • Page 630 2,560 to 536,870,912 ● default: 4,608,000 kb disable ● 6. Which packets should be secured a. Protect rules matching IP source address ● options IP destination address ● 2 of 3 630 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 631 Checklist for configuring site-to-site IPSec VPN Table 144: Checklist for configuring site-to-site IPSec VPN (continued) Parameter Possible values Actual value b. Bypass rules matching IP source address ● options IP destination address ● ● ● dscp ● fragment ● icmp ●...

  • Page 632: Summary Of Vpn Commands

    Configuring IPSec VPN Summary of VPN commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 145: VPN CLI commands Root level command First level Second level Description command command Flush a specific ISAKMP SA or all...
  • Page 633 Summary of VPN commands Table 145: VPN CLI commands (continued) Root level command First level Second level Description command command Enter the crypto ISAKMP peer crypto isakmp context and create or edit an peer ISAKMP peer Enable continuous-channel IKE, continuous- which keeps the IKE phase1 channel session always up and running,...
  • Page 634 Set the DSCP value in the set dscp tunneled packet Attach a peer to a crypto map set peer Attach a peer-group to a crypto set peer-group Configure the transform-set transform-set 3 of 5 634 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 635 Set the minimal PMTU value that crypto ipsec can be applied to an SA when the minimal-pmtu G250/G350 participates in PMTUD for the tunnel pertaining to that SA Activate a crypto list in the context of the interface on which the crypto...
  • Page 636 Display information about a show ip specific policy list or all lists active-lists Display all or specific crypto list show ip configurations crypto-list 5 of 5 636 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 637: Chapter 20: Configuring Policy

    Global rules. A set of rules that are executed before the list is evaluated ● Rule list. A list of filtering rules and actions for the G250/G350 to take when a packet ● matches the rule. Match actions on this list are pointers to the composite operation table.

  • Page 638: Network Security Using Access Control Lists

    IP addresses, protocols, ports, IP fragments, or DSCP values. Figure 47 illustrates how access control lists are used to control traffic into and out of your network. Figure 47: Network security using access control lists 638 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 639: Qos Lists

    DSCP values or CoS values, and can be based on specific values or groups of IP addresses, protocols, ports, IP fragments, or DSCP values. When a packet matches a rule on the QoS list, the G250/G350 sets one or both of the QoS fields in the packet. The following table shows these QoS fields:...

  • Page 640: Managing Policy Lists

    Configuring policy Managing policy lists You can manage policy lists on the Avaya G250/G350 Media 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.

  • Page 641: Defining List Identification Attributes

    ● Defining list identification attributes The policy list attributes including name, owner, and cookie, are used by Avaya QoS Manager software to identify policy lists. 1. Enter the context of the policy list in which you want to define the attribute.

  • Page 642: Default Actions

    Configuring policy Default actions When no rule matches a packet, the G250/G350 applies the default action for the list. The following table shows the default action for each type of policy list: List Default action Access control list Accept all packets...

  • Page 643: Packets Exiting The Interface

    G250/G350. You can choose the ingress QoS list and the egress QoS list from among the QoS lists that are configured on the G250/G350.

  • Page 644: Device-Wide Policy Lists

    Device-wide policy lists You can attach a policy list (other than a policy-based routing list) to every interface on the G250/G350 using one command. To do this, attach a list to the Loopback 1 interface. For more information, see Attaching policy lists to an interface on page 642.

  • Page 645: Defining Global Rules

    Defining rules on page 645. The G250/G350 applies global rules before applying individual rules. 1. Enter the context of the access control list in which you want to define the rule. 2. Enter one of the following commands, followed by the name of a composite command: - ip-fragments-in.

  • Page 646: Editing And Creating Rules

    Rules work in the following ways, depending on the type of list and the type of information in the packet: Layer 4 rules in an access control list with a Permit operation are applied to non-initial ● fragments 646 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 647: Ip Protocol

    Defining rules Layer 4 rules in an access control list with a Deny operation are not applied to non-initial ● fragments, and the device continues checking the next IP rule. This is to prevent cases in which fragments that belong to other L4 sessions may be blocked by the other L4 session which is blocked.

  • Page 648: Source And Destination Port Range

    ● which the rule applies Equal. Type eq, followed by a port name or number, to set a port name or port number to ● which the rule applies 648 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 649: Icmp Type And Code

    Defining rules Greater than. Type gt, followed by a port name or port number, to apply the rule to all ● ports with a name or number greater than the specified name or number Less than. Type lt, followed by a port name or port number, to apply the rule to all ports ●...

  • Page 650: Tcp Establish Bit (Access Control Lists Only)

    G350-001(ACL 301/ip rule 5)# dscp 56 Composite Operation For instructions on assigning a composite operation to an ip rule, see Adding composite operation to an ip rule on page 653. 650 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 651: Composite Operations

    Composite operations Composite operations A composite operation is a set of operations that the G250/G350 can perform when a rule matches a packet. Every rule in a policy list has an operation field that specifies a composite operation. The operation field determines how the G250/G350 handles a packet when the rule matches the packet.

  • Page 652: Pre-Configured Composite Operations For Qos Lists

    CoS or the DSCP value. If the composite operation is set to No Change, the operation makes no change to the packet’s QoS tags. 652 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 653: Configuring Composite Operations

    Composite operations Configuring composite operations You can configure additional composite operations for QoS lists. You can also edit composite operations that you configured. You cannot edit pre-configured composite operations. Note: You cannot configure additional composite operations for access control lists, Note: since all possible composite operations are pre-configured.

  • Page 654: Composite Operation Example

    The following commands create a new composite operation called dscp5 and assign the new composite operation to rule 3 in QoS list 402. If the packet matches a rule, the G250/G350 changes the value of the DSCP field in the packet to 5.

  • Page 655: Changing An Entry In The Dscp Table

    QoS rules on the list take precedence over the DSCP table. If a QoS rule other than the default matches the packet, the G350 does not apply the DSCP table to the packet. The G250/G350 applies only the operation specified in the QoS rule.

  • Page 656: Displaying And Testing Policy Lists

    - show dscp-table. Displays the current list’s DSCP table - show ip-rule. Displays a list of all rules configured for the list - show list. Displays the parameters of the current list, including its rules 656 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 657: Simulating Packets

    IP address. You may also specify other parameters. For a full list of parameters, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. For example, the following command simulates the effect of applying QoS list number 401 to a packet entering the G350 through interface VLAN 2: G350-001(if:VLAN 2)# ip simulate 401 in CoS1 dscp46 10.1.1.1...

  • Page 658: Summary Of Access Control List Commands

    Configuring policy When you use the ip simulate command, the G250/G350 displays the effect of the policy rules on the simulated packet. For example: G350-001(super-if:VLAN 2)# ip simulate 401 in CoS1 dscp46 10.1.1.1 10.2.2.2 tcp 1182 20 Rule match for simulated packet is the default rule...
  • Page 659 Summary of access control list commands Table 149: Access control list CLI commands (continued) Root level Command Command Description command Specify the action taken on ip-fragments-in incoming IP fragmentation packets for the current access control list Specify the action taken on ip-option-in incoming packets carrying an IP option for the current access...
  • Page 660 Copy an existing policy list to a new list policy-list- copy Display the attributes of a show ip specific access control list or of access-control all access control lists -list 3 of 3 660 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 661: Summary Of Qos List Commands

    Summary of QoS list commands Summary of QoS list commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 150: QoS list CLI commands Root level Command Command Description command Enter the Dialer, Serial,...
  • Page 662 Apply the current rule to packets ip-protocol with the specified IP protocol Display the parameters of the show composite operation assigned to composite- the current rule operation 2 of 3 662 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 663 Summary of QoS list commands Table 150: QoS list CLI commands (continued) Root level Command Command Description command Display the current list’s DSCP show table dscp-table Display the attributes of the show ip-rule current rule Apply the current rule to packets source-ip from the specified source IP address...
  • Page 664 Configuring policy 664 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 665: Chapter 21: Configuring Policy-Based Routing

    Each PBR list includes a set of rules, and each rule includes a next hop list. Each next hop list contains up to 20 next hop destinations to which the G250/G350 sends packets that match the rule. A destination can be either an IP address or an interface.

  • Page 666: Applications

    WAN line, and not the Internet. You can configure a PBR list to drop voice packets when the WAN line is down. 666 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 667: Configuring Policy-Based Routing

    Configuring policy-based routing Configuring policy-based routing For a full example of a policy-based routing configuration, see Application example page 674. 1. Define PBR lists. In general context, enter ip pbr-list followed by a list number in the range ● 800-899. For example: G350-001(super)# ip pbr-list 802 G350-001(super-PBR 802)# To assign a name to the list, use the name command, followed by a text string, in the...
  • Page 668 218. A next hop list can include the value NULL0. When the next hop is NULL0, the G250/G350 drops the packet. However, you cannot apply tracking to NULL0. 668 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 669 Configuring policy-based routing The following example creates next hop list 1, named “Data to HQ”, with three entries: The first entry is IP address 172.16.1.221. Object tracker 3 is applied to monitor the ● route. For details about configuring the object tracker see Object tracking configuration on page 320.

  • Page 670: Pbr Rules

    It is recommended to leave a gap between rule numbers, in order to leave room Note: for inserting additional rules at a later time. For example, ip-rule 10, ip-rule 20, ip-rule 30. 670 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 671: Modifying Rules

    Next hop lists PBR rules include a next hop list. When the rule matches a packet, the G250/G350 routes the packet according to the specified next hop list. Each next hop list can include up to 20 entries. An entry in a next hop list can be either an IP address or an interface.

  • Page 672: Modifying Next Hop Lists

    3 deletes the third entry from the next hop list. Canceling tracking and keeping the next hop 1. Enter the context of the next hop list. 2. Use the next-hop-ip or next-hop-interface command again, without the track keyword. 672 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 673: Changing The Object Tracker And Keeping The Next Hop

    Editing and deleting PBR lists Changing the object tracker and keeping the next hop 1. Enter the context of the next hop list. 2. Use the next-hop-ip or next-hop-interface command again, with the track keyword followed by the new track index. Editing and deleting PBR lists You cannot delete or modify a PBR list when it is attached to an interface.

  • Page 674: Application Example

    - show ip pbr-list list number detailed. Displays all the parameters of the specified PBR list - show ip active-lists. Displays a list of each G250/G350 interface to which a PBR list is attached, along with the number and name of the PBR list - show ip active-lists list number.
  • Page 675 This example includes a voice VLAN (6) and a data VLAN (5). The PMI is on VLAN 6. The G250/G350 is managed by a remote Media Gateway Controller (MGC) with the IP address 149.49.43.210. The G250/G350 also includes a local S8300 in LSP mode.

  • Page 676: Configuration For The Sample Policy-Based Routing Application

    G350-001(super-PBR 801/ip rule 40)# next-hop list 1 Done! G350-001(super-PBR 801/ip rule 40)# destination-ip 149.49.123.0 0.0.0.255 Done! G350-001(super-PBR 801/ip rule 40)# dscp 46 Done! G350-001(super-PBR 801/ip rule 40)# exit G350-001(super-PBR 801)# exit G350-001(super)# 676 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 677 The next set of commands applies the PBR list to the Loopback interface. This is necessary to ensure that voice packets generated by the G250/G350 itself are routed via the E1/T1 line. The Loopback interface is a logical interface that is always up. Packets sent from the G250/G350, such as signaling packets, are sent via the Loopback interface.
  • Page 678 (for more information on object tracking, refer to Object tracking on page 319). Note that the GRE tunnel itself has keepalive and can detect the status of the interface and, therefore, modify the next hop status. 678 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 679: Simulating Packets In Pbr

    Policy-based routing supports the ip simulate command for testing policies. Refer to Simulating packets on page 657. Summary of policy-based routing commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 151: Policy-based routing CLI commands Root level...
  • Page 680 Apply the rule to UDP packets from the specified source port source-port Assign a name to the specified list or name operation 2 of 3 680 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 681 Summary of policy-based routing commands Table 151: Policy-based routing CLI commands (continued) Root level First level Second level Description command command command Specify the owner of the current list owner Display the attributes of a specific show ip-rule rule or all rules Display information about the show list specified list...
  • Page 682 Configuring policy-based routing 682 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 683: Chapter 22: Setting Synchronization

    Chapter 22: Setting synchronization If the Avaya G350 Media Gateway contains an MM710 T1/E1 media module, it is advisable to define the MM710 as the primary synchronization source for the G350. In so doing, clock synchronization signals from the Central Office (CO) are used by the MM710 to synchronize all operations of the G350.

  • Page 684: Synchronization Status

    Setting synchronization If the Avaya G250 or Avaya G350 Media Gateway includes a second MM710 media module, enter the following additional command: set sync interface secondary v3 set sync source secondary If, for any reason, the primary MM710 media module cannot function as the clock synchronization source, the system uses the MM710 media module located in slot 3 of the Avaya G350 Media Gateway chassis as the clock synchronization source.

  • Page 685: Displaying Synchronization Status

    Configured when a source has not been defined, for example, when there are no T1 cards installed. Summary of synchronization commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 152: Synchronization CLI commands...
  • Page 686 Setting synchronization 686 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 687: Chapter 23: Fips

    Chapter 23: FIPS The G250, G250-BRI, and G350 are multi-chip stand-alone cryptographic modules in commercial grade metal case. The modules provide: VPN, Voice over Internet Protocol (VoIP) media-gateway services, Ethernet switching, IP ● routing, and data security for IP traffic Status output via LEDs and logs available through the module’s management interface...
  • Page 688 153, Table 154 Table 155 describe the functions of the physical and logical fixed ports, buttons, and LEDs on the G250 front panel. Table 153: Physical and logical interfaces on the G250-Analog front panel Physical Quantity Description FIPS 140-2 logical...
  • Page 689 Table 153: Physical and logical interfaces on the G250-Analog front panel (continued) Physical Quantity Description FIPS 140-2 logical Comments interface interface CONSOLE Console port for direct Control inputs Supports cryptographic ● connection of CLI module administration Status output ● console.
  • Page 690 Link state and activity ● indication on the associated data interface ETH LAN LAN status LEDs Status output Link state and activity ● indication on the associated data interface 690 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 691: G250-Bri Image And Interfaces

    156, Table 157 Table 158 describe the functions of the physical and logical fixed ports, buttons, and LEDs on the G250-BRI front panel. Table 156: Physical and logical interfaces on the G250-BRI front panel Physical Quantity Description FIPS 140-2 logical...
  • Page 692 FIPS Table 156: Physical and logical interfaces on the G250-BRI front panel (continued) Physical Quantity Description FIPS 140-2 logical Comments interface interface RJ-45 port for ACS Power output Contact Closure Adjunct. ● (308) contact closure Powers two contact- adjunct box closure relays.
  • Page 693 Table 156: Physical and logical interfaces on the G250-BRI front panel (continued) Physical Quantity Description FIPS 140-2 logical Comments interface interface USB port. Supports: Control inputs ● Multitech Status output ● ● MultiModemUSB MT5634ZBA-USB- V92 USB modem USB flash (for ●...
  • Page 694 Link state and activity ● indication on the associated data interface ETH LAN LAN status LEDs Status output Link state and activity ● indication on the associated data interface 694 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 695: G250-Dcp Image And Interfaces

    153, Table 154 Table 155 describe the functions of the physical and logical fixed ports, buttons, and LEDs on the G250-DCP front panel. Table 159: Physical and logical interfaces on the G250-DCP front panel Physical Quantity Description FIPS 140-2 logical...
  • Page 696 FIPS Table 159: Physical and logical interfaces on the G250-DCP front panel (continued) Physical Quantity Description FIPS 140-2 logical Comments interface interface ETH WAN RJ-45 Ethernet LAN Data input Supports wide area ● switch port network connectivity Data output ●...
  • Page 697 Table 159: Physical and logical interfaces on the G250-DCP front panel (continued) Physical Quantity Description FIPS 140-2 logical Comments interface interface USB port. Supports: Control inputs ● Multitech Status output ● ● MultiModemUSB MT5634ZBA-USB- V92 USB modem USB flash (for ●...
  • Page 698 Test in progress ● Call activity ● System System status LEDs Status output Indicate: ● Modem connection ● through the Console interface Alarm state ● CPU activity ● Power ● 698 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 699: G250-Ds1 Image And Interfaces

    153, Table 154 Table 155 describe the functions of the physical and logical fixed ports, buttons, and LEDs on the G250-DS1 front panel. Table 162: Physical and logical interfaces on the G250-DS1 front panel Physical Quantity Description FIPS 140-2 logical...
  • Page 700 FIPS Table 162: Physical and logical interfaces on the G250-DS1 front panel (continued) Physical Quantity Description FIPS 140-2 logical Comments interface interface T1/E1 T1/E1 and a PRI trunk Data input ● port Data output ● Status output ● Control input ●...
  • Page 701 Table 162: Physical and logical interfaces on the G250-DS1 front panel (continued) Physical Quantity Description FIPS 140-2 logical Comments interface interface USB port. Supports: Control inputs ● Multitech Status output ● ● MultiModemUSB MT5634ZBA-USB- V92 USB modem USB flash (for ●...
  • Page 702 Console interface Alarm state ● CPU activity ● Power ● ETH WAN T1/E1/PRI trunk Status output Link state and activity ● interface LEDs indication on the associated data interface 702 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 703: G350 Image And Interfaces

    G350 Image and interfaces Figure 56: Image of the G350 cryptographic module 16 17 10 11 12 Figure notes: 1. V6 — high-density media module slot 9. Analog line ports 2. V2 — standard media module slot 10. CCA (Contact Closure) port 3.
  • Page 704 Status output ● Control input ● CONSOLE Console port for direct Control inputs Supports cryptographic ● connection of CLI module administration Status output ● console. RJ-45 connector. 1 of 2 704 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 705 Table 165: Physical and logical interfaces on the G350 front panel (continued) Physical Quantity Description FIPS 140-2 logical Comments interface interface USB port. Supports: Multitech ● MultiModemUSB MT5634ZBA-USB- V92 USB modem USB flash (for ● backup and restore) Externally powered ●...

  • Page 706: Supported Algorithms

    DES CBC for encryption of IPSec, and IKE (only supported for communication with legacy ● VPN systems) TDES CBC Encryption of the serial number date for Voice feature activation controlled by ● the ICC CM server/external blade server 706 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 707: Non-Approved Algorithms In Fips Mode

    Non-Approved Algorithms in FIPS mode Diffie-Hellman for IKE key exchanges - groups 2, 5, and 14 ● MD5 for Radius Client role and peer OSPF router authentication ● HMAC-MD5-96 for SNMPv3 authentication ● The cryptographic module relies on the implemented deterministic random number generator (DRNG) that is compliant with X9.31 with 128-bit Key, 64-bit Seed for generation of all cryptographic keys.

  • Page 708: Security Level

    Cryptographic Module Specification Module Port and Interfaces Roles, Services, and Authentication Finite State Model Physical Security Operational Environment Cryptographic Key Management EMI/EMC Self-Tests Design Assurance Mitigation of Other Attacks 708 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 709: Operational Environment

    The FIPS 140-2 Area 6 Operational Environment requirements are not applicable because the device does not support the loading and execution of un-trusted code. Avaya digitally signs firmware images of the crypto module using RSA SHA1 digital signature. Through this signature, the crypto module verifies the authenticity of any update to its firmware image.
  • Page 710 An entity that facilitates authentication IPSec VPNs Serial Number Role-based verification TDES encrypted Gateway exchanges its Peer challenge serial number with a Server to enable feature activation 2 of 2 710 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 711: Assumptions Concerning User Behavior

    ● three) Device managed locally via direct link to Console port, and remotely via IPSec tunnel only ● Commands are documented in the Avaya G250 and Avaya G350 CLI Reference, ● 03-300437 Critical security parameters and private keys Table 171 describes the CSPs (Critical Security Parameters) defined in the module.
  • Page 712 Used for authentication of default CLI user during first setup Radius Secret Used for hashing password with MD5. One secret common to both Primary and Secondary Radius server. 2 of 3 712 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 713: Public Keys

    (Avaya root CA RSA public key) The Avaya Root certificate is hard-coded in the Gateway image and is used directly for authentication of the chain of trust of the Avaya Signing Authority that is downloaded together with the software. License download public key Used for authentication of license file validity.

  • Page 714: Csp Access Rights Within Roles And Services

    Read all status indications: obtain all statuses securely via IPSEC, console port, and LEDs on the Gateway’s front panel 1 of 2 714 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 715 Table 173: CSP access rights within roles and services (continued) Service Role Read subset of status indications: obtain subset of statuses securely via IPSEC, console port and LEDs on the Gateway’s front panel Module configuration backup: backup non-CSP related configuration data via IPSEC Module configuration restore: restore...
  • Page 716 IKE Session phase-1 secret (SKEYID_d) IKE phase-1 HMAC Key (SKEYID_a) IKE Session phase-1 key (SKEYID_e) IKE Session phase-1 TDES IKE Session phase-1 DES IKE Session phase-1 AES 1 of 3 716 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 717 Table 174: Role and service access to CSPs (continued) IKE phase-1 TDES key (SKEYID-e) Nonce IPSEC SA phase-2 TDES IPSEC SA phase-2 AES IPSEC SA phase-2 HMAC keys IPSEC SA phase-2 keys per protocol Ephemeral DH phase-2 private key DH phase-2 shared secret User password Root password...

  • Page 718: Security Rules

    3. When the module has not been placed in a valid role, the operator does not have access to any cryptographic services. 4. Use DES to encrypt message traffic only for communications with legacy products that do not support AES or TDES. 718 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 719 8. Data output is inhibited during key generation, self-tests, zeroization, and error states. 9. The module supports concurrent operators and maintains separation of roles and services. 10. Users can plug-in and use any Avaya Media Module that does not support cryptographic functionality without restriction.

  • Page 720: Password Guidelines

    FIPS-approved mode of operation. Also note that execution of the NVRAM Init or zeroize commands clear the above defined FIPS-approved mode configuration and returns the box to factory defaults. 720 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 721: Prerequisites

    Administration Procedures Prerequisites Avaya Communication Manager 2.2 or higher ● FIPS-ready gateway ● - Check the Material Code in Table 175. The material code is on the product label on the rear panel of the gateway. Table 175: Material codes of FIPS-compliant media gateways...

  • Page 722: Fips-Related Cli Commands

    ● enhanced security ● ● show self-test-status For a full description see Avaya G250 and Avaya G350 CLI Reference, 03-300437 Prerequisites for entering FIPS mode User type – crypto officer ● FIPS-approved hardware. Version 3.0.x or higher. ● FIPS-approved Media Gateway firmware. Refer to the “Validation Lists for cryptographic ●...

  • Page 723: Entering Fips Mode

    Administration Procedures Entering FIPS mode 1. Log in to the device through the local console port. - User name: root - Password: root Note: Use the password “root” when the Media Gateway is running with the factory Note: default configuration. Login: root Password: **** Password accepted...
  • Page 724 : 00:04:0d:6d:30:e1 WAN MAC address : 00:04:0d:6d:30:e1 Serial No : 03IS07639510 Model No : G250-BRI HW Vintage HW Suffix FW Vintage : 24.11.0 HW ready for FIPS : Yes 724 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 725 Phone Image 10 phone-ImageB Phone Image 10 phone-ImageC Phone Image 10 phone-ImageD Phone Image 10 dhcp-binding DHCP Binding Nv-Ram Ip Address Binding For the G250: ● G250-N(super)# dir M# file ver num file type file location file description -- ---- --------...
  • Page 726 9. If a more recent FIPS-approved G250/G350 image is available, download it using the image download procedures. - Use the copy tftp image command. 10. If it has not yet been installed, download the Avaya License file with the VPN feature activated. - Use the copy tftp license-file command.
  • Page 727 Note: Otherwise you cannot establish a signaling link after disabling encryption in the Media Gateway. 15. Disable Avaya Media Encryption (SRTP, AEA, RTP/AES). - Enter disable media encryption and confirm the operation. G350-001(super)# disable media encryption Warning: The following command will disable the media encryption functionality and it cannot be rolled back.
  • Page 728 ------ ---------- root admin local password b. If there are redundant CLI users, use the no username command to delete them. Note that you cannot delete the root user. 728 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 729 Administration Procedures c. Use the show snmp user command to list SNMPv3 users. G350-001(super)# show snmp user EngineId: 80:00:1a:e9:03:00:04:0d:29:ca:61 (local) User Name: initial Authentication Protocol: none Privacy Protocol: none Storage Type: nonVolatile Row Status: active d. If there are redundant local SNMP users, use the no snmp-server user command to delete them.
  • Page 730 33. Configure primary and secondary RADIUS servers. G350-001(super)# Set radius authentication enable Done! G350-001(super)# set radius authentication server 200.200.200.20 primary Done! G350-001(super)# set radius authentication secret fips_test1 Done! 730 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 731 Inhibits output data traffic during powerup/error states ● Inhibits modification of the active IPSEC transform-set parameters ● In the G250 only: the G250 switches from performing symmetric encryption with a ● hardware accelerator, to software-based encryption - Enter enhanced security.
  • Page 732 FIPS 37. Define an Access Control list that blocks packets with an IP destination address of any of the G250/G350 interfaces for the following protocols, and activate the ACL on the inbound direction of all clear-text interfaces. TELNET ● ●...
  • Page 733 Administration Procedures ip-rule 15 composite-operation "Deny" ip-protocol tcp destination-ip host 10.3.0.3 tcp destination-port eq Telnet exit ip-rule 20 composite-operation "Deny" ip-protocol tcp destination-ip host 1.0.0.1 tcp destination-port eq Ftp exit ip-rule 21 composite-operation "Deny" ip-protocol tcp destination-ip host 10.0.0.1 tcp destination-port eq Ftp exit ip-rule 22 composite-operation "Deny"...
  • Page 734 42 composite-operation "Deny" ip-protocol udp destination-ip host 10.20.0.1 udp destination-port eq Snmp exit ip-rule 43 composite-operation "Deny" ip-protocol udp destination-ip host 100.100.100.1 udp destination-port eq Snmp exit 734 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 735 ----------- ----------------- ----------------- ---- --- -- ----- ----- --- San Jose 111.110.110.112 IPv4 Address MM none New Jersey 149.49.70.1 vpn.ca.avaya.com AM on-de b. Use the no crypto isakmp peer address command to delete redundant VPN peers. G350-001(super)# no crypto isakmp peer address 149.49.70.1 Done! Issue 5 June 2008...
  • Page 736 G350-001# crypto ipsec transform-set ts1 esp-3des esp-sha-hmac comp-lzs G350-001(config-transform:ts1)# exit 43. Configure Crypto Maps using the crypto map command. G350-001# crypto map 1 G350-001(super-crypto:1)# set transform-set ts1 Done! G350-001(super-crypto:1)# set peer 20.0.0.2 Done! G350-001(crypto-map)# exit 736 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 737 Administration Procedures 44. Define one or more IPSec Crypto lists that provide encryption rules for traffic that needs protection. Use the ip crypto-list command. G350-001(super)# ip crypto-list 901 G350-001(super-Crypto 901)# local-address “FastEthernet 10/2.0” Done! G350-001(super-Crypto 901)# ip-rule 10 G350-001(super-Crypto 901/ip rule 10)# protect crypto map 1 Done! G350-001(super-Crypto 901/ip rule 10)# source-ip any Donw!

  • Page 738: Failure Scenarios And Repair Actions

    48. Physically re-connect the network interfaces. Failure scenarios and repair actions The G250/G350 initiates power up tests automatically, without the need for operator intervention, and executes tests in the order defined below. The power-up self-tests are executed during the early boot sequence and before the G350’s data output interfaces are enabled and begin transmitting packets.

  • Page 739: Error States

    "PRNG integrity power-up self test" "Passed" "Crypto integrity power-up self test" "Passed" "EEPROM integrity power-up self test" "Passed" If the G250/G350 fails a conditional or power-up self-test, the module enters the error state. All data output interfaces are immediately blocked. Error states...

  • Page 740: Recovering From An Error State

    If the G350 does not recover from Error State 3, the secrets and other definitions SECURITY ALERT: are retained. If this information is highly sensitive, you should not send the G250/ G350 for repair. 740 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 741 Administration Procedures Figure 57: Recovering from an error state Power down Gatew ay Power up Gateway Gateway operates correctly? D elete setup Perform N VR AM initialization R econfigure Gateway Gateway operates correctly? C ontact Avaya representative Issue 5 June 2008...

  • Page 742: Summary Of Fips Commands

    FIPS Summary of FIPS commands For more information about these commands, see Avaya G250 and Avaya G350 CLI Reference, 03-300437. Table 177: FIPS configuration CLI commands Command Description Disable H.248 signalling encryption disable link encryption Disable Avaya media encryption (SRTP, AEA, RTP/...

  • Page 743: Appendix A: Traps And Mibs

    Appendix A: Traps and MIBs This appendix contains a list of all G250/G350 traps and all MIBs. G250/G350 traps Name Parameters Class Severity Trap Name/ Format Description (MIB variables) Facility Mnemonic coldStart Boot Warning coldStart Agent Up with A coldStart trap indicates...
  • Page 744 Redundancy $1 manager of the deletion Trap Status definition deleted of the specified redundant link, which is identified by the softRedundancyId. It is enabled/disabled by chLntAgConfigChangeTr aps. 2 of 9 744 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 745 G250/G350 traps Name Parameters Class Severity Trap Name/ Format Description (MIB variables) Facility Mnemonic createSW soft P330 SWITCH Info createSWRedu Software The trap is generated on Redundancy Redundancy FABRIC ndancyTrap Redundancy $1 the creation of the Trap Status definition created redundant links for the specified ports.
  • Page 746 Module $2 Inline This trap reports the FaultMask, FltOK Power Supply correction of a failure on genGroupId, failure was cleared an inline power supply. genGroup BUPSActivity Status 4 of 9 746 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 747 G250/G350 traps Name Parameters Class Severity Trap Name/ Format Description (MIB variables) Facility Mnemonic WanPhysical ifIndex, Critical Cable Problem on An E1/T1/serial cable AlarmOn ifAdminStatus, Physical port $4 was disconnected. ifOperStatus, AlarmOn ifName, ifAlias, dsx1Line Status wanPhysical ifIndex, Notification wan...
  • Page 748 This trap reports a PwrFlt Index, NTITY PwrFlt power supply Fault problem with a 3.3V entPhysical power supply. Descr, entPhySensor Value, avEntPhy SensorHi Warning, avEntPhy SensorLo Warningent Physical ParentRelPos 6 of 9 748 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 749 G250/G350 traps Name Parameters Class Severity Trap Name/ Format Description (MIB variables) Facility Mnemonic avEnt2500mv entPhysical AVAYA-E SUPPLY avEnt2500mv 2.5V (2500mv) This trap reports a PwrFlt Index, NTITY PwrFlt power supply Fault problem with a 2.5V entPhysical power supply. Descr,...
  • Page 750 Fault correction of a problem entPhysical Cleared with a 1.8V power supply. Descr, entPhySensor Value, avEntPhy SensorHi Warning, avEntPhy SensorLo Warningent Physical ParentRelPos 8 of 9 750 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 751: G250/G350 Mib Files

    Descr, to the acceptable range entPhySensor for the device. Value, avEntPhy SensorHi Warning, entPhysical ParentRelPos 9 of 9 G250/G350 MIB files MIB File MIB Module Supported by G250/G350 Load.MIB LOAD-MIB RFC1315-MIB.my RFC1315-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...
  • Page 752 IF-MIB.my IF-MIB DS0BUNDLE-MIB.my DS0BUNDLE-MIB RFC1406-MIB.my RFC1406-MIB DS0-MIB.my DS0-MIB POLICY-MIB.MY POLICY-MIB BRIDGE-MIB.my BRIDGE-MIB CONFIG-MIB.MY CONFIG-MIB G700-MG-MIB.MY G700-MG-MIB FRAME-RELAY-DTE-MIB.my FRAME-RELAY-DTE-MIB IP-MIB.my IP-MIB Load12.MIB LOAD-MIB PPP-LCP-MIB.my PPP-LCP-MIB WAN-MIB.MY WAN-MIB 2 of 3 752 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 753: Mib Files In The Load.mib File

    G250/G350 MIB files MIB File MIB Module Supported by G250/G350 SNMPv2-MIB.my SNMPv2-MIB USM-MIB.my USM-MIB VACM-MIB.my VACM-MIB OSPF-MIB.my OSPF-MIB Tunnel-MIB.my TUNNEL-MIB 3 of 3 MIB files in the Load.MIB file The following table provides a list of the MIBs in the Load.MIB file that are supported by the...

  • Page 754: Mib Files In The Rfc1315-Mib.my File

    The following table provides a list of the MIBs in the RFC1315-MIB.my file that are supported by the G250/G350 and their OIDs: Object frDlcmiIfIndex 1.3.6.1.2.1.10.32.1.1.1 frDlcmiState 1.3.6.1.2.1.10.32.1.1.2 1 of 3 754 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 755 G250/G350 MIB files Object frDlcmiAddress 1.3.6.1.2.1.10.32.1.1.3 frDlcmiAddressLen 1.3.6.1.2.1.10.32.1.1.4 frDlcmiPollingInterval 1.3.6.1.2.1.10.32.1.1.5 frDlcmiFullEnquiryInterval 1.3.6.1.2.1.10.32.1.1.6 frDlcmiErrorThreshold 1.3.6.1.2.1.10.32.1.1.7 frDlcmiMonitoredEvents 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 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...

  • Page 756: Mib Files In The Q-Bridge-Mib.my File

    1.3.6.1.2.1.17.7.1.1.4 dot1qGvrpStatus 1.3.6.1.2.1.17.7.1.1.5 dot1qVlanTimeMark 1.3.6.1.2.1.17.7.1.4.2.1.1 dot1qVlanIndex 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 756 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 757: Mib Files In The Entity-Mib.my File

    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 dot1qPortGvrpLastPduOrigin 1.3.6.1.2.1.17.7.1.4.5.1.6 MIB files in the ENTITY-MIB.my file The following table provides a list of the MIBs in the ENTITY-MIB.my file that are supported by the G250/G350 and their OIDs: Object entPhysicalIndex 1.3.6.1.2.1.47.1.1.1.1.1 entPhysicalDescr 1.3.6.1.2.1.47.1.1.1.1.2 entPhysicalVendorType 1.3.6.1.2.1.47.1.1.1.1.3 entPhysicalContainedIn 1.3.6.1.2.1.47.1.1.1.1.4...

  • Page 758: Mib Files In The Ip-Forward-Mib.my File

    1.3.6.1.2.1.4.24.4.1.2 ipCidrRouteTos 1.3.6.1.2.1.4.24.4.1.3 ipCidrRouteNextHop 1.3.6.1.2.1.4.24.4.1.4 ipCidrRouteIfIndex 1.3.6.1.2.1.4.24.4.1.5 ipCidrRouteType 1.3.6.1.2.1.4.24.4.1.6 ipCidrRouteProto 1.3.6.1.2.1.4.24.4.1.7 ipCidrRouteAge 1.3.6.1.2.1.4.24.4.1.8 ipCidrRouteInfo 1.3.6.1.2.1.4.24.4.1.9 ipCidrRouteNextHopAS 1.3.6.1.2.1.4.24.4.1.10 ipCidrRouteMetric1 1.3.6.1.2.1.4.24.4.1.11 ipCidrRouteMetric2 1.3.6.1.2.1.4.24.4.1.12 ipCidrRouteMetric3 1.3.6.1.2.1.4.24.4.1.13 ipCidrRouteMetric4 1.3.6.1.2.1.4.24.4.1.14 ipCidrRouteMetric5 1.3.6.1.2.1.4.24.4.1.15 ipCidrRouteStatus 1.3.6.1.2.1.4.24.4.1.16 758 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 759: Mib Files In The Vrrp-Mib.my File

    G250/G350 MIB files MIB files in the VRRP-MIB.my file The following table provides a list of the MIBs in the VRRP-MIB.my file that are supported by the G250/G350 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...

  • Page 760: Mib Files In The Utilization-Management-Mib.my File

    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 760 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 761: Mib Files In The Entity-Sensor-Mib.my File

    G250/G350 MIB files MIB files in the ENTITY-SENSOR-MIB.my file The following table provides a list of the MIBs in the ENTITY-SENSOR-MIB.my file that are supported by the G250/G350 and their OIDs: Object entPhySensorType 1.3.6.1.2.1.99.1.1.1.1 entPhySensorScale 1.3.6.1.2.1.99.1.1.1.2 entPhySensorPrecision 1.3.6.1.2.1.99.1.1.1.3 entPhySensorValue 1.3.6.1.2.1.99.1.1.1.4 entPhySensorOperStatus 1.3.6.1.2.1.99.1.1.1.5...

  • Page 762: Mib Files In The Applic-Mib.my File

    The following table provides a list of the MIBs in the DS1-MIB.my file that are supported by the G250/G350 and their OIDs: Object dsx1LineIndex 1.3.6.1.2.1.10.18.6.1.1 dsx1IfIndex 1.3.6.1.2.1.10.18.6.1.2 dsx1TimeElapsed 1.3.6.1.2.1.10.18.6.1.3 dsx1ValidIntervals 1.3.6.1.2.1.10.18.6.1.4 1 of 3 762 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 763 G250/G350 MIB files Object dsx1LineType 1.3.6.1.2.1.10.18.6.1.5 dsx1LineCoding 1.3.6.1.2.1.10.18.6.1.6 dsx1SendCode 1.3.6.1.2.1.10.18.6.1.7 dsx1CircuitIdentifier 1.3.6.1.2.1.10.18.6.1.8 dsx1LoopbackConfig 1.3.6.1.2.1.10.18.6.1.9 dsx1LineStatus 1.3.6.1.2.1.10.18.6.1.10 dsx1SignalMode 1.3.6.1.2.1.10.18.6.1.11 dsx1TransmitClockSource 1.3.6.1.2.1.10.18.6.1.12 dsx1Fdl 1.3.6.1.2.1.10.18.6.1.13 dsx1InvalidIntervals 1.3.6.1.2.1.10.18.6.1.14 dsx1LineLength 1.3.6.1.2.1.10.18.6.1.15 dsx1LineStatusLastChange 1.3.6.1.2.1.10.18.6.1.16 dsx1LineStatusChangeTrapEnable 1.3.6.1.2.1.10.18.6.1.17 dsx1LoopbackStatus 1.3.6.1.2.1.10.18.6.1.18 dsx1Ds1ChannelNumber 1.3.6.1.2.1.10.18.6.1.19 dsx1Channelization 1.3.6.1.2.1.10.18.6.1.20 dsx1CurrentIndex 1.3.6.1.2.1.10.18.7.1.1 dsx1CurrentESs 1.3.6.1.2.1.10.18.7.1.2 dsx1CurrentSESs 1.3.6.1.2.1.10.18.7.1.3...
  • Page 764 1.3.6.1.2.1.10.18.8.1.12 dsx1IntervalValidData 1.3.6.1.2.1.10.18.8.1.13 dsx1TotalIndex 1.3.6.1.2.1.10.18.9.1.1 dsx1TotalESs 1.3.6.1.2.1.10.18.9.1.2 dsx1TotalSESs 1.3.6.1.2.1.10.18.9.1.3 dsx1TotalSEFSs 1.3.6.1.2.1.10.18.9.1.4 dsx1TotalUASs 1.3.6.1.2.1.10.18.9.1.5 dsx1TotalCSSs 1.3.6.1.2.1.10.18.9.1.6 dsx1TotalPCVs 1.3.6.1.2.1.10.18.9.1.7 dsx1TotalLESs 1.3.6.1.2.1.10.18.9.1.8 dsx1TotalBESs 1.3.6.1.2.1.10.18.9.1.9 dsx1TotalDMs 1.3.6.1.2.1.10.18.9.1.10 dsx1TotalLCVs 1.3.6.1.2.1.10.18.9.1.11 3 of 3 764 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 765: Mib Files In The Ppp-Ip-Ncp-Mib.my File

    G250/G350 MIB files MIB files in the PPP-IP-NCP-MIB.my file The following table provides a list of the MIBs in the PPP-IP-NCP-MIB.my file that are supported by the G250/G350 and their OIDs: Object pppIpOperStatus 1.3.6.1.2.1.10.23.3.1.1.1 pppIpLocalToRemoteCompressionProtocol 1.3.6.1.2.1.10.23.3.1.1.2 pppIpRemoteToLocalCompressionProtocol 1.3.6.1.2.1.10.23.3.1.1.3 pppIpRemoteMaxSlotId 1.3.6.1.2.1.10.23.3.1.1.4 pppIpLocalMaxSlotId 1.3.6.1.2.1.10.23.3.1.1.5...

  • Page 766: Mib Files In The Rfc1213-Mib.my File

    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 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 1 of 4 766 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 767 G250/G350 MIB files Object 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 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 ipInDiscards 1.3.6.1.2.1.4.8 ipInDelivers 1.3.6.1.2.1.4.9 ipOutRequests 1.3.6.1.2.1.4.10 ipOutDiscards 1.3.6.1.2.1.4.11...
  • Page 768 1.3.6.1.2.1.4.21.1.8 ipRouteProto 1.3.6.1.2.1.4.21.1.9 ipRouteAge 1.3.6.1.2.1.4.21.1.10 ipRouteMask 1.3.6.1.2.1.4.21.1.11 ipRouteMetric5 1.3.6.1.2.1.4.21.1.12 ipRouteInfo 1.3.6.1.2.1.4.21.1.13 ipNetToMediaIfIndex 1.3.6.1.2.1.4.22.1.1 ipNetToMediaPhysAddress 1.3.6.1.2.1.4.22.1.2 ipNetToMediaNetAddress 1.3.6.1.2.1.4.22.1.3 ipNetToMediaType 1.3.6.1.2.1.4.22.1.4 ipRoutingDiscards 1.3.6.1.2.1.4.23 snmpInPkts 1.3.6.1.2.1.11.1 snmpOutPkts 1.3.6.1.2.1.11.2 3 of 4 768 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 769 G250/G350 MIB files Object 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 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...

  • Page 770: Mib Files In The Avaya-Entity-Mib.my File

    Traps and MIBs MIB files 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 G250/G350 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 avEntPhySensorLoWarningClear 1.3.6.1.4.1.6889.2.1.99.1.1.4 avEntPhySensorLoWarning 1.3.6.1.4.1.6889.2.1.99.1.1.5...

  • Page 771: Mib Files In The Xswitch-Mib.my File

    G250/G350 MIB files MIB files in the XSWITCH-MIB.my file The following table provides a list of the MIBs in the XSWITCH-MIB.my file that are supported by the G250/G350 and their OIDs: Object scGenPortGroupId 1.3.6.1.4.1.81.28.1.4.1.1.1 scGenPortId 1.3.6.1.4.1.81.28.1.4.1.1.2 scGenPortVLAN 1.3.6.1.4.1.81.28.1.4.1.1.3 scGenPortPriority 1.3.6.1.4.1.81.28.1.4.1.1.4 scGenPortSetDefaults 1.3.6.1.4.1.81.28.1.4.1.1.5...

  • Page 772: Mib Files In The Croute-Mib.my File

    1.3.6.1.4.1.81.31.1.2.1.5 ipInterfaceBroadcastAddr 1.3.6.1.4.1.81.31.1.2.1.6 ipInterfaceProxyArp 1.3.6.1.4.1.81.31.1.2.1.7 ipInterfaceStatus 1.3.6.1.4.1.81.31.1.2.1.8 ipInterfaceMainRouterAddr 1.3.6.1.4.1.81.31.1.2.1.9 ipInterfaceARPServerStatus 1.3.6.1.4.1.81.31.1.2.1.10 ipInterfaceName 1.3.6.1.4.1.81.31.1.2.1.11 ipInterfaceNetbiosRebroadcast 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 1 of 4 772 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 773 G250/G350 MIB files Object 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 ripInterfaceSendMode 1.3.6.1.4.1.81.31.1.4.1.7 ripInterfaceVersion 1.3.6.1.4.1.81.31.1.4.1.8 ospfGlobalsLeakRIPIntoOSPF 1.3.6.1.4.1.81.31.1.5.1 ospfGlobalsLeakStaticIntoOSPF 1.3.6.1.4.1.81.31.1.5.2 ospfGlobalsLeakDirectIntoOSPF 1.3.6.1.4.1.81.31.1.5.3 ospfGlobalsDefaultExportMetric 1.3.6.1.4.1.81.31.1.5.4 relayVlIndex 1.3.6.1.4.1.81.31.1.6.1.1 relayVlPrimaryServerAddr 1.3.6.1.4.1.81.31.1.6.1.2 relayVlSeconderyServerAddr 1.3.6.1.4.1.81.31.1.6.1.3...
  • Page 774 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 iphcControlRtpAdminStatus 1.3.6.1.4.1.81.31.1.15.1.1.5 iphcRtpSessions 1.3.6.1.4.1.81.31.1.15.1.1.6 iphcNegotiatedRtpSessions 1.3.6.1.4.1.81.31.1.15.1.1.7 iphcControlNonTcpAdminStatus 1.3.6.1.4.1.81.31.1.15.1.1.8 iphcNonTcpSessions 1.3.6.1.4.1.81.31.1.15.1.1.9 iphcNegotiatedNonTcpSessions 1.3.6.1.4.1.81.31.1.15.1.1.10 iphcMaxPeriod 1.3.6.1.4.1.81.31.1.15.1.1.11 iphcMaxTime 1.3.6.1.4.1.81.31.1.15.1.1.12 iphcControRtpMinPortNumber 1.3.6.1.4.1.81.31.1.15.1.1.13 iphcControRtpMaxPortNumber 1.3.6.1.4.1.81.31.1.15.1.1.14 iphcControlRtpCompressionRatio 1.3.6.1.4.1.81.31.1.15.1.1.15 3 of 4 774 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 775: Mib Files In The Rs-232-Mib.my File

    1.3.6.1.4.1.81.31.3.1.1.2 vlConfStatus 1.3.6.1.4.1.81.31.3.1.1.3 4 of 4 MIB files in the RS-232-MIB.my file The following table provides a list of the MIBs in the RS-232-MIB.my file that are supported by the G250/G350 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...
  • Page 776 1.3.6.1.2.1.10.33.4.1.10 rs232SyncPortRTSCTSDelay 1.3.6.1.2.1.10.33.4.1.11 rs232SyncPortMode 1.3.6.1.2.1.10.33.4.1.12 rs232SyncPortIdlePattern 1.3.6.1.2.1.10.33.4.1.13 rs232SyncPortMinFlags 1.3.6.1.2.1.10.33.4.1.14 rs232InSigPortIndex 1.3.6.1.2.1.10.33.5.1.1 rs232InSigName 1.3.6.1.2.1.10.33.5.1.2 rs232InSigState 1.3.6.1.2.1.10.33.5.1.3 rs232InSigChanges 1.3.6.1.2.1.10.33.5.1.4 rs232OutSigPortIndex 1.3.6.1.2.1.10.33.6.1.1 rs232OutSigName 1.3.6.1.2.1.10.33.6.1.2 rs232OutSigState 1.3.6.1.2.1.10.33.6.1.3 rs232OutSigChanges 1.3.6.1.2.1.10.33.6.1.4 2 of 2 776 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 777: Mib Files In The Ripv2-Mib.my File

    G250/G350 MIB files MIB files 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 G250/G350 and their OIDs: Object rip2GlobalRouteChanges 1.3.6.1.2.1.23.1.1 rip2GlobalQueries 1.3.6.1.2.1.23.1.2 rip2IfStatAddress 1.3.6.1.2.1.23.2.1.1 rip2IfStatRcvBadPackets 1.3.6.1.2.1.23.2.1.2 rip2IfStatRcvBadRoutes 1.3.6.1.2.1.23.2.1.3...

  • Page 778: Mib Files In The If-Mib.my File

    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 1 of 2 778 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 779 G250/G350 MIB files Object ifSpecific 1.3.6.1.2.1.2.2.1.22 ifName 1.3.6.1.2.1.31.1.1.1.1 ifInMulticastPkts 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...

  • Page 780: Mib Files In The Ds0Bundle-Mib.my File

    G250/G350 and their OIDs: Object dsx1LineIndex 1.3.6.1.2.1.10.18.6.1.1 dsx1IfIndex 1.3.6.1.2.1.10.18.6.1.2 dsx1TimeElapsed 1.3.6.1.2.1.10.18.6.1.3 dsx1ValidIntervals 1.3.6.1.2.1.10.18.6.1.4 dsx1LineType 1.3.6.1.2.1.10.18.6.1.5 dsx1LineCoding 1.3.6.1.2.1.10.18.6.1.6 dsx1SendCode 1.3.6.1.2.1.10.18.6.1.7 dsx1CircuitIdentifier 1.3.6.1.2.1.10.18.6.1.8 dsx1LoopbackConfig 1.3.6.1.2.1.10.18.6.1.9 dsx1LineStatus 1.3.6.1.2.1.10.18.6.1.10 dsx1SignalMode 1.3.6.1.2.1.10.18.6.1.11 dsx1TransmitClockSource 1.3.6.1.2.1.10.18.6.1.12 1 of 3 780 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 781 G250/G350 MIB files Object dsx1Fdl 1.3.6.1.2.1.10.18.6.1.13 dsx1CurrentIndex 1.3.6.1.2.1.10.18.7.1.1 dsx1CurrentESs 1.3.6.1.2.1.10.18.7.1.2 dsx1CurrentSESs 1.3.6.1.2.1.10.18.7.1.3 dsx1CurrentSEFSs 1.3.6.1.2.1.10.18.7.1.4 dsx1CurrentUASs 1.3.6.1.2.1.10.18.7.1.5 dsx1CurrentCSSs 1.3.6.1.2.1.10.18.7.1.6 dsx1CurrentPCVs 1.3.6.1.2.1.10.18.7.1.7 dsx1CurrentLESs 1.3.6.1.2.1.10.18.7.1.8 dsx1CurrentBESs 1.3.6.1.2.1.10.18.7.1.9 dsx1CurrentDMs 1.3.6.1.2.1.10.18.7.1.10 dsx1CurrentLCVs 1.3.6.1.2.1.10.18.7.1.11 dsx1IntervalIndex 1.3.6.1.2.1.10.18.8.1.1 dsx1IntervalNumber 1.3.6.1.2.1.10.18.8.1.2 dsx1IntervalESs 1.3.6.1.2.1.10.18.8.1.3 dsx1IntervalSESs 1.3.6.1.2.1.10.18.8.1.4 dsx1IntervalSEFSs 1.3.6.1.2.1.10.18.8.1.5 dsx1IntervalUASs 1.3.6.1.2.1.10.18.8.1.6 dsx1IntervalCSSs 1.3.6.1.2.1.10.18.8.1.7...

  • Page 782: Mib Files In The Ds0-Mib.my File

    The following table provides a list of the MIBs in the DS0-MIB.my file that are supported by the G250/G350 and their OIDs: Object dsx0Ds0ChannelNumber 1.3.6.1.2.1.10.81.1.1.1 dsx0RobbedBitSignalling 1.3.6.1.2.1.10.81.1.1.2 dsx0CircuitIdentifier 1.3.6.1.2.1.10.81.1.1.3 dsx0IdleCode 1.3.6.1.2.1.10.81.1.1.4 dsx0SeizedCode 1.3.6.1.2.1.10.81.1.1.5 dsx0ReceivedCode 1.3.6.1.2.1.10.81.1.1.6 dsx0TransmitCodesEnable 1.3.6.1.2.1.10.81.1.1.7 dsx0Ds0BundleMappedIfIndex 1.3.6.1.2.1.10.81.1.1.8 dsx0ChanMappedIfIndex 1.3.6.1.2.1.10.81.3.1.1 782 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 783: Mib Files In The Policy-Mib.my File

    G250/G350 MIB files MIB files in the POLICY-MIB.my file The following table provides a list of the MIBs in the POLICY-MIB.MY file that are supported by the G250/G350 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...
  • Page 784 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 ipPolicyRuleSrcAddrNot 1.3.6.1.4.1.81.36.2.1.24 ipPolicyRuleDstAddrNot 1.3.6.1.4.1.81.36.2.1.25 ipPolicyRuleProtocolNot 1.3.6.1.4.1.81.36.2.1.26 ipPolicyRuleL4SrcPortNot 1.3.6.1.4.1.81.36.2.1.27 ipPolicyRuleL4DestPortNot 1.3.6.1.4.1.81.36.2.1.28 ipPolicyRuleIcmpTypeCodeNot 1.3.6.1.4.1.81.36.2.1.29 ipPolicyRuleSrcPolicyUserGroupName 1.3.6.1.4.1.81.36.2.1.30 ipPolicyRuleDstPolicyUserGroupName 1.3.6.1.4.1.81.36.2.1.31 2 of 7 784 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 785 G250/G350 MIB files Object ipPolicyControlSlot 1.3.6.1.4.1.81.36.3.1.1 ipPolicyControlActiveGeneralList 1.3.6.1.4.1.81.36.3.1.2 ipPolicyControlAllowedPolicyManagers 1.3.6.1.4.1.81.36.3.1.3 ipPolicyControlCurrentChecksum 1.3.6.1.4.1.81.36.3.1.4 ipPolicyControlMinimalPolicyManagmentVersion 1.3.6.1.4.1.81.36.3.1.5 ipPolicyControlMaximalPolicyManagmentVersion 1.3.6.1.4.1.81.36.3.1.6 ipPolicyControlMIBversion 1.3.6.1.4.1.81.36.3.1.7 ipPolicyDiffServSlot 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...
  • Page 786 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 4 of 7 786 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 787 G250/G350 MIB files Object ipPolicyCompositeOpListID 1.3.6.1.4.1.81.36.8.1.2 ipPolicyCompositeOpID 1.3.6.1.4.1.81.36.8.1.3 ipPolicyCompositeOpName 1.3.6.1.4.1.81.36.8.1.4 ipPolicyCompositeOp802priority 1.3.6.1.4.1.81.36.8.1.5 ipPolicyCompositeOpAccess 1.3.6.1.4.1.81.36.8.1.6 ipPolicyCompositeOpDscp 1.3.6.1.4.1.81.36.8.1.7 ipPolicyCompositeOpRSGQualityClass 1.3.6.1.4.1.81.36.8.1.8 ipPolicyCompositeOpNotify 1.3.6.1.4.1.81.36.8.1.9 ipPolicyCompositeOpRowStatus 1.3.6.1.4.1.81.36.8.1.10 ipPolicyCompositeOpErrorReply 1.3.6.1.4.1.81.36.8.1.11 ipPolicyCompositeOpKeepsState 1.3.6.1.4.1.81.36.8.1.12 ipPolicyDSCPmapEntID 1.3.6.1.4.1.81.36.9.1.1 ipPolicyDSCPmapListID 1.3.6.1.4.1.81.36.9.1.2 ipPolicyDSCPmapDSCP 1.3.6.1.4.1.81.36.9.1.3 ipPolicyDSCPmapOperation 1.3.6.1.4.1.81.36.9.1.4 ipPolicyDSCPmapName 1.3.6.1.4.1.81.36.9.1.5 ipPolicyDSCPmapApplicabilityPrecedence 1.3.6.1.4.1.81.36.9.1.6 ipPolicyDSCPmapApplicabilityStatus 1.3.6.1.4.1.81.36.9.1.7 ipPolicyDSCPmapApplicabilityType 1.3.6.1.4.1.81.36.9.1.8...
  • Page 788 1.3.6.1.4.1.81.36.11.2.1.1 ipPolicyValidRuleIfIndex 1.3.6.1.4.1.81.36.11.2.1.2 ipPolicyValidRuleSubContext 1.3.6.1.4.1.81.36.11.2.1.3 ipPolicyValidRuleListID 1.3.6.1.4.1.81.36.11.2.1.4 ipPolicyValidRuleRuleID 1.3.6.1.4.1.81.36.11.2.1.5 ipPolicyValidRuleStatus 1.3.6.1.4.1.81.36.11.2.1.6 ipPolicyValidRuleApplicabilityType 1.3.6.1.4.1.81.36.11.2.1.7 ipPolicyValidRuleErrMsg 1.3.6.1.4.1.81.36.11.2.1.8 ipPolicyValidDSCPEntID 1.3.6.1.4.1.81.36.11.3.1.1 ipPolicyValidDSCPIfIndex 1.3.6.1.4.1.81.36.11.3.1.2 ipPolicyValidDSCPSubContext 1.3.6.1.4.1.81.36.11.3.1.3 ipPolicyValidDSCPListID 1.3.6.1.4.1.81.36.11.3.1.4 ipPolicyValidDSCPvalue 1.3.6.1.4.1.81.36.11.3.1.5 6 of 7 788 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 789: Mib Files In The Bridge-Mib.my File

    1.3.6.1.4.1.81.36.11.3.1.7 ipPolicyValidDSCPErrMsg 1.3.6.1.4.1.81.36.11.3.1.8 7 of 7 MIB files 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 G250/G350 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...
  • Page 790 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 dot1dTpFdbPort 1.3.6.1.2.1.17.4.3.1.2 dot1dTpFdbStatus 1.3.6.1.2.1.17.4.3.1.3 2 of 2 790 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 791: Mib Files In The Config-Mib.my File

    G250/G350 MIB files MIB files in the CONFIG-MIB.my file The following table provides a list of the MIBs in the CONFIG-MIB.MY file that are supported by the G250/G350 and their OIDs: Object chHWType 1.3.6.1.4.1.81.7.1 chNumberOfSlots 1.3.6.1.4.1.81.7.2 chReset 1.3.6.1.4.1.81.7.7 chLntAgMaxNmbOfMngrs 1.3.6.1.4.1.81.7.9.3.1 chLntAgPermMngrId 1.3.6.1.4.1.81.7.9.3.2.1.1...
  • Page 792 1.3.6.1.4.1.81.8.1.1.19 genGroupSpecificOID 1.3.6.1.4.1.81.8.1.1.20 genGroupConfigurationSymbol 1.3.6.1.4.1.81.8.1.1.21 genGroupLastChange 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 2 of 4 792 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 793 G250/G350 MIB files Object 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 genGroupAgentSlot 1.3.6.1.4.1.81.8.1.1.38 genGroupMngType 1.3.6.1.4.1.81.8.1.1.39 genGroupNumberOfLogicalPorts 1.3.6.1.4.1.81.8.1.1.40 genGroupNumberOfInterfaces 1.3.6.1.4.1.81.8.1.1.41 genGroupCascadUpStatus 1.3.6.1.4.1.81.8.1.1.42 genGroupCascadDownStatus 1.3.6.1.4.1.81.8.1.1.43 genGroupSTARootPortID 1.3.6.1.4.1.81.8.1.1.44 genGroupCopyPortInstruction 1.3.6.1.4.1.81.8.1.1.45 genGroupLicenseKey 1.3.6.1.4.1.81.8.1.1.46 genGroupLogFileClear 1.3.6.1.4.1.81.8.1.1.47 genGroupBootVersion 1.3.6.1.4.1.81.8.1.1.48 genGroupResetLastStamp 1.3.6.1.4.1.81.8.1.1.49 genGroupSerialNumber 1.3.6.1.4.1.81.8.1.1.50...
  • Page 794 1.3.6.1.4.1.81.9.1.1.21 genPortClassification 1.3.6.1.4.1.81.9.1.1.22 genPortVLANBindingMode 1.3.6.1.4.1.81.9.1.1.23 softRedundancyId 1.3.6.1.4.1.81.11.1.1.1 softRedundancyName 1.3.6.1.4.1.81.11.1.1.2 softRedundancyGroupId1 1.3.6.1.4.1.81.11.1.1.3 softRedundancyPortId1 1.3.6.1.4.1.81.11.1.1.4 softRedundancyGroupId2 1.3.6.1.4.1.81.11.1.1.5 softRedundancyPortId2 1.3.6.1.4.1.81.11.1.1.6 softRedundancyStatus 1.3.6.1.4.1.81.11.1.1.7 softRedundancyGlobalStatus 1.3.6.1.4.1.81.11.2 softRedundancyMinTimeBetweenSwitchOvers 1.3.6.1.4.1.81.11.4 softRedundancySwitchBackInterval 1.3.6.1.4.1.81.11.5 4 of 4 794 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 795: Mib Files In The G700-Mg-Mib.my File

    G250/G350 MIB files MIB files in the G700-MG-MIB.my file The following table provides a list of the MIBs in the G700-MG-MIB.MY file that are supported by the G250/G350 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...
  • Page 796 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 cmgDhcpControllerHosts 1.3.6.1.4.1.6889.2.9.1.3.7 cmgPrimarySearchTime cmgTotalSearchTime cmgTransitionPoint cmgVoipEngineUseDhcp 1.3.6.1.4.1.6889.2.9.1.4.1 cmgVoipQosControl 1.3.6.1.4.1.6889.2.9.1.4.2 cmgVoipRemoteBbeDscp 1.3.6.1.4.1.6889.2.9.1.4.3.1.1 2 of 5 796 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 797 G250/G350 MIB files Object cmgVoipRemoteEfDscp 1.3.6.1.4.1.6889.2.9.1.4.3.1.2 cmgVoipRemote802Priority 1.3.6.1.4.1.6889.2.9.1.4.3.1.3 cmgVoipRemoteMinRtpPort 1.3.6.1.4.1.6889.2.9.1.4.3.1.4 cmgVoipRemoteMaxRtpPort 1.3.6.1.4.1.6889.2.9.1.4.3.1.5 cmgVoipRemoteRtcpEnabled 1.3.6.1.4.1.6889.2.9.1.4.3.2.1 cmgVoipRemoteRtcpMonitorIpAddress 1.3.6.1.4.1.6889.2.9.1.4.3.2.2 cmgVoipRemoteRtcpMonitorPort 1.3.6.1.4.1.6889.2.9.1.4.3.2.3 cmgVoipRemoteRtcpReportPeriod 1.3.6.1.4.1.6889.2.9.1.4.3.2.4 cmgVoipRemoteRsvpEnabled 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...
  • Page 798 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 4 of 5 798 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 799: Mib Files In The Frame-Relay-Dte-Mib.my File

    1.3.6.1.4.1.6889.2.9.1.8.2 cmgDynCacLastUpdate 1.3.6.1.4.1.6889.2.9.1.8.3 5 of 5 MIB files in the FRAME-RELAY-DTE-MIB.my file The following table provides a list of the MIBs in the FRAME-RELAY-DTE-MIB.my file that are supported by the G250/G350 and their OIDs: Object frDlcmiIfIndex 1.3.6.1.2.1.10.32.1.1.1 frDlcmiState 1.3.6.1.2.1.10.32.1.1.2 frDlcmiAddress 1.3.6.1.2.1.10.32.1.1.3...
  • Page 800 1.3.6.1.2.1.10.32.2.1.17 frCircuitReceivedDEs 1.3.6.1.2.1.10.32.2.1.18 frCircuitSentDEs 1.3.6.1.2.1.10.32.2.1.19 frCircuitLogicalIfIndex 1.3.6.1.2.1.10.32.2.1.20 frCircuitRowStatus 1.3.6.1.2.1.10.32.2.1.21 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 frErrTime 1.3.6.1.2.1.10.32.3.1.4 frErrFaults 1.3.6.1.2.1.10.32.3.1.5 frErrFaultTime 1.3.6.1.2.1.10.32.3.1.6 frTrapState 1.3.6.1.2.1.10.32.4.1 frTrapMaxRate 1.3.6.1.2.1.10.32.4.2 2 of 2 800 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 801: Mib Files In The Ip-Mib.my File

    G250/G350 MIB files MIB files in the IP-MIB.my file The following table provides a list of the MIBs in the IP-MIB.my file that are supported by the G250/G350 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...

  • Page 802: Mib Files In The Load12-Mib.my File

    G250/G350 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 genOpSourceIndex 1.3.6.1.4.1.1751.2.53.1.2.1.4 genOpDestIndex 1.3.6.1.4.1.1751.2.53.1.2.1.5 genOpServerIP 1.3.6.1.4.1.1751.2.53.1.2.1.6 genOpUserName 1.3.6.1.4.1.1751.2.53.1.2.1.7 genOpPassword 1.3.6.1.4.1.1751.2.53.1.2.1.8 genOpProtocolType 1.3.6.1.4.1.1751.2.53.1.2.1.9 genOpFileName 1.3.6.1.4.1.1751.2.53.1.2.1.10 genOpRunningStateDisplay 1.3.6.1.4.1.1751.2.53.1.2.1.11 genOpLastFailureIndex 1.3.6.1.4.1.1751.2.53.1.2.1.12 1 of 2 802 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 803 G250/G350 MIB files Object genOpLastFailureDisplay 1.3.6.1.4.1.1751.2.53.1.2.1.13 genOpLastWarningDisplay 1.3.6.1.4.1.1751.2.53.1.2.1.14 genOpErrorLogIndex 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...

  • Page 804: Mib Files In The Ppp-Lcp-Mib.my File

    1.3.6.1.2.1.10.23.1.1.1.1.4 pppLinkStatusBadFCSs 1.3.6.1.2.1.10.23.1.1.1.1.5 pppLinkStatusLocalMRU 1.3.6.1.2.1.10.23.1.1.1.1.6 pppLinkStatusRemoteMRU 1.3.6.1.2.1.10.23.1.1.1.1.7 pppLinkStatusLocalToPeerACCMap 1.3.6.1.2.1.10.23.1.1.1.1.8 pppLinkStatusPeerToLocalACCMap 1.3.6.1.2.1.10.23.1.1.1.1.9 pppLinkStatusLocalToRemoteACCompression 1.3.6.1.2.1.10.23.1.1.1.1.12 pppLinkStatusRemoteToLocalACCompression 1.3.6.1.2.1.10.23.1.1.1.1.13 pppLinkStatusTransmitFcsSize 1.3.6.1.2.1.10.23.1.1.1.1.14 pppLinkStatusReceiveFcsSize 1.3.6.1.2.1.10.23.1.1.1.1.15 pppLinkConfigInitialMRU 1.3.6.1.2.1.10.23.1.1.2.1.1 pppLinkConfigReceiveACCMap 1.3.6.1.2.1.10.23.1.1.2.1.2 pppLinkConfigTransmitACCMap 1.3.6.1.2.1.10.23.1.1.2.1.3 pppLinkConfigMagicNumber 1.3.6.1.2.1.10.23.1.1.2.1.4 pppLinkConfigFcsSize 1.3.6.1.2.1.10.23.1.1.2.1.5 804 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 805: Mib Files In The Wan-Mib.my File

    G250/G350 MIB files MIB files 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 G250/G350 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 ifTableXtndIndex 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.1 ifTableXtndPeerAddress 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.2...
  • Page 806 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 ifTableXtndCacifStatus 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.33 frDlcmiXtndIndex 1.3.6.1.4.1.6889.2.1.6.2.4.1.1.1 frDlcmiXtndLMIAutoSense 1.3.6.1.4.1.6889.2.1.6.2.4.1.1.2 frStaticCircuitSubIfIndex 1.3.6.1.4.1.6889.2.1.6.2.4.2.1.1 frStaticCircuitDLCI 1.3.6.1.4.1.6889.2.1.6.2.4.2.1.2 frStaticCircuitDLCIrole 1.3.6.1.4.1.6889.2.1.6.2.4.2.1.3 frStaticCircuitStatus 1.3.6.1.4.1.6889.2.1.6.2.4.2.1.4 frSubIfDlcmiIndex 1.3.6.1.4.1.6889.2.1.6.2.4.3.1.1 frSubIfSubIndex 1.3.6.1.4.1.6889.2.1.6.2.4.3.1.2 frSubIfType 1.3.6.1.4.1.6889.2.1.6.2.4.3.1.3 frSubIfStatus 1.3.6.1.4.1.6889.2.1.6.2.4.3.1.4 2 of 2 806 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 807: Mib Files In The Snmpv2-Mib.my File

    G250/G350 MIB files MIB files in the SNMPv2-MIB.my file The following table provides a list of the MIBs in the SNMPv2-MIB.my file that are supported by the G250/G350 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...

  • Page 808: Mib Files 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 G250/G350 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 ospfASBdrRtrStatus 1.3.6.1.2.1.14.1.5 ospfExternLsaCount 1.3.6.1.2.1.14.1.6 1 of 4 808 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 809 G250/G350 MIB files Object ospfExternLsaCksumSum 1.3.6.1.2.1.14.1.7 ospfTOSSupport 1.3.6.1.2.1.14.1.8 ospfOriginateNewLsas 1.3.6.1.2.1.14.1.9 ospfRxNewLsas 1.3.6.1.2.1.14.1.10 ospfExtLsdbLimit 1.3.6.1.2.1.14.1.11 ospfMulticastExtensions 1.3.6.1.2.1.14.1.12 ospfExitOverflowInterval 1.3.6.1.2.1.14.1.13 ospfDemandExtensions 1.3.6.1.2.1.14.1.14 ospfAreaId 1.3.6.1.2.1.14.2.1.1 ospfAuthType 1.3.6.1.2.1.14.2.1.2 ospfImportAsExtern 1.3.6.1.2.1.14.2.1.3 ospfSpfRuns 1.3.6.1.2.1.14.2.1.4 ospfAreaBdrRtrCount 1.3.6.1.2.1.14.2.1.5 ospfAsBdrRtrCount 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...
  • Page 810 1.3.6.1.2.1.14.7.1.14 ospfIfEvents 1.3.6.1.2.1.14.7.1.15 ospfIfAuthKey 1.3.6.1.2.1.14.7.1.16 ospfIfStatus 1.3.6.1.2.1.14.7.1.17 ospfIfMulticastForwarding 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 3 of 4 810 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 811: Mib Files In The Tunnel-Mib.my File

    1.3.6.1.2.1.14.12.1.6 ospfExtLsdbAdvertisement 1.3.6.1.2.1.14.12.1.7 4 of 4 MIB files in the TUNNEL-MIB.my file The following table provides a list of the MIBs in the TUNNEL-MIB.my file that are supported by the G250/G350 and their OIDs: Object tunnelIfLocalAddress 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 1 of 2...
  • Page 812 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 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 2 of 2 812 Administration for the Avaya G250 and Avaya G350 Media Gateways...

  • Page 813: Index

    ....CLI commands ..Avaya Voice Announcement Manager (VAM) ... Access control lists, see Policy .
  • Page 814 ..clear ip dhcp-client statistics ....area 814 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 815 Index ..... . clear ip dhcp-server binding copy cdr-file ftp ......clear ip dhcp-server statistics copy cdr-file scp .
  • Page 816 ........initiate mode 816 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 817 Index ......interface ip dhcp ping packets ..
  • Page 818 ......login authentication inactivity-period 818 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 819 Index ....ppp authentication rtr-schedule ..... ASG authentication running-config startup-config .
  • Page 820 ....set min-length ....set port trap 820 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 821 Index ....... set port vlan set system contact ..
  • Page 822 ........show ip interface show pmi 822 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 823 Index ......show point-to-point status show snmp view ....show port auto-negotiation-flowcontrol-advertisement show spantree .
  • Page 824 ........entering context 824 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 825 Index ........Cost configuring DHCP options ..Crypto list configuring vendor-specific options .
  • Page 826 ....configuring link negotiation protocol FIPS-compliant mode 826 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 827 ....load with ASB button ... . . G250 front panel ... . managing firmware banks .
  • Page 828 ... Internet Key Exchange (IKE) ....displaying test results 828 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 829 Index IP address Load balancing ........assigning to USB port ECMP .
  • Page 830 ....configuring ....Nested tunneling 830 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 831 Index ........NetBIOS suppressing updates ....Network monitoring using with RIP .
  • Page 832 ......port powering priorities precongifured for QoS lists 832 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 833 Index ....... QoS fields assigning static VLANs .....
  • Page 834 ... . defining default gateway ....CLI commands 834 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 835 Index ......determining shortest path configuring .....
  • Page 836 ......ISDN-BRI trunks data snmp-server community 836 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 837 Index ....user groups Survivability ....user-based security model (USM) auto fallback to primary MGC .
  • Page 838 ......configuring for modem use description 838 Administration for the Avaya G250 and Avaya G350 Media Gateways...
  • Page 839 Index ......DHCP/BOOTP requests failover mechanisms ......displaying configuration and statistics introduction .
  • Page 840 WFVQ, see Weighted Fair VoIP Queuing ..... . zeroize 840 Administration for the Avaya G250 and Avaya G350 Media Gateways...

This manual is also suitable for:

G350

Table of Contents