Panasonic NN46240-710 Instruction Manuals and User Guides
We have 1 Instruction Manual and User Guide for NN46240-710 Panasonic
Manuals
| Recognized languages: | English |
|---|---|
| Pages: | 181 |
| Size: | 919 KB |
Show table of contents
Read manual
Document Outline
- Contents
- Figures
- Tables
- Contents
- About this document
- Contents
- Figures
- Tables
- 1
- L2TP troubleshooting
- About this chapter
- 1.1 L2TP overview
- 1.2 VPDN troubleshooting on the L2TP
- 1.2.1 Networking environment
- 1.2.2 Configuration notes
- 1.2.4 Troubleshooting procedures
- Determining that the user address is correct
- Checking whether network congestion occurs
- Checking that the tunnel exists
- Checking the state of PPP negotiation on the LNS side
- Checking that the LAC can ping through the loopback interface of the LNS
- Checking the status of PPP negotiation on the LAC side
- 1.3 Troubleshooting L2TP access to the Layer 3 VPN
- 1.4 Troubleshooting cases
- 1.5 FAQs
- 1.6 Diagnostic tools
- Contents
- Figures
- Tables
- L2TP troubleshooting
- 2
- GRE troubleshooting
- About this chapter
- 2.1 GRE overview
- 2.2 Troubleshooting GRE
- 2.3 Troubleshooting cases
- 2.5 Diagnostic tools
- Contents
- Figures
- About this chapter
- 3.1 BGP/MPLS IP VPN overview
- 3.2 MPLS L3VPN troubleshooting
- 3.3 Troubleshooting cases
- 3.3.1 PE fails to send private network routes to the remote CE
- 3.3.2 CEs cannot communicate
- 3.3.3 Failure to ping large packets of the private network
- 3.3.4 PE cannot ping through the remote CE network segment
- 3.3.5 Failure to establish the MP-EBGP peer in inter-AS VPN-OptionC
- Fault Symptom
- Fault analysis
- Troubleshooting procedure
- Summary
- Q: A BGP adjacency establishes between PEs, but private network packets cannot forward normally. What is the problem?
- Q: In the BGP/MPLS VPN networking of the inter-AS Option B, proper adjacencies establish between ASBRs, but private network packets cannot forward. What are the causes?
- 3.5 Diagnostic tools
- Contents
- Figures
- MPLS L2VPN troubleshooting
- About this chapter
- 4.1 MPLS Layer 2 VPN overview
- 4.3 Troubleshooting cases
- 4.3.1 VC type is not supported when setting up a PW on an ATM subinterface
- 4.3.2 A static PW cannot be switched with other PWs
- 4.3.3 Switch-L2VC is down after PW switching configuration
- 4.3.4 PW attributes cannot be changed by using the reset pw command
- 4.3.5 VC is up but the PPP session cannot establish
- 4.3.6 VC under the interface is missing after the link protocol changes
- 4.3.7 Both the session and the AC are up, but the VC cannot be up
- 4.3.8 Ethernet interconnects with ATM, the VC is up, but the ping between CEs fails
- 4.3.9 CEs cannot communicate by using the accessing mode of VLAN
- 4.3.10 CEs cannot access each other though the static VC is up
- 4.3.11 VC is down though AC is up
- 4.3.12 Large-sized packets are lost between CEs on two ends of Layer 2 VPN
- 4.3.13 Failure to establish the MPLS LDP session between PEs when RIP-1 is used in the Layer 2 VPN backbone
- Fault symptom
- Fault analysis
- Troubleshooting procedure
- Summary
- Q: How can I run Martini mode on the existent version?
- Q: In what cases do I configure local-ce and local-mac in different media interworking?
- Q: What special configuration should be done on an FR interface? What is the configuration guideline when CE acts as DCE and PE functions as DTE?
- Q: What is the function of the control word in Layer 2 VPN?
- Q: Can I specify multihop VCs with the same peer and different encapsulation types when I configure switch-Layer 2 VC on SPE?
- Q: Can I set the PW ID to 0 or ignore the configuration?
- Q: How can I configure Layer 2 VPN load balancing?
- Q: What does the multihop mean in Layer 2 VPN? In what cases is multihop used? How can I configure multihop?
- Q: Why can the same Layer 2 VC be configured with two types of encapsulation when MPLS switch-Layer 2 VC is configured on SPE?
- Q: What are the conditions for a PW being up?
- Q: What are the differences between tag or untagged configuration in the Ethernet interface view and tagged or raw configuration in the PWE3 view?
- Q: After CEs adopt the ATM to access PEs, all the CE interfaces and PE interfaces are up. Why can the CEs on two ends not ping through each other?
- 4.5 Diagnostic tools
- Contents
- Figures
- GRE troubleshooting
- 5
- VPLS troubleshooting
- About this chapter
- 5.1 VPLS overview
- 5.2 VPLS troubleshooting
- 5.2.1 Typical networking
- 5.2.2 Configuration notes
- 5.2.3 Troubleshooting flowchart
- 5.2.4 Troubleshooting procedures
- 5.3.1 A VSI cannot be up in LDP signaling mode
- 5.3.2 Packets cannot forward successfully between two PEs though VSI is up
- 5.3.3 A VSI cannot be up in BGP signaling mode
- Fault symptom
- Fault analysis
- Troubleshooting procedure
- Summary
- Q: Why can the VSI not be up after a tunnel and an AC are established in VPLS configuration?
- Q: Why can the VPLS not be configured successfully on the VLAN interface?
- Q: What are the requirements for the PW to be up in the configuration of VPLS?
- 5.5 Diagnostic tools
- VPLS troubleshooting