Urgent help with LattisHub 2814SA wanted !!!
DComTalk.com Forum Index DComTalk.com
Discussion of VoIP, VPN, Video Conferencen, DSL and other data commucations.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web dcomtalk.com
Urgent help with LattisHub 2814SA wanted !!!

 
Post new topic   Reply to topic    DComTalk.com Forum Index -> Bay Networks
Author Message
Wojciech Galazka
Guest





Posted: Sun Dec 19, 2004 1:42 am    Post subject: Urgent help with LattisHub 2814SA wanted !!! Reply with quote

Hello,

I've just got a used LattisHub 2814SA. When I power on the hub the system operation first displays . some words and the green uP fail led lights on. Finally the system operation comes to displaying BOOT message, at this time the uP led is off. The hub seems to stal then l. Moverover no 10BaseT port is operational. The power on led lights on but the on-line green led blinks. No other led is on.

I removed the cover plate to see what's inside the box. Two square chips denoted u39 and u40 are missing, well I'm not sure if they have to be present. One big SIMM is present.
I tried connecting a serial cable to the service port and a serial terminal (actually hyperterm under Windows) to see if there are any messages coming from the hub while it is powered on. Nothing showed up, though. This is a null modem cable and it's fine since I used it in past to connect to a Sun machined and it worked well.

My questions are:
is this hub broken or it just waits silently for something to happen?
why cannot I see anything from the service port?
why the heck the on-line led blinks instead of just steadily light on?

If I am not able to cope with this hub by next three weeks I'm going to put it in a trash. I was considering this today, actually, but when the cover has been removed a nice piece of electronic stuff saw I inside so I'm going to give this hub a try once more.

If you have such a beast and could give any piece of advice please do! I was not able to find any docs on the net (Nortel no more has any info on this) and I have no idea whatsoever what to do .... Thanks
Back to top
Walter Roberson
Guest





Posted: Sun Dec 19, 2004 2:06 am    Post subject: Re: Urgent help with LattisHub 2814SA wanted !!! Reply with quote

In article <cq24rb$b3d$1@achot.icm.edu.pl>,
Wojciech Galazka <wojciech.galazka@polkomtel.com.pl> wrote:
:I've just got a used LattisHub 2814SA.

:I tried connecting a serial cable to the service port and a serial =
:terminal (actually hyperterm under Windows)

Hyperterm is usually a mistake when trying to talk to older
devices, due to hyperterm's cruft when it comes to sending BREAK
signals.

:to see if there are any
:messages coming from the hub while it is powered on. Nothing showed up,
:though. This is a null modem cable and it's fine since I used it in past
:to connect to a Sun machined and it worked well.

You need a straight through, not a null modem cable.
--
Take care in opening this message: My grasp on reality may have shaken
loose during transmission!
Back to top
Wojciech Galazka
Guest





Posted: Sun Dec 19, 2004 6:11 pm    Post subject: Re: Urgent help with LattisHub 2814SA wanted !!! (some succe Reply with quote

Hello again,
So far I went up to the point where I can see messages flowing out from the service port right into the serial terminal. My previous suspicions that the hub was stalled were correct, I figured out it was trying to read either an image or a config file off the net. I decided to set everything up to be read locally (LOCAL) then reset the hub.
Now the 'on-line' led lights out in plain green, not blinking anymore, one more led labelled 'in' lights out
The funny part is that the 'system operation' display shows something like '<| /' with the '/' spinning out. To me it seems the hub is trying to connect to a bootp server using tftp to grasp the so called config.file or the like. 10baseT ports except the one leftmost still don't work, when connected to another computer.

My understanding is that ithe hardware part and the built-in software works fine (all internal checks passed ok). The next step presumably is to create a config file and place it on a bootp server. Is this right assumption? If so then this is real bad news as without any docs I have no clue how the config file should look like ....
Back to top
Walter Roberson
Guest





Posted: Sun Dec 19, 2004 9:45 pm    Post subject: Re: Urgent help with LattisHub 2814SA wanted !!! (some succe Reply with quote

In article <cq3up8$ugv$1@achot.icm.edu.pl>,
Wojciech Galazka <wojciech.galazka@polkomtel.com.pl> wrote:
:The next step presumably is =
:to create a config file and place it on a bootp server. Is this right
:assumption? If so then this is real bad news as without any docs I have
:no clue how the config file should look like ....

The 28115 documentation should be reasonably close. Here's a copy
of the bootp file that I used to use for one of the 28115.
I had it named 281sa200.cfg but I'm not sure that the name is
important, as the name would be served up in response to the bootp
request. You can see in the comments a number of references to 281x.

Note: each of the below lines ended in carriage return line feed
as in the standard DOS text file format. That's probably important.


# Specify file name for the NMM image file. NOTE this has to be
# the first un-commented line in this file for the NMM to load properly.
# For example:
281sa200.img
#
# Assign local subnet mask for this NMM.
# Default for Class A NMM IP Address is 255.0.0.0.
# Default for Class B NMM IP Address is 255.255.0.0.
# Default for Class C NMM IP Address is 255.255.255.0.
# For example:
#netmask 255.255.255.0
#
# Specify the primary default router for this NMM.
#default-router xxx.xxx.xxx.xxx
# For example:
#default-router 0.0.0.0
#
# Specify the secondary default router for this NMM.
#secondary-default-router xxx.xxx.xxx.xxx
#
# Specify the router address for this NMM's TFTP request.
#boot-router xxx.xxx.xxx.xxx
#
# Enable or disable the automatic discovery of available default
# router(s). Valid entries are on and off. Default is on.
# For example:
#ping-router on
#
# Specify the time interval of pinging router(s) in seconds.
# Maximum number is 42,949,672 seconds. (approximate 497 days)
# Default/ minimum time is:
#ping-time 60
#
# Specify the Novell network number for this NMM. Must be exactly
# eight hexadecimal digits.
#network-number 00000000
#
# Indicate baud rate used for the RS-232 out-of-band port. Valid entries are
# 300, 1200, 2400, 4800 and 9600 baud.
# Default is:
#baud-rate 9600
#
# Enter the NMM's initialization string used for out-of-band communication.
# For example:
#initialization-string ATDT,9,1,415-555-1212
#
# Specify the concentrator's location (64 characters max.).
# For example:
#location Building A
#
# Specify the concentrator's name (64 characters max.).
# The default string is SYNOPTxxyyzz, where xxyyzz represents the
# last 3 bytes of this NMM's hexadecimal MAC address.
# For example:
#sysname concA.abcCompany.com
#
# Specify the name & phone number of the concentrator's administrator
# or contact person (64 characters max.).
# For example:
#syscontact John Smith - Network Administrator - ext 5555
#
# Specify the community string used for read only operations. Specifying
# no community string will default to public for read only objects.
# For example:
#read-community public
#
# Specify the community string used for read and write operations.
# Specifying no community string will default to private for read and
# writable objects.
# For example:
#write-community private
#
# Enter the list of IP trap receivers along with their community strings
# and ageout times, in seconds. The maximum number is 42,949,672 seconds
# (approx 497 days). Specifying no ageout time defaults to indefinite time.
# Specify only one entry pair per line, up to a maximum of 10 entries.
# For example:
#ip-trap-receiver xxx.xxx.xxx.xxx trap-community public 9000
#
# Enter the list of IPX trap receivers along with their community strings
# and ageout times, in seconds. The maximum number is 42,949,672 seconds
# (approx 497 days). Specifying no ageout time defaults to indefinite time.
# Specify only one entry pair per line, up to a maximum of 10 entries.
# Entry format is:
# <Novell network #>:<Novell Host #> trap-community <community string> <ageout time>
# Note that <Novell network #> contains 8 hexadecimal numbers and <Novell Host #>
# contains 12 hexadecimal numbers.
# For example:
#ipx-trap-receiver abcdefab:123456789012 trap-community public 9000
#
# Enable or disable the use of authentication traps. Valid entries are
# on and off. Default is on.
# For example:
#authentication-traps on
#
# Enable or disable concentrator retiming.
# Valid entries are on and off. Default is on.
# The 281xSA NMM does not have this keyword.
# For example:
#retiming on
#
# Specify the image load mode for this NMM. Valid choices are
# remote-only, local-only or remote-with-local-backup.
# For example:
#image-load-mode remote-only
#
# Specify the config load mode for this NMM. Valid choices are
# remote-only, local-only or remote-with-local-backup.
# For example:
#config-load-mode remote-only
#
# Specify the boot mode for this NMM. network configures the
# NMM to use the network for remote loading of the NMM's
# configuration information. eeprom configures the NMM to use
# data stored in NVRAM for local loading. Default is eeprom.
# For example:
#boot-mode eeprom
#
# Specify the management protocol for this NMM. Valid choices are
# IP_IPX, IP, and IPX. Default is IP_IPX.
# For example:
#management-protocol IP_IPX
#
# Specify the boot protocol for this NMM. Valid choices are
# AUTO, IP, IPX, and IP_IPX. Default is AUTO.
# For example:
#boot-protocol AUTO
#
# Save configuration data to NVRAM.
#save-to-eeprom
#
# Specify time interval of traps sent out for existing predefined
# conditions. The valid range is 10 to 3600 seconds, in 10 second
# increments. Default is 10 seconds.
# for example:
#trap-interval 10
#
# Specify the lifetime of a node list entry in seconds.
# Maximum number is 42,949,672 seconds (approximate 497 days).
# Default is 900 seconds.
# For example:
#portlife 900
#
# Specify the lifetime of a traffic matrix entry in seconds.
# Maximum number is 42,949,672 seconds (approximate 497 days).
# Default is 1200 seconds.
# For example:
#trflife 1200
#
# Specify how many nodes are allowed to associate with a particular port.
# Default is 800 for 281xSA and 331xSA.
# For example:
#max-nodes-per-port 800
#
# Specify allowed nodes for this NMM. Specify only one entry per line.
# The format is:
# node AABBCCDDEEFF slot# port#
# Where AABBCCDDEEFF is the hexidecimal MAC address with 12 hex digits.
# slot# and port# are decimal numbers.
# For example:
#node 013489ABCDEF 1 6
#node abcdef987654 2 5
#node 000081111111 2 6
#node 000082222222 2 7
#node 000083333333 2 8
#
# "Wild card" notation:
# If slot# or port# is either 0 or blank, that entry will be treated
# as a wild card.
# For example, this wild card entry specifies all ports associated
# with the concentrator:
#node 1234567890ab
# This wild card entry also specifies all ports associated
# with the concentrator:
#node 1234567890ab 0 0
# This wild card entry specifies all ports associated with slot 5
# in this concentrator:
#node 234567890abc 5 0
#
# Enable allowed nodes and set the security level to be used
# when the system is up. Security can be set at either concentrator,
# slot, or port level. System default is OFF for allowed nodes
# features; to enable allowed nodes, uncomment the appropriate line.
# For example:
#allow-on conc
#allow-on slot
#allow-on port
#
# Specify the action to be taken when a node security violation occurs.
# Actions can be specified for violations at the port, slot, or concentrator
# level. Format are
# port slot# port# action#
# slot slot# action#
# conc action#
# Where slot#, port#, action# are all decimal numbers.
# For action#, valid choices are 2, 3, 4, or 5.
# 2 = no_action;
# 3 = send_trap_only;
# 4 = partition_port_only;
# 5 = send_trap_and_partition_port;
#
# This port-level example is used to check slot 5, port 11.
# If address violation occurs, send trap only.
#port 5 11 3
# This port-level example is used to check slot 4, port 12.
# If address violation occurs, do nothing.
#port 4 12 2
# This port-level example is used to check slot 2, port 3.
# If address violation occurs, send trap and partition port.
#port 2 3 5
#
# This slot-level example is used to check slot 5 and
# partition that port if address violation occurs.
#slot 5 4
# This slot-level example is used to check slot 3 and
# send trap and partition that port if address violation occurs.
#slot 3 5
#
# This concentrator-level example is used to check
# entire concentrator. If address violation occurs,
# send a trap and partition the port to which the concentrator
# is connected.
#conc 5
#
# Specify MAC address auto-learn mode for a LattisSecure port.
# one-shot-auto-learn configures the LattisSecure port to learn
# the first MAC address pass through this port. continuous-auto-learn
# configures the LattisSecure port to continuously learn the MAC
# address pass through this port.
# LattisSecure is not supported by 281xSA.
# The format is:
# learn-mode slot# port# auto-learn-mode
# Where slot# and port# are decimal numbers.
# Default is no auto-learn for all ports in LattisSecure module.
# For example:
#learn-mode 6 1 one-shot-auto-learn
#
# Enable or disable eavesdropping protection for a LattisSecure port.
# Format of the command:
# eavesdropping-protection slot# port# <on | off>
# Where slot# and port# are decimal numbers.
# Default is off for all ports in LattisSecure module.
# LattisSecure is not supported by 281xSA.
# For example:
#eavesdropping-protection 6 12 off
#
# Lock/Unlock security configuration. Valid entries are on and off.
# Default is off.
# For example:
#security-config-lock off
#
# Add an entry to the threshold table.
# Format of the command:
# threshold IN OB SL PO TY CN SV AC DU
# IN = index, for 331xSA from 1 to 288, inclusive
# for 281xSA from 1 to 160, inclusive
# OB = object, which is one of the following:
# conc Threshold is set for a concentrator
# slot Threshold is set for a slot
# port Threshold is set for a port
# SL = slot number, for 3000 concentrator from 1 to 12, inclusive
# for 3030 concentrator from 1 to 4, inclusive
# for 281xSA concentrator from 1 to 5, inclusive
# PO = port number, for 3000/3030 concentrator from 1 to 24, inclusive
# for 281xSA concentrator from 1 to 17, inclusive
# TY = type, which is one of the following:
# good-bytes
# good-packets
# bad-packets
# crc-error-packets
# misaligned-packets
# runt-packets
# fragments
# too-long-packets
# collisions
# late-collisions
# link-status
# multicast-packets
# broadcast-packets
# short-events
# source-address-changes
# data-rate-mismatches
# network-errors
# backoff-errors
# bad-to-good-packets-ratio
# network-errors-to-good-packets-ratio
# collisions-to-good-packets-ratio
# CN = condition, which is one of the following, depending on TY:
# cross Trigger alarm when actual-value crosses set-value
# over Trigger alarm when actual-value is greater than set-value
# over-rate Trigger alarm when actual-value/second is greater than
# set-value/second
# link-on Trigger alarm when port link status is on
# link-off Trigger alarm when port link status is off
# over-ratio Trigger alarm when actual-value (ratio type only) is
# greater than set-value
# SV = set value, which can be an absolute number or a rate per second
# AC = action, which is one of the following:
# trap-only Send trap only
# partition-slot Partition a slot, specified by SL
# partition-port Partition a port, specified by SL and PO
# trap-partition-slot Send trap and partition a slot, specified by SL
# trap-partition-port Send trap and partition a port, specified by SL
# and PO
# DU = Duration in seconds of period during which threshold is monitored
#
# Sample threshold table entries:
# This sample threshold table entry is number 6 in the table.
# It counts CRC error packets for a concentrator. When the number
# of CRC errors in 10 second goes over 1000, it sends a trap.
#threshold 6 conc 0 0 crc-error-packets over 1000 trap-only 10
#
# This sample threshold entry is number 2 in the table.
# It checks slot 3 for 200 good bytes in 10 seconds. When the counter
# crosses 200, it sends a trap and partitions the slot.
#threshold 2 slot 3 0 good-bytes cross 200 trap-partition-slot 10
#
# Enable or disable automatic network topology build-up.
# Valid entries are on and off. Default is on.
# For example:
#hello-message on
#
############### TRAP ENABLE/DISABLE #########################
#
# To selectively enable or disable individual trap PDUs generated
# by the platform, uncomment out the line and indicate
# "enable" or "disable" for the indicated traps.
#
# Example:
# Trap_Snmp_coldStart enable #enable SNMP cold start traps
# Trap_Snmp_coldStart disable # disable SNMP cold start traps
#
#
# Trap_Chassis_boardSwap enable
# Trap_Chassis_boardLEDFailure enable
# Trap_Chassis_flashUpdateFailure enable
# Trap_Chassis_chassisPowerSupplyFailure enable
# Trap_Chassis_chassisFanFailure enable
# Trap_Chassis_boardPowerSupplyFailure enable
# Trap_Chassis_redPsPlus5vCurrentExceed enable
# Trap_Chassis_redPsPlus12vCurrentExceed enable
# Trap_Chassis_redPsAmbientTempStatChg enable
# Trap_Chassis_redPsSummingDiodeFailure enable
# Trap_Snmp_coldStart enable
# Trap_Snmp_authenticatedFailure enable
# Trap_Rmon_risingAlarm enable
# Trap_Rmon_fallingAlarm enable
# Trap_Enet_portAutoPartition enable
# Trap_Enet_portDTEJabbering enable
# Trap_Enet_rptrHealth enable
# Trap_Enet_rptrGroupChange enable
# Trap_Enet_enetThreshExceeded enable
# Trap_Enet_nmmSaturationA enable
# Trap_Enet_redunBadRemCfgDetected enable
# Trap_Enet_enetChannelChange enable
# Trap_Enet_redundPortSwitchover enable
# Trap_Enet_remoteBrigdePortOperationDiagnostic enable
# Trap_Enet_remoteBrigdeDiagnostic enable
# Trap_Enet_remoteBrigdeOperationChanged enable
# Trap_Enet_localBrigdeOperationChanged enable
# Trap_Enet_localBrigdeDiagnostic enable
######## 2k/3k Ethernet Router Traps
# Trap_Enet_routerOperationChanged enable
# Trap_Enet_routerDiagnostic enable
######## 2k/3k Ethernet Platform Trap
# Trap_Enet_AuthorizationViolation enable
# Trap_Enet_LattisSecureInitRequired enable
#
# Specify the maximum number of hosts will be collected on an interface
# on behalf of each RMON hostControlEntry. The valid range is
# [100, 2048]. Default is 100.
# For example:
#rmon-max-host 100
#
# If this keyword is present, the agent will automatically setup RMON host
# control entries for all interface(s) present on the NMM at system startup
# time. This keyword does not require any parameter. Default is off.
rmon-dflt-host
#
# If this keyword is present, the agent will automatically setup RMON matrix
# control entries for all interface(s) present on the NMM at system startup
# time. This keyword does not require any parameter. Default is off.
rmon-dflt-matrix
RMONMaxHost 500
RMON2_MaxConversations 1000
RMON2_MaxHosts 1000
RMON1_MaxConversations 100
RMON1_MaxHosts 100
RMON1_CreateHostAtStartup
RMON1_CreateMatrixAtStartup
RMON2_CreateMatrixAtStartup
RMON2_CreateHostAtStartup

#------------ The following Section is for 281xSA only ---------
#
# Configure the Software Redundant Links
#
# Basic format is
#
# 2k-sw-red ActiveSlot ActivePort StandbySlot StandbyPort
#
# Maximum number of Software Redundant Links that may be set up is 4
#
# When link-based redundant links are specified in this config file, it may
# be done in one or multiple lines. However, if multiple lines are used,
# every new line must start with the key word "2k-sw-red". A redundant
# pair may also not be split into different lines; it must be defined
# completely in the same line.
#
# Legal examples are:
# 2k-sw-red 1 2 3 4-one pair in one line
# 2k-sw-red 1 2 3 4 2 1 4 3 - two pairs in one line
# 2k-sw-red 1 2 3 4 2 1 4 3 5 1 5 6 4 4 4 17- four pairs in one line
#
# 2k-sw-red 1 2 3 4- three pairs in two lines
# 2k-sw-red 1 2 3 4 2 1 4 3
#
# 2k-sw-red 1 2 3 4 -
# 2k-sw-red 2 1 4 3 - three pairs in 3 lines
# 2k-sw-red 5 1 5 6
--
I've been working on a kernel
All the livelong night.
I've been working on a kernel
And it still won't work quite right. -- J. Benson & J. Doll
Back to top
 
Post new topic   Reply to topic    DComTalk.com Forum Index -> Bay Networks All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




VoIP Solutions: Telephone Systems Electronics Satellite TV Tech & Gadgets
Powered by phpBB