SIP Automatic Switchover Using Dual-VLAN
Document Release History
Publication Date
Comments
September 15, 2003
Initial version of the document.
December 5, 2003
Corrected the MML command information for SIP links, due to a change
in command syntax.
May 17, 2005
Corrected the priority information for the provisioning of a second SIP IP
link.
Feature History
Release
Modification
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:
•
Feature Overview, page 2
•
Supported Platforms, page 3
•
Supported Standards, MIBs, and RFCs, page 3
•
Prerequisites, page 3
•
Provisioning Tasks, page 5
•
Configuration Examples, page 15
•
Provisioning Examples, page 16
•
Reference Information, page 16
•
Glossary, page 18
•
Obtaining Documentation and Submitting a Service Request, page 19
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
SIP Automatic Switchover Using Dual-VLAN
Feature Overview
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
The existing automatic switchover functionality is still supported.
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.
SIP Automatic Switchover Using Dual-VLAN
2
SIP Automatic Switchover Using Dual-VLAN
Supported Platforms
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:
•
Release notes for Cisco Media Gateway Controller Software Release 9.4(1)
•
Cisco Media Gateway Controller Hardware Installation Guide
•
Regulatory Compliance and Safety Information for the Cisco Media Gateway Controller
•
Cisco Media Gateway Controller Software Release 9Installation and Configuration Guide
•
Cisco Media Gateway Controller Software Release 9 Provisioning Guide
•
Cisco Media Gateway Controller Software Release 9 Dial Plan Guide
•
Cisco Media Gateway Controller Software Release 9 MML Command Reference Guide
•
Cisco Media Gateway Controller Software Release 9 Messages Reference Guide
•
Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
•
Cisco Media Gateway Controller Software Release 9 MIB Guide
•
Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and
Troubleshooting Guide
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).
SIP Automatic Switchover Using Dual-VLAN
3
SIP Automatic Switchover Using Dual-VLAN
Configuration Tasks
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 on page 17.
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 on page 4.
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
Re-configuration of the MGC software requires that the system software be shut down. In a simplex
system, calls cannot be processed during system shutdown. In a continuous service system, your system
loses the ability to maintain calls during a critical event if the system software on one of the MGC hosts
is shut down.
Step 1
Log in to the standby Cisco MGC as root and change directories to the etc subdirectory by entering the
following UNIX command:
cd /opt/CiscoMGC/etc
Step 2
Open the XECfgParm.dat using a text editor, such as vi.
Step 3
Search for the *.Virtual_IP_Addr1 parameter and ensure that the current setting is a virtual address
within the subnet of the IP address defined in the IP_Addr1 parameter.
Note
The IP address should be expressed in dotted decimal notation (for example, 10.25.81.5).
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
If you have not configured a second virtual IP address, proceed to Step 6. Otherwise, search for the
*.Virtual_IP_Addr2 parameter and ensure that the current setting is a virtual address within the subnet
of the IP address defined in the IP_Addr2 parameter.
Note
The IP address should be expressed in dotted decimal notation (for example, 10.25.81.5).
SIP Automatic Switchover Using Dual-VLAN
4
SIP Automatic Switchover Using Dual-VLAN
Provisioning Tasks
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
Search for the *.sipFailover parameter and ensure that the current setting is true.
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
If you have made any changes to the parameter values, proceed to Step 7. Otherwise, close the text editor
and proceed to Step 10.
Step 7
Save your changes and close the text editor.
Step 8
Manually stop the MGC software on the standby MGC by entering the following UNIX command:
/etc/init.d/CiscoMGC stop
Step 9
Once the software shutdown is complete, manually start the MGC software on the standby MGC by
entering the following command:
/etc/init.d/CiscoMGC start
Step 10
Log in to the active MGC, start an MML session, and enter the following command:
mml>sw-over::confirm
Site alarms are automatically set until the out-of-service (OOS) MGC host is returned to an in-service
(IS) state.
Step 11
Repeat steps 1 through 5 for the newly standby MGC host.
Step 12
If you have not made any changes to the parameter values, proceed to Step 13. If you have made any
changes to the parameter values, repeat steps 7 through 10. Once you have completed step 10, the
procedure is complete.
Step 13
Contact the Cisco Technical Assistance Center (TAC) for assistance in resolving this problem.
Information on contacting the Cisco TAC can be found in the “Obtaining Documentation” section on
page 18.
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:
•
MML name
SIP Automatic Switchover Using Dual-VLAN
5
SIP Automatic Switchover Using Dual-VLAN
Provisioning Tasks
•
Component description
•
Port
•
Priority
•
Virtual IP address 1
•
Virtual IP address 2 (optional)
•
Associated SIP signaling service
You can define the parameters for your SIP IP links in Table 1 in the “Provisioning Worksheets” section
on page 18.
Provisioning Procedures
The provisioning procedures for this feature can be found in the following sections:
•
Provisioning Basics, page 6
•
Enabling SIP Automatic Switchover Using Dual-VLAN, page 9
•
Disabling SIP Automatic Switchover Using Dual-VLAN, page 12
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.
•
Starting a Provisioning Session, page 6
•
Saving and Activating your Provisioning Changes, page 7
•
Ending a Provisioning Session Without Activating your Changes, page 8
•
Retrieving Provisioning Data, page 8
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
curr_ver—The name of the current configuration version. In place of the name of the current
configuration version, you can also enter:
If you do not know the name of your current configuration session, you can use the procedure in
the “Retrieving Data on the Current Provisioning Session” section on page 9.
– new—A new default session configuration; no existing source configuration is available.
– active—Selects the active configuration as the source for configuration changes.
SIP Automatic Switchover Using Dual-VLAN
6
SIP Automatic Switchover Using Dual-VLAN
Provisioning Tasks
Note
•
You can use new as the source configuration only when there is no existing, active set of provisioning
data in the configuration library. Therefore, new cannot be used as the source configuration once a
provisioning session has been saved and activated by using prov-cpy or prov-dply. Once you have
saved and activated a set of data, you must use either active or the name of the set of provisioning
data as the source configuration.
mod_ver—A new configuration version name that contains your provisioning changes.
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 on page 7 or ending your
provisioning session without saving and activating your changes, as described in the “Ending a
Provisioning Session Without Activating your Changes” section on page 8.
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
Using the prov-cpy and prov-dply MML commands can severely impact your system’s call processing
performance, depending on the extent of your provisioning changes. We recommend that these
commands be issued during a maintenance window when traffic is minimal.
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
When you enter the prov-cpy command, your provisioning session is also automatically ended. If you
want to make additional provisioning changes, you must start a new provisioning session as described
in the “Starting a Provisioning Session” section on page 6.
Caution
Using the prov-sync MML command can severely impact your system’s call processing performance.
We recommend that this command be issued during a maintenance window when traffic is minimal.
SIP Automatic Switchover Using Dual-VLAN
7
SIP Automatic Switchover Using Dual-VLAN
Provisioning Tasks
Note
When the prov-sync MML command is used to synchronize the provisioning settings on the standby
MGC host with current settings on the active MGC host, the system does not indicate when the
synchronization process has failed.
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
When you enter the prov-dply command, your provisioning session is also automatically ended, unless
an error occurs during execution. If you want to make additional provisioning changes, you must start a
new provisioning session as described in the “Starting a Provisioning Session” section on page 6.
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, page 8
•
Retrieving Data for All Components, page 9
•
Retrieving Data for All Components of a Particular Type, page 9
•
Retrieving Data on the Current Provisioning Session, page 9
•
Retrieving Data on Supported Signaling Protocols, page 9
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_name
Where:
•
component—The MML component type associated with the desired component. You can find a
complete list of MML component types in the Cisco Media Gateway Controller Software Release 9
Provisioning Guide.
•
MML_name—The MML name for the desired component. You can determine the MML names for
the various components using the prov-rtrv:all MML command.
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"
SIP Automatic Switchover Using Dual-VLAN
8
SIP Automatic Switchover Using Dual-VLAN
Provisioning Tasks
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:all
Retrieving 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:session
The system returns a response similar to the following:
MGC-02 - Media Gateway Controller 2003-01-13 13:39:19
M RTRV
"session=jtest:session"
/*
Session ID = mml1
SRCVER = active
DSTVER = 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:variants
Enabling 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
SIP Automatic Switchover Using Dual-VLAN
9
SIP Automatic Switchover Using Dual-VLAN
Provisioning Tasks
Note
The XECfgParm.dat parameters for this feature must be configured before you can provision virtual
IP addresses for SIP IP links. If you have not configured the parameters, perform the steps in the
“Verifying Parameter Settings and Re-configuring MGC Software” section on page 4 before
performing any of the procedures below.
To provision virtual IP address(es) on your SIP IP links, perform the following steps:
Step 1
Start a provisioning, as described in the “Starting a Provisioning Session” section on page 6.
Step 2
If you are provisioning SIP IP links for the first time, proceed to Step 9. Otherwise, proceed to Step 3.
Step 3
Enter the following command to display the settings for your SIP IP links:
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
The identified SIP IP links must be taken out-of-service. To do this, enter the following command:
mml>set-iplnk:name:OOS
Where 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
The identified SIP IP links must be deleted. Enter the following command to delete one of these SIP IP
links:
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
If any of the SIP IP links have an IP address setting of Virtual_IP_Addr1, proceed to Step 9. Otherwise,
proceed to Step 7.
Step 7
The signaling service associated with the deleted SIP IP links must be deleted. To do this, enter the
following MML command:
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
Enter the following command to provision a new SIP signaling service:
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"
SIP Automatic Switchover Using Dual-VLAN
10
SIP Automatic Switchover Using Dual-VLAN
Provisioning Tasks
Step 9
Enter the following command to provision a virtual IP address on a SIP IP link:
mml>prov-add:siplnk:name="name", desc="description", ipaddr="addr", svc="sigsrv",
port=pnum, pri=priority
Where:
•
name—The MML name you want to give to the component. The name can be as many as 20
characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin
with a letter.
•
description—The long name assigned that can be as many as 128 alphanumeric characters in length.
•
addr—First local IP address for a LAN interface. IP address should be one of the following property
names defined in the XECfgParm.dat file:
– Virtual_IP_Addr1
– Virtual_IP_Addr2
Note
If you attempt to provision a SIP IP link using a virtual IP address when you have not
configured the associated XECfgParm.dat parameter(s), the command will fail when
executed. For information on configuring the associated XECfgParm.dat parameters, refer
to the “Verifying Parameter Settings and Re-configuring MGC Software” section on page 4.
•
sigsrv—The MML name of a previously provisioned SIP signaling service.
•
pnum—Local IP port number. Valid value is any integer above 1024. For SIP IP links, we
recommend that you use 5060.
•
priority—Priority setting for this SIP IP link. Valid value is any integer above 0. Default value is 1.
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
If you want to create a second virtual IP address, enter the command below. Otherwise, proceed to
Step 11.
mml>prov-add:siplnk:name="name", desc="description", ipaddr="addr", svc="sigsrv",
port=pnum, pri=priority
Where:
•
name—The MML name you want to give to the component. The name can be as many as 20
characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin
with a letter.
•
description—The long name assigned that can be as many as 128 alphanumeric characters in length.
•
addr—Defines the second local IP address for a LAN interface. IP address should be one of the
following property names defined in the XECfgParm.dat file (excluding name used for the link
defined in Step 9):
– Virtual_IP_Addr1
– Virtual_IP_Addr2
SIP Automatic Switchover Using Dual-VLAN
11
SIP Automatic Switchover Using Dual-VLAN
Provisioning Tasks
Note
If you attempt to provision a SIP IP link using a virtual IP address when you have not
configured the associated XECfgParm.dat parameter(s), the command will fail when
executed. For information on configuring the associated XECfgParm.dat parameters, refer
to the “Verifying Parameter Settings and Re-configuring MGC Software” section on page 4.
•
sigsrv—The MML name of a previously provisioned SIP signaling service.
•
pnum—Local IP port number. Valid value is any integer above 1024. For SIP IP links, we
recommend that you use 5060.
•
priority—Priority setting for this SIP IP link. Valid value is any integer above 0. Default value is 1.
Note
The priority of the second SIP IP link should not match the priority of the first. If the first SIP
IP link uses a priority of 1, set the value for the second SIP IP link to 2 or higher.
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
Repeat steps 2 through 10 for each set of SIP IP links you want to provision with two virtual IP
addresses.
Step 12
Save and activate your new provisioning settings as described in the “Saving and Activating your
Provisioning Changes” section on page 7.
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 begin the provisioning session, perform the steps in the “Starting a Provisioning Session” section
on page 6. Once you have finished provisioning, save and activate your provisioning data by
performing the steps in the “Saving and Activating your Provisioning Changes” section on page 7.
To disable the virtual IP addresses on your SIP IP links, perform the following steps:
Step 1
Log in to the standby Cisco MGC as root and change directories to the etc subdirectory by entering the
following UNIX command:
cd /opt/CiscoMGC/etc
Step 2
Open the XECfgParm.dat using a text editor, such as vi.
Step 3
Search for the *.Virtual_IP_Addr1 parameter and set the value to 0.0.0.0.
Step 4
If you have not configured a second virtual IP address, proceed to Step 5. Otherwise, search for the
*.Virtual_IP_Addr2 parameter and set the value to 0.0.0.0.
Step 5
Search for the *.sipFailover parameter and set the value to false.
Step 6
Save your changes and close the text editor.
SIP Automatic Switchover Using Dual-VLAN
12
SIP Automatic Switchover Using Dual-VLAN
Provisioning Tasks
Step 7
Manually stop the MGC software on the standby MGC by entering the following UNIX command:
/etc/init.d/CiscoMGC stop
Step 8
Once the software shutdown is complete, manually start the MGC software on the standby MGC by
entering the following command:
/etc/init.d/CiscoMGC start
Step 9
Log in to the active MGC, start an MML session, and enter the following command:
mml>sw-over::confirm
Site alarms are automatically set until the out-of-service (OOS) MGC host is returned to an in-service
(IS) state.
Step 10
Repeat steps 1 through 8 for the newly standby MGC host.
Step 11
The affected SIP links must be taken out-of-service. To do this, enter the following command:
mml>set-iplnk:name:OOS
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 12
Log in to the active MGC host, start an MML session, and begin a provisioning session as described in
the “Starting a Provisioning Session” section on page 6.
Step 13
To change from virtual IP addressing to standard IP addressing, you must delete the SIP IP links
provisioned with virtual IP addressing. Enter the following command to delete an affected SIP IP link:
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
Enter the following command to delete the associated SIP signaling service:
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
Enter the following command to provision a new SIP signaling service:
mml>prov-add:sippath:name="name", mdo="ietf_sip"
Where:
•
name—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-ed:sippath:name="sipsrv1", mdo="ietf_sip"
Step 16
Enter the following command to enable the IP addresses on a SIP IP link:
mml>prov-add:siplnk:name="name", ipaddr="addr", ipaddr="addr"
Where:
•
name—MML name of the affected SIP IP link.
•
addr—First local IP address for a LAN interface. IP address should be one of the following property
names defined in the XECfgParm.dat file:
– IP_Addr1
SIP Automatic Switchover Using Dual-VLAN
13
SIP Automatic Switchover Using Dual-VLAN
Provisioning Tasks
– IP_Addr2
– IP_Addr3
– IP_Addr4
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
Save and activate your provisioning session as described in the “Saving and Activating your
Provisioning Changes” section on page 7.
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 on
page 4. 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
Determine whether the failure is caused by a physical failure or an administrative shutdown.
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
Verify that the LAN interfaces between the Cisco MGC and the affected SIP element are working
properly.
Note
Information on verifying the proper operation of a LAN interface on the Cisco MGC host can be
found in the Sun Microsystems documentation that came with your system. Information on
verifying the proper functioning of a LAN interface on other devices can be found in the user
documentation that came with that device.
SIP Automatic Switchover Using Dual-VLAN
14
SIP Automatic Switchover Using Dual-VLAN
Configuration Examples
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
Information on removing and replacing an Ethernet interface card on the Cisco MGC host can
be found in the Sun Microsystems documentation that came with your system. Information on
removing and replacing components on other devices can be found in the user documentation
that came with that device.
Contact the Cisco TAC to further analyze the problem and determine a solution. For more information
about contacting the Cisco TAC, refer to the “Obtaining Technical Assistance” section on page 19.
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.0
Configuring 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.7
SIP Automatic Switchover Using Dual-VLAN
15
SIP Automatic Switchover Using Dual-VLAN
Provisioning Examples
Configuring 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 = true
You 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
If the sipFailover parameter is set to false in the above configuration, the system uses the existing SIP
automatic switchover method.
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:OOS
set-iplnk:sip-sigchan2:OOS
prov-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, page 17
•
Alarms, page 17
SIP Automatic Switchover Using Dual-VLAN
16
SIP Automatic Switchover Using Dual-VLAN
Reference Information
•
Provisioning Worksheets, page 18
XECfgParm.dat Parameters
The XECfgParm.dat file configuration parameters used for this feature are in the table below.
Configuration Parameter
Definition
*.Virtual_IP_Addr1
Specifies a virtual IP address for a LAN interface. This IP
address must be within the subset of the IP address defined
for *.IP_Addr1.
Default: 0.0.0.0
Valid values: An IP address expressed in dotted decimal
notation.
*.Virtual_IP_Addr2
Specifies a virtual IP address for a LAN interface. This IP
address must be within the subset of the IP address defined
for *.IP_Addr2.
Default: 0.0.0.0
Valid values: An IP address expressed in dotted decimal
notation.
*.sipFailover
Specifies whether the MGC hosts, when connected with a
SIP network, should perform an automatic switchover when
a LAN interface fails.
Default: false
Valid values: true or false
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
Severity
Cause
Type
Action
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.
Critical
This alarm is caused by the failure of LAN interfaces, due to either physical failure or administrative
shut down.
1 (Communication error).
Refer to the “SIP Service Fail Over” section on page 14.
SIP Automatic Switchover Using Dual-VLAN
17
SIP Automatic Switchover Using Dual-VLAN
Glossary
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.
Table 1
SIP IP Link Worksheet
Name
Port
Priority
IP Address 1
SIP Path
Description
sip-sigchan1
5060
1
Virtual_IP_Addr1 sip-sigpath
SIP signaling channel 1
sip-sigchan2
5060
2
Virtual_IP_Addr2 sip-sigpath
SIP signaling channel 2
Glossary
Table 2 contains definitions of acronyms and technical terms used in this feature module.
Table 2
Glossary
Term
Definition
DNS
Domain Name Server
IP
Internet Protocol
LAN
Local Area Network
MGC
Media Gateway Controller
MGCP
Media Gateway Control Protocol
MIB
Managed Information Base
MML
Man-Machine Language
RFC
Return For Comment—A proposed standards document.
SIP
Session Initiation Protocol
VLAN
Virtual Local Area Network
SIP Automatic Switchover Using Dual-VLAN
18
SIP Automatic Switchover Using Dual-VLAN
Obtaining Documentation and Submitting a Service Request
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free
service and Cisco currently supports RSS version 2.0.
CCDE, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence,
Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are
service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP,
CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo,
Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive,
HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace,
MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare,
SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo
are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply
a partnership relationship between Cisco and any other company. (0812R)
SIP Automatic Switchover Using Dual-VLAN
19
SIP Automatic Switchover Using Dual-VLAN
Obtaining Documentation and Submitting a Service Request
SIP Automatic Switchover Using Dual-VLAN
20