Detecting Faulty Hardware
Using the CLI to View Status LEDs
[local]host_name# show
leds all
Slot 01: Run/Fail: Green | Active: Off | Standby: Green
Slot 08: Run/Fail: Green | Active: Green | Standby: Off
Status: Green | Service: Off |
Slot 09: Run/Fail: Green | Active: Off | Standby: Green
Status: Green | Service: Off |
Slot 12: Run/Fail: Green | Active: Green | Standby: Off
Slot 14: Run/Fail: Green | Active: Green | Standby: Off
Slot 17: Run/Fail: Green | Active: Green | Standby: Off
Slot 24: Run/Fail: Green | Active: Green | Standby: Off
Slot 25: Run/Fail: Green | Active: Off | Standby: Green
Slot 30: Run/Fail: Green | Active: Green | Standby: Off
Slot 33: Run/Fail: Green | Active: Off | Standby: Off
Slot 40: Run/Fail: Green | Active: Green | Standby: Off
Checking the LED on the PFU
| Color | Description | Troubleshooting |
|---|---|---|
| Green | PFU powered with no errors detected |
None needed.
|
| None | PFU is not receiving power | Verify that the power switch is in the ON position. |
| Verify that the RTN and -VDC lugs are attached properly. | ||
| Verify that the ground lug is attached properly. Verify that the power source is on and is supplying the correct voltage and sufficient current. | ||
| Check the cables from the power source to the rack for continuity. | ||
| If a power distribution panel (PDP) is installed between the power distribution frame (PDF) and the chassis, verify that the circuit breakers are set to ON. | ||
| If a PDP is installed between the PDF and the chassis, check the cables from the PDP to the chassis for continuity. | ||
| If all of the above suggestions have been verified, then it is likely that the PFU is not functional. Please contact your service representative. |
Checking the LEDs on the SMC
SMC Run/Fail LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card powered with no errors detected. | None needed. |
| Blinking Green | Card is initializing and/or loading software. | This is normal operation during boot-up. |
| Red | Card powered with error(s) detected. | Errors were detected during the Power On Self Tests (POSTs). It is likely that the errors were logged to the command line interface during boot. Refer to one or more of the following to help analyze this problem. |
| Monitoring the System for show commands, the outputs of which will assist in further determining the problem. | ||
| System Logs for information on how to view logs. | ||
| The SNMP MIB Reference for information on associated status and alarm conditions. | ||
| None | Card is not receiving power. | Verify that the POWER LEDs on the PFUs are green. If they are not, refer to Checking the LED on the PFU for troubleshooting information. |
| Verify that the power source is supplying ample voltage and current to the chassis. | ||
| Verify that the card is properly installed per the instructions in the ASR 5000 Installation Guide. | ||
| If all of the above suggestions have been verified, it is possible that the SMC is not functional. Please contact your service representative. |
SMC Active LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is active. | None needed for the SMC in slot 8. If green for the SMC in slot 9, verify that the SMC in slot 8 is installed properly according to the instructions in this document. |
| Blinking Green | Tasks or processes are being migrated from the active SMC to the redundant/secondary SMC. | Verify that the Standby LED on the redundant SMC is also blinking green. If so, there is an issue with the active SMC. Refer to one or more of the following to help analyze this problem. |
| Monitoring the System for show commands, the outputs of which will assist in further determining the problem. | ||
| System Logs for information on how to view logs. | ||
| The SNMP MIB Reference for information on associated status and alarm conditions. | ||
| None |
Card is not receiving power
OR
Card is in Standby Mode.
|
Verify that the Run/Fail LED is green. If so, the card is receiving power and POST test results are positive. If it is off, please refer to SMC RunFail LED States for troubleshooting information. |
| Check the state of the Standby LED. If it is green, the card is in standby mode. If needed, refer to the Configuring Packet Processing Card and Line Card Availability section of System Settings for information on making the card active. |
SMC Standby LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is in redundant mode. | None needed for the SMC in slot 9. If green for the SMC in slot 8, then verify it is installed properly according to the instructions in this document. |
| Blinking Green | Tasks or processes are being migrated from the active SMC to the redundant/secondary SMC. | Verify that the Active LED on the redundant SMC is also blinking green. If so, there is an issue with the active SMC. Refer to one or more of the following to help analyze this problem. |
| Monitoring the System for show commands, the outputs of which will assist in further determining the problem. | ||
| System Logs for information on how to view logs. | ||
| The SNMP MIB Reference for information on associated status and alarm conditions. | ||
| None |
Card is not receiving power.
OR
Card is in Active Mode.
|
Verify that the Run/Fail LED is green. If so, the card is receiving power and POST test results are positive. If it is off, please refer to SMC RunFail LED States for troubleshooting information. |
| Check the state of the Active LED. If it is green, the card is in active mode. If needed, refer to Manually Initiating a Management Card Switchover for information on configuring the card to serve as a redundant component. |
SMC Status LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | No system errors detected. | None needed. |
| Red | Failures detected. | Check the Run/Fail LEDs for all installed application cards, and line cards. If any are red or off, refer to the troubleshooting information in this chapter pertaining to that device. |
| Monitoring the System for show commands, the outputs of which will assist in further determining the problem. | ||
| System Logs for information on how to view logs. | ||
| The SNMP MIB Reference for information on associated status and alarm conditions. | ||
| None | Card is not receiving power. | Verify that the Run/Fail LED is green. If so, the card is receiving power and POST test results are positive. If it is off, refer to SMC RunFail LED States for troubleshooting information. |
SMC Service LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Yellow | System requires maintenance (fan filter, temperature warning, PFU outage etc.). | Refer to one or more of the following to help analyze this problem. |
| Monitoring the System for show commands, the outputs of which will assist in further determining the problem. | ||
| System Logs for information on how to view logs. | ||
| The SNMP MIB Reference for information on associated status and alarm conditions. | ||
| None | Card is not receiving power. |
No maintenance needed.
|
SMC Busy LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green/ Blinking Green | Data is being read from/written to one of the memory devices. |
No maintenance needed.
NOTE: You
should wait until this LED is off before removing the SMC from the
chassis. This practice ensures the integrity of all data
being transferred to or from the memory device.
|
| None | The memory devices are not in use. |
No maintenance needed.
|
Checking the LEDs on the Packet Processing Cards
Packet Processing Card Run/Fail LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card powered with no errors detected. | None needed. |
| Blinking Green | Card is initializing and/or loading software. | None needed. |
| Red | Card powered with error(s) detected. | Errors were detected during the Power On Self Tests (POSTs). It is likely that the errors were logged to the system's command line interface during the boot process. |
| Monitoring the System for show commands, the outputs of which will assist in further determining the problem. | ||
| System Logs for information on how to view logs. | ||
| The SNMP MIB Reference for information on associated status and alarm conditions. | ||
| None | Card is not receiving power. | Verify that the POWER LEDs on the PFUs are green. If they are not, refer to Checking the LED on the PFU for troubleshooting information. |
| Verify that the power source is supplying ample voltage and current to the chassis. | ||
| Verify that the card is properly installed per the instructions in the ASR 5000 Installation Guide. | ||
| If all of the above suggestions have been verified, it is possible that the packet processing card is not functional. Please contact your service representative. |
Packet Processing Card Active LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is active. | The first time power is applied to the system, all of the packet processing cards should be booted into the standby mode. Therefore, this LED should be off. |
| Blinking Green | Tasks or processes are being migrated from an active card to a redundant/secondary card. | Verify that the Standby LED on a redundant packet processing card is also blinking green. If so, there is an issue with the card that was active and is transferring its processes. |
| Refer to Monitoring the System for information on determining the status of the packet processing card and system software processes. | ||
| None |
Card is not receiving power.
OR
Card is in Standby Mode.
|
Verify that the Run/Fail LED is green. If so, the card is receiving power and POST test results are positive. If it is off, please refer to Packet Processing Card Run/Fail LED States for troubleshooting information. |
| Check the state of the Standby LED. If it is green, the card is in standby mode. This is normal operation for the initial power-up. If needed, refer to the Configuring Packet Processing and Line Card Availability section of System Settings for information on making the card active. |
Packet Processing Card Standby LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is in redundant mode. | The first time power is applied to the system, all of the packet processing cards should be booted into the standby mode. Therefore, this is normal operation. |
| Blinking Green | Tasks or processes are being migrated from the active SMC to the redundant/secondary SMC. | Verify that the Active LED on the redundant packet processing card is also blinking green. If so, there is an issue with the active packet processing card and the system is transferring its processes. |
| Monitoring the System for show commands, the outputs of which will assist in further determining the problem. | ||
| System Logs for information on how to view logs. | ||
| The SNMP MIB Reference for information on associated status and alarm conditions. | ||
| None |
Card is not receiving power.
OR
Card in Active Mode.
|
Verify that the Run/Fail LED is green. If so, the card is receiving power and POST test results are positive. If it is off, please refer to Packet Processing Card RunFail LED States for information on troubleshooting. |
| Check the state of the Active LED. If it is green, the card is in active mode. If needed, refer to Manually Initiating a Packet Processing Card Migration for information on configuring the card to serve as a redundant component. |
Checking the LEDs on the SPIO
SPIO Run/Fail LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card powered with no errors detected. | None needed. |
| Red | Card powered with error(s) detected. | Errors were detected during the Power On Self Tests (POSTs). It is likely that the errors were logged to the command line interface during the boot process. |
| Refer to Monitoring the System for information on determining the status of system hardware components. | ||
| None | Card is not receiving power. | Verify that the POWER LEDs on the PFUs are green. If they are not, refer to Checking the LED on the PFU for troubleshooting information. |
| Verify that the power source is supplying ample voltage and current to the chassis. | ||
| Verify that the card is properly installed per the instructions in the ASR 5000 Installation Guide. | ||
| If all of the above suggestions have been verified, it is possible that the SPIO is not functional. Please contact your service representative. |
SPIO Active LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is active. | None needed for SPIO in slot 24. If green for SPIO in slot 25, then verify that SPIO in slot 24 is installed properly. |
| None |
Card is not receiving power.
OR
Card in Standby Mode.
|
Verify that the Run/Fail LED is green. If so, the card is receiving power and POST test results are positive. If it is off, refer to SPIO RunFail LED States for troubleshooting information. |
| Check the state of the Standby LED. If it is green, the card is in standby mode. This is normal for the SPIO in slot 25 since the chassis automatically places the card into standby mode at boot up. |
SPIO Standby LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is in redundant mode. | None needed for SPIO in slot 25. If green for SPIO in slot 24, check the status of the SMC installed in slot 8. |
| If the SMC in slot 8 is in standby mode, it is possible that there is a problem. | ||
| Monitoring the System for show commands, the outputs of which will assist in further determining the problem. | ||
| System Logs or information on how to view logs. | ||
| The SNMP MIB Reference for information on associated status and alarm conditions. | ||
| None |
Card is not receiving power.
OR
Card is in Active Mode.
|
Verify that the Run/Fail LED is green. If so, the card is receiving power and POST test results are positive. If it is off, refer to SPIO RunFail LED States for troubleshooting information. |
| Check the state of the Active LED. If it is green, the card is in active mode. This is normal for the SPIO in slot 24 since the chassis automatically makes the card active at boot up. |
SPIO Interface Link LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Link is up. |
None needed.
NOTE: This
LED will not indicate the presence of a network link until the interface
parameters are set during the software configuration process.
|
| None |
No power is available
to card.
OR
Link is down.
|
Verify that the Run/Fail LED is green. If so, the card is receiving power. If it is off, refer to SPIO RunFail LED States for troubleshooting information. |
| Verify that the interface is cabled properly. | ||
| Verify that the device on which the interface is located is cabled and powered properly. |
SPIO Interface – Activity LED States
Checking the LEDs on Ethernet Line Cards
Ethernet Line Card Run/Fail LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card powered with no errors detected. | None needed. |
| Red | Card powered with error(s) detected. | Errors were detected during the Power On Self Tests (POSTs). It is likely that the errors were logged to the command line interface during the boot process. |
| Refer to Monitoring the System for information on determining the status of system hardware components. | ||
| None | Card is not receiving power. | Verify that the POWER LEDs on the PFUs are green. If they are not, refer to Checking the LED on the PFU for troubleshooting information. |
| Verify that the power source is supplying ample voltage and current to the chassis. | ||
| Verify that the card is properly installed per the instructions in the ASR 5000 Installation Guide. | ||
| If all of the above suggestions have been verified, it is possible that the line card is not functional. Please contact your service representative. |
Ethernet Line Card Active LED States
IMPORTANT:
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is active. | None needed for line cards installed in slots 17 through 23 and 26 through 32 after configuration. |
| If green for half-height line cards in slots 33 through 39 and 42 through 48, verify that the corresponding line card installed in the upper-rear chassis slot is installed properly according to the instructions in this document. | ||
| For example, if this LED is green for a line card in slot 33, verify that the line card in slot 17 is installed properly. | ||
| None |
Card is in Ready Mode.
OR
Card is not receiving
power.
OR
Card is in Standby
Mode.
|
This is normal prior to configuration. Neither the Active or the Standby LED on the card is on. |
| Verify that the Run/Fail LED is green. If so, the card is receiving power and POST test results are positive. If it is off, refer to Ethernet Line Card RunFail LED States for troubleshooting information. | ||
| Check the state of the Standby LED. If it is green, the card is in standby mode. This is normal operation for the initial power-up. If needed, refer to the Configuring Packet Processing and Line Card Availability section of System Settings for information on making the card active. |
Ethernet Line Card Standby LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is in redundant mode. | None needed for half-height line cards installed in slots 33 through 39 and 42 through 48 after configuration. |
| If green for line cards installed in slots 17 through 23 and 26 through 32, refer to Monitoring the System for information on determining the status of the line card and system software processes. | ||
| None |
Card is in Ready Mode.
OR
Card is not receiving
power.
OR
Card is in Active Mode.
|
This is normal prior to configuration. Neither the Active nor Standby LEDs on the card is on. |
| Verify that the Run/Fail LED is green. If so, the card is receiving power and POST test results are positive. If it is off, refer to Ethernet Line Card Run/Fail LED States for troubleshooting information. | ||
| Check the state of the Active LED. If it is green, the card is in standby mode. If needed, refer to Manually Initiating a Line Card or SPIO Switchover for information on configuring the card to serve as a redundant component. |
Ethernet Line Card Interface – Link LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Link is up. |
None needed.
NOTE: This
LED will not indicate the presence of a network link until the interface
parameters are set during the software configuration process.
|
| None |
No power is available
to the card.
OR
Link is down.
|
Verify that the Run/Fail LED is green. If so, the card is receiving power. If it is off, refer to Ethernet Line Card RunFail LED States for troubleshooting information. |
| Verify that the interface is cabled properly. | ||
| Verify that the device where the interface is connected to is cabled and powered properly. | ||
| Check the cable for continuity. |
Ethernet Line Card Interface Activity LED States
Checking the LEDs on the RCC
RCC Run/Fail LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card powered with no errors detected. | None needed. |
| Red | Card powered with error(s) detected. | Errors were detected during the Power On Self Tests (POSTs). It is likely that the errors were logged to the command line interface during the boot process. |
| Refer to Monitoring the System for information on determining the status of system hardware components. | ||
| None | Card powered with error(s) detected. | Verify that the POWER LEDs on the PFUs are green. If they are not, refer to Checking the LED on the PFU for troubleshooting information. |
| Verify that the power source is supplying ample voltage and current to the chassis. | ||
| Verify that the card is properly installed per the instructions in the ASR 5000 Installation Guide. | ||
| If all of the above suggestions have been verified, it is possible that the RCC is not functional. Please contact your service representative. |
RCC Active LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is active. | The RCC is actively routing traffic from a line card installed behind a packet processing card that has failed to a redundant packet processing card. |
| The RCC installed in chassis slot 40 processes traffic for the line cards in chassis slots 17 through 23 and 26 through 32. The RCC installed in chassis slot 41 processes traffic for the line cards in slots 33 through 39 and 42 through 48. | ||
| Refer to Checking the LEDs on the Packet Processing Cards to determine which card has failed. | ||
| None |
Card is not receiving power.
OR
Card is in Standby Mode.
|
Verify that the Run/Fail LED is green. If so, the card is receiving power and POST test results are positive. If it is off, refer to RCC RunFail LED States for troubleshooting information. |
| Check the state of the Standby LED. If it is green, the card is in standby mode. This is the normal operating mode. |
RCC Standby LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is in standby mode. |
This is the normal
operating mode.
|
| None |
Card is not receiving power.
OR
Card is in Active Mode.
|
Verify that the Run/Fail LED is green. If so, the card is receiving power and POST test results are positive. If it is off, refer to RCC Run/Fail LED States for troubleshooting information. |
| Check the state of the Active LED. If it is green, the card is in active mode and the RCC is actively routing traffic from a line card installed behind a packet processing card that has failed. | ||
| Refer to Checking the LEDs on the Packet Processing Cards to determine which packet processing card has failed. Information on determining the cause of the failure can be found in Monitoring the System. |
Testing System Alarm Outputs
[local]host_name# test alarm { audible | central-office [ critical | major | minor ] }
Taking Corrective Action
[local]host_name# card smc switchover
[local]host_name# card switch from <24 or 25> to <25 or 24>
You
will receive the following prompt:
Are You Sure? [Yes|No]:
[local]host_name# show card table
Check
the entry in the Oper
State column next to the SMC just switched. Its state
should be Standby.
[local]host_name# card migrate from original_slot# to final_slot#
You
will receive the following prompt:
Are You Sure? [Yes|No]:
For a complete description
of the above command, see the Exec Mode Commands chapter
of the Command line
Interface Reference.
[local]host_name#show card table
Check
the entry in the Oper
State column next to the packet processing card that was just migrated
from. Its state should be Standby. The
state of the packet processing card migrated to should be Active.
[local]host_name# card switch from slot# to slot#
You
will receive the following prompt:
Are You Sure? [Yes|No]:
For a complete description
of the above command, see the Exec Mode Commands chapter
of the Command line
Interface Reference.
[local]host_name# show card table
Check
the entry in the Oper
State column next to the line card or SPIO that was just switched
from. Its state should be Standby. The
state of the line card or SPIO switched to should be Active.Halting Cards
[local]host_name# card halt slot#
slot# is
the chassis slot number in which the card to be halted is installed. It
can be any integer value between 1 and 7, 10 through 48. You
will receive the following prompt:
Are You Sure? [Yes|No]:
[local]host_name# show card table
Check
the entry in the Oper
State column next to the line card that was just halted. Its state
should be Offline. If
the card was in active mode prior to the execution of this command, the
state of the redundant component associated with it should now be Active.
[local]host_name# card reboot slot# -force
You
will receive the following prompt:
Are You Sure? [Yes|No]:
Verifying Network Connectivity
Using the ping or ping6 Command
Syntax
ping host_ipv4_address [ count num_packets ] [ pattern packet_pattern ] [ size octet_count ] [ src { src_host_name | src_host_ipv4_address } ] [ vrf vrf_nam ]
ping6 host_ipv6_address [ count num_packets ] [ flood ][ pattern packet_pattern ] [ size octet_count ] [ src { src_host_name | src_host_ipv6_address } ] [ vrf vrf_nam ]
PING 192.168.250.1 (192.168.250.1): 56
data bytes
64 bytes from 192.168.250.1: icmp_seq=0
ttl=255 time=0.4 ms
64 bytes from 192.168.250.1: icmp_seq=1
ttl=255 time=0.2 ms
64 bytes from 192.168.250.1: icmp_seq=2
ttl=255 time=0.2 ms
64 bytes from 192.168.250.1: icmp_seq=3
ttl=255 time=0.2 ms
64 bytes from 192.168.250.1: icmp_seq=4
ttl=255 time=0.2 ms
--- 192.168.250.1
ping statistics ---
5 packets transmitted, 5
packets received, 0% packet loss
round-trip
min/avg/max = 0.2/0.2/0.4 ms
Using the traceroute or traceroute6 Command
traceroute – IPv4 Syntax
traceroute { host_name | host_ipv4_address } [ count packets ] [ df ] [ maxttl max_ttl ] [ minttl min_ttl ] [ port port_number ] [ size octet_count ] [ src { src_host_name | src_host_ipv4_address } ] [ timeout seconds ] [ vrf vrf_nam ]
traceroute6 – IPv6 Syntax
traceroute6 { host_name | host_ipv6_address } [ count packets ] [ maxttl max_ttl ] [ port port_number ] [ size octet_count ] [ src { src_host_name | src_host_ipv6_address } ] [ timeout seconds ] [ vrf vrf_nam ]
Viewing IP Routes
"*" indicates
the Best or Used route.
Destination Nexthop Protocol
Prec Cost Interface
*0.0.0.0/0 10.0.4.1 static 0 0
SPIO1
*10.0.4.0/24 0.0.0.0 kernel 0 0
SPIO1
*10.0.4.0/32 0.0.0.0 kernel 0 0
SPIO1
*10.0.4.3/32 0.0.0.0 kernel 0 0
SPIO1
*10.0.4.255/32 0.0.0.0 kernel 0 0
SPIO1
Viewing the Address Resolution Protocol Table
IMPORTANT:
Flags codes:
C - Completed, M - Permanent, P - Published, ! - Not answered
T - has requested
trailers
Address Link
Type Link Address Flags Mask
Interface
10.0.4.2 ether 00:05:47:02:20:20
C SPIO1
10.0.4.2 ether 00:05:47:02:03:36
C SPIO1
10.0.4.2 ether 00:01:30:F2:7F:00
C SPIO1
Using the System Diagnostic Utilities
Using the Monitor Utility
[local]host_name# monitor
protocol
An output listing
all the currently available protocols, each with an assigned
number, is displayed.
WARNING!!! You
have selected options that can DISRUPT USER SERVICE
Existing CALLS MAY
BE DROPPED and/or new CALLS MAY FAIL!!!
(Under heavy
call load, some debugging output may not be displayed)
Proceed? - Select (Y)es
or (N)o
C - Control
Events (ON )
D - Data Events (ON )
E - EventID
Info (ON )
H - Disply
ethernet (ON )
I - Inbound
Events (ON )
O - Outbound
Event (ON )
S - Sender
Info (OFF)
T - Timestamps (ON )
X - PDU Hexdump (OFF)
A - PDU Hex/Ascii (OFF)
+/- Verbosity
Level ( 1)
L - Limit
Context (OFF)
M - Match
Newcalls (ON )
R - RADIUS
Dict (no-override)
G - GTPP Dict (no-override)
Y - Multi-Call
Trace ((OFF))
(Q)uit, <ESC>
Prev Menu, <SPACE> Pause, <ENTER>
Re-Display Options
[local]host_name# monitor subscriber { callid | imei | imsi | ipaddr | ipv6addr | msid | msisdn | next-call | pcf | peer-fa | peer-lac | sgsn-address | type | username }
IMPORTANT:
---------------------------------------------------------------------------
Incoming Call:
---------------------------------------------------------------------------
MSID: 0000012345
Callid: 002dc6c2
Username: user2@aaa
SessionType: unknown
Status: Active
Service Name: xxx1
Src Context: source
Dest Context:
---------------------------------------------------------------------------
<<<<OUTBOUND
10:02:35:415 Eventid:25001(0)
PPP Tx PDU (9)
PAP 9: Auth-Ack(1), Msg=
<<<<OUTBOUND
10:02:35:416 Eventid:25001(0)
PPP Tx PDU (14)
IPCP 14: Conf-Req(1), IP-Addr=192.168.250.70
<<<<OUTBOUND
10:02:35:416 Eventid:25001(0)
PPP Tx PDU (27)
CCP 27: Conf-Req(1), MPPC, Stac-LZS, Deflate, MVRCA
INBOUND>>>>> 10:02:35:517 Eventid:25000(0)
PPP Rx PDU (30)
IPCP 30: Conf-Req(1), IP-Comp
VJ-Comp, IP-Addr=0.0.0.0, Pri-DNS=0.0.0.0,
Sec-DNS=0.0.0.0
<<<<OUTBOUND
10:02:35:517 Eventid:25001(0)
PPP Tx PDU (26)
IPCP 26: Conf-Rej(1), IP-Comp
VJ-Comp, Pri-DNS=0.0.0.0, Sec-DNS=0.0.0.0
INBOUND>>>>> 10:02:35:517 Eventid:25000(0)
PPP Rx PDU (12)
IPCP 12: Conf-Ack(1), IP-Addr=192.168.250.70
INBOUND>>>>> 10:02:35:518 Eventid:25000(0)
PPP Rx PDU (31)
LCP 31: Prot-Rej(1), Rejected-Protocol=CCP (0x80fd)
INBOUND>>>>> 10:02:35:518 Eventid:25000(0)
PPP Rx PDU (12)
IPCP 12: Conf-Req(2), IP-Addr=0.0.0.0
<<<<OUTBOUND
10:02:35:518 Eventid:25001(0)
PPP Tx PDU (14)
IPCP 14: Conf-Nak(2), IP-Addr=192.168.250.87
INBOUND>>>>> 10:02:35:519 Eventid:25000(0)
PPP Rx PDU (12)
IPCP 12: Conf-Req(3), IP-Addr=192.168.250.87