October 2002 - ixp1200 - lists.cs.princeton.edu

Question on Intel-supplied firmware versions
by Magesh Kannan 07 Oct '02

07 Oct '02

Hi, The original firmware supplied with an IXP1200 board is also present in the IXA SDK in the directory IXP1200/BoardSupport/bin. But there are many subdirectories inside this directory. How do I find the right version for the evaluation board that I have? Thanks, Magesh

3 2

Debugging ETH ports of IXP1200 (fwd)
by Magesh Kannan 04 Oct '02

04 Oct '02

Hi, Can someone from Intel on this list please help me on this? Please find enclosed a description of a problem in making the octal Fast Ethernet ports run at 100 Mbps when using the VERA runtime. Today, I restored the flash to the original Intel supplied image, changed the jumper settings back to the factory settings, put the card back in the Evaluation system chassis and started diagnostics. The problem (of LEDs blinking on the ethernet ports and the link flapping) persists even with the Intel firmware. Is there a way to debug the ethernet ports on the evaluation board? In particular, is there a way to find out what speed the MAC has decided on after autonegotiation or to disable autonegotiation and fix the speed at 100 Mbps? Thanks, Magesh ---------- Forwarded message ---------- Date: Wed, 2 Oct 2002 17:36:42 -0500 (CDT) From: Magesh Kannan <magesh(a)ittc.ku.edu> Reply-To: ixp1200(a)CS.Princeton.EDU To: ixp1200(a)CS.Princeton.EDU Subject: [ixp1200] Debugging ETH ports of IXP1200 Hi, This is a follow-up to my earlier emails about not being able to connect the Fast Ethernet ports on the IXP1200 to a PC using a straight-thru cable. Here is a recap. If I connect any of the ports on the IXP1200 to an ethernet card on a Linux PC, the two LEDs on the IXP1200 port (which I think stand for Activity and Full-Duplex) and one of the eight LEDs in the middle (which I think is the Link LED) blink at regular intervals (even when no data is being transmitted) and no link seems to be established. If I run the diagnostic tool 'mii-diag' on the Linux side, this is the output I get. ================ Basic registers of MII PHY #1: 3100 7809 0181 b802 01e1 41e1 0003 0000. The autonegotiated capability is 01e0. The autonegotiated media type is 100baseTx-FD. Basic mode control register 0x3100: Auto-negotiation enabled. Basic mode status register 0x7809 ... 7809. Link status: not established. Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT. End of basic transceiver information. Monitoring the MII transceiver status. 17:13:19.731 Baseline value of MII BMSR (basic mode status register) is 7809. 17:13:34.036 MII BMSR now 782d: Good link, NWay done, No Jabber (41e1). New link partner capability is 41e1 0003: 10/100 HD+FD switch. 17:13:34.326 MII BMSR now 7809: no link, NWay busy, No Jabber (0000). 17:13:41.236 MII BMSR now 782d: Good link, NWay done, No Jabber (41e1). New link partner capability is 41e1 0003: 10/100 HD+FD switch. 17:13:41.396 MII BMSR now 7809: no link, NWay busy, No Jabber (0000). 17:14:00.106 MII BMSR now 782d: Good link, NWay done, No Jabber (41e1). New link partner capability is 41e1 0003: 10/100 HD+FD switch. 17:14:00.136 MII BMSR now 7809: no link, NWay busy, No Jabber (0000). 17:14:09.846 MII BMSR now 7829: no link, NWay done, No Jabber (41e1). New link partner capability is 41e1 0003: 10/100 HD+FD switch. 17:14:09.856 MII BMSR now 782d: Good link, NWay done, No Jabber (41e1). 17:14:10.366 MII BMSR now 7809: no link, NWay busy, No Jabber (0000). 17:14:12.076 MII BMSR now 7829: no link, NWay done, No Jabber (41e1). New link partner capability is 41e1 0003: 10/100 HD+FD switch. 17:14:12.086 MII BMSR now 782d: Good link, NWay done, No Jabber (41e1). ================ The same behavior results with different NICs on the Linux side, one using eepro100 driver and another using the tulip driver on Linux 2.4.3-12. As you can see from the output, the link seems to be flapping. I am sure that the cables that I use are fine (I tested them using a cable tester, connected them on other machines and even used a factory-made CAT5 cable). To cross-check this problem, I also connected one of the IXP1200 ports to a port on a Cisco Catalyst 3500 series switch and observed in the switch's console port that the concerned ethernet port was going up and down fairly regularly. Has anyone seen this before? Given this behavior, is there a way to debug the ethernet ports on the IXP1200 board? In particular, is there a way to find out what speed the MAC has decided on and if possible, disable autonegotiation? FYI, if I interconnect two ports of IXP1200 with each other with a crossover cable, the link is established fine, the yellow LED on the port is lit and link LED is also up. Thanks for your help, Magesh

2 1

Does IXP1200 ENP-2505 PCI board work with vera
by Roberto Maccaferri 04 Oct '02

04 Oct '02

I have an IXA Education Workstation with inside an IXP1200 ENP-2505 PCI board. Can I use Vera? Because in the site said: IXP1200 Evaluation Board users: Update the flash following the directions here. (Princeton people may wish to use our BP-1200 device programmer and use the directions here.) Change the jumper settings on the board so that it may be installed in a PC running Linux by following the directions here. , Install the updated IXP1200 Evaluation Board and/or PMC694 board. I don`t understand if this IXP1200 Evaluation Board or PMC694 board is the only that work with VERA. Thanks Roberto

2 1

errors when trying to load the microcode.
by tomer 03 Oct '02

03 Oct '02

hi, while trying to load the microcode i get this error "bad object error occurred during load microcode operation" ---------------->>>> "microcode load failed"---------------->>>> "unexpected return status (0x1) from udebug library when trying to updatefreestore." i am working with the VxWorks OS there is no problem connecting to the IXPeb with the tornado, i checked my build settings and it is fine. cant understand the reason for the failior in loading the microcode. one more thing, it worked for a few times before but not anymore. does anyone has a clue? thanks tomer

1 0

Debugging ETH ports of IXP1200
by Magesh Kannan 02 Oct '02

02 Oct '02

Hi, This is a follow-up to my earlier emails about not being able to connect the Fast Ethernet ports on the IXP1200 to a PC using a straight-thru cable. Here is a recap. If I connect any of the ports on the IXP1200 to an ethernet card on a Linux PC, the two LEDs on the IXP1200 port (which I think stand for Activity and Full-Duplex) and one of the eight LEDs in the middle (which I think is the Link LED) blink at regular intervals (even when no data is being transmitted) and no link seems to be established. If I run the diagnostic tool 'mii-diag' on the Linux side, this is the output I get. ================ Basic registers of MII PHY #1: 3100 7809 0181 b802 01e1 41e1 0003 0000. The autonegotiated capability is 01e0. The autonegotiated media type is 100baseTx-FD. Basic mode control register 0x3100: Auto-negotiation enabled. Basic mode status register 0x7809 ... 7809. Link status: not established. Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT. End of basic transceiver information. Monitoring the MII transceiver status. 17:13:19.731 Baseline value of MII BMSR (basic mode status register) is 7809. 17:13:34.036 MII BMSR now 782d: Good link, NWay done, No Jabber (41e1). New link partner capability is 41e1 0003: 10/100 HD+FD switch. 17:13:34.326 MII BMSR now 7809: no link, NWay busy, No Jabber (0000). 17:13:41.236 MII BMSR now 782d: Good link, NWay done, No Jabber (41e1). New link partner capability is 41e1 0003: 10/100 HD+FD switch. 17:13:41.396 MII BMSR now 7809: no link, NWay busy, No Jabber (0000). 17:14:00.106 MII BMSR now 782d: Good link, NWay done, No Jabber (41e1). New link partner capability is 41e1 0003: 10/100 HD+FD switch. 17:14:00.136 MII BMSR now 7809: no link, NWay busy, No Jabber (0000). 17:14:09.846 MII BMSR now 7829: no link, NWay done, No Jabber (41e1). New link partner capability is 41e1 0003: 10/100 HD+FD switch. 17:14:09.856 MII BMSR now 782d: Good link, NWay done, No Jabber (41e1). 17:14:10.366 MII BMSR now 7809: no link, NWay busy, No Jabber (0000). 17:14:12.076 MII BMSR now 7829: no link, NWay done, No Jabber (41e1). New link partner capability is 41e1 0003: 10/100 HD+FD switch. 17:14:12.086 MII BMSR now 782d: Good link, NWay done, No Jabber (41e1). ================ The same behavior results with different NICs on the Linux side, one using eepro100 driver and another using the tulip driver on Linux 2.4.3-12. As you can see from the output, the link seems to be flapping. I am sure that the cables that I use are fine (I tested them using a cable tester, connected them on other machines and even used a factory-made CAT5 cable). To cross-check this problem, I also connected one of the IXP1200 ports to a port on a Cisco Catalyst 3500 series switch and observed in the switch's console port that the concerned ethernet port was going up and down fairly regularly. Has anyone seen this before? Given this behavior, is there a way to debug the ethernet ports on the IXP1200 board? In particular, is there a way to find out what speed the MAC has decided on and if possible, disable autonegotiation? FYI, if I interconnect two ports of IXP1200 with each other with a crossover cable, the link is established fine, the yellow LED on the port is lit and link LED is also up. Thanks for your help, Magesh

1 0

Connectivity questions
by Magesh Kannan 02 Oct '02

02 Oct '02

Hi, This is a question for the guys at Princeton. Can you please briefly describe your hardware setup? I mean 1. what cable (cross-over/straight-thru) you use to connect the ethernet ports on the IXP1200 to the outside world. 2. if you always use a switch/hub between a host and the ixp1200 ethernet ports. 3. what ethernet card and driver do you use on the machines that you connect to the IXP1200 for the IPmm experiment. 4. if you force the speed on any of these ports to 10 Mbps etc. Contrary to some advice on this list for my question on cabling, it seems that the ethernet ports on the IXP1200 behave like ports on hubs. This means that straight-thru cables have to be used to connect an IXP1200 port to a PC's ethernet card. When I do this, the yellow LED on the IXP1200 port blinks and the LED in the LED bank in the middle of the two quad connectors does not come on. If I force the speed on the linux PC's interface to 10 Mbps (using mii-diag), the link LED (in the LED bank) comes on, but when I try to send traffic, there is some debug output on the IXP1200's serial port (indicating packet reception) initially. After some time, there is no further output and I get carrier errors on the PC (found from ifconfig). The only configuration in which I have been able to make the IXP1200 ports receive packets is this Linux PC's eth1 <--- STRAIGHT-THRU ----> 10 Mbps ONLY HUB <----- CROSS-OVER ----> 1XP1200 ETH port Consequently, I am confused. Thanks, Magesh

3 3

Connectivity problems
by Magesh Kannan 30 Sep '02

30 Sep '02

Hi, What kind of cabling is needed to connect the 10/100 ethernet ports on the IXP1200 to an ethernet card on another PC? I tried CAT-5 crossover cable but the LEDs on either card do not come on. I also tried straight through cable. The orange LED on the IXP ethernet port blinks and the Link LED on the other card also blinks, but it seems that connectivity is not fine. Should the ports be explicitly brought up? I only added the MAC and IP addresses of the two machines that I am trying to connect via the IXP1200 to the route cache in ipmm.c. Ping from either machine does not work and debug output on IXP's serial port does not seem to indicate any packet reception. Thanks, Magesh

2 1