Traffic Does Not Traverse Ivr Path - Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual

Mds 9000 family
Hide thumbs Also See for 9134 - MDS Multilayer Fabric Switch:
Table of Contents

Advertisement

Chapter 13
Troubleshooting IVR
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m

Traffic Does Not Traverse IVR Path

Symptom
Table 13-8
Traffic Does Not Traverse IVR Path
Symptom
Possible Cause
Traffic does not
Fabric includes an SN5428 or MDS
traverse the IVR path.
9020 switch and you have not added
the IVR virtual domains to the
remote VSAN domain lists.
Internal message payload uses
destination ID.
Devices are in different IVR service
groups.
OL-9285-05
Traffic does not traverse the IVR path.
Solution
Choose Fabricxx > All VSANs > IVR and select the Action
tab in Fabric Manager.Fill in the Create Virtual Domains for
VSAN field and click Apply Changes. Select the CFS tab,
and set ConfigAction to commit, and click Apply Changes.
Or use the ivr virtual-fcdomain-add vsan-ranges CLI
command to add existing and future virtual domains to the
domain list for the selected VSANs.
Repeat this on all edge VSANs.
See the
"IVR Network Address Translation Fails" section on
page
13-8.
Verify the IVR service groups. Choose Fabricxx > All
VSANs > IVR and select the Service Group tab in Fabric
Manager.
Or use the show ivr service-group CLI command.
Move the VSANs into the same IVR service group. Choose
Fabricxx > All VSANs > IVR and select the Service Group
tab in Fabric Manager.
Or use the ivr service-group CLI command. Use the ivr
service-group activate CLI command to activate this
change. If CFS is enabled, use the ivr commit CLI command
to commit this change.
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
IVR Issues
13-11

Hide quick links:

Advertisement

Table of Contents

Troubleshooting

loading

Table of Contents