|
|
Table Of Contents
SIP Automatic Switchover Using Dual-VLAN
Supported Standards, MIBs, and RFCs
Configuring for the Existing SIP Automatic Switchover Method
Configuring for the SIP Automatic Switchover Using Dual-VLAN Method (Two Virtual Addresses)
Configuring for the SIP Automatic Switchover Using Dual-VLAN Method (One Virtual Address)
Obtaining Technical Assistance
Cisco Technical Support Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
SIP Automatic Switchover Using Dual-VLAN
Document Release History
Feature History
9.4(1)
This feature was introduced on the Cisco Media Gateway Controller (MGC) software.
This document describes the Session Initiated Protocol (SIP) Automatic Switchover Using Dual Virtual Local Access Network (VLAN) feature. This feature is described in the following sections:
•
Supported Standards, MIBs, and RFCs
•
•
•
Feature Overview
The existing automatic switchover methodology for a SIP network depends upon on a SIP element detecting a Cisco MGC automatic switchover due to the absence of any SIP responses from the MGC. The SIP device in question obtains the IP address of the newly active MGC host using a DNS SRV or A-record query, or from the internal cache of a previous query. The SIP Automatic Switchover Using Dual-VLAN feature enables the MGC to use up to two virtual IP addresses for use in SIP networks, one for each VLAN.
In the existing automatic switchover methodology, the active MGC host maintains up to four IP addresses, two on each interface. These are not virtual IP addresses, but the same addresses used in general on the MGC. The MGC monitors the LAN interfaces associated with the IP addresses for a failure (due to physical problem or administrative shut down). If a LAN interface fails, the MGC performs an automatic switchover.
The SIP Automatic Switchover Using Dual-VLAN feature enables you to create a virtual IP address for each LAN interface. If you provision two virtual IP addresses for your LAN interfaces, the active MGC does not perform an automatic switchover when a single LAN interface fails. However, if both LAN interfaces fail, the active MGC does perform an automatic switchover. If you choose to provision only one virtual IP address, the active MGC uses the existing automatic switchover methodology to handle the failure of a single LAN interface.
Note
Benefits
This feature has the following benefit:
Enables the MGC to interwork with a greater range of SIP devices
Using this feature, the MGC can successfully interwork with SIP devices that cannot support four IP addresses for a single device.
Enables faster call setup time after an automatic switchover
Using this feature, the MGC provides a virtual IP address, eliminating the need for an associated SIP element to expend resources storing the last working IP address.
Reduces the need for an associated SIP element to expend resources monitoring for MGC automatic switchover
Using this feature, an associated SIP element only expends resources monitoring for MGC automatic switchover when both LAN interfaces fail.
Restrictions
This feature is not supported for systems in which the active and standby MGC hosts are geographically separated. This feature is only supported for systems in which the active and standby MGC hosts are configured as part of the same set of subnets. Systems that have geographically separated MGC hosts must use the existing methodology, using two IP addresses each for the active and standby MGC hosts .
Related Documents
This document contains information that is related strictly to this feature. The documents that contain additional information related to the Cisco Media Gateway Controller (MGC) are listed below:
•
•
•
•
•
•
•
•
•
•
•
Supported Platforms
The hardware platforms supported for the Cisco MGC software are described in the Release Notes for Cisco Media Gateway Controller Software Release 9.4(1).
Supported Standards, MIBs, and RFCs
This feature supports the following standards, MIBs, and RFCs.
Standards
No standards are supported by this feature.MIBs
No new or modified MIBs are supported by this feature. For more information on the MIBs used in the Cisco MGC software, refer to the Cisco Media Gateway Controller Release 9 MIB Guide.RFCs
No RFCs are supported by this feature.Prerequisites
You must have Cisco Media Gateway Controller (MGC) software Release 9.4(1). Prerequisites for this release can be found in the Release Notes for the Cisco Media Gateway Controller Software Release 9.4(1).
Configuration Tasks
Configuration of the MGC software is typically done when the MGC software is shut down, during a software upgrade, or the initial installation and configuration process. Since the implementation of this feature does not require any unique upgrade tasks, you should refer to the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide for detailed information on the MGC software upgrade and initial installation and configuration processes.
The XECfgParm.dat parameters associated with this feature can be found in the "XECfgParm.dat Parameters" section.
For information on configuring the MGC software to support this feature when your MGC software is already up and running, refer to the "Troubleshooting Tips" section.
Troubleshooting Tips
If SIP automatic switchover is not working properly, you should check the parameter values set in the XECfgParm.dat file to ensure that they are configured correctly. If they are not configured correctly, you must re-configure your MGC software.
Verifying Parameter Settings and Re-configuring MGC Software
To verify your parameter settings and re-configure your MGC software to support the SIP Automatic Switchover Using Dual-VLAN feature, perform the following steps:
Caution
Step 1
cd /opt/CiscoMGC/etcStep 2
Step 3
Note
If the value of the parameter is correct, proceed to Step 4. Otherwise, correct the value of the parameter and then proceed to Step 4.
Step 4
Note
If the value of the parameter is correct, proceed to Step 5. Otherwise, correct the value of the parameter and then proceed to Step 5.
Step 5
If the value of the parameter is correct, proceed to Step 6. Otherwise, correct the value of the parameter and then proceed to Step 7.
Step 6
Step 7
Step 8
/etc/init.d/CiscoMGC stopStep 9
/etc/init.d/CiscoMGC startStep 10
mml>sw-over::confirmSite alarms are automatically set until the out-of-service (OOS) MGC host is returned to an in-service (IS) state.
Step 11
Step 12
Step 13
Provisioning Tasks
This section contains the tasks required to provision this feature. For information on provisioning the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Planning for Provisioning
This section lists the data that you must gather to successfully provision this feature. For more information on planning the provisioning for the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Collecting SIP IP Link Data
This component type represents a link to a SIP device. You must be ready to enter the following data:
•
•
•
•
•
•
•
You can define the parameters for your SIP IP links in Table 1 in the "Provisioning Worksheets" section.
Provisioning Procedures
The provisioning procedures for this feature can be found in the following sections:
•
•
Provisioning Basics
The procedures in this section describe how to start a provisioning session and how to save and activate the changes you have made.
•
•
•
•
For more detailed information about provisioning your Cisco PGW 2200, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Starting a Provisioning Session
You may need to start a provisioning session as part of your system operations. To do this, log into the active Cisco MGC, start an MML session, and enter the following command:
mml>prov-sta::srcver="curr_ver",dstver="mod_ver"Where:
•
Note
–
–
Note
•
For example, to use a configuration version called ver1 as the basis for a version to be called ver2, you would enter the following command:
mml>prov-sta::srcver="ver1",dstver="ver2"Once a provisioning session is underway, you may use the prov-add, prov-ed, or prov-dlt MML commands to add, modify, and delete components on your system. For more information on provisioning other functions on your Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
There are two ways to close your provisioning session: saving and activating your provisioning changes, as described in the "Saving and Activating your Provisioning Changes" section or ending your provisioning session without saving and activating your changes, as described in the "Ending a Provisioning Session Without Activating your Changes" section.
Saving and Activating your Provisioning Changes
When you have completed making provisioning changes in your session, you must enter a command to save and activate your changes. There are two different provisioning MML commands that do this: prov-cpy and prov-dply.
Caution
The prov-cpy MML command is used to save and activate your changes on the active Cisco MGC. This command is typically used to save and activate changes on a Cisco MGC in a simplex configuration. However, you can use the prov-cpy MML command on Cisco MGCs in high-availability or continuous-service configurations, to save and activate your changes on the active Cisco MGC. If you choose to do this, you should enter the prov-sync MML command immediately afterwards, to have your changes saved and activated on the standby Cisco MGC.
Note
Caution
Note
The prov-dply MML command is used to save and activate your changes on the active and standby
Cisco MGCs. This command is typically used to save and activate changes on Cisco MGCs in high-availability or continuous-service configurations. This command should not be used on a Cisco MGC in a simplex configuration.
Note
Ending a Provisioning Session Without Activating your Changes
You may find that you want to end a provisioning session without saving and activating the changes you have entered during your session. If this is the case, you can enter the prov-stp MML command. This command ends your current provisioning session and your changes are not entered.
Retrieving Provisioning Data
You can use the prov-rtrv MML command to retrieve information about your current provisioning settings. The ways in which you can use this command to retrieve provisioning data are described in the following sections:
•
•
•
•
•
Retrieving Data for an Individual Component
You can retrieve provisioning data on any individual component on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml>prov-rtrv:component:name=MML_nameWhere:
•
•
For example, to view the value of a SIP IP link called sip-sigchan, you would enter the following command:
mml>prov-rtrv:siplnk:name="sip-sigchan"Retrieving Data for All Components
You can retrieve data on all of the components provisioned on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml>prov-rtrv:allRetrieving Data for All Components of a Particular Type
You can retrieve provisioning data on all components of a particular type on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml>prov-rtrv:component:"all"Where: component is the MML component type associated with the desired component group. You can find a complete list of MML component types in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
For example, to view the provisioning data for all SS7 signaling services, you would enter the following command:
mml>prov-rtrv:ss7path:"all"Retrieving Data on the Current Provisioning Session
You can retrieve provisioning data on the current provisioning session. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml>prov-rtrv:sessionThe system returns a response similar to the following:
MGC-02 - Media Gateway Controller 2003-01-13 13:39:19M RTRV"session=jtest:session"/*Session ID = mml1SRCVER = activeDSTVER = jtest*/Retrieving Data on Supported Signaling Protocols
You can retrieve protocol data for the current provisioning session. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
mml>prov-rtrv:variantsEnabling SIP Automatic Switchover Using Dual-VLAN
This section contains the procedure that you must perform to add SIP Automatic Switchover Using Dual-VLAN support to your Cisco MGC software provisioning data. b
Note
To provision virtual IP address(es) on your SIP IP links, perform the following steps:
Step 1
Step 2
Step 3
mml>prov-rtrv:siplnk:"all"The system returns a response that lists the settings for all of your provisioned SIP IP links. Take note of the IP adress settings (ipaddr1 and ipaddr2) for each link. Identify the SIP IP links that do not have an IP address setting of Virtual_IP_Addr1.
Step 4
mml>set-iplnk:name:OOSWhere name is the MML name of a SIP IP link provisioned with standard IP addressing. Repeat this step for each affected SIP IP link.
Step 5
mml>prov-dlt:siplnk:name="name"Where name is the MML name of a SIP IP link to be deleted.
Repeat this step for each SIP IP link you need to delete.
Step 6
Step 7
mml>prov-dlt:sippath:name="name"Where name is the MML name of a SIP signaling service to be deleted.
Repeat this step for each SIP signaling service you need to delete.
Step 8
mml>prov-add:sippath:name="name", mdo="ietf_sip"Where name is the MML name of the new SIP signaling service.
For example, to provision a new SIP signaling service called sipsrv1, you would enter the following command:
mml>prov-add:sippath:name="sipsrv1", mdo="ietf_sip"Step 9
mml>prov-add:siplnk:name="name", desc="description", ipaddr="addr", svc="sigsrv", port=pnum, pri=priorityWhere:
•
•
•
–
–
Note
•
•
•
For another example, to provision a SIP IP link that supports a virtual IP address, you would enter the following command:
mml>prov-add:siplnk:name="sip-sigchan1", ipaddr="Virtual_IP_Addr1", svc="sip-sigpath", port=5060, pri=1, desc="SIP sigchan 1"Step 10
Step 11.mml>prov-add:siplnk:name="name", desc="description", ipaddr="addr", svc="sigsrv", port=pnum, pri=priorityWhere:
•
•
•
–
–
Note
•
•
•
Note
For example, to provision a SIP IP link that provides a second virtual IP address, you would enter the following command:
mml>prov-add:siplnk:name="sip-sigchan2", ipaddr="Virtual_IP_Addr2", svc="sip-sigpath", port=5060, pri=2, desc="SIP sigchan 2"Step 11
Step 12
Disabling SIP Automatic Switchover Using Dual-VLAN
This section contains the procedure that you must perform to disable SIP Automatic Switchover Using Dual-VLAN support in your system.
Note
To disable the virtual IP addresses on your SIP IP links, perform the following steps:
Step 1
cd /opt/CiscoMGC/etcStep 2
Step 3
Step 4
Step 5
Step 6
Step 7
/etc/init.d/CiscoMGC stopStep 8
/etc/init.d/CiscoMGC startStep 9
mml>sw-over::confirmSite alarms are automatically set until the out-of-service (OOS) MGC host is returned to an in-service (IS) state.
Step 10
Step 11
mml>set-iplnk:name:OOSWhere name is the MML name of a SIP IP link provisioned with virtual IP addressing. Repeat this step for each affected SIP IP link.
Step 12
Step 13
mml>prov-dlt:siplnk:name="name"Where name is the MML name of a SIP IP link provisioned with virtual IP addressing. Repeat this step for each affected SIP IP link.
Step 14
mml>prov-dlt:sippath:name="name"Where name is the MML name of a SIP signaling service associated with the SIP IP links provisioned with virtual IP addressing.
Step 15
mml>prov-add:sippath:name="name", mdo="ietf_sip"Where:
•
For example, to provision a new SIP signaling service called sipsrv1, you would enter the following command:
mml>prov-ed:sippath:name="sipsrv1", mdo="ietf_sip"Step 16
mml>prov-add:siplnk:name="name", ipaddr="addr", ipaddr="addr"Where:
•
•
–
–
–
–
For example, to enable an IP address on a SIP IP link, you would enter the following command:
mml>prov-add:siplnk:name="sip-sigchan1", ipaddr="IP_Addr1"Repeat this step for each SIP IP link you want provision with standard IP addressing.
Step 17
Troubleshooting Tips
This feature does not work if the virtual address(es) are provisioned on your SIP IP links, but the Virtual_IP_Addr1 and/or Virtual_IP_Addr2 XECfgParm.dat parameters are set to 0.0.0.0. Refer to for the procedure in the "Verifying Parameter Settings and Re-configuring MGC Software" section. For more information on troubleshooting the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
Alarm Troubleshooting Procedure
The alarm listed below is new for this feature. For a complete list of Cisco MGC alarms, refer to the Cisco Media Gateway Controller Software Release 9 System Messages Guide.
SIP Service Fail Over
This alarm is caused by the failure of LAN interfaces, due to either physical failure or administrative shut down.
Corrective Action
To correct the problem identified by this alarm, perform the following steps:
Step 1
If the failure is caused by a physical failure, proceed to Step 2.
If the failure is caused by an administrative shutdown, check for this alarm again once the interface has been restored. If this alarm is still active, proceed to Step 3.
Step 2
Note
If an element of the LAN connection (such as a cable or an Ethernet interface card) is not working properly, replace it. Otherwise, proceed to Step 3.
Note
Step 3
Configuration Examples
This section provides the following examples of configuration for this feature. Additional examples of provisioning for the Cisco MGC software can be found in the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide.
Configuring for the Existing SIP Automatic Switchover Method
The example below illustrates the XECfgParm.dat settings required to configure your MGC to use the existing SIP automatic switchover method. The value of the sipFailover parameter does not have any effect since both virtual IP addresses are set to zero.
*.IP_Addr1 = 172.22.119.5*.IP_Addr2 = 172.22.118.5...*.Virtual_IP_Addr1 = 0.0.0.0*.Virtual_IP_Addr2 = 0.0.0.0Configuring for the SIP Automatic Switchover Using Dual-VLAN Method (Two Virtual Addresses)
The example below illustrates the XECfgParm.dat settings required to configure your MGC to use the SIP automatic switchover using dual-VLAN method with two virtual addresses. The value of the sipFailover parameter does not have any affect since both virtual IP addresses are being used for SIP service.
*.IP_Addr1 = 172.22.119.5*.IP_Addr2 = 172.22.118.5...*.Virtual_IP_Addr1 = 172.22.119.7*.Virtual_IP_Addr2 = 172.22.118.7Configuring for the SIP Automatic Switchover Using Dual-VLAN Method (One Virtual Address)
The example below illustrates the XECfgParm.dat settings required to configure your MGC to use the SIP automatic switchover using dual-VLAN method with one virtual IP address.
*.IP_Addr1 = 172.22.119.5*.IP_Addr2 = 172.22.118.5...*.Virtual_IP_Addr1 = 172.22.119.7*.Virtual_IP_Addr2 = 0.0.0.0*.sipFailover = trueYou can also use the second virtual IP address, as shown below.
*.IP_Addr1 = 172.22.119.5*.IP_Addr2 = 172.22.118.5...*.Virtual_IP_Addr1 = 0.0.0.0*.Virtual_IP_Addr2 = 172.22.118.7.*.sipFailover = true
Note
Provisioning Examples
This section provides the following examples of provisioning for this feature. Additional examples of provisioning for the Cisco MGC software can be found in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
set-iplnk:sip-sigchan1:OOSset-iplnk:sip-sigchan2:OOSprov-dlt:siplnk:name="sip-sigchan1"prov-dlt:siplnk:name="sip-sigchan2"prov-dlt:sippath:name="sip-sigpath"prov-add:sippath:name="sip-sigpath", mdo="ietf_sip"prov-add:siplnk:name="sip-sigchan1", ipaddr="Virtual_IP_Addr1", svc="sip-sigpath", port=5060, pri=1, desc="SIP sigchan"prov-add:siplnk:name="sip-sigchan2", ipaddr="Virtual_IP_Addr2", svc="sip-sigpath", port=5060, pri=2, desc="SIP sigchan"Reference Information
The following sections contain reference material related to this feature. Information is included on the following areas:
•
XECfgParm.dat Parameters
The XECfgParm.dat file configuration parameters used for this feature are in the table below.
Alarms
This section lists the alarms that are added and modified to support this feature. For information on the other alarms for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Messages Reference Guide.
SIP Service Fail Over
Description Virtual addresses for the MGC cannot be reached due to failure of the associated LAN interfaces. This alarm is cleared automatically when the LAN interface(s) are ready for traffic again.
Severity Critical
Cause This alarm is caused by the failure of LAN interfaces, due to either physical failure or administrative shut down.
Type 1 (Communication error).
Action Refer to the "SIP Service Fail Over" section.
Provisioning Worksheets
The tables in this section are for planning your provisioning data, specific to this feature. For worksheets covering the rest of the provisioning components in the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
Documentation Feedback
You can send comments about technical documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.
Cisco Technical Support Website
The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/go/marketplace/
•
http://cisco.com/univercd/cc/td/doc/pcat/
•
•
•
http://www.cisco.com/go/iqmagazine
•
•
http://www.cisco.com/en/US/learning/index.html
Glossary
Table 2 contains definitions of acronyms and technical terms used in this feature module.
Posted: Mon Mar 12 16:47:22 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
