To control how Open Shortest Path First (OSPF) calculates default metrics for an interface, use the auto-cost command. To assign the default reference bandwidth of 40Gb/s, use the no form of this command.
auto-cost reference-bandwidth bandwidth [Gbps | Mbps]
Defaults
40 Gb/s. The bandwidth defaults to Gb/s if you do not specify the Gpbs or Mbps keyword.
I wonder why Cisco is leaning towards 40G instead of 100G.
One would think that Cisco will sell 40G linecards to the customer and .... a few months later the same customer has to buy 100G linecards.
Thursday, June 18, 2009
Sunday, June 7, 2009
14th is a sweet number
Friday, June 5, 2009
Nexus 7000 Notes - 4 (from test lab)
"write mem" (or any write command for that matter) is gone.
"copy run star" take approx 15 seconds to write the config and idle for another 35 seconds (exactly) before returning to the command. (have to figure out what is going on during that time)
Nexus no longer supports PagP. It is either LACP or EtherChannel.
OSPF process can either be a number or a name i.e. supports alpha-numeric OSPF process ID. OSPF network statements are now configured per interface basis instead of in router configuration. Not sure if it a good thing since OSPF network statements are scattered all over the places.
"show process cpu history" is gone.
"show process cpu" shows unfamiliar processes (looks like link processes). My co-worker says Cisco fixed high CPU problem by not showing the numbers to the users - at least with a familiar command.
"copy run star" take approx 15 seconds to write the config and idle for another 35 seconds (exactly) before returning to the command. (have to figure out what is going on during that time)
Nexus no longer supports PagP. It is either LACP or EtherChannel.
OSPF process can either be a number or a name i.e. supports alpha-numeric OSPF process ID. OSPF network statements are now configured per interface basis instead of in router configuration. Not sure if it a good thing since OSPF network statements are scattered all over the places.
"show process cpu history" is gone.
"show process cpu" shows unfamiliar processes (looks like link processes). My co-worker says Cisco fixed high CPU problem by not showing the numbers to the users - at least with a familiar command.
Subscribe to:
Posts (Atom)