Troubleshooting PPP and PPPoE Dynamic Interfaces
You can issue the profile-reassign command to help you use PPP and PPPoE packet–logging capabilities to debug and troubleshoot PPP and PPPoE dynamic interfaces. To use the profile-reassign command, you must access Privileged Exec mode at privilege level 5 or higher.
The profile-reassign command enables you to reassign the profile currently assigned to the specified encapsulation type for the specified ATM 1483 subinterface. In effect, you swap the currently assigned nondebug profile for a debug profile that has identical attributes with the addition of one or more PPP or PPPoE packet–logging attributes enabled.
To troubleshoot PPP and PPPoE dynamic interfaces:
- Create a debug profile that includes the same attributes as an existing nondebug profile, with the addition of one or more PPP or PPPoE packet–logging attributes enabled.
Observe the following guidelines when you create the debug profile:
- Because PPP and PPPoE packet logging is performed at log severity 7 (debug priority), configure a destination such as the console to log severity level 7 and issue the log here command to enable packet capture using the debug profile you created.
- Before you reassign the debug profile to the ATM 1483 subinterface, make sure that the number of PPP dynamic interfaces has not already exceeded the maximum number of aggregate dynamic and static PPP interfaces for which you can log PPP packets. For more information about this and other system maximums, see JUNOSe Release Notes, Appendix A, System Maximums.
For details about creating and using profiles, see Configuring a Dynamic Interface from a Profile.
- Access Privileged Exec mode at privilege level 5 or higher.
- From Privileged Exec mode, issue the profile-reassign command to replace the nondebug profile currently assigned to the specified encapsulation type for the specified ATM 1483 interface with the debug profile created in Step 1.
host1>enable 5
Password: *********
host1#
You must specify one of the following encapsulation types to which the debug profile applies: ppp, pppoe, or any. You can use the any encapsulation type if neither the ppp encapsulation type nor the pppoe encapsulation type has an existing profile assignment. For example:
host1#profile-reassign atm 2/0.101 ppp pppLogConfig
- (Optional) Use the appropriate show command to verify the profile reassignment. For example:
host1#show atm subinterface atm 2/0.101
When you reassign a debug profile to an ATM 1483 subinterface, the reassignment is stored in NVS and persists after a reboot. If you issue the show atm subinterface or show configuration command after the profile is reassigned, these commands display the new profile assignment.
- (Optional) To restore the initial (nondebug) profile assignment after you troubleshoot the dynamic interface, issue the profile-reassign command again using the name of the nondebug profile. For example:
host1#profile-reassign atm 2/0.101 ppp pppConfig
enable
- Use to move from User Exec to Privileged Exec mode.
- In Privileged Exec mode, you can access all other user interface modes. From here you can configure, monitor, and manage all aspects of the router.
- Optionally, you can specify one of the following privilege levels; the default level is 10.
- 0—The user can execute the help, enable, disable, and exit commands.
- 1—The user can execute commands in User Exec mode plus commands at level 0.
- 5—The user can execute Privileged Exec show commands plus the commands at levels 1 and 0.
- 10—The user can execute all commands except support commands, which may be provided by Juniper Networks Customer Service.
- 15—The user can execute support commands.
- Set a password for this mode by using either the enable password or the enable secret command in Global Configuration mode. Doing so protects the router from any unauthorized use.
- After a password is set, anyone trying to use Privileged Exec mode is prompted to provide the password.
- Example
host1>enable 5
Password:*******
host1#
profile-reassign
- Use to reassign the profile currently assigned to the specified encapsulation type for the specified ATM 1483 interface. For troubleshooting purposes, use the profile-reassign command to swap the currently assigned profile for one that has PPP or PPPoE packet–logging attributes enabled.
- This command is available from Privileged Exec mode at privilege level 5 or higher.
- Specify one of the following keywords:
- ppp—Specifies a PPP encapsulation type to which the profile applies
- pppoe—Specifies a PPPoE encapsulation type to which the profile applies
- any—Specifies any autoconfigured encapsulation that does not have a specific profile assignment; valid only if neither the ppp encapsulation type nor the pppoe encapsulation type has an existing profile assignment
- Specify a profile name of up to 80 alphanumeric characters.
- Example 1—Facilitates debugging for the ppp encapsulation type by swapping profile pppConfig for profile pppLogConfig, which includes PPP packet–logging attributes
host1#profile-reassign atm 2/0.101 ppp pppLogConfig
WARNING: Execution of this command will cause all dynamic interfaces over atm 2/0.101 to be torn-down.
Proceed with profile reassignment? [confirm] yes
Profile pppConfig replaced by profile pppLogConfig for ppp.
host1#profile-reassign atm 3/0.101 any anyLogConfig
WARNING: Execution of this command will cause all dynamic interfaces over atm 3/0.101 to be torn-down.
Proceed with profile reassignment? [confirm] yes
Profile anyConfig replaced by profile anyLogConfig for any.
host1#profile-reassign atm 2/0.101 ppp pppConfig
WARNING: Execution of this command will cause all dynamic interfaces over atm 2/0.101 to be torn-down.
Proceed with profile reassignment? [confirm] yes
Profile pppLogConfig replaced by profile pppConfig for ppp.