Good day...
I am replacing an Samsung IBG-1000 for a customer using an Adtran Netvanta 3200. I have contacted the clients provider (MegaPath | T1) and asked for general support however they do not support the Adtran unfortunately and have referred me to try Adtran.
When the Adtran is connected to the client T1 and when viewing the "System Summary" => "WAN Summary" indicates that the "WAN Interface" is UP.
Likewise when viewing the "WAN Interface Encapsulation" status is indicated as ACTIVE.
Firmware Version: R11.4.4
The Questions
1) When viewing the "System Summary" the WARNING: Warning a potential problem has been detected with your system. Please go this troubleshooting page for more detail.
Layer 2 Protocols Error: Error fr1 is administratively up, but the sub interface, fr 1.500 (VC500), is inactive. Make sure fr1 is up. If the problem persists contact your service provider.
EDIT:
This unit is currently disconnected from the circuit, but here is the return from "show interface".
t1 1/1 is DOWN
Description: fr 1.500
Transmitter is sending remote alarm
Receiver has loss of signal, loss of frame
T1 coding is B8ZS, framing is ESF
Clock source is line, FDL type is ANSI
Line build-out is 0dB
No remote loopbacks, No network loopbacks
Acceptance of remote loopback requests enabled
Tx Alarm Enable: rai
Last clearing of counters 00:49:07
loss of frame : 1, current duration 00:49:07
loss of signal : 1, current duration 00:49:07
AIS alarm : 0
Remote alarm : 0
DS0 Status: 123456789012345678901234
NNNNNNNNNNNNNNNNNNNNNNNN
Status Legend: '-' = DS0 is unallocated
'N' = DS0 is dedicated (nailed)
Line Status: -- LOS -- Red -- Tx Yellow --
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
Current Performance Statistics:
0 Errored Seconds, 0 Bursty Errored Seconds
0 Severely Errored Seconds, 481 Severely Errored Frame Seconds
481 Unavailable Seconds, 0 Path Code Violations
0 Line Code Violations, 0 Controlled Slip Seconds
0 Line Errored Seconds, 0 Degraded Minutes
TDM group 1, line protocol is DOWN
Encapsulation FRAME-RELAY IETF (fr 1)
0 packets input, 0 bytes, 0 no buffer
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame
0 abort, 0 discards, 0 overruns
0 packets output, 0 bytes, 0 underruns
fr 1 is DOWN
Configuration:
Description: fr logical
Signaling type is AUTO, signaling role is USER
Multilink disabled
Polling interval is 10 seconds,
full inquiry interval is 6 polling intervals
Last clearing of "show interface" counters: 00:49:07
Link information:
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
BW 0 Kbps
Queueing method: weighted fair
HDLC tx ring limit: 2
Output queue: 0/0/684/64/0 (size/highest/max total/threshold/drops)
Conversations 0/0/256 (active/max active/max total)
Available Bandwidth 1152 kilobits/sec
0 packets input, 0 bytes
0 pkts discarded, 0 error pkts, 0 unknown protocol pkts
0 packets output, 0 bytes
0 tx pkts discarded, 0 tx error pkts
fr 1.500 is Inactive
Description: fr 1.500
Ip address is 2xx.xxx.xxx.xxx, mask is 255.255.255.0
IP MTU is 1500 bytes
Interface-dlci is 500
BW is 0 Kbps
Average utilization is 0%
Last clearing of "show interface" counters: never
eth 0/1 is UP, line protocol is UP
Description: Local LAN
Hardware address is 00:A0:C8:57:4B:FB
Ip address is 21x.xxx.xxx.xxx, netmask is 255.255.255.0
Secondary IP:
10.0.0.166, 255.255.255.0
IP MTU is 1500 bytes
BW is 100000 Kbit
100Mb/s, full-duplex
ARP type: ARPA; ARP timeout is 20 minutes
Last clearing of "show interface" counters: never
5 minute input rate 1952 bits/sec, 1 packets/sec
5 minute output rate 904 bits/sec, 1 packets/sec
Queueing method: fifo
Output queue: 0/256/0 (size/max total/drops)
Interface Shaper: NOT ENABLED
7498 packets input, 1601705 bytes
6566 unicasts, 932 broadcasts, 0 multicasts input
0 unknown protocol, 0 symbol errors, 0 discards
0 input errors, 0 runts, 0 giants
0 no buffer, 0 overruns, 0 internal receive errors
0 alignment errors, 0 crc errors
7692 packets output, 2892150 bytes
7588 unicasts, 4 broadcasts, 100 multicasts output
0 output errors, 0 deferred, 0 discards
0 single, 0 multiple, 0 late collisions
0 excessive collisions, 0 underruns
0 internal transmit errors, 0 carrier sense errors
0 resets, 0 throttles
What is this error indicating and how would I resolve the situation of "activating" fr 1.500?
2) Is a "loopback" interface required to be added manually or is this created once the device detects an active link?
I appreciate your help and input greatly
The AdTran Support Community is one of the worst excuses for a support community I have seen in a great many years!
Why does AdTran even invest the time to create and host such a useless source for it's users?
Pat
This sounds like the kind of issue that might be best worked through an ADTRAN Technical Support ticket. If the unit is still within its 5 year warranty, feel free to open up a support case on our website. Also, Pat Garner – ADTRAN’s Community Manager will be reaching out to you to get your input as to why the Support Community is falling short of your expectations.
Thanks,
Charles
WOW! Seriously? Only after I make a second post of truth regarding this sites efficacy to its users would a response finally manifest.
Thanks the same Charles, I did resolve this issue on my own within 24 hours my submitting this thread.
I find it very odd that a manufacturers "support community" suffers such poor adminstration for its users, never receiving response for months up until I submitted my response to my own thread.
This "support community" sports a great deal of other users threads which not unlike my own never garner so much as a response, I call that a disservice to Adtran users and furthermore, it will negatively influence Adtran's potential future upgrade sales likewise!
Users expect some form of a reasonably timely response from "someone". Otherwise why should ANY Adtran users waste their time using this community?
Thank you very much for having the fortitude to at least interact Charles.
Have a great day.
The support community is designed for ADTRAN customers to interact and is not a preplacement for our technical support. However, we will improve our responsiveness to posts that go unanswered for a period of time. We trust that future posts will result in a better experience for you as we work to enhance our Customer Community