Re: command line interface

MPari6 · ‎11-12-2009

I have Installed the Intel Command Line Interface and cannot connect to the interface. the system is a S5000XVN board running Windows 7. I have configured the BMC 'Server Management Guide'. Running as, admin, telnet and 'dpccli.exe' both results in:

Server: localhost

Username:

Password: ****

Connection failed.

Server:

Using 192.168.1.10 gives the same results

Any suggestions as to how to connect will be appreciated. Additional details are below.

Regards

Michael

Details.....Running as admin:

# dpcproxy -d c:\

Error (1063) The service process could not connect to the service controller.

invoking service control dispatcher.

# dpcproxy -viewarg

#

BMC configuration is

C:\Intel\syscfg>syscfg -d lan 1

LAN Configuration Settings:

----------------------------

LAN Channel Selected: 1

LAN Alert Destination Index Selected: None. LAN Alert Configuration will not be

displayed.

IP Address Source: Static

BMC Host IP Address: 192.168.1.10

Subnet Mask: 255.255.255.0

Gateway IP Address: 0.0.0.0

Gateway MAC Address: 00-00-00-00-00-00

Backup Gateway IP Address: 0.0.0.0

Backup Gateway MAC Address: 00-00-00-00-00-00

Community String:

Gratuitous ARP Enable: Enabled

Gratuitous ARP Interval (milliseconds): 2000

BMC ARP Response Enable: Enabled

C:\Intel\syscfg>syscfg -d channel 1

Channel Configuration Settings

-------------------------------

Channel Selected: 1

Channel Type: LAN

Features Supported: Basic Lan & SMTP

Authentication Types:

----------------------

Callback: [Not Configured]

User: [Not Configured]

<p style="padding-left: 60px;...

Daniel_O_Intel · ‎11-13-2009

Does it seem like Windows 7 is blocking this as an unknown inbound connection? I've not tried dpccli with Windows 7, but it works fine in 2003 and 2008.

MPari6 · ‎11-13-2009

Thanks Dan.

The intra net firewall has dpccli enabled as an exception. Come to think of it I am not sure if dpcproxy is enabled as an exception. I am not at that computer now so I will look at it later.

Executing:

# dpcproxy -d c:\

returns 'Error (1063) The service process could not connect to the service controller. invoking service control dispatcher.'

Does this mean that windows is blocking access to the proxy? By the way I have stopped the dpcproxy service and tried to run it in the forground with the same results as above.

Hope this helps

Edward_Z_Intel · ‎11-13-2009

On which system are you running the dpccli or DPC proxy? I don't think dpccli or DPC proxy can connect to it's own BMC, so typing "localhost" in the server field won't work. Also, the BMC LAN channel needs a different IP address from the OS, although it shares the same NIC port. Take your example, correct configuration should be like this:

BMC LAN channel: 192.168.1.10

OS IP address: 192.168.1.11

You'll need to install DPCCLI or DPC proxy on a 2nd system, say 192.168.1.12

On 192.168.1.12, make sure your TCP port 623 is not blocked, and you can ping 192.168.1.10. Then run "telnet 192.168.1.12 623", and type 192.168.1.10 in Server: field.

MPari6 · ‎11-14-2009

The BMC IP address is different than that of the OS. I have installed DPC CLI and Proxy on a different machine to no avail. Also I believe the BMC IP should respond to ping. It does not.

I am using "Intel Command Line User's Guide.pdf" as a reference which suggests the use of localhost and the possibility of connecting to the local system (page 7)

Edward_Z_Intel · ‎11-15-2009

Let me clarify the localhost thing on user manual. Yes you can telnet to localhost which is running DPCproxy, but you don't put localhost at the "Server:" prompt as that's the BMC IP address which OS is not aware of.

Yes you're right that BMC IP address should response to ping, but only if you're running ping from a different system. I'd suggest you perform a BIOS/BMC firmware upgrade first, and then use syscfg to enable BMC LAN channel:

//To assign a static IP address:

syscfg /le 1 static 192.168.1.10 255.255.255.0

//To enable BMC LAN channel 1:

syscfg /c 1 7 Always

//To set the password for BMC user 1 (Anonymous):

syscfg /u 1 "" "password"

/data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAYAAADgdz34AAADsElEQVR4nK2VTW9VVRSGn33OPgWpYLARbKWhQlCHTogoSkjEkQwclEQcNJEwlfgD/AM6NBo1xjhx5LyJ0cYEDHGkJqhtBGKUpm3SFii3vb2956wPB/t 9raEgSs52fuus89613rftdcNH8/c9q9 oe/Vzb5P 3McyNcfm2CcPj9af9w6gwjTwzvethx3Bx3x8xwd1wNM8dMcTNUHTfFLPnX6nVmZpeIYwf3cWD/PhbrvlPkblAzVFurKS6GmmGqqComaS qmBoTI0Ncu3mXuGvWnrJ ZSxweDgnkHf8ndVTdbiT3M7cQp2Z31dRTecHAfqydp4ejhwazh6Zezfnu98E1WIQwB3crEuJ2Y45PBTAQUVR9X4At66AppoEVO1Q8sgAOKJJjw6Am6OquDmvHskZ3R87gW vlHz98zpmiqphkkRVbQtsfPTOC30lJKFbFTgp83bWh7Zx/uX1B6w3hI3NkkZTqEpBRDBRzG2AQHcwcYwEkOGkTERREbLQ/8HxJwuW7zdYrzfZ2iopy4qqEspKaDYravVm33k1R91Q69FA1VBRzFIVvXbx5AgXT44A8MWP81yfu0utIR2aVK3vfCnGrcUNxp8a7gKYKiLCvY2SUvo/aNtnM3e49ucK9S3p0aDdaT0UAVsKi2tVi6IWwNL9JvdqTdihaz79/l u/rHMxmaJVMLkS2OoKKLWacdeE3IsSxctc2D5Qcl6vUlVVgNt fkPPcFFmTw1xruvT7SCd7nuVhDQvECzJH90h0azRKoKFRkAmP5lKTWAGRdefoZL554FQNUxB92WvYeA5UN4PtSqwB2phKqsqMpBgAunRhFR3j49zuU3jnX8k6fHEQKXzh1jbmGDuYU6s4t1rt6socUeLLZHhYO2AHSHmzt19ihTZ48O8Hzl/AmunD/BjTvrvPfNX3hWsNpwJCvwYm ngug4UilSCSq6k8YPtxDwfA WRawIWFbgscDiULcCEaWqBFOlrLazurupOSHLqGnEKJAY8TwBEHumqUirAjNm52vEPPRV4p01XXMPAQhUBjcWm9QZwijwokgAeYHlHYA06KR1cT6ZvoV56pDUJQEjw0KeaMgj1hPEY4vz2A4eW0/e1qA7KtQdsxTYAG0H3iG4xyK1Y xm7XmEPOJZDiENzLi2WZHngeOjj2Pe sMg4GRYyLAsx7ME4FnsyTD9pr0PEc8zPGRAwKXBkYOPEd96cZRvf11g9MDe7e3R4Z4Q vyEnn3P4t0XzK/W ODN5/kPfRLewAJVEQ0AAAAASUVORK5CYII=

//To enable BMC user 1 on LAN channel 1:

syscfg /ue 1 enable 1

MPari6 · ‎11-16-2009

Hello Edward, Thank you for all you time.

The BIOS BMC are both up to date BIOS 98 BMC 65.

I have changed the BMC IP address to 10.12.14.253 (The OS address is 10.12.14.25) and the sub net mask is 255.255.255.0.

I have reconfigured TCP/IP added 10.12.14.253. I can now ping the 253 address.

Telnet 10.12.14.253 623 and server 10.12.14.253 still respond Connection Failed. I also tried Telnet 10.12.14.10 623 and server 10.12.14.253 with the same results.

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Link-local IPv6 Address . . . . . : fe80::4126:c862:329d:24be%11

IPv4 Address. . . . . . . . . . . : 10.12.14.25

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IPv4 Address. . . . . . . . . . . : 10.12.14.253

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.12.14.1

IP Address Source: Static

BMC Host IP Address: 10.12.14.253

Subnet Mask: 255.255.255.0

Gateway IP Address: 0.0.0.0

Gateway MAC Address: 00-00-00-00-00-00

Backup Gateway IP Address: 0.0.0.0

Backup Gateway MAC Address: 00-00-00-00-00-00

Community String:

Gratuitous ARP Enable: Enabled

Gratuitous ARP Interval (milliseconds): 2000

BMC ARP Response Enable: Enabled

Channel Configuration Settings

-------------------------------

Channel Selected: 1

Channel Type: LAN

Features Supported: Basic Lan & SMTP

Authentication Types:

----------------------

Callback: [Not Configured]

User: [Not Configured]

Operator: [Not Configured]

Administrator: [Not Configured]

Per Message Authentication: Enabled

User Level Authentication: Enabled

Access Mode: Always

Privilege Level: Admin

PEF status: Disabled

SOL Configuration Settings:

----------------------------

Channel Number Selected: 1

SOL Enable: Enabled

Privilege Level Limit: Admin

Baud Rate (bits/second): 115200

Retry Count: 5

Retry Interval (ms): 60

Edward_Z_Intel · ‎11-16-2009

Good that we have some progress here.

Now like I mentioned before you can't run DPCCLI from the server you want to mangage (in this case 10.12.14.25). You'll need to install DPCCLI on a different server, i.e. 10.12.14.26, and then telnet to 10.12.14.26. You shouldn't add 10.12.14.253 to OS IP address.

BMC and OS uses different MAC address, even though they share the same LAN port. To verify, ping both 10.12.14 25 and 10.12.14.253 from a second server, then type "arp -a". MAC address of BMC should be MAC address of LAN + 2

MPari6 · ‎11-19-2009

I have carefully followed your suggestions to the letter, however arp -a does not show the BMC IP address (10.12.14.253) & Ping does not respond. I am believing that until arp shows the BMC IP address one will not be able to attach to the BMC with CLI.

In a different thread (/message/73475# 73475 http://communities.intel.com/message/73475# 73475) there is a discussion about enabling the BMC mac on nic1. I know that this works but there must be something 'special' about my system... I am going to try your suggestion from the other post 'You can boot the http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&ProdId=2869&DwnldID=18174&lang=eng IDA CD to configure BMC LAN channel, or you can also use the Save and Restore System Configuration utility (syscfg). "

Let you know if it works

Thanks

Edward_Z_Intel · ‎11-19-2009

So which physical NIC port are you using? On S5000XVN you can use both NICs for management, but since we're configuring LAN channel 1 here, you should connect NIC port 1. NIC 1 is the port next to 9-pin serial port.

MPari6 · ‎11-19-2009

NIC1 is being used and NIC2 is disabled. NIC1 MAC address ends in 80, NIC2 ends in 81 and 82 is assigned to the BMC, I have reset the BIOS and BMC to defaults and programmed the BMC as suggested. There is no indication of the BMC IP when looking at arp -r, however Active Server management console confirms both the BMC IP and MAC address. of course ping and login fail (using another machine).

DPCPROXY logs show the telnet session as do arp / netstat.

Edward_Z_Intel · ‎11-20-2009

This is weird... Could you try the following to isolate the issue:

1. Connect NIC1 and your other machine using a direct cable. Ping OS and BMC IP address from the other machine and see if you can get response.

2. Shut down Windows 7 and ping the BMC IP address.

3. If still can't get response, try to use NIC2 and configure BMC LAN channel 2.

4. Hook your S5000XVN server to a DHCP environment and configure BMC LAN channel to use DHCP. Run Active System Console or syscfg to see if the BMC can get an IP address from DHCP server.

MPari6 · ‎11-25-2009

Edward, thanks for your suggestions.

I rolled back the firmware back to BIOS 96, BMC 64, FRUSDR 46 (from to BIOS 98, BMC 65, FRUSDR 48). The BMC MAC and IP number are now visable and Ping works fine. I am using NIC1 an the computer with an IP address of 10.12.14.25 and the BMC address is 10.12.14.125.

Still cannot attch to the BMC.

Working on a different computer with IP 10.12.14.33. Telenet to 10.12.14.25:623 (telnet 10.12.14.25 623) results in the 'server:' prompt. see below

----------------------------

telnet 10.12.14.25 623

Server: 10.12.14.125

Username:

Password: ****

Connection failed.

Server:

-----------------------------

Dpcprocy logs show

************** C:\dpcLogs/DpcProxy.Log ***************

Client thread 3496 for 10.12.14.27 created

Client thread 780 for 127.0.0.1 created

Client thread 4436 for 10.12.14.33 created

************** C:\dpcLogs/Debug.Log ***************

Attempting LAN connection to : 10.12.14.125

************** C:\dpcLogs/Raw.Log ***************

Attempting LAN connection to : 10.12.14.125

Regards

Michael

Edward_Z_Intel · ‎11-25-2009

Michael,

This is good news. DPCCLI should be installed on a different machine, not on the server you want to manage. In your case, install DPCCLI on 10.12.14.33, and then telnet to 10.12.14.33:623. In the "Server:" prompt type 10.12.14.125.

Regards,

Edward

MPari6 · ‎12-06-2009

Yes things are working just as they should.

Thank you Edward for all your attention to this, it is much appreciated.

Edward_Z_Intel · ‎12-06-2009

Good to know that everything is working fine now. You're welcome