Avaya G350 Administration
  1. Manuals
  2. Brands
  3. Avaya Manuals
  4. Gateway
  5. Media Gateway G350
  6. Administration

Avaya G350 Administration

Hide thumbs Also See for G350:
Table of Contents

Advertisement

Quick Links

See also: Administration Manual , Technical White Paper
Administration of the
Avaya G350 Media Gateway
555-245-501
Issue 2
June 2004

Advertisement

Table of Contents
loading

Related Manuals for Avaya G350

Summary of Contents for Avaya G350

  • Page 1 Administration of the Avaya G350 Media Gateway 555-245-501 Issue 2 June 2004...
  • Page 2 (including but not limited to, human/data privacy, intellectual Avaya Inc. provides a limited warranty on this product. Refer to your sales property, material assets, financial resources, labor costs, and/or legal agreement to establish the terms of the limited warranty.
  • Page 3 • A call is unanswered. • 21 CFR 1040.10 and CFR 1040.11. • A busy tone is received. The LASER devices used in Avaya equipment typically operate within the • A reorder tone is received. following parameters: Avaya attests that this registered equipment is capable of providing users...
  • Page 4 68, but many have been registered with the FCC before the SDoC process If this happens, the telephone company will provide advance notice in was available. A list of all Avaya registered products may be found at: order for you to make necessary modifications to maintain uninterrupted http://www.part68.org...

  • Page 5: Table Of Contents

    Accessing CLI via modem • Accessing Avaya IW • Accessing GIW • Accessing Avaya Communication Manager • Managing login permissions Security overview Managing users and passwords SSH protocol support SCP protocol support Administration of the Avaya G350 Media Gateway June 2004...
  • Page 6 • Viewing the status of the device • Version management File transfer Software and firmware upgrades Managing configuration files Listing the files on the Avaya G350 Media Gateway Configuring logging • Logging overview • Syslog server • Logging file • Logging session •...
  • Page 7 • WAN overview • Serial interface overview Multipoint topology support • Initial WAN configuration Configuring the Avaya MM340 E1/T1 WAN media module Configuring the Avaya MM342 USP WAN media module Configuring frame relay Verifying the WAN configuration and testing connectivity •...
  • Page 8 • Configuring dynamic trap manager • SNMP configuration examples 13 Configuring advanced switching • Configuring VLANs VLAN overview VLAN tagging Multi VLAN binding G350 VLAN table Ingress VLAN security ICC-VLAN VLAN CLI commands Administration of the Avaya G350 Media Gateway June 2004...
  • Page 9 • RMON overview • RMON CLI commands • RMON configuration examples 16 Configuring the router • Overview of the G350 router • Configuring interfaces Router interface concepts IP Interface configuration commands Administration of the Avaya G350 Media Gateway June 2004...
  • Page 10 • Configuring ICMP errors • Configuring RIP RIP overview Preventing routing loops in RIP RIP distribution access lists RIP limitations RIP commands • Configuring OSPF Overview of OSPF OSPF dynamic cost Administration of the Avaya G350 Media Gateway June 2004...
  • Page 11 Editing and creating rules Rule criteria • Composite operations Overview of composite operations Pre-configured composite operations for access control lists Pre-configured composite operations for QoS lists Configuring composite operations Composite operation example Administration of the Avaya G350 Media Gateway June 2004...
  • Page 12 19 Setting synchronization • Displaying synchronization status Traps and MIBs • G350 traps • G350 MIBs Configuring the G350 using the Avaya IW • Preliminary screens • MGC configuration and upgrade • Upgrading an existing MGC • Gateway configuration Administration of the Avaya G350 Media Gateway...
  • Page 13 Modifying IP route configuration Displaying trunk status Removing a trunk Configuring a trunk media module • Endpoint installation • Alarm configuration • Password and final screens Configuring the G350 using the GIW Index Administration of the Avaya G350 Media Gateway June 2004...

  • Page 14: June

    Contents Administration of the Avaya G350 Media Gateway June 2004...

  • Page 15: About This Book

    You can download the latest version of the Administration of the Avaya G350 Media Gateway from the Avaya Web site. You must have access to the Internet, and a copy of Acrobat Reader must be installed on your personal computer.

  • Page 16: Related Resources

    About this Book Related resources Related resources For more information on the Avaya G350 Media Gateway and related features, see the following books: Title Number Overview of the Avaya G350 Media Gateway 555-245-201 Quick Start for Hardware Installation 03-300148 Installation of the Avaya G350 Media Gateway...

  • Page 17: Sending Us Comments

    Westminster, CO 80234 USA • 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 of the Avaya G350 Media Gateway, 555-245-501. Administration of the Avaya G350 Media Gateway June 2004...
  • Page 18 About this Book Sending us comments Administration of the Avaya G350 Media Gateway June 2004...

  • Page 19: Introduction

    Introduction Introduction The Avaya G350 Media Gateway is a high-performance converged networking and telephony device. The G350 provides networking and telephony services for up to 40 endpoint stations. The G350 contains: • an advanced router • a high-performance switch •...
  • Page 20 — how to configure advanced features of the G350 router • Configuring policy — how to configure access control and QoS policy lists on the G350 • Configuring policy-based routing — how to configure policy-based routing lists on the G350 •...

  • Page 21: Configuration Overview

    Done! If you intend to use a USB modem to connect to the G350, you should also assign a new IP address to the USB interface. By default, the IP address of the USB interface is 10.3.0.3 with a subnet mask of 255.255.255.0.

  • Page 22: Configuration Using Cli

    Configuring the Primary Management Interface (PMI) on page 40. Once you have defined a PMI, you must register the G350 with an MGC. The MGC is a media server that controls telephone services on the G350. The MGC can be internal or external. See...

  • Page 23: Saving Configuration Changes

    The Avaya Installation Wizard (Avaya IW) is a web-based installation wizard that leads the user through the key configuration steps of a G350 installation. The Avaya IW can be used for initial configuration of a G350 with an S8300 installed as the G350’s primary (ICC) or backup (LSP) call controller. For...
  • Page 24 You can save an old version of the firmware in case you need to use it later. If it becomes necessary to use the older version, you can reset the G350 using the older version.

  • Page 25: Accessing The Avaya G350 Media Gateway

    — instructions on how to access the CLI from a remote location using a modem CLI Overview The CLI is a textual command prompt interface that you can use to configure the Avaya G350 Media Gateway and media modules. You can access the CLI with any of the following: •...

  • Page 26: Accessing The Cli Locally

    Accessing CLI via local network You can access the CLI from a computer on the same local network as the Avaya G350 Media Gateway by using any standard telnet program. For the host address, you can use the IP address of any G350 interface.

  • Page 27: Accessing Cli Via Modem

    Open any standard telnet program on the remote computer. Open a telnet session to the IP address of the USB port on the G350. The default IP address of the USB port is 10.3.0.3 with subnet mask 255.255.255.0. For instructions on how to change the IP address of the USB port (i.e., the USB interface), see...
  • Page 28 Open any standard telnet program on the remote computer. Open a telnet session to the IP address of the console port on the G350. The default IP address of the console port is 10.3.0.1 with subnet mask 255.255.255.0. For instructions on how to change the IP address of the console port (i.e., the console interface), see...

  • Page 29: Accessing Avaya Iw

    • Change your password When performing initial configuration of the G350, you can access and run the Avaya IW using a laptop computer. To access the Avaya IW: Connect a laptop computer to the Services port of the S8300, using a crossover cable.

  • Page 30: Accessing Giw

    The Gateway Installation Wizard (GIW) is an automated tool that allows you to perform a streamlined installation and configuration of a standalone G350. You can use the GIW to perform initial configuration of the G350 and to upgrade software and firmware. Specifically, you can perform the following tasks with the GIW: •...

  • Page 31: Accessing Avaya Communication Manager

    Gateway provides. Avaya Communication Manager software runs on a media server. There might be several media servers on your network that can control the Avaya G350 Media Gateway. You can access Avaya Communication Manager on any media server that is a Media Gateway Controller (MGC) for the Avaya G350 Media Gateway.

  • Page 32: Managing Login Permissions

    G350 security mechanism. When the user enters a username, the G350 first searches its own database for the username. If the G350 does not find the username in its own database, it establishes a connection with the RADIUS server, and the RADIUS server provides the necessary authentication services.

  • Page 33: Ssh Protocol Support

    35. Privilege level When you start to use Avaya G350 Manager or 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.

  • Page 34: Ssh Configuration

    • The G350 sends the public key (the fingerprint) to the client computer. This public key is used by the client to encrypt the data it sends to the G350. The G350 decrypts the data using the private key. •...

  • Page 35: Scp Protocol Support

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

  • Page 36: Special Security Features

    The G350 includes a special recovery password. The purpose of the recovery password is to enable the system administrator to access the G350 in the event that the regular password is forgotten. You can only use the recovery password when accessing the G350 via a direct connection to the console port. See Accessing CLI with a console device on page 27.

  • Page 37: Enabling And Disabling Telnet Access

    Enabling and disabling telnet access You can enable and disable the G350’s ability to establish incoming and outgoing telnet connections, using the following commands. You can only use these commands when accessing the G350 via a direct connection to the console port. See Accessing CLI with a console device on page 27.
  • Page 38 Accessing the Avaya G350 Media Gateway Special security features Administration of the Avaya G350 Media Gateway June 2004...

  • Page 39: Basic Device Configuration

    G350 Defining an interface In a new Avaya G350 Media Gateway, only the console and USB interfaces are defined. All other interfaces must be defined by the administrator, after installation of the G350. To define an interface: Use the command to enter the interface context.

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

    Sending messages from the G350 using FTP and TFTP protocol You can designate any of the G350’s interfaces to serve as the G350’s PMI. The PMI must be an IP address that the MGC recognizes. If you are not sure which interface to use as the PMI, check with your system administrator.

  • Page 41: Defining The Default Gateway

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

  • Page 42: The Media Gateway Controller (Mgc)

    If the media server with the IP address 132.236.73.2 is available, that media server becomes the G350’s MGC. If that server is not available, the G350 searches for the next media server on the list, and so on. Administration of the Avaya G350 Media Gateway...

  • Page 43: Setting Reset Times

    350-001> set reset-times transition-point 1 In this example, in the event of a loss of connection with the registered MGC, the G350 searches for the primary MGC on its MGC list for 20 minutes. If the 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 44: Accessing The Registered Mgc

    When an MGC controls telephone services on the Avaya G350 Media Gateway in ICC or LSP mode, the G350 monitors the connection with the MGC. If the connection with the MGC is lost, the G350 starts a recovery process. Use the following commands to configure MGC monitoring: •...
  • Page 45 G350. To view information about a specific media module, include the slot number of the media module as an argument. For example, to view information about the media module in slot 2, enter .

  • Page 46: Version Management

    G350 files and their version numbers File transfer The Avaya G350 Media Gateway can be a client for the FTP and TFTP protocols. Use the FTP or TFTP protocols to transfer files between the Avaya G350 Media Gateway and other devices. You can use file transfer to: •...

  • Page 47: Upgrading Software And Firmware

    G350 using the other version. This is particularly important when uploading new versions. By default, when you turn on or reset the G350, the G350 loads firmware from Bank B. To change the default bank from which firmware is loaded during startup, type the command.

  • Page 48: Managing Configuration Files

    G350 Media Gateway. You can use configuration files to back up and restore the configuration of the G350. Use the FTP or TFTP protocol to transfer a configuration file between the G350 and a server on the network. You can back up either the running configuration or the startup configuration to the server as a configuration file.

  • Page 49: Listing The Files On The Avaya G350 Media Gateway

    G350. For more information about running configuration and startup configuration, Configuration using GUI applications on page 22. To transfer a configuration file between the G350 and a server on the network, use one of the following commands: •...
  • Page 50 Basic device configuration Version management Administration of the Avaya G350 Media Gateway June 2004...

  • Page 51: Configuring Logging

    By default, all sinks are disabled. When you reset the G350, the Session sink is disabled, even if you enabled it during the session. The other sinks retain whatever setting they had before the reset. Filters are not disabled when you reset the G350.

  • Page 52: Syslog Server

    IP address of the Syslog server. If you do not specify an IP address, the command displays the status of all Syslog servers defined for the G350. This command displays whether the server is enabled or disabled, and lists all filters defined on the server.

  • Page 53: Logging File

    For a specified sink, you can define the threshold severity for message output for each application. Messages with a severity lower than the defined threshold are not sent to the specified sink. Administration of the Avaya G350 Media Gateway June 2004...
  • Page 54 Core routing system failures config Configuration changes temp Temperature messages filesys File system problem (flash) Cooling system supply Power supply system security Authentication failure cascade Stack CASCADE mechanism QoS messages 1 of 2 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 55 Syslog server to which you want to apply the filter. The following example defines a filter in which no RIP messages are sent to the Syslog server with the IP address 175.5.16.33: set logging server condition rip none 175.5.16.33 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 56 Configuring logging Filters and severity levels Administration of the Avaya G350 Media Gateway June 2004...

  • Page 57: Configuring Ethernet Ports

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

  • Page 58: Configuring Switch Ethernet Ports

    Configuring SNMP traps page 102. Switch Ethernet port commands Use the following commands for basic configuration of switch Ethernet ports. For more information about these commands, see Avaya G350 Media Gateway CLI Reference, 555-245-202. • Use the command to set the flowcontrol set port auto-negotiation-flowcontrol-advertisement advertisement for the specified port when performing auto-negotiation.

  • Page 59: Configuring The Wan Ethernet Port

    — — the port is treated as if it were connected to shared media force-false — — the G350 tries to automatically detect the connection type of the port auto • Use the command to configure the speed of a port or range of ports. In set port speed auto-negotiation mode, the port’s speed is determined by auto-negotiation.

  • Page 60: Backup Interfaces

    Use shutdown form of this command to restore the administrative status of the interface to up. • Use the command to set the port speed. speed Administration of the Avaya G350 Media Gateway June 2004...

  • Page 61: Configuring Voip Qos

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

  • Page 62: Configuring Rtp And Rtcp

    RTP Header Compression can reduce the size of all three headers (IP+UDP+RTP~40 bytes) to 2-4 bytes. The G350 can only compress RTP packets. Any UDP packet with an even destination port within a user- configurable range of ports, is considered an RTP packet.

  • Page 63: Configuring Qos Parameters

    Configuring QoS parameters The G350 uses MGCP (H248) protocol for call signalling and call routing information. Use the following commands to configure QoS for signalling and VoIP traffic. For more information about these commands, including parameters and default settings, see Avaya™ G350 Media Gateway CLI Reference, 555-245-202.

  • Page 64: Configuring Rtcp Qos Parameters

    The parameters that can be set are enabled/disabled, refresh rate (seconds), failure retry (y or n), and service profile (Guaranteed or Controlled). • Use the command to display QoS, RSVP, and RTCP parameters. show qos-rtcp Administration of the Avaya G350 Media Gateway June 2004...

  • Page 65: Configuring Weighted Fair Queuing (Wfq)

    The upper and lower limits of this command depend on the amount of bandwidth configured for the interface. NOTE: This command should generally be used only for troubleshooting. Administration of the Avaya G350 Media Gateway June 2004...
  • Page 66 Configuring VoIP QoS Configuring Weighted Fair Queuing (WFQ) Administration of the Avaya G350 Media Gateway June 2004...

  • Page 67: Configuring The G350 For Modem Use

    Configuring the G350 for modem You can connect either a USB or a serial modem to the Avaya G350 Media Gateway. A USB modem must be connected to the USB port on the G350 chassis. A serial modem must be connected to the console port (CONSOLE) on the G350 chassis.

  • Page 68: Configuring The Console Port For Modem Use

    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, use the async mode terminal command to disable interactive mode.
  • Page 69 The console port uses the following settings: • baud — 9600 • data bits — 8 • parity — none • stop bits — 1 • flow control — hardware Administration of the Avaya G350 Media Gateway June 2004...
  • Page 70 Configuring the G350 for modem use Configuring the console port for modem use Administration of the Avaya G350 Media Gateway June 2004...

  • Page 71: Configuring A Wan

    WAN overview When you add a WAN media module to the Avaya G350 Media Gateway, you can connect an E1/T1 or USP WAN line to the G350. The G350 is an endpoint device and router for the WAN. For more...

  • Page 72: Serial Interface Overview

    Configuring a WAN Serial interface overview • Quality of Service (QoS) — the G350 supports the ability to separate traffic into 4 strict priority queues per egress serial interface. The queue assignment is performed using Policy. For more information, see Configuring QoS parameters on page 63.
  • Page 73 IP interfaces defined using DLCI. Figure 3: USP Port - Frame Relay Protocol. Administration of the Avaya G350 Media Gateway June 2004...

  • Page 74: Multipoint Topology Support

    The G350 responds to inverse ARP queries received on frame relay sub-interfaces with the proper inverse ARP replies. When you connect the G350 as an endpoint in a PTMP configuration, you need to increase the OSPF timers manually. Use the...

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

    Configuring the Avaya MM340 E1/T1 WAN media module For a list of G350 default settings, see E1/T1 default settings on page 77, or use the show controllers command to display the current settings.
  • Page 76 If needed, repeat Step 5 through Step 9 to configure additional channel groups on the same E1 or T1 port. Test the WAN configuration. See Verifying the WAN configuration and testing connectivity page 80. Use the command to save the configuration. copy running-config startup-config Administration of the Avaya G350 Media Gateway June 2004...

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

    DCE equipment that is transmitter-delay connected directly to the G350, or the router on the WAN have a receive buffer that is not large enough to hold the traffic sent by the G350. In this case, configure...

  • Page 78: Configuring Frame Relay

    Use the command to save the configuration. copy running-config startup-config USP default settings Table 6, USP default settings, on page 78 shows the default settings for USP WAN lines on the G350: Table 6: USP default settings Function Default setting Encoding...
  • Page 79 If needed, repeat Step 2 through Step 11 to configure frame relay encapsulation for other serial interfaces on the same WAN port. Test the WAN configuration. See Verifying the WAN configuration and testing connectivity page 80. Use the command to save the configuration. copy running-config startup-config Administration of the Avaya G350 Media Gateway June 2004...

  • Page 80: Verifying The Wan Configuration And Testing Connectivity

    Secondary Disable delay — The time in seconds between the primary interface restoration and the backup interface deactivation. Default = 0 seconds, maximum = 3600 seconds. Both interfaces are active during this time to enable a smooth transition for the routing protocols. Administration of the Avaya G350 Media Gateway June 2004...

  • Page 81: Backup Commands

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

  • Page 82: Dynamic Cac

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

  • Page 83: Frame Relay Encapsulation

    (optional) — If dynamic CAC is activated on more than one active interface, activation priority the G350 reports the bearer bandwidth limit of the interface with the highest activation priority. You can set the activation priority to any number between 1 and 255. The default activation priority is 50.

  • Page 84: Priority Dlci

    DLCI is set as the High Priority DLCI in the Priority DLCI group. On the Avaya 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 85: Priority Queuing

    When using VoIP, the G350 enables a distinction within the high-priority queue between priorities 6 and 7. The G350 uses priority 6 for the voice-bearer traffic, and priority 7 for the voice-controller traffic. These two priorities are served on a round-robin basis. Within the high-priority queue, the priority 6 capacity is a maximum of 25% the size of the priority 7 capacity to reduce the delay of voice flow.

  • Page 86: Ppp Voip Configuration

    Figure 5: PPP VoIP configuration over WAN 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 128Kbps V.35 interface. Following are the connection details for Site A: •...

  • Page 87: Configuration Example For Site A

    — S8300 - 149.49.54.81 — G350 PMI - 149.49.54.82 Site B contains four IP phones and a G350 with S8300 and one MM340 media module. The MM340 media module connects the G350 to the WAN via a two-timeslot (128Kbps) T1 interface. The following are the connection details for Site B: •...
  • Page 88 G350-001(if:Serial 5/1)# bandwidth 128 • VoIP configuration: G350-001(if:Serial 5/1)# fair-voip-queue G350-001(if:Serial 5/1)# ip rtp header-compression G350-001(if:Serial 5/1)# ip rtp compression-connections 20 (4) G350-001(if:Serial 5/1)# ip rtp port-range 2048 3028 G350-001(if:Serial 5/1:1)# queue-limit 1 12 G350-001(if:Serial 5/1)# exit • Static routes configuration: G350-001# ip default-gateway 2.2.2.2...

  • Page 89: Configuration Example For Site B

    (4) At this stage the number of connections (20) depends on the number of phones. (5) At this stage you are matching the RTP port range to that of the G350. (6) At this stage the default queue size is 6, and since RTP is enabled you can double the VoIP queue size.
  • Page 90 Configuring a WAN WAN configuration example • Serial interface configuration: G350-001# controller t1 5/1 G350-001(controller:5/1)# channel-group 1 timeslots 1-2 speed 64 G350-001(controller:5/1)# exit G350-001# interface Serial 5/1:1 G350-001(if:Serial 5/1:1)# ip address 2.2.2.2 24 G350-001(if:Serial 5/1:1)# mtu 300 NOTE: Some LAN data applications do not support fragmented packets. In this case, do not change the MTU from its default of 1500.

  • Page 91: Configuring Poe

    Powering devices Introduction The Avaya G350 MM314 PoE media module provides Inline DC power over the signal pairs, in addition to switched Ethernet, on the existing LAN infrastructure for devices such as IP telephones and Wireless LAN access points. This allows you to deploy devices in the network that require power without installing standard power cables in hard-to-access areas.

  • Page 92: Hot Swapping

    Configuring PoE PoE overview How the G350 detects a powered device The MM314 PoE media module uses specific resistance between the power feed pairs and PD connection verification to determine whether to supply power to a given port. The following figure shows the process.

  • Page 93: Powering Devices

    Powering devices The Avaya G350 MM314 PoE media module has its own power supply. Therefore, a full 210 W of power is available for PDs. Each port can supply up to 15.4 W by default. Since 210 W may not be enough for driving powered devices on all the ports simultaneously, Avaya has implemented a priority mechanism.
  • Page 94 Configuring PoE PoE configuration examples The following example configures PoE priority on a port: G350-003(super)# set port powerinline priority 6/14 high Powering priority on port 6/14 was set to High. The following example displays PoE information: G350-003(super)# show powerinline Port...

  • Page 95: Configuring Emergency Transfer Relay (Etr)

    Avaya Communication Manager. ETR is activated automatically. When ETR is activated, the Avaya G350 Media Gateway connects the fixed analog trunk port (7/1) to the fixed analog line port (7/2). An outside telephone exchange can be connected to the trunk port and an analog telephone can be connected to the line port.

  • Page 96: Viewing Etr State

    Module status (in service, out of service, or out of service waiting for off-hook) • Trunk number of the trunk connected to ETR • Line number of the line connected to ETR • Line status ( off hook on hook Administration of the Avaya G350 Media Gateway June 2004...

  • Page 97: Configuring Snmp

    Configuring SNMP SNMP configuration overview Configuring SNMP This chapter provides information about configuring SNMP on the G350 and contains the following sections: • SNMP configuration overview — an overview of SNMP configuration on G350 devices • SNMP versions — a description of the SNMP versions supported by the G350 •...

  • Page 98: Snmp Versions

    • SNMPv3 The Avaya G350 Media Gateway supports all three of these versions. The implementation of SNMPv3 on the G350 is backwards compatible. An agent that supports SNMPv3 will also support SNMPv1 and SNMPv2c. SNMPv1 SNMPv1 uses community strings to limit access rights. Each SNMP device is assigned to a read community and a write community.

  • Page 99: Users

    Code (MAC) is provided with the message, and no encryption is performed. This method maintains the same security level as SNMPv1, but provides a method for limiting the access rights of the user. Administration of the Avaya G350 Media Gateway June 2004...

  • Page 100: Groups

    The group maps its users to views based on the security mode and level with which the user is communicating with the G350. Within a group, the following combinations of security mode and level can be mapped to views: •...

  • Page 101: Views

    OIDs to the list or exclude OIDs from a list of all of the OIDs in the 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.

  • Page 102: 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 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 103: Configuring Snmp Access

    • Use the snmp-server community command to enable SNMPv1 access to the G350. Use the form of this command to disable SNMPv1 access to the G350. • Use the command to create an SNMPv3 user. Use the form of this snmp-server user command to remove an SNMPv3 user.

  • Page 104: Configuring Dynamic Trap Manager

    Configuring dynamic trap manager Dynamic trap manager is a special feature that ensures that the 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 105 G350-001(super-if:FastEthernet 10/2)# no snmp trap link-status Done! The following example creates a read-only user: G350-001# snmp-server user <username> v3 ReadOnlyG v3 auth {md5|sha} <authPassword> priv des56 <privPassword> The following example creates a read-write user: G350-001# snmp-server user <username> v3 ReadWriteG v3 auth {md5|sha} <authPassword>...
  • Page 106 .G350-001(super)# set port trap 6/1 enable Port 6/1 up/down trap enabled The following example disables link up/down trap on a LAN port: G350-001(super)# set port trap 6/1 disable Port 6/1 up/down trap disabled Administration of the Avaya G350 Media Gateway June 2004...

  • Page 107: Configuring Advanced Switching

    • Port classification — instructions on how to configure port classification Configuring VLANs This section contains information about VLAN configuration on the G350’s switch ports and includes the following topics: • VLAN overview — an overview of VLANs and how they can be used in a network •...
  • Page 108 PC on the Sales VLAN, for example, that traffic is only forwarded out the other ports assigned to that VLAN. Thus, the Engineering and Marketing VLANs are not burdened with processing that traffic. Administration of the Avaya G350 Media Gateway June 2004...

  • Page 109: Vlan Tagging

    VLANs through the same port. This is useful in applications such as multi-tenant networks, where each user has his or her own VLAN for privacy. The whole building has a shared high-speed connection to the ISP. Administration of the Avaya G350 Media Gateway June 2004...

  • Page 110: G350 Vlan Table

    All the ports in Bound to Configured mode support the same list of VLANs G350 VLAN table The G350 VLAN table lists all VLANs configured on the G350. You can configure up to eight VLANs. To display a list of VLANs, use the show vlan command.

  • Page 111: Icc-Vlan

    Configuring VLANs ICC-VLAN When the G350 includes an ICC, the ICC connects to the 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. You can use the command to attach the ICC to a different VLAN.

  • Page 112: Vlan Configuration Examples

    G350-001(super)# set port vlan 54 10/3 VLAN 54 modified VLAN Mod/Ports ---- --------------------------- 10/3 The following example sets a port’s VLAN binding mode: G350-001(super)# set port vlan-binding-mode 10/3 bind-to-configured Set Port vlan binding method:10/3 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 113 0 packets output, 0 bytes 0 output errors, 0 collisions The following example displays port VLAN binding information: G350-001(super)# show port vlan-binding-mode 10 port 10/3 is bind to all configured VLANs Administration of the Avaya G350 Media Gateway June 2004...

  • Page 114: Configuring Port Redundancy

    You can configure any type of Ethernet port to be redundant to any other. You can configure redundant ports from among the Ethernet LAN port on the G350 front panel and the Ethernet ports (1-24) and the Gigabit Ethernet port (51) on the MM314 Media Module.

  • Page 115: Secondary Port Activation

    NOTE: If you configure the Ethernet LAN port on the G350 front panel to be redundant with the Gigabit Ethernet port on the MM314 Media Module, the Ethernet LAN port becomes the primary port after resetting the G350 even if you configured the Gigabit Ethernet port to be primary.

  • Page 116: Port Redundancy Configuration Examples

    Minimum Time between Switchovers: 60 Switchback interval: 30 Configuring port mirroring This section provides information about configuring port mirroring on G350 devices and includes the following topics: • Port mirroring overview — an overview of port mirroring on the G350 •...

  • Page 117: Port Mirroring Overview

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

  • Page 118: Configuring Spanning Tree

    Configuring advanced switching Configuring spanning tree Configuring spanning tree This section provides information about configuring spanning tree on the G350 and contains the following topics: • Spanning tree overview — an overview of spanning tree protocol • Spanning tree CLI commands —...

  • Page 119: Spanning Tree Per Port

    Spanning tree can take up to 30 seconds to open traffic on a port. This delay can cause problems on ports carrying time-sensitive traffic. You can therefore enable or disable spanning tree in the G350 on a per-port basis to minimize this effect.

  • Page 120: Spanning Tree Cli Commands

    – is sufficient for most networks. Spanning tree CLI commands Use the following commands to configure spanning tree. For more information about these commands, see Avaya G350 Media Gateway CLI Reference, 555-245-202. • Use the command to enable or disable the spanning tree mode for specific set port spantree switch ports.
  • Page 121 Spanning Tree Default Path Costs is according to common spanning tree Port State Cost Priority ------ ------------- ---------- ------------ 6 /1 not-connected 100 6 /2 not-connected 100 6 /3 not-connected 100 6 /4 not-connected 100 Administration of the Avaya G350 Media Gateway June 2004...

  • Page 122: Port Classification

    Port classification overview With the 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 123: Port Classification Configuration Examples

    6/12 regular 6/13 regular 6/14 regular 6/15 regular 6/16 regular 6/17 regular 6/18 regular 6/19 regular 6/20 regular 6/21 regular 6/22 regular 6/23 regular 6/24 regular 6/51 valuable 10/3 regular Administration of the Avaya G350 Media Gateway June 2004...
  • Page 124 Configuring advanced switching Port classification Administration of the Avaya G350 Media Gateway June 2004...

  • Page 125: Configuring Contact Closure

    You can also activate and deactivate contact closure using CLI commands. You can only use feature access codes if you configure the Avaya G350 Media Gateway to use a media server with Avaya Communication Manager software. For more information, see...

  • Page 126: Contact Closure Hardware Configuration

    Activates contact closure for the specified relay. manual-off Deactivates contact closure for the specified relay. To configure the Avaya G350 Media Gateway to activate contact closure when the feature access code is dialed: Enter the command. In the following example, the command sets...

  • Page 127: 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 command to change the status of contact closure to mgc or manual-trigger.
  • Page 128 Configuring contact closure Showing contact closure status Administration of the Avaya G350 Media Gateway June 2004...

  • Page 129: Configuring Rmon Monitoring

    You can configure Remote Monitoring (RMON) for switching on the Avaya G350 Media Gateway. The 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 130: Rmon Configuration Examples

    1 was created successfully The following example creates an RMON event entry: G350-003(super)# rmon event 32 log description “Change of device” owner root event 32 was created successfully The following example creates an RMON history entry with an index of 80 on port 24 of the module in slot 6, recording activity over 60 intervals (buckets) of 20 seconds each.
  • Page 131 0 CRC alignment errors and 0 collisions, # of dropped packet events (due to a lack of resources): 0 # of packets received of length (in octets): 64:18965, 65-127:295657, 128-255:4033, 256-511:137, 512-1023:156, 1024-1518:0, Administration of the Avaya G350 Media Gateway June 2004...
  • Page 132 Configuring RMON monitoring RMON configuration examples Administration of the Avaya G350 Media Gateway June 2004...

  • Page 133: Configuring The Router

    — instructions on how to configure IP fragmentation and reassembly on the G350 router Overview of the G350 router The Avaya G350 Media Gateway has an internal router. You can configure the following routing features on the router: • Interfaces •...

  • Page 134: Configuring Interfaces

    — The Avaya MM342 media module provides a USP WAN interface. • Fast Ethernet Interface — The 10/3 Fast Ethernet port on the front panel of the G350 provides a Fast Ethernet interface. This interface is an autosensing 10/100Mbps Fast Ethernet port. It can be used to connect to a LAN, an external firewall, an external Virtual Private Network (VPN), or a DeMilitarized Zone (DMZ).

  • Page 135: Ip Interface Configuration Commands

    VLAN (Vlan 1). When you configure the G350 without an external VPN or firewall, Vlan 1 is used to connect the internal G350 router to the internal 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 136: Interface Configuration Examples

    A static route becomes inactive whenever the underlying Layer 2 interface is down, except for permanent static routes. You can disable the interface manually using the IP admin-state down command. For more Administration of the Avaya G350 Media Gateway June 2004...
  • Page 137 • 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 G350 Media Gateway has an IP interface. Two kinds of static routes can be configured: •...

  • Page 138: Via Interface Static Route

    Permanent static route The Avaya 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 139: Routing Table Commands

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

  • Page 140: Setting Up A Gre Tunnel

    NOTE: The Avaya G350 Media Gateway does not check whether the configured tunnel source IP address is an existing IP address registered with the G350 router. Administration of the Avaya G350 Media Gateway...

  • Page 141: Routing Packets To A Gre Tunnel

    If a loop occurs, the G350 displays a message that the tunnel is down because of nested tunneling. To assign a high route preference to the destination address of a GRE tunnel, use the...

  • Page 142: Additional Gre Tunnel Parameters

    MTU limit. Additional GRE tunnel parameters Use the following commands to configure additional GRE tunnel parameters. For more information about these commands, see Avaya G350 Media Gateway CLI Reference, 555-245-202. • Use the command in the context of the GRE tunnel interface to add a tunnel checksum checksum to the GRE header of packets traveling through the tunnel.

  • Page 143: Configuring Dhcp And Bootp Relay

    BOOTP is an Internet protocol that allows a diskless workstation to discover the following: • Its own IP address • The IP address of a BOOTP server on the network • A file to be loaded into memory to boot the workstation Administration of the Avaya G350 Media Gateway June 2004...

  • Page 144: Dhcp/Bootp Relay

    The same DHCP/BOOTP relay agent serves both the BOOTP and DHCP protocols. When there is more than one IP interface on a VLAN, the 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.

  • Page 145: Configuring Broadcast Relay

    A hostile user can exploit directed broadcasts to launch a denial-of-service attack on the network. For each interface on the Avaya G350 Media Gateway, you can configure whether the G350 forwards directed broadcast packets to the network address or subnet mask address of the interface.

  • Page 146: Configuring The Arp Table

    Static ARP table entries do not expire. You add static ARP table entries manually with the 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 Administration of the Avaya G350 Media Gateway June 2004...

  • Page 147: Arp Table Commands

    G350-001# no arp 192.168.13.76 ARP table commands Use the following commands to configure the ARP table. For more information about these commands, see Avaya G350 Media Gateway CLI Reference, 555-245-202. • Use the command to add a permanent entry to the Address Resolution Protocol (ARP) table.

  • Page 148: Enabling Proxy Arp

    MAC address. Enabling proxy ARP The G350 supports proxy ARP. Proxy ARP is a technique by which a router provides a false identity when answering ARP requests intended for another device. By falsifying its identify, the router accepts responsibility for routing packets to their true destination.

  • Page 149: Rip Overview

    152. You can configure route redistribution between OSPF, RIP, and static routes. With route redistribution, you can configure the G350 to redistribute routes learned from one protocol into the domain of the other routing protocol. For more information, see Route redistribution on page 154.

  • Page 150: Preventing Routing Loops In Rip

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

  • Page 151: 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 G350 with different RIP versions. This configuration is valid as long as all routers on the subnet are configured with the same version.

  • Page 152: Configuring Ospf

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

  • Page 153: Ospf Limitations

    The 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 G350 cannot be configured to be an OSPF area border router itself.

  • Page 154: Route Redistribution

    Route redistribution is the interaction of multiple routing protocols. OSPF and RIP can be operated concurrently in the G350. In this case, you can configure the G350 to redistribute routes learned from one protocol into the domain of the other routing protocol. Similarly, static routes can be redistributed to RIP and OSPF.

  • Page 155: Export Default Metric

    Router OSPF context to configure route redistribution into OSPF. Export default metric The Avaya G350 Media Gateway enables you to configure the metric to be used in updates that are redistributed from one routing protocol to another.

  • Page 156: Vrrp Configuration Example

    The following diagram illustrates an example of a VRRP configuration: Figure 11: VRRP configuration example There is one main router on IP subnet 20.20.20.0, such as a G350, P333R, C460, or any router that supports VRRP, and a backup router. You can configure more backup routers.

  • Page 157: Vrrp Commands

    Use the command to display VRRP information. show ip vrrp Configuring fragmentation This section provides information about configuring fragmentation on the G350 router and contains the following topics: • Overview of fragmentation — an overview of fragmentation and reassembly on the G350 router •...

  • Page 158: Overview Of Fragmentation

    Configuring fragmentation Overview of fragmentation The G350 supports IP fragmentation and reassembly. The 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 159: 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 G350 to take when a packet matches the rule. Match actions on this list are pointers to the composite operation table.

  • Page 160: Qos Lists

    You can use QoS lists to change the DSCP and Ethernet IEEE 802.1p CoS fields in packets. When a packet matches a rule on the QoS list, the G350 sets one or both of the QoS fields in the packet. The...

  • Page 161: Defining Policy Lists

    — instructions on how to configure the attributes of a policy list, such as a list name, owner, and cookie • Default actions — lists the default action the G350 takes when no rule in the policy list matches the packet • Deleting a policy list —...

  • Page 162: Defining List Identification Attributes

    Default actions When no rule matches a packet, the G350 applies the default action for the list. The following table shows the default action for each type of policy list: List...

  • Page 163: Attaching Policy Lists To An Interface

    Control List and the Egress Access Control List from among the access control lists that are configured on the G350. You can choose the Ingress QoS List and the Egress QoS List from among the QoS lists that are configured on the G350.

  • Page 164: Device-Wide Policy Lists

    After changing the list, you can reattach the list to the interface. Device-wide policy lists You can attach a policy list (other than a policy-based routing list) to every interface on the G350 using one command. To do this, attach a list to the Loopback 1 interface. For more information, see...

  • Page 165: Defining Global Rules

    See Defining rules on page 165. The G350 applies global rules before applying individual rules. To define a global rule: Enter the context of the access control list in which you want to define the rule. Enter one of the following commands, followed by the name of a composite command: —...

  • Page 166: Overview Of Rule Criteria

    — instructions on how to define the source and destination IP addresses to which the rule applies • Source and destination port range — instructions on how to define the source and destination port ranges to which the rule applies Administration of the Avaya G350 Media Gateway June 2004...

  • Page 167: Source And Destination Ip Address

    G350-001(ACL 301/ip rule 1)# source-ip 10.10.0.0 0.0.255.255 The following command specifies a source IP address outside the range 64.236.24.0 through 64.236.24.255 for rule 7 in access control list 308: G350-001(ACL 308/ip rule 7)# no source-ip 64.236.24.0 0.0.0.255 Administration of the Avaya G350 Media Gateway June 2004...

  • Page 168: Source And Destination Port Range

    The following command specifies any destination TCP port in the range 5000 through 5010 for rule 1 in access control list 301: G350-001(ACL 301/ip rule 1)# tcp destination-port range 5000 5010 The following command specifies any source TCP port except a port named http for rule 7 in access...

  • Page 169: Icmp Type And Code

    Use the command, followed by the name of a composite operation, to specify an operation for operation the G350 to perform on a packet when the packet matches the rule. For an explanation of composite operations, see Composite operations on page 170.

  • Page 170: Composite Operations

    Overview of composite operations A composite operation is a set of operations that the 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 G350 handles a packet when the rule matches the packet.

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

    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, since all possible composite operations are pre-configured. Administration of the Avaya G350 Media Gateway June 2004...

  • Page 172: 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 G350 changes the value of the DSCP field in the packet to 5.

  • Page 173: Displaying And Testing Policy Lists

    — — displays a list of all rules configured for the list show ip-rule — — displays the parameters of the current list, including its rules show list Administration of the Avaya G350 Media Gateway June 2004...

  • Page 174: Simulating Packets

    IP packet in the interface. You must specify the number of a policy list, the direction of the packet (in or out), and a source and destination IP address. You may also specify other parameters. For a full list of parameters, see Avaya™ G350 Media Gateway CLI Reference, 555-245-202.
  • Page 175 Configuring policy Displaying and testing policy lists When you run the command, the G350 displays the effect of the policy rules on the simulated ip simulate packet. For example: G350-???(super-if:Vlan 2)# ip simulate 401 in CoS1 dscp46 10.1.1.1 10.2.2.2 tcp 1182 20...
  • Page 176 Configuring policy Displaying and testing policy lists Administration of the Avaya G350 Media Gateway June 2004...

  • Page 177: 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 G350 sends packets that match the rule. A destination can be either an IP address or an interface.

  • Page 178: Source-Based Transit Provider Selection

    Enter one of the following commands, followed by a text string or integer: — name — defines a list name (text string). The default value is owner. — owner — defines a list owner (text string). The default value is list#<listnumber>. Administration of the Avaya G350 Media Gateway June 2004...

  • Page 179: Attaching A Pbr List To An Interface

    For example, you can ip pbr-group remove the PBR list from the VLAN interface by typing the following commands: G350-001# interface Vlan 1 G350-001(if:Vlan 1)# no ip pbr-group Done! Administration of the Avaya G350 Media Gateway June 2004...

  • Page 180: Defining Rules

    To view the existing rules in a PBR list, enter the list’s context and type ip show-rule Rule criteria The rule criteria for PBR rules are largely the same as the rule criteria for other policy list rules. Refer to Rule criteria on page 166. Administration of the Avaya G350 Media Gateway June 2004...

  • Page 181: Defining Next Hop Lists

    G350 to apply to packets that match the rule. You can specify Destination Based Routing instead of a next hop list, in which case the G350 applies DBR to a packet when the packet matches the rule. If the next hop list specified in the rule does not exist, the G350 applies DBR to packets that match the rule.

  • Page 182: Assigning Attributes To Next Hop Lists

    — displays all the parameters of the specified show ip pbr-list <list number> detailed PBR list — — displays a list of each G350 interface to which a PBR list is show ip active-lists attached, along with the number and name of the PBR list —...

  • Page 183: Application Example

    IP address between 6.0.0.0. and 6.255.255.255, or the DSCP value 34, 41, 43, 44, or 46, and route these packets in accordance with next hop list 1. ip-rule 1 next-hop list 1 source-ip 6.0.0.0. 0.255.255.255 dscp 34 exit Administration of the Avaya G350 Media Gateway June 2004...
  • Page 184 5.0.0.0. 0.255.255.255 destination-ip host 149.49.43.189 tcp destination-port range 20 21 exit ip-rule 10 next-hop list 2 ip-protocol tcp source-ip 5.0.0.0. 0.255.255.255 destination-ip host 149.49.43.188 tcp destination-port eq Http exit exit Administration of the Avaya G350 Media Gateway June 2004...
  • Page 185 Vlan 5 ip pbr-group 802 ip address 5.0.0.254 255.0.0.0 exit The following commands create VLAN 6, designate it as the VLAN connecting the G350 to the ICC, and assign PBR list 801 to the VLAN. interface Vlan 6 icc-vlan...
  • Page 186 134.1.156.1. Next hop number 20 is Null0. Thus, packets matching rules to which this list is assigned are routed to 134.1.156.1. If that address is unavailable, the packets are dropped. ip next-hop-list 2 name "Data" next-hop-ip 10 134.1.156.1 next-hop-interface 20 Null0 exit Administration of the Avaya G350 Media Gateway June 2004...
  • Page 187 Configuring policy-based routing Application example Figure 15, Sample policy-based routing application, on page 187 illustrates the sample application described above. Figure 15: Sample policy-based routing application Administration of the Avaya G350 Media Gateway June 2004...
  • Page 188 Configuring policy-based routing Application example Administration of the Avaya G350 Media Gateway June 2004...

  • Page 189: Setting Synchronization

    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. If no MM710 is present, it is not necessary to set synchronization.

  • Page 190: Displaying Synchronization Status

    The status can be Active, Standby, or Not Configured. The status is Not Configured when a source has not been defined, for example, when there are no T1 cards installed. Administration of the Avaya G350 Media Gateway June 2004...

  • Page 191: Traps And Mibs

    — a list of all G350 traps. • G350 MIBs — a list of all G350 MIBs. G350 traps The following table provides a list of all G350 traps with important information about each trap: Parameters Trap Name/ Name (MIB variables) Class...
  • Page 192 SNMP_Authen_ P330 SECURITY Notification authentic Incorrect An authentication failure Failure Community Name trap indicates that the Failure (authentication protocol is not properly Failure Trap) authenticated. enterprise:$E ($e) args($#):$* 2 of 12 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 193 P330 SWITCH Info lseIntPort CAM Change at $1 This trap reports of the stChange astChange FABRIC CAMLast occurred configuration Trap Change changes. It is Trap enabled/disabled by chLntAgCAMChangeTrap 3 of 12 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 194 ChangeEvent Activation Event policy list changed in the active list specific EntID, ipPolicy to $2 for a policy-enabled box or ActivationList, module. ipPolicy Activationif Index, ipPolicy ActivationSub Context 4 of 12 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 195 Notification Dormant Dormant Port This trap reports the return ult, FABRIC PortOk Connection of connection on a genPortGroup Returned to Normal dormant port. on Module $2 Port genPortId 5 of 12 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 196 Status wanLocal ifIndex, Notification wanLocal Local Alarm on Local alarms, such as AlarmOff ifAdminStatus, AlarmOff interface $4 was LOS, was cleared. ifOperStatus, cleared ifName, ifAlias, dsx1Line Status 6 of 12 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 197 AVAYA- TEMP Notification AvEntFanOk Fan $2 is OK This trap reports the return Index, ENTITY to function of a faulty fan. entPhysical Descr, entPhySensor Value, avEntPhy SensorLo Warning 7 of 12 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 198 This trap reports a problem PwrFlt Index, ENTITY PwrFlt power supply Fault with a 3.3V power supply. entPhysical Descr, entPhySensor Value, avEntPhy SensorHi Warning, avEntPhy SensorLo Warningent Physical ParentRelPos 8 of 12 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 199 This trap reports a problem PwrFlt Index, ENTITY PwrFlt power supply Fault with a 1.6V power supply. entPhysical Descr, entPhySensor Value, avEntPhy SensorHi Warning, avEntPhy SensorLo Warningent Physical ParentRelPos 9 of 12 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 200 Index, ENTITY PwrFlt power supply Fault correction of a problem entPhysical Cleared with a 3.3V power supply. Descr, entPhySensor Value, avEntPhy SensorHi Warning, avEntPhy SensorLo Warningent Physical ParentRelPos 10 of 12 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 201 Index, ENTITY PwrFlt power supply Fault correction of a problem entPhysical Cleared with a 1.6V power supply. Descr, entPhySensor Value, avEntPhy SensorHi Warning, avEntPhy SensorLo Warningent Physical ParentRelPos 11 of 12 Administration of the Avaya G350 Media Gateway June 2004...

  • Page 202: G350 Mibs

    The following table provides a list of the MIB files and their associated modules that are supported by the G350: MIB File MIB Module 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 UTILIZATION-MANAGEMENT-MIB.my UTILIZATION-MANAGEMENT-MIB ENTITY-SENSOR-MIB.my ENTITY-SENSOR-MIB RSTP-MIB.my RSTP-MIB APPLIC-MIB.MY APPLIC-MIB DS1-MIB.my DS1-MIB 1 of 2 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 203 USM-MIB.my USM-MIB VACM-MIB.my VACM-MIB OSPF-MIB.my OSPF-MIB Tunnel-MIB.my TUNNEL-MIB 2 of 2 The following table provides a list of the MIBs in the Load.MIB file that are supported by the 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...
  • Page 204 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 2 of 2 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 205 1.3.6.1.2.1.10.32.2.1.4 frCircuitReceivedBECNs 1.3.6.1.2.1.10.32.2.1.5 frCircuitSentFrames 1.3.6.1.2.1.10.32.2.1.6 frCircuitSentOctets 1.3.6.1.2.1.10.32.2.1.7 frCircuitReceivedFrames 1.3.6.1.2.1.10.32.2.1.8 frCircuitReceivedOctets 1.3.6.1.2.1.10.32.2.1.9 frCircuitCreationTime 1.3.6.1.2.1.10.32.2.1.10 frCircuitLastTimeChange 1.3.6.1.2.1.10.32.2.1.11 frCircuitCommittedBurst 1.3.6.1.2.1.10.32.2.1.12 frCircuitExcessBurst 1.3.6.1.2.1.10.32.2.1.13 frCircuitThroughput 1.3.6.1.2.1.10.32.2.1.14 frErrIfIndex 1.3.6.1.2.1.10.32.3.1.1 frErrType 1.3.6.1.2.1.10.32.3.1.2 frErrData 1.3.6.1.2.1.10.32.3.1.3 frErrTime 1.3.6.1.2.1.10.32.3.1.4 frTrapState 1.3.6.1.2.1.10.32.4.1 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 206 The following table provides a list of the MIBs in the ENTITY-MIB.my file that are supported by the 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 1 of 2 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 207 1.3.6.1.2.1.4.24.3 ipCidrRouteDest 1.3.6.1.2.1.4.24.4.1.1 ipCidrRouteMask 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 1 of 2 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 208 G350 MIBs Object 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 2 of 2 The following table provides a list of the MIBs in theVRRP-MIB.my file that are supported by the 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...
  • Page 209 The following table provides a list of the MIBs in the ENTITY-SENSOR-MIB.my file that are supported by the 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 entPhySensorUnitsDisplay 1.3.6.1.2.1.99.1.1.1.6 entPhySensorValueTimeStamp 1.3.6.1.2.1.99.1.1.1.7 entPhySensorValueUpdateRate 1.3.6.1.2.1.99.1.1.1.8 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 210 Traps and MIBs G350 MIBs The following table provides a list of the MIBs in the RSTP-MIB.my file that are supported by the G350 and their OIDs: Object dot1dStpVersion 1.3.6.1.2.1.17.2.16 dot1dStpTxHoldCount 1.3.6.1.2.1.17.2.17 dot1dStpPathCostDefault 1.3.6.1.2.1.17.2.18 dot1dStpPortProtocolMigration 1.3.6.1.2.1.17.2.19.1.1 dot1dStpPortAdminEdgePort 1.3.6.1.2.1.17.2.19.1.2 dot1dStpPortOperEdgePort 1.3.6.1.2.1.17.2.19.1.3 dot1dStpPortAdminPointToPoint 1.3.6.1.2.1.17.2.19.1.4...
  • Page 211 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 dsx1IntervalPCVs 1.3.6.1.2.1.10.18.8.1.8 dsx1IntervalLESs 1.3.6.1.2.1.10.18.8.1.9 2 of 3 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 212 1.3.6.1.2.1.10.23.3.2.1.2 The following table provides a list of the MIBs in the RFC1213-MIB.my file that are supported by the G350 and their OIDs: Object sysDescr 1.3.6.1.2.1.1.1 sysObjectID 1.3.6.1.2.1.1.2 1 of 4 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 213 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 2 of 4 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 214 1.3.6.1.2.1.4.21.1.3 ipRouteMetric2 1.3.6.1.2.1.4.21.1.4 ipRouteMetric3 1.3.6.1.2.1.4.21.1.5 ipRouteMetric4 1.3.6.1.2.1.4.21.1.6 ipRouteNextHop 1.3.6.1.2.1.4.21.1.7 ipRouteType 1.3.6.1.2.1.4.21.1.8 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 3 of 4 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 215 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 snmpOutGenErrs 1.3.6.1.2.1.11.24 snmpOutGetRequests 1.3.6.1.2.1.11.25 snmpOutGetNexts 1.3.6.1.2.1.11.26 snmpOutSetRequests 1.3.6.1.2.1.11.27 snmpOutGetResponses 1.3.6.1.2.1.11.28 snmpOutTraps 1.3.6.1.2.1.11.29 snmpEnableAuthenTraps 1.3.6.1.2.1.11.30 4 of 4 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 216 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 avEntPhySensorLoShutdown 1.3.6.1.4.1.6889.2.1.99.1.1.6 avEntPhySensorEventSupportMask 1.3.6.1.4.1.6889.2.1.99.1.1.7 The following table provides a list of the MIBs in the Rnd.MIB file that are supported by the G350 and their OIDs: Object genGroupHWVersion 1.3.6.1.4.1.81.8.1.1.24 genGroupConfigurationSymbol 1.3.6.1.4.1.81.8.1.1.21 genGroupHWStatus 1.3.6.1.4.1.81.8.1.1.17 The following table provides a list of the MIBs in the XSWITCH-MIB.my file that are supported by the...
  • Page 217 1.3.6.1.4.1.81.31.1.2.1.2 ipInterfaceLowerIfAlias 1.3.6.1.4.1.81.31.1.2.1.3 ipInterfaceType 1.3.6.1.4.1.81.31.1.2.1.4 ipInterfaceForwardIpBroadcast 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 1 of 3 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 218 1.3.6.1.4.1.81.31.1.6.1.3 relayVlStatus 1.3.6.1.4.1.81.31.1.6.1.4 relayVlRelayAddr 1.3.6.1.4.1.81.31.1.6.1.5 ipRedundancyStatus 1.3.6.1.4.1.81.31.1.9.1 ipRedundancyTimeout 1.3.6.1.4.1.81.31.1.9.2 ipRedundancyPollingInterval 1.3.6.1.4.1.81.31.1.9.3 ipShortcutARPServerStatus 1.3.6.1.4.1.81.31.1.10.1 distributionListRoutingProtocol 1.3.6.1.4.1.81.31.1.12.1.1 distributionListDirection 1.3.6.1.4.1.81.31.1.12.1.2 distributionListIfIndex 1.3.6.1.4.1.81.31.1.12.1.3 distributionListRouteProtocol 1.3.6.1.4.1.81.31.1.12.1.4 distributionListProtocolSpecific1 1.3.6.1.4.1.81.31.1.12.1.5 distributionListProtocolSpecific2 1.3.6.1.4.1.81.31.1.12.1.6 distributionListProtocolSpecific3 1.3.6.1.4.1.81.31.1.12.1.7 2 of 3 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 219 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 iphcControlNonTcpMode 1.3.6.1.4.1.81.31.1.15.1.1.16 ospfXtndIfIpAddress 1.3.6.1.4.1.81.31.1.16.1.1 ospfXtndIfAddressLessIf 1.3.6.1.4.1.81.31.1.16.1.2 ospfXtndIfPassiveMode 1.3.6.1.4.1.81.31.1.16.1.3 vlConfIndex 1.3.6.1.4.1.81.31.3.1.1.1 vlConfAlias 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 3 of 3 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 220 1.3.6.1.2.1.10.33.4.1.7 rs232SyncPortRole 1.3.6.1.2.1.10.33.4.1.8 rs232SyncPortEncoding 1.3.6.1.2.1.10.33.4.1.9 rs232SyncPortRTSControl 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 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 221 1.3.6.1.2.1.23.3.1.5 rip2IfConfReceive 1.3.6.1.2.1.23.3.1.6 rip2IfConfDefaultMetric 1.3.6.1.2.1.23.3.1.7 rip2IfConfStatus 1.3.6.1.2.1.23.3.1.8 rip2IfConfSrcAddress 1.3.6.1.2.1.23.3.1.9 The following table provides a list of the MIBs in the IF-MIB.my file that are supported by the G350 and their OIDs: Object ifNumber 1.3.6.1.2.1.2.1 ifIndex 1.3.6.1.2.1.2.2.1.1 ifDescr 1.3.6.1.2.1.2.2.1.2 ifType 1.3.6.1.2.1.2.2.1.3...
  • Page 222 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 ifCounterDiscontinuityTime 1.3.6.1.2.1.31.1.1.1.19 2 of 2 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 223 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 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 1 of 2 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 224 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 2 of 2 The following table provides a list of the MIBs in the DS0-MIB.my file that are supported by the 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...
  • Page 225 1.3.6.1.4.1.81.36.1.1.10 ipPolicyListErrMsg 1.3.6.1.4.1.81.36.1.1.11 ipPolicyListTrustedFields 1.3.6.1.4.1.81.36.1.1.12 ipPolicyListScope 1.3.6.1.4.1.81.36.1.1.13 ipPolicyListIpOptionOperation 1.3.6.1.4.1.81.36.1.1.14 ipPolicyListIpFragmentationOperation 1.3.6.1.4.1.81.36.1.1.15 ipPolicyListType 1.3.6.1.4.1.81.36.1.1.16 ipPolicyListEtherTypeDefaultOperation 1.3.6.1.4.1.81.36.1.1.17 ipPolicyRuleSlot 1.3.6.1.4.1.81.36.2.1.1 ipPolicyRuleListID 1.3.6.1.4.1.81.36.2.1.2 ipPolicyRuleID 1.3.6.1.4.1.81.36.2.1.3 ipPolicyRuleSrcAddr 1.3.6.1.4.1.81.36.2.1.4 ipPolicyRuleSrcAddrWild 1.3.6.1.4.1.81.36.2.1.5 ipPolicyRuleDstAddr 1.3.6.1.4.1.81.36.2.1.6 1 of 5 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 226 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 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 2 of 5 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 227 1.3.6.1.4.1.81.36.5.1.14 ipPolicyQuerySubContext 1.3.6.1.4.1.81.36.5.1.15 ipPolicyQueryEtherTypeType 1.3.6.1.4.1.81.36.5.1.16 ipPolicyQueryEtherTypeTrafficType 1.3.6.1.4.1.81.36.5.1.17 ipPolicyQueryIcmpTypeCode 1.3.6.1.4.1.81.36.5.1.18 ipPolicyDiffServControlSlot 1.3.6.1.4.1.81.36.6.1.1 ipPolicyDiffServControlChecksum 1.3.6.1.4.1.81.36.6.1.2 ipPolicyDiffServControlTrustedFields 1.3.6.1.4.1.81.36.6.1.3 ipPolicyDiffServControlValidityStatus 1.3.6.1.4.1.81.36.6.1.4 ipPolicyDiffServControlErrMsg 1.3.6.1.4.1.81.36.6.1.5 ipPolicyAccessControlViolationEntID 1.3.6.1.4.1.81.36.7.1.1 ipPolicyAccessControlViolationSrcAddr 1.3.6.1.4.1.81.36.7.1.2 ipPolicyAccessControlViolationDstAddr 1.3.6.1.4.1.81.36.7.1.3 ipPolicyAccessControlViolationProtocol 1.3.6.1.4.1.81.36.7.1.4 3 of 5 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 228 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 ipPolicyDSCPmapErrMsg 1.3.6.1.4.1.81.36.9.1.9 ipPolicyActivationEntID 1.3.6.1.4.1.81.36.10.1.1 ipPolicyActivationifIndex 1.3.6.1.4.1.81.36.10.1.2 ipPolicyActivationSubContext 1.3.6.1.4.1.81.36.10.1.3 ipPolicyActivationSubContextName 1.3.6.1.4.1.81.36.10.1.4 ipPolicyActivationList 1.3.6.1.4.1.81.36.10.1.5 4 of 5 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 229 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 ipPolicyValidDSCPStatus 1.3.6.1.4.1.81.36.11.3.1.6 ipPolicyValidDSCPApplicabilityType 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 5 of 5 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 230 1.3.6.1.2.1.17.2.10 dot1dStpForwardDelay 1.3.6.1.2.1.17.2.11 dot1dStpBridgeMaxAge 1.3.6.1.2.1.17.2.12 dot1dStpBridgeHelloTime 1.3.6.1.2.1.17.2.13 dot1dStpBridgeForwardDelay 1.3.6.1.2.1.17.2.14 dot1dStpPort 1.3.6.1.2.1.17.2.15.1.1 dot1dStpPortPriority 1.3.6.1.2.1.17.2.15.1.2 dot1dStpPortState 1.3.6.1.2.1.17.2.15.1.3 dot1dStpPortEnable 1.3.6.1.2.1.17.2.15.1.4 dot1dStpPortPathCost 1.3.6.1.2.1.17.2.15.1.5 dot1dStpPortDesignatedRoot 1.3.6.1.2.1.17.2.15.1.6 dot1dStpPortDesignatedCost 1.3.6.1.2.1.17.2.15.1.7 dot1dStpPortDesignatedBridge 1.3.6.1.2.1.17.2.15.1.8 dot1dStpPortDesignatedPort 1.3.6.1.2.1.17.2.15.1.9 1 of 2 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 231 1.3.6.1.4.1.81.7.9.3.7.1.3 chLntAgMaxTrapsNumber 1.3.6.1.4.1.81.7.9.3.100 chGroupList 1.3.6.1.4.1.81.7.18 chLogFileGroupId 1.3.6.1.4.1.81.7.22.1.1 chLogFileIndex 1.3.6.1.4.1.81.7.22.1.2 chLogFileName 1.3.6.1.4.1.81.7.22.1.3 chLogFileAbsoluteTime 1.3.6.1.4.1.81.7.22.1.4 chLogFileMessage 1.3.6.1.4.1.81.7.22.1.5 chLogFileEncryptedMessage 1.3.6.1.4.1.81.7.22.1.6 genGroupId 1.3.6.1.4.1.81.8.1.1.1 genGroupSWVersion 1.3.6.1.4.1.81.8.1.1.2 genGroupKernelVersion 1.3.6.1.4.1.81.8.1.1.3 genGroupType 1.3.6.1.4.1.81.8.1.1.4 genGroupDescr 1.3.6.1.4.1.81.8.1.1.5 1 of 4 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 232 1.3.6.1.4.1.81.8.1.1.27 genGroupThresholdStatus 1.3.6.1.4.1.81.8.1.1.28 genGroupEavesdropping 1.3.6.1.4.1.81.8.1.1.29 genGroupMainSWVersion 1.3.6.1.4.1.81.8.1.1.30 genGroupMPSActivityStatus 1.3.6.1.4.1.81.8.1.1.31 genGroupBUPSActivityStatus 1.3.6.1.4.1.81.8.1.1.32 genGroupPrepareCounters 1.3.6.1.4.1.81.8.1.1.33 genGroupPortLastChange 1.3.6.1.4.1.81.8.1.1.34 genGroupIntPortLastChange 1.3.6.1.4.1.81.8.1.1.35 genGroupFaultMask 1.3.6.1.4.1.81.8.1.1.36 genGroupTypeName 1.3.6.1.4.1.81.8.1.1.37 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 2 of 4 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 233 1.3.6.1.4.1.81.9.1.1.5 genPortAdminStatus 1.3.6.1.4.1.81.9.1.1.10 genPortFaultMask 1.3.6.1.4.1.81.9.1.1.14 genPortSWRdFault 1.3.6.1.4.1.81.9.1.1.15 genPortVLANMode 1.3.6.1.4.1.81.9.1.1.19 genPortAdminPermission 1.3.6.1.4.1.81.9.1.1.20 genPortName 1.3.6.1.4.1.81.9.1.1.21 genPortClassification 1.3.6.1.4.1.81.9.1.1.22 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 3 of 4 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 234 1.3.6.1.4.1.6889.2.9.1.1.10.12 cmgHardwareStatusMask 1.3.6.1.4.1.6889.2.9.1.1.10.13 cmgModuleSlot 1.3.6.1.4.1.6889.2.9.1.1.11.1.1.1 cmgModuleType 1.3.6.1.4.1.6889.2.9.1.1.11.1.1.2 cmgModuleDescription 1.3.6.1.4.1.6889.2.9.1.1.11.1.1.3 cmgModuleName 1.3.6.1.4.1.6889.2.9.1.1.11.1.1.4 cmgModuleSerialNumber 1.3.6.1.4.1.6889.2.9.1.1.11.1.1.5 cmgModuleHWVintage 1.3.6.1.4.1.6889.2.9.1.1.11.1.1.6 cmgModuleHWSuffix 1.3.6.1.4.1.6889.2.9.1.1.11.1.1.7 cmgModuleFWVersion 1.3.6.1.4.1.6889.2.9.1.1.11.1.1.8 cmgModuleNumberOfPorts 1.3.6.1.4.1.6889.2.9.1.1.11.1.1.9 cmgModuleFaultMask 1.3.6.1.4.1.6889.2.9.1.1.11.1.1.10 cmgModuleStatusMask 1.3.6.1.4.1.6889.2.9.1.1.11.1.1.11 cmgModuleReset 1.3.6.1.4.1.6889.2.9.1.1.11.1.1.12 1 of 4 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 235 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 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 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 2 of 4 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 236 1.3.6.1.4.1.6889.2.9.1.4.5.1.4 cmgVoipJitterBufferSize 1.3.6.1.4.1.6889.2.9.1.4.5.1.5 cmgVoipTotalChannels 1.3.6.1.4.1.6889.2.9.1.4.5.1.6 cmgVoipChannelsInUse 1.3.6.1.4.1.6889.2.9.1.4.5.1.7 cmgVoipAverageOccupancy 1.3.6.1.4.1.6889.2.9.1.4.5.1.8 cmgVoipHyperactivity 1.3.6.1.4.1.6889.2.9.1.4.5.1.9 cmgVoipAdminState 1.3.6.1.4.1.6889.2.9.1.4.5.1.10 cmgVoipDspFWVersion 1.3.6.1.4.1.6889.2.9.1.4.5.1.11 cmgVoipDspStatus 1.3.6.1.4.1.6889.2.9.1.4.5.1.12 cmgVoipEngineReset 1.3.6.1.4.1.6889.2.9.1.4.5.1.13 cmgVoipFaultMask 1.3.6.1.4.1.6889.2.9.1.4.5.1.14 cmgCcModule 1.3.6.1.4.1.6889.2.9.1.6.1.1.1 cmgCcPort 1.3.6.1.4.1.6889.2.9.1.6.1.1.2 cmgCcRelay 1.3.6.1.4.1.6889.2.9.1.6.1.1.3 3 of 4 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 237 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 cmgDynCacRBBL 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 4 of 4 The following table provides a list of the MIBs in the FRAME-RELAY-DTE-MIB.my file that are supported by the 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 frDlcmiAddressLen 1.3.6.1.2.1.10.32.1.1.4...
  • Page 238 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 The following table provides a list of the MIBs in the IP-MIB.my file that are supported by the 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...
  • Page 239 The following table provides a list of the MIBs in the Load12-MIB.my file that are supported by the 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 1 of 2 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 240 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 2 of 2 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 241 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 The following table provides a list of the MIBs in the WAN-MIB.MY file that are supported by the 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...
  • Page 242 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.26 ifTableXtndInputLoad 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.27 ifTableXtndOutputLoad 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.28 ifTableXtndReliability 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.29 ifTableXtndCacBBL 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.31 ifTableXtndCacPriority 1.3.6.1.4.1.6889.2.1.6.2.2.1.1.32 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 2 of 3 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 243 1.3.6.1.2.1.11.6 snmpEnableAuthenTraps 1.3.6.1.2.1.11.30 snmpOutPkts 1.3.6.1.2.1.11.2 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 1 of 2 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 244 1.3.6.1.2.1.11.26 snmpOutSetRequests 1.3.6.1.2.1.11.27 snmpOutGetResponses 1.3.6.1.2.1.11.28 snmpOutTraps 1.3.6.1.2.1.11.29 2 of 2 The following table provides a list of the MIBs in the OSPF-MIB.my file that are supported by the 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...
  • Page 245 1.3.6.1.2.1.14.7.1.7 ospfIfRetransInterval 1.3.6.1.2.1.14.7.1.8 ospfIfHelloInterval 1.3.6.1.2.1.14.7.1.9 ospfIfRtrDeadInterval 1.3.6.1.2.1.14.7.1.10 ospfIfPollInterval 1.3.6.1.2.1.14.7.1.11 ospfIfState 1.3.6.1.2.1.14.7.1.12 ospfIfDesignatedRouter 1.3.6.1.2.1.14.7.1.13 ospfIfBackupDesignatedRouter 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 2 of 3 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 246 The following table provides a list of the MIBs in the TUNNEL-MIB.my file that are supported by the 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 tunnelIfEncapsMethod 1.3.6.1.2.1.10.131.1.1.1.1.3 tunnelIfTOS 1.3.6.1.2.1.10.131.1.1.1.1.4 tunnelIfHopLimit 1.3.6.1.2.1.10.131.1.1.1.1.5 1 of 2 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 247 1.3.6.1.2.1.10.131.1.1.2.1.1 tunnelConfigRemoteAddress 1.3.6.1.2.1.10.131.1.1.2.1.2 tunnelConfigEncapsMethod 1.3.6.1.2.1.10.131.1.1.2.1.3 tunnelConfigID 1.3.6.1.2.1.10.131.1.1.2.1.4 tunnelConfigStatus 1.3.6.1.2.1.10.131.1.1.2.1.5 ipTunnelIfIndex 1.3.6.1.4.1.81.31.8.1.1.1 ipTunnelIfChecksum 1.3.6.1.4.1.81.31.8.1.1.2 ipTunnelIfKey 1.3.6.1.4.1.81.31.8.1.1.3 ipTunnelIfkeyMode 1.3.6.1.4.1.81.31.8.1.1.4 ipTunnelIfAgingTimer 1.3.6.1.4.1.81.31.8.1.1.5 ipTunnelIfMTUDiscovery 1.3.6.1.4.1.81.31.8.1.1.6 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 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 248 Traps and MIBs G350 MIBs Administration of the Avaya G350 Media Gateway June 2004...

  • Page 249: B Configuring The G350 Using The Avaya Iw

    This chapter explains how to configure the Avaya G350 Media Gateway using the Avaya Installation Wizard (Avaya IW). The Avaya IW is a web-based installation wizard that is used with the Avaya G350 Media Gateway to perform initial configuration tasks and to upgrade software and firmware. The Avaya IW is designed for use with systems that contain an S8300 Media Server, operating in either ICC or LSP mode.
  • Page 250 Configuring the G350 using the Avaya IW Preliminary screens Click . The Avaya IW performs system auto-discovery and displays the results on the Continue following screen: Click . The Import Electronic PreInstallation Worksheet screen appears. This screen Continue allows you to import system data from the Electronic PreInstallation Worksheet (EPW). The EPW is described in Installation of the Avaya G350 Media Gateway, 555-245-104.

  • Page 251: Mgc Configuration And Upgrade

    . The Usage Options screen appears. This screen allows you to initiate the process Continue of configuring an S8300 media server that is installed on the G350 as a Media Gateway Controller (MGC). You can configure the S8300 as either the primary MGC (ICC configuration) or as a backup MGC (LSP configuration).
  • Page 252 . The Checklist screen appears. The Checklist screen displays a list of required Continue and optional items you need to configure the G350. For details, see Installation of the Avaya G350 Media Gateway, 555-245-104. Administration of the Avaya G350 Media Gateway...
  • Page 253 Primary Management Interface (PMI). For a description of the PMI, see Configuring the Primary Management Interface (PMI) on page 40. Click . The Date/Time screen appears. This screen allows you to reset the G350’s date Continue and time. Administration of the Avaya G350 Media Gateway...

  • Page 254: Upgrading An Existing Mgc

    Configuring the G350 using the Avaya IW Upgrading an existing MGC Click . The Product ID screen appears. If you are configuring a new G350, enter the Continue product ID in the ID field and select Assign the new product ID...
  • Page 255 Configuring the G350 using the Avaya IW Upgrading an existing MGC Click . The Install Update screen appears. This screen allows you to install or remove Continue Avaya Communication Manager updates. Click . The Install Unicode Phone Message Files screen appears. This screen allows you...
  • Page 256 . The Media Server - IP Addresses screen appears. If your S8300 media server is Continue already configured, the Avaya IW should detect and display its address information in this screen. If not, you must enter the required information. Click .
  • Page 257 Configuring the G350 using the Avaya IW Upgrading an existing MGC Click . If you selected Uninteruptable Power Supply (UPS) in the Optional Services Continue screen, the Uninteruptable Power Supply (UPS) screen appears. Enter the required information. Click . If you selected Domain Name Service (DNS) in the Optional Services screen, Continue the Domain Name Service (DNS) screen appears.
  • Page 258 Continue the INADS screen appears. Enter a dialup IP address for INADS remote support. For instructions on how to obtain the INADS IP address, see Installation of the Avaya G350 Media Gateway, 555-245-104. Administration of the Avaya G350 Media Gateway...
  • Page 259 . The Security Files screen appears. This screen displays the status of your license and authentication files, and allows you to install these files from a laptop. For information on these files, see Installation of the Avaya G350 Media Gateway, 555-245-104. Administration of the Avaya G350 Media Gateway...

  • Page 260: Gateway Configuration

    . The IP Addresses screen Media Gateways appears. This screen displays the G350’s ID, as well as the type of media module residing in each slot of the G350’s chassis. To continue, click the icon corresponding to the G350 in the Action column.

  • Page 261: Administration Of The Avaya G350 Media Gateway June

    Configuring the G350 using the Avaya IW Gateway configuration Click . The SNMP screen appears. For information on configuring SNMP settings, see Continue Configuring SNMP on page 97. Click . The Media Gateway Controller Information screen appears. The IP addresses of Continue the primary MGC appears in the first IP address box.
  • Page 262 . The IP Addresses screen appears. This screen displays the G350’s ID, as well as Continue the type of media module residing in each slot of the G350’s chassis. To continue, click the icon corresponding to the G350 in the column.
  • Page 263 Configuring the G350 using the Avaya IW Firmware configuration • To proceed without upgrading any firmware, clear all the boxes in the column and Select click Continue twice. The Firmware File Upload screen allows you to upload a new firmware file from a laptop. Enter the file path of the file you want to upload, or use the button to locate the file.
  • Page 264 Click Media Gateways>G350 Modems from the main menu. The G350 Modem Type Selection screen appears. Select the modem type you want to use. For more information on using a modem with the G350, see Configuring the G350 for modem use page 67.
  • Page 265 Configuring the G350 using the Avaya IW Modem configuration If you selected , enter the required information in the G350 Serial Modem Serial Modem Configuration screen, then click Continue If you selected , enter the required information in the G350 USB Modem...

  • Page 266: Telephony Configuration

    Configuring the G350 using the Avaya IW Telephony configuration Telephony configuration To configure the G350’s telephony parameters, do one of the following: • From the applicable modem configuration screen, click , or Continue • Click Telephony from the main menu.
  • Page 267 Configuring the G350 using the Avaya IW Telephony configuration Click . The Call Routing screen appears. Enter the required call routing information. Continue Click . The Extension Ranges screen appears. To add a range, click Continue Add Extension and enter the starting and ending extensions for the range. If you want this range to be...

  • Page 268: Trunk Configuration

    Enter the file path of the file you want to import, or use the button to locate the Browse file. Click Continue Trunk configuration To configure the G350’s trunk parameters, do one of the following: • From the Import Name/Number List screen, click , or Continue • Click Trunking from the main menu.
  • Page 269 The Cross-Connects screen appears. If your trunk cross-connects have been completed, click Continue to proceed with trunk configuration. If your trunk cross-connects have not been completed, it is strongly recommended to exit the Avaya IW and complete all cross-connects before proceeding with trunk configuration. Click .
  • Page 270 Configuring the G350 using the Avaya IW Trunk configuration You can perform the following actions in the IP Trunk List screen: • Adding a trunk • Modifying trunk parameters • Modifying IP route configuration • Displaying trunk status • Removing a trunk...
  • Page 271 Configuring the G350 using the Avaya IW Trunk configuration The IP Trunk Configuration screen appears, with the trunk’s current parameters displayed. Modify the trunk parameters and click Continue . The IP Trunk List appears. Select an additional action from the column, or click to proceed to the CO Trunk List screen.
  • Page 272 Configuring the G350 using the Avaya IW Trunk configuration The IP Route Configuration screen appears. The IP Route Configuration screen displays the extension ranges available for private-network routing. Modify these ranges, if any, and click . The IP Trunk List appears. Select an...
  • Page 273 Configuring the G350 using the Avaya IW Trunk configuration The IP Trunk Status screen appears. The IP Trunk Status screen displays the operational status of the trunk. To refresh the information, click . Otherwise, click . The IP Trunk List appears. Select an additional action...
  • Page 274 Configuring the G350 using the Avaya IW Trunk configuration A message appears asking if you want to remove the trunk. Click to remove the trunk. Select an additional action from the Actions column, or click to proceed to the CO Trunk List screen.
  • Page 275 Configuring the G350 using the Avaya IW Endpoint installation The CO Trunk List screen appears. This screen lists trunk media modules detected in the G350 and allows you to configure a media module and run diagnostics. To configure or run diagnostics on a trunk media module, click the Actions icon for the module.

  • Page 276: Alarm Configuration

    The Modem Alarming Status & Configuration screen appears. This screen detects any modem connected to the G350. The screen also displays the results of tests performed on the modem. You can perform the following actions from this screen: •...
  • Page 277 Click . The OSS Configuration screen appears. Enter the required information from the Continue ART tool. For information on using the ART tool, see Installation of the Avaya G350 Media Gateway, 555-245-104. Administration of the Avaya G350 Media Gateway June 2004...
  • Page 278 Configuring the G350 using the Avaya IW Password and final screens Click . The SNMP Configuration screen appears. For information on SNMP Continue configuration, see Configuring SNMP on page 97. Password and final screens To change your password (optional) and complete the installation, do one of the following: •...
  • Page 279 Configuring the G350 using the Avaya IW Password and final screens The Change Root Password screen appears. This screen allows you to change the root password on the G350. Click . The Finish Up screen appears. This screen allows you to save the installation log Continue file to your laptop.
  • Page 280 Configuring the G350 using the Avaya IW Password and final screens Click . If you have not installed an allocation license file, a warning appears reminding Continue you to install this file. Administration of the Avaya G350 Media Gateway June 2004...
  • Page 281 Click . The Verify Gateway Installation screen appears. This screen displays a list of Continue CLI commands that you can use to verify the G350 configuration. The following figure shows a portion of the Verify Gateway Installation screen. Click . The Launch Device Manager screen appears. This screen allows you to launch...
  • Page 282 Configuring the G350 using the Avaya IW Password and final screens Click . The Congratulations! screen appears to inform you that the installation is Continue complete. To exit the Avaya IW, click Finish The Exit AIW screen appears. Administration of the Avaya G350 Media Gateway...

  • Page 283: Configuring The G350 Using The Giw

    Wizard (GIW). The GIW is an automated tool that allows you to perform a streamlined installation and configuration of a standalone G350. You can use the GIW to perform initial configuration of the G350 and to upgrade software and firmware. For instructions on accessing the GIW, see Accessing GIW page 30.
  • Page 284 Configuring the G350 using the GIW Click . The COM Port Selection screen appears. Continue Select the COM port on the laptop that you are using the connect to the G350. Click . The G350 Wizard Usage Options screen appears. Continue Select one of the following options: •...
  • Page 285 . For information on the EPW, see Import EPW Installation of the Avaya G350 Media Gateway, 555-245-104. Browse to the EPW file on your laptop. Any values that are included in the EPW will appear as default values from now on as you move through this wizard.
  • Page 286 Click . The IP Addresses screen appears. The IP Addresses screen displays Continue automatically detected information about the G350, such as what media modules are installed in the media modules slots. Click in the Action column. The PMI screen appears. In the PMI screen, specify the details of the Primary Management Interface (PMI) for the G350.
  • Page 287 You can also specify the IP addresses of up to three additional MGCs (optional). For instructions on MGC configuration, see Configuring the Media Gateway Controller (MGC) on page 41. Click Ping Test to test the accessibility of each MGC. Administration of the Avaya G350 Media Gateway June 2004...
  • Page 288 Enter the filename of each firmware upgrade file you want to install in each line of the table where you selected the box. Select Administration of the Avaya G350 Media Gateway June 2004...
  • Page 289 Configuring the G350 using the GIW Click Continue. The firmware is upgraded and the G350 Modem Type Selection screen appears. Select the modem type you want to use. For more information on using a modem with the G350, Configuring the G350 for modem use on page 67.
  • Page 290 Configuring the G350 using the GIW If you selected , enter the required information in the G350 USB Modem USB Modem Configuration screen, then click Continue Click Continue. The Change Root Password screen appears. This screen allows you to change the root password on the G350.
  • Page 291 You have completed the GIW configuration process. Further configuration tasks, as described in this screen, can now be performed either remotely, via a modem that you enabled with GIW, or locally. Administration of the Avaya G350 Media Gateway June 2004...
  • Page 292 Configuring the G350 using the GIW Administration of the Avaya G350 Media Gateway June 2004...
  • Page 293 S8300 Media Server dynamic bandwidth reporting clock GRE tunnels as Codec limitations Command Line Interface overview see CLI Backup service Administration of the Avaya G350 Media Gateway June 2004...
  • Page 294 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 295 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 296 Administration of the Avaya G350 Media Gateway June 2004...
  • Page 297 OSPF mapping Fair VoIP queue Priority FastEthernet interface see Priority DLCI checking status dynamic bandwidth reporting extended keepalive DSCP as policy-based routing rule criteria changing field in GRE header Administration of the Avaya G350 Media Gateway June 2004...
  • Page 298 Ingress Access Control List Generic Routing Encapsulation, see GRE tunneling Ingress QoS List Gigabit Ethernet port Installation location Interfaces port redunancy adjusting bandwidth administrative status accessing applying PBR lists changing password applying policy lists Administration of the Avaya G350 Media Gateway June 2004...
  • Page 299 IP telephones MAC addresses storing in ARP table viewing Map classes applying to all configured Permanent Virtual Keepalive, extended Channels Keepalive, GRE tunnel default number that can be configured parameters Administration of the Avaya G350 Media Gateway June 2004...
  • Page 300 Password Authentication Protocol connecting to console port Passwords connecting to S8300 Media Server changing connecting to USB port changing via GIW connecting via USB modem overview displaying USB modem status recovery password serial Administration of the Avaya G350 Media Gateway June 2004...
  • Page 301 RSTP operations setting priority level policy-based routing, see Policy-based routing QoS lists see USP ports removing policy lists from interface Power over Ethernet rule criteria see PoE rule list Administration of the Avaya G350 Media Gateway June 2004...
  • Page 302 Routing Information Protocol authentication type see RIP compared to OSPF Routing table configuration configuration default metric deleting dynamic entries description deleting static routes distribution access lists Administration of the Avaya G350 Media Gateway June 2004...
  • Page 303 GIW description creating a user discard route creating groups displaying creating remote users dropping packets to creating SNMPv1 community establishing creating users High Preference defining SNMPv1 trap receivers inactive disabling access Administration of the Avaya G350 Media Gateway June 2004...
  • Page 304 G350 via accessing S8300 via enabling and disabling access Temperature VACM Testing LEDs Version management TFTP file transfer via interface static routes Time slots, mapping View-based Access Control Model, see VACM Administration of the Avaya G350 Media Gateway June 2004...
  • Page 305 RSVP protocol Weighted Fair Queuing Voltages VRRP configuration configuration example description backup interfaces checking interface status configuration example dynamic bandwidth reporting extended keepalive features initial configuration interfaces overview testing configuration Administration of the Avaya G350 Media Gateway June 2004...
  • Page 306 Index Administration of the Avaya G350 Media Gateway June 2004...

Table of Contents