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
The Nodal MEP and MIP are expanded to respond to both the Nodal MAC address as well as the
Virtual SMLT MAC address if both MACs are being advertised on its B-VLAN. In addition a source
mode is added to the LTM and LBM command to use either the Nodal MAC or the SMLT virtual
MAC address as the source MAC in the packet.
Configuration considerations
When you configure CFM, be aware of the following configuration considerations.
General CFM
• A single switch has a limit of one MEP and one MIP on a C-VLAN or B-VLAN.
• The maintenance level for MEPs and MIPs on a given B-VID (in a network) must be configured
to the same level for them to respond to a given CFM command.
• You can configure global CFM at only one MD level for each switch for each VLAN type.
• All nodal MEPs and MIPs are restricted to SPBM B-VIDs.
• SMLT Virtual MAC for C-VLAN does not exist, so the switch does not support this option for the
l2 ping and l2 traceroute commands.
Autogenerated CFM
• Autogenerated MEPs are not unique across the entire network unless you configure the global
MEP ID on each switch to a different value. You must configure a unique MEP ID at a global
level, for CFM.
• A single switch can have only one autogenerated MEP or MIP for each B-VLAN or C-VLAN.
Explicit CFM
• Previous explicit CFM configurations of MDs, MAs and MEPs on SPBM B-VLANs continue to
be supported. However, if you want to enable autogenerated CFM you must first remove the
existing MEP and MIP on the SPBM B-VLAN.
• You can assign maintenance levels for each CFM SPBM MEP and MIP to each SPBM B-VLAN
individually or you can assign maintenance levels and global MEPs for all SPBM VLANs by
following the appropriate procedure:
-
Assigning a MEP MIP level to an SPBM B-VLAN on page 163
- Assigning MEP MIP levels to SPBM B-VLANs globally on page 165
- Configuring CFM nodal MEP on page 190
C-VLAN versus SPBM B-VLAN considerations
Important:
Only VSP 4000 Series supports CFM configuration on C-VLANs.
CFM breaks the network into sections, called MEPs, so you can determine exactly where the
problem exists.
The MEPs and MIPs configured for SPBM VLANs do not respond to CFM messages sent from C-
MAC VLANs because the VLAN and packet encapsulation are different.
To forward customer traffic across the core network backbone, SPBM uses IEEE 802.1ah Provider
Backbone Bridging (PBB) MAC-in-MAC encapsulation, which hides the customer MAC (C-MAC)
CFM fundamentals
January 2017 Troubleshooting 153
Comments on this document? infodev@avaya.com










