Configure your Force10 with portmode hybrid and no spanning-tree pvst err-disable cause invalid-pvst-bpdu on the interface which faces the Cisco 6500... Reference: Force10 - Cisco STP Interoperability paper.
This is the complete configuration for your Port-channel (however, see the warning below)
interface Port-channel 2
portmode hybrid
switchport
no spanning-tree pvst err-disable cause invalid-pvst-bpdu
!
As described in the aforementioned white paper, the Force10 "Hybrid Mode" is required for an untagged Vlan1 on the trunk port. Note that hybrid mode accepts both tagged and untagged frames; however, it will err-disable when it sees the PVST+ BPDU from the Catalyst 6500. Thus, I recommended that you also use no spanning-tree pvst err-disable cause invalid-pvst-bpdu.
Warning:
According to at least one blog I found, hybrid mode must be configured before any switchport command; this means you might need to unbundle Port-channel 2 and add it again with portmode hybrid. Sadly, I can't confirm this myself since I don't have a Force10.
Also note that the Force10 needs manual configuration for each Vlan which gets tagged; I'm assuming you've already tagged your Force10 Vlans.
Assigning a /32 to an interface that connects to something else doesn't make any sense. You can assign the /32 to a loopback interface:
interface Loopback0
ip address 192.168.1.1 255.255.255.255
If you want to assign the 192.168.10.1 address to the GigabitEthernet0/0 interface which uses 192.168.10.0/24:
interface GigabitEthernet0/0
ip address 192.168.10.1 255.255.255.0
This results in the network 192.168.10.0/24 entry in the routing table as a connected route (C). I suppose it depends on the IOS version, but you can also get a local (not link local which is something else, entirely) route to the specific (/32) address assigned to an interface in your router. My IOS does this. The version you have doesn't show the L in the codes, whereas mine does as the first entry:
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override
`
Best Answer
The main issue is not related to LACP, but to how L2 (with SVI) and L3 ports handle spanning tree:
If you configure the link as L2 and configure an SVI, you will be running spanning tree on the Etherchannel (if it is enabled). This could have implications such as a 30 second delay before the Etherchannel transitions to Forwarding when it is brought up. If there is link instability, this would delay the link recovery time each time it bounces. Also consider the STP mode the switch is running. If it operates as CST (STP/RSTP), the Etherchannel may be affected by topology changes elsewhere in the network. Similar can happen with MST if it is sharing an instance with other VLANs. You also risk interacting with the SP's STP (if they haven't disabled). If you use L2, I would recommend disabling STP for the VLAN/Etherchannel and enabling BPDU filter. Alternatively, configure the Etherchannel to be an Edge Port (PortFast).
If you configure the Etherchannel as L3, it will not participate in STP. It will start forwarding as soon as the Etherchannel is brought up and will not be tied to your STP topology or that of your SP. L3 Etherchannel will be a lot more stable without requiring additional configuration.
I would recommend going with an L3 Etherchannel.