(no subject)
Boom, that's it. 2.40 hours of overtime and proof of concept has been given. The Foundry switch at the side of my desk has been configured into the management VLAN of the office and I've got the apple airport express reaching through it, to the border router and out to the internet.
This confirms is that base level of configs that I need, everything else is just window dressing. Proper name servers, logging of events, access control lists, control of what commands can be performed at what level. I'll sort that out as the night goes on. The PDF has already proven to be searchable on the different terms that make up the things I need for ntp, sntp in it's case.
Scott and Erica told me that they pretty much configure just like a Cisco. Nope, that description doesn't pan out the way that I first thought. It doesn't mean, per se, that they use the same commandset as Cisco's. In fact not at all, the commands are reliably something different. I think what they were saying, instead, was that once you figure out Cisco commands nothing else is all that difficult to wrap your head around.
The thing is, I may have been the Adtran go-to guy for the spazz install team, but that didn't mean I knew what the commands I was inputting into the devices meant, rather that I was very good at understanding what to do with the commands that the spazz cpe design team had written a script to spit out.
Now, back to going through the Cisco install commands that we use line-by-fucking-line and translating them over to Foundry.
This confirms is that base level of configs that I need, everything else is just window dressing. Proper name servers, logging of events, access control lists, control of what commands can be performed at what level. I'll sort that out as the night goes on. The PDF has already proven to be searchable on the different terms that make up the things I need for ntp, sntp in it's case.
Scott and Erica told me that they pretty much configure just like a Cisco. Nope, that description doesn't pan out the way that I first thought. It doesn't mean, per se, that they use the same commandset as Cisco's. In fact not at all, the commands are reliably something different. I think what they were saying, instead, was that once you figure out Cisco commands nothing else is all that difficult to wrap your head around.
The thing is, I may have been the Adtran go-to guy for the spazz install team, but that didn't mean I knew what the commands I was inputting into the devices meant, rather that I was very good at understanding what to do with the commands that the spazz cpe design team had written a script to spit out.
Now, back to going through the Cisco install commands that we use line-by-fucking-line and translating them over to Foundry.