Application Notes - Avaya



| |

G700 vs. G350 Comparison Application Note - Issue 1.0

Abstract

| |

|With the introduction of the new Avaya G350 Media Gateway with Avaya Communication Manager Release 2.0, it is necessary for us to clearly |

|understand the architectural differences as well as the command-line interface differences between the G700 Media Gateway and the G350 |

|Media Gateway. This application note is intended to address this issue to allow a smooth implementation of the G350. |

Table of Contents

1. Introduction 3

2. G350 Media Gateway 3

3. Targeted Audience 3

4. Acronyms 3

5. Equipment & Software Validated 4

6. Versions of this document 4

7. Key architectural differences between a G700 & G350 Media Gateway 4

8. Overview of configuring a G700 vs. G350 Media Gateway 7

9. Registering the Gateway to the Call Server 12

10. Conclusion 13

11. Acknowledgements 13

12. Appendix A: High-level Block Diagram of the G700 14

13. Appendix B: High-level Block Diagram of the G350 15

14. Appendix C: Factory Default “running” configuration 16

15. Appendix D : Basic “running” configuration with PMI configured 17

16. Index 18

Introduction

With the introduction of the new Avaya G350 Media Gateway with Avaya Communication Manager Release 2.0, it is necessary for us to clearly understand the architectural differences as well as the command-line interface differences between the G700 Media Gateway and the G350 Media Gateway. This application note is intended to address this issue to allow a smooth implementation of the G350.

This document contains the following key information:

❑ Highlights of the key architectural differences between the G700 and the G350

❑ Highlights of the differences in the set of commands used to configure a G350 vs. a G700

❑ High-level block diagrams of the G700 and the G350

❑ A copy of the “factory default” configuration from a G350

❑ A copy of the “basic running configuration” with the Primary Management Interface (PMI) configured for a G350

This document is not intended to replace the installation or operating documents for the G350 Media Gateway or any other equipment.

G350 Media Gateway

The G350 Media Gateway is a unified media-gateway, LAN with power-over-Ethernet switching, and WAN access solution for small branch-offices. The G350 offers seamless integration with Communication Manager. The G350 is 19-inch rack mountable, is 3u (133.3mm) high and can fit into a 480mm deep wiring closet. The G350 can be used in a stand-alone configuration, as a media gateway or as a survivable media gateway. A picture of the basic G350 Media Gateway is shown below:

[pic]

Targeted Audience

The targeted audience for this document is Tier 4, Tier 3, Tier 2, System Technicians, Business Partners and Software Specialists.

Acronyms

|Acronym |Meaning |

|CLI |command-line interface |

|CPU |central processing unit |

|DCP |digital communication protocol |

|FTP |file transfer protocol |

|FX0 |foreign-exchange office |

|FXS |foreign-exchange station |

|FW |firmware |

|ICC |internal call controller |

|LSP |local survivable processor |

|MGC |media gateway controller |

|MGP |media gateway processor |

|MM |media module |

|OSPF |open shortest path first |

|PMI |Primary Management Interface |

|PoE |power over ethernet |

|PPP |point-to-point protocol |

|RIP |routing information protocol |

|SNMP |simple network management protocol |

|TFTP |trivial file transfer protocol |

|USB |universal serial bus |

|VLAN |virtual local area network |

|VoIP |voice over IP processor |

|WAN |wide-area network |

Equipment and Software Validated

The following equipment and software are used for the sample configuration provided in this document:

|Equipment |Software |

|Avaya S8300 Media Server |Communication Manager 2.0 load |

| |218.2 |

|Avaya G350 Media Gateway |V21.16.1 |

|Avaya G700 Media Gateway |V21.14 |

|DCP MM712 |HW 3 FW 5 |

|DCP MM312 |HW 1 FW 1 |

|E1T1 MM710 |HW2 FW8 |

|Analog (on-board) Slot V7 |HW 0 FW 55 |

Versions of this document

|Version |Description of Changes |

|1.0 |Initial document |

Key architectural differences between a G700 Media Gateway and a G350 Media Gateway

The following are key differences between the G700 Media Gateway and the G350 Media Gateway:

❑ The G350 CANNOT be installed in a stack configuration.

❑ The effect of most commands in the G350 can be reversed (to default) by using the “no” prefix (Example: ip address has the corresponding negated command no ip address which will set the IP address of the particular interface to the factory defaults).

❑ With the G350, there is the concept of an “interface” or a “context”. Commands are typically executed within an interface or a context. The CLI prompt for the G350 changes based on the context or interface you are in. By default, you are in a “global” context (i.e., when you first login). Example contexts: interface Console, interface loopback, interface VLAN, Controller, Router OSPF, Router RIP, etc.

❑ The Primary Management Interface (PMI) is associated with the first VLAN established by entering the VLAN context i.e., “interface vlan 1”. The PMI is the IP address used by G350 as a source address for sending packets and as its media-gateway address. The PMI is automatically set to the first defined IP interface. Being a router, the G350 can have many IP interfaces with different addresses. The PMI can be moved to any valid VLAN configured within the G350.

❑ The G350 includes a serial (console) port as well as a USB port. In its initial, the G350 will be modem accessible by using a MultiTech serial modem plugged into the console (serial) port. In a future release of the G350 firmware, the USB port on the G350 will be activated, and, a USB modem could be (preferably) used to access the G350. The modem of choice in the future release will be a MultiTech USB modem over a MultiTech serial Modem. Note that neither a serial nor a USB modem access is provided directly to the G700 Media Gateway.

❑ The G350 involves a concept of a “startup” configuration as well as a “running” configuration. To save any changes you make in a session, run the command copy running-config startup-config commonly abbreviated as copy run start in the global context as shown below. NOTE: If you do not run the copy run start command, all the changes you made to an interface will be lost following a G350 reset or power failure!!

❑ VoIP resources available on the G350 motherboard are restricted to 32 G.711 resources or 16 G.729 resources. If media encryption is being used, the VoIP resources are reduced to 24 G.711 and 12 G.729 resources respectively. The VoIP processor on the G350 does not need a separate firmware image – the G350 firmware image itself includes the VoIP processor firmware. Also, note that the MM760 media module CANNOT be used or provisioned as an external VoIP resource to be used in the G350.

❑ The G350 has only one CLI vs. the G700 that has at least the following CLIs: P330 or Cajun CLI, G700 (a.k.a MGP) CLI, and the VoIP Processor CLI that is primarily used for debugging purposes only.

❑ For the basic configuration of a G700 vs. a G350, the minimum number of IP addresses needed is three for the G700 and only one for the G350 PMI.

❑ The G700 has an optional X330 WAN module available that provides PPP or Frame Relay connections to a remote location. In contrast, the G350 has native routing capability and also provides 2 new media modules that provide that functionality. Note: This document does not cover WAN port configuration for the G350.

❑ The G350 has Analog FXO and FXS ports that are integrated into the G350 chassis to provide Emergency Transfer in power failure conditions, and, when the G350 is not registered to a call controller (LSP or Main controller). These ports are located in the bottom left of the front panel of the G350 chassis and are together labeled as V7. Note: This V7 analog media module is comprised of 3 ports. Port 1 is the FXO trunk port and port 2 and 3 are the FXS station ports. V7 requires firmware upgrades similar to the other analog media modules (but uses a different firmware file from Analog Media Module - MM711). As you can see in the show mg list_config output below, the V7 slot on this particular G350 is running FW vintage 55.

❑ On a basic G350 (i.e., without any other media modules installed), you need at least three firmware files to upgrade the G350:

o The g350_sw_XX_YY_0.bin applies to the VoIP processor, P330 equivalent component, X330 WAN equivalent component and the MGP/G700 equivalent component of the G350. (The mgp_XX_YY_ZZ_ZZ.bin file only applies to the G700, and not used for the G350.)

o For the Analog FXS, FXO ports (i.e., module V7) you need the mmanalogvXX.fdl firmware.

o The g350_emweb_XX_Y_ZZ.bin applies to the device manager on the G350.

(Note: “XX”, “YY”, “ZZ” above are random strings representing the numbers for a current firmware version. The same strings that are used for representation across these firmware files should not imply that these files have the same numbers)

❑ The G350 brings to market two new types of high-density media modules: 24-port PoE and 24-port DCP.

|MG-002-1(super)# show mg list_config |G700: The G700 configuration |

|SLOT TYPE CODE SUFFIX HW VINTAGE FW VINTAGE VOIP FW |shown has no media modules |

|---- ------ ----- ------ ---------- ----------- ------- |installed. |

|v0 G700 DAF1 A 00 20.16.0(A) 18 | |

|v1 ICC S8300 A 3 6 N/A | |

|v2 -- Not Installed -- | |

|v3 -- Not Installed -- | |

|v4 -- Not Installed -- | |

|G350-004(super)# show mg list_config |G350: The G350 configuration |

|SLOT TYPE CODE SUFFIX HW VINTAGE FW VINTAGE |shown has 3 media modules |

|---- ------ ---------- ------ ---------- ----------- |installed: an MM710 E1T1(v2), |

|v0 G350 PC1053 B 0 21.16.1(B) |MM712 DCP(v5) and a HDMM MM312 |

|v1 ICC S8300 A 0 6 |DCP(v6) plus the V7 integrated |

|v2 -- Not Installed -- |analog FXO/FXS ports. |

|v3 E1T1 MM710 A 2 8 | |

|v4 -- Not Installed -- | |

|v5 DCP MM712 A 3 5 | |

|v6 DCP MM312 A 1 1 | |

|v7 Analog (on-board) A 0 55 | |

❑ The following shows the differences in the output of the “show mg list-config” between a G350 and a G700:

Overview of configuring a G700 Media Gateway vs. a G350 Media Gateway

|  | Shading indicates not applicable to the | | |

| |G350. | | |

|Note: Always use the Arrow keys on your keyboard to invoke the previous commands executed on your G700/G350 Media Gateway CLI. |

|Steps |G700/MGP |G350 |Comments |

|1 |Login: root |Login: root |  |

| |Password: root |Password: root | |

|2 |Type P330-1(super)# nvram init |Type G350-???(super)# nvram init |G350 : A copy of the factory default |

| |This will restore the G700 settings to |This will restore the G700 settings to factory|configuration is provided for |

| |factory default settings. |default settings. Note: With the G350, you |reference in Appendix C of this |

| | |have the option of using the “erase |document. |

| | |startup-config” command. | |

|3 |Type in the following commands at the prompt:|Type in the following commands at the prompt: |G350 : *** By default the first |

| | |G350-???(super)# interface vlan 1 |assigned IP address becomes the |

| |P330-1(super)# configure |G350-???(super-if:Vlan 1)# ip address |The G350 does not require "configure."|

| | | | |

| | | | |

| | | |G700: The configure command is a |

| | | |commonly omitted CLI command error for|

| | | |G700 (as per usability test results of|

| | | |Communication Manager 1.3 |

| | | |installations). |

|4 |P330-1(configure)# reset |Not Applicable |  |

| |Select Yes | | |

|5 |Not Applicable |G350-???(super-if:Vlan 1)# exit |G700: There is no concept of context |

| | |This will exit from the VLAN context. |in G700. |

|6 |Not Applicable |G350-???(super)# copy running-config |G350: copy run start is one of the |

| | |startup-config |most important commands and should to |

| | |G350-???(super)# reset |be used regularly during configuration|

| | | |of the G350. Any configuration changes|

| | | |that you make will not be saved until |

| | | |you enter this command. |

|7 |Once the G700 reboot has completed, log back |Once the G350 reboot has completed, log back |  |

| |in. Type in the following commands at the |in. (By default you are in “global” mode.) | |

| |prompt: | | |

| |P330-1(super)# configure | | |

|8 |P330-1(configure)# show interface |G350-???(super)# show interface |G350: This command will display which |

| | | |interface has been assigned as the PMI|

| | | |in the output and various protocol |

| | | |statistics. Alternatively, there is a |

| | | |show PMI command to show the PMI’s |

| | | |configured IP address. |

|9 |P330-1(configure)# set ip route 0.0.0.0 |G350-???(super)# ip default-gateway | |

|10 |P330-1(configure)# show ip route |G350-???(super)# show ip route |  |

|11 |P330-1(configure)# session mgp |Not Applicable |  |

|12 |MG-???-n (super)# configure |Not Applicable |  |

| |MG-???-n (configure)# | | |

|13 |MG-???-n (configure)# set interface mgp |Not Applicable |G350: There is only one CPU in the |

| | | |G350 and therefore only one management|

| | | |interface or PMI. |

|14 |MG-???-n (configure)# reset mgp |Not Applicable |  |

| |Select Yes | | |

|15 |Once the MGP reboot has completed log back |Not Applicable |  |

| |in. P330-1(configure)# | | |

| |session mgp | | |

|16 |MG-???-n (super)# configure |Not Applicable |G700: show interface mgp will only |

| |MG-???-n (configure)# show interface | |show the IP address of the MGP. show |

| |[[mgp][voip]] | |interface voip shows the IP address of|

| | | |the VoIP processor. |

|17 |MG-???-n (configure)# set ip route | | |

|18 |MG-???-n (configure)# show ip route mgp |Not Applicable |  |

|19 |MG-???-n (configure)# set interface voip |Not Applicable |G350: For the G350, VoIP interface IP |

| | | |address is automatically set to PMI IP|

| | | |address; there is no separate IP |

| | | |address needed for the VoIP in the |

| | | |G350. |

|20 |MG-???-n (configure)# show voip |Not Applicable |  |

|21 |MG-???-n (configure)# set mgc list , , … | |

|22 |MG-???-n (configure)# show mgc list |G350-???(super)# show mgc list | |

|23 |MG-???-n (configure)# set snmp trap enable | |argument for adding a NEW entry. |

|24 |MG-???-n (configure)# show snmp |G350-???(super)# show snmp | |

|25 |MG-???-n (configure)# set mgp icc-monitoring |G350-???(super)# set icc-monitoring |G350: The G350 version of the command |

| |enable | |does not have the “mgp” or “enable” |

| | | |keywords. |

|26 |Not Applicable |G350-???(super)# copy running-config |  |

| | |startup-config | |

| 27 |MG-???-n (configure)# show mgp bootimage |G350-???(super)# show boot bank |G700 & G350 : Identifies the current |

| | | |software bank from which the gateway |

| | | |has booted. |

|28 |MG-???-n (configure)# copy tftp mgp-image a |G350-???(super)# copy tftp SW_imageA |G700/G350: The copy ftp/tftp … |

| | | |commands are non-blocking! Once you |

| | |G350-???(super)# copy ftp SW_imageA |execute the command, you are returned |

| | | |to the command prompt immediately, |

| | | |while the command is executing in the |

| | | |background. Use the show download |

| | |(Note: Repeat this command for memory bank B |software status … command to check |

| |(Note: Repeat this command for memory bank B |(i.e., SW_imageB) as applicable). |progress of the copy command. |

| |as applicable). | |G700: The G700 does not have the |

| | |(Note: If the S8300 is being used as the FTP |functionality to use an FTP server to |

| | |server, the firmware files need to in the |serve out the firmware. |

| | |/var/home/ftp/pub directory. |G350: The firmware update procedure |

| | |The path to the firmware needs to be preceded |can be done utilizing a TFTP or FTP |

| | |by the directory pub/ so |server in the G350. |

| | |the ftp server can find the file to be |G350: The command in italics is the |

| | |downloaded). |FTP version of the command. If an FTP |

| | | |is being used, the G350 CLI will ask |

| | |G350-???(super)# show download software |you for the login and password of the |

| | |status 10 |FTP server before performing the |

| | | |operation. |

| | | |  |

| | | |G350: The G700 provides a real time |

| | | |output of the download status of the |

| | | |target image and the G350 does not. To|

| | | |identify the current status of the |

| | | |download, you have to repeatedly issue|

| | | |the command of show download software |

| | | |status 10 The 10 here indicates the |

| | | |object being upgraded which in this |

| | | |case is the G350 motherboard. Note: |

| | | |You can also use the Arrow keys on |

| | | |your keyboard to invoke the executed |

| | | |command repeatedly. |

|29 | | |G700: is the name of the |

| |MG-???-n (configure)# set mgp bootimage |G350-???(super)# set boot bank |bank that will become active after a |

| | | |reset – ‘a’ or ‘b’ |

| | | | |

| | | |G350 : is the name of the |

| | | |bank that will become active after a |

| | | |reset – ‘bank-a’ or ‘bank-b’ |

|30 |MG-???-n (configure)# copy tftp mm-image v0 |G350-???(super)# copy tftp module |G700/G350: The copy ftp/tftp … |

| | | |commands are non-blocking! Once you |

| | | |execute the command, you are returned |

| | |G350-???(super)# copy ftp module |to the command prompt immediately, |

| | | |while the command is executing in the |

| | | |background. Use the show download |

| | | |software status … command to check |

| | |G350-???(super)# show download software status|progress of the copy command. |

| | |4 |G700: The G700 does not have the |

| | | |functionality to use an FTP server to |

| | | |serve out the firmware. In the example|

| | | |shown, “v0” indicates the media module|

| | | |being upgraded. |

| | | |G350:The firmware update procedure can|

| | | |be done utilizing a TFTP or FTP |

| | | |server in the G350. |

| | | |G350: The command in italics is the |

| | | |FTP version of the command. If an FTP |

| | | |is being used the G350 CLI will ask |

| | | |you for the login and password of the |

| | | |FTP server before performing the |

| | | |operation. |

| | | |G350: The G700 provides a real time |

| | | |output of the download status of the |

| | | |target image and the G350 does not. To|

| | | |identify the stage the download is in |

| | | |you have to repeatedly issue the |

| | | |command of show download software |

| | | |status 4. The “4” here indicates the |

| | | |object being upgraded which in this |

| | | |case is the G350 media module in Slot |

| | | |V4. |

| | | |(G350: If the S8300 is being used as |

| | | |the FTP server the firmware files need|

| | | |to in the /var/home/ftp/pub directory.|

| | | |The path to the firmware needs to be |

| | | |preceded by the directory |

| | | |pub/ so the ftp |

| | | |server can find the file to be |

| | | |downloaded). |

| | | |(G350:The Analog FXO & FXS ports would|

| | | |need to be upgraded along with the |

| | | |other components in a G350 identified |

| | | |as “V7”. The firmware version can be |

| | | |identified by issuing the dir command |

| | | |or show mg list config command from |

| | | |the global context on the G350 CLI). |

|31 |MG-???-n (configure)# show system |G350-???(super)# show system |Note: See Section 9 of this document |

| | | |for details. |

Registering the Gateway to the Media Server

|Before a media gateway can be used for IP telephony, it needs to be registered to a media server. To do this, you need the serial number for |

|the G700 and G350 Media Gateway CLI. |

|MG-???-1(super)# show system |Note: The “Serial No” must be populated in the “change media-gateway” |

| |form on the SAT (of the media server). Record the serial number |

|Uptime(d,h:m:s): 5, 02:41:27 |exactly as is. Also notice that the “???” exactly as is. Also notice |

| |that the “???” at the CLI prompt means that the media gateway is |

|System Name : -- Empty -- |currently NOT registered. This “???” string will change to a number |

|System Location: -- Empty -- |formatted as “00X” (X>=1 and X=1 and X ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download