Administration of the Avaya G350 Media Gateway - Avaya Support
Administration of the Avaya G350 Media Gateway - Avaya Support Administration of the Avaya G350 Media Gateway - Avaya Support
Basic device configurationSetting reset timesIf the connection between the G350 and its registered MGC is lost, the G350 attempts torecover the connection. Use the set reset-times primary-search command and theset reset-times total-search command to set the time-out for the G350’s search forthe primary MGC and the other MGC’s on its MGC list, respectively. Use the setreset-times transition-point command to configure the point at which the primaryMGCs in the list end and the LSPs begin. For example, if there are three IP addresses in theMGC list and the third address is the LSP, the transition point should be 2.The default time for the primary search is 1 minute. The default time for the total search is 30minutes. The default transition point is 1.For example:G350-001> set reset-times primary-search 20G350-001> set reset-times total-search 40350-001> set reset-times transition-point 1In this example, in the event of a loss of connection with the registered MGC, the G350searches for the primary MGC on its MGC list for 20 minutes. If the G350 does not establish aconnection with the primary MGC within this time, it searches for the other MGCs on the list fora total of 40 minutes.Use the show recovery command to show the status of MGC and ICC monitoring andrecovery setup.Accessing the registered MGCTo access the G350’s registered MGC through the G350:●●If the MGC is an S8300 media server, use the session mgc commandIf the MGC is an S8500 or S8700 media server, use the set mediaserver command tomanually define the MGC’s IP address, then use the session mgc command to accessthe MGCIf the G350 includes an S8300, use the session icc command to access the S8300. Youcan use this command whether or not the local S8300 is the G350’s registered MGC.Note:Note:Both the session mgc command and the session icc command open atelnet connection to the MGC.To open a connection directly to the Avaya Communication Manager System Access Terminal(SAT) application in the MGC, add sat to the command. For example:G350-001> session mgc sat54 Administration of the Avaya G350 Media Gateway
Viewing the status of the deviceTo open a connection to the MGC’s LINUX operating system, do not add sat to the command.For example:G350-001> session mgcMonitoring the ICC or LSPWhen an MGC controls telephone services on the Avaya G350 Media Gateway in ICC or LSPmode, 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:●●Use the set icc-monitoring command to control heartbeat monitoring of an ICC orLSP. The enable parameter enables heartbeat monitoring. The disable parameterdisables heartbeat monitoring.Use the show icc-monitoring command to display the status of the ICC/LSPmonitoring process.Viewing the status of the deviceTo view the status of the Avaya G350 Media Gateway, use the following commands. For moreinformation about these commands, see Avaya G350 Media Gateway CLI Reference,555-245-202.●●●Use the show faults command to view information about currently active faults.Use the show mgc command to view information about the Media Gateway Controller withwhich the G350 is registered. For more information, see Configuring the Media GatewayController (MGC) on page 51.Use the show mm command to view information about media modules that are installed onthe G350. To view information about a specific media module, include the slot number ofthe media module as an argument. For example, to view information about the mediamodule in slot 2, enter show mm v2. The output of the command shows the followinginformation:- Slot number- Uptime- Type of media module- Description- Serial number and other hardware identification numbers- Firmware version- Number of ports- Fault messagesIssue 3 January 2005 55
- Page 3 and 4: Electromagnetic Compatibility (EMC)
- Page 5: ContentsAbout this Book . . . . . .
- Page 8 and 9: ContentsConfiguring PPP . . . . . .
- Page 10 and 11: ContentsPort classification . . . .
- Page 12 and 13: ContentsConfiguring VRRP . . . . .
- Page 14 and 15: ContentsChapter 19: Configuring pol
- Page 16 and 17: Contents16 Administration of the Av
- Page 18 and 19: About this Book4. Scroll down to fi
- Page 20 and 21: About this BookSending us commentsA
- Page 22 and 23: Introduction●●●●●●●
- Page 24 and 25: Configuration overviewIf you intend
- Page 26 and 27: Configuration overviewSaving config
- Page 28 and 29: Accessing the Avaya G350 Media Gate
- Page 30 and 31: Accessing the Avaya G350 Media Gate
- Page 32 and 33: Accessing the Avaya G350 Media Gate
- Page 34 and 35: Accessing the Avaya G350 Media Gate
- Page 36 and 37: Accessing the Avaya G350 Media Gate
- Page 38 and 39: Accessing the Avaya G350 Media Gate
- Page 40 and 41: Accessing the Avaya G350 Media Gate
- Page 42 and 43: Accessing the Avaya G350 Media Gate
- Page 44 and 45: Accessing the Avaya G350 Media Gate
- Page 46 and 47: Accessing the Avaya G350 Media Gate
- Page 48 and 49: Accessing the Avaya G350 Media Gate
- Page 50 and 51: Basic device configurationConfiguri
- Page 52 and 53: Basic device configurationThe Media
- Page 56 and 57: Basic device configuration●●●
- Page 58 and 59: Basic device configurationEach firm
- Page 60 and 61: Basic device configurationThe follo
- Page 62 and 63: Configuring Ethernet portsConfiguri
- Page 64 and 65: Configuring Ethernet portsWAN Ether
- Page 66 and 67: Configuring loggingSyslog serverA S
- Page 68 and 69: Configuring loggingFilters and seve
- Page 70 and 71: Configuring loggingTable 5: Logging
- Page 72 and 73: Configuring VoIP QoSConfiguring RTP
- Page 74 and 75: Configuring VoIP QoSConfiguring QoS
- Page 76 and 77: Configuring VoIP QoSConfiguring Wei
- Page 78 and 79: Configuring the G350 for modem useN
- Page 80 and 81: Configuring the G350 for modem use8
- Page 82 and 83: Configuring a WAN Interface●●
- Page 84 and 85: Configuring a WAN InterfaceFigure 3
- Page 86 and 87: Configuring a WAN Interface3. Use t
- Page 88 and 89: Configuring a WAN InterfaceE1/T1 de
- Page 90 and 91: Configuring a WAN InterfaceUSP defa
- Page 92 and 93: Configuring a WAN InterfaceFigure 5
- Page 94 and 95: Configuring a WAN Interfacetrying t
- Page 96 and 97: Configuring a WAN Interface8. Use t
- Page 98 and 99: Configuring a WAN InterfaceConfigur
- Page 100 and 101: Configuring a WAN InterfaceFigure 6
- Page 102 and 103: Configuring a WAN InterfaceNote:Not
Viewing <strong>the</strong> status <strong>of</strong> <strong>the</strong> deviceTo open a connection to <strong>the</strong> MGC’s LINUX operating system, do not add sat to <strong>the</strong> command.For example:<strong>G350</strong>-001> session mgcMonitoring <strong>the</strong> ICC or LSPWhen an MGC controls telephone services on <strong>the</strong> <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong> in ICC or LSPmode, <strong>the</strong> <strong>G350</strong> monitors <strong>the</strong> connection with <strong>the</strong> MGC. If <strong>the</strong> connection with <strong>the</strong> MGC is lost,<strong>the</strong> <strong>G350</strong> starts a recovery process. Use <strong>the</strong> following commands to configure MGC monitoring:●●Use <strong>the</strong> set icc-monitoring command to control heartbeat monitoring <strong>of</strong> an ICC orLSP. The enable parameter enables heartbeat monitoring. The disable parameterdisables heartbeat monitoring.Use <strong>the</strong> show icc-monitoring command to display <strong>the</strong> status <strong>of</strong> <strong>the</strong> ICC/LSPmonitoring process.Viewing <strong>the</strong> status <strong>of</strong> <strong>the</strong> deviceTo view <strong>the</strong> status <strong>of</strong> <strong>the</strong> <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong>, use <strong>the</strong> following commands. For moreinformation about <strong>the</strong>se commands, see <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong> CLI Reference,555-245-202.●●●Use <strong>the</strong> show faults command to view information about currently active faults.Use <strong>the</strong> show mgc command to view information about <strong>the</strong> <strong>Media</strong> <strong>Gateway</strong> Controller withwhich <strong>the</strong> <strong>G350</strong> is registered. For more information, see Configuring <strong>the</strong> <strong>Media</strong> <strong>Gateway</strong>Controller (MGC) on page 51.Use <strong>the</strong> show mm command to view information about media modules that are installed on<strong>the</strong> <strong>G350</strong>. To view information about a specific media module, include <strong>the</strong> slot number <strong>of</strong><strong>the</strong> media module as an argument. For example, to view information about <strong>the</strong> mediamodule in slot 2, enter show mm v2. The output <strong>of</strong> <strong>the</strong> command shows <strong>the</strong> followinginformation:- Slot number- Uptime- Type <strong>of</strong> media module- Description- Serial number and o<strong>the</strong>r hardware identification numbers- Firmware version- Number <strong>of</strong> ports- Fault messagesIssue 3 January 2005 55