Troubleshooting Guide
Table Of Contents
- Contents
- Chapter 1: Introduction
- Chapter 2: Safety messages
- Chapter 3: New in this document
- Chapter 4: Data collection required for Technical Support cases
- Chapter 5: Troubleshooting planning fundamentals
- Chapter 6: Troubleshooting fundamentals
- Chapter 7: Troubleshooting tool fundamentals
- Chapter 8: Log and trap fundamentals
- Chapter 9: Log configuration using ACLI
- Configuring a UNIX system log and syslog host
- Configuring secure forwarding
- Installing root certificate for syslog client
- Configuring logging
- Configuring the remote host address for log transfer
- Configuring system logging to external storage
- Configuring system message control
- Extending system message control
- Viewing logs
- Configuring ACLI logging
- Chapter 10: Log configuration using EDM
- Chapter 11: SNMP trap configuration using ACLI
- Chapter 12: SNMP trap configuration using EDM
- Chapter 13: Traps reference
- Chapter 14: Hardware troubleshooting
- Chapter 15: Software troubleshooting
- Chapter 16: Software troubleshooting tool configuration using ACLI
- Using ACLI for troubleshooting
- Using software record dumps
- Using trace to diagnose problems
- Using trace to diagnose IPv6 problems
- Viewing and deleting debug files
- Configuring port mirroring
- Configuring global mirroring actions with an ACL
- Configuring ACE actions to mirror
- Clearing ARP information for an interface
- Flushing routing, MAC, and ARP tables for an interface
- Pinging an IP device
- Running a traceroute test
- Showing SNMP logs
- Using trace to examine IS-IS control packets
- Viewing the metric type of IS-IS route in TLVs – detailed
- Viewing the metric type of IS-IS route in TLVs – summarized
- Chapter 17: Software troubleshooting tool configuration using EDM
- Chapter 18: Layer 1 troubleshooting
- Chapter 19: Operations and Management
- CFM fundamentals
- CFM configuration using ACLI
- Autogenerated CFM
- Configuring explicit mode CFM
- Displaying SPBM nodal configuration
- Configuring simplified CFM SPBM
- Triggering a loopback test (LBM)
- Triggering linktrace (LTM)
- Triggering a Layer 2 ping
- Triggering a Layer 2 traceroute
- Triggering a Layer 2 tracetree
- Triggering a Layer 2 tracemroute
- Using trace CFM to diagnose problems
- Using trace SPBM to diagnose problems
- CFM configuration using EDM
- Autogenerated CFM
- Configuring explicit CFM
- Configuring Layer 2 ping
- Initiating a Layer 2 traceroute
- Viewing Layer 2 traceroute results
- Configuring Layer 2 IP ping
- Viewing Layer 2 IP Ping results
- Configuring Layer 2 IP traceroute
- Viewing Layer 2 IP traceroute results
- Triggering a loopback test
- Triggering linktrace
- Viewing linktrace results
- Configuring Layer 2 tracetree
- Viewing Layer 2 tracetree results
- Configuring Layer 2 trace multicast route on a VLAN
- Configuring Layer 2 tracemroute on a VRF
- Viewing Layer 2 trace multicast route results
- CFM configuration example
- Chapter 20: Upper layer troubleshooting
- Troubleshooting SNMP
- Troubleshooting DHCP
- Troubleshooting DHCP Relay
- Troubleshooting client connection to the DHCP server
- Troubleshooting IPv6 DHCP Relay
- IPv6 DHCP Relay switch side troubleshooting
- IPv6 DHCP Relay server side troubleshooting
- IPv6 DHCP Relay client side troubleshooting
- Enabling trace messages for IPv6 DHCP Relay
- Troubleshooting IPv6 VRRP
- VRRP transitions
- Enabling trace messages for IPv6 VRRP troubleshooting
- Risks associated with enabling trace messages
- VRRP with higher priority running as backup
- Downgrading or upgrading from releases that support different key sizes
- Troubleshooting IPv6 connectivity loss
- Troubleshooting TACACS+
- Troubleshooting RSMLT
- Chapter 21: Unicast routing troubleshooting
- Chapter 22: Multicast troubleshooting
- Chapter 23: Multicast routing troubleshooting using ACLI
- Viewing IGMP interface information
- Viewing multicast group trace information for IGMP snoop
- Viewing IGMP group information
- Showing the hardware resource usage
- Using PIM debugging commands
- Determining the protocol configured on the added VLAN
- Determining the data stream learned with IP Multicast over Fabric Connect on the VLAN
- Displaying the SPBM multicast database
- Troubleshooting IP Multicast over Fabric Connect for Layer 2 VSNs
- Troubleshooting IP Multicast over Fabric Connect for Layer 3 VSNs
- Troubleshooting IP Multicast over Fabric Connect for IP Shortcuts
- Defining the IS-IS trace flag for IP multicast
- Chapter 24: Multicast routing troubleshooting using EDM
- Viewing IGMP interface information
- Viewing IGMP snoop trace information
- Viewing IGMP group information
- Viewing multicast group sources
- Viewing multicast routes by egress VLAN
- Enabling multicast routing process statistics
- Determining the data stream learned when IP Multicast over Fabric Connect is configured on the VLAN
- Showing the SPBM multicast database
- Chapter 25: Transparent Port UNI feature troubleshooting using ACLI
- Chapter 26: Troubleshooting MACsec
- Chapter 27: Troubleshooting MACsec using EDM
- Chapter 28: Troubleshooting Fabric Attach
- Troubleshooting Fabric Attach using the ACLI
- Troubleshooting Fabric Attach using the EDM
- Fabric Attach troubleshooting example
• Simplified: In the simplified way of configuring CFM, you can use the simplified command cfm
spbm enable which automatically creates the MD, MA, MEP and associates it with the B-
VLAN and the MIP level with the B-VLAN.
Autogenerated CFM
CFM provides two methods for configuration; autogenerated and explicit. You cannot use both. You
must choose one or the other. Use the procedures in this section to configure autogenerated MEPs
that eliminate the need to configure a MD, MA, and MEP ID to create a MEP.
• For SPBM B-VLANs, you can use either autogenerated or explicitly configured CFM MEPs.
• For C-VLANs, you can only use autogenerated CFM MEPs.
Important:
Only the VSP 4000 Series switch supports configuring autogenerated CFM on C-VLANs.
The CFM show commands that display MD, MA, and MEP information work for both autogenerated
and explicitly configured CFM MEPs.
Previous explicit CFM configurations of MDs, MAs and MEPs on SPBM B-VLANs continue to
function in this release. However, if you want to enable the new autogenerated commands you must
first remove the existing MEP and MIP on the SPBM B-VLAN.
The switch only supports one MEP and one MIP, either autogenerated or explicitly configured, on
the SPBM B-VLAN. Similarly, the switch only supports one MEP and one MIP on the C-VLAN. This
means that if you want to use these autogenerated MEPs, you cannot use your existing CFM
configuration. You must first remove the existing MEP or MIP on the SPBM B-VLAN.
For information on configuring autogenerated CFM using the ACLI, see:
•
Configuring autogenerated CFM on SPBM B-VLANs on page 155
• Configuring autogenerated CFM on C-VLANs on page 157
Configuring autogenerated CFM on SPBM B-VLANs
Use this procedure to configure the autogenerated CFM MEP and MIP level for every SPBM B-
VLAN on the chassis. This eliminates the need to explicitly configure an MD, MA, and MEP ID, and
to associate the MEP and MIP level to the SPBM B-VLAN.
When you enable this feature, the device creates a global MD (named spbm) for all the SPBM
Nodal MEPs. This MD has a default maintenance level of 4, which you can change with the level
attribute. All the MEPs that the device creates use the MEP ID configured under the global context,
which has a default value of 1.
The nodal MEPs are automatically associated with the SPBM B-VLANs configured. The MIP level
maps to the global level. When you enable the feature, the device automatically associates the MIP
level with the SPBM B-VLANs configured. The feature is disabled by default.
CFM configuration using ACLI
January 2017 Troubleshooting 155
Comments on this document? infodev@avaya.com










