Line State Colours: Difference between revisions
mNo edit summary |
(Make a few things clearer) |
||
Line 3: | Line 3: | ||
Line colours are based on the last cause code reported by RADIUS which depends on whether the line is on-line or off line and why. |
Line colours are based on the last cause code reported by RADIUS which depends on whether the line is on-line or off line and why. |
||
The cause codes are defined by the standard (RFC2866) and do not always fit all circumstances. |
The cause codes are defined by the standard ([https://tools.ietf.org/html/rfc2866#section-5.10 RFC2866]) and do not always fit all circumstances. |
||
{| class="wikitable" |
{| class="wikitable" |
||
|- |
|- |
||
Line 10: | Line 10: | ||
|- |
|- |
||
|style="background-color: #FFFF00;"|User Request |
|style="background-color: #FFFF00;"|User Request |
||
|PPP restart or termination from far end, or L2TP session close from far end |
|PPP restart or termination from far end, or L2TP session close from far end. This means either that your router ended the PPP session cleanly (e.g.for a reboot), or that the wholesale provider terminated the session as part of maintenance work. Appears as UserRequest in e-mails. |
||
|- |
|- |
||
|style="background-color: #FF0000;"|Lost Carrier |
|style="background-color: #FF0000;"|Lost Carrier |
||
|LCP echo timeout. The session has remained up, but LCP packets aren't getting through - this usually means that the line is down. Appears as LostCarrier in e-mails. |
|||
|LCP echo timeout |
|||
|- |
|- |
||
|style="background-color: #FF00FF;"|Lost Service |
|style="background-color: #FF00FF;"|Lost Service |
||
|L2TP session close with specific message indicating loss of sync |
|L2TP session close with specific message indicating loss of sync. Appears as LostService in e-mails. |
||
|- |
|- |
||
|style="background-color: #FF00FF;"|Idle Timeout |
|style="background-color: #FF00FF;"|Idle Timeout |
||
|Used to indicate a lost session, e.g. NAS crash |
|Used to indicate a lost session, e.g. NAS crash. |
||
|- |
|- |
||
|style="background-color: #FF00FF;"|Session Timeout |
|style="background-color: #FF00FF;"|Session Timeout |
||
Line 64: | Line 64: | ||
|- |
|- |
||
|style="background-color: #FF0088;"|Blocked |
|style="background-color: #FF0088;"|Blocked |
||
|Line is logged in but blocked due to bad password or blocked login |
|Line is logged in but blocked due to bad password or blocked login - check the password in your router, then contact support for help. |
||
|- |
|- |
||
|style="background-color: #FFFFFF;"|Invalid |
|style="background-color: #FFFFFF;"|Invalid |
Revision as of 09:20, 17 Mayıs 2017
Line colours are based on the last cause code reported by RADIUS which depends on whether the line is on-line or off line and why.
The cause codes are defined by the standard (RFC2866) and do not always fit all circumstances.
Logged in | Line is logged in, no error |
User Request | PPP restart or termination from far end, or L2TP session close from far end. This means either that your router ended the PPP session cleanly (e.g.for a reboot), or that the wholesale provider terminated the session as part of maintenance work. Appears as UserRequest in e-mails. |
Lost Carrier | LCP echo timeout. The session has remained up, but LCP packets aren't getting through - this usually means that the line is down. Appears as LostCarrier in e-mails. |
Lost Service | L2TP session close with specific message indicating loss of sync. Appears as LostService in e-mails. |
Idle Timeout | Used to indicate a lost session, e.g. NAS crash. |
Session Timeout | Session timeout reached (normally after one hour on a blocked login) |
Admin Reset | Manual or remote session or tunnel termination |
Admin Reboot | LNS reboot or other RADIUS accounting issue |
Port Error | L2TP relay failure, or L2TP tunnel level close |
NAS Error | Any unknown internal error in LNS including no negotiation slots (too busy) |
NAS Request | Session steering (directed to different LNS) |
NAS Reboot | Not used |
Port Unneeded | Try another response on RADIUS (steering) |
Port Pre-empted | Same login twice. As login is based on circuit ID this is not normally seen. |
Port Suspended | Line dropped because of an attack |
Service Unavailable | RADIUS timeout |
Callback | Not used |
User Error | Any sort of PPP negotiation failure, or an authentication failure and also some L2TP negotiation errors |
Host Request | Not used |
Blocked | Line is logged in but blocked due to bad password or blocked login - check the password in your router, then contact support for help. |
Invalid | Line not valid (not installed, or is ceased) |