Sniffer Pro ATMbook

[Elca]

Hi, all

I can't setup ip address in ATMbook like below:
>> si 10.0.0.3
S_errno_ENXIO
ip address could not be set
Updating system configuration...
Erasing Flash Section 86...

I think that Xircom NIC couldn't be bind with ATMbook.
Has anyone seen anything like this before or have any suggestions?
Anxiously waiting to hear from you..It's on Emergency!

- Elca

And here are booting process when power on,
Any key to abort LED Test:


Autoboot in 5 seconds (CTRL-A to abort)......

Using bootString from block #0

bootString: dc(0,0)nohost:/nodir/nofile h=193.1.188.01 u=lt pw=lt tn=noname e=10

0.0.3:ffffff00 f=0x2000

Using IP from NvRam

Using IP:mask 10.0.0.4:ffffff00

Attaching network interface dc0... No Such DC, unit #0

failed: errno = 0xd0003.


Adding 6071 symbols for standalone.

CellTracer ATM Analysis and Test Platform


Copyright Visual Networks Inc., 1994-1999

Copyright Wind River Systems, Inc., 1984-1997


Serial number: A610960001D2000111117

CPU Mem=32M, Capture1 Mem=32M, Capture2 Mem=32M

Installed Phy: Dual STS-12C MM Fiber


Tinker CPU #1, HW Rev: 0.00

Firmware DEBUG: 4.1.00.20, Date: Aug 14 2000


Bind failed


WDB: Ready.


Running cbStartup...


Starting CellBlaster application module built -> Jul 26 2000.

Phy Configuration:

Phy HW Revision (0), Framers (2)

Framing (Channel One), Media (Multi Mode Fiber)

Tx Ref Clock: Onboard reference

Signal Present: Not on Chan 1, Not on Chan 2

Operational Mode: [10] Monitor Mode, Dual Capture

Loading Flyby B

Loading Flyby A

Loading Maker #0, RcvAll_12

Loading Maker #1, RcvAll_12


System initialization complete

Starting task: hcp...

Starting task: watchdog...

Starting task: tCelld...

Starting task: tCbrsrvd...

Starting task: ngcControlTask...

Starting task: ngcOpenCloseTask...

Task initialization complete

Final initialization complete

cbrsd(): can't bind S_errno_ENXIO

Network Associates, Inc.: ATM Book Firmware: Control Task Started

OpenClose: Task Started


CellTracer Command Line Interface


Type "help" or "?" for brief command descriptions


>> Framer Type 8

Initializing Phys Cfg

Loading Flyby B

Loading Flyby A

Loading Maker #0, RcvFB_12

Loading Maker #1, RcvFB_12

Start Receive time is 808





Copyright (C) 1998 - 2000 Network Associates. All rights reserved.



Network Associates, Inc.: Sniffer Version = 4.0.06

Network Associates, Inc.: Firmware Build Time: 10:30:14

Network Associates, Inc.: Firmware Build Date: Aug 14 2000

 

[Guest_imported]

RMA the unit with Technical Support, the firmware is probably hosed. It may be possible to reflash the firmware through the serial port (console), but such operations are quite tedious. I had this happen to a customer ATMBook that I recently upgraded (the Ethernet card was no longer recognized by the ATMBook). Easiest solution is to call support and RMA the unit.

ciao
Jeff Fanelli
Sniffer SE - Detroit MI

 

[AlexTovar]

Hi ATM users ?

I know is a little late to ask this, but can you tell me how this worked out ? I have an ATMbook with the same problem !! Can upgrade be performed via serial interface ?

Thanks in advance !

Alex Tovar
Sniffer SE Mexico.

 

[levelnet]

Was there a solution for this apparent 'Ethernet dc0 failed to bind' issue? I've recently acquired an ATMBook and I get the same message. I don't have prime NAI support (or any support) so RMA'ing the unit to NAI is out of the question. I was anxious to see if reflashing/upgrading the ATMbook firmware was an alternative solution, before I toss the ATMbook in the dumpster. Any assistance appreciated in advance.

 

[AZeemeri]

The KEY is that when the ATM Book powers on, the LED test occurs. If there isn’t a LED Test there isn’t a chance.



Download of the Tinker.fls firmware over a serial connection.

Prior to connection the user should have local access to the Tinker.fls file. This file is found in the C:\Program Files\NAI\SnifferNT\Driver\ATMLT2\WinNT\ directory by default. This procedure instructs the user to erase the flash file system of the ATM Book and download the new firmware image (Tinker.fls file) into it.

A serial connection is the RS 232 9 pin cable between the communications port on the ATM Book and the PC Com1 or Com2 port. The Ethernet connection is through a crossover cable provided with the ATM Book.

Set the HyperTerminal to 57600 8 data bits, 1 Stop bit, No parity (8N1). Connect cables between ATM Book and PC.

Power cycle ATM Book and on HyperTerminal screen observe:

Any key to abort LED Test:

Autoboot in 5 seconds (CTRL-A to abort)........aborted!

Press Control-A when the “Any key to abort LED Test” appears to halt LED test and abort the Autoboot. (Frequently HyperTerminal will not display the initial message or fail to transfer the Control-A command, so the user may need to perform this step a number of times.)

The following message will appear:

Mon960 User Interface: Version MON960 3.1.4
Diagnostics: Version 0.1.50 Jun 4 1999 10:35:32
M1RP; for i960 RP with 32MB DRAM
Mother Board Revision: B
Serial Baud Rate: 57600
Copyright 1997 NET2NET Corporation
Portions Copyright 1995 Intel Corporation
M1RP=>

The message of importance is Mother Board Revision: ? The value is either B or above. Make note of this value as it is necessary in the next step

The prompt M1RP=> or D1RP=> now appears at the bottom.

At this prompt the user will erase the sections of flash based on the revision level of the Mother Board. For Mother Board revision B, the FFS sections to erase are sections 11 through 24.

On Mother Board revisions above B, the FFS sections to erase are sections 23 through 34.

Motherboard Revision B Instructions:

Erase the memory in blocks of four (4) sections. The user interface prevents the user from accidentally erasing the memory blocks by requiring the user to verify the each step of the operation and by setting the default to “no.” That is, when the user starts the Flash Erase procedure, the UI will respond with a prompt are you sure (y/n) with No as the default response. Pressing a carriage return will result in the section of flash not being erased. The user must press “y” and only “y” during this operation. Pressing a CR after pressing “y” will result in the subsequent section of flash not being erased.

Here is the command sequence to erase the flash memory on a Revision B motherboard:

After you reach the M1RP=> or D1RP=>


1) Type ‘FE 11 12 13 14’ and hit Enter. You will receive a message that says: Erasing Flash section 11 Are you sure? (Y / [N]) It is IMPORTANT that the user only respond once per question and that they use only the letter Y to respond. Case doesn’t matter, but if any other key strokes come during the operation the ATMBook will abort erasing flash memory. Don’t worry if it happens, you can re-run the initial command to start the erase procedure again.

2) The ATMBook will print a message for each of the 4 sections we’re erasing. The customer must respond to each one with just a single press of the Y key.

3) After the initial 4 are done you will proceede through the next 4 sections with the command FE 15 16 17 18. As above it will prompt you for confirmation to erase each section of memory. The customer will respond Y to each section as prompted.

4) The next command we issue is FE 19 20 21 22. As before it will prompt you for confirmation to erase each section of memory. The customer will respond Y to each section as prompted.

5) The final command to complete the erasure of the ATMBook Firmware is FE 23 24. As in step one it will prompt you for confirmation to erase each section of memory. The customer will respond Y to each section as prompted.

6) With the firmware on the book erased we will now prepare the system to download the firmware. The first thing you’ll want the customer to do is copy the Tinker.fls file from wherever it is onto a floppy in the A: drive or to a convienent directory on the root of C:

7) Once the file copy is complete issue the do command. The ATMBook will print Downloading on the screen and appear to be hung. It is not hung, but waiting for the user to initiate file transfer over the serial line.

8) Inside of the HyperTerm software go to the Transfer menu and select Send File. This will open the Send File window. Enter the path and file name where indicated and select XModem as the protocol. Once these are entered, click the Send button to initiate file transfer.

9) File transfer will take up to 10 minutes to complete. Sit back, grab a coke and let it process.

10) Once the download has completed it will signal that it’s done and print a starting address. At this point you can manually power cycle the book.

 

[levelnet]

Thanks AXEEmeri for the update-via-serial procedure! I followed it and it seemed to work (motherboard-C revision). However, upon reboot I still get the "Attaching network interface dc0... No Such DC, unit #0" when the ATMbook boots. At D1RP, if I issue the 'qt' command, several of the Cardbus and Ethernet tests fail with "No Cardbus PC Card Detected" - everything else seems to pass 'Ok". And naturally, I can't set the IP address of the interface with the 'si' command either. The PC Card I'm using works in my other ATMBook - so I guess there is a physical flaw with the PC card interface. Any other specific tests that could run to confirm (or fix) this? Goodluck all!

 

[wallyprater]

I have inherited an ATMBook from another department and it is missing the PCMCIA Ehternet card. I tried a Xircom IIps adapter with no success and get the same error message as Elca does in the first message in this forum "Attaching network interface dc0... No Such DC, unit #0
failed: errno = 0xd0003." I successfully updated the firmware using AXEEmeri's procedure (Thank you)for motherboard-C revision but it still does not recognize my PCMCIA Ethernet card. Can anyone tell me which PCMCIA card I can use in the ATRBook, I do not have a support agreement with NAI?

 

[AlfSutherland]

I recommend getting the Xircom CEB2-100 cards, which are pretty much the same as NAI's. You can also use the NAI Xircom drivers, which are located in
C:\program files\nai\sniffernt\driver\xircom\"OS"
To use with the ATMBook, make sure you set the speed of the card to 100Mbps Half Duplex. See the ATMBook Install guide for all the other configs etc.
Alf

 

[levelnet]

Just FYI for all; I'm using the Xircom 10/100 cards and my ATMBook still generates the "No such DC" error message. Even after updating the ATMBook firmware, the error is still there - and I'm using multiple Xircom 10/100 cards. Based on that, it seems like the firmware in the ATMBook is not binding to the Xircom at the physical layer. If anyone wants my ATMBook (that generates this error), just ask and I'll let it go cheap (buyer pays shipping

 

[DanoC]

Whitezin2000,

Just read your 31 March post about "binding" issue to the Xircom PCMCIA card. Alf is correct, Xircom are the best cards to use with Sniffer Pro. But your mention of multiple Xircom cards might suggest an area to delve into --before u offload the ATMbook ;-).

According to NAI in order to have the software work with a related PCMCIA card they must be "loaded" together to work. In essense the particular PCMCIA card becomes bound to the software when loaded. If a different card is used, it might not work as the card's hardware address is linked into the executable. Not sure if that is what is causing your issue. Just a thought.

 

[dfusion]

I'll buy your ATM book if you don't want it.

mh@markholloway.com Sr. Network Engineer
ArcLight Systems, LLC

http://www.markholloway.com