hm.. ok lemme try ... This is what I got.
root> show spanning-tree interface
(-snipped-)
ge-0/0/45 128:535 128:535 32768.88a25ec89240 200000000 BLK DIS
ge-0/0/46 128:536 128:45 0.001560239400 200000 FWD ROOT
ge-0/0/47 128:537 128:46 0.001560239400 200000 BLK ALT
ge-1/0/47 128:547 128:48 0.001560239400 200000 BLK ALT
I'm guessing though that it would show it in LLDP anyway, otherwise I would only see one neighbor with spanning tree going. I plan on making all four connections LAG eventually.
root> show lldp neighbors
Local Interface Parent Interface Chassis Id Port info System Name
ge-0/0/46 - 00:15:60:23:94:00 45 ProCurve Switch 2650
ge-0/0/47 - 00:15:60:23:94:00 46 ProCurve Switch 2650
I tried moving one connection in the stack to the master one and that one suddenly appeared in the LLDP neighbor table.. so I am fairly sure its something i'm missing that is stack related.
UPDATE:
not sure what I did entirely, but I got this to work. I cleared out config, restacked, made sure I was looking at the right port, and added the interface to the configuration since it was missing. I'm not thrilled in how when you add a switch to the stack it means nothing in the config really, but as soon as I included it in the configuration it worked as expected.
So the ports were ge/0/0/46 and ge/1/0/46 (ge-0/0/46 was showing up but not ge-1/0/46)
then I added the port manually
ge-1/0/46 {
unit 0 {
family ethernet-switching {
vlan {
members default;
}
}
}
}
then did a commit syncronize, and that seemed to do the trick.
{master:0}[edit]
root# run show lldp neighbors
Local Interface Parent Interface Chassis Id Port info System Name
ge-1/0/46 - 00:15:60:23:94:00 47 ProCurve Switch 2650
ge-0/0/46 - 00:15:60:23:94:00 48 ProCurve Switch 2650
still unsure what I did wrong but ... oh well.. thanks for trying to help everyone!