freeipmi-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc module


From: Albert Chu
Subject: Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc module
Date: Wed, 19 Jan 2005 16:27:06 -0800

The configuration looks fine.  Have you tried usernames/passwords other
than the anonymous one?  I know there are some BMCs that flat out don't
allow anonymous logins. 

Al

--
Albert Chu
address@hidden
Lawrence Livermore National Laboratory

----- Original Message -----
From: Joshua Williams <address@hidden>
Date: Wednesday, January 19, 2005 2:05 pm
Subject: Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc module

> Al,
> 
> Below is the complete output from bmc-config.  I havn't changed 
> anythingregarding the UserX configurations and so they represent 
> the default
> configurations from the manufacturer.  I don't see anything wrong with
> them.  Can you spot anything?
> 
> address@hidden root]# bmc-config --checkout
> Section User1
>        ## Give username
>        Username                                     Anonymous
>        ## Give password or leave it blank to clear password
>        Password                                     
>        ## Possible values: Yes/No
>        Lan_Enable_Ipmi_Msgs                         Yes
>        ## Possible values: Yes/No
>        Lan_Enable_Link_Auth                         Yes
>        ## Possible values: Yes/No
>        Lan_Enable_Restrict_To_Callback              No
>        ## Possible values: 
> Callback/User/Operator/Administrator/OEM_Proprietary/No_Access      
>  Lan_Privilege_Limit                          User
>        ## Give valid number
>        Lan_Session_Limit                            0
>        ## Possible values: Yes/No
>        Serial_Enable_Ipmi_Msgs                      Yes
>        ## Possible values: Yes/No
>        Serial_Enable_Link_Auth                      Yes
>        ## Possible values: Yes/No
>        Serial_Enable_Restrict_To_Callback           No
>        ## Possible values: 
> Callback/User/Operator/Administrator/OEM_Proprietary/No_Access      
>  Serial_Privilege_Limit                       User
>        ## Give valid number
>        Serial_Session_Limit                         0
> EndSection
> Section User2
>        ## Give username
>        Username                                     Operator
>        ## Give password or leave it blank to clear password
>        Password                                     
>        ## Possible values: Yes/No
>        Lan_Enable_Ipmi_Msgs                         Yes
>        ## Possible values: Yes/No
>        Lan_Enable_Link_Auth                         Yes
>        ## Possible values: Yes/No
>        Lan_Enable_Restrict_To_Callback              No
>        ## Possible values: 
> Callback/User/Operator/Administrator/OEM_Proprietary/No_Access      
>  Lan_Privilege_Limit                          User
>        ## Give valid number
>        Lan_Session_Limit                            0
>        ## Possible values: Yes/No
>        Serial_Enable_Ipmi_Msgs                      Yes
>        ## Possible values: Yes/No
>        Serial_Enable_Link_Auth                      Yes
>        ## Possible values: Yes/No
>        Serial_Enable_Restrict_To_Callback           No
>        ## Possible values: 
> Callback/User/Operator/Administrator/OEM_Proprietary/No_Access      
>  Serial_Privilege_Limit                       User
>        ## Give valid number
>        Serial_Session_Limit                         0
> EndSection
> Section User3
>        ## Give username
>        Username                                     Administrator
>        ## Give password or leave it blank to clear password
>        Password                                     
>        ## Possible values: Yes/No
>        Lan_Enable_Ipmi_Msgs                         Yes
>        ## Possible values: Yes/No
>        Lan_Enable_Link_Auth                         Yes
>        ## Possible values: Yes/No
>        Lan_Enable_Restrict_To_Callback              No
>        ## Possible values: 
> Callback/User/Operator/Administrator/OEM_Proprietary/No_Access      
>  Lan_Privilege_Limit                          Administrator
>        ## Give valid number
>        Lan_Session_Limit                            0
>        ## Possible values: Yes/No
>        Serial_Enable_Ipmi_Msgs                      Yes
>        ## Possible values: Yes/No
>        Serial_Enable_Link_Auth                      Yes
>        ## Possible values: Yes/No
>        Serial_Enable_Restrict_To_Callback           No
>        ## Possible values: 
> Callback/User/Operator/Administrator/OEM_Proprietary/No_Access      
>  Serial_Privilege_Limit                       Administrator
>        ## Give valid number
>        Serial_Session_Limit                         0
> EndSection
> Section User4
>        ## Give username
>        Username                                     Callback
>        ## Give password or leave it blank to clear password
>        Password                                     
>        ## Possible values: Yes/No
>        Lan_Enable_Ipmi_Msgs                         Yes
>        ## Possible values: Yes/No
>        Lan_Enable_Link_Auth                         Yes
>        ## Possible values: Yes/No
>        Lan_Enable_Restrict_To_Callback              No
>        ## Possible values: 
> Callback/User/Operator/Administrator/OEM_Proprietary/No_Access      
>  Lan_Privilege_Limit                          User
>        ## Give valid number
>        Lan_Session_Limit                            0
>        ## Possible values: Yes/No
>        Serial_Enable_Ipmi_Msgs                      Yes
>        ## Possible values: Yes/No
>        Serial_Enable_Link_Auth                      Yes
>        ## Possible values: Yes/No
>        Serial_Enable_Restrict_To_Callback           No
>        ## Possible values: 
> Callback/User/Operator/Administrator/OEM_Proprietary/No_Access      
>  Serial_Privilege_Limit                       User
>        ## Give valid number
>        Serial_Session_Limit                         0
> EndSection
> Section LAN_Channel
>        ## Possible values: 
> Disabled/Pre_Boot_Only/Always_Available/Shared        
> Volatile_Access_Mode                         Always_Available
>        ## Possible values: Yes/No
>        Volatile_Enable_User_Level_Auth              Yes
>        ## Possible values: Yes/No
>        Volatile_Enable_Per_Message_Auth             Yes
>        ## Possible values: Yes/No
>        Volatile_Enable_Pef_Alerting                 No
>        ## Possible values: 
> Callback/User/Operator/Administrator/OEM_Proprietary/No_Access      
>  Volatile_Channel_Privilege_Limit             Administrator
>        ## Possible values: 
> Disabled/Pre_Boot_Only/Always_Available/Shared        
> Non_Volatile_Access_Mode                     Always_Available
>        ## Possible values: Yes/No
>        Non_Volatile_Enable_User_Level_Auth          Yes
>        ## Possible values: Yes/No
>        Non_Volatile_Enable_Per_Message_Auth         Yes
>        ## Possible values: Yes/No
>        Non_Volatile_Enable_Pef_Alerting             No
>        ## Possible values: 
> Callback/User/Operator/Administrator/OEM_Proprietary/No_Access      
>  Non_Volatile_Channel_Privilege_Limit         Administrator
> EndSection
> Section LAN_Conf
>        ## Possible values: 
> Unspecified/Static/Use_DHCP/Use_BIOS/Use_Others        
> Ip_Address_Source                            Static
>        ## Give valid IP Address
>        Ip_Address                                   10.0.65.3
>        ## Give valid MAC Address
>        Mac_Address                                  00:E0:81:2B:0A:AC
>        ## Give valid Subnet mask
>        Subnet_Mask                                  255.255.255.0
>        ## Give valid IP Address
>        Default_Gateway_Ip_Address                   10.0.65.1
>        ## Give valid MAC Address
>        Default_Gateway_Mac_Address                  00:00:00:00:00:00
>        ## Give valid IP Address
>        Backup_Gateway_Ip_Address                    10.0.65.1
>        ## Give valid MAC Address
>        Backup_Gateway_Mac_Address                   00:00:00:00:00:00
> EndSection
> Section LAN_Conf_Auth
>        ## Possible values: Yes/No
>        Callback_Enable_Auth_Type_None               Yes
>        ## Possible values: Yes/No
>        Callback_Enable_Auth_Type_Md2                No
>        ## Possible values: Yes/No
>        Callback_Enable_Auth_Type_Md5                Yes
>        ## Possible values: Yes/No
>        Callback_Enable_Auth_Type_Straight_Password  Yes
>        ## Possible values: Yes/No
>        Callback_Enable_Auth_Type_Oem_Proprietary    No
>        ## Possible values: Yes/No
>        User_Enable_Auth_Type_None                   Yes
>        ## Possible values: Yes/No
>        User_Enable_Auth_Type_Md2                    No
>        ## Possible values: Yes/No
>        User_Enable_Auth_Type_Md5                    Yes
>        ## Possible values: Yes/No
>        User_Enable_Auth_Type_Straight_Password      Yes
>        ## Possible values: Yes/No
>        User_Enable_Auth_Type_Oem_Proprietary        No
>        ## Possible values: Yes/No
>        Operator_Enable_Auth_Type_None               Yes
>        ## Possible values: Yes/No
>        Operator_Enable_Auth_Type_Md2                No
>        ## Possible values: Yes/No
>        Operator_Enable_Auth_Type_Md5                Yes
>        ## Possible values: Yes/No
>        Operator_Enable_Auth_Type_Straight_Password  Yes
>        ## Possible values: Yes/No
>        Operator_Enable_Auth_Type_Oem_Proprietary    No
>        ## Possible values: Yes/No
>        Admin_Enable_Auth_Type_None                  Yes
>        ## Possible values: Yes/No
>        Admin_Enable_Auth_Type_Md2                   No
>        ## Possible values: Yes/No
>        Admin_Enable_Auth_Type_Md5                   Yes
>        ## Possible values: Yes/No
>        Admin_Enable_Auth_Type_Straight_Password     Yes
>        ## Possible values: Yes/No
>        Admin_Enable_Auth_Type_Oem_Proprietary       No
>        ## Possible values: Yes/No
>        Oem_Enable_Auth_Type_None                    Yes
>        ## Possible values: Yes/No
>        Oem_Enable_Auth_Type_Md2                     No
>        ## Possible values: Yes/No
>        Oem_Enable_Auth_Type_Md5                     Yes
>        ## Possible values: Yes/No
>        Oem_Enable_Auth_Type_Straight_Password       Yes
>        ## Possible values: Yes/No
>        Oem_Enable_Auth_Type_Oem_Proprietary         No
> EndSection
> Section LAN_Conf_Misc
>        ## Possible values: Yes/No
>        Enable_Gratuitous_Arps                       No
>        ## Possible values: Yes/No
>        Enable_Arp_Response                          No
>        ## Give valid number
>        Gratuitous_Arp_Interval                      4
> EndSection
> Section Serial_Channel
> Error in checkout of key <Volatile_Access_Mode>
> Error in checkout of key <Volatile_Enable_User_Level_Auth>
> Error in checkout of key <Volatile_Enable_Per_Message_Auth>
> Error in checkout of key <Volatile_Enable_Pef_Alerting>
> Error in checkout of key <Volatile_Channel_Privilege_Limit>
> Error in checkout of key <Non_Volatile_Access_Mode>
> Error in checkout of key <Non_Volatile_Enable_User_Level_Auth>
> Error in checkout of key <Non_Volatile_Enable_Per_Message_Auth>
> Error in checkout of key <Non_Volatile_Enable_Pef_Alerting>
> Error in checkout of key <Non_Volatile_Channel_Privilege_Limit>
> EndSection
> Section Serial_Conf
> Error in checkout of key <Enable_Basic_Mode>
> Error in checkout of key <Enable_PPP_Mode>
> Error in checkout of key <Enable_Terminal_Mode>
> Error in checkout of key <Connect_Mode>
> Error in checkout of key <Page_Blackout_Interval>
> Error in checkout of key <Call_Retry_Time>
> Error in checkout of key <Enable_DTR_Hangup>
> Error in checkout of key <Flow_Control>
> Error in checkout of key <Bit_Rate>
> EndSection
> Section Misc
>        ## Possible Values: 
> Off_State_AC_Apply/Restore_State_AC_Apply/On_State_AC_Apply        
> Power_Restore_Policy                         Off_State_Ac_Apply
> EndSection
> 
> On Wed, Jan 19, 2005 at 01:26:40PM -0800, Albert Chu wrote:
> > Hi Josh,
> > 
> > Are you sure you have username/password/privilege/authentication
> > configuration setup correctly??
> > 
> > For security purposes, I believe some BMCs (under certain 
> configuration> and error conditions) will not reply to messages.  
> This can give off the
> > resemblance that the network connection is bad, and thus 
> ipmipower can
> > "time out".
> > 
> > Al
> > 
> > --
> > Albert Chu
> > address@hidden
> > Lawrence Livermore National Laboratory
> > 
> > ----- Original Message -----
> > From: "Bala.A" <address@hidden>
> > Date: Wednesday, January 19, 2005 1:12 pm
> > Subject: Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc 
> module> 
> > > Hi,
> > > 
> > > Can you try ipmipower with the following conditions?
> > > 
> > > 1. Bring up ONLY on-board Intel Pro100 card (IPMI).
> > > 2. Try ipmipower with cross-over cable connected to another 
> machine.> > 
> > > Thanks,
> > > 
> > > Best Regards
> > > Bala
> > > 
> > > 
> > > > On Wed, Jan 19, 2005 at 01:54:06PM -0600, Joshua Williams wrote:
> > > >> On Wed, Jan 19, 2005 at 10:40:55AM -0800, Bala.A wrote:
> > > >> > Hi
> > > >> >
> > > >> > > Sorry for the confusion on my end... This is an S2882 
> and 
> > > there were
> > > >> > > actually four ethernet cards in the system.  Three 
> onboard 
> > > and one
> > > >> > > PCI (another Intel - eth3).  I was trying to give the 
> BMC the
> > > >> addresses
> > > >> > > of the PCI card (eth3).  Once I figured things out I 
> gave it 
> > > the>> > > addresses of the onboard Intel card (eth2) and 
> started 
> > > using eth2 as
> > > >> > > the primary network interface, ipmiping and rmcpping 
> started to
> > > >> work.
> > > >> > > I can't get 'ipmipower --stat' to work though.  I get 
> the 
> > > simple>> message:
> > > >> > >
> > > >> > >    # ipmipower --stat --hostname tomato
> > > >> > >    tomato: timed out
> > > >> >
> > > >> > 1. Your on-board Intel Pro100 card should be up and 
> running 
> > > with same
> > > >> IP
> > > >> > address of BMC in GNU/Linux. This is known problem in SMDC 
> > > firmware.>>
> > > >> This is true:
> > > >>
> > > >> address@hidden root]# ifconfig eth2
> > > >> eth2      Link encap:Ethernet  HWaddr 00:E0:81:2B:0A:AC
> > > >>           inet addr:10.0.65.3  Bcast:10.0.65.255  
> > > Mask:255.255.255.0>> ...
> > > >>
> > > >> address@hidden root]# bmc-config --checkout
> > > >> ...
> > > >> Section LAN_Conf
> > > >>         ## Possible values:
> > > >> Unspecified/Static/Use_DHCP/Use_BIOS/Use_Others
> > > >>         Ip_Address_Source                            Static
> > > >>         ## Give valid IP Address
> > > >>         Ip_Address                                   10.0.65.3
> > > >>         ## Give valid MAC Address
> > > >>         Mac_Address                                  
> > > 00:E0:81:2B:0A:AC>>         ## Give valid Subnet mask
> > > >>         Subnet_Mask                                  
> 255.255.255.0> > >>         ## Give valid IP Address
> > > >>         Default_Gateway_Ip_Address                   10.0.65.1
> > > >>         ## Give valid MAC Address
> > > >>         Default_Gateway_Mac_Address                  
> > > 00:00:00:00:00:00>>         ## Give valid IP Address
> > > >>         Backup_Gateway_Ip_Address                    10.0.65.1
> > > >>         ## Give valid MAC Address
> > > >>         Backup_Gateway_Mac_Address                   
> > > 00:00:00:00:00:00>> EndSection
> > > >> ...
> > > >>
> > > >> > 2. Install GNU FreeIPMI in another machine (This machine 
> > > should be in
> > > >> same
> > > >> > network of IPMI machine by on-board Intel Pro100 card).
> > > >>
> > > >> Installed on:
> > > >>
> > > >> address@hidden root]# rpm -q freeipmi
> > > >> freeipmi-0.1.3-0.20041102
> > > >
> > > > Sorry, this should have read:
> > > >
> > > > address@hidden root]# rpm -q freeipmi
> > > > freeipmi-0.1.3-0.20041102
> > > >
> > > > - Josh
> > > >
> > > >> address@hidden root]# ifconfig
> > > >> eth0      Link encap:Ethernet  HWaddr 00:0F:1F:2A:FC:B4
> > > >>           inet addr:10.0.3.81  Bcast:10.0.3.255  
> Mask:255.255.255.0> > >> ...
> > > >>
> > > >> This is on a 10.0.3.x subnet while the IPMI card is on a 
> 10.0.65.x> > >> subnet.  Should not matter though because as you'll 
> see below, 
> > > ipmiping>> works between the two.
> > > >>
> > > >> > 3. Test ICMP ping to IPMI machine.  This should be working.
> > > >>
> > > >> This works:
> > > >>
> > > >> address@hidden root]# ping 10.0.65.3
> > > >> PING 10.0.65.3 (10.0.65.3) 56(84) bytes of data.
> > > >> 64 bytes from 10.0.65.3: icmp_seq=0 ttl=62 time=0.447 ms
> > > >> 64 bytes from 10.0.65.3: icmp_seq=1 ttl=62 time=0.386 ms
> > > >> 64 bytes from 10.0.65.3: icmp_seq=2 ttl=62 time=0.373 ms
> > > >> 64 bytes from 10.0.65.3: icmp_seq=3 ttl=62 time=0.382 ms
> > > >> 64 bytes from 10.0.65.3: icmp_seq=4 ttl=62 time=0.365 ms
> > > >>
> > > >> --- 10.0.65.3 ping statistics ---
> > > >> 5 packets transmitted, 5 received, 0% packet loss, time 3999ms
> > > >> rtt min/avg/max/mdev = 0.365/0.390/0.447/0.036 ms, pipe 2
> > > >>
> > > >> > 4. If ICMP ping is successful, test whether ipmipower, 
> > > ipmiping and
> > > >> > rcmpping are working or not.
> > > >>
> > > >> ipmiping works:
> > > >>
> > > >> address@hidden root]# ipmiping 10.0.65.3
> > > >> ipmiping 10.0.65.3 (10.0.65.3)
> > > >> response received from 10.0.65.3: rq_seq=0
> > > >> response received from 10.0.65.3: rq_seq=1
> > > >> response received from 10.0.65.3: rq_seq=2
> > > >> response received from 10.0.65.3: rq_seq=3
> > > >> response received from 10.0.65.3: rq_seq=4
> > > >> response received from 10.0.65.3: rq_seq=5
> > > >> --- ipmiping 10.0.65.3 statistics ---
> > > >> 6 requests transmitted, 6 responses received in time, 0.0% 
> > > packet loss
> > > >>
> > > >> As does rmcpping:
> > > >>
> > > >> address@hidden root]# rmcpping 10.0.65.3
> > > >> rmcpping 10.0.65.3 (10.0.65.3)
> > > >> pong received from 10.0.65.3: msg_tag=0
> > > >> pong received from 10.0.65.3: msg_tag=1
> > > >> pong received from 10.0.65.3: msg_tag=2
> > > >> pong received from 10.0.65.3: msg_tag=3
> > > >> pong received from 10.0.65.3: msg_tag=4
> > > >> pong received from 10.0.65.3: msg_tag=5
> > > >> --- rmcpping 10.0.65.3 statistics ---
> > > >> 6 pings transmitted, 6 pongs received in time, 0.0% packet loss
> > > >>
> > > >> What fails is ipmipower:
> > > >>
> > > >> address@hidden root]# ipmipower --stat --hostnames 10.0.65.3
> > > >> 10.0.65.3: timed out
> > > >>
> > > >> This should not be an IPMI IP port issue (section 13.1 of 
> freeipmi> > >> documentation) because:
> > > >>
> > > >> address@hidden root]# tail -n 4 /etc/services
> > > >> # BMC IPMI/RMCP services
> > > >> rmcp    623/udp         # Aux Bus Shunt (Primary RMCP Port)
> > > >> rmcps   664/udp         # Secure Aux Bus (Secondary RMCP Port)
> > > >>
> > > >> I also have done the following:
> > > >>
> > > >> address@hidden root]# touch -f /var/lib/freeipmi/ipckey.new
> > > >> address@hidden root]# ls --inode /var/lib/freeipmi/ipckey*
> > > >> 3533355 /var/lib/freeipmi/ipckey  3533399 
> > > /var/lib/freeipmi/ipckey.new>> address@hidden root]# mv -f 
> > > /var/lib/freeipmi/ipckey.new>> /var/lib/freeipmi/ipckey
> > > >> address@hidden root]# ls --inode /var/lib/freeipmi/ipckey
> > > >> 3533399 /var/lib/freeipmi/ipckey
> > > >>
> > > >> Any suggestions?
> > > >>
> > > >> - Josh
> > > >>
> > > >> > Please try these steps and let me know.
> > > >> >
> > > >> >
> > > >> >
> > > >> > > The S2882 BIOS and the SMDC firware are the latest up to 
> date> > >> versions.
> > > >> > > The only sign of something amiss is the following bmc-
> config 
> > > output:>> > >
> > > >> > > ...
> > > >> > > Section Serial_Channel
> > > >> > > Error in checkout of key <Volatile_Access_Mode>
> > > >> > > Error in checkout of key <Volatile_Enable_User_Level_Auth>
> > > >> > > Error in checkout of key <Volatile_Enable_Per_Message_Auth>
> > > >> > > Error in checkout of key <Volatile_Enable_Pef_Alerting>
> > > >> > > Error in checkout of key <Volatile_Channel_Privilege_Limit>
> > > >> > > Error in checkout of key <Non_Volatile_Access_Mode>
> > > >> > > Error in checkout of key 
> <Non_Volatile_Enable_User_Level_Auth>> > >> > > Error in checkout 
> of key <Non_Volatile_Enable_Per_Message_Auth>
> > > >> > > Error in checkout of key <Non_Volatile_Enable_Pef_Alerting>
> > > >> > > Error in checkout of key 
> <Non_Volatile_Channel_Privilege_Limit>> > >> > > EndSection
> > > >> > > Section Serial_Conf
> > > >> > > Error in checkout of key <Enable_Basic_Mode>
> > > >> > > Error in checkout of key <Enable_PPP_Mode>
> > > >> > > Error in checkout of key <Enable_Terminal_Mode>
> > > >> > > Error in checkout of key <Connect_Mode>
> > > >> > > Error in checkout of key <Page_Blackout_Interval>
> > > >> > > Error in checkout of key <Call_Retry_Time>
> > > >> > > Error in checkout of key <Enable_DTR_Hangup>
> > > >> > > Error in checkout of key <Flow_Control>
> > > >> > > Error in checkout of key <Bit_Rate>
> > > >> > > EndSection
> > > >> > > ...
> > > >> >
> > > >> > Tyan does not support Serial Channel in BMC.  You can 
> safely 
> > > ignore>> this
> > > >> > as warnings and they are not related with 
> ipmipower,ipmiping or
> > > >> rmcpping.
> > > >> >
> > > >> >
> > > >> >
> > > >> > Thanks,
> > > >> >
> > > >> > Best Regards
> > > >> > Bala
> > > >> >
> > > >> > --
> > > >> > Free as in Freedom
> > > >> > http://www.gnu.org/
> > > >
> > > >
> > > 
> > > 
> > > -- 
> > > Free as in Freedom
> > > http://www.gnu.org/
> > > 
> > > 
> > > _______________________________________________
> > > Freeipmi-users mailing list
> > > address@hidden
> > > http://lists.gnu.org/mailman/listinfo/freeipmi-users
> > > 
> > 
> 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]