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
addresses in a backbone MAC (B-MAC) address pair. MAC-in-MAC encapsulation defines a B-MAC
destination address (BMAC-DA) and a B-MAC source address (BMAC-SA). In SPBM, each node
populates its forwarding database (FDB) with the B-MAC information derived from the IS-IS shortest
path tree calculations.
Typically the SPBM Backbone Core Bridges (BCBs) in the SPBM cloud only learn the B-MAC
addresses. The Backbone Edge Bridges (BEBs) know the Customer MACs on the appropriate
BEBs that terminate the virtual services networks (VSNs). As such, the nodes within the SPBM
cloud have no knowledge of the C-MAC addresses in the VSNs.
Important:
To trace a route to a MAC address, the MAC address must be in the VLAN FDB table.
• For C-VLANs, you have to trigger an l2 ping to learn the C-MAC address.
• For B-VLANs, you do not have to trigger an l2 ping to learn the C-MAC address
because IS-IS populates the MAC addresses in the FDB table.
In both cases, linktrace traces the path up to the closest device to that MAC address that
supports CFM in the SPBM cloud.
C-VLAN source addresses
CFM uses either the VLAN MAC or the CFM C-MAC for the BMAC-SA for the C-VLANs. The CFM
C-MAC is the value of the management base MAC, which ends in 0x64. The system creates the
VLAN MAC after a user adds an IP address to a VLAN.
If a VLAN has a MAC address, the system uses the VLAN MAC as the BMAC-SA by default. If a
VLAN does not have a MAC address, the system uses the CFM C-MAC for the BMAC-SA. You may
also configure the system to use the CFM C-MAC, even if a VLAN MAC exists.
CFM configuration using ACLI
This section provides procedures to configure and use Connectivity Fault Management (CFM) using
Avaya Command Line Interface (ACLI). The Shortest Path Bridging MAC (SPBM) network needs a
mechanism to debug connectivity issues and to isolate faults. This is performed at Layer 2, not
Layer 3. To support troubleshooting of the SPBM cloud, Virtual Services Platform 4000 supports a
subset of CFM functionality.
Note:
When you enable CFM in an SBPM network, Avaya recommends that you enable CFM on the
Backbone Edge Bridges (BEB) and on all Backbone Core Bridges (BCB). If you do not enable
CFM on a particular node, you cannot obtain CFM debug information from that node.
CFM is configured by using the following two ways:
• Explicit: In the explicit way of configuring CFM, you can configure an MD, MA, MEP and then
associate the MEP to a B-VLAN and MIP level to a B-VLAN.
Operations and Management
January 2017 Troubleshooting 154
Comments on this document? infodev@avaya.com