Naviscore NMS for Lucent Switch Problem

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Naviscore NMS for Lucent Switch Problem
# 1  
Old 08-20-2009
Naviscore NMS for Lucent Switch Problem

We have a network of Lucent BSTDX9000 switches for fiber and wireless links in the United States and Costa Rica. I was dragging a BSTDX9000 icon in my Naviscore NMS and it disappeared.
All of my trunks are still up but I can't figure out how to get the icon back. I'm screwed if something happens in that switch and I can't get into it.
If you or somebody you know can help, it would be greatly appreciated
I'm willing to pay whatever it takes and we can set someone up to remotely log in.
You can also contact me on my cell. 602-370-9750

Thanks, Scott
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. SuSE

SLES 11 Switch user problem

Hi, I am using SUSE Linux Enterprise Server 11 (x86_64), PATCHLEVEL = 0 as NIS server. All client is having SUSE Linux Enterprise Desktop 11 (x86_64), PATCHLEVEL = 0. All system are configured to work in GUI. When NIS user say 'a' locks system, and user 'b' wants to login to the same system... (1 Reply)
Discussion started by: sachingujrathi
1 Replies

2. Shell Programming and Scripting

how to access console of a switch having rj45 on switch side to db 9 female on pc side console cable

hi, how to access console of a switch having rj45 on switch side to db 9 female on pc side console cable which needs to be connected to one console server having rj11 on its side and db 9 female on other end.i.e. on switch side,console cable has rj45 and db 9 pin female connector on other side of... (1 Reply)
Discussion started by: pankajd
1 Replies

3. Shell Programming and Scripting

need help for cp with -p switch

Guys, I need to copy files from source to destination with datetime preserved I did it with cp -p <source>/file <destinaltion>/file But when I do stat command on copied file , it seems the copied file has "change time" modified. Please guide me in understanding (2 Replies)
Discussion started by: mohan_xunil
2 Replies

4. Solaris

Naviscore NMS Problem...Need Help, Will Pay good

We have a network of Lucent BSTDX9000 switches for fiber and wireless links in the United States and Costa Rica. I was dragging a BSTDX9000 switch icon in my Naviscore NMS and it disappeared. All of my trunks and circuits are still fuctioning properly but I can't figure out how to get the icon... (3 Replies)
Discussion started by: phxteleport
3 Replies

5. IP Networking

Open Source NMS

Hello there, I wanted to know the members' opinion about the best open source network management software which uses a web browser to show its interface and results. I am interested in the software for both windows and Linux OSs. Thanks. (4 Replies)
Discussion started by: Jawwad
4 Replies

6. UNIX for Advanced & Expert Users

Lucent/Orinoco Wireless card problems

Im running mandrake 9.0 and i just got a Lucent/orinoco PC24E-H-FC. I beleive it was originaly made by lucent but then made by Orinoco.. But anyways i just cant get connected. Ive tried 3 differemt drivers. My wireless access point router is a Linksys. I just cant figure this out ive talked on... (3 Replies)
Discussion started by: jason1234
3 Replies

7. Shell Programming and Scripting

can you switch

hi, i am try to run following script in c-shell, using switch command. #!/bin/csh choice=0 while do echo "system monitor" echo " 1) system paging 2) system file inf. 3) system disk inf. 9) exit " echo "select an option: \c" read choice case $choice in 1)... (3 Replies)
Discussion started by: neer45
3 Replies
Login or Register to Ask a Question
snmpd.conf(5n)															    snmpd.conf(5n)

Name
       snmpd.conf - Simple Network Management Protocol (SNMP) daemon configuration file

Description
       The file is a configuration file that contains information used by the daemon to define the static variables whose values are not available
       in the kernel.  It is created for you when you run the command, or you can create it manually.  The system or network  manager  is  usually
       responsible for maintaining it.

       The following are the file variables and their significance:

       sysDescr ID-string
	    The variable describes the host.  The ID-string is the value of the variable The default entry is of the form:

	    hostname:machine-type:software id

	    For example, the entry for a MicroVAX II named that is running ULTRIX Version 4.0 might read:
	    sysDescr  host1:MicroVAXII:ULTRIX V4.0 (Rev 64) System #2

       interface speed name speed
	    The variable describes a value for the Management Information Base (MIB) variable defined as:

	    The  name  parameter must be an ULTRIX interface name, such as sl0.  The following interfaces have default interface speeds and types:
	    de, qe, ni, ln, se, scs, xna.  If your system has one of these interfaces, you do not need to specify this parameter.

	    The speed parameter is a decimal number that describes the speed of the link in bits per second.  If you  do  not  specify	the  speed
	    parameter, does not return this variable and marks it as unavailable.

       interface type name type
	    The variable describes a value for the MIB variable in the interface table defined as:

	    The name parameter must be an ULTRIX interface name, such as sl0.

	    See  the sample file in the Examples section for a complete listing of the possible type specifications.  If the type parameter is not
	    specified, marks it as unavailable.

       tcpRtoAlgorithm algorithm-type
	    The variable describes a value for the MIB variable in the tcp group defined as This  variable  defines  the  Retransmission  Time-Out
	    (RTO) algorithm your system uses.

	    The  algorithm-type parameter is a numeric code that represents the type of RTO algorithm you are using.  The default algorithm is Van
	    Jacobson's, which is algorithm number 4.  See the sample file in the Examples section for a listing of the other algorithms.

	    If you do not specify this parameter, does not return this variable, and marks it as unavailable.

       community name IP-address type
	    The variable describes an SNMP community for the agent.

	    The name parameter is a string that describes the name of the community.

	    The IP-address parameter is the dot-notation Internet Protocol (IP) address for the  server.   Only  SNMP  packets	coming	from  that
	    address are accepted.  If you specify 0.0.0.0 in the address field, the SNMP agent honors the request from any Network Management Sta-
	    tion (NMS) having the name community.

	    The type parameter can be one of the following:

	    read-only
	    Permits only monitoring of variables.

	    read-write
	    Permits both monitoring and setting of variables.

	    traps
	    Generates traps when appropriate and sends them to the specified address with the specified community name.

	    The possible traps currently generated are cold start and authentication failure.

	    If you do not specify any community, uses the default community with an address 0.0.0.0 and a read-only type.  Invalid uses of  commu-
	    nities  are  logged with the command.  To limit the use of a community to a finite group of machines, specify another community clause
	    with the same community parameter name and a different address.

       timeout value
	    The variable indicates the timeout value in seconds between the Agent and the Extended  Agent.   If  the  Agent  does  not	receive  a
	    response within the allotted time, it returns an error message to the NMS.	The default timeout value is 5 seconds.

       extension extended-agent p1 p2 p3 p4
	    The variable lists the pathname of the extended-agent that the Agent activates.

	    Variables  p1  through  p4	are  passed by the Agent to the Extended Agent; p1 is usually the process name to be given to the Extended
	    Agent.

Examples
       The default file contains only the following entry:
       community public 0.0.0.0    read-only
       The following is an example of an extensive file:
       #
       #    snmpd.conf file
       #
       sysDescr        host1:MicroVAXII:ULTRIX V4.0 System #2

       #
       #  Describe the TCP RTO algorithm you are using.  Values
       #  are listed in RFC 1066, under the TCP group variable:
       #  tcpRtoAlgorithm
       #  They are:
       #
       #  other(1)	-- None of the below
       #  constant(2)	-- constant RTO
       #  rsre(3)	-- MILSTD 1778, appendix B
       #  vanj(4)	-- Van Jacobson's algorithm
       #
       tcprtoalgorithm	   4

       #
       #  Describe who can use your SNMP daemon by
       #  defining "communities".    USAGE:
       #
       #  community <name><IP address><type>
       #
       #  This is a limited-use community; a finite number of
       #  hosts can use it.
       #  Can only query from this community.
       #
       community test1	   128.45.10.100 read-only
       community test1	   128.45.10.101 read-only

       #
       #  These are our wide-open, general-use communities.  Specifying
       #  0.0.0.0 means that any address can use this community only
       #  to monitor variables.
       #
       community public 0.0.0.0 read-only

       #
       #  This is our only management community.  You can set variables
       #  as well as monitor variables with this community.  It is a
       #  wide-open community as well.
       #
       community testwrite 0.0.0.0 read-write

       #
       #  This is a trap community.  We send traps to these addresses
       #  all from the same community name.  Note that a 0.0.0.0
       #  address in a trap session is illegal and snmpd will ignore
       #  that community definition.
       #
       community trap1	   128.45.10.100 traps
       community trap1	   128.45.10.101 traps

       #
       #  The interface speed is given in bits/sec.  USAGE:
       #
       #  interface speed <name> <speed>
       #
       interface speed sl0 9600

       #
       #  The <name> parameter for the interface type is the
       #  same as the <name> for the interface speed, sl0 for
       #  this example.  USAGE:
       #
       #  interface type <name> <type>
       #
       #  The code number for the proper interface hardware type
       #  is specified in RFC 1066 under the ifType object
       #  definition.
       #
       #  Some possible values:
       #
       #  other(1)
       #  regular1822(2)
       #  hdh1822(3)
       #  ddn-x25(4)
       #  rfc877-x25(5)
       #  ethernet-csmacd(6)
       #  iso88023-csmacd(7)
       #  iso88024-tokenBus(8)
       #  iso88025-tokenRing(9)
       #  iso88026-man(10)
       #  starLan(11)
       #  Proteon-10MBit(12)
       #  Proteon-80MBit(13)
       #  hyperchannel(14)
       #  fddi(15)
       #  lapb(16)
       #  sdlc(17)
       #  t1-carrier(18)
       #  cept(19) -- European equivalent of T-1
       #  basicIsdn(20)
       #  primaryIsdn(21)
       #  propPointToPointSerial(22) -- proprietary serial
       #
       interface type  sl0 1

       #
       # Timer value to time out requests to extended agents.
       #
       timeout	 6

       #
       # List of extended agents.
       #
       extension /etc/snmpextd	     snmpextd

       In this example, note the following:

       o  Community can be monitored by either 128.45.10.100 or 128.45.10.101.

       o  Community can be monitored by any NMS.

       o  Community can be monitored and managed by any NMS.

       o  When a trap is generated, it is sent to community at 128.45.10.100 or 128.45.10.101.	Destination addresses must  have  a  mechanism	in
       place to handle the traps.

See Also
       snmpext(3n), snmpd(8n), snmpsetup(8n)
       RFC 1066--Management Information Base for Network Management of TCP/IP- based Internets
       RFC 1067--A Simple Network Management Protocol
       Guide to Networking

																    snmpd.conf(5n)